(PUP-6452) Allow defaultfor to accept regex

Allows easier matching for defaults. For example, Fedora 22+ uses DNF. It's easier to just give a regex of 22-29 rather than add a new one each time

Code is rough right now, but working according to the specs! 😄

CLA signed by all contributors.

I was just thinking earlier today that this would be super useful (especially for things like yum/dnf and systemd). Thanks for taking the time to open it! I'm not gonna do a serious review at 22:30, but I'll get back to you on this as soon as I have some spare cycles.

Would it be possible to make this more flexible than just regex? AIUI, even for Fedora, it's really F22+, not just F2{2-9}. That is, when F30 comes out, the regex is no longer correct and there would be a regression, right? Similarly for Ubuntu, we want to say 15.04 was the turning point for systemd being the default, and just be able to go off that value as to what the default init-script provider is.

Another idea: have defaultfor follow the pattern of confine and allow a code block. Then for the dnf case the code could be something like:
defaultfor :true begin
  Facter.value(:operatingsystem) == :fedora && Facter.value(:operatingsystemmajrelease).to_i >= 22
end

I haven't looked to see if this would fly or not, just tossing out ideas :)

@kylog that's probably the way to go moving forward. In my mind that makes regex not super useful - but I'm also not sure anyone on Client will have the bandwidth to make that change. I don't think we should block small improvements on us having a better idea but not actually doing it
@petems I'm happy to merge this as-is, unless you feel like you want to take on the defaultfor accepting a block change, in which case I'd consider that to supersede this PR

@branan Right now I wouldn't have the bandwidth without some pairing on how to do that (never really got block argument stuff in Ruby). How do we feel about going for Regex in the mean time?

@petems I'd much rather have regex than nothing, and I don't think implementing  regex actively prevents us from doing more complex block stuff in the future. How do you feel about just getting this in @kylog ?

Yeah, I'm +1.

Ok, I'm cool with getting this merged and opening a ticket for more complex block arguments in the future? 👍

@kylog @branan Can I get this unblocked and merged? 👍

@petems resurrecting this PR - do you want to push up your latest code that caused the test failures you referenced in your last comment? We can help debug it.

@MosesMendoza Done!

The spec failures are equality failures: the first group of failures are due to values containing "Darwin" and being compared against "darwin". In the second group, values contains a Symbol, :os1, but the Facter value is a string. So it seems like this logic might actually get more complex to correctly handle all these different cases...

@petems will you have time to play with this more? Probably going to need a different solution than ===.

@petems i'm going to push a commit up to your branch that addresses these failures if i have access, otherwise I'll close this and open a new with your changes and mine

ok I don't have push access so i'll open a new branch/pr

superseded by https://github.com/puppetlabs/puppet/pull/6292


Update tagging script

This should extract the release text

I've removed the broken cloud build integration now


Use start_tabs formatting in API docs, and other tweaks

git grep "1\." api_docs/ shows API docs that have numbered instructions. Spot checking a couple of these, they are not using the {start_tabs} formatting we use in the help center. We should fix this.
On https://zulip.com/api/api-keys, we should also

[ ] Move these into !!! warn "" blocks inside the appropriate subsection (but outside the instruction block, I think).

An API key is how a bot identifies itself to Zulip. Anyone with a bot's API key can impersonate the bot, so be careful with it!
Anyone with your API key can impersonate you, so be doubly careful with it.

[ ] Write out the instructions for Invalidate an API key.

We should also cross-link /api/api-keys and /api/configuring-python-bindings as related articles, and audit the other files we're touching for other cross-linking opportunities.

@drrosa It would be great if you could take this cleanup pass.


Move support window to OTP 25-27

We thus align with other tools doing the same in the ecosystem, e.g. like rebar3. Lemme know if you feel this is a drastic change. (I think we discussed it, which is why we find oldest, plus_one, plus_two, plus_three in the workflow files, but I can't quite say when - or if we did 😄)

Lemme know if you feel this is a drastic change.

Not drastic at all, it is precisely what we all should be doing :) Elixir 1.17 is not out yet though, so this will have to hang for a minute...

Not drastic at all, it is precisely what we all should be doing :) Elixir 1.17 is not out yet though, so this will have to hang for a minute...

Sure. I'm assuming nothing much'll break in this sense, but may be over-optimistic 😄


Fix race condition dead awaits

Start Deferrals with counter = 1, but immediately call _fullfill in
await_exit. This way, Deferrals will never be considered 'done' in the
middle of creating defer_returns.
Fixes https://github.com/maxtaco/coffee-script/issues/175

Published to npm as v3.0.3
thanks!


log print more message about load job on tablet error

Proposed changes
Issue Number: close #xxx
Print channel info (which includes load_id and txn_id) on tablet error, it's easier to gather all error message while we grep log by load_id.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Loosen URL dependency version

Thanks for the PR! You're right, semver allows this and it should eliminate multiples of url where none would be actually necessary. I'll publish the updated crate soon.


Improvements for JWT configuration for the testing application.

The JWT value can be set to the local.properties file.
As an alternative way, it can be saved to the SharedPreferences.

!squash

!merge


TypeError: a bytes-like object is required, not 'dict'

Bert Model doesn't load using spacy
import spacy
nlp = spacy.load('en_pytt_bertbaseuncased_lg')
Your Environment

Operating System: Windows
Python Version Used: 3.7
spaCy Version Used: 2.1.8

Info about spaCy

spaCy version: 2.1.8
Platform: Windows-10-10.0.17763-SP0
Python version: 3.7.3

See #58 – not sure what the exact problem was, but it sounds like redownloading and reinstalling the model fixed it.


Full library catalogue data

Measures

Are all required fields fully implemented?

Do we support bib and series linking?

Do we surface journals and electronic resources?

Can users search across all Sierra bibliographic data?

Link to feature: https://wellcomecollection.productboard.com/feature-board/planning/features/4845056


Exit with zero in case of vulnerability found

Describe the bug
When a vulnerability was found the exit code of the program is zero. Thus it makes it hard to integrate the tool into an automation that should raise an alert in case a vulnerability was found. This is the case when running pyscan either for a specific package or within a repository.
To Reproduce
Steps to reproduce the behavior:

Run pyscan package -n requests -v 2.30.0
Run echo $?
Observe that 0 is returned

Expected behavior
It is expected that a non-zero exit code is returned in case a vulnerability is found.
Desktop (please complete the following information):

OS: macOS Ventura ARM architecture, Debian 11.7 x86 architecture

Yes, this is a known case and will be integrated as default way of exiting in the new version as mentioned in the future notes in CHANGELOG.md. I will be closing this issue as its already taken care of and will be released within the next version.

It was released, but I moved the scanner functions around in the latest version and looks like I forgot about the exit codes. Fixing it ASAP.

Thanks a lot!


Training stability: Continue training even if a data batch was hit which causes OOM

Following my Investigations mentioned in https://github.com/lifeiteng/vall-e/issues/110, I implemented some code which does the following in case a training batch causes an OOM error:

Print Metadata and text contents of the malicious batch to console
Deletes all references to the batch object from current training cycle
Deletes all references to loss output from current training cycle if it exists
Empty CUDA cache to free up stale memory
Continue training with the next batch

This should improve the training process in various aspects, such as:

Easier identification of dataset content which is causing issues
Training can still resume and eventually finish training the epoch in case there are just a few data elements casing issues.

Additionally, I discovered there is a Grad Scaling step missing in the Pre-Training OOM check, which explicitly was the code where the OOM Exception happened during training in my case. So I added thos as well

you can load the batch data display_and_save_batch(batch, params=params) by torch.load(xxxx), the analysis the data(mainly the duration)

@chenjiasheng thank you for your detailed comment. Yes this issue probably needs a bit more in-depth analysis.
In my case it turned out that the error was thrown because of some token generation problem with non-latin characters; causing VRAM to be flooded. As pointed out by @lifeiteng here: https://github.com/lifeiteng/vall-e/pull/111#issuecomment-1536003411, the model needs to be improved in regards to supporting symbols from various languages to overcome this.
However, the main purpose of this PR, to recover the training process in case of an unexpected OOM error - I still don't 100% understand why these errors were not detected by OOM check on start in the first place - is not 100% solved by this yet. So maybe this PR should be converted to draft state in the meantime.

As I pointed out, we should also continue other ranks that didn't encounter an OOM error, to avoid inconsistency among ranks. The inconsistency may be caused by following processes like update_averaged_model, scaler.update.
I think inconsistency is more harmful than just a failure.
@RuntimeRacer
Could you please:

modify the code as I suggested

    is_oom = 0
    try:
        ...
    except:  # noqa
        is_oom = 1
    is_any_rank_oom = torch.tensor(is_oom).cuda(local_rank)
    torch.distributed.all_reduce(is_any_rank_oom)
    if is_any_rank_oom.item() > 0:
        continue

carry out some tests on:

different OOM time point (during forwarding or backwarding)
single-rank and multi-ranks training
different numbers of ranks that encounter OOM error simultaneously.

Closing this since the issue was related to input data format / combo itself, not the way errors are being handled.
Also I currently don't have the time to do a detailed evaluation as proposed by chenjiasheng.


A swallowed exception in exception handling during subscribe new topic

Describe the bug
In MultiTopicsConsumerImpl class there is possibility to swallow an exception in exception handling during subscribe new topic.
This behavior may occur in handleSubscribeOneTopicError() method, which is invoking in exceptionally block in some CompletableFuture.
This handler method is responsible for completing exceptionally a CompletableFuture named subscribeFuture (code below). This future is completed in one place only and just before that there is possibility that checkState() method throws an exception. This exception will be swallowed and it also causes that  subscribeFuture future will be never completed.
if (toCloseNum.decrementAndGet() == 0) {
    log.warn("[{}] Failed to subscribe for topic [{}] in topics consumer, subscribe error: {}",
                    topic, topicName, error.getMessage());
    topics.remove(topicName);
    checkState(allTopicPartitionsNumber.get() == consumers.values().size()); // a possible swallowed exception
    subscribeFuture.completeExceptionally(error);
}

