--all option doesn't work via CLI

When launching via CLI with option --all, only the "regular" sub track for a language is extracted even if the file has multiple sub tracks of the same language (forced, sdh). Launching with -a yields the same result. Specifying languages or not doesn't help.
The issue is not present when when launching with setting one_per_lang=False via the API.
Tested on V 0.1.11
I noticed that two launch options use the same -a argument, could that be the cause?
@click.option('-a', '--age', type=AGE, help='Filter videos newer than AGE, e.g. 12h, 1w2d.')
...
@click.option('-a', '--all', is_flag=True, default=False,
              help='rip all tracks for a given language, even another track for that language was already ripped')

After playing a bit more with the API, I noticed that the issue also happens with the API if "overwrite=False". I updated the issue.


Fix URL for checkin QR code

This PR fixes the URL for the checkin QR code

Pull Request Test Coverage Report for Build 371

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

Totals

Change from base Build 363:
0.0%

Covered Lines:
3187

Relevant Lines:
3187

💛  - Coveralls


Configuration Updates, Code Enhancements

This pull request includes several important changes to the README.md, example/example_config.ini, and various Python files to improve configuration, validation, and login processes. The most significant changes include updating the configuration instructions and file, enhancing the regex for API key validation, and modifying the Moodle login process.
Configuration Updates:

README.md: Added instructions to copy the example configuration file and updated the configuration parameters table to reflect new parameter names and descriptions.
example/example_config.ini: Changed the default value of the SUMMARIZE parameter from 1 to 0.

Code Enhancements:

src/gpt/openai_chat.py: Updated the regex for API key validation to allow for more characters and increased length.

Login Process Improvements:

src/moodle/moodle_notification_handler.py: Added a logged_in attribute to track login status and modified the __login method to use this attribute, ensuring that login attempts are only made when necessary. [1] [2]

Summary by Sourcery
Update the configuration instructions and files, enhance the API key validation regex, and modify the Moodle login process to include login status tracking and prevent unnecessary login attempts.
Enhancements:

Enhance the regex for API key validation to allow for more characters and increased length.
Add login status tracking and modify the login process to prevent unnecessary login attempts.

Documentation:

Update README with instructions for copying the example configuration file and update the configuration parameters table.

BUild status finally not failing


Can this plugin support CSS, HTML and javascript in html file?

Thanks for your work! I used to use Brackets and it can remove comment without selecting all the components . But I find it not working in VS Code. However, I find this plugin in VS Code and it worked in js file. Thank you! And I find that it can't work in CSS, HTML and javascript in html file. I wonder if this plugin can support them. Thanks!

Hey! I'm glad you find it useful!
I've included support for several other languages in v1.1.0

@alexmunteanu needs support for Blade (Laravel) files. Tnx.
vscode identifier 'blade'

Added in v1.2.0
Apologies for the delay!


Refactor {_,}parse_* jinja macros into Python code

In particular, the _parse_option macro is horrifyingly complex.

Fixed in commit 3de88626a0220d022b4f783dcb9f286d62568cd3.

~7.000s serial compile time for all my elvi now (from ~8.100 before any of these changes).

Interesting to note that when surfraw-tools is installed with pip install . rather than pip install -e . (dev mode), the serial compile time is even shorter at ~4s in total (97.56ms average per elvis (2 d.p.)).
The pkg_resources import really tanks it, huh.


[2.3.x] update CHANGELOG and bump version numbers for 2.3.x release

This one is for the 2.3.x branch, I'll need to make another PR for the main branch since we want these updates there too
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Downstream CI failing for the same reason as in #141


Error: Could not find module mock-socket imported from (require)

Just tried to use this lib in my ember-test environment. I simply installed it with npm.
Importing it like this:
var mockWebSocket = require('mock-socket').WebSocket;
var mockServer = require('mock-socket').Server;

Or like this:
import { WebSocket, Server } from 'mock-socket';

