error: docker exporter does not currently support exporting manifest lists

got error after assemble docker-image:
prometheus-speedtest-exporter# ./build.sh
//output:
++ echo linux/amd64,linux/arm/v6,linux/arm/v7,linux/arm64/v8

docker buildx build --file Dockerfile --platform linux/amd64,linux/arm/v6,linux/arm/v7,linux/arm64/v8 --label=built-by=billimek --label=build-type=manual --label=built-on=ubuntu2004.localdomain --tag billimek/prometheus-speedtest-exporter:latest --load .
[+] Building 0.0s (0/0)
error: docker exporter does not currently support exporting manifest lists

The same error on my side:
docker buildx build --load --progress=plain --platform linux/amd64 --platform linux/arm64 -t <image-tag> .

error: docker exporter does not currently support exporting manifest lists

Docker version:
$ docker --version

Docker version 20.10.10, build b485636f4b

I know this issue is about a year old, but it may be due to the fact that the local docker client wasn't configured to use the experimental settings to allow multi-arch builds?
(looking at this issue)


how to start the app?

@ThorstenHans how do we start the electron app after having unzipped the file?
Could you update the readme accordingly?

It's funny I was struggling with this issue quite at the same time. :-)
The problem is the contradiction in the readme vs. the Gulpfile.js vs. index.js, and I have cut the knot like this:

Correct browser/config.js as depcited in the accompanying article.
Copy the contents of app/renderer into app/browser
Change target "copy:app" in Gulpfile.js to copy from 'browser//*' instead of 'renderer//*' in the gulp.src() call. Then after the next gulp run and extraction of the zip the app starts as intended.
Alternatively you could take the choice the other way round, i. e. set up jspm to live in app/renderer.
I hope these hints may help, but I will fork anyway to tailor the template to my needs, e. g. without the crash reporter which is an interesting plus but of minimal use for my case.

Nevertheless and not least I like to thank Thorsten for this groundwork, especially his blog post, which both have led me to the right direction.
Cheers [ofi]

@ofi could you apply those changes directly into the code? To be honest I hoped to have a quick view on the work of @ThorstenHans and nothing more.
Thank you for your time, I'll perform the tasks if I really want to see the result.

Meanwhile I have forked the repo which you can find under the same name in my account.  Good luck!

@ofi send a pull req.

Ok, this will happen within two days, as soon as I get back to my home machine.

:+1:

Thanks Dude!


Clean up and doc the test.runWith*() functions

def run(notebook, rules=None, filename=None):
    nb = nbformat.read(notebook, 4)
    name = filename or notebook[:-6] + '_test.py'  # remove .ipynb, replace with _test.py
    [... generate test file...]
    return name

def runWithReturn(notebook, executable=None, rules=None):
    name = run([...])
    executable = executable or [sys.executable, '-m', 'pytest', '-v']
    argv = executable + [name]
    return subprocess.check_output(argv)

def runWithReport(notebook, executable=None, rules=None, collect_only=False):
    tmpd = tempfile.mkdtemp()
    py_file = os.path.join(tmpd, os.path.basename(notebook).replace('.ipynb', '.py'))
    json_file = os.path.join(tmpd, os.path.basename(notebook).replace('.ipynb', '.json'))
    _ = run(notebook, filename=py_file, rules=rules)
    ret = []
    [...run with ?coverage and collect results - TODO: read this code and see...]
    return ret

def runWithHTMLReturn(notebook, executable=None, rules=None):
    '''use pytest self contained html'''
    name = run(notebook, rules=rules)
    html = name.replace('.py', '.html')
    executable = executable or [sys.executable, '-m', 'pytest', '-v']
    argv = executable + ['--html=' + html, '--self-contained-html', name]
    subprocess.call(argv)
    with open(html, 'r', encoding='utf-8') as fp:
        return fp.read()

def runWithHTMLReturn2(notebook, executable=None, rules=None):
    '''use custom return objects'''
    ret = ''
    executable = executable or [sys.executable, '-m', 'pytest', '-v']
    ret_tmp = run(notebook, rules=rules)
    for test in ret_tmp:
        test = test.to_html()
        ret += '
' + test + '
'
    return '
' + test + '
'

Notes:

runWithHTMLReturn() works fine.
runWithHTMLReturn2() does nothing (doesn't actually run any tests - bug). Is it used? Seems not.
runWithReport() not quite working (see #126) and still undocumented.
runWithReturn() works fine.
run() does no running :) Should be generate_test_script() or something like that.

python -m nbcelltests.test ... does not actually use any of the run functions, but most likely should.


How to get offline information

How to get offline information, I tested and found that Qos1 is also offline after reconnecting for a period of time, but no offline data is obtained.

What do you mean by "no offline data is obtained"?

I still don't understand what is the point here. I will close this issue now. If you can specify the question a bit more, I will try to answer your question and open this issue again. Maybe also https://github.com/chkr1011/MQTTnet/issues/846 goes in this direction?


Make sure the build-docs workflow runs on pull requests and pushes to the specification-1.0 branch

I thought #546 would do it, but that appears not to be enough.

I still want to avoid starting a 10-minute conversation about whether a branch for the docs is worth the effort, but just in case you eventually conclude that those 10 minutes might save you an hour of tearing out your hair... :)

There's a solid chance that no one outside the current group gives the spec more than a cursory review during the month we're updating it. So even if it were to go out of sync in a confusing way, it might not affect anyone.

If anyone pays attention, it might be to the commit history in the main branch, in which case raw activity there might be a good thing :)

I expect the individual PRs we make to be independent, like how updating the package name is independent of substitution or applicable locations. So I don't expect confusion to result.

If anything, I think that every case in which we update the main-branch spec is a chance to avoid confusion that has resulted from differences between the spec and the Javadoc / User Guide.

