Stream source in browser?

Is there a way to support uploading from a readable stream in the browser?
I've a use case where I need to pipe my stream through some processors.

The library has not been designed to directly support your use case but, I believe, one should be able to achieve what you want to do. You may take a look at browserify and the --no-browser-field flag. However, this will remove some functionality such as resuming uploads after a tab is closed. Not sure, how much this advice helps you but some insights into your current setup may be helpful for me.

Seems there is no way to implement smth like a FileWriter so I patched the slice call to support a Promise:
    let blob = this._source.slice(start, end);
    if(blob instanceof Promise) {
      blob.then(data => xhr.send(data)).catch(err => console.error(err));
    } else {
      xhr.send(blob);
    }

Using this with a fixed chunkSize setting gives the possibility to async generate data.

I'm speaking about a stream, data is not (or should not) available at once.
In my case I've to modify all uploaded data and this is to big to do it in memory.
So I can not compute the modifiedBlob before starting the upload.
My last comment with the snippet shows how I could chunk-stream data with tus cause it fires a request for each chunk which gets resolved async through the Promise.
The trick with chunkSize and Promise works well in my case.

Thank you for your clarification. While your code example will probably work in the most cases, I believe it may fail if the server accepts only a part of the chunk and the library tries to slice your chunk in order to upload the remaining part. It is possible to get this working properly on your end but I believe this will be a thought issue to tackle. Instead, it is already possible to upload one chunk at a time which is calculated in an asynchronous fashion. This approach is not intuitive and it took me some time to get it right but I hope following example will guide you a bit: https://jsbin.com/bajeyelate/edit?js,console,output. Personally, I prefer this approach for a few reasons.

Thank you!! upload.abort() on chunkComplete is interesting...
I cant get the problematic thing with the Promise solution. At least in my case tus-js-clients requests the specific slice boundaries as it would do on regular (FileReader) Blobs and I could resolve exactly the requested peace.
Many thanks for all your stuff, I'm quite happy with the monnky-patched xhr.send in this case so I'll close this.

I cant get the problematic thing with the Promise solution. At least in my case tus-js-clients requests the specific slice boundaries as it would do on regular (FileReader) Blobs and I could resolve exactly the requested peace.

It's great to hear that this is working for your specific case. The situation I warned about does not apply to you as it is basically the opposite of what you are doing:

At least in my case tus-js-clients requests the specific slice boundaries as it would do on regular (FileReader) Blobs and I could resolve exactly the requested peace.

This cannot be achieved in every situation, e.g. when you are encoding a video, it is not easy to calculate the chunk of an encoded video at a specific offset.
Also, having to patch a library is not the most inconvenient but it depends on you :) I'm pleased to hear that I could help you!

Of course would be nice if you adopt me patch :)
And youre completly right, the slice transform thing only works for transformations which keeps the bytecount.

@Acconut will your example work if the "uploadSize" is not known in advance? Is it safe to just set it to a very large number, or might that result in data never properly being stored on the server?

will your example work if the "uploadSize" is not known in advance?

The tus protocol does indeed allow setting the length at a later moment (this is called deferring the length). However, tus-js-client currently does not implement this behaviour because at the moment no server features this functionality.

Is it safe to just set it to a very large number, or might that result in data never properly being stored on the server?

You could do it but you need to watch out for:
a) the server may have a limit for the size of the created uploads (so if you create a 1TB upload but only going to use 10GB, the server may still reject the original upload creation) and
b) the upload will never be considered completed which may bring additional difficulties with it.

Thanks! I could probably live with (a), but can you expand on what additional difficulties there might be?

Some server and client implementations expect an upload to be completed at some point. For example, the tusd allows a routine to be executed when an upload is completed which is used to notify other applications but this would obviously not work in your case. The same applies to clients, e.g. the tus-js-client would not emit the upload-complete event. Furthermore, on both sides resources may only be freed when an upload is finished or terminated.

@anonimousse12345 I am sorry that it's not easily possible to use tus-js-client for your application because tus-js-client (and also tusd) both don't supported the principle of deferred lengths yet. If you would like to work on these features, I am more than happy to assist you :)


cephfs: remove explicit size setting of cloned volume

CephFS csi driver explictly set the size of the cloned volume
to the size of parent volume as cephfs mgr was lacking this
functionality previously. However it has been addressed in cephfs
so we dont need explicit size setting.
Ref# https://tracker.ceph.com/issues/46163
Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

/retest ci/centos/mini-e2e-helm/k8s-1.22

Can you add a link to the Ceph change that added the capability?

Can you add a link to the Ceph change that added the capability?

@nixpanic added the tracker too. Thanks !

@humblec if someone still using the older cephfs version this will break cloning?

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

what if the user is not planning to update the ceph version but if they are updating the cephcsi version?
IMHO this is a breaking change from the cephcsi side and also need to update the support metrix https://github.com/ceph/ceph-csi#support-matrix

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

what if the user is not planning to update the ceph version but if they are updating the cephcsi version?

@Madhu-1 Which ceph version is referred here?

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

what if the user is not planning to update the ceph version but if they are updating the cephcsi version?

@Madhu-1 Which ceph version is referred here?

I was thinking the fix was done on the server-side. If the fix is in the client package we are good. Just need confirmation

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

what if the user is not planning to update the ceph version but if they are updating the cephcsi version?

@Madhu-1 Which ceph version is referred here?

I was thinking the fix was done on the server-side. If the fix is in the client package we are good. Just need confirmation

Its in the mgr code, does that answer the concern @Madhu-1 ?

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

what if the user is not planning to update the ceph version but if they are updating the cephcsi version?

@Madhu-1 Which ceph version is referred here?

I was thinking the fix was done on the server-side. If the fix is in the client package we are good. Just need confirmation

Its in the mgr code, does that answer the concern @Madhu-1 ?

@humblec If this is tested with different ceph versions and everything is working fine. am good.

@Madhu-1 the PR looks to be backported to supported ceph versions, so it looks safe.

what if the user is not planning to update the ceph version but if they are updating the cephcsi version?

@Madhu-1 Which ceph version is referred here?

I was thinking the fix was done on the server-side. If the fix is in the client package we are good. Just need confirmation

Its in the mgr code, does that answer the concern @Madhu-1 ?

@humblec If this is tested with different ceph versions and everything is working fine. am good.

Ceph versions equal or above - v16.0.0, v15.2.9, v14.2.12 has the support. I think that should be fine, as we also just promoted clone functionality from alpha to beta in last release 3.4.0

@nixpanic ptal.  Thanks!

Looks reasonable to me, @kotreshhr do you have anything to add to this?

Looks reasonable to me, @kotreshhr do you have anything to add to this?

Nope, looks good to me.

Looks reasonable to me, @kotreshhr do you have anything to add to this?

Nope, looks good to me.

Thanks @kotreshhr ..
@nixpanic @Yuggupta27 ptal ..

/retest ci/centos/mini-e2e-helm/k8s-1.20

/retest ci/centos/mini-e2e-helm/k8s-1.21

/retest ci/centos/mini-e2e/k8s-1.21

@Mergifyio rebase

/retest ci/centos/mini-e2e/k8s-1.22

@Mergifyio rebase

Going crazy with this PR..  Tired off rebasing and e2e failures !!!

/retest ci/centos/upgrade-tests-cephfs


DCO is too strict on the submitter's name

https://github.com/hyperledger/sawtooth-core/pull/1002

Just to clarify, @cclauss, you're suggesting that the signoff name shouldn't have to match the commit author? Here is the commit in question:
From 376dee629950d001716f46df7be41713c16ae531 Mon Sep 17 00:00:00 2001
From: cclauss<EMAIL_ADDRESS>Date: Sat, 14 Oct 2017 09:35:11 +0200
Subject: [PATCH] Remove unused method _generate_id()

Implement  #882 in a way that satisfies the DCO bot.

Signed-off-by: Chris Clauss<EMAIL_ADDRESS>
The challenge is that using git commit --signoff will use whatever is configured in git for the author field, and the DCO documentation recommends using your full name.
From the kernel docs:

then you just add a line saying

       Signed-off-by: Random J Developer<EMAIL_ADDRESS>
using your real name (sorry, no pseudonyms or anonymous contributions.)

So while the docs don't say anything about what should be included in the author field, I would expect it to be the same since it is the default value for the --signoff flag.
Thoughts?
cc @mlinksva @mkdolan @caniszczyk

I believe all the tool checks is that the author's name matches the signed-off-by name. Is that correct @bkeepers?
By example, the Linux kernel community manually checks this, so they know it's not an anonymous person or pseudonym, but I'm not sure how you can do what Chris suggests. One way might be to check for the author name to match or the prefix on the email address to match the signed-off-by name. (just thinking out loud a way around the error Chris points to).
Another issue asked if the author and signed-off-by had to come from the same person (which is not required), but I'm not sure where things ended up there.

So while the docs don't say anything about what should be included in the author field

Really?  I thought that it said:

using your real name (sorry, no pseudonyms or anonymous contributions.)

My real name is Chris Clauss and username/handle/pseudonym is cclauss.  The current DCO seem to be ensuring that I do not sign-off using my real name but that I use a pseudonym instead.

@cclauss when you go into your command line what is you git user's name? As in: $ git config --global user.name. The DCO check is based off of this name, so I'm curious if you set it to be your real name as opposed to your handle.

Ahhhh...  This is the best question yet.  The PR in question was the deletion of four contiguous lines of code.  I really did not need and did not choose to use git in the execution of this PR.  I merely used the GitHub web ui to edit the file, delete the four lines, and create a signature line to match the Random J. Developer example above.  Given that probot comes out of GitHub, I had thought that it would would support the use of the GitHub web ui in addition to the commandline .  Perhaps the best approach would be to add a sign-off checkbox to the GitHub web ui.

Upon clicking on your profile @cclauss, it appears you don't have a first/last name set, so the only name GitHub knows you as is cclauss, which was not what you signed off as, which is why the DCO check failed.
I think there's an interesting take-away about whether or not git usernames (ie mine is hiimbex) could count as a sign off name, but the kermel docs say:

using your real name (sorry, no pseudonyms or anonymous contributions.)

So since I think this specific instance is just user error, I'm gonna close this out.

Makes sense.  Thanks to all.

Thanks for working through this Chris.
On Tue, Oct 17, 2017 at 4:13 PM, cclauss<EMAIL_ADDRESS>wrote:

Makes sense. Thanks to all.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/probot/dco/issues/43#issuecomment-337356102, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHDmBSezQuc89nsKypzN0GFaOZrk-YH-ks5stQpwgaJpZM4P5TNn
.


