chore: 优化 CI Workflow

👀 PR includes

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[x] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description

issue 模版调整为表单, 避免不按模版填写 (参考 G6)

单测按包单独运行

增加自动回复

🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[ ] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

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

Project coverage is 75.71%. Comparing base (ecdc9c8) to head (64c5c1e).
Report is 553 commits behind head on next.

Additional details and impacted files
@@            Coverage Diff             @@
##             next    #3033      +/-   ##
==========================================
- Coverage   75.77%   75.71%   -0.06%
==========================================
  Files         257       19     -238
  Lines       11994      663   -11331
  Branches     2464      116    -2348
==========================================
- Hits         9088      502    -8586
+ Misses       1398       92    -1306
+ Partials     1508       69    -1439

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

:tada: This PR is included in version @antv/s2-v2.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-vue-v2.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-v2.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version @antv/s2-react-components-v2.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


test(hardware): replace pytest-aiohttp with pytest-asyncio

Overview
Just like #10012 and #9981 we should replace pytest-aiohttp with pytest-asyncio. It's faster.
Changelog

replace pytest-aiohttp with pytest-asyncio
remove loop fixture usage
lint

Review requests

Tested locally included integration tests using sim_sock_can

Risk assessment
None

Code changes make sense to me, and running make -C hardware test works. 🧪 I'm not sure how make test-with-emulator works, so I couldn't verify that.

I verified make test-with-emulator.  It requires either ot3 docker emulation or locally running firmware and virtual CAN network,

Looks like there's a hanging test:
Wed, 20 Apr 2022 13:41:21 GMT tests/opentrons/hardware_control/test_poller.py ......                   [ 33%]
Wed, 20 Apr 2022 14:02:36 GMT Error: The operation was canceled.

😬


Creating logging service

closes #101
replaces #112

Looks good 👍 Few points from me:

Need to resolve the lint errors, ideally before transitioning from draft to open.

Will do a PR soon with vscode changes

Avoid using any (this will become an error shortly).

Solved by using unknown

I'm interested to see how each module will be able to easily import this without having to declare if it's hidden each time. Maybe we expose Logger as a named export and have the default export predefined to be hidden in production/tests? It's a common way of emulating the singleton pattern without having to implement logic like instances (I suppose we haven't really got a singleton here as you can have two instances 😛)

Yes, so I found that doing Logger.debug would be the way to go. As anyone who wants to debug can go and import the service and set debug to true as it is fairly encapsulated. I removed the 2 instances thing. I think it's a better approach this way but let me know what you think.


refactor: cleanup and ethereumex bump

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Change 1
Change 2
...

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Coverage decreased (-13.9%) to 70.754% when pulling 6423f2dee321ebecab91c773cf4f42c134e7c769 on inomurko/exvcr+exethereum into f3eb68198072485909b2949abccafe7ab03930d9 on master.


refactor!: Rename command line flags for the sake of consistency

BREAKING CHANGE: renamed -c/--confdir to -cd/--configDirand -f/--file to -cf/--configFile
Signed-off-by: Ginny Guan<EMAIL_ADDRESS>

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-mqtt-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[x] I have opened a PR for the related docs change (if not, why?)
https://github.com/edgexfoundry/edgex-docs/pull/916

Testing Instructions

build device-mqtt
run device-mqtt  -h
verify flags in help have new names
run device-mqtt --confdir <path>, device-mqtt -c <path>, device-mqtt --file <file> and device-mqtt -f <file>
verify errors that the flags are not defined
run device-mqtt --configDir <path>, device-mqtt -cd <path>, device-mqtt --configFile <file> and device-mqtt -cf <file>

New Dependency Instructions (If applicable)

Codecov Report

Merging #444 (f7067d4) into main (2c0ad64) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #444   +/-   ##
=======================================
  Coverage   21.34%   21.34%
=======================================
  Files           5        5
  Lines         492      492
=======================================
  Hits          105      105
  Misses        374      374
  Partials       13       13

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Only send p1 and flaky reports weekly

Daily is probably more frequent than we need for this (reference https://lists.apache.org/thread/29ggd9b6v00l5copnh1cdmcg1bwo5b4t)

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

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

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

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

Can one of the admins verify this patch?


feat: allow to select fields for upsert

This PR attempts to solve #4602 by allowing passing specific columns on which the upsert condition is done. This allows to use entities and generate an ID server-side.
I'm not 100% sure about the approach here, but the change I did is that if you select a different column to act as the on conflict column and that the PK is also present, then it won't update any field on conflict.

Do you plan to work on this in the near future? I'd like to ship new feature release (from master, so this would need to be targetting that instead of v6), and wanted to have this in there as well.
Ideally, I'd ship it during this week, so will be happy to take over if you don't have time. I don't mind the proposal for onConflictFields and onConflictAction.

Hi @B4nan ,
Sorry, I am on holiday for two weeks and won't be able to work on this for this week :(.

Closing in favor of #4669


[gardening] Change static private to private static for consistency

Refs: #15182, #15153
Before the changes:

git grep "private static " | wc -l: 97
git grep "static private " | wc -l: 5

@swift-ci smoke test

@swift-ci smoke test

Please don't do this to test files; some of them are testing that unusual orders still produce expected results!

Okay, sorry for bothering you 😓

Ah, thank you in general for cleaning things up! It's just test files that I'm concerned about.


How much VRAM is needed for this model?

I have 24GB of VRAM which I assumed was enough to run a 7B parameter model. Are you able to let me know how much VRAM you are using with this notebook?

Resolved by loading in 4bit.
import torch
from transformers import AutoTokenizer, AutoModelForCausalLM
from transformers import LlamaTokenizer, LlamaForCausalLM, MistralForCausalLM
import bitsandbytes, flash_attn

tokenizer = LlamaTokenizer.from_pretrained('teknium/OpenHermes-2.5-Mistral-7B', trust_remote_code=True)
model = MistralForCausalLM.from_pretrained(
    "teknium/OpenHermes-2.5-Mistral-7B",
    torch_dtype=torch.float16,
    device_map="auto",#{'': 'cuda:0'},
    load_in_8bit=False,
    load_in_4bit=True,
    use_flash_attention_2=True
)


1400: Creating helper methods for getting attributes from the Context

Adding ContextUtils class with a helper method for fetching attributes from the Context and returning them as a specified type.
Updating classes which retrieve data from the attributes context to use the util method.
https://github.com/SecureApiGateway/SecureApiGateway/issues/1400

Shaun Harrison is inviting you to a scheduled ForgeRock Zoom meeting.
Topic: [SecureApiGateway/secure-api-gateway-core] 1400: Creating helper
methods for getting attributes from the Context (PR #34)
Time: Apr 25, 2024 03:00 PM London
Join Zoom Meeting
https://forgerock.zoom.us/j/99775985404
Meeting ID: 997 7598 5404
One tap mobile
+13092053325,,99775985404# US
+13126266799,,99775985404# US (Chicago)
Dial by your location
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US (Chicago)
+1<PHONE_NUMBER> US (New York)
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US (Washington DC)
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US (San Jose)
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US
+1<PHONE_NUMBER> US (Tacoma)
+1<PHONE_NUMBER> US (Houston)
+1<PHONE_NUMBER> US
+49 69 5050 0951 Germany
+49 69 5050 0952 Germany
+49<PHONE_NUMBER> Germany
+49 69 7104 9922 Germany
+49 69 3807 9883 Germany
+49 69 3807 9884 Germany
+43 12 535 501 Austria
+43 12 535 502 Austria
+43<PHONE_NUMBER> Austria
+43 72 011 5988 Austria
+43<PHONE_NUMBER> Austria
+41 31 528 09 88 Switzerland
+41 43 210 70 42 Switzerland
+41 43 210 71 08 Switzerland
+41 44 529 92 72 Switzerland
+41 22 591 00 05 Switzerland
+41 22 591 01 56 Switzerland
+44<PHONE_NUMBER> United Kingdom
+44<PHONE_NUMBER> United Kingdom
+44<PHONE_NUMBER> United Kingdom
+44<PHONE_NUMBER> United Kingdom
+44<PHONE_NUMBER> United Kingdom
+44<PHONE_NUMBER> United Kingdom
+44<PHONE_NUMBER> United Kingdom
+47 2400 4735 Norway
+47 2400 4736 Norway
+33 1 7037 9729 France
+33 1 7095 0103 France
+33 1 7095 0350 France
+33 1 8699 5831 France
+33 1 7037 2246 France
+65 3129 4891 Singapore
+65 3129 4892 Singapore
+65 3158 7288 Singapore
+65 3165 1065 Singapore
+61 3 7018 2005 Australia
+61 7 3185 3730 Australia
+61 8 6119 3900 Australia
+61 8 7150 1149 Australia
+61 2 8015 6011 Australia
+64 9 884 6780 New Zealand
+64 3 659 0603 New Zealand
+64 4 886 0026 New Zealand
Meeting ID: 997 7598 5404
Find your local number: https://forgerock.zoom.us/u/adauzlXXhx
--
CONFIDENTIALITY NOTICE: This email may contain confidential and privileged
material for the sole use of the intended recipient(s). Any review, use,
distribution or disclosure by others is strictly prohibited.  If you have
received this communication in error, please notify the sender immediately
by e-mail and delete the message and any file attachments from your
computer. Thank you.


[Error 1053] Can't run gitea as a Windows Service

Gitea version (or commit ref): 10effb396 (and 2f39fc7bb)
Git version: 1.8.2+3-g10effb396 (and 1.9.0+dev-347-g2f39fc7bb)
Operating system: Windows 10 Pro build 17134
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
I can create the service however I can't start it. (It runs fine when I run the exe as an user application.)
Error 1053: The service did not respond to the start or control request in a timely fashion
Screenshots
No screenshots because I can't really switch language in the os.

Is there something in the Windows event log?

Yeah, just that it timed out after 30000ms

What about the user? Does he habe sufficient rights to read/write the folders and to open a network connection?

Probably.
When I started the exe it worked. (And I tried to launch the service with my account but that didn't work either)

Can you post your app.ini (minus passwords and secrets)?

Of course
APP_NAME = Gitea: Git with a cup of tea
RUN_USER = NB-DELL-009$
RUN_MODE = prod

[oauth2]
JWT_SECRET = [snip]

[security]
INTERNAL_TOKEN = [snip]
RUN_USER       = NB-DELL-009$
INSTALL_LOCK   = true
SECRET_KEY     = [snip]

[database]
DB_TYPE  = sqlite3
HOST     = <IP_ADDRESS>:3306
NAME     = gitea
USER     = gitea
PASSWD   =
SSL_MODE = disable
PATH     = C:/gitea/data/gitea.db

[repository]
ROOT = C:/gitea/gitea-repositories

[server]
SSH_DOMAIN       = localhost
DOMAIN           = localhost
HTTP_PORT        = 3000
ROOT_URL         = [snip]
DISABLE_SSH      = false
SSH_PORT         = 22
LFS_START_SERVER = true
LFS_CONTENT_PATH = C:/gitea/data/lfs
LFS_JWT_SECRET   = [snip]
OFFLINE_MODE     = false

[mailer]
ENABLED = false

[service]
REGISTER_EMAIL_CONFIRM            = false
ENABLE_NOTIFY_MAIL                = false
DISABLE_REGISTRATION              = false
ALLOW_ONLY_EXTERNAL_REGISTRATION  = false
ENABLE_CAPTCHA                    = false
REQUIRE_SIGNIN_VIEW               = false
DEFAULT_KEEP_EMAIL_PRIVATE        = false
DEFAULT_ALLOW_CREATE_ORGANIZATION = true
DEFAULT_ENABLE_TIMETRACKING       = true
NO_REPLY_ADDRESS                  = noreply.example.org

[picture]
DISABLE_GRAVATAR        = false
ENABLE_FEDERATED_AVATAR = true

[openid]
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = true

[session]
PROVIDER = file

[log]
MODE      = file
LEVEL     = Info
ROOT_PATH = C:/gitea/log

Had this same issue.
The problem was that git was not in path at the system level.

I had the same issue today, that's how I fixed it:
To see what is the actual error, open a cmd in gitea folder and type the following command:
cmd /k gitea.exe (to avoid the window from closing)

In my case, I added git to the path.
Then I launched the .exe with the same command:

I still had the 1053 error when I launched the service at that point:

So I went to the Gitea's logs (gitea/log/gitea.log) and had an error:

Then I just created the role 'gitea' wich was missing and it solved the problem!
Hope this helps :)

This issue actually not resolve yet. Could we re-open it?

I had the same issue today, that's how I've fixed it:
To see the actual error, open a cmd in gitea folder and type the following command:
cmd /k gitea.exe (to avoid the window from closing)

In my case, I added git to the path.
Then I launched the .exe with the same command:

I still had the 1053 error when I launched the service at that point:

So I went to the Gitea's logs (gitea/log/gitea.log) and had an error:

Then I just created the role 'gitea' wich was missing and it solved the problem!
Hope this helps :)

Not work for me. There is no log file generated. The log folder is empty.

This issue is actually unresolved. Could we re-open it?
Appreciate for any help in advance.

@PlusoneWang please open another issue - with more information on your specific configuration i.e. complete version of gitea, your path and a suitably sanitized app.ini.
So far the above issues have been due to configuration and not due to a bug.

I had the same issue today, that's how I've fixed it:
To see the actual error, open a cmd in gitea folder and type the following command:
cmd /k gitea.exe (to avoid the window from closing)

In my case, I added git to the path.
Then I launched the .exe with the same command:

I still had the 1053 error when I launched the service at that point:

So I went to the Gitea's logs (gitea/log/gitea.log) and had an error:

Then I just created the role 'gitea' wich was missing and it solved the problem!
Hope this helps :)

