Unifying CA signing interface

Currently the CA exposes two methods:

Sign(csrPEM []string) which is used by the GRPC server
Generate(name, namespace []string) which is used for generating
cert based on K8S service account.

However these two methods are very similar, and this PR removes the
second method completely. After this PR, the K8S secret controller
constructs a CSR locally and uses the Sign method to get a
certificate.
Release note:

NONE

@lookuptable: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
44799b7944d49300211a5468557017fb309d71f4
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lookuptable: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
8de0cfc6fcde3fa09ccb73277c05186d4e2d3057
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lookuptable: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
a4bee72b2137d03686257f3a9a7e5e1c491aa009
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@lookuptable: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/auth-presubmit.sh
732a3a1a8145c6e41bc7f544cb0d943c096492c2
link
/test auth-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/approve


readme,dockerfile,images: add images to repo and adjust links in readme

This fixes #51 by adding the images to a folder in the repository, not relying on an external source.
Additionally adding the new folder and images to dockerignore because we don't need them in the container

Thanks @RiRa12621!


NativeModules error on iOS in rn 0.16.0

Unable to resolve module NativeModules from projectdirectory/node_modules/react-native-share/index.ios.js: Invalid directory /Users/node_modules/NativeModules

+1

Hi @samuelkraft I had a PR #7 to fix the problem. For temporary solution, you can replace your package.json:
"react-native-share": "^1.0.4",
=>
"react-native-share": "lifuzu/react-native-share"
Hope can help you.

Thanks, your PR works! Hopefully this will be merged soon.

Can this be merged please ? :+1:

+1

+1

+1


Add statistics collection to mock_components/GenericSystem

When running simulations, it would be nice to add statistics collection to mock_components/GenericSystem. For example:

What is the average rate of incoming commands?
What is the average latency (from message stamp to message received)?
What is the standard deviation of time between messages?

I think it would also be nice to add a service call to trigger this data collection so it doesn't begin until the user is ready.
I don't have any immediate need for this but it would have been nice on a few projects in the past.
Bonus if this can be done on hardware as well without breaking realtime constraints.

Hi Andy,
In terms of functionality inside the framework, does it change something to collect this date in a hardware interface rather than in a dedicated controller ? We use some of what you describe here but in a controller version to test our setups what allows us to collect data also if running a real hardware and I am curious if we could expect some different results.

For https://github.com/ros-controls/ros2_control/pull/806 we used an instrumented JTC and instrumented mock hardware components


cChocoInstallerSet resource does not support AutoUpgrade switch

Would it be possible to add the AutoUpgrade switch from the single package installer resource (cChocoInstaller) to the set installer resource (cChocoInstallerSet)?

Yes it would. I marked this as up for grabs. 👍

Looks like it should be a pretty easy fix, however #96 is a blocking Bug. We will need to restore the functionality of the cChocoPackageInstallerSet.schema.psm1 before we can add new functionality

I've submitted a PR for #96 once that is accepted I can start working on this one

Whats the progress on this one? Like @jrdnr says it should be pretty easy to implement due to the fact that the cChocoPackageInstallerSet is based directly on the cChocoPackageInstaller.
@jrdnr are you looking in to this or should I give it a go?

@vidarw I think I had started working on it but didn't want to try to fix this w/o #96 being resolved, and that PR is still open, so I have not touched this in months.  Feel free to take this one.

Note that #96 is closed.


Fine-Tuning is currently available in Limited Preview for select customers only

When I try the Fine Tune API I am getting this error "Fine-Tuning is currently available in Limited Preview for select customers only". when will this be publicly available?

I’ve come across the “Fine-Tuning is currently available in Limited Preview for select customers only” error while trying to use the Fine Tune API. Could you let me know when it will be open to all users, or how I can apply to get access sooner?
Thanks!


[Tooling] Model responses are much slower than they should be in Model and Prompt Runners

Model responses are much slower than they should be in Model and Prompt Runners.
Bug in Genkit Tools version: 0.9.6
Here is a video demonstrating the experience:
https://github.com/user-attachments/assets/1e2ff334-fc99-4430-8d48-7bf4edabafa9
In summary, running a simple prompt in my code against Gemini 1.5 Flash takes a second or less to respond.
Running the exact same prompt in the DevUI against Gemini 1.5 Flash takes much longer, and sometimes never resolves.
Update
Might be related to https://github.com/firebase/genkit/issues/1455.
Looks like the response is being generated, but not shown until I take some sort of action like changing or setting the configurations.
https://github.com/user-attachments/assets/96d7eb92-9f13-4dbb-a96c-d19b0e6ed9ca

Fixed in https://github.com/FirebasePrivate/genkit-ui/pull/1172.


Remove Unicode Py2 shenanigans

This commit removes conditional StringIO import in a few source files as
well as fixes uploading unicode CSV-files.
Conditional import
To support both Py2 and Py3 we had conditional imports:
try:
	from io import StringIO
except ImportError:
	from cStringIO import StringIO

By moving to Py3-only we can drop these imports in favor of nice and
simple from io import StringIO.
Unicode issues with uploaded CSV files
By moving to Py3, it appeared that Django serves uploaded files as byte
files, not text files.  This forces us to encode upcoming files into
UTF-8 text files (which TextIOWrapper does).
UnicodeWriter removal
Helper class UnicodeWriter was required to make unicode CSV files,
because csv module from Python 2.x standard library couldn't handle
unicode files.
With migration to Python 3.x we can get rid of it, because now csv
module fully supports unicode files.

Please review, @gvwilson and @wking.
When this gets merged in, I'll rebase my https://github.com/wking/swc-amy/pull/3 PR. Then we should think about auth issue with empty passwords. Then (or simultaneously) we should fix tests for auth.

On Wed, Feb 04, 2015 at 09:34:54AM -0800, Piotr Banaszkiewicz wrote:

M workshops/util.py (53)

It looks like you're removing the blank line between stdlib and local
imports here 1.  I'd also keep it alphabetical by package, which
would look like:
import csv
from math import pi, sin, cos, acos
from io import TextIOWrapper, StringIO
from .models import Event, Role, Person
although I'm fine with alphabetizing by line:
from io import TextIOWrapper, StringIO
from math import pi, sin, cos, acos
import csv
from .models import Event, Role, Person
If request.FILES['file'] is in bytes, upload_person_task_csv should
take a codec-wrapped file, and the codec should come from the upload
headers.  Then you can drop the TextIOWrapper/StringIO business from
upload_person_task_csv.  Using getreader 2, that would be something
like:
_, params = cgi.parse_header(request['content-type'])
charset = params['charset']
stream = codecs.getreader(charset)(request.FILES['file'])
persons_tasks, empty_fields = upload_person_task_csv(stream)
Other than that, this looks good to me.

I will introduce removed blank line between imports. I group imports by source (standard library vs our code) and then order by appearance in the file, so I won't change the order.

If request.FILES['file'] is in bytes, upload_person_task_csv should take a codec-wrapped file, and the codec should come from the upload headers. Then you can drop the TextIOWrapper/StringIO business from upload_person_task_csv. Using getreader [2], that would be something like:
 _, params = cgi.parse_header(request['content-type'])
 charset = params['charset']

Is it the same as request.encoding? (See https://docs.djangoproject.com/en/1.7/ref/request-response/#django.http.HttpRequest.encoding and https://docs.djangoproject.com/en/1.7/ref/settings/#std:setting-DEFAULT_CHARSET).

On Wed, Feb 04, 2015 at 10:00:03AM -0800, Piotr Banaszkiewicz wrote:

I will introduce removed blank line between imports. I group imports
by source (standard library vs our code) and then order by
appearance in the file, so I won't change the order.

I prefer a more stable ordering, since you likely don't want to
reorder the imports just because you've shifted things around inside
the module.  But this really doesn't matter.

_, params = cgi.parse_header(request['content-type'])
charset = params['charset']

Is it the same as request.encoding?

Yeah, looks like it is :).  Definitely go with request.encoding then.
The fallback to DEFAULT_CHARSET is pretty hacky, since DEFAULT_CHARSET
is really about the response encoding, and should have nothing to do
with the request encoding.  I guess it's just used because you need
some sort of fallback for folks that don't set Content-Type on their
uploads.

Okay, so from what I tested: request.encoding is None when I upload files (for both UTF-16 and UTF-8).
So we cannot encode file based on request.encoding. And I have bad feelings about guessing the encoding from file contents.
Therefore I suggest that we default to UTF-8 encoding for uploded files.

On Wed, Feb 04, 2015 at 11:03:12AM -0800, Piotr Banaszkiewicz wrote:

Okay, so from what I tested: request.encoding is None when I
upload files (for both UTF-16 and UTF-8).

Hmm.  Looking at the docs again 1, HttpRequest.encoding seems to be
a write field.  Can you share the headers set by your upload?  You
should be able to see them in your browser's dev-tools network access.

Here you go.
For 'unicode' (I think LibreOffice calls UTF-16 'unicode'):
Host: <IP_ADDRESS>:8000
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Referer: http://<IP_ADDRESS>:8000/workshops/persons/bulkadd/
Cookie: …
Connection: keep-alive

For UTF-8:
Host: <IP_ADDRESS>:8000
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
DNT: 1
Referer: http://<IP_ADDRESS>:8000/workshops/persons/bulkadd/
Cookie: …
Connection: keep-alive

Hmm, I don't see Content-Type there at all.  Maybe we need to set
enctype 1 and/or accept-charset 2 for the form itself?  There's
also some discussion of encodings and forms here [3,4].  It looks like
the best approach is to set enctype to multipart/form-data.  We might
need to do other things too, but getting away from
application/x-www-form-urlencoded is a good first step.

It looks like the best approach is to set enctype to multipart/form-data. We might need to do other things too, but getting away from application/x-www-form-urlencoded is a good first step.

In our template (person_bulk_add_form.html) we have it already:
<form action="" method="post" enctype="multipart/form-data">

Do you have any other ideas? How does this form behave on your system?

On Wed, Feb 04, 2015 at 01:04:53PM -0800, Piotr Banaszkiewicz wrote:

I would expect the browser to set that as Content-Type when POSTing
the results, but that's not based on any research I've done.

Do you have any other ideas? How does this form behave on your system?

I've been staying away from the CVS-upload stuff ;).  I'll poke around
some tonight though.

I've been staying away from the CVS-upload stuff ;). I'll poke around some tonight though.

It's not a bug that we force people to upload UTF-8 encoded data. It's just a limitation :)

On Wed, Feb 04, 2015 at 01:36:36PM -0800, Piotr Banaszkiewicz wrote:

I've been staying away from the CVS-upload stuff ;). I'll poke
around some tonight though.

It's not a bug that we force people to upload UTF-8 encoded
data. It's just a limitation :)

It's a bug if they correctly declare the charset on their uploaded
file as something other than UTF-8 and we try to parse it as UTF-8
anyway.

It's a bug if they correctly declare the charset on their uploaded file as something other than UTF-8 and we try to parse it as UTF-8 anyway.

