NextJS / next-i18next / https issue with props

Thank you for the lib! It was nice to be able to painlessly add basic password protected routes.
I just setup iron-session with a nextjs app and am running into a strange issue with passing the required props for next-i18next. The setup is pretty much stock in comparison to the provided app examples. The issue is that when I'm running a local server, both in development and production environments, the i18n props are passed through and I can see that it's picked up my translation JSON from public/locales/en/common.json. When I deploy the app and view it over https, most of the i18n props are still there, except for the actual translations. I'm sure I'm just missing something small but any insight would be greatly appreciated! Thank you!
http:
{
  "_nextI18Next": {
    "initialI18nStore": {
      "en": {
        "common": {
          "home": "Home",
          ...etc
        }
      }
    },
    "initialLocale": "en",
    "ns": [
      "common"
    ],
   ...trimmed
  }
}

over https:
{
  "_nextI18Next": {
    "initialI18nStore": {
      "en": {
        "common": {}
      }
    },
    "initialLocale": "en",
    "ns": [
      "common"
    ],
   ...trimmed
  }
}

// pages/api/login.ts
import type { NextApiRequest, NextApiResponse } from 'next'
import { withSessionRoute } from '@lib/session'

export default withSessionRoute(
  async (req: NextApiRequest, res: NextApiResponse) => {
    const { password } = await req.body

    try {
      if (password === process.env.PASSWORD) {
        const user = { isLoggedIn: true }
        req.session.user = user
        await req.session.save()
        res.json(user)
      } else {
        const user = { isLoggedIn: false }
        res.json(user)
      }
    } catch (error) {
      const { response: fetchResponse } = error
      res.status(fetchResponse?.status || 500).json(error.data)
    }
  },
)

// pages/api/logout.ts
import type { NextApiRequest, NextApiResponse } from 'next'
import { withSessionRoute } from '@lib/session'

export default withSessionRoute(
  async (req: NextApiRequest, res: NextApiResponse) => {
    req.session.destroy()
    res.json({ isLoggedIn: false })
  },
)

// pages/api/user.ts
import type { NextApiRequest, NextApiResponse } from 'next'
import type { User } from '@assets/types'
import { withSessionRoute } from '@lib/session'

export default withSessionRoute(
  async (req: NextApiRequest, res: NextApiResponse<User>) => {
    const { user } = req.session

    if (user) {
      res.json({
        isLoggedIn: true,
        ...user,
      })
    } else {
      res.json({
        isLoggedIn: false,
      })
    }
  },
)

// lib/session.ts
import type { IronSessionOptions } from 'iron-session'
import { withIronSessionApiRoute, withIronSessionSsr } from 'iron-session/next'

const sessionOptions: IronSessionOptions = {
  password: process.env.SECRET_COOKIE_PASSWORD,
  cookieName: 'my-site',
  cookieOptions: {
    secure: process.env.NODE_ENV !== 'development',
  },
}

export function withSessionRoute(handler) {
  return withIronSessionApiRoute(handler, sessionOptions)
}

export function withSessionSsr(handler) {
  return withIronSessionSsr(handler, sessionOptions)
}

// hooks/useUser.ts
import { useEffect } from 'react'
import Router from 'next/router'
import useSWR from 'swr'

export default function useUser({
  redirectTo = '',
  redirectIfFound = false,
} = {}) {
  const { data: user, mutate: mutateUser } = useSWR('/api/user')

  useEffect(() => {
    if (!redirectTo || !user) return

    if (
      (redirectTo && !redirectIfFound && !user?.isLoggedIn) ||
      (redirectIfFound && user?.isLoggedIn)
    ) {
      Router.push(redirectTo)
    }
  }, [user, redirectIfFound, redirectTo])

  return { user, mutateUser }
}

// pages/forms/[name]/responses.ts
import type { GetServerSidePropsContext } from 'next'
import { serverSideTranslations } from 'next-i18next/serverSideTranslations'
...
import useUser from '@hooks/useUser'
import { withSessionSsr } from '@lib/session'

export const getServerSideProps = withSessionSsr(
  async ({ req, res, locale, params }: GetServerSidePropsContext) => {
    const { user } = req.session

    const props = {
      ...(await serverSideTranslations(locale, ['common'])),
      responses: [],
      form: {
        name: '',
        data: { name: 'Unknown or Invalid Form', questions: [] },
      },
    }

    if (user === undefined || !user.isLoggedIn) {
      res.setHeader('location', '/login')
      res.statusCode = 302
      res.end()
      return { props }
    }

   ...db lookup for form
   ...db lookup for responses

    return {
      props: {
        ...props,
        form: form ?? props.form,
        responses,
      },
    }
  },
)

interface Props {
  form: FormWithTypedData
  responses: Omit<Response, 'createdAt' | 'updatedAt'>[]
}

export default function ResponsesPage({ responses, form, ...rest }: Props) {
  useUser({
    redirectTo: '/login',
    redirectIfFound: false,
  })

  console.log('i18n', JSON.stringify(rest, null, 2))

   ...
   ...
   ...

  return (
    <div>
   ...
    </div>
  )
}

I'm running into the same issue. If I use withSessionSsr in my SSR pages, translations doesn't seem to work.

Yep, yep, yep
I'm facing this issue, no idea why
and I wonder how not many are complaining about it
is it that the edge runtime is using incorrect algorithms that's leading it to not recognize the cookie and thus destroy it?

Hey there sorry this doesn't seem to be a bug of iron-session but a more generic help on Next.js. i.e. I don't think the session is messing up with the translations. perhaps getting the translations files is getting blocked by your basic auth, good luck 👍


Add MinimumPoint transpiler pass

Summary
This commit adds a new transpiler pass MinimumPoint which is used to find a local minimum point from the property set between executions of the pass. This is similar to the existing FixedPoint pass but will find the minimum fixed point over the past n exeuctions as opposed to finding a when two subsequent exectuions are at the same point. This is then used in optimization level 3 because the 2q unitary synthesis optimization that is part of the optimization loop can occasionally get stuck oscillating between multiple different equivalent decompositions which prevents the fixed point condition from ever being reached. By checking that we've reached the minimum over the last 5 executions we ensure we're reaching an exit condition in this situation.
Details and comments
Fixes #5832
Fixes #9177
(the underlying cause of the optimization loop's inability to converge at optimization level 3 is not fixed here, there is still a root cause of instability in UnitarySynthesis this just changes the loop exit condition so we're never stuck in an infinte loop)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

37 of 37 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 85.281%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
67276

Relevant Lines:
78887

💛  - Coveralls


thrift proxy: improve router code coverage

Adds some additional tests to cover untested lines in the Thrift router
filter. In addition, updates code ownership.
Risk Level: low
Testing: adds test cases
Docs Changes: n/a
Release Notes: n/a
Fixes: #12003

I cleared the CODEOWNERS change with @rgs1 in Slack. Assigning @alyssawilk re: code coverage improvements.


Dont always regenerate parsetab

Could you please squash commits to keep the commit history clean.

Sure thing.

@b0d0nne11 seems reasonable, what do you think? Besides this probably should help with #168.

Works for me.

Thank you!


Update get started with gh-pages directory

Removed loose bracket
Added clarification for gh-pages root folder

Thanks!

Thanks!


Newlines are converted to spaces in the description of an exported photo, but retained in a finder comment.

If I put an {lf} or {newline} into --description-template, it is removed before being written to the exported photo, but using the same template for --xattr-template findercomment leaves the newline in the resulting comment.
Here's a script to test it:
lftest.zip
and a small library with a single photo with both a title and description:
during.zip
Thanks.

Thanks -- the test script & sample library really help with debugging.  As best as I can tell, exiftool is stripping out the newline (I confirmed osxphotos does not do so) but I'll keep digging to confirm and figure out if there's a way to make sure the linefeed is preserved.

@all-contributors please add @dssinger for bug

I was wrong...osxphotos is removing the new lines before passing to exiftool:
https://github.com/RhetTbull/osxphotos/blob/8e2b76823686374cb056691991167431f6878d47/osxphotos/photoinfo/_photoinfo_export.py#L1874-L1880
This is due to the fact that the exiftool command interface I'm using barfs on embedded newlines.  I think there's a workaround for this with exiftool -- will explore.

I think I have this fixed.  Need to do some additional testing then will push a fix later today.
exiftool -j -G -XMP:Description /Users/rhet/Desktop/Test/pizza.jpg
[{
  "SourceFile": "/Users/rhet/Desktop/Test/pizza.jpg",
  "XMP:Description": "Pizza\nFrom Otto Portland"
}]

I think this is fixed in v0.42.78

It's fixed - thanks!  And thanks for osxphotos - it's immensely useful!

Great! Thanks for the feedback & the excellent issue write-ups -- the sample libraries + test scripts are immensely useful for tracking down these issues.


cross_attention_kwargs ['mv_scale'] are not expected

ComfyUI: v0.3.7 (2024-12-04), VRAM=22GB
t2mv_sdxl_ldm.json
After all the files have downloaded, there is a massive amount of messages in the terminal:
cross_attention_kwargs ['mv_scale'] are not expected by AttnProcessor2_0 and will be ignored.

Refer to #14

In the link you provided, you suggest doing what I have already done at the beginning, judging by the screenshot I attached.

Sorry... Could you provide more outputs in the terminal? Your provided cross_attention_kwargs ['mv_scale'] are not expected by AttnProcessor2_0 and will be ignored. will not affect the results in fact.

Certainly! Now I have reinstalled the extension and the output of your t2mv_sdxl_ldm.json has images. But the terminal with the CUI is massively filled with the same quoted message. Yes, this message does not affect the result now, but it clutters up the terminal. Is it possible to remove it from the standard output when running ComfyUI with default arguments?
I am attaching the log.
comfyui_log.zip