和我的状况一样，是因为windows server 没有安装 git，所以 gitea无法在path中找到git的执行程序，添加上之后就好了
same iusse,need install git,and add git path to system environment variables


Support hidden .*.config.js files

Support a dot prefix on .config.js files (similar to .eslintrc.js like #58).

Can't you do this already with the js option?

@davidtheclark Maybe, but can it support both hidden and not?

I don't want to build this convention in by default, because I don't understand it's appeal and I don't think it's used outside of ESLint (right?). So the question is: how can the options change to accommodate your use-case?

@adjohnson916: After thinking about this more, this features seems pretty unnecessary to me. The number of possible variations are endless, and I feel comfortable drawing the line around the (significant) flexibility that the package already allows. However, if you do come up with a good idea for how this could fit into cosmiconfig's options, and what implementation would look like, feel free to re-open.

@AndersDJohnson This is now possible with v5. The searchPlaces option gives you enough flexibility over the names of the files that get searched.


Move columndef to external

@Risk-taker0501 here I move column definition to "external".
In real case using react-datatable2, column definition is coming from the consuming project.  I'm simulating this.
As said I cannot do TS properly, can you help to update the PR so it's TS?


Out action completes with non-empty mail queue

I've faced issues with unsent emails. Messages stay in a queue but I would expect a send task to stay active until queue is empty.

The code currently uses a very lame heuristic for controlling the postfix MTA https://github.com/mdomke/concourse-email-resource/blob/master/opt/resource/out#L40-L44. To be honest I'm not a postfix expert and don't now if there is a deterministic way to find out if all mails in the queue have already been delivered.


Fix object storage for python 3

Fixes #249

Huh, I wonder what this is

Apparently a potentially similar issue plagued tensorflow.

Related

I'm looking into fixing this

Thanks! Looks like the cause and solution is explained in https://github.com/swig/swig/pull/560

Seems from the openmoltools issue that the problem is creating the simtk.openmm.System object inside the generator was the culprit.

Let me fix.

Wait, we don't create a System object inside a generator in perses.tests.test_storage, do we?

No, I'm not sure what's going on here. But I can say that this function:
def test_storage_hopefully_works():
    testsystem_name = 'ValenceSmallMoleculeLibraryTestSystem'
    niterations = 5 # number of iterations to run

    # Create storage.
    tmpfile = tempfile.NamedTemporaryFile()
    filename = tmpfile.name

    import perses.tests.testsystems
    # Instantiate test system.
    testsystem = perses.tests.testsystems.ValenceSmallMoleculeLibraryTestSystem(storage_filename=filename)

    # Test MCMCSampler samplers.
    #for environment in testsystem.environments:
    environment = 'vacuum'
    mcmc_sampler = testsystem.mcmc_samplers[environment]
    mcmc_sampler.verbose = False
    f = partial(run_sampler, mcmc_sampler, niterations)
    f.description = "Testing MCMCSampler for %s with environment %s" % (testsystem_name, environment)
    return f

works, whereas if we replace the last line with yield f it gives the familiar error:
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/grinawap/PycharmProjects/perses/perses/tests/test_storage.py", line 195, in <module>
    for t in test_storage_hopefully_works():
SystemError: <built-in function delete_System> returned a result with an error set

Seems like when the StopIteration exception is raised by the generator (standard behavior), a SystemError is being thrown. But I have no idea why, or what that built-in function is.

In fact, just yielding the mcmc_sampler causes the error:
def test_storage_hopefully_works():
    testsystem_name = 'ValenceSmallMoleculeLibraryTestSystem'
    niterations = 5 # number of iterations to run

    # Create storage.
    tmpfile = tempfile.NamedTemporaryFile()
    filename = tmpfile.name

    import perses.tests.testsystems
    # Instantiate test system.
    testsystem = perses.tests.testsystems.ValenceSmallMoleculeLibraryTestSystem(storage_filename=filename)

    # Test MCMCSampler samplers.
    #for environment in testsystem.environments:
    environment = 'vacuum'
    mcmc_sampler = testsystem.mcmc_samplers[environment]
    mcmc_sampler.verbose = False
    #f = partial(mcmc_sampler.run, niterations)
    #f.description = "Testing MCMCSampler for %s with environment %s" % (testsystem_name, environment)
    yield mcmc_sampler

if __name__ == "__main__":
    for t in test_storage_hopefully_works():
        pass

Yielding the testsystem does not.

This fails:
def thermostate_generator():
    for i in range(2):
        system = openmm.System()
        yield ThermodynamicState(system, 30.0*unit.kelvin)

if __name__ == "__main__":
    for t in test_storage_hopefully_works():
        pass

@bas-rustenburg points out that the problem may lie in the version of SWIG.

Yeah, its what John pointed out in swig. It just hasn't been included yet in the version of SWIG that OpenMM is built against.

My suggested solution for now, stop using the generator concept here until OpenMM has updated it's SWIG version.

What version of swig do we need?
I think we've pinned the openmm recipe to swig ==3.0.7.

Looks like we need swig 3.0.8 or later.

Might be some way around it? Interestingly this code passes:
def thermostate_generator():
    for i in range(2):
        yield ThermodynamicState(openmm.System(), 30.0*unit.kelvin)

while this fails:
def thermostate_generator():
    for i in range(2):
        system = openmm.System()
        yield ThermodynamicState(system, 30.0*unit.kelvin)

OK, a dumb fix is in.

OK, all tests pass.


Add AlphaFilter, deprecate VoidFilter

subj
#4334

I need this PR . I hope it could be merged as soon as possible . Thanks.

There's an issue with TypeScript currently, the master of @types/pixi.js includes AlphaFilter and not VoidFilter, but the master of npm pixi.js doesn't include AlphaFilter.

oh, right, its 4.6.0 soon to be released :)

4.6.0 is here: https://github.com/pixijs/pixi.js/releases/tag/v4.6.0 , now ts is up-to-date


Declaring variables inside selectors and redefine variable inside nested media query doesn't work

Hi, I just read the post on Smashing Magazine and want to give this a try. Here's the issue I met.
  .cell__subtitle {
    @include css-vars(( --margin-left: r(1) ));
    display    : inline-block;
    margin-left: var(--margin-left);
    font-size  : 12px;
    @include susy($tablet) {
      display: block;
      @include css-vars(( --margin-left: 0 ));
    }
  }

The margin-left: 0 didn't show in browser inspector, but when using this in native way, it worked.

It's not a bug, it's one of the caveats.
Just check https://github.com/malyw/css-vars#caveats
"E.g. when you use assigned variable to define something in CSS and then reassign it- the used value will be updated. sass just inline values, so there will be no effect when you change a variable after."
Which means, till you are migrated, you have to do:
@include susy($tablet) {
display: block;
@include css-vars(( --margin-left: 0 ));
margin-left: var(--margin-left);
}
This example shows why CSS variables are more powerful than preprocessors',
as for native variables, you just change a value for a media query and browser reapplies it,
but for processors you have to provide additional CSS output.


Convert Python type hints in tools/make_rst.py to be PEP 484-compatible

