chore(spec): add spec docs for config, alerts, and dashboards

Also fixed dashboard validation issues in all packs

Looks great overall! Can you add the character limits to fields like description and short-description? Since we haven't locked in image file types, I'm fine with not listing them here for now.

@aswanson-nr I added limits in utils/schema/main_config.json (and filled out more of the main config schema)

I split the dashboard fixes out into #95


Insert components inside mwc-top-app-bar

Is your feature request related to a problem? Please describe.
Can be really helpfull to add a component inside the mwc-top-app-bar one. At this moment its "only" possible to add a text using the "title" slot. When i try to add a mwc-select, the style has completly broken, hidding the floating list when i clicked over it.
Describe the solution you'd like
The mwc-top-app-bar component should support web components inside "title" slot (or a new one) to allow create top-app-bars like the Google Drive's one.
Describe alternatives you've considered
I was try to add all kind of custom components inside "title" slot. Some of these works pretty well (like mwc-button), but its more frequent that the style breaks inside the aforementioned slot.
Additional context
None.

I'll take a look to see what type of content should be allowed in the Top App Bar.


Split pyrobosim_ros and pyrobosim_msgs packages into separate repos

This PR moves the pyrobosim_ros and pyrobosim_msgs packages into a separate repo (https://github.com/sea-bass/pyrobosim_ros), including them back here as submodules.
This will facilitate creating releases that officially work within the ROS 2 ecosystem. See

https://github.com/ros/rosdistro/pull/42205
https://github.com/sea-bass/pyrobosim_ros/issues/1

Also updating the release to 3.0.0 as this is the last of the big changes before I try cutting a major release.

@DLu what do you think?

Submodules, my oldest and dearest friend.
So functionally this is fine, I did a quick sanity check and the docs updates look good! But dumb question - is this out of necessity or desire for separation? What exactly is going to break in the bloom process if you just kept this as folders/subfolders?

Hmm... you're right. Maybe we can just keep it all here and still go through the whole release process.
There are still a few places in the pyrobosim_ros/CMakeLists.txt where we're currently pointing to source code in other folders, but as I found yesterday that's not necessary. So we can at least delete that part and keep the repo as is.
Let me sleep on it for a bit, but great point, as I would love to not have to maintain two separate repos.

OK yeah let's not do this. Good bye, PR, and thanks again @eholum!

Lol. Always happy to have my ignkre


Adding animation to the Features section when scrolled down

Adding animation to the Features section when scrolled down.
Let me assign this issue under GSSoC'23.

Are you up for the issue?


adds Dataset for SmsWsj

This pull request adds a Dataset for the SMS_WSJ database. This is a first step in implementing a neural network based example.

Why do the earlystopping PR appear?
Did you merge upstream/master into your branch?

Why do the earlystopping PR appear?
Did you merge upstream/master into your branch?

Oh yes it looks like it, strange. If necessary, I can try to remove the merge from the pull request history.

It's not necessary, thanks.
Is it ready to merge on your end?

It's not necessary, thanks.
Is it ready to merge on your end?

yes, I am happy with the current status. I will start working on a DC example on SMS-WSJ as soon as the dataset is merged.

Merging then, thanks !


Reflect PEGTL api change .content() -> .string()/.string_view()

See PEGTL commit: 7b9d65ded23fe3ccc7ca645f3af73bfe60ae725c
https://github.com/taocpp/PEGTL/commit/7b9d65ded23fe3ccc7ca645f3af73bfe60ae725c

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

Ah, I should mention in the README that I'm trying to maintain C++11 compatibility, so I'm using the 2.7.x branch of PEGTL rather than master.
I've been thinking about adopting some of the newer standards in a new major version (much like PEGTL itself), in which case this is definitely required to stay in synch with PEGTL. There are probably a lot of other spots where I could be taking advantage of string_view as well.

Thanks for the PR, I ended up merging it manually in the 3.0 branch and it no longer applies to master.


Bovine is failing all tests currently (502 errors)

@HelgeKrueger any ideas what the cause of the downtime is? We'd love to keep bovine on the list.
Thanks!
🎩

Should be fixed now. I had to restart the server for it.
Thanks for telling me.


Update README.md

Hi, thanks you for think this tools is useful and contribute this awesome PKGBUILD!
could you please use latest master?  because some changes are proposed.

i bump version to 0.6.3
because i forget change to output the correct version when use translater -v.
make release,  will skip the development dependencies,  i will save 1 minute to install/postinstall ameba. which is not necessary for build release.

Installing ameba (1.6.1)
Postinstall of ameba: shards build -Dpreview_mt


Add axolotl atlas to the list of available atlases

Of course I forgot to add this despite your reminder :laughing: thank you!


BulkWriter auto flushes once _maxBatchSize is exceeded, even without .close()

Environment details

OS: Mac OSX Catalina
Node.js version: 14.15.3
npm version: 6.14.9
@google-cloud/firestore version: 4.8.0

The _maxBatchSize of BulkWriter is 20, and it seems that when more than 20 operations are added to a BulkWriter they auto-flush and commit the changes at some point, even when the script does not explicitly call .close() or .flush(). This is problematic because errors could be thrown in between operations being added and the commits will still take place.
Steps to reproduce

In a node firebase function, create an instance of BulkWriter const bulk = admin.firestore().bulkWriter()
Add 20 various operations to the BulkWriter (set, create, update, delete)
Never call .close() or .flush() and let script finish. No operations are committed.
Update script with a 21st operation and rerun it without calling .close() or .flush()
The first 20 operations will have committed, but the 21st will not have

It seems that there should be a clear intention to commit before allowing these to be auto-flushed, especially if a script were to error, timeout, or the logic intended to not commit for some reason. The desirable behavior would be instead to go along adding operations to the BulkWriter and, if .close() never gets called in the script, the operation promises are never committed.

@cvharris Thanks for writing in!
The flush() and close() methods are intended for developers to wait for writes to complete. Though flush() and close() send existing batches, BulkWriter purposely allows writes to be automatically sent on their own. The design of BulkWriter prioritizes automatically sending writes as they are enqueued, similar to other streaming APIs. Firestore automatically sends writes in batches of 20 to optimize throughput in the underlying backend API (which explains why the first 20 writes are buffered), but the intention is to batch and send writes as soon as they are made.
If you want to batch writes manually and send them conditionally based on the success or failure of other writes, I recommend you use the WriteBatch API. Since this is WAI, I'm going to mark this feature as closed, but please feel free to ask any other questions you may have!

@cvharris Thanks for writing in!
The flush() and close() methods are intended for developers to wait for writes to complete. Though flush() and close() send existing batches, BulkWriter purposely allows writes to be automatically sent on their own. The design of BulkWriter prioritizes automatically sending writes as they are enqueued, similar to other streaming APIs. Firestore automatically sends writes in batches of 20 to optimize throughput in the underlying backend API (which explains why the first 20 writes are buffered), but the intention is to batch and send writes as soon as they are made.
If you want to batch writes manually and send them conditionally based on the success or failure of other writes, I recommend you use the WriteBatch API. Since this is WAI, I'm going to mark this feature as closed, but please feel free to ask any other questions you may have!


Ambiguous steps ruin reporting

Summary
When ambiguous steps are encountered, Cucumber essentially crashes. No reports are generated and no other tests executed. It just dies.
Expected Behavior
All tests should be run and output generated as normal. Some tests might fail/be skipped/have undefined steps, etc. but they will at least get executed.
Current Behavior
As soon as an ambiguous step is encountered, Cucumber declares the ambiguity and then stops. It does not proceed to the next step or even output the results of the run. Using --guess will, naturally, remove this problem but the idea is to have failures due to ambiguous steps (e.g. when using --strict) be handled in a similar way to pending or undefined steps. That is to say, usefully.

Possible Solution
If I recall correctly, it didn't use to be this way and ambiguous steps were handled similarly to undefined/pending steps. Why did that change?

Steps to Reproduce (for bugs)

Have a test with ambiguous steps
Run it
Watch Cucumber fail to fail gracefully

Here is a gist that will trigger the problem (run it one with --guess and once without in order to see the difference)
https://gist.github.com/enkessler/f351c4fd83f1b621789ad1d22cecb369
Context & Motivation
Ambiguous steps happen. Breaking the build happens. However, even a broken build needs useful output but ambiguous steps completely ruin that possibility by crashing the suite immediately.
Your Environment

Version used: 2.4.0
Operating System and version: OSX
Link to your project: N/A (private)

Thanks for reporting @enkessler. Do you have time to add a scenario into our acceptance tests that reproduces this? That would be the first step to fixing it.

@mattwynne I'm a little short on time but I'll try. I've got some other projects to maintain and I'm trying to get them all ready for when I show up to CukenFest.

Cucumber-JS as "ambiguous" as a separate result type, which neither Cucumber-Ruby nor Cucumber-JVM have.

Step 1. Shamelessly steal from Cucumber-JS.
Step 2. Get it working in Ruby
Step 3. Profit.
:)

