Moderation bot

Hey,
I run a very public slack and we are looking for a way to moderate the chat (much like Moobot on twitch) the ability to timeout users (delete all their messages hey send in any channel or specific channel for a period of time), ban users, delete messages with trigger words (profanity), and personal message users (regardless of open dm or not) who have violated rules (or ability to send the "only you can see this" messages)
I'm more looking to see if this adapter has the ability to do some of these things, like check which channel it's in and check the users Id, for bans and deletions. Also deleting messages of users other then the bot.
Thanks :)

I'm no expert, but having implemented Hubot for a few different services I'd assume this project is primarily filling the "adapter" interface to allow Hubot to connect and perform standard actions (reading and responding to messages). I doubt the advanced features you want are included. But you could easily make a plugin for the bot that performs those actions via the Slack API and having Hubot do any automatic monitoring, etc... that you want to include. You can also add commands (limiting access via hubot-auth) that allow moderators to tell hubot to ban a user and after receiving the command hubot can go about banning the user following whatever specific process you desire.

By and large, anything that you can do with the Slack SDK is available through this adapter, or via the underlying Slack SDK! Closing as resolved.


Matrix?

First off, I would like to thank all of you for working on this project that allows beginners like myself to live inside emacs
Describe the feature
It would be great if doom had a module that set up and configured a matrix client, similar to how our irc module works already. Matrix is similar to discord in that it supports images and other stylistic abilites that irc lacks.
As far as I can tell, the prefered package to make emacs a matrix client is: https://github.com/alphapapa/matrix-client.el. The github repository also contains a shell script to isolate the matrix client from the rest of emacs, much like our everywhere or capture scripts.
If we were to add this modules, we would need to create some evil support; this repo lacks any form of evil-like bindings. We may also want to write some kind of integration for  some evil support; this repo lacks any form of evil-like bindings. We may also want to write some kind of integration for pantalaimon, so that we could get end-to-end encryption
System information
https://pastebin.com/tUbHEB7g
<!--
  Post the output of `M-x doom/info` or `~/.emacs.d/bin/doom info` to
  pastebin.com and paste the link here.
<!--

I have no plan to add such a module, largely because I don't use matrix and likely won't. I would be open an a PR, however, so I will leave this open until someone is willing to take it up. (Though, I will close and move it to Discourse, once our Discourse is up, since our issue tracker will no longer be for feature requests)
Keep in mind, however, that the module will be refused if the configuration ends up too trivial.
As for evil support, it may be better to bring that to https://github.com/emacs-evil/evil-collection.

That client deprecated in favor of https://github.com/alphapapa/ement.el


async is a reserved word in Python 3.7

from https://docs.python.org/3.8/whatsnew/3.7.html?highlight=reserved words:

Backwards incompatible syntax changes:
async and await are now reserved keywords.

This prevents us importing qpython as it complains that
def async(self, query, *parameters, **options):

is invalid syntax.

@streetster This and other minor issues running with the latests version of Numpy and Python have been fixed on this fork: https://github.com/nugend/qPython/commit/80d106714cd2d6d907e9f782848a90ec2442b6d1

is this actually going to get fixed in exxeleron/qPython?
thx


Couchbase Cluster Using Docker Compose

