-buildmode=plugin not supported on windows/amd64

See title. I don't expect a bug fix I guess, but I'll leave it here so people can see that using Windows probably will not work 100%. I ended up using WSL instead.
Edit: I installed golang via scoop, maybe there is a version that does support this?

maybe there is a version that does support this

The docs at https://pkg.go.dev/plugin say

Plugins are currently supported only on Linux, FreeBSD, and macOS, making them unsuitable for applications intended to be portable.
so I wouldn't expect any other versions to support it 😞


Store chat or add undo

 version 1.79.0
OS: Windows_NT x64 10.919043
Copilot chat v0.1.2023051801

This is a usability request. It happened to me twice that I clicked the upper right Clear chat button (looks like a hamburger menu) and I lost all the context I had been constructing for a while. It could be nice to have a feature that saves the dialog to a file or an undo command associated. Maybe there is something similar but haven't found it.
Thank you

Hi @gamousquesORT it is already possible to save the current conversation to a json file with the export/import features.
You can access these features via the command panel (ctrl/cmd + p, followed by '>chat export' or '>chat import').
You can also assign these commands to any shortcut.

@AntoineWVN Thank you very much for the tip, it is very useful. I was thinking about this feature to keep the chain of thought with the bot.

History is now enabled by default. But please let me know if there is another issue.


Starting dev server for first time throws 408 timeouts on initial fetch to populate readable store - restart dev server and it goes away

Environment
SvelteKit v1.0.0-next.144
Svelte 3.42.1
OS: macOS 11.5.1
Browser: Safari 14.1.2 and Chrome 92
Describe the bug
If I bump any dependencies then run npm install && npm run dev -- --open, I get HTTP 408 errors when my readable stores are created via GETs to my API (same project - not external). If I immediately do a Ctrl-C and restart the dev server, the errors go away.
Logs (showing the errors then the errors going away after restarting dev server)

% npm run dev -- --open

<EMAIL_ADDRESS>dev
svelte-kit dev "--open"

SvelteKit v1.0.0-next.144
local:   http://localhost:3000
network: not exposed
Use --host to expose server to other devices on this network
12:08:27 PM [vite] new dependencies found: sveltestrap/src, updating...
Getting readable store: /api/location/active.json
12:08:28 PM [vite] ✨ dependencies updated, reloading page...
First request throws a 408 here

{
  size: 0,
  [Symbol(Body internals)]: {
    body: PassThrough {
      _readableState: [ReadableState],
      _events: [Object: null prototype],
      _eventsCount: 5,
      _maxListeners: undefined,
      _writableState: [WritableState],
      allowHalfOpen: true,
      [Symbol(kCapture)]: false,
      [Symbol(kCallback)]: null
    },
    boundary: null,
    disturbed: false,
    error: null
  },
  [Symbol(Response internals)]: {
    url: 'http://localhost:3000/api/product/active.json',
    status: 408,
    statusText: 'Request Timeout',
    headers: {
      'access-control-allow-origin': '*',
      connection: 'close',
      'content-length': '139',
      date: 'Fri, 25 Jun 2021 03:31:20 GMT'
    },
    counter: 0,
    highWaterMark: 16384
  }
}

Failed API call: Error: Bad response trying to retrieve from http://localhost:3000/api/location/active.json.
at getArray (/src/stores.ts:9:11)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
^C
nates@Nates-MacBook-Pro shy-svelte % npm run dev -- --open

<EMAIL_ADDRESS>dev
svelte-kit dev "--open"

SvelteKit v1.0.0-next.144
local:   http://localhost:3000
network: not exposed
Use --host to expose server to other devices on this network
Getting readable store: /api/location/active.json
12:09:29 PM [vite] new dependencies found: @fortawesome/free-brands-svg-icons, updating...
12:09:30 PM [vite] ✨ dependencies updated, reloading page...
Getting readable store: /api/location/active.json

// stores.ts
import { readable, Readable } from 'svelte/store'

const { VITE_WEB_URL } = import.meta.env

const getArray = async (url: string) => {
  const response: Response = await fetch(url)
  if (!response.ok) throw {
    console.error('First request throws a 408 here', response)
    new Error(`Bad response trying to retrieve from ${url}.`)
  }
  return await response.json()
}

const getReadableStore = (url: string) => readable([], set => {
  console.log(`Getting readable store: ${url}`)
  getArray(`${VITE_WEB_URL}${url}`)
    .then(set)
    .catch(err => console.error('Failed API call:', err))
  return () => {}
})

type SearchableStoreArrays = StudioLocation[] | []
type FindParentRecordResults = (arrayOfRecords: SearchableStoreArrays, id: number) => any
export const findParentRecord: FindParentRecordResults = (arrayOfRecords, id: number) => {
  const foundRecord = arrayOfRecords.find( ({ _id }) => _id === id )
  return foundRecord ? foundRecord : {}
}

export const locations = <Readable<StudioLocation[]>> getReadableStore('/api/location/active.json')

Here's the path it takes for the GET from /api/location/active.json...
// src/routes/api/location/active.json.ts
import type { RequestHandler } from '@sveltejs/kit'
import { getLocations } from './_location.controller'

// GET /api/location/active.json
export const get: RequestHandler = async () => {
  return await getLocations(true) // active only
}

// src/routes/api/location/_location.controller.ts
import { query } from '../_db'

type GetLocationsResponse = (activeOnly: boolean) => Promise<{ body: StudioLocation[] }>

export const getLocations: GetLocationsResponse = async (activeOnly: boolean) => {
  const sql = activeOnly ?
    `SELECT * FROM locations_active;`:
    `SELECT * FROM locations_all;`
  const { rows } = await query(sql)
  return {
    body: <StudioLocation[]> rows
  }
}

// /src/routes/api/_db.ts
import pg from 'pg'

const pgNativePool = new pg.native.Pool({
  max: 10,
  connectionString: import.meta.env.VITE_DATABASE_URL,
  ssl: {
    rejectUnauthorized: false
  }
});

type QueryResponse = (sql: string, params?: Array<number|string|boolean>) => Promise<pg.QueryResult<any>>
export const query: QueryResponse = (sql: string, params?: Array<number|string|boolean>) => pgNativePool.query(sql, params)

Severity
Severity is medium because I can always Ctrl-C and restart the dev server but it might create an impression of instability in SvelteKit which is why I didn't mark this as low.
Perhaps the initial fetch is failing because something is still being initialized by SvelteKit and the dev server isn't really up and running?

Same here, Windows and Mac.

Same here, Linux. Doesn't solve it even with a restart.

Just installed SvelteKit v1.0.0-next.146 and the problem (so far) has not reoccured. I believe this change:

[fix] enable Vite pre-bundling except for Svelte packages (#2137)
is what cured this issue.

@frederikhors and @manen - can you please upgrade SvelteKit to v.1.0.0-next.146 and see if the problem goes away for you as well?

Same here, Linux. Doesn't solve it even with a restart.

You need to restart many times!

Just installed SvelteKit v1.0.0-next.146 and the problem (so far) has not reoccured. I believe this change:

[fix] enable Vite pre-bundling except for Svelte packages (#2137)
is what cured this issue.

@frederikhors and @manen - can you please upgrade SvelteKit to v.1.0.0-next.146 and see if the problem goes away for you as well?

Gimme some hours... and I will let you know!

1.0.0-next.146 fixes the issue for me (Windows 10).
I think that now I will cry with happiness.
You can close this issue!

I use the load function now, so for me it's solved. thanks though

Solved by<EMAIL_ADDRESS>


SVG: direction="rtl" ignores text-anchor

Hello there,
I have a problem when setting the direction="rtl" for text tag. In the SVG output, the attribute swaps the text-anchor meaning for the tag but in the PNG output, it remains the same. I don't know how to handle the problem, I would be grateful if anybody helps me.

Please can you provide a sample image that helps explain the question?

Please can you provide a sample image that helps explain the question?

Here's an example:
<?xml version="1.0" encoding="utf-8"?>
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024" xml:lang="fa">

<!--StartFragment-->

    <g direction="rtl" font-family="Dana-FaNum" font-weight="bold" font-size="16">
        <text x="50%" y="260" text-anchor="middle" font-family="Dana">x=50%</text>
        <line x1="50%" y1="0" x2="50%" y2="1000" stroke="red"/>
        <text x="50%" y="300" text-anchor="start">مشکلی در کتابخانه شارپ!</text>
    </g>

<!--EndFragment-->
</svg>

The SVG output looks like this:

But unfortunately, the PNG output doesn't look the same:

That's because direction="rtl" attribute swaps the meaning of text-anchor="start" for SVG output, but for the PNG output, there's not any change!
If I omit the direction="rtl" attribute from the parent tag, both outputs look identical but the exclamation mark is not placed correctly in the RTL text (Persian).
Both the SVG & PNG output in absence of direction="rtl":

Note that if I set the text-anchor to "middle", there's no difference between the two outputs, the problem appears when we want the text-anchor to be either "start" or "end".
Thank you very much for the prompt reply.

Please can you provide a sample image that helps explain the question?

Here's an example:
<?xml version="1.0" encoding="utf-8"?>
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1024 1024" xml:lang="fa">

<!--StartFragment-->

    <g direction="rtl" font-family="Dana-FaNum" font-weight="bold" font-size="16">
        <text x="50%" y="260" text-anchor="middle" font-family="Dana">x=50%</text>
        <line x1="50%" y1="0" x2="50%" y2="1000" stroke="red"/>
        <text x="50%" y="300" text-anchor="start">مشکلی در کتابخانه شارپ!</text>
    </g>

<!--EndFragment-->
</svg>

The SVG output looks like this:

But unfortunately, the PNG output doesn't look the same:

That's because direction="rtl" attribute swaps the meaning of text-anchor="start" for SVG output, but for the PNG output, there's not any change!
If I omit the direction="rtl" attribute from the parent tag, both outputs look identical but the exclamation mark is not placed correctly in the RTL text (Persian).
Both the SVG & PNG output in absence of direction="rtl":

Note that if I set the text-anchor to "middle", there's no difference between the two outputs, the problem appears when we want the text-anchor to be either "start" or "end".
Thank you very much for the prompt reply.

Thank you, this is a great example, I also see the same problem when converting this sample SVG to PNG using the rsvg-convert command line tool.
Please can you report this upstream at https://gitlab.gnome.org/GNOME/librsvg
(As an aside, this looks like the same problem as previously-reported in #2722, but I'm not sure why that issue is closed.)

https://gitlab.gnome.org/GNOME/librsvg/-/issues/789

v0.30.0 now available with prebuilt binaries that include a version of librsvg with the upstream fix.


[3pt] PR: Modifications to rem.py for exporting minimum thalweg elev for each hydroid

Currently there are no readily accessible options for locating the thalweg elevation value associated with each pixel catchment. The minimum thalweg elevation values calculated in rem.py are used to calculate the REM raster and establish the origin for the rating curve at each hydroid segment. These elevation values are needed in order to compare the synthetic rating curves to observed values from the field (e.g. USGS rating curve or peak flow/stage values). Partner feedback example where rating curve comparison helped diagnose FIM issues: #192
Changes

Modified rem.py with a new function "make_catchment_hydroid_dict" to create a dataframe of pixel catchment ids and overlapping hydroids
Creates a new dataframe containing a merge of the hydroid dataframe and thalweg minimum elevation dataframe (already produced in rem.py)
Produces a new output csv containing all catchment ids and corresponding Min Thalweg Elevation value → “hand_ref_elev_table.csv”
Overwrites the demDerived_reaches_split.gpk layer --> adding additional attribute: “Min_Thal_Elev_meters” for easy access to view the elevation data

Notes

No changes to metrics (modifications are producing additional outputs and did not alter the previous outputs)
Slight increase in fim_run.sh runtimes:

@RyanSpies-NOAA can you import getDriver from shared_function.py and update line 124 in rem.py?

@BrianAvant-NOAA updated with getDriver function


Do not force error values

UX is everything:
almost(a, b);
almost(a, b, 0.1);

@mikolalysenko, @rreusser  please have a look)

@mikolalysenko ok I merge it?

@mikolalysenko any thoughts on that? Could you add me to the contributors on the npm?

@mikolalysenko any thoughts on that? Could you add me to the contributors on the npm?

Thoughts:

Overall, I think it makes sense, but it's a matter of style preference whether there should be a default. For most cases though, I think this matches how people will be interested in using it.
Should it be DBL_EPSILON by default since that's the default floating point precision for js?
Could you amend the docs as almostEqual(a, b [, absoluteTolerance [, relativeTolerance]]) with the corresponding notes?

@rreusser done

I don't have access to my computer at the moment but will add you as a collaborator ASAP! Sorry about that! Just spent two weeks on jury duty so I'm not performing admirably on side projects at the moment. 😞 In the mean time, can you confirm the compatibility of the API? This is just a matter of useful defaults, right? Was there a default assumption (zeros, perhaps) that this will break, or was blank simply invalid previously?

It was invalid, so it is a minor API change

Sorry for the delay! I've added you as a collaborator on npm/almost-equal. A default makes sense and looks good to me, so I think publishing is the right move. Unfortunately that doesn't add you across the board on npmjs.com, but I think I have access to most things, so I'm glad to add you as a collaborator and offer a second opinion if I can! Thanks!
:+1:

Sorry, so to clarify, I'm glad to do the honors if you like, but if you have the privileges and want to, I say merge and publish!

@rreusser thank you for the review! Done.


No buttons work

The buttons in chat do nothing and the double damage button is ENORMOUS. Foundry 9.0. All other modules deactivated when testing

The buttons in chat do nothing and the double damage button is ENORMOUS. Foundry 9.0. All other modules deactivated when testing

Sounds exactly like the problem I addressed in the previous issue thread.  Doing the steps i outlined will get the buttons to work again, but won't completely fix the formatting.


Chinese characters not displayed properly when using lxc config edit _container_

Required information

Distribution: Ubuntu
Distribution version: 18.10(cosmic) AMD64
The output of "lxc info" or if that fails:

Kernel version: 4.18.0-12-generic
LXC version: 3.1.0
LXD version: 3.8 (APT snap distribution)
Storage backend in use: dir

Issue description
I'm editing a container's config using the lxc config edit _container_name_ command, after selecting nano as the preferred text editor I noticed that the Chinese text in the edit window is garbled.
It is probably due to the misconfiguration of the locale.
Steps to reproduce

lxc config edit _container_name_
Paste the following text into the terminal: 中文字

Expected behavior
中文字 is inserted into the edit window, and is displayed properly
Current behavior
The text is garbled and is displayed like:    ^ ^   ^, as seen in the following screenshot:

Information to attach
User locale
LANG=zh_TW.UTF-8
LANGUAGE=zh_TW:zh_HK:zh_CN:en_US:en
LC_CTYPE="zh_TW.UTF-8"
LC_NUMERIC=zh_TW.UTF-8
LC_TIME=zh_TW.UTF-8
LC_COLLATE="zh_TW.UTF-8"
LC_MONETARY=zh_TW.UTF-8
LC_MESSAGES="zh_TW.UTF-8"
LC_PAPER=zh_TW.UTF-8
LC_NAME=zh_TW.UTF-8
LC_ADDRESS=zh_TW.UTF-8
LC_TELEPHONE=zh_TW.UTF-8
LC_MEASUREMENT=zh_TW.UTF-8
LC_IDENTIFICATION=zh_TW.UTF-8
LC_ALL=

UPDATE: I originally thought the LXD is provided by the APT(as /usr/bin/lxc and /usr/bin/lxd existed), however, it appears that the snap distribution is also installed and running so it's probably a snap-related problem.

(Moved to https://github.com/lxc/lxd-pkg-snap/issues/29)


ref(build): build windows images with explicit buildx builder

Description:
This change modifies the Makefile targets for building Windows images
with buildx to use the img-builder builder explicitly because the
effects of the --use flag on docker buildx create will not persist
if a user changes the default builder. This way we still ensure a
builder that can build windows/amd64 images exists and use that each
time no matter what the default builder is.

Testing done: local manual testing

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? No

Did you notify the maintainers and provide attribution?

Is this a breaking change? No

Codecov Report

Merging #4150 (3dec4fc) into main (3ff3c66) will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #4150      +/-   ##
==========================================
+ Coverage   69.34%   69.49%   +0.15%
==========================================
  Files         212      212
  Lines       11429    11429
==========================================
+ Hits         7925     7943      +18
+ Misses       3451     3433      -18
  Partials       53       53

Flag
Coverage Δ

unittests
69.49% <ø> (+0.15%)
:arrow_up:

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

Impacted Files
Coverage Δ

cmd/cli/proxy_get.go
40.47% <0.00%> (ø)

pkg/health/health.go
63.26% <0.00%> (ø)

pkg/cli/chart_source.go
80.00% <0.00%> (ø)

pkg/validator/server.go
76.34% <0.00%> (+19.35%)
: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 3ff3c66...3dec4fc. Read the comment docs.


Add MTV network

added MTV network  fixes #2089

Thanks for the pull request! Before a real human comes by, please make sure your PR has all of the below criteria checked

[x] Give a description on what the PR is for.
[ ] Make sure your PR is based on the DEVELOP branch
[x] Don't send big changes all at once. Split up big PRs into multiple smaller PRs that are easier to manage and review

Please make sure you also read contribution guide and followed all of the steps.
Thanks!


Support for multi-package repos (rush or lerna repos)

We have repos which contain multiple package.jsons. These repos use tools such as @microsoft/rush or lerna to manage installing dependencies, linking, building, and publishing them. Babel, React, Angular, Ember, Meteor, Jest, and many others develop all of their packages within a single repository.
For example, same repo, 2 different folders with package.json:
https://github.com/OfficeDev/office-ui-fabric-react/tree/master/packages/office-ui-fabric-react
https://github.com/OfficeDev/office-ui-fabric-react/tree/master/packages/utilities
Is there a way that David can generate badges for these? At a minimum, just be able to generate a badge for each of the packages, but ideally generate a single badge for the repo's README.md which can track all the dependencies in the entire repo. (If there needs to be some metadata in the root package.json to make that work, cool.)
I tried a few variations without any luck:
https://david-dm.org/OfficeDev/office-ui-fabric-react/packages/office-ui-fabric-react.svg
https://david-dm.org/OfficeDev/office-ui-fabric-react/tree/master/packages/office-ui-fabric-react.svg

https://david-dm.org/OfficeDev/office-ui-fabric-react?path=packages/office-ui-fabric-react
https://david-dm.org/OfficeDev/office-ui-fabric-react?path=packages/utilities

@alanshaw Awesome, thanks!

@alanshaw Would it be worthwhile to keep that one open as a feature request for parsing lerna.json and coming up with an aggregate status of all packages?

So having multiple (5+) package.json fils it would be really nice to have an aggregated badge. [Showing 10+ badges (dependencies + devDependencies) will probably defeat its purpose.
However, it seems this might be a bit out of scope for david dm... or is there any plan for something like this? (e.g. search through all files and pick up the package.json ones)
I'm just curious :)


From Range object to list of nodes

Version
1.3.3
Test Environment
Windows 10
Opera
Current Behavior
Inside a wwXXXManager i need to convert a Range object to a list of nodes so i can make a choice. For example if i encounter a node of one kind inside the Range i want to prevent the user to delete it. How i can do it?
Thanks in advance.
this._keyHandlers = {
      'DEFAULT': (ev, range, keyMap) => {
       //range to nodes??
      if(.......) {
        ev.preventDefault();
      }

      }
    };

util.forEach(this._keyHandlers, (handler, key) => this._wwe.addKeyEventHandler(key, handler));

Expected Behavior

I can do it with :)
var fragment = range.cloneContents();
var nodes = fragment.childNodes;


ERROR in KSSwiperModule is not an NgModule

After updating angular-cli to version 1.0.0-beta26 i get this error ERROR in KSSwiperModule is not an NgModule

same

same ++

found another github repo with a really nice working swiper wrapper for angular2, might be a viable alternative if you are in a bind for time.
https://github.com/zefoy/angular2-swiper-wrapper

same here

same here

I have the same problem

same here

Is there any good way to solve this problem?

I'm having the same problem

I fixed it by adding the @NgModule to the main module in ks-swiper.module.d.ts
This is what the file looks like for me:
import { NgModule }      from "@angular/core";

@NgModule()
export declare class KSSwiperModule {
}

After that it compiled for me

The same error :(

I've found a solution by adding ks-swiper.ts and ks-swiper.module.ts manually. So I've downloaded those files from this repo, then made a component in my project called SliderComponent, where I've imported those two files. My SliderComponent looks like this:
import { Component, Input } from '@angular/core';
import { DataGetter } from '../../data-getter.class'
import { iTemplateData } from '../../../typings/template.interface';
import { KSSwiperContainer, KSSwiperSlide } from '../../ks-swiper/ks-swiper';

@Component({
    selector: 'slider-component',
    template: `
        <g-swiper-container [options]="sliderOptions" [items]="data.list" *ngIf="data && data.list">
            <ng-container *ngFor="let sliderItem of data.list">
                <g-swiper-slide [swiperAutoplay]="sliderItem.slideTime">
                    <img [src]="sliderItem.img">
                </g-swiper-slide>
            </ng-container>
        </g-swiper-container>
        `
})

export class SliderMobileComponent extends DataGetter {

    @Input() data;

    private sliderOptions: any;

    constructor() {
        super();
        this.sliderOptions = {
            loop: true,
            autoplay: 3000
        }
    }

    ngOnInit() {
        super.OnInit();
    }

    OnData() { }
}

and it just works fine.

any update here?

Same problem when trying to build the project! any update plz?

I imported NgModule to "ks-swiper.module.d.ts" and got past the error.


Bump .clang-format to 100 columns

rive-cpp side of the change in formatting

LGTM! How did you re-run the formatter for the whole project btw?

find include/ src/ -name *.cpp -o -name *.hpp | xargs clang-format -style=file -i


Improve failure message on database connection error

Currently KubeArchive does not provide a useful message when it fails to connect to the database. We had a problem installing on a cluster where the Secret was populated in the following way:
POSTGRES_DB: ""
POSTGRES_DATABASE: "<database-name>"

This is wrong, because the correct key is POSTGRES_DB and should be populated. This problem yielded the following error:
$ kubectl logs -n kubearchive deployments/kubearchive-api-server
2024/10/02 13:18:42 Starting KubeArchive API with version 'v0.1.0', commit SHA '5b0ad85924e4b50a033f1980fbaac64a1a448d01', built '2024-09-06T07:33:30Z'
2024/10/02 13:18:42 Retry request 1, get error: dial tcp [::1]:5432: connect: connection refused
2024/10/02 13:18:43 Retry request 2, get error: dial tcp [::1]:5432: connect: connection refused
2024/10/02 13:18:45 Retry request 3, get error: dial tcp [::1]:5432: connect: connection refused
2024/10/02 13:18:49 Retry request 4, get error: dial tcp [::1]:5432: connect: connection refused
2024/10/02 13:18:57 Retry request 5, get error: dial tcp [::1]:5432: connect: connection refused

Which led us to think that there was another error other than the database name. I think KubeArchive can do better.
Acceptance Criteria

Reproduce this in the current code.
Make the error yield the URL, port, database used to establish the connection.
Don't print the password.
I'm not sure about printing the user.

I have said this before, but we shouldn't have any empty strings for any of the database connection properties.  Nor do I think we should have <database-name.
All the values should be set to our development settings.  You may get a better error message then.

I have said this before, but we shouldn't have any empty strings for any of the database connection properties.

We do, this is v0.1.0 where we didn't provide default values for them.

All the values should be set to our development settings. You may get a better error message then.

You are right, testing with a wrong database name (and all the other values OK) with v0.2.0 yields:
$ kubectl logs -n kubearchive deployments/kubearchive-sink
2024/10/03 05:27:35.864361 Starting KubeArchive Sink with version 'v0.2.0', commit SHA 'aef4220f58c10914277c2ba791e9a3680ad927c8', built '2024-10-02T11:43:34Z'
2024/10/03 05:27:35 Retry request 1, get error: pq: database "kubearchive" does not exist
2024/10/03 05:27:36 Retry request 2, get error: pq: database "kubearchive" does not exist

However if the DB is an empty string, it yields:
$ kubectl logs -n kubearchive deployments/kubearchive-sink
2024/10/03 05:26:58.479012 Starting KubeArchive Sink with version 'v0.2.0', commit SHA 'aef4220f58c10914277c2ba791e9a3680ad927c8', built '2024-10-02T11:43:34Z'
2024/10/03 05:26:58 Retry request 1, get error: dial tcp [::1]:5432: connect: connection refused
2024/10/03 05:26:59 Retry request 2, get error: dial tcp [::1]:5432: connect: connection refused
2024/10/03 05:27:01 Retry request 3, get error: dial tcp [::1]:5432: connect: connection refused

Wrong URL:
$ kubectl logs -n kubearchive deployments/kubearchive-sink
2024/10/03 05:42:22.788422 Starting KubeArchive Sink with version 'v0.2.0', commit SHA 'aef4220f58c10914277c2ba791e9a3680ad927c8', built '2024-10-02T11:43:34Z'
2024/10/03 05:42:22 Retry request 1, get error: dial tcp: lookup non-existent.postgresq.svc.cluster.local on <IP_ADDRESS>:53: no such host
2024/10/03 05:42:23 Retry request 2, get error: dial tcp: lookup non-existent.postgresq.svc.cluster.local on <IP_ADDRESS>:53: no such host

I tested some combinations of empty and/or wrong values. For wrong values the errors tend to be OK, with empty values there are some problems.

Since this error is prevented by having default values as we have now, I don't think we should implement anything for it. If it happens too much users will complain and we will implement something. Closing.


Add Low Code

https://github.com/zenitysec/awesome-low-code
This is a list of awesome low-code application development platforms, resources, and tools to help citizen and professional developers dive into the low-code world.
Low-code platforms place more power in the hands of business professionals by letting them build application with minimal to no coding skills requires, mostly through a drag and drop interface. This empowers the business to address their own issues rather than ask for IT's help. It also helps proffesional developers accelarate time-to-market and reduce their maintenance costs. The low-code ecosystem is very large, and this list tries to help people navigate it.
The list helps business users and developers answer the following questions (and many more):

Which low-code platforms are relevant for my use case?
Where can I learn about low-code and become a better low-code developer?
What are some common use-cases for low-code?
Where can I discuss my low-code challanges and ideas with likeminded colleagues?

We continously expand this list to include platforms, categories, books, learning materials, reference materials, ready-to-use solutions and more. Including this list as part of the awesome list of awesome topics would help share the knowledge about low-code, improve the knowledge base and make it easier for people to learn about it.
Note that we use awesome-list as part of PR validation so there's no need to check for those issues.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.

Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.

The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Thie repo is well prepared for its high-resolution logo image, clean structure, and rich contents.

Good list to reference as well: https://github.com/valentin-vogel/awesome-nocode-lowcode

https://github.com/valentin-vogel/awesome-nocode-lowcode

Thank you! Added to the list

Can the directories be more detailed, such as adding a level 2 directory to them?

Can the directories be more detailed, such as adding a level 2 directory to them?

Hi @flyq, thank you for your comment. I'm not sure whether a detailed directory would be good fit for the marked categories. I want to enable using the content list for quick navigation.

@sindresorhus, are there any additional requirements we should address?

drag&drop is not a word. Should have spacing.

Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Low Code is written in multiple different ways, both with and without dash and titlized and not. It should be consistent.

Thank you @sindresorhus, fixed both.


Custom Menu Logo

Added Custom Menu Logo feature

True...
BTW i have a New cleaner solution with background Image cache and CSS class
Sent from my iPhone

On 18 Oct 2016, at 10:32, Julien Renaux<EMAIL_ADDRESS>wrote:
@shprink commented on this pull request.
In lib/templates/module/menu.html:

@@ -1,4 +1,7 @@

ng-if here should be enough, why do you use ng-show?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for the PR!
We need a way to disable the icon if we want and also we do not want the img to be tracked by git (avoid conflicts if overwritten).
I would have added the icon property under menu here https://github.com/shprink/wordpress-hybrid-client/blob/develop/config/config.default.cson#L45-L51
We need to make sure null does not display anything (a way to disable it).
For the img itself I would have added it to the dist folder and copy it when installing here https://github.com/shprink/wordpress-hybrid-client/blob/develop/scripts/install.js#L10

We need a way to disable the icon if we want and also we do not want the img to be tracked by git (avoid conflicts if overwritten).
No idea how to manage it

I would have added the icon property under menu here https://github.com/shprink/wordpress-hybrid-client/blob/develop/config/config.default.cson#L45-L51
Agree

We need to make sure null does not display anything (a way to disable it).
In config.json null will do

For the img itself I would have added it to the dist folder and copy it in config when installing here https://github.com/shprink/wordpress-hybrid-client/blob/develop/scripts/install.js#L10
Agree

I will merge and release a new version as soon as you modify this :) thanks again!

Awesome job! thanks very much, will release a version tonight or 2morrow.


Update Java Simple Client Dependencies

Hi,
I added the [io.prometheus/simpleclient_hotspot "0.0.19"] as specified in the README, but i was greeted by a java.lang.NoClassDefFoundError: io/prometheus/client/SummaryMetricFamily when trying to access the /metrics endpoint.
Adding [io.prometheus/simpleclient "0.0.19"] to the deps as well fixed the problem for me.
Am I doing something wrong? Is it just a case of updating the readme?

@vise890 iapetos depends on version 0.1.15 of simpleclient, so it's probable that simpleclient_hotspot 0.1.19 uses stuff from simpleclient that was added somewhere between 0.1.15 and 0.1.19.
You're not doing anything wrong, adding the explicit simpleclient dependency or using simpleclient_hotspot 0.1.15 would be my recommended course of action until iapetos' dependencies have been updated.
Feel free to open a PR with the dependency bumps. :)

ah ok, nice.
Hopefully I'll have some time ti open a PR, unfortunately just bumping the deps breaks a few tests :(

@vise890 I'll check it out! For now, you should probably just use 0.1.15.

The dependencies have been upgraded in version 0.1.3. :)


Cocode LinkLevel Followup

The code developed along with the Chrome group which is taking action for following links in the defined schemes leveraging link depth and other random functions needs to be adapted to FF

FF add-on maintains a data structure to keep track of link-following-depth now.
The following things still need to be done / thought of:

getting initial URL from library
getting new URL from library when link tree is completely processed
special handling when an URL cannot be opened (happens from time to time)

@BrueckmannM  -fixed or is anthing sitll to be done here?

@WielandF - status?

@bensteUEM This issue could be closed!


Gesture Detection Fails When WebViewWidget is Nested Inside a Scaling Layout Widget

What package does this bug report belong to?
webview_flutter
What target platforms are you seeing this bug on?
macOS
Have you already upgraded your packages?
Yes
Dependency versions
No response
Steps to reproduce

Attempt to interact with the web content:
Try scrolling, tapping buttons, or interacting with any clickable element within the scaled WebView.
Observe the behavior:
Gestures may not register correctly, if at all.
Interactions that normally work in an unscaled WebViewWidget fail.

Expected results
Gestures also work when the WebViewWidget was scaled.
Actual results
It seems like all pointers are offset by a linear factor proportional to the scaling.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';

void main() {
  runApp(const MaterialApp(
    home: ScaledWebViewTest(),
  ));
}

class ScaledWebViewTest extends StatelessWidget {
  const ScaledWebViewTest({super.key});

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: const Text('Scaled WebView Gesture Test')),
      body: Transform.scale(
        scale: 0.9,
        child: WebViewWidget(
          controller: WebViewController()
            ..setJavaScriptMode(JavaScriptMode.unrestricted)
            ..loadRequest(
                Uri.parse('https://codepen.io/BananaCoding/pen/mdrGjpL')),
        ),
      ),
    );
  }
}