Step 0: Make the build work on Windows.
:(

Step 0: Make the build work on Windows.

Can you raise a separate ticket about that?

#1115 opened. Links to the failing builds are included. Mind you, I don't necessarily know how to get them working any more than I know how to make ambiguous steps work. But, you know, I'm trying to do my part by keeping you lot informed. ;)


[Grasshopper] RevitFamilyInstance - Optional Host Input Needed

Expected Behaviour

Some components in Revit (such as doors, windows and wall/face/floor based components) expects a host for placement. Optional input for "Host" needed for this kinda components.
As discussed here👇:
https://speckle.community/t/openings-voids-in-revitfloor-and-revitwall/3005/2

Current Behaviour

Currently there is no way to add components that needs a host.
Current Behaviour

Optional input for "Host".

it works the other way around. you put element into a host as part of its elements list.

we discussed this w Alan and adding a host input would make sense for adding new host based components to existing objects in Revit. atm you can only add host based families if their host is also created via Grasshopper.

Agree, also, I believe we are not currently supporting all types of "hosted elements" properly!
A useful exercise would be to check which ones we're missing.
This could also be a potentially related issue: https://github.com/specklesystems/speckle-sharp/issues/586

Closing, we can reopen when we tackle this back


[1pt] Implement mission leaving - Actions

Follow the same logic as with the "Join mission" - but you need to set the reserved key to false.
Dispatch these actions upon click on the corresponding buttons.

https://github.com/mikemtzp/space-travelers-hub/pull/35


An undefined use case.

The 2nd use case: "Copying between a cloud data source and a data source in private network: if either source or sink linked service points to a self-hosted IR, the copy activity is executed on that self-hosted Integration Runtime" does not account for what happens if BOTH cloud and private network define a self-hosted IR. Which one is "preferred"? the cloud or the private network? Is does this use case  result in an error? (compare with the 3rd example, between 2  data sources in a private network). I would say that the cloud to private network is not robust if it cannot handle "preference

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

ID: d1a34b3c-a9b8-29ce-1eca-86f7f42981a1
Version Independent ID: 61d6e6b3-ec54-552d-1bef-86bbcbfea8ff
Content: Integration runtime - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/concepts-integration-runtime.md
Service: data-factory
Sub-service: integration-runtime
GitHub Login: @lrtoyou1223
Microsoft Alias: lle

Thank you for your detailed feedback.  We are looking into the issue, and we will respond when we have more information.

Thank you for your feedback. This has been assigned to the content owner, @lrtoyou1223 , and will be updated as appropriate.

We don't support use different SHIR in source and sink which means the case you mentioned above won't happen.

#please-close


Add "add_to_previous_results" method to UniqueGenerator

This adds an  "add_to_previous_results" method to UniqueGenerator, allowing to manually specify already used values, or excluded ones.
On a Rails app, I had collisions in the tests with manually defined values and the ones created by faker. I guess there are other use cases where having this feature could be useful.
I think the test speaks for itself:
def test_unique_with_already_set_values
  values = ('a'..'z').to_a + ('0'..'9').to_a
  @tester.unique.add_to_previous_results(:character, [], values)
  assert_raise(Faker::UniqueGenerator::RetryLimitExceeded) { @tester.unique.character }
end

[x] Rubocop
[x] Documentation
[x] New test
[x] Tests passing

I can change the method name if it's not understandable.

Perhaps this method could be renamed to exclude... that would more clearly indicate what the method does, I think.

I changed the method name and reworded the commit...


Fix serialize/unserialize issues with DatabaseStore caching and speci…

This pull request fixes PHP's issues with serialize/unserialize which are also used in the DatabaseStore caching.
The fix adds base64_encode and base64_decode as described here http://php.net/manual/en/function.serialize.php
The bug is reproduced when unserializing and special characters like ", ', :, or ; exist in any of the serialized values.

The tests are failing which indicates a breaking change

My bad. Tests are fixed. Please review.

Major breaking change.


Pretrained Weights

@OaDsis  hi thanks for sharing the wonderful work , i had few queries

can you please provide the pretrained weights on google drive or one drive
Thanks in adavance

Thanks for your attention.
I will upload the pre-trained model and the results in a few days.

Hello, I have uploaded the pre-training models, please check that.


amplifyPush from amplify.yml fails with ENOENT: no such file or directory, open 'amplify/backend/awscloudformation/build/root-cloudformation-stack.json'

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
8.4.0
What operating system are you using?
amazon linux
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
Added Admin API and pushed the changes to my dev branch.
Amplify Categories
auth
Amplify Commands
push
Describe the bug
I have added admin queries API. After that, I pushed the changes in my dev branch, and amplify console build is failing for the following error.
2022-06-12T02:58:48.817Z [WARNING]: ✔ Successfully pulled backend environment dev from the cloud.
2022-06-12T02:58:49.572Z [WARNING]: ✖ There was an error initializing your environment.
2022-06-12T02:58:49.673Z [INFO]: Failed to pull the backend.
2022-06-12T02:58:49.676Z [WARNING]: - Creating Zip
2022-06-12T02:58:49.700Z [INFO]: 🛑 ENOENT: no such file or directory, open '/codebuild/output/srcXXXXXXX/src/myproject/amplify/backend/awscloudformation/build/root-cloudformation-stack.json'
2022-06-12T02:58:49.700Z [INFO]: Error: ENOENT: no such file or directory, open '/codebuild/output/srcXXXXXXX/src/myproject/amplify/backend/awscloudformation/build/root-cloudformation-stack.json'
                                 at Object.openSync (fs.js:497:3)
                                 at Object.openSync (pkg/prelude/bootstrap.js:739:32)
                                 at Object.readFileSync (fs.js:393:35)
                                 at Object.readFileSync (pkg/prelude/bootstrap.js:1025:36)
                                 at /snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:131:132
                                 at Array.forEach (<anonymous>)
                                 at createZip (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:130:15)
                                 at zipSend (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:88:35)
                                 at reportError (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:60:15)
                                 at Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:168:46)
                                 at runMicrotasks (<anonymous>)
                                 at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-06-12T02:58:49.718Z [ERROR]: !!! Build failed
2022-06-12T02:58:49.718Z [ERROR]: !!! Non-Zero Exit Code detected

Expected behavior
amplifyPush --simple should work normally as amplify push --yes for the local environment worked successfully.
Reproduction steps
Already described above.
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

I have the same exact issue with a brand new amplify project I am setting up.

I have the same exact issue with amplify env list command after I upgraded to version 8.4.0

Hey @sky4git :wave: thanks for raising this! I was not able to reproduce this with a new app with a Lambda and Auth (+admin queries) attached to Amplify Hosting, however I do have a few follow-up questions to better understand the context:

does this only occur in the Hosting builds? are you able to run commands locally, including amplify push, without error?
can you confirm both locally and in Hosting you are using Amplify CLI 8.4.0?
any further customizations applied to the build process?
is this awscloudformation directory present in your #current-cloud-backend?

@josefaidt

does this only occur in the Hosting builds? are you able to run commands locally, including amplify push, without error? - YES. No error on amplify push command from local.
can you confirm both locally and in Hosting you are using Amplify CLI 8.4.0? - YES
any further customizations applied to the build process? - Nope
is this awscloudformation directory present in your #current-cloud-backend? - YES

I am not sure if I am supposed to be tagging along here but my answers are the same as @sky4git except I do not have a #current-clout-backend folder in my amplify directory and no matter what series of commands I have run I have never seen one generated. I was using CLI 8.4.0 in both locations but I also tried rolling back to the previous minor version in the console in an effort to debug, I got the same result. I hope this is more helpful than opening my own ticket for an identical issue.

I'm seeing this issue as well, after upgrading Amplify CLI to the latest version.

relevant: https://github.com/aws-amplify/amplify-cli/issues/10582

is there a version of the Amplify CLI that would be worth downgrading to on the Amplify Console in order to workaround this issue, at least temporarily @josefaidt?

Hey @stephenc222 can you try removing this line from your buildspec file (amplify.yml)? envCache --set stackInfo

@josefaidt sure, let me make that change and attempt a re-deploy.

@josefaidt Attempted a re-deploy, and got the same terminal error output:
2022-06-14T15:06:57.536Z [WARNING]: ✔ Successfully pulled backend environment dev from the cloud.
2022-06-14T15:06:57.810Z [WARNING]: ✖ There was an error initializing your environment.
2022-06-14T15:06:57.856Z [INFO]: Failed to pull the backend.
2022-06-14T15:06:57.858Z [WARNING]: - Creating Zip
2022-06-14T15:06:57.877Z [INFO]: 🛑 ENOENT: no such file or directory, open '/codebuild/output/src104800858/src/crypto-clamor/next_web_app/amplify/backend/awscloudformation/build/root-cloudformation-stack.json'
2022-06-14T15:06:57.877Z [INFO]: Error: ENOENT: no such file or directory, open '/codebuild/output/src104800858/src/crypto-clamor/next_web_app/amplify/backend/awscloudformation/build/root-cloudformation-stack.json'
                                 at Object.openSync (fs.js:497:3)
                                 at Object.openSync (pkg/prelude/bootstrap.js:739:32)
                                 at Object.readFileSync (fs.js:393:35)
                                 at Object.readFileSync (pkg/prelude/bootstrap.js:1025:36)
                                 at /snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:143:132
                                 at Array.forEach (<anonymous>)
                                 at createZip (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:142:15)
                                 at zipSend (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:99:35)
                                 at reportError (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/commands/diagnose.js:62:15)
                                 at Object.run (/snapshot/repo/build/node_modules/@aws-amplify/cli-internal/lib/index.js:168:46)
                                 at runMicrotasks (<anonymous>)
                                 at processTicksAndRejections (internal/process/task_queues.js:95:5)
2022-06-14T15:06:57.895Z [ERROR]: !!! Build failed
2022-06-14T15:06:57.896Z [ERROR]: !!! Non-Zero Exit Code detected
2022-06-14T15:06:57.896Z [INFO]: # Starting environment caching...
2022-06-14T15:06:57.896Z [INFO]: # Uploading environment cache artifact...
2022-06-14T15:06:57.956Z [INFO]: # Environment caching completed
Terminating logging...

I'm optimistic that this PR may solve this issue?

Hey @stephenc222 thanks for trying that out and great callout with the feature flag. Does your build still error out after bypassing the diagnosis call?