If readers really want the 0.2 version of the spec, they can get it at https://github.com/jspecify/jspecify/blob/9abe30d9ded9a088cca97bf2ce79aad603420484/docs/docs/spec.md (with, admittedly, minor rendering hiccups). We could even link directly there if we want.
If the problem ends up being specifically with branches but we still want to leave the old spec in place, we could consider making a copy of the file in the main branch and iterating on that. (We presumably won't be editing the old spec until it's time to merge, so that shouldn't lead to any merge conflicts.)
If we do want a branch, my guess is that we could live without doc generation until it's time to merge. We'd just have to review carefully then, especially for links.

(But I do hope it's just an easy fix :))

I think the workflow change just has to be on the development branch.


bump factory boy and use the DjangoModelFactory

Currently the factory is outdated and therefore cannot be used in tests within projects that have more recent versions of factory boy.

:shipit:


Split the sessions UI out into its own page.

Previously, the tree UI included two unrelated views; a directory
view of the file system, and a list view of running sessions.
This was confusing as it was not intuitive that you should open
the file listing in order to be able to switch to the session
list, nor was it obvious that the UI controls on that page
toggled the type of view that was presented.
This change tries to clean all of that up by splitting the
session listing into its own page, and putting a link to that
page in the button toolbar that is in the top, right-hand
corner of the UI.

LGTM! A minor comment that can be addressed separately.


2.0 wip

Added the ability to properly destroy a tooltip.

if you use jquery to destroy an element, all the events will be removed for free

hm... actually, read that wrong - i'll take a closer look at this later. thanks!

I wrote this method in order to be able to re-create tooltip with other parameters (e.g. template, placement ...) without recreating the actual html-item.

Just a heads up: this is for the 2.0-wip branch. Be sure to add it to master when you guys are set.


Diagonalize rules

Currently, when the first rule does not terminate, the other rules do not expand.
Diagonalization means that one iterates using breath-first search.

This required an update to monotonic solver: https://github.com/advancedresearch/monotonic_solver/issues/10


Page Text Images: Investigate the best way to maintain aspect ratios on About Us images

We have the Page Text resource that allows org staff to upload a hero image and two About Us images. Currently, if you upload two About Us images of different aspect ratios, they will not render in the same dimensions on the org root page. For example, below.

If both images are the same aspect ratio, they both show as the same size:

Investigate an appropriate way to manage the aspect ratios of uploaded images. If we don't have to use a gem, great. But we can use a gem if there are no other options.
Acceptance criteria:

staff can upload images without worrying about aspect ratios and both images appear the same size on the org root page.
No need for tests

@kasugaijin , what are the steps to reproduce this one? In local environment the About page is quite different

@Hassaan68 so this is on the Org's home page, there is an about us section. You can ignore /about_us page.
Log in as a staff, go to the dashboard, go to Page Texts, make some changes and upload images, save, then go back to that Org's home page and scroll the About Us section.
Let me know if you have more questions!

I think the simplest solution would be to use bootstrap ratio and style: "object-fit: cover;" so the image fills the space.
I pushed a branch up if you want to play around with it. Not sure if this what you had it mind.
https://github.com/rubyforgood/pet-rescue/tree/jmilljr24/investigate-image-aspect-ratios

Awesome thanks @jmilljr24 i will test it out. I think CSS should be all we need!

The aspect ratios are not actually maintained (they get cropped which might be annoying if you don't have a lot of room around the focal point of the image), but the images end up the same size, which is better than current. I prefer keeping it simple for now and not adding more gems that we need. So, let's roll with this, and if we hear frustration with this from user feedback we can fix it. Can you please make a PR if you agree?

I can make a PR for this. I think it's a good baseline to at least keep the layout from looking odd. Worst case staff will have to try a couple different photos to see what looks best.
Maybe we can talk a little more about it at the next meeting. I started typing an essay but it would be easier to talk about.

@jmilljr24 agreed! Sounds good.


Selecting Row & Information

Firstly, I'd like to say thank you for such a wonderful addition to data tables, this is exactly what I have been searching for!
I'd like to point you to a SO question I have raised regarding your plugin, hopefully this can not only provide me with answer to some information, but highlight your plugin too!
https://stackoverflow.com/questions/56488109/select-datatable-row-in-tree-table-plugin
This certainly isn't an "issue", but I'm struggling to execute a few of the data table functions using this plugin, hopefully you can point me in the right direction.
I need to select the row and trigger an event (in this example, providing an alert with the row's name and salary values). I need this to happen independently to expanding and collapsing the row, meaning that these are two seperate triggers (expanding and collapsing from the icon, and selecting the row from the rows contents).
Hope you can help me out!

Hi Scott, thanks for the feedback, I'm so happy you found it useful!
Actually the default behaviour here overrides the ability to select a row without triggering the expand/collapse event, I had overlooked that.
I think this is an "issue" and I'm happy to change the default behaviour to toggle rows only when clicking the icon. Will open a PR to fix this in the next day or so, thanks for pointing this out!


[dxgi] Metro Exodus: Enhanced edition multi GPU crash regression

Since commit https://github.com/doitsujin/dxvk/commit/83a294285e90c65554bc851c4d4a126aa15916a4 Metro Exodus: EE seems to crash right on startup on multi GPU systems.
The reason i believe it might be multi GPU only is because the issue goes away when i either force select my RX 6800 through MESA_VK_DEVICE_SELECT=1002:73bf MESA_VK_DEVICE_SELECT_FORCE_DEFAULT_DEVICE=1 or DXVK_FILTER_DEVICE_NAME=6800
A extra note that i don't know is relevant to the issue or not is that both my GPUs support ray tracing which the game requires.
Software information
Metro Exodus: Enhanced edition
If not using Bleeding Edge or master vkd3d-proton VKD3D_CONFIG=dxr is needed to launch the game as it requires ray tracing. Using radv below version 23.2.1 will also need RADV_PERFTEST=rt
System information

GPUs: RX 6800 and Zen4 rdna2 iGPU
Monitors: Single monitor through displayport on RX 6800
DE: KDE Wayland / X11 5.27.9
Driver: Days old mesa main
Wine version: Proton Experimental
DXVK version: https://github.com/doitsujin/dxvk/commit/83a294285e90c65554bc851c4d4a126aa15916a4 and up

Log files
Proton log, xrandr output and game log
steam-1449560.log
xrandr.txt
metroexodus.log
Possible lines of interest from Proton log
18522.785:0124:0128:info:vkd3d-proton:dxgi_vk_swap_chain_init: Creating swapchain (1920 x 1080), BufferCount = 2.
18522.785:0124:0128:warn:vkd3d-proton:d3d12_resource_validate_desc: Invalid format 0.
err:   DXGI: CreateSwapChainForHwnd: Failed to create swap chain, hr -2147024809

Log with extra logging. Made on X11
steam-1449560-extra-logging.log
Extra test scenarios:
Primary monitor displayport moved to iGPU (motherboard) instead of dGPU. Issue still occurs.
Primary monitor connected to dGPU displayport and secondary monitor added plugged in to iGPU via HDMI. Issue still occurs.

After some more testing it actually seems like with the above commit the game behaves more like on native Windows. On Windows when the game is made to run on the iGPU it will crash at the same spot whereas dGPU works fine.
The more real issue seems to be that the game selects the iGPU by default on Linux no matter where the monitor is plugged in. On Windows the dGPU is selected by default when my monitor is connected to it. This is both in Power Saving and High Performance mode and i have to force the iGPU to be selected specifically if want to use it (where it then crashes). Switching the displayport cable to the motherboard switches the GPU selected in both power modes to the iGPU.

So I think it is clear now. The game selects which GPU it wants to use ignoring dxgi outputs binding to adapters. Then it crashes (on Windows as well) if selected GPU with dxgi adapter without dxgi outputs (@Blisto91 made it on Windows by either forcing iGPU for the game or replugging monitor from dGPU to iGPU output). The only difference is that on Win it selects dGPU while not on problematic setups on Linux it selects dGPU. I figured the game chooses GPU with more dedicated VRAM (as reported by IDXGIAdapter::GetDesc3) after dropping incompatible ones (lacking d3d12 features or having DXGI_ADAPTER_FLAG3_SOFTWARE flag). On Blisto's machine Linux has 16GB device local mem on dGPU and reported 20GB on iGPU. on Windows (through dxgi) it is 16GB / 500MB.
So it is a game bug all around the place, if we want to do anything with it it can only be made through some game specific workaround (easiest is probably setting DXGI_ADAPTER_FLAG3_SOFTWARE for iGPUs for the game or just skipping the iGPU from enumeration). The alternative would be to have dedicated memory capped for iGPUs, but I am not sure it won't break more than fix.


fix absolute vs relative path issue with status on windows

bug was caused by using path.* instead of filepath.*


Add missing function fix_format_for_duration_arithmetic

Add this into operations.py
    def format_for_duration_arithmetic(self, sql):
        # https://clickhouse.com/docs/en/sql-reference/data-types/special-data-types/interval
        return "INTERVAL %s MICROSECOND" % sql

Without it our project crashing.
And may be you could enable PRs? Planned to create PR but they are disabled.

You can folllow this thread to open a PR. https://github.com/orgs/community/discussions/22665

Anyway, can you create an issue about the problem your project faced.
Interval of clickhouse is a special type, so you can not use DurationField in you project.
I am interested in what caused the problem.


Error: unauthorized_client on trying to list files from Google Drive

Expected Behavior
List the files on google drive
Actual Behavior
Getting error :: The API returned an error: Error: unauthorized_client
Steps to Reproduce the Problem
Execute the below code
const fs = require('fs');
const readline = require('readline');
const {
	google
} = require('googleapis');

// If modifying these scopes, delete token.json.
const SCOPES = ['https://www.googleapis.com/auth/drive.metadata.readonly'];
// The file token.json stores the user's access and refresh tokens, and is
// created automatically when the authorization flow completes for the first
// time.
const TOKEN_PATH = 'token.json';

// Load client secrets from a local file.
fs.readFile('credentialsDrive.json', (err, content) => {
	if (err) return console.log('Error loading client secret file:', err);
	// Authorize a client with credentials, then call the Google Drive API.
	authorize(JSON.parse(content), listFiles);
});

/**
 * Create an OAuth2 client with the given credentials, and then execute the
 * given callback function.
 * @param {Object} credentials The authorization client credentials.
 * @param {function} callback The callback to call with the authorized client.
 */
function authorize(credentials, callback) {
	const {
		client_secret,
		client_id,
		redirect_uris
	} = credentials.installed;
	const oAuth2Client = new google.auth.OAuth2(
		client_id, client_secret, redirect_uris[0]);

	// Check if we have previously stored a token.
	fs.readFile(TOKEN_PATH, (err, token) => {
		if (err) return getAccessToken(oAuth2Client, callback);
		oAuth2Client.setCredentials(JSON.parse(token));
		callback(oAuth2Client);
	});
}

/**
 * Get and store new token after prompting for user authorization, and then
 * execute the given callback with the authorized OAuth2 client.
 * @param {google.auth.OAuth2} oAuth2Client The OAuth2 client to get token for.
 * @param {getEventsCallback} callback The callback for the authorized client.
 */
function getAccessToken(oAuth2Client, callback) {
	const authUrl = oAuth2Client.generateAuthUrl({
		access_type: 'offline',
		scope: SCOPES,
	});
	console.log('Authorize this app by visiting this url:', authUrl);
	const rl = readline.createInterface({
		input: process.stdin,
		output: process.stdout,
	});
	rl.question('Enter the code from that page here: ', (code) => {
		rl.close();
		oAuth2Client.getToken(code, (err, token) => {
			if (err) return console.error('Error retrieving access token', err);
			oAuth2Client.setCredentials(token);
			// Store the token to disk for later program executions
			fs.writeFile(TOKEN_PATH, JSON.stringify(token), (err) => {
				if (err) console.error(err);
				console.log('Token stored to', TOKEN_PATH);
			});
			callback(oAuth2Client);
		});
	});
}

/**
 * Lists the names and IDs of up to 10 files.
 * @param {google.auth.OAuth2} auth An authorized OAuth2 client.
 */
function listFiles(auth) {
	const drive = google.drive({
		version: 'v3',
		auth
	});
	drive.files.list({
		pageSize: 10,
		fields: 'nextPageToken, files(id, name)',
	}, (err, res) => {
		if (err) return console.log('The API returned an error: ' + a);
		const files = res.data.files;
		if (files.length) {
			console.log('Files:');
			files.map((file) => {
				console.log(`${file.name} (${file.id})`);
			});
		} else {
			console.log('No files found.');
		}
	});
}

Specifications

Node version (node -v)
OS (Mac/Linux/Windows)

I believe this error indicates that you are trying to refresh an access token using a different client ID then was used to create it. Try deleting your token.json file and trying again.

Was having similar issue: was getting 'Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup.'
What worked :
In listFiles(), change
const drive = google.drive({version: 'v3', auth})
to
const drive = google.drive({version: 'v3', auth: auth})

Closing this issue, as I think I identified the cause in https://github.com/gsuitedevs/node-samples/issues/42#issuecomment-438310048. Let me know if you tried that solution and still experience an issue.


 See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
[10:24:18] npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
[10:24:18] npm WARN deprecated<EMAIL_ADDRESS>See https://github.com/lydell/source-map-resolve#deprecated
[10:24:18] npm WARN deprecated<EMAIL_ADDRESS>some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
[10:24:18] npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
[10:24:18] npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
[10:24:23] npm WARN deprecated<EMAIL_ADDRESS>This is a stub types definition. tailwindcss provides its own type definitions, so you do not need this installed.
[10:24:27] npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
[10:24:27] npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
[10:24:36] npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
[10:24:36] npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js-pure.
[10:24:38]
[10:24:38] ><EMAIL_ADDRESS>prepare
[10:24:38] > husky install && if [ -f codegen.yml ] && [ -f build-utils/generate-theme.mjs ]; then npm run setup; fi
[10:24:38]
[10:24:38] husky - Git hooks installed
[10:24:39]
[10:24:39] ><EMAIL_ADDRESS>setup
[10:24:39] > npm run sync && npm run graphql:generate && npm run theme:generate
[10:24:39]
[10:24:39]
[10:24:39] ><EMAIL_ADDRESS>sync
[10:24:39] > set -a && if [ -f .env ]; then source .env; fi && npm run sync:defaults && npm run sync:content-blocks && npm run sync:editor
[10:24:39]
[10:24:39]
[10:24:39] ><EMAIL_ADDRESS>sync:defaults
[10:24:39] > swell storefront settings push settings -f ./config/defaults.json --strategy "defaults" --store $SWELL_STORE_ID --secret-key $SWELL_SECRET_KEY
[10:24:39]
[10:24:40] - Pushing settings
[10:24:41] ✔ Successfully updated settings to teess store.
[10:24:42]
[10:24:42] ><EMAIL_ADDRESS>sync:content-blocks
[10:24:42] > ls ./config/content/*.json | xargs -L 1 swell model push --store $SWELL_STORE_ID --secret-key $SWELL_SECRET_KEY --strategy "merge" --content -f
[10:24:42]
[10:24:42] - Pushing Categories Preview model.
[10:24:43] ✔ Successfully pushed theme.horizon.categories_preview model to teess store.
[10:24:43] - Pushing Category list page model.
[10:24:44] ✔ Successfully pushed theme.horizon.category model to teess store.
[10:24:44] - Pushing Divider model.
[10:24:46] ✔ Successfully pushed theme.horizon.divider model to teess store.
[10:24:46] - Pushing Full width media model.
[10:24:47] ✔ Successfully pushed theme.horizon.full_width_media model to teess store.
[10:24:48] - Pushing Heading with text model.
[10:24:49] ✔ Successfully pushed theme.horizon.heading_with_text model to teess store.
[10:24:49] - Pushing Memberships model.
[10:24:50] ✔ Successfully pushed theme.horizon.memberships model to teess store.
[10:24:50] - Pushing Multiple features model.
[10:24:51] ✔ Successfully pushed theme.horizon.multiple_features model to teess store.
[10:24:51] - Pushing Multiple panels model.
[10:24:52] ✔ Successfully pushed theme.horizon.multiple_panels model to teess store.
[10:24:52] - Pushing Page model.
[10:24:54] ✔ Successfully pushed theme.horizon.page model to teess store.
[10:24:54] - Pushing Press mentions carousel model.
[10:24:55] ✔ Successfully pushed theme.horizon.press_mentions_carousel model to teess store.
[10:24:55] - Pushing Product detail page model.
[10:24:57] ✔ Successfully pushed theme.horizon.product model to teess store.
[10:24:57] - Pushing Products preview model.
[10:24:58] ✔ Successfully pushed theme.horizon.products_preview model to teess store.
[10:24:58] - Pushing Quiz model.
[10:25:01] ✔ Successfully pushed theme.horizon.quiz model to teess store.
[10:25:01] - Pushing Question page model.
[10:25:02] ✔ Successfully pushed theme.horizon.quiz_question model to teess store.
[10:25:02] - Pushing Transition page model.
[10:25:03] ✔ Successfully pushed theme.horizon.quiz_transition model to teess store.
[10:25:03] - Pushing Customer reviews model.
[10:25:04] ✔ Successfully pushed theme.horizon.reviews model to teess store.
[10:25:04]
[10:25:04] ><EMAIL_ADDRESS>sync:editor
[10:25:04] > swell storefront settings push editor -f config/editor.json --strategy "merge" --store $SWELL_STORE_ID --secret-key $SWELL_SECRET_KEY
[10:25:04]
[10:25:05] - Pushing editor settings
[10:25:06] ✔ Successfully updated editor settings to teess store.
[10:25:07]
[10:25:07] ><EMAIL_ADDRESS>graphql:generate
[10:25:07] > graphql-codegen --config codegen.yml -r dotenv/config
[10:25:07]
[10:25:08] [STARTED] Parse Configuration
[10:25:08] [SUCCESS] Parse Configuration
[10:25:08] [STARTED] Generate outputs
[10:25:08] [STARTED] Generate to ./graphql.schema.json
[10:25:08] [STARTED] Generate to lib/graphql/generated/sdk.ts
[10:25:08] [STARTED] Load GraphQL schemas
[10:25:08] [STARTED] Load GraphQL schemas
[10:25:11] [FAILED]
[10:25:11] [FAILED]         Failed to load schema from https://teess--dev.swell.store//graphql:
[10:25:11] [FAILED]
[10:25:11] [FAILED]         Must provide query string.
[10:25:11] [FAILED]         GraphQLError: Must provide query string.
[10:25:11] [FAILED]     at createGraphQLError (/vercel/path0/node_modules/@graphql-tools/wrap/node_modules/@graphql-tools/utils/cjs/errors.js:9:12)
[10:25:11] [FAILED]     at /vercel/path0/node_modules/@graphql-tools/wrap/cjs/introspect.js:13:102
[10:25:11] [FAILED]     at Array.map ()
[10:25:11] [FAILED]     at getSchemaFromIntrospection (/vercel/path0/node_modules/@graphql-tools/wrap/cjs/introspect.js:13:58)
[10:25:11] [FAILED]     at /vercel/path0/node_modules/@graphql-tools/wrap/cjs/introspect.js:36:32
[10:25:11] [FAILED]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[10:25:11] [FAILED]     at async UrlLoader.load (/vercel/path0/node_modules/@graphql-tools/url-loader/cjs/index.js:211:29)
[10:25:11] [FAILED]     at async /vercel/path0/node_modules/@graphql-tools/load/cjs/load-typedefs/load-file.js:17:39
[10:25:11] [FAILED]     at async Promise.all (index 5)
[10:25:11] [FAILED]     at async loadFile (/vercel/path0/node_modules/@graphql-tools/load/cjs/load-typedefs/load-file.js:15:9)
[10:25:11] [FAILED]
[10:25:11] [FAILED]         GraphQL Code Generator supports:
[10:25:11] [FAILED]           - ES Modules and CommonJS exports (export as default or named export "schema")
[10:25:11] [FAILED]           - Introspection JSON File
[10:25:11] [FAILED]           - URL of GraphQL endpoint
[10:25:11] [FAILED]           - Multiple files with type definitions (glob expression)
[10:25:11] [FAILED]           - String in config file
[10:25:11] [FAILED]
[10:25:11] [FAILED]         Try to use one of above options and run codegen again.
[10:25:11] [FAILED]
[10:25:11] [FAILED]
[10:25:11] [FAILED]
[10:25:11] [FAILED]         Failed to load schema from https://teess--dev.swell.store//graphql:
[10:25:11] [FAILED]
[10:25:11] [FAILED]         Must provide query string.
[10:25:11] [FAILED]         GraphQLError: Must provide query string.
[10:25:11] [FAILED]     at createGraphQLError (/vercel/path0/node_modules/@graphql-tools/wrap/node_modules/@graphql-tools/utils/cjs/errors.js:9:12)
[10:25:11] [FAILED]     at /vercel/path0/node_modules/@graphql-tools/wrap/cjs/introspect.js:13:102
[10:25:11] [FAILED]     at Array.map ()
[10:25:11] [FAILED]     at getSchemaFromIntrospection (/vercel/path0/node_modules/@graphql-tools/wrap/cjs/introspect.js:13:58)
[10:25:11] [FAILED]     at /vercel/path0/node_modules/@graphql-tools/wrap/cjs/introspect.js:36:32
[10:25:11] [FAILED]     at processTicksAndRejections (node:internal/process/task_queues:96:5)
[10:25:11] [FAILED]     at async UrlLoader.load (/vercel/path0/node_modules/@graphql-tools/url-loader/cjs/index.js:211:29)
[10:25:11] [FAILED]     at async /vercel/path0/node_modules/@graphql-tools/load/cjs/load-typedefs/load-file.js:17:39
[10:25:11] [FAILED]     at async Promise.all (index 5)
[10:25:11] [FAILED]     at async loadFile (/vercel/path0/node_modules/@graphql-tools/load/cjs/load-typedefs/load-file.js:15:9)
[10:25:11] [FAILED]
[10:25:11] [FAILED]         GraphQL Code Generator supports:
[10:25:11] [FAILED]           - ES Modules and CommonJS exports (export as default or named export "schema")
[10:25:11] [FAILED]           - Introspection JSON File
[10:25:11] [FAILED]           - URL of GraphQL endpoint
[10:25:11] [FAILED]           - Multiple files with type definitions (glob expression)
[10:25:11] [FAILED]           - String in config file
[10:25:11] [FAILED]
[10:25:11] [FAILED]         Try to use one of above options and run codegen again.
[10:25:11] [FAILED]
[10:25:11] [FAILED]
[10:25:11] [SUCCESS] Generate outputs
[10:25:11] npm ERR! code 1
[10:25:11] npm ERR! path /vercel/path0
[10:25:11] npm ERR! command failed
[10:25:11] npm ERR! command sh -c -- husky install && if [ -f codegen.yml ] && [ -f build-utils/generate-theme.mjs ]; then npm run setup; fi
[10:25:11]
[10:25:11] npm ERR!


[issue][elasticsearch] - allow upgrade statefullset even if currently upgrade

Allow upgrade the current statefullset  being upgraded. It avoid to break all when pod can't start because of bad setting. We can't fix settings ...
The only way is to delete statefullset

It fix


Python 3 issues

Hey,
I'm trying to port my module to python 3 and i have a problem to use it.
Here is the travis report.
The error is
"""
data = ' graph {\n    graph [rankdir=LR];\n    node [label="\N",\n        shape=plaintext\n    ];\n    edge [color=gray50,\n...T>>];\n"child" -- "parent" [taillabel=<{0,1}>,headlabel=<0..N>];\n}'
def parse_dot_data(data):
    global top_graphs

    top_graphs = list()

  if data.startswith(codecs.BOM_UTF8):

E       TypeError: startswith first arg must be str or a tuple of str, not bytes
"""
Do you have any idea?

pydot >= 1.2.0 supports Python 3: https://github.com/erocarrera/pydot/issues/76.

It looks like pydot-1.0.29 installation is broken again with pip and python 3.  I get:
Downloading pydot-1.0.29.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-qom6ktm8/pydot/setup.py", line 6, in <module>
        import pydot
      File "/tmp/pip-build-qom6ktm8/pydot/pydot.py", line 31
        except Exception, e:
                        ^
    SyntaxError: invalid syntax

As I wrote above, pydot >= 1.2.0 supports Python 3. Version 1.0.29 < 1.2.0. The latest version is 1.2.3, and I would be surprised if it doesn't work with Python 3, because it is tested with Python 3.5. on Tavis CI.

OK thanks, I think I was confused by the release date of 1.0.29 on PyPI being listed as 2016-05-17 so I figured it was a newer release that should have been compatible with python3


make sure to get most up-to-date datapoint

this PR fixes two bugs

inconsistent metrics with every scrape
broken scraping when addCloudwatchTimestamp and nilToZero are set, and no metrics return

Thanks a lot! Will review on Friday.


Add/enable iOS simulator tests

We recently had some iOS simulator-only build failures (ref: flutter/engine#3364) that weren't caught by build/test bots.
There is a simulator launch test in flutter/flutter.py but it's currently commented out.

@yjbanov

We should do this, https://github.com/flutter/flutter/issues/7238 is also asking for this. It might be a little bit of work though. The device lab framework currently only understands "android" and "ios". It can't tell "ios physical device" from "ios simulator".

Yes, it is still relevant.


IDEA: New category "Mixed"

Hi! I think a good addition would be a mixed category. My proposition is removing Whatsapp and Linkedin from social and move them to this new category, maybe adding YouTube to this one. Or some sites like the AI ones with NSFW potential, but that would be far too mixed and would create new issues.
Reasoning
My reasons are that: a) Whatsapp is a instant messaging service b) Linkedin is also for job seeking. c) Could help with blocking sites that not all users agree in what category they fall.

Not that I have a say in any of this, but I feel compelled to interject my opinion; there are too many different opinions/ideas on what goes where and what justifies (in|ex)clusion to justify anything like this. Where would it begin and where would it end? This would be a jumbled mess. At the point where too many opinions are involved it is then up to the end-user to compile/(white|black)-list there own lists from the source list. You can write your own scripts. I personally might even write a universal script/program to strip|add items to the base file based on separate (in|ex)clusion lists files, but I don't think it's a good idea to start having countless "mixed" lists as countless it would probably end up being. Just my two cents...

Hi Elian @dev-elian-aav and thank you as always Ian @Lateralus138 for the assist.
Elian I have imaginary archetypal users for each of our lists.
For the social media lists, my archetypes have two flavors:

People with social media addictions who want a reliable way to block social media temptations.
Parents who feel compelled to protect their kids from the internet, or prevent certain facets of the internet from entering their homes.

I think drawing fuzzy lines just leads to problems. These archetypes help to keep the lines sane and consistent.
Nonetheless, thank you for your views on this. I think your views are valid, but the day-to-day implementation is, in my experience, problematic.
Closing.

Thanks @StevenBlack & @Lateralus138 for your responses. I agree this idea would bring new problems, I will follow @Lateralus138 advice on writing my own scripts for solving this issue. Have a good day!


[Tabs] Scroll by width of the first visible tab if only one tab is partially visible

[x] I have followed (at least) the PR section of the contributing guide.

Currently, you're not able to scroll tabs when the container is narrow enough to have only one tab (partially) visible. This is my proposed solution, which would scroll by the width of the first visible tab in such a case.
Fixes https://github.com/mui/material-ui/issues/32748

@mnajdova Thanks for the review. The test I added in Tabs.test.js should already cover this case 😄


Trim down docker image size

Signed-off-by: Joe Grund<EMAIL_ADDRESS>

I wonder if it could be possible to use white listing instead of black listing (.dockerignore).

It looks like * followed by a number of !... lines can be used to simulate whitelisting.

I think for now we can stick to a blacklist as this is basically working.

What are the numbers before and after?

I'll post after it publishes to docker-hub, but I think it was ~ 80MB.


openwrt: Fix wifi leds for ecw5211 wf610d eap102

Fix typo error for ecw5211 and eap102, correct
boardname for wf610d
Signed-off-by: Chaitanya Godavarthi<EMAIL_ADDRESS>

Merged, thank you.


[FEATURE] Bigquery pseudo-column support

It would be good to be able to use the _FILE_NAME pseudo-column which bigquery uses to hold the filename of the files in an external table.
Describe the solution you'd like
To do this, it would need to be selected in the initial stage select CTE, because it is unavailable after that, ie. when derived columns are added. Presumably the best way to do that is to create a macros/tables/bigquery/stage.sql file with an "external_table_filename" kwarg flag, or if this could be covered with a src_extra_columns variable? There are other pseudo-columns too such as in partitioned tables.
Describe alternatives you've considered
Additional context
Happy to work on this if it seems appropriate

Hi! Thanks for this interesting feature request.
I have to admit I don't know much about this bit of BigQuery.
My questions would be: is this something that should be dealt with in dbtvault or is it in fact already built into dbt? From the BigQuery dbt configs documentation it does allude to pseudo-columns.
Otherwise, this should already be possible doing something like the following:

WITH stage AS (
   {{ dbtvault.stage() }}
),

pseudocolumns AS (
   SELECT *, _FILE_NAME AS FILE_NAME
   FROM stage
)

SELECT * FROM pseudocolumns

Hi. The problem as I see it there (and I am not an expert on dbt-vault or dbt-bigquery or how they interact) is that _FILE_NAME can only be selected directly from the source table, if it is not included in the initial CTE then it will be unavailable going forward. It will also require an alias ie. 'FILE_NAME'.
dbt-vault provides a file called dbtvault/macros/staging/stage.sql which I believe is what dbt-vault runs when dbtvault.stage() is called, and the _FILE_NAME needs to be inserted right there at the source.
WITH source_data AS (

    SELECT

    {{- "\n\n    " ~ dbtvault.print_list(list_to_print=all_source_columns, columns_to_escape=columns_to_escape) if all_source_columns else " *" }}
  , _FILE_NAME AS FILE_NAME -- <- we need this line optionally
    FROM {{ source_relation }}
    {%- set last_cte = "source_data" %}
)

I can have a go at a PR

Ok that makes sense, thanks for explaining!
I will add this to our backlog :) Happy for you to do a PR but at this time we cannot accept directly as our test harness is not publicly available and it does need to be run through that before release. We hope to improve contribution guidelines and processes in future.


fix error for https://github.com/HyperDbg/gui/blob/main/sdk/bindgen/m…

…erged_headers.h

Hi, I'm not sure if I'm understanding correctly, in using the library to bind glfw 3.5, zydis 4.1, hyperdbg dev, I found the following bugs.

from zydis 4.1 it can be noticed that types seem to seem to need a map for de-duplication, otherwise multiple structures with duplicate definitions are generated.

from glfw 3.5 the node of function pointer type is not handled, he should be translated to function type with parameters as callback function.

the pr as I understand it correctly fixes the byte offset value of the bitfield field, but some checksums still fail to validate at initialization time. You can find this out from hyperdbg dev.

sometimes it will happen that the dll has obviously exported the api, but after binding it will prompt that the export function can't be found, it seems to happen randomly, it's very suspenseful.

Translated with DeepL.com (free version)

another pr need you check
https://github.com/zyantific/zydis-go/pull/3


Every terraform apply tries to remove and recreate the same record

This is the output of terraforming after each applies even if I did not change anything in my GoDaddy module: it simply removes and re-creates each record in my zone. I am not sure what went wrong, but I suspect this is not the expected behaviour.
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

 # module.final.module.godaddy.godaddy_domain_record.domain will be updated in-place
  ~ resource "godaddy_domain_record" "domain" {
        addresses = []
        domain    = "be-novative.dev"
        id        = "309310494"
     - record {
          - data     = "<IP_ADDRESS>" -> null
          - name     = "api-eu" -> null
          - port     = 0 -> null
          - priority = 0 -> null
          - ttl      = 3600 -> null
          - type     = "A" -> null
          - weight   = 0 -> null
        }
      + record {
          + data     = "<IP_ADDRESS>"
          + name     = "api-eu"
          + port     = 0
          + priority = 0
          + ttl      = 3600
          + type     = "A"
          + weight   = 0
        }

Can I anyhow fix this? Really annoys me.

I think that's the same I reported in #39 . Or rather, it's part of this.

@alexs77 indeed it is the same as #39.


reth-primitives crate import audit

Describe the feature
reth-primitives re-exports a ton of stuff.
we're making significant changes to primitive types and should do a cleanup pass first, shifting imports to the re-exported crates:

reth-primitive-traits (Account,Header..)
alloy-primitives

TODO

replace reth-primitive imports where possible

starting with

[ ] reth-trie (import from alloy-primitives directly) https://github.com/paradigmxyz/reth/blob/3ec5d373c10577efa3cbd4f313fafd68b15c728d/crates/trie/trie/Cargo.toml#L2-L2

Additional context
No response

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a python programmer and my skills and talents will be of great help in this project thank you
How I plan on tackling this issue
I can use Python programming to create the import aspect of this project

Hi, can I work on this?

marking this as completed now, I think we're good on this now


Non-GO terms prioritized in general search

I find this really annoying and not useful:
Is this intended?

The issue is that some GO terms are present in non-GO ontologies (like multicellular). It would be much clearer if non-GO terms were not indexed for the search.
Pascale

I was searching on multicellular which is a string in a GO term. I don't understand why the non GO terms are there...

queries such as: which genes are involved in processes related to B cells?
Or similar for chemical entities. But agree there is a tradeoff between
advanced used cases and keeping this simple and free of confusion. Suggest
product lead @ukemi takes this up, gathers some feedback and use cases +
comes up with recommendations
On Wed, Mar 13, 2019 at 4:55 AM Val Wood<EMAIL_ADDRESS>wrote:

I was searching on multicellular which is a string in a GO term. I don't
understand why the non GO terms are there...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/geneontology/amigo/issues/559#issuecomment-472334084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADGOdFCSHEBtWvooB_DU-AzlsMT9VeJks5vWL0VgaJpZM4brCRq
.

GOC meeting discussion topic?

queries such as: which genes are involved in processes related to B cells?

This would make sense if the terms were used in annotations displayed   in Amigo, but why UBEron, PAT aand phenotype ontilogies? You would not retrieve ny annotation.
I can see value for been able to search on cell type, tissue type of other ontology tets used in extensions? but they need to be used in extant annotations...

Looks like you're on a phone :-)
Uberon is used a lot in extensions, and also linked from existing GO processes. But there should not be any pheno ontologies in there.

GOC meeting discussion topic?

I'd rather not having too open ended and have one proposal or two alternate proposals specified in advance

How about only ontologies used in GO?

Oh yes sorry uberon is anatomy isn't it.
Would it be possible to restrict to terms that are used in extensions?

Two proposals: Restrict to only ontologies used in asserted relationships in the ontology
OR
Restrict to ontologies used in the ontology and annotation extensions.

OR 3
Restrict to ontologies and terms used in the ontology and annotation extensions.
Presumably, these are huge ontologies and only a small subset of terms are used in extensions. Obviously, you want to be able to search on any GO term, but is there any advantage to the user in being to find any term in an ontology that is used in extensions (the entirety of CHEBI?), if it isn't currently connected to a GO annotation in some way.  In the PomBAse website query builder, which is more about finding things than seeing every term, we only include the terms we have used in annotations.
Also, are you suggesting in 1 that all terms used in logical definitions are included? is this useful to the general user? We usually shield the user from this, it's complicated enough  already. How would the user benefit from the inclusion of these terms?

this behaviour affects searching really badly.
I also really dislike that I need to add a space to find an ontology term. If I type only "cell" I don't see any ontology terms, only gene products. I don't think many users would realise that they need to add a space?

This is a real problem. Sometimes I even land on a page and  don't notice it's not a GO term
http://amigo.geneontology.org/amigo/term/UBERON:0002405
It must be a real problem for users who most likely won't be paying attention to the IDs. Can we discuss at the GO meeting (I still don't fully understand what the use case is )

Same as #649
#582
#451

From the technical call and some other conversation threads, I'm noting here that:

for the ontology filtering approach, we'd need to be careful that and still need ncbitaxon and eco; we might be able to drop cl, uberon, and pato; I'll add this to the managers' call
since the issue seems to be focused on the "general" document search, it may be possible

check to make sure that the use of "general" is limited to amigo search
check to see if there is a filterable structure we could use in the general document
see how hard it would be to change the owltool loader to just filter for anything not "GO" (or anything else we want to keep)

TODO: We'll ask for an ontology to be built as an experiment and load it on a dev server for the the manages/others to check.


1.1.0 RC2, back arrow disappeared in token selection page

updates for RC3,
the back arrow appear on sell token selection page, but disappear on transfer token selection page
@JamesSmartCell


Refine parameter test vectors

Modified some values in test vectors with guide from EbEncHandle.c

change api offical checkout

close "set github commit status"

Already merged, close it.


python311Packages.aws-lambda-builders: 1.41.0 -> 1.42.0

Diff: https://github.com/awslabs/aws-lambda-builders/compare/refs/tags/v1.41.0...v1.42.0
Changelog: https://github.com/aws/aws-lambda-builders/releases/tag/v1.42.0
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

Priorities
Add a :+1: reaction to pull requests you find important.

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

10 packages built:

aws-sam-cli
aws-sam-cli.dist
python310Packages.aws-lambda-builders
python310Packages.aws-lambda-builders.dist
python310Packages.dsnap
python310Packages.dsnap.dist
python311Packages.aws-lambda-builders
python311Packages.aws-lambda-builders.dist
python311Packages.dsnap
python311Packages.dsnap.dist


CSS is leaking outside of its boundaries

Using the pydata-sphinx-theme in ipyleaflet, we now see that the theme CSS pollutes the map widget:
For example with this page: https://ipyleaflet.readthedocs.io/en/latest/layers/image_video_overlay.html
What we see:

What we should see:

Other artifacts are visible in other pages of our documentation.

I guess that's why I see a fine white line on my computer between the map tiles

I guess that's why I see a fine white line on my computer between the map tiles

I actually also see this since years even in https://leafletjs.com, nut not in all conditions. For example today I can reproduce this when the page is zoomed-in at 110% on Chrome (cannot reproduce on Firefox).
So I would say the fine white line is not coming from the pydata-sphinx-theme.


Remove Semantic Release.

Remove convention commit.
Remove semantic release.

Coverage remained the same at 100.0% when pulling e47930918da557ddf2cfdca758d019ca0bb92ffc on @feature/remove-semantic-release into 352ee318aff4eb0e536626e2cdb084d58ca94420 on master.


NACK, see https://github.com/kontena/pharos-cluster/issues/440#issuecomment-399014418 for why this workaround is a terrible idea, and https://github.com/kontena/pharos-cluster/pull/446 for a better alternative that actually fixes the issue.

Fixed in kubelet rpm package.


Auto discover column-names from origin

Auto discover column-names from origin (& remove the applicable config)

Done & released as part of 3.4.0 release. 3.x stable branch has the changes


Catch up AppNetCsm test with latest changes

#91, #95, #96, #97 should all be done to the AppNetCsm test as well, just that the test was merged after the fact.
Next step is to refactor out all the common logic into a Mixin class.

[ ] prod:grpc/core/master/linux/psm-csm

cc @ejona86 @zasweq @XuanWang-Amos


Fix pester tests syntax

PR Summary

Remove Unicode BOM from code files (#11546 was incomplete)
Insert final newline into code files, as per .vscode/settings.json
Fix #6265 (compare to [string]'null' instead of $null)
Mark failing CertificateProvider tests as pending (opened #11549)
Pass 'BeOfType' parameter as [RuntimeType] instead of [string]

PR Context

Follow-up to #11546

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None

User-facing changes

[x] Not Applicable

Testing - New and feature

[x] N/A or can only be tested interactively

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.

@iSazonov PR is ready to merge, CodeFactor issues are not new.

Pass 'BeOfType' parameter as [RuntimeType] instead of [string]

I don't changes related to this one are needed. -BeOfType takes a string as the type name, and this is how it's used in Pester's sample code.

@daxian-dbw Judging from BeOfType tests, it is intended for -BeOfType to take a RuntimeType as well as a string. Apparently this is a documentation issue for pester.
Passing a RuntimeType preferable because it is constructed in the scope of the test rather than a pester function.

Usually we use $p | Should -BeOfType [ActionPreference]

@iSazonov The parentheses are necessary for the parser to treat the token [ActionPreference] as an expression. Otherwise it is parsed as a string anyway:
$p | Should -BeOfType [ActionPreference]   # Fails

@xtqqczze I won't say either a RuntimeType or a string is preferable. Both are officially supported and both are useful. If you don't expect the type resolution to depend on anything from your script scope, then using a string is just fine. So I don't think it's necessary to change all -BeOfType instances to use a RuntimeType. We will not enforce this in our tests and gradually, it will again be a mix of both in our tests.


Using relative paths in stacks makes envs stop working

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
I have two stacks, identical in every way, except the fact that one has the uses relative paths.
The one with the paths is not able to load the ENV set in the UI.
They use the same docker-compose file, everything is the same, except the relative paths.
Expected Behavior
For the ENV vars to show
Actual Behavior
The ENV vars are not set
Steps to Reproduce

Create a stack from a git repo
Ensure the docker-compose.yml contains the stack.env defined
Ensure the file exists in the repo
Create ENV vars from the UI
turn on relative paths
Deploy

Portainer logs or screenshots

The logs show the env vars in there
2024/11/09 08:46PM INF github.com/portainer/portainer-ee/api/stacks/deployments/deployer_remote.go:261 > Stack deployment output | output="{\"level\":\"info\",\"repository\":\"https://github.com/thezoomlesss/HomeCloud\",\"composePath\":[\"docker-compose-prod.yml\"],\"destination\":\"/portainer-compose-unpacker\",\"env\":[\"VITE_APP_RESTAPI_URL=http://rpi4.local:9915\",\"FOO=BAR\",\"Test=ER\"],\"skipTLSVerify\":false,\"time\":1731185171,\"caller\":\"/home/runner/work/release/release/deploy.go:31\",\"message\":\"Deploying Compose stack from Git repository\"}\n{\"level\":\"info\",\"user\":\"thezoomlesss\",\"time\":1731185171,\"caller\":\"/home/runner/work/release/release/deploy.go:41\",\"message\":\"Using Git authentication\"}\n{\"level\":\"info\",\"directory\":\"/portainer-compose-unpacker\",\"time\":1731185171,\"caller\":\"/home/runner/work/release/release/deploy.go:56\",\"message\":\"Checking the file system...\"}\n{\"level\":\"info\",\"directory\":\"/portainer-compose-unpacker/stacks/homecloud-relative-path\",\"time\":1731185171,\"caller\":\"/home/runner/work/release/release/deploy.go:82\",\"message\":\"Creating target destination directory on disk\"}\n{\"level\":\"info\",\"repository\":\"https://github.com/thezoomlesss/HomeCloud\",\"path\":\"/portainer-compose-unpacker/stacks/homecloud-relative-path/HomeCloud\",\"url\":\"https://github.com/thezoomlesss/HomeCloud\",\"depth\":1,\"time\":1731185171,\"caller\":\"/home/runner/work/release/release/deploy.go:97\",\"message\":\"Cloning git repository\"}\n{\"level\":\"info\",\"composeFilePaths\":[\"/portainer-compose-unpacker/stacks/homecloud-relative-path/HomeCloud/docker-compose-prod.yml\"],\"workingDirectory\":\"/portainer-compose-unpacker/stacks/homecloud-relative-path/HomeCloud\",\"projectName\":\"homecloud-relative-path\",\"time\":1731185172,\"caller\":\"/home/runner/work/release/release/deploy.go:125\",\"message\":\"Deploying Compose stack\"}\n{\"level\":\"info\",\"time\":1731185179,\"caller\":\"/home/runner/go/pkg/mod/github.com/portainer/portainer/pkg/libstack@v0.0.0-20230831224222-4560a53317b0/compose/internal/composeplugin/composeplugin.go:48\",\"message\":\"Stack deployment successful\"}\n{\"level\":\"info\",\"time\":1731185179,\"caller\":\"/home/runner/work/release/release/deploy.go:143\",\"message\":\"Compose stack deployment complete\"}\n"
2024/11/09 08:46PM INF github.com/portainer/portainer-ee/api/docker/images/digest.go:58 > No environment registry credentials found, using anonymous access | image up to date indicator=docker.io/library/redis:alpine
2024/11/09 08:46PM INF github.com/portainer/portainer-ee/api/stacks/deployments/deployer_remote.go:261 > Stack deployment output | output="{\"level\":\"info\",\"repository\":\"https://github.com/thezoomlesss/HomeCloud\",\"composePath\":[\"docker-compose-prod.yml\"],\"destination\":\"/portainer-compose-unpacker\",\"env\":[\"VITE_APP_RESTAPI_URL=http://rpi4.local:9915\",\"FOO=BAR\",\"Test=ER\"],\"skipTLSVerify\":false,\"time\":1731185206,\"caller\":\"/home/runner/work/release/release/deploy.go:31\",\"message\":\"Deploying Compose stack from Git repository\"}\n{\"level\":\"info\",\"user\":\"thezoomlesss\",\"time\":1731185206,\"caller\":\"/home/runner/work/release/release/deploy.go:41\",\"message\":\"Using Git authentication\"}\n{\"level\":\"info\",\"directory\":\"/portainer-compose-unpacker\",\"time\":1731185206,\"caller\":\"/home/runner/work/release/release/deploy.go:56\",\"message\":\"Checking the file system...\"}\n{\"level\":\"info\",\"directory\":\"/portainer-compose-unpacker/stacks/homecloud-relative-path\",\"time\":1731185206,\"caller\":\"/home/runner/work/release/release/deploy.go:82\",\"message\":\"Creating target destination directory on disk\"}\n{\"level\":\"info\",\"repository\":\"https://github.com/thezoomlesss/HomeCloud\",\"path\":\"/portainer-compose-unpacker/stacks/homecloud-relative-path/HomeCloud\",\"url\":\"https://github.com/thezoomlesss/HomeCloud\",\"depth\":1,\"time\":1731185206,\"caller\":\"/home/runner/work/release/release/deploy.go:97\",\"message\":\"Cloning git repository\"}\n{\"level\":\"info\",\"composeFilePaths\":[\"/portainer-compose-unpacker/stacks/homecloud-relative-path/HomeCloud/docker-compose-prod.yml\"],\"workingDirectory\":\"/portainer-compose-unpacker/stacks/homecloud-relative-path/HomeCloud\",\"projectName\":\"homecloud-relative-path\",\"time\":1731185207,\"caller\":\"/home/runner/work/release/release/deploy.go:125\",\"message\":\"Deploying Compose stack\"}\n{\"level\":\"info\",\"time\":1731185207,\"caller\":\"/home/runner/work/release/release/deploy.go:143\",\"message\":\"Compose stack deployment complete\"}\n"

Portainer version
2.21.4
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker version 26.1.3, build b72abbb
OS and Architecture
ARM64
Browser
No response
What command did you use to deploy Portainer?
No response
Additional Information
No response

Update, I have had since 2 attempts to recreate the stacks and the final one somehow succeeded.
I am sure that there is still an issue with stack creation (the initial one, not running the stack), but it seems like I managed to get around it.

So, I am suspecting that the issue comes from the relative path in relation with the env: stack.env mention in docker-compose.yml.
Is there a known process or format for defining the stack.env in the compose file if relative paths are enabled?
I just retested with 2 other new stacks and the result is the same

I've just done a bunch of testing here and what I'm seeing is this:
With a stack created from a repo that includes a stack.env file and additional environment variables are set via the Portainer UI when deploying:

If relative path volumes are not enabled, the environment variables set in the Portainer UI are available within the stack's containers, but the environment variables within the stack.env file in the Git repository are not.

This is essentially expected behavior, as without relative path volumes enabled, Portainer only has access to the compose file in the repo and nothing else. The stack.env reference is a placeholder name so that you don't need to individually mention each environment variable explicitly in your compose file to include what you set through the Portainer UI.

If relative path volumes are enabled, the environment variables set in the Portainer UI are not available within the stack's containers, but the environment variables within the stack.env file in the Git repository are.

The expected behavior here is less clear. The existence of a stack.env file within the repo essentially conflicts with the placeholder name we're using in order to provide the UI-set environment variables to the stack's containers, and the file in the repo takes precedent. Ideally we'd merge the two somehow (and that was what I personally thought happened), but it seems like that's not how it works. Whether that's the intended behavior or not, I'm not sure - I'll need to raise it internally to clarify. This will also help to clarify whether the message we display in-app:

When deploying via Repository, the stack.env file must already reside in the Git repo.

is correct or not, as right now it doesn't appear to be.
In the meantime, a workaround might be to rename the stack.env file within your repo to something else - for example, simply .env - and reference it as well in your stack file (you can specify multiple env_file options):
env_file:
  - .env
  - stack.env

This way you would be able to include the environment variables set in the (newly renamed) .env file that is in your repo, as well as include those that are set in the UI via the use of the stack.env placeholder.


Update 'Edit' to 'Edit…' on entities context menu

Storage Explorer Version: 1.8.1_20190513.2
Platform/OS: Linux Ubuntu/macOS High Sierra/Windows 10
Architecture: ia32/x64
Commit: 41005d14
Regression From: Not a regression
Steps to reproduce:

Expand a storage account -> Tables -> Create a new table -> Add some entities to it.
Select one entity and check its context menu.

Expect Experience:
Show 'Edit...' on the context menu.
Actual Experience:
Show 'Edit' on the context menu.

Fix in PR

Fix merged into master.

Verified on master\20190610.4. This issue has been fixed, so we close it.


TS: AnyComponent has Problem

https://github.com/developit/preact-redux/blob/0b98ca39c40908a569bd84725d762af3a4a92fc5/src/preact-redux.d.ts#L23
AnyComponent may be ComponentConstructor in preact-redux.d.ts

8.3.0 just got released with the AnyComponent change. https://github.com/developit/preact/pull/1249
Do you think you could check to see if it's still an issue?


Need to extract all related Pipes and Valves to a HT

Parent issue: https://github.com/equinor/lighthouse-client/issues/1458
I need to show all related Pipes (not pipetests) and Valves to a HT, but currently i cant fetch this data.
Im not sure about the approach, so i think we need to have a meeting to talk around this. We probably should get help from @JoneUE aswell. I set up a meeting

Custom_:HeatTraceCableServiceCompletionTag ready in dev. Will be pushed to prod today.
Remeber to filter out for Register = "MANUAL_VALVE" and "PIPE_SUPPORT".
@atlewee  can you confirm is these are the correct type for valves and pipes?

CLosed as parent issue is on hold and not planned for JC


"Align parameters and components" doesn't work if a method call is on the same line as a WHEN or IF condition

Hi Jörg-Michael, the second method parameter in the following example isn't indented correctly:
    DATA example TYPE string.

    CASE example.
      WHEN 'when'. call_example( i_1 = 1
               i_2 = 2 ).
    ENDCASE.

I know that this style contradicts the Clean ABAP rule "No more than one statement per line", but I still think that the ABAP Cleaner should support this case correctly. 😉

It also seems to be the case for IF conditions:
    IF example = 'when'. call_example( i_1 = 1
               i_2 = 2 ).
    ENDIF.

After a discussion internally, we concluded that it is best to move the method call to a separate line. This problem is therefore obsolete.

Hi ConjuringCoffee,
that's nevertheless a nice finding – will be fixed with the next release!
Kind regards,
Jörg-Michael


Delete unnecessary spaces

When copying from the web page, there is an unnecessary space after the code.

@changeworld @Mikejo5000 - We're in the process of pulling this commit to the private repository so we can verify the updates on staging. We'll post a new private repo PR # shortly and then close this PR.

moved to https://github.com/MicrosoftDocs/visualstudio-docs-pr/pull/3906


Implement BulkApply()

This fixes #20.  It completes the implementation of BulkApply().  The implementation uses the existing policies to handle RPC errors, backoff from them, and to decide what operations are idempotent.  The PR is large, but mostly tests.

PTAL.  Apologies if I missed any comments.  @garye I think it is your turn now.


question regarding generation

Hi, thanks for the awesome paper
I was wondering if i can generate a molecule by inserting Zt(coordinates, atom types etc) instead of sampling Zt?

Hi, thank you for the compliment :). To answer your question possibly you could. It depends a bit on what you would want. I’ll give two examples;

You could for example insert an existing molecule at an early timestep (say for z_200, when the maximum is T=1000). The model would then refine the molecule.

Another option is to rewrite part of zt at each step during generation (for instance some/all positions in zt). Then the model could figure out the other stuff.

For these examples, it’s currently unknown how the model will act and so interesting research. Perhaps it is interesting to look at the paper where they show “SDEdit” which does something a bit related to this but on images.

Thank you for your kind response! I got interested in diffusion models from reading your paper.
I am new to this field, and don't know a lot. If i may ask one more question: can I know how equation 19 is derived from equation 16?

Thanks!!


Add missing badges & etc to README

I have tidied up the README - the following badges should be re-added if/when you

- [![Docker badge](https://img.shields.io/docker/pulls/ramp-eu/JS2SF.svg)](https://hub.docker.com/r/<org>/<repo>/)
- [![Build badge](https://img.shields.io/travis/ramp-eu/JS2SF.svg)](https://travis-ci.org/ramp-eu/TJS2SF/)
- [![Coverage Status](https://coveralls.io/repos/github/ramp-eu/JS2SF1/badge.svg?branch=master)](https://coveralls.io/github/ramp-eu/TTE.project1?branch=master)
- [![Codacy grade](https://img.shields.io/codacy/grade/99310c5c4332439197633912a99d2e3c)](https://app.codacy.com/manual/jason-fox/TTE.project1)

Obviously connecting the badges to your own  project rather than the dummy one.
The following items should also be updated
1 - The preferred license is APACHE - please replace and add your company name to the copyright holder
2 -  On the readme add your company name after the copyright symbol.
3 - The purpose of the component is unclear from the README, please amend the lede to better summarize what it does.

Done
Done
Title ia changed


How can I add additional repositories

I have several, unrelated repos for different projects.  Previously I've used Atlassian Source tree, GIT GUI and more recently GitHub desktop for a meta-view of them.  Is there a way to add additional repositories to GitLens?  Did I just miss something easy to do? e.g. in Github desktop I have:

And it has an "add" button to add more repos.  Can I do this with GitLens?

GitLens only shows the repositories that you have open in vscode, so there isn't a notion of adding a repository — you would just open the folder for the repository (or containing repositories) and they should all show up automatically.
Hope that helps.

ah yes, that worked!

@gbritton1 if you think this was helpful, consider adding a reward to this issue using speedoss.com to support the issue solver for their work :)


Fix reference for unknown type: application/octet-stream

Pr(#2814) haved supported application/octet-stream MediaType, And pr(#3870) haved missed this. we should add application/octet-stream MediaType back.
Fix: #4756
Additionally,
in containerd v1.3.4, crictl pull redis:2 is ok.
but in containerd v1.4.3, crictl pull redis:2 is error.

Change is LGTM, but application/octet-stream is not supported mediatype by OCI/Docker image spec (as mentioned in https://github.com/containerd/containerd/issues/4756#issuecomment-731287262).
So  I'm not sure we should support this MediaType.

Change is LGTM, but application/octet-stream is not supported mediatype by OCI/Docker image spec (as mentioned in #4756 (comment)).
So I'm not sure we should support this MediaType.

Can we continue to refer to pr (

Change is LGTM, but application/octet-stream is not supported mediatype by OCI/Docker image spec (as mentioned in #4756 (comment)).
So I'm not sure we should support this MediaType.

Can we continue to refer to pr https://github.com/containerd/containerd/pull/2814 ?

Surely there is not someone with a valid use case for redis:2 image? That version of redis was released 11 years ago; the supported versions of redis are versions like 6.2, 6.0, 5.0.. are there any example images using application/octet-stream that are less than several years old? Even just based on standard security image refresh practices, any image should have been repushed to a registry multiple times since clients have been fixed to use the proper media types already?
I think 3+ years ago it was fine to support this "legacy bug" use case given it was unclear if someone relied on an older image. I think in 2021 relying on an image pushed 5+ years ago is probably revealing a really poor security practice.

in the ole days 5+ years wasn't that old :-) Perhaps a config switch enable-octet-stream with some comments not recommended default is false... see legacy bug ___

in the ole days 5+ years wasn't that old :-)

Don't conflate old software with unsupported/unmaintained images and image health in general. The age of the software is not the issue; it's the fact that images pushed during the window where that bug existed (certain clients were using the wrong media type) are most likely fully unmaintained, with a strong potential that, if scanned, would return a long list of unpatched CVEs.
In the similar way that it's not that hard to make containerd less stringent about OCI distribution API compatibility, we can easily be way more lenient on accepted media types. However, I think we agree it's been better for all to force registries to make fixes rather than make our fetcher/pull code more lenient. In this case, I think it's better to cause people to re-think whether even having examples that use extremely old images are a good idea. It's clearly not an issue of having no alternative: you can create a one-liner Dockerfile with FROM redis:2, build it, and push it, and keep using redis:2 with containerd without even knowing how redis:2 was originally built. This prevents no one one from using very old images if there is a safe use case (unlikely) that absolutely depends on images created during that window of broken pushes.

images pushed during the window where that bug existed (certain clients were using the wrong media type) are most likely fully unmaintained, with a strong potential that, if scanned, would return a long list of unpatched CVEs.
In the similar way that it's not that hard to make containerd less stringent about OCI distribution API compatibility, we can easily be way more lenient on accepted media types. However, I think we agree it's been better for all to force registries to make fixes rather than make our fetcher/pull code more lenient. In this case, I think it's better to cause people to re-think whether even having examples that use extremely old images are a good idea. It's clearly not an issue of having no alternative: you can create a one-liner Dockerfile with FROM redis:2, build it, and push it, and keep using redis:2 with containerd without even knowing how redis:2 was originally built. This prevents no one one from using very old images if there is a safe use case (unlikely) that absolutely depends on images created during that window of broken pushes.

fair.. agree to hold the commit for now.  We can decide on options to address later, for example, if we get any further issue(s) opened with concrete reasons to enable.

We can accept a change which does the conversion in CRI for these images, just as we would for schema 1. We aren't going to accept a change though that treats these invalid images as valid in parts of the code which do processing on the image, such as unpack. We have chosen to be strict about how we process images, but have allowed some workarounds to convert older/broken images to valid oci/schema2 images. The best solution though is to use a valid image, and if you need these exact old broken images, fix them and push them to a registry yourself.

We can accept a change which does the conversion in CRI for these images, just as we would for schema 1. We aren't going to accept a change though that treats these invalid images as valid in parts of the code which do processing on the image, such as unpack. We have chosen to be strict about how we process images, but have allowed some workarounds to convert older/broken images to valid oci/schema2 images. The best solution though is to use a valid image, and if you need these exact old broken images, fix them and push them to a registry yourself.

ok, get it.


SO-4524: Allow searching by CodeType in concept search API

Codecov Report

Merging #727 (e8563f6) into 7.x (67f3a66) will decrease coverage by 0.00%.
The diff coverage is 20.00%.

@@             Coverage Diff              @@
##                7.x     #727      +/-   ##
============================================
- Coverage     58.57%   58.56%   -0.01%
+ Complexity    12604    12601       -3
============================================
  Files          1761     1762       +1
  Lines         64742    64752      +10
  Branches       6412     6412
============================================
+ Hits          37921    37922       +1
- Misses        23817    23824       +7
- Partials       3004     3006       +2

Impacted Files
Coverage Δ
Complexity Δ

...src/com/b2international/snowowl/core/CodeType.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...wowl/core/request/ConceptSearchRequestBuilder.java
31.25% <0.00%> (-14.21%)
5.00 <0.00> (ø)

...wl/core/request/ConceptSearchRequestEvaluator.java
68.75% <100.00%> (+1.35%)
3.00 <0.00> (ø)

...national/snowowl/core/locks/OperationLockInfo.java
43.33% <0.00%> (-3.34%)
7.00% <0.00%> (-1.00%)

...index/src/com/b2international/index/es/EsNode.java
84.70% <0.00%> (-1.18%)
15.00% <0.00%> (-1.00%)

...national/index/revision/BaseRevisionBranching.java
89.72% <0.00%> (-0.69%)
53.00% <0.00%> (-1.00%)

...nternational/snowowl/core/events/util/Promise.java
70.53% <0.00%> (+1.78%)
19.00% <0.00%> (ø%)

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 67f3a66...e8563f6. Read the comment docs.


[flutter_core_web]: Version solving failed

Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Core, Crashlytics, Messaging
Which platforms are affected?
Android, iOS
Description
When i run pub get, i got this error:
Because firebase_core_web 2.17.4 depends on web ^0.5.1 and no versions of firebase_core_web match >2.17.4 <3.0.0, firebase_core_web ^2.17.4 requires web ^0.5.1.
And because emoji_picker_flutter >=3.0.0 depends on web ^1.0.0 and firebase_core >=3.3.0 depends on firebase_core_web ^2.17.4, emoji_picker_flutter >=3.0.0 is incompatible with firebase_core >=3.3.0.
Reproducing the issue
Because firebase_core_web 2.17.4 depends on web ^0.5.1 and no versions of firebase_core_web match >2.17.4 <3.0.0, firebase_core_web ^2.17.4 requires web ^0.5.1.
And because emoji_picker_flutter >=3.0.0 depends on web ^1.0.0 and firebase_core >=3.3.0 depends on firebase_core_web ^2.17.4, emoji_picker_flutter >=3.0.0 is incompatible with firebase_core >=3.3.0.
Firebase Core version
3.3.0
Flutter Version
3.24.0
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Because firebase_core_web 2.17.4 depends on web ^0.5.1 and no versions of firebase_core_web match >2.17.4 <3.0.0, firebase_core_web ^2.17.4
  requires web ^0.5.1.
And because emoji_picker_flutter >=3.0.0 depends on web ^1.0.0 and firebase_core >=3.3.0 depends on firebase_core_web ^2.17.4,
  emoji_picker_flutter >=3.0.0 is incompatible with firebase_core >=3.3.0.
So, because topish depends on both firebase_core ^3.3.0 and emoji_picker_flutter ^3.0.0, version solving failed.

Additional context and comments
No response

Hi @Sardorbee . This issue has been reported several times. Kindly search for duplicates before posting a new issue.
Please refer to this: issue


Move the IsolateNameServer from dart:ui to dart:isolate

The IsolateNameServer is currently in dart:ui, which means it only can be used on the Flutter runtime. I'm working on a non-Flutter project where it would come in handy.
Is there a particular reason it's in dart:ui, although it would intuitively better fit in dart:isolate?

The dart:ui library is maintained by the Flutter team, and the dart:isolate library is owned by the Dart team.
As a Dart library maintiner, I'd probably not put that functionality into dart:isolate.
It's utility functionality, not something most Dart isolate users will necessarily need (something which might be different for Flutter users if the framework uses it).
If the Dart team was to own the functionality, I'd probably put it into package:isolate instead. This keeps the core platform libraries slimmer and the functionality easier to maintain (it's so much easier to make changes to versioned packages than to the SDK libraries). We'd probably not add it, and instead just recommend using the isolate registry functionality instead. It's more complicated than the IsolateNameServer, but if you store one SendPort value per String tag, it should support the same functionality.

Oh, I see. That dart:ui and dart:isolate are owned by different teams explains a lot (for example, I also wondered why hashValues was in dart:ui).
To give a bit more context: My use case is a pure-Dart database where I would need a global namespace: If the developer opens a database in one isolate and also opens the same database in another isolate, I'd like both of those calls to connect to and communicate with the same backend isolate, which would handle accessing the file and exchanging changes.
So if I understand correctly, that's currently not possible in pure Dart and I would have to depend on Flutter?

Correct. It's not possible in pure Dart for an arbitrary isolate to know about another isolate without there being some pre-existing communication. That would generally mean that spawning a new isolate would require sending at least one send port along with the spawn request, so that it's possible to set up communications. If you just do Isolate.spwan(someFunction, null) then there is no available way to start communicating with that isolate using pure isolate communication.
You could set up an HTTP server on a known port and communicate using that, but then you won't have any send ports, and will need to serialize all the data yourself.

Okay, that's what I thought. The HTTP approach sounds interesting, I might look into that.
Would it theoretically be possible that in the future the IsolateNameServer gets migrated to dart:isolate or is that completely off the table?
Given that the functionality exists, it would semantically make more sense for it to be in dart:isolate.
And conceptually, it also makes sense that this functionality exists at all: Having global state (like the global table from names to ports) sounds like a bad idea for most everyday use-cases, but in the end, a Dart program is one entity in the OS that somehow needs to access OS resources – be that files, ports etc. Managing this access using functional-style pure isolates doesn't work (because files, ports etc. inherently have an identity), so there should be a way to manage that access in Dart. Working around this by having to rely on the OS for this functionality (like using ports or files to communicate with other isolates) indicates that something's missing in the DartVM.

There is no technical issue with moving the class and implementation into the Dart SDK from the Flutter SDK.
Whether we want it ... that's a design decision. It sort-of breaks the isolation of isolates, but so does file I/O.
I can see that pragmatically it works. It's a sort of "registry" for send ports, which is all you need to set up communication between any two isolates, so it's a minimal feature which solves the problem.
I probably wouldn't name it IsolateNameServer. It's not serving isolates. More like PortRegistry.

It sort-of breaks the isolation of isolates, but so does file I/O.

Exactly. My issue is that there are valid use-cases for this functionality (like managing file access, port access, communicating with other programs, etc). Currently, developers have the following two choices:

Only make their package available for Flutter, which harms the general Dart ecosystem.

I completely agree that PortRegistry is a better fitting name.

Whether we want it ... that's a design decision.

What would be the next steps? Is there a design committee or something that looks over this?

Since the isolate library is owned by the VM team, I'll make this an area-vm enhancement issue.

Maybe interesting: Elixir also uses an actor approach for concurrency. The equivalent to Isolates are Processes and you can register their ids/ports in a global registry: https://hexdocs.pm/elixir/master/Process.html#register/2

@lrhn I thought I could avoid asking for the VM team to have to spend their developer resources on this by
implementing this for myself using FFI based on the code already there in the Flutter teams implementation.
But sadly what I quickly discovered is that while there is a way to get a native port intended for use by C code, there is no way to then make use of this on the Dart side to get back a SendPort.
So I think the only way this can be done is by moving it into the Dart SDK due to needing to use the Dart native extensions unless there is some way to serialise and then deserialise Dart objects (specifically SendPorts) for use with FFI that I'm missing?
I think I remember seeing somewhere that the FFI could eventually replace the older native extensions mechanism, so this is I guess also an example where that currently isn't possible.
PS. My use is pretty much as per @MarcelGarus comment, of recreating a similar functionality of Erlang/Elixir but I would prefer without needing to pass around a Registry to every spawned Isolate as required by the pure Dart Registry in the Isolate package.


Add custom Meta from dbt into the Custom Properties tab

Is your feature request related to a problem? Please describe.
Nope.
Describe the solution you'd like

Ingesting tables that come from dbt

We would like to add the meta that comes from the schema.yml file, in this example, to create a property called model_dag and automatically fetch it from the artifact manifest.json.
version: 2

models:
  - name: <model_name>
    description: "<model_description>"
    meta:
      model_dag: "<user_input>"

Describe alternatives you've considered
Another catalog that is also open source has this already implemented this if you want to explore a similar feature.
Additional context

We are looking for a similar feature, where dbt meta values map to open metadata custom property values based on matching keys.


[WIP] Side chain lifetime management.

[x] Add authorization in side chain lifetime.
[x] Address authority check in cross chain contact.
[x] Deploy parliament contract during chain creation.

:x: Build AElf <IP_ADDRESS>9 failed (commit https://github.com/AElfProject/AElf/commit/e388687e40 by @shiwk)

:white_check_mark: Build AElf <IP_ADDRESS>7 completed (commit https://github.com/AElfProject/AElf/commit/5eca2e7881 by @shiwk)

:white_check_mark: Build AElf <IP_ADDRESS>2 completed (commit https://github.com/AElfProject/AElf/commit/eb1d20894b by @shiwk)


Unknown function 'fact' python/manifests/install.pp, line: 269

Affected Puppet, Ruby, OS and module versions/distributions

Puppet: 6.17.0
Ruby: 2.5.5
Distribution: centos
Module version: 4.1.1

How to reproduce (e.g Puppet code you use)
from the example code:
python::python_pyvenvs:
  "/opt/env1":
    version: "system"
  "/opt/env2":
    version: "system"
python::python_pips:
  "nose":
    virtualenv: "/opt/env1"
  "coverage":
    virtualenv: "/opt/env2"

What are you seeing
Error: Unknown function: 'fact'.
What behaviour did you expect instead
Puppet run to complete and create virtualenv appropriately.
Output log
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Unknown function: 'fact'. ( .... python/manifests/install.pp, line: 269, column: 14) on node xxxx
Log to entirely verbatim.
Any additional information you'd like to impart
This is the line of code it fails on:
if fact('lsbdistcodename') == 'trusty' {

The fact function comes from the puppetlabs/stdlib module: https://forge.puppet.com/puppetlabs/stdlib/reference#fact
Do you have puppetlabs/stdlib installed?

Hi, kenyon.  It was a problem with stdlib, an older crusty version was installed locally that got in the way of pulling the new one in.


Writing the name of the streams three times each is too much boilerplate

For instance, the example at README.md has 'inputText$' written three times.
If you have a lot of events happening, you not only have to give unique names to them, you also need to write these names on a lot of disconnected places. It is not optimal and refactoring is too difficult.
I've been thinking about it, but I don't have a solution, so I'll just leave this issue here.

@fiatjaf this is fixed in (upcoming) v0.8.0


[Bug]: BTD 6 - Failed to download UnityDependencies ( 2021.3.12, the link is wrong)

All of the following criteria must be met

[X] All Requirements must be installed.
[X] Full Latest.log file included. If no file exists then leave this unchecked and state so.

All of the following are optional to answer

[X] Tried reinstalling the Game.
[X] Tried reinstalling MelonLoader.
[X] Tried restarting PC.
[ ] Was able to see the Start Screen.

Describe the issue.
Latest.log
So I'm trying to launch BTD 6 v34.3.6116 with mods, I have 3 mods in the mods folder, its not even getting to the mod reading part. When I launch the game by double clicking on the .exe file it opens the console thing, does the startup, gets to installing unity dependencies and says that it failed to do it. I checked what link it was downloading from, found out its not hosted there anymore. The link for the dependencies is different now. I thought ok I'll manually download it and put it there but it doesn't read it, it just tries to download and install it. Please help.
Also I'm not sure what the start screen is and if I saw it or not.
Did you attach your log file?

[X] Yes, I attached my log file to the text box above.
[ ] No, I could not find a log file at {Game_Directory}\MelonLoader\Latest.log

Update to 0.6.0
Enable alpha versions in the installer settings

Also, the game was working and launching properly before I installed MelonLoader.

Update to 0.6.0
Enable alpha versions in the installer settings

Umm I tried that and it said missing the .NET framework 6.0.0 CORE, so I went to the official website installed its installer .exe file, ran it and tried again, it didn't work. Said the same thing that its missing the framework. So I switched back to 5.0.7 cuz it got me the farthest.


Replace CRLF with LF

Many, if not all, files contain CRLF instead of LF. While not a huge deal shell scripts are picky about this and currently throw : No such file or directory sh which can be seen with user-consul-nginx-nodejs. This does not seem to affect operations but are a concern and can be fixed by simple conversion.
I recommend all files to be updated from CRLF to LF.

@matthewvalimaki I was just looking into this because it's basic and fundamental. I thought I could squeeze it in but I can't seem to find any CRLF files in the repo. This is my output:
vagrant@ubuntu-14:/vagrant$ file ./examples/user-consul-nginx-nodejs/root/etc/services.d/nginx/run
./examples/user-consul-nginx-nodejs/root/etc/services.d/nginx/run: a /usr/bin/with-contenv sh script, ASCII text executable

It doesn't mention CRLF like it I was expecting. Is this still an issue? Are you able to be a little more specific about the files you're seeing are CRLF?

@matthewvalimaki, I ran this too find . -not -type d -exec file "{}" ";" | grep CRLF and got nothing back :(
The only thing I could find was:
docker-alpine$ find . -not -type d -exec file "{}" ";" | grep "no line terminators"
./examples/user-consul-nginx-nodejs/root/app/node_modules/node-static/test/fixtures/hello.txt: ASCII text, with no line terminators
./examples/user-nginx-nodejs/root/app/node_modules/node-static/test/fixtures/hello.txt: ASCII text, with no line terminators

Is that what you're talking about?

@smebberson you know, I've built some of the images on Windows and it's during git clone when things get converted from LF to CRLF. Sorry about this report. I didn't realize it until you looked into it.


Bump package.json to 13.1.1

Right now when you npm install you will get the old version of the files, which still contain the FabricEnabledViewGroup https://github.com/react-native-svg/react-native-svg/issues/1854
Note:
Even after npm cache clean and removing the node_modules folder I still get the old files

It will be available with the new release, which I am planning on doing today. It is an expected behavior and should not be considered an issue. I will close it then. Feel free to comment here if something is wrong and we can always reopen it then.


Enable one-key-formatting on more pages

Reopen of #4232. Fixes #4231.
Specifically, this PR adds one-key-formatting to:

the title of a new issue
the body of a new issue
the title of a new PR (this already works for the body of a new PR)
the title of a new gist
the title and body of saved replies

Reference for the difference between pageDetect.hasCode and pageDetect.hasRichTextEditor: https://github.com/fregante/github-url-detection/blob/9aa429df7af2807ce4797c02b164f83386c453bb/index.ts#L474-L488
one-key-formatting no longer applies on the pages flagged by pageDetect.isRepoTree and pageDetect.isBlame, which is OK because there are no text inputs on these pages.
Unfortunately, one-key-formatting does not work when creating new files/gists or editing existing files/gists. This is because the GitHub code editor uses CodeMirror, which itself captures text and applies HTML around it, and so the current approach of wrapping text does not seem to work.

Test URLs
Screenshot

Thanks @rly


Change - Metadata field selector, add infinite scroll for data paginated

Hi @tdonohue , I'm @jtimal partner, I like to share this PR with you:
References

Fixes #2730

Description
I changed metadata field selector add infinite scroll for pagination all data from metadata field service, this change load all options in the start
Instructions for Reviewers
To  see the new implementation, I attch a video with the functionality: https://youtu.be/8D-EjhubABI
List of changes in this PR:

I changed the template metadata-field-selector.component.html adding the infinite scroll directives
I changed the search function to page the query detecting change value on input
I changed the observable list to "behaviorsubject" for update the current list
I added a function for update the current list options according the query search, only if the user scroll to last item of the list

Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

Hi, I tested the PR. It works as described : when adding a metadata field to an archived Item, full list of metadata available is listed in the Field Column with ability to scroll down :

When starting to type metadata name (i.e dc.identifier) the metadata list is filtered accordingly and can still be scrolled.


Feature: exclude folders from scan

Looks comparable to what we worked on for #221. Waiting on either to get approved. Really looking forward to this feature.

Would be great if you could resolve merge conflicts

@amilajack , resolved.

@LinusU would be great if you could review this

@amilajack @LinusU please merge

What about merge it?

Any update on this? Could really use this or an automatic ignore of .gitignore entries


Add ability to customise the dismiss button's title

This PR adds the ability to customise the title of the dismiss button via either a LocalisedStringKey (and optional bundle and table name) or a non-localised String.

One thing I'm unsure about is having the localised and non-localised variants have the same view modifier name - since LocalisedStringKey conforms to ExpressibleByStringInterpolation this may lead to some confusion.

@mergesort Couple of responses:

Best I can tell, LocalizedStringResource is just like LocalizedStringKey in that the ExpressibleByStringLiteral conformance is used to give it the key. There isn't a way to make a non-localised LocalizedStringKey looking at the docs. I still think the String variant needs to be there for non-localised values.

I think using LocalizedStringResource internally and having an API for clients for it makes sense.

…however, we use LocalizedStringKey everywhere in our projects and that isn't going away overnight, so we'd need a LocalizedStringKey way of giving values to Recap. Annoyingly, as is SwiftUI's wont, these structs are all completely opaque and I can't see a way of making a LocalizedStringResource from a LocalizedStringKey - which means an extension with a translation shim doesn't seem to be possible.

Best I can tell, LocalizedStringResource is just like LocalizedStringKey in that the ExpressibleByStringLiteral conformance is used to give it the key. There isn't a way to make a non-localised LocalizedStringKey looking at the docs. I still think the String variant needs to be there for non-localised values.

I think this isn't necessarily intuitive, but a
LocalizedStringResource with no matching key will render the text as an unlocalized String.

If you look at SwiftUI's Text you'll see that it takes a LocalizedStringResource. There is no initializer that takes a String, it will just render the String as is if it doesn't find a matching key.
That's why I'm proposing to remove the non-localized initializer, and follow the same pattern as SwiftUI does. I can confirm having done this many times in SwiftUI that the approach should work, and would be my preferred API design.

Separately: Feel free to reach out to me if you need a way to convert a LocalizedStringKey to a LocalizedStringResource, I have some code in Plinky that should make the transition easier for you.

a LocalizedStringResource with no matching key will render the text as an unlocalized String.

Technically correct, but also technically that's a broken key.
We can't switch to LocalizedStringResource because it's just not good enough for our uses.  This has its uses, but that sort of lookup is far too slow for a whole catalog. LocalizedStringResource does have class-based lookup, but as far as I could see there isn't a single class in Recap, so I can't use that here (we can use it in our app, though).
The SwiftUI APIs keep around - without deprecation - LocalizedStringKey for good reason.
Anyway, I've removed everything but LocalizedStringResource as requested. We won't move to it in our codebases for the above reasons, but I can put up with it for one string.


How to make the calendar all vertical display

Did you findout the solution?

Yes,I use this library (https://github.com/square/android-times-square)


Update to javafx18 and java17

Seems to be passing now

Now just have to fix the styling of the client

🔝

?

Was meant like a well done


WIP: Render Engine

Please leave comments while the render engine work continues.

@JackMorganNZ Would you be able to quickly look at my docker set up and leave some comments if there are issues. Thanks.

Looks fine so far, but my knowledge of Docker is very limited.

The requirements file is outside the requirements folder. This is fine for the moment, but it would be good to review this in the future.

@JackMorganNZ @hayleyavw Ping, I think this is ready for review now. This is the infrastructure + Task Queue chunks.

@JackMorganNZ @hayleyavw Ping


Some store finder unit tests fail on Weekend

On Weekend, store close, so cannot get open time. We need mock the time schedule in unit test.

asterix did a storefinder refactor so these are very likely fixed