Screenshots or Videos

Screenshots / Video demonstration
https://github.com/user-attachments/assets/03e356d9-586c-4088-b059-187fc1005bf6

Logs
No response
Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.5, on macOS 14.7 23H124 darwin-arm64, locale en-US)
[✗] Android toolchain - develop for Android devices
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] VS Code (version 1.94.2)
[✓] Connected device (3 available)
[✓] Network resources

! Doctor found issues in 2 categories.

@JesperAtToni
Upon running your code on macOS, I am getting:
A platform implementation for webview_flutter has not been set.. What other setting do you have in order to run the code properly on macOS ?

@darshankawar Sorry for being unclear on this matter. I uploaded the repo here: https://github.com/JesperAtToni/mac_os_webview_scaling_test
git clone https://github.com/JesperAtToni/mac_os_webview_scaling_test.git
cd mac_os_webview_scaling_test
flutter pub get
flutter run -d macos  # For macOS

Thanks for the update. I was able to replicate the reported behavior, although I think that this maybe occuring on mobile as well. Below is macOS desktop behavior in which the pointer / cursor or gestures are not exact.
https://github.com/user-attachments/assets/6f58db74-c8ab-471a-bbff-49b0c106e673
stable : 3.24.5
master : 3.27.0-1.0.pre.744

