npm install on Windows: Error: end of central directory record signature not found

Hi, this happens during npm install -g for 0.35.0 on Win10:

rm -rf ~/.electron/
rm -rf ~/.atom/
npm cache clear
npm install
=> this work for me

Still an issue, but the workaround by Judy worked.

yep, works, thanks

I was trying this to build https://github.com/electron/electron-api-demos on windows 7.
Also tried the workaround mentioned by @JudyHsiao and I get:
77987 verbose stack Error<EMAIL_ADDRESS>postinstall: `node install.js`
77987 verbose stack Exit status 1
77987 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:239:16)
77987 verbose stack     at emitTwo (events.js:106:13)
77987 verbose stack     at EventEmitter.emit (events.js:191:7)
77987 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
77987 verbose stack     at emitTwo (events.js:106:13)
77987 verbose stack     at ChildProcess.emit (events.js:191:7)
77987 verbose stack     at maybeClose (internal/child_process.js:850:16)
77987 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
77988 verbose pkgid<EMAIL_ADDRESS>77989 verbose cwd c:\PRJ\Temp\Electron_Api_Explorer\electron-api-demos
77990 error Windows_NT 6.1.7601
77991 error argv "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
77992 error node v6.1.0
77993 error npm  v3.8.6
77994 error code ELIFECYCLE
77995 error<EMAIL_ADDRESS>postinstall: `node install.js`
77995 error Exit status 1
77996 error Failed at the<EMAIL_ADDRESS>postinstall script 'node install.js'.
77996 error Make sure you have the latest version of node.js and npm installed.
77996 error If you do, this is most likely a problem with the electron-prebuilt package,
77996 error not with npm itself.
77996 error Tell the author that this fails on your system:
77996 error     node install.js
77996 error You can get information on how to open an issue for this project with:
77996 error     npm bugs electron-prebuilt
77996 error Or if that isn't available, you can get their info via:
77996 error     npm owner ls electron-prebuilt
77996 error There is likely additional logging output above.
77997 verbose exit [ 1, true ]

Do you have any clues?

Ignore my previews post .
The problem with that error log was that I was using proxies and I had different values for proxy and ** http-proxy**.
I was using a proxy with username and password
http://myuser:mypas$@proxy.company.com:3128 (proxy setting) and for the https-proxy setting I was escaping the dollar sign http://myuser:mypas\\$@proxy.company.com:3128 .
Still  from the error It was pretty hard to direct the search.

It works for me but this is still happening on OSX.
Maybe the work around can be included in script error output as I only got it via a duplicate bug that got linked to here.

not resolved help me step by step
install node, install electron, and run hello desktop app... thanks

package.json
{   "name":    "demo",   "version": "0.0.1",   "main":    "main.js",   "scripts": {     "start": "electron main.js"   } }
main.js
const app = require('app');
const BrowserWindow = require('browser-window');
app.on('window-all-closed', function() {
if (process.platform != 'darwin') {
app.quit();
}
});
let mainWindow = null;
app.on('ready', function() {
mainWindow = new BrowserWindow({width: 800, height: 600});
mainWindow.loadUrl('http://www.google.com');
mainWindow.on('closed', function() {
mainWindow = null;
});
});
Run just > electron

Run >npm start

There is allways a chance to pick up installation from the point it was interrupted. Just Ctrl+C when it hangs on "node install.js" so that /node_modules/electron/ was not deleted by script; Then navigate to /node_modules/electron/ and "npm install" to continue from "node install.js" point.

Even after following @JudyHsiao and @sencis82's suggestions, the install process still hangs on install.js to then fail. I'm on Windows 10.
`PS C:\Program Files\nodejs\node_modules\electron> npm install
npm WARN deprecated<EMAIL_ADDRESS>standard-format is deprecated in favor of a built-in autofixer in 'standard'
. Usage: standard --fix
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

<EMAIL_ADDRESS>postinstall C:\Program Files\nodejs\node_modules\electron\node_modules\spawn-sync
node postinstall

<EMAIL_ADDRESS>postinstall C:\Program Files\nodejs\node_modules\electron
node install.js

C:\Program Files\nodejs\node_modules\electron\install.js:46
throw err
^
Error: read ECONNRESET
at exports._errnoException (util.js:1023:11)
at TLSWrap.onread (net.js:572:26)
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "ins
tall"
npm ERR! node v7.5.0
npm ERR! npm  v4.3.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node install.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electron package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electron
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electron
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\CK\AppData\Roaming\npm-cache_logs\2017-02-13T01_40_23_562Z-debug.log
PS C:\Program Files\nodejs\node_modules\electron>`


update docker image

Updates docker image for mapq0 step.
If you are using this PP df3ced54b8ea44448d656ecaf42a6829   Somatic WGS June 2019 consider updating your workflow.

Looks to me like the arguments have changed and the CWL might have to change to accommodate that:
Old: https://github.com/genome/docker-mapq0-filter/blob/301de5e65c7f2d3671e35e1e6297110eacb4cdf7/mapq0_vcf_filter.sh
New: https://github.com/genome/docker-mapq0-filter/blob/master/mapq0_vcf_filter.sh


fix bug when applying model with customized image size

Hello @cslxiao , Thanks for you contribution.  #295 is better compared with your PR, we decide to close this PR. Thx anyway.


Starfield

WIP, although everything is implemented now, nothing has been really tested yet.
Do not have a configuration flag for turning on Starfield stuff yet, it's just on by default right now, will add that later.

Ok, this should be good to go now besides the outstanding comment above. I have compiler game configuration implemented on another branch, which includes Skyrim support, but I’ll put that in another PR.


Python versions from pyproject.toml

📋 Description

service-independent
should show required range of python versions same as the one for PyPI

🔗 Data
any pyproject.toml file, from the requires-python field
🎤 Motivation
should be even easier than the one on PyPI and it will work as a dynamic badge for people who are working on packages that are either public or private, but not a public package

Couple of notes:
This would be for a PEP 621-compliant pyproject.toml Not all packageing tools follow the spec. For example, poetry stores this in tool.poetry.dependencies.python, rather than .requires-python
Currently shields has base classes for dealing with requests that return JSON, XML and Yaml. We don't have one for Toml so part of the job would be to add a toml parser and base class for it. This is not a blocker and would be useful to have anyway, but we don't currently have it as a building block.

Hey, i could help.
I guess there is no point in writing a parser from scratch just like we use parsers from other modules for yaml, xml etc...
The toml site refers to a 3 packages that are complaint with tomlv1.0.0 (latest):

name

smol-toml

toml-nodejs

@ltd/j-toml

smol-toml is relatively new but seems easy to use, boasts big performance and appears to be easier to implement.
All of those are hardly in use thats why i also took a look at packages that don't comply with latest toml spec.
There is also toml which is way more in use (900k weekly downloads, 240k github projects) but it only supports toml v0.4.0. could this be an issue? it seems to be very old, i fear newer nodejs versions might conflict with it in the future.
Should i got ahead with smol-toml, This would add a new dependency to the project.

Yeah we should definitely use a package and not write our own parser.

There is also toml which is way more in use (900k weekly downloads, 240k github projects) but it only supports toml v0.4.0. could this be an issue? it seems to be very old, i fear newer nodejs versions might conflict with it in the future.

Yes. This from the readme does not give me high confidence this lib is being actively maintained :smile:

toml-node is tested on Travis CI and is tested against:

Node 0.10
Node 0.12
Latest stable io.js

Lets pass on this one.

Of the other packages you've suggested:

@ltd/j-toml seems to be the most popular
smol-toml requires node 18 minimum. I've been having trouble getting a review on https://github.com/badges/shields/pull/9385. I might just go rogue and merge this at the weekend. In any case, you can assume we'll be running node 18 in the near future, although current master is still on node 16

Having had a quick look at the parsed objects that those 2 parsers return, I think if we implemented this using smol-toml and had to switch it out for @ltd/j-toml at a later date, it should be possible to switch them pretty transparently. I think it would be reasonable to take a punt on smol-toml :+1:

Now that we got TOML support I can add this, I hope i can get it done this weekend

I think for this badge (pulling direct from a pyproject.toml), we should just take the value of requires-python and put it on a badge. If we wanted to add one that presents a delimited list, we could add a variant that does that based on the trove classifiers, but we shouldn't try to derive it from requires-python IMO.
There is a really long thread at https://github.com/badges/shields/issues/5551 about how we should deal with this when we get this from the PyPI and whether we should use python_requires or classifiers. It ended up with us.. not changing anything.


Configure Pastebin Pro API keys

Hello,
I bought the pastebin pro account and I'm looking how to setup this API in Scumblr. Is this possible?
Thank you.

Not currently. We actually don't currently have a separate pastebin search provider, instead relying on scoped google searches. It would probably be relatively simple to create a pastebin search provider though, and this could easily support the API keys.


Scroll position when list refreshed with displayBottomUpward set to true

<InfiniteAnyHeight   list={res}                                     className="messages-container__list"                                                     containerHeight={window.innerHeight - 155 - 69}                                                     handleScroll={ (node) => handleScroll(node) }                                                     scrollContainer                                                     displayBottomUpwards                                                     preloadAdditionalHeight={window.innerHeight - 155 - 69}/>
When I'm adding a new elem to the list the scroll doesn't stay at the bottom, is it normal or I  missed something ?
Thanks

Hi, sorry for the delay. This is a wrapper that adds arbitrary heights. Have you tried with just react-infinite? Props are passed down so it should arrive as a prop to react-infinite. Let me know and if the issue is just in this package, I'll test it and debug.


Antibiotics Volume Usage corrected for seasonality

A request for a new measure came up when testing the All England dashboard. The user would like a measure corrected for seasonality for the  antibiotic volume measure

So seasonal - difficult to tell what it is. Can you adjust for seasonality? I suppose you can but there might be some way of presenting better but then will be different to all others so might confuse people.

