Unexpected token when using "node server.js" with transpiled express server

I am using babel to transpile everything into a build folder, if i try running server.js with
cd build
node server.js
I get this error
SyntaxError: C:/web-liga/node_modules/next/dist/pages/_error-debug.js?entry: Unexpected token (14:11)
  12 |     const { name, message, stack, path } = this.props
  13 |
> 14 |     return

     |            ^
  15 |
  16 |         <meta name='viewport' content='width=device-width, initial-scale=1.0' />
  17 |

But if i run the server using "npm run dev"
"scripts": {
    "build": "node_modules/.bin/babel ./ --out-dir build -s --ignore node_modules",
    "clean": "rm -rf build && mkdir build",
    "dev": "npm run clean && npm run build && npm run watch",
    "start": "NODE_ENV=production node build/server.js",
    "watch": "node_modules/.bin/babel-watch --exclude components --exclude pages --exclude .next build/server.js"
  }

Everything runs perfectly except that .next is getting compiled outside of the build folder because thats where im running npm from
All of this brings problems when trying to deploy to heroku or now

could you show this file complete, gist or pastebin.

http://pastebin.com/jRHgar4Z
This is the file structure
-actions
-build
-components
-database
-layouts
-node_modules
-pages
-reducers
-services
package.json
server.js
store.js

@angel200sdnot was the other file that contains the head.

@aranajhonny None of my files is has

ok but so it is difficult to help you. there must be a syntax error somewhere.

Yeah i know, sorry i've been trying to fix this for days now, in the meantime ive been using the "npm run dev" to keep on developing
If you want the file the error is pointing at its located in the next module, which is this
import React from 'react'
import Head from 'next/head'
import ansiHTML from 'ansi-html'

export default class ErrorDebug extends React.Component {
  static getInitialProps ({ err }) {
    const { name, message, stack, module } = err
    return { name, message, stack, path: module ? module.rawRequest : null }
  }

  render () {
    const { name, message, stack, path } = this.props

    return

        <meta name='viewport' content='width=device-width, initial-scale=1.0' />

      {path ?
Error in {path}
 : null}
      {
        name === 'ModuleBuildError'
        ?

        :
{stack}

      }

  }
}

const encodeHtml = str => {
  return str.replace(/</g, '<').replace(/>/g, '>')
}

// see color definitions of babel-code-frame:
// https://github.com/babel/babel/blob/master/packages/babel-code-frame/src/index.js

ansiHTML.setColors({
  reset: ['fff', 'a6004c'],
  darkgrey: 'e54590',
  yellow: 'ee8cbb',
  green: 'f2a2c7',
  magenta: 'fbe7f1',
  blue: 'fff',
  cyan: 'ef8bb9',
  red: 'fff'
})

everything looks good, apparently the error has nothing to do directly with next.js you can be on the other side.

try to wrap your returned value with ()

@angel200sdnot can we have a sample repo of this? So, we could have a look at this quickly.

@arunoda https://github.com/angel200sdnot/web-liga

I can see the error. It's kind a weird. I'm looking at it.

@angel200sdnot here's how you can fix this issue.
First of all, remove everything in your node_modules directory.
Then remove node_modules from your babel ignore list.

@arunoda This fixed the issue, thanks

@nkzawa we get this because, we don't transpile content inside our pages directory.
Then user explicitly asked to ign

@angel200sdnot great.
But I want to do a proper fix: https://github.com/zeit/next.js/pull/731


Convert v1 selector based LB to v2

If selector is defined on LB service level in v1, it should be transformed to the selector on the port rule in v2.
@deniseschannon we've decided to fix it on the rancher compose side

This is currently malfunctioning on Rancher 1.2.2 (Compose v0.12.1).
When running rancer-compose up on a Docker compose file written from Rancher <1.2 it partially converts the label based LB targets to the newer load balancer but incorrectly sets them to type TCP so the path is ignored causing apps that rely on path routing to fail.
It seems the paths are being read and set. For example an old style LB with a label of     io.rancher.loadbalancer.target.twitter-profile-service: /twitter=8082 created an entry in the new LB config screen targeting twitter-profile-service on port 8082 and once you change the type from TCP to HTTP the path shows correctly in the UI.
Currently for operational reasons we must keep backwards compatibility in our docker-compose & rancher-compose files so this is unfortunately blocking us from upgrading to 1.2.
If you need any more info please don't hesitate to ask.

@joshwget Sure thing

Tested with rancher-server version - v1.4.0-rc3
Created a stack with following yml where Lb is v1 selector based .
lb-1:
  ports:
  - 4001:80
  labels:
    io.rancher.service.selector.link: test2=bar
  image: rancher/load-balancer-service
test-752736:
  labels:
    test2: bar
  image: sangeetha/testlbsd:latest
test-479268:
  labels:
    test2: bar
  image: sangeetha/testlbsd:latest

lb-1:
  scale: 1
  health_check:
    port: 42
    interval: 2000
    unhealthy_threshold: 3
    healthy_threshold: 2
    response_timeout: 2000

When Lb gets created with selector based Port Rule as expected.
Lb is functional and directs traffic to all the containers that have the specified label.


The strict-ssl config is ignored

pnpm version: 0.36.0
Code to reproduce the issue: pnpm i
Expected behavior:
Everything good.
Actual behavior:
"strict-ssl=false" in .npmrc or /users/.npmrc ignored at all and "Unable to verify certificate error".

This should be easy to fix. We use npm-registry-client. We just need to set the ssl.strict option for it

Where can I start?

The RegClient is created here. You just have to pass the option there. The option should be added also to PublicInstallationOptions as sslStrict and to all the places where TypeScript will tell you

I suggest to set not just ssl.strict but all the other options that npm passes to npm-registry-client as well. Here's a map of npm configs to npm-registry-client options

Landed in v0.37.0


feat(no UKI): improve EFI booting from USB stick

Fixes: https://github.com/kairos-io/kairos/issues/3063
https://wiki.debian.org/RepackBootableISO

Closing in favor of https://github.com/kairos-io/AuroraBoot/pull/135


