"Not all required packages are installed" (sklearn-crfsuite missing)

rasa NLU version (e.g. 0.7.3): latest master May 23rd
sklearn-crfsuite seem to be missing in dependencies
ERROR:root:Failed to load model 'current'. Error: Not all required packages are installed. To use this pipeline, run
	> pip install sklearn-crfsuite==0.3.5 scikit-learn==0.18.1 scipy==0.19.0
Traceback (most recent call last):
  File "/app/rasa_nlu/data_router.py", line 87, in __create_model_store
    model_store[alias] = self.__interpreter_for_model(model_path)
  File "/app/rasa_nlu/data_router.py", line 71, in __interpreter_for_model
    return Interpreter.load(metadata, self.config, self.component_builder)
  File "/app/rasa_nlu/model.py", line 226, in load
    components.validate_requirements(meta.pipeline)
  File "/app/rasa_nlu/components.py", line 110, in validate_requirements
    "> pip install {}".format(" ".join(missing_requirements)))
Exception: Not all required packages are installed. To use this pipeline, run
	> pip install sklearn-crfsuite==0.3.5 scikit-learn==0.18.1 scipy==0.19.0

No this is expected. The pip and local install cover only dependencies that we need all the time - some of the components in the processing pipelines do have additional dependencies though. If you really want to install everything, you can run pip install -r dev_requirements.txt.

Beat me to it :(
Since the RASA folks don't know which back end you will use they don't assume to install any libraries that aren't required. You can either install them selectively based on the pipeline you are using or blanket install everything with the dev-requirements file.
See the note on this page https://rasa-nlu.readthedocs.io/en/latest/installation.html#setting-up-rasa-nlu

😉

Makes sense.
I know it can be pip installed or added to the requirements.txt, but since I got this error after pulling from master without changing anything else,  I thought it might be worth reporting.
I suppose ner_crf has a new depency on sklearn-crfsuite, so since my pipeline is only ["nlp_spacy","ner_crf","ner_synonyms"]

Yes, we replaced python-crfsuite with sklearn-crfsuite.

I'm following the tutorial at https://rasa.com/docs/core/quickstart/#quickstart and when running
python -m rasa_nlu.train -c nlu_config.yml --data nlu.md -o models --fixed_model_name nlu --project current --verbose

I do get the following error
Not all required packages are installed. To use this pipeline, you need to install the missing dependencies. Please install sklearn_crfsuite

Do I need to install dev-requirements to follow the quickstart tutorial?

(venv) (base) C:\Users\achatur4\Downloads\DataScience\Rasa_basic_folder>rasa train nlu
Training NLU model...
c:\windows\system32\venv\lib\site-packages\rasa\nlu\config.py:50: FutureWarning: You are using a pipeline template. All pipelines templates are deprecated and will be removed in version 2.0. Please add the components you want to use directly to your configuration file.
return RasaNLUModelConfig(config)
Traceback (most recent call last):
File "C:\Users\achatur4\AppData\Local\Continuum\anaconda3\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "C:\Users\achatur4\AppData\Local\Continuum\anaconda3\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "C:\WINDOWS\system32\venv\Scripts\rasa.exe_main.py", line 7, in
File "c:\windows\system32\venv\lib\site-packages\rasa_main.py", line 91, in main
cmdline_arguments.func(cmdline_arguments)
File "c:\windows\system32\venv\lib\site-packages\rasa\cli\train.py", line 140, in train_nlu
persist_nlu_training_data=args.persist_nlu_data,
File "c:\windows\system32\venv\lib\site-packages\rasa\train.py", line 414, in train_nlu
persist_nlu_training_data,
File "C:\Users\achatur4\AppData\Local\Continuum\anaconda3\lib\asyncio\base_events.py", line 584, in run_until_complete
return future.result()
File "c:\windows\system32\venv\lib\site-packages\rasa\train.py", line 445, in _train_nlu_async
persist_nlu_training_data=persist_nlu_training_data,
File "c:\windows\system32\venv\lib\site-packages\rasa\train.py", line 474, in _train_nlu_with_validated_data
persist_nlu_training_data=persist_nlu_training_data,
File "c:\windows\system32\venv\lib\site-packages\rasa\nlu\train.py", line 74, in train
trainer = Trainer(nlu_config, component_builder)
File "c:\windows\system32\venv\lib\site-packages\rasa\nlu\model.py", line 142, in init
components.validate_requirements(cfg.component_names)
File "c:\windows\system32\venv\lib\site-packages\rasa\nlu\components.py", line 59, in validate_requirements
f"Not all required importable packages are installed. "
Exception: Not all required importable packages are installed. To use this pipeline, you need to install the missing dependencies. Please install the package(s) that contain the module(s): sklearn_crfsuite
I tried installing sklearn-crfsuite again but the issue persists.
In the venv I can see sklearn-crfsuite, scipy, scikit-learn installed .
scikit-image==0.16.2
scikit-learn==0.22.2.post1
scipy==1.4.1
seaborn==0.10.1
Send2Trash==1.5.0
simplegeneric==0.8.1
simplejson==3.17.0
singledispatch==<IP_ADDRESS>
six==1.15.0
sklearn-crfsuite==0.3.6
slackclient==2.7.2
smmap==3.0.4
sniffio==1.1.0
snowballstemmer==2.0.0
sortedcollections==1.2.1
sortedcontainers==2.2.2
soupsieve==2.0.1
spacy==2.1.9
Any assistance will be really appreciated


[BUG] - Cannot initialize  Quasr in fresh nuxt app

Checks

[X] I have searched the existing issues for a similar bug and it does not exist!

Environment

Operating System: Darwin
Node Version:     v20.11.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Quasar version
^2.15.4
Browsers
Google Chrome, Safari
Description
got the error
Failed to resolve import "quasar/src/directives/ClosePopup.js" from "../../../../../../../../__quasar/entry.mjs". Does the file exist?
Reproduction steps
1. install fresh nuxtjs application "nuxt": "^3.11.2"
2. install quasar-ui library
npm install quasar @quasar/extras
npm install --save-dev nuxt-quasar-ui
3. npm run dev

Screenshots
![Error Screenshot] https://i.imgur.com/the1SxZ.png

Logs
Internal server error: Failed to resolve import "quasar/src/directives/ClosePopup.js" from "../../../../../../../__quasar/entry.mjs". Does the file exist?
  Plugin: vite:import-analysis
  File: /__quasar/entry.mjs:126:40
  124|  export { default as QVideo } from "quasar/src/components/video/QVideo.js"
  125|  export { default as QVirtualScroll } from "quasar/src/components/virtual-scroll/QVirtualScroll.js"
  126|  export { default as ClosePopup } from "quasar/src/directives/ClosePopup.js"
     |                                         ^
  127|  export { default as Intersection } from "quasar/src/directives/Intersection.js"
  128|  export { default as Morph } from "quasar/src/directives/Morph.js"

FOUND OUT IT WAS MY globally installed 'quasar' module having conflict with the local package


ConsumeProduct iOS

ConsumeProduct
For android just throwing the product id ( for me it's "hb_solar") is enough
for iOS it doesn't work and I don't have an error either.
In the doc it says
//consume product id, throw away purchase product id info from server.
In iOS case, does it mean we have to use

the product id ("hb_solar")
the order id ("GPA.1234-1234-1234-12345")
the receipt id "hash string"

??
Thanks

The Apple payment system is different - I know the fovea in app purchase plugin works in testing on iOS, but it doesn't consume purchases on android from what I have been able to gather - you might consider splitting the two releases across the two plugins ? ugly I know ...
J


there is something wrong with insertFieldValue

the insertFieldValue is wrong ?
  const insertFieldValue = React.useCallback((field, index, value, options) => {
    apiRef.current.setFieldValue(
      field,
      old => {
        if (Array.isArray(old)) {
          return old.map((d, i) => (i === index ? value : d))
        } else {
          throw Error(
            `Cannot insert a field value into a non-array field. Check that this field's existing value is an array: ${field}.`
          )
        }
      },
      options
    )
  }, [])

This issue should be resolved now as of:
https://github.com/TanStack/form/pull/404


The "amazon" platform should be moved from the "rhel" to the "fedora" platform_family

Description
The "amazon" platform isn't a recompiled-rhel version and never should have been there.  At the same time it uses RPMs and is based on fedora at its core.
This is a major breaking change for 13.

Amazon Linux is really it's own thing at this point.  Originally it was sorta RHEL 5, but not really.  We should just give it the amazon platform_family and be done with it for 13.

Because if you add a new platform_family you have to add it to everywhere the others are, ie.:
./lib/chef/dsl/platform_introspection.rb:        #     [:fedora, :rhel] => "value for all known redhat variants"
./lib/chef/provider/ifconfig/redhat.rb:        provides :ifconfig, platform_family: %w{fedora rhel}
./lib/chef/provider/package/yum.rb:        provides :package, platform_family: %w{rhel fedora}
./lib/chef/provider/service/insserv.rb:        provides :service, platform_family: %w{debian rhel fedora suse} do |node|
./lib/chef/provider/service/redhat.rb:        provides :service, platform_family: %w{rhel fedora suse} do |node|
./lib/chef/provider/service.rb:        Chef.set_provider_priority_array :service, [ Systemd, Insserv, Redhat ], platform_family: %w{rhel fedora suse}
./lib/chef/resource/yum_package.rb:      provides :package, os: "linux", platform_family: %w{rhel fedora}
./spec/functional/resource/group_spec.rb:    when "debian", "fedora", "rhel", "suse", "gentoo", "slackware", "arch"
./spec/functional/resource/group_spec.rb:    when "debian", "fedora", "rhel", "suse", "gentoo", "slackware", "arch"
./spec/functional/resource/user/useradd_spec.rb:        if %w{rhel fedora wrlinux}.include?(OHAI_SYSTEM["platform_family"])
./spec/functional/resource/user/useradd_spec.rb:          if %w{rhel fedora}.include?(OHAI_SYSTEM["platform_family"])
./spec/support/shared/unit/platform_introspector.rb:      [:rhel, :fedora] => "redhatty value",
./spec/unit/dsl/platform_introspection_spec.rb:      [:rhel, "fedora"] => "redhatty value",

If we move from "rhel" to "fedora" none of that code needs to change.  And that is just the code internal to this repo.

Please WARN really loudly about this in subsequent versions of 12.x & maybe even begin supporting it in both families ahead of time (if that is possible) so folks can migrate ahead of time.

a nodes platform_family is single valued, it cannot be both.  i don't know how to warn on this usefully.  platform_family is checked half a million times in a chef-client run due to the resource and provider resolver code, throwing WARNs on access like that will obliterate the logs with noise.  trying to target only recipe is code is a) very hard and b) also prone to false positives since you want to identify a conditional taken on platform_family where "rhel" and "fedora" are not treated the same.
we accept a PR to add a warning, but unless someone steps up i think this is just going to have to be a breaking change for 13.0 that will need to be caught by testing.

Hmm. I figured that the platform_family was single valued and I see your concern about a million WARNS.
Given that, from a cookbook maintainer standpoint, I'm :+1: on @tas50's suggestion of an amazon platform family. I'd note that a lot of cookbooks already have if node[:platform] == "amazon" conditions set inside if node[:platform_family] == "rhel" blocks. That's likely to continue with a switch to fedora.
Adding the Amazon family would allow cookbook maintainers to update existing conditionals ahead of time. It would also provide more consistent behavior for cookbooks that aren't updated, as neither the rhel nor fedora conditions would be met.
I realize that adding the family is more work, but it's more accurate and better solution for users in the long run.

chef/ohai#971


add the fields for signing to crd (#91)

this add four fields to the crd in their own subsection:
FileList - a list of kmod files within the container to sign
KeySecret and CertSecret - these are the names of secrets containing the private and public keys respectivly that will be used to sign the kmods. The public key should be the one added into the uefi moklist for secureboot,
and KeySecret is its private component. (See the kernel docs e.g.
https://www.kernel.org/doc/html/v4.15/admin-guide/module-signing.html#manually-signing-modules for details of this process)
unsignedImage - the optional name of a dtk image containing the unsigned knods, used only if their is no build stage.
The expected workflow will be (not implemented in this commit): if there is only a kernelmapping.build section it will produce the image kernelmapping.containerImage (for the non-secureboot case)
if there is both km.build and km.sign then build will produce an intermediate image and sign will consume that to produce km.containerImage
if there is only km.sign signing will consumse km.sign.unsignedImage and produce km.containerImage (this is for the case where a vendor supplies prebuilt images that need signing)
the generation of the intermediate image name will be handled automatically within the controller (again in a different commit) but will probably be something like km.containerImage + "-unsigned"

/assign @ybettan

Upstream PR for cherry-pick:
https://github.com/kubernetes-sigs/kernel-module-management/commit/4c6a77d4f88fa7839ba20d80e081167196028f06

/lgtm


Update howto-vm-sign-in-azure-ad-linux.md

Added a paragraph about the HTTP proxy configuration

@MicrosoftGuyJFlo

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Expose ScopeGuard

To allow usage without lambdas. Helps with excessive right drift of the code.

Nevermind, I was looking at the wrong functions.


:meat_on_bone:

minor updates after updating npm...guh

I didn't know you could make a specific version of npm a dependency in the project. I figured that'd be outside of that object in the config.

Is this still opened?

It is still technically open. But I dont remember why I made this a PR...the only thing in here is that npm version thing, which was done automysteriously by npm....

I'm going to close for now.


Unhighlight positive category balances - text colour issue for credit card underfunding (white on yellow)

Name of Defective Feature
-Unhighlight all Positive Category Balances
System Settings (Required)

ToolKit Version: 2.12.0
Operating System (Mac/Windows/Etc): Windows
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: 75.0.3770.100
Other Extensions: N/A

Export of Toolkit Settings (Bottom Left of Settings Page)

Settings Export
[{"key":"AccountsDisplayDensity","value":"0"},{"key":"AccountsEmphasizedOutflows","value":true},{"key":"AccountsStripedRows","value":true},{"key":"AutoDistributeSplits","value":true},{"key":"AutomaticallyMarkAsCleared","value":false},{"key":"BetterScrollbars","value":"1"},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"pacing"},{"key":"BudgetQuickSwitch","value":true},{"key":"CalendarFirstDay","value":"1"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"ChangeEnterBehavior","value":false},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseSideMenu","value":false},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":false},{"key":"CreditCardEmoji","value":true},{"key":"CurrentMonthIndicator","value":true},{"key":"CustomFlagNames","value":false},{"key":"DaysOfBuffering","value":true},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"2"},{"key":"DisplayTotalMonthlyGoals","value":true},{"key":"DisplayUpcomingAmount","value":true},{"key":"EasyTransactionApproval","value":true},{"key":"EditAccountButton","value":"0"},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":true},{"key":"FilterCategories","value":true},{"key":"GoalIndicator","value":true},{"key":"GoalWarningColor","value":false},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":true},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":true},{"key":"HideTotalAvailable","value":false},{"key":"HighlightNegatives","value":true},{"key":"ImportNotification","value":"0"},{"key":"IncomeFromLastMonth","value":"1"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"LinkToInflows","value":true},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"1"},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":true},{"key":"RemoveZeroCategories","value":true},{"key":"ResizeInspector","value":true},{"key":"ResizeSidebar","value":true},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"0"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"0"},{"key":"SeamlessBudgetHeader","value":false},{"key":"SetMultipleFlags","value":true},{"key":"ShowCategoryBalance","value":false},{"key":"SpareChange","value":false},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SquareNegativeMode","value":false},{"key":"StealingFromFuture","value":true},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":true},{"key":"ToggleTransactionFilters","value":"0"},{"key":"ToolkitReports","value":true},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":false},{"key":"l10n","value":"0"}]

