Consistent rules naming

🔍 Search Terms
compilerOptions, allowUnreachableCode, allowUnusedLabels, noStrictGenericChecks
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
The naming convention is not consistent across rules in compiler options, therefore obstructing intuitive and straightforward code styling.
One bulk of compiler rules goes with "allow" prefix, another goes with "no" and there is third group using "suppress".
I suggest unifying those rules. It will reduce the need of consulting the documentation and will provide more clarity to the codebase.
Rules with old naming could be marked as deprecated.
📃 Motivating Example
This
{
  "compilerOptions": {
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,

    "noImplicitUseStrict": false,
    "noStrictGenericChecks": false,
  }
}

versus this
{
  "compilerOptions": {
    "noUnreachableCode": false,
    "noUnusedLabels": false,

    "noImplicitUseStrict": false,
    "noStrictGenericChecks": false,
  }
}

💻 Use Cases

What do you want to use this for?
For easier learning of details of ts config and easier setup of projects
What shortcomings exist with current approaches?
No shortcomings, the need of consulting the docs will be reduced to minimum
What workarounds are you using in the meantime?
Remembering the options and consulting the docs.

Adding even more options (or renaming them) will only bring more confusion, and you still need to consult the documentation to understand what the options do.
I've seen similar issues already, and they're always rejected. There gotta be a really good reason for such a change, and IMO you haven't presented any.

therefore obstructing intuitive and straightforward code styling.

It's not code, it's a configuration file.

I don't really see what the upside is here. There's already a completion list here; if you type "returns" you will see that it's noImplicitReturns not allowImplicitReturns.
Conversely, if two options that control the same thing exist:

You have to figure out what it means if both exist
You have to figure out what it means if both exist in different config files
Basic string search no longer works
Someone will log an issue saying you have to remove one of them "for consistency"

Then everyone argues about which one is correct

Someone else logs an issue saying that all options should be phrased in a way that the default value of false is correctly interpeted "for consistency"
Someone else logs an issue saying that they should not be renamed since the options in 5.5 were obviously good enough, and having two names is bad "for consistency"

Let's just remove all the options and have tsc behave the same for everyone and be completely nonconfigurable... "for consistency" 🚎

@fatcerberus let's just be more friendly eh?

@RyanCavanaugh it's just I was studying ts config docs and it appeared to me counterintuitive to have such namings for rules in the first place. You made good point about this as well.

Someone else logs an issue saying that all options should be phrased in a way that the default value of false is correctly interpeted "for consistency"
Those are small things and are easily looked up in docs, but throughout time they gather like snowball and in the end you just have to consult docs for every such details and it's not a good developer experience IMHO.

Or maybe there is some specific reason why those rules were named like this? Or this is just a simple human error?

let's just be more friendly eh?

@medreres That's the reason for the 🚎 emoji - trolleybus for playful trolling (and in this case I was trolling Ryan, not you).  Don't take it too seriously

Those are small things and are easily looked up in docs, but throughout time they gather like snowball and in the end you just have to consult docs for every such details and it's not a good developer experience IMHO.

I would argue if you care about the options in a tsconfig at all you should be consulting the docs anyway, regardless of what they're named.  The name alone can't convey all the effects a given option has, particularly in combination with other options, so what things are called is the least of your worries.

Or maybe there is some specific reason why those rules were named like this? Or this is just a simple human error?

More like "organic growth over time"; individual options are named pragmatically as they're introduced, naming preferences change, etc. etc.  There's no specific reason for the haphazard naming beyond "that's just the way it worked out".

Or maybe there is some specific reason why those rules were named like this?

They're named such that their default values are all false (or at least were at the time when they were named, though I don't think any have changed yet)
For example, if the default behavior is that foo is not allowed, then the flag is called allowFoo
If the default behavior is that bar is allowed, then the flag is called noBar
This keeps you from having to look up in the docs what the default value is - by looking at the name, you can tell.

Note that this scheme is way better in terms of "saving you a trip to the docs" -- the completion list of options itself encodes their default values via the naming convention.
I think it'd be a lot worse if you were looking at a list of allowUmdGlobalAccess, allowPropertyAccessFromIndexSignature, allowImplicitOverride, allowUncheckedIndexedAccess, saying to yourself "Want that, don't want that, want that, don't want that" and having to cross-reference with the docs to see if you need to explicitly toggle them or not.

This keeps you from having to look up in the docs what the default value is - by looking at the name, you can tell.

Interesting thing, good to know, thanks :)
Didn't get the second point about self encoding naming though

The self-encoding naming point is just a restatement of the bit you quoted.


[Feature][import and export] Add code field to support project import and export

Support project import / export function plan

current scheduling does not support migration. For example, migration from development environment to production system.

Therefore, you need to add a field code to support data import and export, and use code to maintain the logical relationship between data
Project management:
import / export [project, process definition, file management, UDF resource, data source] as required
process definition: import and export
Resource Center :
[file management, UDF resources, UDF functions]: import and export
Datasource Center :
[datasource management ]: import and export

project download:

process definition

resources:

datasource:

2.process definition, support to create directory
process definition

db table change

t_ds_project  [Add field code ]
t_ds_process_definition [ Add field code ,parent_code,is_directory, update  project_id -> project_code , resource_ids -> resource_codes ]
t_ds_datasource               [Add field code]
t_ds_udfs                   [add field code, update field resource_id -> resource_code ]

It is a good feature.

Can you send a mail to dev mail list and we need to discuss this feature on the mailing list .

big feature

+1

+1


[SPARK-19220][UI] Make redirection to HTTPS apply to all URIs. (branch-2.0)

The redirect handler was installed only for the root of the server;
any other context ended up being served directly through the HTTP
port. Since every sub page (e.g. application UIs in the history
server) is a separate servlet context, this meant that everything
but the root was accessible via HTTP still.
The change adds separate names to each connector, and binds contexts
to specific connectors so that content is only served through the
HTTPS connector when it's enabled. In that case, the only thing that
binds to the HTTP connector is the redirect handler.
Tested with new unit tests and by checking a live history server.
(cherry picked from commit 59502bbcf6e64e5b5e3dda080441054afaf58c53)

Test build #72060 has started for PR 16717 at commit ddd7727.

Test build #72060 has finished for PR 16717 at commit ddd7727.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72060/
Test PASSed.

Merged build finished. Test PASSed.

Merging to 2.0.


Cache is not cleared properly

Warning:  I will close the bug issue without the minimal init.vim and the reproduce ways.
Problems summary
I commented out the plugin in deinlazy.toml and I found that it will still load in the .cache folder of the dein I set. Like ultisnipes plugin，I commented on it, but it still exists in .cache and is loaded，I tried to clean up cache_nvim. It doesn’t seem to have any effect,
The same I commented on the neoformat plugin. But when I edit the file, it still prompts me that neoformat is working.
Expected
The commented plugin restarts neovim will not be loaded
Environment Information (Required!)

dein.vim version(SHA1):the latest

OS: mac os 10.13.6

Vim/neovim version: neovim 0.4-dev

Provide a minimal .vimrc with less than 50 lines (Required!)

Comment plugin,
Restart neovim

Screen shot (if possible)

Upload the log messages by :redir and :message (if errored)

It is the feature.
You need to specify toml's path in dein#begin() arguments.
You should read the documentation.
							*dein#begin()*
dein#begin({base-path}, [{vimrcs}])
		Initialize dein.vim and start plugins configuration
		block.
		{base-path} is where your downloaded plugins will be placed.
		For example, "Shougo/dein.vim" will be downloaded in
		"{base-path}/repos/github.com/Shougo/dein.vim" directory.
		{vimrcs} is a list of compared .vimrc and/or other
		configuration files. The default is |$MYVIMRC|.
		The typical {base-path} is "~/.cache/dein" or
		"~/.local/share/dein".

I tried to clean up cache_nvim. It doesn’t seem to have any effect,

call dein#recache_runtimepath() for manual clean.

It is the feature.
You need to specify toml's path in dein#begin() arguments.
You should read the documentation.
							*dein#begin()*
dein#begin({base-path}, [{vimrcs}])
		Initialize dein.vim and start plugins configuration
		block.
		{base-path} is where your downloaded plugins will be placed.
		For example, "Shougo/dein.vim" will be downloaded in
		"{base-path}/repos/github.com/Shougo/dein.vim" directory.
		{vimrcs} is a list of compared .vimrc and/or other
		configuration files. The default is |$MYVIMRC|.
		The typical {base-path} is "~/.cache/dein" or
		"~/.local/share/dein".

I use .cache/dein to store the plugin. I  install dein in .config/nvim/repos,I  have this in my .config/nvim/rc/init.vim
let $CONFIG = expand('~/.config')

if !isdirectory(expand($CONFIG))
  call mkdir(expand($CONFIG), 'p')
endif

" Load dein.
let s:dein_dir = finddir('dein.vim', '.;')
if s:dein_dir != '' || &runtimepath !~ '/dein.vim'
  if s:dein_dir == '' && &runtimepath !~ '/dein.vim'
    let s:dein_dir = expand('$CONFIG/nvim')
          \. '/repos/github.com/Shougo/dein.vim'
    if !isdirectory(s:dein_dir)
      execute '!git clone https://github.com/Shougo/dein.vim' s:dein_dir
    endif
  endif
  execute 'set runtimepath^=' . substitute(
        \ fnamemodify(s:dein_dir, ':p') , '/$', '', '')
endif

I tried to clean up cache_nvim. It doesn’t seem to have any effect,

call dein#recache_runtimepath() for manual clean.

maybe  i need this.

You need to specify toml files in {vimrcs} argument.

These code comes from your configuration and I don't see where thesfileis defined. How do I set up toml in {vimrcs} dein.rc.vim

let s:toml_dir = expand($CONFIG.'/nvim/rc/dein')
let s:toml =s:toml_dir.'/dein.toml'
let s:lazy_toml = s:toml_dir.'/deinlazy.toml'
call dein#begin(s:path, [expand('<sfile>'), s:toml, s:lazy_toml])

These code comes from your configuration and I don't see where thesfileis defined.

:help <sfile>