Laravel Integration

How do I add this template to my laravel application?

I think you can try to place vuestic-admin into resources/js folder, then somehow replace access point from app.js to src/app/main.js.
But general recommendation would be to keep vue-cli project separate (backend would only serve view). That allows to prevent a lot troubles.


PPC: Fix validation error on PolyBenchC

Hi team, please consider.
As described in #8380, when running PCC validation on workloads like PolyBenchC, it will report an UnsupportedFact error.
Based on the analysis of trace logs, I think attach_constant_fact introduced by #8173 should also consider the type of constant when adding facts for iconsts. After #8173, we may generate the following facts for i32 constants:
block9:
  v4339 ! range(64, 0xea28, 0xea28) = iconst.i32 0xea28
  v2858 ! range(64, 0x8, 0x8) = iconst.i32 8
  v4406 ! range(64, 0x115a0, 0x115a0) = iconst.i32 0x0001_15a0
  v4407 ! range(64, 0x115a8, 0x115a8) = iadd v4406, v2858  ; v4406 = 0x0001_15a0, v2858 = 8

These i32 constants have their bit_width set to 64, causing the error.
#8173 also exposes another issue on AArch64 when generating facts for MovK, we should calculate the running value for MovK with the field mask.

@jameysharp Thanks for the review!

and he may not be able to get to it until next week.

That’s okay, we can wait until @cfallin comes back!


Research sentry and see if it can be integrated for error reporting issues during production

As a user, I don't want to have to make bug reports when I am having issues.
In our code, we should catch errors and report them to an online service. This is exactly what Sentry was made for.
See here for the official Electron SDK. Although this isn't essential, we want to do this before we put out any releases. Additionally, it should be a pretty good first issue for anyone who wants it.

Hi! I got very interested on helping the project, and I think this is a great first task to work on.
Do you have a Sentry account already defined? Can you give me the DSN or share with me the username / password for the Sentry of DAWG?

Hey @heitorsilva, sorry for the slow reply!
Here is the DSN:
<EMAIL_ADDRESS>
I've never used sentry before today but it seems very slick :) Also excited that you're interested in contributing to this project. Just so you're aware what I'm working on at the moment, I am currently  refactoring the core audio system (currently based on Tone.js) to have zero dependencies (ie. just use the Web Audio API). If there is anything that I can help with let me know :)

Oops try this DSN code actually:
<EMAIL_ADDRESS>
Do you have a sentry account so that I could add you to the team?

Yes, I do. Try searching for the email<EMAIL_ADDRESS>

Just submitted an application to get an account as an open source project :) Once I get an account I can add you!

Ok sorry for the delay, but I've added you to the project :) You should be able to access it using this link!

Hey @jsmith! I entered the link and requested to participate on the organization.
Also, can you put me with some kind of permission here in GitHub, so I can take the issue for me? Or, maybe assign me to this issue here?

Just saw I had an email on my spam folder, to join Sentry. Now I can work on this... thx ^^

I assigned you this issue but also invited you (with basic permissions for now) to this repo :) Definitely let me know if you have any questions. I'd love to take some time to improve the documentation!

@jsmith please, can you go to https://sentry.io/settings/dawg/projects/dawg/ and configure the Allowed Domains box to have only dawg.dev?

Done!

@jsmith sorry, but actually, since we run as an Electron App, it's better to leave with the "*" we had before on https://sentry.io/settings/dawg/projects/dawg/. We'll have to think on the security aspect of the DSN later... can you change it back, please?

No worries, just changed it back!

Done: https://github.com/dawg/dawg/pull/173

Thanks for your help with this :)


spawn zeek on windows with new hidden subcommand

This adds a hidden zqd subcommand "winexec", that executes a command
using the same job object based spawned process termination we are
already using in the windows zeek-launcher utility. Use this subcommand
when we launch zeek on windows. This is a first step to treating zeek as
more of a black box from inside zqd, so that users can run their own
zeek setup.

Rather than use a subcommand like this, it might be a little cleaner and clearer to

start the Zeek process with CREATE_SUSPENDED,
create and configure the job object (including adding the Zeek process to it) in zqd,
use DuplicateHandle to give the Zeek process a handle to the job object,
close the job object handle in zqd, and finally
call ResumeThread on the Zeek process's thread.

Rather than use a subcommand like this, it might be a little cleaner and clearer to

So, funny story, I tried that first. :) And though it worked, I didn't like the solution, because of what it took to get the thread to resume:
If you create the process with CREATE_SUSPENDED, when you want to resume it, you have to resume the processes main (only) initial thread, via ResumeThread. To call ResumeThread, you need a handle to the thread, and for a handle, you need the thread id.
To get the thread id, the only option I found is to use the win32 api CreateToolhelp32Snapshot, and then iterate through all threads in the system (!), looking for the one with the correct parent process. Even if you specify only the process id you're interested in, the CreateToolhelp32Snapshot will always take a snapshot of the state of every system thread, and give you a handle to that snapshot, which you then need to iterate on with other calls.
I implemented all of this myself, both the create suspended & resuming the thread, and got it working. I later found that there's a test utility in the go source code that implements the resume handling:
https://github.com/golang/go/blob/master/src/runtime/syscall_windows_test.go#L828
If it were possible to get the created processes thread id through the exec.Cmd calls, this would be much easier. But that information is thrown away in syscall.StartProcess, which is near the bottom of the chain of exec.Cmd.Start().
Overall, I thought that needing to have all the extra syscall definitions, and then creating a snapshot of all system threads & iterating on it, felt pretty complex to have around. So that led me to this PR's approach.
So with more knowledge about the implementation, let me know what you think between the two approaches.


Fixes issue #11308: Impala Connection overflow on profile and missing CHAR datatype.

Describe your changes:
Fixes #11308

Added the char data type in a using the similar the Hive connection used.  Also added the Real datatype after comparing the datatypes listed at https://impala.apache.org/docs/build/plain-html/topics/impala_datatypes.html vs the data types that were already included in the sqlalchemy _impala_type_to_sqlalchemy_type .
Added a custom Sum function for the Impala Dialect that casts the value to Double instead of bigint.  This handles the huge numbers I was seeing in our data.

Type of change:

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

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@ksirmons it looks like your branch is behind. Could you rebase your branch from main

This PR was re-implemented from a better starting branch..  #11364


[QA-447] Removing RP-stub check and logout step in Auth sign-in journey

QA-447
What?

removes the Logout Step of the signIn Journey
removes the RP Stub check

Changes:

remove rpStubCheck boolean
edit B02_SignIn_05_AuthMFA_EnterTOTP POST and B02_SignIn_07_SMSMFA_EnterOTP POST steps, to an if > else statement to only check for terms and conditions update, and remove the RP stub checks.

Why?

to run a successful Authentication signIn journey

Whilst we are removing stub only calls, can you remove the logout step from the signUp scenario too?


where clause on relation

I have a relationship like this https://prnt.sc/xdh5xi and I need to select rows based on movies.name. How should I do?

There are couple of ways at least:
await Person.query()
  .distinctOn('persons.id')
  .joinRelated('movies')
  .where('movies.name', name)

distinctOn only works on postgres though. Here's another way using a subquery:
await Person.query()
  .whereExists(Person.relatedQuery('movies').where('name', name))

Note that these are both just SQL wrapped in a nice package. That's what objection is.
When you have a problem like this, first find out how you would do this with raw SQL and then simply translate that to objection code. You can then gradually refactor the code and start using objection specific helpers like joinRelated and relatedQuery when you lear about them.
You can always add .debug() to any query and objection will print the generated SQL.

There are couple of ways at least:
await Person.query()
  .distinctOn('persons.id')
  .joinRelated('movies')
  .where('movies.name', name)

distinctOn only works on postgres though. Here's another way using a subquery:
await Person.query()
  .whereExists(Person.relatedQuery('movies').where('name', name))

Note that these are both just SQL wrapped in a nice package. That's what objection is.
When you have a problem like this, first find out how you would do this with raw SQL and then simply translate that to objection code. You can then gradually refactor the code and start using objection specific helpers like joinRelated and relatedQuery when you lear about them.
You can always add .debug() to any query and objection will print the generated SQL.


Caching

ASP.NET 5->Fundamentals->Caching

Output caching
In memory cache
Distributed cache
Using Redis

Working on this now, @danroth27

Unless I'm missing something, Output Caching is an MVC feature, @danroth27

Opened #733 for Output Caching.
@danroth27 Need to meet to discuss this topic and whether it makes sense to split Distributed Caching and Redis into a separate article (in memory cache article is already about 4-5 pages long).


perf(client): lazy load sparkles

Pull Request Test Coverage Report for Build 1649

3 of 5 (60.0%)  changed or added relevant lines in 3 files are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-10.5%) to 63.793%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/src/shared/components/Sparkles.tsx
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

client/src/shared/utils/random.ts
1
50.0%

client/src/shared/components/Sparkles.tsx
5
9.09%

client/src/shared/hooks/useRandomInterval.hook.ts
12
6.25%

Totals

Change from base Build 1647:
-10.5%

Covered Lines:
101

Relevant Lines:
152

💛  - Coveralls


test: use '#teleports' target instead of 'body'

🔗 Linked issue
https://github.com/nuxt/nuxt/issues/28483

📚 Description

Since the recommended teleport target is now '#teleports', I figured it would be a good idea to update this test fixture as well. Not sure if it won't break something, though 🙈

We likely also need to update the test assertions.

Yeah
I'm trying to figure out how to get rid of a playwright error to run the tests locally so that I can verify it after updating them.

You need to run npx playwright install.

@danielroe
So, for the basic tests, the teleportId is set to 'nuxt-teleport':
https://github.com/nuxt/nuxt/blob/52faf52cdef63835d02e6da6b30c34c4f6ad64cd/test/fixtures/basic/nuxt.config.ts#L19
There is already a test case for it:
https://github.com/nuxt/nuxt/blob/52faf52cdef63835d02e6da6b30c34c4f6ad64cd/test/basic.test.ts#L2700
Is it worth keeping the <teleport to="body"> test, given that this is a use case that is not recommended?
Should the default case be tested as well? If so, should I test it under a separate Nuxt instance, since the one in the basic tests has a custom teleportId & teleportTag ?


Test failures when running tests in Docker (exit status 127)

Expected behavior
All tests pass in Docker.
Actual behavior
Tests from server and cmd packages fail when run in Docker.
 Running go test with -v produces no output relevant to the failure.