I'm not sure if platform view gesture passthrough is framework-level, or individual embedder engine level. Framework triage, please redirect to platform-macos if this isn't framework-level.


elasticsearch: bump version, adjust sha256, drop esversion 6.8.21 support

Description of changes
Accidentally used old version of elasticsearch in #224551.

Bumped the version of other plugins
Dropped 6.8.21 support, since we are not actively supporting it in any other plugin

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

➜ nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
$ git -c fetch.prune=false fetch --no-tags --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0
remote: Enumerating objects: 32, done.
remote: Counting objects: 100% (32/32), done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 18 (delta 14), reused 10 (delta 7), pack-reused 0
Unpacking objects: 100% (18/18), 2.30 KiB | 33.00 KiB/s, done.
From https://github.com/NixOS/nixpkgs
   ed7e3a25a9d..bebf8d36831  master     -> refs/nixpkgs-review/0
$ git worktree add /Users/yamashita/.cache/nixpkgs-review/rev-8050381a438cf3a35ff0260c08e6c137dbfafaa8/nixpkgs bebf8d368312b50238bd38ee657135efc40cf681
Preparing worktree (detached HEAD bebf8d36831)
Updating files: 100% (34536/34536), done.
HEAD is now at bebf8d36831 Merge pull request #226391 from marsam/add-dot-language-server
$ nix-env --extra-experimental-features no-url-literals --option system aarch64-darwin -f /Users/yamashita/.cache/nixpkgs-review/rev-8050381a438cf3a35ff0260c08e6c137dbfafaa8/nixpkgs -qaP --xml --out-path --show-trace --no-allow-import-from-derivation
$ git merge --no-commit --no-ff 8050381a438cf3a35ff0260c08e6c137dbfafaa8
Automatic merge went well; stopped before committing as requested
$ nix-env --extra-experimental-features no-url-literals --option system aarch64-darwin -f /Users/yamashita/.cache/nixpkgs-review/rev-8050381a438cf3a35ff0260c08e6c137dbfafaa8/nixpkgs -qaP --xml --out-path --show-trace --no-allow-import-from-derivation --meta
3 packages added:
elasticsearchPlugins.analysis-kuromoji (init at 7.17.4) elasticsearchPlugins.analysis-lemmagen (init at 7.17.4) elasticsearchPlugins.search-guard (init at 7.17.4-53.4.0)

$ nix build --extra-experimental-features nix-command no-url-literals --no-link --keep-going --no-allow-import-from-derivation -f /Users/yamashita/.cache/nixpkgs-review/rev-8050381a438cf3a35ff0260c08e6c137dbfafaa8/build.nix
3 packages built:
elasticsearchPlugins.analysis-kuromoji elasticsearchPlugins.analysis-lemmagen elasticsearchPlugins.search-guard

$ /nix/store/cdp41mfxwl70922ffs1zrnn1lfp8lrag-nix-2.13.3/bin/nix-shell /Users/yamashita/.cache/nixpkgs-review/rev-8050381a438cf3a35ff0260c08e6c137dbfafaa8/shell.nix

@thiagokokada 🙇 I don’t have access to any of the team lists, so my knowledge to who reviews what is limited.

Result of nixpkgs-review pr 226544 run on x86_64-linux 1

3 packages built:

elasticsearchPlugins.analysis-kuromoji
elasticsearchPlugins.analysis-lemmagen
elasticsearchPlugins.search-guard


HWKAPM-525 | Span Service and Elasticsearch Impl

https://issues.jboss.org/browse/HWKAPM-525
Review notes:

SpanService.store() takes the same function as SpanCache to modify ids of given spans. However, modified ids are not stored in span entity but only as an index.

@jpkrohling could you please review?

@jpkrohling thanks for the first review. I have corrected what was "wrong".
Small notes/questions
IndexMissingException is thrown only when you query data of non-existing tenant. Therefore I think that the API should return null/empty/entity thing when the client asks for entities and do not propagate IndexMissingException to the client. What do you think Juca? Some other services TraceService.getTrace propagate this exception but TraceService.searchFragments not.

There are a couple of comments, to which you might or not want to take some action. There's also a request for creating a JIRA, but other than that, LGTM.

Just one quick comment. An index will only exist when data has been written to elasticsearch . So for queries that may be performed before the index exists they should return results equivalent to no data found i.e. null for get id and empty list when returning list.

Hello Gary,
methods which return a single object return null when there is no data null or index does not exist. Methods which return a collection return empty collection when there is no data or  index does not exist. What is confusing for me that some of the elasticsearch services do propagate index exceptions to the clients e.g. https://github.com/hawkular/hawkular-apm/blob/master/server/elasticsearch/src/main/java/org/hawkular/apm/server/elasticsearch/TraceServiceElasticsearch.java#L85

I think I only fixed the services that were used by the gui so this trace service method should be changed to be consistent with the others.

I would also like to discuss the issue of exception on deserialise when back as this approach could cripple the UI if just one piece of bad data got into es. So in general I agree with juca's approach but in this case it wouldn't make the UI resilient to bad data. However the tradeoff is data completeness.

When bad data is detected it is logged so could be sorted by admin. Maybe what is required is api comment to say will not return any bad data found?

Can I create a jira for it? Or I can write it on my paper sticker.


Update FmcLinkController port voltage algorithm

