Website broken after upgrading to latest

Hello,
I switched from legacy version to the latest ones and I am having troubles.
I followed the migration. I removed my _redirects and instead used explicit config in netlify.toml . I also changed the publish to .next.
But now it looks like https://deploy-preview-14--purelambda.netlify.app/ instead of https://purelambda.com . All the CSS and JS seems gone.
What did I do wrong and how to fix it ?
PS: It works fine locally with netlify dev and netlify build.

My build settings

package.json
{
  "name": "learn-starter",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start"
  },
  "devDependencies": {
    "@lottiefiles/react-lottie-player": "^3.4.2",
    "@netlify/plugin-nextjs": "^4.12.2",
    "@netlify/plugin-sitemap": "^0.8.1",
    "ajv": "^8.11.0",
    "axios": "^0.21.1",
    "browserslist": "^4.21.2",
    "classnames": "^2.2.6",
    "feed": "^4.2.2",
    "isbot": "^3.3.4",
    "jquery": "^3.6.0",
    "jsdom": "^18.0.1",
    "lodash": "^4.17.21",
    "netlify-plugin-cache-nextjs": "^1.6.1",
    "netlify-plugin-inline-source": "^1.0.4",
    "netlify-plugin-minify-html": "^0.3.1",
    "next": "^10.0.0",
    "next-pwa": "^5.2.23",
    "postcss": "^8.3.0",
    "postcss-flexbugs-fixes": "^5.0.2",
    "postcss-preset-env": "^6.7.0",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-google-recaptcha": "^2.1.0",
    "react-intersection-observer": "^8.32.0",
    "react-jss": "^10.6.0",
    "react-onclickoutside": "^6.11.2",
    "react-svg": "14.0.0",
    "sass": "^1.34.1",
    "styled-jsx": "^4.0.1",
    "webpack": "^5.9.0"
  }
}

next.config.js
const withPWA = require('next-pwa')

module.exports = withPWA({
    pwa: {
        publicExcludes: [],
        cacheOnFrontEndNav: true,
        skipWaiting: false,
        register: false,
    },
    optimization: {
        minimize: true,
    }
})

netlify.toml
[build]
    command = "npm run build"
    publish = ".next"
    functions = "functions"

[[plugins]]
package = "@netlify/plugin-sitemap"
# https://github.com/netlify-labs/netlify-plugin-sitemap
    [plugins.inputs]
    prettyURLs = true
    trailingSlash = false
    exclude = [
        '**/404*',
        '**/legalNotice*',
        '**/nda*',
        '**/privacyPolicy*',
    ]

[[plugins]]
# https://github.com/jonahsnider/netlify-cache-nextjs#readme
package = "netlify-plugin-cache-nextjs"

[[plugins]]
# https://github.com/philhawksworth/netlify-plugin-minify-html#readme
package = "netlify-plugin-minify-html"

    # Specify which deploy contexts we'll minify HTML in.
    # Supports any Deploy Contexts available in Netlify.
    # https://docs.netlify.com/site-deploys/overview/#deploy-contexts
    [plugins.inputs]
    contexts = [
        'production',
        'branch-deploy',
        'deploy-preview'
    ]

    # Optionally, override the default options for the minification
    # https://github.com/kangax/html-minifier#options-quick-reference
    [plugins.inputs.minifierOptions]
    removeComments = true
    collapseInlineTagWhitespace = true
    collapseWhitespace = true
    minifyCSS = true
    minifyJS = true
    sortAttributes = true
    sortClassName = true

# Redirects

[[redirects]]
from = "/root"
to = "/"
status = 301
force = false

[[redirects]]
from = "/home"
to = "/"
status = 301
force = false

[[redirects]]
from = "/blog"
query = {a = ":a"}
to = "/blog/:a"
status = 301
force = false

[[redirects]]
from = "/blog"
to = "/publicPresence"
status = 301
force = false

jsconfig.json
{
    "compilerOptions": {
        "baseUrl": "."
    }
}

project structure

Thank you very much

Hey.
I'll update here when it is done

ok it is working ! https://deploy-preview-14--purelambda.netlify.app/
but now my asset are not optimized ?

They are optimized by Next.js when the site is built, so you don't need the extra optimization

ok, sounds good.
Since I have all my project structure and config up there. Can I ask an other question ?
Locally it does work but not when deployed which is very frustrating.
I want the URL /blog/?a=data-visualizations to redirect with a 301 to /blog/data-visualizations .
I use
[[redirects]]
from = "/blog"
query = {a = ":a"}
to = "/blog/:a"
status = 301
force = false

for it but i end up with a URL : /blog/data-visualizations?a=data-visualizations.
So I added :
[[redirects]]
from = "/blog/:id"
query = {a = ":a"}
to = "/.netlify/functions/redirects/?a=:id"
status = 301
force = false

before the previous rule in my netlify.toml
and here is the function:
exports.handler = async (event, context) => {
    return {
        statusCode: 301,
        headers: {
            Location: '/blog/' + event.queryStringParameters.a,
            'Cache-Control': 'no-cache',
        }
    }
}

it does work locally, it drops the get query but not after deployment.
Any reason why ?

Hi @leobenkel! I don't think you need the explicit handler for redirects. This should be enough for what you're looking to accomplish. You can put this in your [[redirects]] section of your netlify.toml
/blog a=:a  /blog/:a  301

For more info on this, see https://docs.netlify.com/routing/redirects/redirect-options/#query-parameters

Hi @leobenkel! I don't think you need the explicit handler for redirects. This should be enough for what you're looking to accomplish. You can put this in your [[redirects]] section of your netlify.toml
/blog a=:a  /blog/:a  301

For more info on this, see https://docs.netlify.com/routing/redirects/redirect-options/#query-parameters