thanks a lot, i think i should learn vimscript


[BUG] npm run crm-sync:sf:b2cinstance:setup fails returns a 400 bad request error

Describe the bug
When running the CLI command: npm run crm-sync:sf:b2cinstance:setup I get a request failed 400 error at the line:
-- Seeding B2C CustomerLists and Sites for this B2C Instance in the Salesforce Org
Error: Request failed with status code 400
To Reproduce
Steps to reproduce the behavior:

Follow steps on read me up until the command npm run crm-sync:sf:b2cinstance:setup
Run npm run crm-sync:sf:b2cinstance:setup
Error presents itself

Expected behavior
Running command should create the B2C Instance record successfully.
Screenshots

Your local environment details:

Node version (node -v<EMAIL_ADDRESS>NPM version (npm -v<EMAIL_ADDRESS>SFDX version (sfdx -v) sfdx-cli/7.204.6 win32-x64 node-v18.15.0

Your remote environment details:

Salesforce B2C Commerce version: [e.g. 21.10]
Salesforce Core version: 58.0

The relevant flow: "B2C Commerce: B2C Instance: CustomerLists and Sites: Setup" was not activated and was the cause of this issue.


[c++/r/python] Update to core 2.15.2, TileDB-Py 0.21.3, TileDB-R 0.19.1

Issue and/or context: As these packages are now released.
Changes:
Notes for Reviewer: See also https://github.com/TileDB-Inc/tiledbsoma-feedstock/pull/17

In the R CI fail at
https://github.com/single-cell-data/TileDB-SOMA/actions/runs/4821095098/jobs/8586704033?pr=1303
I do not understand

https://github.com/single-cell-data/TileDB-SOMA/actions/runs/4821095098/jobs/8586704033?pr=1303

as I thought we had TileDB-R 0.19.1 available on CRAN
https://cran.r-project.org/web/packages/tiledb/index.html

I notice that TileDB-Py 0.21.3 has not yet arrived in Anaconda:
https://anaconda.org/tiledb/tiledb-py/labels

Package required and available but unsuitable version: ‘tiledb’

So sorry about that.  I had hoped an installation yesterday would be enough to have tiledb covered today by PPM which goes into r2u for binaries but no so such luck.  We should therefore probably add the line
 Rscript -e "install.packages('tiledb', repos = c('https://eddelbuettel.r-universe.dev', 'https://cloud.r-project.org'))"

as a shell command in the yaml.  And maybe we even want to keep it to always test with upcoming tiledb.

Codecov Report
Patch and project coverage have no change.

Comparison is base (e29ebe3) 91.01% compared to head (9dbd975) 91.01%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1303   +/-   ##
=======================================
  Coverage   91.01%   91.01%
=======================================
  Files          30       30
  Lines        2416     2416
=======================================
  Hits         2199     2199
  Misses        217      217

Flag
Coverage Δ

python
91.01% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix subtract for small durations

Smaller durations (less than a second) where added instead of subtracted

Coverage remained the same at 64.798% when pulling b6876f03f4ffed975f9c9a3804e08005ce284be3 on gabrielelana:subtract-milliseconds into 6c460649b93b60c335fa342e99424722cfb1e7f2 on bitwalker:master.

Thanks!


Makefile.PL Fails for 246 when it works for 244

In Gentoo, the package dev-perl/XML-Parser-2.460.0 does not install XML::Parser.  I've opened a bug regarding the false indication that XML::Parser installs when, in fact, it does not.  The issue https://bugs.gentoo.org/827966
I downloaded and staged XML::Parser-2.44 and 2.46 under /usr/local/src.  I then proceeded to run:
  perl Makefile.PL

in each staging area.  The result is that 2.44 creates files when 2.46 does not:
Writing MYMETA.yml and MYMETA.json
Generating a Unix-style Makefile
Writing Makefile for XML::Parser
Writing MYMETA.yml and MYMETA.json

Both have the warning message.  Here are my attempts:
janus /usr/local/src/XML-Parser-2.46 # perl Makefile.PL EXPATLIBPATH=/usr/lib64 EXPATINCPATH=/usr/include

Expat must be installed prior to building XML::Parser and I can't find
it in the standard library directories. Install 'expat-devel' (or
'libexpat1-dev') package with your OS package manager. See 'README'.

Or you can download expat from:

http://sourceforge.net/projects/expat/

If expat is installed, but in a non-standard directory, then use the
following options to Makefile.PL:

    EXPATLIBPATH=...  To set the directory in which to find libexpat

    EXPATINCPATH=...  To set the directory in which to find expat.h

For example:

    perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include

Note that if you build against a shareable library in a non-standard location
you may (on some platforms) also have to set your LD_LIBRARY_PATH environment
variable at run time for perl to find the library.

janus /usr/local/src/XML-Parser-2.46 # ls -la /usr/lib64/libexpat*
lrwxrwxrwx 1 root root     17 Nov 29 19:46 /usr/lib64/libexpat.so -> libexpat.so.1.8.1
lrwxrwxrwx 1 root root     17 Nov 29 19:46 /usr/lib64/libexpat.so.1 -> libexpat.so.1.8.1
-rwxr-xr-x 1 root root 194536 Nov 29 19:46 /usr/lib64/libexpat.so.1.8.1
lrwxrwxrwx 1 root root     18 Nov 29 19:46 /usr/lib64/libexpatw.so -> libexpatw.so.1.8.1
lrwxrwxrwx 1 root root     18 Nov 29 19:46 /usr/lib64/libexpatw.so.1 -> libexpatw.so.1.8.1
-rwxr-xr-x 1 root root 198632 Nov 29 19:46 /usr/lib64/libexpatw.so.1.8.1
janus /usr/local/src/XML-Parser-2.46 # ls -la /usr/include/exp*
-rw-r--r-- 1 root root 42636 Nov 29 19:46 /usr/include/expat.h
-rw-r--r-- 1 root root  3830 Nov 29 19:46 /usr/include/expat_config.h
-rw-r--r-- 1 root root  6029 Nov 29 19:46 /usr/include/expat_external.h
janus /usr/local/src/XML-Parser-2.46 #

in 244, it works:
janus /usr/local/src/XML-Parser-2.44 #   perl Makefile.PL EXPATLIBPATH=/usr/lib64 EXPATINCPATH=/usr/include

Expat must be installed prior to building XML::Parser and I can't find
it in the standard library directories. Install 'expat-devel' (or
'libexpat1-dev') package with your OS package manager. See 'README'.

Or you can download expat from:

http://sourceforge.net/projects/expat/

If expat is installed, but in a non-standard directory, then use the
following options to Makefile.PL:

    EXPATLIBPATH=...  To set the directory in which to find libexpat

    EXPATINCPATH=...  To set the directory in which to find expat.h

For example:

    perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include

Note that if you build against a shareable library in a non-standard location
you may (on some platforms) also have to set your LD_LIBRARY_PATH environment
variable at run time for perl to find the library.

Writing MYMETA.yml and MYMETA.json
Generating a Unix-style Makefile
Writing Makefile for XML::Parser
Writing MYMETA.yml and MYMETA.json
janus /usr/local/src/XML-Parser-2.44 #

It looks like the point of failure is occurring at the testing stage, lines 32 - 39, in Makefile.PL:
unless (
    check_lib(    # fill in what you prompted the user for here
	lib     => [qw(expat)],
	header  => ['expat.h'],
	incgentoopath => $expat_incpath,
	( $expat_libpath ? ( libpath => $expat_libpath ) : () ),
    )
)

I have these areas waiting for any modified Makefile.PL scripts you would like me to try out.  My guess is check_lib is failing.

I think I found the difference between 244 and 246.
In 244 and 246 on my janus VM, both return "0" in the call
However, in 244, the "exit" is rem'd out with a hashtag, "#":
     #exit;
 }

so the 244 script does not exit as perhaps it should have?  In 246, there is an an exit command that is duly executed.
# exiting before Makefile generation silences CPANTesters reports
# when expat is not available.
exit 0;

The above explains the inconsistent behavior of version 244 and 246 on the same machine.  But Gentoo's ebuild doesn't seem to read the exit correctly and proceeds with what appears to be a successful installation when there is nothing to install.
Now, I'll add a wrinkle.  On another Gentoo instance, taurus, the call to subroutine check_lib() returns 1 whereas on janus it returns 0.  What is odd is that I have the same expat files on taurus and janus and the same package Devel::CheckLibs.
I'll have to scratch around some more and will update with my findings.

I think there is another issue apart from the failure of the test subroutine check_lib().  That is the value provided by the call to exit.  In 266, the exit returns "0" to signify a failure.  In Perl, returns of "0" can be a signal of: FAILED, and a return of "1" can be: SUCCESS.  However, in bash scripting, the opposite is true -- a call to a script when returns "0" means the sub component was successful, and you flag an error by exiting with "1".  On the topic of exit codes for bash, see: https://codefather.tech/blog/exit-bash-script/
So, at this point I'm concluding that version 244 was broken because the failure of check_lib() should have had an "exit 1", but instead the exit line was rem'd out and processing proceeded.  If you system had the expat libraries, then no harm, no foul and in Gentoo the installation of perl-lang/XML-Parser would succeed because in the later steps of Makefile.PL files for compilation where created and expat was found.  So I think this package's Makefile.pl should have at line 69:
 exit 1;

Then, investigation needs to determine why the subroutine check_lib() fails when it should not.  When check_lib() successfully finds the expat library and header file, then line 69 will not be called and the build will continue as it should.

Of course, my suggestion that Makefile.PL's line 69 have "exit 1;" comes from a perspective of a Gentoo bash script.  It may be that within Perl's realm, the Makefile.PL's return should be "exit 0", in which case the maintainter of the Gentoo package perl-lang/XML-Parser should check for a value of "1" instead of "0" to determine success.

See https://metacpan.org/pod/Devel::CheckLib#check_lib_or_exit
I created this test script which produces the desired result on my machines "janus" and "taurus":
#
#
#

use strict;
use warnings;

use Devel::CheckLib;

print "Test for library 'expat':\n";
my $rc1 = check_lib_or_exit( lib => 'expat');
print "rc1 = $rc1\n";

print "Test for header file 'expat.h':\n";
my $rc2 = check_lib_or_exit( header => "expat.h");
print "rc2 = $rc2\n";

if (0){
eval {
	print "Test with error lib 'bogus':\n";
	my $rc3 = check_lib_or_exit( lib => 'bogus');
	print "rc3 = $rc3\n";
};
print "Error from eval: $@" if defined $@;
}

if (0){
eval {
	print "Test with error 'bogus.h':\n";
	my $rc3 = check_li	#
#
#

use strict;
use warnings;

use Devel::CheckLib;

print "Test for library 'expat':\n";
my $rc1 = check_lib_or_exit( lib => 'expat');
print "rc1 = $rc1\n";

print "Test for header file 'expat.h':\n";
my $rc2 = check_lib_or_exit( header => "expat.h");
print "rc2 = $rc2\n";

if (0){
eval {
	print "Test with error lib 'bogus':\n";
	my $rc3 = check_lib_or_exit( lib => 'bogus');
	print "rc3 = $rc3\n";
};
print "Error from eval: $@" if defined $@;
}

if (0){
eval {
	print "Test with error 'bogus.h':\n";
	my $rc3 = check_lib_or_exit( header => "bogus.h");
	print "rc3 = $rc3\n";
};
print "Error from eval: $@" if defined $@;
}

print "Completed $0 at ".localtime."\n";

b_or_exit( header => "bogus.h");
print "rc3 = $rc3\n";
};
print "Error from eval: $@" if defined $@;
}
print "Completed $0 at ".localtime."\n";

If you engage either of the "if" clauses (replacing 0 with 1) then the desired result will occur: the Perl script will exit with a warning.
Perhaps using the function check_lib_or_exit() instead of check_lib() would be the approach to take?

As more people upgrade to 246, larger numbers of users are hitting this. Anything we can do to help?

This looks related to https://github.com/toddr/XML-Parser/issues/86.

I believe this has been resolved by #89


Implement mev-boost circuit breaker

Description
As per https://github.com/ethereum/builder-specs/pull/47

Looks like the specific parameters for activation aren't set in stone yet. We should implement this but it probably needs to be off by default until the parameters are settled.


Allocate action should examine all pending tasks in a job

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
Looks like after first task failed in fitting into node, following tasks would be skipped.
This make an assumption that all tasks requires exact same resources which is not accurate.
For example, TFJob parameter server and worker requires different resources.
If task.resreq is more than node.Idle resource. It will go break loop and get into
I0103 17:50:16.825450   29996 allocate.go:81] Can not find jobs for queue default.