Expose more parameters of its operation
Final link check after setting offset voltage
From testing it was found that headstage-64 needs a very large amount of time to reach an acceptable voltage level to be considered off (nearly 10 seconds)
A new virtual SetPortVoltage method was introduced in the base link controller to allow headstages to change the procedure depending on its needs. In the case of headstage-64, a two-step procedure with a long wait time after turning port voltage off, and a very large offset voltage applied after lock.

Fixes #64

As I said on discord, this looks like a good solution to me


Allow generation of multi-file sources

SourceGen treats binaries as a single large chunk, but that's not always appropriate.  For example, the Super Mario Bros. ROM file has three distinct parts: the iNES header, the main code, and the CHR ROM.  The first and last pieces aren't addressable by the 6502, so it feels natural to split them off into separate files.
For Metroid this division becomes fairly important, as some assemblers struggle to generate 128KB of output from a single input file.  For Battlezone and Asteroids there's a natural division between the main game ROM and the vector ROM.
With the updated address region feature in SourceGen v1.8, we now have a natural place to split the output: top-level regions.
There are two issues that need to be addressed:

Construction of multiple source files, including linker commands to generate the final binary.
Generation of appropriate external reference symbols, either in-file or in a separate "include" file, for symbolic references that span files.

Constructing multiple output files is largely a mechanical issue.  SourceGen already generates two files for cc65 output, which needs a linker config file, so the general idea of having more than one output file already exists.  Figuring out the necessary linker commands for the different assemblers should be straightforward.
Generating the necessary external references is a bit more work, but should be a direct application of the cross-reference tables.
The feature should be optional.  A checkbox on the assembly source generation screen would probably make the most sense.

Moved to "TO DO" wiki.


Question: ParallelStreamProcessor::pollAndProduce with different key or value to produce

ParallelStreamProcessor::pollAndProduce only supports producing with the same key-value with the consumer.
https://github.com/confluentinc/parallel-consumer/blob/78aab492941dc647ea4a828bb4723305267157cd/parallel-consumer-core/src/main/java/io/confluent/parallelconsumer/ParallelStreamProcessor.java#L59-L65
I want to produce message with different key, value format. Since ParallelStreamProcessor::pollAndProduce only supports producing with the same key-value, i used ParallelStreamProcessor::poll and separate producer.
Consumer<String, String> kafkaConsumer = new KafkaConsumer<>(consumerProperties);
var options = ParallelConsumerOptions.<String, String>builder()
    .ordering(ParallelConsumerOptions.ProcessingOrder.KEY)
    .maxConcurrency(1000)
    .consumer(kafkaConsumer)
    .build();
ParallelStreamProcessor<String, String> parallelStreamProcessor = ParallelStreamProcessor.createEosStreamProcessor(options);
parallelStreamProcessor.subscribe(List.of(TOPIC_NAME));

Producer<String, Integer> kafkaProducer = new KafkaProducer<>(producerProperties);

parallelStreamProcessor.poll(pollContext -> {
    logger.info("consumes: {}", pollContext);
    ProducerRecord<String, Integer> producerRecord = new ProducerRecord<>("newTopic", 3);
    logger.info("produces: {}", producerRecord);
    kafkaProducer.send(producerRecord); // uses separate producer
});

It there any way to use pollAndProduce in this case? Maybe code snippet would be
Consumer<String, String> kafkaConsumer = new KafkaConsumer<>(consumerProperties);
Producer<String, Integer> kafkaProducer = new KafkaProducer<>(producerProperties);
var options = ParallelConsumerOptions.<String, String, String, Integer>builder() // need more generic
    .ordering(ParallelConsumerOptions.ProcessingOrder.KEY)
    .maxConcurrency(1000)
    .consumer(kafkaConsumer)
    .producer(kafkaProducer)
    .build();
ParallelStreamProcessor<String, String> parallelStreamProcessor = ParallelStreamProcessor.createEosStreamProcessor(options);
parallelStreamProcessor.subscribe(List.of(TOPIC_NAME));

parallelStreamProcessor.pollAndProduce(pollContext -> {
    logger.info("consumes: {}", pollContext);
    ProducerRecord<String, Integer> producerRecord = new ProducerRecord<>("newTopic", 3);
    logger.info("produces: {}", producerRecord);
    return producerRecord; // just returns new record
});

Hi, not at the moment. See:

#175

It is intended to be fixed for 1.0 though.
Workaround, is to tell PC to do byte,byte, and do your own serve in your function. So, given the workaround isn't a big deal, it's not been a priority, and I want to fix it right.

Thank for reply and workaround!
I didn't know there was an issue already. Close this one.


Cleanup and switch oci8_driver and oci8_result to PHP5 functions

replaced all PHP4 / OCI8 PECL < 1.1.0 functions with those from PHP5 as they are no longer needed and are deprecated anyways
removed a PHP4 backwards compatibility workaround for _fetch_object()
fix _error_message() and _error_code() to work for connect-time generated errors
method visibility declarations (not really needed, but still ... PHP4 no longer supported)
miscellaneous clean-ups (spaces, comments, etc.)

Looking good. Hopefully we can get somebody who uses OCI8 to test this? I don't fancy installing it myself just to give it a go.

I can do some testing on this, we're about to move the UM homepage into beta and it uses oracle. i'll be back when i have more.

Already tested it on a work project that's ready to go live and depends entirely on OCI8 - works fine. No further tests can do any harm though, so @jakanavitch could do some double checking before merging it. :)

Everything looks good from here, all of my code behaved as expected. @narfbg thanks for putting some time into this!

 Most of my projects are based on CI now, so helping to improve it makes my life easier as well. It's a win-win. :)

Right, here we go!


Automated cherry pick of #8818

Cherry pick of #8818 on release-6.0.
/cc  @ctlaltdieliet

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.


[Question]: Azure DevOps Pipelines are failing at checkout task

Describe your question
Azure Pipelines are failing at default checkout task in all the agents in one of our self hosted agent machines with error "fatal: Cannot prompt because terminal prompts have been disabled."
We have another machine with couple of agents, and the pipelines are working fine there.
Versions
Version Dev19.M233.1 (AzureDevOps_M233_20240212.1)
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Operation system
No response
Version controll system
Git
Azure DevOps Server Version (if applicable)
No response

Hi @PhanindraReddyP this error may indicate an issue with authentication. Could you please verify that the tokens used on that machine are not expired/revoked.

Hi @PhanindraReddyP, unfortunately we didn't get any updates from your side,
Please feel free to re-open this issue if it is still bothering you.

Hello @kirill-ivlev and @aleksandrlevochkin, I would like to re-open this case as we are facing this issue again
Aleksandr, it is not about the token, because it works when we try to clone in a different folder or different machine with the token.
Initially the error occurred in Feb 2024 and suddenly it got resolved somehow we dont know how.
But the same error coming up now. We tried the work arounds like changing the logon from the agent service properties from Network Service to Local Account and from Local account to Network Service.
Any help to resolve this would be greatly appreciated.
Thanks in advance.


fix(github): correctly return maxResults releases

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Fixes #1133  🦕

@kalosisz thank you for the contribution.


permalinks generates unbrowseable urls

Describe the bug
permalinks goal is to generate browseable urls, I've updated the plugin from version 0.5.0 to version 2.1.0 and the plugin is now generating some une browseable urls.
To Reproduce
Steps to reproduce the behaviour:

create some markdown document whose title should be stripped from wrong characters ("user guide (en)", "Cahier d'orientations")
Build the static website
See the generated folder, path are not browseable: user-guide-(en), cahier-d'orientations

Expected behaviour
A browseable path, such as user-guide-en/index.html or cahier-d_orientations/index.html
Environment

linux
node v10.15.1
npm 6.4.1
metalsmith 2.3.0
metalsmith-permalinks 2.1.0

This new behaviour seems to appear with version 2.0.0, and the use of slugify to fix security issues.
But default options are not working correctly.

This has been resolved with v2.2.0. See the second example in slug options which shows the config you're after.

That's a good news and I had seen this possibility of configuring slugify.
But in my opinion, the default configuration of metalsmith-permalinks should generate browseable url by default.
Don't you share this opinion?
Why do you want to keep the slugify config vanilla?

The main drawback is that the plugin does not work out-of-the-box because of the generation a invalid url.
The second drawback is that I am forced to reverse engineer the previous behaviour of the plugin, then to post-configure the new behaviour of the plugin so that my old well known urls don't change while upgrading the plugin.
That's why it would be very very very useful if the default configuration of the new release of the plugin:

generate valid url
have the same behaviour as the previous release (pre-2.x.x)

@woodyrew Can you please share your opinion about the futur of this issue?
Do you plan to change the default behavior of the plugin to be compatible with the web, and with the previous behavior of this plugin?
Or do you plan to leave it as is and let each user to tweak the configuration?
Thanks.

Maybe I should open a new issue so that you can see it. Tell me if you read that.

In fact, the default configuration of slugify is the following:
slugify('some string', {
  replacement: '-',    // replace spaces with replacement
  remove: null,        // regex to remove characters
  lower: true          // result in lower case
})

And the line just after the default configuration explains how to remove invalid characters:

For example, to remove +~.()'"!:@ from the result slug, you can use slugify('..', {remove: /[+~.()'"!:@]/g}).

So the default configuration used by metalsmith-permalinks should be:
slugify('some string', {
  replacement: '-',    // replace spaces with replacement
  remove: /[*+~.()'"!:@]/g,        // regex to remove characters
  lower: true          // result in lower case
})

This restore the previous - and correct - behaviour of metalsmith-permalinks.


Canonical way to use local package

Just want to ask for the canonical way to use my local package. Can I do it with package! macro?

package! should be used for installing remote packages. While it could be used to install local packages, it would be a very clumsy and error prone way to do it.
#1213 asks this question and I offer better alternatives there.


Update DG

Implement all feature flaws, fixes #215, #214 , #211 , #210, #206,  #203, #201, #196 , #195, #181, #178
2.Update diagrams and links to remove instances of addressbook
Add more user stories and use cases
Add more test cases for appendix

LGTM


using arabic

why don't use Arabic numbers on Local = (ar)

but those numbers are not arabic

I think he means Western Arabic numerals with Arabic script

Western Arabic numerals as in (0,1,2,3,4,5,6,7,8,9)

As opposed to

Eastern Arabic numerals (٠	١	٢	٣	٤	٥	٦	٧	٨	٩)

The code currently uses the default PHP NumberFormatter to automatically format the numbers based on the locale passed in the locale parameter. So if locale is set to ar, it will tell PHP to format numbers according to how it determines Arabic formats numbers. There is not currently a way to use the translations without also affecting number formats and default date formats at the same time.
A possible feature idea could be to add parameters for the "number locale", "day of week locale", "date format locale", "translation locale" as necessary and of course the existing locale parameter would set all of them, but the specific parameters could be used to override the locale, for example, number_locale=en to use western style numerals instead of the default Arabic numerals.


"interval: daily" checks are not run.

Package manager/ecosystem

pip, docker, github-actions
Manifest contents prior to update

Updated dependency

What you expected to see, versus what you actually saw

The checks are configured to be run daily, but it has been over 3 days since they were run the last time.
Images of the diff or a link to the PR, issue or logs

version: 2
updates:
- package-ecosystem: pip
  directory: "/"
  schedule:
    interval: daily
  open-pull-requests-limit: 10
- package-ecosystem: "docker"
  directory: "/"
  schedule:
    interval: "daily"
  open-pull-requests-limit: 10
- package-ecosystem: "github-actions"
  directory: "/"
  schedule:
    interval: "daily"
  open-pull-requests-limit: 10

https://github.com/oittaa/gcp-storage-emulator/
https://github.com/oittaa/gcp-storage-emulator/blob/97ccaa6953f4d6f4e855bb8c88597959447e8a7c/.github/dependabot.yml

👋 @oittaa: Thanks for getting in touch. As you mentioned, I see that the daily jobs ran for your repository on Feb 26 (at 05:07 UTC), but didn't run on Feb 27 or 28. Sorry about that. We had some exceptions over the weekend. :-/
From the logs, it looks like jobs did successfully run today (March 1 at 05:10:06 UTC) for three of your ecosystems (pip, docker, and github-actions). So, I think things should be back on track now. If you're still seeing issues, please let us know.


Where is HTTPEvent?

The HTTPEvent declared in http-types.d.ts seems to be a non-existent type?

Having this issue as well, trying to compile the types locally also gives a load of errors.

looks like a bug, will fix this

Fixed in the latest version


Nuget Package Restore fails

Hi,
when opening the #rel/2.0.0 solution I get several Nuget Package Restoring issues.
After a subsequent build (of course) this amount of errors even grows.
I use a fresh installation of  Visual Studio 2017 15.3 with all necessary packages and ASP.net Core 2.0.
Do I have to adjust something?

What are you trying to do? SignalR was not shipped as part of Asp.NET Core 2.0 and the #rel/2.0.0 release has been created only because SignalR is part of the Asp.NET Core build system. If you want to build from sources clone the repo, go to the dev branch and and run build.cmd/build.sh from repo root. It will install the runtime (SignalR requires 2.1.0 runtime at the moment) and all dependencies. If you want to just try packages use this NuGet.config install a 2.1.0 runtime.

Ahh thank you very much.
That the  #rel/2.0.0 release was only created because of sharing the built system with Asp.Net Core solves the confusion. Than it is obvious, that the problems appear because of the lack of Asp.Net Core  2.1.0 packages.
I tried to port an Asp.Net MVC/SignalR project to Asp.Core to run it in Service Fabric. But if I have to move to the early 2.1.0 version, I will deploy my project in a Docker container until we can enjoy Asp.Core 2.1.0 and SignalR in Q4. :)

@BaluJr - we are planning an alpha release and we want it to work on top of Asp.NET Core 2.0 so you should be able to try it out sooner.


Can't setup the worker after destroy