Information about your environment (OS/architecture, CPU, RAM, cluster/solo, configuration, etc.)
I reproduced this on Docker for Mac with both the golang:latest and ubuntu:latest Docker images (ubuntu:latest requires additional setup).

I traced this failure to an fdatasync system call from boltdb... not sure where to go from there, but it may not be worth spending time on.

Any progress? This is quite a bumper for our test suite.

@ps23 unfortunately there is no update on this - when I tried to track it down last year, it didn't seem to be an issue with Pilosa, but rather something to do with docker's interaction with fdatasync. Unless you're able to dig into this, I'd suggest trying to find a workaround as I don't think we'll be able to dedicate resources to this issue in the near term.

The command in this ticket runs just fine for Pilosa master with the following configuration:

Ubuntu 18.04
Docker 17.12

@ps23 Could you give some information about your OS, Docker version if you are still having an issue?

Closing this, since the issue seems to be resolved. Please reopen this in case there are problems.


NullInjectorError: No provider for InjectionToken FirebaseAppConfigToken!

I've been busy all night to get firebase working in my Angular 5 application. I've been bouncing from Stackoverflow to Github, and back, but with no solution for something seemingly basic usage.
Just to get it to work, I've created a blank project using ng new, and getting firebase to work. No fancy stuff, just basic this.example = this.db.list('example'); and then showing it on my page. No such luck.
I've tried:

https://github.com/angular/angular/issues/20101
https://github.com/angular/angularfire2/issues/1155
https://github.com/angular/angular/issues/20339
Probably way more, but I can't recall/list em all

Angular:
^5.0.0
Firebase:
4.8.2-0
AngularFire:
5.0.0-rc.5-next
How to reproduce these conditions
Steps to set up and reproduce
I've created a new project using ng new AngFir, the adding the above mentioned dependencies.


Implement Navigator to-spec

Adds a variety of missing properties to Navigator:

appCodeName, product, productSub, vendor, and vendorSub from NavigatorID
language and languages from NavigatorLanguage
onLine from NavigatorOnLine
javaEnabled() from NavigatorPlugins (fixes #1467)

We now emulate Chrome a bit more closely: we follow the spec with "navigator compatibility mode" of Chrome, which locks down appName, platform, and version to be more browser-like instead of Node.js-like. The default userAgent similarly gains a suffix "AppleWebKit/537.36 (KHTML, like Gecko)".

Blocked on https://github.com/jsdom/webidl2js/issues/22 which breaks navigator.platform and thus prevents the web platform tests from passing.
@Sebmaster might also want to give it a look for advice on webidl2js usage; given all the partial interfaces floating around I wasn't sure this was the best setup.

Looking pretty good to me. :tada:


The title in the sliver appbar is not properly centered if centerTitle is true when navigating to other routes

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Create a fresh project
Add a new page and use the material page route to navigate to it
Run the project on Android.
Navigate to another page
the title is not centered in the sliver appbar.

Also, I checked the issue on the master channel and it was not there. So it's probably fixed but I couldn't find any issue. Please check if that fix can be cherry-picked into stable.
Expected results
The title is centered properly
Actual results
The title appears to be shifted towards right.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
          colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
          useMaterial3: true,
          appBarTheme: const AppBarTheme(centerTitle: true)),
      home: const MyHomePage(),
    );
  }
}

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

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: const Text('App bar'),
        actions: [
          IconButton(
            onPressed: () {
              Navigator.push(
                context,
                MaterialPageRoute(builder: (context) => const Settings()),
              );
            },
            icon: const Icon(Icons.settings),
          ),
        ],
      ),
      body: const Center(
        child: Text('home'),
      ),
    );
  }
}

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

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: CustomScrollView(
        slivers: [
          SliverAppBar.large(
            leading: IconButton(
              onPressed: () => Navigator.pop(context),
              icon: const Icon(Icons.arrow_back_outlined),
            ),
            title: Text(
              "settings",
              style: TextStyle(
                color: Theme.of(context).colorScheme.primary,
              ),
            ),
          ),
          const SliverToBoxAdapter(
            child: Column(
              children: [
                Text("settings"),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
                SizedBox(
                  height: 100,
                ),
              ],
            ),
          )
        ],
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]
On flutter 3.7.12, the issue is not there:

Flutter stable 3.10.4 has it:

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Flutter 3.10.4 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 682aa387cf (8 days ago) • 2023-06-05 18:04:56 -0500
Engine • revision 2a3401c9bb
Tools • Dart 3.0.3 • DevTools 2.23.1

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.4, on Microsoft Windows [Version 10.0.22621.1778], locale en-IN)
[✓] Windows Version (Installed version of Windows is version 10 or higher)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
[✓] Chrome - develop for the web
[!] Visual Studio - develop for Windows (Visual Studio Community 2022 17.6.0)
    ✗ Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop development with C++" workload, and include these components:
        MSVC v142 - VS 2019 C++ x64/x86 build tools
         - If there are multiple build tool versions available, install the latest
        C++ CMake tools for Windows
        Windows 10 SDK
[✓] Android Studio (version 2022.2)
[✓] VS Code, 64-bit edition (version 1.79.0)
[✓] Connected device (4 available)
[✓] Network resources

Hi @milindgoel15
This is fixed by https://github.com/flutter/flutter/pull/122542. However, the fix isn't available in the stable 3.10.x channel yet,  currently it is available on beta and above.
It should be available in the next major stable release. Closing as fixed.

I have just tested the beta and the center title is fixed. I came across another problem, the font size of the title is not respected as it was in the stable.
This is my appbar theme config:
    appBarTheme: AppBarTheme(
      elevation: 0,
      scrolledUnderElevation: 8,
      toolbarHeight: 64,
      color: darkDynamic.background,
      surfaceTintColor: darkDynamic.secondaryContainer,
      titleTextStyle: TextStyle(
        color: darkDynamic.onBackground,
        fontSize: 20,
        fontFamily: "CircularStd",
      ),
      systemOverlayStyle: const SystemUiOverlayStyle(
        statusBarColor: Colors.transparent,
        statusBarIconBrightness: Brightness.light,
        systemNavigationBarIconBrightness: Brightness.light,
      ),
    ),

Beta:

Stable:

This is expected. Too large an expanded title will get cut off, so this is limited just like the regular app bar title.  See https://github.com/flutter/flutter/pull/125038
You can try it on Android Compose as well by changing the device font size.

So the font size will have no impact on medium and large app bars from now?
According to the m3 docs, font sizes of both medium and large should be headline small and headline medium respectively. So how do we set them now? While making sure the regular app bar title stays on the title large font size.

So the font size will have no impact on medium and large app bars from now? Although by testing the stable channel, the fontsize doesn't affect sliver appbars only the normal appbar. So it was already respecting the headline font size from m3 docs.

There might be some confusion. Please file a new issue with all the details and a complete sample. (as the current issue isn't related)

According to the m3 docs, font sizes of both medium and large should be headline small and headline medium respectively.

The defaults already match M3 specs.
https://github.com/flutter/flutter/blob/40bb615b0c96b2ca2ec2777fe9ea6aa20c815b14/packages/flutter/lib/src/material/app_bar.dart#L2393-L2419


Random User Generator

It will use Random User API as input and will get the random User when the Click Button with some Details
I want to work on this project.
Please @ urvashi-code1255 and @ Vishal-raj-1 assign me for this project.
I am a GSSOC'21 participant and wants to contribute to this project

@WebVishal Random User project is already present in the project, let me know if you can modify it :)

@urvashi-code1255  It's not yet listed on Project Section how I can try to modify ;)

@WebVishal Are you interested?
Let me know I will assign it to you.

@991rajat  Sure sir 🥰, How long have I been waiting to work on this project, please assign me

Hey @WebVishal Go Ahead develop a new project for this  don't modify existing project.


Tag events in the git log

Tag events that would be useful for feeds and nostr posts, e.g. new listings, sales, mintings.

Converted git comments to JSON in https://github.com/macterra/artx-market/commit/be1aa78ff098421fe8c49abdb9c073e955fd0c57


PropValue creates unaligned pointer references for multi-value types

After upgrading to the 1.78 Rust toolchain, I started getting a panic! in slice_from_raw_parts when converting the unaligned pointers in value.Value.MVszW.lppszW to a &[PCWSTR] slice, because the address of SPropValue::Value.MVszW.lppszW is 32-bit aligned, but it's pointing to an array of 64-bit pointers. This will affect any multi-value type using pointers on a 64-bit platform or any other element that is more than 32-bits wide, such as f64.

Correction, it's not the unaligned data member, it's that the subsequent buffers are packed into unaligned locations in memory. It seems to happen very consistently with PT_MV_UNICODE values, but I suspect it's possible for any SPropValue with a pointer to another location.


docs: Make serverdir/node path consistent with other docs

internal.sock resides in the data dir, which is /serverdir/node in the rest of the "Run your node" docs. In the CLI docs, we just used /serverdir/internal.sock. This PR adds the node subdirectory to make it consistent.

Followup PR #159


Use Ubuntu 14.04 in Travis for Python 2.6

The default OS was switched a while ago from Trusty (14.04) to Xenial (16.04) in Travis. And tests are failing as Python 2.6 isn't supported in Xenial.
This PR makes tests for Python 2.6 run in Trusty again.
Another option is to completely drop support for python 2.6. But I don't see a reason to since it can still work for now.

LGTM, thanks for the contribution! :)


OSError: [WinError 126] The specified module could not be found

Informations

Qiskit version: 0.20.0
Python version: 3.7.8
Operating system: Windows 10

What is the current behavior?
Currently, I switched from a Linux based system to windows based.
I am getting this error whenver I try to import qiskit.
from qiskit import *
from qiskit import QuantumCircuit

Both doesn't work
What is the expected behavior?
The expected behavior should that the qiskit should get imported without any errors.

It should wok, unless there is a path mismatch or something else. If you receive 'importerror', saying 'qiskit not found', then in this case your qiskit installation is faulty. If you receive some other error, Can you share a screen shot of the error you receive.
Best I would recommend a creating a clean environment and trying. Follow the installation instructions on Qiskit.

@deeplokhande The problem got resolved after reinstalling python. Python from the default Windows Store is giving errors similar errors to many. So installed it from the original website. Therefore closing the Issue

Cool!!


Data

[ ] identify all data needed in script so we can place it somewhere
[ ] implement #27 so we can test compression
[ ] add section to document about this while refering to cloudmesh data and use general description for compression and result
[x] create  laszewsk/mlcommons-data-eartchquake
[ ] place data on github
laszewsk/mlcommons-data-eartchquake