This does not work. The resulted URL is /blog/:a?a=:a :(
See other people having the same challenge: https://answers.netlify.com/t/redirect-doesnt-remove-query-params/31548

@leobenkel, you're right about it adding the query string still. My colleague @Hrishikesh-K made me aware that it didn't do this originally and then there was a big demand to have it put back. You can read about it more here, https://answers.netlify.com/t/23436.
Having said. that, you could probably accomplish this with an Edge function, e.g.
export default (request) => {
  const { searchParams, href, pathname } = new URL(request.url)

  if (!searchParams.has('a')) {
    return
  }

  const a = searchParams.get('a');

  const redirectUrl = new URL(href.replace(pathname, `/blog/${a}`).replace(/\?a=.*/, '')).toString()
  console.log(redirectUrl)

  return Response.redirect(redirectUrl, 302);
}

Here's an example repo https://github.com/nickytonline/nextjs-plugin-1490

@leobenkel, you're right about it adding the query string still. My colleague @Hrishikesh-K made me aware that it didn't do this originally and then there was a big demand to have it put back. You can read about it more here, https://answers.netlify.com/t/23436.
Having said. that, you could probably accomplish this with an Edge function, e.g.
export default (request) => {
  const { searchParams, href, pathname } = new URL(request.url)

  if (!searchParams.has('a')) {
    return
  }

  const a = searchParams.get('a');

  const redirectUrl = new URL(href.replace(pathname, `/blog/${a}`).replace(/\?.*/, '')).toString()
  console.log(redirectUrl)

  return Response.redirect(redirectUrl, 302);
}

Here's an example repo, https://github.com/nickytonline/nextjs-plugin-1490 and you can test it out at https://edge-function-redirect.netlify.app/

thank you for your help, looking at the documentation it seems that edge functions are still in beta (https://docs.netlify.com/netlify-labs/experimental-features/edge-functions/). Would it be possible to do the same thing using the classic functions ?
The one i had was :
exports.handler = async (event, context) => {
    return {
        statusCode: 301,
        headers: {
            Location: '/blog/' + event.queryStringParameters.a,
            'Cache-Control': 'no-cache',
        }
    }
}

with
[[redirects]]
from = "/blog/:id"
query = {a = ":a"}
to = "/.netlify/functions/redirects/?a=:id"
status = 301
force = false

[[redirects]]
from = "/blog"
query = {a = ":a"}
to = "/blog/:a"
status = 301
force = false

[[redirects]]
from = "/blog"
to = "/publicPresence"
status = 301
force = false

Thank you

Thank you @Hrishikesh-K , I asked on the support page: https://answers.netlify.com/t/how-to-drop-the-get-arguments-after-redirects/72646


[UBlogList] documentation config is not correct (UI Pro)

Environment

Operating System: Darwin
Node Version:     v20.9.0
Nuxt Version:     3.11.1
CLI Version:      3.11.1
Nitro Version:    2.9.5
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      app, build, colorMode, devtools, eslint, extends, image, mapbox, modules, plugins, srcDir, svgo, tailwindcss, ui
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:

Version
v1.1.0
Reproduction
Context provided should be enough
Description
https://ui.nuxt.com/pro/components/blog-list
The config in the documentation suggests that you can change the vertical and horizontal styling.
But that did not seem to work, and I ended up noticing that you can only change styling through wrapper.
Like so:
blog: {       list: {         wrapper: 'mt-[var(--header-height)] max-w-7xl p-4 sm:p-6 lg:p-8',       },     },
I came to this conclusion because the type of the ui prop on the BlogList component is as follows:
(property) ui?: Partial<{     wrapper: string; }> | undefined
So either I do not understand the documentation, or it is not correct. I'd like to know either way, thanks.
Additional context
No response
Logs
No response

The config was indeed incorrect, you can only change the wrapper through the ui prop. But you do have an orientation prop to switch between horizontal and vertical.


WIP: Add Ctrl+Hover behavior to ShowHoverAction

fixes #46257
Needs to be able to remove decorations after hover is dismissed. Needs to properly handle multiple editors.

Anything new on this PR?

closing this PR as it was too old to merge master. fix is in above linked commit 🎉


chore: don't render reproduce as shell in issue template

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
the last "how to reproduce" section in bug-report issue template will be rendered as bash. But it usually contains some extra descriptions along with commands. Thus it would be better to keep it as plain text and let others to write markdown.
E.g.: #1396

Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

@waynexia lgtm.


[saltstack] update LSSG cheat sheet

At least the LSSG cheat sheet is updated past what is on the Desktop.
Linux Shell Survival Guide is now v2.3.  I can provide link privately until it's updated on website.

@philhagen I think this was updated recently as I had to update the sha256 on the install script? can you confirm?

I'm not sure where to look for the hash - can you point me in the right direction?

https://github.com/teamdfir/sift-saltstack/blob/master/sift/config/user/pdfs.sls#L123

thank you!  yep, that's the new one.  all good.


WIP: [BEAM-8539] Make job state transitions well-defined and consistent

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Java PreCommit

R: @lukecwik
R: @mxm
R: @robertwb
This is a followup to https://github.com/apache/beam/pull/9969 that corrects python-based runners to behave the same as Java-based runners wrt STOPPED: it is the initial state and not a terminal state.
Tests pass, but I'm not sure if this could cause problems with Dataflow.

Should STOPPED be PAUSED?

Based on the comments describing STOPPED, I'd say yes.  But @lukecwik has informed me in the other PR that there are no runners that actually support being paused (RUNNING -> STOPPED -> RUNNING transition) , so STOPPED is not currently used this way.

Run Python PreCommit

Run Java PreCommit

Review notes have been addressed.


#38 add arithmetic for Blocks a la CartesianIndex

This adds Block(1) < Block(2), Block(1) + Block(2), etc. by copying over the code for CartesianIndex.
I couldn't find unit tests for CartesianIndex, so perhaps the tests here should be backported to Base.

Codecov Report

Merging #42 into master will increase coverage by 0.48%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
+ Coverage   89.58%   90.07%   +0.48%
==========================================
  Files           9        9
  Lines         365      383      +18
==========================================
+ Hits          327      345      +18
  Misses         38       38

Impacted Files
Coverage Δ

src/abstractblockarray.jl
91.93% <100%> (+3.29%)
:arrow_up:

src/convert.jl
87.5% <100%> (ø)
: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 5605e4d...10a8831. Read the comment docs.

This is hanging in Julia 0.7 because of replstrmime:
julia> replstrmime(x) = stringmime("text/plain", x)
replstrmime (generic function with 1 method)

julia> replstrmime(BlockArray(collect(reshape(1:16, 4, 4)), [1,3], [2,2]))
ERROR: UndefVarError: BlockArray not defined

julia> using BlockArrays

julia> replstrmime(BlockArray(collect(reshape(1:16, 4, 4)), [1,3], [2,2]))
^C^C^C^C^C^C^C^CWARNING: Force throwing a SIGINT
Internal error: encountered unexpected error in runtime:
InterruptException()
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
has_free_typevars at /Users/solver/Projects/julia7/src/jltypes.c:157
jl_isa at /Users/solver/Projects/julia7/src/subtype.c:1177
jl_tuple_isa at /Users/solver/Projects/julia7/src/subtype.c:1136
jl_typemap_entry_assoc_exact at /Users/solver/Projects/julia7/src/typemap.c:780
jl_typemap_level_assoc_exact at /Users/solver/Projects/julia7/src/typemap.c:821
jl_typemap_assoc_exact at /Users/solver/Projects/julia7/src/./julia_internal.h:940 [inlined]
jl_lookup_generic_ at /Users/solver/Projects/julia7/src/gf.c:1955
jl_apply_generic at /Users/solver/Projects/julia7/src/gf.c:2007
abstract_call_method at ./inference.jl:1923
jl_call_fptr_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:380 [inlined]
jl_call_method_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:399 [inlined]
jl_apply_generic at /Users/solver/Projects/julia7/src/gf.c:2010
abstract_call_gf_by_type at ./inference.jl:1887
jl_call_fptr_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:380 [inlined]
jl_call_method_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:399 [inlined]
jl_apply_generic at /Users/solver/Projects/julia7/src/gf.c:2010
abstract_eval_call at ./inference.jl:2501
abstract_eval at ./inference.jl:2529
jl_call_fptr_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:380 [inlined]
jl_call_method_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:399 [inlined]
jl_apply_generic at /Users/solver/Projects/julia7/src/gf.c:2010
typeinf_work at ./inference.jl:3381
typeinf at ./inference.jl:3450
typeinf_edge at ./inference.jl:3188
jl_call_fptr_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:380 [inlined]
jl_call_method_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:399 [inlined]
jl_apply_generic at /Users/solver/Projects/julia7/src/gf.c:2010
abstract_call_method at ./inference.jl:2008
jl_call_fptr_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:380 [inlined]
jl_call_method_internal at /Users/solver/Projects/julia7/src/./julia_internal.h:399 [inlined]
jl_apply_generic at /Users/solver/Projects/julia7/src/gf.c:2010
abstract_call_gf_by_type at ./inference.jl:1887
…

https://github.com/JuliaLang/julia/issues/24972


:bug: Fix #599 add lazy support for potential self-referential types (plus unit tests)

https://github.com/Code-Hex/graphql-codegen-typescript-validation-schema/pull/838#pullrequestreview-2421134614

hey @Code-Hex i saw you ran the CI checks for me. thanks!
i noticed that it failed and, taking a wild guess, seemingly for a reason unrelated to the PR?
INPUT_BRANCH value: nickdegroot/fix-recursive-types
From https://github.com/Code-Hex/graphql-codegen-typescript-validation-schema
 * [new branch]      main       -> origin/main
fatal: invalid reference: nickdegroot/fix-recursive-types
Error: Invalid status code: 128
    at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v4/index.js:17:19)
    at ChildProcess.emit (node:events:519:[28](https://github.com/Code-Hex/graphql-codegen-typescript-validation-schema/actions/runs/12218195678/job/34143875355?pr=907#step:7:29))
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:[30](https://github.com/Code-Hex/graphql-codegen-typescript-validation-schema/actions/runs/12218195678/job/34143875355?pr=907#step:7:31)5:5) {
  code: 128
}
Error: Invalid status code: 128
    at ChildProcess.<anonymous> (/home/runner/work/_actions/stefanzweifel/git-auto-commit-action/v4/index.js:17:19)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)

any idea how this happened?


Use core platforms when validating manifests

This change means that manifests only supporting linux-arm64 will not pass the validation. It unifies the core packages across validations, though.

I love the idea for HEADing the URLs on validation. Here is a ticket for that https://github.com/cashapp/hermit/issues/112


backend: routes, models, controllers, db folder

initialize the mentioned empty folders

initialize the mentioned empty folders

Can i work on this issue?

initialize the mentioned empty folders

Can i work on this issue?

yes, but before that you have to setup the node server

initialize the mentioned empty folders

Can i work on this issue?

yes, but before that you have to setup the node server

Yed, i will do that

okay, then go ahead :)

@khushi-purwar any updates?

@khushi-purwar any updates?

yes I completed my work, but unable to push @himanshujaidka

@khushi-purwar any updates?

yes I completed my work, but unable to create PR @himanshujaidka

I am getting this

have you refreshed it?

@khushi-purwar any updates?

yes I completed my work, but unable to create PR @himanshujaidka

I am getting this

have you refreshed it? and you need to add something inside files

Ok. I will add content inside files

I have added the content in the files, but still PR is not Creating.


Error In Slash Handler

                        slash.push(pull)
                               ^
ReferenceError : slash is not defined

on handler/slash.js, line 12

ISSUE FIXED


added deduplication of findings

hey @grendel513 @cneill here is the new PR with merge conflicts removed.
I corrected the issues identified in the other PR as best I could.
Fixed spacing.
Added hasattr attribute to safely check if settings.ENABLE_DEDUPLICATION is available.
removed legacy save, however super save must be called twice for the many to many mappings.
added doc info on deduplication.
Other things I added:
added OSX support for setup.bash
added blank / null for the image field on findings

oh and tested changes on Ubuntu 16.04 and OSX

good work!


[Question] Readonly replicas

Hi there,
We're looking for the way of configuring a few replicas, where just one works for writes and others work for reads.
Eg. cloudnative-pg makes three services by default:
# k get svc -n db-pg-test
NAME      TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
test-r    ClusterIP   <IP_ADDRESS>   <none>        5432/TCP   43h
test-ro   ClusterIP   <IP_ADDRESS>   <none>        5432/TCP   43h
test-rw   ClusterIP   <IP_ADDRESS>     <none>        5432/TCP   43h

# k get ep -n db-pg-test
NAME      ENDPOINTS                                       AGE
test-r    <IP_ADDRESS>:5432,<IP_ADDRESS>:5432,<IP_ADDRESS>:5432   43h
test-ro   <IP_ADDRESS>:5432,<IP_ADDRESS>:5432                  43h
test-rw   <IP_ADDRESS>:5432                                  43h

# k get pod -o wide -n db-pg-test
NAME     READY   STATUS    RESTARTS   AGE   IP           NODE   NOMINATED NODE   READINESS GATES
test-1   1/1     Running   0          43h   <IP_ADDRESS>    pve3   <none>           <none>
test-2   1/1     Running   0          43h   <IP_ADDRESS>    pve1   <none>           <none>
test-3   1/1     Running   0          43h   <IP_ADDRESS>   pve2   <none>           <none>

Is there any option to get the similar setup using mariadb-operator?
Does it makes sense for galera cluster?

Hi @kvaps, In the slack channel someone was asking a similar question I believe.

Hey there @kvaps ! Thanks for bringing this questions up.
I've created an issue for this:

https://github.com/mariadb-operator/mariadb-operator/issues/203

Currrently, only the replication HA mode modes creates an extra service to perform writes to a specific node. We are aiming to consolidate and standarize this solution for Galera as well, as it seems to be a common practise for preventing posible deadlocks.
It will be tackled in the following releases!

Ok, thanks a lot!

To answer your question, here it is how are we planning to standarize Services for HA:

<mariadb-name>: To be used for read requests. It will point to all nodes
primary-<mariadb-name>: To be used for write requests. It will point to a single node.

It will be tackled in the following releases!

The only wish I'd like to add is one more service:

secondary-<mariadb-name>: To be only for read requests. It should point to all nodes, except the primary one.

The only wish I'd like to add is one more service:
secondary-: To be used only for read requests. It should point to all nodes, except the primary one.

See this comment. Let's keep the discussion there. Closing


Feature: NerdAsset assets for seed.js

Assignee Tasks

[ ] added unit tests (or none needed)
[ ] written relevant docs (or none needed)
[ ] referenced any relevant issues (or none exist)

Guidelines
Please add a description of this Pull Request's motivation, scope, outstanding issues or potential alternatives, reasoning behind the current solution, and any other relevant information for posterity.

Your PR Notes Here

Added nerdAsset.js file...


Compiler crashes if structs contain functions

What Git revision are you using?
Compiled from source at 075668b52ea748cb1cd3bc6723b1add752976f0f
$ aiken --version
aiken v1.0.26-alpha+unknown

What operating system are you using, and which version?

[ ] Linux / Ubuntu
[x] Linux / Other
[ ] macOS
[ ] Windows

Describe what the problem is?
type Rec<t> {
     get_t: t,
}

fn use_dict(dict: Rec<fn(Bool) -> Bool>, b: Bool) -> Bool {
   let f = dict.get_t
   f(b)
}

fn not(x: Bool) -> Bool {
   when x is {
     False -> True
     True -> False
   }
}

fn foo() -> Bool {
   let dict = Rec {get_t: not}
   use_dict(dict, False)
}

When foo() is used anywhere in validator code, compiler crashes
   aiken::fatal::error
   Whoops! You found a bug in the Aiken compiler.

   Please report this error at https://github.com/aiken-lang/aiken/issues/new.
   In your bug report please provide the information below and if possible the code
   that produced it.

   Operating System: linux
   Architecture:     x86_64
   Version:          v1.0.26-alpha+unknown

   crates/aiken-lang/src/gen_uplc.rs:4193:77

       called `Result::unwrap()` on an `Err` value: NotAConstant(<a lot of uplc>)

What should be the expected behavior?
The code above is valid, it should compile.

The code above is valid, it should compile.

No it is not. Not in Aiken at least. Records aren't allowed to hold functions unfortunately due to how values are encoded on the VM (and specifically, to how Aiken chooses to encode them).
That is however a but with the type-checker here which should catch that.


Style props not being applied

I am trying to apply basic style properties per the docs to input elements and groups, and it is rendering the default layout each time, and not applying props correctly.
react-native, react and native-base version
NB -> 2.0.11 RN->0.41
Expected behaviour
Input style properties render properly
Actual behaviour
Input style properties do not render properly
Steps to reproduce (code snippet or screenshot)
Try to add an InputGroup or Item with rounded corners or icon right alignment
Screenshot of emulator/device

Is the bug present in both ios and android or in any one of them?
only tested on iOS
Any other additional info which would help us debug the issue quicker.
I tried applying the 'light' theme to the component, this did not change anything. I am copy and pasting examples from docs.

cc @shivrajkumar

@srhise In v2.0.x InputGroup has been replaced by Item.
Refer http://nativebase.io/docs/v2.0.0/components#roundedTextbox

Using item doesn't help me in this situation. The only style I have applied is to set the text color to white:

+1

Fixed in v2.1.3
Have a look


Starter: Active Failover, typo leading to agency failure

In the section "deployment-active-failover-using-the-starter", under the subsection "Multiple Machines", the given command has a typo leading to failure of the agency.
The option --agents.agency.supervision.grace-period should be --agents.agency.supervision-grace-period.

Well spotted and thank you for letting us know! I corrected the command: https://github.com/arangodb/docs/commit/9d33d9c53b9ea833ab494a0002b3369275685ecd
It will take a few days before the change goes live.


allow audio to play even when not initiated with a user's gesture

Under discussion currently, as this will impact all media with autoplay
When a user gesture doesn't initiate a sound, it won't play. You can bypass this with a chromium arg.
fix #176284
fix https://github.com/microsoft/vscode/issues/178642
fyi @rebornix @amunger

@meganrogge Let's make sure this doesn't enable auto playing videos with audio on extension pages. You can use edit one the built-in extension's README.md to have a video tag such as:
<video autoplay>
<source src="http://<IP_ADDRESS>:8080/example.mp4">
</video>

I can help test this too if you're running into issues

The flag will affect all media tags across frames which have an autoplay attribute.

Looking a bit more into the history of the autoplay policy in Chromium, it used to be that desktop allowed autoplay by default until the following feature landed in 2017 https://bugs.chromium.org/p/chromium/issues/detail?id=715049 to avoid annoyances to users from Ads on both mobile and desktop. The design doc also highlights the workarounds a website can do to get autoplay, checkout the Media Engagement section of the linked doc.
Based on the above I feel we can just disable the UnifiedAutoplay feature to get the default behavior of autoplay. @meganrogge can you replace the current change with change to L253 app.commandLine.appendSwitch('disable-features', 'CalculateNativeWinOcclusion,UnifiedAutoplay'); and see if it still addresses the issue.

Thanks for investigating @deepak1556 and yes that fixes it 👍🏼


Remove a get* OpenGL function causing CPU-GPU sync point.

Fix bad performance on OpenGL.
Related with #1125

:+1:


.fail example given in readme does not get called

From the readme:
bot.postMessageToUser('user1', 'hi').fail(function(data) {     //data = { ok: false, error: 'user_not_found' } })
if you change user1 to a user that exists, the message does get sent
if user1 does not exist, the anonymous function provided to fail never gets called, the failure simply happens silently.
not sure if this is a change on Slack's end that has broken this, or if it's an issue with the slackbots library, but something likely needs to be updated either way.

I should clarify that yes, I threw a console.log in that function and it doesn't execute, I didn't just copy/paste it verbatim into my code :-)

Thanks for the issue. I will think how to fix it, but you can use callback instead of promises.
bot.postMessageToUser('user1', 'hi', function(data) {/* ... */});


perf: optimize various hot functions on large compiles

Avoid use of polymorphic comparison on types, use bespoke comparison instead.
Optimize hashing of field/variant names.

Cuts compilation times roughly in half (but largely because we type check all intermediate representations).

Did you use profiling to identify the hot paths? Or just gut feeling?

Profiling. On large examples we spend 25 percent of time in polymorphic comparison.
I'm currently shaving 12 seconds off a 50 second compile.

But it makes very little difference with -no-check-ir (but I'd expect that).

@nomeata optimizing Hash.hash to avoid String.explode shaves off another 10s from the (original 50s) compile, now down to 28s.
Not too shabby.

Pretty good. Make sure to brag a bit in the release notes :-)

WTF? Why am I getting a stack overflow?


Add new TimeCal app

Here is a clock I've been working on, it shows the date and time, with a 3 week calendar.
Sorry if I've missed something, this is my first time contributing to this project.

Nice -  looks good!
All I'd say is right now you're polling every second which will affect your battery life a bit. There's a way of getting called only every minute which I've been using in most new clocks that you may be able to use - there's an example at https://www.espruino.com/Bangle.js+Clock+Font

Just FYI I'm talking battery life of maybe 4 weeks down to 2, so this is not some huge issue


Compiler API transpileModule does not emit diagnostics ever - empty array

Bug Report

🔎 Search Terms
diagnostics empty
🕗 Version & Regression Information

I was unable to test this on prior versions because I was in a rush and assume this is just a user error

⏯ Playground Link
Not usable
💻 Code
alex@weejmbp ts-test % cat test.ts
import * as ts from "typescript";

// function test(a: string, b: number) {
//   return b.startsWith(a);
// }

const result = ts.transpileModule(
  `
function test(a: string, b: number) {
    return b.startsWith(a);
}
`,
  {
    reportDiagnostics: true,
    compilerOptions: {
      strict: true,
      target: ts.ScriptTarget.ES2020,
      noImplicitAny: true,
      noEmitOnError: true,
    },
  }
);

console.log("Result:", result);

alex@weejmbp ts-test % npx tsc test.ts && node test.js
Result: {
  outputText: '"use strict";\nfunction test(a, b) {\n    return b.startsWith(a);\n}\n',
  diagnostics: [],
  sourceMapText: undefined
}

🙁 Actual behavior
The diagnostics is always an empty array. It doesn't matter how broken the source is, whether it's Type level errors or severe syntactic malformedness.
🙂 Expected behavior
Diagnostics provided so I can report the code issues.

Thanks for your help!

Type errors are not reported in transpileModule; that’s the whole point of the API. I can’t reproduce a lack of syntax error reporting though. When I run your test program and modify the input by removing the c from function to be funtion test(..., this is the result:
❯ node dist/a.js
Result: {
  outputText: '"use strict";\n' +
    'funtion;\n' +
    'test(a, string, b, number);\n' +
    '{\n' +
    '    return b.startsWith(a);\n' +
    '}\n',
  diagnostics: [
    {
      file: [SourceFileObject],
      start: 1,
      length: 7,
      messageText: "Unknown keyword or identifier. Did you mean 'function'?",
      category: 1,
      code: 1435,
      reportsUnnecessary: undefined
    },
    {
      file: [SourceFileObject],
      start: 15,
      length: 1,
      messageText: "',' expected.",
      category: 1,
      code: 1005,
      reportsUnnecessary: undefined
    },
    {
      file: [SourceFileObject],
      start: 26,
      length: 1,
      messageText: "',' expected.",
      category: 1,
      code: 1005,
      reportsUnnecessary: undefined
    },
    {
      file: [SourceFileObject],
      start: 36,
      length: 1,
      messageText: "';' expected.",
      category: 1,
      code: 1005,
      reportsUnnecessary: undefined
    }
  ],
  sourceMapText: undefined
}

@andrewbranch, thanks for replying so quickly! I must have done something wrong when testing broken source code - I was laughing at how remarkable the effort was that TypeScript had gone to to turn utter nonsense into valid JS...!
Which API is recommended for compiling and emitting diagnostics (is this the wrong term for type errors?) in one go? Similar to how a human running 'tsc' will get compiled results and type errors.
Thanks

There’s an (old, but mostly alright) example here: https://github.com/microsoft/TypeScript/wiki/Using-the-Compiler-API#a-minimal-compiler

Thank you, Andrew. I'll give this a go. Looks like this probably is just a PEBKAC issue!

@alexweej Long shot here: I'm writing a web application that tries to compile typescript into javascript and I 've got the same problem how to have transpileModule to output diagnostics ? It seems to always give out valid code and no errors no matter horrible the code I put in...? Did the minimal compiler example contain anything specific to be done in a browser ?


incorrect class definition string

Sending method classCreationTemplateForClass:hybridBrowser: to RowanDefinitionService results in this class definition string, however this method does not appear to be implemented in Rowan:
Object rwSubclass: 'RowanDefinitionService'
instVarNames: #( definition)
classVars: #()
classInstVars: #()
poolDictionaries: #()
inDictionary: ''
category: 'Rowan-Services'
options: #()

ah ... I removed the inDictionary: arg from the actual messages and missed changing the template ... poor test coverage ..

No problem. I'll pick the change up tomorrow.
fyi - I'm not going to test your new readme instructions tonight. I'll test it tomorrow.

I'll be in the office tomorrow, so that'll be a good time to try out something new ...


EIP 97

this supersedes #381 after #373 was finished

Does this still need to be merged? Are there any other EIPs that aren't in? cc @vbuterin

I think this is outdated


file not ASCII text

Hi there
When I run copydetect -t <folder> I get the error "file not ASCII text".
I have tried with a folder containing pdf files and a folder containing txt files, with same result.
Any clues on what I'm doing wrong?

For PDF files this is expected, copydetect can only parse plain text files. With txt files it should work fine, though. Can you provide more information about what files you're processing and what the error output looks like?

Thank you for getting back to me. The error was purely mine, and I apologise for the inconvenience. 🙏

I met this exact problem when my files contain some unicode characters, such as Chinese characters. Is there any options that I can use for utf-8 files?

@dongmingli-Ben UTF-8 encoded text works fine on my machine but it looks like the default encoding used by python is operating system specific, which may be causing your issue: https://peps.python.org/pep-0597/#using-the-default-encoding-is-a-common-mistake.
Based on that PEP it seems the file loading code should be explicitly specifying UTF-8. But a command line option for controlling encoding may also be useful. I'll look into this later this week.

I look into the code and it appears that on my machine, utf-8 files cannot be opened and read successfully without the encoding option utf-8 in file.read. Add encoding='utf-8' to detector.py [line 83] fixes the problem for me.

@dongmingli-Ben Thank you for testing that. I just released copydetect==0.4.3, which includes the fix. Let me know if you still have encoding issues with the latest version.


Don't trim $filter_name in sanitizeStreamFilter

When using appendStreamFilter to add a filter to a Writer (or Reader) instance, the name of the filter is sanitised by the sanitizeStreamFilter method in StreamFilter.php. This method casts the name to a string, trims and returns it.
Trimming the string causes issues when implementing a filter where it's last argument has a trailing new-line character, for example I am attempting to write a filter that uses str_replace which will be used to convert Windows-style line endings (\r\n) to Linux-style (\n), but the Filter's onCreate method receives only the first argument due to trim removing the tailing new line.
Example code:
$writer = Writer::createFromPath( tempnam( sys_get_temp_dir(), 'csv' ) ); stream_filter_register( FilterReplace::FILTER_NAME . "*", FilterReplace::class ); $writer->appendStreamFilter( FilterReplace::FILTER_NAME . "\r\n:\n" );
Thanks.

hi @HeyRatFans thanks for submitting your PR but I think that you are dealing with 2 problems:

converting your CSV newlines (this problem is for the Csv::writer class)
creating a good stream filter name

For the first problem you could simply use the setNewline method :) . And as far as I am aware PHP's SplFileObject has no problem handling correctly the newline sequence while reading the CSV files, unless you are using a Mac based computer or a CSV that was generated on a Mac based computer for which you can simply set a specific ini value.

For the second problem PHP stream filter name have some restrictions for instance using "new line characters or "invisible" ones in them is forbidden" so using \r or \n or even \0 (the null byte) will trigger a Fatal error when using them. If you had included some tests with your PR like it is recommend by the contribution guidelines you would have stumble on this issue for sure.

TL;DR: If you still want to use stream filter to achieve your goal you need to think of an workaround to specify you input but for those reasons I can not accept your PR.

Hi,
Isn't the setNewLine method used to specify the line-terminator? This isn't intended to change that, but instead alter the text in the fields, i.e.: 1,"two",3,"new\r\nline" would become 1,"two"3,"new\nline" (note the change in new line the 4th field), which we cannot otherwise change using Writer.
We need to do this to normalise the new-lines in the data we export, which unfortunately we can't alter at source and for speed I am using PDO and passing a statement directly into Writer, which is what attracted me to this library in the first place.
Do you have a source for using invisible characters in a filter name? I had no problem creating a stream filter which does exactly as described above with the modified StreamFilter.php I have submitted and I did not encounter any errors, fatal or otherwise.
Apologies for not contributing a test, I have now added one to test the filter name, but not the actual functionality. Do you need one for this?
Thanks.

Okay so you want to change the line terminators inside the cell okay got it :)
here's a blog post I made about enforcing CSV delimiters using stream filters. Hope you'll find what you want in there.
http://nyamsprod.com/blog/2015/qa-enforcing-enclosure-with-leaguecsv/
IMHO in your case you should create a "simple" filter with a fixed filtername. Since you already know what you want to change and with what you want to change it with. The code will be much simpler

I had seen your blog entry previously, which actually gave me the idea of using a StreamFilter in the first place! :)
I did originally start with a simpler filter that did just line-endings, but I have other use cases where a generic str_replace stream filter would be more useful than multiple classes and not just with this library.

