FilePickerContracts - OnCachedFileUpdaterActivated  does not fire on Before Access.

OnCachedFileUpdaterActivated  never fires on the BeforeAccess Example.  (Open Picker -> Pick cached file)
To replicate.
Stick a break point on OnCachedFileUpdaterActivated in App.xaml.custom.cs and CachedFileUpdaterUI_FileUpdateRequested in CachedFileUpdaterPage.xaml.cs
Select Open from a any Text app and select the file picker contracts app for the source
Select option 3 Pick cached file
Add file to basket.
Select open. The breakpoints are never hit
Looking at the code, there's a method AddFileButton_Click in FileOpenPicker_CachedFile.xaml.cs
This looks to be incorrect and hiding the problem.
It creates a new file and then populates the file with some text.
For this example I would expect the CachedFileUpdate to either populate the text or update the text when
ReadActivationMode.BeforeAccess fires the OnCachedFileUpdaterActivated  event.
The result is the file opens in the third party app with content but at no time is the cachedFileUpdater used.

This looks like it's a platform issue, but I've asked the samples team to look at it anyway. You'll probably have better luck (and responsiveness) contacting Developer Support:

Visit http://aka.ms/storesupport and sign-in with your Microsoft account
Under the “App Development” section choose "Windows 10 universal app development", then choose the appropriate problem type and category to get engaged through a formal support channel.

BeforeAccess CFU trigger only covers MostRecentlyUsed List and FutureAccess List accesses and not any type of access. CFU won't trigger for this type of access. I'm updating the sample to have a proper BeforeAccess example.

One language was updated, but the others haven't been done yet.

Fix is published in release v7.0.2.


[ci] apply cpplint to cpp tests

Only one issue left:
tests/cpp_test/test_chunked_array.cpp:42:  Is this a non-const reference? If so, make const or use a pointer: ChunkedArray<int> &ca  [runtime/references] [2]

Please help fix it.

@AlbertoEAF Could you please help with this https://github.com/microsoft/LightGBM/pull/4092#issuecomment-804032948 when have time?
You can checkout cpplint branch and make PR against it.

Thanks to @AlbertoEAF , this PR is ready for review.


[improvements] Return error to application and support SLO request validation

This PR contains the following improvements.
The reason for combining these changes into a single pull request (PR) is that they do not directly affect the gem's core features. Splitting my code into smaller PRs would require manual tasks, which can introduce bugs. Additionally, all these improvements have already been tested in a real environment.

Currently, the gem is failing silently and only provides logs which makes the application cannot take any actions based on failure. For example, it should display errors related to the customer's configurations. To address this, I added an error collection to the SAML request. After validation, these errors will be stored in an array for further processing.
Allow the application to retrieve metadata for usage that is not defined as unspecified_certificate.
Follow the metadata instructions on how to validate the Authn Request. If the metadata specifies that it should be signed, the IdP should accept a signed Authn Request.

@jphenow can you look at this one?


Update the Max base image

This PR updates the Max base image to be the latest one and updates the related parts.

@bdwyer2 Thanks so much for your review! Travis test passes now.


🚀 Feature Request: add Queue Produces support for Pages Dev

Describe the solution
Queue Producers can't currently be interacted with locally when using wrangler pages dev, as mentioned in our docs:
https://developers.cloudflare.com/pages/platform/functions/bindings/#interact-with-your-queue-producer-binding-locally
However Miniflare does provide support for them: https://github.com/cloudflare/workers-sdk/tree/main/packages/miniflare#queues
So supporting them in wrangler pages dev should be possible.

@dario-piotrowicz is this still valid? We do now support Queue Producers locally via Pages, but not consumers.

@admah no I guess this is no longer valid then, thanks for pinging me, I'm happy to close the issue 🙂👍

What's the flag for binding queues locally?  It's not in the --help or in the docs. eg: for d1 it's --d1


Split_screen_effect

Description
The screen splits and moves on mouse hovering and this effect can be used on websites . Built using HTML,CSS and Javascript.
Fixes #160
Type of change

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

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@thejaswin123 resolve conflict


Clean up exports

The DX of importing Base UI components should be cleaned up to avoid unnecessary noise:

Each component should be exported once, and not its parts
Types should be namespaces under component name
Hooks should not be exported

For example, typing Dialog in VSC should not suggest anything but the Dialog component.
Expected import styles:
import { Dialog } from '@base_ui/react';
import * as Dialog from '@base_ui/react/Dialog';

Shouldn't be a thing:
import { DialogRoot } from '@base_ui/react';
import type { DialogRootProps } from<EMAIL_ADDRESS>

Based on our discussions, we agreed to drop the import * as Foo pattern and replace it with import { Foo }, so it's easier to type and VSCode suggestions include it.
import { Dialog } from '@base_ui/react';
import { Dialog } from '@base_ui/react/Dialog';


BufferHelpers added to the tool kit

Added a new header with CreateStaticBuffer, CreateTextureFromMemory, and made the ConstantBuffer internal helper class public per request.
Also added to DirectXHelpers.h a CreateInputLayoutFromEffect helper.

Project file changes summary:

Added public header inc\BufferHelpers.h
Removed private header src\ConstantBuffer.h
Added src\DirectXHelpers.cpp

See version for the DirectX 12 in this pull requests

The test suite update is in pull requests


removed un-needed Ref from Client

PR for https://github.com/http4s/http4s/issues/6326
I'm not entirely sure this is the right direction, but though I would take a try at it.

Thanks for the PR! I think the original proposal was in https://github.com/http4s/http4s/pull/6325#pullrequestreview-951279467.

I don't think this needs the Ref unless the body is a Stream, but this is progress.

In series/0.23 the body is always a Stream so I am not sure if we can make this change here. However in main we have redefined the Entity model so that the body is not always a Stream. In those cases we do not need the Ref.

Thanks for the PR! I think the original proposal was in #6325 (review).

I don't think this needs the Ref unless the body is a Stream, but this is progress.

In series/0.23 the body is always a Stream so I am not sure if we can make this change here. However in main we have redefined the Entity model so that the body is not always a Stream. In those cases we do not need the Ref.

Thanks!  I'll take a look at the main branch and see if I can come up with the right idea.

Committed to wrong branch


Python3 compatible branch

All tests passing, seems fully working.

@atheiste, this looks like some great work. Python 3 compatibility for django-shop would be wonderful. Unfortunately, I cannot merge this because the code has simply changed too much. We must take a new look at Python 3 compatibility soon. Thank you.


Question about Battery Data Template

I have seen on the website https://industrialdigitaltwin.org/content-hub/teilmodelle that a Battery Data Template is under development.

Does anyone here have any "draft" of this template and know anything about the timeline when this will be published?
I would have expected a draft to be in this repository under the development folder.
Greetings
Benedikt

Dear Benedikt,
the KickOff meeting for the submodel "Battery Data Template"  took place just last Thursday, 2023-10-12.
Accordingly, there is no draft yet.
Best regards
Sebastian

Hi Sebastian,
thank you for the quick answer.
It this repository the place where the draft will be worked on and first published, or is there a mailinglist to see the ongoing development?
Greetings
Benedikt

@SAidta: Maybe you can help?

@SAidta is there any update?

Hi Benedikt,
@SAidta is currently on vacation. Maybe I can try to answer your question: usually, the IDTA develops the documents within Teams groups. After finalization, the documents are published like here on github. The working group meetings take place every 2 weeks. If you are interested in joining, please send me a private message.
BR
Sebastian (another one ;-))

Hi (other) Sebastian ;),
thank you for the information.
Ill send you a pm.
Greetings and thanks Sebastian^2
Benedikt


Update to version 3.4.0

MNT: Re-rendered with conda-build 3.21.8, conda-smithy 3.19.0, and conda-forge-pinning 2<IP_ADDRESS>.31.46

Checklist

[x] Used a personal fork of the feedstock to propose changes
Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Usage examples

Hi! Could you add an example for using the python library? I'm a newbie with python but It seems much more suitable for the Algo course than golang. I don't know how to use it to send test tasks.

The README for Python already contains a simple example, verbatim as follows:
from edx_io import edx_io

with edx_io() as io:
    io.writeln(io.next_int() + io.next_int())

Basically, you import the edx_io object from the edx_io module, open it using the with statement, and then perform the input-output operations on the resulting opened object (io in this case).
Note that io.next_token() would return a bytes object, not str. You can just convert it, as in str(io.next_token()) - however, this not only brings you some convenience, but takes some time, which becomes noticeable if you try to read tens of megabytes within a second - so be aware when solving harder problems.
The testing system already contains this edx_io.py file, so you don't have to send it along with your solution (and, in fact, you should not). For local testing, it is necessary to have a local copy, typically in the same directory as your solution (but this may depend on the IDE used).

Thanks


Remove full endpoint and related methods

/retest

/retest

/test trustyai-explainability-e2e

/retest


Upgrade rails 5.0.0

Coverage remained the same at 100.0% when pulling b07444a23b21e758f4847db95d9888f3debb5dfc on fix/upgrade-rails-5.0.0 into d3a2ab2c9c19b696ddd0e7ca1ad729692dae2fac on master.


Firmware Error Encountered: I/O Error

Detailed error:
ERROR: SNP_SET_EXT_CONFIG ioctl(2) failed
because: Firmware Error Encountered: I/O Error
because: I/O Error
because: Invalid argument (os error 22)
Error: SNP_SET_EXT_CONFIG ioctl(2) failed

Caused by:
    0: Firmware Error Encountered: I/O Error
    1: I/O Error
    2: Invalid argument (os error 22)

Does this mean that I use wrong cert format? Now I use pem for ark and ask, der for vcek.

@shuk777 The certificates should be in raw bytes.

https://github.com/tylerfanelli/snphost/blob/cfc259ee4d6135237b60d93c0496df7c771fe336/src/certs/mod.rs#L74
Seems that this line should be ((size / 0x1000) + 1) * 0x1000

@shuk777 Yes, you're right. Will fix.


Tests: Test on all Node.js releases supported by upstream

The browserstack job is run only on Node.js 6. Upstream support for Node.js 5
ends in about a month so I didn't add it.

This is a better version of #887.

Seems good to me. Do we want to move Browserstack out of the "allowed failures" category?

BrowserStack still fails from time to time (see this recent run), I guess that's why failures in it are allowed.
I didn't change this setting, though, I just added more Node versions to the ci tests so maybe that's a separate discussion. :)

BrowserStack still fails from time to time

