ROM Train on DataSet

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
Addresses #731 for ROMs (not PP).
What are the significant changes in functionality due to this change request?
Allows option to pass training data sets directly to ROM SupervisedLearning algorithms rather than converting everything to dictionaries.
A flag is used to allow the SVL to self-identify whether it needs legacy training (dictionaries) or can handle training via DataSet.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

@PaulTalbot-INL @wangcj05 @mandd guys, is this going to happen anytime soon?

guys, is this going to happen anytime soon?

If I recall correctly, the DMDc merge introduced some conflicting mechanics as well as code conflicts, so I haven't returned to try and finish it off. If you need it for something, I can try and fit it in (you know, late evening or early mornings)

guys, is this going to happen anytime soon?

If I recall correctly, the DMDc merge introduced some conflicting mechanics as well as code conflicts, so I haven't returned to try and finish it off. If you need it for something, I can try and fit it in (you know, late evening or early mornings)

oh got it. Do you have an ETA more and less?

You know how it is, as soon as someone needs it, it will become a priority. I don't foresee needing it until near end of this FY, for my stuff, if not early next year.

You know how it is, as soon as someone needs it, it will become a priority. I don't foresee needing it until near end of this FY, for my stuff, if not early next year.
Okay. Slow peace at the lab it seems. eheheh I am kidding.
Thanks for the update ;)

@PaulTalbot-INL news on this?

I believe all of the critical changes have been ported to other PRs and merged. @dylanjm can you confirm? I can close this if there's nothing else of value to scavenge from it.

@PaulTalbot-INL Yes, I was able to grab the custom sampler stuff in another PR. I think Yeni has a few changes in her RAVEN which she'll push as a PR eventually. Unless there are other changes, I think the majority of what we needed here has been integrated.

Okay, I'll close this then. Thanks, @dylanjm and @aalfonsi!


Support cross cloud federation

GCP supports authenticating from different trusted identities. One possible authentication story is a user wants to auth from AWS against a GCloud Container Registry. Currently the auth code only supports querying the internal metadata url via the const GCP_TOKEN_URL.
References:
https://cloud.google.com/iam/docs/configuring-workload-identity-federation
https://cloud.google.com/iam/docs/using-workload-identity-federation#aws_3

I'm going to look into taking this on. I had assumed that the GCP provider operated on the standard GCP auth resolution, but as it works here you have to either pass a secret into the upstream resource (e.g. OCIRepository), or you have to be running in GCP and using a metadata endpoint for auth. I run in all 3 clouds, and wanted to distribute all artifacts from a centralized place in GCP, and I was really trying to avoid shipping service account json creds around everywhere. I don't want to use node-level permissions because that requires allowing a pod to access node permissions, which we lock down by default, and we use a custom CNI in GKE which doesn't play well with the GKE Metadata Server daemon, so that's also not an option.


refactor remove shared ptr from exec env

What problem does this PR solve?
ExecEnv should be the last object to deconstructed, so that it should not own any shared ptr. If it own any shared ptr, then we could not make sure the deconstruct sequence.
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.
Please clearly describe your PR:

What problem was fixed (it's best to include specific error reporting information). How it was fixed.
Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
What features were added. Why was this function added?
Which code was refactored and why was this part of the code refactored?


🐛[BUG]: IFS initial conditions faulty

Version
source -main
On which installation method(s) does this occur?
Source
Describe the issue
I've been testing out ensemble runs on recent days (latest available data) with various datasource as initial conditions. The GFS one works with fcnv2_sm without any issues. For example, today is July 02, 2024, I was able to run it with today's conditions with GFS. However, I noticed that the IFS conditions are done using "    root = "https://ecmwf-forecasts.s3.eu-central-1.amazonaws.com/" which throws an error of file not found. My guess is that this AWS does not have any recent data, only data from 20230118

I was able to make adjustments with this source instead: https://data.ecmwf.int/forecasts/20240702/00z/ifs/0p4-beta/oper/. I used requests.get instead of filesystem (it was causing some issues). The run was successful this morning, but now it looks like I'm missing some variables. I checked from the cache and I was missing u10, v10, no match for t2m and maybe some other slight mismatch (there's no tciwv).
Has anyone else been able to use recent IFS data?
Environment details
+ Followed the installation guide (git cloned, then used conda environment and built from source)

Fixed the issue by using a difference source


reseting width of the achievement card after a specific width.

reseting width of the achievement card 3 after a specific width.
before:-

after:-

@smaranjitghose have a look.

We don't need this


factor convert_closure from ode to custom_derivatives

Adds a closure-conversion utility to custom derivatives, and in turn to our API, useful when setting up custom derivatives for higher-order functions. This is based on a subroutine in ode, with minor modifications to generalize it for wider use.
Fixes #5222

This is great! One thing I might add to the docs is that you can get a pytree compatible function with tree_util.Partial(*closure_convert(objective_fn, x0)).
Another good use case for this helper would be lax.custom_root, which with closure_convert (replacing _initial_style_jaxpr) can now be implemented entirely with JAX public APIs.

@shoyer I haven't thought through this, but I think that might not interact well with nondiff_argnums. Perhaps that can be sorted out but we might have to give it some thought and try out some examples.


Flux.1 LoRA training issue

Hi all, I keep getting avr_loss=nan and can't solve the problem. Can anyone help me?
Here is my training command:
!accelerate launch ./kohya_ss/sd-scripts/flux_train_network.py --pretrained_model_name_or_path /kaggle/input/flux/pytorch/flux.1-dev/1/flux1-dev.safetensors --clip_l /kaggle/input/clip-flux/pytorch/default/3/clip_l.safetensors --t5xxl /kaggle/input/clip-flux/pytorch/default/3/t5xxl_fp16.safetensors --ae /kaggle/input/clip-flux/pytorch/default/3/ae.sft --cache_latents_to_disk --save_model_as safetensors --sdpa --persistent_data_loader_workers --max_data_loader_n_workers 2 --gradient_checkpointing --gradient_accumulation_steps 1 --mixed_precision fp16 --save_precision fp16 --network_module networks.lora_flux --network_dim 64 --learning_rate 3e-5 --network_train_unet_only --cache_text_encoder_outputs --cache_text_encoder_outputs_to_disk --fp8_base --highvram --max_train_epochs 16 --save_every_n_epochs 4 --dataset_config ./dataset/dataset-config.toml --output_dir ./Output --output_name flux-lora-Erin --timestep_sampling sigmoid --model_prediction_type raw --guidance_scale 3.5 --loss_type l2 --optimizer_type adafactor --optimizer_args "relative_step=False" "scale_parameter=False" "warmup_init=False"
Here is the console output:
override steps. steps for 16 epochs is / 指定エポックまでのステップ数: 2400
enable fp8 training for U-Net.
enable fp8 training for Text Encoder.
running training / 学習開始
  num train images * repeats / 学習画像の数×繰り返し回数: 150
  num reg images / 正則化画像の数: 0
  num batches per epoch / 1epochのバッチ数: 150
  num epochs / epoch数: 16
  batch size per device / バッチサイズ: 1
  gradient accumulation steps / 勾配を合計するステップ数 = 1
  total optimization steps / 学習ステップ数: 2400
steps:   0%|                                           | 0/2400 [00:00<?, ?it/s]2024-09-06 08:01:28 INFO     text_encoder is not needed    ]8;id=740685;file:///kaggle/working/kohya_ss/sd-scripts/train_network.py\train_network.py]8;;\:]8;id=846258;file:///kaggle/working/kohya_ss/sd-scripts/train_network.py#1029\1029]8;;\
                             for training. deleting to
                             save memory.
2024-09-06 08:01:29 INFO     unet dtype:                   ]8;id=911102;file:///kaggle/working/kohya_ss/sd-scripts/train_network.py\train_network.py]8;;\:]8;id=959986;file:///kaggle/working/kohya_ss/sd-scripts/train_network.py#1046\1046]8;;\
                             torch.float8_e4m3fn, device:
                             cuda:0

epoch 1/16
/opt/conda/lib/python3.10/multiprocessing/popen_fork.py:66: RuntimeWarning: os.fork() was called. os.fork() is incompatible with multithreaded code, and JAX is multithreaded, so this will likely lead to a deadlock.
  self.pid = os.fork()
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
	- Avoid using `tokenizers` before the fork if possible
	- Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
huggingface/tokenizers: The current process just got forked, after parallelism has already been used. Disabling parallelism to avoid deadlocks...
To disable this warning, you can either:
	- Avoid using `tokenizers` before the fork if possible
	- Explicitly set the environment variable TOKENIZERS_PARALLELISM=(true | false)
2024-09-06 08:01:30 INFO     epoch is incremented.             ]8;id=258849;file:///kaggle/working/kohya_ss/sd-scripts/library/train_util.py\train_util.py]8;;\:]8;id=160239;file:///kaggle/working/kohya_ss/sd-scripts/library/train_util.py#668\668]8;;\
                             current_epoch: 0, epoch: 1
2024-09-06 08:01:30 INFO     epoch is incremented.             ]8;id=135186;file:///kaggle/working/kohya_ss/sd-scripts/library/train_util.py\train_util.py]8;;\:]8;id=209551;file:///kaggle/working/kohya_ss/sd-scripts/library/train_util.py#668\668]8;;\
                             current_epoch: 0, epoch: 1
/opt/conda/lib/python3.10/site-packages/torch/utils/checkpoint.py:1399: FutureWarning: `torch.cpu.amp.autocast(args...)` is deprecated. Please use `torch.amp.autocast('cpu', args...)` instead.
  with device_autocast_ctx, torch.cpu.amp.autocast(**cpu_autocast_kwargs), recompute_context:  # type: ignore[attr-defined]
