Interaction - Button

Implement an instance of a button.

[ ] Create a class as part of View driver.
[ ] Dynamically select what type fo button is needed.
[ ] Build a custom button given an input object.
[ ] Return as a component.

Not going to implement


Update reader.zig

Error: no field named 'sec' in struct 'c.darwin.timeval'
.sec = @intCast(@divTrunc(timeout, 1000))
zig version: 0.13.0

Ya, that's a recent Zig change.
I created a [zig-0.13 branch(https://github.com/karlseguin/smtp_client.zig/tree/zig-0.13) for the previous commit.


Add post-v4.0 freq VDS split fix to ensure all hom refs are kept in all samples

This fixes the existing 4.0 code so all hom ref calls are kept in the subsets after the split and densify. I tried to document extensively to make sure future users knew this wasnt used in v4.0 but would have the desired  freq outcome if it were.

Thakns @KoalaQin , back to you!

https://github.com/broadinstitute/gnomad_methods/issues/683


Disable tracing without deleting the zipkin endpoint

This feature was nice in the firefox extension because it allowed us to only trace when we really wanted to but you also don't have to keep inputting the endpoint over and over

Actually tracing is always enabled, as long as the plugin is turned on :-P
It would be nice to enable it when the zipkin panel is open, and disable it when it's closed.
Do you want to try a PR? :-D

I can take a shot, not a javascript dev though so it might take a bit of time to get any it done well


Assignment link

Thank so you much for providing this helpful resource. It's really helping me catch up!
The link in Class 36 for - Watch: What the heck is the event loop?, links to the Interview Questions (Behavioral / Technical) Google Doc instead.
I believe this is the video: https://www.youtube.com/watch?v=8aGhZQkoFbQ

Thanks for the heads up! Fixed :)


RillRate will not register tracers created after a certain duration.

Adding even a small delay in adding a tracer, results in the tracer not being registered.
This is replicable by but not limited to adding a delay via Thread::sleep().

Version: RillRate v0.23.0
Platform: Replicable on Windows 10 Home.
Minimum Reproducible Example:

use std::error::Error;

use std::time::Duration;

fn main() -> Result<(), Box<dyn Error>> {
    let _rillrate = RillRate::from_env("test")?;
    sleep(Duration::from_millis(100));
    let _table = Table::create("test table")?;
    loop {
        continue;
    }
}

Thank you for the good report! It really exists. We are fixing it.

Yes this fixes the issue. Thanks.


Update to webpack 2

Hoping for someone to update this, or as soon as I got time I will do this.

Actually this was done in https://github.com/alicoding/react-webpack-babel/commit/3f3217ee719e88136c4bcaf23c53580ed36f77f1 but maybe update to webpack3?
https://medium.com/webpack/webpack-3-official-release-15fd2dd8f07b


Solve issue 306 (avoid the nobest parameter in the dnf module)

Tested with several RHEL 8.1...9.1 versions, on x86_64, ppc64le, and s390x. All systems booted successfully and had the Server software environment group installed afterwards.

Why are you using dnf or yum module and not package?  I would prefer  platform independence. Other than that I am fine with the change.

Why are you using dnf or yum module and not package? I would prefer platform independence. Other than that I am fine with the change.
We don't need to be platform independent, as the file  RedHat/installation.yml is in a platform dependent subdirectory already. But we might still use the package module because it acts as a proxy to the underlying package manager module and should forward all parameters to that one.


Attachments not working such as embed images and thumbnails

Attachments
Since the beta version I am no longer able to add image attachments to a message using
add ... to attachments of message
Embed Images
Also I noticed before already that for some reason I'm not able to add thumbnails not images to an embed anymore. They don't give me any error unlikely as the attachemt issue, they just don't show on the embed anymore.
set thumbnail of embed to "image url"
set image of embed to "image url"

Is that still up to date for all reports? We talked about this on Discord but lost the lead 😅

Is that still up to date for all reports? We talked about this on Discord but lost the lead 😅

So the attachements yes, the images and thumbnails of embed no.

I thought about that, but maybe Skript does not accept mixing types in arrays? Are those all images (the functions)?

You have send a custom edited version of disky beta2 in the discord. This error doesen't appear on that version but on the public release it does

Yes they all return a image type

With the latest beta4 it also appears?!

There is no beta4.

The latest release it 4.12.0-beta4: https://disky.me/resources/index.php?resources/disky-official-resource.5/

Download it and check, it's actually 4.12.0-beta3

yeah I may have forgotten to change the internal version name :x, but does it also happens there?

yes it does

Got it, imma investigate that in the afternoon 👌


Few minor changes + opinionated react-component tooltip

Hey, I've made a fork with few changes:

Added d.ts - typescript definition file.
propTypes and displayName is now class static props - uses babel transform-class-properties.
(React complained about this...)
Updated props for C3Chart based on C3 types file.
Added prop - tooltipComponent which accepts tooltip as React Component instead of raw HTML.

Would like to have some feedback :)
Hoping you would accept this PR.

I still struggle trying ot use it in a JSX project of ours though,
Trying to port the example to our app without success so far (yesterday late night ;), How would you write the basic example in JSX?

@MonkeySlut thank you for adding this.
@ungentilgarcon You can return a custom React component in the tooltip.contents function by using  renderToStaticMarkup on your component.
Check out this example I put together. Specifically the tooltipOptions object with the contents function - https://codesandbox.io/s/9j2vj1363w


ci: Fix pr-title not running

It seems that skipping reusable workflow jobs causes inconsistent check names between pull_request_target and merge_group.
For the non-skipped PR runs we get a local_job/remote_job name,
but the skipped jobs in the merge queue are just called local_job.... (even if skipped in the called workflow instead of locally).
I updated the reusable workflow to skip individual steps instead of the whole job, so now we shouldn't have to deal with that inconsistency.
I will need to update the required check name to local/remote

For some reason the check in this PR is called remote/remote 🤦 .

Let's just try and see if it works...

...and the check is called local/remote on the merge queue

I think it's because the workflow is running with the file from main here...

This event runs in the context of the base of the pull request, rather than in the context of the merge commit
https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target

This would explain why the merge queue uses the renamed branch but the PR doesn't.
I removed the job name from the remote definition, and this check was still called Validate (...)/main even though "Validate (...)" is not defined anywhere.
Let's merge this, and hopefully new PRs will use the fixed config.


Dialogue fix for Mac

A smarter version of another pr that should not have been closed.

Thanks @beeanie

your welcome

instead of #if mac instead make it #if macro

please

idk what that does

instead of #if mac instead make it #if macro

I don’t know what that does.

its bascially mac but its macro

actually it dosn't work i just tested it

actually it dosn't work i just tested it

Mac or macro?

let me test it agian

actually nevermind

it works

When I tested it, I think it didn’t work for the very first time but it worked every other time.

aw


No secure curve on node?

The elliptic module's readme links to http://safecurves.cr.yp.to/ which lists secp256k1 as not safe. Can I use other curves from elliptic, eg. ed25519?

Currently no, because secp256k1-node library is being used for ECC when running on Node and it provides only K-256 curve. It's possibe to use e.g. OpenSSL for other curves but I have no plans to implement this, sorry.
I will keep this issue opened since it's valid feature request. I actually wrote this simple wrapper library to use with Bitmessage which has only K-256 so haven't bothered to add anything else yet.


bug: resolve problem with javascript error on button click where enter key works

When using the REFEDS MFA enhancements, the javascript that is rendered in the default theme of ADFS has an error where the submission method needs to be improved to be companioned with the adapter

compared with:

The ADFSToolkit affirmed the approach to resolve is to adjust the adapter dll to improve the javascript being invoked

Solved by #145


[BUG]  Error: spawn ETXTBSY

hi, I got very strange error, unfortunately I didn't find anything related to my issue.
If possible please have a look at this.
Environment

chrome-aws-lambda Version: ^1.20.2,
puppeteer / puppeteer-core Version: ^1.20.0
OS:
Node.js Version: 8 and 10

I tried to run it on different AWS node versions.
Logs:
2019-10-15T21:42:28.073Z 1930cd72-b389-41b5-b5bd-d4534dd0bc25 ERROR Error while generating pdf:Error: spawn ETXTBSY
2019-10-15T21:42:28.076Z 1930cd72-b389-41b5-b5bd-d4534dd0bc25 ERROR Error: params.Body is required
at ManagedUpload.validateBody (/var/task/node_modules/aws-sdk/lib/s3/managed_upload.js:271:13)
at ManagedUpload.configure (/var/task/node_modules/aws-sdk/lib/s3/managed_upload.js:123:10)
at new ManagedUpload (/var/task/node_modules/aws-sdk/lib/s3/managed_upload.js:95:10)
at features.constructor.upload (/var/task/node_modules/aws-sdk/lib/services/s3.js:1133:20)
at /var/task/services/awsUploader.js:18:8
at new Promise ()
at Object.uploadFile (/var/task/services/awsUploader.js:17:10)
at module.exports (/var/task/export.js:38:40)
2019-10-15T21:42:28.076Z 1930cd72-b389-41b5-b5bd-d4534dd0bc25 INFO finally:
2019-10-15T21:42:28.094Z 1930cd72-b389-41b5-b5bd-d4534dd0bc25 ERROR Invoke Error
{
"errorType": "Error",
"errorMessage": "params.Body is required",
"stack": [
"Error: params.Body is required",
"    at ManagedUpload.validateBody (/var/task/node_modules/aws-sdk/lib/s3/managed_upload.js:271:13)",
"    at ManagedUpload.configure (/var/task/node_modules/aws-sdk/lib/s3/managed_upload.js:123:10)",
"    at new ManagedUpload (/var/task/node_modules/aws-sdk/lib/s3/managed_upload.js:95:10)",
"    at features.constructor.upload (/var/task/node_modules/aws-sdk/lib/services/s3.js:1133:20)",
"    at /var/task/services/awsUploader.js:18:8",
"    at new Promise ()",
"    at Object.uploadFile (/var/task/services/awsUploader.js:17:10)",
"    at module.exports (/var/task/export.js:38:40)"
]
}
my code:
 const generatePDF = async data => {
   try {
     const browser = await chromium.puppeteer.launch({
      args: chromium.args,
      defaultViewport: chromium.defaultViewport,
       executablePath: await chromium.executablePath,
      headless: chromium.headless
     });
     const page = await browser.newPage();

     await page.goto(`file://${BASE_FILE}`, {
       waitUntil: 'networkidle0'
     });

     console.log(data);

     page.on('console', msg => console.log('PAGE LOG:', msg.text()));

     await page.evaluate(async params => await startVue(params), data);

     const pdf = await page.pdf({ format: 'A4' });

     browser.close();
     return pdf;
   } catch (error) {
     console.error(`Error while generating pdf:${error}`);
     throw error;
   }
 };