Steps to Reproduce the Behavior

Have a credit card in YNAB Budget that has a balance
Set a "pay off in full" goal
Turn on Unhighlight all Positive Category Balances
Remove any budgeted funds - i.e. create an underfunded credit card category

Expected Behavior
Black text on yellow warning background, as per normal behaviour (see screenshot)

Actual Behavior
white text on yellow background, which is illegible (see screenshot)

Note: the error only applies to credit card categories. Other categories behave as expected (see screenshot).

Try setting the option to use the "Balance Colors" to the "Classic". This option is on the My Account page. At some point we'll do a PR that honors these settings but that could take some time.

The white-on-yellow issue seems to persist no matter whether it's on
default or classic colours, unfortunately.
On Mon, 1 Jul 2019 at 09:18, David Baldon<EMAIL_ADDRESS>wrote:

Try setting the option to use the "Balance Colors" to the "Classic". This
option is on the My Account page. At some point we'll do a PR that honors
these settings but that could take some time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/toolkit-for-ynab/toolkit-for-ynab/issues/1596?email_source=notifications&email_token=AMPTTAK5NOVWOVHNU7TZHYLP5E5LXA5CNFSM4H4MWCGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY4VXPA#issuecomment-507075516,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMPTTAKBXSDVUVYTAWZVPILP5E5LXANCNFSM4H4MWCGA
.

I have also had this for some time. It only seems to affect one of my two credit cards I have defined. When the credit card is paid off in full with zero balance it shows yellow with a white font.


Variable referred to by the wrong name - Waypoint: Iterate over Arrays with map

In Waypoint: Iterate over Arrays with map it says: Use the map function to add 3 to every value in the variable array.
The only variables in the program are oldArray and newArray. It should say:
Use the map function to add 3 to every value in the variable oldArray.

I submitted a pull request to fix it: 4615


ircText config seems to do nothing

It still uses the default <user> message format despite me setting it to {$displayUsername}: {$text}

Nevermind apparently I missed the fact it was supposed to be wrapped in a format


test ci

test ci DNM

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


Idea: No Notifs

Ability to have invisible function similarly to Do Not Disturb, in which you won't receive notifications (or the sounds for them).

Hi, this repo is now beginning to be deprecated so please make an issue in this repo for Module Store v2 instead. Thanks.

Oh, didn't see it. Thank you.

No worries, thank you too.


Guest Access in Teams in GCCH

Please update this page to include that guest access in GCCH is in fact available across cloud.
[Enter feedback here]

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

ID: 5f080a5c-4268-1db4-566f-f1edc27920b5
Version Independent ID: ac556a92-58af-3e05-f53b-0fc00afc96c0
Content: Use guest access and external access to collaborate with people outside your organization - Microsoft Teams
Content Source: Teams/communicate-with-users-from-other-organizations.md
Service: msteams
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Hello @J227668
How are you?
It says here https://www.microsoft.com/en-ww/microsoft-365/roadmap?filters=&searchterms=teams%2Cguest%2Ccross it will roll out this month.
I see you are a Microsoft employee, can you please confirm this is rolled out for all tenants so we can push an update to the article?
Thank you,

@J227668 Were you able to see my comment here? thanks

We appreciate any feedback that improves the content in the Microsoft docs but we haven't had any response from you so we are going to close this issue.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Add Decorator for Components from the metamodel. Closes #3

It might be nice to generate icons using the following schemdraw.

@brollb suggested not to hardcode meta-node Concepts with the decorator. So, an alternative should be followed.


Conflict with Firebase

Hello
As soon as I add "pod 'Google-Maps-iOS-Utils'" to my Podfile, I start getting "'FirebaseAuthInterop/FIRAuthInterop.h' file not found".
Has anyone else seen this?
Thanks
Sam