Working on it! #1


Compile description field

Compile the description like the title. That means you can customize both with details from the current entry.
For instance you could display the ID of an entry in the title and the name in the description, because the names are too long for a big heading. Or you want to display some other extra information about the entry in the description.

tests fail

Do you know, which test failed? When I run make test it says "Executed 102 of 102 SUCESS" and "15 test, 34 assertions, 0 failures", so it seems to be okay. And Travis CI just outputs
Running "protractor:e2e" (protractor) task
Starting selenium standalone server...
Selenium standalone server started at http://<IP_ADDRESS>:41818/wd/hub
[launcher] Error: UnknownError: chrome not reachable

Functional/e2e tests (the ones running scenarios in the browser) fail. I'm surprised they don't run when you call make test. What is the output of this command on your side?

Maybe I do something wrong on my commits? Because until now each of my commits failed on Travis CI with the strange error message Error: UnknownError: chrome not reachable. As I already wrote above the e2e tests output on my pc "15 test, 34 assertions, 0 failures":

Tests pass on my side as well, Travis is drunk. Merging.
Thanks for the patch!


Question regarding application user

Hello,
Is it possible for an application user to access a Premium connector on Power Automate?
Is there a licensing scheme for this?
Tx
Pierre-Olivier

@popujol
Please let us know which topic this question is based on. Thanks.

Hello,
This is a power Automate licensing question.
Thank you
Pierre-Olivier Pujol

@popujol
Please see if you can get your question answered here:
https://powerusers.microsoft.com/t5/Power-Apps-Community/ct-p/PowerApps1
Or create a support request:
https://powerapps.microsoft.com/support/


TypeError when running examples in Julia v 0.4

julia /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl
WARNING: module ApproxFun should explicitly import getindex from Base
... bunch of warnings from ApproxFun deleted to save some space ...
WARNING: module ApproxFun should explicitly import transpose from Base
ERROR: LoadError: LoadError: LoadError: LoadError: TypeError: CauchyWeight: in parameter, expected Type{T}, got Tuple{TypeVar,TypeVar}
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/CauchyWeight.jl, in expression starting on line 15
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/GreensFun.jl, in expression starting on line 1
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/SingularIntegralEquations.jl, in expression starting on line 51
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl, in expression starting on line 8
Version information:
julia> versioninfo()
Julia Version 0.4.0-pre+7303
Commit 404b414* (2015-09-05 05:01 UTC)
Platform Info:
System: Linux (x86_64-redhat-linux)
CPU: Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz
WORD_SIZE: 64
BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Nehalem)
LAPACK: libopenblasp.so.0
LIBM: libopenlibm
LLVM: libLLVM-3.3

Thanks!
The ApproxFun suite is currently developed in Julia v0.3.x and will be until the first v0.4 release. Does it work for you in 0.3?
Cheers,
Mikael

On Sep 5, 2015, at 11:21 PM, mgr58<EMAIL_ADDRESS>wrote:
julia /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl
WARNING: module ApproxFun should explicitly import getindex from Base
... bunch of warnings from ApproxFun deleted to save some space ...
WARNING: module ApproxFun should explicitly import transpose from Base
ERROR: LoadError: LoadError: LoadError: LoadError: TypeError: CauchyWeight: in parameter, expected Type{T}, got Tuple{TypeVar,TypeVar}
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/CauchyWeight.jl, in expression starting on line 15
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/GreensFun.jl, in expression starting on line 1
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/SingularIntegralEquations.jl, in expression starting on line 51
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl, in expression starting on line 8
Version information:
julia> versioninfo()
Julia Version 0.4.0-pre+7303
Commit 404b414* (2015-09-05 05:01 UTC)
Platform Info:
System: Linux (x86_64-redhat-linux)
CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz
WORD_SIZE: 64
BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Nehalem)
LAPACK: libopenblasp.so.0
LIBM: libopenlibm
LLVM: libLLVM-3.3
—
Reply to this email directly or view it on GitHub.

I’ve started switching over to 0.4 (which ApproxFun works fine in.  0.4 really helps reduce compile-time induced suicidal thoughts), so I’ll have a go at fixing this bug.

Sheehan

On 6 Sep 2015, at 9:54 pm, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
Thanks!
The ApproxFun suite is currently developed in Julia v0.3.x and will be until the first v0.4 release. Does it work for you in 0.3?
Cheers,
Mikael

On Sep 5, 2015, at 11:21 PM, mgr58<EMAIL_ADDRESS>wrote:
julia /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl
WARNING: module ApproxFun should explicitly import getindex from Base
... bunch of warnings from ApproxFun deleted to save some space ...
WARNING: module ApproxFun should explicitly import transpose from Base
ERROR: LoadError: LoadError: LoadError: LoadError: TypeError: CauchyWeight: in parameter, expected Type{T}, got Tuple{TypeVar,TypeVar}
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/CauchyWeight.jl, in expression starting on line 15
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/GreensFun.jl, in expression starting on line 1
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/SingularIntegralEquations.jl, in expression starting on line 51
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl, in expression starting on line 8
Version information:
julia> versioninfo()
Julia Version 0.4.0-pre+7303
Commit 404b414* (2015-09-05 05:01 UTC)
Platform Info:
System: Linux (x86_64-redhat-linux)
CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz
WORD_SIZE: 64
BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Nehalem)
LAPACK: libopenblasp.so.0
LIBM: libopenlibm
LLVM: libLLVM-3.3
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/SingularIntegralEquations.jl/issues/37#issuecomment-138076650.

This ran into a problem with (LowRankOperator.jl)
immutable LowRankOperator{S<:FunctionSpace,M<:FunctionSpace,T1,T2} <: InfiniteOperator{promote_type(T1,T2)}
I asked if there is an 0.4 equivalent
	https://groups.google.com/forum/?fromgroups=#!topic/julia-users/9OdU6d7_ogo <https://groups.google.com/forum/?fromgroups=#!topic/julia-users/9OdU6d7_ogo>

otherwise, maybe it should be restructured to only have one T, and promote the type of U and V first.

On 7 Sep 2015, at 9:19 am, Sheehan Olver<EMAIL_ADDRESS>wrote:
I’ve started switching over to 0.4 (which ApproxFun works fine in.  0.4 really helps reduce compile-time induced suicidal thoughts), so I’ll have a go at fixing this bug.
Sheehan

On 6 Sep 2015, at 9:54 pm, Richard Mikael Slevinsky<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Thanks!
The ApproxFun suite is currently developed in Julia v0.3.x and will be until the first v0.4 release. Does it work for you in 0.3?
Cheers,
Mikael

On Sep 5, 2015, at 11:21 PM, mgr58<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
julia /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl
WARNING: module ApproxFun should explicitly import getindex from Base
... bunch of warnings from ApproxFun deleted to save some space ...
WARNING: module ApproxFun should explicitly import transpose from Base
ERROR: LoadError: LoadError: LoadError: LoadError: TypeError: CauchyWeight: in parameter, expected Type{T}, got Tuple{TypeVar,TypeVar}
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/CauchyWeight.jl, in expression starting on line 15
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/./GreensFun/GreensFun.jl, in expression starting on line 1
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/src/SingularIntegralEquations.jl, in expression starting on line 51
while loading /home/xxx/.julia/v0.4/SingularIntegralEquations/examples/erfc.jl, in expression starting on line 8
Version information:
julia> versioninfo()
Julia Version 0.4.0-pre+7303
Commit 404b414* (2015-09-05 05:01 UTC)
Platform Info:
System: Linux (x86_64-redhat-linux)
CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz
WORD_SIZE: 64
BLAS: libopenblas (DYNAMIC_ARCH NO_AFFINITY Nehalem)
LAPACK: libopenblasp.so.0
LIBM: libopenlibm
LLVM: libLLVM-3.3
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/SingularIntegralEquations.jl/issues/37#issuecomment-138076650.

LowRankOperator only has one type T now! Promotions now occur in an outer constructor.

This is now held up by a segmentation fault bug in 0.4:
https://github.com/JuliaLang/julia/issues/13007#issuecomment-138396086

This should now work!

Just make sure you
Pkg.checkout("ApproxFun","development")

Thank you!
Confirming that it works with Julia 0.4.0-pre+7397 (2015-09-08 18:44 UTC Commit c252788*).
As a side comment, in order to succeed in  Pkg.build("SingularIntegralEquations") it was necessary to rename the compiler in SingularIntegralEquations/deps/Makefile from gcc-5 to gcc (gcc is the name that is used on Linux) and uncomment all lines that define M_PI related constants at the top of fundsol.c. (or use a compiler option) - see e.g. the first answer in the discussion http://stackoverflow.com/questions/5007925/using-m-pi-with-c89-standard

I think we are going to remove the build step at some point.  The package doesn't need it
Sent from my iPhone

On 9 Sep 2015, at 10:35 pm, mgr58<EMAIL_ADDRESS>wrote:
Thank you!
Confirming that it works with Julia 0.4.0-pre+7397 (2015-09-08 18:44 UTC Commit c252788*).
As a side comment, in order to succeed in Pkg.build("SingularIntegralEquations") it was necessary to rename the compiler in SingularIntegralEquations/deps/Makefile from gcc-5 to gcc (gcc is the name that is used on Linux) and uncomment all lines that define M_PI related constants at the top of fundsol.c. (or use a compiler option) - see e.g. the first answer in the discussion http://stackoverflow.com/questions/5007925/using-m-pi-with-c89-standard
—
Reply to this email directly or view it on GitHub.


Add someone to GitHub

Please include:

GitHub ID to add: Jsyro and usingtechnology
Project to be added to: Aries

One of:

Team to be added to:

Aries Contributors

Thanks!

FYI @Jsyro (Jason Syrotuck) and @usingtechnology (Jason Sherman)
Both are representing BC Gov.

