Error while initializing app DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.     at Object.We [as appendChild]

I have an error
 Error while initializing app DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
    at Object.We [as appendChild]

nuxt  "version": "1.0.0",
I do  npm run build and npm run start.

I have the same error, with generated static after a yarn generate in the console dev, but the page appears to be displayed correctly.
    at Object.Qe [as appendChild] (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:23837)
    at p (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:51346)
    at u (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:50597)
    at h (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:51429)
    at k (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:54374)
    at k (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:54311)
    at a.t.nodeOps [as __patch__] (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:54908)
    at a.t._update (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:43512)
    at a.r (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:10997)
    at io.get (http://mydomain.com/_nuxt/common.b4c86636141262f1c64f.js:2:39746)
(anonymous) @ client.js:37
Promise rejected (async)
T23V @ client.js:36
n @ bootstrap<PHONE_NUMBER>678a4ce7b3:54
window.webpackJsonp @ bootstrap<PHONE_NUMBER>678a4ce7b3:25
(anonymous) @ app.8b23d36a19073197491e.js:1```

I have the same error. The interesting thing is that the error is only created upon reloading the page, or else invoking the url. AND only upon doing npm run build and npm start, it never occurs under npm run dev. So to reproduce the error, I need to build and do npm start, then reload the offending page (or else invoke its url directly in the browser).
It is a long text containing html and I am using the v-html directive.

I have this error with yarn start after build. yarn run dev is work fine.  yarn generate has not tried.
It looks like a
<nuxt-link to=“/user/my”>link</nuxt-link>

rendered TextElement that tries to add a child node.

@Atinux can you help with this, have the same error ...

@yoyo837 can you try
<nuxt-link to=“'/user/my'”>link</nuxt-link>

(see the single quotes inside the link)

I'm experiencing the same issue.
I tried what you proposed, @vuchl and it gave me the same error.
With the issue specific to <nuxt-link> I managed to fix it by adding a trailing slash to the link.

I'm also experiencing this issue. I managed to (partially) fix the issue by adding trailing slashes to URLs, but it's still broken.
Here's the repo
Here's the live site
To reproduce the error, visit this page directly. The site works fine on all the other pages. The site also works fine if you navigate to that page from any other page on the site.
There are two issues here (that I think are related):

You'll see that the sidebar doesn't get loaded. It does when you visit the home page and then navigate to that page, though.
There will be a brief flash of text on reload. Specifically where it says "A helper tool for keeping..." at the 3rd paragraph down, not the sub-header. It will flash for a second and say "The tricky part of the game...".

The weird part is that the text that flashes at first is correct. It then gets replaced with old text that doesn't exist anywhere. If I do a full search of my entire project directory in my IDE, the only place that text shows up is in .nuxt and then again in dist/_nuxt after I do yarn generate. It's literally nowhere else.
I've tried deleting my entire .nuxt, dist, and node_modules directory, running yarn to fully reinstall everything, and then yarn generate to generate the static site. Same error.

I'm also experiencing this error on this page:
<template>

Greylore Portal

    <form @submit.prevent="login">

{{ loginError }}

Email: <input type="email" v-model="loginEmail" name="email">

Password: <input type="password" v-model="loginPassword" name="password">

      <button type="submit">Enter</button>
    </form>

Welcome, {{ $store.state.authUser.username }}!

    <button @click="logout">Exit</button>

</template>

It only occurs when I have successfully logged in and then I refresh the page (refresh on no authUser results in cleanly rendering the v-if section).
Also, I get a slightly different error when I "npm run dev". Instead of the posted error, I get a [vue warn] about the virtual DOM, and a subsequent error about not being able to call .toLowerCase on something during app initialization.

 #1552

Another update, this issue is caused by Cloudflare for me. I've tried a lot of things and one of the last differences with my local server was Cloudflare. I've disabled Auto Minify for javascript and everything worked

Hi,
This bug was due to generate.minify.collapseWhitespace which was true by default, it will be false by default in 1.0 (next release).
in the meantime, to fix this issue, you can add in your nuxt.config.js:
generate: {
  minify: {
    collapseWhitespace: false
  }
}

Hi
I'm still watching this error
Changing options generate.minify not solve the problem

i am getting this error as well. It works perfectly in localhost but when i host the dist/ it has this error.

Same error for me also, it works perfectly on localhost but got occasionally Failed to execute 'appendChild' on 'Node' on server

Also getting this error. Works fine on localhost but geneated files served from dist break. Error is totally random as I can do a build and sometimes the exact same code works

If you are still having this issue it may be caused by a problem like Mismatching childNodes vs. VNodes in development that you didn't control. For me was a vuetify's v-btn inside a p tag. I changed the
 for a
. And that made the favor.

same issue here. changed v-if with v-show and the issue was solved...

        <router-link :to=item.scrollTo v-scroll-to="item.scrollTo" class="link">{{ item.label }}</router-link>

    computed: {
        currentPage: function() {
            return this.$nuxt.$route.name
        }
    },

[nuxt] Error while initializing app TypeError: n.setAttribute is not a function

It's occured even after fresh Nuxt project install and run "yarn nuxt generate" (same thing happen on npm run)
Problem doesn’t appear on "yarn/npm run dev"
npm 5.7.1
yarn 1.0.2
node v8.10.0
vue/cli 3.0
Nuxt 1.4.0
macOS High Sierra

@jhwh seems like a completely different issue. Try starting with one of the templates:
https://github.com/nuxt-community/awesome-nuxt#starter-template
I'm using nuxt-community/express and just updated to<EMAIL_ADDRESS>and all seems good for me.
I'd also suggest to start a new issue providing a demo (You can try https://codesandbox.io/) or a repository.
Sorry for the inconveniance.

In my case, the issue is caused by v-if on a v-for loop. The v-if generates a comment when not to be rendered. And a Vue-Warning saying mismatching virtual nodes and DOMs maybe becasuse the comment is recognized as a DOM. Changing v-if to v-show solved my issue.

Preventing this kind of errors/warnings is actually not easy at the moment. This has happened to me also with comments not included by me. But I think that it is something more related to Vue itself. It may have to be with the synchronicity of the diffing and the rendering or reconciliation algorithm (if there's actually such a thing in vue). It's what comes to my mind, having this solved by switching to v-show...

Faced the same problem, found a not very good solution, but as a temporary crutch can be someone help.
If you set the boot flag and after a second, for example, change it in the creation hook, the error can be avoided.
  export default {
     data: () => ({
       loading: true
     }),
     created () {
       setTimeout (() => {
         this.loading = false
       }, 1000)
     }
  }

<template>

    // the elements that cause the error: DOMException: Failed to execute 'appendChild' on 'Node'

</ template>

Update the last answer: now I checked, you can replace the
setTimeout (() => {
    this.loading = false
}, 1000)

as
this.$nextTick(function () {
    this.loading = false
})

In my case, I deleted the index.vue of pages directory and added extendRoutes to nuxt.config.js, extendRoutes code like this:
// redirect default route to 'pc' directory
     routes.forEach(item => {
        if (item.path === '/pc') {
          item.path = ''
        } else if (item.chunkName.includes('pages/pc/')) {
          item.path = item.path.replace('/pc/', '/')
        }
      })

then I got this problem in my homepage or refresh my homepage. finally I added a empty index.vue file to pages directory and make it right.  just for reference only.

OUCH. Same error occurring only in generated project, no sign of any error in dev.
Tried SmelayaPanda's solution, but didn't help.
I ultimately had to work my way through dismantling all manner of things in the project until I found for whatever reason that my use of FontAwesomeIcon in multiple components was the culprit. Stripped out all of the font-awesome-icon instances, but the problem persisted until I yanked the plugin loading FontAwesomeIcon globally. Much better now, even if my app now needs a lot of visual surgery.
This was a monster project I've been working on for a couple of months in dev, should have tried to deploy much earlier in the lifecycle. Hope others learn vicariously from my poor judgement there.
Regardless, this error seems to have several manifestations, and it's virtually impossible to diagnose sensibly in production builds. Since it only occurs in production builds, that's pretty frustrating. Not clear still if this is a Vue or Nuxt centric issue, but it doesn't feel like this issue should have been closed.

minify 并不能解决 ， 感觉学习成本太大了

After I uploaded the annotated code to the server, I found that the bug might have been caused by dom operations using third-party plug-ins. I'm using mintui's loadmore. After I removed this component, the whole project ran。
我在不断的注释代码上传到服务器后，发现这个bug可能是使用第三方插件的dom操作导致的。我使用的是mintui 的loadmore。我把这个组件删除后，整个项目运行起来了

I have the same issue after call nuxt generate. The nuxt generate worked for the last 5 moths, but nuxt it gives me this error. I opened a question on [SO] with details, configurations and error (https://stackoverflow.com/questions/51523704/nuxt-generate-failed-to-execute-appendchild-on-node).

Hello @jscheller !
I have same problem with FontAwesomeIcon, did you find any solution?

I wound up going through a few iterations on my FontAwesome plugin file and configuration, but I did get things working... I have a file 'font-awesome.js' in the 'plugins' folder in my project that looks like this...
import fontawesome from "@fortawesome/fontawesome";
import FontAwesomeIcon from "@fortawesome/vue-fontawesome";
import Vue from "vue";

import {
  faExpandArrows, faExpandAlt, faCompressAlt, faTimes
} from "@fortawesome/fontawesome-pro-regular";

import {
  faBars, faTimesSquare, faPlusSquare
} from "@fortawesome/fontawesome-pro-light";

import {
  faFacebookSquare, faTwitterSquare, faGooglePlusSquare
} from "@fortawesome/fontawesome-free-brands";

fontawesome.library.add(
  faTimes, faExpandArrows, faExpandAlt, faCompressAlt, faTimes,
  faBars, faTimesSquare, faPlusSquare,
  faFacebookSquare, faTwitterSquare, faGooglePlusSquare
);

Vue.component("fa-icon", FontAwesomeIcon);

...and then in my nuxt.config.js, that file is incorporated like this...
plugins: [
    {src: '~/plugins/font-awesome' },
  ],

...and the WebPack configuration is setup to tree shake the FontAwesome files, again in nuxt.config.js...
build: {
    analyze: true,
    extend(config, ctx) {

      config.resolve.alias["@fortawesome/fontawesome-free-brands$"] =
<EMAIL_ADDRESS>
      config.resolve.alias["@fortawesome/fontawesome-pro-regular$"] =
<EMAIL_ADDRESS>
      config.resolve.alias["@fortawesome/fontawesome-pro-light$"] =
<EMAIL_ADDRESS>
    }
  },

With all of that in place, I can include corresponding FontAwesome icons in my templates like this...
<fa-icon v-show="!isZoomed"  @click="expandClick"  fixed-width :icon="['far', 'expand-alt']"/>
I'm still not 100% sure what I was doing wrong originally, but went through a lot of gyrations with no-ssr and other mystic incantations before a couple of folks on Discord pointed me this way. Hope it helps...

@SmelayaPanda 方法有效

Any movement on this? I'm seeing this even in a recent nuxt-edge (2.0.0-25594102.4311aca)

Error while initializing app DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
I am also getting this error can anyone help me with this.

@nishantsinghchandel try to defer rendering of problematic components or html elements to the created hook as @SmelayaPanda suggested.

@NishantSinghChandel Take a look at all your v-if's...  Make sure that your are not trying to do any DOM updates to DOM nodes that are not present due to the condition of a v-if... Use v-show to get around this if possible

I'm also experiencing this issue. The weird thing is, if I clear the complete browser cache. The error is gone after a complete refresh.

@Timkor It may related to auth cookie.
I just found that the error occur when I use nuxt-auth with bootstrap-vue's navbar.
appendChild error:

    Profile
    Register
    Login

it works:
<no-ssr>

        Profile
        Register
        Login

</no-ssr>

If anybody else has this issue, You'd better check if there is at least one child in some specific component(You can search 'v-if' keyword in your project). I think it not related to nuxt issue.

@lokielse You could also use v-show instead... So that there are always DOM nodes no matter what the state of the variable

Hi, I am also getting this error on production sometimes. And its gone after a refresh. It never happened on my local development environment. The site normally looks okay in this condition but nothing works until I do a page refresh. This is the stacktrace it generates
[nuxt] Error while initializing app DOMException: Failed to execute 'appendChild' on 'Node': This node type does not support this method.
at Object.appendChild (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:223305)
at h (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:238530)
at c (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:238164)
at m (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:238613)
at T (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:241900)
at T (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:241835)
at T (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:241835)
at T (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:241835)
at T (https://example.com/_nuxt/vendor.3478ce27cf196047ba1b.js:2:241835)

This error is so random and gone after a refresh, I can not even debug it properly or have any Idea what causes this.

@iamsayantan I kindly invite you to upgrade to nuxt@v2+ ;). I haven't had this problem ever since.

@gangsthub yes I am using version 1.0.0. And 2.0 release notes states there is no breaking changes so I'd  upgrade nuxt and lookout for this issue. Thank you.

In my case, even if I upgrade the nuxt version to 2.1.0, the problem still occurs. it's related on bad html nesting block. I'm using vuetify 1.2.6 and the problem disappear if I remove the router on the sidebar <v-list-tile /> option tag. So, I think is an html problem. I tried to nuxt generate a new blank vuetify project and the problem doesn't appear.

I ran into this using Nuxt 2.2.0. I managed to drill down and find the piece of code that was causing the problem...
ol
  li(v-if="isAuthenticated")
    nuxt-link(to="/profile") {{ loggedInUser.name }}
  li(v-if="isAuthenticated")
    a(@click="logout") Logout

There were other list items above these that also had v-if on them, but for some reason, these two appearing together caused the error. The error only happened on production, which added to the fun.
I tired reformatting them a million ways but no luck. I tried a few of the fixes above but the only one that worked was @lokielse's fix.
no-ssr
  ol
    li(v-if="isAuthenticated")
      nuxt-link(to="/profile") {{ loggedInUser.name }}
    li(v-if="isAuthenticated")
      a(@click="logout") Logout

@danchristian its most likely because isAuthenticated on server have different value that on client

@aldarund I can do the following just fine though:
ol
  li(v-if="isAuthenticated")
    nuxt-link(to="/") Home

I ran into this problem yeterday with Nuxt version "nuxt": "^2.4.0". When testing my app online on Heroku I saw this error:
[nuxt] Error while mounting app: HierarchyRequestError: Failed to execute 'appendChild' on 'Node': This node type does not support this method.

In my case I use the universal mode, don't know if that is one of the reasons. I found out the problem was the v-if in one of my components by debugging locally by using npm run build and npm run start (if someone knows a quicker way please let me know).
I changed the v-if to v-show as mentioned above and that worked for me.
Code before

 1 && favoriteListLength < maximumList">
    You can add {{ maximumList - favoriteListLength }} more Pokémon

 9">
    Your list is full!

 9">
    Do you want to
    <button class="nes-btn is-error" @click="emptyFavoritePokemonList">
    Delete
    </button>
    the list?

...

  computed: {
    favoriteListLength() {
      return this.stateFavoritePokemonList.length
    }
  },

Code after

    You can add {{ maximumList - favoriteListLength }} more Pokémon

 9">
    Your list is full!

 9">
    Do you want to
    <button class="nes-btn is-error" @click="emptyFavoritePokemonList">
    Delete
    </button>
    the list?

...

  computed: {
    favoriteListLength() {
      return this.stateFavoritePokemonList.length
    },
    morePokemonCanBeAdded() {
      return (
        this.favoriteListLength > 1 &&
        this.favoriteListLength < this.maximumList
      )
    }
  },

It is good to mention here that using a computed property in v-if also did not resolve the error.

i am getting this error as well. It works perfectly in localhost but when i host the dist/ it has this error.
Changing options generate.minify not solve the problem

excuse me, is your problem solved? i also encountered this situation

i am getting this error as well. It works perfectly in localhost but when i host the dist/ it has this error.
Changing options generate.minify not solve the problem

@lanbau  excuse me, is your problem solved? i also encountered this situation.

@icemirror if u are using cloudflare u need to disable html minifcation on their side

I struggled with this issue and found my root cause:
export default {
data: () => ({
loading: true
}),
created () {
this.$nextTick(function () {
this.loading = false
})
}
}

    // the elements that cause the error: DOMException: Failed to execute 'appendChild' on 'Node'

Faced the same problem, found a not very good solution, but as a temporary crutch can be someone help.

Lost a day on this issue. In the end it was some weird problem with vuex-persistedstate, changed to vuex-persist and now v-if works as it should etc etc.

Faced the same problem, found a not very good solution, but as a temporary crutch can be someone help.
 Tried to change the v-if to v-show to see if the page would mount in the background and change the status on mounted.
`

`

I can't seem to reproduce it consistently but it generally happens the first time I load after I push some large changes to production. Happens once on every device until I refresh the page. Upgraded to<EMAIL_ADDRESS>and didn't help.
Any ideas?

I struggled with this issue and found my root cause:
  export default {
     data: () => ({
       loading: true / false
     })
  }

<template>

    // the elements that cause the error: DOMException: Failed to execute 'appendChild' on 'Node'

   // you have to put an empty div inside the template, otherwise in a few cases you could have an empty template which triggers this error

</ template>

@CsabaSzabo I found that v-if="false" resulted in an empty comment  there, which could be the reason of this error. An emtpy
 will repalce  with

, and everything works well.

Same thing here. Tried to change the v-if to v-show to see if the page would mount in the background and change the status on mounted.

I can't seem to reproduce it consistently but it generally happens the first time I load after I push some large changes to production. Happens once on every device until I refresh the page. Upgraded to<EMAIL_ADDRESS>and didn't help.
Any ideas?

Got it working by replacing the v-show by v-if and smoothing the page construction with a transition.
    <transition name="fade" mode="out-in">

    </transition>

Still, this race condition seems fairly arbitrary.

I've created a minimal reproduce repo here: https://github.com/meteorlxy/vuepress-appendchild-error
I met this problem in VuePress, but I think it's the same cause.
Here are some of the workarounds and the possible explainations:

@unwrittenmike's workaround, changing v-if to v-show. v-show will render the element with display: none, rather than .
@SmelayaPanda's workaround, setting the flag in created hook. created hook will be executed by server-renderer, so that it v-if block will be server-rendered, rather than .
@CsabaSzabo's workaround, putting an empty v-else element. This will render an empty element rather than .

@icemirror if u are using cloudflare u need to disable html minifcation on their side

thanks : D

@icemirror if u are using cloudflare u need to disable html minifcation on their side

@aldarund  thanks : D,  i had solved that problem

I'm having a hard time fixing this issue.
For me it appears once deployed (with nuxt build npm run build) when there is already a cached version in the browser. Once all data cleared it works like a charm 🤔
Any suggestions? Could it be because of a caching issues?

For me, the problem was caused by incorrect html nesting.
I had a component with a named slot
// custom component
<template>

    <slot name="title"></slot>

</template>

And i mistakenly nested another h1 tag within it
<custom-component>

This is a title

</custom-component>

To solve this, avoid illegal html syntax. Use a template or span tag in the slot instead. And avoid putting div tags within p tags.
<custom-component>
  <template slot="title">This is a title</template>
</custom-component>

 solved this for me... just wrapped the offending code and problem gone.

For me the error was caused by the login/logout buttons on initial page load in the header components, my code was like this:
login
logout
I've change to v-if and v-else and the error is gone, So keep in mind v-if on initial page load without a v-else going to cause that error, you can also use v-show that remove the error as well.

For me, it seems to be caused by the

 tag that nuxt inserts by default. I was trying to remove everything from the generated HTML and put the code back bit by bit, but as soon as I hit the second div tag, the error popped up.
Changing from this

to this

causes the error. Any ideas why? I don't even have v-if in my code.

no-ssr component in Vue solved this for me... just wrapped the offending code and problem gone.
For nuxt 2.9+ needed to use client-only, this helped

I had several times the same issue and it resulted in the fact that I had a v-if and a v-show on the same element. Hadn't noticed because the implementation came from part of a template I used.
Anyway, careful with your v-if in general. I always add an empty div with a v-else when I use it too.

I have the same issue.
Wrapv-if inside no-ssr work. But because of this I wrapped a great part of my code.
So what is the point of using nuxt ssr?

For me as many others, this is only happening on my production machine with nuxt generate - I can't debug it on my local machine. It's taking ages for the generate command to complete. I'm going nuts! Hope we get an easier way to avoid this in the future releases of nuxt.

I'm also getting this error with nuxt generate. I can reproduce it locally and it is definitely related to using the $auth plugin.

Wrapping the entire nav in <no-ssr> fixed it for me: https://github.com/nuxt/nuxt.js/issues/1552#issuecomment-425075526
Weird - only made it through trial and error for about 3 hours, but ok.

 I added this dummy index.html so nuxt generate would generate i18n root routes for the other languages.
When I removed the index.html under the pages/index directory the error went away.
I then solved the generate routes issue by manually adding the necessary routes to the generate.routes option in nuxt.config.js.
Hope this helps someone else.

A small guide on how to deal with this error (result of failing hydration)

I am using npx create-nuxt-app and then I can run the site using npm run dev, however as soon as I use npm run generate with the complete vanilla default nuxt website, it doesn't work when I open the index.html in the browser :(
Probably on my 12th hour of trying everything on the web, anybody got any ideas?

Run into the same problem. In my case, it was a form using Netlify forms. It was detected by Netlifys' deploy logic and enhanced plus a hidden field was updated. As this was not present during Nuxt generation, Nuxt failed at processing the form's HTML. My workaround was adding this hidden field directly in my code, and then the prob was gone.

same error. After signing in, none of the pages work.Even if you refresh the current authenticated home page, it does'nt work and gives the same error.Everything works in local though.
Someone please help. It's been over a day!

setting the login property under redirect to false in nuxt.config.js solved the error in my case.
I must say the docs were a bit misleading.

I have found another potential solution. I was using generate, then using the markup provided in another existing web based system. I find that it only works if you host the output HTML on the same route for which it was generated. So if you use it on profile/info in your other website, you need to use the same route in Nuxt for it to work.

This error can be really painfull to debug. In order to quickly get the element causing an issue edit node_modules/vue/dist/vue.esm.js and add the following lines :
// Search for this line:
function hydrate (elm, vnode, insertedVnodeQueue, inVPre) {
    var i;
    var tag = vnode.tag;
    var data = vnode.data;
    var children = vnode.children;
    inVPre = inVPre || (data && data.pre);
    vnode.elm = elm;

    // Add the following lines:
    console.log('elm', elm)
    console.log('vnode', vnode)
    console.log('inVpre', inVPre)
    // ...

You will get in the console the failing node.

I had a similar issue, that was happening due to v-if, v-else. I changed both to v-show & it resolved the issue.
However, the pattern that created the problem is rather common, so it'd be really nice to know how to handle such situations properly.
Consider you have 2 menus, one for desktop version & another for mobile version inside some controller:
<template>

        <TheDesktopNavigation v-if="isDesktop" />
        <TheMobileNavigation v-else :open="isMobileMenuOpen" />

</template>

My isDesktop initially was something like this:
methods: {
    isDesktop() {
        return window.matchMedia('(min-width: 768px)').matches
    }
}

however, Nuxt reasonably complained that it cannot find any window object in Node.js environment, so, I had to re-write the method like this:
methods: {
    isDesktop() {
        if (process.client) {
            return window.matchMedia('(min-width: 768px)').matches
        }
        return false
    }
}

Now there's obviously a mismatch between server-side rendered version & client-side rendered version, since TheMobileNavigation is always rendered on server.
The best solution here is probably to wrap it in <client-only>. However, in this particular case it could greatly affect SEO. Is there any kind of common workaround for that?

For some reason
 doesn't seem to support v-if on hydration after a nuxt generate.
It works when running SPA or Universal.
Error has gone away after I removed the

{{myObj.myStringProperty}}

For reference, this is what I was seeing:

Run into the same problem. In my case, it was a form using Netlify forms. It was detected by Netlifys' deploy logic and enhanced plus a hidden field was updated. As this was not present during Nuxt generation, Nuxt failed at processing the form's HTML. My workaround was adding this hidden field directly in my code, and then the prob was gone.

I'm running into the same problem due to Netlify Forms. However, adding the hidden field directly in my code hasn't solve my problem.

Run into the same problem. In my case, it was a form using Netlify forms. It was detected by Netlifys' deploy logic and enhanced plus a hidden field was updated. As this was not present during Nuxt generation, Nuxt failed at processing the form's HTML. My workaround was adding this hidden field directly in my code, and then the prob was gone.

I'm running into the same problem due to Netlify Forms. However, adding the hidden field directly in my code hasn't solve my problem.

I was running into the same problem when deploying on Netlify, even though I wasn't using Netlify Forms. I suspect it's because of the way Netlify transforms html during the deploy step. There were no issues when the site was statically built and served somewhere other than Netlify.
I worked around this issue by wrapping the offending <form>-containing component with <client only></client-only>.

Run into the same problem. In my case, it was a form using Netlify forms. It was detected by Netlifys' deploy logic and enhanced plus a hidden field was updated. As this was not present during Nuxt generation, Nuxt failed at processing the form's HTML. My workaround was adding this hidden field directly in my code, and then the prob was gone.

I'm running into the same problem due to Netlify Forms. However, adding the hidden field directly in my code hasn't solve my problem.

I was running into the same problem when deploying on a statically-generated Nuxt app on Netlify, even though I wasn't using Netlify Forms. I suspect it's because of the way Netlify transforms html during the deploy step. There were no issues when the site was statically built and served somewhere other than Netlify.
I worked around this issue by wrapping the offending <form>-containing component with <client only></client-only>.

Nice @NWRichmond , You saved my mid-night work.
I have add <clent-only> wrapping the <form> and It's work fine for me.

Locking here as explained in https://github.com/nuxt/nuxt.js/issues/5800#issuecomment-634514110.


again the error: [ngx_pagespeed <IP_ADDRESS>-0] PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches fully successful; is fetching working?

Hi again here, but I write to find a solution to this error:
2018/05/17 11:17:16 [error] 1731#5159: [ngx_pagespeed <IP_ADDRESS>-0] PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches fully successful; is fetching working?
2018/05/17 13:05:20 [error] 1731#5159: [ngx_pagespeed <IP_ADDRESS>-0] PageSpeed Serf fetch failure rate extremely high; only 0 of 44 recent fetches fully successful; is fetching working?
2018/05/17 17:56:56 [error] 1731#5159: [ngx_pagespeed <IP_ADDRESS>-0] PageSpeed Serf fetch failure rate extremely high; only 0 of 89 recent fetches fully successful; is fetching working?
this is my current configuration:
listen 443 ssl http2;
server_name myapp.domain.com
pagespeed on;
pagespeed FetchHttps enable;
pagespeed FileCachePath /var/ngx_pagespeed_cache;
pagespeed EnableFilters rewrite_css;
pagespeed EnableFilters fallback_rewrite_css_urls;
pagespeed EnableFilters combine_css;
location ~ ".pagespeed.([a-z].)?[a-z]{2}.[^.]{10}.[^.]+" { add_header "" ""; }
location ~ "^/ngx_pagespeed_static/" { }
location ~ "^/ngx_pagespeed_beacon" { }
pagespeed LoadFromFile "https://www.domain.com" "/var/www/webapp/";
pagespeed LoadFromFileRuleMatch disallow .;
pagespeed LoadFromFileRuleMatch allow .(ico|pdf|swf|eot|woff|ttf|otf|css|js|jpeg|jpg|png|gif|svg|svgz|mpg|mpeg|mp3|m4a|m4v|mp4|ogg|wmv|mov|mng|3gpp|3gp|webp|webm|flv|avi|asx|asf)
(?.)?$;
I hope a little help, I'm not an expert in pagespeed :)

In https://github.com/apache/incubator-pagespeed-ngx/issues/1562#issuecomment-389434823 @Lofesa said:
pagespeed LoadFromFileRuleMatch disallow .*; is the rigth statement to disallow all files.

It looks like you didn't try that?

hi, I have it in my configuration, here is omitting the asterisk , look:

Hi
I use letsencrypt too b but the ssl config diectives I use the standar ssl that comes with centos.
I see in your error log that none of the fetches are rigth, that make me think is a missconfiguration.
What happend when you try the /?PageSpeedFiltes=+debug (you need to look at the generated html code)?

Hi Lofesa , you recommend me to put this configuration and remove the one from letsencrypt:
pagespeed SslCertDirectory / etc / pki / tls / certs;
pagespeed SslCertFile /etc/pki/tls/cert.pem;
I can not find the correct syntax to debug?

Yes, if these paths are valid for your distro, for me are ok on a centos 7.
For debug pagespeed, in your browser you can add these params, like
https://www.mydomain.com/?PageSpeedFilters=+debug
and then look at the generated html code. You can see some debug messages in it.

Hi Lofesa , I made the change, I'm also using centos 7, debug mode I see many 404 or files that do not exist, I think you have to debug the page and remove links that do not exist.
Is the debug correct?

Yes, these are the ok params but you need to look not at the network tools on chrome. You need to rigth click on the page and choose to view the html code to see pagespeed debug messages.
As I can see you use spanish names to image files:
Clica con el boton derecho del raton sobre la pagina, en el menu que se despliega elige "Ver codigo fuente de la pagina". Los mensajes de debug los veras en verde.

ok , look the debug message:

what do you think of those messages?
regards !

Well, these messages are saying that the resources headers don´t let pagespeed rewrite these resources.
Or the resources are getting a 404 not found or the resources have a header that are not public cacheable.
Pagespeed need the resource public cacheable to work.  What Cache-control header have these resources?

here I do not have it very well tuned the cache with nginx, I'm still making adjustments
proxy_cache_path /var/nginx/ghostcache levels=1:2 keys_zone=ghostcache:10m max_size=300m inactive=24h;
proxy_cache_key "$scheme$request_method$host$request_uri";
proxy_cache_methods GET HEAD;
location / {
proxy_cache ghostcache;
proxy_cache_valid 10m;
proxy_cache_valid 404 1m;
proxy_cache_purge 1;
proxy_ignore_headers Set-Cookie;
proxy_hide_header Set-Cookie;
proxy_cache_use_stale error timeout invalid_header updating http_500 http_502 http_503 http_504;
proxy_ignore_headers Cache-Control;
add_header X-Cache-Status $upstream_cache_status;

Hi
Try to comment these param
proxy_ignore_headers Cache-Control;
and set the header Cache-Control: max-age= in the origin.

Hi Lofesa , I made the change and added it to the location part
 proxy_hide_header Set-Cookie;
    proxy_cache_use_stale error timeout invalid_header updating http_500 http_502 http_503 http_504;
    add_header Cache-Control "max-age=604800,  public";
    add_header X-Cache-Status $upstream_cache_status;

thank you for your patience,  but I have a question here do you need to see something, with this change?

Pagespeed need that the resources bacame public cacheable.
When you put pagespeed off, the resources must have a cache-control header like that you posted (Cache-Control="max-age=604800,  public")
You can test it whit
https://www.mydomain.com/?PageSpeed=off
and look at the headers of resources.
In the image you have posted, you have debug messages like
<!-- Resouce headers are preventing............
these messages are due 2 main reasons, the resouce return a 404, and you need to put the file in their location or delete the html call to these resource, or the resource have a cache-control that is not public cacheable like cache-public="max-age=0" or "private" or "not cache".
Whit these changes I spect to get cache-control="max-age=604800,public" in the resource header when pagespeed is off

I see the header, although some images like png or some css do not cache

Well, in those resources you don´t have cache-control set to public (or max-age=XXXX) you can expect these debug messages <!--Resource headers are preventing... that you showed in an previous image.
In those resources you have set the cache-control you can expect that the resource become ewrited by pagespeed and you can see in the html code like https://www.mysite.com/A.style.css.pagespeed.HASH.css

Hi Lofesa , sorry for delay , I made some changes to the cache part and now I'm caching the jpg, png, css, which I do not know because I see the cache-control header: no-cache , look the image :

based on your experience how you could improve the cache along with pagespeed.

Request headers don´t matter. The ones that ae relevant are the response headers. In the last image you posted, the slide5.png had a valid cache-control : max-age=10800..... but looking in that mage I don´t see any header that sugest the image become optimized by pagespeed, headers like etag: W/"0" , or x-page-speed: <IP_ADDRESS>-0....
Can you post here or send in a private mail a url from your site so I can test it?

How I sent you a private mail on github? , my mail es xserverlinuxatgmail.com

@rickygm , sorry , I forgot that private messages are lost in gibhub. You can send it to lofesa.at.gmail.com

Ok , I send now

i am observing the below logs on mine nginx error. can anybody please help me to resolve this issue
2021/01/12 09:24:56 [error] 2566#2586: [ngx_pagespeed <IP_ADDRESS>-0] http://xxx.xxx.xxx.xxx/ (connecting to:lb1.i):0:Error status=670002 (Name or service not known) serf_connection_create2

i am observing the below logs on mine nginx error. can anybody please help me to resolve this issue
2021/01/12 09:24:56 [error] 2566#2586: [ngx_pagespeed <IP_ADDRESS>-0] http://xxx.xxx.xxx.xxx/ (connecting to:lb1.i):0:Error status=670002 (Name or service not known) serf_connection_create2

i am observing the below logs on mine nginx error. can anybody please help me to resolve this issue
2021/01/12 09:24:56 [error] 2566#2586: [ngx_pagespeed <IP_ADDRESS>-0] http://xxx.xxx.xxx.xxx/ (connecting to:lb1.i):0:Error status=670002 (Name or service not known) serf_connection_create2

The module isn't able to fetch its input resources. It might be good to check https://www.modpagespeed.com/doc/faq#warning-fetch-rate and possibly https://www.modpagespeed.com/doc/https_support

i am observing the below logs on mine nginx error. can anybody please help me to resolve this issue
2021/01/12 09:24:56 [error] 2566#2586: [ngx_pagespeed <IP_ADDRESS>-0] http://xxx.xxx.xxx.xxx/ (connecting to:lb1.i):0:Error status=670002 (Name or service not known) serf_connection_create2

The module isn't able to fetch its input resources. It might be good to check https://www.modpagespeed.com/doc/faq#warning-fetch-rate and possibly https://www.modpagespeed.com/doc/https_support

As stated by @oschaaf the pagespeed module is unable to fecht the resource.
Maybe you have misconfigured https fechting or maybe you have a name resolution problem.

As stated by @oschaaf the pagespeed module is unable to fecht the resource.
Maybe you have misconfigured https fechting or maybe you have a name resolution problem.


Problems and questions on the reproducibility of experiments

Hi, i'm trying to reproduce some of yours evaluation experiments. In particular i'm doing a robustness evaluation on the task of Sentiment Analysis on the IMDB dataset. As you said i'm using the IMDB dataset and the contrast dataset (488 samples each). I'm testing the gpt-j-6b model.
I'm trying to replicate the evaluation by writing the code to do it by myself. However, i have so questions about it.
Since i'm using the transformers library from huggingface, i'm loading the model as a Text generetor, but i did't get if you use a few-shot situation or you are using a zero-shot prompting. And if you are using a few-shot prompring technique, how many prompt examples? Are you defining the task for the model before the evaluation?
Can you provide some details in order to let me able to reproduce the evaluation by coding the evaluation framework for the robustness on sentiment analysis of gpt-j?

Could you clarify if you're trying to reproduce the results (1) by reimplementing the evaluations in your own scripts / framework, or (2) by re-running evaluation the HELM framework?
If 1, for the prompt format, you can look at the runs list for imdb on gpt-j-6b here. You can click on the run, then click Request Details which will give you the exact prompt format for the requests.
If 2, could you let me know if you intend to use local inference of the Hugging Face model?

Hi!
Thanks for answer.
I'm trying to reproduce the evaluation of the gpt-j-6b model by myself without the use of your library. So i'm on the situation (1).
In particular i'm trying to reproduce the robustness evaluation on the sentiment analysis task.
What i infer from the link is that you used a 5-shots input context without any other prompt tuning. Is it correct?
But i have one another question, did you use the vanilla model from eleuther AI or a different fine tuned version?
Is this from huggingface https://huggingface.co/EleutherAI/gpt-j-6b or a different one ?

Great, thanks for the clarification.

What i infer from the link is that you used a 5-shots input context without any other prompt tuning. Is it correct?

That is correct.

But i have one another question, did you use the vanilla model from eleuther AI or a different fine tuned version?
Is this from huggingface https://huggingface.co/EleutherAI/gpt-j-6b or a different one ?

We used the base model (which you linked to), not a fine-tuned version.

Really thanks for the reply!
I'm sorry to bother you but i need this clarification because your research it's really interesting and i want to emulate your results in order to get a better understand of the topic.
I have only one last doubt.
In order to evaluate the robustness of gpt-j-6b on the sentiment analysis task did you used this contrast set https://github.com/allenai/contrast-sets/tree/main/IMDb/data ?
Because here, i have only 488 samples if i use the test set. I'm asking that because in that way i've used 488 samples for the performance on the clear set (the same 488) and 488 for the robustness evaluation on the contrast set.
It seems that you have at least 1000 samples, is it true? Where can i find your dataset?
On those 488 contrast samples i got an accuracy of 0.7479 and on your experiments you have an accuracy near to 0.90, how is it possible?
In the clear samples (just the same 488 in a non-contrast way) you have an accuracy of 0.939 and i have an accuracy of 0.84.
As you said i've used 5-shots prompting
This is the repo for my experiments replication if you need it: https://github.com/CristianCosci/LLMs_Robustness_evaluation_on_Sentiment_Analysis
Thank you so much for the time you dedicated to me


Debian/Ubuntu packages

Would it be possible to provide deb packages to easily install hub on Ubuntu and Debian?

@mislav ubuntu and debian support more than one architecture, so one pre-compiled binary will not be enough unless for some reason you want to only support x86 or x64. However cross-compiling go shouldn't be that hard.
The SO answer mentioned here tells you how to generate a .deb package. This is a package file that contains the pre-compiled binaries and a list of dependencies.
Once you have a .deb for each architecture and ubuntu/debian version that you wish to support you can immediately distribute  it through a PPA as has been mentioned by dbarnett. I guess this answer may be helpful: http://askubuntu.com/a/71516/49920
You can then request it to be posted to the debian repositories:
https://wiki.debian.org/DebianMentorsFaq#How_do_I_make_my_first_package.3F.

There is an ITP for a similar tool on Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763345

+1

+1

+1

@sometimesfood created a .deb PPA for hub a while back. I wonder if he'd be willing to update the package version (it's old at 1.10.1) or allow someone else to do so?

@rroblak My packaging script uses Debian's Ruby-specific packaging tool chain, so it will probably not be too useful.
Still, if there is enough interest, I can look into creating a new Debian package and updating the PPA. Creating packages is not too difficult but it can be quite intimidating for a beginner (lots of tools, lots of policies). Also, to make matters worse, the Debian packaging tools and docs for golang seem to be rather new.

Btw, just for reference: Michael Stapelberg has compiled some nice examples on how to package a simple Go application for Debian:
http://anonscm.debian.org/cgit/collab-maint/dh-golang.git/tree/example
Also, the debian/rules and debian/control files of this package seem to be a nice reference:
https://packages.debian.org/sid/codesearch

Hey guys, I just created two .deb packages (amd64 and i386). I've tested amd64 and it is working fine. It's missing the completion scripts because I didn't know where to put them.
So, I just don't know where I can upload them.

@alfredocdmiranda If you do not want to host your own repository, you can either upload the sources to Launchpad and let it build packages for a PPA, or you can try http://packagecloud.io or a similar service.

@sometimesfood thanks, I liked this packagecloud.io
So, I've uploaded the files. https://packagecloud.io/alfredocdmiranda/misc

I built a "proper" dpkg for Ubuntu and created a ppa.
You should be able to install it with the following:
sudo add-apt-repository ppa:cpick/hub
sudo apt-get update
sudo apt-get install hub

If there's any interest, I'd be willing to try to get these changes into the various upstreams.
In the meantime, please report issues and/or send pull requests to https://github.com/cpick/hub (changes are on the 'debian' branch).

:+1:

@cpick I get this :
W: Failed to fetch http://ppa.launchpad.net/cpick/hub/ubuntu/dists/vivid/main/binary-amd64/Packages  404  Not Found

W: Failed to fetch http://ppa.launchpad.net/cpick/hub/ubuntu/dists/vivid/main/binary-i386/Packages  404  Not Found

Ah, I only built packages for trusty. I'll produce some for utopic and
vivid tomorrow. Thanks for the report!
On Thu, May 14, 2015, 17:32 th3m4ri0<EMAIL_ADDRESS>wrote:

@cpick https://github.com/cpick I get this :
W: Failed to fetch http://ppa.launchpad.net/cpick/hub/ubuntu/dists/vivid/main/binary-amd64/Packages  404  Not Found
W: Failed to fetch http://ppa.launchpad.net/cpick/hub/ubuntu/dists/vivid/main/binary-i386/Packages  404  Not Found
—
Reply to this email directly or view it on GitHub
https://github.com/github/hub/issues/718#issuecomment-102176571.

@th3m4ri0 I've added packages for utopic, vivid, and wily to the ppa and tested it on a vivid VM.
Please try again, it should work.  Thanks for trying out my packages!

Working :+1:

:+1:

Awesome, I really hope they start publishing this in a 'official' upstream ppa. Thanks for your work @cpick.

@cpick Thanks for doing this.
Where do other packages keep their shell completion scripts? Does Ubuntu have some standard for this?

@cpick You're a hero.

Completions should go in /usr/share/bash-completion/completions/ to take advantage of lazy-loading.
Also, #592 blocks hub completion from loading in /etc/bash_completion.d/ if git was lazy-loaded, which should be the default everywhere.
For example, ArchLinux has distributed hub since late 2012. Here is the PKGBUILD, as you can see the hub completion is installed next to the git completion, and everything works smoothly.

thanks for this debian package

@mislav in my initial, previous version (2.2.1-0ubuntu0ppa1) I had already put the hub completion script into /etc/bash_completion.d/ (which is the "compatability" or "legacy" location since its scripts are not lazy-loaded).  However, as @eli-schwartz points out, they still weren't working as a result of #592.
To work around the issue, I just released a new version (2.2.1-0ubuntu0ppa2) which forces git's completion script to be loaded first (ie no longer lazy-loaded).  This works around the issue at the cost of some small, additional bash-startup time.  Once #592 is fixed, I ought to be able to find a way to switch both hub and git to be properly lazy-loaded (out of /usr/share/bash-completion/completions/).
One small peculiarity is that hub's completion script affects completions for both the hub and git commands.  This is correct if the user has followed hub's recommendation and aliased hub to git, but it could be confusing to suggest hub-specific commands when completing on git without the alias in place.
I could install the alias automatically, system-wide, as part of this package.

Also, #592 blocks hub completion from loading in /etc/bash_completion.d/ if git was lazy-loaded, which should be the default everywhere.
For example, ArchLinux has distributed hub since late 2012. Here is the PKGBUILD, as you can see the hub completion is installed next to the git completion, and everything works smoothly.

Hmm, I thought this was true, but turns out it only works for the primary commands. subcommands don't complete until you attempt to complete hub.

The package should never install the alias. Instead, the user should be a able to opt-in to the alias by using alias git=hub in their shell config.
I hope that future iterations of our shell completion will allow for lazy loading. Right now, I don't know why lazy loading doesn't work for our script and how can we make it work.

+1

@cpick Thanks for the repo!
I get this error though
W: Failed to fetch http://ppa.launchpad.net/cpick/hub/ubuntu/dists/jessie/main/binary-amd64/Packages  404  Not Found

Is it possible to add the Debian releases as well?

@simonvanderveldt to my knowledge, launchpad won't host PPA builds for non-Ubuntu (ie Debian, etc) distros.
That being said, since hub is a (largely) statically linked executable and the package is simple, you shouldn't have any trouble installing and using the Ubuntu packages/binaries on your Debian system.  You'll just need to update the apt sources.list entry for my PPA so that it points to an Ubuntu codename, say 'trusty' (instead of 'jessie'), run an apt-get update and you should be good to go.

@cpick

to my knowledge, launchpad won't host PPA builds for non-Ubuntu (ie Debian, etc) distros.
Seems like you're right https://bugs.launchpad.net/launchpad/+bug/188564. I hoped it would be possible, but didn't check before.

I'll adjust the line in my sources.list, thanks for the quick response!

any news for the 2.2.3 release debian package?

@cpick Are your Debian packages ready to use? Should we update the installation documentation with instructions? How should we handle updates on new releases?

@cpick Any news about Xenial package?

@Mte90 I should be able to update my PPA in the next couple of days
@mislav my PPA is certainly functional (albiet a touch out of date at the moment), the instructions for installing hub from the PPA are:
sudo add-apt-repository ppa:cpick/hub
sudo apt-get update
sudo apt-get install hub

For now the update process is just a matter of me noticing (or someone pinging me to tell me) that there's a new hub version and then pulling those changes into the package.  When I pull in 2.2.3 I'll take notes of my steps.
@mhalano I just copied the existing (2.2.1) packages on over to xenial as well (and did some rough testing), please give it a go.

@Mte90 @mhalano I was actually able to get to updating the package to 2.2.3, it's already released for xenial.  If there's any interest in having it backported to any older Ubuntu versions please let me know.
@mislav I took notes on my steps for updating the package.  It was somewhat involved so let me know if you'd like me to put them somewhere.

I think the biggest problem is keep repository update. May we could look for a way to find out how to get the latest version number and pack automagically.

@mhalano I have a post-CI hook that automatically publishes pre-built binaries on tagged releases. Maybe the same process could create new packages? All I would need is some destination to upload them to.

@mislav Unfortunately I can't help you much in this point. My suggestion is look about PPA on Launchpad.net, one of the main methods to distribute Debian packages, for Ubuntu, at least. But my suggestion is publish packages in the same way you release the pre-compiled binaries. A lot of projects (like Nylas N1 - https://github.com/nylas/N1/releases) do in this way. What you think?

@cpick It seems your ppa is a few versions old. Could you update that please. :)

sudo apt-get install ruby
sudo curl https://hub.github.com/standalone -Lo /usr/bin/hub
sudo chmod 755 /usr/bin/hub

Ubuntu 16.04

@mileo That approach installs a very old version of hub. Please don't use it! New precompiled binaries are available from Releases section on this project.

here's the ITP for github-hub: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807866

This worked on debian.
RUN echo "deb http://ftp.us.debian.org/debian testing main contrib non-free" >> /etc/apt/sources.list \
     &&      apt-get update              \
     &&      apt-get install -y git      \
     &&      apt-get clean all

http://stackoverflow.com/questions/15104089/packaging-go-application-for-debian

I'd love if the CI kept this PPA up to date.  In the mean time, can you push a new version?  Thank you.

I've updated hub to version 2.2.9 in my ppa:cpick/hub.  A sudo apt update && sudo apt upgrade should retrieve it.
For my future reference this is the series of commands I run perform the update:
# Having initially setup my ppa at: https://launchpad.net/~cpick/+archive/ubuntu/hub
export<EMAIL_ADDRESS>export DEBFULLNAME=Chris Pick
git clone cpick/hub
cd hub
git checkout debian
HUB_VERS="2.2.9"
git merge "v${HUB_VERS}"
dch -v "${HUB_VERS}-0ubuntu0ppa1" -u low
# Copy release notes over from https://github.com/github/hub/releases/tag/v${HUB_VERS}
dch -r "$(lsb_release -sc)"
git commit -am "Update debian changelog for ${HUB_VERS}"
git push origin debian
cat >|Vagrantfile <<EOF
Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/xenial64"
  config.vm.synced_folder ".", "/home/ubuntu/src"
end
EOF
vagrant up
vagrant ssh
sudo apt-get update
sudo apt-get install -y packaging-dev equivs
cd src
mk-build-deps -irs sudo
dpkg-buildpackage -us -uc
dpkg-genchanges -S >"$(echo ../hub_*.dsc | sed -e 's/\.[^.]*$/_source.changes/')"
mkdir bin
mv ../hub_* bin/
exit
cd bin
debsign hub_*_source.changes
dput ppa:cpick/hub hub_*_source.changes
git checkout Vagrantfile

Thank you for the PPA! There doesn't seem to be a build in it for Yakkety, but installing the package built for Xenial seems to work on my system.

@abesto I just copied the latest packages into yakkety and zesty repos (they contain the same binaries as the ones you installed from xenial, so I don't know that there's any reason to take any further action in your case).

Thanks for the PPA! Should it be advertised in the README?

@cpick I made a PR that updates README.md with instructions to install from the PPA. Tested under Ubuntu and Windows Subsystem for Linux.
https://github.com/github/hub/pull/1502
BTW, the PPA needs to be refreshed with the latest version again.

If maintaining a PPA is a burden we can publish the deb file to bintry or packagecloud.

Maybe Alin Andrei (andrew@webupd8.org), who runs webupd8, would be more co-operative. His repo is widely used, and is thoughtfully put together. See his Launchpad page.

@mslinn thanks for the effort and the pull request!
I usually only update my PPA when there's a full (non-pre) release.
I don't usually find it a burden, but certainly would love if something was upstreamed/hosted officially by the hub team.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807866

Hello all,
I would suggest to use PPA continual build service to automate the creation of deb packages. I already do something similar for other projects, eg, tmate, if you're ok, I could help to setup everything for this project, what I would need from hub's authors would be:

Separate branch or repository where to host debian/ packaging instructions, maybe adopting @cpick work?
A hub or github organization at https://launchpad.net
Permitions in the launchpad team, my lp id is: https://launchpad.net/~javier-lopez

How it works?

LP sync continually target projects, for this case could be stable + debian branches
When LP detect changes it rebuilds packages and host them at the specified PPA

Example:
https://code.launchpad.net/~tmate.io/+recipe/tmate-stable

Any updates for this?

Adding sudo add-apt-repository ppa:cpick/hub on my Ubuntu 17.10 followed by sudo apt-get update yields:
Hit:1 http://security.ubuntu.com/ubuntu artful-security InRelease
Hit:2 http://archive.canonical.com/ubuntu artful InRelease
Ign:3 http://ppa.launchpad.net/cpick/hub/ubuntu artful InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu artful InRelease
Hit:5 http://us.archive.ubuntu.com/ubuntu artful-updates InRelease
Hit:6 http://ppa.launchpad.net/cwchien/gradle/ubuntu artful InRelease
Err:7 http://ppa.launchpad.net/cpick/hub/ubuntu artful Release
  404  Not Found
Hit:8 https://download.sublimetext.com apt/stable/ InRelease
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/cpick/hub/ubuntu artful Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

This used to work a couple weeks ago on a different Ubuntu machine that has the same set up. Also adding --allow-unauthenticated didn't help.

@vanniktech I copied the latest packages to the artful and bionic repos and ran a quick installation test in an artful VM.
You should be able to install them with a sudo apt update && sudo apt install hub.

That was super quick, thank you. Everything works now again 🚀

What about the Debian ITP?

@cpick opened a pr (hopefully I did it right) to get the debian updated to 2.3.0.
https://github.com/cpick/hub/pull/1

@jonstuebe thanks for giving it a whack!  I've updated the cpick/hub:debian branch to pull in the new v2.3.0 code, but haven't yet gotten it to build.
I'm not as familiar with debhelper's go builds as I once was so it won't be super easy for me to sort out.  If anyone is able to lend a hand it would be much appreciated: https://github.com/cpick/hub/issues/2

Based partly on @mhalano's trick to get the latest version, I wrote a script to install the latest version on Ubuntu: https://gist.github.com/Taytay/4b463d3e7ebf9915107251b3abad7073
This script can be turned into a one-liner, but it's obviously a bit harder to read:
HUB_DIST=linux-amd64 HUB_VERSION=`curl -w "%{url_effective}\n" -I -L -s -S github.com/github/hub/releases/latest -o /dev/null | awk -F'releases/tag/v' '{ print $2 }'`; curl "https://github.com/github/hub/releases/download/v$HUB_VERSION/hub-$HUB_DIST-$HUB_VERSION.tgz" -L | tar xvz && sudo ./hub-$HUB_DIST-$HUB_VERSION/install && rm -r ./hub-$HUB_DIST-$HUB_VERSION

I think a good idea would be create a debian/ directory with all the metadata to allow to compile the application.

I did sudo apt install linuxbrew-wrapper && linuxbrew install hub

@graingert super helpful and much prefer that to the (currently outdated) PPA (on 2.2.9) since I get 2.5.0 now. I had to add an alias for bash/fish for those who use both.
For bash:
# in ~/.bashrc, ~/.profile, or ~/.bash_profile or wherever you keep aliases
alias hub="/home/linuxbrew/.linuxbrew/bin/hub"
source /home/linuxbrew/.linuxbrew/etc/bash_completion.d/hub.bash_completion.sh

For fish:
~> ln -s /home/linuxbrew/.linuxbrew/share/fish/vendor_completions.d/hub.fish ~/.config/fish/completions/
~> fish_update_completions  # this may not be needed
~> alias hub="/home/linuxbrew/.linuxbrew/bin/hub"
~> funcsave alias

@graingert I tried your command with a Ubuntu based docker image and got the following error
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linuxbrew-wrapper

I'm not super familiar with this and I also tried to install the linuxbrew according to their website and it didn't work as well. but the response from @Taytay worked for me.

Ubuntu in docker won't tell you what packages to install to be able to run
a command
On Sun, 12 Aug 2018, 09:09 Simon Tse<EMAIL_ADDRESS>wrote:

@graingert https://github.com/graingert I tried your command with a
Ubuntu based docker image and got the following error
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linuxbrew-wrapper
I'm not super familiar with this and I also tried to install the linuxbrew
according to their website and it didn't work as well. but the response
from @Taytay https://github.com/Taytay worked for me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/github/hub/issues/718#issuecomment-412326324, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZQTDIwbpRry2BCCEdTT7zW5LbgqEXMks5uP-LAgaJpZM4DCt8k
.

https://askubuntu.com/questions/959932/installation-instructions-for-golang-1-9-into-ubuntu-16-04/1075726#1075726
# https://github.com/moovweb/gvm/issues/302
sudo apt-get install golang-go
bash < <(curl -s -S -L https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer)
. ~/.gvm/scripts/gvm
v=go1.11
gvm install "$v"
gvm use "$v"
go get github.com/github/hub

Apparently the preferred way of installing hub on Ubuntu is snap install hub as seen in this repo's README.md, but snap is not available on the stable version of Windows Subsystem for Linux (by design). Perhaps it would be better to provide an ubuntu package? I read what Mte90 wrote above but couldn't download using sudo apt install and used cpick's ppa instead

@3nuc Follow this issue for Ubuntu https://github.com/github/hub/issues/2434


Error when call startRecordVideo on Android.

Describe the bug
APP closed with error when call startRecordVideo on Android.
On Android Studio. In Logcat  we can see this error messages:
Capacitor/Plugin                                V  To native (Capacitor plugin): callbackId: 58129015, pluginId: CameraPreview, methodName: startRecordVideo
Capacitor                                       V  callback: 58129015, pluginId: CameraPreview, methodName: startRecordVideo, methodData: {"position":"front","width":640,"height":480}
CameraActivity                                  D  CameraPreview startRecord camera: front width: 640, height: 480, quality: 70
libc                                            W  Access denied finding property "vendor.camera.aux.packagelist"
CameraActivity                                  W  ************orientationHint ***********= 90
MediaRecorder                                   D  constructor+ 0xb40000773592ca80
MediaRecorder                                   D  constructor- 0xb40000773592ca80
CheckPermission                                 E  media_record-code= 24
CheckPermission                                 E  media_record-code= 22
MediaRecorder                                   D  init+ 0xb40000773592ca80
CheckPermission                                 E  media_record-code= 2
CheckPermission                                 E  media_record-code= 23
MediaRecorder                                   D  init- 0xb40000773592ca80
CheckPermission                                 E  media_record-code= 12
AndroidRuntime                                  D  Shutting down VM
AndroidRuntime                                  E  FATAL EXCEPTION: main
Process:    , PID: 20892
java.lang.RuntimeException: setAudioSource failed.
at android.media.MediaRecorder.setAudioSource(Native Method)
at com.ahm.capacitor.camera.preview.CameraActivity.startRecord(CameraActivity.java:865)
at com.ahm.capacitor.camera.preview.CameraPreview$2.run(CameraPreview.java:230)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at android.app.ActivityThread.main(ActivityThread.java:8381)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)
W  Attempt to remove non-JNI local reference, dumping thread
Process                                         I  Sending signal. PID: 20892 SIG: 9
To Reproduce
const cameraPreviewOptions: CameraPreviewOptions = {
position: 'front',
width: window.screen.width,
height: window.screen.height,
};
CameraPreview.startRecordVideo(cameraPreviewOptions);
Smartphone (please complete the following information):

Device: Android 13
OS: Android 13

I am also having this issue on a Pixel 7 running Android 13 and a moto g stylus running Android 11.
I've found that by editing CameraPreview.java to add the RECORD_AUDIO permission, the app will request permission to record audio and then will not crash. You also need to add <uses-permission android:name="android.permission.RECORD_AUDIO" /> to your app's AndroidManifest.xml file.
Ideally, we could solve this by implementing the disableAudio flag in Android too. I've started to look into it, but I haven't found a way to disable audio recording in the MediaRecorder API.

I have the same issue and can confirm that adding a "record_audio" permission requirement in Java and in the manifest resolves the issue. Will there be a new version of the plugin soon?


Alternate Folder Structure for Schema Migrations

Summary
A bundle that has a large number of schema migration versions eventually become unwieldy because of the large number of folders in the Migrations/Schema folder.  Everything still works, it's just awkward to deal with (especially in graphical IDEs).
You can see an example of this problem in the Magento 1 bundle for OroCRM where there's 62 migration folders today... https://github.com/oroinc/orocrm-magento1-connector/tree/master/src/Oro/Bundle/MagentoBundle/Migrations/Schema .  Due to customer requirements constantly changing schema, one of my bundles have 77 migration folders today.
To help make this more manageable I propose the addition of an alternate folder structure vMajor/Minor/Patch.
Example
In addition to the current vMajor_Minor_Patch (e.g. v1_50 or v1_50_1) structure, I propose the OroMigrationBundle be extended to also allow vMajor/Minor/Patch or vMajor/Minor_Patch (e.g. v1/50 and v1/50/1 or v1/50_1).
If the OroMagentoBundle migration versions roughly tracked the release version (incrementing the Major version when the major product version changed, even if minor and patch numbers didn't match the release version exactly) this would help make the migrations for this bundle more manageable by putting all of the migrations added in v5 of the product in their own folder.  Also, due to the need to support existing customers upgrading from old version of OroCRM, the CRM team can't simply squash all of their exsiting migrationjs into an installer and delete the migrations.  The individual migrations need to be present, so the number of folders in Migrations/Schema will only grow over time.
In the case my bundle with 77 migrations, this would mean I could start a new major version with it's own folder periodically to keep the number of subfolders in each manageable.  I don't want to delete my old migrations because I'd like to retain the ability to recreate a unit test database from scratch by running all of the migrations again.  I'm wary about creating an installer to replace my 77 existing migrations because it will be difficult to ensure that the results of the migrations vs the installer are identical.  It would be much easier to simply organise my migrations into a folder structure.
Moving migrations into subfolders is a low risk change as it's just renaming existing folders.  The alternate solution of creating an installer to "roll up" all of the changes carries substantial risk as ensuring both the original migrations and the installer (even if generated by oro:migration:dump) creates identical schema is difficult.

Related slack thread here: https://orocommunity.slack.com/archives/C11NBUUGY/p1615507777060700

I see no problem with that as long as it preserves the old way as well.
You are welcome to create a PR.


[5.4][CodeCompletion] Reset 'hasSingleExpressionBody' when setting function body

Cherry-pick of #37324 into release/5.4

Explanation: Fix a crash when fast-completion in a function body with multiple statements but if the user had done completions with single expression in the same body. Previously, fast-completion didn't reset hasSingleExpressionBody flag before setting the new body. Because of that, type checker tried to get the single expression from the non single expression body, which caused the crash
Scope: Code completion inside function bodies
Risk: Low
Testing: Added regression test to the suite
Issue: rdar://78122363
Reviewer: Ben Langmuir (@benlangmuir)

@swift-ci Please test

@swift-ci Please nominate

Build failed
Swift Test Linux Platform
Git Sha - 0b13b05df96b7ccfd752ed8acc5a38193d31726e

@swift-ci Please test Linux

Build failed
Swift Test Linux Platform
Git Sha - 0b13b05df96b7ccfd752ed8acc5a38193d31726e

@swift-ci Please test Linux


Migrate project to Spezi

Migrate project to Spezi
:recycle: Current situation & Problem
The project is currently using the January 2023 version of CardinalKit.
:bulb: Proposed solution
Migrates the project to the new Spezi structure.
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[X] I agree to follow the Code of Conduct and Contributing Guidelines.

All tests are passing locally, as seen in the screenshot below - tested with a reset simulator and Firebase emulator. I am not sure why the trend test is failing on Github actions.

@PSchmiedmayer  The tests are all passing locally. After reviewing the result from the Github action, I noticed this error occurring before the test fails:

There is a similar issue noted on StackOverflow: https://stackoverflow.com/questions/72702642/github-ci-uitest-gives-flaky-tests-unable-to-monitor-event-loop
Could this be a Github Actions issue unrelated to our project?

As @PSchmiedmayer and I discussed, the trends UI test has been disabled since it passes locally, but does not pass on Github actions for an unclear reason. A separate issue will be made to track this.


Remove RenderEditable textPainter height hack

Remove the height hack now that https://github.com/flutter/flutter/issues/112123 has been resolved.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

(triage) @LongCatIsLooong Do you still have plans for this one?

Yeah I'll either create an issue for the skipped test or fix the implementation.

Looks like tests are passing now. Ready for review.


Add update and updateIn functions

Makes nested updates a lot easier.
All the cool kids have it😉

People have asked for this before, and it looks like the implementation is simple and well-tested. Thanks!

@evgenykochetkov I expect to merge https://github.com/rtfeldman/seamless-immutable/pull/119 soon and will release once that's in.

Actually, never mind - that one is a breaking change, and I think giving this its own minor version bump is worthwhile. Released as 5.2.0!


Deploy status stuck on 'PENDING'

Hi,
I have a issue when I try to deploy, the status is stuck on 'PENDING'.
The SLD installed on EKS cluster.
The log from worker(stack-deploy-worker-default-7dcbdfd87f-57mvm):
[2022-04-07 13:18:34,045: INFO/MainProcess] Task pipeline git pull[f9c33aed-f988-426f-bdc4-25c99b29d48b] received
[2022-04-07 13:18:34,051: INFO/ForkPoolWorker-2] Download git repo https://github.com/D10S0VSkY-OSS/aws_vpc_poc branch master
[2022-04-07 13:18:34,983: WARNING/ForkPoolWorker-2] [WARNING]: No inventory was parsed, only implicit localhost is available
[2022-04-07 13:18:35,909: WARNING/ForkPoolWorker-2] localhost | SUCCESS => {
"after": "8076b398a8db5f535436298e912f1367b296088a",
"before": "8076b398a8db5f535436298e912f1367b296088a",
"changed": false,
"remote_url_changed": false
}
[2022-04-07 13:18:36,139: INFO/ForkPoolWorker-2] Task pipeline git pull[f9c33aed-f988-426f-bdc4-25c99b29d48b] succeeded in 2.092451297910884s: {'command': 'get_vars_json', 'rc': 0, 'stdout': '{"variable": {"region": {"default": "eu-west-1"}, "vpc_cidr": {"type": "string", "description": "The allowed block size is between a /28 netmask and /16 netmask", "default": "<IP_ADDRESS>/16"}, "subnet_cidr": {"type": "map("string")", "description": "Don't change this without first changing vpc_cidr", "default": {"be1": "<IP_ADDRESS>/24", "be2": "<IP_ADDRESS>/24", "fe1": "<IP_ADDRESS>/24", "fe2": "<IP_ADDRESS>/24"}}, "vpc_name": {"type": "string", "description": "Set VPC name without special characters", "default": "name"}, "enable_dns_support": {"type": "bool", "description": "Set true or false if you want dns support", "default": false}}}'}
[2022-04-07 13:21:06,506: INFO/MainProcess] Task pipeline git pull[ce2c9f7c-e3bc-4b75-9062-2294eb8db26f] received
[2022-04-07 13:21:06,508: INFO/ForkPoolWorker-2] Download git repo https://github.com/D10S0VSkY-OSS/aws_vpc_poc branch master
[2022-04-07 13:21:07,399: WARNING/ForkPoolWorker-2] [WARNING]: No inventory was parsed, only implicit localhost is available
[2022-04-07 13:21:08,401: WARNING/ForkPoolWorker-2] localhost | SUCCESS => {
"after": "8076b398a8db5f535436298e912f1367b296088a",
"before": "8076b398a8db5f535436298e912f1367b296088a",
"changed": false,
"remote_url_changed": false
}
[2022-04-07 13:21:08,604: INFO/ForkPoolWorker-2] Task pipeline git pull[ce2c9f7c-e3bc-4b75-9062-2294eb8db26f] succeeded in 2.096647311002016s: {'command': 'get_vars_json', 'rc': 0, 'stdout': '{"variable": {"region": {"default": "eu-west-1"}, "vpc_cidr": {"type": "string", "description": "The allowed block size is between a /28 netmask and /16 netmask", "default": "<IP_ADDRESS>/16"}, "subnet_cidr": {"type": "map("string")", "description": "Don't change this without first changing vpc_cidr", "default": {"be1": "<IP_ADDRESS>/24", "be2": "<IP_ADDRESS>/24", "fe1": "<IP_ADDRESS>/24", "fe2": "<IP_ADDRESS>/24"}}, "vpc_name": {"type": "string", "description": "Set VPC name without special characters", "default": "name"}, "enable_dns_support": {"type": "bool", "description": "Set true or false if you want dns support", "default": false}}}'}
[2022-04-07 13:21:15,040: INFO/MainProcess] Task pipeline git pull[a1fc132c-b86f-4acf-93c5-774e3350ed3c] received
[2022-04-07 13:21:15,043: INFO/ForkPoolWorker-2] Download git repo http://<IP_ADDRESS>/test-ram branch master
[2022-04-07 13:21:15,916: WARNING/ForkPoolWorker-2] [WARNING]: No inventory was parsed, only implicit localhost is available
[2022-04-07 13:21:16,408: WARNING/ForkPoolWorker-2] localhost | SUCCESS => {
"after": "a0b548490759552a9813a40cd58de96c0bbe6902",
"before": "a0b548490759552a9813a40cd58de96c0bbe6902",
"changed": false,
"remote_url_changed": false
}
[2022-04-07 13:21:16,604: INFO/ForkPoolWorker-2] Task pipeline git pull[a1fc132c-b86f-4acf-93c5-774e3350ed3c] succeeded in 1.5627696781884879s: {'command': 'get_vars_json', 'rc': 0, 'stdout': '{"variable": {"instance_type": {"type": "string", "description": "instance type", "default": "t2.micro"}}}'}
[2022-04-07 13:22:00,693: INFO/MainProcess] Task schedule remove[b1eb0191-7f1d-4c3e-a717-bd303c2b0e31] received
[2022-04-07 13:22:00,694: INFO/MainProcess] Task schedule add[922932d4-9b4b-40d2-8295-03372ccab376] received
[2022-04-07 13:22:00,701: INFO/ForkPoolWorker-2] Task schedule remove[b1eb0191-7f1d-4c3e-a717-bd303c2b0e31] succeeded in 0.0072300180327147245s: {'result': '{'11': 'removed'}'}
[2022-04-07 13:22:01,044: INFO/ForkPoolWorker-2] Task schedule add[922932d4-9b4b-40d2-8295-03372ccab376] succeeded in 0.34154637693427503s: {'deploy': 'start-test-sld_test-ram_test (trigger: cron[month='', day='', day_of_week='0-4', hour='', minute=''], next run at: 2022-04-07 13:23:00 CEST)', 'destroy': 'destroy-test-sld_test-ram_test (trigger: cron[month='', day='', day_of_week='0-4', hour='18', minute='30'], next run at: 2022-04-07 18:30:00 CEST)'}
The log from dashboard(sld-dashboard-75f9bf9476-l9rcr):
cko) Chrome/99.0.4844.51 Safari/537.36"
[2022-04-07 13:22:45 +0200] [1] [CRITICAL] WORKER TIMEOUT (pid:437)
[2022-04-07 13:22:45 +0200] [437] [INFO] Worker exiting (pid: 437)
[2022-04-07 13:22:45 +0200] [441] [INFO] Booting worker with pid: 441
The log from schedule(schedule-584bc87b48-xqz67):
INFO      Get deploy info by id 11 - 200
INFO      Update deploy info by id 11 - 409
INFO      Job "start-test-sld_test-ram_test (trigger: cron[month='', day='', day_of_week='0-4', hour='', minute=''], next run at: 2022-04-07 13:34:00 CEST)" executed successfully
INFO      Get deploy info by id 13 - 200
INFO      Update deploy info by id 13 - 409
INFO      Job "start-test_vpc_test-ram_test (trigger: cron[month='', day='', day_of_week='0-4', hour='', minute=''], next run at: 2022-04-07 13:34:00 CEST)" executed successfully
INFO      Get deploy info by id 12 - 200
INFO      Update deploy info by id 12 - 409
INFO      Job "start-test-sld2_test-ram_test (trigger: cron[month='', day='', day_of_week='0-4', hour='', minute=''], next run at: 2022-04-07 13:34:00 CEST)" executed successfully
INFO:     <IP_ADDRESS>:58988 - "GET / HTTP/1.1" 200 OK
All other microservices show ok in the logs.

Hello Ramazulay,
I don't see the result in the log at all.
In SLD, pending status can have two meanings:

That you have launched a deployment and the task is pending because there is no available worker that can handle it (when doing a redeployment you should receive an error in the console "The task already exists in pending status waiting to be executed",

Or that task have passed more than three days (it's the default that values are saved) and you don't know what the status of that task is, this last behavior is done intentionally to enforce good practices and apply every 3 days (you can change the behavior by passing the variable to the worker)

I understand that you are testing the product, it is recommended to exclude the EKS database to an RDS mysql.
If you need more help, don't hesitate to contact me.


There are some typos on website

Fix them.

[x] I have read the CONTRIBUTING.md and make ci passes on my machine.
[x] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #108   +/-   ##
=======================================
  Coverage   19.04%   19.04%
=======================================
  Files           3        3
  Lines         147      147
=======================================
  Hits           28       28
  Misses        117      117
  Partials        2        2

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 3c51da1...4c3beab. Read the comment docs.


Remove master branch

Since main is being used as the default remote branch we should probably remove the remote master branch to avoid any confusion.

Deleted


Admin/Accounts/Roles errors: "create a copy" and "publish/unpublish" in "with selected"

attempting to create a copy of a role results in a failure because role model has no attribute "slug"
same goes for publish/unpublish, with no attribute

Gooa catch, that actions should be available only for Contents


added note about logout

added warning that end users will be logged out.

I'm not accepting PRs on this project anymore, please reopen one in one of the components at python-social-auth. Looks like this one should be in social-docs.
Thanks!


Remove any data files that are not being used

Estimating this at 3 (see waffle.io) to cover identification of data files that are unused, which may involve some communication with other users.


Lazy load nearest items

Is it possible to lazy load the nearest items?
I want the user to see a little bit of the next item in the slider. I need the items around the active item to be loaded with the active item. Possible?

Ok. I solved it.
In the lazy plugin I added
"changed.owl.carousel" to 'initialized.owl.carousel change.owl.carousel': $.proxy(function(e) {
and changed
while (i++ < n) {
this.load(clones / 2 + this._core.relative(position));
clones && $.each(this._core.clones(this._core.relative(position++)), load);
}
to
while (i++ < n) {
this.load(clones / 2 + this._core.relative(position));
this.load(this._core.current() + 1 );
clones && $.each(this._core.clones(this._core.relative(position++)), load);
}
Now the item after the active item gets loaded.


Replace swaylock-blur with swaylock-effects

swaylock-blur is deprecated in favor of swaylock-effects, see https://github.com/cjbassi/swaylock-blur/blob/master/README.md

Ah, so it is! Thank you!


[MatOption/MatOptgroup] - Expose docs to site

Bug, feature request, or proposal:
Bug/Proposal
What is the expected behavior?
It'd be good to see some docs about MatOption/MatOptgroup.
What is the current behavior?
There's no docs about MatOption/MatOptgroup.

MatOption has been moved to a new file, so MatSelect doc doesn't contain MatOption documentation anymore.
Can you please add the documentation back?

How is this not a thing. Please consider this

Seconded- would love to see some MatOption documentation.

Any update on this ? Without this post on stackoverflow about onSelectionChange, I would still be stuck figuring out how to deal with multi-select, to get only what the user selected

It's really necessary to know about the mat-option API. Actually I'm just researching in source code to figure out how to do certain things like listening on click event and other similar.


eInk theme

{:name "eink"
:version "0.0.1"
:author "Aleš Roubíček"
:source "https://github.com/rarous/lt-eink-theme/"
:desc "Light Table e-ink theme"
:behaviors "lighttable_eink_theme.behaviors"}

Added


fix: model change date() to Time class in intToDate

Description
Fixed #7082.
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Can you add test code to reproduce the bug?

@ddevsr Do you still need this PR?
#7082 was simply a user mistake, not a bug.

By the way, the parameter $userData is not passed at all?
https://github.com/codeigniter4/CodeIgniter4/blob/c6ad1de5d501796d8ea91f134685a445f6aa8c56/system/BaseModel.php#L1263

By the way, the parameter $userData is not passed at all?

Yes, i see $userData no needed in Model or BaseModel. What do you think to remove it and use setDate() directly return Time

What do you think to remove it and use setDate() directly return Time

We cannot remove it. Because it is a breaking change.
But we can make it deprecated.
I think the parameter is not needed.

This PR contains no code change.
Close.


Remove byte array allocation from JNI string methods

Getting string data out of SQLite has involved 2 copies: 1 in JNI-land
(allocating a byte buffer to return to Java) and 1 in Java-land (creating a
String instance).
Rather than do the first copy we can return a direct ByteBuffer instance and
then do the conversion from byte -> String in Java as before.  So this removes
a copy getting string data out of SQLite and into Java.
Since these arrays are immediately copied into Java string instances accessing
SQLite memory in Java will be safe.  I added a test for a string that used
non-ASCII codepoints just to make sure this was still working as expected.

Fixes #561 (well, it's much better than existing behavior, at least).

Thanks for the quick fix! The code basically looks good to me. I'll double-check whether we need to properly release the allocated memory in sqlite.

Nice, I was working off the guidance here https://sqlite.org/c3ref/column_blob.html which seems to indicate it would handle it until
a type conversion or step() function was called... but there may be more going on.  Thanks for the pointers again!

@tildedave Thanks. Yeah. In this usage, allocated DirectByteBuffer will be immediately converted into Strings, so it should be safe.

be care for,   nativeByteBuffer to string is a slow operation due to the decoder access each byte by JNI


Name of testnet is not updated from aggron to pudge totally

Related issue: https://github.com/nervosnetwork/ckb-testnet-faucet/issues/163

How is it going

Fixed by https://github.com/Magickbase/ckb-testnet-faucet/commit/0d6033f082f2ff3d4c1e2268827fa801dc1cd71b


Fix kodai/sotd cast bug. add cl entries, fix staff of water, ehp autoslay, cox rebalance

Description:
Fixed Kodai / Staff of the Dead bug causing non-rune costs to be altered.
Fixed bug that I introduced during code review breaking Staff of Water similaritems.
Added EHP autoslay
Rebalanced cox to only give 10% more boost instead 16% (10% shorter times, 26=>24 vs 26=>22 minutes)
Added some cl entries
Other checks:

[x] I have tested all my changes thoroughly.

have to close since i need to force push, and it will break some of the tests.


Fixes the functions not downloading properly on download.

I have removed throwError cos... it's useless, I have used them before my extendable Message#error. Extendables ftw.
I might PR that extendable soon, as Download.js v2 from Indev is able to download extendables.


Framework entry point debate

IMHO I like the my proposed route better because it takes full advantage of shareable code.
It is also technically more correct, because while you are in node form it is correct to call the child canister methods as such but as soon as you flatten then down into the token stream declaration lists and all of the inline types come out, that list of token streams won't be just canister methods; it will also have some data type declarations sprinkled in there. Not a huge deal, but still technically more correct to abandon the specific labels once we flatten to a list of declarations.
I also think its the more technically interesting solution because of point one. Though I will concede that being technically more sound and more interesting is not by itself a good enough virtue to trump developer experience. However I believe in this case it is also just as good or better of a user experience.


Pass a context to every kopf call/handler

Question

I would like to embed kopf in an application to perform some extra cluster functions as a response to events.

I can always use a global variable.
Actually, I have to go the embedding way as I want to build wrappers to take some custom arguments as input, validate them, form connection strings, and then start the kopf asyncio loop. Plus I have to pass these params around as every handler would need them.
This should be a pretty common ask, and I am not sure how is that done currently.
Checklist

[x] I have read the documentation and searched there for the problem

[x] I have searched in the GitHub Issues for similar questions

Keywords

"kopf pass context to handlers" on Google and in docs.

@krish7919 Just to clarify: do you mean an arbitrary object of arbitrary class, which is passed through the call stack from the owning application down to the handlers (all of them), right? Something like a memo kwarg (per-resource container for arbitrary keys/fields), but global and of external origin?

Precisely. In Go, this is the context, or a struct with the values required.

This is something that's interesting for our usage too, especially when we're constantly trying to connect to the Kuberentes API..

This issue also may be related to my question in #367


etcd is running, but not bind 4001, 7001

I've installed CoreOS on 3 nodes. Two nodes are fine but one node is going wrong.
$ sudo systemctl status etcd
● etcd.service - etcd
   Loaded: loaded (/usr/lib64/systemd/system/etcd.service; static; vendor preset: disabled)
  Drop-In: /run/systemd/system/etcd.service.d
           └─20-cloudinit.conf
   Active: active (running) since Thu 2015-07-23 02:02:13 UTC; 8s ago
 Main PID: 1708 (etcd)
   Memory: 1.8M
      CPU: 15ms
   CGroup: /system.slice/etcd.service
           └─1708 /usr/bin/etcd

Jul 23 02:02:13 deis2 systemd[1]: Started etcd.
Jul 23 02:02:13 deis2 systemd[1]: Starting etcd...
Jul 23 02:02:13 deis2 etcd[1708]: [etcd] Jul 23 02:02:13.086 INFO      | Discovery via https://discovery.etcd....b689b.
Jul 23 02:02:14 deis2 etcd[1708]: [etcd] Jul 23 02:02:14.280 INFO      | Discovery found peers [http://129.254...:7001]
Jul 23 02:02:14 deis2 etcd[1708]: [etcd] Jul 23 02:02:14.280 INFO      | Discovery fetched back peer list: [12...:7001]
Jul 23 02:02:14 deis2 etcd[1708]: [etcd] Jul 23 02:02:14.281 INFO      | Send Join Request to http://129.254.1...1/join
Jul 23 02:02:18 deis2 etcd[1708]: [etcd] Jul 23 02:02:18.782 INFO      | fac687b5306b4d6d8cf680a42b36e284 atte...aders)
Jul 23 02:02:18 deis2 etcd[1708]: [etcd] Jul 23 02:02:18.783 INFO      | Send Join Request to http://129.254.1...1/join
Hint: Some lines were ellipsized, use -l to show in full.

$ sudo netstat -lntp
sudo netstat -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:5355            <IP_ADDRESS>:*               LISTEN      887/systemd-resolve
tcp6       0      0 :::22                   :::*                    LISTEN      1/systemd
tcp6       0      0 :::2375                 :::*                    LISTEN      1/systemd
tcp6       0      0 :::5355                 :::*                    LISTEN      887/systemd-resolve

I would suggest you to try etcd2 instead of etcd0 by using etcd2 service. We are not actively maintaining etcd0 at the moment.


Update docs for For Nodes

since transparent scopes have been removed, the local variables are now at the same level and we handle the mismatch in the CRuby compiler
cf. https://github.com/ruby/prism/pull/1962

Thanks!


IMIS package has been remove from CRAN

source("analysis/03_calibration.R", echo = TRUE)
will return Error in loadNamespace(x) : there is no package called ‘IMIS’ because IMIS was removed from Cran and no longer runs in the latest versions of R
https://cran.r-project.org/web/packages/IMIS/index.html
The workaround is to comment out this line i.e. do not run calibration, but ideally, the framework example should be updated with another equivalent package to remain and end-to-end working example.

Dear Gloria, thank you for bringing this to our attention. I added code to download the archived version of IMIS in this line: https://github.com/DARTH-git/darthpack/blob/8f82230ab0ee6261ee569f0ef97d0ed341dcaeb5/analysis/03_calibration.R#L22
You should be able to install IMIS now and run the working example from beginning to end :).

amazing! such an speedy reply

Thank you for raising this issue!
From: Gloria Macia @.>
Date: Wednesday, January 17, 2024 at 1:26 PM
To: DARTH-git/darthpack @.>
Cc: Fernando Alarid Escudero @.>, Comment @.>
Subject: Re: [DARTH-git/darthpack] IMIS package has been remove from CRAN (Issue #7)
amazing! such an speedy reply
—
Reply to this email directly, view it on GitHubhttps://github.com/DARTH-git/darthpack/issues/7#issuecomment-1896808533, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACEQULWWWSH6L6GBDWPJLCTYPA6YBAVCNFSM6AAAAABB5EHSMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJWHAYDQNJTGM.
You are receiving this because you commented.Message ID: @.***>


theme/styling issue - after install

the theme isnt working on the site so its all just text and hyperlinks

if you can login to the admin dashboard, go to settings, and the site URL, and make it to start with https://.
if you can not open the dashboard, then using phpmyadmin open the kleeja database, and from the config table, find a row with setting name called siteurl, change the setting value to start with https://.
and i think this is the issue that you are facing it

That didn't work. Looks the same even after I edited the database


bug report template: use

Much more pleasing to see. Output will look like this:
Description of issue
[insert a detailed description of your issue here]
Output of `brew cask  --verbose`
[paste output here]

Output of `brew doctor`
[paste output here]

Output of `brew cask doctor`
[paste output here]

Huge improvement! I should take some time to learn about other neat HTML5 features 😄


4 or 8 pixel blocks in downloaded Sentinel imagery

hi Pau @prlz77 and Oscar @oscmansan,
Thanks for your work. We were downloading the data with seco_downloader.py but noticed a certain 4 or 8-pixel block structure in the images.
Looking over the source code, I can't find a concrete reason.
Could it be connected to the getInfo line https://github.com/ElementAI/seasonal-contrast/blob/5395c027922569f5c5b1785ad1ccddd839749c36/datasets/seco_downloader.py#L175
where (maybe) only an approximated representation of the images is returned?

hi @MarcCoru , may i ask how did you sample these connected tiles? It seems the original code would randomly sample tiles around all the 1000 cities.


[Bug]: An error is reported when data archiving, scheduled tasks, and editing description information are reported

ODC version
4.3.3
OB version
no related
What happened?

Data archiving, scheduled execution, enter a new description, click Save, and an error is reported
What did you expect to happen?
Data archiving, scheduled execution, enter a new description, click Save, and the description can be modified normally
How can we reproduce it (as minimally and precisely as possible)?
Initiate a data archiving task, execute the task on a scheduled basis, modify the description information, click Save, and observe whether there is any abnormality in the system
Anything else we need to know?
No response

scheduled task can only be edited if it is in a disabled state and has no running subtasks


Scrolling always starts at the top for Chrome and Firefox

Expected Behaviour
Scroll.toElement starts scrolling at current position
Actual Behaviour
On Chrome and Firefox the scroll position is reset to the top and starts there.
Usage
const element = document.getElementById(id);
const scroll = new Scroll(document.body);
scroll.toElement(element)

Details
This is most likely related to the weird fact that document.body.scrollTop is always 0 on Chrome and Firefox
Hacky fix
This works for us:
const element = document.getElementById(id);
const scroll = new Scroll(document.documentElement.scrollTop > 0 ? document.documentElement : document.body);
scroll.toElement(element)

Notice: I know this will use document.body when the page is not scrolled. This prevents you from initializing the scroll object only once.

This duplicates #25 - sorry

thanks, yeah. Its related to the browser inconsistency as mentioned in #25. Would you mind opening a PR for the change? :smiley:

I haven't really dug into the library details yet, but may probably find some time next week.
You seem to be handling the differences between document.body and document.documentElement already, but there seems to be some race-condition

A race condition? Hmm.. it's hard to diagnose the problem without an example. The bug identified in  #25 was partially due to absolute positioning being used and the parent not having its overflow content scrollable in the css. Maybe you can send me an example of your code? I'm not able to reproduce using the Scroll To Element example exposed by this package.

Going to close this for now. Feel free to reopen if you can verify this is a bug with the package.


q.sh breaks Cobra-based autocomplete and leaks the debug settings

What is says in the title. #7 fixes this.

@cal2195 Just trying to bump this. It was a pretty serious issue for me and I'd rather others not experience it if possible :)


Are any release versions planned?

Code is kind of stable now (while nothing is happening at the sg14 side). Want to finish the Readme before making a release. Might take several days.

OK, no problem. I am keen to port your projects to Buckaroo, since they are great building-blocks that I think people will benefit from. I'll check back in a few days once a release tag is available. Thanks!

@njlr created first release.

Buck build has been added per PR #4 , thanks to Nick La Rooy @njlr