Based on @AaronRecord 's comment in #63510, I checked the required Python version in the docs. Since Python 3.5+ is required, we can use type hints based on PEP 484.
Note that this does not include variable type hints (not available until 3.6), so they are left as-is.
There is only one type error left & that has to do with annotations (return_type is unbound - line 350). Looking at the XML in the classes directory, annotations don't seem to be used anywhere. Old code? Should the code to handle them be removed?
(This change is compatible with 3.x since it also requires Python 3.5+ and can be cherry-picked.)
Edit: just to note that I compared before-and-after results and they were the same.

For contributor tooling, we can require Python 3.6+ even in the 3.x branch. Therefore, you can use the : syntax for variable declarations as well :slightly_smiling_face:

There is only one type error left & that has to do with annotations (return_type is unbound - line 350). Looking at the XML in the classes directory, annotations don't seem to be used anywhere. Old code? Should the code to handle them be removed?

You couldn't find them, because they are only exposed in the docs for the GDScript module, here https://github.com/godotengine/godot/blob/master/modules/gdscript/doc_classes/%40GDScript.xml

Thanks @YuriSizov! I'll make that change.
@Calinou : Should I convert the variable declarations  as part of this PR then?
(Once I figure out why Python in the CI is not doing the same thing as on my machine... 😄 )

@YuriSizov - making that change does result in some differences in<EMAIL_ADDRESS>Example before:
Annotations
-----------

.. _class_@GDScript_annotation_export:

- :ref:`bool<class_bool>` **@export** **(** **)**

----

.. _class_@GDScript_annotation_export_category:

- :ref:`bool<class_bool>` **@export_category** **(** :ref:`String<class_String>` name **)**

...

Example after:
Annotations
-----------

.. _class_@GDScript_annotation_export:

- void **@export** **(** **)**

----

.. _class_@GDScript_annotation_export_category:

- void **@export_category** **(** :ref:`String<class_String>` name **)**

...

Does this look correct?

Does this look correct?

Definitely more correct than it is now 😃 I thought I removed the return type completely when printing annotations, but I guess I didn't? Ideally we don't need to say anything at all about their return types, but that can be fixed later. This is definitely better.

Thanks!


Connect ~ENVA, ~ENVB, ~OEQ, ~ALERT to spare FPGA balls

These are all active-low with pullups, so they can be shared by the FPGA and FX2 for added flexibility.

On second thought having two entities in the system control I/O buffers doesn't sound like such an awesome idea after all, so probably not.


Create a route to access the microservice

As a develoepr
I need to create a route to the wishlist service in OpenShift
So that the service is accessible externally
Details and Assumptions

The route will expose the service using an environment variable for BASE_URL.

Acceptance Criteria
Given a deployed wishlist service in Kubernetes
When I create a route to the service
Then the service should be accessible via the defined route

I think starting from slides 200 has the instruction, just bunch of manual operations but I have no idea what kind of code needs to be commit.
name: cd-pipeline


Is there a way to restore BIOS motherboard information to NUC defaults?

My system identifies as:
Intel Macmini8,1
BIOS
Version
1<IP_ADDRESS>.0
Date
1/17/2020
MOTHERBOARD
Manufacturer
Intel Corporation
Model
Mac-XXXXXXXXXXXXXXXX (My board id)
Version
Macmini8,1
This seems to confuse Intel Driver Support Assistant.
I keep getting a notification that there would be an update for Intel® HD Graphics 630. The update then cannot be installed.
I did not get offered the latest BIOS, I had to download it manually.
Is there a way to (at least temporarily) put back the NUC8I7HVK motherboard info?
I already tried NVRAM reset, but it still identifies as Macmini8,1

You need to boot into Windows without using OpenCore. An easy way is to open EFI Shell and run windows' \EFI\Microsoft\boot\bootmgfw.efi in the EFI partition.

I'm not sure this is your issue @HorstBrack75 , as I have this same symptom but I am not using OpenCore to boot to Windows.
I think it's because the driver offered by Intel Driver Support is a generic driver, so the installer rejects the NUC as being a valid target, instead requiring the custom one.  Well, that was the error message last time I checked, but it used to be fine, so if you can get round it I'll be interested too!

After resetting NVRAM and booting withou OpenCore, the system now identifies as:
Version
HNKBLi70.86A.0059.2019.1112.1124
Date
11/12/2019
MOTHERBOARD
Manufacturer
Intel Corporation
Model
Unknown
Version
J68196-503
The Model "Unknown" still bothers me, but at least I could now finally install igfx_win10_100.8190 and the intel updater does no longer offer an update.


Errors trying to run set up for the C IoT hub sample on Raspberri Pi - linking errors

