Update Brazil soybeans notebook link in main README

Moved in https://github.com/gro-intelligence/api-client/pull/93 into its own directory. Expect to see it reorganized back up into the main crop_models folder in the future, but as a more immediate fix, point this link at the Brazil soybeans directory

As discussed, I don't think this is the reorganization we want. We should not force requirements on models that do not need them. Brazil TRS model does not need geopandas and we shouldn't make users think it's a requirement, since windows users would then also need anaconda to run it.
If we want to have a single requirements doc for crop models, that's fine, but then Brazil TRS shouldn't be a crop model. Let's bring it up to it's own folder.

ok updated and tested both examples

As discussed, I don't think this is the reorganization we want. We should not force requirements on models that do not need them. Brazil TRS model does not need geopandas and we shouldn't make users think it's a requirement, since windows users would then also need anaconda to run it.
If we want to have a single requirements doc for crop models, that's fine, but then Brazil TRS shouldn't be a crop model. Let's bring it up to it's own folder.

Yup... turns out the only diff is seaborn which is a simple viz package and statsmodel where we use one regression model which overlaps with sklearn. Neither one is particularly onerous but we can clean that up and reduce the deps a bit separately.

separately

As discussed, I don't think this is the reorganization we want. We should not force requirements on models that do not need them. Brazil TRS model does not need geopandas and we shouldn't make users think it's a requirement, since windows users would then also need anaconda to run it.
If we want to have a single requirements doc for crop models, that's fine, but then Brazil TRS shouldn't be a crop model. Let's bring it up to it's own folder.

Yup... turns out the only diff is seaborn which is a simple viz package and statsmodel where we use one regression model which overlaps with sklearn. Neither one is particularly onerous but we can clean that up and reduce the deps a bit separately.

We tested conda install geopandas from scratch on  windows and it worked.  As discussed, I have changed the main readme to say anaconda is recommended for windows.
overall, we don't want to overwhelm the novice user with too many ifs in the readmes, we just want to pick the most pain free most general installation and recommend that. ( ditto for pip install vs git clone for example).

separately

As discussed, I don't think this is the reorganization we want. We should not force requirements on models that do not need them. Brazil TRS model does not need geopandas and we shouldn't make users think it's a requirement, since windows users would then also need anaconda to run it.
If we want to have a single requirements doc for crop models, that's fine, but then Brazil TRS shouldn't be a crop model. Let's bring it up to it's own folder.

Yup... turns out the only diff is seaborn which is a simple viz package and statsmodel where we use one regression model which overlaps with sklearn. Neither one is particularly onerous but we can clean that up and reduce the deps a bit separately.

We tested conda install geopandas from scratch on windows and it worked. As discussed, I have changed the main readme to say anaconda is recommended for windows.
overall, we don't want to overwhelm the novice user with too many ifs in the readmes, we just want to pick the most pain free most general installation and recommend that. ( ditto for pip install vs git clone for example).

cleaned up the same issue in ../prevented_plant/README.md  Now they all reference the common setup instructions, shouldbe much easier.   interestingly in that dir geopandas in windows is assumed to just work. ( But there's as separate issue with xgboost on windows, which is handled nicely in the code with a fallback alg).

https://github.com/gro-intelligence/api-client/tree/e010553e35e37e330abbe8311107407c7f2f2b63/api/client/samples/crop_models
Looks like the brazil_soybeans folder is still there, with brazil_soybeans_model_overview.md
Want to remove that file and directory?

"and" -> "or"

done


A white line appears below the mainwindow

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):
10.0.19025.1051
Any other software?
none

Steps to reproduce
there's a white line below this window , no matter when I use dark theme or light theme

Expected behavior
it is a small bug... i hope it can be fixed in next version... thx

Actual behavior

Sounds like a duplicate of #3064.

Thanks for the triage @j4james! Yep, this is definitely a /dup of #3064, which is fixed by #3394.


no such file or directory, open '/path/schema.prisma' since 3.1.1

Bug description
When I call  new PrismaClient(), I get the error
(node:12802) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, open '/mnt/d/workspace/path/packages/api/src/schema.prisma'

That just happen on 3.1.1
How to reproduce

Upgrade prisma to 3.1.1
Execute prisma db push command
Call  new PrismaClient()

Expected behavior
No response
Prisma information

Environment & setup

OS: Windows(wsl)
Database: SQLite
Node.js version: v14.17.4

Prisma Version
prisma                  : 3.1.1
@prisma/client          : 3.1.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine c22652b7e418506fab23052d569b85d3aec4883f (at ../../.yarn/unplugged/<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli c22652b7e418506fab23052d569b85d3aec4883f (at ../../.yarn/unplugged/<EMAIL_ADDRESS>Introspection Engine    : introspection-core c22652b7e418506fab23052d569b85d3aec4883f (at ../../.yarn/unplugged/<EMAIL_ADDRESS>Format Binary           : prisma-fmt c22652b7e418506fab23052d569b85d3aec4883f (at ../../.yarn/unplugged/<EMAIL_ADDRESS>Default Engines Hash    : c22652b7e418506fab23052d569b85d3aec4883f
Studio                  : 0.423.0

@s97712 Are you also getting this in context of a Yarn Workspace Package?

I forgot to mention, I'm seeing this using yarn v1. I haven't confirmed
this with V2.
On Wed, 29 Sep 2021, 3:10 am Jan Piotrowski, @.***>
wrote:

@s97712 https://github.com/s97712 Are you also getting this in context
of a Yarn Workspace Package?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prisma/prisma/issues/9435#issuecomment-929417980, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF73EX5R6OH42WINUSUPZO3UEHZJPANCNFSM5EX2VDVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I am also getting a similar error after upgrading to 3.1.1. Seems to "stop" at the first folder in the workspace. I am currently outputting the prisma client as a sibling workspace package and importing it accordingly. 3.0.2 works fine.
Error: ENOENT: no such file or directory, open '/usr/src/app/packages/server/.vscode/schema.prisma'
prisma                  : 3.1.1
@prisma/client          : 3.1.1
Current platform        : darwin
Query Engine (Node-API) : libquery-engine c22652b7e418506fab23052d569b85d3aec4883f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : c22652b7e418506fab23052d569b85d3aec4883f
Studio                  : 0.423.0

@danielmahon Also Yarn workspaces?

Based on the folder structure I would imagine so
On Wed, 29 Sep 2021, 8:48 pm Jan Piotrowski, @.***>
wrote:

@danielmahon https://github.com/danielmahon Also Yarn workspaces?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/prisma/prisma/issues/9435#issuecomment-930063562, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF73EX36ITMXEJJUTAW72IDUELVIZANCNFSM5EX2VDVQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@danielmahon Also Yarn workspaces?

Yup, but I'm also using the traditional node_modules workflow, not pnp. (For the time being)

I'm using npm workspaces and seeing this issue with Next.js.

Using Yarn v3 with PnP getting the error
Error: ENOENT: no such file or directory, open<EMAIL_ADDRESS>Not using any workspaces.

@s97712 Are you also getting this in context of a Yarn Workspace Package?

Yup

Facing the same issue on 3.0.2 btw.
I have the monorepo setup working with a regular Node.js app but facing this issue when trying to use it with Next.js.

Everyone else has this working in 3.0.x but it only broke in 3.1.1 @s97712 @henry-young @coolcalcacol @danielmahon?
I suggest everyone for whom it did not only break with 3.1.1 please open a separate issue so we can investigate this properly. Thanks. The original poster here explicitly mentions that this happens after the update to 3.1.1, so let's only investigate these cases here. Might have very different root causes.

I'm using 3.1.1 -
It’s not running properly in my lambda function/layer setup. I get the error ENOENT: no such file or directory, open '/var/task/schema.prisma'
Can I at least tell it what path my schema.prisma file is at somehow? I couldn’t find anything in the docs. I have the file in a lambda layer (/opt/nodejs/prisma)

Additionally, it seems like in Prisma 3 it now is trying to find the schema.prisma file when I import the file that constructs my prisma client (new PrismaClient()), whereas before it didn’t do that. This is a problem for me because some of my lambda functions are set up to use prisma (with secrets, layer, network access to the DB, etc) and some aren’t but still import files which import the prisma client. So now I can’t start the functions that don’t have anything to do with prisma because it explodes saying it can't find schema.prisma even though I have no intention of using it in that function.

Is this a new problem with 3.1.1 @revmischa? If not, please open a new issue as this one is about a change between Prisma 3.0.x and 3.1.1.

Can you please help us out and create a minimal reproduction of your setup that shows the problem occurring? Please put it in a Github repository and post the link here. Thanks.

I cannot reproduce in the new project, I will try to find out the real reason

Is this a new problem with 3.1.1 @revmischa? If not, please open a new issue as this one is about a change between Prisma 3.0.x and 3.1.1.

I was testing upgrading from 2.x right now. I just tried 3.0.2 and got the same missing schema error.

Can you please help us out and create a minimal reproduction of your setup that shows the problem occurring? Please put it in a Github repository and post the link here. Thanks.

https://github.com/s97712/prisma-workspace

Can you please help us out and create a minimal reproduction of your setup that shows the problem occurring? Please put it in a Github repository and post the link here. Thanks.

https://github.com/coolcalcacol/prisma-issue

Everyone else has this working in 3.0.x but it only broke in 3.1.1 @s97712 @henry-young @coolcalcacol @danielmahon?

This is correct.
I am currently using 3.0.2 with no issues. Issue only happens after upgrade.

I can reproduce with https://github.com/s97712/prisma-workspace and https://github.com/coolcalcacol/prisma-issue.
We don't officially support Yarn 2/3 but still going to mark this as confirmed bug for now.

We don't officially support Yarn 2/3

Is this expected to happen?

@coolcalcacol Follow https://github.com/prisma/prisma/issues/1439. No timeline yet.

I can confirm the same bug. Works fine with 3.0.2

Same problem here. @henry-young helped me work around the issue.
findSync is very eager to find a match for the generated output and one needs to work around the current implementation in order to trick it to fall back to __dirname.
First of all, having a path with only one segment will make the second passed matcher to findSync be an empty string, which matches everthing. So my first fix was to move around my setup so that the output path had 2 segments, i.e.
generator client {
  provider = "prisma-client-js"
  output = "./generated/client"
}

Next thing i did was make sure that my path would not be accidentally matched by any filename in the yarn cache, since prisma will recurse through that(!). Picking an output path like ./prisma/client will match for the first segment and break.
I ended up choosing ./generated/client, which works for my case. It sure would be nice to pass the dirname in the config, next to the output 😁

I can confirm. Setting it to "./generated/output" from "../prisma-client" fixes it for me.

Confirming that the above works. Thanks for that @tobilen.
As @tobilen mentioned, it's important that the path starts with ./ and has two segments (I also chose generated/output).
It is nice to have a workaround, although my preference would still be to add the quotes back into the string as per <= v3.0.2.

Also, for anyone wondering my folder structure is as follows:
node_modules/
prisma/
├─ generated/
│  ├─ output/
│  │  ├─ ...generated files here...
├─ migrations/
├─ schema.prisma
.gitignore
package.json
tsconfig.json

I was unable to have my schema file (and my generated output) in the root of the package. Nesting everything under /prisma works well for me.
Also here is a snippet from my package.json just incase anyone was needing help with yarn workspaces.
{
  "name": "@db/client",
  "private": true,
  "main": "prisma/generated/output/index.js",
  "types": "prisma/generated/output/index.d.ts",
...
}

So I can access prisma using import { PrismaClient } from '@db/client'; from another package in the workspace.

Hit this using NPM workspaces for a monorepo (with Next.js).
I couldn't get @henry-young's ./generated/output fix to work for me - but figured another way that's working:

prisma folder nested within monorepo workspace package e.g. <monorepo root>/packages/mydbpackage/prisma/schema.prisma
generator output= directly into <root>/node_modules/ (similar to the default when output isn't specified)
.. and use the @ prefix to scope the generated client node_module package name
Finally, be sure import the client using the @prefix-scoped module pathname

Works for me importing into a separate monorepo Next.JS package:
prisma.schema:
generator = "../../../node_modules/@~internal/prisma-myschema/client"

then:
import { PrismaClient } from "@~internal/prisma-myschema/client

(No dependencies required in the calling module package.json - node will automatically look in the root node_modules)
This is now working for me with multiple prisma schemas, managed separately from within one package within my monorepo, and generated separately into different top-level node_modules folders.
Using the @-scope prefix seems to force the client to be treated as an external dependency to be loaded from node_modules and not anywhere else. The client is then found correctly, not transpiled by Next.JS (as encountered in #10171), and the import treated successfully as CommonJS rather than hitting an error when the generated client attempts to require('./runtime..') which I encountered due to my monorepo being configured with type="module".
(Thanks for the shares above, directed me to figure this out after digging around in the zaniness of the findSync() / __dirname logic - which appears to be attempting more magic than some might consider healthy 😬 )

@andyjy are you able to share a sample project that includes the different pieces?
I have this in a db package:
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
  generator = "../../../node_modules/@~internal/prisma-myschema/client"
}

And when I import the following into my web package (a Next.js project). I get the following error:
import { PrismaClient } from "@~internal/prisma-myschema/client"

Or in Next:
Module not found: Can't resolve '@~internal/prisma-myschema/client'

@andyjy are you able to share a sample project that includes the different pieces?

Sure! https://github.com/andyjy/prisma-multiple-schemas-monorepo-demo

I've been facing a similar issue where the path points to .git
Error: ENOENT: no such file or directory, open '/home/opc/Documents/project/.git/schema.prisma'
And I think it has something to do with this code at the beginning of runtime/index.js
const dirname = findSync(process.cwd(), [
    ".prisma",
    "",
], ['d'], ['d'], 1)[0] || __dirname

After some investigating, findSync was matching all the directories in process.cwd() and just listing them out and then picking the first one. I fixed it by removing the empty string in the array, and it works now. Not sure if this helps at all but the issue seems similar, and only happened after I upgraded from ~3.0.0
const dirname = findSync(process.cwd(), [
    ".prisma",
], ['d'], ['d'], 1)[0] || __dirname

Appearently, is this function here:
https://github.com/prisma/prisma/blob/62b91fd9bd32da983f457857411edef6daeecda1/packages/client/src/generation/utils/buildDirname.ts#L31
It fails to generate the correct directory to the generated code. For me, if i change it to only __dirname it works seamlessly
Located at the generated code index.js

Looks like https://github.com/prisma/prisma/pull/9295 caused this by removing the quotes

Still seem to be hitting this issue in 3.8.0, any chance of a fix any time soon? I'd rather not write a script to modify a generated file and languishing on 3.0.2 prevents me from getting bug fixes, vulnerability fixes, etc.

In the same boat here. The fix is there, I just can't figure out why the test won't run. Ideally this is done before the 3.9 milestone

Same<EMAIL_ADDRESS>

Facing same issue on 3.9.1

Hey everyone, we have a fix that is ready. Could you please give it a try?
<EMAIL_ADDRESS>

Hey @millsp, can confirm your version mentioned in above works for solving this issue. Thanks for taking care! cc @Jolg42 @janpio

@millsp, 3.11.0-integration-fix-empty-path.1 version resolved the issue, thanks.

Willing to bet reproduction is the same as #10512

Same<EMAIL_ADDRESS>version time？

@millsp I just tried your fix but it doesn't seem to solve the issue that when I build my app into ./build/index.js in a workspace, Prisma then tries to find the schema file at ./build/schema.prisma instead of ./prisma/schema.prisma.
Is this a different issue than the one you fixed?

Getting the same issue with yarn v3.1.1<EMAIL_ADDRESS>

Managed to resolve this issue by symlinking the schema.prisma and engine files. Check out this comment for the details.

if you are using next u can also try #10433


OSGi - Jsoup imports its own packages

Discussed in https://github.com/jhy/jsoup/discussions/2145

Originally posted by bencebarna June 19, 2024
Hi!
I have noticed that with the current maven-bundle-plugin configuration the OSGi manifest is generated in way that Jsoup imports it's own packages. Is this being done on purpose?
I am asking because in my current project a 3rd-party bundle embeds and exports Jsoup (already notified the vendor not to do that) while the Jsoup bundle is also deployed standalone. The embedded Jsoup is a different version than the standalone one.
And in some cases, during deplyment, the standalone bundle imports the embedded Jsoup packages from the 3rd-party lib and exports them with that version. Making the version of the standalone packages unavailable.

Updated per @bencebarna's suggestion in #2145.


Bump Bottlerocket to 1.15.1

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Single item recall problem

Indeed, he can get here, but the application screen remains black without displaying anything
import 'package:cloud_firestore/cloud_firestore.dart';
import 'package:flutter/material.dart';
import 'package:try22/config/toast_component.dart';

class UserInformation extends StatefulWidget {
  UserInformation(data);

  @override
  _UserInformationState createState() => _UserInformationState();
}

class _UserInformationState extends State<UserInformation> {
  final Stream<QuerySnapshot> _usersStream =
      FirebaseFirestore.instance.collection('productId').snapshots();
  ScrollController _mainScrollController = ScrollController();

  @override
  Widget build(BuildContext context) {
    print(['productTitle1']);
    return StreamBuilder<QuerySnapshot>(
      stream: _usersStream,
      builder: (BuildContext context, AsyncSnapshot<QuerySnapshot> snapshot) {
        print(['productTitle2']);
        if (snapshot.hasError) {
          return Text(
            'Something went wrong',
            style: TextStyle(color: Colors.white),
          );
        }
        print(['productTitle3']);
        if (snapshot.connectionState == ConnectionState.waiting) {
          return Text("Loading");
        }

        print(['productTitle4']);

        return new ListView(
          children: snapshot.data!.docs.map((DocumentSnapshot document) {
            Map<String, dynamic>? data =
                document.data() as Map<String, dynamic>?;

            return Scaffold(
              body: CustomScrollView(
                controller: _mainScrollController,
                physics: const BouncingScrollPhysics(
                    parent: AlwaysScrollableScrollPhysics()),
                slivers: [
                  SliverList(
                      delegate: SliverChildListDelegate([
                    Padding(
                        padding: const EdgeInsets.fromLTRB(
                          16.0,
                          8.0,
                          16.0,
                          0.0,
                        ),
                        child:  Text(
                        data!['productTitle'],

                          style: TextStyle(
                              fontSize: 20,
                              color: MyTheme.font_grey,
                              fontWeight: FontWeight.bold),
                          maxLines: 2,
                        )
                        ),
                  ])),
                ],
              ),
            );
          }).toList(),
        );
      },
    );
  }
}

@SylvesterTube
if it's an issue with firebase should be opened here

Hi @SylvesterTube
From what I can see, the issue is related to a FlutterFire plugin rather than to Flutter itself. Please open the issue in the dedicated repository.
Closing, as this isn't an issue with Flutter itself.
If you disagree, please write in the comments,  providing your flutter doctor -v, your pubspec.yaml, a minimal reproducible code sample that does not use 3rd party plugins, your complete flutter run -v logs running the minimal code sample
and I will reopen it.
Thank you


[Cosmos] Migrate get_attachment operation to pipeline architecture

Moving get_attachment to pipeline architecture.
Continuing #290
I am pretty new to rust and wanted to get my hands on something real. Let me know if I've made any mistakes! I have tried to use previous migration examples as much as I can.

@rylev I have been trying to run the test you have pointed me towards locally but I can't get it to work. I have tried:
 $ TESTING_MODE=RECORD cargo run --example create_database_and_collection --features=mock_transport_framework
which gave this error:
error: no example target named "create_database_and_collection"
and
cargo test --features mock_transport_framework
with TESTING_MODE set to RECORD in my environment. This gives the following error:
[2021-10-09T11:49:54Z ERROR azure_core::policies::retry_policies::exponential_retry] Error occurred when making request: failed to execute request: error sending request for url (https://.documents.azure.com/dbs): error trying to connect: dns error: failed to lookup address information: Name or service not known

I think the first error is expected, since you moved the create_database_and_collection test out of the examples directory. The second is more interesting. The URL (https://.documents.azure.com/dbs) doesn't contain the cosmos account name. Following the code made me think this issue is arising in setup.rs. I can see that tests that don't use the mock_transport_framework get the cosmos account name from an environment variable, COSMOS_ACCOUNT, but I can't see how the mock_transport_framework tests get the cosmos account name.
It would be great for me to be able to run this locally so I can look at the output of a successful RECORD test. What am I missing/doing wrong here?
Thanks

Some notes from the latest updates - which pipeline-ify more attachment-related APIs

slugs were a bit awkward.

I'm not sure whether adding the Slug type is right just so that I can add this as a header, or whether I've missed some utility function that would have done the job.
slug replacement was previously using the CreateSlugAttachmentResponse, I've chosen to copy that into a ReplaceSlugAttachmentResponse, valuing the consistency more than the duplication

I have removed the explicit setting of content-length and content-type for requests with bodies.

This is also what the other operations do so I assume there's some magic somewhere that adds these headers, but mentioning it in case I'm wrong and reviewer says "oops, we should be setting those".

We currently don't have a cosmosdb where this API is enabled... so none of this is yet tested against a real system.  We have a support request open so hopefully we'll be able to get to this soon and add the mock transport tests

The interesting new commits here are https://github.com/Azure/azure-sdk-for-rust/pull/375/commits/976539c45badefd7782a2104e5fd0dcb0af11a98, https://github.com/Azure/azure-sdk-for-rust/pull/375/commits/6bc2ae2ccbb6c24c3e8fd3a0b67f7191dbd485bd, https://github.com/Azure/azure-sdk-for-rust/pull/375/commits/7bf9b9b8e36620d591cf3d2078344fcf1a94ff0b, https://github.com/Azure/azure-sdk-for-rust/pull/375/commits/41f022b690034dfd5c22c54e1f7de134799a020e, and https://github.com/Azure/azure-sdk-for-rust/pull/375/commits/36525e2aeb5c6eec22b4c8a7e7748a13f57733bd.

The first two are direct responses to mark-ups from @rylev above
The third is a simple bug fix
The fourth pipeline-ifies list_attachments() and delete_database(), allowing us to move the attachments testcase over to the mock transport framework

The delete_database() work was meanwhile also done in main, so that part of this MR is largely erased by subsequent merges

The fifth makes some fixes arising from running the e2e tests

again includes some delete_database() work which is undone or duplicated by a later merge

The rest is just merging from main - it's been a busy couple of weeks on main while we've been waiting for everything to come together at our end.
Sorry that this has gotten rather large and unwieldy, I think it is finally ready to go now (modulo any further merges that may be needed...)

I'm really sorry we've let this go for so long. Unfortunately the diff is really large and very hard to review. If you're still interested in getting this merged, I suggest creating new PRs where smaller changes are included in each individual PR. For example, you can see how #584 was closed in favor of smaller more easy to review PRs like #586 and #592. This makes it much easier to review and changes can land much quicker.


reference：https://github.com/wbkd/react-flow/issues/916

I had a similar problem. When I dynamically add a handler on a custom node, I find that the node's handlerDOM is updated, but when I create an edge for the node at the same time after the addition is successful, I find that the targetNode cannot be found (I specified targetNode), followed by I used useUpdateNodeInternals when the handler was successfully created. I found that getHandle still cannot get the latest handler dom. I suspect that there is a bug in the state synchronization.

here i can't get the latest handlers
Originally posted by @sunWoodsen in https://github.com/wbkd/react-flow/issues/916#issuecomment-1012030847

Hi @sunWoodsen !
Can you share an example or your code ?
I created a custom node that allows to dynamically manage the number of handles. I also had a state problem for the handles, and I was able to solve it thanks to a useEffect containing the updateNodeInternals function.
I share my issue with you, maybe it can help you : https://github.com/wbkd/react-flow/issues/1641
I'm not sure I fully understand your problem, but hope my answer helps you.

I experience same issue.
Using dynamic handles looks fine in the browser as added handles are visible.
However connecting the new generated handle (outbound) to an existing input handle will not draw the line.
This also results in following warning: "couldn't create edge for source handle id: handle__id; edge id: edge_id"
I guess that @sunWoodsen is programmatically generating an edge, which will lead to the same issue I'm experiencing.

Yes, it is this situation that causes the error, when I create the handler dynamically, it looks normal, but when I create a new edge for the new handler, I get an exception

I experience same issue.
Using dynamic handles looks fine in the browser as added handles are visible. However connecting the new generated handle (outbound) to an existing input handle will not draw the line.
This also results in following warning: "couldn't create edge for source handle id: handle__id; edge id: edge_id"
I guess that @sunWoodsen is programmatically generating an edge, which will lead to the same issue I'm experiencing.

Yes, it is this situation that causes the error, when I create the handler dynamically, it looks normal, but when I create a new edge for the new handler, I get an exception

Hey @sunWoodsen ,
could you create a codesandbox for this issue?


Proposal to rename parquet-mr to parquet-java

When I first encountered "parquet-mr" I didn't not understand what the mr meant (I think it is map reduce?) but I believe what the https://github.com/apache/parquet-mr repo actually contains is a java implementation maintained by the Apache Parquet PMC

@pitrou  mentions the confusion about parquet-mr naming as well here
https://github.com/apache/parquet-site/pull/53#discussion_r1598284018

Also, can we explain what "mr" stands for? It's a mystery for most people.

Julien Le Dem suggested  renaming the parquet-mr repository to parquet-java to reduce confusion about its content: https://github.com/apache/parquet-site/pull/59#pullrequestreview-2056038304

This looks great. Thank you for taking the initiative. Hadoop is not required indeed. Perhaps at some point we should rename parquet-mr to parquet-java?

Thus I suggest we rename the repo to parquet-java. This requires an infra ticket which I can do if people agree with this

Note that all existing github links would continue to function by redirecting to the new name we recently renamed https://github.com/apache/arrow-datafusion to https://github.com/apache/datafusion for example and all the old links still work)
Reporter: Andrew Lamb / @alamb
Note: This issue was originally created as PARQUET-2475. Please see the migration documentation for further details.

Andrew Lamb / @alamb:
Repo has been renamed: https://github.com/apache/parquet-java

Andrew Lamb / @alamb:
Related mailing list discussion: https://lists.apache.org/thread/m911chzz5pz8o8fb1y0x49h96g8w29d7

Andrew Lamb / @alamb:
Infra request: https://issues.apache.org/jira/browse/INFRA-25802


🍒 Cherry pick PR #18778 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/18778 to staging 🍒

🚀 Cherry-picked to staging by https://github.com/OSBotify in version: 1.3.13-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/Beamanator in version: 1.3.13-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/AndrewGable in version: 1.3.28-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/AndrewGable in version: 1.3.28-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Automatic .env and config.md Script for Farmerbot (.v, .sh and .py)

Automatic .env and config.md Script for Farmerbot (.v, .sh and .py)
Here is a script that generates the .env and config.md files for the Farmerbot.
This is a first draft. It should write the files properly. I set this as an issue to get feedback from the community and the dev team and then adjust accordingly.
Every input asked are dealt in terms of potential input errors, except for the HEX or seed phrase to give room for the two formats.
The 12 hour format is required to simplify the script.

Link to the Script
Follow the steps on this repo:
https://github.com/Mik-TF/farmerbot-script

If Threefold appreciates this script, we could add it on the Farmerbot guide and also on this repository (threefoldtech/farmerbot)

Feedback and questions are welcome.
UPDATE: The script is now available in both Python and Bash, as discussed in this issue.

Nice work! Although a bash script might not be the best solution here... For future development purposes I mean. Maybe I can do it in V or in Python and release it together with the farmerbot?

@brandonpille
Great! Thanks for the proposition Brandon. I think it would be great if you want to tune this into a V or Python version.
That's exactly what I had in mind: build a script that works and get your feedback to see how to go forward.
Let me know if I can be of any help.

Edit: I changed the name from nodes.md to config.md for convention purpose (detail).

@brandonpille
You can have a look here: https://github.com/Mik-TF/farmerbot-script/blob/main/farmerbot_script.py
I did the necessary changes to have it in python, as requested.
Let me know what you think!
Clearly the code could be shorter, with functions et al. But it gets the job done!

It's a bit messy indeed. Maybe I can give a few pointers:

It is preferred to use the main function when creating tools in python: https://realpython.com/python-main-function/#a-basic-python-main
It is indeed a better idea to put the code in separate functions
One more thing. The users will have to install Python in order to run this... Maybe an executable build with V would have been better, no?

OK thanks for the feedback.
I agree using a main function and different functions for the code in Python would be 100% better.
Also, it's a good point that an executable build with V instead of Python would be better.
If you have a clear idea on what is needed to get it in V with a better flow, let me know if you want to go ahead and convert either the bash or python to V yourself.
Otherwise, I can do the conversion to V myself. But it would surely take some more time.
Thanks again for all the great feedback and help on this.

You can go ahead with the conversion. Did you ever write V code? If no I can help you. We can have a quick call if you like.

Thank you Brandon for the help. I did try some V before and did check the documentation a little. It looks very well designed. I know it can be learned over a weekend, so there's no excuse! I'll go through the documentation and vlib.
I will have a try and let you know if I get stuck or need help at some point.
I'll start by converting the python and/or bash to Vlang, and then "clean" the code (setting the main and other functions).

The Vlang version is now done with the necessary steps to install and run: https://github.com/Mik-TF/farmerbot-script
The script itself: https://github.com/Mik-TF/farmerbot-script/blob/main/farmerbot_script.v
I can either do a PR now, or get feedback and update the VLang version.
Should I publish also the bash and python? Or just the Vlang for the pull request in the farmerbot repo?
Should I do a branch and put the script in this subrepo?: https://github.com/threefoldtech/farmerbot/tree/development/scripts
Thanks!

There is a new version that queries grid proxy when possible:
https://github.com/Mik-TF/farmerbot-script/blob/main/farmerbot_script_gridproxy.v
The user only needs to give the node ID for the program to query:

farm ID
public IP in the farm
public config of the node
dedicated status of the node
certification status of the node

The Vlang version is now done with the necessary steps to install and run: https://github.com/Mik-TF/farmerbot-script
The script itself: https://github.com/Mik-TF/farmerbot-script/blob/main/farmerbot_script.v
I can either do a PR now, or get feedback and update the VLang version.
Should I publish also the bash and python? Or just the Vlang for the pull request in the farmerbot repo?
Should I do a branch and put the script in this subrepo?: https://github.com/threefoldtech/farmerbot/tree/development/scripts
Thanks!

Hi. Thanks, yes you can create a branch, put it in the scripts folder and then open up a PR. I'll review it.

What exactly is the purpose of that script?

OK I will soon make a PR with both versions: the one that queries gridproxy and the other than ask all the questions for the user to add manually.
The purpose: with this script, farmers can create very quickly the .env and config.md files.
Also with the version that queries gridproxy, they only need to enter the node IDs to get farm ID, public IP of the farm, public config, dedicated, certification status of the node.

@brandonpille
Here is a new version that will show more clearly the purpose:
https://github.com/Mik-TF/farmerbot-script/blob/main/fbot_README.md
By following those steps, the farmer can deploy the farmerbot very quickly.

create the folder and files structure
download and run .yaml farmerbot


HexColor defines no transparency

The color definition lacks transparency.
In CSS the alpha value represents the transparency of a color.
The HexColor does only support red, green and blue value.
I suggest a fourth optional alpha value at the end of the HexColor.
<xs:pattern value="#[0-9a-fA-F]{6}([0-9a-fA-F]{2})?"/>
The effect of transparency applies each time, when containers are used in BPMN, e.g. colored lanes with transparent flow elements.

BPMN MIWG 8 Sep 2021 Webmeeting
o	Given that the Diagram Definition (DD) covers these topics and that a subset of an early version of DD was pasted in BPMN at the time of its release (when DD was not yet an official standard). We felt this would be better addressed with a BPMN 3.0 RFP/submission)


Exception handling

Attach (recommended) or Link to PDF file here:
Happens for any PDF file
Configuration:
Web browser and its version: Chrome -79
Operating system and its version: MacOS-Mojave
PDF.js version:v2.3.200
Is a browser extension: No
Steps to reproduce the problem:
I am getting the below crash when we zoom or rotate pages faster (faster means before zoom is completed zoom again, continuous clicking)
pdf.js:20157 Uncaught (in promise) Error: TextLayer task cancelled.
    at TextLayerRenderTask.TextLayer_cancel [as cancel] (pdf.js:20157)
    at TextLayerBuilder.cancel (pdf_viewer.js:2855)
    at PDFPageView.cancelRendering (pdf_viewer.js:6146)
    at PDFPageView.reset (pdf_viewer.js:6027)
    at PDFPageView.update (pdf_viewer.js:6131)
    at PDFViewer.set (pdf_viewer.js:8049)
    at Object.rotatePages (pdfApp.js:277)

1. I am not able to catch the above exception
2. Can you please let know how to solve the crash. I think the exception is ok because it is trying to cancel the previous render, please correct me if I am wrong.
Note: I am not using the default PDF viewer. I am using PDFJS api to build my own viewer.
What is the expected behavior? (add screenshot)
There should not be any exception
What went wrong? (add screenshot)
There is exception and not able to catch exception
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):
It is not yet hosted. I am testing in my local machine.

When opening an issue, you need to provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md

@Snuffleupagus I updated the information as per template

pdf.js:20157 Uncaught (in promise) Error: TextLayer task cancelled.
...

That message simply informs you that there was a catch missing in a promise-chain, but doesn't necessarily mean that there's any breaking errors.

[...] I think the exception is ok because it is trying to cancel the previous render,

This sentence seem to suggest that there's no actual errors, but rather only the console message as quoted, which makes the use of words such as "crash" and "exception" in https://github.com/mozilla/pdf.js/issues/11469#issue-544990393 slightly difficult to interpret (since those would generally only be used if things break completely).

PDF.js version: v2.3.200

The only case of "Uncaught promise" messages, relevant for the TextLayer code, I'm able to recall was fixed by PR #10962, which is included in that version of the library; see https://github.com/mozilla/pdf.js/releases/tag/v2.3.200
Hence this issue unfortunately doesn't really make sense, given the currently provided information.

It is not yet hosted. I am testing in my local machine.

Considering everything above, the only way to make this issue actionable would be actually provide a runnable example, please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us on the IRC channel -- keep in mind that just code snippets won't help us troubleshoot the problem.

ok..thanks for your help.


Modify scaffolding command to use dotnet ef

Updated dotnet tools version to use preview4, and also modified the command to reverse engineer databases to use dotnet ef instead.

Hi @zemien, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

This walkthrough is specifically designed for Visual Studio users (we have https://docs.microsoft.com/en-us/ef/core/get-started/netcore/ for cross-platform/non-VS users). Package Manager Console commands are the approach we push folks toward in VS, they are the most robust and have the most context about the solution (current project, startup project, etc.). To that end, this is not a change we want to take.


CAPP ruleset not provided on Bionic

Ran into this while running a wrapper cookbook on bionic.
According to https://reposcope.com/package/auditd/files the CAPP rules (and others) archive(s) previous available on xenial are no longer included with the auditd package.
Compare the file list for the auditd package on xenial and bionic.
For me, auditd::rules dies with the following on bionic.

Seems like the assumption is that "/usr/share/doc/auditd/examples/capp.rules.gz" exists:
Recipe: auditd::rules
  * auditd_builtins[capp] action create[2018-11-02T19:48:21+00:00] INFO: Processing auditd_builtins[capp] action create (auditd::rules line 24)

    * execute[installing ruleset capp] action run[2018-11-02T19:48:21+00:00] INFO: Processing execute[installing ruleset capp] action run (/tmp/packer-chef-client/local-mode-cache/cache/cookbooks/auditd/resources/builtins.rb line 35)

      [execute] gzip: /usr/share/doc/auditd/examples/capp.rules.gz: No such file or directory

      ================================================================================
      Error executing action `run` on resource 'execute[installing ruleset capp]'
      ================================================================================

      Mixlib::ShellOut::ShellCommandFailed
      ------------------------------------
      Expected process to exit with [0], but received '1'
      ---- Begin output of zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules ----
      STDOUT:
      STDERR: gzip: /usr/share/doc/auditd/examples/capp.rules.gz: No such file or directory
      ---- End output of zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules ----
      Ran zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules returned 1

      Resource Declaration:
      ---------------------
      # In /tmp/packer-chef-client/local-mode-cache/cache/cookbooks/auditd/resources/builtins.rb

       35:     execute "installing ruleset #{new_resource.name}" do
       36:       command "zcat /usr/share/doc/auditd/examples/#{new_resource.name}.rules.gz > /etc/audit/audit.rules"
       37:       notifies :restart, 'service[auditd]'
       38:     end
       39:   end

      Compiled Resource:
      ------------------
      # Declared in /tmp/packer-chef-client/local-mode-cache/cache/cookbooks/auditd/resources/builtins.rb:35:in `block in class_from_file'

      execute("installing ruleset capp") do
        action [:run]
        default_guard_interpreter :execute
        command "zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules"
        backup 5
        declared_type :execute
        cookbook_name "auditd"
        domain nil
        user nil
      end

      System Info:
      ------------
      chef_version=14.6.47
      platform=ubuntu
      platform_version=18.04
      ruby=ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux]
      program_name=/usr/bin/chef-client
      executable=/opt/chefdk/bin/chef-client

[2018-11-02T19:48:21+00:00] INFO: Running queued delayed notifications before re-raising exception

    ================================================================================
    Error executing action `create` on resource 'auditd_builtins[capp]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    execute[installing ruleset capp] (/tmp/packer-chef-client/local-mode-cache/cache/cookbooks/auditd/resources/builtins.rb line 35) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
    ---- Begin output of zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules ----
    STDOUT:
    STDERR: gzip: /usr/share/doc/auditd/examples/capp.rules.gz: No such file or directory
    ---- End output of zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules ----
    Ran zcat /usr/share/doc/auditd/examples/capp.rules.gz > /etc/audit/audit.rules returned 1

    Resource Declaration:
    ---------------------
    # In /tmp/packer-chef-client/local-mode-cache/cache/cookbooks/auditd/recipes/rules.rb

     24:   auditd_builtins 'capp'
     25: when 'lspp'

    Compiled Resource:
    ------------------
    # Declared in /tmp/packer-chef-client/local-mode-cache/cache/cookbooks/auditd/recipes/rules.rb:24:in `from_file'

    auditd_builtins("capp") do
      action [:create]
      default_guard_interpreter :default
      declared_type :auditd_builtins
      cookbook_name "auditd"
      recipe_name "rules"
    end

    System Info:
    ------------
    chef_version=14.6.47
    platform=ubuntu
    platform_version=18.04
    ruby=ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-linux]
    program_name=/usr/bin/chef-client
    executable=/opt/chefdk/bin/chef-client

Like shouting into the void.


Trouble connecting to the database

As of a couple hours ago, I keep running into this with workflow:
$ k get pods
NAME                  READY     STATUS             RESTARTS   AGE
deis-builder-faenw    1/1       Running            0          3m
deis-database-zw9a9   1/1       Running            2          3m
deis-minio-7awtz      1/1       Running            0          3m
deis-registry-fqdlh   1/1       Running            0          3m
deis-router-9daqc     1/1       Running            1          3m
deis-workflow-qua36   0/1       CrashLoopBackOff   5          3m

The reason:
$ k logs deis-workflow-qua36 --previous
system information:
Django Version: 1.9.3
Python 3.5.1
Django checks:
System check identified no issues (2 silenced).
Health Checks:
Checking if database is alive
There was a problem connecting to the database

@krancour what are the logs in the database showing? This is expected behaviour while everything is booting up (database relies on minio, workflow relies on the database) and should shake itself out once the database is ready to accept connections and workflow has rebooted (to speed up the CrashLoopBackOff, just delete the workflow pod).

This is happening on a fresh install (no db restore) and seems to continue after the db is up.  I'll grab db logs shortly.

I've discussed with @krancour offline that this is because the database was not ready at the time of the health check, so it went into a CrashLoopBackOff. Waiting for the controller to restart or killing it (forcing a new pod to boot) fixes this.


maud_macros does not work under older Rust nightly versions

When trying to compile Maud under rustc 1.27.0-nightly (ac5c0848d 2018-05-14) (not using the current version because of Diesel 1.3 compilation errors and rust-lang/rust#50825 and rust-lang/rust#51042), Maud fails to compile because TokenTree and Ident have been removed from the proc_macro crate in the most recent version.
error[E0432]: unresolved import `proc_macro::Ident`
 --> maud_macros/src/generate.rs:8:5
  |
8 |     Ident,
  |     ^^^^^ no `Ident` in the root

error[E0432]: unresolved import `proc_macro::Ident`
  --> maud_macros/src/lib.rs:19:33
   |
19 | use proc_macro::{Literal, Span, Ident, TokenStream, TokenTree};
   |                                 ^^^^^ no `Ident` in the root

error[E0599]: no variant named `Ident` found for type `proc_macro::TokenTree` in the current scope
  --> maud_macros/src/lib.rs:37:24
   |
37 |     let output_ident = TokenTree::Ident(Ident::new("__maud_output", Span::def_site()));
   |                        ^^^^^^^^^^^^^^^^ variant not found in `proc_macro::TokenTree`

error[E0599]: no variant named `Ident` found for type `proc_macro::TokenTree` in the current scope
   --> maud_macros/src/generate.rs:185:33
    |
185 |         name: TokenStream::from(TokenTree::Ident(Ident::new(attr_name, Span::call_site()))),
    |                                 ^^^^^^^^^^^^^^^^ variant not found in `proc_macro::TokenTree`
..snipped for brevity...

If possible, maud_macros should move to proc_macro2 to avoid this issue.
I see Ident is available through the proc_macro crate in newer Rust nightly versions, but unfortunately Ident is not available through proc_macro in the 2018-05-14.

The above compilation errors are from overriding the nightly version using rustup override set nightly-2018-05-15 and running cargo test from the master branch of Maud.

This issue may not be relevant as Rust nightly is the unstable version, which implies older versions of it are not supported and I should downgrade the Maud version I am using.

You're correct in that Maud does not support older versions of Nightly.
That said, either 0.17.4 or 0.17.3 should work with your setup. I haven't introduced any user-facing changes lately so it should be safe to downgrade.

Using a forced version on maud_macros to version =0.17.4, my program compiles. Thank you anyway.


Detailed installation instructions for rust and emscripten:

I'm not sure if you want to add this to the docs,  but I started from scratch on a new mac, and these were the commands I needed to run.  I believe the commands should be the same on linux/bsd.
(you may need to install cmake if you haven't already installed it)
curl https://sh.rustup.rs -sSf | sh
source $HOME/.cargo/env
rustup update
curl -O https://s3.amazonaws.com/mozilla-games/emscripten/releases/emsdk-portable.tar.gz
tar -xvf emsdk-portable.tar.gz
cd emsdk-portable
./emsdk update
./emsdk install sdk-incoming-64bit
./emsdk activate sdk-incoming-64bit
source ./emsdk_env.sh
cd ..
cargo install cargo-web
rustup target add asmjs-unknown-emscripten
git clone https://github.com/DenisKolodin/yew.git
cd yew/examples/counter
cargo web start

Readme currently has conflicting setup instructions: under "Rust to WASM compilation" there's a link to wasm-and-rust that says to install emscripten etc. but doesn't mention that with nightly you can use wasm32-unknown-unknown without having to build the emscripten sdk. Then under "Development setup" it says to use wasm32-unknown-unknown, and that sometimes you have to use the emscripten target, but then it doesn't mention the link. So maybe the two can be merged?

I added build environment directions here: https://yew.rs/docs/getting-started/build-environment


drive won't show and close app problem

Description
After a quick test of files, when i try to change settings files app close, moreother after some hours in sleep mode on my laptop, files will not show my drives on the first panel.
Steps To Reproduce
go to setting, preference, here the app auto kill and crash
when i open files, ly drives won't show
Expected behavior
just want to change some settings, and see my drives
Files Version
Version : <IP_ADDRESS> OS Version: 10.0.19042.1320
Windows Version
Windows 10 20H2
Relevant Assets
No response

Thanks for the report. Could you upload the app's log files?

I not have it anymore cause i uninstall the app.....
Just try to reinstall and reproduce the error but for now work fine (the app need many time to access l'an folder and folder with many content)

just try some more time the app and have the same problem than before, don't know where to find log files from now but if you point me I can upload it to have some help.

You can get them from %localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState (debug.log + debug_fulltrust.log)


Resource Graph Query issue

The below query does not perform as expected, the properties that are returned do not have a keyCreationTime property within the JSON payload. Via powershell and the Portal however you can access the property, maybe for the Graph product team to look into.
resources
| where type =~ 'microsoft.storage/storageAccounts'
| extend days = datetime_diff('day', now(), todatetime(parse_json(properties).**keyCreationTime**))
| extend KeyExpiryStatus = iff(days > 180, "Policy Violated", "")
| project name, days, KeyExpiryStatus

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

ID: 3463d1c7-f458-738a-2317-b756a1be7de0
Version Independent ID: 40f9e40a-0f2f-f510-7ee4-39e55158c99e
Content: Manage account access keys - Azure Storage
Content Source: articles/storage/common/storage-account-keys-manage.md
Service: storage
GitHub Login: @tamram
Microsoft Alias: tamram

Thanks for reporting this. I have assigned the issue to the content author to investigate further and update the document as appropriate.

@nazakathussain - We now recommend using the built-in policy to monitor compliance with the key expiration policy. See here for details.
The query in question has been removed from the documentation.
#please-close


IntelliJ 2019.1 EAP: Plugin not supported

Short description
IntelliJ 2019.1 EAP considers the Lombok Plugin not compatible and warns before updating.
Expected behavior
Lombok Plugin should not show up as incompatible when updating to 2019.1 EAP
Version information

IDEA Version: 2019.1 EAP 191.4214.41
Lombok Plugin Version: v0.23-2018.3

Steps to reproduce

Have IntelliJ 2018.x installed, have Lombok plugin installed
Start IntelliJ Update dialog

Additional Info
Screenshot of update dialog:

In 2018.3.4 also

I am not sure I understand the fix here: if the plugin version is declared as not compatible with IDEA, how could reinstalling it fix the issue and remove the warning? Or is there a fix available in 0.24 version of the plugin?

This error was displayed after importing settings.

@mmoayyed 0.24 version will prevent Intellij to show this warning during update from 2018.3 to 2019.1
But you can also use existing plugin version -> ignore this warning-> update Intellij-> update plugins. This will install plugin marked as supported for 2019.1

Thank you very much for clarifying this.

I have a new laptop, downloaded this IntelliJ 2019.1, installed the lombok plugin 0.24, from scratch, and still it's getting disabled by Intellij. I will have to use the previous Intellij version in order to work.

@DianaAlcantara https://github.com/mplushnikov/lombok-intellij-plugin/issues/583#issuecomment-466990522

@DianaAlcantara try to reinstall the plugin.

Thanks Alex, but I already removed and installed it again twice. I know the resinstalling the For now,  I'll try working with 2018.3.6. I plugin thing worked for one of my team mates who had the previous intellij and installed the new one: he had to remove and reinstall the plugin. In this case I'm starting with the 2019.1, no other intellij version was on this machine, and reinstalling it is not working.  For now I'm gonna use the old one, until this is solved. Thanks!

@DianaAlcantara This is already solved? create other issue.


Package isn't up to date on PyPi

Hello,
I installed this package from PyPi and it wasn't up to date. Maybe it should be updated on the repository or even saying in the README file to download from Github for the current version.
Thanks!

Yes, this is mentioned in many places.  Please follow PR #260 for when to expect PyPI to be updated shortly after that is merged.


feat: Add views

#10
Checklist

[x] I did't over-scoped my PR
[x] My PR title match the commit convention
[ ] I did not include breaking change
[ ] I included unit test that cover my changes
[ ] I added/updated the documentation about my changes
[ ] I made my own code-review before requesting one

Description of the changes

Technical highlight/advice

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


confirmed rule break on 2.0.0.rc.9

Versions:

VueJs: 2.4.2
Vee-Validate:2.0.0-rc.9

Description:
confirmed rule break in 2.0.0-rc.9, but works in older rc
Steps To Reproduce:
jsfiddle

duplicate of #712
It is already fixed and a new release will be up shortly.


Focus lost when clicking on a selection

Version: 2.0.10
When selecting an option from the drop-down menu by clicking with the mouse, the focus on the field is lost. (Note that when selecting with the keyboard - by pressing ENTER - the focus is maintained.)
I was able to find a fix. See below:
        ...
        dropdownMenu.on('click', function menuEventHandler (event) {
          if(isDisabled) {
            return;
          }

          if(jqLite(event.target).hasClass('dropdown-header')) {
            return;
          }
          var nyaBsOptionNode = filterTarget(event.target, dropdownMenu[0], 'nya-bs-option'),
            nyaBsOption;

          if(nyaBsOptionNode !== null) {
            nyaBsOption = jqLite(nyaBsOptionNode);
            if(nyaBsOption.hasClass('disabled')) {
              return;
            }
            selectOption(nyaBsOption);
            dropdownToggle[0].focus(); // <--- Added this
          }
        });
       ...

I'm not sure if this issue fixed, the following PR will break
https://github.com/lordfriend/nya-bootstrap-select/pull/44


Ether currency support

Hi,
as Kraken supports now Ether (Ethereum digital currency unit) I'd like to know if XChange plans to introduce that currency in its CurrencyPair soon or not.
thanks,
Enrico

I added Ether. I didn't see Ether on Kraken.com though.


Remove FLASH_0 mpu region when CONFIG_XIP=n

When not using CONFIG_XIP (CONFIG_XIP=n)
the FLASH_0 mpu region needs to be removed,
otherwise it will have the default base
address = 0, which means that MPU will try
to configure the region with address 0.
We don't want this as in some situations
address 0 can be a restricted memory region
such as ROM code.
I am making this PR to solve this PR https://github.com/zephyrproject-rtos/zephyr/pull/79993 .Here as CONFIG_XIP=n, both .text and .data are placed in SRAM region and FLASH section get the default value 0 and size 0. Even it is not used FLASH_0 mpu region is created for address 0. So even if just the SRAM_0 will be used, both SRAM_0 and FLASH_0  will be configured by MPU. After these 2 regions are configured, MPU should be enabled, but immediately after it is enabled, the m33 jumps to an exception. Probably because the address 0 that is configured by MPU is M33 boot rom code.
I managed to solve this issue by not configuring the FLASH_0 when CONFIG_XIP=n.
Also I think that FLASH_0 should not be configured by MPU if CONFIG_XIP=n, as this imply that only the CONFIG_SRAM_BASE_ADDRESS will be used for both .text and .data.
Let me know you opinion.

I'm not familiar with this code, but this looks more like an workaround.
Most likely the problem is in another part of the code.
Your board config should use a proper FLASH_BASE_ADDRESS or maybe better understand the issue. What does the exception look like?

@ithinuel  all good. We can merge this.

@ithinuel can you take a look?


React 16: update the react-dom dependency version to 16 instead of 15.6.2 to work with react 16

ERROR in ./~/react-onclickoutside/~/react-dom/lib/ReactMount.js
Module not found: Error: Can't resolve 'react/lib/React' in '...\react-onclickoutside\node_modules\react-dom\lib'
 @ ./~/react-onclickoutside/~/react-dom/lib/ReactMount.js 15:12-38
 @ ./~/react-onclickoutside/~/react-dom/lib/ReactDOM.js
 @ ./~/react-onclickoutside/~/react-dom/index.js
 @ ./~/react-onclickoutside/es/index.js
 @ ./~/react-datetime/src/DaysView.js
 @ ./~/react-datetime/src/CalendarContainer.js
 @ ./~/react-datetime/DateTime.js

went to the following path
<project>-> node_modules -> react-onclickoutside -> node_modules -> react-dom -> package.json

and found that the version number inside package.json of react-dom was 15.6.2 and as a result does not work well with react 16.

Could u share ur setup? Exact versions of react-datetime, also what got installed as react-onclickoutside and what version of npm are you using.

Seeing the same issue :(

@aligfl can you please give some more details? Have you reduced this to where you are 100% certain it's exactly this library and not another component or dependency?


Update gpu_device.cpp

In systems with multiple discrete or integrated GPUS, ensures that the FIRST device is selected.  Fixes #19 for chapter 4. Similar changes need to be applied to all later chapters.

I've added another commit which fixes this issue more thoroughly for Chapter 15.
My Chapter 4 changes simply ensure that if there are multiple discrete devices then the first is chosen.
My Chapter 15 changes are more substantial, and select the first device that is compatible with the display surface.


Produce helpful logs for ffmpeg

When ffmpeg refuse to process a video, no logs are produced even in debug mode. I think it was the case before, need to look at this. At least in debug mode a full log should be produced.

Done in 744ac2ed24b6114e9d29ecfeafdd79136bec2066


Using back (dragging from the side) doesn't immediately exit the app, you need to use back twice

expected - back immediately exits the app

https://github.com/kristapsbe/meteo_android/commit/69a22de35821881beea1d07123c8b9748730d1fe should fix this


Use builtin UUID type for uuid format in schemas

Formats such as "email", "uuid", and so on, MAY be used even though undefined by this specification.
— Specification

The builtin UUID type is already Codable, so unless I'm missing something this should just work.
import Foundation

struct Model: Codable {
    let id: UUID
}

let json = """
{
    "id": "f44d74e7-a8ca-4d5d-9d7d-6b28fc28b552"
}
"""

let decoder = JSONDecoder()
let decoded = try! decoder.decode(Model.self, from: json.data(using: .utf8)!)

let encoder = JSONEncoder()
let encodedData = try! encoder.encode(decoded)
let encodedString = String(data: encodedData, encoding: .utf8)

Looks good, thanks @PhilipTrauner. I'll review the other MR later today too.


Calamares Installer: include config in package

Describe the bug
When i try to run the program from the package it fails:
[nix-shell:~/.cache/nixpkgs-review/pr-161788]$ results/calamares/bin/calamares
19:21:22 [1]: static Calamares::Settings* Calamares::Settings::init(bool)
    ERROR: Cowardly refusing to continue startup without settings.
     "/nix/store/j14061yzi80b78yi93i9ld4rzy5q2ib5-calamares-3.2.56/etc/calamares/settings.conf"
     "/nix/store/j14061yzi80b78yi93i9ld4rzy5q2ib5-calamares-3.2.56/share/calamares/settings.conf"
19:21:22 [1]: static Calamares::Settings* Calamares::Settings::init(bool)
    ERROR: FATAL: none of the expected configuration file paths exist.

Can we include our config, so we can just start it from the current system to see if it starts? That would help with review of further updates.
Steps To Reproduce
Steps to reproduce the behavior:

...
...
...

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
@vlinkz
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Maybe it would be a better idea to include extensions as an extra source for the calamares package rather than a separate package? But for testing purposes, you can always run results/calamares/bin/calamares -d with an appropriate settings.conf in the current directory. Definitely not ideal right now

Can a default config be added that it starts? Would that cause issues?

By default, calamares doesn't include any settings.conf file as that is meant for distros to do themselves. It is possible to add one by creating yet another patch, but even so, if we wanted NixOS branding and module, you still need the extensions to be installed. So I'm not sure what would be suitable to put in such a default config. Although one thing that I do plan on fixing is that right now even with calamares-nixos, it won't detect all the correct paths unless installed as a system package. I could probably use the NIX_PROFILES env var to correctly search more paths

I thought if we should use the calamares package as our installer, but maybe someone want to make their own distro based on NixOS and Calamares. So it makes sense to separate it.
Maybe you can add a very simple example.conf and add it to share?

I think it would make more sense to not have a configuration in by default, since if a person wants to use the calamares package for their own distro, they should probably create a package similar to calamares-nixos-extensions that contains the configs a branding for their distro. Also I'm not opposed to adding a default configuration, but since it's not part of upstream calamares' build by default, I'm not too enthusiastic about adding more custom patches to the base package. Maybe it would make more sense to have calamares-nixos have calamares-nixos-extensions as a depencency or something similar? That way someone could install that one packages, test and see how it works, and then make their own based off of that

since it's not part of upstream calamares' build by default, I'm not too enthusiastic about adding [default config]

that's fine

Maybe it would make more sense to have calamares-nixos have calamares-nixos-extensions as a depencency or something similar?

that sounds good if it helps to have one package you can install and run


[FeatureRequest] Set Number of Workers to #Cores by default.

Describe the request: A clear and concise description.
More context: https://github.com/Azure/azure-functions-host/pull/6806#issuecomment-712384756
Related to: https://github.com/Azure/azure-functions-host/issues/6671

Potential Dependency: https://github.com/Azure/azure-functions-host/issues/6704

Potential Dependency: https://github.com/Azure/azure-functions-host/issues/6704

Closing this as an internal feature in preview now dynamically sets the worker count.


Use different user agent for every request in Google provider

We are still blocked but to avoid being blocked in the future we should change User-Agent at least
@business-factory/pythonistas

@martinvy From my experience, it requires some time to be unblocked. This is just preparation to eliminate the future possibility of blocking by Google.
We were hitting Google quite a lot maybe we should distribute the requests sent to Google in a time. I mean add some sleep time between requests. What do you think?

@Joozty It's difficult to do something when we are blocked at the moment. You can see that I disabled (commented out) Google provider weeks ago so I could try if they unblock us after some time, but while I was doing review for this PR yesterday I saw that we are still blocked so I don't know. I think our IP addresses are blocked.


re_encoded interface

Right now users cannot implement the same interfaces possible in the library, because they have no re-encoding functions. We might consider adding
template< class CharSet = grammar::all_chars_t >
std::size_t
re_encoded_size(
    pct_string_view const& s,
    encode_opts const& opt,
    CharSet const& allowed = {} ) noexcept;

and
template<
  class CharSet = grammar::all_chars_t,
  class StringToken = string_token::return_string >
typename StringToken::result_type
re_encode(
    pct_string_view const& s,
    encode_opts const& opt,
    CharSet const& allowed = {},
    StringToken&& token = {} ) noexcept;

Unfortunately this API doesn't work because StringToken can't capture the needs of writing to a char buffer

Closing this for now until there is user demand.


Error: Can't resolve $ref relative to current document

When trying to generate Qraft services, I'm getting the following error with $ref relative to current document.
e.g.
 ✘  Can't resolve $ref: ENOENT: no such file or directory '/app/docs/#components/schemas/GlobalPagination'
Can't resolve $ref: ENOENT: no such file or directory '/app/docs/#components/schemas/GlobalPagination' Error: Can't resolve $ref: ENOENT: no such file or directory '/app/docs/#components/schemas/GlobalPagination'
    at validateAndBundle (file:///.npm/_npx/09ac6d5fc70ce7ef/node_modules/openapi-typescript/dist/lib/redoc.js:124:23)
    at async readSchema (file:///.npm/_npx/09ac6d5fc70ce7ef/node_modules/@openapi-qraft/cli/dist/lib/open-api/readSchema.js:9:20)
    at async writeOpenAPIServices (file:///.npm/_npx/09ac6d5fc70ce7ef/node_modules/@openapi-qraft/cli/dist/writeOpenAPIServices.js:13:20)
    at async Command.<anonymous> (file:///.npm/_npx/09ac6d5fc70ce7ef/node_modules/@openapi-qraft/cli/dist/bin.js:32:5)

Example snippet in my openapi file:
  /breadcrumbs/page/:
    get:
      summary: Returns paginated breadcrumbs
      tags:
        - Breadcrumbs
      responses:
        "200":
          description: A JSON object
          content:
            application/json:
              schema:
                type: object
                properties:
                  breadcrumbs:
                    type: array
                    description: a list of breadcrumbs from the segment
                    items:
                      $ref: "#/components/schemas/Breadcrumb"
                  pagination:
                    $ref: "#components/schemas/GlobalPagination"
        "403":
          $ref: "#/components/responses/403Forbidden"

Hi, @moonray, thank you for the first issue! 🎉
According to the spec, it looks like the syntax $ref: "#components/schemas/GlobalPagination" is invalid. Are you sure the / character is not missing after the #?

@moonray, btw, the better guide currently exists only for the @openapi-qraft/react  package.
This may not be obvious if you only use the README for @openapi-qraft/cli


Improve styling

Add Frontend via CSS

We should use something like Tailwind CSS as it makes styling easier and comes with a design system built in

Styles are for the most part done. Closing. If there are issues with styling on pages they should be opened separately.


Fix serializing all stack trace frames

What does this PR do?
closes #1570
Checklist

[ ] This is an enhancement of existing features, or a new feature in existing plugins

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] I have made corresponding changes to the documentation

[x] This is a bugfix

[x] I have updated CHANGELOG.asciidoc
[x] I have added tests that would fail without this fix

[ ] This is a new plugin

[ ] I have updated CHANGELOG.asciidoc
[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated supported-technologies.asciidoc
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.

[ ] This is something else

[ ] I have updated CHANGELOG.asciidoc

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1571 opened

Reason: Aborted from #2

Start Time: 2020-12-15T15:48:19.510+0000

Duration: 6 min 53 sec

Commit: eafa59447ceb30d7b678b0686209e369c1e93f22

Log output
Expand to view the last 100 lines of log output

[2020-12-15T15:51:26.395Z]  > git config core.sparsecheckout # timeout=10
[2020-12-15T15:51:26.400Z]  > git checkout -f eafa59447ceb30d7b678b0686209e369c1e93f22 # timeout=15
[2020-12-15T15:51:26.620Z]  > git remote # timeout=10
[2020-12-15T15:51:26.628Z]  > git config --get remote.origin.url # timeout=10
[2020-12-15T15:51:26.641Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-15T15:51:26.642Z]  > git merge 81688c7f993bd460f87d6aa3ccfe18f39f393ffc # timeout=10
[2020-12-15T15:51:26.653Z]  > git rev-parse HEAD^{commit} # timeout=10
[2020-12-15T15:51:26.661Z]  > git config core.sparsecheckout # timeout=10
[2020-12-15T15:51:26.665Z]  > git checkout -f eafa59447ceb30d7b678b0686209e369c1e93f22 # timeout=15
[2020-12-15T15:51:30.567Z] Commit message: "Fix serializing all stack trace frames"
[2020-12-15T15:51:30.567Z] First time build. Skipping changelog.
[2020-12-15T15:51:30.590Z]  > git --version # timeout=10
[2020-12-15T15:51:30.603Z]  > git --version # 'git version 2.17.1'
[2020-12-15T15:51:30.615Z] fatal: bad object 50f7a67166559b6e9f54232c1d84613679b1ea55
[2020-12-15T15:51:31.837Z] Masking supported pattern matches of $JOB_GCS_BUCKET or $NOTIFY_TO
[2020-12-15T15:51:31.909Z] Timeout set to expire in 1 hr 0 min
[2020-12-15T15:51:31.939Z] The timestamps step is unnecessary when timestamps are enabled for all Pipeline builds.
[2020-12-15T15:51:32.251Z] [INFO] Number of builds to be searched 10
[2020-12-15T15:51:32.565Z] [INFO] 'shallow' is forced to be disabled when running on PullRequests
[2020-12-15T15:51:32.588Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1571/src/github.com/elastic/apm-agent-java
[2020-12-15T15:51:32.627Z] [INFO] gitCheckout: Checkout SCM PR-1571 with some customisation.
[2020-12-15T15:51:32.660Z] [INFO] Override default checkout
[2020-12-15T15:51:32.725Z] Sleeping for 10 sec
[2020-12-15T15:51:42.855Z] using credential 2a9602aa-ab9f-4e52-baf3-b71ca88469c7-UserAndToken
[2020-12-15T15:51:42.955Z] Cloning the remote Git repository
[2020-12-15T15:51:42.969Z] Cloning repository https://github.com/elastic/apm-agent-java.git
[2020-12-15T15:51:42.990Z]  > git init /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1571/src/github.com/elastic/apm-agent-java # timeout=10
[2020-12-15T15:51:42.995Z] Using reference repository: /var/lib/jenkins/.git-references/apm-agent-java.git
[2020-12-15T15:51:42.995Z] Fetching upstream changes from https://github.com/elastic/apm-agent-java.git
[2020-12-15T15:51:42.996Z]  > git --version # timeout=10
[2020-12-15T15:51:43.010Z]  > git --version # 'git version 2.17.1'
[2020-12-15T15:51:43.010Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-15T15:51:43.011Z]  > git fetch --tags --progress -- https://github.com/elastic/apm-agent-java.git +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-12-15T15:51:43.558Z]  > git config remote.origin.url https://github.com/elastic/apm-agent-java.git # timeout=10
[2020-12-15T15:51:43.562Z]  > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
[2020-12-15T15:51:43.575Z]  > git config remote.origin.url https://github.com/elastic/apm-agent-java.git # timeout=10
[2020-12-15T15:51:43.583Z] Fetching upstream changes from https://github.com/elastic/apm-agent-java.git
[2020-12-15T15:51:43.583Z] using GIT_ASKPASS to set credentials GitHub user @apmmachine User + Personal Access Token
[2020-12-15T15:51:43.584Z]  > git fetch --tags --progress -- https://github.com/elastic/apm-agent-java.git +refs/pull/1571/head:refs/remotes/origin/PR-1571 +refs/heads/master:refs/remotes/origin/master # timeout=10
[2020-12-15T15:51:44.114Z] Checking out Revision 2e266eac944c68131c9dd9f152cbb727f1c6bac4 (origin/PR-1571)
[2020-12-15T15:51:44.293Z] Commit message: "Add changelog"
[2020-12-15T15:51:44.293Z] First time build. Skipping changelog.
[2020-12-15T15:51:44.308Z]  > git --version # timeout=10
[2020-12-15T15:51:44.312Z]  > git --version # 'git version 2.17.1'
[2020-12-15T15:51:44.318Z] fatal: bad object 50f7a67166559b6e9f54232c1d84613679b1ea55
[2020-12-15T15:51:44.108Z]  > git rev-parse origin/PR-1571^{commit} # timeout=10
[2020-12-15T15:51:44.117Z]  > git config core.sparsecheckout # timeout=10
[2020-12-15T15:51:44.121Z]  > git checkout -f 2e266eac944c68131c9dd9f152cbb727f1c6bac4 # timeout=10
[2020-12-15T15:51:45.316Z] Masking supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD
[2020-12-15T15:51:45.920Z] + git fetch<EMAIL_ADDRESS>+refs/pull/*/head:refs/remotes/origin/pr/*
[2020-12-15T15:51:46.933Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1571/src/github.com/elastic/apm-agent-java/.git
[2020-12-15T15:51:46.975Z] Archiving artifacts
[2020-12-15T15:51:47.708Z] + git rev-parse HEAD
[2020-12-15T15:51:48.075Z] + git rev-parse HEAD
[2020-12-15T15:51:48.387Z] + git rev-parse origin/pr/1571
[2020-12-15T15:51:48.443Z] [INFO] githubEnv: Found Git Build Cause: pr
[2020-12-15T15:51:48.735Z] Masking supported pattern matches of $GITHUB_TOKEN
[2020-12-15T15:51:49.679Z] [WARN] githubApiCall: The REST API call https://api.github.com/repos/elastic/apm-agent-java/pulls/1571/reviews return 0 elements
[2020-12-15T15:51:49.746Z] [INFO] githubPrCheckApproved: Title: Fix serializing all stack trace frames - User: felixbarny - Author Association: MEMBER
[2020-12-15T15:51:52.780Z] Stashed 3446 file(s)
[2020-12-15T15:51:52.831Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1571/src/github.com/elastic/apm-agent-java
[2020-12-15T15:51:53.200Z] + git diff --name-only origin/master...2e266eac944c68131c9dd9f152cbb727f1c6bac4
[2020-12-15T15:51:53.270Z] [INFO] isGitRegionMatch: not found with regex [.*\.(asciidoc|md)]
[2020-12-15T15:51:56.127Z] + cp -rf /var/lib/jenkins/.m2/repository .m2
[2020-12-15T15:52:14.546Z] + du -hs .m2
[2020-12-15T15:52:14.546Z] 794M	.m2
[2020-12-15T15:52:14.574Z] Running in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1571/src/github.com/elastic/apm-agent-java
[2020-12-15T15:52:14.891Z] + ./mvnw -q dependency:go-offline --fail-never
[2020-12-15T15:52:14.891Z] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8
[2020-12-15T15:52:15.461Z] Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
[2020-12-15T15:52:15.461Z] Maven home: /var/lib/jenkins/.m2/wrapper/dists/apache-maven-3.6.3-bin/1iopthnavndlasol9gbrbg6bf2/apache-maven-3.6.3
[2020-12-15T15:52:15.461Z] Java version: 11.0.6, vendor: Oracle Corporation, runtime: /var/lib/jenkins/.java/oracle-11.0.6+8-linux
[2020-12-15T15:52:15.461Z] Default locale: en_US, platform encoding: UTF8
[2020-12-15T15:52:15.461Z] OS name: "linux", version: "5.4.0-1030-gcp", arch: "amd64", family: "unix"
[2020-12-15T15:53:51.430Z] Sending interrupt signal to process
[2020-12-15T15:54:06.426Z] Click here to forcibly terminate running steps
[2020-12-15T15:54:06.972Z] script returned exit code 143
[2020-12-15T15:54:08.648Z] Stage "Tests" skipped due to earlier failure(s)
[2020-12-15T15:54:08.863Z] Stage "Unit Tests" skipped due to earlier failure(s)
[2020-12-15T15:54:08.878Z] Stage "Smoke Tests 01" skipped due to earlier failure(s)
[2020-12-15T15:54:08.893Z] Stage "Smoke Tests 02" skipped due to earlier failure(s)
[2020-12-15T15:54:08.908Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-12-15T15:54:08.924Z] Stage "Javadoc" skipped due to earlier failure(s)
[2020-12-15T15:54:09.153Z] Failed in branch Unit Tests
[2020-12-15T15:54:09.166Z] Failed in branch Smoke Tests 01
[2020-12-15T15:54:09.178Z] Failed in branch Smoke Tests 02
[2020-12-15T15:54:09.191Z] Failed in branch Benchmarks
[2020-12-15T15:54:09.203Z] Failed in branch Javadoc
[2020-12-15T15:54:09.533Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-12-15T15:54:09.646Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-12-15T15:54:09.698Z] Stage "AfterRelease" skipped due to earlier failure(s)
[2020-12-15T15:54:11.062Z] Running on worker-1095690 in /var/lib/jenkins/workspace/_java_apm-agent-java-mbp_PR-1571
[2020-12-15T15:54:11.211Z] [INFO] getVaultSecret: Getting secrets
[2020-12-15T15:54:11.464Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-12-15T15:54:13.994Z] + chmod 755 generate-build-data.sh
[2020-12-15T15:54:13.994Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1571/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1571/runs/1 ABORTED 353015
[2020-12-15T15:54:13.994Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1571/runs/1/steps/?limit=10000 -o steps-info.json
[2020-12-15T15:54:14.717Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-java/apm-agent-java-mbp/PR-1571/runs/1/tests/?status=FAILED -o tests-errors.json
[2020-12-15T15:54:15.443Z] Retry 1/3 exited 22, retrying in 1 seconds...
[2020-12-15T15:54:16.943Z] Retry 2/3 exited 22, retrying in 2 seconds...

Codecov Report

Merging #1571 (2e266ea) into master (81688c7) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #1571      +/-   ##
============================================
+ Coverage     58.98%   58.99%   +0.01%
  Complexity       92       92
============================================
  Files           391      391
  Lines         17615    17617       +2
  Branches       2436     2437       +1
============================================
+ Hits          10390    10394       +4
  Misses         6508     6508
+ Partials        717      715       -2

Impacted Files
Coverage Δ
Complexity Δ

.../apm/agent/report/serialize/DslJsonSerializer.java
89.19% <100.00%> (+0.14%)
0.00 <0.00> (ø)

...ic/apm/agent/profiler/collections/LongHashSet.java
16.66% <0.00%> (-1.20%)
0.00% <0.00%> (ø%)

.../bci/bytebuddy/SoftlyReferencingTypePoolCache.java
93.75% <0.00%> (+12.50%)
0.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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


Ensure custom extension names end in '-ext'

Fixes #127.

Codecov Report

Merging #139 into master will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #139      +/-   ##
==========================================
+ Coverage   94.00%   94.07%   +0.07%
==========================================
  Files          61       61
  Lines        5717     5722       +5
==========================================
+ Hits         5374     5383       +9
+ Misses        343      339       -4

Impacted Files
Coverage Δ

stix2validator/test/v21/observed_data_tests.py
100.00% <100.00%> (ø)

stix2validator/v21/musts.py
67.07% <100.00%> (+0.20%)
:arrow_up:

stix2validator/v21/shoulds.py
91.07% <100.00%> (ø)

stix2validator/validator.py
89.32% <0.00%> (+0.56%)
:arrow_up:

stix2validator/errors.py
87.94% <0.00%> (+1.41%)
:arrow_up:

Continue to review full report at Codecov.

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


Bar labels only show integers but floats

Hi. Thank you for developing it.
I need to show percentages next to the bars but it only showed integers rather than floats. Can you add an option to change the format?
Also, the ticks have no shading color and they will overlie each other when they meet and people can see neither. Can you add shading color so people can see at least one of them? Thank you.

Yes! I made this change in #16. New release coming soon (next week).


[✨] Update your template to include eslint.config.js by default

Is your feature request related to a problem?
Yes. I used npm create qwik and it created a project based on 1.5.2 version. Yet when I updated it to use eslint 9.0.0 and ran npm run build I got this error:

node:748) ESLintIgnoreWarning: The ".eslintignore" file is no longer supported. Switch to using the "ignores" property in "eslint.config.js"

Describe the solution you'd like
Please remove .eslintignore and .eslintconfig.cjs from your template and replace them with a single eslint.config.js.
Describe alternatives you've considered
Right now we should manually do this in every project.
Additional context
No response

@gioboa, I'm sorry I don't know how to do that.

let me try it

Will this bug from v1 be merged into v2?

Yep, it will be merged. Thanks for your help @JerryWu1234

because the eslint 9.0 was a breaking change version, and I have used this library @eslint/eslintrc which the official have offered for migrate to v9.0,
But it's still unstable
https://github.com/eslint/eslintrc/issues/158

I think we should use the ts one that helps with the types https://typescript-eslint.io/getting-started/

BTW @JerryWu1234 you need to rename your file to .cjs or it won't work in type:module projects. And maybe you should make it ESM with .mjs, but then __dirname needs to be replaced with the equivalent import.meta statement

I think we should use the ts one that helps with the types https://typescript-eslint.io/getting-started/

we just upgrade the Eslint's grade. and follow this doc  don't you?,
So why we have to refer a new library?

BTW @JerryWu1234 you need to rename your file to .cjs or it won't work in type:module projects. And maybe you should make it ESM with .mjs, but then __dirname needs to be replaced with the equivalent import.meta statement

I tried both ways, it's still wrong.

https://github.com/typescript-eslint/typescript-eslint/issues/8211
still going on

yup it would be awesome to convert those two files into one


Fix typo in Office KMS docs - "active" -> "activate"

Just a minor grammatical typo I happened to notice while skim reading the docs!

@jamesorlakin -- thanks for catching and fixing that.


Various audit fixes

Contributing to homebrew-xorg:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Does your submission pass
brew audit --strict <formula> (where <formula> is the name of the formula you're submitting)?
[x] Have you built your formula locally prior to submission with brew install <formula>?

This fixes the audits for a number of formulae.
I didn't get all the fixes necessary, but I got as many as I felt reasonable to do at once.

Various errors from Travis:

configure: error: C compiler cannot create executables

The problem here appears to be with GCC. To speed up this build, I think we should probably bottle check in core, but that wouldn't solve the problem for libice.

check has been bottled in https://github.com/Linuxbrew/homebrew-core/pull/1193. To speed things up here, I also cherry-picked two trivial commits from here into master and just pushed them.
Rebasing and then will try again.

LGTM. Why do you not merge it? The errors are cause by mesa (actually, its patch) so feel free to merge these changes.


Add runtime repo (portable and non-portable) and build in master

Note: Setting known-good to build through runtime - coreclr.

FYI @crummel @dagood @adaggarwal - this should be ready for review.


64KiB Server request limit

It seems the server has a hardcoded 64KiB limit. This isn't actually a problem because it should be possible to override it at least that's what the comment says at
https://github.com/reactphp/http/blob/master/src/Server.php#L180
But if I read the code correctly it's not possible to override this 64 KiB limit.
Looking at https://github.com/reactphp/http/blob/master/src/Server.php#L335 the limit will never exceed the MAXUM_BUFFER_SIZE
Do I missed something?
The only way to overcome this limit is to use the streaming interfaces, if this is right then the comment should be changed.

Hmm you might actually be right. Will have a look why this slipped past our tests and how to fixed it in both the code and tests 👍

While debugging this it was hard to find out why I got an empty body, may it would sense to set an attribute to the request when the body is truncated?

@HLeithner Thanks for bringing this up. There is indeed a default 64 KiB limit as described in the documentation.

In order to override the above buffering defaults, you can configure the Server explicitly. You can use the LimitConcurrentRequestsMiddleware and RequestBodyBufferMiddleware (see below) to explicitly configure the total number of requests that can be handled at once like this:
$server = new React\Http\Server(
    new React\Http\Middleware\StreamingRequestMiddleware(),
    new React\Http\Middleware\LimitConcurrentRequestsMiddleware(100), // 100 concurrent buffering handlers
    new React\Http\Middleware\RequestBodyBufferMiddleware(2 * 1024 * 1024), // 2 MiB per request
    new React\Http\Middleware\RequestBodyParserMiddleware(),
    $handler
);

– https://github.com/reactphp/http#server

I believe this has been answered, so I'm closing this for now. Please come back with more details if this problem persists and we can always reopen this :+1:

@clue please look again on the linked code lines, there are 2 bugs in React\Http\Server

in the documentation that you could override RequestBodyBufferMiddleware which is actually not true.
in getMaxRequestSize which has a broken if statement.

in the documentation that you could override RequestBodyBufferMiddleware which is actually not true.

Have you checked my above code snippet? This should be covered by the existing test suite. Note that this requires a StreamingRequestMiddleware as given above.

in getMaxRequestSize which has a broken if statement

Can you elaborate? This has 100% code coverage, but if you feel a specific case isn't covered adequately, perhaps add an additional test case? :+1:

Ok I missed the Streaming Middleware but it looks like a shady workaround.
I checked the documentation about the post_max_size ini were 64KiB capped is intended. I'm not sure why I'm not allowed to shoot my self in the foot by specifying a bigger ini setting then 64KiB especially when there is a documentation I can do it working around the well tested code.
But yes you are right the function does what it should. thx

Ok I missed the Streaming Middleware but it looks like a shady workaround.

I understand where you're coming from, but from experience I would argue that this works good enough. If you feel there's any way to improve this, PRs are very much appreciated! :+1:

I checked the documentation about the post_max_size ini were 64KiB capped is intended. I'm not sure why I'm not allowed to shoot my self in the foot by specifying a bigger ini setting then 64KiB especially when there is a documentation I can do it working around the well tested code.

I understand where you're coming from and I think we agree that defaults should be sane. However, the post_max_size is really designed for a non-concurrent execution and for obvious reasons doesn't take into account that multiple requests may occur at the same time. That's why we've decided to cap this by default to allow higher concurrency in favor of bigger uploads by default. See https://github.com/reactphp/http/pull/371, https://github.com/reactphp/http/issues/334, https://github.com/reactphp/http/issues/335, https://github.com/reactphp/http/issues/336 and others.

I see Limiting can be improved on all layers also looking at #411
Thanks for you time and we will see what the future brings, maybe some more dynamic limiting Middleware which can automatically balance between requests and size and maybe park requests or deny them based on server load.

Thanks for you time and we will see what the future brings, maybe some more dynamic limiting Middleware which can automatically balance between requests and size and maybe park requests or deny them based on server load.

Agreed, see also #255 if you're looking for ways to contribute to this project :+1:


Memory leak

Hello
I have an issue with pub/sub model. I have one publisher that listen to ip:5556 and 4 workers(subs) that dial to ip:5556. After few hour of test work the usage of used memory increased. Can You please recommend me how can I solve such problem?
My code
type Publisher struct {
sync.RWMutex
pub mangos.Socket
}
func GatherSyncData(ip string, cache *ccache.Cache) {
subscriber := GetSubscriber(ip)

for {
	subscriber.Lock()
	message, err := subscriber.pub.Recv()
	subscriber.Unlock()
	if err != nil {
		log.Println(err)
		continue
	}

	go SeveSyncUUID(string(message), cache)
}

}
func SeveSyncUUID(msg string, cache *ccache.Cache) {
glink := strings.Split(msg, "|")

cache.Set(glink[0], glink[1], time.Minute*10)

}
func GetPublisher() Publisher {
socket, err := pub.NewSocket()
if err != nil {
	log.Println(err)
	return Publisher{pub: nil}
}

socket.AddTransport(tcp.NewTransport())
err = socket.Listen(fmt.Sprintf("tcp://%s:5556", *ip))

if err != nil {
	log.Println(err)
	return Publisher{pub: nil}
}

socket.SetOption(mangos.OptionSendDeadline, time.Second*1)

return Publisher{pub: socket}

}
func GetSubscriber(worker string) Publisher {
socket, err := sub.NewSocket()
socket.SetOption(mangos.OptionSubscribe, []byte(worker))
if err != nil {
	log.Println(err)
	return Publisher{pub: nil}
}

socket.AddTransport(tcp.NewTransport())
err = socket.Dial(fmt.Sprintf("tcp://%s:5556", worker))

if err != nil {
	log.Println(err)
	return Publisher{pub: nil}
}
return Publisher{pub: socket}

}

It looks to me like SeveSyncScreen is responsible for leaking the strings into the cache?
Other than that, do you have any more data about what data you think is leaking?

I have checked everything one more time. Everything seems right. But I have one more question about connections. My pub/sub code now working infinitely. After starting of pub and subs they are newer close and unsubscribe because there are approximately 500 messages per second. Is it right for keeping connection forever. Can it be a cause of memory leak?

sorry didnt see this. yes we keep the connection open until one of the
sides closes it. no this isnt a leak.
On Fri, May 26, 2017 at 2:55 AM Arhius<EMAIL_ADDRESS>wrote:

I have checked everything one more time. Everything seems right. But I
have one more question about connections. My pub/sub code now working
infinitely. After starting of pub and subs they are newer close and
unsubscribe because there are approximately 500 messages per second. Is it
right for keeping connection forever. Can it be a cause of memory leak?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/go-mangos/mangos/issues/276#issuecomment-304241532,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABPDfe8Rp2mC-9KJII5o_6Tz6CFyv8x6ks5r9qGJgaJpZM4NlL5-
.

You might also look at https://github.com/go-mangos/mangos/pull/285
I think that PR found some actual leaks.  Not sure if you're seeing that or not, but I hope to merge that today.

I'm closing this -- it's not a bug.