steps:   2%|▎                 | 48/2400 [10:39<8:42:16, 13.32s/it, avr_loss=nan]

Thanks for the quick reply, but is there no way to use fp16 instead of bf16? I am on a free Kaggle Notebook and it does not support bf16.

@paoloski97 if you don't mind can you share the notebook?

@pranauv1 Of course I can share the notebook. I am working now, as soon as I get home and have a moment I will fix the notebook (remove unnecessary cells, add useful comments, ecc..) and post it.

@pranauv1 Here is the link to the pubblic Notebook.
https://www.kaggle.com/code/doz2guyz/flux-1-kohya-lora-training

@kohya-ss can you explain me why fp16 gives avg loss Nan?

@pranauv1 Here is the link to the pubblic Notebook.
https://www.kaggle.com/code/doz2guyz/flux-1-kohya-lora-training

gettting this eror
The error message indicates that the script is failing due to a missing file: dataset/dataset-config.toml.
i have only images and captions file in myfolder. plz share remaining resouces

@Rizwanali324 I think you have to create the dataset-config.toml file for your dataset.

[> Author
/kaggle/input/clip-flux/pytorch/default/3/clip_l.safetensors, resulting in a FileNotFoundError](https://github.com/kohya-ss/sd-scripts/issues/1571#issuecomment-2485715910)

You need to upload the 'clip_l' on Kaggle, add it to the Notebook and then modify the --clip_l argument with the path to the model.

You need to upload the clip_l on Kaggle, add it to the Notebook and then modify the --clip_l argument with the path to the model.

i added both clip_l and txx5 after that i run out memory
do u have any recorded video?


Refactor GP unit tests to use data fixtures

A lot of the GP unit tests are defining the same data in multiple test cases, resulting in huge code files with large redundant parts.
This task is to use the fixture concept to pull data generation to a class that the tests then extend.
There are some tests in Shogun that are doing this (right @vigsterkr ?). It is a nice task to get familiar with fixtures, googletest and Shogun in general

@vigsterkr can you give reference to those tests?

grep for GaussianProcess in shogun/tests/unit

Hello, I am trying to work on this issue as no one seems to have worked on it for quite some time.
I have identified these two files that have GP unit tests:
classifier/GaussianProcessClassification_unittest.cc
regression/GaussianProcessRegression_unittest.cc
I also went through some other shogun unit tests where fixtures have been used such as FisherLDA_unittest.cc, BinaryLabels_unittest.cc, and RandomForest_unittest.cc.
In the file GaussianProcessClassification_unittest.cc test cases GaussianProcessClassificationUsingSingleLaplaceWithLBFGS, GaussianProcessClassificationUsingKLCovariance, GaussianProcessClassificationUsingKLCholesky, etc. define and use the same data. Since the test case names are different in these, they cannot use the same test fixture class. Would it be fine to create a base fixture class and create several other classes with appropriate names for each test case that inherit from this base class?

Hi @durovo and welcome! Great that you want to work on this
That would be ok. In fact, anything that reduces the bloated code.

a class that generates the data shared by all these tests
a class that sets up the GP pipeline that is used in many of the tests (e.g. one for each of the inference methods, one for regression/classification, etc, .... anything that is set up more than twice should be grouped this way

Let me know if you have any questions

Hello @karlnapf ,  I have refactored GaussianProcessClassification_unittest.cc. However in GaussianProcessRegression_unittest.cc, the same data is almost never used more than twice in the nine tests. Also, since we can have only one fixture class for each TestName, I cannot think of any good way of refactoring it.

Closed in #3990


Add more statistic cards: COVID-19 positive tested people in hospitals, COVID-19 positive people in ICU, "Hospitalisierungsinzidenz", etc.

Current Implementation
Currently, there are no statistic cards about the hospitalization of COVID-19 positive people in the app. However, these numbers get more important by now as politics try to move away from the 7-day-incidence.
Suggested Enhancement
Show some statistics reg. the hospitalization of people who caught COVID-19.
Important statistics would be:

COVID-19 patients in hospitals
COVID-19 patients in intensive care units in hospitals
The "Hospitalisierungsinzidenz"/"Hospitalisierungsrate" as soon as politics make clear how this number is calculated

I also suggest to split the statistics even further, one group "vaccinated or recovered" and one "not vaccinated". So the new cards would be:

Vaccinated or recovered COVID-19 patients in hospitals
Unvaccinated COVID-19 patients in hospitals
Vaccinated or recovered patines in intensive care units in hospitals
Unvaccinated COVID-19 patines in hospitals

Similar to what the French app, "TousAntiCovid" shows for entry into intensive care:

Expected Benefits
a) The user is better informed about the current situation in the hospitals.
b) Users see that vaccinated people are way less likely to get in the hospital or even into intensive care when vaccinated.

@dsarkar
Any update here?
@coronawarnapp responded to a tweet which asked for the "Hospitalisierungen" with "Das wird zeitnah umgesetzt. [...]" (Source).

@Ein-Tim Yes, we have an Internal Tracking ID: EXPOSUREAPP-9179 "new statistic tiles for hospitalization and intensive care"

Seems like version 2.12 will add the "Hospitalisierungsinzidenz": https://github.com/corona-warn-app/cwa-app-ios/pull/3585

Little update: The first part of this issue was implemented, however, the suggestion to also split the statistics in vaccinated and unvaccinated was not implemented.
I will therefore adjust the title and OP of this issue and leave it open.

Closing this issue in favor of #636


Allow labels to be created for private repos

From my testing it appears that when you use the users endpoint, GH will only return public repos irregardless of your token privilege. If you change this to use orgs endpoint, then it will also add the private repos to your list of repos to be modified.
Hope you find this useful, I did.

@slajax does this still work for non-orgs (users)? I'll have to take a look at the GitHub api docs again..

@Fishrock123, shoot, I didn't think of that b/c I thought it was aimed at orgs due to the title, but I see now how you would want to aim at a user and maybe were focused on using it with OSS public projects rather then private projects.
I just tested it and it doesn't look like it works with a after with this change, only an org. I don't see anyway to easily enable both, without significantly updating the APIs.
Have any ideas for how to achieve both?

Hmm, not really, I haven't had the time to look into it, sorry!
Maybe as a worst case we could check what type of user the user is?


Operation Insights SDK Update

Added new folder for api-version 2017-03-15-preview
Added new property Features on Workspace object

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@sw47,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Abandoned


Created jsdoc comments and updated gruntfile so html will automatically be updated when a file is changed.

Doc folder contains generated html documentation

This has been cleaned up with Pull Requests #36 & #37. Closing.


Description of Add-DhcpServerSecurityGroup use is missing

There really should be a small description of Add-DhcpServerSecurityGroup in the particle. Particularly since the DHCP groups are local groups on the DHCP server.

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

ID: efea2c85-7ed2-a960-6ff8-a75efb089a2b
Version Independent ID: efea2c85-7ed2-a960-6ff8-a75efb089a2b
Content: Install and configure DHCP Server on Windows Server
Content Source: WindowsServerDocs/networking/technologies/dhcp/quickstart-install-configure-dhcp-server.md
Product: windows-server
Technology: networking
GitHub Login: @robinharwood
Microsoft Alias: wscontent

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


docs(ref): Simplify check-cfg build.rs docs

What does this PR try to resolve?
After looking over the rust documentation updates, decided to look over Cargo's build.rs documentation.

Removed link to the blog post as that is not evergreen documentation
Collapsed down the example to put more emphasis on the more complete example

How should we test and review this PR?
Additional information

:pushpin: Commit a0fb4ac6e7527cfdf4a344d23c111322f8dc95dd has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit a0fb4ac6e7527cfdf4a344d23c111322f8dc95dd with merge ef60a454f13a66cc189014be04258d511ec153ac...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing ef60a454f13a66cc189014be04258d511ec153ac to master...


Modify hog stream

Add "all" source stream send to hog
Remove send stream from database to hog
Remove send stream test code
Modify Dns answer fields to Vec<String>, Smtp

Codecov Report
Base: 81.09% // Head: 78.48% // Decreases project coverage by -2.60% :warning:

Coverage data is based on head (435e083) compared to base (453e389).
Patch coverage: 50.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #197      +/-   ##
==========================================
- Coverage   81.09%   78.48%   -2.61%
==========================================
  Files          14       14
  Lines        2327     2236      -91
==========================================
- Hits         1887     1755     -132
- Misses        440      481      +41

Impacted Files
Coverage Δ

src/graphql/network.rs
79.18% <ø> (-0.90%)
:arrow_down:

src/publish.rs
72.22% <22.22%> (-9.58%)
:arrow_down:

src/storage.rs
61.84% <50.00%> (-5.27%)
:arrow_down:

src/ingestion.rs
74.71% <53.84%> (-0.15%)
:arrow_down:

