KBFS shows a lot of free disk space

While I'd like to try to fill up those 2.3 exabytes, this doesn't look correct.
OS X 10.11.4 Beta (15E56a), should this be relevant.
my log id: 4bcb3f2dd0273e224e1de61c

I get the same thing on Mac as well as on Linux Mint (shown below)

Log ID: 89644d0fe4b42b449f22931c

We aren't pulling down personal quota info yet and sharing it with the OS, but when we do this bug will resolve itself.


Disallow nested custom multiplayers in SceneTree

Enables clearing the custom multiplayer
Considering further restricting to only absolute paths (the only thing that makes sense imo)

Fixes: #77817 (resolves the issue raised)

I understand the issue, and I see how this can be confusing, but this PR heavily de-optimize the most common case (having few custom multiplayer instances and deep path names).
You can test this with the following script (full project):
extends Node

const MULTIPLAYERS = 4
const PATH_DEPTH = 10
const CALLS = 10000

var nodes = []

func build():
	for i in range(MULTIPLAYERS):
		var s = Control.new()
		var cur = s
		for j in range(PATH_DEPTH):
			var step = Control.new()
			cur.add_child(step)
			cur = step
		add_child(s)
		nodes.append(cur)
	for i in range(MULTIPLAYERS):
		get_tree().set_multiplayer(SceneMultiplayer.new(), get_child(i).get_path())

func _ready():
	build()
	test()
	var args := OS.get_cmdline_user_args()
	if args.size() and args[0] == "q":
		get_tree().quit.call_deferred()

# Tests a single node, searching for its custom multiplayer parent
func _test_call(node: Node):
	var mp : MultiplayerAPI
	var time = Time.get_ticks_usec()
	for i in range(CALLS):
		mp = node.multiplayer
	return Time.get_ticks_usec() - time

# Tests each node for its custom multiplayer parent
func test():
	var time = Time.get_ticks_usec()
	var avg = 0
	for node in nodes:
		avg += _test_call(node)
	return avg / nodes.size()

Benchmarks for optimized editor builds (using hyperfine)
$ ~/Downloads/hyperfine --warmup 3 --runs 10 '~/godot-a --path ~/Downloads/mp_test/ --headless -- q' '~/godot-b --path ~/Downloads/mp_test/ --headless -- q'
Benchmark 1: ~/godot-a --path ~/Downloads/mp_test/ --headless -- q
  Time (mean ± σ):     161.2 ms ±   9.4 ms    [User: 121.9 ms, System: 16.5 ms]
  Range (min … max):   151.4 ms … 174.4 ms    10 runs

Benchmark 2: ~/godot-b --path ~/Downloads/mp_test/ --headless -- q
  Time (mean ± σ):     294.0 ms ±   3.4 ms    [User: 183.3 ms, System: 24.1 ms]
  Range (min … max):   288.6 ms … 300.0 ms    10 runs

Summary
  ~/godot-a --path ~/Downloads/mp_test/ --headless -- q ran
    1.82 ± 0.11 times faster than ~/godot-b --path ~/Downloads/mp_test/ --headless -- q

As per the original issue, I think we should simply disallow having nested custom multiplayer APIs.

Gotcha! Will investigate and restructure

This doesn't handle the case when a custom API is configured for a descendant of the new path, unsure how to deal with that case

No worries! And agreed, noticed the same limitation/quirk before but now you're right about that part
I think unless I come up with a clean way to identify and handle those cases I'll leave it as is in that sense, to not complicate the process, but I will consider how to approach it
Could for example add a warning if setting a nested path, should be trivial to identify it (i.e. if a path is a prefix of another path), but will ponder

In that case I will update the wording in the docs too to something like:
"Will error if an API is already configured for a parent" etc.

Thank you! It's been a great journey figuring out exactly how to do it, complicated thing

Thanks!

Thank you!


Pull in cluster branch

Pull in Robert Hubley’s cluster branch
George looked at this and it doesn’t look terrible but we probably ought to think about whether we want to do this first or last (one or the other seems right, doing it in the middle would just cause unnecessary chaos)
We should manually review the entire diff (couple hours, max) to try to maximize the odds that we don’t cause mysterious breakage

In trying to figure out #27 I discovered that while the cluster branch was based on another branch develop, avx is not based on develop. Aside from code changes some of the project structure was moved around, so this could become a bit tricky to review+merge.

Yeah, this is kind of a "nice to have" at this point. We're going to move certain changes forward and then take a look at the diff with the cluster branch and decide how we want to deal with it.

A clarification: "this" means "pulling the cluster branch", as in "we view it as nice to have the cluster branch pulled into the upcoming NINJA release; if it doesn't happen right away, we'll figure out how to get it in there later"


compiling issues

👋 hello together,
I'm quite new in app-development.
I have a sticky problem compiling the mattermost-mobile-app and sadly I can't find a clue what's going wrong.
I download the source files via git.
cd into 'mattermost-mobile' and execute 'npm install'. After that I cd into 'android' and execute './gradlew assembleRelease ' to get an apk-File.
Sadly I get the following error
15:45:27.243 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING 15:45:27.245 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command '/home/fries/Android/Sdk/build-tools/23.0.1/aapt'. 15:45:27.248 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: FAILED 15:45:27.248 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'command '/home/fries/Android/Sdk/build-tools/23.0.1/aapt'' finished with exit value -1 (state: FAILED) 15:45:27.250 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':jail-monkey:processReleaseResources' 15:45:27.250 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :jail-monkey:processReleaseResources FAILED 15:45:27.250 [INFO] [org.gradle.execution.taskgraph.AbstractTaskPlanExecutor] :jail-monkey:processReleaseResources (Thread[main,5,main]) completed. Took 0.058 secs. 15:45:27.251 [DEBUG] [org.gradle.execution.taskgraph.AbstractTaskPlanExecutor] Task worker [Thread[main,5,main]] finished, busy: 2.184 secs, idle: 0.006 secs 15:45:27.265 [ERROR] [org.gradle.BuildExceptionReporter] 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build failed with an exception. 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong: 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] Execution failed for task ':jail-monkey:processReleaseResources'. 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] > com.android.ide.common.process.ProcessException: Failed to execute aapt 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] * Try: 15:45:27.267 [ERROR] [org.gradle.BuildExceptionReporter] Run with --stacktrace option to get the stack trace. 15:45:27.267 [LIFECYCLE] [org.gradle.BuildResultLogger] 15:45:27.267 [LIFECYCLE] [org.gradle.BuildResultLogger] BUILD FAILED

Hi @MamoulianDelacroix have you followed https://docs.mattermost.com/developer/mobile-developer-setup.html ?

@enahum : Thanks a lot I will take a look at it.
But I'm a bit confused the instructions look quiet different from the one from here
https://github.com/mattermost/mattermost-mobile

