Automatically generate project based fixtures and updates tests

This PR attempts to automatically convert a given test to use project based fixtures.
It roughly works by:

Running the actual test, and hooking into the let definitions called in that test
Comparing the let with a known list of fixture names
Grabbing the files that we load from disk in those fixtures
Create a folder using the original fixture names that were used and placing the files we grabbed earlier in there
Parsing the tests AST and remove the offending let statements, and replace them with a single project based fixture setup

The code is a bit of a hot mess, but I've ran it on a few tests and it works well! 🎉
A small annoyance is that Parser::TreeRewriter will add a newline when we attempt to remove a block. Running rubocop afterwards fixes this but I think we can also fix it in the code.

An example
```
npm_and_yarn jurre/hack-mass-update-tests % AUTOFIX_PROJECT_FIXTURES=true be rspec
.
Finished in 3.26 seconds (files took 1.05 seconds to load)
1 example, 0 failures
Randomized with seed 9031

npm_and_yarn jurre/hack-mass-update-tests % g aa && g dc
diff --git a/npm_and_yarn/spec/dependabot/npm_and_yarn/file_updater_spec.rb b/npm_and_yarn/spec/dependabot/npm_and_yarn/file_updater_spec.rb
index 8ace723f0..fccd3182b 100644
--- a/npm_and_yarn/spec/dependabot/npm_and_yarn/file_updater_spec.rb
+++ b/npm_and_yarn/spec/dependabot/npm_and_yarn/file_updater_spec.rb
@@ -124,11 +124,11 @@ RSpec.describe Dependabot::NpmAndYarn::FileUpdater do
end
 context "with multiple dependencies" do

 let(:files) { [package_json, package_lock, yarn_lock] }

 let(:files) { project_dependency_files("generic/multiple_updates_multiple_updates_multiple_updates") }

 let(:manifest_fixture_name) { "multiple_updates.json" }

 let(:npm_lock_fixture_name) { "multiple_updates.json" }

 let(:yarn_lock_fixture_name) { "multiple_updates.lock" }

   let(:dependencies) do
     [

diff --git a/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/package-lock.json b/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/package-lock.json
new file mode 100644
index 000000000..38088fea7
--- /dev/null
+++ b/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/package-lock.json
@@ -0,0 +1,18 @@
+{

"name": "example",
"version": "1.0.0",
"lockfileVersion": 1,
"requires": true,
"dependencies": {
"etag": {

 "version": "1.0.1",

 "resolved": "https://registry.npmjs.org/etag/-/etag-1.0.1.tgz",

 "integrity": "sha1-KqQd5HT/xFZp8lyf7azWT+pPb/c="

},
"is-number": {

 "version": "2.0.0",

 "resolved": "https://registry.npmjs.org/is-number/-/is-number-2.0.0.tgz",

 "integrity": "sha1-RRx4v+bEJ/N7wqQGIm4M3kSfO1o="

}
}
+}
diff --git a/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/package.json b/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/package.json
new file mode 100644
index 000000000..429c2cdc6
--- /dev/null
+++ b/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/package.json
@@ -0,0 +1,23 @@
+{
"name": "example",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {

 "test": "echo \"Error: no test specified\" && exit 1"

},
"repository": {

 "type": "git",

 "url": "git+https://github.com/waltfy/PROTO_TEST.git"

},
"author": "",
"license": "ISC",
"bugs": {

 "url": "https://github.com/waltfy/PROTO_TEST/issues"

},
"homepage": "https://github.com/waltfy/PROTO_TEST#readme",
"dependencies": {

 "etag": "^1.0.1",

 "is-number": "^2.0.0"

}
+}
diff --git a/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/yarn.lock b/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/yarn.lock
new file mode 100644
index 000000000..cf380d0f9
--- /dev/null
+++ b/npm_and_yarn/spec/fixtures/projects/generic/multiple_updates_multiple_updates_multiple_updates/yarn.lock
@@ -0,0 +1,13 @@
+# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
+# yarn lockfile v1

<EMAIL_ADDRESS>
version "1.0.1"
resolved "https://registry.yarnpkg.com/etag/-/etag-1.0.1.tgz#2aa41de474ffc45669f25c9fedacd64fea4f6ff7"
integrity sha1-KqQd5HT/xFZp8lyf7azWT+pPb/c=

<EMAIL_ADDRESS>
version "2.0.0"
resolved "https://registry.yarnpkg.com/is-number/-/is-number-2.0.0.tgz#451c78bfe6c427f37bc2a406226e0cde449f3b5a"
integrity sha1-RRx4v+bEJ/N7wqQGIm4M3kSfO1o=

</details>

I'd recommend keeping this as a branch and not merging it. We do nasty things to hook into rspec etc that I don't think should be in main

This is a useful hack, but we're never going to merge this


Vulkan swapchain and graphics queue error happening when light baking

Tested versions

Reproducible in : v4.2.1.stable.official [b09f793f5], v4.3.dev4.official [df78c0636]

System information
Windows 10 - Godot.4.2.1.stable.- Forward Renderer- Nvidia Geforce GTX 1650 4GB
Issue description
When attempting light baking a custom mesh scene, increasing bake quality causes editor to stop refreshing visually, while mouse events are still processed underneath(resizing subwindow .etc) similar to https://github.com/godotengine/godot/issues/74700 .
lowering rays_per_pass project property value allows to prevent this upto the high quality bake settings.
Bake progress goes upto 14% before the console starts spamming errors and the editor doesn't refresh.
dev4:
success: low quality/4 bounces
failure: low quality/5 bounces (refer attached for console log)
after modification(Set bake_performance/max_rays_per_pass=16(previously 32 by default))
success: low quality/6 bounces, medium quality/3 bounces, medium/6 bounces
failure: high quality/3 bounces(refer attached for console log)
stable:
success: low quality/4 bounces, medium quality/3 bounces
failure: low quality/5 bounces (refer attached for console log), medium quality/6 bounces(see attached), high quality/3 bounces(see attached)
Attachments:
stable:
failure console log(low quality/5 bounces):

failure console log(medium quality/6 bounces):

failure console log(high quality/3 bounces):

dev4:
failure console log (low quality/ 5 bounces):

after rays per pass modification:
failure console log (high quality/3 bounces):

Additional: Bake progress meter did not even show up. reducing max rays per pass to 8 or 2 did not change the outcome.
Steps to reproduce
Maybe specific to my environment, regardless:
-Open the zip file.
-Run project with console enabled
-Set LightmapGI bake quality to high
-Hit bake
-Progress goes upto 14% before the console spams error
-In case of High Quality Bake, the progress popup shows but the bake progress meter doesnt even show up
Minimal reproduction project (MRP)
bakeTest.zip

I've also encountered this problem (was quite a headache as I was about to finish a project I needed to turn in the next day). I remember reading something about it running out of VRAM (and that's what I also saw when looking at task manager) but idk.
I'll do some bake tests later to see if I can reproduce it.

I've also encountered this problem (was quite a headache as I was about to finish a project I needed to turn in the next day). I remember reading something about it running out of VRAM (and that's what I also saw when looking at task manager) but idk. I'll do some bake tests later to see if I can reproduce it.

I was suspecting the same thing. Any ideas on how to reduce vram usage with lightmapping? I only see 3 properties under bake performance settings and only 2 of them are relevant to my case(rays per pass and region size)

Any ideas on how to reduce vram usage with lightmapping?

Try increasing the Lightmap Texel Size property for 3D scenes in the Import dock. In 4.3 or later, you can also decrease the Texel Scale property in LightmapGI.


Alfred workflow isn't working

The script for Alfred isn't working and has many errors in the debug.

Please Make sure Alfred integration enabled in Numi.


Successfully committed the change to the ledger by the peer

Successfully committed the change to the ledger by the peer but it is not upadating the ledger what is the problem Thank you.

@vishal3152  thank you for the answer but i am a new to fabric how to read the emitted block

This is one of the way :-
var startBlockListener = async function () {
const client = await Client.loadFromConfig("");
const channel = client.getChannel("");
var eh = channel.getChannelEventHubsForOrg()[0];// read from network-config.json
var block_reg = eh.registerBlockEvent((block) => {
console.log('Successfully received the block event: ' + block.number);
// read block here
}
startBlockListener().then(() => {});


Tina - Get it working with a separate content repo

https://tina.io/docs/guides/separate-content-repo/#introduction
This requires pulling the Content repo locally.
See an example here https://github.com/tkapa/test-tinacms-on-gatsby/tree/main

[x] Can see basic "posts/Hello-World.md" on the TinaCMS Admin Editor (Sourced from the separate repo)
[x] In staging, can see "posts/Hello-World.md" on the Admin Editor

Done - We can now see our SSW.Rules.Content branch on our Staging site.

Figure: /admin on Tina Staging


Fix for<EMAIL_ADDRESS>and npm@3

Fixes https://github.com/eslint/eslint/issues/4356
This handles a side effect of https://github.com/eslint/eslint/pull/4307

Will look into it - didn't hear about this issue before.
  // monkeypatch estraverse
  estraverse = estraverseRelative.require("estraverse");
  assign(estraverse.VisitorKeys, t.VISITOR_KEYS);

  // monkeypatch estraverse-fb
  var estraverseFb = eslintMod.require("estraverse-fb");
  assign(estraverseFb.VisitorKeys, t.VISITOR_KEYS);

  // ESLint v1.9.0 uses estraverse directly to work around https://github.com/npm/npm/issues/9663
  var estraverseOfEslint = eslintMod.require("estraverse");
  if (estraverseOfEslint !== estraverseFb) {
    assign(estraverseOfEslint.VisitorKeys, t.VISITOR_KEYS);
  }

We should probably be able to remove one of these?
And this was added for npm 3 as well https://github.com/babel/babel-eslint/commit/e84741070e68c8c805fef31a53c59849996d7b2e

Will have to test on both npm 2/3 but maybe we can just do
  estraverse = eslintMod.require("estraverse");
  assign(estraverse.VisitorKeys, t.VISITOR_KEYS);

Goina simply it after this - thanks for looking into it

And remove the rest

If do so, npm@3 and<EMAIL_ADDRESS>pair might come to not work.

Oh right. I was wondering if we needed the  eslintMod.require("estraverse-fb"); change at all but I guess that was changed recently so we should keep it?


Support for client certificates

This adds support for specifying a client certificate to use in mutual TLS authentication when communicating with a syslog server. Optionally, the private key can be encrypted and the password can be specified in the config file.
I am currently using this code to talk directly to a LogRhythm system monitor that has the RequireSecureSyslogClientCert option enabled.

@jgarman Do you have some time to review this and provide some feedback? Thanks!

Thanks for the contribution!  We are working on a new release in the next couple of weeks.


Minor wording changes/corrections

Hi Adin, thanks for your contribution. However, these copy edits aren't necessary. Our documents (including this one) are picked up by internal editors for copy edits and they edit in accordance with our internal standards. Thanks.
#please-close

@AErmie - Hi Adin, just to confirm that I've addressed the fixes that were relevant in another PR. Those should show up today. Thanks for your help!


The latest version of npm does not contain the latest updates from github

Package version on npm 0.2.1, does not contain the keyword addition update

A workaround i did was this
value={doc.name+" "+doc.keywords?.join(" ")}
It seems to work.

Yees, I need the asChild prop that is available only in the main branch 🙈

@pacocoursey Should we expect npm version bump soon?

https://github.com/pacocoursey/cmdk/releases/tag/v1.0.0


Devbuildcosmo for mch

Fixes the problem with the +gt1 variant not being passed to the dycore.

launch jenkins cosmo@master%pgi

Green on Tsa, merging


Fixing win x64 build with vs2015

After this, x64 should build with vs2015.
Basically couple more fixes related to sizeof(long) == 4 on windows.

Addressed the comments. PTAL.


Migrate to Openzeppelin test Environment

Closes: #1528
Migrating to the Openzeppelin Test environment should cut downtime requirement for JS tests significantly. 1/2 minutes compared to 9/10

[x]  2/3 unresolved tests
[x] Circle CI
[x] good .sol test alternative/ combination. I think the .sol tests run normally with truffle test after successful .js test completion, so we could probably just chain it.

@ngrinkevich, pushed this on draft until the above are resolved.

Great work! For the .sol test problem, I've found that moving the tests to stub contracts and replacing Asserts with requires results in a ~5x reduction in the time it takes to run them: #1549

  1) KeepRandomBeaconOperator/DkgMisbehavior
       should be able to save group members based on misbehaved data:
     Error: Returned error: VM Exception while processing transaction: revert Malformed signatures array -- Reason given: Malformed signatures array.
     at PromiEvent (node_modules/@truffle/contract/lib/promievent.js:9:30)
      at TruffleContract.submitDkgResult (node_modules/@truffle/contract/lib/execute.js:169:26)
      at Context.it (test/random_beacon_operator/TestDkgMisbehavior.js:120:28)
      at processTicksAndRejections (internal/process/task_queues.js:86:5)

  2) TokenStaking
       eligibleStake
         should report no eligible stake for passed future undelegation:
     AssertionError: expected<PHONE_NUMBER>000000000000000 to equal 0
      at Context.it (test/token_stake/TestTokenStake.js:808:35)
      at processTicksAndRejections (internal/process/task_queues.js:86:5)

:(

16:36 vs 06:28 for the entire cd solidity && npm run test step on CircleCi, nice!


Support other class-based test engines in junitPlatform

Building on #4250, support other class-based engines as well. If they already work, add some test coverage to prove it.

Just FYI, I wouldn't consider Spek class-based. Once https://github.com/Kotlin/KEEP/issues/75 lands, the wrapping class may go away in favor of script files.

Got it, in that case #4773 would be the appropriate issue.

I've just merged a change yesterday to support parallel test execution which completely overhauled the test execution listener used by Gradle to hook into JUnit Platform events. That should make it much easier to address additional issues.
I think #4912 can be addressed next, and then #4438. So, these things are on our radar and should be fixed in Gradle core but are not the top priority at the moment. Other issues, such as #4773, that would require substantial changes to the whole testing infrastructure could benefit from custom short-term solutions. For example, it's quite easy to create a custom task that uses the JUnit Platform ConsoleLauncher. The downside is the missing HTML reporting.

Any update on this issue..please let us know what needs to be done to support this?

@naveenchandra91 Class-based engines should generally work. Which one are you struggling with?

Related issues:

https://github.com/gradle/gradle/issues/4438
https://github.com/gradle/gradle/issues/4912


Add a Neo4j graph DB viewer

Add a Neo4j graph DB viewer to docker compose

sufficiently addressed with built-in neo4j DB viewer, added instructions to README.md
see https://github.com/eureka-network/DiscussionTrees/commit/f78be3dc659d02f43ab5b9c50e64e719ca006e63


[type:feature] init context path plugin shenyu ingress controller

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #5167 (deb7215) into master (75cdd03) will decrease coverage by 0.20%.
The diff coverage is 24.10%.

@@             Coverage Diff              @@
##             master    #5167      +/-   ##
============================================
- Coverage     60.87%   60.67%   -0.20%
- Complexity     8467     8473       +6
============================================
  Files          1242     1243       +1
  Lines         37433    37560     +127
  Branches       3532     3555      +23
============================================
+ Hits          22786    22791       +5
- Misses        12689    12806     +117
- Partials       1958     1963       +5

Files Changed
Coverage Δ

...org/apache/shenyu/k8s/common/IngressConstants.java
0.00% <ø> (ø)

...rg/apache/shenyu/k8s/parser/ContextPathParser.java
0.00% <0.00%> (ø)

...pache/shenyu/k8s/reconciler/IngressReconciler.java
33.67% <41.77%> (+2.90%)
:arrow_up:

...va/org/apache/shenyu/k8s/parser/IngressParser.java
53.65% <51.85%> (+18.65%)
:arrow_up:

... and 4 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Next.js Development does not work well with ngrok

Bug report
Describe the bug
When running Next.js in dev mode and then trying to load the app with ngrok.io everything kinda goes wonky. The CLI reports back Warn: You are opening multiple tabs of the same site in the same browser, this could cause requests to stall. https://err.sh/zeit/next.js/multi-tabs. That is not the case, I've got it open in one tab.  The reloading of the page/code sometimes doesn't happen.  I'm assuming it's because of the 2 connections that Next.js tries to keep open and ngrok is messing with that.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Run $ next dev
Start ngrok on the port Next.js reports back: $ ngrok -p 3000
Make changes to your app and navigate around while checking your terminal and the browser console.

Expected behavior
Running the dev through ngrok should not have an issue.  I'm assuming this is a pretty low priority bug, but I thought I should file it nonetheless.

any update on this

Hi, this was removed/updated in #7084. I'm going to close this, feel free to reply with additional info if you are still encountering trouble with this on an updated version.


[Bug] Cannot compile CodeLlama-7b-hf because of wasm-ld: error: initial memory too small

🐛 Bug

I tried compile CodeLlama-7b-hf for webgpu with q4f32 quantization. However it failed with wasm-ld: error: initial memory too small, 269728288 bytes needed.
To Reproduce
Steps to reproduce the behavior:

git clone https://github.com/mlc-ai/web-llm
cd web-llm
mkdir -p dist/models
cd dist/models
git clone https://huggingface.co/codellama/CodeLlama-7b-hf
cd ../..
python3 -m mlc_llm.build --model CodeLlama-7b-hf --target webgpu --quantization q4f32_1

This showed following error message.
Using path "dist/models/CodeLlama-7b-hf" for model "CodeLlama-7b-hf"
Target configured: webgpu -keys=webgpu,gpu -max_num_threads=256
Load cached module from dist/CodeLlama-7b-hf-q4f32_1/mod_cache_before_build.pkl and skip tracing. You can use --use-cache=0 to retrace
[17:06:44] /Users/catalyst/Workspace/mlc-ai-package-self-runner/_work/package/package/tvm/src/target/llvm/codegen_llvm.cc:185: Warning: Set native vector bits to be 128 for wasm32
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/clankpan/mlc-llm/mlc_llm/build.py", line 47, in <module>
    main()
  File "/Users/clankpan/mlc-llm/mlc_llm/build.py", line 43, in main
    core.build_model_from_args(parsed_args)
  File "/Users/clankpan/mlc-llm/mlc_llm/core.py", line 923, in build_model_from_args
    build(mod, args)
  File "/Users/clankpan/mlc-llm/mlc_llm/core.py", line 762, in build
    ex.export_library(args.lib_path, **args.export_kwargs)
  File "/Users/clankpan/.pyenv/versions/anaconda3-2023.09-0/lib/python3.11/site-packages/tvm/relax/vm_build.py", line 146, in export_library
    return self.mod.export_library(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/clankpan/.pyenv/versions/anaconda3-2023.09-0/lib/python3.11/site-packages/tvm/runtime/module.py", line 624, in export_library
    return fcompile(file_name, files, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/clankpan/.pyenv/versions/anaconda3-2023.09-0/lib/python3.11/site-packages/tvm/contrib/emcc.py", line 79, in create_tvmjs_wasm
    raise RuntimeError(msg)
RuntimeError: Compilation error:
wasm-ld: error: initial memory too small, 269796256 bytes needed
emcc: error: '/opt/homebrew/Cellar/emscripten/3.1.50/libexec/llvm/bin/wasm-ld -o dist/CodeLlama-7b-hf-q4f32_1/CodeLlama-7b-hf-q4f32_1-webgpu.wasm /Users/clankpan/mlc-llm/3rdparty/tvm/web/dist/wasm/wasm_runtime.bc /Users/clankpan/mlc-llm/3rdparty/tvm/web/dist/wasm/tvmjs_support.bc /Users/clankpan/mlc-llm/3rdparty/tvm/web/dist/wasm/webgpu_runtime.bc /var/folders/cj/vx3ycjy53klgp5r3nszk171w0000gn/T/tmp6_xuspag/lib0.o /var/folders/cj/vx3ycjy53klgp5r3nszk171w0000gn/T/tmp6_xuspag/devc.o -L/opt/homebrew/Cellar/emscripten/3.1.50/libexec/cache/sysroot/lib/wasm32-emscripten /opt/homebrew/Cellar/emscripten/3.1.50/libexec/cache/sysroot/lib/wasm32-emscripten/crt1_reactor.o -lGL -lal -lhtml5 -lbulkmemory -lstandalonewasm-nocatch-memgrow -lstubs -lnoexit -lc -ldlmalloc -lcompiler_rt -lc++-noexcept -lc++abi-noexcept -lsockets -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr /var/folders/cj/vx3ycjy53klgp5r3nszk171w0000gn/T/tmp7gxkykanlibemscripten_js_symbols.so --import-undefined --strip-debug --export-if-defined=__start_em_asm --export-if-defined=__stop_em_asm --export-if-defined=__start_em_lib_deps --export-if-defined=__stop_em_lib_deps --export-if-defined=__start_em_js --export-if-defined=__stop_em_js --export-if-defined=stackSave --export-if-defined=stackRestore --export-if-defined=stackAlloc --export-if-defined=__errno_location --export-table -z stack-size=65536 --initial-memory=83886080 --max-memory=2147483648 --entry=_initialize --table-base=1 --global-base=1024' failed (returned 1)

Expected behavior

I expected code llama can be build same as Llama-2-7b-chat-hf-q4f32_1
Environment

Platform (e.g. WebGPU/Vulkan/IOS/Android/CUDA): WebGPU
Operating system (e.g. Ubuntu/Windows/MacOS/...): MacOS 14.1
Device (e.g. iPhone 12 Pro, PC+RTX 3090, ...): Apple M3 Pro
How you installed MLC-LLM (conda, source): conda python3 -m pip install --pre -U -f https://mlc.ai/wheels mlc-chat-nightly mlc-ai-nightly
How you installed TVM-Unity (pip, source): following this page
Python version (e.g. 3.10): Python 3.11.5
GPU driver version (if applicable):
CUDA/cuDNN version (if applicable):
TVM Unity Hash Tag (python -c "import tvm; print('\n'.join(f'{k}: {v}' for k, v in tvm.support.libinfo().items()))", applicable if you compile models): 0ed0be0fdf006e9a9ae52f48e1cd25f0cc2c4637
Any other relevant information:

Additional context

If I increased the initial memory size by editing tvm/contrib/emcc.py from 80MiB to 320MiB, the compilation succeed. However chrome shows this error after initializing model.
Buffer size<PHONE_NUMBER>) exceeds the max buffer size limit<PHONE_NUMBER>).
 - While calling [Device].CreateBuffer([BufferDescriptor]).

try to limi your max-seq-len to a smaller number, right now the model have a larger max-seq-len that might cause the model to request more than available vram

Thanks!! It was fixed.

It seems compilation flow was changed recently. Where can I set max_seq_len in mlc_chat compile command?

you should be able to specify through mlc_chat gen_config, cc @CharlieFRuan on cross checking docs clarity

Which option is it? I could not find the option.
❯ mlc_chat gen_config -h
usage: MLC LLM Configuration Generator [-h] --quantization {q0f16,q0f32,q3f16_1,q4f16_1,q4f32_1,q4f16_awq} [--model-type {auto,llama,mistral,gpt2,gpt_neox,gpt_bigcode}] --conv-template
                                       {guanaco,mistral_default,oasst,conv_one_shot,vicuna_v1.1,minigpt,open_hermes_mistral,stablecode_completion,gpt2,codellama_instruct,LM,llama-2,stablelm,glm,wizardlm_7b,stablecode_instruct,gpt_bigcode,stablelm-3b,codellama_completion,redpajama_chat,llama_default,dolly,chatml,wizard_coder_or_math,gorilla,rwkv,rwkv_world,neural_hermes_mistral,moss}
                                       [--context-window-size CONTEXT_WINDOW_SIZE] [--sliding-window-size SLIDING_WINDOW_SIZE] [--prefill-chunk-size PREFILL_CHUNK_SIZE] [--tensor-parallel-shards TENSOR_PARALLEL_SHARDS] --output OUTPUT
                                       config

positional arguments:
  config                1) Path to a HuggingFace model directory that contains a `config.json` or 2) Path to `config.json` in HuggingFace format, or 3) The name of a pre-defined model architecture. A `config.json` file in HuggingFace format defines the
                        model architecture, including the vocabulary size, the number of layers, the hidden size, number of attention heads, etc. Example: https://huggingface.co/codellama/CodeLlama-7b-hf/blob/main/config.json. A HuggingFace directory
                        often contains a `config.json` which defines the model architecture, the non-quantized model weights in PyTorch or SafeTensor format, tokenizer configurations, as well as an optional `generation_config.json` provides additional
                        default configuration for text generation. Example: https://huggingface.co/codellama/CodeLlama-7b-hf/tree/main. Pre-defined model architectures include "llama2_7b", "llama2_13b", "llama2_70b", "codellama_7b", "codellama_13b",
                        "codellama_34b", "mistral_7b", "gpt2", "redpajama_3b_v1". (required)

options:
  -h, --help            show this help message and exit
  --quantization {q0f16,q0f32,q3f16_1,q4f16_1,q4f32_1,q4f16_awq}
                        The quantization mode we use to compile. If unprovided, will infer from `model`. (required, choices: q0f16, q0f32, q3f16_1, q4f16_1, q4f32_1, q4f16_awq)
  --model-type {auto,llama,mistral,gpt2,gpt_neox,gpt_bigcode}
                        Model architecture such as "llama". If not set, it is inferred from `mlc-chat-config.json`. (default: "auto", choices: auto, llama, mistral, gpt2, gpt_neox, gpt_bigcode)
  --conv-template {guanaco,mistral_default,oasst,conv_one_shot,vicuna_v1.1,minigpt,open_hermes_mistral,stablecode_completion,gpt2,codellama_instruct,LM,llama-2,stablelm,glm,wizardlm_7b,stablecode_instruct,gpt_bigcode,stablelm-3b,codellama_completion,redpajama_chat,llama_default,dolly,chatml,wizard_coder_or_math,gorilla,rwkv,rwkv_world,neural_hermes_mistral,moss}
                        Conversation template. It depends on how the model is tuned. Use "LM" for vanilla base model (required, choices: guanaco, mistral_default, oasst, conv_one_shot, vicuna_v1.1, minigpt, open_hermes_mistral, stablecode_completion,
                        gpt2, codellama_instruct, LM, llama-2, stablelm, glm, wizardlm_7b, stablecode_instruct, gpt_bigcode, stablelm-3b, codellama_completion, redpajama_chat, llama_default, dolly, chatml, wizard_coder_or_math, gorilla, rwkv,
                        rwkv_world, neural_hermes_mistral, moss)
  --context-window-size CONTEXT_WINDOW_SIZE
                        Option to provide the maximum sequence length supported by the model. This is usually explicitly shown as context length or context window in the model card. If this option is not set explicitly, by default, it will be determined
                        by `context_window_size` or `max_position_embeddings` in `config.json`, and the latter is usually inaccurate for some models. (default: "None")
  --sliding-window-size SLIDING_WINDOW_SIZE
                        (Experimental) The sliding window size in sliding window attention (SWA). This optional field overrides the `sliding_window_size` in config.json for those models that use SWA. Currently only useful when compiling Mistral. This
                        flag subjects to future refactoring. (default: "None")
  --prefill-chunk-size PREFILL_CHUNK_SIZE
                        (Experimental) The chunk size during prefilling. By default, the chunk size is the same as sliding window or max sequence length. This flag subjects to future refactoring. (default: "None")
  --tensor-parallel-shards TENSOR_PARALLEL_SHARDS
                        Number of shards to split the model into in tensor parallelism multi-gpu inference. (default: "None")
  --output OUTPUT, -o OUTPUT
                        The output directory for generated configurations, including `mlc-chat-config.json` and tokenizer configuration. (required)

Just in case I'v changed position_embedding_base smaller in mlc-chat-config.json but it showed  following error while generating.
Generate error, TypeError: Failed to execute 'createBuffer' on 'GPUDevice': Failed to read the 'size' property from 'GPUBufferDescriptor': Value is outside the 'unsigned long long' value range.

Current config params are here
{
  "model_lib": "CodeLlama-7b-hf-q4f32_1",
  "local_id": "CodeLlama-7b-hf-q4f32_1",
  "model_type": "llama",
  "quantization": "q4f32_1",
  "model_config": {
    "hidden_size": 4096,
    "intermediate_size": 11008,
    "num_attention_heads": 32,
    "num_hidden_layers": 32,
    "rms_norm_eps": 1e-05,
    "vocab_size": 32016,
    "position_embedding_base": 2048,
    "context_window_size": 4096,
    "prefill_chunk_size": 4096,
    "num_key_value_heads": 32,
    "head_dim": 128,
    "tensor_parallel_shards": 1
  },
  "vocab_size": 32016,
  "context_window_size": 4096,
  "sliding_window_size": -1,
  "prefill_chunk_size": 4096,
  "tensor_parallel_shards": 1,
  "mean_gen_len": 512,
  "max_gen_len": 2048,
  "shift_fill_factor": 0.3,
  "temperature": 0.7,
  "repetition_penalty": 1.0,
  "top_p": 0.95,
  "conv_template": "llama-2",
  "pad_token_id": 0,
  "bos_token_id": 1,
  "eos_token_id": 2,
  "tokenizer_files": [
    "tokenizer.model",
    "tokenizer.json",
    "tokenizer_config.json"
  ],
  "version": "0.1.0"
}

Generate error, TypeError: Failed to execute 'createBuffer' on 'GPUDevice': Failed to read the 'size' property from 'GPUBufferDescriptor': Value is outside the 'unsigned long long' value range.

This error was fixed by --prefill_chunk_size 1024 option!
Thanks!!

Thanks! For future reference, this error is brought up here in the WebGPU tab https://llm.mlc.ai/docs/compilation/compile_models.html#get-started


DHCP address for RecoveryNIC

I was not able to assign DHCP or dynamic address as the target IP on the recovery network interface. It is a simple task using the portal, but don't seems to be a way to do it using powershell.
Am I missing something or is this feature still don't available?

@rayne-wiselman - Do you have any information from a docs perspective that might help here?
@markcowl - Is this currently possible within the recovery/networking cmdlets, or would it be a feature request?

@diegopietruszka Hi, can you provide some context about which disaster recovery scenario you're setting up with Site Recovery, or the document that you're following. Thx!

@rayne-wiselman Hi, I created my own script based on this article https://docs.microsoft.com/en-us/azure/site-recovery/azure-to-azure-powershell
We have multiple environments in Azure West Europe Data Center (Each environment is a group of VMs belonging to a country), what the scrip does is basically create a recovery service vault for each of those environments, create a replication policy, add all the VMs as replicated items and create a recovery plan. All that using Azure North Europe Data Center as target.
Of course there are more details on the script but that is the idea.
On the target VNET we have multiple subnets (one per environment). When each VM is added as a Protected Item using “New-azurermrecoveryservicesASRReplicationProtectedItem”, Azure assigns as target subnet the first one in alphabetical order on the target VNET and an IP on it.
For that reason after the VMs are added, I change the target subnet and IP address using “Set-AzureRmRecoveryServicesAsrReplicationProtectedItem”.
The problem about assigning a fix IP to a protected item on the target subnet is that Azure does not consider the assigned IP as “used”. Which means, if you manually create a NIC (for another VM) on the target subnet using the portal and leave the IP address as dynamic, there are big chances it will assign the one already assigned to the protected item. The same way if you test the IP assigned to the protected item using “Test-AzureRmPrivateIPAddressAvailability” it will come up as a none used IP.
For that reason and to prevent conflicts, the previously used command “Set-AzureRmRecoveryServicesAsrReplicationProtectedItem” should have a parameter to assign a dynamic IP address on the target subnet (which is not possible today).

Can you take a look at this to see if it  helps - https://social.msdn.microsoft.com/Forums/en-US/85e57dd8-ee04-48d6-b54a-4e0d52fd3fb0/set-protected-vms-static-ip-address-using-powershell?forum=hypervrecovmgr

I saw that, but unfortunately does not help.
At one point they mention that you could assign a DHCP address, but there is no example on how to.

I suggest asking this question over on the Site Recovery forum - https://social.msdn.microsoft.com/forums/azure/en-us/home?forum=hypervrecovmgr

@diegopietruszka Going to close this issue since you've been directed to forums. If you think that there's documentation missing in the cmdlet itself, you can file a reference documentation issue with the engineering team: https://github.com/azure/azure-powershell/issues


Removal of secrets present in the test files

I've detected possible secrets in the test files that are generating alerts in the SAST analysis.
model/test_files/api.github.com.yaml:62179
model/test_files/api.github.com.yaml:1362
model/test_files/api.github.com.yaml:1247
model/test_files/api.github.com.yaml:1154
model/test_files/api.github.com.yaml:969
model/test_files/api.github.com.yaml:894
model/test_files/api.github.com.yaml:846
model/test_files/api.github.com.yaml:794
model/test_files/api.github.com.yaml:750
model/test_files/api.github.com.yaml:62182

I understand. I will consider this as resolved in my SAST analysis.
I suggest that this information be added to the FAQ, allowing Security Analysts to disregard… The same could also be done as a file comment.


Revive the variable names in GanaSquitVersionWrapper

Give the variables t1, t2, ..., tn better names.

I renamed the variables in 'summary' and in 'historian'. @feeds could you rename the variables?

@feeds Did you merge the branch variable-renaming?

no, i just fixed the stuff on transcrpt output...

i did not expect someone opened a branhc for such a minor change. Its all done now, so ill delete the other branch

also it seems @Lariiii did not push her branch... or she did it on the one commit happend on transcr-output.
Anyways, its done


Datepicker User Experience - Position should not change

What is the expected behavior?
When navigating between months in Datepicker, the position of the datepicker dialog should not change.
What is the current behavior?
If the datepicker appears above the control and we have to navigate between the months, switching to another month changes the height of the datepicker dialog, which ultimately changes its position. Which creates inconvenience since we have to reposition the mouse pointer on navigation control.
What are the steps to reproduce?
Visit https://material.angular.io/components/datepicker/examples
Resize the browser window and scroll the page such that the datepicker control is at the bottom of the windows.
Now click the datepicker icon, it should open the datepicker above the text box control.
Try navigating between months.

I noticed it too. It's kind of anoying if you have to jump fast through 5 or 6 months. In fact I'm working in a page right now with the console open that caused it. I click in in the left arrow and the calendar shrinks making the next click hitting the page background.

@mmalerba, maybe something like what is sugested in #5543, could avoid this in an elegant way.

Dupe of #5426

@jelbourn just clarify, I am referring to switching between months using the next/previous arrows shown on top right of the datepicker.


Add Role to Database

Add Role to Database
User Story
AS A business owner
I WANT to be able to view and manage the departments, roles, and employees in my company
SO THAT I can organize and plan my business
Acceptance Criteria
GIVEN a command-line application that accepts user input
WHEN I choose to add a role
THEN I am prompted to enter the name, salary, and department for the role and that role is added to the database

A new role can be added to the database through the addRole function.


Internal error + error 12/11 with multiple format on/off

Using black on master, Fedora 28.
I was trying to produce a minimal testcase for a different bug, but found this along the way. They're probably related, so I'm going to include them on the same issue for now.

 Please report a bug on https://github.com/ambv/black/issues.

Here's the contents of that file:
   File "/home/virtuald/black/black.py", line 3122, in assert_equivalent
    dst_ast = ast.parse(dst)
  File "/usr/lib64/python3.6/ast.py", line 35, in parse
    return compile(source, filename, mode, PyCF_ONLY_AST)

# fmt: off
def test_fader(test):

pass

# fmt: on

# fmt: off
something = 1
# fmt: on

Note that when I remove the empty line from test_fader() that the crash stops occurring, so that's probably the issue.

While that's definitely a bug to be solved, here's the source that I was trying to minimize for the original issue I encountered:
import pytest

# fmt: off

# Test data:
#   Position, Volume, State, TmSt/TmEx/None, [call, [arg1...]]

@pytest.mark.parametrize()
def test_fader(test):
    pass

# fmt: on

# fmt: off

something = ''

# fmt: on

The error from black is error: cannot format black_error.py: 12. When adding/removing whitespace, the error number changes.
Thanks!

Oh, and potentially related to #329, but they are differentish.


Auto-closing pairs feature activates when changing from {% ... %} to {%- ... -%}

Describe the bug
When changing from {% ... %} to {%- ... -%} on a nested tag, the auto-closing pairs feature activates where it shouldn't. Here's a video:
https://github.com/user-attachments/assets/6c2d33b3-89f6-4ce4-9efa-74bce7d5986a
Source

{% render 'product-card' %}

{% if true %}
  <!-- Adding "-" after "%" causes the issue -->
  {% render 'product-card' %}
{% endif %}

Expected behaviour
We should be able to change the opening bracket from {% to {%- without issues.
(Or better yet: Automatically add the dash at the closing bracket)
Actual behaviour
{% turns into {% %}-
Debugging information

Mac 14.7
Extension v2.4.3

That's a nice bug report if I've ever seen one. Thanks. Looking into it 🧐

However... I can't reproduce it. Can you send the list of extensions you are using? Maybe you have something conflicting?
https://github.com/user-attachments/assets/d92be12c-2431-4856-a54f-ca0e4d3e61fe


grandMA3

Works great with the grandMA2 software. Since the grandMA3 has just launched, hope it could work in the new grandMA3 platform as well.

GrandMA 3 Plugin for Companion is launched: https://bitfocus.io/connections/malighting-grandma3


B/better loging

Pull Request for initial Implementation

@Whatsuup
Trace is already the lowes mode.
We now only trace every request once. I think this is ok, because if you dont want to get all these messages, you can just disable the trace level.


Add badge and link to the Matrix room

This PR adds a badge and link for the Gitea Matrix room.
This allows people to choose how they can join the chat, as the Matrix room is bridged to Discord.

LGTM

build/testing failed because of github problem that are now fixed.
If you can please force commit or rebase to restart the process.
This is maybe not mandatory for this type of change and can be override by people with merge power.


Disallow 'open let', mark 'willSet' as 'private'

Follow-up to #15996:

Mark willSet/didSet accessors as private, always. These functions are always immediately inlined into a synthesized setter, and cannot be used with computed properties, so there's no benefit (and some harm) in having their access follow the property's.

Disallow open let, and add a verifier check to make sure we don't mix open and final in the future. You could write open let in Swift 4.1, but you couldn't actually override such a property (within the module or outside). To maintain source compatibility, this is just going to emit a warning before Swift 5 (instead of an error), since it wasn't harming anything in practice.

I wouldn't have bothered with the first part right now except that it was the only other place where we ended up with declarations that were both final and open under the old code.

@swift-ci Please test

@swift-ci Please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 6a080d8c5c88b62b3c3f945689b774efd770d808

@swift-ci Please test Linux

Hm, looks like I have more work to do!

Two additional commits. @slavapestov, mind glancing it over once more?
@swift-ci Please test

@swift-ci Please test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 6a080d8c5c88b62b3c3f945689b774efd770d808

Build failed
Swift Test OS X Platform
Git Sha - 6a080d8c5c88b62b3c3f945689b774efd770d808


upper level wind anomaly

Expected Behavior
With iterative winds, vertical motion should smoothly decay to 0 at the top of the model
Current Behavior
Currently with a flat z height below the model top, vertical motion decays to 0 at that height, then everything above it often has a large magnitude.
Possible Solution
investigate wind solver and z coordinate calculation, update iterative winds to always use model top.
Steps to Reproduce (for bugs)

set flat_z_height to -5
set wind = 3
may need to use sleeve coordinate?
run a domain with some topography

Your Environment

all environments

example from an ideal simulation @bertjebertjek tested

fixed by #130


Bootstrap CloudFormation Enhancements

This PR adds:

the ability to specify multiple IAM policies
context-appropriate path for the IAM role
default changed to ReadOnlyAccess

Signed-off-by: Jarod Neuner<EMAIL_ADDRESS>

Also added logic to suppress AWS credentials calls when secrets are not configured on the repo (ie, for this template).

@kajalnp The Test AWS Credentials was originally for debugging, but I left it in because it effectively logs the identity used to execute the workflow.


Shorten CI Runtime by Limiting Tests Based on Which Files Change

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3107
Originally created by @pnadolny13 on 2021-12-07 18:10:13

Currently a change to a discovery.yml runs CI tests that take ~1 hr. See target-bigquery change.
We should be able to run a subset of these tests to encourage faster iteration on discoverable plugins.

View 3 previous comments from the original issue on GitLab


drivers: sensor: Add OPT3001 light sensor driver

All checks passed.
checkpatch (informational only, not a failure)
-:99: WARNING:LONG_LINE: line over 80 characters
#99: FILE: drivers/sensor/opt3001/opt3001.c:39:
+	if (i2c_transfer(drv_data->i2c, msgs, 2, DT_INST_0_TI_OPT3001_BASE_ADDRESS) != 0) {

-:171: WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#171: FILE: drivers/sensor/opt3001/opt3001.c:111:
+	 * bits 11 to 0 are the mantissa bits
+     *

-:172: WARNING:LONG_LINE_COMMENT: line over 80 characters
#172: FILE: drivers/sensor/opt3001/opt3001.c:112:
+     * lux is the integer obtained using the following formula: (2^(exponent value)) * 0.01 * mantisa value

-:173: WARNING:BLOCK_COMMENT_STYLE: Block comments should align the * on each line
#173: FILE: drivers/sensor/opt3001/opt3001.c:113:
+     * lux is the integer obtained using the following formula: (2^(exponent value)) * 0.01 * mantisa value
+	 */

-:174: WARNING:LONG_LINE: line over 80 characters
#174: FILE: drivers/sensor/opt3001/opt3001.c:114:
+	uval = (1 << (drv_data->sample >> OPT3001_SAMPLE_EXPONENT_SHIFT)) * (drv_data->sample & OPT3001_MANTISSA_MASK);

-:198: WARNING:LONG_LINE: line over 80 characters
#198: FILE: drivers/sensor/opt3001/opt3001.c:138:
+	if (opt3001_reg_read(drv_data, OPT3001_REG_MANUFACTURER_ID, &value, true) != 0) {

-:198: WARNING:LINE_SPACING: Missing a blank line after declarations
#198: FILE: drivers/sensor/opt3001/opt3001.c:138:
+	u16_t value;
+	if (opt3001_reg_read(drv_data, OPT3001_REG_MANUFACTURER_ID, &value, true) != 0) {

-:207: WARNING:LONG_LINE: line over 80 characters
#207: FILE: drivers/sensor/opt3001/opt3001.c:147:
+	if (opt3001_reg_read(drv_data, OPT3001_REG_DEVICE_ID, &value, true) != 0) {

-:265: WARNING:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#265: FILE: drivers/sensor/opt3001/opt3001.h:20:
+#define OPT3001_CONVERSION_MODE_MASK BIT(10) | BIT(9)

-:266: WARNING:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#266: FILE: drivers/sensor/opt3001/opt3001.h:21:
+#define OPT3001_CONVERSION_MODE_CONTINUOUS BIT(10) | BIT(9)

- total: 0 errors, 10 warnings, 272 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

Your patch has style problems, please review.

NOTE: Ignored message types: AVOID_EXTERNS BRACES CONFIG_EXPERIMENTAL CONST_STRUCT DATE_TIME FILE_PATH_CHANGES MINMAX NETWORKING_BLOCK_COMMENT_STYLE PRINTK_WITHOUT_KERN_LEVEL SPLIT_STRING VOLATILE

NOTE: If any of the errors are false positives, please report
      them to the maintainers.

Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.


Protocol 'BinaryInteger' requires that 'Data' conform to 'BinaryInteger'

hi, when i run, it xcode say  "Protocol 'BinaryInteger' requires that 'Data' conform to 'BinaryInteger'", thanks.

@shenfu1991, this library is no where near ready to usage.


feat: Changing the timing of initializing the project folder

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/xun082/create-neat/blob/master/CONTRIBUTING.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:

What is the current behavior?

Closes https://github.com/xun082/create-neat/issues/78
Related to https://github.com/xun082/create-neat/issues/78

What is the new behavior?
I changed the timing of initializing the project folder so that the project folder is only created when the user finishes typing the preset.
And also cleans up the project folder if dependency is being downloaded and the user types CTRL+C to terminate it.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

改错文件了，架构迁移目前是在 createAppTest 中进行操作

OK


Implement boolean column subsetting for cupyx.scipy.sparse.csr.csr_matrix

E.g. xs[:, subset], where subset is e.g. np.array([True, False, True, False, True]) and xs is a cupyx.scipy.sparse.csr.csr_matrix. Note that row subsetting does not work in this case.
This came up when trying to run Scanpy with CuPy and Dask: https://github.com/theislab/scanpy/issues/921.

cc @mrocklin @pentschev


Init template

add @Kravalg and @Mihailmihail111 to codeowners
https://stackoverflow.com/questions/46340474/set-a-default-reviewer

the wrong pr


Decrease rank not visible but rank changed

Hi,
at the beginning - wonderfull library.
I've found just one problem. If I set disableAfterRate: false - I can change rating every time I click on a star - and this is GOOD. But if at second click I want to change rating to lower - f.e. from 4 stars to 3, rank is changed, but 4 stars still shows as active - and this is NOT GOOD.
$ ('. my-rating'). starRating ('getRating') shows 3, but 4 stars still shows "red". Is there any 'hook' to overcome this?

Bug fixed with code posten here: https://github.com/nashio/star-rating-svg/issues/51#issue-696607709
The same issue.


The size is reduced too much.

Describe the bug
I load a higher resolution image and it returns a very small image.
To Reproduce
Steps to reproduce the behavior:

Go to File
Click on Open File
Select the image
Click Remove Background
Click Save Image

Expected behavior
It should remove the background while maintaining the original resolution of the image.
Screenshots

Desktop (please complete the following information):

OS: Win8
Browser chrome
Version 2.0

Additional context

bug listed


Feature/nope resolver

Hey @bluebill1049, big fan ;)
I made this to use on a new project of mine, and figured I should put up a pr.
Let me know what you guys think!

oh wow! nice! thank you very much for this.

This is looking great! However, I believe that this could also be put up on a website. The README is starting to be bloated with examples. I think it makes sense to include a list of examples and link them to it.

Haven't seen any other library aside from the first three on the README. This kinda a great to experiment. Thank you. Really appreciated it.

@kysley
Thank you very much for sending the PR🙏
I reviewed your code.

Hey guys, I'm new to using Typescript in more complex situations, and would love a little guidance here.
Any NopePrimitive can be validated, changing the return signature.
Nope.string() //String, Number, Date, Boolean
  .test(a => (a === '42' ? undefined : 'Must be 42'))
  .validate('41');

// string => 'Must be 42'

If NopeObject has shape({...}), then ShapeErrors is returned.
const schema = Nope.object().shape({
  name: Nope.string()
    .atMost(15)
    .required(),
  email: Nope.string()
    .email('Please provide a valid email')
    .required(),
});

const errors = schema.validate({
  name: 'Test',
  email: 'invalidemail',
});

// ShapeErrors => { email: 'Please provide a valid email', }

I think to keep consistent, we should require a NopeObject WITH the shape signature. But I am unsure how to write a type signature for this scenario.

shall we get this boy in and sort out the type afterword? ship it first :)

shall we get this boy in and sort out the type afterword? ship it first :)

There seems to be an issue with nope. It doesn't validate nested objects within a schema. I think we should wait? Since RHF users may have nested form fields.

Thanks @kysley for the update, let's wait for nope validator author to response on the above :)  🙏

I would love to see this library supported, would want to replace my yup with something smaller

I would love to see this library supported, would want to replace my yup with something smaller

use Zod instead.

I close this one because the nope resolver is released


Embedding MFMessageComposeViewController/ImagePicker

Hi there,
I'm trying to embed an MFMessageComposeViewController into the semi modals and it will not work. I keep getting an error saying I cannot push a Navigation Controller. This does not happen with any view controllers from the storyboard. It happens with the Image Picker too.
Is there any solution to this problem?
Thank you!

@emleeh Hey sorry to hear that, if you send me a sample project i'd be happy to debug it!

@lukegeiger That would be amazing, thank you!
This is the bones of the problem, but I'll put together a quick project and send it to you too so you can see.
`if (![MFMessageComposeViewController canSendText]) {
NSLog(@"Message services are not available.");
}else{
    MFMessageComposeViewController *composeVC = [[MFMessageComposeViewController alloc]init];
    composeVC.messageComposeDelegate = self;

    // Configure the fields of the interface.
    composeVC.recipients = @[@"14085551212"];
    composeVC.body = @"Hello from California!";

    LGSemiModalNavViewController *semiModal = [[LGSemiModalNavViewController alloc]initWithRootViewController:composeVC];
    //Make sure to set a height on the view controller here.
    semiModal.view.frame = CGRectMake(0, 0, self.view.frame.size.width, (self.view.frame.size.height/6)*5);

    //Selected customization properties, see more in the header of the LGSemiModalNavViewController
    semiModal.backgroundShadeColor = [UIColor blackColor];
    semiModal.animationSpeed = 0.35f;
    semiModal.tapDismissEnabled = YES;
    semiModal.backgroundShadeAlpha = 0.4;
    semiModal.scaleTransform = CGAffineTransformMakeScale(.94, .94);

    [self presentViewController:semiModal animated:YES completion:nil];
}