Results in the same error:
Error: Could not find module `mock-socket` imported from `(require)`
    at missingModule (http://localhost:4201/assets/vendor.js:173:11)
    at findModule (http://localhost:4201/assets/vendor.js:188:17)
    at requireModule (http://localhost:4201/assets/vendor.js:177:12)
    at Module.callback (http://localhost:4201/assets/tests.js:406:23)
    at Module.exports (http://localhost:4201/assets/vendor.js:92:34)
    at Module.build (http://localhost:4201/assets/vendor.js:142:10)
    at findModule (http://localhost:4201/assets/vendor.js:190:9)
    at requireModule (http://localhost:4201/assets/vendor.js:177:12)
    at Object.TestLoader.require (http://localhost:4201/assets/test-loader.js:67:9)
    at Object.TestLoader.loadModules (http://localhost:4201/assets/test-loader.js:58:18)

Am I doing something wrong?

@badazz91 If you are using it within ember then you will need to install it via bower.
bower install mock-socket

Then in your ember-cli-build.js add:
https://github.com/thoov/ember-websockets/blob/master/ember-cli-build.js#L17
Let me know if this works for you.

No luck so far. Installed it via bower and included it in the ember-cli-build.js like this:
  app.import('bower_components/mock-socket/dist/mock-socket.min.js', {
    exports: {
      'mock-socket': [
        'default',
        'WebSocket',
        'Server'
      ]
    }
  });

Yet the import in my test file stil fails... Am I missing something?

If included in the ember-cli-build.js you can simply access it like this:
 window.MockServer
 window.MockWebSocket
 window.MockSocketIO

Sorry for not reading the documentation more thoroughly ;-)

@badazz91 Glad you were able to get it installed!


Create one hot embedding

The PR has the following updates to Seq2Pat:

Add one-hot encoding, by mining patterns locally (csp_local.py) or globally (csp_global.py) in each sequence.
Add Dichotomic Pattern Mining Notebook to show a pipeline of running DPM on a sample dataset.
Clean up C++ vector variables datab_MDD, mdd_q from calling Build_MDD()
Clean up vector variable attr in node_mdd.hpp
Clean up vector variables indic_vec, result from calling Freq_miner()
Add an introduction of DPM notebook to README and the Examples section in Docs

@skadio @dorukkilitcioglu, thanks for the comments. I believe I have all them addressed. Some updates will include the following parts:

Added a DPM example in README, docs, and the bibtex citation
Added tests for repeatedly calling seq2pat, with or without constraints
Updated encodings column names, e.g. feature_0
Added comments to backend where vectors get cleaned up
Added more description to DPM notebook, updated the print out with new column names
Removed unused functions, parameters,  such as set_attribute(), simplified logic in checking constraints
Moved the lines for cleaning up the same vector together
Set the version=1.3.0

Let me know if these updates look good.

Sounds good!


ui: Show rule violations (main page)

This is the first PR in a series of upcoming PRs, which implements the main view of rule violations.:
Statistics card in the ORT run results main page, showing the number of rule violations:

Rule violations main page, which is a grouped table, by default grouping is set for the severity:

Details modal (see pending issues):

Pending issues:

as rule violation endpoint doesn't return unique IDs for rule violations, details routes cannot yet be created in the front-end. Therefore, as a first implementation, the details are shown in modals
dynamic sorting needs to possibly be added to the rule violations table in an upcoming PR
once the details are moved to their own separate sub-pages, we need a markup renderer for how-to-fix texts

I have some serious problems with resolving merge conflicts with GitButler, so need to take care of those before continuing with this.

Rule violations main page, which is a grouped table, by default grouping is set for the severity:

I find this an unusual approach for a table. What is the benefit over making the severity column sortable and filterable?

What is the benefit over making the severity column sortable and filterable?

Do you mean what's generally the benefit of grouping?

What is the benefit over making the severity column sortable and filterable?

Do you mean what's generally the benefit of grouping?

Yes, I wonder what problem it solves and I find sorting and filtering by column more intuitive for a table.

What is the benefit over making the severity column sortable and filterable?

Do you mean what's generally the benefit of grouping?

Yes, I wonder what problem it solves and I find sorting and filtering by column more intuitive for a table. Especially as filters can be combined, grouping not.

Grouping can be combined. IME of clearance work with ORT, the difference of what I want to do with errors, warnings and hints is massive, so I find grouping to make very much sense there.

Do you mean what's generally the benefit of grouping?

Yes, I wonder what problem it solves and I find sorting and filtering by column more intuitive for a table. Especially as filters can be combined, grouping not.

From past experience when looking at rule violations in the WebApp report, users were intimidated by the vast number of rule violations. In many cases the have the same root cause e.g. for multiple files in a package, and a single simple configuration change can make dozens of violations go away. To get a better overview in such cases, IMO it's beneficial to e.g. group violations by package, so easily identify problematic packages.

Grouping the rule violations table can be mixed and matched; every column is groupable, and groupings "stacks". It can also be toggled off if wanted.

I guess I have to see how that works in practice, currently I cannot imagine how grouping properly works with pagination.


Identity claims does not reflect the claim value when used as placeholders in "Account Confirmation" email templates

Description
Identity claims does not reflect the claim value when used as placeholders in "Account Confirmation" email templates
How to reproduce:

Add a placeholder for an identity claim in the "Account Confirmation" email template. ex: {{user.claim.identity.emailVerified}}
Try the user self-registration REST API with a value for the above claim in the request payload.
ex: http://wso2.org/claims/identity/emailVerified

Expected behaviour:
Reflect the value of the identity claim in the placeholder when the account confirmation email is sent to the user.
Environment information:

Product Version: IS 5.7.0

Workaorund:
Assuming that the identity claim used for the email template was http://wso2.org/claims/identity/emailVerified

In the email template replace all the usages of {{user.claim.identity. emailVerified }} with {{emailVerified}} and save the template.

Under the properties in the request payload you have given above, you need to include an additional property called emailVerified and the respective value (same value given for the emailVerified identity claim). See the example below.

{
    "user": {
        "username": "john",
        "realm": "PRIMARY",
        "password": "passwd",
        "claims": [
         ...
            {
                "uri": "http://wso2.org/claims/identity/emailVerified",
                "value": "something"
            }
         ...
        ]
    },
    "properties": [
         ...
        {
            "key": "emailVerified",
            "value": "something"
        }
         ...
    ]
}

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Notification View does not work correctly

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Feature request
[ ] Question

Current behavior
Clicking on a notification from the notification list shows Readme.md of that repo
Expected behavior
It should show a specific issue or PR
Steps to reproduce the behavior
Whenever new notification(s) arrive, click on the notifications icon and then click on any notification from the list.
Environment
Windows 10 Fall update

Fixed in #108

Merged.


Add enable_output service to Yamaha platform

Description:
This PR adds the service yamaha_enable_output that makes it possible to enable or disable an output (usually HDMI).
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#2602
Example service call:
service: media_player.yamaha_enable_output
data:
  entity_id: media_player.yamaha
  port: hdmi1
  enabled: true

Checklist:
If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable (example).
[X] New dependencies are only imported inside functions that use them (example).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.

I'm curious - what do you envision this use case to be? When would a yamaha owner (such as myself) want to disable or enable an HDMI input?

I have my TV connected to hdmi1 and projector to hdmi2 and they both loose sync if both ports are enabled (just keeps flickering). So I can just have one port enabled at the time.

@postlund thanks!

This PR seems to have gone stale. Closing it. You can reopen it when you're ready to finish it.


Update startup-nvim/startup.nvim

Owner changed to max397574.
Repo URL:
https://github.com/startup-nvim/startup.nvim
Checklist:

[ ] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[ ] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[ ] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else. No .. for Neovim.
[ ] The description doesn't contain emojis.
[ ] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[ ] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR!


GATK AnnotatedInervalCodec Exception (GATK4)

Greetings,
I am running bcbio v1.2.9a, and I'm encountering this issue for all my samples.
Seek your help in resolving this please. Thank you.
My yaml file is as attached.
[2022-03-16T08:24Z] org.broadinstitute.hellbender.exceptions.GATKException: Unable to automatically instantiate codec org.broadinstitute.hellbender.utils.codecs.AnnotatedIntervalCodec
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.FeatureManager.getCandidateCodecsForFile(FeatureManager.java:529)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.FeatureManager.getCodecForFile(FeatureManager.java:476)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.FeatureDataSource.getCodecForFeatureInput(FeatureDataSource.java:397)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.FeatureDataSource.getFeatureReader(FeatureDataSource.java:373)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.FeatureDataSource.(FeatureDataSource.java:319)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.FeatureDataSource.(FeatureDataSource.java:291)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.VariantWalker.initializeDrivingVariants(VariantWalker.java:58)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.VariantWalkerBase.initializeFeatures(VariantWalkerBase.java:67)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.GATKTool.onStartup(GATKTool.java:726)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.engine.VariantWalker.onStartup(VariantWalker.java:45)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(CommandLineProgram.java:138)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(CommandLineProgram.java:192)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(CommandLineProgram.java:211)
[2022-03-16T08:24Z]     at org.bro
config.yaml.txt
adinstitute.hellbender.Main.runCommandLineProgram(Main.java:160)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.Main.mainEntry(Main.java:203)
[2022-03-16T08:24Z]     at org.broadinstitute.hellbender.Main.main(Main.java:289)
[2022-03-16T08:24Z] 16:24:14.062 WARN  NativeLibraryLoader - Unable to load libgkl_compression.so from native/libgkl_compression.so (Disk quota exceeded)
[2022-03-16T08:24Z] Using GATK jar /scratch/users/astar/gis/simngl/apps/bcbio/anaconda/envs/java/share/gatk4-<IP_ADDRESS>-1/gatk-package-<IP_ADDRESS>-local.jar
[2022-03-16T08:24Z] Running:
[2022-03-16T08:24Z]     java -Dsamjdk.use_async_io_read_samtools=false -Dsamjdk.use_async_io_write_samtools=true -Dsamjdk.use_async_io_write_tribble=false -Dsamjdk.compression_level=2 -Xms681m -Xmx3181m -XX:+UseSerialGC -Djava.io.tmpdir=/scratch/users/astar/gis/simngl/bcbioruns/TCGA-ESCA/runs/TCGA-L5-A4ON/bcbio_work/bcbiotx/tmpcscn29vc -jar /scratch/users/astar/gis/simngl/apps/bcbio/anaconda/envs/java/share/gatk4-<IP_ADDRESS>-1/gatk-package-<IP_ADDRESS>-local.jar FilterMutectCalls --reference /home/users/astar/gis/simngl/scratch/apps/bcbio/genomes/Hsapiens/hg38/seq/hg38.fa --variant /scratch/users/astar/gis/simngl/bcbioruns/TCGA-ESCA/runs/TCGA-L5-A4ON/bcbio_work/mutect2/chr11/TCGA-L5-A4ON-chr11_112615613_128704003-raw.vcf.gz --output /scratch/users/astar/gis/simngl/bcbioruns/TCGA-ESCA/runs/TCGA-L5-A4ON/bcbio_work/bcbiotx/tmpcscn29vc/TCGA-L5-A4ON-chr11_112615613_128704003-raw-filt.vcf.gz
[2022-03-16T08:24Z] Uncaught exception occurred

Hi @gis-nlsim !
"Disk quota exceeded" - is it possible that the run is out of disk space?
SN

Hi Dr Naumenko,
Thanks for pointing that out, but I cleared up the disk space and reran with only a few samples; I’m still getting the same error, even without the disk quota issue, so I think this is a separate problem? Attached is the error log file. Thank you.
Sim Ngak Leng
From: Sergey Naumenko @.>
Sent: Sunday, 20 March 2022 10:47 AM
To: bcbio/bcbio-nextgen @.>
Cc: SIM Ngak Leng @.>; Mention @.>
Subject: Re: [bcbio/bcbio-nextgen] GATK AnnotatedInervalCodec Exception (GATK4) (Issue #3631)
Hi @gis-nlsimhttps://github.com/gis-nlsim !
"Disk quota exceeded" - is it possible that the run is out of disk space?
SN
—
Reply to this email directly, view it on GitHubhttps://github.com/bcbio/bcbio-nextgen/issues/3631#issuecomment-1073153320, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMRXQUPC73VVW5NR6G4FFBLVA2GRBANCNFSM5Q3I7SCA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
This e-mail and any attachments are only for the use of the intended recipient and may contain material that is confidential, privileged and/or protected by the Official Secrets Act. If you are not the intended recipient, please delete it or notify the sender immediately. Please do not copy or use it for any purpose or disclose the contents to any other person.

@gis-nlsim I don't see the attachment - is it missing?


Do gradle plugin portal releases to bintray instead of directly to gradle plugin portal.

The gradle plugin portal's directly upload mechanism doesn't seem to support tracking download which we require : https://discuss.gradle.org/t/plugin-portal-download-statistics/11609/5
But there are mechanisms for publishing to the gradle-plugin portal via bintray instead which does give all that information : https://bintray.com/package/readme/etienne/gradle-plugins/gradle-plugindev-plugin
I would do a little poking around, I haven't done all the homework on this yet.

Can't seem to find method for using Bintray as the hosting repository for a Gradle Plugin Portal plugin - posted a question about it.
Linking an existing Bintray repo seems to be just copying the the artifacts to plugins.gradle.org/m2.


Wrap messages in text to avoid interpreting as markdown

In the current system, AbstractString is interpreted as markdown by default (at least, the official docs say that, and TerminalLogger follows through on it).
So wrap messages from streams in Text to avoid this.

@tanmaykm this allows logging backends to distinguish the text arising from a stream as "just plain text", whereas the messages from @info are conventionally markdown.
I think this is semantically correct, but I also wanted to check it doesn't cause problems for the JuliaRun use case.

Looks like it should be fine. But will test it out and confirm.

:+1:  JuliaRunLogger worked fine with this change.


Interoperable CSS (ICSS) modules are not supported

System Info
System:
    OS: macOS 12.6.1
    CPU: (8) arm64 Apple M1
    Memory: 78.09 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 103.0.5060.114
    Safari: 16.1
  npmPackages:
    @rspack/cli: ^0.1.5 => 0.1.5
Details
ICSS modules, which allows us to use :export {...} in our CSS, does not seem to be supported.
If I create styles.module.css with a simple class, importing it via import myStyles from './styles.module.css works fine.
styles.module.css example:
.my-class {
  background-color: #000;
}

The output of myStyles is { my-class: 'src-styles-module-css__my-class }', as expected.
However, if I use :export {...} (icss) in my CSS file, the import produces an empty object.
styles.module.css example:
:export {
  black: #000;
}

import myStyles from './styles.module.css
myStyles comes out being an empty object {}
Using webpack and css-loader, the solution was to set the mode to icss. Details available here.
{
  loader: 'css-loader',
  options: {
    modules: {
      mode: 'icss'
    }
  }
}

I don't see any way to set the CSS module mode to support "icss".
Reproduce link
No response
Reproduce Steps

Start a new rspack project
Add a styles.module.css file
Add an :export {...} directive to the css file
Import the css file
The import produces an empty object

This can be achieved by adding support for style-loader and css-loader compatibility, which we have already started doing it.

Thank you, @ahabhgk
Do you know when style-loader and css-loader are going to be supported? Is there a issue/pipeline I can watch for updates?

style-loader and css-loader is supported now, please try it in 0.1.12 version

@hardfist @ahabhgk @hyf0
I've confirmed that this works with css-loader. I'm all good here and as far as I'm concerned, the issue can be closed. Thank you!

lets leave it open until we support it in native css

we will wait until webpack experiments.css support it, so close now


[3.0.0-beta.10] Can't import node-fetch when using TypeScript in CJS mode

When upgrading node-fetch to v3.0.0-beta.10 in a TypeScript project which compile modules in CommonJS mode, the following error occured:
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /tmp/node-fetch-test/node_modules/node-fetch/src/index.js
require() of ES modules is not supported.
require() of /tmp/node-fetch-test/node_modules/node-fetch/src/index.js from /tmp/node-fetch-test/index.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename /tmp/node-fetch-test/node_modules/node-fetch/src/index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /node-fetch-test/node_modules/node-fetch/package.json.

Reproduction
Steps to reproduce the behavior:

Create an empty project:

npm init
npm i -D typescript
npm i<EMAIL_ADDRESS>npx tsc --init

Create a file index.ts with the following code:

import fetch from "node-fetch";

(async () => {
    const res = await fetch("https://api.github.com/repos/touchifyapp/player/releases/latest", {
        headers: { Accept: "application/vnd.github.v3+json" }
    });

    console.log(await res.json());
})();

Run the project:

tsc -p .
node index.js

Expected behavior
It should be able to import node-fetch correctly.
Many projects are using commonjs. When using TypeScript in cjs mode, it is not possible to mix require and import statements. Even in traditional javascript projects, importing an ES module is a mess. you have to use the async import() syntax, you can't import the module as usual.
I think we should provide both ESM and CJS versions of the package to ensure all users can migrate to node-fetch v3.
We can use package.json exports configuration to ensure projects are using the appropriate version of the module depending on their configuration.
The simplest and quickest method could be to use esbuild which can transpile esm modules to cjs.
Your Environment

software
version

node-fetch
3.0.0-beta.10

node
14.15.3

npm
7.19.1

Operating System
WSL 2

typescript
4.3.5

(I gave a longer answer on my opinion on the change in the PR)
Since you are using Node.js 14.15.3, can't you switch from "module": "CommonJS" to "module": "ES2020" in your tsconfig.json? Then also add "type": "module" to your package.json, add the .js file extension to your imports, and you should be good to go 🚀

@LinusU I have similar issues - my code happens to be a plugin for another project that itself doesn't currently support ES2020 yet. This represents a significant breaking change for that use case. I understand why you are pushing folks to update, but it's simply not possible in a non-trivial percentage of use cases where one is dependent on upstream packages / solutions also updating, and our user communities get impacted as a result.
My current "fix" for this is to pin the dependency to beta9 or below. Not thrilled about it, but updating to ES2020 modules is just not an option that is meaningfully available to me right now since it would break the entire module/plugin, although certainly open to suggestions about how to solve for it if there's a workaround. I'd much rather keep up with the most recent versions, but don't see a good way to do it without breakage unless node-fetch offers broader compatibility with legacy ways of doing things, for the time being.
My thoughts for what it's worth - a breaking change like this is a year too soon. There's still an awful lot of code that falls into the above categories, and it isn't going to get updated overnight.

My thoughts for what it's worth - a breaking change like this is a year too soon. There's still an awful lot of code that falls into the above categories, and it isn't going to get updated overnight.

I personally do not think it's too soon, since all currently supported versions of Node.js supports ESM. If someone is using an older version of Node.js then they aren't getting any security patches at all at this point. I don't see why we have to keep supporting those older runtimes in the beta version of our next major release.

My current "fix" for this is to pin the dependency to beta9 or below. Not thrilled about it, but updating to ES2020/ESM modules is just not an option that is meaningfully available to me right now since it would break the entire module/plugin, although certainly open to suggestions about how to solve for it if there's a workaround.

Without knowing which system your plugin is for is hard to give a good recommendation. My general take for libraries is that they should release a new major version that drops support for older versions of Node.js, and switches from CommonJS to ESM.
There are also other possible ways forward:
You could use version 2.x of node-fetch. Is there a specific reason why you are using the 3.x beta?
You could use the following shim that uses the ESM module from a CommonJS context:
const fetch = (...args) => import('node-fetch').then(module => module.default(...args))

I'd much rather keep up with the most recent versions, but don't see a good way to do it without breakage unless node-fetch offers broader compatibility with legacy ways of doing things, for the time being.

It's always a trade off between keeping up with the most recent versions and supporting legacy workflows. I personally think the best way forward is to push on with every library to help the ecosystem forward. Many packages are moving to ESM now so most likely you'll run into another one even if we revert the changes here.
As long as these changes are made in a major release, I don't see a problem since it won't break anything for anyones current workflow. They just cannot use the latest version until the upgrade...

Mostly I needed #715. :smile: But using a few of the other features / evolutions built into 3.0.
To be honest - there's nothing you wrote that I wouldn't feel the same way about in your position. I think you're right that it's beta and a major release and therefore expecting breaking changes is not unreasonable. But it does make me work more right now while I try to support my own codebase. :smile: I knew what I was getting into when I shifted to 3.0...it's on me to adapt, but also try to nudge where I can to get a bit more breathing room!
The platform in question I'm supporting is Homebridge. There's an open PR to support ESM, but it'll be a while before it gets pulled into the mainline...and that's what's creating more hand-wringing for me.
I'll try the shim you suggested out and see if I can make it work.

Dropping CommonJS is an intended consequnce of #1141. Since ESM imports in Node.js also support CJS, the change should come with no repurcussions. Besides, as new packages are published with the intention of only supporting ESM, the CommonJS version becomes less and less useful.
For information about migrating your package to ESM, see https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c

@Richienb nodejs packages is not only used in node version >= 12.
please give us low version nodejs user a choices.

@image72 may I ask why are using an older version of Node.js? Anything below version 12 is no longer receiving security updates and are end of file.

please give us low version nodejs user a choices.

Is sticking with the 2.x version of node-fetch a good enough choice? We have made other changes than just ESM which will break in Node.js versions below 12...

company have many huge online base API services, should upgrade runtime versions every 2year.
in nodejs version 12,
need Add the --experimental-modules flag when running Node.js
but, provide commonjs build is easy work. deprecate old nodejs v12 below just TSC duty

should upgrade runtime versions every 2year.

Node.js 12 was released over two years ago 🤔

need Add the --experimental-modules flag when running Node.js

This is no longer required, as long as you are running Node.js 12.17.0 or newer...

but, provide commonjs build is easy work.

There is actually some pitfalls, drawbacks, and just additional work with doing that. So we would prefer to stick with ESM...

One use case for cjs even in modern node environment is server apps build with webpack.
It is pretty common to compile react app for node to enable server-side rendering simply because jsx syntax is not native JS feature and webpack one of the most popular tools for that.
But webpack also transforms native imports to own implementation that uses require() under the hood. Which makes node app bundled with webpack incompatible with esm module imports.
Yes, it is possible to include node-fetch into bundle and transform it to cjs on app level in cases like this but:

it is not recommended in general for node target (external package might use binary files, etc.)
it is very unreliable because end-user need to analyse which esm dependencies node-fetch has and whitelist it as well from externals

I wish webpack can support esm compilation target so imports can be left untouched but it is still under development and does not seems to be released soon.

Locking b/c it's nicer to keep the discussion in one place.
(We still keep a open mind and looking for a solution - it dose not mean we will overlook this Issue)
Feel free to keep the discussion in #1227 where most of the discussion is already happening


Give different sets of users different access to data

It would be helpful if we could provide different levels of access for different users.
E.g. to simplify queries for data journalists, just provide access to kingfisher-views tables for a subset of publishers.

Internal issue - https://crm.open-contracting.org/issues/4351

 Make it easier to create new read-only users for the hosted Kingfisher database

We need to strongly define what we need here. The technical work could vary a lot based on different requirements.
So far we have:
Split data into public and private. Have a way to create read only external database users to View only AND to public data only.
Any advances?
Public & Private - probably by marking collections in Kingfisher process?
Also, a solution for this might build on #31 so check that.

I think this will need to build on #31.
If views do become generated in their own schemas to solve #31, e.g. view_collectionid or view_set_of_collection_ids, then this issue is about being able to generate a read-only user just for particular schemas.
The added complication there is that not all views contain the source data so schema-level-users might not be able to access all the raw JSON. @kindly is thinking about that as part of #31.

As I understand it, there are two user stories here:
"As a researcher, I want to have access to a set of data that I can easily query so that I can understand government contracting in a particular context"
"As a Helpdesk analyst, I want to be able to give out credentials for a database of real OCDS data without worrying about accidentally exposing data that isn't yet public so that I can share resources more widely"
Does that match your understanding @pindec ?

We've solved this for Views: https://kingfisher-views.readthedocs.io/en/latest/users.html. For Process, we can open an issue there as needed.


Scoping a unique index to a user / compound indexes

I have an issue whereby each of my lead documents stores an email address and a reference to a user ID e.g.:
{
  userId: 1234,
  email<EMAIL_ADDRESS>}

I need different users to be able to create lead documents with the same email address. But they shouldn't be able to create a lead with a duplicate email.
If I use the following in my schema:
{
  "email": {
    type: String,
    index: true,
    unique: true
  }
}

Then it doesn't respect the scoping of the index to the user so if a second user tries to create a lead with an email address already in use by a lead owned by another user, it fails validation.
I'm just wondering if it's possible to create a compound index as you would with the undocumented Collection._ensureIndex e.g.
Leads._ensureIndex(
  { userId: 1, email: 1 },
  { unique: 1 }
);

+1

+1

Hi, I'm not really sure if this should be the same issue or not, but it seems similar given that my question concerns how to make a scoped unique index.
I'm not doing much with schema-index directly. Rather, I'm using node-simpl-schema and collection2 and was referred to this repo in regards to the unique flag.
OK, so I have this in my schema for a "chat room" record; it lists which users belong to that room. A room's user list can only contain a specific user once. The problem I'm having is that with this configuration, a user cannot be in multiple rooms.
  'users': Array,
  'users.$': Object,
  'users.$._id': {
    type: String,
    unique: true,
    custom: ->
      user_id = @value
      unless Meteor.users.findOne(user_id)
        return "user_doesnt_exist" # a key added to setDefaultMessages
      false
  }

when my app starts it creates a 'lobby' room that all users are added to through the onCreateUser hook. This is working fine. Now I am trying to create direct message rooms, but it's failing because the user ids are already present in the lobby list and thus the uniqueness fails.
In this use-case it only makes sense to scope the uniqueness to that particular room record; I don't want it to look at the users in the other rooms. If this feature isn't possible, then the alternative would have to be to re-implement the uniqueness check inside the custom function (using findOne to check if the record exists).
This alternative isn't too hard, but I'm curious if this is something that is supported in this package but I'm failing to use correctly.


Workflow control / Multipass generation

I need to generate a webpage with a subject index (like in the book, but for website). Items of the index aren't known beforehand and are registered by a helper. After the creation of the list of items I'm able to generate the whole index.
However, filter can be applied on the compile stage only, and new pages can't be created there. I see that I need either more sophisticated workflow or multipass generation.
Can that be done in nanoc? Maybe with use of hooks?

I guess you use a filter to collect information because it can be applied to every existing item when they're touched anyway: during compilation. You can loop over all items in your entire site, too, and collect data before compilation. Then you wouldn't need a filter.
I have a tag index on my website. I put the generation into the preprocess block in Rules.rb:
preprocess do
  My::Environment::setup_environment(site)

  items.delete_if { |item| item[:publish] == false }

  def tag_worklog
    tags = all_tags

    tags.each do |tag|
      @items << Nanoc::Item.new(
        "",
        {
          :title => %Q{Posts tagged “#{tag}”},
          :tag => tag,
          :mtime => Time.now#parse(Date.now) # for the sitemap
          # TODO ^-- this is the wrong mtime actually, it should be the time of the last item change
        },
        "/posts/tags/#{tag}"
      )
    end

    @site.tags = tags
  end

  tag_worklog
end

The actual all_tags method is a helper method in lib/:
def all_tags
  posts = sorted_posts
  tags = Set.new # unique items only

  posts.each do |post|
    post[:tags].each do |tag|
      tags.add(tag)
    end unless post[:tags].nil?
  end

  return tags.to_a.sort
end

This creates items on the fly before compilation, so it's possible to use compile and routing rules on the items just as if they were file-based:
compile '/posts/tags/' do
  # tag index *is* a file, actually, looping over all tags
end

compile '/posts/tags/*/' do
  # this matches the items we've just created
end

Thank you for the answer.
Unfortunately, this approach don't work in my case, since items for the index are defined in the text, not in the metadata. I can't use post[:tags] to get items for the index. I use helper that logs items and also creates <a id=...> HTML tags. (Firstly I wrote filter, it's actually helper). I could write custom parser and use it in the preprocess stage, but I look for a simpler way.
The same problem exists in LaTeX which uses makeindex for the generation of index. For the full build it requires several runs. First updates index file, second incorporates created file. If in the second generation index file is changed, then there is third generation and so on, until everything stabilizes. Now I see that I can try to emulate this behavior using guard. I'll try it, but it would be good if this would work from the box.

Ah well, if it's in the contents, then I understand why you'd need something similar to LaTeX's makeindex indeed!

On 04 Feb 2015, at 01:47, Basil Peace<EMAIL_ADDRESS>wrote:
Thank you for the answer.
Unfortunately, this approach don't work in my case, since items for the index are defined in the text, not in the metadata. I can't use post[:tags] to get items for the index. I use helper that logs items and also creates  HTML tags. (Firstly I wrote filter, it's actually helper). I could write custom parser and use it in the preprocess stage, but I look for a simpler way.
The same problem exists in LaTeX which uses makeindex for the generation of index. For the full build it requires several runs. First updates index file, second incorporates created file. If in the second generation index file is changed, then there is third generation and so on, until everything stabilizes. Now I see that I can try to emulate this behavior using guard. I'll try it, but it would be good if this would work from the box.
—
Reply to this email directly or view it on GitHub https://github.com/nanoc/nanoc/issues/527#issuecomment-72768803.

There’s no easy way to do this in nanoc, because what you’d like to achieve doesn’t fit in nanoc’s conceptual compilation flow, where new items cannot be created after compilation has started.
I’d suggest creating a separate rake task for generating the index. A full compilation would then invoke nanoc, the index generation script, and nanoc again, pretty much the way LaTeX would do it.
This is something I’d like to address for nanoc 4.

Also, please use the nanoc forum to get support. GitHub Issues is dedicated purely to issues and pull requests.
I’ll close this issue here for now.


Bugfix: Ignore empty discount/addon arrays

The Braintree API is just fine with accepting an empty array – so FakeBraintree
should be fine with this as well.
Example:
Braintree::Subscription.update(subscription_id, discounts: {
  add: [],
  update: [{ existing_id: some_id, amount: some_amount }]
})

This previously failed because FakeBraintree would stop at the add key since
it can be found and isn't nil. After this patch, FakeBraintree continues on the
empty array and correctly updates the discount.

Any feedback on this?

Sorry @clemens been a bit behind on fake_braintree stuff. Merging!


error

try the code but itś not working for me. i tried the code with Chrome and i get the following output if i running the script. do you have sugestions to run the code and fixing the errors?
Opening browser...
Traceback (most recent call last):
File "facebook-connections.py", line 127, in
fb_login()
File "facebook-connections.py", line 12, in fb_login
browser.get('https://www.facebook.com/')
File "/root/anaconda2/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 248, in get    self.execute(Command.GET, {'url': url})
File "/root/anaconda2/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py", line 236, in execute    self.error_handler.check_response(response)
File "/root/anaconda2/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py", line 192, in check_response   raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: Runtime.executionContextCreated has invalid 'context': {"auxData":{"frameId":"5192.1","isDefault":true},"id":1,"name":"","origin":"://"}
(Session info: chrome=54.0.2840.71)
(Driver info: chromedriver=2.9.248304,platform=Linux 4.4.0-36-generic x86_64)

Hi @k9team3, apologies for the massive delay. I had notifications off and haven't touched this in almost 2 years. The script has been updated to use python3 and Google Chrome as the browser. Could you try it again? Let me know if any more issues


Misc moving from /support/

/support/more-dashboard-apps/cloudflare-custom-pages/configuring-custom-pages-error-and-challenge/
/waf/tools/custom-error-pages/
/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors/
/fundamentals/basic-tasks/troubleshooting-crawl-errors/
/support/troubleshooting/general-troubleshooting/troubleshooting-surges-or-spikes-in-web-traffic/
/fundamentals/basic-tasks/troubleshooting-surges-or-spikes-in-web-traffic/

Closing out as there hasn't been any activity on this for 3+ months


feat!: v3

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow disabling Kotlin support when org.jetbrains.kotlin.jvm is present

Feature description
I am adding Kotlin files to an existing Micronaut Java project. The project depends heavily on Lombok, which Kapt is incompatible with (simply stops it from working). I would like to use the Kotlin classes independent of Kapt/Micronaut rather than remove Lombok from the project where it is heavily used (a compromise of disabling Micronaut features for Kotlin). However it seems Micronaut Gradle plugin will force itself to require kapt if org.jetbrains.kotlin.jvm is present in the build.gradle file, regardless of if it's supposed to be independent from Micronaut or not.
Would it be possible to have a flag that disables the MicronautKotlinSupport module even if Kotlin is a dependency in Gradle?

Nevermind, I was able to solve my Lombok issue by putting this in the Gradle file
kapt {
    keepJavacAnnotationProcessors = true
}

Stack Overflow answers were inaccurate/outdated, newest documentation is here


Add a Next Button in Quiz.

The quiz section has only 1 button "SUBMIT" to go to both next question and submit the quiz.
Proposed Changes

Make a new button Next to go to the next question till their is no question left and at the end question ,Submit button should be used to submit the quiz.

Hello, can you assign to this?

Assigned!

can you assign me this issue?

Assigned!


CLOUD-59081 Infinite polling

@keyki @biharitomi pls review

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/cloudbreak-pull-request/2648/

Refer to this link for build results (access rights to CI server needed):
http://ci.sequenceiq.com//job/mock-integration-test/139/


Update definition of optimizer in introduction_guide.rst

I looked at the guidelines and this pull request does not fix a bug, but simply make sure that the tutorial run with the code base from the version 1.5.3. Hence, I do not think it is useful to create another branch for this.
Please let me know if I have missed any guidelines.
sorry that I closed / reopened the issue, it is my first pull request.
What does this PR do?
The guide was a bit misleading, and following it naivly would make that the code is not runnable, because the training requires an optimisers. My solution is to put the optimiser chunk higher in the explainations.

Fixes #<issue_number>
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[ ] 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 internal minor changes/refactorings)

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

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

Did you have fun?
Make sure you had fun coding 🙃

Just noticed, there is a PR already trying to achieve mostly the same thing: #10519


[#234] Add help function for kscript

#234
What happened 👀
Old bash script have --help function which prints the instruction of how to use the script to create a new project but new script doesn't have one.
Insight 📝
Add additional parameter and check if the passed parameter is help and show message
Proof Of Work 📹

@ryan-conway @chornerman @Wadeewee Updated 🚀.


fix bad taste

What is the purpose of the change
fix bad taste
issue url
https://github.com/apache/dubbo/issues/5919

@qiaolin-li  thanks for your PR. I just double check this change and notice that the previous code rely on exceptions is not empty. so which means this change is not equivalent to previous code.

I don't understand what you mean..

sorry @qiaolin-li , I think it's my mistake when I first time look at the issue you raised.
I test this change in my local, It's possible if one stream open fail, so exceptions map can be empty, so we can't print , possible causes: in error message


Fix matplotlib with wide parameters

Summary
This commit fixes issues reported with long parameter lists in the mpl
drawer. The issue is that when the length of the parameters list exceeds
20 characters the mpl drawer removes the parameters. Multiple attempts
have attempted to address this issue (#2994 #3353) by just increasing
that limit. But this doesn't actually solve the problem because the
boxes are fixed width so the parameters just exceed the width of the
boxes. The proper way to fix this is to dynamically
In addition this whole problem is primarily caused because we don't
round any parameter values. This commit rounds the parameters so that we
rarely have to scale to have super wide parameter lists.
Details and comments
Fixes #2822

I've been testing this PR with this circuit code:
from qiskit import QuantumCircuit

qc = QuantumCircuit(2)
qc.x(0)
qc.y(1)
qc.h(0)
qc.u3(3.1234, 2.1234, 1212311.66, 1)
qc.u2(321.21231123412, 17655.789879879, 0)
qc.barrier(1)
qc.u3(323.131232131, 1231232.1412, 3.14159, 1)
qc.draw(output='mpl', filename='test.png')

which after this PR returns:

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: mtreinish:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: mtreinish:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


WIP: First pass at admin resources

This is a re-write of admin resources to a design that minimizes dependencies and separates the REST endpoints from the UI rendering.  Admin REST endpoints are implemented as simple Java classes using naming conventions to map the methods to REST paths.  A basic server implementation using RxNetty is provided as a separate project and can easily be replaced by the JDK's internal web server or Jetty with a simple servlet.
To add admin resources to an application just add new AdminModule() and RxNettyAdminModule() to Karyon.
Karyon.createInjector(
    ArchaiusKaryonConfiguration.builder()
        .build(),
    new AdminModule(),              // Picks up the modules
    new RxNettyAdminModule()  // Serves REST endpoints via RxNetty
    )

To add a custom REST endpoint create a class using the following convention,
@Singleton
public class MyResource {
    @Inject
    MyResource(/* Inject anything that is needed by MyResource*/) {
    }

    // This will map to : <controllername>/
    public List<String> get() {
    }

    // This will map to : <controllername>/:id
    public String get(String id) {
    }

    // This will map to : <controllername>/:id/subs
    public List<String> getSubs(String id) {
    }

    // This will map to : <controllername>/:id/subs/:subid
    public String getSubs(String id, String subid) {
    }
}

Create a module, the module will be auto-loaded if AdminModule is installed,
@ConditionalOnModule(AdminModule.class)
public final class MyAdminModule extends AbstractAdminModule {
    @Override
    protected void configure() {
        bindAdminResource("my").to(MyResource.class);
    }
}

NetflixOSS » karyon » karyon-pull-requests #66 ABORTED

NetflixOSS » karyon » karyon-pull-requests #67 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #68 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #69 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » karyon » karyon-pull-requests #70 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #71 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #72 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » karyon » karyon-pull-requests #74 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #76 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » karyon » karyon-pull-requests #77 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #78 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #79 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #80 SUCCESS
This pull request looks good


Page subclasses fail to use PageManager on current Django stable/1.10.x

As reported by @pjstevns, Django commit https://github.com/django/django/commit/21f18e5372fe86090a82b696f3208e56c6a2aa80 breaks the behaviour of the objects manager on subclasses of Page - it now gets set to a plain django.db.models.manager.Manager instance instead PageManager, causing numerous test failures anywhere that the custom PageManager / PageQuerySet methods are used.
A minimal models.py that reproduces the change of behaviour:
from __future__ import absolute_import, unicode_literals

from django.db import models
from django.utils import six
from treebeard.mp_tree import MP_Node, MP_NodeQuerySet

class PageQuerySet(MP_NodeQuerySet):
    pass

class BasePageManager(models.Manager):
    def get_queryset(self):
        return PageQuerySet(self.model).order_by('path')

PageManager = BasePageManager.from_queryset(PageQuerySet)

class PageBase(models.base.ModelBase):
    """Metaclass for Page"""
    def __init__(cls, name, bases, dct):
        super(PageBase, cls).__init__(name, bases, dct)

        # Override the default `objects` attribute with a `PageManager`.
        # Managers are not inherited by MTI child models, so `Page` subclasses
        # will get a plain `Manager` instead of a `PageManager`.
        # If the developer has set their own custom `Manager` subclass, do not
        # clobber it.
        if not cls._meta.abstract and type(cls.objects) is models.Manager:
            PageManager().contribute_to_class(cls, 'objects')

class Page(six.with_metaclass(PageBase, MP_Node, models.Model)):
    title = models.CharField(max_length=255)
    objects = PageManager()

class EventPage(Page):
    date = models.DateField()

Pre-https://github.com/django/django/commit/21f18e5372fe86090a82b696f3208e56c6a2aa80 behaviour:
>>> from core.models import Page, EventPage
>>> EventPage.objects
<django.db.models.manager.BasePageManagerFromPageQuerySet object at 0xb66eacec>

New behaviour:
>>> from core.models import Page, EventPage
>>> EventPage.objects
<django.db.models.manager.Manager object at 0xb64c670c>

The inheritance situation here is quite complicated: Model is subclassed as treebeard's MP_Node (abstract), which sets the manager MP_NodeManager. MP_Node is subclassed as Page (concrete), which sets PageManager. Page is then subclassed as EventPage (MTI), and the PageBase metaclass attempts to force the use of PageManager on that too.
Interestingly, if I take MP_Node out of the chain, the regression happens further back in time in https://github.com/django/django/commit/ed0ff913c648b16c4471fc9a9441d1ee48cb5420 - which points to the possibility that this was an intended change of behaviour for 1.10 but the change was masked by https://code.djangoproject.com/ticket/27073.
(cc @timgraham in case this is a legitimate Django 1.10.1 regression, rather than Wagtail misbehaving - I'll do some more unpicking to try and figure out which...)

Better to \cc @loic if you need some expertise about the intentions of these changes.

Thanks @timgraham.
I'm now 99% certain this can be chalked up to bad behaviour on Wagtail's part :-) We're relying on metaclass hacking to ensure that MTI subclasses of the Page model retain the custom manager defined on Page - https://github.com/django/django/pull/6175 breaks this ability (although it seems that certain quirky inheritance patterns can mask this and cause our custom manager to appear after all, which is why we didn't spot this on 1.10).
I now realise that I can achieve what I need by introducing an abstract superclass of Page and setting the manager there instead. So, since the metaclass hack is avoidable, I think it's entirely reasonable for Django to not support it across versions.
The minimal test case I ended up with, for the record:
from __future__ import absolute_import, unicode_literals

from django.db import models
from django.utils import six

class CustomManager(models.Manager):
    pass

class ManagedModelBase(models.base.ModelBase):
    def __init__(cls, name, bases, dct):
        super(ManagedModelBase, cls).__init__(name, bases, dct)
        CustomManager().contribute_to_class(cls, 'objects')

class Page(six.with_metaclass(ManagedModelBase, models.Model)):
    pass

class EventPage(Page):
    pass

# old behaviour
>>> from core.models import EventPage
>>> EventPage.objects
<core.models.CustomManager object at 0xb6663f6c>

# new behaviour
>>> from core.models import EventPage
>>> EventPage.objects
<django.db.models.manager.Manager object at 0xb63ff5ec>


Update 2015-09-11-sandboxing.md

The post contained so much stuff that is just wrong and outdated, but people kept referring to it and asked me, why /usr/local isn't mounted. Let's update it to reflect the current situation better.

@ensonic FYI.

Thanks for the update.


Fix ESLint plugin recommended config

Greetings,
this fixes issue #2953

Codecov Report

Merging #2954 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2954   +/-   ##
======================================
  Coverage    67.6%   67.6%
======================================
  Files         146     146
  Lines        5338    5338
======================================
  Hits         3609    3609
  Misses       1729    1729

Impacted Files
Coverage Δ

packages/eslint-plugin-jest/src/index.js
100% <ø> (ø)
:white_check_mark:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d12e4a4...70fbe27. Read the comment docs.

thanks!


lib/constants, lib/utils missing

It seems that some files were not commited to git.

fixed. these were old and have been since merged into lib/rtrace.rb


Add an option to toggle visuals in the moving navigation agents benchmarks

To make it easier to just check CPU usage of the navigation system itself, without visuals. The visuals are enabled by default, like they are in the physics benchmarks, but I can make them disabled if desired. EDIT: They are now off by default.

This should be applied to the physics benchmarks as well. I'd also suggest parsing a command-line argument instead of using a variable that needs to be changed manually in the source code, e.g. --debug-visuals.
There's a system parsing CLI arguments into member variables if they exist with a arg_ prefix in main.gd: https://github.com/godotengine/godot-benchmarks/blob/main/main.gd#L5-L10

I added a --visualize command-line argument that enables visualizations in the physics and navigation benchmarks, and it's set to false by default.


[BUG] MAP_AT_K cross check

Description

Hi,
I was doing some calculations for MAP_AT_K off SAR example: https://github.com/Microsoft/Recommenders/blob/master/notebooks/00_quick_start/sar_movielens.ipynb
and noticed the difference between MAP and Precision@K: 0.105815 and 0.326617.
The Precision@K is re-creatable at 0.326617
######### Precision@K
new_df = pd.merge(top_k, test, how='left', on=['UserId','MovieId'])
from dplython import (DplyFrame, X, select, sift, head, arrange, mutate, group_by, summarize, DelayFunction)
new_df = DplyFrame(new_df)
where = DelayFunction(np.where)
new_df = new_df >> mutate(Relevant = where(X.Rating > 0, 1, 0))
dd2 = new_df >> group_by(X.UserId) >> summarize(mm = X.Relevant.sum()/10)
dd2['mm'].mean()
######### End of Precision@K
But MAP might open for a discussion:
######### MAP 1
new_df = pd.merge(top_k, test, how='left', on=['UserId','MovieId'])
from dplython import (DplyFrame, X, select, sift, head, arrange, mutate, group_by, summarize, DelayFunction)
new_df = DplyFrame(new_df)
where = DelayFunction(np.where)
new_df = new_df >> mutate(Relevant = where(X.Rating > 0, 1, 0))
new_df = new_df >> arrange(X.UserId, -X.prediction)
new_df['ForCount'] = 1
new_df['cumsum'] = new_df.groupby('UserId')['Relevant'].transform(pd.Series.cumsum)
new_df['cumsum2'] = new_df.groupby('UserId')['ForCount'].transform(pd.Series.cumsum)
new_df['prec'] = new_df['cumsum'] / new_df['cumsum2']
new_df['prec'] = new_df['prec'] * new_df['Relevant']
dd2 = new_df >> group_by(X.UserId) >> summarize(ss = X.prec.sum())
dd2['prec2'] = dd2['ss'] / 10
dd2['prec2'].mean()
######### End of MAP 1
The above lines had MAP calculated as 0.2271
Instead of dividing the precision rates with 10, if we divide it with total Movies rated by user in test group like below:
############## MAP 2
new_df = pd.merge(top_k, test, how='left', on=['UserId','MovieId'])
from dplython import (DplyFrame, X, select, sift, head, arrange, mutate, group_by, summarize, DelayFunction)
new_df = DplyFrame(new_df)
where = DelayFunction(np.where)
new_df = new_df >> mutate(Relevant = where(X.Rating > 0, 1, 0))
new_df = new_df >> arrange(X.UserId, -X.prediction)
new_df['ForCount'] = 1
new_df['cumsum'] = new_df.groupby('UserId')['Relevant'].transform(pd.Series.cumsum)
new_df['cumsum2'] = new_df.groupby('UserId')['ForCount'].transform(pd.Series.cumsum)
new_df['prec'] = new_df['cumsum'] / new_df['cumsum2']
new_df['prec'] = new_df['prec'] * new_df['Relevant']
dd2 = new_df >> group_by(X.UserId) >> summarize(ss = X.prec.sum())
dd3 = test >> group_by(X.UserId) >> mutate(nn = 1) >> summarize(m = X.nn.sum())
dd4 = pd.merge(dd2, dd3, how='left', on = ['UserId'])
dd4['prec2'] = dd4['ss'] / dd4['m']
dd4['prec2'].mean()
################ End of MAP2
Then the MAP rate is the same as given in the example: 0.1058
Question is why do we divide by total rated Movies in test set only? For UserId = 1, this from test set is 69 but in total he/she rated 272 movies. Why do we divide by 69 and not 272?
Reference: I couldn't get to your advised reference https://people.cs.umass.edu/~jpjiang/cs646/03_eval_basics.pdf so tried a different source here:
http://sdsawtelle.github.io/blog/output/mean-average-precision-MAP-for-recommender-systems.html
which seems to agree with one from Stanfor Uni at:
http://web.stanford.edu/class/cs276/handouts/EvaluationNew-handout-6-per.pdf
I may miss out some important details too.
Thanks,
In which platform does it happen?
 CPU

How do we replicate the issue?
 I have pasted the codes using Dplython module.

Expected behavior (i.e. solution)

Other Comments

thanks @seancaodo, we will take a look

@seancaodo Thanks for the ask and discussion. Greatly appreciate it. 👍

Following your code, the MAP calculated is 0.2212. I think the discrepancy comes from dd2['prec2'] = dd2['ss'] / 10 where your calculation is based on a division by k, whilst our implementation is based on a division by the number of ground truth items in the testing data. So, when I changed line 588 in this from df_sum_all["map"] = df_sum_all.apply(lambda x: (x.precision / x.actual), axis=1) to df_sum_all["map"] = df_sum_all.apply(lambda x: (x.precision / k), axis=1) it gave me 0.2212.
Our implementation referenced the one in PySpark - we try to make sure the two versions of Python evaluator and PySpark evaluator produce matched results. See here for details. In this implementation, it uses the actual number of ground truth items for normalization.
The link to the reference was not valid. We will fix it.

@yueguoguo  Hello, I just figured it out too. We were posting in parallel 👍. Thanks very much for the fast response.
I think we can close the threat. A minor question left for me to think is why we divide by number of ground truth for each user as number split by test, train sets. If we scale up or down the size of these two sets, the MAP rates will differ I suppose. It's minor I think as we use these for comparisons between algorithms anyway.


Videos showing as anchors

{
  "kind": "Anchor",
  "label": "https://video.parler.com/Nr/4w/Nr4wNawMApbI_small.mp4",
  "location": "https://video.parler.com/Nr/4w/Nr4wNawMApbI_small.mp4",
  "id": "Nr4wNawMApbI"
}

Data is still good but the kind is wrong :/

solved in multithread branch


Adding Options to MarginBalance due to missing fields in response

Adding Options around the fields I've found could be absent from responses from the Schwab Trader API. If there is an easier way to get around missing fields, I'm all ears!
Great crate!

Could you provide a test case to Accounts_real.json? If possible, please remember to remove any sensitive information.

Thanks for contribution. Merging this PR for now.


Upgraded log4j from 2.15.0 to 2.16.0 (CVE-2021-45046)

For resolve problem of Security Vulnerabilities (CVE-2021-45046)
https://logging.apache.org/log4j/2.x/security.html

Thanks!

Is there a release with this fix?

2.1.17 should be released soon.

2.1.17 was released some hours ago, but I don't see the artifacts in maven central.


File 'C....idea' specified for property 'ideaExtension.path' is not a file.

Expected Behavior
Folders should recognized as valid input for ideaExtension.path on Windows
Observed Behavior
Even if the specified folder is valid, detekt failes. Reason is that it want's a file were a folder is needed.
Steps to Reproduce
Configure detekt gradle plugin on a windows machine.
    detekt {
        toolVersion = "1.2.2"
        buildUponDefaultConfig= true
        idea {
            path = "$project.rootDir/.idea"
            codeStyleScheme = "$project.rootDir/config/codestyleConfig.xml"
            inspectionsProfile = "$project.rootDir/config/inspectConfig.xml"
            report = "$project.rootDir/build/detekt/report"
            mask = "*.kt"
        }
}

This configuration (plus the usual plugin and dependencies) Will fail with the message described in the title.
Your Environment

Version of detekt used: 1.2.2
Version of Gradle used (if applicable): 6.0.1
Operating System and version: Windows 10

Suggestion: Use InputDirectory instead InputFile in https://github.com/arturbosch/detekt/blob/ffbd6e119105f6e07d686bc5632f7b531bf91a59/detekt-gradle-plugin/src/main/kotlin/io/gitlab/arturbosch/detekt/extensions/IdeaExtension.kt#L14
See https://docs.gradle.org/current/javadoc/org/gradle/api/tasks/InputDirectory.html

with this bug you can't run either detektIdeaFormat or detektIdeaInspect

@3flex, I would suggest this as a bug, as opposed to improvement.

Is there a workarround, because there are not so many +1. Does people are using this feature ?

The workaround is to use the inspect.sh and format.sh scripts from the IntelliJ installation yourself.
detekt just provides Gradle wrapper tasks for them.

Does people are using this feature ?

Not many I'm afraid as this feaure must have been broken for a long time now.
I've worked on a fix for this. Just need to find time to commit everything.

+1


No worky on Arch Linux

My friend is trying to use the CLI and GUI script on Arch, and it tells him the username and password have been saved on NetworkManager, but when trying to connect to the eduroam WIFI it goes through an infinite loop of asking for the credentials which never actually connect to the network.
Please help.

that means the credentials are not correct. Ensure they are correct, do the same credentials work on e.g. android?

Everything works fine on devices using Windows and Android, only on Arch Linux, and it's not just one person, I have another friend with the same issue.

please give the output of sudo journalctl -u NetworkManager (or could be called network-manager) when this happens

closing due to no response

Hello, having the same issue. I have tried the program with the exact same credentials on andriod and on arch. The only place where it doesnt connect me is on arch.
Journalctl output:
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2560] audit: op="connection-update" >
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2568] policy: auto-activating connec>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2591] device (wlp1s0): Activation: s>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2593] device (wlp1s0): state change:>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2867] device (wlp1s0): set-hw-addr: >
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2899] device (wlp1s0): state change:>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2905] device (wlp1s0): Activation: (>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2906] device (wlp1s0): state change:>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2926] device (wlp1s0): state change:>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2935] device (wlp1s0): state change:>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2941] device (wlp1s0): Activation: (>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2942] Config: added 'ssid' value 'ed>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2942] Config: added 'scan_ssid' valu>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2943] Config: added 'bgscan' value '>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2943] Config: added 'key_mgmt' value>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'proto' value 'R>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'pairwise' value>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'group' value 'C>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'password' value>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'eap' value 'TTL>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'fragment_size' >
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2944] Config: added 'phase2' value '>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2945] Config: added 'ca_cert' value >
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2945] Config: added 'altsubject_matc>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2945] Config: added 'identity' value>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2945] Config: added 'anonymous_ident>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.2945] Config: added 'proactive_key_c>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.3039] device (wlp1s0): supplicant in>
sep 11 11:38:59 ricoyogur NetworkManager[493]:   [1726047539.3039] device (p2p-dev-wlp1s0): suppl>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.7799] device (wlp1s0): supplicant in>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.7800] device (p2p-dev-wlp1s0): suppl>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.7841] device (wlp1s0): supplicant in>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.7841] device (p2p-dev-wlp1s0): suppl>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.8010] device (wlp1s0): supplicant in>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.8010] device (p2p-dev-wlp1s0): suppl>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.9852] device (wlp1s0): supplicant in>
sep 11 11:39:00 ricoyogur NetworkManager[493]:   [1726047540.9854] device (p2p-dev-wlp1s0): suppl>
sep 11 11:39:01 ricoyogur NetworkManager[493]:   [1726047541.0851] device (wlp1s0): supplicant in>
sep 11 11:39:01 ricoyogur NetworkManager[493]:   [1726047541.0853] device (p2p-dev-wlp1s0): suppl>