https://github.com/kubernetes-sigs/kube-batch/blob/0be5265b4b23e09343f39ab4dce261454a8426be/pkg/scheduler/actions/allocate/allocate.go#L141-L145
https://github.com/kubernetes-sigs/kube-batch/blob/0be5265b4b23e09343f39ab4dce261454a8426be/pkg/scheduler/actions/allocate/allocate.go#L162-L167
What you expected to happen:
Go through all tasks in one job.
How to reproduce it (as minimally and precisely as possible):
Schedule a job which could result in pending with at least 2 tasks.
Here, we have 4 tasks in total and enough resources for 2 tasks. But last one get skipped.
I0103 17:50:16.825077   29996 allocate.go:61] Try to allocate resource to 1 Queues

I0103 17:50:16.825085   29996 allocate.go:78] Try to allocate resource to Jobs in Queue <default>
I0103 17:50:16.825101   29996 allocate.go:102] Try to allocate resource to 4 tasks of Job <default/qj-1>
I0103 17:50:16.825111   29996 allocate.go:109] There are <2> nodes for Job <default/qj-1>
I0103 17:50:16.825119   29996 allocate.go:120] Considering Task <default/qj-1-nd485> on node <ip-192-168-46-32.us-west-2.compute.internal>: <cpu 2000.00, memory 0.00, GPU 0.00> vs. <cpu 3690.00, memory<PHONE_NUMBER>0.00, GPU 0.00>
I0103 17:50:16.825159   29996 allocate.go:132] Binding Task <default/qj-1-nd485> to node <ip-192-168-46-32.us-west-2.compute.internal>
I0103 17:50:16.825174   29996 session.go:170] After allocated Task <default/qj-1-nd485> to Node <ip-192-168-46-32.us-west-2.compute.internal>: idle <cpu 1690.00, memory<PHONE_NUMBER>0.00, GPU 0.00>, used <cpu 2310.00, memory 146800640.00, GPU 0.00>, releasing <cpu 0.00, memory 0.00, GPU 0.00>

I0103 17:50:16.825196   29996 allocate.go:78] Try to allocate resource to Jobs in Queue <default>
I0103 17:50:16.825205   29996 allocate.go:102] Try to allocate resource to 3 tasks of Job <default/qj-1>
I0103 17:50:16.825214   29996 allocate.go:109] There are <2> nodes for Job <default/qj-1>
I0103 17:50:16.825222   29996 allocate.go:120] Considering Task <default/qj-1-8djdt> on node <ip-192-168-46-32.us-west-2.compute.internal>: <cpu 2000.00, memory 0.00, GPU 0.00> vs. <cpu 1690.00, memory<PHONE_NUMBER>0.00, GPU 0.00>
I0103 17:50:16.825264   29996 allocate.go:120] Considering Task <default/qj-1-8djdt> on node <ip-192-168-71-35.us-west-2.compute.internal>: <cpu 2000.00, memory 0.00, GPU 0.00> vs. <cpu 3890.00, memory<PHONE_NUMBER>0.00, GPU 0.00>
I0103 17:50:16.825296   29996 allocate.go:132] Binding Task <default/qj-1-8djdt> to node <ip-192-168-71-35.us-west-2.compute.internal>
I0103 17:50:16.825311   29996 session.go:170] After allocated Task <default/qj-1-8djdt> to Node <ip-192-168-71-35.us-west-2.compute.internal>: idle <cpu 1890.00, memory<PHONE_NUMBER>0.00, GPU 0.00>, used <cpu 2110.00, memory 0.00, GPU 0.00>, releasing <cpu 0.00, memory 0.00, GPU 0.00>

I0103 17:50:16.825327   29996 allocate.go:78] Try to allocate resource to Jobs in Queue <default>
I0103 17:50:16.825339   29996 allocate.go:102] Try to allocate resource to 2 tasks of Job <default/qj-1>
I0103 17:50:16.825348   29996 allocate.go:109] There are <2> nodes for Job <default/qj-1>
I0103 17:50:16.825355   29996 allocate.go:120] Considering Task <default/qj-1-rdvph> on node <ip-192-168-46-32.us-west-2.compute.internal>: <cpu 2000.00, memory 0.00, GPU 0.00> vs. <cpu 1690.00, memory<PHONE_NUMBER>0.00, GPU 0.00>
I0103 17:50:16.825398   29996 allocate.go:120] Considering Task <default/qj-1-rdvph> on node <ip-192-168-71-35.us-west-2.compute.internal>: <cpu 2000.00, memory 0.00, GPU 0.00> vs. <cpu 1890.00, memory<PHONE_NUMBER>0.00, GPU 0.00>
I0103 17:50:16.825442   29996 allocate.go:78] Try to allocate resource to Jobs in Queue <default>
**I0103 17:50:16.825450   29996 allocate.go:81] Can not find jobs for queue default.**

Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.5-eks-6bad6d", GitCommit:"6bad6d9c768dc0864dab48a11653aa53b5a47043", GitTreeState:"clean", BuildDate:"2018-12-06T23:13:14Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration: aws
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

+1 , good catch :)


Replace old mimeparse package with python-mimeparse

Note! These packages occupy the same namespace. You might need to uninstall
mimeparse and reinstall python-mimeparse.
Refs #3570

Perhaps yeah. This was on sending an email. I'm not sure when i'll be able to get back to adding a test for this. maybe someone else can take it or we can create an issue for it.

That makes more sense, yeah. I'll update here.


fix(styles): don't let sidebar crossover footer

Close: #2815

Did not work for me locally, you sure it solved it on your end?

Sure, didn't work, that's not the way to fix it. I'm confused, next commit is right thing....

@montogeek wanna give it a shot?

Thanks!


enhancement: granular control over retries

when a test is being retried the beforeEach hook runs as expected, but the before hook does not

This behavior is correct/consistent: before only runs once per suite (and the retries functionality only reruns individual tests and not whole suites). Is there a particular problem you are trying to solve by running certain code both at the start of the suite and before each retry?

my case is that I have a before hook that opens a url followed by bunch of describe blocks that test different sections of that page. most of the flakiness is typically with the page itself (loading the page on test env), so if a specific test failed it makes no sense for me to retry that test without reloading the page. Sure I could change the before to a beforeEach but that slows my test unnecesserily (by reloading the page for testing each section).

@ScottFreeCode

Hi @dalimian, sorry about the wait -- I haven't had a whole lot of time to think this one over.
I can tell you that that's a fairly unusual case in the grand scheme of things -- we are generally cautious about changing anything risky (e.g. potentially confusing or potentially breaking code relying on the old behavior), but doubly so for unusual cases. On the other hand, we want to help people resolve all the cases we can.
Off the top of my head, some kind of "onRetry" hook might be the most appropriate way to handle this kind of situation, but somebody would have to figure out how to implement it and we'd need to think a little about how much potential there is for abuse.
A clumsy alternative might be to wrap tests a retry-like function instead of using Mocha's retry:
function retryable(test) {
  return function(done) { // remove all `done` if tests should not have `done`
    for (var index = 0; index < retryCount; index += 1) {
      try {
        return test(done)
      } catch (ignore) {}
      refreshPage()
    }
    return test(done)
  }
}

it("example test", retryable(function(done) {
  ...
})

thanks @ScottFreeCode, we ended up doing something like this
  before(() => {
      loadPage();
    }
  });
  beforeEach(() => {
    if (this.ctx.currentTest._currentRetry) {
      loadPage();
    }
  });

don't really like referencing props with underscores - _currentRetry but other than that pretty clean no?

