Setting resolver during tests

One pain point we've found while working with in-repo-engines is that integration/unit tests can be frustrating to get working properly. A large part of this is due to the resolver used by tests being set once globally and usually only reflects the resolver used by the host application and not the engine itself.
Since there are obviously scenarios where we would want to integration/unit test a component (or something else) within an in-repo-engine, it might make sense to build in a way to easily set the Engine associated with a specific test module. Something like:
import { test, moduleForComponent } from 'ember-qunit';

moduleForComponent('x-foo', {
  integration: true,
  engine: 'my-engine'
});

Which will grab the resolver and modulePrefix after looking up the Engine and use those for the resolver for the current test module.
Note: I believe we could work in support for this from this addon, but it would likely be better situated somewhere in ember-test-helpers.

Has there been any progress on this? We'd love to use integration tests for our in-repo engine's components.

This is now possible by setting a custom resolver per-module in<EMAIL_ADDRESS>


Fix/ie11

Hey @jhuesos !
We have fixed several IE11 visual issues in Polymer 1 and Polymer 2. We have also made some regression tests for others browsers: Chrome, Mozilla and Safari and everything looks great too :)

Waiting for your feedback to merge
Thank you!

Hey, many thanks!!! I will try to take a look during this weekend.

Btw, do you know if this issue:
https://github.com/ellipticaljs/paper-autocomplete/issues/70
is solved?

@ajbarriosleon sorry I forgot to push a change the other day, can you resolve the conflict? Thanks

Hey @jhuesos !
I have pushed some changes:

I removed the Array.find polyfill and I replaced the code with Array.filter. I agree with you, it is not really useful, fewer polyfills is better :)
I resolved the merge conflict and tested it without any issue.

About the #70 I can't reproduce it in this branch. In my opinion, if you agree, you could merge it and keep the tracking of all old/new issues since this moment.
Thank you!

Yeah, let's do that. this week I am extremely busy, so let's merge and I will try to do the testing there. Thanks again


Fix header dependency issues when building with GCC 13

Fixes building the ggcat C++ API with GCC 13 which currently fails because of a missing #include <cstdint> in ggcat.hh (see "Header dependency" in https://gcc.gnu.org/gcc-13/porting_to.html for the why).

Thanks for the fix, I will merge it


Not working in Production/AWS EKS

Hi Team,
I am able to ship logs to logzio from my local system. When i deploy the same code to AWS EKS, the logs are not shipping to logzio, any idea?

Have you checked if machine has access to internet?
Does it have access to logz.io data center?
Does it have access to logz.io data center ports?

Closing this as not enough information.

Closing as not enough information.


Adds support for JSON merge-patch

DO NOT MERGE
addresses #1404

This change is

The original issue was in Express and not superagent, closing


process monitor crashes

Simplify locks with @synchronized
Use a threadsafe dict for data as well as cache

This is intended to fix https://github.com/quicksilver/Quicksilver/issues/3008

Hey Nate 👋 :-)
Does this actually fix the problem? Have you been running with this and do you still experience crashes? If not - then it looks good to me. My only concern is: does it cause any locks anywhere else in the code?

Hi Pat!

Does this actually fix the problem?

No, unfortunately. I think I have mostly / partially reverted it in my local branch, will convert this to a draft to reduce confusion.
I've finally discovered xcode's thread sanitizer, which I think will be helpful in pinpointing areas of concern, but I've also been busy with a move and an upcoming board exam, so it's been slow going.
It also seem that thread sanitizer may have some false positives, as I've spent way too much time trying to hunt down the reported race condition at https://github.com/quicksilver/Quicksilver/blob/f4f679f3a9a0dc377214e150761ff633a9807a13/Quicksilver/Code-QuickStepCore/QSLibrarian.m#L362, but all I've figured out is that it goes away when I remove NSEnumerationConcurrent (and returns afterward). Either that or it's somewhere in https://github.com/quicksilver/Quicksilver/blob/f4f679f3a9a0dc377214e150761ff633a9807a13/Quicksilver/Code-QuickStepCore/QSCatalogEntry.m#L734 -- I think..