I have a similar issue:
Error: Connection activation failed: Secrets were required, but not provided Hint: use 'journalctl -xe NM_CONNECTION=52cae50c-8dbf-4d53-ad7d-93a7a466660f + NM_DEVICE=wlan0' to get more details.


Update Stop-SPOTenantRename.md

Added links to related cmdlets

@dariomws @tseward @get-itips

@tiburd Please merge this PR. Thanks

Docs Build status updates of commit 623c860:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Stop-SPOTenantRename.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


My first revup foo

Topic: foo

Reviews in this chain:
└https://github.com/f440/revup/pull/1 My first revup foo

#
head
base
diff
date
summary

0
e41314ad
22f331e5
diff
Dec 6 10:25 AM
1 file changed, 1 insertion(+)


QR Codes not working in Laravel 5.4.

I keep getting invalid QR codes when using default settings on Laravel 5.4.
Here is my code:
`/**
* Generate a new 2FA key.
*
* @return void
*/
public function setup2FA(Google2FA $google2fa)
{
$user = Auth::user();
$google2fa_secret = $google2fa->generateSecretKey();
$google2fa_url = $google2fa->getQRCodeGoogleUrl(
config('app.name', 'Laravel'),
$user->email,
$user->google2fa_secret
);
    return view('2fa.setup', ['google2fa_secret' => $google2fa_secret, 'google2fa_url' => $google2fa_url]);
}`