@EugeneEl It looks like the snippet you shared is incomplete, so hard to tell what's going on.
A couple of points:

file:// the file protocol needs 3 forward slashes (like file:///...)
what's BASE_FILE? does it exist on disk?
what's startVue()? and why is it complaning that params.Body is required?

Please share the whole repro so that I can help you better.

Hi Alixaxel,
I had the same error this is why I am leaving my comment on this closed issue:
When I deploy my lambda, I constantly get "spawn ETXTBSY" error.
When I delete the layer from  AWS console and reattach it again, it works.
At the end of the lifecycle of the lambda (more than 10 minutes after), when calling the lambda again I fall back on the same error.
Do you have an idea?
Below the stack error as well as my generation function
{
	"errorType": "Error",
	"errorMessage": "spawn ETXTBSY",
	"trace": [
		"Error: spawn ETXTBSY",
		"    at ChildProcess.spawn (internal/child_process.js:366:11)",
		"    at Object.spawn (child_process.js:551:9)",
		"    at Launcher.launch (/var/task/node_modules/puppeteer-core/lib/Launcher.js:132:40)"
	]
}

const convertToPdf = async function (html) {
	let browser = null;
	let pdf = null;
	try {
		const executablePath = await chromium.executablePath;
		browser = await chromium.puppeteer.launch({
				args: chromium.args,
				defaultViewport: chromium.defaultViewport,
				executablePath: executablePath,
				headless: chromium.headless
			});
		const page = await browser.newPage();
		await page.setContent(html);

		pdf = await page.pdf({
				format: 'A4'
			});

	} catch (error) {
		throw error;
	}
	finally {
		if (browser !== null) {
			await browser.close();
		}
		if (pdf) {
			return pdf;
		}
	}

};

@karimc1 It's really hard to help without a complete repro. My guess is that you're calling convertToPdf multiple times from the same Lambda instance? Also, you only have a single chrome-aws-lambda layer attached right?
The ETXTBSY error code is thrown when puppeteer is trying to start the Chromium binary but the binary file is under a exclusive lock - that can happen if you don't wait for executablePath to resolve, or, if you call executablePath multiple times.
I'd be happy to help you further if you need, just open a new issue and share a full repro.

Thanks for your quick answer I will open another ticket for that.
Bests,

@karimc1 how did you fix it?

I ma having the same issue

having the issue too

I am facing the same issue when launching chrome-aws-lambda browser inside WSL2 in headless mode. It used to work fine for quite a while now I don't whether I made a change in my environment which caused this.

@alixaxel can you reopen the issue ?

Sam issue happening to me, everything on the latest versions

Getting same issue

I am having the same issue. First I get an error that it can't find chromium. {"errno":-2,"code":"ENOENT","syscall":"open","path":"/var/task/src/functions/bin/chromium.br"}"
subsequent calls result in "{"errno":-26,"code":"ETXTBSY","syscall":"spawn"}"
the chromium.executablepath is actually /tmp/chromium which I'm guessing is a symlink to /var/task/src/functions/bin/chromium.br which isn't actually there for some reason, the layer is setup correctly afaik. Been working on this for two days straight, need help, about to shoot myself

I am running into this error when bundling with esbuild (only when in lambda, local invoke works fine).  However, I can successfully execute when using webpack as in this repo https://github.com/metacollective9/playwright-amz-scrape

Same happening for me, with node 16 and 12. Any idea?

@gventuri it could happen when you launch more than 1 puppeteer instance synchronously in your code.
is it your case?

@gventuri it could happen when you launch more than 1 puppeteer instance synchronously in your code.
is it your case?

Well, this was the issue in my case 🤦
This comment made me read me code again and therefore I found the issue. Thanks a lot 😄

Just in case anyone else made the same mistake as me, I forgot to comment out the running of the handler function at the end of my Lambda function that I use to run locally for testing during development. This caused two instances of the function to run causing this error.


Add missed probes metrics

wip needs https://github.com/cilium/ebpf/pull/1295

Thanks, LGTM.
One question what exactly is this missed metric? :) Is it when a link exists without a program? Or is it something else?

so it's incremented any time we don't execute the bpf program due to recursion in kernel,
like when you have 2 kprobe programs trying to run on top of each other on the same cpu
there was a case +- year ago where we were loosing exit events for this reason due to wrong
hook we used.. now if that happens again we will see that in the metrics

@lambdanis could you please recheck, I changed few things on metrics side because the tetragon base changed

A few comments:
1. Ideally we should use `MustNewCustomCounter` and `NewCustomCollector` from `pkg/metrics` here. See how other collectors were defined in [a05fbc7](https://github.com/cilium/tetragon/commit/a05fbc71ba49225c045a6354737724810409e4c7) or [7309c9b](https://github.com/cilium/tetragon/commit/7309c9ba22a2b07bae182e5ea8b10aa214be13fd). If it's a trouble for some reason, I'm ok with merging as-is, but then we should have a follow-up item to refactor it.

ok, used that in new version

2. The new metrics are not documented. Using helpers from 1. should provide an easy way to include them in the generated reference.

ok

3. I'm not sure `kprobe_multi (3 functions)` is a useful label value. Seeing such metric, how do I find out which functions were missed?

we don't have any more insight than that.. we get the counter per link/program that is attached to multiple functions,
and the missed counter spans over all attached functions.. we discussed some time ago to add a feature that would break down the counter to specific functions, but there was no need so far

ok, used that in new version

I see you use MustNewCustomCounter but the collector is defined as a separate type, not using NewCustomCollector. It would be nice to have the new metrics documented (in docs generated by make metrics-docs), and using NewCustomCollector should make it easy (you need to pass a collectForDocs function reporting fake metrics).


[TC-MF-1.17] [TC-MF-1.18] - Removable of fabric that is when we send remove-fabric command in chip-tool of TH2 makes DUT abort.

Issue :

[TC-MF-1.17] [TC-MF-1.18], Step 8 of test-plan for the mentioned test-cases says to remove fabric in TH2 which  makes DUT abort.
Test-plan reference : https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/multiplefabrics.adoc#tc-mf-1-17-removing-fabrics-from-dut-and-fabric-index-enumeration-using-ecm-dut-commissionee
Test platform :
Chip-tool - RPI/MAC
DUT - RPI

Steps to reproduce :

DUT side :

sudo rm -rf /tmp/chip_*
sudo ./chip-all-clusters-app --wifi

TH side :

./chip-tool pairing ble-wifi 1 zigbeehome matter123 20202021 3840 (on TH1)
./chip-tool pairing open-commissioning-window 1 1 100 1000 3840 / ./chip-tool administratorcommissioning open-basic-commissioning-window 500 1 0 --timedInteractionTimeoutMs 1000 (on TH1)
./chip-tool pairing manualcode 2<PHONE_NUMBER>6 / ./chip-tool pairing onnetwork 2 20202021 (on TH2)
./chip-tool pairing open-commissioning-window 3 1 100 1000 3840 / ./chip-tool administratorcommissioning open-basic-commissioning-window 500 3 0 --timedInteractionTimeoutMs 1000(on TH3)
./chip-tool pairing manualcode 3<PHONE_NUMBER>6 / ./chip-tool pairing onnetwork 2 20202021  (on TH3)
./chip-tool operationalcredentials read fabrics 2 0 --fabric-filtered 0
./chip-tool operationalcredentials remove-fabric 2 2 0

After step 7 DUT gets aborted automatically

Screenshot :

PFA logs :
remove-fabric_cntrl.txt
remove-fabric_dut.txt

Duplicate of #16748


Savings Chart

Maybe just a misunderstanding on my part, but I am not understanding how this chart works:

Does this use the TOU rates that I have loaded in the Tesla app? Why does the combined value exceed the sum of solar and battery?

Unfortunately there is no connection to the Tesla app settings to get the TOU data.  The Savings Chart was inherited from the powerwall_montior project.  It was always on my list to fix this so I worked on it tonight.  I have a new version that I hope makes a lot more sense.  However, it doesn't factor in TOU. It just assume $0.19/kWh which you can edit.  Because there are so many TOU plans, I figure I will start with the lowest common savings, but at least break it down in a way that makes more sense:

Future to-do:  Create a stacked TOU graph.  If you figure it out, please feel free to share. :-)


Github generated binaries aren't runnable on Mojave

Might be related to #91 ?

Looks like GitHub changed their targets to be Catalina, but I can't find where this was announced. :frowning_face:

Unless I provide a private runner, this situation isn't going to change. Closing.


Upgrade terraform-provider-consul to v2.21.0

This PR was generated via $ upgrade-provider pulumi/pulumi-consul.

Upgrading terraform-provider-consul from 2.20.0  to 2.21.0.
Fixes #492

Required a specific version to be set to match upstream to compile:
-	github.com/hashicorp/terraform-provider-consul v1.1.1-0.20231120153550-b46ab37b60ba
+	github.com/hashicorp/terraform-provider-consul v1.1.1-0.20240802192014-7a097673283b


Finalize APIs 07/22/16

[ ] Error Handling
[ ] Forgot Password
[ ] Admin Page
[ ] Multi-vineyard

This due date was yesterday. What's the word?

Decided, just need to throw it into docs today.

Multivineyard is just going to be downloaded with the login success packet. The rest is in the doc store in a new API folder. Admin pages aren't fully fleshed out but I don't expect them to be for a while honestly.

Everything looks good to me!

For those that haven't looked, the API doc is here:
Project Documentation > Wiki+Reference > API > Basics

Looks good to me as well. I'm hitting the button!


eigs_qpe.py does not output correctly the eigenvalues

Information

Qiskit Aqua version: 0.7.0.dev0+d0bdae9
Python version: 3.8.1
Operating system: Windows 10 Pro

What is the current behavior?
Eigenvalues are not correctly detected even when these can be exactly represented in binary with the given amount of qubits. The problem was found while investigating issue #899 from which it seemed that the problem was in detecting only the negative eigenvalues.
Steps to reproduce the problem
The matrix

has eigenvalue -0.5 for the eigenvector v and 0.5 for w. And below is the code used to create the eigs_qpe circuits in the subsequent examples.
from qiskit.aqua.components.eigs import EigsQPE
from qiskit.aqua.components.qfts import Standard as StandardQFTS
from qiskit.aqua.components.iqfts import Standard as StandardIQFTS

backend = BasicAer.get_backend('statevector_simulator')

