@media doesn't seem to compile with css / scss modules + more

The Problem
I'm using jest-preview to visualize screens using css modules. Some of the styling is dependent on media queries. None of the @media statements seem to get compiled into the embedded style tags. Other classes from the module make it in fine.
I also cannot import SCSS files into the setup file. If I compile them using gulp or webpack and then import the resulting .css file, it appears to work fine.
Additional issue but not related, I can't get auto preview to work at all.
What I've tried
So far I've tried compiling the SCSS myself and removing hashes from the class names. I've faced trouble using the advanced configuration to try and remove the hashes from the jest-preview transform source. This didn't seem to work either.
I've also tried using a custom transform with some additional postCss utilities but haven't had any success. If I render components with no media queries, this tool is absolutely wonderful.
What is the framework/ technology you want to integrate Jest Preview to?
"react": "^16.13.1"
"jest": "^26.6.3"
"postcss": "^8.4.6"
"sass": "^1.53.0"
"sass-loader": "^10.2.1"

Thank you
Thank you for your time and continued effort on this tool! If I can contribute, I'd love to if someone can point me in the right direction.

None of the @media statements seem to get compiled into the embedded style tags

Can you provide minimum reproduction. I added a commit to include @media query and it works fine. Please refer to this commit:
https://github.com/nvh95/jest-preview/commit/0e8a8273146a993b300500e30b2c5fc7e157bbd3#diff-650149a55a5b9fea04fefedba299bd2bf341e1a1c8b4d6e63e483e95669efbfcR4-R9

I also cannot import SCSS files into the setup file.

