Support for function "wrappers"

It would be cool if PSScriptAnalyzer had a way to support different "function keywords". For example when using PSake to create build files the build tasks are captured in a special kind of function like this:
Task Compile -Depends Clean {
   "Compile"
 }

The problem lies in the fact that the Compile "Task"/function is not checked by PSScriptAnalyzer. Maybe a possible solution would be to offer users a way to register other "function keywords" (like "Task" in the example).

Just thinking out loud, but tools like PSake should probably ship with their own PSScriptAnalyzer rules and rule sets.  That seems like a logical way to solve this problem.  I don't think PSScriptAnalyzer should have rules for non-core functions/features, but community members can extend PSScriptAnalyzer so DSL tool makers should probably create extensions that ensure their DSL is used correctly and that best practices are followed.

@KirkMunro Very good point. Is there already an extension mechanism?

We are already doing this with the Configuration keyword. @raghushantha: can you provide guidance here? Thanks


ClientCorsOrigins?

Question
Is there a reason "Skoruba.IdentityServer4.Admin.BusinessLogic.Services.ClientService.GetClientsAsync" doesn't include the "ClientCorsOrigins"?  Is there a way I can get them using the admin API?
Thanks!
Brad.

Actually, I figured out how to get them (by getting each client by id), but I guess the question remains. :)


delete entities