To Reproduce
Above behavior can be reproduced using following sample test code:
    CompletableFuture<Void> someMethod() {
        return CompletableFuture.failedFuture(new RuntimeException("someMethod error")); // always fails for test purposes
    }

    CompletableFuture<Void> mainMethod() {
        CompletableFuture<Void> toFinishFuture = new CompletableFuture<>();

        someMethod().thenAccept(x -> {
            // some code
            // ...
            toFinishFuture.complete(null);
        }).exceptionally(throwable -> {
            checkState(1 == 2); // always fails for test purposes, throws an exception, which is swallowed
            toFinishFuture.completeExceptionally(new RuntimeException("some error"));
            return null;
        });

        return toFinishFuture;
    }

    @Test
    void swallowedExceptionTest() throws ExecutionException, InterruptedException, TimeoutException {
        CompletableFuture<Void> completableFuture = mainMethod();
        completableFuture.whenComplete((aVoid, throwable) -> {
            if (throwable == null) {
                System.out.println("OK");
            } else {
                System.out.println("ERROR");
            }
        }).get(20, TimeUnit.SECONDS); // the completableFuture will never complete, the TimeoutException will be thrown
    }

Expected behavior
An exception shouldn't be swallowed and completable future named subscribeFuture should always be completed inside handleSubscribeOneTopicError() method.

@git-enzo Are you interested in contributing a bug fix?

Hi,
I would like to prepare a pull request for this issue.

This issue has been resolved as part of https://github.com/apache/pulsar/pull/7522
The problematic checkState invocation has been removed completely.

@sandrzejczak thanks for the confirmation. I will close this issue first.


Feature/basic repo setup

Related Tickets

SAR-###

Other Repos' PR(s) Intended to Work With This PR

LINK_TO_THE_PR or "None."

How Things Worked (or Didn't) Before This PR
Previously we had three open PRs (HbA1c, BP, Childhood immunizations) that all had some sort of pieces of repo setup that were needed - however, we want to start merging these PRs in independently, so I've taken all of the repo setup and put it here.
Readiness

[x] This PR passes all automated tests.
[x] This PR has no linting errors.
[x] This PR's changes to configuration files have been documented in all appropriate places (such as but not limited to README.md), if applicable.

Codecov Report

Merging #9 (778d346) into master (656353d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #9   +/-   ##
=======================================
  Coverage   91.82%   91.82%
=======================================
  Files          46       46
  Lines        3828     3828
=======================================
  Hits         3515     3515
  Misses        313      313

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 656353d...778d346. Read the comment docs.


Biometrics not working properly

After activating biometrics, I get mutiple fingerprint requests, and sometimes after about 3 or 5 inputs, the app just closes.
Samsung Galaxy Note 9

Is there any kind of error message on failed attempts? Could this be just something like scanner not working properly and then phone reacting to too much unsuccessful attempts?

No error, just keeps asking for the fingerprint ant then just works or fail silently. Can't know for sure if it's in the phone or the app. Other apps are working fine. Phone has original firmware without root.

No error, just keeps asking for the fingerprint ant then just works or fail silently. Can't know for sure if it's in the phone or the app. Other apps are working fine. Phone has original firmware without root.

Biometrics should be removed any from a bitcoin wallet

Fixed in https://github.com/btcontract/wallet/commit/ce7ab77e9f34fada3e4769e4146445fa4b987644.
There's now an option to use a built in PIN in case if fingerprint does not work right for whatever reason or user wants to avoid it.


Provide the concept of globjects being in drawing state

Provide two functions (e.g. glow::startRendering and glow::endRendering so that glow can track if any resource allocation is done during rendering (which is considered bad) and print warnings if it detects allocation.
This can help tracking performance issues.
As this is a purely debugging related feature, an easy way to disable the feature to either compile or runtime should be provided.

Dismissed for now.


Need support for file attachments

Looking for the ability for visitors to send file attachments such as pictures/videos to agents.

Hi,
we didn't added option to add files because we focused only on basic functionality.
However it can be archived using this method: https://developers.livechatinc.com/docs/visitor-sdk/#sendfile  ;)


node run publish generates error for aws s3 deployment

Following this guide: https://github.com/kriasoft/react-static-boilerplate/blob/master/docs/recipes/deploy-to-amazon-s3.md
Followed step 1 -> 3
When I do step 4: node run publish, I get the following error:
module.js:457
    throw err;
    ^

Error: Cannot find module '/home/magi/code/ico/run'
    at Function.Module._resolveFilename (module.js:455:15)
    at Function.Module._load (module.js:403:25)
    at Module.runMain (module.js:590:10)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

I'm using nvm, have tried node 6.0, 6.5, and latest 6.9.
Have tried clearing npm cache, removed node_modules, tried npm install instead of yarn, but it appears nothing I do can change this error. It appears to have nothing to do with the run.js file

It should be either yarn run publish or node tools/publish.js.. also you would need to tweak tools/config.js to set the deployment destination. Need to update the docs.

@jackywhlee if you want to deploy to s3 instead of firebase, try below
const task = require('./task');
const s3 = require('s3');

// deploy the app to Firebase
global.DEBUG = process.argv.includes('--debug') || false;

module.exports = task('publish', () => new Promise((resolve, reject) => {
  const client = s3.createClient({
    s3Options: {
      region: '_yourregion_',
      sslEnabled: true,
    },
  });
  const uploader = client.uploadDir({
    localDir: 'public',
    deleteRemoved: true,
    s3Params: { Bucket: '_yourbucket_' },
  });
  uploader.on('error', reject);
  uploader.on('end', resolve);
}));

Hmm. I had problems because build wasn't run on upload. Changed to the following
const path = require('path');
const s3 = require('s3');
const build = require('./build');
const task = require('./task');
const config = require('./config');

module.exports = task('deploy', () => Promise.resolve()
  .then(() => build())
  .then(() => {
    return new Promise((resolve, reject) => {
      const client = s3.createClient({
        s3Options: {
          accessKeyId: 'ACCESSKEY',
          secretAccessKey: 'SECRET',
          region: 'us-east-1',
          sslEnabled: true,
        },
      });
      const uploader = client.uploadDir({
        localDir: 'public',
        deleteRemoved: true,
        s3Params: {Bucket: 'BUCKET.NAME'},
      });
      uploader.on('error', reject);
      uploader.on('end', resolve);
    })
  })
  .then(() => {
    setTimeout(() => process.exit());
  }));


[WIP] No Region file

This takes #6248 to the next logical conclusion by removing the REGION file.
It tests that creating the database with the REGION environment variable will set the region correctly.
/cc @jrafanie :)

Please test this with replication, as it is the main consumer.

Please mark dependent PRs right in the title if they have not been merged yet.  It takes time to review, and I didn't realize the dependent PR wasn't merged until I got to the end :(

I should have posted this here instead of the other PR...ETOOMANYPRS

Oh, another thing to verify is log collection. I believe we pick up REGION and GUID as part of that process.

Got most of the way here.
Remaining tasks are to clean up the seeding and a few specs.
May want to revisit in the future, but doubtful.


About your translate function

Hi,
I clone your code and run "python main.py --word 风火山林 --num 7".
But only the first two lines are translated to English. Could you please tell how to deal with it?
Thank you very much!

很抱歉现在才看到消息，翻译我使用的是百度翻译的API对生成的诗句进行翻译，如果出现异常可能是接口规则改变了


Spaces query information for has-focus and is-visible is swapped

On the current master the information for has-focus and is-visible is swapped for multiple monitors.
When using yabai -m query --spaces is-visible is false for the non-focused monitor, while has-focus is set to true. For the focused and visible monitor both are true.

This was fixed in https://github.com/koekeishiya/yabai/commit/28c2e8e778210103c04d4574cbed446bd54bc965


[Feature] Custom keep alive intervall

To limit bandwidth we would like to change the interval the device is calling home. For us it would be totally fine if the device only contacts the server once every hour.
To access the shell there could be two options:

let the server know to establish a ssh connection next time he calls home and notify the user that a ssh session has been established
let the user predefine commands he likes to sent to the server. Next time the server calls home he will then execute them.

Related question

I was wondering where to put that option:

In the one line install script
In the settings page or ShellHub UI

I think it'd be nice if it'd be configurable on the settings page as it could receive it when "going home".
Imagine when it uses the keep-alive, the API server might reply to the agent with settings override. It could start small but provide a solid foundation for the future.
Thoughts?

Thinger.io does a good job to display the device state in the GUI. I think you could copy part of the concept:

Device state is considered "online/active" as long as the timeout is not reached.


Are there any examples of using Feign with Eureka?

The documentations has examples of using Fiegn without Eureka, but I'm unable to get Feign working with Eureka and can't find any examples or documentation on it.

I figured it out.
If you have @FeignClient("helloservice") then your application.yml needs this
helloservice:
  ribbon:
    DeploymentContextBasedVipAddresses: helloservice
    NIWSServerListClassName: com.netflix.niws.loadbalancer.DiscoveryEnabledNIWSServerList

You actually shouldn't need to do that.  I'm going to reopen to add a feign sample.  If you use @FeignClientScan and @FeignClient("helloservice") it should automatically use eureka.

There is already a feign sample here: https://github.com/spring-cloud-samples/feign. It uses a hardcoded server list, not Eureka, but the client configuration is the same.

I am hitting the same problem I think.  Without setting ribbon.DeploymentContextBasedVipAddresses and ribbon.NIWSServerListClassName the load balancer cant find the service and I have both @FeignClientScan and @FeignClient set.
It also seems like this question is related as well http://stackoverflow.com/questions/27483866/spring-cloud-with-feign-ribbon-eureka-unable-to-discover-service-instances

@ryanjbaxter I'll take a look

@ryanjbaxter I was unable to reproduce the problem with the sample project in the so issue you mentioned.  Any chance you can share a project?

@ryanjbaxter As I was implementing a feign eureka example, I got the following error while the ribbon/eureka caches warmed up.
Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.

Wed Jan 07 13:13:39 MST 2015
There was an unexpected error (type=Internal Server Error, status=500).
com.netflix.client.ClientException: Load balancer does not have available server for client: HelloServer

but after a minute or so, it starts working

I have waited about 15 minutes and the load balancer still cant find the service.  I will check out your sample and see what the potential difference is.

yeah, it should only be a minute or two

Can U guys help? :)
Where can I find @FeignClientScan?
I'm trying to build https://github.com/andrefaria/spring-cloud-feign-example... and getting...
[ERROR] /Users/abc/dev/github/spring-cloud-feign-example/src/main/java/example/App.java:[7,47] cannot find symbol
[ERROR] symbol:   class FeignClientScan
[ERROR] location: package org.springframework.cloud.netflix.feign
[ERROR] /Users/abc/dev/github/spring-cloud-feign-example/src/main/java/example/App.java:[17,2] cannot find symbol
[ERROR] symbol: class FeignClientScan
[ERROR] /Users/abc/dev/github/spring-cloud-feign-example/src/main/java/example/GitHubClient.java:[9,62] cannot find symbol
[ERROR] symbol:   method loadbalance()
[

I'm assuming the example is missing a dependency somewhere...

That's an old sample. Try @EnableFeignClients instead.

Thanks Dave, got it now, https://github.com/micklove/spring-cloud-feign-example
Loving the spring cloud stuff, keep up the good work :)


Paramount+ on SkyQ Receiver: tags.tiqcdn.com

Hi,
due to the block of tags.tiqcdn.com Paramount+ is not working on SkyQ Receiver in Germany.

Hello @the0bone thank you for this observation.
That's a tracker. It comes to us from upstream, via yoyo.org.  Please make your case with<EMAIL_ADDRESS>

Will also add, blocking tags.tiqcdn.com seems to block logging into Sunlife insurance portal

Thank you for this observation Amit @amit-bh.
So we're clear, there are no "legitimate" domains here.
It doesn't matter if a listing a domain interferes with fundraising by the Holy Sisters relict of Mother Theresa of Calcutta. If the domain vehicles tracking, adware, or worse, it gets listed here.
This repository serves people who value privacy and online safety, not Sunlife Insurance. If Sunlife or Paramopunt or SkyQ want people using their websites, maybe they should be  less scummy about it.


Fix default value setting for save_dir parameter in agentscope.init

name: Pull Request
about: Create a pull request
Description
In the current implementation, when the user does not specify the save_dir parameter in the external configuration, the agentscope.init method still requires the user to import _DEFAULT_SAVE_DIR to fulfill the default value setting. This is inconvenient, especially when users want to flexibly set the save_dir through configuration files.
Checklist
Please check the following items before code is ready to be reviewed.

[ ]  Code has passed all tests
[ ]  Docstrings have been added/updated in Google Style
[ ]  Documentation has been updated
[ ]  Code is ready for review

Modify the agentscope.init method to make the default value setting of the save_dir parameter more flexible. If the user does not specify save_dir in the external configuration, _DEFAULT_SAVE_DIR will be automatically used as the default value. This change eliminates the need for users to manually import _DEFAULT_SAVE_DIR, e.g.,
We have to import _DEFAULT_SAVE_DIR to meet the requirements
agentscope.init(
    project=self.config["project_name"],
    save_code=False,
    save_api_invoke=False,
    model_configs=self.config["model_configs_path"]
    ),
    use_monitor=False,
    save_dir=(
        self.config["save_dir"] or _DEFAULT_SAVE_DIR
    ),
)