Please help to prepare a reproduction. In our demo, we can import CSS modules file (https://github.com/nvh95/jest-preview/blob/41019e629c89c48580f29841d6380d89d8cdb41d/demo/setupTests.js#L4). Thanks.

It looks like you are correct! I do think I might have an idea of what's happening. I think the class name property on the component changes based on the media or screen size and it doesnt seem to be updating properly. Regardless of the window or screen size I stub in jest, it falls back to either default or the mobile values. Maybe it's something with the way I'm handling my renders?


[Processing Request]: Historical DSWx-S1 Request in Florida

Venue
PST
Product
DSWx-S1
SAS Version
No response
SDS Version
No response
Input Data
Here is a list of the input granules used along with the MGRS tiles: https://github.com/OPERA-Cal-Val/DSWx-Validation-Experiments/blob/main/marshak/dswx-s1-organization/jwjones_eden_request.csv
Share Results

[ ] Google Earth Engine (GEE)
[ ] NASA Distributed Active Archive Centers (DAAC) User Acceptance Testing (UAT)

Additional Notes
For John Jones

Products should be available. Please let me know if any output sheets/lists are needed.

Will reprocess with final DSWx-S1 release for IV validation.

Output products from 2024-08 processing campaing on PST S3:
request-48-outputs.txt


Connect AVS to a new virtual network - Failed

Didn't recognize my sub:  https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2FEnterprise-Scale-for-AVS%2Fmain%2FBrownField%2FNetworking%2FAVS-to-VNet-NewVNet%2FARM%2FVNetWithExR.deploy.json
{
"code": "SubscriptionNotFound",
"message": "The subscription '/subscriptions/ed0a3e52-X-X' could not be found."
}

All instances of subscription().Id need to be changed to subscription().subscriptionId
see here: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-functions-scope#return-value-2

@sblair01  please let us know if you are still having issues.

@sblair01  please check and let me know

@fskelly is this a flag we can make permanent in the bicep so that I don't have to manually populate it,

Corrected this in the ARM template in pull request https://github.com/Azure/Enterprise-Scale-for-AVS/pull/194.  @prasad3017 and @sblair01. I've tested the ARM deployment and this is working now.  Please let me know if you need me to re-open and fix anything else.


Compile flag fixes for latest clang and Z3 dependency reduction

Removed Z3 dependencies from the heuristic lib
Added the ability to build python bindings without Z3
Fixed compile flags for clang on apple silicon

also see https://github.com/iic-jku/qmap/pull/15 for the original PR

The reason why macOS bindings fail to build in the CI is most certainly because of: https://github.com/iic-jku/qfr/blob/fbd4310d7e7c8b88b314376283dcb15b61e5f3ad/CMakeLists.txt#L24-L30
If not set explicitly in the top level project, CMake will try to build fat binaries. Unfortunately, Z3 offers no universal wheels for download (which is why #14 is on hold until either Z3 publishes universal wheels or GitHub Actions provides M1 runners). Something like
if (DEPLOY)
	set(CMAKE_OSX_ARCHITECTURES "x86_64" CACHE STRING "" FORCE)
endif ()

should resolve the error in the meantime.

I added the option but i'm not sure this will solve the problem. As far as i can see the qfr project already sets the CMAKE_OSX_ARCHITECTURES and forces it back to 'x86_64;arm64' which in turn breaks delocate-listdeps (it does not expect universal binaries) and i'm not sure about its status either :D https://github.com/matthew-brett/delocate/issues/78

Hm. I would have guessed that setting this before including the submodule overrides anything done in the submodule. Does not seem like it 🙃
Let's continue the discussion in #14 and see whether we can find a solution there that also solves the problem here.

Now that #14 is merged, this PR should be good to go after a rebase 👍🏼


UsageTrackingHeaderProvider determines wrong project version

This may be caused by getClass().getPackage().getImplementationVersion() not working correctly when the project jars are repackaged. We should find an alternative way of capturing the version. Perhaps by writing it to a file during the Maven build.

@meltsufin
I'm thinking we could just have a java constant string for the version and then a unit test that checks

if getClass().getPackage().getImplementationVersion() says "SNAPSHOT" then pass.
otherwise, if the java constant string doesn't match getClass().getPackage().getImplementationVersion() then fail. this way we'll not forget to update this string when we do real releases.

It's a good idea to have a test like that. However, I would rather have the version constant updated automatically during the build. Maven resource filtering can probably be used for this.

I'll take this one and use the resource filtering then

@meltsufin Do you want to stick with properties files or potentially write the version into the java files automatically? Note that i don't think resource filtering will work for the java file approach, and it could be more complicated.

@ChengyuanZhao I'm now thinking just hard-coding the version in code. We can later optimize it by auto-generating the source file.

We would lose the (potential) per-module version differences then, right ? And both components in that header would always be the same then ?

Right, but frankly, I'm not too concerned about the per-module version tracking, we can even leave it as this.clazz.getPackage().getImplementationVersion(), or add an assertion that this.clazz.getPackage().getImplementationVersion() == .

FYI our metrics use the per-module version. The one from Spring/1.0.0.whatever is currently unused.

Do you mean adding that assertion in UsageTrackingHeaderProvider ? Wouldn't that crash the user's program if he had rebuilt it and his own strange version was there?  In that case shouldn't we use the hard-coded-version, and just have a unit test on our side for our builds to make sure that the hard-coded version isn't outdated?

@joaoandremartins Thanks for pointing that out! In that case we should definitely have tests verifying the version match in each tracked module.

@meltsufin to confirm, we want what I described at the very top of this thread, but for each module. right?

@ChengyuanZhao Disregard my comment about the assertion. It doesn't really make sense. Unit tests can also be problematic when someone forks and changes the version. I'm leaning towards just using the same root version for every module. That way you don't have to hard-code it in multiple places. It's currently unlikely that we will have different module versions across the project.

I'm ok with that. However, wouldn't a mechanism to prevent us from forgetting to update this hard-coded java string be valuable and worth the potential cost of somebody forking this having to also update that test ? The cost of forgetting to update that string could be high, because if we release without updating it then we may taint much of our metrics results from ppl who grabbed the new release but still using the old version string.


GitHub Actions SHA doesn't always work for pull requests

👓 What did you see?
No after property in /home/runner/work/_temp/_github_workflow/event.json:

Followed by the contents of the file:
{
  "action": "opened",
  "pull_request": {
    "base": {
      "sha": "1c668f7546a31cfa77f486970af0d642634b6db0"
    },
    "head": {
      "sha": "d79b417f8e974b9a2d5e6483845a96446695f944"
    }
  }
}

(I have only included relevant properties in the JSON)
✅ What did you expect to see?
I had expected to see no error, and an event payload like this:
{
  "action": "synchronize",
  "after": "3738117e3337e54955580f4e98cf767d96b42135",
  "before": "06aa815724888e86f37e41e43e07b0ec1bb0ffe1"
}

(I have only included relevant properties in the JSON)
Upon further inspection, it seems both the synchronize event and open events include a .pull_request.head.sha property that can be used in both cases.
This makes the Java implementation a bit more complicated since it relies on regexp matching rather than using a JSON parser. We can probably fix this by skipping pas the head property before we grab the sha.

From what I can tell, the event is opened when a PR is first created. If new commits are pushed to the same PR, the events are synchronize.


Update Mocha link

Coverage remained the same at 100.0% when pulling cfecf8a1b8bc7bc4ef36fea85428fc5952427a8f on mortonfox:patch-1 into 691f2d48dd8b48846ba6f2fff9c2fb2e5a6055d8 on rudijs:master.


Phunk shows as purple but there is no bid on it

I'm attaching a screenshot.  You'll see that a few of my phunks have the purple bg which I thought meant there is an active bid on it. However, when I click on these, I do not see any bids.  Maybe the bid was withdrawn? If so, the transaction history does not say that.

I have the same. And #9702 was bid on by me, prior to purchasing. There is no option to remove the prior bid. So it stays in the purple purgatory.
They can be escrowed & listed still. But the number stays purple as shown on #3506.


Split tests for invalid arguments out into their own files, and ignore them for HHVM

And we also add a cast because of HHVM not allowing current() on an object

LGTM.


Update device-images.md

@TinaNeville, can you review these changes and approve? Feel free to edit. I'm trying to add information related to our recent Windows 10 announcement and comms we are about to send out. thx.

@TinaNeville, can you review these changes and approve? Feel free to edit. I'm trying to add information related to our recent Windows 10 announcement and comms we are about to send out. thx.

@VinnieFlynt Looks good to go.

@TinaNeville, can you review these changes and approve? Feel free to edit. I'm trying to add information related to our recent Windows 10 announcement and comms we are about to send out. thx.

@VinnieFlynt Looks good to go.


Fix typedef parsing issue

There is a bug where the children JSDoc tag nodes of @typedef tag are parsed and added to the tree twice, once as the children nodes of the @typedef tag, and again as the children nodes of the top level JSDocComment node. This PR fixes the issue.

👍


updated ZooKeeper to CamelCase

Minor copy editing change. Apache ZooKeeper uses camel case (https://zookeeper.apache.org/).

@paul-rogers can this be merged? I'm not sure what the process for gh-pages is.

@ilooner, this is a doc. issue which @bbevens usually handles. Is this fix still relevant? If so, maybe Bridget can use her process to apply the fix.


Builds from most up-to-date fork cannot load CBR files

Unless I'm mistaken it looks like Onizuka89 has implemented most of the various code changes from the various forks. It builds under Xcode 7 for me (Yay!). But will load CBR files, just CBZ and raw folders.
The binaries Onizuka89 hosts at http://www.stiandrobak.com/CustomBuilds/Simple_Comic.php have the same issue for me.
No error messages and the only pertinent entry in console I can see is:
10/16/15 1:40:52.150 PM Simple Comic[1873]: Drawn
Is this a known issue?
Is there another fork that builds with Xcode 7 that would be better as a starting point?
I love Simple Comic and donated back when I found it many years ago, but arauchfuss seems to have dropped off the map. I know he was off coding 2.0, but I'd be happy just to fix a few annoyances in 1.x.
Thanks,
Mike

I've identified that all the forks that use the 3.3 XADMaster framework fail to decode RAR/CBR.   arauchfuss' last version was 2.7 as far as I can tell. I compiled the latest v3.10 from the Unarchiver site and used it as a brute force replacement in an executable from Onizuka89's latest build and it now handles RAR. But dropping the compiled frameworks in the Xcode project fails to build QuickComic with error: "Cannot find protocol declaration for 'XADArchiveParserDelegate'".
A quick review of the 3.10 headers show a lot code pulled for XADArchiveParserDelegate including the @protocol statement. Weird that Simple Comic doesn't use this, only QuickComic. The Unarchiver app doesn't use it either based on a quick review of that source code.
The iComics fork that MaddtheSane is beginning to use has no version identifier that I can determine. But it appears to be an older version as much of the XADArchiveParserDelegate code is still there.

Curiouser is that the headers from the compiled XADMaster framework with the Info.plist identifier as 3.3 don't match the 3.3 source code headers from The Unarchiver site. Modified for Simple Comic?

I thought I had replied to this, sorry. XADMaster is the cause as you suspect. In the newest version on my branch now there should be a description in the README.md to maintain the RAR functionality if it is lost. It tells you how to checkout a version of XADMaster where it RAR works, and to remove references to two files that didn't exist in that commit of XADMaster.

Thanks

Could someone pull from master and verify this is does not happen.  Seems to work fine for me, but that does not mean much.

Wow, great to see you back. :)
I just pulled and built and it solves the problem for me. Just a quick test to post this note so I haven't tested extensively yet.

I must say I'm sad to see you used the same status bar implementation as the forks. I greatly prefer the media player styled popup controls from the original design. This implementation either requires disabling the status bar (and it's useful information) or having it shown in fullscreen mode ruining the comic book reading effect.

That progress bar is from my really old transition to a modern fullscreen view, not the branches. Once I have refactored some things that will come back.

@arauchfuss
Thanks. After I posted, I tried to remember where I had first seen the change, but wasn't able to find the commit where you had implemented it.  I definitely remembered seeing it when I tried building one of the forks to fix the CBR issue, thus the mistaken attribution.
Any chance of focusing the new pinch-to-zoom to "center" on the cursor position?

Is this fixed in the current code? I've read the comments but don't really follow them. I'm using 1.7 downloaded from the website and CBRs don't work with it, which is probably 90% of my collection. If it's fixed in the current code I can probably figure out how to build it. :-)


Create mremoteng.json

Adds mRemoteNG remote desktop tool from https://mremoteng.org/

Hm, adding persistence to those files isn't that easy. We can't provide a default confCons.xml because the Protected attribute has to be generated by mRemoteNG and we can't create a link until it has created the file.

@r15ch13 Does it choke if you just generate a blank file? What if you generate the symlink against a blank file and delete the file in post_install?

Windows doesn't support symbolic links for files, which is why we use hard links (mklink /h).
The linked file will not change and still point to the "same" file if the source is deleted. So you end up with two different files. Already tried that... 😢
A blank file crashes mRemoteNG. I also tried adding only the XML Doctype and Doctype + Root node.
mRemoteNG doesn't like that either...

@r15ch13 It seems I'm able to create symlinks in Powershell using New-Item -Type SymbolicLink -Target test.txt sym.txt using PowerShell. If I open sym.txt I see the content of test.txt. I can also delete test.txt without sym.txt disappearing (although attempting to open it no longer does anything). If I then create a different test.txt, and try opening sym.txt again, I once again see the content of the new test.txt.

@masaeedu As far as I know, administrator privileges are required to create symbolic links, except in recent versions of Windows 10 with Developer Mode enabled.
That's why we don't want to use symbolic links. If we did use them, most users would see admin elevation prompts and that ruins the experience and breaks unattended installs.

@lukesampson Gotcha. After some digging, I've found you can configure the location in which confCons.xml will be stored/read using the following setting in mRemoteNG.exe.config:
            <setting name="LoadConsFromCustomLocation" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="CustomConsPath" serializeAs="String">
                <value>C:\Users\asaeeduddin\AppData\Roaming\mRemoteNG\confCons - Copy.xml</value>
            </setting>

So after the folder is extracted and before the program is run for the first time, that can be updated so that the confCons.xml file is stored directly in the persist folder.

@r15ch13

This directory has a random string and will be created for each program version

I think that file is copied from mRemoteNG.exe.config, which is part of the archive. If you modify mRemoteNG.exe.config, I think the copied file (whatever random subfolder in localappdata it ends up), will have the modified settings.

What's the status of that pull request ?
I took back the file in my repo and evertyhing seems ok except a few warnings about persisted files that are not created yet...


feat: Batch eval wasm

Fixes: #234
TODO

[ ] Get browser tests working

Codecov Report
Attention: Patch coverage is 0% with 14 lines in your changes are missing coverage. Please review.

Project coverage is 82.29%. Comparing base (4197d57) to head (b390984).

Files
Patch %
Lines

flipt-engine-wasm/src/lib.rs
0.00%
12 Missing :warning:

flipt-engine-ffi/src/evaluator/mod.rs
0.00%
1 Missing :warning:

flipt-evaluation/src/lib.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #237      +/-   ##
==========================================
- Coverage   82.61%   82.29%   -0.32%
==========================================
  Files          11       11
  Lines        3140     3152      +12
==========================================
  Hits         2594     2594
- Misses        546      558      +12

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


panic: runtime error: invalid memory address or nil pointer dereference

Describe the bug
I'm running EVCC 0.118.10 in a docker container on Synology.
After some time (less than a day), EVCC is crashing with errors in log:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x11a2535]