So I learned a little something.  I ran 'pod try Google-Maps-iOS-Utils' and ran the sample 2.  Everything ran fine until I realized that the target iOS env that the sample project uses is 7.0.  As soon as you upgrade ie change SwiftDemoApp->General->Deployment Info->Deployment Target to 12.1, everything starts to act crazy.  The sample is still using Swift 3 which is deprecated.

Any love on this?

Is this project supported at all?


pathToElectron.endsWith is not a function

I read the Electron doscs + the README file in @electron/fuses.
First time I try to ue the Fuses so I assumed the example shown in the readme is code within the main process file.
Problem: it throws exception and I cannot use the fuses.
// main.js
'use strict';
console.time('init');

if (require('electron-squirrel-startup')) {
    //https://www.electronforge.io/config/makers/squirrel.windows#my-app-is-launching-multiple-times-during-install
    return;
}

(async () => {
    const {flipFuses, FuseVersion, FuseV1Options} = require('@electron/fuses');

    await flipFuses(
        require('electron'), // Returns the path to the electron binary
        {
            version: FuseVersion.V1,
            [FuseV1Options.EnableNodeOptionsEnvironmentVariable]: false, // Disables the NODE_OPTIONS environment variable
            [FuseV1Options.EnableNodeCliInspectArguments]: false, // Disables the --inspect and --inspect-brk family of ClI options
            [FuseV1Options.OnlyLoadAppFromAsar]: true // Enforces that Electron will only load your app from "app.asar" instead of it's normall search paths
        }
    );
})();

console.timeEnd('init');

Error log: `
init: 38.898ms
(node:4524) UnhandledPromiseRejectionWarning: TypeError: pathToElectron.endsWith is not a function
at pathToFuseFile (C:\Users\Alex\localdev\finance-d-electron\node_modules@electron\fuses\dist\index.js:48:24)
at setFuseWire (C:\Users\Alex\localdev\finance-d-electron\node_modules@electron\fuses\dist\index.js:57:26)
at exports.flipFuses (C:\Users\Alex\localdev\finance-d-electron\node_modules@electron\fuses\dist\index.js:108:19)
at C:\Users\Alex\localdev\finance-d-electron\src\main\main.js:12:11
at Object. (C:\Users\Alex\localdev\finance-d-electron\src\main\main.js:21:3)
at Module._compile (node:internal/modules/cjs/loader:1116:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1169:10)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:829:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
(Use electron --trace-warnings ... to show where the warning was created)
(node:4524) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on
unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
`
How are we meant to use this?
Could you please provide just a little more context around where and when to use the fuses properly?
I don't think I am getting this right.
Thank you very much in advance

Yes! I definitely assumed this too. What I think the intention is, is that you are supposed to set the fuses on the binary after it has been built (or maybe after you have installed Electron? I'm not sure). I think the example in the README is supposed to be in a separate file that gets executed at the end of the build process. The README should be more clear about this.
Can somebody please verify that this is correct?

Haven't tested yet, but looks like correct usage: https://github.com/electron-userland/electron-builder/issues/6365#issue-1033809141

@Slapbox is correct, this script should be run during your packaging process. Not at runtime


Question about optimization options of clang

Could I asked  a question. GCC is used as the optimization option in the original code. The paper also conducted experiments on llvm optimization options. What specific optimization options are used?

Thank you very much for your interest in our paper and for being prepared to try out BinTuner!
BinTuner is an auto-tuning framework, which can deliver a near-optimal binary code that reveals much more differences than -Ox settings.
That means you can feel free to add any option to extend or modify the array FLAGS = ['reorder-blocks', 'reorder-functions',  'inline-functions', 'unswitch-loops'] in the main.py program depending on the compiler version. Please note that different compiler versions may support different options, make sure that the choices you add are a match for the compiler you configured (for iterative compilation), otherwise you will get compilation errors.
For clang, please refer to the configuration methods under main_clang.py, for example, LLVM_FLAGS_fno = ['blocks', 'borland-extensions', 'delayed-template-parsing', 'fast-math',], LLVM_FLAGS_mno = ['backchain', 'incremental-linker-compatible', 'global-merge'], LLVM_FLAGS_On = ['gnu-runtime', 'stack-protector-all'], LLVM_FLAGS_Off = ['sanitize-blacklist', 'crash-diagnostics'], there are very detailed configuration methods and use cases here. https://github.com/BinTuner/Dev/blob/main/BinTuner/examples/gccflags/main_clang.py To double check before running to make sure the paths to all program (you will compile) files needed to compile are configured, otherwise you will get compilation errors and failures.
In addition, we use Z3 Prover to analyze all generated optimization option sequences for conflicts and make changes to conflicting options for greater compiling success. For more details, please refer Z3Prover.
Thanks again for your interest and feedback!


config changes in github ci workflow for artifact files

@AloisKraus, The task is completed and can be closed


Gift of Hateful Retribution cost

Gift of hateful retribution is granted by sourcerer as your base class as an option. When upgrading to a higher tier of Gift of Hateful Retribution, you are just supposed to pay for the difference in cost between the two, but it charges the difference in cost +1
e.g. if I'm a sourcerer, going from Gift of hateful retribution rank 1 to gift of hateful retribution rank 4, it should cost me 3cp, but it costs me 4.

The character engine is stateless, so it doesn't know the order in which bonuses and purchases are acquired. So for perks with varying costs, I had to decide which ranks to apply bonuses to. It seemed at the time like as though ranks tended to get more expensive as you went up, so I made the bonus always apply to the top-most ranks, but this actually varies. I think GoHR is the only one that has the bottom rank as the most expensive.
I suppose the engine will need to be more flexible about how it optimizes bonus rank assignment.


How to compile the source code? How do I reference source code in my project?

macOS
iOS platform
Thanks

Please see the file BUILDING.md for all the information on how to compile Filament.

Please see the file BUILDING.md for all the information on how to compile Filament.

Hello, I was able to compile all the static libraries with build.sh.
I want to use the source code into our project.
No solution was found in building.md.

The easiest thing would be to invoke our CMake files from your build.


Region aria correction

I found 3 page templates without <main>:
http://localhost:8000/de/blog/2022-02-02-cwa-2-17/
http://localhost:8000/de/science/2021-10-15-science-blog-4/
http://localhost:8000/error.html
Can you please make sure these 3 layouts have a <main> area added as well? Thanks a lot!

Changes approved, thanks @ibexad !


Ignore tasks defined outside of Task module

This changes the gem to only consider Tasks (MaintenanceTasks::Task subclasses) defined in the MaintenanceTasks.tasks_module (Maintenance by default).
Previously it was possible to define a Task anywhere:

It wouldn't show in the list by default in development (the constant would not have been loaded).
It would show in production though.
In any case it was possible to access the task URL directly and start running.
Running would work normally.

I think the first point in particular is not ideal, and we have no way of finding all the subclasses without knowing where to look for them when eager loading is not on.
With these changes:

Accessing the URL directly doesn't work.
Running will cause a validation error (using Runner or the command line).

This is a breaking change but it's also a use case that wasn't supported so I think it's OK to do this.

Actually we want to support multiple modules instead of enforcing one.


Merging master into devel to avoid compilation issues due to Eigen

@GiulioRomualdi if you agree we can merge


Bug: DNS Check can never use targets supplied by target manager

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Currently, targets supplied by targetmanager to the dns check fail the validation and cannot be registered. This is because the targets include a scheme like http or https, which the dns checks config validation will reject.
Expected Behavior
Sparrow should "just work", i.e. just parse the url and throwaway everything that is not the domain name
Steps To Reproduce

Run sparrow with targetmanager enabled and configured.
Configure a dns check
Add a targetmanager remote target with a https scheme
Check logs

Relevant logs and/or screenshots, environment information, etc.
{"time":"2024-06-06T13:19:38.257569916Z","level":"ERROR","source":{"function":"github.com/caas-team/sparrow/pkg/sparrow.(*ChecksController).Reconcile","file":"/home/runner/work/sparrow/sparrow/pkg/sparrow/controller.go","line":100},"msg":"Failed to create checks from config","error":"invalid configuration field \"targets\" in check \"dns\": target URLs must not start with 'https://' or 'http://'"}

Who can address the issue?
No response
Anything else?
No response

I'm going to create a temporary hacky fix for this, by just overwriting the name in the config validation. This will be very ugly, but we need this fixed now. Later on, this should be refactored and a more permanent solution should be implemented instead of this mess :/

Turns out I didn't have to do that, the issue was actually in the enrichTargets function. I'm writing a pull request right now, so you guys can have a look at it


How to add new peers to the existing org

What would you like to be added?
Want to add new peers like if I have 2 peers in an existing org then I can add another one or two peers so I can join them to a different channel.
Why is this needed?
I was looking doc of bevel-operator-fabric however I am unable to find anything on how to add new peers to the existing org. could you please help me how to get it?
Thanks

Follow these step

Register the identities for new peer
Create the peer node
join the peer to the channel

After Registering a peer, I try to Deploy the peer but it throws me some error :
[$ kubectl hlf peer create --statedb=couchdb --image=$PEER_IMAGE --version=$PEER_VERSION --storage-class=standard --enroll-id=peer --mspid=Org1MSP
--enroll-pw=peerpw --capacity=5Gi --name=org1-peer0 --ca-name=org1-ca.default
--hosts=peer0-org1.localho.st --istio-port=443
W1101 12:43:08.129100   13521 warnings.go:70] unknown field "spec.gatewayApi"
W1101 12:43:08.129129   13521 warnings.go:70] unknown field "spec.secret.enrollment.component.external"
W1101 12:43:08.129135   13521 warnings.go:70] unknown field "spec.secret.enrollment.tls.external"
Error: FabricPeer.hlf.kungfusoftware.es "org1-peer0" is invalid: [spec.tag: Invalid value: "": spec.tag in body should be at least 1 chars long, spec.image: Invalid value: "": spec.image in body should be at least 1 chars long]
As I am following this documentation : [https://hyperledger.github.io/bevel-operator-fabric/docs/getting-started/]

Hi @vigneshbalu96, did you set the $PEER_IMAGE before creating the peer node?


Update 1.3

https://github.com/HenryQuan/AnimeGo-Re/issues/24

Removed macOS, Windows, Web

This can be merged after this final testing


Donation crud components

Refines layout, adds color palette, adds Navbar Drawer with styled links, adds logos to header and Landing Page, adds styling and links to footer, adds donations table with static data conditionally rendered by dummy user (added at app level), and adds donations form.
Landing Page

Landing page with Color Palette and full Donations Table

Donations Page dashboard

Donations Form on Donations dashboard

Amazing!!!


Any performance issues or cons if combined?

If we have for example 7 forms - it is 14 store keys. I want to combine it into forms key:
forms: combineReducers({
  user: ...
  userForm: ...
  ...
})

Are there any cons of doing this (performance or smth else) ?

I don't believe so! They're all just functions and I think the performance impact would be minimal.

Awesome, then I'll be using RRF this way. Thanks!


feat: added WIP flag to feeds

Summary:
This pull request introduces visibility restrictions for work-in-progress (WIP) feeds in feeds_api_impl.py and search_api_impl.py, based on user email domains. It includes a new function to determine if a user’s email is restricted, updating query filters accordingly to enforce feed visibility rules. Additionally, a new SQL script is included to update the database schema and refresh the materialized view to support these changes.
Expected Behavior:
Feeds marked with an internal status of "WIP" are only visible to users with email domains ending in @mobilitydata.org. Users with other domains will not see these WIP feeds.
Testing Instructions:

Set up a local database and run the populate script.
Update the internal status of selected feeds to "WIP" in the database.
Run the API locally.
Make requests to the gtfs, gtfs_rt, and feeds endpoints, as well as the search functionality, while setting the x-goog-authenticated-user-email header to emails ending with both @mobilitydata.org and<EMAIL_ADDRESS>domains.
Verify that only users with @mobilitydata.org emails can view WIP feeds.

Testers are encouraged to follow these instructions but are also welcome to explore other test cases to ensure robust behavior outside the listed scenarios.
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with ./scripts/api-tests.sh to make sure you didn't break anything
[ ] Add or update any needed documentation to the repo
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

Integration tests are expected to fail as this issue introduces changes to the database schema

Integration tests are expected to fail for this PR due to changes in the database schema. Specifically, the error encountered is:
psycopg2.errors.UndefinedColumn: column feed.operational_status does not exist
LINE 1: ...ed_contact_email, feed.provider AS feed_provider, feed.opera...

View full logs for additional details.

This makes sense. When we added the integration tests pointing to QA, we predicted that in cases of schema changes, this step would fail as a guardrail for merging. However, it is still a great check for PRs that don't introduce a schema change on the main tables.


Dependencies from imports are not generated correctly in Python Dataclasses

Running pipenv run gen-py-classes kgcl.yaml > kgcl.py generates the desired kgcl.py file.
However, import dependencies from the modules ontology_model and prov are not generated correctly.
For example, instead of about_edge: Optional[Union[dict, Edge]] = None I find about_edge: Optional[Union[dict, "Edge"]] = None.

Running pipenv run gen-py-classes --no-mergeimports kgcl.yaml > kgcl.p resolves the dependencies correctly.

It looks like merging the imports resolved the issue - but it's not clear there was an issue, it's valid to declare the python type as a string, this is common practice for forward referencing


feat: optional save list metadata to p2p

Signed-off-by: Jim Ma<EMAIL_ADDRESS>
Description

Related Issue

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.

Codecov Report

Merging #1822 (4cf2882) into main (3786370) will decrease coverage by 0.48%.
The diff coverage is 10.48%.

@@            Coverage Diff             @@
##             main    #1822      +/-   ##
==========================================
- Coverage   43.74%   43.26%   -0.49%
==========================================
  Files         128      129       +1
  Lines       16032    16282     +250
==========================================
+ Hits         7013     7044      +31
- Misses       8480     8697     +217
- Partials      539      541       +2

Flag
Coverage Δ

Object-compatibility-e2etests
?

e2etests
?

unittests
43.26% <10.48%> (-0.49%)
:arrow_down:

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

Impacted Files
Coverage Δ

client/config/peerhost.go
33.07% <ø> (ø)

pkg/source/header.go
42.85% <ø> (ø)

pkg/source/source_client.go
9.78% <ø> (+7.60%)
:arrow_up:

pkg/source/list_metadata.go
5.20% <5.20%> (ø)

client/daemon/rpcserver/rpcserver.go
48.39% <8.39%> (-8.23%)
:arrow_down:

client/daemon/storage/local_storage.go
30.14% <45.00%> (+0.03%)
:arrow_up:

client/daemon/transport/transport.go
47.65% <100.00%> (ø)

scheduler/service/service.go
77.19% <0.00%> (-1.11%)
:arrow_down:

scheduler/resource/seed_peer.go
16.66% <0.00%> (-0.81%)
:arrow_down:


Terminate Event Cannot be Re-Enabled after Disabling

I was able to configure my vmss to pick up terminate events via the Azure Rest API call. It appears that after you enable it if you disable by changing enable to false in the payload of the API call you cannot re-enable after doing so. So, on my scale set, I enabled terminate events, disabled, and I am unable to re-enable the scale set to get terminate events.
API Call Payload To Enable (this initially worked and subsequent calls to re-enable do not):
{ "properties":{ "virtualMachineProfile":{ "scheduledEventsProfile":{ "terminateNotificationProfile":{ "notBeforeTimeout":"PT15M", "enable":true } } } }, "location":"eastus" }
API Call Payload To Disable:
{ "properties":{ "virtualMachineProfile":{ "scheduledEventsProfile":{ "terminateNotificationProfile":{ "notBeforeTimeout":"PT15M", "enable":false } } } }, "location":"eastus" }
I know the API call is correct and working because I have been able to enable terminate events on multiple scale sets by using it.
After running the api call I make a powershell call to:
Get-AzVmss -ResourceGroupName "redacted" -VMScaleSetName "redacted"
After enabling and running that command I would expect to see:

Instead after attempting to re-enable I see this when executing the call to get vmss info:

The scheduledEventProfile never gets reset with another value after attempting to re-enable.
Docs for Enabling Terminate Notification: https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification

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

ID: 435c7f55-11e0-202d-cc7a-6f636f0c2a11
Version Independent ID: 31cac987-8d27-5f7b-2cf6-c7b6b0edee48
Content: Terminate notification for Azure virtual machine scale set instances
Content Source: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification.md
Service: virtual-machine-scale-sets
GitHub Login: @shandilvarun
Microsoft Alias: vashan

@ThunderHorse Thanks for the feedback. We are actively investigating and will get back to you soon.

@shabanovanton do you know if this is a currently known limitation? I know this feature is in preview but if we are not aware of this it would be worth looking into.

Have no clue:) why asking me?:)