@josefaidt It does, looks like there's an error with importing my "blog" dynamodb table:
2022-06-14T15:38:06.007Z [WARNING]: ✖ There was an error initializing your environment.
2022-06-14T15:38:06.051Z [INFO]: Failed to pull the backend.
2022-06-14T15:38:06.053Z [INFO]: 🛑 storage headless expected 1 element for resource: blog, but found: 0
2022-06-14T15:38:06.054Z [INFO]: Error: storage headless expected 1 element for resource: blog, but found: 0
                                 at ensureHeadlessParameters (/snapshot/repo/build/node_modules/@aws-amplify/amplify-category-storage/lib/provider-utils/awscloudformation/import/import-dynamodb.js:406:11)
                                 at headlessImport (/snapshot/repo/build/node_modules/@aws-amplify/amplify-category-storage/lib/provider-utils/awscloudformation/import/import-dynamodb.js:360:40)
                                 at importedDynamoDBEnvInit (/snapshot/repo/build/node_modules/@aws-amplify/amplify-category-storage/lib/provider-utils/awscloudformation/import/import-dynamodb.js:260:12)
                                 at runMicrotasks (<anonymous>)
                                 at processTicksAndRejections (internal/process/task_queues.js:95:5)
                                 at async updateConfigOnEnvInit (/snapshot/repo/build/node_modules/@aws-amplify/amplify-category-storage/lib/provider-utils/awscloudformation/index.js:157:9)
                                 at async /snapshot/repo/build/node_modules/@aws-amplify/amplify-category-storage/lib/index.js:352:22
2022-06-14T15:38:06.093Z [ERROR]: !!! Build failed
2022-06-14T15:38:06.094Z [ERROR]: !!! Non-Zero Exit Code detected
2022-06-14T15:38:06.094Z [INFO]: # Starting environment caching...
2022-06-14T15:38:06.094Z [INFO]: # Uploading environment cache artifact...
2022-06-14T15:38:06.165Z [INFO]: # Environment caching completed

Ultimately - I'm going to workaround this new import issue (hopefully...) by just re-creating the table within the amplify project. For the context of this table, I don't get any value from importing this table vs creating it within the project and specific for each environment I have

Hey @stephenc222 I do see two tables with the same names in the constructed pull/init command. Are you seeing something similar in the references stored in your team-provider-info.json or backend-config.json?

This is what I see in both my backend-config.json and team-provider-info.json:
    "blog": {
      "service": "DynamoDB",
      "serviceType": "imported",
      "providerPlugin": "awscloudformation",
      "dependsOn": []
    }

@josefaidt I decided to go with an alternative approach to create the "blog" table as part of the amplify project, and not as an imported resource. From there, I was able to successfully build and deploy from the Amplify Console!
FWIW, I wonder if there's an issue with recently imported storage resources. Not sure. Thanks for your input!
Can this issue be notified when the diagnostic-related bug is fixed? I would like to opt back in to send diagnostics when future errors occur :+1:

Similar to above, this revealed the actual error that was happening behind the scenes, not sure it's at all helpful but I will post here for posterity:
                                                              ## Checking for associated backend environment...                                                                 ## Backend environment association found 2022-06-14T19:10:46.388Z [INFO]: Amplify AppID found: daaj114gsrp5i. Amplify App name is: propertytoolsio 2022-06-14T19:10:46.437Z [INFO]: Backend environment beta found in Amplify Console app: propertytoolsio 2022-06-14T19:10:47.211Z [WARNING]: - Fetching updates to backend environment: beta from the cloud. 2022-06-14T19:10:47.898Z [WARNING]: - Building resource auth/propertytoolsio19dd8f27 2022-06-14T19:10:48.035Z [WARNING]: ✔ Successfully pulled backend environment beta from the cloud. 2022-06-14T19:10:48.041Z [WARNING]: ✖ There was an error initializing your environment. 2022-06-14T19:10:48.048Z [INFO]: Failed to pull the backend. 2022-06-14T19:10:48.050Z [INFO]: 🛑 auth headless is missing the following inputParams facebookAppIdUserPool, facebookAppSecretUserPool, googleAppIdUserPool, googleAppSecretUserPool 2022-06-14T19:10:48.051Z [INFO]: Error: auth headless is missing the following inputParams facebookAppIdUserPool, facebookAppSecretUserPool, googleAppIdUserPool, googleAppSecretUserPool                                  at updateConfigOnEnvInit (/snapshot/repo/build/node_modules/@aws-amplify/amplify-category-auth/lib/provider-utils/awscloudformation/index.js:93:23)                                  at /snapshot/repo/build/node_modules/@aws-amplify/amplify-category-auth/lib/index.js:278:34                                  at /snapshot/repo/build/node_modules/promise-sequential/index.js:16:18                                  at runMicrotasks (<anonymous>)                                  at processTicksAndRejections (internal/process/task_queues.js:95:5) 2022-06-14T19:10:48.066Z [ERROR]: !!! Build failed 2022-06-14T19:10:48.066Z [ERROR]: !!!

Hey @sky4git 👋 thanks for raising this! I was not able to reproduce this with a new app with a Lambda and Auth (+admin queries) attached to Amplify Hosting, however I do have a few follow-up questions to better understand the context:

does this only occur in the Hosting builds? are you able to run commands locally, including amplify push, without error?
can you confirm both locally and in Hosting you are using Amplify CLI 8.4.0?
any further customizations applied to the build process?
is this awscloudformation directory present in your #current-cloud-backend?

My app id is d1ejtq711s7jra in ap-southeast-2

Hey @bobthemagicman :wave: thanks for chiming in here! From the error it appears we will need a few environment variables set in the Amplify Hosting console https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html#amplify-console-environment-variables
@stephenc222 glad to hear you are back up and running! And yes, please subscribe to https://github.com/aws-amplify/amplify-cli/issues/10581 and https://github.com/aws-amplify/amplify-cli/issues/10582 for further updates regarding the diagnostics issues

"debug": {
"shareProjectConfig": false
}

My app id is d1ejtq711s7jra in ap-southeast-2.  I tried "debug": {     "shareProjectConfig": false   } But now I started getting Above mentioned error regarding missing Error: auth headless is missing the following inputParams googleClientId
My team-provider-info.json has that value in it. I am not sure where else I need to put it again.

Hey @bobthemagicman 👋 thanks for chiming in here! From the error it appears we will need a few environment variables set in the Amplify Hosting console https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html#amplify-console-environment-variables
@stephenc222 glad to hear you are back up and running! And yes, please subscribe to #10581 and #10582 for further updates regarding the diagnostics issues

FYI: I already have the following environment variables in Amplify Hosting console
AMPLIFY_GOOGLE_CLIENT_ID
AMPLIFY_GOOGLE_CLIENT_SECRET

My error is fixed by adding googleClientId in cli-input.json

Hey @sky4git for the environment variable issue would you mind filing an issue on our Hosting repo? https://github.com/aws-amplify/amplify-hosting/issues/new/choose

Closing in favor of tracking root cause bugs #10581 and #10582

My issue was solved for me after adding
AMPLIFY_GOOGLE_CLIENT_ID
AMPLIFY_GOOGLE_CLIENT_SECRET

to the Environment variables in the Amplify Console under App Settings / Environment Variables.
This is not ideal because I now I have two places to update the ID+Secret per environment, on Amplify Studio Authentication  section and in the Console Environment Variables section.


Unittest does not work.

VS Code version: 1.47.0-insider
Extension version:2020.7.86945-dev

Expected behaviour
Tests are discovered
Actual behaviour
no any tests can be found, and no test lens, status bar does not show the test result.
Steps to reproduce:

Launch VSC and create python file named unit_test.py in folder1
**Clear the part of workspace configuration in setting.json
Enter below code:

	import unittest
	class PassingTests(unittest.TestCase):
		def test_passing(self):
        self.assertEqual(42, 42)
		def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")
	class FailingTests(unittest.TestCase):
		def test_failure(self):
        self.assertEqual(42, -13)
		def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")

Run "Run All Unit Tests", ensure:
a. triggers the prompt to configure the test runner
a) Click "Enable and configure a test framework"

b) Select "Unittest" and next ". Root directory"

c) Select first test file name format

Output window of Python Test log
> ~\AppData\Local\Programs\Python\Python38\python.exe -c "
import unittest
loader = unittest.TestLoader()
suites = loader.discover(".", pattern="*test.py")
print("start") #Don't remove this line
for suite in suites._tests:
    for cls in suite._tests:
        try:
            for m in cls._tests:
                print(m.id())
        except:
            pass"
cwd: c:\Users\111\Desktop\u1-1
> ~\AppData\Local\Programs\Python\Python38\python.exe -c "
import unittest
loader = unittest.TestLoader()
suites = loader.discover(".", pattern="*test.py")
print("start") #Don't remove this line
for suite in suites._tests:
    for cls in suite._tests:
        try:
            for m in cls._tests:
                print(m.id())
        except:
            pass"
cwd: c:\Users\111\Desktop\u1-1
> ~\AppData\Local\Programs\Python\Python38\python.exe -c "
import unittest
loader = unittest.TestLoader()
suites = loader.discover(".", pattern="*test.py")
print("start") #Don't remove this line
for suite in suites._tests:
    for cls in suite._tests:
        try:
            for m in cls._tests:
                print(m.id())
        except:
            pass"
cwd: c:\Users\111\Desktop\u1-1
> ~\AppData\Local\Programs\Python\Python38\python.exe -c "
import unittest
loader = unittest.TestLoader()
suites = loader.discover(".", pattern="*test.py")
print("start") #Don't remove this line
for suite in suites._tests:
    for cls in suite._tests:
        try:
            for m in cls._tests:
                print(m.id())
        except:
            pass"
cwd: c:\Users\111\Desktop\u1-1
> ~\AppData\Local\Programs\Python\Python38\python.exe c:\Users\111\.vscode-insiders\extensions\ms-python.python-2020.7.86945-dev\pythonFiles\visualstudio_py_testlauncher.py --us=. --up=*test.py --uvInt=2 --result-port=53782
cwd: c:\Users\111\Desktop\u1-1
> ~\AppData\Local\Programs\Python\Python38\python.exe c:\Users\111\.vscode-insiders\extensions\ms-python.python-2020.7.86945-dev\pythonFiles\visualstudio_py_testlauncher.py --us=. --up=*test.py --uvInt=2 --result-port=53782
cwd: c:\Users\111\Desktop\u1-1