I should note that I am using the Microsoft Authenticator app on Windows 10 mobile, but my coworker is having the same issue using Google Authenticator on Android.
Also the Secrets themselves work just fine, if entered manually.
What gives?

I'm using this in a brand new test 5.4 projects and it's generating both the getQRCodeGoogleUrl() and getQRCodeInline() QR codes. Of course, to use the latter, you need to composer require "bacon/bacon-qr-code":"~1.0" too.

I figured it out. My mistake. I was tired and missed an error in my code above.
And as you can see from above, I used the Google url variant, and it did generate it just fine.
I just didn't give it the actual secret, because of a mistake in my code.
Closing this issue now.


Feature: Add oom monitor for cgroupv2.

Add oom monitor for cgroupv2.

@kzys @dims @caniszczyk @tianon Hi, cgroup v2 version of oom monitor is pushed, please review, thx!

#229 Implemention of cgroup v1 oom monitor is here.

@mxpv @jsturtevant @Burning1020


Restarting Cilium pods sometimes disconnects the network of CNI managed pods

Restarting Cilium pods sometimes disconnects the network of CNI managed pods:
Characteristics of the failure

pod egress network traffic no longer makes it onto the VXLAN (cilium_vxlan) (like, say, to CoreDNS pods addressed directly from the pod within the same Pod network address space)
pod ingress network traffic no longer makes it to the pod.