Invites sent!


Types: ark-serialize dependency should use workspace

https://github.com/EspressoSystems/HotShot/blob/58690984bca20c7c60cdabc7dd6dbf5bd6d899f2/crates/types/Cargo.toml#L18-L20

why is this marked as closed while it's not using { workspace = true}
@jbearer

why is this marked as closed while it's not using { workspace = true}
@jbearer

@alxiong I just did a quick check, looks like the ark-serialize in the specified path is indeed using workspace = true.
All other ark-serializes in HotShot also seem correct, except the one in HotShot/Cargo.toml which is using ark-serialize = "0.4". Let me reopen this issue and send a quick fix for the remaining one.


keyboard shortcuts: Add keyboard basics in bottom of right sidebar.

Keyboard shortcuts completely change how people use Zulip, so it'd be great to teach this to users as soon as we can.
We should add a section to the bottom of the right sidebar which looks something like
KEYBOARD BASICS
r     Reply to message
n     Next unread topic
c     Start new topic
See all          :icon:

where:

See all is a link that opens the keyboard help modal
The icon is something like :keyboard: and toggles showing the Keyboard basics section.

@zulipbot claim

Yes
On Mar 19, 2018 12:00 PM, "zulipbot"<EMAIL_ADDRESS>wrote:
Hello @shubham-padia https://github.com/shubham-padia, you claimed this
issue to work on it, but this issue and any referenced pull requests
haven't been updated for 10 days. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let
me know that you're still working on it. Otherwise, I'll automatically
remove you from this issue in 4 days.
If you've decided to work on something else, simply comment @zulipbot
abandon so that someone else can claim it and continue from where you left
off.
Thank you for your valuable contributions to Zulip!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/issues/8605#issuecomment-374094990, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANRCIXpB2QDtMEjGY-_tlWpl3cOVCGyQks5tfy1HgaJpZM4Sfcr5
.

yes, I'm currently working on making it stick at the bottom of the right
sidebar with the resizing code.
On Mon, Apr 2, 2018 at 5:46 AM, zulipbot<EMAIL_ADDRESS>wrote:

Hello @shubham-padia https://github.com/shubham-padia, you claimed this
issue to work on it, but this issue and any referenced pull requests
haven't been updated for 10 days. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let
me know that you're still working on it. Otherwise, I'll automatically
remove you from this issue in 4 days.
If you've decided to work on something else, simply comment @zulipbot
abandon so that someone else can claim it and continue from where you
left off.
Thank you for your valuable contributions to Zulip!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/issues/8605#issuecomment-377827823, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANRCIdnl7vaNvMtQDabsJ1ra7x92corhks5tkW3agaJpZM4Sfcr5
.

@zulipbot abandon
College has been hectic lately

@zulipbot claim

yes
On Thu, May 3, 2018 at 5:41 AM zulipbot<EMAIL_ADDRESS>wrote:

Hello @shubham-padia https://github.com/shubham-padia, you claimed this
issue to work on it, but this issue and any referenced pull requests
haven't been updated for 10 days. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let
me know that you're still working on it. Otherwise, I'll automatically
remove you from this issue in 4 days.
If you've decided to work on something else, simply comment @zulipbot
abandon so that someone else can claim it and continue from where you
left off.
Thank you for your valuable contributions to Zulip!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/issues/8605#issuecomment-386158839, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANRCIRxH_QV7wnlYfem4SRxGvQ9sxrE6ks5tuktHgaJpZM4Sfcr5
.

Fixed via #9182.


docs: fix async annotation for custom server endpoint

Server endpoint documentation was missing async annotation for the function as it uses await. Quickly added this.

thank you!


Displaying Gifs

Not sure if the issue is with flutter or the library but the gifs won't display using a grid view builder.

From what I can see its the URLs. if I got to Giphy.com and get a Gif Link like https://media.giphy.com/media/2vjnYaOAqTJJ8DMCQo/giphy.gif it works.


question about "environment marker de-selection"

Hello!
I'm trying to understand why a pex built at work cannot execute properly.
If I try to execute this pex in debug mode, I have the following interesting things:
pex: Unresolved requirements:
pex:   - fqdn; extra == "format-nongpl"
pex:   - isoduration; extra == "format-nongpl"
pex:   - jsonpointer>1.13; extra == "format-nongpl"
pex:   - uri-template; extra == "format-nongpl"
pex:   - webcolors>=1.11; extra == "format-nongpl"

and somewhere else in the log:
pex: Skipping activation of `isoduration; extra == "format-nongpl"` due to environment marker de-selection
pex: Skipping activation of `jsonpointer>1.13; extra == "format-nongpl"` due to environment marker de-selection

(etc)
So, my understanding is that these packages are indeed in the pex, but due to not having the correct "environment marker" , pex decides to not activate the module.
I managed to understand where this issue of [format-nongpl] is coming from:

the lib jsonschema provides a set of optional dependencies ( link ) called "format-nongpl"
in our project, we have dependencies on jsonschema through several indirection: most of the indirection don't require the optional dependencies, but we also have a dependency on jupyter-event which indeed requires this optional dependency ( link )

Further than this, I'm a bit lost as I can't really easily built the pex myself (it's built in CI system from work, and the script is quite complex to copy/paste).
But I still wanted to understand a few things :

Is the setup I'm describing supposed to be handled by pex automatically ? ie should the pex build command be able to automatically find out and add the format-nongpl marker "by itself" in the pex file ? (or should this marker be automatically added during the build ?)
if no, can I manually override it somehow when I'm calling the generated pex file ?

I couldn't really find many infos on what exactly are "environment marker" and how they are handled
thanks!

Ah, actually it seems I can just reproduce the issue by doing:
pex jsonschema jupyter-events -o test.pex
I can't execute the resulting pex

....and if I follow what's written in https://github.com/pantsbuild/pex/issues/616 and execute:
pex --resolver-version pip-2020-resolver jsonschema jupyter-events
this works
But I'm still not sure what's going on :)

Changing defaults is a breaking change. I won't do these without a major version change. Pex 3.x will be coming this year and will change several defaults including --resolver-version pip-2020-resolver and --pip-version 22.3.

I'm going to close this as an answered question. Thanks for figuring out what options you needed.

Changing defaults is a breaking change. I won't do these without a major version change. Pex 3.x will be coming this year and will change several defaults including --resolver-version pip-2020-resolver and --pip-version 22.3.

thanks, this makes sense to not want breaking changes
just to be sure, for pip-version, we default to here : https://github.com/pantsbuild/pex/blob/25947de151c639d9cdf893e417f3f2d8a0daa051/pex/pip/version.py#L70 currently ?

That's correct, the default is a patched version of 20.3.4 that is vendored inside Pex.


Is There a Similar Function "Create-AlProjectFolderFromNavContainer" To OnPremise

Like this wonderful function Create-AlProjectFolderFromNavContainer, exists To work with  Local Database?
I means, Create-AlProjectFolderFromNAVDatabase, and this database isn't container, but in your machine installed.
I hope that I was clear.
Thanks

The reason for using containers is, that it makes it easier for me to describe how things are done (works the same way always) With on premises, I need to take care of database server versions, urls, locations etc. etc. it complicates things a lot.
Therefore, I can do much more when I can settle with containers. Having said that - everything is open source and you are welcome to decipher the functions and try to make them run without containers.

Totally clear, Ok.
Thanks.


Generate docs when compiling protos

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4cffc30dc806d15a7c70f3394cf74cd5e53d24fd
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
e9792f1a79fbeabe62837e66b173b885a6eea4aa
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
01980a926c3133a9f2e5990d91512fb93b3acc60
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
11fcfb08b9a4d183ca1e6ebb1a34f5d459562f54
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
d51ce09eb1f1e4072d29bf2cd21ce4910d295193
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
076f3a4d68a9a462c7b974bbb6825be546f06165
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
7282d873a43837083fb6373f58f243793f533d28
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
bd419a032b3e98d215c6353238b342ed94e28b37
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
25967dd54703bbdb4344173095ae8cf7883a7bd8
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
2ce294c87a9be9cd058016d14d1553d36b7d4d0e
link
/test istio-pilot-e2e

prow/istio-presubmit.sh
8ecabc0076d369c1d9a90eb4c7b9bbd7102051d3
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
bbe02003aa06b24488b89bb03f7b3ec02dfcaa34
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
bbe02003aa06b24488b89bb03f7b3ec02dfcaa34
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
bbe02003aa06b24488b89bb03f7b3ec02dfcaa34
link
/test istio-pilot-e2e

prow/e2e-smoke.sh
cb0af34d6c45ce1ce66f9f771b0d28071364dc0d
link
/test e2e-smoke

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@geeknoid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-smoke.sh
cb0af34d6c45ce1ce66f9f771b0d28071364dc0d
link
/test e2e-smoke

prow/istio-pilot-e2e.sh
cb0af34d6c45ce1ce66f9f771b0d28071364dc0d
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


How to use pix2struct for pure OCR tasks

Using the OCR-VQA model does not always give consistent results when the prompt is left unchanged
What is the most consitent way to use the model as an OCR?

You can use the fine-tuned text-caps model, train it again on ocr tasks which involves learning to generate text from a given image. I hope this will get you there.


Update rtsp_rebroadcast.cpp removed hard coded IP and made it an argu…

…ment

I am sorry I'm going to close this (public) repository is specifically for the SIYI camera, so the IP can stay hard-coded here.
(In our private copy of this application that is more generic this change is fine.)


Is it possible to support locale zh-TW?

Yes, contributions welcome.

Raised a PR - https://github.com/d3/d3-format/pull/131
Please let me know in case you have suggestions.
Thanks!

@mbostock PR - https://github.com/d3/d3-format/pull/131 has been pending since long. This fix is important for us. Can you help in getting it merged?