def create_eigs(matrix, num_ancillae, negative_evals, evo_time=None):
    ne_qfts = [None, None]
    if negative_evals:
        num_ancillae += 1
        ne_qfts = [StandardQFTS(num_ancillae - 1), StandardIQFTS(num_ancillae - 1)]

    return EigsQPE(MatrixOperator(matrix=matrix),
                   StandardIQFTS(num_ancillae),
                   num_time_slices=1,
                   num_ancillae=num_ancillae,
                   expansion_mode='trotter',
                   expansion_order=1,
                   evo_time=evo_time,
                   negative_evals=negative_evals,
                   ne_qfts=ne_qfts)

q = QuantumRegister(1)
qc = QuantumCircuit(q)

# State preparation
qc.x(q[0])
qc.h(q[0])

# Initialise eigenvalue finding module
nl = 3
eigs = create_eigs(A, nl, False, evo_time = 2*np.pi/2)
num_q, num_a = eigs.get_register_sizes()
qc += eigs.construct_circuit("circuit", q)
result = execute(qc,backend).result()
counts = result.get_counts()
print(counts)

In this example the eigenvalues can be exactly represented in binary, however playing with the time and using 3 qubits to represent the positive eigenvalue gives the following results:

The case for negative eigenvalues,i.e.
# State preparation
qc.h(q[0])
(...)
eigs = create_eigs(A, nl, True, evo_time = 2*np.pi/2)
(...)

is incorrect in more cases. However, writing down on paper what the eigs_qpe.py module does for this example gives the right result. So the problem might be either in the Hamiltonian simulation (which should be exact in this case) or in the phase_estimation_circuit.py module.

HHL is being reworked under this PR Qiskit/qiskit-terra#5698 where core algorithms have been moved to Terra repo and are being maintained there. The code here will be deprecated and as such is frozen - hence I am closing this issue.

HHL is being reworked under this PR Qiskit/qiskit-terra#5698 where core algorithms have been moved to Terra repo and are being maintained there. The code here will be deprecated and as such is frozen - hence I am closing this issue.


Several splitter_ports, video accelerated

Hi, as my below code where I'm using multithread to record several videos(3), where any of then could start and stop at different moments, the picamera behave strange:
using just one splitter the video generate 60s in 60s OK
using two splitters each video generate 55s in 60s Not OK
using three splitters each video generate 38s in 60s Very Wrong
After the files are done I insert the header of the file eg:
ffmpeg -i done-5050-2 -vcodec copy -f mp4 done-5050-2.mp4
The file done-5050-2.mp4 should have a lenght of 60s but it is showing just 43s
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'done-5050-2.mp4':   Metadata:     major_brand     : isom     minor_version   : 512     compatible_brands: isomiso2avc1mp41     encoder         : Lavf56.40.101   Duration: 00:00:43.20, start: 0.000000, bitrate: 2881 kb/s     Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p, 1440x1080, 2880 kb/s, 25 fps, 25 tbr, 1200k tbn, 2400k tbc (default)     Metadata:       handler_name    : VideoHandler
What I'm doing wrong, or how should it work?
import sys
import threading
import time
import datetime as dt
import picamera
import os
import os.path
from random import randint, random
from threading import Thread

class MoveCamChannel(threading.Thread):

    job = 0
    running = True
    quality = 20
    framerate = 60
    path = ''
    split = 60
    channel = 0
    timeout = 1800
    camera = None

    def __init__(self, job, camera, channel, path, framerate, split, quality, timeout):
        self.job = job
        self.channel = channel
        self.path = path
        self.framerate = framerate
        self.split = split
        self.quality = quality
        self.timeout = timeout
        self.camera = camera
        threading.Thread.__init__ (self)

    def stop(self):
        self.running = False

    def run(self):
        inter = 1
        file = '{0}-{1}'.format(self.job, inter)
        self.camera.start_recording('{0}/{1}'.format(self.path, file), format='h264', quality=self.quality, splitter_port = self.channel)
        start = dt.datetime.now()
        while self.running:
            nowTime = dt.datetime.now()
            diff = nowTime - start
            if diff.total_seconds() >= self.split:
                inter += 1
                fileNew = '{0}-{1}'.format(self.job, inter)
                self.camera.split_recording('{0}/{1}'.format(self.path, fileNew), splitter_port = self.channel)
                self.move(file)
                file = fileNew
                start = dt.datetime.now()
            self.camera.wait_recording(1, splitter_port = self.channel)
        self.camera.stop_recording(splitter_port = self.channel)
        self.move(file)

    def move(self, file):
        if os.path.exists(file):
            os.rename('{0}/{1}'.format(self.path, file), '{0}/done-{1}'.format(self.path, file))

class MoveCamRecorder(threading.Thread):

    quality = 20
    framerate = 60
    path = ''
    width = 640
    height = 480
    split = 60
    led = 'off'
    fontSize = 20
    backgroundColor = 'black'
    banner = ''
    dtFormat = '%d/%m/%Y %H:%M:%S'
    timeout = 1800
    gravacao = {}
    camera = None

    def __init__(self, path, led, timeout):
        self.path = path
        self.led = led
        self.timeout = timeout
        threading.Thread.__init__ (self)

    def setBanner(self, fsize, fbg, banner, dtformat):
        self.fontSize = fsize
        self.backgroundColor = fbg
        self.banner = banner
        self.dtFormat = dtformat

    def setVideoSize(self, w, h):
        self.width = w
        self.height = h

    def setQuality(self, quality):
        self.quality = quality

    def setVideoSplit(self, split):
        self.split = split

    def setFramerate(self, fr):
        self.framerate = fr

    def startRecording(self, id):
        if len(self.gravacao) > 3:
            return False
        else:
            self.gravacao[id] = MoveCamChannel(
                    id,
                    self.camera,
                    len(self.gravacao)+1,
                    self.path,
                    self.framerate,
                    self.split,
                    self.quality,
                    self.timeout
            )
            self.gravacao[id].start()

    def stopRecording(self, id):
        if id in self.gravacao:
            self.gravacao[id].stop()
            self.gravacao[id].join()
            del self.gravacao[id]

    def detectCamera(self):
        try:
            with picamera.PiCamera() as camera:
                camera.start_recording('/dev/null', format='h264')
                camera.wait_recording(3)
            return True
        except Exception, e:
            self.recCamera = False
            return False

    def run(self):
        with picamera.PiCamera() as self.camera:
            self.camera.led = True if self.led == 'on' else False
            self.camera.resolution = (self.width, self.height)
            self.camera.framerate = self.framerate
            self.camera.start_preview()
            self.camera.annotate_background = picamera.Color(self.backgroundColor)
            self.camera.annotate_text_size = self.fontSize
            #self.camera.start_recording('/dev/null', format='h264', quality = 30, splitter_port = 0)
            start  = dt.datetime.now()
            while True:
                now = dt.datetime.now()
                diff = now - start
                self.camera.annotate_text = '{2} - {0} {1}'.format(self.banner, dt.datetime.now().strftime(self.dtFormat), diff.total_seconds())
                time.sleep(1)
            #self.camera.stop_recording(splitter_port = 0)

if __name__ == "__main__":
    recorder = MoveCamRecorder('./', 'on', 1800)
    recorder.setVideoSize(1440, 1080)
    recorder.setQuality(25)
    recorder.setFramerate(25)
    recorder.setVideoSplit(60)
    recorder.setBanner(40,'blue', 'Test', '%d/%m/%Y %H:%M:%S')
    recorder.detectCamera()
    recorder.start()
    time.sleep(5)
    recorder.startRecording('5050')
    time.sleep(20)
    recorder.startRecording('900')
    time.sleep(60)
    recorder.startRecording('1900')
    time.sleep(120)
    recorder.stopRecording('1900')
    time.sleep(30)
    recorder.stopRecording('900')
    time.sleep(5)
    recorder.stopRecording('5050')

You're dropping frames and not looking at timestamps, so ffmpeg just glues together all the frames assuming 30fps.
Additional encodes are not free operations, and there are limits to the compute power.
The encoder is rated for a single stream at H264 Level 4.1, which is the equivalent of approx 1080P30 (technically it is 62,914,560 luma samples/s). You can get a little bit more than that out (1080P33 was always the aim), and you can split that encode power between multiple streams with a small overhead.
If I'm reading your code correctly then you're pushing 1440x1080@25fps through, so 38,880,000 luma samples/s. Two streams would be 77,760,000 luma samples/s and you're beyond the hardware spec and it will drop frames.
I'm also not sure which encoding formats PiCamera is setting up the splitter ports with. I suspect it is having to convert a load of images between planar and an internal image format which is going to hit memory bandwidth.

I was able to recording several videos at same time using a encoder class and passing it to an object. Than the object use the frame buffer to write in several ffmpeg pipes, using it I have several videos in h264 mp4 without loss frames or using too much harware from raspi.
Thanks for your explanation.