For example, this problem can cause the Pod to fail liveness probes sent by the kubelet with the following message: Readiness probe failed: Get http://<IP_ADDRESS>:9093/-/ready: dial tcp <IP_ADDRESS>:9093: connect: no route to host

The problem persists even if the cilium-agent container is restarted within the pod
The problem only seems to be resolved by deleting the pod and allowing a new one to be scheduled in its place

The problem can be caused by deleting the pod and allowing a new Cilium to schedule on the node (like in kubectl -n kube-system rollout restart daemonset/cilium)
The problem can be resolved by deleting the pod and allowing a new Cilium pod to be scheduled on the node. 🤪

Characteristics of the pods

pods are colocated on the same node as the "bad" cilium pod
pods are using CNI and successfully receive a pod IP
pods usually have K8s Network Policy applied (L3/L4)
pods sometimes are CNI pods which have no network policy applied to their namespace
pod network address space is within <IP_ADDRESS>/16 with a /24 assigned to each node

Cluster characteristics:

~115 worker nodes
~700 network policy objects
~137 namespaces
~2879 pods
~198 k8s service objects

General Information

Cilium version (run cilium version)

Client: 1.6.7 d26878333 2020-03-03T22:55:12-08:00 go version go1.12.17 linux/amd64
Daemon: 1.6.7 d26878333 2020-03-03T22:55:12-08:00 go version go1.12.17 linux/amd64