`

@lukegeiger Also, it seems that viewDidAppear and viewDidLoad aren't called when the semi modal is dismissed. Is there any way of fixing this?
Thanks again!

Weird! I'll take a look as soon as you get a chance to send over a project.
Sent from my iPhone

On Feb 27, 2016, at 1:13 PM, emleeh<EMAIL_ADDRESS>wrote:
@lukegeiger Also, it seems that viewDidAppear and viewDidLoad aren't called when the semi modal is dismissed. Is there any way of fixing this?
Thanks again!
—
Reply to this email directly or view it on GitHub.

@emleeh Thanks so much for sending over the sample project! I have figured out what is going wrong.

The LGSemiModalNavController is a UINavigationController subclass. And you are trying to wrap the MFMessageComposeViewController in a NavigationController, which is not allowed. You can check this yourself by substituting the LGSemiModalNavController with a regular UINavigationController. So in your use case I'm afraid what you are trying to do can't be achieved.

For your second question, this is just how the view controller life cycle works in iOS. viewDidLoad is only going to get called once, when the view controller is initialized. In our case, we are never releasing the view controller from memory, and thus never re-initializing it again, so viewDidLoad will never get called again. As for viewWillAppear/viewDidAppear, again we are just presenting a vc over another, and the view behind is never actually disappearing, as it would with a navigation stack, so since it is not disappearing, it won't "re appear". You can achieve this same sort of affect programmatically however, if you set up some sort of delegate callback!

Thank you so much for being so helpful. I really appreciate it. I figured out that question two was my fault alright, sorry about that!
Best of luck with everything and thanks again.

Hi,
One good solution for dealing with 2) is using:
[self.parentViewController beginAppearanceTransition:YES animated:YES];
On the completion block after the semi modal is dismissed, that way all the necessary view lifecycle methods will be automatically triggered.
Cheers.

hey @apascual this repository is no longer maintained, but feel free to open up a pull request and i'll try to merge it in. thanks!


how can i visualize the loss curve

thanks！

you need to write code yourself. maybe read from log and draw with matplotlib or sth


Add AssumeRole support for EFS provider

Change Overview
Adds AssumeRole support for EFS provider.
Pull request type
Please check the type of change your PR introduces:

[X] Feature

This change looks good and makes sense to me.
I have a high level question though - @hakanmemisoglu do you have a sense for how this parameter will be specified from the callers? What is the end mechanism to configure this?

Blockstorage structs are mainly used by the structs in function package. These function structs are responsible for setting up the config.
I think, as a next step, we should add EFS support in these functions. Config should be set up exactly how EBS is set up. As an additional step, we can also check Role information. If we find one, role argument should be passed to the provider.
Right now, configuration building is done by checking credentials in profile and the info from PVC (in EBS case). We can add define additional key-pair for AssumeRole ARN in credentials. Or  we can add operation parameters argument to the whole process; so PVC info, secret credentials and operation parameters together will be sufficient to run Kanister ops (functions).


New Addon required for the app Sun Nxt and VI movies and Tv. REWARDS ARE GIVEN......

Required addon for the app(visit app store for the apps)

sun nxt (https://www.sunnxt.com/)
VI movies and TV (https://vimoviesandtv.in/)

Reward for creating the addon for KODI will be given
RS-1000 FOR EACH. IT SHOULD BE SIMILAR TO HOTSTAR OR NETFLIX........

Any update?


Password field validation

When creating a password, we should check that it has required conditions.

upper case
lower case
numeric
special character
length of at least 8

@vaastav @StephenVanSon it would be nice to validate this on the backend as well as frontend


Update Ontologies SOP with latest process

Description of the task:

Previously we made all ontology requests through our HCA ontology repo but in a meeting with David today it seems like it would be more efficient to make tickets directly in each of the individual git repos for each ontology. This ticket is to both confirm the process that we should use with David and/or Zoe as well as update the SOP documentation here: https://github.com/ebi-ait/hca-ebi-wrangler-central/blob/master/docs/SOPs/request_ontology_terms.md
Acceptance criteria for the task:

Based on our conversation with Paola yesterday, it might be better to default to using the HCAO repo and only post issues to the specific ontology repos when we have certainty that a new term is needed

Some information from latest ontology call:
l). Paola suggests a “decision tree” along the following:
Are you requesting a cell type or anatomy term? If yes,
Are you requesting a term that already exists in another ontology?
Then open a ticket in the HCAO tracker and request that we import that term
Are you requesting a term similar to one that already exists in another ontology?
Try to make an explicit case for having a new term; clarify what the differentia is with the existing term (e.g. "PMID:123456 suggests that cells in zone A and B of organ X are functionally different because..." rather than just listing PMID:123456).
If you think you have a reasonably strong case, then open a ticket in the appropriate source ontology tracker (CL, Uberon…)
If you think your case is not strong enough at the moment, but may become stronger in the future when more experimental evidence is available, then open a ticket in the HCAO tracker
If you are unsure, then open a ticket in the HCAO tracker
Are you requesting a grouping term, e.g. lumping together 2 or more existing cell types or anatomical structures?
Follow the same procedure as above
Are you requesting a term that doesn’t exist at all in CL or Uberon, possibly because it’s specific to mammals?
Then open a ticket in the CL or Uberon tracker; provide references and suggest appropriate taxon restrictions if applicable.
Are you requesting a term other than cell type or anatomy? If yes,
Open a ticket in the EFO tracker
It is advisable to keep term requests, and specific questions/update requests about existing tickets, within the GitHub trackers please, rather than on Slack. It’s easier to keep track in GitHub. Of course, feel free to ping Paola on Slack if it’s urgent (just be aware that she’s part-time so may not respond immediately).
https://docs.google.com/document/d/1PXLco-VtpRIFA1DuDDafxqQl2PSW2ZZMG82qA_-1xIE/edit#

I tried to make a diagram of this flow here: https://app.diagrams.net/?libs=general;flowchart&src=about#G1CSUSllc_1LWz3QG3dKXkIMLe-t_1PqgG
I still have some questions about it so I am trying to set up a time to talk to paola and get those questions answered before incorporating into the SOP.

This is waiting on feedback from ontology team on what the process should be, should check back up on it the week of 30/11

Pinged paola to ask if a suitable process and decision tree has been worked out that we can incorporate into the SOP.

I made some updates based on the latest communications with Paola but still have some open questions before closing this ticket

I would like another wrangler to have a quick read through before classifying as done.

I have read the SOP and it looks easy to follow and clear to me.
I have found a potential typo in the sentence
Does it already exist in FAO?.
https://ebi-ait.github.io/hca-ebi-wrangler-central/SOPs/request_ontology_terms.html#decision-tree
Did you mean FMA in place of FAO?
Other than this, the SOP looks fine to me.

Thanks for the review and feedback, I have fixed the typo and will close this issue, we can update if people come across any further issues


Very Confusing Paragraph

You should remove or reword this paragraph.  It's very confusing to be reading an article about SQL MI and have a paragraph that's specific to SQL DB.  For a SQL MI article, don't tell customers to use DMA and then tell them DMA isn't supported for SQL MI.
"Use Data Migration Assistant (DMA) to detect potential compatibility issues impacting database functionality on Azure SQL Database. DMA does not yet support Managed Instance as migration destination, but it is recommended to run assessment against Azure SQL Database and carefully review list of reported feature parity and compatibility issues against product documentation. Most of the blocking issues preventing a migration to Azure SQL Database have been removed with Managed Instance. For instance, features like cross-database queries, cross-database transactions within the same instance, linked server to other SQL sources, CLR, global temp tables, instance level views, Service Broker and the like are available in Managed Instances."

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

ID: b4f5af17-9b52-8353-eb19-973b0d210057
Version Independent ID: 32c6337c-5e56-d7d2-dc58-f81f0ca4e23f
Content: Migrate SQL Server instance to Azure SQL Database Managed Instance
Content Source: articles/sql-database/sql-database-managed-instance-migrate.md
Service: sql-database
GitHub Login: @bonova
Microsoft Alias: bonova

@jhenriks79 Thanks for the feedback! We are currently investigating and will update you shortly.

@bonova The specific paragraph is found in this section of the document. The title of the document is "SQL Server instance migration to Azure SQL Database Managed Instance" and the second paragraph of the linked section is telling you to use Data Migration Assistant.

@Mike-Ubezzi-MSFT The recommendation in the paragraph in question explains why we recommend running DMA to provide an assessment of the current state of a database for migration to SQL Database. While it is true that not all of these limitations will apply to Managed Instances - some do and understanding the results from running the DMA tool will be useful before beginning a migration to a Managed Instance.
#please-close

The way you just described why DMA is important is far more helpful than what currently exists in that paragraph in the docs. Suggest you reword that paragraph.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Carl Rabeler<EMAIL_ADDRESS>Sent: Tuesday, April 17, 2018 4:25:21 PM
To: MicrosoftDocs/azure-docs
Cc: jhenriks79; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Very Confusing Paragraph (#6033)
@Mike-Ubezzi-MSFThttps://github.com/Mike-Ubezzi-MSFT The recommendation in the paragraph in question explains why we recommend running DMA to provide an assessment of the current state of a database for migration to SQL Database. While it is true that not all of these limitations will apply to Managed Instances - some do and understanding the results from running the DMA tool will be useful before beginning a migration to a Managed Instance.
#please-close
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/6033#issuecomment-382189306, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD72tWezsUq1BJe6bo-Zf1-djBDS0oaGks5tpnnhgaJpZM4SyW26.

Thanks – will rewrite for the author.
From: jhenriks79<EMAIL_ADDRESS>Sent: Tuesday, April 17, 2018 4:49 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Carl Rabeler<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Very Confusing Paragraph (#6033)
The way you just described why DMA is important is far more helpful than what currently exists in that paragraph in the docs. Suggest you reword that paragraph.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Carl Rabeler <notifications<EMAIL_ADDRESS>Sent: Tuesday, April 17, 2018 4:25:21 PM
To: MicrosoftDocs/azure-docs
Cc: jhenriks79; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Very Confusing Paragraph (#6033)
@Mike-Ubezzi-MSFThttps://github.com/Mike-Ubezzi-MSFT The recommendation in the paragraph in question explains why we recommend running DMA to provide an assessment of the current state of a database for migration to SQL Database. While it is true that not all of these limitations will apply to Managed Instances - some do and understanding the results from running the DMA tool will be useful before beginning a migration to a Managed Instance.
#please-close
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/6033#issuecomment-382189306, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AD72tWezsUq1BJe6bo-Zf1-djBDS0oaGks5tpnnhgaJpZM4SyW26.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F6033%23issuecomment-382194277&data=02|01|Carl.Rabeler%40microsoft.com|64d108583ad749364e0108d5a4bdbd34|72f988bf86f141af91ab2d7cd011db47|1|0|636596057185356475&sdata=wsUmhe2NTpV3sHft9xfdOtsC9AnmscBDWaHIJGXsMJk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMCBn0gXI0J-wOmfdnkWRVJJfX-XP0S_ks5tpn9TgaJpZM4SyW26&data=02|01|Carl.Rabeler%40microsoft.com|64d108583ad749364e0108d5a4bdbd34|72f988bf86f141af91ab2d7cd011db47|1|0|636596057185366480&sdata=erLz9%2B1Hf6JQ411RurZsOPrASTFHa4LwDoknzHvn4ec%3D&reserved=0.


SOLR-14758: Fix NPE in QueryComponent.mergeIds when using timeAllowed and sorting

See https://issues.apache.org/jira/browse/SOLR-14758 for more information and discussion!

All tests pass for me, precommit succeeds.

@intixbram I changed the check for partial results to use SolrJ API. In main branch this failed because the type of the NamedList value was different. Now it expects a boolean.

I ran the DistributedQueryComponentCustomSortTest test using gradlew beast -Dtests.dups=40 and it now passed each time.


fix: fix infinite spinner in overlay after login (Issue #1454)

Description:
Removed filter in the initSelectedConversationsEpic to allow getSelectedConversations during init in Overlay
Issues:

Issue #1454

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


Haystack SearchFieldError: ... has an empty model_attr 'version' and doesn't allow a default or null value

I try to set up solr search for my local RTD. I get an error:
haystack.exceptions.SearchFieldError: The model '<ImportedFile: MyFileName.html: MyProjectName>'
has an empty model_attr 'version' and doesn't allow a default or null value.

This error occurs after the following commands:
./manage.py build_files
./manage.py update_index

The command update_index raises this error.
What's going on? What am I doing wrong?

Haystack isn't supported anymore. All search now uses Elastic Search directly.

ger


too slow

Hi
we write a go example in libmill and seem to consume lot of memory?
https://play.golang.org/p/8YDG82gqnF

That's 10000 stacks. You may try to preallocate stacks of specific size using goprepare.


trace file location

Background
We need trace file on same location independent on where user stands
Problem/Issue
What have I done
Check list
I have:

[ ] Tested with Stub run
[ ] Tested on our HPC

I thought the trace file would contain the same information that you get when running nextflow log -f trace.txt | less, which is not true. This PR will not be merged.


Masterisation -  identifying one and only one canonical record per health facility

https://docs.google.com/document/d/1iE5zqgfh1JmQpPBQ9A4IrTdX1HcZx98ZWHuDR0wnhYU/edit?usp=sharing

Current story
Now our locality can be flagged as synonym or master. It can be changed in edit mode
here is test case :

we have : Rumah Sakit Bhayangkara Sartika Asih

than we have : Klinik IT Telkom. We want Rumah Sakit Bhayangkara Sartika Asih as it's master. Here is the screenshot how to set it.

but we want to set Rumah Sakit Bhayangkara Sartika Asih has master

and we decide Rumah Sakit Pindad as Rumah Sakit Bhayangkara Sartika Asih's master

here is Rumah Sakit Bhayangkara Sartika Asih info

and because Klinik IT Telkom has Rumah Sakit Bhayangkara Sartika Asih as master, it will change it's master to Rumah Sakit Bhayangkara Sartika Asih's master too

The backend already handle based on story in document


Postday1

based on how things went today :) See issue #286

@avahoffman I know with previous years you wanted to wait for updates - do you want to do that again? I can merge this later - or if you think it could be helpful I will merge this now.

@avahoffman I know with previous years you wanted to wait for updates - do you want to do that again? I can merge this later - or if you think it could be helpful I will merge this now.

@carriewright11 I think it might confuse folks if the lab is different from what it was in class. Ok if we wait?

@avahoffman I know with previous years you wanted to wait for updates - do you want to do that again? I can merge this later - or if you think it could be helpful I will merge this now.

@carriewright11 I think it might confuse folks if, when they go to download something, it is different from what it was in class. Ok if we wait?

yeah we can wait


Community patch clickhouse make it possible to not specify index

Vector indexes in ClickHouse are experimental at the moment and can sometimes break/change behaviour. So this PR makes it possible to say that you don't want to specify an index type.
Any queries against the embedding column will be brute force/linear scan, but that gives reasonable performance for small-medium dataset sizes.
Previous PRs:
https://github.com/langchain-ai/langchain/pull/19527
https://github.com/langchain-ai/langchain/pull/18381

@efriis  can you get the build to run on this version of the PR?

@efriis did you get a chance to look at this?

@efriis would you be able to kick off the build so that we can see if these changes work?

@efriis any chance you can take a look at this?


To change the Done text color

Is there any way to change the color of the text from Blue to my own color for DONE which comes for actions. Thanks

Use the confirm parameter by Text widget
confirm: Text('custom confirm')


Fix node height handling in dynamic_tree.c

Should improve balance calculation
Pull requests for core Box2D code are generally not accepted. Please consider filing an issue instead.

Fixed in #847


Furkan's suggestions

Fixes #439
Fixes #442

I rebased away the change to the append section.
The co-location section actually has other things in its queries that don't make sense, like a reference to tenant_id which doesn't exist. I'll look the section over, supply some sample data, and run the queries to get any bugs out.

I rebased away the change to the append section.
Also simplified the code in co-location section. Ran the example, adding some data in and verified that it runs.


Automate the installation of VirtualBox extension pack with cask

It is as simple as running VBoxManage extpack install name-of-extpack

+1

+1

What I do in bash after brew cask install virtualbox:
(
  cd /tmp;
  vbox_full_version=$(brew cask info virtualbox | head -1 | cut -d' ' -f2);
  vbox_short_version=${vbox_full_version/-*};
  curl -L -O http://download.virtualbox.org/virtualbox/${vbox_short_version}/Oracle_VM_VirtualBox_Extension_Pack-${vbox_full_version}.vbox-extpack;
  sudo VBoxManage extpack install --replace Oracle_VM_VirtualBox_Extension_Pack-${vbox_full_version}.vbox-extpack;
  rm *.vbox-extpack;
)

@delitescere - thanks for that josh, very useful.
now any chance we can get a brew cask install virtualbox-extensionpack that does that? ;-)

@delitescere - thanks for that josh, very useful.
now any chance we can get a brew cask install virtualbox-extensionpack that does that? ;-)

Unlikely unless we get a PR, @delitescere. This is really low priority (0, I’d say) and no maintainer seem to have the time or inclination to work on it.

yeah?
https://github.com/caskroom/homebrew-cask/pull/12806
done

Thank you, @ftc2! This cask does the job very well. I guess, this issue can be closed for now. Feel free to open it if some additional problems with the current solution will occur.


BufferBuilder - Processing Reported Aspatial Points

This Pull Request is to merge the BufferBuilder branch into main after testing and such has been completed.
Changes:

Added new BufferBuilder tool that will look as a aspatial master data sheet and create some site points and site buffered polygons based on the metadata contained within the sheet.
Some processing takes place in the background with the new tool, so feel free to look through that and see how the data get processed.
Starting to transition to the new file structure of the toolkit, it will be more fleshed out in future updates and pull requests.
Swapped over to some new library versions and updating the toolkit version.

Has been tested by Andrea, merging to main.


Small bug of element hovering in a list on windows

I found this bug while trying to see how the window reacted to getting resized.
Basically when we resize a window containing a list, it seems like the list will think that the cursor is hovering over some elements when it isn't the case.
It isn't that big of a deal and doesn't prevent to work at all, but it's something that I think can be considered a bug.
I am using Windows 10 64 bits 1909 and my current project uses .NET Core 3.0

I suspect this is related to https://github.com/AvaloniaUI/Avalonia/pull/2988 where we don't properly null the mouse position when the mouse leaves the client area.  Well done for finding a case to make it fail :)


Create an interface for Gurobi on AWS

This is as simple as changing a gurobi config file, closing.


Support command-line interface for custom models

It would be waste of time for me to try and put all the possible Keras options you could tweak into the command line interface. Ultimately Mycroft is more useful if you can write your own models in code.
Still Mycroft provides some advantages over starting from scratch every time: e.g. all the pandas data processing, seamless incorporation of word embedding vectors, the prediction and evaluation code which remains the same regardless of model, and a command line interface. It would be good to be able to easily leverage that for new models.
Do this by adding command line support to the TextEmbeddingClassifier. Add to the interface a command_line function that returns an argparse subparser. Refactor the current models to use this and call it from console.py:main to build the command line parser. Also export a main function that somebody else's code could call passing in a TextEmbeddingClassifier as an argument. This would build a command-line interface for just this class.
Would need to explain this clearly in the README, where the value-add over writing Keras code from scratch lies.

Actually, this isn't done until I have an example script that trains a model outside of the Mycroft module. Need to make the model constructors a little more generic.

Determine what command options need to be created for the training of a model by inspecting the arguments in its constructor.
Make it so that the argument parsing code writes itself.


Button loading text

Is your feature request related to a problem? Please describe.
When property isLoading is true on the button component the loading text is always in Spanish
Describe the solution you'd like
Add a property to specify the language and display it in English or Spanish
Describe alternatives you've considered
Add a property to set a custom text in the loading

You can use the prop renderLoading with this properties to customizate the text or the component to render loader.


Update package.json

My command line did not like the colons, added sniper to the scripts.

Thanks


Modules 241 branch 11

I am rejecting this PR. I will put the discussion on the JIRA issue though.


Add Depth to components

Feature
Use the new Depth mixins in HSDS components:
d200 - FluffyCard
d300 - Page
d300 - RadioCard
d300 - CheckmarkCard
d400 - ArticleCard
d600 - Notification
d700 - Modal

Hi @digitaldesigner, a couple of questions for ya!
CheckmarkCard

I put the same depth as -> RadioCard, is that ok? should I roll back those?
Just noticed that the focus style on a checked card is invisible as the border and the focus style are the same

Other components
Should we apply depth to any of these?

AttachmentList with preview
MessageCard

Ah sorry man, CheckmarkCard should be d400
If you want to apply depth to AttachmentList with preview then it'd be d400, and MessageCard is d600

Thanks! I made the updates


feat: A CLI around #find

(WIP)

[ ] depends on: #6363

This turned into https://github.com/nomeata/loogle


Feature Request: Block::getByName() shouldn't be limited to Stacks

The current implementation of Block::getByName() currently searches only stacks, despite the fact that any block can be assigned a name. This appears to be supported by the documentation: "scrapbooks let you name a Block, and then refer to that Block with PHP code."
Proposal
We should either:

Remove the restriction that you can only retrieve blocks by name if the block is in a stack
Restrict the ability to assign a block a name when not in a stack.

Since I see no reason to limit functionality, I'm suggesting we remove the restriction.
Block::getByName()
https://github.com/concrete5/concrete5/blob/develop/web/concrete/src/Block/Block.php#L69
public static function getByName($globalBlockName)
    {
        if (!$globalBlockName) {
            return;
        }
        $db = Loader::db();
        $sql = 'SELECT b.bID, cvb.arHandle, cvb.cID'
            . ' FROM Blocks AS b'
            . ' INNER JOIN CollectionVersionBlocks AS cvb ON b.bID = cvb.bID'
            . ' INNER JOIN CollectionVersions AS cv ON cvb.cID = cv.cID AND cvb.cvID = cv.cvID'
            . ' WHERE b.bName = ? AND cv.cvIsApproved = 1'
            . ' AND cvb.cID IN (SELECT cID FROM Stacks)'
            . ' ORDER BY cvb.cvID DESC'
            . ' LIMIT 1';
            var_dump($sql);die();
        $vals = array($globalBlockName);
        $row = $db->getRow($sql, $vals);
        if ($row != false && isset($row['bID']) && $row['bID'] > 0) {
            return self::getByID($row['bID'], Page::getByID($row['cID']), $row['arHandle']);
        } else {
            return new self();
        }
    }

:+1:

Makes sense to me, too


Use libtermkey git repository when installing HEAD (refers #155)

This should prevent the problem when users try to install libtermkey dependency from behind a firewall. The libtermkey git repository doesn't provide tags/versions, so I preferred to adopt it only on the HEAD version (after all, people upgrades neovim frequently).

Are you certain this works? The "dist" version of libtermkey (see its Makefile for context) is different than the raw source.
Reason I asked for a PR is that I had hoped you found a way to auto-create the "dist" version.

Well, I've just used the git repo for the HEAD version of neovim. It's a simple workaround/hack to compile neovim from a machine behind a firewall. It works in this sense :-P

Any updates on this?

I don't see how this can possibly work. libtermkey makefile has a "dist" target:
https://github.com/neovim/libtermkey/blob/master/Makefile#L173
The "dist" target modifies the contents for end-user compilation. The contents at http://www.leonerd.org.uk/code/libtermkey/libtermkey-0.18.tar.gz are the result of the "dist" target. Whereas the changes in this PR point to the raw source tree.

After #195 this won't be possible. And the questions above were not addressed.


Add influxdb cloud

Proposed change

Added support for the new v2 cloud version that influxdb added. Copy is a heavy port from existing influxdb component. This will require that you have registered an account https://cloud2.influxdata.com/signup and copy your bucket and org from there website.
Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New integration (thank you!)
[ ] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
influxdb_cloud:
  url: "https://eu-central-1-1.aws.cloud2.influxdata.com"
  token: "xxx"
  bucket: "xxx"
  org: "xxx"

Additional information

The easiest way to get your bucket and org token is to click on the default bucket that was created for your new account and then copy it out of the url.

Link to documentation pull request:
Doing documentation now..

Checklist

[x] The code change is tested and works locally.
[x] Local tests pass. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the development checklist
[x] The code has been formatted using Black (black --fast homeassistant tests)
[ ] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

not sure how to get this?

[x] No score or internal
[ ] 🥈 Silver
[ ] 🥇 Gold
[ ] 🏆 Platinum

Maybe I misunderstand Influxdb Cloud, but is it not just another place to host influxdb? If so, why do we need a new component?

Agreed, but its build of there new v2 client. Its not just cloud specific, could be used for non cloud instances as well. They have changed the API and released a new client. https://github.com/influxdata/influxdb-client-python.
Could integrate it into the existing component, but the variables are different and if the new library introduces newer functionality then the complexity of keeping a single implementation could get out of hand. Other option is to just call this one influxdb_v2 ?
Open to suggestions?

I think this should be merged into our existing influxdb integration.
Add a configuration option that allows the user to choose between v1/v2 APIs (ideally autodetected of course).


RUMM-3256: Support building with Java 17

What does this PR do?
This PR brings support of running and building the project with Java 17.
NOTE: Plugin artifact still has to emit Java 11 bytecode for the backward compatibility on the customer side.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #162 (ff2e946) into develop (74af2f1) will increase coverage by 0.15%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop     #162      +/-   ##
=============================================
+ Coverage      86.75%   86.90%   +0.15%
- Complexity       178      179       +1
=============================================
  Files             21       21
  Lines            581      580       -1
  Branches          73       73
=============================================
  Hits             504      504
  Misses            48       48
+ Partials          29       28       -1

see 2 files with indirect coverage changes


Fix Cypress Tests

This change is

The Cypress test appears to still be failing in the automated checks. We should probably wait until it passes to review it. Thoughts?

@klappy Yes! I am testing different methods to fix the tests, trying to pin-point the problem. Will pm you when I get it thanks! :)

@klappy done!


MB-11032 estimated weights and progear form added to storybook

Jira ticket for this change
Summary
Zeplin designs
The code changes can be reviewed here: https://602640-114694829-gh.circle-artifacts.com/0/storybook/index.html?path=/story/customer-components-ppm-booking-estimated-weights-and-pro-gear--blank-estimated-weights-pro-gear
Things to call out:

The PR doesn't include upgrades to the latest USWDS and React-USWDS libraries, as this introduced a number of client test errors throughout the front end code. So without the upgrades <InputSuffix> wasn't available so I added the ability for MaskedTextField to display and format a suffix
Because the form styles were similar for this form and the existing DatesAndLocation form, I created a shared scss file called PPMBookingStyles

Setup to Run Your Code

💻 You will need to use three separate terminals to test this locally.
Terminal 1
Start the Storybook locally.
make storybook

Verification Steps for Author
These are to be checked by the author.

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

Verification Steps for Reviewers
These are to be checked by a reviewer.

Frontend

[ ] User facing changes have been reviewed by design.
[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] There are no new console errors in the browser devtools
[ ] There are no new console errors in the test output
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.

Screenshots

Messages

:book:
:link: MB-11032

  Generated by :no_entry_sign: dangerJS against c897f16cadc97d8308eae3fe89347826948f77cd

Thanks for making the other changes! I added a few more comments. Also, I noticed that the zeplin mocks have a PPM badge on the top left that aren't in the component. I'm not sure if it's meant to be at this level, or if that's going to be done at a higher level:

I left this and heading out because I think it should happen at the page level. I updated the AC in the ticket for incorporating this form into a page so that this doesn't get lost https://dp3.atlassian.net/browse/MB-10675

When the field is in an error state, there's some extra space added above the field label that moves all the text down. The error indication line to the left of the field shows blank space as well. Not expected behavior.
(Also shows up in @duncan-truss's #8177)

@scarequotes Thanks for flagging this James, we didn't introduce it but it was definitely a bug 🐛 in our global styles.  I think I have a fix for it here in my PR https://github.com/transcom/mymove/pull/8177/commits/3d3e62e541ffababcd93c71bd97fd709d9e668f3

When the field is in an error state, there's some extra space added above the field label that moves all the text down. The error indication line to the left of the field shows blank space as well. Not expected behavior.
(Also shows up in @duncan-truss's #8177)

@scarequotes Thanks for flagging this James, we didn't introduce it but it was definitely a bug 🐛 in our global styles. I think I have a fix for it here in my PR https://happo.io/a/488/p/603/compare/9931ccdcd4bb66484c2cd4315e149b3f6cceb780/fe57debf2788182ac4b16b2052076e36eb514807. We can double check it doesn't create a bunch of Happo diffs, unless it fixes the problem elsewhere too.

@scarequotes Are you okay with removing the "changes requested" flag from this PR since the UI bug has been fixed in Duncan's PR?


feat: core injected wallet support

Description
Adding Core(Avalanche Core) wallet support in inject wallet
Checklist

[x] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[ ] I have run yarn type-check & yarn build to confirm there are not any associated errors
[ ] This PR passes the Circle CI checks

Thanks for this @itsmnthn. We will review this and get it merged.

@itsmnthn couple small changes requested

@itsmnthn does this PR work on your end? I am not able to get it to work from your fork

@itsmnthn does this PR work on your end? I am not able to get it to work from your fork

I've tried adding custom wallet when initializing onboard check this project https://github.com/itsmnthn/nuxt3-web3-onboard-mvp

@itsmnthn we have reached out to AvaLabs to get the issues with the wallet provider resolved

Closing as Core wallet support has been merged with #1259 and is available with injected-wallet package version 2.2.2-alpha.1


sdk: Remove borsh 0.9 and 0.10

Problem
We've been carrying around borsh 0.9 and 0.10 dependencies for backwards compatibility on things like Pubkey and StakeState.
Summary of Changes
Since the SDK's usage of those dependencies have been deprecated since 1.18 and earlier, remove them since the SDK is on 2.0 and we can do breaking changes.
Fixes #554

Note: setting this as "draft" since I don't know if it'll pass downstream building.

Never mind, Anchor is still on pre v1 versions of borsh, so we'll break them immediately. We'll have to do this differently


"Raw mode" including custom front matter for posts?

Hi there,
is it possible to have some kind of "raw mode" where you can add posts including defining the front matter? currently my post's front matter will be doubled as soon as I publish or unpublish something.
Instead, it should check if there is any header already there and add or replace the published setting.
I'm happy to work on this if it's not there yet.

Hi there @florrablog. I've been slowly trying to revive work on the project and am happy to take a look at this but I think I need some more info/examples as I'm not exactly sure what you're asking for.
Right now you can make a new post via the "New file" button. The front matter defined will depend on your prose configuration in your _config.yml file and can be edited in the metadata panel. If you're editing front matter on an existing file, prose will load those values into the metadata editor where they can be edited.
What exactly is the functionality you're looking for?


Updated 9GAG english description

Updated 9GAG english description to be more accurate.

Hello @stumro ,
This repo is not being maintained anymore, but we are trying to keep it alive on a detached fork here, would you kindly submit your PR there and close this one here? :)


CMP headset is weird

Description

The CMP headset does not have access to squad radio but the normal MP headset does? The CMP radio also has req access for some reason?

You are correct, they are supposed to have the squad radios but by default should be toggle off (we need toggling radio frequencies)

In that case is it also supposed to be there for normal MPs? I don't really understand why MPs need req anyways.

It's not in normal MP (req)

closing because the above PR was merged and should fix this.


Convert custom PyTorch models to IR error

Platform (like ubuntu 16.04/win10): Ubuntu 16.04
Python version: 2.7.14
Source framework with version (like Tensorflow 1.4.1 with GPU): PyTorch 0.4.0
Destination framework with version (like CNTK 2.3 with GPU): IR
Pre-trained model path (webpath or webdisk path): customized PyTorch model
Running scripts: mmtoir -f pytorch -d resnet101 --inputShape 3,224,224 -n imagenet_resnet101.pth
I made some modification to the PyTorch ResNet and tried to convert it to IR, but I got the following errors:
Traceback (most recent call last):
  File "/home/bcheng/anaconda2/bin/mmtoir", line 11, in <module>
    load_entry_point('mmdnn==0.2.3', 'console_scripts', 'mmtoir')()
  File "/home/bcheng/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 192, in _main
    ret = _convert(args)
  File "/home/bcheng/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/_script/convertToIR.py", line 92, in _convert
    parser = PytorchParser(model, inputshape[0])
  File "/home/bcheng/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/pytorch/pytorch_parser.py", line 76, in __init__
    model = torch.load(model_file_name, map_location='cpu')
  File "/home/bcheng/anaconda2/lib/python2.7/site-packages/torch/serialization.py", line 303, in load
    return _load(f, map_location, pickle_module)
  File "/home/bcheng/anaconda2/lib/python2.7/site-packages/torch/serialization.py", line 469, in _load
    result = unpickler.load()
ImportError: No module named models.resnetv1

I tried torch.load('imagenet_resnet101.pth') and it worked fine.
Any suggestions how to convert this model? Thanks!

Hi @bowenc0221 , It's caused by modified class in your model.Please refer to
https://github.com/Microsoft/MMdnn/issues/241
https://github.com/Microsoft/MMdnn/issues/281

It works! Thanks! @namizzz


Update active-directory-whatis azure free details.md

Added self-service password change verbiage to azure ad free description. Studying for AS-900, this was covered on one of the questions, and it's not to be confused with self-service password reset for cloud users. Correction based on table in https://azure.microsoft.com/en-us/pricing/details/active-directory/

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

@kebullen Looking at the pricing chart you referenced, there is no checkmark next to the Self-Service Password Reset for cloud users option under Free. However, @MicrosoftGuyJFlo can you validate this, since you're the licensing guru.

The submitted change was for self-service password change, which is checked in Free. Self-Service password reset, is not checked under Free but is checked under standard and above.
From: Elizabeth Ross<EMAIL_ADDRESS>Sent: Monday, June 24, 2019 2:12 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Kevin Bullen<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update active-directory-whatis azure free details.md (#33876)
@kebullenhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fkebullen&data=02|01|Kevin.Bullen%40microsoft.com|4e9ad7f6f06b4e5ce41d08d6f8cf786f|72f988bf86f141af91ab2d7cd011db47|1|0|636969967296644209&sdata=DPpDAm25U39YwfU9fEQgUsytiXvNcr9CQ09pkR2rZy0%3D&reserved=0 Looking at the pricing chart you referenced, there is no checkmark next to the Self-Service Password Reset for cloud users option under Free. However, @MicrosoftGuyJFlohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftGuyJFlo&data=02|01|Kevin.Bullen%40microsoft.com|4e9ad7f6f06b4e5ce41d08d6f8cf786f|72f988bf86f141af91ab2d7cd011db47|1|0|636969967296644209&sdata=p%2BbOXjsqVnKZkelyu4SWGhDUk11yOnqoLfHcI67RCEo%3D&reserved=0 can you validate this, since you're the licensing guru.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F33876%3Femail_source%3Dnotifications%26email_token%3DAMOBVV46ED7DOUAXMBCPR2TP4EE7PA5CNFSM4H3A7DSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYNYJQY%23issuecomment-505119939&data=02|01|Kevin.Bullen%40microsoft.com|4e9ad7f6f06b4e5ce41d08d6f8cf786f|72f988bf86f141af91ab2d7cd011db47|1|0|636969967296654205&sdata=genZ5EE0AttA5Bg3Op683pvkchWQFj9oeJWSrDzEuFk%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMOBVV2BR3TPTORNYNURNDDP4EE7PANCNFSM4H3A7DSA&data=02|01|Kevin.Bullen%40microsoft.com|4e9ad7f6f06b4e5ce41d08d6f8cf786f|72f988bf86f141af91ab2d7cd011db47|1|0|636969967296654205&sdata=cpFGPNeVgYUOL32m0S3%2BIWvnEwsBRarJjR7PADja%2BN0%3D&reserved=0.

@kebullen  You're correct. I'll go ahead and approve this PR for the change. Thank you for pointing it out!
#sign-off