Happens also with 0.118.9
Maybe unrelated, but crash happens just after the Porsche token refresh error....
Steps to reproduce

no idea...

...
Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

sponsortoken: xxxxxxxxx

log: info
levels:
  cache: info

# unique installation id
plant: xxxxxxxxx

interval: 10s # control cycle interval

meters:
- type: template
  template: sma-home-manager
  usage: grid
  host: <IP_ADDRESS>
  name: grid1
- type: template
  template: sma-hybrid
  id: 3
  host: <IP_ADDRESS>
  port: 502
  usage: pv
  modbus: tcpip
  name: pv2
- type: template
  template: sma-hybrid
  id: 3
  host: <IP_ADDRESS>
  port: 502
  usage: battery
  modbus: tcpip
  name: battery3
  capacity: 20.0 # in kWh

vehicles:
- type: template
  template: porsche
  title: Taycan
  user: xxxxxxxxx
  password: xxxxxxxxx
  vin: xxxxxxxxx
  capacity: 93
  name: porschetaycanV2

site:
  title: Thuis
  meters:
    grid: grid1
    pv:
    - pv2
    battery:
    - battery3
  residualPower: 100
  bufferSoc: 80
  prioritySoc: 75

chargers:
  - name: sma_charger
    type: template
    template: smaevcharger
    host: <IP_ADDRESS> # IP-Adresse oder Hostname
    user: xxxxxxxxx # Benutzerkonto (bspw. E-Mail Adresse, User Id, etc.)
    password: xxxxxxxxx # Passwort des Benutzerkontos (bei führenden Nullen bitte in einfache Hochkommata setzen)

hems:
  type: sma
  AllowControl: false

loadpoints:
- title: Garage_7kWh # display name for UI
  charger: sma_charger # Wallbox Referenz
  vehicle: porschetaycanV2 # Referenz auf Standardfahrzeug
  mode: off # charge mode (off, now, minpv, pv)
  phases: 3
  minCurrent: 6 # minimum charge current (default 6A)
  maxCurrent: 9 # maximum charge current (default 16A, max 32)

tariffs:
  currency: EUR # three letter ISO-4217 currency code (default EUR)
  grid:
    # either static grid price
    type: fixed
    price: 0.44 # EUR/kWh
  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.15 # EUR/kWh

Log details
[main  ] INFO 2023/07/22 15:56:59 evcc 0.118.10
[main  ] INFO 2023/07/22 15:56:59 using config file: /etc/evcc.yaml
[main  ] INFO 2023/07/22 15:56:59 starting ui and api at :7070
[db    ] INFO 2023/07/22 15:57:01 using sqlite database: /root/.evcc/evcc.db
[semp  ] WARN 2023/07/22 15:57:06 SEMP_BASE_URL unspecified, using http://<IP_ADDRESS>:7070 instead
[site  ] INFO 2023/07/22 15:57:06 site config:
[site  ] INFO 2023/07/22 15:57:06   meters:      grid ✓ pv ✓ battery ✓
[site  ] INFO 2023/07/22 15:57:06     grid:      power ✓ energy ✓ currents ✓
[site  ] INFO 2023/07/22 15:57:06     pv 1:      power ✓ energy ✗ currents ✗
[site  ] INFO 2023/07/22 15:57:06     battery 1: power ✓ energy ✗ currents ✗ soc ✓ capacity ✓
[site  ] INFO 2023/07/22 15:57:06   vehicles:
[site  ] INFO 2023/07/22 15:57:06     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✓
[lp-1  ] INFO 2023/07/22 15:57:06 loadpoint 1:
[lp-1  ] INFO 2023/07/22 15:57:06   mode:        off
[lp-1  ] INFO 2023/07/22 15:57:06   charger:     power ✓ energy ✗ currents ✓ phases ✗ wakeup ✗
[lp-1  ] INFO 2023/07/22 15:57:06   meters:      charge ✓
[lp-1  ] INFO 2023/07/22 15:57:06     charge:    power ✓ energy ✗ currents ✓
[lp-1  ] INFO 2023/07/22 15:57:06 vehicle updated: unknown -> Taycan
[site  ] WARN 2023/07/22 15:57:07 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
[lp-1  ] INFO 2023/07/22 15:57:07 car disconnected
[porsche] ERROR 2023/07/23 04:32:04 token refresh: oauth2: "invalid_grant" "Unknown or invalid refresh token."
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x11a2535]

goroutine 100 [running]:
github.com/evcc-io/evcc/util/oauth.Refresh(0xc0012471d0, 0xc00115b500, {0x2fae640, 0xc00047e570}, {0xc000c97fc8, 0x1, 0x1})
        /build/util/oauth/helper.go:32 +0x175
created by github.com/evcc-io/evcc/vehicle/porsche.(*Identity).Login
        /build/vehicle/porsche/identity.go:163 +0x13c5

What type of operating system are you running?
Docker container
Version
0.118.10

Closed in 192180722d8d62d89fa9f7c1a14c6994c1b85cb1


feat: add system startup task to expand os volume

What type of PR is this?
/kind feature

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 79.321%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2290

Relevant Lines:
2887

💛  - Coveralls


Can simultaneous request override traceId ?

If two users will send 2 requests simultaneously:

first one will set traceId: some-uuid-1,
second one will set traceId: some-uuid-2,

then:

first one will log some-uuid-2 (but it should log some-uuid-1, becuase this is first request)
second one will log proper traceId some-uuid-2

Am I right or Am I wrong?

No, in if this corner case is possible - that's bug in Node.js core, see https://nodejs.org/api/async_context.html#class-asynclocalstorage
https://github.com/nodejs/node/issues/22360

This library is simple wrapper for AsyncLocalStorage

Got it, thank you😊!


Trusting multiple root CA

I am using opendistro with SSL authentication in my kubernetes cluster. In that way, i am using Kubernetes CA as my CA, and it worked fine if my logstash is from the same cluster.
Right now, I have a situation where I need to deploy the logstash from a different cluster. This resulting in SSL error since it could not trust the certs that my logstash are using. When I read the documentation, it says that opendistro can trust multiple CA through this key
opendistro_security.ssl.transport.pemtrustedcas_filepath
However, no luck so far when I try to add my other kubernetes root CA certs to this key. Is there a practical example of how the opendistro plugin can trust more than one root CA?

Thanks for your question @reynaldiwijaya and apologies from the Open Distro team. Could you give this another try with the most recent release <IP_ADDRESS> The documentation has also been updated. For the flag you mentioned above, could you check if the root CA is present in the config directory as well?
opendistro_security.ssl.transport.pemtrustedcas_filepath ->
Path to the root CAs (PEM format), which must be under the config directory, specified using a relative path. Required.

Do you have an example of how this looks within the yml?

Please take a look at https://opendistro.github.io/for-elasticsearch-docs/docs/security/configuration/tls/

Hi @vrozov
I have been through this documentation and it doesnt give an example or mention how to supply more than 1 CA cert.
opendistro_security.ssl.transport.pemtrustedcas_filepath
asks for:
Path to the root CAs (PEM format), which must be under the config directory, specified using a relative path. Required.

This doesnt state whether it should be a single PEM file with multiple CA's in it our if it should be a folder with multiple separate PEM files or can a list be provided to this property, i.e.:
opendistro_security.ssl.transport.pemtrustedcas_filepath:
  - ca-cert1.pem
  - ca-cert2.pem

Hi @thenom, It should be a single pem file with multiple CA's

Thanks for that @debjanibnrj.  This is good information to know, especially when the CA needs replacing because the nodes need to go through a transition period where they trust the old and new.
This info should probably be in the documentation.

Hi @debjanibnrj @thenom how did you manage to do this? I have dumped the content of the local CA on the remote CA, resulting a file like the following:
-----BEGIN CERTIFICATE-----
<remote CA.pem content>
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
<local CA.pem content>
-----END CERTIFICATE-----

