Android typing slow

Description
When running detox tests on android the typing seems to be really slow, and it's even slower on my CI. iOS is fine and types quiet fast. What could be causing this?
https://user-images.githubusercontent.com/90803159/191717576-6813f77b-e600-45bc-a440-b8d68f434b1c.mp4
Your environment
Detox version: 19.12.1
React Native version: 0.69.5
Node version:
Device model: Pixel 5 Android 12 API 31
OS: MacOS
Test-runner (select one): jest-circus

I ran into the same problem. For us, it seemed related to synchronization. From my understanding, because Detox is a gray box testing framework, it knows when the system is doing something (like IO) and will pause to let the system "settle". I think it's typing slow because it's waiting for things to "settle" after each character is typed.
https://github.com/wix/Detox/blob/master/docs/Troubleshooting.Synchronization.md
I used
await device. disableSynchronization();

to disable synchronization and used
await device.enableSynchronization();

after typing to turn it back on.
I don't know if it was the correct solution but it helped.

I have tried doing that before typing and it seems to just be as slow:
    await device.disableSynchronization();
    await element(by.id('input-login-email')).typeText(
<EMAIL_ADDRESS>    );
    await element(by.id('input-login-password')).typeText('Password123');
    await element(by.id('input-login-orgid')).typeText('XXXXX\n');
    await device.enableSynchronization();

When typing all I can see this in the logs:
09:17:33.129 detox[26516] INFO:  [APP_STATUS] The app seems to be idle
09:17:43.133 detox[26516] INFO:  [APP_STATUS] The app seems to be idle
09:17:53.136 detox[26516] INFO:  [APP_STATUS] The app seems to be idle
09:18:05.219 detox[26516] INFO:  [APP_STATUS] The app seems to be idle
09:18:23.175 detox[26516] INFO:  [APP_STATUS] The app seems to be idle
09:18:36.210 detox[26516] INFO:  [APP_STATUS] The app is busy with the following tasks:
• "LooperIdlingResource-135-mqt_js" (JS Thread) is executing (JavaScript code).
• UI elements are busy:
  - Reason: UI rendering activity.
• Activity on the React-Native bridge.
09:18:56.656 detox[26516] INFO:  [APP_STATUS] The app is busy with the following tasks:
• "LooperIdlingResource-135-mqt_js" (JS Thread) is executing (JavaScript code).
• UI elements are busy:
  - Reason: UI rendering activity.
• Activity on the React-Native bridge.

Same, it's excruciatingly slow on Android.

Facing the same issue

Same, it's excruciatingly slow on Android.
See
The app is busy with the following tasks:
• "LooperIdlingResource-114-mqt_js" (JS Thread) is executing (JavaScript code).

And
The app is busy with the following tasks:
• Activity on the React-Native bridge.

repeated multiple times.

Well to be reading it out loud, it looks like Detox is alerting you with the fact that typing somehow overloads your system. Do you happen to be using some sort of a fancy input component? Does typing manually (regradless of Detox) work smoothly, at all?
In any case, sharing a video would help a great deal.

I'm in the same situation.
Works very quickly on iOS but takes forever (and even fails due to not finding the typed element) on Android.

I'm in the same situation.


introspection: Keep user-defined order for arguments

This change allows to preserve the order in which arguments have been
defined in introspection queries.

/cc @sipsma @vito


eco-cfgbuild uses an invalid sitemap

foo.us is not a valid site with a sitemap. Unclear why this is here since there is no xml file there even as a test
https://github.com/internetofwater/scheduler/blob/4b52f87ffb26acc7e812730f2a0479252e312bff/dagster/implnets/Makefile#L9

addressed in #13


Simplify punctuator scanning.

Reduce the amount of repetition. Consistently use character check
instead of character code throughout the function.
No performance increase or regression was observed.
Closes #1072

scanPunctuator() is now about half the size, but hopefully more readable :yum:

Can we have the performance number posted here?


Standardizes some Form Inputs + TitleBar Back Button

This PR attempts to show the general pattern that I'm hoping to use for form validation + error handling in that domain. I'd like for that to be consistent across forms, so if you have ideas on that structure, please let me know.
I also implemented a title-bar-back-button because we're becoming more complex, and it seemed worthwhile.

I folded this into #38.


[MM-48202] Upgrade memoize-one to v6.0.0

Summary

In the context of regular dependency upgrades, this PR is upgrading memoize-one to its latest version:

From version
To Version
Changelog
Notes

5.2.1
6.0.0
changelog
Despite being a major version upgrade, there are no changes in the API, only improvements in types and also a new feature: the clear method for clearing memoize function's cache

Ticket Link

https://mattermost.atlassian.net/browse/MM-48202
Release Note

NONE

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/260054


Make landing page mobile friendly

Per offline discussion, there may also be some minimal mobile requirements for non-landing pages.

Per offline discussion, there may also be some minimal mobile requirements for non-landing pages.

Is this fixed by #535 ?


self._set_xvfb_display() makes ChromeDriver fail to start

I had the same issue as the one described in https://github.com/NikolaiT/GoogleScraper/issues/86.
Basically, Chromedriver failed to start and threw this:
2015-02-24 07:40:07,684 - GoogleScraper - ERROR - Message: unknown error: Chrome failed to start: exited abnormally
However running
webdriver.Chrome()
in another console worked without a problem.
After trying to trace the error, I commented this line:
self._set_xvfb_display()
in the file 'GoogleScraper/selenium_mode.py'
This seems to fix it and allow chromedriver to start. I'm using ChromeDriver 2.15.322448

Hi. I also had this issue but seems that we just need to properly set the 'DISPLAY' env variable. So, in my config I have:


demo site running again

Coverage decreased (-0.07%) to 95.719% when pulling a85bb4704fface26d6b9220257d3110c45584a21 on development into 4f133f4dbfcbcaddb8da15b3bc821b3c2eae7e96 on master.


GC config hardcoded in template

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 7.20
Ruby: 2.7.6p219
Distribution: Ubuntu 22.04
Module version: 0.3.0

How to reproduce (e.g Puppet code you use)
class { 'opensearch':
}

What are you seeing
JVM GC settings are hardcoded in template templates/jvm.options.epp
What behaviour did you expect instead
It would be very helpful to be configurable through manifests, in particular Xloggc, NumberOfGCLogFiles and GCLogFileSize.  Otherwise the GC logs can fill up the filesystem considerably, even in small installs, with Gbs of largely useless logs.

@siliconalchemy are you satisfied with the change I have made? If so you can close this issue.

Thankyou!  Are all the entries for different jdk versions still applicable to opensearch?  It's quite confusing to a non-java user that's just looking to use opensearch.  I note that even in the reference the default settings aren't mentioned, or any clear note on how to change the default logging - for a non-java user it's relatively hard work to find out how to turn off GBs worth of useless (to a user) logs.


Feature request: Sort tile count within missions

A request from the forums: When tiles are placed during a mission, they are out of order. They could be ordered according to their tile number, and multiple tiles maybe even summarized like you did with the tile info popup before a mission (with a "x 2" for two tiles, for example).

Ah, yes that should be doable with a split and order!


Support Premium Core

Gotta bug when using premium core feature:
thread '<unnamed>' panicked at clashctl/src/ui/components/proxy/tree.rs:205:26:
Group member should be in all proxies

Sorry but there's no plan to support close-source core. However I'm happy to accept any PR that add such functionality.

Sorry but there's no plan to support close-source core. However I'm happy to accept any PR that add such functionality.

I've been reading this repo's code and adding premium core support, I'll PR when it's ready ;)

I'll PR when it's ready ;)

That will be helpful! Thanks in advance.


required block parameter for snapshot eth endpoints

Description
According to https://eth.wiki/json-rpc/API#the-default-block-parameter, passing a block parameter for snapshot calls is required. This PR makes them required by erroring if the unmarshalling of the request returns a 0 block number. Ideally blockNumber is passed in as nil to these eth endpoints and we can check for that, but it seems like the reflection makes it a 0.
If you guys are OK with this, I can add some tests
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[x] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
Calling any of the
eth_getBalance
eth_getCode
eth_getTransactionCount
eth_getStorageAt
eth_call
will return an error now if the block param is not passed as an extra arg. In geth:
https://github.com/ethereum/go-ethereum/blob/d8ff53dfb8a516f47db37dbc7fd7ad18a1e8a125/rpc/json.go#L303
Checklist

[ ] I have assigned this PR to myself
[ ] I have added at least 1 reviewer
[ ] I have tested this code
[ ] I have updated the README and other relevant documents (guides...)
[ ] I have added sufficient documentation both in code, as well as in the READMEs

Additional comments
Please post additional comments in this section if you have them, otherwise delete it

The only thing I'm worried about is that if we do this, we lose the ability to do these requests for the genesis block since its number is 0.
@Kourin1996 @zivkovicmilos @lazartravica Do you guys think we can refactor stringToBlockNumber to somehow return nil as a block number if it wasn't passed through or if it was explicitly nil?
We need to be careful though since on some calls like eth_newFilter and eth_getLogs this parameter should still be optional with the default value.