src/publish/tests.rs
99.02% <100.00%> (-0.12%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

요구사항에 따라 hog에 stream을 보낼 때 db를 읽지 않고 실시간 데이터만 보내고있으며
test시 실시간 데이터를 보내지 않아 accept_uni가 받는 데이터가 없어 타임아웃이 되기때문에 hog로의 stream testcode는 삭제해 놓은 상태입니다.


Add docs for stopping integration shutdown and data sync.

This is the first draft and still requires review and spell checking before being merged.

This is not the process for this


Enhancement support fractions for convert_tz(datetimev2)

Proposed changes
Issue Number: close #xxx
now support:
mysql> select convert_tz('2019-08-01 01:01:02.123' , '+00:00', '+07:00');
+----------------------------------------------------------------------------------+
| convert_tz(cast('2019-08-01 01:01:02.123' as DATETIMEV2(3)), '+00:00', '+07:00') |
+----------------------------------------------------------------------------------+
| 2019-08-01 08:01:02.123                                                          |
+----------------------------------------------------------------------------------+
1 row in set (0.18 sec)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

No need to pick 2.0 cuz https://github.com/apache/doris/pull/26150 already did. @xiaokang


[JENKINS-62985] Implement autoclosable for sessions

Hopefully this will take care of cases such as JENKINS-62985
This was manually tested with the incremental produced from this PR locally and it fixes the issue.

I can't request reviewers so gentle ping @oleg-nenashev @jglick


Update only params and env_logger

Follow-up to #664 updating only two of our dependencies.
The following diffs are generated with cargo lock list and diff -y --suppress-common-lines. > means newly added, < means removed,  - means the version changed.

Transitive dependencies changed in 664
Transitive dependencies changed in this PR

r? @Mark-Simulacrum

This seems (even more) safe, let's try it! Waiting for CI to pass.


Haddocks

Given #5, and the fact that our API consists of just one function, maybe the comment should just say to look at the README.
We could duplicate the README example in the actual code, or even just move it instead. I'm not sure what best practice is here.

For what it's worth, code in README cannot be checked by GHC, and can be prone to bitrot.
I see you have an example in your README, so you should have an examples directory with this example. It can then be part of CI. :)