I'd love to be able to provide this.
We could use something like the decompose function used by Alex in this notebook.
However, our current workflow does everything in-SQL, so it would require some kind of python-based post-processing.
It may be better to look at this once we've progressed some of our other work relating to rationalising measures and our data formats.
In the mean time it would be helpful if @alexwalkercebm has a chance to try applying the decompose method to the antibiotic measure in a notebook, and seeing if it produces useful outputs.

Like this?
https://gist.github.com/alexwalkercebm/4f884ea5d3b7ef4e014d61c6918a52b7
I've just smoothed the deciles, along with the global calc_value, it looks reasonable to me. It takes a fraction of a second to do the smoothing.
I think the ideal way to present this on the site could be as a smooth button/switch on existing measures, rather than as separate measures. No idea how difficult to implement that would be.

Are we waiting for the matrix store for implementing this? Possible one for next top 3?
Blog is here on prototyping for users.

Yes, we should wait ideally, simply because otherwise we'll just have to do it again in a different way


feat(dev): pre-configure testing for react-ts

Description
Having examples include testing configured and ready to go seems like a good thing.
What is the purpose of this pull request?

[ ] Bug fix
[X] New Feature
[X] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

Yea, I have no clue how to make your build system not build those tests, sorry. Need some help please.

I don't think we should add this. The template should be kept as simple as possible and not everyone needs testing from the get-go. It would be better if this is created as a separate community template.

Yes, thanks for the PR @lookfirst, but this feature is out of the scope of the create-vite templates. The idea is that they are a way to quickly try out Vite with your framework of choice, and we want to keep them as barebone as possible. They aren't directly intended to replace something like CRA. In the Vue ecosystem for example, now there is create-vue that also scaffolds a Vite app, but giving you the option to add Vitest, Cypress, and a lot more: https://vuejs.org/guide/quick-start.html#with-build-tools. Something similar should be available for each framework, maintained by each community. It is the only way this can scale.

@patak-dev @bluwy If testing was explained better from the get go, it would create more resilient developers and applications. Trying to hide does nothing to help anyone.
If anything just add a README section to explain things. All this PR really did was add some packages and a file, it wasn't like some massive contextual shift for new developers.

@lookfirst we are working on a redesign of the create-vite templates that will hopefully make more clear that these are intended to try out Vite with your favorite framework, to quickly get started and explore Vite features. It is out of the scope of Vite core to promote a certain testing library through the templates. This isn't about how much was added on the PR.
That being said, we have already discussed adding a testing-related section in the docs. We are going to add an ecosystem page soon, and there may be a section there linking to the different projects. We may something else in the guide, but this could be better as a blog post so we don't need to maintain something that isn't directed related to Vite core (we should talk about Jest that a lot of projects still use, and also about playwright test on the unit testing side... but why not also about Cypress and Playwright for e2e).

It is out of the scope of Vite core to promote a certain testing library through the templates.

The only thing anyone should be trying to promote is the concept of testing frontend code as a first class citizen. There really isn't enough focus on writing tests and that is a huge part of the problem why everything becomes such a maintenance nightmare. It is really too hard for new developers to just pick up and test components.
I picked vitest since it seemed affiliated and tuned with this project. Cypress and Playwright look great, but again... I was just trying to give the simplest example and use something fairly well integrated already.
But even these things don't get it 100%... where is the "test" script property? =)
https://github.com/cypress-io/cypress-component-testing-apps/blob/main/react-vite-ts/package.json#L5

You bill this project as next generation frontend tooling and totally skip over one of the most important parts... tests.

We deeply care about testing, that is why some Vite core team members started Vitest. I think that could count as not skyping over that part ;)
Again, I agree with you that testing is important, it is just that blessing a certain testing tool and maintaining its integration in the templates isn't part of the scope of create-vite. Check out create-vue for something very similar to what you are picturing (also including linting and other things that are also important). If you would like to work on a new scaffolding tool that does something like create-vue for every framework, that would be awesome. It would be a helpful project, even if I think that it is better that each framework maintains its own... your project could push them to do so.

Actions speak louder than words and the word 'test' doesn't appear anywhere on the homepage...

We continue down the path of everyone having to build their own project to do these things when the core projects that everyone uses gloss over on the important bits.
vite is a fantastic effort and definitely one of the best out there right now. It would be even more fantastic if you made testing a first class citizen. This PR was a test to scratch the surface and see if there was interest in going further, but it is clearly not something you guys are interested in because you keep punting me off to do it as a separate endeavor.
Take Vue as an example. Their testing page is buried in the navigation. Everything is poorly documented as an afterthought and requires studying a whole bunch of documentation before you can even get started. create-vue kind of creates something useful... but there isn't any documentation for it at all.

but it is clearly not something you guys are interested in because you keep punting me off to do it as a separate endeavor.

Exactly, it is good that you understand what it means for this to be out of scope for Vite. Open Source projects need to set scopes to keep things maintainable in the long term.


Mujoco v2.2.1 Unity Plugin crashing on any import in method Mujoco.MujocoLib:mj_loadXML on Mac M1 (Unity rosetta)

Obtained 256 stack frames.
#0  0x00000168c2c9e6 in mono_unity_backtrace_from_context
#1  0x0000010130d199 in PrintStackTraceOSX(void*)
#2  0x000001011cab41 in HandleSignal(int, __siginfo*, void*)
#3  0x00000168c85c3c in mono_chain_signal
#4  0x00000168ba91a0 in mono_sigsegv_signal_handler_debug
#5  0x007ff8111badfd in _sigtramp
#6  0x00000000000000 in (Unknown)
#7  0x007ff8111badfd in _sigtramp
.......... <repeat>
#2430x007ff8111badfd in _sigtramp
#2440x00000000000000 in (Unknown)
#2450x007ff8111badfd in _sigtramp
#2460x00000000000000 in (Unknown)
#2470x00000000000000 in (Unknown)
#2480x000001011cab41 in HandleSignal(int, __siginfo*, void*)
#2490x00000168c85c3c in mono_chain_signal
#2500x00000168ba8e97 in mono_crashing_signal_handler
#2510x007ff8111badfd in _sigtramp
#2520x00000000000000 in (Unknown)
#2530x000002250326d3 in mjParseXML(char const*, mjVFS_ const*, char*, int)
#2540x0000022503162b in mj_loadXML
#2550x000002067dac94 in  (wrapper managed-to-native) Mujoco.MujocoLib:mj_loadXML (string,void*,System.Text.StringBuilder,int) [{0x7f9f72650c78} + 0x164]  (0x2067dab30 0x2067dadff) [0x168742a80 - Unity Child Domain]

Include the following context:

Mac M1 (Rosetta)
MuJoCo version 2.2.1 and 2.2.0 both crashing
Unity v2022.2.0b1 and 2021.3.6f1 LTS both crashing

Repro steps -

Use unity package manager to locate and install mujoco from its package.json
Import a model (humanoid.xml/cloth.xml etc. in models folder)

Result: Crash (or indefinite hang)

Instead of import, try adding a component in a gameobject in scene (Tried mj geom on a plane)
Hit play

Result: crash  (or indefinite hang)

Using native silicon version of Unity 2021.3.8f1 is working. But I need the rosetta version for my other plugin dependencies in project which are intel only


Remove AfterCommit

This is a very SQL-only feature. Move it to SQLStrategy or remove it.

That one has been removed


platform integration:update --fetch-branches 1 has no effect

platform integration:update y3cfhgv7neyao --project=zj4rrk32qwbk6 --fetch-branches 1
Produces no visible output, and results of integration:get before and after running this command is the same (fetch branches false)

Thanks for the report - this is fixed in version 3.2.2


global option defaults to true?

Tests should answer this but the build is currently failing. From what I can tell, if I don't pass { global: false } I don't get my styles namespaced.

This seems to happen only when requiring a css from a node_module

Oh yeah, I believe that's correct - the reasoning was that if you're importing a package from npm you probably don't want to have it namespaces. Whereas if you're inlining styles you do. Does this make sense?

Well now that you put it that way I think that makes sense. I'd say { global: true } is the better default for node_modules. You might want to add a line in the readme about that though it was already there and I didn't read documentation before opening issue :facepunch:

yay!


[WIP] Implementing basic stimulus presentation for tasks and control over psychopy

Add some stimuli for test purposes
Implements settings, so that tasks can have more reproducible order of stimulus displays and allowing control over conditions etc.

Scaffolding for package is now mostly set up, stimuli are included (but possibly will be updated). Minor documentation included.


Adjust SwiftPM 5.7 to minimum supported deployment target changes

Update minimum supported deployment targets and mark older version constants as deprecated in tools-version 5.7
rdar://93920177
Motivation:
Xcode 14.0 is raising the minimum supported deployment target versions for most platforms.

@swift-ci please smoke test

Not 100% sure I caught all the tests that need updating since I am still seeing the _StringProcessing thing locally 😬

error: the library 'TSCBasic' requires macos 10.10, but depends on the product 'SystemPackage' which requires macos 10.13; consider changing the library 'TSCBasic' to require macos 10.13 or later, or the product 'SystemPackage' to require macos 10.10 or earlier.

Probably an issue with TSC explicitly declaring a 10.10 deployment target: https://github.com/apple/swift-tools-support-core/blob/main/Package.swift#L21

I wonder whether that means that we have to do something where the raised minimum is for tools-version 5.7 only or we have to adjust these checks to not enforce the minimum?
Otherwise I can see a scenario where an existing package declares e.g. macOS 10.12 as its deployment target and depends on a package that doesn't declare one. With the raised deployment target, the dependency will implicitly have a 10.13 minimum deployment target, so the check will fail and prevent building at all where otherwise there may have been a build time warning, but XCBuild would implicitly raise both to 10.13 anyway.