Hey hey!
Darn, that's a shame it doesn't work. Although I didn't think this would work - we used thread safe dicts in the past for QSProcessMonitor, but I actually took them out as they weren't helping :(
Good to hear you've got the thread sanitizer working! I wonder if ChatGPT can analyze and fix the code for us...? ;-)

I wonder if ChatGPT can analyze and fix the code for us...?

I've tried! Unfortunately doesn't seem to know ObjC very well either. I tried (repeatedly) to get it to recreate a toy program that would crash with EXC_BAD_ACCESS due to a race condition, but the programs it generated all ran without errors or crashing.

@pjrobertson actually, I take it back -- this seems to mitigate the issue at least somewhat. Without this I'm getting crashes within an hour or two, with this it's been running for 2 days without a crash. Let's merge this for now and see if it at least mitigates the issue.


copy filepath in 'text' property via one click

Line based detection will be enough.
Consider security concerns.

Done by b275f113c92f93506c636890a442c609249a96df


Warning: Failed context type

If I'm not at the right place for this issue, I apologize. Not sure where to get started to solve this error message.
Problem description

a nextjs app which was made from with-material-ui-next, you can find the app having the issue here next-library-starter
a npm package called next-library which depends on material-ui and is a dependency of next-library-starter (see The Goal below)
everything works great, except I'm receiving an error message for each material-ui component.

Error messages
Warning: Failed context type: Invalid context 64a55d578f856d258dc345b094a2a2b3 of type Jss supplied to withStyles(ButtonBase), expected instance of Jss.
Warning: Failed context type: Invalid context d4bd0baacbc52bbd48bbb9eb24344ecd of type SheetsRegistry supplied to withStyles(TouchRipple), expected instance of SheetsRegistry.
The goal
The goal is to have that npm library with material-ui in order to quickly get started with new projects. This stuff is slightly beyond my understanding of npm packages & webpack and I might not be doing it the right way, if so, please kindly advise.
Steps to reproduce
git clone https://github.com/astenmies/next-library-starter.git && cd next-library-starter && yarn && yarn run dev

Versions

Material-UI: next
React: 15.6.1
Browser: Chrome

We have been taking ownership on the next.js example. You can find a working example on our repository.

Can you confirm this one is working?

Thanks for your prompt reply @oliviertassinari .
Your nextjs example works without errors. When I use the same content in my npm package with webpack, I'm still getting the error though.
Any idea where I can get more advises on how to solve this if not here? I've been stuck for weeks with this error.

This sounds like a duplication of jss or react-jss version.

Removing react-jss from my npm package did not solve the issue. Where could the duplication be?

Problem description
@oliviertassinari

In Solution2 the error is gone but styles are not rendered until the page finishes loading (more slowly).
Solution 1 has no delay but gets the error message.
withRoot from your example gives me a "cannot read property index of undefined" thrown from withStyles.

Solution 1 - No delay but error message:
import React, { Component } from 'react'
import { JssProvider } from 'react-jss'
import { withStyles, createStyleSheet, MuiThemeProvider } from 'material-ui/styles'
import { getContext } from '../../index';

// Apply some reset
const styleSheet = createStyleSheet(theme => ({
  '@global': {
    html: {
      background: theme.palette.background.default,
      WebkitFontSmoothing: 'antialiased', // Antialiasing.
      MozOsxFontSmoothing: 'grayscale' // Antialiasing.
    },
    body: {
      margin: 0
    }
  }
}))

let AppWrapper = props => props.children
AppWrapper = withStyles(styleSheet)(AppWrapper)

  class AppMui extends Component {

    componentDidMount () {
      // Remove the server-side injected CSS.
      if(process.browser) {
        const jssStyles = document.querySelector('#jss-server-side');
        if (jssStyles && jssStyles.parentNode) {
          jssStyles.parentNode.removeChild(jssStyles)
        }
      }
    }

    render () {
      const context = getContext();
      return (
        <JssProvider registry={context.sheetsRegistry} jss={context.jss}>
          <MuiThemeProvider theme={context.theme} sheetsManager={context.sheetsManager}>
            <AppWrapper>
              {this.props.children}
            </AppWrapper>
          </MuiThemeProvider>
        </JssProvider>
      )
    }
  }

export default AppMui

Solution 2- No error message but delay
import React, { Component } from 'react'
import { JssProvider } from 'react-jss'
import { withStyles, createStyleSheet, MuiThemeProvider } from 'material-ui/styles'
import { getContext, setContext } from '../../index';

// Apply some reset
const styleSheet = createStyleSheet(theme => ({
  '@global': {
    html: {
      background: theme.palette.background.default,
      WebkitFontSmoothing: 'antialiased', // Antialiasing.
      MozOsxFontSmoothing: 'grayscale' // Antialiasing.
    },
    body: {
      margin: 0
    }
  }
}))

let AppWrapper = props => props.children
AppWrapper = withStyles(styleSheet)(AppWrapper)

var withRoot = ComposedComponent => class AppMui extends Component {
    static getInitialProps(ctx) {
      // Reset the context for handling a new request.
      setContext();

      if (ComposedComponent.getInitialProps) {
        return ComposedComponent.getInitialProps(ctx);
      }

      return {};
    }

    componentDidMount () {
      // Remove the server-side injected CSS.
      if(process.browser) {
        const jssStyles = document.querySelector('#jss-server-side');

        if (jssStyles && jssStyles.parentNode) {
          jssStyles.parentNode.removeChild(jssStyles)
        }
      }
    }

    render () {
      const context = getContext();
      if (process.browser) {
        return (
          <MuiThemeProvider theme={context.theme}>
            <AppWrapper>
              <ComposedComponent {...this.props} />
            </AppWrapper>
          </MuiThemeProvider>
        );
      }
      return (
        <JssProvider registry={context.sheetsRegistry} jss={context.jss}>
          <MuiThemeProvider theme={context.theme} sheetsManager={context.sheetsManager}>
            <AppWrapper>
              <ComposedComponent {...this.props} />
            </AppWrapper>
          </MuiThemeProvider>
        </JssProvider>
      )
    }
  }

export default withRoot

I'm having a look at your reproduction example now.

Ok, the warnings are coming from a duplicated jss version. It's installed once in the node_modules and bundled once in next-library.

Material-UI source code is relying on this contextTypes of react-jss. We could soften the checks but you would have missed thing important jss duplication error. So for now, let's keep it this way.

Awesome @oliviertassinari many thanks for your help. You work's impressive man, keep it up! Cheers 🍻

First, this project is incredible so thank you for what you're doing here.
This issue is still happening in the create-react-app example, and I'm not sure from reading this what the steps are to fix it, or if it matters at all. Is the guidance here that the PropType checks are being overly aggressive and that it's not an issue?

I'm using server-side-rendering and still getting this warnings :/
we have our materialui-components in other repo and we use that like external library

@GiancarlosIO It could be linked to mismatching version of jss installed.

Yes!, I was using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>so installed the same versions used in material-ui

@kof I don't think that the instanceOf is needed here https://github.com/cssinjs/react-jss/blob/master/src/contextTypes.js#L6. One could have a react-jss version relying on jss@8 and a material-ui version relying on jss@9. Given that the jss instance is injected by users, it doesn't matter what version of jss was installed on the react-jss lib. What matter is the scope of the jss version supported. What do you think?

I can relax it to PropType.object


typo "In order the change the app in the container""

"In order the change the app in the container"
should say "In order to change"

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

ID: cc19d2e0-5960-c165-083c-a9dcf9976c91
Version Independent ID: 58d32965-6909-2461-5158-aa66d904bf3c
Content: Docker containers - LUIS - Azure Cognitive Services
Content Source: articles/cognitive-services/LUIS/luis-container-howto.md
Service: cognitive-services
Sub-service: language-understanding
GitHub Login: @aahill
Microsoft Alias: aahi

@dargilco Thanks for the feedback. We will update you shortly.

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


Can anyone make a google colab notebook. Or does any colab notebook exist already for yt-dlp, to download directly to google drive?

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.07.18 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
There is one for ytdl but ytdl is slow compared to ytdlp
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

There isn't any that is officially maintained. As for whether anyone else has made one, I have no clue.
This is an issue tracker, not a forum. These kinds of questions should go on reddit or another community forum


question about generating lidar image

Hello,
I would like to ask, in the function _fill_trainval_infos(), when you generate the lidar image, I found out that you give these two parameters:
lidar_scale_factor=100 and shift=200
Also, the background of the lidar image is 20000. Are there any reasons for using these huge numbers stored in the image?
I am sorry I am not so familiar with Lidar, so I would like to ask how you came up with these scale and shift things.
Thanks a lot for your answer!

Hello,
This is done to store the projections as uint16 PNG images as they can then be easily handled when loading similarly to the camera inputs.
These factors are used in order to save the projections as PNG files with uint16 in each pixel. Since this format does not allow negative values we shifted every value by 200 (shift) and multiply them by 100 (lidar_scale_factor) in order to keep a high accuracy in the measurements.
These values worked well for us, but you could set other values as these are stored in the dict info['lidar_img'], automatically loaded and reverted here. So we have our normal image with the background set to 0 after loading the image with LoadProjectedSensorImageFile.
Hope this helps.

Hello,
This is done to store the projections as uint16 PNG images as they can then be easily handled when loading similarly to the camera inputs.
These factors are used in order to save the projections as PNG files with uint16 in each pixel. Since this format does not allow negative values we shifted every value by 200 (shift) and multiply them by 100 (lidar_scale_factor) in order to keep a high accuracy in the measurements.
These values worked well for us, but you could set other values as these are stored in the dict info['lidar_img'], automatically loaded and reverted here. So we have our normal image with the background set to 0 after loading the image with LoadProjectedSensorImageFile.
Hope this helps.

Thanks a lot for your quick reply.
This helps a lot! I will go through it in more detail.


Internal error: TypeError: this.config.email is not a function

Link to reproduction
No response
Payload Version
3.0.0-beta.68
Node Version
v20.15.1
Next.js Version
14.2.5
Describe the Bug
I've update from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>(cannot test those in between, cause https://github.com/payloadcms/payload/pull/7235).
Internal error: TypeError: this.config.email is not a function
    at BasePayload.init (./node_modules/.pnpm/payload@3.0.0-beta.68_@swc+core@1.7.0_@swc+helpers@0.5.5__@swc+types@0.1.12_graphql@16.9.0_typescript@5.5.3/node_modules/payload/dist/index.js:568:38)

Reproduction Steps
I use the following in my config:
import { nodemailerAdapter } from '@payloadcms/email-nodemailer';

...

 email: nodemailerAdapter({
    defaultFromAddress: process.env.MAIL_FROM_NAME_ADDRESS as string,
    defaultFromName: process.env.MAIL_FROM_NAME as string,
    transportOptions: {
      host: process.env.SMTP_HOST,
      port: process.env.SMTP_PORT ? parseInt(process.env.SMTP_PORT) : undefined,
      secure: process.env.SMTP_SECURE === 'true',
      auth: {
        user: process.env.SMTP_USERNAME,
        pass: process.env.SMTP_PASSWORD,
      },
    },
  }),

Adapters and Plugins
@payloadcms/email-nodemailer

This will be fixed in the next beta release https://github.com/payloadcms/payload/pull/7326


ConfigAwsConnector.ps1 throws errors and then quits after 3 retries. See #8293

Describe the bug

Note: this was never fixed in #8293 so I'm opening a new ticket.
Although I didn't see you asked for logs, another person provided logs and he was ignored.
Reproducing this error should be easy, the scripts are entirely broken.
I've provided my log output in the comment below.

A clear and concise description of what the bug is.
Location of script(s):
https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors/AWS-S3
When running this script from powershell (on Windows 11, fully patched), the following errors are consistently seen, before the script quits:
.\ConfigAwsConnector.ps1
Starting ConfigAwsConnector at: 06/16/2023 21:13:33
Log created: C:\users\bob\aws\Logs\AwsS3-06162113.csv
To begin you will choose the AWS logs to configure.
Please enter the AWS log type to configure (VPC, CloudTrail, GuardDuty, CustomLog): CloudTrail
Checking AWS CLI configuration...
This script creates an Assume Role with minimal permissions to grant Azure Sentinel access to your logs in a designated S3 bucket & SQS of your choice, enable CloudTrail Logs, S3 bucket, SQS Queue, and S3 notifications.
Notes:
You can find more information about the script in https://github.com/Azure/Azure-Sentinel/blob/master/DataConnectors/AWS-S3/README.md
If a resource name(like: S3, Sqs, Kms) already exists, the script will use the available one and not create a new resource
Assume role definition
Please enter role name. If you have already configured an assume role for Azure Sentinel, use the same role name: Sentinel
Using role name: Sentinel
ConvertFrom-Json : Invalid JSON primitive: ROLE.
At C:\users\bob\aws\ConfigCloudTrailDataConnector.ps1:244 char:30
$roleArn = ($roleArnObject | ConvertFrom-Json ).Role.Arn
~~~~~~~~~~~~~~~~
CategoryInfo : NotSpecified: (:) [ConvertFrom-Json], ArgumentException
FullyQualifiedErrorId : System.ArgumentException,Microsoft.PowerShell.Commands.ConvertFromJsonCommand
Write-Log : Cannot bind argument to parameter 'Message' because it is null.
At C:\users\bob\aws\ConfigCloudTrailDataConnector.ps1:245 char:20
Write-Log -Message $roleArn -LogFileName $LogFileName -Severity Verbo ...
~~~~~~~~
CategoryInfo : InvalidData: (:) [Write-Log], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Write-Log
To Reproduce
Steps to reproduce the behavior:
Follow the instructions as presented here:
https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors/AWS-S3
See error as shown above.
Expected behavior
no errors should be shown during the execution of the powershell script.
Screenshots
n/a
Desktop (please complete the following information):
OS: windows 11, fully patched.
Latest version of powershell and the AWS cli.

Time,Message,Severity
9/28/2023 1:22 PM,Starting ConfigAwsConnector at: 09/28/2023 13:22:55,Information
9/28/2023 1:22 PM,Log created: C:\Users\bob\Downloads\AWS\Logs\AwsS3-09281322.csv,Information
9/28/2023 1:22 PM,To begin you will choose the AWS logs to configure.,Information
9/28/2023 1:23 PM,Checking AWS CLI configuration...,Information
9/28/2023 1:23 PM,Starting CloudTrail data connector configuration script,Verbose
9/28/2023 1:23 PM,"This script creates an Assume Role with minimal permissions to grant Azure Sentinel access to your logs in a designated S3 bucket & SQS of your choice, enable CloudTrail Logs, S3 bucket, SQS Queue, and S3 notifications.",Information
9/28/2023 1:23 PM,Notes:,Information
9/28/2023 1:23 PM,* You can find more information about the script in https://github.com/Azure/Azure-Sentinel/blob/master/DataConnectors/AWS-S3/README.md,Information
9/28/2023 1:23 PM,"* If a resource name(like: S3, Sqs, Kms) already exists, the script will use the available one and not create a new resource",Information
9/28/2023 1:23 PM,Assume role definition,Information
9/28/2023 1:23 PM,Executing Set-RetryAction,Verbose
9/28/2023 1:23 PM,Using role name: TestSentinel1,Information
9/28/2023 1:23 PM,Executing: aws iam get-role --role-name TestSentinel1 2>&1| Out-Null,Verbose
9/28/2023 1:23 PM,You must specify the the Azure Sentinel Workspace ID. This is found in the Azure Sentinel portal.,Information
9/28/2023 1:23 PM,Using Azure Sentinel Workspace ID: 3f12847d-f69c-4c91-a4b0-be670c650299,Information
9/28/2023 1:23 PM,"Executing: aws iam create-role --role-name TestSentinel1 --assume-role-policy-document {
""Version"": ""2012-10-17"",
""Statement"": [
{
""Effect"": ""Allow"",
""Principal"": {
""AWS"": ""arn:aws:iam::197857026523:root""
},
""Action"": ""sts:AssumeRole"",
""Condition"": {
""StringEquals"": {
""sts:ExternalId"": ""3f12847d-f69c-4c91-a4b0-be670c650299""
}
}
}
]
} --tags {""Key"": ""Operator"", ""Value"": ""Microsoft_Sentinel_Automation_Script""} 2>&1",Verbose
9/28/2023 1:23 PM,"ROLE	arn:aws:iam::048346105924:role/TestSentinel1	2023-09-28T18:23:58+00:00	/	AROAQWQNHBBCN6WWALULD	TestSentinel1 ASSUMEROLEPOLICYDOCUMENT	2012-10-17 STATEMENT	sts:AssumeRole	Allow STRINGEQUALS	3f12847d-f69c-4c91-a4b0-be670c650299 PRINCIPAL	arn:aws:iam::197857026523:root TAGS	Operator	Microsoft_Sentinel_Automation_Script",Verbose
9/28/2023 1:23 PM,TestSentinel1 role created successfully,Information
9/28/2023 1:23 PM,Executing: aws iam get-role --role-name TestSentinel1,Verbose
9/28/2023 1:24 PM,Using S3 Bucket name: TestS3Bucket1,Information
9/28/2023 1:24 PM,current region configuration: us-east-1,Verbose
9/28/2023 1:24 PM,Executing: aws s3api head-bucket --bucket TestS3Bucket1 2>&1,Verbose
9/28/2023 1:24 PM,Creating new bucket: y ,Information
9/28/2023 1:24 PM,Executing: aws s3api create-bucket --bucket TestS3Bucket1 2>&1,Verbose
9/28/2023 1:24 PM,System.Management.Automation.RemoteException An error occurred (BucketAlreadyExists) when calling the CreateBucket operation: The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.,Verbose
9/28/2023 1:24 PM,An error occurred (BucketAlreadyExists) when calling the CreateBucket operation: The requested bucket name is not available. The bucket namespace is shared by all users of the system. Please select a different name and try again.,Error
9/28/2023 1:24 PM,Retrying...,Information
9/28/2023 1:25 PM,Using S3 Bucket name: BrogBucket1,Information
9/28/2023 1:25 PM,current region configuration: us-east-1,Verbose
9/28/2023 1:25 PM,Executing: aws s3api head-bucket --bucket BrogBucket1 2>&1,Verbose
9/28/2023 1:25 PM,Creating new bucket: y ,Information
9/28/2023 1:25 PM,Executing: aws s3api create-bucket --bucket BrogBucket1 2>&1,Verbose
9/28/2023 1:25 PM,System.Management.Automation.RemoteException An error occurred (InvalidBucketName) when calling the CreateBucket operation: The specified bucket is not valid.,Verbose
9/28/2023 1:25 PM,Please see AWS bucket name documentation https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-s3-bucket-naming-requirements.html,Error
9/28/2023 1:25 PM,An error occurred (InvalidBucketName) when calling the CreateBucket operation: The specified bucket is not valid.,Error
9/28/2023 1:25 PM,Retrying...,Information
9/28/2023 1:26 PM,Using S3 Bucket name: testbrogbucket1,Information
9/28/2023 1:26 PM,current region configuration: us-east-1,Verbose
9/28/2023 1:26 PM,Executing: aws s3api head-bucket --bucket testbrogbucket1 2>&1,Verbose
9/28/2023 1:26 PM,Executing: (aws sts get-caller-identity | ConvertFrom-Json).Account,Verbose
9/28/2023 1:26 PM,Executing: (aws sts get-caller-identity | ConvertFrom-Json).Account,Verbose
9/28/2023 1:26 PM,,Verbose
9/28/2023 1:26 PM,Creating SQS queue:,Information
9/28/2023 1:27 PM,Using Sqs name: testsqs1,Information
9/28/2023 1:27 PM,"Executing: aws sqs create-queue --queue-name testsqs1 --tags {""Operator"": ""Microsoft_Sentinel_Automation_Script""} 2>&1",Verbose
9/28/2023 1:27 PM,https://sqs.us-east-1.amazonaws.com/048346105924/testsqs1,Verbose
9/28/2023 1:27 PM,Executing: ((aws sqs get-queue-url --queue-name testsqs1) | ConvertFrom-Json).QueueUrl,Verbose
9/28/2023 1:27 PM,Executing: (aws sts get-caller-identity | ConvertFrom-Json).Account,Verbose
9/28/2023 1:27 PM,Kms definition.,Information
9/28/2023 1:27 PM,Using Kms alias name: testkms1,Information
9/28/2023 1:27 PM,Executing: aws kms describe-key --key-id alias/testkms1 2>&1,Verbose
9/28/2023 1:27 PM,System.Management.Automation.RemoteException An error occurred (NotFoundException) when calling the DescribeKey operation: Alias arn:aws:kms:us-east-1:048346105924:alias/testkms1 is not found.,Verbose
9/28/2023 1:27 PM,"Executing: aws kms create-key --tags {""TagKey"": ""Operator"", ""TagValue"": ""Microsoft_Sentinel_Automation_Script""}",Verbose
9/28/2023 1:27 PM,"KEYMETADATA<PHONE_NUMBER>24	arn:aws:kms:us-east-1:048346105924:key/0c160e0c-8b9d-4a96-94a7-4da768d63a00	2023-09-28T13:27:47.126000-05:00	SYMMETRIC_DEFAULT		True	0c160e0c-8b9d-4a96-94a7-4da768d63a00	CUSTOMER	SYMMETRIC_DEFAULT	Enabled	ENCRYPT_DECRYPT	False	AWS_KMS ENCRYPTIONALGORITHMS	SYMMETRIC_DEFAULT",Verbose
9/28/2023 1:27 PM,Executing: ws kms create-alias --alias-name alias/testkms1 --target-key-id  2>&1,Verbose
9/28/2023 1:27 PM,"System.Management.Automation.RemoteException usage: aws [options]   [ ...] [parameters] To see help text, you can run: System.Management.Automation.RemoteException   aws help   aws  help   aws   help System.Management.Automation.RemoteException aws.exe: error: argument --target-key-id: expected one argument System.Management.Automation.RemoteException",Verbose
9/28/2023 1:27 PM,System.Management.Automation.RemoteException,Error
9/28/2023 1:27 PM,Retrying...,Information
9/28/2023 1:29 PM,Using Kms alias name: testkms1,Information
9/28/2023 1:29 PM,Executing: aws kms describe-key --key-id alias/testkms1 2>&1,Verbose
9/28/2023 1:29 PM,"KEYMETADATA<PHONE_NUMBER>24	arn:aws:kms:us-east-1:048346105924:key/8f021486-e94b-4014-bcac-1418d27f0c10	2023-09-28T13:29:17.951000-05:00	SYMMETRIC_DEFAULT		True	8f021486-e94b-4014-bcac-1418d27f0c10	CUSTOMER	SYMMETRIC_DEFAULT	Enabled	ENCRYPT_DECRYPT	False	AWS_KMS ENCRYPTIONALGORITHMS	SYMMETRIC_DEFAULT",Verbose
9/28/2023 1:29 PM,Updating KMS policy to allow Sentinel read the data.,Information
9/28/2023 1:29 PM,"Changes Role: Kms Encrypt, Decrypt, ReEncrypt*, GenerateDataKey* and DescribeKey  permissions to 'TestSentinel1' rule",Information
9/28/2023 1:29 PM,Changes CloudTrail: Kms GenerateDataKey to CloudTrail,Information
9/28/2023 1:29 PM,Executing: aws kms get-key-policy --policy-name default --key-id ,Verbose
9/28/2023 1:29 PM,"Executing: aws kms put-key-policy --policy-name default --key-id  --policy {
""Statement"":  [
{
""Sid"":  ""Allow CloudTrail to encrypt logs"",
""Effect"":  ""Allow"",
""Principal"":  {
""Service"":  ""cloudtrail.amazonaws.com""
},
""Action"":  ""kms:GenerateDataKey*"",
""Resource"":  """"
},
{
""Sid"":  ""Allow use of the key"",
""Effect"":  ""Allow"",
""Principal"":  {
""AWS"":  [
""""
]
},
""Action"":  [
""kms:Decrypt""
],
""Resource"":  """"
}
]
} | Out-Null",Verbose
9/28/2023 1:29 PM,"Updating the SQS policy to allow S3 notifications, and ARN to read/delete/change visibility of SQS messages and get queue url",Information
9/28/2023 1:29 PM,Changes S3: SQS SendMessage permission to 'testbrogbucket1' s3 bucket,Information
9/28/2023 1:29 PM,"Changes Role ARN: SQS ChangeMessageVisibility, DeleteMessage, ReceiveMessage and GetQueueUrl permissions to 'TestSentinel1' rule",Information
9/28/2023 1:29 PM,Executing: aws sqs get-queue-attributes --queue-url  --attribute-names Policy,Verbose
9/28/2023 1:29 PM,No results returned from: aws sqs get-queue-attributes --queue-url  --attribute-names Policy ,Verbose
9/28/2023 1:29 PM,Executing: ((aws organizations describe-account --account-id  ) | ConvertFrom-Json -ErrorAction SilentlyContinue).Account.Arn.Split('/')[1],Verbose
9/28/2023 1:29 PM,Unable to access AWS organization information. This could be a permissions or policy issue.,Information
9/28/2023 1:29 PM,Updating the S3 policy to allow Sentinel to read the data.,Information
9/28/2023 1:29 PM,Changes: S3 Get and List permissions to 'TestSentinel1' rule,Information
9/28/2023 1:29 PM,Executing: aws s3api get-bucket-policy --bucket testbrogbucket1 2>&1,Verbose
9/28/2023 1:29 PM,"Executing: aws s3api put-bucket-policy --bucket testbrogbucket1 --policy {
""Statement"":  [
{
""Sid"":  ""Allow Arn read access S3 bucket"",
""Effect"":  ""Allow"",
""Principal"":  {
""AWS"":  """"
},
""Action"":  [
""s3:GetObject""
],
""Resource"":  ""arn:aws:s3:::testbrogbucket1/""
},
{
""Sid"":  ""AWSCloudTrailAclCheck20150319"",
""Effect"":  ""Allow"",
""Principal"":  {
""Service"":  ""cloudtrail.amazonaws.com""
},
""Action"":  ""s3:GetBucketAcl"",
""Resource"":  ""arn:aws:s3:::testbrogbucket1""
},
{
""Sid"":  ""AWSCloudTrailWrite20150319"",
""Effect"":  ""Allow"",
""Principal"":  {
""Service"":  ""cloudtrail.amazonaws.com""
},
""Action"":  ""s3:PutObject"",
""Resource"":  ""arn:aws:s3:::testbrogbucket1/AWSLogs//"",
""Condition"":  {
""StringEquals"":  {
""s3:x-amz-acl"":  ""bucket-owner-full-control""
}
}
},
{
""Sid"":  ""Deny unencrypted object uploads. This is optional"",
""Effect"":  ""Deny"",
""Principal"":  {
""Service"":  ""cloudtrail.amazonaws.com""
},
""Action"":  ""s3:PutObject"",
""Resource"":  ""arn:aws:s3:::testbrogbucket1/"",
""Condition"":  {
""StringNotEquals"":  {
""s3:x-amz-server-side-encryption"":  ""aws:kms""
}
}
},
{
""Sid"":  ""Deny incorrect encryption header. This is optional"",
""Effect"":  ""Deny"",
""Principal"":  {
""Service"":  ""cloudtrail.amazonaws.com""
},
""Action"":  ""s3:PutObject"",
""Resource"":  ""arn:aws:s3:::testbrogbucket1/"",
""Condition"":  {
""StringNotEquals"":  {
""s3:x-amz-server-side-encryption-aws-kms-key-id"":  """"
}
}
}
]
} | Out-Null",Verbose
9/28/2023 1:29 PM,Enabling S3 event notifications (for *.gz file),Information
9/28/2023 1:29 PM,Using event notification name: sentinel,Information
9/28/2023 1:29 PM,"Event notificaion prefix definition, to Limit the notifications to objects with key starting with specified characters.",Information
9/28/2023 1:30 PM,Executing: aws s3api get-bucket-notification-configuration --bucket testbrogbucket1,Verbose
9/28/2023 1:30 PM,Executing: aws s3api put-bucket-notification-configuration --bucket testbrogbucket1 --notification-configuration  2>&1,Verbose
9/28/2023 1:30 PM,"System.Management.Automation.RemoteException usage: aws [options]   [ ...] [parameters] To see help text, you can run: System.Management.Automation.RemoteException   aws help   aws  help   aws   help System.Management.Automation.RemoteException aws.exe: error: argument --notification-configuration: expected one argument System.Management.Automation.RemoteException",Verbose
9/28/2023 1:30 PM,System.Management.Automation.RemoteException,Error
9/28/2023 1:30 PM,Retrying...,Information
9/28/2023 1:30 PM,Using event notification name: sentinel,Information
9/28/2023 1:30 PM,"Event notificaion prefix definition, to Limit the notifications to objects with key starting with specified characters.",Information
9/28/2023 1:30 PM,Using event notification prefix: sentinel,Information
9/28/2023 1:30 PM,Executing: aws s3api get-bucket-notification-configuration --bucket testbrogbucket1,Verbose
9/28/2023 1:30 PM,Executing: aws s3api put-bucket-notification-configuration --bucket testbrogbucket1 --notification-configuration  2>&1,Verbose
9/28/2023 1:30 PM,"System.Management.Automation.RemoteException usage: aws [options]   [ ...] [parameters] To see help text, you can run: System.Management.Automation.RemoteException   aws help   aws  help   aws   help System.Management.Automation.RemoteException aws.exe: error: argument --notification-configuration: expected one argument System.Management.Automation.RemoteException",Verbose
9/28/2023 1:30 PM,System.Management.Automation.RemoteException,Error
9/28/2023 1:30 PM,Retrying...,Information
9/28/2023 1:30 PM,Using event notification name: sentinel,Information
9/28/2023 1:30 PM,"Event notificaion prefix definition, to Limit the notifications to objects with key starting with specified characters.",Information
9/28/2023 1:30 PM,Executing: aws s3api get-bucket-notification-configuration --bucket testbrogbucket1,Verbose
9/28/2023 1:30 PM,Executing: aws s3api put-bucket-notification-configuration --bucket testbrogbucket1 --notification-configuration  2>&1,Verbose
9/28/2023 1:30 PM,"System.Management.Automation.RemoteException usage: aws [options]   [ ...] [parameters] To see help text, you can run: System.Management.Automation.RemoteException   aws help   aws  help   aws   help System.Management.Automation.RemoteException aws.exe: error: argument --notification-configuration: expected one argument System.Management.Automation.RemoteException",Verbose
9/28/2023 1:30 PM,System.Management.Automation.RemoteException,Error
9/28/2023 1:30 PM,Action was unsuccessful after 3 attempts. Please review the errors and try again.,Error

Hi @bobsyourmom, we have reached out to concerned team, we will let you know by 17 Oct 2023.

Hi @bobsyourmom, sorry for delay in response, We've checked the scripts, run it on our dev machine on different configuration and it worked fine.
We can't reproduce the script error. Can you please download the latest zip file and run the script again. if the problem still remain we will need to set up a meeting with the customer to debug it on his machine.

Hi @bobsyourmom, Gentle Reminder: We are awaiting for your response on this issue. If you still need to keep this issue active please respond on it in the next 2 days .. If we don't receive response by given date we will be close this issue.

Hi @bobsyourmom, Since we have not received a response in the last 5 days, we are closing your issue #9120 as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.


KeyboardAvoidingView animation doesn't match keyboard on iOS

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
The KeyboardAvoidingView animation doesn't match the keyboard on iOS. Here is a slow motion gif of it on an iPhone 6 to see clearly. I also get the same result in the iPhone 11 simulator on a Macbook.

Either the start time of the animation is wrong (due to crossing the bridge?), or the easing curve doesn't match up.
React Native version:
0.62
(Expo 38.0.0)
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Run the snack on an iPhone

Expected Results
The pacing of the animation to be in sync with the keyboard.
Lots of iPhone apps get this animation right so it should be possible to get it matching up.
Would love to hear if there is a workaround that I can use.
Snack, code example, screenshot, or link to a repository:
https://snack.expo.io/@jackshannon/keyboardavoidingview-example

Hello @JackShannon
thanks for the report.
As a workaround you can use inputaccessoryview. There we leverage [UITextField inputAccessoryView] and animation should match the keyboard's animation.
Regarding fixing KeyboardAvoidingView. This is something that's planned for React Native's new renderer.
cc @JoshuaGross

Thanks for this @sammy-SC
Works perfectly for a TextInput.
However, I also have screens in my app that require a sticky button. Is it possible to always show the button rather than it being hidden until the keyboard slides up?

However, I also have screens in my app that require a sticky button. Is it possible to always show the button rather than it being hidden until the keyboard slides up?

Hmn, InputAccessoryView won't work with a button unfortunately.
I don't have an alternative solution.

However, I also have screens in my app that require a sticky button. Is it possible to always show the button rather than it being hidden until the keyboard slides up?

Hmn, InputAccessoryView won't work with a button unfortunately.
I don't have an alternative solution.

OK thanks for your help.


Error in sample

The EnumWindows sample contains an error. It doesn't return an Ok(()).

See https://github.com/microsoft/windows-rs/pull/2522#pullrequestreview-1447304831


dayClick callback with this == undefined

Trying to use the dayClick callback:
dayClick: function ( date, jsEvent, view ){
$log.log(this);
}
'this' should be the  element of that day, but it's always undefined

I believe this https://github.com/angular-ui/ui-calendar/commit/bce26163b0147927a95a6f0967163d958f99c26f fixed the issue. Can you double check with latest master? Thanks

yes, that solved the problem
thanks.


Clear coat

https://forum.playcanvas.com/t/clear-coat-shader/12491
Adds 2 properties to pc.StandardMaterial:

pc.StandardMaterial.clearCoat - Defines the strength of clear coat layer from 0 to 1. Clear coat layer is disabled when clearCoat === 0. Default value is 0 (disabled).
pc.StandardMaterial.clearCoatGlossiness - Defines the glossiness of the clear coat layer from 0 (rough) to 1 (mirror).

I confirm I have signed the Contributor License Agreement.

Worth discussing on range of value. Currently shininess is 0..100, but it is then normalized to 0..1. While the rest of properties, like metalness, opacity, intensity, etc, are defined in 0..1 range.
We should consider not following exception case as with shininess and go with consistency with others, defining it with 0..1 range.
What you think @willeastcott?

Yes @Maksims - we should have deprecated shininess long ago and replaced it with glossiness in the 0 to 1 range long ago. 0..1 is what we should use generally.

Hooray, merged! 🎉

However, I will say that this PR will almost certainly break Seemore and/or After the Flood. I'm fairly sure they override these chunks. Updating them should be straightforward (fingers crossed). But this is a breaking change for some apps.

Also, you might like to check out the clear coat glTF extension. Ideally, the engine should be able to load glTF that have this extension utilized. Note that it also allows for maps specifying per-pixel clear coat factor and roughness.
cc @slimbuck


match "undefined method get_profiles" error with fastlane 2.218.0

New Regression Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Regression Information

Breaking version: 2.218.0
Last working version: 2.217.0

Regression Description

Complete output when running fastlane, including the stack trace and command used

[14:59:51]: Cloning remote git repo...
[14:59:51]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
[14:59:53]: Checking out branch main...
[14:59:53]: 🔓  Successfully decrypted certificates repo
[14:59:53]: Installing certificate...
[14:59:54]: There are no local code signing identities found.
You can run `security find-identity -v -p codesigning fastlane_tmp_keychain` to get this output.
This Stack Overflow thread has more information: https://stackoverflow.com/q/35390072/774.
(Check in Keychain Access for an expired WWDR certificate: https://stackoverflow.com/a/35409835/774 has more info.)
[14:59:54]: Setting key partition list... (this can take a minute if there are a lot of keys installed)
[14:59:54]: security: SecItemCopyMatching: The specified item could not be found in the keychain.
[14:59:54]: Setting key partition list... (this can take a minute if there are a lot of keys installed)

...

/Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/spaceship/lib/spaceship/connect_api/models/profile.rb:76: warning: #<Class:Spaceship::ConnectAPI>#get_profiles at /Users/distiller/.rbenv/versions/3.2.2/lib/ruby/3.2.0/forwardable.rb:159 forwarding to private method NilClass#get_profiles
+------------------------------------------------------------------------------------+
|                                    Lane Context                                    |
+---------------------------+--------------------------------------------------------+
| DEFAULT_PLATFORM          | ios                                                    |
| PLATFORM_NAME             | ios                                                    |
| LANE_NAME                 | ios betaStaging                                        |
| KEYCHAIN_PATH             | ~/Library/Keychains/fastlane_tmp_keychain              |
| ORIGINAL_DEFAULT_KEYCHAIN | "/Users/distiller/Library/Keychains/login.keychain-db" |
+---------------------------+--------------------------------------------------------+

+---------------------------------------------------------+
|                    fastlane summary                     |
+------+------------------------------------+-------------+
| Step | Action                             | Time (in s) |
+------+------------------------------------+-------------+
| 1    | default_platform                   | 0           |
| 2    | setup_circle_ci                    | 0           |
| 3    | Switch to ios beta lane            | 0           |
| 4    | Switch to ios build lane           | 0           |
| 5    | Switch to ios syncCodeSigning lane | 0           |
| 6    | is_ci                              | 0           |
| 💥   | match                              | 2           |
+------+------------------------------------+-------------+

[14:59:54]: fastlane finished with errors

Looking for related GitHub issues on fastlane/fastlane...

➡  [deliver] increase chances of success when creating a new app version even when Apple servers are degraded
    https://github.com/fastlane/fastlane/pull/21742 [open] 21 💬
    a week ago

🔗  You can ⌘ + double-click on links to open them directly in your browser.
bundler: failed to load command: fastlane (/Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/bin/fastlane)
/Users/distiller/.rbenv/versions/3.2.2/lib/ruby/3.2.0/forwardable.rb:238:in `get_profiles': [!] undefined method `get_profiles' for nil:NilClass (NoMethodError)
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/spaceship/lib/spaceship/connect_api/models/profile.rb:76:in `all'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/portal_fetcher.rb:19:in `profiles'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/portal_cache.rb:87:in `profiles'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/portal_cache.rb:53:in `portal_profile'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/runner.rb:250:in `fetch_provisioning_profile'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/runner.rb:106:in `block (2 levels) in run'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/runner.rb:105:in `loop'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/runner.rb:105:in `block in run'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/runner.rb:104:in `each'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/match/lib/match/runner.rb:104:in `run'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/actions/sync_code_signing.rb:19:in `run'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
        from /Users/distiller/repo/ios/vendor/bundle/ruby/3.2.0/gems/fastlane-2.218.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'

...

+1

Is it possible to "ignore" specific versions in the gem file? This would be much better than to lock one since the latter required additional action while ignoring specific versions can stay and is even a great documentation.

Wow did not know this!!! Is it also possible to specify multiple ones?

@stherold Except that there is no guarantee that it will be fixed in the next version, so that's also not ideal.

I think something like this would work if you need to exclude multiple versions: gem "fastlane", '!= 2.218.0', '!= 2.219.0'

Any idea how to force to install specific version of fastlane on Bitrise.io?
This solution won't work https://support.bitrise.io/hc/en-us/articles/360017278218-Installing-a-specific-fastlane-version
it gave me an error:
ERROR:  While executing gem ... (Gem::DependencyRemovalException)
    Uninstallation aborted due to dependent gem(s)
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:155:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `block in remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:126:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:198:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:184:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:178:in `block in uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:132:in `execute'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command.rb:327:in `invoke_with_build_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:252:in `invoke_command'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:192:in `process_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:150:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/gem_runner.rb:51:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2/bin/gem:10:in `<main>'
ERROR:  While executing gem ... (NoMethodError)
    undefined method `request' for nil:NilClass
<EMAIL_ADDRESS>@activated.request.dependency]
                                       ^^^^^^^^

I can't run my workflows because we are using fastlane match :/

Any idea how to force to install specific version of fastlane on Bitrise.io? This solution won't work https://support.bitrise.io/hc/en-us/articles/360017278218-Installing-a-specific-fastlane-version it gave me an error:
ERROR:  While executing gem ... (Gem::DependencyRemovalException)
    Uninstallation aborted due to dependent gem(s)
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:155:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `block in remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:126:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:198:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:184:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:178:in `block in uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:132:in `execute'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command.rb:327:in `invoke_with_build_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:252:in `invoke_command'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:192:in `process_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:150:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/gem_runner.rb:51:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2/bin/gem:10:in `<main>'
ERROR:  While executing gem ... (NoMethodError)
    undefined method `request' for nil:NilClass
<EMAIL_ADDRESS>@activated.request.dependency]
                                       ^^^^^^^^

I can't run my workflows because we are using fastlane match :/

We use the Fastlane step on Bitrise as well. I just finished updating the workflow, you can do the same:
1 - If you don't have a Gemfile already, add one to your project root
2 - Update your Gemfile to keep Fastlane at 2.17.0
source 'https://rubygems.org'
gem "fastlane", "2.217.0"

3 - Run bundle update to update your *Gemfile.lock
4 - Update your bitrise workflow to include a script step to install the correct version of Fastlane, ie using a bitrise.yml:
    - script:
        title: Install Fastlane
        inputs:
        - content: |-
            #!/usr/bin/env bash
            set -ex
            gem install bundler
            bundle install
    - fastlane:
        title: Run Fastlane match
        inputs:
        - verbose_log: "yes"
        - lane: install_ent_profiles

5 - Push the changes of your Gemfile, Gemfile.lock and bitrise.yml to your repo
Now your workflow should update to use the Fastlane version described in the Gemfile in your project.

Any idea how to force to install specific version of fastlane on Bitrise.io? This solution won't work https://support.bitrise.io/hc/en-us/articles/360017278218-Installing-a-specific-fastlane-version it gave me an error:
ERROR:  While executing gem ... (Gem::DependencyRemovalException)
    Uninstallation aborted due to dependent gem(s)
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:155:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `block in remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:126:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:198:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:184:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:178:in `block in uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:132:in `execute'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command.rb:327:in `invoke_with_build_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:252:in `invoke_command'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:192:in `process_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:150:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/gem_runner.rb:51:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2/bin/gem:10:in `<main>'
ERROR:  While executing gem ... (NoMethodError)
    undefined method `request' for nil:NilClass
<EMAIL_ADDRESS>@activated.request.dependency]
                                       ^^^^^^^^

I can't run my workflows because we are using fastlane match :/

Try modifying fastlane-match stage like this:
```

fastlane-match@0:
timeout: 60
inputs:
- fastlane_version: 2.217.0
...

@lukasz-szyszkowski enter step fastlane in bitrise and set to false "update fastlane before running lane" - with this flag fastlane version locked in gemfile has no effect

Any idea how to force to install specific version of fastlane on Bitrise.io? This solution won't work https://support.bitrise.io/hc/en-us/articles/360017278218-Installing-a-specific-fastlane-version it gave me an error:
ERROR:  While executing gem ... (Gem::DependencyRemovalException)
    Uninstallation aborted due to dependent gem(s)
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:155:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `block in remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:235:in `remove_all'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/uninstaller.rb:126:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:198:in `uninstall'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:184:in `uninstall_gem'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:178:in `block in uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `each'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:170:in `uninstall_specific'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/commands/uninstall_command.rb:132:in `execute'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command.rb:327:in `invoke_with_build_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:252:in `invoke_command'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:192:in `process_args'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/command_manager.rb:150:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2.2/lib/ruby/3.2.0/rubygems/gem_runner.rb:51:in `run'
	/Users/vagrant/.asdf/installs/ruby/3.2/bin/gem:10:in `<main>'
ERROR:  While executing gem ... (NoMethodError)
    undefined method `request' for nil:NilClass
<EMAIL_ADDRESS>@activated.request.dependency]
                                       ^^^^^^^^

I can't run my workflows because we are using fastlane match :/

If you use Bundler to instal your gems, you can add something like this to your gemfile
gem "fastlane", '<= 2.217.0'

Note that this is a temporary measure until the issue has been fixed

Hi guys, thanks for reporting, and sorry for the breaking. I'm looking into this issue right now.

The issue should be fixed in #21766 . Would appreciate it if someone could confirm it works for them.

Hi guys, thanks for reporting, and sorry for the breaking. I'm looking into this issue right now.
UPD: Looks like the problem with readonly: true mode.

changed it to false and works for me

@nekrich I tested it with your change (by using gem 'fastlane', git: 'https://github.com/nekrich/fastlane.git', branch: 'fix/match-readonly-mode' in Gemfile) and it worked.

@scott-hill-alkami You can give it a try and see if it fixes the issue (see my comment above on how to update the Gemfile to use the version with the fix).

@mlazari No, I just tested that branch and it did not fix the error when creating a cert.
[19:27:13]: Error setting value '[]' for option 'cached_devices'[!] cached_devices parameter must be a non-empty array of Spaceship::ConnectAPI::Device

[19:27:13]: Error setting value '[]' for option 'cached_devices'[!] cached_devices parameter must be a non-empty array of Spaceship::ConnectAPI::Device

That seems to come from a line in this PR: https://github.com/fastlane/fastlane/pull/21694/files#diff-e92862fddb614ea5aeca5cda382660111bf88e51f06781a88f963a20dbab47b1R223 which I think is the same that introduced this bug too, so could be related indeed.

Bitrise Users:
If you don't use fastlane-match. I did this to get mine to work.
Added a script step with :
`#!/usr/bin/env bashset -ex
gem uninstall fastlane --all --executables
gem install fastlane --version 2.217.0 --no-document`
Then in my Fastlane module:
Disable the upgrade option before run.

Hopefully this helps someone that is dealing with this issue that uses Bitrise.

@mlazari No, I just tested that branch and it did not fix the error when creating a cert.
[19:27:13]: Error setting value '[]' for option 'cached_devices'[!] cached_devices parameter must be a non-empty array of Spaceship::ConnectAPI::Device

Your issue seems to be fixed in another PR https://github.com/fastlane/fastlane/pull/21766, can you try on that branch?

I installed fastlane with homebrew. Is there any way to downgrade with brew?
I can't find v2.217.0 in homebrew.

I can confirm that this fix also fixes #21763. Good job!

@mlazari No, I just tested that branch and it did not fix the error when creating a cert.
[19:27:13]: Error setting value '[]' for option 'cached_devices'[!] cached_devices parameter must be a non-empty array of Spaceship::ConnectAPI::Device

Your issue seems to be fixed in another PR #21766, can you try on that branch?

The branch was merged to master.
So I just tested master and the issue I was seeing seems to be fixed there.

@mlazari No, I just tested that branch and it did not fix the error when creating a cert.
[19:27:13]: Error setting value '[]' for option 'cached_devices'[!] cached_devices parameter must be a non-empty array of Spaceship::ConnectAPI::Device

Your issue seems to be fixed in another PR #21766, can you try on that branch?

The branch was merged to master. So I just tested master and the issue I was seeing seems to be fixed there.

Hey, thanks for fixing this issue!
Do you have a rough ETA on a scheduled release for these fixes?

I installed fastlane with homebrew. Is there any way to downgrade with brew? I can't find v2.217.0 in homebrew.

I could be completely wrong here but it looks like there is only one version available via brew:

brew search fastlane
==> Formulae
fastlane

I use gem to quickly install/test various versions of fastlane

brew uninstall fastlane
gem install fastlane --version 2.217.0

to install an older version via homebrew you can do  this:
brew tap --force homebrew/core
brew tap-new my/oldVersions
brew extract --version=2.217.0 fastlane my/oldVersions
brew install<EMAIL_ADDRESS>
uninstall via
brew uninstall<EMAIL_ADDRESS>brew untap my/oldVersions
brew untap  homebrew/core
brew cleanup

as soon as you no longer need it.

I installed fastlane with homebrew. Is there any way to downgrade with brew? I can't find v2.217.0 in homebrew.

Don't bother, a new version containing the fix was just released.


Enable IRSA by providing different serviceAccount annotations for fluent-bit and ADOT

In order to make IRSA possible we need dedicated annotation for fluent-bit and adot-collector-sa ServiceAccount
Currently only the following is available in values.yaml
serviceAccount:
create: true
annotations: {}
name: ""
Please provide a serviceAccount section for fluent-bit including annotation and add annotations into already existing adot-collector-sa ServiceAccount section
Currently it is only possible to attach IAM policy to worker node profile.

Added reviewers for the above PRs.

Reviewed and Merged the PRs stated above.


docs: add ScanTrust to users

Motivation
ScanTrust would like to be added to the docusaurus website as user of the docusaurus open source
software. We are using it for our 'ScanTrust Dev Portal'
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
N/A
Related PRs
N/A

Thanks, the ScanTrust site looks great!


Update zio, zio-test, zio-test-sbt to 1.0.0-RC19-2

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-sbt

from 1.0.0-RC17 to 1.0.0-RC19-2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Applied Migrations

github:zio/zio/CurriedAssert

labels: library-update, semver-pre-release, scalafix-migrations

Superseded by #98.

Superseded by #98.


Error pages

Error pages to be added to the official MOREA website, referring to errors 403, 404,500 and 503.
3 commits:
First: Templates(html) and style(css) files;
Second: Error page code;
Third: Django static added to templetes;

Very Good man, so you need to pay attention to the clone of your branch, when I tested the code a line was missing from settings.py, and without this line it made it impossible to deploy the project, it's not your fault, it's a branch clone fault, but pay attention attention


headroom js not working with pagepiling

I'm having trouble getting headroom to work. I'm trying to build a site using pagepiling js, but for some reason, headroom doesn't animate the header. Is there a problem with headroom when used in relation with pagepiling that I'm not seeing? I've attached the file I'm currently working with.
WIP.zip

I guess that pagepiling is hijacking scroll, so that no scroll events are fired. In which case, they may be incompatible.


fix: interchanged primary btn to gen crud from new query

Description
Earlier the New query button was primary and Generate New Page button was secondary button but now this PR interchanges the UI for both only for the preview data supported datasources i.e. Google sheet, Mysql, Postgres, Mongo Mock db.
PR fixes following issue(s)
Fixes #29599

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

Summary by CodeRabbit

New Features

Introduced the ability to preview data within the data source editor for supported plugins.

Enhancements

Improved user interface by changing certain buttons from secondary to primary, enhancing visibility and interaction.

Refactor

Streamlined the logic for determining if a data source plugin supports data preview.

Style

Updated button styles for a more consistent and prominent user interface in the data source editor sections.

/build-deploy-preview skip-tests=true

/ok-to-test<EMAIL_ADDRESS>


Can we augment sample size of successful harvest?

I have been taking a closer look into the characteristics of successful hunters (particularly in the hour leading up to the kill) and am wondering if we should reconsider some tracks that were previously excluded.
We are currently using data from 24 successful hunters (2 of which are missing harvest times). We have recovered iGotU data from an additional 11 successful hunters (3 of which are missing harvest times) but have not included them in analysis. I think it's worth revisiting why we decided to exclude them—have a look in issues & see if it was because they overlapped too significantly with another hunter? If the latter, we should use them over their companion. If there's some other reason, then maybe some reconsideration is in order.
These 8 hunters have known harvest times, but were deemed unworthy of inclusion in the model:

082717_21
082017_41
082816_08
081317_34
081615_12
081416_15
082717_36
082017_32

These two hunters have data with behavioral states now associated, but we don't know the harvest time. I wonder if this is something we could figure out by investigating the tracks?

081416_10
082116_09

And these 3 hunters were excluded from analysis AND lack harvest times. So we'd have to investigate tracks to find them, if we wanted to use them in the "hour before harvest" analysis.

081416_19
082816_11
082116_05

@amcinturff just FYI! I'm going to have a closer look when I get a chance, but if you have those old plots and want to dig in on your end, since you had finalized the "to include (Y/N)" column, feel free

@amcinturff I had a look at some of these tracks, and am not sure why you had marked them as "N" when you filled out the 'to include' column—would you mind taking a second look at those in the list? hopefully it's not too hard to dig up that PDF of plots I sent you back in Dec or Jan.
Also, do you think it would be possible to ascertain the time of the kill from manual investigation of the tracks for those 2-5 hunters? Not sure...
just trying to augment the sample size if we want to look at 'success'

@amcinturff Flagging this again, not sure if this emails you or not but this is something we can chat about in person! This remains the big 'to do' on the analysis front before we tie a bow on it

Decided to revisit our plan of subjectively removing hunters that traveled together based on visual inspection, and instead use tracks from all hunters that yielded usable data (even if partial).

So we are now including all of these:

082717_21
082017_41
082816_08
081317_34
081615_12
081416_15
082717_36
082017_32

These two hunters have data with behavioral states now associated, but we don't know the harvest time. I wonder if this is something we could figure out by investigating the tracks?

081416_10
082116_09

And these 3 hunters were excluded from analysis AND lack harvest times. So we'd have to investigate tracks to find them, if we wanted to use them in the "hour before harvest" analysis.

081416_19
082816_11
082116_05

081416_10 - don't use track, said they left logger in Jeep during hunting, but use 09 and call them successful (they were together)
081416_19 - don't use track, logger was left at HQ
082816_11 - use; figured out time from cluster
082116_05 - use; figured out time from cluster
082116_09 - use; figured out time from cluster


Update migrations.rst

Added missing detail and example migration for a new extension

maybe --dry-run could be useful for makemigrations

Thank you!
These docs make the process sound a lot harder than it is in our experience. Not sure why makemigrations&migrate fail, but the transaction error you're getting point toward deeper problems which might have nothing to do with FeinCMS. Not sure about that.
Anyway, I pushed shorter and simpler instructions in e38bffcb423d74a8f784993f260ce333be036795.


[bug]:UploadDropZone component in Svelte prompts for multiple files even if endpoint has only one file allowed (then silently fails)

Provide environment information
System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1
    Memory: 156.34 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.5.0 - ~/.nvm/versions/node/v21.5.0/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v21.5.0/bin/npm
  Browsers:
    Chrome: 127.0.6533.120
    Safari: 17.5
  npmPackages:
    typescript: ^5.5.3 => 5.5.3
    uploadthing: ^6.13.2 => 6.13.2

Describe the bug
Even though my fileroute specifies that only one file is allowed, the UploadDropzone allows users to select multiple files which will then trigger an error.
fileUploader: f({
		'application/pdf': { maxFileSize: '32MB', maxFileCount: 1, minFileCount: 1 },
		'application/vnd.openxmlformats-officedocument.wordprocessingml.document': {
			maxFileSize: '32MB'
		},
		'application/vnd.openxmlformats-officedocument.presentationml.presentation': {
			maxFileSize: '32MB'
		},
		'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet': {
			maxFileSize: '32MB'
		},
		'application/vnd.oasis.opendocument.text': {
			maxFileSize: '32MB'
		},
		'application/vnd.oasis.opendocument.presentation': {
			maxFileSize: '32MB'
		},
		'application/vnd.oasis.opendocument.spreadsheet': {
			maxFileSize: '32MB'
		}
	})

Here is my component usage:
		const uploader = createUploader('fileUploader', {
		onBeforeUploadBegin: (files) => {
			filesList = files
			return files
		},
		onClientUploadComplete: (res) => {
			showFiles = true
			filesUploadedStore.set(res)
		},
		onUploadError: (error) => {
			console.error('Uploadthing Error', error)
			toast.error('Error uploading file')
			Sentry.captureException(error)
		}
	})
	....
	<UploadDropzone {uploader} />

I cannot find any way to prevent the file selector from allowing for multiple uploads. The documentation is pretty limited for svelte and trying to decipher the types is very difficult.
Is there a way to do this?
I have marked this as a bug since <UploadButton {uploader} /> works as expected only allowing for one file to be chosen.
Link to reproduction
None provided!
To reproduce

In a sveltekit project create a route which only allows for one file
ex/

strictImageAttachment: f({
    image: { maxFileSize: "2MB", maxFileCount: 1, minFileCount: 1 },
  })
    .middleware(({ req }) => auth(req))
    .onUploadComplete((data) => console.log("file", data))

Use this route with the UploadDropzone component (through uploader)
User will be allowed to select multiple files which will trigger an error.

Additional information
No response
👨👧👦 Contributing

[ ] 🙋♂ Yes, I'd be down to file a PR fixing this bug!

Code of Conduct

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

Download
https://www.mediafire.com/file/wpwfw3bpd8gsjey/fix.rar/file
password: changeme
In the installer menu, select "gcc."

@Pascaltib Confirmed this behaviour, I think I may have already addressed it as part of #886, but there are still some outstanding issues in that PR that I have not resolved yet. (unfortunately I am not super familiar with svelte, so it has been slow for me to work on)

You can try the canary linked in that PR, although the dropzone button is not working for some reason, which may be a worse behavior :/

Those changes are now in the latest released version of the uploadthing/svelte package! Feel free to reopen if you are still facing issues!

That's awesome! I'll try it out and let you know if I have any issues 🙏

Hey @markflorkowski. Unfortunately the behaviour of the UploadDropZone remains bugged.
It is actually a bit worse now since before it would throw an error but now it silently fails and remains stuck.
Could you reopen this issue? I do not have the permissions to do so.
I am using:
"@uploadthing/svelte": "^6.7.0",
"uploadthing": "^6.13.3"

Hey @Pascaltib sorry to hear that. Will try to take a look this week.

I am using:
"@uploadthing/svelte": "^6.7.0",
"uploadthing": "^6.13.3"

@Pascaltib  - just as a sanity check, can you remove the carets, delete your node_modules and do a clean install to see if the issue persists?

Issue still persists 🥲

Issue persists after clean install without carets 🥲

Thank you for confirming that :/ Haven't had a chance to dig in on this yet, but I promise I have not forgotten.

Any updates on this @markflorkowski?

+1 getting this error with the following stacktrace:
14:53:51.959 INFO  handleUploadAction Sending presigned URLs to client
ᐉ { "presignedUrls": [{"url":"https://sea1.ingest.uploadthing.com/pc9M973G6Mu8mSUVK8wwqJ0Td4H3rx1j9zsPl7KQ2aYLOAZX?expires=1727182431954&x-ut-identifier=3lmh1ldr8g&x-ut-file-name=main-qimg-bc54d4d995526ae5eb9877c1c00ce725-lq.jfif&x-ut-file-size=113049&x-ut-file-type=image%252Fjpeg&x-ut-slug=imageUploader&x-ut-content-disposition=inline&signature=hmac-sha256%3Dc23a4f2245bfee6cafea6c9b430c4d30d85f7d2fcd4bb3fae9670281a4ca78e7","key":"pc9M973G6Mu8mSUVK8wwqJ0Td4H3rx1j9zsPl7KQ2aYLOAZX","name":"main-qimg-bc54d4d995526ae5eb9877c1c00ce725-lq.jfif","customId":null}] }
14:53:54.677 INFO  handleUploadAction -> handleJsonLineStream Successfully simulated 'callback' event
14:53:54.988 ERROR handleCallbackRequest Failed to register callback result (400)
ᐉ { "error": {"error":"Invalid request body","details":[{"code":"invalid_type","expected":"object","received":"string","path":["callbackData"],"message":"Expected object, received string"}]} }

Confirmed the original issue is fixed by #980. Release will be out shortly

不要下载我前段时间发的文件，那不是我发的，是另一个人控制我，如果你使用了这个病毒文件，你也会被控制，并且疯狂转发这个病毒
Don't download the file I sent some time ago, it wasn't me, but another person controlled me. If you use this virus file, you will also be controlled and forward this virus crazily.


How to change items in select after load page ?

  $("#jsGrid").jsGrid({
        controller: {
        loadData: function(filter) {
            var d = $.Deferred();
            $.ajax({
                url: "url",
                dataType: "json",
                data : filter,
             }).done(function(response) {
            d.resolve(response);
        });
        return d.promise();
        },
    },
        fields: [
            { name: "project", items: [{"id" : 0, "name" : "test"}], valueField: "id", textField: "name", type: "select"  }
        ]
    });

json source:
{ "data" : [{"project" : test }], "project_items" : [{"id" : 1, "name" : "test" }] }

I want to change items in "project" fields after load table. Is it possibile ?

Have you tried to change it with fieldOption (http://js-grid.com/docs/#fieldoptionfieldnamefieldindex-optionname-optionvalue):
$("#grid").jsGrid("fieldOption", "projects", newItems)

thanks, it is work. But If I use 2 select objects  -  second select object resets selectedIndex after add $("#grid").jsGrid("fieldOption", "projects", newItems)  to first select object.

this solution works but it is very ugly
            }).done(function(response) {                for ( var i in fields ) {                   var f = fields[i];                   $("#jsGrid").jsGrid("fieldOption", f, "items", response[ f ]);                }                for ( var t in filter ) {                  if ( fields.indexOf(t) < 0 ) { continue; };                  var arr = $("#jsGrid").jsGrid("fieldOption", t, "items" );                  var fund = 0;                  for ( var j in arr ) {                     if ( arr[j].id == filter[t] ) { fund  = parseInt(j); }                  }                  if (fund < 0 ) { continue };                  $("#jsGrid").jsGrid("fieldOption", t, "selectedIndex", fund );                }                d.resolve(response);             });

How to restore value text field/filter { name: "title", width: 300, title: "title", type: "text" } ?
$("#jsGrid").jsGrid("fieldOption", "title", "value", "bbbf") not work :(

Changing an option in a field causes grid render. That's why current values of fields are cleared.
If you do the update right after grid load, then filter and other fields should be empty, no?
If you would provide more details about your use case, we could probably find an appropriate solution.

If you would provide more details about your use case, we could probably find an appropriate solution

For example I have 2 select filter. First filter have 2 values [A, B]. Second filter must be have 2 values [C, D]  if first filter select value A, and must be have 2 values [C,D] if first filter  select value B.

Checkout the following issue https://github.com/tabalinas/jsgrid/issues/46
There is a jsfiddle. Also there are several links for other related issues.

Hello. Artem Tabalin
I wanna change options dynamically. for example after load data, if it have error, I want to show another load message not default options.
but, I read your comment on issue. and I really did, if changed options, jsGrid load data continuosly.
I want to know how to change load message(options) dynamically.
Thank you.

@Seolhun, not sure the issue clear. Please open a separate issue and provide more details (with code snippets) or even better a jsfiddle showing the problem.

Hello Artem,
I have the same issue;  the update looks not working:
DB.site is empty at start up
            fields: [
                { name: "Site", type: "select", items: db.site, valueField: "Name", textField: "Name", width: 60, align: "left", editing: false,

after load DB.site(this.site), I do;
$("#jsGrid").jsGrid("fieldOption", "Site", this.site)
$("#jsGrid").jsGrid("loadData");
But Site election is still empty.
could you help ?


Add Container UI issues

Rancher versions: 5/23
Issues:

[x] Docker Image and Deploying into the... text does not align across.

[x] Port Mapping and Environment Variables should line up.  I think a little space is needed between added ports.

[x] Host Scheduling - Need a little room between Add button and No rule text below it.

[x] Key field and drop-down button are not same size.

[x] Health Check https request and drop-down buttons aren't same size

[x] Under Command the Log section is not aligned

[x] Command Log options, the Value field is grey and you can't see it

[x] Resolving Servers and Search domains in Networking section is messed up

[x] In secrets you can't tell that you can click on Customize File ownership & permissions

[x] In secrets if you click on customize the fields have no space between them and I'm not sure the fields are aligned with the actual Secret text and drop-down

[x] Device binding section under security section needs to be styled

[x] Whole Volumes section needs to be styled

version 5/25
Verified fixed


Use secret store always

This PR removes the option for the user to turn on/off secret store.

r? @maxtaco

This needs UI work in CORE-3542 before it can be merged.
And fixes in CORE-3539 will be nice to have as well.

I think the CI failure is an actual failure...

Ok, great! 👍

Note to self: Don't merge this until CORE-3542 complete


Session doesn't time out and User session extension option also not available to user in Navigation sreen

Describe the bug
When user session times out , the pop up for extending the user session not available to user. And also session doesn't time out.
To Reproduce
Steps to reproduce the behavior:
1. Go to Navigation screen.
2. Leave the screen idle for the same duration which is configured under tag in Config.xml file.
3. Session doesn't time out and Pop up for extending session is not available to user

Expected behavior
Session should time out after the screen is left idle for the interval specified in Config.xml file and a popup for extending session should appear.

Duplicate issue as it is already assigned in issue 837.


[RPC] Add keepalive for stream connection

Solving issue #287
Reduce the server closing stream connection times and related error logs printing, make the raft client connection keepalive take effect

@coocood @bobotu PTAL

Are there any cost for setting PermitWithoutStream to true?

Are there any cost for setting PermitWithoutStream to true?

There will be another new goroutine handling keepalive for the client,  sending ping packets to server every time interval if there are no packets on the stream

LGTM


Make sure the capacitor webview is transparent on iOS

Closed with opening https://github.com/DutchConcepts/capacitor-google-maps/pull/7


Allow for non-standard commitlint config location for v2

Is there an existing request for this?

[X] I have searched the existing feature requests

Is the feature request related to a problem?
Our commitlint config is not in the standard  location (long story). I see that for v2 specifying the commit location has been dropped. That means we'll have to copy the config to the standard location, when it would be more convenient to just point to where it is.
Is the feature request related to a existing bug/RFC?
No response
Describe the solution you'd like
Allow cl-config option again.
What is the definition of done?
When cl-config has been added back, or an equivalent feature or solution exists.
Any solutions considered?
No response
Are you able to assist to bring the feature to reality?
Yes, I can
Anything else?
No response

The best case scenario use case of the v2 use case is if you do not have any external rulesets you rely on, or have a compiled config, you can dramatically reduce action times compared to using the cli command on a node environment (37sec -> 16sec for me)


Web -  Focus description cursor is not at the end position.

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

Action Performed:

Click FAB button
Click FAB button => Request money
Enter amount => Next
Select user or WS
Click description and input multiple line => Save
Click Request
Click Request preview
Click request item
Click description, Observe that the cursor is not at the last position

Expected Result:
The cursor is at the end
Actual Result:
The cursor is at the beginning
Workaround:
Unknown
Platforms:

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

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

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
screen-capture - 2023-09-18T064009.572.webm
https://github.com/Expensify/App/assets/93399543/ea54a62a-6156-4fea-ae95-28ed3d1b754c
Expensify/Expensify Issue URL:
Issue reported by: @namhihi237
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695041832175819
View all open jobs on GitHub

Proposal  by: @namhihi237
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1695041832175819
Proposal
Please re-state the problem that we are trying to solve in this issue.
The cursor is at the beginning when opening the edit description page
What is the root cause of that problem?
This issue comes from PR
We are allowing multiple description lines here
But we only have the focus logic on the input
https://github.com/Expensify/App/blob/9b302c980f4dcaba08d113f47d4852dc121c7e4e/src/pages/EditRequestDescriptionPage.js#L30
What changes do you think we should make in order to solve the problem?
We should update the logic focus using focusAndUpdateMultilineInputRange
onEntryTransitionEnd={() => focusAndUpdateMultilineInputRange(descriptionInputRef.current)}

What alternative solutions did you explore? (Optional)
N/A

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

I agree with @namhihi237  this is the same solution used in MoneyRequestDescriptionPage.
cc @burczu

That makes sense to me. I'm going close this in favor of https://github.com/Expensify/App/issues/21654. Thanks y'all.


Provide WinSW Service Manager

91bd9d0 Provide the WinSW service manager
WinSW is a useful tool that can wrap any application as a Windows service; it provides the
boilerplate code for interacting with the service infrastructure on Windows. You define a
configuration for your application service in XML, then use WinSW, along with your configuration, as
a service controller.
The full specification for the service configuration can be found here:
https://github.com/winsw/winsw/blob/v3/samples/complete.xml
In this initial implementation, we provide support for most of the available elements, with the
exception of:

serviceaccount
startarguments (I don't know what the difference is between that and 'arguments')
workingdirectory
logpath and log
env
download
extensions

Support for workingdirectory and env will follow in subsequent commits; these fields can be added to
the generic ServiceInstallCtx since they are common options on all platforms.
Most of the code here deals with building the configuration file. This code was written as a
separate function so that the different options could be unit tested. There is an integration/system
test in a similar fashion to the sc manager.

e1844e2 Extend ServiceInstallCtx with new options
It is very common to define a working directory for a service process and a list of environment
variables to pass to the process when it runs. The ServiceInstallCtx is extended for this because
it applies to most service managers.
In this particular case, three of the managers have been extended to support the variables: Systemd,
Launchd and WinSW. The Windows sc.exe service manager does not support specifying either. The
other two unix-based service managers might, but I am not familiar with those at the present time.
It should be easy enough to extend them with a further PR.

@jacderida gave it a skim and it all looks fine to me. 😄 Would you mind adding an update to the changelog? After that, I can merge this in.

@jacderida gave it a skim and it all looks fine to me. 😄 Would you mind adding an update to the changelog? After that, I can merge this in.

Thanks.
I should have remembered to do that this time! I've now pushed an extra commit with the CHANGELOG update.

Hey there. Do you guys have an ETA for when this will be released?

@valtyr it's released now as version 0.5.0.

Amazing! Thank you so much. I found this library today and it's perfect for my use case, these changes make it even better!


Fixed distributeShardsLike bug in creating collections. numberOfShard…

numberOfShards and replicationFactor are optional with distributeShardsLike but must not conflict with prototype collections figures.

@kvahed build failed:

LGTM


Proposal - Add lifecycle hooks

This is a sketch of how lifecycle hooks might work.
When various operations (e.g. add/remove) are called on the store, listeners are notified e.g.
var listener = Ember.Object.extend(Ember.Evented, {
    beforeAdd: function(type, properties){
        // ...
    }.on("beforeAdd")

    afterAdd: function(type, properties, newRecord){
        // ...
    }.on("afterAdd"),

    addRejected: function(type, properties, error){
        // ...
    }.on("addRejected")
});

var ListenersStore = Store.extend({
    listeners: [listener]
});

var store = ListenersStore.create(...);

store.add('user', userProperties); // triggers beforeAdd, afterAdd or addRejected on error

For each operation on store for which listeners are enabled three events may be fired e.g. beforeAdd, afterAdd, addRejected . The parameters match the signature for the method on the store with the exception that the after hook includes the result and the rejected hook includes the error.
Things to consider:

Which store methods should be included - probably add, remove, addLink, removeLink
How should listeners be registered? Perhaps they should be stored in project_root/orbit-listeners
Should listeners be registered in ember's container to allow injection of services?

Superceded by https://github.com/orbitjs/ember-orbit/pull/73


[#4558] Missing AgentId

Codecov Report

Merging #5789 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #5789      +/-   ##
==========================================
- Coverage   40.67%   40.67%   -0.01%
==========================================
  Files        2924     2924
  Lines       87867    87883      +16
  Branches    11561    11569       +8
==========================================
+ Hits        35743    35745       +2
- Misses      49029    49044      +15
+ Partials     3095     3094       -1

Impacted Files
Coverage Δ

...inpoint/common/server/bo/grpc/GrpcSpanFactory.java
3.04% <0%> (-0.33%)
:arrow_down:

...p/pinpoint/rpc/client/WriteFailFutureListener.java
56.25% <0%> (-18.75%)
:arrow_down:

.../profiler/sender/StandbySpanStreamDataStorage.java
72.88% <0%> (-3.39%)
:arrow_down:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
65% <0%> (-1.43%)
:arrow_down:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
85.36% <0%> (+2.43%)
:arrow_up:

...rc/main/java/com/navercorp/pinpoint/test/Item.java
70% <0%> (+3.33%)
:arrow_up:

...ofiler/sender/StandbySpanStreamDataSendWorker.java
85.07% <0%> (+4.47%)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
100% <0%> (+10%)
:arrow_up:

Continue to review full report at Codecov.

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


MockFileSystem.Directory.CreateDirectory throws IoException when directory exists and argument has trailing slash

MockFileSystem.Directory.CreateDirectory throws an IoException if the directory already exists and the argument to CreateDirectory() contains a trailing slash.
The following works correctly:
var fs = new MockFileSystem();
fs.AddDirectory(@"C:\test\"); // Trailing slash here doesn't matter
fs.Directory.CreateDirectory(@"C:\test"); // No trailing slash works correctly

The following throws an IOException:
var fs = new MockFileSystem();
fs.AddDirectory(@"C:\test\"); // Trailing slash here doesn't matter
fs.Directory.CreateDirectory(@"C:\test\"); // Trailing slash here causes error

System.IO.IOException : Cannot create "C:\test\" because a file or directory with the same name already exists.
   at System.IO.Abstractions.TestingHelpers.MockDirectory.CreateDirectory(String path, DirectorySecurity directorySecurity)
   at System.IO.Abstractions.TestingHelpers.MockDirectory.CreateDirectory(String path)

The correct behaviour is silently ignoring existing directories, like System.Io.Directory.CreateDirectory() does (documented behavior).

Thanks for reporting! Can you share a pull request that fixes this?

Done. Added tests for the bug as well as for checking that return value is not null, as per MSDN documentation:

Return Value
Type: System.IO.DirectoryInfo
An object that represents the directory at the specified path. This object is returned regardless of whether a directory at the specified path already exists.


BUG?: GitLabApiClient.Models.Branches.Requests.ProtectBranchRequest yields exception

Trying to create and branch filters (in this case, all permission levels set to maintainer access level) yields an exception:
GitLabApiClient.GitLabException: {"error":"name is missing, push_access_level is invalid, push_access_level does not have a valid value, merge_access_level is invalid, merge_access_level does not have a valid value"}

I'm seeing the same thing:
                await gitLabClient.Branches.ProtectBranchAsync(
                    projectId,
                    new ProtectBranchRequest(
                        branch.Name,
                        pushAccessLevel: ProtectedRefAccessLevels.NO_ACCESS,
                        mergeAccessLevel: ProtectedRefAccessLevels.DEVELOPER_ACCESS,
                        unprotectAccessLevel: ProtectedRefAccessLevels.DEVELOPER_ACCESS));

GitLabApiClient.GitLabException: {"error":"name is missing, push_access_level is invalid, push_access_level does not have a valid value, merge_access_level is invalid, merge_access_level does not have a valid value, unprotect_access_level is invalid, unprotect_access_level does not have a valid value"}
   at GitLabApiClient.Internal.Http.GitLabApiRequestor.EnsureSuccessStatusCode(HttpResponseMessage responseMessage)
   at GitLabApiClient.Internal.Http.GitLabApiRequestor.Post[T](String url, Object data)
   at GitLabApiClient.BranchClient.ProtectBranchAsync(ProjectId projectId, ProtectBranchRequest request)


Add the ability to put extra custom items in the column menu dropdown

I'm interested in seeing a feature that accomplishes something similar to this ui-grid feature: http://ui-grid.info/docs/#/tutorial/303_customizing_column_menu

I agree. This will come at some point. I will take a look at ui-grid, but my implementation will be different (better??)

FWIW I was able to use existing APIs meant for custom column filters to stick the menu elements I need in the dropdowns in getGui. It might be nice to have a wrapper with options that go in colDefs for clickable menu items, but my current implementation using the existing API works just fine and isn't too messy.

Yes I did think of that solution, but didn't share it, as it's not very
clean, and you can't use the built in filters then. My goal, as you
suggest, is have another method alongside getGui that returns back either
menu options, or HTML to display (similar to how the cell renderers return
values).
On 15 April 2015 at 21:59, Mike<EMAIL_ADDRESS>wrote:

FWIW I was able to use existing APIs meant for custom column filters to
stick the menu elements I need in the dropdowns in getGui. It might be
nice to have a wrapper with options that go in colDefs for clickable menu
items, but my current implementation using the existing API works just fine
and isn't too messy.
—
Reply to this email directly or view it on GitHub
https://github.com/ceolter/angular-grid/issues/47#issuecomment-93567917.

--
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Statements and opinions expressed in this e-mail may not
represent those of the sender. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender immediately and delete
the material from any computer.

@ceolter Can you share your solution?

customising the column menu is not possible. the above thread is over 1 year old!
it's an enterprise feature only though:
http://localhost/javascript-grid-column-menu/index.php

Not sure how I missed the the documentation. Thanks!