RFC Replace Zend_Locale with new i18n backend

See https://github.com/silverstripe/silverstripe-framework/issues/5359
dev list post: https://groups.google.com/forum/#!topic/silverstripe-dev/BVgFrxb7ISw
Introduction
Currently SilverStripe framework relies on Zend framework v1 for several core localisation features. This includes the below Zend components:

Zend_Locale

Text direction
Geographic information
Numeric formatting
Date formatting

Zend_Currency

Currency formatting

Zend_Date

Date formatting

The libraries these features are built on top of are several years out of date and require upgrading.
Exclusions
Note that the following other zend components remain a dependency of other parts of the CMS and are not covered by this RFC, even if these may be affected by the outcome of the decided direction.

Zend_Translate Moved to https://github.com/silverstripe/silverstripe-framework/issues/6221
Zend_Cache
Zend_Loader (only exists as a dependency of the prior Zend components)

Solution Requirements:
The chosen solution will need to either provide the below functionality, or have added on top of the core library to meet the necessary functionality:

Support for mi_NZ locale
Date formatting
Numeric formatting
Currency formatting

PHP INTL Dependency
Many modern i18n Solutions require the php intl library. Currently SilverStripe does not, although evading this as a requirement in future releases will limit our options.
Symfony currently provides a polyfill for intl https://github.com/symfony/polyfill.
Our options are:

Choose a solution that does rely on php-intl and require it as a core dependency
Choose a solution that does rely on php-intl, but rely on a polyfill
Choose a solution that does not rely on php-intl
Require php-intl to be installed to support i18n, but allow i18n to be disabled.

Investigation of symfony's polyfill implementation seems extremely incomplete, or implemented at a very shallow level only. E.g. stubs containing MethodNotImplementedException and hard-coded support for en locale only. Supporting or offering an incomplete solution in my mind is worse than no solution at all.
I recommend option 4, as it allows us to build a full i18n backend that will operate with all necessary features, but provides room for the community to develop a custom backend (or backends) to support environments without php-intl.
Example i18n Options:
Given that there are a huge number of possible i18n solution libraries, below is a non-exhaustive list of examples of solutions that could be considered.
1. Write i18n wrapper over php-intl
If we rely on php-intl, we could simplify the current i18n class into a wrapper over this extension. This solution would be the most work and be the hardest to maintain, but would allow us to minimise our dependencies.
Separate components would need to be built for string / number manipulation, as well as message translations, with the bulk of the work in implementing a translation mechanism which is compatible with our current yml translation system.
Dependencies:

php-intl

2. Zf2-i18n
Currently at version 2.7, which is also the current version for this component in the current zend-framework 3.0. The good news is that this implies the 2.x branch of this module will be supported within the immediate future.
This is probably the least disruptive upgrade as zendframework/zend-i18n replaces Zend_Translate API. This provides standard formatters for Currency, Date, Number, and Pluralisation.
Documentation at:

https://docs.zendframework.com/tutorials/i18n/
https://framework.zend.com/manual/2.4/en/modules/zend.i18n.translating.html

Dependencies: (1.5mb)

php-intl
zendframework/zend-i18n
zendframework/zend-eventmanager
zendframework/zend-loader
zendframework/zend-view
zendframework/zend-stdlib

4. Cakephp intl
Mainly a message formatting library, but has some php-intl wrappers around date and number formatting. Documentation http://book.cakephp.org/3.0/en/core-libraries/internationalization-and-localization.html
Dependencies: (600k)

php-intl
cakephp/chronos
cakephp/i18n
cakephp/core
cakephp/utility
aura/intl
aura/installer-default

Conclusion
Based on the solution we choose to pursue, it appears that there may be as many as two separate components; One for message localisation, and another for formatting of strings / date / time / numbers.
The desired response to this RFC should be in the form of either suggestion of an unnamed solution, or support for one of the prior named solutions.
The desired outcome of this RFC will be a mutually agreed upon technical direction, and a next step to explore. This will include our desired response to php-intl as a requirement.
Related

Zend_Translate
Zend_Cache

Notes:

Investigate rtl / ltr language support

I think within the "Date formatting" requirements, we need to list a couple of sub-requirements:

ISO/CU format support (Zend default, php-intl IntlDateFormatter default, different from  PHP's date() and DateTime::format()). Used for Member.Locale preferences (and corresponding localised output). For example, two-digit months in ICU is MM, in date() it's m. So we can't easily fall back to date() here, unless we create a conversion layer similar to DateField::convert_iso_to_jquery_format)
Localised day and month names, both long and short (preconfigured so authors can select their language). Could use date_format()+set_locale())
Localised country/language lookups (dropdown in CMS author profile - we could extract that information from CLDR into our YAML files) We currently hardcode this to English via i18n::$all_locales
Preferred date format for locale (long/short). Might get away with that and just getting authors to choose from a few custom formats. See Zend_Locale_Format::getDateFormat() and Member->getCMSFields()
Script direction for a given locale (see i18n::get_script_direction())

And for message translation, any new solution we choose should also support the following new feature:

Define count-based plurals (some languages have more than one plural form), see parseMessage()

Write i18n wrapper over php-intl

I don't think there's much value in a full wrapper (the API surface is huge) - it's an extension supported by the PHP project itself, so creating an abstraction layer in order to minimise risk of third party deprecations seems overkill. In the short term, we should pass through existing i18n methods to php-intl, but deprecate those in favour of using php-intl directly (for date/number/currency formats).
But by adding another half a dozen methods to our existing i18n API (with some refactoring and dependency injection), we should be able to cover off the use cases listed above. The problem is removing reliance on ISO date formats - we'd have to investigate how feasible (non-ambiguous) a format conversion  is.

Require php-intl to be installed to support i18n, but allow i18n to be disabled.