Looks like this ticket's answered so I'll close it (do feel free to re-open if you've further queries regarding this).


[feat] New restful API for workflow and schedule

CURD for workflow and schedule

This PR is not only refactored exists API, we also separate existingprocess definition and schedule into single resources CRUD(previous process definition also will submit tasks and task relation). And we make it more Restful

Codecov Report

Merging #11912 (16b1546) into dev (d833a28) will increase coverage by 0.33%.
The diff coverage is 70.10%.

:exclamation: Current head 16b1546 differs from pull request most recent head cb52a01. Consider uploading reports for the commit cb52a01 to get more accurate results

@@             Coverage Diff              @@
##                dev   #11912      +/-   ##
============================================
+ Coverage     38.71%   39.05%   +0.33%
- Complexity     3999     4070      +71
============================================
  Files          1003     1013      +10
  Lines         36548    36804     +256
  Branches       4222     4269      +47
============================================
+ Hits          14151    14373     +222
  Misses        20788    20788
- Partials       1609     1643      +34

Impacted Files
Coverage Δ

...eduler/api/dto/schedule/ScheduleFilterRequest.java
0.00% <0.00%> (ø)

...scheduler/api/controller/ScheduleV2Controller.java
9.09% <9.09%> (ø)

...eduler/api/dto/workflow/WorkflowFilterRequest.java
33.33% <33.33%> (ø)

...cheduler/api/service/impl/ExecutorServiceImpl.java
45.27% <37.50%> (-0.09%)
:arrow_down:

...eduler/api/dto/schedule/ScheduleUpdateRequest.java
48.48% <48.48%> (ø)

...er/api/controller/ProcessDefinitionController.java
51.04% <50.00%> (+1.53%)
:arrow_up:

...eduler/api/dto/workflow/WorkflowUpdateRequest.java
50.00% <50.00%> (ø)

...api/service/impl/ProcessDefinitionServiceImpl.java
35.42% <61.90%> (+2.78%)
:arrow_up:

...heduler/api/service/impl/SchedulerServiceImpl.java
27.38% <80.76%> (+18.77%)
:arrow_up:

...eduler/api/dto/schedule/ScheduleCreateRequest.java
84.61% <84.61%> (ø)

... and 34 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

fix conflict from adding log in #11782

PTAL if you have time @caishunfeng @SbloodyS

we still have discuss in https://github.com/apache/dolphinscheduler/pull/11912#discussion_r973823553 and https://github.com/apache/dolphinscheduler/pull/11912#discussion_r973825097

Thanks @zhongjiajie


Pull GCI docs into main Zulip repo.

Some of our assets, like git cheatsheets, currently live in the zulip-gci repo.  We should move them to the main Zulip repo and link from appropriate places.
cc @synicalsyntax @lonerz @tommyip

(move or copy, as appropriate)

I'd probably move and just update the links in zulip-gci to point to the new place.

@zulipbot claim

Yeah, and probably under the DEVELOPER TUTORIALS section.

@tommyip is this what you are referring to?

I belive @tommyip talks about the whole Developer tutorials in the docs structure. This means that the docs you'll be moving from the GCI repo should have their own entries here, in docs/index.rst:
 74 .. _developer-tutorials:
 75
 76 .. toctree::
 77    :maxdepth: 2
 78    :caption: Developer tutorials
 79
 80    integration-guide
 81    webhook-walkthrough
 82    new-feature-tutorial
 83    writing-views
 84    life-of-a-request
 85    reading-list

So you should basically copy them as new files inside docs/, update the links as @timabbott pointed out (in a separate PR in the zulip-gci repo), and add the new files' names to the abovementioned list in index.rst.


hybrid_android_views_integration_test fails on Pixel 7 Pro

https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro hybrid_android_views_integration_test/6/overview
Maybe it's because hybrid composition isn't use on the Pixel 7 Pro?
Either way, I am going to switch hybrid_android_views_integration_test back to running on the Moto G4, but it will probably need to be migrated to the A02.

@zanderso who owns this test/move to A02s?

@stuartmorgan is listed as the owner in the TESTOWNERS file.

@johnmccutchan Do you want to take this test over in TESTOWNERS? You're probably the best owner for Android platform view tests now.

@stuartmorgan Sure. What is actionable on this bug for me?

I don't have any context on this specific issue other than what's above, but for my comment the action would be to change https://github.com/flutter/flutter/blob/59242b75c569c6d3aea24038f112201271c5b484/TESTOWNERS#L143 to list you rather than me.

I retitled the issue. The overall goal is to get this test off of the Moto G4s since those devices are reaching end-of-life. There's question that I'm hoping that @stuartmorgan or @johnmccutchan are able to answer which is whether this test is supposed to pass on the Pixel 7.

I haven't looked at the test details, but Hybrid Composition as a mode certainly should work on a Pixel 7, so we should be able to have some test of it that passes on Pixel 7.

Yes, hybrid composition should work fine on Pixel 7/Pro phones.

Thanks! In that case, the the next action on this issue would be to investigate the failure of the test on the Pixel 7 =)

@zanderso is there someone who should be assigned to the investigation/issue?


New pixel 001

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Hey @BzerkSkemer I already merged a different PR of yours so I'll mark this as duplicate. Thank you for your contribution!


Purpose

The README says that spaghetto is:

The next iteration of Spago.

But why spago needs the next iteration? What is the reason to create this tool? It would be nice if README would have answers for this questions.

Hi! The main reason for the rewrite is because the current Spago codebase got quite tangly over time, and since we need to support the upcoming Registry (see there for more info), the effort for the integration was too large and we opted for a rewrite instead, which is going much better.
This is not supposed to be used in production (or at all) just yet, so the readme will stay empty until we are sure this is the right way forward.
That is, I'm actively discouraging you and everyone else reading this from using this tool at all right now.


ember-responsive

Having responsive diffs is quite awesome!
With ember-responsive or flexi one might render different DOM for each device.
Do you have any solution for this scenario in mind?
With ember-response it might be quite easy to overwrite the service and do multiple tests/snapshots

