Question: Sticky session in routes with load balancer

Question/Enhancement:
Is there any plans to support sticky session for the load-balanced routes?
Currently, I found out the way how to do it via override LoadBalancerClientFilter and create custom "sticky" ribbon rule.
But I wonder maybe there are any plans to do it "out of the box"?

We have no plans for this

+1 - this would be a useful enhancement

+1 - especially in enterprise development

Question/Enhancement:
Is there any plans to support sticky session for the load-balanced routes?
Currently, I found out the way how to do it via override LoadBalancerClientFilter and create custom "sticky" ribbon rule.
But I wonder maybe there are any plans to do it "out of the box"?

How to create Ribbon rule, could you share your code ?
thinks!

@xinghen110
For Ribbon
to make it work you should do a few things

Override LoadBalancerClientFilter
to add code like:

    @Override
    public ServiceInstance choose(ServerWebExchange exchange) {
        String host = ((URI) exchange.getAttribute(GATEWAY_REQUEST_URL_ATTR)).getHost();
        return this.loadBalancer.choose(host, allSourcesMultiValueMapFrom(exchange));
    }

    private MultiValueMap<String, String> allSourcesMultiValueMapFrom(ServerWebExchange exchange) {
//choose only params you need, just sample code to illustrate a few options
        ServerHttpRequest request = exchange.getRequest();
        MultiValueMap<String, String> multiValueMap = new LinkedMultiValueMap<>();
        multiValueMap.addAll(request.getHeaders());
        multiValueMap.addAll(request.getQueryParams());
        request.getCookies().entrySet()
                .forEach(entry -> multiValueMap.add(entry.getKey(),entry.getValue().get(0).getName());
        return multiValueMap;
    }

Implement
Ribbon Rule
public class StickySessionRule extends RoundRobinRule {

    @Override
    public void initWithNiwsConfig(IClientConfig clientConfig) {
    }

    @Override
    public Server choose(Object routingOptions) {
        validateRoutingOptions(routingOptions);
        String instanceName = getInstanceName((MultiValueMap<String, String>) routingOptions);
        return hasInstanceName(instanceName)
                ? getStickyServer(instanceName)
                : super.choose(routingOptions);
    }
//specific logic is omitted
}

for each sticky service add
property
service-with-sticky.ribbon.NFLoadBalancerRuleClassName={ClassPackage}.StickySessionRule

Anyway I think this ribbon related login won't ever appear in this repo since it will be superseded by https://github.com/spring-cloud/spring-cloud-commons/issues/689

@spencergibb
I've played around new ReactiveLoadBalancerClientFilter and found you that for now, it disallows to use custom load balancing strategies per-route since it is not by-pass request data to the loadBalancer.choose method
https://github.com/spring-cloud/spring-cloud-gateway/blob/master/spring-cloud-gateway-core/src/main/java/org/springframework/cloud/gateway/filter/ReactiveLoadBalancerClientFilter.java#L132
would you accept PR to by-pass ServerHttpRequest in the Request context (or even ServerWebExchange, since I'm not sure about other use-cases in the community )?
or as an alternative (probably preferable) rework
private Request createRequest() {
		return ReactiveLoadBalancer.REQUEST;
	}

to
// protected here instead of private to give an ability to customize context bypassing
protected Request createRequest(ServerWebExchange exchange) {
		return ReactiveLoadBalancer.REQUEST;
	}

or there plans to bypass some custom context once features like
https://github.com/spring-cloud/spring-cloud-commons/issues/689
will be done?

We're planning on supporting passing a context especially since a server request makes a lot of sense to make decisions during load balancing

We'll be adding a sticky implementation for the new LoadBalancer: https://github.com/spring-cloud/spring-cloud-commons/issues/689

@Fetsivalen
Could you provide the entire implementation of how you implemented sticky session rule with implementation for the functions you have mentioned like getStickyServer. Please do help me out

@neelimaj97 sorry, but no.
In comment https://github.com/spring-cloud/spring-cloud-gateway/issues/1176#issuecomment-612791740
I put all except logic specific to my case, which is definitelly shouldn't be here.

@Fetsivalen I am not able to override LoadBalancerClientFilter in spring-cloud-gateway 2.2.2-RELEASE. Could you show just the part where you have overridden the LoadBalancerClientFilter. Thanks, it would help so much

Goal
HA microservice setup, with 2 gateways, 2 frontend-services and of course a couple of backend services behind them.

Every user request can be routed through a random gateway to one of the frontend instances.
Upon first request a frontend instance is picked, following requests should end up at the same frontend instance for session reasons.
Solution
Following the suggestion in this issue, especially @Fetsivalen spring-cloud-gateway comment in #1176
and the PR of @fitzoh in spring-cloud-commons #764 I was able to implement a load-balanced sticky session based on Spring Boot 2.5.4, Spring Cloud 2020.0.3, Spring Cloud Gateway 3.0.3. Information to which frontend instance subsequent requests are routed to are stored in a cookie.
See exemplary implementation.
Basic logic upon every request:

GlobalFilter ReactiveLoadBalancerStickySessionFilter. Chooses ServiceInstance from LoadBalancer.

If available take ServiceInstance from cookie, otherwise choose one.

Enrich cookie with ServiceInstance id.

However, this smells a bit clumsy with quite some custom code.
After seeing @OlgaMaciaszek  mention of spring-cloud-commons issue #689 and the merge of spring-cloud-commons #862 I'm beginning to suspect this approach might be doable with more "in-house" usage of spring classes. Specifically with SameInstancePreferenceServiceInstanceListSupplier but I currently don't really see how to plug it together.
Questions

Is what I did a "valid" approach in general?
Is @spencergibb comment final, there won't be an implementation in spring-cloud-gateway?

If not, why is this issue still open?
Does spring-cloud-commons #689 fully answer spring-cloud-gateway #1176?

Is there an easier solution in sight with less custom code, maybe by using the spring-cloud commons classes?

If yes, any hints or examples how to apply?

Did I miss something totally obvious?

Any thoughts in this regard appreciated.


Doesn't work

I was looking for a good spinner library and this seemed the best but on the latest version of React etc it gives me

when I try to do
import { BarLoader } from 'react-css-loaders'

@forgetableDr same happened to me but rolling back to v0.0.5 works (with<EMAIL_ADDRESS>npm install<EMAIL_ADDRESS>


win32 and macOS should be included the list of available platforms

What happened?
Currently all our jest tests run on Android. We want to be able to run them on win32. When we try to configure the test to run on win32, we get an error that the only available platforms are iOS and Android.
ERR! [@fluentui-react-native/win32-theme test] ERROR DETECTED
ERR! started
ERR! hash: 6c9d8d460cd73da8f083ae615393c0efa630f1da, cache hit? false
ERR! Running /var/folders/d2/s15t9v9s09392vpbfv_h78dw0000gn/T/yarn--1666295648841-0.6314284952155775/yarn run test -- -u
warning From Yarn 1.0 onwards, scripts don't require "--" for options to be forwarded. In a future version, any explicit "--" will be forwarded as-is to the scripts.
$ fluentui-scripts jest -u
ERR! [12:54:47 PM] ■ started 'jest'
ERR! [12:54:47 PM] ■ Running Jest
ERR! [12:54:47 PM] ■ /usr/local/bin/node "/Users/lyzhan/Documents/GitHub/fluentui-react-native/node_modules/jest/bin/jest.js" --config "/Users/lyzhan/Documents/GitHub/fluentui-react-native/packages/theming/win32-theme/jest.config.js" --colors --updateSnapshot
ERR! Error: 'win32' was not found among available platforms: ios, android
ERR!     at getTargetPlatform (/Users/lyzhan/Documents/GitHub/fluentui-react-native/node_modules/@rnx-kit/jest-preset/src/index.js:91:11)
ERR!     at module.exports (/Users/lyzhan/Documents/GitHub/fluentui-react-native/node_modules/@rnx-kit/jest-preset/src/index.js:198:42)
ERR!     at configureReactNativeJest (/Users/lyzhan/Documents/GitHub/fluentui-react-native/scripts/lib/configs/configureJest.js:41:38)
ERR!     at Object.<anonymous> (/Users/lyzhan/Documents/GitHub/fluentui-react-native/packages/theming/win32-theme/jest.config.js:2:18)
ERR!     at Module._compile (internal/modules/cjs/loader.js:1085:14)
ERR!     at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
ERR!     at Module.load (internal/modules/cjs/loader.js:950:32)
ERR!     at Function.Module._load (internal/modules/cjs/loader.js:790:12)
ERR!     at Module.require (internal/modules/cjs/loader.js:974:19)
ERR!     at require (internal/modules/cjs/helpers.js:101:18)
ERR! [12:54:54 PM] x Error detected while running 'jest'
ERR! [12:54:54 PM] x ------------------------------------
ERR! [12:54:54 PM] x Error: Command failed: /usr/local/bin/node /Users/lyzhan/Documents/GitHub/fluentui-react-native/node_modules/jest/bin/jest.js --config /Users/lyzhan/Documents/GitHub/fluentui-react-native/packages/theming/win32-theme/jest.config.js --colors --updateSnapshot
ERR!     at ChildProcess.<anonymous> (/Users/lyzhan/Documents/GitHub/fluentui-react-native/node_modules/just-scripts-utils/lib/exec.js:93:31)
ERR!     at ChildProcess.emit (events.js:400:28)
ERR!     at ChildProcess.emit (domain.js:537:15)
ERR!     at Process.ChildProcess._handle.onexit (internal/child_process.js:282:12)
ERR!     at Process.callbackTrampoline (internal/async_hooks.js:130:17)
ERR! [12:54:54 PM] x ------------------------------------
ERR! [12:54:54 PM] x Error previously detected. See above for error messages.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERR! failed
info ----------------------------------------------
info Took a total of 44.45s to complete
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Affected Package
@rnx-kit/jest-preset
Version
0.1.11
Which platforms are you seeing this issue on?

[ ] Android
[ ] iOS
[X] macOS
[X] Windows

System Information
info Fetching system and libraries information...
System:
    OS: macOS 12.6
    CPU: (8) x64 Apple M1
    Memory: 18.80 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.19.1 - /usr/local/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 6.14.16 - /usr/local/bin/npm
    Watchman: Not Found
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK: Not Found
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: 14.0/14A309 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.15 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: Not Found
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to Reproduce
In our jest.config file, we called jest-preset with 'win32' instead of 'android' and then ran the test.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @lyzhan7, platform availability is determined by react-native config. You need to at least have @office-iss/react-native-win32 declared under devDependencies for the win32 platform to be detected. Can you try adding it to @fluentui-react-native/win32-theme and run Jest again?


[ 96%] Built target fibonacci_one
Scanning dependencies of target random_mem_access_component
[ 96%] Building CXX object examples/random_mem_access/random_mem_access/CMakeFiles/random_mem_access_component.dir/random_mem_access.cpp.o
[ 96%] Linking CXX shared library ../../../lib/libhpx_random_mem_access.so
[ 96%] Built target random_mem_access_component
Scanning dependencies of target random_mem_access_client
[ 96%] Building CXX object examples/random_mem_access/CMakeFiles/random_mem_access_client.dir/random_mem_access_client.cpp.o
[ 96%] Linking CXX executable ../../bin/random_mem_access_client
[ 96%] Built target random_mem_access_client
Scanning dependencies of target spell_check_file
[ 96%] Building CXX object examples/spell_check/CMakeFiles/spell_check_file.dir/spell_check_file.cpp.o
[ 96%] Linking CXX executable ../../bin/spell_check_file
[ 96%] Built target spell_check_file
Scanning dependencies of target spell_check_simple
[ 96%] Building CXX object examples/spell_check/CMakeFiles/spell_check_simple.dir/spell_check_simple.cpp.o
[ 96%] Linking CXX executable ../../bin/spell_check_simple
[ 96%] Built target spell_check_simple
Scanning dependencies of target startup_shutdown_component
[ 96%] Building CXX object examples/startup_shutdown/CMakeFiles/startup_shutdown_component.dir/server/startup_shutdown.cpp.o
[ 96%] Building CXX object examples/startup_shutdown/CMakeFiles/startup_shutdown_component.dir/startup_shutdown.cpp.o
[ 96%] Linking CXX shared library ../../lib/libhpx_startup_shutdown.so
[ 96%] Built target startup_shutdown_component
Scanning dependencies of target thread_aware_timer
[ 96%] Building CXX object examples/thread_aware_timer/CMakeFiles/thread_aware_timer.dir/thread_aware_timer.cpp.o
[ 96%] Linking CXX executable ../../bin/thread_aware_timer
[ 96%] Built target thread_aware_timer
Scanning dependencies of target spin
[ 96%] Building CXX object examples/throttle/CMakeFiles/spin.dir/spin.cpp.o
[ 96%] Linking CXX executable ../../bin/spin
[ 96%] Built target spin
Scanning dependencies of target throttle_component
[ 96%] Building CXX object examples/throttle/throttle/CMakeFiles/throttle_component.dir/throttle.cpp.o
[ 96%] Building CXX object examples/throttle/throttle/CMakeFiles/throttle_component.dir/server/throttle.cpp.o
[ 96%] Linking CXX shared library ../../../lib/libhpx_throttle.so
[ 96%] Built target throttle_component
Scanning dependencies of target throttle_client
[ 96%] Building CXX object examples/throttle/CMakeFiles/throttle_client.dir/throttle_client.cpp.o
[ 96%] Linking CXX executable ../../bin/throttle_client
[ 96%] Built target throttle_client
Scanning dependencies of target simple_central_tuplespace_component
[ 96%] Building CXX object examples/tuplespace/central_tuplespace/CMakeFiles/simple_central_tuplespace_component.dir/simple_central_tuplespace.cpp.o
[ 96%] Linking CXX shared library ../../../lib/libhpx_simple_central_tuplespace.so
[ 96%] Built target simple_central_tuplespace_component
Scanning dependencies of target simple_central_tuplespace_client
[ 96%] Building CXX object examples/tuplespace/CMakeFiles/simple_central_tuplespace_client.dir/simple_central_tuplespace_client.cpp.o
[ 96%] Linking CXX executable ../../bin/simple_central_tuplespace_client
[ 96%] Built target simple_central_tuplespace_client
Scanning dependencies of target transpose_block
[ 96%] Building CXX object examples/transpose/CMakeFiles/transpose_block.dir/transpose_block.cpp.o
[ 96%] Linking CXX executable ../../bin/transpose_block
[ 96%] Built target transpose_block
Scanning dependencies of target transpose_smp
[ 96%] Building CXX object examples/transpose/CMakeFiles/transpose_smp.dir/transpose_smp.cpp.o
[ 96%] Linking CXX executable ../../bin/transpose_smp
[ 96%] Built target transpose_smp
Scanning dependencies of target transpose_serial_vector
[ 96%] Building CXX object examples/transpose/CMakeFiles/transpose_serial_vector.dir/transpose_serial_vector.cpp.o
[100%] Linking CXX executable ../../bin/transpose_serial_vector
[100%] Built target transpose_serial_vector
Scanning dependencies of target transpose_smp_block
[100%] Building CXX object examples/transpose/CMakeFiles/transpose_smp_block.dir/transpose_smp_block.cpp.o
[100%] Linking CXX executable ../../bin/transpose_smp_block
[100%] Built target transpose_smp_block
Scanning dependencies of target transpose_serial
[100%] Building CXX object examples/transpose/CMakeFiles/transpose_serial.dir/transpose_serial.cpp.o
[100%] Linking CXX executable ../../bin/transpose_serial
[100%] Built target transpose_serial
Scanning dependencies of target transpose_serial_block
[100%] Building CXX object examples/transpose/CMakeFiles/transpose_serial_block.dir/transpose_serial_block.cpp.o
[100%] Linking CXX executable ../../bin/transpose_serial_block
[100%] Built target transpose_serial_block
Scanning dependencies of target transpose_block_numa
[100%] Building CXX object examples/transpose/CMakeFiles/transpose_block_numa.dir/transpose_block_numa.cpp.o
[100%] Linking CXX executable ../../bin/transpose_block_numa
[100%] Built target transpose_block_numa
ayaan@ayaan-Predator-PH315-51:~/workspace/repos/hpx/build$

Hmm, it looks like that there is a missing dependency in our testing infrastructure. The default make does only build the core modules (which is what we want), however the way you invoked the tests (how did you do that?) does not force the test binaries to be built, first. Could you report your command lines (cmake, make, ctest, etc.), please?

i was following the guidelines mentioned on http://stellar.cct.lsu.edu/files/docsplayground/boostbook/html/hpx/debugging/testing.html
i don't know may be i was missing something earlier, i rebuild everything again and things are good now, i am able to run tests, @hkaiser thanks for your time and support.

Is the original issue resolved?
@ayaankhan98 you might want to use this link for documentation instead: https://hpx-docs.stellar-group.org/latest/html/index.html. That page you linked was only used temporarily a long time ago. If you found a link to that somewhere on our pages I'd like to correct it.

Sorry, I closed this by mistake. Reopening...


Create Poscon Banner

Fixes AB#73965
Checklist

[ ] Includes tests
[ ] Update documentation

Changes proposed in this pull request:

Reviewers should focus on:

Screenshot

Just one tip up-front - the banner should have a role="alert" attribute, eg

. This means that assistive technology will draw attention to it when it appears (eg a screen reader would read it out).

Marking as ready for review, why is centre-ing divs such a pain?

Re: your comment about centring divs, if you're stuck on some CSS feel free to show me on a call and we can debug together.

Re: your comment about centring divs, if you're stuck on some CSS feel free to show me on a call and we can debug together.

A refactor has made centre-ing this easier, used Flexbox to position child items


Feature: support custom protocol

Signed-off-by: 楚贤<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
This PR enables customization protocol for dfget and supernode.
Register custom protocol example:

cmd/supernode/main.go

package main

import (
	helloworld

	"github.com/dragonflyoss/Dragonfly/cmd/supernode/app"
	"github.com/dragonflyoss/Dragonfly/pkg/httputils"
)

func init() {
	// here we register "helloworld" protocol
	helloworldTransport := helloworld.NewTransport()
	httputils.RegisterProtocol("helloworld", helloworldTransport)
}

func main() {
	app.Execute()
}

cmd/dfget/main.go

package main

import (
	helloworld

	"github.com/dragonflyoss/Dragonfly/cmd/dfget/app"
	"github.com/dragonflyoss/Dragonfly/pkg/httputils"
)

func init() {
	// here we register "helloworld" protocol
	helloworldTransport := helloworld.NewTransport()
	httputils.RegisterProtocol("helloworld", helloworldTransport)
}

func main() {
	app.Execute()
}

run with dfget

dfget --url helloworld://example/path/to/helloworld --output /path/to/helloworld

Ⅱ. Does this pull request fix one issue?

No
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
N/A

Codecov Report

Merging #1235 into master will decrease coverage by 0.12%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1235      +/-   ##
==========================================
- Coverage   47.91%   47.78%   -0.13%
==========================================
  Files         118      118
  Lines        7436     7454      +18
==========================================
- Hits         3563     3562       -1
- Misses       3587     3605      +18
- Partials      286      287       +1

Impacted Files
Coverage Δ

pkg/httputils/http_util.go
57.52% <0%> (-4.98%)
:arrow_down:

supernode/daemon/mgr/scheduler/manager.go
21.91% <0%> (-0.69%)
: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 7aa441b...0120f51. Read the comment docs.


Updates to Azure installation

As of today, DC/OS 1.8.4 is available in the Azure Marketplace. The policy is: the current docs always contain the detailed setup instructions for the current version (ATM 1.8.4.) and the old/upcoming docs (ATM 1.7 and 1.9) point to the ARM templates via downloads.dcos.io.
Changes in this PR according to above policy:

updates the outdates 1.8 install instructions (incl. new OAuth enable feature)
updates 1.7 and 1.9 docs, replacing step-by-step instructions with ARM templates references

@pyronicide can you pls review and publish, I'd like to blog about it and spread the word ASAP since many folks are waiting for this.

@mhausenblas https://dcosjira.atlassian.net/browse/DCOS-596


Datagrid with actions inside an iframe overlaps columns

Select one ... (check one with "x")
[ x ] bug
[ ] feature request
[ ] enhancement

Expected behavior
When the Datagrid is running inside an iframe and if it has enabled  it should auto fix columns width to the contents like it does when it doesn't has  enabled.
Actual behavior
When the Datagrid is running inside an iframe and if it has enabled  it doesn't fix columns width to the contents.
Reproduction of behavior

You can reproduce the issue in the following link, please make any change in the app component (eg: change Home text button) and save it to reproduce the issue in the iframe view:
https://stackblitz.com/edit/clarity-light-theme-v11-pvcrub
Environment details

Angular version: 5.2.9

Clarity version: 0.11.9

OS and version: OSX 10.13.5

Browser: Chrome Version 67.0.3396.99 (Official Build) (64-bit)

This issue is about a version of Clarity that is out of support. In an effort to better manage our backlog, we are closing this issue. We recognize that some of these issues may remain problematic for you, but to help us to be able to prioritize it we ask for a new GitHub issue with an updated demo with a recent supported version of Clarity.

This issue is about a version of Clarity that is out of support. In an effort to better manage our backlog, we are closing this issue. We recognize that some of these issues may remain problematic for you, but to help us to be able to prioritize it we ask for a new GitHub issue with an updated demo with a recent supported version of Clarity.


Add container test for crashhandler: start qdrouterd in container and have it crash

This way we can check that the Containerfile is correct in respect to libunwind-provided functionality.

I had trouble causing crash in a way that would be detected. Sending SIGABRT to the process did not work. I remember talking to @kgiusti about it, but I forgot the precise problem and the resolution since. I will have to refresh my memory.
Anyways, causing crash through skmanage in -T mode should be a safe alternative to whatever I wanted to do originally.


Small Suggestion Regarding "Correction Comments" in Compiler Error Code Articles (Like this one for CS0230)

When Visual Studio gives an error code it provides a hyperlink to the official MS article regarding the error (like this one for CS0230).    Very helpful.  And I like how these articles provide both (1) an example of C# code that generates the error and (2) a comment showing the correction for the error.
This is often exactly what a coder wants and all they need: A quick example of code clearly demonstrating the error (and the correction) in a style and format that is very easy to "see" and understand quickly.  However, I think the "correction comment" should probably "stand-out" more in these articles.  Ultimately, that is what the reader is really looking for: the correct way.
The "correction comment" in these articles is a bit mild and understated.   It is even written in all lower case letters which is not very "eye catching".  When referencing these pages, a coder is looking to "see" and understand them quickly.  I think making the "correction comment" a little more "eye catching" would help.   This suggestion below might help the coder get to the "correction" a little quicker.
NOTE:  I am not necessarily recommending this style of commenting for commenting code in general.  But, these pages have a special purpose which they understate in a mild fashion.
Below uses this CS0230 error page as an example.
I would suggest the change described below - or something like it.
Change From:
//try the following line instead
Change To:
// *** CORRECTED CODE BELOW ***
// *** THE COMMENTED CODE BELOW CORRECTS THE ERROR GENERATED BY THE CODE ABOVE
Below, I expand the text in this example taken from this CS0230.  I think it demonstrates the difference even more.
Change From:
class MyClass
{
public static void Main()
{
int[] myarray = new int[3] {1,2,3};
  foreach (int in myarray)   // CS0230
  // try the following line instead
  // foreach (int x in myarray)
  {
     Console.WriteLine(x);
  }

}
}
Change To:
class MyClass
{
public static void Main()
{
int[] myarray = new int[3] {1,2,3};
  foreach (int in myarray)   // CS0230
  // *** CORRECTED CODE BELOW
  // *** THE COMMENTED CODE BELOW CORRECTS THE ERROR GENERATED BY THE CODE ABOVE
  // foreach (int x in myarray)
  {
     Console.WriteLine(x);
  }

}
}
Did you see the difference quickly and easily?  If so, people referencing these error code pages will likely see the same.
Just a suggestion.

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

ID: 416d2cb6-250d-f20a-2351-39c7d31d0ac0
Version Independent ID: 12889d33-75e4-b698-f020-3f63061f5768
Content: Compiler Error CS0230
Content Source: docs/csharp/misc/cs0230.md
Product: dotnet-csharp
Technology: csharp-diagnostics
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for opening this @toddalbers
I think it's better to not include the correction in the same snippet, but a new snippet under a new heading. Similar to CS1721.

Thanks @toddalbers
This is important information to take into account in any plans for #24002


Remove hasAttribute

@kquick or @Ptival could you check the change to assist?

@glguy
The Prolog files in the ontology directory are actually generated via:
https://github.com/ge-high-assurance/RACK/blob/9b5b027072cc0df0b947b4ec403e6b0cf965a9c7/assist/bin/rack/write_ontology.pl#L179-L186
However, the files are otherwise out of date, as well as the instructions (since we have moved folder structures a bit).
Note that the OWL files in OwlModel still contain mentions of hasAttribute, so currently, regenerating prov-s.pl adds back hasAttribute.
Are we currently updating the OWL files alongside the SADL files? Or is this part of the current trouble with having OWL files checked in?
Anyway, I'm happy with you committing those changes to the Prolog file if you want, or to not update it, after which I can make regenerate it (as well as the other outdated files) and update the documentation where needed.

With the new changes, this seems good to me!

@Ptival , should  the write_ontology process be done as part of CI?

@kquick oh that's a good idea!

@Ptival , should the write_ontology process be done as part of CI?

@kquick oh that's a good idea!

Let's make an issue!

Covered by #217


Fixes #37

Added most of the asynchronous receiver which will allow peer handlers (Issue
ADD:

receiver/receiver.go Houses functionality for the asynchronous receiver.

This isn't done until it removes the hash key from the dictionary after it sends to the channel.

Also, unit tests aren't actually being ran.


[devicelab] retain first frame data in certain integration tests.

Part of https://github.com/flutter/flutter/issues/143404
We currently drop the first N frames of all benchmarks. For the app based benchmarks (not microbenchmarks) this is harmful as we miss first time initialization costs in our CI.
Still need to do this with flutter/gallery, but that lives in a different repo.

Caveats:

We can't do this for the e2e based benchmarks.
The flutter/gallery tests live in flutter/gallery

The e2e tests do not use the timeline at all, instead they're using the FrameTimings API: https://api.flutter.dev/flutter/dart-ui/FrameTiming-class.html . I haven't looked to see if they are retaining the events, because without the timeline its going to be difficult to confirm if its actually working or not.
Though most of our important tests are not e2e

Glorious:
https://flutter-flutter-perf.skia.org/e/?queries=device_type%3DPixel_7_Pro%26sub_result%3D90th_percentile_frame_rasterizer_time_millis%26sub_result%3D99th_percentile_frame_rasterizer_time_millis%26sub_result%3Daverage_frame_rasterizer_time_millis%26sub_result%3Dworst_frame_rasterizer_time_millis%26test%3Dcomplex_layout_scroll_perf_impeller__timeline_summary&selected=commit%3D39340%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253DPixel_7_Pro%252Cdevice_version%253Dnone%252Chost_type%253Dlinux%252Csub_result%253Dworst_frame_rasterizer_time_millis%252Ctest%253Dcomplex_layout_scroll_perf_impeller__timeline_summary%252C


Fixed Issues around setTimeTo() in the testing Utils:

Tonight @failfmi (https://github.com/failfmi) reported to me that there were bugs in the utils.setTimeTo()
After some investigation, I found that this is indeed the cases.
There were 2 issues in latestTimestamp() that is being used in setTimeTo() and cuased it to not work at all.
One of them is a missing dependency to "promisify", which is no longer required.
The second one trying to use "web3" instead of ethers.js
Note; The timeTravel() functionality was not being affected by this bugs and was working correctly
Again Thanks @failfmi
ChangeLog:

Fixed Issues with latestTimestamp()

No longer using the missing "promisify" dependency
Using the Provider to get the Block information that is needed

Removed Moment.js as it was causing problems in some cases.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #104   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          17     17
  Lines         309    309
=====================================
  Hits          309    309

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 7e7fef2...0302470. Read the comment docs.


plantcv extractor code integration

Need Rob's help to get dockerfile part and extractor source code into the two code repos on opensource.ncsa.illinois.edu

@yanliu-chn does this duplicate #10?

I don't see any overlapping. #10 is to define statement of work.

@yanliu-chn sorry wrong repository. I meant - is this a duplicate of #13


Update dependency express to v4.19.2 [SECURITY]

This PR contains the following updates:

Package
Type
Update
Change

express (source)
dependencies
minor
4.18.2 -> 4.19.2

GitHub Vulnerability Alerts
CVE-2024-29041
Impact
Versions of Express.js prior to 4.19.2 and pre-release alpha and beta versions before 5.0.0-beta.3 are affected by an open redirect vulnerability using malformed URLs.
When a user of Express performs a redirect using a user-provided URL Express performs an encode using encodeurl on the contents before passing it to the location header. This can cause malformed URLs to be evaluated in unexpected ways by common redirect allow list implementations in Express applications, leading to an Open Redirect via bypass of a properly implemented allow list.
The main method impacted is res.location() but this is also called from within res.redirect().
Patches
https://github.com/expressjs/express/commit/0867302ddbde0e9463d0564fea5861feb708c2dd
https://github.com/expressjs/express/commit/0b746953c4bd8e377123527db11f9cd866e39f94
An initial fix went out with<EMAIL_ADDRESS>we then patched a feature regression in 4.19.1 and added improved handling for the bypass in 4.19.2.
Workarounds
The fix for this involves pre-parsing the url string with either require('node:url').parse or new URL. These are steps you can take on your own before passing the user input string to res.location or res.redirect.
References
https://github.com/expressjs/express/pull/5539
https://github.com/koajs/koa/issues/1800
https://expressjs.com/en/4x/api.html#res.location

Release Notes

expressjs/express (express)
v4.19.2
Compare Source
==========

Improved fix for open redirect allow list bypass

v4.19.1
Compare Source
==========

Allow passing non-strings to res.location with new encoding handling checks

v4.19.0
Compare Source
==========

Prevent open redirect allow list bypass due to encodeurl
deps<EMAIL_ADDRESS>
v4.18.3
Compare Source
==========

Fix routing requests without method
deps<EMAIL_ADDRESS>
Fix strict json error message on Node.js 19+
deps<EMAIL_ADDRESS>deps<EMAIL_ADDRESS>

deps<EMAIL_ADDRESS>
Add partitioned option

Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Self-Hosted Renovate Bot. Find all logs here.

 You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.
If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.


Added pre-commit hook for local pylint checks

Will run pylint locally to speed up development cycles.

Coverage remained the same at 70.367% when pulling 450b6abe16c5869194c7fef44d00b99d33a23130 on felixbb:pylint-precommit into 7f90499af4342404309dce123fa518b10bbdc479 on GoogleCloudPlatform:master.

Coverage remained the same at 70.367% when pulling 972b40c280dfabc9b4902cb632b9f92054aea74f on felixbb:pylint-precommit into 7f90499af4342404309dce123fa518b10bbdc479 on GoogleCloudPlatform:master.

Adding cla: yes label, as the PR author is a googler at the time of this PR was created.


Accidental clashing with admin username and imported user

If I were to deselect this, and decided to import a huge DB, there's no guarantee that I might not accidentally clobber somebody else's posts and render them as a guest. Unless I'm reading this wrong?

If you think the admin should do a check on MySQL etc first for an existing username then that's fair enough to close, just thought I'd bring it up

well, yea, the thing is each adaptor would need to provide an interface to check for the existing. Since each MySQL schema is different. I am not saying it's not doable, I think it's OK to leave some of this initial leg work for the main Admin to decide on pre-import.
Another thing I could do is check EACH username on creation, if it clashes with the admin uid=1, then make the switch, and transfer each post/topic to the uid=1 - in another words, behave like this checkbox is ALWAYS checked, but let the import process detect what is the username in question.
leave it open, I think I can make it simpler

closing this one in favor of its superset https://github.com/akhoury/nodebb-plugin-import/issues/144


How does JSON work?

Looking at the tests I see the _df and _v fields.
Is this really what we want users to be seeing in their genesis files and over RPC?
Can we get the old format with type and value back ?

@ebuchman
"_df" are the disambiguation/disfix bytes that are necessary when we encode an interface with methods
"_v" are the bytes of the underlying type
They are used later on while disambiguating to a specific type.


Revisit candidates feature

Need to decide whether it's worth keeping and if we can make improvements with the data we have.

We want to get to a point where you can input your address and out pops a list of your candidates and ballot questions.  @robkorobkin did some work figuring out how to replicate the state's district lookup tool in this site: http://groundgamer.org/
Can we replicate this on Maine Ballot?
Details from Rob about what he did below:
Nothing's minified, and there are comments and variable / function names that actually make sense, so whoever's coding for you should hopefully have an okay time reading it?
If you're curious how I handle going from an address to identifying the legislative district for that address, here's the technobabble:
So, the first thing I did was get the GIS lat/lon boundary points of each legislative region out of the State's GIS archive, which I then wrote a script to convert to JSON:
http://groundgamer.org/data/turfs/senate_districts.js
http://groundgamer.org/data/turfs/house_districts.js
For data files, they're actually not that hard to read. Just a bunch of (lat,long) coordinates that pin out the boundaries of each legislative district.
Then, since I now had the districts as JSON, it wasn't all that hard to feed them into the Google Maps JS SDK to create the district overlay polygons that you see when you load the app.
The UI for the app contains a little form that takes an address, and then pings it to Google's geocode API, which spits back the lat/lon of the target address:
https://maps.googleapis.com/maps/api/geocode/json?address=85 Fessenden St, Portland, ME 04103&key=AIzaSyDxvSHxYEcCAseWokSJ4HyTE0g9xA0IH0w
Then, this is where the magic happens, there's a little javascript function that iterates through the list of displayed polygons to see if each polygon contains the specified location. Ie: it goes through all the districts (which are now loaded onto the map) and checks to see if your address (which you just got back from the API) is contained within it.
--
Hopefully this won't be too hard for you guys to implement into your thing.
Basically all you should need to do so is:

Those JSON files that lay out the districts (takes some string manipulation to load them into RAM).

A way to get the lat/lon of the point you're looking for. That api endpoint above is super useful for all sorts of stuff.

And then a function that can take a polygon and a point (address) and can see if the point is in the polygon (legislative district) or not. The GoogleMaps JS SDK offers this as a global static utility function. But I mean, people have been trying to do that since Euclid was born in 365 BCE, there's got to be a bunch of libraries out there that can do that.

--
Hope this helps.
All the stuff for GroundGamer.org is here:
https://github.com/OpenMaine/GroundGamer_maine

More from Rob:
Now that I think about it, Google or somebody probably just has an endpoint now that you can submit an address to and it’ll send back all the political district data for that address as some sort of big JSON dump.
That’s probably what you actually want.
It’s a fun dataset to have the boundaries of all the legislative districts in the state, like I’m working with here, and you obviously need it if you want to map out all the districts on a single map, etc. But if that’s not what you’re trying to do, that’s some serious overkill. It’s effectively drawing a detailed map of the state before you can find out about a single place on that map.
Just ping this:
https://developers.google.com/civic-information

This is the spreadsheet we use for local websites:
https://docs.google.com/spreadsheets/d/1dk58MD0qBAM37BDOZwKIz10hp5AARAIX8u_qvuDnYaI/edit?usp=sharing
And candidates:
https://docs.google.com/spreadsheets/d/14RapVz5_AlGRza-MsSzzu6cOQRIX_oSu-mcNQy8ytyo/edit?usp=sharing

@mfras3r started working on this, if anyone wants to pick up where he left off.
https://github.com/mfras3r/maineballot-sandbox

There is a spreadsheet of candidates for the June election, if anyone wants to play around with it.
https://www.maine.gov/sos/cec/elec/upcoming/index.html


Support for Service Worker Life Cycle Events

Hi
Support for events notifying changes to the state of a Service Worker is not consistent across browsers, eg https://github.com/Microsoft/ChakraCore/issues/5815
Please consider adding support for the following:

onupdatefound
waiting
installing
active

The last two appear to be supported across browsers, but not the first two.
Thanks!

Not sure if this is too granular but ServiceWorkerRegistration.update is also part of the life cycle.


CLN: blocks, not series, should contain logic for arithmetic

See discussion here: https://github.com/pydata/pandas/pull/9848#discussion_r28181084
This would likely help clean up some of the Series/DataFrame discrepancies in arithmetic operations (mostly for datetime types).

Would this also help performance materially, if DataFrame ops could iterate over Blocks rather than  Columns?
ref https://github.com/pydata/pandas/issues/11623, https://github.com/pydata/pandas/pull/11618

@maximilianr most things are already dispatched already by blocks.

Ah, fair, cheers. The ones that are applied across columns (which happen to have been the ones I've been using recently), seem to only be quantile & round.
(There are others on the DataFrame object such as rank, but don't iterate over columns in python)

yeh round is almost a display thing so doesn't really count (and could be daily broadcast)
quantile is bad impl ATM

I could do a PR for quantile if it's not too complex - what should that look like? Could it go straight to np.nanpercentile [link]?
Looking at the current code, it's doing a lot though.


Add Maintainer

@tylerb Can I be added to this as a maintainer, seems some PR's are stale

Certainly. Thanks for volunteering!

@tylerb Thank u sir, writing a Gitlab Provider


az generate

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

az generate

Any context?

Hi @haroldrandom , thank you. It's for onboarding AZ_DESKTOPVIRTUALIZATION https://dev.azure.com/azure-mgmt-ex/Onboarding/_boards/board/t/Onboarding Team/Features/?workitem=901.
Please hold review for this PR, let me check the pipeline errors first.

The test test_windows_virtual_desktop  failed, you should upload recording file otherwise CI would ask you to login because CI run test on playbck mode.

Close this PR since the extension name is changed in the speclet, so the whole extension file tree is changed.
Will start another PR for DESKTOPVIRTUALIZATION


Fixed-form highlight: support \t at start of line

In fixed-form Fortran, \t at the start of a line is the same as 6 white-spaces, which is supported by this modification.

I would appreciate this change too!


bump package version to libcephfs2

I'm seeing some teuthology failures when trying to install ceph packages, such as this on centos (full teuthology.log):
Error: Package: 1:ceph-common-11.0.2-2242.gbfb49aa.el7.x86_64 (ceph)
           Requires: libcephfs2 = 1:11.0.2-2242.gbfb49aa.el7
           Installed: 1:libcephfs2-11.0.2-2336.g27f6b03.el7.x86_64 (@ceph)
               libcephfs2 = 1:11.0.2-2336.g27f6b03.el7
           Available: 1:libcephfs2-11.0.2-2242.gbfb49aa.el7.x86_64 (ceph)
               libcephfs2 = 1:11.0.2-2242.gbfb49aa.el7

It appears that the existing package for libcephfs2 was not cleaned up by the ceph-ansible's Ensure ceph packages are not present task, which is referring to this package as libcephfs1.

In terms of installation: "yum install ceph-common" should pull in libcephfs1 or libcephfs2, so I don't think we want Ansible to try to install either one explicitly.
In terms of cleanup: I don't see an issue with ceph-ansible ensuring that both libcephfs1 and libcephfs2 are absent from a system.

In terms of installation: "yum install ceph-common" should pull in libcephfs1 or libcephfs2, so I don't think we want Ansible to try to install either one explicitly.

the comments in roles/ceph-common/defaults/main.yml suggest that libcephfs1 was there to make sure it wasn't skipped on upgrades. i guess we should either change this to libcephfs2, or remove libcephfs1 from the list. this part should be unrelated to the teuthology failures, so i don't mind either way

In terms of cleanup: I don't see an issue with ceph-ansible ensuring that both libcephfs1 and libcephfs2 are absent from a system.

okay, it makes sense to leave libcephfs1 in that list to be safe

there to make sure it wasn't skipped on upgrades.

Good point. In Hammer's /debian/control, ceph-common does depend on python-cephfs (= ${binary:Version}), but python-cephfs does not depend on the exact version of libcephfs1. So this is needed in Hammer, but not in Jewel or newer.
If we're adding support for Kraken now, I think it's time to drop Hammer support. The estimated EOL date was last month.

updated to preserve libcephfs1 in the list of packages for purge-cluster, and removed the old dependency on libcephfs1 from debian_ceph_packages

jenkins test ansible2.2-xenial_cluster


BUG-111172 stackViewResponse instead of stackResponse: performance improvement for fetching list of stacks in V3

@keyki pls review

UI is almost done, will be tested with the backend changes tomorrow...


How to run the benchmark tests

Hi,
I am using Ubuntu system. Should I put the osqp_benchmarks to some specific location? Because when I tried to run run_benchmark_problems.py, the terminal shows ImportError: No module named osqp.

This is just the benchmarks repository.   You still need to actually install osqp.   See here.

Thank you so much for your quick response. Actually, I installed osqp but not using pip install. I build and make install, and can find them in /usr/local/...

Are you now able to run the benchmarks?   If not, are you able to solve an example problem in python like those shown in the OSQP interface documentation pages?

I figured it out. Thanks.


objcopy: copy file, section, and symbol flags

Also a couple of COFF write fixes.
Fixes #159, fixes #160
WIP: there's probably more non-COFF flags that still need to be copied, but probably worth testing if it really does fix #159, cc @jayvdb

Updated to handle more ELF/Mach-O flags (e.g. you can set RWX sections for ELF now).

I'll test it this weekend.

#159 is fixed, both<EMAIL_ADDRESS>and "string'"<EMAIL_ADDRESS>in the linking side of things.  I haven't run the Python test suites yet to stress test the resulting binaries, but with this fix I have bigger fish to fry and the hacks in https://github.com/indygreg/PyOxidizer/pull/192 are no longer needed.  Thanks so much.


Default behavior of json generation is likely more verbose than users expect

We currently respect JSON Schema's semantics around the additionalProperties keyword; i.e. leaving it unset is interpreted as "any property not specified by the properties keyword is (1) allowed and (2) has no restrictions on its value (other than being valid JSON)".
These semantics are useful (see https://github.com/guidance-ai/guidance/issues/887), and I think we should continue respecting them.
That being said, I also think that the majority of our users will expect the LLM to only produce the properties that were explicitly requested. Anything "extra" costs the user time and money, and it will likely be thrown away.
I recommend the following solution:

Recommend that all users use the pydantic interface (passing a BaseModel subclass to the json generation function) UNLESS they want the extra fine-grained control that directly passing a JSON object provides.
Write a custom BaseModel.model_json_schema implementation that sets additionalProperties to False and use it to convert the BaseModel to a JSON schema we'll generate against.

I feel far more comfortable being "opinionated" when our users use the high-level pydantic interface rather than the low-level JSON interface.
Additional notes:

currently users CAN get this behavior from pydantic if they add model_config = ConfigDict(extra="forbid") to their BaseModel
extra is allowed to take on the following values: "ignore" (default), "allow", "forbid"
when extra is "ignore", any additional properties will be discarded when validating an instance, while "allow" will propagate their values to the constructed instance
it should be safe to coerce "ignore" to "forbid" since we know anything extra is going to be discarded anyway

@JC1DA @Harsha-Nori ping for visibility

I think of json as a bit of a "higher level" guidance function (e.g. in contrast with select), and therefore think it's OK to have reasonable but configurable defaults across both the high-level pydantic and slightly lower-level "JSON schema" interfaces.
We've chatted on this, but to continue the discussion openly, my gut feel is that some well-named kwarg on guidance.json that sets the "strict" or "ignore" style behavior is the right thing to do, and let users toggle it to match "true" json schema validation semantics maybe? I agree with your assessment that most people would be surprised to receive non-specified keys back from their constrained schema generation, so we should plan on making that opt-in. Not quite sure on the arg naming yet.


Crash on adding widget

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.22621.1778
Other software
OS Build Version: 10.0.22621.1778.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.16
Steps to reproduce the bug
Add a widget to the Dashboard
Expected result
That it will let me add a widget to my DashBoard
Actual result
Some times it crashes
Included System Information
CPU: AMD Ryzen 5 3600X 6-Core Processor
Physical Memory: 15.94GB (4.57GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

Duplicate of #745


Adding language that clarifies complaints that will not be acted upon

In the Code of Conduct created by Geek Feminism, which is currently considered a community standard, it addresses which issues will not be addressed. This list adds a sense of safety to marginalized people, like myself, knowing we won't be written up for asking not to be harassed. The below list is list of "tools" our oppressors often use against us, and under the current Open COC, we could get in trouble for not liking it.
The Geek Feminism community prioritizes marginalized people’s safety over privileged people’s comfort. The Geek Feminism Anti-Abuse Team will not act on complaints regarding:
‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’ (because these things don’t exist)
Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.”
Refusal to explain or debate social justice concepts
Communicating in a ‘tone’ you don’t find congenial
Criticizing racist, sexist, cissexist, or otherwise oppressive behavior or assumptions

Thanks for your feedback, we are working on part of this in this PR:
https://github.com/todogroup/opencodeofconduct/pull/24
We are in the process of collecting feedback from initially launching this and will incorporate changes in the coming weeks based on community feedback.

I am looking at the commit and I do not see how the commit in that PR addresses this issue. It links to GF, and clarifies that the definition of harassment comes from GF, but does not address the point about complaints made with the intent to silence marganilized people.

If you have suggestions on text to add, change or modify, please submit something as a discussion point. PRs are generally the best way to help with this.

No. The work of writing concise, enforceable Codes of Conduct that truly uphold the safety of marginalized people over the comfort of bigots has already been done. You can find this at GeekFeminism, Contributor Covenant,and Citizens Code of Conduct. We, as a community, have already created and set these standards. We have been working hard to try to find a way to collaborate with GitHub, major and minor conferences, meet ups, and slack channels to create a safe community in which EVERYONE feels comfortable and safe contributing. We are not doing this work AGAIN for the benefit of the corporate members of TODO Group. Doing so would REMOVE us from our YEARS of work, it would be doing UNPAID labor for group of start ups and companies, and not even getting the cheap compensation of "exposure."
You want to write a GOOD code of conduct? You do it yourself. I posted a suggestion. That is the amount of free labor you get out of me. Your other option: Work WITH Geek Feminism, Coraline Ehmke, and other community members to implement an easy CoC feature on Github. Instead of reinventing this CoC wheel, add a drop down box to Github that would let people choose (much like they choose from multiple licenses) if they would like GeekFeminism, Contributor Covenant, or Citizen's Code of Conduct.

This issue provides little value and is with a clear goal of emphasizing goals of one particular community, which is in a direct conflict to the ultimate goal of this project - to build a culture of respect without discrimination and with culture of equality across communities. Suggestion made in this issue promotes none of that, as it directly emphasizes rights of one group above another and demotes discussion and reasoning by preventing contest of the issues by explicitly banning different opinions.
In addition to that, the last comment of the author is rude, not constructive and provides no value to the issue. If you have something to contribute, do so. If not, this issue has no future.
As a side note, "community standard", as you said, is yet to become one. At this point I don't see that it has much influence outside the group of origin, nor is it widely accepted.

In addition to that, the last comment of the author is rude, not constructive and provides no value to the issue. If you have something to contribute, do so. If not, this issue has no future.

Likewise, your comments are dismissive as well. I don't think the tone policing is necessary. It's derailing and doesn't address the actual points made.

Instead of reinventing this CoC wheel, add a drop down box to Github that would let people choose (much like they choose from multiple licenses) if they would like GeekFeminism, Contributor Covenant, or Citizen's Code of Conduct.

@jdax I personally really like this idea. It's very much in the spirit of the license picker (which I was involved with). I raised your suggestion with others at GitHub who are in a better position to give it due consideration. I can't make promises since I don't work on the teams that own this area of the site, but your suggestion has been heard. Thanks!

Likewise, your comments are dismissive as well. I don't think the tone policing is necessary. It's derailing and doesn't address the actual points made.

Taking a sentence out of context and declaring it tone argument, completely ignoring everything else stated in the comment is cherry picking and abuse of the tone argument. My comment contains 4 paragraphs - please, consider all of them. Any comments regarding that are welcome.

jdax, this is all irrelevant to open source development.

This was added in #17


[Bug]: Inventory option does not list RDS instances

What happened?
running prowler with inventory option does not list RDS instances in the inventory output
How to reproduce it
Steps to reproduce the behavior:

What command are you running? ./prowler -i on AWS Cloudshell
Environment :I'm connected to an account that is a member of an organization
See error:  List of type of resources per service for AWS Account xxx -=-

-=- cloudformation service -=-
1 stack
2 stackset
-=- ec2 service -=-
3 instance
1 snapshot
5 vpc-endpoint
-=- events service -=-
1 rule
-=- iam service -=-
1 group
1 policy
17 role
1 user
-=- lambda service -=-
2 function
-=- ssm service -=-
4 document
Total resources found: 39
Expected behavior
A clear and concise description of what you expected to happen.
The RDS instances should be included in the inventory as they are covered by the checks.
Running  ./prowler -g rds can perform checks on RDS instances and shows existing ones
Screenshots or Logs
prowler -i

./prowler -g rds

From where are you running Prowler?
Resource: AWS CloudShell
OS: Linux/4.14.291-218.527.amzn2.x86_64
AWS-CLI Version [aws --version]: aws-cli/2.7.34 Python/3.9.11 Linux/4.14.291-218.527.amzn2.x86_64 exec-env/CloudShell exe/x86_64.amzn.2 prompt/off
Prowler Version [./prowler -V]: Prowler 2.11.0-21July2022
Shell and version: GNU bash, version 4.2.46(2)-release (x86_64-koji-linux-gnu) - Others:
Additional context
I understand that the inventory option is beta so that may be an expected behaviour

Generally speaking, RDS should be in scope as mentioned here https://github.com/prowler-cloud/prowler/discussions/1398

Hi @ldina the services covered by checks and by the quick inventory are not related because the latter is using the resourcegroupstaggingapi from AWS and at this moment it doesn't cover RDS. For that reason you are not seeing the RDS resources or some others because that API doesn't include all AWS services.
https://docs.aws.amazon.com/resourcegroupstagging/latest/APIReference/overview.html
Thanks!

@jfagoagas thanks for clarifying that the two options are relying on different APIs but it seems that the API you mention support it.
https://docs.aws.amazon.com/resourcegroupstagging/latest/APIReference/supported-services.html

From the user's perspective, it's confusing if the scope of the checks and of the quick inventory is different.

Yes @ldina my bad, this service covers RDS.
I'm testing it in our environment and the execution using ./prowler -i outputs the number of RDS resources.
Prowler runs the following command underneath, can you execute it and paste the output here?
aws resourcegroupstaggingapi get-resources --region<YOUR-REGION> --query ResourceTagMappingList[].ResourceARN --output json 2>&1)
Please redact sensitive information.
Thanks!

hi @jfagoagas , no worries
I run the command you provided and the result seems comparable to what I got from prowler. So it seems that is not specific to prowler, maybe permissions related or cloudshell specific?

Hi @ldina, do you have any SCPs restricting the usage of service?
I think you need to talk with your AWS support because for some reason the Resource Groups and Tagging API is not returning your RDS instance.
Thanks!

Hi @jfagoagas thanks for the suggestion, I looked in the Organization SCP and is disabled. I'll talk with the AWS support and I'll let you know.

@ldina we're closing this issue because there is no possible solution from our side. Feel free to reopen it if you need it.
Thanks for using Prowler!


Same classname applied in SSR

I have created my environment Next JS with styled component.

Some first time style appear not properly, after refresh only render correctly.
Same classname is appear different HTML tag.

So if it's appearing same classname total page will collapse

@vijayaganthF22 do you have a minimal github repo or codesandbox sample to reproduce this?

@koellcode @vijayaganthF22 I am also having this issue with SSR and rehydration in production mode (again no nextjs). Issue only occurs using SC 5.0

I'm having this issue using Next.js & SSR, and another issue that seems related too.

It seems to be unrelated as to whether the babel plugin has displayName set to true or false.
I've also noticed a similar mismatch in props I'm passing to a styled component:

Another thing I've noticed is that whenever the app hot reloads, the classes & props get re-applied correctly. That's unfortunately not very helpful in a production build, where this is the biggest pain point.
I'm sure this was not an issue pre-Styled-Components 5.0. Not very clear on when it started though. Any ideas on workarounds in the meantime? 🙏

Could this be related to NODE_ENV somehow? Seeing this issue if I set NODE_ENV to production. However, if I change it to anything else, it seems to render correctly.

Bumping as we are seeing this exact same issue, but we are still on SC 4.4.1 - no nextjs either.
Like @bozskejkaja we see this when using conditional checks around components and only when it hydrates - the initial server render is correct. Has anybody found the root cause for this?
Changing the NODE_ENV is unfortunately a complicated workaround for us.

@inestavares I only had the issue on SC5+ reverting to SC 4.4.1 didnt show the issue. Unfortunately I haven't had the time to attempt to create a failing test case

Having the same issue but specifically in non-dev environments. Local machines have no collisions when running dev and prod builds but as soon as it hits our testing environment we have this issue. Tried replicating the testing environment as much as possible on our machines but can't get the error to occur.

I have the same problem. The problem starts to appear with version 5.0.0-rc.3
This works fine on version 5.0.0-rc.2 and below.

I have same issue.
version is 5.1.1 and only happen with NODE_ENV=production.
Is there a workaround other than changing NODE_ENV?

+1 Same here with 5.1.0
For me version 5.0.0-rc.2 still have this issue. Had to downgrade to 4.4.1 as @brendanmoore and @inestavares said to make this work.
It seems that could be something related to componentIds and parentIds generation when style collection occurs server side upon a different client hydration/render root component
Maybe from 4.4.1 to 5.1.1 something about the id generation went towards having the id calculated based on the component hierarchy instead of maybe a Native/DOM component perspective (guessing...)

FYI we downgraded because of this.

If you're using webpack-node-externals with an external library that has a peer-dependency on styled-components, you can try adding that library to allowlist (or whitelist in old versions) which then bundles the library for server builds and see if that fixes the issue.

See also:
https://github.com/styled-components/babel-plugin-styled-components/issues/277
https://github.com/styled-components/babel-plugin-styled-components/issues/291

We have same issue. https://github.com/styled-components/styled-components/issues/3230

Any updates on this? We're also stuck on 4.x.x because of this issue. As mention above: happens when building with NODE_ENV=production.

same issue.only happen when NODE_ENV=production

Hi @all,
I've stuck into the same problem and analysed it.
I think, this is the problem:
https://github.com/styled-components/styled-components/blob/a8507e6ac7267e3d74b08b457ced58d182b49515/packages/styled-components/src/models/ComponentStyle.js#L69
After manually adding this line to the production build, all errors are resolved.
Maybe I've a different scenario because I using my own defined styled component Mixin/HOC like this:
type VisibleAttrs = { visible?: boolean };
export const Visible = <C extends AnyStyledComponent>(
    element: C,
): StyledComponent<
    StyledComponentInnerComponent<C>,
    DefaultTheme,
    StyledComponentInnerOtherProps<C> & VisibleAttrs,
    StyledComponentInnerAttrs<C>
> => styled(element).attrs<VisibleAttrs>((props) => ({
    'aria-hidden': props.visible === false,
}))<VisibleAttrs>`
    ${(props) => {
        return (
            props.visible === false &&
            css`
                display: none;
            `
        );
    }}
`;

It only adds display:none and aria-hidden if props.visible === false.
But it is used on many styled components such as:
export const SCContent = Visible(styled.div`
    display: grid;
    grid-row: 3;
    padding: 2rem;
`);

or
export const SCContainer = Visible(styled.div``);

This results in
class="Contentcss__SCContent-wlss8h-0 Visiblemixin__Visible-sc-4z0g1d-0 KIzlc"

or
class="Containercss__SCContainer-1r93u80-0 Visiblemixin__Visible-sc-4z0g1d-0 KIzlc

The visible classNames are generated correctly because I'am using the Visible Mixin styled component and the original component based styled component, but the effective hash is not updated. It's always based on the outer styled component and this is the Visible Mixin and is only updated in a none production environment.

Any updates on this? We're also stuck on 4.x.x because of this issue. As mention above: happens when building with NODE_ENV=production.

No comments / hints from the developers?

is there any workaround apart from downgrading to v4?

is there any workaround apart from downgrading to v4?

Might remember wrong but think the problem disappeared when displayName was set to true in babel config (see https://styled-components.com/docs/tooling#better-debugging) ...did not investigate so thoroughly (it was not an option for prod in my case).

Any updates on this? With SC v5, I want to make use of very good RTL support, but this issue is restricting me. Just to update @ludwighogstrom and @idDemonov - both solutions described by you do not work.
What works? - you have to downgrade to 4.4.1
And with the downgrade, I cannot make use of RTL support with stylis-rtl-plugin

Same here. We are now making use of shouldForwardProp (for AMP compatibility) and so can’t easily downgrade but we are encouraging this issue randomly.

Same problem here, only happens on ssr. The only way to temporary mitigate it is to use another HTML element, like article instead of div. Tried to resolve it on library level, no luck so far. But it's a real deal breaker and big problem.

Same problem here, only happens on ssr. The only way to temporary mitigate it is to use another HTML element, like article instead of div. Tried to resolve it on library level, no luck so far. But it's a real deal breaker and big problem.

Same problem here, only happens on ssr. The only way to temporary mitigate it is to use another HTML element, like article instead of div. Tried to resolve it on library level, no luck so far. But it's a real deal breaker and big problem.

Confirmed this works, but agree this is a big issue. Is there any active development being done on a solution?

Same problem here, only happens on ssr. The only way to temporary mitigate it is to use another HTML element, like article instead of div. Tried to resolve it on library level, no luck so far. But it's a real deal breaker and big problem.

Confirmed this works, but agree this is a big issue. Is there any active development being done on a solution?

Any news about this problem?

Any news about this problem?

Going to add to the pile. This issue has prevented me from upgraded all our stacks and design system from v4.4.1 to v5. Now with v6 coming out, I fear we'll be stuck left behind and forced to switch to a new library all because of something that seems small, but isn't.
It fails on:

Next.js 10.0.5
Styled-Components 5.2.1
React 17.0.1

It succeeds on:

Next.js 10.0.5
Styled-Components 4.4.1
React 17.0.1

This issue only occurs on production, thus making it even worse to try and debug.

Going to add to the pile. This issue has prevented me from upgraded all our stacks and design system from v4.4.1 to v5. Now with v6 coming out, I fear we'll be stuck left behind and forced to switch to a new library all because of something that seems small, but isn't.
It fails on:

Next.js 10.0.5
Styled-Components 5.2.1
React 17.0.1

It succeeds on:

Next.js 10.0.5
Styled-Components 4.4.1
React 17.0.1

This issue only occurs on production, thus making it even worse to try and debug.

Last I heard @kitten need more details and investigation related to this.
https://github.com/styled-components/styled-components/issues/3230#issuecomment-681841726

Last I heard @kitten need more details and investigation related to this.
https://github.com/styled-components/styled-components/issues/3230#issuecomment-681841726

Having the same issue with an internal library and the projects using it.
I understand we are providing little to no details but it is extremely difficult to debug since it only happens in production after building.

I have the same issue with nextJS.
fails on:

Library
Version

Next.js
10.0.6

Styled-Components
5.2.1

React
17.0.1

works on:

Library
Version

Next.js
10.0.6

Styled-Components
4.4.1

React
17.0.1

Only happens on production

This seems to happen to our project a lot when we conditionally render components. Like when I have the following inside a container, the components after will have seemingly randomly wrong class names.
 {boolean && (


RuntimeError: The size of tensor a (151936) must match the size of tensor b (152064) at non-singleton dimension 1

when I try train minillm from qwen14b to  qwen1.5b, I encountered the following problem
`[rank0]: Traceback (most recent call last):
[rank0]:   File "/miniLLM/LMOps-main/minillm/train_minillm.py", line 103, in
[rank0]:     main()
[rank0]:   File "/miniLLM/LMOps-main/minillm/train_minillm.py", line 89, in main
[rank0]:     train(
[rank0]:   File "/miniLLM/LMOps-main/minillm/minillm/init.py", line 37, in train
[rank0]:     sampler.run_sample(args.num_rollouts_per_device)
[rank0]:   File "/miniLLM/LMOps-main/minillm/minillm/sampler.py", line 70, in run_sample
[rank0]:     gen_out = self.trainer.generate(**batch, return_dict_in_generate=True, mode=mode, teacher_mixed_sample=(self.args.teacher_mixed_alpha is not None), output_scores=True)
[rank0]:   File "/miniLLM/LMOps-main/minillm/minillm/trainer.py", line 618, in generate
[rank0]:     gen = model.generate(
[rank0]:   File "/miniLLM/LMOps-main/minillm/minillm/model.py", line 21, in generate
[rank0]:     return self.base_model.generate(**x)
[rank0]:   File "/usr/local/lib/python3.9/dist-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:   File "/miniLLM/LMOps-main/minillm/transformers/src/transformers/generation/utils.py", line 2229, in generate
[rank0]:     result = self._sample(
[rank0]:   File "/miniLLM/LMOps-main/minillm/transformers/src/transformers/generation/utils.py", line 3331, in _sample
[rank0]:     probs = (1 - mix_in_alpha) * probs + mix_in_alpha * m_probs
[rank0]: RuntimeError: The size of tensor a (151936) must match the size of tensor b (152064) at non-singleton dimension 1
E1212 22:55:56.524920<PHONE_NUMBER>72544 torch/distributed/elastic/multiprocessing/api.py:826] failed (exitcode: 1) local_rank: 0 (pid: 739442) of binary: /usr/bin/python3
Traceback (most recent call last):
File "/usr/local/bin/torchrun", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.9/dist-packages/torch/distributed/elastic/multiprocessing/errors/init.py", line 347, in wrapper
return f(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/torch/distributed/run.py", line 879, in main
run(args)
File "/usr/local/lib/python3.9/dist-packages/torch/distributed/run.py", line 870, in run
elastic_launch(
File "/usr/local/lib/python3.9/dist-packages/torch/distributed/launcher/api.py", line 132, in call
return launch_agent(self._config, self._entrypoint, list(args))
File "/usr/local/lib/python3.9/dist-packages/torch/distributed/launcher/api.py", line 263, in launch_agent
raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
/miniLLM/LMOps-main/minillm/train_minillm.py FAILED`

It seems that qwen14b and qwen1.5b use different vocabulary sizes and KD methods generally requires the teacher and student models to share the same vocabulary.
However, the vocabulary difference of different-sized qwen is just for padding. Therefore, cutting the larger vocabulary to the smaller one or padding the smaller to the larger one would be fine.

@t1101675 how to padding the smaller to the larger

@t1101675 I need to modify the size, re-train SFT, and then perform distillation?

@t1101675 I need to modify the size, re-train SFT, and then perform distillation?

Mostly likely. Besides, I think the SFT re-training does not need to be extensive to adapt the model for a few padding tokens.

You probably need to resize the embeddings of the student model after changing config.json.


DBZ-6899 Refactor Oracle streamings metrics

https://issues.redhat.com/browse/DBZ-6899

Hi @jpechane, I took a look at their implementation, and while there are some conceptual overlaps they also have this concept of QuantileMeter associated with each Statistics instance that tracks this "histogram" data, and each instance starts its own thread (about 11 in total) per Spanner connector.
Overall I think we can refactor this eventually, but I think that's likely better to coordinate with Nancy to understand the implications of doing that to make sure that both Oracle's needs and Google's are aligned when doing that refactor.  I have logged https://issues.redhat.com/browse/DBZ-6898.

Applied to main (=2.5).


Change the name with Tibco requirement

#62
Have changed the name with Tibco requirement, but the icon part is waiting for Tibco's resource.

About the description in package.json I looked into Tibcos examples and found that they just name it "" (see picture).
I noticed that there are some changes in index.js, percentage.js, stackedBars.js and html that are probably from an earlier version of the code. You need to change that to what we have in main. When I ran this code we're not able to render the chart.

I have fixed it now


iOS: Feeds list account rows should be normal rows

It should be the same as in Mail. A row for an account is a regular row. Has chevron, is same height as other rows. Doesn’t float.

I think I got it right this time.  Let me know if it wasn't what you were expecting.


[explore]time picker select dropdown and scroll

🗒this issue was not seen when the PR was last tested and merged. it might caused by conflicts
https://user-images.githubusercontent.com/67837651/102680719-bcd23480-416f-11eb-87e6-e2862790a659.mov
due to the conflicts with recent refactoring work, new time picker select dropdown is cutoff, scroll bar is not showing.
(not caused by the original PR)

@junlincc
I would use Antd Popover to replace the original Modal, refactor DateFilterControl, and maybe avoid this problem.

@zhaoyongjie thanks for fix, going forward please link PR to issue so that they can close automatically when PR is merged

@zhaoyongjie thanks for fix, going forward please link PR to issue so that they can close automatically when PR is merged

got it. ^_^
On Tue, Jan 5, 2021 at 11:36 PM Junlin Chen<EMAIL_ADDRESS>wrote:

[image: Screen Shot 2021-01-05 at 7 30 04 AM]
https://user-images.githubusercontent.com/67837651/103665700-94e12000-4f28-11eb-9aff-87e19d7f71ad.png
@zhaoyongjie https://github.com/zhaoyongjie thanks for fix, going
forward please link PR to issue so that they can close automatically when
PR is merged
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-superset/issues/12140#issuecomment-754712103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPMKUS5CYK5GJBQR4UC3KTSYMWZHANCNFSM4VB76UBQ
.

got it. ^_^
On Tue, Jan 5, 2021 at 11:36 PM Junlin Chen<EMAIL_ADDRESS>wrote:

[image: Screen Shot 2021-01-05 at 7 30 04 AM]
https://user-images.githubusercontent.com/67837651/103665700-94e12000-4f28-11eb-9aff-87e19d7f71ad.png
@zhaoyongjie https://github.com/zhaoyongjie thanks for fix, going
forward please link PR to issue so that they can close automatically when
PR is merged
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-superset/issues/12140#issuecomment-754712103,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPMKUS5CYK5GJBQR4UC3KTSYMWZHANCNFSM4VB76UBQ
.


Clarification on persistent file system access in browsers

When you talk about 'FileSystem access' in browsers, does this mean that the data is persistent? Through OPFS or another storage offered by browsers?

Context https://github.com/vincent-herlemont/native_db/issues/65

When you use the new Directory() constructor, it will create a temporary in-memory filesystem that is backed by a virtual_fs::mem_fs::FileSystem.
In #337, I'm adding a static Directory.fromBrowser() function which will create a Directory backed by the browser's FileSystem API. That means you'd be able to mount a directory backed by OPFS or the FileSystemDirectoryHandle you get from window.showDirectoryPicker().
That PR hasn't been merged yet, but that's mainly because we chose to implement the easier in-memory version first and add support for the FileSystem API after making @wasmer/sdk public.

Amazing work! Any indication when persistent OPFS will be available? This would all such high-demand applications like vector search in the browser by the very popular usearch library.


Add translation for Spanish

Expected time to finish: 1 week. I'll start working on it when I get a response to this issue.
Hello 👋.
I'm a native Spanish speaker who has previously contributed to the translation of other open-source projects from English to Spanish. I found this project and thought it was interesting (especially for me as Python is my main programming language!) so it'd be a pleasure working on the translation of this.
If you want this translation, please give me indications (if any) about the translation process.
Thank you in advance!

Hi @JoseDeFreitas
Thanks for considering translating this project :)
You can check out the existing translation issues to see how other contributors have done it https://github.com/satwikkansal/wtfpython/labels/translation
As long as you keep the example-ids (in the readme) intact, there shouldn't be much to worry about.

Alright! I'll start working on it then. Thank you @satwikkansal!

Hi @JoseDeFreitas , I would like to help on this. Is there any way I could join?

Hello @cajotafer!
See, I forked this repository (following the same thing the contributors for other languages did). This is my fork: https://github.com/JoseDeFreitas/wtfpython. I'm translating the text from the README file on the master branch (I'm at the line 708 and I skipped the "Table of Contents" section in order to translate that later so I can be more careful to match the titles/subtitles and the links).
I'd really like your help, so if you want you can open pull requests in there. Or, maybe better, I can give you collaborator access so you can work on it freely. Let me know any other thing. You can also contact me by my Twitter or my Discord (Jose#7947) for an easier conversation.


[PE-D][Tester C] Editing Color Palette in preferences.json Causes All Tags to Display as One Color

Users trying to modify the tag color palette by editing the preferences.json file are unable to achieve unique colors for different tags. After making changes, all tags show up in a single color, rather than each tag having a distinct color.
  "tagColors" : {
    "colors" : [ "#FFB3BA, #FFDFBA, #FFFFBA, #BAFFC9, #BAE1FF, #C1C8E4, #FFD1DC, #E2F0CB, #F4D4E0, #D4F4FA" ]
}

Labels: type.FunctionalityBug severity.High
original: iamdiluxedbutcooler/ped#27

Tester entered a single string instead of array of string


Chewy support for eager global ordinals?

I'd like to use "eager global ordinals" as documented here for ElasticSearch 5 (see section "Global ordinals" halfway down the page).
Does Chewy support this? I can't find anything in the docs and/or source code.

Hey, can you provide a usage example in pure ES requests?

@pyromaniac - It should just be the eager_global_ordinals property on keyword fields.
Example:
curl -X PUT "localhost:9200/my_existing_index/_mapping/my_existing_type" -H 'Content-Type: application/json' -d'
{
    "properties": {
        "test_field_2018_09_24": {
          "type":  "keyword",
          "eager_global_ordinals": true
        }
      }
    }
  }
}
'

So did you try to add it to a field definition? Like, field :test, type: 'keyword', eager_global_ordinals: true

Yes, that works. I did not know that chewy took arbitrary options.
Thanks for your help.


Issues with gnome apps

I recently changed my theme to Dracula in gnome 43 but the default gnome apps such as settings or Gnome-Control-Center and Nautilus wont apply the theme. On some threads it was mentioned that "copying the contents of gtk-4.0 folder from the theme folder to ~/.config/gtk-4.0 will fix the problem." And it did changed the theme but my minimize/maximize and close buttons are missing. And it is only in gnome apps others are fine
And if clicked on empty spaces where the buttons were supposed to be they will perform minimize/maximize or close action its just that they aren't visibly present

There is no buttons in upper left corner

But other apps as you can see have buttons present

Wow, I had no idea; I would like to help, but I am not a user of this platform! 😓
But there is a better place to share the same, which is the project repository, where you can talk to the theme maintainers.
✅ Clicking here, you can open an Issue on it.


[4rc1]Weird crash

Godot version
v4.0.rc1.official [8843d9ad3]
System information
Debian 11
Issue description
I have several projects that I'm used to open at same time (mostly two at same time - [client/server], [client/castle], ...)
And usually I have to set the language server into different ports because I use vscode as editor.
I did some porting from 3.5 into 4.0 so in my file system I have, for example, the client project folder into client folder for 4.0 while for the versione 3.5 of godot it is into Client folder.
The crash happen when I do some changes in vscode.
Godot close itself without any warnings/errors so I suppose its a crash.
I investigate in .local/share/godot/app_userdata/ to find some info in logs and I found this error
USER ERROR: Condition "_first != nullptr" is true.
   at: ~List (./core/templates/self_list.h:106)

The weird thing is I found it in the wrong folder. I was expecting to find it in client folder but it was into Client instead
Because it is a random issue I cannot give any MRP at this time. Sorry.
It happen in beta version too. I didn't report it before because I thought is was a problem related to beta stage.
Thanks
Steps to reproduce
Wel,l as stated is a random issue that happen when I work in vscode
Minimal reproduction project
na

Not much can be said from your logged error, it's just the end of the trace, not the root of the problem. Only live debugging would help there, or more specific steps to reproduce.

It happen in beta version too. I didn't report it before because I thought is was a problem related to beta stage.

Problems related to the beta stage are only going to be resolved during beta if they are reported. Otherwise they will simply remain problems, unsolved and still present.

Problems related to the beta stage are only going to be resolved during beta if they are reported. Otherwise they will simply remain problems, unsolved and still present.

Well its depends.
If the issue can be fixed during that stage it will be, otherwise it will be postponed to the next. It happen often.
Sure the early the issue will be reported the better is.. But this one is so weird that I was hoping to be related to other issues in beta stage.  Its not that I could give more details two months ago - also at that time I was not in the mood :)
It is still possible that is related because there are several issues in beta stage that are not yet fixed. So I think we can wait.


Provide 'Pass Through' Handling for Equation Link Handling

Provide an additional value for the args.eqnlink.style parameter such that no equation link handling is performed by this plugin. The suggestion was to use a value of "default" for this feature.
Reference: comment on DITA-OT issue 1774

Could this be addressed using the DITA OT '_template' XSL functionality instead?


docs: How to work with local packages

Resolves #269
Resolves #13 (inasmuch as there's nothing we can do aside from documenting a way; see https://github.com/srid/haskell-flake/issues/13#issuecomment-1468723328)
Related: https://github.com/srid/haskell-flake/issues/262#issuecomment-1996018310

Also adds a page to begin to document our default options:

https://community.flake.parts/haskell-flake/local
https://community.flake.parts/haskell-flake/defaults


Fix no args

Display help message when no arguments are passed.

Is this supposed to fix these errors:
wtpython on  fix-no-args via wtpython via 🐍 3.9.5
➜ wtpython -n
IndexError: list index out of range
──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
Stack Overflow Results:

1. Why does this iterative list-growing code give IndexError: list assignment index out of range?
https://stackoverflow.com/questions/5653533/why-does-this-iterative-list-growing-code-give-indexerror-list-assignment-index

2. IndexError: tuple index out of range when using py2exe
https://stackoverflow.com/questions/41578808/indexerror-tuple-index-out-of-range-when-using-py2exe

3. IndexError: too many indices for array
https://stackoverflow.com/questions/28036812/indexerror-too-many-indices-for-array

4. iloc giving 'IndexError: single positional indexer is out-of-bounds'
https://stackoverflow.com/questions/42739327/iloc-giving-indexerror-single-positional-indexer-is-out-of-bounds

5. IndexError: Python
https://stackoverflow.com/questions/52543529/indexerror-python

6. Python - IndexError
https://stackoverflow.com/questions/27695157/python-indexerror

7. Python : IndexError
https://stackoverflow.com/questions/49253986/python-indexerror

8. IndexError: tuple index out of range ----- Python
https://stackoverflow.com/questions/20296188/indexerror-tuple-index-out-of-range-python

When you call the app with no args, there is nothing in sys.argv and it throws an index error. So by default the app was searching for a solution to that. Now we shortcut it and just throw help if there are no args

@briancohan On the help page both -n and -c create errors which then are displayed in a list for -n or in the tui for -c if you don't pass any other args.

You should be checking if the second return value from parse_known_args is empty, not just if sys.argv is empty.
Additionally, I think we should also add some text at the end of the usage message telling the user to enter the script name / arguments after wtpython, since it's not really clear from the help message. This can be done with:
parser = argparse.ArgumentParser(epilog="wtpython acts as a substitute for python, you should also pass in the script name and command line args for it")

... Or something of the sort


HttpSink plugin functionality for #874.

Description
HttpSink plugin functionality for #874.
Issues Resolved
#874
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

What is the difference between this and #3036?

What is the difference between this and #3036?

@dlvenable This PR has access token changes and junit test cases, since 3036 PR is not merged yet, the code changes of PR 3036 is also there is in this PR

@dlvenable writeEvent() removed


OCPBUGS-11442: properly reconcile with user specified changes for in proxy configuration

What this PR does / why we need it:
Users are able to and directed to configure the cluster-wide proxy directly in the guest cluster when needing to setup local proxying in the guest cluster network: https://docs.openshift.com/container-platform/4.10/networking/enable-cluster-wide-proxy.html. Currently: even when the proxy configuration in the hosted cluster is nil: we are squashing all these changes and revoking what they are doing locally. This makes it impossible for them to configure the proxy within their network (they should not need to have to proxy these configurations to the hostedcluster resource each time and get it to propogate as that can be controlled by a separate entity like a managed cloud provider). This allows the user to create those changes and have them persist
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes # https://issues.redhat.com/projects/OCPBUGS/issues/OCPBUGS-11442
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/retitle OCPBUGS-11442: properly reconcile with user specified changes for in proxy configuration

/jira refresh

We need to decide if we authoritatively control the guest cluster Proxy config from the HC before we merge this.  If the HC is authoritative, the code is already doing the right thing i.e. stomping the spec.

@sjenning I agree: let's discuss that: I believe we need to still leave users of the guest clusters with proper permissions paths to do some of these operations: otherwise there is a large burden on managed service teams to continually provide wrapper APIs to modify and store resources associated with operations users within the cluster should be able to do

/hold
testing clear path of proxy configuration.

/unhold

Will now clear on a change to the hostedcluster Configuration:
Tylers-MacBook-Pro-2:armada-hypershift-operator tylerlisowski$ kubectl get proxy -o yaml
apiVersion: v1
items:
- apiVersion: config.openshift.io/v1
  kind: Proxy
  metadata:
    annotations:
      hypershift.io/hosted-cluster-proxy-config: "true"
    creationTimestamp: "2022-10-27T16:43:23Z"
    generation: 7
    labels:
      hypershift.io/managed: "true"
    name: cluster
    resourceVersion: "80896510"
    uid: 9d89d4b6-bf8a-4f31-837e-5108c13c4eb7
  spec:
    httpProxy: http://<IP_ADDRESS>:3128
    httpsProxy: http://<IP_ADDRESS>:3128
    readinessEndpoints:
    - https://github.com
    trustedCA:
      name: ""
  status: {}

Then when removed
- apiVersion: config.openshift.io/v1
  kind: Proxy
  metadata:
    creationTimestamp: "2022-10-27T16:43:23Z"
    generation: 8
    labels:
      hypershift.io/managed: "true"
    name: cluster
    resourceVersion: "80896791"
    uid: 9d89d4b6-bf8a-4f31-837e-5108c13c4eb7
  spec:
    trustedCA:
      name: ""
  status: {}

In addition: when stays nil: user can set what they need for the in cluster configuration (important for openshift builds of samples, etc)

/approve

/lgtm

/lgtm

/lgtm

/cherry-pick release-4.13

/cherry-pick release-4.12

/cherry-pick release-4.11


Make grpc_channel_create_call accept NULL for host

With recent URI target naming changes, it becomes difficult (if not impossible) for wrapped languages to determine the correct host string to pass to grpc_channel_create_call.
Make the following architectural change to the client_config/client_channel systems:

add a host field to grpc_client_config
allow resolvers to set it
make existing resolvers provide good host values based on input uri
stash the host field in client_channel.c somewhere
add it if no host is provided in initial metadata, add it based upon the value provided

During call creation, omit adding an authority header if host==NULL.

it becomes difficult (if not impossible) for wrapped languages to determine the correct host string to pass to grpc_channel_create_call

In which cases, if any, will the host argument to grpc_channel_call_create need to be something different than NULL?
Currently, if the client needs to override the SSL target name for testing, that name also needs to be passed as host to grpc_channel_call_create for the handshake to succeed. Will that still be the case after this change?

Ping.

Users will need to supply a host if:

the core cannot determine it from the target passed to create channel
(this is a pluggable system, so we don't know with certainty when this
would arise)
the user wants to access a different host than indicated by their target
string (ex: connect to database.google.com, access bigtable.google.com)

On Sat, Aug 1, 2015, 11:38 AM Jorge Canizales<EMAIL_ADDRESS>wrote:

Ping.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/2635#issuecomment-126944104.

Does one still have to pass the SSL target name override to grpc_channel_call_create as host, or can the core determine it from the channel args?
I assume the core can always determine the host for channels created using DNS addresses?

It looks like grpc_channel_call_create does not automatically pick up the SSL target name override. However, in any case where we need an SSL target name override, we can also pass the channel argument grpc.default_authority to avoid this problem.

Nice catch :) Craig, should the core do that automatically?

I don't think so.
Although related, one of these features is strictly for testing (the SSL
override), while the other is normal behavior.
On Mon, Aug 3, 2015 at 10:58 AM Jorge Canizales<EMAIL_ADDRESS>wrote:

Nice catch :) Craig, should the core do that automatically?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/2635#issuecomment-127350792.


Feature Request: Support for "resizable" property on individual items

I'm using angular-gridster to show widgets on a page (e.g. a widget for current time, one for a gauge etc.). Some widgets look terrible when resized (e.g. a clock looks good when square, but not when it's width is 6 and it's height is 1) and I'd like to disable resizing, or only allow diagonal resizing (so it stays square, but can be expanded and shrunk)
Adding "resizable" to the customItemMap does nothing, so I'm not able to set resizable properties on individual items, just all of the items (which I don't want).
Is it possible to add this feature in? I'd have a go myself, but I'm not au fait with the code yet

You should be able to set minSizeY maxSizeY and minSizeX maxSizeX to the same the size to disable able resizing.  This doesn't address the locked aspect ratio that you mention (diagonal resizing)

Disabling resize was an afterthought (I'm already locking the max and min sizes to prevent resizing, which works, except the drag hand still shows up), locked aspect ratio was more what I was after.
Ultimately, the user can see that the gauge or clock looks like crap if they resize the wrong way, and just not resize that way, but for that extra bit of UX goodness, only allowing certain resize directions (like you can set with the global options currently) would be ideal.


Set mobile title

This addition inserts title into the header on mobile devices along with a fix to the Header.ss file inside the ss.org project which will need to be tested together

@unclecheese is it possible to review this update?

@unclecheese can we get a review and merge


BUG: Not Responsive for small screens

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?

i want to work on this issue will make website responsive for all types of screens from mobile -  laptop
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Issue #406

Can I work on this

@rohit-yadavv Keep checking the status of #406 . If it isn't completed on time, it could be assigned to you.


Tab crashes if query is run while sorting a boolean column

I am able to reproduce regularly, sorting a large table by the values in a boolean column, and then clicking a run query while the loading circle is spinning.
Tab crashes and the error message:
'rowA[col]._.toLowerCase is not a function'

Storage Explorer Version: 1.11.0
Build Number: 20191105.2
Platform/OS: Windows 10
Architecture: x64

We haven't touched that code for a while.  This must be in the old releases as well.

Won't fixing this. We're having trouble reproducing this. We also don't recommend running a query while the table is still loading.

You can also reproduce this by clicking Column Options and moving a boolean column to the top of the list. Save, close the table tab, and reopen it. The tab will not be able to load because it is trying to sort the table by the first column, which is now a boolean column.
You can fix this issue by opening this file on macOS (or the equivalent on Windows): /Applications/Microsoft\ Azure\ Storage\ Explorer.app/Contents/Resources/app/out/CloudHub/js/StorageExplorer/Tables/TableEntityListViewModel.js
On line 241 (currently) you will find the following switch block:
switch (rowA[col].$) {
    case StorageExplorerConstants.EdmType.Int32:
    case StorageExplorerConstants.EdmType.Int64:
        itemA = parseInt(rowA[col]._, 0);
        itemB = parseInt(rowB[col]._, 0);
        break;
    case StorageExplorerConstants.EdmType.Double:
        itemA = parseFloat(rowA[col]._);
        itemB = parseFloat(rowB[col]._);
        break;
    case StorageExplorerConstants.EdmType.DateTime:
        itemA = new Date(rowA[col]._);
        itemB = new Date(rowB[col]._);
        break;
    default:
        itemA = rowA[col]._.toLowerCase();
        itemB = rowB[col]._.toLowerCase();
}

Add a new case to handle boolean values. Something like this will work:
case StorageExplorerConstants.EdmType.Boolean:
    itemA = rowA[col]._;
    itemB = rowB[col]._;
    break;


MRIQC crashing on resting data only

Hi,
We have been running MRIQC on our data and we have recursive problem with resting state data. The crash log shows a problem with null bytes, but we did not use Heudiconv to convert our data and we could not find the padding key in our json file. And this error occurs with resting data only, all other data (T1 and task fMRI) run smoothly on MRIQC.
I have the crash log and an example json attached here.
Thank you very much!
Eva
crash-20191211-182511-UID16777218-metadata.a3-792e29f6-a9b5-425d-b258-c6448765e0cf.txt
__REST_20191210142255_15.txt

Closing as this is a very old issue and we never had time to have a deeper look. From what I see in the crash file and the metadata it is hard to tell what could be happening.