Kernel version (run uname -a)

Linux cpt-worker-ethos11prodor1-603.ethos.adobe.net 4.19.84-coreos #1 SMP Tue Nov 19 20:51:06 -00 2019 x86_64 x86_64 x86_64 GNU/Linux

Orchestration system version in use (e.g. kubectl version, Mesos, ...)

Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.0", GitCommit:"70132b0f130acc0bed193d9ba59dd186f0e634cf", GitTreeState:"clean", BuildDate:"2019-12-07T21:20:10Z", GoVersion:"go1.13.4", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.8", GitCommit:"ec6eb119b81be488b030e849b9e64fda4caaf33c", GitTreeState:"clean", BuildDate:"2020-03-12T20:52:22Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"linux/amd64"}

Link to relevant artifacts (policies, deployments scripts, ...)
Upload a system dump (run curl -sLO https://github.com/cilium/cilium-sysdump/releases/latest/download/cilium-sysdump.zip && python cilium-sysdump.zip and then attach the generated zip file)

How to reproduce the issue

You may change the cilium config or not and issue a restart like so:
kubectl -n kube-system rollout restart daemonset/cilium
Some previously healthy pods will start failing health checks.
Some newly scheduled pods will crash and/or fail health checks
Restarting Cilium on the nodes where this is occurring may resolve the issue.

Our initial assessment on this is that there are potentially two issues happening here:

https://github.com/cilium/cilium/pull/10630  (it is highly likely that you hit this issue, and it was addressed in Cilium 1.6.8 release).   Restarting the Cilium pod will not fix the issue, and so upgrading to 1.6.8 to get this fix is key.
During the analysis we felt like there were certain scenarios on cilium restart + restoration of endpoints where Cilium may not properly retry.  We filed https://github.com/cilium/cilium/issues/11256 .    The workaround for this would be to restart the Cilium pod.   However, with further analysis, it seems like persistent connectivity lost due to this issue is quite unlikely, as the scenarios were this happen are less likely than we had originally thought, and such scenarios are not likely to persist.   We'll still do analysis on this issue as we believe things should be improved here, but this is a much less to cause problems than we originally thought.


Remove hardcoded header logging in spray client

https://github.com/paypal/squbs/blob/master/squbs-httpclient/src/main/scala/org/squbs/httpclient/HttpClientManager.scala#L77
If there are other places, those should be masked as well.

We will be addressing optional header logging for Akka Http client in 0.9.0 with https://github.com/paypal/squbs/issues/247.

We are removing it just in case it may contain potential sensitive information.


Update some deprecated uses of libraries

Coverage increased (+0.09%) to 88.684% when pulling f656a850c497d95a22a81e2ae53c31283b5494fe on deprecations into 7b87faec7fc6f2d6ee88a0090a622968ab26d9a9 on master.

We want to seed the pseudo-random number generator with a seed (i.e., do default_rng(seed) instead of default_rng()) to get reproducible results (e.g., when we instantiate a random graph then check its properties).
Whether seed is 42, 1, or anything usually doesn't matter much. But sometimes we might prefer a random draw over another (e.g., a seed that generates a connected graph over a disconnected one).

Approved. You can merge.
Thanks a lot

Thank you!


Create server function not doing anything

I login, and do everything right. But when I call it, nothing happens, and I entered in all of the info correctly. The createUser works too, so it is just the createServer function.

The createServer function works fine, please join our discord server and post your code there.


Some values started to show zero

Some of the values started to show ZERO value. They were working before and studently became zero.
JK BMS power / current / voltage / capacity / balance current / temperatures. Rest of parameters are still reported correctly
20:19:38 INFO [sampling] battery1: BmsSampl(0.0%,U=0.0V,I=0.00A,P=0W,q=21102.6Ah/0,mos=0.0°C)
20:19:39 INFO [sampling] battery1 volt=3324,3324,3323,3323,3322,3322,3321,3323,3321,3324,3323,3324,3323,3323,3323,3322 temp=[0.0, 0.0]

did this happen after an update?

Hi Fabian,
Issue was fixed by changing / re-set the battery capacity in the BMS and
when reconnected it started to send correct data again.
Not sure what caused it, it was working fine no update was made in that day
and it just suddenly stopped sending some values, was sending zero value
for certain parameters.
Before fixing the issue, I downgraded to previous versions with no succes,
so it was something that happened in the BMS. BMS on local app was showing
correct values though.
Best regards,
Alin.
On Thu, Sep 28, 2023 at 6:58 PM Fabian @.***> wrote:

did this happen after an update?
—
Reply to this email directly, view it on GitHub
https://github.com/fl4p/batmon-ha/issues/143#issuecomment-1739608732,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6BI7RXTAHKLNCQOFANDYL3X4WNDRANCNFSM6AAAAAA5ICK4OM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Progressive Web App

We can leverage a progressive web app instead of standalone mobile apps. The language should not matter too much, but we may want to leverage JS or swift-native.
The app should expose the necessary fields to post a cap message and will generate fields based on a profile for the user.
Once the go app accepts a post of the data, we can wire up a full e2e client/server system.

Seems like a good way to reach the most clients in a first pass.


Fixes race condition encountered when diconnecting from RTM API

The race condition is described in #302 including a small program that allows to reproduce it.
Closes nlopes/slack/#302

LG thanks.


Look for branches that are literally the word main

Description
When finding the default git branch, use a regex that matches only the word main, instead of any branch that has the substring main in it.
Motivation and Context
I have a repo with many other branches that contain the string main,
but our default branch is still master.  This grep was seeing those other branches
and deciding that my default branch was main.
How Has This Been Tested?
I tested this change on the repository I described above, and it correctly decided my default branch was master again.
Screenshots (if appropriate):
Types of changes

[X] 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)