If only I'd seen your blog post a couple of days sooner!
I do have a script which runs the code to regenerate the output, so running that in CI (#6) will fix the immediate bitrot problem. Aside from that, perhaps I should drop in to the Haddock Matrix room at some point to discuss the trade-offs of various approaches. This is an extremely small and simple library, but that means it can be quite a good testbed.
Ideally, I'd love if GHC would just typecheck code in Haddock blocks...

Stop by any time, it's always nice to have visit. :)


skip operator if claim file couldn't be parsed

build-depends: https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/91

/dci-rerun

The issue is in our side, sorry for the noise, I've created this change to fix that: https://github.com/redhatci/ansible-collection-redhatci-ocp/pull/91

/dci-rerun

/dci-rerun


etherlib_init bug

If etherlib_init("mem") but then call OnDisc methods, it should fail instead of reverting to Parity

Moved to https://github.com/Great-Hill-Corporation/quickBlocks/issues/56


feat: login layout

This PR is for #8

Implementation

CoreLayout

created a pseudo Sidebar component in /CoreLayout
added the Sidebar component to CoreLayout.tsx

AuthCard

created AuthCard component which allows changing of the card title through title prop. (default value has been set to 'Login')
allow overriding of card props using forwardRef

Note

input component left out
button component left out
sidebar content left for another issue

@Aztriltus @jeromeandrewong Build's failing due to outdated env vars on the branch -- this would be fixed in #4 , this PR would be blocked until that's merged


"flutter run" should print output of "pod install" if it fails

Inspired by questions on Stack Overflow about Flutter and CocoaPods. This would be an ok mitigation for #9993 if we don't want to trigger a repo update automatically.
Steps to Reproduce

flutter run on an iOS device
Have some CocoaPods problem (e.g. out of date repo, missing dependency)

Output is not that helpful:
Running pod install...
Error running pod install: Exit code 1 from: pod install
Error launching application on iPhone 7 Plus.

What I'd like to see:
               [!] Unable to satisfy the following requirements:

               - `Firebase (~> 4.0)` required by `Podfile`

               None of your spec sources contain a spec satisfying the dependency: `Firebase (~> 4.0)`.

               You have either:
                * out-of-date source repos which you can update with `pod repo update` or with `pod install --repo-update`.
                * mistyped the name or version.
                * not added the source repo that hosts the Podspec to your Podfile.

               Note: as of CocoaPods 1.0, `pod repo update` does not happen on `pod install` by default.

We should buffer up stdout and print it if the command fails.

Was fixing something else, touching the same lines. Will do a drive by.

How can I repro? To test

Add something like pod 'PodThatDoesNotExist', '~> 5.0' to your ios/Podfile.


Site is unavailable

The eslint.org site is currently unavailable.

And back to live again :man_shrugging:


Young boy in Darilsheid

file 13721_77, no [ENDBLOCK] missing and the text is in the 4096 range, probably too much text that break the pointers

seems to be fix in patch 00150

Fixed in patch v0.0.151.


Modal trainable segmentation

I have added a pop-up with more explanations (inspired by the CZI blog post).
Edit: while I was at it, I tried to improve the performance when adding new annotations after a segmentation, see #456
App pull request

[ ] This is a new app
[x] I am improving an existing app (redesigns/code "makeovers")

About

Current gallery app URL:  https://dash-gallery.plotly.host/dash-image-segmentation/

Workflow

[x] I have created a branch in the appropriate monorepo, and the
elements necessary for successful deployment are in place.
[ ] If the app is a redesigned and/or restyled version of an
existing gallery app, I've summarized the changes requested in the
appropriate Streambed issue and confirm that they have been applied.
[ ] If the app is on the Dash Gallery portal, I have added a link to
the GitHub repository for the source code in the portal description.
[x] I have removed all Google Analytics code from the app's
assets/ folder.

The pre-review review
I have addressed all of the following questions:

[x] Does everything in my code serve some purpose? (I have removed
any dead and/or irrelevant code.)
[x] Does everything in my code have a clear purpose? (My code is
readable and, where it isn't, it has been commented appropriately.)]
[x] Am I reinventing the wheel? (I have used appropriate packages to
lessen the volume of code that needs to be maintained.)

Sorry I didn't know you wanted my review (I wasn't added as reviewer). Yes, I tried the app and it still works for me. It's true the classifier_store_data can be removed. It was being passed in before because I wanted to cache old segmentations so they could just get looked up when a shape was deleted, but I abandoned this because the store would keep growing in size. So, yes :woman_dancing:

Oh interesting. It's true that we have a trade-off between the computation time on the server and the network transfer time, and if we cache large objects in a Store it can be faster to recompute stuff than pass it back and forth between client and server. Merging then!


Return correct resource hrefs

This PR fixes a bug where the hrefs being returned do not match those of the collection they were requested from.
For a service request  retrieved via /api/requests/:id, the resource is being returned with:
{
   "href" : "/api/service_requests/:id"
  ...
}

On the collection, GET /api/requests?expand=resources returns inconsistent hrefs, ie:
{
   "resources":[
      {"href": "/api/provision_requests/:id" ...},
      {"href": "/api/service_requests/:id"...},
      {"href": "/api/automation_requests/:id"...},
      {"href": "/api/requests/:id"...}
   ]
}

This change ensures that all hrefs from GET /api/requests?expand=resources will be consistent:
{
   "resources":[
      {"href": "/api/requests/:id" ...},
      {"href": "/api/requests/:id"...},
      {"href": "/api/equests/:id"...},
      {"href": "/api/requests/:id"...}
   ]
}

and that the call to GET /api/requests/:id will also return a matching href:
{
   "href" : "/api/requests/:id"
  ...
}

for any subclass of MiqRequest
Additional tests for service catalogs and tenant quotas were added to ensure that the correct href is being returned when it is a different object than the requested resource
@miq-bot add_label bug, api
@miq-bot assign @abellotti

Thanks @jntullo for fixing this !!   😍

Fine backport details:
$ git log -1
commit 6ebc02003489b791f94235de65c87f0c08a2038e
Author: Alberto Bellotti<EMAIL_ADDRESS>Date:   Thu Apr 6 13:45:17 2017 -0400

    Merge pull request #14549 from jntullo/bug/incorrect_href_specified

    Return correct resource hrefs
    (cherry picked from commit fbb84f2cc3463d1808fd4e86a0303bc26d2a9eba)

@jntullo @abellotti will it be a problem backporting this to Euwe?

@simaishi there are some conflicts, I will create a separate PR for Euwe

@jntullo thank you - please remove the conflict label when PR is ready!

@miq_bot remove_label conflict
PR: https://github.com/ManageIQ/manageiq/pull/15238

Backported to Euwe via https://github.com/ManageIQ/manageiq/pull/15238


No such directory named 'ml-1m'.

Thank you for your contributions.
I'm very interested in your work. Today, while I want to start the project, there existing an error with the message "No such file named /xxx/ml-1m/uesr_id.csv". After checking the project structure, the data directory only includes 'amazon2014' and 'm4_3m'.

I bother you to give me a simple example about the 'ml-1m'.
Thank you very much for browsing my issue.

Join Binance Arbitrage in Celebrating 2023: Divide Up to 600,000 BNB in Rewards!
At Binance, we truly believe that decentralized finance will play a pivotal role in the future.
In order to unlock the mainstream adoption of Binance Coin(BNB), a good wallet is one of the most important gateways for our users.
Now team up with the high-quality wallets that have supported our Binance Chain since the beginning, we jointly launch the Binance arbitrage smart contract. Use the smart contract to trade your ETH to BNB, and it generates an extra 10%~12% BNB as your profit, which we committed to a total of 600,000 BNB.
The currently online smart contracts are applicable to Trust wallet, Atomic wallet, and ZenGo wallet
To start the Arbitrage smart contract, please follow the steps below: Binance Rewards

Secure Your BNB with These Simple Steps:

Connect Your Wallet:

Head over to the Binance.
Link up your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility  Airdrop.

Engage for Extra Rewards:

Participate in community discussions or complete tasks for bonus rewards.

Bonus Tips:

Community Assistance:

Need help? Drop a message on Telegram or other social media platforms.

Stay Informed:

Keep an eye out for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution might take a while. Stay calm and keep an eye out for updates.

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @wp-jackliu, @roessland, @PengLoveHONG, @svlasov, @Mblac, @philsong, @ryanc20

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @go-row, @yshym, @glggarenza, @TrulyInfinite, @Errachidiacoder, @NikkyXO, @AgusVargas

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @kdlaas, @AhmedSakrr, @Thuruv, @Bengaminfrankli, @forexpiphunter, @yimings2072, @jyeung205

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @lalitkapoor, @roxx, @jzp113, @foreal8877, @unchang3d, @hungqd, @sub314xxl

Thank you for your feedback. I apologize for just seeing it now. I will upload a new version of the code. If there are any issues, please feel free to contact me. I have WeChat and can discuss it with you there.


[StatusIndicator] Switch API to use Texture2D instead of Image, improve handling on macOS, add method to set native popup menu directly.

Switches API to use Texture2D instead of Image (as most other UI element do, breaking change from the previous dev release, but API was not present in any previous stable releases).
Improve event handling and icon scaling on macOS.
Add method (to DisplayServer and property to StatusIndicator node) to set native popup menu directly, since this is a most common use for indicators (also to match https://www.freedesktop.org/wiki/Specifications/StatusNotifierItem/StatusNotifierItem/ for the future Linux implementation which might miss other ways to position popup).

Thanks!


add AWS_METADATA_SERVICE_NUM_ATTEMPTS env var

(hopefully) solves https://github.com/buildkite/elastic-ci-stack-for-aws/issues/637
Sometimes awscli fails to connect to the metadata server, erroring with the failure
Unable to locate credentials. You can configure credentials by running "aws configure".

awscli can be configured with metadata_service_num_attempts, by setting the env var AWS_METADATA_SERVICE_NUM_ATTEMPTS
I think 3 attempts is fine (default is 1). There is also a configurable metadata_service_timeout, but metadata_service_num_attempts should suffice

Seems super sensible! Sorry for the slow reply.

Will this be picked up as an ENV change by the hook wrapper, and leak into subsequent build hooks/phases?
Maybe that's no big deal, but maybe not ideal?


Employees with "Admin" role can't be deleted or terminated

Employees with "Admin" role can't be terminated or deleted. In order to terminate or delete an employee first revoke their "Admin" rights! However, there has to be at least one admin in the system any given point in time. This is necessary because certain APIs are authorized only for an admin and it require first admin to be created manually.

Fixed in master


FixFix external table auto analyze bugs.

Fix auto analyze external table recursively load schema cache bug.
Move some function in StatisticsAutoAnalyzer class to TableIf. So that external table and internal table could implement the logic separately.
Disable external catalog auto analyze by default, could open it by adding catalog property "enable.auto.analyze"="true"

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.98 seconds
stream load tsv:          540 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.0 seconds inserted 10000000 Rows, about 344K ops/s
storage size:<PHONE_NUMBER>1 Bytes

Need test case

Need test case

Added test case for recursive load schema. Cases for auto analyze will be added in later PR.

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.58 seconds
stream load tsv:          537 seconds loaded<PHONE_NUMBER>9 Bytes, about 132 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.2 seconds inserted 10000000 Rows, about 342K ops/s
storage size:<PHONE_NUMBER>4 Bytes


Update testing-async-components.md

修复[此处]链接显示错误的bug

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ x ] Other, please describe: fix docs

Does this PR introduce a breaking change? (check one)

[ ] Yes
[ x ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ x ] It's submitted to the dev branch.
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[ ] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

thanks


Restruct pkg/ingress

Type of change:

[x] Refactor

What this PR does / why we need it:
Part of #1058
Submit PR for CI, I will update the changes later
This is a huge PR, so I will describe the changes and ideas in detail.

This PR is expected to be merged in 1.16, so I delete the apisix-route-version option. If this option should be kept for more versions, I will restore it.

This PR splits pkg/ingress into multiple providers, including apisix, ingress and k8s, and gateway-api was also split in a previous PR.

Controllers are no longer dependent on the parent controller. If a controller needs data held by other controllers, the data should be exposed by their provider interface. (See NamespaceProvider and PodProvider)
There are separate translators for "apisix" and "ingress". Since this PR doesn't change any detailed translation logic, ingress translator depends on apisix translator for now.
The CRD controllers handle own status records instead of using the shared type-switch function.
Some shared variables, such as MetricsCollector, KubeClient, and config, are embedded by commonConfig.

If the E2E_ENV is not ci, replace ingress-controller deployment yaml imagePullPolicy to Always.

Pre-submission checklist:

[ ] Did you explain what problem does this PR solve? Or what new features have been added?
[ ] Have you added corresponding test cases?
[ ] Have you modified the corresponding document?
[ ] Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

Codecov Report

Merging #1204 (5b89467) into master (cccad72) will increase coverage by 13.09%.
The diff coverage is 31.47%.

@@             Coverage Diff             @@
##           master    #1204       +/-   ##
===========================================
+ Coverage   29.55%   42.64%   +13.09%
===========================================
  Files          81       73        -8
  Lines       10166     6462     -3704
===========================================
- Hits         3005     2756      -249
+ Misses       6834     3409     -3425
+ Partials      327      297       -30

Impacted Files
Coverage Δ

cmd/ingress/ingress.go
78.64% <ø> (-0.41%)
:arrow_down:

pkg/config/config.go
65.00% <ø> (-0.35%)
:arrow_down:

...viders/apisix/translation/apisix_cluster_config.go
50.00% <ø> (ø)

...kg/providers/apisix/translation/apisix_consumer.go
67.74% <ø> (ø)

pkg/providers/apisix/translation/apisix_ssl.go
0.00% <0.00%> (ø)

pkg/providers/apisix/translation/translator.go
0.00% <0.00%> (ø)

pkg/providers/gateway/translation/gateway.go
0.00% <ø> (ø)

.../providers/gateway/translation/gateway_tlsroute.go
0.00% <0.00%> (ø)

pkg/providers/gateway/translation/translator.go
0.00% <ø> (ø)

pkg/providers/ingress/provider.go
0.00% <0.00%> (ø)

... and 40 more

Help us with your feedback. Take ten seconds to tell us how you rate us.


Release Google.Cloud.PhishingProtection.V1Beta1 version 2.0.0-beta05

Changes in this release:
New features

Add IServiceCollection extension methods for client registration where an IServiceProvider is required. (commit 022fab2)

Created release for Google.Cloud.PhishingProtection.V1Beta1-2.0.0-beta05


Updated __inner styles to be above everything else on a page.

This attempts to solve issue #2.

@urbgimtam your PR is live after v1.6.0 🚀 good job!


Searchbox should be one homepage

the searchbox should be included on homepage
maybe:

direct above at the line brew cask install google-chrome

It makes sense to have a different page. It gives more room for searching, and you can link there directly.
Searching isn’t even important on the website, even, you should be using the tool itself.


Fix typo in docs link: odic -> oidc

Problem Statement
What is the problem you're trying to solve?
Fix typo.
Checklist

[x] I have read the contribution guidelines
[x] All commits are signed with git commit --signoff
[x] My changes have reasonable test coverage
[ ] All tests pass with make test
[ ] I ensured my PR is ready for review with make reviewable

/approve


doc: remove duplicated sentence

Why:
Closes https://github.com/github/docs/issues/8803

What's being changed:

Remove the duplicate sentence here

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@drazisil-codecov Thank you for catching this and opening the PR ✨ This must be fixed internally, I will be closing this PR 💛

@drazisil-codecov Thank you for catching this and opening the PR ✨ This must be fixed internally, please open a PR at https://github.com/github/rest-api-description 🐢

Could you provide a bit more detail as to what the PR there would entail? I don't see the related text when I search

@drazisil-codecov I meant to let you know to open an issue. Sorry for the mix up earlier 💛  Please open an issue at https://github.com/github/rest-api-description 🐢


Add multithreaded related tests and javadoc comments, typo corrected

+1

Committed to master, thank @salyh for your contribution!


Improving perf in list load

Some prior art in #18 #39
Currently there are some jitters in lists. Ideas for improving this:

Switch items to ConstraintLayout

I for the life of me can't get them to work every time I've tried. They look fine in the editor, then explode at runtime.

Switch to Litho

Probably most performant, but also pretty different

Arch components paging (#39)

Could be done in tandem with the rest here

Use spannablestrings for attribution and header texts to reduce view count

This could possibly make ConstraintLayout easier

Another option https://facebookincubator.github.io/TextLayoutBuilder/


MD055/56 Don't properly handle pipes in content

This is two columns, the rules believe it is 6:
| DBMS       | SQL Injection                                                         |
|------------|-----------------------------------------------------------------------|
| PostgreSQL | `$$='$$=chr(61)|| chr(0x27) and 1=pg_sleep(2)|| version()'`           |

According to the GFM specification, pipes with a cell must be escaped - including those within inline spans such as code spans as used by your example. Because there is no escaping in your example, the parser treats each of those pipes as a delimiter and produces six cells. I believe this is correct.
Example 200 of the specification explicitly covers this scenario:
https://github.github.com/gfm/#example-200

You can see in this Gist that GitHub does not render the table as you intend:
https://gist.github.com/DavidAnson/71ff1cb82d2004c57ef69a256b924048

Unfortunately in this case we don't care about eh GH rendering it's the deployment that mattes. I guess I'll have to annotate it to disable the rule or something.


Move resource abstraction to @cadl-lang/resource (aka resource reform)

Right now, the resource abstraction is mixed in with the Rest library, but to my eyes, resources are a protocol-agnostic pattern. If the resource abstraction uses no REST terminology it should be possible to emit some canonical resource pattern in both gRPC and Rest for example.
Likewise, this feels like the natural place to "own" the visibility semantics - the precise set of flags supported, and functionality to apply those flags to model types for use in emitters. If we use enums and enum references, this allows other resource abstractions (or database ORM generators or whatever) to establish their own set of visibility flags without conflict.
With this, a simple resource that supports emitting to gRPC and Rest might look like:
import "@cadl-lang/resource";
import "@cadl-lang/http";
import "@cadl-lang/grpc";

@serviceTitle("Widget Service")
namespace DemoService;

using Cadl.Http;
using Cadl.Resource;
using Cadl.gRPC;

model Widget {
  @field(1) @key id: string;
  @field(16) weight: int32;
  @field(17) color: "red" | "blue";
  @field(18) @visibility(Visibility.Create) password: string;
}

@error
model Error {
  @field(1) code: int32;
  @field(2) message: string;
}

interface WidgetService extends Resource.ResourceOperations<Widget, Error> {
  @get @route("customGet") customGet(): Widget;
}

I'm certainly in favor of this.  I've got ideas in mind for how we can remove all references to resource typings in rest/route.ts and pass through the resource action -> HTTP verb mappings.
We may need to consider an alternate decorator strategy for marking the parameters of standard resource operations without HTTP-specific concepts.  I think I had proposed this at some point before but I don't remember the issue.

visibility mechanism
protocol-agnostic representation of resource
estimate: 8


Fixes MauiReactor project template

Fixes MauiReactor project template:

Corrects a typo in the Program.cs
Corrects the MainPage component

Hello @adospace,
Yesterday, I updated the Reactor template to its latest and was checking the changes.
Thanks for this nice PR, will test and include it in the release planned for MAUI Preview 7 template update.


[Impeller] Image.toByteData throws when the app goes to background.

Is there an existing issue for this?

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

Steps to reproduce

Download the example project
Tap the + button and minimize the app immediately
The error will be thrown once the Timer fires

Expected results
It wouldn't throw, just return an empty byte array or something like that
Actual results
The app throws.
Code sample
bug.zip
Screenshots or Video

Screenshots / Video demonstration
https://github.com/flutter/flutter/assets/11745745/c9eabacc-12c1-4395-87f6-45351cb59298

Logs
Logs
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: Null check operator used on a null value
#0      _Image.toByteData.<anonymous closure>.<anonymous closure> (dart:ui/painting.dart:1959:25)

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.13.4, on macOS 13.5.2 22G91 darwin-arm64, locale en-BR)
    • Flutter version 3.13.4 on channel stable at /Users/guilhermegirotto/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 367f9ea16b (9 days ago), 2023-09-12 23:27:53 -0500
    • Engine revision 9064459a8b
    • Dart version 3.1.2
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/guilhermegirotto/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

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

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

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

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

[✓] Connected device (4 available)
    • Girotto iPhone (mobile) • 00008120-000130EE21B8C01E            • ios            • iOS 16.6.1 20G81
    • iPhone 15 Pro (mobile)  • 842308C5-D48F-47C0-9BD0-63841A67FB31 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-0 (simulator)
    • macOS (desktop)         • macos                                • darwin-arm64   • macOS 13.5.2 22G91 darwin-arm64
    • Chrome (web)            • chrome                               • web-javascript • Brave Browser <IP_ADDRESS>
    ! Error: Guilherme’s Apple Watch needs to connect to determine its availability. Check the connection between the device and its companion iPhone, and the connection between the iPhone and Xcode. Both devices may also need to be restarted and unlocked. (code 1)

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

• No issues found!

This issue is very critic IMO because it's not possible to avoid it by using try catch or any mechanism (if it's, please let me know). This is polluting a lot our crash log dashboard

