Change report name in mast head upon modification

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/35419
PROPOSAL: https://github.com/Expensify/App/issues/35419#issuecomment-1917551505
Tests

Go offline
Create a room
Change the name of the room
Take a note of room name on header and room name above the composer and make sure they are same.

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Go offline
Create a room
Change the name of the room
Take a note of room name on header and room name above the composer and make sure they are same.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

https://github.com/Expensify/App/assets/77237602/c4c94d00-837e-436d-a022-beb4aaf680d4

iOS: Native

iOS: mWeb Safari

https://github.com/Expensify/App/assets/77237602/05019058-2b8a-4564-9287-b019e20845f6

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/77237602/ea60dbf4-998d-4410-88de-3b0b90dded63

MacOS: Desktop

https://github.com/Expensify/App/assets/77237602/5497a0f0-05af-4d09-94a6-3130f7b1e95a

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/thienlnam in version: 1.4.41-12 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Public UI: Add  tag in HTML

More Info
Reported by: Taras Hetmanchuk<EMAIL_ADDRESS>Source URL: https://supergiant.io/
BrowserChrome 70.0.3538.77Screen Size1680 x 1050OSOS X 10.14.0Viewport Size1680 x 1027Zoom Level100%Pixel Ratio@2x

https://qboxio.slack.com/archives/CBJDVM0MQ/p1542537050177600

This was reported as fixed via slack.


Update the qcSeed whenever it is used.

Now, very invocation of quickcheck is using the same seed. We would like to change that whenever it is used so that it doesn't go stale.

Being worked on in https://github.com/Tritlo/Endemic/tree/updating-qc-seed

Fixed in https://github.com/Tritlo/Endemic/commit/5ce47e6b4f700bee463a342d6ca910a4206fc7d4


Option to sort facets alphabetically

Suggested here:

https://github.com/simonw/datasette/discussions/1908

The list of states here is a good example of somewhere this might be useful: https://congress-legislators.datasettes.com/legislators/legislator_terms?_facet=state&_facet_size=max


Update numtoword.py

fixed bahttext not working #350

Hello @wannaphongcom! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file pythainlp/util/numtoword.py:

Line 55:11: E111 indentation is not a multiple of four
Line 56:11: E111 indentation is not a multiple of four
Line 92:80: E501 line too long (83 > 79 characters)
Line 94:29: E203 whitespace before ':'
Line 94:47: E203 whitespace before ':'
Line 94:70: E203 whitespace before ':'
Line 94:80: E501 line too long (82 > 79 characters)
Line 99:14: E231 missing whitespace after ','
Line 106:15: E231 missing whitespace after ','
Line 107:39: E231 missing whitespace after ','

Coverage decreased (-0.001%) to 29.247% when pulling 299e6c7cfe1ffde80211dd2d0fbf1e1b205a6594 on fix-num_to_thaiword into c3f223cd769e67d14d1cf5c3c0526b7e088422ec on 2.1.


TS-4755: Header Frequency plugin. Initial version

Very basic version of the plugin. Additional options can be added to traffic_ctl to reset the counters, to print specific headers, maybe regex support. Additionally, the simple counters can be converted to decimal fractions.
Also, I am not convinced I am retrieving the relevant headers via TSHttpClientRespGet. Any feedback would be great.

Looks good, but I didn't see any locking when updating client_freq and origin_freq.

Aw yeah, totally meant to do that and forgot. Will update ASAP.

Should this use a TextLog rather than standard output? Then you would get log rotation, etc, which is probably desirable.

I have mixed feelings on the custom log for this. This is really for intermittent testing of behavior, similar to e.g. the memory usage dump feature. I.e. I can't imagine someone would use this in a way where it dumps the metrics more than a handful of times.

Fwiw, it's important to point out the the intent of this plugin is to provide some statistics for future analysis, our known use case is to produce an update to the set of WKS for 7.0.0.

[approve ci]

Linux build failed! See https://ci.trafficserver.apache.org/job/Github-Linux/462/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/566/ for details.

Have to run clang format, (I highly recommend installing the git hook that we have, see
https://github.com/apache/trafficserver/blob/master/tools/pre-commit

Also, I think we suggested/agreed on moving this to a new directory, like plugins/test ?

[approve ci]

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/586/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/690/ for details.


Fix codestyle and merge master into dev

Questions
Answers

Branch?
develop

Description?
Fix codestyle and merge master into dev

BC breaks?
no

Deprecations?
no

Fixed ticket?

How to test?
No QA needed

Thanks @matks


chore: results of npm audit fix

SUMMARY

On a whim, I decided to try npm audit fix on the superset-frontend directory.
A pretty large diff resulted, but that boils down to:
59 vulnerabilities (4 moderate, 54 high, 1 critical)
rather than:
72 vulnerabilities (8 moderate, 61 high, 3 critical)
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Hope CI passes? ¯\_(ツ)_/¯
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Abandon ship! Too much breakage, these things need to be done piece by piece.


INTERNAL_SERVER_ERROR: TypeError: Cannot read properties of null (reading 'assetId')

Summary
Graphql query returns an unexpected internal server error
Steps to reproduce the bug

send graphql query

query {
  paymentAddresses(
    addresses: [
      "addr1qygcsk5l4xh3y3m8j8akv93yyun06wfadrr3de02vj80xyg33pdfl2d0zfrk0y0mvctzgfexl5un66x8zmj75eyw7vgsfpl75e"
    ]
  ) {
    summary {
      assetBalances {
        asset {
          assetId
        }
        quantity
      }
    }
  }
}

Actual Result
{
  "errors": [
    {
      "message": "TypeError: Cannot read properties of null (reading 'assetId')",
      "locations": [
        {
          "line": 5,
          "column": 5
        }
      ],
      "path": [
        "paymentAddresses",
        0,
        "summary"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "stacktrace": [
            "Error: TypeError: Cannot read properties of null (reading 'assetId')",
            "    at /app/packages/api-cardano-db-hasura/dist/executableSchema.js:93:39",
            "    at Generator.throw (<anonymous>)",
            "    at rejected (/app/packages/api-cardano-db-hasura/dist/executableSchema.js:6:65)",
            "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
          ]
        }
      }
    }
  ],
  "data": {
    "paymentAddresses": [
      {
        "summary": null
      }
    ]
  }
}

Expected Result
actual balances
Environment
mainnet
Platform

[ ] Linux (Ubuntu)
[ ] Linux (Other)
[ ] macOS
[ ] Windows

Platform version
No response
Runtime

[ ] Node.js
[ ] Docker

Runtime version
No response

Summary
Graphql query returns an unexpected internal server error
Steps to reproduce the bug

send graphql query

query {
  paymentAddresses(
    addresses: [
      "addr1qygcsk5l4xh3y3m8j8akv93yyun06wfadrr3de02vj80xyg33pdfl2d0zfrk0y0mvctzgfexl5un66x8zmj75eyw7vgsfpl75e"
    ]
  ) {
    summary {
      assetBalances {
        asset {
          assetId
        }
        quantity
      }
    }
  }
}

Actual Result
{
  "errors": [
    {
      "message": "TypeError: Cannot read properties of null (reading 'assetId')",
      "locations": [
        {
          "line": 5,
          "column": 5
        }
      ],
      "path": [
        "paymentAddresses",
        0,
        "summary"
      ],
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR",
        "exception": {
          "stacktrace": [
            "Error: TypeError: Cannot read properties of null (reading 'assetId')",
            "    at /app/packages/api-cardano-db-hasura/dist/executableSchema.js:93:39",
            "    at Generator.throw (<anonymous>)",
            "    at rejected (/app/packages/api-cardano-db-hasura/dist/executableSchema.js:6:65)",
            "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
          ]
        }
      }
    }
  ],
  "data": {
    "paymentAddresses": [
      {
        "summary": null
      }
    ]
  }
}

Expected Result
actual balances
Environment
mainnet
Platform

[ ]  Linux (Ubuntu)
[ ]  Linux (Other)
[ ]  macOS
[ ]  Windows

Platform version
No response
Runtime

[ ]  Node.js
[ ]  Docker

Runtime version
No response

i'm facing the same issue.
i get this error when i run the same query with an account that has many different tokens. the account you mentioned has 50 different tokens!
in my case i just need ada balance. but i don't know how to filter it and just get ada balance. i think it would solve my own problem.
@cryptosystems6300

in my case this helped me:
`
query = """
query PaymentAddressSummary ($address: String!){
utxos (
where: {
_and: {
address: { _eq: $address }
}
}
) {
value
}
}
"""
graphql_url = "https://explorer.cardano.org/graphql/"
address = "addr1vqkzkjxm33tms7xr5qjuu92m3ygs8mpfvvyncp3atj08hlgh9n7xs"
data = {"query": query, "variables": {"address": address}}
response = requests.post(
url=graphql_url,
headers={"Content-Type": "application/json"},
data=json.dumps(data),
timeout=60,
)
utxos = response.json().get("data").get("utxos")
balance = sum([utxo['value'] for utxo in utxos])
print(balance)
`


Looking for an example - create Azure DevOps Release Pipeline

Are there any examples of how to use this module to create an Azure DevOps pipeline available? I'm especially interested in having access to a release pipeline.

Please let us know if https://www.pulumi.com/docs/guides/continuous-delivery/azure-devops/ helps. If not, would be great to get your feedback.

That guide is for how to run Pulumi inside Azure DevOps - what I'm looking for is a guide on using Pulumi to create one using the Pulumi.AzureDevOps package.

Thanks for the clarification on that. So specifically an example that uses this resource? https://www.pulumi.com/docs/reference/pkg/azuredevops/pipeline/

Would also appreciate a example on how to create pipeline. I'm not even sure if its currently implemented. I believe it would require this API https://docs.microsoft.com/en-us/rest/api/azure/devops/pipelines/pipelines/create?view=azure-devops-rest-6.0