Checklist:

[X] My code follows the code style of this project.
[X] If my change requires a change to the documentation, I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
[ ] I have added tests to cover my changes, and all the new and existing tests pass.

I didn't see any existing tests for the git aliases (or any aliases).  Should I add a new test file?

Hi @william-richard,
I don't think you caught all of my previous comment.
I believe I showed that \smain\s does not work, and was waiting for you to update the PR.
I think the "full line" matcher is the way to go ...

Apologies @davidpfarrell - I thought I had pushed up the full line match commit, but didn't notice the error message and moved onto something else.
I've been running with the full line match version for about 2 weeks now, and I agree, I think it's the way to go forward.


Implement snapshot repository cleanup

Relates to https://github.com/elastic/elasticsearch/pull/43900

Integration test failures due to PinnedQuery missing SkipVersion attribute

cherry-picked to master


Can not set topcontraint for menuviewcontroller in Swift 3

What is the alternative to this line in Swift 3 with for uacaps PageMenu?
pageMenu?.menuScrollViewTopConstraint.constant = topView.frame.size.height
I can't seem to find an alternative that lets me start the menu not at the top of the view.

Hey @wessamabdrabo, did you ever find a solution for this? I'm looking for similar functionality (i.e. my menu bar starting at say 44 points from the top of the screen).