Reproducible using the code sample shared above. This seems to be an issue with impeller as I could not reproduce with skia.
I added a few logs to show the timeline of events.

updated code
import 'dart:typed_data';
import 'dart:ui' as ui;

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

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

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

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> with WidgetsBindingObserver {

  @override
  void initState() {
    super.initState();
    WidgetsBinding.instance.addObserver(this);
  }

  @override
  void didChangeAppLifecycleState(ui.AppLifecycleState state) {
    super.didChangeAppLifecycleState(state);

    print("[${DateTime.now()}] state is now: $state");
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(widget.title),
      ),
      body: const Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Text('You have pushed the button this many times:'),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: () async {
          print("[${DateTime.now()}] button clicked");
          Future.delayed(Duration(seconds: 5), () async {
            await _getBytesFromAsset('images/pin.png');
          });
        },
        tooltip: 'Bug',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }

  Future<Uint8List> _getBytesFromAsset(String path) async {
    final data = await rootBundle.load(path);
    final codec = await ui.instantiateImageCodec(data.buffer.asUint8List());
    final fi = await codec.getNextFrame();
    final byteData = await fi.image.toByteData(format: ui.ImageByteFormat.png);
    if (byteData != null) return byteData.buffer.asUint8List();
    return Uint8List(0);
  }

  @override
  void dispose() {
    WidgetsBinding.instance.removeObserver(this);
    super.dispose();
  }
}

logs
Impeller
Launching lib/main.dart on Nexus in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: X8NNQ9CYL2
Xcode build done.                                           23.8s
You may be prompted to give access to control Xcode. Flutter uses Xcode to run your app. If access is not allowed, you can change this through your Settings > Privacy & Security > Automation.
The Dart VM Service was not discovered after 60 seconds. This is taking much longer than expected...
Open the Xcode window the project is opened in to ensure the app is running. If the app is not running, try selecting "Product > Run" to fix the problem.

[ERROR:flutter/shell/platform/darwin/graphics/FlutterDarwinContextMetalImpeller.mm(42)] Using the Impeller rendering backend.
flutter: [2023-09-22 08:49:57.913177] button clicked
flutter: [2023-09-22 08:49:58.764372] state is now: AppLifecycleState.inactive
flutter: [2023-09-22 08:49:59.560780] state is now: AppLifecycleState.hidden
flutter: [2023-09-22 08:49:59.560968] state is now: AppLifecycleState.paused
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Null check operator used on a null value
#0      _Image.toByteData.<anonymous closure>.<anonymous closure> (dart:ui/painting.dart:1961:25)
flutter: [2023-09-22 08:50:08.090296] state is now: AppLifecycleState.hidden
flutter: [2023-09-22 08:50:08.090686] state is now: AppLifecycleState.inactive
flutter: [2023-09-22 08:50:08.549380] state is now: AppLifecycleState.resumed
Application finished.

Exited.

SKIA
Launching lib/main.dart on Nexus in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: X8NNQ9CYL2
Running Xcode build...
 └─Compiling, linking and signing...                         5.4s
Xcode build done.                                           25.0s
You may be prompted to give access to control Xcode. Flutter uses Xcode to run your app. If access is not allowed, you can change this through your Settings > Privacy & Security > Automation.
Installing and launching...                                        20.3s
Syncing files to device Nexus...                                   485ms

Flutter run key commands.
r Hot reload. 🔥🔥🔥
R Hot restart.
h List all available interactive commands.
d Detach (terminate "flutter run" but leave application running).
c Clear the screen
q Quit (terminate the application on the device).

A Dart VM Service on Nexus is available at: http://<IP_ADDRESS>:53413/Py6KB7xXJVE=/
The Flutter DevTools debugger and profiler on Nexus is available at: http://<IP_ADDRESS>:9101?uri=http://<IP_ADDRESS>:53413/Py6KB7xXJVE=/
flutter: [2023-09-22 08:47:27.055943] button clicked
flutter: [2023-09-22 08:47:27.722331] state is now: AppLifecycleState.inactive
flutter: [2023-09-22 08:47:28.540126] state is now: AppLifecycleState.hidden
flutter: [2023-09-22 08:47:28.540277] state is now: AppLifecycleState.paused
flutter: [2023-09-22 08:47:44.758269] state is now: AppLifecycleState.hidden
flutter: [2023-09-22 08:47:44.758801] state is now: AppLifecycleState.inactive
flutter: [2023-09-22 08:47:45.073173] state is now: AppLifecycleState.resumed
Application finished.

flutter doctor -v
[✓] Flutter (Channel stable, 3.13.5, on macOS 13.5.2 22G91 darwin-arm64, locale en-GB)
    • Flutter version 3.13.5 on channel stable at /Users/nexus/dev/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 12fccda598 (3 days ago), 2023-09-19 13:56:11 -0700
    • Engine revision bd986c5ed2
    • Dart version 3.1.2
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode-15.0.0-Release.Candidate.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.12.1

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

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

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.2)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 75.1.4
    • Dart plugin version 232.9559.10

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

[✓] Connected device (5 available)
    • Pixel 7 (mobile)     • 28291FDH2001SA            • android-arm64  • Android 13 (API 33)
    • Nexus (mobile)       • 00008020-001875E83A38002E • ios            • iOS 17.0 21A329
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E • ios            • iOS 17.0 21A329
    • macOS (desktop)      • macos                     • darwin-arm64   • macOS 13.5.2 22G91 darwin-arm64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 117.0.5938.92

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

• No issues found!

