String.toLowerCase and toUpperCase does not work with current locale

It seems like in SJS, the toUpperCase and toLowerCase are using JS's corresponding functions: (from RuntimeString.scala):
    def toLowerCase(): String = js.native
    def toUpperCase(): String = js.native

In JVM, those operations are working using the current locale. The similar behaviour in JS would correspond to using  these:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/toLocaleLowerCase
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/toLocaleUpperCase

Please ping the scala-java-time project, because we use the current behavior. It's no big deal to move to calling JS' "real" toLowerCase instead, but we need to know it so we can fix it.

this seems to be pretty new (at least to me):

Note: ECMAScript Internationalization API, implemented with Firefox 29, added the locales argument to the Number.toLocaleString() method. If the argument is undefined, this method returns localized digits specified by the OS

(from : Number.toLocaleString)
moreover it seems they are moving implementing this specification as mentioned here .
It does look promising!

Just to mention:
https://tc39.github.io/ecma402/#sec-defaultlocale

@andreaTP that is great, but unfortunately as it is not possible to polyfill those features, it will take a long time before we can depend on them being available.
@sjrd is it possible somehow for an external dependency (like scala-java-locales) that knows the right locale to override these methods (as they are in RuntimeString)?

It is unfortunately not possible to override methods defined in RuntimeString. I am prenuptial concrete proposals to include the necessary hooks in the library.

I will close this as won't fix, until Scala.js as a whole has a clearer view on locale.

See #1773 for overall locale tracking.


Blade Sintax Error Unexpected: End of File Expected: T_BLADE_COMMENT, T_BLADE_STOP

From #12, I have that problem too, i don't know how to avoid it

@section('content')

@endsection

@section('content')

@endsection

Blade Sintax Error Unexpected: End of File Expected: T_BLADE_COMMENT, T_BLADE_STOP
when after @ there is a especial character or a space it is not a blade directive

Hi I've did some updates. I hope this issue is fixed.
https://github.com/haidubogdan/netbeans-php-blade-plugin/releases/tag/v.<IP_ADDRESS>-beta
This parse error is due to LESS parser, I think it's not directly related with the plugin.
@section('content')

@endsection

This parse error for the snippet bellow is due to LESS parser
@section('content')

@endsection

If you disable LESS parser,  Blade Sintax Error pop up, but it doesn't matter to me, thanks


QA value meaning

Can some one explain this value?
<ID=QA,Number=A,Type=Integer,Description="Alternate allele quality sum in phred">

Which quality score is actually summed up?
Thanks! And thanks for this great tool!

This sums the base qualities of the alternate allele observations. It's in
phred space.
On Wed, Feb 5, 2020, 17:02 Marten<EMAIL_ADDRESS>wrote:

Can some one explain this value?
<ID=QA,Number=A,Type=Integer,Description="Alternate allele quality sum in phred">
Which quality score is actually summed up?
Thanks! And thanks for this great tool!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ekg/freebayes/issues/594?email_source=notifications&email_token=AABDQEM33DNI46Y5HEOUEXDRBLPI3A5CNFSM4KQNU4NKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ILICMZA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABDQEITBAYDFP4UUGV7YMDRBLPI3ANCNFSM4KQNU4NA
.

Thanks for the reply


chore: remove pnpm devDependency

Description
found that during debugging an issue in vite-ecosystem-ci and havn't seen any usage of it.
Having it as a local devDependency causes it to be used over global pnpm after the global was used for the initial install.
This can cause mismatches.
If we want to enforce a certain pnpm version, using engines.pnpm alongside the already set packageManager field would be a better option imho.
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

My understanding is that this exists to lock the version of pnpm used here.
https://github.com/vitejs/vite/blob/c56b95448b43f59d2b93394e1a5099bcc7879a16/netlify.toml#L6
So I think we can remove this when we can revert #11477.

pinning pnpm that way comes with the drawbacks mentioned above and seeing that the current value is ^7.27.0 which isn't really pinning, i think it would be better to use npx pnpm@version ... in that script if we have that need again in the future

Ah, that makes sense.


"No Cloud Variables Found"

I am testing the demo example found in the tutorial and I'm getting the error:
"scratchcloud.errors.MissingCloudVariable: No Cloud Variables Found!"
I'm using the provided example project as well.
I'm not sure but could it be related to me not seeing 'cookies' popping up in the headers for the WebSocket in chrome dev tools?

I haven't updated this library in a good while, and in that time, scratch changes how it handles cloud handshakes. Before, when connecting to a scratch project, scratch would guarantee a "handshake" with the client object containing a list of all of the cloud variables. If you connected to a project without any cloud variables, then scratch would tell you that the project you're connecting to doesn't have any variables.
Since I've been gone, scratch changed this system to be very unreliable. I haven't had the time to test it, but it seems like the influx of people using 3rd-party cloud librarys (like scratchcloud and scratchattach) caused scratch to change how cloud variables are handled—namely scratch doesn't always let the connected clients know what cloud variables exist.
You can fix this by passing ignore_missing_variables=True when creating a CloudClient.

from scratchcloud import CloudClient

client = CloudClient(username='username', project_id='12345678', ignore_missing_variables=True)

Hope this helps. Let me know if you have further questions!


Error when migrating extension to 0.6.0

This is an extract from our current config for our deployment:
resource "ec_deployment" "example-name" {
  name                   = "example-name"
  alias                  = "example-name-${var.environment}"
  region                 = "aws-eu-central-1"
  version                = "8.7.0"
  deployment_template_id = "aws-io-optimized-v3"

  elasticsearch = {
    hot = {
      autoscaling = {}
      id         = "hot_content"
      size       = lookup(var.config, var.environment).es_node_ram_size
      zone_count = lookup(var.config, var.environment).zone_count
    }
    warm = {
      autoscaling = {}
    }
    cold = {
      autoscaling = {}
    }
    frozen = {
      autoscaling = {}
    }

    extension {
      name    = ec_deployment_extension.example-extension.name
      type    = "bundle"
      version = "*"
      url     = ec_deployment_extension.example-extension.url
    }
  }

  kibana = {
    topology = {
      size       = "1g"
      zone_count = 1
    }
  }

  traffic_filter = [
    ec_deployment_traffic_filter.aws-vpc-endpoint-filter.id,
    ec_deployment_traffic_filter.vpn-ip-filter.id
  ]

}

locals {
  file_path = "analysis.zip"
}

resource "ec_deployment_extension" "example-extension" {
  name           = "example"
  description    = "bundle for example"
  version        = "*"
  extension_type = "bundle"
  file_path      = local.file_path
  file_hash      = filebase64sha256(local.file_path)
}

When I apply this deployment I get the following error:
Inappropriate value for attribute "elasticsearch": attribute "extension": set of object required.

When I then change the extension block to this (like it is documented here):
extension = { # note the equals sign here, only difference
  name    = ec_deployment_extension.mcr-and-synonyms-extension.name
  type    = "bundle"
  version = "*"
  url     = ec_deployment_extension.mcr-and-synonyms-extension.url
}

I get the following error:
Expected an equals sign ("=") to mark the beginning of the attribute value.

So how do we now configure an extension correctly? Also please update your documentation. Thank you!

Sorry for the confusion here. You should be able to specify a set of extensions, for example:
extension = [{ # note the equals sign here, only difference
  name    = ec_deployment_extension.mcr-and-synonyms-extension.name
  type    = "bundle"
  version = "*"
  url     = ec_deployment_extension.mcr-and-synonyms-extension.url
}]

I've updated the docs and examples in https://github.com/elastic/terraform-provider-ec/pull/634

Thanks @tobio! That worked great.


Fix typo in incremental tasks user guide documentation

Signed-off-by: Mike Kobit<EMAIL_ADDRESS>Context
Typo in docs
Contributor Checklist

[ ] Review Contribution Guidelines
[ ] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[ ] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[ ] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Thanks for the fix, @mkobit!


Missing nuget dependence on nuget version.

Describe the bug
When you install with nuget, the functions throw a assembly missing exception, in exception.innerException.innerException.
Instaling the last version of System.ComponentModel.Annotations nuget the exception completly disappear
Your code piece

        Dim Gpt3 = New OpenAIService(New OpenAiOptions() With {
            .ApiKey = GetSetting(Application.ProductName, "Config", "APIKeyBx", "")
        })

        Dim GerarResult = Gpt3.ChatCompletion.CreateCompletion(New ChatCompletionCreateRequest() With {
            .Messages = {ChatMessage.FromUser(Prompt)},
            .Temperature = 0.7,
            .MaxTokens = 1000,
            .Model = Models.Gpt_3_5_Turbo
        })

        While Not GerarResult.IsCompleted
            EsperaMS(16)
        End While

        Try
            result = If(GerarResult.Result.Successful, GerarResult.Result.Choices(0).Message.Content, $"Erro: {If(GerarResult.Result.Error.Message, "Erro desconhecido")}")
        Catch ex As Exception
            result = "ERRO_ERRO_DESCONHECIDO_CHAT_GPT"
        End Try

Result
Result completed, but with exception and "not computed yet" state
Expected behavior
Expected to retuns the GPT response.
Desktop (please complete the following information):

OS: Windows 10
Language VB.NET
Version 8.5.0

Did it start with 8.5.0? Were there such problems in previous versions?

Nop, started before the 8.0.0.

Please try again with the latest version and reopen this issue if the bug still exists.


Release for cache@v4 change

Any chance you can release v2 of this action, to include the already merged actions/cache@v4
Thanks

Hey @andrewnicols, Thank you for raising this issue. v1.1 is now available.


PowerShell 7.2-Preview.6 bombs in Windows Terminal

I Downloaded and finished installing PowerShell 7.2-Preview.6 bombs in Windows Terminal
Steps to reproduce
I Downloaded and finished installing PowerShell 7.2-Preview.6 bombs in Windows Terminal.
PowerShell 7.2.0-preview.6
Copyright (c) Microsoft Corporation.

https://aka.ms/powershell
Type 'help' to get help.

PS C:\Users\max_t>
Oops, something went wrong.
Please report this bug with ALL the details below, including both the 'Environment' and 'Exception' sections.
Please report on GitHub: https://github.com/PowerShell/PSReadLine/issues/new?template=Bug_Report.md
Thank you!

### Environment
PSReadLine: 2.2.0-beta2
PowerShell: 7.2.0-preview.6
OS: Microsoft Windows 10.0.21390
BufferWidth: 120
BufferHeight: 30

