text:
android.os.BadParcelableException: Unable to start activity ComponentInfo{com.mixpanel.android.surveys.SurveyActivity}

Hi,
Mixpanel SDK: 'com.mixpanel.android:mixpanel-android:4.5.3'
Our app crashes with the following stack traces.

java.lang.RuntimeException: Unable to start activity ComponentInfo{<packagename>/com.mixpanel.android.surveys.SurveyActivity}: android.os.BadParcelableException: Parcelable protocol requires a Parcelable.Creator object called CREATOR on class com.mixpanel.android.mpmetrics.Survey
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2661)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2726)
at android.app.ActivityThread.access$900(ActivityThread.java:172)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1421)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:145)
at android.app.ActivityThread.main(ActivityThread.java:5835)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1388)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1183)
Caused by: android.os.BadParcelableException: Parcelable protocol requires a Parcelable.Creator object called CREATOR on class com.mixpanel.android.mpmetrics.Survey
at android.os.Parcel.readParcelableCreator(Parcel.java:2298)
at android.os.Parcel.readParcelable(Parcel.java:2239)
at android.os.Parcel.readValue(Parcel.java:2146)
at android.os.Parcel.readArrayMapInternal(Parcel.java:2479)
at android.os.BaseBundle.unparcel(BaseBundle.java:221)
at android.os.BaseBundle.getInt(BaseBundle.java:781)
at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState.<init>(UpdateDisplayState.java:184)
at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState.<init>(UpdateDisplayState.java:107)
at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState$1.a(UpdateDisplayState.java:116)
at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState$1.createFromParcel(UpdateDisplayState.java:111)
at android.os.Parcel.readParcelable(Parcel.java:2246)
at android.os.Parcel.readValue(Parcel.java:2146)
at android.os.Parcel.readArrayMapInternal(Parcel.java:2479)
at android.os.BaseBundle.unparcel(BaseBundle.java:221)
at android.os.BaseBundle.getString(BaseBundle.java:918)
at com.mixpanel.android.mpmetrics.UpdateDisplayState.<init>(UpdateDisplayState.java:424)
at com.mixpanel.android.mpmetrics.UpdateDisplayState.<init>(UpdateDisplayState.java:25)
at com.mixpanel.android.mpmetrics.UpdateDisplayState$1.a(UpdateDisplayState.java:380)
at com.mixpanel.android.mpmetrics.UpdateDisplayState$1.createFromParcel(UpdateDisplayState.java:375)
at android.os.Parcel.readParcelable(Parcel.java:2246)
at android.os.Parcel.readValue(Parcel.java:2146)
at android.os.Parcel.readArrayMapInternal(Parcel.java:2479)
at android.os.BaseBundle.unparcel(BaseBundle.java:221)
at android.os.Bundle.getParcelable(Bundle.java:804)
at android.app.Activity.onCreate(Activity.java:981)
at com.mixpanel.android.surveys.SurveyActivity.onCreate(SurveyActivity.java:65)
at android.app.Activity.performCreate(Activity.java:6221)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2614)
... 10 more

Seeing the same problem with 4.6.0:

compile 'com.mixpanel.android:mixpanel-android:4.6.0'

java.lang.RuntimeException: Unable to start activity ComponentInfo{<app package>/com.mixpanel.android.surveys.SurveyActivity}: android.os.BadParcelableException: Parcelable protocol requires a Parcelable.Creator object called  CREATOR on class com.mixpanel.android.mpmetrics.Survey
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2693)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2758)
	at android.app.ActivityThread.access$900(ActivityThread.java:177)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1448)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loop(Looper.java:145)
	at android.app.ActivityThread.main(ActivityThread.java:5942)
	at java.lang.reflect.Method.invoke(Native Method)
	at java.lang.reflect.Method.invoke(Method.java:372)
	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1399)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1194)
Caused by: android.os.BadParcelableException: Parcelable protocol requires a Parcelable.Creator object called  CREATOR on class com.mixpanel.android.mpmetrics.Survey
	at android.os.Parcel.readParcelableCreator(Parcel.java:2298)
	at android.os.Parcel.readParcelable(Parcel.java:2239)
	at android.os.Parcel.readValue(Parcel.java:2146)
	at android.os.Parcel.readArrayMapInternal(Parcel.java:2479)
	at android.os.BaseBundle.unparcel(BaseBundle.java:221)
	at android.os.BaseBundle.getInt(BaseBundle.java:781)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState.<init>(SourceFile:184)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState.<init>(SourceFile:107)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState$1.createFromParcel(SourceFile:116)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState$DisplayState$SurveyState$1.createFromParcel(SourceFile:111)
	at android.os.Parcel.readParcelable(Parcel.java:2246)
	at android.os.Parcel.readValue(Parcel.java:2146)
	at android.os.Parcel.readArrayMapInternal(Parcel.java:2479)
	at android.os.BaseBundle.unparcel(BaseBundle.java:221)
	at android.os.BaseBundle.getString(BaseBundle.java:918)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState.<init>(SourceFile:424)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState.<init>(SourceFile:25)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState$1.createFromParcel(SourceFile:380)
	at com.mixpanel.android.mpmetrics.UpdateDisplayState$1.createFromParcel(SourceFile:375)
	at android.os.Parcel.readParcelable(Parcel.java:2246)
	at android.os.Parcel.readValue(Parcel.java:2146)
	at android.os.Parcel.readArrayMapInternal(Parcel.java:2479)
	at android.os.BaseBundle.unparcel(BaseBundle.java:221)
	at android.os.Bundle.getParcelable(Bundle.java:804)
	at android.app.Activity.onCreate(Activity.java:991)
	at com.mixpanel.android.surveys.SurveyActivity.onCreate(SourceFile:65)
	at android.app.Activity.performCreate(Activity.java:6289)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1119)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2646)
	... 10 more

We are still getting this errors on mixpanel v4.7.0. Are there any updates about this crash?

We update Mixpanel to 4.8.0. We also turned on surveys in our app which is causing our app with this crash. Can you please fix this?

@Digisha I've just pushed a change and it should fix it. Are you using proguard when this crash happens?

@patedit Thanks for the fix. Yes, the crash happening on our release build which has proguard turned on.

@Digisha Thanks for the info! Let me know if 4.8.5 fixes your issue :)

@patedit We have a build running with 4.8.5 fixes and we are not seeing this issue anymore. Thanks again for the fix.

Thanks for the update! Glad it is solved :)

@GreenDeveloperMukesh What's the SDK version you are using? Could you provide an stack trace and how to reproduce your issue?

I got it fixed thankyou

I am also seeing a similar crash in the wild, mixpanel version is 5.0.0 and proguard is on.
Let me know if you need more details.
Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{<appPackage>/<appPackage>.<appActivity>}: android.os.BadParcelableException: ClassNotFoundException when unmarshalling: com.facebook.flatbuffers.helpers.FlatBufferModelHelper$LazyHolder
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3319)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3415)
       at android.app.ActivityThread.access$1100(ActivityThread.java:229)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1821)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:148)
       at android.app.ActivityThread.main(ActivityThread.java:7325)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
Caused by android.os.BadParcelableException: ClassNotFoundException when unmarshalling: com.facebook.flatbuffers.helpers.FlatBufferModelHelper$LazyHolder
       at android.os.Parcel.readParcelableCreator(Parcel.java:2432)
       at android.os.Parcel.readParcelable(Parcel.java:2358)
       at android.os.Parcel.readValue(Parcel.java:2264)
       at android.os.Parcel.readArrayMapInternal(Parcel.java:2614)
       at android.os.BaseBundle.unparcel(BaseBundle.java:221)
       at android.os.BaseBundle.containsKey(BaseBundle.java:269)
       at android.content.Intent.hasExtra(Intent.java:6040)
       at com.mixpanel.android.mpmetrics.MixpanelActivityLifecycleCallbacks.onActivityStarted(SourceFile:31)
       at android.app.Application.dispatchActivityStarted(Application.java:229)
       at android.app.Activity.onStart(Activity.java:1324)
       at android.support.v4.app.FragmentActivity.onStart(SourceFile:595)
       at android.support.v7.app.AppCompatActivity.onStart(SourceFile:178)
       at<appActivity>.<appBaseActivity>.onStart(SourceFile:59)
       at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1266)
       at android.app.Activity.performStart(Activity.java:6943)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3276)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3415)
       at android.app.ActivityThread.access$1100(ActivityThread.java:229)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1821)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:148)
       at android.app.ActivityThread.main(ActivityThread.java:7325)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

I'm getting same issue with no proguard. BadParcelableException: ClassNotFoundException when unmarshalling: com.facebook.events.common.ActionSource

I don't know how to reproduce it but it's the same as @mvarnagiris.... I suppose
Android 7.0 and 6.0.1
with
compile "com.mixpanel.android:mixpanel-android:5.+"
Here is the complete StackTrace
Fatal Exception: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.wesmartpark.parking/com.wesmartpark.parking.SplashScreen}: android.os.BadParcelableException: ClassNotFoundException when unmarshalling: com.facebook.events.common.ActionSource
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2984)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3045)
       at android.app.ActivityThread.-wrap14(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1642)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)
Caused by android.os.BadParcelableException: ClassNotFoundException when unmarshalling: com.facebook.events.common.ActionSource
       at android.os.Parcel.readParcelableCreator(Parcel.java:2545)
       at android.os.Parcel.readParcelable(Parcel.java:2471)
       at android.os.Parcel.readValue(Parcel.java:2374)
       at android.os.Parcel.readArrayMapInternal(Parcel.java:2727)
       at android.os.BaseBundle.unparcel(BaseBundle.java:269)
       at android.os.BaseBundle.containsKey(BaseBundle.java:341)
       at android.content.Intent.hasExtra(Intent.java:6561)
       at com.mixpanel.android.mpmetrics.MixpanelActivityLifecycleCallbacks.onActivityStarted(MixpanelActivityLifecycleCallbacks.java:37)
       at android.app.Application.dispatchActivityStarted(Application.java:231)
       at android.app.Activity.onStart(Activity.java:1271)
       at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:595)
       at com.my.SplashScreen.onStart(SplashScreen.java:254)
       at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1256)
       at android.app.Activity.performStart(Activity.java:6972)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2937)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3045)
       at android.app.ActivityThread.-wrap14(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1642)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:154)
       at android.app.ActivityThread.main(ActivityThread.java:6776)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1520)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1410)