Convert example project to ts (#1)

++ hedera local node start stop scripts

++ test to package scripts

++ get-current-block task & startBlock to sg.yaml

+- contract-call hardhat task

small config changes

switch off github workflows

small config changes from desktop

config changes mac

+- hardhat-example project to typescript

remove internal network from hardhat config

++ typechain gen types script

++ greeter-factory.test.ts

+- subgraph-example yaml for GreeterFactory

++ call setGreeting on greeter{1&2}

commented out emit GreetingSet in constructor

neatened up subgraph

Description:

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Closing this PR as it's only for a demo for #644


Custodian's table has repeated rows

When an admin goes to the 'Manage Custodians' page, the table listing the custodian shows repeated rows.
If one of the custodians is in more than one time, the same row is repeated as many times as teams has the custodian. It makes sense to have the custodian repeated but the values 'Registers' and the links to 'View Team' should be different for each row, right now, their are the same for all the entries related with a custodian.
URL
/custodians#custodians
** Steps to reproduce**

Log as admin
Click 'Manage Custodians'

Expected result
If a custodian is in more than one team, a row for each team the custodian is in but with different registers and links.
Actual Result
All the rows are exactly the same.
/cc @Maidment64

not 100% sure I understand - can I clarify that:
currently if a custodian is assigned to more than one register, they appear multiple times in the 'manage custodians' table
this should be the case, but each row should relate to a different register - currently each row for an individual repeats the same register.
so currently:
Ellie Craven -- > Register Register
Ellie Craven -- > Register Register
should be
Ellie Craven -- > Register Register
Ellie Craven -- > Field Register
If this is the case - are we confident that this is an error in the display of the assigned register, and not an error in the staging app created by members of the team being added to the same register more than once before we had implemented any validation?
Either way, we should fix this before external release 1.


Update s3, sdk-core, sqs to 2.17.236

Updates

software.amazon.awssdk:s3
software.amazon.awssdk:sdk-core
software.amazon.awssdk:sqs

from 2.17.191 to 2.17.236.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #520.


Offline transaction - not able import QR on offline machine

Steps:

Close wallet and clear all profiles (Linux ~/.symbol-desktop-wallet)
Turn off Internet Connection
Open wallet again.
Create or import profile
Logout
Go to Offline transaction
"Cosign transaction" tab
"Import QR Code"
Try import QR

When we try import QR (for example by file upload) scanner is not processing.
I checked on web version and wallet is trying connect to network to get resource (not sure if same issue is on Electron app but it's very likely). Js should be included to app.
<EMAIL_ADDRESS>

the issue is tested , under the cosign transaction during offline(withut internet), imported QR code and it worked. so this can be closed


Compilation fails

Compilation fails with a nightly compiler:
   Compiling oursh v0.4.3
error[E0599]: no function or associated item named `with_options` found for struct `std::fs::File` in the current scope
   --> /home/dev/.cargo/registry/src/github.com-1ecc6299db9ec823/oursh-0.4.3/src/program/posix/mod.rs:220:46
    |
220 | ...                   let file = File::with_options()
    |                                        ^^^^^^^^^^^^ function or associated item not found in `std::fs::File`

error[E0599]: no function or associated item named `with_options` found for struct `std::fs::File` in the current scope
   --> /home/dev/.cargo/registry/src/github.com-1ecc6299db9ec823/oursh-0.4.3/src/program/posix/mod.rs:229:46
    |
229 | ...                   let file = File::with_options()
    |                                        ^^^^^^^^^^^^ function or associated item not found in `std::fs::File`

error[E0599]: no function or associated item named `with_options` found for struct `std::fs::File` in the current scope
   --> /home/dev/.cargo/registry/src/github.com-1ecc6299db9ec823/oursh-0.4.3/src/program/posix/mod.rs:238:46
    |
238 | ...                   let file = File::with_options()
    |                                        ^^^^^^^^^^^^ function or associated item not found in `std::fs::File`

For more information about this error, try `rustc --explain E0599`.
error: failed to compile `oursh v0.4.3`, intermediate artifacts can be found at `/home/dev/.cache/tmp/cargo-installDjSFLz`

Caused by:
  could not compile `oursh` due to 3 previous errors

Hmmmm, this should be a really small fix. But there seems like there might be another bug here too...

:yawning_face:
Closed with 41978f5b.

FWIW, the other bug is related to #26.


prod-requirements.md: Fix grammar.

Change "strong" to "strongly" (adverb).

(Closed previous PR because it was on my master and was annoying.)

Merged, thanks @lonerz!


is there a way to create an end point for downloading a file?

Thanks for the help but I am interested in getting an endpoint for doing the opposite - returning (downloading) a file instead of uploading one within fastui framework. Any idea?

That makes me think of the server component ServerLoad although I have no experience with it yet. In the Recorder component I'm putting together, I have a typescript function that conditionally executes on the client-side browser, if the python FastUI component has save_download=True. I'll provide that typescript code below. It's blob data is set dynamically during runtime, it's supplied by the browser API MediaRecorder class, and it functions as expected.
  const handleDownloadRecording = (blob: Blob): void => {
    const url = URL.createObjectURL(blob);
    const a = document.createElement('a');
    a.style.display = 'none';
    a.href = url;
    a.download = 'recording.webm';
    document.body.appendChild(a);
    a.click();
    window.URL.revokeObjectURL(url);
  }

Is that closer to what you're talking about? Or are you thinking about a separate FastUI download component? Just thinking out loud, couldn't you use the Form component? Then again, maybe there's no way for you to route the file to the client rather than the endpoint. Then again, I could just be confusing myself about it now 😃
Can you provide a step by step of what you want/expect to happen and include your best guess which environment that step takes place (typescript react / python FastUI). If it's python FastUI, it would help if you also included if it's in the endpoint vs the initial instance layout code too.
Maybe what you need is a custom FileDownload component where the file Blob is set dynamically, I'm not sure if this is possible with the existing ServerLoad or not but that too is worth investigating.

I would like a new FastUI component for that, something like DownloadEvent, so that I can create an endpoint like this:
@router.post("/download")
async def download() -> list[AnyComponent]:
	file = gen_file()   // returns a io.BytesIO object or a file handle maybe
	file_name = ...

return [c.DownloadEvent(file_handle = file, name = file_name)]

this will result in a file download in broswer....

Oh okay, I was making it much more complex in my mind. 😃
The good news, what you're looking to do is possible with the current version of FastUI. It looks like the mistake you're making has to do with thinking about everything you want, all at once. At least that's how I've made similar mistakes. For example, your endpoint is trying to do 2 things; it's trying to generate the file and the return type list[AnyComponent] is saying it wants to return the UI. Sometimes it's helpful to remind yourself that the UI is served independent from anything in the python backend.
In the specific case adding download links to dynamically created files, split the dynamic file generation and the return of that file from the UI element Link which is pointing to the file. Below I've created a gen_file function to mock dynamically generating the file bytes and filename. I split the demonstration into two endpoints for clarity but there's no reason you can have a single endpoint that uses something like query string params to conditionally return different files or to be used in the dynamic generation of a file. In fact, I'll include a 3rd endpoint that serves both.
I've added a 3rd endpoint which uses a path parameter to determine if the file is returned from the bytes stream or if a static tempfile is generated and returned. The gen_file function allows for dynamic content and a custom filename now too. There are example links for each of the options, including the dynamically determined file creation using the same endpoint and a path parameter of stream or static, and an optional query string parameter to override the name. Note that the GoToEvent has an attribute for query which I believe will convert a dict to query string parameters but you'll need to play with that to verify how it works.

import io
import tempfile
from fastapi import FastAPI
from fastapi.responses import FileResponse, StreamingResponse

app = FastAPI()

@app.get('/', response_model=FastUI, response_model_exclude_none=True)
def components_view() -> list[AnyComponent]:
    return [
        c.Page(
            components=[
                c.Heading(text='Download Links', level=2),
                c.LinkList(
                    links=[
                        c.Link(
                            components=[c.Text(text='Download File (Stream)')],
                            on_click=GoToEvent(url='/api/dl_file_stream', target='_blank'),
                        ),
                        c.Link(
                            components=[c.Text(text='Download File (Static)')],
                            on_click=GoToEvent(url='/api/dl_file_static', target='_blank'),
                        ),
                        c.Link(
                            components=[c.Text(text='Download Dynamic File (Stream)')],
                            on_click=GoToEvent(url='/api/dl_file/stream', target='_blank'),
                        ),
                        c.Link(
                            components=[c.Text(text='Download Dynamic File (Static)')],
                            on_click=GoToEvent(url='/api/dl_file/static', target='_blank'),
                        ),
                        c.Link(
                            components=[c.Text(text='Download Dynamic File-Customized Name (Stream)')],
                            on_click=GoToEvent(url='/api/dl_file/stream?filename=my_stream_generated_file.txt', target='_blank'),
                        ),
                        c.Link(
                            components=[c.Text(text='Download Dynamic File-Customized Name (Static)')],
                            on_click=GoToEvent(url='/api/dl_file/static?filename=my_static_tempfile_generated_file.txt', target='_blank'),
                        ),
                    ],
                ),
            ]
        )
    ]

def gen_file(extra_text: str | None = None, override_filename: str | None = None) -> tuple[io.BytesIO, str]:
    content = f"This is the content of the file.\n{extra_text or 'The End'}"
    file_bytes = io.BytesIO(content.encode())
    filename = override_filename or "my_generated_file.txt"
    return file_bytes, filename

@app.get("/api/dl_file/{source}")
async def dl_file(source: str | None = None, filename: str | None = None):
    file_bytes, filename = gen_file(f"I was generated from '{source}' path parameter.", filename)
    if source == 'stream':
        async def iterfile():  # Generator function
            yield file_bytes.getvalue()

        response = StreamingResponse(iterfile(), media_type="application/octet-stream")
        response.headers["Content-Disposition"] = f"attachment; filename={filename}"
        return response
    elif source == 'static':
        with tempfile.NamedTemporaryFile(delete=False) as temp_file:
            temp_file.write(file_bytes.getvalue())

        return FileResponse(temp_file.name, filename=filename, media_type="application/octet-stream")
    return {"detail": "Supported path query values are 'stream' and 'static'."}

@app.get("/api/dl_file_static")
async def dl_file_static():
    file_bytes, filename = gen_file()

    with tempfile.NamedTemporaryFile(delete=False) as temp_file:
        temp_file.write(file_bytes.getvalue())

    return FileResponse(temp_file.name, filename=filename, media_type="application/octet-stream")

@app.get("/api/dl_file_stream")
async def dl_file_stream():
    file_bytes, filename = gen_file()

    async def iterfile():  # Generator function
        yield file_bytes.getvalue()

    response = StreamingResponse(iterfile(), media_type="application/octet-stream")
    response.headers["Content-Disposition"] = f"attachment; filename={filename}"
    return response

it worked really nicely! Thanks so much for help!

I found some issue about this moment. The site lose headers from user, and can't using
user: Annotated[User | None, Depends(User.from_request_opt)] in download get. But if i use router link site back "Request Error
Response not valid JSON"

Pleased you sorted it 👍.


Added support for StackedBar charts

I wanted to use a stacked bar chart in a project so added it to chart.xkcd (https://github.com/timqian/chart.xkcd/pull/54).  I figured I would add it here as well.

Thank you for the PR, merged. (:


golang.org/x/text CVE-2021-38561

there is a cve in golang.org/x/text before 3.8. https://www.cve.org/CVERecord?id=CVE-2022-32149.
bump the version to 3.8 should do.

Has been fixed with https://github.com/go-playground/validator/pull/1015.


problem in signal mode

i try to run libcamera-still with -s option but the process run continuously until i send SIGUSR2 signal .
the process don't wait after the first image.
it works well with -k (keypress) option .
is it normal ?
libcamera-still --version
libcamera-apps build: 6145daf-intree 27-11-2021 (07:06:36)
libcamera build: v0.0.0+3156-f4070274

Thanks for reporting this. I'll check it out as soon as I can.

Yes, sorry about that. I've just pushed a fix here: https://github.com/raspberrypi/libcamera-apps/pull/160

This has been merged now so I'll close this issue. We'll get it into our apt repository shortly, if the feature is more urgent then libcamera-apps can be built from source.

Yes it works! Thanks


Axe Violations fixed by adding missing/wrong roles.

Summary
Fixes #945

What version of the axe plugin are you using? Is it the same version we are testing with in wdio? I am curious why these errors were not see in the tests? Should we add tests for these states to ensure the correct aria labels are used?

What version of the axe plugin are you using? Is it the same version we are testing with in wdio? I am curious why these errors were not see in the tests? Should we add tests for these states to ensure the correct aria labels are used?

I used axe core version 3.3.2 and got these violations. But I am seeing we are using v3.2.2 in the toolkit.

After discussing the implications of the changes on this PR for addressing this rule introduced in axe-core-3.3.0, we decided to hold off on these changes and disable this new rule for now in terra-toolikit. We will revisit this rule once we have a better plan on how to address it. I will close this PR after I disable the rule to ensure the violations no longer appear.

This PR is for a different axe issue in v3.4 regarding aria-roles,  not the keyboard accessibility one. If this one looks good to be merged, it can be merged, or this rule can be disabled in toolkit @benbcai .

@saket2403 Yes, this is an existing rule and we will not disable it and should be fixed before bumping to axe-core v3.4.
I found one other place that has this violation. This test also shows that the popup menu in terra-application-navigation uses an incorrect role. This is the violation.
[large] ApplicationNavigation - Large Tabs roll up properly [default] is accessible and is within the mismatch tolerance:
expected no accessibility violations but got:
	{
  "description": "Ensures elements with an ARIA role that require child roles contain them",
  "help": "Certain ARIA roles must contain particular children",
  "helpUrl": "https://dequeuniversity.com/rules/axe/3.4/aria-required-children?application=axeAPI",
  "id": "aria-required-children",
  "impact": "critical",
  "nodes": [
    {
      "all": [],
      "any": [
        {
          "data": [
            "listitem"
          ],
          "id": "aria-required-children",
          "impact": "critical",
          "message": "Required ARIA child role not present: listitem",
          "relatedNodes": []
        }
      ],
      "failureSummary": "Fix any of the following:\n  Required ARIA child role not present: listitem",
      "html": "<ul class=\"PopupMenu-module__utility-list___2rhJk\" aria-label=\"More Navigation\" role=\"list\" tabindex=\"0\">",
      "impact": "critical",
      "none": [],
      "target": [
        "ul"
      ]
    }
  ],
  "tags": [
    "cat.aria",
    "wcag2a",
    "wcag131"
  ]
}

It shows that the popmenu has a role of list and expects its children to have a role of listitem but its children's role is link.

In talking with @dkasper-was-taken he thinks the link role should be set in a div contained inside an <li> similar to the navigation side menu.

I found one other place that has this violation. This test also shows that the popup menu in terra-application-navigation uses an incorrect role.

Fixed in 95f43ac

@saket2403 The role for the children should remain link instead of changing to listitem. The content should be wrapped in a div inside an li similar to how the navigation side menu in the above screenshot.

@saket2403 The role for the children should remain link instead of changing to listitem. The content should be wrapped in a div inside an li similar to how the navigation side menu in the above screenshot.

changed in 662d37c


Current tar implementation requires begin to be run as root

The ExpandTar function untars the ACI in a chroot, which requires root permissions to set up.

ah, thanks for reminding me about this, I was intending to file an issue. I
think we should be able to just split this out and use ExtractTarChroot iff
euid == 0, and ExtractTar otherwise?
On Wed, Oct 14, 2015 at 11:12 AM, Derek Gonyeo<EMAIL_ADDRESS>wrote:

The ExpandTar function untars the ACI in a chroot, which requires root
permissions to set up.
—
Reply to this email directly or view it on GitHub
https://github.com/appc/acbuild/issues/35.

If a regular non-root user bob wants to build an ACI that contains files belonging to someone else than bob, the tar create/extract functions must be able to ignore the file ownership in the .acbuild directory, and instead acbuild must have a separate database of files' ownerships.
Basically this is what FakeRoot does but since we control the tar library from go, we don't need this kind of LD_PRELOAD trick.
The tar writer BuildWalker used by End already has a callback that can be used to change the files ownership in the tarball (added by https://github.com/appc/spec/issues/498). But for the tar reader part (extract), I don't know if rkt/pkg/tar (https://github.com/coreos/rkt/pull/1616) should grow this kind of feature or if it should be implemented directly in acbuild?

Also, ExpandTar can only extract to /: see how it is hardcoded: filepath.Join("/", hdr.Name). This is ok for rkt but does not really fit acbuild's requirements.

@alban my proposal here

@dgonyeo is this done now?

Nope, I still need to make a PR to make use of the new ExtractTarInsecure function. I'll get around to it in the near future.


Fix permalink generation on production env

Fixed in https://github.com/hirusi/smix-eleventy-starter/commit/e0b85653bd071727835f69272fce1d2d7ab33940.


chore(main): release 2.6.20

:robot: I have created a release beep boop
2.6.20 (2024-10-18)
Bug Fixes

deps: update rust crate anyhow to v1.0.90 (445a6bb)
deps: update rust crate serde_json to v1.0.129 (38f9a19)
deps: update rust crate tokio to v1.40.0 (27eafb5)
Include uniq constraint (7dce0d2)
Require a unique index for updating the name (710042f)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/philipcristiano/et/releases/tag/v2.6.20 :sunflower:


[glist/glist-h] Decompile this stupidity

Pull Request Test Coverage Report for Build 602041645

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 68.704%

Totals

Change from base Build 601589310:
0.002%

Covered Lines:
30642

Relevant Lines:
44600

💛  - Coveralls


tar: Unexpected EOF in archive with params_model_1.npz at install time

Hello,
When I try to install bindcraft with:
bash install_bindcraft.sh --cuda '12.6' --pkg_manager 'conda'

I get this error at the end:
Building wheels for collected packages: colabdesign
  Building wheel for colabdesign (setup.py) ... done
  Created wheel for colabdesign: filename=colabdesign-1.1.2-py3-none-any.whl size=49867922 sha256=1845ceb2a56d8d23dca95e14dea70f7e7aba2fdab232caf12ae76932c95c11a7
  Stored in directory: /tmp/pip-ephem-wheel-cache-dn55pkyx/wheels/17/cf/49/c29de6f205fc51717698726bf695a5f1e02c8aaeaac9ad1797
Successfully built colabdesign
Installing collected packages: colabdesign
Successfully installed colabdesign-1.1.2
--2024-10-16 09:35:41--  https://storage.googleapis.com/alphafold/alphafold_params_2022-12-06.tar
Resolving storage.googleapis.com... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to storage.googleapis.com|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length:<PHONE_NUMBER> (5.2G) [application/x-tar]
Saving to: '/home/pacho/BindCraft-1.1.0/params/alphafold_params_2022-12-06.tar.5'

alphafold_params_2022-12-06.tar.5                                      100%[==========================================================================================================================================================================>]   5.20G  10.7MB/s    in 8m 22s

2024-10-16 09:44:03 (10.6 MB/s) - '/home/pacho/BindCraft-1.1.0/params/alphafold_params_2022-12-06.tar.5' saved [5587968000/5587968000]

params_model_1.npz
tar: Unexpected EOF in archive
tar: rmtlseek not stopped at a record boundary
tar: Error is not recoverable: exiting now
BindCraft environment installed
Cleaning up conda temporary files to save space
Will remove 41 (44.3 MB) tarball(s).
Will remove 1 index cache(s).
Will remove 41 (145.0 MB) package(s).
There are no tempfile(s) to remove.
There are no logfile(s) to remove.
conda cleaned up
Finished setting up BindCraft environment
Activate environment using command: "conda activate BindCraft"
Installation took 0 hours, 9 minutes and 40 seconds.(base)

I am also unsure if it could be related with #48
Thanks a lot

Can you try to download the alphafold parameters separately?
wget -P ${install_dir}/params/ https://storage.googleapis.com/alphafold/alphafold_params_2022-12-06.tar
tar -xvf ${install_dir}/params/alphafold_params_2022-12-06.tar

Ah, I see what happened:
It seems that there was an issue the first time it tried to download it. When I retried to re-run the installer, wget downloaded the new copy appending the .1 suffix but, as tar xvf is hardcoded in the installer, it was trying to unpack the bogus tarball.
The problem is that it seems that there is no easy way to force wget to overwrite the previous downloaded copy. Options look to be to:

Use "-O" option and specify a filename. That could be interesting as that "unchangeable" filename could be reused when executing tar.
--backups=0 looks to be able to achieve a similar result...

Best regards


Automattic hosting compatibility

I was just about to write a plugin like this to use on Automattic's VIP hosting service, but yours does most of what I wanted already. I've forked it and I'd like to modify it so it passes VIP coding requirements. Mostly it's escaping, spacing, explicit conditionals, stuff like that. Please let me know if you have any concerns with this.
Thanks,
Charles

For context, this is related to the VIP Coding Standards, most of which are checked by the VIP Coding Standards PHPCS ruleset.

There are actually very few issues:
PHP CODE SNIFFER REPORT SUMMARY
--------------------------------------------------------------------------------------------------
FILE                                                                              ERRORS  WARNINGS
--------------------------------------------------------------------------------------------------
/home/philipjohn/feature-flags/feature-flags/feature-flags.php                    2       3
/home/philipjohn/feature-flags/feature-flags/assets/css/feature-flags.css         0       1
/home/philipjohn/feature-flags/feature-flags/assets/js/feature-flags.js           0       1
/home/philipjohn/feature-flags/feature-flags/includes/admin/settings-page.php     2       0
/home/philipjohn/feature-flags/src/js/feature-flags.js                            2       1
--------------------------------------------------------------------------------------------------
A TOTAL OF 6 ERRORS AND 6 WARNINGS WERE FOUND IN 5 FILES
--------------------------------------------------------------------------------------------------

Time: 192ms; Memory: 8Mb

Hi @cmjaimet & @philipjohn. I'll work to fix the standards issues highlighted ASAP to get this working on WordPress VIP.

Code should now conform to the VIP standards. Haven't been able to find much useful documentation on the *_user_attribute() vs *_user_meta() differences between standalone and VIP WordPress so any guidance you have would be appreciated.
I've written a wrapper but I'm not sure if it is suitable. See class-featureflags.php#L240-L281.

Cool, thanks James. I've made a whole lot of changes that may have more to do with my needs than yours but I'll share them with you shortly. One of the main ones is moving from user meta to options. My need is to create a beta flag that affects the experience for regular users, so I can deploy new features but ave them turned off by default.

https://github.com/cmjaimet/beta-flags
Still needs unit testing but it's done other than that.


Linux file format not recognized.

I got an ELF that I want to debug and RenderDoc can't open it, it says "file format not supported".
I tried renaming the executable from untitled to untitled.bin but it makes not difference.

Hi there, your issue has been closed due to not correctly following the issue template. Please read the documentation about filing issues and open a new issue which does follow the issue template. Do not reply to this issue with more information or with a correctly formatted issue, as that will only lead to confusion.
I try to address all github issues and fix bugs quickly, but badly formatted issues or poorly described bug reports especially are a significant drain on project resources. Taking a few minutes to file a good issue makes a huge difference and will get it addressed faster - everybody wins!
In github when you first create a new issue the form is pre-populated with a template which you should read over and follow. As linked above there is documentation going into more detail about what makes a good issue.


Update Go to 1.21.3, direct Go dependencies, and alpine image in the KubeOne image

What this PR does / why we need it:

Update Go to 1.21.3
Update direct Go dependencies
Update alpine in the KubeOne image

What type of PR is this?
/kind cleanup
Does this PR introduce a user-facing change? Then add your Release Note here:
KubeOne is now built with Go 1.21.3

Documentation:
NONE

/assign @kron4eg @ahmedwaleedmalik

/lgtm
/approve


Install - hello world test failed

OS X 10.10.3.  First install and test resulted in the following screen;

No further information.  All I was trying to do was the simple hello world test as my first test.

If you open a Docker CLI (button in bottom left of Kitematic) and type docker pull kitematic/hello-world-nginx what does it show?
  I have repeated the same error and correction by manual pull with a different repostitory

I see. Thanks. Are you logged into Docker Hub via Kitematic?

I might not be, I had a problem when logging in initially and might have skipped that step.  Let me restart the app and try again to see if logging in fixes it.

@mfkilgore I don't think it will make a big difference. Interesting. It must be a bug in the downloading code. I'll take a look now.
Thanks for all the help

@mfkilgore one more question - if you reproduce the error and then open the logs (cmd+alt+i) are there any errors in the console?

Not sure if this is what you are looking for command cmd+alt+i opens the dev tools  and the console has - <IP_ADDRESS>
/Applications/Kitematic (Beta).app/Contents/Resources/app/node_modules/react/lib/warning.js:48 Warning: Any use of a keyed object should be wrapped in React.addons.createFragment(object) before being passed as a child.
I did not see a way to open the logs

That's what I was looking for - though there's no obvious error there. Thanks @mfkilgore . I'm diving into the code.

I'm running into the same 404 error when creating the hello-world-nginx container and tried running the docker pull command but I'm getting the following:
bash-3.2$ docker pull kitematic/hello-world-nginx
Pulling repository kitematic/hello-world-nginx
FATA[0000] Get https://index.docker.io/v1/repositories/kitematic/hello-world-nginx/images: dial tcp: lookup index.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:53: connection refused

@specialbrand can you follow that link:
https://index.docker.io/v1/repositories/kitematic/hello-world-nginx/images
And show us what you see?

 Do you have a proxy? It looks like the ip mapping was previously different and now resolves properly - Try perhaps the image install again?

No proxy. I just updated the app and now I can see the message from within the app.

Duplciate of #718 with instructions on how to fix it there

That worked for me. Thank you!

Great to hear. Thanks!


BibTeX Entries without Trailing Commas

The BibTeX standard does not explicitly require the last entry to end with a comma. Moreover, example from Wikipedia and automatically generated BibTeX from Google Scholar do not include a comma at the end of the last entry.
While bibtex-js-parser currently handles entries without trailing commas correctly and produces the expected output, it also prints a warning in the console for such cases.
Take the example in the README, if we remove the comma at the end of the last entry, it would be:
@inproceedings{ding_dagbase_2020,
	title = {Dagbase: a decentralized database platform {Using} {DAG}-based consensus},
	copyright = {All rights reserved},
	isbn = {1-72817-303-5},
	booktitle = {2020 {IEEE} 44th {Annual} {Computers}, {Software}, and {Applications} {Conference} ({COMPSAC})},
	publisher = {IEEE},
	author = {Ding, Yepeng and Sato, Hiroyuki},
	year = {2020},
	pages = {798--807}
}

@article{ding_formalism-driven_2022,
	title = {Formalism-{Driven} {Development}: {Concepts}, {Taxonomy}, and {Practice}},
	volume = {12},
	copyright = {All rights reserved},
	issn = {2076-3417},
	url = {https://www.mdpi.com/2076-3417/12/7/3415},
	doi = {10.3390/app12073415},
	number = {7},
	journal = {Applied Sciences},
	author = {Ding, Yepeng and Sato, Hiroyuki},
	year = {2022}
}

This would cause two warnings:
line 10:0 missing ',' at '}'
line 23:0 missing ',' at '}'

I suggest changing the program's behavior to make it more tolerant of entries without trailing commas, eliminating the warning from the console output. This adjustment would align the program with common BibTeX practices and user expectations.
In addition, the warning printed to the console does not indicate that it is from bibtex-js-parser. It would be more helpful for users to debug if the warning message can indicate its source (for example, print bibtex-js-parser: line 10:0 missing ',' at '}'). I spent a lot of time looking for where the warning comes from.

Thank you for reporting this issue.
The recent patch (0417cae) of the grammar project has addressed it.
I have also scheduled the update for both JS and Java parsers. Your patience would be appreciated.


Add an auto-fix or auto-correct feature

Is your feature request related to a problem? Please describe.
It's nice that Bandit flags lines of code that require attention, but it would be even more valuable to suggest fixes for problem lines.  Other linters such as ESLint provide a --fix command line option to automatically fix problems it finds.
See https://eslint.org/docs/user-guide/command-line-interface#options
Describe the solution you'd like
A start might be that Bandit includes another field in the output data called suggested fix or something.  It would include the modified line of code it found to be wrong with the proposed solution.
For example, if the yaml_load plugin found a case of yaml.load(), it would replace with yaml.load(Loader=yaml.SafeLoader).
Each plugin would need to handle fixes it could address.
Describe alternatives you've considered
n/a
Additional context
https://developer.ibm.com/node/2016/07/27/auto-fixing-formatting-your-javascript-with-eslint/

Nice idea. Would it give a generic example, or try to amend and suggest the flagged line of code from the project being scanned?

@lukehinds Yeah, I was thinking Bandit would output a new field of the suggested fix.  But it could also have a command line option to actually make the changes in the file automatically.  Similar to what ESLint offers.

I think this is a great idea.
Maybe could be added on the Issue class a new optional field.

I investigated this some. The ast includes a NodeTransformer that enables rewriting the tree. And in Python 3.9 and later, ast can do an unparse in addition to parse. So in effect, you can create a suggested fix and even automatically fix the code.
However, Python's ast is not a CST (comcrete syntax tree) and therefore doesn't include things like trailing comments. The undesirable effect is that suggested code wouldn't retain these elements.
We could look at switching Bandit to use something like libcst. But this would be a major change to the base parsing mechanism of Bandit and adds another dependency.

Here's a short example using libcst to auto-correct a problem in code, all while preserving the comments.
import libcst as cst

code = '''
from paramiko import client

class foo:
    def test(self):
        if True:
            ssh_client = client.SSHClient()
            # test test test
            ssh_client.set_missing_host_key_policy(client.AutoAddPolicy) # comment test
'''

class PolicyFix(cst.CSTTransformer):
    def leave_Call(self, original_node: cst.Call, updated_node: cst.Call) -> cst.Call:
        if (cst.ensure_type(original_node.func, cst.Attribute)
            and original_node.func.attr.value == "set_missing_host_key_policy"
            and original_node.args[0].value.attr.value == "AutoAddPolicy"
        ):
            return updated_node.with_deep_changes(
                old_node=updated_node.args[0].value,
                attr=cst.Name("RejectPolicy")
            )
        else:
            return original_node

tree = cst.parse_module(code)
new_tree = tree.visit(PolicyFix())
print(new_tree.code)


add uniformer model and ut

Signed-off-by: gexy5<EMAIL_ADDRESS>

Codecov Report

Merging #1218 (7238947) into main (d54adb6) will increase coverage by 0.06%.
The diff coverage is 71.32%.

:exclamation: Current head 7238947 differs from pull request most recent head 8a6f510. Consider uploading reports for the commit 8a6f510 to get more accurate results

@@            Coverage Diff             @@
##             main    #1218      +/-   ##
==========================================
+ Coverage   68.50%   68.57%   +0.06%
==========================================
  Files         248      249       +1
  Lines       11869    12148     +279
  Branches     1964     2007      +43
==========================================
+ Hits         8131     8330     +199
- Misses       3228     3296      +68
- Partials      510      522      +12

Impacted Files
Coverage Δ

towhee/models/uniformer/uniformer.py
71.32% <71.32%> (ø)

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 d54adb6...8a6f510. Read the comment docs.

/lgtm

/lgtm
/approve


feat: Add e2e Wallet always on Rinkeby if the context is Cypress

What it solves
This is a change from the latest approach for injecting a custom module for testing
Now when we are on Rinkeby and the execution context is Cypress the e2e module in added and we can see and choose it from the onboard popup. This open a new testing scenarios.
I updated as well the cypress command cy.configWindow (Bad naming BTW)  for cy.connnectE2EWallet() what can be used before any cy.visit() for making the web app autoconnect to the E2E Wallet provider by injecting it in the localStorage 'SAFE__lastUsedProvider'
For injecting the Mnemonic we changed the approach and now can be injected as a Cypress env variable in multiple ways (https://docs.cypress.io/guides/guides/environment-variables), the custom onboard module will read it from there. It allows for example, our Safe Apps tests to inject the tests mnemonics from our repos when doing e2e tests.
This is a new experiment so please take a look and feel free to discard it if you think does not improve anything
Screeenshots

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 9 (44.44%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.005%) to 36.932%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/logic/wallets/utils/walletList.ts
1
2
50.0%

src/logic/wallets/e2e-wallet/module.ts
3
7
42.86%

Totals

Change from base Build<PHONE_NUMBER>:
-0.005%

Covered Lines:
3894

Relevant Lines:
9575

💛  - Coveralls

Hey @katspaugh thanks for merging this yesterday. We will start using it with our own mnemonics
@francovenica if you want I can explain you the main changes here because your connected tests are going to behave different now

The only problem it throws cy.configWindow is not a function :)

ah yeah, I changed the name, will create a PR updating that now
The spec is not used in CI so no problem there. If you are going to add connected specs in CI later then you will need to add the CYPRESS_MNEMONIC env variable to the workflows probably depending on how you will approach reading it

Created PR here => https://github.com/safe-global/safe-react/pull/3941


Fix query failed when Some index file not exists(#1031)

What changes were proposed in this pull request?
Add a simple test case  to reproduce #1031  and fix it.
How was this patch tested?
Add new test suite named "OAP#1031- query failed when Some index file not exists"

@LuciferYang
Seem good.   In UT, how about  creating a case with  "create oindex index1 on parquet_test (b) partition (...)"
Thanks

@zhixingheyi-tian ok~

@zhixingheyi-tian  done


NUnit template included in cli

Summary
NUnit template is now in dotnet CLI.
Adding the package dotnet new -i NUnit3.DotNetNew.Template is no longer required since the template is pre-installed.
I also updated the version numbers and tweaked a few places the csproj names lost a period.
Contributes to https://github.com/dotnet/docs/issues/7204

Created PR for updating the project and also added tags so we can reference the csproj from here instead of having to update both places every time for package versions:
https://github.com/dotnet/samples/pull/269

Just noticed we also have VB and F# versions of the same topic. So I'll apply all changes we make to those topics once we're done with the changes to the C# one.

@mairaw That would be awesome! I was thinking of those, but wanted to make sure I had the right changes before I repeated them on the other docs. Sweet!

@mairaw Is there anything else I need to add for approval?

I've updated the date to reflect the change and I'll keep that issue open so I can mirror the same changes to the VB and F# versions.

I was going to create a separate PR for some improvements but decided it would be better to have it done here so the C# version is 100% complete. Some things bothered me as I was testing the whole topic before.

You are awesome! Thank you!

F# and Visual Basic docs to follow.


Adding new test cases to test_routes

Add some new test cases to the test_routes.py. file to increase the testing code coverage rate.

Please update the branch so that we can tell what tests you added to the code, and make sure there aren't duplicated tests.

Wrong branch name, don't use master as name.


Generate and resolve criteria

Codecov Report
Patch and project coverage have no change.

Comparison is base (70b6a25) 100.00% compared to head (ec45a01) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##               1.5     #1088    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           46        46
  Lines         2652      2414   -238
  Branches       396       354    -42
==========================================
- Hits          2652      2414   -238

Flag
Coverage Δ

foundry
?

production
100.00% <ø> (ø)

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 29 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


The default value for CleanPodPolicy is inconsistent.

In the comments of common, the default value is Running：
type RunPolicy struct {
	// CleanPodPolicy defines the policy to kill pods after the job completes.
	// Default to Running.
	CleanPodPolicy *CleanPodPolicy `json:"cleanPodPolicy,omitempty"`

In actuality：

mpiJob's default cleanpod policy is None.
mxJob's default cleanpod policy is All.
paddleJob's default cleanpod policy is None.
pytorchJob's default cleanpod policy is None.
tfJob's default cleanpod policy is Running.
XGBoostJob's default cleanpod policy is All.

Should we set all jobs default to Running, or remove the comments(// Default to Running.) in common.

Thanks for reporting this.
Yes. This has to be consistent.  I think, we can keep defaults to None IMO.
/cc @terrytangyuan @gaocegege  @tenzen-y

I agree. We should set None as default. Setting Running as default looks weird to me.

Sounds good


New package: Casey.Just version 1.13.0

- [X] Have you signed the Contributor License Agreement?

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.4 schema?

Resolves #4413

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Executable-Error


[CCXDEV-6474] Update go image version to 1.16

Description
Use RHEL image with go 1.16 version.
Fixes CCXDEV-6474.
Type of change

Bump-up dependent library (no changes in the code)

Testing steps
Checklist

[x] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #721 (1c94a01) into master (79ec7ae) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #721   +/-   ##
=======================================
  Coverage   54.09%   54.09%
=======================================
  Files          21       21
  Lines        2616     2616
=======================================
  Hits         1415     1415
  Misses       1037     1037
  Partials      164      164

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 79ec7ae...1c94a01. Read the comment docs.


pydantic error

First of all, great work.
For a while it work fine, but now I'm, sometimes, receiving an error:
Exception has occurred: ValidationError
1 validation error for Raindrop
cache -> size
ensure this value is greater than 0 (type=value_error.number.not_gt; limit_value=0)
in models.py module, while calling _search_paged in the line:
return [cls(**item) for item in results["items"]]
it doesn't happen always - that's the strange thing, and seems to be related with some cache value and with pydantic.
Any clue on how to solve this?
Regards

Thank you!
I haven't run into this but it sounds very much like it's associated with something specific to your particular collection (which is why I haven't run across it).
On first blush, not sure why the Raindrop API would be returning that something is in Cache but with a size of 0. I'm going to run this by the Raindrop developer and see if he has any ideas (his API doc is a bit "light"...).
A fix might be as simple as relaxing the pydantic type requirement on the cache size from PositiveInt to simply Int. Gimme a few days to see if anything better comes up.

I never heard back from Raindrop so I'm trying the "easy" route of simply allowing sizes of 0.
Feel free to let me know if you still run into anything around this!


Formulae not found in latest Docker image

Bug report

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Install the secrethub-cli in the Docker container linuxbrew/brew:latest.
What happened (include command output)
The formulae was not found (Error: No available formula or cask with the name "secrethub/tools/secrethub-cli".)

Command output

brew install secrethub/tools/secrethub-cli
==> Tapping secrethub/tools
Cloning into '/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/secrethub/homebrew-tools'...
remote: Enumerating objects: 55, done.
remote: Counting objects: 100% (55/55), done.
remote: Compressing objects: 100% (43/43), done.
remote: Total 182 (delta 12), reused 0 (delta 0), pack-reused 127
Receiving objects: 100% (182/182), 30.87 KiB | 1.19 MiB/s, done.
Resolving deltas: 100% (39/39), done.
Tapped 1 formula (27 files, 136.6KB).
Error: No available formula or cask with the name "secrethub/tools/secrethub-cli".
==> Searching for similarly named formulae...
This similarly named formula was found:
secrethub-cli
To install it, run:
  brew install secrethub-cli

What you expected to happen
Successful installation of the CLI, just like when using the linuxbrew/brew:2.5.2 image.
Step-by-step reproduction instructions (by running brew commands)
docker run linuxbrew/brew brew install secrethub/tools/secrethub-cli

Output of brew config and brew doctor commands

# brew doctor
Your system is ready to brew.

# brew config
HOMEBREW_VERSION: 2.5.2-69-g2331927
ORIGIN: https://github.com/Homebrew/brew
HEAD: 2331927a3498e1107aef13f76f1ed2b8309be4b0
Last commit: 5 hours ago
Core tap ORIGIN: https://github.com/Homebrew/linuxbrew-core
Core tap HEAD: ebc6339d1832683cb3d9e14ae0f7e2b049102299
Core tap last commit: 5 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /home/linuxbrew/.linuxbrew
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.3 => /home/linuxbrew/.linuxbrew/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: octa-core 64-bit skylake
Clang: N/A
Git: 2.28.0 => /bin/git
Curl: 7.68.0 => /usr/bin/curl
Kernel: Linux 5.4.0-48-generic x86_64 GNU/Linux
OS: Ubuntu 20.04.1 LTS (focal)
Host glibc: 2.31
/usr/bin/gcc: 9.3.0
/usr/bin/ruby: N/A
glibc: N/A
gcc: N/A
xorg: N/A

brew doctor resolves the problem. Are we supposed to run brew doctor every time we start using the docker image?

This isn't limited to the SecretHub tap. I'm seeing a similar error for `heroku/brew/heroku`

docker run linuxbrew/brew brew install heroku/brew/heroku
==> Homebrew has enabled anonymous aggregate formula and cask analytics.
Read the analytics documentation (and how to opt-out) here:
  https://docs.brew.sh/Analytics
No analytics have been recorded yet (or will be during this `brew` run).
==> Homebrew is run entirely by unpaid volunteers. Please consider donating:
https://github.com/Homebrew/brew#donations
==> Tapping heroku/brew
Cloning into '/home/linuxbrew/.linuxbrew/Homebrew/Library/Taps/heroku/homebrew-brew'...
Tapped 2 formulae (30 files, 368KB).
Error: No available formula or cask with the name "heroku/brew/heroku".
==> Searching for similarly named formulae...
This similarly named formula was found:
heroku
To install it, run:
brew install heroku

brew doctor resolves the problem. Should we run brew doctor every time we start using the docker image?

Can you elaborate how it seems to fix the problem?

@MikeMcQuaid I cannot seem to reproduce. I must have overlooked something when I reported it did solve the problem, sorry.
So the problem still persists after running brew doctor.

Docker is a red herring. Merely running:
brew untap secrethub/tools
HOMEBREW_NO_ANALYTICS=1 brew install --only-dependencies secrethub/tools/secrethub-cli

is enough to observe the error.

 Library/Homebrew/cask/cmd/abstract_command.rb |   1 +
 Library/Homebrew/cask/cmd/install.rb          |  29 +++-
 Library/Homebrew/cask/cmd/reinstall.rb        |   6 +-
 Library/Homebrew/cli/named_args.rb            |  63 ++++---
 Library/Homebrew/cmd/install.rb               | 227 +++++++++++++++++---------
 Library/Homebrew/exceptions.rb                |  16 +-
 docs/Manpage.md                               |  20 ++-
 manpages/brew.1                               |  40 ++++-
 8 files changed, 285 insertions(+), 117 deletions(-)


[FEATURE] orbital on explosion boost

Feature
the KB uses an explosion to launch coins, thus other explosion (even ones made by enemies) should allow for orbital striking.
Usage
useful in the Cyber Grind and any level where orbital strikes are possible.
Extras
not much else. just making the orbital strike work from explosions.
https://github.com/eternalUnion/UltraPain/assets/112786974/8579468b-a25a-49e7-ac29-d8f0ebfbfcfd

it is possible. Only reason I limited it to kb is it is easy to throw coins high. I may need to add a distance limiter to avoid short range orbitals with coins that did not go that high

you could also make it so damage scales with velocity. making KB the most consistent version.

basically. more distance (after a threshold) = more damage
maybe this:
Y=damage X=distance Z=multiplier W=base damage
well use the marksmen default for this.
so
Y=1(W)*(2(Z)*X)
i think i got that equation right. please tell me if i did.

https://github.com/eternalUnion/UltraPain/releases/tag/fr33-1.0.2-0

i have played it and it is really fun and balanced.


Minor update to Struts 2.5.x build configuration, SecurityMemberAccess.

Minor update to Struts 2.5.x build configuration, SecurityMemberAccess.
pom.xml changes:

updated maven-surefire-plugin 2.20.1-> 2.22.1

code changes:

updated SecurityMemberAccess for compatibility with future OGNL 3.1.19+ versions
updated SecurityMemberAccess constructor (minor cleanup and comment)

Hello.
Although this PR should permit usage of OGNL 3.1.19+, it may be prudent to stick with 3.1.18 for the Struts 2.5.19 build.  There are enough changes between 3.1.15-to-3.1.18 to absorb, and the behaviour changes in 3.1.19 may need some deeper consideration before including in a future Struts build.

Coverage decreased (-0.03%) to 46.941% when pulling 2d97ac605f7a9ebe71fe4140ef5e2a778637e07c on JCgH4164838Gh792C124B5:localS2_2_5_x_Branch into 06e5dfc2ab550987abb79e4eb76c8c77151a1e78 on apache:struts-2-5-x.

Coverage decreased (-0.03%) to 46.941% when pulling 2d97ac605f7a9ebe71fe4140ef5e2a778637e07c on JCgH4164838Gh792C124B5:localS2_2_5_x_Branch into 06e5dfc2ab550987abb79e4eb76c8c77151a1e78 on apache:struts-2-5-x.

I personally think those null checks and throwing exceptions may aren't essential because they decrease our test coverage percent and also they're for Struts internal usages so almost always aren't null. I also had an improvement at 459b3f7023176a516b8cec26daa47c4b1902ebed which you may like to see and import :) Thanks!

Hello @yasserzamani .
I've taken a quick look at the changes you made with https://github.com/apache/struts/commit/459b3f7023176a516b8cec26daa47c4b1902ebed for WW-4973 ( resolved for Struts 2.6).  They look good but are more sophisticated/involved than I was thinking of for this PR.   :)
So I attempt to remove the null checks/explicit exception throws you pointed out and try pushing that up for further review (should resolve the code coverage issue).
Let me know what you think of the revised changes (hopefully "good enough" for future OGNL 3.1.x in 2.5.x, without too many other changes).

After attempting to amend/rebase my change locally I encountered some Git behaviour such that I'm not trusting pushing back to my remote fork.
So ... I will instead close this PR, re-do my (now single file) change in a new branch and create a new PR.

I use it all the time with an alias as git please.
see https://medium.freecodecamp.org/git-please-a182f28efeb5

Thank you very much for the advice, @lukaszlenart  and @sepe81 .  Next time I'll be less worried about the state of my remote working branch.  :)
I have added the git alias (thanks to the instructions from the link above), and hopefully I'll remember I have it now.  ;-)


Feat: Skip Tags + Releases

This will let us skip releases with the NONE keyword (no tags, no release) for small things like README tweaks or pipeline changes.
NONE

This will let us skip releases with the NONE keyword (no tags, no release) for small things like README tweaks or pipeline changes. The NONE keyword will do this.


EC2 - Cross region VPC peering bug

Bug where Python would throw an UnboundLocalError in the get_cross_vpc-method if no vpc was found in that region.
There was a test for this usecase, test_vpc_peering_connections_cross_region_fail. This test fails when running it on it's own, but would pass when running the entire EC2-test suite. That's why it was never discovered.
Solution
When a (cross-region) VPC is not found, it should throw a VpcNotFound error.
The new solution simplifies this approach  - it tries to find the VPC in the other region, and the get_vpc-method throws the error if the VPC does not exist.
The test now passes when running on it's own, as well as when running the entire suite.

Codecov Report

Merging #4764 (c04fcc0) into master (f3313be) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #4764      +/-   ##
==========================================
- Coverage   95.38%   95.38%   -0.01%
==========================================
  Files         575      575
  Lines       61464    61461       -3
==========================================
- Hits        58629    58625       -4
- Misses       2835     2836       +1

Flag
Coverage Δ

servertests
47.36% <0.00%> (-0.01%)
:arrow_down:

test_responses
33.01% <0.00%> (-0.01%)
:arrow_down:

unittests
95.27% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/ec2/models.py
94.92% <ø> (-0.02%)
:arrow_down:

moto/ec2/responses/vpc_peering_connections.py
100.00% <100.00%> (ø)

moto/awslambda/models.py
92.85% <0.00%> (-0.12%)
:arrow_down:

moto/awslambda/responses.py
91.61% <0.00%> (+0.17%)
: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 f3313be...c04fcc0. Read the comment docs.


Failed to fetch existing assets

I'm trying to push my build artifacts back into my Gitea 1.4.2 instance using the following configuration:
  release:
    image: plugins/gitea-release
    base_url: https://example.com
    secrets: [ gitea_token ]
    files:
      - target/x86_64-unknown-linux-musl/drone-test
    checksum:
      - md5
      - sha1
      - sha256
      - sha512
    when:
      event: tag

The new release is created, but before uploading the new assets, the plugin fails when trying to fetch the existing assets:
Failed to upload the files. Failed to fetch existing assets: 404 Not Found
Did the Gitea API change?

Sadly not but I didn't have any time to investigate further, yet.

I encountered the same problem, has anyone found a solution yet?

@JonasFranzDEV can you check that?

only master or 1.5 version of gitea is supported.

Gitea 1.5 isn't released yet. Wouldn't it be better to support the current stable version?

That's not possible since 1.5 is the first version which supports the attachment api. So you have to wait for 1.5 or use master branch.

Ah ok. I didn't know that. I gues I'll have to wait until the docker image gets updated to 1.5.
Maybe this fact should be documented in the README.

'aight I see, I guess this is not an issue then, though I agree that it should be noted somewhere, that those api features are not available in the current release versions of gitea,
thanks for clarification.

I think so yeah, thank you.

YW


Add Windows MSI build for PRs just to see how it works

This build includes a jlink-produced image of Java 16.

It works, though the generated MSI is for unattended installation. Given the hassle of mandatory signing, I'm inclined to ditch MSI and just use ZIP archives with bundled Javan runtime.


Update API doc

Updated cURL requests in the API documentation

Can one of the admins verify this patch?


Improve Dolby Digital Playback

Amazon Fire TV devices have to be difficult... they have their own unique ways of playing back content on various amazon fire tv versions.   This is outline here, but in general we may have to incorporate their version of ExoPlayer for the Amazon builds.
https://developer.amazon.com/docs/fire-tv/dolby-integration-guidelines.html#exoplayer
This will require an Amazon Flavor of the application going forward to handle these device specific issues.

Testing this currently and Dolby Digital seems to be working on Amazon Fire TV with the latest version of ExoPlayer.


EIP To - Should have pattern property

You cannot configure the pattern (Message Exchange Pattern) that is an enum
@XmlAttribute
@Metadata(label = "advanced", javaType = "org.apache.camel.ExchangePattern", enums = "InOnly,InOut")
private String pattern;

"pattern": { "kind": "attribute", "displayName": "Pattern", "label": "advanced", "required": false, "type": "enum", "javaType": "org.apache.camel.ExchangePattern", "enum": [ "InOnly", "InOut" ], "deprecated": false, "autowired": false, "secret": false, "description": "Sets the optional ExchangePattern used to invoke this endpoint" },

I can only see Disabled in the advanced properties.


Introduce a mechnism for caching ACL check results for a session for chunked WriteRequest

Problem
ACL check is conducted on every AttributeDataIB for a write request, we should only check for first chunk only so we can send a enpty list at the beginning of the chunked list.
Proposed Solution
My idea:

Add a access check "token" to WriteHandle, including a path and a flag (pass / fail)
WriteSingleClusterData can accept that token, if the path match and the ACL check is pass, it will skip the check and grant access.

CC: @mlepage-google @bzbarsky-apple

Fixed in #13641 together.


[BACKLOG-25823] Upgrade to ElasticSearch 6.4.2

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/elasticsearch-bulk-insert/assemblies/plugin/assembly/assembly.xml
  plugins/elasticsearch-bulk-insert/core/pom.xml
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulk.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java
  plugins/elasticsearch-bulk-insert/core/src/test/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.3% (click to expand)
org.pentaho.di.trans.steps.elasticsearchbulk.ElasticSearchBulkMeta.Server

Complexity Change: -16.7% :small_red_triangle_down:
Line Change: -16.7% :small_red_triangle_down:
Method Change: -16.7% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulk.java

:heavy_exclamation_mark: 'lambda arguments' has incorrect indentation level 12, expected level should be 6. at Line: 476

/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 62 Column: 7

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 66 Column: 111

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 67 Column: 21

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 67 Column: 72

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 121 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 121 Column: 33

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 123 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 123 Column: 33

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 125 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 125 Column: 33

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 127 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 127 Column: 33

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 130 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 130 Column: 31

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 132 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 132 Column: 41

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 134 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 134 Column: 38

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 136 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 136 Column: 33

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 138 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 138 Column: 36

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 141 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 141 Column: 33

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 143 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 143 Column: 36

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 145 Column: 14

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 145 Column: 35

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 148 Column: 18

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 148 Column: 35

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 150 Column: 18

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 150 Column: 34

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 152 Column: 18

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 152 Column: 36

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 603 Column: 22

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 603 Column: 111

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 605 Column: 22

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 605 Column: 112

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 609 Column: 23

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 609 Column: 114

:heavy_exclamation_mark: '(' should be on the previous line. at Line: 657 Column: 15

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 782 Column: 16

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 782 Column: 32

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 784 Column: 16

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 784 Column: 29

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 798 Column: 16

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 798 Column: 29

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 800 Column: 16

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 800 Column: 36

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 805 Column: 16

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 805 Column: 29

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 807 Column: 16

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 807 Column: 30

/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java

:heavy_exclamation_mark: '+' should be on a new line. at Line: 338 Column: 116

:heavy_exclamation_mark: '+' should be on a new line. at Line: 345 Column: 115

:heavy_exclamation_mark: '+' should be on a new line. at Line: 546 Column: 116

:heavy_exclamation_mark: 'array initialization' child has incorrect indentation level 20, expected level should be one of the following: 14, 26, 27. at Line: 686

:heavy_exclamation_mark: 'lambda arguments' has incorrect indentation level 14, expected level should be 8. at Line: 906

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/elasticsearch-bulk-insert/assemblies/plugin/assembly/assembly.xml
  plugins/elasticsearch-bulk-insert/core/pom.xml
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulk.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java
  plugins/elasticsearch-bulk-insert/core/src/test/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.3% (click to expand)
org.pentaho.di.trans.steps.elasticsearchbulk.ElasticSearchBulkMeta.Server

Complexity Change: -16.7% :small_red_triangle_down:
Line Change: -16.7% :small_red_triangle_down:
Method Change: -16.7% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 603 Column: 22

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 603 Column: 111

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 605 Column: 22

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 605 Column: 112

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 609 Column: 23

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 609 Column: 114

:heavy_exclamation_mark: '(' should be on the previous line. at Line: 657 Column: 15

/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java

:heavy_exclamation_mark: 'array initialization' child has incorrect indentation level 12, expected level should be one of the following: 6, 47, 48. at Line: 683

:heavy_exclamation_mark: 'array initialization' child has incorrect indentation level 12, expected level should be one of the following: 6, 47, 48. at Line: 684

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/elasticsearch-bulk-insert/assemblies/plugin/assembly/assembly.xml
  plugins/elasticsearch-bulk-insert/core/pom.xml
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulk.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java
  plugins/elasticsearch-bulk-insert/core/src/test/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.3% (click to expand)
org.pentaho.di.trans.steps.elasticsearchbulk.ElasticSearchBulkMeta.Server

Complexity Change: -16.7% :small_red_triangle_down:
Line Change: -16.7% :small_red_triangle_down:
Method Change: -16.7% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 603 Column: 22

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 603 Column: 111

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 605 Column: 22

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 605 Column: 112

:heavy_exclamation_mark: '(' is not followed by whitespace. at Line: 609 Column: 23

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 609 Column: 114

:heavy_exclamation_mark: '(' should be on the previous line. at Line: 657 Column: 15

/home/buildguy/project/plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java

:heavy_exclamation_mark: 'array initialization' child has incorrect indentation level 12, expected level should be one of the following: 6, 47, 48. at Line: 683

:heavy_exclamation_mark: 'array initialization' child has incorrect indentation level 12, expected level should be one of the following: 6, 47, 48. at Line: 684

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/elasticsearch-bulk-insert/assemblies/plugin/assembly/assembly.xml
  plugins/elasticsearch-bulk-insert/core/pom.xml
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulk.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java
  plugins/elasticsearch-bulk-insert/core/src/test/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.3% (click to expand)
org.pentaho.di.trans.steps.elasticsearchbulk.ElasticSearchBulkMeta.Server

Complexity Change: -16.7% :small_red_triangle_down:
Line Change: -16.7% :small_red_triangle_down:
Method Change: -16.7% :small_red_triangle_down:

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'plugins/elasticsearch-bulk-insert/core' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  plugins/elasticsearch-bulk-insert/assemblies/plugin/assembly/assembly.xml
  plugins/elasticsearch-bulk-insert/core/pom.xml
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulk.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMeta.java
  plugins/elasticsearch-bulk-insert/core/src/main/java/org/pentaho/di/ui/trans/steps/elasticsearchbulk/ElasticSearchBulkDialog.java
  plugins/elasticsearch-bulk-insert/core/src/test/java/org/pentaho/di/trans/steps/elasticsearchbulk/ElasticSearchBulkMetaTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.3% (click to expand)
org.pentaho.di.trans.steps.elasticsearchbulk.ElasticSearchBulkMeta.Server

Complexity Change: -16.7% :small_red_triangle_down:
Line Change: -16.7% :small_red_triangle_down:
Method Change: -16.7% :small_red_triangle_down:

@pentaho/r2d2


Tab name falls back to just the filename after dragging tab

Filenames render fine normally (parent folder is displayed, ellipsis etc.). But when I drag a tab to another place in the tab bar, the name returns to just the filename (and it stays that way).
Atom: 1.0.11
Smart-tab-name: 1.0.3
Theme: One Dark
Syntax theme: Base16 Tomorrow Dark

There I made a pull request to fix this, it seems moving tabs re-rendered the panel, so I just added a subscription to that event to re-process them.

Thanks!


feat(shuttle-poise): Add support for Poise 0.6

Description of change

Adds poise and poise-0-6 feature flags, with poise enabled by default
Note similar to shuttle-serenity added to readme

How has this been tested? (if applicable)

cargo clippy
cargo clippy --no-default-features -F poise-0-6

Thanks for the PR! :D
I think it'll soon be time for switching the serenity plugin to use 0.12 by default (a PR that you can do if you want to), so I think having this released at the same time with 0.6 as the default feature will be good.

Sounds great, all that's needed for that is changing the defaults? So:
default = ["poise"] -> default = ["poise-0-6"]
default = ["rustls_backend"] -> default = ["serenity-0-12-rustls_backend"]

Rather with a new feature for the older version, and no feature for the current one. See the shuttle-axum crate.

Since the changes are so closely related, I don't mind having both changes in one PR. Either way works.

@supleed2 You can restore shuttle-poise to its state before this PR, change the requirement on shuttle-runtime to <=0.40.0, add a #[deprecated = "..." ] on the PoiseService. The readme and the deprecation message can have a link to the latest docs.rs/shuttle-serenity.
Then there is also an opportunity to update the examples to use the newer versions of serenity and poise. :wink:


When should I fork?

So I am confused about forking and creating pull requests. I forked DS a while back to make some code updates. I've done some pull requests with no issues. When I want to create a new pull request today should I fork again or does my fork get updated with Git desktop?

You can merge changes from DotSpatial into your fork. This brings your fork's master branch into sync with the upstream repository, without losing your local changes.
See https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork

oic. i will try that.

If I sync my fork with the main branch will I lose all the pull requests that are in the queue that have not yet been approved?

They're not lost. They are simply from older commits on your fork. You may feel you also want to update your branches & the PRs if there are conflicting changes. Github usually points out any conflicts on the PR page.

I did several and the PR page said the Changes document was problematic. I tried to fix it to no avail. So I deleted my PRs and now am just waiting to figure out how to fix them.


diff:ignoreChildren does not Ignore Children of a Button

Describe the bug
Using diff:ignoreChildren does not ignore child elements or text of a button
Example:
<button id="buttonid" class="somecss">
    Not Ignored Span
</button>

Or
<button id="buttonid" class="somecss">
    Not Ignored
</button>

With this test:
[Fact]
public void GivenComponent_MatchMarkup()
{
    var cut = RenderComponent<Test>();
    var expectedHtml = @$"<button diff:ignoreAttributes diff:ignoreChildren></button>";

    cut.MarkupMatches(expectedHtml);
}

Results in this output:
BlazorApp1Tests.ComponentTests.GivenComponent_MatchMarkup [229 ms]
  Error Message:
   Bunit.HtmlEqualException : HTML comparison failed.

The following errors were found:
  1: The text at button(0) > #text(0) was not expected.

Actual HTML:
<button id="buttonid" class="somecss">
  Not Ignored Span
</button>

Expected HTML:
<button diff:ignoreattributes="" diff:ignorechildren=""></button>

  Stack Trace:
   at Bunit.MarkupMatchesAssertExtensions.MarkupMatches(INodeList actual, INodeList expected, String userMessage) in /_/src/bunit.web/Asserting/MarkupMatchesAssertExtensions.cs:line 238
   at Bunit.MarkupMatchesAssertExtensions.MarkupMatches(IRenderedFragment actual, String expected, String userMessage) in /_/src/bunit.web/Asserting/MarkupMatchesAssertExtensions.cs:line 114
   at BlazorApp1Tests.ComponentTests.GivenComponent_MatchMarkup() in C:\Code\Projects\BlazorApp1\BlazorApp1Tests\UnitTest1.cs:line 14
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Void** arguments, Signature sig, Boolean isConstructor)
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)

Expected behavior:
The test would succeed.
Version info:

bUnit version: 1.28.9
.NET Runtime and Blazor version: .NET 8
OS type and version: Windows 11

Additional context:
This should work according to the documentation here, and in general it has worked correctly.
The only way I have found to get the test to succeed is to change the button expected HTML to the following
<button diff:ignoreAttributes></button>

Thanks for reporting this @japhelps. I am very busy right now, but will take a look as soon as possible. This may also be an issue that should be addressed over in the anglesharp-diffing repository. I would start looking there and see if this issue also exists in the diffing library. If it does, then the fix needs to be applied there.

Thanks for a very useful library and for your talks guiding how to test Blazor.
I'm also seeing this bug.
Fails:
var cut = Render( @<MudButton/> );
cut.Find("button").MarkupMatches(@<button diff:ignoreAttributes diff:ignoreChildren></button>);

Passes:
cut.Find("button").MarkupMatches(@<button diff:ignoreAttributes diff:ignoreChildren></button>);

@nref isn't those two assertions identical?

@egil My mistake, I pasted the wrong thing. I've just now updated it. That is the code that I am using to make my test pass. But the design of the test really doesn't care that there is a span or not.

@egil It can be closed. I've verified it isworking too.

I believe this is an AngleSharp bug.  I have submitted at  AngleSharp/AngleSharp.Diffing#43, because the following test fails using just AngleSharp.
public class AngleSharpTests
{
    private readonly ITestOutputHelper output;

    public AngleSharpTests(ITestOutputHelper output)
    {
        this.output = output;
    }

    [Theory]
    [InlineData(@"<button id=""buttonid"" class=""somecss"">Not Ignored</button>")]
    [InlineData(@"<button id=""buttonid"" class=""somecss"">Not Ignored</button>")]
    public void GivenButton_MarkupMatches(string actual)
    {
        var control = @"<button diff:ignoreAttributes diff:ignoreChildren></button>";

        var diffs = DiffBuilder.Compare(control)
            .WithTest(actual)
            .Build();

        foreach (var diff in diffs)
            output.WriteLine(diff.ToString());

        Assert.False(diffs.Any());
    }
}

Thanks for reporting the issue over at AngleSharp. I will close the issue for now.


CAISO Fix Forecast Time and Rename to Publish Time

Fixes the publish time for CAISO load_forecast and solar_and_wind_forecast_dam

Screenshot of the publish times in OASIS. (You can't link directly to this).


Warehouse did not detect new image automatically (without manual refresh)

Description
I had a new image in my container registry sitting there for 5 hours. But Kargo did not detect the new image automatically. It took a manual refresh before it showed up. See attached video where I had pushed a v0.0.35 image 5 hours ago, went to check kargo UI to look for it, but it did not show up until I clicked refresh on the warehouse.
Screenshots
https://github.com/akuity/kargo/assets/12677113/68adbd0e-5df0-41b3-9cc1-2944e8e2f2d7
Steps to Reproduce
Push a new image to a monitored registry. Wait N minutes (or however long we expect it to resync).
Version
Main as of today (d342b0d9bffc8acc53334fe47d82ff32e916b176).
Logs
Paste any relevant application logs here.

I feel as if I have recently seen even manual refresh fail to detect a new image, but I not entirely certain.
@jessesuen if you see this happen again, would you mind looking at logs to see if the warehouse is reconciling periodically when left to its own devices?
It's a debug level message. (idk if you have debug enabled in the kargo.demo.akuity.io instance or not.)

I feel as if I have recently seen even manual refresh fail to detect a new image, but I am not entirely certain.

Manual refreshes always work for me. It indicates the time-based reconciliations are not happening.

@jessesuen do you still see this happening? If so, was there anything revealing in the debug logs?


Reducer - All standard library functions should be available as lambda functions so that they can be passed to map/reduce directy

Currently one has to wrap them in a lamda function to work around.
This will be solved when the module API to get rid of switch statements are ready

Sounds good. Feel free to prioritize as you see fit.

New interpreter solves...

Let's keep issues like this one open until the #1119 is merged? It might take a few more days still.

Reassigned to me.

Solved in 0.5.


add: Geekverma

Description
Added my bio, social handles, and my projects
Related Issues
[Include any related issues or pull requests that this PR addresses or is related to. Use GitHub's shorthand syntax to link to them, like #1234.]
Changes Proposed
added Geekverma.json file in public\data and include that file name in src\ProfileList.json
Checklist

[ ] I have read and followed the Contribution Guidelines.
[ ] All new and existing tests passed.
[ ] I have updated the documentation to reflect the changes I've made.
[ ] My code follows the code style of this project.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@Geekverma Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and Star the repo to help us grow even further!
Sorry for the late response, was busy.


Backport "[lldb] Don't emit artificial constructor declarations as global functions"

Summary:
When we have a artificial constructor DIE, we currently create from that a global function with the name of that class.
That ends up causing a bunch of funny errors such as "must use 'struct' tag to refer to type 'Foo' in this scope" when
doing Foo f. Also causes that constructing a class via Foo() actually just calls that global function.
The fix is that when we have an artificial method decl, we always treat it as handled even if we don't create a CXXMethodDecl
for it (which we never do for artificial methods at the moment).
Fixes rdar://55757491 and probably some other radars.
Reviewers: aprantl, vsk, shafik
Reviewed By: aprantl
Subscribers: jingham, shafik, labath, JDevlieghere, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D68130
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@375151 91177308-0d34-0410-b5e6-96231b3b80d8

@swift-ci test


Internal_hostname or identity_server_service_url is not honored in resending account confirmation email flow

Describe the issue:
With the introduction of Internal_hostname configuration in IS 5.11, it's expected to use the hostname configured in Internal_hostname for every internal communication (ref: #11878). Further, if identity_server_service_url is configured, this should be prioritized and the request should be made to the hostname configured in identity_server_service_url. Neither of these configurations is honored in resending the account confirmation email flow.
How to reproduce:

Configure a separate internal_hostname other than the hostname.
Check the hostname used for the backend API requests made by the authentication endpoint in resending account confirmation email flow.
Configure a separate identity_server_service_url other than the hostname configured for hostname.[identity.auth_framework.endpoint]
identity_server_service_url = "https://test.com:9443"

Check the hostname used for the backend API requests made by the authentication endpoint in resending account confirmation email flow.

Expected behavior:

In the 2nd step above, the request is made to the hostname configured for hostname and it's expected to make the request to internal_hostname.
In the 4th step above, the request is made to the hostname configured for hostname and it's expected to make the request to identity_server_service_url.

Workaround
Add the configuration below to configure the hostname to be used in the above flow.
[identity.auth_framework]
identity_server_origin = "https://localhost:9443"

Environment information

Product Version: IS 5.11.0

Related issues:
#11878
#8194

@minolih are we good to resolve the issue? Did we fix it in master?

Yes. This has been fixed in master with https://github.com/wso2/identity-apps/pull/2746