I understand what you are trying to do but the main issue is not really League\Csv. To illustrate, I'll use your stream filter and SplFileObject:
use lib\FilterReplace;

require 'FilterReplace.php';

stream_filter_register(FilterReplace::FILTER_NAME.'*', FilterReplace::class);
$streamPath = 'php://filter/read='.FilterReplace::FILTER_NAME."\r\n:\n"."/resource=".__DIR__."/test.csv";
new SplFileObject($streamPath); //SplFileObject will throw a RuntimeException

I've register your filter
League\Csv will keep a registry of the registered filter (this is what your added test just verify)
League\Csv uses lazy loading, so the SplFileObject is only created when needed (when using foreach) . On foreach call  the object generates the streamPath and feed it to SplFileObject constructor since this is the only way to apply stream filtering to a SplFileObject.
Because you've added \r, \n and other characters that have a numerical value < 32 SplFileObject will throw a RuntimeException because you've submitted an invalid path.

TL;DR: Removing the path trimming will not resolve you issue.

What exception are you're seeing? I was seeing this:
PHP Fatal error:  Uncaught exception 'RuntimeException' with message 'SplFileObject::__construct(): unable to create or locate filter "convert.replace.\r\n:\n"'
Which was entirely my mistake as I hadn't commit the latest version of the FilterReplace class. The version submitted previously wasn't correctly matching "\r\n:\n" which caused the onCreate method to return false and the above Exception to be raised.
I'm not getting any other exceptions with your code snippet now.
Thanks.