I wonder whether that means that we have to do something where the raised minimum is for tools-version 5.7 only or we have to adjust these checks to not enforce the minimum?
Otherwise I can see a scenario where an existing package declares e.g. macOS 10.12 as its deployment target and depends on a package that doesn't declare one. With the raised deployment target, the dependency will implicitly have a 10.13 minimum deployment target, so the check will fail and prevent building at all where otherwise there may have been a build time warning, but XCBuild would implicitly raise both to 10.13 anyway.

Right, it sounds as if the comparison should be on the adjusted minimum deployment target.  I guess that could make the error confusing if the package claims one thing but then the error is about a higher version.

A few tests are hitting exactly this situation:

error: the executable 'Dealer' requires macos 10.12, but depends on the product 'DeckOfPlayingCards' which requires macos 10.13; consider changing the executable 'Dealer' to require macos 10.13 or later, or the product 'DeckOfPlayingCards' to require macos 10.12 or earlier.

@swift-ci please smoke test

@swift-ci please smoke test

Updated now to automatically raise the derived deployment target to the minimum. We could consider emitting a warning if the specified deployment target is lower than the minimum, but I am not sure if that would be annoying in practice.
If a package is using the 5.7 tools-version, using an older deployment target will already show a deprecation warning after these changes, so a secondary warning seems redundant.
If a package is using an older tools-version, it might be desired to support older deployment targets if older tools are used, so the author would end up with an unfixable warning in 5.7.
The only case that actually seems interesting is executables, because the author may want to legitimately deploy to older versions of macOS and may have missed that those are not supported anymore, so the warning could be useful.

Some good points there about a warning — I think that there are a lot of subtle traps with adding a warning, and we can hold off and see if one should be added later.