thanks @ScottFreeCode, we ended up doing something like this
  before(() => {
      loadPage();
    }
  });
  beforeEach(() => {
    if (this.ctx.currentTest._currentRetry) {
      loadPage();
    }
  });

don't really like referencing props with underscores - _currentRetry but other than that pretty clean no?

thanks @ScottFreeCode, we ended up doing something like this
  before(() => {
      loadPage();
    }
  });
  beforeEach(() => {
    if (this.ctx.currentTest._currentRetry) {
      loadPage();
    }
  });

don't really like referencing props with underscores - _currentRetry but other than that pretty clean no?

don't really like referencing props with underscores - _currentRetry but other than that pretty clean no?

Indeed!
I've chewed this over and I can think of a few approaches:

Make _currentRetry an officially public property.

Basically canonicalizes (canonizes?) your solution.
Trivial to implement.
I have a vague recollection that it's been discussed as a potential solution to other use cases, but can't recall whether there were any concerns (e.g. that some uses might be antipatterns); searching the issues list for it might bring up something interesting, when I have time for it.

Make an onRetry hook.

Usage-wise, pretty much the same except no if wrapper necessary.
Should be straightforward to implement, but not necessarily trivial.
Potentially problematic in the ways the hooks tend to be problematic -- e.g. it's one more thing where we have to ask how it interacts with nested suites.

Add a setting for whether before and after should be run on retries.