I have updated the tests to show that the stream filter does work to replace \r\n with \n with Writer. No exception is throw by writing the file! I have double checked this on both Ubuntu and Windows 7.
However, I have discovered an interesting issue using Reader to read back the written data. If I use PHP's native fopen and fgetcsv I can verify the data is written successfully, but using Reader the data in my "new line" field appears to be stripped of all new lines, including both \r\n and \n and I can't determine where or why this is occurring. This happens regardless of whether FilterReplace is attached to the Reader.
Hopefully you'll know better :)
Thanks.

Could you please:

Open an issue related to this PR
Make a PR from one of your a dedicated branch and not from your master branch.
Remove the fgetcsv test which does not test the package per se.
Once this is done I'll accept your PR but I reserve the right to change/adapt some of your code to make it pass the HHVM.
Open a distinct issue for the one you just found so I can work on it separately.

Except for the tests changes, what I'm asking is written in the CONTRIBUTING to make it easier for any maintainer and future users to quickly find references to bugs in the issue tracker.
As your patch boils down to removing the usage of the trim function on the stream filter name I'm ok with it :+1: .

Closing in favour of #123.


Warnings with terraform 0.13.7

Thanks for writing this module, saved us some time. Currently this module produces warnings when used with terraform 0.13.7 due to using the older syntax. Here's an example output:
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
 <= read (data resources)

Terraform will perform the following actions:

  # module.resource-0.data.template_file.lifecycle_policy_rules[0] will be read during apply
  # (config refers to values not yet known)
 <= data "template_file" "lifecycle_policy_rules"  {
      + id       = "01fa380f384decf846c1579d2cf56a79d67f6046e3f3227bb3766af2218d4578"
      + rendered = jsonencode(
            {
              + action       = {
                  + type = "expire"
                }
              + description  = "Rotate images after amount of: 30 is reached for prefix v"
              + rulePriority = "1"
              + selection    = {
                  + countNumber   = 30
                  + countType     = "imageCountMoreThan"
                  + tagPrefixList = [
                      + "v",
                    ]
                  + tagStatus     = "tagged"
                }
            }
        )
      + template = jsonencode(
            {
              + action       = {
                  + type = "expire"
                }
              + description  = "Rotate images after amount of: 30 is reached for prefix v"
              + rulePriority = "1"
              + selection    = {
                  + countNumber   = 30
                  + countType     = "imageCountMoreThan"
                  + tagPrefixList = [
                      + "v",
                    ]
                  + tagStatus     = "tagged"
                }
            }
        )
    }

....

  # module.resource-1.data.template_file.lifecycle_policy_rules[1] will be read during apply
  # (config refers to values not yet known)
 <= data "template_file" "lifecycle_policy_rules"  {
      + id       = "c312856242402d680474a18c336216d1c8d543de56689eb6e381a67a9760811c"
      + rendered = jsonencode(
            {
              + action       = {
                  + type = "expire"
                }
              + description  = "Rotate images after amount of: 90 days since image pushed, is reached for untagged images"
              + rulePriority = "2"
              + selection    = {
                  + countNumber = 90
                  + countType   = "sinceImagePushed"
                  + countUnit   = "days"
                  + tagStatus   = "untagged"
                }
            }
        )
      + template = jsonencode(
            {
              + action       = {
                  + type = "expire"
                }
              + description  = "Rotate images after amount of: 90 days since image pushed, is reached for untagged images"
              + rulePriority = "2"
              + selection    = {
                  + countNumber = 90
                  + countType   = "sinceImagePushed"
                  + countUnit   = "days"
                  + tagStatus   = "untagged"
                }
            }
        )
    }

Plan: 0 to add, 0 to change, 0 to destroy.

Warning: Interpolation-only expressions are deprecated

  on .terraform/modules/ecr-retention-max-days-untagged/main.tf line 3, in locals:
   3:   validate_tag_status = "${lookup(var.allowed_tag_status,var.tag_status)}"

Terraform 0.11 and earlier required all non-constant expressions to be
provided via interpolation syntax, but this pattern is now deprecated. To
silence this warning, remove the "${ sequence from the start and the }"
sequence from the end of this expression, leaving just the inner expression.

Template interpolation syntax is still used to construct strings from
expressions when the template includes multiple interpolation sequences or a
mixture of literal strings and interpolations. This deprecation applies only
to templates that consist entirely of a single interpolation sequence.

(and 49 more similar warnings elsewhere)

Do you want to perform these actions in workspace "shared"?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value:

Would you accept a PR to fix these warnings?