We have to import _DEFAULT_SAVE_DIR to meet the requirements

I'm confused about the statement

when the user does not specify the save_dir parameter in the external configuration, the agentscope.init method still requires the user to import _DEFAULT_SAVE_DIR to fulfill the default value setting.

Why does agentscope.init requires the user to import _DEFAULT_SAVE_DIR? To use the default directory, maybe just leaving the save_dir for empty is okay?


chore(merge-back): 2.24.0

See CHANGELOG

AWS CodeBuild CI Report

CodeBuild project: githubautobuild-for-cdk-v2
Commit ID: 0b05838071c80061097188f9313ea8562319ab4c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


v0.13.2 release

v0.13.2

Updated dependencies

nerves_system_br v1.29.0
Buildroot 2024.08
Erlang/OTP 27.1.1

This PR was overcome by events.


Run reports migration before setting the alumni date.

I tested it locally and seems to be working fine.
r+


Fixes #107 by using OS dependent path separator.

make test fails due to indent. I will correct that.

@arkottke
JFI: there is no need to create a new PR for fixes in the future - you can update your existing PR/branch.

@blueyed Thanks, I think that makes sense. I am still learning the art of PRs.

No worries, and thanks again for doing them! :)


vFramer update for ED-cam to RGB calibration

vframer has the --out_height <int> and --out_width <int> parameters that should set the resolution of the output image.
The BLACK drawer is now inverted to better display the flashing checkerboard.

@marco-monforte and @GiuliaDAngelo - can you please test these functionalities work. We need to run a stereo calibration (i.e. MONO_CALIBRATION = 0) in which we input both the realsense RGB and the output of
vFramerLite --displays "(/edcam (BLACK))" --out_width <real-sense-width> --out_height <real-sense-height>

We tested the modifications and everything works: events are white over a black background, and dumped images from the vFramer reflect the input parameters


Something About Parallel Training

Thanks for your great work.
I'm trying to training in parallel, singe machine and two GPUs.
The program uses a single graphics card by default, then i set the --distributed
but there occurs an error
=> No resume checkpoint found at 'output/try_d/ReadySetGo/train/model_latest.pth'
Traceback (most recent call last):
  File "main.py", line 675, in <module>
    main()
  File "main.py", line 137, in main
    mp.spawn(train, nprocs=args.ngpus_per_node, args=(args,))
  File "/home/june/anaconda3/envs/FFNeRV/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 240, in spawn
    return start_processes(fn, args, nprocs, join, daemon, start_method='spawn')
  File "/home/june/anaconda3/envs/FFNeRV/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 198, in start_processes
    while not context.join():
  File "/home/june/anaconda3/envs/FFNeRV/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 160, in join
    raise ProcessRaisedException(msg, error_index, failed_process.pid)
torch.multiprocessing.spawn.ProcessRaisedException:

-- Process 0 terminated with the following error:
Traceback (most recent call last):
  File "/home/june/anaconda3/envs/FFNeRV/lib/python3.8/site-packages/torch/multiprocessing/spawn.py", line 69, in _wrap
    fn(i, *args)
  File "/home/june/projects/NeRVs/FFNeRV/main.py", line 318, in train
    len_agg = len(agg_ind)+1
NameError: name 'agg_ind' is not defined

i checked the code, here

    parser.add_argument('--agg_ind', nargs='+', default=[-2,-1,1,2], type=int, help='relative indices of neighboring frames to reference')
    parser.add_argument('--wbit', default=32, type=int, help='QAT weight bit width')

    args = parser.parse_args()

    global agg_ind
    agg_ind = args.agg_ind

BTW, i modified here for error sampler option is mutually exclusive with shuffle
@@ -303,7 +303,7 @@ def train(local_rank, args):

     train_dataset = DataSet(train_data_dir, img_transforms,vid_list=args.vid, resol=args.resol, frame_gap=args.frame_gap, )
     train_sampler = torch.utils.data.distributed.DistributedSampler(train_dataset) if args.distributed else None
-    train_dataloader = torch.utils.data.DataLoader(train_dataset, batch_size=args.batchSize, shuffle=True,
+    train_dataloader = torch.utils.data.DataLoader(train_dataset, batch_size=args.batchSize,
          num_workers=args.workers, pin_memory=True, sampler=train_sampler, drop_last=True, worker_init_fn=worker_init_fn)

Thank you for your interest and notice!
As the baselines used single-batch training, we have not focused on multi-GPU training.
Does it perform the same with reduced training time? It would be very useful to implement it!

Thank you for your interest and notice! As the baselines used single-batch training, we have not focused on multi-GPU training. Does it perform the same with reduced training time? It would be very useful to implement it!

I have not run through the program under multiple GPUs, but it is okay under a single GPU.
I am  a novice and trying to solve it. Thanks again for your work.


The canvas is redrawn when the content is entered

when I enter codes in the input box, the canvas will redrawn like the page refresh....how to solve this problem.
thanks~

Similar to #43 .
You have to separate the Particles component from the component which state changes.

thank you so much!
I created a new component named "particles" and put it in router.js, that the states chang will not affect the component


Typo

"Monetization is one of the most important elements of your game’s strategy..", Notice the 2 dots at the end.

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

ID: 400ac88a-cecf-1da2-3fbf-6540070bb74b
Version Independent ID: e6b7e92e-3757-0a93-8bf6-9961b1a966ec
Content: LiveOps features - PlayFab
Content Source: playfab-docs/personas/LiveOps/liveops-playfab-features.md
Product: playfab
GitHub Login: @v-kciril
Microsoft Alias: v-kciril

Thank you for reporting this. The content has been updated.


No license statement

I'd like to use this, but the absence of a license is a problem.

@KimberleyLawrence sent me #5, closing this issue as fixed.
Thanks for letting me know :+1:


[Feature] modelling, projections and parameters related to South African COVID-19 projections

Is your feature request related to a problem? Please describe.
This feature is related to standardisation when it comes to modelling that can be performed on the data.
Describe the solution you'd like
All over the world, researchers have published enough literature related to COVID-19, and there are two processes that can be decided upon by the group - and anyone interested in predictive modelling or forecasting, based on the data available within the repository.
If there could be two features that arise from this issue request, then it can be ideal.

The first is a Readme that describes literature and how it is being used to optimise features in predictive models that are currently being used globally by experts. Included in the Readme should be the features used in the models, as well as a reference to the literature used.

The second is a notebook/several notebooks that contain the code for such a model/models, based on the data in the repo. This script can be updated daily/weekly/once an update is made in the repo etc.

The scripts can be updated via github actions. See that now the data/calc folder is updated everytime the provincial confirmed cases data is updated.


Enable grey/beta options such as Auto Questions/Auto UI

Is there a switch we could turn on in order to enable the options? I can't find anything in the documentation? Or should we hide them based on user preferences?

Right now function calling doesn't work well across models. This is why they are disabled. However with models being more reliable now we can try to turn it on. I'll keep this ticket updated based on our progress.

I understand, but as a dev, how could I turn it on and experiment with it?

I'll let you know once they are back online. Making a huge and useful change.

The next version has them:


src: tests to create XML and HTML

Connects to #149
Missing test for mergeXMLs for now.

I was fighting with tape+blue-tape+Sync functions+ (Sync+Promised function)
I'll try to write later in a separated file to see what happens, or change the mergeXml function a bit to be able to use tape (or blue-tape) in a good way.

Coverage decreased (-9.4%) to 84.532% when pulling 2c3ee9a78fc943e908f44ed8dd2699cdef4f92ea on helio-frota:lr-149 into f4e226ffa7669dbbbc015aa32f86cd498d08d697 on bucharest-gold:master.


rm-modules needs to upgrade to readdirp 2.0.0+ to avoided minimatch security issue

rm-modules is using an old version of readdirp which is pulling in a version of minimatch that has a security issue.  readdirp 2.0.0+ uses the latest version of minimatch and should resolve the security warning.
WARNING] npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
[INFO] ├─┬<EMAIL_ADDRESS>[INFO] │ ├─┬<EMAIL_ADDRESS>[INFO] │ │ └──<EMAIL_ADDRESS>[INFO] │ └─┬<EMAIL_ADDRESS>[INFO] │   ├──<EMAIL_ADDRESS>[INFO] │   ├─┬<EMAIL_ADDRESS>[INFO] │   │ └──<EMAIL_ADDRESS>[INFO] │   └──<EMAIL_ADDRESS>