Meteoric + plugin.google.maps don't work together.

Hello,
I wanted to tell you that it's impossible to use google maps plugin with Meteoric (https://github.com/wf9a5m75/phonegap-googlemaps-plugin). I don't know why but I can use it in a blanck meteor project, but I got a blank map in a meteoric project.
Do you know what is the problem ?
If I find an issue, i'll come back to give it to you.

It may just a CSS/display issue, I've used that plugin in a meteoric project with no issues.

Well, for anyone else experiencing the problem:
The problem is caused by google maps plugin applying background-color opacity of 0 to map and every parent.  Simple css workaround for now:
._gmaps_cdv_.snapjs-left .snap-drawers, ._gmaps_cdv_.snapjs-right .snap-drawers {
	display: block;
}

._gmaps_cdv_ .snap-drawers {
	display: none;
}

The css workaround did not work for my case: "google autocomplete search result list does not work(i.e. the list is not selectable) when wrapped in any ionic view"


Clinical Notes

Will MIMIC-IV have clinical notes (diagnosis notes, etc.)?  I've been digging through the documentation and data set but haven't been able to find references to clinical notes.

Alistair, thanks!
When we can expect clinical notes ?

Would love to know this as well!

Waiting for the note/clinical events as well !

@alistairewj is there any update on the roadmap for clinical notes?

Oh wow, so MIMIC-4 just has no text data now whatsoever?

@johntiger1 Notes will be released on PhysioNet as a separate project/module at a later date.


Update dependencies

The primary 2 updates are for qs and wd
• qs: ~5.1.0 -> ~6.0.1
• wd: ^0.3.12 -> ^0.4.0
The remaining are covered by existing semver though when in Rome...

@ntwb it looks like the build is failing...related to the new qs version using const in strict mode. I don't think earlier versions of node support ES6 syntax, so we need to either deprecate support for those versions or keep qs on the current version. For now, can you rollback the qs upgrade and submit a separate PR where we can discuss the pros and cons of that upgrade while still being able to take advantage of these other dependency updates?
Also, sorry about taking so long to get back to you...if there are some more new versions since you submitted this PR, feel free to update them as well. I'll merge once we have a passing build.

They actually refactored the const in https://github.com/ljharb/qs/commit/224c8af8fc8abf48fd9ded33a38997a1d942c1c1
So this is probably "safe" now

Apologies it took me a while to get back to this, refreshed the pull request update all the dependancies except qs

Added a PR for qs v6.x https://github.com/mklabs/tiny-lr/pull/101

@ntwb can you rebase this really quick? Build looks good, I'll merge. Thanks!

Rebase went horribly wrong, fresh pull request in #102


CSOAR-272 - Add "API Quickstart" content

Purpose of this pull request
This pull request (PR) adds the content of the "Cloud SOAR API Quickstart" manual to the Cloud SOAR APIs article:
https://help.sumologic.com/docs/cloud-soar/cloud-soar-apis/
It also removes the recently-added table of APIs (#2557), since those APIs are in a closed beta for "Cloud SOAR Delivery 2", and should instead be presented in the beta article rather than to the general public.
Issue number:
CSOAR-272
Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

Thanks, @kimsauce!


Add a section for "Known Issues", including ellipticity bug

As discussed at the Feb 3, 2022 CSS meeting with Bryce, we would like to add a "Known Issues" section to the note and include a brief summary of the ellipticity bug.  See discussion on Slack to converge on some text.

Thanks @evevkovacs!
Maybe we can work out some text to include in the DC2 release note and the footnote would point to your LSSTDESC note.  I started a google doc and here is what it says - basically just pulling your works from the your document:
Since the DC2 public data release, a bug in the ellipticity distribution has been identified and documented.[footnote pointing to Eve's doc] The issue resulted in the distribution of ellipticities being skewed to lower values, i.e., galaxies are rounder than they should have been. This affects the intrinsic (pre-lensing) galaxy ellipticities; the lensing shape distortions were unaffected in the catalog, and are added to the too-round intrinsic shapes.

I added a slightly edited version on Overleaf.

Thank you @yymao !  The text looks fine to me :)  For citing, I see in PubDB that there is now a link in the CosmoDC2 project to the [google doc](https://docs.google.com/document/d/1D5EyZ8l9rEs0A0v38Fe5QNDstEih9SbhBtdHYkOIZyo/edit that Eve posted above - is that what we're to use for citing?

I think it'd be better if we put Eve's note on Zenodo so that it's citable.  @evevkovacs is that ok with you?
Also, there is no plan to fix this bug right? I think it may be helpful to point that out in our note if that's the case.

Yes, fine to post the note.
Yes, there is a plan to put out a new version of cosmoDC2 with the values fixed. A new version of SkySim5000 with these and other corrected values is also forthcoming.

Just one more question from me - how do we manage zenodo for DESC? I really haven't kept up with this! There's 2 aspects of this question:
first - for a LSST DESC Note - in this case I guess one that is supporting a journal article - we're all set for review from the WG (CSS)?
And then more technically - we have a zenodo DESC account as well as a DESC Zenodo community.  The DESC account can do uploads, as can anyone associated with DESC - so in this case, @yymao, you'll deal with the upload (and that's fine!)  just making sure.

Since @evevkovacs is the main author of the note, I think it's best if Eve uploads it.

@yymao Happy to do this if you tell me where it needs to go.

Do you have an account on https://zenodo.org/ already? If not, sign up for on. Once you have an account, you can go to https://zenodo.org/deposit to upload the PDF file.
You'll also need to fill in a few things like:
Communities: choose "LSST Dark Energy Science Collaboration"
Publication Type: Technical note
And also title, authors, etc.

Document has been uploaded to Zenodo.

Thanks @evevkovacs.  I just added the reference to the release note on Overleaf.
I'm going to keep this issue open until we upload the updated note to arXiv.

Question for @heather999 @JoanneBogart -- should we upload the release note to arXiv now, or wait a bit for the truth catalog release?

How do I get to the Overleaf release note?

The note looks fine, but I'm inclined to wait for the truth catalog release  (which will mean first adding some text about the new datasets) if that release is going to be fast.  Otherwise we'll have to go through this whole cycle again right away.


Update README.md

Raku hasn't been called Perl6 in a long time, so I thought I'd make the correction.

Thank you!


panel of normals creation for Mutect2

Description of feature
With 40 normal samples a panel of normals file should be generated which can be used with Mutect2.

Can this be closed now? :D


Replace Xtend with Java

In the Xtext release notes of version 2.20.0 you find the following about "Xtend"

A word on Xtend. Back in 2013 Xtend was the “Java 10 of today” even before Java 8 was out. Meanwhile Java Release cadence has speeded up and many of Xtends features can be achieved with pure Java, too. There is still some areas where Xtend is particularly advanced like Code generation, Unit tests and lambda heavy APIs like JvmModelInferrer and Formatter. For other tasks there is no need to use Xtend. Also the resources we have no longer allow us to keep the head start against Java. And learning Xtend still is a burden for new Xtext users. To reflect this changed situation we have decided to make Java the default in the wizard again (except e.g. the Generator and a few other APIs). You can still decide if you want Java or Xtend in the workflow.

IMO Xtend is really superior in the area of string templating. It's used to build SQL statements in this project. However, this is not a code generation project. Therefore we can live with inferior Java features in this area. Java 13/14/15 text blocks would address some issues, but not all. Anyway, In this project we have to stick to the Java version used by SQL Developer. The current version of SQL Developer 19.4.0 supports JDK8 or JDK11. The user chooses the exact version. Hence we have to stick with JDK8 for the moment.
Moving from Xtend to Java will have the the following positive impact:

reduced compile time
IDE independence (Xtend works quite good in Eclipse but the IntelliJ support has been dropped)
better debugging experience (no bridge between Xtend and Java representation)
more inclusive / simplified contribution (because Java is much more popular than Xtend)
reduced size of final artefact (no Xtend runtime libraries required).

But there is also a negative impact:

more verbose code due to missing, equivalent feature in Java (see also Xtend features)

Extension methods (used)
Lambda expressions (used, but there are acceptable options in Java8)
Active annotations (used)
Operator overloading (used)
Switch expressions (used)
Polymorphic method invocation (used)
Template expressions (used)
Properties (used)
Type inference (used)

Xtend generated Java5 code. However, this code is not meant to be maintained manually. It looks ugly and since it is based on Java5 it does not use Java8 features where possible (e.g. for lambda expression). Hence the migration from Xtend to Java is a semi-automated process, where the generated code might be used as a starting point only, but must not be used 1:1.
A migration is possible class by class. However, I suggest to do it for the whole project including tests.

Btw have you considered Kotlin?

Yes I have. Especially since there are a lot of similarities with Xtend. I would have liked to use a JVM language with multiline text blocks in string literals. However, I decided for Java because of popularity (even if Kotlin seems to be now the 2nd most popular JVM language according this post) and because we are using it as the JVM language of choice in the other utPLSQL projects.
And I have already started to migrate classes to Java. Painful. Commits to local branch. Not pushed yet.