Add support for OSP17 deployment

I think the neutron team has plans to make RAFT clusters the default for OVN in the future, so Jetpack should also support it. Passing these parameters to the infrared deploy command enables OVN RAFT.
--config-resource OS::TripleO::Services::OVNDBs=/usr/share/openstack-tripleo-heat-templates/deployment/ovn/ovn-dbs-cluster-ansible.yaml


Adding some content related to grocery shopping

also moving don'ts related to water hoarding to different don't section.

this has two approvals, so I will merge


SWDEV-336378 - cmake support for vulkan example

Change-Id: I5ac28d2f57c1732e243674aa904cabe23be34797

Closing in favor of #2725


Segmentation Fault

make[1]: Leaving directory '/cygdrive/c/bitcrack-0.26/KeyFinderLib'
make --directory KeyFinder
make[1]: Entering directory '/cygdrive/c/bitcrack-0.26/KeyFinder'
make[1]: Nothing to be done for 'all'.
make[1]: Leaving directory '/cygdrive/c/bitcrack-0.26/KeyFinder'
asamp@DESKTOP-C6SDA8C /cygdrive/c/bitcrack-0.26
$ ./clbitcrack 1FEExnBQziLgNKJzXUy1t5jqN2BK6yACCU
Segmentation fault
Please how do I debug this?

Question: what exactly do you want to do? What is the operating system? If Windows, is it not easier to download the compiled binary?

And where do I get the compiled binary from?

for Windows (x64) https://github.com/brichard19/BitCrack/releases


Using GUI Visualizer to change marker positions (by dragging): new positions are not saved

https://docs.google.com/spreadsheets/d/1E9Em79S5Y52hfAePmK-XcvTcPYwFWQBSchYemuWYTfE/edit#gid=1519816561

@chrisdembia I just loaded arm26, saved it in 4.0, changed the location of a marker and saved and the changes were saved. There must be a specific scenario to reproduce. Any details? @carmichaelong can you reproduce? Thank you

@carmichaelong let me know if you want to work together on reproducing this.

For the record, I tested only editing the numbers in the Properties panel and not other ways (e.g. Graphically dragging or changing the Frame the marker is attached to, or loading Markers from file and editing or creating a new Marker and edit 😸 ) Would be good if a witness can help us narrow the search path.

The issue was specifically moving the marker graphically. Sorry that wasn't clera.

I am having some difficulty reproducing the situation.
Rachel was also saying the issue is sporadic; it doesn't always happen.
Whether or not a marker is fixed can also complicate the matter.
@rwj1 could I come by the HPL to observe the bug?

@chrisdembia FYI I also haven't been able to reproduce yet.

@chrisdembia @carmichaelong @jenhicks I'm woking on a fix to refresh the text faster and allow undo, but it is not clear if related or if it should be in this last sprint. Let me know your thoughts.

Nice investigative work @chrisdembia
Loading markers from a file has changed a few times including last time when we moved MarkerSet to be component, every Marker addition likely goes through the expensive initialization sequence (though 20 seconds is too much and I'm sure we can optimize).
In step 5, do they get different behavior if they click in the Navigator or elsewhere in the application?
Is it the case that one of the 3 markers didn't move while the two others did? Just clarifying

Lauren sent me her own files and I still could not reproduce the issue. The markers did take a long time to load on my computer.
Could the issue be related to the speed of the computer? Or Windows vs Mac?

I don't think it's the speed of the computer, or Mac vs. Window,  I'd suspect it's model having lots of muscles and wrapping objects that take forever to render/initialize. We could try to add all Merkers at once I just want to make sure we understand the scope.

In step 5, do they get different behavior if they click in the Navigator or elsewhere in the application?

Yes, all 3 markers move if they first click in the Properties area.

Is it the case that one of the 3 markers didn't move while the two others did?

Correct.

Thanks for reviewing.

Then I think I have a fix for this (other than perfomance) to make the properties window update as soon as the user is done dragging. I just need to get my environment up again.

Sounds good.
I could not reproduce on Windows.

If we can pass the Mac build to Lauren or Rachel to confirm that would be awesome since we couldn't reproduce on our machines. Thanks @chrisdembia 👍


Add Darwin case for java.swt

Fixes crash on Darwin when running nix-env -qas.

Thanks, however I'd like to handle this better as I'm seeing more cases like this lately. So better give a good sample for the future. Can we have a map stdenv.system -> url/sha ? Something like:
let
  archmap = { "x86-64-linux" = { arch = "..."; sha = "..."; }; ... };
  metadata = assert archmap ? stdenv.system; archs.${stdenv.system};
in ...

Thanks for the advice, @lethalman. That's certainly much cleaner!

I saw this build error happen on a Travis build for a different branch, meaning it's likely not the fault of this PR. Is there a way to re-invoke the Travis build?


Read and write 32-bit value

Hi,
to read and write 16-bit value I use -s 0x2
It's good also to full manage 32-bit value or I need to use another argument?
Thanks a lot

32-bit is 4 bytes (one byte is 8 bits in architectures that this tool supports), so -s 0x4 is adequate.


Update pom.xml version to 0.6.1.

The maven release plugin is not able to push the changes to the version though. At least that was the reason why the build failed for the last release 0.6.1.

See:
https://app.circleci.com/pipelines/github/envoyproxy/protoc-gen-validate/1020/workflows/b558e11b-fee8-40dc-99af-358d5fa8e202/jobs/1946?invite=true#step-105-2125

The java release is blocked by expired GPG keys #486

I just released Java 0.6.1 from master.


Intel QAT accelerated Multicloud GitOps pattern

Add documentation for Multicloud GitOps pattern accelerated with Intel QAT

This is an automated message:
You can preview this docs PR at http://421.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.

/ok-to-test


[question][license] What is the license to use the code

Hello,
Thank you for this code and for your efforts.
What is the license for code usage?

It's MIT licensed, I just added the license 👍


Add support for DNS over TLS (RFC 7858)

Support for DNS over TLS (as specified in RFC 7858) would be nice:
https://tools.ietf.org/html/rfc7858
It's very simple to implement, you basically just put nginx as TLS frontend in front of the TCP port of the normal nameserver. Since RFC 7858 got assigned its own port 853, it won't interfere with normal operation. A quick configuration example can be found here:
https://dnsprivacy.org/wiki/display/DP/Using+a+TLS+proxy
The reference client implementation for RFC 7858 seems to be "stubby", which is built upon a library called "getdns". I'd recommend simply reusing getdns's default list of ciphersuites:
https://github.com/getdnsapi/getdns/blob/develop/src/context.c#L1426
Since release 1.3.0, getdns also supports TLS 1.3, however this requires OpenSSL 1.1.1, which is not released yet. To get support for TLS 1.3 on the server side, you'd equally have to build nginx using OpenSSL 1.1.1. Whilst some features of TLS 1.3 (0rtt) would obviously be nice to have, TLS 1.2 should be sufficient for the time being. TLS < 1.2 and/or non-PFS cipher suites should explicitly not be supported (stubby, which is by far to most widespread client implementation, does the same).
It seems that Google is currently working to include support for DNS over TLS into one of the next Android releases, so this will hopefully gain more momentum than DNScrypt did.
https://android-review.googlesource.com/q/topic:dns-dev-opt+(status:open+OR+status:merged)

We're considering to implement DNS over HTTPS instead, as that seems to have a few advantages.
@hardfalcon , do you have any strong opinions on pros and cons?
The plan is to revisit this once dnsdist 1.4 is released (it comes with a few improvements in that area).

First: I'm not opposed to DoH in any way - I have actually am running my own private DoH resolver in parallel to my DoT resolver, and I have started using the DoH resolver as the only DNS resolver on several machines I use every day, both on a Laptop and on Desktop computers (it's probably just an implementation or configuration issue, but when compared to DoT, DoH has far less issues with frequent network disconnects on my Laptop).
Of course, DoT and DoH can be run in parallel on the same server without interfering with each other - and my recommendation would be to just run both and look at the usage statistics.
However, with the current landscape of DoT and DoH implementations, DoH currently seems pretty useless to run on authoritative name servers (this may of course change in the future). Apart from manual debugging, authoritative name servers typically get queried by recursive resolvers like unbound, knot-resolver, PowerDNS or BIND in recursive mode. The problem is: none of these recursive resolver implementations seem to have a DoH client implementation (which they would need to make use of your DoH server), and none of those projects seem to be even just considering the possibility of adding such a DoH client implementation. Knot-resolver (and, as you mentioned, PowerDNS dns-dist 1.4) do only implement the server part of DoH, unbound and BIND implement none of both.
On the other hand, at least unbound has a DoT client implementation (along with a DoT server implementation), and can even be configured to only use (and require) DoT for certain zones while using traditional unencrypted DNS for the rest.
All the DoH client implementations that I'm aware of are only stub resolvers or DNS forwarders, so they probably won't be able to make actual use of your DoH server in any real-world usage scenario. The closest thing that I am aware of would be unbound's ability to download BIND zone files from a HTTPS server when run in authoritative mode - but that's of course a very different beast and can certainly not be considered an actual DoH client.

Thanks for these insights! Does your argument about missing DoH support in resolvers also apply to DoT?

https://arxiv.org/pdf/1907.08089.pdf may be interesting

Unfortunately the paper only covers the recurser. What we can learn though is that bare look-up times are slower with DoT and DoH in nearly all cases, but page load times may be faster using DoT. Cloudflare, Quad9 and Google all offer DoT and DoH. The paper also mentions censorship resistance as an advantage of DoH, as it uses port 443.
To conclude, I don't see a big advantage to offer DoT or DoH for our authoritative name servers currently. The benefits are marginal, and we have more important items on the agenda. If someone volunteers however, I'm happy to accept a contribution.