I guess value is set to 0 (it is default value for BlockNumber=int64) if block number is not in json arguments. And unmarshalling is done by reflect automatically. So my suggestion is to create new type for Optional Block Number (it's same to *int64)

Difficult to know json params has required values because json.Unmarshal set default value if the value doesn't exist in json. Let's imagine json.Unmarshal parse ["0x...."] to [types.Address, BlockNumber] type value. (parsing second value would be skipped)
https://github.com/0xPolygon/polygon-sdk/blob/b8659d19bb432c74be9310055084ebd7c26fcd2b/jsonrpc/dispatcher.go#L300-L309

Happy to do whatever. I like @Kourin1996's approach

Happy to do whatever. I like @Kourin1996's approach

Agree, I think we can go forward with @Kourin1996 's approach

@Kourin1996 Bit stuck here. Probably my go-noobness! Wondering if you can help.
I created the OptionalBlockNumber type alias, but it still seems like it is struggling with passing "latest", "earliest", etc. Those are now failing. My guess is that the UnmarshalJSON is no longer being called and hence it can't convert "latest" -> OptionalBlockNumber.
Any ideas how I could do this? I tried editing UnmarshalJSON to something like this, but it doesn't seem to like it
// UnmarshalJSON automatically decodes the user input for the block number, when a JSON RPC method is called
func (b OptionalBlockNumber) UnmarshalJSON(buffer []byte) error {
	num, err := stringToBlockNumber(string(buffer))
	if err != nil {
		return err
	}
	*b = num
	return nil
}

@mrwillis Thank you for your investigating! I checked this problem little bit. Error happens if we define OptionalBlockNumber and use this. But when just change type of argument in endpoint handler to pointer, it works. As of now, we can use this way.
Thanks for taking your effort!
func (e *Eth) GetTransactionCount(address types.Address, number *BlockNumber) (interface{}, error) {
	fmt.Printf("\n\nGetTransactionCount %+v, %v\n\n", address, number)
        // => number should be nil when second arguments are not passed

	if number == nil {
		return nil, fmt.Errorf("block parameter is required")
	}
	nonce, err := e.d.getNextNonce(address, BlockNumber(*number))
	if err != nil {
		if err == ErrStateNotFound {
			return argUintPtr(0), nil
		}
		return nil, err
	}
	return argUintPtr(nonce), nil
}

Thanks @Kourin1996 figured it out!


Seems to require Google Tag Manager

I struggled to get this working but eventually figured it out. I couldn't see this anywhere in the docs, but I had to add the container ID using Google Tag Manager. It's simple enough with the Nuxt module:
modules: [
   ['@nuxtjs/google-tag-manager', { id: 'your-container-id' }],
]

Without this, experiment data was not being sent back to Optimize.
I have not looked into this deeply, so maybe my case is a one-off, or maybe this belongs in the docs, I dunno.

I still have doubts


[RFC] wasm32-wasi-p2-module

wasm32-wasi-p2-module, or wasm32-wasi-t2, is a new concept highlighted in a slide in Wasm CG June 2024. The initial idea can be found in a discussion.
P2-module is expected to enhance core modules by integrating advanced features of the WASI-p2, such as networking and encryption capabilities, which are anticipated to be highly appealing to users.
While there hasn't been an official release yet, developers can create wasm-wasi-p2-modules using the latest versions of wasi-sdk(22 and 23). This is done by compiling with the options --target=wasm32-wasip2 -fuse-ld=lld. The output has a mixed version of imports, wasi_snapshost_preview1 and<EMAIL_ADDRESS>Import[15]:
 - func[0] sig=2 <__imported_wasi_snapshot_preview1_args_get> <- wasi_snapshot_preview1.args_get
 - func[1] sig=2 <__imported_wasi_snapshot_preview1_args_sizes_get> <- wasi_snapshot_preview1.args_sizes_get
 - func[2] sig=3 <__imported_wasi_snapshot_preview1_fd_close> <- wasi_snapshot_preview1.fd_close
 - func[3] sig=2 <__imported_wasi_snapshot_preview1_fd_fdstat_get> <- wasi_snapshot_preview1.fd_fdstat_get
 - func[4] sig=4 <__imported_wasi_snapshot_preview1_fd_seek> <- wasi_snapshot_preview1.fd_seek
 - func[5] sig=5 <__imported_wasi_snapshot_preview1_fd_write> <- wasi_snapshot_preview1.fd_write
 - func[6] sig=6 <__imported_wasi_snapshot_preview1_proc_exit> <- wasi_snapshot_preview1.proc_exit
 - func[7] sig=6 <__wasm_import_poll_pollable_drop> <-<EMAIL_ADDRESS> - func[8] sig=6 <__wasm_import_streams_input_stream_drop> <-<EMAIL_ADDRESS> - func[9] sig=6 <__wasm_import_streams_output_stream_drop> <-<EMAIL_ADDRESS> - func[10] sig=6 <__wasm_import_udp_udp_socket_drop> <-<EMAIL_ADDRESS> - func[11] sig=6 <__wasm_import_udp_incoming_datagram_stream_drop> <-<EMAIL_ADDRESS> - func[12] sig=6 <__wasm_import_udp_outgoing_datagram_stream_drop> <-<EMAIL_ADDRESS> - func[13] sig=6 <__wasm_import_tcp_tcp_socket_drop> <-<EMAIL_ADDRESS> - func[14] sig=3 <__wasi_preview1_adapter_close_badfd> <- wasi_snapshot_preview1.adapter_close_badfd

The imports are same with wasm32-wasi-p2.
When implementing, the original wasi library at core/iwas/libraries/libc-wasi won't be touched. The new stuff will be stored at core/iwasm/libraries/libc-wasi-p2-module. If later, it is found to be able to shared with wasm32-wasi-p2, might be renamed to libc-wasi-p2.

P2-module is expected to enhance core modules by integrating advanced features of the WASI-p1, such as networking and encryption capabilities, which are anticipated to be highly appealing to users.

do you mean WASI-p2?

The output has a mixed version of imports, wasi_snapshost_preview1 and<EMAIL_ADDRESS>
wasi_snapshost_preview1 will eventually be replaced by wasip2 things, right?

do you mean WASI-p2?

IIUC, if using --target=wasm32-wasip2, the output is a component. If using --target=wasm32-wasip2-module, the output is a core module. The difference is which linker is used, component-ld or ld.

wasi_snapshost_preview1 will eventually be replaced by wasip2 things, right?

I don't know. I am hoping somebody might be able to answer that.

do you mean WASI-p2?

IIUC, if using --target=wasm32-wasip2, the output is a component. If using --target=wasm32-wasip2-module, the output is a core module. The difference is which linker is used, component-ld or ld.

my question was about your sentence "by integrating advanced features of the WASI-p1".

Yes. Advanced features of the WASI-p2.

Thanks for kicking off the discussion. From our perspective, at least for time being, we don't need a full P2 support (i.e. WASI + Component Model) and just having "T2" would be sufficient. From what I understand, both T2 and preview1 can co-exist as they're in completely different namespaces, so one can choose to build WAMR with both T2 and preview1 enabled, and core module compiled to either target will work (ofc mixing T2 and preview1 calls within the same module might be dangerous, so users should be careful with that). And I think that might be a reasonable plan to first focus on just P2 imports, and only after that provide a full component model support (if ever needed).
Regarding potential deprecation of preview1 in WAMR - at that stage we'd really need to keep it around; however, we'll invest in the adapter https://github.com/loganek/wasi-snapshot-preview2-to-preview1-adapter/ and as soon as it's stable, my team will no longer need preview1 support in WAMR - if there are no other teams relying on that, perhaps it's something we might choose to deprecate over time.

The output has a mixed version of imports, wasi_snapshost_preview1 and<EMAIL_ADDRESS>
wasi_snapshost_preview1 will eventually be replaced by wasip2 things, right?

in case it was not clear, i meant about the use of the adapter in wasi-libc wasip2 build.
i didn't mean the deprecation of wasip1.

I'm not entirely certain if this is an actual issue or just a misunderstanding on my part.
There are roughly 25+ WASI proposals, yet only a handful are supported by wasi-libc, even in P2. This means that a developer cannot utilize the capabilities of the new proposals without directly using binders (often created by wit-bindgen) or libraries built on top of these binders. Compared to using established libraries, working with raw binders demands a deeper understanding of the intricacies involved in type conversion, memory management, and communication between the host and WebAssembly. This can be confusing and challenging.
Despite the fact that more than 75% of the new proposals focus on networking and cloud applications, the trends and practices established now could influence future proposals.
When we look at the Rust/WebAssembly ecosystem, programmers have a wealth of libraries at their disposal, with crates available for almost all WASI proposals on crates.io. On the other hand, C/WebAssembly programmers face a scarcity of libraries, making it difficult to find C libraries related to WASI proposals.
The goal of raising this issue is to enhance support for WASI capabilities. Initially, I believed that all that was needed was to back wasi-libc (P2). However, it now appears that there is also a need to develop C libraries related to WASI proposals that based on binders.


Run go mod tidy in docs and vulnfeeds, update renovate.json.

Run go mod tidy in docs and vulnfeeds, update renovate.json to automatically run go mod tidy after automated update.

You may wish to do the same on the osv-scanner repo as well.


Issue with Screen recorder code

[I am trying to install the screen recording extension from : https://github.com/microsoft/FMLab/tree/master/FMLab/TaskRecorderScreenshot. In both Chrome and Edge, it rejects with an error message : manifest is not valid json]

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

ID: b5762f9e-d7f4-e7fc-49c7-6db64c01bc6a
Version Independent ID: 2aab18ad-f2f1-c0ad-c109-38806c8491a3
Content: Task recorder resources - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/user-interface/task-recorder.md
Service: dynamics-365-cross-app
Product: ****
Technology: ****
GitHub Login: @jasongre
Microsoft Alias: jasongre

Created bug 620276 to track this issue.

@owlkeeper What version of Chrome/Edge are you testing on? I was able to successfully load and use the extension from that location today in both browsers.

@.***
@.***
From: Jason Green @.>
Sent: Thursday, September 23, 2021 9:11 AM
To: MicrosoftDocs/dynamics-365-unified-operations-public @.>
Cc: Mannes Neuer @.>; Mention @.>
Subject: Re: [MicrosoftDocs/dynamics-365-unified-operations-public] Issue with Screen recorder code (#3548)
@owlkeeperhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fowlkeeper&data=04|01|mneuer%40anthology.com|4e535f5c4e2a479e353908d97eacc35e|75853e87aaca4625a00a5a7ca2fe1a72|0|0|637680102754313539|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=i6a29Z83%2FHZF4BK1ola7NonpiIDj9HaEGLwmTmj6RYc%3D&reserved=0 What version of Chrome/Edge are you testing on? I was able to successfully load and use the extension from that location today in both browsers.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-unified-operations-public%2Fissues%2F3548%23issuecomment-925956621&data=04|01|mneuer%40anthology.com|4e535f5c4e2a479e353908d97eacc35e|75853e87aaca4625a00a5a7ca2fe1a72|0|0|637680102754323502|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=sBMMEyezViYfDfGEvPOEmBPfQTpZGZiq3DQjhCdzBS8%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAVOH4N5XFEKU5AT65RLWEN3UDNGSBANCNFSM5DHSFG2A&data=04|01|mneuer%40anthology.com|4e535f5c4e2a479e353908d97eacc35e|75853e87aaca4625a00a5a7ca2fe1a72|0|0|637680102754323502|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=hEeKtsAm9Fl4bIsKpmDdvULQvVvhPUlLVCZ5S6vrio0%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|mneuer%40anthology.com|4e535f5c4e2a479e353908d97eacc35e|75853e87aaca4625a00a5a7ca2fe1a72|0|0|637680102754333456|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=6YjohjCKdY8Apl2KzZkt2rpk3w0SACuw3CtKwXbWe7o%3D&reserved=0 or Androidhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|mneuer%40anthology.com|4e535f5c4e2a479e353908d97eacc35e|75853e87aaca4625a00a5a7ca2fe1a72|0|0|637680102754333456|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Jqa9ZVOeBKrd2bZ2zjSFl4KiTvWCTAMqqevvRkCfev4%3D&reserved=0.

CONFIDENTIALITY NOTICE:- The information contained in this email and any document attached hereto is intended only for the named recipient(s). It is the property of Anthology and shall not be used, disclosed or reproduced without the express written consent of Anthology. If you are not the intended recipient or the employee or agent responsible for delivering this message in confidence to the intended recipient(s), you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this email or its attachments is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email or by calling<PHONE_NUMBER>. Thank you.


Minor update

import "materialize-css"; in app.module.ts so otherwise you will have error
Uncaught Error: Couldn't find Materialize object on window. It is created by the materialize-css library. Please import materialize-css before importing angular2-materialize.

@allahbaksh , thanks for your contribution!


Adding example for useEffect changing the currency

Fixes #96
https://user-images.githubusercontent.com/13142568/112827255-75a7e980-9064-11eb-92bc-84d9e8d9c744.mov

I’m not a fan of this useEffect solution since it’s ignoring the state of the asynchronous script loader. How about we leverage the disabled state of the select box instead? The thinking is the select box remains disabled while the script is loading based on isResolved state.

Well, I completely understand that this example doesn't quite shows the benefits of it, but this example was created to show how to do it for devs who actually need it. In my case, was when I had a CurrencyContext, and changed the the currency based on the user location, so we load first it as GBP, and then to whatever the user needs.
What do you suggest? Creating a full usable example?

Closing this one out in favor of https://github.com/paypal/react-paypal-js/pull/100 instead.


[CWS-2966] add missing cws-instrumentation flags in attach mode

What does this PR do?
Some of the main cws-instrumentation flags were not passed to forked processes in attach mode (especially, no-seccomp flag). This PR adds all missing and organizes then in the same order was the flag definition hopefully ensuring we don't forget those in the future.
Motivation
Describe how to test/QA your changes
Tested manually, the core code is covered by tests.
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Fix "lock/em/up" link

Expected behavior and actual behavior.
Elaine Boosler's Quote
How to fix the problem.
Remapped, using wildcards (lock / * / *), i.e. the "shucks" method inside the "Welcome" controller
Requirements for fixing problem.
Wildcard Routing, routing rule leasing to welcome/shucks

"lock/em/up" image fixed.  A new routing rule was added that redirect /lock// to /welcome/shucks.


ModuleNotFoundError: No module named 'werkzeug.wrappers.etag'

ModuleNotFoundError: No module named 'werkzeug.wrappers.etag' #20723
How to reproduce the bug
Install using pip on Ubuntu with python 3.9
Get to this point as per instructions:
$HOME/venv/superset/2.0.0/bin/superset db upgrade
Expected results
No error
Actual results
logging was configured successfully
2022-07-15 15:10:24,707:INFO:superset.utils.logging_configurator:logging was configured successfully
2022-07-15 15:10:24,713:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-07-15 15:10:24,716:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-07-15 15:10:24,720:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Failed to create app
Traceback (most recent call last):
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/app.py", line 37, in create_app
    app_initializer.init_app()
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/initialization/__init__.py", line 460, in init_app
    self.init_app_in_ctx()
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/initialization/__init__.py", line 409, in init_app_in_ctx
    self.configure_url_map_converters()
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/initialization/__init__.py", line 508, in configure_url_map_converters
    from superset.utils.url_map_converters import (
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/utils/url_map_converters.py", line 21, in <module>
    from superset.models.tags import ObjectTypes
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/models/__init__.py", line 17, in <module>
    from . import core, datasource_access_request, dynamic_plugins, sql_lab, user_attributes
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/models/core.py", line 63, in <module>
    from superset.utils import cache as cache_util, core as utils
  File "$HOME/venv/superset/2.0.0/lib/python3.9/site-packages/superset/utils/cache.py", line 28, in <module>
    from werkzeug.wrappers.etag import ETagResponseMixin
ModuleNotFoundError: No module named 'werkzeug.wrappers.etag'

A hack to get around it:
python3 -m pip uninstall -y Werkzeug
python3 -m pip install Werkzeug==2.0.3

If there's one thing you can reply on with a superset release is dodgy pip deps.

Duplicate of #20717.

I just installed Superset 2.0.0 from scratch and wasn't able to replicate this issue unfortunately.

Did you test this on Ubuntu 22.04?

I tested this within a Docker container and on Mac OS X. It's unclear to me why Ubuntu would be playing a role here, or what am I missing? The packages installed are all the same on any *nix operating system :)

I'm just the Ubuntu messenger. I cannot speak for Mac.
I recommend trying to install on a fresh Ubuntu 22.04 using pip install and you'll see the problems. It comes with python 3.10, and this results in a failure based on a couple of problematic deps (see below).
Even when I install python 3.9 alongside, I get the error described above.
In order to overcome ALL issues I encountered I need to perform:

Python 3.9 install using pyenv (and run pip install apache-superset using the 3.9 binary)
And immediately after that:

- python3.9 -m pip uninstall -y markupsafe
- python3.9 -m pip install --cache-dir="$CARI_PIP_CACHE/3.9.13" markupsafe==2.0.1
- python3.9 -m pip uninstall -y Werkzeug
- python3.9 -m pip install --cache-dir="$CARI_PIP_CACHE/3.9.13" Werkzeug==2.0.3

The above needs to be done before the superset db upgrade step
Just reporting as I see it based on a fresh install of Ubuntu 22.04 (with all system updates applied). Issues re markupsafe, Werkzeug have been reported elsewhere on this message board.

I just installed Superset 2.0.0 from scratch and wasn't able to replicate this issue unfortunately.

It happends only in LXC containers and python 3.9 installations

can confirm it is indeed happening inside my LXC 20.04 container

I ran into a similar issue trying @dat-linux 's workaround, and also had to downgrade Flask - downgrading to Flask 2.1.0 seemed to fix things. (I also downgraded markup safe / Werkzeug as they suggested - did not try tweaking anything else)

@eogren Yes, Flask is now also creating a problem. Which version of Flask did you fall back to?

@dat-linux I installed Flask == 2.1.0

Do note that production Superset installations should use pinned dependencies based on: https://github.com/apache/superset/blob/master/requirements/base.txt

We are all installing Superset via pip!

OK, so what's the full install command, because the apache-superset package is not in that requirements file.

@dpgaspar thanks a lot for pointing that out!
Was facing the same problem. Running 1.5.0,  upgrading to 2.0.0.
My solution was:
wget -O- https://raw.githubusercontent.com/apache/superset/2.0.0/requirements/base.txt | tail -n +10 > superset_requirements.txt
pip install apache-superset==2.0.0 -r superset_requirements.txt

This requirements/base.txt assumes a development environment (considering the -e file:. in there), and that was causing conflicts with my installation setup. tail in my command is to skip those lines.
After that I could move forward with applying db migrations successfully :)

Do note that production Superset installations should use pinned dependencies based on:

Would it be a good idea to use constraints like Airflow does, considering that there a quite a lot of optional extra requires in Superset which do not need to be installed?
I'm not sure if any of the dependencies for the extra requires are actually currently included in the pip-compile-multi generated requirements files to begin with.
Just thinking out loud.

Collecting pyarrow==5.0.0
Downloading pyarrow-5.0.0.tar.gz (739 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 739.1/739.1 kB 4.4 MB/s eta 0:00:00
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [945 lines of output]
Ignoring numpy: markers 'python_version < "3.9"' don't match your environment

Install still fails on platforms that have Python 3.10 by default (ie Ubuntu 22.04).
That is not exactly related to the original issue. Python 3.10 support is in a different issue: https://github.com/apache/superset/pull/21002

Well, the original issue was found due to an attempt to install Superset on Ubuntu 22.04.

wget -O- https://raw.githubusercontent.com/apache/superset/2.0.0/requirements/base.txt[](https://raw.githubusercontent.com/apache/superset/2.0.0/requirements/base.txt) | tail -n +10 > superset_requirements.txt
pip install apache-superset==2.0.0 -r superset_requirements.txt

I made a variant of the command @WesleyBatista made, since the one he shared creates a file which isn't necessary:
curl -sS https://raw.githubusercontent.com/apache/superset/2.0.0/requirements/base.txt | tail -n +10 | awk -v ORS=" " '/^[A-z]/{print}' | xargs pip install apache-superset==2.0.0

I'm just the Ubuntu messenger. I cannot speak for Mac.
I recommend trying to install on a fresh Ubuntu 22.04 using pip install and you'll see the problems. It comes with python 3.10, and this results in a failure based on a couple of problematic deps (see below).
Even when I install python 3.9 alongside, I get the error described above.
In order to overcome ALL issues I encountered I need to perform:

Python 3.9 install using pyenv (and run pip install apache-superset using the 3.9 binary)
And immediately after that:

- python3.9 -m pip uninstall -y markupsafe
- python3.9 -m pip install markupsafe==2.0.1
- python3.9 -m pip uninstall -y Werkzeug
- python3.9 -m pip install Werkzeug==2.0.3

The above needs to be done before the superset db upgrade step.
Just reporting as I see it based on a fresh install of Ubuntu 22.04 (with all system updates applied). Issues re markupsafe, and 3.10 failure (it results in an error when building the pyarrow pkg) have been reported elsewhere on this message board.

i then get an error while installing Werzeug 2.0.3
"flask 2.2.2 requires Werkzeug>=2.2.2,"
and further during superset db upgrade
"TypeError: init() got an unexpected keyword argument 'unbound_message'"

@trimat1 , I couldn't get 22.04 to work whatsoever.. python 3.10 has some breaking changes in the dependencies superset uses..
I backed down to 20.04 and did this routine to get setup, remove the sudo -u ubuntu .. I use Juju and that runs as Root by default which I do not want for Superset
apt-get update
apt-get -y upgrade
apt-get -y install build-essential libssl-dev libffi-dev python3-dev python3-pip libsasl2-dev libldap2-dev default-libmysqlclient-dev libpq-dev python-is-python3

pip install --upgrade pip
sudo -u ubuntu pip install --upgrade pip --no-warn-script-location
sudo -u ubuntu pip install werkzeug==2.0.3 --no-warn-script-location
sudo -u ubuntu pip install flask==2.1.3 --no-warn-script-location
sudo -u ubuntu pip install wtforms==2.3.0 --no-warn-script-location
sudo -u ubuntu pip install --upgrade pyopenssl --no-warn-script-location
sudo -u ubuntu pip install psycopg2-binary pillow gunicorn gevent --no-warn-script-location

sudo -u ubuntu pip install sqlalchemy-trino pyhive --no-warn-script-location
sudo -u ubuntu pip install apache-superset --no-warn-script-location

sudo touch /etc/profile.d/superset.sh
echo -e 'export FLASK_APP=superset' >> /etc/profile.d/superset.sh

export FLASK_APP=superset
sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset db upgrade
sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset fab create-admin --username admin --firstname admin --lastname user --email<EMAIL_ADDRESS>--password YOURFAVORITEPASSWORDHERE

install_example_data="$(config-get install_example_data)"
if $install_example_data; then
  sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset load_examples
else
  juju-log -l "WARNING" "Forgoing superset load_examples"
  status-set maintenance "Forgoing superset load_examples $(date +"%H:%M")"
fi
sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset init

@trimat1 , I couldn't get 22.04 to work whatsoever.. python 3.10 has some breaking changes in the dependencies superset uses..
I backed down to 20.04 and did this routine to get setup, remove the sudo -u ubuntu .. I use Juju and that runs as Root by default which I do not want for Superset
apt-get update
apt-get -y upgrade
apt-get -y install build-essential libssl-dev libffi-dev python3-dev python3-pip libsasl2-dev libldap2-dev default-libmysqlclient-dev libpq-dev python-is-python3

pip install --upgrade pip
sudo -u ubuntu pip install --upgrade pip --no-warn-script-location
sudo -u ubuntu pip install werkzeug==2.0.3 --no-warn-script-location
sudo -u ubuntu pip install flask==2.1.3 --no-warn-script-location
sudo -u ubuntu pip install wtforms==2.3.0 --no-warn-script-location
sudo -u ubuntu pip install --upgrade pyopenssl --no-warn-script-location
sudo -u ubuntu pip install psycopg2-binary pillow gunicorn gevent --no-warn-script-location

sudo -u ubuntu pip install sqlalchemy-trino pyhive --no-warn-script-location
sudo -u ubuntu pip install apache-superset --no-warn-script-location

sudo touch /etc/profile.d/superset.sh
echo -e 'export FLASK_APP=superset' >> /etc/profile.d/superset.sh

export FLASK_APP=superset
sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset db upgrade
sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset fab create-admin --username admin --firstname admin --lastname user --email<EMAIL_ADDRESS>--password YOURFAVORITEPASSWORDHERE

install_example_data="$(config-get install_example_data)"
if $install_example_data; then
  sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset load_examples
else
  juju-log -l "WARNING" "Forgoing superset load_examples"
  status-set maintenance "Forgoing superset load_examples $(date +"%H:%M")"
fi
sudo -u ubuntu FLASK_APP=superset /home/ubuntu/.local/bin/superset init

Hi @EMCP ,
i finally managed to run it.
pip uninstall -y markupsafe
pip install markupsafe==2.0.1
pip uninstall -y Werkzeug
pip install Werkzeug==2.0.3
pip uninstall WTForms
pip install WTForms==2.3.0

this is whats was needed (hopefully).
installed and uninstalled a dozen of packages, but these might be the relevant ones.

I get this when I tried your options
superset db upgrade
Traceback (most recent call last):
  File "/root/venv/bin/superset", line 33, in <module>
    sys.exit(load_entry_point('apache-superset==2.0.0', 'console_scripts', 'superset')())
  File "/root/venv/bin/superset", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 86, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/root/venv/lib/python3.9/site-packages/superset/__init__.py", line 18, in <module>
    from flask import current_app, Flask
  File "/root/venv/lib/python3.9/site-packages/flask/__init__.py", line 4, in <module>
    from . import json as json
  File "/root/venv/lib/python3.9/site-packages/flask/json/__init__.py", line 8, in <module>
    from ..globals import current_app
  File "/root/venv/lib/python3.9/site-packages/flask/globals.py", line 56, in <module>
    app_ctx: "AppContext" = LocalProxy(  # type: ignore[assignment]
TypeError: __init__() got an unexpected keyword argument 'unbound_message'

I also face this problem when I test 2.0.1RC1. @srinify
I follow above steps

create a new virtual environment

yongjie.zhao@:tmp$ mkvirtualenv release
created virtual environment CPython3.8.6.final.0-64 in 482ms
  creator CPython3Posix(dest=/Users/yongjie.zhao/.virtualenvs/release, clear=False, global=False)
  seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/Users/yongjie.zhao/Library/Application Support/virtualenv)
    added seed packages: pip==22.2.2, setuptools==65.3.0, wheel==0.37.1
  activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator
virtualenvwrapper.user_scripts creating /Users/yongjie.zhao/.virtualenvs/release/bin/predeactivate
virtualenvwrapper.user_scripts creating /Users/yongjie.zhao/.virtualenvs/release/bin/postdeactivate
virtualenvwrapper.user_scripts creating /Users/yongjie.zhao/.virtualenvs/release/bin/preactivate
virtualenvwrapper.user_scripts creating /Users/yongjie.zhao/.virtualenvs/release/bin/postactivate
virtualenvwrapper.user_scripts creating /Users/yongjie.zhao/.virtualenvs/release/bin/get_env_details

download rc1 tarball

(release) yongjie.zhao@:tmp$ wget -c https://dist.apache.org/repos/dist/dev/superset/2.0.1rc1/apache-superset-2.0.1rc1-source.tar.gz
--2022-10-08 14:08:32--  https://dist.apache.org/repos/dist/dev/superset/2.0.1rc1/apache-superset-2.0.1rc1-source.tar.gz
Resolving dist.apache.org (dist.apache.org)... <IP_ADDRESS>
Connecting to dist.apache.org (dist.apache.org)|<IP_ADDRESS>|:443... connected.

Use a strong complex alphanumeric string and use a tool to help you generate
a sufficiently random sequence, ex: openssl rand -base64 42
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
logging was configured successfully
2022-10-08 14:16:48,961:INFO:superset.utils.logging_configurator:logging was configured successfully
2022-10-08 14:16:48,968:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-10-08 14:16:48,971:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-10-08 14:16:48,974:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the following cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Failed to create app
Traceback (most recent call last):
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/app.py", line 37, in create_app
    app_initializer.init_app()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 460, in init_app
    self.init_app_in_ctx()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 409, in init_app_in_ctx
    self.configure_url_map_converters()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 508, in configure_url_map_converters
    from superset.utils.url_map_converters import (
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/utils/url_map_converters.py", line 21, in <module>
    from superset.models.tags import ObjectTypes
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/models/__init__.py", line 17, in <module>
    from . import core, datasource_access_request, dynamic_plugins, sql_lab, user_attributes
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/models/core.py", line 63, in <module>
    from superset.utils import cache as cache_util, core as utils
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/utils/cache.py", line 28, in <module>
    from werkzeug.wrappers.etag import ETagResponseMixin
ModuleNotFoundError: No module named 'werkzeug.wrappers.etag'
2022-10-08 14:16:49,065:ERROR:superset.app:Failed to create app
Traceback (most recent call last):
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/app.py", line 37, in create_app
    app_initializer.init_app()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 460, in init_app
    self.init_app_in_ctx()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 409, in init_app_in_ctx
    self.configure_url_map_converters()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 508, in configure_url_map_converters
    from superset.utils.url_map_converters import (
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/utils/url_map_converters.py", line 21, in <module>
    from superset.models.tags import ObjectTypes
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/models/__init__.py", line 17, in <module>
    from . import core, datasource_access_request, dynamic_plugins, sql_lab, user_attributes
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/models/core.py", line 63, in <module>
    from superset.utils import cache as cache_util, core as utils
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/utils/cache.py", line 28, in <module>
    from werkzeug.wrappers.etag import ETagResponseMixin
ModuleNotFoundError: No module named 'werkzeug.wrappers.etag'
Traceback (most recent call last):
  File "/Users/yongjie.zhao/.virtualenvs/release/bin/superset", line 8, in <module>
    sys.exit(superset())
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/click/core.py", line 1654, in invoke
    super().invoke(ctx)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/flask/cli.py", line 354, in decorator
    app = __ctx.ensure_object(ScriptInfo).load_app()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/flask/cli.py", line 308, in load_app
    app = locate_app(import_name, name)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/flask/cli.py", line 237, in locate_app
    return find_app_by_string(module, app_name)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/flask/cli.py", line 165, in find_app_by_string
    app = attr(*args, **kwargs)
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/app.py", line 44, in create_app
    raise ex
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/app.py", line 37, in create_app
    app_initializer.init_app()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 460, in init_app
    self.init_app_in_ctx()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 409, in init_app_in_ctx
    self.configure_url_map_converters()
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/initialization/__init__.py", line 508, in configure_url_map_converters
    from superset.utils.url_map_converters import (
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/utils/url_map_converters.py", line 21, in <module>
    from superset.models.tags import ObjectTypes
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/models/__init__.py", line 17, in <module>
    from . import core, datasource_access_request, dynamic_plugins, sql_lab, user_attributes
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/models/core.py", line 63, in <module>
    from superset.utils import cache as cache_util, core as utils
  File "/Users/yongjie.zhao/.virtualenvs/release/lib/python3.8/site-packages/superset/utils/cache.py", line 28, in <module>
    from werkzeug.wrappers.etag import ETagResponseMixin
ModuleNotFoundError: No module named 'werkzeug.wrappers.etag'

I get this when I tried your options
superset db upgrade
Traceback (most recent call last):
  File "/root/venv/bin/superset", line 33, in <module>
    sys.exit(load_entry_point('apache-superset==2.0.0', 'console_scripts', 'superset')())
  File "/root/venv/bin/superset", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.9/importlib/metadata.py", line 86, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 850, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/root/venv/lib/python3.9/site-packages/superset/__init__.py", line 18, in <module>
    from flask import current_app, Flask
  File "/root/venv/lib/python3.9/site-packages/flask/__init__.py", line 4, in <module>
    from . import json as json
  File "/root/venv/lib/python3.9/site-packages/flask/json/__init__.py", line 8, in <module>
    from ..globals import current_app
  File "/root/venv/lib/python3.9/site-packages/flask/globals.py", line 56, in <module>
    app_ctx: "AppContext" = LocalProxy(  # type: ignore[assignment]
TypeError: __init__() got an unexpected keyword argument 'unbound_message'

I got the same result.....

Solved problem with flask==2.1.0 WTForms==2.3.0  Werkzeug==2.0.3


add upnp support

What was wrong?
Currently, Trin cannot support a private node running behind a firewall/gateway.  Inspired by libp2p, this PR adds UPnP support, which is the default NAT used in libp2p.
How was it fixed?
UPnP protocol will ask the gateway to map a private IP/port to an external IP/port and return the external address to Trin.  By encoding the external address in ENR, Trin will allow any node to access a Trin node running behind the gateway.
Test:

Run a Trin node behind a gateway with an empty bootnode.  The node will print the ENR with an external IP/port mapped by UPnP.
Run another Trin node using the bootnode's ENR, which connects the bootnode.
Call portal_historyGossip (using test vector) from one node and check that another node receives the data.

To-Do

[ ] Clean up commit history and use conventional commits.

The guy at nimbus who was pushing for 4444s told me why aren't you guys just using upnp, so I think this is a good first direction.
As Qi said on discord in general channel we will probably end up supporting

UPnP (default)
rendezvous
relay

In that order of priority.
This will also majorly support our effort to having a large network.
Thank you Qi for looking into this I believe this PR solves or at least work towards https://github.com/ethereum/trin/issues/22 Carver can correct me if I am wrong on that
I guess I am saying I support this change


Minitest 5 compatibility?

Are there plans to make mongoid-minitest compatible with minitest 5? Activesupport 4.1+ now depends on minitest 5.1.

I'm working on this now, but starting on minitest-activemodel
https://github.com/frodsan/minitest-activemodel/pull/5

This is ready to pull-in, but the full build matrix is going to fail until minitest-activemodel v1.1.0 is officially released.  See https://github.com/frodsan/minitest-activemodel/pull/5#issuecomment-109848070

v1.1.0 gem released. https://rubygems.org/gems/mongoid-minitest


Darwin panic: PANIC 56: uncaught error (calling abort)

Gist at
https://gist.github.com/f3e185e7f2dc40364faf95959ff8a920
Freshly downloaded binary from bintray, invoked as
/don_dev_darwin-amd64 --public_url=http://localhost:5000 --addr=":5000"

Yep, I think I've got go.rice configured incorrectly. Investigating now!

If you start it inside the don source directory though, so the build directory is available to it, and if you do make build/entry-client-bundle.js build/entry-server-bundle.js beforehand, it should work. Hopefully this will be solved momentarily though.

Actually, that's incorrect - it turned out to be a bug in the client code. Poor error reporting from duktape (my fault) hid a bug in the UI JavaScript. My react static rendering in go is still verrrry experimental. This does remind me though - I should tighten up the client code with flowtype now that it's actually working.


Fix: return statement for multiply documents remove

Without return statement execution of function continue and fail with TypeError: $_id must be string.

Thanks!


[tests] Improve Cosmos EndToEnd test

Wait for the texts indicating that the db, and service are ready for requests before sending the http request. This helps with unnecessary attempts, and wait times in the retry pipeline.

[tests] TestProject.WorkerA - reduce pings logged to every 30s instead of 1s to reduce noise in the logs
[tests] TestProject.AppHost - use single line logging to help with matching log texts in the tests
[tests] EndToEnd tests - add some text to wait for before sending the http request

Microsoft Reviewers: Open in CodeFlow

Related: https://github.com/dotnet/aspire/pull/5641

What do you think about removing this test from the EndToEnd and putting it in its own FunctionalTests? Like we did for the other integrations. I think this is just left over from that work.
Then we wouldn't need to clutter up the EndToEnd tests with this change.

Makes sense. cc @sebastienros as he has been adding the functional tests.

Added cosmos to https://github.com/dotnet/aspire/issues/4741 . Closing this in favor of that issue.


Implement Field Constraints in Game Model

We need to add specific constraints to the Game model and related models in our Django application to ensure logical consistency. For example, we want to make sure min_players <= max_players. In this issue, we will identify what needs constraints we need to add.

For the Game model:

Player Number Constraints: The min_players field must always be less than or equal to the max_players field. This logic needs to be implemented to prevent inconsistencies in player numbers.

Playtime Constraints: Implement a check to ensure that min_playtime <= expected_playtime <= max_playtime. This validation is crucial to keep the playtime data logically consistent.

Complexity Range Constraint: The complexity field should be a float that ranges between 0 and 5. This constraint must be strictly enforced, possibly through a custom validator.

We can also add in a similar constraints to make sure min_players <=  max_players in the Lobby model since it is in the same file.

Closing comments:
A PR implementing these changes been merged. Here is a description of the work that was done:

I added some basic validation was added to the Game and Lobby models.
Examples:
Ensuring min_players <= max_players for both models
Ensuring this ordering: `min_playtime <= expected_playtime <= max_playtime
Ensures the complexity field is between the range of 1 and 5 inclusive.
This also involved making changing to the Games factory and a small tweak to existing tests.


UI[feature]: Addition of ESLint for the UI

Signed-off-by: kushthedude<EMAIL_ADDRESS>
Description

Addition of ESLint and its required dependencies for the Next Configuration
This PR refers  #696

Checklist

[x] DCO signed.
[x] Title of the PR starts with area name, e.g. meshery:, mesheryctl:, ui:.

@leecalcote

Currently, I have just the ESLint Configuration. I have not enforced the configuration as there are many places where I have to make changes manually.
There are some extra parameters in eslint.rc file as I have dynamically imported the React Version from the Package.json.
Changes are huge as I have applied all the changes which can be automatically fixed by linter.
In a follow-up PR, I will add the config loader and test script for the same in CI and package.json.

If there is anything more you had like, feel free to suggest me. Also, since I am new to the Next.js framework which is built over react. I have just used some standard react and EcmaScript rules for the configuration

@mcastre you don't happen to have a perspective here with regard to best practices, do you?


Avoid to render or redirect multiple times

This PR fix this error:
AbstractController::DoubleRenderError (Render and/or redirect were called multiple times in this action. Please note that you may only call render OR redirect, and at most once per action. Also note that neither redirect nor render terminate execution of the action, so if you want to exit an action after redirecting, you need to do something like "redirect_to(...) and return".):

When tried to request a AMP page but the app redirects or render before is raising that error.
I think that the best approach is to check if render or redirect has already been called before.

Thank you for the pull request! Just merged it.
I appreciate that you found this bug, and I confirmed the solution works well. 👍


[Network] Load Balancing Rules CLI/Portal Discrepancies

When creating load balancing rules in the portal a probe is required before any rules can be created. In the CLI, probe is optional.
Additionally, the portal exposes a SessionPersistence setting that the CLI does not.

I've verified that you can successfully create a load balancing rule without referencing a probe, so I would argue we simply leave this aspect as-is.
Additionally, the "SessionPersistence" setting is exposed in the CLI by its SDK-name "load distribution". Closing this issue.

If there is no valid reason to create a rule without a probe, then this would be a service deficiency and we can implement a workaround until it's fixed.  If that's the case we can reopen this later.


Relocatable Package: create product prefixed relocatable archive

The build system was hardcoded to produce a package that is
prefixed with scylla instead of the product name. This is not
in line with out CI system requirements and can be also a source
for confusion.
This commit make the packaging system generate a package of
the format: {product}-tools-package.tar.gz instead of
scylla-tools-package.tar.gz

@penberg ping (merge or comment :slightly_smiling_face: )
unless @avikivity or you are not convinced with my explanation why we don't need to change the build_deb procedure.

@scylladb/scylla-tools-maint can someone merge please.

@scylladb/scylla-tools-maint ping

Committed - e97c1060476085d25f9709b94df8ab48eac03c39


add standard-summary to readme

standard-reporter didn't quite fit my needs and doesn't appear to be open-source, so I whipped up this alternative module for summarizing standard output with error counts. Here's what the output looks like for the electron refactor I'm working on:
> cat test/fixture.txt | node index.js

5966   Extra semicolon
1615   Missing space before function parentheses
318    Strings must use singlequote
55     Return statement should not contain assignment
38     Expected { after 'if' condition
24     Expected '===' and instead saw '=='
23     Missing '()' invoking a constructor
17     Block must not be padded by blank lines
16     Unexpected trailing comma
13     Multiple spaces found before '+='
12     The '__proto__' property is deprecated
10     Expected space(s) after "catch"
9      Multiple spaces found before '='
8      Gratuitous parentheses around expression
8      Expected '!==' and instead saw '!='
7      More than 1 blank line not allowed

https://github.com/zeke/standard-summary#readme

I like it :+1:
Probably not useful for new code bases, but for transitioning,  absolutely.

Very cool project! This is a great way for teams to gauge the impact of transitioning a codebase to standard.


password authentication failed for user

When I try to backup a Postgres database, I get the following error:
pg_dump: [archiver (db)] connection to database "my_db" failed: FATAL:  password authentication failed for user "my_db"
Even though the password is set, the command still uses --no-password.
I have tried using DBBACKUP_CONNECTORS and not, but it still can't authenticate.
DBBACKUP_CONNECTORS = {
    'default': {
        'USER': os.getenv('DATABASE_USER', 'al'),
        'PASSWORD': os.getenv('DATABASE_PASSWORD', None),
        'HOST': os.getenv('DATABASE_HOST', 'db')
    }
}

Why is the command sent without a password (pg_dump  --host=db --port=5432 --username=my_user --no-password --clean my_db )?

Looks like I need to create a pgpass file.

Solution with pgpass file seems bad, because on server it would be really insecure, and even worse if using containers.

Why? Worse than an environment variable? Is there an alternative solution?

In case of docker containers, env vars are really not secure, there is a security vulnerability discovered.
pgpass file could end up in docker image which leads to database password being leaked.
Docker has a solution like Docker Secrets, which uses files but in a bit different way - they are encrypted unless connected to a container, they are immutable and won't be ever end up in Docker Image. This is why I'm moving my stacks from using common .env to Docker Secrets for sensitive data and all other variables being set from GitLab CI Variables.

the point of my "pgpass solution is bad" comment is that django-dbbackup should NOT rely on it, or any other file, except it's Docker Secrets file.

Wouldn't you just mount the file just like env files? It doesn't seem less secure than env files and seems more secure than environment variables.


Support storage-service in cache configuration

See original merge request on GitLab
In GitLab by [Gitlab user @juergbi] on Oct 29, 2020, 17:07
This replaces the pull-artifact-files config option with a storage-service option in the cache config section to properly support remote execution without downloading blobs that are not needed locally.
With pull-artifact-files disabled, artifact file blobs are completely ignored in cache checks. While this allows remote execution builds without downloading build outputs, it can result in build failures when blobs expire on the server side. It also does not download missing blobs on demand. I.e. bst artifact checkout and other commands don't work with pull-artifact-files disabled.
This branch replaces the pull-artifact-files support with a new storage-service option in the cache config section. When that's configured, all blobs in that remote CAS server are considered cached and only downloaded to the local system when needed (e.g. bst artifact checkout). This works for build outputs with remote execution as well as sources in remote asset servers. Unlike pull-artifact-files this still checks whether the artifact file blobs are available (using FindMissingBlobs without actually downloading them).
While the main use case is to minimize downloads with remote execution, the new configuration option does not depend on remote execution. If used with local builds, this allows BuildStream to operate with a small local cache even for large projects.

In GitLab by [Gitlab user @juergbi] on Oct 31, 2020, 11:35
added 77 commits
3ff58f40...7fee0e64 - 40 commits from branch master00df2f81 - utils.py: Catch correctly if a process is dead when trying to kill it430359fc - utils.py: Don't block on the call's `communicate` call8006ff09 - _signals.py: allow calling signal handler from non-main threads37f4d296 - element.py: Stop setting a deterministic umask for staging sourcesbe1c982f - downloadablefilesource.py: Reset the file opener between every test19170750 - plugin.py: Add a helper to run blocking processes in subprocesses78bb6cb7 - scheduler.py: Use threads instead of processes for jobsce2f23c5 - utils.py: remove 'is_single_threaded' method, we use it only in tests81c18fb4 - tests/frontend/push.py: Allow pushing of dependencies4978d215 - tests/internals/pluginloading: Add missing get_ref() to FooSourcee593414f - fetchqueue.py: Don't skip elements with a cached failure8377e923 - _pipeline.py: Drop the optimization for cached elements in the planner4cf3cb49 - _artifact.py: Make cache query explicit152765f7 - _elementsources.py: Make cache query explicit057403e2 - _stream.py: Add query_cache() methode162f4fa - Move source cache query to fetch jobf24fa15d - _artifact.py: Add cached and strong_key parameters to set_cached()8e2e26fa - Always schedule pull job4b79ff0f - Move artifact cache query to pull jobde4bd316 - Call _initialize_state() in Element._new_from_load_element()9e73b654 - element.py: Move get_logs() to internal API742b2423 - Drop pull-artifact-files config option for remote execution87cd0396 - Always require artifact filesdb257884 - _sandboxremote.py: Drop unused output_files_required parameter3c6ab1e0 - Move _reachable_refs_dir() method from cascache.py to testutilsbe56787c - cascache.py: Reimplement _fetch_directory() with FetchTree()995916d2 - cascache.py: Also fetch file blobs in _fetch_directory()a215fd5d - cascache.py: Remove _ensure_blob() methode3e9adfd - cascache.py: Remove unused parameters from add_object()57f76842 - cascache.py: Add add_objects() method14f29855 - cascache.py: Optimize _fetch_tree() using add_objects()2c5f5afa - cascache.py: Generalize remote_missing_blobs() into missing_blobs()c8ed6895 - cascache.py: Add open() method469498a3 - Use CASCache.open()4e8c0e47 - _cas: Add support for remote cache7b0f8c3f - _context.py: Add support for remote-cache configuration91412205 - _sandboxremote.py: Make storage-service optional with remote cache
Compare with previous version

In GitLab by [Gitlab user @juergbi] on Nov 3, 2020, 04:54
added 32 commits
8ba53497 - plugin.py: Add a helper to run blocking processes in subprocesses1a8423e9 - scheduler.py: Use threads instead of processes for jobs2e592a38 - utils.py: remove 'is_single_threaded' method, we use it only in testsd7a00eeb - tests/frontend/push.py: Allow pushing of dependenciesdd5e656b - tests/internals/pluginloading: Add missing get_ref() to FooSource142fa6bb - fetchqueue.py: Don't skip elements with a cached failureabb6edde - _pipeline.py: Drop the optimization for cached elements in the planner00ca98bf - _artifact.py: Make cache query explicit45bd765c - _elementsources.py: Make cache query explicit25194ffc - _stream.py: Add query_cache() methodbaec8fd6 - Move source cache query to fetch job9bf9d864 - _artifact.py: Add cached and strong_key parameters to set_cached()470b5b2d - Always schedule pull jobf2506c3b - Move artifact cache query to pull job1c82d0f1 - Call _initialize_state() in Element._new_from_load_element()6d3a7ae1 - element.py: Move get_logs() to internal API78e86628 - Drop pull-artifact-files config option for remote executionad45b752 - Always require artifact files824002b0 - _sandboxremote.py: Drop unused output_files_required parameterbdbe67e5 - Move _reachable_refs_dir() method from cascache.py to testutils15d762bc - cascache.py: Reimplement _fetch_directory() with FetchTree()bc1ab828 - cascache.py: Also fetch file blobs in _fetch_directory()59524a61 - cascache.py: Remove _ensure_blob() methodc92c0525 - cascache.py: Remove unused parameters from add_object()a79c517d - cascache.py: Add add_objects() methodfbc35d13 - cascache.py: Optimize _fetch_tree() using add_objects()a4073574 - cascache.py: Generalize remote_missing_blobs() into missing_blobs()a01a298a - cascache.py: Add open() method3e466382 - Use CASCache.open()0ecef22c - _cas: Add support for remote cache0684729f - _context.py: Add support for remote-cache configurationafe016d0 - _sandboxremote.py: Make storage-service optional with remote cache
Compare with previous version

In GitLab by [Gitlab user @juergbi] on Dec 5, 2020, 17:58
added 63 commits
afe016d0...458c0575 - 34 commits from branch master97fc9dd0 - tests/frontend/push.py: Allow pushing of dependencies9f2370e3 - tests/internals/pluginloading: Add missing get_ref() to FooSource17c3ee5a - fetchqueue.py: Don't skip elements with a cached failuree9f34da1 - _pipeline.py: Drop the optimization for cached elements in the plannerde981f94 - _artifact.py: Make cache query explicit23045bc5 - _elementsources.py: Make cache query explicit6d3518a4 - _stream.py: Add query_cache() methoda3a794fd - Move source cache query to fetch jobb6bf6429 - _artifact.py: Add cached and strong_key parameters to set_cached()94a1fb42 - Always schedule pull job7079ac74 - Move artifact cache query to pull job5ef4aba0 - Call _initialize_state() in Element._new_from_load_element()2bc6fd02 - element.py: Move get_logs() to internal API613ae896 - Drop pull-artifact-files config option for remote execution87e93c1f - Always require artifact filesbded35e7 - _sandboxremote.py: Drop unused output_files_required parameter87975ab5 - Move _reachable_refs_dir() method from cascache.py to testutils18393295 - cascache.py: Reimplement _fetch_directory() with FetchTree()0a0573f6 - cascache.py: Also fetch file blobs in _fetch_directory()9a7d7962 - cascache.py: Remove _ensure_blob() methodd229eb57 - cascache.py: Remove unused parameters from add_object()5bc81227 - cascache.py: Add add_objects() methodc17c9875 - cascache.py: Optimize _fetch_tree() using add_objects()0ca4e536 - cascache.py: Generalize remote_missing_blobs() into missing_blobs()fa3018c7 - cascache.py: Add open() method206dbe0c - Use CASCache.open()e17157f8 - _cas: Add support for remote cache802f4f8a - _context.py: Add support for remote-cache configuration425e8dcb - _sandboxremote.py: Make storage-service optional with remote cache
Compare with previous version

In GitLab by [Gitlab user @juergbi] on Dec 7, 2020, 05:58
mentioned in merge request !2112

I've rebased this on top of PR #1450 and changed the cache query strategy. This branch now schedules cache queries as jobs for parallelization only if a remote cache is configured. If only a local cache is used and thus, the job overhead may not be worth it, cache query remains serialized in the main thread. Both cases are handled by Stream.query_cache(). This change is in a separate commit and it could be deferred to a follow-up (i.e. until we reduce the overhead to a point where we can enable it unconditionally).
Remote cache tests still need to be added to the test suite / CI.

Are we testing erroneous configuration conditions ?
Do we get an appropriate error with the provenance to the remote execution configuration block specifying that the storage-service was left unspecified, explaining that it is required to specify the storage service if a storage-service has not been specified globally ?

Do we get an appropriate error with the provenance to the remote execution configuration block specifying that the storage-service was left unspecified, explaining that it is required to specify the storage service if a storage-service has not been specified globally ?

There was already an error message with correct provenance, however, the message was generic:

Dictionary did not contain expected key 'storage-service'

I've replaced this with a clearer error message:

Remote execution requires 'storage-service' to be specified in the 'remote-execution' section if not already specified globally in the 'cache' section

Overall looks good, let's approve :)


ARROW-3800: [C++] Vendor a string_view backport

Vendor the std::string_view backport from https://github.com/martinmoene/string-view-lite

Codecov Report

Merging #2974 into master will increase coverage by 12.8%.
The diff coverage is 88.11%.

@@            Coverage Diff             @@
##           master    #2974      +/-   ##
==========================================
+ Coverage   74.86%   87.67%   +12.8%
==========================================
  Files          68      423     +355
  Lines        5173    63928   +58755
==========================================
+ Hits         3873    56046   +52173
- Misses       1214     7882    +6668
+ Partials       86        0      -86

Impacted Files
Coverage Δ

cpp/src/arrow/compute/kernels/cast.cc
91.15% <100%> (ø)

cpp/src/arrow/python/deserialize.cc
91.7% <100%> (ø)

cpp/src/arrow/builder.h
97.73% <100%> (ø)

cpp/src/arrow/array-test.cc
100% <100%> (ø)

cpp/src/arrow/pretty_print.cc
84.87% <100%> (ø)

cpp/src/arrow/array.h
100% <100%> (ø)

cpp/src/arrow/python/arrow_to_pandas.cc
89.32% <100%> (ø)

cpp/src/arrow/util/string.h
95% <100%> (ø)

cpp/src/arrow/builder.cc
82.23% <70%> (ø)

cpp/src/arrow/util/string_view/string_view.hpp
83.78% <83.78%> (ø)

... and 491 more

Continue to review full report at Codecov.

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


scalacOptions do not follow the delegation rules

steps

Given a file build.sbt with the following content in an empty directory:
lazy val foo = settingKey[Int]("dummy key")

Zero / Zero / Zero / foo := 100
Zero / Test / Zero / foo := { foo.value - 30 }

Zero / Zero / Zero / scalacOptions := List("-Ysafe-init-global")
Zero / Test / Zero / scalacOptions := scalacOptions.value.filter(_ != "-Ysafe-init-global")

lazy val X = (project in file("."))

lazy val printTask = taskKey[Unit]("a dummy print task")
printTask := {
  println((X / foo).value)                      // 100
  println((X / Test / foo).value)               // 70

  println((X / scalacOptions).value)            // List(-Ysafe-init-global)
  println((X / Test / scalacOptions).value)     // List(-Ysafe-init-global)
}

Launch sbt (version 1.9.9) and run:
sbt> printTask

We will get
100
70
List(-Ysafe-init-global)
List(-Ysafe-init-global)

problem

We can see that the value for foo follows the delegation rules, but scalacOptions do not.
expectation

We would expect X / Test / scalacOptions to print the value Nil.
notes
I'm not sure whether it's caused by the code
https://github.com/sbt/sbt/blob/586e0a752cd5d0f0335deaa910c4355e0e0a0e56/main/src/main/scala/sbt/Defaults.scala#L982-L995

Hi @liufengyun!
Your example is probably hitting Rule 1 - https://www.scala-sbt.org/1.x/docs/Scope-Delegation.html#Rule+1%3A+Scope+axis+precedence

Rule 1: Scope axes have the following precedence: the subproject axis, the configuration axis, and then the task axis.

Anything on subproject Zero would be ignored for scalacOptions because there's an existing value in the subproject X. I plan to change the semantic of the bare settings in sbt 2.x to address this issue - https://github.com/sbt/sbt/commit/dbaa34bdacb796dfca54ecc83e8ed85ea27b5756

Thank you for the quick response @eed3si9n .

there's an existing value in the subproject X

Could you elaborate more about it? It seems we did not set scalacOptions for X. In particular, I would expect scalacOptions and foo to behave the same.
When I inspect the delegates precedence, it lists Test / scalacOptions as the first one, and we also see Zero / Test / scalacOptions. Aren't they are the same scope?
sbt:X> inspect X / Test / scalacOptions
[info] Task: scala.collection.Seq[java.lang.String]
[info] Description:
[info] 	Options for the Scala compiler.
[info] Provided by:
[info] 	ProjectRef(uri("file:/Users/liufengyun/Documents/sbt-bug/"), "X") / Test / scalacOptions
[info] Defined at:
[info] 	(sbt.Defaults.configTasks) Defaults.scala:975
[info] 	(sbt.Defaults.configTasks) Defaults.scala:982
[info] 	(sbt.Classpaths.compilerPluginConfig) Defaults.scala:4205
[info] 	(sbt.plugins.SemanticdbPlugin.configurationSettings) SemanticdbPlugin.scala:72
[info] 	(sbt.plugins.SemanticdbPlugin.configurationSettings) SemanticdbPlugin.scala:80
[info] Dependencies:
[info] 	Test / settingsData
[info] 	Test / semanticdbEnabled
[info] 	Test / configuration
[info] 	Test / autoCompilerPlugins
[info] 	Test / scalacOptions / streams
[info] 	Test / fileConverter
[info] 	Test / buildDependencies
[info] 	Test / exportPipelining
[info] 	Test / scalaVersion
[info] 	Test / thisProjectRef
[info] 	Test / earlyOutput
[info] 	Test / sbtPlugin
[info] 	Test / update
[info] 	Test / semanticdbOptions
[info] Reverse dependencies:
[info] 	Test / bspBuildTargetScalacOptionsItem
[info] 	printTask
[info] Delegates:
[info] 	Test / scalacOptions
[info] 	Runtime / scalacOptions
[info] 	Compile / scalacOptions
[info] 	scalacOptions
[info] 	ThisBuild / Test / scalacOptions
[info] 	ThisBuild / Runtime / scalacOptions
[info] 	ThisBuild / Compile / scalacOptions
[info] 	ThisBuild / scalacOptions
[info] 	Zero / Test / scalacOptions
[info] 	Zero / Runtime / scalacOptions
[info] 	Zero / Compile / scalacOptions
[info] 	Global / scalacOptions
[info] Related:
[info] 	Zero / Test / scalacOptions
[info] 	Test / doc / scalacOptions
[info] 	Compile / scalacOptions
[info] 	Global / scalacOptions
[info] 	Compile / doc / scalacOptions

It seems we did not set scalacOptions for X.

sbt's default compile task is implemented by JvmPlugin, and unfortunately I think it needs to inject scalacOptions at the subproject level for various reasons, for example https://github.com/sbt/sbt/blob/586e0a752cd5d0f0335deaa910c4355e0e0a0e56/main/src/main/scala/sbt/Defaults.scala#L982-L988

Test / scalacOptions as the first one, and we also see Zero / Test / scalacOptions. Aren't they are the same scope?

I think the first one means ProjectRef(uri("file:/Users/liufengyun/Documents/sbt-bug/"), "X") / Test / scalacOptions, but we omit the subproject part when we display it.

Thank you for the explanation @eed3si9n !
Now I see the resolution rules are observed. For end users, the rules are seemingly violated due to the implicit injections.
It would be nice to have an injection mechanism that can avoid such surprises. It will be more natural to users if the injection only intercepts and transforms the resolution result in a reasonable way --- such that the resolution rules would "seem" to follow in spite of the injection.
I see it's a complicated design problem, it's already beyond the reach of most build tools.

Yea with https://github.com/sbt/sbt/commit/dbaa34bdacb796dfca54ecc83e8ed85ea27b5756 (https://eed3si9n.com/simplifying-sbt-with-common-settings/),
scalacOptions := scalacOptions.value.filter(_ != "-Ysafe-init-global")

would be injected into all subprojects in sbt 2.x.

https://eed3si9n.com/simplifying-sbt-with-common-settings/

That sounds like a very good design --- it solves both simple and complex problems with low cognitive load. Yet it's still easy to explain to experts simply by saying they are "automatic subproject-level settings".
One minor detail: I guess users can still specify the axis of the common settings, right? That would make advanced use cases possible.


regression-test add order by to make test stable

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Feature/apb province municipality select filter

I tried to fix conflicts before merging but i seem to have made a mistake somewhere you can ignore this prequest

I'm only seeing it now but this behavior should also be added to the new route, when a user created a new administrative unit.


Correction for raw affiliation Adaptations Physiologiques à l'Exercice et Réadaptation à l'effort - UR UPJV 3300; French Institute of Sport (INSEP), Laboratory Sport, Expertise and Performance (EA7370)

Correction needed for raw affiliation Adaptations Physiologiques à l'Exercice et Réadaptation à l'effort - UR UPJV 3300; French Institute of Sport (INSEP), Laboratory Sport, Expertise and Performance (EA7370)
raw_affiliation_name: Adaptations Physiologiques à l'Exercice et Réadaptation à l'effort - UR UPJV 3300; French Institute of Sport (INSEP), Laboratory Sport, Expertise and Performance (EA7370)
new_rors: 03jczk481;01gyxrk03
previous_rors: 03jczk481;05vb5nm66
works_examples: W3179730894
contact: 1a26ee3f5e6d92487f038f5d857bd3c8:1df032e84f5839a35de5a75d32d66b2c @ u-picardie.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-10. The new affiliations should be visible within the next 7 days.


Release July 2024

@smahati There are a lot of conflicts in this PR, which probably come from the patches in cap.cloud.sap that we done for 8.0.0.
The strategy to resolve them would be to accept all from main and to overwrite cap.cloud.sap, which cannot be done in this 'merge from main' PR → I will open a new PR.

@smahati Update: I merged cap.cloud.sap to main first (resolving conflicts by taking all from main).  With this approach I could 'save' this PR.


fix getPrices for the wrapper

As we discussed, a better solution is if arrays reside in the memory.


Improve recurring event fields, fixes #506

Short description
This PR addresses issue 506
Proposed changes

Verbiage for "Interval" needed updated to avoid confusion
Default value "WEEKLY" to frequency field

Resolved issues

[x] Updated to the desired verbiage in django.po
[x] Added the default value for frequency in the recurrence_rule model to be WEEKLY

Fixes: #506

I'm looking into the failures above

I applied our coding style standards and merged this via the command line in 66371ad3fa1c228b8936873a48377dbca066f29f.
Sorry that this PR is not recognized as merged, I will add the label hacktoberfest-accepted to make 100% sure this is counted towards this year's challenge (although I think the review approval should suffice in theory)...


Support #tag along with mentions.

Hey just published a new react-native-mentions package. Check it out.


[SPARK-15957][Follow-up][ML][PySpark] Add Python API for RFormula forceIndexLabel.

What changes were proposed in this pull request?
Follow-up work of #13675, add Python API for RFormula forceIndexLabel.
How was this patch tested?
Unit test.

Test build #66734 has started for PR 15430 at commit e34610c.

Test build #66734 has finished for PR 15430 at commit e34610c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66734/
Test PASSed.

cc @jkbradley

cc @jkbradley

Since it's a minor change, I will merge it into master. Any comments are still appreciated and I will address in follow-up work. Thanks.


Sync block is 1 Way - upload only

This document should state the sync block ONLY blocks the ODFB Sync client from uploading a file. It does not block the sync client from downloading a file type that has been blocked.  (One way Sync Block, not a Two way block)
This behavior can result in data loss when a user edits a blocked file type in a sync folder, causing the file to be deleted from ODFB and unsynced locally.

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

ID: a3a0cebd-7e82-6631-bdee-031b3b84f74d
Version Independent ID: ee04db29-a6db-2874-2573-d80f0b415308
Content: Block syncing of specific file types
Content Source: OneDrive/block-file-types.md
Service: one-drive
GitHub Login: @kaarins
Microsoft Alias: kaarins

@dobby10, Thanks for this feedback. I thought I had already updated this article to clarify, but it looks like I never published the changes. Publishing them now!

The updates have been published. The formatting of the note is off, but I've fixed it and it will go live soon. :)


Missing features of linker script for crt0

With capabilities that linker script and its set eval is offering at this moment it is not possible to write fully functional crt0 routine as there is no way to get informations about how big BSS section is. There should be commands in eval environment that will return size of section or memory. Also start address of section or memory.
Another missing feature of linker script is ability to put data into two memories. Because, data section have to be stored in memory where code is located, thus it will be distributed with binary, and have to be linker against RAM as data section is used for initialized variables and its content is often copied from read only memory into read write memory.
TODO list

[x] Add mem_size() and mem_begin()
[x] Add section_size() and section_begin()
[x] Add relevant information about functions above into doc
[ ] Find and implement best way to deal with data in two memories problem

Small improvement done in d18a5b7e3242634a718c10c695687f7cc953cad7. Now it is possible to use mem_begin() and mem_size() functions in linker script.

Added section_size() and section_begin() in 0b26d0f20a5857aa214821b536ba5809f463dd24.

Updated documentation in 1c404d9e19a4014ea55f6177668df8fa1771fee4.


fix: add missing slash to jump_url property

Summary
Fixes what seems to be a typo in the jump_url

Checklist

[ ] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[x] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, …)

smh beat me too it


Creator api summary

Data Plane API - Pull Request
NO CHANGES TO ANY API, ONLY THE USER DOCUMENTATION.
Update Creator docs so that each services overview page shows a summary of the API, to do so, remove 'Creator makes it possible to develop applications based on your private indoor map data using Azure Maps API and SDK.' paragraph.
for example:

Files to be updated:
\preview\2.0\alias.json
\preview\2.0\dataset.json
\preview\2.0\dwgconversion.json
\preview\2.0\featurestate.json
\preview\2.0\tileset.json
\preview\2.0\wfs.json
\preview\2023-03-01-preview\alias.json
\preview\2023-03-01-preview\dwgconversion.json
\preview\2023-03-01-preview\featurestate.json
\preview\2023-03-01-preview\mapconfiguration.json
\preview\2023-03-01-preview\routeset.json
\preview\2023-03-01-preview\wayfind.json
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

Checks stuck in `queued` state?
If the PR CI checks appear to be stuck in `queued` state, please add a comment with contents `/azp run`.
This should result in a new comment denoting a `PR validation pipeline` has started and the checks should be updated after few minutes.

There are Git conflict markers in these files.

What? Where? Which files?

There are Git conflict markers in these files.
What? Where? Which files?

But it looks like I was looking at a specific commit. Looking at the PR overall it looks like they've all been removed.

/azp run

@mikekistler ack and confirmed. Thank you for noticing this issue and following up.
@stevemunk on the next PR that comes through, this is the adjustment to WFS_GetFeatures.json that you need.


Clint write only?

https://github.com/black-parrot/pre-alpha-release/blob/19cd8defcda72d27de7595a615c4e3c49a01869c/bp_top/src/v/bp_clint.v#L156
I believe that these registers need to be readable as well per the spec.

Where in the spec do you see this? I don't see anything mentioning memory-mapped reads

Platforms provide a real-time counter, exposed as a memory-mapped machine-mode register, mtime. mtime must run at constant frequency, and the platform must provide a mechanism for determining the timebase of mtime.

The machine-level MSIP bits are written by accesses to memory- mapped control registers, which are used by remote harts to provide machine-mode interprocessor interrupts.

Also, if mtime needs to be writable, then we'll need to modify bsg_cycle_counter to support setting.

Seems like there should be one read/writable mtime and mtimecmp register
per core? Maybe it does not make sense to put it on the network?
M
On Mon, May 27, 2019 at 7:58 AM Dan Petrisko<EMAIL_ADDRESS>wrote:

Also, if mtime needs to be writable, then we'll need to modify
bsg_cycle_counter to support setting.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/189?email_source=notifications&email_token=AEFG5AAPMFJCLPUE2QSYFG3PXPZKDA5CNFSM4HP4DCQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKAGLY#issuecomment-496239407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5AC2QPJPHCPR5CSEIM3PXPZKDANCNFSM4HP4DCQA
.

mtime should be shared among all cores. If it's an RTC we only want to have 1 per system. Then, mtimecmps should live near it so we're only sending the timer_irq across the proc instead of the mtime value.
(oh, and mtime should definitely be readable. whoops, I was mixing up a few requirements).

If you read the spec carefully, I think they say you need a real time clock
that is uniform across the system, but that each core had its own
read/writeable counter?
M
On Mon, May 27, 2019 at 10:49 AM Dan Petrisko<EMAIL_ADDRESS>wrote:

mtime should be shared among all cores. If it's an RTC we only want to
have 1 per system. Then, mtimecmps should live near it so we're only
sending the timer_irq across the proc instead of the mtime value.
(oh, and mtime should definitely be readable. whoops, I was mixing up a
few requirements).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/189?email_source=notifications&email_token=AEFG5AEQTGVZAELERYAGQLTPXQNI3A5CNFSM4HP4DCQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKI2IQ#issuecomment-496274722,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5AEUD5UKEUFO6465PDLPXQNI3ANCNFSM4HP4DCQA
.

The spec is ambiguous, but Rocket and Ariane both only have 1 mtime register and N mtimecmp registers.  Back when mtime and mtimecmp were CSRs, I believe it was 1 and N as well (although I can't find an old enough spec to prove it).
On the one hand, it makes sense that having mtime be global means that you could sync timers between cores more easily. On the other, you don't want cores to clobber each other's timer interrupts, which is why I figured read-only mtime makes sense.

https://github.com/black-parrot/pre-alpha-release/blob/top_dev_feature_clintpdrework/bp_top/src/v/bp_clint.v
I made them all (including mtime) MMIO read/write capable for now.  We can take out pathways when we confirm either way

Great — seems like they should all be read/write. The RISC-V forum has a
couple of code snippets where mtimecmp is read.
M
On Mon, May 27, 2019 at 2:27 PM Dan Petrisko<EMAIL_ADDRESS>wrote:

https://github.com/black-parrot/pre-alpha-release/blob/top_dev_feature_clintpdrework/bp_top/src/v/bp_clint.v
I made them all (including mtime) MMIO read/write capable for now. We can
take out pathways when we confirm either way
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/189?email_source=notifications&email_token=AEFG5AA4DXA7ICLEMOVCO4TPXRG2TA5CNFSM4HP4DCQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKRB6Y#issuecomment-496308475,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5ACRSAQJAFWIC53PELTPXRG2TANCNFSM4HP4DCQA
.

Just putting this here for reference.
https://groups.google.com/a/groups.riscv.org/forum/m/#!topic/hw-dev/m3VoPhteSgw
On Mon, May 27, 2019 at 8:04 PM Michael Nguyen Taylor <
<EMAIL_ADDRESS>wrote:

Great — seems like they should all be read/write. The RISC-V forum has a
couple of code snippets where mtimecmp is read.
M
On Mon, May 27, 2019 at 2:27 PM Dan Petrisko<EMAIL_ADDRESS>wrote:

https://github.com/black-parrot/pre-alpha-release/blob/top_dev_feature_clintpdrework/bp_top/src/v/bp_clint.v
I made them all (including mtime) MMIO read/write capable for now. We can
take out pathways when we confirm either way
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/black-parrot/pre-alpha-release/issues/189?email_source=notifications&email_token=AEFG5AA4DXA7ICLEMOVCO4TPXRG2TA5CNFSM4HP4DCQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWKRB6Y#issuecomment-496308475,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFG5ACRSAQJAFWIC53PELTPXRG2TANCNFSM4HP4DCQA
.

Fixed on off-chip network branch. Will get merged in with those changes


Warning when an interface with an optional function is declared

Discussed in https://github.com/sxzz/unplugin-vue-macros/discussions/234

Originally posted by wsaca January 26, 2023
Before create an issue I would like to understand if the next warning could be resolved here:
[Vue warn]: Missing required prop: "onClick"
  at <HelloWorld>
  at <App>

I have this interface with two ways of declaring a function:
export interface HelloWorldProps {
  msg?: string;
  onClick?(): void;
  onFocus?: () => void;
}

Only If I use an arrow function it works.
Example:
https://stackblitz.com/edit/vitejs-vite-bcwnrm?file=src/components/types.ts

It's also a bug of Vue.