Sorry @shabanovanton for some reason you are listed as the author of this doc. I will get that update :)
Adding @shandilvarun to help :)

@shandilvarun do you know if this is a currently known limitation? I know this feature is in preview but if we are not aware of this it would be worth looking into.

@ThunderHorse
I tried to find an example of what you are reporting.
I see some usage where scheduled events are enabled, and then disabled in the VM Scale Set API, and looking at the current state of the system I see that after enable - disable - enable the terminate notifications appear to be enabled.
I think to investigate this issue in more detail I need the resource details where you were testing this.
Can you please email me at szimmer [at] microsoft.com with the following details

SubId
resource group name
Vmss Name
Time you attempted this enable - disable -reenable
How you are issuing the enable / disable (powershell, cli, some client library?) and the command you used

thanks @szimmerMicrosoft !
@ThunderHorse please send the email with the requested details. You can also include me mimckitt [at] microsoft.com
I will close this and we can continue offline. We we end up needing to add any notes to the doc I will reopen and do so.

@szimmerMicrosoft , this should be reproducible on any scale set. I will email you details but you shouldn't need them.  @MicahMcKittrick-MSFT please open this issue back up it is not yet resolved.

@ThunderHorse we tested this but were not able to reproduce the issue you are seeing. Hence, we can continue it offline. And this issue will still be visible on the doc regardless of if it is open or closed.

@MicahMcKittrick-MSFT, Ok, I sent the email over earlier today. I look forward to your response.
@szimmerMicrosoft