Unfortunately I am not able to reproduce this. I create the file below in folder1
import unittest

class PassingTests(unittest.TestCase):
    def test_passing(self):
        self.assertEqual(42, 42)
    def test_passing_still(self):
        self.assertEqual("silly walk", "silly walk")

class FailingTests(unittest.TestCase):
    def test_failure(self):
        self.assertEqual(42, -13)
    def test_failure_still(self):
        self.assertEqual("I'm right!", "no, I am!")

unit_test.py
Opened folder1 as workspace folder, and then followed the steps you described.
I am suspecting you may not the correct folder opened. Please send the directory structure of your workspace folder (which should be folder1), and the relative path to unit_test.py in it. Also paste your settings.json file.

found tests in 2020.6.91350 python Extension .


docs(readme): minor improvement

As there more than M1 Apple devices, they are called Apple Silicon CPU family so i propose this change
And used only Macbook words as on Apple Silicon Mac Studio, Mac Mini and M1 iMac 24 devices does not have an battery

Thank you @dalisoft!


Page URL link is dead

Need to investigate where this URL is: https://service-manual.ons.gov.uk/design-system/guidance/page-titles-and-urls/#page-titles

Guidance page for page-titles-and-urls no longer exists - which is why link is not working.


DHCP times out on Google Compute Engine

I'm following http://blog.includeos.org/2017/03/21/includeos-on-google-compute-engine, but I can't seem to get it working. Maybe a recent regression in the DHCP handling? I've tried builds on both master and dev.
(Everything works when run locally with qemu.)
Some logs: verbose.log.

Here is a full, more verbose.txt

After applying the fix from #1246 (leaving the IP address set to <IP_ADDRESS> until we timeout), everything works. Problem solved :)

Thanks for trying IncludeOS on GCE and for the detailed log! As you found out, a fix was already in the queue, but we should have documented this better in the meantime. Please let us know if you run into any other issues!


Creation of UserController and listAction method.

Creation of UserController and listAction() method in UserController.

1hour

Creation of UserController and list method is terminated.


Unable to load images from a specific bucket from IBM Cloud Object storage.

Unable to load images from a specific bucket from IBM Cloud Object storage.

@bourdakos1 FYI

It looks like the images are stored at paths with multi-bit characters. For example, 炒小卷.zip. I will look into how COS expects you to fetch for this path. Right now I urlencode the path which results in %E7%82%92%E5%B0%8F%E5%8D%B7.zip which it doesn't seem to accept

It looks like the images are stored at paths with multi-bit characters. For example, 炒小卷.zip. I will look into how COS expects you to fetch for this path. Right now I urlencode the path which results in %E7%82%92%E5%B0%8F%E5%8D%B7.zip which it doesn't seem to accept

should be fixed now :)

should be fixed now :)


bump stylus version (Node 6 fixes)

Bumping Stylus is necessary for the loader to work in Node 6 too. Can we have a new release of this module please?
related: https://github.com/stylus/stylus/blob/dev/History.md

@mzgoddard @shama friendly bump

@givanse Thanks for the PR and the friendly bump. Why do we need this though? I see you mention node 6 but shouldn't node 6's version of npm install the latest stylus that is >=0.52? If you are bumping your node version on your local machine I'd imagine the typical advice for bumping node versions would apply, to clear your node_modules for a project and reinstall. That reinstall should get any new version, unless there is something I'm unaware of npm's semver package and how it compares >=.
Normally I'd probably just merge this but I'm hesitant since the the version bumped stylus-loader I'd release after this PR would restrict out older versions of stylus a project may depend on. And that, along with making it easier for stylus-loader users to keep up to date, are why we removed the direct stylus dependency.

understood, thanks!


Google via OAuth

As far as I understand it, Google will phase out app passwords for G Suite (basically Gmail with a custom domain) for “security reasons”: https://gsuiteupdates.googleblog.com/2019/12/less-secure-apps-oauth-google-username-password-incorrect.html?m=1
Any idea how large the effort would be to support Google’s OAuth for accessing these types of accounts?

@paulgessinger Thanks for letting me know.
Doing OAuth would require opening a browser and asking the user to go through the authorization flow.
it would certainly require a bit of work, but the main problem is that it means using this library with a cron job would become more difficult.
Here's an blog post by Martin Fowler about a similar use case: https://martinfowler.com/articles/command-line-google.html
Momentarily, seeing as there's a while before this gets enforced, I'll see if someone comes up with a PR

Right, makes sense. In principle, some of this flow could be pretty manual I guess. There doesn’t need to be a fully automated auth. flow, as also described in the link you included.
Once that’s done (i.e. once the refresh token is in the config file), everything else should not be problematic in a cron job, right? You just need to make sure the auth sequence ran once before.
I have no experience in ruby, otherwise I’d have stab at it myself.

I dug around a little bit. I found this which mentions using Google's own oauth2.py tool to do the sequence with the google api. Subsequently, it should be possible to do something like
require 'gmail_xoauth'
imap = Net::IMAP.new('imap.gmail.com', 993, usessl = true, certs = nil, verify = false)
imap.authenticate('XOAUTH2'<EMAIL_ADDRESS>my_oauth2_token)
messages_count = imap.status('INBOX', ['MESSAGES'])['MESSAGES']
puts "Seeing #{messages_count} messages in INBOX"

(copied verbatim from the first url) to get an imap connection, which I believe this tool operates off of.