I work on a project that uses a new version of SPM but needs to deploy back to older platforms. I understand that this is no longer officially supported but in practice everything "works"…except for this check, which forces the deployment target up. I'd be interested in seeing if we could turn off this behavior on an opt-in basis. Happy to eat a warning too if need be.
What I was thinking was I could specify a target with all my dependencies in it, and explicitly specify a string version (e.g. MacOSVersion(string: "10.11"), rather than MacOSVersion.v10_11. If I spell it out explicitly it seems reasonable to me that I know what I'm doing and would not like this adjustment to be performed. Thus, my package (and its dependencies) would build with that platform version, rather than having the version automatically raised. Does this sound reasonable?


[HACDOCS-1016] Added ArgoCD plugin content

Purpose: To resolve HACDOCS-1016
Version for cherrypicking: NA
Content for preview:  Output
SME review: @karthikjeeyar

/lgtm

@linfraze Thank you for the comments. Raised a new PR addressing your comments: https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/413
Also, requested some suggestions on your comments


Example: Less with Ant Design

Hint: This is also a good starting point for anybody who wishes to build a sass etc. example.

Ant Design is a TypeScript and Less based React UI Component Library . It can be challanging to set it up with tree shaking (only require the styles that you really import) and be able to customize it (overwriting its theme variables; using styled-components to create an individual feel) without relying on css imports.

Ant Design is written in TypeScript, which means the typescript code lens always tells you what properties and functions components accept. TypeScript is enabled to make use of that, though this example can also just be used in plain JS and/or in a mix with TypeScript.

Let me know when this is ready to merge

@tannerlinsley tested — can be merged. We'll just pick this up again when changes to the pre-processor were made. We use exactly this in production.


Refactor Desired Chain to activeChain

Refactor Desired Chain to activeChain
Added const folder for yourDetails

Thanks for contributing!


Terminate Contracts/Contract Requests on Legal entity deactivation

On Deactivation Legal Entity
- deactivateLegalEntity(id: ID!): LegalEntity
- api/legal_entities/id/actions/deactivate

we need to check whether there is any

contract in status NEW, IN_PROCESS, APPROVED, PENDING_NHS_SIGN, NHS_SIGNED
contract_requests in status VERIFIED
with legal_entity_id=contractor_legal entity_id and change status to TERMINATED for such contract/contract_requests with status_reason='auto_deactivation_legal_entity'

Is confluence page updated?

updated confluence page can be found here


problem in compilation with last babel7 (beta.1)

i found an issue with last babel7 ,
don't know where it was from
but when i installed the last cosmiconfig 3  it was resolved .. maybe you should to update it in your repo

I'm aware of the required cosmiconfig update and will do it as soon as possible


Build_libs.sh build problems

Hello! I am getting this output when compiling
./build_libs.sh
GOARCH: amd64
GOOS: linux
OPTION:
and it does nothing more.
Thanks.

Your environment should be able to build github.com/devsisters/libquic , so you may have to install cmake, ninja or make, gcc and g++, and so on. Could you check it please? I will add this requirement to README.md.


gce_virtual_machine: Support user provided instance metadata

Two of the instance metadata keys that are particularly interesting are
'startup-script' and 'user-data', which are reserved by google-startup-script
and Cloud
Config(https://cloudinit.readthedocs.org/en/latest/topics/format.html#cloud-config-data)
to run user specified workloads at boot time. This can be a useful way to
measure VM boot time as a lot cloud workloads are started through some init
scripts, instead of SSH. Plus, sshd on GCP images is usually started at a
pretty late stage.
@voellm @skschneider @cmccoy

Thanks for the PR. Two general comments:

Have you looked into whether other clouds support a similar metadata-on-boot that could warrant making the flag global, rather than GCP-specific? If that's the case, I recommend moving the flag out of the GCP module. If not, the flag should be prefixed, as mentioned in my earlier code comment. I don't think it would be a big deal if we started by prefixing the flag even if we were unsure, because if we later learned there was another cloud that supported the feature, we could easily make a duplicate flag without the prefix that does the same thing.
Would it make sense to treat these new flags more like the existing --metadata flag, which is a defined as a multistring and uses the format --metadata=k0:v0,k1:v1?  The way the --metadata flag is handled, you can put it twice in the same command, making it easier for scripts to add more metadata to a base command stored in a variable that already adds some metadata. On the other hand, I see that the k=v syntax you're using more closely matches the gcloud commands, but if we're going to be consistent with something, I'd cast my vote for the method that avoids commands like --gcp_vm_metadata=key=value.

@skschneider  Thanks for the comments. PTAL.

Have you looked into whether other clouds support a similar metadata-on-boot that could warrant making the flag global, rather than GCP-specific?

I looked at it. EC2 seems to support similar instance metadata as GCP does, but it has a different format for configuring those metadata - may not be simple key-value pairs, or may not be applied the same way gcloud applies them. I am not familiar with other cloud providers but I assume it'll be hard to unify VM metadata across the board into one common flag, and that is clearly beyond my reach. So I'd not do it in this PR.

Would it make sense to treat these new flags more like the existing --metadata flag, which is a defined as a multistring and uses the format --metadata=k0:v0,k1:v1?

Yes, and that seems neat.

I'd cast my vote for the method that avoids commands like --gcp_vm_metadata=key=value

You don't necessarily have to write it that way - you can do something like --gcp_instance_metadata k1=v1,k2=v2 when you use gflags, but looking at the full pkb command line dump, I think making all key value pairs conform with the same format makes sense, so I changed to use colon.

Took another pass - main issue at this point is handling commas.

Took another pass - main issue at this point is handling commas.

Addressed the comments and created a helper function to parse key value pairs from command line. PTAL.

LGTM other than the three small things, which you've fixed already. Let me know when you've pushed your changes to GitHub, and I can merge it.

Thanks. Just pushed a new patch with the suggested changes.

Looks good, thanks! Merged.


Part variant BOM pricing way too high

Please verify that this bug has NOT been raised before.

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

Describe the bug*
While trying to create a "pack of 9" by creating a BOM, I ran into a nasty bug.
I have a $0.30 part that inventree calculates as worth $6,863,037,736,488.3 if I use it as a BOM item in a variant of itself.
I opened up Inventree's official demo and easily re-created it. (If it hasn't deleted itself, it's part 913 and 914 as of right now, but I'll show how to reproduce it)
Steps to Reproduce

Create a new part (we'll call it Main Part). Make sure it can be used as a template.
Add internal pricing to the part. I used $0.30 in my test. (it just needs any sort of pricing, whether it's internal or wherever)
Create a variant of 'Main Part'.
Add a BOM to it and use 'Main Part' with a quantity of 9.
It should instantly go haywire with the max pricing of the BOM.
Each time you refresh the pricing, it should go higher until the database can't handle that high of a number.

Expected behaviour
Expected the BOM price to be $0.30 x 9 = $2.70 instead of $6,863,037,736,488.3
Deployment Method

[X] Docker
[ ] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.13.0 dev
Django Version: 3.2.22
Commit Hash: 6f2dca7
Commit Date: 2023-10-09
Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-5.15.0-82-generic-x86_64-with
Installer: DOC
Active plugins: False
Please verify if you can reproduce this bug on the demo site.

[X] I can reproduce this bug on the demo site.

Relevant log output
No response

Ok, that's an interesting case. The BOM for the variant includes the parent part - and so each time the "variant price" is calculated, it looks at the bill of materials, which includes the template part. The pricing for the template part includes the calculation of pricing for all variant parts. So, the variant price is 9x template price which is 1x the variant price.
Essentially we have created for ourselves a nice little infinite loop.

Thinking about it some more, the most robust solution would be to prohibit a BOM item from containing items which are either children or ancestors of the assembly.
This would mean that your "pack" would need to be a different part (not a variant). But it is the simplest approach which avoids a lot of potential edge cases.

@matmair @wolflu05 I'd like to get a fix for this into 0.13.0. Any thoughts on the idea of preventing BOMs from containing variants of the target part?
I'd also like to consider how we would stop this infinite loop in pricing calculations too. As each pricing calculation is considered "separately" it is hard to detect loops like this

I think the logical problems arising from BOMs containing itself alone are enough reason to not allow this; I would just close down this possibility and check the tree on BOM changes if the item itself is in the tree in either direction.


Minor patches

For newer versions of docker and for when the container doesn't have su in the local PATH

Sorry for the slow answer here :-/
OK, your changes make sense (and would address #60, it seems!)
Do you think you could rebase?
Thank you so much!


Add context to model config docs

pass cause to log to know actual error
called out the explicit models + some docs/links

bad merge/branch.


phenomenon translation updates

updates to STASH CF translations, sourced from various metarelate contributors

Given our testing actually passes, I don't really mind that stickler-ci doesn't. Fixing that would require adding another exclude list in sticker.cfg, which feels a bit of a shame/redundant.


3D filtering benchmark

This PR, to the benchmarks branch, contains

a benchmark of the 3D filtering code (benchmarks/filter_3d.py)
pure Python implementations of the Cython code used in 3D filtering

It also switches the code to use the pure python implementations, so a successful CI run should confirm the code is still working (tests pass locally on my laptop too).
It also applies numba to the hottest loops in this code. The numba application is currently not complete, but as it stands runtimes a factor of 1 - 2 slower than previous Cython code. The remaining part that needs numba is CellDetector.connect_four(), but this will be done in a subsequent PR, with work ongoing at https://github.com/dstansby/cellfinder-core/tree/jit-connect-four.

Given the benchmark script isn't run by any CI and linting passed and this is approved, I will merge


I'm missing ip info

Hey guys, thanks for the great work!
since 7 it feels faster and even though content is still reachable by ip address within the local network it's not being shown anymore which I'm missing as my ip address changes from time to time so i have to look it up to test my projects on mobile and other machines
any chance we could get it "back" or should i make a little wrapper for my use case? or any other suggestions?
e.g. accepting connections at http://<IP_ADDRESS>:3000
greets

I think we'll add it back to the output, just in a more minimalistic way 👍

awesome..i'm satisfied 💯 :D


Add new security page and update related links

closes: #ISSUE_Number

Change logs
As the ASF site checks[1], the "Security" should link to either to a project-specifi page, or to the main http://www.apache.org/security page.
[1] https://whimsy.apache.org/pods/project/cloudberry
Contributor's checklist
Here are some reminders before you submit your pull request:

Make sure that your Pull Request has a clear title and commit message. You can take the Git commit template as a reference.
Learn the code contribution and doc contribution guides for better collaboration.
Make sure that your changes deployment preview is successful.
List your communications in the GitHub Issues or Discussions (if has or needed).
Feel free to ask for the cloudberry committers or other people to help review and approve.

Hi @edespino Thank you for your draft. I have added a few more points. Could you please review it again? Thank you!

This PR is out of date: This branch is out-of-date with the base branch. Consequently, it can not reference the recently added mailling list page (https://github.com/apache/cloudberry-site/blob/main/src/pages/community/mailing-lists.md).

Good catch. All places have been updated. Please take a look again. Thanks!

+1 much better ... thank you.

Thanks for your feedback and review!


Midea dongle OSK102 / OSK103 / OSK105

Are Midea dongle OSK102 / OSK103 / OSK105 all supported?

I only have an OSK105 dongle, but if I have to guess then I would say yes, it supports all of them. Hopefully I can publish the plugin to npm tomorrow and you can test it then. Any feedback is appreciated!

I use midea_ac_lan,georgezhao2010 and OSK102 works perfectly. So if you use this library, maybe it's ok.!
I noticed that display off feature used to work on older versions of midea_ac_lan,georgezhao2010 and no on newer, but I think this is a next step fix and other fixes have priority

I've managed to control the display of the AC, but it looks like when querying if the display is on or off, the AC always respondes with on.

I will check on it! In the meanwhile I've published the package as "homebridge-midea-platform".

OSK105 work!

So OSK103 and OSK105 are verified.
I will close this for now. Can be reopened if some other dongle is not compatible.


[BUG] Snapshot::push_shadow has an unsound signature

https://github.com/gtk-rs/gtk4-rs/blob/a7b3c61fd95a57a980bf17442e5861f58b32c1ad/gtk4/src/auto/snapshot.rs#L236-L245
gtk_snapshot_push_shadow expects an array+length.

Indeed. Do you want to provide a PR for that?

CC @bilelmoussaoui

I wonder if there's an issue in the introspection annotation as well, something to be checked when fixing this issue manually here for now.

You re-import the .gir files once this is done?

You re-import the .gir files once this is done?

Definitely


⚠ ClamAV has degraded performance

In f1265b2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 500 ms

Resolved: ClamAV performance has improved in b8a3cac.


LBRY app error on startup: Wallet server took a bit too long to respond

Bug
Occasionally when starting the app, I will get a persistent error about how the wallet server was taking too long to connect and LBRY won't start up.
To Reproduce
This is intermittent and seems to happen randomly. This PC (Windows 7) is on 24/7 as it LBRY. After some time, LBRY will stop loading channel video lists and stop populating my "Uploads" list prompting me to restart the app. I'd say 4/5 times, the app loads normally upon restart. The other time, I get this error which usually persists for 12-24 hours before spontaneously resolving itself and being fine again for several restarts.
Screenshots

System Configuration
Using most recent LBRY version ( I always update when prompted). I tried rolling back a version and it has no effect on the issue nor did reinstall of the latest 53.9.

LBRY App version: 53.9
Operating system: Windows 7

Additional context
The following is from the lbrynet.txt file in AppData/Local/lbry/lbrynet:
2023-07-30 11:03:00,202 INFO     lbry.wallet.network:254: 2 possible spv servers to try (0 urls in config)
2023-07-30 11:03:00,410 INFO     lbry.wallet.network:269: spv17.lbry.com/<IP_ADDRESS>:50001 has latency of 206.97ms (available: False, height: 0)
2023-07-30 11:03:03,193 WARNING  lbry.wallet.network:284: 2 spv status probes failed, retrying later. servers tried: spv17.lbry.com/<IP_ADDRESS> (('<IP_ADDRESS>', 50001)), <IP_ADDRESS> (('<IP_ADDRESS>', 50001))
2023-07-30 11:03:03,194 WARNING  lbry.wallet.network:287: trying fallback to randomly selected spv: <IP_ADDRESS>:50001
2023-07-30 11:03:03,195 INFO     lbry.wallet.udp:232: closed udp spv server selection client
2023-07-30 11:03:04,816 WARNING  lbry.wallet.network:307: Connecting to <IP_ADDRESS>:50001 failed
2023-07-30 11:03:04,817 WARNING  lbry.wallet.network:323: failed to connect to any spv servers, retrying later
2023-07-30 11:03:14,174 INFO     lbry.torrent.session:146: torrent alert: UDP error: An existing connection was forcibly closed by the remote host from: <IP_ADDRESS> op: sock_read
2023-07-30 11:03:34,823 INFO     lbry.wallet.network:254: 2 possible spv servers to try (0 urls in config)
2023-07-30 11:03:35,032 INFO     lbry.wallet.network:269: spv17.lbry.com/<IP_ADDRESS>:50001 has latency of 207.58ms (available: False, height: 0)
2023-07-30 11:03:37,822 WARNING  lbry.wallet.network:284: 2 spv status probes failed, retrying later. servers tried: spv17.lbry.com/<IP_ADDRESS> (('<IP_ADDRESS>', 50001)), <IP_ADDRESS> (('<IP_ADDRESS>', 50001))
2023-07-30 11:03:37,823 WARNING  lbry.wallet.network:287: trying fallback to randomly selected spv: <IP_ADDRESS>:50001
2023-07-30 11:03:37,824 INFO     lbry.wallet.udp:232: closed udp spv server selection client
2023-07-30 11:03:43,829 WARNING  lbry.wallet.network:307: Connecting to <IP_ADDRESS>:50001 failed
2023-07-30 11:03:43,830 WARNING  lbry.wallet.network:323: failed to connect to any spv servers, retrying later
2023-07-30 11:04:09,173 INFO     lbry.torrent.session:146: torrent alert: UDP error: An existing connection was forcibly closed by the remote host from: <IP_ADDRESS> op: sock_read
2023-07-30 11:04:13,943 INFO     lbry.wallet.network:254: 2 possible spv servers to try (0 urls in config)
2023-07-30 11:04:14,156 INFO     lbry.wallet.network:269: <IP_ADDRESS>/spv17.lbry.com:50001 has latency of 211.85ms (available: False, height: 0)
2023-07-30 11:04:16,953 WARNING  lbry.wallet.network:284: 2 spv status probes failed, retrying later. servers tried: <IP_ADDRESS> (('<IP_ADDRESS>', 50001)), <IP_ADDRESS>/spv17.lbry.com (('<IP_ADDRESS>', 50001))
2023-07-30 11:04:16,954 WARNING  lbry.wallet.network:287: trying fallback to randomly selected spv: <IP_ADDRESS>:50001
2023-07-30 11:04:16,955 INFO     lbry.wallet.udp:232: closed udp spv server selection client
2023-07-30 11:04:22,945 WARNING  lbry.wallet.network:307: Connecting to <IP_ADDRESS>:50001 failed
2023-07-30 11:04:22,946 WARNING  lbry.wallet.network:323: failed to connect to any spv servers, retrying later
Any ideas what this might be or how I can resolve it? This is a relatively new issue which started maybe a couple months ago. I was hoping it was temporary, but figured I'd report it here this time and see what's up with this.

I'm getting the same on Linux.

As I stated in the OP, it once again resolved itself spontaneously later on in the evening. I am just wondering if this is a LBRY issue that can be fixed or if it's a server issue and out of the scope of what can be fixed in the app.
Glad to know it's not just me though.

That happens with default hub servers having issues.
If it happens again, you could try to connect to Odysee hub, or some other hub.
You can do that by adding something like this in your daemon_settings.yml https://lbry.tech/resources/daemon-settings
lbryum_servers:
  - a-hub1.odysee.com:50001

(Hub servers index the metadata from blockchain in a database that can be queried. https://github.com/lbryio/hub)

Not sure how it selects. But if you prefer to use default servers, you can just remove or comment out that line completely.   Generally default servers should be up, so rarely need to handle hubs manually.

Ok. I suppose I will just leave it as it is now with three servers (including the two defaults) manually added and see if this happens again. I'll close this issue, but at least there's a solution here to try for anyone else having this issue from time to time.


model didn't exist.  Delegate to source to fix

I'm not sure why this happened all of the sudden.  Was causing page_entries_info not to work.  See this StackOverflow question:
http://stackoverflow.com/questions/2601265/link-to-not-working-in-script-console

Any possibility to get the two PRs merged and released?  I'm also happy to help if you give me access to the repo / rubygems.


Backend rewrite

The main backend functionality has been rewritten in Go. As a result, the entire application now weighs about 8MB and can be run either from a Docker container or as a single executable file.
Examples of compiled binaries, ready to run and weighing only ~5MB, can be found here: https://github.com/skrashevich/chatgpt-web/releases/tag/go-backend-nightly
Docker container: docker run -it --rm -p 3002:3002 -e OPENAI_API_KEY=$OPENAI_API_KEY skrashevich/chatgpt-web:go-backend (image size ~6MB)

Hey buddy, it looks really good. But me and my other maintainers are not familiar with Go

Although I am a fan of the Go language, I strongly recommend that this Go implementation of the backend be put in a new project instead of being included in this project. If joint debugging is required, tools such as node-foreman, forego with Procfile support, or pm2 can be used.
虽然我是位Go粉，但我强烈建议，这个Go实现的后端放在放在一个新的项目中，而不要放在这个项目里，如果需要联合调试，可以尝试使用支持Procfile的node-foreman、forego等工具或者pm2也可以

重新开了一个独立的后端项目，使用 Golang 实现 https://github.com/liut/morrigan，敬请关注

I checked the code and found that OPENAI was not used_ ACCESS_ TOKEN, is the ChatGPTUnificialProxy API request method missing
我查看了一下代码，发现并没有使用OPENAI_ACCESS_TOKEN，是否缺失 ChatGPTUnofficialProxyAPI 请求方式


clusterloader2: Fix error of probes about metrics-server

What type of PR is this?
/kind bug

What this PR does / why we need it:
When using InClusterAPIServerRequestLatency to measure the latency of metrics-server, need to add serviceMonitor and other information, and update the probe image
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

"NONE"

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

"NONE"

Plan to use perf-test in kubernetes-sigs/metrics-server, which requires the probe resources, fix the bugs
/cc @mborzx @mm4tt

/test pull-perf-tests-clusterloader2

/assign @marseel
@marseel - can you please help with pushing the new image?

/approve
But we need to push the image before lgtm-ing.

I've pushed 0.0.5, but please change also util-images/probes/Makefile version from 0.0.4 to 0.0.5

I've pushed 0.0.5, but please change also util-images/probes/Makefile version from 0.0.4 to 0.0.5

Hi, @marseel I have applied all modifications, any other updates?

/lgtm


Email adress with quoted local part has quotes truncated

Example of an email address which is valid according to https://en.wikipedia.org/wiki/Email_address#:~:text=example.org.-,Examples,-[edit]
From<EMAIL_ADDRESS>AddressHeader->getEmail() returns<EMAIL_ADDRESS>which is invalid as quotes are missing.

That's a very good point.  Thanks for that :)
Fix will come soon.

Released in 2.3.0


[WIP] Introducing Node for py-libp2p

What was wrong?

The first step of migrating from the existing p2p code to py-libp2p.
The local package name libp2p conflicts with the dependency libp2p/py-libp2p.

How was it fixed?

Add Node to contain the components in py-libp2p we need.
Change the name of the existing package libp2p to libp2p_daemon_bindings.

To-Do

[ ] Add needed API and components in Node.
[ ] Test, test, test.

Cute Animal Picture

Will fix the CI tomorrow and this PR should be ready by the time. 🙏

Should be ready now.


Ansi escape character doesn't work

I'm writing a discord bot which renders code. I wrote a lexer and it works fine.
The problem: When I use highlight() to highlight my string, it outputs something like \x1b[37m# % H\x1b[39;49;00m\x1b[37m\x1b[39;49;00m\n
Se the escape characters: \x1b. What I need though is \u001b. How can I get the desired escape character and if I can't, please add the option to change it.

You're using TerminalFormatter I assume? It doesn't output the 4 character string \x1b literally, just the one control character (escape). That representation is just how Python represents that character when using repr() on a string.


Remove a Brick and Update the Elements

Hello,
first of all, thank you for this awesome plugin!
So, when i remove a brick from my grid, which method i could call to get the new number of elements in my grid?
Because, when i call:
$('.gridly').gridly('draggingEnded'); // Forcing call the reordered callback
the callback is called passing the old elements, with the element i removed before.
Anything i can do?

From sample.css:
$(document).on("click", ".gridly .delete", function(event) {
  var $this;
  event.preventDefault();
  event.stopPropagation();
  $this = $(this);
  $this.closest('.brick').remove();
  return $('.gridly').gridly('layout');
});

Then to get a count you can use the jQuery length methods:
%('.gridly .brick').length

From sample.css:
$(document).on("click", ".gridly .delete", function(event) {
  var $this;
  event.preventDefault();
  event.stopPropagation();
  $this = $(this);
  $this.closest('.brick').remove();
  return $('.gridly').gridly('layout');
});

Then to get a count you can use the jQuery length methods:
%('.gridly .brick').length


LayerNorm class duplicate

https://github.com/Becomebright/GroundVQA/blame/de7c1c663c315f9edaa576755fa850f1d66bdd9b/model/ours/nlq_head.py#L326
Hey there,
just noticed that the LayerNorm class appears twice in the code.
Once in line 326 and once in line 9 :)

Thanks a lot for pointing this out. It's fixed: https://github.com/Becomebright/GroundVQA/commit/7aceb17d1a7dab126e46335a8c5f0dbfa454c111.


[Fix] Update Code of Conduct

Update official code of conduct in the website FreeCodeCamp.com/code-of-conduct with the one in the wiki Code of Conduct (wiki) which was updated recently.
Related Files:

File to Update: code-of-conduct.jade (FCC repository file)
Reference File: Code-of-Conduct.md (FCC wiki file)

Need Help? Read CONTRIBUTING Guidelinesor Chat with us in  FreeCodeCamp/HelpContributors

Currently Assigned to: @josevill

If you want to work on this, please comment below and we can chat over  gitter
Note: you may be assigned only if the current assignee doesn't respond within a given time-frame.

I will make a PR later today on this matter.

I would like to do this, if not done already.

@josevill Are you working on this fix? If not I will assign @nishant-tomer.

Link broken for reference file : Code-of-Conduct.md

@nishant-tomer since you have already made a PR, we may accept it this time. But please make a note that you can resolve only one "first-timers-only" only issue.
@theflametrooper already accepted the other PR. (which should have been rejected because the issue had a PR already)
Nevertheless in good spirit and the hard work you have put in is much appreciated.
Thanks again for contributing.

oh oh oh! I see. my bad. Thank you for explaining this or i'd have gone on with this streak. I'll take care from now on.

@nishant-tomer
Keep those PR's coming, please go wild on taking down as many "help wanted" ones :wink: , we encourage you to! But as you have already noticed just not on the first-timers-only ones!
Thanks a lot again for contributing!


Tooltipster with bing map

Hi. I am loading a div containing a bing map as content of tooltipster. The map shows up in the tooltip but the map is not interactive . Am I using tooltipster in a wrong way?
http://jsfiddle.net/UxND3/129/

Hi, it's your map that does not like to be moved around in an unproper way. Check this out, the map is working : http://jsfiddle.net/UxND3/130/

That's great. Thanks !


feat: add last successful run for each provider to the metadata

adding the last successful run timestamp for all providers to the grype-db metadata.json file

Closes #255


Hello! The csharp code hint is incomplete.

Hello! The csharp code hint is incomplete.

Please troubleshoot it carefully. I hope to see you fix it in the next version. Thank you very much!
vscode window zoom level is 2
OmniSharp 1.25.3
vscode 1.74.3
dotnet sdk 7.0.101
Windows 10 19044

This bug has been around for a long time and hopefully the team will fix it soon.

Code documentation information error


Documentation pages header shrink/redesign

Fixes #1865
Fixes #1907
Fixes #1914
The new header is much smaller.
I compacted the main top header with the logo and menu into the breadcrumb, which fixes #1907. I also integrated the multiple archive links into the breadcrumb, too, which fixes #1865. Finally, I introduced selected states on the breadcrumb dropdown menus, fixing #1914.
Lots of screenshots are incoming! Discussion on the design is welcome.
The simplest possible case. One version and one set of documentation archives:
The dropdown on the version still shows, but it also shows that the default branch is selected. Also, note that no warning about being on the default branch is visible as there is no stable branch with documentation.

Multiple versions of documentation with the stable branch selected

Multiple versions of documentation with the default branch selected
Here's where the warning comes in. There is stable documentation, so people should know about that.

Multiple versions, multiple archives

LOTS of archives

I approved the Percy build, but someone else should take a quick look, too. There should only be two snapshots that have changed (including one renamed snapshot, which is why it says there's a missing snapshot). However it has marked lots of snapshots as changed, but with no visual diffs that I can see.
Weird

I'm not sure how to interpret this but it's not really flagging any diffs. I see two "new" snapshots (first one and one towards the end), lots of "reintroduced" snapshots like this:

and one actual diff - which I guess is the change?

I'm not sure how to interpret this but it's not really flagging any diffs. I see two "new" snapshots (first one and one towards the end), lots of "reintroduced" snapshots

Yea, I'm not sure what's going on. It has never done this before.

and one actual diff - which I guess is the change?

There are two real diffs, but I also renamed one of the tests (it was incorrect) and so maybe my rename messed this up.

As an aside, should we drop the "Switch to" from the drop down? It's pretty clear how drop downs work, isn't it?

Is there a way to force percy to re-compare? Maybe that shakes it lose.

Is there a way to force percy to re-compare? Maybe that shakes it lose.

I just had a quick look and I don't think so. I think it'll be fine. Once this is merged, it will adjust the base screenshots to match these.

As an aside, should we drop the "Switch to" from the drop down? It's pretty clear how drop downs work, isn't it?

Removed


[feature] Packages aliasing

Hi, I would like to request for the packages aliasing feature which can help quite a lot when we are working with github forks.
This issue may duplicates #64  but it was closed.

Would an "origin" field referencing the full path to a different repo location be acceptable (this is what vendor.json does)?
So you would have something like this to "alias" the package github.com/heroku/slog from the location github.com/freeformz/slog.
...
"Deps": [
  {
    "ImportPath": "github.com/heroku/slog",
    "Origin": "github.com/freeformz/slog",
    "Rev": "abcdefg"
  }
]
...

restore would also have to add the other remote somehow and also fetch from there. Maybe it's okay to punt on that though to start?

I think that's a good start. @freeformz

Any progress? @freeformz

@on99 @freeformz Any progress on this feature?

What is the status on this?

I'm not actively maintaining godep anymore. I should update the README to reflect that. I suggest taking a look at dep instead.


Find a solution to track our projects & tasks

Currently trying GitHub issues with projects

Everybody seems happy with using GitHub issues & project so far. We can revisite if it doesn't fit our needs in the future.


Pin pytest to 3.2.2 and pytest-catchlog to 1.2.2

High-level description
The default pytest version moved to 3.4.0 and apparently in this version catchlog (AKA the caplog fixture in pytest) stopped working and so the test that checks the log stream failed.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:
https://jira.mesosphere.com/browse/DCOS_OSS-2124
Checklist for all PRs

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: N/A this fixes the test
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

@mesosphere-mergebot bump-ee


Fix the shaded issue with Apache Pulsar

As mentioned in #7221, Apache Pulsar plugin did not create the
shaded jar. This PR addresses it. Moreover, we also fix the
javadoc lint issue when building the apache release.

Codecov Report

Merging #7223 (6f9f24c) into master (069bae0) will decrease coverage by 8.21%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #7223      +/-   ##
============================================
- Coverage     73.46%   65.25%   -8.22%
  Complexity       92       92
============================================
  Files          1508     1508
  Lines         73951    73951
  Branches      10685    10685
============================================
- Hits          54330    48255    -6075
- Misses        16054    22277    +6223
+ Partials       3567     3419     -148

Flag
Coverage Δ

integration
?

unittests
65.25% <ø> (+<0.01%)
:arrow_up:

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

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


Typo - "pricacy.html" should likely be "privacy.html"

https://github.com/alexa/skill-sample-nodejs-fact-in-skill-purchases/blob/c8a63fde3164d18fdb96ca4a4cdae380927d1203/isps.samples/entitlement/history_pack.json#L44

Corrected spelling of 'privacy' in entitlement and subscription files.


Saving line's color

Saving line's color, despite possible colorful lines inside.
Now lines such as:
message = colored(str(x), 'red') + ' divide by ' + colored(str(y), 'red') + ' without residue'
cprint(message, 'yellow')
Will be keep in save their start color.

Not done yet, my fault


Implementation of ReleasePartitions

Issue: #44
Signed-off-by: Ji Bin<EMAIL_ADDRESS>

/cc @yhmo
/cc @ArkaprabhaChakraborty

/lgtm


Properly Implement StringSegment and StringSegmentComparer GetHashCode

From @Tratcher on Monday, May 22, 2017 3:41:08 AM
https://github.com/aspnet/Common/issues/213
StringSegment.GetHashCode and StringSegmentComparer.GetHashCode(StringSegment) both substring and then string.GetHashCode() which defeats the purpose of using StringSegment.
Note that .NET Core strings use randomized hash codes to mitigate issues like dictionary hash collision attacks.
The header parsers in HttpAbstractions call both of these methods the header value types GetHashCode implementations, but I'm not aware of any instances where those header value types are used as keys into hashed collections.
Copied from original issue: aspnet/Common#232

This is no longer blocked 👍 See: https://github.com/dotnet/coreclr/pull/20422/files#diff-3f06377a79f6009a753e2864e9bdaab6R774
We should look for other places we can use this new functionality - possibly ModelStateDictionary or anywhere else that StringSegment is used.


[cluster-test] add gas price non zero test

Motivation
Add new test with non zero gas price to see performance difference with gas price = 0
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
./scripts/cti -W zihao --pr 6179 --run bench -- --gas-price 1
====json-report-begin===
{
  "metrics": [
    {
      "experiment": "all up, gas price 1",
      "metric": "avg_txns_per_block",
      "value":<PHONE_NUMBER>813187
    },
    {
      "experiment": "all up, gas price 1",
      "metric": "submitted_txn",
      "value": 150360.0
    },
    {
      "experiment": "all up, gas price 1",
      "metric": "expired_txn",
      "value": 0.0
    },
    {
      "experiment": "all up, gas price 1",
      "metric": "avg_tps",
      "value": 626.0
    },
    {
      "experiment": "all up, gas price 1",
      "metric": "avg_latency",
      "value": 7272.0
    },
    {
      "experiment": "all up, gas price 1",
      "metric": "p99_latency",
      "value": 8800.0
    }
  ],
  "text": "all up, gas price 1 : 626 TPS, 7272 ms latency, 8800 ms p99 latency, no expired txns"
}
====json-report-end===
2020-09-24T20:15:28.379671Z [main] INFO testsuite/cluster-test/src/main.rs:230 Experiment Result: all up, gas price 1 : 626 TPS, 7272 ms latency, 8800 ms p99 latency, no expired txns

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/libra/libra/developers.libra.org, and link to your PR here.)

I will add it into nightly run by a separate pr

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

:broken_heart: Test Failed - Build images and run cluster test

/land

:broken_heart: Test Failed - commit-workflow

/land


Send a direct message

I'm trying in any possible way to send a direct message to an user, but I can't find a way. Please can you help me?

I found a way to response to an instanciated chat, but I can't init a new chat. Any advise?

Assuming you're logged in:
const userId = await ig.user.getIdByUsername('username');
const thread = ig.entity.directThread([userId.toString()]);
await thread.broadcastText('Message from node');

Yes it's work. I forgot to write a response. Thank you.

I want create a chatbot for direct Instagram. I need to listen the chat from keep the conversation. This is possible? How?

Hello @trandreluis, you need to use the instagram_mqtt library by Nerixyz.
If you need help I'm available on Discord! Androz#2091

Thanks, man! I will analyze and test!

user

const userId = await ig.user.getIdByUsername('whitestorm_.07');
const thread = ig.entity.directThread([userId.toString()]);
await thread.broadcastText('Message from node');


[Python][CI] Failing test_dateutil_tzinfo_to_string due to new release of python-dateutil

Describe the bug, including details regarding any error messages, version, and platform.
test_dateutil_tzinfo_to_string started failing with:
         tz = dateutil.tz.gettz('Europe/Paris')
>       assert pa.lib.tzinfo_to_string(tz) == 'Europe/Paris'
E       AssertionError: assert 'Europe/Monaco' == 'Europe/Paris'
E         - Europe/Paris
E         + Europe/Monaco

see: https://github.com/ursacomputing/crossbow/actions/runs/8103088008/job/22164107523#step:6:4305.
This is most probably due to new release of python-dateutil package.
The test is failing on the CI now also, with dateutil 2.9.0: https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/49322144?fullLog=true
Component(s)
Continuous Integration, Python

cc @raulcd

I can't reproduce this on Linux, so most probably a Windows issue (or related to the exact tzdata being used there, since for me locally it's using the system provided data)
Might be good to report upstream?

The logic we use to convert a dateutil tz to a string:
https://github.com/apache/arrow/blob/2b194ad222f4dc8ecf2eb73539ab8cab5b1fc5e7/python/pyarrow/src/arrow/python/datetime.cc#L554-L568
(so it might also be that something changed under the hood in dateutil that messes that u. It would be good to verify if the actual tz object in the snippet above, before conversion to a string by pyarrow, also shows "Europe/Monaco")

Agree with you Joris. I would first like to check the behaviour of dateutil, as you mention, but also can't do that on my M1. I could in any case open an issue upstream before, if we think that makes sense.

The same issue is being reproduced on my PR on the conda feedstock:
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=888527&view=logs&j=ab98fee7-5bc6-5c2f-a410-3ab9b2f2e8ca&t=472408ae-fc68-5791-981c-69ea41d2d692&l=38399
    def test_dateutil_tzinfo_to_string():
        pytest.importorskip("dateutil")
        import dateutil.tz

        tz = dateutil.tz.UTC
        assert pa.lib.tzinfo_to_string(tz) == 'UTC'
        tz = dateutil.tz.gettz('Europe/Paris')
>       assert pa.lib.tzinfo_to_string(tz) == 'Europe/Paris'
E       AssertionError: assert 'Europe/Monaco' == 'Europe/Paris'
E         - Europe/Paris
E         + Europe/Monaco

A temporary skip was added in https://github.com/apache/arrow/pull/40486


Can storage proofs be implemented using bitvm?

Storage proofs are used in some altcoins, e.g. Sia
The idea is that one participant (renter) uploads data to another participant's server (host). The renter and host lock some funds in a contract. After predefined period of time, if the host publishes a storage proof on Sia blockchain, the funds go to the host. Otherwise the hosts looses his funds (the collateral) as a punishment of failing to provide storage proof.
Storage proof is a merkle proof of random 64 byte segment of the stored data, which is chosen based on block hash at a certain block height, predefined in the contract.
Can a similar contract be implemented using bitvm? I don't know other ways to implement storage proofs in Bitcoin blockchain.

It certainly sounds possible. The merkle tree of stores bits would be known in advance by both host and client, and the host could send their proof to the client (I don't see why posting it to the blockchain would be necessary). If the proof is wrong the client can slash the host.

It is necessary to post the proof on blockchain at least in non-cooperative scenario to enforce the penalty for the host for not storing the data. Absence of a proof is interpreted as host losing data. Penalty can not be done client side, because how one can prove absence of something?
So, let me define it in more formal way. A (renter) and B (host) agree on storing some amount of data provided by A for certain period of time, defined in blocks. A allocates funds to cover payment for storage and B allocates a collateral. There is a certain agreed upon ratio between payment and collateral, say 1:1. All that money is locked in a smart contract. As time passes, A uploads data to the contract. Each successful upload results in updated balances in the contract and updated Merkle root. There are 2 outcomes in the contract, each having two outputs: to A and to B:

Successful outcome sends change back to A and earned money + collateral to B.
Penalty outcome sends the change of collateral (the unspent part) to B and the remaining of money to A.

Both outcomes are updated upon uploading, moving some money from one output to another.
After the storage contract expires, B has certain time [block height] window to publish a storage proof. Publishing storage proof unlocks the successful outcome of the contract. Non publishing results in penalty outcome.
That is more or less how this is done in Sia. (They also burn the collateral in penalty case, but I think it should be sent to A as compensation for lost data.)
In Bitcoin it could work more or less the same, with the same incentives structure, but the cooperative case might happen without publishing a Merkle proof, similar to cooperative channel closure in Lightning Network.

Good point about proving the absence of something. I suppose the proof needs to be posted somewhere public, but I'd prefer to use a spacechain for that instead of clogging up bitcoin.


Update parallel TEST_TIME logic

enable TEST_TIME option
if the TEST_TIME is not achievable, set NUM_MACHINES to machine limit

grinder: Grinder/33436/

FYI v0.9.8-release is created.

Grinder_TKG/1908


Why the temperature is set to be 1?

According to the example provided by OpenAI and the doc, tasks like grammar check requires higher deterministic so the temperature should be set closed to 0. However, I also found 0.8 or 1 have better results. What's the reason for this?

@Matt-Zhang Hi Matt,
High temperature produces more creative content than low temperature. It will not answer you based entirely on what AI trained (and 0 will do so to a large extent).
In addition, the low temperature gives less criticism to the AI, which results in the AI answering the question from the perspective of a superior student, so the resulting answer is better for the AI, but we do not think so.
In short, it is like facing the orientation of a student. If it is positioned as a superior student (low temperature), then it will have absolute confidence to answer your questions, and it will tacitly agree that the questions it answers are correct. And often intermediate students (around 1), will answer your questions with scepticism, and may question their own answers, in the continuous optimization of the answer will become more perfect.
Hope it helps.

Please note that if there is no further conversation, this issue will be closed within 24 hours.


GitHub workflows

added github workflows for tests

Those aren't needed on this repo.

I thought that it will be helpful at the time of testing.

And can we add Travis for testing?

What are the tests?

What are the tests?

Yeah, you are right. In this repo we don't need this because there are no tests for performing.

But in this case, tagbot will help us to create tags, releases, and changelogs for our Julia packages when it will register.

As the julia package DiffEqTutorials is registered because it has a good resource of tutorials and other things. We can also do the same for this repo. And now it's up to you. 🥰

This repo would need a pretty substantial change for that to be useful IMO. I think there's a lot of issues with the reliance on notebooks that this approach has.

Oh, I see but we can do those substantial changes. As mostly I would like to spend my time on Julia related projects. So, it will help me to deep dive also. 🤔


Issues with Docker-compose volumes

I'm trying to create a docker-compose for this just so its easier to spin up the server. However, for some reason I cannot use a volume in the base directory that the container creates. If i use ./minecraft-data:/minecraft/world. It works, but, if I bind that I can't edit the server properties or other server config files.
version: "3"

services:
  ftb:
    image: jonasbonno/ftb-infinity
    ports:
      - 25567:25565
    tty: true
    stdin_open: true
    restart: always
    volumes:
      # attach a directory relative to the directory containing this compose file
      - ./minecraft-data:/minecraft
    container_name: ftb

Running that compose gives me this error. Do you know how I might be able to fix this?
ftb    | /bin/bash: /minecraft/ServerStart.sh: No such file or directory

You cannot use that volume path because that is where the binaries files are, and mounting it to a empty folder would make impossible for the container to start the server binaries.
Instead use "/minecraft/world"

That's odd because I've done other minecraft servers with docker-compose using that command and didn't have any issues. I mainly want to just use docker-compose so I can spin it up/down quickly.


Errors appeared literally out of nowhere

Describe your problem here.
I literally just commented out a lines of code THAT i added in StoryModeMenu:

then i recompiled and these are the errors i got:
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/texture/FlixelTextureLoader.hx:6: characters 8-33 : Type not found : spinehaxe.atlas.AtlasPage
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/texture/FlixelTextureLoader.hx:7: characters 8-35 : Type not found : spinehaxe.atlas.AtlasRegion
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/texture/FlixelTextureLoader.hx:8: characters 8-37 : Type not found : spinehaxe.atlas.TextureLoader
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:26: characters 8-42 : Type not found : spinehaxe.animation.AnimationState
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:27: characters 8-46 : Type not found : spinehaxe.animation.AnimationStateData
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:28: characters 8-29 : Type not found : spinehaxe.atlas.Atlas
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:29: characters 8-35 : Type not found : spinehaxe.atlas.AtlasRegion
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:30: characters 8-40 : Type not found : spinehaxe.attachments.Attachment
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:31: characters 8-44 : Type not found : spinehaxe.attachments.MeshAttachment
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:32: characters 8-46 : Type not found : spinehaxe.attachments.RegionAttachment
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:33: characters 8-51 : Type not found : spinehaxe.attachments.AtlasAttachmentLoader
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:34: characters 8-22 : Type not found : spinehaxe.Bone
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:35: characters 8-26 : Type not found : spinehaxe.Skeleton
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:36: characters 8-30 : Type not found : spinehaxe.SkeletonData
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:37: characters 8-30 : Type not found : spinehaxe.SkeletonJson
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:38: characters 8-22 : Type not found : spinehaxe.Slot
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:59: characters 116-128 : Type not found : SkeletonData
source/FreeplayState.hx:27: lines 27-534 : ... Defined in this class
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/texture/FlixelTextureLoader.hx:10: characters 38-51 : Type not found : TextureLoader
source/FreeplayState.hx:27: lines 27-534 : ... Defined in this class
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:534: characters 15-23 : flixel.addons.editors.spine.FlxSpine has no field skeleton
/home/koki1019/haxelib/flixel-addons/2,11,0/flixel/addons/editors/spine/FlxSpine.hx:553: characters 15-23 : flixel.addons.editors.spine.FlxSpine has no field skeleton
source/PlayState.hx:5318: lines 5318-5323 : Warning : This case is unused

I have all libraries needed i even reinstalled haxe nothing seems to work and i have no ideaaaaaaa why
I even installed spinehaxe same error
Are you modding a build from source or with Lua?
Source
What is your build target?
Linux
Did you edit anything in this build? If so, mention or summarize your changes.
Pretty much just added mechanics in PlayState.hx they work fine. also edited the MenuState.hx, just moved the buttons on the right works fine and also edited StoryModeState.hx and that works fine too

Error has been fixed
All i had to do is install git version of spinehaxe and add it in project.xml file


add ci/ small fmt fix

add a github action for automated testing and formatting.

great thanks! only pb is the tests all fail rn (we have to fix the init).


[6.3.x] BZ1299870: GSS Business Central Repo Clone Fails To Clone SCP Style SSH URLs

See https://bugzilla.redhat.com/show_bug.cgi?id=1299870
This is the corollary of https://github.com/droolsjbpm/kie-docs/pull/51 for 6.3.x.
NOTE 6.3.x has a different BZ number but the fix is the same.
(cherry picked from commit 0ad5346afa79250460a3dd0bc9c48c4920c6ace5)
Conflicts:
shared/Workbench/Installation/Installation.xml

merged into 6.3.x


Add docs for cli commissioner command.

Document the early version of commissioner cli command.
Fixes #642.

Current coverage is 65.05% (diff: 100%)

Merging #647 into master will decrease coverage by 0.09%

@@             master       #647   diff @@
==========================================
  Files            99         99
  Lines         14338      14338
  Methods        1972       1972
  Messages          0          0
  Branches       1684       1684
==========================================
- Hits           9341       9328    -13
- Misses         4466       4476    +10
- Partials        531        534     +3

Powered by Codecov. Last update 4bd6297...5dee330

Deprecated by #668.


Drag and drop doesn't work if tab is not nested in the main window

Drag and drop doesn't work if tab is not nested in the main window. It just shoots everything in early hours that I don't even see on the screen.
A temporary work around could be if I could have a duplicate window of the day planner on a second screen and another one as side panel for editing.
PS: it's already mentioned in another topics but I'd like being able to treat some night crunches that are going beyond midnight as day of work that I started.
PSS: Thank you very much for your plugin Ivan, it's so useful for me. Your work is much appreciated

Drag and drop doesn't work if tab is not nested in the main window. It just shoots everything in early hours that I don't even see on the screen.
I came here to report the same issue. I use multiple monitors and I like to drag the weekly planner to a different screen when I am planning out my week.

Thank you so much for making this! I LOVE the new updates.


Add realcompactification of Rudin's space and basic properties

See #1139
While I'm not confident about Rudin's original proof that this space is ultraparacompact, I am confident that it is ultraparacompact. See those notes by K. P. Hart (maybe I should add those as a reference?).

It seems that you forgot to add ~T5.

It seems that you forgot to add ~T5.

Yes, although #1135 is still open, so I'm not sure if I want to add this in this PR

It seems that you forgot to add ~T5.

Yes, although #1135 is still open, so I'm not sure if I want to add this in this PR

#1135 is solved now, it seems you can added {S208|P8} now.

I thought "realcompactification" always refers to Hewitt realcompactification.  Is there another one?
If not, the shorter name "Realcompactification of Rudin's Dowker space" would be better.

@prabau Just as "compactification" doesn't always refer to Stone-Cech compactification, similarly "realcompactification" doesn't always refer to Hewitt realcompactification.


[App]: Unable to display runs for large number of total runs in workspace

Current Behavior
In Workspace, lists of runs cannot be displayed. It shows 0/ of 0 runs although the total run number is large.
Can you fix this? Or how can I get it back to normal? With a specific run web link, I still have access to the run. But it's really hard to find out the runs now let alone to sort and filter them. When the total run number is large, it's disappointing. Thanks!  Looking forward to your reply.
Expected Behavior
No response
Steps To Reproduce
No response
Screenshots

Environment
OS: Windows11/Ubuntu20.04
Browsers: Chrome/Firefox
Version: 120.0.6099.199 for chrome
Additional Context
No response

Hi @Lily-Le , happy to help. Could you provide me a link to the affected project for us to review (you may keep it private).
This could be happening due to a visibility selection, could you check if "Visualize None" is not toggled on. To access, select the eye next to Name.

Hi @MBakirWB  Thanks for the quick reply. It gets to normal now. But the problem is not caused by visibility selection as the eye is open. I toggled on 'visialize all'  then.  And even if I toggled on 'visualize none' , at the end it shoud show xx of 3302 but not 0 of 0.

Hello @Lily-Le , glad that it is normal now. We'll mark this as resolved but feel free to write in again when you have more questions or this weird behavior comes up again.


Optional customer managed keys

KMS Customer Managed Keys are expensive.
I'm looking at the cost examples in the documentation. Take the first one, $3.30/month. I believe it's wrong. 10 accounts is 10 keys. That's an extra $10/month.... the first year, then 20, 30 and so on.
Using customer managed keys should be opt-out by parameter.
Or having a shared key on the administrator account.

Hello, thank you for bringing this to our attention! As of now this is something we can offer in a future release with some caveats — a few remediations depend on this key so you’d be missing functionality for CloudTrail.1, CloudTrail.2, CloudWatch.2, Config.1, SNS.1, and SQS.1. I’ve added this to our backlog internally so we can track this.

I agree with @camitz . I am investigating using this to auto remediate security issues in our AWS Org. We have enabled Control Tower and have about 120 accounts with 4 regions enabled. The automated response solution would cost 120 * 4 * $1 = $480 in KMS keys alone, but outside of the cost of the keys, it would only come in around $55, based on my estimates of the number of checks we have failing.
This means KMS costs would be 90% of the total monthly running cost, meaning the solution wouldn't really stack up for us at the moment.
Control Tower (and the CfCT which I would use to orchestrate the deployment) already has a common place for CMK KMS keys - in the audit account - and other AWS solutions such as the SRA utilise this to create a KMS key that is shared to the org. Here is an example of the SRA pre-requisite stack that creates a key shared to the org: https://github.com/aws-samples/aws-security-reference-architecture-examples/blob/main/aws_sra_examples/solutions/common/common_prerequisites/templates/sra-common-prerequisites-secrets-kms.yaml.
A solution like this may only be suitable for a Control Tower setup, but it would represent considerable cost savings over the current key per account, per region setup.


alicloud data conncetor - re-implement with storage-queue

Change(s):
This is a full re-implementation of this function, since it's not resilient, can't handle high scale, and is very vulnerable to timeouts (which apparently, Ali endpoints have a tendency to cause in high scale).
In short, this function has been split into 2 functions (time triggered sends messages to storage queue, & queue triggered that handles each storage queue message).

TimeTrigger - Similar to the existing function for GoogleWorkspaceReports.

Runs every X minutes (configurable - 4 minutes by default)
Retrieves list of projects from Ali endpoint (if necessary; if customer included list of needed projects in config, no need)
For every project, retrieves list of log stores from Ali endpoint.
Filters out unwanted log stores (if configured).
For each project, log store & time window (by default 1 minute, can be changed by customer), creates a message in the storage queue.
Each message indicates a data-polling job that needs to be performed by the 2nd function. So if we run every 4 minutes for 2 projects & stores, each run of the function will create 8 messages in the queue (and allow the 2nd function to run with 8 separate instances, one per queue message).
We rely on a bookmark to continue for each project from the previous date-range we scheduled. The difference from before is that now we have a bookmark per project, and not for entire run.
If storage queue has too many items (it indicates that the 2nd function isn't running or has a problem), we don't send more into the queue, so not to cause to much load. If queue has 1k items, our timer function will just wait until there's room in the queue (again, similar to the googleWS connector).
As in the previous version, we only schedule data retrieval for minimum 10-minutes ago from Ali cloud (this remained as before, since we don't want to miss late-arriving data in Ali, so if now is 8:00, we don't schedule message for 7:51, only for up to 7:50.
Note: we use a 2nd queue called "poison" queue - it gets messages in case the 2nd function (Queue trigger) throws an exception or is killed due to runtime timeout.
TimeTrigger checks the poison queue. If it finds any messages, it checks them. If there's a basic error in the message (corrupt/illegal message) or if the message reached it's max internal retry (15 by default), it moves that message to the dead-letter queue (no one is querying that queue, so it will just remain there for the customer to monitor, or clear).
If the poison message is valid, we assume that it's because of a timeout (that's almost usually the case). In that case, we increase the internal retry by 1 (to prevent infinite processing of same message). We try to split the message into upto 4 separate messages (if the original message was for 1 minute worth of data of project & store X, it will be 4*15 seconds for same project & store X) and re-submit to the main queue (if we reached the minimal size of 15 seconds, we don't split, and just resubmit to main queue as-is, assuming the failure was due to runtime exception). The goal is to handle cases where too much data exists in the same 1-minute chunk in Ali (happens from time to time), so would causes consistent 10-minute timeout of this function.

QueueTrigger - runs when a new message is received in the storage queue. Performs the data collection from Ali endpoint according to the data included in the message (project, store, time range).

LA-post resiliency - previously, if we failed to send a given chunk of events to LA, we would only print an entry to the log and that's it. That's problematic since it's data loss for the customer that will probably get unnoticed. Instead, we now treat LA-send failures just like any other failures. We retry the function until max-retry, etc. Also, in case of transient failures for LA-send operations (http status >= 500 only), we perform up to 3 internal retry attempts (during same function execution, not causing the function to stop and waiting for a new run).
Failure handing - assuming we experienced a failure or caught an exception, our azure function doesn't throw an exception. Instead, we schedule a similar queue message (with invisibility of 1 min - so it's taken for retry in 1 minute) with same details and increased internal dequeue_count field and gracefully stop (so function doesn't appear as failed in azure; azure runtime will delete the original message on its own automatically). However, if dequeue_count reached 15, we move the message to a poison queue. The time trigger function will move it to the dead-letter-queue if needed.
Timeout handling - both functions have an internal timeout mechanism that causes it to gracefully stop before the runtime timeout and kills the function on its own. So if we defined 10 minute runtime timeout, each function has 8-9 internal timeout; so if we reached that internal timeout mark, we gracefully stop. This allows us to continue from where we left off in the next retry, and also reduces the failure noise for the customer (again, if we get 15 straight timeouts on the message, it will not be re-tried and the function will be flagged as failed).

Change ARM template to have different env variables -

AliCloudWorkers - removed. No need as concurrency is now handled automatically by azure runtime (since one function per queue message).
MaxWindowSizePerApiCallInSeconds - determines the time range of each queue message. by default, 1 minute. It's helpful when there's high scale and retrieving X-seconds worth of data takes too long. So customer can increase if there aren't scale issues, and reduce it if there are.
MaxQueueMessageRetries - determines how many times the message is re-tried (due to caught exceptions and failures) before stopping and moving to poison queue. By default it's 15. Note that this does NOT change the number of retries for uncaught exceptions (and runtime failures), this cannot be dynamically configured (as it's defined in host file) and is always 15. However, in most cases, failures will be caught failures.
TimerCronSchedule - allows the customer to control how often the TimeTrigger functions runs. By default it's every 4 minutes.
Added mock for Ali SDK - this isn't used (commented out), but it's in the package for easier debugging (has same relevant interface as the Ali SDK).
AliCloudLogStores - as requested by customers. Allow to filter out log-stores that don't appear in this list (assuming it was populated). This is an allow-list. If it's not populated, we process all log-stores for the supported projects.
Upgrade to Python 3.9 (since Python 3.8 won't be supported in azure function in a few months).

Reason for Change(s):
In high scale, the function keeps failing on timeout as it sometimes takes 10 minutes to retrieve 1 minute worth of data from Ali endpoints. Also, we need ability to run multiple function instances to improve latency (due to the latency mentioned above).
Version Updated:
No
Testing Completed:
Yes - Manual & with customer with high volume (with original timeouts issues).
Checked that the validations are passing and have addressed any issues that are present:
See guidance below

We wanted to check on the status of PR #10595. PR is pending for more than 30+ days. Please let us know if you need any assistance to review this PR. Per our standard operating procedures if no response is received in the next 7 business days, we will close this PR. Thank you for your cooperation.

Since we have not received a response in the last 30+ days, we are closing your PR #10595 per our standard operating procedures. If you still need support for this issue, you can re-open the PR at any time.
If you do re-open, we simply request that you ensure the PR has response to the last request. Thank you for your cooperation.