text:
SSR (for Next static HTML export) with hooks

In my project I have the following in place which forces me to not use Query, and instead in to a combination of ApolloConsumer + hooks in my components, which seems to not allow for fully rendered static HTML exports from next.
Why? Because I have two GraphQL data sources and need to be able to specify the client in the component, and Query doesn't take this parameter.
What follows is my code from the following files, in this order:

init-apollo.js
with-apollo-client.js
_app.js
Post.js

init-apollo.js

import getConfig from "next/config";
import ApolloClient from "apollo-boost";
import { InMemoryCache } from "apollo-cache-inmemory";
import { IntrospectionFragmentMatcher } from "apollo-cache-inmemory";
import { endpoint } from "../config";
import introspectionQueryResultData from "../fragmentTypes.json";

import fetch from "isomorphic-unfetch";

let apolloClient = null;

// Polyfill fetch() on the server (used by apollo-client)
if (!process.browser) {
  global.fetch = fetch;
}

const { serverRuntimeConfig, publicRuntimeConfig } = getConfig();
const fragmentMatcher = new IntrospectionFragmentMatcher({
  introspectionQueryResultData
});

const { WP_TOKEN } = publicRuntimeConfig;
function create(initialState) {
  const authHeaders = {
    authorization: WP_TOKEN ? `Bearer ${WP_TOKEN}` : ""
  };

  const wpClient = new ApolloClient({
    uri: process.env.NODE_ENV === "development" ? endpoint : endpoint,
    cache: new InMemoryCache({ fragmentMatcher }).restore(initialState || {}),
    request: operation => {
      operation.setContext({
        // fetchOptions: {
        //   credentials: "include"
        // },
        authHeaders
      });
    }
  });
  return wpClient;
}

export default function initApollo(initialState) {
  // Make sure to create a new client for every server-side request so that data
  // isn't shared between connections (which would be bad)
  if (!process.browser) {
    return create(initialState);
  }

  // Reuse client on the client-side
  if (!apolloClient) {
    apolloClient = create(initialState);
  }

  return apolloClient;
}

with-apollo-client.js

import React from "react";
import initApollo from "./init-apollo";
import Head from "next/head";
import { getDataFromTree } from "react-apollo";

export default App => {
  return class Apollo extends React.Component {
    static displayName = "withApollo(App)";
    static async getInitialProps(ctx) {
      const { Component, router } = ctx;

      let appProps = {};
      if (App.getInitialProps) {
        appProps = await App.getInitialProps(ctx);
      }

      // Run all GraphQL queries in the component tree
      // and extract the resulting data
      const apollo = initApollo();
      if (!process.browser) {
        try {
          // Run all GraphQL queries
          await getDataFromTree(
            <App
              {...appProps}
              Component={Component}
              router={router}
              apolloClient={apollo}
            />
          );
        } catch (error) {
          // Prevent Apollo Client GraphQL errors from crashing SSR.
          // Handle them in components via the data.error prop:
          // https://www.apollographql.com/docs/react/api/react-apollo.html#graphql-query-data-error
          console.error("Error while running `getDataFromTree`", error);
        }

        // getDataFromTree does not call componentWillUnmount
        // head side effect therefore need to be cleared manually
        Head.rewind();
      }

      // Extract query data from the Apollo store
      const apolloState = apollo.cache.extract();

      return {
        ...appProps,
        apolloState
      };
    }

    constructor(props) {
      super(props);
      this.apolloClient = initApollo(props.apolloState);
    }

    render() {
      return <App {...this.props} apolloClient={this.apolloClient} />;
    }
  };
};

_app.js

import App, { Container } from "next/app";
import Layout from "../components/Layout";
import { ApolloProvider } from "react-apollo";
import GlobalState from "../context/GlobalState";
import ApolloClient from "apollo-boost";
import { InMemoryCache } from "apollo-cache-inmemory";
import { secondEndpoint, secondApiToken } from "../config";
import withApolloClient from "../lib/with-apollo-client";

const createSecondClient = () => {
  const headers = {
    "Access-Token": secondApiToken
  };

  const client = new ApolloClient({
    uri: secondEndpoint,
    cache: new InMemoryCache(),
    fetchOptions: {
      credentials: "include"
    },
    request: operation => {
      operation.setContext({
        headers
      });
    }
  });
  return client;
};

class MyApp extends App {
  static async getInitialProps({ Component, ctx }) {
    let pageProps = {};
    if (Component.getInitialProps) {
      pageProps = await Component.getInitialProps(ctx);
    }
    pageProps.query = ctx.query;
    return { pageProps };
  }

  render() {
    const { Component, apolloClient, pageProps } = this.props;

    const wpClient = apolloClient;
    const secondClient = createSecondClient();

    return (
      <Container>
        <ApolloProvider client={{ wpClient, secondClient }}>
          <GlobalState>
            <Layout>
              <Component {...pageProps} />
            </Layout>
          </GlobalState>
        </ApolloProvider>
      </Container>
    );
  }
}

export default withApolloClient(MyApp);

Post.js