Elasticsearch restarts successfully on the remote node, but when I try to read information from the local cluster, I get the following response:
[root@centos7-50 vagrant]# curl -XGET -k -u admin:admin https://<LOCAL_NODE_IP>:9200/<remote_cluster_name>:<index_name>/_search?pretty
{
  "error" : {
    "root_cause" : [
      {
        "type" : "transport_exception",
        "reason" : "handshake failed because connection reset"
      }
    ],
    "type" : "connect_transport_exception",
    "reason" : "[][<REMOTE_NODE_IP>:9300] general node connection failure",
    "caused_by" : {
      "type" : "transport_exception",
      "reason" : "handshake failed because connection reset"
    }
  },
  "status" : 500
}

I really don't know how to proceed. I did it successfully with Xpack but with Open Distro I'm having a hard time. Any help would be appreciated!
Thanks,
Sergio.

Hi @sergiospa,
To be honest i pretty much did the same thing, i concatenated the 2 certs into one.  Are you getting protocol\cipher issues as i am not sure i got handshake failed messages.  Does OD support the  protocol (i.e. TLS1.2) and your ciphers on the server?

Hi @reynaldiwijaya - it looks like you've found a workaround. That's great! If you're still using ODFE, you may want to give this another try using the latest OpenSearch which has superseded ODFE.


Pyright reports false positive error with asynccontextmanager

Pyright gets confused and will give you error messages like this:
error: Object of type "AsyncIterator[AsyncGenerator[...]]" cannot be used with "with" because it does not implement __aenter__ (reportGeneralTypeIssues)
error: Object of type "AsyncIterator[AsyncGenerator[...]]" cannot be used with "with" because it does not implement __aexit__ (reportGeneralTypeIssues)

For code like this:
async with Client("test.mosquitto.org") as client:
    async with client.filtered_messages("floors/+/humidity") as messages:
        await client.subscribe("floors/#")
        async for message in messages:
            print(message.payload.decode())

This change statically checks against sys.version_info for the right version, which Pyright understands.
For additional discussion, see https://github.com/encode/httpx/discussions/1829.

Whoops...I had checked for issues on this, but failed to check PRs.  It looks like https://github.com/sbtinstruments/asyncio-mqtt/pull/86 by @laundmo is an alternative fix for this as well.

Thanks for opening this pull request. There is a lot of overlap with #86, yes, so let's take the discussion in there. :+1: Seems to me that @laundmo is open to your approach. Let's discuss in #86. :)

After some discussion in #86, I chose to merge #86 first. That puts this PR (#87) in conflict.
I'd like to merge it in, though. I think it's trivial to make it compatible with the current master. Can you please update this PR accordingly? Thanks! :)

Looks good to me. :) Thank you for your contribution to asyncio-mqtt. 👍

@frederikaalund, any thoughts on when you might be cutting a new release?

@sdwilsh, I'll make a new release first thing on Monday. :) I just need to update the changelog accordingly. Should take 10 mins.

@sdwilsh, I'll make a new release first thing on Monday. :) I just need to update the changelog accordingly. Should take 10 mins.

I just released v0.11.1. Better late than never. :)


[BUG] Nested classes cannot access static members of outer classes, when used in Annotations

Describe the bug
When a static nested class (B) exposes a static final String attribute, which uses a field name generated using @FieldNameConstants on the outer class (A), and the outer class is annotated with an annotation (MyAnnotation), that references the inner field, the compilation on javac fails with:
.\A.java:19: error: cannot find symbol
                static final String string = Fields.myField;
                                             ^
  symbol:   variable Fields
  location: class B
.\A.java:14: error: element value must be a constant expression
@MyAnnotation(A.B.string)

To Reproduce
Simply invoce javac -cp lombok-1.18.8.jar A.java on the following file: A.java
Expected behavior
The code should compile fine. Value of A.B.string should be "myField"
Version info (please complete the following information):

Lombok version: 1.18.8
Platform (javac): javac 1.8.0_131

Additional context
Eclipse IDE shows no errors

Can you please submit the source code that triggered this error?

See the linked file. It is public now


How to build mapviz in ros2 foxy

I am trying to build mapviz on ros2 foxy using colcon build. I am on the dashing-devel branch.
I understand that ros2 does not use catkin, but other people seem to be using this package on ros2. How do I do this?
Thanks
colcon build --packages-select mapviz
Starting >>> mapviz
--- stderr: mapviz
CMake Error at CMakeLists.txt:27 (find_package):
By not providing "Findcatkin.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "catkin", but
CMake did not find one.
Could not find a package configuration file provided by "catkin" with any
of the following names:
catkinConfig.cmake
catkin-config.cmake

Add the installation prefix of "catkin" to CMAKE_PREFIX_PATH or set
"catkin_DIR" to a directory containing one of the above files.  If "catkin"
provides a separate development package or SDK, be sure it has been
installed.

Failed   <<< mapviz [0.04s, exited with code 1]
Summary: 0 packages finished [0.18s]
1 package failed: mapviz
1 package had stderr output: mapviz

It really looks like you're on the master branch, which is for ROS 1. For Foxy and later, the ros2-devel branch is where current development is being done.


Removes download count

Download count is not supported anymore. It was broken for a long period of time, but now it was completely removed.
That's how it looks right now:

So, I have removed this badge.

Thanks, that number was total garbage anyways


MCEdit doesn't load correctly

So, I'm using the latest version of MCEdit(<IP_ADDRESS>), and when I load the application, the cmd popup and "MCEdit is Loading" logo thing comes up, but then, the logo disappears and a whole ton of text(errors, I assume) come up on the cmd popup. This is what happens every time I load the application.

My computer's specs: Windows 7, Intel core i7, 64 bit, 8 gigs of ram(7.8 gb usable), about 23 gigs of space free on my hard drive.
I have redownloaded multiple versions of MCEdit and relaunched it, but every time, I get the same result. I have searched the internet for a solution, but I can't seem to find an answer that matches my error. In case you need, here is a screenshot of my mcedit folder.

I have no experience as a coder, and I only created this github acount to post this issue, so please don't facepalm if this is a really simple problem that any coder can fix.
If you respond with a solution to my problem, I will try it immediately and respond ASAP if it worked or not. Thank you in advance.

What is your system's video card? That looks like a driver problem and would likely be fixed by a graphics driver update depending what card you have..

Ok, this is what I found about my graphics card.

Ok, I checked my graphic card updater thingy and I found that my graphics card is up to date. So this might not be the graphic's card problem. I have used MCEdit on this computer before, and it worked perfectly. But now, for some reason, it doesn't work. Yesterday, when I clicked on the MCEdit application, it didn't work, so I posted this issue. But about 2 weeks ago, MCEdit was working fine.

No update on you computer since two weeks?
Did you used the same MCEdit version until two weeks ago?
By the way, having a graphics card (especially Intel ones) may be the problem. But I 'll let people with more knowledge about this answer :wink:

I found that I used MCEdit 3 weeks ago rather than 2. I used version <IP_ADDRESS> just as it came out. Also, I checked my computer update history, and yes, there were exactly 24 windows updates from now and then(some failed, and others successful).

There was a huge windows update about a week ago that resolved some long standing problems, it may have done something with your drivers. Could you give us some more information on your video card such as cpu model or the specific intel card, there is a known issue with second gen intel graphics chips which has a potential workaround.

Also the built in driver update checker often doesn't actually check the manufacturer's site, only Microsoft's driver repository.

I think I have all the driver information in this screenshot

Well, the actual model is missing, if you could get the CPU model from the system information pane I can look it up.

Ok, I found my system model, which is 0831CTO.

Okay, I just decided to run MCEdit for no apparent reason, and it worked! I swear it didn't work for me when I posted this issue, so I have no idea why it just started to work all of a sudden. I guess if MCEdit doesn't work, you just wait for a bit or something. I don't know. :/

That's a first gen i7, haven't heard problems from them in the past, ah well at least it works now.


:seedling: Update readme for onboarding

This change updates the readme.md in preparation for on-boarding new developers to the project. The current readme was a little hard to follow and jumped around a bit. The intention here is to give all of the commands required to get our preferred (minikube) environment up and running in a sequential order. Additional info is added via links within the markdown & a troubleshooting section is added at the end of the doc to add any supplemental information.

#565


drop package dependencies