@leezen I believe what folks are requesting is for a ReleaseDefinition resource to be made available in the Pulumi AzureDevOps integration. Currently there is only a BuildDefinition resource, which is different. I myself just came looking for docs on that resource and noticed it wasn't there (and ended up at this issue).

Closing as duplicate of #45, but also because this is a missing feature in the upstream provider.


Revert "Add Flora helper methods"

Reverts ImperialCollegeLondon/pyrealm#296
Adding all of this in one go and then restructuring it in bits makes for a horrible mess. The problem is that the cleaner structures we're aiming for don't work well as parts if the current structure. So building it up a bit at a time from scratch avoids horrible hacky patches.

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

Project coverage is 95.54%. Comparing base (1f315ba) to head (f6d0c57).
Report is 145 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #299      +/-   ##
===========================================
+ Coverage    95.29%   95.54%   +0.25%
===========================================
  Files           28       34       +6
  Lines         1720     2243     +523
===========================================
+ Hits          1639     2143     +504
- Misses          81      100      +19

Flag
Coverage Δ

95.54% <ø> (?)

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

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


Draft behavior of order execution logic

Should we draft a spec with the overall behavior we want to implement? Then translate that into actual code handled by the right module.
This could take the form of a github gist (with python pseudo code, e.g), or a google doc, or other
No strong idea on the format. I find this kind of doc interesting: https://docs.hummingbot.io/strategies/twap
note the activity diagram that helps build a finite state machine (pseudo code can be enough) that could be tick-ed from a task queue, eg.
This could be the opportunity to clarify behavior (eg: are we supposed to have open orders overnight? what do we do with open orders intraday: what is the trigger for us to decide to replace their price? Should a TargetPositionRequest be considered constant during a day? etc)

I made a quick diagram of the execution logic, I hope this helps.

A few notes:

I think it would be wise to add a timeout to this loop, if reached it'll place a market order
Update price can use the order book and match the price of the 3rd best bid/ask
Security should lose the base currency 'BTC/USD' becomes 'BTC' then we can add an additional field execution_symbold to the security model which defaults to USD base currency but can be manually changed in the admin panel. The logic for deciding this isn't trivial and doesn't need to be automated right now

Drafted in a google doc, open for comment.
I'm considering closing this issue, unless somebody is actively working on this


[Table] Strange bug with Table in Tabs

Describe the bug
I set tabs and I clicked on tab with table I get data by API but table has strange view:

TabPanel in code:

I notice that if open/close chrome devtools the table become normal
Reproduction
/
Steps to reproduce
No response
System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vexip UI issue.
[X] The provided reproduction is a minimal reproducible example of the bug.

You can try using refresh method of tanble instance after tab switched.

TabPanal have no show event, you should view the docs of Tabs.

I dont understnad when I need refresh table, on which event? Could you pls send example demo

thx finally it works


Failure to implicitly open existential on initialization through factory method

Describe the bug
Per the thread here:  SE-0352 allows the implicit opening of existentials only when the generic type occurs exactly once in the function signature. In the sample code from the thread's first post, the init of S is implicitly using the generic type twice.
protocol P {
  associatedtype A
  func getA() -> A
}

struct S<T: P> {
    var s: T
}

func testOpenSimple(p: any P) {
  let _ = S(s: p) // **error**, Type 'any P' cannot conform to 'P'
}

An alternative approach was proposed here by @jckarter that involves a static factory method that returns the S as a protocol existential or opaque return type.
Applying this approach still yields the same error Type 'any P' cannot conform to 'P' and @jckarter thought it seemed like a bug.
To Reproduce

Attempt to run the following Swift code in a Playground with Xcode 14 beta 2 (Swift 5.7)

protocol P {
  associatedtype A
  func getA() -> A
}

protocol Q {}
struct S<T: P>: Q {
  var s: T

  static func make(s: T) -> some Q { return S(s: s) }
}

func testOpenSimple(p: any P) {
  let q = S.make(s: p) // q has type `any Q`
}

Expected behavior
Should build successfully and allow the initialization of S through the factory method resulting in an instance of any Q living in q
Screenshots

Environment (please complete the following information):

OS: [e.g. macOS 11.0] macOS 12.4/iOS 16.0
Xcode Version/Tag/Branch: 14 beta 2

Additional context

A temporary workaround
func testOpenSimple(p: any P) {
    // Error
    //  let q = S.make(s: p) // q has type `any Q`

    func bridge2<T: P>(_ s: T) -> some Q {
        S.make(s: s)
    }

    let q = bridge2(p)
}


Another given priority scheme to ensure transitivity

It applies the following tweaks:

Do treat givens as higher priority than implicits. The previous logic was faulty, but is corrected now.
Drop special handling of NotGiven in prioritization. The previous logic pretended to do so, but was ineffective.
Do use the old priority scheme for implicit/implicit pairs.
Do use owner score for givens as a tie breaker if after all other tests we still have an ambiguity.

Alternative to #21305

@WojciechMazur Can we test this one as well with the OpenCB?

I've started the OpenCB for 3.5.0-RC6 + this change so we can compare it directly with the results from alternative PR and don't need to care of other issues present on main. I should have results in ~3h