For anyone using this and its paired module (https://github.com/doingcloudright/terraform-aws-ecr-cross-account) make sure you convert every occurrence of pre TF v13 syntax or you will get errors.


fix: shorten email otp length

What kind of change does this PR introduce?

Addresses concerns in #379
Shorten email otp length to range between 6-10 digits
Email link token param is now a hash(email + otp)
Values stored in xxx_token in the db is now hash(email + otp) instead of just the otp
Email link verification works by matching the token param with the token field in the db (since both are hashed, we can just compare the hashes)
Email otp works by taking hash(email + otp) and comparing the value with the token field in the db (for sms otps, the hash will be hash(phone + otp))
support old otp format (to be deprecated within a week - current otps only last for 24 hrs so users will have to regenerate new ones regardless)
Potentially a breaking change if user has already built a UI to account for the old token format (xxxxx-xxxxx-xxxxx-xxxxx)

To-Dos

[x] Fix tests
[x] Generate link endpoint should also return the raw unhashed otp

Actually for even more security you could use Sum224 which is also resistant to padding attacks.

One other remark, and this is really a nit, is to use encoding/hex as it expresses intent more clearly than fmt.Sprintf("%x", ...). I'd be OK with Base64 too.

decided not to use the encoding/hex package and stuck to fmt.Sprintf("%x", ...) instead because EncodeToString takes in a byte slice while sha256.Sum224 returns a [28]byte array

One other remark, and this is really a nit, is to use encoding/hex as it expresses intent more clearly than fmt.Sprintf("%x", ...). I'd be OK with Base64 too.

decided not to use the encoding/hex package and stuck to fmt.Sprintf("%x", ...) instead because EncodeToString takes in a byte slice while sha256.Sum224 returns a [28]byte array

Usually you can just do something like:
hex.EncodeToString(array[:])

To convert the array to a slice...
No need to block the PR on this though, if you want you can change it in another PR -- do it, if not, c'est la vie. 😸

Actually. This seems to not be working very well: https://go.dev/play/p/yKmLeyU2vmi

LOL. No this uses Println not Printf. This is good to go.


Raise error when unknown key specified in template

Problem Statement
While working on the template, I noticed if I specify a non-existent key in the template, the reconciliation succeeds and inserts value <no value>. This behavior seems quite error-prone since users could accidentally insert base64 encoded <no value> to their secret value.
Related Issue
N/A
Proposed Changes
Use the missingkey=error option for the go template to raise the error.
Checklist

[x] I have read the contribution guidelines
[x] All commits are signed with git commit --signoff
[x] My changes have reasonable test coverage
[x] All tests pass with make test
[x] I ensured my PR is ready for review with make reviewable

IIRC this was set on purpose - @moolen  do you happen to know what was the reason we did that on purpose?

I don't know, it doesn't ring a bell. From the looks of it i think this is fine.

In that case, I think we need to update documentation as well in https://external-secrets.io/latest/guides/templating/:
base64encode was renamed to b64enc.
base64decode was renamed to b64dec. Any errors that occur during decoding are silenced.
fromJSON was renamed to fromJson. Any errors that occur during unmarshalling are silenced.
toJSON was renamed to toJson. Any errors that occur during marshalling are silenced.

As these are no longer silenced if I understand correctly 😄

Thanks for the feedback! IIUC, the doc states errors returned from those three functions are ignored, I personally believe we don't have to change that part since we keep ignoring those errors even after the change, but WDYT? 🤔

wouldn't a (fromJson .).key start failing now?

wouldn't a (fromJson .).key start failing now?

Yes, that is correct! At the same time, the current statement "fromJSON was renamed to fromJson. Any errors that occur during unmarshalling are silenced." also stays true even after this change. Why don't we simply update the doc and tell users that any missing keys raise an error?

wouldn't a (fromJson .).key start failing now?

Yes, that is correct! At the same time, the current statement "fromJSON was renamed to fromJson. Any errors that occur during unmarshalling are silenced." also stays true even after this change. Why don't we simply update the doc and tell users that any missing keys raise an error?

works for me. :) sorry for nitting

@gusfcarvalho Thanks, updated the docs!

Hey, just wanted to ask about this. With this change it is now not possible to use .missing_key | default "some-default" anymore, since it throws an error when accessing the missing key. Is there any way to make | default work?

@qlonik Hmm, yes that is correct... There must be some ways to workaround the problem so let me check 🙇

@qlonik I've figured out how we can set the default values without raising errors. If this is a common use case, it might be favorable to add syntax sugar for it...
{{ if index . "missing_key" }}{{ .missing_key }}{{ else }}some-default{{ end }}

Hey @shuheiktgw, sorry, I haven't responded sooner. I don't know if this is necessary - I only had a few spots where this was an issue, and I just inlined default values where it was necessary.
However, I also found dig function, which I think can be used here and also can be used in the pipe:
{{ dig "missing_key" "some-default" . }}
{{ . | dig "missing_key" "some-default" }}
{{ . | ... | dig "missing_key" "some-default" | ... }}

Hi.
I think this broke my push secret. I create a secret from a k8s secret on top of data I set using the templating and I get the error of:
external-secrets {"level":"error","ts":1720450212.1143377,"msg":"Reconciler error","controller":"pushsecret","controllerGroup":"[external-secrets.io](http://external-secrets.io/)","controllerKind":"PushSecret","PushSecret":{"name":"rabbitmq","namespace":"rabbitmq"},"namespace":"rabbitmq","name":"rabbitmq","reconcileID":"<REDACTED>","error":"could not execute template: could not execute template: unable to execute template at key endpoint: unable to execute template at key endpoint: template: endpoint:1:3: executing \"endpoint\" at <.endpoint>: map has no entry for key \"endpoint\"","stacktrace":"[sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler](http://sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler)\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.3/pkg/internal/controller/controller.go:324\[nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem](http://nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem)\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.3/pkg/internal/controller/controller.go:261\[nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2](http://nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2)\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.18.3/pkg/internal/controller/controller.go:222"}

This is my spec
Spec:
  Data:
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:         endpoint
        Remote Key:       rabbitmq
      Secret Key:         host
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:         endpoint-scheme
        Remote Key:       rabbitmq
      Secret Key:         endpoint-scheme
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:         management-port
        Remote Key:       rabbitmq
      Secret Key:         management-port
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:         management-scheme
        Remote Key:       rabbitmq
      Secret Key:         management-scheme
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:         port
        Remote Key:       rabbitmq
      Secret Key:         port
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:         password
        Remote Key:       rabbitmq
      Secret Key:         password
    Conversion Strategy:  None
    Match:
      Remote Ref:
        Property:    username
        Remote Key:  rabbitmq
      Secret Key:    username
  Deletion Policy:   None
  Refresh Interval:  1h
  Secret Store Refs:
    Kind:  ClusterSecretStore
    Name:  cluster-secret-store
  Selector:
    Secret:
      Name:  rabbitmq-default-user
  Template:
    Data:
      Endpoint:             {{ .endpoint }}
      Endpoint - Scheme:    amqp
      Management - Port:    15672
      Management - Scheme:  http
      Password:             {{ .password }}
      Port:                 {{ .port }}
      Username:             {{ .username }}
    Engine Version:         v2
    Merge Policy:           Replace
  Update Policy:            Replace

The secret should be
{
  "endpoint": "rabbitmq.rabbitmq.svc",
  "endpoint-scheme": "amqp",
  "management-port": "15672",
  "management-scheme": "http",
  "port": "5672",
  "password": "<REDACTED>",
  "username": "<REDACTED>"
}

What's weird is if I set
Endpoint:             {{ .endpoint }}

to
Endpoint:             {{ .host }}

It now works.... ?


latest enum-support - certain embers are broken? ambient:bindings/component