feat: Add support for typescript files and ESModules.

When relying on third party dependencies that are ESModules (which is getting more popularity in the Node.js community it is important to be invoked by an ESModule.
Currently the @oclif/core already works when using pure ESModules by setting the "type": "module" inside the package.json.
But if you want to leverage typescript you currently need to compile the typescript sources to the lib folder by running npx tsc --project tsconfig.json. This will compile the command inside the lib folder. After that running ./bin/run.js will work.
IMHO this developer experience can be enhanced by leveraging ts-node to directly run the typescript sources.
All that the developer now needs to do is to specify the ts-node/esm loader when invoking the binary by updating the binary file with the following content:
The file bin/run.js
#!/usr/bin/env node --experimental-specifier-resolution=node --no-warnings --loader ts-node/esm
import { Errors, flush, run } from '@oclif/core';

run(void 0, import.meta.url)
  .then(flush)
  .catch(Errors.handle);

now it can be invoked by running NODE_ENV=development ./bin/run.js and it will use ts-node to transpile the modules on the fly and resolve them correctly with this changes.
A better DX as first compiling and then running IMHO.

I've signed the CLA but it seems not to update:

Yes please! I am trying to do exactly this with a library that is required to be an es module, and I am using typescript and I am pulling my hair out. +1 +1 for getting this pulled in


The loss doesn't seem to converge after 1000 iterations

I'm working on the C version of the code in preparation for (#40)
So llm.c with no code modifications I observe the following:

test_gpt2 works successfully and the loss matches
train_gpt2 after 1000 iterations the loss sill hovers around 4.0

I notice similar behaviour for 40 iterations on the README

I'm curious if this a platform specific bug (I'm using Intel Xeons rather than ARM) or something with the code itself. Also GPT2 may take many iterations and I need to wait longer. Any guidance would be useful.

I think it's because the first few iterations are super easy gains and after that they get much less easy. Also the dataset is super tiny, so it may be that one cannot do much better on the val loss. The train loss should continue to improve though, if you smooth it enough, or evaluate it over a large set of batches and average. Also note that default training on non .cu version is tiny - batch 4, seq len 64.

I see other implementations train for 10000's of steps and on other base models to get lower losses on tinyshakespeare and tinystories. Bunch of interesting papers.
You compare the outputs of different CFLAGS, might make minor differences. (also add -march=native)

Both of your advice was quite useful. I ran it a little more an the losses eventually converged.
However, validation loss >> training loss, which suggests over fitting.

Do you have any suggestions for larger data sets?
Are there any training parameters I can adjust?

As a side note, the distributed MPI implementation is pretty much done.


Broken links

Hi, just fyi, the second link in the readme (for Apache 2.0 License Evaluation) is broken.
https://github.com/stan-dev/math/blob/e0884615b80182965f78cbf21cfe044d7b170e3b/README.md?plain=1#L21
This link is broken in the Stan readme as well.
Edit: The contributing link is broken as well. https://mc-stan.org/math/contributing.html
Edit 2: Same with Sundials. The updated link is https://computing.llnl.gov/projects/sundials

Thanks  @ankane, should be addressed by #2735

Thanks @rok-cesnovar!


Create Splash Screen

See https://docs.expo.io/versions/latest/guides/splash-screens.html

Not important now.


Synthesis failed for Google.Cloud.PubSub.V1

Hello! Autosynth couldn't regenerate Google.Cloud.PubSub.V1. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth-Google.Cloud.PubSub.V1'
Cloning into '/tmpfs/tmp/tmppmne_579/googleapis'...
Note: checking out '88316b63a486002727e14032d104690541179fc9'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 88316b63a Generated synth.py files with multiple commits enabled
Note: checking out '7be2811ad17013a5ea24cd75dfd9e399dd6e18fe'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 7be2811a fix: Update gapic-generator version to pickup discogapic fixes
Switched to a new branch 'autosynth-Google.Cloud.PubSub.V1-2'
Running synthtool
['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-03-30 07:26:23,646 synthtool > Executing /tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.PubSub.V1/synth.py.
Contents of preconfig file:
{"preclonedRepos": {"https://github.com/googleapis/google-cloud-dotnet.git": "/tmpfs/src/git/autosynth/working_repo", "https://github.com/googleapis/googleapis.git": "/tmpfs/tmp/tmppmne_579/googleapis"}}Extracted repo location: /tmpfs/tmp/tmppmne_579/googleapis
generateapis.sh: line 40: declare: GOOGLEAPIS: readonly variable
2020-03-30 07:26:23,693 synthtool > Failed executing /bin/bash generateapis.sh --check_compatibility Google.Cloud.PubSub.V1:

None
2020-03-30 07:26:23,695 synthtool > Wrote metadata to synth.metadata.
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/git/autosynth/working_repo/apis/Google.Cloud.PubSub.V1/synth.py", line 22, in <module>
    hide_output = False)
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/git/autosynth/env/lib/python3.6/site-packages/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '('/bin/bash', 'generateapis.sh', '--check_compatibility', 'Google.Cloud.PubSub.V1')' returned non-zero exit status 1.
Synthesis failed
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 482, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 334, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 429, in _inner_main
    branch,
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 135, in synthesize_loop
    metadata_path, extra_args, deprecated_execution, environ, synthesize_py_path,
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 278, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/git/autosynth/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Added jetstream strength and latitude calculation

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #923

[x] Tests for the changes have been added (for bug fixes / features)
[x] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)

[x] Link to issue (:issue:number) and pull request (:pull:number) has been added.

[x] bumpversion patch has been called on this branch
[x] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?

Calculation of strength and latitude of jetstream. This code will return two DataArrays but can easily be split into two methods or modified to return a single Dataset if that's more convenient.

Does this PR introduce a breaking change?
Other information:

[x] We need to add Tom Keel (@Thomasjkeel, thomas.keel.18 at ucl.ac.uk) to the list of contributors.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 27 (7.41%)  changed or added relevant lines in 1 file are covered.
18 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.3%) to 90.069%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/indices/_threshold.py
2
27
7.41%

Files with Coverage Reduction
New Missed Lines
%

xclim/core/locales.py
1
90.2%

xclim/core/units.py
1
89.8%

xclim/indices/fwi.py
1
96.11%

xclim/indices/run_length.py
1
94.61%

xclim/core/indicator.py
2
96.53%

xclim/core/utils.py
12
68.44%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
12606

Relevant Lines:
13996

💛  - Coveralls

The build is failing because of a new dependency (cf_xarray). Once you've added this new dependency to the setup.py,  please also be sure to add that information to the breaking changes (on the PR description and in the history - on its own line). Thanks!

Thanks for reviewing @huard. Just released that I should have pushed commit suggestions in one go (instead of individually in the browser), so sorry if you got sent a lot of emails just then (it is getting late in the UK!). Thanks everyone for all your help in getting this PR ready (up until this point), been a really valuable experience!

@raquel-ucl @Thomasjkeel Thanks for the PR !


Add Samba-CoE-v0.2 to AlpacaEval

We would like to add Samba-CoE series models to AlpacaEval!
Details of the two models can be found here: https://sambanova.ai/blog/samba-coe-v01-composition-of-experts
HF space hosting the endpoint: https://huggingface.co/spaces/sambanovasystems/Samba-CoE-v0.1
We are also looking for further collaborations and contributing back to the open-sourced LLM community, we provide completely FREE API endpoints for 50+ popular opensourced models in the market, let me know if you guys are interested in working together to verify those models or any models beyond! Here is the entry point to the said APIs:
https://sambaverse.sambanova.net/

Impressive results, thanks @kyleliang919! 💯
Happy to merge any evaluation of the opensource models on sambanova (very cool!) but I won't have time to run those myself!


Goals for 1.0

I should get this package to 1.0 when I eventually find some more time. Some goals before doing so:

[ ] Better default methods for interface methods (#62)
[ ] Provide supporting for clipping Voronoi tessellations on more general geometries (#48)
[ ] I want to eventually support curved segments. I don't think this will be in 1.0, but I should at least double check that the interface I currently use could be easily extended to support a more general definition of a boundary (e.g. I provide a function defining a boundary which I can then sub-sample to get boundary notes until I have "enough", as is required for some curved boundary methods).
[ ] Spatial sorting is a big need (#34). I just haven't found a good reference for it.
[ ] Better support should be provided for cleaning up a user's input if needed, or at least making it possible. There is currently check_args that has to be used e.g. for disjoint domains - I wonder if that can be modified somehow (it's currently like that because I don't know of an efficient way for testing if a domain is in disjoint components). This could be something separate to triangulate, since it is nice to assume that everything is working (if a user provides duplicate points, should I remove them? error? continue? etc. This is hard to think about since it may make the user use e.g. each_point which will include the duplicate points but won't match the vertices in the triangulation). A related issue is #42. This can probably be done before or after 1.0, but I should think about it first.
[ ] Of course, it would be nice to resolve #49 and #44, but those can be done anytime. Not a priority right now, though.

I wonder if, once curved boundaries are supported, I should remove Gmsh support. I guess it doesn't hurt to keep it, but my implementation (1) only exists because I didn't have CDT/refinement support at the time and (2) is quite limited compare to Gmsh support in other Julia packages.


Fix/stm32f746 examples

This PR updates the mbed project generation for the hello_world and micro_speech examples for the disco_f746ng board. Based on a recent PR addressing this issue regarding "the TAGS command line option is no longer supported in the TFLM Makefile".

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!


Show me what's new

If I come back to MapRoulette after not having logged on for a while, show me what the new challenges are that have been added, especially ones that are being worked on actively.

At the very least, I think we should have a "New Challenges" section on the new user dashboard once that is implemented.
UI/UX: Does it also make sense to have a special icon for challenges that are new for areas like results on the challenge search page?


Add PSR-7 ServerRequestInterface to the PSR-7 Request

This PR adds a PSR-ServerRequestInterface to the request.
This won't handle server params, cookies or uploaded files. This will be addressed in several other PRs.
The new class makes it possible to handle parsed request bodies (#105 for v0.8.0).

Just noticed that the Server inline examples are all still using RequestInterface instead of ServerRequestInterface


Create AccessFromCentralDomains.php

add middleware run only central domain . invert PreventAccessFromCentralDomains  . i have module cms we need run cms route only in central domain

What does this solve? And does it need to be part of the package? You can just use your own middleware. This would also need to be documented if it's added.


multi-instantiable

Multi-instantiable of the module with one instalment. Just add configuration in config.js

@ulrichwisser Check plz.


Add people with merge rights

Nothing has happened with this plugin for a long time despite some issues. If @jan-molak is too busy, maybe more people should be added to the project to offload?

Help would be greatly appreciated, let me know if anyone has capacity to become the member of the "core team" :-)

I would love to, but I'm not sure I'm really qualified nor that I have much more time than you.
However, since it's in my and my company's personal interest to have some of the outstanding PR:s merged, I'd certainly be willing to have a look at them.
Specifially my own PR #293 as well as #365

Maybe you should at something to the readme and/or the plugin wiki that you're looking for contributors?

I'll start looking at that.
However, I had to add proxy support to make tests work behind proxy, so I added a PR for that (#368).
However, not all tests go through and they shouldn't be related to the proxy stuff, so I wonder if the tests are working for you in the master branch?

The master branch is also broken. The problem is that the tests will pull the latest version of the plugins that the build-monitor plugins can integrate with (using the install manager) but those plugins are not compatible anymore with the jenkins core that is being used.
In my opinion this is two different problems:

The tests should use the versions as declared in the pom (and make sure these exact plugin versions are installed and not the latest).
The jenkins core version used should be maintained to a reasonable baseline.

@dcendents ok, I see!
Would bumping to the latest Jenkins version break compatibility with older versions? I.e. would it be better to bump to a newer, but not the latest version?

Look at this: https://wiki.jenkins.io/display/JENKINS/Choosing+Jenkins+version+to+build+against
I suppose the best thing would be to keep a low version (2.19.4), test against that version but also find a way to test against the latest LTS as well (maven profiles?).

Okay thanks.
I'll do it in two steps then.
Currently I'm working on getting the current master to work with the old version of Jenkins by defining specific plugin versions.
After that I'll see what has to be done to run on later Jenkins versions

The more I think about it maybe we should let the install manager as it is and install the latest version of the plugins.
Since 2.46, jenkins have introduced different update sites to make sure we get only plugins compatible with a given core version.
e.g.:

https://updates.jenkins.io/stable-2.46/update-center.json
...
https://updates.jenkins.io/stable-2.107/update-center.json

So it might be a good idea to keep the current behavior as it would test what the users experience. It means the tests might break when a dependent plugin is updated but at least we are testing the reality.
So we could update the core version to 2.46.3 and find a way to test every LTS release since then. If a new LTS release breaks the build, we either try to be backwards compatible or we increase the core version and it means only people using the latest LTS will get the new features. People using and older version will still be able to install an older version of the build monitor that was compatible with that specific LTS version.
e.g.:

BuildMonitor 2.0 -> Jenkins 2.46+
BuildMonitor 2.1 -> Jenkins 2.107+

If I use jenkins 2.89.3, the update site would let me install version 2.0 which is fine for me. To get new features I need to update jenkins to 2.107.1

Yeah that sound's like a plan. And I was almost done with fixing the master branch the old way 😏

I'll still do it twofold, though, although the steps will be

Bump Jenkins version to 2.46.3 and fix everything
Implement future-testing

Actually, three-fold:

Bump Jenkins version to 2.46.3 and make it work with old groov

Status update:
I've bumped the Jenkins version to 2.46.3, the org.jenkins-ci.plugins:plugin parent to 3.8 and the jenkins-test-harness to 2.38.
The bumped parent pom includes a lot of new Maven Enforcer rules and findbugs rules that I had to solve, so after wrestling with conflicting dependencies, and bumping some here and there and simply overriding some rules I've gotten everything to compile.
build-monitor-plugin builds without issue now, while pretty much every test in build-monitor-acceptance fails. So the next step is to solve that.
I haven't merged in #365 yet, though, as I want as much as possible working before I do that.

Another status update:
I've gotten 6 of 11 tests to work. It has mostly been updating selenium tests that has been necessary.
I've also had to wrestle some with getting the ITs to work on a Windows/WSL environment but it works now.
I still haven't run into any issues regarding #364 but I think one test might have that issue (Badges) so I'll leave that for last.
Hopefully I'll have a PR soon. I hope to be able to work on it the coming evenings. It would be great if both @jan-molak and @dcendents could have a look at it then.

@jan-molak and @dcendents please have a look at #369.
Note that I have ONLY bumped the Jenkins version in that. I haven't merged the #365 PR, nor have I made forward-testing possible. I think that should be a combined second step after this is merged.

@erikhakansson sounds like a plan! I've merged #369, happy to help with the subsequent PRs.
Jan

Thanks @erikhakansson , I was actually logging in to check the work like you asked, I'm glad @jan-molak had time to do it and merge it.

I've solved compatibility with both 2.46.3 and 2.107.2, but I managed to broke a couple of tests in the process so I'm working on solving them.
However, I'm having some difficulties in automating testing both. When manually setting ${jenkins.version} it works. When adding executions to run both in different phases, using one ${jenkins.version} property and one ${jenkins.lts.version} property I get weird errors in Jenkins. I think it's related to the Jenkins Test Harness forcing the ${jenkins.version}.
For now I added a profile -Plts-test that changes ${jenkins.version} to 2.107.2 and that way it works, but it would be far prettier to have it as part of the normal mvn clean verify process.

I was thinking about the problem and I suppose it cannot be done easily with a single maven module. To run both sets of tests I think you will need to split them in different modules.

build-monitor: common parent

build-monitor-plugin: the plugin
build-monitor-acceptance: Becomes a parent, can define common dependencies here

build-monitor-acceptance-base: Java tests against base version, will also produce a test-jar
build-monitor-acceptance-latest: Run same tests (from build-monitor-acceptance-base test-jar) against latest lts

It shouldn't break the builds with cloudbees' jenkins.
Otherwise we could start different jenkins instances (using docker) and configure a selenium grid to run the tests against both of them at the same time. But it might be harder to configure that in a free publicly available build server (cloudbees, travis, etc).

Well it seems the "standard" way of testing plugins against other jenkins version is to use the plugin-compat-tester: https://github.com/jenkinsci/plugin-compat-tester
The documentation is a bit poor but they have an example here under Testing plugins against Jenkins 2.102 and above: https://jenkins.io/blog/2018/01/13/jep-200/
This means the tests would need to be run manually though.

Unless I misunderstand, plugin-compat-tester isn't really for automated testing, right?
I went with your first suggestion, splitting upp acceptance into two modules.
PR #370 is waiting for review 😄 @jan-molak I added some comments for you where I was unsure of stuff.

#370 is updated.
I noticed that an old version of maven-enforcer-plugin was hardcoded in one of the submodules so I removed that to enable inheritance from the parent pom. I haven't had any issues locally but it could be related to your build troubles.

Ping @jan-molak had any time to check the PR?
I'm running it locally at work here (Well actually, I'm running #293 , but I've rebased that on #370) and it works fine.

Also, I have a suggestion with dealing with the backlog of PRs. Since a lot of them, if not most, need to be rebased on the Jenkins 2 functionality, you could close all of them with a message like "Major changes have been made to Build Monitor Plugin. Therefore I'm closing all older PR's. Please rebase you PR against master and reopen pull request if still relevant". Or something.

#370 builds fine for me as well. I had some small improvements I wanted to submit, I'll rebase on that and add some acceptance tests.

Awesome, let me take a look :-)

Thanks!
I've added #371 to hopefully solved the issue you had.

Thanks! The build has just succeeded on Jenkins, so you can take the hpi for a spin if you'd like.

Great news! Thanks! :smile:
I've also rebased #293 which was my initial motivation for getting involved :smile:
I'd be very happy if you could have a look at that!

Any news, @jan-molak ?
Both on a release of the current state and on #293

Hi @erikhakansson! I've released the last build and should have some time over the next week or two to look into #293. Thanks for your efforts!

Great, thanks!

Had time yet? :smile:

That sounds great!
I think that some merge and release rights would be the best course of action to avoid stagnation!


Green Grass & High Tides - Remastered by The Outlaws unsupported.

Check if issue with swaglyrics or whether song lyrics unavailable on Genius.

stripper -> The-Outlaws-Green-Grass-and-High-Tides
version -> 0.2.9

https://genius.com/The-outlaws-southern-rock-band-green-grass-and-high-tides-lyrics


gulp documentation runs out of memory

The relevant bit is this:
ATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
The end of the console output is below. Note the first line.
[10:10:05] Finished 'documentation:projects' after 44 s
<--- Last few GCs --->
87956 ms: Mark-sweep 1364.2 (1434.7) -> 1362.5 (1434.7) MB, 926.5 / 0.0 ms [allocation failure] [GC in old space requested].
88878 ms: Mark-sweep 1362.5 (1434.7) -> 1362.4 (1434.7) MB, 921.8 / 0.0 ms [allocation failure] [GC in old space requested].
89811 ms: Mark-sweep 1362.4 (1434.7) -> 1362.4 (1410.7) MB, 932.9 / 0.0 ms [last resort gc].
90732 ms: Mark-sweep 1362.4 (1410.7) -> 1362.4 (1410.7) MB, 920.1 / 0.0 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x121b8a6cfb51
1: emit [events.js:~136] [pc=0x198642d24786] (this=0x205b916410a1 <a DestroyableTransform with map 0x21429a4e3a61>,type=0x121b8a6dd349 <String[4]: data>)
2: arguments adaptor frame: 2->1
3: flow [/Users/jmedley/Documents/tools/sw-helpers/node_modules/vinyl-fs/node_modules/readable-stream/lib/_stream_readable.js:~617] [pc=0x198642cd5e7f] (this=0x121b8a6e6ec1 ,src=0x...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
1: node::Abort() [/usr/local/bin/node]
2: node::FatalException(v8::Isolate*, v8::Localv8::Value, v8::Localv8::Message) [/usr/local/bin/node]
3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node]
4: v8::internal::Factory::NewFixedArray(int, v8::internal::PretenureFlag) [/usr/local/bin/node]
5: v8::internal::LCodeGenBase::PopulateDeoptimizationData(v8::internal::Handlev8::internal::Code) [/usr/local/bin/node]
6: v8::internal::LChunk::Codegen() [/usr/local/bin/node]
7: v8::internal::OptimizedCompileJob::GenerateCode() [/usr/local/bin/node]
8: v8::internal::Compiler::FinalizeOptimizedCompileJob(v8::internal::OptimizedCompileJob*) [/usr/local/bin/node]
9: v8::internal::OptimizingCompileDispatcher::InstallOptimizedFunctions() [/usr/local/bin/node]
10: v8::internal::StackGuard::HandleInterrupts() [/usr/local/bin/node]
11: v8::internal::Runtime_StackGuard(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/bin/node]
12: 0x198641e092a7
Abort trap: 6

Just to clarify: this is using gulp documentation

I'll file a PR to update the documentation dependency, which I'd been meaning to do anyway. Maybe it's resolved in a more recent release.
Also, @jpmedley, what does node --version say?

Upgraded to 7.4.0 and getting an identical message.
This is on mac.

I believe @gauntface fixed this with https://github.com/GoogleChrome/sw-helpers/pull/154


Fix post message handling

Codecov Report

Merging #119 into master will increase coverage by 0.54%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   44.03%   44.58%   +0.54%
==========================================
  Files           8        8
  Lines         822      812      -10
==========================================
  Hits          362      362
+ Misses        433      423      -10
  Partials       27       27

Impacted Files
Coverage Δ

server/plugin.go
54.17% <0.00%> (+1.62%)
:arrow_up:

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 9f1a26e...9168325. Read the comment docs.


Backup Authentication Method

Our environment is currently syncing on-premises AD to Azure AD. While we don't mind syncing password hashes, we would like to synchronize password expiry and the most effective way to do that is with passthrough authentication. That said, our only concern is high availability. Our DCs are all on the same campus. If we have a disaster that suddenly incapacitates our campus with all of our DCs, our identity management would also be down. Even if we have a cloud DC, we would have it VPN to our campus where it would then communicate to Azure AD, but that would still be a problem in that scenario. Is there any way to continue syncing password hashes, even with passthrough authentication turned on? That way if passthrough authentication fails, there will still be a method for authentication?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e4e5a986-727e-a83d-568f-304ec86caef3
Version Independent ID: 8d384088-0ae0-d111-a10b-173720a9106b
Content: Azure AD Connect: Pass-through Authentication
Content Source: articles/active-directory/connect/active-directory-aadconnect-pass-through-authentication.md
Service: active-directory
Product: unspecified
GitHub Login: @swkrish
Microsoft Alias: billmath

@marmstrong94 Thanks for your feedback! We will investigate and update as appropriate.

@marmstrong94 I would like to know more on synchronize password expiry requirement for which you are looking for Pass Through Authentication. However, the best place to discuss and get guidance is in forums. Please open a MSDN forum where we further discuss this scenario. Also forum community thread is check by other community members and could provide their expert guidance on your scenario based on their experience. Please post the forum thread once open here and I will make sure that you are provided with necessary guidance,
Please let us know if you have any issue with the content of this document and we will work on it to addrress your feedback.

@marmstrong94 We will now proceed to close this thread. As mentioned above, please post the forum URL here so that I could monitor and ensure necessary guidance is provide on it.


Implement onWebSocketMessageFragment

Make sure that fragment messages can be received by wrapping the corresponding method
https://github.com/TooTallNate/Java-WebSocket/blob/e43bb7638ebd61b6213aa3553048c4ef887f19d9/src/main/java/org/java_websocket/WebSocketAdapter.java#L75

This should be fixed with release 1.4.0 by using the normal onMessage methods in MATLAB.


Semantic Hub Release 23.12 Security Acceptance Criteria

Release Security 23.12
Source in Catena-X Confluence and Expert Contacts here(Source only accessible for Catena-X Consortia members in current transition phase).

[ ] Threat Modelling Analysis results
Analysis completed (operations excluded):

List of risks generated or updated, rated & actions defined
Risks accepted or mitigation actions implemented and tested
no high threats acceptable

Artifact Repository:

risk register (decentral on Catena-X confluence)

Prime Contacts:

Security Team: SEC0

[ ] Static Application Security Testing (SAST)

code must be scanned weekly with Veracode tool
medium risks require mitigation statement
high and above not accepted

Best Practise:

Confirm relevant repository as early as possible to SEC team to enable regular, automated scans. Evidence required for Gate approval.

Artifact Repository:

Veracode UI
(+ GitHub Action)

Prime Contacts:

Security Team: SEC1

[ ] Dynamic Application Security Testing (DAST)
incl API testing (if applicable)

all findings assessed
high & very high findings mitigated
evidence by re-scan

Best Practise:

Confirm relevant repository as early as possible to SEC team to enable regular, automated scans. Evidence required for Gate approval.

Artifact Repository:

INVICTI tool

Prime Contacts:

Security Team: SEC3 SEC4

[ ] Secret scanning
Scan executed centrally by SEC team and ZERO valid findings
Artifact Repository:

Veracode or alternative tool
GitHub Secret Scanning
GitGuardian

Best Practise:

Confirm relevant repository as early as possible to SEC team to enable regular, automated scans. Evidence required for Gate approval.

Prime Contact:

Security Team: SEC1

[ ] Software Composition Analysis (SCA)
Dependencies must be scanned with Veracode tool with regards to vulnerability

high and above not accepted
FOSS whitelist policy has to be passed

Best Practise:

Confirm relevant repository as early as possible to SEC team to enable regular, automated scans. Evidence required for Gate approval.

Artifact Repository:

Veracode UI
(& GitHub Action)

Prime Contacts:

Security Team: SEC1

[ ] Container Scan conducted
All containers in GitHub Packages must be scanned

High / Critical findings not accepted

Best Practise:

Confirm relevant repository as early as possible to SEC team to enable regular, automated scans. Evidence required for Gate approval.

Artifact Repository:

Trivy
via nightly GitHub Action

Prime Contacts:

Security Team: SEC2

[ ] Infrastructure as Code
IaC code must be scanned.

Error findings not accepted

Best Practise:

Confirm relevant repository as early as possible to SEC team to enable regular, automated scans. Evidence required for Gate approval.

Artifact Repository:

KICS or alternative tool
via nightly GitHub Action

Prime Contacts:

Security Team: SEC2

@Security Team: SEC0
Threat Modelling Analysis results:
risk register
Security Assessment Semantic Hub
(Source only accessible for Catena-X Consortia members in current transition phase)

Security Team: SEC1
Secret scanning:
Secret Scanning (gitleaks) is activated and available: https://github.com/eclipse-tractusx/sldt-semantic-hub/actions/workflows/gitleaks.yml

@Security Team: SEC1
Static Application Security Testing (SAST):
One medium finding which is mitigated - LocalOauthSecurityConfig.java is only used for local development.
See also: https://analysiscenter.veracode.com/auth/index.jsp#ReviewResultsAllFlaws:47240:1397649:30667647:30637878:30653528::4406299

@Security Team: SEC1
Software Composition Analysis (SCA):
Application is scanned and third-party compnents are scanned:
https://analysiscenter.veracode.com/auth/index.jsp#ReviewResultsSCA:47240:1397649:30667647:30637878:30653528:::::4406299:

@Security Team: SEC2
Infrastructure as Code

Security Team: SEC1
Static Application Security Testing (SAST):
one medium finding which is mitigated.
Please have a look: https://analysiscenter.veracode.com/auth/index.jsp#ReviewResultsAllFlaws:47240:1397649:30762585:30732799:30748449::4406299

Software Composition Analysis (SCA):
Please have a look here: https://analysiscenter.veracode.com/auth/index.jsp#ReviewResultsSCA:47240:1397649:30762585:30732799:30748449:::::4406299:

Hi All,

 **SCA Passed**

@Security Team: SEC3 SEC4
Dynamic Application Security Testing (DAST):
Invicti scan has been made - the results can be seen here:  https://www.netsparkercloud.com/scans/report/7894969dc61a46834bf3b0c002e1fd39/

@Security Team: SEC2
** Container Scan conducted:**
currently under clarification as Trivy scan is marking some unresolvable findings.

Hi,
there are no open GitGuardian findings:

-> Secret scanning approved
Best regards
Daniel

Hello,
No critical/high findings reported back by the Invicti scan.

Please address the potential XSS medium-severity before the next QG.
DAST PASSED
Best regards,
Piotr

@kelaja , @guenterban
Hi together,
I had a quick check in front of the upcoming QG meeting at Monday.
There still some checks open:

Threat Modelling Analysis results
Static Application Security Testing (SAST)
Infrastructure as Code

Please have a look at that open points.
Many thanks in advance!
Best regards
Simone


Binary search: check for non-sorted input defeats the purpose of binary search

Checking for non-sorted input is an O(n) operation. Performing the actual binary search is O(log(n)). Forcing the inclusion of an O(n) operation in the implementation of an O(log(n)) algorithm is confusing.
If you don't know that your input is sorted, there's no point in doing a binary search (sorting or checking for sorted input takes at least as long as a linear search), so I think this requirement should be removed.

You mean in the example implementation?

The example implementation has this issue, but only because the tests require it to check for sorted input. The example is particularly inefficient because it is recursive and checks for sorted input on each invocation, but this is a moot point if the tests are updated.

Aha. I'd suggest you raise an issue on x-common as this pertains to more than just the Clojure track and it'd be good to solve it universally.

There isn't a canonical test list for this exercise in x-common so for now this fix is only appropriate here. I'll put together a PR as long as you're in agreement that it should be fixed.

Definitely, but we should bring it up on x-common too.

Created an issue in x-common: https://github.com/exercism/x-common/issues/234


How to remove inactive devices?

This is more of a question.
I suspect there are many inactive users (who uninstalled my app, but account at our server is alive).
Is there a way to exclude those users before sending push notifications?
-- edit --
I found a section regarding APNS for this.(python manage.py prune_devices)
How about android devices? GCM seems to send notRegistered error to notify the server, can we utilize this in any way?

Looks like there's a way if you contact the feedback server:
http://stackoverflow.com/questions/2362785/howto-remove-device-tokens-received-by-apple-apns-feedback
Then it's a matter of removing the Devices matching that id.

Thanks jleclanche, I updated my question.

It's probably possible to add a GCM backend to prune_devices yes. Someone would have to do it though; I can't realistically work on this without sponsorship nowadays.

ok Thank for the response!


Filter out CRLFs in hyperlinker backend

This prevents spurious lines from appearing in the final output.
This appears to fix #812.

Looks good to me. Thanks Alec!


Update autobuyers values on enter (fixes #1278)

Note that this pull request currently solves the main issue of using the enter key to confirm the current selection, however, doesn't include the escape button to "undo" the unsaved text. I can implement this if it would be helpful, but I feel like it may not be intuitive so it would need to be documented somewhere if added.

I don't think the escape functionality is necessary because it's unintuitive as you point out, but if you change your mind and feel like adding it, the How to Play entry for autobuyers would be an appropriate place for the documenting it.
One comment I have is that while pressing enter does indeed update the value, the player doesn't necessarily see that until the autobuyer next triggers if it's currently off. Perhaps, in line with how it's often done on input forms elsewhere, the autobuyer box should defocus after pressing enter as well?

This should address the comment you made: let me know if there's anything else I should do :).

Looks solid now, thanks for the code contribution! ❤


<EMAIL_ADDRESS>cannot be imported correctly.

Environment

Operating System: Darwin
Node Version:     v18.1.0
Nuxt Version:     3.6.3
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://github.com/Sara2009/bug-report-nuxt3
run yarn

Describe the bug
nuxt dev use jiti to import module with interopDefault: true.
In winson:
exports.transports = require('./winston/transports');

Object.defineProperty(exports, 'default', {
  get() {
    return {
      exceptionHandlers: defaultLogger.exceptionHandlers,
      rejectionHandlers: defaultLogger.rejectionHandlers,
      transports: defaultLogger.transports
    };
  }
});

import winston from 'winston';

I want to use the exports.transports. But it is changed to exports.default.transports.
Additional context
No response
Logs
No response

This looks like an upstream issue with https://github.com/unjs/jiti.
cc: @pi0

Do you mind to open an issue in jiti as well with repro? 🙏🏼

Do you mind to open an issue in jiti as well with repro? 🙏🏼

https://github.com/unjs/jiti/issues/177

Thank you! ❤
Let's track there.


Archiving Hull City of Culture : linking Hyrax and Archivematica

This talk will present a project at the University of Hull, working with CoSector and Cottage Labs, to create a permanent digital archive of the Hull City of Culture. Hull was awarded UK City of Culture for 2017 and, throughout the year, generated a wealth of digital material documenting the events and activities celebrating the city, as well as archives from the organization and evaluation of the event. The University of Hull, already an active user of Samvera technologies, wanted to build on the work done for the Jisc ‘Filling the Digital Preservation Gap’ by using Archivematica for the digital archives preservation pipeline and Hyrax as a showcase for the City of Culture. We will also talk about how the project was originally conceived, and how that has changed through active and engaged project meetings to reflect ongoing service needs for the management of digital archives, of which the City of Culture archive forms a part. Integration with CALM (archives management solution ) and the existing Hull History Centre Blacklight catalogue (developed by DCE) is being explored to create a fully integrated digital archiving solution.
Julie Allinson<EMAIL_ADDRESS>Chris Awre<EMAIL_ADDRESS>

Julie and Chris confirmed and OK with recording 8/8

Both registered 8/14 - system info


vverbose output duplicates some lines, sometimes

it seems that the vverbose output mode duplicates some lines, sometimes. see this screenshot when running against PMA 01-01:

the result document has multiple entries:

so its not that vverbose is wrong, the result document has duplicates.

this comes from the rule:

and the fact that we trim the DLL name from API features:

so we end up with logic that looks like:
- or:
  - api: recv
  - api: recv

which is correctly matched and rendered.
to fix, we should deduplicate these features that the rule wants to match.

the trimming was introduced here: https://github.com/mandiant/capa/commit/c9df78252a19891cc9a12cf85bf20ed0153e2bc4
#1824 and #1815

Yeah, I noticed this as well while working on explorer:
Example: the first 2 socket api statements in "create TCP socket": https://mandiant.github.io/capa/explorer/#/?rdoc=https://raw.githubusercontent.com/mandiant/capa-testfiles/master/rd/0000a65749f5902c4d82ffa701198038f0b4870b00a27cfca109f8f933476d82.json.gz


logging: Processing by default in the idle thread

Removed internal logger thread and added optional log processing
to the idle thread (enabled by default). Kept the possibility to
use custom thread for log processing and possibility to wake up
such thread on threshold.
Signed-off-by: Krzysztof Chruscinski<EMAIL_ADDRESS>

fyi: @jhedberg @carlescufi @jukkar @pizi-nordic

Codecov Report

Merging #9004 into master will decrease coverage by <.01%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master    #9004      +/-   ##
==========================================
- Coverage   52.25%   52.25%   -0.01%
==========================================
  Files         196      196
  Lines       24802    24805       +3
  Branches     5155     5156       +1
==========================================
  Hits        12961    12961
- Misses       9762     9765       +3
  Partials     2079     2079

Impacted Files
Coverage Δ

subsys/logging/log_core.c
69.07% <ø> (ø)
:arrow_up:

kernel/idle.c
64% <40%> (-8.73%)
:arrow_down:

Continue to review full report at Codecov.

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

I have grave concerns about using the idle thread like this and would like to know why this change was made.

@jhe since there are concerns about moving log processing to idle thread ( see @nashif @andrewboie comments) I would reduce this change just to make internal log processing thread a default.

@nashif @andrewboie I suspect this PR is the result of the following short exchange on IRC yesterday:
<jhe> carlesc, nordic-krch[m]: another thing I'm confused about: when the logger design
was originally presented, I got the impression that the system idle thread would be used
for the log processing. Now however it seems that a separate thread is being created.
Why is that?
<nordic-krch[m]> jhe: it may be my lack of knowledge about zephyr. we can use idle
thread i guess.

@nordic-krch I have no problem with this being done in a separate thread, as long as there's a good reason for it (as there clearly seems to be based on the comments from @nashif and @andrewboie). That said, I suppose the default priority for that thread should be the lowest possible, and I don't think that's the case currently?

Do you think that this should that be changed to -1 (K_IDLE_PRIO)?

I have no idea. I'll let @andrewboie or @nashif weigh in on whether that or K_LOWEST_APPLICATION_THREAD_PRIO makes sense.

I think the confusion here is that when we say run something when idle, we mean run a thread when there is nothing else left to do, i.e. before we go to idle (lowest priority), it does not mean we would run this inside the idle thread, which conflicts with the purpose of the idle thread (idling and and doing no actual work). So running the thread with  K_LOWEST_APPLICATION_THREAD_PRIO might make sense here.

I'm closing this one. Will come back with PR which changes in default configuration (internal thread enabled by default)


RecursiveTreeView unable to select parent nodes when depth greater than 2

Current Behavior
On first load, only able to select the leaf nodes and their direct parents of a RecursiveTreeView (haven't tried it with regular TreeView) with selection, multiple and relational enabled. Clicking any other parent node has no effect.
Clicking a second time fixes the issue and all nodes can then be selected.
Expected Behavior
Are able to select any node in the TreeView without having to click a second time
Steps To Reproduce

Add a RecursiveTreeView component to a page with selection, multiple and relational enabled.
Bind to a source of nodes that has nested children with a depth greater than 2
On page load click the first / top level node

Link to Reproduction / Stackblitz
https://stackblitz.com/edit/skeletonlabs-repl-j4d2s8?file=src%2Froutes%2F%2Bpage.svelte
More Information
No response

That's not going to make @Mahmoud-zino very happy but thank you for reporting the issue and thank you very much for providing a stackblitz reproduction, that makes triage and testing so much easier!

That's not going to make @Mahmoud-zino very happy but thank you for reporting the issue and thank you very much for providing a stackblitz reproduction, that makes triage and testing so much easier!

Sorry 😬, really amazing work @Mahmoud-zino. I really love the component, it's a central feature of the app I'm building!

That's not going to make @Mahmoud-zino very happy but thank you for reporting the issue and thank you very much for providing a stackblitz reproduction, that makes triage and testing so much easier!

Sorry 😬, really amazing work @Mahmoud-zino. I really love the component, it's a central feature of the app I'm building!

Thank you very much for reporting the issue, I must have missed it during testing, I will take a look at it 👍

@Mahmoud-zino same deal here, assigned to you.