Last 0 Keys

### Exception

System.TypeLoadException: Could not load type 'System.Management.Automation.Subsystem.PredictionResult' from assembly 'Microsoft.PowerShell.PSReadLine.Polyfiller, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
   at Microsoft.PowerShell.PSConsoleReadLine.PredictionViewBase.Reset()
   at Microsoft.PowerShell.PSConsoleReadLine.PredictionInlineView.Reset() in Microsoft.PowerShell.PSReadLine2.dll:token 0x60004ca+0x0
   at Microsoft.PowerShell.PSConsoleReadLine.Prediction.Reset() in Microsoft.PowerShell.PSReadLine2.dll:token 0x600049b+0x7
   at Microsoft.PowerShell.PSConsoleReadLine.Initialize(Runspace runspace, EngineIntrinsics engineIntrinsics) in Microsoft.PowerShell.PSReadLine2.dll:token 0x6000101+0x118
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics, CancellationToken cancellationToken) in Microsoft.PowerShell.PSReadLine2.dll:token 0x60000fa+0x60

Expected behavior
To work after intallation.

Actual behavior
Booms after the PowerShell logo comes up.

Environment data
PSReadLine: 2.2.0-beta2
PowerShell: 7.2.0-preview.6
OS: Microsoft Windows 10.0.21390
BufferWidth: 120
BufferHeight: 30

See #2 in the Note: section at the top of the Release Notes. This is a known issue that will be fixed when PSRL 2.2.0-beta3 drops.


Fix some metadata including ms assetid values made unique across pages

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Docs/Overview/additional-information.md
:white_check_mark:Succeeded

Docs/Overview/certificates.md
:white_check_mark:Succeeded

Docs/Overview/client-playready-services.md
:white_check_mark:Succeeded

Docs/Overview/client-server-protocol.md
:white_check_mark:Succeeded

Docs/Overview/communication-protocols.md
:white_check_mark:Succeeded

Docs/Overview/compliance-and-robustness-rules.md
:white_check_mark:Succeeded

Docs/Overview/developing-applications.md
:white_check_mark:Succeeded

Docs/Overview/developing-packager.md
:white_check_mark:Succeeded

Docs/Overview/domain-server.md
:white_check_mark:Succeeded

Docs/Overview/license-server.md
:white_check_mark:Succeeded

Docs/Overview/license-to-use-playready.md
:white_check_mark:Succeeded

Docs/Overview/playready-on-windows.md
:white_check_mark:Succeeded

Docs/Overview/playready-on-xbox.md
:white_check_mark:Succeeded

Docs/Overview/secure-clock-services.md
:white_check_mark:Succeeded

Docs/Overview/server-on-azure.md
:white_check_mark:Succeeded

Docs/Overview/servers.md
:white_check_mark:Succeeded

Docs/Overview/test-server.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Please export types for your components, custom hooks, etc.

Is your feature request related to a problem? Please describe.
This library is quite difficult to use sicne it's not exposing any type:

That means I need to check examples to know how to use the custom hooks and components:

This has become a bigger problem now that I'm getting an error related to the payment methods, and I don't know if it's a problem with the lib or the problem is that I'm not setting the right prop paymentMethods in AdyenCheckout component.
I'm setting the response I get from my backend which looks like this:
[
  {
    "brands": [
      "amex",
      "cup",
      "diners",
      "discover",
      "jcb",
      "maestro",
      "mc",
      "visa"
    ],
    "name": "Credit Card",
    "type": "scheme"
  }
]

but I get this error when I run start('scheme'):
TypeError: undefined is not an object (evaluating 'paymentMethods.paymentMethods.find')

Describe the solution you'd like
The best solution would be to write this lib in TS, so types exported are 100% accurate
Describe alternatives you've considered
Another alternative would exposing .d.ts files that accurately describe the types of the lib

Hey @codeserk
Thanks for reaching out!
There are JsDoc types, but unfortunately, those types are not mapped correctly inside the final package.
We are working on fix for this..

error related to the payment methods

Indeed, your paymentMethods object is incorrect and this could have been avoided if JsDocs were exposed.
Try:
{
  "paymentMethods": [
    {
      "brands": [ ... ],
      "name": "Credit Card",
      "type": "scheme"
    }
  ]
}

FYI one can provide whole json response from \paymentMethods API to AdyenCheckout. The start('scheme') will cherry pick CardComponent out of it.

Hello @descorp
Thanks for the quick reply, the problem was indeed that I was setting paymentMethods field inside the response from adyen (instead of setting the whole response from adyen), so 💥 .
I've been able to make my first scheme payment and works great! :)
Looking forward to seeing types in a newer version.

Our current d.ts file in case it helps anyone:
// @adyen/react-native.d.ts

declare module '@adyen/react-native' {
  import { FunctionComponent, ReactNode } from 'react'
  import { NativeModule } from 'react-native'
  import '@adyen/react-native'

  export enum ErrorCode {
    /** Payment was canceled by shopper. */
    Canceled = 'canceledByShopper',
    /** Payment method not supported on current platform.. */
    NotSupported = 'notSupported',
    /** Missing or invalid clientKey in configuration. */
    NoClientKey = 'noClientKey',
    /** Missing or invalid amount or country code in configuration. */
    NoPayment = 'noPayment',
    /** Can not parse paymentMethods or the list is empty. */
    InvalidPaymentMethods = 'invalidPaymentMethods',
    /** Can not parse action. */
    InvalidAction = 'invalidAction',
    /** Can not find selected payment method type in provided list. */
    NoPaymentMethod = 'noPaymentMethod',
  }

  export enum Environment {
    Test = 'test',
    Europe = 'live-eu',
    US = 'live-us',
    Australia = 'live-au',
    AsiaPacificSouthEast = 'live-apse',
    India = 'live-in',
  }

  export enum ResultCode {
    /** The payment has been successfully authenticated with 3D Secure. */
    AuthenticationFinished = 'AuthenticationFinished',
    /** The transaction does not require 3D Secure authentication, for example, the issuing bank does not require authentication or the transaction is out of scope. */
    AuthenticationNotRequired = 'AuthenticationNotRequired',
    /** The payment was successfully authorised. */
    Authorised = 'Authorised',
    /** The payment was cancelled (by either the shopper or your own system) before processing was completed. */
    Cancelled = 'Cancelled',
    /** The issuer requires further shopper interaction before the payment can be authenticated. Returned for 3D Secure 2 transactions. */
    ChallengeShopper = 'ChallengeShopper',
    /** There was an error when the payment was being processed. You'll receive a refusalReason in the same response, indicating the cause of the error. */
    Error = 'Error',
    /** The issuer requires the shopper's device fingerprint before the payment can be authenticated. Returned for 3D Secure 2 transactions. */
    IdentifyShopper = 'IdentifyShopper',
    /** It's not possible to obtain the final status of the payment at this time. This is common for payments with an asynchronous flow, such as Boleto or iDEAL. */
    Pending = 'Pending',
    /** Present the voucher or the QR code to the shopper. */
    PresentToShopper = 'PresentToShopper',
    /** This is part of the standard payment flow for methods such as SEPA Direct Debit, where it can take some time before the final status of the payment is known. */
    Received = 'Received',
    /** The shopper needs to be redirected to an external web page or app to complete the payment. */
    RedirectShopper = 'RedirectShopper',
    /** The payment was refused. You'll receive a `refusalReason` in the same response that indicates why it was refused. */
    Refused = 'Refused',
  }

  export type PaymentMethod = {
    /** The unique payment method code. */
    type: string
    /** The displayable name of this payment method. */
    name: string
  }

  /**
   * Initiate payment flow for selected payment method.
   * @param typeName Payment method name. Use "dropin" or `type` name of a selected payment method.
   */
  type StartFunction = (typeName: string) => void

  /** JSON response from Adyen API `\paymentMethods`. */
  export type PaymentMethodsResponse = {
    storedPaymentMethods: PaymentMethod[]
    paymentMethods: PaymentMethod[]
  }

  type AdyenCheckoutContextState = {
    start: StartFunction
    paymentMethods: PaymentMethodsResponse
  }

  export const useAdyenCheckout: () => AdyenCheckoutContextState

  type AdyenActionComponent = {
    /** handle Handles action from Adyen API `\payments` response. */
    handle: (action: unknown) => void
  }

  type AdyenComponent = {
    /** Show component above current screen. */
    open: (
      paymentMethods: PaymentMethodsResponse,
      config: AdyenCheckoutConfig,
    ) => void
    /** Dismiss component from screen. */
    hide: (success: boolean, alert: { message?: string | undefined }) => void
  }

  /** Universal interface for Adyen Native payment component. */
  export type AdyenNativeComponent = NativeModule &
    AdyenActionComponent &
    AdyenComponent

  /**
   * @param data Payment details collected by component. Your server should use it to make the Adyen API `/payments` request.
   * @param nativeComponent Native component that performing payment.
   */
  type OnSubmitFunction = (
    data: AdyenPaymentPayload, // Added
    nativeComponent: AdyenNativeComponent,
  ) => void

  /**
   * @param data Additional payment challenge details.
   * @param nativeComponent
   */
  type OnAdditionalDetailsFunction = (
    data: AdyenPaymentPayload, // Added
    nativeComponent: AdyenNativeComponent,
  ) => void

  type OnCompletedFunction = (nativeComponent: AdyenNativeComponent) => void

  export type AdyenPaymentError = { message: string; errorCode: string }

  /**
   * @param error Reason for payment termination.
   * @param nativeComponent Native component that performing payment.
   */
  type OnErrorFunction = (
    error: AdyenPaymentError,
    nativeComponent: AdyenNativeComponent,
  ) => void

  export type AdyenAmount = {
    currency: string
    value: number
  }

  export type AdyenCheckoutConfig = {
    environment: Environment
    clientKey: string
    /** Amount to be displayed on the Pay Button. It expects an object with the minor units value and currency properties. For example, { value: 1000, currency: 'USD' } is 10$. For card pre-authorisation set amount to 0 (zero). */
    amount: AdyenAmount
    /** The shopper's country code in ISO 3166-1 alpha-2 format. Example: "NL" or "US". */
    countryCode: string
    merchantAccount: string
    shopperLocale?: string
    /** For iOS, this is the URL to your app, where the shopper should return, after a redirection. Maximum of 1024 characters. For more information on setting a custom URL scheme for your app, read the Apple Developer documentation. For Android, this value is automatically overridden by AdyenCheckout. */
    returnUrl?: string
    channel?: 'iOS' | 'Android'
    dropin?: {
      skipListWhenSinglePaymentMethod?: boolean
      showPreselectedStoredPaymentMethod?: boolean
    }
    card?: {
      holderNameRequired?: boolean
      addressVisibility?: string
      showStorePaymentField?: boolean
      hideCvcStoredCard?: boolean
      hideCvc?: boolean
    }
    applepay?: {
      merchantID: string
      merchantName: string
      allowOnboarding?: boolean
    }
  }