Superior usage: avoids having to call setup (and/or cleanup) code in two places.
Ideally, should be able to be set for each individual hook, in case only certain things need to be done over on retry. (If it's like most Mocha settings, it would also be possible to set a default at a suite level or even a global level via the outermost Mocha APIs such as the CLI.)
However, I'm not sure how that would be set for after hooks before they run, so it might only be possible to set it one way or the other for all after hooks in a suite.

Change nothing and make note of _currentRetry as a workaround.

Avoids officially endorsing the practice of doing things when a test is retried. (This may or may not be desirable -- as previously alluded to, I don't remember whether there have previously been concerns about this. If there haven't, then obviously this kind of caution isn't necessary.)
Still works as long as _currentRetry is in the implementation (which it probably will be since the number of retries has to be tracked somewhere).
Arguably not great inasmuch as it conflates "not officially encouraged" with "implementation detail that could be subject to change".

Not really sure where I lean on this one, as there are a lot of tradeoffs here (whether we want to officially support this case, whether we want to go for a solution that's the most weird/boilerplatey in usage but easiest to implement/maintain, whether we could find a way to tag some after hooks as applying on retry and others as not...)

Thanks alot!
my favorite is prob Add a setting for whether before and after should be run on retries. - it's simplest both as an an implementation and concept to grasp. it would also help people discover this feature easy.
downsides of Change nothing and make note of _currentRetry as a workaround. or Make _currentRetry an officially public property is feature discoverability. Also, first reaction of people seems to be "this is a bit weird"

I'm working on the same tests as @dalimian. I think one way to solve the problem is to have different types of retries: describe level and it level.
To clarify what I mean:
it retry
When an it function fails, the it is rerun. Rerunning the it causes beforeEach functions to be called. This is what I believe mocha does currently more or less.
describe retry
The describe runs through all of its tests. If there are any it function failures, the describe is rerun. Rerunning the describe causes before to be called once and every failing it to be rerun. Nested describe functions are only rerun if one of its child it functions fail.
This is what we want our retries to do.
An undesired consequence of our current solution of the conditional beforeEach, is that if there are multiple it failures then we have to reload the page for each it failure, rather than for each retry. The onRetry hook would have the same issue.

Add a setting for whether before and after should be run on retries.

This sounds better than the alternatives provided.

Hmm, the option to retry all failing tests in a describe in one go, with before and after, is very interesting. I'll have to think about whether that covers all the same use cases, or whether there's a way to combine that with any of the other ideas to cover all use cases.

I'm not really convinced this casts a wide enough net to be in core... feel free to make the case though.  I see this as being specifically useful for certain integration or functional tests, but it might be too narrow.

Hmm, the option to retry all failing tests in a describe in one go, with before and after, is very interesting. I'll have to think about whether that covers all the same use cases, or whether there's a way to combine that with any of the other ideas to cover all use cases.

This is a very useful case for managing debug-level logging in automated testing, the example being case where if we turn on our debug logging for all tests, we overflow our allowed log-length in Travis.  If we had this ability, we could run our tests at log-level INFO, but have it re-run the failing tests at log-level DEBUG, enabling us to gather the root-cause information that's normally only exposed in debug-level logs.

I'm working on the same tests as @dalimian. I think one way to solve the problem is to have different types of retries: describe level and it level.
To clarify what I mean:
it retry
When an it function fails, the it is rerun. Rerunning the it causes beforeEach functions to be called. This is what I believe mocha does currently more or less.
describe retry
The describe runs through all of its tests. If there are any it function failures, the describe is rerun. Rerunning the describe causes before to be called once and every failing it to be rerun. Nested describe functions are only rerun if one of its child it functions fail. This is what we want our retries to do.
An undesired consequence of our current solution of the conditional beforeEach, is that if there are multiple it failures then we have to reload the page for each it failure, rather than for each retry. The onRetry hook would have the same issue.

Add a setting for whether before and after should be run on retries.

This sounds better than the alternatives provided.

This is a highly useful feature on our app, is there a chance it will be implemented at any time?

Per #5027, we're not looking to significantly overhaul Mocha any time soon. Given that you can implement this in userland with wrapper functions and that less than one end user has interacted with this on average per year in the >6 years it's been open, closing as out of scope. Cheers all!
Please yell at me if you strongly believe this feature must exist in Mocha core. 🙂


Enable mouseevent to be passed through the stdin stream

Nothing fancy, this is an initial code for supporting mouse events on widget.
Eventually, I'll add a code to determine which widget is clicked based on the MouseEvent information and try to simulate the events are triggered from the widgets when the user interacts with it.

This change is

Oops, sorry. The suceedding commits are my own experiments. Don't merge it.


Not require iTunes to be open when app is running.

Whenever the app is running, iTunes has to be open. I wish that you could still close iTunes while the app is running, and then open it again when you wanted to.

Due to the way that we interact with iTunes, this is not possible.

Due to the way that we interact with iTunes, this is not possible.


Fix table reserve logic

Fixes #1692
Alternative to #1696
This ensures that the capacity actually grows in increments of grow_amount, and also ensures that Table capacity is always <= column and entity vec capacity.
Debug logs that describe the new logic (running the example in #1692)
out.txt

bors r+


[feat] 避免每次从网络上拉取资源，有必要做的脚本优化

Describe the problem
网络的不稳定性会，打包过程中由于拉取资源需访问网络导致速度很慢或被中断
Describe the solution you'd like
动态生成的build_appimage.sh中多处都是需要从网络上拉取资源，尤其是从raw.githubusercontent.com拉取镜像资源，导致中国国内用户因为国家防火墙问题无法继续。
希望提供资源的可选下载地址，并且拉取资源可选择由本地复制。
Alternatives considered
No response
Additional context
No response

In the last few days, two interesting PRs were merged: https://github.com/tauri-apps/tauri/pull/10866 and https://github.com/tauri-apps/tauri/pull/11096 - Do they solve your question/problem?
To make the bundler use local files it should be enough to just save them to the location Tauri will download them to anyway (something in ~/.cache/tauri/ i think)

你也能上github了，这个项目的主要维护者中又没有中国人，为什么不用英语提issue呢？

In the last few days, two interesting PRs were merged: #10866 and #11096 - Do they solve your question/problem?

These two PRs do not solve his problem. He is encountering an issue with a shell script located at https://github.com/tauri-apps/tauri/blob/dev/crates/tauri-bundler/src/bundle/linux/appimage/appimage. The problem might be due to network issues that prevent the file from being downloaded from GitHub. A new PR needs to be created to address this.


embedder_utils.get_embedding: No need to update the reference of embedding with the return value from initializers

In the current implementation of embedder_utils.get_embedding, it update the reference of embedding with the return value of initialization function. However, this is not necessary because the initialization functions in Pytorch are in-place operations. Moreover it will cause error with the customized initialization such as https://github.com/asyml/texar-pytorch/blob/master/texar/custom/initializers.py#L10.

Fixed by #48.


Can't login dashboard

I have  a  Panther X2 (868). and when i use https://ip    I can't open the webside . one of the pather X2 web view nginx.And one of other view ERR_CONNECTION_REFUSED.
Please help me to fix it. And tell me how  can i do .
THX

@sd1894999 Please summit the SN and more information in https://panther.global/. the tech support team will fix it for you. thanks


Question: changing icon color(s) or font

Is there a config parameter for changing icon colors and/or font?

I was looking at the config exampleSite/config/_default/hugo.toml, and I didn't see any fields for specifying overrides on these.

This is something I'm working on documenting better.
You can override any of the CSS custom properties in an /assets/custom.css file or whatever file you set custom_css to in params.toml.
If you want to change your whole theme's primary color in one go, set a --color-primary property to your chosen color.
Global property override:
/* Light AND dark theme override */
:root, [data-theme="dark"] {
    --color-primary: green;
}
/* Separate overrides for light and dark */
:root {
    --color-primary: green;
}
[data-theme="dark"] {
    --color-primary: green;
}

For individual elements that don't have a property, find their class in the source code or browser and override that.
Those buttons in the image, for example, have classes .btn-primary and .btn-secondary and are children of .hero-info.
.hero-info .btn-primary {
    background-color: green;
    border-color: green;
}

.hero-info .btn-secondary {
    color: red;
    border-color: green;
}

Because CSS is ubiquitous, I felt it was easier just using CSS for these types of changes rather than trying to support a million different style preferences via configs.
Something you just made me realize is that in development the custom CSS file was linked before the compiled source Sass, and therefore the cascade wasn't picking up some custom CSS changes. I just fixed that in the version I released a minute ago (v3.3.0). This only impacted custom CSS in development because in prod the custom CSS was bundled with the source CSS in the correct order.
Icons use --color-primary for their fill property (CSS color won't change SVG color unfortunately so you'll have to override the SVG layout templates if you want them to differ from your --color-primary property).
As for fonts, I didn't expose those as CSS properties yet, just the font sizes. This is because the theme uses local fonts and doesn't load them from a CDN which makes the process a little more difficult. You can however customize fonts by adding the files to <your_site>/static/fonts/<font_name>/* for example, then creating @font-face declarations for them (see themes/hugo-liftoff/assets/scss/base/_fonts.scss to see how it's done for the default font.
Single font-face declaration, in practice you'd have 1 for each font style:
@font-face {
    font-family: 'Montserrat';
    src: local('Montserrat Thin'),
      url('/fonts/Montserrat/Montserrat-Thin.ttf') format('truetype');
    font-weight: 100;
    font-style: normal;
    font-display: swap;
}

Then in your custom.css, add an override for the body font:
body {
    font: normal 125%/1.4 "Montserrat", "Helvetica Neue Light", "Helvetica Neue", "Helvetica", "Arial", sans-serif;
}

Apologies for the long-winded answer. I'm going to work on documenting this better and improving some of these customization workflows.

Okay thank you, I appreciate the detailed answer!  I agree with your thoughts on allowing user to extend colors directly via CSS.  Sounds good on changing fonts.
Feel free to close this out whenever you're ready

My pleasure; it's helpful getting feedback like this


The Flutter Slider widget shows lagging performance on Android when used as a progress bar for voice playback.

Is there an existing issue for this?

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

Steps to reproduce
After testing the playback functionality of the app on an iOS device, I proceeded to test it on an Android device. However, I noticed that the Slider is not as smooth on Android. The progress bar stutters during playback. Please take a look at the following video. I'm not sure what went wrong. Has anyone encountered a similar issue?
Expected results
The Slider performs equally smooth on both iOS and Android devices with the same code.
Actual results
The progress bar performs smoothly on the iOS platform with the same code.
Code sample
Code sample
import 'package:audioplayers/audioplayers.dart';
import 'package:flutter/material.dart';
import 'package:tk_hsk/app_theme.dart';
import 'package:tk_hsk/common/component/my_space.dart';
import 'package:tk_hsk/common/global.dart';

class CusAudioPlayer extends StatefulWidget {
  const CusAudioPlayer({Key? key, required this.path, this.showProgressBar = true, this.autoPlay = false, this.sourceType = 1, this.onPlayerComplete, this.isContinue = false}) : super(key: key);
  final String path;
  final int? sourceType;
  final bool showProgressBar;
  final bool? isContinue;
  final bool? autoPlay;
  final Function? onPlayerComplete;

  @override
  State<CusAudioPlayer> createState() => _CusAudioPlayerState();
}

class _CusAudioPlayerState extends State<CusAudioPlayer> {

  final AudioPlayer audioPlayer = AudioPlayer();
  Duration _duration = const Duration(milliseconds: 0);
  PlayerState _playerState = PlayerState.paused;
  Duration _position = const Duration(milliseconds: 0);

  String get _durationText => _duration.toString().split('.').first;
  String get _positionText => _position.toString().split('.').first;

  @override
  void initState() {
    audioPlayer.setPlaybackRate(global.playbackRate);
    audioPlayer.onDurationChanged.listen((Duration d) {
      // print('Max duration: $d');
      if (mounted) {
        setState(() => _duration = d);
      }

    });

    audioPlayer.onPositionChanged.listen((Duration  p) {
      // print('Current position: $p');
      if (mounted) {
        setState(() => _position = p);
      }

    });

    audioPlayer.onPlayerStateChanged.listen((s) {
      // print('Current player state: $s');
      if (mounted) {
        setState(() => _playerState = s);
      }

    });

    audioPlayer.onPlayerComplete.listen((event) {
      // onComplete();
      // print('Current player Complete');
      if (mounted) {
        setState(() {
          _position = _duration;
          // _playerState = PlayerState.paused;
        });
      }

      if(widget.isContinue!){
        play();
      }else{
        if( widget.onPlayerComplete != null){
          widget.onPlayerComplete!();
        };
      }

    });

    if(widget.autoPlay!){
      if(_playerState == PlayerState.playing){
        return;
      }
      play();
    }

    super.initState();
  }

  @override
  void didUpdateWidget(covariant CusAudioPlayer oldWidget) {
    if(widget.autoPlay!){
      if(_playerState == PlayerState.playing){
        return;
      }
      play();
    }else{
      audioPlayer.stop();
    }
    super.didUpdateWidget(oldWidget);
  }

  @override
  void dispose() {
    audioPlayer.release();
    super.dispose();
  }
  play() async {
    if(global.currAudioPlayer != null){
    if(!identical(global.currAudioPlayer, audioPlayer)){
      global.currAudioPlayer.release();
      global.currAudioPlayer = audioPlayer;
    }
    }else{
      global.currAudioPlayer = audioPlayer;
    }

    if(widget.sourceType == 1){

      await audioPlayer.play(DeviceFileSource("${global.destPath}${widget.path}"));
    }else if(widget.sourceType == 2){
      await audioPlayer.play(AssetSource(widget.path));
    }else if(widget.sourceType == 3){
      await audioPlayer.play(UrlSource(widget.path));
    }
  }
  @override
  Widget build(BuildContext context) {
    return Padding(
      padding: const EdgeInsets.only(bottom: 10),
      child: widget.showProgressBar ? Row(
        mainAxisAlignment: MainAxisAlignment.center,
        crossAxisAlignment: CrossAxisAlignment.center,
        children: [
          IconButton(
              padding: EdgeInsets.zero,
              constraints: const BoxConstraints(
                  minWidth: 40,
                  minHeight: 40
              ),
              onPressed: () async {
                if(_playerState == PlayerState.playing){
                  await audioPlayer.pause();
                }else{
                  play();
                }
              },
              icon: _playerState == PlayerState.playing ? const Icon(Icons.pause_circle_outline, color: AppTheme.bg_yellowf2, size: 45,) : const Icon(Icons.play_circle_outline, color:AppTheme.bg_yellowf2, size: 45,)
          ),
          const MySpace(horizontal: 15,),
          Expanded(
              flex: 1,
              child: Column(
                children: [
                  const MySpace(vertical: 17,),
                  SliderTheme(
                    data:  SliderThemeData(
                      thumbShape: const RoundSliderThumbShape(enabledThumbRadius: 8),
                      overlayShape: SliderComponentShape.noOverlay,
                    ),
                    child: Slider(
                      thumbColor: AppTheme.bg_yellowf2,
                      activeColor: AppTheme.bg_grayd9,
                      inactiveColor: AppTheme.bg_grayf0,
                      onChanged: (v){
                        final duration = _duration;
                        final position = v * duration.inMilliseconds;
                        // print(position.round());
                        audioPlayer.seek(Duration(milliseconds: position.round()));
                      },
                      value: (_position.inMilliseconds > 0 &&
                          _position.inMilliseconds < _duration.inMilliseconds)
                          ? _position.inMilliseconds / _duration.inMilliseconds
                          : 0.0,
                    ),
                  ),
                  Padding(
                    padding: const EdgeInsets.only(top: 2, left: 8, right: 10),
                    child:Row(
                      mainAxisAlignment: MainAxisAlignment.spaceBetween,
                      children: [
                        Text(_positionText, style: TextStyle(fontSize: 11, color: AppTheme.font_gray70),),
                        Text(_durationText, style: TextStyle(fontSize: 11, color: AppTheme.font_gray70),),
                      ],
                    ),
                  )
                ],
              )
          ),
        ],
      ) : IconButton(
          padding: EdgeInsets.all(4),
          onPressed: () async {
            if(_playerState == PlayerState.playing){
              await audioPlayer.pause();
            }else{
              play();
            }
          },
          icon: _playerState == PlayerState.playing ? const Icon(Icons.pause_circle_outline, color: AppTheme.bg_yellowf2, size: 45,) : const Icon(Icons.play_circle_outline, color:AppTheme.bg_yellowf2, size: 45,)
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]
ios
https://github.com/flutter/flutter/assets/13778798/ccbee0fe-7182-4857-bc8a-4b794fd590f8
android
https://github.com/flutter/flutter/assets/13778798/67719ace-b74c-46b6-85ca-e7913b5592d6

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]
[✓] Flutter (Channel stable, 3.3.9, on macOS 12.3.1 21E258 darwin-x64, locale zh-Hans-CN)
    • Flutter version 3.3.9 on channel stable at /Users/zhongpeng/file/env/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (7 months ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/zhongpeng/Library/Android/sdk
    • Platform android-33, build-tools 30.0.3
    • ANDROID_HOME = /Users/zhongpeng/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

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

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

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

[✓] Connected device (3 available)
    • M2011K2C (mobile) • b56a416e • android-arm64  • Android 13 (API 33)
    • macOS (desktop)   • macos    • darwin-x64     • macOS 12.3.1 21E258 darwin-x64
    • Chrome (web)      • chrome   • web-javascript • Google Chrome 114.0.5735.106

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Hi @giantss. Thanks for filing this issue. Can you try upgrading to latest flutter stable version to confirm if this issue still persist? Also, can you provide a minimal complete reproducible code sample?
Thank you

I think this is a difference in how often the audio-player is reporting its progress, rather than a problem in the slider. You can check that by logging in the onPositionChanged function. I've noticed a similar thing for video-player. But you can update it at your own frequency by using a Timer to check the position manually.

@moffatman @moffatman  Your judgment is very accurate, and I greatly appreciate your help in analyzing and pinpointing the issue.

Hi @giantss. Thanks for filing this issue. Can you try upgrading to latest flutter stable version to confirm if this issue still persist? Also, can you provide a minimal complete reproducible code sample that doesn’t include 3rd party plugins or complex production code? Thank you

I have created a simple example that demonstrates that the issue is not with the Slider control. The example runs smoothly on a physical Android device as well. I apologize for the disturbance, and I will close the issue myself.

import 'dart:async';
import 'package:flutter/material.dart';

class DemoView extends StatefulWidget {
  const DemoView({Key? key}) : super(key: key);

  @override
  State<DemoView> createState() => _DemoViewState();
}

class _DemoViewState extends State<DemoView> {

  double sliderValue = 0.0;
  late Timer _timer;
  @override
  void initState() {
    super.initState();
  }

  void startTimer() {

    const period = Duration(milliseconds: 20);
    _timer = Timer.periodic(period, (timer) {
      print(sliderValue);
      if(sliderValue >= 1.0){
        _timer.cancel();
        setState(() {
          sliderValue = 0.0;
        });
      }else{
        setState(() {
          sliderValue+=0.001;
        });

      }

    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: null,
      body: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: [
          SizedBox(
            width: MediaQuery.of(context).size.width,
            height: 50,
            child: Slider(
                thumbColor: Colors.yellow,
                activeColor: Colors.grey,
                inactiveColor: Colors.grey,
                onChanged: (v){

                },
                value: sliderValue > 1.0 ? 1.0 : sliderValue
            ),
          ),

          SizedBox(
            height: 100,
          ),
          TextButton(onPressed: (){
            startTimer();
          }, child: Text('Click to play'))
        ],
      )
    );
  }
}


WEBSITE: Announcements bar overlaps search

Announcements bar overlaps search from 768 width

Thx for feedback! We'll try to fix it asap

@azinit  .announcementBar and .DocSearch-Container have the same z-index, current version used is 2.1.0, according to https://github.com/facebook/docusaurus/pull/8163 described bug have been fixed in version 2.2.0, so if you update dependency atleast up to 2.2.0 everething gonna be all right 😊

@sldk-yuri thank you for comment! ❤


hide import spreadsheet button

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/48913
PROPOSAL: https://github.com/Expensify/App/issues/48913#issuecomment-2341527268
Tests

Precondition: Workspace is connected to QBO.

Go to Workspace Settings > Categories.
Click the three-dot menu.
Verify that the Import Spreadsheet button is not shown.

[x] Verify that no errors appear in the JS console

Offline tests

Same as above
QA Steps

Precondition: Workspace is connected to QBO.

Go to Workspace Settings > Categories.
Click the three-dot menu.
Verify that the Import Spreadsheet button is not shown.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/user-attachments/assets/3309b30c-d295-469f-978a-936aabfbac03

Android: mWeb Chrome

https://github.com/user-attachments/assets/25801066-4392-4bdc-85f6-fc91d20a47a4

iOS: Native

https://github.com/user-attachments/assets/c44d3b84-c5a9-458d-8973-1ddd853c8eb7

iOS: mWeb Safari

https://github.com/user-attachments/assets/ca1fd6b1-f8e5-4a53-9158-964ab9f31146

MacOS: Chrome / Safari

https://github.com/user-attachments/assets/f13458a8-5d39-4a91-a83f-e0c2c621d9de

MacOS: Desktop

https://github.com/user-attachments/assets/880bff7a-21ca-4043-9067-c0b559c15c36

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


Allow page_size to be requested by the user.

The UI shows only ten search results per page, yet the backend allows 50. This
creates a mismatch when paging. To resolve, allow the user to request a
specific page size (within bounds).

Coverage increased (+0.05%) to 93.359% when pulling 3fab4664266c406d68e32d11d943d85fd57823a8 on 499-page-size into 63a9b91c9e95b8b286f83c3fc47abff652e763bd on master.

Thanks @tadhg-ohiggins


shutter: 0.94.2 -> 0.94.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/shutter/versions.
meta.description for shutter is: '"Screenshot and annotation tool"'.
meta.homepage for shutter is: '"http://shutter-project.org/"

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.94.3 with grep in /nix/store/k1cxj3nqi987x1p4cjk9218hqj8xk2vy-shutter-0.94.3
directory tree listing: https://gist.github.com/5d324bca45ffa01d92531f954a0fbb97
du listing: https://gist.github.com/33deb4ac8ca9c443c260316d632b7f03

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
shutter

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k1cxj3nqi987x1p4cjk9218hqj8xk2vy-shutter-0.94.3 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A shutter https://github.com/r-ryantm/nixpkgs/archive/87081f877c67c0c470c5b7c221a0ff487d7e8cc9.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/k1cxj3nqi987x1p4cjk9218hqj8xk2vy-shutter-0.94.3
ls -la /nix/store/k1cxj3nqi987x1p4cjk9218hqj8xk2vy-shutter-0.94.3/bin

cc @bjornfor for testing.

I tested shutter on master (with and without this PR) and release-19.03 on NixOS with GNOME3 desktop.
Instead of capturing the screen, it captures a picture consisting of multiple copies of it's own application icon, side by side. I guess merging this doesn't make it worse, but shutter seems broken now. (It works fine in release-18.03.)
Does this have something to do with wayland? Is GNOME3 using wayland since 19.03?

Looks like a problem related to wayland: https://bugzilla.redhat.com/show_bug.cgi?id=1299293 ("Shutter does not work with Gnome/ Wayland").

Might as well do the update, for those using X instead of Wayland.


Install and config automatic changelog (conventional changelog)

Description
Install and config:

[ ] Conventional changelog

Waiting for @Sergih28 to decide when to release the first version.
Also need to decide how the release notes will be.


drivers: can: implement native Linux SocketCAN driver

Background Information
This is a new attempt to add a CAN driver for the native_posix board to interface with a Linux host system using the SocketCAN API. The driver itself is called native_linux, as it supports only Linux hosts and no other POSIX-based systems.
A similar driver was introduced in #37124. However, the CAN implementation in Zephyr changed significantly since that PR, so the driver was pretty much rewritten from scratch. Comments by @gmarull and @alexanderwachter in previous PR are addressed.
Details about the Linux SocketCAN implementation can be found in the Linux kernel CAN documentation and API header file.
Testing
In order to test the driver, a virtual CAN interface has to be set up on the Linux host:
sudo ip link add dev vcan0 type vcan
sudo ip link set up vcan0
sudo ip link property add dev vcan0 altname zcan0

In addition to that, the following overlay (or update of native_posix.dts) is required:
/ {
	chosen {
		zephyr,canbus = &can0;
	};
};

&can0 {
	status = "okay";
};

Afterwards, the driver passes all CAN driver tests:
scripts/twister -p native_posix -T tests/drivers/can

The driver does currently not pass the ISO-TP tests in tests/subsys/canbus/isotp. The ISO-TP tests are known to be brittle (e.g. they also fail for STM32G4, see #47014) and there is most probably a timing issue in the ISO-TP implementation itself. Fixing that is not within the scope of this PR.

Thanks @str4t0m for your very thorough review. I think all your points are valid and I'll come up with a solution latest tomorrow.

The remarks by @str4t0m are now considered. For easier review you can take a look at the changes which were squashed into the commit in this PR here: https://github.com/zephyrproject-rtos/zephyr/commit/eef547f84cd2732e1c27f48b6ea8f811b88693c8
I have also reduced the sleep time in the RX thread from 10ms to 1ms so that we can receive frames with less latency.


logLevel is not honored by instance

For React SDK. logLevel is not honored when setting up the instance.
const optimizely = optimizelySDK.createInstance({
  sdkKey: OPTIMIZELY_SDK_KEY,
  // Log Level settings [0, 1, 2, 3, 4]
  // https://github.com/optimizely/node-sdk/blob/master/lib/utils/enums/index.js#L20-L26
  logLevel: 0
})

Still displays console logs when running.

Hi @KyruCabading, to clarify your question.  Is the problem that its not respecting the log level at all or is it not allow you to set a PER instance log level?


Content change in setting ( Update in app )

[x] Content changes on Settings "App Access" 1. add subheading and also check the flow, must be as per content

LINK https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/f8070387-e976-4149-87cc-3fa2abfe6e9c/

[x] Need to change below heading in both screen as per design "Key details" and inside that "Settings"

Link
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/d13e1c1f-86e7-41fe-bfab-2987b0a2d92b/

Resolved.
Task 01,

Task 02,

Completed


hi

[Enter feedback here]

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

ID: e5a952d6-62a1-7cc4-c4ff-b67b3c5554bd
Version Independent ID: e2ca10ed-e883-c924-1b62-17c3c8e6ca64
Content: User Account Control (Windows 10) - Microsoft 365 Security
Content Source: windows/security/identity-protection/user-account-control/user-account-control-overview.md
Product: w10
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Looks like a test from the docs pages. Very likely that this one can be closed (unless the ticket author posts back).


[RyuJIT] node ILCompiler.DependencyAnalysis.GCStaticsNode is not marked when ILCompiler.DependencyAnalysis.RyuJitNodeFactory is MarkingComplete

Compiling a simple Tizen application on Ubuntu causes assertion in CoreRT/RyuJIT because the node
ILCompiler.DependencyAnalysis.GCStaticsNode is not marked when the factory ILCompiler.DependencyAnalysis.RyuJitNodeFactory is MarkingComplete
The stack trace is
            at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
            at System.Environment.get_StackTrace()
            at System.Diagnostics.Debug.Assert(Boolean condition, String message, String detailMessage)
            at ILCompiler.DependencyAnalysis.ExternalReferencesTableNode.GetIndex(ISymbolNode symbol, Int32 delta)
            at ILCompiler.DependencyAnalysis.ReflectionFieldMapNode.GetData(NodeFactory factory, Boolean relocsOnly)
            at ILCompiler.DependencyAnalysis.ObjectWriter.EmitObject(String objectFilePath, IEnumerable`1 nodes, NodeFactory factory, IObjectDumper dumper)
            at ILCompiler.RyuJitCompilation.CompileInternal(String outputFile, ObjectDumper dumper)
            at ILCompiler.Compilation.ILCompiler.ICompilation.Compile(String outputFile, ObjectDumper dumper)
            at ILCompiler.Program.Run(String[] args)
            at ILCompiler.Program.Main(String[] args)
         Unhandled Exception: System.Diagnostics.Debug+DebugAssertException:

            at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
            at System.Environment.get_StackTrace()
            at System.Diagnostics.Debug.Assert(Boolean condition, String message, String detailMessage)
            at ILCompiler.DependencyAnalysis.ExternalReferencesTableNode.GetIndex(ISymbolNode symbol, Int32 delta)
            at ILCompiler.DependencyAnalysis.ReflectionFieldMapNode.GetData(NodeFactory factory, Boolean relocsOnly)
            at ILCompiler.DependencyAnalysis.ObjectWriter.EmitObject(String objectFilePath, IEnumerable`1 nodes, NodeFactory factory, IObjectDumper dumper)
            at ILCompiler.RyuJitCompilation.CompileInternal(String outputFile, ObjectDumper dumper)
            at ILCompiler.Compilation.ILCompiler.ICompilation.Compile(String outputFile, ObjectDumper dumper)
            at ILCompiler.Program.Run(String[] args)
            at ILCompiler.Program.Main(String[] args)
            at System.Diagnostics.Debug.UnixDebugLogger.ShowAssertDialog(String stackTrace, String message, String detailMessage)
            at ILCompiler.DependencyAnalysis.ExternalReferencesTableNode.GetIndex(ISymbolNode symbol, Int32 delta)
            at ILCompiler.DependencyAnalysis.ReflectionFieldMapNode.GetData(NodeFactory factory, Boolean relocsOnly)
            at ILCompiler.DependencyAnalysis.ObjectWriter.EmitObject(String objectFilePath, IEnumerable`1 nodes, NodeFactory factory, IObjectDumper dumper)
            at ILCompiler.RyuJitCompilation.CompileInternal(String outputFile, ObjectDumper dumper)
            at ILCompiler.Compilation.ILCompiler.ICompilation.Compile(String outputFile, ObjectDumper dumper)
            at ILCompiler.Program.Run(String[] args)
            at ILCompiler.Program.Main(String[] args)

To reproduce this failure unarchive the attached file into the directory corert/tests/src/Simple as one more "Simple" test and run the build.sh script.
Uploading XForms.TizenMobile.tar.gz…
The used version of corert is ea7364d7a2ce1ea6547c96699c1ba9087ff21fe3 Merge pull request #3208 from shrah/master

CC: @Dmitri-Botcharnikov

@fadimounir  can you please take a look.

This is interesting. I haven't looked at the repro app in question but, from the stack, I thought the simpler repro would be this:
internal class Program
{
#pragma warning disable 649
    public static object Foo;
#pragma warning restore

    private static void Main(string[] args)
    {
        new Program();
    }
}

Except it doesn't repro with this because the statics info hashtable will end up generating the GC static base even though it's not used.
This would be a question to @fadimounir: do we always need to generate the GC static base? If so, this is probably the problem here. If not, we should make this also fail the same way for my repro, and fix it in the mapping table emission code.

do we always need to generate the GC static base?

Yes for constructed generic types that have GC statics (because it's needed by the StaticsInfoHashtable), but there isn't any code that i'm aware of that always generates the GC static base for non-generic types.
Sounds like the fix should be to check whether the statics node was marked in the dependency graph before emitting static field information in the reflection mapping table.

there isn't any code that i'm aware of that always generates the GC static base for non-generic types

Well, if I'm compiling the repro program I posted above, we do generate the GC static base and the DGML log says we generated it because:
  <Link Source="2101" Target="2105" Reason="GC statics indirection for StaticsInfoHashtable" Stroke="#FF0000" />

Sounds like the fix will be what you say plus more.

Ah, there's the repro:
class Foo
{
#pragma warning disable 649
    public static object Bar;
#pragma warning restore
}

class Gen<T> { }

class Program
{
    private static void Main(string[] args)
    {
        typeof(Gen<Foo>).ToString();
    }
}

Code got added to ConstructedEETypeNode that is trying to make sure we can generate the mapping table entry for the bases, but we need to mirror it in the unconstructed EEType. The fix will be there.


Modules API change

As of v4RC1, custom data type registration has been changed to struct-based approach.
This PR pulls the new redismodule.h file and migrates the module to use the new API. Additionally, it adds an implementation of the .mem_usage function to enable correct memory usage reporting with Redis' MEMORY USAGE command.
Note: in order to implement TDigestMemUsage I moved the definition of struct Point to the header file.

This should close #4

Thanks!


use templatefile function instead of data resource

what
instead of using deprecated (and not supported on new Macs) hashicorp/template provider use templatefile function
why

This module is using provider hashicorp/template https://registry.terraform.io/providers/hashicorp/template/latest/docs#deprecation which is deprecated
Provider hashicorp/template does not work on darwin_arm64 platform.

references
closes #20

had the issue in #20, would be great if this can be merged

/test all

@moperacz can you pull in the changes from the master branch into your PR? That will fix our tests and get this moving along. Thanks!

@Gowiem done 😉

/test all

Please why is the hashicorp/template still listed in versions file after this change?
https://github.com/cloudposse/terraform-aws-iam-user/issues/20#issuecomment-1195270118

Please why is the hashicorp/template still listed in versions file after this change?
#20 (comment)

could be from the state file, should be removed after you run a terraform apply

it is still listed in required_providers in versions.tf of this module
https://github.com/cloudposse/terraform-aws-iam-user/blob/master/versions.tf
If it is not required anymore can it be removed please?

@ivanmartos you're correct -- we missed that. Can you put up a PR and request a review from me? I'll review and merge ASAP.

@ivanmartos @b1n9s @moperacz -- @mehowthe was gracious enough to put up a PR to address removing the provider block. That was just merged and has been released as https://github.com/cloudposse/terraform-aws-iam-user/releases/tag/0.8.4


Add exception marker for positions which do not match the symmetry

Fixes #78.

Codecov Report

Merging #79 into dev will increase coverage by 0.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev      #79      +/-   ##
==========================================
+ Coverage   98.87%   99.06%   +0.18%
==========================================
  Files          10       10
  Lines        1066     1066
==========================================
+ Hits         1054     1056       +2
+ Misses         12       10       -2

Impacted Files
Coverage Δ

tbmodels/_tb_model.py
98.77% <100%> (+0.24%)
:arrow_up:

tbmodels/exceptions.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


fix: ensure checkout_plugin_ref only operates in expected worktree

fixes #55
--git-dir doesn't work as by itself, so also include --worktree

@aabouzaid, Any idea, when this will be merged.? we are also facing this issue if we aren't using the latest commit ref for the plugins.

I've fixed the issue, which will be included in the next release.


add options menu to radial ui

here you should be able to set their home position, name, and be able to unclaim/claim them

now is a wip


docs(cleanup): Update verbiage for Google App Engine to be more descriptive

Resolves GitHub issue:

Resolves Jira: [JIRAPROJECT-123]

@jasonmcintosh improved the wording in the release notes, so I had to make a new PR.


Feature/pre build credential

If we expose a login() method I think it feels more natural to cache the credentials.
And the parameter can be perfectly opt-out, so I changed the name and behavior.
Take a look and tell me what you think!

Much better! Thanks!


Optional ShouldQueue Behavior

Added a simple config option to use alternative Listeners without ShouldQueue interface

Oops, sorry for code style changing 😮

@volkv check my comment for my vision how it should be done. There is no need to make so many changes.

'queue_connection' => null, in Love's config file to use default queue connection
Publish this config file to your app and change this value to sync
Find a way how to force listener to use value from the config

@antonkomarev yes, got a way. will rePR ;)

There is no need to create separate Listener without ShouldQueue interface. I'm sure there is a way how we could set queue connection to sync on the fly.

Closing in favor of https://github.com/cybercog/laravel-love/issues/145#issuecomment-583730266


Misc/Code stuff regardless of ideas

[ ] Standardize coding style
[ ] Comments
[ ] Move UI into class instead of being in Game
[ ] Fix how main camera is fetched
[ ] Better asset file distribution
[x] Advanced UI functionality (ie: drag + drop)
[x] Fix compute shader branch - Texture rebind bug and emission code
[ ] Investigate texture disctance UV change bug

Fixed (most of) the compute shader branch with merge #36 and added drag-and-drop with merge #37


build-script-impl: Don't let distcc farm out cmake to run on other machines.

@swift-ci Please smoke test

@gottesmm What do you think about the above patch idea?

@erg That was the original intention of that line. So I am all for this. We should make sure that this still solve's DaveA's issue before we continue though.

None of the changes we're making now make sense to me.  Maybe we should wait until we can discuss this in person.


misc: run Lighthouse CI without assertions

Pre-flight checklist

[x] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation
This should not prevent the creating of a comment with the report in case of insufficient score (see https://github.com/facebook/docusaurus/runs/6289742244?check_suite_focus=true)

just wondering if it's possible to fail the CI check and yet publish the comment?

Apparently yes, I was too hasty with this deletion, since I should better change error to warn, and CI check was passed without fail.


Deprecate Transaction::dataset{,_mut} in favour of Deref{,Mut}

[x] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

@ttencate this looks great to me.  We should however deprecate the existing APIs, and remove in the next release.  Can you make that change?
@lnicola any other blockers?

All done!

bors r=rmanoka,lnicola


Problem with Flutter Future Exception Error Stacktrace

On Flutter 1.22 we can get trace bellow:

On Flutter newest (Channel master, 2.13.0-0.0.pre.549):

On Flutter newest (Channel master, 2.13.0-0.0.pre.549):
if I runApp widthout https://pub.dev/packages/stack_trace Or  without registerUnaryCallback for ZoneSpecification:

So, The new version of flutter's exception stack makes it harder for developers to locate problems.

Code sample
import 'package:flutter/material.dart';
// flutter 1.22 use stack_trace: ^1.9.6
// flutter 2.13 use stack_trace: ^1.10.0
import 'package:stack_trace/stack_trace.dart';

void main() {
  Chain.capture(() {
      runApp(MyApp());
  }, onError: (e, strace) {
    print(strace);
  });
}

Future thirdFuture() async {
  await Future.delayed(Duration(seconds: 1));
  throw 'throw exception';
}

Future secondFuture() async {
  await thirdFuture();
}

Future firstFuture() async {
  await secondFuture();
}
class MyApp extends StatelessWidget {
  const MyApp({ Key? key }) : super(key: key);

  @override
  Widget build(BuildContext context) {
    firstFuture();
    return Container();
  }
}

@linxuebin1990
Since https://pub.dev/packages/stack_trace is a dart package, I suggest you to open this issue in package's dedicated repo: https://github.com/dart-lang/stack_trace/issues for proper resolution on your issue.
Closing from here.

@linxuebin1990 Since https://pub.dev/packages/stack_trace is a dart package, I suggest you to open this issue in package's dedicated repo: https://github.com/dart-lang/stack_trace/issues for proper resolution on your issue.
Closing from here.

No, this is Bug of flutter, not stack_trace.

@darshankawar log 1 is perfect.
Now log is as fellow:


Minor Bug fixes

removing the "Token" word prevents it from responding with a 401 Unauthorized header.

Also, the env variables MeSomb_APP_KEY and API_KEY are the same?
Payments worked when I used the API key for both env variables. Because, in the request, the X-MeSomb_Application has to be the API key and the Authorization has to be the API key too.


do I need to configure server side or change HTTP header

I am new to pjax and trying to use django-easy-pjax as this:

1.html

views.py

urls.py

But this is not working.Do I need to add pjax_base.html or configure HTTP header to make it work? What else do I need to add in pjax_base.html more than base.html if that is required?

No, there is no need to change anything in an existing application.
You have to configure PJAX to load all links into a PJAX container on your base page:
https://github.com/defunkt/jquery-pjax


[BUG] Add a new resource.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
see https://github.com/apache/shenyu-dashboard/issues/224
Expected Behavior
No response
Steps To Reproduce
No response
Environment
ShenYu version(s): master

Debug logs
No response
Anything else?
No response

Please assigne to me.

Fix at the frontend.


Bug fixes, new setting, code clean up, and added support u64::max values per arg

This turned into a little more than just a quick bug fix :stuck_out_tongue_winking_eye:
Thanks to #409 I've piggy backed on that and added support for > 256 values as well.
There's also just a bunch of code deduping and super small macro cleanups.
After this merges I'll put out 2.0.3

88% coverage! Almost to 90!

@homu r+

:pushpin: Commit c31c2fb has been approved by sru

:hourglass: Testing commit c31c2fb with merge e47f825...

:sunny: Test successful - status


Require Elixir 1.12+

Pull Request Test Coverage Report for Build 4681cb8b5b7886e42a39c8b94a8ac94aa5dd55cc-PR-16
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-2.0%) to 92.667%

Files with Coverage Reduction
New Missed Lines
%

lib/hpax.ex
3
90.54%

Totals

Change from base Build f09f2478ae8c988cf76a1792fd5db0f18f394159:
-2.0%

Covered Lines:
139

Relevant Lines:
150

💛  - Coveralls


Added list of choices to termui prompt for user data if the data requested is a Choice

I found it odd that the user had to give incorrect input in order to be presented with the list of available options, for example:
Group by: something
Error: invalid choice: something. (choose from none, day, week, month)

In the above example the user is asked to give the program some interval to group by but offers no help as to what the valid inputs are until the user has incorrectly entered 'something'. With the modifications included in this commit the prompt would look as follows:
Group by (none, day, week, month):

It is now clear to the user that it has a limited set of options to chose from. This of course works in combination with default options.
Group by (none, day, week, month) [week]:

It is possible to disable the display of the choices by passing show_choices=False just like passing show_default=False works.
Also added a test for the new behaviour.
The last test of the test_chain.py test suite xFails, whatever that means, but it does that on master too so I don't think it's related to my changes.

This PR now has conflicts that need to be resolved. But other than that, is there any feedback you want to leave, anything you want to change in order merge these changes?

Depending on how many choices there are, this might become too verbose. Wouldn't it be better if this is explained through a custom helptext?

Depending on how many choices there are, this might become too verbose.

We can imagine some click application having more than twenty available options in a single choice, then it could become messy - iff the feature was enabled. But then such a large number of options in a choice is probably the exception rather than the norm amongst click programs.  And since the display of the available options in a choice has to be explicitly enabled by the developer I don't see how this is an issue in the context of the click framework providing this feature for developers to use. We have to be able to trust the program developer not to explicitly enable features of click which are unfit for his situation.

Wouldn't it be better if this is explained through a custom helptext?

This is automatic. It changes with the code and stays consistent with the program at all times. A custom help text has to be explicitly written by the developer as well as kept up to date by the same developer.
Part of what got me into using click was that it did much of the user facing documentation and interaction "for free" based on the program's internal structure. This is another step in that direction.

I've just come across this myself, you convinced me.

Hey @Rovanion any updates?

@untitaker Haven't had any time to spend on the PR since last and since it took a couple of months for someone to get back to me in the first place I figured there was no rush.
I'll look into it when I get a free evening.

@untitaker I've updated the code according to your suggestions and added documentation for show_choices to the docstring of prompt.

Sorry if I wasn't clear enough in my earlier message: I have a fix in the
works. Just gotta test it a bit, commit and push.
2016-10-31 21:46 GMT+01:00 Markus Unterwaditzer<EMAIL_ADDRESS>
@untitaker commented on this pull request.
In click/core.py https://github.com/pallets/click/pull/496:

@@ -1461,7 +1461,7 @@ def init(self, param_decls=None, show_default=False,
prompt=False, confirmation_prompt=False,
hide_input=False, is_flag=None, flag_value=None,
multiple=False, count=False, allow_from_autoenv=True,

            type=None, help=None, hidden=False, **attrs):

            type=None, help=None, hidden=False, show_choices=True, **attrs):

Yeah but right now it appears to get ignored.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pallets/click/pull/496, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmnx74h5mimNNuDd3J3jgbKCv1ZcY4uks5q5lOYgaJpZM4G9M0k
.

With this latest version of the commit, hash 1f1e1a5, I've added an additional test to make sure that you can both turn the choices list on and off in the prompt. I could still rewrite the tests to assert against the exact string but then the tests would test for other features of click than that in this PR, they would stop passing even if code was changed which is unrelated to the choices list.

And now there's a changelog entry!


Could you support layer diffusion?

Hi there,
Could you support layer diffusion? It needs custom model weights to generate transparent background image.
See here: https://github.com/huchenlei/ComfyUI-layerdiffuse
Highly appreciated!

I am really looking forward to receiving support layer diffusion

Layer diffuse support added in #66


angular-tablesort.d.ts is not a module

Getting this error when trying to build my project:

Error TS2656: Exported external package typings file 'SOMEPATH/node_modules/angular-tablesort/typedefs/angular-tablesort.d.ts' is not a module. Please contact the package author to update the package definition.

Perhaps we just need to change declare namespace angular.tablesort to export module angular.tablesort in the typedefs file here: https://github.com/mattiash/angular-tablesort/blob/master/typedefs/angular-tablesort.d.ts#L5
I'm not sure though, I'e not experienced this issue in my TS builds.

@realph Check the PR that this issue is now linked to. I think this will solve your problem.

@realph version 1.3.2 has now been released which includes this PR.  Please see if this fixes the issue

Fix included in 1.3.2


Killing the lact-daemon

After killing lact-daemon fan speed increases somewhere to 60 percents. The same thing happens for one second when you turn off the computer.

When the daemon shuts down, it turns fan control back to "automatic" (controlled by the driver). Due to a kernel bug this is not handled properly on all GPUs, and unfortunately there is nothing I can do about it. Not switching fan control to automatic is also not an option, since that would leave with no fan control at all after daemon shutdown.
If you want to be able to shut the daemon down without the fan speed bugging out, don't use the fan control feature.


[DOCS] Fix Sphinx Warning: the target found for cross-reference

Hi @tqchen @comaniac
Following issue #4908 and our discussion, this PR is going to fix the following two errors
WARNING: 'any' reference target not found:
WARNING: Unknown target name:

I would appreciate that if you could help to review/manage it, thanks.

The log shows 25 warnings including 4 undefined labels. Could you take a look and fix them? Other major warnings are related to lex python. You can also try to fix it, or I’ll take a look next week.
Sent with GitHawk

Hi @comaniac
Thanks for the review.
I solve the undefined label warnings and the output file as shown below link:
https://gist.github.com/cchung100m/f8bdef470b1a41c2408895610ee3b03e

@tqchen @comaniac
Thanks for the review and feedback. :)

Thansk @comaniac @cchung100m


fix(DCD): read frames with missing unit cell data

Molfile now defaults to all lengths set to zero. Did some quick tests and this does not seem to interfere with anything.
Depends on https://github.com/chemfiles/molfiles/pull/2.
Might fix #419.

Just updated the molfiles.tar.gz to the latest chemfiles branch just to be sure things are consistent. This should effectively contain the exact same files so I guess the hash change is due to timestamps.
Should be ready to merge.


Adds Register with RHUI/Public Cloud path

https://projects.engineering.redhat.com/browse/RHCLOUD-8031

Here's what I got ...

@mhuth looks like a second radio option is missing (from the mocks) the rhel6/7 rhel8 radio option? 🤔

Good catch @AllenBW.  Totally missed the OS version radio button.  Here's my new attempt ...


[sdk-stamps] add sdk stamps to bundle images

Description of the change:
Add SDK related metric labels and annotations to bundle images
Motivation for the change:
To enable OLM track SDK Operators with help of these stamps on bundle resources.
Things to do:

[X] Add stamps to bundle.Dockerfile and annotaions.yaml
[x] Add stamps csv (during generate csv command)

[x] Write test cases to verify the stamps on CSV

[x] Add stamps to crd (during generate crds command)

@estroz @joelanford @jmrodri Would be helpful to have initial reviews

Thanks @camilamacedo86 ! It was really helpful. I have made the suggested changes and also addressed the comment regarding gopkg.in/yaml.v2. Please have a look at it.

@estroz Modified the PR based on bumping of OR version. Please take a look.

@estroz Modified the PR based on comments. We had earlier discussed here that we would still like to have CRD-stamps on legacy projects and would be injecting it via the built in crd generation. Is it fine to leave it here and have a separate PR for new project layouts?

@estroz Removed labels from CRDs. Please have a look.

Modified the PR addressing the comments. --generate-csv command will not add sdk metric labels.