Thanks!
Is there any way to grab the current test breakpoint from ember-responsive after using setBreakpoint('mobile');? Because you could potentially just customize the name of the percy snapshot to include the breakpoint, like percySnapshot(${this.test.fullTitle()} [breakpoint:${breakpoint}]`) or something.


PIP installation not working

Hi,
just tried to install via PIP, ended up with error
 Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-HRCezx/pi-eltakows-webthing/

Could you please add some information about your environment -> Python version, OS, ...

sure!
Raspberry Pi 2B
OS Buster
Python 2.7.16

this project requires python3. I have updated the readme file regarding the required python version


Failed to "go get github.com/cloudfoundry-incubator/route-registrar"

With this commit 2b97f10192741236b0733119cda938b92ef87986, godeps is removed. Could you please give some background why it's removed?
Because godeps is removed, the latest multierror is installed when I run go get github.com/cloudfoundry-incubator/route-registrar. But the latest multierror.MultiError (https://github.com/cloudfoundry/multierror/commit/6bb1731c7a73a24f2bdaffc04e170d4c2c54d1e7) doesn't have the method AddWithPrefix and HasAny. So, I got the following error:
$ go get github.com/cloudfoundry-incubator/route-registrar
# github.com/cloudfoundry-incubator/route-registrar/config
cloudfoundry-incubator/route-registrar/config/config.go:84: errors.AddWithPrefix undefined (type multierror.MultiError has no field or method AddWithPrefix)
cloudfoundry-incubator/route-registrar/config/config.go:94: errors.HasAny undefined (type multierror.MultiError has no field or method HasAny)
cloudfoundry-incubator/route-registrar/config/config.go:95: cannot use errors (type multierror.MultiError) as type error in return argument:
        multierror.MultiError does not implement error (Error method has pointer receiver)
cloudfoundry-incubator/route-registrar/config/config.go:177: errors.HasAny undefined (type multierror.MultiError has no field or method HasAny)
cloudfoundry-incubator/route-registrar/config/config.go:178: cannot use errors (type multierror.MultiError) as type error in return argument:
        multierror.MultiError does not implement error (Error method has pointer receiver)
cloudfoundry-incubator/route-registrar/config/config.go:213: errors.HasAny undefined (type multierror.MultiError has no field or method HasAny)
cloudfoundry-incubator/route-registrar/config/config.go:214: cannot use errors (type multierror.MultiError) as type error in return argument:
        multierror.MultiError does not implement error (Error method has pointer receiver)
cloudfoundry-incubator/route-registrar/config/config.go:225: cannot use errors (type multierror.MultiError) as type error in return argument:
        multierror.MultiError does not implement error (Error method has pointer receiver)
cloudfoundry-incubator/route-registrar/config/config.go:230: cannot use errors (type multierror.MultiError) as type error in return argument:
        multierror.MultiError does not implement error (Error method has pointer receiver)
cloudfoundry-incubator/route-registrar/config/config.go:239: cannot use errors (type multierror.MultiError) as type error in return argument:
        multierror.MultiError does not implement error (Error method has pointer receiver)
cloudfoundry-incubator/route-registrar/config/config.go:239: too many errors

hi @bingosummer,
We recently moved the route-registrar from cf-release to the routing release. This is part of a wider effort to slowly move everything out of cf-release. In this process, we decided to no longer manage dependencies using Godeps, and instead use the routing-release as the canonical GOPATH for all of our repositories.
We have updated the installation instructions in the readme to reflect this change.


Create link in RW pointing to non-RW Foundry documents

This one is a bit tough to explain...
The game system, in my case PF 1e, already comes with some items, journal entries etc. Would it possible to create a link in Realm Works to a topic that does not exist in RW but once imported into Foundry the link will lead to the correct thing?
Maybe better with an example:
In a scene in Realm Works I write in the 'Rewards' section, that the players can find a Belt of Incredible Dexterity +2. In my realm, there's no topic or article like this. But in my Foundry world that item exists.
Now, how could I manage it, that after importing that scene into Foundry, the words 'Belt of Incredible Dexterity +2' become a link to the item?
I can't create internal RW links that point nowhere, as far as I know. Maybe the hyperlink could be repurposed somehow? Or I could add a placeholder string that your importer recognized and creates the link. Something like [[foundry_link::Belt of Incredible Dexterity +2]] or any other convention.

You could probably achieve this by putting the existing Foundry links into the realm works topic. Using the older type of link you can use the name of the Foundry thing rather than always needing to use the uuid.
So you could put @Item[Belt of Incredible Dexterity +2] and if such an item exists, then the link should work automatically.
I don't think that the RW Importer does any stripping out of these links.

You can even use the @UUID[item id]{label} syntax if you are happy to do the copy-and-paste from Foundry to RW.

Ah! Didn't think of the most obvious solution!
Going to try this out tomorrow. Thankfully the Quick Insert module let's me grap links like @Compendium[pf1.items.PC3K6eeXRdUwJxLA]{Belt of Incredible Dexterity +2} very easily.
Thanks for the help!

Wood for the Trees :-)
Hopefully it works.

Just wanted to report back that it works :-)


Warnings wordings for #168

Thanks to @aug-riedinger in https://github.com/tomchentw/react-google-maps/pull/168#issuecomment-225692098

Make sure you've put the   tag in your  element to load Google Maps JavaScript API v3.
Careful the async defer options as suggested (here)[http://googlegeodevelopers.blogspot.fr/2015/09/map-tips-speeding-up-page-load-times.html] doesn't work.
If you're looking for built-in support to load it for you, use the "async/ScriptjsLoader" instead.
See https://github.com/tomchentw/react-google-maps/pull/168

Cheers. :smile:
Do you expect me to PR this?

@aug-riedinger if you like that'd be great! Also, #266

Regarding your search for maintainers, I shall consider helping if I dive further into the projet that uses this repo. But this won't be before september because I'll be off this summer.
Cheers

Just to let you know  6.0.0 is released on npm beta tag now. See the changelog here. We also have a new demo page. Feel free to try it:
https://tomchentw.github.io/react-google-maps/

Seems like it should point to this instead: https://github.com/tomchentw/react-google-maps/blob/master/src/app/pages/async/AsyncGettingStartedExample.js

Please refer to Getting Help section in the README (or #469).


Enable managers from category No category

Following commit enables managers asdf, fvm, hermit, homebrew, nix, osgi, pre-commit, vendir. There are 3 managers left in this category (copier, gleam, mise), which are currently not available and require a rebase of renovate project.
A Google sheet  shows details of dependencies of each manager. Some managers require to set an environment variable with a Github token. The controller code should be sufficient to provide auth for GITHUB_COM_TOKEN, I was not able to test locally if it works for the HERMIT_GITHUB_TOKEN as well.
https://github.com/konflux-ci/mintmaker-renovate-image/pull/50 Must be merged together with this change.
Closes CWFHEALTH-3187.

Looks good +1


Make the dashboard page reponsive

Make the dashboard page responsive for atleast tablets and pc view, currently its only good for laptops and has no responsiveness.

Hi @ShubhamPatel2305 , I'd like to help with this issue. Could you please assign it to me?


Text measurement with TextTrimming="CharacterEllipsis" are wrong

Describe the bug
We were using the nightly build 0.10.999-cibuild0020667-beta then switched to 0.10.999-cibuild0021055-beta.
After this update we noticed that the text box with TextTrimming="CharacterEllipsis" is now trimming the text although there is enough available space to it to grow (width direction).

this effect would disappear on a monitors with resolution
- 1920 x 1080 (125% scaling)
the effect will be noticed again on monitors with resolutions
- 1920 x 1080 (100% scaling)
- 3840x2160 (150% scaling)
Desktop (please complete the following information):

OS: Windows 11.

Additional context
we solved the issue (at least in our test machines) by inflating the finale size in ArrangeOverride
    protected override Size ArrangeOverride(Size finalSize)
    {
        var measuredSize = base.ArrangeOverride(finalSize.Inflate(new(1)));

        return measuredSize;
    }

I can't repro the issue with the information you gave me. Please try to reproduce it in the Sandbox or some other minimal project.


SPIR-V: BuiltIn variables use the Input storage class

The OpenCL SPIR-V Environment Specification was updated to mandate that
all variables decorated with BuiltIn must be in the Input storage
class, see https://github.com/KhronosGroup/OpenCL-Docs/pull/278.
Global variables with the Input storage class have to be listed in the
entry points’ interface, which was also taken care of in this commit.

FYI, I ran spirv-val on all the updated binaries and didn’t get any validation errors (besides the one tracked in https://github.com/KhronosGroup/SPIRV-Tools/issues/3322 about NonWritable), and tested a few binaries on an OpenCL implementation but not all of them.

This change made me think a bit more about the spec change (https://github.com/KhronosGroup/OpenCL-Docs/issues/269#issuecomment-626403247), but regardless of the thoughts there I think this change makes sense.  It brings the spirv_new tests closer to what current tooling produces.

LGTM

@StuartDBrady You may want to take a look at this change.

Friendly ping

Thank you for approving the changes and merging.


Bug fixes in surface glint model

Updates to windowing in analytical line + glint model to allow glint surface to work for EMIT and other sensors

Thanks for the updates, @reginaeckert! Checks are failing because the workflows in my fork are really out of date, so merging this PR anyway.


BUG Remove special symbols from Ken embeddings

Fix #599

Thanks, I think this is ready to be merged then. Not to confuse with #602 which maybe needs some additional work on :)

Thanks. Maybe a small changelog entry, so as not to surprise users

Actually now the main changes were made with #602, merging this just to update the changelog..


API log request ID and response body content (debug only)

This pull-request adds API request ID (header) and response body content logging.
The Sensu API will generate a request ID if the HTTP client does not provide one. The request ID can be used to trace a HTTP request via the Sensu API log.
We are back-porting these changes to get them into an Enterprise patch release sooner.

Ignoring the Ruby 2.2 Travis CI failure, it's due to a Bundler version issue that was fixed in a later release.


Adjust the slider value to include current_size

Description
I am not sure how this could be implemented best, therefore I will leave it here as a request and I am more than happy to implement the change after some discussion :) I put a first draft here for a start.
When creating a Point layer the size slider is limited to be between 0 and 100.
However, in our field of cryo-em we would like to visualize sizes of up to 1000 (or more dependent on the protein) to verify the centering of the image within the point.
Therefore, I wrote a plugin to set the size of the respective points and the value of current_size so that new points added will have the same value. However, this means that the current_size value and the respective slider value are out of sync, which is very confusing for the user.
In my initial draft I propose to adjust the slider limits so that the current_size value is included in the range and therefore properly displayed.
I also noticed that the way events are emitted in the points layer are kind of random!?
Some are only emittered when _update_properties is True and  points are selected (like current_edge_width and current_size) but others are just always emitted (like current_edge_color). Therefore I needed to update the event manually in my test, which feels kind of wrong but maybe there is more to it :)
Type of change

[X] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

There is a test in the points layer that sets a list for the current_size attribute, but the method documentation does not expect lists at this point but is of type Union[None, float]. https://github.com/mstabrin/napari/blob/56d6e5ac6cd988832d2488a922b2efac237c8401/napari/layers/points/_tests/test_points.py#L2428
Therefore, I needed to add some extra list logic.

Yes, sorry, Fixed it now ^^

I am not sure how this could be implemented best, therefore I will leave it here as a request and I am more than happy to implement the change after some discussion :)

So just putting some ideas around.

photoshop and some other graphic software have logarithmic sliders for brush size and alike. At least it is non-linear as generally you only care about a granularity proportional to your current size – we could go with more complex than log with a range that is globally exponential but tappers around current value for precision ?
instead of having max = max(100, current+1), should the max be proportional to current value ? On a linear scale having max = max(100, current*4/3) seem reasonable, on a log scale we could even easily go to max = max(100, current*10) That would make it easy to reach large size even with manipulating the slider.

@Carreau I like the idea :)
Shall we keep the +1 version for now to fix the current situation and open another PR to rethink the slider scaling behavior?
It sounds like something that easily can take a longer time due to the testing.
I did a quick test and the slider just went crazy so from my side it requires a lot more thinking ^^

Shall we keep the +1 version for now to fix the current situation and open another PR to rethink the slider scaling behavior?
It sounds like something that easily can take a longer time due to the testing.
I did a quick test and the slider just went crazy so from my side it requires a lot more thinking ^^

That sounds reasonable to me.


Fix : DREMIO to supported dbt profile types

Problem
The dbt provider has a hardcoded set of supported dbt connection types FIX. This adds dremio to the list.
Closes: https://github.com/OpenLineage/OpenLineage/issues/2668
Reference Review : #2671
Solution
Add an if-elif clause for DREMIO to DbtArtifactProcessor.extract_namespace for profile (host or software_host)

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

One-line summary:
Add support for dbt-dremio, solving https://github.com/OpenLineage/OpenLineage/issues/2668 and reference review #2671
Checklist

[x] You've signed-off your work
[x] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[x] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

@JDarDagran , @mobuchowski
Fixed : DREMIO to supported dbt profile types PR as per review comments.
Please re-review and approve


[GUI] Installer: going back to change the Network on the installer doesn't change the network connection directory.

If from this screen i go back to change the network, once i'm back here it's still "testnet3" also I selected another one.

Did this happen following https://github.com/wizardsardine/liana/pull/932? For me, the address and cookie path are now updating when I change network.

Oh, yes on V4. Great to see you guys fixed it already
On Fri, Feb 2, 2024, 06:40 jp1ac4 @.***> wrote:

Did this happen following #932
https://github.com/wizardsardine/liana/pull/932? For me, the address
and cookie path are now updating when I change network.
—
Reply to this email directly, view it on GitHub
https://github.com/wizardsardine/liana/issues/946#issuecomment-1923230847,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADWNZE2XPMTJCMEUHY5EEULYRSJ5LAVCNFSM6AAAAABCQABAR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTGIZTAOBUG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

just tested, seems fixed on master, closing issue


Update Invoke-DbaDbLogShipping.ps1

Typing mistake

Type of Change

[ X] Bug fix (non-breaking change, fixes #)
[ ] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Fantastic! These look like solid changes. Will merge once tests pass. Thanks so much, @AartHoevenberg 👍

Thanks again 🎉


erases all styles for material-ui components

Wrapping any material-ui component in a shadow root element (i.e. <root.div>) causes all the styles on that mui component to no longer show.

nvm

sorry, yes, this seems to be like a real issue. Although it may actually be a feature, not a bug. Please excuse my ignorance, i am new to React and programming in general.

That’s all right @meerkat-citronella.
Could you setup an example with Codesandbox please? Might just be a case of adding the Material UI CSS to the shadow root rather than globally.

sure can, thanks for the prompt reply!
here: https://codesandbox.io/s/amazing-goldstine-v57ec?file=/src/App.js

i also tried implementing this solution: (last answer) . The wrapper fixes the styles on the table, but not the button on codesandbox

Good effort on the wrapping, but it does seem as though the button's styles are still applied outside of the shadow boundary, which is why it's unstyled.
We do have a couple of wrappers for styled-components and @emotion so I'll take a look at also implementing a material-ui version so hopefully you'll just be able to import root from 'react-shadow/material-ui' but that button still being unstyled despite the explicit StyleSheetManager is concerning.

Have a play with<EMAIL_ADDRESS>please – I've updated your example and everything seems to be working well.
I don't really use Material UI myself though, so there could be further problems. In the Material UI repo there are a few mentions of shadow DOM compatibility issues, but some may have been resolved already.
Also I'm not sure how to implement server-side rendering support for Material UI, so that's something else for me to look into, as their StylesProvider requires you pass in the insertionPoint which you wouldn't have server-side.

Hey man, thanks for the solution. It works pretty well. Just wanted to follow up a bit... pulling back the curtain, the way that my team is trying to implement this is as part of a chrome extension. The extension targets input elements on the page, and then whenever an input is clicked on, it creates a dropdown with popper.js and fills it with some data. We came across react-shadow because we are trying to keep the dropdown styles consistent no matter what the styles on the page are; our idea was to render the dropdown into an instance of <root.div>. It seems like the fix you have works fine on the first render, but on subsequent renders, the styles are still stripped. See the codesandbox for example (just click on the inputs to show the dropdown). My hunch is that it has something to do with how the shadow DOMs are interacting with one another... one can never actually delete an instance of a shadow DOM, right?
I don't expect you to fix our specific implementation of your module, you've been enough help already, but just wanted to let you know how it's being used if it's helpful to you at all. I think we are just going to use styled-components and style all the tags manually, instead of using some library. But thanks for your help anyway, cheers!

I setup a simpler example to re-render on click, and it does seem to maintain the styling. Suggests there may be something quirky in your example that's breaking the styles somehow?

I didn't explain myself correctly lol. I said 'render' and 'subsequent render' but what I really meant was that there are still problems when we have more than one instance of a shadow root. I extended your simpler example to show what I'm talking about.

Oh. Yah, in that case it looks to be an issue with Material UI only paying attention to the first insertionPoint — on second record it assumes it's already applied the styles, and so doesn't (re)-apply them to the other insertionPoint.
Hmm.

We were able to work with this and implemented it. Thanks for all your help!

There is a problem with the material-ui style not being applied to Dialog components.
What is the solution to this problem?
Here is simple example: https://codesandbox.io/s/recursing-star-gqx6p?file=/src/App.js

There is a problem with the material-ui style not being applied to Dialog components.

You could use the container prop on Modals, which Dialogs inherit. Just provide anything inside the shadow root.


Release Eventing Kogito 1.2.0 on OLM

Prepare manifests to release 1.2.0 on OLM

Related PRs:

https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/733
https://github.com/k8s-operatorhub/community-operators/pull/682

/lgtm


Remove HTML-safe from I18n

Replace with _html names that are escaped internally
This removes a brakeman XSS warning

interesting 👍


Using DownloadMore jumps the chart on the X axis, it doesn't keep still.

Can I replace the data array with a new one or should I mutate the existing array?

Closed because I don't have a reproducible small example


Adding additional headers to post operation

I'm uploading a file to a business account, so I need to add a header
'Dropbox-Api-Select-User'=> DROPBOX_MEMBER_ID
Here's the error, fyi:
Error in call to API function "files/upload": This API function operates on a single Dropbox account, but the OAuth 2 access token you provided is for an entire Dropbox Business team.  Since your API app key has team member file access permissions, you can operate on a team member's Dropbox by providing the "Dropbox-API-Select-User" HTTP header or "select_user" URL parameter to specify the exact user https://www.dropbox.com/developers/documentation/http/teams.
Is there a good way to add a header to a file upload?

Additional headers cannot be added if you're using the API methods directly (upload()  in your case). However, you can create a DropboxRequest object including any headers (Dropbox-Api-Select-User) you wish to send along with the request, either through the constructor or the setHeaders() method.
Then, send the DropboxRequest object directly through the sendRequest() method on the DropboxClient class's object, which can be obtained from the Dropbox class's object by calling the getClient() method.
Here's how you can achieve the above:
// Dropbox
$dropbox = new Dropbox(..);

//Access Token
$accessToken = "you-access-token";

//Make Dropbox File
$dropboxFile = $this->makeDropboxFile("/path-to-your-file.txt");

// Path on Dropbox to upload the file to
$path = "/my-folder"

//Set the path and file
$params = ['path' => $path, 'file' => $dropboxFile];

// Custom Headers
$headers = ['Dropbox-Api-Select-User'=> 'DROPBOX_MEMBER_ID'];

//Make a DropboxRequest object
$request = new DropboxRequest("POST", "/files/upload", $accessToken, "content", $params, $headers);

//Send Request through the DropboxClient
//Fetch the DropboxResponse
$dropboxResponse = $dropbox->getClient()->sendRequest($request);
// @see https://github.com/kunalvarma05/dropbox-php-sdk/blob/master/src/Dropbox/DropboxResponse.php
$body = $dropboxResponse->getDecodedBody();

//Make and the Model
$fileMetadata = new FileMetadata($body);

Works! Thanks so much.


Standardize "OS" to "system"

Some strings, particularly those for settings, use the term "OS", and some use "system". We should use the same term in all cases. "System" is preferred.

I have time to drop the usage of OS from strings related to the authentication broker. I don't have time to work on other strings (proxy settings, AzCopy proxy settings, OS theme settings, locale settings, etc.)


Merge refs/heads/feature/no-redis into alpha

Merge refs/heads/feature/no-redis into alpha

This PR has been merged into alpha and tagged as 1.5.49-alpha-202303252016. Thanks for your contribution!


We have too many wine editions

Issue description
Disclosure: I need a configuration which is not built on Hydra (full+staging) so I have an interest in seeing it supported.
Currently we have:

wineMinimal
wine
wineFull
wineStable
wineUnstable
wineStaging

wineMinimal, wine and wineFull differ in supported features while wineStable, wineUnstable and wineStaging use wine feature set while following different release branches. This seems both excessive and not covering enough:

People who want to have the latest and greatest features run wineStaging. wine resolves to the stable channel by default. Is wineUnstable actually used much?
People who try to run various applications may just run wineFull to avoid thinking about what's supported (for example we only have gtkSupport and gstreamerSupport in wineFull while the former is needed for GTK theming (yay, Windows apps are no longer ugly!) and latter is wanted for a range of games). Default wine is a middle ground. What case is covered by wineMinimal?

IMHO we should just make wine = wineFull and drop current wine and wineMinimal. I don't think wine's closure size is of such a big importance to split it into three different feature sets because in my mind it belongs (subjectively) to "big desktop apps". I'd also stop building wineUnstable but I'm less keen on that. This way we'll just have full-featured wineStable, maybe wineUnstable and wineStaging (that's what I'm interested in personally) built on Hydra; it's both less things to build and covers new cases.
To point it out again it's very subjective, so let's discuss this.
cc @bendlas @avnik @FRidh
Closure sizes (staging for no particular reason):

wineMinimal.override { wineRelease = "staging"; } 668M
wine.override { wineRelease = "staging"; }: 945M
wineFull.override { wineRelease = "staging"; }: 1.3G

Technical details

Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion) 9ab21a88b2ecd02c53fe2d8cdcbf864c737d90bf

we probably also want to enable 64-bit by default on x86_64. The 64-bit variant can also run 32-bit application: https://wiki.archlinux.org/index.php/Wine

wineFull is the kitchen sink for everything that can be enabled in wine
I have no issue with making this the default, but watchers of the closure size might.
wineMinimal is the smallest configuration that allows wine to compile
I have also no issue with making this the default, but dependents of wine might.
wine is the configuration we had before I factored out the config flags
I kept it, because I didn't want to break any dependents while maintaining closure size. I haven't evaluated whether wine is a good balance between functionality and closure size. I thought it might be, as it has been the default for a while.
wine64 can, in fact, not run 32bit code
For this, a combined variant called wineWow is needed with both binaries. This, in effect, doubles the closure size.

@edolstra has already reverted my patch making wineWow the default on 64bit, because of closure size
And for good reason too: win64 support in wine is really crappy and most win64 apps won't work anyway

wineUnstable and wineStaging are separated in the wine developer community with an explicit remark that not all staging patches are unstable candidates. I don't know the reasons for this separation, but I'd also rather not get in the middle of that discussion.

All that said, I'm all for cutting down on top-level wine derivations, if we can. Maybe a winePackages cellar is justified?

Oh, I forgot to mention: I checked out if there are any packages that use wine -- there are some that do (airwave, pipelight, playonlinux) but no that use wineMinimal`.

Yeah, I created wineMinimal as the baseline to incrementally enable configuration flags on.

About the cellar: it sounds good (at least for allowing people to use shorthands instead of .overrides when they need a specific configuration). Still, the question of what do we want in the top level persists...

In that case: Just wine and winePackages.

Good idea but let me rephrase the question then: what do we want to build on Hydra? wineStaging is useful for running games so it should probably be built in some configuration. There's also question of what feature sets do we want to build. Wine is a big beast so leaving users without prebuilt binaries is bad.

I see I'd propose two hydra builds:

sysadminsWine: The minimal configuration to support our dependent packages and run boring apps like MS Word reasonably well.
gamersWine: wineFull + staging + wineWow

(please don't call any actual packages "sysadmin swine" or "gamer swine" ;-) )

Sounds good to me! We could just call those wine and wineStaging respectively to avoid swine jokes :)
Let's wait for other opinions to arrive for a few days; I can prepare a patch later.

I did use wineUnstable because didn't know wineStaging is the most recent version.

On Thu, May 25, 2017 at 01:08:13AM -0700, Danylo Hlynskyi wrote:

I did use wineUnstable because didn't know wineStaging is the most recent version.

wineStaging is set of experimental patches, some of them unmerged for
years.

See #26152.


Implementation of Job-Forker

What this PR does / why we need it:
Implements the job-forker described in #393
It does so by using a newly created package githubinteractor, which simplifies the cloning, and pushing of changes in repositories.
It was requested by @oliver-goetz to use at a later point in time.
The vendoring needed to be adjusted and updated to make it possible to test the changes with ginkgo
Which issue(s) this PR fixes:
Fixes #393
Special notes for your reviewer:
The prowjob-configuration for running this periodically isn't implemented yet, as the image has to be built and pushed to a container repository first

/retest-required

/kind enhancement


WSL2-Linux-Kernel repository mess

Version
Microsoft Windows [Version 10.0.19044.1466]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps
Clone  https://github.com/microsoft/WSL2-Linux-Kernel.git
Expected Behavior
No errors
Actual Behavior
PS C:\GitHub> git clone https://github.com/microsoft/WSL2-Linux-Kernel.git
Cloning into 'WSL2-Linux-Kernel'...
remote: Enumerating objects: 8970371, done.
remote: Total 8970371 (delta 0), reused 0 (delta 0), pack-reused 8970371R
Receiving objects: 100% (8970371/8970371), 1.66 GiB | 10.52 MiB/s, done.
Resolving deltas: 100% (7579929/7579929), done.
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.c'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Checkout fails with:
PS C:\GitHub\WSL2-Linux-Kernel> git checkout linux-msft-wsl-5.10.y
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.c'
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.h'
error: invalid path 'include/soc/arc/aux.h'
error: The following untracked working tree files would be overwritten by checkout:
        .clang-format
        .cocciconfig
        .get_maintainer.ignore
        .gitattributes
        .gitignore
        .mailmap
        COPYING
        CREDITS
        Documentation/.gitignore
        Documentation/ABI/README
        Documentation/ABI/obsolete/sysfs-bus-usb
        Documentation/ABI/obsolete/sysfs-class-dax
        Documentation/ABI/obsolete/sysfs-class-net-batman-adv
        Documentation/ABI/obsolete/sysfs-class-net-mesh
        Documentation/ABI/obsolete/sysfs-class-typec
        Documentation/ABI/obsolete/sysfs-cpuidle
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-arvo
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-isku
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-konepure
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-lua
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-ryos
        Documentation/ABI/obsolete/sysfs-driver-hid-roccat-savu
        Documentation/ABI/obsolete/sysfs-driver-intel_pmc_bxt
        Documentation/ABI/obsolete/sysfs-firmware-acpi
        Documentation/ABI/obsolete/sysfs-gpio
        Documentation/ABI/obsolete/sysfs-kernel-fadump_enabled
        Documentation/ABI/obsolete/sysfs-kernel-fadump_registered
        Documentation/ABI/obsolete/sysfs-kernel-fadump_release_mem
        Documentation/ABI/obsolete/sysfs-selinux-checkreqprot
        Documentation/ABI/obsolete/sysfs-selinux-disable
        Documentation/ABI/removed/devfs
        Documentation/ABI/removed/dv1394
        Documentation/ABI/removed/ip_queue
        Documentation/ABI/removed/net_dma
        Documentation/ABI/removed/o2cb
        Documentation/ABI/removed/raw1394
        Documentation/ABI/removed/sysfs-bus-nfit
        Documentation/ABI/removed/sysfs-class-rfkill
        Documentation/ABI/removed/sysfs-kernel-fadump_release_opalcore
        Documentation/ABI/removed/sysfs-kernel-uids
        Documentation/ABI/removed/video1394
        Documentation/ABI/stable/firewire-cdev
        Documentation/ABI/stable/o2cb
        Documentation/ABI/stable/syscalls
        Documentation/ABI/stable/sysfs-acpi-pmprofile
        Documentation/ABI/stable/sysfs-bus-firewire
        Documentation/ABI/stable/sysfs-bus-mhi
        Documentation/ABI/stable/sysfs-bus-nvmem
        Documentation/ABI/stable/sysfs-bus-usb
        Documentation/ABI/stable/sysfs-bus-vmbus
        Documentation/ABI/stable/sysfs-bus-w1
        Documentation/ABI/stable/sysfs-bus-xen-backend
        Documentation/ABI/stable/sysfs-class-backlight
        Documentation/ABI/stable/sysfs-class-infiniband
        Documentation/ABI/stable/sysfs-class-rfkill
        Documentation/ABI/stable/sysfs-class-tpm
        Documentation/ABI/stable/sysfs-class-ubi
        Documentation/ABI/stable/sysfs-class-udc
        Documentation/ABI/stable/sysfs-devices
        Documentation/ABI/stable/sysfs-devices-node
        Documentation/ABI/stable/sysfs-devices-system-cpu
        Documentation/ABI/stable/sysfs-devices-system-xen_memory
        Documentation/ABI/stable/sysfs-driver-aspeed-vuart
        Documentation/ABI/stable/sysfs-driver-dma-idxd
        Documentation/ABI/stable/sysfs-driver-dma-ioatdma
        Documentation/ABI/stable/sysfs-driver-firmware-zynqmp
        Documentation/ABI/stable/sysfs-driver-ib_srp
        Documentation/ABI/stable/sysfs-driver-mlxreg-io
        Documentation/ABI/stable/sysfs-driver-qla2xxx
        Documentation/ABI/stable/sysfs-driver-speakup
        Documentation/ABI/stable/sysfs-driver-usb-usbtmc
        Documentation/ABI/stable/sysfs-driver-w1_ds28e04
        Documentation/ABI/stable/sysfs-driver-w1_ds28ea00
        Documentation/ABI/stable/sysfs-firmware-efi-vars
        Documentation/ABI/stable/sysfs-firmware-opal-dump
        Documentation/ABI/stable/sysfs-firmware-opal-elog
        Documentation/ABI/stable/sysfs-fs-orangefs
        Documentation/ABI/stable/sysfs-hypervisor-xen
        Documentation/ABI/stable/sysfs-kernel-notes
        Documentation/ABI/stable/sysfs-module
        Documentation/ABI/stable/sysfs-transport-srp
        Documentation/ABI/stable/thermal-notification
        Documentation/ABI/stable/vdso
        Documentation/ABI/testing/configfs-acpi
        Documentation/ABI/testing/configfs-iio
        Documentation/ABI/testing/configfs-most
        Documentation/ABI/testing/configfs-rdma_cm
        Documentation/ABI/testing/configfs-spear-pcie-gadget
        Documentation/ABI/testing/configfs-stp-policy
        Documentati
Aborting

Diagnostic Logs
No response

This is not an issue with the WSL2-Linux-Kernel repository. AUX is reserved filename in Windows, regardless of file extension. Files cannot be created named AUX or AUX.*
From Microsoft docs:

Do not use the following reserved names for the name of a file:
CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. Also avoid these names followed immediately by an extension;

This can be reproduced with the upstream kernel:
PS C:\Users\hayde\Downloads> git clone --depth 1 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Cloning into 'linux'...
remote: Enumerating objects: 79574, done.
remote: Counting objects: 100% (79574/79574), done.
remote: Compressing objects: 100% (77586/77586), done.
remote: Total 79574 (delta 5604), reused 17121 (delta 1164), pack-reused 0Receiving objects: 100% (79574/79574), 214.06Receiving objects: 100% (79574/79574), 215.72 MiB | 7.99 MiB/s, done.

Resolving deltas: 100% (5604/5604), done.
error: invalid path 'drivers/gpu/drm/nouveau/nvkm/subdev/i2c/aux.c'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Work from the wsl file system, https://docs.microsoft.com/en-us/shows/tabs-vs-spaces/wsl2-code-faster-on-the-windows-subsystem-for-linux

As sirredbeard said this is indeed a Windows filesystem limitation.
You can clone this repository within WSL though.


Depend on a no_std compatible version of chrono

I'm running into a dependency conflict where I can't depend on uom because it depends on num-traits, which has been made no_std compatible since the most recent version of chrono.  The problem is, the released version of chrono depends on a conflicting version of num-traits that requires std.  Why cargo can't sort out conflicts of this sort is beyond me, but since it can't, would cortex-m-rt switching to the github version of chrono be permissible (at least until chrono gets their act together and cuts a no_std compatible release)?
To recreate the problem for yourself, all you have to do is start a blank no_std library project, add a dep for
uom = { git = "https://github.com/iliekturtles/uom", branch = "dev-num-std", default-features=false, features =["si", "f32"] }

verify that xargo can build it, then add a dep for cortex-m-rt = "*" and try to build again

would cortex-m-rt switching to the github version of chrono be permissible (at least until chrono gets their act together and cuts a no_std compatible release)?

I'd like to note that crates.io doesn't accept crates that depend on git repositories, so switching to chrono's GitHub version would effectively block new versions of cortex-m-rt from being released.

...Oh, I definitely didn't realize that, yeah, that's definitely not worth it!

https://crates.io/crates/chrono is now at 0.4.1 which is no_std compatible. \o/?

Note that because of https://github.com/rust-lang/cargo/issues/4866 it is not enough for chrono to support no_std to handle every case. Dropping it is the right approach.


[FEATURE]: Support for MongoDB.

Describe what you want
I was thinking to start mongoDB support for DrizzleORM. After killing SQL market, I think drizzle should go multi-db mode. I want to start this with mongoDB. OG mongoose lib feels like deprecation. LMK how to start with this idea..
Thanks and keep building.

Same thoughts on mongoose. Its awful when you want to work with typescript.

I would like someone from the core team, such as @AndriiSherman, to confirm this. It's important for the OG developers to be aware and aligned if I proceed with creating something like this..

I only got light confirmation on twitter. Should I start?

any update on this?

I can contribute as well

I am waiting for confirmation. .. There is no point of creating something, if it won't get merged..

+1 on the mongodb support...Prisma.io performance is killing me 🫠

Drizzle is an ORM for SQL and it's very tightly coupled with that ecosystem. Drizzle has yet to integrate many features from Postgres, MySQL and SQLite, not to mention requests about supporting MSSQL, Oracle DB, Duck DB, etc. All of this will be worked on before seriously considering branching out, because if we add support for something like Mongo then people will start requesting support for other NoSQL databases.
The team might consider doing something with NoSQL databases in the future, but this will likely be it's entirely separate package as, again, Drizzle is a SQL ORM first and foremost

+1 on the mongodb support...Prisma.io performance is killing me 🫠

Can you please explain where the prisma.io performance is giving an issue?  I am using it in all my projects.

I am working with Prisma and MongoDB as well, but I want to try Drizzle. I'm using MongoDB for easy deployment on Vercel, but I guess I just need to move to PostgreSQL. 😅


@(TargetPathWithTargetPlatformMoniker) outside GetTargetPath

Some projects (and some NuGet packages) override GetTargetPath, and they
can't be expected to keep up with changes in the metadata now returned
by it.
This change moves the computation of the item returned from GetTargetPath
and Build into its own target (recycling
GetTargetPathWithTargetPlatformMoniker), so that it will still be
created by a project that overwrites GetTargetPath.
Fixes #2183.

FYI @agr
FYI @pilchie -- this is an alternate way to approach the change you made two years ago to simplify GetTargetPathWithTargetPlatformMoniker. I recently changed the Build target to return the same metadata as the GetTargetPath target, so projects that overrode GetTargetPath were ignored when ProjectReferenced because the item never got computed.

Sounds good to me.

Got confirmation from @agr that this fixes the problem.


Suggestion:  Add a "ALL" filter" on the webpage

On the Webpage, add the filter "All" to make the filter system more understable.
It's empty and not explicit

fix on 0.1.10


Added request response example

Added a basic request response example

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


add the ability to load firmware.bin (firmware.nds renamed extension) in the Menu

I changed my mind about this, I will test and see if it works once I get home and it may be merged


[feat] Improved AI Chat Scrolling

Applying these conditions to our AI chat for the best user experience.
LLM Scrolljacking Manifesto

If the user scrolls to bottom of generated text while still generating, enable auto-scroll
Stop auto-scroll if the user manually scrolls up at any point & do not turn it back on until the user manually scrolls to bottom
On mobile, stop auto-scroll if the user's finger is touching the screen
If you choose to enable auto-scroll by default, stop auto-scrolling when the start of the response gets to the top of the visible window.

Performance tips

Do not trigger auto-scroll callback on every token, only set new scroll position (or animate) when height of the container changes.
If using React hooks, your state machine will depend on re-renders which can add jank due to latency. Use a class component & class variables to keep track of scroll state independent of renders.

From: https://x.com/mayfer/status/1858698456086282583?s=46&t=pd3uh4BnhkMVspxVU9blSQ

hey,can you assign me this?

For sure go for it @tasbi03

Solved


[cloud_firestore] iOS build failed

Describe the bug
After adding cloud_firestore: any to pubspec and launching it, Flutter fails to build the IOS App and  outputs the following:
Launching lib/main.dart on iPhone 8 in debug mode...
Running pod install...
Xcode build done.                                           50.8s
Failed to build iOS app
Exited (sigterm)
Could not build the application for the simulator.
Error launching application on iPhone 8.

To Reproduce
Steps to reproduce the behavior:

Run "flutter create (projectname)"
Open pubspec.yaml
Add "cloud_firestore: any" to dependencies
flutter pub get
Run "flutter run"
Get Error Message

Expected behavior
I expected it, to build the ios App successfully and then open the app in the Xcode Simulator.
Additional context
I tried different versions of cloud_firestore, Flutter and Cocoapods.
And when I put the GoogleService-Info.plist in the Runner/Runner folder and run it i get the following Error
Xcode's output:
↳
    /Users/sav/workspace/github/ios/Pods/gRPC-C++/src/cpp/server/async_generic_service.cc:19:10:
    fatal error: 'grpcpp/generic/async_generic_service.h' file not found
    #include <grpcpp/generic/async_generic_service.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    /Users/sav/workspace/github/ios/Pods/gRPC-C++/src/cpp/server/async_generic_service.cc:19:10:
    note: did not find header 'generic/async_generic_service.h' in framework 'grpcpp' (loaded
    from '/Users/sav/workspace/github/build/ios/Debug-iphonesimulator/gRPC-C++')
    1 error generated.
    /Users/sav/workspace/github/ios/Pods/gRPC-C++/src/cpp/server/channel_argument_option.cc:19:10
    : fatal error: 'grpcpp/impl/channel_argument_option.h' file not found
    #include <grpcpp/impl/channel_argument_option.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    /Users/sav/workspace/github/ios/Pods/gRPC-C++/src/cpp/server/channel_argument_option.cc:19:10
    : note: did not find header 'impl/channel_argument_option.h' in framework 'grpcpp' (loaded
    from '/Users/sav/workspace/github/build/ios/Debug-iphonesimulator/gRPC-C++')
    1 error generated.
    /Users/sav/workspace/github/ios/Pods/gRPC-C++/src/cpp/client/client_interceptor.cc:19:10:
    fatal error: 'grpcpp/impl/codegen/client_interceptor.h' file not found
    #include <grpcpp/impl/codegen/client_interceptor.h>
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    /Users/sav/workspace/github/ios/Pods/gRPC-C++/src/cpp/client/client_interceptor.cc:19:10:
    note: did not find header 'impl/codegen/client_interceptor.h' in framework 'grpcpp' (loaded
    from '/Users/sav/workspace/github/build/ios/Debug-iphonesimulator/gRPC-C++')
    1 error generated.
    note: Using new build system
    note: Building targets in parallel
    note: Planning build
    note: Constructing build description

Flutter doctor
Run flutter doctor and paste the output below:
[✓] Flutter (Channel stable, 1.20.0, on Mac OS X 10.15.6 19G73, locale en-CH)
    • Flutter version 1.20.0 at /Users/sav/development/flutter
    • Framework revision 840c9205b3 (33 hours ago), 2020-08-04 20:55:12 -0700
    • Engine revision c8e3b94853
    • Dart version 2.9.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/sav/Library/Android/sdk
    • Platform android-30, build-tools 30.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.13.2

[✓] Connected device (1 available)
    • iPhone 8 (mobile) • A4587B9D-A8A4-462D-A1DC-5A38AA6B2E2B • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)