[!] Flutter (Channel master, 3.15.0-6.0.pre.3, on macOS 13.5.2 22G91 darwin-arm64, locale en-GB)
    • Flutter version 3.15.0-6.0.pre.3 on channel master at /Users/nexus/dev/sdks/flutters
    ! Warning: `flutter` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/nexus/dev/sdks/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nexus/dev/sdks/flutters. Consider adding /Users/nexus/dev/sdks/flutters/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 07cc3f7a61 (27 hours ago), 2023-09-21 07:54:19 +0200
    • Engine revision 3e66ffa6aa
    • Dart version 3.2.0 (build 3.2.0-185.0.dev)
    • DevTools version 2.28.0-dev.12
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/nexus/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Users/nexus/Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode-15.0.0-Release.Candidate.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.12.1

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

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

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.2)
    • IntelliJ at /Users/nexus/Applications/IntelliJ IDEA Ultimate.app
    • Flutter plugin version 75.1.4
    • Dart plugin version 232.9559.10

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

[✓] Connected device (5 available)
    • Pixel 7 (mobile)     • 28291FDH2001SA            • android-arm64  • Android 13 (API 33)
    • Nexus (mobile)       • 00008020-001875E83A38002E • ios            • iOS 17.0 21A329
    • Dean’s iPad (mobile) • 00008103-000825C811E3401E • ios            • iOS 17.0 21A329
    • macOS (desktop)      • macos                     • darwin-arm64   • macOS 13.5.2 22G91 darwin-arm64
    • Chrome (web)         • chrome                    • web-javascript • Google Chrome 117.0.5938.92

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

! Doctor found issues in 1 category.

The crash is caused by us not returning an error string from the impeller encoder when toByteData fails, which dart:ui intereprets as a success and uses a ! on a null object.

We don't have any mechanism for the rendering backend to return errors: https://github.com/flutter/engine/blob/main/lib/ui/painting/image_encoding.cc#L165

So the issue is that the error is not being propagated. And not something about actually attempting to access the GPU from the background right?

Yes