I suggest we drop some package dependencies.
replace FactCheck with Base.Test. There is no really good reasons to use FactCheck over Base.Test. It seems to be common problem that testing will stop to syntax errors or similar, and FactCheck doesn't help for this. It's true that Base.Test will stop to first failed test, but it can be very easily dealed with custom handler, see http://docs.julialang.org/en/release-0.4/stdlib/test/
So we can "simulate" FactCheck very easily
function get_test_handler()
    passed = 0
    failed = 0
    errors = 0
    function test_handler(r::Test.Success)
        passed += 1
    end
    function test_handler(r::Test.Failure)
        failed += 1
        println("Failed test: $(r.expr)") # <-- this is no more causing LoadError and stop test routine.
    end
    function test_handler(r::Test.Error)
        errors += 1
        println("Error when testing: $(r.expr)")
    end
    return test_handler
end

handler = get_test_handler()

And we anyway need some try/except because syntax errors or similar are causing test routine to stop anyway. See #27 for example how this happens.
Another package we could consider stop using is Logging. The main reason we started to use this is that we really don't want any println lines to our code because we want to control the amount of output easily. Julia already has different levels:
julia> info("moimoi")
INFO: moimoi

julia> warn("heihei")
WARNING: heihei

julia> error("eiei")
ERROR: eiei
 in error at ./error.jl:21

It's trivial to create some custom level, say for example
julia> function debug(s)
           println("DEBUG: $s")
           return nothing
       end

to get more levels. If we want to disable for example level info we can do
julia> Base.info(msg) = nothing
info (generic function with 3 methods)

julia> info("moimoi")

julia>

And how many logging levels we really need and especially can handle? I've seen programs with so many as 20(!) levels of logging. I would like to see some systematic way to decide does this message X belong to level 11 or level 12 etc ;). I think four levels might be sufficient. We still need some sort of debug level which can be automatically disabled to get rid of all unnecessary debug information. But I doubt do we really need one more package dependency to make this work.
Docile, Lexicon and Lint are used to verify code quality and generate documentation, they are not essential for using JuliaFEM, they can also be dropped from REQUIRE list so that they don't have to be installed in order to use JuliaFEM. If user wants to do something which requires some of these then he/she can install them.
LightXML and HDF5 are needed by XDMF writer. We could consider creating a separate package to write XDMF. Moreover, installing HDF5 seems to be hard for some systems.
The only requirement what do we really need is just ForwardDiff. Any thoughs?

I did quite nice POC of using Base.Test with custom handler, see
https://github.com/JuliaFEM/JuliaFEM.jl/blob/master/src/test.jl
Now test set is always run completely no matter what. At the end short summary is displayed what tests has failed and why. See also https://github.com/JuliaFEM/JuliaFEM.jl/blob/master/test/test_fields.jl which is written to follow this idea. It's very Pythonic approach.

Maybe relevant: https://github.com/JuliaLang/julia/pull/13062 and to use in v0.4: https://github.com/IainNZ/BaseTestNext.jl

Damn. Did I just redesign the wheel.

Ok to drop FactCheck
Existing four levels is enough, thus we can drop Logging
I agree about Docile, Lexicon and Lint, let's remove them.
Let's make a new XDMF writer or even better, let's try to add this functionality in JuliaIO and FileIO

I think we should use this BaseTestNext becase it's going to be standard in next release. Clearly testing of packages is now going to the right way, now there's a testset which can be used to delay throwing error so that all tests are ran even though some tests fail. That was the point number 1 in our earlier discussions related to testing.
Another thing I feel important is the possibility to run single tests for rapid testing. Basically this is implemented to our test.jl using ugly makefile: make test_function FILE=test/test_foo.jl FUNCTION=test_this_important_thing. Seems that BaseTestNext is not implementing this kind of features yet. It would be supercool to have something similar to py.test, e.g. julia-test test/my_tests.jl --testset test_something_important to run only some spesific testset.

This is use.


Error during uploading metadata: The attribute 'releaseType' can not be modified.

New Issue Checklist

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

Issue Description
I got an error during metadata upload:
[!] An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified.
In the past, I used deliver for uploading metadata without any issues.
Command executed
fastlane run deliver skip_metadata:false skip_screenshots:true
Complete output when running fastlane, including the stack trace and command used
ci$ fastlane run deliver skip_metadata:false skip_screenshots:true
[✔] 🚀
[17:36:53]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[17:36:55]: ---------------------
[17:36:55]: --- Step: deliver ---
[17:36:55]: ---------------------
[17:36:55]: Successfully loaded '/Users/ci/sources/xxxxxx/xxxxxx/fastlane/Deliverfile' 📄

+----------------------------+-------------------------------+
|       Detected Values from './fastlane/Deliverfile'        |
+----------------------------+-------------------------------+
| username                   |<EMAIL_ADDRESS>      |
| app_identifier             | com.xxxxxx.xxxxxx |
| team_name                  | xxxxxx X.X.            |
| skip_binary_upload         | true                          |
| skip_metadata              | true                          |
| skip_app_version_update    | true                          |
| run_precheck_before_submit | false                         |
| overwrite_screenshots      | true                          |
+----------------------------+-------------------------------+

[17:36:55]: Login to App Store Connect<EMAIL_ADDRESS>[17:36:57]: Login successful

+--------------------------------------+-------------------------------+
|                       deliver 2.152.0 Summary                        |
+--------------------------------------+-------------------------------+
| skip_metadata                        | false                         |
| skip_screenshots                     | true                          |
| screenshots_path                     | ./fastlane/screenshots        |
| metadata_path                        | ./fastlane/metadata           |
| username                             |<EMAIL_ADDRESS>      |
| app_identifier                       | com.xxxxxx.xxxxxx |
| platform                             | ios                           |
| edit_live                            | false                         |
| use_live_version                     | false                         |
| skip_binary_upload                   | true                          |
| skip_app_version_update              | true                          |
| force                                | false                         |
| overwrite_screenshots                | true                          |
| submit_for_review                    | false                         |
| reject_if_possible                   | false                         |
| automatic_release                    | false                         |
| phased_release                       | false                         |
| reset_ratings                        | false                         |
| team_name                            | xxxxxx X.X.            |
| run_precheck_before_submit           | false                         |
| precheck_default_rule_level          | warn                          |
| ignore_language_directory_validation | false                         |
| precheck_include_in_app_purchases    | true                          |
+--------------------------------------+-------------------------------+

[17:36:59]: Loading './fastlane/metadata/en-AU/description.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/name.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-AU/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/description.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/name.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-CA/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/description.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/name.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-GB/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/description.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/name.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/en-US/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/description.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/name.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/es-ES/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/description.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/name.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/es-MX/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/description.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/name.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-CA/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/description.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/name.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/fr-FR/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/description.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/keywords.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/release_notes.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/support_url.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/marketing_url.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/promotional_text.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/name.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/subtitle.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/privacy_url.txt'...
[17:36:59]: Loading './fastlane/metadata/nl-NL/apple_tv_privacy_policy.txt'...
[17:36:59]: Loading './fastlane/metadata/copyright.txt'...
[17:36:59]: Loading './fastlane/metadata/primary_category.txt'...
[17:36:59]: Loading './fastlane/metadata/secondary_category.txt'...
[17:36:59]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[17:36:59]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[17:36:59]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[17:36:59]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/first_name.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/last_name.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/phone_number.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/email_address.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/demo_user.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/demo_password.txt'...
[17:36:59]: Loading './fastlane/metadata/review_information/notes.txt'...
[17:37:00]: Verifying the upload via the HTML file can be disabled by either adding
[17:37:00]: `force true` to your Deliverfile or using `fastlane deliver --force`
[17:37:00]: Does the Preview on path './fastlane/Preview.html' look okay for you? (y/n)
y
[17:37:06]: HTML file confirmed...
[17:37:33]: Will begin uploading metadata for 'X.X' on App Store Connect
[17:37:33]: Uploading metadata to App Store Connect for version

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

➡  Deliver: The attribute 'releaseType' can not be modified
    https://github.com/fastlane/fastlane/issues/16679 [closed] 11 💬
    an hour ago

➡  Server error 504 when uploading metadata
    https://github.com/fastlane/fastlane/issues/16665 [closed] 63 💬
    3 weeks ago