This app is now blocked by Google as a "Less secure app" :( so this enhancement might be necessary

@paulgessinger If you're willing to beta test, I've implemented this in a branch https://github.com/joeyates/imap-backup/blob/feature/gmail-oauth. It's all documented here.

@paulgessinger If you're willing to beta test, I've implemented this in a branch https://github.com/joeyates/imap-backup/blob/feature/gmail-oauth. It's all documented here.

Hey @joeyates, I actually don't have access to a paid Google account anymore, since I migrated hosts. (that was what my other issue had been about, actually :) ).
So I'm afraid I can't test this I think.

Hey @joeyates, I actually don't have access to a paid Google account anymore, since I migrated hosts. (that was what my other issue had been about, actually :) ).
So I'm afraid I can't test this I think.

I've released version 3.0.0 with OAuth2 support for GMail.


Cannot read property 'renderReporter' of undefined

Hiya,
I'm receiving the following error when I import and use the Devtools component in my React app:
Uncaught TypeError: Cannot read property 'renderReporter' of undefinede @ index.js:1value @
index.js:1invokeComponentDidMountWithTimer @ ReactCompositeComponent.js:54notifyAll @
CallbackQueue.js:67close @ ReactReconcileTransaction.js:81closeAll @
Transaction.js:204perform @ Transaction.js:151batchedMountComponentIntoNode @
ReactMount.js:126perform @ Transaction.js:138batchedUpdates @
ReactDefaultBatchingStrategy.js:63batchedUpdates @
ReactUpdates.js:98_renderNewRootComponent @
ReactMount.js:285_renderSubtreeIntoContainer @ ReactMount.js:371render @
ReactMount.js:392(anonymous function) @ routes.js:33(anonymous function) @
routes.js:34(anonymous function) @ bundle.js:1173__webpack_require__ @
bundle.js:20(anonymous function) @ multi_main:3(anonymous function) @
bundle.js:2376__webpack_require__ @ bundle.js:20(anonymous function) @
bundle.js:64(anonymous function) @ bundle.js:67

The devtools themselves don't actually work, but the toolbar is visible. In addition, all of my app functionality - routing via react-router, form -> get request, etc. - is now causing a page reload where before it wouldn't.
My app is built on top of<EMAIL_ADDRESS>Not sure if that is relevant or not.
Thanks for any help!

@alexjhannan, please update mobx-react: https://github.com/mobxjs/mobx-react/issues/96

Perfect! Thanks for your help.


OpenAIRE 4 relatedIdentifier being used for all dc:identifier:* metadata other than dc:identifier:uri

Describe the bug
datacite:relatedIdentifier element being used for all dc:identifier:* metadata other than dc:identifier:uri. Not all dc:identifier:* values can be assumed to be relatedIdentifier and may be alternateIdentifier instead.
To Reproduce
Access an openaire4 OAI record for an item that has many different dc:identifier:* values. Every one other than dc:identifier:uri will show up as datacite:relatedIdentifier elements.
Expected behavior
When it isn't known for sure that the dc:identifier:* value is actually a relatedIdentifier value, perhaps it is better to assume it is an alternateIdentifier by default. This follows the approach originally included with the proposed PR 2709 for DSpace 6.x that used alternateIdentifier, except for the case of dc:identifier:issn that was handled separately as a relatedIdentifier. Another common use case is with dc:identifier:doi being an externally-generated DOI for the item (i.e., not generated by DSpace automatically) and being an alternateIdentifier to the DSpace Handle.
Related work
See discussions from:
PR 2576 (specifically this comment)
DS-3708

@paulo-graca : pinging you on this to get your feedback since you created the initial implementation here.  This seems reasonable to me, but I don't know if you foresee problems with this approach.

Thank you so much @uofmsean for testing this out. I will take a closer look as soon as possible.
You are right, we decided what's in this post:
https://github.com/DSpace/DSpace/pull/2576#issuecomment-559110676
If the result is different, to me it can only be one of two things: there is a bug, or the schema used it's poor and it's not the OpenAIRE 4 (please check: https://wiki.lyrasis.org/display/DSDOC7x/OpenAIRE4+Guidelines+Compliancy for more details)

@uofmsean I've just created PR #3107 to address this issue. Some of the approaches referred might need further discussion. For instance, dc.identifier.doi will be a custom change. So, any support for it should be also custom. Also the relation type might require a proper field type (complex field), so we are assuming that all supported related identifiers have the relation type isPartOf. And alternate identifiers will be mapped from dc.identifier.uri (the case of DSpace registered DOIs when you already have an Handle)

@uofmsean I've just created PR #3107 to address this issue. Some of the approaches referred might need further discussion. For instance, dc.identifier.doi will be a custom change. So, any support for it should be also custom. Also the relation type might require a proper field type (complex field), so we are assuming that all supported related identifiers have the relation type isPartOf. And alternate identifiers will be mapped from dc.identifier.uri (the case of DSpace registered DOIs when you already have an Handle)


Conversion for markdown highlight

Hi,
I've been using python-semantic-release for generating the Changelog markdown files, but apparently m2r2 is not correctly converting to RST.
Example from Changelog.md
* Update setup.py ([`2513d97`](https://gitlab.com/felipe_public/badges gitlab/-/commit/2513d970f9b055675de2f5479856604a7774f430))

Result after m2r2 inclusion in sphinx
Update setup.py (``2513d97` <https://gitlab.com/felipe_public/badges-gitlab/-/commit/2513d970f9b055675de2f5479856604a7774f430>`_)

I believe insted of converting to double quotes (for .rst) it is missing the second double quotes?
Am I missing something?
Regards,

Hi, this seems to be related to #36 . RST does not allow for hyperlinks to be formatted.
Closing this as to centralize in a single issue.


Cannot find module 'eslint-config-google' in atom editor

I've npm install executed and done the npm install eslint-config-google still got this error.Any solutions?

I would try an npm cache clean && rm -rf node_modules followed by a fresh npm install. Occasionally dependencies fail to install due to network issues. Feel free to reping this thread if its still an issue.


Request:  Symbols that can represent multiple letters

Description
I've tried with a few combinations of EnglishTransformers, but I haven't been able to correctly censor words like sh*t or f*ck.  In both cases, words should be censored, however, in the first word * represents an i and * represents a u. Is there a way to create a new transformer for multiple letters/regex?
Solution
I do not know how this can be implemented. Looking at the L33tspeak transformer, I can see there's a map per character:
	['a', '@4'],
	['c', '('],
	['e', '3'],
	['i', '1|'],
	['o', '0'],
	['s', '$'],

However, I don't know how it would work for multiple characters where for example, we could have
	['*', 'any_letter_or_vowel_etc.'],

Code of Conduct

[X] I agree to follow this project's Code of Conduct.

Allowing one character to map to multiple characters is untenable with Obscenity's current design, and I do not think it is something we would like to support--we would need to test patterns against all possible transformed strings instead of just one, degrading performance significantly. (Consider the input text **** with * -> any of aeiou, for instance: there are 5^4 = 625 possible output strings. With adversarial inputs this could be disastrous.)
The correct way to solve this issue is to either adjust the patterns (that is, add a pattern that matches directly on the text sh*t), or to strip out the * with a transformer. Some previous versions of Obscenity actually correctly identified a match in the input f*ck using the second approach (see the skipNonAlphabetic transformer, disabled by default due to #46.) It has always been my goal to eventually add the skipNonAlphabetic` transformer back after fixing that issue, but I have not gotten to it yet.
With these considerations in mind, I am inclined to close this specific request as wontfix, but I think the intent of your issue is actually already tracked in #46--so, to be clear, I do hope that eventually Obscenity's detection quality can be improved to catch the cases you mention, just not in the manner you propose. Does that sound reasonable to you?

For some context on why I have not yet fixed #46, the code dealing with transformations and matching is some of the more nasty code in this package, in part due to its age--I would have done things differently now compared to 3 years ago--and in part due to the complexity in mapping match positions in the transformed text back to the original text in a Unicode-aware way. (Working in both Unicode code points and UTF-16 code units depending on context makes this even nastier.) Consequently, for some time, this code was on rather shaky ground (as you observed in #71), and I was very reluctant to adjust it for fear of breaking it more.
Recently, however, after your previous report I took the time to rework some of the code and fuzz tested it in https://github.com/jo3-l/obscenity/commit/25bd1db98591f4be75a9787aafcec4d850d0ddc0 and am now much more confident that things are as they should be. Addressing #46 should, I think, be considerably more straightforward after this, and it's possible we can do it in the next release.

I did read #46, but not necessarily tied it to the use case presented here. I'll add asterisks in my word inputs since that will work for the moment as per your suggestion.
Thanks a lot for your hard work!!

I did read https://github.com/jo3-l/obscenity/issues/46, but not necessarily tied it to the use case presented here.

That's fair. The title of #46 is a little misleading at the moment; it's more of a tracking issue to get the skipNonAlphabetic transformer re-enabled by default since the original problem there was fixed.

For ease of tracking, I'm going to close this in favor of #46, which I just renamed to better reflect the current state of that issue. As discussed above, the suggestion ultimately presented there is a directly actionable way of solving the same problem in your original issue. Thanks!


Meteor local server on mobile - Error: Error parsing asset manifest

I have deployed a Meteor app on Heroku.
I have added a platform: Android
When I try I build the app using the meteor build command meteor build --directory ~/builds --server https://my-app.herokuapp.com and the install the apk using adb, I get an error.
I get the same error when trying to run app locally, but with different server: meteor run android-device --mobile-server https://my-app.herokuapp.com
The error is:
Error: Error parsing asset manifest(…)
(anonymous function) @ webapp.js?hash=2552b0d8c8f134d5763b6897c1be6c9bfa3e9c28:68
(anonymous function) @ webapp_local_server.js:37
cordova.callbackFromNative @ cordova.js:293
processMessage @ cordova.js:1081
processMessages @ cordova.js:1104
pollOnce @ cordova.js:973
pollOnceFromOnlineEvent @ cordova.js:960

Here is some more information: https://forums.meteor.com/t/meteor-local-server-on-mobile-error-error-parsing-asset-manifest/21215/3

Thanks for the forum link! Very helpful.  Should be fixed in #90.


fix: Use massongit/actions-get-node-active-major-versions in CI test

CI test seems to be testing Node.js LTS and maintenance major versions.
It's difficult to maintain these versions manually.
Therefore, I use the automatically got action https://github.com/massongit/actions-get-node-active-major-versions.

I want to update Node.js versions manually.


add basic html content and styles

In this pull request I created an npm project with webpack and added basic HTML markup with minimum styling (just to make the layout)

Hi, @KayLemba KayLemba how are you doing!
Thank you so much for taking the time to review my PR. Happy coding!


Install specific groups of deps?

I'm working on a project where there are multiple requirements.txt files that are meant to be mutually exclusive and deployed in different environments (one file has only a single dependency in it since it's meant to run a scheduler package in a constrained environment). I was wondering if poetry supported that, where the TOML file would look something like
[tool.poetry.dependencies]
...
[tool.poetry.deps1-dependencies]
...
[tool.poetry.deps2-dependencies]
...

and you would do something like poetry install -E deps1 and it would install only the set in deps1 without touching the base set of dependencies used elsewhere.

What you want to use in this case are extras
Dependencies sections other than dependencies and dev-dependencies will likely not be supported.


Support Point-in-time Data Operation

Description

Support Point-in-time Data Operation
Motivation and Context

How Has This Been Tested?

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[x] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[ ] Fix bugs
[x] Add new feature
[ ] Update documentation

我想在本地把这个pr合并到当前主分支来用，但是有大量的代码冲突。请问这个pr还在开发中吗？没有的话我准备在当前主分支版本的基础上按照这个pr的逻辑进行开发来支持时点数据。

The development of this PR is finished and it is ready for review now.
Welcome to try this feature.
It will be merged to master soon!
@Chaoyingz


diesel migration generate create_users does not work anymore

This used to work on early versions of disel_cli, but now I re-installed diesel_cli 0.9.0 it will keep displaying the help message.
$diesel migration generate create_users
diesel-migration-generate
Generate a new migration with the given name, and the current timestamp as the version

USAGE:
    diesel migration generate [OPTIONS] <MIGRATION_NAME>

FLAGS:
    -h, --help    Prints help information

OPTIONS:
        --database-url <DATABASE_URL>            Specifies the database URL to connect to. Falls back to the DATABASE_URL environment variable if unspecified.
        --migration-dir <MIGRATION_DIRECTORY>    The location of your migration directory. By default this will look for a directory called `migrations` in the
                                                 current directory and its parents.
        --version <MIGRATION_VERSION>            The version number to use when generating the migration. Defaults to the current timestamp, which should
                                                 suffice for most use cases.

ARGS:
    <MIGRATION_NAME>    The name of the migration to create

However with a correct .env with the DATABASE_URL set correcly, diesel setup works and creates the needed database and tables.
Tested both on MacOS and ubuntu 16.04, with the same behavior.

I saw this failure as well but couldn't reproduce it locally. Are you using
the 0.9 from crates.io or from git master?
Did maybe one of our dependencies change? (We use clap for the CLI.)
ivanceras<EMAIL_ADDRESS>schrieb am Mi. 1. Feb. 2017 um 07:40:

This used to work on early versions of disel_cli, but now I re-installed
diesel_cli 0.9.0 it will keep displaying the help message.
$diesel migration generate create_users
diesel-migration-generate
Generate a new migration with the given name, and the current timestamp as the version
USAGE:
diesel migration generate [OPTIONS] <MIGRATION_NAME>
FLAGS:
-h, --help    Prints help information
OPTIONS:
--database-url <DATABASE_URL>            Specifies the database URL to connect to. Falls back to the DATABASE_URL environment variable if unspecified.
--migration-dir <MIGRATION_DIRECTORY>    The location of your migration directory. By default this will look for a directory called migrations in the
current directory and its parents.
--version <MIGRATION_VERSION>            The version number to use when generating the migration. Defaults to the current timestamp, which should
suffice for most use cases.
ARGS:
<MIGRATION_NAME>    The name of the migration to create
However with a correct .env with the DATABASE_URL set correcly, diesel
setup works and creates the needed database and tables.
Tested both on MacOS and ubuntu 16.04, with the same behavior.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/diesel-rs/diesel/issues/602, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABOX62gtYB2buaW3vmn1F8rh0YKuSW8ks5rYCjLgaJpZM4Lzic8
.

Yes, by installing it via cargo install diesel_cli
I'm using rust nightlies
$cargo -V
cargo 0.17.0-nightly (40a4ce6 2017-01-06)
$rustc -V
rustc 1.16.0-nightly (47c8d9fdc 2017-01-08)

I'm also having this error, Debian 8.7
Just following along with the getting started, diesel setup worked fine.
diesel 0.9.0
rustc 1.16.0-nightly (df8debf6d 2017-01-25)
cargo 0.17.0-nightly (67e4ef1 2017-01-25)

I'm also running into this problem:
Mac OS 10.11.16
rustc 1.16.0-nightly (df8debf6d 2017-01-25)
cargo 0.17.0-nightly (67e4ef1 2017-01-25)
diesel 0.9.0

diesel setup worked fine, diesel migration generate create_entries did create the migrations/ folder, but it did not create the migration files. The CLI usage text is outputted to the console instead.

@killercup I'm able to reproduce this, as you assumed this related to dependency change. Building diesel with clap 2.19 will produce a fully working build, but building with 2.20 (the most current version) will produce a build that showed the described issue.

So it's a breaking change in clap? cc @kbknapp
@weiznich, why would it ever load a clap ≥ 2.11, though? diesel_cli contains a Cargo.lock :O
I really hope this has nothing to do with workspaces :/ (or I'll need to cc some more people)

It seems like that this lock is ignored because diesel uses a cargo workspace and therefore a common lock file for all workspace members. The common lock file should be located in the workspace root.

Interesting. I'm not aware of any breaking changes in from clap 2.19 to 2.20. I'll look into this more and see if I can find anything.

It's possible it could be a regression bug, would someone mind filing an issue on the clap repo? I'm on mobile right now. Also compiling clap with the features = ["debug"] will help as well.

Quick workaround: clap = "=2.19.3". We should probably remove diesel_cli from the workspace for now.

/cc @alexcrichton it looks like there's also no way for us to opt just the one crate out of being in the workspace? What's the best option here since binaries are supposed to check in their Cargo.lock?

I'm going to remove the Cargo.lock from the tree as well, since crates.io will never use it by the look of things.

I'm looking into this bug as we speak, if it's what I think is happening I
should have a fix out momentarily.
On Feb 2, 2017 3:09 PM, "Sean Griffin"<EMAIL_ADDRESS>wrote:

I'm going to remove the Cargo.lock from the tree as well, since crates.io
will never use it by the look of things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/diesel-rs/diesel/issues/602#issuecomment-276966918,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGnttvgR8PW-jXZvGzyYzc9vInBU9LWSks5rYeOUgaJpZM4Lzic8
.

@sgrif thanks for the cc! Yeah currently there's no opt-out, but that's tracked at https://github.com/rust-lang/cargo/issues/3192


Sub fields returning null

Having an issue returning sub fields.. Not sure If there is something I need to add to resolvers, but have attempted that as well with no luck.  Name returns fine, but null is coming back for any fields inside location. Even though the data exists in the same format. Am i missing something?
type Query {
    findPeople(
        personId: [String!]
    ): [Person]
}

type Person {
    location: Location
    name: String
}

type Location {
    city: String
}

It's hard to say if you're missing something without knowing a bit more about your entire setup. I'm curious how you're relating the records in Mirage, if you're having trouble even after adding your own resolvers. Feel free to chat in the Mirage Discord, too.

Leaving this comment in case anyone else runs into this issue. I found somewhat of a workaround based on the recommendation from this ticket. I basically had to do the changes shown below. Please note I changed some of the code due to the nature of the private project I am on so some of the things are too exact, but should give a general idea. Essentially, make sure you have revolvers for fields that are coming back as null.
The Schema:
type Response {
  name: String,
  payload: ResponsePayload
}

type ResponsePayload {
  id: String,
  name: String,
  data: ResponsePayloadData
}

type ResponsePayloadData {
  Acctrefno: Int
  Loan_Type: Int
  Status_Code_No: Int
  Borrower_Loan_Nickname: String,
}

The Query:
const UPDATE_NICKNAME = gql`
  mutation UpdateUserNickname($loan_id: String!, $body: String!) {
    UpdateNickname(loan_id: $loan_id, body: $body) {
      payload {
        data {
          Nickname
        }
      }
    }
  }
`;

The Resolver in the Mock Server:
createServer({
  routes() {
    const graphQLHandler = createGraphQLHandler(GRAPH_QL_SCHEMA, this.schema, {
      resolvers: {
        Mutation: {
          UpdateNickname: (obj, args, context, info) => {
            const result = {
              payload: {
                data: {
                  Nickname: 'Mock Test Loan',
                },
              },
            };

            return result;
          }
        },
        ...
        ResponsePayload: {
          data: ({ data }) => data,
        },
        Response: {
          payload: ({ payload }) => payload,
        }
      },
    });
    this.post('/graphql', graphQLHandler);
  },
  ...
});

I'm not sure why this happens (maybe something to do with nested response values?) but my hope is that this helps someone who may run into a similar issue. Event with this little gotcha, overall this library is very useful. Thanks to the team for putting it together.

Leaving this comment in case anyone else runs into this issue. I found somewhat of a workaround based on the recommendation from this ticket. I basically had to do the changes shown below. Please note I changed some of the code due to the nature of the private project I am on so some of the things are too exact, but should give a general idea. Essentially, make sure you have resolvers for fields that are coming back as null.
The Schema:
type Response {
  name: String,
  payload: ResponsePayload
}

type ResponsePayload {
  id: String,
  name: String,
  data: ResponsePayloadData
}

type ResponsePayloadData {
  name: String,
  nickname: String,
}

The Query:
const UPDATE_NICKNAME = gql`
  mutation UpdateUserNickname($userid: String!, $body: String!) {
    UpdateNickname(userid: $userid, body: $body) {
      payload {
        data {
          nickname
        }
      }
    }
  }
`;

The Resolver in the Mock Server:
createServer({
  routes() {
    const graphQLHandler = createGraphQLHandler(GRAPH_QL_SCHEMA, this.schema, {
      resolvers: {
        Mutation: {
          UpdateNickname: (obj, args, context, info) => {
            const result = {
              payload: {
                data: {
                  nickname: 'My Nickname',
                },
              },
            };

            return result;
          }
        },
        ...

        // NOTE: Here are the resolvers for the fields of specific types where the values kept coming back as null.
        ResponsePayload: {
          data: ({ data }) => data,
        },
        Response: {
          payload: ({ payload }) => payload,
        }
      },
    });
    this.post('/graphql', graphQLHandler);
  },
  ...
});

I'm not sure why this happens (maybe something to do with nested response values?) but my hope is that this helps someone who may run into a similar issue. Even with this little gotcha, overall this library is very useful. Thanks to the team for putting it together.

Thanks for sharing. I'm not sure why you need to add resolvers for the ResponsePayload and Response types 🤔  The library should be doing this by default. It's definitely worth investigating. If you don't mind, could you open a separate issue for this so it's easier to work on?

@jneurock Yes, I can raise an issue for this and in a few days I will see if I can put together a repo with a simple example for review. I will try to match the configuration I'm using on a current project in case my setup of the library is off in some way.

Thanks, @ronbravo!

I'm experiencing this as well, currently trying with a relatively simple schema like the OP's example:
type Location {
  city: String
  state: String
}

type Event {
  id: String
  description: String
  location: Location
}

And I can confirm using the workaround to explicitly grab this field in a resolver when creating the mirage-server achieves the desired effect:
resolvers: {
  Event: {
     location: ({ location }) => location
   }
 }

I'm experiencing this as well, currently trying with a relatively simple schema like the OP's example:
type Location {
  city: String
  state: String
}

type Event {
  id: String
  description: String
  location: Location
}

And I can confirm using the workaround to explicitly grab this field in a resolver when creating the mirage-server achieves the desired effect:
resolvers: {
  Event: {
     location: ({ location }) => location
   }
 }

Can you share the query where you see the issue? What's hard for me to understand is why this is happening. I have a test that covers nested records. Thanks!

Update: Through a Discord chat I was able to tweak a test mutation in the library and reproduce the issue. At least, the issue where related records result in null field values.
I'd have to see the actual resolver code in each case above to compare but in my case the issue came from returning records that were not Mirage model instances.
For example, there's a custom resolver test involving a mutation. The resolver code looks like this:
resolvers: {
  Mutation: {
    optionallyMutateTestObject(_obj, { id, input }, context) {
      return context.mirageSchema.db.testObjects.update(id, input);
    },
  },
}

This works fine if I don't want to return related records but that may just be by chance. This doesn't return a Mirage model instance. If I seed my database with a record related to this and I ask for the related fields in my GraphQL mutation, it will fail.
In order for me to successfully resolve this with related records, I need to change my resolver like this:
resolvers: {
  Mutation: {
    optionallyMutateTestObject(_obj, { id, input }, context) {
      return context.mirageSchema.testObjects.find(id).update(id, input);
    },
  },
}

There's a subtle difference in the Mirage API used but the latter will return a Mirage model and Mirage GraphQL knows how to auto-resolve its fields.


Fix up some typoes and stuff; add listships + getshiplocation commands

see title

Lets hope this merge works. 🙏

Hooray it worked! Sorry for taking so long to handle the pull request.


[image_picker] pickMultipleMedia future never ends on iOS devices

Is there an existing issue for this?

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

Steps to reproduce

Open the gallery with pickMultipleMedia.
Close the native modal very quickly

Expected results
The future ends normally.
Actual results
The future never ends.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';

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

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

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: OutlinedButton(
            onPressed: () async {
              debugPrint('Gallery opened');
              await ImagePicker().pickMultipleMedia();
              debugPrint('Gallery closed');
            },
            child: const Text('Open gallery'),
          ),
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/26067909/454a2489-3e4e-4e48-8de0-34f8412dbb2d

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.1, on macOS 13.0.1 22A400 darwin-arm64, locale fr-FR)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] VS Code (version 1.82.1)
[✓] Connected device (2 available)
[✓] Network resources

• No issues found!

Thanks for the report. I also check other methods and see the issue is reproducible as well (verified on iPhone 7, iOS 15.7.2)

pickMultipleMedia()
pickMultiImage()
pickMedia()
pickImage(source: ImageSource.gallery): As the 1st request is not finished, it causes an exception at the 2nd request:

Exception log (pickImage)
flutter: Gallery opened
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: PlatformException(multiple_request, Cancelled by a second request, null, null)
#0      ImagePickerApi.pickImage (package:image_picker_ios/src/messages.g.dart:172:7)
<asynchronous suspension>
#1      ImagePickerIOS.getImageFromSource (package:image_picker_ios/image_picker_ios.dart:78:26)
<asynchronous suspension>
#2      MainApp.build.<anonymous closure> (package:reproduce_issues/imagepicker_neverend_134715.dart:19:15)
<asynchronous suspension>

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.13.3, on macOS 13.5 22G74 darwin-x64, locale en-VN)
    • Flutter version 3.13.3 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (32 hours ago), 2023-09-06 14:32:31 -0700
    • Engine revision b8d35810e9
    • Dart version 3.1.1
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode15-beta8.app/Contents/Developer
    • Build 15A5229m
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.7.2 19H218
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 116.0.5845.179

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.14.0-14.0.pre.288, on macOS 13.5 22G74 darwin-x64, locale en-VN)
    • Flutter version 3.14.0-14.0.pre.288 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ee9aef0130 (26 minutes ago), 2023-09-13 19:48:22 -0700
    • Engine revision cd90cc8469
    • Dart version 3.2.0 (build 3.2.0-140.0.dev)
    • DevTools version 2.27.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 32.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 116.0.5845.187

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Given the timing in the video it looks like we're not getting a delegate callback (or at least one we are listening to) when dismissing it while it's still in the process of animating in. We'll need to experiment on the native side to see if there's anything we can listen to get notified when this happens. (If not, we may need something ugly like a timer to check if it's gone.)


[KYUUBI #3366] Support hive write code path

Why are the changes needed?

Fix https://github.com/apache/incubator-kyuubi/issues/3366
This PR is a subtask of Kyuubi's support for Hive data sources, and aims to support write code path
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Codecov Report

Merging #3367 (ee7a9db) into master (f4120a0) will decrease coverage by 0.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3367      +/-   ##
============================================
- Coverage     51.51%   51.38%   -0.13%
  Complexity       13       13
============================================
  Files           475      476       +1
  Lines         26475    26537      +62
  Branches       3694     3702       +8
============================================
- Hits          13638    13636       -2
- Misses        11506    11573      +67
+ Partials       1331     1328       -3

Impacted Files
Coverage Δ

...client/exception/RetryableKyuubiRestException.java
0.00% <0.00%> (-100.00%)
:arrow_down:

.../org/apache/kyuubi/client/RetryableRestClient.java
48.78% <0.00%> (-24.40%)
:arrow_down:

...org/apache/spark/kyuubi/SQLOperationListener.scala
73.17% <0.00%> (-7.08%)
:arrow_down:

...main/java/org/apache/kyuubi/client/RestClient.java
82.75% <0.00%> (-3.45%)
:arrow_down:

...g/apache/kyuubi/operation/BatchJobSubmission.scala
72.00% <0.00%> (-2.41%)
:arrow_down:

...c/main/java/org/apache/kyuubi/jdbc/hive/Utils.java
35.95% <0.00%> (-0.83%)
:arrow_down:

.../kyuubi/plugin/spark/authz/PrivilegesBuilder.scala
69.15% <0.00%> (-0.22%)
:arrow_down:

.../org/apache/kyuubi/jdbc/hive/KyuubiConnection.java
3.97% <0.00%> (-0.20%)
:arrow_down:

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
96.89% <0.00%> (-0.08%)
:arrow_down:

.../org/apache/kyuubi/config/KyuubiReservedKeys.scala
0.00% <0.00%> (ø)

... and 15 more

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

@Yikf, please separate the renaming changes to another PR to make the final git commit cleaner.

cc @zhaomin1423 if you have time to help review

thanks, merging to master


Method java.lang.Math.addExact(JJ)J was not found

[ERROR] Method java.lang.Math.addExact(JJ)J was not found
    at java.time.LocalDate.plusDays(TLocalDate.java:588)
    at java.time.LocalDateTime.plusDays(TLocalDateTime.java:472)
    at java.time.Instant.parse(TInstant.java:221)
    at java.time.Instant.parse(TInstant.java:157)

In my PR for TeaVM I fixed this by extending TMath:
https://github.com/konsoletyper/teavm/pull/467
I will have to provide another PR for TeaVM that only adds this change to TMath to get this accepted. TeaVM project is rather monolithic and perfectionalistic. Hence, I have to go for small steps that each are fully complete and consistent rather than being blocked for years...

In my PR for TeaVM I fixed this by extending TMath:
https://github.com/konsoletyper/teavm/pull/467
I will have to provide another PR for TeaVM that only adds this change to TMath to get this accepted. TeaVM project is rather monolithic and perfectionalistic. Hence, I have to go for small steps that each are fully complete and consistent rather than being blocked for years...

Ah, cool. This change has already been done. I just need to update TeaVM version then. Awesome.

Ah, cool. This change has already been done. I just need to update TeaVM version then. Awesome.

Mhm, but I am using 0.7.0-dev-1169 what seems to be the latest available release:
https://dl.bintray.com/konsoletyper/teavm/org/teavm/teavm-core/

Mhm, but I am using 0.7.0-dev-1169 what seems to be the latest available release:
https://dl.bintray.com/konsoletyper/teavm/org/teavm/teavm-core/

OK, missing floorDiv and floorMod methods had been added meanwhile but toIntExact and addExact are still missing. So I will create a PR in TeaVM for that.

OK, missing floorDiv and floorMod methods had been added meanwhile but toIntExact and addExact are still missing. So I will create a PR in TeaVM for that.

Fixed.


[CSBindings] Don't record duplicate bindings for opened nominal types

Otherwise it would result in checking the same type multiple times
and results in worse pontential binding picks.

@slavapestov Does it look like what you meant in https://github.com/apple/swift/pull/19066?

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please test source compatibility

Chatto and CoreStore failed in the debug mode, which is unrelated.


Android and flutter mixed development, how to console to print the developer.log of flutter?

Android and flutter mixed development, how to console to print the developer.log of flutter?
Android Studio, flutter + android hybrid, Run window and Logcat window have only print output, no log output. If I use print, long data cannot be output.
doctor:
D:\flutter\bin\flutter.bat doctor --verbose
[√] Flutter (Channel stable, 2.2.1, on Microsoft Windows [Version 10.0.22000.100], locale zh-CN)
    • Flutter version 2.2.1 at D:\flutter
    • Framework revision 02c026b03c (8 weeks ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\10338\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Android Studio
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6842174)

[√] IntelliJ IDEA Ultimate Edition (version 2021.1)
    • IntelliJ at D:\idea\IntelliJ IDEA 2021.1.2
    • Flutter plugin version 58.0.3
    • Dart plugin version 211.7665

[√] VS Code (version 1.58.2)
    • VS Code at C:\Users\10338\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.21.0

[√] Connected device (3 available)
    • Android SDK built for x86 (mobile) • emulator-5554 • android-x86    • Android 10 (API 29) (emulator)
    • Chrome (web)                       • chrome        • web-javascript • Google Chrome 91.0.4472.124
    • Edge (web)                         • edge          • web-javascript • Microsoft Edge 92.0.902.55

• No issues found!
Process finished with exit code 0

HI @ddxl123
You can use flutter attach from the module to get logs from your add to app
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this, you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


Example not working

Github pages link to demo is broken

https://bvaughn.github.io/redux-search/

Oops, I recently moved orgs for this repo since I was leaving Treasure Data. Forgot to update the URL. Thanks for pointing it out! Fixed~


Empty root after building with nested prismic data

Steps:

react-static create (basic prismic)
yarn build
check in browser > works

add my own endpoint
bypass the transformer
yarn build > gives empty root

<!DOCTYPE html><meta charSet="UTF-8"/><meta name="viewport" content="width=device-width, initial-scale=1"/>

It looks like react-static can't handle the nested prismic data
The reason i don't want to map this data is because i'm using RichText from prismic-reactjs
Is there a solution for this?

Can you post a link to the repo or code that you're referring to?

I found the bug, i had window in my code!
Solved it with this snippet:
if (typeof window === 'undefined') {
  global.window = {
    innerWidth: 0,
  };
}


godcr slows down while syncing

when syncing a new wallet, the user interface seems to lag. It is understood that syncing a new wallet can be CPU intensive, however, the UI shouldn't lag when this is going on.
Machine Specifications
OS: MacOs
Processor: 2.4 GHz Quad-Cor Intel Core i5
Memory:  8gb

I do profile track and see the high pressure on CPU, as I mage show (*addrFinder).filter and (*filter).MatchAny during sync


Update pre-merged workflow

This commit refactors the pre-merged workflow to enhance the CI/CD pipeline for pull requests. The changes include:

Adding a new job named "e2e-tests" that performs end-to-end tests.
Setting up environment variables for the Docker registry and repository details.
Adding steps to log into ghcr.io, build and push a Docker image, and deploy to the HNS CI cluster.
Running end-to-end tests using the 'make test-e2e' command.
Restricting the workflow to trigger only on pull requests targeting the 'main' branch.

Remove the existing go-vet from CI since it's not in the Pre Merge

/lgtm
/approve

/lgtm
/approve


customers: accept yyyy-mm-dd formatted birthDates

Requested from @joshsadler

Big thanks!

btw @InfernoJJ Identity has the same problem. We can use model.YYYYMMDD though.
https://github.com/moov-io/identity/blob/master/pkg/client/model_identity.go#L27

Codecov Report

Merging #163 into master will increase coverage by 0.00%.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##           master     #163   +/-   ##
=======================================
  Coverage   61.61%   61.62%
=======================================
  Files          43       44    +1
  Lines        2493     2504   +11
=======================================
+ Hits         1536     1543    +7
- Misses        699      701    +2
- Partials      258      260    +2


Cant use markdown text objects in elements array.

Describe the Bug
I can't put a markdown text object as an element
{
"type": "context",
"elements": [
	{
		"type": "mrkdwn",
		"text": "_5 channels maximum_"
	}
     ]
}

Additional Context
Is this not supported? I cannot find a way to do this.

Hello! It does the conversion to a markdown text object under the hood, you can simply pass in strings or an array of strings. Cheers!


Always use JS Date type in model value

This should fix #49
Before, depending on what the initial value for daterangepicker was, the model contained either JS Date objects or moments.
After this PR, the model always contains JS Dates for date ranges (or single dates if singleDatePicker is set to true).
This might be considered breaking change, because someone migtht have assumed that the component is returning moments.
Why JS Date instead of moment?
JS Date is native. Moment is just a library that might be changed in the future.

I would vote against this breaking change. The underlying plugin returns moment objects. Doesn't make sense to me for an Angular wrapper to change the object it returns. I suggest if you want native JS dates that this be a fork. RE: moment being a library that could change, it seems unlikely that moment will be taken out of dan grossman's plugin.


File Explorer Add-ons Support for Email (*.eml) files

Description of the new feature / enhancement
Support *.eml (Email message) file format in File Explorer Preview add-ons.
Possibly also include support for Outlook *.msg format.
Scenario when this would be used?
Preview the content of email files when saved to File Explorer.
Supporting information

Appropriate filtering would need to be in place to disable remote/embedded content and scripts for privacy/security reasons.
Option to toggle between Plain-text and HTML-formatted emails.
Possible use of Message Header Analysis API? (see https://mha.azurewebsites.net)

Thanks for the feedback - this seems like a neat feature! I'm going to remove the needs-triage label and add this to our backlog.


Managed Instance restores

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[x] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Implements #5297 and prevents non compatible parameters being pushed through to a managed instance
In draft as there's be some other bits to come as people spot issues or come up with other use cases. But only expecting it to be around a day or so.
Approach
Check the DatabaseEngineEdition property of the restore server. If it's SqlManagedInstance then check parameters and stop if anything that MI won't touch aren't being used.
If withreplace is needed and specified then do a drop/restore as traditional WithReplace isn't supported
Commands to test
$op = Get-DbaBackupHistory -SqlInstance localhost -database mitest | Restore-DbaDatabase -SqlCredential $cred -SqlInstance dbatoolsmi.cus19c972e4513d6.database.windows.net -TrustDbBackupHistory -DatabaseName tes3t  -verbose

Merging as I need it for the Copy-DbaDatabase work


Use lint configs from lint-configs subtree repository

Part of https://github.com/StackStorm/st2/pull/2503#issuecomment-185323722 change.

I also noticed there is a bug in the Makefile targets.
We don't correctly exit if a loop iteration returns non-zero (aka fails). The Makefile target would only fail if the last item in the loop iteration exited with non-zero.
This means there are some issues in the master branch which have managed to slip through because of this bug.
In any case, I'm working on a fix in this branch.


Virtual Kubelet: working queue based reflection

Description
This PR re-implements the reflection logic in the virtual kubelet leveraging working queues, for better resiliency and improved performance.
Note: this PR is temporary and will be splitted later on.
Fixes #(issue)
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[ ] Test A
[ ] Test B

/test

/test

/test

/test


Fixing names in the parameters table

IncludePosition was mistakenly listed 3 times instead of the correct names.
The documentation for Selection.InsertCrossReference has them correct and this patch matches that.

Hi @ethack, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). 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, MSBOT;

ethack,
Thank you for making changes to the GitHub repo. Your contributions help improve the quality of our documentation.
Office Scale team


Integrate JQuery datatables into vdataFrame tables

This is 1st PR of a series whose goal will be to support interactive tables i.e dynamic tables using javascript.
I created a separate branch as I would like to merge it to the main only it will be statble and complete.
For now you can test it with:

init_interactive(all_interactive=True): this will enable interactive table on all vdataframes.
vdf.idisplay(): use this method if you only one to activate interactive table on the current vdataframe.

This is achieved using the jQuery dataTables library. It comes with its own style, so although we can make it as similar as possible as a normal vdataframe html table there will be some differences. For now there are only the search bar, the page length and the previous/next buttons are supported but more features will be added.
This has been tested with only 3 vdataframes so more feedbacks are highly appreciated.
An interactive table will look like the picture below:

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


Add zsh-autosuggestions module

I like following zsh script which offers based on the zsh-history a possible completion candidate which can be accepted with <ctrl-f>.
https://github.com/tarruda/zsh-autosuggestions
It feels like advertised unobtrusive and fast.
What I like most about zim compared to the many other zsh frameworks, is its speed. So I do not want to suggest feature creep or new modules which slow zim down which would undermine the spirit of zim.
Any critical thoughts are welcome.

This seems like something I may include. Let me play with it (and test speed/usability) over the next few days.

Thanks for considering it.
BTW, the repository has moved to https://github.com/zsh-users/zsh-autosuggestions

Yeah, no problem. I may let it mature a bit and may even do some work on it myself; would be nice to integrate syntax-highlighting into it, if that hasn't already been done. But at some point, this will most definitely get pulled into zim. I like this feature in fish. Moving this into Zsh is extremely cool; a combination of history-substring-search, syntax-highlighting, and zsh-autosuggestions makes for a (basically) close-to-POSIX fish shell. Good stuff being done by zsh-users.

I took a look at this again. It seems there are still a few bugs to be worked out. Additionally, there's a proposal to implement async support. I would really like to have that as a feature before I implement it here. One of the main goals of zim is to keep things fast.

As an update, I'm waiting for the following issues to be resolved (as the minimum requirement for inclusion):

[ ] pasting is slow when using bracketed-paste-magic
[ ] plugin's strange behavior after commands with unicode character
[ ] Evals need escaping

There may be additional issues that are discovered between now and the time of inclusion. I will do my best to add those to the list above. Additionally, more issues may arise when combining this with zsh-syntax-highlighting.
I will re-evaluate this in a couple of weeks.

I'm using zsh-autosuggestions and https://github.com/zsh-users/zsh-autosuggestions/issues/136 made using mc terrible.

Can't this be an optional module? I am using it for months and can't live without it any more. I don't care about midnight commander or "pasting is slow" e.g.
Currently I have to load and update it myself via
if [[ ! -d ~/zsh-autosuggestions ]]; then
  git clone git://github.com/zsh-users/zsh-autosuggestions ~/zsh-autosuggestions
fi
source ~/zsh-autosuggestions/zsh-autosuggestions.zsh

Would be great if zim could support this even if only as experimental feature or something like that.

@Eriner
+1 bijancn
I will really helpful to add this module with disabled by default. People who are used to it find it very helpful.

@Eriner You mentioned that you want to wait till certain issues have been resolved. I think the last one has been closed 26 days ago.

The slow mc issue is still present.

@Inicola sorry, I didn't see this. However, not everyone uses mc. I think, if it's disabled by default, it does not interfere with your usage. Adding a note to this module, that mc user shouldn't enable this, would be sufficient.

@kiryph of course; I don't care either way. I was using something like @bijancn's method and mc -u (to disable the subshell), but I finally removed zsh-autosuggestions today.

The mc issue is closed now. Would really love to see this feature in zim.

Works fine for me now, it seems. Unless I encounter any problems, I'd love to see this merged.

Cool! Thanks a lot!


stageless shellcode exit

execute the stageless shellcode and just exit

Can you tell me more about the test environment? OS, architecture, loaded CNA scripts, loader implementation (how is memory allocated, written, executed).

win10, cs4.7, x64, example.profile, only load aceldr.cna,
use   runshc64.exe from https://github.com/hasherezade/pe_to_shellcode/releases/tag/v1.1 to execute the stageless bin

The problem is here: https://github.com/hasherezade/pe_to_shellcode/blob/4badc3b769ce7c1ceb6f2d098516bfca82ecd94d/loader_v2/peloader.cpp#L174
This loader appears to cast the shellcode as a function pointer, executes it, and then returns. As stated in the readme, AceLdr is not compatible with loaders that rely on the shellcode thread staying alive. Try adding a WaitForSingleObject((handle)-1,infinite); below that line to keep the loader from exiting.

i will try later, thank you so much!

it works well.
btw, i can't build the raw petoshellcode project, but i build a new shellcode loader by golang to test this


Fix bad indentation in bot config file.

This indentation was breaking the bot initialization.

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


Feature request: Terminal connect to running container

Thanks for this great tool!
Is it possible to add a terminal tab to connect to running container to execute some scripts inside?

This sounds like a great feature. The team is currently brainstorming how this would work. It's fairly complex as we don't currently have a terminal tab component.

I put together some thoughts on this. I'm still thinking about this and will have some more edits later, but wanted to get this out so we could start the conversation.
https://hackmd.io/@wwitzel3/octant-container-exec

Some notes:

Browser terminal should support clipboard events
Where in the UI should be tracking all the existing terminals?
When do the terminal connection close?
Notifying user if terminal disconnects for other reasons
Look into xterm support for resizing

I added some details about handling terminals in the UI and how we are going to deal with timeouts and disconnects. xtermjs supports resizing and clipboard/mouse support.


Can I use this for paid app validation?

I am searching long time for protect my application from sharing, for this purpose I am not published my application yet. First I want to know can I validate the paid app or not? If yes then how can I validate? Do I need to save anything like receipt? Can you please explain whole details?

you could probably use this funtion at app start up and look to see if it bought it?
https://github.com/cranberrygame/cordova-plugin-payment-iap/blob/master/example/basic/index.html#L90
im not sure i am not that concerned about it.