• No issues found!

The problem was gRPC itself. It probably failed cloning all the files to the cached version of gRPC-C++. I deleted the cached version and now it works.

The problem was gRPC itself. It probably failed cloning all the files to the cached version of gRPC-C++. I deleted the cached version and now it works.

Hey @NoahVersace , I faced the similar issues. Could you share more about where to deleted the cached version of gRPC-C++ ?
Thanks a lot !

Me Too @NoahVersace

The problem was gRPC itself. It probably failed cloning all the files to the cached version of gRPC-C++. I deleted the cached version and now it works.

Hey @NoahVersace , I faced the similar issues. Could you share more about where to deleted the cached version of gRPC-C++ ?
Thanks a lot !

Hey @shingsoso @YazeedAlKhalaf
What I did is:

Open terminal
Enter cd /Users/yourusername/Library/Caches/CocoaPods/Pods/Release/
Enter open .
Delete gRPC-C++
Go back to your flutter project, navigate in to the ios/Pods folder and delete gRPC-C++
Run your flutter app

Cocoapods will then detect, when trying to install the gRPC-C++ Pod, that there is no cached version and clone it again from its repository.
I hope this helps!

@NoahVersace
Thanks a lot, man! You literally saved hours of refactoring the project!
I really appreciate it, btw this is the project I am talking about. It is a flutter chatting app called "beast". Under development.