@ThunderHorse I was able to repro the issue, thanks for providing the details, and thank you for reporting this issue.
I identified the bug. We execute the update on the server side, but if that is the only change we are making we forget to persist it :^ (.
The fix should be rolled out globally in the next month, if you need to work around this in the meantime if you update an unrelated property while applying the reenable scheduled events (such as changing a tag, or making any other change) then the update should be applied.

@szimmerMicrosoft would it make sense to add a note to the doc about the work around? Or leave it as is and users can reference this issue if they encounter an issue?

I think this thread is good enough for now.
This feature does not have high usage, and this is a niche issue I think.

@szimmerMicrosoft , @MicahMcKittrick-MSFT,   Thank you both for looking into this issue!

@szimmerMicrosoft , I attempted this today by changing a tag as recommended and also by adding a new tag in a second attempt. It does not appear that I can re-enable this way. Were there any other properties that may work for this? Here is an example of my payload:
{
"properties":{
"virtualMachineProfile":{
"scheduledEventsProfile":{
"terminateNotificationProfile":{
"notBeforeTimeout":"PT5M",
"enable":true
}
}
}
},
"location":"westeurope",
"Tags":{
"newTag":"blah"
}
}

@ThunderHorse I took a look at your operation -- from the logs it looks like you need to update some other property within the virtualMachineProfile, for us to persist the scheduledEventsPolicy in the virtualMachineProfile
You could add a custom script extension which does nothing ( or any other extension_
You could update any networking settings (unfortunately I do not have a recommendation here for a harmless network setting).
You could also update your password, or customData (if you are using linux).

Updating a path on a powershell script extension allowed me to re-enable.
Thanks @szimmerMicrosoft

@ThunderHorse  Great.
We are still on track to complete the rollout he fix by end of next week

@ThunderHorse Thanks again for your feedback on this feature.
Terminate events have left Preview and are now GA if that is something that would influence your adoption.


Adding jobs to a batch throws Redis::pipeline(): Can't activate pipeline in multi mode

Laravel Version: 8.36.2
PHP Version: 8.0.3
Database Driver & Version: -

Description:
From within a queued job I want to create a new batch processing job:
$batch = Bus::batch([])
            ->allowFailures()
            ->finally(function () use ($campaign) {
               ...
            })
            ->name($campaign->getBatchName())
            ->onQueue(...)
            ->dispatch();

Once I am adding jobs to this batch
$batch->add(...);
I receive the exception
{
    "class": "Symfony\\Component\\ErrorHandler\\Error\\FatalError",
    "message": "Redis::pipeline(): Can't activate pipeline in multi mode!",
    "code": 0,
    "file": "/var/www/versions/current/vendor/laravel/framework/src/Illuminate/Redis/Connections/PhpRedisConnection.php:402"
}

Horizon is running on its own redis connection. Not the default on. Dispatching jobs from within jobs works fine. Just using the batch function does not.
I believe it to be a bug, as apparently the redis connector is trying to use two different redis modes both established by 1st party laravel packages.
Thank you :)

So when I change the line in PhpRedisConnection.php:402 from
$pipeline = $this->client()->pipeline();
to
 $pipeline = $this->client()->multi();
all issues are gone. The batch processing seems to switch to pipeline mode even though a multimode is already open, which seems to not be allowed. Eventually this happens at
src/Illuminate/Queue/RedisQueue.php:97
 public function bulk($jobs, $data = '', $queue = null)     {         $this->getConnection()->pipeline(function () use ($jobs, $data, $queue) {             $this->getConnection()->transaction(function () use ($jobs, $data, $queue) {                 foreach ((array) $jobs as $job) {                     $this->push($job, $data, $queue);                 }             });         });     }

Where do you actually call $batch->add() in your example code?

The batch is created from within a queued job:
public function handle()
    {
    $batch = Bus::batch([])
            ->allowFailures()
            ->finally(function () {
                // ...
            })
            ->name($this->batchName)
            ->onQueue('mail')
            ->dispatch();
    // ...
    foreach($this->models as $model){
        $batch->add([new CreateInvitationJob($model)]);
    }
}

The redis exception is thrown at $batch->add.

@themsaid do you have any ideas on this?

@seabass86  I can't replicate the issue on PHPRedis or Predis. Adding jobs to an existing batch works fine. Haven't seen any similar reports either.

@seabass86 since there's no clear way to reproduce this I'm going to close this one. If you have specific steps to reproduce feel free to open a new issue.

I was able to reproduce this. Occurs when you have two Redis connections for the same server (even if the database is different), so, at some point, he tries to activate the pipeline mode in a connection the already started using another mode.
If you have just one connection, this never happens.
Fun fact: The issue only occurs when using the phpredis extension. With predis all goes fine.

@KennedyTedesco did you ever found a fix/resolve this problem? :-)

@robbinjanssen I don't remember what I did to deal with this, but I'm confident that updating PHP, Redis, and phpredis to the last version probably fixed my issue. I don't remember the last time I saw this issue. But, indeed, it was a real issue back then.

It happens when you set after_commit = true in database.php for redis
'redis' => [             'driver'       => 'redis',             'connection'   => 'horizon',             'queue'        => env(key: 'REDIS_QUEUE', default: 'default'),             'retry_after'  => 10,             'block_for'    => null,             'after_commit' => true,         ],


Wait for each parallel build individually so that errors get properly

propagated
Change-type: patch
Signed-off-by: Giovanni Garufi<EMAIL_ADDRESS>

@balena-ci retest


Updated frontend/backend tests

Description
This PR includes the following proposed change(s):

Updated tests on CSO account endpoint
Updated frontend tests

Type of change

[x] New tests (non-breaking change which adds tests)

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
On localhost in demo mode.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code

-50 DKP for PR during sprint planning


add reducer

Current coverage is 91.04% (diff: 90.90%)

Merging #8 into master will decrease coverage by 0.33%

@@             master         #8   diff @@
==========================================
  Files             3          3
  Lines            58         67     +9
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits             53         61     +8
- Misses            5          6     +1
  Partials          0          0

Powered by Codecov. Last update e5bc185...b179b17


Tests disappearing and not reappearing

If I click on Hide tests, tests disappear.
Then, if I click on the code lens, tests do not reappear.

This is actually how VSCode works.
If you choose to hide some tests, then they will be hidden from view. They are still on the list, but they are not shown by default.
You can click on Show hidden tests, and then you can see the list again.
You can select the ERCx tests and click on Unhide Tests and you are back to normal.
I can't find a way to unhide the tests programmatically so I'm closing this issue with no further action.


IllegalStateException: jsonObject["default-gamemode"] must not be null

PerWorldInventory-KT dev 50
Testing KT version with PWI 1.x files / conversion.
[15:37:03] [Server thread/WARN]: [PerWorldInventory] Task #125 for PerWorldInventory v2.0.0 generated an exception
java.lang.IllegalStateException: jsonObject["default-gamemode"] must not be null
	at me.ebonjaeger.perworldinventory.GroupManager$loadGroups$1$$special$$inlined$use$lambda$1.invoke(GroupManager.kt:108) ~[perworldinventory-kt-2.0.0.jar:?]
	at me.ebonjaeger.perworldinventory.GroupManager$loadGroups$1$$special$$inlined$use$lambda$1.invoke(GroupManager.kt:16) ~[perworldinventory-kt-2.0.0.jar:?]
	at me.ebonjaeger.perworldinventory.service.BukkitServiceKt$sam$Runnable$7e5632db.run(BukkitService.kt) ~[perworldinventory-kt-2.0.0.jar:?]
	at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftTask.run(CraftTask.java:63) ~[patched_1.12.2.jar:git-Paper-1410]
	at org.bukkit.craftbukkit.v1_12_R1.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:415) [patched_1.12.2.jar:git-Paper-1410]
	at net.minecraft.server.v1_12_R1.MinecraftServer.D(MinecraftServer.java:833) [patched_1.12.2.jar:git-Paper-1410]
	at net.minecraft.server.v1_12_R1.DedicatedServer.D(DedicatedServer.java:427) [patched_1.12.2.jar:git-Paper-1410]
	at net.minecraft.server.v1_12_R1.MinecraftServer.C(MinecraftServer.java:767) [patched_1.12.2.jar:git-Paper-1410]
	at net.minecraft.server.v1_12_R1.MinecraftServer.run(MinecraftServer.java:665) [patched_1.12.2.jar:git-Paper-1410]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_172]

As a note, both of your worlds configuration related issues will be resolved with the move back to YAML. Yay beta software! Ugh.

@mibby could you try the latest beta release here and report if the issue is resolved?

Using the latest build, and everything seems to be working fine now.

Going to close this as it indeed seems to work. If this is in error, please re-open the issue.

Apologies for the late reply. Seems to be working without error now. Thanks!


Do not use SETLENGTH

Close #209.
cf. https://fosstodon.org/@shikokuchuo/112325582047868252
But, the implementation is not efficient. Probably manual Rf_allocVector() + memcpy should faster. Or, maybe I can just collect() into a Vec first?
https://github.com/r-devel/r-svn/blob/faa2ca57cc03c26c49a5de39db980268c6c4cc67/src/main/builtin.c#L832C6-L832C17
Anyway, let's think about it later. I'd like to get rid of the CI error for now.

Current status: this implementation is not correct about unprotecting the old one and protecting the new one.

I'm not sure I like this implementation, but let's go ahead and revisit here when it's necessary.


FancyZones not usable

Hi, I'ver tried to get this running for 30 Minutes now. I consider this as much time if one only want to use split screen functions. I can see the split screen, but cannot find out how to arrange open windows accoring to the split screen. I would expect that if you draw a window in a Zone using drag&drop that the zone gives visual feedback and that I can just let the window go there by "unclicking" the left mouse button. But unfortunetly nothing happens.
This is anoying when time is money ... simple function should be easy and intuitive...
Sorry ;-)
ℹ Computer information

PowerToys version:
PowerToy Utility:
Running PowerToys as Admin:
Windows build number: [run "winver"]

📝 Provide detailed reproduction steps (if any)

…
…
…

✔ Expected result
What is the expected result of the above steps?
❌ Actual result
What is the actual result of the above steps?
📷 Screenshots
Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form

Do you hold shift while dragging the window?

@nschlimm
https://docs.microsoft.com/en-us/windows/powertoys/fancyzones