Article checklist
ATTENTION: In your PR - add the ISSUE (topic form) # that this PR corresponds to. You can do this by also adding a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.
NOTE: (Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
If you have not already please go over our Resources Page for more tips and tricks on how to improve our overall technical writing.
Preliminary Checks - Formatting and Structure

[x] Does your article follow any of the suggested structure formats? - see example formats
[x] Is your article properly formatted in Markdown? - see Github Markdown guide
[x] Have you used the correct folder and file structure? - see Contribution Guidelines
[x] Is your article over 750 words? - Tool: Wordcounter.net
[x] Have you used our preferred heading structure? - H3 (###) and up
[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.
[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.
[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images
[x] In your PR - add a comment that states "This fixes #(enter your Idea Content Form #)" to link and close your Idea Content (issue) when the PR is merged.

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid -  Grammarly
[x] Please place your article through a 3rd party plagiarism checker? We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide

Contribution guidelines
For first-time contributors and for more details, see Contributing Guidelines
This fixes #2299

plagiarism check completed - all good
2120420-1f5b2bfef94a39a65c4d-1626806270878.pdf

@jaredphelix amazing article.

Hi @jaredphelix
This is a great article. Easy to follow through.
Keep up the amazing job. Just check my commits for more edits on the flow.
cc: @paulodhiambo


tabs-item

hover tab
Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

redirect to #658 , closed.


Tree Structure support for taggings

Hi, do you have any plans for parent-child relation in taggings? Thanks

No, sorry!

Any ideas on how to use tags rather than categories and display in a nested format like categories?
i.e.
Category A
-- Subcategory 1
Category B
-- Subcategory 1
-- Subcategory 2

Duplicate of #74.


Bundle promql-lsp inside the extension

Downloading it after installation would also be ok but should be avoided.

Web Assembly might be the way to go here.

Web assembly is not properly supported in VS Code, so something else should be found.


feat(RHTAPREL-818): add product_version_name to advisory template

Moving to draft as there is an unresolved comment on the Jira about a second new field


how to set SetSegmentedIndex

I am using JCSegmentedBarController and i have 3 view controller declared in appdelegate.
But when app launch by default now its loads with the view controller at index 0, but i want to load the view controller at index 1 when app launch. Please help me how to set the default index of JCSegmentedBarController.

@darshanpatel9773 sorry, just saw your insues, after updating the code can use selectedIndex property settings

@lijingcheng Thanks


handles authentication

Simple authentication handling.
I carry the login urls with me via objects, which allows for more data to be added if needed.
Line 452 of script.js unblurs the area around the chart, but it doesn't matter for this pull request, so I commented it out.

Nice PR! The code here is clear and a digestible size!

Learned from the best

It looks like a lot of other files/changes got added into this PR, like the algorithm files. You might need to merge a few branches of approved PR work into master, then pull those changes from master into this branch.

@jessicaslaughter just seeing your comment...would it be ok just to merge everything with this one since every pr was approved before?


Adding Jenkins CI support and updating README

Adds Jenkins CI support (push and pull request)
Updates README to show relevant environment variables for custom builds

Coverage decreased (-1.13%) to 83.77% when pulling 7c480bc6f692cd5c5fc950cc46088c3e6b4c0920 on seatgeek:pr-jenkins into 0f4e0bb23f98b29903da3c3cbcd05e98648d57c4 on kt3k:master.

Really thanks for the enhancement and documentation!
I'll release it soon.

My pleasure.

Released this version as v2.2.0.
http://search.maven.org/#artifactdetails|org.kt3k.gradle.plugin|coveralls-gradle-plugin|2.2.0|jar
https://bintray.com/kt3k/gradle-plugins/coveralls-gradle-plugin/2.2.0/view
Thanks,

Hey @kt3k I've noticed that this is not showing the right pull number in coveralls.io; I've tried both the direct link and the number. Any idea what the value is supposed to be for the servicePullRequest?

https://coveralls.zendesk.com/hc/en-us/articles/201770395-Do-you-support-Circle-CI-pull-request-comments-
This post says it should be CircleCI's CI_PULL_REQUEST env var. I'm personally not using CircleCI, then I can't give an example at the moment, but I'll try to check it later.

https://github.com/circleci/frontend/blob/master/resources/assets/docs/environment-variables.md#build-details
According to this doc, it should be the url of the pull request. Hmm strange...

The original implementation uses the URL, but coveralls shows "Pull #0" and doesn't link to the correct PR when clicked either. This might need some input from the coveralls team.


[DO NOT MERGE] feat: added fscloud profile

Description
FSCloud implementation for the Data Engine module. This PR adds an FSCloud profile and example.
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[x] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[x] Examples or tests (addition or updates of examples or tests)
[x] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
If a release is required, replace this text with information that users need to know about the release. Write the release notes to help users understand the changes, and include information about how to update from the previous version.
Your notes help the merger write the commit message for the PR that is published in the release notes for the module.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

Data Engine does not support CBR, private endpoints or HPCS currently, so the fscloud profile is on hold

IBM Cloud® Data Engine is deprecated. As of 18 February 2024 you can't create new instances, and access to free instances will be removed. Existing Standard plan instances are supported until 18 January 2025. Any instances that still exist on that date will be deleted.


Update Configuring Docker Article

The "configuring docker" section is not updated to reflect the new packages, which no longer use /etc/sysconfig/docker on SystemD; https://docs.docker.com/engine/articles/configuring/#configuring-docker-1
Installation articles duplicate a lot of this same content.  Updating this should include fixing that material; we might want to update the installs to link to configuring rather than having a lot of material duplicated all around.
See #16662 for the origination story behind this issue

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

I have this page fixed so the RHEL/CentOS section is right. However, now that Ubuntu switched to systemd it kind of feels like this would just turn into a Upstart page as there already is a systemd page. I did try to make my section feel like the Ubuntu section even though it does duplicate some work done in the systemd page.
Should I still do a pull request and see what you think?

@jeffjohnston yes, please! It's easier for us to look at it and discuss / add suggestions. Thanks in advance!

Reopening this, per https://github.com/docker/docker/issues/9889#issuecomment-168379960; the Ubuntu section also needs a mention that newer Ubuntu releases use systemd

hello @thaJeztah I am a newbie to docker and working on configuring the private registry... I am unable to use --insecure registry on my rhel 7.2 OS. Here are the details on my config...
$docker version
Client:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:25:01 UTC 2015
OS/Arch:      linux/amd64
Server:
Version:      1.9.1
API version:  1.21
Go version:   go1.4.2
Git commit:   a34a1d5
Built:        Fri Nov 20 13:25:01 UTC 2015
OS/Arch:      linux/amd64
$docker info
Containers: 11
Images: 80
Server Version: 1.9.1
Storage Driver: devicemapper
Pool Name: docker-253:4-12897049-pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem:
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 3.289 GB
Data Space Total: 107.4 GB
Data Space Available: 6.996 GB
Metadata Space Used: 5.386 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.142 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.107-RHEL7 (2015-10-14)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.10.0-327.4.5.el7.x86_64
Operating System: Red Hat Enterprise Linux Workstation 7.2 (Maipo)
CPUs: 2
Total Memory: 1.954 GiB
Name: xyz
ID: NBC6:F2KA:DJOM:BPDV:G5MF:FNJW:KJCD:TVXU:6LEE:ZU7F:4B5N:PTGY
Username: write2sathyan
Registry: https://index.docker.io/v1/
By default I don't find the below files on my system...
/etc/default/docker
/etc/sysconfig/docker
I manually ran $ echo 'DOCKER_OPTS="--insecure-registry myregistry:5000"' > /etc/default/broker
And restarted the docker service but still I dont see the docker daemon running on insecure mode.
Are there anyway I would use $DOCKER_OPTS and declare in systemd files?
Looking for your help here....

RHEL 7.2 uses systemd; custom options for the daemon should be set by creating a "drop-in" file that overrides the default settings that are set in the systemd docker.service file. See this section for how to do that; https://docs.docker.com/engine/admin/systemd/#custom-docker-daemon-options

Hello @thaJeztah
As you recommended I created a drop-in file under "etc/systemd/system/docker.service.d" however still the docker daemon is starting with just the defaults not with the defined OPTIONS. Please let me know if I am missing anything here...
cat docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target docker.socket
Requires=docker.socket
[Service]
Type=notify
EnvironmentFile=-/etc/sysconfig/docker
EnvironmentFile=-/etc/sysconfig/docker-storage
EnvironmentFile=-/etc/sysconfig/docker-network
ExecStart=
ExecStart=/usr/bin/docker daemon -H fd:// --insecure-registry="<IP_ADDRESS>:5000"
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
[Install]
WantedBy=multi-user.target
pwd
/etc/systemd/system/docker.service.d
After service restart still it works with defaults...
ps -ef | grep docker
root      8717     1  0 14:40 ?        00:00:00 /usr/bin/docker daemon -H fd://

Did you sudo systemctl daemon-reload to load the changes?

You can also look at this page which shows a more condensed how-to for Redhat 7.x.
https://docs.docker.com/engine/admin/configuring/

Yes I did...
On Thu, Feb 18, 2016 at 3:09 PM, Sebastiaan van Stijn <
<EMAIL_ADDRESS>wrote:

Did you sudo systemctl daemon-reload to load the changes?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/16770#issuecomment-185943481.

Thanks @jeffjohnston and @thaJeztah
This time it worked !!! Instead of copying the entire file from "/usr/lib/systemd/system".. I just create a docker.conf with the required entries for ExecStart, that kicked-off the custom options while starting.
$cat docker.conf
[Service]
ExecStart=
ExecStart=/usr/bin/docker daemon -H fd:// --insecure-registry <IP_ADDRESS>:5000"
Thanks


test: Check for some unlikely null dereferences in tests

High Level Overview of Change
I stumbled upon these couple of places where test code could, but is very unlikely to, dereference a null pointer. I added a simple check to each of them.
Context of Change
This was a random find.
Even though these changes are tiny, I don't think they are insignificant enough to be considered "trivial", so I'm requesting two reviews.
Type of Change

[X] Bug fix (non-breaking change which fixes an issue)
[X] Tests (you added tests for code that already exists, or your new feature included in this PR)

Before / After
There should be no observable change, as tests aren't currently likely / able to get a null value.
Future Tasks
Maybe there are more of these?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 70.9%. Comparing base (3f7ce93) to head (95ca921).

Additional details and impacted files

@@           Coverage Diff           @@
##           develop   #5004   +/-   ##
=======================================
  Coverage     70.9%   70.9%
=======================================
  Files          796     796
  Lines        66792   66792
  Branches     11015   10999   -16
=======================================
+ Hits         47356   47374   +18
+ Misses       19436   19418   -18

see 8 files with indirect coverage changes

Hold pending 2.3.0 release.

Manually merged as 8215c605b456d16ce041f5fc579e0dfdaf415576
$ git diff --exit-code 8215c605b456d16ce041f5fc579e0dfdaf415576 ximinez/pr/test_fixes && echo Identical
Identical


Set evaluation epoch iterator object to None for each model.fit call

When using model.fit() with validation_data, during first call to fit() it will create an EpochIterator object for evaluation and cache it. This cache will be deleted after completion of all epochs.
However if we try to change the validation_data shapes for any reason and called model.fit() again it will raise an exception like Graph execution error which is intended. After this if we call model.fit() with correct validation_data that of first training call it won't work.
The reason being is after first call is success evaluation EpochIterator will be deleted at the end and during second training call a new EpochIterator will be generated again with changed shape.But during evaluate() call it will raise an exception terminating the process without deleting evaluation EpochIterator object and it remains in cache. During third call though with correct validation_data it will not create new EpochIterator object as one already exists in cache which makes it fail again.
Hence proposing a fix for this with this commit.
Fixes #18653

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (6e54f7f) 78.50% compared to head (e48e4f8) 57.93%.
Report is 2 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18659       +/-   ##
===========================================
- Coverage   78.50%   57.93%   -20.57%
===========================================
  Files         334      334
  Lines       32596    32606       +10
  Branches     6376     6377        +1
===========================================
- Hits        25589    18891     -6698
- Misses       5452    12285     +6833
+ Partials     1555     1430      -125

Flag
Coverage Δ

keras
57.93% <0.00%> (-20.46%)
:arrow_down:

keras-jax
?

keras-numpy
57.93% <0.00%> (-0.02%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

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

Files
Coverage Δ

keras/backend/torch/trainer.py
0.00% <ø> (-90.05%)
:arrow_down:

keras/backend/jax/trainer.py
0.00% <0.00%> (-95.52%)
:arrow_down:

keras/backend/tensorflow/trainer.py
13.98% <0.00%> (-64.52%)
:arrow_down:

... and 176 files with indirect coverage changes

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


Data Stream support for Audit- Log

Description
Documentation for the MR https://github.com/opensearch-project/security/pull/4257
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@tmanninger: Is there a doc issue associated with this PR?

@natebower: This is ready for editorial review.


Add support for github.com/aws/aws-lambda-go/lambda#Handler

What does this PR do?
This adds support for the Handler interface from github.com/aws/aws-lambda-go/lambda.
Motivation
I tried to emit metrics from a lambda using apex/gateway, it failed. With this change, code like the following works:
package main

import (
	"net/http"

	ddlambda "github.com/DataDog/datadog-lambda-go"
	"github.com/apex/gateway"
	"github.com/aws/aws-lambda-go/lambda"
)

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		w.WriteHeader(http.StatusOK)
	})

	lambda.Start(ddlambda.WrapHandler(gateway.NewGateway(http.DefaultServeMux), nil))
}

Testing Guidelines
go test -v ./...
Types of changes

[x] Bug fix
[x] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Checklist

[x] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[x] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

Unfortunately, this turns out not to work in practice 😢
The way lambda.Start is implemented doesn't support returning already marshaled JSON. Something like the following works though:
package main

import (
	"context"
	"encoding/json"
	"net/http"
	"reflect"

	ddlambda "github.com/DataDog/datadog-lambda-go"
	"github.com/apex/gateway"
	"github.com/aws/aws-lambda-go/lambda"
	"github.com/pkg/errors"
)

func main() {
	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		w.WriteHeader(http.StatusOK)
	})

	lambda.StartHandler(&ddlambdaInvoker{handler: gateway.NewGateway(http.DefaultServeMux)})
}

type ddlambdaInvoker struct {
	handler lambda.Handler
}

func (i *ddlambdaInvoker) Invoke(ctx context.Context, payload []byte) ([]byte, error) {
	withMetrics := ddlambda.WrapHandler(i.handler, nil)

	f, ok := withMetrics.(func(ctx context.Context, msg json.RawMessage) (interface{}, error))
	if !ok {
		return nil, errors.Errorf("unexpected return type from ddlambda.WrapHandler: %v", reflect.TypeOf(withMetrics))
	}

	result, err := f(ctx, payload)
	if err != nil {
		return nil, err
	}

	resultBytes, ok := result.([]byte)
	if !ok {
		return nil, errors.Errorf("unexpected return type calling handler, expected []byte, got: %v", reflect.TypeOf(result))
	}

	return resultBytes, nil
}

Implementing first class support for this in the package seems like a fair bit more work :/

@Bowbaq Regarding your latest comment "Unfortunately, this turns out not to work in practice". Are you still interested in working on this PR? Otherwise, I would like to close it to reduce the noise in our internal tracking tool :)

@Bowbaq I just noticed that you actually force-pushed some changes after your original comment. So do you still want to push this change forward and get a review from us? Thanks for your contribution, btw!

Hi @Bowbaq, we are going to close this pull request for now, but do let us know if this is something you want to continue pursuing. Thank you for your contribution!


IDVA6 1407 Add analytics for remove member and remove yourself flow

Link to Jira
https://companieshouse.atlassian.net/browse/IDVA6-1407
Change Description
Add Matomo (data-event-id) tags for the remove-member page, the remove member success page, remove yourself success page and the stop page when user is the only owner and removing themselves.

CI: No security warnings found


feat: added-media-dialog-component

Summary

This PR adds the MediaDialog component. This PR is not to be approved as it still has bugs.
Test plan

Hey @austincondiff, I'm having trouble understanding how the sizing is working for ThumbnailGrid. Take a look and see. When I reload the component, the size of children elements changes on the same view screen. Any ideas?

@tinfoil-knight We need to change the ThumbnailGrid component to accept a minWidth prop. Preserve the values that are there as default values (if this new minWidth prop is not defined). Check out the file here... https://github.com/netlify/netlify-cms/blob/v3-ui-redesign/packages/netlify-cms-ui-default/src/Thumbnail/ThumbnailGrid.jsx

@austincondiff How does this looks?

Looks great! Nice work! 👏🏻


Jest testID react-native

Hi guys, can you please add the testID to the icons?  Thanks

We do not maintain the React Native library, please create an issue over on the phosphor-react-native repo.