Yeah, that's why I added the allowed failures to begin with. Let's keep it as is for now then.


Methods may contain outdated code

I am not sure, if the use of "top" and "getUserID()" is still recommended.
var inn = new top.Innovator();
var aliasId = aras.getUserID();

Latest version use correct code style.


FIX-#5509: default to pandas for read_parquet if any additional kwargs are passed to the engine

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5509
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

Thanks @mvashishtha!


Replace actions/create-release

https://github.com/reviewdog/action-detect-secrets/blob/4673e16bbcc26c596f3eeb08be79ac6c2a5d7a9e/.github/workflows/release.yml#L43
actions/create-release used above is unmaintained and uses the deprecated Node.js 12.
Therefore, it should be replaced with other Actions.
[FYI]

Alternate Actions list: https://github.com/actions/create-release
Error that Node.js 12 is deprecated: https://github.com/reviewdog/action-detect-secrets/actions/runs/5205495227

closed #45


TimeSeries Create function always creates the TS as "uncompressed" when specifying true or false to the function argument

NRedisStack Version: 0.12.0
Description:
Expected:
I'm calling the TS create function with the uncompressed argument set to false, expecting that it should create the TS with compression enabled.
Actual:
The TS is still created as uncompressed.
Notes:
In debugging with redis MONITOR I can see that specifying true or false still issues a TS.CREATE with the UNCOMPRESSED parameter set.
It looks like the problem is with this function in TimeSeriesParamsBuilder where it is setting the UNCOMPRESSED option entirely based on the presence of the arg regardless of it's value.
https://github.com/redis/NRedisStack/blob/master/src/NRedisStack/TimeSeries/TimeSeriesParamsBuilder.cs#L109
Workaround:
Set the uncompressed argument to null

Hello @Auttcast
Thanks for the bug report. We will address it soon.


test: integration test

Create integration test of full flow to avoid manual testing.
An integration test should execute succesfully before allowing merge to main

Closed because it doesn't work with the current version of the project. We can open another issue later.


Task: Re-Evaluate the requirements tool

Task (User Story)
Doorstop is from various sides not considered the ideal tool.

Hardly maintained
Limited concerning link relations
Limited concerning export formats (no reqif)

In the #57516 the following alternatives were named:

StrictDoc
Sphinx-needs

The most suitable open source requirements management tool for Zephyr OS shall be evaluated.

Requirements torwards the RQM tool shall be collected
The tools shall be bench-marked against the requirements
Describe or possibly implement prove-of-concepts for each

Acceptance Criteria

[ ] Tool requirements complete and prioritized (must, must not (weight: 5), should, should not (weight: 3), may (weight: 1))
[ ] Candidate tool's requirement fulfillment for each requirement [none: 0 - fully: 5]
[ ] Use/value analysis transparently summarizing weights and fulfillment in some table form
[ ] Descriptive of implemented prove-of-concepts to give a good confidence that tool and processes work

Here's a start on user needs for an RM solution.
User Need:
As a Chip Vendor,
I need to capture and trace requirements and design decisions to Zephyr from my commercially licensed HAL in a non-public repository,
so that I can generate additional revenue through licensed value-added functionality.
User Need:
As a downstream user with access to relevant Zephyr release certification artifacts,
I need to capture and trace requirements in a Zephyr release to my bootloader requirements without modifying the Zephyr or MCUboot repositories,
so that I can re-submit a subset of the certification artifacts to reduce the time and cost of certifying the image on my device.
User Need:
As a downstream user following the T2 workspace topology with my manifest-module's build interface files located in the repository's zephyr/ subdirectory,
I need the Zephyr-associated requirements to also be beneath the repository's zephyr/ subdirectory,
so that I can avoid conflicts with pre-existing non-zephyr content located at the repository top level.
User Need:
As a downstream user following the T3 topology with my module assigned a fixed name in zephyr/module.yml,
I need the requirement UIDs to be independent of the pathname of my module repository,
so that I can continue to have the file organization freedom the Zephyr build system currently supports.
User Need:
As a downstream user of both Zephyr and a Zephyr fork (e.g., NCS),
I need an individual requirement UID to have consistent meaning across all forks,
so that I can avoid hard-to-detect errors in requirements tracing.
User Need:
As a manufacturer,
I want a requirements management solution from Zephyr Project that can scale up to cover my entire system (including cloud services) and the multiple levels of regulations my product must meet,
so that I do not have to split my requirements and verification of them across multiple tools.
User Need:
As a manufacturer,
I need to filter the requirements and links based on my product feature set (product configuration),
so that I can evaluate and track only those requirements that apply to my product variant.
User Need:
As a downstream module provider,
I need to capture my module requirements in a form and structure that aligns with the upstream modules and integrates with end user content consistent with upstream modules,
so that fewer barriers exist to others using my module.

The focus on downstream user needs resonates very much with me. Zephyr has no application on its own and will always be treated as some component in whatever safety-critical device you may envision. Treating your product development as a downstream activity also makes a ton of sense, in fact the entire tooling of zephyr is pushing you into this direction. And I mean this in the most positive sense possible. Zephyr is more than a RTOS kernel under the kernel folder. It also provides many integration points (for silicon vendors, chip manufacturers, middleware providers etc.) It is opionated to the greatest extent possible (again in the most positive sense) and if it starts to capture requirements or (much more interesting for me) design specifications it should be done in a way that downstream projects could build upon the tooling by using extension points than offered as we can extend CMake/KConfig/DeviceTree/West modules today.
Nordic provides a nice example with how they build the docs for their connectSDK  on how to even extend things not yet meant to be extended.

if it starts to capture ... design specifications

When, not if. :-) As downstream users integrate multiple subsystems into a device they must not violate the design assumptions of any subsystem. The cleanest way to communicate this to product integrators and subsystem maintainers is through design specifications.

User Need:
As a secure IoT device manufacturer,
I need to clearly identify which requirements apply to each of my immutable images,
so that I can identify security risks that may require device HW replacement to mitigate and follow the appropriate SDLC.
User Need:
As a secure IoT device manufacturer,
I need to clearly identify which requirements apply to each of my mutable images,
so I can identify security risks that may estimate the risk exposure on units that are not allowed to be automatically updated.

Here's a start on user needs for an RM solution.
User Need: As a Chip Vendor, I need to capture and trace requirements and design decisions to Zephyr from my commercially licensed HAL in a non-public repository, so that I can generate additional revenue through licensed value-added functionality.
User Need: As a downstream user with access to relevant Zephyr release certification artifacts, I need to capture and trace requirements in a Zephyr release to my bootloader requirements without modifying the Zephyr or MCUboot repositories, so that I can re-submit a subset of the certification artifacts to reduce the time and cost of certifying the image on my device.
User Need: As a downstream user following the T2 workspace topology with my manifest-module's build interface files located in the repository's zephyr/ subdirectory, I need the Zephyr-associated requirements to also be beneath the repository's zephyr/ subdirectory, so that I can avoid conflicts with pre-existing non-zephyr content located at the repository top level.
User Need: As a downstream user following the T3 topology with my module assigned a fixed name in zephyr/module.yml, I need the requirement UIDs to be independent of the pathname of my module repository, so that I can continue to have the file organization freedom the Zephyr build system currently supports.
User Need: As a downstream user of both Zephyr and a Zephyr fork (e.g., NCS), I need an individual requirement UID to have consistent meaning across all forks, so that I can avoid hard-to-detect errors in requirements tracing.
User Need: As a manufacturer, I want a requirements management solution from Zephyr Project that can scale up to cover my entire system (including cloud services) and the multiple levels of regulations my product must meet, so that I do not have to split my requirements and verification of them across multiple tools.
User Need: As a manufacturer, I need to filter the requirements and links based on my product feature set (product configuration), so that I can evaluate and track only those requirements that apply to my product variant.
User Need: As a downstream module provider, I need to capture my module requirements in a form and structure that aligns with the upstream modules and integrates with end user content consistent with upstream modules, so that fewer barriers exist to others using my module.

I am lost here and not sure why any of this applies to selecting a requirement management tool for Zephyr. As a chip vendor, manufacturer, downstream user you can use whatever tool you like and everyone will have different requirements for tooling. None of that is relevant to what we are trying to do here. We are looking for a tool to manage our own requirements for the zephyr project, full stop. Nothing more. This is not about providing tools for downstream users to manage their own requirements. Maybe the only relevant item we need to make sure a tool provides, hence a requirement on the tool, is to be able to export zephyr requirements  in some standard format that can be imported into other tools, thats it. Everything else should be about how such tool integrates with zephyr workflows and how Zephyr's own requirements are managed and maintained.

how Zephyr's own requirements are managed and maintained.

Zephyr's own requirements will include constraints on workflows, SDLC, and the standards it has committed to meeting (e.g., IEC 62443). For Zephyr to be desirable, many of the requirements on Zephyr should be based on realistic user needs and usage models. (See @tobiaskaestner comment above.) Zephyr is not very useful in isolation.

As a chip vendor, manufacturer, downstream user you can use whatever tool you like

Agreed. Many will be very interested in using Zephyr's OSS solution for managing their own requirements.  Ignoring that now is inconsiderate of Zephyr's target userbase and contrary to the ZP vision statement.

Maybe the only relevant item we need to make sure a tool provides, hence a requirement on the tool, is to be able to export zephyr requirements in some standard format that can be imported into other tools,

If that were the only requirement on Zephyr's tool then it wouldn't be useful for producing safety- and security- certification inputs.
If you prefer, we can use example-application or mcuboot module maintainer for downstream end user, and hal_<whomever> maintainer for chip vendor (since they may distribute HAL fixes before they get merged into zephyrproject-rtos mainlines). The needs are still the same.

how Zephyr's own requirements are managed and maintained.

Zephyr's own requirements will include constraints on workflows, SDLC, and the standards it has committed to meeting (e.g., IEC 62443). For Zephyr to be desirable, many of the requirements on Zephyr should be based on realistic user needs and usage models. (See @tobiaskaestner comment above.) Zephyr is not very useful in isolation.

This is not about doing things isolation. You are mixing requirements with a requirement management tool. this issue is about selecting a tool, not about setting requirements. Requirements can be managed in different ways, a text file, a csv file, a database, GH issues, Jira, some commercial tool, etc etc and any of those is acceptable for whatever standard you target.
Right now, we are trying to identify a tool that is to be used to manage Zephyr's own requirements. This is not about finding a tool that fits needs the rest of the world. This is what the issue about, nothing more. If you want to contribute to this, start looking at possible options and how they fit the needs of the project, not your needs as a downstream user.