Thanks. But I cannot place windows in zones on my machine. It just shows the layout but I cannot „drag&drop“ open windows in
Viele Grüsse,
Niklas Schlimm
Hufer Weg 61
51467 Bergisch Gladbach
Tel.: 02202/2492942
Fax: 02202/2492941
Mobil: 0175/2070321
e-Mail<EMAIL_ADDRESS>
Am 15.02.2021 um 10:42 schrieb Enrico Giordani<EMAIL_ADDRESS>
@nschlimm
https://docs.microsoft.com/en-us/windows/powertoys/fancyzones
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Works.  I’m not saying I read the Manual super concentrated but just the way I Always do.
Thanks again, anyway. Looks really cool and is exactly what I was Looking for !
Gesendet von Mail für Windows 10
Von: Aaron Junker
Gesendet: Montag, 15. Februar 2021 09:27
An: microsoft/PowerToys
Cc: Niklas Schlimm; Author
Betreff: Re: [microsoft/PowerToys] FancyZones not usable (#9718)
Do you hold shift while dragging the window?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

No. With your new OOBE we will better explain to the users how to use FancyZones


NSIS Custom String Internationalization

See LangString.

Hi @evshiron , how could I use this feature, since there is no nsi thing exposed to me in the demo app.

Sorry it's not implemented at the moment and I am still considering what this should look like.
The idea came to me when I wrote some English strings in the generated scripts, which looked quite uncomfortable when used in installers of other languages.
The original idea is to add some LangString for some languages for these strings, but it has low priority until someone requests for it.
As it isn't implemented yet, I want to know why you want this feature and what's your expectation for it, so I can start with an overall idea. Thanks.

https://github.com/evshiron/nwjs-builder-phoenix/tree/nsis-i18n
I made a prototype here, hopefully you can clone and npm install, try it out and see if it helps in your cases. If you have other ideas please share with me :)


Make WordNet's synset relations available from the lemmas

Fix #1970: make WordNet's synset relations available from the lemmas.
from nltk.corpus import wordnet as wn
insect = wn.lemmas("insect")[0]
print(insect.hypernyms())

[Synset('arthropod.n.01')]

The in_topic_domain() relation ("-c") is hybrid, because a few lemmas have both lemma and synset targets. For ex:
print(insect.in_topic_domains())

[Lemma('chirpy.a.01.chirpy'), Synset('holometabolism.n.01')]

This needs more work in order to return the lemmas of the synset targets, as in the last example from this comment by @marcevrard.
Alternatively, depending on the consensus, the relation definitions  could be moved from the WordnetObject class to the Synset class.

@ekaf I believe it is more important to maintain the conceptual distinction between synsets (senses) and lemmas (forms).


Fix return value annotations for methods returning copies

These methods always return a new object of the same type as the object they are bound to, even if this is a subclass. Change the annotations to reflect that.
I have not opened an issue, because it's not a functional bug. It just causes issues with static type checkers.

Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change. (N/A)
[ ] Add or update relevant docs, in the docs folder and in code.  (N/A)
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs. (N/A)
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

The pre-commit failure is not related to the changes in the PR and also happens with the current state of the branch.


Fix Typing for strategies.ddp

What does this PR do?
Part of #11371 and #7037.
add important words
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
yes?! 🙃

This is done alreayd. Thanks for your contribution!


Running database/webots-cloud.sql gives syntax errors

Describe the Bug
Running database/webots-cloud.sql on a blank MySQL database gives three syntax errors:

a duplicate column error:

(Duplicate column name 'viewed')
Lines 39 and 48 both create the same viewed column. Deleting line 48 and the comma at the end of line 47 seems to solve the error.

two additional syntax errors:

(You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MODIFY `id` int(11) NOT NULL AUTO_INCREMENT' at line 1)
Replacing the semicolons at the end of lines 53 and 105 with commas seems to solve these errors.
Steps to Reproduce

Create a new MySQL database
source the file webots-cloud.sql in the MySQL console
Errors pop up during the execution of the file

Expected behavior
The script should configure the database without any errors.
System

Ubuntu 22.04
MySQL ver 8.0.32-0ubuntu<IP_ADDRESS> for Linux on x86_64 ((Ubuntu))

Thank you @moneylobster for this bug report. It should be fixed in #105.


remove 'late' and compiled Flutter/Dart app successfully but "start inquiry" button generates errors

I get the following error when running in the ios Simulator:
flutter: - Inquiry Template Ids with prefix: itmpl are not supported in this version, please upgrade to an SDK version >= 2.0.0.
I don't think that's referring to the dart version: dart-lang/dart/dart: stable 2.16.2, HEAD
So I am assuming it's requiring that I need to use persona SDK v 2.0
However, I'm using the pub.dev package, which I assume would be using the correct SDK.
Based on the instructions, I am unclear what else I need to do to get it to work.
Note: I am creating the Flutter mobile app using FlutterFlow.

Hi @timfong888
Check the plugin prerelease version 3.0.0-beta.0.
The new inquiry templates format (itmpl) are only supported on the Persona SDK 2.0 and above. The Prerelease version implements the newer SDK version.

When I set the dependency to beta I get an error. Do you have a cloneable sample that works with the v2 SDK?  That I can clone and run locally?

Yes. Clone the repository and run the folder example. Its a test project for the plugin.


remove Operations_List from Microsoft.Insights 2020-06-02-preview livetoken_API.json

This is to fix #17215. An identical definition of Operations_List is already in:
Microsoft.Insights/stable/2015-05-01/aiOperations_API.json
This just removes the duplicate.

Removing the Go workaround should remove the breaking change.

Looks like the Operation_List models are different. This won't work. Trying #17246.


Issues with the url bar autocompleter

Two situations, I've found, where the autocompleter in the URL bar stays open and won't go away:

If your target URL ends up triggering a download
If you change tabs while typing

Closed by https://github.com/beakerbrowser/beaker/commit/345a2293366ad3fef00348d79bb8ebba114e8928


Add support for provider specific options

It would be useful to have provider specific run options, for example -oracle:case-insensitivity.

@hazzik i guess it's already there see -providerswitches=QUOTEDIDENTIFIERS=TRUE for instance on oracle to quote identifiers, needs documentation on the wiki though

@hazzik i've added the switch to the wiki see https://github.com/schambers/fluentmigrator/wiki/Command-Line-Runner-Options


Adding support for configuring a binary download target

Should provide a stopgap for those of us who want to keep moving with Phoenix + Sass!
"Fixes" https://github.com/CargoSense/dart_sass/issues/7

Hi @clone1018 - thanks for the PR! I think I would like to take the approach in #8. We can continue to treat arch detection in an automatic way, and we can support native ARM packages when they become available, wdyt?

Perfectly fine with me :)


Dig object map out of container when building metadata

Coverage remained the same at 100.0% when pulling d7c698ac469bc1f81420b0c76a84651ac4519fb4 on CyberiaResurrection:HookMetadataExtractToContainer into 9b60c91bec58adcb398da94b8d5509e529a63b56 on Algo-Web:master.


Release new version

I know there are many refactorings still going on but perhaps we could release a new version because there are already a lot of improvements (over 60 commits since v0.18.0 https://github.com/Mindwerks/worldengine/compare/v0.18.0...master).
What do you think @psi29a ?

Even though I wasn't explicitly asked:
I think it would be good to get at least two more things out of the way first.
1. Removing pickle
This might simplify installation and, if done at a later point, could break compatibility with old saves. Better get it done as soon as possible (or rule it out completely).
I think that pickle-saves would not transfer well between Python 2 and 3, by the way.
2. More changes to seeding different algorithms
As stated here https://github.com/Mindwerks/worldengine/pull/133 the current solution does not seem 100% deterministically stable. Therefore changes might come up at some point that make old worlds "unregeneratable". I don't know yet how, but if I could polish that branch so that those concerns will never crop up again, that would be really nice. (Help is appreciated since so far I have not come up with a clean solution.)
Aside from those things a new release would be great! Especially for users under Windows it is probably quite painful to get the latest version running. Giving them an easy-to-use release with some incredible speed-boosts (50-66% less time needed than before) on top would certainly be really good. :)

We can re-write the pickle tests to only run based on python version. That way we can keep pickle and compare apples to apples as a result. Not that I like pickle, I'm just not 100% sold on protobuf yet. :)

protobuf is a Google-thing, isn't it? They tend to radically change things without hesitation, so I am kind of with you on that.^^
Do you know what would have to be changed to make pickle work properly?

Nothing really, just that world files created with python2 should only be compared on python2. Same with python3, the resulting file should only be read by python3. I suggest  in our current tests to add a check on python version:
    @unittest.skipIf(mylib.__version__ < (1, 3),
                     "not supported in this library version")
    def test_format(self):
        # Tests that work for only a certain version of the library.
        pass

https://docs.python.org/2/library/unittest.html#skipping-tests-and-expected-failures
That is an example of course, the @blahblah are decorators that we can use.
We can then write tests that are specific to a version.
We can nuke pickle and the tests when we are comfortable with our new 'stable' format.
In the next release, we can make protobuf the default and see what breaks for people. :)
The release after that, we can consider removing pickle.