Then we can use request.encoding and fall back to UTF-8 if it's empty, can we?

On Wed, Feb 04, 2015 at 02:11:10PM -0800, Piotr Banaszkiewicz wrote:

It's a bug if they correctly declare the charset on their uploaded
file as something other than UTF-8 and we try to parse it as UTF-8
anyway.

Then we can use request.encoding and fall back to UTF-8 if it's
empty, can we?

We should be falling back to DEFAULT_CHARSET, as recommended by the
docs you linked.  And I'm still not clear if request.encoding is setup
by Django for us to read, or just something we set to tell Django how
to decode whatever it reads next.  A form POST could conceivably have
strings and files encoded in several different encodings, and I'm not
sure how Django tries to expose all of that information, or how the
browser is supposed to set it on POST.

Please go ahead and merge as soon as you're both comfortable with this - and thanks for digging into it.

Now the encoding is set to request.encoding and if it's empty the default is DEFAULT_CHARSET.

Is this good enough that we can merge, press on, and revisit later if
need be?

@gvwilson in my opinion yes, we can merge and move on.

OK - please push the button.

On Wed, Feb 04, 2015 at 01:17:28PM -0800, W. Trevor King wrote:

Wed, Feb 04, 2015 at 01:04:53PM -0800, Piotr Banaszkiewicz:

Do you have any other ideas? How does this form behave on your
system?

I've been staying away from the CVS-upload stuff ;).  I'll poke
around some tonight though.

It looks like I missed the merge window here, so I pushed the way I
think we should handle this in #177.


Upcoming major releases of Chocolatey products that may impact functionality on the integration

I'm the Technical Engineering Manager at Chocolatey Software, Inc. and I wanted to make sure you are aware that there will be a new major release of Chocolatey products soon. As it is a major release, we are making changes that may have an impact on the Chocolatey integration.
We have beta versions of Chocolatey CLI and Chocolatey GUI publicly available that you can test against.
The release notes for the various products are below (some may or may not be applicable to the module, but I wanted to list them all for completeness):

Chocolatey CLI
Chocolatey Licensed Extension
Chocolatey Agent
Chocolatey GUI
Chocolatey GUI Licensed Extension

We have no fixed date for release as yet, but it is coming soon.
Apologies for the non-standard issue. Please let me know if I can help in any way.

The Chocolatey products were released today. Please refer to the above links for the release notes. Here is some more information that may be helpful:

Blog Post.
Guide to upgrading.
Highlight of changes.

Please let me know if you need any more details.


How do you continue your epoch dataload when iteration %epoch_size==0?

In you code, I see that you do the running loop by the iterating of the variable "iteration" from "args.start_iter" to  "cfg['max_iter']".
but I see that the declaration of dataloader—— data_loader = data.DataLoader(dataset, args.batch_size,                num_workers=args.num_workers,   shuffle=True, collate_fn=detection_collate,     pin_memory=True).
there's nothing special of the dataset VOC0712's declaration. so how do you continue feeding new batches into the model when iteration % epoch_size==0??? it puzzled me few days. I cannot find where you handle the dataloading when itertation%epoch_size==0.

@onbigion13 have you understand this issue ?


Proposal: Help text for commands could link to documentation

Now with the hard limit on help text width, the documentation for options is much less descriptive, so it can be quite hard to tell what each option does.
For each command, we could link off the documentation for more information:
$ docker run --help
Usage: docker run [OPTIONS] IMAGE [COMMAND] [ARG...]

Run a command in a new container

  -a, --attach=[]            Attach to STDIN, STDOUT or STDERR
  --add-host=[]              Add a custom host-to-IP mapping (host:ip)
...
  -v, --volume=[]            Bind mount a volume
  --volumes-from=[]          Mount volumes from the specified container(s)
  -w, --workdir=             Working directory inside the container

For more information on this command and its options, see the docs:
https://docs.docker.com/reference/run/