See #20 for the identified missing data from the release.
Note that this still assumes that the data in the 1950start folder in the google drive share is up-to-date: https://drive.google.com/drive/folders/1wz7K2R4gc78fXLNZMHcaSVfQvIpIhNPi
It looks like this for those not members of mlcommons:

I have ondone the #27 task so we can recertify this. data was uloaded to github, but we have not tested to uncompress and see if it is the same.


Auto generate first workfile base on build template with workfile

In GitLab by @support-bot on Mar 6, 2023, 13:26

From Olivier

We would like when there is no workfile, that when we launch the task with the soft (maya, nuke) that the Build workfile from template auto execute
Softwares concerned
Maya, Nuke, Fix

@friquette can you add the PR to this issue.

PR => https://github.com/ynput/OpenPype/pull/5077

cyclic import solve


Docker Setup

Hello guys!
I've added an new option to setup development environment. Docker removes the need to install dependencies manually.
Hope it helps. (:

Thanks for the PR!
We're not interested in adding Docker to the project right now, so I'm closing this PR. Since our dependencies are simple, we don't think the added Docker dependency is worth it.
I'll take a look at your other PR shortly!


feat:(Core) prevents Amplify.configure while running for SwiftUI Previews

Previews crash when it is not possible to load awsconfiguration.json when Amplify.configure is run which prevents this feature from working in Xcode.
Issue #, if available:
#1508
Description of changes:
Check points: (check or cross out if not relevant)

[x] Added new tests to cover change, if needed
[x] Build succeeds with all target using Swift Package Manager
[x] All unit tests pass
[x] All integration tests pass
[x] Documentation update for the change if required
[x] PR title conforms to conventional commit style
[x] If breaking change, documentation/changelog update with migration instructions

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This Swift package was created to test this change. It includes setup.sh to clone the required repo.
1508-previews.zip

Codecov Report

Merging #1509 (9c5b5e0) into main (4cb25de) will increase coverage by 0.52%.
The diff coverage is 86.87%.

@@            Coverage Diff             @@
##             main    #1509      +/-   ##
==========================================
+ Coverage   58.24%   58.76%   +0.52%
==========================================
  Files         675      678       +3
  Lines       20565    20792     +227
==========================================
+ Hits        11978    12219     +241
+ Misses       8587     8573      -14

Flag
Coverage Δ

API_plugin_unit_test
61.57% <100.00%> (+0.07%)
:arrow_up:

AWSPluginsCore
73.10% <72.22%> (+0.23%)
:arrow_up:

Amplify
46.01% <61.53%> (+0.05%)
:arrow_up:

Analytics_plugin_unit_test
71.76% <ø> (ø)

Auth_plugin_unit_test
78.96% <100.00%> (+0.20%)
:arrow_up:

DataStore_plugin_unit_test
75.72% <86.87%> (+1.18%)
:arrow_up:

Predictions_plugin_unit_test
26.81% <ø> (ø)

Storage_plugin_unit_test
58.06% <ø> (ø)

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

Impacted Files
Coverage Δ

...ies/DataStore/Subscribe/MutationEvent+Schema.swift
0.00% <0.00%> (ø)

...lugins/API/AWSAPICategoryPlugin/AWSAPIPlugin.swift
100.00% <ø> (ø)

...Configuration/AmplifyAWSServiceConfiguration.swift
82.60% <ø> (ø)

...WSPluginsCore/Sync/MutationSync/MutationSync.swift
32.60% <0.00%> (ø)

...tegoryPlugin/Sync/RemoteSyncEngine+Retryable.swift
78.37% <ø> (-0.57%)
:arrow_down:

...Engine+IncomingEventReconciliationQueueEvent.swift
54.54% <33.33%> (-7.96%)
:arrow_down:

...lify/Core/Configuration/AmplifyConfiguration.swift
88.40% <40.00%> (-3.79%)
:arrow_down:

...cileAndLocalSave/AWSModelReconciliationQueue.swift
80.74% <50.00%> (ø)

...gin/Subscribe/DataStoreObserveQueryOperation.swift
75.28% <68.42%> (-1.77%)
:arrow_down:

...WSDataStoreCategoryPlugin/AWSDataStorePlugin.swift
71.77% <81.81%> (+4.15%)
:arrow_up:

... and 33 more

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 a581adb...9c5b5e0. Read the comment docs.

i don't think feat:(Core) will get picked up by the release scripts as a Core feature, since (Core) is after the semicolon, just FYI we may need to manually modify the changelog later

I never had issue with my projects' using Amplify to run previews - until this release 😬
Do you have any guidance to condition the use of plugins methods as the Amplify.isConfigured is inaccessible due to 'internal' protection level?
I would love to avoid use of target environment compiler's directive #if targetEnvironment(simulator)
Best,

@hervenivon .. It would be nice if you could comment on the issue https://github.com/aws-amplify/amplify-ios/issues/1508 with the exact problem you are facing for tracking purposes. May be provide some examples of why you think the solution in the PR should be avoided. It will help us to prioritize and resolve your issue. Thanks.

@harsh62 I believe I'm facing the same issue as @hervenivon.
Before the update to 1.17.0, previews worked fine. This is presumably because Amplify.configure worked because I had a awsconfiguration.json file in the project, unlike the problem case where the code was in a Swift Packages (i.e. issue #1508). Use of any following methods such as Amplify.Auth.fetchAuthSession then worked, since Amplify was configured.
With 1.17.0, I now find that the previews all crash. This is because the changes in this PR mean that Amplify has not been configured before Amplify.Auth.fetchAuthSession is used by the preview process, and hence there is a fatal error.
What's the intended approach to avoid this crash? I don't believe there is any method to check whether Amplify is configured so the only solution I have been able to use is checking for ProcessInfo.processInfo.environment["XCODE_RUNNING_FOR_PREVIEWS"] != "1" before calling any Amplify methods.
I'm assuming there is a better solution though. Unfortunately, the documentation doesn't seem to address this anywhere so far as I can see.

Any update on this?


Thread interruption when executing the callback is not propagated

Hi,
The doc of rejectionPredicates would lead to think that if the thread is interrupted during the execption of the callback, the call won't be retried:
"the predicates used to decide if the attempt must be rejected or not. If an attempt is rejected, the retryer will retry the call, unless the stop strategy indicates otherwise or the thread is interrupted."
However, this is not the case. I think that a more consistent behaviour would be to exit the retrier if the thread is interrupted during the execution of the callback, and not only during the sleep.

Thanks, and I agree. But this is a duplicate of #24.


Incompatible with Ghidra V 9.1.2

Seems like the latest build is incompatible with Ghidra's 2020-Feb-12 release.

is there any solution for this problem?

Not really a solution but I simply use radare's ghidra bridge...

Not really a solution but I simply use radare's ghidra bridge...

Do you have any tutorial or whatever that would quick start me into debugging this way?

I mean it won't provide code wise stepping but, if you use radare's debugger you could look at ghidra's decompilation which I believe is the most useful feature. https://github.com/radareorg/r2ghidra

I found this plugin https://github.com/bootleg/ret-sync which works with the latest ghidra, it also consumes less memory. I also use a gdb plugin https://github.com/cyrus-and/gdb-dashboard to watch registers in real time.


I expected just 3 to work and replace symlinks with the templated file.
May be related to #791
Meta
System: Linux
  Platform: Linux-5.13.0-40-generic-x86_64-with-glibc2.34
  Release: 5.13.0-40-generic
  Machine: x86_64
pyinfra: v2.1
Executable: env/bin/pyinfra
Python: 3.9.9 (CPython, GCC 10.3.0)

I thought this would be a workaround:
server.shell(["[[ -L /etc/resolv.conf ]] && rm /etc/resolv.conf"])
--> Starting operation: Server/Shell (['[[ -L /etc/passwd ]] && rm /etc/resolv.conf'])
    [dash] sh: 1: [[: not found
    [dash] Error

I think you want the force option.  You should be able to only have one operation when using force.
So you should be able to get away with doing:
from pyinfra.operations import files
files.file(path='/tmp/resolv.conf', present=False, force=True)

And this should work for both symlink and regular files.
The downside of doing this is the file is renamed, instead of fully being deleted.

I think this is correct - by default the files.[link|directory|file] operations will raise these errors if the path exists and doesn't match the desired type. The force=True argument can be used to rename before creating the expected path. There is also a force_backup (default True) that can be set to False to remove the path without backup.
The files.template operation does not check anything about the target path which is why it'll work whether the path is a link or a file. I think this makes sense so a template could be written to a link directly?
So I'm not sure there's a bug to fix except maybe the error messages need improvement, something like:

--> pyinfra error: path /etc/resolv.conf already exists as a , use force=True to move the  and create the  (<include call location here)


Fix VPN create

This PR will fix VPN create command. Past VPN failed to execute command on VPN container because VPN container was not yet registered to Master. With this PR cli waits until container is present and continues execution after that.

Imho this is not the right way to fix this bug... I'll push an alternative fix soon.

Closing in favor of #1537


Add PlatformText utility to have specific platform strings

This PR adds PlatformText. It is a wrapper to access strings localized for the platform.
It permits new and unknown platforms to edit (some specific) text shown by the editor and the game.

This line isn't hardcoded in the editor, it's based on strings found in platform/macos (not included in this PR)
For now, this PR doesn't implement any new lines. It just setups the class.
Relates to #92984

Open question: should we use StringName instead of PlatformTextID and PlatformTextEditorID? Could be interesting for custom builds of Godot without having to resort to edit an enum for new lines.

Aside from the "Show in Finder" thing, what are examples of strings that need to be platform specific in this way?
Adding a whole abstraction just for that seems overkill to me.

Aside from the "Show in Finder" thing, what are examples of strings that need to be platform specific in this way?
Adding a whole abstraction just for that seems overkill to me.

This opens the possibility to really localize the engine for each platform. But other than the tangible "Show in Finder" issue, I don't know yet. Maybe @bruvzg, @shana, and @m4gr3d could have some ideas.

I'd wait until we have at least a few different practical use cases, and those use cases have been confirmed and implemented

Aside from the "Show in Finder" thing, what are examples of strings that need to be platform specific in this way?

Not sure if I see any other uses (apart for File Manager, and maybe Terminal), maybe references to mac specific keys (Option/Alt, Command/Meta), but theses are already hard-coded in the keyboard handing code and never change.

Other possible platform specific strings (referencing VSCode):

deleting: Recycle bin (Windows) vs Trash
permissions: Admin (Windows) vs sudo or Superuser
closing: quit (macOS) vs exit
Any tooltips that reference a ctrl/cmd or alt/option key and don't use the regular system.
external links that include platform, such as https://git-scm.com/download/win

I don't know how necessary any of these would be or if they need this system.
For ctrl/cmd we already just check OS::get_singleton()->has_feature("macos") (and web_macos and web_ios).

Looks like a overwork to me, atleast as of now where broader use cases aren't discovered


Large binary sizes

Hi,
I compiled the examples and I was surprised that each examples is approximately 16 M in size in release mode and 21M in debug mode.
After striping, I get 1.6M and 4.4M respectively  binary sizes.
That make the library practically unusable on constrained environments.
Is there a way to reduce the binaries sizes ? if no why ?
Thanks

I've no idea I'm afraid. Googling "Rust binary size" produces a lot of discussion about this, so the problem (and solution, if there is one) isn't specific to this library.

Note that this crate enables debuginfo in release mode, so you do need to strip that if you care about size. For the examples, the size of the code that comes from this crate is quite small (mostly less than 10k, but about 40k for the font example). So I don't think there's any problem with this crate.
Of the other crates, image (300k) and inflate (200k) are large contributors, so there may be saving possible there (eg disable image formats you don't need). The inflate size looks like poor optimization to me, it's all in one function (inflate::InflateStream::next_state).
There's also the base code from the std library. A sizable portion of this is due to jemalloc. This will be reduced once we can switch to using the system allocator.

I've just had a look at the gradients example. It's now 1.8mb in release mode, 1.1mb stripped. Cargo bloat output for the release build is shown below.
 Use -n N to show more.
50.7% 100.0% 919.0KiB           .text section size, the file size is 1.8MiB

Binary sizes with the settings shown above are now 10x smaller than those in the original report. If this is still too large then try the guide linked from the previous comment which explains how to build a smaller std.


add browser tests to gh actions.

Fixes #370

Added browser tests to GH Actions
Fixed two tests that were failing in browser tests. Failing due to fetch not being avail in karma environment.
** NOTE: a fetch polyfill may be a better option here, I just wanted to make sure current state was passing so it didn't block anything once added to gh actions.

Apologies. Accidentallyl opened this not as a draft. Pretty sure you all are now getting emails as I troubleshoot some browser test issues. Going to close and reopen as draft.


[ bug Report ] Issues with pushables and bridges in LOS refactor branch.

TombEngine version
Development Build
Tomb Editor version
Development Build
Describe the bug
Branch: sezz/los-refactor-from-modern-controls
Testing the branch, I spotted some issues, I'm making list to don't forget them and do a follow of them, the issues I noted were the next:

[x] Climbable Pushables getting stuck in dropping animation.
[x] When dropped over the quicksands, it gets teleported to the ceiling.
[x] Climbable pushables don't floating over water surface.
[x] The pushables gap with underwater ceiling is bigger than expected.
[x] When Pushables are released over trapdoors, they fall down through them.
[ ] Possibility to drop two object pushables on the same sector.
[x] When flip map the room from water to dry, pushables don't fall to ground.
[ ] When pushables (climbable and objects) are destroyed, they are keeping their bounding box collision and floor stopper flag.

Test Level:
https://drive.google.com/file/d/1v649rJ6UzvLTU3G827U0GSUg-6vsBqbD/view?usp=sharing (38.4 mb)
Recompiled version (16/11/2024)
https://drive.google.com/file/d/12knVml6-q-tOPLHDzp49laubTcduCzXG/view?usp=sharing

The two remaining issues, are present also in develop branch, I'll review them once the los branch gets completed to avoid potential conflicts.


Incorrect syntax highlighting for .properties files

Single quote characters hold no special meaning in .properties files, however, vscode highlighting tries to match a second quote even on different lines.
.properties files follow the syntax [key]=[value] where the value is simple text and can contain any character.
How to reproduce:

Create a new .properties file
Add a key-value pairs with random single quote as per the attached image

Can you please share a copy/pastable sample?


PL-400 Issues

Practice Lab – Validate lab environment
This should be Next and not Save

Lab 01 – Data Modeling | Exercise #2: Create Tables and Columns |  Task #5: Edit Status Reason Options | Step 3.  In class view, this is still "Entities" instead of Tables.

Same section, this is still "Fields" and not columns:

Step 11 as well:

Lab 02 – Model driven app |  Task #1: Edit Permit Form and View | Step 2
There needs to be steps of how to find the Permit Type column to drag and drop.
Lab 03 - Canvas App | Task #4: Add Inspection Details Screen |  Step 3.  This should be "Tree View" not "Three View".
Same section, step 5 the name and scheduled date already exist. Instructions need to read to add Status Reason and Comments:

Step 6 should read you will see an error message:

Lab 04 – Client Scripting |   Task #4: Test Event Handlers | Step 3
In two test runs, we consistently get the following with the on-load permit form (this is post-clear and refreshing):

Lab 05 – Power Apps Component Framework | Exercise #1: Create the PCF Control | Task #2: Setup Components Project | Step 4
A new command prompt needs to be opened before running the PAC commands:

Lab 05 – Power Apps Component Framework |  Exercise #2: Publish to Microsoft Dataverse |  Task #3: Debug
F12 returned the following errors, making this task incompletable:

Lab 06 – Plug-ins |  Exercise #1: Block New Permit Creation Plugin | Task #1: Create the plugin | Step 1
Suggestion:   Add a note of which version of Visual Studio is in reference.
Lab 06 – Plug-ins |  Exercise #1: Block New Permit Creation Plugin | Task #1: Create the plugin | Step 5
Screenshot   does not display the the 'using' statements below the class. 'using'   statements should be included at the start of the program.

Lab 07 – Azure Functions |  Task #2: Create Application User and Security Role | Step 4
Full Name column is absent.
Exercise #2: Create Azure Function for Inspection Routing |  Task #1: Create the Function |  Step 2
The   below output is made, contradictory to the one present in the instructional   screenshot.

Exercise #2: Create Azure Function for Inspection Routing |  Task #1: Create the Function |  Step 3 (9)
Add a   note at step 2(4) not to stop debugging else the below error will be present.

Lab 9:
Suggestion to put all code blocks in a type/text |  code block. Example:
   ```
   private static Task<CRMGetListResult<ExpandoObject>> GetUsers(CRMWebAPI api)
    {
    var users = api.GetList<ExpandoObject>("systemusers");
    return users;
    }
   ```

Lab 9 | Exercise #3: Publish and Test | Task #1: Publish to Azure | Step 1

Due to   the error above, publishing seemed unaccomplishable Lab 07 was finished   prematurely and Lab 08 was continued.
Lab 08 – Publishing Events Externally | Exercise #1: Create an Azure Function |  Task #1: Create Azure Function App | Step 1 (4)
Creating   a new resource group requires a name.

Exercise #2: Configure Web Hook |  Task #2: Create an Azure Function | Step 2
Suggestion:
Instructions   to observe past logs should be included. Instructions unclear.
Lab 09 – Custom Connector |  Exercise #3 Test Connector | Task #2: Test on Flow |  Step 4
Connection   must be recreated before step 4 can continue;

Lab 10 – Application Lifecycle Management |  Exercise #3: Test the Pipeline |  Task #1: Run the Pipeline | Step 1 (12)
Run did   not execute successfully - 'Power Platform Export Solution' task failed to   connect to environment. See error below;

Task #3: Run Build Pipeline |  Step 2 (6)  Jobs did not succeed due to above error.
Step 3(3)  Due to earlier error reported

Suggestion/Ask: For the labs that have a majority of VS code entries, solution files be provided. That way if the end-user needs to compare what they may have done wrong, they can cross compare.

Thank you for reporting this. We are releasing an update for this lab in the next couple of weeks.

Thank you again for the feedback, we just updated the lab and these issues should be resolved. Please continue to support us by reporting any issues you may find.


Gerneated Tests are empty when run on a fresh project.

When i delete the pythagora_tests folder first and then generate the tests, it always generates me an almost empty unit-test file with only  the lines

` ` ` ` javascript

in it.
After i leave the existing folder and just delete the unit-test-file, it will run fine again.

Typo in the title. Mus say: "Generated"

Update: Now i also get it, when the pythagora_tests folder already exists, while expanding tests with
npm run clean && npx pythagora --expand-unit-tests --force --path matchesValue.test.ts
The result is then:
Content of my handwritten tests

//Expanded tests using Pythagora:
```javascript

Seems a bit non-deterministic here.


Website down

http://mc-stan.org is down

Thanks. I'm looking into it.
On Thu, Nov 24, 2016 at 10:34 AM, Andrés Gottlieb<EMAIL_ADDRESS>wrote:

http://mc-stan.org is down
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/issues/2130, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F9bYhR2q89YmS5f_dLgEax6T2z3dks5rBa6LgaJpZM4K7xXr
.

Looks like it's up again. Thanks.
On Thu, Nov 24, 2016 at 11:37 AM, Daniel Lee<EMAIL_ADDRESS>wrote:

Thanks. I'm looking into it.
On Thu, Nov 24, 2016 at 10:34 AM, Andrés Gottlieb <
<EMAIL_ADDRESS>wrote:

http://mc-stan.org is down
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/stan/issues/2130, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F9bYhR2q89YmS5f_dLgEax6T2z3dks5rBa6LgaJpZM4K7xXr
.


Library versions should be 3 digits instead of 4

Currently the version format of the mock env is 4 digits even though in-game it is 3 digits.

Done with https://github.com/ayecue/greybel-gh-mock-intrinsics/commit/3585bfd34cf4102696885afc2d9bcf6c6770e211


Also use React.PropTypes.func in lib/

This is a follow-on to #54 -- we also need to change the type specification inside lib/

Sorry to keep bugging you, but this should have been part of my previous PR and it too is a very small change. Would you mind merging it?

(Bump)

I'll buy you a beer if you merge this!1
1 Offer only valid in San Francisco

Looks like this got fixed at some point, so I'll close


desktop_surface_at: Set a "surface" argument in case of fullscreen surface

Rootston is being moved here:
https://github.com/swaywm/rootston


Automated cherry pick of #888: - set disk storage_id not required - can't do syncstatus on guest has active tasks in last one hour - fix guestdisk index set wrong number on guest attach disk

Cherry pick of #888 on release/2.8.0.
#888: - set disk storage_id not required - can't do syncstatus on guest has active tasks in last one hour - fix guestdisk index set wrong number on guest attach disk

/lgtm
/approve


Provide binaries

I'm not fully sure if this is possible, but if we could get a pre-compiled version to download on top of the sources that would greatly help.
I now have to download 5gb of Xcode in order to run the install script. Depending on your bandwidth this can means a lot of time.

+1

I've updated the repo to include a binary. It was built on OS X 10.11, so let me know if it works / doesn't work for you. I'll gladly provide pre-build plugins for people who don't have Xcode, but if people are reading this and they do have Xcode, I would recommend building it on your own machine just in case.
You can use the pre-built plugin by copying the PlugIns directory into the AVRCPAgent directory
cp -r ./prebuilt/PlugIns ./AVRCPAgent/

Then running the install
./install.sh install

Note I separated build and install steps in the install.sh script, so if you're not using the binary, you need to run "./install.sh build" first.
Sorry it took so long, I've been doing school / work and had to put GitHub aside for a little. I'm going to keep this issue open in case the binary doesn't work on machines other than 10.11 for whatever reason so I can try to tweak it.


Release 0.5.0

@rultor release it, tag is 0.5.0.

@rultor release it, tag is 0.5.0.

@rafamizes OK, I will release it now. Please check the progress here

@rultor release it, tag is 0.5.0.

@rafamizes Done! FYI, the full log is here (took me 2min)


[INFRA-351] enable ML2/OVN and DVR by default

Not necessary, it will get merged from zed to 2023.1


Clean up duplicated client code

A easy fix to clean up client.client
Fixes #127
Except Attach(), it will be fixed by its own PR.

LGTM


Log2Timeline elsatic search too recent!!

I downloaded the latest version of SIFT-Workstation which is built on Ubuntu 16.04.  Installation to a VM was fine.
However, when I tried to run the log2timeline command -
log2timeline.py plaso.dump diskimage.e01
I get an error that tells me:
[FAILURE]  elasticsearch version 6.2.0 is to recent, 5,5,1 or earlier required
I am working with an .E01 image taken from a laptop that was running Windows 10
Any ideas would be helpful.

Try downgrading elasticsearch

I have tried - sudo apt-get remove elasticsearch -  and to ensure it was gone, I ran it again.
Installed 5.5.1 using - sudo apt-get install elasticsearch=5.5.1
Still receiving the same "elasticsearch version is too recent" error.  Removed elastic search and tried to run Log2Timeline without elastic search installed -- and I still get the same error message.


[Water Float Decoration] They can be placed in admin claims such as spawn

Describe the bug
I logged in to see a water float randomly placed in spawn. I went and bought one of my own and respecting claims was also able to place them in spawn. I tried all of the other decorations from warp market and the water floats are the only ones that work this way.
To Reproduce
Steps to reproduce the behavior:

Go to warp market
Get yourself a water float of any color
Go to an admin claimed area and place away

Expected behavior
Items should not be able to be placed anywhere from any player in admin claims
Username: _Peyton_7
Server name: FunPolice (all applicable):

This also applies for item frames and paintings in the end but I believe i made a separate ticket for that some time ago

I think this is likely a missing GD flag, @chefburne or @WisconsinWinters

Duplicate of https://github.com/NebulaMC-GG/Bugs-and-Issues/issues/2288


Running azd init on an existing project should allow me to use my existing Bicep files

Output from azd version
azd version 1.5.0 (commit 012ae734904e0c376ce5074605a6d0d3f05789ee)
Describe the bug
When attempting to "azd-ify" an existing app, consisting of Python Azure Function code and Bicep, I want AZD to set up the necessary AZD configuration (azure.yaml and AZD environment variables). Currently AZD is taking me through a generation flow to seemingly create new Bicep files.  I'd like to use the existing Bicep files in the solution directory.
To Reproduce
Assume a directory structure as follows:
.devcontainer/
customskills/
  - functionA/
  - functionB/
  - host.json
  - requirements.txt
infra/
  - modules/
  - main.bicep

Run the azd init command to "azd-ify" an existing app.  AZD correctly discovers Python in the customskills folder.  However, it assumes that the app should be hosted in Azure Container Apps and prompts to "generate the files necessary to host your app on Azure using Azure Container Apps".  I am presented with three options:

Confirm and continue initializing my app
Remove a detected service
Add an undetected service

I don't want any of the above options, as I already have Bicep files to host my app on Azure Functions.
Expected behavior
Allow me to use my existing Bicep files.  No additional Bicep files need to be created.
Environment
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.23545
Additional context

@weikanglim , is this already supported somehow?  or would it be a new feature for easy-init?

@mcollier For azdevifying scenarios, have you tried "Select a template -> Minimal"? This will provide the minimal azure.yaml, and gives you a main.bicep.azd with some hints on how to perform azd's resource tagging.
The "initialize from app code" currently assumes "app code only", we can likely bridge the gap over time, but there's definitely more considerations. FYI @savannahostrowski

@weikanglim It didn't occur to me to pursue selecting a minimal template, as I already have the Bicep files (and in an infra folder already, thus aligning with AZD's directory structure).
I was following the doc at Make your project compatible with Azure Developer CLI and the "Use code in the current directory" approach.  I assumed that AZD would create the azure.yaml and give me an option to not generate the Bicep since I already had an AZD-compatible directory structure (an existing infra folder with existing .bicep files).
In this case, I'd like azd init to generate the azure.yaml, set up the AZD environment, and get the minimum required environment variables in place.


Email notification for low stock

This Pull Request

facilitates email notifications when a part's stock quantity falls below the minimum quantity.

closes #2093

@rocheparadox @SchrodingersGat I think this is ready

In addition to a post_save hook we'll also need a delete hook (on the StockItem model). If a stock item is deleted, the available stock for the parent Part is also reduced.
This is another reason to add the check_low_stock method to the Part model - it can be then reused in the multiple hooks.

@rocheparadox this is looking pretty good now! Can you also please add a post_delete hook for the StockItem model?

@SchrodingersGat I thought of doing adding post_delete hook but was quite unsure of what to do inside the hook function. Can you explain a lil bit?

I would just duplicate the code that you have here, but into the "delete" hook:

Now I get it. I was reading the parent Part as parent StockItem the whole time :face_with_head_bandage: and had no idea what that meant. My bad.

@SchrodingersGat , I have added the post_delete hook. Kindly merge the changes.

Looks good @rocheparadox :)


NTR: data items - sampling location

Sampling Location Terms

ROBOT table new term requests (basic template, data item specific template unavailable at this time)
Terms with tan labels have already undergone an initial OBI review but need final review and to be entered into OBI.
GenEpiO ID (temporary) and Curation Notes annotations are for curation work and should be removed prior to ROBOT integration.

ROBOT table URL ("sampling-location" tab): https://docs.google.com/spreadsheets/d/1SiVgFDy9jOoFIhywvLjYLMBLqJsZ0B9An9170RYpQRM/edit#gid=2066156117

ontology ID
label

OBI:0002868
sampling location room

OBI:0002869
sampling location surface material

OBI:0002870
sampling location building level

OBI:0002871
sampling location condition

OBI:0002872
sampling location average daily occupancy

OBI:0002873
sampling location frequency of cleaning

@ddooley

Discussed on call.  OBI is shy of creating more data items as shadow hierarchies.  Prefer to have models of material references like building locations/conditions described generally (ENVO?).
@zhengj2007 will add some content about how "sample/specimen location" currently is in OBO.

@griffie could you provide "example of usage" annotations for these terms?

A couple of OBO ontologies have defined the sample collection location. In FLU, it is data about a collection location that has several subClasses, such as collection city, collection longitude GPS, collection location name, and collection state etc. In VEuPathDB ontology, it is defined as a site, location of specimen collection.

@zhengj2007 do you want "location of specimen collection" moved into OBI?
Does anyone have an opinion about how it should be named?  "specimen collection location"?
Also as I understand it, ENVO is moving away from having stuff under "site", since there is no axiomatization that seems to be useful beyond how material entities are defined anyways (i.e. both sites and material entities have fiat boundaries; beside that are there any features that distinguish the categories found under each? - this is an argument that Chris Mungall put forward).  So is it ok to have "specimen collection location" under ME?


No warnings when there is no find match

#59267
Search for something which doesn't exist, there is no indicator for "No results".

Duplicate of #28768


Release 2.0.0-preview2

When upgrading a Core 2 Preview 1 application to Core 2 Preview 2 we started experiencing this exception using the PG lib. This occurs on both Windows and Linux.
Message:

System.TypeLoadException: System.TypeLoadException: Could not load type 'Microsoft.EntityFrameworkCore.Metadata.IRelationalAnnotationProvider' from assembly 'Microsoft.EntityFrameworkCore.Relational, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'

StackTrace:
Microsoft.Extensions.DependencyInjection.NpgsqlEntityFrameworkServicesBuilderExtensions.AddEntityFrameworkNpgsql(IServiceCollection serviceCollection)
   at Microsoft.EntityFrameworkCore.Infrastructure.Internal.NpgsqlOptionsExtension.ApplyServices(IServiceCollection services)
   at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.ApplyServices(IDbContextOptions options, ServiceCollection services)
   at Microsoft.EntityFrameworkCore.Internal.ServiceProviderCache.<>c__DisplayClass4_0.<GetOrAdd>b__2(Int64 k)
   at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
   at Microsoft.EntityFrameworkCore.DbContext.InitializeServices()
   at Microsoft.EntityFrameworkCore.DbContext.get_InternalServiceProvider()
   at Microsoft.EntityFrameworkCore.DbContext.get_DbContextDependencies()
   at Microsoft.EntityFrameworkCore.DbContext.EntryWithoutDetectChanges[TEntity](TEntity entity)
   at Microsoft.EntityFrameworkCore.DbContext.SetEntityState[TEntity](TEntity entity, EntityState entityState)
...

Npgsql EF Core version 2.0.0-preview2 hasn't been released yet, and it's not possible to use preview1 with EF Core preview2 (they introduced significant API changes). You'll have to wait until a 2.0.0-preview2 version of Npgsql.EntityFrameworkCore.PostgreSQL released (probably very soon).
I'll post back here once this is released.

It is already released

@MathiasKowoll no, it's not. EF Core 2.0.0-preview2 has been released, but not the Npgsql provider. It should be out in the next hour or two.

2.0.0-preview2 has been pushed to nuget, please let me know of any issues you come across.

@roji I menat that it was release about EF ;) will test asap

I get this error while creating migrations:

@SleepyDeb  I fix that error upgrading npgsql to <IP_ADDRESS>

@SleepyDeb for errors about NpgsqlDesignTimeServices, please use version 2.0.0-preview2-final where it is fixed.

Thank you @roji for the work. All our unit tests are passing on this library on preview 2.


Added additional methods to both, Chip and Line, as well as adding jsdoc comments to the .d.ts file

awesome!


Respect BUILDER_IMAGE argument when provided

Signed-off-by: Moti Asayag<EMAIL_ADDRESS>rh-pre-commit.version: 2.3.1
rh-pre-commit.check-secrets: ENABLED

it is my bad I didn't document that. The usage of the argument with no value is effectively unsetting it, and that is why the build-image make target work with the default builder image from the docker file:
FROM ${BUILDER_IMAGE:-quay.io/kiegroup/kogito-swf-builder:9.99.1.CR1} AS builder

This is important because with that we can use the $workflowid/argfile.conf for both upstream build (make build-image) and konflux build (which uses only the argfile.conf)

So as long as the BUILDER_IMAGE is "" by default I'm we are OK.


Sizes and animation not working

Just dropped the css and js files in my Bootstrap 3 projects, two things are weird:

The switch works, but doesn't animate, just switches.

The 'switch' is stretching to the height of it's container. When I inspect the div your js creates, it's got inline width and height so I can't target it with css. I've got the mini directive on my checkbox but it's being totally ignored.

Any ideas?

which browser are you using. recent update added width/height as an option

hey @minhur I was using Safari 8. It was just a vanilla install of the library and then the sizes didn't change. I just tried the mini flag, didn't mess around with width/height...?
I might try and recreate it if I get some time. I ended up going with another library just to get it implemented quickly but if you can't recreate it I'll give it another go.


DOM XSS does not work with Firefox version 40 or above

I found that "A3 Cross Site Scripting DOM Based" does not work with Firefox version 40 or above.
https://github.com/OWASP/railsgoat/wiki/A3-Cross-Site-Scripting-DOM-Based#dom-based-cross-site-scripting-attack
According to this Firefox's specification change, location.hash returns percent-encoded value.
https://www.fxsitecompat.com/en-CA/docs/2015/urlutils-hash-no-longer-decodes-fragment/

Firefox 39.0.3

> location.hash
"#test=<script>alert(1)</script>"

Firefox 40.0

> location.hash
"#test=%3Cscript%3Ealert(1)%3C/script%3E"

How about to add decodeURIComponent to app/views/sessions/new.html.erb ?
       var hashParam = location.hash.split("#")[1];
       var paramName = hashParam.split('=')[0];
       var paramValue = hashParam.split('=')[1];
+      paramValue = decodeURIComponent( paramValue );
       document.write("<OPTION value=3>" + paramValue + "</OPTION>");
     } catch(err) {
     }

Resolved using the method you demonstrated @jx6f , thank you. Found in commit fafe94b571fcb064a719ccdb0a0412bb2493bd0c


No way to add Anchor outofthebox

Missing feature in the editor. A CMS needs anchor's. (i don't know why, but customers need them for newsletter linking etc)

Hi @maartenkling - there's an existing ticket for this, at #1049.


Cannot read properties of undefined (reading '_parse')

Hey, I've come across this issue in my project while composing schemas from imported zod objects/enums.Here is the code:
CountryCode.ts
import { z } from 'zod';

const countryCode = z.enum(['IE', 'GB']);

type CountryCode = z.infer<typeof countryCode>;

const countrySchema = z.object({
  alpha2: z.string(),
  alpha3: z.string(),
  code: countryCode,
  name: z.string(),
  region: z.string(),
  regionCode: z.number(),
  subRegion: z.string(),
  subRegionCode: z.number(),
});

type Country = z.infer<typeof countrySchema>;

export { countryCode, countrySchema };
export type { Country, CountryCode };

CurrencyCode.ts
import { z } from 'zod';

const currencyCode = z.enum(['EUR', 'GBP']);

type CurrencyCode = z.infer<typeof currencyCode>;

const currencySchema = z.object({
    code: currencyCode,
    name: z.string(),
    minorUnit: z.number(),
  });

  type Currency = z.infer<typeof currencySchema>;

export { currencyCode, currencySchema };
export type { CurrencyCode, Currency };

If i import the above like so:
invitePerson.ts
import { z } from 'zod';
import { countryCode, currencyCode } from '../../api';

const invitePersonSchema = z.object({
  startDate: z.date().optional(),
  firstName: z.string().min(1, 'First name is required'),
  lastName: z.string().min(1, 'Last name is required'),
  role: z.string().optional(),
  dateOfBirth: z.date().optional(),
  email: z.string().email('Email is required'),
  residentialAddress: z.object({
    addressLine1: z.string().optional(),
    addressLine2: z.string().optional(),
    addressLine3: z.string().optional(),
    city: z.string().optional(),
    countryCode: countryCode,
    postalCode: z.string().optional(),
  }),
  annualSalary: z
    .string()
    .min(1, 'Annual salary is required')
    .transform(value => parseInt(value, 10)),
  salaryCurrency: currencyCode,
  taxId: z.string().optional(),
});

type InvitePersonData = z.infer<typeof invitePersonSchema>;

export { invitePersonSchema };
export type { InvitePersonData };

I get the error in the title. However, if I define the enums directly in the invitePersonSchema and don't import, there is no error. I would have expected this to be allowed, so please forgive me if I am misusing the library in some way.
Note: this was already discussed here, but the last comment provides a reproducible example which I have copied below, just in case it helps: https://github.com/colinhacks/zod/issues/643

I ran into the same error message and found this issue. Now while my problem is likely a different another one, I thought sharing this might still help others ending up here.
Essentially what I was doing is exporting a schema from one file, using it in another one to compose another schema, and then importing that composed schema back into the first file. While there isn't a cyclic dependency per se, it causes the mentioned error at runtime.
See this CodeSandbox for an example: https://codesandbox.io/s/patient-butterfly-hsg3q?file=/src/index.ts The message isn't as descriptive as in my local (larger) project, but removing this exact kind of import solved it for me. (Maybe this is generally "wrong" in terms of my tsconfig or simply unsupported by zod and I don't know it, but I would intuitively expect it to work 🙈.)

I seem to be running into this issue as well while migrating from jest to vitest and it seems to have to do with a cjs vs esm.
It worked fine with cjs but seems to break with vitest's esm-first approach. Not sure if this info is helpful or not, will keep looking into this.

Hmmm, I've been using tsup to manage packages in a monorepo and my schemas package is esm.

I just discovered zod recently and was about to migrate our project to it, but apparently I'm running into this issue too.
The Enum is in a different file (where it belongs to) and I get this cryptic error message ("TypeError: Cannot read properties of undefined (reading '_parseSync')"). If I temporarly put the enums inline in the same file where the zod object is created, everything works.

Same issue, receiving TypeError: Cannot read properties of undefined (reading '_parse') while having
import { FooDomain } from '../../types/foo';

foo.ts:
const FooDomain = z.string().refine(
    (arg) => isValidFooDomain(arg),
    (arg) => ({ message: `'${arg}' is not a valid foo domain` }),
);

so it does not seem to be purely related to Zod enums

I solved it by modifying some imported files: splitting them or joining other parts together. Apparently this is some kind of circular dependency issue - even though the rest of the code did just work fine all the time. But after restructuring everything worked. (Note that I also had to seperate stuff which actually wasn't even called but webpack did combine it into a bundle and therefore caused that issue)

The Enum is in a different file (where it belongs to) and I get this cryptic error message ("TypeError: Cannot read properties of undefined (reading '_parseSync')"). If I temporarly put the enums inline in the same file where the zod object is created, everything works.

I had a Zod schema defined in a file using schemas defined in another. I was having the about the same issue (Cannot read properties of undefined (reading '_asyncParse').
Moving the schemas in the same file fixed it.

Had the same issue, turned out to be a circular dependency between two files

We got the same issue today, couldn't seem to find any circular dependency or anything like that. We were calling safeParse on a zod schema within a typescript type guard. The zod schema have other schemas imported from other places, but no circularity of any kind what we could see. We are also using vitest. So esm (module type stuff) could maybe be a factor. Didn't have time to get to the bottom of it so replaced the safeParse call with a simpler check in the code for now. But it's a real issue.

Facing the same issue and this is a clear reproducible example without any circular dependency:
https://codesandbox.io/s/patient-butterfly-hsg3q?file=/src/index.ts

this issue is not really related to zod but to the way circular imports work. when you have a circular dependency between two files, the second one to be loaded will get "undefined" for all the objects exported by the first one.
for example, if you have these two files:
// a.ts
import { b } from "./b";
export const a = {};
console.log("in a.ts:", "a", a, "b", b);

// b.ts
import { a } from "./a";
export const b = {};
console.log("in b.ts:", "a", a, "b", b);

when running a.ts, you get this output:
$ ts-node src/a.ts
in b.ts: a undefined b {}
in a.ts: a {} b {}

note that a is undefined when logging from file b.ts. this happens regardless of whether there is a circular dependency between the objects a and b themselves.
in your example, index.ts imports otherFile.ts which imports index.ts. the value Severity is undefined when creating the schema Issue, which then fails when calling parse.

i'd say the standard trick for solving the issue is to just avoid the circular imports (in your case, that would be moving Severity into its own file which is imported by the other two).
or else you can defer the execution of the code that needs both files to be loaded completely by returning a factory function instead of the object itself. e.g.:
// a.ts
import { b, log } from "./b";
export const a = {};
log();
console.log("in a.ts:", "a", a, "b", b)

// b.ts
import { a } from "./a";
export const b = {};
export const log = () => console.log("in b.ts:", "a", a, "b", b);

which then gives you this output:
$ ts-node src/a.ts
in b.ts: a {} b {}
in a.ts: a {} b {}

@cromaniuc

Facing the same issue and this is a clear reproducible example without any circular dependency: https://codesandbox.io/s/patient-butterfly-hsg3q?file=/src/index.ts

// otherFile.ts
import { Severity } from "./index";

// index.ts
import { Issue as IssueImported } from "./otherFile";

That's circular dependency 😁

I am encountering the same problem. I have two projects in a repository. One containing the zod schemas (models), and one containng my business code (backend). Both projects are (according to tsc and madge) free of circular dependencies. Nevertheless I still get the aforementionted error when running the backend.

bite the bullet --- stick all models in a single file


Installation issue on Debian 11 with php8.0

Hi,
I want to add this plugin to my Sylius installation and have error like this:
`php bin/console sylius:theme:assets:install --symlink
Trying to install assets as symbolic links.
In Filesystem.php line 41:
Failed to copy "/home/sylius/acme/vendor/api-platform/core/src/Bridge/Symfony/Bundle/Resources/public/es6-promis
e/es6-promise.auto.min.js" because file does not exist.
`
Can I ask for help?

Not related to our plugin, looks like OS problem or entire Sylius/Symfony.


Flux v2.2.0: Update CRDs and component versions

What this PR does / why we need it:
Updates the CRDs to include the latest specs, updates components to latest versions
Special notes for your reviewer:
Allows the helm-chart to be used for proper install/function of the latest component versions
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] helm-docs are updated
[x] Helm chart is tested
[x] Update artifacthub.io/changes in Chart.yaml
[x] Run make reviewable

Yeah, i was about to ask about bumping those since the release date is expected to be today right? :)

Yeap couple of hours from now

@rsafonseca please bump the app version and the CLI tag, we've released v2.2.0

all set @stefanprodan 👍

Please bump the other charts as well

Done, it was actually in 2 places :)

argh, the liniting job is tying all the charts together so it's failing for the charts i didn't update :(

Please bump the chart version for flux2-notification and flux2-sync

argh, the liniting job is tying all the charts together so it's failing for the charts i didn't update :(

There is an update, the app version so chart version needs a bump too

Yeah, just noticed that as I typed it... the Makefile target did that for me hehe.. i added the notification.toolkit.fluxcd.io apiversion bump to flux2-notification chart as a bonus :)

It should be all green now :)


App should use pagination when first loading

Currently, app loads ALL of the Database info when first loaded.
App needs to load 20 posts at a time starting at the most recent.

Pagination function working on server side.
Next issue is integrating it with frontside in React


editor.fontSize has no effect

No matter what I set editor.fontSize to in my config.cson, it does not change the font size in the editor at all. I can sit here and hit the increase and decrease font hot keys, with my config.cson file open, and watch the value go up and down as Atom reloads the file as it changes. And yet, my font never changes.

The setting simply doesn't do anything. Ever. Starting atom with atom --safe makes no deference.
$ atom --version
0.200.0

Can you reproduce this if you try changing the font size in the settings UI? Can you paste the contents of your config.cson?

Also please paste in the contents of your styles.less.

That was it. Somehow a font-size property got in there for the selector atom-text-editor. Ignore me!


GitHub icon add

@MitulSonagara
I have added github icon successfully
Kindly check it out
https://github.com/user-attachments/assets/70896dc5-9ef0-480a-88c2-a5055a5f4fb5

@AswaniBolisetti
Please follow the PR template for creating the PR and mention the issue number so that it will automatically close that issue


Detecting ` and not removing '

If you put this en your code "hello!" and you try and put this "`${" it doesnt replace the " with `

there's a setting for that - something like convert within backticks

Oh, i dont see this config can u provide more info pls


General inconsistencies and typos

[ ] Landwarhkanal -> Landwehrkanal
[ ] Gunther -> Günther
[ ] Schroder -> Schröder
[ ] Hanover -> Hannover
[ ] Wendell -> Weddell
[ ] String ID 21946 looks a bit weird in-game

There is actually a lot of more NPC names with issues I saw recently. A bit too much to just list them separately. And all "Kruger" must be set to "Krüger" if one wants to make it right. Some capship names are also inconsistent, like "Koeln", "Köln" which is just the same.


FIX Project Compile and Update

*Add empty key.properties file and create debug flavors so project can be easily run.
*Update Android libraries.

Any updates on this PR?

Please update or this app no longer builds due to Flutter updates. Thanks!


⚠ Bofrost.be has degraded performance

In 1cc41e5, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 984 ms

Resolved: Bofrost.be performance has improved in c34704c after 9 minutes.


Ability to Poll for Messages in Arbitrary Database Tables

This is 100% about being able to integrate with external, legacy systems and allow the external systems to pump message to Wolverine w/ their own outbox.
Thoughts

Allow for an arbitrary database table structure, but part of defining it will be specifying the primary key type and field
build it into MessageDatabase<T> so that this can move messages out of the outbox tables and into Wolverine's inbox tables at one bite
Use advisory locks so only one node at a time is allowed to fetch records. That sidesteps a need -- hopefully -- to get too fancy with database SQL on the polling
Pretty well say that the mechanism is to tie an external table to a local, durable queue. Have a polling mechanism pull up to a configurable number of messages at a time into the local queue on the node
Besides the table structure, plug a "ADO reader to Envelope" mapper

New Questions

Can we assume the external message tables are written to the same database as the default message storage database that Wolverine is already using for envelope storage?
Is there any multi-tenancy requirements here? (yikes)
Should we try to support causation & correlation tracking as an opt in, or leave that for a follow up if anyone wants it later?
Right now I'm assuming that the incoming endpoints would always be Durable. Wondering if anyone would want fire and forget instead


Remove version: Rainmeter.Rainmeter version 4.5.3

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/rainmeter/rainmeter/releases/download/v<IP_ADDRESS>46/Rainmeter-4.5.3.exe
OK
(Automated message - build 917)


feat: store uses multiple peers

--WIP--
Problem
https://github.com/waku-org/js-waku/issues/1685
Solution
Store uses multiple peers to query
Notes

Resolves https://github.com/waku-org/js-waku/issues/1685
Related to https://github.com/waku-org/pm/issues/143

Contribution checklist:

[ ] covered by unit tests;
[ ] covered by e2e test;
[ ] add ! in title if breaks public API;

deprioritised for now


make manifest.mime part of the public API

This moves manifest._.mime to manifest.mime, so that adapters can use it. This will enable #4276 to serve static assets without pulling in a mime library
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpx changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

Changed it to mimeTypes


fix: svc monitor port

Description
Made a mistake in my previous PR, the port should not be a number but the name of the http port in the svc http.
So apologies about the extra PR, but better this than to leave something broken right.

thanks @WDaan !!! ♥


687 sudo travis

Fixes #687

[?] npm run test succeeds.
[x] npm run lint succeeds.
[x] Appropriate changes to README are included in PR.

@grant any reason why os like MacOS and Windows are not covered by Google (beside saving quotas?)

@grant any reason why os like MacOS and Windows are not covered by Google (beside saving quotas?)

Only because of quotas.

Please don't have so many commits in PRs. To reduce commits, you need to:

git checkout master
git remote add upstream git@github.com:google/clasp.git
git fetch upstream
git merge upstream/master

Before your commits.


How to use the older (V4) version?

Hi,
I've been using your model to detect vocals in audio tracks. It was working pretty fine and the choice of the window was a cool feature that allowed me to optimize the detection. Now with the newer version I see a lot of the activity is not detected, and I would revert back to the older model. Is there a way to do this? I tried loading the older model from the hub but it seems it's not available anymore.
By loading it in this way:
USE_ONNX = False # change this to True if you want to test onnx model
if USE_ONNX:
!pip install -q onnxruntime
model, utils = torch.hub.load(repo_or_dir='snakers4/silero-vad:v4.0',
model='silero_vad',
force_reload=True,
onnx=USE_ONNX)
(get_speech_timestamps,
save_audio,
read_audio,
VADIterator,
collect_chunks) = utils
I get this error:
~/.cache/torch/hub/helloWorld199_silero-vadv4_master/hubconf.py in
2 import torch
3 import json
----> 4 from utils_vad import (init_jit_model,
5                        get_speech_timestamps,
6                        get_number_ts,
ImportError: cannot import name 'get_number_ts' from 'utils_vad' (/root/.cache/torch/hub/snakers4_silero-vad_master/utils_vad.py)
I'm don't really know how torch hub works, but I would like to know how to resolve this versions conflict, and use the v4 one,
Thank you!

https://github.com/snakers4/silero-vad/issues/474
will be fixed here
we know about the problem

the choice of the window was a cool feature that allowed me to optimize the detection

turns out some people were passing the whole instead of a chunk
in any case with the new version we changed some internals in the model
and audio chunk size choice became pointless since the results now hardly depend on it


Update homepage in gemspec

Appears development is being done and released tagged under the rails organization now.

Thanks for the quick merge!


Virtual Scroll error - "Cannot read property 'left' of undefined"

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x ] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
Current behavior:
I'm doing a search on an item array that is displayed in a virtual scroll, so the array is changing a lot. Then and now the app crashes with error "Cannot read property 'left' of undefined". See the full error stack below.
Related Error:
Uncaught TypeError: Cannot read property 'left' of undefined
    at writeToNodes (virtual-util.js:344)
    at VirtualScroll._stepDOMWrite (virtual-scroll.js:543)
    at virtual-scroll.js:500
    at dispatch (dom-controller.js:139)
    at DomController._flush (dom-controller.js:108)
    at rafCallback (dom-controller.js:101)

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (C:\Users\ADMIN\AppData\Roaming\nvm\v8.9.0\node_modules)

    @ionic/cli-utils  : 1.19.1
    ionic (Ionic CLI) : 3.19.1

global packages:

    cordova (Cordova CLI) : not installed

local packages:

    @ionic/app-scripts : 3.1.6
    Cordova Platforms  : android 6.3.0
    Ionic Framework    : ionic-angular 3.9.2

System:

    Android SDK Tools : 25.2.5
    Node              : v8.9.0
    npm               : 5.5.1
    OS                : Windows 10

Environment Variables:

    ANDROID_HOME : C:\Users\ADMIN\AppData\Local\Android\Sdk

Misc:

    backend : legacy

Same error here. My template is as follows:
<ion-searchbar autocomplete="off" autocorrect="off" spellcheck="false" animated="true"
  [(ngModel)]="searchInput"
></ion-searchbar>

<ion-item-group
    [virtualScroll]="configurations | filterBy:['name','application.name']:searchInput"
    [headerFn]="headerText" approxItemHeight="69px"
  >

If typing in the search box quickly (like you would type text normally), the error will appear. Only way is to type slowly...

@mebibou have you tried a debounce function as a temporary solution, a la lodash.debounce? And post the relevant TS file?

@jayands actually there is a debounce on the ionInput event, so doing this worked:
<ion-searchbar autocomplete="off" autocorrect="off" spellcheck="false" animated="true"
  [(ngModel)]="searchInput" (ionInput)="searchValue = searchInput"
></ion-searchbar>

<ion-list [virtualScroll]="configurations | filterBy:['name','application.name']:searchValue">

This is a good solution when using ion-searchbar, and yes debouncing is the workaround