  type AdyenCheckoutProps = {
    config: AdyenCheckoutConfig
    /** JSON response from Adyen API `\paymentMethods`. */
    paymentMethods?: PaymentMethodsResponse
    /** Event callback, called when the shopper selects the Pay button and payment details are valid. */
    onSubmit: OnSubmitFunction
    /** Event callback, called when a payment method requires more details, for example for native 3D Secure 2, or native QR code payment methods. */
    onAdditionalDetails?: OnAdditionalDetailsFunction
    /** Event callback, called when a shopper finishes the flow (Voucher payments only). */
    onComplete?: OnCompletedFunction
    /** Event callback, called when payment about to be terminate. */
    onError?: OnErrorFunction
    /** Inline elements. */
    children?: ReactNode
  }

  export const AdyenCheckout: FunctionComponent<AdyenCheckoutProps>

  // Added
  export type AdyenPaymentResult = {
    resultCode: ResultCode
    paymentMethod: PaymentMethod
    action?: unknown
  }

  // Added
  export type AdyenPaymentPayload = {
    paymentMethod: {
      type: string
    } & (
      | {}
      | {
          encryptedExpiryMonth: string
          type: 'scheme'
          threeDS2SdkVersion: string
          brand: string
          encryptedCardNumber: string
          encryptedSecurityCode: string
          encryptedExpiryYear: string
        }
    )
    browserInfo?: {
      userAgent?: string
    }
    storePaymentMethod: boolean
    returnUrl?: string
  }
}

Hey @jesperjohansson @codeserk
We have PR for Typescript
You can try it out with
"dependencies": {
    "@adyen/react-native": "Adyen/adyen-react-native#type_script",
}

Typescript support released in RC.2


Compatibility with Render.com

Bug description

Deploying a FastAPI application to render.com will not work. Minimal repo can be found here: https://github.com/RobertCraigie/prisma-python-render
How to reproduce

Setup referenced repo on render.com, this error is encountered:
Mar 25 08:00:07 PM  INFO:     Waiting for application startup.
Mar 25 08:00:07 PM  ERROR:    Traceback (most recent call last):
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/starlette/routing.py", line 677, in lifespan
Mar 25 08:00:07 PM      async with self.lifespan_context(app) as maybe_state:
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/starlette/routing.py", line 566, in __aenter__
Mar 25 08:00:07 PM      await self._router.startup()
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/starlette/routing.py", line 654, in startup
Mar 25 08:00:07 PM      await handler()
Mar 25 08:00:07 PM    File "/opt/render/project/src/main.py", line 19, in startup
Mar 25 08:00:07 PM      await prisma.connect()
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/client.py", line 239, in connect
Mar 25 08:00:07 PM      datasources=datasources,
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/engine/query.py", line 128, in connect
Mar 25 08:00:07 PM      self.file = file = self._ensure_file()
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/engine/query.py", line 116, in _ensure_file
Mar 25 08:00:07 PM      return utils.ensure(BINARY_PATHS.query_engine)
Mar 25 08:00:07 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/engine/utils.py", line 113, in ensure
Mar 25 08:00:07 PM      + 'Try running prisma py fetch'
Mar 25 08:00:07 PM  prisma.engine.errors.BinaryNotFoundError: Expected /opt/render/project/src/prisma-query-engine-debian-openssl-1.1.x, /opt/render/.cache/prisma-python/binaries/4.11.0/8fde8fef4033376662cad983758335009d522acb/prisma-query-engine-debian-openssl-1.1.x or /opt/render/.cache/prisma-python/binaries/4.11.0/8fde8fef4033376662cad983758335009d522acb/node_modules/prisma/query-engine-debian-openssl-1.1.x to exist but none were found.
Mar 25 08:00:07 PM  Try running prisma py fetch
Mar 25 08:00:07 PM
Mar 25 08:00:07 PM  ERROR:    Application startup failed. Exiting.
Mar 25 08:00:44 PM  ==> Starting service with 'PRISMA_PY_DBEUG=1 uvicorn main:app --log-level debug'
Mar 25 08:00:51 PM  INFO:     Started server process [53]
Mar 25 08:00:51 PM  INFO:     Waiting for application startup.
Mar 25 08:00:51 PM  ERROR:    Traceback (most recent call last):
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/starlette/routing.py", line 677, in lifespan
Mar 25 08:00:51 PM      async with self.lifespan_context(app) as maybe_state:
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/starlette/routing.py", line 566, in __aenter__
Mar 25 08:00:51 PM      await self._router.startup()
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/starlette/routing.py", line 654, in startup
Mar 25 08:00:51 PM      await handler()
Mar 25 08:00:51 PM    File "/opt/render/project/src/main.py", line 19, in startup
Mar 25 08:00:51 PM      await prisma.connect()
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/client.py", line 239, in connect
Mar 25 08:00:51 PM      datasources=datasources,
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/engine/query.py", line 128, in connect
Mar 25 08:00:51 PM      self.file = file = self._ensure_file()
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/engine/query.py", line 116, in _ensure_file
Mar 25 08:00:51 PM      return utils.ensure(BINARY_PATHS.query_engine)
Mar 25 08:00:51 PM    File "/opt/render/project/src/.venv/lib/python3.7/site-packages/prisma/engine/utils.py", line 113, in ensure
Mar 25 08:00:51 PM      + 'Try running prisma py fetch'
Mar 25 08:00:51 PM  prisma.engine.errors.BinaryNotFoundError: Expected /opt/render/project/src/prisma-query-engine-debian-openssl-1.1.x, /opt/render/.cache/prisma-python/binaries/4.11.0/8fde8fef4033376662cad983758335009d522acb/prisma-query-engine-debian-openssl-1.1.x or /opt/render/.cache/prisma-python/binaries/4.11.0/8fde8fef4033376662cad983758335009d522acb/node_modules/prisma/query-engine-debian-openssl-1.1.x to exist but none were found.
Mar 25 08:00:51 PM  Try running prisma py fetch
Mar 25 08:00:51 PM
Mar 25 08:00:51 PM  ERROR:    Application startup failed. Exiting.

The last path referenced in that error message does exist and can be executed.
Expected behavior

Should work out of the box.