🔗  You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
	26: from /usr/local/bin/fastlane:23:in `<main>'
	25: from /usr/local/bin/fastlane:23:in `load'
	24: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/bin/fastlane:23:in `<top (required)>'
	23: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	22: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	20: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	18: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	17: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	16: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:224:in `block (2 levels) in run'
	14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/one_off.rb:22:in `execute'
	13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/one_off.rb:42:in `run'
	12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:253:in `block in execute_action'
	 9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:261:in `block (2 levels) in execute_action'
	 7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:17:in `run'
	 6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/deliver/lib/deliver/runner.rb:42:in `run'
	 5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/deliver/lib/deliver/runner.rb:124:in `upload_metadata'
	 4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/deliver/lib/deliver/upload_metadata.rb:181:in `upload'
	 3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:88:in `update'
	 2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:733:in `patch_app_store_version'
	 1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/client.rb:110:in `patch'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/client.rb:163:in `handle_response': An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified. (Spaceship::UnexpectedResponse)
	26: from /usr/local/bin/fastlane:23:in `<main>'
	25: from /usr/local/bin/fastlane:23:in `load'
	24: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/bin/fastlane:23:in `<top (required)>'
	23: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	22: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	20: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	18: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	17: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	16: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:224:in `block (2 levels) in run'
	14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/one_off.rb:22:in `execute'
	13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/one_off.rb:42:in `run'
	12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:227:in `execute_action'
	11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:227:in `chdir'
	10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:253:in `block in execute_action'
	 9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:261:in `block (2 levels) in execute_action'
	 7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:17:in `run'
	 6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/deliver/lib/deliver/runner.rb:42:in `run'
	 5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/deliver/lib/deliver/runner.rb:124:in `upload_metadata'
	 4: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/deliver/lib/deliver/upload_metadata.rb:181:in `upload'
	 3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:88:in `update'
	 2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:733:in `patch_app_store_version'
	 1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/client.rb:110:in `patch'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/client.rb:163:in `handle_response': [!] An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified. (Spaceship::UnexpectedResponse)

 [REPLACE THIS WITH YOUR INFORMATION]

Environment
### Stack

| Key                         | Value                                                          |
| --------------------------- | -------------------------------------------------------------- |
| OS                          | 10.15.6                                                        |
| Ruby                        | 2.6.3                                                          |
| Bundler?                    | false                                                          |
| Git                         | git version 2.24.3 (Apple Git-128)                             |
| Installation Source         | /usr/local/bin/fastlane                                        |
| Host                        | Mac OS X 10.15.6 (19G73)                                       |
| Ruby Lib Dir                | /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib |
| OpenSSL Version             | LibreSSL 2.8.3                                                 |
| Is contained                | false                                                          |
| Is homebrew                 | false                                                          |
| Is installed via Fabric.app | false                                                          |
| Xcode Path                  | /Applications/Xcode.app/Contents/Developer/                    |
| Xcode Version               | 11.6                                                           |

### System Locale

| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_US.UTF-8 | ✅ |
| LC_ALL   | en_US.UTF-8 | ✅ |
| LANGUAGE |             |   |

### fastlane gems

| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.152.0 | ✅ Up-To-Date  |

### Loaded fastlane plugins:

**No plugins Loaded**

 [REPLACE THIS WITH YOUR INFORMATION]

@oleksiisedun Hey!  This will help me figure out if its an app issue or a weird state caused by other operations.

+1

No problem, I got this error:
ci$ fastlane test_update
[✔] 🚀
[20:37:05]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[20:37:06]: ------------------------------
[20:37:06]: --- Step: default_platform ---
[20:37:06]: ------------------------------
[20:37:06]: Driving the lane 'ios test_update' 🚀
[20:37:06]: Installing Ruby gem 'spaceship'...
+------------------+-----------------+
|            Lane Context            |
+------------------+-----------------+
| DEFAULT_PLATFORM | ios             |
| PLATFORM_NAME    | ios             |
| LANE_NAME        | ios test_update |
+------------------+-----------------+
[20:37:13]: You don't have write permissions for the /Library/Ruby/Gems/2.6.0 directory.

+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
+------+------------------+-------------+

[20:37:13]: fastlane finished with errors

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

➡  [screengrab] Permission denied on API level >= 24
    https://github.com/fastlane/fastlane/issues/15788 [open] 25 💬
    22 hours ago

➡  fastlane action fir_cli
    https://github.com/fastlane/fastlane/issues/16109 [closed] 6 💬
    6 weeks ago

➡  Fastlane not working on MacOS Catalina Dev beta
    https://github.com/fastlane/fastlane/issues/15183 [closed] 23 💬
    10 May 2020

and 3 more at: https://github.com/fastlane/fastlane/search?q=You%20don%27t%20have%20write%20permissions%20for%20the%20%2FLibrary%2FRuby%2FGems%2F2.6.0%20directory.&type=Issues&utf8=✓

🔗  You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
	28: from /usr/local/bin/fastlane:23:in `<main>'
	27: from /usr/local/bin/fastlane:23:in `load'
	26: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/bin/fastlane:23:in `<top (required)>'
	25: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	24: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	23: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	22: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	21: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	20: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	19: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	18: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	16: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	14: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	13: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	12: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	10: from Fastfile:271:in `block (2 levels) in parsing_binding'
	 9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/fast_file.rb:232:in `fastlane_require'
	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/fastlane_require.rb:36:in `install_gem_if_needed'
	 7: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/commands/install_command.rb:212:in `install_gem'
	 6: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/request_set.rb:183:in `install'
	 5: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/request_set.rb:183:in `each'
	 4: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/request_set.rb:195:in `block in install'
	 3: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/resolver/specification.rb:93:in `install'
	 2: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/installer.rb:294:in `install'
	 1: from /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/installer.rb:894:in `pre_install_checks'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/installer.rb:724:in `verify_gem_home': [!] You don't have write permissions for the /Library/Ruby/Gems/2.6.0 directory. (Gem::FilePermissionError)

@oleksiisedun Oops, sorry! Can you change fastlane_require 'spaceship' to require 'spaceship'?

Of course, results:
ci$ fastlane test_update
[✔] 🚀
[20:41:41]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[20:41:42]: ------------------------------
[20:41:42]: --- Step: default_platform ---
[20:41:42]: ------------------------------
[20:41:42]: Driving the lane 'ios test_update' 🚀
[20:41:48]: Which release type?
1. MANUAL
2. AFTER_APPROVAL
3. Don't update
?  1
[20:43:00]: Update copyright? (y/n)
n
[20:43:02]: Updating with: {:releaseType=>"MANUAL"}
+------------------+-----------------+
|            Lane Context            |
+------------------+-----------------+
| DEFAULT_PLATFORM | ios             |
| PLATFORM_NAME    | ios             |
| LANE_NAME        | ios test_update |
+------------------+-----------------+
[20:43:05]: An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified.

+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
+------+------------------+-------------+

[20:43:05]: fastlane finished with errors

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

➡  Error during uploading metadata: The attribute 'releaseType' can not be modified.
    https://github.com/fastlane/fastlane/issues/16911 [open] 4 💬
    a minute ago

➡  Deliver: The attribute 'releaseType' can not be modified
    https://github.com/fastlane/fastlane/issues/16679 [closed] 16 💬
    32 minutes ago

➡  Server error 504 when uploading metadata
    https://github.com/fastlane/fastlane/issues/16665 [closed] 63 💬
    3 weeks ago

🔗  You can ⌘ + double-click on links to open them directly in your browser.
Traceback (most recent call last):
	22: from /usr/local/bin/fastlane:23:in `<main>'
	21: from /usr/local/bin/fastlane:23:in `load'
	20: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/bin/fastlane:23:in `<top (required)>'
	19: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	18: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	17: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	16: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	15: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	14: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	13: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	12: from /Library/Ruby/Gems/2.6.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	11: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	10: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	 9: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	 8: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	 7: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	 6: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	 5: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	 4: from Fastfile:314:in `block (2 levels) in parsing_binding'
	 3: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:88:in `update'
	 2: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:733:in `patch_app_store_version'
	 1: from /Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/client.rb:110:in `patch'
/Library/Ruby/Gems/2.6.0/gems/fastlane-2.152.0/spaceship/lib/spaceship/connect_api/client.rb:163:in `handle_response': [!] An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified. (Spaceship::UnexpectedResponse)

@oleksiisedun Thanks for testing this! So the fix I put in for 2.152.0 for this was an order of operations thing which solved the issue for some of users. Your issue looks like be something much different 🤔
Are you able to go to the App Store Connect website and try to change this option there?

Do you see the option to change this there?
Does it allow you to successfully change it there?