As a chip vendor, manufacturer, downstream user you can use whatever tool you like

Agreed. Many will be very interested in using Zephyr's OSS solution for managing their own requirements. Ignoring that now is inconsiderate of Zephyr's target userbase and contrary to the ZP vision statement.

There is nothing here that is contrary to any vision. We are looking for a tool, we have options, we will pick one, just like we did in the past, as a project. Thats why we are having this discussion, some think whatever was selected is not good enough, we are reconsidering that. This is very considerate of the userbase.

Maybe the only relevant item we need to make sure a tool provides, hence a requirement on the tool, is to be able to export zephyr requirements in some standard format that can be imported into other tools,

If that were the only requirement on Zephyr's tool then it wouldn't be useful for producing safety- and security- certification inputs.

Fully disagree. Standards do not have any requirements on the tools. That requirement of being able to import/export is to satisify  interchangability of information in a standard format. We do not need more than that.
And, I noted this being the only relevant item in the context of reuse and end-users. I did not say this is the only requirements on a tool.

If you prefer, we can use example-application or mcuboot module maintainer for downstream end user, and hal_<whomever> maintainer for chip vendor (since they may distribute HAL fixes before they get merged into zephyrproject-rtos mainlines). The needs are still the same.

No, I do not prefer that. I do not think any of that has any relevance here.

@gregshue What Zephyr OS safety concerns I look at it as if I buy an safe RTOS, e.g. Wittensteins SafeRTOS or MS Azure RTOS ThreadX, ask for / buy from my favorite MCU vendor a safety certified HAL and start building a Safety application. If I need a bootloader, the I will have to develop that similar to my application either I use the same certified RTOS or I do that bare-metal with the certified HAL. And I will have to do the same puzzle with the requirements management.
What you are asking for or would like to build is, as I understand it, a requirements management framework around or to the existing ecosystem, that allows requirements management and traceability to the full extent, from HAL (module), to RTOS (zephyr repo), middleware (other modules) to user application(s).
It would be cool to get that - one day.
At the moment we are struggling to get the core tasks done and I therefore feel we need to focus on the basics. Get the Zephyr OS safety scope described with requirements and achieve traceability there. If you need traceability to those requirements from "outside" (I would not even know If you get the full requirements set from Wittenstein for SafeRTOS, and if so, the as reqif or pdf), you will need to link from your tool and your higher level requirements to those of Zephyr OS or, as Anas mentioned, you need requirements export/import facilities and formats to transfer at least the layer of your "greybox" you want to link to.
For the moment, I feel, you are asking for too much. I doubt that we can manage that right now.

So I will need some guidance on what kinds of things are in/out of the safety scope:
The boundaries may need to contain code inside/outside trusted execution environments, which may be one of the decomposition layers.  Does it need to create an independent executable with its own certification criteria?
Could any module content be pulled into the safety-critical code (including any headers with macros or inline implementations)? Carefully consider HALs, tfm, picolibc, crypto content.  Any of these will bring up the question of cross-repo linking. Is this currently an issue?  If not and we choose to ignore it, how will we prevent it from becoming an issue?
Requirements for secure code will need to use the same tool and probably exist in the same dataset. How does the safety-critical code boundary align with the boundary needed for secure code? Do we need to identify a requirement as being relevant for safety-critical? secure? secure-trusted-environment? secure-immutable?
Are we looking for a tool that is ready to handle the needs as the safety- and security- scopes grow over time?

So I will need some guidance on what kinds of things are in/out of the safety scope:
The boundaries may need to contain code inside/outside trusted execution environments, which may be one of the decomposition layers. Does it need to create an independent executable with its own certification criteria?
Could any module content be pulled into the safety-critical code (including any headers with macros or inline implementations)? Carefully consider HALs, tfm, picolibc, crypto content. Any of these will bring up the question of cross-repo linking. Is this currently an issue? If not and we choose to ignore it, how will we prevent it from becoming an issue?
Requirements for secure code will need to use the same tool and probably exist in the same dataset. How does the safety-critical code boundary align with the boundary needed for secure code? Do we need to identify a requirement as being relevant for safety-critical? secure? secure-trusted-environment? secure-immutable?
Are we looking for a tool that is ready to handle the needs as the safety- and security- scopes grow over time?

once again, I am not sure why all of this is relevant to selecting a requirement management tool.  Would be progress if we could see list of available tools, how they differ, what they offer, maybe in form of a table so we can make a decision and STOP referring to modules and HALS and security.

What safety claims can you make that don't depend on a secured implementation?

Sphinx-needs specification sandbox for Zepyhr
https://github.com/romkell/zephyr/blob/spec_with_sphinx_needs
https://github.com/romkell/zephyr/blob/spec_with_sphinx_needs/specs
https://github.com/romkell/zephyr/blob/spec_with_sphinx_needs/specs/README.md
I couldn't get the vscode plugin to work.
@danwos would you mind having a look at the sandbox and at the Requirement Tool requirements me not stating anything wrong concerning sphinx-needs? I would also appreciate some support on the vscode plugin. Does not show anything in the window so far.

@romkell: I wrote some comments in the Sphinx-Needs column.
I hope this helps a little bit and I wrote 1-2 comments about in what kind of projects Sphinx-Needs is already used.
Currently, I have really zero time to take a deep look into the sandbox (projects needs to be finished, vacation time starts, ..).  Sorry, will try to come back to it in 3-4 weeks.
From the requirement management perspective, the written requirements are quite good.
Here are some additional points (but I may have missed them):

Analysis: Show filtered results in tables, flows, piecharts and Co.
Automation: Calculate values. For instance, the status of a sys-req is based on the status of linked comp-reqs.
Templating: Add req-specific analysis under each req. E.g. show the dependency tree
Layout: Customize what data to show in the HTML representation
Styles: Set colors based on status or other data

You may also think about how separated the requirement definition shall be from the other documentation.
Does it make sense to have normal rst/md-text between reqs, to maybe explain something which shall not be part of an official req?
Or can reqs be part of a SW-Architecture page?
Can they be linked/combined with other Documentation features, like Test-Results or imported Data from systems like JIRA, github Issues, ...
So the core of this question is: Are there benefits for you that Sphinx-Needs extends Sphinx and feels therefore like just writing Sphinx docs, no extra files or format?

@stanislaw Since I directed Daniel Woste, the main developer of sphinx-needs to the Projects Requirement Tool requirements I would like to give you the same opportunity to comment on the requirement fulfillment of StrictDoc (entries done by Roberto Bagnara).
I feel it would be helpful if the main developer can comment on it.