Solution that worked for me was to change the default location where the binaries are cached.
CONTEXT: In render the default location is /opt/render/.cache/prisma-python/binaries/. Unfortunatley the .cache directory never gets created during the build. My guess is because in Render special permissions are needed to create folders/files that start with "." such as ".cache".
SOLUTION: create a custom folder to store the binaries and set the path to the env variable PRISMA_BINARY_CACHE_DIR
e.g. PRISMA_BINARY_CACHE_DIR=/opt/render/project/src/.binaries. /opt/render/project/src/ is the root location of your project code. The .binaries folder was manually created.
(see the Binary Cache Directory section at https://prisma-client-py.readthedocs.io/en/stable/reference/config/#config-options)


Heatmap options...can this one be added to line above?

When creating the heatmap object you set opts and then set another opts. Can this be added to the line above???
https://github.com/cal-adapt/climakitae/blob/984d67e7950f333fc019b7b1c523fbe931b7b641/climakitae/tmy.py#L371

Testing now, yes! Will push clean now.


README.md wrongly states that Uri implements PSR-7 UriInterface

Related to #117
It is said in README.md that Uri does implement PSR-7 UriInterface: https://github.com/thephpleague/uri/blame/e8ae03fdbfde795f9ef8c843c2fad284a787458d/README.md#L49
This is actually wrong, so I think this info should be deleted from the README.

@someniatko please read carefully the text and the documentation this is not the case


Type 'Token' is missing the following properties from type 'Token': isNative, isToken, wrapped on computePoolAddress

I have this method in a class:
    private tokenClass(chainId: number, address: string, decimals: number): Token {
        return new Token(chainId, address, decimals);
    }

    private async _computePoolAddress(chaindId: number, _tokenA: string, _decimalsA: number, _tokenB: string, _decimalsB: number, fee: number): Promise<any> {
        try {
            const poolAddress = computePoolAddress({
                factoryAddress: this.factoryAddress,
                tokenA: this.tokenClass(chaindId, _tokenA, _decimalsA),
                tokenB: this.tokenClass(chaindId, _tokenB, _decimalsB),
                fee: fee
            })
            return poolAddress
        } catch (error) {
            throw new Error(`${error.message}, for quoteTokenPertToken`)
        }
    }

And i'm getting errors on the properties tokenA and tokenB from that method. It's complaning that the new Token instance i'm creating and using as param is missing properties isNative, isToken, and wrapped.
How to reproduce:
Use these versions in a node project:
  "dependencies": {
    "@uniswap/sdk": "^3.0.3",
    "@uniswap/v3-sdk": "^3.10.0",
  },

Run a class like this:
import { Token } from '@uniswap/sdk';
import { computePoolAddress,  } from **'@uniswap/v3-sdk';

export class WalletService extends {
    constructor(private readonly configService: ConfigService) {
        super()
        this.factoryAddress = configService.get<string>(EnviromentVariablesEnum.POOL_FACTORY_CONTRACT_ADDRES)
    }

    private factoryAddress: string

    private tokenClass(chainId: number, address: string, decimals: number): Token {
        return new Token(chainId, address, decimals);
    }

    private async _computePoolAddress(chaindId: number, _tokenA: string, _decimalsA: number, _tokenB: string, _decimalsB: number, fee: number): Promise<any> {
        try {
            const poolAddress = computePoolAddress({
                factoryAddress: this.factoryAddress,
                tokenA: this.tokenClass(chaindId, _tokenA, _decimalsA),
                tokenB: this.tokenClass(chaindId, _tokenB, _decimalsB),
                fee: fee
            })
            return poolAddress
        } catch (error) {
            throw new Error(`${error.message}, for quoteTokenPertToken`)
        }
    }
}

You need to use @uniswap/v2-sdk instead of @uniswap/sdk. The package you are using is an old version of the v2-sdk that was deprecated when Uniswap v3 was released.


LB Listener protocol docs are worng

For https://www.pulumi.com/docs/reference/pkg/aws/lb/listener/#protocol_python is stated that "The protocol for connections from clients to the load balancer. Valid values are TCP, TLS, UDP, TCP_UDP, HTTP and HTTPS. Defaults to HTTP."
But when trying to use HTTP i get the fllowing error: * error creating ELBv2 Listener: ValidationError: Listener protocol 'HTTP' must be one of 'TLS, TCP, TCP_UDP, UDP'
So I believe that HTTP and HTTPS are not valid values.

Could you confirm you are trying to attach the listener to an ALB and not an NLB?

Yes i was creating an NLB, didn't realize the documentation covered both. Maybe make some kind of separation or notation to be aware of this?

Fixed with https://github.com/pulumi/terraform-provider-aws/pull/60.


⚠ Bofrost.lu has degraded performance

In 632a794, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 806 ms

Resolved: Bofrost.lu performance has improved in 9195e0f after 15 minutes.


Cannot craft leads with colored slime

I'm still deciding whether Coloured Slimeballs should be equivalent to vanilla Slimeballs.


Invalid metric name: 'mqtt.sent.bytes' with latest xk6

Related: https://github.com/pmalhaire/xk6-mqtt/issues/21
Hi, thank you for the extension. I ran into the error in the title after building with the default xk6 build latest --with github.com/pmalhaire/xk6-mqtt. I was able to work around by specifying a commit like xk6 build latest --with github.com/pmalhaire/xk6-mqtt@231ecd388e503ca4a59eb346e03ac8a66011e12e. I see the latest release was created back in July but the commit that fixes the issue was made in November so perhaps it's just a matter of creating a new release.

My fault, I see that you've listed support for v0.43.1 of k6. For posterity I was able to get the extension working with xk6 build v0.45.1 --with github.com/pmalhaire/xk6-mqtt

You are right, I fixed this but I did not do a release

Release created v0.40.0


use wasm-pack-template in the wasm-pack tutorial

@ashleygwilliams should this be moved to the wasm-pack repo?

The wasm-pack tutorial is moved/moving into wasm-pack. Closing this issue.


Add accessibilityId to Compound message

Codecov Report

Merging #556 into master will decrease coverage by 0.06%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #556      +/-   ##
==========================================
- Coverage   59.75%   59.69%   -0.07%
==========================================
  Files          87       87
  Lines        3956     3960       +4
==========================================
  Hits         2364     2364
- Misses       1592     1596       +4

Impacted Files
Coverage Δ

...ems/CompoundMessage/CompoundMessagePresenter.swift
0% <0%> (ø)
:arrow_up:

...poundMessage/CompoundMessagePresenterBuilder.swift
0% <0%> (ø)
: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 8c0d8ed...1cc3482. Read the comment docs.


Route parameter openapi generation is incompatible with 3.0

When using a parameter in a route: @bp.route('/<string:foo_id>')
The openapi.json generated is not compatible with openapi 3.0:
"parameters": [
          {
            "in": "path",
            "name": "foo_id",
            "required": true,
            "type": "string"
          }
        ]

should be:
"parameters": [
          {
            "in": "path",
            "name": "bar_id",
            "required": true,
            "schema": {
                 "type": "string"
            }
          }
        ]

I am not sure if this is a flask-rest-api issue, or something to fix in a dependency… But I would be happy to take  stab at a PR, if pointed in the right direction (I couldn't figure where in blueprint.py that part of the doc was generated).

Ha. What a coincidence! Sorry I wasn't around yesterday: I'll be happy to try it from github now, or confirm it works from the release.

Fix released !


online tool problem

Hello,author
I get 502 Bad Gateway when I try to  visit your online tool web.
After checking my computer's network link,  I still get 502 Bad Gateway.
I have no idea about the case. Is there any solution to that?

Hmmm—the website works for me… This is MIDEL.org?
Brad Erickson
On Mar 19, 2023 at 8:19 AM -0500, wang @.***>, wrote:

Hello,author
I get 502 Bad Gateway when I try to visit your online tool web.
After checking my computer's network link, I still get 502 Bad Gateway.
I have no idea about the case. Is there any solution to that?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Oh,sorry it still don't work since I have used different computers and vpn.
I google the error code :502 Bad Gateway
The reasons may be that  the link of 'Link to the online tool' on https://github.com/mayo-radiology-informatics-lab/mbti need updating,
or the server of  the website has been closed for ip address outside your university

Dear author.
Thanks for making your tool available.
Unfortunately the online tool is not working. Either I got ‘bad gateway’ or  “no interface is running”.
Could you have a look on this issue or sharing you code?
best


Added User-Agent string to AFD Probes doc

AFD uses header - User-Agent: Edge Health Probes , which can help users identify AFD health probes, allow through firewalls, etc. Documenting this information.

@ryanborMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ryanborMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@ktoliver please merge this PR. Thank you!
@ryanborMSFT This should be published soon. Sorry for the delay.


[SR-4116] Implement protocol-associated-type-declaration in lib/Syntax

Previous ID
SR-4116

Radar
None

Original Reporter
@bitjammer

Type
Bug

Additional Detail from JIRA

Votes
0

Component/s
Compiler

Labels
Bug, Syntax

Assignee
@bitjammer

Priority
Medium

md5: cb8260295d828a4e2f80b54f147aee02

libSyntax was removed in #62145 and succeeded by swift-syntax.


Add client-nonce to outgoing private message

resolves #3

Ah meant to commit the last commit to the main branch not this PR, but I guess it's fine.


Response size

Hi @unstabl3 It would be better if you add Page Response Size along with status code

Hi, @jaikishantulswani Thank you for suggesting. I will add this in the next release of recce.

Hi @unstabl3 I think response length switch is ignored

hi, response length only works with -s option.. hit me up on twitter if you
face more issues. i don't check mails daily.
On Thu, Sep 5, 2019 at 3:25 PM Jaikishan Tulswani<EMAIL_ADDRESS>wrote:

Hi @unstabl3 https://github.com/unstabl3 I think response length switch
is ignored
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/unstabl3/recce/issues/1?email_source=notifications&email_token=ALR2VDGZSADAUMLP4WS4HCLQIDJRXA5CNFSM4IK3QW6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD56RJEI#issuecomment-528290961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALR2VDAF7QPPVYAV2AYVH33QIDJRXANCNFSM4IK3QW6A
.


Add support for feature flags

Part of a push to add feature flags to commonly used libraries.

@yakkomajuri This package is just a thin wrapper around the iOS and Android libraries, so if you want to add feature flags here, you need to add them to both mobile libraries first.

Hmm yeah hadn't looked into it when we did sprint planning today. I guess I could write a feature flags layer in JS though as long as I can get the user's distinct ID?

The main reason this library uses some native bindings is to get some basic screen name and whatnot autocapture working. Plus some native apis to get more context ($something in properties).
I guess such a layer for feature flags could be possible.
There is also the much requested feature of expo support https://github.com/PostHog/posthog/issues/1174 (aka pure js react native). This code could be shared between both when the expo plugin gets built.

Done in v2.0.0


Code Completion Plugin: Define Element Pattern for Beam Java SDK

Implemented an Element Pattern that is triggered after 'apply' method of org.apache.beam.sdk.Pipeline class.
Wrote tests that ensure the element pattern is triggered at expected places.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

LGTM! Thanks @sultanalieva-s


Disable universal when there are fewer than 2 universal_archs

This PR makes the changes proposed in ticket #57133 to make having fewer than 2 universal_archs no longer be considered invalid, and to instead make it disable the universal variant.

Had an odd error while testing on High Sierra with universal_archs x86_64 set in macports.conf. I had glib2-devel installed with the universal variant (it's in my variants.conf), then installed a new version of it (which now built without the universal variant):
$ sudo port install
--->  Computing dependencies for glib2-devel
--->  Fetching archive for glib2-devel
--->  Attempting to fetch glib2-devel-2.58.1_0+x11.darwin_17.x86_64.tbz2 from https://packages.macports.org/glib2-devel
--->  Configuring glib2-devel
--->  Building glib2-devel
--->  Staging glib2-devel into destroot
--->  Installing glib2-devel @2.58.1_0+x11
Error: Failed to deactivate glib2-devel: Active version of glib2-devel is not 2.58.0_0+x11 but 2.58.0_0+universal+x11.
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_glib2-devel-2.58.0_0_acfe0990e4c09f67f3aeea0850938c9d30d0867c182b38eac8ef8ed59a2e67ff-5570/glib2-devel/main.log for details.
Warning: Failed to execute portfile from registry for glib2-devel @2.58.0_0+universal+x11
--->  Deactivating glib2-devel @2.58.0_0+universal+x11
--->  Activating glib2-devel @2.58.1_0+x11
--->  Cleaning glib2-devel

$ cat /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_glib2-devel-2.58.0_0_acfe0990e4c09f67f3aeea0850938c9d30d0867c182b38eac8ef8ed59a2e67ff-5570/glib2-devel/main.log
version:1
:debug:sysinfo macOS 10.13 (darwin/17.7.0) arch i386
:debug:sysinfo MacPorts 2.5.99
:debug:sysinfo Xcode 9.4.1
:debug:sysinfo SDK 10.13
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.13
:debug:main Executing org.macports.main (glib2-devel)
:debug:deactivate deactivate phase started at Fri Sep 21 20:53:58 CDT 2018
:debug:deactivate Executing org.macports.deactivate (glib2-devel)
:error:deactivate Failed to deactivate glib2-devel: Active version of glib2-devel is not 2.58.0_0+x11 but 2.58.0_0+universal+x11.
:debug:deactivate Error code: NONE
:debug:deactivate Backtrace: Active version of glib2-devel is not 2.58.0_0+x11 but 2.58.0_0+universal+x11.
:debug:deactivate     invoked from within
:debug:deactivate "registry_deactivate $subport $version $revision $portvariants [array get user_options]"
:debug:deactivate     (procedure "portdeactivate::deactivate_main" line 10)
:debug:deactivate     invoked from within
:debug:deactivate "$procedure $targetname"
:error:deactivate See /opt/local/var/macports/logs/_opt_local_var_macports_registry_portfiles_glib2-devel-2.58.0_0_acfe0990e4c09f67f3aeea0850938c9d30d0867c182b38eac8ef8ed59a2e67ff-5570/glib2-devel/main.log for details.

I don't know if it relates to my changes. I find it odd that the error says it failed to deactivate, right before it successfully deactivated.

It failed to run the deactivate target in the portfile. When that happens, there's a fallback to deactivating directly with registry calls, which is of course unable to run any pre/post deactivate code that the port may have.

Could we not just disable the default universal variant for Mojave and require it to be created explicitly via universal_variant yes?
Let's just change the default here:
https://github.com/macports/macports-base/blob/4b36e605d76fa3a423b4e35a6722ade4185ffa4f/src/port1.0/portmain.tcl#L138
This is used by universal_setup to decide whether to add a +universal variant to the port:
https://github.com/macports/macports-base/blob/6b0d697a1e050722071519b61c51dc0cf183d7aa/src/port1.0/portutil.tcl#L2098

Could we not just disable the default universal variant for Mojave and require it to be created explicitly via universal_variant yes?

I explained above the changes that would have to be made to a great many ports to accommodate that. In addition, portgroups that offer universal variants will need changes. I was hoping to avoid the need for such extensive changes by making just a few changes to base.

I am now seeing for the first time the option os.universal_supported which we could set to no on Mojave and later. However, without further changes along the lines I already proposed in this PR, that won't do any better at solving the problem.

We already have code for filtering out unsupported archs based on the port's supported_archs, which will need to be updated anyway to not substitute i386 for x86_64 when using the 10.14 SDK. I'd suggest actively filtering out i386 as well and then basing the decision of whether to allow universal on the length of ${configure.universal_archs}.
I would also not attempt to undefine explicitly defined universal variants, but rather just unset variations(universal) when there's only one arch. A warning when the user explicitly passes +universal on the command line would also be appropriate. E.g. ui_warn "+universal ignored because only one architecture is supported".

Come to think of it, what's the worst that would happen if we just left the vestigial universal variants? Some users wouldn't get binaries? A warning when using single-arch "universal" would probably cover that sufficiently.

I don't know where we are with this since it's been so long, but:

Come to think of it, what's the worst that would happen if we just left the vestigial universal variants? Some users wouldn't get binaries?

That would be one consequence, yes. Each combination of variants should produce something unique and useful. We should not allow variants that do nothing.

A warning when using single-arch "universal" would probably cover that sufficiently.

I don't agree. When there are fewer than 2 universal_archs, MacPorts should either remove the universal variant so that the user cannot see it and cannot select it or it should cause the universal variant to emit an error when it is used.


Merge 9 -> 11

➡ Forward port
Port sdf9 to sdf11. Normally I would merge from sdf10 to sdf11 after #614, but I wasn't sure if the parameter passing prototype on sdf10 is ready to be merged forward to edifice. Meanwhile, there are a lot of conflicts between #601 and #602 that completely disappear after taking several minutes to resolve them all, so I wanted to simplify our lives by getting that conflict resolution out of the way.
Branch comparison: https://github.com/ignitionrobotics/sdformat/compare/sdf11...sdf9
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

There's a new test failure.
I haven't done one of these skipped forward ports, it will be interesting to see what the subsequent ones look like.

There's a new test failure.

I fixed the test in a force push

I haven't done one of these skipped forward ports, it will be interesting to see what the subsequent ones look like.

I locally did a test merge of this branch with sdf10 and there were fewer conflicts


chore: dependency pinning and audit

Closes #3448

Summary
Adds pnpm audit in CI and pins dependency versions.
Checklist

[x] All changes are covered by tests (or not applicable)
[x] All changes are documented (or not applicable)
[x] I reviewed the entire PR myself (preferably, on GH UI)
[x] I described all Breaking Changes (or there's none)

@maschad neither of these changes were intended as full-proof solutions, but merely mitigation. Agreed deps can be retroactively compromised and we commit our lock file.
Pinning dependencies does mitigate risk of us upgrading to a compromised version, which in my experience is a more common risk.
Good point on the audit, with pinning in place we would only be upgrading from dependabot, so it would be redundant.

@maschad neither of these changes were intended as full-proof solutions, but merely mitigation. Agreed deps can be retroactively compromised and we commit our lock file.
Pinning dependencies does mitigate risk of us upgrading to a compromised version, which I believe is a more common risk.
Good point on the audit, with pinning in place we would only be upgrading from dependabot, so it would be redundant.

Thanks for the clarification @danielbate
Upon further consideration, I believe we could strengthen our security approach by adding pnpm audit specifically to our release workflow. This would ensure we never release with any known vulnerabilities. So I would welcome that change. Of course we can also simultaneously still benefit from the dependabot security alerts as well, perhaps we need to revisit the dependabot upgrade workflows to ensure that process is more streamlined.
While version pinning seems like it would increase security through strict control, it can actually work against us by making it harder to receive automatic security fixes, bug fixes, and improvements. Since we already commit our lockfile, we get the best of both worlds: reproducible builds through the lockfile, plus the ability to receive ranged upgrades with important fixes.
What are your thoughts on this approach?

I agree with adding pnpm audit as a part of our CI. I believe the frontend team has this as well

Thankyou for the investigation @maschad, agreed with you and @Dhaiwat10 I'll implement audit here. Although that will introduce some upgrade problems which I'll need to fix, so I'll convert this to draft.
Re dep pinning, I did take a look at something @petertonysmith94 mentioned in sync yesterday, that although we do commit the lock file, it isn't included in our published distribution so only benefits us in development and not consumers installing fuels. So they would still be at risk of installing a compromised package installed by a range dependency?

I caught up with @maschad earlier and we agreed that implementing audit on release is a good idea to ensure we aren't shipping with compromised versions. We also agreed that committing the lock file doesn't protect consumers of fuels. So we are left with a file predicament that is do we:

Pin versions in an attempt to protect consumers from malicious upgrades, but they also miss out on security updates, and we're still at risk of a pinned version being compromised
Keep the range versions to protect consumers by ensuring they can receive security updates by having the latest version

This feels like a bit of play off and would appreciate another opinion @FuelLabs/sdk-ts.
A potential solution that @maschad did propose would be to pin the consumer versions (prod deps inside fuels) but allow ranges for our dev deps so we can still benefit from security upgrades internally.


[CTA] Looking for Maintainers

Been a while since I've been able to commit time to jotai-form or OSS contributions in general.
As much as I'd like to keep contributing, the maintainer role isn't something I'm able to live up to right now and would like to pass it on to someone who'd be happy to maintain the library.
If you are interested in doing so, please reply here and we'll help you with the next steps

I’m very interested in becoming the maintainer of this project.

Sounds great!
I gave @L-Qun the maintainer role in this repository. You can do anything including changing some tooling like eslint. If you have questions feel free to drop messages.
For some design decisions, you may ask @barelyhuman and hope they can respond when they have time.

@dai-shi Could you also add me as a maintainer of jotai-scheduler https://github.com/jotaijs/jotai-scheduler

Done. (I didn't know how the transferred repo has permissions. Usually write permission would be enough.)

That was quick!
@L-Qun thanks a ton! and do let me know if there's anything you wish to discuss :)


Bump CodeQL action version

Summary: CodeQL seems unhappy with the go version update, testing to
see if this fixes it.
Type of change: /kind cleanup
Test Plan: Check action run on this PR.

This isn't necessary. This was fixed by the codeql cli update.


haskellPackages.hakyll: remove unnecessary patch, unbreak

Motivation
Unbreak hakyll.
Things done
Removed obsolete patch, as it's replacement was merged and is in the current version.

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build haskellPackages.hakyll

I think you should instead remove hakyll (and dependents of it, if they build) from the list of broken packages here: https://github.com/NixOS/nixpkgs/blob/eca09e0d997546e005241d7c8cd6f8c999bf8496/pkgs/development/haskell-modules/configuration-hackage2nix.yaml#L5088
on the haskell-updates branch. Then the next automated update (probably by @peti) of hackage-packages.nix will not mark is at broken anymore. Remove the patch on that branch too.

Ok I changed the base to haskell-updates and removed everything from the broken section in configuration-hackage2nix.yaml that depends on hakyll. But I didn't do any builds, because that would be too time/bandwidth/storage consuming for me right now.
I find this workflow to be quite a frustrating one and I would like to explain here how I come to that conclusion.
First of all this is a commit that doesn't change anything to the better for me. If I build hakyll, I still get an error that the package is broken. I can't tell OfBorg to build it, and I can't easily prove to anybody else, that the packages builds now. For me I still need to remove the broken attribute with overrideCabal until the package set is regenerated.
Second, this leaves me with reverse dependency resolution, a task that I've never needed to do in other sections of Nixpkgs. Why should I care wether agda-snippets-hakyll builds? I fixed hakyll and every other problem with agda-snippets-hakyll should be subject to somebody trying to fix that package. Still in the current situation I need to remove agda-snippets-hakyll from configuration-hackage2nix.yaml because otherwise it could stay marked as broken while it actually could build.
Regarding this new practice of marking packages automatically as broken I agree with the reasoning @peti laid out here:

The change prevents people from wasting half an hour of their lives trying to compile a package that we already know will not succeed.

So I wonder wether it would be possible to only mark packages as broken if theyself fail to build? Packages with a broken dependency will fail to evaluate anyway, even if they are not marked as broken. This way I wouldn't need to work my way through the package set and find reverse dependencies.
Atm this blew up the time I take to simply remove a patch from ~30min to 3h. I'm already more of a low volume contributer but if this stays this way I'll find even less time to upstream my patches…
Still: Thanks for all the work.

Yeah it is a bit cumbersome, I hope in the future only failing builds themselves will get marked as broken and not all dependents too.

I pushed a commit to fix a dependency of hakyll on that branch.
The packages unmarked as broken often still don't build, but I think that's still fine.

I wonder whether it would be possible to only mark packages as broken if theyself fail to build?

Attempts to build packages that depend on a broken packages result in an evaluation error on Hydra, unfortunately, so we cannot leave those builds enabled.

I agree with most of what @erictapen wrote, and especially the "thanks for all your work" part. I tripped over broken hakyll last night, made a PR and was notified about this one overnight.
I disagree that it's impossible to prove it works: I can at least tell people that running nix-build -E '(import ./. { config.allowBroken = true; }).whatever builds. It does seem like a sticky trap for packages, though: they get marked broken easily but it's not so easy to get them unmarked. #61536 , which unmarks the lattices package, which has been stuck for a week.
What's needed to get either this or my hakyll PR ( #61875 ) over the line?

Alright I merged your PR's @endgame. Note that you can also use nix-build -A whatever --arg config '{ allowBroken = true; }' :)

Do broken packages get automatically added to this file?

No. That file is maintained manually.


[SPARK-36682][CORE][TEST] Add Hadoop sequence file test for different Hadoop codecs

What changes were proposed in this pull request?

This patch proposes to add e2e tests for using Hadoop codecs to write sequence files.
Why are the changes needed?

To improve test coverage.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Added tests.

Test build #143040 has started for PR 33924 at commit a0b115f.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47543/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47543/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47543/

Test build #143040 has finished for PR 33924 at commit a0b115f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143040/

We have dedicated JIRAs for snappy and lz4 issues. We already verified the issues in above CI test, going to remove them first to make test passed.

Test build #143054 has started for PR 33924 at commit a9139b3.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47557/

cc @sunchao @cloud-fan @dbtsai too

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/47557/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/47557/

Test build #143054 has finished for PR 33924 at commit a9139b3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

The last commit is comment doc only. Thanks for reviewing. Merging to master/3.2.

+1, late LGTM.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/143054/


Pipeline adaptation

To-Do List:

[x] The workflow sequence and helper functions should be modularized so they can be easily used by Pipeline.
[x] Fix the codestyle issue to avoid future problems.
[x] Use Python/CASA logging for statements.
[ ] Ideally, the new restructured code can be used either in the Pipeline environment or as a "script" for the monolithic CASA:

To minimize the change to the original code, we could design a translating/adaptive layer to deal with externally developed scripts/modules in general. They are often/unfortunately written for the monolithic CASA (i.e. with the extra bits provided by casashell), rather than standard pythonic modules/class/functions. Under the proposed layer, the same namespace could present a "true" CASA task (when running as a script in CASA) or a Pipeline wrapper of a CASA task (when running as an "extern" dependency of Pipeline). Then external codes can be used in both contexts, without substantial rewriting.

Check List:

[ ] The refactored code should still work similarly to the original code in the "CASA script" mode.

A new branch (pipeline-adaptation-more) is created from 292bb78baeda331e306f470b5989626c0d4e6330 (the latest commit to pipeline-adaptation-with-code-refactoring).


Better Testing-farm response for cluster problems

Response to testing-farm errors.
Link centos-ci issue on known problem.

recheck


New Version 2 codebase

This is a complete rewrite of the plugin to support tox v4 and a scope currently very specific to the faciliation of collection testing.
Additional capabilities and PR are, of course, always welcome.

@greg-hellings TY for taking the time to review....  I'm still sorting out the tox internals, so I suspect there are better ways to do some of this. LMK

@ssbarnea @greg-hellings I think this is ready.  We can sort out the release pipeline next week once this is merged and put a 2.0 out on pypi...


Return correct error

Description

closes: #5204
ref: #5201

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

good call @crodriguezvega / @DimitrisJim  will add one

update: we do have a test, we are just using the old expPass (perfect reason for why we are moving to the expErr :D )


DeduplicationHandler always registers ::DEBUG

https://github.com/Seldaek/monolog/blob/78bd7bd33313c3a7ad1f2b0fc0c11a203d4e3826/src/Monolog/Handler/DeduplicationHandler.php#L67
The DeduplicationHandler always registers Logger::DEBUG, it should be $deduplicationLevel because otherwise all DEBUG data is logged to the dedup file and parsed for dedup, leading to unintentional memory issues and logging.

The point is that it wants to catch all logs to forward everything to the nested handler, but in flush() only records with a higher level than $deduplicationLevel are actually looked at and logged to the dedup file, so it seems fine to me?
If you are really logging lots and are worried about memory issues (if you are running long processes, don't forget to call $logger->reset() between every job to make sure to clear buffers), worst case you could wrap the DeduplicationHandler in a FilterHandler or BufferHandler to filter out what reaches it..

The point is that it wants to catch all logs to forward everything to the nested handler, but in flush() only records with a higher level than $deduplicationLevel are actually looked at and logged to the dedup file, so it seems fine to me?
If you are really logging lots and are worried about memory issues (if you are running long processes, don't forget to call $logger->reset() between every job to make sure to clear buffers), worst case you could wrap the DeduplicationHandler in a FilterHandler or BufferHandler to filter out what reaches it..

BTW added docs about reset which I just realized were missing.. https://github.com/Seldaek/monolog/blob/main/doc/01-usage.md#long-running-processes-and-avoiding-memory-leaks

BTW added docs about reset which I just realized were missing.. https://github.com/Seldaek/monolog/blob/main/doc/01-usage.md#long-running-processes-and-avoiding-memory-leaks

Actually, this was a long-running script with lots of debug data, which suddenly consumed several GB of memory (and was killed by oom-killer) because this DEBUG data was being stored.
At the very least I would say the level should be configurable.

Actually, this was a long-running script with lots of debug data, which suddenly consumed several GB of memory (and was killed by oom-killer) because this DEBUG data was being stored.
At the very least I would say the level should be configurable.

Well you can call $handler->setLevel() to override this if you must, but I'd rather recommend making use of reset() to properly handle long running scripts.

Well you can call $handler->setLevel() to override this if you must, but I'd rather recommend making use of reset() to properly handle long running scripts.


Something changed tonight can't find typings any more

All of a sudden tonight I am getting errors for all of my typings.  Did something change?
D:\dev\proj\slb\planck\src\CoreServices\Dev\Src\Client\Web\Client.Web.Framework>typings install
typings ERR! message Unable to read typings for "angular-mocks". You should check the entry paths in "angular-mocks.d.ts" are u
p to date
typings ERR! caused by https://raw.githubusercontent.com/DefinitelyTyped/DefinitelyTyped/3030a4be536b6530c06b80081f1333dc0de4d7
03/angularjs/angular-mocks.d.ts responded with 503, expected it to equal 200
typings ERR! cwd D:\dev\proj\slb\planck\src\CoreServices\Dev\Src\Client\Web\Client.Web.Framework
typings ERR! system Windows_NT 6.1.7601
typings ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\bbeal\AppData\Roaming\npm\node_modules\typings\dis
t\bin.js" "install"
typings ERR! node -v v4.2.2
typings ERR! typings -v 0.7.9
typings ERR! If you need help, you may report this error at:
typings ERR!   https://github.com/typings/typings/issues

Not really working, since I can't get any build to complete because one typing fails or another, but i figured it wasn't typings fault.  I'm about to check in all typings into source control.  I can't rely on external services when we are about to release.

 Recently github is not that stable


Bump lint version to 30.4.0-alpha03

Summary
Describe the goal of this PR. Mention any related Issue numbers. Please note that we do not normally
accept new externally-contributed PRs to this repo unless it's something Slack-relevant and came
up in prior discussion
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

The following point can be removed after setting up CI (such as Travis) with coverage reports (such as Codecov)

[ ] I've written tests to cover the new code and functionality included in this PR.

The following point can be removed after setting up a CLA reporting tool such as cla-assistant.io

[ ] I've read, agree to, and signed the Contributor License Agreement (CLA).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Upgrade from 0.5 to 0.7 leads to hundreds of errors in the generated file

Hi there,
I'm upgrading a tool which uses prost in version 0.5. The protobufs are automatically build using the build.rs script, but then I copy that output file (xb.rs) into a source folder.
The .proto file is valid (it's used in Python and C without issue), and compiles with prost/prost-build/prost-derive version 0.5.
I get two errors repeated for each structure:
error[E0433]: failed to resolve: unresolved import
   --> /home/chris/Workspace/xb/xbrs/target/debug/build/xbrs-596b816b7bed7198/out/xb.rs:869:28
    |
869 |     pub instrument_root: ::core::option::Option<Instrument>,
    |                            ^^^^
    |                            |
    |                            unresolved import
    |                            help: a similar path exists: `nalgebra::core`

And
error[E0283]: type annotations needed
 --> /home/chris/Workspace/xb/xbrs/target/debug/build/xbrs-596b816b7bed7198/out/xb.rs:1:28
  |
1 | #[derive(Clone, PartialEq, ::prost::Message)]
  |                            ^^^^^^^^^^^^^^^^ cannot infer type
  |
  = note: cannot satisfy `_: Default`
  = note: required by `std::default::Default::default`
  = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

How can I solve this? Maybe related #375 ?
Thanks

Thanks to @danburkert for the live help on tokio's discord!
Solution:

If Cargo.toml doesn't have edition = "2018", then you need to add extern create core;.
If you may switch to the 2018 edition, just add that line in the Cargo.toml file and the problem will fix itself.

Thanks to @danburkert for the live help on tokio's discord!
Solution:

If Cargo.toml doesn't have edition = "2018", then you need to add extern create core;.
If you may switch to the 2018 edition, just add that line in the Cargo.toml file and the problem will fix itself.


BUG: Handling process.arch inconsistency

Because this action use https://github.com/tauri-apps/tauri-action/blob/688bc7beb550380b8a4c3542f84d2704312cfe91/src/utils.ts#L225, it is returning the wrong target for Mac M1/M2.
Specifically, M1 and M2 both report process.arch as arm64 instead of aarch64. Thus, the action needed a dedicated target to build for tauri.
I wonder if there's a way to detect M1/M2?...

Thanks for the report! You're right, the action does not factor in self-hosted runners right now (funnily enough i accidentally made the json uploader work for this so it should only be the actual asset uploader being left)

I don't have access to (arm64) self hosted runners, could you test the fix/hosted-runner branch if you got the time? 🙏

@FabianLars just tested, the fix works :D - thanks so much for the PR!

Thanks for testing!


Fix gcp

Description
I made the biqquery operators use standard sql by defualt. The legacy sql has limited support for dates and datetimes, which we need. I've consequently also removed the casting of dates to UTC seconds, since the standard sql dialect handles this fine.

Added location support for the BigQuery ValueCheckOperator


Fix lowercase in XxxComponent's model namespace

use App\Models\book; in app/CRUD/BookComponent.php

Thanks!


Rename -gap to -spacing

Fixes #60

This change is

Reviewed 10 of 10 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Way to identify plugins for 1.13

Could we create a doc that has a table of plugins that are supported for 1.13?  Ideally in the future this should be in the hub / store but a doc to start would be great.

/cc @anusha-ragunathan

Starting today, Docker store can be searched for available plugins. https://store.docker.com/search?certification_status=certified&q=&type=plugin


Running Issue

As I am not used to python, I need some help running the MobileNet. Please help :)
When I do 'python main.py config/test.json'
It prints out
'main.py: error: unrecognized arguments: config/test.json
Add a config file using '--config file_name.json'
What do I have to do?
Thank you.

@ohcurrent i think it's an issue with python version.Can you try it with python3
python3 main.py --config config/test.json
it will probably resolve the issue


[core] Fix TypeScript type for children

This is a follow-up to #20450.
See https://github.com/mui-org/material-ui/pull/20450#issuecomment-610303516

[x] I have followed (at least) the PR section of the contributing guide.

@eps1lon thanks for updating the PR

@NMinhNguyen Thanks!


Set Default Value

Hello Krystal,
I hope we can set a default value for the dates. The example on this repo isn't working,
<HotelDatePicker :value="'2020-07-14 ► 2020-07-20'"/>
I hope you can add something like this
<HotelDatePicker :startingDateValue="'2020-07-14'" :endingDateValue="'2020-07-20'"/>
Cheers

I spent an hour to figure out how to set the default value, and found nothing till I saw this opened issue, hope we can merge this and make it work :)


[Feature] Support full functions of g30esli_interface

Status
DEVELOPMENT
Description
We upgrade g30esli_interaface for supporting full functions of Yamaha Golfcar ECU.
Related PRs
Issue: #1961
Previous PR: #1962
Todos

[ ] Tests
[ ] Documentation

Steps to Test or Reproduce
## connect CAN device as SocketCAN
## up interface
$ rosrun ymc canset up

## not use DS4 joystick
$ roslaunch ymc g30esli_interface.launch
# -> press "s" key to engage

## use DS4 joystick
$ roslaunch ymc g30esli_interface.launch use_ds4:=true
# -> press "option" key to engage
# -> press "ps" key to use `vehicle_cmd`

## down interface
$ rosrun ymc canset down

This feature was not scheduled for 1.12, so it cannot be merged into master until after the 1.12 release.

@wep21 I fixed that by adding "catkin_install_python".

Please add the sign-off line to your commits.

I tested the operation until https://github.com/autowarefoundation/autoware/pull/2139/commits/94760dce9e120e05e81aef05f0690c40fcdaca48, but had the following problems.
Have these problems been solved?

It takes longer to brake than previous versions.
I can not start again after braking.

@gbiggs Thanks. I added using cherry-pick.

@yn-mrse Since you said those problems, I added braking logic in cfd3f58 and restating logic in 7bf69ad. Thanks for your review.

@yn-mrse Please confirm if the problem you found has been fixed.

@wep21 @yn-mrse Thanks for your code review. I updated this PR with the more detailed testing process, please check if you can.

@aohsato I tried offline test as described above. I could obtain a desired result as following.

https://github.com/autowarefoundation/autoware/pull/2139#issuecomment-492895665
@aohsato @gbiggs The corresponding part has been verified at the code level.

@aohsato Conducted an online test and confirmed the operation.
The parts necessary for the correction are as described above. It has been confirmed that it works without any problems if these patches are added.

@yn-mrse @wep21 Please confirm if your review comments have been dealt with satisfactorially, and if they have please set your review to "approved".
@aohsato Some of your commits are missing the DCO sign-off line.

@yn-mrse @wep21 Thanks for your review!
@gbiggs I forgot that, pushed again by using cherry-pick.

The GitLab CI is failing because the binary format does not work in cross compilation (obviously), so I'm going to override the CI requirement and merge. The non-cross CI run compiles.


TypeError: Object.entries is not a function

Describe the bug
Just installed the tool with :
sudo npm install -g kubelive
and when trying to use it :
$ export KUBECONFIG=<PATH_TO_KUBECONFIG_FILE>

$ kubectl cluster-info
Kubernetes master is running at ...
KubeDNS is running at ...
Metrics-server is running at ...

$ kubelive
/usr/local/lib/node_modules/kubelive/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

TypeError: Object.entries is not a function
    at Module.assembleStyles [as exports] (/usr/local/lib/node_modules/kubelive/node_modules/slice-ansi/node_modules/ansi-styles/index.js:123:42)
    at Function.Module._load (module.js:440:16)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/usr/local/lib/node_modules/kubelive/node_modules/slice-ansi/index.js:4:20)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)

Expected behavior
kubelive displays help message
Desktop (please complete the following information):

OS: [e.g. iOS] Ubuntu 17.10

Additional context
$ kubectl version --short
Client Version: v1.17.0
Server Version: v1.16.6

$npm -v
3.5.2

Hi @yogeek, what is your node version,  can you please try upgrading to v10

Hi @ameerthehacker , thank you for your help. As I indicated in my previous comment, my npm version was "3.5.2". I just tested with the latest docker image node (version v13.8.0), and it is working well.
Perhaps you can indicate the mininal node version kubelive is compatible with in the install instructions ?
And if you are interested, here are the instructions to launch your tool with docker :
# Build kubelive docker image
docker build -t kubelive -f - . << EOF
FROM node:latest
RUN npm install -g kubelive
ENTRYPOINT ["kubelive"]
CMD ["-h"]
EOF

# Use it
docker run --rm -it --net=host -v ~/.kube/kubeconfig:/root/.kube/kubeconfig -e KUBECONFIG=/root/.kube/kubeconfig kubelive get pods

Thanks !

Hi @yogeek, this is fixed by  #18 and it has been published to npm so I'm closing this issue
Please feel free to reopen the issue if you still face any issues


Support @strawberry.type

support @strawberry.type as dataclass
How to build it
https://koxudaxi.github.io/pydantic-pycharm-plugin/development/

@patrick91
Thank you for reviewing PR.

Is there anything you need from us to get this published, shall we merge it and deal with the rest later?

Jetbrains Account, plugin Id, and a token to publish the plugin.
https://plugins.jetbrains.com/docs/marketplace/plugin-upload.html
https://account.jetbrains.com/login
I will add this CI file after I have dinner. 😉
https://github.com/koxudaxi/poetry-pycharm-plugin/blob/da2d98bbf3853711770cb32b1d7d4f39b844dcd1/.github/workflows/publish.yml#L74-L78

The pydantic plugin is my first plugin project.
I used a plugin.xml to configure the plugin.
But, we should move some settings to build.gradle.
gradle-intellij-plugin can descript few configs in build.gradle that  instead ofplugin.xml
gradle-intellij-plugin  provides dynamically configuration. (we can write gralde script or kotlin DSL)
For example,
Poetry plugin use patchPluginXml in build.gradle. It's my second project.
This is not a dynamic attribute. But, I feel the style is better than writing it in plugin.xml
https://github.com/koxudaxi/poetry-pycharm-plugin/blob/da2d98bbf3853711770cb32b1d7d4f39b844dcd1/build.gradle#L28-L31
This idea is not required for first release.
We should add it TODO list 📝

I've added a token in the configuration:

We can use GitHub issues for TODOs :) I'll add you to this repo, feel free to merge this PR when you want.


fix: :bug: Fixed imports

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


docs: add more details to champions document

Description
This PR adds a few changes to the champions document as well as updates the code owners file to reflect the new generator and inputs.
@ron-debajyoti did you want to champion the TS input?

@jonaslagoni sure !


fix: NullPointerException when stage.imageName is missing

fixes #89

Hi @lexemmens, Could you please review this PR?

LGTM!


[WFCORE-6446] Enable better test failure output when the queue for sy…

…slog messages is not empty.
https://issues.redhat.com/browse/WFCORE-6446

/retest

Merged @jamezp , I hope this helps with the final resolution ... random failures are always tricky


Medium images rendering is wrong

Hi,
Some feeds in my Miniflux come from Medium. And since the 2.0.18 release (I haven't setup the 2.0.19 yet), the image rendering is wrong, indeed images are not usable at all. Here is an example:

Well, really wish this could be fixed.

 But I was able to create a rewrite rule fix_medium_images that seems to work. See https://github.com/miniflux/miniflux/commit/31435ef83e8fc1fd90126bd8eed03073ee600753.

This is great, just gonna wait for the next release.

It's released in version 2.0.24. Fell free to improve this feature.


Add jupiter client implementation

Motivation

Add jupiter client mod

Solution

I defined some functions based on js sdk

Hi @jordy25519
Thank you for the response.
I didn't know the repo.  The repo does same thing. Thank you for sharing.
I understand your point, so I will close the the PR.

Hi @jordy25519
Thank you for the response.
I didn't know the repo.  The repo does same thing. Thank you for sharing.
I understand your point, so I will close the the PR.


WIP Add: crop csv file and import to the database

Get crops from the CSV file and add them to the database
Refers to issue #359

Coverage decreased (-0.2%) to 98.982% when pulling 8a11610b32f577e411b46a403b358fb314fdb985 on sigu:import_crops into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on openfarmcc:master.

Coverage decreased (-0.2%) to 98.982% when pulling 8a11610b32f577e411b46a403b358fb314fdb985 on sigu:import_crops into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on openfarmcc:master.

@simonv3  is there any documentation that needs to be modified to show why and how this import is done.

Coverage decreased (-0.2%) to 98.982% when pulling 67991b2391bad79fc6d5ed6cc2bd4a7eed8afa41 on sigu:import_crops into<PHONE_NUMBER>4c0d5d59c01f1796362665e7998e85 on openfarmcc:master.

No but feel free to add some!

Not any documentation adjustment I can think of right now. 😄

Merging cause I think the test failures are outside of this PR.


Completed Issue #42

CHANGELOG :memo:

PRINTS(OPTIONAL) :framed_picture:
LABELS

Example: enhancement, wip etc

@sampathbandla Thank you for your contribuition..
I think this gif is incomplete. It shows only the yarn install.
It should display only the rocket in action, without install steps..
BONUS
If you could to add some zoom to improve the visualization, it will be good.

this issue was done at #47
Thank you, but is already done. Take a look in our issues list for new challenges!


Implement messagetoast

Implement a messagetoast on each page which displays the route that has been hit.
Can probably be implemented within the app/view

https://github.com/SAPMarco/UI5-navigation-and-routing/commit/3d1dc08ee3de51c919132c3fc17f91052e3ecbb7


Need to be able to insert top level Object properites that aren't indexed in a list

You should be able to describe this structure inside a line in Depot, specifically the props:
{
        "guid": "ba90a294-8065-4c5b-b7f0-252d245a3275",
        "id": "0",
        "props": {
          "guid": "9c385502-7766-4210-984a-7e0b435b6c9a",
          "newInt": 0,
          "newBool": true
        }

Right now you can only describe lists as nested types, meaning that indexing a nested value of something needs to work by array index like lines[0].props[0].someKey. Instead, you should be able to do lines[0].props.someKey

implemented in 18df6b068a32dda1927ca99ebad10de38dd82d91


Unable to set response headers

Problem statement
I need to set CORS headers but am unable to do so by any method I have tried.
Steps to reproduce
I tried the method described in issue #481. That did not work.
I tried describing headers in the spec and setting them in my handler. That did not work.
I tried hacking to get the http.Handler and adding the headers. That did not work.
Environment
swagger version: v0.25.0
go version: 1.14.6
OS:   Mac

cors are technical headers typically not part of the spec.
The UI server available from the swagger command to serve doc, swagger serve ... onboards some cors middleware.
The generated API server does not: you have to configure your cors middleware in the configure_api section.

Yes. What you describe is the solution from #481. I tried that. It does not work.

I came up with a novel work around. Basically I copied get-somepath-responses.go to a new folder, renamed it, and gave it a new package. I then deleted all of the "generated code" comments, and added headers to the WriteResponse function. I then import my "custom" response package into configure-my-service.go. If you attempt this work around, you must add your headers before calling WriteHeader().
// WriteResponse to the client
func (o *GetSomethignOK) WriteResponse(rw http.ResponseWriter, producer runtime.Producer) {
	// Add the next line
        rw.Header().Add("Access-Control-Allow-Origin", "*")
	rw.WriteHeader(200)
	payload := o.Payload
	if payload == nil {
		// return empty array
		payload = models.InsightList{}
	}

	if err := producer.Produce(rw, payload); err != nil {
		panic(err) // let the recovery middleware deal with this
	}
}

"github.com/rs/cors" comes with a debug mode you can use to investigate what is being done. I don't see any reason why this middleware wouldn't work in the context of a swagger-generated server. There is nothing special about the generated code...

I also think something else must be wrong, would it be possible to share the code that doesn't work as a repo. I've used middlewares with the generated code many times.

I solved this using configure_apis.go. In the configureServer
The code became like this
// As soon as server is initialized but not run yet, this function will be called.
// If you need to modify a config, store server instance to stop it individually later, this is the place.
// This function can be called multiple times, depending on the number of serving schemes.
// scheme value will be set accordingly: "http", "https" or "unix"
func configureServer(s *http.Server, scheme, addr string) {
	s.Handler = cors.AllowAll().Handler(s.Handler)
}

@lpegoraro thank you for adding this example.
Indeed, inserting a middleware is the idiomatic way to add CORS support to your API (usually, you don't want these headers to be part of the spec, and neither do you want other standard HTTP headers to pollute the spec)

I tried the above and it works. But whenever I run go generate again, the middleware disappears since the files are regenerated.

19 dec 2024 ..


update Kubeflow Notebooks docs

This PR updates the Kubeflow Notebooks docs:

creates new "overview" page
removes specific references to "Jupyter" (as Kubeflow 1.3 now supports multiple IDEs)
added lots of information about how to build your own container images (for Jupyter, VSCode, and RStudio)
simplifies the "getting started" guide (and makes it generic to not just be about Jupyter)

This is the first step towards having the docs updated for 1.4:

https://github.com/kubeflow/manifests/issues/1961

In future PRs, to be updated for 1.3/1.4, we need to:

the PNG images of the UI need to be updated for 1.4
add a page about spawner_ui_config.yaml
add a page about how to configure logos for "group 1" and "group 2"

/src/apps/default/static/assets/group-one-icon.svg
/src/apps/default/static/assets/group-one-logo.svg
/src/apps/default/static/assets/group-two-icon.svg
/src/apps/default/static/assets/jupyter-icon.svg
/src/apps/default/static/assets/jupyterlab-logo.svg

@zijianjoy can you please review this before we cut the 1.4 branch (it's pretty important updates for the Kubeflow Notebooks docs)!

@thesuperzapper yep, it's one of my highest priorities! I'm having my hands full with KubeCon right now, but I'll try to do this in parallel in the next days

Left a few comments, but the overall structure and additions look good to me. Would you like to get a review from @kimwnasptd as well.
Thanks @thesuperzapper ! Really appreciate the work here.

Thank you very much for this work @thesuperzapper! I've left some initial comments on some parts of your work. The main theme of the comments is to not use the naming Kubeflow Notebooks since this implies that only some Notebooks are Kubeflow while others are not.

@kimwnasptd I think I am not understanding what you mean by "this implies that only some Notebooks are Kubeflow while others are not".
In my mind, the name "Kubeflow Notebooks" is the brand-name of the "applications which run notebooks in Kubeflow". Similarly, "Kubeflow Pipelines" is the brand-name of the "set of applications that run pipelines in Kubeflow" (note, we already use "Kubeflow Pipelines" in the docs for that component).
To put it another way, these docs are describing the "set of applications in Kubeflow which run notebooks", and the collective noun for those things is "Kubeflow Notebooks" not "Notebooks".
I feel very strongly that this will improve the brand recognition of the Kubeflow Notebooks "product".

@thesuperzapper @kimwnasptd My two cents here on naming. So the problem stems from the fact that the component’s name is the same name as the objects being handled by the component. I think this is why it’s Kubeflow Pipelines and not just Pipelines. Because Pipelines is a generic term that by itself does not identify a specific product. Take Katib or KFServing instead, they are brand names that identify a specific component.
So, in terms of Docs, I think that using Kubeflow Notebooks to refer to the components and Notebooks to the specific instances can help. BUT, this has in no way change what we do in the dashboard. There, we should continue showing Notebooks, which are the objects.

@thesuperzapper @kimwnasptd My two cents here on naming. So the problem stems from the fact that the component’s name is the same name as the objects being handled by the component. I think this is why it’s Kubeflow Pipelines and not just Pipelines. Because Pipelines is a generic term that by itself does not identify a specific product. Take Katib or KFServing instead, they are brand names that identify a specific component.

@StefanoFioravanzo If I am reading this correctly, you are agreeing with my proposal to use the "brand name" of "Kubeflow Notebooks" on https://kubeflow.org, rather than what is currently on the website: "Notebook Servers"?

So, in terms of Docs, I think that using Kubeflow Notebooks to refer to the components and Notebooks to the specific instances can help. BUT, this has in no way change what we do in the dashboard. There, we should continue showing Notebooks, which are the objects.

I completely agree that within Central Dashboard, it makes no sense to specify "Kubeflow Notebooks" on the sidebar, and we should continue to use "Notebooks". However, this PR is changing the section-name on https://kubeflow.org from "Notebook Servers" to "Kubeflow Notebooks" (which will not affect Central Dashboard).

@kimwnasptd you gave a thumbs up to @StefanoFioravanzo comment above. Are you in agreement with @thesuperzapper's summary that follows that comment?

@shannonbradshaw thanks for your comments, but in the interest of getting this PR merged, can you raise a separate PR which makes your desired changes after this has been merged (NOTE: the notebooks/quickstart-guide.md is not actually a new page, it was just moved/cleaned by this PR)

@Bobgy this PR has been reviewed by @shannonbradshaw and @kimwnasptd and I have addressed the comments from them, but we still need someone with root OWNER to /approve this (because it updates the _redirects file)
Can you /approve this so that we can have the notebooks docs updated for Kubeflow 1.4 (and 1.3, lol)?

@thesuperzapper it is OK with me to address my comments in a separate PR. Thanks for following up. It looks like we've provided enough time for other reviewers to chime back in. I'm in favor of merging this. @Bobgy or @zijianjoy

/approve
I'm interested to see if there are ways for WGs to self service on redirection changes.
Looks like hugo also supports a field called "aliases", it can be added directly on content pages.
Can you confirm if you can set up redirect in that approach?
https://gohugo.io/content-management/urls/#example-aliases

@shannonbradshaw can you /lgtm so this gets merged?

I'll go on and merge this PR, thanks for your effort in this @thesuperzapper!
Although, in the future please give an explicit heads up to WG leads when renaming the product name of a Component since this needs discussion. This is a significant change and there was no mention of this the PR description. Doing such a change alongside a whole refactoring makes it difficult to discuss specific parts when dealing with such huge PRs.
/lgtm


is this an older version

is this version older than the one on https://yourworldoftext.com
the one i have:

the one on https://yourworldoftext.com :

or am i doing something wrong?

Yes
On Sat, Jun 10, 2017 at 10:25 AM, James<EMAIL_ADDRESS>wrote:

is this version older than the one on https://yourworldoftext.com
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/reverie/yourworldoftext/issues/7, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEe5p3hHZYO7ftjPtvv16D9_nXHiyKfks5sCmD1gaJpZM4N2D-e
.

any plans of updating it?

Probably not, sorry
Sent from my phone

On Jun 10, 2017, at 12:34, James<EMAIL_ADDRESS>wrote:
any plans of updating it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


 It got killed. Is there anything I can do to help track down the problem?

When I run ncdu on the same location it seems to soldier on using 1GB or RAM

I tried with dust too, it also got killed when it started using over 8GB of RAM.
---------------------------Server Information---------------------------
 ____^____
 |\  |  /|     os     CentOS Linux release 7.9.2009 (Core)
 | \ | / |     host   r5a.large
<---- ---->    kernel 5.4.125-200.el7.x86_64
 | / | \ |     uptime 122d 17h 7m
 |/__|__\|     pkgs   746
     v         memory 10508M / 15757M

ncdu is now using 4GB and still going.

This can happen. When the system runs out of memory, OOM Killer will kill gdu. The memory consumption of gdu will always be higher than of ncdu, because Golang has some overhead in comparison to plain C.
The memory consumption of gdu could still be improved a bit though.

Is there not something I can do to help? Run it with debugging turned on or something?

You can turn on profiler - https://pkg.go.dev/net/http/pprof and see what consumes the memory.

I probably should add one clarification first: this behaviour is expected. When some process consumes too much memory and the operating system runs out of it, the process is terminated by the system. So it's not a bug in gdu, it's a consequence of using a lot of memory when scanning huge filesystems.
We probably could lower this usage a bit, but I guess not by a large margin. It will always be using more memory than tool written in pure C.


Removing module service provider from composer.json stub

Having the service provider in composer.json causes Laravel to auto detect it. This change stops this from happening

Sorry for the delay, thanks for the contribution! 👌