Opened wallet file from .2.2 with .3.0 and now it I can no longer access my Nano S.

What to I do?

I couldn't even open my wallet from 0.2.2.
I ended up creating a new wallet using my ledger nano x.
Create a new receive address.
Then open 0.2.2 with existing wallet and send all funds from your 2.2 wallet over to new 0.3.0 receive address.
But then all of a sudden, all my transactions from my wallet 0.2.2 showed up in new version!!!
And my old receive address isn't showing in 0.3.0 version but it's still receiving from foxypool using that old address.
Does this mean that address is locked to ledger or something?

Everything is tied to your ledger device so your funds are safe. You can create a new wallet with it if you need to. Seems to be a problem upgrading wallet files. There should be log files in your electrum folder would you mind posting the error here?

electrum_log_20210608T211727Z_12060.log

I see the problem, thank you for the help. This will be fixed in the next update. For now creating a "new" wallet again with your ledger or re-entering your seed words if its a software wallet will allow to make the jump from 0.2.2 to 0.3.0

Closed in favor of https://github.com/Electrum-RVN-SIG/electrum-ravencoin/issues/4

OK.  Sorry, I'm a bit new to all of this. So my old wallet is no longer accessible and all the coin in it is gone?


Skip all integration tests that are failing for now and add a note in the automated test guide

The guide is: https://github.com/bf2fc6cc711aee1a0c2a/ffm-fleet-manager-go-template/blob/main/docs/automated-testing.md#integration-tests
It might catch some people by surprise to see the integration tests failing. The idea of having some integration tests was to be able to show how the setup phase is done. So it actually makes sense to skip the failing ones with a note on why they are failing and what will be needed to make them pass.

Closed by https://github.com/bf2fc6cc711aee1a0c2a/ffm-fleet-manager-go-template/pull/29


Added min_assets params

Summary of changes

min_assets parameter has been added in providing liquidity msg
As the type is Option<[Asset, 2]>, it doen't occur any break. (Default min_assets is 99.5% of the input assets)
Need slippage tolerance option in the frontend. And min_asset = asset * (1 - slippage_tolearnce) should be applied

Report of required housekeeping

[ ] Github issue OR spec proposal link
[ ] Wrote tests
[ ] Added a relevant changelog entry to CHANGELOG.md

(FOR ADMIN) Before merging

[ ] Added appropriate labels to PR
[ ] Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)
[ ] Confirm added tests are consistent with the intended behavior of changes
[ ] Ensure all tests pass

Codecov Report
Patch coverage: 97.14% and project coverage change: +0.26 :tada:

Comparison is base (cca56ff) 90.12% compared to head (72421ee) 90.39%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   90.12%   90.39%   +0.26%
==========================================
  Files          17       17
  Lines        3099     3133      +34
==========================================
+ Hits         2793     2832      +39
+ Misses        306      301       -5

Impacted Files
Coverage Δ

contracts/dezswap_pair/src/testing.rs
99.43% <95.65%> (+0.01%)
:arrow_up:

contracts/dezswap_pair/src/contract.rs
92.92% <100.00%> (-0.06%)
:arrow_down:

... and 4 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