Hmm 🤔
Now I used your instructions and the error pictures has changed:
`fries@fries-virtual-machine:~$ git clone https://github.com/mattermost/mattermost-mobile.git
Cloning into 'mattermost-mobile'...
remote: Counting objects: 15039, done.
remote: Compressing objects: 100% (86/86), done.
remote: Total 15039 (delta 73), reused 95 (delta 59), pack-reused 14894
Receiving objects: 100% (15039/15039), 11.45 MiB | 3.12 MiB/s, done.
Resolving deltas: 100% (9876/9876), done.
fries@fries-virtual-machine:~$ cd mattermost-mobile/
fries@fries-virtual-machine:~/mattermost-mobile$ make pre-run

daemon not running; starting now at tcp:5037
daemon started successfully
error: no devices/emulators found
Getting Javascript dependencies
yarn install v1.3.2
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.26.0 || ^0.24.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^3.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^4 || ^5".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| 0.20.x || 0.22.x || 1.0.0-rc.1".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^2.3.0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0-0".
warning "chai-enzyme ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.1".
warning "mocha-react-native > react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "mocha-react-native > react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "mocha-react-native > react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "mocha-react-native > react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "mocha-react-native > react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "mocha-react-native > react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-native-mock ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] Building fresh packages...
$ make post-install
make[1]: Verzeichnis „/home/fries/mattermost-mobile“ wird betreten
error: no devices/emulators found
PASS Inject RemoteDev server into React Native local server.
PASS Inject RemoteDev monitor into React Native debugger.
Cloning into 'PerformanceBezier'...
remote: Counting objects: 241, done.
remote: Total 241 (delta 0), reused 0 (delta 0), pack-reused 241
Receiving objects: 100% (241/241), 123.76 KiB | 443.00 KiB/s, done.
Resolving deltas: 100% (139/139), done.
yarn run v1.3.2
$ babel src --out-dir .
src/action_types/admin.js -> action_types/admin.js
src/action_types/alerts.js -> action_types/alerts.js
src/action_types/channels.js -> action_types/channels.js
src/action_types/emojis.js -> action_types/emojis.js
src/action_types/errors.js -> action_types/errors.js
src/action_types/files.js -> action_types/files.js
src/action_types/general.js -> action_types/general.js
src/action_types/index.js -> action_types/index.js
src/action_types/integrations.js -> action_types/integrations.js
src/action_types/jobs.js -> action_types/jobs.js
src/action_types/posts.js -> action_types/posts.js
src/action_types/preferences.js -> action_types/preferences.js
src/action_types/search.js -> action_types/search.js
src/action_types/teams.js -> action_types/teams.js
src/action_types/users.js -> action_types/users.js
src/actions/admin.js -> actions/admin.js
src/actions/alerts.js -> actions/alerts.js
src/actions/channels.js -> actions/channels.js
src/actions/emojis.js -> actions/emojis.js
src/actions/errors.js -> actions/errors.js
src/actions/files.js -> actions/files.js
src/actions/general.js -> actions/general.js
src/actions/helpers.js -> actions/helpers.js
src/actions/integrations.js -> actions/integrations.js
src/actions/jobs.js -> actions/jobs.js
src/actions/posts.js -> actions/posts.js
src/actions/preferences.js -> actions/preferences.js
src/actions/search.js -> actions/search.js
src/actions/teams.js -> actions/teams.js
src/actions/users.js -> actions/users.js
src/actions/websocket.js -> actions/websocket.js
src/client/client.js -> client/client.js
src/client/client4.js -> client/client4.js
src/client/fetch_etag.js -> client/fetch_etag.js
src/client/index.js -> client/index.js
src/client/websocket_client.js -> client/websocket_client.js
src/constants/alerts.js -> constants/alerts.js
src/constants/files.js -> constants/files.js
src/constants/general.js -> constants/general.js
src/constants/index.js -> constants/index.js
src/constants/posts.js -> constants/posts.js
src/constants/preferences.js -> constants/preferences.js
src/constants/request_status.js -> constants/request_status.js
src/constants/stats.js -> constants/stats.js
src/constants/teams.js -> constants/teams.js
src/constants/websocket.js -> constants/websocket.js
src/reducers/entities/admin.js -> reducers/entities/admin.js
src/reducers/entities/alerts.js -> reducers/entities/alerts.js
src/reducers/entities/channels.js -> reducers/entities/channels.js
src/reducers/entities/emojis.js -> reducers/entities/emojis.js
src/reducers/entities/files.js -> reducers/entities/files.js
src/reducers/entities/general.js -> reducers/entities/general.js
src/reducers/entities/index.js -> reducers/entities/index.js
src/reducers/entities/integrations.js -> reducers/entities/integrations.js
src/reducers/entities/jobs.js -> reducers/entities/jobs.js
src/reducers/entities/posts.js -> reducers/entities/posts.js
src/reducers/entities/preferences.js -> reducers/entities/preferences.js
src/reducers/entities/search.js -> reducers/entities/search.js
src/reducers/entities/teams.js -> reducers/entities/teams.js
src/reducers/entities/typing.js -> reducers/entities/typing.js
src/reducers/entities/users.js -> reducers/entities/users.js
src/reducers/errors/index.js -> reducers/errors/index.js
src/reducers/index.js -> reducers/index.js
src/reducers/requests/admin.js -> reducers/requests/admin.js
src/reducers/requests/channels.js -> reducers/requests/channels.js
src/reducers/requests/emojis.js -> reducers/requests/emojis.js
src/reducers/requests/files.js -> reducers/requests/files.js
src/reducers/requests/general.js -> reducers/requests/general.js
src/reducers/requests/helpers.js -> reducers/requests/helpers.js
src/reducers/requests/index.js -> reducers/requests/index.js
src/reducers/requests/integrations.js -> reducers/requests/integrations.js
src/reducers/requests/jobs.js -> reducers/requests/jobs.js
src/reducers/requests/posts.js -> reducers/requests/posts.js
src/reducers/requests/preferences.js -> reducers/requests/preferences.js
src/reducers/requests/search.js -> reducers/requests/search.js
src/reducers/requests/teams.js -> reducers/requests/teams.js
src/reducers/requests/users.js -> reducers/requests/users.js
src/selectors/entities/admin.js -> selectors/entities/admin.js
src/selectors/entities/alerts.js -> selectors/entities/alerts.js
src/selectors/entities/channels.js -> selectors/entities/channels.js
src/selectors/entities/emojis.js -> selectors/entities/emojis.js
src/selectors/entities/files.js -> selectors/entities/files.js
src/selectors/entities/general.js -> selectors/entities/general.js
src/selectors/entities/integrations.js -> selectors/entities/integrations.js
src/selectors/entities/jobs.js -> selectors/entities/jobs.js
src/selectors/entities/posts.js -> selectors/entities/posts.js
src/selectors/entities/preferences.js -> selectors/entities/preferences.js
src/selectors/entities/teams.js -> selectors/entities/teams.js
src/selectors/entities/typing.js -> selectors/entities/typing.js
src/selectors/entities/users.js -> selectors/entities/users.js
src/selectors/errors.js -> selectors/errors.js
src/store/configureStore.dev.js -> store/configureStore.dev.js
src/store/configureStore.prod.js -> store/configureStore.prod.js
src/store/helpers.js -> store/helpers.js
src/store/index.js -> store/index.js
src/store/initial_state.js -> store/initial_state.js
src/utils/channel_utils.js -> utils/channel_utils.js
src/utils/deep_freeze.js -> utils/deep_freeze.js
src/utils/delayed_action.js -> utils/delayed_action.js
src/utils/emoji_utils.js -> utils/emoji_utils.js
src/utils/event_emitter.js -> utils/event_emitter.js
src/utils/file_utils.js -> utils/file_utils.js
src/utils/helpers.js -> utils/helpers.js
src/utils/key_mirror.js -> utils/key_mirror.js
src/utils/post_utils.js -> utils/post_utils.js
src/utils/preference_utils.js -> utils/preference_utils.js
src/utils/team_utils.js -> utils/team_utils.js
src/utils/theme_utils.js -> utils/theme_utils.js
src/utils/user_utils.js -> utils/user_utils.js
Done in 10.57s.
make[1]: Verzeichnis „/home/fries/mattermost-mobile“ wird verlassen
Done in 37.51s.
Generating app assets
Copying assets/base/config.json from base to dist/assets/config.json
Copying assets/base/i18n/de.json from base to dist/assets/i18n/de.json
Copying assets/base/i18n/en.json from base to dist/assets/i18n/en.json
Copying assets/base/i18n/es.json from base to dist/assets/i18n/es.json
Copying assets/base/i18n/fr.json from base to dist/assets/i18n/fr.json
Copying assets/base/i18n/it.json from base to dist/assets/i18n/it.json
Copying assets/base/i18n/ja.json from base to dist/assets/i18n/ja.json
Copying assets/base/i18n/ko.json from base to dist/assets/i18n/ko.json
Copying assets/base/i18n/nl.json from base to dist/assets/i18n/nl.json
Copying assets/base/i18n/pl.json from base to dist/assets/i18n/pl.json
Copying assets/base/i18n/pt-BR.json from base to dist/assets/i18n/pt-BR.json
Copying assets/base/i18n/ru.json from base to dist/assets/i18n/ru.json
Copying assets/base/i18n/tr.json from base to dist/assets/i18n/tr.json
Copying assets/base/i18n/zh-CN.json from base to dist/assets/i18n/zh-CN.json
Copying assets/base/i18n/zh-TW.json from base to dist/assets/i18n/zh-TW.json
Copying assets/base/images/gitlab.png from base to dist/assets/images/gitlab.png
Copying assets/base/images/icon.png from base to dist/assets/images/icon.png
Copying assets/base/images/icons/audio.png from base to dist/assets/images/icons/audio.png
Copying assets/base/images/icons/code.png from base to dist/assets/images/icons/code.png
Copying assets/base/images/icons/excel.png from base to dist/assets/images/icons/excel.png
Copying assets/base/images/icons/generic.png from base to dist/assets/images/icons/generic.png
Copying assets/base/images/icons/image.png from base to dist/assets/images/icons/image.png
Copying assets/base/images/icons/patch.png from base to dist/assets/images/icons/patch.png
Copying assets/base/images/icons/pdf.png from base to dist/assets/images/icons/pdf.png
Copying assets/base/images/icons/ppt.png from base to dist/assets/images/icons/ppt.png
Copying assets/base/images/icons/video.png from base to dist/assets/images/icons/video.png
Copying assets/base/images/icons/webhook.jpg from base to dist/assets/images/icons/webhook.jpg
Copying assets/base/images/icons/word.png from base to dist/assets/images/icons/word.png
Copying assets/base/images/icons/youtube-play-icon.png from base to dist/assets/images/icons/youtube-play-icon.png
Copying assets/base/images/logo.png from base to dist/assets/images/logo.png
Copying assets/base/images/menu.png from base to dist/assets/images/menu.png
Copying assets/base/images/profile.jpg from base to dist/assets/images/profile.jpg
Copying assets/base/images/send.png from base to dist/assets/images/send.png
Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying<EMAIL_ADDRESS>from base to<EMAIL_ADDRESS>Copying assets/base/themes.json from base to dist/assets/themes.json
fries@fries-virtual-machine:~/mattermost-mobile$ make unsigned-android
error: no devices/emulators found
Checking for style guide compliance
Starting React Native packager server
Building unsigned Android app
/bin/sh: 1: bundle: not found
Makefile:215: die Regel für Ziel „do-unsigned-android“ scheiterte
make: *** [do-unsigned-android] Fehler 127
fries@fries-virtual-machine:~/mattermost-mobile$ [RemoteDev] Start server...

[Busy] Launching SocketCluster
[Active] SocketCluster started
Version: 6.8.0
Environment: dev
WebSocket engine: uws
Port: 5678
Master PID: 1657
Worker count: 1
Broker count: 1

┌────────────────────────────────────────────────────────────────────────────┐
│  Running packager on port 8081.                                            │
│                                                                            │
│  Keep this packager running while developing on any JS projects. Feel      │
│  free to close this tab and run your own packager instance if you          │
│  prefer.                                                                   │
│                                                                            │
│  https://github.com/facebook/react-native                                  │
│                                                                            │
└────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
/home/fries/mattermost-mobile
React packager ready.
Loading dependency graph, done.
fries@fries-virtual-machine:~/mattermost-mobile$
`
Do I need a virtual device in order to make a apk file?
Greetings

@enahum
this is the issue that I faced after the command :-
make check-device-android
/bin/sh: 2: @echo: not found
/bin/sh: 3: @exit: not found
Makefile:116: recipe for target 'check-device-android' failed
make: *** [check-device-android] Error 127

@prateekpandey44 we’ve made some changes to our Makefile and this should not happen now when running make check-device-android

@MamoulianDelacroix @enahum
apt-get install bundler

cd fastlane

bundle install

was necessary for me to fix "bundle: not found".
apt-get install lib32stdc++6 lib32z1

was necessary to get aapt working (from https://stackoverflow.com/a/28231767)

This documentation might help resolve your issue.


Add new rule for detecting potential performance-related bugs

New rule for detecting potential performance-related bugs.
Checklist

[ ] Type annotations added to new functions
[ ] Docs added to functions touched in main classes
[ ] Dry-run produced the expected results
[ ] The to-be-announced tag added if this is worth announcing

Dry-Run

Hi there,

The following bugs are probably performance related and don't have performance impact value:

Bug
Summary
Confidence (%)

1876285

Constant high cpu & gpu usage + framerate degredation on beatport.com
25

1876263

See how much we can optimize `all` transition handling.
24

1876157

Nightly-as-release builds are slower than regular Nightly builds (not PGO'ing properly)
35

1876051

test_fetch perf test takes a long time with http/3
28

1875469

High CPU use on gmail.com due to exzessive window.message usage (blocking other tabs from loading)
32

            Sincerely,

            BugBot

                See the search query on Bugzilla.

        See the source / report issues on the GitHub repo


chore: 0.1.2 release

Pull Request Test Coverage Report for Build 40
Details

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

Totals

Change from base Build 39:
0.0%

Covered Lines:
126

Relevant Lines:
133

💛  - Coveralls


Deploy only if RC is released

Our RC test workflow was updating the deployment and running the master DAG even if there was no RC release. This PR only initiates deployment and DAG triggers when we have an RC release.

is this PR needed @vatsrahul1001 ?

@vatsrahul1001 can we merge this if we were able to test this?


Support for multipart/mixed Content-Type?

Does Flask have support for working with multipart/mixed Content-Type?
If so, HOW? I'm having really hard time trying to understand how to do this.

The only request bodies that Werkzeug knows how to parse are form data and JSON. Otherwise, you need to parse it yourself. There are many functions in Werkzeug, especially  werkzeug.http (with examples of how to use them in werkzeug.formparser), that may be helpful here. If anything needs to be added, that should be reported against Werkzeug.


Fix terms and add installation commands

Updating Apache guide in Portuguese translation

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Congrats @lcnzg on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Security

I have some users that can not create in the estimate board.  I did however see that there is an issue with the creation on my account being an admin.  I had to put in a Title before anything else, if I didnt I would have to close the dialog and try again.
The issue my user has is following the title creation first the next two dropdowns are grayed out. ( Team Field and Sprint Field) and because there blank the create button is grayed out.
The screen shot if from my user account

This is what the user sees:

Thank you for informing us about this issue. We will investigate it promptly and make the necessary corrections as soon as possible.

is there a permission I need to apply, that would cause this.  it just looks like the users needs something added to there account?  We try to lock down everything is why I'm asking.  If there is something to adjust here let me know.

I will first check the issues to see if they work as expected for me. If they do, we can schedule a web session so that I can assist you further.

I performed a test and checked the code to ensure that nothing was preventing the user from creating a session. I tested it, and it worked as expected.
Could you help us track this down by checking the browser network log (f12 in the browser), and the console log for errors?

Could you help us track this down by checking the browser network log (f12 in the browser), and the console log for errors?

We will close this issue. If you encounter the same problem again, please feel free to create a new issue


Adding TTS Beta samples : Audio profile

@nnegrey
Please review

Fixed and added in the README file updates as well. Please let me know if there is anything else required.

All changes done. Please let me know if this is good to merge.

All done. Hoping we are good to merge.

I signed it!

Per an email from OSPO, nirupa-kumar has a signed CLA.


[Feature-878][shims] support Flink 1.15-SNAPSHOT

What problem does this PR solve?
Issue Number: close #878
Problem Summary: support Flink 1.15-SNAPSHOT

add streamx-flink-shims_flink-1.15

compatible flink-1.15 api

Contribution Checklist

Make sure that the pull request corresponds to a GITHUB issue.

Name the pull request in the form "[Feature] [component] Title of the pull request", where Feature can be replaced by Hotfix, Bug, etc.

Minor fixes should be named following this pattern: [hotfix] [docs] Fix typo in README.md doc.

Purpose of this pull request

@wolfboys PTAL. Considering that flink 1.15 is not released,I use profile to load dependencies,instead of  switching the global flink version.

LGTM.


[WIP] Accept T2w images in recon-all

Starting to track progress on T2w incorporation.
Follow-up to #347.

I've run a test on sub-s483.
Nipype log excerpts:
170301-02:39:34,493 workflow INFO:
	 Executing node Reconstruction in dir: /scratch/workflow_enumerator/s483/t1w_preprocessing/Reconstruction
170301-02:39:34,498 workflow INFO:
	 Running: recon-all -autorecon1 -i /data/sub-s483/ses-1/anat/sub-s483_T1w.nii.gz -i /data/sub-s483/ses-2/anat/sub-s483_T1w.nii.gz -T2 /data/sub-s483/ses-1/anat/sub-s483_T2w.nii.gz -noskullstrip -hires -openmp 8 -parallel -subjid sub-s483 -sd /out/freesurfer

170301-07:04:35,101 workflow INFO:
	 Executing node Reconstruction2 in dir: /scratch/workflow_enumerator/s483/t1w_preprocessing/Reconstruction2
170301-07:04:35,167 interface INFO:
	 resume recon-all : recon-all -all -noskullstrip -hires -openmp 8 -parallel -subjid sub-s483 -sd /out/freesurfer -T2pial -nomotioncor -notalairach -nonuintensitycor -nonormalization

-T2 flag is being added correctly to recon-all -autorecon1, and -T2pial to recon-all -all.
Waiting to finish to verify that -T2pial runs correctly, but this should be in good shape.
I will note that for hi-res images the inflated surface looks a bit pointy in places, so we may want to reconsider adjusting mris_inflate -n in an expert file. I'm pretty sure the issue I was having with that before is that the output file needed to be marked as needed to avoid being deleted by remove_unnecessary_outputs.

It's freesurfer doing some form of skull stripping on the t2 you had to
take care off?
On Mar 1, 2017 6:26 AM, "Chris Markiewicz"<EMAIL_ADDRESS>wrote:

I've run a test on sub-s483.
Nipype log excerpts:
170301-02:39:34,493 workflow INFO:
Executing node Reconstruction in dir: /scratch/workflow_enumerator/s483/t1w_preprocessing/Reconstruction
170301-02:39:34,498 workflow INFO:
Running: recon-all -autorecon1 -i /data/sub-s483/ses-1/anat/sub-s483_T1w.nii.gz -i /data/sub-s483/ses-2/anat/sub-s483_T1w.nii.gz -T2 /data/sub-s483/ses-1/anat/sub-s483_T2w.nii.gz -noskullstrip -hires -openmp 8 -parallel -subjid sub-s483 -sd /out/freesurfer
170301-07:04:35,101 workflow INFO:
Executing node Reconstruction2 in dir: /scratch/workflow_enumerator/s483/t1w_preprocessing/Reconstruction2
170301-07:04:35,167 interface INFO:
resume recon-all : recon-all -all -noskullstrip -hires -openmp 8 -parallel -subjid sub-s483 -sd /out/freesurfer -T2pial -nomotioncor -notalairach -nonuintensitycor -nonormalization
-T2 flag is being added correctly to recon-all -autorecon1, and -T2pial
to recon-all -all.
Waiting to finish to verify that -T2pial runs correctly, but this should
be in good shape.
I will note that for hi-res images the inflated surface looks a bit pointy
in places, so we may want to reconsider adjusting mris_inflate -n in an
expert file. I'm pretty sure the issue I was having with that before is
that the output file needed to be marked as needed to avoid being deleted
by remove_unnecessary_outputs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/pull/376#issuecomment-283353631,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp9SWVMeli3XRevd2IOtWUZp2ao99ks5rhYABgaJpZM4MN4eC
.

It uses brainmask.mgz, which we're injecting from ANTs. See https://surfer.nmr.mgh.harvard.edu/fswiki/ReconAllTableStableV6.0#line-116.

T2 coregisters fine. I want to try adjusting mris_inflate, because the inflated surface (with and without T2) is kind of pointy in places.

Upping mris_inflate -n definitely makes the inflated surface much smoother, so I'm including that.
No expert:

expert:

This PR is waiting on nipy/nipype#1857. The expert option for ReconAll is needed to mark the expert.opts file as not to be deleted.
Going to do a clean run on Sherlock and report total time.

Interesting. Is there an impact on how reconstructed surfaces look like in
our HTML reports?
On Mar 3, 2017 6:46 AM, "Chris Markiewicz"<EMAIL_ADDRESS>wrote:

Upping mris_inflate -n definitely makes the inflated surface much
smoother, so I'm including that.
No expert:
[image: no_expert]
https://cloud.githubusercontent.com/assets/83442/23555148/c7516a80-fff5-11e6-87fd-029512a7c830.png
expert:
[image: expert]
https://cloud.githubusercontent.com/assets/83442/23555149/c7533f04-fff5-11e6-8665-a808cf4416ad.png
This PR is waiting on nipy/nipype#1857
https://github.com/nipy/nipype/pull/1857. The expert option for ReconAll
is needed to mark the expert.opts file as not to be deleted.
Going to do a clean run on Sherlock and report total time.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/pull/376#issuecomment-283971556,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkpw1anpGxGxk1Or2ETdiqQUSTLnZEks5riCd_gaJpZM4MN4eC
.

So reports uses ?h.white and ?h.pial, and I don't think those are affected by mris_inflate. I believe ?h.sphere is affected, which is used for subject-subject surface registration.

So ?h.white does depend on ?h.inflated in the smoothing stages, as do ?h.sphere. So this isn't purely aesthetic wrt the ?h.inflated surfaces.

I set this as RTM because it works. If you want to wait on Sherlock build, that's fine. (If I can't get Sherlock to work, I'll run on my laptop overnight and give you an 8-core estimate.)

We also should wait for https://github.com/nipy/nipype/pull/1857 to be merged, right?

Oh right. Yes, somehow I forgot that. I'll mark it [WIP] again. Once a final pin is set, I'll set it back to RTM.

SLURM Job_id=13250524 Name=sub-s483 Ended, Run time 09:38:39, COMPLETED, ExitCode 0

I like the explicit threshold. Just make sure you cast everything to float!
On Sat, Mar 4, 2017 at 11:04 AM, Chris Markiewicz<EMAIL_ADDRESS>wrote:

@effigies commented on this pull request.
In fmriprep/workflows/anatomical.py
https://github.com/poldracklab/fmriprep/pull/376#discussion_r104294634:

         t1w_ref = nib.load(t1w_list[0])

       hires = max(t1w_ref.header.get_zooms()) < 1

       hires = round(max(t1w_ref.header.get_zooms()), 1) < 1

Woops. Lost the thread in the rebase. Recap:
@oesteban https://github.com/oesteban suggested we set an explicit
threshold, rather than round.
hires = np.all(np.array(t1w_ref.header.get_zooms()) - 1 < -tol)
Where tol here = 0.05.
If we're going to do that, I'd prefer to stick with the max formulation,
and keep constants on the right-hand-side, e.g.:
hires = max(t1w_ref.header.get_zooms()) < 1 - 0.05
I'll do whatever the consensus is, but I think the round(max(zooms), 1) <
1 and max(zooms) < 1 - tol are the most readable options. Opinions,
@chrisfilo https://github.com/chrisfilo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/pull/376#pullrequestreview-25130057,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp4qUZK6zZ9lf-_TRbMW3z3YFJc6aks5ribW-gaJpZM4MN4eC
.

I don't see where casting is required... even if zooms are int (Nifti zooms are 'f4', anyway), numerical comparisons aren't going to be affected by an explicit cast. Am I missing something?

LGTM

Another run, following the nipype PR: Run time 09:22:15

LGTM too

+1
On Mar 5, 2017 8:33 PM, "Oscar Esteban"<EMAIL_ADDRESS>wrote:

LGTM too
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/poldracklab/fmriprep/pull/376#issuecomment-284300698,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOkp1AeppbnqtiuBqGs2XOJSPUluSvjks5ri4yEgaJpZM4MN4eC
.


DSD-390: Adding the indeterminate state to the Checkbox component.

Fixes JIRA ticket DSD-390
This PR does the following:

Adds the "indeterminate" state to the Checkbox component and adds an example in the CheckboxGroup.
Adds a fix to a DatePicker unit test which I'll have to redo in other PRs or make a separate ticket into development.

How has this been tested?
Storybook.
Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] All new and existing tests passed.

Front End Review:

[ ] View the example in Storybook

Tugboat has finished building the preview for this pull request!
Link:

https://pr747-zz8kxrnxtaokkzs7yaopgpefrolevgov.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61800b569468f86339239b63

@bigfishdesign13  updated. I set the initial isChecked prop value to false and it could not be updated. The  Checked and Indeterminate stories shouldn't be clickable. Those checkboxes are controlled by the isChecked and isIndeterminate props, respectively. In order to uncheck or remove the indeterminate state, those props must be removed or set to false.

Tugboat has finished building the preview for this pull request!
Link:

https://pr747-zz8kxrnxtaokkzs7yaopgpefrolevgov.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61800b569468f86339239b63


[Rust] Support Taproot, Ordinals and BRC20

About
In order to implement BRC20, we need to support the Ordinal protocol, which requires Taproot. Respectively, wallet-core must be able to create "inscriptions".
From the docs:

Inscription content is entirely on-chain, stored in taproot script-path spend scripts. Taproot scripts have very few restrictions on their content, and additionally receive the witness discount, making inscription content storage relatively economical.

Since taproot script spends can only be made from existing taproot outputs, inscriptions are made using a two-phase commit/reveal procedure. First, in the commit transaction, a taproot output committing to a script containing the inscription content is created. Second, in the reveal transaction, the output created by the commit transaction is spent, revealing the inscription content on-chain.

Inscriptions are created with the following Bitcoin script (which never executes):
OP_FALSE
OP_IF
  OP_PUSH "ord"
  OP_1
  OP_PUSH "text/plain;charset=utf-8"
  OP_0
  OP_PUSH "Hello, world!"
OP_ENDIF

Related:

https://github.com/trustwallet/wallet-core/discussions/3155
https://github.com/trustwallet/wallet-core/issues/1785
https://github.com/trustwallet/wallet-core/issues/3119

Task List
Part 1:

UPDATE 2023-05-26
I found a Rust project that implements many of Bitcoin mechanisms: https://github.com/rust-bitcoin/rust-bitcoin/
I'm using this to build a MVP as of now and digging through the source code. We can still decide on whether we want to include the full library or strip out the parts that we need.

[x] Implemented a mechanism to build transactions with custom Scripts (builder pattern).
[x] Sign transactions with our tw_keypair crate.

[x] Write unit tests for this, test against bitcoind RPC (regtest mode) output.

[x] Encode (signed) transaction.
[x] Implement builder pattern for ordinals.

[x] Implement the construction of Taproot addresses.
[ ] Extend Script.cpp with a buildPayToTaproot function, which must support two ways of spending the outputs:

2023-05-26: This will wrap over the Rust code.
[x] key-path: Spend output with Schnorr signatures and pubkey (the easier way).

2023-05-26: rust-bitcoin handles this for us.

[x] script-path: Spend output with a Merkle branch (the harder way). Do note that the Ordinal docs explicitly mention this, meaning we need to implement the Merkle tree in order to support Ordinals/BRC20 (I first assumed that we could do this later).

2023-05-26: rust-bitcoin handles this for us.

[ ] Extend Script.cpp with any required witnessData construction.

2023-05-26: This will wrap over the Rust code.

[x] Implement the construction of the Merkle tree and the extraction of any of its branches.

This one might be tricky but I have experience with Merkle trees. Had to deal with the specification of that at my previous role (no this one specifically, though): https://spec.polkadot.network/chap-state#sect-state-storage
2023-05-26: rust-bitcoin handles this for us.

[x] ~Extend our Rust curve implemenation with Schnorr support (straight forward to do since we rely on k256)~

2023-05-26: rust-bitcoin uses the secp256k1 library underneath, which we got rid-off. I'll try to integrate this with k256, if possible.
2023-06-05: tw_keypair is on hold (audit related), so we'll just stick with secp256k1 for now which already has support for Schnorr signatures and public key tweaking.

[x] Add derivation support for Taproot (BIP86)

[x] Derivation support for Bitcoin is already implemented and which we can reuse. Taproot address is now generated from the public key.

For the sake of completeness, we should eventually work on this:

[x] Implement the generation of Segwit addresses.

Right now we only support sending to Segwit addresses, but not receiving to a Segwit address.
We might get this for free when implementing Taproot, I'll see.

Part 2:

[x] Implement construction of Ordinal Inscriptions.
[x] ~Implement "Ordinal Theory" and how it results in the handling of Taproot outputs.~

2023-06-05: That part is handled by the indexer (network layer). From the wallet-core perspective, we just construct whatever inputs/outputs are provided via FFI.

[x] (optional) Implement deployment of BRC20 tokens.
[x] (optional?) Implement the minting of BRC20 tokens.
[x] Implement the transfer of BRC20 tokens.

Hi lamafab，
Thank you for your great work. I would like to know when the development can be completed and released?

@vccomnet just opened this last night -> https://github.com/trustwallet/wallet-core/pull/3233, almost there!

It's done

Can i generate taproot address with wallet-core now? i uesd @trustwallet/wallet-core.

Hey @weixuefeng no it's not possible, there is the current status:
- Support for **BRC20 transfers**, sending and receiving:
    - [x]  Implemented and tested in Wallet Core.
    - [x]  Publicly exposed (high priority).
- Support for P2WPKH (**Segwit**), sending and receiving:
    - [x]  Implemented and tested in Wallet Core.
    - [ ]  Publicly exposed via C interface (low priority).
- Support for P2TR key-path (**Taproot**), sending and receiving:
    - [x]  Implemented and tested in Wallet Core.
    - [ ]  Publicly exposed via C interface (low priority).

Hey @weixuefeng no it's not possible, there is the current status:

Support for BRC20 transfers, sending and receiving:

[x]   Implemented and tested in Wallet Core.
[x]   Publicly exposed (high priority).

Support for P2WPKH (Segwit), sending and receiving:

[x]   Implemented and tested in Wallet Core.
[x]    Publicly exposed

Support for P2TR key-path (Taproot), sending and receiving:

[x]   Implemented and tested in Wallet Core.
[ ]   Publicly exposed via C interface (low priority).

Hi Milerius, is it exposed to C interface now? can I generate taproot address in the iOS App or Android App?

Hey @hanxianlong, it's not exposed yet. We're planning this for Q1 2024.


⚠ Bofrost.fr has degraded performance

In 7c786b5, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 934 ms

Resolved: Bofrost.fr performance has improved in 8e38e7c after 7 minutes.


Fix ocaml kernel hangs in jupyterlab

Fix #69

Thank you! I reproduced the bug and your patch works well.


TFoS Key Input Error

Hi,
Below is the spark-submit for the TF 1.2 Version and getting error from TFManager.py.could you please advice on this.
$spark-submit --master yarn --deploy-mode client --queue root --num-executors 4 --executor-memory 24G --executor-cores 4 --driver-memory 8G --py-files TensorFlowOnSpark/examples/mnist/spark/mnist_dist.py --conf spark.dynamicAllocation.enabled=false --conf spark.yarn.maxAppAttempts=1 --conf spark.executorEnv.LD_LIBRARY_PATH="$LIB_HDFS:$LIB_JVM" --conf spark.executorEnv.HADOOP_HDFS_HOME="$HADOOP_HDFS_HOME" --conf spark.executorEnv.CLASSPATH="$($HADOOP_PREFIX/bin/hadoop classpath --glob):${CLASSPATH}" TensorFlowOnSpark/examples/mnist/spark/mnist_spark.py --images examples/mnist/csv/train/images --labels examples/mnist/csv/train/labels --mode train --model hdfs:///user/xyz/mnist_model --steps 6000 --epochs 1
RemoteError:
Traceback (most recent call last):
File "/data/anaconda/4.3.1/2/lib/python2.7/multiprocessing/managers.py", line 207, in handle_request
result = func(c, *args, **kwds)
File "/data/anaconda/4.3.1/2/lib/python2.7/multiprocessing/managers.py", line 386, in create
obj = callable(*args, **kwds)
File "/data/anaconda/4.3.1/2/lib/python2.7/site-packages/tensorflowonspark/TFManager.py", line 45, in
TFManager.register('get_queue', callable=lambda qname: qdict[qname])
KeyError: 'input'
    at org.apache.spark.api.python.PythonRunner$$anon$1.read(PythonRDD.scala:193)
    at org.apache.spark.api.python.PythonRunner$$anon$1.<init>(PythonRDD.scala:234)
    at org.apache.spark.api.python.PythonRunner.compute(PythonRDD.scala:152)
    at org.apache.spark.api.python.PythonRDD.compute(PythonRDD.scala:63)
    at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:323)
    at org.apache.spark.rdd.RDD.iterator(RDD.scala:287)
    at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:87)
    at org.apache.spark.scheduler.Task.run(Task.scala:108)
    at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:335)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:744)

This generally means that there are more Spark task slots available than TensorFlow cluster nodes.  In your case, I think you should use --executor-cores 1, which tells Spark to not schedule more than a single task per executor.

Does that mean that we cannot take advantage of all the cores ?

@krishdey No, I'm pretty sure that's not what that means.
Here is a good reference on spark tuning.  The key phrase is:
"The cores property controls the number of concurrent tasks an executor can run. --executor-cores 5 means that each executor can run a maximum of five tasks at the same time."
So, I'm fairly certain that this is just a scheduling hint to Spark (vs. some hard physical limit at a kernel/hw level).  As another example, you can follow this code to see how this setting is used within the Spark code.  In our case, we just want to ensure that we place only one (TensorFlow) task per executor.

Closing due to inactivity.  Feel free to open if this is still an issue.


[Bug]: Don't use cluster label in PodMonitor

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
<EMAIL_ADDRESS>Version
1.24.0
What version of Kubernetes are you using?
1.31
What is your Kubernetes environment?
Self-managed: kind (evaluation)
How did you install the operator?
YAML manifest
What happened?
The cluster label in PodMonitor should be renamed to something like pg_cluster because Prometheus Stack and VictoriaMetrics Stack already use it in multicluster monitoring setups, therefore cluster label of CNPG is overwritten by cluster label by Prometheus.
Cluster resource
No response
Relevant log output
No response
Code of Conduct

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

Oops
https://github.com/cloudnative-pg/cloudnative-pg/issues/2501


DownloadBuildArtifacts buildVersionToDownload option does not have any documentation.

Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Environment

Server: Azure Pipelines

Account: jellyfin-project
Project: jellyfin

Agent: Hosted Ubuntu

Issue Description
So the option does not have a doc string: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/download-build-artifacts?view=azure-devops
It says "(Required) undefined".
And some context
Used here: https://github.com/jellyfin/jellyfin/pull/1091
DownloadBuildArtifacts@0 does not seem to actually download the artifacts from the latest build from the given branch when the option buildVersionToDownload is set to latestFromBranch. And the build is current, which might be by design, but is undocumented.
The goal is to download a previous non-PR build that succeeds to compare the two artifacts for ABI compatibility.
Download 1 YAML:
- task: DownloadBuildArtifacts@0
      displayName: Download the Reference Assembly Build Artifact
      inputs:
        buildType: 'current' # Options: current, specific
        buildVersionToDownload: 'latestFromBranch' # Required when buildType == Specific# Options: latest, latestFromBranch, specific
        allowPartiallySucceededBuilds: false # Optional
        branchName: '$(System.PullRequest.TargetBranch)' # Required when buildType == Specific && BuildVersionToDownload == LatestFromBranch
        downloadType: 'single' # Options: single, specific
        artifactName: '$(NugetPackageName)'# Required when downloadType == Single
        downloadPath: '$(System.ArtifactsDirectory)/current-artifacts'

Download 2 YAML:
- task: DownloadBuildArtifacts@0
      displayName: Download the New Assembly Build Artifact
      inputs:
        buildType: 'current' # Options: current, specific
        allowPartiallySucceededBuilds: false # Optional
        downloadType: 'single' # Options: single, specific
        artifactName: '$(NugetPackageName)' # Required when downloadType == Single
        downloadPath: '$(System.ArtifactsDirectory)/new-artifacts'

Task logs
This specific build, demonstrates the problem
https://dev.azure.com/jellyfin-project/jellyfin/_build/results?buildId=33
Result 1
Downloading artifacts for build: 33
Downloading items from container resource #/2624379/Jellyfin.Naming
Downloading artifact Jellyfin.Naming from: https://dev.azure.com/jellyfin-project//_apis/resources/Containers/2624379?itemPath=Jellyfin.Naming&isShallow=true&api-version=4.1-preview.4
Downloading Jellyfin.Naming/Emby.Naming.dll to /home/vsts/work/1/a/current-artifacts/Jellyfin.Naming/Emby.Naming.dll
Downloaded Jellyfin.Naming/Emby.Naming.dll to /home/vsts/work/1/a/current-artifacts/Jellyfin.Naming/Emby.Naming.dll
Total Files: 1, Processed: 1, Skipped: 0, Failed: 0, Download time: 1.009 secs, Download size: 23637Bytes
Successfully downloaded artifacts to /home/vsts/work/1/a/current-artifacts

Result 2
Downloading artifacts for build: 33
Downloading items from container resource #/2624379/Jellyfin.Naming
Downloading artifact Jellyfin.Naming from: https://dev.azure.com/jellyfin-project//_apis/resources/Containers/2624379?itemPath=Jellyfin.Naming&isShallow=true&api-version=4.1-preview.4
Downloading Jellyfin.Naming/Emby.Naming.dll to /home/vsts/work/1/a/new-artifacts/Jellyfin.Naming/Emby.Naming.dll
Downloaded Jellyfin.Naming/Emby.Naming.dll to /home/vsts/work/1/a/new-artifacts/Jellyfin.Naming/Emby.Naming.dll
Total Files: 1, Processed: 1, Skipped: 0, Failed: 0, Download time: 1.009 secs, Download size: 23637Bytes
Successfully downloaded artifacts to /home/vsts/work/1/a/new-artifacts

Newer builds also have issues with the specific build config, but that is probably purely user error. ALthough the documentation does not really give any pointers.

@EraYaN I see that the documentation for the field is updated now at https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/utility/download-build-artifacts?view=azure-devops. If you are still running into any issues with the new version of task let us know.


Adding support for rOCCI-server v2

Overview

New flag --rocci-remote-templates for use with rOCCI-server v2
Scoped pool info (no user-defined images or templates published)
Added --cloudkeeper-images alias for --vmcatcher-images
Minor adjustments in configuration samples

Important
--rocci-remote-templates tells the provider to pull resource templates from OCA (OpenNebula's XML-RPC API), not from a local directory. This option is REQUIRED for deployments with rOCCI-server v2+.

This PR still needs a bit of work. Mainly testing and code clean-up.

Hi Boris,
Thanks, so this should be compatible with all the rOCCI server versions?
Best,
Baptiste

Hi @gwarf ,
yes, it should be backwards compatible. With rOCCI-server < 2, no changes. For rOCC-server >= 2, use --rocci-remote-templates and --rocci-template-dir will be ignored.

@gwarf Can we push this for release ASAP? It is a requirement for the upcoming rOCCI-server v2 stable release. If there is anything you need me to do, pls, let me know.

LGTM. Thanks Boris! :+1:


[BUG] released version Cargo.lock is out of date

Describe the bug
I'm picking up my effort to package this for nixpkgs, but:
       > Executing cargoSetupPostPatchHook
       > Validating consistency between /build/source/Cargo.lock and /build/tplay-0.4.5-vendor.tar.gz/Cargo.lock
       > Finished cargoSetupPostPatchHook
       > updateAutotoolsGnuConfigScriptsPhase
       > configuring
       > building
       > Executing cargoBuildHook
       > ++ env CC_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/cc CXX_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/c++ CC_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/cc CXX_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/c++ cargo build -j 16 --target x86_64-unknown-linux-gnu --frozen --release
       > error: the lock file /build/source/Cargo.lock needs to be updated but --frozen was passed to prevent this
       > If you want to try to generate the lock file without accessing the network, remove the --frozen flag and use --offline instead.

The key part:
 error: the lock file /build/source/Cargo.lock needs to be updated but --frozen was passed to prevent this

@colemickens I'm not sure how I can fix this on my end.
I can see that the --frozen flag is passed to it in the command cargoBuildHook, is that part of the Nix  package manager? If you can control that try to remove the --frozen flag and try again
   > ++ env CC_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/cc CXX_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/c++ CC_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/cc CXX_x86_64-unknown-linux-gnu=/nix/store/75slks1wr3b3sxr5advswjzg9lvbv9jc-gcc-wrapper-12.3.0/bin/c++ cargo build -j 16 --target x86_64-unknown-linux-gnu **--frozen** --release

Sorry, I should've been more explicit. Simply regenerating and checking in the Cargo.lock is sufficient to bypass this problem. However, I can't figure out how to get opencv+clang+rust to cooperate. (If you're curious: https://github.com/NixOS/nixpkgs/pull/229526, but it's almost certainly a Nix/my ignorance problem)

ah I see, I may have forgotten to run cargo update after the latest changes, I'll refresh the cargo lock now

@colemickens done. I'll close this issue for now, let me know if there are other problems :)

ah wait, does it mean I need to re-publish the crate?

We (nixpkgs) prefer to point to tagged versions, but since I'm blocked on the build issue I mentioned, there's no rush. And in the meantime I can simply pin to the latest git revision.

I'd consider this closed, unless you want to dive into Nix and fix the hairy build issue :wink: . Either way, closing this. Thanks for the fast turn-around!

Sorry, I should've been more explicit. Simply regenerating and checking in the Cargo.lock is sufficient to bypass this problem. However, I can't figure out how to get opencv+clang+rust to cooperate. (If you're curious: NixOS/nixpkgs#229526, but it's almost certainly a Nix/my ignorance problem)

OpenCV was a big headache for me too, if you don't get every duck in a row it's a path of pain! I'll look into it but I doubt I will be of help

@colemickens did you try by any chance to install libstdc++-12-dev as part of the dependencies?
It was reported (#27) to resolve installation errors ( not the same as yours but you never know..)


We do not need a separate coverage module

Description:
It is unnecessary to have a separate module to generate the coverage. We should merge and create one testgrid-core module that has the binary and tests with coverage.
https://github.com/wso2/testgrid/tree/master/test/coverage
Affected Product Version:
0.9.0-m10
OS, DB, other environment details and versions:
N/A
Steps to reproduce:
https://github.com/wso2/testgrid/tree/master/test/coverage
Related Issues:
N/A

@kasunbg IMO we need to have the coverage module as a separate since coverage is for all the modules and is not apart of the core. WDYT?

We need to merge all our sub-modules except 'web' and 'distribution' module into one core module. IMO it is not correct to have dao, infra, reporting etc. are just need to be separate java packages, not in separate modules.

Closing due to low priority and the current repository structure is fixed ATM.


BingGPT support?

Can u add support for BingGPT? Thanks in advance

for example https://www.bing.com/search?q=what+are+some+which+industries+threated+by+generative+ai%3F


Sampler choices for finetuned stable diffusion model

The stable diffusion model finetuned with Pokemon dataset works well with DDIM sampler but works poorly with PLMS sampler.

The first one is using ddim and second is using plms, all other params are the same.

I used "512-base-ema.ckpt" of stable diffusion v2 and parameterization: "v" in the finetuning.

That is interesting, not something I've looked into. I do remember some anecdotal evidence that dream booth worked better with ddim too.

这很有趣，不是我研究过的东西。我确实记得一些轶事证据表明，梦想展位在 ddim 中也效果更好。

Traceback (most recent call last):
File "/content/stable-diffusion/main.py", line 923, in
raise err
File "/content/stable-diffusion/main.py", line 905, in
trainer.fit(model, data)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 553, in fit
self._run(model)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 918, in _run
self._dispatch()
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 986, in _dispatch
self.accelerator.start_training(self)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/accelerators/accelerator.py", line 92, in start_training
self.training_type_plugin.start_training(trainer)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 161, in start_training
self._results = trainer.run_stage()
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 996, in run_stage
return self._run_train()
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/trainer/trainer.py", line 1045, in _run_train
self.fit_loop.run()
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/base.py", line 111, in run
self.advance(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/fit_loop.py", line 200, in advance
epoch_output = self.epoch_loop.run(train_dataloader)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/base.py", line 111, in run
self.advance(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 130, in advance
batch_output = self.batch_loop.run(batch, self.iteration_count, self._dataloader_idx)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 101, in run
super().run(batch, batch_idx, dataloader_idx)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/base.py", line 111, in run
self.advance(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 148, in advance
result = self._run_optimization(batch_idx, split_batch, opt_idx, optimizer)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 202, in _run_optimization
self._optimizer_step(optimizer, opt_idx, batch_idx, closure)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 396, in _optimizer_step
model_ref.optimizer_step(
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/core/lightning.py", line 1618, in optimizer_step
optimizer.step(closure=optimizer_closure)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/core/optimizer.py", line 209, in step
self.__optimizer_step(*args, closure=closure, profiler_name=profiler_name, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/core/optimizer.py", line 129, in __optimizer_step
trainer.accelerator.optimizer_step(optimizer, self._optimizer_idx, lambda_closure=closure, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/accelerators/accelerator.py", line 296, in optimizer_step
self.run_optimizer_step(optimizer, opt_idx, lambda_closure, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/accelerators/accelerator.py", line 303, in run_optimizer_step
self.training_type_plugin.optimizer_step(optimizer, lambda_closure=lambda_closure, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 226, in optimizer_step
optimizer.step(closure=lambda_closure, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/optim/lr_scheduler.py", line 65, in wrapper
return wrapped(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/optim/optimizer.py", line 113, in wrapper
return func(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/optim/adamw.py", line 119, in step
loss = closure()
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 236, in _training_step_and_backward_closure
result = self.training_step_and_backward(split_batch, batch_idx, opt_idx, optimizer, hiddens)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 537, in training_step_and_backward
result = self._training_step(split_batch, batch_idx, opt_idx, hiddens)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/loops/batch/training_batch_loop.py", line 307, in _training_step
training_step_output = self.trainer.accelerator.training_step(step_kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/accelerators/accelerator.py", line 193, in training_step
return self.training_type_plugin.training_step(*step_kwargs.values())
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/plugins/training_type/ddp.py", line 383, in training_step
return self.model(*args, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/parallel/distributed.py", line 1008, in forward
output = self._run_ddp_forward(*inputs, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/parallel/distributed.py", line 969, in _run_ddp_forward
return module_to_run(*inputs[0], **kwargs[0])
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/pytorch_lightning/overrides/base.py", line 82, in forward
output = self.module.training_step(*inputs, **kwargs)
File "/content/stable-diffusion/ldm/models/diffusion/ddpm.py", line 406, in training_step
loss, loss_dict = self.shared_step(batch)
File "/content/stable-diffusion/ldm/models/diffusion/ddpm.py", line 872, in shared_step
x, c = self.get_input(batch, self.first_stage_key)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/content/stable-diffusion/ldm/models/diffusion/ddpm.py", line 725, in get_input
encoder_posterior = self.encode_first_stage(x)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/content/stable-diffusion/ldm/models/diffusion/ddpm.py", line 869, in encode_first_stage
return self.first_stage_model.encode(x)
File "/content/stable-diffusion/ldm/models/autoencoder.py", line 325, in encode
h = self.encoder(x)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/stable-diffusion/ldm/modules/diffusionmodules/model.py", line 439, in forward
hs = [self.conv_in(x)]
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl
return forward_call(*input, **kwargs)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 457, in forward
return self._conv_forward(input, self.weight, self.bias)
File "/content/stable-diffusion/env/lib/python3.9/site-packages/torch/nn/modules/conv.py", line 453, in _conv_forward
return F.conv2d(input, weight, bias, self.stride,
RuntimeError: Given groups=1, weight of size [128, 3, 3, 3], expected input[512, 1, 512, 3] to have 3 channels, but got 1 channels instead
Pleae help me

Looks like somehow your images it not the right shape, should be 1,3,512,512. The code expects nhwc images out of your dataset I think, and converts to nchw somewhere else


sgadmin.sh doesn't work when invoked from a symlink

I have some slightly odd deployment requirements that require me to run sgadmin.sh from a specific directory. When invoked from the symlink, sgadmin.sh sets the classpath argument to java relative to the symlink:
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

This should account for being called from a symlink like so:
DIR="$( cd "$( dirname "$( realpath "${BASH_SOURCE[0]}" )" )" && pwd )"

can you prepare a pull request for that?

I need to request permission from my employer for formal contributions, which could take... an indeterminate amount of time. I'm using a patch file in my deployment to get sgadmin.sh correct, but it could be some time before I can open a PR

@floragunncom Was it intentional for https://github.com/floragunncom/search-guard/commit/bf56ecf8e0224238a6e7424acdef83a334a413e2#diff-7715bbac7a963d83a2abdb87c46f1a5b to swallow the usage info printed when sgadmin is invoked with no args?

Only stderr (not stdout) gets swallowed to /dev/null and the nor arg usage gets printed out on stdout. I just verified this and I see the usage info as expected.

fixed with v24.1 (also for hash.sh and the demo installer)


Upgrade ebpf builder images, remove hack

Gimme is now part of the build image.

We shouldn't mix versions of the same image on different jobs, but for different images I think it's fine. We can discuss this though.


"noOptions" slot is not documented

Reproduction Link
Steps to reproduce
           <slot name="noOptions">List is empty.</slot> Isn't documented

Expected behaviour
the slot is useful and need to be in the API list.
Actual behaviour
the slot isn't in the list and I was forced to find it in the source code.

:+1: for that and for showNoOptions config option to completely disable this slot (useful when using debounce + async)

noOptions attr was already documented here https://github.com/shentao/vue-multiselect/pull/854
But it seems the page was not updated

Warning...

Looks like this was fixed elsewhere as noOptions slot is documented, as you can see at https://vue-multiselect.js.org/#sub-slots


WIP: Port 3d testing to BackgroundPlotter completely

This PR ports testing of the PyVista 3d backend to the BackgroundPlotter completely.
As a consequence, the variable MNE_3D_BACKEND_TESTING needs refactoring.
Known issue

The dimensions of a screenshot taken with the BackgroundPlotter are not equal to win_height x win_width x 3 but slightly less. I suppose that the real dimensions taken into account are effectively those of the render view (which is smaller than the window).

I reported this behaviour in https://github.com/pyvista/pyvista/issues/703

One way to mitigate this issue is to use setMinimumSize() on the render view widget so that the window don't automatically shrink it.

the window does not automatically shrink it.

The drawback is that the user is no longer able to resize the window to a geometry smaller then window_size.

This can be relevant to https://github.com/mne-tools/mne-python/pull/7211 (about minimum/fixed widget geometry)

The drawback is that the user is no longer able to resize the window to a geometry smaller then window_size.

Can you set this until the super init finishes, then un-set it?

I use it after BackgroundPlotter init to resize the render view. I'll see if there is a way to un-set it without updating the geometry of the window.

I use it after BackgroundPlotter init to resize the render view.

Can you see if it's possible to do before initializing the view? It should help prevent more jerky resizes, if those happen with the current approach

The window is resized before being shown so I don't think this will lead to jerkiness. But this is a workaround without a way to setting it at init. So far, locally the main issue I notice is with show_traces=True. When the window opens:

I have to manually resize to get all the content:

Also, the CIs do not seem to like those changes.

Probably whatever setMinSize you do for the 3D area, you need to do for the 2D area as well. Maybe at 1/4 of whatever the requested 3D vertical size is?

For now you could assert_allclose(shape, expected_shape, atol=40)  # XXX undo once size fixed or so to get things to pass. Seems worth it to get the actual BackgroundPlotter used, then we can deal with fixing the size separately

Awesome idea, thank you. I was stuck with SetMinimumSize() tbh

The Azure failure is fixed by #7740, but I couldn't see the failed OSX log so I restarted that build.

Failures on OSX apparently seem real
https://travis-ci.org/github/mne-tools/mne-python/builds/683971748

Actually if https://github.com/mne-tools/mne-python/pull/7758 is chosen, I would prefer to keep testing on both plotters.


ddev start could check to see if database type matches existing database type

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe
When you change the database type in config.yaml, you may or may not be able to start the project. It tries to upgrade if possible, but mariadb:10.3 to mysql:8.0 or postgres:14 will never ever work.
The previous version is actually stored in /var/lib/mysql/db_mariadb_version.txt, but it's hard to get at that (requires running a container with the volume mounted), so would slow down start.
But the results when somebody does a change are pretty ugly, and they have to do a ddev logs -s db to figure out what happened.
But ddev could store away the previous version, for example in ~/.ddev/global_config.yaml like it does with used_host_ports:
  d9mysql:
    approot: /Users/rfay/workspace/d9mysql
    used_host_ports: ["9999"]

Describe the solution you'd like
Above
Describe alternatives you've considered
Mounting the db volume and looking at the file.
Additional context
No response

After update to version 1.21 i have this problem on every project. I fixed it with complete deletings and new setups. But on one project now i miss a google json file. So is there a easier way to do this
Failed to restart nca-sulu: Unable to start project nca-sulu because the configured database type does not match the current actual database. Please change your database type back to  and start again, export, delete, and then change configuration and start. To get back to existing type use 'ddev config --database=' and then you might want to try 'ddev debug migrate-database mariadb:10.6', see docs at https://ddev.readthedocs.io/en/latest/users/extend/database_types/

Maybe this helps
ddev debug get-volume-db-version
Failed to get existing DB type/version: could not split version string 10.3

Also replace mariadb and mysql with
database:
type: mariadb
version: 10.6
still this issue

You're in the wrong issue here. The issue is https://github.com/drud/ddev/issues/4129 and you'll find a couple of solutions there, and also in top of the release notes, https://github.com/drud/ddev/releases/tag/v1.21.1

This scrip and @rfay on discord helps me https://gist.github.com/rfay/27b12e49ceb1ed1e3959c603401b7010


Fix a couple of typos for v1.2

Fix a couple of typos:

Fix a typo in tools/arkmanager - says the SteamCMD exec could not be found, when it should say the ARK server exec could not be found.
Fix a typo in tools/openrc/arkdaemon - should be need net, not require net

Oh - collided with your fix. Closing.


Add Chinese translation support

Hello,
I am an open-source technology enthusiast and am deeply impressed by your pynecone project. I noticed that the project does not yet have Chinese translation support, so I would like to introduce the project to more Chinese developers by creating a Chinese translation document.
I hope to create a Chinese translation document for the latest version of the project and upload it to the README or documentation section of the project, so that Chinese developers can better understand and use the project. I will do my best to ensure the quality of translation based on my translation ability and experience, and submit the documents to the warehouse within two months.
If this meets your requirements, I would be very grateful. If you need to further understand my experience and abilities, or if you would like me to follow specific standards when translating, please let me know.
Thank you for your time and look forward to your reply.
Best regards,
Gaolele

Hello,
just to clarify, but do you mean that:

you want Pynecone to support displaying Chinese text.
you want the documentation to be in Chinese.

I want Pynecone documentation to displaying Chinese text.

Yes feel free to translate the docs, we can chat more on discord.
Maybe an easier starting point would be to translate the readme first on our GitHub?

No problem.

closing this now


Feature lc plotting

added basic light curve plotting. much more to be done

Codecov Report

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

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
- Coverage   89.06%   89.02%   -0.05%
==========================================
  Files          24       27       +3
  Lines         924      984      +60
==========================================
+ Hits          823      876      +53
- Misses        101      108       +7

Impacted Files
Coverage Δ

cosmogrb/io/__init__.py
100.00% <0.00%> (ø)

cosmogrb/sampler/__init__.py
100.00% <0.00%> (ø)

cosmogrb/__init__.py
100.00% <0.00%> (ø)

cosmogrb/lightcurve/light_curve_storage.py
87.64% <0.00%> (-2.61%)
:arrow_down:

Continue to review full report at Codecov.

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

Codecov Report

Merging #4 into master will decrease coverage by 0.04%.
The diff coverage is 86.41%.

@@            Coverage Diff             @@
##           master       #4      +/-   ##
==========================================
- Coverage   89.06%   89.02%   -0.05%
==========================================
  Files          24       27       +3
  Lines         924      984      +60
==========================================
+ Hits          823      876      +53
- Misses        101      108       +7

Impacted Files
Coverage Δ

cosmogrb/lightcurve/gbm_lightcurve.py
90.9% <ø> (ø)
:arrow_up:

cosmogrb/response/response.py
90% <ø> (ø)
:arrow_up:

cosmogrb/io/grb_save.py
98.46% <ø> (-0.03%)
:arrow_down:

cosmogrb/sampler/constant_cpl.py
26.82% <0%> (ø)
:arrow_up:

cosmogrb/grb/grb.py
98.71% <100%> (ø)
:arrow_up:

cosmogrb/sampler/cpl_source.py
97.56% <100%> (ø)
:arrow_up:

cosmogrb/__init__.py
100% <100%> (ø)

cosmogrb/lightcurve/lightcurve.py
90.8% <100%> (-0.21%)
:arrow_down:

cosmogrb/response/__init__.py
100% <100%> (ø)
:arrow_up:

cosmogrb/io/__init__.py
100% <100%> (ø)

... and 10 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 070ab61...3f3d061. Read the comment docs.


Whatever message this is, it's not needed. I am using the version from Curse...

Stop posting this in my chat...

Fixed in 1.0.3


Allow the user to add new markets and assets from the UI

The user should be able to add new markets through the UI somehow.
These markets should be persistent so that if the user opens up or returns to the app later, they can still see their markets.
Some possible persistence options:

localStorage (web, possibly desktop too if Electron can guarantee persistence between app restarts)
Add a new custom-exchanges.json file (only for desktop)
edit the config.json file (only for desktop)

The user should also be able to edit existing markets through the UI. For example, they can change the DEX and blockchain node IPs to use for the API endpoints.


python310Packages.robotframework: 5.0.1 -> 6.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.robotframework is: "Generic test automation framework"
meta.homepage for python310Packages.robotframework is: "https://robotframework.org/"
meta.changelog for python310Packages.robotframework is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 6.0 with grep in /nix/store/bjk6j48nqwr4i80d1z0gn1dly75bhfs2-python3.10-robotframework-6.0
found 6.0 in filename of file in /nix/store/bjk6j48nqwr4i80d1z0gn1dly75bhfs2-python3.10-robotframework-6.0

Rebuild report (if merged into master) (click to expand)

19 total rebuild path(s)

19 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.robomachine
python310Packages.robotframework
python310Packages.robotframework-databaselibrary
python310Packages.robotframework-requests
python310Packages.robotframework-selenium2library
python310Packages.robotframework-seleniumlibrary
python310Packages.robotframework-sshlibrary
python310Packages.robotstatuschecker
python310Packages.robotsuite
python39Packages.robomachine
python39Packages.robotframework
python39Packages.robotframework-databaselibrary
python39Packages.robotframework-requests
python39Packages.robotframework-selenium2library
python39Packages.robotframework-seleniumlibrary
python39Packages.robotframework-sshlibrary
python39Packages.robotframework-tools
python39Packages.robotstatuschecker
python39Packages.robotsuite

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bjk6j48nqwr4i80d1z0gn1dly75bhfs2-python3.10-robotframework-6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.robotframework https://github.com/r-ryantm/nixpkgs/archive/09d607ce997521f4a3b085063cb2d39a4a96ce38.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bjk6j48nqwr4i80d1z0gn1dly75bhfs2-python3.10-robotframework-6.0
ls -la /nix/store/bjk6j48nqwr4i80d1z0gn1dly75bhfs2-python3.10-robotframework-6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.robomachine
python39Packages.robomachine

5 packages failed to build:

python310Packages.robotframework-selenium2library
python310Packages.robotframework-seleniumlibrary
python39Packages.robotframework-selenium2library
python39Packages.robotframework-seleniumlibrary
python39Packages.robotframework-tools

12 packages built:

python310Packages.robotframework
python310Packages.robotframework-databaselibrary
python310Packages.robotframework-requests
python310Packages.robotframework-sshlibrary
python310Packages.robotstatuschecker
python310Packages.robotsuite
python39Packages.robotframework
python39Packages.robotframework-databaselibrary
python39Packages.robotframework-requests
python39Packages.robotframework-sshlibrary
python39Packages.robotstatuschecker
python39Packages.robotsuite

Maintainer pings
cc @bjornfor for testing.

nixpkgs-review reveals no new failures for me on macos 10.15 or nixos x86_64. But several robotframework-related libraries are already broken, so not sure how much of a thorough test that is.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.robotframework is: "Generic test automation framework"
meta.homepage for python310Packages.robotframework is: "https://robotframework.org/"
meta.changelog for python310Packages.robotframework is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 6.0.1 with grep in /nix/store/qdxdfirhkh4q65l5ak8hlyg6ibwnxjls-python3.10-robotframework-6.0.1
found 6.0.1 in filename of file in /nix/store/qdxdfirhkh4q65l5ak8hlyg6ibwnxjls-python3.10-robotframework-6.0.1

Rebuild report (if merged into master) (click to expand)

19 total rebuild path(s)

19 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.robomachine
python310Packages.robotframework
python310Packages.robotframework-databaselibrary
python310Packages.robotframework-requests
python310Packages.robotframework-selenium2library
python310Packages.robotframework-seleniumlibrary
python310Packages.robotframework-sshlibrary
python310Packages.robotstatuschecker
python310Packages.robotsuite
python39Packages.robomachine
python39Packages.robotframework
python39Packages.robotframework-databaselibrary
python39Packages.robotframework-requests
python39Packages.robotframework-selenium2library
python39Packages.robotframework-seleniumlibrary
python39Packages.robotframework-sshlibrary
python39Packages.robotframework-tools
python39Packages.robotstatuschecker
python39Packages.robotsuite

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qdxdfirhkh4q65l5ak8hlyg6ibwnxjls-python3.10-robotframework-6.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.robotframework https://github.com/r-ryantm/nixpkgs/archive/0750b18cab94b818cd79cdc8ca50e449fc6875e8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qdxdfirhkh4q65l5ak8hlyg6ibwnxjls-python3.10-robotframework-6.0.1
ls -la /nix/store/qdxdfirhkh4q65l5ak8hlyg6ibwnxjls-python3.10-robotframework-6.0.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

python310Packages.robomachine
python39Packages.robomachine

5 packages failed to build:

python310Packages.robotframework-selenium2library
python310Packages.robotframework-seleniumlibrary
python39Packages.robotframework-selenium2library
python39Packages.robotframework-seleniumlibrary
python39Packages.robotframework-tools

12 packages built:

python310Packages.robotframework
python310Packages.robotframework-databaselibrary
python310Packages.robotframework-requests
python310Packages.robotframework-sshlibrary
python310Packages.robotstatuschecker
python310Packages.robotsuite
python39Packages.robotframework
python39Packages.robotframework-databaselibrary
python39Packages.robotframework-requests
python39Packages.robotframework-sshlibrary
python39Packages.robotstatuschecker
python39Packages.robotsuite

Maintainer pings
cc @bjornfor for testing.


33B llama quantization post-inference time

Why is it that after I quantize, my inference is 2 times slower than the original `model?
Quantize command：python main.py $MODEL_PATH $DATASET_PATH --nsamples=1024 --num_codebooks=1 --nbits_per_codebook=16 --in_group_size=8 --relative_mse_tolerance=0.01 --finetune_relative_mse_tolerance=0.001 --finetune_batch_size=32 --local_batch_size=1 --offload_activations --wandb --save $SAVE_PATH --dtype float32
Quantitative results：

In addition, looking at the GPU usage, it seems that it has become a parallel pipeline. I use four cores to load the model, but only one GPU utilization is 100% at the same time.

Have you encountered the same problem as me again? Is the inference speed of your quantized model normal?

Hi @ACoder-J !
The inference speed is really bottlenecked by transformers for multiple reasons (transformers being slow and kernel launches taking long).
One way to achieve proper speedup is to compile your model into a cuda graph. It's a new feature added to PyTorch in 2.0.0 and refined in 2.2.1. People of transformers have also been working hard to properly support and document it. To check out what you can do with it already, please refer to this AQLM demo.
Another way to properly serve AQLM is to use the vllm integration. It's not complete yet but it might be usable already (not sure).


About the implementation in HMDB51 case.

Hello I am very appreciate for your work. And I now I start to try to reproduce your work in HMDB51 case by your code. But I noticed some parts for HMDB51 case is nor included in your webpage, such as 'cnn_hmdb51_setup_data.m', and baseline networks for hmdb51.
I have just run the training and testing in HMDB51 case by adapting from your UCF case (e.g. adapt your ucf101 baseline networks into networks for 51 categories).
But my result is a little weird. Could you please kindly upload your HMDB51 part code and network models?
Thank you very much for your precious time.

I have the same question,have you solved it?


[api-docs] Document guild time outs (#4075)

A new commit was made into the api-docs repo.
https://github.com/discord/discord-api-docs/commit/b51c34f8f50ae8455f351f869ed22d025c1d2852
This is a bot created issue.

#1862


Update IpmiApi.scala

https://github.com/tumblr/collins/issues/303
modify the ipmi password text validation conditions minLength / maxLength

@froxart
Please create a pull request to tumblr/collins [1] from your fork. The change looks fine
[1] https://github.com/tumblr/collins/compare/master...froxart:froxart-ipmipw-validation


Could not excecute entrypoint stage 'main' due to errors provided by 'create'

Context
I'm trying to make a modpack on Curseforge and I keep getting the same issue no matter what I try. I'm sure I have some redundant mods but nothing should be causing create to break
Crash Report
https://mclo.gs/B3LZ4xR

Can you also post latest.log from your logs folder

https://mclo.gs/x4HB79A

Try disabling mialeemisc

The game crashed whilst initializing game
Error: java.lang.RuntimeException: Could not execute entrypoint stage 'main' due to errors, provided by 'kiwi' at 'snownee.kiwi.Kiwi'!

https://mclo.gs/zhr6m0T

Disable kiwi aswell then

That worked thank you, it was an issue that Kiwi was causing


The "required" fields are not appearing as orange, and are greyed out instead

The "required" fields are not appearing as orange, and are greyed out instead. In the old Modals they used to be orange for required fields when not filled. In the current modal they only turn orange on blur.

https://www.loom.com/share/af71cd61b72348ce85744bae35cbf73c

this is not really a bug, it's a fundamental pattern in formik -- https://formik.org/docs/tutorial#visited-fields

Thank you for that link @lucas-homer and you are right its not really a bug and that is what I thought initially and reported as such on the bug ticket related to this issue on our repo. But I was asked to report this and hopefully get it to work in that particular way as mentioned above where the 'required' gets highlighted in orange for required fields, regardless of whether the user has visited it or not.

I don't know what else to say other than whoever wrote that quote needs to understand that SQForm behaves slightly differently in this regard, and it's a design supported by industry leaders.

@lucas-homer
I noticed that we are passing validateOnMount={true} in the SQForm but that fix was made in formik v2.16. Please see the link below:
https://codesandbox.io/s/formik-codesandbox-template-forked-mz9le?file=/index.js
So, I believe this issue can resolved (or at least the functionality we are looking for in LQT can be achieved)  if we bump up the Formik version to 2.16 or above as opposed to the current 2.14.

Hi @rizwanahmedziai
Can you provide some further information on this request, please?
Who is requesting this change? What is the link to the ticket?
I'd like to discover who to have this conversation with.
Thanks!

@SeanGroff Sure mate. Here is the link to the ticket:
https://selectquote.atlassian.net/browse/P12-1915
You can discuss this further with Stuart Washington or Skylar Hoch

Link to the same issue on Formik
https://github.com/formium/formik/issues/2652

@rizwanahmedziai I've moved the discussion back to the Jira ticket
https://selectquote.atlassian.net/browse/P12-1915?focusedCommentId=174382
I'll revisit this once UI/UX chimes in

Closing this issue per https://selectquote.atlassian.net/browse/P12-1915?focusedCommentId=174404

Thank you for the input @SeanGroff That removed our confusion.


DatabaseLockError: Unable to get write lock on .nvim: already locked

Hi,
Nvim is working great for me, but I'm having to rebuild the Xapian database every time I launch. When I try to reload the db with :python nvimdb.reload_database() I get the below error. It's possible this is related to permissions/user issue I have on my setup, stemming from an attempt to share a drive between mac osx and arch linux. But after trying to chase that down for a while, I'm sort of stuck, hence coming here.
This happens across reboots. The error only shows up when I call :python nvimdb.reload_database() myself; upon launching nvim either from the script or in vim, it just loads with an empty databse and strace doesn't show any such error. Maybe I've misread the nvim.py file in thinking reload_database runs at each init?
Thanks for such a great program!
Edit: quick clarification. I have nvim installed as "nvel" in my neovim plugins folder, hence the possibly confusing use of "nvim" and "nvel" below.
Error detected while processing function provider#python#Call:
line   18:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/hgv/.local/share/nvim/plugged/nvel/python/nvim.py", line 26, in reload_database
    self.db = xapian.WritableDatabase( self.database,xapian.DB_CREATE_OR_OPEN )
  File "/usr/lib/python2.7/site-packages/xapian/__init__.py", line 4399, in __init__
    _xapian.WritableDatabase_swiginit(self,_xapian.new_WritableDatabase(*args))
DatabaseLockError: Unable to get write lock on .nvim: already locked

hmmm. So yes, reload_database does get called  on start. The error indicates that it thinks another running process currently owns the .nvim directory, it could be permissions, but unlikely.
Does this occur in a fresh directory or just the one with your old notes in? if you have a terminal on the directory where the error occurs, what does ls -lA .nvim give you?

Yes, this occurs in both a fresh directory (tried on both the shared partition I mentioned and on a nonshared one) and the already existing one. And on both, I get (depending on size) the same output on ls -lA .nvim, so should be writable by me:
total 8500
-rw-r--r-- 1 hgv hgv       0 Jan  3 13:17 flintlock
-rw-r--r-- 1 hgv hgv      28 Jan  3 13:17 iamchert
-rw-r--r-- 1 hgv hgv      13 Jan  3 13:17 position.baseA
-rw-r--r-- 1 hgv hgv 3432448 Jan  3 15:28 position.DB
-rw-r--r-- 1 hgv hgv      13 Jan  3 13:17 postlist.baseA
-rw-r--r-- 1 hgv hgv 3457024 Jan  3 15:23 postlist.DB
-rw-r--r-- 1 hgv hgv      13 Jan  3 13:17 record.baseA
-rw-r--r-- 1 hgv hgv   49152 Jan  3 15:28 record.DB
-rw-r--r-- 1 hgv hgv      13 Jan  3 13:17 termlist.baseA
-rw-r--r-- 1 hgv hgv 1744896 Jan  3 15:28 termlist.DB

Poking around xapian docs hasn't helped me; I don't see the cat process or anything related to fcntl() on top (as mentioned here: https://getting-started-with-xapian.readthedocs.io/en/latest/advanced/admin_notes.html#single-writer-multiple-reader).
Just thought to try lsof to see if anything else is up. When nvim is not running, nothing shows up; once I've opened it via my nvel script (but without the database loading or being rebuilt), lsof | grep .nvim results in (with results for nvim as in neovim omitted). Though maybe this isn't helpful as nvim is already running.
nvel      6021       hgv  255r      REG                8,5       885     303743 /home/hgv/.local/share/nvim/plugged/nvel/nvim
[. . .]
python2   6025       hgv    7ww     REG                8,5         0     389724 /home/hgv/documents/Details/Data/NotationalVelocity/.nvim/flintlock
python2   6025       hgv    8u      REG                8,5     49152     389731 /home/hgv/documents/Details/Data/NotationalVelocity/.nvim/record.DB
python2   6025       hgv    9u      REG                8,5   1744896     389729 /home/hgv/documents/Details/Data/NotationalVelocity/.nvim/termlist.DB
python2   6025       hgv   10u      REG                8,5   3432448     389733 /home/hgv/documents/Details/Data/NotationalVelocity/.nvim/position.DB
python2   6025       hgv   11u      REG                8,5   3457024     389727 /home/hgv/documents/Details/Data/NotationalVelocity/.nvim/postlist.DB

I'm happy to keep digging, as nvalt was pretty fundamental to my work life on mac, so nvim has been a godsend in switching—would just be nice to not have to rebuild the db everytime (though this hasn't seemed to cause any problems).

rebuilding the db is safe - it is just a cache after all. I wonder if it is (if I understand you correctly) because you are running it under neovim - some difference in the python engines between the two?

You are correct and I had wondered about that. Will check in and report back.

Did you get anywhere on this?

I actually moved away from using the plugin when I found others that met my needs more specifically (and allowed me to stop troubleshooting this). But thanks for checking in!

Interesting. Which one, out of curiousity?

I started using fzf in general, which led me to https://github.com/Alok/notational-fzf-vim.

Interesting. Thanks for the update.