Hope this info is useful to reproduce it....
I can't reproduce it, this info are from the analytics service we use to track app exceptions.
:)

It seems that Facebook is messing with us, developers that rely on good practices. This issue has affected projects like firefox or chromium and I've sent a PR #483
Thanks for reporting this!

It is a missing enum in the facebook android sdk, which can only be handled in the app. I havea 'fix' for it:
https://github.com/seviu/facebook-android-sdk
Basicaly create an enum com.facebook.events.common.ActionSource with the following implementation:
`package com.facebook.events.common;
import android.os.Bundle;
import android.os.Parcel;
import android.os.Parcelable;
public enum ActionSource implements Parcelable {
UNKNOWN(0),
PERMALINK(1),
DASHBOARD(2),
NEWSFEED(3),
GROUP(4),
PAGE(5),
TIMELINE(22),
NOTIFICATION(29),
GRAPH_SEARCH(70),
LAUNCHER(78),
PAGE_UPCOMING_EVENTS_CARD(98),
MOBILE_SUGGESTIONS_DASHBOARD(201),
MOBILE_SUGGESTIONS_LIST(202),
MOBILE_EVENT_COMPOSER(203),
MOBILE_BOOKMARK_TAB(206),
MOBILE_SYSTEM_NOTIFICATION(207),
MOBILE_SUBSCRIPTIONS_DASHBOARD(208),
MOBILE_SUBSCRIPTIONS_LIST(209),
GUESTS_VIEW(400);
public static final String ACTION_REF_PARAM = "action_ref";

private final int mParamValue;

public static final Creator<ActionSource> CREATOR = new Creator<ActionSource>() {
    @Override
    public ActionSource createFromParcel(Parcel source) {
        String name = source.readString();
        return ActionSource.valueOf(name);
    }

    @Override
    public ActionSource[] newArray(int size) {
        return new ActionSource[0];
    }
};

private ActionSource(int i) {
    this.mParamValue = i;
}

public int describeContents() {
    return 0;
}

public int getParamValue() {
    return this.mParamValue;
}

public static void putActionRef(Bundle bundle, ActionSource actionSource) {
    bundle.putParcelable(ACTION_REF_PARAM, actionSource);
}

public void writeToParcel(Parcel parcel, int i) {
    String name = name();
    parcel.writeString(name);
}

}
`

Thanks for the tip @seviu ! This has been handled in the SDK for a while now as well :)

authors: AamirAbro Digisha GreenDeveloperMukesh jjchiw lnanek mvarnagiris patedit seviu

repo: mixpanel/mixpanel-android


text:
RangeError: Maximum call stack size exceeded

Hello! I'm getting the following errors in our error logging system, and I can't figure out what's causing them. Do you have any thoughts about what the problem might be?
RangeError: Maximum call stack size exceeded
    at e.push(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:92)
    at getLibrarySnippets(webpack:///./js/core/analytics.js:142)
    at a.push([d].concat(Array.prototype.slice.call(arguments, 0)));
    at e.<anonymous>(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:90)
    at c.a(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:15)
    at b(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:90)
    at e.Aa(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:91)
    at e.push(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:92)
    at getLibrarySnippets(webpack:///./js/core/analytics.js:142)
    at a.push([d].concat(Array.prototype.slice.call(arguments, 0)));
    at e.<anonymous>(https://cdn.mxpnl.com/libs/mixpanel-2-latest.min.js:90)

I am also seeing this. Any updates?

source: gharchive/issue

authors: distolma hraschke-sift

repo: mixpanel/mixpanel-js

license_type: permissive

license_source: github-api


text:
java.lang.IllegalAccessError when trying to access syncBranchesLog

When I'm trying to view the syncBranchesLog for a project the following error occures since 0.3:

javax.servlet.ServletException: java.lang.IllegalAccessError: tried to access method com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject.getSyncBranchesTrigger()Lcom/github/mjdetullio/jenkins/plugins/multibranch/SyncBranchesTrigger; from class com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject$SyncBranchesTransientActionFactory
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:370)
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949)
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668)
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.IllegalAccessError: tried to access method com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject.getSyncBranchesTrigger()Lcom/github/mjdetullio/jenkins/plugins/multibranch/SyncBranchesTrigger; from class com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject$SyncBranchesTransientActionFactory
at com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject$SyncBranchesTransientActionFactory.createFor(AbstractMultiBranchProject.java:1477)
at com.github.mjdetullio.jenkins.plugins.multibranch.AbstractMultiBranchProject$SyncBranchesTransientActionFactory.createFor(AbstractMultiBranchProject.java:1458)
at hudson.model.Actionable.createFor(Actionable.java:107)
at hudson.model.Actionable.getAllActions(Actionable.java:98)
at hudson.model.Actionable.getActions(Actionable.java:119)
at hudson.model.Job.getPermalinks(Job.java:1033)
at hudson.model.Job.getDynamic(Job.java:810)
at sun.reflect.GeneratedMethodAccessor244.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:409)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
... 63 more

The logfile is ok when accessed via filesystem.

Looks like a plugin classloading problem.  Have you tried restarting Jenkins?

Yeah restarted multiple times since it occured initially. When I sync the branches manually it works so I'll use that until I got more time to investigate further.

authors: mjdetullio t-stamm

repo: mjdetullio/multi-branch-project-plugin

license: MIT


text:
height: 'auto'  in  defaultAttributes for 'mj-image' breaks template draft

By default, there are defined defaultAttributes for mj-image tag that include:
static defaultAttributes = {
    align: 'center',
    border: '0',
    height: 'auto',
    padding: '10px 25px',
    target: '_blank',
    'font-size': '13px',
  }

Adding heigt="auto" by default breaks image display inside email drafts in the Apple Mail application. Images are not displayed at all or are not correctly scaled.
Possible solutions for this issue:

Don't add height="auto" by default to images (if it is not really necessary)
Allow skipping height="auto" by MJML (before compilation) without the need to define image height to a particular size.
Compile height to the tag style= without adding it as a separate height attribute.

Adding heigt="auto" by default breaks image display inside email drafts in the Apple Mail application.

I'm not sure what's the usecase here as sending HTML email via clients will alter the HTML and most likely break the email.
However you can add height="" to mj-image and reset it with mj-attributes if you want so. I'm not sure if the blank height attribute will do something bad tho.

Thanks for the quick answer @iRyusa .

I'm not sure what's the use case here as sending HTML emails via clients will alter the HTML and most likely break the email.

I know that sad phenomenon, however, I believe that the more such use cases can be captured and corrected from a code perspective, the scope for uncontrolled HTML changes between email clients can decrease. This particular case I reported is an important part of a project I'm working on, and I believe many developers will find the option to have more control over it helpful.
I have tested the blank height attribute and it still causes the same problem as with height="auto" .

I am wondering if that patch allow the Outlook pixel line bug to appear its' ugly head.  I post it over at - https://github.com/mjmlio/mjml/issues/2630

Don't think so.
But this has been release in 4.14.x

authors: TechBill iRyusa olgaplaga

repo: mjmlio/mjml


text:
parseTranslationUnit and parseTranslationUnit2 wrong signatures?

According to clang docs [here] (http://clang.llvm.org/doxygen/group__CINDEX__TRANSLATION__UNIT.html#ga494de0e725c5ae40cbdea5fa6081027d) the 5th parameter of parseTranslationUnit2, struct CXUnsavedFile*, is an in parameter (an array of struct) but ClangSharp has it as an out parameter.
And same for parseTranslationUnit.

The usage of the out parameter is to help marshal correctly. I could have also specified "ref" (which is really how the parameter is passed), but I chose not to because:
        int x;
        Foo(out x); // ok.

        int x;
        Foo(ref x); // compile error

Finally, the code is auto-generated, so special casing this instance would not be that great. The heuristic ClangSharp uses to make it an array of X versus making it an out X is if there is a const qualifier, which is present for the source_filename and command_line_args formal arguments to parseTranslationUnit but is missing for the unsaves_files parameter.
To unblock, I would do the following:
var x = new CXUnsavedFile[..];
parseTranslationUnit2(...., out x);
Furthermore, one of us should ask the Clang folks or submit a patch to make that parameter a const if it is indeed an "in" (which it looks like).

Ok.  I didn't know the marshalling would copy arguments both ways (in and
out) in the case of an out parameter.  Thanks!
On Sun, Mar 29, 2015 at 11:31 PM, Mukul Sabharwal notifications@github.com
wrote:

The usage of the out parameter is to help marshal correctly. I could have
also specified "ref" (which is really how the parameter is passed), but I
chose not to because:
    int x;
    Foo(out x); // ok.

    int x;
    Foo(ref x); // compile error

Finally, the code is auto-generated, so special casing this instance would
not be that great. The heuristic ClangSharp uses to make it an array of X
versus making it an out X is if there is a const qualifier, which is
present for the source_filename and command_line_args formal arguments to
parseTranslationUnit but is missing for the unsaves_files parameter.
To unblock, I would do the following:
var x = new CXUnsavedFile[..];
parseTranslationUnit2(...., out x);
Furthermore, one of us should ask the Clang folks or submit a patch to
make that parameter a const if it is indeed an "in" (which it looks like).
—
Reply to this email directly or view it on GitHub
https://github.com/mjsabby/ClangSharp/issues/2#issuecomment-87569852.

authors: david-bakin mjsabby

repo: mjsabby/ClangSharp

license: NCSA


text:
Whitelist LinkedIn

LI seems like a false positive
www.linkedin.com

That is a major false positive, thanks for reporting. This has highlighted an issue in the program used to generate the blocklist, as it is saying none of the included lists are blocking that domain, while the domain is still in the generated blocklist.

Turns out one of it's old cnames (2-01-2c3e-005a.cdx.cedexis.net) was blocked which resulted in www.linkedin.com being blocked. I've whitelisted www.linkedin.com


text:
Question? Where should I look in the source code to see all the splats?

I would like to play around with changing colors and removing splats from the Gaussian splat. Where would you recommend looking in the code for that?

SplatMesh.js is the file that contains the core of the rendering code, specifically in the vertex shader: https://github.com/mkkellogg/GaussianSplats3D/blob/77b4af26ef138aeb05323f64b0eb5410d562f3a7/src/SplatMesh.js#L136 as well as the fragment shader: https://github.com/mkkellogg/GaussianSplats3D/blob/77b4af26ef138aeb05323f64b0eb5410d562f3a7/src/SplatMesh.js#L341

I'll close this for now, but let me know if you need any more guidance with the code.

finally got the chance to look into this. Been playing around with the shaders to change the color.
Some things I'm looking for is where is the Root truth for a color? is it in one of the buffers and what is the structure of those?
And do you have any way you reccomend looking points that are around other splats? So if I raycast and get an index how possible would it be to get points around it? Would I need to implement kNN and just run it on all the points or does that already exist?

So for the "real" color of a splat, the source of truth is in the SplatBuffer object for a given splat scene. You can retrieve just color data from a splat buffer by calling the fillSplatColorArray() function.
For updating the color values, do you want to replace the whole texture or just update a sub-section of it? If you want to update/replace the whole texture, you need to do something like:
material.uniforms.centersColorsTexture.value = newtexture;
material.uniforms.centersColorsTexture.value.needsUpdate = true;

If you want to just update a sub-section of the texture, there are a couple ways to do it. You can use three.js' built-in method WebGLRenderer.copyTextureToTexture() (which I haven't personally used). Internally that function just calls the WebGL function texSubImage2D() to update a texture. I update the data textures in SplatMesh by calling texSubImage2D() directly in SplatMesh.updateDataTexture()

how would you recommend updating that data in splatBuffer? Im seeing in the code that there is lots more then color in the data. You get colors specifically by using fillSplatColorArray it seems. Would It be best to modify the splatBuffer, or update the textures that are stored in the mesh?
If i do update this.splatDataTextures.baseData.colors then do the actions to update the material, would that update the splats colors?

@mkkellogg what im looking at right now is fillSplatColorArray. Im trying to figure out how this creates the uint4array but it seems to be dependent on the to and from input info. How would you reccomend getting a uint8array of all the colors in the mesh?
additionally, it looks like just calling refreshGPUDataFromSplatBuffers will update the mesh too. Is this the best way or is there a faster method?

fillSplatColorArray() accepts as its first argument a parameter called outColorArray. That array should be an instance of Uint8Array, and it will get filled with color data from the SplatBuffer using the range values you specify (srcFrom & srcTo). destFrom is the start position in outColorArray to begin populating data.
Once the scene is completely loaded, this.splatDataTextures.baseData.colors will have all the color data extracted & uncompressed from the splat buffer. There is not currently a function that will just take that extracted color data and push it to the texture on the GPU, but you could totally write one :) It would be a lot like updateDataTextures(), except it wouldn't pull any data from the splat buffer. Actually updateDataTextures() should probably be renamed something like updateDataTexturesFromSplatBuffers() and it could call two new functions: one to extract & decompress the splat buffer data and another to push it to the GPU.

I got the function working for changing the color thanks. One thing to note, im not sure the updateDataTextures() works.
when I change the data using:
for all points...
this.material.uniforms.centersColorsTexture.value.source.data.data[colorDestBase] = rgbaArrayToInteger([r,g,b,a], 0);
this.material.uniforms.centersColorsTexture.value.needsUpdate = true;
then call mesh.udpateDataTextures()
the colors dont revert back to their original color. Is that expected behavior? I would assume since I changed the colors away from the splatBuffer it would have gone back to the original color

So you're right about updateDataTextures(), it works only during the progressive loading of a scene (I never intended it to be used after that). In theory, it should be able to be modified to work as I previously claimed it did. In many places you'll see references to this.lastBuildSplatCount and splatCount or splatCount - 1 as parameters to function calls within updateDataTextures() -- Those are just specifying a range of splats to do some update stuff with. When a scene is fully loaded, lastBuildSplatCount should be equal to splatCount so that's why you aren't seeing any effects. If you change those values (as appropriate) to be your desired range, that should make it work.

I should be able to do a pr. just wanna make sure its implemented well. One thing im working on now is implementing that tree search. Im using visitLeaves but that seems to only include a small portion of the nodes. Is there a better function?

this  was done using the SplatMesh.splatTree I assumed it would have been everything?

my bad. looks like the node has node.data.indexes... no need to answer

authors: lewibs mkkellogg


text:
Build against multiple Gradle versions #20

Check against 4.3-rc-3

I'm leaning towards putting this check into an additional - run: step rather than the current one.
What do you think?
Also, I think this is a satisfactory approach for now, but I left some comments in https://github.com/mkobit/assertj-gradle/issues/20#issuecomment-339122520 for issues that this approach will have and how we may want to approach this differently going forward.

I extracted a separate step. If the build against an other Gradle version fails, it may be helpful to easily see that the build still passes for the default Gradle version.

source: gharchive/pull-request

authors: mkobit pkubowicz

repo: mkobit/assertj-gradle


text:
How can I obtain the correct cam_param for the Neuman dataset?

Hi, thanks for sharing your excellent work!
When I  try to render the mesh of smplx for Neuman dataset, I found the pre-processed data you provided (in this link ) does not contain the cam_param.
So I try to use the virtual camera generation script (in this script) to generate the camera parameter for rendering. However, the rendering results is incorrect as shown bellow.

By the way, I have also try to render the mesh for the gyeongsik dataset provided in this link, which uses the virtual camera parameter generated by the above script. The rendered result is correct as shown bellow.

I seems that to render smplx mesh, the camera parameters for different dataset (NeuMan dataset and gyeongsik) are generated in different manner. Would you please tell me how to obtain the 'correct' camera parameters for NeuMan dataset?
Thanks a lot!

Hi,
Each dataset could have different camera parameter.
For the NeuMan dataset, you can check it from the dataloader like here and here.

Hi,
Each dataset could have different camera parameter. For the NeuMan dataset, you can check it from the dataloader like here and here.

After using the correct camera parameter, the rendered smplx seems normal.
However, the rendered result (from this script) still fails to meet the performance you provide under the folder 'renders'. The comparison of the rendered results are shown bellow, (upper: you provide in the pre-process data, lower: the rendered results generated by script )
Would you please tell what opration I am missing to obtain the well-aligned rendered results like you provided?
Thanks a lot.

Hi, the smoothing code assumes input SMPL-X parameters are from reasonable frame rates of a video. For example, 30 fps. However, NeuMan dataset is released after being downsampled to 5 fps, so it would be hard to apply any smoothing code. 5 fps is too sparse to apply some temporal smoothing stuff.

Get it! Without conducting the smoothing operation, the rendered results get correct. Thanks a lot!

Hi Gyeongsik @mks0601, a very quick question: have you re-run COLMAP on NeuMan dataset or just taken what the original dataset provides? Somehow I cannot render the SMPL-X to match the images using the cameras provided by NeuMan. Thanks!

I used the original camera parameters without re-running COLMAP. How do you load camera parameters?

I used the original camera parameters without re-running COLMAP. How do you load camera parameters?

Thanks for the prompt response! It's very good to know! I used the same way as you pointed out: https://github.com/mks0601/ExAvatar_RELEASE/blob/5ef87f4db2a91630cf8061ff43e63c7fc934b4a6/avatar/data/NeuMan/NeuMan.py#L34
I initially saw the mismatch and thought the COLMAP has been rerun. I will double check my visualization code.

sure. you can post minimally implemented your rendering code here if you want.

sure. you can post minimally implemented your rendering code here if you want.

Thanks for offering that! I just compared with your visualization code and it seems like all optimized SMPL-X parameters are in the camera space (rendering with identity matrix for Rt). I used the loaded Rt from COLMAP to render based on the optimized SMPLX- parameters and that's why there is a mismatch. Now I used an identity matrix for Rt and now it matches. Could you please correct me if I don't understand correctly?

You're correct. All optimized smplx parameters are in camera coordinate space. That's the reason why I convert the coordinates to the world coordinates when creating the avatar in here.


text:
gemma2

python -m mlx_lm.generate --model google/gemma-2-9b-it --prompt "Write a story about Einstein" --temp 0.0
Fetching 11 files: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████| 11/11 [00:00<00:00, 107797.53it/s]
==========
Prompt: <bos><start_of_turn>user
Write a story about Einstein<end_of_turn>
<start_of_turn>model

The year was 1921. A young woman named Greta, with eyes the color of a stormy sky and hair like spun moonlight, stood nervously outside the grand lecture hall in Berlin. She clutched a worn copy of "Relativity: The Special and the General Theory" in her hand, its pages dog-eared and underlined. Tonight, she would finally meet Albert Einstein, the man whose theories had captivated her imagination and ignited a passion for physics within her soul.

Greta had spent months
==========

CC @Blaizzy you can use this if you are planning to upload some models!

repo: ml-explore/mlx-examples


text:
Daftar Akun Pro Rusia Situs Slot Server Rusia Gacor Terpercaya No 1 Indonesia

Daftar Akun Pro Rusia Situs Slot Server Rusia Gacor Terpercaya No 1 Indonesia
SLOT RUSIA I >>> DAFTAR SEKARANG <<<
SLOT RUSIA II >>> DAFTAR SEKARANG <<<
Akun pro Rusia | slot Rusia | slot server Rusia | situs server Rusia | slot online Rusia | daftar slot server Rusia | slot gacor server Rusia | akun pro Rusia gacor | akun pro Rusia asli | situs akun pro Rusia | akun pro server Rusia
Akun Pro Rusia adalah salah satu alternatif dimana member mencari permainan slot online Rusia atau situs luar negeri lainnya, disini kamu dapat mengakses dengan mudah Server Slot Rusia. Beberpa situs yang menginduk di sini biasanya adalah situs dengan winrate kemenangan yang tinggi dengan RTP 88% Akurat, banyak juga yang bilang situs slot luar negeri lebih gacor di bandingkan server Rusia. Karena itulah kami menyediakan banyak opsi permainan slot online di server Rusia ini.
Kemenangan mudah adalah salah satu alasan mengapa para bettor mencari permainan slot luar negeri, hal tersebut bukanlah hal yang salah dan lumrah terjadi. Permainan slot online luar negeri cenderung lebih gacor dibandingkan situs Rusia, terlebih server yang di gunakan memanglah server terpercaya. Server Slot Rusia salah satunya, disini kamu bisa memainkan permainan slot online Rusia dengan bebas dan juga sudah di terjemahkan ke Bahasa Indonesia, keunggulan lain diantaranya adalah deposit menggunakan Bank yang ada di Indonesia, kamu sudah tidak lagi harus berpusing pusing melakukan deposit menggunakan visa card atau master card karena bank yang kamu gunakan sudah teregistrasi di server ini termasuk juga di dalamnya ada e-wallet.
Akun Pro Rusia Dengan Rtp Tertinggi
Saat ini Akun Pro Rusia memiliki RTp (Return To Player) paling tinggi di bandingkan dengan negara lain, karena RTP disini menggunakan rtp yang sudah sah dan sudah di validasi keakuratannya secara langsung. Kemudahan kemenangannya pun tidak memilih, kemenangan di bagikan secara merata dengan deposit kecil ataupun besar. Akun Pro Rusia adalah salah satu alternatif yang bisa kamu pakai untuk mengembalikan modal bermainmu. Sudah menjadi rahasia umum jika RTP di server luar negeri lebih valid di bandingkan dengan server Rusia, hal ini karena system yang di buat di server Rusia lebih mengutamakan data jangka panjang, sedangkan di server luar negeri menggunakan system jangka pendek yang bisa menilai seberapa gacor game tersebut dengan menghitung jumlah kemenangan valid orang orang yang bermain di dalamnya, kamu juga bisa memainkan permainan lainnya dengan RTP yang tinggi, ini memungkinkan kamu memenangkan permainan slot online lebih sering.
Tersedia Promo Dan Bonus Akun Rusia
Bonus yang di berikan sama persis seperti situs yang berada di indonesia, banyak yang mengira kalau bonus yang di berikan akan berbeda karena kemenangan dan kegacoran dari situs Rusia ini besar, nyatanya bonus yang di berikan sama persis hanya saja dengan server yang berbeda. Hal ini membuat Akun Pro Rusia sangat di gemari di kalangan para bettor sekarang ini karena kemenangan yang di dapat di sini terbilang sangat mudah di dapatkan dengan menggunakan dan memaksimalkan bonus yang di dapat.
Cara Bermain Situs Slot Server Rusia
Gunakan Rtp Yang Di Sediakan Paling Update
Situs Rusia biasanya menggunakan rtp yang akan update setiap beberapa jam, RTP ini sudah di bekali dengan pola slot gacor dan juga jam gacor yang bisa kamu lihat langsung.
Memahami Pola Game Slot Gacor
Memahami pola permainan sangatlah di wajibkan dan di anjurkan, karena dengan memahami permainan yang kamu mainkan kamu bisa mendapat banyak sekali kemenangan yang berlipat ganda, ketidak tahuan dalam permainan slot online adalah kekalahan pertama yang akan kamu rasakan
Menguasai Diri
Menguasai diri dan mengendalikan emosi saat bermain adalah salah satu hal penting yang bisa kamu lakukan untuk mendapatkan hasil yang lebih maksimal, mengontrol emosi dengan menganalisa permainan sangat di butuhkan di permainan slot online.
Daftar 5 Situs Judi Slot Terpercaya & Terbaik Di Server Rusia
Banyak game slot yang bermunculan hingga tahun 2022 ini. Oleh karena itu kami akan memberikan beberpa daftar provider online yang selalu diburu oleh banyak pemain di Indonesia. Berikut ini adalah provider slot terbaik yang bisa kamu mainkan di :

Slot Pragmatic Play

Salah satu provider yang kian di gemari oleh banyak orang adalah Pragmatic Play, provider ini sangat di gemari karena kemudahan permainan gamenya. Design interface yang mudah di pahami dengan mudah oleh para player menjadi salah satu keunggulan provider ini.

Slot Microgaming

Kemudian yang berikutnya ada provider microgaming yang bisa di mainkan oleh orang dewasa, ini membuat permainan slot online microgaming popular karena permainan ini memberikan banyak keuntungan jika kamu sudah memahami permainan ini dengan seksama, susunan yang mudah dan juga pola yang tidak terlalu rumit adalah salah satu keunggulannya.

Slot PG Soft

Provider ini adalah salah satu profider yang baru-baru ini popular karena grafik 3D yang memanjakan mata kamu, kemenangan yang di dapatkan dari profider ini sangatlah besar, tanpa adanya batas maksimal kemenangan kamu bisa menikmati permainan ini dan juga menjadikannya salah satu list profider favorit kamu untuk memenangkan permainan slot online dengan mudah.

Slot Habanero

Permainan slot yang sudah sangat mendarah daging di kalangan para bettor menjadi salah satu alasan kenapa provider Habanero menjadi salah satu profider favorit dan juga di gemari oleh para player slot lama dan juga baru.

Slot CQ9

Permainan slot online yang digemari oleh para bettor adalah salah satunya slot cq9 yang bisa kamu nikmati dan mainkan dengan modal kecil, permainan ini disukai karena kestabilan RTP di dalam game yang membuat para pemain bisa memaksimalkan kemenangan yanga da di dalam game tersebut.

I read through google translator but it looks like a spam. Closing

repo: mlc-ai/mlc-llm


text:
Change GroupRecordSet call to return the sample directly.

Croissant now output samples in the form: {"name": "person0", "age": 0}} (instead of: {"persons": {"name": "person0", "age": 0}}, as it was before)

Hi Pierre, I'm still having a look at why the data generation pipeline seems to be broken in my codespaces. But the CI Unittests seem to be green.

repo: mlcommons/croissant


text:
[HPC] More HPC fixes.

Creating verify_for_v1.0_hpc.sh.
Removing num_workers from rcps_deepcam.json since this hyper-parameter is being deprecated.

@xyhuang, you should merge this one.

authors: guschmue shangw-nvidia

repo: mlcommons/logging


text:
gw 5k-et setting DOD issue

Already starting the issue, still need to add additional information.
my 5k-et is reguralery spitting out this in the logs:
2022-02-25 10:03:17 DEBUG (MainThread) [goodwe.protocol] Sending: f703891c007d7ae7
2022-02-25 10:03:17 DEBUG (MainThread) [goodwe.modbus] Response has unexpected length: 2, expected 250.
2022-02-25 10:03:17 DEBUG (MainThread) [goodwe.protocol] Received invalid response: aa55f70302ffff71e1
2022-02-25 10:03:17 DEBUG (MainThread) [goodwe.protocol] Sending: f703891c007d7ae7 - retry #1/3
2022-02-25 10:03:17 DEBUG (MainThread) [goodwe.protocol] Received: aa55f703fa1602190a03110b0e0007000000c60eb80006000000e2000000000000000000000000000000000000020208cb000b13800000007608a8000d137e0000009c0908000c137e0000009d0001000001b00000f830000000000000000008cc0002137f00010000000608a70002137e00010000000009180003137e00010000000600000422000001c5000007150000000d000009730003014a000001294000198e0cc60a110000fffffffb00010000000600010000000000000000471b0000000400006511000017b2001f00001f9200000000d346005500003c9500000000383300190005000000010000000000000000000003000004000200000000afabaa55f703fa1602190a03110b0e0007000000c60eb80006000000e2000000000000000000000000000000000000020208cb000b13800000007608a8000d137e0000009c0908000c137e0000009d0001000001b00000f830000000000000000008cc0002137f00010000000608a70002137e00010000000009180003137e00010000000600000422000001c5000007150000000d000009730003014a000001294000198e0cc60a110000fffffffb00010000000600010000000000000000471b0000000400006511000017b2001f00001f9200000000d346005500003c9500000000383300190005000000010000000000000000000003000004000200000000afab
2022-02-25 10:03:17 DEBUG (MainThread) [goodwe.protocol] Sending: f70390880018fc7c
2022-02-25 10:03:18 DEBUG (MainThread) [goodwe.protocol] Received: aa55f7033000ff0137000100be002800280000000a0063000500000105000000000000000000000000000000000000000000000000e60c
2022-02-25 10:03:18 DEBUG (MainThread) [goodwe.protocol] Sending: f7038ca0002dbbf3
2022-02-25 10:03:19 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to f7038ca0002dbbf3 in time (1s).
2022-02-25 10:03:19 DEBUG (MainThread) [goodwe.protocol] Sending: f7038ca0002dbbf3 - retry #1/3
2022-02-25 10:03:19 DEBUG (MainThread) [goodwe.modbus] Response has unexpected length: 250, expected 90.
2022-02-25 10:03:19 DEBUG (MainThread) [goodwe.protocol] Received invalid response: aa55f703fa1602190a03130b260007000000c60ef90006000000e4000000000000000000000000000000000000020208cb000c137f0000007808a6000d1381000000990905000c137f000000a00001000001b30000f834000000000000000008d30002137f00010000000508a20002138200010000000109120003137f00010000000600000421000001c6000007180000000c000009730003014a000001294000198d0cc40a110000fffffffc00010000000600010000000000000000471b0000000400006511000017b2001f00001f9200000000d346005500003c95000000003833001900050000000100000000000000000000030000040002000000006595aa55f7035a00010021000a01110001fc4f025ff980f82e035afcc80361fc20fdc9137f49f03b5e4a287c0afffffc4f0000025ffffff980fffff82e00000203000000ee000000680000035afffffb83000002f1fffff972fffff20400010004cc68
2022-02-25 10:03:19 DEBUG (MainThread) [goodwe.protocol] Sending: f7038ca0002dbbf3 - retry #2/3
2022-02-25 10:03:20 DEBUG (MainThread) [goodwe.protocol] Received: aa55f7035a00010021000a01110001fc4c0260f984f830037dfcc8034afc1ffdcc137f49f03b5e4a287c0afffffc4c00000260fffff984fffff83000000200000001130000006a0000037dfffffb84000002c0fffff976fffff23a000100042c4f