I just pushed my fork  and published new release 1.1.0 to npm with fix for this issue (readdrip updated to v3.6.0).


Cleaner way to build header string

This is just a 'cleanup', which handles building the header string in a slightly more readable way (no battling ' vs ").
No additional spec coverage as original specs cover the same case, and output should be identical.

@carpodaster back with you now 👍

Thanks!


Escaping string for variable value.

Firstly, thanks for all the hard work!
Not an issue, more a question. Is it possible to use any arbitrary string as variable value? An example from lesscss:
.weird-element {
  content: ~"^//* some horrible but needed css hack";
}

My use case:
--heading-font-family: ~"string here";

Output:
--heading-font-family: string here;

I totally understand this may not be possible and that cssnext isn't lesscss.
:cake:

You should be able to escape css with , this it not related to string or something.
example of valid css classname: .stuff\@md.

I may have picked the wrong wording. I want to use any string for the variable value, this may not be a css value, for instance:
--heading-font-family: <?php /* code */ ?>;

Thanks for the response, I appreciate this maybe out of the scope of cssnext.

You can in theory use any value that respect css syntax. cssnext use postcss so be sure to provide something that the parser accept. Or you can try to add your own parser, but indeed, that's not the scope of cssnext.


Edge 105 and 106 send cipher 4866 twice in ClientHello

The Cipher Suite
TLS_AES_256_GCM_SHA384 (0x1302)

is sent twice in ClientHellos by Edge in versions 105 and 106: once in position 2 and again in position 3 of the cipher list.
It makes no sense to send the same cipher twice, and some very defensive TLS stacks reject such ClientHellos.
I haven't seen this behaviour from Chrome or the other Chromium-derived browsers.

Thanks for reporting this. However, this isn't related to Edge DevTools, but rather to the browser itself. The right channel to send feedback about the browser is in the browser directly:

Click Settings and more (the ... button in the toolbar).
Help and feedback.
Send feedback.

Can you please send your message again this way? Thanks for your understanding!


koverHtmlReport task fails when macrobenchmark project is configured

Describe the bug
koverHtmlReport task fails when macrobenchmark project is configured. Sample is available here (forked from https://github.com/android/performance-samples): https://github.com/smozhaykin/performance-samples/commit/def292eb33d9574056b734995c953b23228abd4c
Errors
gradlew clean koverHtmlReport
> Task :macrobenchmark:koverHtmlReport FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Some problems were found with the configuration of task ':macrobenchmark:koverHtmlReport' (type 'KoverHtmlTask').
  - In plugin 'org.jetbrains.kotlinx.kover' type 'kotlinx.kover.gradle.plugin.tasks.reports.KoverHtmlTask' property 'filters' doesn't have a configured value.

    Reason: This property isn't marked as optional and no value has been configured.

    Possible solutions:
      1. Assign a value to 'filters'.
      2. Mark property 'filters' as optional.

    Please refer to https://docs.gradle.org/8.1.1/userguide/validation_problems.html#value_not_set for more details about this problem.
  - In plugin 'org.jetbrains.kotlinx.kover' type 'kotlinx.kover.gradle.plugin.tasks.reports.KoverHtmlTask' property 'reportDir' doesn't have a configured value.

    Reason: This property isn't marked as optional and no value has been configured.

    Possible solutions:
      1. Assign a value to 'reportDir'.
      2. Mark property 'reportDir' as optional.

    Please refer to https://docs.gradle.org/8.1.1/userguide/validation_problems.html#value_not_set for more details about this problem.
  - In plugin 'org.jetbrains.kotlinx.kover' type 'kotlinx.kover.gradle.plugin.tasks.reports.KoverHtmlTask' property 'title' doesn't have a configured value.

    Reason: This property isn't marked as optional and no value has been configured.

    Possible solutions:
      1. Assign a value to 'title'.
      2. Mark property 'title' as optional.

    Please refer to https://docs.gradle.org/8.1.1/userguide/validation_problems.html#value_not_set for more details about this problem.

Expected behavior
Kover plugin should gracefully handle projects with macrobenchmark.
Reproducer
https://github.com/smozhaykin/performance-samples/commit/def292eb33d9574056b734995c953b23228abd4c
Environment

Kover Gradle Plugin version: 0.7.4
Gradle version: 8.1.1
Kotlin project type: Kotlin/Android

Closed as stale.
Feel free to open new issue if you have any additional questions.


Ensure language server is not blocked on discovery

If discovery takes a long time (https://github.com/microsoft/vscode-python/issues/18200), it seems language server is not started until it has finished, even though it is not "blocked" on discovery NodeJS-wise. This prevents users from using the most basic features like the indexer, so they can't click through functions, variable definitions, etc.
In https://github.com/microsoft/vscode-python/issues/18200 the user is blocked for about 15 mins, files are also on a shared network drive.
As language server activations takes less time, I think we can afford to postpone triggering discovery until after it has started. FYI @kimadeline as you're working on the new design to activate/deactivate language servers 🙂
cc/ @karthiknadig

Friendly ping on when this might be slated for development? My team of 200 hits this every morning and at lunch when we come back to our IDEs

Unfortunately we haven't been able to prioritize it yet partly as it didn't get enough upvotes. Does the VSIXs provided in https://github.com/microsoft/vscode-python/issues/18200 serve as a workaround?

Thanks @karrtikr, I can use the VSIX but I think it gets wiped every time I update the extension. If this post receives enough upvotes would it be prioritized?

It'll have much more chances of being prioritized yes.

I can use the VSIX but I think it gets wiped every time I update the extension

You can follow https://stackoverflow.com/a/63831525/8152786 to stop auto-updates for the Python extension.

https://github.com/microsoft/vscode-python/issues/18647 received enough upvotes as well and could work for you.

@wubdub https://github.com/microsoft/vscode-python/issues/19102 now ensures auto discovery only happens in the first session and turns it off for subsequent sessions. Try the latest pre-release, activate the extension, and then reload window, auto-discovery should no longer happen:

Let me know if that unblocks you.

This is now only a problem the first time a scope is opened.

@wubdub #19102 now ensures auto discovery only happens in the first session and turns it off for subsequent sessions (given Jupyter is not installed). Try the latest pre-release, activate the extension, auto-discovery should no longer happen:

Let me know if that unblocks you.

Sorry for the delay in getting back to you. Running v2022.9.11681004, I still have the same problem as I originally reported, the "Discovering Python Interpreters" with a spinning icon runs and during this time no language features are available (such as click to go to definition or syntax highlighting). Like before, the output terminal has logs like > /XXX/shared/conda-envs/XXX-9f9d08bc8-990/bin/python ~/.vscode-server/extensions/ms-python.python-2022.9.11681004/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2022.9.11681004/pythonFiles/interpreterInfo.py and spins for 10+ mins. This is looking at one file that previously was indexed the last time VSCode was open

Do you have Jupyter extension installed? Note that still needs to be disabled.

Ah! Amazing I disabled Jupyter extension and now it is instant, thanks!


Migrate From NewtonSoft.Json to System.Text.Json

as a follow-up of issue https://github.com/xpouyat/MK.IO/issues/57

I am maintaining the code into a specific branch https://github.com/microsoft/MK.IO/tree/dotnet-9-with-native-json


First 1500 customer one year €25 discount / Exclude customers from discount when they have already have one

What if we would like to give the first 1500 customers €25 off the first year they apply for certain subscriptions? This would not be a coupon code, but a sale or discount. One that is valid for one year only and for certain yearly packages only. Would I still need to make a coupon contract for this? It is a discount applied to the standard packages for one year.
It is not a coupon code we will hand it so wonder what the right way to go is here. We have built this in but now that we are planning to migrate to Cashier Mollie we would appreciate some pointers
Two, are there existing methods to apply coupons or discounts only when no other discounts are running? When a customer has a Halloween discount for example we would not want these guys to get another Christmas discount on top.
Thanks for your feedback. This package is really appreciated a lot.

To prevent nasty concurrency issues I'd:

apply the discount reactively by adding 25€ to their balance and not use a coupon

or switch them reactively to a dedicated discounted plan, and update the price on that plan after a year or switch them to the original plan.

Thanks for getting back on this @sandervanhooft . Sounds like solid approaches. As for discount or coupon discounts applying and excluding customers that already have a discount running, if you have pointers for that as well please let me know.

There are no methods available for this, as features like these tend to get very use case specific.
Best to start out by checking the  RedeemedCoupon model and accompanying table.
Also note these related RedeemedCoupons are accessible through the billable model:
https://github.com/laravel/cashier-mollie/blob/6acdadc69b00bde337c37a10b6e2f1838ac93217/src/Billable.php#L537
Closing this for now, let me know if it should be reopened.


WCIFS/AttachLayerStorageFilter read-only mount support

This is a fairly speculative feature request, since it almost certainly requires OS-level support.
I was reminded by discussion in a containerd PR that the current best-known (by me...) approach to do a read-only mount of a committed WCOW container image on the host is to mount it as a read-write mount with a small-as-possible sandbox/scratch VHDX, and then discard that VHDX at the end.
Although workable, this suffers from two issues:

Anything that tests the readonlyness will see a read-write layer; although this is a documented-valid implementation, the containerd Snapshotter test suite doesn't currently agree.
We're spending time on VHD manipulation/mounting needlessly.

So the request is that either AttachLayerStorageFilter gain a parameter, or a new API be introduced, that would in-effect take just a layerData structure, with no layerPath, and resulting in a mountable volume GUID or whatever AttachLayerStorageFilter actually produces... (See #1076 where I documented that I have never used AttachLayerStorageFilter successfully, so am not totally sure what the expected flow is).
Looking at the user-space WCIFS and Bind Filter APIs introduced after RS5 (which I learned about via #1462), the tools for this might already exist at an OS level, in Windows Server 2022, if I'm guessing correctly that a Bind Filter merged mapping is the same as a WCIFS layer stack.
The other reason this is speculative is that I don't have a concrete use-case for this apart from "the containerd snapshotter tests this". I suspect BuildKit's COPY --from=<some_image> will hit this code-path, though, from minimal code-tracing efforts, as it relies on host-mounts, which is how that PR got started in the first place.

For the record, in containerd we ended up mounting the volume read-write as usual with WCIFS, and then using a read-only bindfilter binding to the target directory, so it looks read-only to the caller.
Because it's WCIFS, we still use the scratch VHDX that we discard later, i.e. on the snapshotter side the readonly/readwrite disctinction is currently irrelevant. (Resizing the VHDX down from the default 20GB hit issues in the test suite, so we dropped that, since the read-only bind means we should never touch that (sparse) volume anyway).
So still scope for this issue to be resolved nicer, e.g., a read-only WCIFS Activate/Prepare-alike that doesn't need a scratch layer.


docs: Tweak FAQ

Update What can you do with PRQL to say... "Prototype PRQL queries...";
Update Press Materials link to point to PRQL/prql-brand;
Fix "What's with the 'aggregate'..." heading

@aljazerzen What should happen to the dbt-prql reference? Thanks

What should happen to the dbt-prql reference?

That can go out. It's not usable at the moment.

What should happen to the dbt-prql reference?

That can go out. It's not usable at the moment.

The current website lists dbt-prql and Jupyter. Are neither of these available now? Thanks.

Jupyter works, dbt does not.
Can you also include this:
For more information about what's possible with PRQL, checkout
[Querying with PRQL](https://eitsupi.github.io/querying-with-prql/).

@richb-hanover sorry I lost track of these, I've gradually been getting my notifications back in order.
These are good improvements as ever, thank you!


Allow error to be of node type

In case you want to display a link in the error message.

PropTypes.node seems to be the right thing to use then to allow all sort of "rendering" elements.

Oh, I did not know this type existed. thanks, will change!

From the doc

// Anything that can be rendered: numbers, strings, elements or an array
// (or fragment) containing these types.
optionalNode: React.PropTypes.node,

So only node is enough. Also, could you please squash your commits please?

It took a while but I think I squashed it. Always grateful for a chance to work on my git skills.

perfect! :) Thanks @Gregoor


Support for selectors when deciding which links to follow (set-based label)

It should be possible to follow up on selectors taht are using set-based labels
https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
Currently, we are not capable of processing them properly, and thus we are missing on advanced use cases (taints, advanced selectors)
Supporting this type of selector implies being able to understand and follow up on matchExpression, for at least Job, Deployment, ReplicaSet and DaemonSet.
In, NotIn, Exists, and DoesNotExist
It should be possible to use these selector to filter resources in the search

We need to split this into 3 issues: one for the logic and two for the UI (desktop + cloud)


Consider using functools.singledispatch to replace 'registries of functions to call depending on type'

https://docs.python.org/3/library/functools.html#functools.singledispatch
E.g. could be used to replace script_repr_reg.
There's a backport to python 2, but it has to be installed from pypi. So this is something to consider in the distant future.

So this is something to consider in the distant future.

2020 when Python 2 is no longer supported?

Just a note that I vaguely recall we often don't respect the class hierarchy when looking things up in dicts, but various times we should.

@jbednar doesn't likely to be urgent for anyone anytime soon.

Just a note that I vaguely recall we often don't respect the class hierarchy when looking things up in dicts, but various times we should.

E.g.
https://github.com/holoviz/param/blob/master/param/parameterized.py#L2324
vs

Where there is no registered implementation for a specific type, its method resolution order is used to find a more generic implementation.

(https://docs.python.org/3/library/functools.html#functools.singledispatch)


[Idea] Function to look for files which can potentially have the license

I'm not even sure this function belongs here, but I'm throwing this idea anyway.  As far as I understand, licensecheck reads the content of a file and tries to determine whether it matches a known license.  The problem is that often you need first to find the license file.  Unless you plan to open all files in a directory, I suggest to have a function which looks for files with names usually employed by license files (case insensitive):
COPYING
COPYRIGHT
LICENCE
LICENSE
NOTICE
...

plus all possible combinations with extensions like .txt, .md, .rst.  Sometimes license files have the name of the license, like GPL.txt, or GPL-2.0.txt.

Yeah, that sounds useful. Probably that function would have to be duplicated by most users of LicenseCheck if it doesn't exist here, so this is a good place for it.
We could re-use the list of names in OSI_LICENSES for things like GPL.txt, though that will only work if the license is OSI approved and the name they use is the SPDX identifier.
A kind of wild idea would be to just try every plaintext toplevel file and take whichever one has the highest percent_covered. That seems like it would be pretty comprehensive but could take awhile if for some reason there were many top-level files, or if there were really big files (which could cause licensecheck to be slow).


add package version to github workflow

Sometimes we need to get python package version from github workflow CI.
steps:
  - name: Set the value
    id: step_one
    run: |
      echo "action_state=yellow" >> $GITHUB_ENV
  - name: Use the value
    id: step_two
    run: |
      echo "${{ env.action_state }}" # This will output 'yellow'

add the following:
env.package_version_short
env.package_version_full
env.repo_name
env.repo_owner

they could be used in web hook like this:
      - name: Dingtalk Robot Notify
        uses<EMAIL_ADDRESS>        env:
          DINGTALK_ACCESS_TOKEN: ${{ secrets.DINGTALK_ACCESS_TOKEN }}
          DINGTALK_SECRET: ${{ secrets.DINGTALK_SECRET }}
        with:
          msgtype: markdown
          notify_when: 'success'
          title: CI Notification | Success
          text: |
            ### Build success
            ${{ env.package_version_full }} is built and published to test pypi
            ### Change History
            Please check change history at https://${{ env.repo_owner }}.github.io/${{ env.repo_name }}/history
            ### package download
            Please download the pacakge at: https://pypi.org/project/${{ env.repo_name }}/

and the result could be:
### Build success
cfg4py 0.9.3.DEV.22 is built and published to test pypi
### Change History
Please check change history at https://zillionare.github.io/cfg4py/history
### package download
Please download the pacakge at: https://test.pypi.org/project/cfg4py/


Change perf script timeout mechanism

Probably a bad idea to do a delayed killall qps_workers on a machine given that the same machine is used in many tests.

This PR is not the right way to solve this problem, so closing it up.


Service Reference Overviews, Namespace Summaries

:x: Validation status: errors

File
Status
Preview URL
Details

api/overview/azure/index.yml
:x:Error

Details

:x:Error

Details

api/overview/azure/index.yml

[Error] Error transforming model "W:\qn4t-o-unknown\raw-\3vkdm5ig.sma\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

[Error] Error transforming model "W:\qn4t-o-unknown\raw-\3vkdm5ig.sma\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

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


Multiple invocation of @HiltComposeNavigationFactory create method

I am facing issue where create of @HiltComposeNavigationFactory is getting called multiple time causing infinite invocation of compose. I am not sure what is triggering this but i followed exact same steps as your sample,

hi @shekaroppo
sorry to hear that. I'm happy to help trying to resolve this. Out of interest is the project your trying to integrate this into public?
Failing that can you please tell me your versions of the following:

Gradle
Jetpack Compose
Dagger/Dagger Hilt


Specific data types for FDP

One of the FDP templates, created by NCI, has a list of specific data types that they are interested in having appear on the Research Outputs tab. These are more areas of research than types of outputs, so I'm not sure where best to put it. Let's discuss.

We can add these fields as options for when we allow admins to determine what data types appear in the RO list.

We need to allow organizational administrators to replace the list of default research output types, or add additional types to the default list.
Here is a screenshot of the select box a researcher currently interacts with when editing/adding a research output:

Please refer to the spec document for some ideas on implementation.
This will require the creation of a new table that stores the template_id foreign key and the value of the type. When the admin wants to append their entries to the default list, the code should add an entry for each default type to this table . This will ensure that changes to the default list do not change the admin's selections over time.
The current output types are defined as an enum on the research_output model. If it makes things easier, those values can be moved into a separate table of their own.
The template model will then need to be updated to ensure that the version method is still working and does not require any changes needed to accommodate the new values. The Template's deep_copy method should also be updated to ensure that the values in the table are carried forward to new versions.
Once the admin components are in place, the research outputs view and controller will need to be updated to fetch the correct values.


2 Fixes for Problems when refunding custom rewards and getting reward redemptions.

Describe the bug
1.Refunding a custom reward doesn't works with .refund() .
2.get_reward_redemptions() always throws an error.
Are you using TwitchIO within a Discord Bot?
Yes
What commit of TwitchIO are you using?
1.2.0
How to fix these Bugs:

in dataclasses.py in line 647/648
data = await self._http.update_reward_redemption_status(token, self._broadcaster_id, self.id, reward_id,                                                                  "CANCELLED")
has to be
data = await self._http.update_reward_redemption_status(token, self._broadcaster_id, self.id, reward_id,                                                                  False)
and in http.py in line 416
 status = "FULFILLED" if status else "CANCELLED"
has to be
 status = "FULFILLED" if status else "CANCELED" because the Twitch API only wants 1 L

in http.py there is a / missing in line 412
return await self.request("GET", "channel_points/custom_rewards/redemptions", params=params, headers={"Authorization": f"Bearer {token}"}, limit=limit)
has to be
return await self.request("GET", "/channel_points/custom_rewards/redemptions", params=params, headers={"Authorization": f"Bearer {token}"}, limit=limit)

(please complete the following information):

OS: Windows 10

I couldn't actually test these as I'm not an affiliate, so thanks!

I couldn't actually test these as I'm not an affiliate, so thanks!


requirements: mention unmotivated forks

https://make.wordpress.org/plugins/2015/08/26/forks-and-copies/ has some good wording of what's acceptable.


0.2.0 版本UI启动有webpack兼容问题，0.1没问题

Uncaught TypeError: Cannot assign to read only property 'exports' of object '#'
at Module.eval (webpack-internal:///./node_modules/webpack-dev-server/client/clients/BaseClient.js:26)
at eval (webpack-internal:///./node_modules/webpack-dev-server/client/clients/BaseClient.js:42)
at Module../node_modules/webpack-dev-server/client/clients/BaseClient.js (app.js:7498)

it guess this should reported to dubbo-admin?

可以到这里建issue: https://github.com/apache/dubbo-admin/issues


Not able to run the project

This error pops up when i run the project:

Which version of the plugin and which stencil version did you use?

Which version of the plugin and which stencil version did you use?
Hi @DominikPieper  I am using the following version of stencil and plugin

"@nxext/stencil": "^1.1.0",
"@stencil/core": "1.16.3"

Okay, one question that came up. Nx 10? Until now there's no nx 10 support


Segmentation violation - goroutine panic on shutdown of node

Background
After requesting the shutdown of the lnd process at the end there was a segmentation violation error and a bunch of goroute panic stacktraces:
https://gist.github.com/cryptagoras/0e2d6ec01f2772a8fc0c039ba2900ac5
Your environment

0.5.0-beta commit=2f1b0246798eab417cf928d720140237bb08d0ff

operating system: Ubuntu 16.04 LTS - Linux host 4.4.0-119-generic 143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

bitcoind: Bitcoin Core v0.16.2

Lots of available resources (CPU/RAM)

Popular LND node 330-350 active channels & peers

Many long-lived channels

Steps to reproduce
Logs with stacktraces: https://gist.github.com/cryptagoras/0e2d6ec01f2772a8fc0c039ba2900ac5
Active node with long history maybe, during shutdown.
It happened at least twice, but then I tried again 4 times but I never got the stacktraces of doom, just once I got a 1-line segfault error but no stacktraces.
Expected behaviour
Shutdown cleanly without erros
Actual behaviour
Goroutine stacktraces of doom on shutdown

The issue here looks to be with boltdb in that as you're shutting down, the DB has already been closed.

How are you trying to shutdown lnd?

Single Ctrl+C, I think the culprit might be some "corrupted" old channel and the combo with the hundreds of channels.

It boots normally, but :disappointed: yes I forgot to mention I do have a script that polls crudely by calling 6 lncli commands sequentially with 10 seconds delay between those group of calls.

Looks like this can be prevented by adding a check to the RPCs to exit if the server is in the process of shutting down as the RPC server is shut down after.


Feature: lifecycle preStop postStart hooks in Kubernetes pods

From @Cryptophobia on June 12, 2017 20:46
We are trying to implement lifecycle preStop and postStart hooks that will be respected by resque workers inside Kubernetes pods. We want to define scripts that will run in the Deis applications by setting environment variables to run preStop and postStart hooks. Except imagine that the command part is just a long environment variable set in Deis environment variables:
    lifecycle:
      postStart:
        exec:
          command:
            - "/bin/bash"
            - "-c"
            - >
              echo 'Ran the postStart Lifecycle Handler' > test;
      preStop:
        exec:
          command:
            - "/bin/bash"
            - "-c"
            - >
              kill -QUIT 1;

The problem that we are encountering is this:
The deis/kubernetes process is monitoring the worker process, in our case resque-pool with pid 1. Once we send the -QUIT command to this process, the Kubernetes worker pod enters "CrashBackoffLoop" and restarts the main resque-pool worker process. This is great behavior for resiliency, but not the behaviour we want because we want the pod to be terminated after the workers are terminate gracefully. However, the worker pod is restarted because something is monitoring the main process.
Is there a way we can unhook the deis/kubernetes main process monitor from binding to pid 1 from inside the pod or is there a simpler way to implement lifecycle hooks like the example above?
We were hoping for a successful test so that we can contribute to the deis-workflow by adding environment variables for lifecycle hooks and support for them.
Any help would be greatly appreciated.
Copied from original issue: deis/workflow#825

Any update on that feature?


Python: Fix FC stepwise planner.

Motivation and Context
The FC stepwise planner was breaking when trying to process the function call result because if a filter is not configured, then the context will be None. We need to only try to extract the FC result if the context is not none, otherwise it will already be present in the chat history.

Description
Check that the FC result context is not None, if so, then extract the FC result, otherwise proceed as the FC result is in the chat history. Fixes #6350.

Removes some extranous logging from json schema addition.

Contribution Checklist

[X] The code builds clean without any errors or warnings
[X] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[X] All unit tests pass, and I have added new tests where possible
[X] I didn't break anyone :smile:

Python 3.10 Test Coverage Report • FileStmtsMissCoverMissingsemantic_kernel/planners/function_calling_stepwise_planner   function_calling_stepwise_planner.py1094261%125–212, 246–251semantic_kernel/prompt_template/utils   jinja2_system_helpers.py48394%15, 45, 50semantic_kernel/schema   kernel_json_schema_builder.py45296%32, 57TOTAL6232103083%
Python 3.10 Unit Test Overview

Tests
Skipped
Failures
Errors
Time

1341
1 :zzz:
0 :x:
0 :fire:
13.046s :stopwatch:


Supports setting the vfox configuration path via the VFOX_HOME environment variable

close: #45

This also involves the issue of whether there are permissions. In addition, The default permissions granted now are 0755. Since we are allowed to change VFOX_HOME, we should also consider the permissions.

This also involves the issue of whether there are permissions. In addition, The default permissions granted now are 0755. Since we are allowed to change VFOX_HOME, we should also consider the permissions.

This is a problem, I will add a check for VFOX_HOME permissions.

Regarding permissions, currently, only errors related to insufficient permissions are being returned.
As for #51, regarding the potential support for multiple users sharing the VFOX_HOME directory, this would require setting permissions to at least 775. We need to discuss this matter further, perhaps it could be addressed in another PR.

Regarding permissions, currently, only errors related to insufficient permissions are being returned.
As for #51, regarding the potential support for multiple users sharing the VFOX_HOME directory, this would require setting permissions to at least 775. We need to discuss this matter further, perhaps it could be addressed in another PR.

Yes, so simply changing VFOX_HOME does not seem to be of much use at present. The default 755 permissions still limit this feature.

Can you add command like vfox config store-path=D:/app/vfox

Can you add command like vfox config store-path=D:/app/vfox


xp.from_dlpack to move data to a preallocated array on the target device

Since #741 was merged, it should now be possible to perform data transfers across devices and namespaces in a standard, namespace agnostic way (as long as both namespace have a shared understanding of a common device type, such as the CPU/host).
However, such transfers cannot reuse pre-allocated buffers in the target namespace/device.
Would it be possible to add an out argument to from_dlpack?
def move(x, y):
    xp_x = x.__array_namespace__()
    xp_y = y.__array_namespace__()
    if not xp_x == xp_y:
        xp_x.from_dlpack(y, copy=True, out=x)  # device=x.device is implicit in this case.
    else:
        x[:] = y

This API might be a bit too weird. I am open a to better suggestions.

This question isn't specific to DLPack, is it? It seems to me that this is the same as a generic out= keyword or a "reuse this memory" API (or at least the other copy= keywords in functions like asarray). The main discussion on that happened in gh-24.

Ah yes sorry, I forgot about that. Let's close.

@ogrisel this is a very good exercise to consider the design challenges for what you asked for, even if we were to allow out= in the standard.
In your snippet, xp_x (xp_y) is the consumer (producer), and we're passing a consumer array x to from_dlpack. As noted elsewhere, DLPack is a one-way protocol, not two-way, but your requirement means a capsule (for x) needs to be passed to the producer from a consumer too (but so far we only support the other way around), which requires a two-way protocol.
Furthermore, the latest copy feature is possible because the burden is still on the producer to provide a valid capsule, whose deleter would be responsible for releasing the tensor back to the producer when it's done. With this two-way exchange, the deleter is no longer specific to the producer anymore. We would at least need to set the deleter as no-op when out= is set (and I might have missed other subtleties here).
In any case, it's technically not feasible without redesigning the exchange protocol. Not saying it can't be done, but it'd take quite some effort.


Does React-Fastclick needs Fastclick ?

Hello;
I don't get the what react-fastclick does. Thinking that it remove the 300ms delay from click event; I would like to know if  for using react-fastclick I need first fastclick and what are the browser that it supports?

You don't need fastclick on the page to use this
This is a React component that you can wrap around your other React components that listens for touch start and touch end events and detects a 'tap' similar to how FastClick works, and then triggers a 'click' and/or 'focus' on the tapped element


feat: Add Intel Enhanced Optimizations for RDS MySQL Example

Description
The PR adds an Intel Enhanced Optimizations for RDS MySQL example. The example implements:

Intel Xeon Instance Selection
Intel Xeon MySQL Optimizations via an Intel Parameter Group module

Please squash commits if approved/merged.
Motivation and Context
New Example
Breaking Changes
No
How Has This Been Tested?

[X] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[X] I have tested and validated these changes using one or more of the provided examples/* projects

[X] I have executed pre-commit run -a on my pull request

Successfully tested deployment:

TF Plan/Apply
TF Idempotency(terraform plan/apply a second time)
Destroy

thank you for the PR - however, I don't know that this is the appropriate place for this. From what I can tell, this is mostly just using the module that you all have created for the parameter group. The examples we have provided here are demonstrations of the various configurations that this module supports - users are absolutely able to provide their own parameter groups and/or parameter group values, but it doesn't really have any bearing on the examples we've provided. Closing this for now

thank you for the PR - however, I don't know that this is the appropriate place for this. From what I can tell, this is mostly just using the module that you all have created for the parameter group. The examples we have provided here are demonstrations of the various configurations that this module supports - users are absolutely able to provide their own parameter groups and/or parameter group values, but it doesn't really have any bearing on the examples we've provided. Closing this for now

Hi Bryant,  in our example we are showcasing the Intel Optimizations based on our Intel Xeon Tuning Guides.  Our goal was not to show how to utilize parameter groups, but to highlight the specific optimizations/configuration that can increase RDS performance based on Intel Architecture.   We spoke with @antonbabenko at HashiConf & then again at AWS re:Invent about showcasing these value add to customers.    Please let me know if there are additional questions or if a quick meeting would be best.   Thank you  Josh H   cc: @lucasmelogithub

@bryantbiggs What you say was also my point to Josh when I met him in October. :) Such examples are not as helpful since users can specify whatever they want in the argument. We know that, and usually, we don't accept such contributions.
On the other hand, let's consider some changes and review it once more if it makes sense to have it here or not. I recommend that the author make this example 100% self-contained without reference to external modules (like this) and unnecessary logos/images. Include the correct/optimal values for the parameter group as arguments to the module created by this repository - this can be the only interesting part of the example that differentiates it from other similar examples we already have. Leave links to the external repositories/sources, if necessary.

I like referring to text documents with or without the code inside. I also don't want us to maintain code where we depend on external repositories we don't control.
@lucasmelogithub @JoshHilliker What do you think? Will you be able to do the change?

I like referring to text documents with or without the code inside. I also don't want us to maintain code where we depend on external repositories we don't control.
@lucasmelogithub @JoshHilliker What do you think? Will you be able to do the change?

@antonbabenko  @bryantbiggs - Lucas & I were talking, what are your thoughts about moving the Intel MySQL parameter group module into this repo, that way it's managed under the same tree, but we can still use the sub modular approach.

I looked into the Intel MySQL parameter group module once more, and the only piece of code that can be interesting to have in our module is this variable - https://github.com/intel/terraform-intel-aws-mysql-parameter-group/blob/main/variables.tf#L1-L165 .
I don't see a need to make a separate submodule in our repository just for this variable, but instead, I prefer to add a small example or just a markdown file with such values listed. Everyone interested in knowing how to use this module to deploy RDS resources with an opinionated config provided by Intel can just look there.
I will let @bryantbiggs decide if he is open to "a small opinionated example" or a "markdown file" (as Bryant mentioned earlier). I am more in favor of a solution that requires less maintenance (=markdown file).

I think what is important as well is the benchmarking and branding of Intel behind these data points in the variables.tf.   We kept this as a separate module to have updates/consumption via git tags w/ the standard tf source version control.    I think having this a separate module with reference to Intel (we can remove image branding) would be of high value to consumers of the module.  We plan to continue to update the module as new Xeon generations land on AWS.  @antonbabenko  @bryantbiggs @lucasmelogithub

@bryantbiggs  @antonbabenko  - Happy New Year!    Love to pick this back up and get your feedback on my latest comment.   Thank You

Hi @JoshHilliker  - so if you wish to keep the module separate and as a standalone module, then I think that we are discussing here is just a markdown file that demonstrates how to use the module with this module plus any other details might need to be aware of and links back to your module/docs.

Lucas & I talked more. Here's our proposal: 1) removal of Intel branding from Enhanced-Optimization example 2) pull in all parameter group configuration into the stand alone example, so no external dependencies. What do you think?

@antonbabenko  @bryantbiggs

But we (Anton and I, and other contributors) do not have knowledge or experience with these Intel enhanced optimizations - so it doesn't make sense to have code here for that because we will be unable to troubleshoot it. This is why the static markdown is recommended - we can inform users of these configurations and of the module that will do this for them, but we're not testing and validating that

But we (Anton and I, and other contributors) do not have knowledge or experience with these Intel enhanced optimizations - so it doesn't make sense to have code here for that because we will be unable to troubleshoot it. This is why the static markdown is recommended - we can inform users of these configurations and of the module that will do this for them, but we're not testing and validating that

Okay..  here's my proposal.  we can create an example directory for this and put in the markdown file.   good?

@JoshHilliker Yes, please do that, and link to such an example from the main README.md file in the root.

@JoshHilliker Yes, please do that, and link to such an example from the main README.md file in the root.

Closing PR. A new one will be created per discussion above.


Adding pytest and pytest-black dynamic and static settings

adding initial settings for using pytest and avoid conflicts with other PRs of the common basis of PRs related to tests using pytest

The issue got split into two separate issues


Line items, remove redirectUrl, Adyen_paymentMethod

Summary

Tested scenarios

Fixed issue:

Sorry guys, I don't understand why you fix all issues in one PR?
They're related? and also why there's no description at all


remove unused script and update the doc

Contributing to the Azure SDK
Fix https://github.com/Azure/azure-sdk-tools/issues/9422

Remove Invoke-GenerateAndBuild.ps1 which is not used anymore
Rename the script Invoke-DataPlaneGenerateSDKPackage.ps1 to Invoke-AutorestDataPlaneGenerateSDKPackage.ps1 to clear that this script only for generate SDK with OpenAPI/swagger.
Update the doc to clarify that the scaffolding is for SDKs with TypeSpec

Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/azp run

/azp run net - eng-script-tests

https://github.com/search?q=repo%3AAzure%2Fazure-sdk-for-net Invoke-GenerateAndBuild.ps1&type=code
I still see references to the script you are removing. We should either update those or clean those up as well.

/azp run net - eng-script-tests

https://github.com/search?q=repo%3AAzure%2Fazure-sdk-for-net Invoke-GenerateAndBuild.ps1&type=code
I still see references to the script you are removing. We should either update those or clean those up as well.

hello @weshaggard I removed those files. Please help to review again. thanks

@chunyu3
There are some additional files can be deleted too. You might refer to this PR for the details.
https://github.com/Azure/azure-sdk-for-net/pull/27179/

@chunyu3 There are some additional files can be deleted too. You might refer to this PR for the details. #27179

There will be follow-up PR for this.


Vim9: cannot use :function {'123'} to get body of lambda expression

Describe the bug
In Vim9 script, we cannot get the body of a lambda expression.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9
    timer_start(1'000, () => 0)
    exe timer_info()[0].callback
        ->string()
        ->substitute('(', '{', '')
        ->substitute(')', '}', '')
        ->substitute('function\zs', ' ', '')
EOF
)

E129 is raised:
E129: Function name required

Expected behavior
No error is raised, because the command function {'<lambda123>'} is valid and documented at the end of :h lambda.
https://github.com/vim/vim/blob/ebbf11c1198b7aec8a1a55f7231ecb4f1a432fa0/runtime/doc/eval.txt#L648-L650
Environment

Vim version: 8.2 Included patches: 1-2306
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(363)

Additional context
The exact same code works fine in Vim script legacy:
call timer_start(1000, {-> 0})
exe timer_info()[0].callback
    \ ->string()
    \ ->substitute('(', '{', '')
    \ ->substitute(')', '}', '')
    \ ->substitute('function\zs', ' ', '')

function <lambda>1(...)
1  return 0
endfunction

This syntax is useful while debugging a lambda expression.  I rely on it in a plugin to display the output of timer_info() in a more human-readable form, and with more info (i.e. with the lambda's definition).

Regression introduced in 8.2.0601 (which is weird considering that the commit message is about something completely different...).

This uses the {} notation, which is not supported in Vim9 script.
The :disassemble command understands the 9 name, we can make :function do the same.

This uses the {} notation, which is not supported in Vim9 script.
The :disassemble command understands the 9 name, we can make :function do the same.


[Enhancement] Set catalog is modified to authentication privilege usage and add compatible code

Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/persist/gson/GsonUtils.java
2
2
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 27 / 28 (96.43%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/privilege/DefaultAuthorizationProvider.java
26
27
96.30%
[264]

:large_blue_circle:
com/starrocks/sql/analyzer/Authorizer.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 27 / 28 (96.43%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/privilege/DefaultAuthorizationProvider.java
26
27
96.30%
[264]

:large_blue_circle:
com/starrocks/sql/analyzer/Authorizer.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 27 / 28 (96.43%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/privilege/DefaultAuthorizationProvider.java
26
27
96.30%
[264]

:large_blue_circle:
com/starrocks/sql/analyzer/Authorizer.java
1
1
100.00%
[]

@Mergifyio backport branch-3.1


Fix logo : html-loader img

What kind of change does this PR introduce?
I fixed the broken html-loader logo image.

Did you add tests for your changes?
I looked at the path of the image before modifying it, but this path does not currently exist.
So I revised it as follows.
Before Change:
After Change:

Does this PR introduce a breaking change?
Nope

What needs to be documented once your changes are merged?
Nope

@alexander-akait This is fixed in the main branch, we can close.


Device (dlq) not showing in Accesories, but detected in log and works in Tuya IoT Platform

Describe the bug
I own only one device in my Tuya account, a breaker, that shows up correctly in the Tuya IoT Platform development project, I can go to the “Debug” tab there and I'm able to reach the device and send commands to it from the Tuya IoT Platform and they work perfectly.
In Homebridge, with this plug-in, I see it detected during the startup log. It discovers its name, attributes, commands, but doesn't show the device in the “Accesories” tab
Expected behavior
I expect the device to show up in Accesories as a switch, in order to be able to turn it on/off, the same way it works fine from the debug tab in Tuya IoT Platform
Screenshots
It works great form the Debug tab in the Tuya IoT Platform. It show these values as available and it would be expected to get the “switch” value in accesories / HomeKit to be able to turn on/off the device; the same way it works from the Debug tab there

Device info
{
"active_time":1642750341,
"biz_type":0,
"category":"dlq",
"create_time":1642750341,
"icon":"smart/icon/bay1591839287906taVN/073f2e2ff5f3c3c3b62c096c74145863.png",
"id":"”,
"ip":"",
"lat":"",
"local_key":"",
"lon":"",
"model":"",
"name":"Breaker ",
"online":true,
"owner_id":"",
"product_id":"",
"product_name":"电源保护器",
"status":[
{
"code":"total_forward_energy",
"value":0
},
{
"code":"phase_a",
"value":"CKwAAAAAAAAAAA=="
},
{
"code":"phase_b",
"value":"AAAAAAAAAAAAAA=="
},
{
"code":"phase_c",
"value":"AAAAAAAAAAAAAA=="
},
{
"code":"fault",
"value":0
},
{
"code":"switch_prepayment",
"value":false
},
{
"code":"energy_reset",
"value":"empty"
},
{
"code":"balance_energy",
"value":0
},
{
"code":"charge_energy",
"value":0
},
{
"code":"switch",
"value":false
},
{
"code":"breaker_number",
"value":""
}
],
"sub":false,
"time_zone":"",
"uid":"",
"update_time":1642750346,
"uuid":""
}
Device functions
{
"code":"switch_prepayment",
"desc":"switch prepayment",
"name":"switch prepayment",
"type":"Boolean",
"values":"{}"
},
{
"code":"energy_reset",
"desc":"energy reset",
"name":"energy reset",
"type":"Enum",
"values":"{"range":["empty"]}"
},
{
"code":"charge_energy",
"desc":"charge energy",
"name":"charge energy",
"type":"Integer",
"values":"{"unit":"kW·h","min":0,"max":999999,"scale":2,"step":1}"
},
{
"code":"switch",
"desc":"switch",
"name":"switch",
"type":"Boolean",
"values":"{}"
}

Hello,
I have exactly the same issue. How can it be fixed?
I see the clkg in the IoT page, in the Tuya app and it works both. It also shows up in the log in Hoobs but doesn't shows up in the accessories page.
Any help would be much appreciated.
Thanks!
Vasco

The awesome talrhv added these devices in his fork! Could you please update this main one to support those too?
Thanks.

Thank you for your feedback, we will solve this issue soon

Any updates?

Hello.
I, too, have the same issue. Although it is with a ceiling fan with LED light (which I assume are supported devices)
I see the device in the Homebridge logs and every command I send (either by the physical remote, Tuya Smart app or Tuya web IoT Device Debugging) is logged correctly.
The device is not shown in Homebridge accessories panel. I'm wondering/hoping if this will be shown as two devices (one for the fan and one for the LED light)
I have also created a new instance of Homebridge to bridge to Home app and issue remains. (I did this because if I followed the YouTube installation video it says to pair Homebridge to Home and I get a message saying already paired and need to reset which I didn't want to do because I would lose all current Homebridge accessories. And I wondered if a clean install would resolve issue.)
I assume the Tuya plug-in is supposed to populate the accessories and there is no need to create accessories in the config file. Additionally, using the Homebridge UI settings dialog box for plugin the endpoint parameter was not shown, so I entered that manually in the config file.
I've been struggling with this plug in for many months. I'm hesitant to purchase other Tuya based products until I can resolve this one.
Thanks, Greg.

Hi @gregconnors,
From what I have gathered these past few months here, if your device shows up in the boot-up log in Homebridge, they could “easily” add it to a some kind of whitelist that they have in the code (I don't know what it is, exactly), where they add the device and it shows in accesories; as most of the work is already done.
But sadly, I don't think they are supporting this plug-in very much (if at all), as I see a lot of these issues opened, with the automatic response of “This will be fixed soon"

Thanks for the response @DanAykroyd256. Sadly, I agree with you regarding ongoing development/support.
Maybe Matter will make a difference, although I don't hold out hope that most things like ceiling fans will get firmware upgrades (they'll want to get us to pay for new models).

after more than a year and a half the problem is still present. is there any possibility of resolution?


[docs] SSR guide

Describe the solution you'd like
Include multiple methods like:

react-lightyear
simply using the suspense fallback mechanism and not loading any data
integration with things like after.js (using something similar to https://resthooks.io/docs/guides/no-suspense)

Ideally example code will have been tested.

Will come soon but don't want lingering issues.

Hey, I'm trying to integrate rest-hooks with a Next.js app and obviously it crashes on:

Error: ReactDOMServer does not yet support Suspense.

I guess I have to use the useStatefulResource() from the link above?
Perhaps I could assist with writing the SSR docs?

There's a few ways to do this, and we'd be happy to accept contributions for the way that works best for you.
With next.js it expects pass getInitialProps() in. This can work, by reading those props if they exist, else fallback to the value from useStatefulResource(). This is probably the easiest way to integrate. However, it does have a downside (tho that's true of anything using getInitialProps()) - in that it doesn't prime the cache, so navigating back and forth it will have to fetch still, which brings us to the second way.
<CacheProvider /> takes initialState, which means you if you serialize the cache from SSR, then on client you can deserialize and load it via initialState. https://resthooks.io/docs/next/api/CacheProvider This requires a bit more orchestration, but has the advantage of priming the cache. In this case, you can just ignore the initialProps stuff - but it's still important to fetch in there. To achieve this you will likely need to use a redux backend so the store can be external.
Lastly a note about suspense. If you use the experimental react release, it will actually work with suspense, and simply display the fallback at all times when doing SSR. This allows you to useResource() instead of useStatefulResource() - however it does mean you'll need to do a two pass render. This is the best future proofing methodology.

Thanks! I actually don't need fetching in ssr (not yet at least), so useStatefulResource or the 2nd way you've mentioned (experimental React) should be fine.
I'm also struggling to integrate with a json-api api (just a simple one actually, eg:
{
  data: {  <-- here could be either an object or an array of objects
    id: '123',
    attributes: { fieldA, fieldB, fiedC },
  }
}

I tried to manually set the schema but didn't succeed - K don't want to spam this issue so perhaps I should open a new one?

https://resthooks.io/docs/next/api/Union should model two different possible data types showing up somewhere


Undo / redo stack should be saved between reloads.

I'm trying to develop a plugin for Atom, but every time I reload the editor to see the new code changes, I lose the undo/redo stack.
Would be nice to be able to save it per 'session' and only clear it when the tab or editor is closed.
I understand that reloading the editor using ctrl+alt+cmd+L is effectively closing the tabs and it could get tricky to detect if the user manually closed a tab, or chose to close all tabs, but I think it's doable.
Also, I had to disable the "Whitespace" package: https://discuss.atom.io/t/save-redo-save-redo-then-redo-did-not-work-bug/10501
In my opinion, the undo/redo stack should not be affected by packages.

Thanks for the suggestion! This looks like a duplicate of https://github.com/atom/atom/issues/148 – please subscribe there for updates.


Use implementation-only imports

This makes it so compiling a manifest won't require the presence of the Foundation .swiftmodule

@swift-ci please smoke test

This makes sense to me, and is good cleanup.  It wouldn't affect any existing manifests, right, since they would have had to independently import Foundation in order to have access to the symbols?  Since PackageDescription wasn't actually reexporting anything.  Do I understand that right?

It wouldn't affect any existing manifests, right, since they would have had to independently import Foundation in order to have access to the symbols? Since PackageDescription wasn't actually reexporting anything. Do I understand that right?

Yep, that's right.

This does impact existing manifests, as apparently some Foundation symbols are exported. For example, the swift-standard-library-preview package manifest uses StringProtocol.capitalized, which is added by Foundation, so this change meant the manifest could no longer be compiled. See: https://github.com/apple/swift-standard-library-preview/pull/4


Add removebg extension

Description
An extension  that takes an instant screenshot, removes the background using remove.bg API, and then copies it to the clipboard.
A simple tool to automate the workflow of instantly capturing and pasting an image without a background.

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

We already have this in the store, sounds like it could be an enhancement for that one?


KeyError on Initialize phase of robot script.

GenieRobot currently requires a device or alias with the name uut


Creating New Application Fails

I attempted to create a new application using the latest revel command:
revel new -a $GOPATH/src/$VENDORPATH/newapp -s ""

The documentation is incorrect, -s, --skeleton is required although I was allowed to pass ""
I get an error because a skeleton cannot be found:

CRIT  09:01:40    new.go:248: Abort: could not clone the  Skeleton  source code:
Cloning into '/var/folders/w3/gpkz60lj19n53lyndxmz62ndhdytbw/T/revel/skeleton'...
fatal: read error: Operation timed out
git://github.com/revel/skeletons:basic/bootstrap4
This on on mac osx using go 1.11.1 (which I don't believe to be the problem).
As a workaround can I just copy a sample application and use that as the basis for a new application?

There was an issue with revel/cmd where the skeleton repository used was retrieved via ssh - which would fail if behind a proxy or firewall. The next milestone release changed the retrevial to use https.


Update v1alpha2 HNCConfig modes to camel case

Update v1alpha2 HNCConfig sync modes to camel case, e.g. 'propagate' to
'Propagate'.
In addition, add e2e test case to make sure v1alpha2 HNCConfig
reconciler is working as expected. Verify v1alpha1 'propagate' is not
treated as unknown and converted to v1alpha2 'Ignore'. Verify object
propagation is still working after conversion. Verify all modes are
converted correctly.
Update 2 HNC e2e test cases in demo_test to use the new camel-case
modes.
Tested by 'make test-conversion'. When the old cached image was used,
v1alpha1 'propagate' was converted to v1alpha2 'Ignore'. After the image
was re-pulled, it was converted to v1alpha2 'Propagate' correctly.
Also passed the focused tests on the 2 HNC e2e test cases.
See #1025 about the cached image issue.
Part of #868

/assign @adrianludwin
/assign @rjbez17
/cc @GinnyJI , @adrianchung

/hold
for now for https://github.com/kubernetes-sigs/multi-tenancy/issues/1025#issuecomment-675738933 and the failed test.

/hold cancel
/assign @adrianludwin
/assign @rjbez17
Cancel the hold because the test and #1025 are done. PTAL.

/lgtm
/approve
/hold
hold for @adrianludwin

/hold cancel


KAFKA-16052: create a real dummy replicaManager instance to save memory

For more detail, please check KAFKA-16052.
The mockito will keep the invocation history in the test suite and cause the huge heap usage. Since the mock replicaManager is only used to bypass the replicaManager constructor without verifying/mocking anything, we can create a real dummy replicaManager to avoid the mockito invocation history in memory.
Kudo to @divijvaidya 's great find, and @jolshan 's investigation!
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hey @showuon
There are multiple other things that need to be corrected with this test, such as closing metrics, ensuring that producePurgatory is being closed etc. Also, the change you proposed does not reset the mock of LogManager after every test. Hence, I have taken the liberty of creating a commit with a bunch of more changes: https://github.com/divijvaidya/kafka/commit/d4228a339035d83225408e5651e5cacbf604f0e8
Please feel free to implement the changes in this PR or cherry-pick the commit in this PR. Whatever is convenient for you.

I had also started an attempt of this and was trying to get the produce purgatory to be hooked up as expected.
I also had some issues with passing nulls into the optional arguments. (But maybe I was doing something wrong)
I'm happy to review this or Divij's commits. Let's agree to focus on one PR though :)

in this PR

@divijvaidya , Good catch! We have to close replicaManager now since we're creating a real one. Let's use your commit for the fix. Please open a PR with this commit.


Use SSL in template URL scheme

Throws this error when not using SSL: redirection forbidden: http://emberjs.com/edge_template.rb -> https://emberjs.com/edge_template.rb (RuntimeError)

Awesome thanks, @faucct !
📝  Now emberjs.com is served via https. Ref: https://github.com/emberjs/website/pull/2828


Fix build warnings

After these changes, the Debug and Release builds are clean except for CS1591

@peleyal @jtattermusch kindly take a look?

Thanks for doing that Matt!

In addition I see that we have a lot of "...The variable `xxx' is assigned but its value is never" in our tests. Do you want to handle those ones as well, or do you prefer to open a new issue?

@peleyal Thanks for the review! Ready for another look.
I didn't see the unassigned variable warnings. Maybe because I'm building with an older toolchain? Anyway, I'm content with these changes for now. We'll come to the rest in due time. :)

I took a quick look and the changes look good to me. Thanks for doing that!
It would be great if we could come up with some way how to prevent the need for all those binding redirects.

I left some comments regarding the code that we delete (I think I prefer to have a warning than to have less tests), but I'm open to it, if both of you agree on that.
Besides that, looks GOOD :+1:

jtattermusch@, https://github.com/google/google-api-dotnet-client/issues/555 is still open, so I think we will get to it soonish :)

@peleyal ready for one last look

LGTM. Build is still in progress. WEIRD, since you commented here 3 hours ago. Any suggestion? I prefer to NOT merge it until we see the continuous-integration/travis-ci/pr is OK