@NoahVersace
Thanks a lot, man! You literally saved hours of refactoring the project!
I really appreciate it, btw this is the project I am talking about. It is a flutter chatting app called "beast". Under development.
https://github.com/yazeedalkhalaf/beast
Nice, I'm very glad to hear that I could help and good luck with your project beast. 👍


Checkpoint averaging

This a script for checkpoint averaging adapted from Tensor2Tensor.
The question for discussion is: should it remain like this, or should it get only one argument - the experiment directory - and generate the averaged checkpoint there?

tl;dr: I am for the output_dir/output_path option (with default as a subdir of the original experiment dir).
IMO, it depends on what files are being created by the Saver.save method. I think that aside from the variables.data.* files, a new checkpoint file (containing the default model name) is also created which might create confusion, if the averaged model is saved in the same directory as the original models (or at least its the behavior in t2t, which I do not prefer).


Consistency between tracer and Cls cosmology

Currently, it seems possible to pass a given cosmology to build a tracer, and then use that tracer with a different cosmology to obtain Cls. Is there a way to prevent this inconsistency or at least issue a warning to the user?

@philbull Do you have any thoughts on this one?

I think there's a point in noting this in the documentation (that tracers hold some cosmology-dependent information) so people don't make that mistake, but there's only so much you can do to enforce consistency without losing modularity and ease of use (i.e. I wouldn't really implement any software measures to prevent this)