An account that I use listed as Developer and Marketing. I am not able to change this option, please see screenshot: https://ibb.co/TgdH5fR.
In the past, I used the same account (with the same rights) to upload metadata without any issues.

@oleksiisedun Oh, interesting! It looks like the permission might have changed for this now 😱 I will reach out to someone to see if this should be considered an issue or if it was planned. Thank you for testing! I will find a way to fix this either way.

@oleksiisedun It sounds like this permission behavior you are experiencing is the expected behavior 🤷♂

@joshdholtz, please can you explain a bit further? An account that I use allows me to change metadata manually. I tried to update metadata using the deliver tool (using the same account), but it failed.

@oleksiisedun It seems like "Developer" and "Marketing" don't have the ability to update the "Release Type" (manual, automatic, automatic on date). But those roles should have the ability to update other meta information. But but you might not be seeing that because its failing on "Release Type".
Maybe I should add a check for account permission roles or something there? 🤔 And maybe only set release type if you have the proper permission and show a warning if not? Thoughts?

@joshdholtz, thank you for the provided info, now the problem is clear for me.

And maybe only set release type if you have the proper permission and show a warning if not?

I think it's a good idea. Also maybe you can add something like the skip_set_release_type parameter. It will be very useful for users with restricted permissions like me.

Yeah yeah, I like that! I will get on this 😊

I meet this problem. My account is admin.
Fastlane version:  2.158.0
my deliver config:
    skip_screenshots: true,
    automatic_release: false,
    platform:   'ios',
    ignore_language_directory_validation: true,
    #phased_release: true,
    metadata_path: "./fastlane/metadata/",
    force: true

error message:
Traceback (most recent call last):
	40: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/ruby_executable_hooks:24:in `<main>'
	39: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/ruby_executable_hooks:24:in `eval'
	38: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/fastlane:23:in `<main>'
	37: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/fastlane:23:in `load'
	36: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/bin/fastlane:23:in `<top (required)>'
	35: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	34: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	33: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	32: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	31: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	30: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	29: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	28: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	27: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	26: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	25: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	24: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	23: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	22: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	21: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	20: from Fastfile:8:in `block (2 levels) in parsing_binding'
	19: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	18: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:146:in `trigger_action_by_name'
	17: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:204:in `try_switch_to_lane'
	16: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	15: from Fastfile:14:in `block in parsing_binding'
	14: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	13: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	12: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	11: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	10: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	 9: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	 8: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	 7: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:17:in `run'
	 6: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/deliver/lib/deliver/runner.rb:43:in `run'
	 5: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/deliver/lib/deliver/runner.rb:124:in `upload_metadata'
	 4: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/deliver/lib/deliver/upload_metadata.rb:184:in `upload'
	 3: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:96:in `update'
	 2: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:772:in `patch_app_store_version'
	 1: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/api_client.rb:135:in `patch'
/Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/api_client.rb:188:in `handle_response': [!] An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified. (Spaceship::UnexpectedResponse)

I meet this problem. My account is admin.
Fastlane version: 2.158.0
my deliver config:
    skip_screenshots: true,
    automatic_release: false,
    platform:   'ios',
    ignore_language_directory_validation: true,
    #phased_release: true,
    metadata_path: "./fastlane/metadata/",
    force: true

error message:
Traceback (most recent call last):
	40: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/ruby_executable_hooks:24:in `<main>'
	39: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/ruby_executable_hooks:24:in `eval'
	38: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/fastlane:23:in `<main>'
	37: from /Users/test1/.rvm/gems/ruby-2.5.4/bin/fastlane:23:in `load'
	36: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/bin/fastlane:23:in `<top (required)>'
	35: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/cli_tools_distributor.rb:119:in `take_off'
	34: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	33: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	32: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	31: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	30: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	29: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	28: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	27: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	26: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	25: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	24: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	23: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	22: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	21: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	20: from Fastfile:8:in `block (2 levels) in parsing_binding'
	19: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	18: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:146:in `trigger_action_by_name'
	17: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:204:in `try_switch_to_lane'
	16: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	15: from Fastfile:14:in `block in parsing_binding'
	14: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	13: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	12: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	11: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	10: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	 9: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in `execute_action'
	 8: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	 7: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:17:in `run'
	 6: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/deliver/lib/deliver/runner.rb:43:in `run'
	 5: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/deliver/lib/deliver/runner.rb:124:in `upload_metadata'
	 4: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/deliver/lib/deliver/upload_metadata.rb:184:in `upload'
	 3: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:96:in `update'
	 2: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:772:in `patch_app_store_version'
	 1: from /Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/api_client.rb:135:in `patch'
/Users/test1/.rvm/gems/ruby-2.5.4/gems/fastlane-2.158.0/spaceship/lib/spaceship/connect_api/api_client.rb:188:in `handle_response': [!] An attribute value is not acceptable for the current resource state. - The attribute 'releaseType' can not be modified. (Spaceship::UnexpectedResponse)

It will be ok if I comment this line:
automatic_release: false

This is probably related to the "Make available for pre-order" flag in appstore connect. If you disable that option, you should be able to upload with fastlane. @joshdholtz do you have any idea how this could be fixed in fastlane?

@mogbot @myanime Ahhhhh, I think there are issues with this when its an "Apple Arcade" app and also "pre-order" 😱
I will look into how to best fix this while providing backwards capability for other users 🤔 Yell at me if you don't hear from me in a day or two 😉

I also get "An attribute value is not acceptable for the current resource state." (but only that message) - it seems as if that is the really last step when putting our apps in review, it may be a run condition?
No Apple Arcade and no pre-order here! Also no changes in submission_information values or other flags. Just delivering a new version of our app with updated screenshots and metadata...
Thanks in advance.

Hey, fam! 👋
I made a fix for this over at https://github.com/fastlane/fastlane/pull/17383. automatic_release is now optional (which is a slightly breaking change but I think this is how it should behave). If you are an Apple Arcade, a Pre Order, or just don’t this to be set you can either 1) not set this or 2) explicitly set it to nil and you should be good 👍
This decision was made because we are actually not able to query if an app is an Apple Arcade app with the official App Store Connect API so I will be filing a radar for that ability. But I do think that users should have the option to not set this at all.
There are instructions over in the PR for trying this out. I would greatly appreciate if somebody could to make sure this is a valid solution.
—
Oh! I also added a 2 second sleep before and after the app version update for some of the users seeing “ An attribute value is not acceptable for the current resource state.” because I think there could be a weird race condition thing going on 🤷♂

The issue is fixed, thank you @joshdholtz!


Extend the README

@yegor256 suggested to extend the README (link) with:

A short overview of the project
A quick start

@deemp please, don't forget to remove this information from the statically generated site, to avoid duplication

@yegor256, good point. I'm not sure we should avoid duplication here. Some people may prefer to read the site instead of the README. Hence, they may want to read the project overview and the quick start on the site.
I believe we can share some sections between README and the site. mdbook and mdsh (tools that we use) allow inlining files.

@deemp sure, render it in both places is fine, as long as you don't duplicate the content inside the repo


OracleJDK to OpenJDK fix for license issue

This codebase uses JavaFX (or another oracleJDK specific jar).
As you know, Oracle is starting JDK license model in 2019.
My understanding is this specific library is only used in a custom configuration to pop web browser client. We don't use this and have no need for this feature.
Anyone know the specific details to use alternate library or process and make this codebase openJDK8 compliant?
Thanks
Joe

OpenJFX is bundled with the release. It is GPLv2 with the classpath exception:
https://github.com/javafxports/openjdk-jfx/blob/develop/LICENSE

OpenJFX is free software, licensed under the GPL with the class path exception, just like the OpenJDK.
SOURCE: https://openjfx.io/

My understanding is that there is no problem with bundling OpenJFX in this manner.
I am not a lawyer.

I am running this on AdoptOpenJDK 11 locally without issues.

I’m going to guess this is okay and close this.


Add required steps for installing OSS Calico on Openshift v4.16+ on AWS

Product Version(s):

Issue:

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

LGTM, with suggestions.
@coutinhop This PR covers OSS 3.28+. Am I right to assume this does not apply to 3.27? What about CE?

Thanks @ctauchen and @radTuti ! I've addressed your comments. Yes, this doesn't apply to v3.27 as the product changes to support OCP v4.16+ were only backported to v3.28+. The changes for Calico EE are still in flight, I'll change the docs once the product changes are merged.

LGTM


Update OpenCV from 3.4.1 to 3.4.2

Current image fails to build because latest gocv version requires OpenCV 3.4.2