According to Google Analytics on silverstripe.org, about 30% of our visitors have a browser locale other than en-us or en-gb. In terms of developer directory (and hence a likely content author location), it's about 45% countries where English isn't the official language. So I'd expect a significant part of SilverStripe installs to require internationalisation (at least a third).
Requiring php-intl will raise the bar for getting SilverStripe installed (e.g. check some SO posts).
Other projects requiring php-intl: CakePHP, Magento
Projects not requiring it: Drupal, Yii, Wordpress, Laravel (unsurprisingly since it's just a framework without UI)

Transifex Dependency

We could deprecate the YAML translation format (and provide a conversion script) if it limits our choices too much. Transifex can deal with lots of other formats: http://docs.transifex.com/formats/, incl. XLIFF and PHP.

BTW, Drupal originally supported date() only, and had added a magic switch between date() and ISO date formats in Drupal 8: https://www.drupal.org/node/2276183. As far as I can tell, they've decided to revert this back to date() only before the Drupal 8 final release: https://github.com/drupal/drupal/commit/949e7fe6119fd4c546dc446ab1fd5f592a90680c
This is a bit different to our situation though: We're already using ISO formats, so the challenge is the other way around.

ISO/CU format support (Zend default, php-intl IntlDateFormatter default, different from PHP's date() and DateTime::format()). Used for Member.Locale preferences (and corresponding localised output). For example, two-digit months in ICU is MM, in date() it's m. So we can't easily fall back to date() here, unless we create a conversion layer similar to DateField::convert_iso_to_jquery_format)

Yes zend used RFC 2822 format date, which I had originally documented, but I decided to keep an open mind about format specificity. :) I'd be happy to add this back into the requirements.
Based on what you've stated above, even allowing i18n to be disabled with a lack of a core dependency could be pretty huge. Perhaps it's worth looking at an i18n custom option that negated the need to use php-intl (or at least approximated the functionality adequately in its absence).
This is most definitely the highest maintenance of the options.

Preferred date format for locale (long/short). Might get away with that and just getting authors to choose from a few custom formats. See Zend_Locale_Format::getDateFormat() and Member->getCMSFields()

The problem is that there may not be an author in certain cases (e.g. anonymous front-end users). The i18n system should really be able to infer standard formats without requiring human interaction.

Is php intl really such a big hurdle?
AFAIK it is bundled with PHP since 5.3 and I've checked some of the hosting providers I use and didn't find an instance where it's not installed. I don't think php intl falls into the category of an "exotic" extension, does it?
Do you collect information about the installed PHP extensions with the SilverStripe installer? If yes, it might be useful to see what the coverage of php intl is like?
As for the preferred solution: I'd stick with Zend. Reasoning: Easier migration and it seems to cover the requirements.

It would be good to understand whether php-intl is provided by default in the current stable versions of:

Debian
centos
ubuntu
php.net windows download
xampp
Mamp
homebrew

I was initially nervous about requiring php-intl as a dependency for all users but if half of users are likely to benefit from l10n, making it optional adds substantial cost, and php-intl is widespread amongst current installs, maybe it's okay to require.

So,

Debian and Ubuntu require sudo apt-get install php5-intl, then it works
Homebrew requires brew install php56-intl

I'm assuming that CentOS is similar.

The problem is that there may not be an author in certain cases (e.g. anonymous front-end users). The i18n system should really be able to infer standard formats without requiring human interaction.

It does (through i18n::$date_format, but if an author is logged in then LeftAndMain will overwrite this configuration with their preference.

I was initially nervous about requiring php-intl as a dependency for all users but if half of users are likely to benefit from l10n, making it optional adds substantial cost, and php-intl is widespread amongst current installs, maybe it's okay to require.

I think for self-hosting we should be fine. For managed hosting, it's a bit harder to find out about support. I've looked at a few common hosting providers. Basically anybody claiming to host Magento needs to have php-intl, which should make it pretty common already. Also anyone allowing SSH access and/or CPanel should have it.
*a2hosting - Yes

SiteGround - Likely (using CPanel)
bluehost - Yes
site5 - Unclear
arvixe - Unclear

So we'll be trailblazers with this decision, but it seems doable. Worth putting a vote to the community? Phrased as "if we require php-intl, we can spend more resources on other features"

OK so on the basis of all that my recommendation is that we require php-intl, and refactor our current Zend code just to use the php-intl library directly, at least for date/time/currency/number stuff.
I don't have a clear idea of what we would need between php-intl and transifex to to our string replacements, but I think that the current family of _t() helpers should continue working more or less without changes, as these are peppered throughout everyone's code.

@chillu I've drafted a voting ticket that we can post on twitter and silverstripe-dev: https://github.com/silverstripe/silverstripe-framework/issues/6207
Any objections to the content, anyone?

There should be a way to customise localised data anyway, Zend 1 libraries were great for customisation.
For example when more countries in Europe have changed to Euro currency in 2004, CLDR database was outdated. Or bugs in ICU/CLDR, e.g. http://unicode.org/cldr/trac/ticket/9747

So it sounds like symfony/translation might be a better bet than ZF2?

OK the results of the vote on #6207 are that we shouldn't have too much of a problem adding php-intl as a requirement for ss4.

I'm wondering how you solved the text direction (LTR or RTL) issue. I don't see a solution in pnp-intl or symfony.

@craigh  I've added a note; Since it's not an explicit acceptance criteria at this stage (although I'd like it to be) I'll raise it with @sminnee when we come to writing the stories for implementation.

I'm wondering how you solved the text direction (LTR or RTL) issue. I don't see a solution in pnp-intl or symfony.

@craigh I just coded a list of RTL locales in a config var in i18n. It's not perfect, but the list is short enough we can just list them.

👍

WIP here:

https://github.com/open-sausages/silverstripe-framework/commits/pulls/4.0/i18n-locale
https://github.com/open-sausages/silverstripe-reports/commits/pulls/4.0/i18n-locale
https://github.com/open-sausages/silverstripe-cms/commits/pulls/4.0/i18n-locale

can this be closed?

We will close this RFC with the above being merged.

PR at https://github.com/silverstripe/silverstripe-framework/pull/6607

Created a follow up issue with https://github.com/silverstripe/silverstripe-framework/issues/6626


Tests use .eslintrc files defined outside the project

I've run npm test and found out that there are a lot of errors. After looking around for a bit I've found the culprit - the .eslintrc file defined in the root directory. After changing its name to something else so that ESLint ignores my global rules, tests completed without issues.
Shouldn't there be an .eslintrc file in the root of the project so that stuff like this won't happen?

the config that's used here is provided by lab, so we don't bother including it in the root of the project. i'm not sure i follow how it is that your eslint config took over from that one, however, as i'm pretty sure lab is designed to use its built in config whenever there isn't an .eslintrc in the root of the project.

Well, I'm not sure what is happening either :/
But the fact is - tests don't work when there is .eslintrc in my root dir, and they do work when there is no such file.

what do you mean by root dir? like literally at /.eslintrc?

In which directory do you execute tests? And what is the command you use?

I'm in the project directory, where I fire npm test.
Placing my .eslintrc in the project's parent dir, parent's parent dir, and so on (including the root dir - I'm on Windows, so it's more like D:\.eslintrc), causes some linting errors.

throwing this upstream to lab https://github.com/hapijs/lab/issues/488


Feature: Migrate from Vanara Shell

What feature or improvement do you think would benefit Files?
Vanara is a library that streamlines the use of P/Invoke functions, enabling an easier use of Windows' programming functionalities.
While it helped us developped some functionalities within Files, it has been done to a cost. It is preventing us from enabling the trimming of the application and increases greatly the start up time of the application.
We want to remove any tie to Vanara in the upcoming future. This issue is opened to centralize any progress made toward that end.
Requirements

Vanara is no longer used inside the codebase.
Files compiles and shows no regression after the removal of Vanara.

Files Version
Version 2.4.40
Windows Version
Irrelevant
Comments
No response

@dahall Vanara has been incredibly useful in Files but it's holding us back from enabling trimming, do you have plans to add trimming support? This will save us a lot of time and will enable us to continue using the library.

Vanara's assemblies are all marked for trimming. However, any COM interface exposed, which is almost all the IShellXxx interfaces, cannot be trimmed. It is a shortcoming of .NET, not Vanara.

In that case we can limit the scope of this task to only apply to code where com is being accessed.


Deprecate tap pinning (and remove odisabled)

Tap pinning is not used by Homebrew or the Homebrew maintainers so issues relating to pinned taps (#5418, #5796) don’t get fixed. Tap pinning does not work consistently or reliably and is conceptually confusing to encourage users to use fully-scoped user/tap/formula naming or avoid shadowing core tap formulae' names instead.
While we are handling deprecations: remove all odisabled.
This will not be merged until the next minor release is imminent.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

fully-scoped user/tap/formula naming or avoid shadowing core tap formulae' names.

To a novice user, that wording may be confusing. When the user calls tap-pin, it can be assumed that they explicitly want to override the default. Perhaps one could immediately print:

brew tap-pin foo/bar (where foo/bar is whatever the user wrote) is deprecated. If you want to install formulae from foo/bar, always use the full formula name (foo/bar/<formula>).

Also, the "is shadowed by" message that is printed when the user does something with a tap formula that shadows a core formula … maybe it could mention that this behavior is going away?

@slhck Good points, I've updated some of the messaging.


Vietnamese Translation of Expose, Scale & Update in Tutorials

/assign @truongnh1992
Hi, please check my work

@kubernetes/sig-docs-vi-reviews please take a look at this PR

@kubernetes/sig-docs-vi-reviews if you have time, please take a look at this PR


Fix lxml import for ParseError, fix csw test

As pointed out by @drnextgis on 66200494ab59, I had the import for ParseError in the lxml path incorrect.  This patch fixes it, as well as an unrelated CSW test that had started failing because the source happened to be producing less records than when the test was written (moving targets and all).

@tomkralidis the test failures on travis are only a timeout, same error on each one.

@daf what about this error? https://travis-ci.org/geopython/OWSLib/jobs/69449926#L386

Oh sure, make my spot checking look bad :)  I'll check it out..

And now a lesson in why you always check the easiest/most obvious thing first: NODC geoportal is returning 503s on every request. (this was after I had built a docker container for OWSLib to run python 3.2 as that was the easiest way to get that version going)
The error could likely be better (check HTTP code somewhere instead of trying to parse an error page) but that's a separate issue and not affected by this PR.

@tomkralidis what reason this PR is still unmerged?

Thanks!


Remove spirv_new binaries and add Python script to generate them

Avoid storing binaries in version control, as it is generally not well suited to this.  Instead, add a script to regenerate the .spv files from their sources.
This also changes the ext_cl_khr_spirv_no_integer_wrap_decoration assembly source so that the SPIR-V version is listed as 1.0, to ensure that the output of spirv-dis exactly matches the assembly.
Fixes #21.
Signed-off-by: Stuart Brady<EMAIL_ADDRESS>

Two approvals (from two SPIR-V implementers), merging. Build system integration will follow in a separate PR.


Error each time lyo is ran over a new package.

When I try to run lyo-service over a package that's not already compiled (ex: left-pad), I always get an error:
Error: ENOENT: no such file or directory, rename '/home/nowuser/src/tmp/node_modules/npm-module-stats/node_modules/npm/node_modules/dezalgo' -> '/home/nowuser/src/tmp/node_modules/npm-module-stats/node_modules/npm/node_modules/.dezalgo.DELETE'
Looks like Z͘à͉̟l̞̪g̪̪̝̬͚̼͠o҉ is released, run for your life !

The problem was already reported in the dezalgo issue #7
I redeployed the server so node_modules was deleted, and the problem now seems to be solved: https://lyo.now.sh/left-pad
Was left-pad the only package having issues?

I tried a few packages and all seems to work fine now. Thanks !


Error in log: "The main field in package.json may be incorrect, which causes the App to fail to start."

While working in electron-vite-react the following message in the vite-plugin-electron.log is repeated on each build:
[24/07/2022, 14:09:15]
  Command: "vite serve".
  The main field in package.json may be incorrect, which causes the App to fail to start.
  File build path: "C:\Users\PAXANDDOS\Desktop\electron-vite-react\dist\electron\main\index.js".
  Recommended main value: "C:\Users\PAXANDDOS\Desktop\electron-vite-react\dist\electron\main\index.js".

Even though it looks like something that would break the application, it works as intended 🤔
The issue exists both on Vite v3 and v2, so it should be something in the plugin

The BUG will resolved in v0.8.2 😅
Because I am using a Mac, the duration will make such a mistake 😖
https://github.com/electron-vite/vite-plugin-electron/commit/0016d52e2157e3bda7732168cd60af88ba8aa9b0


Upgrade to Dropwizard 1.0.0, add authorization support

Based upon the 0.9 support added by @omodica, I upgraded the plugin to support Dropwizard 1.0.0. Additionally, there is support for configured roles per application. Endpoints can then be secured using the @RolesAllowed annotation.

@alexwen @bbeck any insights on when this may get merged? I'm planning on upgrading to Dropwizard 1.0.0 in the coming weeks and would like to upgrade this bundle as well. Thanks.


[#988] fix(isMobilePhone): update vi-VN validation

Updated Vietnam's mobile phone format to match most recent format
Source: https://en.wikipedia.org/wiki/Telephone_numbers_in_Vietnam#Mobile_telephone_numbers_[1]_[2]
This update closes issue #988

Thanks for the PR :smile:


Example code

Originally reported by: Craig McQueen (Bitbucket: cmcqueen1975, GitHub: Unknown)

Provide example source code that demonstrates basic usage of the encode and decode functions.
C unit tests would also demonstrate usage, however a separate example would be more accessible.

Bitbucket: https://bitbucket.org/cmcqueen1975/cobs-c/issue/4

i cant understand you code ... i saw  size_t funtions but how i am going to use them? Could you provide us an example with numbers and results


Revert "jsk_recognition: 0.3.8-1 in 'jade/distribution.yaml' [bloom]"

Reverts ros/rosdistro#10026
The jsk_pcl_ros package has been failing on the new build farm since being added in Jade.
@k-okada please try to fix this build within a few days or I will remove it from the jade distro until someone can fix it.
Thanks.
See:

http://build.ros.org/job/Jbin_uT64__jsk_pcl_ros__ubuntu_trusty_amd64__binary/
http://repositories.ros.org/status_page/ros_jade_default.html?q=jsk_pcl_ros
http://jenkins.ros.org/job/ros-jade-jsk-pcl-ros_binarydeb_trusty_amd64/ (same story with the old farm)

thanks for notifying me, the new version will goes to rosdistro soon, I also added myself to the maintainer so that I can notice this situation.

should be fixed in https://github.com/ros/rosdistro/pull/10423

Thanks, working now http://build.ros.org/job/Jbin_uT64__jsk_pcl_ros__ubuntu_trusty_amd64__binary/30/


[BUG] ChatCompletionsToolCall missing index field

Describe the bug
OpenAI response for a tool call contains a field index. This is particularly important for streaming tool call requests because the tool calls are returned individually within chunks. Without the index, it is not clear which tool call a particular chunk is referring to. While currently it seems OpenAI only returns id in the first chunk of a tool call and that could be used as a delimiter, I think that behavior could change in the future and isn't intended to be how we delimit tool calls in streaming.
JSON response:
{
  "id" : "chatcmpl-AiWm43aBO7oeXWZ3bOGNh48zGSfDN",
  "object" : "chat.completion.chunk",
  "created" :<PHONE_NUMBER>,
  "model" : "gpt-4o-mini-2024-07-18",
  "system_fingerprint" : "fp_0aa8d3e20b",
  "choices" : [ {
    "index" : 0,
    "delta" : {
      "tool_calls" : [ {
        "index" : 0,
        "id" : "call_c5QfAjfoKgdc8TLCZwCLqe75",
        "type" : "function",
        "function" : {
          "name" : "get_weather",
          "arguments" : ""
        }
      } ]
    },
    "logprobs" : null,
    "finish_reason" : null
  } ]
}

index field not parsed:
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/openai/azure-ai-openai/src/main/java/com/azure/ai/openai/models/ChatCompletionsFunctionToolCall.java#L71
Exception or Stack Trace
Add the exception log and stack trace if available
To Reproduce
Execute a streaming parallel tool call request. OpenAI docs only have one for streaming tool calls, and parallel tool calls, not parallel streaming tool calls but they can be combined to exercise the functionality.
https://platform.openai.com/docs/guides/function-calling#advanced-usage
Code Snippet
Add the code snippet that causes the issue.
    private static class StringField {
        private String type = "string";

        private String description;

        public StringField(String description) {
            this.description = description;
        }
    }

    private static class GetWeatherFunctionProperties {
        StringField
                location = new StringField("The location to get the current temperature for");
    }

    private static class GetWeatherFunctionParameterDefinition {
        private String type = "object";

        private List<String> required = List.of("location");

        private boolean additionalProperties = false;

        private GetWeatherFunctionProperties
                properties = new GetWeatherFunctionProperties();
    }

    void streamParallelToolsAndCaptureMessageContent(boolean useResponseApi) {
        FunctionDefinition functionDefinition = new FunctionDefinition("get_weather");
        GetWeatherFunctionParameterDefinition
                parameters = new GetWeatherFunctionParameterDefinition();
        functionDefinition.setParameters(BinaryData.fromObject(parameters));

        List<ChatRequestMessage> chatMessages = new ArrayList<>();
        chatMessages.add(new ChatRequestSystemMessage("You are a helpful assistant providing weather updates."));
        chatMessages.add(new ChatRequestUserMessage("What is the weather in New York City and London?"));

        ChatCompletionsOptions options = new ChatCompletionsOptions(chatMessages)
                .setTools(List.of(new ChatCompletionsFunctionToolDefinition(functionDefinition)));

        IterableStream<ChatCompletions> chatCompletionsStream = openai.client.getChatCompletionsStream(TEST_CHAT_MODEL, options);

Expected behavior
A clear and concise description of what you expected to happen.
ChatCompletions.choices.delta.toolCalls have index populated
Issue is obvious from ChatCompletionsFunctionToolCall code so will leave out remaining.
Screenshots
If applicable, add screenshots to help explain your problem.
Setup (please complete the following information):

OS: [e.g. iOS]
IDE: [e.g. IntelliJ]
Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)]
Java version: [e.g. 8]
App Server/Environment: [e.g. Tomcat, WildFly, Azure Function, Apache Spark, Databricks, IDE plugin or anything special]
Frameworks: [e.g. Spring Boot, Micronaut, Quarkus, etc]

If you suspect a dependency version mismatch (e.g. you see NoClassDefFoundError, NoSuchMethodError or similar), please check out Troubleshoot dependency version conflict article first. If it doesn't provide solution for the problem, please provide:

verbose dependency tree (mvn dependency:tree -Dverbose)
exception message, full stack trace, and any available logs

Additional context
Add any other context about the problem here.
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

@anuraaga Thank you for reaching out. @mssfang Can you please look into this?


[docs]: split each component into it's own page, similar to api docs.

Thank you for all the people who worked on the documentation website for Ionic, it's probably one of the best and easiest docs I've seen.
The request is to make each component documentation into a separate page, in similar fashion to the api docs.
The reasons for this are:

It's less confusing as sometimes when you are scrolling you move into the next component which may cause some confusion, also sometimes the demo shows the screen for the above component.
When searching for something within a given component the results set will show results for the current component's page only, not for all components (easier to find things).
Less load on server and client.

Thanks, we believe it's more important to let users unfamiliar scroll through and "window shop" ionic components when they're first learning what the framework can do.
I think by making the header bar fixed and update as you scroll, it should help with some of the confusion, though. That's in issue #949.
I get the concern, but for this section, the initial impression to new users is more important.


[bug] - hvac_power_level when off

Hi,
three bugs that I found :

I don't know if it happens only in my Home Assistant but in Settings > Device & Services > Integrations > Dual Smart Thermostat it continues to show me 0.9.6 even if I installed 0.9.8.beta.6 version

even if hvac_action_reason: opening and / or hvac_action: off (so, when the thermostat switch off heater and cooler for different reasons than achieved target temperature) hvac_power_level and hvac_power_percent stay with values different from 0

it continues to show hvac_power_percent value with a lot of decimals instead of an int number and hvac_power_level show 2.0 instead of 2 (0, 1 and 3 are ok; i cannot test more because my fancoils are a 3-speeds type)

Please check v0.9.8.beta-7

The problems were the same in 0.9.8.beta-7

But speed 2 is fixed

Also in speed 2 hvac_power_percent doesn't show 66,66666666 but 67
The problem of 33,333333333 is only on speed 1

Please check v0.9.8.beta-8

Ok, power levels now work good on device state changes.
Remain only speed 1 - percentage 33,333333333 as You can see

OK. It's foxed now in v0.9.8.beta-9

Ok, it is fixed !
Good work, well done !


Involuntary object transformations, due to freeform mouse drag handling in viewport

Tested versions
I'm using v4.2.stable.official [46dc27791]
System information
Windows 10; only tested in 3D, might be the same in 2D
Issue description
I often accidentally move or rotate nodes a tiny bit around. I often notice that much later. This is especially annoying with objects that are supposed to be in precise locations, like parts of build kits.
Steps to reproduce
The four modes Select, Move, Rotateand Scale Mode allow moving/rotating/scaling the currently selected object(s) even when the cursor is not near the gizmo or the object is actually seen on screen. I understand the upside: this allows transforming objects based on the current viewport space, instead of world/object space. But this also makes it very easy to accidentally transform things with one or more misplaced clicks.
Another minor gripe: in Move/Rotate/Scale Mode, even if you just click without actually dragging (mostly because I always forget that I can't select another object if I'm not in Select Mode), it creates an entry in the undo history.
So I guess the main question is if there is a way to block Godot from moving 3D objects in Select or any of the Translation Modes if I click/drag the cursor in the scene but not hovering the gizmo? In any case I would rather propose to extend the "Use Local Space (T)" button to allow switching between global/local/viewport, and get rid of the input recognition outside of the gizmo.
Minimal reproduction project (MRP)
N/A

I changed the title, maybe it makes it a bit more clear that this a problem.
Also, as an addendum, when testing this: The mouse dragging leading to the transformation is only registered if it starts over other objects - not over the background.

The issue with the history will be resolved with #87161

Yeah; another idea would be to (de)activate this kind of transform via an option in the Editor settings.

I think I've read somewhere the maintainers don't like that kind trivial behavior tucked away in the editor settings, since it's ends up not being used by 99% of people, and just forgotten about, so it becomes clutter. You can try the PR I made above a shot, let me know what you think:  Testing pull requests

This behavior in Select Mode is a bug #85736


Force migrate 'alter' on tests

Force default migrate to 'alter' so it's independent from waterline core's default: balderdashy/waterline#887
Addresses balderdashy/waterline#887

Seems good to me :heavy_check_mark:

@tjwebb, if we compare the latest master build (using the merged new default balderdashy/waterline#962) we can see:
 -------------------------------------------------------------------
| adapter          | version | status  | failed | total | wl-sequel |
|------------------|---------|---------|--------|-------|-----------|
| sails-postgresql | 0ad94e5 | failed  |      6 |     6 |     0.3.0 |
| sails-memory     | 7cf3600 | success |      0 |   207 |           |
| sails-disk       | 5210c18 | success |      0 |   209 |           |
| sails-mongo      | 414d748 | failed  |      5 |   210 |           |
| sails-mysql      | d289f11 | failed  |      2 |     2 |     0.3.0 |
| sails-redis      | 6eb8f92 | failed  |     29 |   196 |           |
 -------------------------------------------------------------------

On the other hand this PR's build brings the results to normality:
 -------------------------------------------------------------------
| adapter          | version | status  | failed | total | wl-sequel |
|------------------|---------|---------|--------|-------|-----------|
| sails-postgresql | 0ad94e5 | failed  |      2 |   228 |     0.3.0 |
| sails-memory     | 7cf3600 | success |      0 |   211 |           |
| sails-disk       | 5210c18 | success |      0 |   209 |           |
| sails-mongo      | 414d748 | failed  |      5 |   209 |           |
| sails-mysql      | d289f11 | failed  |      3 |   235 |     0.3.0 |
| sails-redis      | 6eb8f92 | failed  |     42 |   209 |           |
 -------------------------------------------------------------------

With only the known/expected errors. Any other concerns or shall we merge this as well?


UnboundLocalError: local variable 's' referenced before assignment

In tweetfeels.py I always get this error  on the
return s
There is data (I can print it and there are many tweets with the subjects i'm looking at) and sentiments is a generator returned, but it never gives a next. What could be wrong?

Think I found the answer; you need to unzip and manually copy the vader lexicon txt file into your working directory if you are under Windows, otherwise the sentiment is always 0 and it throws those away.

Thanks for reporting and testing. I am currently traveling so don't have windows machine readily available to test. However, feel free to send a pull request if you end up making any changes.
-Thomas

On Jul 2, 2017, at 2:13 AM, tluyben<EMAIL_ADDRESS>wrote:
Think I found the answer; you need to unzip and manually copy the vader lexicon txt file into your working directory if you are under Windows, otherwise the sentiment is always 0 and it throws those away.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have this error in Ubuntu. Whenever I try to run trump_feels.sentiment.values I always get UnboundLocalError: local variable 's' referenced before assignment .


Shorten lamindb import time

Currently takes ~11s

I created an import log which can be viewed with https://github.com/nschloe/tuna
python -X importtime -c "import lamindb as ln" 2> lamindb_import.log
tuna lamindb_import.log

lamindb_import.log
This then looks something like

So the biggest offenders are lndb_setup and lamindb_check_versions

As far as I know there's a couple of ways to speed up application startup and the whole performance of a package:

Lazily import packages. We should only do this when we can ensure that the function importing the module is not called repeatedly. Else wise, we'll keep scanning the environment to find the package to import which can get expensive over time.
Lazily run startup functions. This is a tradeoff between startup time and application performance. We're basically moving some expensive startup imports to functions that users have to call anyways.
from imports
Instead of

import math
value = math.sqrt(50)

we do
from math import sqrt
value = sqrt(50)

remove unused imports & reduce dependency sets in general. Generally flake8 should annoy us about the former and we hopefully figure out the latter.

I can't look into lndb_setup yet because I don't have access so I looked into _check_versions instead.
from bionty import __version__ as bionty_v
from lndb_setup import __version__ as lndb_setup_v
from lnschema_core import __version__ as lnschema_core_v
from nbproject import __version__ as nbproject_v
from packaging import version

if version.parse(lndb_setup_v) != version.parse("0.30.10"):
    raise RuntimeError("Upgrade lndb_setup! pip install lndb_setup==0.30.10")

if version.parse(lnschema_core_v) != version.parse("0.25.3"):
    raise RuntimeError("lamindb needs lnschema_core==0.25.3")

if version.parse(bionty_v) != version.parse("0.6.4"):
    raise RuntimeError("lamindb needs bionty==0.6.4")

if version.parse(nbproject_v) < version.parse("0.8.0"):
    raise RuntimeError("lamindb needs nbproject>=0.8.0")

All of these required versions are pinned in the pyproject.toml
dependencies = [
    # Lamin pinned packages
    "lndb_setup==0.30.10",
    "lnschema_core==0.25.3",
    "bionty==0.6.4",
    "nbproject>=0.8.0",
]

Hence, the installation would already raise errors if for some reason this specific version of lamindb were installed in an environment with the wrong set of dependencies.
In any case, I noticed that the __version__ imports import all of the respective packages.

My guess is when importing __version__ all other statements and imports of the packages are also executed.
Hence,
>>> from importlib.metadata import version
>>> version('bionty')
'0.6.4'

etc might be faster. I'll try this later.

Thanks for benchmarking this in-depth, Lukas!
We haven't gotten around to optimizing anything for LaminDB yet, but I did similar benchmarks for other packages in the past. :sweat_smile:
Let's keep this open and decide whether to act on anything - I think the current situation is a lot better than what we had in early December already, but @sunnyosun will speak more to this.
To this note:

Hence, the installation would already raise errors if for some reason this specific version of lamindb were installed in an environment with the wrong set of dependencies.

You're right (edit: I think, pip raises red-colored "errors" but will still successfully install say lamindb; some users might ignore these "errors" as they behave more like warnings)! The ._check_versions.py piece is mostly meant for devs who pip install -e . and update via git pull --rebase. This is currently the common workflow for us, and within it, .check_versions is pivotal for raising early errors related to inconsistent local environments. We had added similar functionality to Scanpy back in the days.

Thank you for such deep analysis @Zethson! Yes, we improved from 11s → 5s in the past month.
I think 5s is acceptable for now, if importing the version as you suggested can give immediate improvement, that would be great! Otherwise maybe we could look into this a bit more in the future when needed. 😄


database test does not exist，and image 404

I used docker-compose to deploy the superset, which is version v1.0.0,
Test database does not exist during initialization
Unable to open it after login.
superset_app             | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app             | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_worker          | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_tests_worker    | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_db              | 2021-01-25 02:51:53.376 UTC [31] FATAL:  database "test" does not exist
superset_tests_worker    | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker    |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker    | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL:  database "test" does not exist
superset_tests_worker    |
superset_tests_worker    | (Background on this error at: http://sqlalche.me/e/13/e3q8)
superset_tests_worker    | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_tests_worker exited with code 1
superset_init            | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init            | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init            |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_init            | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
superset_init            | INFO  [alembic.runtime.migration] Will assume transactional DDL.
superset_init            | Loaded your LOCAL configuration at [/app/docker/pythonpath_dev/superset_config.py]
superset_worker          | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_worker          |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_worker          | /usr/local/lib/python3.7/site-packages/celery/platforms.py:801: RuntimeWarning: You're running the worker with superuser privileges: this is
superset_worker          | absolutely not recommended!

......

superset_init            | INFO:superset.models.helpers:Updating table_columns yt_other
superset_init            | INFO:superset.models.helpers:Updating table_columns gender
superset_init            | INFO:superset.datasets.commands.importers.v1.utils:Loading data inside the import transaction
Exception in thread Thread-22:
Traceback (most recent call last):
  File "site-packages/urllib3/connectionpool.py", line 384, in _make_request
  File "<string>", line 2, in raise_from
  File "site-packages/urllib3/connectionpool.py", line 380, in _make_request
  File "http/client.py", line 1331, in getresponse
  File "http/client.py", line 297, in begin
  File "http/client.py", line 258, in _read_status
  File "socket.py", line 586, in readinto
socket.timeout: timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "site-packages/requests/adapters.py", line 449, in send
  File "site-packages/urllib3/connectionpool.py", line 638, in urlopen
  File "site-packages/urllib3/util/retry.py", line 368, in increment
  File "site-packages/urllib3/packages/six.py", line 686, in reraise
  File "site-packages/urllib3/connectionpool.py", line 600, in urlopen
  File "site-packages/urllib3/connectionpool.py", line 386, in _make_request
  File "site-packages/urllib3/connectionpool.py", line 306, in _raise_timeout
urllib3.exceptions.ReadTimeoutError: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "threading.py", line 916, in _bootstrap_inner
  File "threading.py", line 864, in run
  File "compose/cli/log_printer.py", line 214, in watch_events
  File "compose/project.py", line 493, in yield_loop
  File "compose/project.py", line 461, in build_container_event
  File "compose/container.py", line 48, in from_id
  File "site-packages/docker/utils/decorators.py", line 19, in wrapped
  File "site-packages/docker/api/container.py", line 755, in inspect_container
  File "site-packages/docker/utils/decorators.py", line 46, in inner
  File "site-packages/docker/api/client.py", line 230, in _get
  File "site-packages/requests/sessions.py", line 537, in get
  File "site-packages/requests/sessions.py", line 524, in request
  File "site-packages/requests/sessions.py", line 637, in send
  File "site-packages/requests/adapters.py", line 529, in send
requests.exceptions.ReadTimeout: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out. (read timeout=60)

superset_init            | /app/docker/docker-init.sh: line 79:    36 Killed                  superset load_examples
superset_db              | 2021-01-25 02:56:12.771 UTC [39] LOG:  unexpected EOF on client connection with an open transaction
superset_app             | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_app             |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_app             | <IP_ADDRESS> - - [25/Jan/2021 02:56:12] "GET / HTTP/1.1" 302 -

.....
superset_app             | <IP_ADDRESS> - - [25/Jan/2021 02:57:00] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [25/Jan/2021 02:57:00] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [25/Jan/2021 02:57:00] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [25/Jan/2021 02:57:00] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | DEBUG:superset.stats_logger:[stats_logger] (incr) welcome
superset_app             | <IP_ADDRESS> - - [25/Jan/2021 02:57:01] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [25/Jan/2021 02:57:01] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [25/Jan/2021 02:57:01] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [25/Jan/2021 02:57:01] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -

seems like a internet connection problem:
superset_init            | INFO:superset.datasets.commands.importers.v1.utils:Loading data inside the import transaction
Exception in thread Thread-22:
Traceback (most recent call last):
  File "site-packages/urllib3/connectionpool.py", line 384, in _make_request
  File "<string>", line 2, in raise_from
  File "site-packages/urllib3/connectionpool.py", line 380, in _make_request
  File "http/client.py", line 1331, in getresponse
  File "http/client.py", line 297, in begin
  File "http/client.py", line 258, in _read_status
  File "socket.py", line 586, in readinto
socket.timeout: timed out

seems like a internet connection problem:
superset_init            | INFO:superset.datasets.commands.importers.v1.utils:Loading data inside the import transaction
Exception in thread Thread-22:
Traceback (most recent call last):
  File "site-packages/urllib3/connectionpool.py", line 384, in _make_request
  File "<string>", line 2, in raise_from
  File "site-packages/urllib3/connectionpool.py", line 380, in _make_request
  File "http/client.py", line 1331, in getresponse
  File "http/client.py", line 297, in begin
  File "http/client.py", line 258, in _read_status
  File "socket.py", line 586, in readinto
socket.timeout: timed out

I have the same issue when running docker-compose up from a Mac running latest Docker Desktop. There's no evidence of network errors in the startup logs, but I have flask_appbuilder errors. And the end result is the same - a blank page with broken image links and buttons.
db_1                     | CREATE DATABASE
db_1                     |
db_1                     |
db_1                     | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1                     |
db_1                     | 2021-01-25 18:27:34.546 UTC [48] LOG:  received fast shutdown request
db_1                     | waiting for server to shut down....2021-01-25 18:27:34.547 UTC [48] LOG:  aborting any active transactions
db_1                     | 2021-01-25 18:27:34.549 UTC [48] LOG:  worker process: logical replication launcher (PID 55) exited with exit code 1
db_1                     | 2021-01-25 18:27:34.551 UTC [50] LOG:  shutting down
db_1                     | 2021-01-25 18:27:34.563 UTC [48] LOG:  database system is shut down
db_1                     |  done
db_1                     | server stopped
db_1                     |
db_1                     | PostgreSQL init process complete; ready for start up.
db_1                     |
db_1                     | 2021-01-25 18:27:34.659 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1                     | 2021-01-25 18:27:34.659 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1                     | 2021-01-25 18:27:34.661 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1                     | 2021-01-25 18:27:34.672 UTC [76] LOG:  database system was shut down at 2021-01-25 18:27:34 UTC
db_1                     | 2021-01-25 18:27:34.677 UTC [1] LOG:  database system is ready to accept connections
superset_node            | npm WARN using --force I sure hope you know what you are doing.
superset_app             |  * Serving Flask app "superset.app:create_app()" (lazy loading)
superset_app             |  * Environment: development
superset_app             |  * Debug mode: on
superset_app             |  * Running on http://<IP_ADDRESS>:8088/ (Press CTRL+C to quit)
superset_app             |  * Restarting with stat
superset_tests_worker    | INFO:superset.utils.logging_configurator:logging was configured successfully
db_1                     | 2021-01-25 18:27:38.783 UTC [83] FATAL:  database "test" does not exist
superset_tests_worker    | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker    |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker    | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL:  database "test" does not exist
superset_tests_worker    |
superset_tests_worker    | (Background on this error at: http://sqlalche.me/e/13/e3q8)

I have the same issue when running docker-compose up from a Mac running latest Docker Desktop. There's no evidence of network errors in the startup logs, but I have flask_appbuilder errors. And the end result is the same - a blank page with broken image links and buttons.
db_1                     | CREATE DATABASE
db_1                     |
db_1                     |
db_1                     | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1                     |
db_1                     | 2021-01-25 18:27:34.546 UTC [48] LOG:  received fast shutdown request
db_1                     | waiting for server to shut down....2021-01-25 18:27:34.547 UTC [48] LOG:  aborting any active transactions
db_1                     | 2021-01-25 18:27:34.549 UTC [48] LOG:  worker process: logical replication launcher (PID 55) exited with exit code 1
db_1                     | 2021-01-25 18:27:34.551 UTC [50] LOG:  shutting down
db_1                     | 2021-01-25 18:27:34.563 UTC [48] LOG:  database system is shut down
db_1                     |  done
db_1                     | server stopped
db_1                     |
db_1                     | PostgreSQL init process complete; ready for start up.
db_1                     |
db_1                     | 2021-01-25 18:27:34.659 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1                     | 2021-01-25 18:27:34.659 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1                     | 2021-01-25 18:27:34.661 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1                     | 2021-01-25 18:27:34.672 UTC [76] LOG:  database system was shut down at 2021-01-25 18:27:34 UTC
db_1                     | 2021-01-25 18:27:34.677 UTC [1] LOG:  database system is ready to accept connections
superset_node            | npm WARN using --force I sure hope you know what you are doing.
superset_app             |  * Serving Flask app "superset.app:create_app()" (lazy loading)
superset_app             |  * Environment: development
superset_app             |  * Debug mode: on
superset_app             |  * Running on http://<IP_ADDRESS>:8088/ (Press CTRL+C to quit)
superset_app             |  * Restarting with stat
superset_tests_worker    | INFO:superset.utils.logging_configurator:logging was configured successfully
db_1                     | 2021-01-25 18:27:38.783 UTC [83] FATAL:  database "test" does not exist
superset_tests_worker    | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker    |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker    | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL:  database "test" does not exist
superset_tests_worker    |
superset_tests_worker    | (Background on this error at: http://sqlalche.me/e/13/e3q8)

seems like a internet connection problem:
superset_init            | INFO:superset.datasets.commands.importers.v1.utils:Loading data inside the import transaction
Exception in thread Thread-22:
Traceback (most recent call last):
  File "site-packages/urllib3/connectionpool.py", line 384, in _make_request
  File "<string>", line 2, in raise_from
  File "site-packages/urllib3/connectionpool.py", line 380, in _make_request
  File "http/client.py", line 1331, in getresponse
  File "http/client.py", line 297, in begin
  File "http/client.py", line 258, in _read_status
  File "socket.py", line 586, in readinto
socket.timeout: timed out

I can guarantee that my network is good

seems like a internet connection problem:
superset_init            | INFO:superset.datasets.commands.importers.v1.utils:Loading data inside the import transaction
Exception in thread Thread-22:
Traceback (most recent call last):
  File "site-packages/urllib3/connectionpool.py", line 384, in _make_request
  File "<string>", line 2, in raise_from
  File "site-packages/urllib3/connectionpool.py", line 380, in _make_request
  File "http/client.py", line 1331, in getresponse
  File "http/client.py", line 297, in begin
  File "http/client.py", line 258, in _read_status
  File "socket.py", line 586, in readinto
socket.timeout: timed out

I can guarantee that my network is good

Yeah, I have the same issue too. How to fix it?

Yeah, I have the same issue too. How to fix it?

docker-compose ps

        Name                       Command                   State                     Ports
----------------------------------------------------------------------------------------------------------
superset_app            /usr/bin/docker-entrypoint ...   Up (unhealthy)   8080/tcp, <IP_ADDRESS>:8088->8088/tcp
superset_cache          docker-entrypoint.sh redis ...   Up               <IP_ADDRESS>:6379->6379/tcp
superset_db             docker-entrypoint.sh postgres    Up               <IP_ADDRESS>:5432->5432/tcp
superset_init           /usr/bin/docker-entrypoint ...   Up (unhealthy)   8080/tcp
superset_node           docker-entrypoint.sh /app/ ...   Up
superset_tests_worker   /usr/bin/docker-entrypoint ...   Exit 1
superset_worker         /usr/bin/docker-entrypoint ...   Up (unhealthy)   8080/tcp

I encountered this error following the tutorial too. (git clone,git checkout latest, docker-compose up) on mac os.
Let me say that I do not know much about this project, but this connection error comes from the test_worker, and I don't know if the tests_worker is really necessary in the demo.
It fails because is looking for a local test postgres database in the host network. see https://github.com/apache/superset/blob/master/docker-compose.yml#L93
  superset-tests-worker:
    image: *superset-image
    container_name: superset_tests_worker
    command: ["/app/docker/docker-bootstrap.sh", "worker"]
    env_file: docker/.env
    environment:
      DATABASE_HOST: localhost
      DATABASE_DB: test
      REDIS_CELERY_DB: 2
      REDIS_RESULTS_DB: 3
      REDIS_HOST: localhost
    network_mode: host
    depends_on: *superset-depends-on
    user: "root"
    volumes: *superset-volumes

docker-compose ps

        Name                       Command                   State                     Ports
----------------------------------------------------------------------------------------------------------
superset_app            /usr/bin/docker-entrypoint ...   Up (unhealthy)   8080/tcp, <IP_ADDRESS>:8088->8088/tcp
superset_cache          docker-entrypoint.sh redis ...   Up               <IP_ADDRESS>:6379->6379/tcp
superset_db             docker-entrypoint.sh postgres    Up               <IP_ADDRESS>:5432->5432/tcp
superset_init           /usr/bin/docker-entrypoint ...   Up (unhealthy)   8080/tcp
superset_node           docker-entrypoint.sh /app/ ...   Up
superset_tests_worker   /usr/bin/docker-entrypoint ...   Exit 1
superset_worker         /usr/bin/docker-entrypoint ...   Up (unhealthy)   8080/tcp

I encountered this error following the tutorial too. (git clone,git checkout latest, docker-compose up) on mac os.
Let me say that I do not know much about this project, but this connection error comes from the test_worker, and I don't know if the tests_worker is really necessary in the demo.
It fails because is looking for a local test postgres database in the host network. see https://github.com/apache/superset/blob/master/docker-compose.yml#L93
  superset-tests-worker:
    image: *superset-image
    container_name: superset_tests_worker
    command: ["/app/docker/docker-bootstrap.sh", "worker"]
    env_file: docker/.env
    environment:
      DATABASE_HOST: localhost
      DATABASE_DB: test
      REDIS_CELERY_DB: 2
      REDIS_RESULTS_DB: 3
      REDIS_HOST: localhost
    network_mode: host
    depends_on: *superset-depends-on
    user: "root"
    volumes: *superset-volumes

I think the problem is in the superset_node container, this seems a more likely kind of cause..
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-tEu6DGxGgRJPb/mVPIZ48e69xCn2yRmCgYmDugAVwmJ6o+0u1RI18eO7E7WBTLYLaEVVOhwQmcdhQHweux/WPg==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-6SDcJbLVOcfQyjPg+spNU1+JVrkU1B9fzUa5tpbP/mMNUPyigCOJwcEIQAJSbp9jt5UP3EXvQR0vtYXIo9AjyA==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-GUXpO713URNzaExVUgBtqA5fr2UuxUG/fVitI04zEFHVL2FHSjd672alHq8E16oQqRNzF0m1bmx8WlTnDrGSqQ==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/datamaps-264ee032/dist/datamaps.cod.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, futime

but maybe it's just very very slow to compile the frontend?

I think the problem is in the superset_node container, this seems a more likely kind of cause..
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-tEu6DGxGgRJPb/mVPIZ48e69xCn2yRmCgYmDugAVwmJ6o+0u1RI18eO7E7WBTLYLaEVVOhwQmcdhQHweux/WPg==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-6SDcJbLVOcfQyjPg+spNU1+JVrkU1B9fzUa5tpbP/mMNUPyigCOJwcEIQAJSbp9jt5UP3EXvQR0vtYXIo9AjyA==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-GUXpO713URNzaExVUgBtqA5fr2UuxUG/fVitI04zEFHVL2FHSjd672alHq8E16oQqRNzF0m1bmx8WlTnDrGSqQ==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/datamaps-264ee032/dist/datamaps.cod.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, futime

but maybe it's just very very slow to compile the frontend?

Try increasing the RAM to 7-8gb and restarting docker, fixed it for me

Try increasing the RAM to 7-8gb and restarting docker, fixed it for me

I have the same issue when running docker-compose up from a Mac running latest Docker Desktop. There's no evidence of network errors in the startup logs, but I have flask_appbuilder errors. And the end result is the same - a blank page with broken image links and buttons.
db_1                     | CREATE DATABASE
db_1                     |
db_1                     |
db_1                     | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
db_1                     |
db_1                     | 2021-01-25 18:27:34.546 UTC [48] LOG:  received fast shutdown request
db_1                     | waiting for server to shut down....2021-01-25 18:27:34.547 UTC [48] LOG:  aborting any active transactions
db_1                     | 2021-01-25 18:27:34.549 UTC [48] LOG:  worker process: logical replication launcher (PID 55) exited with exit code 1
db_1                     | 2021-01-25 18:27:34.551 UTC [50] LOG:  shutting down
db_1                     | 2021-01-25 18:27:34.563 UTC [48] LOG:  database system is shut down
db_1                     |  done
db_1                     | server stopped
db_1                     |
db_1                     | PostgreSQL init process complete; ready for start up.
db_1                     |
db_1                     | 2021-01-25 18:27:34.659 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
db_1                     | 2021-01-25 18:27:34.659 UTC [1] LOG:  listening on IPv6 address "::", port 5432
db_1                     | 2021-01-25 18:27:34.661 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
db_1                     | 2021-01-25 18:27:34.672 UTC [76] LOG:  database system was shut down at 2021-01-25 18:27:34 UTC
db_1                     | 2021-01-25 18:27:34.677 UTC [1] LOG:  database system is ready to accept connections
superset_node            | npm WARN using --force I sure hope you know what you are doing.
superset_app             |  * Serving Flask app "superset.app:create_app()" (lazy loading)
superset_app             |  * Environment: development
superset_app             |  * Debug mode: on
superset_app             |  * Running on http://<IP_ADDRESS>:8088/ (Press CTRL+C to quit)
superset_app             |  * Restarting with stat
superset_tests_worker    | INFO:superset.utils.logging_configurator:logging was configured successfully
db_1                     | 2021-01-25 18:27:38.783 UTC [83] FATAL:  database "test" does not exist
superset_tests_worker    | /usr/local/lib/python3.7/site-packages/flask_caching/__init__.py:192: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker    |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker    | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL:  database "test" does not exist
superset_tests_worker    |
superset_tests_worker    | (Background on this error at: http://sqlalche.me/e/13/e3q8)

After changing to the CentOS environment with RAM 8G, everything is well done, fixed it for me, you can try it

I just tried again on the latest master. Mac os, 9gb ram in my docker setup. Not fixed afaict. still blank page after the login.
I could run the frontend manually in the host, after the superset-node container crashed,  by cd'ing into the frontend folder, installing the deps via npm i and then npm run dev.

Same here. Blank page after the login.
MacOS version : 11.2.1
Docker Desktop : 3.1.0
8GB Memory allocated to Docker.

#10773
check this, you need wait for a while

Try increasing the RAM to 7-8gb and restarting docker, fixed it for me

This worked for me. Thanks @gee-m , you made my day.

Same problem:
MacOS version : 11.2.3
Docker Desktop : 3.2.2
7.5GB Memory allocated to Docker
Latest master branch (cloned 3/23/2021)
Errors:

Same problem:
MacOS version : 11.2.3
Docker Desktop : 3.2.2
7.5GB Memory allocated to Docker
Latest master branch (cloned 3/23/2021)
$ docker-compose up is used.
Errors:

I just did the following to make it work:

change to master branch git checkout master
change redis from 3.2 to latest in docker-compose-non-dev.yml

use docker-compose -f docker-compose-non-dev.yml up to start the server
wait sometime and superset_init exited with 0 is expected - it does not affect the server:

as per the label resolved this question seems answered --> closing


[ENH] Default alpha values

Is your feature request related to a problem? Please describe.
DEFAULT_ALPHA = 0.05 today, but defaults in predict_quantiles are [0.05, 0.95] which is equivalent to alpha = 0.10.
https://github.com/alan-turing-institute/sktime/blob/87bdf36dbc0990f29942eb6f7fa56a8e6c5fa7b7/sktime/forecasting/base/_base.py#L375
Describe the solution you'd like
Defaults in predict_quantiles should be 0.025 and 0.975 to make it consistent with DEFAULT_ALPHA and backward compatible after return_pred_int is deprecated in 0.11.0.

Hmmm - I admit this may be confusing now.
I´m not sure there is an inconsistency and I thought we did the refactor in a downwards compatible way.
There are a number of quantities in play here, for predictive quantiles and intervals:

the coverage of a symmetric predictive interval
the lower quantile point of a symmetric predictive interval, alpha_low, corresponding to the "lower" end value (the quantile at alpha_low)

the higher quantile point of a symmetric predictive interval, alpha_high, corrdsponding to the "upper" end value (the quantile at alpha_high)

the significance level p arising from a symmetric predictive interval if containedness is the null

For the same interval, assuming symmetry, the relations are as follows:

coverage = 1-p
coverage = alpha_high - alpha_low
alpha_high = 1 - alpha_low (symmetry)

The "old" DEFAULT_ALPHA, to the best of my understanding, was (somewhat confusingly) implemented as alpha_low in most of the cases. Unfortunately, this was nowhere properly documented, only now we have proper docstrings that explain what alpha and coverage are, mathematically.
The "old" DEFAULT_ALPHA of 0.05 (alpha_low above) corresponds to a coverage of 0.9, and quantile points alpha_low = 0.05, alpha_high = 0.95.
That would be downwards compatible choices of defaults?

@fkiraly - What might be helpful is to get the equivalent of what Hyndman uses here.

The hilo() function converts the forecast distributions into intervals. By default, 80% and 95% prediction intervals are returned, although other options are possible via the level argument.

Level
What does level correspond to in sktime terminology?
Is level in Hyndman's language = coverage in sktime language?
Hilo
What would be equivalent of hilo 80 and hilo 95 using predict_interval and predict_quantiles in sktime?
Would hilo 80 be equivalent to predict_interval(coverage=0.9) and predict_quantiles(alpha=[0.1, 0.9])?
Would hilo 95 be equivalent to predict_interval(coverage=0.95) and predict_quantiles(alpha=[0.025, 0.975])?

Yes, I think this is all correct.
Once we have predict_proba implemented, you can also just call the quantiles methods on the distribution, but using predict_interval is more direct.

Thanks for clarifying. I will close this for now.


Player walking off the platform

If you leave the player where it spawned, you can make the player walk off the platform by holding the down and right keys. Releasing the down key (but not the right key) will teleport the player back onto the platform.

Edit: you can do the same to the other corners of the map too.

Thanks! Just realized that this can happen on any corner. The problem will be fixed soon.

.

Issue fixed in version 2021.7.8.
If you want to see your contribution to make the game better, try installing the new version.
Note: This update will not be available through the included updater in each version. But future versions will.


Allow user to download SSL certificate

Hello,
I would like to be allowed to download ssl/cert/key from dashboard.
also it would be nice if you replace the number count of vconf file and ssl folder from number to domain/subdomain name!
ex when i create first proxy_host you create nginx vhost as 1.conf it will be better if domainname.com.conf this way i more easy to find out where is domain config file or ssl folder!

There are some good questions in #683; I personally would like to see certificate-foldernames in /etc/letsencrypt/live/ to use the certificate name as show in the GUI. I.e. "domain.ext".
That IMHO would make it much easier to re-use the certs from NPM in other docker containers, something that will come up again and again...
I've looked at the code and I see it is not a simple change.
But maybe it is possible to make symlinks the active certs to a 'static' [cert displayname] location?
I.e. /certificates/mydomain.ext (wildcard or tld) or /certificates/host.mydomain.ext (for hostname certs).
It could be a separate dir && docker-volume i.e. /certificates, or a dir under the data or letsencrypt volumes.
I wish I was a programmer and could help a bit, but alas, I can just (barely) get the gist of the code.
Thanks for listening to my input.
Best regards,
George

For now https://github.com/jc21/nginx-proxy-manager/pull/1100 has been implemented to make it generally possible to know which certificate is which.

Added via https://github.com/jc21/nginx-proxy-manager/pull/1343


Archive artifacts for kube_smoke_test

This will archive kube_smoke_test.log/.journal/.html and discard after 14 days

@rguthriemsft @dcaro FYI


Access-Control-Allow-Origin Error

Http requests failed after updated to v3.0. I received
Failed to load resource: Origin http://localhost:8080 is not allowed by Access-Control-Allow-Origin.
in console. Somehow the request origin is localhost:8080. Is this intended? I also updated CLI to v3.

Cordova CLI: 6.5.0
Ionic Framework Version: 2.2.0
Ionic CLI Version: 3.0.0-beta.4
ios-deploy version: 1.9.0
ios-sim version: 3.1.1
OS: OS X El Capitan
Node Version: v6.10.0
Xcode version: Xcode 8.2.1 Build version 8C1002

You could allow cors to localhost (though it would not be recommend)
Duplicate of https://github.com/driftyco/cordova-plugin-wkwebview-engine/issues/111


Quick peek at a data folder in JBrowse

Suppose you have freshly assembled data files and assorted config.json in path/to/my/tiny/herb
Then:
scripts/browse path/to/my/tiny_herb

Open http://localhost:3000, and voilà :)
That is, if the image exists, which you can ensure by:
scripts/browse --build

I'm not sure you'll find it useful, but in doubt I open this PR :)

So the difference from dockerserve --dev

As an example, the workflow you used  in #43:
./scripts/dockerserve --dev
./scripts/dockermake --test SPECIES=linum_popgen
cp -r tests/data/linum_popgen hugo/static/data

becomes:
./scripts/dockermake --test SPECIES=linum_popgen
./scripts/browse tests/data/linum_popgen


App does not appear

Im trying to launch an android vr app from the google play store but I cannot find it in the launcher.

can you provide more details? which app is it?

Vf 2000 on google play

@tedwaltmuf, can you go to settings (the gear icon in the top left) and enable "2d apps"? Let me know if it shows up. By default, 2d apps are hidden. (I just tried it with this app)

I did and it’s not supposed to be 2d it’s a vr app. It does not show up still.

Hi @tedwaltmuf  - I installed the app and it shows up as 2d (under the 2d tab). The launcher checks for a specific manifest setting to determine if this is an Oculus 3d app ("com.samsung.android.vr.application.mode"). This app does not contain this setting.

Is there a way to change it because it is a vr app that works on Samsung gear normally

Are you sure that this is a VR app? When I launch it on my Quest, it runs as a 2D app. Here's the documentation for VR apps, which describes the above manifest setting: https://developer.oculus.com/documentation/mobilesdk/latest/concepts/mobile-native-manifest/

Yes I can use it on a Samsung gear, I’m trying to port it over to the oculus because I do not like the gear. There’s the vf2000 which is vr portion and it has another app that acts as the controller from a tablet called vf2000 controller.

Just to clarify: On my quest, vf2000 runs as up as a 2d app. Is that the same for you?

Yes I can only see it on the side quest launcher in my quest and when I load it is only in 2d and it doesn’t register with the headset tracking.

Ok - so that's not an issue with quest app launcher; the app itself runs as 2d on the quest. If you enabled "Show 2D" in settings, does it show up under the 2D tab?

It seems to show up now after selecting show 2d and a restart. Is there anyway to make it play how it’s supposed to in vr?

Thanks for confirming. I'm going to close this issue because it's not an issue with the launcher. I think you'll need to contact the developers of this app and ask them to port it to Quest.


Players load to black screen with UI and "press E" prompt

I'm a bit confused that nobody else is posting this issue, but everyone within my group is having it independent of me - whenever I or someone else joins a game with LGU installed, the screen looks like this:

At first I assumed this was incompatibility with other mods, However, we've all disabled all of our other (non-essential) mods, verified integrity. We ran the preloader fix in r2modman, and I also confirmed that the FixPluginTypesSerialization error there happened regardless of whether LGU was the only mod installed, or we had all the others enabled EXCEPT LGU - didn't change that part. I scanned the log here but didn't really see anything that would indicate what was going on.
The log from the player seeing this screen is as follows:
[Message:   BepInEx] BepInEx <IP_ADDRESS> - Lethal Company (10/23/2024 8:37:46 PM)
[Info   :   BepInEx] Running under Unity v2<IP_ADDRESS>51836
[Info   :   BepInEx] CLR runtime version: 4.0.30319.42000
[Info   :   BepInEx] Supports SRE: True
[Info   :   BepInEx] System platform: Bits64, Windows
[Message:   BepInEx] Preloader started
[Info   :   BepInEx] Loaded 1 patcher method from [BepInEx.Preloader <IP_ADDRESS>]
[Info   :   BepInEx] Loaded 1 patcher method from [FixPluginTypesSerialization <IP_ADDRESS>]
[Info   :   BepInEx] Loaded 1 patcher method from [BepInEx.MonoMod.HookGenPatcher <IP_ADDRESS>]
[Info   :   BepInEx] 3 patcher plugins loaded
[Info   :HookGenPatcher] Previous MMHOOK location found. Using that location to save instead.
[Info   :HookGenPatcher] Already ran for this version, reusing that file.
[Message:FixPluginTypesSerialization] Not using the config cache
[Info   :FixPluginTypesSerialization] Downloading : http://symbolserver.unity3d.com/UnityPlayer_Win64_player_mono_x64.pdb\8C09BC2213204B18A647FD90F53236701\UnityPlayer_Win64_player_mono_x64.pd_
This pdb file is needed for the plugin to work properly. This may take a while, relax, modding is coming.
[Error  :FixPluginTypesSerialization] Failed to initialize plugin types serialization fix: (System.Net.Http.HttpRequestException) An error occurred while sending the request. Some plugins may not work properly.
[Error  :FixPluginTypesSerialization] System.Net.Http.HttpRequestException: An error occurred while sending the request ---> System.Net.WebException: Invalid status code: 308 ---> System.Net.ProtocolViolationException: Invalid status code: 308
  at System.Net.HttpWebRequest.Redirect (System.Net.HttpStatusCode code, System.Net.WebResponse response) [0x000e2] in <d054a9182977441aa432503a474315ba>:0
  at System.Net.HttpWebRequest.CheckFinalStatus (System.Net.HttpWebResponse response) [0x0016f] in <d054a9182977441aa432503a474315ba>:0
  at System.Net.HttpWebRequest.GetResponseFromData (System.Net.WebResponseStream stream, System.Threading.CancellationToken cancellationToken) [0x0006f] in <d054a9182977441aa432503a474315ba>:0
  at System.Net.HttpWebRequest.MyGetResponseAsync (System.Threading.CancellationToken cancellationToken) [0x00307] in <d054a9182977441aa432503a474315ba>:0
   --- End of inner exception stack trace ---
  at System.Net.HttpWebRequest.RunWithTimeoutWorker[T] (System.Threading.Tasks.Task`1[TResult] workerTask, System.Int32 timeout, System.Action abort, System.Func`1[TResult] aborted, System.Threading.CancellationTokenSource cts) [0x000f8] in <d054a9182977441aa432503a474315ba>:0
  at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00020] in <d054a9182977441aa432503a474315ba>:0
  at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x0000f] in <787acc3c9a4c471ba7d971300105af24>:0
--- End of stack trace from previous location where exception was thrown ---

  at System.Net.Http.MonoWebRequestHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x004ae] in <b73d7057dcc84219a589cdac327773ec>:0
   --- End of inner exception stack trace ---
  at System.Net.Http.MonoWebRequestHandler.SendAsync (System.Net.Http.HttpRequestMessage request, System.Threading.CancellationToken cancellationToken) [0x00509] in <b73d7057dcc84219a589cdac327773ec>:0
  at System.Net.Http.HttpClient.SendAsyncWorker (System.Net.Http.HttpRequestMessage request, System.Net.Http.HttpCompletionOption completionOption, System.Threading.CancellationToken cancellationToken) [0x000e8] in <b73d7057dcc84219a589cdac327773ec>:0
  at FixPluginTypesSerialization.Util.MiniPdbReader.DownloadFromWeb (System.String url) [0x00026] in <7e35fed9c5b3448891388d58e908306c>:0
  at FixPluginTypesSerialization.Util.MiniPdbReader.DownloadUnityPdb (FixPluginTypesSerialization.Util.PeReader peReader) [0x0002f] in <7e35fed9c5b3448891388d58e908306c>:0
  at FixPluginTypesSerialization.Util.MiniPdbReader..ctor (System.String targetFilePath) [0x00075] in <7e35fed9c5b3448891388d58e908306c>:0
  at FixPluginTypesSerialization.FixPluginTypesSerializationPatcher.DetourUnityPlayer () [0x0001e] in <7e35fed9c5b3448891388d58e908306c>:0
  at FixPluginTypesSerialization.FixPluginTypesSerializationPatcher.InitializeInternal () [0x00000] in <7e35fed9c5b3448891388d58e908306c>:0
  at FixPluginTypesSerialization.FixPluginTypesSerializationPatcher.Initialize () [0x00005] in <7e35fed9c5b3448891388d58e908306c>:0
[Info   :   BepInEx] Patching [UnityEngine.CoreModule] with [BepInEx.Chainloader]
[Message:   BepInEx] Preloader finished
[Message:   BepInEx] Chainloader ready
[Message:   BepInEx] Chainloader started
[Info   :   BepInEx] 5 plugins to load
[Info   :   BepInEx] Loading [LethalLib 0.16.1]
[Info   : LethalLib] LethalLib loaded!!
[Info   :   BepInEx] Loading [CSync 5.0.1]
[Info   :     CSync] CSync successfully applied patches.
[Info   :   BepInEx] Loading [Lethal Company Input Utils 0.7.7]
[Info   :Lethal Company Input Utils] Registered InputUtilsExtendedMouse Layout Override!
[Info   :Lethal Company Input Utils] InputUtils 0.7.7 has finished loading!
[Info   :   BepInEx] Loading [Interactive Terminal API 1.2.0]
[Info   :Interactive Terminal API] Game managers have been patched
[Info   :Interactive Terminal API] Interactive Terminal API 1.2.0 has been loaded successfully.
[Info   :   BepInEx] Loading [More Ship Upgrades 3.10.11]
[Info   :More Ship Upgrades] Registed sample for the enemy "centipede"...
[Info   :More Ship Upgrades] Registed sample for the enemy "bunker spider"...
[Info   :More Ship Upgrades] Registed sample for the enemy "hoarding bug"...
[Info   :More Ship Upgrades] Registed sample for the enemy "flowerman"...
[Info   :More Ship Upgrades] Registed sample for the enemy "mouthdog"...
[Info   :More Ship Upgrades] Registed sample for the enemy "baboon hawk"...
[Info   :More Ship Upgrades] Registed sample for the enemy "crawler"...
[Info   :More Ship Upgrades] Registed sample for the enemy "forestgiant"...
[Info   :More Ship Upgrades] Registed sample for the enemy "manticoil"...
[Info   :More Ship Upgrades] Registed sample for the enemy "tulip snake"...
[Info   :More Ship Upgrades] Registed sample for the enemy "bush wolf"...
[Info   :More Ship Upgrades] Registed sample for the enemy "puffer"...
[Info   :More Ship Upgrades] Registed sample for the enemy "maneater"...
[Info   :More Ship Upgrades] Items have been setup
[Info   :More Ship Upgrades] Commands have been setup
[Info   :More Ship Upgrades] Upgrades have been setup
[Info   :More Ship Upgrades] Enemies have been patched
[Info   :More Ship Upgrades] HUD has been patched
[Info   :More Ship Upgrades] Interactables have been patched
[Info   :More Ship Upgrades] Items have been patched
[Info   :More Ship Upgrades] Game managers have been patched
[Info   :More Ship Upgrades] Weathers have been patched
[Info   :More Ship Upgrades] More Ship Upgrades 3.10.11 has been loaded successfully.
[Message:   BepInEx] Chainloader startup complete
[Info   : LethalLib] Adding 0 unlockables to unlockables list
[Info   : LethalLib] Adding 2 items to terminal
[Info   : LethalLib] Found 13 prefabs to fix

This is happening to all of us, in any combination, whoever hosts and whoever joins and whatever order. Saw the other open issue, but backdating to 3.10.4. One issue I did notice the last time we played, some months ago - even on a full reinstall of LC and r2modman, when a friend and I would load into LGU, the upgrades we had on a previous save would still load in. As far as I could tell I'd deleted everything, but it seemed like there might've been some file it was still pulling from? Is there some outside location that files were saved to to keep track of upgrades and stuff in a prior version? I didn't see anything like that this time, just a thought I had of an odd issue last time.

Currently deleting R2Modman and fully reinstalling again, will update and/or close this if it fixes the issue, but it did not last time.

FixPluginTypeSerialization seems to be having a problem downloading the required data to execute correctly according to the logs you posted.

Thought that might be the case, but that error occurred identically regardless of if LGU was enabled or not - it also seemed to stop after the entire wipe and reinstall of both LC, the saves/data folder, and r2modman + cache itself, but the issue persisted, even with solely LGU + dependencies installed.

Aye, will do - didn't save that at the time, we'd eventually given up trying different things. Won't be able to send it until likely around 12h from now, but I'll post it as soon as I am able.

Also found the same issue while enabling only the mod and its dependencies. With the following logs here.
joining.txt
hosting.txt
The interesting part is if you freshly install the mod and only enable the mod, it is actually working.
But after I enabled other mods which somehow causing the joining issue (different logs from above, might occurs from mods that works with sound, not very sure), then disable all mods and enable only the lategame upgrade mod and its dependencies, the issue still persists with the uploaded logs.

Also found the same issue while enabling only the mod and its dependencies. With the following logs here.
hosting.txt
joining.txt
joining2.txt (after host disconnected)

FixPluginTypeSerialization seems to be having a problem downloading the required data to execute correctly according to the logs you posted.

Also found the same issue while enabling only the mod and its dependencies. With the following logs here.
hosting.txt
joining.txt
joining2.txt (after host disconnected)

FixPluginTypeSerialization seems to be having a problem downloading the required data to execute correctly according to the logs you posted.

Other mods using FixPluginTypeSerialization as dependency doesn't cause this issue. So, I don't know what to do about this.
Example Mods:
IAmBatby-LethalLevelLoader
Alice-ScarletDevilMansion
skidz-PoolRooms
Boniato-Ganimedes
Badham_Mods-SCPFoundationDungeon
Alice-DungeonGenerationPlus
Piggy-LC_Office
Magic_Wesley-WesleysInteriors
Zehs-WesleysInteriorsAddon
DiFFoZ-CompanyCruiserFix

Other mods using FixPluginTypeSerialization as dependency doesn't cause this issue.
Right but CSync (which is a dependency of LGU) is not executing correct behaviour (shown from the errors it throws in the provided logs) probably due to FixPluginTypeSerialization not correctly downloading the required data. Others may not use the same functionalities as CSync uses thus not showing errors.

Just for more information.
The game is working correctly enabling only dependency modes while disabling the LGU mod itself.
The only difference is probably CSync error logging?
So it might have to do with LGU tried to use CSync that failed to download the required data?
What could be the way to handle this issue though?
hosting-with-dependency-mods.txt
joining-with-dependency-mods.txt

I have also tried mods that using CSync as dependency and it seems that the issue occurs as well.
Example mods:
LethalInternship
ShipInventory

So it might have to do with LGU tried to use CSync that failed to download the required data?
What could be the way to handle this issue though?

CSync is used for LGU's Config Synchronization, yes.
Not sure, it's the first time seeing people being unable to download something for a mod. Could be either being blocked from accessing the solicited URL or it doesn't exist, there are many things.
One thing for sure is that it's a FixPluginTypeSerialization problem and not a LGU problem since it's just a dependency problem.

Edit: I have been told that using Gale mod manager makes the download issue appear and if using other mod manager like r2modman will make the issue go away. I don't know if that will solve this exact issue since this just what I heard and not what I tested.

Unfortunately, my friends and I used r2modman and still found this issue.

I have no idea then. A thing being last updated ten months ago suddenly not working sounds unlikely to be the fault of such errors.

I somehow fix it. I have the old config when the mod still working. So I copy the old FixPluginTypesSerialization config to replace to current config (newly generated) and the problem is solved.
Current Config
[Cache]

## Unity version is Major.Minor.Patch format i.e. 2017.2.1. If specified, this version will be used instead of auto-detection from executable info. Specify only if the patcher doesn't work otherwise.
# Setting type: String
# Default value:
UnityVersionOverride =

## The GUID of the last downloaded UnityPlayer pdb file.
## If this GUID matches with the current one,
## the offsets for the functions below will be used
## instead of generating them at runtime.
# Setting type: String
# Default value:<PHONE_NUMBER>00000000000000000000000
LastDownloadedGUID =<PHONE_NUMBER>00000000000000000000000

## The in-memory offset of the MonoManager::AwakeFromLoad function.
# Setting type: String
# Default value: 00
MonoManagerAwakeFromLoadOffset = 00

## The in-memory offset of the MonoManager::IsAssemblyCreated function.
# Setting type: String
# Default value: 00
MonoManagerIsAssemblyCreatedOffset = 00

## The in-memory offset of the IsFileCreated function.
# Setting type: String
# Default value: 00
IsFileCreatedOffset = 00

## The in-memory offset of the ScriptingManagerDeconstructor function.
# Setting type: String
# Default value: 00
ScriptingManagerDeconstructorOffset = 00

## The in-memory offset of the ConvertSeparatorsToPlatform function.
# Setting type: String
# Default value: 00
ConvertSeparatorsToPlatformOffset = 00

## The in-memory offset of the free_alloc_internal function.
# Setting type: String
# Default value: 00
FreeAllocInternalOffset = 00

## The in-memory offset of the malloc_internal function.
# Setting type: String
# Default value: 00
MallocInternalOffset = 00

## The in-memory offset of the m_ScriptingAssemblies global field.
# Setting type: String
# Default value: 00
ScriptingAssembliesOffset = 00

Old Config (Working)
[Cache]

## Unity version is Major.Minor.Patch format i.e. 2017.2.1. If specified, this version will be used instead of auto-detection from executable info. Specify only if the patcher doesn't work otherwise.
# Setting type: String
# Default value:
UnityVersionOverride =

## The GUID of the last downloaded UnityPlayer pdb file.
## If this GUID matches with the current one,
## the offsets for the functions below will be used
## instead of generating them at runtime.
# Setting type: String
# Default value:<PHONE_NUMBER>00000000000000000000000
LastDownloadedGUID = 8C09BC2213204B18A647FD90F53236701

## The in-memory offset of the MonoManager::AwakeFromLoad function.
# Setting type: String
# Default value: 00
MonoManagerAwakeFromLoadOffset = 76C0C0

## The in-memory offset of the MonoManager::IsAssemblyCreated function.
# Setting type: String
# Default value: 00
MonoManagerIsAssemblyCreatedOffset = 76BBF0

## The in-memory offset of the IsFileCreated function.
# Setting type: String
# Default value: 00
IsFileCreatedOffset = 00

## The in-memory offset of the ScriptingManagerDeconstructor function.
# Setting type: String
# Default value: 00
ScriptingManagerDeconstructorOffset = 781360

## The in-memory offset of the ConvertSeparatorsToPlatform function.
# Setting type: String
# Default value: 00
ConvertSeparatorsToPlatformOffset = 683330

## The in-memory offset of the free_alloc_internal function.
# Setting type: String
# Default value: 00
FreeAllocInternalOffset = 648220

## The in-memory offset of the malloc_internal function.
# Setting type: String
# Default value: 00
MallocInternalOffset = 3556D0

## The in-memory offset of the m_ScriptingAssemblies global field.
# Setting type: String
# Default value: 00
ScriptingAssembliesOffset = 1BFBA40

What do you mean by "Current Config" which config (filename)? @PureStream

@WhiteSpike
These are the logs that lead up to the originally described error, also on my machine.

It seems the link used by FixPluginTypeSerialization to download the required data was changed from HTTP to HTTPS (which makes a redirect request when attempting so) and its code doesn't support it.
I can't really do anything from LGU's perspective if something else is failing before. Either the patcher's code changes to take account redirect responses or you will have to find some configuration which downloaded the data already.

But where does one get a pre-downloaded patch configuration?

The comment below with a config seems to be working, according to the commenter.


hello-python not working

Spin version (spin --version)  spin 2.6.0 (a4ddd39 2024-06-20)
Installed plugin versions (spin plugins list --installed) No plugins found

When I tried to build hello-python on my windows machine:
Building component hello-python with componentize-py -w spin-http componentize app -o app.wasm
Traceback (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in run_code
File "D:\miniconda3\envs\spin\Scripts\componentize-py.exe_main.py", line 7, in
AssertionError: no WIT files found; please specify the directory or file containing the WIT world you wish to target
Caused by:
0: failed to read file "wit"
1: The system cannot find the file specified. (os error 2)
Error: Build command for component hello-python failed with status Exited(1)

CC @dicej might have more context about an issue like this.

Hi @abzou7275!  I'm having trouble finding a hello-python example in either this repo or the spin-python-sdk repo.  I also can't find a template with that name.  Where did you get it from?
BTW, this is a good place to start if you're new to using Python with Spin: https://developer.fermyon.com/spin/v2/python-components
And since it looks like you're using Windows, please make sure you use componentize-py 0.13.4, which includes a recent fix for building components on Windows.

Ah, perhaps you're following the Python directions on https://developer.fermyon.com/spin/v2/quickstart ?  If so, did you make sure to follow all the steps, including the pip3 install -r requirements.txt one?  If so, and you're still having issues, please post a complete list of the steps you took from the beginning, and I'll try to reproduce the issue.

I followed exact steps in the quick start https://developer.fermyon.com/spin/v2/quickstart. Except I used conda to create the virtual env. I tested in two windows machines, all have the same issue.

Would you mind trying it using python3 -m venv venv to create the virtual env?  componentize-py doesn't know how to discover the site-packages directory in a conda-based venv, so I imagine that's the problem.

Can you double-check you're using componentize-py 0.13.4 by running componentize-py --version?

yes, I am using componentize-py 0.13.4

I was able to reproduce this; will debug and report back when I have a fix.  Thanks for reporting it!

This fixes it: https://github.com/bytecodealliance/componentize-py/pull/95
I'll upload a new release once that's merged and CI finishes.

A 0.13.5 release is available with the fix.  Please let me know if that works for you.

I believe we've now verified the fix with another user - is it okay to close this issue?


Define gutter-width variable

Hi @etumyan!
Thanks for helping with improving the flexboxgrid! I like the idea of making the gutter width a variable and it looks like more people are agreeing with you (see #6). Consider this feature implemented at the end of the week!
My apologies for the late response. Updating the repository has been on my todo list for a long time, but I couldn't find the time to do this. I've already updated the grid drastically and it is easier for me to add functionality in the future.

Fixed in https://github.com/vivid-web/flexboxgrid-sass/commit/6acc05edec230842cbb45f0e1301fc472c82d3d5 and released in V5.0.2.


update root OWNERS (remove inactive, add @thesuperzapper)

This PR updates the root OWNERS to reflect the currently active and highly trusted maintainers of the website.
Regarding the approvers, the following actions are taken:

Remove anyone who has not approved a PR in many years (or who has publicly left the project)
Adds @thesuperzapper:

(NOTE: if adding me is too controversial with the remaining approvers, I am happy to make a separate PR for further discussion)

This leaves the following members:

@chensun
@james-jwu
@thesuperzapper
@zijianjoy

Regarding the reviewers, the following actions are taken:

Aligns them exactly with the approvers:

This is NOT a reflection on anyone who was removed, it's just that there is no practical reason to have root reviewers who are separate from the approvers.
This ensures PRs that make changes to something that ONLY a root approver can approve are automatically assigned to the root approvers for review.
(NOTE: root reviewers are only assigned by the bot when a file does not have a more specific OWNER reviewer)

@zijianjoy @chensun @james-jwu as you are currently the only active root owners, one of you will need to approve this.
Happy to discuss this further in the next community meeting.

I suggest we don't add new approvers at this point until we finalize the governance structure.
/hold


Git ignore ecosystem.json5

Is it possible to ignore the ecosystem.json5 file in the source repo but still deploy?
Running deploy with ecosystem.json5 ignored results in:
○ executing post-deploy `pm2 startOrRestart ecosystem.json5 --env production`
Configuration file ecosystem.json5 is missing. Action canceled.

  post-deploy hook failed

I have a project that is publicly visible on a github organisation.  Hope that makes sense.

you could copy ecosystem.json5 to a secure location on your server, then do pm2 startOrRestart /path/to/ecosystem.json5 --env production


CentOS Stream 8 is EOL

CI was failing to build ceph-csi image
#8 [updated_base 4/4] RUN dnf -y update --nobest        && dnf -y install nfs-utils        && dnf clean all        && rm -rf /var/cache/yum
#8 0.555 CentOS Stream 8 - AppStream                     490  B/s |  38  B     00:00
#8 0.563 Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
#8 ERROR: process "/bin/sh -c dnf -y update --nobest        && dnf -y install nfs-utils        && dnf clean all        && rm -rf /var/cache/yum" did not complete successfully: exit code: 1
------
 > [updated_base 4/4] RUN dnf -y update --nobest        && dnf -y install nfs-utils        && dnf clean all        && rm -rf /var/cache/yum:
0.555 CentOS Stream 8 - AppStream                     490  B/s |  38  B     00:00
0.563 Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist

CentOS 8 was EOL on 31 May 2024.
And quay.io/ceph/ceph:v18 is based on CentOS 8 stream. Probably that is the reason.
pm@dhcp53-176:~$ podman run --rm -it quay.io/ceph/ceph:v18 cat /etc/os-release
NAME="CentOS Stream"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Stream 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_SUPPORT_PRODUCT_VERSION="CentOS Stream"

Workaround for now will be to update the centos repo url. This should be removed once the base image (ceph) is updated to a version with a newer CentOS.
Originally posted by @iPraveenParihar in https://github.com/ceph/ceph-csi/issues/4658#issuecomment-2146673400

See also ceph/ceph-container#2183 and<EMAIL_ADDRESS>

The quay.io/ceph/ceph:v18 image has been updated to CentOS Stream 9. New builds won't use CentOS 8 anymore.