Decision taken in Safety Committee in favor of StrictDoc (see Requirement Tool requirements
Decision communicated to Safety WG, no objections received form WG
Safety Committee decision to be taken to TSC for approval


Can not reproduce BraTS 2020 results.

Hi, thanks for sharing the code base. I try to reproduce the results on BraTS 2020 dataset, but the results I got are much worse than the paper. Here are the details:
For model training:
wt is 0.8498, tc is 0.4873, et is 0.4150, mean_dice is 0.5840
The tensorboard files are:

The final model files are:

My settings are default settings:
env = "DDP"
max_epoch = 300
batch_size = 2
num_gpus = 4
GPU type: A100
Then I use the best model (best_model_0.5975.pt) to do evaluation on the test set, and I got:

My python environment is:
Python 3.8.10
monai 1.1.0
numpy 1.22.2
SimpleITK 2.2.1
torch 1.13.0a0+936e930
The most strange thing is the segmentation performance of TC and ET is quite bad. Do you have any idea why the performance is so weird, and could you give me some advice on model training? BTW, could you please share the conda env file and your model weights for BraTS 2020 dataset? If you can create and share a docker image I think that could be perfect! Thanks.

Also I train and test the code on BTCV dataset, the results are quite similar with the paper. Here are the details:
The tensor board files are:

The final model files are:

The results on test set are (evaluated by the best model (best_model_0.7873.pt)):

Please check your BraTS2020 data, and also you can plot some input data in the training phase (in the training_step function) to confirm that the training data is right.

first of all, thank you to the authors for your excellent work ! and I might reproduce the results in the paper.my results are as follows,even better:

Thank you for your experiments!

first of all, thank you to the authors for your excellent work ! and I might reproduce the results in the paper.my results are as follows,even better:

Hi, thanks for sharing your results @Devil-Ideal . Could you please share your environment settings? for example, your python version and torch version. Also, did you train the model on 4xV100 GPUs and keep hyper-parametes as defaults? Here is my test result:

Hi Devil @Devil-Ideal , many thanks for your quick reply, I will try the dataset that you download from kaggle to see whether I can achieve the results.

Hi Devil @Devil-Ideal , many thanks for your quick reply, I will try the dataset that you download from kaggle to see whether I can achieve the results.

Hello, have you reproduced the results of the successful paper?

Turning to the kaggle version seems useless for me...

Me too, did you finally solve this problem？
------------------ 原始邮件 ------------------
发件人:                                                                                "ge-xing/Diff-UNet"                                                                                @.>;
发送时间: 2023年11月3日(星期五) 上午10:49
@.>;
<EMAIL_ADDRESS>主题: Re: [ge-xing/Diff-UNet] Can not reproduce BraTS 2020 results. (Issue #21)
Turning to the kaggle version seems useless for me...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

I am encountering the same problem with reproducing the benchmark. sofar I haven't changed to the kaggle dataversion
I too have results in the same range:
wt is 0.86446, tc is 0.49546, et is 0.45163 , mean_dice is 0.603 for the best performing epoch during training.
Did somethings resolve

I am encountering the same problem with reproducing the benchmark. sofar I haven't changed to the kaggle dataversion I too have results in the same range: wt is 0.86446, tc is 0.49546, et is 0.45163 , mean_dice is 0.603 for the best performing epoch during training. Did somethings resolve the issue for you guys?
I'm not training on 4 v100's but I doubt this is the problem Will run the samething on the kaggle dataset

How many GPUs did you use and what was the batch size? In fact, in the code, batch size refers to the batch size on each GPU. Therefore, it is best to be the same as the original paper, the total batch size is 2*4

I only trained on 1 GPU sofar, I actually haven't change the batch size..will rerun it with batchsize set to 8. Thank you for the suggestion. Regarding the epochs, training happens with 300 epochs right?

Thank you for the suggestion. I only trained on 1 GPU sofar, I actually haven't change the batch size..will rerun it with batchsize set to 2 since I only have 1GPU available would you consider this approach feasible?
Regarding the epochs, training happens with 300 epochs right?

yep，300 epochs are enough. And if you don't have enough GPUs, I think even total batch size == 4 or 6, the performence will be much better

I double checked and saw that I've already trained with batchsize = 2 & one GPU. Seems a bit odd that I don't get the same results.

I double checked and saw that I've already trained with batchsize = 2 & one GPU. Seems a bit odd that I don't get the same results.

if the total batchsize = 2, it's normal, since the original setting is equal 8, so just ues bigger batchsize (e.g 4 GPUs with batchsize = 2)

Increasing the Batchsize wouldn't improve the results... I was wondering if you have a requirements.txt file or something to see what kind of configurations for python, pytorch etc you are using.

Increasing the Batchsize wouldn't improve the results... I was wondering if you have a requirements.txt file or something to see what kind of configurations for python, pytorch etc you are using.

It's weired, since I have run it several times, and the results are not bad. Here is my configurations:
absl-py==2.0.0
blobfile==2.1.0
certifi==2023.7.22
charset-normalizer==3.3.1
filelock==3.13.0
grpcio==1.59.0
idna==3.4
importlib-metadata==6.8.0
joblib==1.3.2
lxml==4.9.3
Markdown==3.5
MarkupSafe==2.1.3
MedPy==0.4.0
monai==1.3.0
mpi4py
numpy==1.23.4
Pillow==10.1.0
protobuf==3.20.0
pycryptodomex==3.19.0
PyYAML==6.0.1
requests==2.31.0
scikit-learn==1.3.2
scipy==1.11.3
SimpleITK==2.3.0
six==1.16.0
tensorboard==1.15.0
threadpoolctl==3.2.0
torch==1.11.0+cu113
torchaudio==0.11.0+cu113
torchvision==0.12.0+cu113
tqdm==4.66.1
typing_extensions==4.8.0
urllib3==2.0.7
Werkzeug==3.0.1
zipp==3.17.0

I use kaggle's BraTS2020 data set, because the official did not reply, and converted the dependency library version for many times, but the effect is the same as the host, I would like to ask if the friend with better training effect is the official data set used.Thanks.

您好，感谢您分享代码库。我尝试在 BraTS 2020 数据集上重现结果，但得到的结果比论文差很多。详细信息如下：
对于模型训练： wt为0.8498，tc为0.4873，et为0.4150，mean_dice为0.5840
张量板文件是：
最终的模型文件为：
我的设置是默认设置： env = "DDP" max_epoch = 300 batch_size = 2 num_gpus = 4 GPU 类型：A100
然后我使用最佳模型（best_model_0.5975.pt）对测试集进行评估，得到：
我的python环境是： Python 3.8.10 monai 1.1.0 numpy 1.22.2 SimpleITK 2.2.1 torch 1.13.0a0+936e930
最奇怪的是TC和ET的分割性能相当糟糕。您知道为什么性能如此奇怪吗？您能给我一些关于模型训练的建议吗？顺便说一句，您能否分享一下 BraTS 2020 数据集的 conda env 文件和模型权重？如果您可以创建并共享 docker 镜像，我认为那就完美了！谢谢。

18340097191<EMAIL_ADDRESS>, you can add my wechat or email me to further discuss these problems. Recently, I also will open-source the v2 version of Diff-UNet. Welcome to try it.

我用的是kaggle的BraTS2020数据集，因为官方没有回复，并且转换了很多次依赖库版本，但是效果和宿主一样，请问训练效果比较好的朋友是不是官方数据设置已使用。谢谢。

您好，感谢您分享代码库。我尝试在 BraTS 2020 数据集上删除结果，但得到的结果比论文差很多。详细信息如下：
对于模型训练：wt为0.8498，tc为0.4873，et为0.4150，mean_dice为0.5840
张量板文件为：
最终的模型文件为：
我的设置是默认设置： env = "DDP" max_epoch = 300 batch_size = 2 num_gpus = 4 GPU 类型：A100
然后我使用最佳模型（best_model_0.5975.pt）对测试集进行评估，得到：
我的python环境是： Python 3.8.10 monai 1.1.0 numpy 1.22.2 SimpleITK 2.2.1 torch 1.13.0a0+936e930
最奇怪的是 TC 和 ET 的分割性能相当惊人。您知道为什么性能如此奇怪吗？您能给我一些关于模型训练的建议吗？顺便说一句，您能否分享一下 BraTS 2020 数据集的 conda env 文件和模型权重？如果你可以创建并共享docker镜像，我想那就完美了！谢谢。

请问您解决了吗

Recently, I have also reproduce my code on brats2023 dataset, this is the training process:

I use 4 4090GPUs to run and batch_size is set as 2.
If you still have questions about it, please contact with me by email<EMAIL_ADDRESS>


update "com.typesafe" % "config" dependency

(extracted from #4000)

The problem is that SSL Config uses 1.2.0 - https://github.com/lightbend/ssl-config/blob/master/project/Dependencies.scala
/cc @kanischev

is this not help wanted?

The bar for "help wanted" should be that it's immediately workable.

is this for you not immediately workable because the first change required is in ssl config?

does typesafe-config follow semver? could we not depend on version 1.3.1 in sbt with or without ssl-config updating?

is this for you not immediately workable because the first change required is in ssl config?

Basically. I think the realistic compromise for us (or a potential contributor) might be to shade SSL Config in Gigahorse so it doesn't conflict with the latest Lightbend Config.

ah right, yeah, because of #2796 depending on typesafe-config 1.3.1 in sbt is still working around the problem.
we might want to actually deal with #2796..

(Blocked on updating of LM.  But perhaps "Blocked on Upstream" is used to mean outside of the sbt library circle.)


Common.Logging.WinRT depends on Common.Logging.Core, but core does not provide wpa81 target

The Common.Logging.Core nuspec needs to be updated to include support for wpa81.  I cannot install the Common.Logging.WinRT nuget into a Window Phone 8.1 project because the dependency on Common.Logging.Core fails.

I'm traveling and won't be able to look into this until early next week.

Any news on this? I still get the same error.

Sorry about the delay; I'll look into resolving this for you first thing tomorrow morning.  At first glance it sounds like (mostly?) just a package metadata oversight; AFAIK we're not doing anything that would preclude support for the WP8.1 TFM.
-----Original Message-----
From: "Mike Gottlieb"<EMAIL_ADDRESS>Sent: 5/11/2016 7:22 PM
To: "net-commons/common-logging"<EMAIL_ADDRESS>Cc: "Steve Bohlen"<EMAIL_ADDRESS>"Comment"<EMAIL_ADDRESS>Subject: Re: [net-commons/common-logging] Common.Logging.WinRT depends onCommon.Logging.Core, but core does not provide wpa81 target (#103)
Any news on this? I still get the same error.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

Agreed. I think it is just a nuspec issue.
On Wed, May 11, 2016 at 8:08 PM Steve Bohlen<EMAIL_ADDRESS>wrote:

Sorry about the delay; I'll look into resolving this for you first thing
tomorrow morning. At first glance it sounds like (mostly?) just a package
metadata oversight; AFAIK we're not doing anything that would preclude
support for the WP8.1 TFM.
-----Original Message-----
From: "Mike Gottlieb"<EMAIL_ADDRESS>Sent: 5/11/2016 7:22 PM
To: "net-commons/common-logging"<EMAIL_ADDRESS>Cc: "Steve Bohlen"<EMAIL_ADDRESS>"Comment" <
<EMAIL_ADDRESS>Subject: Re: [net-commons/common-logging] Common.Logging.WinRT depends
onCommon.Logging.Core, but core does not provide wpa81 target (#103)
Any news on this? I still get the same error.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/net-commons/common-logging/issues/103#issuecomment-218625796

Actually, as I look into this, it might be a bit more complicated than just correcting NuSpec metadata.  In Visual Studio (2015, Update 2) I'm precluded from adding a reference of Common.Logging.Core into Common.Logging.WinRT with a "the portable targets are not the same or compatible" error.
I'd be interested in any input from anyone as to why this is the case.  As far as I can tell, the PCL targets that are declared in Common.Logging.WinRT are a subset of the targets declared in Common.Logging.Core as follows:
Common.Logging.Core targets:

.NET Framework 4
Silverlight 5
Windows 8
Windows Phone 8.1
Windows Phone Silverlight 8

Common.Logging.WinRT targets:

.NET Framework 4.5
Windows 8
Windows Phone 8.1

The only (apparent) mismatch I can see here would be that Common.Logging.Core targets .NET 4 whereas Common.Logging.WinRT targets .NET 4.5.  But I always understood .NET 4.5 to be a full proper superset of .NET 4 (i.e., there isn't anything in .NET 4 that's not also in .NET 4.5, meaning it should be possible for a .NET 4.5 assembly to reference a .NET 4 assembly as I'm attempting here).  However the tooling seems to vehemently disagree with my understanding :-/
Obviously at some point I was able to add the reference successfully (else how would the entry be in the .csproj file in the first place?), but now the solution explorer is displaying a "yellow triangle" warning icon on the reference and the tooling refuses to let me re-add the reference if I remove it and attempt to re-add it back.
This suggests that while I might be able to correct the initially-reported issue by tweaking the NuSpec metadata to add a declaration of support for WPA8.1, this may only uncover the next error: a runtime failure when the consuming app attempts to load the Common.Logging.Core assembly.
I'm continuing to try to puzzle this one out, but if anyone has any insight into this that they can offer, I'd certainly appreciate it to speed me along to a resolution...at first glance this has me a bit baffled...

Circling back on this to share an update....
I've performed further testing and exploration into this and I am now 99% convinced that this is a tooling bug in the add-reference tool in VS 2015.  I'm currently running VS 2015 Update 2 and unfortunately I don't have a system with VS 2015 pre-Update 2 to help determine exactly when this behavior changed.  However I was able to find a system with VS 2013 installed and test this very same cross-PCL-reference scenario -- the result is that this same set of PCL targets referencing between each other in VS 2013 seems entirely acceptable/proper (as one would expect).
I'm seeking to get 100% confirmation that this isn't an intentional change in the rules about what PCLs are permitted to reference each other, but assuming that I can achieve certainty on this point I'd expect to be able to correct the NuSpec metadata appropriately and push an updated package shortly.
Thanks for everyone's patience as we puzzle this one out ...

@sbohlen Thanks for following up on this. I'm building an app using Xamarin for iOS, Android, and Windows Phone 8.1 specifically (yeah I know, but its not my call). It is incredible how little support is available when you add Windows Phone 8.1 into the mix. Half of Xamarin's own libraries barely work. I really appreciate you looking into this.

FWIW I've now managed to (finally) confirm that https://github.com/net-commons/common-logging/issues/103#issuecomment-218867074 is indeed a bug in VS 2015.  It first appeared in Update 1 and is still present in Update 2 and is related to the introduction of support for .NET Core that was added to the PCL-compatibility-checker that validates attempts to cross-reference assemblies during the add-reference experience.
Now that I know what's going on there, I can return to fix this specific packaging/metadata issue.  I don't have time to see to it today, but its on my TODO list for first thing tomorrow a.m. so look for an updated NuGet package that addresses this issue in < 24 hours.
Thanks for your patience on this, everyone!

This is fixed in https://github.com/net-commons/common-logging/commit/6ab4a9835f0ccad1cd8c81c410a0323b5e3e71fe and has been pushed to NuGet as 3.3.2-Alpha1 and will be included in the official release of 3.3.2 (and forward).  I'm going to close this issue for now -- if by chance this fails to properly fix the issue, please return here and re-open this issue accordingly.
Thanks again for you patience on this!

Awesome!


Revert "Game server api"

Reverts space-wizards/space-station-14#24015
This was, still, not suitable for merge.

my life is ruined /s


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in 9c69600.


Attempt to fix #61 by adding logs:tail task

namespace logs
task :logs => 'logs:default' (no tail)
this could by DRYer, I suppose, but I am a Rake newb

@kmayer Any feedback on this PR?

+1

Closed with 6b30b


[Doc] Improve codgen

Introduce an expand/retract button for code example.
This is useful for long examples as we have on the Toolbars page.
I have also rename some page to stay coherent.

@subjectix Could you have a look?

@oliviertassinari Expanding is done instantly, It scares me :scream: Can it be animated?

Can it be animated?

Would be better indeed, let me fix this.

@oliviertassinari Thanks a lot :+1:  :+1:

@subjectix Added https://github.com/callemall/material-ui/pull/2438/files#diff-97439f8083792f35079c7682f86df377R18

Why? It's not fully expanded

Alright, I have increased the max height from 1000px to 2000px.

@oliviertassinari Awesome :+1: :+1: Thanks :tada: :tada:


Reorganize our code

Move include to b9/
Move external stuff to third_party (googletest, omr)
Move all test programs to test/
Rename b9docker to docker
Misc cleanup

@xliang6 @arianneb: Take a look at the directory layout here. Let me know if there is anything else we want to reorg.

We have the have a b9 directory under b9/include/b9 so that we can reference headers with #include "b9/core.hpp".  If the old layout and this new layout are not working for you, we could just put the header files alongside the source files.

I think the new include layout is fine after a quick chat with Rob. Thanks.

Rebased and fixed merge issue. Updated OMR to latest.


Define recur depth up to next power of 2.

Having the recur depth support a power of two will no doubt have
tremendous utility in the future.

1024 should be enough for everyone. :+1


Update comments indention of 02-Input-Tasks.md

comments indention should be the same as surrounding code

Thanks!


A strange error

sorry, i have solved it! Compared with Casadi, it is indeed much faster.

Hi, if possible, could you share how you fixed it? That'd be valuable for future references.
Many thanks.

Hi, @xkhainguyen !I just convert nonlinear relationships into linear relationships.But, I have not yet implemented nonlinearity in tinympc.


Directions are not obvious.

Challenge Change Text Inside an Element Using jQuery has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
Directions are:
Emphasize the text in your target4 button by adding HTML tags.
Correct answer is to put   tags, otherwise checking system fails. If user enters f.e.   it won't work. Directions should be like:
Emphasize the text in your target4 button by adding  HTML tags.
My code:

jQuery Playground

#left-well

        <button class="btn btn-default target" id="target1">#target1</button>
        <button class="btn btn-default target" id="target2">#target2</button>
        <button class="btn btn-default target" id="target3">#target3</button>

#right-well

        <button class="btn btn-default target" id="target4">#target4</button>
        <button class="btn btn-default target" id="target5">#target5</button>
        <button class="btn btn-default target" id="target6">#target6</button>

@wjaron thanks for the feedback. I can see how the directions are now self-evident, but the directions around it make it clear

Here's how you would rewrite and emphasize the text of our heading:
$("h3").html("jQuery Playground");

I think we try to strike a balance between giving information and require critical thinking in solving the challenges. I can see an argument for changing this but I can also argue the other way. But I think for the earlier challenges, we can give them more direction.

I think the directions are clear enough. Any clearer and as @erictleung said, they would require no thought.

I agree with @atjonathan and @erictleung.
Thanks @wjaron for initiating this discussion, and for continuing to look out for potentially confusing wording in our challenges.


Enable forced SSL and forced user sign in

Enabled forced user sign in and sign up whitelist. Forced SSL is best enabled on a case by case basis.


Hyperlink DOIs against preferred resolver

Hello :-)
The DOI foundation recommends this new resolver. Yes, a bit ironic that they would change the URL of their service, but it's now encrypted. Because the old links with the dx subdomain continue to work, there is no urgent need to do anything.
However, I'd hereby like to suggest to follow the new recommendation and update all static DOI links.
Cheers!
PS: Regarding the all data/software BibTeX entries should be of the @misc type, https://github.com/zenodo/zenodo/issues/1428#issuecomment-398781531 might be of interest.

I'm happy to accept this as I've been negligent to track all these down (and yes, I also found the URL change to be o_O)

You're welcome, and thanks for merging :-)


Automated cherry pick of #4996: azure的主机监控信息的获取

Cherry pick of #4996 on release/3.0.
#4996: azure的主机监控信息的获取

/cc @swordqiu
/cc @yousong
/cc @ioito

/area region

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/3.0@dc6eab6). Click here to learn what that means.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             release/3.0   #4998   +/-   ##
=============================================
  Coverage               ?    6.9%
=============================================
  Files                  ?     532
  Lines                  ?   90467
  Branches               ?       0
=============================================
  Hits                   ?    6244
  Misses                 ?   83702
  Partials               ?     521

Flag
Coverage Δ

#aFlag
6.9% <ø> (?)

Continue to review full report at Codecov.

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

/lgtm

/approve


config module.generator.emit is no longer available

Bug report

What is the current behavior?
It seems that in latest version (v5.50) the emit of global options for all generators' (module.generator.emit) is no longer available?
I tried changing my config to using config for seperate rules which worked fine.
I checked recent change logs and found nothing about this change. I assume it is a bug?

If the current behavior is a bug, please provide the steps to reproduce.
Add config module.generator.emit = false. Webpack building process should encounter error.

What is the expected behavior?
Config module.generator.emit = false should work and will not emit asset module files.

Other relevant information:
webpack version:  5.50.0
Node.js version: 14.16.0
Operating System: Windows 10 21H1
Additional tools:

The asset/inline module has no emit option. A data URI doesn't emit a file, so that's not something you can disable here.

The asset/inline module has no emit option. A data URI doesn't emit a file, so that's not something you can disable here.

My bad.
Correction: The configuration for seperate asset module in global generator options, e.g. module.generator.asset.emit module.generator['asset/resource'].emit

Correction: The configuration for seperate asset module in global generator options, e.g. module.generator.asset.emit module.generator['asset/resource'].emit

That is fine, but the error message state asset/inline, so you added the emit option to a module of type asset/inline

Answered, feel free to feedback


Added Time Distributed Softmax to allow softmax activation over 3D inputs

Allows softmax activation over tensor3 values. Given output A from this activation, sum(A[i][j][:])==1.0
Impetus: Output from RNNs is generally considered of size (nb_samples, time_steps, values). This activation allows for softmax over this tensor3, where the softmax is applied over a vector of size (values, ) which corresponds to the softmax of one sample at one time step.
Example:
model = Sequential()
model.add(SimpleRNN(2, 3, return_sequences=True))
model.add(Activation('time_distributed_softmax'))

sgd = SGD(lr=0.1, decay=1e-6, momentum=0.9, nesterov=True)
model.compile(loss='mse', optimizer='sgd')
A = model._predict(np.asarray([[[1,1],[2,2]], [[3,3], [4,4]]]))

print A
print np.sum(A[0][0][:])

Yields
[[[ 0.32846826  0.33231813  0.33921361]
  [ 0.32311559  0.33156598  0.34531844]]

 [[ 0.31882143  0.33012739  0.35105121]
  [ 0.31376582  0.32922304  0.35701114]]]
1.0

Also, additional name ideas:

Time Sensitive Softmax
Dimension Sensitive Softmax
Shape Sensitive Softmax
Softmax 3D

From Torch, they have just a single SoftMax function, which works in the same way for n-dimensional tensors, such that the sum of the last dimension, for a single subtensor, sums to 1. https://github.com/torch/nn/blob/master/doc/transfer.md
I think we should still bounce around ideas for making SoftMax perform as Torch does (Which would be the dimensionality check in the SoftMax activation, a reshape if required to 2D, application of softmax, and a reshape back if required).

Do we need a fully customizable reshape?
import numpy as np
import theano
from keras.models import Sequential
from keras.layers.core import Activation, Layer
from keras.optimizers import SGD
from keras.utils import np_utils, generic_utils
from keras.layers.recurrent import SimpleRNN
from keras.utils.generic_utils import make_tuple

class MyReshape(Layer):
    def __init__(self, dims, batchwise = True):
        self.dims = dims
        self.params = []
        self.batchwise = batchwise

    def output(self, train):
        X = self.get_input(train)
        if self.batchwise:
            nshape = make_tuple(X.shape[0], *self.dims)
        else:
            nshape = make_tuple(*self.dims)
        return theano.tensor.reshape(X, nshape)

model = Sequential()
model.add(SimpleRNN(2, 3, return_sequences=True))
model.add(MyReshape((2 * 2, 3), batchwise=False))
model.add(Activation('softmax'))
# model.add(MyReshape((2, 2, 3), batchwise=False)) # maybe this line breaks the metric of loss function.

sgd = SGD(lr=0.1, decay=1e-6, momentum=0.9, nesterov=True)
model.compile(loss='mse', optimizer='sgd')

x = np.asarray([[[1,1],[2,2]], [[3,3], [4,4]]])
A = model._predict(x).reshape(2, 2, 3) # reshape

print A
print np.sum(A[0][0][:])

[[[ 0.33217808  0.33681527  0.33100665]
  [ 0.33198774  0.33990619  0.32810607]]

 [[ 0.32982884  0.34381771  0.32635345]
  [ 0.32959331  0.34696015  0.32344653]]]
1.0

I don't know much about RNN.

The above is a little off, it shouldn't compile (3 output -> 2 * 2 input).
model = Sequential()
model.add(SimpleRNN(2, 3, return_sequences=True))
model.add(MyReshape((3 * 4, 5), batchwise=False))
model.add(Activation('softmax'))

This makes the assumption that the batch size will be a constant 4. This may break if, for example we have a training set of 14 samples, the last batch would only be of size 2. Thus the reshape would break.
The Reshape layer seems a little buggy to me - I can't really think of a model it which it would be useful, especially with the first dimension fixed, and no way to revert back and forth from, say, 2D -> 3D -> 2D (which has to happen for RNNs to be effective, or even possible). To go back and forth like that, you need to know the batch size and the input size, at a minimum, to be able to calculate the reshape intelligently and correctly.
With RNNs, you need to utilize tensor3 objects to get the job done. For example, with a batch input:
# Forward recurrent network, where outputs of recurrent layer at T1 are also inputs to the recurrent layer at T2
output = []
for sample in batch:
    previous = np.zeros((.. , ..))
    for time_step in sample:
        previous = concatenate( dot(previous, W1), dot(time_step, W2)) + b
    output.append(previous)
return output

The above double loop doesn't make sense - parallelism is key. So we can work some magic:
reshaped_input = input.reshape(timesteps, batch_size, values)
previous = np.zeros((.. , ..))
for time_step in reshaped_input:
    previous = concatenate( dot(previous, W1), dot(time_step, W2)) + b
return previous.reshape(batch_size, previous.shape[0]/batch_size, output_size
or
return previous.reshape(previous.shape[0]/batch_size, batch_size, output_size

...where the first return gives a tensor3 out, or the second gives a restacked matrix, for faster parallel processing.
The problem with the above is that it assumes that a tensor3 object is the type of the input.

oh, I see.


[azservicebus] Create a programmatically useful code for when a session is not available

Adding a new error Code (CodeTimeout) for when we get back a com.microsoft:timeout error from Service Bus. The primary use is if we are doing an AcceptNextSessionFor<Entity>() and there aren't any available sessions.
This should allow customers to figure out if there's a genuine failure or if their session-enabled queue/subscription is simply "empty".
This also improves the tests and adds in some more customer exposed examples for reading through a a queue of sessions.
Fixes #19039

/azp run go - azservicebus


Binance no longer trading during sims

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): contos 7
Zenbot version (commit ref, or version): latest
Zenbot branch: unstable
NodeJS version: v9.6.1
Python version (when using a python script): Python 2.7.5
Exact command to reproduce (include everything):
Did I make any changes to conf-sample.js?: no

Describe the problem
There appears to be some issue with backtesting Binance, i've tried 3 or 4 different coin pairs and the genetic algo never does a trade. If I switch over to GDAX I am able to backtest and return trades. Any idea whats going on?
Source code / Error logs
0 trades binance

GDAX with trades

I believe there was an issue with the Binance API around that time, do you still have a problem?

Have you tried other coin pairs? How about other strategies?  Try running it with a strategy like SAR because it will always make trades with any normal set of parameters.


chore: add more tests, hash and repr changes

I found these docs so I thought Id implement all the suggestions there.
This adds:

Tests for all comparison operators of version
Changes __repr__ to include the class names
Add __hash__ for version  with tests (showing some edge cases)
Instead of manual implementing functions for comparison, we can use the Pyo3s __richcmp__ function.

@Wackyator you are the designated reviewer :)

@wolfv looks good to me


Adding warning for ctors

Adding highlighting (warning) if script doesn't contain ctor with 0 arguments and quick fix for it. Also fixing Godot tracker and removing -PskipDotnet=true from arguments for running IDE. Adding internal mode in build.gradle.kts, resolves #42

I haven't yet commited quickfix, because it isn't ready, but the highlighting part is ready and can be inspected for problems. Also I removed 1 argument from the run command, because I think it could be commited accidently because it doesn't belong there

It looks like it will affect all classes, not only derived from the Godot.GodotObject.
I have some new infrastructure for that in https://github.com/JetBrains/godot-support/pull/126, which will get merged shortly.

I've inspected the #126, but I'm not really sure I understand the way it is done. If I have a right direction, I must inspect all IClassDeclaration node types from PSI tree and then, using constants that was added in this PR, check if they are derived from this particular class Godot.GodotObject, am I right?

Once you rebase your work on current net241, you'd be able to add in your analyser Run.
        var typeElement = element.DeclaredElement;
        if (typeElement == null)
            return;

        if (!typeElement.DerivesFromGodotObject()) // could you please check if it only makes sense for the Node or all GodotObjects?
            return;

It would ensure that other classes unrelated to Godot would not be affected by the new analyzer.

Added and tested mechanism for quickfix and added validation for classes, so the issue must be resolved now

Some wording improvement could be done.
I think using term "parameterless constructor" would be better then "Constructor with no parameters" and "empty constructor with no parameters"

Try to use similar wording as Godot documentation:
here is what I have found https://docs.godotengine.org/en/latest/tutorials/scripting/resources.html#creating-your-own-resources
(in the C# example)
// Make sure you provide a parameterless constructor.
// In C#, a parameterless constructor is different from a
// constructor with all default values.
// Without a parameterless constructor, Godot will have problems
// creating and editing your resource via the inspector.

Would be ConstructorElementProblemAnalyzer, NoParameterlessConstructorError and ParameterlessConstructorQuickFix appropriate naming for classes?

Also Add parameterless constructor and Parameterless constructor is required to initialize a script/game object as messages for users

Yeah, sure

Additionally we can use external annotations to mark the default ctor as UsedImplicitly.


Changelog

With the flurry of releases/versions that were just published, please can you update the CHANGELOG.md file so that we can see a summary of what happened and better understand where the breaking changes in 4.x are? Thanks.

Or if the https://github.com/visionmedia/debug/releases page is where that information should be referenced can you link it from Changelog?

I very much agree with the above, the CHANGELOG should either be updated or point to the releases section on GitHub

Yes, I plan on it. In the meantime, please see the post-mortem in #603 for a description of the versions that were released.
To be clear, versions should be deprecated in a way that acts like the snafu didn't happen - as if only debug@4 was the only version released.

Hi - the releases page has been updated. Thanks for the issue!


Consumer GetOffset from kafka after restart

if i do not save the last offset in the client side, ie if I'm not passing OffsetPosition[] to the Consumer(), Is there any way I can use the kafka-net API to automatically read the saved offset from kafka broker and continue consume where I left off ?  This is helpful to avoid duplicates when my client (consumer ) restart.

got it, i'll be creating a highlevel consumer using the offsetcommitrequest and solve my problem.

It would be great if you can share the way of handling the offset.


Tutorial

Sections

Setting up dev environment
Tour of Haskell syntax
Type driven development
Getting a hello world server
Following along MDN tutorial

https://wiki.clean.cs.ru.nl/Quick_impression


Reword ssl_conf_max_frag_len documentation to clarify its necessity

This PR is supposed to fix #2258 by increasing precision of the max fragment length API documentation.

@hanno-arm Thanks for the review. I have addressed your comments.

@AndrzejKurek Thanks for the review. I have addressed your comments. If @hanno-arm, who you asked for comments, objects my new changes, I am willing to introduce further changes.

@hanno-arm You left comments on an earlier version, can you please re-review?

Thank you all for further comments. I tried addressing all of them.
@hanno-arm I made an attempt of restructuring the initial part of the comment, but, unfortunately I didn't feel that I can improve what is already there. Also, I would rather avoid referring from the code to external documentation due to a maintenance costs. So, as I think I cannot address that suggestion correctly, I decided I should not do it.

@mpg or @hanno-arm - please re-review this PR.

@hanno-arm Thanks for your review. I have address your comment; could you please re-review the PR?
@AndrzejKurek Could you please re-review the PR as well?

@hanno-arm @AndrzejKurek As the backports have been approved, I added a change log entry here, which forced me to rebase this PR. Could you please re-review it?


builder: Switch to goversioninfo RPM

The golang-github-josephspurrier-goversioninfo RPM is now available through CBS.

It's there :) https://cbs.centos.org/koji/buildinfo?buildID=44184
If you could run a test build on arm64 before merging, that'd be great though!


Fix import eDistantObject for cocoapods

Fix for #1510

Please merge this PR as it is blocking our use case where we have a separate Pod Framework in our Podfile hence EarlGrey is failing to build without this fix at the moment.

How long does it take for changes to get merged in to CocoaPods? Am still not observing this change in installed EarlGreyTest Pod

@shaneong we merged this internally so closing this. We'll have to do another CocoaPods release which I can check with the team on the duration of.

Can you prioritize this fix as being able to use EarlGrey in conjunction with use_frameworks! should be a common ask in CocoaPods, or at least provide a workaround solution in the meantime?


[Bug-9608] Serialize the task definition failed

Fix: #9608

Codecov Report

Merging #9622 (e5d5f70) into dev (9d11be4) will decrease coverage by 0.04%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##                dev    #9622      +/-   ##
============================================
- Coverage     39.96%   39.92%   -0.05%
- Complexity     4437     4462      +25
============================================
  Files           832      835       +3
  Lines         33351    33541     +190
  Branches       3683     3707      +24
============================================
+ Hits          13328    13390      +62
- Misses        18792    18906     +114
- Partials       1231     1245      +14

Impacted Files
Coverage Δ

...he/dolphinscheduler/dao/entity/TaskDefinition.java
73.10% <66.66%> (+8.76%)
:arrow_up:

...lphinscheduler/api/controller/UsersController.java
59.25% <0.00%> (-2.28%)
:arrow_down:

...er/api/controller/ProcessDefinitionController.java
45.34% <0.00%> (-2.22%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...api/service/impl/ProcessDefinitionServiceImpl.java
31.07% <0.00%> (-0.67%)
:arrow_down:

...i/service/impl/ProcessTaskRelationServiceImpl.java
21.03% <0.00%> (-0.64%)
:arrow_down:

...scheduler/api/service/impl/ProjectServiceImpl.java
77.12% <0.00%> (-0.54%)
:arrow_down:

...cheduler/api/service/impl/ExecutorServiceImpl.java
40.62% <0.00%> (-0.26%)
:arrow_down:

.../org/apache/dolphinscheduler/api/enums/Status.java
100.00% <0.00%> (ø)

...ache/dolphinscheduler/dao/entity/K8sNamespace.java
0.00% <0.00%> (ø)

... and 13 more

Continue to review full report at Codecov.

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

Thanks for your contribution @naziD


error pull image sonarqube

Expected behavior
Download images
Actual behavior
Information about the Issue
HTTP code is 500 which indicates error: server error - {"message":"Get https://registry-1.docker.io/v2/library/sonarqube/manifests/latest: Get https://auth.docker.io/token?account=ssanchezbassan\u0026scope=repository%3Alibrary%2Fsonarqube%3Apull\u0026service=registry.docker.io: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"}
Steps to reproduce the behavior

intro to kitematic
download image sonarqube

I'm not having the same issue and able to download the image without any issue.
Can you try again?


[AP-7516] Receptor Config Support

wip
wip
config for receptors
wip
Summary

Test Plan

Task
[AP-###]

#60  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sen-trustero and the rest of your teammates on  Graphite


Simple Interface: Configure STUN/TURN

The Simple interface is very nice to use and sufficient for an app I am developing.
The only thing missing for me is the ability to configure STUN and TURN servers.
As these configuration options seem to be pretty essential, even for a simple SIP client, because
the absence of them can break connectivity, I'd like to suggest adding those options to the Simple Configuration Parameters.
Tnx for sip.js.

The Simple Interface is deprecated for the SimpleUser interface and will be gone in 0.16.0.


As Portal User, I need to enter initial set of characters into the keyword search field so that it display the suggested keyword terms, corrected misspellings, and phrases.

From @czdiana2321 on June 1, 2018 19:53
USER-> Search
Acceptance Criteria:

The system is able to display the suggested keyword terms after entering the initial set of characters into the keyword search field.
Portal User is able to view the suggested keyword terms after entering the initial set of characters into the keyword search field.

Copied from original issue: Microsoft/Access2Justice#114

duplication of #481


feat(api): Allow restricting access for API tokens via resource/method rules

Note: remember to toggle "hide whitespace changes" when reviewing cause the prettier changed indentation all around
What does this pull request do? Explain your changes. (required)
This is to add support for creating API tokens that have limited access to the API.
It can be used for things like read-only API tokens or well-scoped tokens that only have access
to a specifc API or API group.
e.g.: A token that would only give access to POST /api/stream/hook/*, POST /api/usage/update
and PUT /region/:id:
{
  access: {
    rules: [
      {
        resources: ["stream/hook/*", "usage/update"],
        methods: ["post"],
      },
      { resources: ["region/:id"], methods: ["put"] },
    ],
  }
}

Specific updates (required)

New logic in auth middleware to authorize access rules on API tokens, if present
New logic in api-token API to validate access rules on tokens being created
Lots of tests on both of those
Some typescript changes and utilities that I ended finding helpful on the way

-
How did you test each of these updates

yarn test --silent
Ran locally and tested with 4 api tokens:

legacy: no access field configuration, should have all access
all-access: * * access, should have all access as the legacy above
read-only: access to GET methods only
infra: access to only the stream/hook, usage/update and region/:id apis mentioned above

All worked well 😌
Does this pull request close any open issues?
Implements: https://github.com/livepeer/livepeer-com/issues/491
Checklist:

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

This is now ready for review!

@iameli Sure, I can do that! Just not sure how I can test all the flows to make sure they work properly (especially the other ones apart from /stream/hook/*).
Are you thinking of 1 api key for all those APIs, as I exemplified in the PR description? Or only for the '/stream/hook/*' for now?

Just done on staging:

Created the<EMAIL_ADDRESS>account, made it an admin
Created an API key with:

curl --location --request POST 'https://livepeer.monster/api/api-token' \
--header 'Authorization: JWT <infraservice JWT>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "name": "PRODUCTION KEY FOR STREAM HOOKS AND ORCH CRON DON'T DELETE",
    "access": {
        "rules": [
            {
                "resources": ["stream/hook/*"],
                "methods": ["post"]
            },
            {
                "resources": ["region/:id"],
                "methods": ["put"]
            }
        ]
    }
}'

Checked token really only works for the specified APIs
Updated it on staging vault, both for admin key used in orch cron and basic auth for webhooks
Re-deployed staging stuff with ansible-playbook ...deploy-staging.yaml
Checked token was working for /region/:id by orchs cronjob via kubectl and dashboard's lastActive
Checked token was working for /stream/hook with successful stream through stream-tester
Checked token was working for /stream/hook/detection by testing detection webhook from webhook.site. Checked lastActive kept up to date as stream was live

I'm now confident about taking this to production, let's do it next week :D


SAK-32459 - Equals method incorrect in sitestats locale

Yeah, I thought about doing Lombok but that has a non zero chance of introducing issue where I didn't think this either left alone or changed would have much risk.


fix path issue in windows

Signed-off-by: yxxhero<EMAIL_ADDRESS>fix path issue in windows
fix: https://github.com/helmfile/helmfile/issues/382

@mumoshu


Is it possible to use the MakeCustomLimit method in the Python framework?

What language and solver does this apply to?
Python
Describe the problem you are trying to solve.
I am using CP-SAT from Python and I would like to use a custom limit, to stop the solver when a given in-house criterion is met. I've found a method that seems to do so in C++ here but nothing in Python.
Describe the solution you'd like
I'd love to be able to pass such a custom limit function to the solver.Solve method, just as a solution_callback is passed.
Describe alternatives you've considered
Otherwise, I would probably try and use the solution_callback possibility, and send a SIGINT (Ctrl+C) when my condition is met. I haven't tried yet but I guess that would work.
Additional context
Nope.
Thanks for your reply and excellent job!

OK.

this is not a product issue.
this is explained here: https://github.com/google/or-tools/blob/master/ortools/sat/docs/solver.md#stopping-search-early

Thanks @lperron! and sorry for the "product issue" labelling, I was asked to make a labelling choice and could find the right one...
I didn't know about this solver.md page, it's great!


Add an unload data method to some of the Product classes

Specifically this thought was triggered by the PSFGrid and PSF product classes, as it is highly unlikely that they will be used again after the first PSF correction, and they take up a LOT of memory. It would be nice if the rl_psf (or any future PSF deconvolution algorithm) function could call an unload_data() method and get it out of memory.

The PSFGrid class will have an 'unload_data' method that will cycle through the component PSFs and remove their data from memory. The component PSFs are subclasses of Image, so I will add a @data.deleter property to the Image class to allow for the unloading of data, thats what unload_data will call.


Add VehicleImpact to RestrictionRoadEvent

Summary
The Specification Update Subgroup recommends adding the VehicleImpact property, as-is, to the RestrictionRoadEvent Object.
Motivation
Adding the VehicleImpact property to RestrictionRoadEvent Object lets data publishers inform drivers about how a restriction affects navigation.
Proposed changes
After Change

Name
Type
Description
Conformance
Notes

core_details
RoadEventCoreDetails
Describes the basic characterisitics of a road event.
Required

restrictions
Array; [Restriction]
A list of zero or more road restrictions that apply to the roadway segment described by this road event.
Conditional: required if lanes property is not provided.
Restrictions can also be provided on an individual lane.

lanes
Array; [Lane]
A list of individual lanes within a road event (roadway segment).
Conditional: required if restrictions property is not provided.

vehicle_impact
VehicleImpact
The impact to vehicular lanes along a single road in a single direction.
Required

Before Change

Name
Type
Description
Conformance
Notes

core_details
RoadEventCoreDetails
Describes the basic characterisitics of a road event.
Required

restrictions
Array; [Restriction]
A list of zero or more road restrictions that apply to the roadway segment described by this road event.
Conditional: required if lanes property is not provided.
Restrictions can also be provided on an individual lane.

lanes
Array; [Lane]
A list of individual lanes within a road event (roadway segment).
Conditional: required if restrictions property is not provided.

For reference, the vehicle_impact property already exists on the WorkZoneRoadEvent object.

The extension committee intends to rescind this issue because it will be covered in Issue #270.


Improve performance of query - getPowerBoostingSnapshotWithoutBalance

This query takes more than one minutes to run.
select "userId", "powerSnapshotId", "blockNumber","walletAddress"
        from (select DISTINCT "powerSnapshotId", "userId" from power_boosting_snapshot) as boosting
        inner join public."user" as "user" on  "userId"= "user".id
        inner join power_snapshot as "snapshot" on boosting."powerSnapshotId" = snapshot.id
        where snapshot."blockNumber" is not NULL
        and not exists (
          select
          from power_balance_snapshot as "balance"
          where balance."powerSnapshotId" = boosting."powerSnapshotId" and
          balance."userId" = boosting."userId"
        )
        order by "blockNumber" ASC
        LIMIT $1
        OFFSET $2

Need to change how we have designed back-end, putting a heavy load on the back-end, we probably cannot optimize this since it is a complex query.
Will need a few weeks to work on technical debts like this

How can I test this issue?
should we check all scenarios related to Givpower and ranking calculation  to sure every thing works as before on STG or sth more should be tested?
@aminlatifi

How can I test this issue? should we check all scenarios related to Givpower and ranking calculation to sure every thing works as before on STG or sth more should be tested? @aminlatifi

@maryjaf Yes, GIVpower sorting (not instant boosting) must be tested. We must be sure the balance snapshotting and calculating the balance based on average of periodic snapshots is working as before

On stg:
Start Date :Sun Aug 6 2023 8:00 PM
End Date: Sun Aug 20 2023 8:00 PM
Can you decrease the round time on stg ?

Some times by modifying the percentage of Givpower, my Givpower is changed to 0 and after that by refreshing has been resolved

@aminlatifi

we get data from the subgraph, maybe it has a problem when you check it. Besides that, we refactored this part completely on GIVeconomy. and will fix on new release.

Some times by modifying the percentage of Givpower, my Givpower is changed to 0 and after that by refreshing has been resolved

Thanks @MohammadPCh I didn't see this problem on GIVeconomy and it seems it has been resolved


Changed Github to default brand color.

This changes the GitHub icon to the default brand color of Github. I know you can change the bgColor in CSSinJS but it is more difficult when mapping an array to do so.
Please accept this PR.

Thank you for bringing up this issue @eclectic-coding. I've updated the brand color to #24292e  per github's style guide at https://styleguide.github.com/primer/utilities/colors/ in commit https://github.com/jaketrent/react-social-icons/commit/aa3e78f675f585d2a3ab518e89f753152ab3017c. I will work on getting a v5 release with this change prepared.


Make it German

the readme is auto generated, so it has to be changed in the template in https://github.com/EngineeringKiosk/GermanTechPodcasts/blob/main/assets/README.template but we have to discuss first how we want to proceed with the language in #29

In https://github.com/EngineeringKiosk/GermanTechPodcasts/blob/main/DEVELOPMENT.md we describe a bit the generated README part.

Ich lerne Deutsch. Ich möchte es meiner Lehrerin zeigen.

Closed by #112


chore: update go version in travis

Coverage remained the same at 63.767% when pulling 99b8e0f9caf8f280dbd08e09fa0ac892d0bc5507 on ci/go-version into 2d4605d582ad6f24cd62ee7860e907d828fbe28c on master.

Coverage remained the same at 63.767% when pulling 99b8e0f9caf8f280dbd08e09fa0ac892d0bc5507 on ci/go-version into 2d4605d582ad6f24cd62ee7860e907d828fbe28c on master.


Finalize 2.7.0 try2

[x] Mask high latitudes where albedo has extreme values in ceres ebaf, to resolve #589
[x] Add script to shift TRMM data; upload revised TRMM 3hourly climo
Added script for manually fixing the data; uploaded fixed data to LCRC
[x] Include Dust AOD (model only for now)
[ ] Update complete test by adding aerosol aeronet diags, lat-lon-land, lat-lon-river
[x] Refine ELM and Mosart lat-lon figures.
[ ] Update observation data paths for all machines in docs, tests scripts (using mache?) and create symlinks for backward compatibility.
[x] Update test datasets by adding land and river datasets. (data copied to /lcrc/group/e3sm/public_html/e3sm_diags_test_data/postprocessed_e3sm_v2_data_for_e3sm_diags/ . Need further clean-up, and need update mache for test data path.
[x] Update documentation with updated diags (Change README)

@chengzhuzhang Got it, thanks. I will review this and then try to get the new run_2_7_0_all_sets_E3SM_machines.py script in this PR.

@tomvothecoder Thank you. Just to add one note to remember to add aerosol_aeronet to the run set as follows:
    runner.sets_to_run = [
        "lat_lon",
        "zonal_mean_xy",
        "zonal_mean_2d",
        "zonal_mean_2d_stratosphere",
        "polar",
        "cosp_histogram",
        "meridional_mean_2d",
        "annual_cycle_zonal_mean",
        "enso_diags",
        "qbo",
        "area_mean_time_series",
        "diurnal_cycle",
        "streamflow",
        "arm_diags",
        "tc_analysis",
        "aerosol_aeronet",
    ]

I think we are in good shape to merge this PR, @tomvothecoder .  Since @golaz and @forsyth2  already did good amount of testing through zppy and e3sm_unified on earlier version of e3sm_diags 2.7.0 rcs, I think we can start the releasing process.

Sounds good @chengzhuzhang, I will merge this and can handle bumping to v2.7.0 in a new PR.

@tomvothecoder Thank you! I will draft the release message afterward.


Yaml linter

What does it do?

What does it do?

It verifies YAML format for the actions that don't run on PRs, so you don't have to merge to find out your formatting is incorrect.


Output invalid and filled with _'s. Also, Datetime documentation

I apologize if this isn't the right place to put this, but I could not figure out how to contact you Robin.
So I am trying to find some detailed info on the DateTime documentation. Does any exists?
Also, I am trying to get a format of .inputmask("mm/dd/yyyy hh:mm"), but it keeps coming out as 0312/2016/________________ :
Is this a bug?

@Godrules500 ,
Sorry, I missed your issue.
Is this still valid or can it be closed?


Indicate loading in UI while sorting options are changing on category page

Codecov Report

Merging #1016 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1016      +/-   ##
==========================================
- Coverage   63.69%   63.67%   -0.02%
==========================================
  Files         116      116
  Lines        6112     6112
  Branches      744      744
==========================================
- Hits         3893     3892       -1
  Misses       2066     2066
- Partials      153      154       +1

Impacted Files
Coverage Δ

saleor/core/utils/random_data.py
83.59% <0%> (-0.4%)
:arrow_down:

Continue to review full report at Codecov.

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


add whole binary datasource

What changes were proposed in this pull request?

[ ] Add two source files (org/apache/spark/WholeBinaryFileFormat.scala, streaming/core/datasource/impl/MLSQLWholeBinary.scala) to support whole binary datasource. Whole binary datasource can load hdfs file as a table with two columns(path: string, content: binary)  but don't support save!

How was this patch tested?

[ ] use mlsql test: load wholeBinary.`/tmp/test/` as output;

Are there and DOC need to update?

[ ] Doc is not finished

Spark Core Compatibility

It's a nice PR. But there are some minor changes you may do:
First, Have you tested spark 2.3.x/2.4.x? If WholeBinaryFileRecordReader is compatibility with both versions, that's fine. If not, please put this file in streamingpro-spark-2.4.0/streamingpro-spark-2.3.0 separately, and it may require you to do some minor changes.
Second, can you move MLSQLWholeBinary to tech.mlsql.datasource.impl?  And when I fetch the PR, it seems you are not developing based on the latest master codebase.
And the last but most importantly, can you add come unit test or docs for your features?

I changed some thing for this pr:

Whole binary datasource support streamingpro-spark-2.4.0/streamingpro-spark-2.3.0 separately.
Add scala test streaming.test.datasource.HDFSWholeBinaryFileSpec.
Move MLSQLWholeBinary to package tech.mlsql.datasource.impl.
Whole binary datasource support save.

And i think wholeBinary datasource can replace image datasource, they are the same datasource!

Useage exemples
select 'twbFile2.txt' path, binary('abcdef222') content as testWholeBinary;
save append testWholeBinary as wholeBinary.`/tmp/wbtest2`;

load wholeBinary.`/tmp/wbtest2` as tmp;

select path, string(content) from tmp as output;


Can we have both ssl and non-ssl SRV records?

Can we have both ssl and non-ssl SRV records for discovery?
If yes then how will etcd behave, I mean will the peers communicate on ssl or non-ssl?

@raoofm etcd will be misconfigured. Do you think it make sense to prioritize ssl ones over non-ssl? Or do you want to try weights? There are todos for srv discovery.
See  https://github.com/coreos/etcd/blob/master/discovery/srv.go#L31-L33

@raoofm Closing due to low activity. If you are still interested in making this happen, please reopen it.

@xiang90 I opened this issue based on our prod experiences and extensive performance testing.
We figured that etcd performance degrades in two cases (auth & https)
etcd is fast enough for our usage but in case we hit a point where we wanted to disable https or auth then it shouldn't be a multi layer change, u should be allowed to just flip a flag to use https or not. It shouldn't be a change in SRV records managed by other teams, it should be local to etcd.
Keeping that in mind, if it is allowed to have ssl and non ssl SRV records and having a flag in etcd to indicate whether https is required or not will be great.
I understand it is not possible for v2. If it is an acceptable usecase then it will be good if you guys consider this for v3.
Also what i meant by saying "can we have both ssl and non-ssl" is within a same cluster can we have a mixed cluster with ssl and non-ssl records
node1 -> node2 ssl
node2 -> node1 ssl
node1 -> node3 non-ssl
node2 -> node3 non-ssl
node3 -> node1 ssl
node3 -> node2 ssl

Also what i meant by saying "can we have both ssl and non-ssl" is can we have a mixed cluster with ssl and non-ssl records

What is the use case for this? Cross DC cluster? To support this, we need to change a few things, not just srv records.

yes

Another thing that i wanted to propose is - why do we have different SRV records for ssl and non ssl records
As of now we specify
_etcd-server._tcp.example.com. 300 IN   SRV 0 0 2380 infra0.example.com.
or
_etcd-server-ssl._tcp.example.com 300 IN   SRV 0 0 2380 infra0.example.com.
and start etcd like
$ etcd -name infra0 -discovery-srv example.com
Instead we can always specify only
_etcd-server._tcp.example.com. 300 IN   SRV 0 0 2380 infra0.example.com.
and start etcd like
$ etcd -name infra0 -discovery-srv example.com -peer-mode ssl
or
$ etcd -name infra0 -discovery-srv example.com -peer-mode non-ssl
Another option is we can always specify only
_etcd-server._tcp.example.com. 300 IN   SRV 0 0 2380 infra0.example.com.
and start etcd like
$ etcd -name infra0 -discovery-srv example.com
and determine whether ssl is required or not from -listen-peer-urls and/or -initial-advertise-peer-urls
By doing this, we keep the change of etcd peer communication ssl/non-ssl local to etcd and not on DNS SRV

Same thing for something you recently proposed for new SRV for client

@raoofm
The first proposal requires additional flag and it is just for srv discovery.
The second proposal requires for smart etcd configuration, which we try hard to avoid.
Is there any trouble for you to switch from non-ssl SRV records to ssl ones?

@raoofm In another word, I feel a SRV discovery configuration should deterministically define one etcd cluster configuration. Restarting etcd or changing etcd flags should not affect the cluster configuration. Mixing ssl and non-ssl might be acceptable, but that requires other changes. Changing a flag in etcd to change the entire cluster configuration seems to be not acceptable.

agree, thanks

@raoofm No problem. It would be great if you can create an issue for mixing https and http member cluster? I can do that later.

sure


libev: Add statically linked libev to pkgsStatic

Motivation for this change
I have a use case for compiling a fully static binary with libev. I added this my project and it worked nicely.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @r-ryantm

Could I get a review please? Tagging more folks from the commit history:  @wkennington @fpletz @joachifm

@GrahamcOfBorg build pkgsStatic.libev

Thanks. I haven't managed to cross compile on macOS yet. Last time I tried it failed to build the toolchain.
I could've done something wrong too. I'll try again soon.


⚠ Fortnite has degraded performance

In 48ff921, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1502 ms

Resolved: Fortnite performance has improved in 17added.


Minor changes.

Minor changes.

@harawata  @kazuki43zoo Thank you for your suggestions.

Merged. Thank you for your contribution, @peterchenhdu !
@kazuki43zoo Good catch! Thanks!