The problem in this particular case (docker run) is that a lot of information is spread over the Command Line Reference (https://docs.docker.com/reference/commandline/cli/#run) and the Docker Run Reference (https://docs.docker.com/reference/run/); Perhaps each command should get its own page and the Command Line Reference only used as an index; this would make it easier to automatically generate the URL
I like the idea though; I think the domain-name should be dynamically inserted as well, so that a "Master" / "Development" build can point to http://master.dockerproject.com and an "Experimental" build to http://experimental.docker.com

@bfirsh It has been detected that this issue has not received any activity in over 1 year. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?
Thank you!

We do have separate pages for all subcommands, so programmatically generating a link would be possible now.
However, ideally, I'd like the help output to be useful

improving the overall output and description (https://github.com/docker/docker/issues/18797, https://github.com/docker/docker/issues/18385, https://github.com/docker/docker/issues/25615, https://github.com/docker/docker/issues/25615)
incorporating more information from the man pages in the help output

@bfirsh @dnephin wdyt should we close this issue in favor of the other issues linked?

#25615 is listed twice, did you mean to link a different issue?
I think it would be better to include the full help in the --help instead of link to it. That is what git does.

#25615 is listed twice, did you mean to link a different issue?

hm, possibly, or I just lost track, haha

I think it would be better to include the full help in the --help instead of link to it. That is what git does.

Alright, let's close this one


Use correct tooltip for deactivated bots

Currently, the deactivated indicator in the Organization settings > Bots panel has this tooltip:

Instead, it should say: "Bot is deactivated"
Please include screenshots of the correct tooltips from both this table and the Deactivated users table to demonstrate your changes.

@zulipbot claim


fixes that the migration is added even if it fails

fixes #20
Just removed the migration insert when it starts, and left only the insert when it completes

sorry for the horrible hostory. I dont know how to change it. Maybe just take the changes and dont do the pull request

Hey just a heads up AFAIK nobody is supporting this project anymore. You'll want to fork and publish your own package if you want changes beyond the last released version.


update packing receipt when create data with non exist product

Coverage increased (+0.03%) to 74.68% when pulling 9afe0d81a105f0c2d979ab0aa4a679efc289d4ba on leslieaula:dev into adaf11dda551faf471153dd276d68415fb8c2ba7 on danliris:dev.


scatter eos hook or proxy provider can not push action to nodeos

I am using eosjs2
const api = new Api({
        rpc,
        signatureProvider: scatter.eosHook(network),
        textDecoder: new TextDecoder(),
        textEncoder: new TextEncoder()
      });

and using api.transact to push an action to the nodeos, but nothing happend, no response, no error.
But If I use<EMAIL_ADDRESS>and as follows of eosjs document, action can push to the nodeos.
does scatter supoorted eosjs2?

Are you using the scatterjs-plugin-eosjs2 ?
Can you show me full code in a gist maybe?

Yes, I'm sure.
code is here:
const scatter = await getScatterEOS();
  if (scatter != null) {
    if (scatter.identity) {
      // Always use the accounts you got back from Scatter. Never hardcode them even
      // if you are prompting the user for their account name beforehand. They could
      // still give you a different account.
      const account = scatter
        .identity
        .accounts
        .find(x => x.blockchain === 'eos');

      // Get a proxy reference to eosjs which you can use to sign transactions with a
      // user's Scatter. eosjs2
      const network = {
        blockchain: 'eos',
        protocol: process.env.EOS.PROTOCOL,
        host: process.env.EOS.host,
        port: process.env.EOS.PORT,
        chainId: process.env.EOS.CHAINID
      };

       const api = new Api({
        rpc,
        signatureProvider: scatter.eosHook(network),
        textDecoder: new TextDecoder(),
        textEncoder: new TextEncoder()
      });
      const api = scatter.eos(network, Api, {rpc});

      try {
        const result = await api.transact({
          actions: [
            {
              account: 'xxxx',
              name: 'xxx',
              authorization: [
                {
                  actor: `${account.name}`,
                  permission: `${account.authority}`
                }
              ],
              data: {
                xxxxxx:xxxxx
              }
            }
          ]
        }, {
          blocksBehind: 3,
          expireSeconds: 10
        });
        console.dir(result);
        return result;
      } catch (e) {
        console.log('\nCaught exception: ' + e);
        if (e instanceof RpcError)
          console.log(JSON.stringify(e.json, null, 2));
        }
      }
  }

If I use hook provider。Console says eosHook is not a function.
If I use proxy provider. Console says TypeError: Cannot read property 'length' of undefined
but if I use eosjs
const defaultPrivateKey = 'dddddddd'; // privkey
const signatureProvider = new JsSignatureProvider([defaultPrivateKey]);
const rpc = new JsonRpc(process.env.EOS.JSONRPC, {fetch});
const api = new Api({rpc, signatureProvider, textDecoder: new TextDecoder(), textEncoder: new TextEncoder()});

everything is fine!
env
mac chrome.
scatter desktop and chrome has the same result.

Need more of this code as it's not showing imports for scatterjs, or what getScatterEOS() does.

getScatterEOS() follow the document:https://get-scatter.com/docs/examples-interaction-flow
I think you should must already know what getScatterEOS() does, no need to post more code of it.
And if I didn't imports scatterjs, does the code can go through to the ````const api = xxxxx```,  not a chance.
And I think hook provider show eosHook() not a function, I checked the code of packages/plugin-eosjs2, not a function named eosHook, maybe use hookProvider instead, params of it can fit the document. I will try tonight.

Using hookProvider will not work as they are renamed.
Please post the code inside the getScatterEOS() so I can see the full thing. I can't help with only pieces of the code.
Also please post an image of the error that you are getting with desktop open and the extension disabled ( extension does not support eosjs2 )

I have changed to the scatterjs-plugin-eosjs，and works fine. Great job, thank you


feat: Generate release redirects at build time with latest release from Github

I've noticed that you update manually links to the latest release with version.
This PR will use the latest release version directly from Github api.
One thing that I was not able to retrieve is the md5 checksum.
How do you calculate it, from what I know there is no way to retrieve it from API (but I may be wrong) ?

@jbleuzen you have conflicts because we released 2.6.1

Thank you @jbleuzen !


Some files starting with dot are not added in a new addon created with generator-volto

Describe the bug
Although the template has several files that start with a dot, such as .dockerignore, .editorconfig, etc., only .gitignore is added.
To Reproduce
Steps to reproduce the behavior:
npm install -g @plone/generator-volto
yo @plone/volto test-volto
cd test-volto
yo @plone/volto:addon myaddon

Expected behavior
All files that start with dot in the template must be in the generated addon
Software (please complete the following information):

OS: Ubuntu 22
Volto Version : 17.11.5

Additional context
It looks like .gitignore was added after @instification 's PR: https://github.com/plone/volto/pull/5258

Hi @wesleybl
The generator doesn't automatically include dotfiles when copying the template over.
The code that copies over the dotfiles is here:
https://github.com/plone/volto/blob/4a0580a518756f0cfcbb79fed7d175e84f12453f/packages/generator-volto/generators/addon/index.js#L207-L229
So only the .github/workflows .yarn/releases and .gitignore get copied over at the moment.
I'm afraid I don't know why it doesn't just copy the whole template including ignore files, I suspect it might not be possible to do it that way and all dotfiles will need to be manually added in index.js

@wesleybl yeah my change seems to have stopped the other dotfiles coming through.
I have made a fix in #5724 which should resolve the issue


[WIP] Increase CI/CD resources

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Documentation:

Does this PR introduce a user-facing change?:


Sveltekit: Can't do signups with email autoconfirm enabled

Bug report

[X] I confirm this is a bug with Supabase, not with my own application.
[X] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug
On my project, I have enabled the email provider with email verifications off.
Following the examples on the Sveltekit tutorial
// +page.svelte
<script>
	export let data;

	async function singup() {
		await data.supabase.auth.signUp({
			email: '...',
			password: '...'
		});
	}
</script>

I get the following error:
AuthApiError: PKCE flow is not supported on signups with autoconfirm enabled

It seems that the flowType is set to 'PKCE' instead of implicit. I cannot override this since the createSupabaseLoadClient() does not expose the auth configurations.
Expected behavior
PKCE flowType should not be the default.
Aditional context
Seems that the issue relies on this recent change: https://github.com/supabase/auth-helpers/pull/507/files#diff-6312d77cdcaf977045a7ed00ad8a5adb2503bca98d59ea42b331d083bd0b6cf3R93
The signup process works perfectly if I use my own supabaseClient from the @supabase/supabase-js
const supabase = createClient(PUBLIC_SUPABASE_URL, PUBLIC_SUPABASE_ANON_KEY, {
	auth: { flowType: 'implicit' }
});

await data.supabase.auth.signUp({
        email: '...',
        password: '...'
});

But since these clients have different configurations on how the sessions are stored, my users are not automatically logged in aftert singup, which is something i expect.
System information
"@supabase/auth-helpers-sveltekit": "^0.10.0",
"@supabase/supabase-js": "^2.22.0"

If you need implicit flow please use version 0.9.x and not 0.10.0. Going forward we are only supporting the pkce flow with the auth-helpers.

@silentworks It's not immediately clear how one should do e2e testing—eg using cypress—with PKCE forcing emails to be confirmed now as part of the flow. Am I missing something here?

The auth-helpers only supporting PKCE going forward seems to to mean that one has to actually disable autoconfirm.
I had it only enabled it for local development, which now seems to no longer be compatible with the auth-helpers.
To disable  autoconfirm locally set  enable_confirmations = true in the supabase config.toml.
For my local E2E tests I had to then "actually click the confirmation link":
cy.visit(`http://localhost:54324/monitor`) // the Inbucket URL you get via "supabase status"
cy.get('tbody > tr:first-child').click()
cy.get(".message-body a[href]").contains("Confirm your email address").click()


G8driver refreshtoken

G8driver refreshtoken
Description
Update g8 driver fixed some small issues when creating portforwards
And adds functionality to update the apitoken
Status

done, ready for review

Checklist (tick everything that applies)

[ ] Code linting (required, can be done after the PR checks)
[x] Tests

Merged, thanks.

This required a bit more work to fix the tests failing in trunk - 4004375ccb9d5e899e70b85b33bb7a018c312eee


‘LoomRunnableConfig’ object has no attribute ‘project_name’

Expected behavior
Extension should start (compile the project) without error
Actual behavior
The following message is output as a project problem: “There is a problem in your dbt project. Compilation failed: ‘LoomRunnableConfig’ object has no attribute ‘project_name’”
Steps To Reproduce
I am using project dependencies with dbt-loom.
Everything worked fine with dbt-power-user version 0.39.20, but broke with 0.40.0.(and 0.40.1).
The error occurs immediatly after starting VSCode and loading the extension.
Log output/Screenshots
No response
Operating System
Debian 11
dbt version
1.7.3
dbt Adapter
bigquery
dbt Power User version
0.40.1
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Pushed a fix in 0.40.2. @alangner Can you verify the fix?

Can confirm that it is fixed! 👍


[AutoComplete]: filter function passes the React element instead of dataSource

According with the doc for AutoComplete, filter signature:
key: dataSource element, or text property on that element if it's not a string.

If I have pass a React.node element into the dataSource, the filter funciton is called with that node, instead of the dataSource relative element

@LeoIannacone v0.x is in a low maintenance mode. We still accept PR fixes but the core team don't prioritize any work on the master branch.

Ok, thanks to let me know.


Feature request: Add global Desktop Site setting

Add global setting to enable Desktop Site automatically for all tabs.

Hello @jfitie , thanks for taking the time to submit this feature request. Sorry for the very late response, we are currently going through old feature requests.
After internal discussion with the team, we've agreed that there's no plan in the foreseeable future to support this request. Should this change in the future, we'll update this conversation appropriately.


Search: scale down document size, let the overall score do the ranking.

Based on top of #846.
Previously, when an expression e.g. haversine was present in a much longer text, the ranking gave it a lower score and the end result was further down, but it may have been only because of the more detailed example. With this tweak, we still prefer matches on shorter text, but the difference is more subtle.
Another effect: searching for AngularDart will not rank the angular package that behind, it will be likely on the first page.

@isoos – you'll have to rebase, it seems...

you'll have to rebase, it seems...

done.


Switch to Connect-MgGraph PowerShell for Automation (App-only)

Hi SharePoint-Team
I would like to switch from the "SharePoint Online Management Shell" to "Microsoft Graph PowerShell", because we can then automate this request, over an App Registration (Enterprise App) instead of a Service Account.
Please update the documentation how to request this for SharePoint!
Here my Idea:
Connect-MgGraph -Scopes "Sites.Read.All"
# Select-MgProfile -Name "beta"
$sitesGraph = Get-MgSite -Search * -Property * -All
$sitesGraph | Select -First 1 -ExpandProperty Drive
Get-MgSiteDrive -SiteId ($sitesGraph | Select -First 1).Id -Property Quota | Select -ExpandProperty Quota  # Empty
Get-MgSiteDrive -SiteId ($sitesGraph | Select -First 1).Id -Property Quota -ExpandProperty Quota | fl # Get-MgSiteDrive : Parsing OData Select and Expand failed: Property 'Quota' on type 'microsoft.graph.drive' is not

I was not able to convert this, got just 198 of over 3000 sites and didn't get the usage attribute out.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d657793d-ad57-3801-6586-9c36b949386f
Version Independent ID: ce570a07-c861-b43c-67c3-088780ee8fec
Content: Manage site storage limits - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/manage-site-collection-storage-limits.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


remote-touchpad: 1.2.0 -> 1.2.1

Description of changes

Things done

Built on platform(s)

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

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

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

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

[x] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg eval

@ofborg build remote-touchpad

Maybe you will wish to investigate why hash mismatch is happening (see output from ofborg) :eyes:


SQL DB Project - Open Existing project window 'select project file Location' textbox is disappearing

Azure Data Studio Version:
OS Version:

Open Existing project window 'select project file Location' textbox is disappearing when selecting git repository radio button and selecting Local radio button again.
Steps to Reproduce:

Install SQL DB Projects extension
Select DB Projects from the side bar.
Click on Open existing folder icon) on top and a open existing project window opens.
Select Git repository button and select back to Local, notice the "select project file Location" textbox is disappearing.

Repro Video:
https://user-images.githubusercontent.com/74571829/129240045-4378cd9f-85d6-4ba6-80e4-62bb648bf652.mp4

Does this issue occur when all extensions are disabled?: Yes/No

Note that the local clone path is having the same issue so likely the same fix will be needed there

Yep noticed that too. restating the same worry - I am still not sure if we are catching all of these instances affected by model view change

Closing since port is merged


[Feature Request] NTLM pass-through

Can you add reverse proxy config with Windows authentication that uses NTLM SSO.

Hello @geektalz!
I think this is a very unique use-case, you should add these rules to your generated config.


Road to 2.0

Our dependencies are getting creaky and some parts of this gem are long in the tooth so I wanted to go ahead and put together a list of what I think we need to do to transition to a solid 2.0

[ ] Remove support for ruby 1.8 / REE
[ ] Ensure support for ruby 2.2
[ ] Remove support for deprecated versions of methods
[ ] Unlock faraday version dependency (possible once we don't need to support 1.8)
[ ] Don't require multijson as a hard dependency, only use if present (otherwise use stdlib json)
[ ] Upgrade rspec stack to modern versions / conventions (expect, etc)

/cc @obfuscurity just wanted to give you a heads up on this

Yup, I'm getting the notifications anyways. :heart:

Resolved in #120.


rectangular_symmetric yields unexpected output

Expected behavior: (What you expect to happen)
sf.decompositions.rectangular_symmetric(np.identity(4)[::-1])
should give a decomposition with all internal and external phases equal to zero, i.e.

([[0, 1, 0.0, 0.0, 4],
  [2, 3, 0.0, 0.0, 4],
  [1, 2, 0.0, 0.0, 4],
  [0, 1, 0.0, 0.0, 4],
  [2, 3, 0.0, 0.0, 4],
  [1, 2, 0.0, 0.0, 4]],
 array([0, 0, 0, 0]),
 None)

Actual behavior: (What actually happens)
I get strange values, and negative phases.

([[0, 1, 0.0, 0.0, 4],
  [2, 3, 0.0, 0.0, 4],
  [1, 2, 0.0, -3.141592653589793, 4],
  [0, 1, 0.0, -4.71238898038469, 4],
  [2, 3, 0.0, 4.71238898038469, 4],
  [1, 2, 0.0, 4.71238898038469, 4]],
 array([1.8369702e-16+1.j, 3.0616170e-16+1.j, 6.1232340e-17+1.j,
        1.0000000e+00+0.j]),
 None)

The negative phases should be transformed into positive ones in the range [0, 2*pi), and the values should be all zeros.

Reproduces how often: (What percentage of the time does it reproduce?)
For any unitary above dimension 4 that I tried.

System information: (post the output of import stawberryfields as sf; sf.about())

Strawberry Fields: a Python library for continuous-variable quantum circuits.
Copyright 2018-2019 Xanadu Quantum Technologies Inc.

Python version:            3.6.8
Platform info:             Linux-4.15.0-55-generic-x86_64-with-debian-buster-sid
Installation path:         /home/leo/xanadu/code/strawberryfields/strawberryfields
Strawberry Fields version: 0.12.0-dev
Numpy version:             1.16.3
Scipy version:             1.2.1
The Walrus version:           0.7.0
Blackbird version:         0.2.1
TensorFlow version:        1.7.0

I suspect the numpy.fmod in the implementation should simply be replaced by the regular modulus operator, and relevant tests should be added.

We should also add a test for the case sf.decompositions.rectangular_symmetric(np.identity(4)[::-1])!

PR #196 makes all returned phases positive, but still results in nonzero (positive) external phase values for unitaries that can be obtained by composition of Mach-Zehner elements and final phase shifts with all phases equal to zero. For example (see below)for nine modes, this procedure gives the matrix np.identity(9)[::-1], but the decomposition yields different values. Nevertheless, the test in test_decompositions.pythat composes an original unitary with a recomposed decomposed version passes, meaning that both these decompositions are valid. Thus, the decomposition is not unique for certain settings, notably wheninternal_phase` is 0 or pi.
This can be understood when looking at one of the last MZI's in an interferometer that realizes a 'bar' or 'cross': its 'external' phase shift is directly imprinted onto one output mode, which goes straight through the Mach-Zehnder part without interfering with the other input mode, and eventually gets imprinted a final phase from the final phase shifter that is necessary to guarantee decomposability of arbitrary unitaries.
Conclusion: it is unclear to me which decomposition should be chosen out of the infinite possibilities in this case. But the current decomposition, as it is in strawberry fields, is not wrong.
import strawberryfields as sf

internal_phase = 0.0
external_phase = 0.0
n_max = 9

print('composition')
unitary = np.identity(n_max)
for col in range(n_max):
    start = col % 2 # even column numbers start from mode 0, odd ones from 1
    for m in range(start, n_max-1, 2):
        ti = (m, m+1, internal_phase, external_phase, n_max)
        print(ti)
        mzi = sf.decompositions.mach_zehnder(*ti)
        unitary = mzi @ unitary

print('composed unitary')
print(unitary)

print('decomposition')
tis, final_phase, _ = sf.decompositions.rectangular_symmetric(unitary)
print('Ti\'s')
for ti in tis:
    print(ti)
print('final_phases')
print(final_phase)

yiels
composition
(0, 1, 0.0, 0.0, 9)
(2, 3, 0.0, 0.0, 9)
(4, 5, 0.0, 0.0, 9)
(6, 7, 0.0, 0.0, 9)
(1, 2, 0.0, 0.0, 9)
(3, 4, 0.0, 0.0, 9)
(5, 6, 0.0, 0.0, 9)
(7, 8, 0.0, 0.0, 9)
(0, 1, 0.0, 0.0, 9)
(2, 3, 0.0, 0.0, 9)
(4, 5, 0.0, 0.0, 9)
(6, 7, 0.0, 0.0, 9)
(1, 2, 0.0, 0.0, 9)
(3, 4, 0.0, 0.0, 9)
(5, 6, 0.0, 0.0, 9)
(7, 8, 0.0, 0.0, 9)
(0, 1, 0.0, 0.0, 9)
(2, 3, 0.0, 0.0, 9)
(4, 5, 0.0, 0.0, 9)
(6, 7, 0.0, 0.0, 9)
(1, 2, 0.0, 0.0, 9)
(3, 4, 0.0, 0.0, 9)
(5, 6, 0.0, 0.0, 9)
(7, 8, 0.0, 0.0, 9)
(0, 1, 0.0, 0.0, 9)
(2, 3, 0.0, 0.0, 9)
(4, 5, 0.0, 0.0, 9)
(6, 7, 0.0, 0.0, 9)
(1, 2, 0.0, 0.0, 9)
(3, 4, 0.0, 0.0, 9)
(5, 6, 0.0, 0.0, 9)
(7, 8, 0.0, 0.0, 9)
(0, 1, 0.0, 0.0, 9)
(2, 3, 0.0, 0.0, 9)
(4, 5, 0.0, 0.0, 9)
(6, 7, 0.0, 0.0, 9)
composed unitary
[[0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 1.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 1.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 1.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 1.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 0.+0.j 1.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 0.+0.j 1.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 0.+0.j 1.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [0.+0.j 1.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j]
 [1.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j 0.+0.j]]
decomposition
Ti's
[0, 1, 0.0, 0.0, 9]
[2, 3, 0.0, 0.0, 9]
[1, 2, 0.0, 3.141592653589793, 9]
[0, 1, 0.0, 1.5707963267948966, 9]
[4, 5, 0.0, 0.0, 9]
[3, 4, 0.0, 3.141592653589793, 9]
[2, 3, 0.0, 3.141592653589793, 9]
[1, 2, 0.0, 3.141592653589793, 9]
[0, 1, 0.0, 1.5707963267948963, 9]
[6, 7, 0.0, 0.0, 9]
[5, 6, 0.0, 3.141592653589793, 9]
[4, 5, 0.0, 3.141592653589793, 9]
[3, 4, 0.0, 3.141592653589793, 9]
[2, 3, 0.0, 3.141592653589793, 9]
[1, 2, 0.0, 3.141592653589793, 9]
[0, 1, 0.0, 1.5707963267948966, 9]
[7, 8, 0.0, 1.5707963267948966, 9]
[6, 7, 0.0, 1.5707963267948966, 9]
[5, 6, 0.0, 1.5707963267948966, 9]
[4, 5, 0.0, 1.5707963267948972, 9]
[3, 4, 0.0, 1.5707963267948966, 9]
[2, 3, 0.0, 1.5707963267948966, 9]
[1, 2, 0.0, 1.5707963267948966, 9]
[0, 1, 0.0, 4.440892098500626e-16, 9]
[7, 8, 0.0, 4.71238898038469, 9]
[6, 7, 0.0, 4.71238898038469, 9]
[5, 6, 0.0, 4.71238898038469, 9]
[4, 5, 0.0, 4.71238898038469, 9]
[3, 4, 0.0, 4.71238898038469, 9]
[2, 3, 0.0, 4.71238898038469, 9]
[7, 8, 0.0, 4.71238898038469, 9]
[6, 7, 0.0, 4.71238898038469, 9]
[5, 6, 0.0, 4.71238898038469, 9]
[4, 5, 0.0, 4.71238898038469, 9]
[7, 8, 0.0, 4.71238898038469, 9]
[6, 7, 0.0, 4.71238898038469, 9]
final_phases
[ 1.0000000e+00-2.44929360e-16j  1.0000000e+00-4.44089210e-16j
 -6.2778623e-16-1.00000000e+00j -1.8369702e-16-1.00000000e+00j
 -1.0000000e+00+3.67394040e-16j -1.0000000e+00+1.22464680e-16j
  3.0616170e-16+1.00000000e+00j  6.1232340e-17+1.00000000e+00j
  1.0000000e+00+2.39393768e-16j]

@lneuhaus, what's the status of this issue?

I will close this, because the current functionality in SF is not wrong, it just picks one out of many possible decompositions. A similar issue was fixed in #311.


Add projects

https://adityahirapara.github.io/wdlsvnit.github.io/projects

@ajayns @AdityaHirapara Are we good to merge this?

Yes!


apt-get install opencoarrays :)

Hello,
First of all thank you for all the good work ! :+1:
Maybe you could consider providing some apt package ? That would be much welcome for instance for rapid testing (i.e. without the lengthy compilation time associated with ./install).

  We would love to support package management by any and every means.  As you probably know, we currently support installation via package management with macports on OS X and via aur on the Arch Linux distribution. (@afanfa, please update the macports Portfile when you have a chance.)  @zbeekman is also working on supporting installation via homebrew on OS X and considering support for linuxbrew thereafter.  Regarding apt, I think there might be an issue with our dependencies, which keep us at the bleeding-edge of compiler releases.  Does apt currently install gfortran 5.3?  That's our current minimum version requirement and we're likely to move to gfortran 5.4 when it releases. We also require a fairly recent version of CMake (3.0), but I assume apt installs something sufficiently recent in that regard.
We are mostly volunteer effort.   If you have any expertise relevant to generating the apt package and getting it accepted or if you would like to gain such expertise, contributions of coding time are welcome. :)

In Ubuntu 15.10 (the latest version),
apt-get install gfortran installs version 5.2
apt-get install cmake installs version 3.2.2.
In Ubuntu 14.04 (the latest Long Term Support (LTS) version):
gfortran 4.8 and cmake 2.8
For future reference, the command to get this information in Ubuntu is
apt-cache policy cmake
I understand these versions do not satisfy your constraints :( but yet and even if I'm not an expert I'd be glad to help.

Would you be interested in using OpenCoarrays with earlier versions of gfortran with an understanding that there could be associated bugs?  I'm pretty sure the building directly with the CMake scripts will work with any gfortran 5.x version and will even work in a very limited sense with gfortran 4.9. I haven't tried with gfortran 4.8 so I can't comment.
If you decide to work on the apt package for us, I'd be glad to provide any advice you need for building OpenCoarrays with these older versions of gfortran.  I'd recommend starting with gfortran 5.2.  The CMake build instructions are here.  As a last resort, there is a static Makefile, which should work, but CMake is preferred.
As far as bugs associated with earlier features, the biggest one that comes to mind is that gfortran must compile CAF source with no optimizations when using gfortran versions < 5.4 (which is the current development version on the gcc 5 branch) as mentioned here.  Also, I believe that support for Fortran 2015 EVENT_TYPE (which can be very helpful with writing scalable algorithms) requires gfortran 5.4.

Just to elaborate a bit more: Once OpenCoarrays is part of Homebrew, then you will be able to install it through Linuxbrew as well. The nice thing about Linuxbrew is that it lives in user land, so that you can install software on any linux distro, without root privileges. You can create binary distributions for Linuxbrew and Homebrew, and so long as the installation directory is standard for Homebrew, brew install opencoarrays should download and install a binary if it can. Similarly, linuxbrew will have the same functionality eventually, but for now, there is a limited subset of packages with binary "bottles". We may also provide links to bottles for binary installations, eventually, for both Linux and OS X.
Another idea that Damian and I should discuss is whether or not we may be able to provide Linux and/or OS X binary distributions ourselves.
If you know anything about creating linux packages, then we would welcome your help. However, I am weary of officially supported any linux package manager (other than Linuxbrew) because there are so many of them. I think that any support (there is some user contributed support for an Archlinux package, which might be out of date) for distro package managers will be 100% user contributed/supported unless we find compelling evidence to change this policy. Damian and/or Alessandro may have different opinions, I don't think we've discussed this at length, so consider these "policies" my suggested policies.

I understand these version constraints better, thanks. I also prefere cmake a lot.
I will have a look at this and come back to you.
What about the suboptimal but rapid solution of preparing binaries ?
Does it make sense ?

I did not see your comment before posting mine, sorry we overlapped. I don't know much about Homebrew since I don't know Apple's world. I had never heard about Linuxbrew. I'll have a look at all of this and come back to you.

Regarding Linuxbrew, it is derived from homebrew, and seems to be somewhat experimental but rapidly stabilizing. It patches Homebrew "formulas" to be able to build on linux. It is starting to provide binary "bottles" for some formulae just like Homebrew.
The tricky thing with preparing binaries is that there is a combinatorial explosion of potential binaries that are needed: OpenCoarrays is directly integrated with GCC. As such, it must be compiled with the compiler that it will be wrapping/integrating with (as far as I know) AND it uses MPI as the backend for communications. So the tricky thing is how does one prepare binaries for this? Will a binary build with GCC 5.3 and MPICH x.y work on a system that has MPICH x.z and GCC 5.2? What if they are installed in different locations than the machine OpenCoarrays was build with? Right now I don't definitively know whether it will be possible to relocate opencoarrays binaries, and whether issues will arise if different MPI  and GCC implementations are linked against. The last bit of trouble is the CAF wrapper scripts need to be adjusted after installation to point to the correct MPI and GCC...

@maxlevesque, please let us know if you're planning to work on the apt-get install and would like any advice from us.  If not, we'll close this issue.
We still plan to provide a homebrew formula, which will get pulled into linuxbrew.  Also, we continue to make improvements with our installer and you can now force the use of GCC versions lower than the current default 6.1.0 version using syntax such as the following:
./install.sh --with-fortran /opt/local/bin/gfortran --with-c /opt/local/bin/gcc --with-cxx /opt/local/bin/g++
or equivalently
./install.sh -f /opt/local/bin/gfortran -c /opt/local/bin/gcc -C /opt/local/bin/g++
Also, the bug that required disabling optimization (with -O0) when compiling OpenCoarrays has been fixed in the latest releases of OpenCoarrays (1.6.0) and gfortran (6.1.0).  The fix will also appear in gfortran 5.4.0 when it releases. Now the build uses the CMake default optimization of -O3.

Yes I am planning to do this. You can assign me. Nevertheless, it is on my todo list for the end of june since I have other projects to finish within the academic year. Is this delay acceptable to you? If no, please close the issue.

@maxlevesque, that timeline is great for us.  I just sent you an invitation to become a collaborator on this repository with read privileges.  That should enable me to assign this issue to you after you accept the invitation.  Thanks for your interest and willingness to contribute.

opencoarrays is now in Debian (as of yesterday!)
I'm the Debian Maintainer and have added it. Works for me (tm) with gfortran 6.1 and OpenMPI 1.10.3.
Presumably it will flow into Ubuntu in the following days.
(I didn't see this issue in the tracker until now, so sorry for arriving late to the party)

hi @amckinstry thanks. So, is there anything I still can do ?

@amckinstry Awesome!
Questions:

Is there a way to track user downloads/installs?
Would it be possible to specify MPICH as the default rather than OpenMPI? It should work fine with OpenMPI, however, on most machines some of the tests run by ctest are oversubscribed, and OpenMPI can encounter an error in these cases.

(1). Debian has a "popularity contest' (popcon) feature, that tracks downloads from users who opt into it.
Its pretty low at the moment, unsurprisingly:
https://qa.debian.org/popcon.php?package=open-coarrays
(2) Yes. I've built it against the default arch (openmpi) only; the question was where to put the library. As /usr/lib/libcaf_mpi.a it gets found trivially and is straight-forward; (next thing to do is add it as a recommends: for gfortran compilers, so its present by default for Fortran users).
If I build both openmpi and mpich, a choice has to be made: (a) place in a 'private' directory like /usr/lib/mpich/libcaf_mpi so that users have to use -L/usr/lib/mpich -lcaf_mpi to link, or (ditto for openmpi) or  (b) change the name to caf_mpi_mpich? or (c) two conflicting packages, both installing as /usr/lib/libcaf_mpi.a (least favoured option).
The build and test logs, BTW, are at : https://buildd.debian.org/status/package.php?p=open-coarrays&suite=unstable

(1). Debian has a "popularity contest' (popcon) feature, that tracks downloads from users who opt into it.
Its pretty low at the moment, unsurprisingly:
https://qa.debian.org/popcon.php?package=open-coarrays

Thanks for the info

(2) Yes. I've built it against the default arch (openmpi) only; the question was where to put the library. As /usr/lib/libcaf_mpi.a it gets found trivially and is straight-forward; (next thing to do is add it as a recommends: for gfortran compilers, so its present by default for Fortran users).
If I build both openmpi and mpich, a choice has to be made: (a) place in a 'private' directory like /usr/lib/mpich/libcaf_mpi so that users have to use -L/usr/lib/mpich -lcaf_mpi to link, or (ditto for openmpi) or (b) change the name to caf_mpi_mpich? or (c) two conflicting packages, both installing as /usr/lib/libcaf_mpi.a (least favoured option).

Ah, OK, if OpenMPI is the default on Debian, I think it should be fine. Let's just stick with OpenMPI for now...
I noticed that none of the tests were run during the build process; for the time being, if you do run tests, some of them may fail with OpenMPI, but I have added logic to the build script to detect OpenMPI and prevent the tests from oversubscribing... This should make it into a future release in the next week or so.

The build and test logs, BTW, are at : https://buildd.debian.org/status/package.php?p=open-coarrays&suite=unstable

Very cool.  I checked out the logs, and things look like they are working as expected...

@maxlevesque I'm not sure; test it out for a start! If you're a Debian or Ubuntu developer, it would be good to have a co-maintainer.

Should I close this issue? Will Ubuntu pick this up from upstream? If so will it be in the default PPA or somewhere like ubuntu-toolchain-r/test?

@zbeekman Yes.  Its now in the default Ubuntu upstream.  (Universe, I think). I think the issue can be closed.

🎉 🙇

Hello @amckinstry (and also @maxlevesque)
OpenCoarrays 1.6.2 has been released. There were issues that caused some of the tests to fail with OpenMPI but I believe these are now fixed in the latest release. Could you please update the  ubuntu package definition to use the latest 1.6.2?
Many thanks.

Done.
Regards
Alastair
On 25/07/2016 20:26, Izaak Beekman wrote:

Hello @amckinstry https://github.com/amckinstry (and also
@maxlevesque https://github.com/maxlevesque)
OpenCoarrays 1.6.2 has been released. There were issues that caused
some of the tests to fail with OpenMPI but I believe these are now
fixed in the latest release. Could you please update the ubuntu
package definition to use the latest 1.6.2?
Many thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sourceryinstitute/opencoarrays/issues/165#issuecomment-235057702,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA32rgmL7Dcb9pBIkZRQwu_Q2y-UefKdks5qZQ3lgaJpZM4IFWYr.

--
Alastair McKinstry<EMAIL_ADDRESS><EMAIL_ADDRESS>https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.


⚠ ClamAV has degraded performance

In 0d52de5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 426 ms

Resolved: ClamAV performance has improved in b02d082.


OpenSSL 3.0 and OpenSSL 1.x coexistence compatility

Hello,
We have recently consumed OpenSSL 3.0.1 in our product. However, we have few Open Source modules that are still compiled with OpenSSL 1.1.x and we can't upgrade them to use OpenSSL 3.0.x for various reasons. By including both versions of OpenSSL (.dll, .so) in the installation, the product and modules worked fine in our sanity test. However, we wanted to understand what kind of issues we may encounter if we proceed further with this approach. Our product runs on Windows, Linux and MacOS. Any suggestions and/or insights are highly appreciated.

Unless these independent modules try to share the internal data of the OpenSSL library across the different versions, this should be fine.
An example of broken scenario is to try to pass a pointer to an X509* certificate object or EVP_PKEY* object across the versions.
However the scenario where you link in an application two independent libraries that use different versions of OpenSSL to do unrelated things should work fine.


install with ROS2 galactic& gazebo garden

Hi,
I'm trying to install the vrx with ROS2 galactic and got an error while colcon build (working on PC without docker).
My steps are as follow:
mkdir -p ~/vrx_ws/src
cd ~/vrx_ws/src
git clone https://github.com/osrf/vrx.git -b gazebosim
cd ~/vrx_ws/src
git clone https://github.com/gazebosim/ros_gz.git -b galactic
cd ~/vrx_ws
GZ_VERSION=garden colcon build --merge-install

The output:
Starting >>> ros_ign_interfaces
Starting >>> ros_ign_gazebo
Starting >>> vrx_gazebo
Starting >>> vrx_ros
Finished <<< vrx_gazebo [1.13s]
Starting >>> wamv_description
--- stderr: vrx_ros
CMake Error at CMakeLists.txt:12 (find_package):
  By not providing "Findros_gz_interfaces.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "ros_gz_interfaces", but CMake did not find one.

  Could not find a package configuration file provided by "ros_gz_interfaces"
  with any of the following names:

    ros_gz_interfacesConfig.cmake
    ros_gz_interfaces-config.cmake

  Add the installation prefix of "ros_gz_interfaces" to CMAKE_PREFIX_PATH or
  set "ros_gz_interfaces_DIR" to a directory containing one of the above
  files.  If "ros_gz_interfaces" provides a separate development package or
  SDK, be sure it has been installed.

---
Failed   <<< vrx_ros [1.47s, exited with code 1]
Aborted  <<< wamv_description [0.55s]
Aborted  <<< ros_ign_interfaces [1.75s]
Aborted  <<< ros_ign_gazebo [2.53s]

Summary: 1 package finished [2.76s]
  1 package failed: vrx_ros
  3 packages aborted: ros_ign_gazebo ros_ign_interfaces wamv_description
  2 packages had stderr output: ros_ign_gazebo vrx_ros
  6 packages not processed

Is there a wiki for this kind of installation?
Thank you,
Ehud

hi Ehud,
You need to combine Gazebo Garden with ROS 2 Humble. We're not supporting Galactic at this point.


send uploader up to parent compnent so the parent has access to it

regarding this conversation: https://github.com/AltSchool/ember-plupload/pull/1

I'll probably pull this in, then handle iOS natively in the addon, where you won't have to care that you're running this addon on a iOS device.

sounds good.

In 1.13.7. Note that this will probably be removed in 2.0 and you won't have to do anything special. (The plupload object will be swapped out with <input capture="camera"/>.)


Form Error Message

Issue: https://github.com/bloom-housing/bloom/issues/3241

OK, this feels pretty solid now I think. @ludtkemorgan @emilyjablonski I was wondering how we want to handle per-component token naming. In the past I had sometimes done a more simple naming scheme without spelling out the whole component name, but maybe we should make it more clear? (So for example this time I specified something like --form-error-message-font-size.) Jessie at one time had suggested all our tokens start with a --bloom prefix, but I'm not sure if we need that per-component.

OK, this feels pretty solid now I think. @ludtkemorgan @emilyjablonski I was wondering how we want to handle per-component token naming. In the past I had sometimes done a more simple naming scheme without spelling out the whole component name, but maybe we should make it more clear? (So for example this time I specified something like --form-error-message-font-size.) Jessie at one time had suggested all our tokens start with a --bloom prefix, but I'm not sure if we need that per-component.

@jaredcwhite I don't have a strong opinion. It would be nice if it's not too long of a name but also we want it to be clear what it does just from its name. The bloom prefix could help make it certain that there aren't duplicates tokens between bloom and other things (I'm more thinking of future cases by consumers of ui-seeds), but I don't really think that chance is likely.


Build failed when using APP_TYPE = tflm_yolo8_od

I am trying to build the firmware using the tflm_yolo8_od app type. The build fails with this error:

/trustzone/tz_cfg/trustzone_cfg.h:16:10: fatal error: CM55M_TrustZone_FW_mem.h: No such file or directory
16 | #include "CM55M_TrustZone_FW_mem.h"

The build succeeds with APP_TYPE = allon_sensor_tflm. What is different between the two app types?

Hi @JakeSays
The APP_TYPE="tflm_yolo8_od" is a typo. It should be "tflm_yolov8_od". Please try again. Thanks.

@stevehuang82 ah that fixed it:) Thanks!


During lag, new chunks appear before everything's loaded (camera)

Line 37 in tilechunk during lag, camera becomes undefined.

To recreate, join & leave the game very quickly during lag.


Sdk extra guard

Closes #1156
Changes

code to check git info

How I tested this

tests

Notes
Checklist

[ ] PR has an informative and human-readable title (this will be pulled into the release notes)
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future TODOs are captured in comments
[ ] Project documentation has been updated if adding/changing functionality.

pip install sf-hamilton-sdk==0.7.3rc0


Include deploy syscalls in gas calculation

We should be including the resources consumed in constructor + syscalls cost when deploy is used (both the native one and the cheatcode variant)

I believe it already works this way, a call to constructor is just a call, so it is included

It should be, but i still would like to put this forward, verify and perhaps add some tests for that

Tests are being added in the https://github.com/foundry-rs/starknet-foundry/pull/1195


Grammar installation instructions for Windows

treesit-auto implicitly assumes the presence of a C compiler and linker on exec-path by relying on treesit-install-language-grammar for installing missing grammars. On linux this is a reasonable assumption, but it is rarely true on Windows. The grammar installation section of the README should either recommend either installing compiler tool-chain onto exec-path or directly downloading and manually installing the grammar. I'm not sure which is more preferable.

Hi @non-Jedi !
Since I do not have a Windows machine to test, I cannot help here unfortunately :(

@non-Jedi Thank you for the clear instructions: I just tested and they work.


Stopping video container when service startup timed out (fixes #504)

Codecov Report

Merging #514 into master will decrease coverage by 0.11%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #514      +/-   ##
==========================================
- Coverage   77.16%   77.04%   -0.12%
==========================================
  Files          11       11
  Lines        1292     1294       +2
==========================================
  Hits          997      997
- Misses        233      235       +2
  Partials       62       62

Flag
Coverage Δ

#unittests
77.04% <0%> (-0.12%)
:arrow_down:

Impacted Files
Coverage Δ

service/docker.go
80.83% <0%> (-0.57%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 70c7afa...00428fe. Read the comment docs.


Research Swaplace blockchain queries

Optimization Required: Reducing Excessive Blockchain Queries in dApp
Description:
Our decentralized application (dApp) is currently making an unusually high number of queries to the blockchain, with approximately 300 queries being sent from a single page. This level of querying is highly inefficient, potentially leading to increased costs, slower performance, and a suboptimal user experience. The objective of this issue is to identify the major sources of these excessive queries, discuss potential optimization strategies, and implement solutions to significantly reduce the number of unnecessary blockchain queries.
Possible Problems:

Redundant Queries: The same information is being requested multiple times due to inefficient state management or lack of caching mechanisms.

High-Frequency Polling: The dApp might be polling the blockchain at intervals that are too short, leading to unnecessary queries.

Unoptimized Smart Contract Interactions: Certain interactions with smart contracts may be inefficient, requesting more information than necessary or making separate calls when batch requests could be utilized.

Lack of Pagination/Lazy Loading: Large datasets are being loaded in their entirety instead of being paginated or lazily loaded as needed.

Inadequate Query Aggregation: Opportunities to aggregate queries into a single call are being missed, resulting in higher than necessary query numbers.

Definition of Done
To consider this task completed, we must achieve the following objectives:

Identify High-Query Pages: Determine which pages within the dApp are generating the most blockchain queries.

Root Cause Analysis: Understand why these pages are making excessive queries by identifying inefficiencies or design flaws.

Strategize Optimizations: Propose targeted strategies for each identified high-query page to reduce the number of blockchain queries, ensuring these strategies are practical and applicable.

Achieving these milestones will signify the successful reduction of excessive blockchain queries, enhancing our dApp's efficiency and user experience.

Optimized Results Summary
Key Strategies for Reducing Alchemy Query Volume
Implement User Context Management

Objective: Streamline user information retrieval by establishing a user-specific context. This approach aims to eliminate redundant queries for user data across different sections of the application.
Benefit: Reduces the need for repeated calls to fetch user information, thereby decreasing the total number of queries.

Integrate Direct User Information Storage in UI

Objective: Enhance the user interface to directly incorporate user-related data, such as addresses. This method seeks to avoid unnecessary queries by storing and reusing user data within the UI.
Benefit: Minimizes repetitive requests for user addresses and related information, cutting down on query volume.

Utilize Batch Requests for Token Interactions

Objective: Consolidate multiple token-related queries into single batch requests. This strategy is designed to reduce the overhead associated with individual requests for token data.
Benefit: Significantly decreases the number of queries sent by grouping several requests into one, improving efficiency and performance.

Optimize Ponder for Direct Data Retrieval

Objective: Modify the Ponder mechanism to fetch precisely the required information in a more direct manner. This aims to streamline data retrieval processes by eliminating unnecessary data queries.
Benefit: Enhances data fetching efficiency by directly accessing the needed information, thereby reducing the total query count.

Conclusion
By focusing on these targeted optimization strategies, we can significantly reduce the number of excessive blockchain queries. This will not only improve our decentralized application's performance but also enhance the overall user experience by making the application more efficient and cost-effective.

@0xneves Let me know if any more information would be useful here


froze webpack cli version

Reverted webpack cli version to a functioning version.

This fixes the issues with npm and #11


feat: ✨ footer template

Checklist (for the issue creator)

[x] I have looked at the documentation site and was not able to find the component.
[x] I have looked into the Figma boards and was not able to find the component.
[ ] I would be willing to provide a PR for this component.

Story
As an application or website developer, I want to add a footer that includes all the required legal information. Since every website and application is legally required to include this, the footer should look the same (or similar) on all SICK websites. Otherwise, everyone will make their own footer that behaves and looks differently.
Example footers:

https://www.sick.com/de/en/
https://id.sick.com
https://cloud.sick.com/

What the components needs to do:

Be displayed at the bottom of the page
Include links to:

Imprint
Terms and conditions
Terms of Use
Privacy Policy

Include a copyright notice
Provide translations for our 18 or so supported languages (or be translatable)
Reactive layout that adapts to different resolutions (e.g. sick.com changes the position of the copyright notice depending on the size of the viewport)

Alternative design: Provide a way to add links to the footer from the application level. Then, synergy does not need to provide the translations.
Application context: Every website or application that is customer facing needs this at the bottom of the page for legal reasons.
Acceptance criteria

[ ] All DoD items successfully completed
[ ] A footer template is included into the synergy library (AppShell)
[ ] Add to FW demos
[ ] Dog footing of link styling
[ ] Optionally add footer style into styles-package (background color, paddings,...)
[ ] add responsiveness

We can provide the translations for the footer link texts (SICK ID team) if that is necessary. Depending on whether you want to include them in synergy.

Hi Fabian,
thanks for you input.
We already discussed the footer topic in the team and decided to go for a template approach instead of having a component. Templates are more flexible and provide a copy & paste approach which can be adapted better to application needs.
Regarding translation: we decided against translating text inside synergy. Otherwise we have to provide translations for each language and we cannot know which languages are necessary for an application. Also translations may come from other sources (like the CMS on the website).
Nevertheless your Input is valuable and we certainly take your requirements into account.

blocked by #405 and design

Design done, see Figma Branch: https://www.figma.com/design/bZFqk9urD3NlghGUKrkKCR/branch/WV4ZTdX9FpEpdfvzhhpV2B/Synergy-Digital-Design-System?m=auto


tolerate empty imagestream annotations field for slave lookup

fixes https://github.com/openshift/jenkins/issues/220

@mfojtik you did the original I think and probably know templates better than me, ptal.

LGTM (I thought annotations are defaulted...)

@mfojtik i'm at least find the that the repository check annotation immediately gets added to any imagestream i create, so it's pretty hard to hit this, but the user who hit this was on 3.3, perhaps behavior was different then.  I was able to recreate it by deleting the annotation block from the IS and then quickly running the template, so it's definitely not defaulted.


chore: use esno to replace ts-node

Continues #8152 (previously reverted by #8161)

@antfu the prev issue should be fixed after https://github.com/vitejs/vite/pull/8152#issuecomment-1126238944, no?


Fixed getRawTemperature and getRawHumidity

The internal variables that the raw values are read from were swapped.

Thanks for catching this bug
I will investigate it later today.

Looks like I was somewhere completely else with my mind.

Happens to the best of us 😉
Nice to see you are this fast to react to pull requests 👍
Have a nice sunday :)

Nice to see you are this fast to react to pull requests 👍

If they are this obvious one has no choice 😁

@theandy94
Triggered by your PR a new 0.2.0 release is prepared. See the develop branch

adds get / set resolution - based upon SHT20 datasheet.
check batteryOK  (checks VDD)
some updates in readme.md.

If you have time to test with real hardware, would be appreciated. (especially resolution)
I have no hardware available at the moment, and still need to write an example sketch.

The only hardware I've got is a HTU21D connected to an ESP32 devboard using its 3.3v to supply the sensor.
I've downloaded the current dev branch with 0.2.0 and ran the SHT2x_resolution.ino sketch.
Upon starting I get:
STAT: 0
BATT: OK
I can confirm, that the temperature and humidity readings are the same for each resolution setting +-noise.
Always glad to help :)

Thanks for testing, I will dive into the datasheets tomorrow to check for diffs. The EIDA is less important than the setresolution.
To be continued

updated the develop with crc8 test in the read()
it will set the error flag, but will not fail on invalid crc.
(don't know if it adds value as the error rate seems to be pretty low)

Output from SHT2x_resolution.ino from latest develop:
SHT2x_LIB_VERSION:      0.2.0
STAT:   0
BATT:   OK
RES:    0
        102448  23.9    58.2
RES:    1
        101452  23.8    58.2
RES:    2
        101452  23.8    58.3
RES:    3
        101452  23.8    58.1
RES:    0
        101452  23.8    58.0
RES:    1
        101452  23.8    58.0
RES:    2
        101452  23.8    58.1
RES:    3
        101452  23.8    58.1
RES:    0
        101452  23.8    58.2
RES:    1
        101452  23.8    58.1
RES:    2
        101452  23.8    58.1
RES:    3
        101452  23.8    58.1
RES:    0
        101452  23.8    58.1
RES:    1
        101452  23.8    58.1
RES:    2
        101452  23.8    58.1
RES:    3
        101452  23.8    58.1

Thanks, i notice the timing is still hard-coded.
Will look into that tomorrow.
Without shorter delays there is no reason to set a lower resolution.
Tbc

Just pushed a change with adjusted timing for the different resolutions. (based upon table 7 SHT21)
also changed the decimals to 3 in the test sketch to see the difference in resolution.
Please rerun the test sketch.
If it is OK, I am going to merge it into master and release version 0.2.0

Output from latest develop:
SHT2x_LIB_VERSION:      0.2.0
STAT:   0
BATT:   OK
RES:    0       116452  24.300  60.727
RES:    1       1113875 24.300  60.727
RES:    2       1084875 24.279  60.727
RES:    3       1102875 24.279  60.727
RES:    0       116452  24.268  61.291
RES:    1       1113874 24.268  61.291
RES:    2       1084875 24.268  61.291
RES:    3       1102875 24.268  61.291
RES:    0       116452  24.290  60.795
RES:    1       1113874 24.290  60.795
RES:    2       1084875 24.290  60.795
RES:    3       1102875 24.290  60.795
RES:    0       116452  24.279  60.689
RES:    1       1113874 24.279  60.689
RES:    2       1084875 24.268  60.689
RES:    3       1102875 24.268  60.689
RES:    0       116452  24.290  60.620
RES:    1       1113874 24.290  60.620
RES:    2       1084875 24.279  60.620
RES:    3       1102875 24.279  60.620
RES:    0       116452  24.279  60.559
RES:    1       1113874 24.279  60.559
RES:    2       1084875 24.279  60.559
RES:    3       1102875 24.279  60.559

Thanks for testing,
Good tip to improve comments here.
Still the time used by the various resolutions make no sense except for zero.
Tbc

The expected times versus the measured times

RES
HUM
TEMP
TOTAL
REAL

0
29
85
114
116

1
4
22
26
1113

2
9
43
52
1084

3
15
11
26
1102

So only the resolution == 0 meets the expectation.
I do not see a pattern in the deviations and
Which processor do you use?

What I do notice is that the sensor gives 4x the same temperature in a row.
And humidity values seem to repeat too.
That could indicate that time between measurements is too short.
I am going to rewrite the example.
Please be so kind to run another test. (give me 10 minutes to patch the test).

I've used an ESP32 which is known to not be very precise with its delays...
I now used an Arduino Nano with the latest develop version.
Output is the following:
SHT2x_LIB_VERSION:      0.2.0
STAT:   0
BATT:   OK
RES:    0       115368  23.946  59.887
RES:    0       115376  23.882  60.017
RES:    0       115364  23.871  60.193
RES:    0       115368  23.871  60.139
RES:    0       115364  23.861  60.101
RES:    1       112292  23.861  60.101
RES:    1       113008  23.861  60.101
RES:    1       113016  23.861  60.101
RES:    1       113012  23.861  60.101
RES:    1       113000  23.861  60.101
RES:    2       83300   23.839  60.101
RES:    2       84396   23.839  60.101
RES:    2       83360   23.828  60.101
RES:    2       83364   23.828  60.101
RES:    2       84388   23.818  60.101
RES:    3       101796  23.818  60.101
RES:    3       100716  23.818  60.101
RES:    3       101752  23.818  60.101
RES:    3       101748  23.818  60.101
RES:    3       101736  23.818  60.101

done...

Looks better than last test but still most are longer than expected.
Either the datasheet is incorrect or ?
I will make a remark in the readme and start merging process later today. Enough time spent on it for now.
Thanks

Always glad to help.

Note: that the timing in the last test is very similar per resolution MINUS 1 second ...
(Will dive into it later again as said before, but I want to keep this observation)


Where do you apply DenseCRF to the score map?

Hello， thank you for sharing your nice project.
In sec3.4， you write about how to get the instance masks， but I do not know where you apply the DenseCRF...
For example,
we first generate the score map for the detected box using the trained segmentation branch.
Then, the predicted score map of the box is pasted to a map Sˆ of the same size as the input image according to the box’s location.

is corresponding to the first score map and paste pate
And，values predicted by the model are returned in this part
All the above codes are run in this inference part.
Finally， the encoded masks are outputed in the encode part.
However， I do not know the DenseCRF part...
For setting up DenseCRF, we employ the map Sˆ as the unary term and use the color and pixel location differences with the bilateral kernel to construct the pairwise term.
After optimization using mean field approximation, DenseCRF produces the final instance mask

Please teach us， thank you.

Hi UdonDa,
Thanks for asking.
But for now, the post-processing (DenseCRF) part has not been included in the repository.
The DenseCRF code is based on Matlab and was developed by another author.
Unfortunately, I currently have no access to his server.
I will upload them next week (after I return from the NeurIPS conference).
Cheng-Chun

Thanks for replying.
You implement the CRF part by MATLAB, ok.
I think that It's easier to implement CRF by pydencecrf.
After you upload the part, I will try!
Please do your best NeurlPS.
Thanks.

Hi UdonDa,
Actually, the run_test function will evaluate the performance of the trained model "without" post-processing (DenseCRF).
If you have implemented the post-processing part in python.
You can let me know by opening an issue or commits.
Thanks!
Cheng-Chun

Hi @UdonDa , what is your mask AP on VOC 2012 validation set.
We strictly follow the author's settings, however, we cannot reproduce the results.
Box AP:
AP25: 0.81
AP50: 74.4
AP70: 0.54
AP75: 0.46

Mask AP: (wo/ CRF)
AP25: 0.74
AP50: 0.44
AP70: 0.16
AP75: 0.11

Could you please share your Mask AP result? We have at least 9 points gap compared to the author's reported results.


Overlapping stats request when switch reconnects

Hi,
When a switch disconnects in the middle of a FlowStats request, we will see Overalapping stats request messages being logged for a few cycles before it discards the old request and send a new one.
This can lead to a delayed Flow Consistency routine, as well as Kytos Stats delayed reports, among others. Another impact we are actually seeing is the End to End tests eventually failing in the following test case:
rerun: 0
tests/test_e2e_60_of_multi_table.py::TestE2EOfMultiTable::test_010_delete_miss_flow: 2023-09-18,07:08:29.768108 - 2023-09-18,07:08:54.694563
self = <tests.test_e2e_60_of_multi_table.TestE2EOfMultiTable object at 0x7f2759f5ad30>

   def test_010_delete_miss_flow(self):
       """Delete a miss flow so is recreated"""
       pipeline = {
           "multi_table": [
               {
                   "table_id": 0,
                   "description": "First table for miss flow entry",
                   "table_miss_flow": {
                       "priority": 0,
                       "instructions": [{
                           "instruction_type": "goto_table",
                           "table_id": 1
                       }],
                       "match": {"dl_vlan": 101}
                   },
               },
               {
                   "table_id": 1,
                   "description": "Second table for coloring",
                   "napps_table_groups": {
                       "coloring": ["base"],
                       "of_lldp": ["base"],
                       "mef_eline": ["evpl", "epl"],
                   },
               },
           ]
       }

       # Add pipeline
       api_url = f"{KYTOS_API}{OF_MULTI_TABLE_API}"
       response = requests.post(api_url, json=pipeline)
       data = response.json()
       assert response.status_code == 201, response.text
       assert 'id' in data

       # Enabled pipeline
       api_url = f"{KYTOS_API}{OF_MULTI_TABLE_API}/{data['id']}/enable"
       response = requests.post(api_url)
       assert response.status_code == 200, response.text
       time.sleep(10)

       s1 = self.net.net.get('s1')
       flows_s1 = s1.dpctl('dump-flows')
       assert 'actions=resubmit(,1)' in flows_s1

       # Delete all flows from switch 1
       s1.dpctl('del-flows')
       self.net.reconnect_switches()

       time.sleep(10)

       flows_s1 = s1.dpctl('dump-flows')
     assert 'actions=resubmit(,1)' in flows_s1
E       AssertionError: assert 'actions=resubmit(,1)' in ' cookie=0xab00000000000001, duration=13.738s, table=1, n_packets=0, n_bytes=0, priority=50000,dl_vlan=3799,dl_type=0x88cc actions=CONTROLLER:65535\r\n'

tests/test_e2e_60_of_multi_table.py:277: AssertionError

Looking into the Kytos logs we can see why this is happening:
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,093 (MainThread) kytos.core.atcp_server:INFO atcp_server:182:  Connection lost with client <IP_ADDRESS>:51402. Reason: Request closed by client
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,151 (MainThread) kytos.core.atcp_server:INFO atcp_server:182:  Connection lost with client <IP_ADDRESS>:51406. Reason: Request closed by client
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,203 (MainThread) kytos.core.atcp_server:INFO atcp_server:182:  Connection lost with client <IP_ADDRESS>:51404. Reason: Request closed by client
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,253 (MainThread) kytos.core.atcp_server:INFO atcp_server:131:  New connection from <IP_ADDRESS>:51436
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,318 (MainThread) kytos.core.atcp_server:INFO atcp_server:131:  New connection from <IP_ADDRESS>:51438
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,366 (thread_pool_sb_0) kytos.napps.kytos/of_core:INFO main:158:  Connection ('<IP_ADDRESS>', 51436), Switch 00:00:00:00:00:00:00:01: OPENFLOW HANDSHAKE COMPLETE
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,537 (thread_pool_sb_4) kytos.napps.kytos/of_core:INFO main:158:  Connection ('<IP_ADDRESS>', 51438), Switch 00:00:00:00:00:00:00:02: OPENFLOW HANDSHAKE COMPLETE
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,649 (MainThread) kytos.core.atcp_server:INFO atcp_server:131:  New connection from <IP_ADDRESS>:51440
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,773 (thread_pool_sb_2) kytos.napps.kytos/of_core:INFO main:82:  Overlapping stats request: switch 00:00:00:00:00:00:00:01 flows_xid<PHONE_NUMBER> ports_xid<PHONE_NUMBER>
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,869 (AnyIO worker thread) kytos.napps.kytos/flow_manager:INFO utils:196:  Send FlowMod from request dpid: 00:00:00:00:00:00:00:01, command: add, force: False,  flows[0, 1]: [{'actions': [{'action_type': 'output', 'port':<PHONE_NUMBER>}], 'table_id': 1, 'owner': 'of_lldp', 'table_group': 'base', 'priority': 50000, 'cookie':<PHONE_NUMBER>0485677057, 'match': {'dl_type': 35020, 'dl_vlan': 3799}}]
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,931 (MainThread) uvicorn.access:INFO httptools_impl:506:  <IP_ADDRESS>:46862 - "POST /api/kytos/flow_manager/v2/flows/00%3A00%3A00%3A00%3A00%3A00%3A00%3A01 HTTP/1.1" 202
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,922 (AnyIO worker thread) kytos.napps.kytos/flow_manager:INFO utils:196:  Send FlowMod from request dpid: 00:00:00:00:00:00:00:02, command: add, force: False,  flows[0, 1]: [{'actions': [{'action_type': 'output', 'port':<PHONE_NUMBER>}], 'table_id': 1, 'owner': 'of_lldp', 'table_group': 'base', 'priority': 50000, 'cookie':<PHONE_NUMBER>0485677058, 'match': {'dl_type': 35020, 'dl_vlan': 3799}}]
Sep 18 07:08:40 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:40,981 (MainThread) uvicorn.access:INFO httptools_impl:506:  <IP_ADDRESS>:46864 - "POST /api/kytos/flow_manager/v2/flows/00%3A00%3A00%3A00%3A00%3A00%3A00%3A02 HTTP/1.1" 202
Sep 18 07:08:41 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:41,049 (thread_pool_sb_2) kytos.napps.kytos/of_core:INFO main:158:  Connection ('<IP_ADDRESS>', 51440), Switch 00:00:00:00:00:00:00:03: OPENFLOW HANDSHAKE COMPLETE
Sep 18 07:08:41 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:41,177 (AnyIO worker thread) kytos.napps.kytos/flow_manager:INFO utils:196:  Send FlowMod from request dpid: 00:00:00:00:00:00:00:03, command: add, force: False,  flows[0, 1]: [{'actions': [{'action_type': 'output', 'port':<PHONE_NUMBER>}], 'table_id': 1, 'owner': 'of_lldp', 'table_group': 'base', 'priority': 50000, 'cookie':<PHONE_NUMBER>0485677059, 'match': {'dl_type': 35020, 'dl_vlan': 3799}}]
Sep 18 07:08:41 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:41,195 (MainThread) uvicorn.access:INFO httptools_impl:506:  <IP_ADDRESS>:46866 - "POST /api/kytos/flow_manager/v2/flows/00%3A00%3A00%3A00%3A00%3A00%3A00%3A03 HTTP/1.1" 202
Sep 18 07:08:41 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:41,794 (thread_pool_sb_6) kytos.napps.kytos/of_core:INFO main:82:  Overlapping stats request: switch 00:00:00:00:00:00:00:03 flows_xid<PHONE_NUMBER> ports_xid 18022052
Sep 18 07:08:47 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:47,294 (Thread-95) kytos.napps.kytos/of_core:INFO main:82:  Overlapping stats request: switch 00:00:00:00:00:00:00:01 flows_xid<PHONE_NUMBER> ports_xid<PHONE_NUMBER>
Sep 18 07:08:47 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:47,651 (Thread-96) kytos.napps.kytos/of_core:INFO main:82:  Overlapping stats request: switch 00:00:00:00:00:00:00:03 flows_xid<PHONE_NUMBER> ports_xid 18022052
Sep 18 07:08:54 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:54,314 (Thread-98) kytos.napps.kytos/of_core:INFO main:82:  Overlapping stats request: switch 00:00:00:00:00:00:00:01 flows_xid<PHONE_NUMBER> ports_xid<PHONE_NUMBER>
Sep 18 07:08:54 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:54,671 (Thread-99) kytos.napps.kytos/of_core:INFO main:82:  Overlapping stats request: switch 00:00:00:00:00:00:00:03 flows_xid<PHONE_NUMBER> ports_xid 18022052
Sep 18 07:08:54 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:54,859 (MainThread) uvicorn.error:INFO on:67:  Waiting for application shutdown.
Sep 18 07:08:54 runner-rmtk68xb-project-107-concurrent-0 2023-09-18 07:08:54,860 (MainThread) uvicorn.error:INFO on:78:  Application shutdown complete.

In summary: after the switch disconnects (while a flow stats requests was pending from reply), the of_core keeps waiting for the reply of the old request, until a point where it eventually clear the existing request and send a new one. Switches seems to discard flow stats requests that were sent before the switch reconnects to controller, so I believe it is safe to clear flow stats request after a switch reconnects.
Ccing @viniarck to also hear his opinion on that.

@italovalcy, thanks for reporting this and your analysis.
We have a clean up when a KytosEvent ".*.connection.lost" is received, and we're safely keeping a reference to the switch. However, what probably happened was the task was scheduled in the event loop but hasn't been executed yet, and then the new handshake happened and ended up in this case. Yes, indeed, it'd be safer to actually do a clean up right before setting the connection as established, up to that point the switch isn't "is_connected()" yet (and handshake not completed yet), so it should be safe before any flow stats request is sent.
I'll push a fix for this soon. Thanks.


Doesn't seem to work due to non-sorting --append in hasktags?

I'm trying to sort out using tags with gutentags in haskell, and find that the behavior of hasktags under this shim doesn't seem to work. The non-sorting append seems to cause vim to no longer find tags (contrary to my reading of vim docs). See https://github.com/MarcWeber/hasktags/issues/67
A simple repro would be to rename an identifier that starts with "a", then try to jump to it.
I'm on vim 8.1. Do you still use this shim, and do you find it works for you?

I'd like to use hasktags with gutentags as well. Any recent experience reports?


Feature request: Mish activator

Feature description
Hey, can I implement the Mish activator (of course as well as its unit test) for burn?
Feature motivation
It does have better performance in our projects (implemented by Tensorflow in the past).
(Optional) Suggest a Solution
I wanna do this job myself. Could I:smile:?

Yes, go ahead, if you need help or anything just ask on the discord.


Added plotshape live script

Closes issue #13

Nice to see plotshape working in a live script.
This example would naturally need more narrative text w/ scientific content to become part of a release. These future contributions might come from the Yale side.
To help get this delivered from the VORTech side, my suggestion is to create either a separate branch (e.g., 'examples-wip') or a separate folder in the directory that makes it clear they're a work-in-progress.
@ramcdougal @edovanveen


chore: Run a spellchecker

Description
This pull request fixes typos detected by tox run -e typos
Checklist

[x] I have read the contribution guidelines
[x] I have coordinated with the docs team<EMAIL_ADDRESS>if this PR deletes files or changes any file names or file extensions.
[x] This notebook or file is added to the CODEOWNERS file, pointing to the author or the author's team.

I'm sure you've probably thought of this, but any reason not to add a CI check for this in this PR?


merging by sample name

Dear @BioOmics ,
is there any option for merging fastqs based on sample ID instead of experiment ID?
thanks
best
nic

Dear @nicolo-tellini ,
Thank you for using iSeq. I apologize that currently iSeq does not have parameters to support the merging of Sample IDs. However, I am aware of another software that can fulfill your requirements, and that is fastq-dl.
Best

@BioOmics
What do you think about it as a new feature to implement?


reorg checkboxes, add load testing

cc @erik-dunteman
The bottleneck right now is in the / route, and I'm pretty sure it's due to the creation of the checkbox array. The array elements depend on the client ID in their hx_post, and I didn't see an easy way to get around that.
If we can do that at server start, I think we can get to 1M checkboxes!

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-df08693.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-9c6bbc7.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-9661209.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-da21c86.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-d15d173.modal.run

🚀 The docs preview is ready! Check it out here:     https://modal-labs-examples--frontend-preview-7b3933d.modal.run


ingest does not process parquet files correctly

I am trying to use the recipe with a directory of parquet files locally. However, MLflow is throwing the following error:

The parquet files have one column that is a date that I can read just fine using pandas or pyarrow but MLflow seems to be having problems.
My local.yaml profile...

setting line 81 to True fixed the issue, but its not clear how how this behavior can be controlled from local.yaml

adding this to the local.yaml indeed fixed my issue but leaving this open because the profiling does not seem to work 100% of the time.


Allocation in execv, execvp, and execve

The exec family of functions replace the current process with the new one, thus programs that wish to spawn a child normally call exec*() soon after a fork(). Unfortunately, fork interacts badly with threads, because of which POSIX restricts the functions that are allowed to be called after fork() to a small set of async-signal-safe functions. The part that affects Rust is that, in particular, calls to malloc() are not allowed, which means any heap allocation after fork() is forbidden. See std::process documentation and source for additional details.
The nix interface to execv, execve, and execvp calls to_exec_array to allocate the kind of array that the corresponding C functions expect. It makes sense that this is done inside exec; the argv and envp pointers are laid out in a way completely alien to Rust, and in violation to its safety rules. However, since exec* functions are typically invoked after a fork, it would be very nice to make the allocation optional, while still providing a fully safe wrapper.
One way to avoid allocation after fork and retain safety is allocate the needed buffers before forking. For example, a type that encapsulates an owning vector of C strings could be instantiated before fork(), and passed to actual exec. Since it would always store both the vector of CString objects and a vector of pointers to their content, its as_c_vec() method could produce the layout needed by exec* without further allocation:
struct CVec {
    strings: Vec<CString>,

    // nullptr-terminated vector of pointers to data inside self.strings.
    ptrs: Vec<*const libc::c_char>,
}

impl CVec {
    fn new<S>(slice: &[S]) -> Result<CVec>
        where S: AsRef<OsStr>
    {
        // ...
    }

    pub fn as_c_vec(&self) -> *const *const libc::c_char {
        self.ptrs.as_ptr()
    }
}

A safe variant of unistd::execvp() would only accept CVec objects:
pub fn safe_execv(path: &CString, argv: &CVec) -> Result<Void> {
    unsafe {
        libc::execv(path.as_ptr(), argv.as_c_vec())
    };
    Err(Error::Sys(Errno::last()))
}

Another option, which is more of a hassle to implement, but perhaps more convenient to use, is to completely encapsulate the allocation done inside the exec wrapper. It would effectively support staged execution, where first stage would prepare the needed data and return a closure that carries out the actual call to libc::exec, to be called after forking:
let do_exec = unistd::stage_execvp("cmd", &["arg0", "arg1", "arg2"])?;
if unistd::fork()?.is_child() {
    do_exec();  // handle errors
    _exit(127);
}

String arguments are supported by accepting AsRef<OsStr>, again converted to C strings before fork(). Here is an example of a library that implements this approach to wrap exec* and implement the equivalent of execvpe. (While developing this library, the code exhibited real hangs before its own exec wrapper was switched to the approach described above.)

Thanks for raising this. I need to read up a bit more on the restrictions post-fork.

I was writing a shell last weekend, and came up against this. The shell was single-threaded, but I found it quite uncomfortable to be doing allocation after fork.
Do you know if unsafety can result from allocating after fork, or is it just deadlock?

If the process has only one thread, then you have nothing to worry about. The problem arises if and only if fork() is executed while another thread holds a lock that will also be needed in the child. One thing you need to consider, though, is that a library or a crate you are using might be spawning threads behind your back.

Note that exec could require &CStr in arguments. &CString is not needed.

Hi guys,
I have filed a new PR at #975 for this. I would be glad to receive feedback and have it merged eventually.


Content Suggestion: Rabbit Hole Podcast

Link to Content: https://anchor.fm/RHJ
Briefly Describe Content: Persian Podcast about Bitcoin
Suggested Section: Podcasts

Added - Thanks

I'm the owner of the podcast, it's called "Lane Khargoosh" meaning "Rabbit Hole" in English.. maybe you can add the farsi title along with it so it won't be confused with other content that use the same name
suggestions:
Rabbit Hole Podcast/Lane Khargoosh
Rabbit Hole Podcast (Lane Khargoosh)
Rabbit Hole Podcast (Farsi)
Lane Khargoosh (Rabbit Hole Podcast)
or any other way you guyz deem it better to be presented to users