There seems to be less arnings in general when compared to previous solution
Given stats for 3.5.0-RC6 (baseline)
Given alternatives choice: Some(the second alternative) - 483
Given alternatives choice: Some(none - it's ambiguous) - 762
Given alternatives choice: Some(the first alternative) - 264
Projects with changed alternatives warnings - 23

Given stats for 3.5.0-RC6 + #21305
Given alternatives choice: Some(the second alternative) - 1868
Given alternatives choice: Some(none - it's ambiguous) - 21
Given alternatives choice: Some(the first alternative) - 831
Projects with changed alternatives warnings - 88

Given stats for 3.5.0-RC6 + this PR
Given alternatives choice: Some(the second alternative) - 1437
Given alternatives choice: Some(none - it's ambiguous) - 22
Given alternatives choice: Some(the first alternative) - 215
Projects with changed alternatives warnings - 28

There is 1 new ambiguous choice in com-lihaoyi/upickle (it was not ambiguous in neither of other revisions)
Search [1]: ReadersVersionSpecific_this.Reader[upickle.Gadt2.IsDir[V]] : choice=none
    -  (upickle.Gadt2.IsDir.rw : [V²] (implicit evidence$1: upickle.default.ReadWriter[V²]): upickle.default.ReadWriter[upickle.Gadt2.IsDir[V²]] )
    -  (upickle.default.superTypeReader : [T, V² >: T] (implicit evidence$1: scala.deriving.Mirror.ProductOf[T], evidence$2: upickle.default.Reader[V²], evidence$3: scala.deriving.Mirror.SumOf[V²], x$1: scala.util.NotGiven[upickle.core.CurrentlyDeriving[V²]]): upickle.default.Reader[T] )

Here're links to each of the types:
ReadWriter
default.superTypeReader
Gadt2.IsDir and it's rw implicit instance
No new compilation failures in OpenCB, lemonlabsuk/scala-uri is not building successfully (failed previously)

There is 1 new ambiguous choice in com-lihaoyi/upickle (it was not ambiguous in neither of other revisions)

OK, here's what goes on here.

superTypeReader is a given and isDir.rw is an implicit.
Both superTypeReaderandisDir.rw` are polymorphic
superTypeReader's type variables can be instantiated to match a supertype of isDir.rw's type. This would normally
make isDir.rw chosen over superTypeReader except that isDir.rw is now an implicit and therefore loses the comparison. The result is that isDir.rw is not better than superTypeReader in the "wins type" contest.
In the other direction we alsp get a "not better" since isDir.rw's type variable cannot be instantiated to match superTypeReade's result at all.

Based on the results in #21328 should I run additional OpenCB build with additional https://github.com/scala/scala3/pull/21325/commits/5d584078da2b9db6a98821fdc3de11a8cf5dd7d7 change?

No I think we should hold off with l https://github.com/scala/scala3/commit/5d584078da2b9db6a98821fdc3de11a8cf5dd7d7 unless the other PR #21328 is disappointing. I think the other PR is both nicer and might solve more problems.

Superseded by #21318


fix(deps): update images to latest

This PR contains the following updates:

Package
Type
Update
Change

icr.io/ibm-iac-charts/sysdig-deploy
helm_release
minor
1.52.7 -> 1.55.0

icr.io/ibm-iac/agent-kmodule

minor
13.1.1 -> 13.2.0

icr.io/ibm-iac/agent-slim

minor
13.1.1 -> 13.2.0

icr.io/ibm-iac/vuln-host-scanner

minor
0.9.1 -> 0.10.0

icr.io/ibm-iac/vuln-runtime-scanner

minor
1.6.12 -> 1.7.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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


libssl: Make some global data constant

Make ssl_cert_info read-only
Make bitmask table read only
Make nid_to_group read-only
Make scsv read-only
QUIC TSERVER: Fix erroneously static variable

This pull request is ready to merge

Merged to master. Thanks for the reviews.


Update/dependencies

When I tried to run the tests, I was getting the following error during build:
><EMAIL_ADDRESS>build /Users/fleur/work/rug/ol-mapbox-style
> webpack-cli --config ./webpack.config.olms.js && webpack-cli

/Users/fleur/work/rug/ol-mapbox-style/node_modules/webpack-cli/bin/config-yargs.js:89
				describe: optionsSchema.definitions.output.properties.path.description,
				                                           ^

TypeError: Cannot read property 'properties' of undefined
    at module.exports (/Users/fleur/work/rug/ol-mapbox-style/node_modules/webpack-cli/bin/config-yargs.js:89:48)
    at /Users/fleur/work/rug/ol-mapbox-style/node_modules/webpack-cli/bin/webpack.js:60:27
    at Object.<anonymous> (/Users/fleur/work/rug/ol-mapbox-style/node_modules/webpack-cli/bin/webpack.js:515:3)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
    at startup (internal/bootstrap/node.js:279:19)

The fix was upgrading the npm packages webpack and webpack-cli.
While I was in there, I also updated everything npm outdated listed.  The new documentation package changed the readme, and the new eslint and eslint-config-openlayers required some lint fixes.
Tests pass, but I haven't done any testing past that.

Ok.  Didn't realize the tests didn't cover the examples.  FYI, the 'TileJSON vector tiles' example is not working from the master tree due to https://osm.tegola.io/capabilities/osm.json not being available.  It returns a 503.  I will open a separate issue for that.
I'll also open a pull request just for the webpack upgrade to get that out of the way.

Yep, you were right, there is a breaking change in @mapbox/mapbox-gl-style-spec@13 that broke the GeoJSON Inline example.  Aside from the one getting a 503, this was the only example that appeared to be broken.  Since I don't have enough domain knowledge yet to tackle that one, I'm downgrading it back to what it was. (For reference: https://github.com/mapbox/mapbox-gl-js/pull/6521.)
Also, can you elaborate a bit on the var -> let/const changes please?  I get hoisting and scope.  I'm confused because there's no src/ and the top-level stylefunction.js file doesn't have any changes.  Did you mean processStyle() in index.js?  That seems likely.  I'll go ahead and look that over.  Please let me know if I interpreted that right, thanks.

Sorry for the confusion. Yes, I meant the changes in toplevel index.js.


Consider adding version to init.

It might be nice to add __version__ to init as well as add a version mgmt setup.cfg file with bump2version.
Also, it might be nice to add a MANIFEST.in as well.

Agreed to all.


prometheus store data into influxDB

can prometheus store data into influxdb

see prometheus --help
...
   -storage.remote.influxdb-url
      The URL of the remote InfluxDB server to send samples to. None, if
      empty.

   -storage.remote.influxdb.database "prometheus"
      The name of the database to use for storing samples in InfluxDB.

   -storage.remote.influxdb.retention-policy "default"
      The InfluxDB retention policy to use.

   -storage.remote.influxdb.username
      The username to use when sending samples to InfluxDB. The
      corresponding password must be provided via the INFLUXDB_PW environment
      variable.
...

https://prometheus.io/docs/introduction/roadmap/#long-term-storage

./prometheus -config.file=prometheus.yml -storage.remote.influxdb-url=http://<IP_ADDRESS>:8086 -storage.remote.influxdb.database=prometheus -storage.remote.influxdb.retention-policy=default -storage.remote.influxdb.username=admin
I am using this command to write data into Influx DB. But seems like the InfluxDB for database Prometheus is empty. Something I am missing ?

@jeunii Please ask usage questions on the users mailing list or the IRC channel: https://prometheus.io/community/


Crash on Joining Server [BUG]

Greeeetings
I'm playing on a custom pack with my friend, here are the mods (in the form of screenshots of my mods folder):
https://gyazo.com/068c5f936e7314a50369349b710d7662
https://gyazo.com/f7aa1d12872660967c6e5052f2148b5d
It started crashing this morning, I was playing on the server without a problem last night.
Here's the log:
http://pastebin.com/Pd5EjgT7
I can't find a thing on this. Anyone got any ideas?

i've found 2 Optifines. leave only 1.... You Shutdown the mod in night and when u open in morning it's crash ??

Issue resolved, apparently someone spawned in a couple hundred villagers too many and the server had to restart. Thanks for pointing out the optifine issue though!


0x526728dbc96689597f85ae4cd716d4f7fccbae9d

Add msUSD token on Base
Please review the following token assets:
📑 Description

Token Name: msUSD
Project Website: https://app.metronome.io
Explorer URI: https://basescan.org/token/0x526728dbc96689597f85ae4cd716d4f7fccbae9d

✅ Checks

[x]  I created a new folder with the token address (all in lowercase for EVM chains, case sensitive for Solana)
[x]  I added the token's logo as a 32x32 PNG file, named logo-32.png
[x]  I added the token's logo as a 128x128 PNG file, named logo-128.png
[x]  I added the token's logo as a SVG file, named logo.svg
[x]  My SVG logo is a proper SVG and not some base64 stuff
[x]  My documentation/website clearly display the token address somewhere

can you do the following please:

delete the extra.png on some files
move the logos to a sub-directory with the token address as the name (make sure the addresses are lowercase)


Use Sodiumoxide Keys

There's no need to re-implement PublicKey and SecretKey structs within revault_net. Instead use PublicKey and SecretKey from sodiumoxide which already have conversion functions and memory zeroing for SecretKey when it is dropped.
Fixes #29
based on #33

Needs rebase after #33 merge

Neat. Could we just keep a typedef for abstracting out the key use ?

Sure, but why?

Actually, re-export it anyways as we'll need real types no matter what

Alright, did the change myself as i need it downstream for revaultd.

ACK 92e923d


fix tdp resume command

Which issue(s) this PR fixes

Fixes #361
Additional comments

ORM model may be improved to automatically query the operation logs ordered by order. This could be done in another issue.
Agreements

[X] I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004.
[X] I hereby agree to grant TOSIT a copyright license to use my contributions.

Forced pushed after rebase on matser.


fix Correct if syntax

Closes #166

Let's test all of the combinations:
FOO=2
if [[ $FOO -eq 1 ]]; then
    echo "FOO is 1";
elif [[ $FOO -eq 2 ]]; then
    echo "FOO is 2";
else
    echo "FOO is not 1 or 2";
fi

and
FOO=2
if [[ $FOO -eq 1 ]]; then
    echo "FOO is 1"
elif [[ $FOO -eq 2 ]]; then
    echo "FOO is 2"
else
    echo "FOO is not 1 or 2"
fi

and
FOO=2
if [[ $FOO -eq 1 ]];
then
    echo "FOO is 1";
elif [[ $FOO -eq 2 ]];
then
    echo "FOO is 2";
else
    echo "FOO is not 1 or 2";
fi

and
FOO=2
if [[ $FOO -eq 1 ]]
then
    echo "FOO is 1";
elif [[ $FOO -eq 2 ]]
then
    echo "FOO is 2";
else
    echo "FOO is not 1 or 2";
fi

I'll add these to the tests crate for now. But in the future, we should add a way to properly test the scripts in the script folder as well.

Agreed.
I'll go ahead and merge this then.


Rebase arcanist for on phorge

Rebase our fork of arcanist off upstream.The new upstream for this project is https://we.phorge.it/source/arcanist.git. This also adds in one extra commit to remove a call to utf8_decode, this function was deprecated as of php 8.2

lgtm

@dkhenry What is the motivation for this change? I think rebasing onto a fork requires further scrutiny and slow rollout before landing.
I suspect the motivation is as mentioned in the description, being able to use php8? If so, lets cherry-pick that one over by itself, unless there are features/fixes we want in phorge

@joeljeske this is entirely so we can use php8. I initially tried to just spot fix our fork to work on php8, but ran into a lot of problems which is when I investigated rebasing off upstream. The current upstream philicity/arcanist is no longer supported, but development has moved to phorge. Even with that I needed 86f33419c928fe9dd73ab791f10f9105060e124c in addition to the rebase to get it working on 8.2 which is the current php version.


Added another possible path for the weather information

 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.


Maximum call stack size exceeded...

I'm using a tweaked version of this cytoscape.js example (http://www.wineandcheesemap.com/).
I'm trying to plot a hierarchical tree with 3452 nodes and 3451 edges.
Firstly, I tried using:

dagre 0.7.4
cytoscape.js 2.7.12
cytoscape-dagre 1.6.0
I get the following error:

Maximum call stack size exceeded
at .../dagre.js:2368:61
at arrayReduce (.../dagre.js:6112:31)
at Function. (.../dagre.js:8124:19)...

I tried then with the newest releases:

dagre 0.7.4
cytoscape.js 3.2.15
cytoscape-dagre 2.2.1

I get the same error as well.
Just to clarify, line 2368 here starts with this (I beautified the file. Original file says line 1).
var min = _.reduce(blockG.outEdges(v), function (min, e) {
  pass2(e.w);
  return Math.min(min, xs[e.w] - blockG.edge(e));
}, Number.POSITIVE_INFINITY);

EDIT: I tried chopping the root (bringing it down to 3451 nodes and 1369 edges), but the error persists.

It worked using 0.8.2 release. It's quite slow, but it does its job.


[Feature] enable use subquery and CTE in MV

What type of PR is this：

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Support CTE and subquery in async MV.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[x] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] I have checked the version labels which the pr will be auto backported to target branch

run starrocks_fe_unittest

run starrocks_admit_test

@Mergifyio backport branch-2.5

@Mergifyio rebase

run starrocks_admit_test

run starrocks_fe_unittest

[FE PR Coverage Check]
:heart_eyes: pass : 4 / 4 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/analyzer/MaterializedViewAnalyzer.java
4
4
100.00%
[]

run starrocks_admit_test


Changing color of the selected row

I would like to change the color of a selected row to have something like this

Now in my code i have
                                 <vue-table ref="vuetable"
                               @vuetable:pagination-data="onPaginationData"
                               @vuetable:row-clicked="onRowCLicked"
                    >

                   onRowClicked(row){
                       //here now change row color
                   }

How do i change the background of the selected row

Use row-class prop.


[stable/jenkins] fix chart errors

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @torstenwalter

/ok-to-test

/approve

/retest

@kimxogus could you rebase you branch and fix the version conflict, please?

/test

/test all

@torstenwalter just rebased and fixed version conflict :)

@kimxogus Thank you for the PR!


Guard for choosing visualization types

Currently, setting visualization type to "bla" will lead to silent failure of visualization of a given field. We should set possible visualization types and compare on launch whether the set visualization types in all corpus definitions matches any of the predefined types.

closed by #1226


[DASH1-102] Add 'Participant' enrollment status

This is a resurection of #530 and #532 for a supplemental release.
[DASH1-102]

Also wanted to highlight the version parameter on this one (not to be confused with the URL segment v1). It is what will allow us to release this after the RDR does without breaking backwards compatibility.


Support more adapters including Mysql2, Mysql2Spatial and PostGIS

This makes the ignore mode work for more adapters than just Sqlite, PostgreSQL and (a bit outdated) MySQL adapters.

Thank you for contributing!


Update Constants.java

Went through the tutorial and compiling failed because by default (as per documentation) the cloud uses https/realms.
Since our documentation assumes Realm Cloud for a first user, we should use https/realms (e.g. SSL secure) channel by default.

@cmelchior : Can you review the above pull request.
Similar issue was found by another user (see pull request #51 ).


Flaky AWS Provisioner Tests

Specifically the multi-node and spot bid tests.

This might be relevant: https://github.com/BD2KGenomics/toil/pull/680

And this: https://github.com/BD2KGenomics/toil/pull/753


Error from workflow worker: "Failed to connect to Temporal server"

Pod for the workflow-worker deployment is failing with the following logs:
wait-for-it.sh: waiting for mydatabase.myregion.rds.amazonaws.com:5432 without a timeout
wait-for-it.sh: mydatabase.myregion.rds.amazonaws.com:5432 is available after 0 seconds
not untarring the bundle
{"message":"[process service types] WORKFLOW_TEMPORAL_WORKER","level":"info","timestamp":"2023-05-22T13:26:33.658Z"}

Warning: POSTGRES_SSL_REJECT_UNAUTHORIZED is currently set to 'false'. This will default to 'true' in a future version of Retool, which may break connections to databases with self-signed SSL/TLS certificates. To prepare for this change, either explicitly set POSTGRES_SSL_REJECT_UNAUTHORIZED=false or configure a custom certificate chain by setting POSTGRES_CUSTOM_SSL_CERT_PATH & POSTGRES_CUSTOM_SSL_CA_FILE_NAME (and optionally POSTGRES_CUSTOM_SSL_CERT_FILE_NAME & POSTGRES_CUSTOM_SSL_KEY_FILE_NAME) — see https://docs.retool.com/docs/environment-variables.

{"message":"Not configuring StatsD...","level":"info","timestamp":"2023-05-22T13:28:22.141Z"}
{"message":"Not configuring StatsD...","level":"info","timestamp":"2023-05-22T13:28:22.144Z"}
Setting http and https agent maxSockets to 25
(node:18) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at<EMAIL_ADDRESS>Update this package.json to use a subpath pattern like "./*".
(Use `retool_backend --trace-deprecation ...` to show where the warning was created)
(node:18) [LRU_CACHE_UNBOUNDED] UnboundedCacheWarning: TTL caching without ttlAutopurge, max, or maxSize can result in unbounded memory consumption.
(node:18) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at<EMAIL_ADDRESS>Update this package.json to use a subpath pattern like "./*".
(node:18) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at<EMAIL_ADDRESS>Update this package.json to use a subpath pattern like "./*".
(node:18) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /packages/common/package.json imported from /packages/common/build/workflows/types.js.
Update this package.json to use a subpath pattern like "./*".
(node:18) [LRU_CACHE_OPTION_maxAge] DeprecationWarning: The maxAge option is deprecated. Please use options.ttl instead.
(node:18) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /packages/workflowsBackend/package.json imported from /packages/workflowsBackend/build/runBlocksLambdaHandler.js.
Update this package.json to use a subpath pattern like "./*".
(node:18) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.
{"message":"Rechecking license status...","level":"info","timestamp":"2023-05-22T13:28:23.254Z"}
{"message":"license check http response code: 200","level":"info","timestamp":"2023-05-22T13:28:23.803Z"}
{"message":"License key feature flag overrides: {}","level":"info","timestamp":"2023-05-22T13:28:23.806Z"}
{"message":"Updated license status from licensing server","level":"info","timestamp":"2023-05-22T13:28:23.811Z"}
{"message":"installing temporal runtime","level":"info","timestamp":"2023-05-22T13:28:23.842Z"}
{"message":"creating temporal worker connection","level":"info","timestamp":"2023-05-22T13:28:23.844Z"}
{"message":"Scheduling UpdateTimedOutWorkflows","level":"info","timestamp":"2023-05-22T13:28:23.845Z"}
{"message":"creating temporal worker","level":"info","timestamp":"2023-05-22T13:28:23.962Z"}
{"label":"worker","level":"info","message":"Creating worker","timestamp":1684762103963,"options":{"namespace":"workflows","identity":"18@retool-workflows-test-retool-wf-workflow-worker-74948868d62k78z-workflows-workflows","shutdownGraceTime":"11 minute","maxConcurrentActivityTaskExecutions":10,"maxConcurrentLocalActivityExecutions":10,"enableNonLocalActivities":true,"maxConcurrentWorkflowTaskExecutions":10,"stickyQueueScheduleToStartTimeout":"10s","maxHeartbeatThrottleInterval":"60s","defaultHeartbeatThrottleInterval":"30s","isolateExecutionTimeout":"5s","workflowThreadPoolSize":8,"maxCachedWorkflows":200,"enableSDKTracing":false,"showStackTraceSources":false,"debugMode":false,"interceptors":{"activityInbound":[null,null,null],"workflowModules":["/snapshot/retool_development/node_modules/@temporalio/worker/lib/workflow-log-interceptor.js"]},"sinks":{"defaultWorkerLogger":{"trace":{},"debug":{},"info":{},"warn":{},"error":{}}},"bundlerOptions":{},"workflowBundle":{"codePath":"/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/workflowsExecutor-workflows-bundle.js"},"activities":{},"taskQueue":"workflows","connection":{"nativeClient":{},"referenceHolders":{}},"shutdownGraceTimeMs":660000,"stickyQueueScheduleToStartTimeoutMs":10000,"isolateExecutionTimeoutMs":5000,"maxHeartbeatThrottleIntervalMs":60000,"defaultHeartbeatThrottleIntervalMs":30000,"loadedDataConverter":{"payloadConverter":{"converterByEncoding":{},"converters":[{"encodingType":"binary/null"},{"encodingType":"binary/plain"},{"encodingType":"json/plain"}]},"failureConverter":{"options":{"encodeCommonAttributes":false}},"payloadCodecs":[]}}}
{"label":"worker","level":"warn","message":"Ignoring WorkerOptions.bundlerOptions because WorkerOptions.workflowBundle is set","timestamp":1684762103963}
{"message":"Ran into error when scheduling UpdateTimedOutWorkflows ServiceError: Failed to connect to Temporal server","level":"error","timestamp":"2023-05-22T13:28:38.280Z"}
/snapshot/retool_development/node_modules/@temporalio/client/lib/connection.js:167
                            throw new errors_1.ServiceError('Failed to connect to Temporal server', { cause: err });
                                  ^

ServiceError: Failed to connect to Temporal server
    at /snapshot/retool_development/node_modules/@temporalio/client/lib/connection.js:167:35
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at runNextTicks (node:internal/process/task_queues:65:3)
    at processTimers (node:internal/timers:499:9)
    at async getTemporalClient (/snapshot/retool_development/backend/transpiled/temporal/common/client.js)
    at async startUpdateTimedOutWorkflows (/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/client.js)
    at async Object.main (/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/main.js) {
  cause: Error: 4 DEADLINE_EXCEEDED: Deadline exceeded
      at Object.callErrorFromStatus (/snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
      at Object.onReceiveStatus (/snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/client.js:195:52)
      at /snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/call-stream.js:111:35
      at onReceiveStatus (/snapshot/retool_development/node_modules/@temporalio/client/lib/grpc-retry.js:134:25)
      at Object.onReceiveStatus (/snapshot/retool_development/node_modules/@temporalio/client/lib/grpc-retry.js:137:17)
      at InterceptingListenerImpl.onReceiveStatus (/snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/call-stream.js:106:23)
      at Object.onReceiveStatus (/snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:365:141)
      at Object.onReceiveStatus (/snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:328:181)
      at /snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/call-stream.js:188:78
      at processTicksAndRejections (node:internal/process/task_queues:78:11)
      at runNextTicks (node:internal/process/task_queues:65:3)
      at processTimers (node:internal/timers:499:9)
  for call at
      at ServiceClientImpl.makeUnaryRequest (/snapshot/retool_development/node_modules/@temporalio/client/node_modules/@grpc/grpc-js/build/src/client.js:163:34)
      at Service.rpcImpl (/snapshot/retool_development/node_modules/@temporalio/client/lib/connection.js:206:27)
      at Service.rpcCall (/snapshot/retool_development/node_modules/@temporalio/proto/node_modules/protobufjs/src/rpc/service.js:94:21)
      at executor (/snapshot/retool_development/node_modules/@protobufjs/aspromise/index.js:44:16)
      at new Promise (<anonymous>)
      at Object.asPromise (/snapshot/retool_development/node_modules/@protobufjs/aspromise/index.js:28:12)
      at Service.rpcCall (/snapshot/retool_development/node_modules/@temporalio/proto/node_modules/protobufjs/src/rpc/service.js:86:21)
      at Service.getSystemInfo (eval at Codegen (/snapshot/retool_development/node_modules/@protobufjs/codegen/index.js:50:33), <anonymous>:4:15)
      at /snapshot/retool_development/node_modules/@temporalio/client/lib/connection.js:161:82
      at AsyncLocalStorage.run (node:async_hooks:322:14)
      at Connection.withDeadline (/snapshot/retool_development/node_modules/@temporalio/client/lib/connection.js:216:46)
      at /snapshot/retool_development/node_modules/@temporalio/client/lib/connection.js:161:32
      at processTicksAndRejections (node:internal/process/task_queues:96:5)
      at async getTemporalClient (/snapshot/retool_development/backend/transpiled/temporal/common/client.js)
      at async startUpdateTimedOutWorkflows (/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/client.js)
      at async Object.main (/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/main.js) {
    code: 4,
    details: 'Deadline exceeded',
    metadata: Metadata { internalRepr: Map(0) {}, options: {} }
  }
}

The pod then restarts as the command has exited with exit code 1, eventually going into CrashLoopBackOff.
This seems to be telling me that the workflow-worker pod can't connect to temporal. But if I port-forward to temporal from my local machine, I can talk to temporal using tctl, so I think temporal is working. I suspect this means something is wrong in the config being passed to the workflow-worker pod.

All pods other than the workflow-worker are ready, and are not restarting.
What can I do to debug and fix this?

This appears to have been fixed by changing image.tag from 2.117.3 to 2.119.3.
I also tried latest in the 2.117 series, which was 2.117.9, and this also seemed to fail, so I think something is broken with workflows in 2.117 that is fixed in 2.119. But https://github.com/tryretool/retool-workflows-helm#usage says "The minimum supported image for Retool Workflows is 2.108.4", so I would expect 2.117.[latest] to work.
From some more checking:

tag
works with workflows

2.117.3
:x:

2.117.9
:x:

2.119.1
:heavy_check_mark:

2.119.3
:heavy_check_mark:

(it appears there are no tags in the semver range between 2.117.9 and 2.119.1 on Docker Hub:
$ curl -s "https://hub.docker.com/v2/namespaces/tryretool/repositories/backend/tags?page_size=100" | jq -r '.results[] | .name' | grep -v -e 'latest$' -e '-enterprise$' | sort -rV | grep '^2\.11[7-9]'
2.119.3
2.119.2
2.119.1
2.117.9
2.117.8
2.117.7
2.117.6
2.117.5
2.117.4
2.117.3
2.117.2

)
So perhaps this fix needs to be backported to the 2.117 release line. However, from https://updates.retool.com/en/whats-new-in-self_hosted-retool-2119-45487736, none of the "fixed" items appear to have anything to do with this, so hard to tell what is going on.


332 add core ui based theme with build process

Q
A

Branch
master

Bug fix?
no

New feature?
yes

BC breaks?
no

Deprecations?
no

Tests pass?
unknown

Fixed issues
chameleon-system/chameleon-system#332

License
MIT

This PR contains everything to...

re-install CoreUI
build CourUI using CoreUI's own build process
store scss variables to override CoreUI's styles
add custom scss as imports
build CoreUI with all overrides and additional scss files
develop using a watch mode

See customer/vendor/chameleon-system/chameleon-base/src/CoreBundle/Resources/Theme/readme.md for more details.

Move to this PR: https://github.com/chameleon-system/chameleon-base/pull/387


unit test added for task result type mismatch

Changes

We fixed an issue where the results were added to taskrun status with the modified types and zero values when they were initialized to a value of different type. Thank you @Yongxuanzhang 🙏
Adding a unit test to make sure we catch such bugs when only some of the results are not initialized to expected types.
Signed-off-by: pritidesai<EMAIL_ADDRESS>Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[ ] Follows the commit message standard
[ ] Meets the Tekton contributor standards (including
functionality, content, code)
[ ] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[ ] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/lgtm
Thanks for adding test case! This covers the case which contains both valid and invalid results


config: make client-id configurable

[x] docker entry point env variable
[ ] update chart template

Was this issue closed through https://github.com/SwissDataScienceCenter/renga-ui/pull/186?


User Locations Fix

Bug Fixes

Fixed User Locations for super users
Added a previously removed use statement for Collection

[Delivers#110698174]

You are mixing some concerns there. Please move stuff related to Locations to separate methods, don't mix them with standard User edit and create actions.

@wnowicki Took a standard index approach like in Controller. Thoughts?

is it really ready ?

@wnowicki Yeah, really, ready! 😂

Happy.
Please do marge for me. As I'm tryng to test framework change on TEST.


[HUDI-7709] ClassCastException while reading the data using TimestampBasedKeyGenerator

Change Logs
Before this MR for TimestampBasedKeyGenerator we got
Failed to cast value `2004-02-29 01` to `LongType` for partition column `ts`

when we read data by Spark SQL.
listPartitionPaths() is called with parsePartitionColumnValues(), and we got ClassCastException during parsing of partition paths. But we couldn't reconstruct partition column values from partition paths when TimestampBasedKeyGenerator of SCALAR, UNIX_TIMESTAMP or EPOCHMILLISECONDS types is used, due to lost information after corresponding processing of values.
This MR fixes ClassCastException, but there are still not finished separate tasks (old ones) mentioned in the added TestSparkSqlWithTimestampKeyGenerator:

Fix for [HUDI-3896] overwrites shouldExtractPartitionValuesFromPartitionPath in BaseFileOnlyRelation. I couldn't figure out during fixing this issue, should it be fixed, or it should be left as it is.

There is no logic for shouldExtractPartitionValuesFromPartitionPath in HoodieBaseHadoopFsRelationFactory. Couldn't find a corresponding task, so created a new one, HUDI-7925.

Impact
Fixes ClassCastException. Save previous behavior for unaffected cases.
Risk level (write none, low medium or high below)
Low. Affects only if TimestampBasedKeyGenerator of SCALAR, UNIX_TIMESTAMP or EPOCHMILLISECONDS types is used. There is added TestSparkSqlWithTimestampKeyGenerator.
Documentation Update
No need.
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[ ] CI passed

Bring back previous behavior for TimestampBasedKeyGenerator of DATE_STRING type in ffe3270a736b0a817a4f04a53133adb471b6577b.

Bring back previous behavior for TimestampBasedKeyGenerator of DATE_STRING type in 289a413daa15426844822a50e80ae09d79a4f262

Got only 1 fail with
Error:    ITTestConsistentBucketStreamWrite.testWriteMOR » IO Failed to delete temp dire...

It looks like there is some flaky problem. I will try to fix it in a separate MR, and restart CI for this MR.


Generate noise as a dynamic background view in iOS

This is really not an issue but mostly an interrogation on my part.
I was wondering if I could generate dynamic noise background patterns and include them in my iOS app.
Questions:

Would that be feasible as far as rendering time?
Can I leverage the png creation capability of the tests and display the generated image directly in a view?
Would it be possible to seed the noise generator to support a light and dark pattern to follow the iOS app environment (light or dark)?

Thanks

i don't know if the library can generate noise animations in real time, but one thing you could do is bake an animation of the noise to run in a loop. to make it seamless, i suggest sampling one of the three-dimensional noises in a ring-like motion. you’d have to implement a little bit of geometric math for that though.

you could certainly use PNG, but i’m not an iOS expert and there might be a better file format for this.

what i would recommend is to generate primary color channels, and then map each of those channels to a light or dark hue to customize the appearance.

Thanks a bunch for this. I was unclear in my previous message but my initial goal was to display a single generated noise image as a background view.
However I will surely rethink this and possibly have some subtle motion / animations between various images.
Will play around with this and report back if I get stuck. Thanks.


Unstable wrap tabs

Issue Type: Bug
Pre-condition
Shoud be opened at least  10 tabs
Steps to reproduce

Window shoud be not opened to full screen
Resize the windows
Expected: Tabs grouped all the time
Actual: Sometimes tabs not grouped

VS Code version: Code 1.53.1 (5d424b828ada08e1eb9f95d6cb41120234ef57c7, 2021-02-08T23:29:42.785Z)
OS version: Windows_NT x64 10.0.19042

/gifPlease


runtime: fatal error: stoplockedm: inconsistent locking

freebsd-386-gce101 at 6270c5ac28e89322268acd92c14a7a490a53e3a1
https://build.golang.org/log/ce4de82bc9e073e9f2f95b49b2f20ce6954d1876
##### ../misc/cgo/errors
test union2 failed unexpectedly with expensive checks: exit status 2
=== test union2 output ===
fatal error: stoplockedm: inconsistent locking

runtime stack:
runtime.throw(0x80a1f7b, 0x21)
	/tmp/workdir/go/src/runtime/panic.go:596 +0x76
runtime.stoplockedm()
	/tmp/workdir/go/src/runtime/proc.go:1758 +0x4b
runtime.schedule()
	/tmp/workdir/go/src/runtime/proc.go:2150 +0x287
runtime.goschedImpl(0x38e000f0)
	/tmp/workdir/go/src/runtime/proc.go:2270 +0xcc
runtime.gopreempt_m(0x38e000f0)
	/tmp/workdir/go/src/runtime/proc.go:2285 +0x26
runtime.newstack(0x0)
	/tmp/workdir/go/src/runtime/stack.go:1056 +0x25c
runtime.morestack()
	/tmp/workdir/go/src/runtime/asm_386.s:409 +0x6e

goroutine 1 [runnable]:
main._Cfunc_f(0x38e74000)
	dir29/_obj/_cgo_gotypes.go:47 +0x2d
main.main()
	/tmp/cgoerrors981982312/src/dir29/t29.go:11 +0x56

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
	/tmp/workdir/go/src/runtime/asm_386.s:1629 +0x1
=== end of test union2 output ===
exit status 1
2016/12/02 21:39:29 Failed: exit status 1
2016/12/02 21:39:29 FAILED

Austin, is this new?

This is the only instance of "stoplockedm: inconsistent locking" ever.
I wonder if this is related to #15658 and is just random memory corruption. There's a lot of forking/execing going on around this test, though the crashing binary itself didn't fork/exec.
Obviously it's too late for this instance, but I wonder if it would be possible to get core dumps or something out of the builders for runtime crashes. Something to make post-mortem debugging easier than feeling around in the dark.

Closing since this has only happened once. Reopen if we ever see this again.

I have get the same issue, but it is random error, I made some changes inside the runtime but nothing that affect this part directly (I mean the stoplockedm), but as I'm compiling the whole language many times per day, so I'm getting this error each 5 of 10 times when I run ./all.bash.

This issue was closed a long time ago.  Whatever you are encountering, it is a different problem.  Please open a new issue.  But please only open the issue if you are encountering a problem with unmodified sources.  If you only encounter the problem with your runtime modifications, then the problem is almost certainly due to your modifications.

I do not believe that any change that I made has cause this error, as you see @bradfitz got the same, with the same version go1.8, I'll not open a new issue cause I made some modifications at runtime, but I'm still comparing with a stable release of 1.8, if I catch this error again I will report.

I do not believe that any change that I made has cause this error, as you see @bradfitz got the same, with the same version go1.8, I'll not open a new issue cause I made some modifications at runtime, but I'm still comparing with a stable release of 1.8, if I catch this error again with the stable version I will report.


Decoding ?

Hey @lucidrains I from classical ML and Speech Synthesis space, and I am sorta new to the NLP space and I have read this article with regards to decoding.
https://huggingface.co/blog/how-to-generate
I am wondering if the same techniques could be applied to character level embeddings? I am trying to find literature on the subject but I have hit a wall. If you know any resources a survey perhaps that would be helpful. It seems like the only thing that would work in a naive fashion here is greedy decoding

nevermind figured it out.


Application SSR Angular 7: Cannot read property 'forEachChild' of undefined

🐞 Bug report
Command (mark with an x)

[ ] new
[x ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Version Angular?
Your global Angular CLI version (9.0.5) is greater than your local
version (7.3.9). The local Angular CLI version is used.
Angular CLI: 7.3.9
Node: 10.15.3
OS: darwin x64
Angular: 7.2.16
... animations, common, compiler, compiler-cli, core, elements
... forms, http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
Package                           Version
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.13.9
@angular-devkit/build-optimizer   0.13.9
@angular-devkit/build-webpack     0.13.9
@angular-devkit/core              9.0.5
@angular-devkit/schematics        7.3.9
@angular/cdk                      7.3.7
@angular/cli                      7.3.9
@angular/material                 7.3.7
@ngtools/webpack                  7.3.9
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.4
typescript                        3.2.4
webpack                           4.29.0
Description
I have a SSR application, when I build the application it brakes after the webpack build.
🔥 Exception or Error

(...)/dist/prerender.js:360819
            node.importClause.namedBindings.forEachChild(function (name) {
                                            ^

TypeError: Cannot read property 'forEachChild' of undefined

Packages
{
"name": "marketplace",
"version": "0.0.0",
"scripts": {
"ng": "ng",
"start": "node --max_old_space_size=8048 ./node_modules/@angular/cli/bin/ng serve --aot --disableHostCheck",
"build": "ng build",
"build:qa": "ng build --configuration qa --base-href=/pp/web/ --deploy-url=/pp/web/",
"build:pp": "ng build --configuration pp --base-href=/ --deploy-url=/",
"test": "ng test --browsers Chrome_without_security",
"test:ci": "ng test --code-coverage --progress false --watch false --browsers ChromeHeadlessCI",
"test:ci:firefox": "ng test --code-coverage --progress false --watch false --browsers FirefoxHeadless",
"test:ci:phantom": "ng test --code-coverage --progress false --watch false --browsers PhantomJS_custom",
"lint": "ng lint",
"e2e": "ng e2e",
"compodoc": "npx compodoc -p src/tsconfig.app.json",
"compile:server": "webpack --config webpack.server.config.js --progress --colors",
"serve:ssr": "node local.js",
"build:ssr": "npm run build:client-and-server-bundles && npm run compile:server",
"build:client-and-server-bundles": "ng build --prod && ng run my-app-Marketplace:server:production",
"server": "node local.js",
"build:prod": "npm run build:ssr",
"serve:prerender": "node static.js",
"build:prerender": "npm run build:prod && node dist/prerender.js"
},
"private": true,
"dependencies": {
"@angular-devkit/core": "^9.0.5",
"@angular/animations": "^7.2.15",
"@angular/cdk": "^7.3.7",
"@angular/common": "^7.2.15",
"@angular/compiler": "^7.2.15",
"@angular/core": "^7.2.15",
"@angular/elements": "^7.2.15",
"@angular/forms": "^7.2.15",
"@angular/http": "^7.2.15",
"@angular/material": "^7.3.7",
"@angular/platform-browser": "^7.2.15",
"@angular/platform-browser-dynamic": "^7.2.15",
"@angular/platform-server": "~7.2.0",
"@angular/router": "^7.2.15",
"@ng-toolkit/universal": "^7.1.2",
"@nguniversal/common": "0.0.0",
"@nguniversal/express-engine": "0.0.0",
"@nguniversal/module-map-ngfactory-loader": "0.0.0",
"@ngx-meta/core": "^8.0.2",
"@ngx-share/button": "^7.1.4",
"@ngx-share/core": "^7.1.4",
"@types/gapi": "0.0.39",
<EMAIL_ADDRESS>"0.0.50",
"angular2-text-mask": "^9.0.0",
"angulartics2": "^7.4.1",
"ansi-escapes": "^4.2.1",
"bootstrap": "^4.3.1",
"chart.js": "^2.7.3",
"classlist.js": "^1.1.20150312",
"core-js": "^2.5.4",
"domino": "^2.1.3",
"express": "^4.17.1",
"file-saver": "^2.0.2",
"hammerjs": "^2.0.0",
"jasmine-data-provider": "^2.2.0",
"jwt-decode": "^2.2.0",
"keycloak-angular": "^6.1.0",
"localstorage-polyfill": "^1.0.1",
"moment": "^2.24.0",
"ngx-chips": "^2.0.2",
"ngx-clipboard": "^12.2.1",
"ngx-cookie-service": "^2.2.0",
"ngx-device-detector": "^1.3.9",
"ngx-infinite-scroll": "^7.0.0",
"ngx-mask": "^8.1.2",
"ngx-swiper-wrapper": "^7.2.1",
"rxjs": "~6.5.2",
"tslib": "^1.6.1",
"web-animations-js": "^2.3.2",
"zone.js": "~0.8.26"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.13.5",
"@angular/cli": "~7.3.9",
"@angular/compiler-cli": "^7.2.15",
"@angular/language-service": "^7.2.15",
"@types/jasmine": "~2.8.8",
"@types/jasminewd2": "~2.0.3",
"@types/node": "~8.9.4",
"@typescript-eslint/eslint-plugin": "^2.6.1",
"@typescript-eslint/parser": "^2.6.1",
"angular-oauth2-oidc": "^5.0.2",
"codelyzer": "~4.5.0",
"eslint": "^6.6.0",
"husky": "^3.0.8",
"jasmine-core": "^3.5.0",
"jasmine-spec-reporter": "^4.2.1",
"karma": "^4.4.1",
"karma-chrome-launcher": "^3.1.0",
"karma-coverage-istanbul-reporter": "^2.1.0",
"karma-firefox-launcher": "^1.2.0",
"karma-jasmine": "^2.0.1",
"karma-jasmine-html-reporter": "^1.4.2",
"karma-phantomjs-launcher": "^1.0.4",
"karma-spec-reporter": "0.0.32",
"ng2-charts": "~2.2.3",
"ng5-slider": "^1.2.4",
"node-sass": "4.10.0",
"protractor": "~5.4.0",
"puppeteer": "^2.0.0",
"ts-loader": "^5.4.3",
"ts-node": "~7.0.0",
"tslint": "~5.11.0",
"typescript": "~3.2.2",
"webpack-cli": "^3.3.11"
},
"prettier": {
"singleQuote": true
}
}
🌍 Your Environment

prod

Hi, can you try to update to Angular and Angular CLI version 9 and see if the problem persists?
You can read here on how to update http://update.angular.io/#7.0:9.0
If the problem persists after upgrading, please provide a simple repository reproducing the problem.
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

Thanks for reporting this issue. However, you didn't provide sufficient information for us to understand and reproduce the problem. Please check out our submission guidelines to understand why we can't act on issues that are lacking important information.
If the problem persists, please file a new issue and ensure you provide all of the required information when filling out the issue template.


✨ Astro support

Is your feature request related to a problem? Please describe.
No response
Describe the solution you'd like
Add support for Astro. Astro is a web development framework that supports a ton of integrations (some of which are already supported by CodeEdit, like React).
Describe alternatives you've considered
None
Additional context
More stuff here, like the VScode extension.

We will not build-in support for frameworks and libraries, at least not at the moment/the foreseeable future. This is something that could be developed as extension though, which you mention yourself. But please note that we do not and will not develop every extension ourselves. We want to facilitate the tools to the community so they can make those extensions themselves.


Bump web-components-tester dependency to latest major version

Connected to vaadin/expense-manager-demo-pro#2

This change is

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

Comments from Reviewable


Flannel fails after upgrade because of lock: iptables: Resource temporarily unavailable.

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Setup where this occurred:

Start with Rancher 2.1.1
Create Kubernetes 1.10 cluster with Flannel CNI
Use Rancher to edit the cluster and upgrade kubernetes to 1.11.3
Notice Rancher does this nicely, and without any downtime of the hosts. (I rebooted one)
Now (possibly after some time), notice networking between (some) pods stopped working.

Result:
Networking between (some) pods stops working. In my case specifically, I could ping /some/ containers from the one of the host os's, but not others.
When checking the logs of kube-flannel it showed me several lines of:
I0227 14:22:31.917220 1 vxlan_network.go:60] watching for new subnet leases
E0304 05:39:31.131114 1 iptables.go:97] Failed to ensure iptables rules: Error checking rule existence: failed to check rule existence: running [/sbin/iptables -t nat -C POSTROUTING ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j MASQUERADE --wait]: exit status 4: iptables: Resource temporarily unavailable.

Other details that may be helpful:
Here is what I believe caused this, and why I'm making this issue on the rancher repository:

During the upgrade some service touched or modified the IPTABLES on each host, but did not fully release it.
I only restarted one of the hosts
On the hosts that were not restarted Flannel now could not get the lock on IPTABLES, because something was already holding it.

A reboot of each node resolved the issue. (But I lost a day figuring this out).
I believe it has to do with:

https://github.com/coreos/flannel/issues/950 and
https://github.com/kubernetes/kubernetes/issues/57428
and it sound a little like this: https://github.com/rancher/rancher/issues/15576

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Rancher 2.1.1

all nodes are running: Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-1075-aws x86_64)

Installation option (single install/HA):
Single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Rancher created AWS EC2 cluster

Machine type (cloud/VM/metal) and specifications (CPU/memory):
AWS t3 Medium instances

Kubernetes version (use kubectl version):
Kubernetes 1.11.3

Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T17:53:03Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Server:
 Version:      17.03.2-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   f5ec1e2

@dhrp double checking: This cluster was configured to using proper Flannel CNI, ie. not Canal, correct?

This seems to be combination of a race condition in iptables access due to kube-proxy not mounting the flock file from host (PR)and Flannel issue failing to recover from a failed attempt to ensure iptable rules https://github.com/coreos/flannel/issues/988.

We should also update Flannel to >= v0.11 to allow configuration of the iptables update interval from hardcoded 5 seconds which might lead to contention. https://github.com/coreos/flannel/issues/933

➤ Jack Luo commented:
The bug fix is validated in Rancher: master d0d79b0e
Steps:

add a cluster with k8s version 1.11.9 and Flannel as the network provider
run automation to deploy about 200 workloads with cluster IP and test their cross-node and cross-workload accessibility.
check logs of the workload kube-flannel for errors
upgrade k8s to 1.12.7
check logs of the workload kube-flannel for errors
test cluster IP randomly picked
upgrade k8s to 1.13.5
check logs of the workload kube-flannel for errors
test cluster IP randomly picked

➤ Jack Luo commented:
[~jan]  Is the test in my previous comment sufficient to validate the bug fix? Are there any other cases needed to be covered?

@JacieChao Yes, what you tested should cover the scenarios in which the race is most likely to manifest itself.


Reenable Pirlo end to end testing #3766

Fixed the test script to reenable Pirlo.
Sample result for the new flow can be seen at
https://app.pirlo.io/result/4f487c39-f6fe-48a2-8ccb-ab0ca3465171/details#steps

Thanks @vinayjain404!
(The CI failure is in the regular suite, inside async-test.js; that's an unrelated flake we've seen a time or two recently.)


Remove restriction on closeness of nodes returned on FindContent

blocked till https://github.com/ethereum/portal-network-specs/pull/222 is merged
What was wrong?
There is a update to the spec where we no longer list of ENR records of nodes that are closer than the recipient is to the requested content. and instead do list of ENR records of nodes that are closest to the requested content.
How was it fixed?
By removing the filter that compared if a nodes distance was closer then our distance or not

It's not obvious to me that this change requires a test. But, it might be worth including one in portal-hive which tests that all clients respect this change in docs?

https://github.com/ethereum/portal-hive/pull/88
I already have a PR open for it


[Slack] avoid duplicating message when editing a msg not in cache

Currently, if a msgid for an edit is not in the cache, the new message text will be dropped again it conversation. This can be confusing and unexpected.
It would be great if this was possible to toggle. Then admins can choose to set this based on the tempo and nature of the conversation in their chat tool. If it's a frequent source of confusion, they might wish to disable posting of the update as a new msg.
I feel a better alternative is to keep a more persistent and longterm cache (suggested in another issue).
I believe message edits used to he dropped if they were not in cache, but will need to investigate.

Well the messages shouldn't be duplicated, if they're edited they've changed and are not a duplicate.
Or are you actually seeing duplicates ?

True, not duplicates. (Updated issue title.)
While not duplicates per se, can still create misunderstanding. For example, if someone edits, and on the other end, it looks like they're just repeating themselves again, that could represent a communication breakdown through the tool.
Off the top of my head, there are a few options:

send cache miss edits through as new msg, unmodified (current situation)
send cache miss edits through as new msg, but modify to hint at what's happening
allow edits not to be sent when they can't be updated (config option?)

more generally
In the larger scheme, would perhaps make sense to have default "templates" for when messages have something done to them that results in different experiences on one side of gateway vs the other. What comes to mind are these events: 1) msg unthreaded, 2) msg edited, 3) [option options?]. By default, the "template" would be self-referential {{content}}, but someone could choose to set it to their own needs, like thread reply: {{content}} or {{content}} (edited).


Add optional dark mode button/switch

Actually, this theme doesn't have a button or a switch to switch dark mode. Dark mode is fully automated. It follows your browser's preferences and changes automatically.
But I think I may need to add an optional button to switch. I'll add it in the future.

Actually, this theme doesn't have a button or a switch to switch dark mode. Dark mode is fully automated. It follows your browser's preferences and changes automatically.
But I think I may need to add an optional button to switch. I'll add it in the future.
Thanks for your suggestion 😃

If I want to write a dark button, where should I put the js codes?
Suppose, I write a floating button on css and add it to footer.css and add html into footer.ejs
now where to put the js codes? Should it be inside main.js?

Actually, this theme doesn't have a button or a switch to switch dark mode. Dark mode is fully automated. It follows your browser's preferences and changes automatically.
But I think I may need to add an optional button to switch. I'll add it in the future.
Thanks for your suggestion 😃

If I want to write a dark mode switcher button, where should I put the js codes?
Suppose, I write a floating button on css and add it to footer.css and add html into footer.ejs
now where to put the js codes? Should it be inside main.js?

Dark mode is realized in source/css/var.css with prefers-color-scheme. You can't switch dark mode by adding or removing the class name of <body>. Before creating a button to switch the class name, you need to add the class names into var.css.
Also, you can take a look at how GitHub realizes this feature.

1e5f5b1 added this feature.
To enable this, update and edit: https://github.com/MrWillCom/hexo-theme-cupertino/blob/1e5f5b1c589d87057ef129eb035de4e07bb5af26/_config.yml#L13 https://github.com/MrWillCom/hexo-theme-cupertino/blob/1e5f5b1c589d87057ef129eb035de4e07bb5af26/_config.yml#L16
Or visit my blog to test this feature. 😃


⚠ Bofrost.at has degraded performance

In 8ce4c51, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1134 ms

Resolved: Bofrost.at performance has improved in b8c3998.


Rd saucelabs cleanup

There's an issue with saucelabs launching browsers, and we are not cleaning up properly in this case. Adding some exception handling for remote browser startup to attempt to retrieve the last job id and kill it when browser startup fails.
@DramaFever/qa

WIP -- I need to handle concurrency here and making sure we are closing out the correct job id in the case of parallelized runs.


Dartanalyzer does not allow declare class A with "X extends FutureOr<A>" type parameter .

Dart SDK Version: 2.1.0-dev.2.0
OS: Windows 10 (64 bit)
The following code sample declares two classes with Future and FutureOr type parameters:
import "dart:async";

class B<X extends Future<A<X>>> {}
class A<X extends FutureOr<A<X>>> {}

Dart passes with both code lines, i.e. just print OK as a result.
Dartanalyzer  passes with class B<X extends Future<A<X>>> {} and fails with class A<X extends FutureOr<A<X>>> {}, sample output is:
Analyzing test.dart...
  error - 'X' doesn't extend 'FutureOr<A<X>>' at test.dart:4:30 - type_argument_not_matching_bounds
1 error found.

I believe this is incorrect result and analyzer should pass both for Future and FutureOr parameters.

The spec says (in 10.9):
"It is a compile-time error if the type in the extends clause of a class C is a type variable (14), a type alias (19.3.1), an enumerated type (13), a malformed type (19.1), a deferred type (19.1), type dynamic (19.6), or type FutureOr for any T (19.7)."
So the class declaration with FutureOr as supertype is not valid Dart. See also https://github.com/dart-lang/sdk/issues/33744

Oh, but in this case we do not use FutureOr<..> as a superclass, we use it as the bound of a type variable (in this case: an F-bounded one), and I couldn't spot any reason why that would be an error.
It's not even impossible to find a type argument that satisfies this constraint: A<Null> would do, and with class C extends A<C> {}, A<C> would do as well (C can be given as an actual type argument to A in the first place because C <: A<C> <: FutureOr<A<C>>), and similarly for class D extends Future<A<D>>> {} and A<D>.

And anyway, analyzer and dart should behave in the same way here.

Closing: dart as well as dartanalyzer accepts the example program as of a49217bc3aa46e5406ad72017901490c2913c409.


Need Payment and Deposit UI for admin

Does Deposit really need an attributes field?  YES

Duplicate of #223
Duplicate of #222


add playDrum project using JS

hey @irshadmd i would like to add playDrum project using JS under hacktober fest

go ahead 🚀


ENH no libcrypt on cos7

Checklist

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

@conda-forge-admin rerender

@conda-forge-admin rerender

And another bad rerender
@conda-forge-admin rerender

@conda-forge-admin rerender


'version' key missing in the manifest

Current dev build of HA shows this warning:
2021-02-10 09:31:51 WARNING (MainThread) [homeassistant.loader] No 'version' key in the manifest file for custom integration 'samsungtv_smart'. This will not be allowed in a future version of Home Assistant. Please report this to the maintainer of 'samsungtv_smart'
Should be easy to fix ;-)
Thank you,
Simone

Thanks for advise, added in last release.


Custom delete option

Describe your suggested feature
Yokai have single chapter delete option means. It delete 1 chapter at a time. I think adding an option to delete multiple chapters  is a  required features.
Other details

Maybe something like this.
Yokai already have custom download option add option to delete multiple chapters too
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an request for a feature in the original Tachiyomi, I am opening because multiple versions of Yōkai have been released without this feature.
[X] If this is an issue with an extension, or a request for an extension, I should be contacting the extensions repository's maintainer/support for help.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have checked through the app settings for my feature.
[X] I will fill out all of the requested information in this form.

It already have one, try tap and hold the download button, it'll get into selection mode then select your "destination", it'll prompt you with "Remove downloads", click that, then it'll prompt you again with how many downloaded chapters is about to get deleted.
But I'll rename the suggestion to "Better selection mode" since it is very confusing

It already have one, try tap and hold the download button, it'll get into selection mode then select your "destination", it'll prompt you with "Remove downloads", click that, then it'll prompt you again with how many downloaded chapters is about to get deleted.
But I'll rename the suggestion to "Better selection mode" since it is very confusing

Ah so i should hold the download button?
Its really getting complicated 😂


CursesDriver doesn't render wide codepoints correctly

Curses is doing something funky with glyphs that report GetColums() of 1 yet are rendered wide. E.g. 0x2064 (invisible times) is reported as 1 column but is rendered as 2. WindowsDriver & NetDriver correctly render this as 1 column, overlapping the next cell.
I've spent many hours trying to figure this out. I'm at a loss.

I'm pretty sure curses is actively trying to determine a codepoint is wide and ignoring wcwidth (which it does use, and I've verified is that latest).
I suspect the way to address this is to stop using Curses.addstr etc... and instead emit ANSI sequences directly to the output stream.

Relevant. Esp 2070.
https://github.com/mintty/mintty/blob/master/wiki/CtrlSeqs.md

Another good set of characters to be sure to test things with is the wide decimal digits. They count as numbers but are multibyte and supposed to render as 2 columns.


unify trial job id name

Unify trial job id name in TrialJobInfo and ExportedDataFormat.

Please describe the changes with more details  and rebase the PR.

Migrate to #3053


Multiple language (project requirement)

Now is available two languages - EN and FI. I will add LT and UA that Gigi and I will translate later since it doesn't take much time.
BUT in the future, if there is time and opportunity, it would be very interesting to add localization for Arabic languages with the adaptation of the mirror transfer of all elements


KDE.Kate.Release

Addition of support for .appx, because .appx is undoubtedly better than mere .exe, and shall cause submission to the "msstore" and "winget" repositories to be more consistent. Also, I did cause the version of KDE.Kate.Release to be more consistent with KDE's other software.
This should allow the improvements that have been submitted to http://github.com/microsoft/winget-pkgs/issues/30234 to be merged.

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow
Microsoft Reviewers: Open in CodeFlow

https://github.com/microsoft/winget-pkgs/pull/33718#issuecomment-959151815
switching to .appx might be better


[BEAM-9547] Identify remaining WontImplement operations

I went through the remaining operations that have not been implemented yet and identified the ones that fall into one of our WontImplement categories. I think after this only feasible operations remain.
GitHub Actions Tests Status (on master branch)

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

R: @robertwb

retest this please

Thanks!


Git bisect until maplibre-gl-js v1.14.0

First making sure v1.14.0 is bad.
Then I will do a git bisect.
#309

I'm using act to run the workflows locally because the built went through for me on Arch Linux.


SNI based ACL not working HAPROXY

Hello,
The sni based SNI not work as expected. the haproxy not read or ignore the SNI value.
Lets explain :)  :
My client request to the HAProxy a webpage in HTTPS, in this request the SNI field is OK and set with with the servername:

In my condition of Haproxy setting, i have two condition defined :

In this condition i check the name of the server in SNI field :

But the condition is never trigered.
If i negate the condition, it's working fine and the reverse proxy works.
Why this condition not works ? how i can fix it ?
Version :
OPNsense 19.1.9-amd64
FreeBSD 11.2-RELEASE-p10-HBSD
OpenSSL 1.0.2s 28 May 2019
Extention :
Name | HAProxy
Version | 1.8.20
Release_date | 2019/04/25
Dear,

The error in webpage is :

In the log i have that :

Jun 12 13:02:45
haproxy[13722]: <IP_ADDRESS>:16103 [12/Jun/2019:13:02:45.402] Serveur_HTTPS~ Serveur_HTTPS/ -1/-1/-1/-1/0 503 212 - - SC-- 2/2/0/0/0 0/0 "GET / HTTP/1.1"

i have find some problem similar to mine here :
https://discourse.haproxy.org/t/ssl-certificate-verify-on-specific-domain-with-sni/1635

When i edit the file haproxy.conf in /usr/local/etc/haproxy.conf
the configuration autogenerated with opensense and not working :
# ACL: LORA SNI
acl acl_5d00ecdce705f2.67510393 req.ssl_sni -m sub -i lora.versailles.fr
# ACL: SUPERVISION SNI
acl acl_5d00ed9601afc7.32643278 req.ssl_sni -m sub -i belier.versailles.fr
the modification for the haproxy working :
# ACL: LORA SNI
acl acl_5d00ecdce705f2.67510393 ssl_fc_sni lora.versailles.fr
# ACL: SUPERVISION SNI
acl acl_5d00ed9601afc7.32643278 ssl_fc_sni belier.versailles.fr

@ad1rie1 Thanks for your report.
So the essence of all this information is:

req.ssl_sni should be used for TCP content inspection, when the SSL connection is NOT locally deciphered
ssl_fc_sni should be used for SSL connections that are locally deciphered by HAProxy

I've added a new condition "SNI TLS extension matches (locally deciphered)" to support the latter. Furthermore I've improved the wording on the existing options to highlight the difference.
This will be available in the upcoming os-haproxy 2.17.


Catch errors sending store updates to extension

[ ] Documentation update
[x] Bug fix
[ ] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview) Catches postMessage errors.
Which issue (if any) does this pull request address? Fixes #5

don't worry about the test, I will increase the minimum packet size to 500bits.

@all-contributors please add @mrclay for a bugfix

@all-contributors please add @mrclay for a bug fix


Source maps are currently not useful

bundle.js.map ends up super tiny and useless.

This was fixed in 000079b8b06fd051980068af8a989f712f398c26


Deprecate old listeners?

While working on https://github.com/phetsims/projectile-motion/issues/177 I found myself doing a code review on some of the older listeners. For example DownUpListener. I saw only a few usages, and none of them were instrumented for PhET-iO. I'm pretty sure that's because we prefer PressListener, but it would be nice if that could be marked in old scener listeners.
I know @jonathanolson had some work still to do in the new listeners, but aren't they functional enough to at least point people to them first? Here is the list that I thought of as the "old" listeners:

DownUpListener
SimpleDragHandler
ButtonListener
SCENERY_PHET/FireOnHoldInputListener?

Perhaps people already feel this way, in which case we should just add @deprecated doc so it isn't tribal knowledge.

Sounds fine to me to mark them deprecated.

@jonathanolson is this an accurate and complete list?

Sounds fine to me to mark them as deprecated.  But also finish up the work on their replacements.  Specifically:

Close issues related to creation of the replacement listeners. For example https://github.com/phetsims/scenery/issues/131 (create DragListener as a replacement for SimpleDragHandler) is still open.

Code review the new listeners.  A quick look at classes MultiListener and PanZoomListener is all it takes to know that they will fail code review. If they are experimental and not part of the new listeners package, document them as such.

@jonathanolson is this an accurate and complete list?

It is accurate, but I'm not sure what would be needed for a complete list.
I definitely want to finish up a few things for the new listeners.

Today @samreid and I found that there were only two base classes of old listeners, SimpleDragHandler and DownUpListener, and they were both already marked as deprecated.

Code review the new listeners. A quick look at classes MultiListener and PanZoomListener is all it takes to know that they will fail code review.

Created https://github.com/phetsims/scenery/issues/1027 to track these specifically. They ARE being used in the pan/zoom work.

SCENERY_PHET/FireOnHoldInputListener?

@zepumph or @pixelzoom Is there a replacement for FireOnHoldInputListener?

I've marked the listeners I'm aware of that I feel should be deprecated. I have issues to track the main work, but I feel confident now that the "new" listeners should be used over the deprecated alternatives.
I think FireOnHoldInputListener is the main remaining question, otherwise this issue can be closed after that is figured out.

Is there a replacement for FireOnHoldInputListener?

Not that I'm aware of. You might look to see how PushButtonModel is handling the "fire on hold" feature.

The PushButtonModel setup looks like it could be integrated into FireListener. @pixelzoom, any objections to that, or also potentially moving CallbackTimer into axon itself (since it has no sun dependencies)?

Previous comment sounds like a good plan, no objections.

In https://github.com/phetsims/scenery/issues/1078, I identified uses of deprecated input listeners in common code, to be replaced.
So assuming that all deprecated input listeners are actually annotated with @deprecated... @jonathanolson can this issue be closed?

Correct! Closing.

Correct! Closing.


Added Source Reference in Parameter Type

🤔 What's changed?
I added a SourceReference field in ParameterType.
⚡ What's your motivation?
Fixes #145
🏷 What kind of change is this?

:zap: New feature (non-breaking change which adds new behaviour)

♻ Anything particular you want feedback on?
N/A
📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[x] I've changed the behaviour of the code

[ ] I have added/updated tests to cover my changes.

[x] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

[x] Users should know about my change

[x] I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

Cheers. I'll kick of the release pipeline tomorrow.


Why is there NO input_data in the file?

NOTE: Issues that are not bugs or feature requests will be closed. Please ask usage questions on StackOverflow.

TensorFlow installed from (source or binary)?:
TensorFlow version:
Bazel version (if compiling from source):
CUDA/cuDNN version:
GPU Model and Memory:
Exact command to reproduce:
My question is irrelevant to these.

Describe the problem clearly
I am learning the MNIST based on the tutorial on the TensorFlow website
the first line of code is:
from tensorflow.examples.tutorials.mnist import input_data
But when I open the file in GitHub
I do not see the function Input_data in the file. WHY?
Source Code / Logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full-traceback. Large logs and files should be attached. Try to reproducible test-case code the bare-minimum necessary to generate the problem

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!
That said, input_data is a module and does exist in its own file. See: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/tutorials/mnist/input_data.py
Closing this out since this doesn't seem to be a bug or feature request.


Add Support for Landscape.io Code Health Checks and Fix Lint Errors

This fixes a number of lint errors using landscape.io code health settings. We can use landscape.io to periodically check on the health of the code as well as make sure that a given commit does not decrease it.
There are already numerous fixes we could make to improve our health, but I didn't want a severely bloated change so I only made a handful of easy fixes for the moment.
Since we are following the 2 space convention for python, I also generated a .pylintrc file that sets our indent setting to 2 to remove at least those complaints.

@jpevarnek to review as well.

This is sweet!  :+1: