text:
Support distant:// scheme?

Any thoughts on supporting distant (https://distant.rocks) as another option for remote editing? It offers a JSON lines API that you can used for authentication, file I/O, process management (including running LSP servers), remote shells, file/directory watching, and automatic reconnecting for poor networking.
I've built out distant.nvim to leverage that CLI to both support SSH and the custom distant protocol, but would also love to see more adoption across fellow plugins and integrations to enable remote editing features.

Ironically I looked at your plugin before creating netman!
Because of how netman is structured, a distant provider can absolutely be created for netman. My provider creation docs aren't great though. If you're willing to provide some assistance/long term maintenance with the provider, I have no issue in including that provider in core :)
I will not include it in the 1.15 or 1.2 milestones, imo something like this would be it's own work effort altogether. But I am very much behind adding this kind of support!

Alright, so do you recommend revisiting this later? 😄

Ah, okay. I misunderstood your earlier comments as needing to wait for documentation and reaching a later milestone. I'll take a look at the plugin docs, but my interest would be to avoid maintaining a second plugin myself (e.g. the standalone plugin route), so if I can help integrate the feature into netman directly and provide answers/support in this repo, that'd be my preference.
How would you recommend proceeding when it comes to integrating into core? Any code pointers for me to look at?

I'll take a look at the plugin docs, but my interest would be to avoid maintaining a second plugin myself (e.g. the standalone plugin route), so if I can help integrate the feature into netman directly and provide answers/support in this repo, that'd be my preference.

Its worth mentioning that distant.nvim could actually just integrate itself into netman to avoid having a separate plugin :)
Anyway! To your question
The best way to get started is the developer doc I linked above, it walks through how to create an (admittedly out of date) docker provider.
Alternatively, you can checkout the docker provider in core.
Adding a new provider to core should be reasonably simple.

Create a new provider in netman.providers (we can call it distant.lua)
Add the path to this new provider to netman.providers.init
Implement the required attributes and functions for a provider. Details on this can be found in the api doc.

I would say the best "code" starting point is the docker provider which is what I would call the "most complete" provider.
Please note, per #117 , Netman is purely synchronous currently. There will be optional functions that a provider can implement if it wishes to support asynchronous behavior, but I do not have them fleshed out yet.
Feel free to reach out to me on discord miversen33#0131 if you have questions and would like "more immediate" assistance on how to do things :) I know parsing doc and someone else's code can be... Painful at times.
And thank you! I have been hoping others would have interest in creating providers for netman, (as well as consumers but I haven't fleshed that out just yet). Please let me know how I can help you

I can appreciate the strictness on dependencies as distant.nvim also avoids needing any additional dependencies, although I do make concessions by providing integrations into other plugins like telescope.nvim, but they're all optional.
So it sounds like if I want to have distant be available as a provider in core, I would need to write the API communication again rather than importing distant.nvim, which already supports synchronous and asynchronous APIs. That's not a dealbreaker for me, but want to make sure I understood your explanation before I commit to one approach versus the other!
I was skimming through your documentation and the docker provider, and didn't immediately see a standard way to support connection setup and/or authentication. For the distant plugin, when you launch a new server or connect to an existing server, a handshake is performed that includes zero or more authentication challenges. My first guess is that I could provide this synchronously through the optional init function?

So it sounds like if I want to have distant be available as a provider in core, I would need to write the API communication again rather than importing distant.nvim, which already supports synchronous and asynchronous APIs. That's not a dealbreaker for me, but want to make sure I understood your explanation before I commit to one approach versus the other!

This is correct unfortunately. It may be easier to add a bit of wrapper code to distant.nvim to integrate with netman (thus making netman an optional dependency of distant.nvim, like you do for telescope for example), in which case you don't have to completely port your code over to Netman. It may not be easier though, I don't know lol. I am happy to provide support in either decision though :)

I was skimming through your documentation and the docker provider, and didn't immediately see a standard way to support connection setup and/or authentication. For the distant plugin, when you launch a new server or connect to an existing server, a handshake is performed that includes zero or more authentication challenges. My first guess is that I could provide this synchronously through the optional init function?

Ya I haven't landed on exactly how I want connections to work unfortunately. I am currently toying with this as the core ssh plugin could benefit from a "connect" function as well. For the time being, I execute the connect logic automagically with SSH_MULTIPLEXING (meaning SSH handles the initial connection and I am able to just assume the pipe exists). However there are definitely times that that hurts.
The optional "init" function is called on the initial load of the plugin (as seen in api.load_provider). This is called (most likely) during neovim startup and gives your provider an opportunity to verify it can run (all dependencies are met for example). It is not called on initial read of a URI as the API has no concept of URI connection states.
Currently (until/unless an optional connect method is introduced to the provider spec), your best bet would be to have an object that manages your distant information (including if its connected) and perform the connection whenever it recognizes it isn't connected. I don't know what that logic looks like for distant, but that is how I would go about handling that within the Netman environment.
I want to call out, I am not against a adding this kind of functionality (so if you have an idea of what you would like it to look like, I would be fine with chatting about that spec), however as I call out in the api documentation the API should be as stateless as possible and as dumb as possible. Thus implementing some kind of URI connection logic would likely need to be very well thought through as I am not open to having the API manage if a URI is connected or not (as that is what the provider should do).
I hope that answered your questions :)

Yeah, thanks for the detailed responses here :) Figure having questions answered in this issue (versus discord chat) would be better for others who inquire later.
For distant, I actually mirrored ssh's method of authentication (being in protocol and client APIs), so I'd be happy to chat about how that works in the future. Lazy validation of authentication seems like a path forward to me, so I can certainly implement that approach for netman.

Makes sense to me! Let me know if/when you need anything. I would fork off of main as opposed to v1.15 (if you are unsure which branch to use). Anything not main is unstable and subject to being yeeted off at anytime. I think I am going to close this issue out as it sounds like we have a general plan on what to do for this. Feel free to open new issues about whatever obscure (or not) bugs you encounter :)


text:
add size to snapshot list

resolves #7
Size calculation is fast on my machine so it doesn't hurt to do it even when we don't need it.
I'm happy to refactor it to just pull the size when needed, so in the cli/list method.

Amazing. Thank you!
I pushed a couple of commits just to update the branch and fix the tests.

thanks for fixing the tests!
is running tests on PRs disabled? I would also totally have done it myself

Yes. It's currently set to require manual approval for first-time collaborators.
And no worries. It was a one-line fix and to be honest I just didn't want to wait so that's on me 😛
Thanks for the contribution though, it's working great!

source: gharchive/pull-request

authors: mixxorz syphar

repo: mixxorz/DSLR

license: MIT

license_type: permissive

license_source: github-api


text:
Next steps for sharejs

I think to prepare sharejs for the future we need to focus on these points.

[ ]  Rewrite the code in ecmascript 2015
[ ]  Use npm packages for code mirror and ace
[ ]  Add React components for the editor

emascript 2015
The main reason is, that I never really liked coffeescript. It will also help users with no coffeescript experience to faster dig into the code.
NPM Packages
The current importing of ace and code mirror works, but with the introduction of npm packages in meteor 1.3 this seems to be a better suitable approach.
React Components.
As React gained some serious focus in the meteor community this should be supported.

React is so much easier and faster than blaze just DO IT :)
Thanks bro <3

You may also want to check out a rather long discussion we had about supporting rich text editing over at share/ShareJS#1.

@mizzao I'm currently working on a project which required me to use React instead of Blaze and things work perfectly. If you need my help, please let me know!

Hi @vincentracine - @DavidSichau is doing most of the work on this package now, so I'm sure he'll be interested. Do you have some code available somewhere or posted in a gist (other than what you pasted in that other issue?)

@vincentracine It would be nice if you could share some code with me.
I am currently working on the transition to npm packages. As soon as I finish this I will focus on react.

@DavidSichau @mizzao Here you go guys. This is copy and pasted from my own little project. Hope this can help you get started!
// AceEditor.js
export default AceEditor = React.createClass({

	getInitialState(){
		return {
			doc: null,
			editor: null
		}
	},

	componentDidMount(){
		// Get Ace Editor from DOM
		this.setState({
			editor: ace.edit("editor")
		});

		// Set Ace Editor behaviour
		this.setTheme('ace/theme/chrome');
		this.state.editor.getSession().setMode("ace/mode/python");
		this.state.editor.setFontSize(14);
		this.state.editor.setShowPrintMargin(false);
		this.state.editor.getSession().setUseWrapMode(true);
		this.state.editor.$blockScrolling = Infinity;
		this.state.editor.resize();

		this.onChange();
	},

	shouldComponentUpdate(nextProps, nextState) {
		return nextProps.docid !== this.props.docid;
	},

	componentDidUpdate(){
		this.onChange();
	},

	componentWillUnmount(){

		// Disconnect from ShareJS
		this.disconnect();

		// Clean up Ace memory to avoid memory leaks
		this.state.editor.destroy();

	},

	// ------- ShareJS

	onChange(){

		// Doesn't have a document opened but wants to connect
		if(!this.isConnected() && this.props.docid){
			this.connect(this.props.docid);
		}

		// Has a document opened but wants to open a new document
		if(this.isConnected() && this.props.docid){
			this.disconnect();
			this.connect(this.props.docid);
		}

		// Has a document opened but wants to close it
		if(this.isConnected() && !this.props.docid){
			this.disconnect();
		}

	},
	connect(documentId){
		let self = this;

		if(this.isConnected()){
			throw new Error('Already connected to ShareJS');
		}

		// Open the document
		sharejs.open(documentId, 'text', function(error, doc){
			if(error) {
				console.error("Connection error:", error);
			}else{
				// Update state
				self.setState({ doc: doc });

				// Check we are connected
				if(self.isConnected()){
					// Attach ace editor to document
					doc.attach_ace(self.state.editor);
					console.log('Opened document [',documentId,']');
				}else{
					console.error("Document was opened but closed right away");
				}
			}
		});
	},
	disconnect(){
		if(this.isConnected()){
			let name = this.state.doc.name;
			this.state.doc.close();
			if(this.state.doc.state === 'closed'){
				console.log('Closed document [',name,']');
			}else{
				console.error('Failed to close document [',name,']');
			}
			this.state.doc.detach_ace();
		}
	},
	isConnected(){
		return this.state.doc != null && this.state.doc.state === 'open';
	},

	// ------- End of ShareJS

	// ------- Editor State

	setTheme(theme){
		this.state.editor.setTheme(theme);
	},
	getAceInstance(){
		return this.state.editor;
	},
	getText(){
		return this.state.editor ? this.state.editor.getValue() : null;
	},

	// ------- End of Editor State

	render() {
		return (

		)
	}
});

And you can use it like this:
EditorPage = React.createClass({

	mixins: [ReactMeteorData],

	getMeteorData() {
		return {
			currentUser: Meteor.user(),
			document: Documents.findOne({_id: this.props.docId})
		}
	},

	ready(){
		return this.data.document;
	},

	render(){
		return (
			<Row class="container-fluid">

{this.ready() ? this.data.document.title : 'Loading...'}

					{this.ready() ? (
						<AceEditor ref="editor" docid={this.props.docId}/>
					) : null}

			</Row>
		)
	}
});

@vincentracine Sorry for the long delay. I will take a look at this. I think the best would be to distribute it as an individual package. Something like sharejs-ace-react.
I will first merge my other pull request and than have a look at your code.

source: gharchive/issue

authors: DavidSichau capensisma mizzao vincentracine

repo: mizzao/meteor-sharejs

license: mit

license_source: bigquery


text:
Make it a Middleware

I was looking for some projects to make it easy to access a shared network folder. Found yours and David Whitehead's.
He also implemented the impersonation as a middleware.
https://github.com/lilpug/ASP.NET-Core-Impersonation

Thanks, but I think David (@lilpug) has done a good job with his middleware.  I don't see the need to re-implement that here.   One certainly could use SimpleImpersonation to do the actual impersonation bits, if you or David wanted to take a dependency - but I don't think there's necessarily an advantage.  At the end of the day, we're all calling LogonUser.


text:
Advanced Git behaviour not supported?

It appears that the advanced behaviour when using Git, is not supported. For example, an advanced Git behaviour that is not supported is initialising and syncing  submodules. Are there any plans to implement this?

I ran into this today. I want to do shallow clones but the button for "Advanced behaviour" doesn't exist under the Git-SCM options. It doesn't appear on the Multi-Branch config page, but it does appear on the individual branch configure pages. Not much help to me as I want new branches to do shallow clones by default but this might help people who want to change existing branches.

SCM options, including those on the multi-branch project configuration page, are implemented by the SCM plugins themselves.

authors: gmetal mjdetullio rmasters

repo: mjdetullio/multi-branch-project-plugin


text:
make social icon color settable (always white until now?)

Is your feature request related to a problem? Please describe.
I wanted to change the color of the icon itself, not the background color of the icon. I couldn't find a way to mange it.
Describe the solution you'd like
Add a icon-color css element ?

Hi @npracht  You can change the icon color, background-color is actually made for this, like this : https://mjml.io/try-it-live/HJstr_OfB
(This works only because the social icons we provide are natively transparent and the color is really applied as a background-color, thus the attribute name. There is no way to change an image's color with outlook-supported css)
Does it suit your needs ?

Nope ! In case you're on a black backgrounded section, and white social, how do you manage it ? i'd like that the logo (F of Facebook, In of Linkedin) is in black.

In this case you'll have to use your own icon, with the src attribute (https://mjml.io/try-it-live/HJstr_OfB)
The f is white in the provided image, and as i said there is no way to change an image's color with outlook-supported css.

repo: mjmlio/mjml


text:
android.content.res.Resources$NotFoundException

I can't reproduce this consistently.  It's usually when the app is launching after it's been backgrounded for a while.
I'm essentially using version 1.2.2 of the plugin.  So far only seen on Android 7.1, Nexus 5X (bullhead).
java.lang.RuntimeException: Unable to start activity ComponentInfo{ca.koho/ca.koho.Koho}: android.content.res.Resources$NotFoundException: Resource ID #0x0
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2665)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
	at android.app.ActivityThread.-wrap12(ActivityThread.java)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1477)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:154)
	at android.app.ActivityThread.main(ActivityThread.java:6119)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)
Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x0
	at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:190)
	at android.content.res.Resources.loadXmlResourceParser(Resources.java:2101)
	at android.content.res.Resources.getLayout(Resources.java:1115)
	at android.view.LayoutInflater.inflate(LayoutInflater.java:424)
	at com.cordova.plugin.android.fingerprintauth.FingerprintAuthenticationDialogFragment.onCreateView(FingerprintAuthenticationDialogFragment.java:85)
	at android.app.Fragment.performCreateView(Fragment.java:2353)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:995)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1171)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1153)
	at android.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:2039)
	at android.app.FragmentController.dispatchActivityCreated(FragmentController.java:176)
	at android.app.Activity.performCreateCommon(Activity.java:6673)
	at android.app.Activity.performCreate(Activity.java:6681)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1118)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2618)
	... 9 more

Same error here! Found some solution?

Hopefully this has been resolved with the fix to allow state loss in version 1.2.8
Closing this issue for now.  If it is still occurring please reopen the issue.

Got this exception again while using 1.3.0. Same stacktrace.

+1 to what @SeeWhat said, although we're still on 1.2.8. We've seen about ~150 crashes on 7.0 Samsung Galaxy devices:

First of all, thank you for this plugin. It's very usefull.
We have the same problem on Redmi 4, Redmi Note 3, Redmi 4X using plugin version 1.3.1. Please, could you reopen this issue and answer when the problem will be resolved?
This is emergency situation.
Thank you in advance.

Very difficult to troubleshoot with the stack trace alone.  It has been mentioned that it cannot be reproduced consistent.  I can not reproduce the error so I can't debug the issue.  I do not have access to the devices mentioned for testing.  If you would like resolution to this issue please contribute by providing more helpful/useful information.

@mjwheatley, I'm sorry for long answer. I had problems that demanded my immediate attention.
I can't reproduce it neither. I saw this from crash reporter in firebase console. I have only the stack trace. But it is the same as @jskrepnek wrote.
Exception java.lang.RuntimeException: Unable to start activity ComponentInfo{air.com.ssdsoftwaresolutions.clickuz/air.com.ssdsoftwaresolutions.clickuz.MainActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x0 android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2984) android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3045) android.app.ActivityThread.-wrap14 (ActivityThread.java) android.app.ActivityThread$H.handleMessage (ActivityThread.java:1642) android.os.Handler.dispatchMessage (Handler.java:102) android.os.Looper.loop (Looper.java:154) android.app.ActivityThread.main (ActivityThread.java:6776) java.lang.reflect.Method.invoke (Method.java) com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1496) com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1386) arrow_drop_down Caused by android.content.res.Resources$NotFoundException: Resource ID #0x0 android.content.res.ResourcesImpl.getValue (ResourcesImpl.java:202) android.content.res.Resources.loadXmlResourceParser (Resources.java:2970) android.content.res.Resources.getLayout (Resources.java:1986) android.view.LayoutInflater.inflate (LayoutInflater.java:425) com.cordova.plugin.android.fingerprintauth.FingerprintAuthenticationDialogFragment.onCreateView (FingerprintAuthenticationDialogFragment.java:85) android.app.Fragment.performCreateView (Fragment.java:2352) android.app.FragmentManagerImpl.moveToState (FragmentManager.java:995) android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1171) android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1153) android.app.FragmentManagerImpl.dispatchActivityCreated (FragmentManager.java:2043) android.app.FragmentController.dispatchActivityCreated (FragmentController.java:177) android.app.Activity.performCreateCommon (Activity.java:6949) android.app.Activity.performCreate (Activity.java:6957) android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1126) android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2927) android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:3045) android.app.ActivityThread.-wrap14 (ActivityThread.java) android.app.ActivityThread$H.handleMessage (ActivityThread.java:1642) android.os.Handler.dispatchMessage (Handler.java:102) android.os.Looper.loop (Looper.java:154) android.app.ActivityThread.main (ActivityThread.java:6776) java.lang.reflect.Method.invoke (Method.java) com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1496) com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1386)

Nothing new to add, but having the same issue with our apps.   Not sure what Samsung does differently with their phones.

We traced most (but not all) of these to the scenario where the fragment was displayed when the application was paused.  It our case it would usually happen when the power button was pressed.  Have a look at the changes: https://github.com/kohofinancial/cordova-plugin-android-fingerprint-auth/commits/master.

Thanks for the response.  I'm confused. We have version 1.31. of the plugin.   The fix should be in that version?  Not sure why we still get the crashes for samsung devices.

@newuser44 We forked the plugin - the fixes have not come back to the origin.  You'd have to look at the commits in our forked repo for details.

Hi
Current status for this error?

same here .. current status?

Same as my last post as no additional information has been provided to help troubleshoot the issue.

What do you need? we have crash logs

java.lang.RuntimeException:
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2924)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2985)
at android.app.ActivityThread.-wrap14 (ActivityThread.java)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1635)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:154)
at android.app.ActivityThread.main (ActivityThread.java:6692)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1468)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1358)
Caused by: android.content.res.Resources$NotFoundException:
at android.content.res.ResourcesImpl.getValue (ResourcesImpl.java:202)
at android.content.res.Resources.loadXmlResourceParser (Resources.java:2968)
at android.content.res.Resources.getLayout (Resources.java:1984)
at android.view.LayoutInflater.inflate (LayoutInflater.java:425)
at com.cordova.plugin.android.fingerprintauth.FingerprintAuthenticationDialogFragment.onCreateView (FingerprintAuthenticationDialogFragment.java:85)
at android.app.Fragment.performCreateView (Fragment.java:2352)
at android.app.FragmentManagerImpl.moveToState (FragmentManager.java:995)
at android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1171)
at android.app.FragmentManagerImpl.moveToState (FragmentManager.java:1153)
at android.app.FragmentManagerImpl.dispatchActivityCreated (FragmentManager.java:2043)
at android.app.FragmentController.dispatchActivityCreated (FragmentController.java:177)
at android.app.Activity.performCreateCommon (Activity.java:6906)
at android.app.Activity.performCreate (Activity.java:6914)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1126)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2877)

Please provide steps to reproduce the issue on a simulator and the simulator config information.

It only happens on 7.0 devices as far as i can see. Perhaps somethings to do with theme? I cant reproduce it yet in emulators.

same

Just noting that per this, which is based off your work, and the reports here, I think this is handled.

Thanks for the references.  I will go ahead and close this issue.

authors: Azamat-Nurzhanuly SeeWhat WuglyakBolgoink danicholls dickverweij jeansantana jonathankau jskrepnek mjwheatley newuser44 videmort


text:
use of clientSecret: "a_very_secret_encryption_key" ?

Could you provide a little more detail in the README regarding the use of the clientSecret?
I'm guessing this key needs to be protected and probably stored securely... recommendations would be nice.

The clientSecret is used to generate the encryption token that is returned upon successful fingerprint authentication.
return mCipher.doFinal(mClientSecret.getBytes());
Yes, the client secret should be passed in at runtime when compiling your application.  This is a plugin that can be used by several frameworks, not all of which I have experience with, so I can not really provide recommendations for them all.
I use this plugin with the MeteorJS framework.  When building for production I pass in a settings.json file that contains all my API credentials.  These are only available via process.env so they would not be able to be harvested from the application bundle.
What framework are you using this plugin with?

I'm using just HTML5 and JavaScript with Phonegap / Cordova.  No frameworks (yet).  At the moment, I'm not sure how to accomplish passing something in at runtime and not bundled with the app -- besides making an AJAX call out to another system.
Thanks for the information!

Is not unsafe to place the encryption key inside js files? they can be easily decoded. In .class is better but I think that until the whole archive is encrypted the key is not safe

authors: Slumber86 charlesmccann mjwheatley


text:
New test case for "Signature mismatch exception"

See #187
Please merge it after #189

@KvanTTT: I merged #189. Seems this one still needs a rebase to work.

:x: Build ConfuserEx 478 failed (commit https://github.com/mkaring/ConfuserEx/commit/c7883fd34d by @KvanTTT)

Rebase is done. I've also remove not used parameter from Run signature.

:x: Build ConfuserEx 479 failed (commit https://github.com/mkaring/ConfuserEx/commit/d4b220a503 by @KvanTTT)

Thank you. I am looking into the issue.

Was merged in #215

authors: AppVeyorBot KvanTTT mkaring

repo: mkaring/ConfuserEx


text:
Use binary decimal when possible?

Many drivers do not handle binary decimal structures per the specification so pyodbc retrieves these as text instead.  Consider doing a check in the CnxnInfo for proper handling and using binary when possible?

After getting back into the decimal code, I've decided not to pursue this right now.

repo: mkleehammer/pyodbc


text:
Cleanup codebase, create v1

Thanks for a great port of the Github library.
I'm offering this PR to cleanup a few things in the codebase, to make them a bit more friendly to what a node.js dev would expect in 2016. Here's a summary of the changes:

parse_reply renamed to parse.
String.prototype is no longer augmented, instead we use local functions for performing trim, chomp, etc.
The module is exported directly, meaning you get the whole module when you require('emailreplyparser').
Test dependencies added to package.json to make testing easier.
underscore replaced with lodash in the tests.
Code style cleaned up: use single quotes everywhere, add 'use strict' definitions, use triple equals where necessary.

I hope this is acceptable, if not then I'm happy to maintain my fork and publish to npm under a different name.

@fiznool Did you fork and publish to npm under a different name?

@CTassisF the changes are still in my fork at https://github.com/flowxo/emailreplyparser
I didn't publish anything to npm yet. If @mko doesn't reply in the next few weeks I'll look to do that. In the meantime you can depend on my fork directly. In your package.json:
"emailreplyparser": "github:flowxo/emailreplyparser#0834875

authors: CTassisF fiznool

repo: mko/emailreplyparser


text:
Показувати рейтинг і статистику для незалогінених юзерів

В меню, елемент рейтинг і статистика повинен бути видимий для незалогінених юзерів. Всі інші елементи - лише для залогінених

@ivanursul в такому випадку для отримання статистики та рейтингу в запиті хедер "Authorization" має бути не обов;язковим ?

authors: ivanursul mkozhukharenko

repo: mkozhukharenko/ums-frontend


text:
mx.std() doesn't exist?   [BUG]

Describe the bug
mx.std() doesn't exist?
To Reproduce
import mlx.core as mx
mx.array([1,2,3]).std()

AttributeError: 'array' object has no attribute 'std'
Expected behavior
https://ml-explore.github.io/mlx/build/html/python/_autosummary/mlx.core.std.html
Desktop (please complete the following information):

OS Version: MacOS 14.1.2
Version 0.17.2

Additional context
mx.array([1,2,3]).var().sqrt() # works for now

mx.std(x) should also work

repo: ml-explore/mlx


text:
Hardware details in training

May I ask you about the hardware you used in training for the NeSy ConceptLearner part and the whole project, such as which GPU, how many GPUs you used and the training time?

Sorry for my late reply. Each seed was trained on a single gpu, though you can of course run several seeds in parallel on one gpu.
The GPU was a Tesla V100 SXM3 32GB.
I don't fully remember the training time. It depends on whether you train via XIL or not. it might have been under an hour for 100 epochs, but don't pin me down on this ;)

Thank you very much for this information ;)

authors: provincit wolfstam

repo: ml-research/NeSyConceptLearner


text:
OCI compliant Images in mlcube

Creating an issue for documenting the conversation about OCI compliant images
and also talk about the recent news of docker being removed from Kubernetes and what it means to users of mlcube.

There are a lot of tools that are building OCI compliant images and adhere to the standard. Just to name a few: podman, buildah, kaniko, bazel, source-to-image, cloud native buildpacks.
If the tools would not create OCI compliant images the whole container eco system would not work.

The beauty of standards is. that we can run several tools interchangeably especially with k8s. We can run k8s with contianerd, crio or any other CRI compliant runtime. The major change in deprecating docker in k8s was to abandon the dockershim.

Before:
kubelet -> dockershim -> docker -> containerd -> container
Now:
kubelet -> CRI-containerd -> containerd -> container
RH has build cri-o this works as following:
kubelet -> CRI-O -> runc -> container

Any container build with docker or any other tool will work the same on future k8s systems. No change needed.

authors: sub-mod zvonkok

repo: mlcommons/mlcube


text:
Unsplash images are not showing on Android

Unsplash images are not showing on Android. On the browser works fine but building and exporting the app for Android is not showing the images because is getting the URL.
D/InputMethodManager: startInputInner - Id : 0
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/framework-9b5d6ec4444c80fa.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/main-f8fa0ccd6fd7cd8a.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/pages/_app-aa083d9be419673c.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/pages/index-b66aa8961d88c178.js
D/Capacitor: Handling local request: http://localhost/_next/static/6U466ftwKTYJF493z9tiP/_buildManifest.js
D/Capacitor: Handling local request: http://localhost/_next/static/6U466ftwKTYJF493z9tiP/_ssgManifest.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/34fce5f1.bef0fa3d8439f59e.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/718.47e85776f93458d8.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/968.1d6014add1dad642.js
D/Capacitor: Handling local request: http://localhost/favicon.ico
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/990.b5c55a40fcc26f6b.js
D/Capacitor: Handling local request: http://localhost/_next/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1610235554447-41505d7962f8%3Fixid%3DMXwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHw%253D%26ixlib%3Drb-1.2.1%26auto%3Dformat%26fit%3Dcrop%26w%3D882%26q%3D80&w=828&q=75
D/Capacitor: Handling local request: http://localhost/_next/image?url=%2Fimg%2Fmax.jpg&w=828&q=75
D/Capacitor: Handling local request: http://localhost/_next/image?url=https%3A%2F%2Fimages.unsplash.com%2Fphoto-1610212594948-370947a3ba0b%3Fixid%3DMXwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHw%253D%26ixlib%3Drb-1.2.1%26auto%3Dformat%26fit%3Dcrop%26w%3D934%26q%3D80&w=828&q=75
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/823.5d5644b559a8593e.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/78.46dcf55d1ff46d94.js
D/Capacitor: Handling local request: http://localhost/_next/static/chunks/544.1be07b82b4f34332.js
I/ViewRootImpl@cf65327[MainActivity]: ViewPostIme pointer 0
I/ViewRootImpl@cf65327[MainActivity]: ViewPostIme pointer 1

me too, is there any update?

Fix this by not using next/image. I'm guessing the update to Next.js 12 broke this or maybe a transitive dependency in the time since that update landed. Now next/image requires custom loaders when using export and I didn't want to deal with that right now when it's just easier to use <img> https://github.com/vercel/next.js/discussions/19065

authors: adelynx chiqors mlynch


text:
datasets cant loading correctly

I have downloaded the datasets and weights from gdrive, but when I try to train the model, some error happened.
When I try to run
vit=l task=ovd dataset=coco bash scripts/train.sh
The error is FileNotFoundError: [Errno 2] No such file or directory: 'datasets/coco/train2017/000000183332.jpg'
When I try to run
task=ovd dataset=lvis bash scripts/train.sh MODEL.MASK_ON True
The error is FileNotFoundError: [Errno 2] No such file or directory: 'datasets/lvis/lvis_v1_val.json'
My datasets download from the link in Downloads.md haven't the above paths, I don't know where is wrong?
Maybe I need deal with the datasets firstly?
Btw, need I uncompress the files cocosplit.tar.gz & cocosplit2017.tar.gz in the datasets/coco and what is it used for?
Thank you for you great work!

Hello, have you solved it? I had the same problem. Thank you.

I have the same problem.
When I try to run
vit=l task=ovd dataset=coco bash scripts/eval.sh
The error is FileNotFoundError: [Errno 2] No such file or directory: 'datasets/coco/val2017/000000000139.jpg'

You need to download the Coco Dataset from the website and place the images into datasets/coco/valXXXX so the images are in the devit folder.
If you are on linux you can just use wget http://images.cocodataset.org/zips/val2017.zip and then unzip the files into the directory

repo: mlzxy/devit


text:
Entanglement issue #3

Added a class Entanglement. Extended little the class Qubit, fixed few bugs.

Great job.

repo: mmcs-ruby/qar


text:
Release 0.2.0

@JuliaRegistrator register
Release notes:
This is an alpha release of a statistical toolbox that does inference for diffusion processes based on path imputation with guided proposals. Since the last version it has seen a major redesign of functionality - making it more accessible as we hope. For more details see the README.md and the documentation. The full release of the package will be announced at a later time.

Registration pull request created: JuliaRegistries/General/4923
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 5b9b8f4d2b0f606859ca249099a9a445b35141c8
git push origin v0.2.0

@JuliaRegistrator register
Release notes:
This is an alpha release of a statistical toolbox that does inference for diffusion processes based on path imputation with guided proposals. Since the last version it has seen a major redesign of functionality - making it more accessible as we hope. For more details see the README.md and the documentation. The full release of the package will be announced at a later time.

Registration pull request updated: JuliaRegistries/General/4923
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" 00c75134c68b1a415d76435975a06dfa0fd845eb
git push origin v0.2.0

@JuliaRegistrator register
Release notes:
This is an alpha release of a statistical toolbox that does inference for diffusion processes based on path imputation with guided proposals. Since the last version it has seen a major redesign of functionality - making it more accessible as we hope. For more details see the README.md and the documentation. The full release of the package will be announced at a later time.

Registration pull request updated: JuliaRegistries/General/4923
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.0 -m "<description of version>" d4f4545ede4f6f53644e752fec6938d1aac6be7f
git push origin v0.2.0

authors: JuliaRegistrator mschauer


text:
Authentication allure

hello, can you add authentication before accessing the allure report, you have to log in first?

@fauzisunarya I'm not sure what are you talking about
This plugin doesn't have any authentication. It only helps to generate allure results, from which you can afterwards generate Allure Report

I mean, I request to add a login page, is that possible sir?

this plugin doesn't have any html generation or html pages. It generates only json files in a proper format for Allure Report to be able to read it. Allure Report is something that I cannot control - it is separate library. If you want something to be added there you should ask them about it.
I addition I want to say that your request is quite strange:  to have login page you need to have a server where login information will be stored, but Allure Report is html with some javascript, it doesn't have any server. If you want to login before accessing the report you need to have your own server for that and implement auth logic there. Or as other option you can use paid version of allure which is called Allure TestOps.

Thank you for the confirmation, I have read about Allure Test Ops, but there is no method or example of a project that uses Cypress, how to implement a Cypress project using Allure Test Ops

there is no difference which test framework you use - cypress, jest, mocha etc. Allure Testops will use generated json files by adapter (which is this plugin helps with). So it is enough for you read Allure TestOps documentation to understand how it should be setup. Also you can use chatGPT, it knows a lot about that.

OK, thank you sir.
You really helped me as a beginner, I hope your luck goes smoothly

authors: fauzisunarya mmisty

repo: mmisty/cypress-allure-adapter


text:
recitationの55番と283番の文ついて、pdfとtxtで相違があります

こんにちは、素晴らしいコーパスの公開ありがとうございます。
2点、pdfとtxtファイルで相違がある文を見つけましたので、報告させていただきます。
■1点目
recitationの55番
「、」がある/ないで相違があります。
pdf：ヌルシアのベネディクトゥスはアポロン神殿を壊し、ベネディクト会の修道院を建てた。
txt：ヌルシアのベネディクトゥスはアポロン神殿を壊しベネディクト会の修道院を建てた。
https://github.com/mmorise/ita-corpus/blob/main/recitation_transcript_utf8.txt#L55
■2点目
recitationの283番
「併せて」「合わせて」で相違があります。
pdf：インスティテュートで、リデュースの話と併せて、ルデュックの話も聞いた。
txt：インスティテュートで、リデュースの話と合わせて、ルデュックの話も聞いた。
https://github.com/mmorise/ita-corpus/blob/main/recitation_transcript_utf8.txt#L283
以上です。よろしくお願いいたします。

ご指摘ありがとうございます．
担当者に確認したところ，どちらもpdfが正しいとのことでした．テキストの方を修正するようにします．

修正を確認しました。ご対応ありがとうございます！

authors: Haruqa mmorise

repo: mmorise/ita-corpus

license: unlicense


text:
Twitter Api support

Added twitter Api, also bounced version number on package.json for release.
Thanks again for porting scribe :)

Nice work! Im glad you appreciated the port, which is still on infant state, but should be ok after few test iterations.

repo: mmstud/scribe-node


text:
Mail TLS is used even if value set to false

root@passbolt-passbolt-helm-598bf58569-5zqql:/var/www/passbolt# printenv | grep EMAIL
EMAIL_TRANSPORT_DEFAULT_PASSWORD=
EMAIL_TRANSPORT_DEFAULT_TIMEOUT=30
EMAIL_TRANSPORT_DEFAULT_USERNAME=
EMAIL_TRANSPORT_DEFAULT_PORT=25
EMAIL_TRANSPORT_DEFAULT_HOST=ourpostfix
EMAIL_DEFAULT_FROM=passbolt@ourdomain
EMAIL_TRANSPORT_DEFAULT_TLS=false

root@passbolt-passbolt-helm-598bf58569-5zqql:/var/www/passbolt# ./bin/cake passbolt send_test_email --recipient=fourslashw@gmail.com

     ____                  __          ____
    / __ \____  _____ ____/ /_  ____  / / /_
   / /_/ / __ `/ ___/ ___/ __ \/ __ \/ / __/
  / ____/ /_/ (__  |__  ) /_/ / /_/ / / /
 /_/    \__,_/____/____/_.___/\____/_/\__/

 Open source password manager for teams
---------------------------------------------------------------
 Debug email shell
---------------------------------------------------------------

Email configuration
---------------------------------------------------------------
Host: ourpostfix
Port: 25
Username:
Password: *********
TLS: true

Sending email from: passbolt@ourdomain
Sending email to: fourslashw@gmail.com

Also same problem with username and password

https://github.com/mmz-srf/passbolt-helm/pull/8 possible fix

Sorry for the late reply and thank you for your contribution.
Looks great so far. We will merge it asap.

It is merged now in Chart Version 1.3.1

authors: fourslashw mms-gianni

repo: mmz-srf/passbolt-helm


text:
SAM vs Serverless: switch to Serverless again?

Yes let's discuss switching back again from SAM to the serverless framework (documentation) 😄  (see #99)
I open this issue because things have moved forward with the serverless framework. Mainly: it supports layers and it can run things locally with Docker.
But another big reason is that, after trying again serverless, it solves a lot of small pain points with SAM. For example:

the region is defined in the config, you never have to deal with it in the CLI
deploy in only one step (instead of 3 with SAM)

and it is extensible. That opens very interesting doors, for example to simplify a lot some things like setting layer ARNs:
Resources:
    SimpleFunction:
        Type: AWS::Serverless::Function
        Properties:
            FunctionName: 'bref-demo-function'
            Handler: function.php
            Runtime: provided
            Layers:
                - 'arn:aws:lambda:us-east-2:209497400698:layer:php-72:4'

After with serverless:
functions:
    bref-demo-function:
        handler: function.php
        runtime: provided
        layers:
            - ${bref:layer.php-72}

What's great with that as well is that runtime versions could be handled by Bref itself, making upgrading Bref as simple as composer update.
In short serverless could help make things simpler.
BC break
If we switch we would direct tooling efforts towards serverless.
However Bref would still work with SAM.
But since the documentation would be rewritten to target serverless I think it could be considered a BC break (or a major change).
Full comparison SAM vs Serverless
Here is a complete comparison of features:
https://docs.google.com/spreadsheets/d/1DP2uVbg6TLfBa56XJ1GwlSSKQM1sM87-S3LQ2Pl9sPI/edit?usp=sharing
Please have a look and comment (here or in Google Docs) what is missing and what should be added to the list.
As you will see Serverless has a lot of advantages, the only big question left is local development.
WDYT?

Hey @mnapoli,
I will always favor Serverless Framework because it's one less vendor lock we have.
I also think SLS framework is better and more documented than SAM.
I will have a look in local dev with custom layer the next few days and will let you know if I get anywhere.  With python I know it works great.

Ok, some updates.
Definitely Possible to run bref locally with SLS.
The test:
the YML:

service: localTest
plugins:
  - serverless-offline
provider:
  name: aws
  runtime: provided
functions:
  hello:
    handler: index.php
    layers:
      - arn:aws:lambda:us-east-1:209497400698:layer:php-72-fpm:6
    events:
      - http: ANY /
      - http: 'ANY {proxy+}'

Install serverless-offline (npm install serverless-offline --save-dev).
In Serverless offline need to edit 2 files,
index.js
Lines 367 to 381:  (need to add --docker if it is provided) need to remove the error they put for provided and allow it.
  // if (serviceRuntime === 'provided') {
   //   if (this.options.providedRuntime) {
   //     serviceRuntime = this.options.providedRuntime;
   //   }
   //   else {
   //     throw new Error('Runtime "provided" is unsupported. Please add a --providedRuntime CLI option.');
   //   }
   // }

   if (!( serviceRuntime.startsWith('provided') || serviceRuntime.startsWith('nodejs') || serviceRuntime.startsWith('python') || serviceRuntime.startsWith('ruby'))) {
     this.printBlankLine();
     this.serverlessLog(`Warning: found unsupported runtime '${serviceRuntime}'`);

     return;
   }

functionHelper.js - (need to add --docker if it is provided)
line 16:
   const args = funOptions.runtime.startsWith("provided") ? ['invoke', 'local', '-f', funOptions.funName, '--docker'] : ['invoke', 'local', '-f', funOptions.funName];
That's it. on console, execute
sls offline
it will start a Webserver in port 3000. Every call he builds the layer and execute.
Everything is working with a test php file.
Of course we need to Edit some things in serverless-offline and make a PR, but we can Definitely run it.
You can edit in the Google Sheets :)

I would ask not to rewrite (a.k.a remove) the SAM documentation. If you decide to change, I understand switching the entire focus of the docs, but keep the bare minimum (layer arn) documented. I would personally stick with CloudFormation since that's where everything else is deployed and the vendor lock-in argument doesn't work at all for my company since we make heavy use of AWS-only services. Having AWS structure declared in the SLS framework is means leaked abstraction which means vendor lock in anyway.
The only commitment I would expect from Bref is to at least never stop providing the layer. I can write my own templates without any help needed from the bref tools and my deployments are powered by AWS CodePipeline with CF so I dont need anything more than aws cloudformation package.
I say this as someone that would love to put bref in production but haven't done so for the fear of instability of an early project. Once it's there I would start using Lambda-only features that would lock me in there and if bref doesn't allow me to update my functions it would be a disaster.

@atrope thanks that sounds really cool, I'll have a look at it. And yes if it's a matter of a quick fix in the plugin I'm sure this is something we can sort out over time.
@deleugpn good points.
Just to be clear I still plan on targeting AWS only for now.
But yes since layers work with SAM or Serverless or any other tool, people can still use Bref tooling with whatever they prefer :+1: The switch to serverless would be mostly useful for those starting and those looking for an all-in-one solution with complete documentation.

Just dumping the link here: https://www.jeremydaly.com/developing-serverless-applications-locally-with-the-serverless-cloudside-plugin/

This new Serverless Framework plugin allows you to use AWS CloudFormation intrinsic functions (such as !Ref and !GetAtt) to reference cloud resources during local development. When used in your environment variables, these values are replaced with the same identifiers used when deployed to the cloud!

It's compatible with serverless-offline as well.
That's another advantage for serverless here ^^

Gotta be extra careful with that one. Imagine pushing local development messages to a Queue and having your deployed worker inside AWS picking those up and trashing your staging / live database.
Pretty cool to see the advancement on tooling around serverless nonetheless.
Personally, I use and recommend localstack. You can provision S3, SQS, SNS, etc in a local container and network it with your application using docker-compose and environment variables. I have a few test code that actually pushes messages to SQS and work them before performing assertions using localstack.

Localstack looks really interesting! There are so many things to try out 😅 But it's great!

FWiW, I'm in favour of serverless.

I would also ask not to remove CloudFormation docs. This will be a huge breaking change. I personally use BREF in my job and we have a setup our "infrastructure as code". Using AWS with BREF, CloudFormation template can be imported in other stacks, and can import stacks as well. With Serverless you loose all that, and forcing you to define everything in your Serverless config.
IMO best case will be to choose what to use during setup time - Serverless or CloudFormation, and then a template will be generated based on your choice. This way changes you plan to introduce will be backwards compatible.
But please don't remove support for CloudFormation as it will break a lot of production apps that currently opted to use Bref and relying on CloudFormation.

@Sh1d0w supporting 2 deployment config (both in the code and documentation) would be too much effort at the moment. One of Bref's principle is this:

simplify problems by removing choices instead of trying to address every need

We should support one format perfectly instead of spreading our effort and making it more confusing for users.

But please don't remove support for CloudFormation as it will break a lot of production apps that currently opted to use Bref and relying on CloudFormation.

Rest assured however that anything you wrote will still work. Also you will still be able to use SAM if you want for new projects. For example right now I use serverless for some projects even though Bref recommends SAM. The PHP layer works with both solutions. Nothing should break.
Also I want to reassure you that serverless configuration supports CloudFormation syntax. There are a few specific bits that a different but anything you do with SAM can be done with serverless. But if you don't want to change that's fine, it will still work.

By reading the documentation, I felt like SAM is not completely local. There is some communication taking place with AWS Cloud although the function itself runs locally.

I support switching to serverless. And I agree that we can't maintain both. Serverless it is!

For those interested there is a WIP in this branch: https://github.com/mnapoli/bref/tree/serverless

For those interested there is a WIP in this branch: https://github.com/mnapoli/bref/tree/serverless

Wow! @mnapoli ! Thank you for the heads up! Can't wait for it to be released. Currently I need to deploy my lambda to multiple regions and doing with sam is a pain.

Nice! You can start using Serverless right now, I've been using it for some projects. It's already compatible.

@mnapoli You made my day! That's really great news! Yay!

@mnapoli A question on serverless plugin usage. Is it supposed I need to copy bref.js to my project .serverless_plugins/ ?
What about ${bref:layer.php-73} variable in serverless.yaml? How is it resolved? Do I need to include bref.yaml into my serverless.yaml?
Thank you!

That is experimental, you can ignore all this and keep using the layer ARN explicitly.

But how can I do it if I need to deploy it to multiple regions? I guess I want to run:
serverless deploy --stage production --region us-east-1
serverless deploy --stage production --region us-west-1
serverless deploy --stage production --region eu-central-1
serverless deploy --stage production --region ap-southeast-1

but if I have the layer ARN specified explicitly it will not work. I was thinking maybe I could modify the plugin to make some sort of switch there and specify ARN for each region?

You can use region variables (see https://serverless.com/framework/docs/providers/aws/guide/variables/) but I'm sorry I can't document everything in this issue.
My first priority is to keep the same set of features. Right now you can't deploy easily to multiple regions with SAM and Bref.

Yeah, it works like this:
        layers:
            - 'arn:aws:lambda:${opt:region}:209497400698:layer:php-73-fpm:6'

awesome! thank you @mnapoli for all your work on bref! can I help you with anything to make it better?

I confirm that @atrope's PR makes it possible to run API Gateway + Lambda locally with Serverless (it works through Docker): https://github.com/dherault/serverless-offline/pull/648
This isn't as fast as it could be (a bit like SAM, the lambda starts from scratch every time) but it can be optimized over time. We need https://github.com/dherault/serverless-offline/pull/648 to be merged (or the worst case would be to fork the plugin to apply the change, but that's way more work).

Hi @mnapoli as i said, i think some work could be done in the future so the docker container would be reutilized instead of initializing from scratch all the time.
I updated the code from master in the PR and fixed what needed to be fixed now we must wait and see if they will approve it.

authors: MadhavChoudhary Sh1d0w akrabat atrope deleugpn esurov mnapoli

repo: mnapoli/bref


text:
bem model and source estimate

Hey guys so I was able to get sLORETA working for evoked data for now. But I have an issue with the BEM model and the source estimate.

If you see here the occipital regions dont have sources. @dgwakeman when you were working on the colin27 t1 did you see this issue?

Also is there an alternative to pysurfer for py3 for now to visualize surface maps?

mayavi should soon work with py3k. In the mean time the answer is no unfortunately.

I don't fully understand. While showing evoked data might be how you detect the problem, it is best to work step by step to trace it. You are trying to view data on a T1 slice. Have you looked at the alignment between the T1 and your source space surfaces? (next move on down the analysis stream checking alignments etc.
hth
d

I see that the plot above is not very informative. I was trying to show you the alignment of the colin t1 and the sources. The following should be more clear.

What does the alignment look like between the T1 and the source space surfaces ?

Closing due to non response, @ImmanuelSamuel feel free to reopen if you have other updates

Finally got back to this. I checked the alignment between the T1 and the BEM model and they are perfectly aligned in freeview.
The following the code I used for analysis:
# source
src = mne.setup_volume_source_space(mri='path/to/colin27.nii')
model = mne.make_bem_model('spm12_canonical_folder',subjects_dir='path/to/spm12_canonical_folder')
bem_sol = mne.make_bem_solution(model)
fwd = mne.make_forward_solution(info, None, src, bem_sol)
cov = mne.compute_covariance(epochs, method='auto')
inv = mne.minimum_norm.make_inverse_operator(info, fwd, cov, loose=1)
stc = mne.minimum_norm.apply_inverse(evoked, inv, lambda2=1. / 9.,  method='dSPM')
volume = stc.as_volume(fwd['src'], dest='mri')

This is what I get:
data:image/png;base64,[encoded data, 46096 characters]

Finally got back to this. I checked the alignment between the T1 and the BEM model and they are perfectly aligned in freeview.
The following the code I used for analysis:
# source
src = mne.setup_volume_source_space(mri='path/to/colin27.nii')
model = mne.make_bem_model('spm12_canonical_folder',subjects_dir='path/to/spm12_canonical_folder')
bem_sol = mne.make_bem_solution(model)
fwd = mne.make_forward_solution(info, None, src, bem_sol)
cov = mne.compute_covariance(epochs, method='auto')
inv = mne.minimum_norm.make_inverse_operator(info, fwd, cov, loose=1)
stc = mne.minimum_norm.apply_inverse(evoked, inv, lambda2=1. / 9.,  method='dSPM')
volume = stc.as_volume(fwd['src'], dest='mri')

This is what I get:

Instead of the last line if I use ...
volume = stc.as_volume(fwd['src'], dest='surf')

... I get the following

mri should point to the T1.mgz file from your freesurfer reconstruction. Could it the pb?

Yes in this case T1.mgz is the freesurfer reconstruction of the colin27 image. Also that and the original are identical right? They both will look the same when loaded in freeview.
What is pb?

I don't know what the problem is
can you try passing the T1.mgz ?
can show me what you get with plot_alignment function?

The freesurfer subject directory is too large for github. But I did try the plot_alignment and I get this

OK so the problem is the alignment as you suspected.
mne.viz.plot_alignment shows:

However freesurfer can properly align it

Since this (using the spm canonical surfaces) had all these issues. I just went ahead and manually edited the BEM surfaces to match my T1. Now the surfaces are very much aligned

The sources are also much better. But there still seems to be some alignment issues especially in the anterior and posterior sources.

you should not have to align manually anything if you rely on a freesurfer
recon (unless we have a but which is possible).
can you share data via dropbox or google drive if it's too big for github ?

Sometimes the meshes are not correct with brain surfaces that are outside the skull. In those cases some surface tweaking is necessary. Will try to get the data to you soon.

@agramfort were you able to look into this?

did you share anything with me? I don't know how we can replicate the pb

Yes, in the last post I had posted the link with the data.

I have your files. thanks. Can you share a script working from the files so
I can easily replicate and investigate?

I'm pretty sure this was due to not properly including the surface information in the BEM files, which has been fixed. Feel free to reopen if I'm wrong

authors: Eric89GXL ImmanuelSamuel agramfort dgwakeman larsoner

repo: mne-tools/mne-python


text:
CUDA crashes with large arrays?

Hitting error on previously processed data after updating to upstream https://github.com/mne-tools/mne-python/commit/3b09ed062226bbe017243071f450e0254fc3a769 data during filter/resampling operations. CUDA complains about array size after initializing:

CUDA not used, could not instantiate memory (arrays may be too large), falling back to n_jobs=1

Then fails with:

Traceback (most recent call last):
File "/home/ktavabi/Projects/shiva/shiva/process.py", line 163, in
print_status=True
File "/home/ktavabi/Projects/mnefun/mnefun/_mnefun.py", line 591, in do_processing
outs[ii] = func(p, subjects, run_indices)
File "/home/ktavabi/Projects/mnefun/mnefun/_mnefun.py", line 1765, in do_preprocessing_combined
phase=p.phase, fir_window=p.fir_window, pick=True)
File "/home/ktavabi/Projects/mnefun/mnefun/_mnefun.py", line 1701, in _raw_LRFCP
r.resample(sfreq, n_jobs=n_jobs_resample, npad='auto')
File "", line 2, in resample
File "/home/ktavabi/Projects/mne-python/mne/utils.py", line 708, in verbose
return function(*args, **kwargs)
File "/home/ktavabi/Projects/mne-python/mne/io/base.py", line 1286, in resample
window=window, n_jobs=n_jobs))
File "", line 2, in resample
File "/home/ktavabi/Projects/mne-python/mne/utils.py", line 708, in verbose
return function(*args, **kwargs)
File "/home/ktavabi/Projects/mne-python/mne/filter.py", line 1804, in resample
cuda_dict)
File "/home/ktavabi/Projects/mne-python/mne/cuda.py", line 341, in fft_resample
x_fft *= W[np.arange(1, len(x) + 1) // 2].real
File "/home/ktavabi/anaconda2/lib/python2.7/site-packages/pycuda/gpuarray.py", line 874, in getitem
raise IndexError("invalid subindex in axis %d" % index_axis)
IndexError: invalid subindex in axis 0

So this doesn't happen on older MNE-Python (like 0.12) but does on master?
This shows that there is definitely a bug with our handling of the case where CUDA seems like it will work during init, but fails later -- but I'm curious whether the fallback worked before. I suspect you'll still hit the could-not-instantiate error on older MNE.

@Eric89GXL No, I've never seen this one before, and I am not sure where/how to go back to figure out how the "bug" was introduced. I am now on branch maint/0.12 and I can reproduce the error with the mne sample data using raw.resample(200, n_jobs='cuda', npad='auto'); I also get the error when running analysis.py with gen_ssp=True on the mnefun funloc datasets.

Oh God...

pycuda.driver.CompileError: nvcc preprocessing of /tmp/tmpqs5L7d.cu failed
[command: nvcc --preprocess -arch sm_30 -I/home/ktavabi/anaconda2/lib/python2.7/site-packages/pycuda/cuda /tmp/tmpqs5L7d.cu --compiler-options -P]
[stderr:
In file included from /usr/local/cuda-7.5/bin/../targets/x86_64-linux/include/cuda_runtime.h:76:0,
from :0:
/usr/local/cuda-7.5/bin/../targets/x86_64-linux/include/host_config.h:115:2: error: #error -- unsupported GNU version! gcc versions later than 4.9 are not supported!
#error -- unsupported GNU version! gcc versions later than 4.9 are not supported!

This is probably yet another CUDA/pyCuda configuration issue on my end

@Eric89GXL It looks like the error is due to an incompatibility between CUDA and gcc version (>4.9) in Ubuntu 16.04. See here and here for related conversations and workaround, and here for general relief.


text:
Adding neural networks as inverse solutions

Describe the new feature or enhancement
The feature
Currently, there are a handful of M/EEG source localization methods available within mne-python: minimum norm estimates and derivatives (dSPM, eLORETA...), equivalent current dipole, sparse bayesian approaches and beamforming. To this list I would like to add artificial neural networks (ANNs) as demonstrated in Hecker et al., 2021. A working implementation outside of MNE can be found here.
Why do I think it's useful?
This feature would add a new approach to the inverse problem, which has shown to work well on simulated data. An implementation within MNE would hopefully allow users to test and compare the ANN-based inverse solutions with the existing and more established approaches using their own data.
Additional comments
I would like to discuss this feature with the mne-python community. Let's say I'll implement this feature such that the devs are satisfied with it. How will maintainence work in the long run? For example, if mne-python receives  major updates in the upcoming years which cause my code to not work anymore - how do you proceed in these cases? My concern is that submodules like this one may clutter the mne-python repository if I don't personally commit to maintainance for an elongated period. I'm happy to hear your thoughts about it!
Literature:
Hecker, L., Rupprecht, R., Tebartz van Elst, L., & Kornmeier, J. (2021). ConvDip: A convolutional neural network for better EEG Source Imaging. Frontiers in Neuroscience, 15, 533.

@LukeTheHecker I would really advise to maintain this in a separate package that is fully compatible with mne.
basically you would have
from my_package import my_great_inverse_method

stc = my_great_inverse_method(fwd, evoked, ...)

stc.plot()

the main reason is the dependency on deep learning toolkits in our CIs that would really like to limit due to an already super long test time.

That makes sense to me, thank you for your fast reply!

authors: LukeTheHecker agramfort


text:
Protect filter against info["{high|low}pass"] None

Proposal for dealing with filtering data where info["highpass"] or info["lowpass"] == None. Currently, the filter compares these fields to a float, which throws an error. Now, instead of checking (h_freq < info["lowpass"]), we check (info["lowpass"] is None or h_freq < info["lowpass"]).
Resolves #1833

Can you test this by setting the corresponding fields to None in one of the filter tests? The test should fail on master, not on this branch.

+1 for merge when travis is happy
thanks @jona-sassenhagen !

AppVoyeur has a problem with pulling some URL, but I think that's not due to the patch. (Travis is happy.)

@jona-sassenhagen thanks!!

nice

authors: agramfort dengemann jona-sassenhagen


text:
FIX: Fix some test warnings, DRY code

Some tweaks to make the code more DRY and silence some test warnings that have cropped up. If the warn=False is for too recent numpy, I can change it to use a backend-lookup pattern.

LGTM
merging thx


text:
[FIX/MAINT/ENH] Covlove clip rank

Work in progress & to be fine tuned.
But here is what I propose (pooling over the last months of discussion):

detect the rank prior to cov estimation and clip the cov if the rank is < n_sensors.
This should then stabilize the performance of plot_white
compute SSSed covariance in a low dimensional space to save time and improve regularization.

cc @agramfort @larsoner

Codecov Report

Merging #4637 into master will decrease coverage by 0.11%.
The diff coverage is 50.34%.

@@            Coverage Diff             @@
##           master    #4637      +/-   ##
==========================================
- Coverage   87.69%   87.57%   -0.12%
==========================================
  Files         351      351
  Lines       66569    66693     +124
  Branches    10345    10379      +34
==========================================
+ Hits        58376    58405      +29
- Misses       5234     5316      +82
- Partials     2959     2972      +13

These changes look too extensive for 0.15. I think we'll want to test for some months before unleashing on the public. 0.16 okay with you?

@larsoner give us one more day to evaluate.
It's more bug fixes

I think this solves a circrular import issue. I could not get it working
inside meas info IIRC ...
On Tue 3 Oct 2017 at 18:16, Eric Larson notifications@github.com wrote:

@larsoner commented on this pull request.
In mne/io/tests/test_proc_history.py
https://github.com/mne-tools/mne-python/pull/4637#discussion_r142449681:

from mne.io.constants import FIFF
-from mne.io.proc_history import _get_sss_rank
+from mne import _get_rank_sss

I don't think we should put this at the root level, it seems better buried
in io.proc_history
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/4637#pullrequestreview-66812508,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0finPbHNZC2K2yQmF8a07XXvH1vwIuks5sol3OgaJpZM4Pr1jp
.

I think this solves a circrular import issue.

Probably better to solve it with a nested import

Let me try that. I agree that it is far from ideal as it is now.
On Tue 3 Oct 2017 at 19:04, Eric Larson notifications@github.com wrote:

I think this solves a circrular import issue.
Probably better to solve it with a nested import
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/4637#issuecomment-333911948,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0figbEj6p9-V27mbDiJPvOsX0dO719ks5somk0gaJpZM4Pr1jp
.

Circle CI is happy: https://6087-1301584-gh.circle-artifacts.com/0/tmp/circle-artifacts.Vslzm8M/html/auto_tutorials/plot_compute_covariance.html#sphx-glr-auto-tutorials-plot-compute-covariance-py

@larsoner @larsoner @jasmainak this is good for review.

@dengemann I am sorry I need one more day before I can try it on biomag data ...

@dengemann you have some undesired commits in this PR (stuff already in master)

@dengemann you need to rebase and clean history...

Copied that. Did not have time yet to fix the mess.
On Mon 9 Oct 2017 at 20:44, Alexandre Gramfort notifications@github.com
wrote:

@dengemann https://github.com/dengemann you need to rebase and clean
history...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/pull/4637#issuecomment-335251814,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fimMt59CWm326Td1_oe2LE5mznQTZks5sqml0gaJpZM4Pr1jp
.

Travis failure is the unrelated OSX failure currently in master.
Can you add to whats_new.rst to summarize the change? Maybe toward the top of BUG so it's clear what's fixed. Otherwise LGTM!

Slightly OT, but do you think this can be merged ASAP to finalize 0.15 (if possible, please consider #4662, which is ready to go, but I'd argue for no further major delays)?

but do you think this can be merged ASAP to finalize 0.15

+1 yes I think this is all we are waiting for currently

Closing to split into mergeable and more-dev-to-do part.

authors: agramfort cbrnr codecov-io dengemann jasmainak larsoner


text:
fix(client): return chained promise to avoid unhandled promise rejections

Closes #19

I don't understand how it solves the problem: if promise is in the rejected state, without the second callback of then (or a catch), it will still be rejected, no ?

The code does this:
var promise = ???;  // first instance created, it's a failed promise
promise.then(???); // second instance created, but it's discarded (not returned)
return promise;

the engine complains about an unhandled promsie because of line 2 in my example. The then function, like the map on Future[T] in Scala, gives you a new Promise. If it's in a failed state and you don't catch it, node complains.
LGTM 👍

💡  : it works because of side effect...
The catch is done by the called of this function...
ok for me then.

The catch is done by the caller of this function...

The code was not broken, it was working (because of a side effect, yes). The warning in the console did not mean the code was broken.

Yes indeed, I was not chaining the promises properly. Leaking one along the way.

authors: blemoine daddykotex jtheoof

repo: mnubo/smartobjects-js-client


text:
"Server do not support X-OC-MTime" from owncloudcmd

While using owncloudcmd to sync files to a Davros grain, I get a message in my owncloudcmd log that says:
Server do not support X-OC-MTime ""
I suspect it would be wise for us to add support to this to Sandstorm. Presumably my client is going to submit duplicated requests to Davros based on not having access to remote mtimes, so I thought I should file this.
Slightly longer log snippet:
!!! OCC::PUTFileJob created for "https://api.rose.sandcats.io/" + "/pub/pub/scrapy-talk/_static/up.png"
void OCC::PropagateUploadFileQNAM::slotPutFinished() QUrl("https://sandstorm@api.rose.sandcats.io/remote.php/webdav/pub/pub/scrapy-talk/_static/up.png") FINISHED WITH STATUS QNetworkReply::NetworkError(NoError) "" QVariant(int, 201) QVariant(QString, "Created")
Server do not support X-OC-MTime ""
*==* duration UPLOAD 363 0 1166
OCC::SyncJournalFileRecord::SyncJournalFileRecord(const OCC::SyncFileItem&, const QString&) "./pub/pub/scrapy-talk/_static/up.png" Retrieved inode  331892 (previous item inode:  331892 )
"INSERT OR REPLACE INTO metadata (phash, pathlen, path, inode, uid, gid, mode, modtime, type, md5, fileid, remotePerm, filesize, ignoredChildrenRemote) VALUES (?1 , ?2, ?3 , ?4 , ?5 , ?6 , ?7,  ?8 , ?9 , ?10, ?11, ?12, ?13, ?14);" -1275537046966359755 34 "pub/pub/scrapy-talk/_static/up.png" 331892 0 "1374686074" "0" "e06a5c2d79aa917614dcd2977bbbd27c" "" "" 363 0
"DELETE FROM uploadinfo WHERE path=?1" "pub/pub/scrapy-talk/_static/up.png"
void OCC::SyncJournalDb::commitInternal(const QString&, bool) Transaction commit  "upload file start" and starting new transaction
void OCC::SyncEngine::slotItemCompleted(const OCC::SyncFileItem&, const OCC::PropagatorJob&) "pub/pub/scrapy-talk/_static/up.png" INSTRUCTION_NEW 4 ""
!!! OCC::PUTFileJob created for "https://api.rose.sandcats.io/" + "/pub/pub/scrapy-talk/_static/view-source.img"

Moving here from https://github.com/sandstorm-io/sandstorm/issues/1205

Funny enough, the first search result for "x-oc-mtime" is now this github issue. In digging around in the owncloud source, it seems that x-oc-mtime is actually just a piece of metadata the server is expected to hold onto.
Unfortunately right now Davros' storage is just the filesystem, so I'm not sure there's an easy way to keep these around. At some point in the mid-term future I'd like to revamp the storage layer to add things like metadata and versioning, and at that point it would be a lot easier to support this.

FWIW, since Davros uses the filesystem, and the x-oc-mtime seems to mirror
the filesystem's concept of "modified time" aka "mtime", it seems to me
that Davros can use
https://nodejs.org/api/fs.html#fs_fs_futimes_fd_atime_mtime_callback
fs.futimes() to change the mtime.
Other reference:

http://owncloud.10557.n7.nabble.com/API-to-set-MTIME-of-files-td14962.html

I have a partially working implementation of this, but it turns out that X-OC-MTime needs both a request and response header in order to work. (client sends X-OC-MTime: 123456789, server sends X-OC-MTime: accepted) So I think the best bet is to wait on https://github.com/sandstorm-io/sandstorm/pull/1202 to be merged.

Just wanted to add I saw this error today too in this constellation:
Installed owncloud client on my MACbook, copied a folder with some 20 files or so into it, then installed the client on Windows 10 and about 6 files or so were giving this error and had not been synced to the Win10 machine. I then quit/restarted the client on the MAC and the files were synced to my sandstorm instance. Once I quit and restarted the Win10 client the changes were synced there too.No more X-OC-Time errors.
No idea what went on here but there you go.

So if davros gives  me this mtime error, that does mean those files have not been synced, right?

Unfortunately it looks like we're still stuck on https://github.com/sandstorm-io/sandstorm/pull/1202, but I don't believe the x-oc-mtime warning should hurt anything. It may just involve an extra request as the client verifies its version matches the server's.

I had believed that this was just a warning, but it appears that there may be some mysterious off-by-one error in the Owncloud client which causes crashes relating to this header. smashbox (the owncloud acceptance test suite) fails hard when no X-OC-MTime: accepted header is sent, but works when it is.
It's doubly unfortunate since mtime is a totally unreliable thing to sync across machines due to clock differences, etc.

This is now fixed.

authors: mnutt ovizii paulproteus

repo: mnutt/davros


text:
Missing style files from Bootstrap template

Description
The vender folder was removed from the original setup branch. A sub-folder datables is needed for the Table visualization. There are also calls to the jquery subfolders and fontawsome-free folder

Just verify the license is OK?

https://startbootstrap.com/themes/sb-admin-2/
MIT Licence

authors: Erik-Handeland arunk054 thorncorona


text:
Flakyness when running flow on android emulator

When running a flow on an emulator maestro sometimes fail to assertVisibility of some text.
I can see the text in Maestro Studio. When running the same flow several times in a row it sometimes fails and sometimes run successfully. The element is not present in the hierarchy (maestro hierarchy) if the test fails, and is present when it succeeds.
There are no animations or loading state interfering with this test, and I've tried different ways of referencing, scrolling, and waiting for the element:
- scrollUntilVisible:
    element:
      text: "Gi tilbakemelding"
- extendedWaitUntil:
    visible:
       text: "Gi tilbakemelding"
    timeout: 10000
- assertVisible:
    text: "Gi tilbakemelding"
- assertVisible: Gi tilbakemelding

I'm not experiencing any issues when running the same flow on a physical device.
Issue is discussed on slack: https://mobile-dev-inc.slack.com/archives/C041FU72T54/p1678700923860579
Maestro version: 1.24.0
Emulator: API 32, arm64

I'm seeing a similar issue for a Compose lazy list that's populated after a delay. I've noticed that while the test is running, maestro hierarchy indeed does not include the desired element, but almost immediately after the test fails maestro hierarchy does include the element. I hypothesized that the rapid polling of the hierarchy was preventing it to update somehow, but adding a delay with exponential back-off of up to 2 seconds did not help.
Finally, I was able to workaround the issue in a very hacky way by something like this:
- repeat:
    while:
      notVisible: ${desired_text}
    commands:
      - assertVisible:
          text: ${desired_text}
          optional: true
      - tapOn: "foobar"  # Whatever idempotent interaction just to trigger the hierarchy to update
# continue with the rest of the test
...

@Dambakk Hi there! If you upgrade to the most recent version of maestro, are you still experiencing issues? If so, please share reproduction steps (Flows and app file) if you are able to and we will take a look.

I have upgraded to maestro 1.27.0, ran some flows and was not able to reproduce the issue described here! I guess we can consider this issue resolved! :)

authors: Dambakk axelniklasson larryng

repo: mobile-dev-inc/maestro


text:
Add QR code reader states, update overlay view look and feel

I wanted to refactor the code to allow the user to change the state of the overlay and decouple QR code parsing logic from the pod. The idea is that the module would simply parse a QR code to a string, and our SDK would handle the result, as well as directly changing the state of the overlay view based on a parsed code.

UPD: QR code scanning and validation for MobileCoin codes are extremely fast, so the "reading" dashed line overlay likely won't be needed at all.


text:
Add detailed documentation about the gsd evaluation parameters

Once #81 is merged, we should add detailed explanations for the calculated metrics in the respective docstrings

@felixkluge Do you have time to look into this?

repo: mobilise-d/mobgap


text:
Add New doc form gets pre-filled with previous doc info

On FF, when I view other doc on its modal prior to adding new doc the form gets pre-filled with previous doc info. On Chrome, only 'Campaign' field gets pre-filled with previous doc info.

should be fixed now, tested in FF24 and chrome and no fields are erroneously pre-filled.

fixed

authors: ctrance stevenolen


text:
describe.only runs multiple unrelated tests

When multiple unit tests have same name in describe, mocha ignores the .only setting.
Steps to reproduce:

Create test1.js and test2.js as per template below
Run mocha test1.js test2.js -R spec
Expected result

You should see only the test1 to get run

Actual result

Both test1 and test2 get run

test1.js
describe.only('Test', function () {
        it('Should run test1 only', function() {});
});

test2.js
describe('Test', function () {
        it('Should run test2', function() {});
});

This substring matching is a pain in the rear for us as well. When we mark describe as .only we'd expect that only that particular describe block will run. I understand maybe running another describe if the string matches 100%, but substring matches should be excluded IMHO.

+1, I think this issue is sabotaging my tests right now as well.

+1 this is really needs fixing. I would consider this a bug fix, the documented behaviour is:

The exclusivity feature allows you to run only the specified suite or test-case by appending .only() to the function.

I don't think prioritising upsetting someone relying on a bug over everyone else expecting documented behaviour is a good reason to not fix it.

if @mochajs/mocha can agree it's a bug, then it could go into a minor

@boneskull rather than discuss that (although I could be convinced to go put it in a minor [that sounds worrying]), how about we change #1782 to become a release of v3.0.0 in stead, merge #1632 and #1481 asap, lift the rest of milestone V3.0.0 to the next major release and ship v3.0.0? :)

This has bitten me multiple times and kind of stinks. Is there a better way we could do preprocessing of all .only() and build out a tree? The desired behavior is such that I can mark a 'top level' suite with only, then as I work through sub-level describes I can attach another only without having to remove the top-level marker.

This issue is causing problems for me because I want to describe my tests in a hierarchical structure like below, but then it is not possible to run one suite exclusively.
describe('components/Form', function() { ... })
describe('components/FormField', function() { ... })
describe('components/FormControls', function() { ... })

@PerlPong Why not restructure the specs to be something like this:
context('components', function () {
  describe('Form', function () {...});
  describe('FormField', function () {...});
  describe('FormControls', function () {...});
});

@demisx thanks for the tip, but unfortunately it does not work around this bug. If you execute the following with mocha, both suites will run:
var expect = require('chai').expect;

context('components', function() {
    describe.only('Form', function() {
        it('should be true', function () {
            expect(true).to.be.true;
        });
    });
    describe('FormField', function() {
        it('should be false', function () {
            expect(false).to.be.false;
        });
    });
});

  components
    Form
      ✓ should be true
    FormField
      ✓ should be false

@PerlPong  I see. Yeah, I believe if the spec describe string matches or starts with the string that you set .only on, it will run that test too. Ran into this inconvenience in the past myself and had to ensure my describes always start with a unique string.

Closing in favor of #1481. PR #1807 (referencing that other issues) is in the works .

authors: BobbieBarker PerlPong aft-luke boneskull dasilvacontin demisx dominataa jbnicolai lobodpav

repo: mochajs/mocha


text:
Default test directory with non-global mocha installation

I am trying to write an npm script in my package.json to run a bunch of pre-test tasks followed by my mocha unit tests. I want the caller to be able to specify which paths mocha will run. This is how it's currently implemented, which works correctly if I want to run all tests in my test directory.
"test": "eslint && gulp db:prepare_test && istanbul cover _mocha ./test"

If I want to specify a single test or directory for mocha to run, I can do this:
"test": "eslint && gulp db:prepare_test && istanbul cover _mocha --"

and then call it like this:
npm test ./path/to/specific/test.js

The second form should, theoretically, support both the default case and the specific case. So if I don't specify a path, it will default to the test directory. However, the default case does not work, and results in 0 tests being executed.
I'm going to assume this is because I'm not using the global installation of mocha, so the node_modules version in my project doesn't know where to look for the default test directory to run. If that's the case, I guess this can be filed as a bug?

Consider "pretest" (which is run before "test" automatically) for your pre-test tasks, if for no other reason than to help narrow down issues like this. I'd guess anything before the final && can/should be moved there.
Mocha is designed to be run from a local install, because it's used heavily in continuous integration; if anything, global installation is not deliberately supported and is potentially hazardous (e.g. having two installs can interfere with each other in subtle ways, or you can call the wrong version when running manually).
Mocha's default test directory is test and it will find it if you really are running the local version and nothing else is interfering, as this is the normal way Mocha is used with such a folder.
I don't know what happens if you use _mocha instead of mocha; the former is, if I'm not mistaken, an artifact of how some technicalities are handled while the latter is typically intended for actual usage (mocha will run _mocha with some additional wrapping/configuration that could be relevant here).
Try an NPM script that runs Mocha directly, or running the local instance of Mocha yourself, instead of the version augmented with istanbul, in order to confirm that it isn't an issue with correct usage of the istanbul augmentation.
Do you have a test/mocha.opts file that could be interfering?

@ScottFreeCode Thank you for the detailed response! It led me to discover the real problem, which  wasn't so much a problem as a misunderstanding.
I had a mocha.opts file which had this line:
--require test/globals.js test/setup_test.js

I assumed this was requiring both files, which allowed me to declare global beforeEach and afterEach hooks in setup_test.js. But what it actually does is tell mocha to run the setup_test.js file, overwriting the default test path.

authors: RyanMcDonald ScottFreeCode


text:
Fix some issues reported by lintian

Fix some issues reported by lintian

Set upstream metadata fields: Bug-Database, Bug-Submit. (upstream-metadata-file-is-missing, upstream-metadata-missing-bug-tracking)
Drop unnecessary dependency on dh-autoreconf. (useless-autoreconf-build-depends)

This merge proposal was created automatically by the Janitor bot.
You can follow up to this merge proposal as you normally would.
The bot will automatically update the merge proposal to resolve merge conflicts
or close the merge proposal when all changes are applied through other means
(e.g. cherry-picks). Updates may take several hours to propagate.
Build and test logs for this branch can be found at
https://janitor.debian.net/lintian-fixes/pkg/boxfort/053cef02-a2e3-4dbf-8eeb-96eb76cd8f13.
These changes have no impact on the binary debdiff.
You can also view the diffoscope diff (unfiltered).

This merge proposal will be closed, since the branch for the role 'main'
has changed to None.

repo: mochrul/BoxFort-debian


text:
Mocking internal types results in compiler errors

Hey!
When I was using Mockative in combination with internal interfaces, I ran into compiler errors. I suspect that right now, Mockative only generates public stubs for the mock<TSomething>(...) call and assume that corresponding support has to be added here: https://github.com/mockative/mockative/blob/main/mockative-processor/src/main/kotlin/io/mockative/kotlinpoet/ProcessableFunction.KotlinPoet.kt#L33
Maybe somebody could verify this issue and tell me, if I my speculations are correct.
Thank you.

Hi @firefligher
Can you share a snippet of the internal interface you're trying to mock as well as the error you're seeing?

Closing due to inactivity.

authors: Nillerr firefligher

repo: mockative/mockative


text:
await client.hello()

Just noticed this

Check these boxes or delete any item (or this section) if not relevant for this PR.

[x] Client+Server: this change is compatible with old servers
[x] Client forward compatibility: this change ensures client can accept data intended for later versions of itself

Note on protobuf: protobuf message changes in one place may have impact to
multiple entities (client, server, worker, database). See points above.

Changelog

@prbot approve

repo: modal-labs/modal-client


text:
GPT3 13B,30B下载和175B模型体验开放时间？

您好GPT3的13B，30B模型现在是没有放出的状态，现在实验室想使用一下模型做一些实验，是否有申请下载的途径？
175B的之前在modelscope说一月份放出在线体验，何时放出？会延期么？

您好，实验室申请模型下载，可以辛苦您写出具体的实验室的名称，以及申请的背景，发送邮件到contact@modelscope.cn, 我们请模型的贡献者评估后给您答复。
175B的模型目前还没有明确在modelscope社区的在线体验的时间，如果确认可以体验后，会随着release note发出，请关注社区公告，谢谢您

好的邮件已经发送，希望尽快回复哈

@ccyhxg 请问1.3B和2.7B的中文预训练模型有计划开放下载的时间吗？

@ccyhxg 请问1.3B和2.7B的中文预训练模型有计划开放下载的时间吗？

1.3B:
https://www.modelscope.cn/models/damo/nlp_gpt3_text-generation_1.3B/summary
2.7B:
https://www.modelscope.cn/models/damo/nlp_gpt3_text-generation_2.7B/summary

authors: ccyhxg chasonlee liuxz0801 yingdachen

repo: modelscope/modelscope


text:
微调qwen1.5 110B chat后会重复说

Describe the bug
微调后模型输出结果天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于一天半的时间，相当于

微调2个epoch后的效果

调崩了，考虑增大数据量，数据分布也要考虑一下

请问改善了吗

authors: lylala8 tastelikefeet zhangfan-algo

repo: modelscope/ms-swift