const SinglePost = props => {
  let client;

  const [post, setPost] = useState({});
  const [thisPostId, setPostId] = useState(null);
  const [ctx, setContext] = useState(null);
  const [error, setError] = useState(null);
  const [loading, setLoading] = useState(true);

  async function getPost() {
    console.log("the client", client);
    const response = await client.wpClient.query({
      query: GET_POST,
      variables: {
        uri: props.uri
      }
    });
    const {
      data: { postBy },
      error
    } = response;

    if (error) {
      setLoading({ message: "There was an error fetching the article" });
      setError(error);
    }
    setLoading(false);
    setPostId(postBy.postId);
    setPost(postBy);
  }

  useEffect(() => {
    getPost();
  }, post);

  return (
    <AppContext.Consumer>
      {context => {
        if (ctx === null) {
          setContext(context);
        }
        const { showGlobalCommentForm } = context;

        return (
          // We wrap this Query in an ApolloConsumer so that we have 'client' to pass on to the LoadComments component
          <ApolloConsumer>
            {c => {
              client = c;

So, the end result is that whereas previously when using the Query component, with only one client, when I would run next export and get a fully rendered static HTML version of the page, now I have to wait for the fetch and render.
I have read the documentation on the front page of this project for SSR, but I can't figure out how to include the call for getMarkupFromTree in this structure, and if I could, if that would do the trick.
Thanks for any advice.

Update your with-apollo-client.js file to include:
import React from "react";
import initApollo from "./init-apollo";
import Head from "next/head";
import { getDataFromTree } from "react-apollo";
+ import { getMarkupFromTree } from "react-apollo-hooks";
+ import { renderToString } from "react-dom/server";

export default App => {
  return class Apollo extends React.Component {
    static displayName = "withApollo(App)";
    static async getInitialProps(ctx) {
      const { Component, router } = ctx;

      let appProps = {};
      if (App.getInitialProps) {
        appProps = await App.getInitialProps(ctx);
      }

      // Run all GraphQL queries in the component tree
      // and extract the resulting data
      const apollo = initApollo();
      if (!process.browser) {
        try {
          // Run all GraphQL queries
          await getDataFromTree(
            <App
              {...appProps}
              Component={Component}
              router={router}
              apolloClient={apollo}
            />
          );

+         await getMarkupFromTree({
+		renderFunction: renderToString,
+		tree: <App
+			{...appProps}
+			Component={Component}
+			router={router}
+			apolloClient={apollo}
+		/>,
+	  });
        } catch (error) {
          // Prevent Apollo Client GraphQL errors from crashing SSR.
          // Handle them in components via the data.error prop:
          // https://www.apollographql.com/docs/react/api/react-apollo.html#graphql-query-data-error
          console.error("Error while running `getDataFromTree`", error);
        }

        // getDataFromTree does not call componentWillUnmount
        // head side effect therefore need to be cleared manually
        Head.rewind();
      }

      // Extract query data from the Apollo store
      const apolloState = apollo.cache.extract();

      return {
        ...appProps,
        apolloState
      };
    }

    constructor(props) {
      super(props);
      this.apolloClient = initApollo(props.apolloState);
    }

    render() {
      return <App {...this.props} apolloClient={this.apolloClient} />;
    }
  };
};

This has also been pointed out by another person in https://github.com/trojanowski/react-apollo-hooks/issues/52#issuecomment-456864176

Unfortunately, even with that change in place, my queries are still running after the page loads in the static HTML export, instead of having been fully rendered via the export process.

Your scenario (not fully rendered) only happens once one or multiple graphql errors occurred during „getDataFromTree“ / „getMarkupFromTree“.
Asides from that, I quickly just glanced over your code and you forgot to import the ApolloProvider of this module. ( See )
Add it to your existing providers in _app.js and add the snipet from above and you should be good to go.

Thanks for the feedback, but still not getting a rendered export.
I have checked for any graphql errors (there are none that I see in the console on any page), and I have imported the module you mentioned, and still have the same result. Is there a way to enable logging of graphql renders during build so I can make sure no pages are returning errors? The catch statement in with-apollo-client never catches.
_app.js current stands as :
import App, { Container } from "next/app";
import Layout from "../components/Layout";
import { ApolloProvider } from "react-apollo";
import { ApolloProvider as ApolloHooksProvider } from "react-apollo-hooks";
import GlobalState from "../context/GlobalState";
import ApolloClient from "apollo-boost";
import { InMemoryCache } from "apollo-cache-inmemory";
import { secondEndpoint, secondApiToken } from "../config";
import withApolloClient from "../lib/with-apollo-client";

const createSecondClient = () => {
  const headers = {
    "Access-Token": secondApiToken
  };

  const client = new ApolloClient({
    uri: secondEndpoint,
    cache: new InMemoryCache(),
    fetchOptions: {
      credentials: "include"
    },
    request: operation => {
      operation.setContext({
        headers
      });
    }
  });
  return client;
};

class MyApp extends App {
  static async getInitialProps({ Component, ctx }) {
    let pageProps = {};
    if (Component.getInitialProps) {
      pageProps = await Component.getInitialProps(ctx);
    }
    pageProps.query = ctx.query;
    return { pageProps };
  }

  render() {
    const { Component, apolloClient, pageProps } = this.props;

    const wpClient = apolloClient;
    const secondClient = createSecondClient();

    return (
      <Container>
        <ApolloProvider client={{ wpClient, secondClient }}>
          <ApolloHooksProvider client={{ wpClient, secondClient }}>
            <GlobalState>
              <Layout>
                <Component {...pageProps} />
              </Layout>
            </GlobalState>
          </ApolloHooksProvider>
        </ApolloProvider>
      </Container>
    );
  }
}

export default withApolloClient(MyApp);

and with-apollo-client.js stands as:
import React from "react";
import initApollo from "./init-apollo";
import Head from "next/head";
import { getDataFromTree } from "react-apollo";
import { renderToString } from "react-dom/server";
import { getMarkupFromTree } from "react-apollo-hooks";

export default App => {
  return class Apollo extends React.Component {
    static displayName = "withApollo(App)";
    static async getInitialProps(ctx) {
      const { Component, router } = ctx;

      let appProps = {};
      if (App.getInitialProps) {
        appProps = await App.getInitialProps(ctx);
      }

      // Run all GraphQL queries in the component tree
      // and extract the resulting data
      const apollo = initApollo();
      if (!process.browser) {
        try {
          // Run all GraphQL queries
          await getDataFromTree(
            <App
              {...appProps}
              Component={Component}
              router={router}
              apolloClient={apollo}
            />
          );
          await getMarkupFromTree({
            renderFunction: renderToString,
            tree: (
              <App
                {...appProps}
                Component={Component}
                router={router}
                apolloClient={apollo}
              />
            )
          });
        } catch (error) {
          // Prevent Apollo Client GraphQL errors from crashing SSR.
          // Handle them in components via the data.error prop:
          // https://www.apollographql.com/docs/react/api/react-apollo.html#graphql-query-data-error
          console.error("Error while running `getDataFromTree`", error);
        }

        // getDataFromTree does not call componentWillUnmount
        // head side effect therefore need to be cleared manually
        Head.rewind();
      }

      // Extract query data from the Apollo store
      const apolloState = apollo.cache.extract();

      return {
        ...appProps,
        apolloState
      };
    }

    constructor(props) {
      super(props);
      this.apolloClient = initApollo(props.apolloState);
    }

    render() {
      return <App {...this.props} apolloClient={this.apolloClient} />;
    }
  };
};

-<ApolloProvider client={{ wpClient, secondClient }}>
-          <ApolloHooksProvider client={{ wpClient, secondClient }}>
            <GlobalState>
              <Layout>
                <Component {...pageProps} />
              </Layout>
            </GlobalState>
          </ApolloHooksProvider>
        </ApolloProvider>

These two lines look fishy, more precisely that you pass an object containing two clients.
In the typings of this library and of apollo react one can see that only one apollo client is expected and not an object containing multiple.
If you want to utilize multiple clients, consider using a composite link with two http links, each pointing to your a different endpoints

Yep, two clients was the initial point of my question:

Why? Because I have two GraphQL data sources and need to be able to specify the client in the component, and Query doesn't take this parameter.

When I only had one client, I was getting static HTML renders no problem. This comment on this issue for react apollo was the inspiration for my going with the direction of putting two clients on the client object passed to ApolloProvider.
This setup does indeed function, and I can run queries like so:
const response = await client.wpClient.query({
   query: GET_POST,
   variables: {
     uri: props.uri
   }
});

vs client.query, as you would usually do with ApolloConsumer.
In any event, the composite link information you shared sent me down the right path, and was able to refactor using multiple links and useQuery. After that, I now get static HTML exports again.
Thanks for your help!

In case anyone comes across this in the future, here is a write-up of the method I ended up using: https://www.loudnoises.us/next-js-two-apollo-clients-two-graphql-data-sources-the-easy-way/

@paulisloud you forgot the "getMarkupFromTree" and "renderToString" import in your blog post (in the final with-apollo-client.js file).

Good catch, many thanks for taking the time to go through the post. Updated and added a hat tip @ThomasK33.

repo: trojanowski/react-apollo-hooks


text:
add screenshots or frontend demo

Can you please add screenshots or demo of frontend so devs can see if its relevant for them? Thanks.

Hi there - a demo is available at https://vxnn.troncali.com/demo/.  The demo site uses VuePress, which is a static site generator based on Vue.
The frontend app in the repo is currently just the standard files scaffolded by vue.  More will be added to the demo as things are built out, but there are no specific frontend components yet.

source: gharchive/issue

repo: troncali/nest-vue

license: MIT

license_type: permissive

license_source: github-api


text:
feat: upgraded bitKeepWallet

Hi, Team tronprotocol,
This PR upgrades bitkeep wallet to the bitget wallet to make it easier for our users to connect to tronwallet-adapter dapps.
Please let me know if anything needs to be added or changed to satisfy your requirements.
Cheers,
Bitget Wallet team

Thank you very much! We will merge the PR and publish a new version later.

hello, does the bitget wallet app support Tron Dapp? I found that there is not window.tronLink or window.tronWeb in Bitget Wallet App browser.

Hello, does the bitget wallet app support Tron Dapp? I found that there is no window.tronLink or window.tronWeb. And i can not use Tron Dapp anymore.

source: gharchive/pull-request

authors: kisenyang way2ex zhuqingguang

repo: tronprotocol/tronwallet-adapter


text:
🛑 qBit is down

In 2ea0ba2, qBit (https://tronflix.app/qbit/) was down:

HTTP code: 520
Response time: 166 ms

Resolved: qBit is back up in 7723f73.

repo: tronyx/upptime


text:
reference (ref) on svg does not work

If I want to receive reference to svg element:
var Inferno = require('inferno');

var IconHeart = function(props, context) {
  var className = props.className || 'icon-heart s-1em';
  return (
    <svg xmlns="http://www.w3.org/2000/svg" class={className} ref={props.ref} ...>
      <path fill="#000" d="..." />
    </svg>
  )
};

module.exports = IconHeart;

I get an Error in Inferno:
		function getRefInstance$1(node, instance) {
			var children = instance.props.children;

			if (deepScanChildrenForNode(children, node)) {
				return getRefInstance$1(node, instance._parentComponent);
			}
			return instance;
		}

It says: Uncaught TypeError: Cannot read property 'props' of null
Looks like Inferno could not determine instance of svg.

@volodalexey As per React, you cannot use refs in stateless functional components. You can use hooks instead within functional components or stateful components.

@trueadm Thanks for the information. Ok. Then I will use stateful component.

authors: trueadm volodalexey

repo: trueadm/inferno

license: mit

license_source: bigquery


text:
coeducationally

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[c]

/trunk merge

repo: trunk-io/mergequeue-staging


text:
dissever, asyla

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,d]

/trunk merge


text:
bludgeoned, germanely

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,g]

/trunk merge


text:
demagnetising, behedge

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,d]

/trunk merge


text:
deregulations, forgivingly

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[d,f]

/trunk merge


text:
epitheliomatous, abevacuation

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,e]

/trunk merge


text:
eternals, acacetin

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,e]

/trunk merge


text:
ferrumination

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f]

/trunk merge


text:
bloomsbury

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b]

/trunk merge


text:
furmety, gambesons

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[f,g]

/trunk merge


text:
cowrie, amylosis

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[a,c]

/trunk merge


text:
emperize, grading

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,g]

/trunk merge


text:
girny, carretela

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 30
deps=[c,g]

/trunk merge


text:
falsework, eyewinks

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[e,f]

/trunk merge


text:
glassworking, frotteurs

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[f,g]

/trunk merge


text:
brindled, dakoities

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 100
sleep for: 300s
close stale after: 4 hours
[pullrequest]
requests per hour: 0
deps=[b,d]

/trunk merge


text:
cynogenealogist, amus

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,c]

/trunk merge

repo: trunk-io/mergequeue


text:
elaphe, dorsoventrally

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[d,e]

/trunk merge


text:
feus, coronule

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,f]

/trunk merge


text:
eastings, formation

This pull request was generated by the 'mq' tool

/trunk merge


text:
furbished, bloodless

This pull request was generated by the 'mq' tool

/trunk merge


text:
gestatorium, countermeet

This pull request was generated by the 'mq' tool

/trunk merge


text:
ascitan, footway

This pull request was generated by the 'mq' tool

/trunk merge


text:
ectorganism

This pull request was generated by the 'mq' tool

/trunk merge


text:
eurygnathous, finality

This pull request was generated by the 'mq' tool

/trunk merge


text:
encratism, gaucherie

This pull request was generated by the 'mq' tool

/trunk merge


text:
amputative, furfuramide

This pull request was generated by the 'mq' tool

/trunk merge


text:
batrachoid, adhesions

This pull request was generated by the 'mq' tool

/trunk merge


text:
cecidomyiid, embryonally

This pull request was generated by the 'mq' tool

/trunk merge


text:
cherimoya, absented

This pull request was generated by the 'mq' tool

/trunk merge


text:
functioning

This pull request was generated by the 'mq' tool

/trunk merge


text:
bribe, coked

This pull request was generated by the 'mq' tool

/trunk merge


text:
ensilaging, dehydrogenise

This pull request was generated by the 'mq' tool

/trunk merge


text:
cladoselache, firesafe

This pull request was generated by the 'mq' tool

/trunk merge


text:
disdiazo, carmoisin

This pull request was generated by the 'mq' tool

/trunk merge


text:
assessee

This pull request was generated by the 'mq' tool

/trunk merge


text:
embouchures, corrupt

This pull request was generated by the 'mq' tool

/trunk merge


text:
ancestress, diaphragmatic

This pull request was generated by the 'mq' tool

/trunk merge


text:
fredaine, castanian

This pull request was generated by the 'mq' tool

/trunk merge


text:
foreyard, disglorify

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,f]

/trunk merge


text:
disvaluing, crombec

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[c,d]

/trunk merge


text:
derisory, flawy

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 100
deps=[d,f]