That is a great solution. Once Google releases a proper version 3.0 of protobuf (not an alpha) we will at least have that as a fallback, should they ever decide to completely change directions on it. But until then supporting both formats sounds like a very good idea.
(How about a custom format, by the way? I don't even know what things are really saved, but I loved to come up with custom file-formats in C++.^^)

Probably next version should be 0.19.0: there are a lot of improvements!

To come back to this:
 @unittest.skipIf(mylib.__version__ < (1, 3),
                     "not supported in this library version")
    def test_format(self):
        # Tests that work for only a certain version of the library.
        pass

Would this not be equally good, maybe even better? This way the functionality that is the same under Python 2 and 3 can easily be reused.
diff --git a/tests/blessed_images/generated_blessed_images.py b/tests/blessed_images/generated_blessed_images.py
index 913ccbe..0d070b2 100644
--- a/tests/blessed_images/generated_blessed_images.py
+++ b/tests/blessed_images/generated_blessed_images.py
@@ -8,6 +8,7 @@ A script, generate_blessed_images, can be used to regenerate blessed images
 """

 import os
+import platform
 from worldengine.world import *
 from worldengine.draw import *

@@ -26,7 +27,10 @@ def main(blessed_images_dir, tests_data_dir):
     draw_temperature_levels_on_file(w, "%s/temperature_28070.png" % blessed_images_dir)
     draw_biome_on_file(w, "%s/biome_28070.png" % blessed_images_dir)

-    w_large = World.from_pickle_file("%s/seed_48956.world" % tests_data_dir)
+    if platform.python_version_tuple()[0] < 3:
+        w_large = World.from_pickle_file("%s/py2_seed_48956.world" % tests_data_dir)
+    else:
+        w_large = World.from_pickle_file("%s/py3_seed_48956.world" % tests_data_dir)
     draw_ancientmap_on_file(w, "%s/ancientmap_28070_factor3.png" % blessed_images_dir, resize_factor=3)
     draw_ancientmap_on_file(w_large, "%s/ancientmap_48956.png" % blessed_images_dir, resize_factor=1)

diff --git a/tests/data/data_generator.py b/tests/data/data_generator.py
index a47dcee..5793ad0 100644
--- a/tests/data/data_generator.py
+++ b/tests/data/data_generator.py
@@ -8,12 +8,16 @@ because the plate simulation steps do not provide the same results on all the pl
 """

 import os
+import platform
 from worldengine.plates import _plates_simulation

 def main(tests_data_dir):
     w = _plates_simulation("Foo", 300, 200, 279)
-    w.to_pickle_file("%s/plates_279.world" % tests_data_dir)
+    if platform.python_version_tuple()[0] < 3:
+        w.to_pickle_file("%s/py2_plates_279.world" % tests_data_dir)
+    else:
+        w.to_pickle_file("%s/py3_plates_279.world" % tests_data_dir)

 if __name__ == '__main__':
diff --git a/tests/drawing_functions_test.py b/tests/drawing_functions_test.py
index 1a6775d..a18e676 100644
--- a/tests/drawing_functions_test.py
+++ b/tests/drawing_functions_test.py
@@ -1,4 +1,5 @@
 import unittest
+import platform

 from worldengine.drawing_functions import draw_ancientmap, gradient, draw_rivers_on_image
 from worldengine.world import World
@@ -12,7 +13,10 @@ class TestDrawingFunctions(TestBase):
         self.w = World.open_protobuf("%s/seed_28070.world" % self.tests_data_dir)

     def test_draw_ancient_map_factor1(self):
-        w_large = World.from_pickle_file("%s/seed_48956.world" % self.tests_data_dir)
+        if platform.python_version_tuple()[0] < 3:
+            w_large = World.from_pickle_file("%s/py2_seed_48956.world" % self.tests_data_dir)
+        else:
+            w_large = World.from_pickle_file("%s/py3_seed_48956.world" % self.tests_data_dir)
         target = PixelCollector(w_large.width, w_large.height)
         draw_ancientmap(w_large, target, resize_factor=1)
         self._assert_img_equal("ancientmap_48956", target)
diff --git a/tests/generation_test.py b/tests/generation_test.py
index 8ad27d3..2142f9c 100644
--- a/tests/generation_test.py
+++ b/tests/generation_test.py
@@ -1,4 +1,5 @@
 import unittest
+import platform
 from worldengine.plates import Step, center_land, world_gen
 from worldengine.world import World

@@ -29,7 +30,10 @@ class TestGeneration(TestBase):
         return borders_total_elevation / n_cells_on_border

     def test_center_land(self):
-        w = World.from_pickle_file("%s/plates_279.world" % self.tests_data_dir)
+        if platform.python_version_tuple()[0] < 3:
+            w = World.from_pickle_file("%s/py2_plates_279.world" % self.tests_data_dir)
+        else:
+            w = World.from_pickle_file("%s/py3_plates_279.world" % self.tests_data_dir)

         # We want to have less land than before at the borders
         el_before = TestGeneration._mean_elevation_at_borders(w)

If that was ok, I would immediately generated the Python 3 file, rename the Python 2 file, create a PR for this patch and all pickle-related problems might be delayed for a bit. :P

Here is a different version, prettier in my opinion.
diff --git a/tests/blessed_images/generated_blessed_images.py b/tests/blessed_images/generated_blessed_images.py
index 913ccbe..d3d03b6 100644
--- a/tests/blessed_images/generated_blessed_images.py
+++ b/tests/blessed_images/generated_blessed_images.py
@@ -8,6 +8,7 @@ A script, generate_blessed_images, can be used to regenerate blessed images
 """

 import os
+import platform
 from worldengine.world import *
 from worldengine.draw import *

@@ -26,7 +27,7 @@ def main(blessed_images_dir, tests_data_dir):
     draw_temperature_levels_on_file(w, "%s/temperature_28070.png" % blessed_images_dir)
     draw_biome_on_file(w, "%s/biome_28070.png" % blessed_images_dir)

-    w_large = World.from_pickle_file("%s/seed_48956.world" % tests_data_dir)
+    w_large = World.from_pickle_file("%s/py%s_seed_48956.world" % (tests_data_dir, platform.python_version_tuple()[0]))
     draw_ancientmap_on_file(w, "%s/ancientmap_28070_factor3.png" % blessed_images_dir, resize_factor=3)
     draw_ancientmap_on_file(w_large, "%s/ancientmap_48956.png" % blessed_images_dir, resize_factor=1)

diff --git a/tests/data/data_generator.py b/tests/data/data_generator.py
index a47dcee..2d627c3 100644
--- a/tests/data/data_generator.py
+++ b/tests/data/data_generator.py
@@ -8,12 +8,13 @@ because the plate simulation steps do not provide the same results on all the pl
 """

 import os
+import platform
 from worldengine.plates import _plates_simulation

 def main(tests_data_dir):
     w = _plates_simulation("Foo", 300, 200, 279)
-    w.to_pickle_file("%s/plates_279.world" % tests_data_dir)
+    w.to_pickle_file("%s/py%s_plates_279.world" % (tests_data_dir, platform.python_version_tuple()[0]))

 if __name__ == '__main__':
diff --git a/tests/drawing_functions_test.py b/tests/drawing_functions_test.py
index 1a6775d..91600a5 100644
--- a/tests/drawing_functions_test.py
+++ b/tests/drawing_functions_test.py
@@ -1,4 +1,5 @@
 import unittest
+import platform

 from worldengine.drawing_functions import draw_ancientmap, gradient, draw_rivers_on_image
 from worldengine.world import World
@@ -12,7 +13,7 @@ class TestDrawingFunctions(TestBase):
         self.w = World.open_protobuf("%s/seed_28070.world" % self.tests_data_dir)

     def test_draw_ancient_map_factor1(self):
-        w_large = World.from_pickle_file("%s/seed_48956.world" % self.tests_data_dir)
+        w_large = World.from_pickle_file("%s/py%s_seed_48956.world" % (self.tests_data_dir, platform.python_version_tuple()[0]))
         target = PixelCollector(w_large.width, w_large.height)
         draw_ancientmap(w_large, target, resize_factor=1)
         self._assert_img_equal("ancientmap_48956", target)
diff --git a/tests/generation_test.py b/tests/generation_test.py
index 8ad27d3..0a16b4a 100644
--- a/tests/generation_test.py
+++ b/tests/generation_test.py
@@ -1,4 +1,5 @@
 import unittest
+import platform
 from worldengine.plates import Step, center_land, world_gen
 from worldengine.world import World

@@ -29,7 +30,7 @@ class TestGeneration(TestBase):
         return borders_total_elevation / n_cells_on_border

     def test_center_land(self):
-        w = World.from_pickle_file("%s/plates_279.world" % self.tests_data_dir)
+        w = World.from_pickle_file("%s/py%s_plates_279.world" % (self.tests_data_dir, platform.python_version_tuple()[0]))

         # We want to have less land than before at the borders
         el_before = TestGeneration._mean_elevation_at_borders(w)

If the pickle can be written and read by both Py2 and Py3, then that is also great IMHO.
@ftomassetti we ok with replacing the blessed images? Did you want to eyeball them first?

I hope you noticed this:
"%s/py%s_plates_279.world" % (self.tests_data_dir, platform.python_version_tuple()[0])

Regarding the "new" blessed images: They are probably so different because I fed different parameters to platec.

The blessed images are just the output created from the world files... 'blessed' is all data that goes into worldengine-data. ;)
Ah, now that you mentioned it... building it into the name is rather handy. :)

The idea of the "blessed" images is that any time you change them you look at them and approve them to be used in tests after "visual inspection". In other words you have to check they looks good and give to them your blessing.

86 commits and 43 files changed so far. I would definitely go for v 0.19.0: this is a huge improvement over v 0.18.0!
I would love to release what has been done throught these great contributions (thanks @tcld  and @esampson !) and share it.

What kind of timeframe are you thinking about?

Nothing specific, but it would be nice to have a new release soon. Bear in mind that nothing prevents us to release v0.19.1 the day after we released v0.19.0

One of my PRs (at the very least the change to the RNG-handling https://github.com/Mindwerks/worldengine/pull/146) will break seed-compatibility, meaning that old seeds will produce different worlds. At the same time, if done right, this might guarantee seed-compatibility for the foreseeable future. So I think this should be done before a new release.
Then there is the non-working parameter ocean_level, which I so far failed to properly handle (the output was ugly). Should something be done about that before a release? Maybe the parameter should be "muted" for now so users aren't confused by it? (Solving the problem would be a lot better, of course.)
And, finally, I was working on changing the standard heightmap-output to 16 Bit grayscale PNGs - which I think could be very useful if worldengine was used to create 3D-worlds. If the quality of the 16 Bit heightmaps was satisfying, this, too, would be a nice thing to include in a release.
And just to be sure: Are there any major bugs to take care of at the moment? I saw the negative masses crop up once or twice (that's platec, right?), but that seems rare and (strangely) still leads to valid worlds, as far as I can tell.

I think that the compatibility breakage are the only things which necessarily goes in: bug fixes and backward-compatible improvements can be inserted in a successive version without any problem I think.
In my opinion release early, release often is a very valid principle for Open-Source (and for most kinds of software).
If we start to produce a new release the user could benefit from the great improvements we already have and start reporting possibly new bugs we introduced :)
In the meantime we can work on the next release with even more cool stuff.
So we can definitely wait for #146 (no hurry!) and also for the 16 Bit grayscale PNGs. That is just my opinion, we should also listen to @psi29a of course

#146 is a very simple one, although there is one thing I need some input about before finishing it:
https://github.com/Mindwerks/worldengine/pull/146/files#diff-80eed145c1070172ffba1f642a13b731R185
The 16 Bit-stuff...well, I continued working on that for probably too long (I fully replaced Pillow in my local branch) and now I am not sure if I have gone too far for the sake of getting rid of a single dependency. So that needs some thinking and refining by me before I can even update the corresponding PR.

If you are asking an opinion about the sub_seeds thing it seems fine to me. However could be a bit painful to specify the right index (sub_seeds[0] for precipitation, sub_seeds[1] for erosion, etc. What if I add a step in between?). Perhaps you can use constants or a wrapper class for that which exposes the method next_seed.

I wanted things to be deterministic - if one were to add a step in between, one could use sub_seeds[2] (or any other one as there are 100 of them). Some kind of mapping or similar might be prettier, though. I will think about how to do it.

111 commits since v0.18.0 :)