See my project @ https://github.com/droqen/23-08Blue
Ever since switching to a 'workspace' and updating to the newest enum-support (I've remained on the bleeding edge pretty much every day), I can't run certain embers. I haven't been able to figure out why, but it can be (hopefully) easily reproduced.
> ambient run blue-moon successfully runs everything in blue-moon, but its dependencies, ww_gen and a_nice_overhead_camera both fail with the following error(s):
[2023-08-08T22:24:57Z ERROR ambient::client::wasm] [client_nice_overhead_camera] error: Runtime error: import `ambient:bindings/component` has the wrong type
    Root cause: expected record field named includes, found include

> ambient run a_nice_overhead_camera and > ambient run ww_gen individually also causes this error.

Try https://github.com/droqen/23-08Blue/pull/3 and see if that fixes it for you. I can get into the game with blue-moon, ww_gen and a_nice_overhead_camera, but I don't see anything with them, so you'll have to judge their correctness for yourself 😅

Is this sorted now?


fix text rendering when preformat identifier is used inline

only treat preformat identifier as such when it is positioned at the start of the line

Interesting, thanks.


[RFC] Loss Functions - Survival Model and Binomial Loss with count upper bound

Motivation
XGBoost supports a different kind of loss functions ranging from least square to cox-proportional hazard model. We have rich support for linear regression, classification, count and survival loss models. But, adding more important survival and classification loss functions would improve the features and flexibility of the package.
Goals

Support survival model - Accelerated Failure Time for left, right and interval censored data.

Support count data with an upper bound, Binomial loss.

Non-Goals
This proposal is for XGBoost only. The interface proposed here is specific to R but can be generalized to other language bindings later.
Assumptions
Adding new attributes in the data matrix is allowed. This might change the properties of cox-proportional hazard model given that we might support for interval censored regression.
Risks
New hyperparameters sigma for tuning which might slow the computation for cross-validation.
Design
Existing Code

Survival Model - Cox-Proportional model is supported now where the label’s values are assigned accordingly where it is positive if the event happens and negative if the event doesn’t happen. This is for right censored data only.
Logistic regression - Logistic regression, Logistic regression for binary classification are supported having labels with {0,1} values.

Phase 1: Accelerated Failure Time(AFT)
Here we aim to support left, right and interval censored datasets.

New loss functions for Accelerated Failure time with normal and logistic distributions.

Interval regression requires two labels to be input, where left and right censored data can be represented in the form of interval-censored where the lower limit is -inf for left and higher limit is inf for right censored datasets. We add a new attribute to the DMatrix object to store the extra label.

For point event (un-censored label), lower limit equals to a higher limit.

New parameter is created to pass the distribution type, belonging to Normal or Logistic distribution.

Gradient, hessian and metric performance will be added for AFT loss functions.

Loss functions require extra parameter - sigma. This is going to be treated as one of the hyperparameters.

Phase 2: Binomial Loss for count data with an upper bound
Here we aim to add new loss function for binomial Loss.

Input is count as a label which is different from binary classification.

We have an upper bound on the count of response for each row differently. New attributed is added to the DMatrix object to store this upper bound count.

Gradient, hessian and metric performance will be added for this loss function.

cc @hcho3 @tdhock
Note. This work is being carried out under the Google Summer of Code 2019. See discussion at #4242.

For those unfamiliar with survival analysis: this survey paper provides an excellent overview of survival analysis.

you wrote that AFT model requires "extra sigma for normal distribution as a parameter to be estimated and beta for logistic distribution" but it would be better if you use the standard parameterization, which has sigma for both distributions, and allows easy extension to other distributions as well. this is described in section 6.9 of the survival package manual http://members.cbio.mines-paristech.fr/~thocking/survival.pdf

also see https://github.com/avinashbarnwal/xgboost/issues/1 which is a summary of calls with @avinashbarnwal our GSOC'19 student

I will change it to standard parameterization-sigma for both distributions. I was referring to your document https://github.com/tdhock/aft-poster/blob/master/HOCKING-AFT.pdf for log-logistic where you have mentioned beta as the parameter.

AFT is now part of XGBoost: #4763

@hcho3 Can we close this?


FancyZones is not saving my Layout's configuration

Microsoft PowerToys version
0.45.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
Using as specified.
✔ Expected Behavior
Saving my configuration when rebooting my PC.
❌ Actual Behavior
Every time I reboot my PC I loose my FancyZones Layout's Saved Configuration, even if I'm running PowerToys as administrator.
Other Software
No response

Duplicate of #13069

Thanks for reporting this. This issue is a duplicate. We'll track this in #13069 to centralize the discussion thread.


How to speed up compilation?

Hello,
In my project, there are a lot of  classes need  to be exported. the cpp file is about 100,000 lines, takes 30 minutes to compile, and  fails out of memory.
At present, I have split the CPP files.
The compiler is vs2019, and I tried the CLang compiler, but it took a long  time.
So, how can i speed up compilation?
Thanks for your help !

I assume your mainly registering usertypes? This is non-performace critical code, so chunk your usertype defintions into seperate files and cache the object files.
Use CCache (linux, I assume windows has something similar) to speed up object compilation and llvm linker to speed up linking.
Compile times are long - that is the trade off for runtime speed.

My suggestions are along the same lines:

use .new_enum<blah>( { { "name", value }, {"name", value } } ); to explicitly use the initializer_list` form, which is vastly cheaper than the variadic functino form
similarly, use auto ut = state.new_usertype<my_class>("my_class", constructor ); and then ut["foo"] = &my_class::foo to prevent from using the long-form constructor that is a variadic template and thus takes a million years to compile
split usertypes up between different files, make sure they are in .cpp files and not headers to avoid dragging bloat into every other header/compiled file

I have to do a formal compile-time investigation with aras-p's tool. I just have a lot of other things on my plate at the moment, too. 😅


Invalid Version when Using Self-Compiled/Beta PyTorch

I encountered an exception when running import meddlr.ops as oF in an NGC PyTorch container.
The exception says,
>>> import meddlr.ops as oF
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/workspace/meddlr/meddlr/__init__.py", line 3, in <module>
    from meddlr.engine.model_zoo import get_model_from_zoo
  File "/workspace/meddlr/meddlr/engine/__init__.py", line 10, in <module>
    from .hooks import *  # noqa
  File "/workspace/meddlr/meddlr/engine/hooks.py", line 19, in <module>
    from meddlr.evaluation.testing import flatten_results_dict
  File "/workspace/meddlr/meddlr/evaluation/__init__.py", line 2, in <module>
    from .recon_evaluation import ReconEvaluator  # noqa: F401
  File "/workspace/meddlr/meddlr/evaluation/recon_evaluation.py", line 16, in <module>
    from meddlr.data.transforms.transform import build_normalizer
  File "/workspace/meddlr/meddlr/data/__init__.py", line 1, in <module>
    from meddlr.data import build, catalog, collate, data_utils, slice_dataset
  File "/workspace/meddlr/meddlr/data/build.py", line 13, in <module>
    from meddlr.data.slice_dataset import SliceData
  File "/workspace/meddlr/meddlr/data/slice_dataset.py", line 10, in <module>
    from meddlr.data.transforms.transform import DataTransform
  File "/workspace/meddlr/meddlr/data/transforms/transform.py", line 9, in <module>
    from meddlr.forward import SenseModel
  File "/workspace/meddlr/meddlr/forward/__init__.py", line 1, in <module>
    from meddlr.forward import mri
  File "/workspace/meddlr/meddlr/forward/mri.py", line 4, in <module>
    import meddlr.ops as oF
  File "/workspace/meddlr/meddlr/ops/__init__.py", line 1, in <module>
    from meddlr.ops import categorical, complex, fft, utils  # noqa: F401
  File "/workspace/meddlr/meddlr/ops/fft.py", line 10, in <module>
    if env.pt_version() >= [1, 6]:
  File "/workspace/meddlr/meddlr/utils/env.py", line 314, in pt_version
    version = [dtype(x) for x in version]
  File "/workspace/meddlr/meddlr/utils/env.py", line 314, in <listcomp>
    version = [dtype(x) for x in version]
ValueError: invalid literal for int() with base 10: '0a0'

I checked the related lines, the code assumes the PyTorch is using stable versions and installed from binary packs.
https://github.com/ad12/meddlr/blob/b2f055b482c534a2a6eb161c19e6abb6ea94c196/meddlr/utils/env.py#L314
However, the PyTorch in the NGC container is self-complied, and the version string contains a commit ID. It looks like this,
>>> import torch
>>> torch.__version__
'1.13.0a0+08820cb'

I suspect that's why it triggered the exception.
Would you please kindly modify the function to accept the version strings like this?

Thanks for raising this bug! #61 fixes this - meddlr v0.0.4 has this most recent push


Add support for Redis component

Issue Description
Type: feature request
Describe what you expected to happen
Add failure scenarios that you think will occur, such as set, get, etc., operation exception, connection pool full, etc.

#79


FIX: Move _stim.<ext> specification within the Task Events module

This fix builds on #1749 to separate _stim and _physio in the specs.
Currently _stim files are specified sideways as an addon or extra branch of _physio, which can be confusing and misrepresent their intent.
Moving them with the other stimuli definitions increases the consistency of the spec and the findability of _stim specifications.
This fix requires #1749 for a more consistent prescription of tsv.gz files.

This fix builds on https://github.com/bids-standard/bids-specification/issues/1748 to separate _stim and _physio in the specs.

did you mean to reference:

https://github.com/bids-standard/bids-specification/pull/1749 instead?

Since #1749 is looking very close to the finish line, the following link https://github.com/oesteban/bids-specification/compare/fix/large-tabular-files...oesteban:bids-specification:fix/stim-files-with-stimuli can be used to look at the changes specific of this PR without distractions.

I introduced a merged conflict. Will fix.

I introduced a merged conflict. Will fix.

I can take care, will be faster

Perhaps moving them inside the admonition?

Perhaps moving them inside the admonition?

That actually did the trick!

I think this should be ready to merge after the 5 days period.

I agree with the changes here in principle, pending this review item:
* https://github.com/bids-standard/bids-specification/pull/1750/files#r1548105139

it'd be important that the reference to an example points at a valid example

BTW: did a quick check on openneuro via the datalad superdataset and I could not find a dataset with stim files except the one that @oesteban had mentioned.

@Remi-Gau @sappelhoff @effigies - may I merge this? I'd like to rebase BEP020, which will benefit substantially from getting stim out of physio.


Post featured Image Link in Wordpress

jQuery(document).ready(function($) {
$('.news-box h3 a')
.attr('data-cursor-img', '/wp-content/uploads/2023/04/soccer_cover.jpg');
});
REFERENCE FROM THE ATTRIBUTE ABOVE, INSTEAD OF USING A LINK OF AN IMAGE, HOW CAN I SET THE DATA-CURSOR-IMG TO dynamicaly call the post featured image when $('.news-box h3 a') text link is hovered upon? Any clues?

you should write your code together with php!

jQuery(document).ready(function($) { $('.news-box h3 a') .attr('data-cursor-img', '/wp-content/uploads/2023/04/soccer_cover.jpg'); });
REFERENCE FROM THE ATTRIBUTE ABOVE, INSTEAD OF USING A LINK OF AN IMAGE, HOW CAN I SET THE DATA-CURSOR-IMG TO dynamicaly call the post featured image when $('.news-box h3 a') text link is hovered upon? Any clues?

You need put an url of the featured image on the data-cursor-img, if you're make a custom template, you can do it like this
`<?php
// Get the post's featured image URL
$featured_image_url = get_the_post_thumbnail_url(get_the_ID(), 'full');
// Output the HTML element with the data-cursor-img attribute
if ($featured_image_url) {
echo '';
// Your post content here...
echo '';
}
?>
`


Fix summary message in MSMonitor; other minor improvements

Fixes #9425
Status
ready
Description
Minor improvements to the MSMonitor logging.
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
none
External dependencies / deployment changes
none

I took note of the unstable/failing unit test to be followed up in a different GH issue.


error: Unable to find vcvarsall.bat

KittiBox/submodules/utils
python setup.py build_ext --inplace
running build_ext
skipping 'stitch_wrapper.cpp' Cython extension (up-to-date)
building 'stitch_wrapper' extension
error: Unable to find vcvarsall.bat

also tried mingw:
python setup.py build --compiler=mingw32
running build
running build_ext
skipping 'stitch_wrapper.cpp' Cython extension (up-to-date)
building 'stitch_wrapper' extension
creating build
creating build\temp.win-amd64-3.6
creating build\temp.win-amd64-3.6\Release
creating build\temp.win-amd64-3.6\Release\hungarian
C:\MinGW\bin\gcc.exe -mdll -O -Wall -DMS_WIN64 -ID:\ProgramFiles\Conda\include -ID:\ProgramFiles\Conda\include -c stitch_wrapper.cpp -o build\temp.win-amd64-3.6\Release\stitch_wrapper.o
stitch_wrapper.cpp:453:28: fatal error: stitch_rects.hpp: No such file or directory
 #include "stitch_rects.hpp"
                            ^
compilation terminated.
error: command 'C:\\MinGW\\bin\\gcc.exe' failed with exit status 1

I also got the error:
stitch_wrapper.cpp(453): fatal error C1083: Cannot open include file: 'stitch_rects.hpp': No such file or directory
Could you resolve the issue?

I compiled on ubuntu, anyway this vehicle detection doesn't work good, it works similarly to ordinary haar classificator (can give false results)


rocketmq: fix protobuf import path

#17796 moved rocketmq to contrib, but forgot to update the relative import in v4alpha/rocketmq_proxy.proto as it did for v3/rocketmq_proxy.proto. Update the import to fix the Protobuf generation.
This was discovered when trying to build latest envoy with buf. Would you be interested
in adding some buf steps to your CI to avoid this sort of issue in the future?
Commit Message: rocketmq: fix protobuf import path
Additional Description: #17796 moved rocketmq to contrib, but forgot to update the relative import in v4alpha/rocketmq_proxy.proto as it did for v3/rocketmq_proxy.proto. Update the import to fix the Protobuf generation.
Risk Level: Low
Testing: Existing tests
Docs Changes: None
Release Notes: None

CC @mattklein123

Hmm, looks like format is failing probably due to the proto format code not working quite right in v4alpha generation. @htuch is this worth fixing since it's not failing our CI and we are going to remove soon?
/wait

@mattklein123 yeah, v4alpha is not long for this world in the repo, I'll get around to removing after https://github.com/envoyproxy/envoy/pull/17724 lands.

@johanbrandhorst I've been working on adding buf to CI actually! https://github.com/envoyproxy/envoy/pull/17793
It actually caught this same issue, you beat me to it: https://dev.azure.com/cncf/envoy/_build/results?buildId=86148&view=logs&j=b4781dd6-e8d1-56ca-824c-e97e27bdf79d&t=45617383-04d6-5506-f07f-2ba46008d9c7&l=30168
Also, the pre-push hooks seemed to have some trouble when I tried to make this same change on my own fork.


Archived Accounts are included in Account Number Count

App Version: 0.6.2
OS Version: Windows 10 x64
I have three active bunq accounts and two archived ones. In the BunqDesktop app, the text at the top says "bunq accounts - 5". It seems like the number shown there also includes archived accounts, not only active ones.
Either the number should be calculated excluding archived accounts, or there should be the possibility to view archived accounts.

Thanks for the bug report. I fixed it and this will be added in 0.7.0


Handle multiple batches in a more generic way

Currently the way we handle multiple batches is to send repeated trajectories as input.
This is memory consuming and also might cause degradation in performance as deep inside we use tf.map_fn which runs with O(elem.shape[0]) So effectively, by sending reoeated trajectory, we seem to not be in great place. (Although on a contrary, using parallel_iterations will help us here, but mostly not by a lot. I still need to do some simple benchmark tests.).
However, we still need support for multiple trajectory for distributed training and training in a reconstruction pipeline that runs on multiple trajectories.
We can still come to a generic solution which can handle batches better even if we dont send repeated trajectories. That way, we can carry out the computations more easily in a vectorized fashion!
Tasks :

[ ]  I will add a colab notebook here, to actually understand if there is any issues and what is the impact.
[ ] If we have a strong impact, we can work in such a way that we can work across coils and batch dimension internally as long as the trajectory is the same.

Also, a side note here that when executing eagerly, parallel_iterations = 1, making debugging of code extremely slow (batch_size times slower), which is bad in case we want to reach to better results and iterate faster..

Just to make sure we are on the same page, in eager mode it's 1 by default, we could definitely work on that to make it higher.

No, if i set it higher i get a warning saying that cant run it in parallel in eager mode. The parallel iterations are used particularly while graph is being built, so this cant be done in eager mode.


Is it possible to generate the dll files of the projects to access the functions from unity

Hi and thank you for the code!
I want to ask you if it is possible to generate the dll files of xamarin project (android, ios, uwp) to be used in unity, I mean build the projects, through class library in visual studio and then access the methods in c# in unity and build the final app from unity
Thank you
Best regards

In theory yeah. You could take the source out of the application projects and into class libraries than build for each platform. Those could then be exposed to your scripts in Unity.


Scheme Registry doesn't work as befoer

Previously with the Android legacy httpclient, I have code like this:
 SchemeRegistry schReg = new SchemeRegistry();
 schReg.register(new Scheme("http", PlainSocketFactory.getSocketFactory(), 80));
 schReg.register(new Scheme("https", new TLSSocketFactory(), 443));
 ClientConnectionManager conManager = new ThreadSafeClientConnManager(
                        params, schReg);

Where TLSSocketFactory() implements LayeredSocketFactory().
However, after replacing with httpclient-android, it doesn't compile. Any suggestion?
Thanks.

Oh...my mistake. Please ignore this.


[DOCFIX] Change the group in Powered-By-Tachyon.md of Chinese version from "Dev Resources" to "Resources"

The group attribute in Powered-By-Tachyon.md of Chinese version hasn't been modified to "Resources"

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8533/
Test PASSed.


How to remove underline Class name

Hi
I like this syntax a lot, but how to remove underline Class name? It's really painful to see it.
Thanks

Hey @edyywang -- you can tweak those styles in your styles.less file:
https://atom.io/docs/latest/using-atom-basic-customization#style-tweaks
For example, try adding this:
atom-text-editor::shadow .entity.name.type {
  text-decoration: none;
}

@izuzak I was wondering how would I prevent the class parameters from being underlined as  well?
Thanks


[2.4] KDM Release - k8s Jan patches

Going with v2.4.13 release:

Kubernetes Version
Rancher Versions

1.18.15
2.4.5+

1.17.17
2.4.4+

https://github.com/rancher/kontainer-driver-metadata/pull/465

https://github.com/rancher/kontainer-driver-metadata/pull/465

Available to test with dev-v2.4 KDM.

Available to test with dev-v2.4 KDM.

Verified an upgrade from 2.4.12 to 2.4.13-rc3
Steps:

On 2.4.12 pointing to release-v2.4 - deployed clusters for all 4 network providers - 1 etcd, 1 control and 2 worker nodes
Pre upgrade checks looked good
Upgrade to 2.4.13-rc3, changed KDM to dev-v2.4
Upgraded K8s versions to new versions 1.18.15 and 1.17.17
Post upgrade checks looks good

Verified an upgrade from 2.4.12 to 2.4.13-rc3
Steps:

On 2.4.12 pointing to release-v2.4 - deployed clusters for all 4 network providers - 1 etcd, 1 control and 2 worker nodes
Pre upgrade checks looked good
Upgrade to 2.4.13-rc3, changed KDM to dev-v2.4
Upgraded K8s versions to new versions 1.18.15 and 1.17.17
Post upgrade checks looks good

On 2.4.13-rc3 fresh install

The kubernetes version came up with new versions 1.18.15 and 1.17.17
rke-tools version is v0.1.69
Deployed clusters for 4 network providers with the k8s versions 1.18.15 and 1.17.17
Network related test cases - PASS
Validation test cases - PASS

On 2.4.13-rc3 fresh install

The kubernetes version came up with new versions 1.18.15 and 1.17.17
rke-tools version is v0.1.69
Deployed clusters for 4 network providers with the k8s versions 1.18.15 and 1.17.17
Network related test cases - PASS
Validation test cases - PASS

Min rancher version checks for 2.4.4

2.4.4 pointing to release v2.4 - changed to dev v2.4
On all network providers each with 1 etcd, 1 control plane and 2 worker nodes deployed clusters with k8s version 1.17.17
All network related test cases - PASS

Min rancher version checks for 2.4.5

2.4.5 pointing to release v2.4 - changed to dev v2.4
On all network providers each with 1 etcd, 1 control plane and 2 worker nodes deployed clusters with k8s version 1.18.15
All network related test cases - PASS

Min rancher version checks for 2.4.4

2.4.4 pointing to release v2.4 - changed to dev v2.4
On all network providers each with 1 etcd, 1 control plane and 2 worker nodes deployed clusters with k8s version 1.17.17
All network related test cases - PASS

Min rancher version checks for 2.4.5

2.4.5 pointing to release v2.4 - changed to dev v2.4
On all network providers each with 1 etcd, 1 control plane and 2 worker nodes deployed clusters with k8s version 1.18.15
All network related test cases - PASS

Reopening the issue because we have 2 more versions coming in, for the rke-tools update:

Kubernetes Version
Rancher Versions

v1.16.15-rancher1-4
2.4.4+

v1.15.12-rancher2-8
2.4.6+

Reopening the issue because we have 2 more versions coming in, for the rke-tools update:

Kubernetes Version
Rancher Versions

v1.16.15-rancher1-4
2.4.4+

v1.15.12-rancher2-8
2.4.6+

Upgrade checks from 2.4.12 to 2.4.13-rc4

Canal clusters for v1.16.15-rancher1-4 and v1.15.12-rancher2-8 deployed on 2.4.12
Run pre upgrade checks
Upgrade to 2.4.13-rc
Upgrade k8s versions
rke-tools changed to new
Run post upgrade checks.
Snapshot after upgrade of rancher also used new rke tools
New RKE tools was on the nodes

Upgrade checks from 2.4.12 to 2.4.13-rc4

Canal clusters for v1.16.15-rancher1-4 and v1.15.12-rancher2-8 deployed on 2.4.12
Run pre upgrade checks
Upgrade to 2.4.13-rc
Upgrade k8s versions
rke-tools changed to new
Run post upgrade checks.
Snapshot after upgrade of rancher also used new rke tools
New RKE tools was on the nodes

Fresh install checks for rke-tools 2.4.13-rc4

Canal clusters for v1.16.15-rancher1-4 and v1.15.12-rancher2-8
Verified the rke-tools version be v0.1.69
Run network test cases and validation test cases

Min version checks:

Fresh installation of 2.4.4
Bring up all the network providers with v1.16.15-rancher1-4
Update the rke-metadata config
Verify rke-tools version updated [v0.1.69] on the nodes
Run network test cases

Fresh installation of 2.4.6

Bring up all the network providers with v1.15.12-rancher2-8
Update the rke-metadata config
Verify rke-tools version updated [v0.1.69] on the nodes
Run network test cases

Fresh install checks for rke-tools 2.4.13-rc4

Canal clusters for v1.16.15-rancher1-4 and v1.15.12-rancher2-8
Verified the rke-tools version be v0.1.69
Run network test cases and validation test cases

Min version checks:

Fresh installation of 2.4.4
Bring up all the network providers with v1.16.15-rancher1-4
Update the rke-metadata config
Verify rke-tools version updated [v0.1.69] on the nodes
Run network test cases

Fresh installation of 2.4.6

Bring up all the network providers with v1.15.12-rancher2-8
Update the rke-metadata config
Verify rke-tools version updated [v0.1.69] on the nodes
Run network test cases


Latest Dockerfile/Image has errors

Just pulled the latest Docker image and tried running a command but getting the following error:
python: can't open file 'setup.py': [Errno 2] No such file or directory.
Latest push was a day ago so may have been something from that.

Do you have a setup.py file in the directory in which you're running the container?

@andrewoh531  - did you manage to get this working with a setup.py in the base directory?  I think the bigger issue here is just having better documentation/examples on how to use the docker image.  @troyready do you guys use it at all?

Sorry I moved on from stacker. It may have been an error on my side and/or lack of documentation. Closing this issue.

@phobologic it's really only mentioned by as as a theoretical 'fallback' option / support for older versions . I put a no-op setup.py alongside all of our configurations to support this (since the config yamls specify a local sys_path for the blueprints).

@troyready cool, thanks!


How to style the systray menu?

Can anyone tell me how to style (with css) the systray menu?
I can style it changing the settings for the * class, but that is not an ideal solution. I tried using eww inspector to gather more information, but the menu disapper when I click on anything in the screen, so it can't be selected in the debugger.

In your yuck use (systray :class "DesiredNameHere") then reference it in css with .DesiredNamerHere {background-color: red;}

menu {
  padding: 5px;
  background-color: $background;
  color: #fff;

  menuitem {
    border-radius: 5px;
    padding: 8px 12px;
  }
  menuitem:hover {
    background-color: $blue;
  }
}


Complete "hole" interface

Made an interface that will be linked to the graph generator, making certain spots in the graph "dead," and unable to have nodes.
This is just a PR for the interface.

Looks fine.

I've completed the "obstacle" feature.
Let me know what you think


Question: how to change selected item background color and cursor character

Sorry for making Issue with this one, but I couldn't find anything and none of highlight groups worked for some reason
For color (how to change it):

And also I'd love to know if it's possible to change cursor from "full block" (█) to "beam" (|)

Was able to change colors, thanks.
Also googled about terminal cursor shape and it isn't possible right now (https://github.com/neovim/neovim/issues/3681), so I'm closing


Inverse of an array Added #847

#847 Done
@rudrakshi99  @OjusWiZard @nakul-19
Please Review it

#1620 correct PR

Done with Good Aproach in other PR


High-level flexible and fine-grained column level access control through encryption with pluggable key access

This JIRA is an extension to Parquet Modular Encryption Jira(PARQUET-1178) that will provide the basic building blocks and APIs for the encryption support. On top of PARQUET-1178, this feature will create a high-level layer that enables fine-grained and flexible column level access control, with pluggable key access module, without a need to use the low level encryption APIs. Also this feature will enable seamless integration with existing clients.
A detailed design doc will follow soon.
Reporter: Xinli Shang
Related issues:

EncryptionPropertiesFactory and DecryptionPropertiesFactory (Blocked)

Externally tracked issue: https://issues.apache.org/jira/browse/PARQUET-1178
Note: This issue was originally created as PARQUET-1325. Please see the migration documentation for further details.

Xinli Shang:
This Jira is replaced by Parquet-1396.


Deprecation support in the generator

Heya @jbalsas @izaera
As I've been looking through the SDK, I noticed in the generator-liferay-theme that you guys had done some refactoring to the deprecation support.
What I'm noticing is a bit different than what I was expecting, and wanted to clear it up with you guys on what the intent is before submitting a pull to "fix" it.
What is currently happening

Just running yo liferay-theme

After selecting 7.1 as my Liferay version, it prompts for me to choose a language, but only .FTL is supported
If I choose 7.0, it skips the question, and immediately goes to the npm install portion of the lifecycle.

Running yo liferay-theme --deprecated

After selecting 7.1, it still prompts me to choose a language, but only Freemarker is listed
If I choose 7.0, it will prompt me to choose between Velocity and Freemarker

What I expect to happen

Just running yo liferay-theme

After selecting 7.1 as my Liferay version, it should immediately skip the question and go to npm install
If I choose 7.0, it should behave as 7.1 (no question prompted)

Running yo liferay-theme --deprecated

This one is probably the most questionable, but I'm assuming we're officially dropping Velocity support as of 7.1, so I would imagine it would still skip the prompt
If I choose 7.0, it should prompt as it does now

I think my question is twofold: 1, do you guys agree that the way I typed above is correct, and 2, whether or not we want to keep Velocity as a deprecated option (I'm doubting it, but wanted to check first rather than assuming).
If you guys agree on my expectations, I can submit a pull to change that portion.
Thanks guys :)

Hey @natecavanaugh, thanks a lot for looking into this!
I agree with your expectations. We removed velocity support for theme templates in 7.1, so yeah, there's no sense in supporting it under deprecated for a 7.1. theme.
Feel free to go ahead with the PR in that direction :)

@natecavanaugh : there’s a thing called divert in the theme generator. It’s not as good as I would like it to be, but I introduced it as a first attempt to manage different target versions.
The rationale behind it is that modules loaded with “divert” use the code in common except if there is an specific folder for the version being targeted (7.0 in this case).
For example, in this line the divert call loads this when the target version is 7.0, and this for any other target version (currently it could only be 7.1). Of course, as you may have guessed, both files export the same interface.
Take a little time to understand how it works and if you have any doubt, don't hesitate to ask.
Cheers :-)


Added proposed impl. details for user authentication system

Coverage remained the same at 65.551% when pulling 97d808c4f08bbd2fdeafc0f24934c4263e630664 on m-aslam-mj2:staging4 into 4abcf5d30de161229579ff5626215e12dcdb0775 on CS2113-AY1819S1-T16-1:master.


Permissions on vasp files are not set properly

as the title says,
spack@setonix-01:gcc-12.1.0$ ls -lah  | grep vasp
drwxr-sr-x   4 spack spack 4.0K Nov  8 19:07 vasp-5.4.4-zrju2pmfu6wzqkq7ogkjccfensnmflwf
drwxr-sr-x   4 spack spack 4.0K Nov  8 19:36 vasp-6.2.1-hubld72zncwadyttun2vtg26jdd62zix
drwxr-sr-x   4 spack spack 4.0K Nov  8 20:06 vasp-6.3.0-ewt4rli3l3fwsj4asz3dz2kdnwwhjyrn

what we want is
spack@setonix-01:gcc-12.1.0$ ls -lah | grep vasp
drwxr-s---   4 spack vasp  4.0K Nov  8 19:07 vasp-5.4.4-zrju2pmfu6wzqkq7ogkjccfensnmflwf
drwxr-s---   4 spack vasp6 4.0K Nov  8 19:36 vasp-6.2.1-hubld72zncwadyttun2vtg26jdd62zix
drwxr-s---   4 spack vasp6 4.0K Nov  8 20:06 vasp-6.3.0-ewt4rli3l3fwsj4asz3dz2kdnwwhjyrn
spack@setonix-01:gcc-12.1.0$

https://github.com/PawseySC/pawsey-spack-config/blob/main/setonix/setup_scripts/post_set_licensing_permissions.sh

so, Spack has a feature to take care of that in the yaml configs,
but we had discussed with Pascal, Sam and team a few months ago that we wanted to have full control on the permission settings... can be changed of course :-)

We stick to our bash scripts. Thanks Marco.


Fix/discounts UI

Implements the Polaris discount UIs for TIKI app.
This PR implements the UIs and the backend functions to save the UI data.
The save/edit functions and the dynamic fields will be handled by #103, #105, #106 and #107, with specific backend functions.
The helper messages and dashboard UI will be added in #97
How to test
in frontend folder run npm run start. The following routes are implemented:

/ui - Dashboard placeholder. Will be the root of the app UI in Shopify admin backend.
/ui/discounts/product - Product discounts UI
/ui/discounts/order - Order discounts UI

The UIs are equal but we need both for configuring discounts that will be applied to just a product or the whole order, following Shopify default UX.

Added the code for handling the data saving in the backend.


add new dev wisdoms

add new dev wisdoms to the tiny troves of wisdom game

Thanks for your contribution!


Does pw work with iCloud Keychains?

I wonder is it possible to work with icloud keychains?

@snakewa
Unfortunately not, as the security model of the iCloud keychain is very different from the security model of the original file-based keychain


Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[X] Android
[ ] UWP
[ ] watchOS
[ ] tvOS
[ ] Tizen
[ ] .NET Standard

Feature Library

[ ] Core
[X] BluetoothLE
[ ] Beacons
[ ] Locations
[ ] HTTP Transfers
[ ] Notifications
[ ] Sensors

Version of Library
<IP_ADDRESS>1-beta
Version of OS(s) listed above with issue
8.1 & 9.0
Steps to Reproduce
To reproduce this, I adjusted the sample project for ease of use.  Make the following changes in the following files.

GattServerViewModel.cs
Change the following to pass a string array:
     byte[] abit = System.Text.Encoding.UTF8.GetBytes("--Test--");
     await this.peripheralManager.StartAdvertising(new AdvertisementData
     {
         LocalName = LocalName,
         ManufacturerData = new Shiny.BluetoothLE.ManufacturerData(ushort.Parse("242"), abit)
     });

PeripheralItemViewModel.cs
Under the Update function:
         //this.LocalName = ad.LocalName; <-- comment here
         this.TxPower = ad.TxPower;
         if (ad.ManufacturerData != null)
         {
             this.LocalName = ad.ManufacturerData.CompanyId.ToString() + ": " + System.Text.Encoding.UTF8.GetString(ad.ManufacturerData.Data);
         }

Expected Behavior
In the previous library, BLE - I was able to pass a string array as long as it was beneath the 26 bytes reserved.  I should be able to read that array
Actual Behavior
If I pass a string array, the server doesn't appear to start.  If I remove the array, the server will appear.
Allan, I had implemented the library before contacting you via email - this is why I thought the server was not working.  Thank you for your excellent work on this project, it is much appreciated.
regards,
Dave

Have you tried disabling the device name and seeing if the manufacturer data can go?
Is there any error in the console?
Have you checked online to see if there is anything weird with certain devices?

I tried 3 different Android devices, the same ones that work on the old library but I need the IsConnectable that isn't supported on the old Android version.  I am not sure how many different combinations I can try.  If you suggest a few - I will try.
How do I disable the device name?

Can you tell me how to disable the device name?  I do not see how to do this on either the adapter or the server objects.  I provided the steps above on how to reproduce this - could you give me some code back to resolve this?

No offense, this isn't tech support and I don't owe you anything.  I don't know how to resolve your issue because I don't know what it is.  The source code is all open for you to debug yourself.  This is the line you are looking for:
https://github.com/shinyorg/shiny/blob/f124695ebbda81d1f8462c88ab835d72400dbed4/src/Shiny.BluetoothLE/Peripherals/Platforms/Android/PeripheralManager.cs#L76

I am not trying to ask for tech support, I was reporting a bug which your suggestion above fixed.  I altered the StartAdvertising to allow the bool to disable it.  I just didn't know your library well enough to find that reference.
I appreciate the response.  Have a good day.


version information wrong for <IP_ADDRESS>

In the plugin-descriptor.properties file for version <IP_ADDRESS>, the version property is still set to <IP_ADDRESS>. That's causing issues with my deployment automation, which always thinks the plugin is out of date and so re-installs it on every run.
I don't really know the right approach to fix this, since Maven release artifacts are supposed to be immutable. Maybe just release <IP_ADDRESS> with no changes except fixing the errant version number?
Separately, you may want to make Maven generate the plugin-descriptor.properties file as part of the build so that the version always matches the one in the POM, which will make it so using the Maven release plugin will just work.

thx, will fix this