Followed the steps to get the sample app running on my Raspberry Pi but ran into the following errors trying to run the set up script. Let me know if you need more info to diagnose, I was unable to complete the tutorial:
Scanning dependencies of target app
[ 20%] Building C object CMakeFiles/app.dir/main.c.o
[ 40%] Building C object CMakeFiles/app.dir/bme280.c.o
[ 60%] Building C object CMakeFiles/app.dir/wiring.c.o
[ 80%] Building C object CMakeFiles/app.dir/telemetry.c.o
/home/pi/iot-hub-c-raspberrypi-client-app/telemetry.c: In function ‘exec_comman ’:
/home/pi/iot-hub-c-raspberrypi-client-app/telemetry.c:144:19: warning: implicit declaration of function ‘popen’ [-Wimplicit-function-declaration]
FILE * pipe = popen(command, "r");
^~~~~
/home/pi/iot-hub-c-raspberrypi-client-app/telemetry.c:144:19: warning: initialization makes pointer from integer without a cast [-Wint-conversion]
[100%] Linking C executable app
//usr/local/lib/libiothub_client.a(iothub_client_ll_uploadtoblob.c.o): In function parse_result_json': iothub_client_ll_uploadtoblob.c:(.text+0x354): undefined reference to json_parse_string'
iothub_client_ll_uploadtoblob.c:(.text+0x3c0): undefined reference to json_value_get_object' iothub_client_ll_uploadtoblob.c:(.text+0x438): undefined reference to json_object_get_string'
iothub_client_ll_uploadtoblob.c:(.text+0x4b0): undefined reference to json_object_get_string' iothub_client_ll_uploadtoblob.c:(.text+0x528): undefined reference to json_object_get_string'
iothub_client_ll_uploadtoblob.c:(.text+0x5a0): undefined reference to json_object_get_string' iothub_client_ll_uploadtoblob.c:(.text+0x618): undefined reference to json_object_get_string'
iothub_client_ll_uploadtoblob.c:(.text+0x804): undefined reference to `json_value_free'
collect2: error: ld returned 1 exit status
CMakeFiles/app.dir/build.make:172: recipe for target 'app' failed
make[2]: *** [app] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/app.dir/all' failed
make[1]: *** [CMakeFiles/app.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

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

ID: 773d535b-29c4-20ca-d260-1d6c20fc43dd
Version Independent ID: b38b426a-6f56-026c-be29-6aee30586170
Content: Raspberry Pi to cloud (C) - Connect Raspberry Pi to Azure IoT Hub
Content Source: articles/iot-hub/iot-hub-raspberry-pi-kit-c-get-started.md
Service: iot-hub
GitHub Login: @rangv
Microsoft Alias: rangv

@inesk-vt I'm sorry you are facing this issue. We are aware there are issues going on with this sample. I will update with you shortly.

Great, thanks for the update!
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Alberto Vega<EMAIL_ADDRESS>Sent: Tuesday, February 5, 2019 6:52:59 PM
To: MicrosoftDocs/azure-docs
Cc: Ines Khelifi; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Errors trying to run set up for the C IoT hub sample on Raspberri Pi - linking errors (#24308)
@inesk-vthttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Finesk-vt&data=02|01||ba6eef798fe641add37008d68bde3499|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636850183805459884&sdata=U8SQSntTFvvDSk7J%2FHe2GsCGz7pR7OZGWZu00vCHvAY%3D&reserved=0 I'm sorry you are facing this issue. We are aware there are issues going on with this sample. I will update with you shortly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F24308%23issuecomment-460884190&data=02|01||ba6eef798fe641add37008d68bde3499|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636850183805469903&sdata=FEKEgOvPMgPw8LWqcbdDBttjKMuPftAKtRfUu1zoRQE%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FArtjNvhYtPZeSC0TJLrpzT48P-qwiGqdks5vKkOLgaJpZM4akFip&data=02|01||ba6eef798fe641add37008d68bde3499|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636850183805479899&sdata=khugSAZR0kjmGE19pPrmlAU1lXa3Np0DmyyqofBdJJs%3D&reserved=0.

I am facing this issue too. I am using Raspbian Stretch with RPi 3

@inesk-vt @kuriancjohn We are moving this issue to the Azure Samples repo. https://github.com/Azure-Samples/iot-hub-c-raspberrypi-client-app/issues/22


⚠ Fortnite has degraded performance

In 4a3235f, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1746 ms

Resolved: Fortnite performance has improved in 912aae1.


Unity 5.3 Windows example scene SQLiteException no such table: Person

For Windows x86 and x86_64 build this plugin appears to not be working
SQLiteException no such table: Person
when running scene "ExistingDBScript"
Works in the editor just fine.
This is under Windows 10 and Unity 5.3.1f1
CreateDBFromScript scene seems to work fine in editor and build.

Mono path[0] = 'E:/@Documents/Unity Repos/SQLite4Unity3d/Example_unity5/Build/test2/test2_Data/Managed'
Mono path[1] = 'E:/@Documents/Unity Repos/SQLite4Unity3d/Example_unity5/Build/test2/test2_Data/Mono'
Mono config path = 'E:/@Documents/Unity Repos/SQLite4Unity3d/Example_unity5/Build/test2/test2_Data/Mono/etc'
PlayerConnection initialized from E:/@Documents/Unity Repos/SQLite4Unity3d/Example_unity5/Build/test2/test2_Data (debug = 0)
PlayerConnection initialized network socket : <IP_ADDRESS> 55421
Multi-casting "[IP] <IP_ADDRESS> [Port] 55421 [Flags] 3 [Guid]<PHONE_NUMBER> [EditorId] 267894875 [Version] 1048832 [Id] WindowsPlayer(Big_Daddy) [Debug] 1" to [<IP_ADDRESS>:54997]...
Waiting for connection from host on [<IP_ADDRESS>:55421]...
PlayerConnection accepted from [<IP_ADDRESS>] handle:0x2c8
Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,defer=y,address=<IP_ADDRESS>:56270
PlayerConnection already initialized - listening to [<IP_ADDRESS>:55421]
Initialize engine version: 5.3.1f1 (cc9cbbcc37b4)
GfxDevice: creating device client; threaded=1
Direct3D:
    Version:  Direct3D 11.0 [level 11.0]
    Renderer: AMD Radeon HD 5800 Series (ID=0x689e)
    Vendor:   ATI
    VRAM:     2023 MB
Begin MonoManager ReloadAssembly
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.dll into Unity Child Domain
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\Assembly-CSharp.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\Assembly-CSharp.dll into Unity Child Domain
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.UI.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.UI.dll into Unity Child Domain
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.Networking.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.Networking.dll into Unity Child Domain
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\SQLite4Unity3d.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\SQLite4Unity3d.dll into Unity Child Domain
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.Networking.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.Networking.dll into Unity Child Domain
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.UI.dll (this message is harmless)
Loading E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\UnityEngine.UI.dll into Unity Child Domain
- Completed reload, in  0.268 seconds
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\System.Core.dll (this message is harmless)
Platform assembly: E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Build\test2\test2_Data\Managed\System.dll (this message is harmless)
desktop: 1920x1080 60Hz; virtual: 3840x1080 at 0,0
<RI> Initializing input.

<RI.Hid> Failed to create device file:
 2 The system cannot find the file specified.

(Filename: C:/buildslave/unity/build/PlatformDependent/Win/RawInput.cpp Line: 54)

<RI> Input initialized.

<RI> Initialized touch support.

UnloadTime: 1.290177 ms
Final PATH: C:/Users/BigDaddy/AppData/LocalLow/DefaultCompany/Example_unity5/existing.db
UnityEngine.DebugLogHandler:Internal_Log(LogType, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:Log(Object)
DataService:.ctor(String) (at E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Assets\Scripts\DataService.cs:53)
ExistingDBScript:Start() (at E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Assets\Scripts\ExistingDBScript.cs:11)

(Filename: E:/@Documents/Unity Repos/SQLite4Unity3d/Example_unity5/Assets/Scripts/DataService.cs Line: 53)

SQLiteException: no such table: Person
  at SQLite4Unity3d.SQLite3.Prepare2 (IntPtr db, System.String query) [0x00000] in <filename unknown>:0
  at SQLite4Unity3d.SQLiteCommand.Prepare () [0x00000] in <filename unknown>:0
  at SQLite4Unity3d.SQLiteCommand+<ExecuteDeferredQuery>d__0`1[Person].MoveNext () [0x00000] in <filename unknown>:0
  at System.Collections.Generic.List`1[Person].AddEnumerable (IEnumerable`1 enumerable) [0x0001a] in /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/List.cs:128
  at System.Collections.Generic.List`1[Person]..ctor (IEnumerable`1 collection) [0x00025] in /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/List.cs:65
  at System.Linq.Enumerable.ToList[Person] (IEnumerable`1 source) [0x00000] in <filename unknown>:0
  at SQLite4Unity3d.SQLiteCommand.ExecuteQuery[Person] () [0x00000] in <filename unknown>:0
  at SQLite4Unity3d.TableQuery`1[Person].GetEnumerator () [0x00000] in <filename unknown>:0
  at ExistingDBScript.ToConsole (IEnumerable`1 people) [0x00000] in E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Assets\Scripts\ExistingDBScript.cs:28
  at ExistingDBScript.Start () [0x00012] in E:\@Documents\Unity Repos\SQLite4Unity3d\Example_unity5\Assets\Scripts\ExistingDBScript.cs:14

(Filename: /Users/builduser/buildslave/mono-runtime-and-classlibs/build/mcs/class/corlib/System.Collections.Generic/List.cs Line: 128)

Setting up 1 worker threads for Enlighten.
  Thread -> id: 1f0 -> priority: 1
Waiting for finish

EDIT: I think I found the issue. File.Copy is to slow or not executing properly. I get a copy of the file in the persistentDataPath, but it is empty (0 bytes). Not exactly sure why that's happening, but I'll see if I can figure it out. If you have any ideas I'd love to hear it. Maybe there needs to be a callback for the file copy process.

Fixed it. You are using preprocessor directive UNITY_WINRT in DataServices.cs you could probably just switch that to #else
Cheers and thanks for the work on this!

Hi @Naphier I've just tested in a previous version and it works ok. I'm unable to reproduce it. I'll let you know when I've finished installing the latest version as I would like to understand the issue and fix it properly. ;D
Thanks for your feedback and investigation work! :smile:

Hi @Naphier, I'm unable to reproduce your issue... It just works... I'm using the latest version of Unity (5.3.1f) and Windows 10. I've kept the original code (no compilation directives modifed) and launched the app in x86 as per your attached picture.

Do you have more info on what really happened or how to reproduce it?

Strange. It has been 100% reproducible for me when the UNITY_WINRT directive is there. I change it to a simple #else and it works just fine. Unity's documentation says UNITY_WINRT == UNITY_WP8 | UNITY_WSA, that's Windows Phone 8 or Windows Store, so it would make sense that the directive is ignored in a standalone build. Seems really odd that it does work for you.
At any rate, I've found what works for me.
I appreciate the quick response though.
Thanks!

No problem, just in case I will add and #else there and problem solved ;D


Document how to bind Docker build, tag & push to Maven phases

And how to skip Docker build & tag when these goals are bound to Maven phases.
Related to issues:

https://github.com/spotify/docker-maven-plugin/issues/203
https://github.com/spotify/docker-maven-plugin/issues/174
https://github.com/spotify/docker-maven-plugin/issues/187

Awesome, thanks so much.


Evaluate if we should add Sorbet

Evaluated the advantages and disadvantages to add Sorbet to the ruby-lsp, so that we can decide on whether we want to do it or not.
If the decision is to add Sorbet, add it using our default tooling.

Awesome, thank you!

Let's close this since we already decided to add it: https://github.com/Shopify/ruby-lsp/pull/119.


[KeePassXC] Add PIN to use extension

Extension
https://www.raycast.com/zkytech/keepassxc
Description
Current behavior:
Once you have entered the KeePass password and key file, anyone with access to the computer can access all the passwords in the database. This is potentially insecure - particularly on laptops, which could be used in public areas.
Suggested feature:
Add an option to add a PIN, which would be required to access the database.
Who will benefit from this feature?
Users who are concerned about unauthorized access to the database.
Anything else?
No response

Hello,
It sounds a nice idea. @zkytech is the owner of the extension. I don’t know what he would think about it.


fix!: import.meta not supported, drop support of Node<14

#4 Change esbuild target to es2020 and add a notation on README.

Great, thanks!

Great, thanks!

Forcing Node >= 14 will limit the cloud hosting services that can support Vite.
I was considering using Vite for a project but this will kill it.

Forcing Node >= 14 will limit the cloud hosting services that can support Vite.
I was considering using Vite for a project but this will kill it.

Don't know there is anything we can do here. If you found a way to make it work for v12 or v10, would you mind drafting a PR for it? Thanks.

Don't know there is anything we can do here. If you found a way to make it work for v12 or v10, would you mind drafting a PR for it? Thanks.

I had an issue with that engine limitation. I don't know is that fix still applies to latest vite version or not.
While deploying an app to Netlify build has failed because of that.
I bypassed engine check setting that env variable on Netlify console and had no issue while deploying. But my app was just a single page app and doesn't even import any deps.


[BUG] Can't configure uri to cosmos mongo db using:  mongodb://username:password@host:10255/database?ssl=true

Describe the bug
When I'm configuring my cosmos db connection like this:
azure:
  cosmos:
    uri: mongodb://username:password@host:port/database?ssl=true
    key: primary-key
    secondaryKey: secondary-key
    database: database

Please note, that port in this case: 10255
as advised in this tutorial: https://docs.microsoft.com/en-us/azure/cosmos-db/connect-mongodb-account#get-the-mongodb-connection-string-by-using-the-quick-start
Exception or Stack Trace
Caused by: java.lang.RuntimeException: Client initialization failed. Check if the endpoint is reachable and if your auth token is valid
	at com.azure.cosmos.implementation.RxDocumentClientImpl.initializeGatewayConfigurationReader(RxDocumentClientImpl.java:388)
	at com.azure.cosmos.implementation.RxDocumentClientImpl.init(RxDocumentClientImpl.java:415)
	at com.azure.cosmos.implementation.AsyncDocumentClient$Builder.build(AsyncDocumentClient.java:241)
	at com.azure.cosmos.CosmosAsyncClient.<init>(CosmosAsyncClient.java:123)
	at com.azure.cosmos.CosmosClientBuilder.buildAsyncClient(CosmosClientBuilder.java:741)
	at com.azure.spring.data.cosmos.CosmosFactory.createCosmosAsyncClient(CosmosFactory.java:70)
	at com.azure.spring.data.cosmos.config.AbstractCosmosConfiguration.cosmosAsyncClient(AbstractCosmosConfiguration.java:57)
	at com.lendico.kycservice.config.AzureCosmosDbConfig$$EnhancerBySpringCGLIB$$5810af8c.CGLIB$cosmosAsyncClient$3(<generated>)
	at com.lendico.kycservice.config.AzureCosmosDbConfig$$EnhancerBySpringCGLIB$$5810af8c$$FastClassBySpringCGLIB$$31264ac5.invoke(<generated>)
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244)
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
	at com.lendico.kycservice.config.AzureCosmosDbConfig$$EnhancerBySpringCGLIB$$5810af8c.cosmosAsyncClient(<generated>)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
	... 155 more

To Reproduce
Use configuration like (in application.yaml):
azure:
  cosmos:
    uri: mongodb://username:password@host:10255/database?ssl=true
    key: primary-key
    secondaryKey: secondary-key
    database: database

Code Snippet
Add the code snippet that causes the issue.
Expected behavior
I would expect that I still can connect to cosmos db, no matter how I configured url
Two possible options are:

working

azure:
  cosmos:
    uri: https://host:443/
    key: primary-key
    secondaryKey: secondary-key
    database: database

not working

azure:
  cosmos:
    uri: mongodb://username:password@host:10255/database?ssl=true
    key: primary-key
    secondaryKey: secondary-key
    database: database

Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: MacOS Catalina
IDE: Eclipse
Library/Libraries:

	<dependency>
           <groupId>com.azure.spring</groupId>
           <artifactId>azure-spring-boot-starter-cosmos</artifactId>
           <version>3.4.0</version>
       </dependency>

Additional context
I believe that I can see where the problem is (but obviously not 100% sure)
com.azure.cosmos.implementation.RxGatewayStoreModel ->  private URI getUri(RxDocumentServiceRequest request) throws URISyntaxException
when uri is created:
    return new URI("https",
            null,
            rootUri.getHost(),
            rootUri.getPort(),
            ensureSlashPrefixed(path),
            null,  // Query string not used.
            null);

You use https, and if I'm not mistaken - https would require port 443, but in this instance you're retrieving it from root uri which looks like:
mongodb://username:password@host:10255/database?ssl=true

and where port passed is 10255
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ ] Bug Description Added
[ ] Repro Steps Added
[ ] Setup information Added

Hi @kushagraThapar, as azure-spring-boot-starter-cosmos depend on azure-cosmos, does azure-cosmos support endpoint like "mongodb://username:password@host:10255/database?ssl=true" ?

@xytrams azure-spring-boot-starter-cosmos support cosmos sql only, if you want to interact with mongo , you can use spring data MongoDB.
https://spring.io/projects/spring-data-mongodb

to reduce such misunderstanding, we may add some uri schema check and throw a more readable exception if there is any unsupported protocol provided in the azure-cosmos


add triggers on listener creation

Wrote some pretty simple code to check functionality, looks like the moment add listener is instantiated, it triggers the add event if file is already there (file was copied to path before code was run). Is this a feature?
var chokidar = require('chokidar');

var testJson = '/path/to/file.json';

  // Initialize watcher.
  var watcher = chokidar.watch(testJson, {
    ignored: /[\/\\]\./,
    persistent: true,
  });

  watcher
    .on('add', console.log);

  var watchedPaths = watcher.getWatched();

Yes. If you don't want those events then use the ignoreInitial: true option.

Thanks for quick reply.


Add explicit advice on avoiding concurrency issues for Android tracker

Add explicit advice on avoiding concurrency issues for Android tracker
The iOS docs make it explicit that only one Tracker should exist at once, I believe the case is the same for Android - the docs should make this explicit.
https://github.com/snowplow/snowplow/wiki/Android-Tracker#5-sending-event-emitter

migrated to https://github.com/snowplow/snowplow-android-tracker/issues/297


setItemIndex method not working with navigator inside "open" event

I have tried setting index of of an item, but I'm getting error all the time
viewer.world.setItemIndex(item, 8);
item is the tile image and current index is 5. Want to move to 8th index.
Error : [World.setItemIndex] item is required
While looking through the library file, setItemIndex method keeps looping with item-index-change event. After commenting the below statement, viewer.world data is getting updated. Please advice what's wrong with code.
Commented  section:
this.raiseEvent( 'item-index-change', {
            item: item,
            previousIndex: oldIndex,
            newIndex: index
        } );

Interesting. One thing to try: do you have the navigator on? What if you turn it off (and uncomment that code)?
Other than that, would it be possible for you to share a link to your project, or a codepen that reproduces your issue?

It seems working on turning off the navigator. In our case, we need navigator as per our requirement.
Also there is an another issue in  setItemIndex method. Index is setting properly, but positions aren't changing. In the code it's just using splice method to change the index of the items and positions are not being affected as it's not changing. I'll create another issue for this.

this._items.splice( oldIndex, 1 );
this._items.splice( index, 0, item );

Looks like it's a timing issue. Are you doing the setItemIndex in your open handler? If so, it looks like the navigator isn't yet set up by then. Looks like just adding a setTimeout of 1 is enough to fix it. We could do something like that here:
https://github.com/openseadragon/openseadragon/blob/master/src/navigator.js#L234
Would you be up for making a patch for this?

Fixed by #1201


Shutdown hook in parquet-avro library corrupts data and disables logging

Parquet-avro and probably also other Parquet libraries are not well behaved. It registers a shutdown hook that bypasses application shutdown sequence, corrupts data written to currently opened Parquet file(s) and disables or reconfigures slf4j/logback logger so no further log message is visible.
Scope
Our application is a microservice that handles stop request in form of signal SIGTERM, resp. JVM shutdown hook. If it arrives the application will close all opened files (writers), release all other resources and gracefully shutdown. We are swiching from sequence files to Parquet at the moment and using Maven dependency org.apache.parquet:parquet-avro:1.8.1 which is current latest version. We are using Runtime.getRuntime().addShutdownHook() to handle SIGTERM.
Example code
See archive in attachment.

Optionally update version of hadoop-client in pom.xml to match your Hadoop.
Use mvn package to compile.
Copy Hadoop configuration XMLs to config directory.
Update configuration at the top of ParquetBrokenShutdown class.
Execute ParquetBrokenShutdown class.
Send SIGTERM to shutdown the application (kill PID).

Initial analysis
Parquet library tries to care about application shutdown but this introduces more issues than solves. If application is writing to a file and the library asynchronously decides to close underlying writer, data loss will occur. The handle is just closed and all remaining records can't be written.
Writing to HDFS/Parquet failed
java.io.IOException: can not write PageHeader(type:DICTIONARY_PAGE, uncompressed_page_size:14, compressed_page_size:34, dictionary_page_header:DictionaryPageHeader(num_values:1, encoding:PLAIN))
	at org.apache.parquet.format.Util.write(Util.java:224)
	at org.apache.parquet.format.Util.writePageHeader(Util.java:61)
	at org.apache.parquet.format.converter.ParquetMetadataConverter.writeDictionaryPageHeader(ParquetMetadataConverter.java:760)
	at org.apache.parquet.hadoop.ParquetFileWriter.writeDictionaryPage(ParquetFileWriter.java:307)
	at org.apache.parquet.hadoop.ColumnChunkPageWriteStore$ColumnChunkPageWriter.writeToFileWriter(ColumnChunkPageWriteStore.java:179)
	at org.apache.parquet.hadoop.ColumnChunkPageWriteStore.flushToFileWriter(ColumnChunkPageWriteStore.java:238)
	at org.apache.parquet.hadoop.InternalParquetRecordWriter.flushRowGroupToStore(InternalParquetRecordWriter.java:165)
	at org.apache.parquet.hadoop.InternalParquetRecordWriter.close(InternalParquetRecordWriter.java:113)
	at org.apache.parquet.hadoop.ParquetWriter.close(ParquetWriter.java:297)
	at com.avast.bugreport.parquet.ParquetBrokenShutdown.writeParquetFile(ParquetBrokenShutdown.java:86)
	at com.avast.bugreport.parquet.ParquetBrokenShutdown.run(ParquetBrokenShutdown.java:53)
	at com.avast.bugreport.parquet.ParquetBrokenShutdown.main(ParquetBrokenShutdown.java:153)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: parquet.org.apache.thrift.transport.TTransportException: java.nio.channels.ClosedChannelException
	at parquet.org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:147)
	at parquet.org.apache.thrift.transport.TTransport.write(TTransport.java:105)
	at parquet.org.apache.thrift.protocol.TCompactProtocol.writeByteDirect(TCompactProtocol.java:424)
	at parquet.org.apache.thrift.protocol.TCompactProtocol.writeByteDirect(TCompactProtocol.java:431)
	at parquet.org.apache.thrift.protocol.TCompactProtocol.writeFieldBeginInternal(TCompactProtocol.java:194)
	at parquet.org.apache.thrift.protocol.TCompactProtocol.writeFieldBegin(TCompactProtocol.java:176)
	at org.apache.parquet.format.InterningProtocol.writeFieldBegin(InterningProtocol.java:74)
	at org.apache.parquet.format.PageHeader.write(PageHeader.java:918)
	at org.apache.parquet.format.Util.write(Util.java:222)
	... 16 more
Caused by: java.nio.channels.ClosedChannelException
	at org.apache.hadoop.hdfs.DFSOutputStream.checkClosed(DFSOutputStream.java:1635)
	at org.apache.hadoop.fs.FSOutputSummer.write(FSOutputSummer.java:104)
	at org.apache.hadoop.fs.FSDataOutputStream$PositionCache.write(FSDataOutputStream.java:58)
	at java.io.DataOutputStream.write(DataOutputStream.java:107)
	at parquet.org.apache.thrift.transport.TIOStreamTransport.write(TIOStreamTransport.java:145)
	... 24 more

Stored file is also currupted in such case. It contains only four bytes "PAR1" header so actually all data are lost.
Together with that whole application logging using slf4j/logback is reconfigured or completely disabled so no more application's log messages appear in the output. This may be related to PARQUET-369 and will be hopefully fixed in PARQUET-401. No such issue was observed when sequence files were used in the past.
Known workaround
Java executes threads of shutdown hooks independently and in parallel, but it is possible for the application to force its own shutdown to be executed before the Parquet's one. Parquet library uses Hadoop's ShutdownHookManager to register the hook which has a possibility to define a priority.
if (!USE_WORKAROUND) {
	Runtime.getRuntime().addShutdownHook(shutdownHook);
} else {
	int maxPriority = Integer.MAX_VALUE; // Execute application hook before hook in Hadoop library
	ShutdownHookManager.get().addShutdownHook(shutdownHook, maxPriority);
}

This workaround would be impossible if there are two or more such nasty libraries.
No workaround has been found for the second issue with disabled logging until now.
Suggestions for fix

Never touch logging configuration in libraries.

Use slf4j-api interfaces and just output log messages.
Application is responsible for configuration of logging.

Do not register any shutdown hook in libraries that releases resources that are still possibly in use.

Instead provide an API to the application to close/free the allocated resources (already present).
The application is responsible to call close on all Closeables during shutdown in correct order and correct time.
No library has enough information for that.

Be well behaved library, do not try to be smarter than the application, it isn't possible.

Reporter: Michal Turek / @mixalturek
Assignee: Michal Turek / @mixalturek
Related issues:

Shading SLF4J prevents SLF4J locating org.slf4j.impl.StaticLoggerBinder (is related to)
Deprecate Log and move to SLF4J Logger (requires)
Format: Do not shade slf4j-api (requires)

Original Issue Attachments:

parquet-broken-shutdown_2015-12-16.tar.gz

Note: This issue was originally created as PARQUET-408. Please see the migration documentation for further details.

Ryan Blue / @rdblue:
<EMAIL_ADDRESS>thank you for the very detailed report of what you're seeing. Bug reports like this are much easier to work with.
I'm not sure I'm convinced that this is a bug with Parquet. If I understand correctly, you're using a Java 7 try-with-resources block to instantiate the parquet-avro writer, which is calls close on that writer when it exits. That happens only when the thread is signaled via AtomicBoolean finished. Finished is set in your shutdown hook, so your when hook runs, it gracefully shuts down the writing thread, which closes the file. But the error you're seeing is from closing the Parquet file after the underlying file stream has been closed. Parquet doesn't have a shutdown hook that causes that, I think HDFS does.
I think the problem is that your hook gets called to shut down after the HDFS client closes all of its connections. That's solved by your work-around, which I think isn't a work around so much as the only way to do what you want to with HDFS. :)
Does that sound reasonable? I think the logging issues are unrelated, too.

Michal Turek / @mixalturek:
Hi Ryan, thank you for the very quick response and pointing to FileSystem class. I found configuration "fs.automatic.close" in its code, setting it to "false" solves the corruption of files too.
https://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/core-default.xml

By default, FileSystem instances are automatically closed at program exit using a JVM shutdown hook. Setting this property to false disables this behavior. This is an advanced option that should only be used by server applications requiring a more carefully orchestrated shutdown sequence.

I don't expect that the last closed Parquet writer will also close the underlying instance of FileSystem, on the other hand it is not accessible to the application code at all. Should I call static FileSystem.closeAll() by myself? It's pretty undocumented and looks like broken by design in Hadoop... or I missed something again.
Why do you think the logging issues are unrelated? Parquet library disables application logging for no reason, it looks like very related for me. I have updated the example to support also sequence files to show you differences (parquet-broken-shutdown_2015-12-17.tar.gz).
While using sequence files I see:
...
2015-12-17 13:09:30.249 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:136)
2015-12-17 13:09:31.250 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:136)
Logging test: stopping application
2015-12-17 13:09:31.913 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: =============== STOPPING APPLICATION =============== (ParquetBrokenShutdown.java:176)
2015-12-17 13:09:31.913 TRACE c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: stopping application (ParquetBrokenShutdown.java:177)
2015-12-17 13:09:31.913 DEBUG c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: stopping application (ParquetBrokenShutdown.java:178)
2015-12-17 13:09:31.913 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: stopping application (ParquetBrokenShutdown.java:179)
2015-12-17 13:09:31.913 WARN  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: stopping application (ParquetBrokenShutdown.java:180)
2015-12-17 13:09:31.913 ERROR c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: stopping application (ParquetBrokenShutdown.java:181)
2015-12-17 13:09:31.913 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Closing instance (ParquetBrokenShutdown.java:61)
2015-12-17 13:09:32.251 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Closing sequence file: hdfs://nameservice1/user/turek/bugreport.seq (ParquetBrokenShutdown.java:141)
2015-12-17 13:09:32.425 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Sequence file closed: hdfs://nameservice1/user/turek/bugreport.seq (ParquetBrokenShutdown.java:144)
2015-12-17 13:09:32.425 INFO  c.a.b.parquet.ParquetBrokenShutdown [main]: =============== APPLICATION FINISHED =============== (ParquetBrokenShutdown.java:176)
2015-12-17 13:09:32.425 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application finished (ParquetBrokenShutdown.java:177)
2015-12-17 13:09:32.426 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application finished (ParquetBrokenShutdown.java:178)
2015-12-17 13:09:32.426 INFO  c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application finished (ParquetBrokenShutdown.java:179)
2015-12-17 13:09:32.426 WARN  c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application finished (ParquetBrokenShutdown.java:180)
2015-12-17 13:09:32.426 ERROR c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application finished (ParquetBrokenShutdown.java:181)
Logging test: application finished
2015-12-17 13:09:32.527 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: =============== SHUTDOWN HOOK FINISHED =============== (ParquetBrokenShutdown.java:176)
2015-12-17 13:09:32.528 TRACE c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: shutdown hook finished (ParquetBrokenShutdown.java:177)
2015-12-17 13:09:32.528 DEBUG c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: shutdown hook finished (ParquetBrokenShutdown.java:178)
2015-12-17 13:09:32.528 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: shutdown hook finished (ParquetBrokenShutdown.java:179)
2015-12-17 13:09:32.528 WARN  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: shutdown hook finished (ParquetBrokenShutdown.java:180)
2015-12-17 13:09:32.528 ERROR c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: Logging test: shutdown hook finished (ParquetBrokenShutdown.java:181)
Logging test: shutdown hook finished

But while using Parquet files and parquet-avro library I see only:
...
2015-12-17 13:10:36.909 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:110)
2015-12-17 13:10:37.910 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:110)
Logging test: stopping application
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Logging test: application finished
Logging test: shutdown hook finished

Ryan Blue / @rdblue:
After you're done closing Parquet files, I think you should call FileSystem.closeAll() since that is what the hook you've disabled would do.
I think your file corruption issue is now understood and the logging problem isn't causing it. That's what I mean when I say they are independent.
PARQUET-369 will only drop logs from thrift within parquet-format, and the only one I've seen is when close, not flush, fails. That didn't happen here because the exception wasn't caught, logged, and suppressed in thrift. It was correctly propagated up to your application. You can see in the stack trace that it went through TIOStreamTransport. You may be right that we should expose the logs with the trade-off of adding the dependency, which we are discussing on that issue.
I'm not sure what the problem you're seeing in this application is, but it looks like it is related to not configuring SLF4J. All of the log lines you list above that are missing are from your application, not from calls into Parquet.

Ryan Blue / @rdblue:
Thanks, Jim! I think that closes out what we needed to explain here. We'll follow up on the Parquet logging changes in PARQUET-412 and I'll close this issue. Feel free to re-open if I missed something.

Michal Turek / @mixalturek:
Ok, I was debugging for a while and finally found what is happening. Logging is not disabled on shutdown at all but shutdown hook of java.util.logging corrupts stdout stream. Messages that go to System.out using ConsoleAppender are not written, because the stream is closed. On the other hand messages that go to a file using RollingFileAppender are correctly there.
Bellow is a detailed analysis if anyone is interested. Note there is a workaround at the very end.
Effective logback.xml:
<?xml version="1.0" encoding="UTF-8" ?>
<configuration scan="true" scanPeriod="30 seconds">
    <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
        <encoder>
            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %-35logger{35} [%thread]: %msg \(%file:%line\)%n%xThrowable{full}</pattern>
        </encoder>
    </appender>

    <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <file>test.log</file>

        <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
            <fileNamePattern>test.log.%d{yyyy-MM-dd}_%i.gz</fileNamePattern>
            <maxHistory>30</maxHistory>
            <timeBasedFileNamingAndTriggeringPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP">
                <maxFileSize>250MB</maxFileSize>
            </timeBasedFileNamingAndTriggeringPolicy>
        </rollingPolicy>

        <encoder>
            <pattern>%d{yyyy-MM-dd HH:mm:ss.SSS} %-5level %-45logger{45} [%thread]: %msg%n%xThrowable{full}</pattern>
        </encoder>
    </appender>

    <root level="INFO">
        <appender-ref ref="STDOUT"/>
        <appender-ref ref="FILE"/>
    </root>

    <logger name="com.avast.bugreport" level="TRACE"/>
</configuration>

Output on console or in JIdea IDE:
Logging test: starting application
Logging test: application started
2016-02-16 12:39:58.922 INFO  c.a.b.parquet.ParquetBrokenShutdown [main]: =============== STARTING APPLICATION =============== (ParquetBrokenShutdown.java:177)
2016-02-16 12:39:58.928 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: starting application (ParquetBrokenShutdown.java:178)
2016-02-16 12:39:58.928 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: starting application (ParquetBrokenShutdown.java:179)
2016-02-16 12:39:58.928 INFO  c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: starting application (ParquetBrokenShutdown.java:180)
2016-02-16 12:39:58.928 WARN  c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: starting application (ParquetBrokenShutdown.java:181)
2016-02-16 12:39:58.928 ERROR c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: starting application (ParquetBrokenShutdown.java:182)
2016-02-16 12:39:58.929 INFO  c.a.b.parquet.ParquetBrokenShutdown [main]: =============== APPLICATION STARTED =============== (ParquetBrokenShutdown.java:177)
2016-02-16 12:39:58.930 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application started (ParquetBrokenShutdown.java:178)
2016-02-16 12:39:58.930 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application started (ParquetBrokenShutdown.java:179)
2016-02-16 12:39:58.930 INFO  c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application started (ParquetBrokenShutdown.java:180)
2016-02-16 12:39:58.930 WARN  c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application started (ParquetBrokenShutdown.java:181)
2016-02-16 12:39:58.931 ERROR c.a.b.parquet.ParquetBrokenShutdown [main]: Logging test: application started (ParquetBrokenShutdown.java:182)
2016-02-16 12:39:59.188 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Opening Parquet file: hdfs://nameservice1/user/turek/bugreport.parquet (ParquetBrokenShutdown.java:95)
2016-02-16 12:39:59.335 WARN  o.a.hadoop.util.NativeCodeLoader    [main]: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable (NativeCodeLoader.java:62)
2016-02-16 12:40:00.228 INFO  o.a.hadoop.io.compress.CodecPool    [main]: Got brand-new compressor [.gz] (CodecPool.java:151)
2016-02-16 12:40:00.295 DEBUG c.a.b.parquet.ParquetBrokenShutdown [main]: Parquet file opened: hdfs://nameservice1/user/turek/bugreport.parquet (ParquetBrokenShutdown.java:105)
2016-02-16 12:40:00.297 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:111)
2016-02-16 12:40:01.299 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:111)
2016-02-16 12:40:02.299 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:111)
2016-02-16 12:40:03.301 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:111)
2016-02-16 12:40:03.585 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: =============== STOPPING APPLICATION =============== (ParquetBrokenShutdown.java:177)
Logging test: stopping application
Logging test: application finished
Logging test: shutdown hook finished

Process finished with exit code 143

Output in test.log file:
2016-02-16 12:39:58.922 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: =============== STARTING APPLICATION ===============
2016-02-16 12:39:58.928 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: starting application
2016-02-16 12:39:58.928 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: starting application
2016-02-16 12:39:58.928 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: starting application
2016-02-16 12:39:58.928 WARN  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: starting application
2016-02-16 12:39:58.928 ERROR c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: starting application
2016-02-16 12:39:58.929 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: =============== APPLICATION STARTED ===============
2016-02-16 12:39:58.930 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application started
2016-02-16 12:39:58.930 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application started
2016-02-16 12:39:58.930 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application started
2016-02-16 12:39:58.930 WARN  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application started
2016-02-16 12:39:58.931 ERROR c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application started
2016-02-16 12:39:59.188 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Opening Parquet file: hdfs://nameservice1/user/turek/bugreport.parquet
2016-02-16 12:39:59.335 WARN  org.apache.hadoop.util.NativeCodeLoader       [main]: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2016-02-16 12:40:00.228 INFO  org.apache.hadoop.io.compress.CodecPool       [main]: Got brand-new compressor [.gz]
2016-02-16 12:40:00.295 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Parquet file opened: hdfs://nameservice1/user/turek/bugreport.parquet
2016-02-16 12:40:00.297 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Writing record: {"test": "test value"}
2016-02-16 12:40:01.299 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Writing record: {"test": "test value"}
2016-02-16 12:40:02.299 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Writing record: {"test": "test value"}
2016-02-16 12:40:03.301 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Writing record: {"test": "test value"}
2016-02-16 12:40:03.585 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: =============== STOPPING APPLICATION ===============
2016-02-16 12:40:03.585 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: stopping application
2016-02-16 12:40:03.585 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: stopping application
2016-02-16 12:40:03.585 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: stopping application
2016-02-16 12:40:03.585 WARN  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: stopping application
2016-02-16 12:40:03.586 ERROR c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: stopping application
2016-02-16 12:40:03.586 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Closing instance
2016-02-16 12:40:04.302 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Closing Parquet file: hdfs://nameservice1/user/turek/bugreport.parquet
2016-02-16 12:40:04.514 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Parquet file closed: hdfs://nameservice1/user/turek/bugreport.parquet
2016-02-16 12:40:04.514 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: =============== APPLICATION FINISHED ===============
2016-02-16 12:40:04.514 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application finished
2016-02-16 12:40:04.514 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application finished
2016-02-16 12:40:04.515 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application finished
2016-02-16 12:40:04.515 WARN  c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application finished
2016-02-16 12:40:04.515 ERROR c.a.bugreport.parquet.ParquetBrokenShutdown   [main]: Logging test: application finished
2016-02-16 12:40:04.616 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: =============== SHUTDOWN HOOK FINISHED ===============
2016-02-16 12:40:04.616 TRACE c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: shutdown hook finished
2016-02-16 12:40:04.616 DEBUG c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: shutdown hook finished
2016-02-16 12:40:04.616 INFO  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: shutdown hook finished
2016-02-16 12:40:04.616 WARN  c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: shutdown hook finished
2016-02-16 12:40:04.617 ERROR c.a.bugreport.parquet.ParquetBrokenShutdown   [Thread-0]: Logging test: shutdown hook finished

So somebody either manipulates console appender or closes System.out stream.
    private static void loggingTest(String description) {
        LOGGER.info("=============== {} ===============", description.toUpperCase());
        LOGGER.trace("Logging test: " + description);
        LOGGER.debug("Logging test: " + description);
        LOGGER.info("Logging test: " + description);
        LOGGER.warn("Logging test: " + description);
        LOGGER.error("Logging test: " + description);
        System.out.println("Logging test: stdout, " + description);    // <<<<< ADDED
        System.err.println("Logging test: stderr, " + description);
    }

2016-02-16 13:14:22.497 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:111)
2016-02-16 13:14:23.498 TRACE c.a.b.parquet.ParquetBrokenShutdown [main]: Writing record: {"test": "test value"} (ParquetBrokenShutdown.java:111)
2016-02-16 13:14:23.726 INFO  c.a.b.parquet.ParquetBrokenShutdown [Thread-0]: =============== STOPPING APPLICATION =============== (ParquetBrokenShutdown.java:177)
Logging test: stderr, stopping application
Logging test: stderr, application finished
Logging test: stderr, shutdown hook finished

Process finished with exit code 143

So somebody closes System.out, nice! Put a breakpoint to java.io.PrintStream.close() and the winner is... java.util.logging, which is used internally in org.apache.parquet.Log.
"Thread-1@3141" prio=5 tid=0xe nid=NA runnable
  java.lang.Thread.State: RUNNABLE
	  at java.io.PrintStream.close(PrintStream.java:355)
	  at sun.nio.cs.StreamEncoder.implClose(StreamEncoder.java:320)
	  at sun.nio.cs.StreamEncoder.close(StreamEncoder.java:149)
	  - locked <0xc55> (a java.io.OutputStreamWriter)
	  at java.io.OutputStreamWriter.close(OutputStreamWriter.java:233)
	  at java.util.logging.StreamHandler.flushAndClose(StreamHandler.java:278)
	  - locked <0xc56> (a java.util.logging.StreamHandler)
	  at java.util.logging.StreamHandler.close(StreamHandler.java:302)
	  at java.util.logging.LogManager.resetLogger(LogManager.java:1346)
	  at java.util.logging.LogManager.reset(LogManager.java:1332)
	  at java.util.logging.LogManager$Cleaner.run(LogManager.java:239)

It seems workaround from here http://stackoverflow.com/a/13825590 works and can be used as a temporary fix in the application code.
public class Main {
    static {
        // must be called before any Logger method is used.
        System.setProperty("java.util.logging.manager", MyLogManager.class.getName());
    }

    public static class MyLogManager extends LogManager {
        static MyLogManager instance;
        public MyLogManager() { instance = this; }
        @Override public void reset() { /* don't reset yet. */ }
        private void reset0() { super.reset(); }
        public static void resetFinally() { instance.reset0(); }
    }

    public static void main(String... args) {
        // ...
    }
}

java.util.logging dependency is planned to be removed in PARQUET-401, which will be a final fix.

Michal Turek / @mixalturek:
I have just tried to add log4j.xml and log4j2.xml on classpath but it didn't help as expected.
http://coders-kitchen.com/2014/01/29/tip-disable-log4j-2s-shutdown-handler/
<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="WARN" monitoringInterval="30" shutdownHook="disable">
    <!-- Empty -->
</Configuration>

Adding import org.apache.logging.log4j.Logger; introduces a compiler error so I'm pretty sure, log4j2 is not the cause.
Can you update the attached sample code and make it functional to demonstrate your fix, please?

Michal Turek / @mixalturek:
Hi Jim, can you point to a related code snippet where log4j2 comes from? I can't find anything, where did you find it? Is it shadowed somewhere similarly to slf4j-api and slf4j-nop in parquet-format? Our project doesn't use it at all and there is no related JAR in dependencies. We use standard slf4j-api, various slf4j bridges and logback as logger implementation. It's also quite bad idea to configure logging of everything e.g. in logback.xml and have a second configuration file only due to one concrete library that is not well behaved. Am I the only one who see it? ;-)
find . -name '*log4j*'
./log4j-over-slf4j-1.7.14.jar

Jim Gawron:
Logging breaks in shutdown hooks because log4js own shutdown hook is being called in parallel with the others. This can be disabled via configuration in log4j2.

Michal Turek / @mixalturek:
I'm closing the issue, workaround is known and can be used in the applications and PARQUET-401 will introduce a final fix.


Bank tags sometimes does not remember last tag tab

Describe the bug
The bank interface is not remembering which tag tab I was last on. It just resets to the vanilla normal tab whenever I press esc or click the close button in the corner. Restarting the client seems to temporarily fix it, but it sporadically breaks again and multiple users are having this issue after the recent update.
To Reproduce
Steps to reproduce the behavior:

Open Bank
Select bank tag tab
Close Bank
Bank tag tab is not remembered

Expected behavior
Closing the bank interface while viewing a tag tab should display that tab when opening the interface again
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: Windows 10
RuneLite version: 1.5.29
Launcher version: 1.6.2

Additional context
Logs didn't seem to have information related but I will include them anyways
client.log

Is there anymore information on this? I can't reproduce this.

video replicating it, took like 5-10 minutes of being logged in and me teleporting to ge instead of crafting guild (not sure if that could be relevant) before it started happening, but now it doesn't stay open, toggling option in the plugin also temporarily fixes it for me, I'm not sure what's causing it to happen
https://youtu.be/IzbOB-3t4uQ
logs from today, my internet dced earlier today, but there's nothing I can see during this session that'd be an issue
client.log

My best guess is because of tick lag. There is some hoops we have to jump through for maintaining vanilla bank search. Thus a lot of logic is placed into onGameTick for determining current tab.

Why has this only recently become a problem?

It appears there are 2 different issues that can happen.

#9528 If you try and open a tag tab while not on bank tab 0.

#9406 If you close the bank and open it too fast. It appears the bank closes and opens on the same tick.


Value of key in secrets should be base64 encoded

In MSSQL scaler example in docs, The values for all keys in the data field in secrets should be base64-encoded. But  it mentioned as a string as shown below:
apiVersion: v1
kind: Secret
metadata:
  name: mssql-secrets
type: Opaque
data:
  mssql-connection-string: "Server=example.database.windows.net;port=1433;Database=AdventureWorks;Persist Security Info=False;User ID=user1;Password=Password#1;Encrypt=True;TrustServerCertificate=False;"

we used stringData field if we want to mention string value. but for uniformity of the docs we should mentioned  base64 encoded value.

Hi @tomkerkhove @zroubalik
could you please take a look!

Fixed it here #436


[Game Crash] Sending any MIDI Input while transitioning between Screens crashes the game

1. What you were doing before it crashed and what action made the game to crash.
In every screen, whenever i'd be transitioning from a screen to another and i'd send any MIDI signal from my Hercules DJControl Inpulse 200, the game would crash with an Access Violation reason.
This also happens with default Soundwaves theme, as well as SL-Outfox.
2. Upload the crashinfo.txt (GameFolder/crashinfo.txt)
crashinfo.txt
3. Upload the info.txt and log.txt (GameFolder/Logs)
log.txt
info.txt
Explain how we can reproduce the error

Start the game
Send any midi input (i.e. turn knobs on a console)
2a. While doing this, transition to another screen (i.e. press start)
Game crashed

If there's any information that you think would help us.
I happened to have the PC output set to the console, but that wasn't enough to not make it crash as it would still do that with another output set before launching the game.
I also tried replicating the crash in the MidiTest2.exe build Jous gave me the 18th and it did.

Fixed in 4.9.9 - we only need to adjust screenselect music now, but the major bug this was upset with is solved.


Need support for OR constraints in path queries

In updating the gene search API, I realized that we do not support OR constraints. The use case is that the user enters a string which is matched against either the Gene.primaryIdentifier or the Gene.name, which sometimes is totally different from the primaryIdentifier.
Example:

primaryIdentifier
name

glyma.Hwangkeum.gnm1.ann1.GmHk_13G038699
HSP70_11

The appropriate path query looks like this, with the constraintLogic and indentifying code attributes:
<query name="" model="genomic" view="Gene.primaryIdentifier Gene.name" longDescription="" sortOrder="Gene.primaryIdentifier asc" constraintLogic="A or B">
  <constraint path="Gene.primaryIdentifier" code="A" op="CONTAINS" value="HSP70_11"/>
  <constraint path="Gene.name" code="B" op="CONTAINS" value="HSP70_11"/>
</query>

@cann0010 and @adf-ncgr : an alternative would be to bail on the "name or identifier" search parameter and have separate name and identifier fields in the gene search UI. This might be confusing to people that have no idea what the difference is. But we can certainly do it that way in the near term.
This is in reference to intermine.server.ts:interminePathQuery.

Thanks @sammyjava- the example you gave is probably extreme ("totally different from the primaryIdentifier"), but does the same issue apply if we want one field that supports entering either primary or secondary identifier (ie full yuck or yuck-less id)- I am guessing that our saving grace in that case is that we can use CONTAINS. But I don't think we need to worry too much about "names" that aren't identifiers for the time being, since most Names (in gff) are just going to be secondary ids. Just my 2c, but probably if and when we start doing a better job of associating "biology names" with gene models I will reinvest.

I think adding an optional constraintLogic parameter to the interminePathQuery function you mentioned and then implementing logic on a per endpoint basis (e.g. searchGenes) would be sufficient. Note that the constraintLogic parameter would require adding an optional code parameter to the intermineConstraint function as well.

No, secondaryIdentifier is a substring of primaryIdentifier so it will always match a primaryIdentifier. I think this is only an "extreme case" because we're not providing gene names very often. Almost every Arabidopsis gene has a function-determined name (or symbol, if you will) different from ATnGnnnnn.
These both use CONTAINS. The problem is the OR to or-wise match two different fields. Right now I'm just coding a CONTAINS against primaryIdentifier and we can decide if we want to support the name field.
FWIW, here are the accessions for which name is NOT a substring of primaryIdentifier, typically because of extra Cajan. type prefixes.
       species         |  strain
-----------------------+--------------
 Cajanus cajan         | ICPL87119
 Cicer arietinum       | CDCFrontier
 Cicer arietinum       | ICC4958
 Glycine max           | Hwangkeum
 Lens culinaris        | CDC_Redberry
 Lupinus albus         | Amiga
 Lupinus angustifolius | Tanjil
 Medicago truncatula   | HM004
 Medicago truncatula   | HM010
 Medicago truncatula   | HM022
 Medicago truncatula   | HM023
 Medicago truncatula   | HM034
 Medicago truncatula   | HM050
 Medicago truncatula   | HM056
 Medicago truncatula   | HM058
 Medicago truncatula   | HM060
 Medicago truncatula   | HM095
 Medicago truncatula   | HM125
 Medicago truncatula   | HM129
 Medicago truncatula   | HM185
 Medicago truncatula   | HM324
 Medicago truncatula   | R108
 Trifolium pratense    | MilvusB
 Vigna unguiculata     | IT97K-499-35

I think adding an optional constraintLogic parameter to the interminePathQuery function you mentioned and then implementing logic on a per endpoint basis (e.g. searchGenes) would be sufficient. Note that the constraintLogic parameter would require adding an optional code parameter to the intermineConstraint function as well.

I think I'll pass on implementing that.

I am not sure I am following this correctly, but I wonder if the "identifier field" could be handled as a separate keyword search ... which could be used to find genes via their gene symbols (when available)? I expect it will be fairly common for a biologist to enter "LHY" or "Tfl1" or "Dt1" and hope to find genes in their selected species.

Thanks @cann0010 I agree this will be common but not sure we currently have the data to support getting good results. Try a keyword search in LegumeMine for any of those symbols and you will likely be dismayed. I think you have recently begun putting data that will be useful for this into https://github.com/legumeinfo/gene-function-registry so it will probably become more relevant soon. But I think the experiment of putting these symbols into the keyword search suggests that when the time comes we should make this a separate field than identifier (license plate gene naming tends to create a lot of false positives to gene symbols when "CONTAINS" is used)

Which is fine, and we can have rollovers providing examples to clarify that one field is for a license plate, the other is for a traditional gene symbol.

This was done when we added support for join queries; see PR #90. Closing.


window.webkitStorageInfo is deprecated and can be easily replaced

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
An audit on my uptime website, thrown this:
Deprecation / Warning | Source

'window.webkitStorageInfo' is deprecated. Please use 'navigator.webkitTemporaryStorage' or 'navigator.webkitPersistentStorage' instead. | …scripts/invisible.js:1:5162

2nd warning is :
URL | Map URL

/assets/vendor.66254805.js(uptime.achicrip.org) |
Large JavaScript file is missing a source map

👟 Reproduction steps
Run a web Page quality report, using https://web.dev/measure/ on your uptime-kuma site.
👀 Expected behavior
All API's should be bumped up to the latest version
😓 Actual Behavior
Recommendation is thrown
🐻 Uptime-Kuma Version
louislam/uptime-kuma            latest    957e1ceb8ac4   4 weeks ago    323MB
💻 Operating System and Arch
ubuntu Impish
🌐 Browser
Edge latest
🐋 Docker Version
Docker latest
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Doesn't seems to be a bug.
And this project do not use window.webkitStorageInfo, I believe that it is used by one of the libraries. If you find which libraries, just report to them.


ViteTagHelper cannot find chunk on Windows when not using ViteOptions.Base

Since #43 was merged, ViteTagHelper attempts to normalize script references to use the system's path separator. So with a script tag like this one:
<script type="module' vite-src="~/src/main.js"></script>

the ViteTagHelper normalizes the script reference to src\main.js when running on Windows, and then attempts to look up a chunk by that string.
If the app is not overriding ViteOptions.Base, then the chunk dictionary in ViteManifest is not updated to normalize the keys to use the same Windows path separator, so the entrypoint for src/main.js remains as-is and the key is stored in the dictionary with the forward slash. This means production builds on Windows cannot resolve assets from the manifest if they have a path separator in them.
I'd like to voluteer to fix this issue, if that's alright. I think it may make most sense to always use Unix-style path separators for the chunks, since that is what Vite will produce in the assets manifest regardless of platform. It also matches how script and link tags will be referencing the assets since URLs use the forward slash in that context too.

Fixed with v1.9.3. Thanks


Use role-focused configurations

https://docs.gradle.org/8.4/release-notes.html#easier-to-create-role-focused-configurations

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against 4784729d18f25eb694cf18229e43defe49589cf5

Side-effect: including the build from sources, now requires 8.4+.
Example failure: https://github.com/TWiStErRob/detekt-4165/actions/runs/6446917941/job/17502641358#step:5:33


windicss support webcomponents ?

// vite: 2.4.4
import WindiCSS from 'vite-plugin-windicss'

export default defineConfig({
    plugins: [
        WindiCSS(),
    ],
});

When I import 'virtual:windi.css'
// main.js
import 'virtual:windi.css'

It will insert <style type="text/css">/* windicss layer base */ in my head tag.
so It will fail to use in shadowDom

/cc @antfu probably something we would need to handle in vite-plugin


ci: add jammy sources for benches workflow

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Docs
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Checklist

[ ] This PR will resolve #___
[ ] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary
[ ] It can be built on all targets and pass CI/CD.

Other information

guess we are stuck with ubuntu 22.04 now


[SPARK-6078][CORE] create event log dir if not exists

when event log directory does not exists, spark just throw IlleagalArgumentException and stop the job. User need manually create directory first. It's better to create the directory automatically if the directory does not exists.

Test build #28120 has started for   PR 4829 at commit e76a1b4.

This patch merges cleanly.

This looks like a duplicate of #4120 / https://issues.apache.org/jira/browse/SPARK-5311, which we marked as "Won't Fix": https://github.com/apache/spark/pull/4120#issuecomment-72954989

If we do decide to create directories, then we should only create the last missing directory, not all missing parent directories.

Hi @JoshRosen, it's duplicate with  https://issues.apache.org/jira/browse/SPARK-5311, now that it won't fix, should I also close this PR?
But it is really not user friendly to manually create directory if user wants to put file in a new directory.

@srowen @vanzin @andrewor14, what are your thoughts on the usability / security trade-offs here?

Test build #28120 has finished for   PR 4829 at commit e76a1b4.

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

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

FWIW I think the reasoning at https://github.com/apache/spark/pull/4120#issuecomment-72954989 still stands and so we should also close this PR + JIRA as a duplicate.

Yes, we purposefully removed this feature. @liyezhang556520 would you mind closing this?

sure, I'll close this PR then, thanks for your review @JoshRosen, @srowen  @andrewor14


Enable web extension static theme upload.

@darktrojan Can you double check that this makes sense. It removes static theme support from Firefox, adds it to Thunderbird, adds appropriate categories, and makes the uploader reject xpis with no guid since we don't use signing, those won't installl.
Attached are a couple test themes if you need them.
test_xpis.zip

Are you planning to add tests?

Are you planning to add tests?

It would just be changing existing tests, but short answer is no, long answer:
Our tests don't really work because of all the swaps of TB -> Firefox app IDs and things we've made, and even getting a local installation working properly is a challenge, darktrojan has difficulty with it every time, and I don't even do local dev, I just do my dev on staging.
The docker compose stuff pulls several custom docker images from mozilla docker hub and those have been updated for newer versions, so we don't have access to the old ones anymore, and that has probably caused problems. The whole docker compose local setup is rather fragile in general, imo. So many moving parts just to run a local dev server.
I never planned to be making significant changes to the code, in all honesty. I would like to get all that resolved, but it's at least 2 weeks of work on just cleaning up technical debt. This is compounded by the fact that I don't work on addons-server code directly often enough to develop a good understanding of it. It really demands a dedicated dev, but we don't have that.