I have only one "new" thing left in mind that I might start working on, aside from that I will focus on finishing the things I started (that includes 16 Bit heightmaps, for which there is no PR at the moment).
I realized that I never updated the changelog, maybe I should do that at the end. Although almost none of my changes will be visible at the surface, so sped things up and totally broke seed-compatibility might be enough to add.^^

You should definitely add yourself as a contributor. We are now at 135 commits since v0.18.0 :)

How would I even do that?

You could list yourself in the README file

170 commits since version 0.18.0
This is a lot :)
I would like just to get the satellite map because it comes from a new contributor and we want his code to be part of a new release. After that I think we could make new binary packages and make it available for people who do not want to know what a compiler is.
And promote it, and asks for more feedback and keep working on really cool stuff.
And also discuss an agenda for version 1.0.0

It's probably a good time for a release. The only open issue I remember is the one with non-working ocean-levels, but maybe that is fine for a release? Aside from that we should hope for a time with less PRs.^^
And yes, the satellite-PR should go in. And be non-optional in my opinion. I don't really see any use for it aside from eye-candy, but at that it is a tremendously great addition I wouldn't want to see left out.

I love PRs, I hope to keep having a lot of those good PRs you Evan and others keep throwing at us :D

We should hammer out the open PRs first.
I was hoping that documentation will make it in, but it isn't necessary for a release.

Probably not the best place to mention this, but I noticed that there are quite a lot of branches to choose from in the WorldEngine-repo at the moment. I assume that at least some of them stem from merged PRs - could they maybe deleted?

I closed a few merged PRs, others are connected to open PRs or require some investigation to understand if they still have valuable code.

It's already a lot better, thank you very much! :)


Need full explaination of configuration variables.

Docs here http://mrq.readthedocs.org/en/latest/configuration/  only say a little.
I want to know how to set mongodb and other useful variables

Yes we definitely have to update the online doc.
For now you can either do mrq-worker --help or check https://github.com/pricingassistant/mrq/blob/master/mrq/config.py

I think https://github.com/pricingassistant/mrq/pull/91 and https://github.com/pricingassistant/mrq/pull/92 fixed this issue on the documentation issue. If there is anything else you would like me to explain, I'd be more than welcome to do a PR to fully fix this.  Lets get MrQ to version 1.0.0

Yep, we can definitely consider this as closed. Thanks a lot @IAlwaysBeCoding !

@sylvinus No problem,your project will be the brainchild of a project I have in mind, so it is definitely in my best interest to have MrQ ready for  "production" .Cheers!


Bug: Plugins in the _plugins folder aren't working

I'm trying to add this splashtag plugin but it is not recognised by the theme.
I get a liquid exception when I try to use it:
Liquid Exception: Liquid syntax error (line 3): Unknown tag 'splash' in /Users/USER/Projects/FOLDER/_posts/2019-02-23-test.md

Maybe the plugin not support the new version of Jekyll.


server won't run

I cloned the repo and followed the install outlined in the readme but the app fails to start.  I'm seeing this repeatedly in the startup logs:
dev/typings/browser/ambient/angular-component-router/index.d.ts
(49,29): error TS2304: Cannot find name 'Promise'.
any ideas?

I have updated the version of typings used for this seed.  It should help resolve any typing issues like this.  The version of angular-component-router typings it was using had some issues apparently.


Bugreport

Dockerfile slimmed

by using the python:3.8-slim as base image instead of  tiangolo/uvicorn-gunicorn-fastapi:python3.8 and reducing some dependencies has reduced image size from 1.3 GB to 450 MB.
Gives extra control over processes in docker image as dockerfile and scripts completely reliant on us now

SQL support
Previously internal storage was done using sqlite but without the use of handler packages like sqlalchemy or alembic to handle them. Hence internal storage was hardcorded and complex and only supported for argorithm data storage. Thats why previously auth features could not be utilised without external mongoDB database.

Added alembic for migrations

sqlalchemy core functionalities utilized which allows us to now store all data internally

Can be easily extended to MySQL and PostgreSQL databases

will require to add some dependencies

Database monitoring
pymongo has a useful monitoring module that allows us to create metrics for database opertaions. So added database monitoring metrics:

DB_EVENT_STARTED : COUNTER
DB_EVENT_FINISHED : COUNTER
DB_EVENT_TIME : HISTOGRAM

Updated dashboard to include database dashboards
Bug report
resolves #15
Created a reports API which takes 3 kinds of reports
@Vin-dictive

User Report
{
    "argorithmID" : "",
    "description" : {
	   "text" : "<description>",
        "severe" : true|false,
        "test_params" : {
            "param_1" : 1
        }
    }
}

The test_params is an optional data that a user can add if he wants to send some params so that can maintainer can replicate the problem faced by user.
This request should be send with authentication token if AUTH=ENABLED

System Report
{
    "argorithmID" : "",
    "description" : {
        "text" : "error traceback"
    }
}

This should be used when a particular argorithm error breaks the unity application.  It does need to have an authorization token

System crashes not done by argorithm should be reported to github issues

Metrics Alert
Not yet implemented completely but it handles alerts raised by prometheus so does not need attention from unity application

Documentation
Server documentation has been shifted to server repo from toolkit repo
Pending tasks

Detailed documentation for Server - ( @UtkG07 )

Testing for Server

Bug report compilation

Metrics alert system

Kubernetes testing with recent changes

Closing issue as repo is being archived.


 Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>abci script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-08-22T16_54_02_521Z-debug.log

I had these folders in /tmp
drwxr-xr-x  2 root root  4096 Thg 8  21 22:00  drive_json_1.log/
drwxr-xr-x  2 root root  4096 Thg 8  21 22:00  drive_json_2.log/
drwxr-xr-x  2 root root  4096 Thg 8  21 22:00  drive_json_3.log/
drwxr-xr-x  2 root root  4096 Thg 8  21 22:00  drive_pretty_1.log/
drwxr-xr-x  2 root root  4096 Thg 8  21 22:00  drive_pretty_2.log/
drwxr-xr-x  2 root root  4096 Thg 8  21 22:00  drive_pretty_3.log/

I deleted them and ran sudo chmod 777 /tmp for good measure, now dashmate finished with success

Discussed in triage. Fix due in v21

v.21-dev still hangs, one way to trigger it is to restart the computer while the node is running:
the log files are mounted as directories
sudo rm /tmp/drive_*
rm: cannot remove '/tmp/drive_json_1.log': Is a directory
rm: cannot remove '/tmp/drive_json_2.log': Is a directory
rm: cannot remove '/tmp/drive_json_3.log': Is a directory
rm: cannot remove '/tmp/drive_pretty_1.log': Is a directory
rm: cannot remove '/tmp/drive_pretty_2.log': Is a directory
rm: cannot remove '/tmp/drive_pretty_3.log': Is a directory

the workaround is:
sudo rm -rf /tmp/drive_*

@dashameter, as per discord convo, please retest. Should be fixed due to:
https://github.com/dashevo/dashmate/pull/437

@dashameter, as per discord convo, please retest. Should be fixed due to:
#437

exactly - please let me know as we've been also discussing that today with the Team (should be fixed now)


Revert "hack.build: reduce the size of pouch and pouchd binaries"

Reverts alibaba/pouch#1484
debug symbols also are removed by strip, although size of pouch and pouchd binaries are reduced, perhaps, we can append --only-keep-debug option to strip to avoid this issue later.

Codecov Report

Merging #1530 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1530      +/-   ##
=========================================
+ Coverage   40.75%   40.8%   +0.05%
=========================================
  Files         256     256
  Lines       16756   16756
=========================================
+ Hits         6829    6838       +9
+ Misses       9048    9042       -6
+ Partials      879     876       -3

Impacted Files
Coverage Δ

daemon/mgr/container.go
49.14% <0%> (+0.08%)
:arrow_up:

daemon/mgr/network.go
69.43% <0%> (+0.48%)
:arrow_up:

ctrd/container.go
50.93% <0%> (+0.62%)
:arrow_up:

daemon/logger/jsonfile/utils.go
73.17% <0%> (+1.62%)
:arrow_up:

ctrd/watch.go
78.12% <0%> (+3.12%)
:arrow_up:

LGTM


[WIP] feat: actions/core upgraded to v1.10.0

Issue #, if available:
Description of changes:
Following the recommendations from Github (https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/) to remove the set-output warnings we propose to update the version of actions/core component.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Same PR raised here: https://github.com/smitp/amazon-ecs-run-task/pull/108
But tests failing: Error: Network Configuration must be provided when networkMode 'awsvpc' is specified.
An additional parameter will be required to add for this configuration before merging.

Closed due a wrong base code.