Hi @Vertice, (cc'ing @nherment)
seems that deleting entities doesn't work.

there's a passing test for this


MAJOR ISSUE: we have over 100 open issues.

well, now we have....

Thanks....

No problem, Bernd, my pleasure. I have a couple of issues to open in my mind in case we ever drop below that magic line again. This repo is  :100:!

We can close this!! (for now)
:fireworks: :champagne: :tada:

I'll be back!!!! :muscle:

AAAND WE'RE BAACK!
:muscle: :100: :muscle:


2.2/small fixes for #95 and #96

Solves #95 and #96. Note that this is a pull without migrations, because the only thing that had to be migrated is the related_name="children" line in models/propoals.py that should already be in the code. I will make sure that line is not duplicated after automatically merging.

Looks good.
One small note:
You're using translations for new/revised in the mail... Considering the mail isn't translated at all, that's not really necessary.
Additionally, making new_or_revised a boolean and using an if/else in the template would keep the text in the template.

Looks good.
One small note:
You're using translations for new/revised in the mail... Considering the mail isn't translated at all, that's not really necessary.
Additionally, making new_or_revised a boolean and using an if/else in the template would keep the text in the template.


Revamp runtimeCaching.options to account for new plugins usage.

R: @addyosmani @gauntface
Fixes #1088

Changes Unknown when pulling f319ddfd404f3bbf5f71919d02069e41269222a7 on runtime-caching-plugins-update into ** on v3**.

This PR takes the current functionality in v3 and pretty directly migrates it to support the new Plugin-based approach to configuring everything.
I also filed https://github.com/GoogleChrome/workbox/issues/1096 to track a larger discussion about runtimeCaching.options in v3, and that might lead to follow-up PRs depending on what the resolution is.


🧪 test: add delete test exact

fix

截断读取写入错误

test

添加截断读取写入测试

Pull Request Test Coverage Report for Build<PHONE_NUMBER>1
Details

23 of 26 (88.46%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 71.652%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/rfuse_core/src/sys_fs.rs
9
10
90.0%

crates/rfuse_core/src/tmp_file.rs
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
0.1%

Covered Lines:
1236

Relevant Lines:
1725

💛  - Coveralls


docs: fix the emoji deprecation message and invalid file name

Fixes the following minor issues:

reference to invalid .yaml file
deprecated emoji warning (ref: https://github.com/squidfunk/mkdocs-material/discussions/6207)
extra character in output

/lgtm
/approve


extra newlines in jenkins

Larastan Version: 0.2.10
--level used: any

Description:
I run larastan as part of my CI flow in Jenkins. There is an annoying issue with larastan compared to running phpstan manually.  Im including a link to a screenshot that shows the issue, first run is larastan, second run is phpstan.  In larastan extra newlines get introduced.
http://shot.ter.net/img/201809191315-6e572f53592cbb3967d7b9fddaab45b9.png
Any idea what could be causing those?

I think with 0.5, this is no longer a problem.


Target release-v2.8 for dependabot

@mjura can you bump golang.org/x/net to 0.17.0 as part of the same PR?

This change is only about bumping go lang module, dependabot configuration will updated in other PR


How kerckhoffs principle is applied in cryptography

This fixes #4247

Hi @leence00
Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept. Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content. Be sure to see our resources page to see more info on plagiarism and what is considered as such.
How kerckhoffs principle is applied in cryptography #5074 Copyleaks Report.pdf

hello @WanjaMIKE have fixed the plagiarism

finishing up

Finishing up

@leence00 I had to abort my review because I am understanding the direction of the article. You started well but in the middle of it, you lose it. There are numerous repetitions that have affected its quality. You will need to rework and resubmit. Thanks


Mocha runner's EventEmitter does not work correctly in parallel mode

Prerequisites

[ x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[ x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[ x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[ x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description

The EventEmitter does not work correctly with parallel mode. It executes callbacks after all tests done, not after event.
I am using mocha programmatically like that:
runner.js
const Mocha = require("mocha");

function mochaRunParallel(file) {
  const mocha = new Mocha({
    parallel: true,
  });

  mocha.addFile(file);

  const testRunner = mocha.run(() => {
    console.log(`All Done For ${file}`);
  });

  // This event emitter will not work propertly
  testRunner.on("pass", () => {
    console.log("TEST PASSED");
  });
}

mochaRunParallel("./simpleTest.js");

simpleTest.js
const sleep = (ms) => new Promise((res) => setTimeout(res, ms));

describe("Event Emitter does not work correctly in parallel mode", () => {
  it("test 1", async () => {
    await sleep(1000);
    console.log("test 1 done");
  });

  it("test 2", async () => {
    await sleep(1000);
    console.log("test 2 done");
  });
});

Steps to Reproduce

Create a file "runner.js" with the code that I provided.

Create a file "simpleTest.js" with the code that I provided.

Run "node ./runner.js"

Expected behavior: [What you expect to happen]
I expected to see a console.log() after first test passed.
Actual behavior: [What actually happens]

But the actual behavior is a console.log() after all tests are done.
The same behavior occurs with "failure", "test end", and other events. But if you remove "parallel" flag everything is working as expected.
Reproduces how often: [What percentage of the time does it reproduce?]
It reproduces 100%.
Versions

The output of mocha --version and node node_modules/.bin/mocha --version: mocha version = 8.2.1
The output of node --version: node version = 15.6.0
Your operating system

name and version: Windows 10
architecture (32 or 64-bit): 64-bit

Your shell (e.g., bash, zsh, PowerShell, cmd): cmd

Quick update: the latest version (8.3.0) still has the same issue.

I'm pretty sure this effect is by design. It is explained here: https://mochajs.org/#parallel-mode. Since tests are executed in parallel processes (note: processes not worker threads), they are only reported back to the main process after a test file is executed.
What is it exactly that you try to accomplish?

I'm pretty sure this effect is by design. It is explained here: https://mochajs.org/#parallel-mode. Since tests are executed in parallel processes (note: processes not worker threads), they are only reported back to the main process after a test file is executed.
What is it exactly that you try to accomplish?

I am trying to track the progress of tests(I am using Mocha programmatically). This is very easy to do with serial-mode, like this:
runner.on ('pass', callbackFunc);
And as far as I understand, there is no way to track the execution progress of tests in parallel-mode?

No there isn't at the moment. Each test runner worker process reports back only once at the end, so you'll always see them buffered.
The only workaround I can currently think of is to add a afterEach root hook and using that to report status back. to your reporter, via a socket / named pipe.

No there isn't at the moment. Each test runner worker process reports back only once at the end, so you'll always see them buffered.
The only workaround I can currently think of is to add a afterEach root hook and using that to report status back. to your reporter, via a socket / named pipe.

I'm not sure if I fully understand this part:"using that to report status back. to your reporter, via a socket / named pipe."
In this case, we still won't be able to tell which test ended, right?

Per #5027, we're not looking to make major changes to Mocha at this point. Which would leave just the type: question parts of this thread.

we still won't be able to tell which test ended, right?

From https://mochajs.org/#available-root-hooks:

As with other hooks, this refers to to the current context object

...so you should be able to view the test information from this.
If I'm wrong about that, please do file a new issue with the docs template. We should treat me being wrong here as a docs bug. 🙂


feat: add batch_config handling in append_builtin_config()

Resolves #1571
I discovered this when trying to configure another tap's config json schema.

:books: Documentation preview :books:: https://meltano-sdk--1572.org.readthedocs.build/en/1572/

@edgarrmondragon - I'm not able to add any further commits to this branch. What are your thoughts about getting this merged?
I think we had a failure specific to python3.8 but I didn't dig deep into that issue to analyze root cause.
As a quick first step, do you think you could update this branch from main and see if test is still failing?
Based on that info, I may better be able to say if I would have to open a new PR, or conversely if you feel comfortable to get it merged on your side.

@edgarrmondragon - Thanks very much for your help on this. I'm excited to see it merge.
I noticed that it is still in auto-merge state and I don't have permission to disable that.
I'm hesitating to mark resolved the final conversation thread above because that (probably?) will trigger the merge. But if you feel comfortable with this, you can go ahead and do so. 👍  For my side, it looks like this is ready to go thanks to your additional commits. 🙏


.sand problem

Excuse me,
I want to use .send send a message will have a speaker and speaker the front of things
Is there any way to simply display the text? (Do not show other things, only the text is good)
(The previous version did not have anything in front of the speaker and speaker)

update your bot. if you're on windows - wait.


Cannot sign in - We're currently unable to complete your request.

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[x] Documentation issue or request
[ ] Other... Please describe:

Browser:

[x] Chrome version 72
[ ] Firefox version XX
[ ] IE version XX
[ ] Edge version XX
[ ] Safari version XX

Library version
Library version: 0.2.4
Current behavior
After entering the email address in the login popup, I'm redirected to a page that says: We're currently unable to complete your request.
Expected behavior
Proceed with the sign in process.

I'm pretty certain that this is a configuration issue with my app registration in the Azure portal as I tried using this page with my client id, and it failed too. However, by now I tried every possible combination of settings. What configuration would I need for example to use my application with the above mentioned tool?
My understanding is that

I do not need any web redirect URIs
I need the suggested public redirect URI msal<client_id>://auth
I don not need to provide access token/id token with the authorization endpoint

Are these assumptions correct?

From the client side you should provide:

clientId  <== from your registered app
resource  <== https://login.microsoftonline.com/YOUR_TENANT_NAME.onmicrosoft.com
redirectUri  <== Something like http://localhost:8080

The redirectUri from the client side should match what you have set in your registered Azure app.
The authorization endpoint will return an id_token from which you can get an access_token.


getTeacher

@mbeier-tgm please implement following function /getTeacher?id=1234
Input:
id of the teacher
Output:
{
UUID: 1234,
Short: "szakall",
Longname: "Stefan Zakall",
AV: false,
PEK: false,
Administration: false
}

implemented in bb4bf90
The endpoint /getTeacher responds to a GET-Request when a query parameter uuid containing the uuid of the teacher and a valid access token is provided as authentication.


ivi-share: create ivi-share.so

Normally, wayland applications should generate wayland files from xml file via wayland-scanner.
In preparation for the case which the scanner can not be used, ivi-share.so is created. (e.g. 3rd party application)
Signed-off-by: Kenji Hosokawa<EMAIL_ADDRESS>

Sorry for my inadequate check. I modified it. Please check it again.


Refactorings for loading this plugin faster

I did some refactorings mainly for loading this plugin faster (and fixing some global scope pllution).

Move implementation into autoload/ directory to defer loading plugin until omni completion is executed
Fix variable prefixes not to pollute global scope and to stop variables living longer unnecessarily
Improve file path separator for Windows
Fix indentation

I believe I fixed all the points. Could you review additional fixes? Diff is below:
https://github.com/rhysd/vim-racer/compare/d6f3d30803d193406fcbb8f5130eb993137749a9...2b029aab0e97fd32a18085473734ab3cc055f31c

Almost good.
Please fix the new comments.

Thank you for catching them. I fixed.

Nice.  Merged.

Thank you for your review.


Low accuracy & tiny-imagenet bugs

I ran the pytorch code and got a completely different result than the paper.
Thus, I ran the paddle code with your default command with --clsmodel resnet18. The results were still quite different from the paper.
After viewing code, I found no netC.eval() or tiny-imagenet pre-processing. This means that the tiny-imagenet result of the publicly available code cannot be achieved. The test_acc is also somehow incorrect.
Why tiny-imagenet32 is in code? tiny-imagenet and tiny-imagenet32 result "Invalid atk model".

Did you find a solution for the tiny-imagenet implementation? I have been trying to apply it and I keep getting errors.


import type should not have any effect on output code

import type declarations should not appear in the JS output and should not have any effect on the JS output.
As of 4.0 adding import type to a file causes export {}; to be added to the output. This worked in 3.8
This breaks components that use ES modules syntax (because the rest of project also uses it) but will not be loaded as modules. Examples include service workers, web workers, shared workers and custom elements loaded as side effects.
This is a breaking change with no workaround possible in TS. External workarounds are possible.
The general case has already been raised as #41513, this issue is specifically for the subset where the files only contain import type declarations and no plain import statements.
The documentation for import type states:

import type only imports declarations to be used for type annotations and declarations. It always gets fully erased, so there’s no remnant of it at runtime.

This was the case in 3.8, it is not the case with 4.0
TypeScript Version:  4.0.5
Search Terms: import type, export {}
Code
Using import type in a file so that TS can check types:
import type { InterfaceType } from './MyLibrary';
const test: InterfaceType = {};

Note that this file is not a module and will not be loaded as a module.
Expected behavior:
JS output should not include any reference to the import type declaration:
const test = {};

Actual behavior:
JS output includes export {}; to force the output to be a module:
const test = {};
export {};

Related Issues:

Bug in Webpack this change was introduced to fix: https://github.com/webpack/webpack/issues/10889

Not all TS users also use Webpack, is it a pre-requisite now?

Design meeting where problems this change introduces were dismissed: https://github.com/microsoft/TypeScript/issues/38713

Apparently "They will have a point", though it's not clear whether anything followed from that.

Change to always export {}; where this exact issue with import type was already identified: https://github.com/microsoft/TypeScript/issues/38696#issuecomment-699558340
Bug raised for general case: https://github.com/microsoft/TypeScript/issues/41513

Duplicate of #41513.

@MartinJohns It isn't because #41513 is the general case, i.e. don't always emit export {};
This issue is for the specific case where there are no import statements in the JS output. Even if you accept that #41513 is by design because export {}; is strictly spec compliant (and I don't) in this case that spec should not apply.

I thought #41513 explicitly mentioned "import type" as well. But my impression was still that it's intentional that any use of module-syntax (aka import/export) leads to the file being treated as a module.
This impression aligns with the comment by @andrewbranch in the PR that added type-imports: https://github.com/microsoft/TypeScript/pull/35200#issuecomment-645565073

When you write an import type declaration, it’s essentially the same as writing an import declaration that you never use in an emitting position, except that it’s enforced that you never use it in an emitting position. Now, since import type is not standard ES grammar, I think you could reasonably argue that we could implement whatever rules we wanted; that it would not be inherently incorrect to say that import type does not constitute a module. But ultimately, given how similar it is to writing a regular import of a type, I think maintaining consistency that all import declarations are module markers was the correct choice.

@MartinJohns In that case this bug would become with the documentation.

I think you could reasonably argue that we could implement whatever rules we wanted;

I agree, but in 3.8's release the statement on import type was

import type only imports declarations to be used for type annotations and declarations. It always gets fully erased, so there’s no remnant of it at runtime. [my emphasis]

This needs to be amended in the 4.0 release notes and documentation to something like:

By using import type you are telling TS that you want to force the output to be a module, so the JS output will always include export {}; for consistency, even if there are no plain import statements.

It would also be really helpful to have some documentation, anywhere, on what we should do instead? Is the TS design intent that web workers/service workers/custom elements/etc should not be able to share type definitions with ES module code? I really don't want to have two versions of './MyLibrary.d.ts', one for import and another for /// <reference path="..." />. That used to be the case and it was a PitA.
Finally I disagree entirely with:

I think maintaining consistency that all import declarations are module markers was the correct choice.

If import and import type behave the same for consistency then what is the point of import type in the first place? In what context would I ever use import type if it always behaves consistently with plain import.
I'm using import type because I want the design/transpile time definition specifically without changing my JS output.
Specifically the assumption that all files that include import type are intended to be modules is wrong, sometimes. We can argue about whether that intent is more one way or the other, but what it does do it break all places where import type was used and not intended to output a module.
At the very least I think this needs to be configurable within TS. If you think the most common intent is that import type should force module output then: fine, make that the default, but we can't opt out.
Out only options are:

Don't use import type, or
Don't use TypeScript 4, or
Add additional build steps to strip this bug out so that the JS works again.

I agree, but in 3.8's release the statement on import type was

import type only imports declarations to be used for type annotations and declarations. It always gets fully erased, so there’s no remnant of it at runtime. [my emphasis]

There is no remnant of import type at runtime.

This needs to be amended in the 4.0 release notes and documentation to something like:

I agree that fixing the bug should be mentioned in the breaking-changes section of the release notes.
But the behavior is mentioned on the documentation regarding modules: https://www.typescriptlang.org/docs/handbook/modules.html

In TypeScript, just as in ECMAScript 2015, any file containing a top-level import or export is considered a module.

You're having a top-level import, so the file is a module.

If import and import type behave the same for consistency then what is the point of import type in the first place? In what context would I ever use import type if it always behaves consistently with plain import?

The purpose of import type is described in the PR that I linked.

I'm using import type because I want the design/transpile time definition specifically without changing my JS output.

Then you're using it for something it was not designed or intended for.

There is no remnant of import type at runtime.

Apart from, you know, the export {}; that is a remnant of the import type at runtime and that wouldn't be there if I'd just used any.

But the behavior is mentioned on the documentation regarding modules: https://www.typescriptlang.org/docs/handbook/modules.html

Er, ok, let's look: https://www.typescriptlang.org/docs/handbook/modules.html#importing-types:

import type is always guaranteed to be removed from your JavaScript

Oh, ok then.

You're having a top-level import, so the file is a module.

There is no top level import in my JS file. Why does it have to be a module?

Then you're using it for something it was not designed or intended for.

I guess, but it's something that did work, now doesn't, and that there is no workaround for other than either opt out of TS or add something that fixes TS output afterwards. I don't get how this is not a problem with TS.

Anyway, I'm going to unsubscribe.

Fair enough, thanks for the help.

The fix for this is to replace all instances of import type X with import(...).X:
- import type { InterfaceType } from './MyLibrary';
+ type InterfaceType = import('./MyLibrary').InterfaceType;

I still think the side effect of import type is very obtuse to anyone not directly involved in writing it, and some kind of documentation explaining that import type will always force the JS output to be a module would be helpful.


Add new ScyllaDB metrics

What does this PR do?
Updates our integration to support the current latest version of ScyllaDB.
Motivation
The ScyllaDB integration hasn't been updated since ScyllaDB 3.1. Scylla only supports the two most recent versions released, so currently the Scylla integration does not support a supported version of ScyllaDB. There are 12 version upgrades worth of metric additions/renames upstream has created.
Additional Notes
https://github.com/DataDog/integrations-core/issues/15578
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

Can you add a change log entry to this under the unreleased section?


Feature/moviecard

Description
Updated the sizing of movie cards and on adjusting grid of overall watchlist

functionality you created/updated

Type of change

[ x] Bug fix (non-breaking change which fixes an issue)
expected)

Change Status

[ x] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?
Checklist

[x ] My code follows the style guidelines of this project
[ x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x ] There are no merge conflicts

@jvillalp let's make sure we are cleaning the formatting for the Pull request checkboxes, I think you just need to delete the space between the brackets and the 'X'

@jvillalp let's make sure we are cleaning the formatting for the Pull request checkboxes, I think you just need to delete the space between the brackets and the 'X'

Didn't even realize that. WIll do!

For Desktop are we keeping everything single column? I deployed this branch and on the explore page it loaded as pic attached


non-zero exit status 2 while running python setup.py develop (exiting after building target assimp)

Hello,
I'm having trouble building from source. At first I thought it was similar to #17 , but the build seems to fail a little earlier, right after finishing to build assimp.
I've tried doing the checks @alex-petrenko recommended in #17 and I am getting the expected outputs.

First of all, please make sure that you executed the setup_env script in Vulkan SDK, i.e. following the instruction:
$ cd vulkansdk/<IP_ADDRESS>
$ source ./setup-env.sh
After you've done this, check that VULKAN_SDK env variable is set by running this in your terminal:
$ echo $VULKAN_SDK
To make sure the SDK headers contain the correct macros (the build procedure seems to be complaining about VK_ERROR_UNKNOWN), can you please search for it in the SDK folder, i.e. like this:
$ grep -r 'VK_ERROR_UNKNOWN' ./x86_64/include
Expected output is something like:
./x86_64/include/vulkan/vk_enum_string_helper.h:        case VK_ERROR_UNKNOWN:
./x86_64/include/vulkan/vk_enum_string_helper.h:            return "VK_ERROR_UNKNOWN";
./x86_64/include/vulkan/vulkan.hpp:    eErrorUnknown = VK_ERROR_UNKNOWN,
./x86_64/include/vulkan/vulkan_core.h:    VK_ERROR_UNKNOWN = -13,

However even if all the test commands run fine (as well as the ones on the vulkand sdk website), I have noticed that the vulkan-sdk is supported for Ubuntu 20.04 and over. I am running Ubuntu 18.04.
Full output of the build command: setup_outputs.txt

Other things I've tried:

building my environment from the provided environment.yml : same issue.
building the docker image: the link to download vulkansdk-linux-x86_64-<IP_ADDRESS>.tar.gz and I couldn't find a working one.
modifying Dockerfile.base to the setup instructions in the readme: same issue, built process fails after assimp.

RUN tar -xzf vulkansdk-linux-x86_64-<IP_ADDRESS>.tar.gz

ENV VULKAN_SDK=/vulkan/<IP_ADDRESS>/x86_64
ENV PATH=${VULKAN_SDK}/bin:${PATH}
ENV LD_LIBRARY_PATH=${VULKAN_SDK}/lib:${LD_LIBRARY_PATH:-}
ENV VK_LAYER_PATH=${VULKAN_SDK}/etc/vulkan/explicit_layer.d

RUN vulkaninfo

WORKDIR /

RUN cd /usr/bin \
    && ln -s python3 python \
    && ln -s pip3 pip

RUN curl -LO http://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh && \
    bash Miniconda3-latest-Linux-x86_64.sh -p /miniconda -b && \
    rm Miniconda3-latest-Linux-x86_64.sh

ENV PATH=/miniconda/bin:${PATH}
RUN conda update -y conda && conda --version

WORKDIR /workspace

RUN git clone https://github.com/alex-petrenko/sample-factory.git
RUN git clone https://github.com/alex-petrenko/megaverse.git
WORKDIR /workspace/megaverse

RUN conda env create -f environment.yml
RUN conda init bash
SHELL ["conda", "run", "-n", "megaverse", "/bin/bash", "-c"]

RUN git submodule update --init --recursive
RUN python setup.py develop
RUN pip install -e .

Hi @francelico !
Do you think this is Ubuntu 18-specific? I.e. it works on 20 but fails in 18?
It would be very helpful if you could run again with make -j1 to do the build in a single process. Because at this point it's not actually clear what's failing. Like I don't see a clear compilation or linking error in the logs.

You can do it by adding arguments -j and 1 here https://github.com/alex-petrenko/megaverse/blob/c38436d69b7a2b6d77ed9de06f6a5e69251696e3/setup.py#L105
You can also manually run in the terminal from the root of the project:
mkdir build
cd build
cmake ..
make -j1

Hi @alex-petrenko ,
I don't think this is distribution specific as I have the same error on a clean install of 22. I didn't try 20 yet though, should I?
Log output with -j1 option
out.log

@francelico sorry maybe I'm missing something but the log looks like it just abruptly ends. I don't see any compilation or linking errors. Does the build just stop here? Can you make sure you log both stdout and stderr, without seeing the error it is hard to understand what is happening.

Hi @alex-petrenko , apologies for the delayed reply. Indeed I double checked and I was only logging stdout in my original file. I'm attaching the full log with both stdout and stderr.
out.log

@francelico frustrating as it might be, I still have no idea what the actual error is. I can't find a concrete linking or compiling error in the logs. I can indeed see that the build is failing (with the error code 2) but it's impossible to figure out why without seeing the actual compilation output.
There's a million warnings from different libraries we include, but no errors to be seen.
I recommend that you try a standalone build, i.e. just regular cmake and then make, without the Python libraries first. You can pass the option -j1 to make to make sure it builds single-thread and stops immediately when the compiler fails. You can then just copy-paste the error from the terminal.
Building C++ programs from sources can be frustrating like this, I guess this is one reason everyone uses python for everything. But hey, you can't write a million FPS renderer in Python :)

@alex-petrenko indeed, that huge boost in FPS alone makes it worth it to fight a bit for it :)
Building from the command line fails much earlier and throws a different compilation error (I am building from the src/ directory as there is no CMakeList.txt at the root). Attaching the log
out.log

@alex-petrenko indeed, that huge boost in FPS alone makes it worth it to fight a bit for it :)
Building from the command line fails much earlier and throws a different compilation error (I am building from the src/ directory as there is no CMakleList.txt at the root). Attaching the log
Uploading out.log…


Dragging VSCode window with NSWindowShouldDragOnGesture on macOS no longer works

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

VS Code Version: 1.96.0
OS Version: macOS 15.1.1

Version: 1.96.0
Commit: 138f619c86f1199955d53b4166bef66ef252935c
Date: 2024-12-11T02:29:09.626Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0

Steps to Reproduce:

Enable NSWindowShouldDragOnGesture
defaults write -g NSWindowShouldDragOnGesture -bool true

Try to drag the window while holding ⌘+control

Context window opens instead.

References
https://mmazzarolo.com/blog/2022-04-16-drag-window-by-clicking-anywhere-on-macos/

Same here, really infuriating. Started happening yesterday.

I can confirm from my side that this is an regression. Running 1.95.3 on Apple Silicon downloaded from https://code.visualstudio.com/updates/v1_95 works as expected.

Can confirm here as well. Dragging worked normally until VS Code updated itself and restarted today.

Some extensions already stopped being compatible with 1.95.3 (Jupyter notebook support) so downgrading to version that didn't have the problem stops being a valid workaround.


Added auto commenting feature on issue creation

Fixes #33

Please merge this pull request and add the labels as per gssoc guidelines.


Add note between headline and table, that the shop information are from "Stand: 11.12.2020" (see ppt changes)

tested and is Okay


[FEATURE REQ] Please add method RenewMessageLockAsync to ServiceBusMessageActions (isolated worker process model)

Library name
Microsoft.Azure.Functions.Worker.Extensions.ServiceBus
Please describe the feature.
Greetings,
Please add the 'RenewMessageLockAsync' to the 'ServiceBusMessageActions' class of the 'Microsoft.Azure.Functions.Worker.Extensions.ServiceBus' library, as was requested in feature request, in the Azure Function IsolatedProcess libraries to the ServiceBusMessageActions class.
This prevents us from migrating from 'In-process model' to the  'isolated worker process model'.
Thanks in advance!
Note: Similar to feature request which is in a similar library, but is part of the InProcess Azure Function libraries
The In-process model class vs the isolated worker process model class.

@JoshLove-msft @mattchenderson for awareness

@liliankasem @JoshLove-msft @mattchenderson Any update on this topic?

Any update on this? Thanks

Any update on this guys?

This is a problem in our solution as well. Is there any update to report?

Experiencing the same issue and would greatly appreciate this feature being implemented.

Same issue here, Its blocking us to migrate to .net 8 as the isolated model seems to be the way forward.

Wanted to provide an update on this. This has been reviewed and it's a valid request, but it is not yet assigned and we don't have an ETA on implementation at the moment.
We'll keep this updated when we have more to share.

Also, if folks flagging this as a requirement could please share more details about your scenario (how/why you're using RenewMessageLockAsync in your function code), what would help us track them and prioritize the work.
In most cases, the host will ensure this is done and the lock is not lost, so we're tracking the scenarios where this is still required.

When we did some performance testing we saw it did happen locks were expiring so we added a precautionary check and renewed the lock if it was too close to expiration. As a workaround we lowered our prefetech count and will use the abandon-method to release the messages.

Also, if folks flagging this as a requirement could please share more details about your scenario (how/why you're using RenewMessageLockAsync in your function code), what would help us track them and prioritize the work.

@fabiocav Do you know if this change was prioritized already? We would like to know if we need to start considering implementing a work-a-round. This is an impediment for us to migrate to .Net 8 which is due to '12 November 2024' and we have over 200 Azure functions to migrate to the isolated model and then to .Net 8.

One use case is: In case the message handling does not end up as expected, I want to retry the message later (with some jitter in order for the other messages not being retried at the exact same time.
I may also want to have different message renewal delay, depending of the business issue that occurred.

Also, if folks flagging this as a requirement could please share more details about your scenario (how/why you're using RenewMessageLockAsync in your function code), what would help us track them and prioritize the work.
In most cases, the host will ensure this is done and the lock is not lost, so we're tracking the scenarios where this is still required.

we have long running functions that should remain running, hence we need to be able to extend the lock for the duration of the request.

So, apparently the 'RenewMessageLockAsync' is added to the code in version 5.16.1 of the package 'Microsoft.Azure.WebJobs.Extensions.ServiceBus'. (See: github)

So, apparently the 'RenewMessageLockAsync' is added to the code in version 5.16.1 of the package 'Microsoft.Azure.WebJobs.Extensions.ServiceBus'. (See: github)

Do you know when will the changes be include to package 'Microsoft.Azure.Functions.Worker.Extensions.ServiceBus'?
@fabiocav


Updating client

I've been using this for Roblox for a week or two now, but it's been saying that it needs an update recently and I'm not sure how to do this.

Could you take a screenshot of the message?

Nevermind, I just opened it now and I guess it figured it out. For the last
couple of days it had been crashing and saying that Roblox needed an update
to run. I suppose it's automatically updated whatever it is now. Thanks
anyways. I'll let you know how it goes.
On Fri, Sep 1, 2023, 11:06 AM Bugadinho @.***> wrote:

Could you take a screenshot of the message?
—
Reply to this email directly, view it on GitHub
https://github.com/CorkHQ/Cork/issues/17#issuecomment-1702903779, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/BCI23BDELM4NPTZQ2GFUYCDXYH2YBANCNFSM6AAAAAA4G2BLIE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Alright then, keep in mind however that if you are using the zintegration channel, you can safely remote it now, as Wine support already reached the live channels.


Why the ThreadPoolExecutor corePoolSize = 0🙉

What is the purpose of OKHttp setting the corePoolSize in ThreadPoolExecutor to 0

If there is no traffic after 60 seconds we don't keep a thread hanging around doing nothing in the thread pool.
Tuning docs https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ThreadPoolExecutor.html
    private val executor = ThreadPoolExecutor(
        0, // corePoolSize.
        Int.MAX_VALUE, // maximumPoolSize.
        60L, TimeUnit.SECONDS, // keepAliveTime.
        SynchronousQueue(),
        threadFactory
    )

corePoolSize is the number of threads to keep in the pool, eve if they are idle.
Perhaps the comment of newCachedThreadPool can give you an answer.


We could use History.js for cross-browser compatibility

It would be nice if pjax supported History.js to solve those pesky cross-browser compatibility bugs and also optionally support HTML4 browsers.

@ckald: when I tried to use your merge of hashchange-event and pjax, I got this error in IE9 saying that .pjax is not a method. When I used the regular version of pjax, I did not get the error.
This is how I'm calling pjax (using jquery 1.7.1): $("a[href^='"+siteURL+"']:not([href*='/wp-admin/']):not([href*='/wp-login.php']):not([href$='/feed/'])").pjax("#primary");

@DogKnob as I remember, nobody didn't have problems with this. Leave an issue on https://github.com/ckald/jquery-pjax/ with a proof link please to continue discussion

@ckald: I did manage to get this working somewhat. I no longer get the error, but I'm having IE-specific issues with Wordpress now :(

@DogKnob Hey, i think defunkt doesn't wants us talking here not about his lib. Personally i won't flood here anymore. https://github.com/ckald/jquery-pjax


datastore: update to v1beta3

Fixes #872
Docs
http://stephenplusplus.github.io/gcloud-node/#/docs/master/datastore
Blockers

[ ] Datastore v1beta3 release
[x] #913 -- need it for testing test/datastore/request.js

To Dos

[ ] Update resource links (blocked by v1beta3's release (public docs required to get URLs))
[ ] Remove entry from Troubleshooting (https://github.com/GoogleCloudPlatform/gcloud-node/pull/1172)
[ ] Convert to gRPC
[x] Add support for env vars from cli (#1040):

[x] DATASTORE_PROJECT_ID
[x] DATASTORE_EMULATOR_HOST (protocol not included)

[x] Use Service & ServiceObject
[x] Tests

[x] Unit

[x] Entity
[x] Index (Datastore, formerly Dataset)
[x] Query
[x] Request
[x] Transaction

[x] System

[x] Readme snippet update
[x] Depend on a new release of protobuf.js (tracking)

:warning: Big Breaking Changes
Dataset isn't a thing anymore:
var gcloud = require('gcloud')({/*...*/});

Before
var datastore = gcloud.datastore;
var dataset = datastore.dataset();

dataset.get(dataset.key(['Kind', 1]), function(err, results) {});

After
var datastore = gcloud.datastore();
datastore.get(datastore.key(['Kind', 1]), function(err, results) {});

// Use a different project:
var datastore = gcloud.datastore({ projectId: 'grape-spaceship-123' });

Thanks for the review @pcostell! I'll be making some adjustments throughout the week and will ping if I have any questions.

No worries -- one more note, the url has changed. So for example for runQuery it is now:
datastore.googleapis.com/v1beta3/projects/:runQuery
Instead of www.googleapis.com/datastore/v1beta2/datasets//RunQuery

Starting the conversion to gRPC and I ran into an issue:
The Cloud Datastore API is not enabled for the project nth-circlet-705

I've emailed @pcostell about this, hoping it's just a matter of whitelisting.

I think you just have to enable it in the APIs page on
cloud.google.com/console

Sorry, I should have mentioned that it's enabled. It's the same project I use with Datastore that works without gRPC.

Have you tried it without gRPC recently? We just enabled the requirement to enable it in the APIs page -- I sent you a direct link as I think it is still unaccessible publicly.

I haven't, sorry the gRPC part wasn't related. For anyone following along, Patrick is going to enable the API himself after becoming an owner of the project.

@pcostell I'm having an issue running a query with a filter on a key. The code executes fine without error, but there aren't any results returned. Does anything look wrong from these:
commit
{
  "mutations": [
    {
      "upsert": {
        "key": {
          "path": [
            {
              "kind": "Person",
              "name": "name"
            }
          ]
        },
        "properties": {
          "fullName": {
            "stringValue": "Full name"
          },
          "linkedTo": {
            "keyValue": {
              "path": [
                {
                  "kind": "Person",
                  "name": "name"
                }
              ]
            }
          }
        }
      }
    }
  ],
  "projectId": "nth-circlet-705",
  "mode": "NON_TRANSACTIONAL"
}

runQuery
{
  "readOptions": {},
  "query": {
    "distinctOn": [],
    "kind": [
      {
        "name": "Person"
      }
    ],
    "order": [],
    "projection": [],
    "filter": {
      "compositeFilter": {
        "filters": [
          {
            "propertyFilter": {
              "property": {
                "name": "linkedTo"
              },
              "op": "EQUAL",
              "value": {
                "keyValue": {
                  "path": [
                    {
                      "kind": "Person",
                      "name": "name"
                    }
                  ]
                }
              }
            }
          }
        ],
        "op": "AND"
      }
    }
  },
  "projectId": "nth-circlet-705"
}

Your query isn't strongly consistent. Can you try with a parent and ancestor?

Ah, okay. This code works now:
var personKey = datastore.key(['People', 'US', 'Person', 'name']);

datastore.save({
  key: personKey,
    data: {
      fullName: 'Full name',
      linkedTo: personKey // himself
    }
  }, function(err) {
    assert.ifError(err);
    var query = datastore.createQuery('Person')
      .hasAncestor(personKey.parent);

Was it just luck that this test has been working until now?

This fails... should it?
var personKey = datastore.key(['People', 'US', 'Person', 'name']);

      datastore.save({
        key: personKey,
        data: {
          fullName: 'Full name',
          linkedTo: personKey // himself
        }
      }, function(err) {
        assert.ifError(err);

        var query = datastore.createQuery('Person')
          .hasAncestor(personKey.parent)
          .filter('linkedTo', personKey);

Hmm I think that should work. What's the proto getting sent?

commit
{
  "mutations": [
    {
      "upsert": {
        "key": {
          "path": [
            {
              "kind": "People",
              "name": "US"
            },
            {
              "kind": "Person",
              "name": "name"
            }
          ]
        },
        "properties": {
          "fullName": {
            "stringValue": "Full name"
          },
          "linkedTo": {
            "keyValue": {
              "path": [
                {
                  "kind": "People",
                  "name": "US"
                },
                {
                  "kind": "Person",
                  "name": "name"
                }
              ]
            }
          }
        }
      }
    }
  ],
  "projectId": "nth-circlet-705",
  "mode": "NON_TRANSACTIONAL"
}

runQuery
{
  "readOptions": {},
  "query": {
    "distinctOn": [],
    "kind": [
      {
        "name": "Person"
      }
    ],
    "order": [],
    "projection": [],
    "filter": {
      "compositeFilter": {
        "filters": [
          {
            "propertyFilter": {
              "property": {
                "name": "__key__"
              },
              "op": "HAS_ANCESTOR",
              "value": {
                "keyValue": {
                  "path": [
                    {
                      "kind": "People",
                      "name": "US"
                    }
                  ]
                }
              }
            }
          },
          {
            "propertyFilter": {
              "property": {
                "name": "linkedTo"
              },
              "op": "EQUAL",
              "value": {
                "keyValue": {
                  "path": [
                    {
                      "kind": "People",
                      "name": "US"
                    },
                    {
                      "kind": "Person",
                      "name": "name"
                    }
                  ]
                }
              }
            }
          }
        ],
        "op": "AND"
      }
    }
  },
  "projectId": "nth-circlet-705"
}

@eddavisson Any thoughts here? Could it be related to key normalization?
@stephenplusplus Does this work if you query for the fullName instead of linkedTo?

I can't reproduce this. I ran these two commands in our internal gRPC shell, and got the expected single result for the query.
Commit mutations:[{upsert:{key:{path:[{kind:"People",name:"US"},{kind:"Person",name:"name"}]},properties:[{key:"fullName",value:{string_value:"Full name"}},{key:"linkedTo",value:{key_value:{path:[{kind:"People",name:"US"},{kind:"Person",name:"name"}]}}}]}}],project_id:"eddavisson-e2e-prod",mode:NON_TRANSACTIONAL

RunQuery query:{kind:[{name:"Person"}],filter:{composite_filter:{filters:[{property_filter:{property:{name:"__key__"},op:HAS_ANCESTOR,value:{key_value:{path:[{kind:"People",name:"US"}]}}}},{property_filter:{property:{name:"linkedTo"},op:EQUAL,value:{key_value:{path:[{kind:"People",name:"US"},{kind:"Person",name:"name"}]}}}}],op:AND}}},project_id:"eddavisson-e2e-prod"

Thanks for checking @eddavisson. We have some differences in our commit request. Should mutations[0].upsert.properties be an object or array? I tried converting my request to the array format you used and the protobuf message parser didn't agree with that format.
For completeness, here's the runQuery response:
{
  "batch": {
    "skippedResults": 0,
    "skippedCursor": {},
    "entityResultType": "FULL",
    "entityResults": [],
    "endCursor": "CgA=",
    "moreResults": "NO_MORE_RESULTS"
  },
  "query": null
}

@pcostell querying for fullName = "Full name" doesn't return results either.

@stephenplusplus --
Are you sure the data is in Datastore? Can you send us the mutation result and double check the entity is in your viewer?

Yes, here's the result from the commit:
{ mutationResults: [ { key: null } ], indexUpdates: 5 }

In an earlier test, I do a commit and then a lookup. The commit returns similar results (a mutationResults array with a single { key: null } object), but the lookup succeeds.

The viewer (which I believe means https://console.cloud.google.com/datastore, lmk if that's wrong) seems to be hit or miss to see an accurate representation of the data. I tested by inserting completely new data [Kind: Stephen, ID: autogenerated], and received a successful response. When I went to the viewer, it appeared instantly. Then I inserted more new data [Kind: Stephen, name: Two]. Refreshed and saw it, but [Kind: Stephen, ID: autogenerated] was gone. Refreshed again and they both have been missing ever since. I kicked off 15 jobs through the admin panel to remove entities from 15 various kinds (not the newly created "Stephen"). All of those are still showing in the viewer even after the jobs completed.

The viewer (https://console.cloud.google.com/datastore) uses non-ancestor queries (unless you specifically create one in GQL), so the behavior you describe is possible.
After you run the test, can you see the entity ({kind:"People",name:"US"},{kind:"Person",name:"name"}) in the viewer?

No, I actually don't see anything in there. In the Entities section, there appear to be some remnants of the jobs that deleted all of the entities.

I'm able to save and do a lookup for the saved data, but it doesn't appear in the viewer or via runQuery.

Data should generally be visible in the viewer very quickly. Is it possible that the test is deleting the entity before you run the query? Or it's inserting the data into a different project?
A suggestion for isolating this: run just the code that inserts the entity, wait a few minutes, and see if it shows up in the viewer.

I'm embarrassed to say that was the problem with not seeing it in the viewer, which instantly led to me realizing the problem. Feel free to tune out now, 'cause it's the fault of this library. Thank you for your help!
Working with gRPC/protobuf.js means we have to convert camelcase to snakecase in certain places to comply with its API. It's not supposed to seep into user code, but clearly it has, since data the user saves under a property like "linkedTo" is being converted and saved as "linked_to". That's why the query didn't return any results.
Sorry to get you both involved in this, but thank you very much for helping me work through it.

Having some issues with upgrading gRPC. Issue logged here: https://github.com/grpc/grpc/issues/5972
I need to use updates since the last release of gRPC that include https://github.com/grpc/grpc/issues/5005 and https://github.com/grpc/grpc/issues/5006, so it's currently a blocker.

@stephenplusplus Do we need these grpc additions in order to launch v1beta3? If not, are there any blockers?

It's the last thing left aside from updating our docs to link to the v1beta3 docs once they're live. I'll take a look tomorrow if I can work around the grpc issue.

Unsure of when the next grpc release will be, I published http://npmjs.com/package/@stephenplusplus/grpc (npm install @stephenplusplus/grpc) which is the current state of the grpc library. It has everything we need (https://github.com/grpc/grpc/issues/5005, https://github.com/grpc/grpc/issues/5006, and some other fixes for unwanted logging output).
The PR is now complete.

@callmehiphop ptal. I'll squash this up after you've had a chance to check out the recent commits.

@stephenplusplus We are ready for you to merge this into master.

Is v1beta3 generally available? I've been using the response code of https://cloud.google.com/datastore/docs/apis/v1beta3 to tell me if it's live or not, and it's still a 404.

The docs and blog post won't drop until Monday, however the API can be enabled: https://console.cloud.google.com/apis/api/datastore.googleapis.com/overview

For users that already have Datastore enabled and have been running v1beta2, they won't have to re-enable the API, right?

Any projects active in the last 7 days will not need to re-enable.

Cool, thanks. And more generally, thanks for all of the help along the way! :+1:

Thank you for helping us get this out the door!
As a heads up, the cloud SDK will not have a grpc emulator at launch time. So users that want to use gcloud-node will have to use the gcd.sh tool directly, which they can get from here.

Release notes for Datastore available if you need to link to them: https://cloud.google.com/datastore/release-notes

@callmehiphop - all squashed.

:tada:

@pcostell any API flakiness going on? We are having inconsistent results querying for data:
Commit:
{
  "mutations": [
    {
      "upsert": {
        "key": {
          "path": [
            {
              "kind": "Person",
              "name": "name"
            }
          ]
        },
        "properties": {
          "f": {
            "stringValue": "Full name"
          }
        }
      }
    }
  ],
  "projectId": "nth-circlet-705",
  "mode": "NON_TRANSACTIONAL"
}

Query:
{
  "readOptions": {},
  "query": {
    "distinctOn": [],
    "kind": [
      {
        "name": "Person"
      }
    ],
    "order": [],
    "projection": [],
    "filter": {
      "compositeFilter": {
        "filters": [
          {
            "propertyFilter": {
              "property": {
                "name": "f"
              },
              "op": "EQUAL",
              "value": {
                "stringValue": "Full name"
              }
            }
          }
        ],
        "op": "AND"
      }
    }
  },
  "projectId": "nth-circlet-705"
}

Sometimes the query returns the entity, other times it doesn't. Is there anything we're doing wrong?

@stephenplusplus That looks like standard Eventual Consistency. For any e2e tests that require a get and a query you should be using ancestors.

I'm getting it with that as well:
Commit:
{
  "mutations": [
    {
      "upsert": {
        "key": {
          "path": [
            {
              "kind": "People",
              "name": "US"
            },
            {
              "kind": "Person",
              "name": "name"
            }
          ]
        },
        "properties": {
          "f": {
            "stringValue": "Full name"
          }
        }
      }
    }
  ],
  "projectId": "nth-circlet-705",
  "mode": "NON_TRANSACTIONAL"
}

Query
{
  "readOptions": {},
  "query": {
    "distinctOn": [],
    "kind": [
      {
        "name": "Person"
      }
    ],
    "order": [],
    "projection": [],
    "filter": {
      "compositeFilter": {
        "filters": [
          {
            "propertyFilter": {
              "property": {
                "name": "f"
              },
              "op": "EQUAL",
              "value": {
                "stringValue": "Full name"
              }
            }
          }
        ],
        "op": "AND"
      }
    }
  },
  "projectId": "nth-circlet-705"
}

Maybe I'm not understanding how to save and/or query using ancestors?

Sorry, I got it using hasAncestor. I think I'm good.

Cool, let me know if there are any other issues


Add an improved file-widget for zsh

The new widget uses the already typed path as a root directory for the file search. It's not enabled by default.

Thanks, but this should instead be on the wiki page. I would like the behaviors of the three key bindings consistent across bash, zsh, and fish, and I decided not to add more shell stuff to this repo. Maintenance burden is just too much for me. By the way the widget doesn't seem to handle multiple selections.

I understand.
Yes, I've missed the multiple selection handling. I've managed to fix it but I needed to change some of your functions. Does it still make sense to add it to the wiki?

Thanks for understanding. I want to keep the core simple and small.

but I needed to change some of your functions

I see, but I think you can still make it work without the code in this repo, make it self-contained, although it can cause some code duplication. It's up to you to put it on the wiki page or not.

Ok. I'll clean it up a bit and then add to the wiki.

Currently we don't have a dedicated page for custom key bindings. Consider creating Examples (key bindings) page.


change old (<=0.10) node detection

Not sure that you will agree with export changes, but I ready remove this.

LGTM.
ping @calvinmetcalfe was there any reason not to do it like this?

the current version will always work while the updated version will probably work, I can't see this as being much of a speed up considering the a single round of pbkdf2 is by definition a small fraction of the total run time of the eventual computation

Updated.
@calvinmetcalf I returned check for digest support through pbkdf2Sync, but remove isNode10 call from every call pbkdf2Sync/pbkdf2. It should give little speed-up.

so yes it will add a speed up to the first call, but a slowdown for every program that requires this module, previously the has was calculated only the first time pbkdf2 was called and then never calculated again.  I'm not convinced that removing that one function call if statement is much of a speedup in the first place...

Agree isNode10 has cache and I sure that function call will be very fast, but main idea now that we don't need wrapper for node > 0.10

ok but your way of testing slows down the start up of every program that requires this module...

I don't understand...
IIFE will be called once, require caches this.
$ cat a.js
require('./x')
require('./b')
$ cat b.js
require('./x')
$ cat x.js
var f = (function () {
  console.log('h1')
  return true
})()

module.exports = f ? 1 : 0
$ node a.js
h1

yes but it will be called even if somebody never uses pbkdf2 instead of the
first time pbkdf2 is called.  Or put another way it will delay the startup
of the program instead of the start of the first call to this function.
On Wed, Feb 24, 2016 at 12:22 PM Kirill Fomichev<EMAIL_ADDRESS>wrote:

I don't understand...
IIFE will be called once, require caches this.
$ cat a.js
require('./x')
require('./b')
$ cat b.js
require('./x')
$ cat x.js
var f = (function () {
console.log('h1')
return true
})()
module.exports = f ? 1 : 0
$ node a.js
h1
—
Reply to this email directly or view it on GitHub
https://github.com/crypto-browserify/pbkdf2/pull/25#issuecomment-188360603
.

Oh, I see it now. Thanks @calvinmetcalf for explanation!
I see two options:

if we want remove wrapper for node > 0.10, we should check through process.version
if we want use check through crypto.pbkdf2Sync, we should use wrapper and close this PR

yes you got it, I believe I originally used process.version, but when iojs happened the tests broke which is why I'm somewhat distrustful of the process.version testing

this was merged as part of #27


Ability to terminate ASG members, rather than just stop them

At the moment, Revolver stops EC2 instances that are members of ASGs, before pausing the ASG.  It would be beneficial if Revolver could terminate the instances to remove parasitic cost (EIP, EBS volumes and snapshots)

This will be a little challenging because Revolver doesn't really have a ASG resource - it kindof magically uses them when it finds EC2 that are members of ASGs.  If revolver terminates the EC2s it won't find them anymore, so won't even notice the ASGs.

Maybe... if instances are terminated, we could make "virtual" InstrumentedEc2 to represent instances in paused ASGs?  The virtual-EC2 wouldn't support EC2 start/stop commands, but could still allow the ASG-resume to happen.
The properties of the virtual-EC2 could be built from either one of the instances before shutdown, or synthetically from the ASG Launch Template + ASG overrides/tags.
Any better ideas @abukharov @alutman-innablr ?   Customer really wants to terminate, not pause, because the instances have really large EBS volumes (with disposable content).

Also, customer has some ASG where they use step functions to install/startup the instances properly, so just restarting the VMs won't work.

One solution to this could be to modify the ASG parameters to allow it to scale to zero, then restore the old values when the shutdown period exits.


Support transforms on schemas (Closes #120)

I'm unable to add a reviewer, so tagging @AGalabov for review

@dvargas92495  this has just been merged through this PR so I'll be closing yours, sorry.

Great news! Thanks for getting it across the finish line


Don't try to publish to balena if balena_slugs is empty

Change-type: patch

The description of balena_slugs already says this will happen but in practice it did not

@balena-ci I self-certify!


[Bug]: Text Widget Inserts New Line When Using  Tag

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The Text widget inserts an unwanted new line when the user uses a  tag.
E.g.,
this is a  span  thing
results in:
This is a
span
thing

It should not add a line break before and after the  tag.
Steps To Reproduce

Add a Text widget to the canvas.
Type some text and use a  tag. E.g.: this is a  span  thing
Note that line breaks are added before and after the text inside the  tag.

Public Sample App
No response
Issue video log
No response
Version
Appsmith v1.8.16-SNAPSHOT
 Front conversations

@ame-appsmith we have closed this issue here - https://github.com/appsmithorg/appsmith/issues/19285
It's already in release. Should be available in the next version

I am on Appsmith Community 1.9.2 but it still does not work properly. The same error (inserted line breaks) happen when I enter'
 a  span  thing in a text widget. Am I missing something?

@dhruvikn is the given change has reached prod, can you kindly verify the above statement?

Hey @somangshu @tomgw, I checked and it looks like this change will reach production in v1.9.3. The promotion happened yesterday https://github.com/appsmithorg/appsmith/pull/19545
Please wait until the next release @tomgw. Thanks a lot.

It works correctly in v<IP_ADDRESS>
Thanks!


Incorrect type annotation for FFmpegPCMAudio stderr

Summary
Incorrect type annotation for FFmpegPCMAudio stderr
Reproduction Steps
See code snippet
Minimal Reproducible Code
stderr: BinaryIO = io.BytesIO()
stream: discord.FFMpegOpusAudio = discord.FFMpegOpusAudio('file.mp3', stderr=stderr)
ctx.voice_client.play(stream)

Expected Results
Successful playback
Actual Results
Error: Command raised an exception: UnsupportedOperation: fileno
Stacktrace:
"Command raised an exception: UnsupportedOperation: fileno".
Exception ignored in: <function AudioSource.__del__ at 0xffff908063a0>
Traceback (most recent call last):
  File "/home/USER/.local/lib/python3.9/site-packages/nextcord/player.py", line 115, in __del__
    self.cleanup()
  File "PROJECT.py", line 60, in cleanup
    super().cleanup()
  File "/home/USER/.local/lib/python3.9/site-packages/nextcord/player.py", line 211, in cleanup
    self._kill_process()
  File "/home/USER/.local/lib/python3.9/site-packages/nextcord/player.py", line 176, in _kill_process
    proc = self._process
AttributeError: 'FFMpegOpusAudio' object has no attribute '_process'

Intents
Default
System Information
Ubuntu 21.04
Python 3.9.5
Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
The constructor for FFMpegPCMAudio accepts a stderr argument of type BinaryIO. However, instances of BinaryIO that don't support the fileno operation (for example, io.BytesIO) cause an error if passed.

See https://github.com/Rapptz/discord.py/issues/5192

Your stacktrace means you have not installed ffmpeg.


Feat: Add Lark support for notification (#3053)

Signed-off-by: Shuai Tian<EMAIL_ADDRESS>Description of your changes

Feat: Add Lark support for notification (#3053)
I have:

[x] Read and followed KubeVela's contribution process.
[x] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer
@FogDong

 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: basuotian sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Camera into Home Assistant

Hello
I have install the integration on my Home Assistant and it was connected nice with the speeder pad of my printer 3D FLSUN V400
For complete the information : FL SUN V400 has a tablet speeder pad where is installed into this pad Mainsail, moonraker and klipper....
My webcam is connected to the speeder pad and I have access to the video into the URL Mainsail....
How does I must do for to have the video into Home Assistant ? If it possible

Hey,
Can you get me a copy of your logs please.
Try to enable logging .

Then go try to look at the device or the entities, try to reload the integration.
Then can you send the logs here

Can you also show me what this gives your:
http://<IP_ADDRESS>/server/webcams/list
Replace IP with your Printer IP

@titou4307 ☝

Hello
With the http://<IP_ADDRESS>/server/webcams/list
I have a JSON to download I have put in txt here....
list.txt

Can you check in your mainsail webUI, what is the camera/crownest details
https://user-images.githubusercontent.com/12702322/198850218-a8e12baf-f057-40c5-8203-9cf5ff7d1efa.jpg

For the Logs, you can go in

Home-Assistant
Settings
Device

Then you can click the 3 littles dots and enable logs

Does it you need ? :

I have enable the log ....
But How this log are ? for made copy and paste here ??

If you have the log enable, then on the same sub menu you can click to reload the app
Then click the same sub menu and click disable log.
It should download a log file

home-assistant_moonraker_2023-03-03T23-13-13.575Z.log

Look like there is something fishy with your moonraker.

have you try restarting the pi? (or whatever device use it)

If you still have the same 404 error with the http://<IP_ADDRESS>/server/webcams/list (make sure to replace IP)
Can you login ssh on your device and get this log: /tmp/moonraker.log.

Hello
I have found this files...
moonraker-3.log
moonraker-1.log
moonraker-2.log

I am pretty sure there is some setup thing to fix on your moonraker,
The right query hits your moonraker 2023-03-03 21:33:04,895 [app.py:log_request()] - 404 GET /server/webcams/list (<IP_ADDRESS>) [No User] 9.36ms
But you have a user/permission error.
Looks like other have got this issue
https://www.reddit.com/r/klippers/comments/ugdle8/unable_to_connect_over_lan_to_moonraker/
https://github.com/Arksine/moonraker/issues/321
https://github.com/Arksine/moonraker/issues/568

At this point I am 98% convinced the issue is not with the integration

Hello @marcolivierarsenault
My Klipper Mainsail Moonraker is into the speeder pad of FLSUN (not a PI) so I don't know where is this log
Look at this video :
https://www.youtube.com/watch?v=dQcC7aBL7oM
I will try to SSH and navigate into speeder pad... And read the 3 links...

I don't have this equipement I can't help you debug so much. Sorry.

Hey, Right now this integration does not support device using FLSUN.
Until we can get our hands on one and develop or someone propose a fixing patch, not much we can do.

I find myself in the same situation, also have a Flsun v400, same behaviour.

+1 on no cam.
/server/webcams/list lists the cam as available, but Home Assistant never picks it up and no entity created for the cam

@joaomcampos I think you are onto something.
can you tell me what this gives you
http://<IP_ADDRESS>/server/webcams/list
(replace the IP with your moonraker IP)

{"error": {"code": 404, "message": "Not Found", "traceback": "Traceback (most recent call last):\n\n  File "/home/pi/moonraker-env/lib/python3.8/site-packages/tornado/web.py", line 1681, in _execute\n    result = self.prepare()\n\n  File "/home/pi/moonraker/moonraker/app.py", line 909, in prepare\n    raise tornado.web.HTTPError(404)\n\ntornado.web.HTTPError: HTTP 404: Not Found\n"}}

ok I think I get the issue.

(Note for future me)
With FLSUN the http://<IP_ADDRESS>/server/webcams/list return a 404, we can't grab the camera path from the API, we can probably try to hardcode it.

@joaomcampos any chance you can get me a dump of your HA logs
https://moonraker-home-assistant.readthedocs.io/en/stable/support/logs.html

@titou4307 @joaomcampos
Can one of you test this branch. try_hardcode_cameras
Easiest is to go in your HA install,
Replace the file custom_components/moonraker/camera.py with this file. https://raw.githubusercontent.com/marcolivierarsenault/moonraker-home-assistant/try_hardcode_cameras/custom_components/moonraker/camera.py
Let me know if it works

@marcolivierarsenault
Hello
I have try this middle of day
After delete old file camera.py, I have put the file you give by link here....
I have the camera view in the add on....

Thanks @titou4307 for the help,
We finally have a fix, fresh of the merge.
So to get the latest code (while waiting for the new release) please download the main verison of the code.
DEtails here: https://moonraker-home-assistant.readthedocs.io/en/stable/support/latest.html

No Problem
I am here for to help .... too....


Sharding support for broadcast add

Stable diffusion needs broadcast add for row major tensors on h dim for block and width sharded tensors. The smaller tensor can be either sharded or interleaved, whatever's easier.

@jliangTT can you please coordinate?

If row_major inputs is difficult, tilized could work too (although RM is preferred).

@tarafdarTT , are you the right person to triage (for sharding support for op), or is this more on the op owner for the broadcast category?

hey Jason. ya more of an op owner situation. But I have added sharding support for ops I didn't own in the past, so either or.

@AleksKnezevic , is this a big performance hitter for SD? what percentage of speed-up are we looking at for this?

Sorry everyone, my bad, I completely missed that this issue is being tracked elsewhere and actively worked on https://github.com/tenstorrent/tt-metal/issues/5657. Closing as it's a duplicate.


Fix handling of vendor directory in the Go standard lib

The main change is in scan.go. Unifies handling of vendored source unit names across scan, depresolve, and graph. Previously, these were handled differently and could result in some inconsistencies.

LGTM


qt5ct: 0.35 -> 0.36

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/qt5ct/versions.
meta.description for qt5ct is: '"Qt5 Configuration Tool"'.

Checks done (click to expand)

built on NixOS
Warning: no invocation of /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36/bin/qt5ct had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.36 with grep in /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36
directory tree listing: https://gist.github.com/98d8adcf960ca82778ab72b74b1e4e32
du listing: https://gist.github.com/9703f1501939026cbdaf38a29209a844

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout f3dff8dafc1840d5f541d2f924bfbd7f071c1de3 && nix-shell --pure -I nixpkgs=. -p qt5ct

cc @ralith for testing.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: qt5ct
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: qt5ct
Partial log (click to expand)
shrinking /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36/lib/qt-5.11/plugins/styles/libqt5ct-style.so
shrinking /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36/lib/qt-5.11/plugins/platformthemes/libqt5ct.so
shrinking /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36/bin/qt5ct
/nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip is /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip
stripping (with command /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip and flags -S) in /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36/lib  /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36/bin
patching script interpreter paths in /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36
checking for references to /build in /nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36...
postPatchMkspecs
postPatchMkspecs
/nix/store/0ndkn3xwgzkrrbbyymki7w897pj05dj6-qt5ct-0.36

Success on aarch64-linux (full log)
Attempted: qt5ct
Partial log (click to expand)
shrinking /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36/bin/qt5ct
shrinking /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36/lib/qt-5.11/plugins/styles/libqt5ct-style.so
shrinking /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36/lib/qt-5.11/plugins/platformthemes/libqt5ct.so
/nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip is /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip
stripping (with command /nix/store/8wl4dykwswy42wxj671b6k7vk2ydxg86-binutils-2.30/bin/strip and flags -S) in /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36/lib  /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36/bin
patching script interpreter paths in /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36
checking for references to /build in /nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36...
postPatchMkspecs
postPatchMkspecs
/nix/store/8x8m4vfmahpfhyv2pjc5rrkf3c17b88x-qt5ct-0.36


Issue with line endings

I tried to run zalc on a Mac, and saw the following:
❯ zalc publish
env: node\r: No such file or directory

The temporary solution was here: https://stackoverflow.com/a/30349952/598628, and so I ran:
❯ dos2unix /Users/brad/.config/yarn/global/node_modules/zalc/Dist/Bin.js
dos2unix: converting file /Users/brad/.config/yarn/global/node_modules/zalc/Dist/Bin.js to Unix format...

But it would be nice to not have to do this.  Would different line-endings still work on Windows?

Good point; I'm assuming leaving out the "\r" (carriage return character) would be just fine on Windows, so will try to make that change soon (added to personal todo list).


feat(amplify-codegen-appsync-model-plugin): add appsync dart visitor …

Issue #, if available:
Description of changes:
Added dart declaration block and visitor to generate model code for the use of Amplify Datastore. Directives implemented:

@model
@connection
@auth
@key

Added unit tests for dart model generation
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

LGTM😸


Update Type Declartions

Coverage remained the same at 100.0% when pulling aa273df0a534c4f784040b57b1db2776a3656aca on SaiX123:es2015-i18n-tag-Update-Type-Declartions into 4622d54352001a0462a3258ceefb6b91266057f1 on skolmer:master.

Looks good, thank you!

@SaiX123 Can you explain why you changed the return types to any? What issues did you run into with the old type definitions?

released as 1.3.2

@all-contributors please add @SaiX123 for infrastructure, tests and code


Feature/resource-entities

Adds support for FusionAuth entities. (OAuth 2 client credentials grant 🎉)
Adds resources:

fusionauth_entity
fusionauth_entity_grant
fusionauth_entity_type
fusionauth_entity_type_permission

Haaah.
And it's at this point I see #82  ... 😂😭
I see there are a couple of random bug fixes in there, which could be useful to extract though.
I've been using this branch internally to inject entities to our FA cluster 👍

I may as well comment here. I was sitting down and I saw this as I was sitting down to finally try and tackle the golint errors (the previous PR being basically my first non-toy exposure).
We are in a similar state using our repo to manage entities. The interface seems relatively similar and we just want the pieces upstreamed eventually. The one thing I noticed is that our branches have different mechanisms for storing the entity permission grants. I would say yours probably look more like an idiomatic usage of the fusionauth client but doesn't look like it is setting an Id at all, but I figured I might as well call it out to decide on the preferred approach. For reference, https://github.com/gpsinsight/terraform-provider-fusionauth/pull/82/files#diff-e61a77b609613506b4c3db4c8eee053dc6da3f9cfda7f98f4b23c9b4109413c4R58 is where I do the similar.
The Computed changes we added as the continual flagged changes in TF were annoying our ops person.

@rzeigler would you be okay if I merged this one in and then you can create a pr for the computed changes and id creation?

Sure. I'll do a PR for each unless you prefer them together.

Sorry @rzeigler!!
I'll check the PRs first next time 😅
Also thanks for the cross-check of functionality with your PR. The computed bug fixes and the setId fix are super helpful 💪🎉💯


AC support for person-detection-0106

This PR should be merged with PR 1184. Now you have no need to change it, but in future please publish all that model need, under single PR.


Impossible to fuse Mistral-7b-Instruct-v0.2 after finetuning

Hi everyone,
I'm unable to fuse the model after finetuning, I got this error. Can someone please help? All paths are correct and the adapter works just fine.
antoine@Mac-Studio lora % python fuse.py --model "/Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/Models.nosync/Mistral/Mistral-7B-Instruct-v0.2/" --save-path "/Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/Models.nosync/Mistral/fine-tuned/" --adapter-file "/Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/Models.nosync/Mistral/adapters/adapters.npz" --de-quantize
Loading pretrained model
Traceback (most recent call last):
File "/Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/mlx-examples-main-2/lora/fuse.py", line 55, in
model, tokenizer, config = utils.load(args.model)
^^^^^^^^^^^^^^^^^^^^^^
File "/Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/mlx-examples-main-2/lora/utils.py", line 154, in load
raise FileNotFoundError("No safetensors found in {}".format(model_path))
FileNotFoundError: No safetensors found in /Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/Models.nosync/Mistral/Mistral-7B-Instruct-v0.2

The --model flag should point to the original model (hugging face repo or local path) that you fine tuned with.

Could you share the output of:

ls /Users/antoine/Documents/GitHub/EVD.COVID_ANALYSIS/EVD.COVID_ANALYSIS/Models.nosync/Mistral/Mistral-7B-Instruct-v0.2/

Could you share the command you used to fine-tune?


Flutter GraphQL Issue

Amplify CLI Version
2.0
Question
I am trying to add the AWS AppSync API plugin into the Flutter app to support GraphQL from the amplify backend that already exists. It sends an error message that the configuration failed and no API plugin was found when I ran my Flutter app.
Is the configuration in the image correct or is there any other way to add multiple plugins to amplify configuration.dart?

@haverchuck @ykethan Can I get some help with this issue, please?

@salihgueler Can you help, please?

@Tructivity Could you provide us the error message/output on the terminal?
when running amplify codegen models do you observe any error messages?
On diving into the documentation, could you try installing the libraries provided here https://docs.amplify.aws/lib/graphqlapi/getting-started/q/platform/flutter/#install-amplify-libraries
and initialize the Amplify API category using the call Amplify.addPlugin() method provided in the example. Then run amplify codegen models.

@ykethan The first image attached displays the configuration of plugins.
The second image shows the error I received when running the command "amplify codegen models."
Upon initially running the app, it displays the message: "No API plugin found."
Furthermore, we are not making any edits to the backend or pushing any changes. I have added a schema.graphql file to the project, but "amplify codegen models" is unable to locate it.

@ykethan for this project, @Tructivity is trying to pull an Amplify project that they already have over Web into their Flutter project as well.

@salihgueler Yep, that's true

Hey @Tructivity, could you try adding the --model-schema with the path to the schema file with the amplify configure models command.
@Tructivity to better understand, over Web meaning was the API added resources added on Amplify Studio or added via push in the same environment?
If the API was added on Amplify Studio, you should just be able to run the pull command to sync your resources locally.

@Tructivity was able to get some additional information on the use case. I understand currently you have a application with a Amplify backend already present and would like to create a new frontend that utilizes existing backend resources.
Diving into this, we should be able to pull the backend environment amplify pull --appId <app-id> --envName staging and select Do you plan on modifying this backend? No which should pull your existing backend resource as immutable. If there an changes on the main backend, we should be able to run amplify pull to pull the changes.

@ykethan I have performed the amplify pull command for already existing amplify backend but it doesn't have added any plugins to amplifyconfiguration.dart and no models or schemas were added into the amplify folder yet the amplify backend has auth API and storage. Yet it's not fetching those into Flutter app and adding them automatically via the pull command. Is there any way to avoid this manual work?

Hey @Tructivity, would you be open for a quick call? i am available on discord, my handle is ykethan.

@ykethan up to u but is it a big issue? I've contacted u there

@Tructivity thank you for hopping on the call, were were able to import the resources and generate the models.
Closing the issue, please feel free in reaching out to us again.


service: fix charset definition for DownloadCaption

@scentless-apprentice sorry, I missed that when reviewing #87.

Codecov Report

Merging #88 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #88   +/-   ##
=======================================
  Coverage   62.35%   62.35%
=======================================
  Files           7        7
  Lines         433      433
=======================================
  Hits          270      270
  Misses        151      151
  Partials       12       12

Impacted Files
Coverage Δ

service/job.go
77.31% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Closing in favor of #90.


Deprecation of dashes affects other project settings

Hi! I checked https://setuptools.readthedocs.io/en/latest/history.html#v54-1-0 but I wasn't entirely clear: is this meant to warn for all keys using hyphens in setup.cfg? For example, I see warnings for these Flake8 options:
$ cat setup.cfg
[flake8]
extend-ignore = E203
max-line-length = 88

[isort]
profile = black

[tool:pytest]
addopts = -ra --color=yes
testpaths = Tests
$ python setup.py --version
/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/setuptools/dist.py:633: UserWarning: Usage of dash-separated 'extend-ignore' will not be supported in future versions. Please use the underscore name 'extend_ignore' instead
  warnings.warn(
/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/setuptools/dist.py:633: UserWarning: Usage of dash-separated 'max-line-length' will not be supported in future versions. Please use the underscore name 'max_line_length' instead
  warnings.warn(
/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/setuptools/dist.py:633: UserWarning: Usage of dash-separated 'extend-ignore' will not be supported in future versions. Please use the underscore name 'extend_ignore' instead
  warnings.warn(
/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/site-packages/setuptools/dist.py:633: UserWarning: Usage of dash-separated 'max-line-length' will not be supported in future versions. Please use the underscore name 'max_line_length' instead
  warnings.warn(
8.2.0.dev0

Flake8 themselves say both underscores and hyphens are fine in setup.cfg:
https://flake8.pycqa.org/en/latest/user/configuration.html#project-configuration
Thanks!
Originally posted by @hugovk in https://github.com/pypa/setuptools/issues/2588#issuecomment-792040266

Short answer, no. It was unintentional to affect config for other projects.


feat(hmi): new multi select file import dialog and preview

[X] The files are in a multi-select list
[X] The files are group by type based on their extensions
[X] Code (.js, .py, .m, etc)
[X] Data (.csv, .json, eyc)
[X] Documents (.md, .txt, .pdf, etc)
[X] Unknown file type (anything not falling in the above categories).
[ ] User could select from the above three types using the dropdown and bring that content in. - Note: This part could be done in a later pass. DEV NOTE: this is going to be done in another pass
[X] The selected/file in focus is show in the preview window. Note: this could be done as a second pass.  DEV NOTE: Text files only are previewed - PDFs are not, this will be done in another pass
[X] The Import bottom should indicate how many files are selected/will be imported.
[ ] The end result should be to see all these files in the Resources panel in their proper bin.  DEV NOTE: Blocked by inability to save files from github in current version TDS. This will be done in another pass

Description

Changing github code importer to be more generic github file chooser
Preview panel for any text based files
Ability to select multiple files for import (this is UI only at this point, not working)
UI will need some love - a bit rough at the moment
Filled out the back end with POJOs for github files.

Resolves #1142

There is also a need to do a second pass at the UI side of this - its a bit rough. I'd love to work with someone on that portion though to better learn our front end code!

Breakoff issues:
unknown types: https://github.com/DARPA-ASKEM/Terarium/issues/1164
dataset creation: https://github.com/DARPA-ASKEM/Terarium/issues/1165
document creation: https://github.com/DARPA-ASKEM/Terarium/issues/1166
code creation: https://github.com/DARPA-ASKEM/Terarium/issues/1167
provenance: https://github.com/DARPA-ASKEM/Terarium/issues/1168


Error upgrading StackBlitz app to 6.0.0-beta.5

Bug, feature request, or proposal:
Bug. Material2's StackBlitz app does not work after upgrading dependencies to 6.0.0-beta.5.
Specifically, I updated:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
What is the expected behavior?
Working sample app in StackBlitz.
What is the current behavior?
AppComponent.html:1 ERROR Error: StaticInjectorError(AppModule)[MatSlideToggle -> Platform]:
  StaticInjectorError(Platform: core)[MatSlideToggle -> Platform]:
    NullInjectorError: No provider for Platform!
    at _NullInjector.get (injector.js:39)
    at resolveToken (injector.js:413)
    at tryResolveToken (injector.js:355)
    at StaticInjector.get (injector.js:189)
    at resolveToken (injector.js:413)
    at tryResolveToken (injector.js:355)
    at StaticInjector.get (injector.js:189)
    at resolveNgModuleDep (ng_module.js:145)
    at NgModuleRef_.get (refs.js:1059)
    at resolveDep (provider.js:462)

What are the steps to reproduce?
Please see my fork: https://angular-material2-6beta5-injector.stackblitz.io
What is the use-case or motivation for changing an existing behavior?
I am experiencing a similar error updating my application to use<EMAIL_ADDRESS><EMAIL_ADDRESS>Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Whatever is running on StackBlitz, not sure how to check.

This commit #10507 switch to using "scoped injectables" which is probably why you're having issues, make sure the core angular packages rc.0 or later

Thanks, rc.0 was the issue!


Remove Materializers

We no longer use akka streams, that means in theory we could remove all the implicit materializers

This will break API, specifically the Baker constructors, so probably we need to schedule it for 3.1

It doesn't break public API


add lockAttributes call to configNFT

also lock the first configNFT manually

https://assethub-kusama.subscan.io/extrinsic/5257708-2


Removes the link as it now becomes static text: FESS

It seems ok as requested by Rachel Cooper in INC0229148


⚠ Jenkins Plugins Artifactory has degraded performance

In 7eb0539, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1221 ms

Resolved: Jenkins Plugins Artifactory performance has improved in d1f5b22 after 12 minutes.


Issue with imports

Describe the bug
When you import a file in another file and then use a function from the original file in the core file, there's no diagnostic.
It's a problem in the binding of imports inside the BindGlobalScope method.
To Reproduce
Steps to reproduce the behavior:

Create file a.ao
Create a function that prints a
Create file b.ao
Import a
Create file core.ao
Import b.ao
Reference the function inside a.ao
Run the compiler

Expected behavior
We should get an error saying that <functionName> does not existing.

Fixed by pull #58


Implement v6 limit order

Separate coordinator from LimitOrder contract, implement it using a special taker contact instead
Add fillLimitOrderFullOrKill function to allow taker choose different fill strategy
Allow fill with better price than the order specified
Add GroupFill feature
FeeFactor now is per order, not global

The light weight version #221


Add command line option for target music directory

For some users (including me) and cases it might me useful to specify the directory the files will be downloaded to. Otherwise copy&pasting is required, which is rather annoying. So to have all the music stored in /home/user/Music/, one would type python spotdl.py -u spotify -f "/home/user/Music/" (or --folder) . Music/ will stay default if the option is not given.
Should not be too hard to implement.

What about a settings.txt file where you put all these options and that is loaded as default? The command line input is huge if we have to type all these things again and again each time:
python spotdl.py -l songs_that_get_white_girls_excited.txt -i .m4a -p .m4a -f "C:\Users\Me\Music\...\".
(great playlist btw 🔥)
A simple .txt would be sufficient
music_path=C:\Users\Me\Music\...\
input_enc=.m4a
output_enc=.m4a
default_user=0123456789
...

@KLVN That sounds a good idea!

Yup, but this would be another issue. I think I'll add the -f option ant then the possibility to feed settings from a file.

Fixed as of https://github.com/ritiek/spotify-downloader/commit/cc7260dfa672d377bd5374bf1e23141340a1a103. Just need to update the Readme now. Works fine, test are passing (and adapted).

Updated Readme and fixed minor issues (typo, spaces) as of https://github.com/ritiek/spotify-downloader/commit/75be7285c0fdda5fa83875bc942e0bf93d1233d1.


1.16.5 No pop up

I don't get any errors part from mixer complains you never set a min version but I don't get the pop up and it just locks up.
I believe the problem is I am using a tool that is capturing the console window and for some reason it's not poping open, unless the pop up is meant to happen in the client then I can't see what would be blocking the login pop up.
This is happening with 3.1.1 and I testing it on 1.16.5 minicplayer worked though.
I think it's waiting for the pop up or something though as it locks up here

I was able to grab a error
[main/DEBUG] [mixin/]: Mixing MixinMain from forge-devlogin.mixins.json into net.minecraft.client.main.Main
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052 java.lang.NoSuchFieldError: f_91002_
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at forge.com.ptsmods.devlogin.MSA.showDialog([MSA.java:451](file://forge.com.ptsmods.devlogin.msa:451/))
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at forge.com.ptsmods.devlogin.MSA.lambda$reqTokens$2([MSA.java:133](file://forge.com.ptsmods.devlogin.msa:133/))
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at forge.com.ptsmods.devlogin.MSA.lambda$doRequest$15([MSA.java:428](file://forge.com.ptsmods.devlogin.msa:428/))
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at java.util.concurrent.ThreadPoolExecutor.runWorker([ThreadPoolExecutor.java:1149](file://java.util.concurrent.threadpoolexecutor:1149/))
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at java.util.concurrent.ThreadPoolExecutor$Worker.run([ThreadPoolExecutor.java:624](file://java.util.concurrent.threadpoolexecutor:624/))
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at java.lang.Thread.run([Thread.java:750](file://java.lang.thread:750/))```

I cannot replicate this issue, however, you can now disable the dialog using the --msa-no-dialog program argument.


Update searching--downloading--and-installing-updates.md

Adding additional script functionality to demonstrate new techniques (notably "commit" on changes before rebooting, and showing/hiding updates).

@mark-phaedrus : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thank you very much!
// Mark Phaedrus, Software Developer, Windows On Prem and Rollout (WSUS Я Us) - he/him/his/hey you
From: McLean Schofield @.>
Sent: Monday, March 15, 2021 11:34
To: MicrosoftDocs/win32 @.>
Cc: Mark Phaedrus @.>; Mention @.>
Subject: Re: [MicrosoftDocs/win32] Update searching--downloading--and-installing-updates.md (#794)
Merged #794https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwin32%2Fpull%2F794&data=04|01|phaedrus%40microsoft.com|9c43ebdb94704f7f149708d8e7e0dce4|72f988bf86f141af91ab2d7cd011db47|0|0|637514300252909301|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=b1MFHsyOjWK2%2F15oBw0MBugdOvtC5HVx7PssnN4pj%2B8%3D&reserved=0 into docs.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fwin32%2Fpull%2F794%23event-4460437010&data=04|01|phaedrus%40microsoft.com|9c43ebdb94704f7f149708d8e7e0dce4|72f988bf86f141af91ab2d7cd011db47|0|0|637514300252919294|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=d4d4FD6XH9gnAyOoxWlTq2pQiP0gWTRLMRaCnHJKSw8%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMODRD2WIY7KINQNXBSDPCLTDZHIPANCNFSM4ZHCN4KA&data=04|01|phaedrus%40microsoft.com|9c43ebdb94704f7f149708d8e7e0dce4|72f988bf86f141af91ab2d7cd011db47|0|0|637514300252929289|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OnSYiMqR5%2F9tT1w6EXRNyQ2mLKLoBaL19Rbrg8K%2Fp5I%3D&reserved=0.


update youtube downloader project

Is your feature request related to a problem? Please describe.
playlist download , channel information and search functionalities
Describe the solution you'd like
to add playlist download , channel information and search functionalities to youtube downloader project
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
i would like to take up the issue

Sure ,go for it 👍

the project is updated ..please merge the pull request