I'm trying to set the DOD using node-red, sending a value to this field for the goodwe device
number.depth_of_discharge_on_grid

Already set log to debug, so I'm collecting all information, also the first time I noticed the above scrolling by, since I was in info mode before.
I'll add more info tonight (if you want me to test something specific, please ask, and I'll provide)

just adding more info switching from Eco to generic mode
2022-02-25 12:16:53 DEBUG (MainThread) [custom_components.goodwe] Finished fetching GoodWe data in 0.699 seconds (success: True)
2022-02-25 12:16:58 DEBUG (MainThread) [goodwe.protocol] Sending: f710b99b0004080000173b0014ff7fe368
2022-02-25 12:16:58 DEBUG (MainThread) [goodwe.protocol] Received: aa55f710b99b000481ef
2022-02-25 12:16:58 DEBUG (MainThread) [goodwe.protocol] Sending: f710b99f0004083000300000640000f36a
2022-02-25 12:16:58 DEBUG (MainThread) [goodwe.protocol] Received: aa55f710b99f0004c02e
2022-02-25 12:16:58 DEBUG (MainThread) [goodwe.protocol] Sending: f710b9a30004083000300000640000a33a
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Received: aa55f710b9a300040022
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Sending: f710b9a7000408300030000064000052f5
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Received: aa55f710b9a7000441e3
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Sending: f706b79800037b06
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Received: aa55f706b79800037b06
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Sending: f710b99700020400010000a8f9
2022-02-25 12:16:59 DEBUG (MainThread) [goodwe.protocol] Received: aa55f710b9970002c1ee
2022-02-25 12:17:11 DEBUG (MainThread) [goodwe.protocol] Sending: f706b79800003b07
2022-02-25 12:17:11 DEBUG (MainThread) [goodwe.modbus] Response is command failure: UNKNOWN.
2022-02-25 12:17:11 DEBUG (MainThread) [goodwe.protocol] Received exception response: aa55f703fa1602190c110b0ae2000b000001320f3400090000015e000000000000000000000000000000000000020208d7000813890000004608d4000a13880000005308e9000913890000004d0001000000e50000ffce000000000000000008dc0002138900010000000508d30002138800010000000008f900031389000100000007000003a6000002aa000000100000000d0000010a00030159000001424000198c0ca10a59ffeffffffe310003000000060001000000000000000047290000001200006515000017b5002300001fa0000e0000d35c006b00003cae00190000383300190005000000010000000000000000000003080812000201cf0000bf8faa55f703fa1602190c110b0ae2000b000001320f3400090000015e000000000000000000000000000000000000020208d7000813890000004608d4000a13880000005308e9000913890000004d0001000000e50000ffce000000000000000008dc0002138900010000000508d30002138800010000000008f900031389000100000007000003a6000002aa000000100000000d0000010a00030159000001424000198c0ca10a59ffeffffffe310003000000060001000000000000000047290000001200006515000017b5002300001fa0000e0000d35c006b00003cae00190000383300190005000000010000000000000000000003080812000201cf0000bf8faa55f706b79800003b07
  File "/config/custom_components/goodwe/select.py", line 89, in async_select_option
  File "/usr/local/lib/python3.9/site-packages/goodwe/et.py", line 334, in set_operation_mode
  File "/usr/local/lib/python3.9/site-packages/goodwe/et.py", line 311, in write_setting
  File "/usr/local/lib/python3.9/site-packages/goodwe/inverter.py", line 108, in _read_from_socket
  File "/usr/local/lib/python3.9/site-packages/goodwe/protocol.py", line 109, in execute
  File "/usr/local/lib/python3.9/site-packages/goodwe/protocol.py", line 48, in datagram_received
  File "/usr/local/lib/python3.9/site-packages/goodwe/protocol.py", line 208, in <lambda>
  File "/usr/local/lib/python3.9/site-packages/goodwe/modbus.py", line 116, in validate_modbus_response
goodwe.exceptions.RequestRejectedException: UNKNOWN
2022-02-25 12:17:13 DEBUG (MainThread) [goodwe.protocol] Sending: f703891c007d7ae7
2022-02-25 12:17:14 DEBUG (MainThread) [goodwe.protocol] Failed to receive response to f703891c007d7ae7 in time (1s).
2022-02-25 12:17:14 DEBUG (MainThread) [goodwe.protocol] Sending: f703891c007d7ae7 - retry #1/3

The issue has been found:
Setting the DOD to 90% can't be done in the current goodwe python code
        if 0 <= dod <= 89:

https://github.com/marcelblijleven/goodwe/blob/70eb0b05219d96aa6aa77ba666c28e59e7f448ba/goodwe/et.py#L358
If this was set to 90, I would agree, but 89 sucks bigtime, since my invertor was always running at 90% and I was trying to set this using HA

repo: mletenay/home-assistant-goodwe-inverter


text:
As a developer, when using a module loader failed tests are not being reported correctly.

Basically, I want them.
Since I use karma-webpack in order to roll my tests through my WebPack config, I urgently need to be able to see backtraces. Because of some preprocessors, lines have an offset, or I get to see the wrong file entirely! But the backtrace itself would solve many, many problems.
That files arent displayed correctly is a karma-webpack thing, fo' sho'. But having no idea where an error is coming from is problematic.
How can I get them?
Also... https://lh4.googleusercontent.com/-APYsZ_NfGTc/TsV4umugivI/AAAAAAAAFok/dgi1WC6Aw6c/w800-h800/687474703a2f2f692e696d6775722e636f6d2f6a61636f6a2e6a7067.jpg

Are you not getting any type of reporting at all? Can you post your karma.config.js please?
Unfortunately, I've never used a webpack before. karma-spec-reporter is a reporter, not a preprocessor. I'm not sure what relation the preprocessor has to the reporter, as they are supposed to be two completely different plugins, I'll have to do some digging.
Any type of information, examples, console output, or further explanations would help a lot! We might need to collaborate to help get this working, I completely understand the need for a solid stacktrace!

@IngwiePhoenix have you tried bumping the version that it used in karma-webpack to the latest release? It looks like they are a few versions behind. Let me know if that works!!

@IngwiePhoenix please verify that with the latest karma that you are still not seeing reporting, this was actually a recent defect that was just fixed: https://github.com/karma-runner/karma/issues/1894

Closing since no one else has verified that this is still an issue. I'll re-open if that's not the case.

repo: mlex/karma-spec-reporter

license: mit

license_source: bigquery


text:
Updated README.md

This pull request fixes a small typo in the README.md

Just a minor typo fix. @steffenmllr @SachaMPS please review

thanks! sorry it took me so long

authors: Marketionist steffenmllr

repo: mllrsohn/gulp-protractor


text:
Xslwriter extension not displayed

Hello,
With current online version https://mlocati.github.io/pecl-info/, we cannot displayed the xslwriter extension that is supposed to be available : see https://github.com/mlocati/docker-php-extension-installer#supported-php-extensions

Sorry to disturb you, its my fault. A typo error: extension is called xlswriter and not xslwriter. Got it now

repo: mlocati/pecl-info


text:
Adding "preview" Status.

Adding the "preview" status which is listed in the submission rules here: https://github.com/mlperf/policies/blob/master/submission_rules.adoc#73-results-categories

Submitting live during SWG.

repo: mlperf/logging


text:
DeepSpeech 2 isn't a benchmark

DeepSpeech 2 isn't in v0.5 or any version of MLPerf. Please update documentation to be consistent.

SWG Agrees to remove deepspeech 2 from our benchmark lists.
https://github.com/mlperf/training_policies/blob/master/training_rules.adoc

Deepspeech 2 is not currently in rules, so all good.

authors: TheKanter bitfort petermattson


text:
cannot work in windows 10?

Hi, i'm currently have difficulty to get the extension work at my system (Windows 10 1903).
   jupyter==1.0.0
   jupyter-client==5.3.1
   jupyter-console==6.0.0
   jupyter-core==4.5.0
   jupyterlab==1.1.2
   jupyterlab-server==1.0.6

    @ijmbarr/jupyterlab_spellchecker v0.1.5 enabled  ok
    @jupyter-widgets/jupyterlab-manager v1.0.2 enabled  ok
    @jupyterlab/commenting-extension v0.2.0 enabled  ok
    @jupyterlab/geojson-extension v1.0.0 enabled  ok
    @jupyterlab/shortcutui v0.4.0 enabled  ok
    @lckr/jupyterlab_variableinspector v0.3.0 enabled  ok
    @mflevine/jupyterlab_html v0.1.4 enabled  ok
    @pyviz/jupyterlab_pyviz v0.8.0 enabled  ok
    ipyevents v1.6.3 enabled  ok
    jupyter-gmaps v0.9.0 enabled  ok
    jupyter-leaflet v0.11.1 enabled  ok
    jupyter-threejs v2.1.1 enabled  ok
    jupyterlab-cpustatus v1.0.0 enabled  ok
    jupyterlab-dash v0.1.0-alpha.3 enabled  ok
    jupyterlab-datawidgets v6.2.0 enabled  ok
    jupyterlab-flake8 v0.3.1 enabled  ok
    jupyterlab-jupytext v1.0.2 enabled  ok
    jupyterlab-python-bytecode v0.7.0 enabled  ok
    jupyterlab-python-file v0.3.0 enabled  ok
    jupyterlab-spreadsheet v0.2.0 enabled  ok
    jupyterlab_bokeh v1.0.0 enabled  ok

when i see in the terminal, it pass up side down multiline command  as below.

Thanks before

the reason the command looks backwards is the plugin is piping the contents of your file/notebook into the linter
try 0.3.2 - i can't test on powershell so I apologize if this does not work.

authors: andibuwono mlshapiro


text:
Create, Read, Update, and Delete food menu for Admin

Menu Management
2.1 CRUD Foods