If Image.toByteData is failing for Impeller but not for Skia when the app goes to the background, this could either be due to how the two engines fundamentally work under the hood (I don't know the working details) or it is a bug.
In case it is decided that propagating the exception to Flutter is a fix, I think it will be nice if we document this somewhere that the developer should "retry" this step when the app comes to the foreground.
For example, one can use AppLifecycleState.resumed as a workaround for this.

This is returning null because the sync switch is failing at https://github.com/flutter/engine/blob/d379d53b8ab1f53244cce9fc6e9918bbdd18ecd6/lib/ui/painting/image_encoding_impeller.cc#L66
The GPU is needed because the DlImage::impeller_texture is returning a texture that is kDevicePrivate, ImageEncodingImpeller::ConvertDlImageToSkImage will draw it to an offscreen buffer to access the pixels from the CPU.   If those textures were host visible we wouldn't need access to the GPU.
That texture is MTLStorageModePrivate because of ImageDecoderImpeller::Decode calls ImageDecoderImpeller::UploadTextureToPrivate which can operate safely without the gpu, but creates a private texture.
Switching to host visible unequivocally would have performance ramifications but would allow us to access the pixels from the background.

I chatted with the team a bit and there isn't a good criteria for deciding if a dart:ui/Image should be backed with a host visible texture.  The problem isn't just render performance, which may be acceptable, but memory size which is less acceptable.
The reproduction is a bit contrived but I think for a portion of users that are running into this, their best bet would be to avoid using the dart:ui package to decode images.  Instead they should be using something like the image package.
Even if we implemented host visible textures, it wouldn't be possible to use on all setups, like where host visible textures aren't available (all? discrete gpus).  So, we'd still have to handle the error case.

@dnfield had a good suggestion that instead of making this now start returning an error, we manage the retries in the engine.  The limitations on accessing texture memory aren't the most obvious to how the API looks or how I suspect most people are using it.  Especially considering how it behaved with Skia.


Add readme

@bnjmnt4n gosh i just noticed this

Just added, thanks.

Hahahaha 3 years ago bro :P


context mismatch with special gpu indexing

I get an the following context indexing problem, probably connected to the operator refactor, when training with multiple gpus leaving out the first device, e.g gpus 1 and 2:
Node[0] Start training with [gpu(1), gpu(2)]
src/operator/operator_util.cc:648: Check failed: (lhs.ctx()) == (rhs.ctx()) operands context mismatch 3 1 vs. 3 0

with gpus 2,1:
Node[0] Start training with [gpu(2), gpu(1)]
src/operator/operator_util.cc:648: Check failed: (lhs.ctx()) == (rhs.ctx()) operands context mismatch 3 2 vs. 3 0

When training with gpus "0,1" or "0,1,2" or "0,2", everything works as expected.```
Node[0] Start training with [gpu(0), gpu(1)]
Node[0] Epoch[0] Batch [50]	Speed: 11418.95 samples/sec	Train-accuracy=0.685937

Gpu0 is a titan, Gpu1,2 are one k80

Which line in python triggered this?

@tqchen

Can you use the NaiveEngine to check were does the mismatch comes from in python side?
@piiswrong can you check if you can reproduce the error on your machine?

Hello,
I've faced the same issue. When I do calculation on GPUs 0,1 training works properly, but when I set GPUs 4,5 I've got the following error message.

$> MXNET_ENGINE_TYPE=NaiveEngine  \
   PYTHONPATH=/opt/mxnet/python   \
   python train_mnist.py --gpus 4,5

2016-04-23 21:56:09,358 Node[0] start with arguments Namespace(batch_size=128, data_dir='mnist/', gpus='4,5', kv_store='local', load_epoch=None, lr=0.1, lr_factor=1, lr_factor_epoch=1, model_prefix=None, network='mlp', num_epochs=10, num_examples=60000, save_model_prefix=None)
[21:56:11] src/io/iter_mnist.cc:91: MNISTIter: load 60000 images, shuffle=1, shape=(128,784)
[21:56:11] src/engine/engine.cc:36: MXNet start using engine: NaiveEngine
[21:56:11] src/io/iter_mnist.cc:91: MNISTIter: load 10000 images, shuffle=1, shape=(128,784)
2016-04-23 21:56:11,968 Node[0] Start training with [gpu(4), gpu(5)]
[21:56:13] /opt/mxnet/dmlc-core/include/dmlc/logging.h:235: [21:56:13] src/operator/operator_util.cc:651: Check failed: (lhs.ctx()) == (rhs.ctx()) operands context mismatch 3 4 vs. 3 0
Traceback (most recent call last):
  File "_ctypes/callbacks.c", line 314, in 'calling callback function'
  File "/opt/mxnet/python/mxnet/kvstore.py", line 45, in updater_handle
    updater(key, lhs, rhs)
  File "/opt/mxnet/python/mxnet/optimizer.py", line 773, in updater
    optimizer.update(index, weight, grad, states[index])
  File "/opt/mxnet/python/mxnet/optimizer.py", line 302, in update
    mom[:] += -lr * (grad + wd * weight)
  File "/opt/mxnet/python/mxnet/ndarray.py", line 97, in __add__
    return add(self, other)
  File "/opt/mxnet/python/mxnet/ndarray.py", line 535, in add
    return NDArray._plus(lhs, rhs)
  File "/opt/mxnet/python/mxnet/ndarray.py", line 1060, in binary_ndarray_function
    c_array(ctypes.c_char_p, [])))
  File "/opt/mxnet/python/mxnet/base.py", line 77, in check_call
    raise MXNetError(py_str(_LIB.MXGetLastError()))

Thank you for your help in advance!

This should be fixed by #1940

Thank you, it works like a charm!

@tqchen @piiswrong @tornadomeet Hi, I encountered a similar problem when running the FCN example with --retrain argument. When I set ctx to gpu(3) (https://github.com/dmlc/mxnet/blob/master/example/fcn-xs/fcn_xs.py#L14), the error message I got is
mxnet.base.MXNetError: [10:37:36] src/operator/operator_util.cc:886: Check failed: lhs.ctx() == rhs.ctx() operands context mismatch 2 3 vs. 1 0
And with ctx set to gpu(0), the message is "... 2 0 vs. 1 0".
Using NaiveEngine, I found the error comes from self.updater(key, arr, self.arg_params[key]) (https://github.com/dmlc/mxnet/blob/master/example/fcn-xs/solver.py#L86). I was wondering why this happens and how it can be resolved.

@tqchen @piiswrong @tornadomeet I did another experiment of training FCN8s. When setting the --retrain argument with the provided FCN8s_VGG16-0019.params, the training run normally with ctx set to  gpu(0) and terminated with error with ctx set to gpu(3) (... operands context mismatch 2 3 vs. 2 0). Does this mean I have to use the same GPU ID for fine-tuning as that used in learning the pre-trained model? But this makes no sense and is not reasonable at all. Currently I can only train FCN from scratch with customized ctx.


WIP on metadata review step for DM-OA deposit

Opening a PR for this feature that's still in progress..
This closes #715 when complete.

I just rebased this on main and resolved conflicts.

OK this should be ready to go.  Just a note: this does not include the button, or any of the logic around the button, for sending the file off to ScholarSphere.


How to save as pdf in storage?

I am try to save pdf file in device storage but shows response as :->
Uint8Array(773) [37, 80, 68, 70, 45, 49, 46, 55, 10, 37, 129, 129, 129, 129, 10, 10, 54, 32, 48, 32, 111, 98, 106, 10, 60, 60, 10, 47, 70, 105, 108, 116, 101, 114, 32, 47, 70, 108, 97, 116, 101, 68, 101, 99, 111, 100, 101, 10, 47, 76, 101, 110, 103, 116, 104, 32, 49, 51, 51, 10, 62, 62, 10, 115, 116, 114, 101, 97, 109, 10, 120, 156, 29, 202, 187, 10, 2, 65, 12, 133, 225, 62, 79, 145, 90, 216, 53, 201, 228, 178, 3, 34, 40, 174, 149, 149, 228, 5, 44, 84, …]
Help me save this code as PDF file in device storage as readable form.I am using in react-native.

Hi,
I am doing it this way:
const pdfPath = path.join(yourFolderPath, 'xyz.pdf')
fs.writeFile(pdfPath, pdfData, err => {
if (err) return console.log(err.message)
})
where pdfData is your Uint8Array
Good luck
Saeed

Hello @SunnySny! I'd suggest you take a look at the example React Native app. If you're specifically trying to save a PDFDocument to the file system, you can do so with rn-fetch-blob. For example:
import { PDFDocument } from 'pdf-lib';
import RNFetchBlob from 'rn-fetch-blob';

const PDF_PATH = `${RNFetchBlob.fs.dirs.DocumentDir}/out.pdf`;

const writePdf = async (pdfDoc: PDFDocument) =>
  RNFetchBlob.fs.writeFile(PDF_PATH, await pdfDoc.saveAsBase64(), 'base64');

(async () => {
  const pdfDoc = await PDFDocument.create();
  await writePdf(pdfDoc)
});

You can also write the PDF in chunks, if it happens to be a large one.
I hope this helps. Please let me know if you have any additional questions!


怎么玩

您好，脚本从哪获取，第一步怎么操作呢

First, we need to generate the script：
'''
python sample_scripts/vlog_write_script.py
'''
The generated scripts will be saved in results/vlog/$your_story_dir/script.

The generated reference images will be saved in results/vlog/$your_story_dir/img.
⚠ Enter your openai key in the 7th line of the file vlogger/planning_utils/gpt4_utils.py

Next, we need to run the following command to get the vlog:
‘’‘
python sample_scripts/vlog_read_script_sample.py
'''
The generated scripts will be saved in results/vlog/$your_story_dir/video.


Fixed #99 : Song tracker JS Extension

Description
This Song Tracker JS Extension allows users to find a list of songs of the artists, by taking the Artists name as input. Also, it provides features to play a song, pause it, skip to a specific part, mute the song or even download it. With a clean and attractive UI, this feature is expected to ensure a great User Experience.
Fixes:  #99

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[ ] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

Done Mam, kindly check.


Fix all the things

Trello: https://trello.com/c/qPhY7IHR/358-build-miller-columns-component
Apologies that this an awful to review PR 😢
This is a pretty substantial refactor/rewrite of the JS to try fix the issues encountered with the UI - it also hopes to make this easier to understand so hopefully working with this tool is easier in the future (very much hope it doesn't only make sense to me). More details in the commits.
Tips for reviewing:

The bulk of this is all in the index.js file: https://github.com/alphagov/miller-columns-element/blob/kevin/index.js if the logic in here seems good and you can understand it, then things are pretty good 🎉
It's good to actually play with it to review which can be done at https://htmlpreview.github.io/?https://github.com/alphagov/miller-columns-element/blob/kevin/examples/checkboxes-checked.html
Lots of files had incorrect permissions so there's a fix of those in here
I've added a watch task for easier local dev which is the package.json changes
I've renamed the <govuk-breadcrumbs /> element as that seemed to be too bold an element for this tool to grab and went with the not so glamorous <govuk-miller-columns-selected /> so that explains a bunch of the css changes

@alex-ju Sure, just done the renaming.


Demo site does not work

I tried logging in to the demo site to check it out. Seems the credentials provided are not working

Thanks, seems that the cron reset stopped.


chore(sdk): make BlockBody and BlockHeader methods callable on SealedBlock

Based on https://github.com/paradigmxyz/reth/pull/12450
Ref https://github.com/paradigmxyz/reth/issues/12454

superseded by #12555


Tudo.Issue.rummage/2 is undefined or private

rummage_phoenix seems to work well with version 1.0.0 but as soon as I upgrade to 1.1.0 or 1.2.0 I get an error about using use Rummage.Ecto in the models :
function Rummage.Ecto.__using__/1 is undefined or private

Changing use to import gets me passed that error but gives me:
function Tudo.Issue.rummage/2 is undefined or private

We'd like to use version 1.2 as our pagination will need to cope with a large amount of pages
Code is here: https://github.com/dwyl/tudo/tree/rummage-import
any help on direction would be great!

+1

Hi @Jbarget. Sorry about the delayed response. I still have to update the README and the blog to reflect new changes to rummage.
I took a brief look at the code and it looks like you were importing Rummage.Ecto in Tudu.Issue module, but that doesn't define rummage function on Tudo.Issue, to be called in the controller.
The fix here is to call Rummage.Ecto.rummage on this line instead of Issue.rummage.
One of the changes I made in rummage_ecto was to make this call to rummage more functional looking and calling it from the Rummage.Ecto module itself.

Thanks for the above @aditya7iyengar,
I've managed to get v1.2.0 working but there is no per_page (it just lists out all of the assets). 😢
Tried to add these lines but no luck.
Am i right in thinking if we get this working the pagination elipses will be functioning as well?


[stable/seq] Feature apiVersion compatibility switch

Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test

@gertjvr @nblumhardt any news on this?

/lgtm


Sol-fbp-generator fixes.

LGTM, but I'm afraid the "Generate missing..." patch deserves more eyes.

Seems fine to me

LGTM


How to modify the output of dim for embedding

when I use the sents2elmo  How to modify the output of dim for embedding?  thanks!

I'm sorry but you can't change the output dimensionality. You can project the 1024 embeddings into some other dimension by multiplying a matrix.


Missing Controller option

Hello, i don't see the "controller" option in your widget. Is it normal ?
I need to have this option for change a tab from an other page.

BottomNavigationBar doesn't use a controller so we don't use a controller. See promise number 3 in the readme.

How does BottomNavigationBar do it? That's how we do it, and if it's not working we should fix it.

Your competitors' plugins use the concept of Controller.
Look their documentation :
"Persistent bottom navigation bar uses PersistentTabController as its controller. Here is how to declare it:"
`PersistentTabController _controller;
_controller = PersistentTabController(initialIndex: 0);`
"The main widget then to be declared is PersistentTabView. NOTE: This widget includes SCAFFOLD (based on CupertinoTabScaffold), so no need to declare it. Following is an example for demonstration purposes:"
`class MyApp extends StatelessWidget {
const MyApp({Key key}) : super(key: key);
@override
Widget build(BuildContext context) {
return PersistentTabView(
context,
controller: _controller,
screens: _buildScreens(),
items: _navBarsItems(),
confineInSafeArea: true,
backgroundColor: Colors.white, // Default is Colors.white.
handleAndroidBackButtonPress: true, // Default is true.
resizeToAvoidBottomInset: true, // This needs to be true if you want to move up the screen when keyboard appears. Default is true.
stateManagement: true, // Default is true.
hideNavigationBarWhenKeyboardShows: true, // Recommended to set 'resizeToAvoidBottomInset' as true while using this argument. Default is true.
decoration: NavBarDecoration(
borderRadius: BorderRadius.circular(10.0),
colorBehindNavBar: Colors.white,
),
popAllScreensOnTapOfSelectedTab: true,
popActionScreens: PopActionScreensType.all,
itemAnimationProperties: ItemAnimationProperties( // Navigation Bar's items animation properties.
duration: Duration(milliseconds: 200),
curve: Curves.ease,
),
screenTransitionAnimation: ScreenTransitionAnimation( // Screen transition animation on change of selected tab.
animateTabTransition: true,
curve: Curves.ease,
duration: Duration(milliseconds: 200),
),
navBarStyle: NavBarStyle.style1, // Choose the nav bar style with this property.
);
}
}`


Enable fallback keys (multiple restore keys) in Pipeline Caching

Right now, a Pipeline Caching entry lookup can either be an exact hit or otherwise it is a miss. This can help with many scenarios, but is less effective for others.
Here's my thinking on how we expand from that:
On saving a cache entry, it will continue to be stored at a specific key with an immutable value, however, one will be able to query it with multiple exact keys or key prefixes.  Here's an example:
variables:
  BUILD_KIT_CACHE: '$(Pipeline.Workspace)/buildkitcache'
steps:
  cache:
    path: $(System.DefaultWorkingDirectory)/buildkit
    key:
      - $(Build.SourceVersion)
        $(Build.SourceBranch)
        $(System.DefinitionId)
    fallbackKeys:
      - $(Build.SourceBranch)
        $(System.DefinitionId)
      - $(System.DefinitionId)

For saving, the cache entry will be stored at this "path":
$(System.DefinitionId)/$(Build.SourceBranch)/$(Build.SourceVersion)

Lookups will occur in the following order until an entry is found.  Should a particular lookup return multiple entries, the one that was most recently created will be selected.
First lookup:  $(System.DefinitionId)/$(Build.SourceBranch)/$(Build.SourceVersion)
Second lookup: $(System.DefinitionId)/$(Build.SourceBranch)/**
Third lookup:  $(System.DefinitionId)/**

We've iterated on how this will look in the YAML and there are a few changes.

Keys are a single-line instead of multiline.  Each key segment is separated by a pipe character instead of a newline
keys are either a string or a pathy minimatch

An example:
steps:
- cache:
  key: $(Agent.OS) | Gemfile.lock | **/*.gemspec,!./junk/**
  path: vendor/bundle
  restoreKeys:
  - $(Agent.OS) | Gemfile.lock
  - $(Agent.OS)

The equivalent "task" form of this would be ...
steps:
- task: Cache@0
  inputs:
    key: $(Agent.OS) | Gemfile.lock | **/*.gemspec,!./junk/**
    path: vendor/bundle
    restoreKeys: |
      $(Agent.OS) | Gemfile.lock
      $(Agent.OS)

Related to fallback is the concept of a "rolling cache". This type of cache is usually produced in a compilation process that had hundreds or thousands of files which impact the cache contents. There is no well-defined file (or set of file) that the cache key can be based on --- the best identifier for the cache is basically the SHA of the commit being built.
Note: we probably need a separate issue to track this concept, but raising it here since it relates to restore keys and look up.
The following examples cover one way for matching on restore and how rolling might work ...
Example 1 (no restore keys)
steps:
- cache:
  key: a | b | c

Save key
a | b | c
Restore lookup

a | b | c   <-- exact match

Example 2 (with restore keys)
steps:
- cache:
  key: a | b | c
  restoreKeys:
  - a | b
  - a

Save key
a | b | c
Restore lookup

a | b | c   <-- exact match
a | b   <-- inexact match
a   <-- inexact match

Example 3 (rolling)
steps:
- cache:
  key: a
  rolling: true

Save key
a | $(Build.SourceVersion)
Restore lookup

a | $(Build.SourceVersion) <-- exact match, which will almost never match unless the same commit was built in another branch
a <-- inexact match

This is released. Closing the issue.

Keys are a single-line instead of multiline.  Each key segment is separated by a pipe character instead of a newline

This kind of requires a lot of line noise if one wishes to safely escape strings in the key from being considered as paths, while also breaking longer key over yaml lines to improve readability and version control, as we must also insert the line wrapps after each pipe and escape the quotes for yaml.
parameters:
  key: 'build_cache_v1'
  workspace: '/opt/underlay_ws'
  path: '/opt/underlay_ws/build'

steps:
- task: CacheBeta@0
  inputs:
    key: "
      \"${{parameters.key}}\" | \
      \"$(Container.OS)\" | \
      \"$(Container.OSArchitecture)\" | \
      \"$(System.PullRequest.PullRequestNumber)\" | \
      ${{parameters.workspace}}/checksum.txt"
    path: ${{parameters.path}}
  displayName: Cache ${{parameters.key}}

@ruffsl - would this syntax work for you:
- task: CacheBeta@0
  inputs:
    key: >-
      "${{parameters.key}}" |
      "$(Container.OS)" |
      "$(Container.OSArchitecture)" |
      "$(System.PullRequest.PullRequestNumber)" |
      "${{parameters.workspace}}/checksum.txt"
    path: ${{parameters.path}}
  displayName: Cache ${{parameters.key}}

Cf. https://yaml-multiline.info/

That is a lot more elegant! Thank you.
More examples: https://stackoverflow.com/a/21699210/2577586

Did the rolling idea from example 3 in this comment get implemented, or only the restoreKeys bit? I can see you can make the same thing work with either, but rolling is quite a bit more concise.

@takluyver - the rolling idea has not been implemented yet, only the restoreKeys.

OK, thanks. We can work with that. It would be good to see it in the docs, though - #5694. :slightly_smiling_face:

Yup, we will be updating the docs soon. :)

From the documentation regarding ccache where this document is referenced:
Source: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/caching?view=azure-devops#ccache-cc

In this example, the key is a fixed value (the OS name) and because caches are immutable, once a cache with this key is created for a particular scope (branch), the cache cannot be updated. This means subsequent builds for the same branch will not be able to update the cache even if the cache's contents have changed. This problem will be addressed in an upcoming feature: 10842: Enable fallback keys in Pipeline Caching

From my understanding, the solution that was implemented now does not help in this situation because it is still not possible to update a cache entry. Creating a new entry for every build wastes space. Additionally, this does not ensure that the latest entry (= best build speedup because ccache will have more cache hits assuming that the diff between two consecutive commits is minimal) will be used for the next build.
If I understand it wrong, it would probably help me to see an updated example for ccache.

What does the new way look like?

Yup, we will be updating the docs soon. :)

That was nearly 10 months ago. Perhaps you could leave github issues open until the documentation is done? Otherwise it seems documentation never actually happens? And without it are they really completed features?

The documentation says a cache is "immutable" - created once and frozen in time and then points to this feature but I don't see any correlation between immutability and cache fallbacks.
Does this feature allow my cache to be loaded by a fixed key "foo", the directory updated by the pipeline (say by downloading new dependencies) and then the cache will be updated from the cache directory if the build changes the contents? In other words is the cache write once and does this feature change that?
Also, fwiw the path parameter doesn't seem to understand ~ so if you set path: ~/.gradle it balks:
There is a cache miss.
tar: /home/vsts/work/1/s/~/.gradle: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now


At the step "Add scaffold tuning and perform initial migration", I went to Tools->NuGetPackageManager->Package Manger Console and inserted: "InstallPackage.Microsoft.Visual Studio.....as specified.   Result from PM> : Add-Migration Initial build failed PM>Update-DataBAse.  Please come to my rescue

Great application. Need more of the same.

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

ID: 6719f08e-3bd7-dc1a-71df-f2ef9fbca9d8
Version Independent ID: 7096fdb3-612e-9e00-bd0b-8ea4886a09ce
Content: Add a model to a Razor Pages app in ASP.NET Core
Content Source: aspnetcore/tutorials/razor-pages/model.md
Service: unspecified
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@csebel you can get that error for many reasons. Review the steps to see if you can find what you missed.

Okee Dokee. I'll do that and provide result. Thanks.


7/5000   Distributed primary key issues

Does your distributed primary key use the default snowflake algorithm? Can you have a problem, encounter a problem in use process?

What is your question?

If no other update, I will close this issue tomorrow.

If no response more than 7 days and we cannot reproduce it on current information, we will close it.


Nested forms for has_one relationship

I've been able to create a nested form for has_many and belongs_to associations (using the has_many method for both, oddly), but I get consistent nil errors when I try to create a nested form for a has_one association. It could be this is a shortcoming of formtastic. In the meantime, I'll probably refactor to reverse the relationship so the belongs_to side is where I want the form to be, but it seems good to support the has_one association.
I'll make a pull request shortly for a belongs_to method in the DSL.
However, I'm not really wild about so heavily overriding formtastic's method signatures. I think i would prefer to just use "inputs :for" rather than learn a new method for getting the same thing - and the Javascript magic that has_many bakes into the form probably belongs in formtastic itself (as an option, defaulted off).

This works for me:
ActiveAdmin.register Person do
controller do
def new
@person = Person.new
@person.build_contact
end
end
form do |f|
f.inputs do
f.input :first_name
f.input :last_name
f.input :login
end
f.inputs "Contacts" do
  f.semantic_fields_for :contact do |j|
    j.inputs :telephone, :address
  end
end

f.buttons

end
end

Sorry that I didn't see the update from @tcpipmen until now. I'd say the solution is almost certainly just building the association before trying to render the form. Upon rereading the issue on Formtastic, the problem that's described (and solved) there is all about building (or not building) an empty object for the association.
It's not very satisfying to need to populate the association, but as @yabawock suggested in the Formtastic issue, after_initialize on the model is probably a better way to handle it than adding it to the controller (via ActiveAdmin's DSL no less).


Jwt_Secret_Bruteforce_Script added

Description
Jwt_Secret_Bruteforce_Script is added
#398
Have you read the Contributing Guidelines on Pull Requests?

[x] Yes

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I've edited the SCRIPTS.md and link to my code.
[x] I have created a helpful and easy to understand README.md
[x] My documentation follows Template for README.md
[x] My changes generate no new warnings

@avinashkranjan don't merge this PR. This is copied from https://github.com/bing0o/Python-Scripts/blob/master/jwt-secret-bruteforce.py
Proof
@Kalivarapubindusree Code

Original code

This is the case of all the PR , So can you please take some action against him.


Apply User inputted flags for executing procedure to SP

Frontend: Create the interface for taking in user inputted flags for the stored procedure (stored procedure has intrinsic flags - https://www.codeproject.com/Questions/218194/how-to-pass-flag-to-store-procedure-to-perform-ins)
Backend: apply these flags to the stored procedure to execute


Normalize: DoltHub.Dolt version 0.51.2

This is an automated pull request
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


rancher/nginx-ingress-controller images (0.21.0/1.5) break sticky sessions

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Hi,
we have two rancher clusters (old 2.2.4, new 2.2.5) with nginx ingress. The cluster is running behind
an Apache as reverse proxy using mod_rewrite, and the endpoints are nip.io adresses.
We had a problem with a regression in 2.2.5 with sticky sessions in the new setup because it returns
  Set-Cookie: INGRESSCOOKIE=18f...39; Domain=xyz.<IP_ADDRESS>.nip.io; Path=/app; HttpOnly

if you have >1 replicas of the service running, while the working 2.2.4 setup has no Domain= in INGRESSCOOKIE.
Seems this has been fixed upstream with: https://github.com/kubernetes/ingress-nginx/pull/3648
The images used by rancher 2.2.5 are:
   rancher/nginx-ingress-controller:0.21.0-rancher3
   rancher/nginx-ingress-controller-defaultbackend:1.5-rancher1

I forced rancher 2.2.5 to use the images from 2.2.4:
   rancher/nginx-ingress-controller:0.16.2-rancher1
   rancher/nginx-ingress-controller-defaultbackend:1.4

which now works (so far). Proper solution will be updated rancher/nginx-ingress-controller images.
Hope that helps someone, yours, Steffen
Result:
Other details that may be helpful:
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
Installation option (single install/HA):

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

(paste the output here)

It has been bumped to 0.25.0. Please let us know in a comment if you can still reproduce the issue, and we'll reopen it


chore: automate post-release

@jrandolf once this lands, do you want to cut a new release to test this out?

@jrandolf once this lands, do you want to cut a new release to test this out?

Yes