I have previously installed the farmvibes-ai and run some tasks successfully, but at some point it started to give connection refused or 500 errors:
HTTPConnectionPool(host='<IP_ADDRESS>', port=30000): Max retries exceeded with url: /v0/runs (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fb0b6cdada0>: Failed to establish a new connection: [Errno 111] Connection refused'
I have tried to stop/start the cluster, but it didn't help. After that I tried to destroy it and then install again, however I get the following error when trying to setup the cluster:
 Deploying the Dapr control plane to your cluster...
✅  Success! Dapr has been installed to namespace dapr-system. To verify, run `dapr status -k' in your terminal. To get started, go here: https://aka.ms/dapr-getting-started
Installing redis in the cluster...
statefulset.apps/redis-replicas scaled
Installing rabbitmq in the cluster...
^[[B^[[BError: INSTALLATION FAILED: timed out waiting for the condition
Failed to install rabbitmq in k8s cluster ❌
Error from server (BadRequest): pod redis-master-0 does not have a host assigned
Error from server (BadRequest): pod redis-master-0 does not have a host assigned

I have also tried to clean up the .config/farmvibes-ai/, .kube and .k3d folders, but it didn't help.

The command docker rm k3d-farmvibes-ai-serverlb k3d-farmvibes-ai-server-0 k3d-farmvibes-ai-registry.localhost should allow you to delete the cluster.
If you can, please share the output of docker logs k3d-farmvibes-ai-server-0.

Yes, I've tried deleting the services as well. I've attached the logs
logs.txt

Thanks for sharing the logs. Will analyze them.
Are you able to recreate a cluster after deleting the individual containers?

@iharshulhan, from looking at the logs, looks like k3d is under disk pressure. How full is your disk there? (The output of df -h.)

No, I'm not. I can see the containers appearing in the docker while setup is running, but then it fails with the same error and they are stopped:
Installing rabbitmq in the cluster...
E0224 13:31:30.699003   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:30.712449   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:30.992132   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:30.997496   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.007208   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.009850   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.014913   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.021951   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.033744   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.034761   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.041707   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.047921   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.053529   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.059946   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.066667   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.072413   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.083565   83016 memcache.go:255] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
E0224 13:31:31.084413   83016 memcache.go:106] couldn't get resource list for metrics.k8s.io/v1beta1: the server is currently unable to handle the request
Error: INSTALLATION FAILED: timed out waiting for the condition
Failed to install rabbitmq in k8s cluster ❌

@iharshulhan, from looking at the logs, looks like k3d is under disk pressure. How full is your disk there? (The output of df -h.)

There is still 40G available:
/dev/nvme0n1p3  916G  830G   39G  96% /
At the moment the cache of farmvibes takes about ~640GB

Is that running on an ext4 filesystem? By default, ext4 reserves 5% of the filesystem to the root user.
Considering your fs has 916GiB total space, that'd give ~45.8 GiB of reserved space to the root user, which is pretty close to the free 39 GiB you're seeing.

Is that running on an ext4 filesystem? By default, ext4 reserves 5% of the filesystem to the root user.
Considering your fs has 916GiB total space, that'd give ~45.8 GiB of reserved space to the root user, which is pretty close to the free 39 GiB you're seeing.

Yes, you were right it worked after freeing some memory. Feel free to close the issue. Thanks!
As a follow up question, Is there a  clean up agent in farmvibes, which would remove unused cache data to free up space? I'm trying to run the crop_cycles calculation for a small polygon (~2000sq metres), but it uses hundreds of gigabytes to do that.

As a follow up question, Is there a clean up agent in farmvibes, which would remove unused cache data to free up space? I'm trying to run the crop_cycles calculation for a small polygon (~2000sq metres), but it uses hundreds of gigabytes to do that.

Not right now. We are working on that feature, though. Should land in the repos in a month, give or take. (CC @msplants)

BTW: You can change the reserved space percentage with tune2fs -m <percentage> /dev/nvme0n1p3.


New version: JetBrains.Kotlin.Compiler version 1.9.0-RC

Pull request has been created with Komac v1.9.1 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116163&drop=dogfoodAlpha

@wingetbot waivers Add Validation-Executable-Error


How to set coverageThreshold with CLI

As the code, https://github.com/facebook/jest/blob/3e805bc082c8da90c33a4dff9d3e1b0804a4386d/packages/jest-cli/src/cli/args.js#L211
The argument should be a JSON string, but the below command always doesn't work.
 jest --coverage --coverageThreshold='{\"global\":{\"branches\":90,\"functions\":90,\"lines\":90,\"statements\":90}'

It should be failed since it does not reach the target. However, it is always successful.

Funnily enough if there is coverageThreshold defined in the jest.config.js and then one passes through --coverageThreshold={} it ignores the coverageThreshold in the config file. So it does do something.

for package.json you need to escape
    "test:coverage": "jest --coverage --coverageThreshold='{\"global\":{\"statements\":\"80\"}}'",

For not-100% exceptions I'm taking like that:
{
"scripts": {
"test/%subproject%"
: "jest --selectProjects %subproject% --coverageThreshold=\"'$(cat %subproject%.coverage.json)'\""
}}

--coverageThreshold='{"global":{"statements":"80"}}'"

have you had the problem where this is treated as an invalid json object before?
It works on Mac, but on windows the following error appears:
> jest --coverage --collectCoverageFrom=*.ts --collectCoverageFrom=*/**/*.ts --coverageThreshold='{"global":{"statements":"85"}}'

SyntaxError: Unexpected token g in JSON at position 1
    at JSON.parse (<anonymous>)

On Windows I had to escape \
"test:coverage": "jest --coverage --changedSince=master --coverageThreshold=\"{\\\"global\\\":{\\\"statements\\\":80,\\\"branches\\\":80}}\"",

which results
jest --coverage --changedSince=master --coverageThreshold="{\"global\":{\"statements\":80,\"branches\":80}}"

Putting the JSON object in the CLI parameter is a good workaround but makes the CLI usability a bit cumbersome and ugly. I'm migrating from mocha and this is the only thing that is worse here...
Any chance to move this forward?

I made this solution for my project, to only push with husky when I have minimum coverage.
Package.json
"scripts": {
  "test": "jest --clearCache && jest --passWithNoTests --no-cache --runInBand --coverageThreshold=\"{}\"",
  "test:push": "jest --clearCache && jest --passWithNoTests --no-cache --runInBand"
},

Jest.config.ts:
coverageThreshold: {
  global: {
    branches: 80,
    functions: 80,
    lines: 80,
    statements: 80,
  },
},

Can we please just get --coverageThresholdPercentage=100 for 100% on everything for more fine grained --coverageThresholdPercentage=100,100,90,80


Feat state refac removeunusedstate

Refactored state to supply new structure for needs corresponding connections and messages

tested on integration test with chrome:
cannot create needs, if i try to publish a need it doesnt work, js error is:
Uncaught (in promise) ReferenceError: q is not defined
    at F.acquireUpdateLock (app_jspm.bundle.js:39)
    at Object.o.fetch (app_jspm.bundle.js:40)
    at Object.o.ensureLoaded (app_jspm.bundle.js:39)
    at app_jspm.bundle.js:46
    at app_jspm.bundle.js:3
    at Object.dispatch (app_jspm.bundle.js:28)
    at Array.d (app_jspm.bundle.js:46)
    at app_jspm.bundle.js:46
    at <anonymous>

Additionally i got a weird error when trying to sign up there was kind of an endless loop on the start page with constantly printing the following js errors:
Tried to access view "createNeed" that won't workwithout logging in. Blocking route-change. Error: transition prevented     at v [as $get] (angular-ui-router.js:1375)     at Object.e [as invoke] (angular.js:2035)     at angular.js:1892     at d (angular.js:2004)     at Object.e [as invoke] (angular.js:2030)     at Object.$get (angular.js:1920)     at Object.e [as invoke] (angular.js:2035)     at angular.js:1892     at Object.d [as get] (angular.js:2004)     at g (ngRedux.js:52)

closing pull request


Delete deploy

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind api-change
/kind bug
/kind cleanup
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake
/kind code-refactoring

What does does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #?
How to test changes / Special notes to the reviewer:

Could not delete deployment nodejs-deploy as deployment was not found should be the test


Support fenced code block in list.

It would be great if we can do something like this:

A list item with some code sample
console.log('hello, world.');

Why do not use marked? It should better than showdown.

:+1:
@vilic Have you found a decent workaround for this in the meantime?

@tomekr sadly no.

Unless I'm wrong, this is https://github.com/showdownjs/showdown/issues/208 and there's an easy solution.

@jgillich I cant get the work around you posted to work on http://showdownjs.github.io but not in Ghost. The best I've been able to manage is:
1. item one
    ```code 1
    code 2
    ```
2. item two
Which creates a what looks like a code block broken in half over two lines:

@JohnWestlund I believe the workaround doesn't used "fenced" code blocks, rather relies on the indentation to indicate a code block. e.g.:

@kevinansfield yes, the indentation work but how do you use syntax highlight without fenced code blocks
 ```language-javascript
 [...]
 ```

How about this?

Code blocks nested in blockquote are not rendered correctly. It should be a
...
, but in Ghost got just 。
Take below as example:
> Note:
>
> Some code in blockquote.
>
> ```javascript
> function() {
>   consoel.log('hello world!');
> }
> ```

These markup is rendered to:

Note:

Some code in blockquote.

javascript
  function() {
    consoel.log('hello world!');
  }

The correct result should be:

Note:

Some code in blockquote.

function() {
  consoel.log('hello world!');
}

The official demo of Showdown works well.

Marked works well, too.
So why do not use the official version of Showdown, the Ghost fork is out of date and bugly.

I really wanna know when will this issue be fixed

need fixed + 1

When will fenced code block be supported in Ghost? Have been waiting for this for a long long time


Add Dis-Snek

Dis-Snek is an in-development Discord library for Python that is meant to be fast, easy to use, and easily modifiable.
The library already has significant coverage of the Discord API (pretty much everything but voice), and while there are still many parts that aren't exactly polished, it is more than usable for basic use.
In terms of where to place it, the - was a slight problem - I decided to sort it based on if the - wasn't there.

We have an action for sorting now thanks to https://github.com/apacheli/discord-api-libs/pull/31 In theory, sorting will automatically be corrected :)


#1332: Performance improvements.

Description
This pr changes a bit when the frontend renders fields.
For block editor: It will only render the fields if the item is expanded. Freeing up dom space.
For fields: It will only render the active language fields, Freeing up dom space.
This was tested on a page with 100 blocks, each having 102 fields and 8 languages.
After this pr:
Time to interactive (via lighthouse): 3.2 s
Dom size: nodes: 2972, depth: 17, length: 188737
Before this pr (had to reduce the languages to 2 to make it work):
Time to interactive (via lighthouse): 8.3 s
Dom size: nodes: 45331, depth: 31, length: 410479
So this pr dramatically reduces the size of the page and improved the performance by quite a lot on bigger blocks editors/language combinations.
Please do have a look at this as I don't know why it is there or what side effects it may generate:
https://github.com/area17/twill/compare/2.x...haringsrob:1332-dom-performance?expand=1#diff-4d78aaef72f437ac2e1e4230b2bf68cc575aa52a7ec4798ecf659ef89768f71f
Related Issues
Fixes #1332

Amazing @haringsrob!
Thanks for flagging what to look for. Regarding the beforeDestroy, it was meant to remove deleted fields values from the vuex store. Say the user deletes a block or repeater, we want to make sure that the fields it contained are not going to be sent to the backend on save.
It might be that this is not necessary anymore, but worth testing further.

Ok makes sense, I will test this further.

Having another look at this today it seems to break reference fields, media fields

I double checked this and resolved some issues.
For all destroy hooks I checked and the db is clean after removing an item.


Job cmake_* broken due to dependecy issue

🐛 Describe the bug
The cmake_windows_cpu job started failing on 20220912 with:
Specifications:

  - pytorch=1.13.0.dev20220912 -> python[version='>=3.10,<3.11.0a0|>=3.9,<3.10.0a0|>=3.8,<3.9.0a0']

Your python: python=3.7

If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.

The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Package intel-openmp conflicts for:
numpy -> mkl[version='>=2021.4.0,<2022.0a0'] -> intel-openmp[version='2021.*|2022.*']
pytorch=1.13.0.dev20220912 -> mkl[version='>=2018'] -> intel-openmp[version='2021.*|2022.*']
pytorch=1.13.0.dev20220912 -> intel-openmp

Package ca-certificates conflicts for:
python=3.7 -> openssl[version='>=1.1.1n,<1.1.2a'] -> ca-certificates
numpy -> python[version='>=2.7,<2.8.0a0'] -> ca-certificates

Package mkl conflicts for:
numpy -> mkl[version='>=2018.0.0,<2019.0a0|>=2018.0.1,<2019.0a0|>=2018.0.2,<2019.0a0|>=2018.0.3,<2019.0a0|>=2019.1,<2021.0a0|>=2019.3,<2021.0a0|>=2019.4,<2021.0a0|>=2021.2.0,<2022.0a0|>=2021.3.0,<2022.0a0|>=2021.4.0,<2022.0a0|>=2019.4,<2020.0a0']
numpy -> mkl_random -> mkl[version='>=2020.1,<2021.0a0']

Versions
Latest main for TorchVision, PyTorch Core 20220912
cc @seemethere

It was fixed by @atalman yesterday but it broke again today. See latest failure.

The cmake_windows_cpu was fixed on the 20220919 but unfortunately the cmake_macos_cpu broke now.
@atalman @malfet @seemethere I understand that this issue pops up when the Core nightly releases break. Can we do anything to avoid breaking our CI (perhaps keep the older nightly available)? It's been happening quite often the last few weeks. Thanks!

@datumbox @malfet looks like this issue is related to: https://github.com/pytorch/pytorch/issues/85085
Which related to our nightly failures, here an example:
https://github.com/pytorch/pytorch/actions/runs/3088067813/jobs/4995149208
error during conda upload:
Error:  ('Connection aborted.', ConnectionResetError(104, 'Connection reset by peer'))
Error: Process completed with exit code 1.

Hence missing binary makes conda find wrong package or not find package at all as in this case.
I think to mitigate this issue we should implement retry for conda uploads

Bumping priority on this issue, since it required for nightly and CI/CD stability

The problem was fixed again yesterday by @atalman but broke again today. See:

https://app.circleci.com/pipelines/github/pytorch/vision/20449/workflows/af45d07b-293f-4d16-83c8-9ebbc8998d60/jobs/1663608
https://app.circleci.com/pipelines/github/pytorch/vision/20449/workflows/af45d07b-293f-4d16-83c8-9ebbc8998d60/jobs/1663584

Today the following is failing: https://app.circleci.com/pipelines/github/pytorch/vision/20545/workflows/59f0125b-d7f1-4e30-962b-c2fbbd59086a/jobs/1671677

I think one simple solution is to relax the requirement on TorchVision side to always have nightly corresponding to the day CI is running, but use older ones if necessary (But say throw an error if nightly is older than 2 weeks)

@malfet It's a tricky tradeoff. I think we might need the expertise of RelEng and Core devs on this choice.
99% of problems recorded in these series of issues is because some web request fails and can't download dependencies. It typically happens to 1 or 2 binaries at the time, with the rest working fine. So on our current situation, only a fraction of binaries from core are expected to fail. So, if a real breaking change occurs, because our tests run fully in the entire matrix, we would be able to capture it even if one or two binaries are old.
There are risks associated though:

@YosuaMichael is moving towards reducing the amount of tests we run on the matrix to speed up the tests and reduce costs. If one of them gets broken, then we risk not knowing about a significant change on Core that might be hard to revert 2 weeks later.
It's possible that an exotic breakage exists that is visible only on a very specific configuration. One example of such a breakage was on the dispatching of TorchVision kernels in M1 (see #6152).

On one hand, this proposal seems low risk given our current setup and will remove the burden of dealing with these issues every other week. On the other hand, it can lead to big breakages that might undo the aforementioned time savings. There is also the option of doing a hybrid approach of retrying to download the dependencies multiple times within the day and at the same time do what you said with reduced time window (3 days instead of 2 weeks). I would love to hear your thoughts on pros/cons here.

@datumbox The regression regarding the job retry should be fixed by https://github.com/pytorch/pytorch/pull/85545

@atalman indeed it looks like it. Thanks a lot for the patch. Shall we close this issue and if it reoccurs reopen?


Added support for Vector2 and Vector3 motor value types

I feel that supporting Vector2 and Vector3 value types is important because they are more natural to work with for animating position and size than GroupMotors. They should also be faster than GroupMotors because they only step one Goal as opposed to 2 or 3 with GroupMotors.

Modified live type checking to accept Vector2 and Vector3 values
Added static type checking that comes from a new Types.lua
Modified the math in Linear and Spring to support Vector2 and Vector3
Added tests for supplying Linear and Spring with a different targetValue type than initialValue type

I originally added the static type checking because I thought luau did type checking on runtime, which is not the case. This is also the reason why I initially removed the asserts and then added them back. If you prefer, I can remove the static type checking altogether.

This has the same pitfalls as this PR and is honestly not a direction I'd like to go in. I apologize.


Declare less Hugo versions

We currently specify in many different places which version of hugo to use:
website on  main [$] via  v12.22.4 via 🐍 v3.8.10
❯ git grep 0.86.0
Makefile:HUGO_VERSION               ?= 0.86.0
docker-support/Dockerfile:FROM fluxcd/website:hugo-0.86.0-extended
netlify.toml:  HUGO_VERSION = "0.86.0"
package-lock.json:      "version": "0.86.0",
package-lock.json:      "resolved": "https://registry.npmjs.org/hugo-extended/-/hugo-extended-0.86.0.tgz",
package.json:    "hugo-extended": "^0.86.0",
website on  main [$] via  v12.22.4 via 🐍 v3.8.10

Right now, only package*.json are updated through dependabot. AFAIK, only netlify.toml is relevant for building the website? Can we slim this down somewhat?
@hiddeco @kingdonb Do you have any input on this?

The convention in Ruby that I've seen to avoid duplicating the version is to put a file .ruby_version which is honored by some version managers, and use string interpolation to get that pulled into the Gemfile. That's not possible with package.json (and wouldn't work well for Dockerfile either.)
I think the best we can do is to build some CI job around the docker-support image, it should keep the published website support image updated on some cycle, and assert that versions in all of these places are correctly aligned. This can be something I could take a look at.

Is https://github.com/fluxcd/website/blob/main/Makefile#L126-L127 used at all anywhere?

Yes, this builds the base image since Hugo upstream doesn't provide one with the flags we need (or one per version at all)


Besu onchain permissioning, initial set of nodes are NOT getting added  into the besu network.

Description
While executing 'yarn run build' accounts specifie in .env file are getting added but nodes are not getting added. I have tried not pto provide initial set of enodes, however server is getting up. from browser also nodes are not getting added .I have checked all enode details, all are current. I spin up 3 nodes as described in the example .
https://besu.hyperledger.org/en/stable/Tutorials/Permissioning/Getting-Started-Onchain-Permissioning/
Error trace
I am executing on chain per missioning example . while running 'yarn migrate --reset ' node are not getting added
Adding Initial Allowlisted eNodes ...
enode://9526c2994497fd9f6a8f2288f344afa8dd1142f30af2d9c69176786adbdc4dddaaa00f82cc9518dcb39984fecfbb359a8751897d7741c34de99bf5dd4444be9a@<IP_ADDRESS>:30303,enode://5095fe60ab5f0cb30f76044fec5278ea57fa189c01a65e4bb03808ee337af64e63342f84b2945e64f22ef2ef5ab4fe10fadd2e92ddaea8548ed8b4004180483f@<IP_ADDRESS>:30304,enode://3691dd126e791534d8f1f44a0c95397e124f4ccdb96af29f084ee7f18af6dfd36ed4d16720b85642cd73956e247670f7d8d0d3dfef7ffb444aea4b37990d5780@<IP_ADDRESS>:30305
Exiting: Review successful transactions manually by checking the transaction hashes above on Etherscan.
Error: Execution reverted
at module.exports (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/migrations/3_deploy_node_ingress_rules_contract.js:87:50)
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Migration._deploy (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:72:1)
at Migration._load (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:54:1)
at Migration.run (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:202:1)
at Object.runMigrations (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:152:1)
at Object.runFrom (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:117:1)
at Object.runAll (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:121:1)
at Object.run (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/migrate/index.js:86:1)
at runMigrations (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate/run.js:78:1)
at Object.module.exports [as run] (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate/run.js:44:1)
at Command.run (/home/ubuntu/Documents/block-poc/hyperledger-besu/onchain-sec11/onchain-permissioning/permissioning-smart-contracts/node_modules/truffle/build/webpack:/packages/core/lib/command.js:189:1)
Truffle v5.4.32 (core: 5.4.32)
Node v16.14.0
error Command failed with exit code 1.

Hi, I think this should be fixed in this PR https://github.com/ConsenSys/permissioning-smart-contracts/pull/265 - can you please try the latest version?

Seems its working in updated version. Thanks!

Great to hear, thanks!


Other react element functionalities breaks after click on calendar input

Hi,
I added this react date picker.So when i clicked on the calendar input it opens calendar pop up .After that when the calendar pop is closed, whole page is not functined.All the functionalities are broken.What should i do

What browser are you running, and can you did you notice any errors in your console?


[v3] Spatial meshing support

This issue tracks the development of a spatial mesh visualization solution for v3.

[x] Evaluate diff between existing MRTK 2.x spatial meshing system/provider
[x] Port spatial mesh visualization from2.x system into a scene-only visualizer
[x] Evaluate connection between spatial mesh visualization and SU
[x] Migrate from Windows XR plugin-based mesh API to the Unity native API (Blocked on remoting limitations)

ISSUE MIGRATION
Issue migrated from: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/10122

Original comment by:
 Zee2

Done, ARFoundation ARMeshManager works.


Travis parallel testing

This merge adds a new build matrix to the travis setup that includes a thread-parallel GCC builder to address issue #144. It also seems to fix recent OSX builder instabilities by updating the OXC builder to xcode8.

looks uncontroversial

Yes, but the last commit (OSX fix) doesn't actually work. So, I think for now we want to disable the OSX tests and file an issue until someone properly debugs and tests the intermittent TTI failures.

Ok, all green, so merging...


Fix "Set up working directory" step for windows

The code snippet copied the shell script instead of the powershell script.

@loicbs : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @loicbs,
Thanks for the fix. The change looks good.
Thanks,
Pat
#sign-off


Fix node readme file: url's was pointing to rep root not node folder

The example url's in the node's folder readme file are pointing to repository root, not to the actual node examples.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: eduardpaul sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Wow, you JUST beat me! I submitted the same thing in #51 ... feel free to ignore mine if you merge this one.

Hi @eduardpaul
Thank you for this contribution.  However, It looks like you and @navzam both submitted PRs to fix the broken links in examples.  However, https://github.com/MicrosoftDX/botauth/pull/51 appears to have fixed a couple that this PR missed.  I've merged the other PR and will be closing this one.


Digest: NEXT_NOT_FOUND

in the directory:  /problems/1
It happens only when deploying to vercel, on the local computer works fine

fixed


Upgrade Component for K8up 2.0

Context
K8up 2.0 contains breaking changes. Adapt the component to support K8up 2.0 and provide an upgrade path.

https://k8up.io/k8up/explanations/what-has-changed-in-v2.html

Alternatives
None

Discussion during backlog refinement: To provide an upgrade path where users have a period of time in which they can migrate their backups from v1.x to v2.0, we came up with the idea to run K8up 1.x and K8up 2.0 side-by-side for a couple weeks which should be possible without big issues since the CRDs are different for 1.x and 2.0.
This would mean that the component needs to be able to deploy K8up 1.x and 2.0 on a single cluster and needs to be able to produce both the K8up 1.x and K8up 2.0 custom resources in the component library.


How do I modify the font size of workspace, not editor？

I know how to modify the font of editor, but now i want to modify font size of workspace, for example explorer, console, and so on.

I am sorry, I found the zoomLevel can resolve my problem, so I close it now.


Make BeamRelNode take a PCollectionList always

This removes the variation in what PInput different BeamRelNode implementations expect. There is still variation in the size of the PCollectionList<Row> which basically corresponds to the same checks. But it eliminates the need for a BeamRelNode to need to override the method that builds its own inputs.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @apilloud
It isn't a net deletion because of added input validation and error messages.

And also I wanted to do the small change first. After this, since they have a uniform interface, all the BeamRelNode.Transform inner classes can be eliminated and replaced with a single BeamSqlRelUtils.Transform inner class whose expand() method calls BeamRelNode.implement that does not manage the transform encapsulation.

Thanks!


DSA <IP_ADDRESS> Array Rotation some O(N) problems

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #452

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] DSA

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

OK I will add it soon!

is this alright @Subhradeep10 ?

@arjyo851 Perfect