(fix #2607): Fix router.back in abstract mode when 2 consecutive same routes appear in history stack

This PR provides a fix to the issue #2607.
Reproduction link
https://jsfiddle.net/Rocka/bhu5vkn8/3/
In abstract mode, if you try to navigate through your history with the same routes appearing consecutively in your stack history, the history index remains unchanged.
In History or Hash mode, this issue does not appear because history navigation is handled by the browser and not by vue-router. In all modes, we do not want to re-render a page if the current route and the next route are identical. However, in the case of abstract mode, we still need to update the history index whenever the current and next routes are the same since AbstractHistory handles its own history stack.

I rebased against dev and adapted the code to use an Error object

Thank you @posva !


old events

simulcast and exploring still showing up on home page

Hmmm... I'm not seeing this in Chrome, Firefox, or Safari on my mac. Is this on iPhone?


docs: add github action workflows to update README on DockerHub

Update README and make it a basic documentation for running cassandra-stress.
README is propagated to DockerHub where cassandra-stress image is uploaded after release

Closes #5

@annastuchlik
we want to embed this one into core docs as well
in https://github.com/scylladb/scylladb/pull/21723
any advise on how to keep them in sync ? maybe just reference this repo from the core docs ?

@annastuchlik
we want to embed this one into core docs as well in scylladb/scylladb#21723
any advise on how to keep them in sync ? maybe just reference this repo from the core docs ?

The main issue is that core docs are written in RST, and this one is in Markdown, Dockerhub does not support RST (tried it first), so keeping them in sync is a bit tricky, unless we do some translation between the two. Just referencing this page, does not look good on documentation site.
I can try something with GitHub Actions to translate MD to RST and open PR to core repo with DIFF from Markdown. Is that ok solution @fruch?


Yarn Warning when compiling for neovim: warning<EMAIL_ADDRESS>The engine "vscode" appears to be invalid.

yarn install --frozen-lockfile and yarn compile both return error warning<EMAIL_ADDRESS>The engine "vscode" appears to be invalid.

@CharaD7  im also getting this and i can't get the snippets to work. Did you amke any progress?


The search fails if the filter contains non-ascii characters and "*"

This issue is the sequel of ldapjs/node-ldapjs#860. After upgrading to v3, my search request fails when combining wildcard (*) and non-ascii characters. Using Apache directory studio or ldapsearch my search request succeeds but not when using ldapjs.
I have read the logs on my OpenLDAP server and we clearly see a problem on how the filter is processed:
ldapjs for (&(description=*réseau*))
In the logs: filter="(&(description=*r\5Cc3\5Ca9seau*))"
❌ Not working
Apache Directory Studio for (description=*réseau*)
In the logs: filter="(description=*r\C3\A9seau*)"
🆗 Working
ldapjs for (&(description=réseau))
In the logs: filter="(&(description=r\C3\A9seau))"
🆗 Working thanks to ldapjs/node-ldapjs#860 and no wildcard
ldapjs for new EqualityFilter({ attribute: "description", value: "*réseau*"})
In the logs: filter="(description=\2Ar\C3\A9seau\2A)"
❌ Not working
ldapsearch for (description=*réseau*)
In the logs: filter="(description=*r\C3\A9seau*)"
🆗 Working
Thank you in advance for your help!

Good find. The out.final is likely also incorrect. See the findings in https://github.com/ldapjs/filter/issues/6. Are you willing to contribute a PR to resolve this issue?

Good find. The out.final is likely also incorrect. See the findings in #6. Are you willing to contribute a PR to resolve this issue?

I have opened a PR, please tell me if something is missing!

In the meantime, to solve this problem in my project I have added the following script as a postinstallation script in package.json:
const colors = require('colors');
const fs = require('fs');
const path = require('path');

const nodeModulesPath = path.resolve(process.cwd(), 'node_modules');
const packageName = '@ldapjs';

console.log(path.resolve(nodeModulesPath, packageName));
if (!fs.existsSync(path.resolve(nodeModulesPath, packageName))) {
    console.log(colors.red(`@ldapjs was not found.`));
    return;
}

console.log(colors.yellow(`Detected "${packageName}" package...`));
console.log(colors.yellow(`Applying ldapsjs@3 patch`));

const fileToPatchPath = path.resolve(
    nodeModulesPath,
    packageName,
    'filter',
    'lib',
    'string-parsing',
    'escape-substring.js'
);

const fileContent = fs.readFileSync(fileToPatchPath, { encoding: 'utf8' });
if (!fileContent.match('escapeFilterValue')) {
    colors.red(
        `Nothing to patch found in @ldapjs/filter.`
    );
}

fs.writeFileSync(
    fileToPatchPath,
    fileContent
        .replace(`const escapeFilterValue = require('../utils/escape-filter-value')`, ``)
        .replace(`escapeFilterValue(fields.shift())`, `fields.shift()`)
        .replace(`escapeFilterValue(fields.pop())`, `fields.pop()`)
        .replace(`fields.map(escapeFilterValue)`, `fields`)
);

console.log(colors.yellow(`ldapjs@3 patch was successfully applied`));


[ZEPPELIN-4964] Cassandra: add formatter for decimal values

What is this PR for?
New options for formatting of decimal values.  By default, formatted without any
precision loss (by specifying special value -1 as precision)
What type of PR is it?
Improvement
What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-4964

How should this be tested?

https://travis-ci.org/github/alexott/zeppelin/builds/710727496
tested manually

LGTM


Select what aspect ratio you want through the Lazy Pack generator

Just to make life a bit easier for the lazy ones (like myself lol) make it so that we can select which aspect ratio we want in the Lazy Pack generator, and also make it so that they are compatible with the UI mods. But if that is not possible then it's ok, you devs have already done a lot for the TOTK modding community anyway, so thank you :)

I think what Chuck means when he says he is working on aspect ratios is some resolution related patch to make the game less blurry when rendering in ultrawide. Right now the ultrawide mod just increases the fovx while using the same amount pixels, essentially leading to strechted out pixels. Dynamic fps still only supports 16:9 resolutions I believe. I don't think Chuck is working on changing the actual aspect ratio or on UI changes. Anyway, I'm just guessing. Probably should indeed just wait and ask him directly to be sure.

say, has any of you had any luck contacting him?
i've been trying for over a month now, and he's just permanently unresponsive

New TOTK Optimiser by @MaxLastBreath  features aspect ratio functionality


Support for PHPStorm 9.0.2

I'm using PHPStorm 9.0.2 and would be great to have this plugin here. Can make it happens?

what about remove it and re-install from repository?

thanks it works.
I was downloading the jar file and adding to my ide.


Subsetting Dataset not equivalent to subsetting raw data then creating Dataset

Using Dataset.subset() to train on specific rows of your data is not equivalent to creating a new Dataset with only those specific rows (I've included an example below).
I assume maybe this is the intended behavior? Is it because when you create the Dataset on data some global properties are computed like histogram bin widths and these are copied to the subset Dataset? If that's the case what is the use case for the subset function?
My intended use case is to train many models on different subsets of the data, in a way that data/information from outside of the subset doesn't leak into the subset. Is there a way to do that without creating a completely new Dataset for every subset?
Thanks in advance.
import pandas as pd
import numpy as np
import lightgbm as lgb

data = pd.DataFrame(np.random.rand(100, 10))
data.columns = [str(i) for i in range(len(data.columns))]

feature_columns = list(data.columns)[2:]
label = '1'
# Masking specific rows
index = data['0'] < 0.2

# Creating the datasets using the same rows, first by masking the data then with subset()
ld1 = lgb.Dataset(data[index][feature_columns], data[index][label], free_raw_data=False).construct()
ld2 = lgb.Dataset(data[feature_columns], data[label], free_raw_data=False).subset(np.flatnonzero(index)).construct()

# Check that the underlying data is the same
assert not np.any(ld1.get_data() != ld2.get_data())

reg1 = lgb.train({}, ld1)
reg2 = lgb.train({}, ld2)

# Get predictions
data['reg1'] = reg1.predict(data[feature_columns])
data['reg2'] = reg2.predict(data[feature_columns])

# Returns true because of different predictions
np.any(data['reg1'] != data['reg2'])

This is the intended behavior. When creating the subset LightGBM uses the same bin thresholds as the original dataset instead of calculating them from scratch. However the histogram (i.e. the number of data points in each bin) is recalculated for the subset.
This functionality is used for cross-validation in CVBooster (https://lightgbm.readthedocs.io/en/latest/pythonapi/lightgbm.CVBooster.html)
I think subset is suitable for your use case; the only information leakage will be that the bin thresholds are calculated using the full dataset. If you want to avoid even this, you could manually specify the binning thresholds, see https://github.com/microsoft/LightGBM/blob/master/examples/regression/forced_bins.json


Deploy Your Multi-Target Application (MTA)

Tutorials: https://developers.sap.com/tutorials/btp-app-cap-mta-deployment.html
In step 4 of this tutorial, I recommend that you first run the node --version command to check that you use the minimal required version of Node.js. If it's higher than 16, you can go ahead and set the v16 limitation.

Mahati, can you please address this user's feedback?  Thank you.

Hello,
Sorry for not replying earlier, I'll fix this and close it after it's published.
Best regards,
Mahati


Make it possible to extend a KeyPair-credential with a certificate

In some cases, for example in a CA, the key pair is first generated, and then the certificate is issued. We should make sure that this case can be handled.

Closed by PR https://github.com/swedenconnect/credentials-support/pull/13


Changed DryIoc.Syntax.Autofac to target .Net Standard

This should close #193
@dadhi Please let me know of any changes. I appreciate your hard work in maintaining DryIoc.

That's fine, thanks.
I would like to extend the package more, but don't have as much time.


Checkpoint

Units are looking good, but I've not yet fully integrated this into a true pipeline, e.g. chipseq.py,.
Wanted to go ahead & open for review, though, since the tests are behaving.
The elements to focus on, IMO, are stage.Stage, pipeline.Pipeline, and updates to PipelineManager (now in manager.py)
Close https://github.com/epigen/pypiper/issues/56

This is an implementation for https://github.com/epigen/pypiper/issues/56

this version gives an erroneous message. Why is it generating recover files when target exists? there should be no lock or recovery files generated.
Here's an example from pepsra:
Expected output:
Processing 1 of 4

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030718.bam`
Processing 2 of 4

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030719.bam`
Processing 3 of 4

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030720.bam`
Processing 4 of 4

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030721.bam`

Actual output:
Processing 1 of 4
Generating recovery file from lock file: '/sfs/lustre/allocations/shefflab/data/sra/lock.__sfs__lustre__allocations__shefflab__data__sra_bam__SRR1030718.bam'

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030718.bam`
Processing 2 of 4
Generating recovery file from lock file: '/sfs/lustre/allocations/shefflab/data/sra/lock.__sfs__lustre__allocations__shefflab__data__sra_bam__SRR1030719.bam'

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030719.bam`
Processing 3 of 4
Generating recovery file from lock file: '/sfs/lustre/allocations/shefflab/data/sra/lock.__sfs__lustre__allocations__shefflab__data__sra_bam__SRR1030720.bam'

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030720.bam`
Processing 4 of 4
Generating recovery file from lock file: '/sfs/lustre/allocations/shefflab/data/sra/lock.__sfs__lustre__allocations__shefflab__data__sra_bam__SRR1030721.bam'

Target exists: `/sfs/lustre/allocations/shefflab/data/sra_bam/SRR1030721.bam`

Sorry, good catch. The message is misleading; it's not actually creating the files (at least I think it's not & definitely shouldn't be); the message is being provided at time of derivation of that filepath.

ok that fixed it.

this is adding another error message:
Could not remove flag file: '/sfs/lustre/allocations/shefflab/data/sra/sra_convert_initializing.flag'

which was not previously showing up.

It also adds another redundant error message:
Can't find custom config file: /sfs/nfs/blue/ns5bc/code/pepsra/sra_convert/sra_convert.yaml
No config file

previously it didn't say "No config file" as well.

The config file message redundancy and flag removal message for initialization should be gone with the most recent commit.

Counting raw fastq reads is broken:
> `Raw_reads`	-1	ATACseq	_RES_
> `Fastq_reads`	19486778	ATACseq	_RES_
Skipping undefined pypiper argument: 'sample_name'
Traceback (most recent call last):
  File "/home/ns5bc/code/ATACseq/pipelines/ATACseq.py", line 655, in <module>
    sys.exit(main())
  File "/home/ns5bc/code/ATACseq/pipelines/ATACseq.py", line 303, in main
    follow=ngstk.check_fastq(local_input_files, unaligned_fastq, args.paired_end))
  File "/sfs/nfs/blue/ns5bc/.local/lib/python2.7/site-packages/pypiper/manager.py", line 686, in run
    call_follow()
  File "/sfs/nfs/blue/ns5bc/.local/lib/python2.7/site-packages/pypiper/manager.py", line 619, in call_follow
    follow()
  File "/sfs/nfs/blue/ns5bc/.local/lib/python2.7/site-packages/pypiper/ngstk.py", line 507, in temp_func
    raise Exception("Fastq conversion error? Number of reads "
Exception: Fastq conversion error? Number of reads doesn't match unaligned bam

I flagged where I may have found the error but too much has changed for me to really diagnose...
This example case is specifically with gzipped fastq input.

Closer but still not quite there;

Raw_reads	1645650
Fastq_reads	47803236

Ok, that should do it. it's working now.

can you add a readme for devs on how we should run tests now? my old way of testing is no longer functional with this PR, and when I run 'pytest' it does not show the output as it used to -- it looks like it's still running the old tests, how can we make it show the output?

can you explain the rationale for having both a Pipeline and a PipelineManager class? What is the difference? Why not just have 1 class?
I am not sure I would name this new class "pipeline", as to me, that is what the python script itself is, so there a conceptual disconnect at least in the way I think of things.

Mostly separation of concerns. Generally, fewer and larger classes impedes code comprehensibility.

Ok, I don’t have a strong name preference. Yes, it essentially represents a program/script. Like in the new chipseq version, there’s a main method that calls into the arguments parser but then is primarily responsible for building the pipeline instance and allowing it to handle execution

both Pipeline and PipelineManager are user-facing, right? To me this adds confusion, I wouldn't understand why there are 2 classes, and what the difference is. I would favor a single user-facing class -- it doesn't have to be a huge class, I'm not opposed to subdividing the classes, but maybe we can do that internally and then present only single interface to the user?
the checkpoint is really just adding a single new function to pypiper, it doesn't seem to necessitate presenting the user with two classes

Just to keep a note here for later: I think the cleaning is now too verbose ("1 items to clean: 0 items to clean: 1 items to clean:" etc)

Agreed!

Is this ready to be merged or are you still working on it?

I'd like to write up a couple more tests, but I feel pretty good about it. If you have something small that you'd like to test with however you envision using the checkpointed timestamping and start/stop, that'd be a huge plus but I think not immediately necessary since this is just to dev.

if you use stop-after, it calls fail_pipeline on every subsequent command call, and keeps changing status flags back and forth. it's doing weird stuff for me.

I think I'm understanding better now; I think it needs to raise an exception to cause the pipeline to quit, so it doesn't keep progressing (even though it doesn't run subsequent commands, it should just stop and not even attempt to run them).

Units and some in-person tests look good, merging with permission from @nsheff


[Configurable] Revisit Config.toml file location for configurables

Description:
Currently, Config.toml file  is located for program execution in the following ways.

Path is given in an environment variable BALCONFIGFILE
look for Config.toml in the current working directory (where the CLI command is executed)

It would be better to have an option to locate the file at the project root before looking at the current working directory.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):
https://github.com/ballerina-platform/plugin-vscode/issues/132
Suggested Labels (optional):
Suggested Assignees (optional):

It would be better to have an option to locate the file at the project root before looking at the current working directory.

Not before current working directory, we should only pick the project root config for development time tasks.
current working dir will be used for jar execution.

We need to find the location for single bal file scenario

I feel like having it next to source is better for user experiences for the development tasks. When we are working via VSCode, we'll anyway have to enforce it. Otherwise there has to be a UI in VSCode to specify it.
So I think it's better to enforce it from the language itself.
WDYT @sameerajayasoma
related issues was pointed by @prabushi


Fix type issue / Update amqp cacoon

Fix type issue
Update amqp cacoon library

:tada: This PR is included in version 2.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Subselected value should be nullable

Version
1.10.0
What happened?
-- name: ShouldHaveNull :many
select
   (select other_table.name from other_table where this_table.name = other_table.name) as "name"
from this_table;

sqlc will generate an output struct like this:
type ShouldHaveNullRow struct {
  Name string
}

But the struct should be:
type ShouldHaveNullRow struct {
  Name sql.NullString
}

The above example is with strings but I thought it was relevant to mention that this is happening with a replaced type that's configured similarly to:
  - db_type: "pg_catalog.numeric"
    nullable: false
    go_type:
      import: "github.com/shopspring/decimal"
      type: "Decimal"
      pointer: false
  - db_type: "pg_catalog.numeric"
    nullable: true
    go_type:
      import: "github.com/shopspring/decimal"
      type: "NullDecimal"
      pointer: false

I know the types in this example are all messed up. I'm in a huge rush and don't have time to file the issue with extreme precision at this moment.
You can see in the playground link because the type is non nullable in the table, it incorrectly assumes that the subselect can never return null for that field.
Relevant log output
No response
Database schema
No response
SQL queries
No response
Configuration
No response
Playground URL
https://play.sqlc.dev/p/bb47e4143c86e1b45bc659b147c4072d0464d968332d8598e36f7c2e3e531f18
What operating system are you using?
Linux
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

I think you may be misunderstanding the complaint.
Let me explain more clearly (I have a bit more time now). There is a subselect query happening where we're retrieving a single value from it:
(select o.name from one o where one.name = 5 limit 1) as "name"

If you look at the struct it created to capture the result of Test query it is:
type TestRow struct {
	Otherfield sql.NullString
	Name       decimal.Decimal
}

However it should be:
type TestRow struct {
	Otherfield sql.NullString
	Name       decimal.NullDecimal // note the difference here
}

The first struct (the one sqlc generates and is in my playground link) is incorrect. This valid query cannot properly be bound to this struct for all possible return values. Does that make it more clear?
Your example is working I agree. However I could only reproduce when using type overrides which your example does not include. Please take another look.

I am also having the same problem. Even if I reflect the type in sqlc.yml in the subquery results, it is not applied. Could you please check this Issue again?

@voluntas pinged me on this issue, but I cannot find where the problem is here. I am having no problems generating the correct return types. I think there needs to be better repro instructions

@WesleyMiller1998 I agree this issue configuration and generation seems to works fine; as the override is done at the database data type. However, your issue #1752 the override requested is by column name and it does have a bug. @kyleconroy I propose this issue to be closed.

@jakoguta @WesleyMiller1998 this issue is still a real issue. There's a clear reproduce here in my original playground link: https://play.sqlc.dev/p/bb47e4143c86e1b45bc659b147c4072d0464d968332d8598e36f7c2e3e531f18
Note the struct:
type One struct {
	ID         int32
	Otherfield sql.NullString
	Name       decimal.Decimal
}

Until Name is generated as a decimal.NullDecimal (as per the config for the nullable decimal type) there is a bug here as the Name field in the query is coming from a subselect which can be null. See the query here:
-- name: Test :many
select
	otherfield,
	(select o.name from one o where one.name = 5 limit 1) as "name"
from one;

In the simplest case, if the one table is null, this query will run fine in postgres and return results, and then the results should fail to bind properly because null will be returned and attempt to scan into Name decimal.Decimal which isn't a valid value for a decimal.Decimal.
Kyle's response earlier in the thread tries to show that there is "no bug" by creating a smaller reproduce but in doing so avoids the bug altogether because the bug seems contingent on having replaced types in the config file (as I have in my playground link).
Let me know if further explanation is required but let's keep the issue opened so long as sqlc is generating structs that cannot be bound to all result sets from a given query.

@aarondl0 Thank you for the response I'm understanding the problem much better now and you are absolutely correct that it is generating the wrong type. I've spent a good hour digging around in the code and I think I found the issue, but I am not entirely sure yet. I will update later this week

Okay, as I thought I located the issue. It has to do with the follow [lines of code]:(https://github.com/kyleconroy/sqlc/blob/0ae16d272c715c8ef91197512bef98e34b03fbe2/internal/compiler/output_columns.go#L230-L250)
case *ast.SubLink:
			name := "exists"
			if res.Name != nil {
				name = *res.Name
			}
			switch n.SubLinkType {
			case ast.EXISTS_SUBLINK:
				cols = append(cols, &Column{Name: name, DataType: "bool", NotNull: true})
			case ast.EXPR_SUBLINK:
				subcols, err := outputColumns(qc, n.Subselect)
				if err != nil {
					return nil, err
				}
				first := subcols[0]
				if res.Name != nil {
					first.Name = *res.Name
				}
				cols = append(cols, first)
			default:
				cols = append(cols, &Column{Name: name, DataType: "any", NotNull: false})
			}

With this particular example, we hit the EXPR_SUBLINK switch case where we then recursively determine the output columns of the select statement. I created a PR: #1758 which does allow for type generation to occur as expected. I can't see any obvious negative impact from this, but I would really like some general thoughts on if this appropriate.

@aarondl0 とても丁寧な再現方法をありがとうございます。私も同様の問題が発生しています。


Missing dependencies in python package

Hi, not sure if this is an issue with package dependencies or an issue of compatibility between pip and conda.
After creating an environment like so:
conda create -n testing_tea python=3.7
And installing tea:
conda activate testing_tea
pip install tealang
The install process shows no errors, but when attempting to import tea, I get a
ModuleNotFoundError for pandas, followed by a number of other packages. This is resolved by installing everything in the pipfile by hand.
I would guess that a lot of people (like me) who would be interested in the project are accustomed to using conda, so smoothing this out would be beneficial.
Very cool work by the way, looking forward to further development and added features 👍

Hi @g-simmons2 ! So sorry for the latency.
GREAT point! I hadn't run into this issue before. Let me look into how I can make the installation process easier for Conda users!
Be in touch...
Eunice

By the way, those're all packages needed (at version 0.0.10):
pip install tealang pandas scipy sklearn statsmodels bootstrapped z3-solver
HTH

Even after using the pip install line above I still have the error AttributeError: module 'z3' has no attribute 'BoolSort'

This should be working now.
I have installed tealang on conda environment as provided by OP and everything worked fine.
I think we can close this issue, new users can open a new one.


is it possible to change the credits?

What is your question?
i wanted to know so i can add myself into the credits

Yes, you need to edit CreditsState.hx including your own credit icon, twitter link (optional, you can use YouTube as an alternative.


Problems using script after updating python.

I recently updated python to 3.10, when doing so, i noticed in mpv that autosubsync was no longer working for whatever reason, whevener i try to use it with ffsubsync it gives this error: "couldn't add synchronized subtitle", alass: "subtitle synchronization failed", can you help me sort out this bug? i'm not really sure what caused it, it just started happening after i updated python to do a project, i installed python 3.9.13, uninstalled every other python version i had, reinstalled ffsubsync and autosubsync on mpv and yet i i'm not able to use the script.
Windows 10 x64 21H1, mpv 0.34.0-468-gba81e4ed88, Python 3.9.13, FFmpeg version: git-2022-09-17-ed83a3a5b

When you upgrade python, usually you have to reinstall all pip packages installed in the home directory because they are not automatically transferred to a newer python version. On GNU the packages are stored in ~/.local/lib/python3.XX. You also have to be sure that the directory where pip stores executable scripts is added to the PATH.
Try upgrading from Windows. I recommend installing Arch Linux, but other distros of GNU are also fine.
https://tatsumoto.neocities.org/blog/our-immersion-learning-toolset.html#gnulinux

It's not possible for me to switch to GNU/Linux right now, but certainly i'm doing so in the future. For now i have to live without this script since i tried every possible fix i could imagine. I think it's related to windows at this point.

Check if ffsubsync works properly by itself, e.g. when you run it from the terminal. And as I mentioned before, check your PATH.

Solved the problem. It was some weird issue with Windows not properly recognizing ffmpeg in the path.

What specifically helped solve this for you? I have the same issue on an M1 Mac (downgrading to Py9 didn't fix it, it just made the error so generic I don't know what's wrong lol) whereas my older Intel Mac works fine.


unlocked hashie version

Hashie is locked to an old version 3.x which conflicts with other gems using newer hashie versions. There is no reason to keep it locked to 3.x as it works just fine with newer versions as well.

Hello @feliksg, I am going to close this PR because I added your requested changes in PR #25 which was recently merged into the main branch.
We also were able to publish our first Gem of this Ruby SDK to rubygems.org, feel free to download it here and use it in your next project - ShipEngine Ruby SDK Gem 😎
Let us know if there is anything else you would like to see in our Ruby SDK.


Issues with proxies and enhanced classes in Spring context

We are using Mbassador extensively as the event bus in a Spring 4 environment with multiple application contexts etc.
I have run into some oddities when using the message bus with listeners that are either aop proxies or cglib enhanced:

handlers do not register (subscribe) because the proxy does not have the method annotations (probably in case of an AOP proxy, not cglib)
filters get a reference to a proxied or enhanced method and don't find the annotations on the originally declared method

The behavior i'm looking for a in Spring context would be:

when subscribing a listener, the target class (not the proxy) is used to determine the handlers
filters are run against with the target method metadata
execution is done on the outer proxied method

However, using this approach would (i think) remove the ability to do the reverse: using AOP to decorate regular methods with Handler annotations and subscribe them to the event bus.  I think the case for the latter is perhaps less common.
Anybody else has experience with this and built solutions around it?  Any thoughts on how and where this whould be fixed from a generic mbassador point of view?
I have to checkout mbassador-spring myself, will try to build some test cases we can build on to reproduce/resolve.

@bennidi I am interested in your hack to check for CGLIB. I wrote a simple BeanPostProcessor for auto registration but it doesn't seem to ever get passed the CGLIB enhanced class. Maybe this is a change in spring behavior? I'm using spring 5

The BeanPostProcessor I wrote was for Spring 3, I think. I assume that a lot of behaviour changed within the past releases (of Spring and CGLIB). I found my way to the right class with a break point in the main method of the BeanPostProcessor and inspected the instances which were handed to it. Took me a while because I did not create a sample app but used the complex production app. I suggest you make a minimal example and debug your way through then. Have fun! :)


How i can set value for paymentTextField?

Hi @orazz , how i can set text for this paymentTextField of great CreditCardForm-iOS ? Many thank for  support !

Did you try use demo app?

i had try both use demo, it only can get value of paymentTextField.cardnumber, i cant not set value for paymentTextField.cardnumber. @orazz  many thank for support sir.

Why do you want to set value to paymentTextField?

Becaue we need edit card information (Example: Exp of card), then user only need change number exp. Many thank for support @orazz .

I used stripe for payment and stripe aren't allowed to set cardnumber (paymentTextField), but you can save card details to charge it later.

I think the above functionality will be very useful while scanning credit card details and setting the same in textfield. What's your opinion regarding same?

@abhishekNebQuovantis it would be great!

any news about this feature ?

According to stripe documentation you can do it.
STPCardParams *cardParams = [[STPCardParams alloc] init];
cardParams.number = @"4242424242424242";
cardParams.expMonth = 10;
cardParams.expYear = 2018;
cardParams.cvc = @"123";

then apply this to your STPPaymentCardTextField.cardParams

Are you familiar with the concept PCI?


Code folding doesn't ignore comments

Issue Type: Bug
Code folding breaks on unindented comment.
unfolded

folded

Compiler tolerates it, so should IDE too.
Extension version: 2021.6.944021595
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.18363
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz (8 x 2304)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.81GB (5.55GB free)

Process Argv
--crash-reporter-id e4b48720-5a3d-4415-bc92-03f829fdb834

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspyt653:30270858
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
vscoreces:30322571
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30323308
vscorehov:30309549
vscod805cf:30301675
vscextlangct:30322307
binariesv615:30325510
vsccppwt:30329788

Not indenting comments to the same level as the code it applies to is not a common practice and is considered a quirk of Python's compiler that it's supported at all. Plus making this work would be a lot of work. So thanks for bringing this to our attention, but we are closing this as "won't fix".


Dataframe Algebra - how Pandas operations were written using algebra defined by Modin?

In Modin documentation, it says that Modin internal dataframe algebra has narrowed down 200+ Pandas operations to 15 operations. Few examples('pivot', 'agg' and reindex_like) were explained in the paper. Where can I find, how other Pandas operations were written using Modin dataframe algebra?

Hi @deHasara, thanks for posting!
I'm currently working on a paper that explains this for every operator. It is a lot of work as you can imagine! We don't have any current resources published on it yet. We started with the implementation as a concrete reference implementation, and are now going back and writing about it.

Closing this since the paper has been published now. @deHasara please check out: https://people.eecs.berkeley.edu/~totemtang/paper/Modin.pdf


Reset Button

Challenge http://freecodecamp.com/challenges/waypoint-target-elements-by-class-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.
I write the code and if I accidentally erased a line and I want to reset my code, I click on the "Reset" button and it asks if I would like to return my editor to its original state. When I do that nothing happens. The code remains the same and the challenge isn't restarted.

@irmattg thanks for posting this issue!
That button worked for me.
See my comment.

Please review the Guidelines for Contributing, thank you!.

Hello @irmattg,
Can you post screenshots?

Closing as stale, please reopen if the issue is not resolved (and post the screenshots).


fix: fixed a bug that caused onPageChange to return the previous page

Using the currentPageState immediately after using setcurrentPageState results in having the previous currentPageState used on getCurrentPage.  This is easily fixed by using result instead.
Also, you can fix it by using useEffect like this:
useEffect(() => {
    const pageList = getCurrentPage(list, itemsPerPage, currentPageState);
    onPageChange && onPageChange(pageList, currentPageState + 1);
}, [currentPageState]);

Hope this helps.

Thanks for the fix!


Broken links

There are lot of broken links on this page. It would be good to update the links.

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

ID: 5cbad219-645b-4478-e284-8136cb65f210
Version Independent ID: b8628dca-0242-92c3-5830-b0c965c89438
Content: Universal Serial Bus (USB) - Windows drivers
Content Source: windows-driver-docs-pr/usbcon/index.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @duncanmacmichael
Microsoft Alias: dumacmic

Hi @kenr, thanks for pointing this out. It looks like some of those links might have pointed to older pages that got swept up in a content migration we did, so I'll take a look at fixing them.

OK @kenr, I've fixed these links and they should be live in a few minutes. Thanks again for finding these!


Design

Hey @mzgnr!
What are your current thoughts on design? I have a small web development company in Denmark, and we have a great designer. If needed, we could provide a clean design for the website.

Hey @onbjerg ! I'm working on it in my free time. Its almost done. Thanks :smiley:


Document metadata.shareable type as boolean

Before this change metadata.shareable was wrongly documented as
string typed attribute.
This change fixes the documented type of the attribute.

@duglin not to drag this one further, please do it in a new PR.


boltdesignsystem.com components page looks weird after hitting back

I tested it on Ubuntu 18.04, Chromium, Chrome, Firefox
Steps to replicate:

Go to https://boltdesignsystem.com/pattern-lab/?p=components-overview
Click on any component (ie. Accordion)
Click the back button of the browser
Now you are going to see a very long page, scroll down a lot and you'll find somewhere in the middle the list of components

Thank you @shaal! We will take a look at this.

@shaal - we have create BDS-1520 in our internal JIRA to cover this issue. Thank you so much for the heads up!

@shaal FYI, #1255 (which just got merged down to master) has a few updates which should fix this UIKit bug!


Add Apple Vision Pro as a target for Flutter

Use case
The apple vision pro was released yesterday. It would be nice to have support for that. Even though most apps will be supported out of the box. This ticket can track the evolution of vision pro for Flutter
Proposal
This should just work out of the box.

At least some of this tvOS comment and this watchOS comment will almost certainly be applicable here. The extent to which visionOS differs from iOS remains to be seen as we learn more about the target and SDK.

I feel these is a great opportunity for Flutter here as iOS tooling is lacking and Vision OS is the perfect environment for a free rendering framework like Flutter. If Flutter doesn't compete, React Native will charge ahead. Vision OS won't be for everyone (at least at this stage), but it would be excellent for developers who will likely be early adopters of this technology. Getting the jump on this could be pivotal in Flutter growth.

As shown in the impeller demo, flutter could support 3D scenes within the widget tree, which is an amazing in the direction.  More work could definitely be put to improve Spatial UI elements such that in future - if not vision pro, but other AR devices could run Flutter app as a better option to already existing ones.

We can checkout the new visionOS SDK now. It has been release with Xcode 15 beta 2.

Great news! VisionOS is released along with Xcode 15 beta 2. Although, Flutter has yet to support VisionOS SDK, it seems to be working on visionOS via iOS (Design for iPad) target.
You can also do hot reload just like Design for iPad target using flutter attach. See #84411 .
For better DX, I also think we should properly support flutter run 'Design for iPad' as a target.

Managed to get the flutter demo to run natively (not as a iPad app) through a few little tweaks, convinces me that it would be possible and actually quite trivial to add VisionOS as a target, only mystery to me is how it would work with the eye gaze
Here is a video where I show it in action: https://twitter.com/MrMambwe/status/1671969959553933318

Since this is a broad umbrella request, I've filed some specific issues for targeted requests that would apply to iOS Flutter apps running on visionOS. I would encourage anyone interested in those issues to vote for them specifically so that we can gauge interest in specific items (which have much different scope from some of the comments above):

Support visionOS devices for iOS apps in flutter devices, flutter run, etc.
Support eye tracking when running on visionOS

I would love to see a demo with Impeller 3d models working on visionPro!

Managed to get the flutter demo to run natively (not as a iPad app) through a few little tweaks, convinces me that it would be possible and actually quite trivial to add VisionOS as a target, only mystery to me is how it would work with the eye gaze
Here is a video where I show it in action: https://twitter.com/MrMambwe/status/1671969959553933318

Very cool. Would love to see the code!

Managed to get the flutter demo to run natively (not as a iPad app) through a few little tweaks

@Mambsy Is this using a custom engine build? I wouldn't expect that running in native visionOS mode would be possible without one.

@Mambsy Is this using a custom engine build? I wouldn't expect that running in native visionOS mode would be possible without one.

@stuartmorgan  You can find what he did in this thread: https://twitter.com/MrMambwe/status/1672339427136249857

If that's a complete set of steps, then all that's actually demonstrating is that the visionOS simulator will, as has long been the case with the iOS simulator, run code that an actual device would not (because it's a simulator, not an emulator). It's not valid to draw any conclusions about actually supporting visionOS (e.g., that it's "actually quite trivial to add VisionOS as a target") from that.

Just watched the VisionOS section of the WWDC Keynote. This is a very exciting request for my use case! Subscribed.

Hi!
I think it is a great waste that Flutter is not compatible with Vision OS.
Because Flutter is a great framework for creating adaptive layouts.
Vision OS apps are basically 3D, but I think 2D screens will still be necessary.
Vision OS's 2D screen must be able to be resized vertically and horizontally, just like the macOS app screen.
This response is one of Flutter's strengths.
Also, although Vision OS can run iOS and iPadOS apps,
The drawback is that the aspect ratio is fixed.
I believe that Flutter has clear strengths over Vision OS as a framework that allows you to create applications that can freely change the aspect ratio.
So, why not start by just supporting the creation of 2D applications for Vision OS?
I think the following is necessary to support Vision OS.

Adding support for Vision OS in of Embedder

https://github.com/flutter/engine/tree/main/shell/platform/darwin
To check the difference from iOS, implement them.

fix Flutter Tools
for commands (example: flutter run )
enable debugging
test and CI

Depending on the eye tracking specifications, it may be necessary to support input in the widget on the Engine and Flutter sides.
Let me say it again: It is a great waste that Flutter is not compatible with Vision OS.
Why not start by investigating what to do and where the problem is?

Hi! I think it is a great waste that Flutter is not compatible with Vision OS.
Because Flutter is a great framework for creating adaptive layouts. Vision OS apps are basically 3D, but I think 2D screens will still be necessary. Vision OS's 2D screen must be able to be resized vertically and horizontally, just like the macOS app screen. This response is one of Flutter's strengths. Also, although Vision OS can run iOS and iPadOS apps, The drawback is that the aspect ratio is fixed.
I believe that Flutter has clear strengths over Vision OS as a framework that allows you to create applications that can freely change the aspect ratio. So, why not start by just supporting the creation of 2D applications for Vision OS?
I think the following is necessary to support Vision OS.

Adding support for Vision OS in of Embedder

https://github.com/flutter/engine/tree/main/shell/platform/darwin
To check the difference from iOS, implement them.

fix Flutter Tools

for commands (example: flutter run )

enable debugging

test and CI

Depending on the eye tracking specifications, it may be necessary to support input in the widget on the Engine and Flutter sides.
Let me say it again: It is a great waste that Flutter is not compatible with Vision OS. Why not start by investigating what to do and where the problem is?

Great thoughts. You're right that starting with something smaller is important. Exploring the issue and implementing the best aspects of Flutter in the context of Vision OS is crucial. However, I want to point out that Flutter is becoming 3D (thanks to Impeller), which is a significant step in expanding Flutter's capabilities. I'm specifically referring to Flutter in the context of Gamedev, AR, VR, and so on. Limiting Flutter to just 2D applications wouldn't be accurate because its architecture allows for much more, which is great. As we know, Flutter is actively moving towards Impeller, which enables exploration and implementation 3D apps too. However, considering that AR applications take external surroundings into account for further rendering, I believe it's important to also look towards another library, namely Filament. It's also from Google and allows for real-time physical rendering on Android, iOS, Linux, macOS, Windows, and WebGL. If we can build a strong infrastructure from this, Flutter could become a powerful tool in a new dimension, like GameDev, AR, VR.

So, why not start by just supporting the creation of 2D applications for Vision OS?
I think the following is necessary to support Vision OS.

Adding support for Vision OS in of Embedder

https://github.com/flutter/engine/tree/main/shell/platform/darwin
To check the difference from iOS, implement them.

fix Flutter Tools

for commands (example: flutter run )

enable debugging

test and CI

That is what this issue tracks. Please see my initial comment in this issue for links to discussions of the "why not".

@4e6anenk0
Thank you for your reply. I think Flutter's 3D support is  amazing.
I also understand that it has a large impact.
However, I feel like it would be a waste to just wait for 3D support.
I think a good development process would be to first sort out what needs to be implemented in detail,
start implementing parts that are not related to 3D, and then incorporate 3D support.
https://github.com/flutter/flutter/issues/58145 is the issue of 3D support?
This discussion seems to have stopped as well.
In order to fully support Vision OS, we need to move forward with this discussion.

@stuartmorgan
Thank you for your reply.
Of course I read your comments.
However, I thought that comment was because it was difficult, not because it was technically impossible.
If we don't stop the discussion and move forward with development because it's difficult or it will take a long time,
this issue will never be resolved.
Currently, I think there are issues that are time-consuming and difficult,
but there are no stated issues that are technically impossible.
Can you tell us if there are any such issues?

If we don't stop the discussion and move forward with development because it's difficult or it will take a long time,
this issue will never be resolved.

There are no current plans to resolve this issue, because of the permanent long-term costs mentioned in my earlier comment and discussed in more detail in the comments it links to. That may change in the future, but for now not moving forward with developing visionOS support is a deliberate decision.
As with tvOS and watchOS, interested parties could certainly maintain a fork of the engine with such support, and we would be happy to review any PRs upstreaming generally applicable changes from such a fork (e.g., minimizing UIScreen usage).

@stuartmorgan
Thank you for your reply.
I understood why not moving forward with developing visionOS support.
However, I believe that Spatial computing systems like Vision OS will have a place in the future.
I believe that Flutter's Vision OS support will definitely be necessary.
So I'm going to personally proceed with development for that time.
Of course, I will submit pull requests for features that can be added to the current Flutter version.
I would like you to continue to pay attention to the demand for Vision OS so that you do not miss the opportunity to decide to develop it.

At least some of this tvOS comment and this watchOS comment will almost certainly be applicable here. The extent to which visionOS differs from iOS remains to be seen as we learn more about the target and SDK.
[Update Oct 2023]: Some specific differences at the engine level:

All uses of UIScreen would need to be conditionalized. In many cases we probably want to move away from UIScreen anyway (e.g., Audit use of UIScreen scale #134062), and this is an area where someone motivated to maintain a custom engine build could upstream some PRs, but other would need different codepaths.
A new OS type needs to be plumbed into the build, including dependencies like Dart and Skia. Parts of Skia would need conditional compilation (e.g., MTKView).
Various specific areas of code would need to be conditionalized (keyboard handling, status bar handling)

Based on the initial investigation, it is the case that most of the work would be in the long term support, as discussed in the linked issues above.

Hello @stuartmorgan,
How much work would that require? It seems the react native already have those changes made: https://github.com/callstack/react-native-visionos
I wonder if it is too complicated to make those changes in flutter.

Adjusting just the code that lives in flutter/engine to get that layer compiling is not especially complicated, but it's possible there's more to do at that layer Getting skia and/or impeller working is an unknown amount of work, especially given that Metal support is an area when visionOS diverges from iOS.
In general with porting complex codebases, the only way to actually know how much work is involved is to actually do it, because not all work is obvious until well into the process.

@stuartmorgan Thank you for your reply.
I understood why not moving forward with developing visionOS support. However, I believe that Spatial computing systems like Vision OS will have a place in the future. I believe that Flutter's Vision OS support will definitely be necessary.
So I'm going to personally proceed with development for that time. Of course, I will submit pull requests for features that can be added to the current Flutter version.
I would like you to continue to pay attention to the demand for Vision OS so that you do not miss the opportunity to decide to develop it.

Hey @Umigishi-Aoi, I saw that you tried to make the flutter compatible with the visionOS, do you wanna share what did you manage to do so far?

If anyone is interested in trying to build a fork that supports visionOS, some potentially useful (but very rough, and surely already somewhat bitrotted, so primary just a reference) bits from my earlier experimentation:

gn changes to the engine build:

buildroot.A lot of these changes won't be necessary if/when upstream clang supports visionOS (which wasn't the case at the time I did the initial experiment, but may already be true).
flutter/engine

Dart's runtime/BUILD.gn will also need changes to include handling visionos as a target_os. For initial hack purposes I opted it into the same codepaths as ios in any target_os branching (only a few lines needed changing at the time), which may or may not be good enough.
Some plugin APIs must be marked as unavailable.

That's most of what's needed to get to the point where it tries to compile, at which point:

All uses of mainScreen need revisiting; that could mostly be done upstream per https://github.com/flutter/flutter/issues/134062
Skia and/or impeller would need significant investigation.

If anyone is interested in trying to build a fork that supports visionOS, some potentially useful (but very rough, and surely already somewhat bitrotted, so primary just a reference) bits from my earlier experimentation with an engine build:

gn changes to the engine build:

buildroot.A lot of these changes won't be necessary if/when upstream clang supports visionOS (which wasn't the case at the time I did the initial experiment, but may already be true).
flutter/engine

Dart's runtime/BUILD.gn will also need changes to include handling visionos as a target_os. For initial hack purposes I opted it into the same codepaths as ios in any target_os branching (only a few lines needed changing at the time), which may or may not be good enough.

Some plugin APIs must be marked as unavailable.

That's most of what's needed to get to the point where it tries to compile (at least for simulator, using ./tools/gn --visionos --unoptimized --simulator --simulator-cpu=arm64 to configure the build and then adding use_xcode = true to the resulting build dir's arg.gn if using Xcode's clang is still required), at which point:

All uses of mainScreen need revisiting; that could mostly be done upstream per Audit use of UIScreen scale #134062
Keyboard code needs to be updated for visionOS (or temporarily stubbed out).
Skia and/or impeller would need significant investigation.

Using the resulting engine build easily would require a bunch of work in the flutter tool. It's possible to manually insert it into Flutter.xframework though:

In flutter/bin/cache/artifacts/engine/ios/Flutter.xcframework/, create a new folder called xros-arm64_x86_64-simulator.
Update the Info.plist's AvailableLibraries to reflect the new folder.
Copy Flutter.framework from visionos_debug_sim_unopt_arm64 into the newly created xros-arm64_x86_64-simulator folder.

Thank you Stuart for the work done.
It seems clang already supports visionOS : https://github.com/llvm/llvm-project/issues/77674
So the changes in https://github.com/flutter/buildroot/commit/256b943af3be9755093512fd44a45a389292de5b#diff-3bc9360582491eaa46bb0248ba4e06ad224b22bbeb8dad1dd37b0d0ca19adc54 doesn't look necessary anymore.

@guilherme-francisco Thank you for your reply.

Hey @Umigishi-Aoi, I saw that you tried to make the flutter compatible with the visionOS, do you wanna share what did you manage to do so far?

Sorry, my progress is very little and I'm not ready to share it yet.
I will contact you here when we are able to share it.


Fixing broken nested tab structure.

This page has a nested tab structure that doesn't work. I've removed the page-wide tab and replaced that information with a note. Perhaps not the best way, but it allows the other information to display properly.
See what happens when you click the Operator tab at Using host-local IPAM
Preview: https://deploy-preview-6576--calico-master.netlify.app/reference/cni-plugin/configuration

@caseydavenport Does this work for you?

bump @caseydavenport


Enforce capitalization of Compliant Kubernetes

⚠ IMPORTANT ⚠: This is a public repository. Make sure to not disclose:

[x] personal data beyond what is necessary for interacting with this Pull Request;
[x] business confidential information, such as customer names.

Can I ask you to kill any variation of ck8s as well? We moved away from that, and it would be lovely if a hook complained.

Smart! Added, PTAL.


Make a mode flag that follows the parent

so right now i can only specify if the mode should be debug or release. but there should be a mode that follows what the parent project is.
clib = { dir = "../../clib", type="pybuildc", mode="parent" }

Made the needed adjustment in the clib library

wait it actually can be usefull for testing libraries like in claymore and sandbox


Bottom Overflow in Inbox Messages[GSSoC'23]

When we open the Messages tab their is bottom overflow by 1.7 pixels. The code is not responsive
Under GSSoC'23

please assign me this issue under GSSOC'23

@AnubhaSharma2709 assigning you

Thankyou so much ! Working on the same


FileNotFoundError: [Errno 2] No such file or directory (mri_robust_register command)

What happened?
When I ran 'mri_robust_register', there is an error:
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/work/fmriprep_23_0_wf/single_subject_994509xxx_wf/anat_preproc_wf/surface_recon_wf/fsnative2t1w_xfm/T1_robustreg.lta'
Do you have any suggestions?

What command did you use?
fmriprep-docker
RUNNING: run --rm -e DOCKER_VERSION_8395080871=20.10.23 -it -v /media/xxxx-data/Localizer_BIDS/code/license.txt:/opt/freesurfer/license.txt:ro -v /media/xxxx-data/BIDS/data_rs/rs:/data:ro -v /media/xxx-data/BIDS/data_rs/derivatives:/out nipreps/fmriprep:23.0.0 /data /out participant --participant-label 994509xxx --skip-bids-validation --md-only-boilerplate

What version of fMRIPrep are you running?
23.0.0
How are you running fMRIPrep?
Docker
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
Traceback (most recent call last):
  File "/opt/conda/lib/python3.9/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
    result["result"] = node.run(updatehash=updatehash)
  File "/opt/conda/lib/python3.9/site-packages/nipype/pipeline/engine/nodes.py", line 527, in run
    result = self._run_interface(execute=True)
  File "/opt/conda/lib/python3.9/site-packages/nipype/pipeline/engine/nodes.py", line 645, in _run_interface
    return self._run_command(execute)
  File "/opt/conda/lib/python3.9/site-packages/nipype/pipeline/engine/nodes.py", line 771, in _run_command
    raise NodeExecutionError(msg)
nipype.pipeline.engine.nodes.NodeExecutionError: Exception raised while executing Node fsnative2t1w_xfm.

Cmdline:
        mri_robust_register --satit --iscale --lta /tmp/work/fmriprep_23_0_wf/single_subject_994509xxx_wf/anat_preproc_wf/surface_recon_wf/fsnative2t1w_xfm/T1_robustreg.lta --mov /out/sourcedata/freesurfer/sub-994509xxx/mri/T1.mgz --dst /data/sub-994509xxx/ses-01/anat/sub-994509xxx_ses-01_T1w.nii
Stdout:
        7.3.2

        --satit: Will iterate with different SAT to ensure outliers below wlimit!
        --iscale: Enabling intensity scaling!
        --lta: Output transform as /tmp/work/fmriprep_23_0_wf/single_subject_994509xxx_wf/anat_preproc_wf/surface_recon_wf/fsnative2t1w_xfm/T1_robustreg.lta .
        --mov: Using /out/sourcedata/freesurfer/sub-994509xxx/mri/T1.mgz as movable/source volume.
        --dst: Using /data/sub-994509862/ses-01/anat/sub-994509xxx_ses-01_T1w.nii as target volume.

        reading source '/out/sourcedata/freesurfer/sub-994509xxx/mri/T1.mgz'...
        reading target '/data/sub-994509862/ses-01/anat/sub-994509xxx_ses-01_T1w.nii'...
        INFO: This is an unsigined short.

        Registration::setSourceAndTarget(MRI s, MRI t, keeptype = TRUE )
           Type Source : 0  Type Target : 10  ensure both FLOAT (3)
           Reordering axes in mov to better fit dst... ( -1 -3 2 )
         Determinant after swap : 1
           Mov: (0.7, 0.7, 0.7)mm  and dim (320, 320, 320)
           Dst: (0.7, 0.7, 0.7)mm  and dim (290, 320, 256)
           Asserting both images: 0.7mm isotropic
            - reslicing Mov ...
               -- changing data type from 0 to 3 (noscale = 0)...
            - reslicing Dst ...
               -- changing data type from 10 to 3 (noscale = 0)...
        MRIchangeType: Building histogram 0 24198 1000, flo=0, fhi=0.999, dest_type=3
               -- Original : (0.7, 0.7, 0.7)mm and (290, 320, 256) voxels.
               -- Resampled: (0.7, 0.7, 0.7)mm and (320, 320, 320) voxels.
               -- Reslicing using cubic bspline
        MRItoBSpline degree 3

         Registration::findSaturation
           - computing centroids
Stderr:
        makeIsotropic WARNING: not different enough, won't reslice!
        CostFunctions::centroid is NAN (empty image? n = 0 )
Traceback:
        Traceback (most recent call last):
          File "/opt/conda/lib/python3.9/site-packages/nipype/interfaces/base/core.py", line 399, in run
            runtime = self._post_run_hook(runtime)
          File "/opt/conda/lib/python3.9/site-packages/niworkflows/interfaces/freesurfer.py", line 248, in _post_run_hook
            fix_lta_length(lta_file)
          File "/opt/conda/lib/python3.9/site-packages/niworkflows/interfaces/freesurfer.py", line 399, in fix_lta_length
            lines = Path(lta_file).read_text().splitlines(keepends=True)
          File "/opt/conda/lib/python3.9/pathlib.py", line 1266, in read_text
            with self.open(mode='r', encoding=encoding, errors=errors) as f:
          File "/opt/conda/lib/python3.9/pathlib.py", line 1252, in open
            return io.open(self, mode, buffering, encoding, errors, newline,
          File "/opt/conda/lib/python3.9/pathlib.py", line 1120, in _opener
            return self._accessor.open(self, flags, mode)
        FileNotFoundError: [Errno 2] No such file or directory: '/tmp/work/fmriprep_23_0_wf/single_subject_994509862_wf/anat_preproc_wf/surface_recon_wf/fsnative2t1w_xfm/T1_robustreg.lta'

Additional information / screenshots
No response

I'm sorry, I missed this.
        CostFunctions::centroid is NAN (empty image? n = 0 ) would indicate that there's some issue with the input images.
Looking at mri_robust_register --satit --iscale --lta /tmp/work/fmriprep_23_0_wf/single_subject_994509xxx_wf/anat_preproc_wf/surface_recon_wf/fsnative2t1w_xfm/T1_robustreg.lta --mov /out/sourcedata/freesurfer/sub-994509xxx/mri/T1.mgz --dst /data/sub-994509xxx/ses-01/anat/sub-994509xxx_ses-01_T1w.nii. I would check what /out/sourcedata/freesurfer/sub-994509xxx/mri/T1.mgz and /data/sub-994509xxx/ses-01/anat/sub-994509xxx_ses-01_T1w.nii look like, and see if you can run mri_robust_register outside of fMRIPrep.
Please retry with 23.2.0a1, and if this is still an issue, reopen.


fix(form-field-benchmark): fix component comment so that form field can sync properly

@wagnermaciel I'm assuming that patch is the correct target here, but feel free to change it if it's not.


no-unused-prop-types false positive in functions that can return JSX in stateless components

eslint version 3.19.0
eslint-plugin-react version 7.1.0
This minimal example causes eslint to incorrectly flag props.append as never used:
import React from 'react';
import PropTypes from 'prop-types';

export default function SampleComp(props) {
  function buildText(text) {
    return (

        {text}
        {props.append}

    );
  }

  return (

      {buildText(props.text)}

  );
}

SampleComp.propTypes = {
  text: PropTypes.string,
  append: PropTypes.string
};

I've noticed that the following things don't trigger the false positive:

Calling buildText with a literal, e.g. buildText('hello')
Calling buildText with a variable that doesn't ultimately come from props: const hello = 'hello'; buildText(hello);
Assigning props.append to a variable outside of buildText, and using that variable instead inside the function body: const {append} = props; function buildText(text) { /* use append here instead of props.append */ }; buildText(props.text);
Refactoring buildText to take and use the whole props object, and adjusting the call accordingly
Refactoring buildText to not take any arguments and use the props directly inside the function body

In this case, even if you don't use any of the props at all, eslint doesn't complain... a bug in the other direction?

Refactoring buildText to take multiple arguments and passing all prop to it accordingly: function buildText(text, append) { /* ... */ }; buildText(props.text, props.append);
And obviously, returning something other than JSX from buildText

The following things don't affect the outcome at all:

Assigning props.append to a variable inside buildText doesn't get rid of the eslint warning
Using the prop in a flow control statement (if, switch, etc), even if reassigned as above

Not even if the statement that returns JSX is completely unreachable, e.g. if (false) return (
bla
)

This might be similar to #885 but I figured it was different enough to warrant its own issue, especially because of the JSX thing.

@jaromero  thanks for reporting this issue and documenting all the options you tried.
The issue here is that for all practical purposes  buildText function looks like a valid react component since it is a function and return JSX.
Also this react component is defined inside another react component SampleComp. So the append props is only considered to be used inside inner react component.
To account for this case we could have considered any component declared inside another component to be a helper method.
Although this would break few tests from a different rule (prop-types that actually is no-undefined-props) that allows for nested components definitions as a valid test case.
class DynamicHello extends Component {
  render() {
    const {firstname} = this.props;
    class Hello extends Component {
      render() {
        const {name} = this.props;
        return
Hello {name}
;
      }
    }
    Hello.propTypes = {
      name: PropTypes.string
    };
    return <Hello />;
  }
}
DynamicHello.propTypes = {
  firstname: PropTypes.string,
};

So the question to maintainers @ljharb, @jseminck  whether we want to add the reported use case to the list of known issues/limitations for this rule suggesting few work arounds, or reconsider nested components tests like one above from prop-types rule.
I created a PR to illustrate the issue.

buildText is conceptually an SFC, and should actually be one - not a function.

@ljharb , this sounds good to me. I will create a PR to update docs for this rule adding known issues/limitations section. What SFC stands for?

Thanks! "stateless functional component".
Closing as "works as intended".


Settings Improvements

[x] Make accent color work instantly in Main theme
[x] History settings, make 2 sections
[x] Comments depth colors "space" hex is randomized (UIColor issue possibly @colejd ? Wasn't happening before the PR)
[x] Select all in Subreddit themes
[x] Color background of Subreddit themes and Manage subreddits
[x] Subscribe when adding to Manage subs screen
[x] Send message to Slide bot when user goes pro if they want to set their flair

That shouldn't be the case unless you're calling the weird code I wrote. Otherwise it's something else.

We can leave the slide pro thing for later ;)