Objective: The feature allows Admin to create, read, update, and delete food items.

CRUD Foods Feature

Requirements
        User Story
        Acceptance Criteria
        Notes

Menu ManagementAs an Admin, I want to be able to manage the menu So that I can update, add, or remove items easily to keep it current and appealing to customers.

As an Admin, I should be able to log into the menu management system using my credentials securely.

Once logged in, I should see a dashboard or menu management section where I can view the current list of menu items.

I should have the option to add a new menu item, providing details such as name, description, price, category, and an optional image.

I should be able to edit existing menu items, allowing me to update information such as name, description, price, category, and image.

I should have the capability to remove menu items that are no longer available or have been discontinued.

When adding or editing items, I should be able to categorize them into sections such as appetizers, main courses, desserts, etc.

I should have the capability to view the list of restaurants using the menu items.

The menu management system should provide a user-friendly interface that is easy to navigate and use, even for someone without technical expertise.

Add comments

@haneeva @Naqibullah-sediqi Figma URL for Menu Management: https://www.figma.com/file/hjM0xWSadExn3CN0nOfqkv/Yummy?type=design&node-id=67-3&mode=design

authors: haneeva mmafrar

repo: mmafrar/yummy


text:
Setup repo

[ ] Update Gemspec and Gemfile 💎
[ ] Add Linux as a platform 🐧
[ ] Setup Build Action on Github  🛠
[ ] Add integration with CodeClimate ⛰ (I will provide the secret to setup)
[ ] Add badges 🏅
[ ] Make sure build passes and metrics work ✨

take it

@josephjoguts Без паники, это я разрешил. Сетап нужен поскорее, так что все ок. Брать issue вдвоем-втроем можно, это тоже я озвучивал.

repo: mmcs-ruby/qar


text:
redshift-data connection request

There are some use cases for this provider where for security reasons, you cannot have direct connectivity with the RedShift cluster, specially when there is an isolation between your ci/cd pipelines and your production redshift cluster.
How complex would be to implement a way to allow to choose between direct TCP/IP connection or via AWS redshift-data when you want to manage a Redshift cluster?
Thanks.

Hi Carlos, thank you for your issue. I do agree that in many protected environments it would be great to interact with the redshift using the native aws redshift-data cli.
However, the TCP/IP connection based *sql.DB Golang struct type is deeply integrated into the provider (see https://github.com/mmichaelb/terraform-provider-redshift/blob/main/redshift/config.go#L42). Therefore, in my opinion this addition would be an enormous refactoring and would require heavy work. At the moment, sadly, I do not have the time to implement this feature.
I am leaving this issue open so that someone (or a future me) can start such implementation. Feel free to share your thoughts :)

authors: carlosperello mmichaelb

repo: mmichaelb/terraform-provider-redshift


text:
Make comment section collapsible and different font/style than main content

[x] This is a feature request.
Environment informations

Minimal Mistakes version: I don't know how to tell, here is my Github
github-pages:

Expected behavior
Thanks for making this awesome theme available. Traffic to my blog is picking up, as well as comments. Currently, the comments are displayed in the same font and style as the main content, which IMHO, is a little distracting, and also ends up taking up some space at the bottom (case in point, http://blog.abhijitsarkar.org/technical/netflix-eureka/).
Thus, I'm making a couple of feature requests:

Collapse the comment section until someone expands it.
Use a different font, preferably smaller than the content, and style, for the comments.

The styling you can easily take care of by adding some custom CSS to the main stylesheet. The entire comment's section has the class .page__comments so you could very easily change the font (or other styling) for just that section.
The same could be said for making it collapsible that expands by adding custom JS to _includes/scripts.html.
I'd rather not bake either into the theme as they're the sort of thing some people will want and others won't. I've tried to make the theme easily customizable to allow you to tailor it as you see fit.

@mmistakes Sorry about the delayed response. I agree with what you said, but the problem is that not everyone has your skills. What if there's an features or extras folder,  where people, including you, can contribute features that can be optionally added? Then front end dummies like me can simply copy-paste the features they want, and those who don't, can ignore the folder.

authors: asarkar mmistakes

repo: mmistakes/minimal-mistakes


text:
Update Haml-Lint dependency

We have made some large changes to the haml_lint gem that caused some
incompatibilities in pronto-haml. In order to deal with these issues,
I updated to the version recommendation for haml_lint to a newer
version and updated the wrapper to use the new structure.
Closes brigade/haml-lint#197

Hmm ... the tests are failing on Travis. That's odd. I'll look into it.
Also, we require Ruby 2.1+ for modern Haml-Lint. That's why Ruby 2.0 is failing.

The build is now passing. I removed Ruby 2.0 from the Travis configuration in a separate commit. Hopefully, that's acceptable given that haml-lint requires Ruby 2.1+.
Please let me know if there's anything else you need for this!

@michaelherold thanks, that's perfect! 🙇

Released as v0.8.1.

authors: michaelherold mmozuras

repo: mmozuras/pronto-haml


text:
Improve I/O with EEGLAB

I have to work a bit with EEGLAB, and I'm not very familiar with it (yet) but I already noticed a couple of improvements that could be made to the I/O in my opinion.
Reader
Channel type is hard-coded to 'eeg' here while EEGLAB seems to support a larger variety of channel types.
From the documentation:

‘EEG’, ‘MEG’, ‘EMG’, ‘ECG’, ‘Events’, etc.

Proposition: Try to retrieve the channel types saved by EEGLAB and convert it to one of MNE channel types (e.g. 'EEG' -> 'eeg', 'Events' -> 'stim').
Writer / Export
Looking at export_set in eeglabio, it has an argument ref_channels that is not used by the export code. If I'm not mistaken, the referencing information is present in Info, so it could be passed to the .set file via this argument.
eeglabio.raw.export_set(
        fname, data=raw.get_data(picks=ch_names), sfreq=raw.info['sfreq'],
        ch_names=ch_names, ch_locs=cart_coords, annotations=annotations)

Support for channel type is not included in eeglabio, I would like to add it https://github.com/jackz314/eeglabio/pull/4
Once added to eeglabio, the exporter could make use of this additional argument.

TODO:

[x] Add support for MNE channel types in the reader (#9990)
[ ] Add a warning when exporting with unapplied projectors + warning in documentation ()
[ ] Add support to export MNE channel types (depends on jackz314/eeglabio#4)

Sounds good! However, MNE does not keep track of the reference channel so unfortunately this won't work automatically.

@cbrnr Arf! Too bad for that, but to be honest my main priority is the channel types :)
Now that I think about it, what about projectors that are not yet applied? I think, for now, the export is not applying them.. maybe we could add a proj argument also to add the possibility to apply them prior to export.
If so, we could also check for the presence of a common average reference projector, in which case we could set ref_channels='average' during the export. If MNE is not keeping track of the reference channel(s), then I think this is the only case in which ref_channels can be define.

True, but I'd rather leave it to the user to define what they want to export. That way, we don't have to add another parameter (which as you correctly say only works for that single case).

But projectors may contain other types of projectors that the user may want to set. I think the method .apply_proj() is not very well known because of the argument proj present in many MNE functions. At the very least, I think the export should not silently get rid of the projectors without any warning for the user in the docstring / notes section.

EEGLAB is mostly used for EEG analysis, and setting an average reference in MNE does not use a projector by default. The other popular projector in MNE is SSP, which is used in MEG analysis. I think if someone uses one of these two projectors in EEG analysis (or some other custom projector), they probably know what they are doing and should be able to apply_proj() before exporting. But yes, feel free to mention this explicitly in the docs (and also issue a warning if there are unapplied projectors).

Sounds good! However, MNE does not keep track of the reference channel so
unfortunately this won't work automatically.

what do you mean?

I think he meant that if you reference to a specific channel, e.g. CPz, this information is lost and all you know is that a custom reference has been applied, but not which one.

@cbnr what was the reason for this? we have no fif constant tag to store
this?
note that the info['chs'][0]['loc'][3:6] should contain the location of the
reference for EEG channel of index 0
but this is still  not done properly. I was not aware of this FIF
requirement when this was written years ago...

what was the reason for this? we have no fif constant tag to store this?

Yes. And my opinion is still that we should move beyond FIFF when it is holding us back. EEG data is not stored in FIFF very often, and I believe other formats such as EDF or BrainVision do support storing the reference name.

@cbrnr @agramfort Related to this, mne.io.proj._needs_eeg_average_ref_proj is not doing what it's supposed to.
# ANT Neuro dataset referenced to 'CPz' by the amplifier
raw= mne.io.read_raw_fif(fname,  preload=True)

_needs_eeg_average_ref_proj(raw.info)
Out: True

raw.set_eeg_reference(ref_channels=['M1', 'M2'])
_needs_eeg_average_ref_proj(raw.info)
Out: False

@agramfort @cbrnr

what was the reason for this? we have no fif constant tag to store this?

Yes. And my opinion is still that we should move beyond FIFF when it is holding us back.

We discussed this before, and yes, I too believe this is a massive lack we need to resolve for EEG users.
Here's the discussion thread, in which we discussed some concrete ideas how to best address this:
https://github.com/mne-tools/mne-python/issues/8962

I would phrase it as "we should extend the FIF spec when it's holding us back." So far the times we've done it I think it has forced us to really think about and distill what's necessary about the new information. Without this constraint (e.g., if we adopted a looser approach for example based on HDF5) I imagine things would have been messier long term.

... and I think #8962 is good example actually, even though we haven't settled on a solution there

... and I think #8962 is good example actually, even though we haven't settled on a solution there

I'd like to second that

can we discuss this tomorrow during the MNE office hours?

authors: agramfort cbrnr hoechenberger larsoner mscheltienne

repo: mne-tools/mne-python


text:
[DOC, MRG] Small fixes

Fixes leftovers from https://github.com/mne-tools/mne-python/pull/10373

What should I have skipped for just doc? Is it [skip ci]? I think that still runs the make docstring test right?

Okay, thanks!

Looks good to go


text:
Fixes clone method to return new Color instead of alpha

The clone method was returning the value from the alpha() method. it should return the new Color instead. the Color.ts seems to do this correctly already.
And many thanks for this :) it's a handy utility for managing colors!

Thank you!

authors: adamwulf moagrius

repo: moagrius/Color


text:
Prevent several Videos from playing at the same time on the same page.

See https://community.afterglowplayer.com/discussion/2/what-do-you-need-in-your-everyday-life#Comment_31

Will be fixed in v0.3.

repo: moay/afterglow


text:
add send_typing

add send_typing method
update evilbot

work on auxin? groups?

works on groups, doing this with auxin would require the simulate dance, which i'm hoping will be simpler soon

i tried adding a version for auxin, but i don't know why it doesn't work. can be tested with evilbot

authors: itdaniher technillogue

repo: mobilecoinofficial/forest


text:
Extend Memo.getPlainValue method

Now Memo.getPlainValue method plays well with text memos, which value is an array of integers.
But more important here is that I moved stellar-base classes type definitions inside our repo to adjust it more rapidly because it's incomplete. I'll create PR to DefinitelyTyped too

Well, somehow I opened the Pandora box of type checking with this PR, I don't know how it worked on Friday. He-he, classic

repo: mobius-network/astrograph


text:
Fixed auto location of vpnkit socket

Fixes https://github.com/moby/hyperkit/issues/253

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:yinzara/hyperkit.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

This PR maintains legacy behavior if the older versions of Docker for Mac are installed but supports the new location if the file exists.

authors: GordonTheTurtle yinzara

repo: moby/hyperkit


text:
🚀 Feature: Add pseudo-tests for timing of before()/after() hooks

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label

Related issues/proposals:
#419
#700
cybertk/abao#203
Description
Breakdown of test timing should add setup/teardown pseudo-tests to help give better individual test timings. Timing of before() functions would be added to the "setup" pseudo-test, and after() functions to the "teardown" pseudo-test of each describe().
Timing of beforeEach()/afterEach() would remain with each it().
Reporters would display these as two additional tests named "setup" and "teardown", assuming they exceeded some threshold.
Rationale
When using Mocha tests to perform RESTful interface testing against a resource, timing of a database setup routine in a before() would be added to the first test -- making its performance look terrible. When running API tests, the timing of the routine can be almost as important as it passing.

I think it will be better to provide a way to access the timing API or a "pseudo it" that will record the timing. Currently, I have a test file like this:
describe("test cases", () => {
  for (const case of cases) {
    it(case.name, () => {
      const input = fs.readFileSync(case.inputFile);
      const output = doSomething(input);
      const expectedOutput = fs.readFileSync(case.outputFile);
      assert.equal(output, expectedOutput);
    });
  }
});

The problem is that setup, assert, and teardown phases are all counted in the timing. What I really care is the calculation time i.e. doSomething(input). Currently, I can use a workaround like:
describe("test cases", () => {
  for (const case of cases) {
    describe(case.name, () => {
      let input, expectedOutput;
      before(() => {
        input = fs.readFileSync(case.inputFile);
        expectedOutput = fs.readFileSync(case.outputFile);
      });
      it("run", () => {
        const output = doSomething(input);
        assert.equal(output, expectedOutput);
      });
    });
  }
});

With a timing API, we can simplify this to:
describe("test cases", () => {
  for (const case of cases) {
    it(case.name, function () {
      const input = fs.readFileSync(case.inputFile);
      const expectedOutput = fs.readFileSync(case.outputFile);

      this.timeStart();
      const output = doSomething(input);
      this.timeEnd();

      assert.equal(output, expectedOutput);
    });
  }
});

Or, with a "pseudo it":
describe("test cases", () => {
  for (const case of cases) {
    it(case.name, function () {
      const input = fs.readFileSync(case.inputFile);
      const expectedOutput = fs.readFileSync(case.outputFile);
      let output;

      timeMe(() => {
        output = doSomething(input);
      });

      assert.equal(output, expectedOutput);
    });
  }
});

The API should accept an optional label in case that the user want to record multiple time-span e.g. setup time:
this.timeStart("setup");
// ...
this.timeEnd("setup");
this.timeStart();
// ...
this.timeEnd();

// or

timeMe("setup", () => {...});
timeMe(() => {...});

The concept was to add the timing information for each test to the stats object automatically; there is no API.

This issue has had exactly two people interact with it since it was filed in 2019. That's less than one every two years. Per #5027, we're trying to stay away from changes that don't have broad appeal. Closing as wontfix.
But, if anybody thinks I'm wrong here, please do file a new issue with one of our new issue templates. They'll prompt for the supporting info that would help us triage this higher.
Cheers, all!

authors: JoshuaKGoldberg eight04 plroebuck

repo: mochajs/mocha


text:
upgrade deps; closes #3018 (WIP--DO NOT MERGE)

upgrades: production

[x] commander
[x] debug
[ ] diff
[x] glob
[x] supports-color
[x] browserify (affects production)

upgrades: development

[x] karma-phantomjs-launcher
[x] karma
[x] karma-sauce-launcher

modules added

[x] buffer

modules removed

[x] lodash.create
[x] phantomjs (installed via karma-phantomjs-launcher instead)
[x] readable-stream
[x] json3 (this was for IE7/8's crap implementation)

The story on buffer is that browserify@14.4.0 ships with buffer@5 which is incompatible with IE10 and older.  So we have to explicitly depend on buffer@4 and tell browserify to use it.

Changes Unknown when pulling 62aefdc2d2c5640928812ae5486c6958fa806614 on issue/3018 into ** on master**.

Changes Unknown when pulling 3bd12d864447ed4495d031dc60b5da2e214b4311 on issue/3018 into ** on master**.

Coverage increased (+0.02%) to 89.047% when pulling 1c2543ea39b5ac8a2b09eaa24b9176de1c3e8bd1 on issue/3018 into 0ed529747aff4fcd95cc226217e38c47d5c6caf9 on master.

Coverage increased (+0.1%) to 89.154% when pulling 7862a9ba017504278a8adff269873f5700fc161d on issue/3018 into 0ed529747aff4fcd95cc226217e38c47d5c6caf9 on master.

Coverage increased (+0.2%) to 89.193% when pulling 00b111690fe0ea1ef76f63856b2da4708a087e2e on issue/3018 into 0ed529747aff4fcd95cc226217e38c47d5c6caf9 on master.

Coverage increased (+0.2%) to 89.193% when pulling 3833a74d3a001548bbc5ff5fc45a5ce147e0c386 on issue/3018 into 0ed529747aff4fcd95cc226217e38c47d5c6caf9 on master.

Coverage increased (+0.2%) to 89.193% when pulling 3287c7f260190b167872dc759a0106bd46eedc18 on issue/3018 into 0ed529747aff4fcd95cc226217e38c47d5c6caf9 on master.

Coverage decreased (-0.004%) to 89.174% when pulling f1baaad742c7e276a29cb0051a21881bb38bc3f7 on issue/3018 into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

Coverage decreased (-0.004%) to 89.174% when pulling 05118d07b7346f6dd53f5b3e1adb253689c97783 on issue/3018 into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

Coverage decreased (-0.004%) to 89.174% when pulling d4b1289c0daf113614ef7e5a7873e2e687f8c253 on issue/3018 into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

Coverage decreased (-0.004%) to 89.174% when pulling d4b1289c0daf113614ef7e5a7873e2e687f8c253 on issue/3018 into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

Coverage increased (+0.1%) to 89.3% when pulling 9f7d4bd2f0c1a84c3f46b7b8d48303f5392ab1b9 on issue/3018 into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

okay, I'm going to merge this.  maybe a bit of rebasing but I'll try to keep things separated.

Coverage increased (+0.1%) to 89.3% when pulling 4554ceb00959772cca15a70608b479bc713ce1d5 on issue/3018 into 228dc4758dfebf0430b9295c6b75221c3390aee4 on master.

authors: boneskull coveralls


text:
uncaughtException: fix ignoring them when test has already failed or is pending

Description
describe('test', () => {
  it('test1', () => {
    setTimeout(() => {
      throw new Error('Uncaught');
    }, 3);
  });
  it('test2', function () { this.skip(); });
  it('test3', function () { this.skip(); });
  it('test4', function () { this.skip(); });
});

output with exitCode: 0
test suite
    √ test1
    - test2
    - test3
    - test4

  1 passing (34ms)
  3 pending

Description of the Change

Runner#uncaught: an uncaughtException should never be ignored, even worse when Mocha exits with an exitCode: 0

label current test as failing, even if it already has failed.
label current test as failing, even if it is pending.

Runner#uncaught: per default Mocha tries to map uncaughtExceptions to the correct test cases and keep the runner working. This is done on a "best effort" basis. With the --allow-uncaught option the user has the choice to throw an error and explicitly exit Mocha's process.

Applicable issues
closes #3938

Coverage decreased (-0.01%) to 92.695% when pulling b72c5af39032ff44bc9ff9c2df9f86d77cc322e0 on juergba/uncaught-swallow into f73e7c681699a72a1b6b4d8db5c3af9ceccce66f on master.

authors: coveralls juergba


text:
Revert "Revert "Custom protoc plugin to generate a grpclib wrapper""

Reverts modal-labs/modal-client#2189

Backend adjustments ready to go live now to not break type safety there after this thanks to @TheQuantumFractal

@prbot approve

Seems fine to me.

authors: TheQuantumFractal freider

repo: modal-labs/modal-client


text:
Reduce implementation inheritance

I have a mild aversion towards implementation inheritance so let's try to avoid it

needs a bit more work, not worth it


text:
Check == and <> usages in functions

Reported by otter on 19 Feb 2016 13:31 UTC
In https://trac.modelica.org/Modelica/ticket/1867#comment:41 the following was reported:
The LMS Amesim compiler found several "warnings" related to equality comparison of Real variables. For example, there are lines like if (d_vap <> d_liq) or if abs(m) <= tol or fb == 0.0 . I suspect most other tools just ignore the warnings, like we do. However, it might be nice to clean up as many of them as we can before the v3.2.2 release. This is most likely just a partial list…
Functions that use == comparisons on Real variables:
Modelica.Media.Water.IF97_Utilities.BaseIF97.Basic.f3
Modelica.Media.Common.OneNonLinearEquation.solve

Functions that use <> comparisons on Real variables:
Modelica.Media.Water.IF97_Utilities.waterBaseProp_ph
Modelica.Media.Water.IF97_Utilities.waterBaseProp_ps
Modelica.Media.Water.IF97_Utilities.waterBaseProp_pT
Modelica.Media.Water.IF97_Utilities.BaseIF97.Isentropic.hofps4
Modelica.Media.Water.IF97_Utilities.BaseIF97.TwoPhase.waterSat_ph
Modelica.Media.Water.IF97_Utilities.BaseIF97.TwoPhase.waterR4_ph
Modelica.Media.Water.IF97_Utilities.BaseIF97.TwoPhase.waterR4_dT

Although == and <> are allowed in Modelica functions, there might be issues and the functions should be inspected.
I have analyzed the first two (Hubertus, please have a look at the other ones):
Modelica.Media.Common.OneNonLinearEquation.solve
Here the following code is present
 if abs(m) <= tol or fb == 0.0 then
    // root found (interval is small enough)

This code fragment checks whether the interval of the independent variable (abs(m) <= tol) is small enough or whether the residue is exactly zero. If this is the case, the root was found. The "fb == 0.0" is correct here: We cannot use an eps, abs(fb) <= eps, because the "size" of fb is not known (could be very large or very small). However, if the residue is exactly zero, it is impossible to further reduce the x-interval. Therefore, this check must be present.
Modelica.Media.Water.IF97_Utilities.BaseIF97.Basic.f3
Here the following code fragement is present:
f.delta := if (d == data.DCRIT and T == data.TCRIT) then
                1 - Modelica.Constants.eps
           else abs(d/data.DCRIT);

Looks a bit surprising to me and it might be better to have an eps here, such as (but I am unsure):
f.delta := if ( abs(d-data.DCRIT)<=eps and
                abs(T-data.TCRIT)<=eps then
                1 - Modelica.Constants.eps
...

Migrated-From: https://trac.modelica.org/Modelica/ticket/1915

Comment by hansolsson on 19 Feb 2016 14:01 UTC
Just so that the previous comment isn't lost:
https://trac.modelica.org/Modelica/ticket/1867#comment:44
It is formally correct Modelica to use equality tests - but it might indicate a problem, and might cause problems for e.g. automatic differentiation.
Consider f3:
  f.delta := if (d == data.DCRIT and T == data.TCRIT) then 1 - Modelica.Constants.eps
     else abs(d/data.DCRIT);

Around the critical density f.delta goes from -1/data.DCRIT to 1/data.DCRIT.
IF we want f.delta to be continuously differentiable we will have to create a complicated expression. I don't know if it is worth it, and I don't see the point in any other change. (I don't even know if we want to differentiate this function in some cases.)

Comment by hansolsson on 19 Feb 2016 15:30 UTC
Replying to [comment:1 hansolsson]:

Just so that the previous comment isn't lost:
https://trac.modelica.org/Modelica/ticket/1867#comment:44
It is formally correct Modelica to use equality tests - but it might indicate a problem, and might cause problems for e.g. automatic differentiation.
Consider f3:
  f.delta := if (d == data.DCRIT and T == data.TCRIT) then 1 - Modelica.Constants.eps
     else abs(d/data.DCRIT);

Around the critical density f.delta goes from -1/data.DCRIT to 1/data.DCRIT.

Oh, sorry - this is wrong.
The f.delta derivative is 1/data.DCRIT both before and after the critical point.
I thought the code was more complicated.
That makes it easier to support automatic differentiation (assuming DCRIT is positive!):
   f.delta := if (d == data.DCRIT and T == data.TCRIT) then 1 - Modelica.Constants.eps
      + (d/DCRIT-1) else abs(d/data.DCRIT);

But that also makes me wonder what problem would f.delta=1 at the critical point cause?

Comment by hubertus on 19 Feb 2016 22:17 UTC
There are derivatives that jump from +1/x to -1/x when crossing the critical point (cp does that). This is a type of function where I would really not recommend to use AD to compute derivatives. In no symbolic math engine that I ever used (Mathematica, Maple, and an open source one) this ever worked properly without my massaging the code manually before and after taking derivatives. That aside, it is worthwhile checking that the current code is fully numerically robust. But it has been used for around 15 years now without me ever getting a bug report on this, so I would strongly prefer to see a failure-example before I change anything.

repo: modelica/Modelica


text:
Remove protected element from record

The record kc_flatTube_IN_con contained the protected element
        type TYP =
            Modelica.Fluid.Dissipation.Utilities.Types.HTXGeometry_flatTubes;

This is illegal according to Modelica specification section 4.6. as records can only contain public sections. As TYP is never used in the record simply delete it.

For me it looks rather odd that this bug is not present in FluidDissipation >= v1.1.7 which means, the two repositories (Modelica.Fluid.Dissipation and FluidDissipation) are already out of synchronized maintenance.
Since we do not have a modularized MSL it would be good to know if it is intended that bug fixes on FluidDissipation are ported to Modelica.Fluid.Dissipation and vice versa. @wischhusen Can yo please comment on the maintenance strategy. Thanks a lot!

authors: beutlich miscco


text:
build: use husky to execute Prettier on pre-commit

The hook https://github.com/pre-commit/mirrors-prettier is archived because it will not support newer versions of Prettier.
The new setup:

reduces the duplication of versions and configuration files
lints more files automatically

I also plan to use Husky to run ESLint.
This would solve the issues currently blocking the upgrade in https://github.com/modelix/modelix.core/pull/1003.
To be verified by reviewers

[ ] Relevant public API members have been documented
[ ] Documentation related to this PR is complete

[ ] Boundary conditions are documented
[ ] Exceptions are documented
[ ] Nullability is documented if used

[ ] Touched existing code has been extended with documentation if missing
[ ] Code is readable
[ ] New features and fixed bugs are covered by tests

Husky interferes with https://pre-commit.com


text:
build: check binary compatibility of Kotlin JVM APIs

It's not always obvious if a change in the Kotlin code is a breaking change of the JVM API. Sometimes annotations such as @JvmOverloads are required to maintain binary compatibility.
Some changes are not breaking changes in the sense that they don't require changes in Kotlin code that uses the API, but if the JVM API is incompatible it can cause LinkageErrors at runtime, if the Kotlin code wasn't re-compiled against the new version.
See https://github.com/Kotlin/binary-compatibility-validator for details.

As discussed in a meeting today: Failing the build contradicts ADR 0007. If we want to stick to that decision, we should only treat those JVM API incompatibilities as hints, for instance, by putting them in a PR comment.

It's probably annoying to run gradle dumpApi all the time and it solves a problem that we currently don't really have and will ignore for now..

authors: languitar slisson


text:
您好，在尝试streamlit时，会出现"已杀死"问题

我在streamlit中尝试stable_diffusion获得了效果

但是当我使用HunyuanDiT，程序崩溃，如下图所示，请问可能是为什么？

已解决，多次尝试就好了

但是目前我生成的图片似乎和我绘制的没有太大关系，是如何设置哪里吗

还是有“被杀死”的情况

请问可以提供详细的报错信息吗？

内存不足？

请问可以提供详细的报错信息吗？

没有详细的报错信息，就如上图的“以杀死”这个错误信息

内存不足？

不太清楚，因为没有详细的报错信息，但是我使用nvidia-smi -l 1命令监视显卡使用情况，运行时占用50%左右，没有用完

安装nvitop，可以实时监控显卡，并且有内存占用百分比

内存不足？

不太清楚，因为没有详细的报错信息，但是我使用nvidia-smi -l 1命令监视显卡使用情况，运行时占用50%左右，没有用完

安装nvitop，可以实时监控显卡，并且有内存占用百分比

谢谢，确实是RAM爆了，我的是32GB的RAM

authors: Artiprocher JoshonSmith thgpddl

repo: modelscope/DiffSynth-Studio


text:
Add UI for easily creating new links from a JID or URI

This makes it easy for people to create a shareable link by entering a JID or URI, and avoids them having to manually construct URLs and deal with escaping. The resulting URL can be visited directly, or copied to the clipboard with a button.
To simplify the code, it also changes how translation is applied (it now uses data attributes on elements).
TODO: There are some new strings that need translating.
(this PR is based on a local feature branch, and replaces the original PR at #61)

I've now added a fallback to the English translation where strings are not translated. That should unblock merging this until we can find translators.

repo: modernxmpp/easy-xmpp-invitation


text:
Add support for registering a custom accessor to allow user to extend DataFrames/Series

pandas supports adding custom methods directly onto a DataFrame/Series. pandas docs
This pandas feature allows users to extend a pandas DataFrame/Series, and add their own functionality.

Two examples of libraries that use this are geopands and woodwork

It would be cool to also have the ability to register custom accessor in a modin DataFrame/Series

import modin.pandas as pd

@pd.api.extensions.register_dataframe_accessor("geo")
class GeoAccessor:
    def __init__(self, pandas_obj):
        self._validate(pandas_obj)
        self._obj = pandas_obj

    @staticmethod
    def _validate(obj):
        # verify there is a column latitude and a column longitude
        if "latitude" not in obj.columns or "longitude" not in obj.columns:
            raise AttributeError("Must have 'latitude' and 'longitude'.")

    @property
    def center(self):
        # return the geographic center point of this DataFrame
        lat = self._obj.latitude
        lon = self._obj.longitude
        return (float(lon.mean()), float(lat.mean()))

    def plot(self):
        # plot this array's data on a map, e.g., using Cartopy
        pass

In [1]: ds = pd.DataFrame({"longitude": np.linspace(0, 10),
   ...:                    "latitude": np.linspace(0, 20)})
In [2]: ds.geo.center
Out[2]: (5.0, 10.0)
In [3]: ds.geo.plot()  # plots data on a map

Duplicate of #3948

It looks like we need to add support for pd.api.extensions.register_dataframe_accessor.register_dataframe_accessor.

authors: RehanSD anmyachev gsheni

repo: modin-project/modin