/trunk merge


text:
baglike, gemmipares

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,g]

/trunk merge


text:
arietid, gantleting

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,g]

/trunk merge


text:
buirdly, carminate

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,c]

/trunk merge


text:
auriculae, commuting

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,c]

/trunk merge


text:
almoning, downthrust

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,d]

/trunk merge


text:
amphitokal, enhance

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,e]

/trunk merge


text:
geogenesis, brooch

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,g]

/trunk merge


text:
foreshop, ballcarrier

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[b,f]

/trunk merge


text:
carfour, deseam

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[c,d]

/trunk merge


text:
anele, footprint

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.1
logical conflict every: 1000
sleep for: 600s
close stale after: 24 hours
[pullrequest]
requests per hour: 20
deps=[a,f]

/trunk merge


text:
Is it possible to simplify Database::for_test ?

➜  trustify git:(main) rg "Database\:\:for_test"
modules/ingestor/src/service/cve/loader.rs
80:        let db = Database::for_test("ingestors_cve_loader").await?;

modules/importer/src/test.rs
30:    let db = Database::for_test("test_default").await.unwrap();
125:    let db = Database::for_test("test_oplock").await.unwrap();

modules/ingestor/src/service/advisory/osv/loader.rs
154:        let db = Database::for_test("ingestors_osv_loader").await?;

modules/ingestor/src/endpoints/advisory.rs
74:        let db = Database::for_test("upload_advisory_csaf").await?;
101:        let db = Database::for_test("upload_advisory_osv").await?;
128:        let db = Database::for_test("upload_unknown_format").await?;

modules/graph/src/graph/vulnerability/mod.rs
146:        let db = Database::for_test("ingest_cve").await?;
173:        let db = Database::for_test("get_advisories_from_cve").await?;

modules/graph/src/graph/advisory/mod.rs
469:        let db = Database::for_test("ingest_advisories").await?;
507:        let db = Database::for_test("ingest_affected_package_version_range").await?;
564:        let db = Database::for_test("ingest_fixed_package_version").await?;
624:        let db = Database::for_test("ingest_advisory_cve").await?;
651:        let db = Database::for_test("advisory_affected_vulnerability_assertions").await?;
692:        let db = Database::for_test("advisory_not_affected_vulnerability_assertions").await?;

modules/graph/src/graph/sbom/mod.rs
685:        let db = Database::for_test("ingest_sboms").await?;
710:        let db = Database::for_test("ingest_and_fetch_sboms_describing_purls").await?;
760:        let db = Database::for_test("ingest_and_locate_sboms_describing_cpes").await?;
810:        let db = Database::for_test("transitive_dependency_of").await?;
879:        let db = Database::for_test("ingest_contains_packages").await?;
951:        let db = Database::for_test("sbom_vulnerabilities").await?;

modules/graph/src/graph/package/package_version.rs
218:        let db = Database::for_test("package_version_not_affected_assertions").await?;

modules/graph/src/graph/sbom/spdx.rs
174:        let db = Database::for_test("parse_spdx_quarkus").await?;
228:        let db = Database::for_test("parse_spdx_openshift").await?;
280:        let db = Database::for_test("parse_spdx").await?;

modules/graph/src/graph/package/mod.rs
618:        let db = Database::for_test("ingest_packages").await?;
651:        let db = Database::for_test("ingest_package_versions_missing_version").await?;
676:        let db = Database::for_test("ingest_package_versions").await?;
711:        let db = Database::for_test("get_versions_paginated").await?;
768:        let db = Database::for_test("ingest_qualified_packages_transactionally").await?;
808:        let db = Database::for_test("ingest_qualified_packages").await?;
866:        let db = Database::for_test("ingest_package_version_ranges").await?;
918:        let db = Database::for_test("package_affected_assertions").await?;
1011:        let db = Database::for_test("package_not_affected_assertions").await?;
1066:        let db = Database::for_test("package_vulnerability_assertions").await?;
1130:        let db = Database::for_test("advisories_mentioning_package").await?;

modules/graph/src/graph/package/qualified_package.rs
142:        let db = Database::for_test("vulnerability_assertions").await?;

It works with the same database name
let db = Database::for_test("a").await?;

https://github.com/trustification/trustify/discussions/136#discussion-6459188
But I don't know the reason so I'm asking, thanks :+1:

The databases named by that parameter are DROPped and CREATEd within that for_test call. If the tests are run in parallel, and all the db names are the same, there is a potential race condition in which a database created in one test might be dropped by another test.

@jcrossley3 thanks!
we can close this :+1:

repo: trustification/trustify


text:
Update contract deploy tools dependency version

Related to: trustlines-network/project#631

Codecov Report

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

@@           Coverage Diff           @@
##           master      #56   +/-   ##
=======================================
  Coverage   76.41%   76.41%
=======================================
  Files           7        7
  Lines         301      301
=======================================
  Hits          230      230
  Misses         71       71

Continue to review full report at Codecov.

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

Merge by successful CI and optimistic approval by Ralf.

authors: codecov-io weilbith

repo: trustlines-protocol/merkle-drop


text:
Remove Typescript code from core repo

Fixes https://github.com/trustwallet/wallet-core/issues/1427

removed from release repo too

repo: trustwallet/wallet-core


text:
latest version (v1.3.0) not available in maven registry

Expected Behavior
Expected latest version of courier-java in maven registry to be the latest released/tagged version in github.com/trycourier/courier-java
Actual Behavior
The latest version available in maven registry is v1.2.0 (https://search.maven.org/search?q=a:courier-java)

thanks for bringing this up to our attention @raniero-sequence - we've pushed 1.3.0 up.

great! when i checked again it was there so i closed the ticket proactively. thanks for taking care of it.

No worries at all - would love to hear any feedback you may have on the SDK @raniero-sequence

repo: trycourier/courier-java


text:
Create 0000-01-02-trying-alfare.md

I haven't made any changes yet, just still learning how this thing works.

That was fun. Man, I really need to learn more of this stuff.

repo: trying-alfare/github-slideshow


text:
visualising bboxes/masks

Hey, how about an extension for the Detection class and drawing.py to add bboxes and masks to directly visualize them?
Do you think this would fit norfair?

Hey, thanks for the proposal! We are currently in the process of merging support for MOT metrics into the library, which includes a bbox drawing function, so that capability will soon be added. Regarding segmentation, I don't think it currently fits into Norfair's use cases, though I may be wrong.
I think for the time being these capabilities won't be needed, but I really appreciate the ideas. Any other ideas you have are most definitely welcome. Thanks!

Hi, I just wanted to add a note of support for the proposed functionality of drawing masks. I think it would be really helpful to be able to visualise the predicted segmentation in addition to the centroid spot. This will help to verify the quality of the detections.
Thanks!

Hey @nachonacho2 thanks for the feedback. I think we'll add mask drawing through https://github.com/tryolabs/norfair/pull/24/files as it seems to be something people need, doesn't really expand norfair's surface area too much, and is easy to implement. So stand by for it!

authors: SharifElfouly joaqo nachonacho2

repo: tryolabs/norfair


text:
add index access to dictionaries

would it be possible to have
export type ErrorCodeKey = 'unknownJoi' | 'notFound' | 'badRequest' | 'ise' | 'npe' | 'dataMissing' | 'any.required'

SafeDictionary<[number, string], ErrorCodeKey>

behave like
export type ErrorCodeKey = 'unknownJoi' | 'notFound' | 'badRequest' | 'ise' | 'npe' | 'dataMissing' | 'any.required'

type ErrorCodeTuple = [number, string]

type ErrorCodeIndex = { [k: string]: ErrorCodeTuple }

export const errorCodes: SafeDictionary<ErrorCodeTuple, ErrorCodeKey> & ErrorCodeIndex

or maybe add a new dictionary type?

Hey @xenoterracide!
Thank you for the suggestion!
Do I understand you right, that you want the autocompletion for ErrorCodeKey but still want to access other keys and get ErrorCodeTuple, right?

@xenoterracide is there anything we can do here? do we have any action point that we can convert to a PR?

I'm going to say no for now, or perhaps, I forget... lol. I'll reopen if yes.

authors: Beraliv xenoterracide

repo: ts-essentials/ts-essentials


text:
Import names with dash dont properly import

/bounty $5

repo: tscircuit/snippets


text:
TSDuck at IBC 2018

Hi,
For TSDuck users who will be at IBC 2018 in Amsterdam next September, I will make a very short presentation at the EBU Open Source Meetup. Several open source projects are presented every year. There won't be much time for each project, so you won't probably learn anything. For users who are already familiar with TSDuck, let's just use the event as an opportunity to meet and share ideas and experiences.
EBU is the European Broadcasting Union. Its Open Source Meetup will take place Saturday Sept. the 15th, 16:00-17:00 at the EBU stand 10.F20. If you plan to meet here before or immediately afterwards, please leave a message here or send an email to contact @ tsduck.io.

Thanks to TSDuck users who attended the presentation. It is always refreshing to meet users.

repo: tsduck/tsduck


text:
[FEAT] Pre-Release for debian

It would be great to have pre-release packages for debian

Hi @enricovittorini
Agreed. However, the nightly builds are created in the GitHub CI/CD environment which does not provide Debian runners, only Ubuntu runners (and Windows and macOS).
Since rebuilding .deb packages for TSDuck on Debian is as simple as make installer, there is no real need to look for a complicated external CD/CD setup for Debian.

@lelegard I was trying to build tsduck on debian:stable docker could not install prerequisites. To fix them I had to install the following packages:

sudo
lsb-release
locales
locales-all

Hi @enricovittorini
Packages such as sudo and the like are basic. I assumed that they are installed everywhere.
For the rest, execute first the script scripts/install-prerequisites.sh as documented here.

@lelegard  on debian:stable docker form dockerhub it is not the case:
# sudo
/bin/sh: 1: sudo: not found
#

After installing sudo only, pre-req script does not install anything:
root@9be689751d70:/tsduck/scripts# ./install-prerequisites.sh
root@9be689751d70:/tsduck/scripts#

after installing lsb-release, the script gets executed correcty.
root@9be689751d70:/tsduck/scripts# ./install-prerequisites.sh  Packages: git git-lfs g++ cmake flex bison dos2unix curl tar zip linux-libc-dev dpkg-dev python3 libedit-dev pcscd libpcsclite-dev libcurl4 libcurl4-openssl-dev libsrt-openssl-dev librist-dev libusb-1.0-0-dev default-jdk doxygen graphviz Hit:1 http://deb.debian.org/debian stable InRelease Hit:2 http://deb.debian.org/debian stable-updates InRelease Hit:3 http://deb.debian.org/debian-security stable-security InRelease Reading package lists... Done Building dependency tree... Done
Still not enough, without locales-all (indeed no need for "locale" package) there are warnings during the "make"
root@9be689751d70:/tsduck# make bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
Once isntalled locales-all, all is ok
root@9be689751d70:/tsduck# make   [DEP] base/xml/tsxmlElement.cpp   [DEP] base/xml/tsxmlDocument.cpp   [DEP] base/xml/tsxmlDeclaration.cpp   [DEP] base/xml/tsxmlComment.cpp   [DEP] base/xml/tsxmlAttribute.cpp

Rationale:

sudo : without it, you cannot install anything.
lsb-release : required to identify the system and version, required to decide which packages to install with which command.
locale during the build : previously, some people had issues with their locale which affected the sort order of some shell commands during the build, therefore the locale of the build process is forced to en_US.UTF8 to enforce a reproductible build.

I would say that a docker container is an execution environment for applications, not a developer's environment. Developers need many tools and a typical full operating system. This is why scripts/install-prerequisites.sh assumes a reasonable developer's environment and installs specific tools and libraries which are needed to build TSDuck.
Reading this script, you will see it supports a large number of operating systems and versions. It took years to get there. All addressed configurations were tested at some point, typically in a virtual machine. So, there is no room to add "non-standard" development environments.

@lelegard thanks.
My goal was to give a clue to those who will have the same issue in the future. Maybe it could be worth to add a note in "how to build" tsduck section.

Maybe it could be worth to add a note in "how to build" tsduck section.

Precisely, there is a complete section about this in the TSDuck programmer's guide: https://tsduck.io/doxy/building.html
This section has been existed for a long time and I often post a link to it, almost every time someone new needs to build TSDuck, for instance to take advantage of a new feature or bug  fix. I hardly see what to add.

@lelegard I was trying to build tsduck on debian:stable docker could not install prerequisites. To fix them I had to install the following packages:

sudo
lsb-release
locales
locales-all

You can omit the locales-all package, and instead do this:
RUN echo "en_US.UTF-8 UTF-8" >>/etc/locale.gen && \
locale-gen

authors: ajkq enricovittorini lelegard


text:
[FEAT] Read cell Identifier

Is your feature request related to a problem?
Hi @lelegard,
Is it possible to read the cell identifier on TSSCAN?
In Italy the 8 bits S40-$47 are used by RAI also in DVB-T, for identify the cell.
So it would be very useful to be able to receive this parameter.
Thanks
Cristian

In Italy the 8 bits S40-$47 are used by RAI also in DVB-T, for identify the cell.

What do you mean by "8 bits S40-$47"? Looking at the Italian DVB-T files you previously provided, I do not see any standard DVB descriptor to signal the cell_id in the NIT.

I refer to the TPS carrier
RAI and others operators in Italy have studied a "trick" to differentiate the locations, taking inspiration from the cell-id created for DVB-H. Some analyzer is able to receive it correctly.
This link explains in English the project of RAI : http://www.crit.rai.it/CritPortal/progetti/?p=707

OK, it is in the DVB-T TPS. To my knowledge, there is no standard API to get the TPS from tuners on Linux and Windows. Maybe some proprietary application is delivered with a given tuner to get the TPS. But I do not know how to get the TPS in the general case.

thanks @lelegard,
I just thought so. I read that the specification was born for DVB-H and then later used without any standard also for DVB-T.
With the arrival of DVB-T2 it will be easier to implement?

With the arrival of DVB-T2 it will be easier to implement?

It is not a matter of DVB-T vs. DVB-T2. It is a matter of standard software API on Linux and Windows. The two operating systems provide two very different uniform API's to access tuners. The Linux API is well alive. The Windows API is more or less in an abandoned state. Operations such as tuning and receiving packets are implemented in both systems (fortunately!) Getting the signal state is not so well implemented (see #853). Getting the TPS is not implemented at all. So, even if a hardware tuner can receive the TPS and its driver can read its content, there exist no standard way to read it from an application such as TSDuck. And I do not really expect this to change. DVB-T and TPS exist for more than 20 years now.

[CrazyCat](url=https://sourceforge.net/u/crazycat69/profile/

) implementoval čítanie Cell_ID do svojho CrazyScan2

authors: EnoSat cristianpuddu lelegard


text:
Add P90 metric

Background
Adds P90 value in metrics
Issue: #426
Checklist

[x] Git commit messages conform to community standards.
[x] Each Git commit represents meaningful milestones or atomic units of work.
[ ] Changed or added code is covered by appropriate tests.

This seems to be a duplicate of #452 :/

authors: otherpirate tsenart

repo: tsenart/vegeta


text:
Can not Install ternjs

[Enter steps to reproduce below:]

...
...

Atom Version: 1.11.2
Electron Version: 0.37.8
System: Unknown Windows Version
Thrown From: atom-ternjs package, v0.15.0
Stack Trace
Failed to load the atom-ternjs package
At Cannot find module 'underscore-plus'

Error: Cannot find module 'underscore-plus'
  at Module._resolveFilename (module.js:339:15)
  at Function.Module._resolveFilename (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\module-cache.js:383:52)
  at Function.Module._load (module.js:290:25)
  at Module.require (module.js:367:17)
  at require (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:50:27)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ternjs\lib\atom-ternjs-manager.js:11:23)
  at Module._compile (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:103:30)
  at Object.defineProperty.value [as .js] (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\compile-cache.js:208:21)
  at Module.load (module.js:357:32)
  at Function.Module._load (module.js:314:12)
  at Module.require (module.js:367:17)
  at require (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:50:27)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ternjs\lib\atom-ternjs-provider.js:11:26)
  at Module._compile (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:103:30)
  at Object.defineProperty.value [as .js] (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\compile-cache.js:208:21)
  at Module.load (module.js:357:32)
  at Function.Module._load (module.js:314:12)
  at Module.require (module.js:367:17)
  at require (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:50:27)
  at Object.<anonymous> (C:\Users\Administrator\.atom\packages\atom-ternjs\lib\atom-ternjs.js:15:27)
  at Module._compile (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:103:30)
  at Object.defineProperty.value [as .js] (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\compile-cache.js:208:21)
  at Module.load (module.js:357:32)
  at Function.Module._load (module.js:314:12)
  at Module.require (module.js:367:17)
  at require (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\native-compile-cache.js:50:27)
  at Package.module.exports.Package.requireMainModule (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package.js:721:27)
  at C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package.js:117:28
  at Package.module.exports.Package.measure (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package.js:92:15)
  at Package.module.exports.Package.load (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package.js:106:12)
  at PackageManager.module.exports.PackageManager.loadPackage (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package-manager.js:457:14)
  at C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package-manager.js:402:19
  at Config.module.exports.Config.transact (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\config.js:312:16)
  at PackageManager.module.exports.PackageManager.loadPackages (C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\package-manager.js:397:19)
  at C:\Users\Administrator\AppData\Local\atom\app-1.11.2\resources\app.asar\src\atom-environment.js:759:28

Commands

Config
{
  "core": {
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ]
  }
}

Installed Packages
# User
activate-power-mode, v1.0.2 (inactive)
atom-ternjs, v0.15.0 (inactive)
atomic-chrome, v0.3.0 (inactive)
emmet, v2.4.3 (inactive)
tree-view-finder, v0.2.1 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (inactive)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (inactive)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (inactive)
archive-view, v0.61.1 (inactive)
autocomplete-atom-api, v0.10.0 (inactive)
autocomplete-css, v0.11.2 (inactive)
autocomplete-html, v0.7.2 (inactive)
autocomplete-plus, v2.31.1 (inactive)
autocomplete-snippets, v1.11.0 (inactive)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (inactive)
background-tips, v0.26.1 (inactive)
bookmarks, v0.42.0 (inactive)
bracket-matcher, v0.82.1 (inactive)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (inactive)
dev-live-reload, v0.47.0 (inactive)
encoding-selector, v0.22.0 (inactive)
exception-reporting, v0.40.0 (inactive)
find-and-replace, v0.201.1 (inactive)
fuzzy-finder, v1.4.0 (inactive)
git-diff, v1.1.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (inactive)
image-view, v0.59.0 (inactive)
incompatible-packages, v0.26.1 (inactive)
keybinding-resolver, v0.35.0 (inactive)
line-ending-selector, v0.5.0 (inactive)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (inactive)
metrics, v1.0.0 (inactive)
notifications, v0.65.1 (inactive)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (inactive)
snippets, v1.0.2 (inactive)
spell-check, v0.68.2 (inactive)
status-bar, v1.4.1 (inactive)
styleguide, v0.47.0 (inactive)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (inactive)
timecop, v0.33.2 (inactive)
tree-view, v0.209.3 (inactive)
update-package-dependencies, v0.10.0 (inactive)
welcome, v0.35.1 (inactive)
whitespace, v0.33.0 (inactive)
wrap-guide, v0.38.2 (inactive)
language-c, v0.52.1 (inactive)
language-clojure, v0.21.0 (inactive)
language-coffee-script, v0.47.2 (inactive)
language-csharp, v0.12.1 (inactive)
language-css, v0.37.1 (inactive)
language-gfm, v0.88.0 (inactive)
language-git, v0.15.0 (inactive)
language-go, v0.42.1 (inactive)
language-html, v0.45.1 (inactive)
language-hyperlink, v0.16.0 (inactive)
language-java, v0.23.0 (inactive)
language-javascript, v0.119.0 (inactive)
language-json, v0.18.2 (inactive)
language-less, v0.29.5 (inactive)
language-make, v0.22.2 (inactive)
language-mustache, v0.13.0 (inactive)
language-objective-c, v0.15.1 (inactive)
language-perl, v0.35.0 (inactive)
language-php, v0.37.2 (inactive)
language-property-list, v0.8.0 (inactive)
language-python, v0.45.0 (inactive)
language-ruby, v0.69.0 (inactive)
language-ruby-on-rails, v0.25.0 (inactive)
language-sass, v0.56.0 (inactive)
language-shellscript, v0.22.4 (inactive)
language-source, v0.9.0 (inactive)
language-sql, v0.23.0 (inactive)
language-text, v0.7.1 (inactive)
language-todo, v0.28.0 (inactive)
language-toml, v0.18.0 (inactive)
language-xml, v0.34.9 (inactive)
language-yaml, v0.26.0 (inactive)

# Dev
No dev packages

underscore-plus is an dependency in the package.json of this package. You may first check if there are any problems with apm while installing it.
You also may try to manually do a $ apm install.
$ cd ~/.atom/packages/atom-ternjs
$ apm install

git clone this repository,and $npm install

authors: andmeics tststs yummy222

repo: tststs/atom-ternjs


text:
🛑 Webserver is down

In 0c66486, Webserver (https://web.campa.tools) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Webserver is back up in 8f619de.

repo: tsueri/upptime


text:
Update leccion_8.md

Corrijo un par de erratas. Lo que no veo es que lo del ejercicio de visualización haya quedado en ninguna parte en este archivo, seguramente hay que actualizarlo en el sitio de TTHub

Pensé que lo habías eliminado, por eso sugerí que se eliminara el título.

authors: gabrielcalarco susannalles

repo: tthub-repo/lecciones


text:
stack trace on buffer (warmth) apply

triggered by:
gi.m_FreezingBuff.Apply(nV);
[01:14:34.600] [Error] Exception in Harmony patch of method GearItem.ApplyBuffs(System.Single):
UnhollowerBaseLib.Il2CppException: System.NullReferenceException: Object reference not set to an instance of an object.
at UnhollowerBaseLib.Il2CppException.RaiseExceptionIfNecessary (System.IntPtr returnedException) [0x00018] in <56ec66a01d45498298ce9793c60195c6>:0
at FreezingBuff.Apply (System.Single normalizedValue) [0x00048] in <4d543663e0e846feb0cb39f285ba95d1>:0
at WarmFood.Implementation.Buffs (GearItem gi, System.Single nV) [0x00168] in :0
at WarmFood.GearItem_ApplyBuffs.Prefix (GearItem __instance, System.Single normalizedValue) [0x00001] in :0
at (wrapper dynamic-method) GearItem.ApplyBuffs_Patch1(GearItem,single)
at (wrapper dynamic-method) GearItem.ApplyBuffs_Patch1_il2cpp(intptr,single)

Fixed with help of zeobviouslyfakeacc and Xpazeman

repo: ttr/tld-WarmFood


text:
Added basic icon support for webview (Windows Only!)

This pull request will add basic support for changing the default icon on webview.
This was only tested on a Windows machine as I do not have Linux installed.
One thing I do think we will need to do is wrap the C functions in a macro, so that they will only be exported if the OS is Windows.
This will avoid undefined errors for Linux users. Any suggestions would be appreciated.
[if windows]
fn C.set_window_icon(application_title &wchar.Character, ico_file_path &wchar.Character)

Currently this is only supported by Windows, but Linux and MacOS will come in the future.
Here is an example of how different webview windows can have different icons.
The one on the left has a darker icon compared to the one on the right.

In order to make this as abstract as possible, I had to create a new parent struct WebviewContext which takes the webview context as well as the title, this is also a design change since it would be nice to offer more meta data to developers in order to make their application as unique as possible.
pub struct WebviewContext {
pub:
	ctx &C.webview_t
pub mut:
	title string
}

Also when creating a webview window a default title and icon is set.
pub fn create(opts CreateOptions) &WebviewContext {
	ctx := C.webview_create(int(opts.debug), opts.window)
	mut s := &WebviewContext{
		ctx: ctx
		title: 'webview'
	}
	s.set_title(s.title)
	s.set_window_icon('${@VMODROOT}/assets/icon.ico')
	return s
}

I also changed the location of the test files in order to keep them within the same module as to avoid V trying to use .vmodules instead.

Basic usage:
	mut w := create(debug: false)
	w.set_title('My Awesome App!')
	w.set_size(600, 400, .@none)
	w.set_html('
<samp>${@FILE}</samp>

Testing set_icon

')
	w.set_window_icon('my_awesome_icon.ico')
	w.run()

	w.destroy()

[if windows]
fn C.set_window_icon(application_title &wchar.Character, ico_file_path &wchar.Character)

Having written the review from the code view I missed that you also suggested this. So yes, I think it's good as long as just windows is supported!

[if windows]
fn C.set_window_icon(application_title &wchar.Character, ico_file_path &wchar.Character)

Having written the review from the code view I missed that you also suggested this. So yes, I think it's good as long as just windows is supported!

Thanks for the great feedback, I did see some changes that, I forgot to remove, like the bool 😄 .
I have added the macros, will just adjust the code and we can go for another round 😎 .

You'll probably run into an error an error when adding the macro and trying to use a return value.
E.g:
pub fn (w &Webview) set_icon(icon_file_path string) ! {
	if !C.set_window_icon(wchar.from_string(w.title), wchar.from_string(icon_file_path)) {
		return error('Failed setting icon.')
	}
}

A V result return could be more valuable than having the temporary [if windows] macro. It would be okay then to just mention in the doc comment that only windows is supported for now. What do you think on this?
There is probably also a better option than using a bool, as it can return multiple errors. Then both errors MessageBoxW(NULL, L"Failed to load icon from file!", L"Error", MB_ICONERROR); and MessageBoxW(NULL, L"Failed to find the application window!", L"Error", MB_ICONERROR); can be signaled to the user as V errors.

You'll probably run into an error an error when adding the macro and trying to use a return value.
E.g:
pub fn (w &Webview) set_icon(icon_file_path string) ! {
	if !C.set_window_icon(wchar.from_string(w.title), wchar.from_string(icon_file_path)) {
		return error('Failed setting icon.')
	}
}

A V result return could be more valuable than having the temporary [if windows] macro. It would be okay then to just mention in the doc comment that only windows is supported for now. What do you think on this?
There is probably also a better option than using a bool, as it can return multiple errors. Then both errors MessageBoxW(NULL, L"Failed to load icon from file!", L"Error", MB_ICONERROR); and MessageBoxW(NULL, L"Failed to find the application window!", L"Error", MB_ICONERROR); can be signaled to the user as V errors.

I like it, will have it return the errors instead and we can panic (that is, if we want to panic on error) when trying to set the icon on linux/macos.
I am also currently working on Linux support, just getting my dev environment up, but for this pull request, it will only be windows.
I will update the docs as mentioned.

Thanks for the updates.
I'll walk the dog, and come back to the PR later.

I am also currently working on Linux support, just getting my dev environment up, but for this pull request, it will only be windows.

Nice!

I don't want to interfere with anything ongoing, let me know when this is ready then I go about it as soon as a free moment opens up :+1:

So, I got it to work on Linux running Lubuntu.
MacOS will be a bit of a challenge since, I don't own one, but for now this should be good for most use cases.
What do you think?

So, I got it to work on Linux running Lubuntu with GTK.
MacOS will be a bit of a challenge since, I don't own one, but for now this should be good for most use cases.
What do you think?

I think that's awesome @Ouri028! It's planned to publish a new version with the latest changes soon, maybe we can make the feature be part of it.
I think it's okay if mac follows later (it would be great, as incorporating communication with native mac windows might also be a good step towards solving #6 directly from this V wrapper).
There are also solutions to the platfrom related problem. I'll do some tests later so I can speak having tested this specific case without doing too much guessing.
Other things are:

I haven't fully thought through the default icon yesterday as it was quite crowded, sorry about this. Setting a default window icon is not a choice the lib should make for the user. But the feature itself is great! Adding and setting the icon in the lib can can be done for the app example as examples/v-js-interop-app/icon.ico examples/project-structure/assets/icon.ico.
Same goes for a default window title, not a choice the lib wants to make for the user.

Platform support works. I push the changes here so it can remain part of the PR and we have some actual code to discuss about.

Platform support works. I push the changes here so it can remain part of the PR and we have some actual code to discuss about.

I agree fully about it being a user choice instead of making it a default option, I will just add an example to the project such as how to set the default icon and title.
I will clean up the code and move the tests back and push the feature, I will have a look at the MacOS implementation to see what I can do there, even if just to get a sample started.

Okay, I don't want to break anything ongoing or make merging changes and suggestions to complicated. So I pushed it as temporary branch for now: https://github.com/ttytm/webview/commits/temp/add-icon-support

The test couldn't be automated to check of the icon actually works, it needs to be viewed. So it fits well as example.

LGTM. Needs a rebase and addressing the latest feedback about the icon_test file. When there is no conflict with macOS I say it can be merged :) else we can use the e.g. icon_windows.v approach to reduce it to supported platforms.

I'm fine with either, I'll look into the MacOS support and see what can be done there, but if people want the feature, we can make it available as suggested icon_windows.v

Workflows should run automatically after the first approval. Sorry about the delays. I'll check what is goin on there after the PR was merged. I'm back at my desk in about 2-3h. Thanks already for all the efforts 💪

Workflows should run automatically after the first approval. Sorry about the delays. I'll check what is goin on there after the PR was merged. I'm back at my desk in about 2-3h. Thanks already for all the efforts 💪

Glad I was able to help, I'm actually planning on using this library to build my future desktop apps , so its mutually beneficial 😎

Glad I was able to help, I'm actually planning on using this library to build my future desktop apps , so its mutually beneficial 😎

That's nice to hear! It's also my first choice and I'll continue to use it for my GUI Apps too. It gets better and better 😇
Now this is also finished. Good work @Ouri028!

repo: ttytm/webview


text:
使用self_search时搜出来的结果链接错误

链接中的部分内容有时候会出现两遍，如
posts/b956e9d5.html --> posts/posts/b956e9d5.html

在主页搜是正常的，在谋篇博客搜会出现url重复

搜出来的结果应该是没错的，不管在主页搜还是博客正文搜都是posts/xxxx.html，但是在主页能正确跳转，博客正文跳转的时候就会多出一个posts。我用了hexo-abbrlink，所以链接是“posts/xxxx.html”形式，如果不用的话重复的就是一堆日期。
我不懂前端，暂时只能hardcode将就一下，在search.js第53行强行补全链接：
str += ""+ data_title +""


text:
ERROR Plugin load failed: hexo-renderer-sass

好像是我的各种版本都太高了。。。。
版本信息：
hexo -version
INFO  Validating config
hexo: 6.3.0
hexo-cli: 4.2.0
os: Darwin 21.6.0 darwin x64
node: 16.17.1
v8: 9.4.146.26-node.22
uv: 1.43.0
zlib: 1.2.11
brotli: 1.0.9
ares: 1.18.1
modules: 93
nghttp2: 1.47.0
napi: 8
llhttp: 6.0.9
openssl: 1.1.1q+quic
cldr: 41.0
icu: 71.1
tz: 2022a
unicode: 14.0
ngtcp2: 0.1.0-DEV
nghttp3: 0.1.0-DEV
OS:mac monterny 12.6
依赖安装日志：
maupassant git:(master) npm install hexo-renderer-pug --save
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated cryptiles@0.2.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated pug-loader@1.0.0: Please use pug-load for pug-loader@<=1.0.2.
npm WARN deprecated boom@0.4.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@0.2.4: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
npm WARN deprecated mkdirp@0.3.0: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated hoek@0.9.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated request@2.51.0: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated npmconf@2.1.3: this package has been reintegrated into npm and is now out of date with respect to npm
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated tar@1.0.3: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated hexo-bunyan@1.0.0: Please see https://github.com/hexojs/hexo-bunyan/issues/17
npm WARN deprecated hawk@1.1.1: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated ejs@1.0.0: Critical security bugs fixed in 2.5.5
npm WARN deprecated pangyp@2.3.3: no longer maintained
npm WARN deprecated highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 607 packages, and audited 608 packages in 55s

14 packages are looking for funding
  run `npm fund` for details

54 vulnerabilities (5 low, 14 moderate, 26 high, 9 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.
➜  maupassant git:(master) ✗ npm install hexo-renderer-sass --save

up to date, audited 608 packages in 2s

14 packages are looking for funding
  run `npm fund` for details

54 vulnerabilities (5 low, 14 moderate, 26 high, 9 critical)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

hexo启动日志信息：
Error: Module did not self-register: '/Users/boy/Code/windanchaos.github.io/themes/maupassant/node_modules/node-sass/precompiled/darwin-x64/binding.node'.
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1210:18)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/Users/boy/Code/windanchaos.github.io/themes/maupassant/node_modules/node-sass/sass.js:11:13)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at req (/Users/boy/Code/windanchaos.github.io/node_modules/hexo/lib/hexo/index.js:292:23)
    at /Users/boy/Code/windanchaos.github.io/themes/maupassant/node_modules/hexo-renderer-sass/index.js:2:10
    at /Users/boy/Code/windanchaos.github.io/node_modules/hexo/lib/hexo/index.js:305:14
    at tryCatcher (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromise0 (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/promise.js:649:10)
    at Promise._settlePromises (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/promise.js:729:18)
    at _drainQueueStep (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/async.js:93:12)
    at _drainQueue (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/Users/boy/Code/windanchaos.github.io/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (node:internal/timers:466:21)

#517


text:
Get license code from transaction-id when storing school in ETH Ropsten blockchain

Just 4 fun if we have any time left

not enough time left


text:
Resizing

I am a beginner in Linux Mint (19.2 - Cinnamon).
I have TunePack and it works smoothly...downloaded plenty of songs.
Just one issue - I am not able to resize the window.
The tunepack window is slightly more vertical than my screen which block little bit of the window i cant access.

I also face the issue, I can not see the buttons fully at the bottom (only partially)

repo: tunepack/tunepack-desktop


text:
Support for Python 3.10 / 3.11?

PyPI only has wheels for Python 3.7-3.9. Would it be possible to publish wheels for newer versions?

Ping @LeonhardFS ?

Hi Erik,
we just published new wheels for Python 3.8 - 3.11 including Apple Silicon support for Python 3.9 - 3.11. Closing this issue for now with the release, if you encounter any problems please let us know and we'll do our best to address them swiftly.

authors: LeonhardFS ecederstrand

repo: tuplex/tuplex


text:
[Suggestion] Increase fission fuel consumption rate?

This mod is great but the one thing I find odd about it is the very low fuel consumption (once you build a good reactor you need hardly any fuel, no matter the size).
Are there any plans to make this into something like "1 fuel rod required per fuel cell block in the fission reactor?"
As it stands, a single fuel rod is enough to fully power even the largest reactors.  I find myself wanting it to work more like IC2 where efficiency is a huge factor but larger reactors still require more fuel.

It's a good suggestion... of course the issue with the 'one rod per cell block' system in this mod is that a player can change the number of cell blocks in the reactor at any point during a cycle, so I'd certainly have to take that into account.
Right now, all that happens for reactors with more cell blocks is that the fuel runs dry more quickly. So with either system, the rate of fuel consumption would be exactly the same.
Perhaps what I need to do then is just lower the base lifetimes of the fuels? If so, by how much should they be cut?

Hmm, I didn't realize that the number of cell blocks will increase the consumption rate of the one cell inside (I thought I found that didn't happen but that was in a much older version of the mod so it might have changed).  Is that linear?
The approach I am suggesting is, unfortunately, pretty complicated (since you somehow need to track/expose each fuel cell independently - works within the IC2 reactor design but this one doesn't lend itself to a similar approach).  I am not convinced that it can be done in a way which would preserve other aspects of the existing design (change reactor internals while fuelled) or make sense from a UI perspective (minimally, requires exposing partially-consumed fuel).
You might just want to make a consumption rate multiplier config file option so this can be tweaked from the outside (probably a good idea since the ore generation rates will be different when combined with different mods - since it is also up to the user/pack developer which mods generate potential fuel ores).

Yes, it is linear. The fuel consumption rate is the base rate multiplied by the number of cell blocks. And there already is a fuel consumption rate multiplier - an overall one, and one for each individual fuel also :)

Those should suffice for general usage (sorry I didn't notice the cell blocks increasing the consumption rate).  I will close this since any other action on this would be pretty "pie in the sky" and might break other approaches currently in place.


text:
Fix example query for table: net_connection

Describe the bug
Fix example query
https://hub-steampipe-io-git-staging-turbot.vercel.app/plugins/turbot/net/tables/net_connection > Test a TCP connection to steampipe.io on port 443
The below query is correct in the repo, however, it's rendered differently in hub with the condition as in
In .md file
select
  *
from
  net_connection
where
  protocol = 'tcp'
  and address = 'steampipe.io:443'

In Hub
select
  *
from
  net_connection
where
  protocol = 'tcp'
  and address in 'steampipe.io:443'

Steampipe version (steampipe -v)
Example: v0.3.0
Plugin version (steampipe plugin list)
Example: v0.5.0
To reproduce
Steps to reproduce the behavior (please include relevant code and/or commands).
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here.

Already addressed here

repo: turbot/steampipe-plugin-net


text:
Upload wheels to PyPI

Wheels (.whl) for this package are currently missing from PyPI. Could wheels be uploaded for the current and future releases?
Read more about the advantages of wheels to understand why generating wheel distributions are important.
To create a wheel along with source distribution:
(venv) $ pip install --upgrade pip setuptools wheel
(venv) $ python setup.py sdist bdist_wheel

# See dist/*.whl

To upload wheels:
(venv) $ pip install twine
(venv) $ twine upload dist/*

I did not realize wheels were useful for pure Python packages.  Thanks for the linked info.  I'll get that pushed tonight or tomorrow.

The wheel is up on PyPi now.  I'm planning on pushing a new version of the package once a month or so, just to keep rolling in the latest Swagger UI source files, and I'll make sure to do source & wheel distributions at the same time from now on.

Sounds great. Thanks!

authors: johnthagen turettn


text:
This app has become too bloated

This was a great app, but it has become too bloated for my use. It's trying to do too much and is trying to be everything to everyone. I'm back to using Speccy.

This was a great app, but it has become too bloated for my use. It's trying to do too much and is trying to be everything to everyone. I'm back to using Speccy.

Glow continues to evolve with each release. Even as the number of features grows, the program is more optimized and faster. What exactly is the problem?

authors: pelaird turkaysoftware

repo: turkaysoftware/glow


text:
Add support for generating build provider files

Addresses this issue.
Here's a quick demo...

LGTM. Just one comment about HCs. Can be a later feature. But would be nice if we could get that in on first release of this.

@jritsema yeah I agree. Right now it would potentially cause more issues than it would help. Go ahead merge this in.

authors: jkurz jritsema

repo: turnerlabs/harbor-compose


text:
ROS change suggestion

Please provide the following information:

OS: (. Ubuntu 22.04)
ROS Distro: (. HUMBLE)
Built from source

My turtlebot4 lite working on 20.04 and it was doing good i was able to drive it through laptop keyboard but after upgrade to 22.04 and remove galactic Ros the system won't be able to identify the Ros system downloaded which is humble please i want your recommendation if its good idea to format the SD card and  download Ubuntu 20.04 again with galactic or re-download Ubuntu 22.04lts with humble any other suggestion would be appreciated
Best regards
Ahmed

Hi @Hanbali11,
Can you please confirm that you upgraded both the turtlebot and your laptop to run 22.04 and ROS 2 Humble. If not, please update your laptop as well (or use a VM or docker container running Humble).
How did you go about updating the turtlebot? Did you use the images provided? if not please try again using the instructions and the provided image for Turtlebot Lite Humble

This issue is being closed due to inactivity. If you are still experiencing the issue, feel free to reopen this ticket when you are ready to continue the troubleshooting process.


text:
backends/libdile_vt: new capture backend

seems to work on webOS 3.8 / K3LP (where libvt capture didn't work)

FYI this is pretty much ready for merging. I added some minor changes when I were at it, can split them up into separate PRs or drop them completely if you want.

Looks great 👍 Will merge this now, then get TBSniller's changes in.
Thanks

authors: Informatic tuxuser

repo: tuxuser/hyperion-webos


text:
device seem to be unable to connect to AP

please help
Trying to run it on a lsc lamp with mcu 2.9.27, the script is setting up a AP named smartlife-234f that i can see on phone, pc , however it thus not connect to it , i did try the -r option to reset the network manager , no luck , is the anyone who can advice me on this ?
kurt@raspberrypi:~/tuya-cloudcutter $ sudo ./tuya-cloudcutter.sh -r -s thuis makeitso
Building cloudcutter docker image
[+] Building 4.3s (13/13) FINISHED                               docker:default
=> [internal] load .dockerignore                                          0.0s
=> => transferring context: 2B                                            0.0s
=> [internal] load build definition from Dockerfile                       0.1s
=> => transferring dockerfile: 460B                                       0.0s
=> [internal] load metadata for docker.io/library/python:3.9.12-slim-bus  1.8s
=> [base 1/2] FROM docker.io/library/python:3.9.12-slim-buster@sha256:83  0.0s
=> [internal] load build context                                          0.5s
=> => transferring context: 3.02kB                                        0.0s
=> CACHED [base 2/2] RUN apt-get -qq update && apt-get install -qy --no-  0.0s
=> CACHED [python-deps 1/4] RUN pip install --upgrade pipenv              0.0s
=> CACHED [python-deps 2/4] COPY src/Pipfile /src/                        0.0s
=> CACHED [python-deps 3/4] COPY src/Pipfile.lock /src/                   0.0s
=> CACHED [python-deps 4/4] RUN cd /src && PIPENV_VENV_IN_PROJECT=1 pipe  0.0s
=> CACHED [cloudcutter 1/2] COPY src /src                                 0.0s
=> CACHED [cloudcutter 2/2] WORKDIR /src                                  0.0s
=> exporting to image                                                     0.0s
=> => exporting layers                                                    0.0s
=> => writing image sha256:cfe4bb85910528b04f56aa9ee2de2c3a4f5fad044a44a  0.0s
=> => naming to docker.io/library/cloudcutter                             0.0s
Successfully built docker image
Loading options, please wait...
[?] How do you want to choose the device?: By firmware version and name
By manufacturer/device name

By firmware version and name
From device-profiles (i.e. custom profile)

[?] Select the firmware version and name: 0.0.2 - BK7231N / oem_bk7231n_light_st[?] Select the firmware version and name: 0.0.3 - BK7231N / oem_bk7231n_light_st[?] Select the firmware version and name: 0.0.6 - BK7231N / oem_bk7231n_strip_43[?] Select the firmware version and name: 1.0.0 - BK7231N / oem_bk7231n_ceiling_[?] Select the firmware version and name: 1.0.0 - BK7231N / oem_bk7231n_dltj_plu[?] Select the firmware version and name: 1.0.0 - BK7231N / oem_bk7231n_garage_d[?] Select the firmware version and name: 1.0.0 - BK7231N / oem_bk7231n_jiabitai[?] Select the firmware version and name: 1.0.0 - BK7231T / HYS_03_018_bk7231t_t[?] Select the firmware version and name: 1.0.0 - BK7231T / oem_bk7231s_dltj_1pl[?] Select the firmware version and name: 1.0.1 - BK7231N / bk_light_rgbcw_vpylf[?] Select the firmware version and name: 1.0.1 - BK7231N / oem_bk7231n_scene_sw[?] Select the firmware version and name: 1.0.1 - BK7231N / oem_bk7231n_strip_ff[?] Select the firmware version and name: 1.0.1 - BK7231T / HYS_03_010_RGB_soq7i[?] Select the firmware version and name: 1.0.1 - BK7231T / oem_bk7231s_1_plug_a[?] Select the firmware version and name: 1.0.1 - BK7231T / oem_bk7231s_light_mi[?] Select the firmware version and name: 1.0.1 - BK7231T / oem_bk7231s_ty_ffc_n[?] Select the firmware version and name: 1.0.10 - BK7231N / bk7231n_lowpower_co[?] Select the firmware version and name: 1.0.10 - BK7231N / oem_bk7231n_gate_ma[?] Select the firmware version and name: 1.0.10 - BK7231N / oem_bk7231n_light_p[?] Select the firmware version and name: 1.0.10 - BK7231T / oem_bk7231s_light_t[?] Select the firmware version and name: 1.0.14 - BK7231N / oem_bk7231n_slide_s[?] Select the firmware version and name: 1.0.15 - BK7231N / oem_bk7231n_slide_s[?] Select the firmware version and name: 1.0.18 - BK7231N / oem_bk7231n_slide_s[?] Select the firmware version and name: 1.0.2 - BK7231N / bk7231n_common_user_[?] Select the firmware version and name: 1.0.2 - BK7231N / oem_bk7231n_dctrl_sw[?] Select the firmware version and name: 1.0.2 - BK7231N / oem_bk7231n_strip_sl[?] Select the firmware version and name: 1.0.2 - BK7231T / HYS_03_010_RGB_xhsx0[?] Select the firmware version and name: 1.0.2 - BK7231T / bk7231t_common_user_[?] Select the firmware version and name: 1.0.2 - BK7231T / oem_bk7231s_2_plug_g[?] Select the firmware version and name: 1.0.2 - BK7231T / oem_bk7231s_control_[?] Select the firmware version and name: 1.0.2 - BK7231T / oem_bk7231s_dltj_tes[?] Select the firmware version and name: 1.0.2 - BK7231T / oem_bk7231s_light_mi[?] Select the firmware version and name: 1.0.2 - BK7231T / oem_bk7231s_rnd_zero[?] Select the firmware version and name: 1.0.2 - BK7231T / oem_bk7231s_strip_ke[?] Select the firmware version and name: 1.0.3 - BK7231N / oem_bk7231n_curtain_[?] Select the firmware version and name: 1.0.3 - BK7231T / oem_bk7231s_control_[?] Select the firmware version and name: 1.0.3 - BK7231T / oem_bk7231s_light_ty[?] Select the firmware version and name: 1.0.4 - BK7231N / oem_bk7231n_strip_li[?] Select the firmware version and name: 1.0.4 - BK7231T / oem_bk7231s_light4_4[?] Select the firmware version and name: 1.0.4 - BK7231T / oem_bk7231s_light_st[?] Select the firmware version and name: 1.0.4 - BK7231T / oem_bk7231s_ty_ffc_n[?] Select the firmware version and name: 1.0.5 - BK7231N / oem_bk7231n_dctrl_sw[?] Select the firmware version and name: 1.0.5 - BK7231N / oem_bk7231n_light_at[?] Select the firmware version and name: 1.0.6 - BK7231N / oem_bk7231n_strip_rg[?] Select the firmware version and name: 1.0.6 - BK7231T / oem_bk7231s_dltj_2sw[?] Select the firmware version and name: 1.0.6 - BK7231T / oem_bk7231s_fan_cont[?] Select the firmware version and name: 1.0.6 - BK7231T / oem_bk7231s_light_db[?] Select the firmware version and name: 1.0.6 - BK7231T / oem_bk7231s_rnd_swit[?] Select the firmware version and name: 1.0.6 - BK7231T / realme_BK7231T_plug_[?] Select the firmware version and name: 1.0.7 - BK7231T / oem_bk7231s_rnd_swit[?] Select the firmware version and name: 1.0.7 - BK7231T / oem_bk7231s_rnd_zero[?] Select the firmware version and name: 1.0.8 - BK7231T / oem_bk7231s_light2_p[?] Select the firmware version and name: 1.0.8 - BK7231T / oem_bk7231s_light_db[?] Select the firmware version and name: 1.0.8 - BK7231T / oem_bk7231s_rnd_swit[?] Select the firmware version and name: 1.0.8 - BK7231T / oem_bk7231s_ty_ffc_d[?] Select the firmware version and name: 1.0.9 - BK7231N / BL_RGBCW_LIGHT_12KEY[?] Select the firmware version and name: 1.0.9 - BK7231T / oem_bk7231s_ty_ffc_d[?] Select the firmware version and name: 1.1.0 - BK7231N / oem_bk7231n_curtain_[?] Select the firmware version and name: 1.1.0 - BK7231N / oem_bk7231n_dctrl_sw[?] Select the firmware version and name: 1.1.0 - BK7231T / HYS_03_018_bk7231t_q[?] Select the firmware version and name: 1.1.0 - BK7231T / HYS_03_018_bk7231t_t[?] Select the firmware version and name: 1.1.0 - BK7231T / oem_bk7231s_curtain_[?] Select the firmware version and name: 1.1.0 - BK7231T / oem_bk7231s_dltj_out[?] Select the firmware version and name: 1.1.0 - BK7231T / oem_bk7231s_light5_s[?] Select the firmware version and name: 1.1.0 - BK7231T / oem_bk7231s_rnd_swit[?] Select the firmware version and name: 1.1.1 - BK7231N / oem_bk7231n_ffc_remo[?] Select the firmware version and name: 1.1.1 - BK7231T / HYS_03_018_bk7231t_a[?] Select the firmware version and name: 1.1.1 - BK7231T / oem_bk7231s_light_ty[?] Select the firmware version and name: 1.1.11 - BK7231N / oem_bk7231n_temp_hu[?] Select the firmware version and name: 1.1.14 - BK7231T / oem_bk7231s_switch1[?] Select the firmware version and name: 1.1.17 - BK7231N / oem_bk7231n_temp_hu[?] Select the firmware version and name: 1.1.2 - BK7231N / oem_bk7231n_control_[?] Select the firmware version and name: 1.1.2 - BK7231N / oem_bk7231n_dimmer_k[?] Select the firmware version and name: 1.1.2 - BK7231T / oem_bk7231s_control_[?] Select the firmware version and name: 1.1.2 - BK7231T / oem_bk7231s_dltj_2sw[?] Select the firmware version and name: 1.1.2 - BK7231T / oem_bk7231s_hailai_1[?] Select the firmware version and name: 1.1.2 - BK7231T / oem_bk7231s_rnd_swit[?] Select the firmware version and name: 1.1.2 - BK7231T / oem_bk7231s_ty_ffc_d[?] Select the firmware version and name: 1.1.2 - BK7231T / oem_bk7231t_light3_l[?] Select the firmware version and name: 1.1.3 - BK7231T / oem_bk7231s_double_s[?] Select the firmware version and name: 1.1.3 - BK7231T / oem_bk7231s_irbox_mo[?] Select the firmware version and name: 1.1.3 - BK7231T / oem_bk7231s_switch_c[?] Select the firmware version and name: 1.1.4 - BK7231T / oem_bk7231s_dltj_2sw[?] Select the firmware version and name: 1.1.4 - BK7231T / oem_bk7231s_ty_ffc_d[?] Select the firmware version and name: 1.1.5 - BK7231N / oem_bk7231n_control_[?] Select the firmware version and name: 1.1.5 - BK7231T / oem_bk7231s_4_speed_[?] Select the firmware version and name: 1.1.5 - BK7231T / oem_bk7231s_rnd_zero[?] Select the firmware version and name: 1.1.6 - BK7231N / oem_bk7231n_water_se[?] Select the firmware version and name: 1.1.6 - BK7231T / oem_bk7231s_control_[?] Select the firmware version and name: 1.1.6 - BK7231T / oem_bk7231s_light_ff[?] Select the firmware version and name: 1.1.6 - BK7231T / oem_bk7231s_switch1_[?] Select the firmware version and name: 1.1.7 - BK7231N / CL_DREAM_RGB_STRIP_1[?] Select the firmware version and name: 1.1.7 - BK7231N / oem_bk7231n_ceiling_[?] Select the firmware version and name: 1.1.7 - BK7231T / oem_bk7231s_light_pi[?] Select the firmware version and name: 1.1.71 - BK7231T / bk7231t_common_user[?] Select the firmware version and name: 1.1.8 - BK7231T / oem_bk7231s_rnd_swit[?] Select the firmware version and name: 1.1.80 - BK7231T / bk7231t_common_user[?] Select the firmware version and name: 1.1.9 - BK7231N / oem_bk7231n_water_se[?] Select the firmware version and name: 1.1.9 - BK7231T / bk7231s_common_iot_c[?] Select the firmware version and name: 1.1.9 - BK7231T / oem_bk7231s_ceiling_[?] Select the firmware version and name: 1.1.9 - BK7231T / oem_bk7231s_strip_ir[?] Select the firmware version and name: 1.2.1 - BK7231N / oem_bk7231n_control_[?] Select the firmware version and name: 1.2.1 - BK7231N / oem_bk7231n_dctrl_sw[?] Select the firmware version and name: 1.2.16 - BK7231N / oem_bk7231n_light_t[?] Select the firmware version and name: 1.2.2 - BK7231N / oem_bk7231n_ceiling_[?] Select the firmware version and name: 1.2.21 - BK7231N / oem_bk7231n_light_t[?] Select the firmware version and name: 1.2.6 - BK7231N / oem_bk7231n_ceiling_[?] Select the firmware version and name: 1.2.8 - BK7231T / oem_bk7231_2onoff_we[?] Select the firmware version and name: 1.3.0 - BK7231N / kltwfb_single_winctr[?] Select the firmware version and name: 1.3.19 - BK7231N / oem_bk7231n_light_t[?] Select the firmware version and name: 1.3.2 - BK7231T / oem_bk7231s_ceiling_[?] Select the firmware version and name: 1.3.2 - BK7231T / oem_bk7231s_light_pi[?] Select the firmware version and name: 1.3.21 - BK7231N / oem_bk7231n_light_t[?] Select the firmware version and name: 1.6.0 - BK7231T / oem_bk7231s_curtain_[?] Select the firmware version and name: 2.0.0 - BK7231N / oem_bk7231n_irbox_mo[?] Select the firmware version and name: 2.0.0 - BK7231N / oem_bk7231n_smart_ir[?] Select the firmware version and name: 2.0.0 - BK7231T / oem_bk7231s_light5_s[?] Select the firmware version and name: 2.0.2 - BK7231N / bk7231n_common_user_[?] Select the firmware version and name: 2.0.3 - BK7231T / oem_bk7231s_light5_s[?] Select the firmware version and name: 2.0.5 - BK7231N / oem_bk7231n_smart_ir[?] Select the firmware version and name: 2.0.8 - BK7231N / oem_bk7231n_smart_ir[?] Select the firmware version and name: 2.1.0 - BK7231N / bk7231n_lowpower_com[?] Select the firmware version and name: 2.1.1 - BK7231T / HYS_03_018_bk7231t_r[?] Select the firmware version and name: 2.1.6 - BK7231N / bk7231n_common_user_[?] Select the firmware version and name: 2.3.5 - BK7231N / Zhimei_WiFi_smart_me[?] Select the firmware version and name: 2.9.12 - BK7231T / oem_bk7231s_light_t[?] Select the firmware version and name: 2.9.15 - BK7231T / oem_bk7231s_light_t[?] Select the firmware version and name: 2.9.16 - BK7231T / oem_bk7231s_light_t[?] Select the firmware version and name: 2.9.25 - BK7231T / oem_bk7231s_light_t[?] Select the firmware version and name: 2.9.27 - BK7231T / oem_bk7231s_light_ty  2.1.1 - BK7231T / HYS_03_018_bk7231t_r1e1zch4rds9ypqq
2.1.1 - BK7231T / HYS_03_018_bk7231t_r1e1zch4rds9ypqq
2.1.6 - BK7231N / bk7231n_common_user_config_ty
2.2.4 - BK7231N / ele_1switch
2.3.5 - BK7231N / Zhimei_WiFi_smart_meter_main
2.9.12 - BK7231T / oem_bk7231s_light_ty
2.9.15 - BK7231T / oem_bk7231s_light_ty
2.9.16 - BK7231T / oem_bk7231s_light_ty
2.9.25 - BK7231T / oem_bk7231s_light_ty

2.9.27 - BK7231T / oem_bk7231s_light_ty
2.9.3 - BK7231T / oem_bk7231s_light_ty
2.9.6 - BK7231T / oem_bk7231s_light_ty
7.0.0 - BK7231T / oem_bk7231s_dltj
7.0.2 - BK7231N / Klarstein_Wonderwall_Smart

[?] Select the brand of your device: LSC

LSC

[?] Select the article number of your device: 2578539 970719 RGBCT Bulb 2.9.27

2578539 970719 RGBCT Bulb 2.9.27

Performing safety checks to make sure all required ports are available
Checking UDP port 53... Available.
Checking UDP port 67... Available.
Checking TCP port 80... Available.
Checking TCP port 443... Available.
Checking TCP port 1883... Available.
Checking TCP port 8886... Available.
Safety checks complete.
Selected Device Slug: lsc-2578539-970719-rgbct-bulb-2.9.27
Selected Profile: oem-bk7231s-light-ty-2.9.27-sdk-2.3.2-40.00
================================================================================
Place your device in AP (slow blink) mode.  This can usually be accomplished by either:
Power cycling off/on - 3 times and wait for the device to fast-blink, then repeat 3 more times.  Some devices need 4 or 5 times on each side of the pause
Long press the power/reset button on the device until it starts fast-blinking, then releasing, and then holding the power/reset button again until the device starts slow-blinking.
See https://support.tuya.com/en/help/_detail/K9hut3w10nby8 for more information.
Wiping NetworkManager configs
Scanning for open Tuya SmartLife AP
............................................................................................................................................................................^CError: nmcli terminated by signal Interrupt (2)
kurt@raspberrypi:~/tuya-cloudcutter $

update : please close , a complete reboot of the box did the trick

repo: tuya-cloudcutter/tuya-cloudcutter


text:
fix(Popup.list): When Popup.list is set to subtitle, it cannot be dis…

Description
When Popup.list is set to subtitle, it cannot be displayed normally.
Type of change
Please select the relevant option.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Codecov Report

Merging #125 (bf0670c) into master (2e8e09f) will decrease coverage by 0.04%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
- Coverage   90.77%   90.73%   -0.05%
==========================================
  Files         155      155
  Lines        7375     7380       +5
  Branches     2026     2026
==========================================
+ Hits         6695     6696       +1
- Misses        559      563       +4
  Partials      121      121

Impacted Files
Coverage Δ

...ckages/tuya-panel-kit/src/components/popup/list.js
74.44% <71.42%> (-3.21%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: ZengBeauty codecov-commenter

repo: tuya/tuya-panel-kit


text:
🛑 KKK is down

In 25da541, KKK (https://www.kkk.tsk.tr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KKK is back up in 15648e2.

repo: tuz-z/upp


text:
IOS调用微信APP支付时，返回支付验证签名失败

用的是 createUnifiedOrder 返回的sign，然后在ios中调用微信支付。微信提示支付验证签名失败。。。
请问大神有遇过这种情况么。。。。

@luchenwei9266 working on v2.0

repo: tvrcgo/weixin-pay


text:
建议：Twitter的两个使用不便的地方

Search before asking

[X] 我在 issues 列表中搜索，没有找到类似的内容。
I searched in the issues and found nothing similar.

Motivation

找不到“我的书签”，不知道是什么原因把书签入口给去掉了。
Twitter视频无法全屏

Solution
No response
Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

下一个版本安排