Thank you!


API

Is necessary to use public API, or can we use other API as per our choice

Absolutely, any API would work, you can even create your own API.
But keep in mind that you should have proper rights to use it and it must be HTTPS.


Update Generic Pages “en-ce-moment”

Automatically generated by Netlify CMS

👷 Deploy Preview for shiny-babka-998c7e processing.

Name
Link

🔨 Latest commit
8754a736b123a204cddf73b82e846a99b0974fb1

🔍 Latest deploy log
https://app.netlify.com/sites/shiny-babka-998c7e/deploys/668f9440be6b740008f89979


[Improvement] Standardize the invocation method for the Builder pattern

What would you like to be improved?
There are two invocations for Builder pattern in the project currently:
case one:
ColumnDTO column =
        ColumnDTO.builder()
            .withName(name)
            .withDataType(type)
            .withComment(comment)
            .withNullable(false)
            .build();

case two:
SchemaDTO schema =
        new SchemaDTO.Builder()
            .withName("SchemaA")
            .withComment("comment")
            .withAudit(audit)
            .build();

The first provides fluent interfaces that make the code cleaner and more readable
How should we improve?
Standardize the invocation method to the first format.
Following are some classes that need to be modified. If you are interested in this, please create a new subtask issue before starting work.

[x] AuditInfo.java (#1730 )
[ ] BaseColumnExtension.java
[ ] CatalogDTO.java
[x] CatalogEntity.java #2023
[ ] DistributionDTO.java
[ ] FuncExpressionDTO.java
[ ] HiveColumn.java
[ ] HiveSchema.java
[ ] HiveTable.java
[ ] IcebergSchema.java
[ ] LiteralDTO.java
[ ] MetalakeDTO.java
[ ] SchemaDTO.java
[ ] SortOrderDTO.java
[ ] TableDTO.java

in which file/files does this have to be updated?

in which file/files does this have to be updated?

There are many files that need to be updated. You can find them by searching for .build() throughout the text, and then locate the corresponding class file using the code new xxx.Builder(). After you updated the class file, you may find the build failed then you just need to modify the invocation according to the error message
There are many files that need to be updated. You can:

Search for .build() throughout the text and
Identify the results that use new xxx.Builder()
Once you have found the corresponding class file (usually xxx.java), update it. (such as AuditInfo.java, SchemaDTO.java etc.)
You may encounter build failures after updating the class files. In that case, simply modify the call according to the error message
Just make sure the CI passed in Github

Tips: You can split this task into multiple PRs. Once the first PR is merged, you will know how to proceed. However, ensure that each PR passes the CI. Enjoy the coding :)

For example , i have found an instance of the use of xxx.Builder() , but when I visit class of AudioInfo or Its superclasses/interfaces , I can't find an instance of SchemaDTO , please guide me regarding what to update in this instance so I get an overall idea.

You can take a look at this draft PR #1663

in which file/files does this have to be updated?

[ ] AuditInfo.java
[ ] BaseColumnExtension.java
[ ] CatalogDTO.java
[ ] CatalogEntity.java
[ ] DistributionDTO.java
[ ] FuncExpressionDTO.java
[ ] HiveColumn.java
[ ] HiveSchema.java
[ ] HiveTable.java
[ ] IcebergSchema.java
[ ] LiteralDTO.java
[ ] MetalakeDTO.java
[ ] SchemaDTO.java
[ ] SortOrderDTO.java
[ ] TableDTO.java

I think it's great.
ColumnDTO column =
        ColumnDTO.builder()
            .withName(name)
            .withDataType(type)
            .withComment(comment)
            .withNullable(false)
            .build();

In the fist case, if we use the lombok @Builder to generate it. It will have no prefix with until we add setterPrefix='with'
@mchades Do you have any tendencies？ Or why do we just use the Lombok @Builder to generate it?
ColumnDTO column =
        ColumnDTO.builder()
            .name(name)
            .dataType(type)
            .comment(comment)
            .nullable(false)
            .build();

I think it's great.
ColumnDTO column =
        ColumnDTO.builder()
            .withName(name)
            .withDataType(type)
            .withComment(comment)
            .withNullable(false)
            .build();

In the fist case, if we use the lombok @builder to generate it. It will have no prefix with until we add setterPrefix='with'
@mchades Do you have any tendencies？ Or why do we just use the Lombok @builder to generate it?
ColumnDTO column =
        ColumnDTO.builder()
            .name(name)
            .dataType(type)
            .comment(comment)
            .nullable(false)
            .build();

I prefer using withXxx() because it aligns with the existing Builder pattern used in our project.

@mchades which DTO's i can pick up.

@mchades i am picking up CatalogDTO

@mchades i am picking up CatalogDTO

Sorry, it seems #2560 already resolved all issues. I think you can check out the other GOOD FIRST ISSUES, thank you so much for your enthusiasm! @ajayl83

@charliecheng630
Can you leave a comment here, I'm handling the release work, as this is your credit, but due to GitHub restrictions, I can't assign it to you.


Transparent WebM videos do not render correctly

It seems that previously rendered video frames are not cleared:
https://jsfiddle.net/vm4h4928/
I dived into the code but could not find the cause of this issue. All you do is upload the texture, but this should also include transparent pixels?

Interesting point - this only happens for WebGL. It displays fine on Canvas renderer

@themoonrat Anything new regarding this issue?

Honestly not sure if this is a pixi bug since we just pass the video directly to the gl context as a texture and the browser takes care of it.

@englercj It seems to be a pixi4 problem
I forked the jsfiddle and changed it to pixiv3
That one seems to do it correctly.
https://jsfiddle.net/t06hep8m/

@englercj Me and my colleague @pietervanneste  did some investagation.
It seems that following part is causing the problem.
if(newHeight !== this.height || newWidth !== this.width)
	{
		gl.texImage2D(gl.TEXTURE_2D, 0, this.format, this.format, this.type, source);
	}
	else
	{
    	gl.texSubImage2D(gl.TEXTURE_2D, 0, 0, 0, this.format, this.type, source);
	}

If we change it to
gl.texImage2D(gl.TEXTURE_2D, 0, this.format, this.format, this.type, source);

so we don't call gl.texSubImage2D, It seems to clear the texture after every frame.

I can confirm that @barbarosso's fix does indeed work. Can we please get this fix applied to the latest version of Pixi.js as soon as possible?

I believe this is fixed in v5


Random Passcode exceeds the range

Problem
During the opening commissioning window ECM, the chip device controller assigns Random Passcode which exceeds the Passcode range (e.g 109172366).
<IP_ADDRESS>. Passcode
A Passcode SHALL be included as a 27-bit unsigned integer, which serves as proof of possession
during commissioning. The 27-bit unsigned integer encodes an 8-digit decimal numeric value, and
therefore shall be restricted to the values 0x0000001 to 0x5F5E0FE (00000001 to 99999998 in decimal),
excluding the invalid Passcode values.

Isn't it fixed by https://github.com/project-chip/connectedhomeip/commit/12ce67285e75337d613361620bf4ccadb861167f?


healthcheck: exclude hosts when receiving x-envoy-immediate-health-check-fail

Send x-envoy-immediate-health-check-fail on all responses that the
health check filter processes, not just non-HC responses.
Exclude hosts from load balancing when x-envoy-immediate-health-check-fail
is received.
Can be reverted via the envoy.reloadable_features.health_check.immediate_failure_exclude_from_cluster
feature flag.

Fixes https://github.com/envoyproxy/envoy/issues/9246
Risk Level: Medium
Testing: New UTs and integration tests, fixed other tests
Docs Changes: Added
Release Notes: Added
Platform Specific Features: N/A
Runtime guard: Added

cc @jessicayuen

cc @jessicayuen

@snowp @yanavlasov merged main PTAL

@snowp @yanavlasov merged main PTAL


Try out gomponents at new module path

Is your feature request related to a problem? Please describe.
I'm trying to move gomponents to a new module path, maragu.dev/gomponents. If you have the time and would like to help out, could you do go get<EMAIL_ADDRESS>global-replace the old import path with the new one in Go files, and see whether everything still works?
Describe the solution you'd like
I would like it to still work. :D
Describe alternatives you've considered
Not moving the import path.
Additional context
https://github.com/maragudk/gomponents/releases/tag/v1.0.0-beta1

Works well

@EwenQuim thank you for the quick response! Excellent. I've also not hit any issues yet migrating a large codebase.