I second @damonge on this. We can't save people from themselves.
If we attach all of these methods to the cosmology struct, we will solve some of these issues. However ppl could still cheat the system.
Are we good to close this one @elisachisari ?

Any comments here or shall we close this?

Mmmmk. No comments since Nov 1 of last year. Closing. Feel free to reopen.


Running vLLM in docker in CPU only

Hello how can I run vLLM in CPU mode only with docker ?
Thanks for the help

Hi @delta-whiplash, NVIDIA or AMD GPUs are required to run vLLM. If you want to try vLLM, you use google colab with a T4 GPU for free.

Hi @delta-whiplash, NVIDIA or AMD GPUs are required to run vLLM. If you want to try vLLM, you use google colab with a T4 GPU for free.

Ok I understand do you know great inference software with CPU only to use I don't have big GPU to run Mistral 8x7b


[occm] Allow deleting LBs in ERROR status

What this PR does / why we need it:
In practice Octavia is quite an unreliable system. We should expect that load balancers will occasionally go into ERROR state for reasons as elaborate as race conditions and as simple as lack of resources to spawn a new Amphora VM.
This commit makes sure that we allow deleting LBs in ERROR state, so that Services served by such LBs could be deleted and their creation retried.
Obviously there's room for improvement, as we should probably detect LBs going into ERROR and attempt to delete and recreate them ourselves, but this patch is a low hanging fruit fix for the issue.
Which issue this PR fixes(if applicable):
fixes #2036
Release note:
NONE

/ok-to-test

/lgtm

/lgtm

/approve


Rust-lang crate ownership policy

The Rust project publishes a lot of crates, and it's not always clear what their guarantees are. This aims to start an endeavor to categorize these crates and introduce a policy for consistently messaging their raison d'être and guarantees.
This policy doesn't directly affect crates published by the wider ecosystem, however the results of such categorization will likely be very useful to the ecosystem for knowing what should and shouldn't be depended on.
:memo: Rendered :memo:

This looks great!  I'm wondering what the intent is around crates that have no team or are ambiguous? For example, mdbook does not have a formal team, just a set of maintainers. git2 is used heavily by Cargo, and maybe should be under the cargo team, but that is not clear.
What happens if a team dissolves or fades away? (Presumably some sort of transfer to core or another team and possibly deprecated or expatriated? Would core be responsible for that?)
It might be helpful to have some information on the process of creating and publishing a new crate.  The details don't need to be in the RFC, but perhaps the RFC could say that this information will be published on the forge? Right now, the process is roughly: for GitHub: ask infra to create a new repo or accept a transfer of an existing one. For crates.io: publish under a personal account, then invite rust-lang-owner, and hope someone behind that alias accepts the invite (or infra sets up the publishing).  This process can be a little ad-hoc and difficult, so it might be nice to make it clearer and easier.
I prefer to keep publishing rights to an absolute minimum instead of allowing the entire team. Is infra willing to create additional GitHub sub-teams for that purpose? How does that work?

I'm wondering what the intent is around crates that have no team or are ambiguous? For example, mdbook does not have a formal team, just a set of maintainers. git2 is used heavily by Cargo, and maybe should be under the cargo team, but that is not clear.

I think an effort can be made to create a team/project group. E.g. I imagine mdbook fitting under devtools.
git2 can just be the cargo team if it's an "internal use", if it's an "intentional artifact" the cargo team can figure it out with the libs team. This RFC does not prescribe a particular choice, it asks the teams to figure it out -- I expect if this lands we will have a slow process of working through the crates and figuring a lot of this out.

The details don't need to be in the RFC, but perhaps the RFC could say that this information will be published on the forge?

Done, it's mostly a matter of process set by the infra team so it's not worth figuring out the details here

I prefer to keep publishing rights to an absolute minimum instead of allowing the entire team. Is infra willing to create additional GitHub sub-teams for that purpose? How does that work?

I think creating a foo-publish team is totally fine. This can again be included in the actual forge page, and doesn't need to be figured out here.

@HeroicKatora and myself been working on a tool that might be of use. It provides visibility into crate ownership for a given crate and all of its dependencies. https://github.com/rust-secure-code/cargo-supply-chain
I've added structured output support (currently in git), so you can create logic enforcing custom policies on top of it. I'd be happy to hear if it works or doesn't work for you. Feature requests are also welcome.

I suggest retitling this to make it more obvious. Something like

Add ownership policy for crates published by the Rust project

The current title sounds like it is talking about every crate.

Oops, my bad, it picked up the title from the commit

Looks great ^_^

@rfcbot merge

Tracking issue at https://github.com/rust-lang/rust/issues/88867

@Manishearth The file 0000-rust-crate-ownership.md should be renamed, and fixed to link to this PR, right?

Huh, I thought I did that

oh shoot

Fixed