Support Django 1.4

What prevents the app to work on Django 1.4? As far as I could see it's all about the customisable AUTH_USER_MODEL, right? If so, it could be done by setting manually with minor changes.
The point is: I am working in a big project based on Django 1.4 so, I'd rather do this effort on adapting it to support 1.4 too than going through the whole project and upgrading it to 1.5 only because of that.

I think the only issue is indeed the custom user model. I started working on this app when 1.5 was the latest release so I kind of just stuck with it.
I don't think that the migrations need to be adapted as these are Django 1.7-style migrations, not South migrations, but it should not do any harm.
Did you test your code with Django 1.4, and if not, could you?

Yes, I tested, but it's actually more behind it. The code relying on "instance._meta.model" is raising an error like "Options" has no attribute "model", which I got no time to investigate any deeper, so, it could be something specific on my project or something to Django 1.4. I gonna check more and respond soon.
Thanks

Well, the thing with "Options" object is actually easy to solve, but migrations is the complicated one.
What do you suggest then? The actual option I have now is to adapt my fork for Djanto 1.4 and remove migrations module from it to let it work. Any better insight?

Can't you just ignore the migrations? Or is South complaining that there is a migrations module, but that the migrations in it are not valid?

Why not use https://github.com/arteria/django-compat for back- and forward compatibility?

@philippeowagner One of the key benefits of this library is the small footprint and lack of dependencies - I like to keep it that way.
Furthermore, to get back on topic about specifically 1.4, I know it is an LTS release and it is still supported by the Django team. However, due to major compatibility issues (in general, not only the ones discussed in this thread) with 1.5, 1.6 and especially 1.7 and 1.8 I am not compelled to backport the library myself. However, the license allows you to fork the project and backport it yourself. I am happy to provide a reference to your backported fork, but I have decided to not include support for 1.4 and Django versions that are currently not supported.
After all, this project is still in development and far from production ready. Considering the amount of time I have available and the progress on this project I simply cannot justify the work.


Adding explicit identity method for use in Query strings

Closes #1158
Includes docs as well as cleaned up some nearby test names

Seems great to me (see my comments, though)!
:+1: from @subvertallchris ?

Ugh, sorry if you guys were waiting on me. Maybe a dumb question but does the node_identity method not provide this?

@subvertallchris I couldn't get access to the node_identity...  If you take the tests in this PR and try and replace identity with node_identity - ex spec/e2e/scope_spec.rb:55:
    before(:each) do
      Person.scope :in_order, -> { order("#{node_identity}.level_num DESC") }
    end

it fails with:
     NameError:
       undefined local variable or method `node_identity' for #<Neo4j::ActiveNode::Scope::ScopeEvalContext:0x007fe4ae948370>
     # ./spec/e2e/scope_spec.rb:56:in `block (4 levels) in <top (required)>'
     # ./lib/neo4j/active_node/scope.rb:70:in `instance_exec'
     # ./lib/neo4j/active_node/scope.rb:70:in `_call_scope_context'
     # ./lib/neo4j/active_node/scope.rb:45:in `block (2 levels) in scope'
     # ./spec/e2e/scope_spec.rb:61:in `block (4 levels) in <top (required)>'

Not sure if it works in some places and not others, but it definitely doesn't work here.

@subvertallchris is out for the week, but I just looked again and this is all fab.  Thanks again so much!


Relax orjson requirements

Summary

It seems that on some platforms orjson 3.6.6 is not available.
https://github.com/openvinotoolkit/datumaro/runs/5836494376?check_suite_focus=true
How to test

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Probably, the reason was in a PyPI failure
https://status.python.org/


Make Draft working as a WIP prefix

The issue was that only the actual title was converted to uppercase, but
not the prefix as specified in WORK_IN_PROGRESS_PREFIXES. As a result,
the following did not work:
WORK_IN_PROGRESS_PREFIXES=Draft:,[Draft],WIP:,[WIP]

One possible workaround was:
WORK_IN_PROGRESS_PREFIXES=DRAFT:,[DRAFT],WIP:,[WIP]

Then indeed one could use Draft (as well as DRAFT) in the title.
However, the link Start the title with DRAFT: to prevent the pull request from being merged accidentally. showed the suggestion in uppercase; so
it is not possible to show it as Draft. This PR fixes it, and allows
to use Draft in WORK_IN_PROGRESS_PREFIXES.
Fixes #19779.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@a9af93c). Click here to learn what that means.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main   #19780   +/-   ##
=======================================
  Coverage        ?   47.28%
=======================================
  Files           ?      957
  Lines           ?   133339
  Branches        ?        0
=======================================
  Hits            ?    63053
  Misses          ?    62617
  Partials        ?     7669

Impacted Files
Coverage Δ

models/pull.go
55.90% <100.00%> (ø)

Continue to review full report at Codecov.

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

You also need to fix GetWorkInProgressPrefix() a few lines below that.

In actuality I think the better solution would be to go to modules/setting/repository.go line 297 and uppercase the WorkInProgressPrefixes just after reading them from the configuration file.

It's better to update the comment or document that is not case sensitive.

In actuality I think the better solution would be to go to modules/setting/repository.go line 297 and uppercase the WorkInProgressPrefixes just after reading them from the configuration file.

I think that would be equivalent to the workaround I mentioned: WORK_IN_PROGRESS_PREFIXES=DRAFT:,[DRAFT],WIP:,[WIP], which works, but then Gitea puts DRAFT instead of Draft into the suggested prefix for Work in Progress. So I think a better solution is the one provided in this PR.

You also need to fix GetWorkInProgressPrefix() a few lines below that.

Excellent point, fixed in 11754a123b4a4da732114efc4cba60a739fdd6a6. This is needed so that the "Remove Draft Prefix" button works. I tested it and it seems to work.

Cool. Thanks...
It would be helpful to update:
https://github.com/go-gitea/gitea/blob/4266bd924bb8fff20271c17f8989b39b04ef6673/custom/conf/app.example.ini#L941
and
https://github.com/go-gitea/gitea/blob/4266bd924bb8fff20271c17f8989b39b04ef6673/docs/content/doc/advanced/config-cheat-sheet.en-us.md?plain=1#L90
To mention that these are matched in a case insensitive manner too. Then I will approve and we can get this merged.

@zeripath I made the changes, good point. Let me know if there is anything else to be done.

make lgtm work

I think it would be appropriate to backport this to 1.16.
If you would like to do this:
In your git repo
## Update your repo
git pull --all

## Checkout a backport branch
git checkout origin/release/v1.16 -b backport-19780-v1.16

## Cherry pick the above commit
git cherry-pick 8720f87

## and fix any conflicts...

## Adjust the commit message to make the first line after the title (and its blank line):
## Backport #19780
git commit --amend

## Push it up
git push certik backport-19780-v1.16

## Then open a PR
xdg-open https://github.com/go-gitea/gitea/compare/release/"$VERSION"...certik:backport-19780-v1.16

## Put it on the v1.16.9 milestone with the label: kind/bug
## And then one of us will add the backport/done label to this.

@zeripath thanks for fixing it up and merging. I backported it here: https://github.com/go-gitea/gitea/pull/19811, it seems I am not allowed to change milestones and labels, so you'll have to do that.


python310Packages.whois: 0.9.20 -> 0.9.21

Changelog: https://github.com/DannyCork/python-whois/releases/tag/0.9.21
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 209220 run on x86_64-linux 1

4 packages built:

dnstwist
home-assistant-component-tests.whois
python310Packages.whois
python39Packages.whois


60

experimental impl

@h1alexbel take a look, please
Here a test impl with "handling" for updates, what you think about it?

Codecov Report
Base: 82.85% // Head: 40.27% // Decreases project coverage by -42.57% :warning:

Coverage data is based on head (10bcba5) compared to base (109da69).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@              Coverage Diff              @@
##             master      #67       +/-   ##
=============================================
- Coverage     82.85%   40.27%   -42.58%
  Complexity       12       12
=============================================
  Files             8        8
  Lines            35       72       +37
  Branches          0        2        +2
=============================================
  Hits             29       29
- Misses            6       43       +37

Impacted Files
Coverage Δ

...ain/java/com/l3r8yj/elegramapi/bot/DefaultBot.java
12.82% <0.00%> (-87.18%)
:arrow_down:

...3r8yj/elegramapi/request/RqWithOffsetTelegram.java
0.00% <0.00%> (ø)

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.

@rultor merge
as test variant with some issues

@rultor merge

@rultor merge

@l3r8yj OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@l3r8yj Done! FYI, the full log is here (took me 1min)


Identity management and digital certs

Discussion 🗣
The issue of identity management and digital certificates were raised recently.
Details can be found here: Cicero Issue #562
TL;DR
There's currently no way to sign an Accord Contract. The assertion is that there should.
Context
All other contract platforms (e.g. DocuSign, Adobe Sign, HelloSign, etc.) have contract signing as a means to confirm all parties have agreed to the terms of the agreement.
Keerthi Thomas recently presented ideas on how identity might be integrated into Accord for digital signing of agreements stored in DLTs.

This could be a "Lab" candidate - under the Apache definition as there is no existing codebase.

Not having this as a part of Accord Project technology seems like a strange omission, and I'm all for us steering in this direction.

Possibly related issues:

Document/File format for Accord Project contracts https://github.com/accordproject/cicero/issues/562
Support for custom resources in Accord Project templates / contracts  https://github.com/accordproject/cicero/issues/598

As per the recent TSC meeting, general plan is to focus on instantiation of an Accord Project contract instance first and then layer digital sigs, digital authorisation on top once instances are in place.

From TSC Meeting: 30-Sep-2021

Recent work by Sanket on digitally signing templates and contract instances is starting to move AP in this direction.
No current obvious digital identity standard or service to integrate with.
Current strategy is to follow through with the work Sanket is doing on SLC file format and signing SLC instances, and then (potentially) augment with digital identity service(s) as the need/requirement arises.


chore: re-enable test:browser task in CI

I think this is blocked by https://github.com/denoland/deno/issues/25847
It currently passes because we published<EMAIL_ADDRESS>and the difference between published package and local packages was removed. I think the same error will happen when someone added a new entrypoint in any package.


Fixed issue #1588 | Easy Issue 2 (Dart)

Pull Request Type
What kind of change does this PR introduce?

Solved an issue/task

What is the current behavior?

Issue Number: https://github.com/fork-commit-merge/fork-commit-merge/issues/1588
What is the new behavior?

A function countLength that counts the length of a string.

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


Implement testerina code coverage

Purpose

Implement code coverage feature along with the testerina report. A json file is generated with a summary of module statutes and coverage information.

To make the report presentable an HTML report will be generated which will be tracked by #21580
Fixes #21084
Fixes #14605
Approach
Code Coverage

Jacoco has been used for analyzing the code coverage of Ballerina source files. The implementation is broken into two parts.

instrumentation of files and generating code coverage information in binary format
Converting the report in to readable format

The first part is done by injecting the jacoco agent.jar in to the process that runs the test suite. This will create a .exec binary file in the target/coverage directory. Required filters are used to avoid instrumenting unnecessary classes.
The second part is implemented using jacoco java APIs since the jacoco reports are not meaningful for Ballerina tests. For this, the generated .exec file is given and based on the source class files, the coverage of Ballerina source files (.bal) is generated.
Report generation runs as another separate process after running the test suite since instrumentation and analysis cannot be done in a single process.
The mapping from java class file to the corresponding ballerina source file happens automatically in Jacoco using the lineNumberTable.

Test Report

As of this PR, the test report is a json file. The file has three main elements, namely, the projectName, the moduleStatus and the modulCoverage(empty if code coverage is not enabled).
Since there are separate processes run for executing tests and generating the code coverage report, separate json files are generated in these processes and later aggregated in to a single report in RunTestsTask#execute metthod.
The final json report is located at target/test_results.json

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[x] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #21581 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #21581   +/-   ##
=======================================
  Coverage   14.72%   14.72%
=======================================
  Files          51       51
  Lines        1399     1399
  Branches      214      214
=======================================
  Hits          206      206
  Misses       1177     1177
  Partials       16       16

Continue to review full report at Codecov.

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


Fixing bug where wizard steps indicator was too narrow in IE11

Before:

After:

@jeff-phillips-18 did you create a PF issue?

LGTM, we should file an issue to get this fixed in patternfly.

This was an intentional implementation decision in PatternFly.  Paging @priley86

@rhamilto yes, I still prefer autoprefixer and think it saves us a ton more effort.
in this case, I have opted to ease the stylint rules to ignore "consecutive-duplicates-with-different-values". This allows us to still add display: flex after display: inline-block for ie11 (which does not support @support blocks like other browsers), and let autoprefixer take care of the prefixing for ie10/11. will this fix work for you?
https://github.com/patternfly/patternfly/pull/645
Out of curiosity, what minimum IE support does your app have these days? Microsoft has ended support for all IE versions except IE11.  It'd be nice to rid ourselves of these IE10 prefixes...and of course I can't wait for the day until we can just say "flex" and use BS4...
https://www.microsoft.com/en-us/windowsforbusiness/end-of-ie-support

in this case, I have opted to ease the stylint rules to ignore "consecutive-duplicates-with-different-values". This allows us to still add display: flex after display: inline-block for ie11 (which does not support @support blocks like other browsers), and let autoprefixer take care of the prefixing for ie10/11. will this fix work for you?
patternfly/patternfly#645

It will.  Thanks, @priley86.

Out of curiosity, what minimum IE support does your app have these days?

We only support 11.


The GroundStateEigensolver is excruciatingly slow on the IBM Quantum Lab

What is the expected enhancement?
Though this may well be a Quantum Lab issue, I'd like to let you comment on it first.
Here is an excerpt of the code from the tutorial here https://qiskit.org/documentation/nature/tutorials/03_ground_state_solvers.html
# Test case 1: real quantum hardware - slower
# vqe_solver = VQEUCCFactory(least_busy(IBMQ.load_account().backends(simulator=False, filters=lambda b: b.configuration().n_qubits >= 4)))

# Test case 2: simulator - faster
vqe_solver = VQEUCCFactory(QuantumInstance(backend=Aer.get_backend("aer_simulator_statevector"), shots=4000))

calc = GroundStateEigensolver(QubitConverter(JordanWignerMapper()), vqe_solver)
molecule = Molecule(geometry=[["H", [0.0, 0.0, 0.0]], ["H", [0.0, 0.0, 0.735]]], charge=0, multiplicity=1)
es_problem = ElectronicStructureProblem(ElectronicStructureMoleculeDriver(molecule, basis="sto3g", driver_type=ElectronicStructureDriverType.PYSCF))

res = calc.solve(es_problem)

When the simulator aer_simulator_statevector is used, the whole thing will be done in 3 seconds.
When the real IBM quantum hardware, e.g., ibmq_bogota from the IBMQ.load_account().backends() is used, one iteration of the solver will take 25 seconds. I am not talking about the time spent on waiting in the queue. The attached screenshot shows the actual running time is too long.

The real quantum hardware is supposed to be much faster than any classical simulators. That is the whole point of using the quantum computers in the IBM Quantum Lab, isn't it?

As far as I know, this is not something we can improve in qiskit-nature but in the whole stack of executing quantum circuits / programs on IBM Quantum. A new metric, Circuit Layer Operation Per Second (CLOPS), to benchmark execution of quantum circuits was introduced by IBM Quantum last year: blog (https://research.ibm.com/blog/circuit-layer-operations-per-second), paper (https://arxiv.org/abs/2110.14108).
You can find CLOPS for IBM Quantum Systems in this page: https://quantum-computing.ibm.com/services?services=systems As CLOPS get improved, you can expect to see shorten execution time for each iteration. You can also test by changing ibmq_bogota (2.3K CLOPS) to ibmq_manila (2.8K CLOPS), which should give you a slightly shorter execution time.

As this is an issue for qiskit-nature, I would suggest to close it.

Thanks, @HuangJunye, for the explanations above. I agree with your comments.
@DevelopDaily you should also keep in mind that you are testing this on a very small system. H2 in the STO-3G basis with the JW mapper results in a 4-qubit Hamiltonian. Thus, the classical solution of this system is indeed very fast.


Setting to disable opening in browser

How do I disable the package from opening the started server in a URL. I use it often to test my APIs via Postman; however, I constantly have to close tab after tab that was opened by the plugin. Can we get an option to disable this feature?

Commit line 146
open href
in file ~/.atom/packages/php-server/lib/php-server.coffee

Added in v0.8.0 :+1:


BIDS-Derivatives compliancy revision

Double-check that the current infrastructure fully supports BIDS-Derivatives:

[ ] Revise BIDS entities and default patterns in the nipreps.json config.
[ ] AROMA metadata key forces acronyms to CamelCase  "aroma_motion_1": {
    "CsfFraction": 0.06,
    "EdgeFraction": 0.44,
    "HighFrequencyContent": 0.09,
    "MaximumRpCorrelation": 0.81,
    "Method": {
      "Name": "ICA-AROMA",
      "Version": "0.4.4-beta"
    },
    "MotionNoise": false
  },

@rciric any chance you can look into this anytime soon?

I have reused the somewhat anecdotical original issue about aroma


Additional lorem function or additional argument for paragraphs of blind text

Description
#lorem(n) currently yields n words of the lorem ipsum blind text as a single paragraph. True text is separated into paragraphs, and presently the only way to reflect this with blindtext is to make multiple calls to #lorem, but as these all output the same text, the resulting blindtext looks unnatural.
an additional optional argument asParagraphs (or named as appropriate according to codebase style) would preserve existing functionality while allowing more natural output for longer passages.
Use Case
It would be useful for blindtexts that are of lengths that would otherwise be split into paragraphs were they written by a person.

Makes sense. In the meantime, you can do something like this:
#let lorem-pars(n, each: 4) = {
  let sentences = lorem(n * each * 30).split(". ")
  range(n)
    .map(i => sentences.slice(i * each, count: each).join(". "))
    .join(parbreak())
}

#lorem-pars(6)

Makes sense. In the meantime, you can do something like this:
#let lorem-pars(n, each: 4) = {
  let sentences = lorem(n * each * 30).split(". ")
  range(n)
    .map(i => sentences.slice(i * each, count: each).join(". "))
    .join(parbreak())
}

#lorem-pars(6)

Don't forget to add back in the full-stop at the end of each paragraph:
#let lorem-pars(n, each: 4) = {
  let sentences = lorem(n * each * 30).split(". ")
  range(n)
    .map(i => sentences.slice(i * each, count: each).join(". ") + [.])
    .join(parbreak())
}


[MINOR] [DOCS] Fix the link to test building info on the wiki

Merged build triggered.

Merged build started.

Test build #32426 has started for   PR 6063 at commit db62018.

LGTM.

Test build #32426 has finished for   PR 6063 at commit db62018.

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

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

Merged build finished. Test PASSed.


Defend/process magic effects for Snatch and Frostball

Assume input data to be provided in data structure to be coordinated with Titos

Working basic version of defendSnatch is stored in https://github.com/phylll/mychs-macro-magic/commit/c1a65d485b2cdf188cb295227873aee259df9feb

Closed via https://github.com/michael-buschbeck/mychs-macro-magic/pull/157


Add Hebrew translation

Fixes (No Issue was open)
Changes proposed in this pull request:

added Hebrew translation including a config with rtl attribute set to true

cc @HospitalRun/core-maintainers

Thank you @morsh for the PR!


Fix issue-684

@sylvanc @jemc I did this intentionally as 2 commits on one branch. They are 2 logically distinct changes but the second depends on the existence of the first.

:+1:
So you don't want these squashed right?

Correct @jemc. Squashing doesn't make sense in this case.

You do know I enjoyed this, right? :smiling_imp:

I'm a very pragmatic person when it comes to squashing. All I want are nice logical commits that will be meaningful it a couple months. And yes, I know you enjoyed it. ;)


Broken Link in README.md

This is the link I found on the bottom of the README.md file in the project root, goes to HTTP 404:
https://github.com/hyperledger-labs/TrustID/blob/master/trustid-sdk/README.md

Fixed


chore(*): add Apache 2.0 license

Description
Add Apache 2.0 license. Include MIT reference for nx
Previously package.json had MIT. Apache 2.0 is similar, but much more verbose and includes a revocation clause against patent trolls. In exchange for not being able to incite software litigation users can now patent derivative works. (At least thats my interpretation).
For most people they function the same. The update is mostly for consistency.
Breaking Changes
None
JIRA Link
DA-460
Checklist

[X] Updated the Readme.md (if required) ?

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@latest dist-tag) :package::rocket:
GitHub release :package::rocket:


Define Default Sort Programmatically

Would be a nice feature to be able to specify a default sort column when the columns are being rendered via an ng-repeat:
Given the following controller
$scope.columns = ['foo', 'bar', 'biz'];
$scope.collection = [
  {
    'foo': 0,
    'bar': 7,
    'biz': 4
  },
  {
    'foo': 2,
    'bar': 9,
    'biz': 3
  },
  {
    'foo': 1,
    'bar': 1,
    'biz': 99
  }
  //, ...
]

Be able to specify 'bar' as the default sort key, as such

      {{ column }}

      {{ row[column] }}

+1. I just came here to look for this option.

+1

In case this helps anyone, this is the workaround I've implemented currently. At some point I'd like to actually write this feature but for now this admittedly hacky solution works.

      {{ column }}

      {{ row[column] }}

Given the controller mentioned in the initial post (I know this shouldn't be in a controller),
var columnHeaderName = $scope.columns[2];
angular.element('#col-header-' + columnHeaderName).click()
// For ascending
// angular.element('#col-header-' + columnHeaderName).click().click()

Hopefully that helps for now.

Hello,
I tried to use ng-attr like
 ng-attr-ts-default="{{isSortable ? '' : undefined}}"
but it doesn't work because all my column are default sorted... :(
I have the same behaviour with ng-attr-ts-criteria

You're setting ng-attr-ts-default to undefined in both conditions of that ternary.

This problem has been bugging me recently on a project I'm implmenting, I have put a pull request in with a fix that does work for me using an ng-attr-ts-default= test.

    {{col}}


There are many small inaccuracies in the segmentation results on my dataset. Could you please provide some suggestions?

Thank you for open sourcing your code!
I trained the model on my own dataset. In my segmentation scenario, I have a class representing over 30 potted plants. the average precision (AP) value for this class is an impressive 0.9. However, upon reviewing the segmentation results, I noticed the presence of many small instances resembling speckles on each potted plant. Could you provide some tuning advice?

Thank you for open sourcing your code! I trained the model on my own dataset. In my segmentation scenario, I have a class representing over 30 potted plants. the average precision (AP) value for this class is an impressive 0.9. However, upon reviewing the segmentation results, I noticed the presence of many small instances resembling speckles on each potted plant. Could you provide some tuning advice?

Hi!
May I please ask you to share the versions of the modules that are working for you? I am getting the error especially for hydra. It seems that the reported versions in environments no longer work. Thanks in advance for your help!

Hi! May I please ask you to share the versions of the modules that are working for you? I am getting the error especially for hydra. It seems that the reported versions in environments no longer work. Thanks in advance for your help!

hydra-core == 1.0.5, maybe you can try offline mode.
environment_mask3d.zip

Hi! May I please ask you to share the versions of the modules that are working for you? I am getting the error especially for hydra. It seems that the reported versions in environments no longer work. Thanks in advance for your help!

hydra-core == 1.0.5, maybe you can try offline mode. environment_mask3d.zip

Many thanks for your great help!

Thank you for open sourcing your code! I trained the model on my own dataset. In my segmentation scenario, I have a class representing over 30 potted plants. the average precision (AP) value for this class is an impressive 0.9. However, upon reviewing the segmentation results, I noticed the presence of many small instances resembling speckles on each potted plant. Could you provide some tuning advice?

Hi!
May I please ask to guide me through how to visualize segmentation results? In fact, following are the content of my visualization folder. However, when I open the .bin files of segmentation in cloud compare it is a huge file for even a very small subset and can not be opened. Thanks in advance for your help.

Thank you for open sourcing your code! I trained the model on my own dataset. In my segmentation scenario, I have a class representing over 30 potted plants. the average precision (AP) value for this class is an impressive 0.9. However, upon reviewing the segmentation results, I noticed the presence of many small instances resembling speckles on each potted plant. Could you provide some tuning advice?

Hi! May I please ask to guide me through how to visualize segmentation results? In fact, the following figure is the content of my visualization folder. However, when I open the .bin files of segmentation in cloud compare it is a huge file for even a very small subset and can not be opened. Thanks in advance for your help.

Based on the generated bin file names, find the code part that stores the point cloud. You need to add the code to save the point cloud and its labels.
In another issue, the author replied about the methods for visualization.

Thank you for open sourcing your code! I trained the model on my own dataset. In my segmentation scenario, I have a class representing over 30 potted plants. the average precision (AP) value for this class is an impressive 0.9. However, upon reviewing the segmentation results, I noticed the presence of many small instances resembling speckles on each potted plant. Could you provide some tuning advice?

Hi! May I please ask to guide me through how to visualize segmentation results? In fact, the following figure is the content of my visualization folder. However, when I open the .bin files of segmentation in cloud compare it is a huge file for even a very small subset and can not be opened. Thanks in advance for your help.

Based on the generated bin file names, find the code part that stores the point cloud. You need to add the code to save the point cloud and its labels. In another issue, the author replied about the methods for visualization.

Thanks a lot for your prompt help!

Thank you for your issues,may I know how your dataset is made, and how to use it?

Thank you for open sourcing your code! I trained the model on my own dataset. In my segmentation scenario, I have a class representing over 30 potted plants. the average precision (AP) value for this class is an impressive 0.9. However, upon reviewing the segmentation results, I noticed the presence of many small instances resembling speckles on each potted plant. Could you provide some tuning advice?

Thank you for your issues,may I know how your dataset is made, and how to use it?

Thank you for your issues,may I know how your dataset is made, and how to use it?

You need to modify the pre-processing code provided by the author based on the format of your own dataset.

Thank you for your issues,may I know how your dataset is made, and how to use it?

You need to modify the pre-processing code provided by the author based on the format of your own dataset.

I tried to change the dataset to my own, but the predicted semantic label is always 1. And the number of points in the saved ply data is always larger than the original one.  I hope to get your response in your busy schedule. Thank you.

Thank you for your issues,may I know how your dataset is made, and how to use it?

You need to modify the pre-processing code provided by the author based on the format of your own dataset.

I tried to change the dataset to my own, but the predicted semantic label is always 1. And the number of points in the saved ply data is always larger than the original one.  I hope to get your response in your busy schedule. Thank you.
Yes, I've also encountered the issue of having more points than the original. My predicted semantics are all correct, it might be due to parameter settings or issues with the dataset preprocessing program.

我尝试将数据集更改为我自己的数据集，但预测的语义标签始终为1。并且保存的层数据中的点数始终大于原始数据集。您遇到过这种情况吗？希望在您百忙之中得到您的回复。谢谢。

Yes, I've also encountered the issue of having more points than the original. My predicted semantics are all correct, it might be due to parameter settings or issues with the dataset preprocessing program.


Lord of the Rings: Return of the King crashes when on foreground.

Describe the bug

Using dxWrapper. The game crashes immediatelly on launch, but if I force it to run in windowed mode and open another window in front of the game window, thus running the game on the background, it works normally. As soon as I bring the game to the foreground, it crashes.
Remix 0.1.1
RTX 3060 Ti
Driver 531.41
Retail version (From CDs)

Attach logs!

NvRemixBridge.log
d3d9.log
The game specific log will be named gamename_d3d9.log

To Reproduce
Steps to reproduce the behavior:

Follow the steps to install the dxWrapper (https://github.com/elishacloud/dxwrapper) and on the configuration file, enable D3d8to9  and on the d3d9 section, enable windowed mode.
Run the game and immediately click away from the game screen.
Hover the mouse over the icon on the task bar, it should show a preview of the game running.
Click on the game icon to bring the game to the foreground, and it should crash.

Expected behavior
The game should open normally without crashing. It would open normally on the initial Portal RTX release, but after the update it stopped working, and both 0.1.1 and 0.1.0 exhibit this behavior.
d3d9.log
dxwrapper-rotk.log
rotk_d3d9.log
NvRemixBridge.log

Using x32dbg I found out that it crashes due to a "Access Violation" Exception. It only occurs when trying RTX remix tho.

Hello! Will you please check on the latest release and let us know if this issue persists? Thank you!

The issue was fixed.

Excellent, thank you for confirming! We'll close this ticket.


TLS state-of-the-art in pump.io. We need to progress!

Hi Evan:
I open this issue with the aims to make evolu the state-of-the-art in pump.io security.
By default pump.io in its standalone mode has a wrong and terrible TLS configuration that  don't follow the latests good practices. The security and privacy of the users is primordial for me, and for that I wrote this patch that aims to help with that.
The patch implement the following:

SSLv3 protocol deactivation to prevent POODLE attack
Improve cipher strength disabling weak ciphers and prefer DHE,EDHE ciphers when nodejs 0.12.x arrive.
Enable SSL session resumption. This boost the TLS session resume and performance overall.
Disable TLS client renegotiation

And here, a small list the would be nice to be in the TODO list.
Desirable:

DANE support
Forbid connections to pump servers with weak RSA keys (<=1024 bits)
Support for Nodejs v0.12.x. This is necessary in order to support Forward Secrecy.
Disallow access via HTTP Plain!!! Only support the creation of HTTPS servers. Its mandatory for any protocol by IETF since a few years ago

Please evan, be aware of the patch and help us to protect our users.
PS.- Edited for fix typos.

Is @evanp still working on pump.io?

If Pump itself doesn't get these types of improvements, this creates incentive for more users to put it behind Nginx, which is something the documentation recommends against.

A side problem is also trust of certificates #786

Closing as this is a super broad issue.
Better cipher suites just got merged into master. You'll need at least Node 0.12 to get decent ones, however.
I'll file followups for the remaining issues.


[todo-mvvm-live] What is "Live" about the todo-*-live versions? They are not using LiveData integration of Room DAO.

I was trying to find a sample that uses LiveData<List<T>> from Room DAO, to show how to use reactive Room DAO which is pretty much the most important feature of Room, but apparently not even the LiveData samples use Room DAO's LiveData integration.
What makes the Live branches special, then?

Thankfully https://github.com/googlesamples/android-architecture-components/blob/1c2af45fa614867a1a40047e2bd4f9b3fe61778e/BasicSample/app/src/main/java/com/example/android/persistence/db/dao/ProductDao.java#L30-L31 will suffice.

They use LiveData and ViewModels (so the lifecycle package).
The official basic sample for Room seems to be using LiveData
https://github.com/googlesamples/android-architecture-components/blob/master/BasicSample/app/src/main/java/com/example/android/persistence/db/dao/CommentDao.java


[Fix #3723] Add new Rails/EnumUniqueness cop.

A new Rails/EnumUniqueness cop which identifies any (presumably accidental) usage of duplicate enum value definitions.
# bad
enum status: { active: 4, archived: 4 }

More details in issue #3723.
This is functional (and tested), but probably not the best approach. I'm open to feedback around any shortcuts / simplifications / alternative approaches / other cops to take inspiration from - specifically around my (somewhat clunky) handling of args passed to enum via RuboCop::Node. I'm also open to alternative names for this cop.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[ ] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

Apart from my small remarks - this has to be rebased.

Thanks Bozhidar; you're the human Rubocop I can only strive to be! 😉
I've addressed all remarks and rebased again. Thanks for reviewing.

Btw, I'm sure if this happens or not, but I'm guessing another problem we can check for is duplicate elements in an array enum - e.g. enum status: [:ala, :bala, :ala].

Good point. Rails at least catches that (albeit indirectly and confusingly) as follows:

/Users/ollie/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/enum.rb:187:in `detect_enum_conflict!': You tried to define an enum named "status" on the model "User", but this will generate a instance method "ala?", which is already defined by another enum. (ArgumentError)

It would make sense to catch at Rubocop stage though. Will enhance this cop when I get a moment.

^ I got a moment.


Privacy group resources

A part of #1216.
This PR is specific to privacy group resources on q2t and p2p app to expose apis for privacy group operations

Codecov Report

Merging #1236 (5d8f724) into master (d6d5b44) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             master    #1236    +/-   ##
==========================================
  Coverage     99.52%   99.52%
- Complexity     3176     3221    +45
==========================================
  Files           488      495     +7
  Lines          9446     9561   +115
  Branches        483      483
==========================================
+ Hits           9401     9516   +115
  Misses            5        5
  Partials         40       40

Flag
Coverage Δ
Complexity Δ

unittests
99.52% <100.00%> (+<0.01%)
0.00 <45.00> (ø)

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

Impacted Files
Coverage Δ
Complexity Δ

.../quorum/tessera/api/PrivacyGroupDeleteRequest.java
100.00% <100.00%> (ø)
5.00 <5.00> (?)

...va/com/quorum/tessera/api/PrivacyGroupRequest.java
100.00% <100.00%> (ø)
11.00 <11.00> (?)

...a/com/quorum/tessera/api/PrivacyGroupResponse.java
100.00% <100.00%> (ø)
12.00 <12.00> (?)

...uorum/tessera/api/PrivacyGroupRetrieveRequest.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

.../quorum/tessera/api/PrivacyGroupSearchRequest.java
100.00% <100.00%> (ø)
3.00 <3.00> (?)

...c/main/java/com/quorum/tessera/p2p/P2PRestApp.java
100.00% <100.00%> (ø)
7.00 <0.00> (ø)

...a/com/quorum/tessera/p2p/PrivacyGroupResource.java
100.00% <100.00%> (ø)
2.00 <2.00> (?)

...a/com/quorum/tessera/q2t/PrivacyGroupResource.java
100.00% <100.00%> (ø)
9.00 <9.00> (?)

...c/main/java/com/quorum/tessera/q2t/Q2TRestApp.java
100.00% <100.00%> (ø)
5.00 <0.00> (ø)

... and 6 more

Continue to review full report at Codecov.

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


Null forgiving operator grammar issues

The approach to specifying the null forgiving operator to prevent x!!! and the like causes some problems, and might be better dealt with as "make it valid in the grammar, but prohibit it in semantic text".
TG2: see Nigel's email about "null_forgiving_expression is either wrong or a lot of work for no gain" for more details.

We agree with the approach. @Nigel-Ecma will create a PR, but may ask for suggestions for how we express "even if parenthesized, it's not valid" (e.g. ((x!))!).

Addressed by #1195


feat: Chatgpt clone added

Fixes Issue🛠

Closes #252
Description👨💻
Added a gpt clone made on mern stack
Checklist✅

[] My code follows the style guidelines of this project
[] I have performed a self-review of my own code
[] I have added demonstration in the form of GIF/video file
[] I am an Open Source Contributor

Screenshots/GIF📷
added in readme

@Kritika30032002 the checks are failing coz codeql file is written wrong, swift is mentioned in it and it is a React repo, I have corrected them in this PR only, the checks won't fail once the Codeql is corrected, repo is all fine , so you can merge it ithout any worries. Thanks for ur time. :)

Thanks for your Valuable contribution.
Don't forget to star the repo.


FileStat.mode always gets the same file permissions bits regardless of real ones

Create file 'testfile.txt' in test project folder and try to set several different file permissions and run the code below. You'll see that FileStat.mode property is the same and equals 666 in oct.
import 'dart:io';
void main() {
  FileStat fileinfo = File('testfile.txt').statSync();
  print((fileinfo.mode & 0x1FF).toRadixString(8));
}

Windows 7 x64, Dart SDK 2.8.0-dev.13.0

I played a bit with my windows machine. I think this is something wrong with _wstat64. statSync will call _wstat64 and return st_mode.
We probably can't do much about that.
My Windows 10 version is 10.0.18362.

Zichang, can you clarify that this is a bug in Windows and maybe link to some advisory about it?

I think it is a bug.  But I didn't find any detailed information on file permissions. These observation came from my experiments.
From _wstat64

Bit mask for file-mode information. The _S_IFDIR bit is set if path specifies a directory; the _S_IFREG bit is set if path specifies an ordinary file or a device. User read/write bits are set according to the file's permission mode; user execute bits are set according to the filename extension.

"execute bits" purely depends on file extension. Regarding read and write, it will always return 666 if file permissions are readable.


POWERLEVEL9K_MODE isn't updated unless I manually source ~/.zshrc

As you can see in this screenshot, I started a new zsh session, then only a second later manually sourced my ~/.zshrc, and it looks drastically different:

I'd be fine with this, except for the fact that if I start another zsh session, the settings are once more reset until I source ~/.zshrc:

What could be going on here?

Also note that this happens on both my terminals, Terminal.app and HyperTerm, so it's not an issue with my terminal emulator.

Most likely you are setting POWERLEVEL9K_MODE after you are loading p9k.  When you resource it is reloading the theme after the setting was set on the first run.

Ok, I'll try this.
On Mon, Aug 15, 2016 at 2:00 PM Robert Jorgenson<EMAIL_ADDRESS>wrote:

Most likely you are setting POWERLEVEL9K_MODE after you are loading p9k.
 When you
resource it is reloading the theme after the setting was set on the first
run.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bhilburn/powerlevel9k/issues/302#issuecomment-239877288,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ5Yr04vtGgfP-5Ik5zkQ8oubwB03Ga6ks5qgKkhgaJpZM4JkDcf
.

Works great, thanks


can't decode multiple times

i try to use jsqrcode on electron application with stream decode, but it just scan only one time, when i start the webcam again it say "qrcode.decode is not a function", i want to know how to use it for multiple times

you only need to call setwebcam() function  after scan success.... i faced same issue and fix it by calling this function after scanning ..

Hi @mwj-1992 How to know when it has successfully scanned one time? I can't figure out which event it fires or how to hook into a successful scan. Please help out here.

Use setInterval to get canvas and pass it to decode function then you can achieve decode multiple times.


Docker grows from 500mb to 2GB memory use in a day with no new containers started

The docker daemon memory use on my machine grows from 500mb to 2GB in a day with no new containers started. This seems to have started with a recent update, and it's wrecking havoc on my production machine. A fix would be appreciated.

Output of docker version:
root@Ubuntu-1510-wily-64-minimal ~ # docker version
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 15:59:07 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 15:59:07 2016
 OS/Arch:      linux/amd64
root@Ubuntu-1510-wily-64-minimal ~ #

Output of docker info:
root@Ubuntu-1510-wily-64-minimal ~ # docker info
Containers: 56
 Running: 3
 Paused: 0
 Stopped: 53
Images: 1362
Server Version: 1.10.3
Storage Driver: btrfs
 Build Version: Btrfs v4.0
 Library Version: 101
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
 Volume: local
 Network: bridge null host
Kernel Version: 4.2.0-34-generic
Operating System: Ubuntu 15.10
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.86 GiB
Name: Ubuntu-1510-wily-64-minimal
ID: 2ILP:SBMD:2NB7:JY7W:YC3K:CYYV:AX5E:FZLB:CON4:3JCT:3GT4:W4PB
WARNING: No swap limit support
root@Ubuntu-1510-wily-64-minimal ~ #

Additional environment details (AWS, VirtualBox, physical, etc.):
Steps to reproduce the issue:

Start a lot of services
Wait 48 hours (let them run, don't stop/start any)
Check excessive memory usage of docker daemon

Describe the results you received:
Absolutely excessive memory usage growth
Describe the results you expected:
Memory usage stays at 500MB
Additional information you deem important (e.g. issue happens only occasionally):
This used to never happen, now it happens always. I pretty much need to restart the docker daemon & with it all my services daily, or the server runs out of memory.

Can you see if the same thing happens on a more recent version, eg 1.12.0?
Also you do not say how you are measuring the memory usage, it would help to see the output of what you are running to make comparisons easier and to see what measure you are using.

I didn't write down the exact numbers because I tried to fix in the situation in kind of a hurry before it ran completely out of memory, right now I'm not so sure I checked the correct column in htop 😕  how about I update this tomorrow if it's actually the docker daemon before anyone wastes their time with a big bug hunt? Sorry about that, I should have checked this more thoroughly before filing. I'll update tomorrow with more accurate numbers and/or close..

Note that Ubuntu Wiley reached EOL recently, and won't receive security updates (not related, just something to pay attention to)

It seems I actually looked at the virtual memory instead of resident memory so this is a misfile, sorry again!


Panic deserializing response when some datacenters return a string instead of an int for OneDrive item field

I've recently started seeing panics from the kiota-serialization-json-go library when attempting to deserialize a response from the user/<userID>/drive/root/delta (user's OneDrive delta) endpoint. The cause of the failure is an item that has had extra information attached to it by OneDrive. Specifically, it seems that some information about the image was populated including the image dimensions. The image orientation appears to have been partially populated in the sense that now it's not nil/null but instead empty. A minimal sample response for the failing item is
{
<EMAIL_ADDRESS>"#microsoft.graph.driveItem",
<EMAIL_ADDRESS>"\"{787C2A2D-DF31-4BAF-9ACC-2FB7D14A4029},1\"",
    "createdDateTime": "2023-06-23T17:52:58Z",
    "id": "01BAFL6LRNFJ6HQMO7V5FZVTBPW7IUUQBJ",
    "lastModifiedDateTime": "2023-06-23T17:52:58Z",
    "name": "woohoo_homer.png",
    "photo": {
        "orientation": ""
    },
    "size": 180589
}

This request had an x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"West US 2","Slice":"E","Ring":"1","ScaleUnit":"002","RoleInstance":"MWH0EPF0009A922"}} header.
When receiving a response for this particular image the library panics trying to cast a string into a float (which is later cast to an int). The relevant stack trace for the failure is
panic: interface conversion: interface {} is *string, not *float64 [recovered]
  panic: interface conversion: interface {} is *string, not *float64

goroutine 51 [running]:
testing.tRunner.func1.2({0x1072a47c0, 0x14000bba960})
  /opt/homebrew/Cellar/go/1.20.3/libexec/src/testing/testing.go:1526 +0x1c8
testing.tRunner.func1()
  /opt/homebrew/Cellar/go/1.20.3/libexec/src/testing/testing.go:1529 +0x384
panic({0x1072a47c0, 0x14000bba960})
  /opt/homebrew/Cellar/go/1.20.3/libexec/src/runtime/panic.go:884 +0x204
github.com/microsoft/kiota-serialization-json-go.(*JsonParseNode).GetFloat64Value(...)
  /go/pkg/mod/github.com/microsoft/kiota-serialization-json-go@v1.0.2/json_parse_node.go:406
github.com/microsoft/kiota-serialization-json-go.(*JsonParseNode).GetInt32Value(0x140006a7718?)
  /go/pkg/mod/github.com/microsoft/kiota-serialization-json-go@v1.0.2/json_parse_node.go:411 +0x9c
github.com/microsoftgraph/msgraph-sdk-go/models.(*Photo).GetFieldDeserializers.func9({0x107d71e80?, 0x140008a6d00?})
  /go/pkg/mod/github.com/microsoftgraph/msgraph-sdk-go@v1.4.0/models/photo.go:170 +0x34
github.com/microsoft/kiota-serialization-json-go.(*JsonParseNode).GetObjectValue(0x140008a6d20, 0x140008b25a8?)
  /go/pkg/mod/github.com/microsoft/kiota-serialization-json-go@v1.0.2/json_parse_node.go:225 +0x368
github.com/microsoftgraph/msgraph-sdk-go/models.(*DriveItem).GetFieldDeserializers.func18({0x107d71e80?, 0x140008a6d20?})
  /go/pkg/mod/github.com/microsoftgraph/msgraph-sdk-go@v1.4.0/models/drive_item.go:283 +0x3c
github.com/microsoft/kiota-serialization-json-go.(*JsonParseNode).GetObjectValue(0x140008a6d60, 0x0?)
  /go/pkg/mod/github.com/microsoft/kiota-serialization-json-go@v1.0.2/json_parse_node.go:225 +0x368
github.com/microsoft/kiota-serialization-json-go.(*JsonParseNode).GetCollectionOfObjectValues(0x140008a76a0?, 0x107d3c4c8)
  /go/pkg/mod/github.com/microsoft/kiota-serialization-json-go@v1.0.2/json_parse_node.go:251 +0x17c
github.com/microsoftgraph/msgraph-sdk-go/drives.(*ItemItemsItemDeltaResponse).GetFieldDeserializers.func1({0x107d71e80?, 0x140008a7660?})
  /go/pkg/mod/github.com/microsoftgraph/msgraph-sdk-go@v1.4.0/drives/item_items_item_delta_response.go:27 +0x3c
github.com/microsoft/kiota-serialization-json-go.(*JsonParseNode).GetObjectValue(0x140008a7680, 0x107d65500?)
  /go/pkg/mod/github.com/microsoft/kiota-serialization-json-go@v1.0.2/json_parse_node.go:225 +0x368
github.com/microsoft/kiota-http-go.(*NetHttpRequestAdapter).Send(0x1400004d400, {0x107d65500?, 0x14000374c90?}, 0x14000606cc0, 0x14000374cf0?, 0x140007e9c70?)
  /go/pkg/mod/github.com/microsoft/kiota-http-go@v1.0.0/nethttp_request_adapter.go:359 +0x294
github.com/microsoftgraph/msgraph-sdk-go/drives.(*ItemItemsItemDeltaRequestBuilder).Get(0x14000374b40, {0x107d65500, 0x14000374c90}, 0x1065abdc8?)
  /go/pkg/mod/github.com/microsoftgraph/msgraph-sdk-go@v1.4.0/drives/item_items_item_delta_request_builder.go:62 +0x104

A coworker and I have been going back and forth trying to debug this and so far we've seen it on requests marked with West US 2 but not West US (we mostly end up hitting those two DCs it seems). Attempts to get other images in OneDrive to have the additional metadata that seems to cause this error have been unsuccessful
Is there any way to gracefully handle this sort of situation?

Thanks for reporting this. While we could add fault tolerance here, the service should honor the contract.
In the service metadata the field is described as Edm.Int16. Per OData conventions, it should never return an empty string.
My suggestion at this point is that you open a support ticket so the service team can investigate and fix this inconsistent payload.

sorry, this got pushed down on the pile of things to do. Unfortunately I got bounced around a few times while trying to find the correct team to contact to get this fixed. We've been able to work around the issue and the original cause of the error (the photo attribute in OneDrive) may have been fixed, but there's no guarantees that we won't hit something similar in the future

thanks for reverting, closing


Extend Typespec definitions

In the ./typespec directory, extend the definitions based on community feedback

[ ] Gather feedback for Typespec definitions

Definitions
blocks.tsp

[ ] any other Buf requirements?

chains.tsp (mainly used as reference to other registries ex: chainId/block/networkId )

[ ] any other ID's required for chain matching?

[ ] CoinGecko? https://www.coingecko.com/en/chains
[ ] CMC?

icons.tsp

[ ] How to implement Dark/Light mode?
[ ] Do we provide single or multiple icons? (Array vs. Object)
[ ] Which image file formats do we allow? (ex: png/jpg only?)
[ ] Do we allow vector images? (svg)

providers.tsp

[ ] which other services are required?
[ ] Any other additional metadata of provider required?

replaced with json-schema in #21


app fizz when we enter value like this

when we enter value like this
_hcLineChartView.xElements = [[NSMutableArray alloc] initWithObjects:@(120),@(120), nil];
_hcLineChartView.yElements = [[NSMutableArray alloc] initWithObjects:@(119),@(119), nil];

Thank in advance.

Hi,
We fixed the problem and updated code. You can test it out and let us know if that fixed your problem.

Thank for update,
when we enter like this then fizz
_hcLineChartView.xElements = [[NSMutableArray alloc] initWithObjects:@(0),@(1), nil];
_hcLineChartView.yElements = [[NSMutableArray alloc] initWithObjects:@(0),@(0), nil];

We are going to test it with that data and if we find it not working we will update it again.

Hi,
We fixed the problem with 0 values. You can try version 1.0.2

Fixed


raidboss: add Ttokrrone (worldboss: Shaaloani)

This is my first attempt at writing one of these so I'm sure there will be issues, but hopefully not too many. I am not sure if the way some callouts are created will work for localization but that can be re-worked.
There is still an issue I am working out with some rare-ish mechanic combos (sand spouts + orbs + tempests, usually if the fight goes really long) but wanted to go ahead and get feedback in case lots of things do have issues.
I also went ahead and made all the errors from testing go away, not sure if I was supposed to? I did lookup/copy the names of mobs in other languages.
I did talk to @wexxlee about working on this, and will hopefully do the other world boss faster than this.

Thanks so much for putting this together!  I'm going to try to give this a run in the next few days (when my availability happens to coincide with the fate being up 😁) and see how it feels in game.

I am going to be going back over more old logs/videos to double check, but this is complete I would say. I have elected to just not deal with the case where the boss rotates before a tempest (incomplete but still helpful callout).
Ttokrrone maybe got more effort than it deserved lol.
Can also share a log, not sure how you would prefer.

(Just approved lint/test workflows to be run; haven't been able to test yet, but hoping to do so in the next day or two.)

You'll need to add 'missingTranslations': true, to the CN translation block.

I was going to add the in combat check to the triggers to match other world boss fates but since the triggers interact a lot, someone dying at the wrong time could cause issues so maybe I just leave them out?
I had also already looked up the translations but I forgot to push it seems.

I was going to add the in combat check to the triggers to match other world boss fates but since the triggers interact a lot, someone dying at the wrong time could cause issues so maybe I just leave them out?

Yeah, given the cross-pollination between the triggers, I think leaving it commented is fine.  Given these fates are not every-hour sort of things, I think it's better to have zone-wide triggers firing during the fate even if the player isn't in combat (e.g. flying in to the battle).  If people happen to be in the zone, not in the fate, have cactbot turned on, and don't like the triggers, they have options for that... 😄


Use list values for requires_system_checks

See the changes in Django 4.1 for https://docs.djangoproject.com/en/dev/releases/4.1/#features-removed-in-4-1.

Can you please add Django 4.1 to the test matrix, so we know it works fine?

@danlamanna I think what @ulgens means is this:
https://github.com/philippbosch/django-extensions/commit/c7aa2c3460e58a0be4e5ebd6967a28dff3063cc6
Would be great if you could add this to this PR. Thank you!

Hello friends, is there a reason this PR isn't merged yet? It's more than two months since @danlamanna opened it and it's a very small change.
Can I do anything to help merge it and release a new  version quicker ?
Thank you

Let's fix the small mypy / linter error :-)

Let's fix the small mypy / linter error :-)
Need type annotation for "requires_system_checks" (hint: "requires_system_checks: List[<type>] = ...")

@trbs done.

Thanks !


Patch: UI improvements

Remove redundant "Home" link from footer
Improve HTML template modularity: Create separate template for common modals
Remove unused import from Python code

Good to go. 🫡


Customize gitmojis URL

I see it is hardcoded here: https://github.com/arvinxx/gitmoji-commit-workflow/blob/7f762dad916f65b15e825af4fd59b14237e19c98/packages/plugin/src/gitmojiCode.ts#L9
Could it also possibly link to a local file?

@aureooms  It's possible i think. Let me think about it.

Thanks!


feat(GraphQL::Batch::SetupMultiplex) use multiplex instrumentation to share a batching context

This patch adds support for a shared batching context when multiple queries are run concurrently. Is it something you're interested in for this gem?
Single queries are still supported because graphql 1.6+ treats Schema#execute as a special case of Schema#multiplex: a multiplex with one query. So it's still covered by instrument(:multiplex,...).

This is awesome! It fixes all the issues I was having integrating graphql-batch with react-apollo. Just chiming in to show interest in getting this merged. Thanks @rmosolgo!


Free translations

saw you talking about translations on Discord, thought I'd help (and the Spanish variables always bothered me)

Thank you very much for your commits.
We still need to test the other translations which will take a while because I'm not at my place but we definitely will take a look at that!


rectangles: Add JSON test data

This is a union of the three existing tests:

https://github.com/exercism/xlua/blob/master/exercises/rectangles/rectangles_spec.lua
https://github.com/exercism/xpython/blob/master/exercises/rectangles/rectangles_count_test.py
https://github.com/exercism/xrust/blob/master/exercises/rectangles/tests/rectangles.rs

Closes https://github.com/exercism/todo/issues/136

ok.

removed spaces before and after the large input test
checked against my solution and rust example solution, everything looks good


logs: Discussion about how to store and search logs

Idea
Use existing software like filebeat and write to Kafka, read the messages with Clickhouse and have a API that converts queries from LogQL to Clickhouse SQL.
Docs
Filebeat Kafka Docs
Potential Table layout:
As we dont want to configure the whole ECS inside clickhouse we would potentially store just the most queried fields as seperate column and the rest inside a Map.
CREATE TABLE libbeat_data
(
    `@timestamp` DateTime64(3) CODEC(Delta(8), ZSTD(1)),
    `message` String CODEC(ZSTD(1)),
    `fields` Array(Map(LowCardinality(String), String)) CODEC(ZSTD(1)),
    INDEX idx_fields_key mapKeys(fields) TYPE bloom_filter(0.01) GRANULARITY 1,
    INDEX idx_fields_value mapValues(fields) TYPE bloom_filter(0.01) GRANULARITY 1
)
ENGINE = MergeTree
PARTITION BY toDate(@timetstamp)
ORDER BY (toUnixTimestamp(@timetstamp))
TTL toDateTime(@timetstamp) + toIntervalDay(3)
SETTINGS index_granularity = 8192, ttl_only_drop_parts = 1

An instance of https://github.com/monogon-dev/vortex is deployed as POC


WIP - Change variable names to keep consistent between jenkins and build scripts

Probably want to hold off till after releases.
Renames:
javaVersion/javaToBuild -> forestName
target_os/os -> operatingSystem

I am not a fan of the naming either. We have never had a concept of just "VERSION" we have had OPENJDK_FOREST_NAME that is of the form "jdk8u" which most closely matches what we use in the Jenkins code hence why I mirrored the name in Jenkins. We also have OPENJDK_CORE_VERSION that is of the form "jdk8", the majority of the scripts use this however -v/--version argument typically takes what the scripts would call a OPENJDK_FOREST_NAME and not a CORE_VERSION.
Think your options here are redefine/rename OPENJDK_FOREST_NAME in the existing scripts, or start using CORE_VERSION jenkins side then add code to add the "u" if needed to build the FOREST_NAME.

Thanks for the details! OPENJDK_FOREST_NAME can also be interesting values like amber.  I wonder if it's better-called something like OPENJDK_SOURCE.  I've set a reminder to myself to look at this properly in the morning after coffee


Make language_strong tests pass dartanalyzer --strong

Right now these tests are disabled in the status file.  Go through and fix the ones that have analyzer errors.  There are 42 of them, plus the ones that are also disabled for ddc.

These tests should be made strong-mode clean (or correct if they are testing strong-mode warnings/errors).
The tests that are failing because package:unittest is not strong-mode clean should be fixed
by changing them to use package:expect or some other light test library, not by changing them
to use package:test, which has too many dependencies to be used in core lib tests.
We haven't yet settled on a best replacement for unittest.
The following lines have been added to the tests/language_strong/language_strong.status file:
[ $compiler == dart2analyzer && $strong ]
async_await_test/02: StaticWarning # Issue 28823
async_await_test/03: StaticWarning # Issue 28823
async_await_test/none: StaticWarning # Issue 28823
async_star_test/01: StaticWarning # Issue 28823
async_star_test/02: StaticWarning # Issue 28823
async_star_test/03: StaticWarning # Issue 28823
async_star_test/04: StaticWarning # Issue 28823
async_star_test/05: StaticWarning # Issue 28823
async_star_test/none: StaticWarning # Issue 28823
bit_operations_test/01: MissingStaticWarning # Issue 28823
bit_operations_test/02: MissingStaticWarning # Issue 28823
bit_operations_test/03: MissingStaticWarning # Issue 28823
bit_operations_test/04: MissingStaticWarning # Issue 28823
closure_side_effect_test: StaticWarning # Issue 28823
constant_type_literal_test/01: MissingCompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/as_operation: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/catch_check: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/is_check: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/new_before_load: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/new_generic2: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/new_generic3: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation1: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation_generic1: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation_generic2: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation_generic3: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation_generic4: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation_null: CompileTimeError # Issue 28823
deferred_constraints_type_annotation_test/type_annotation_top_level: CompileTimeError # Issue 28823
field3a_negative_test: StaticWarning # Issue 28823
interface_inherit_field_test: StaticWarning # Issue 28823
internal_library_test/02: MissingStaticWarning # Issue 28823
main_not_a_function_test/01: MissingStaticWarning # Issue 28823
main_test/03: MissingStaticWarning # Issue 28823
many_named_arguments_test: StaticWarning # Issue 28823
no_main_test/01: MissingStaticWarning # Issue 28823
regress_23089_test: CompileTimeError # Issue 28823
reify_typevar_static_test/00: MissingCompileTimeError # Issue 28823
super_setter_test: StaticWarning # Issue 28823
top_level_non_prefixed_library_test: CompileTimeError # Issue 28823
try_catch4_test: StaticWarning # Issue 28823
try_catch5_test: StaticWarning # Issue 28823


StorageMigrations fails from RWX to RWX DataVolume

What happened:
I try to make use of StorageMigration by following this guide: https://kubevirt.io/user-guide/storage/volume_migration/
Right now the migration gets triggered but then fails with this error message:
Live migration failed error encountered during MigrateToURI3 libvirt api call: virError(Code=84, Domain=10, Message='Operation not supported: use of 'VIR_MIGRATE_PARAM_MIGRATE_DISKS' requires use of 'VIR_MIGRATE_NON_SHARED_DISK' or 'VIR_MIGRATE_NON_SHARED_INC' flag'
What you expected to happen:
The LiveMigration should be successful and the new instance runs on the new DV.
How to reproduce it (as minimally and precisely as possible):

Create two RWX StorageClasses
Create a VM with DataVolumeTemplate which uses one of the StorageClasses
Create a new DV on the other StorageClass
Update the VM spec to use the new DV
LiveMigration should get trigger and fail with the error.

Additional context:
I currently running KubeVirt on main branch version (image tag: 20240911_926edf646) because of this issue here: https://github.com/kubevirt/kubevirt/issues/12519
Environment:

KubeVirt version (use virtctl version): N/A
Kubernetes version (use kubectl version): 1.30.0
VM or VMI specifications:

apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  labels:
    kubevirt.io/vm: vm-dv
  name: vm-dv
spec:
  updateVolumesStrategy: Migration
  dataVolumeTemplates:
    - metadata:
        creationTimestamp: null
#        name: src-dv
        name: dst-dv
      spec:
        storage:
          accessModes:
            - ReadWriteMany
          volumeMode: Block
          resources:
            requests:
              storage: 10Gi
          storageClassName: sc-san-standard
        source:
          http:
            url: http://<IP_ADDRESS>/jammy-server-cloudimg-amd64.img
  runStrategy: "Always"
  template:
    metadata:
      labels:
        kubevirt.io/vm: vm-dv
    spec:
      domain:
        devices:
          disks:
            - disk:
                bus: virtio
              name: datavolumedisk1
          interfaces:
            - masquerade: {}
              name: default
        resources:
          requests:
            memory: 128Mi
      terminationGracePeriodSeconds: 0
      volumes:
        - dataVolume:
#            name: src-dv
            name: dst-dv
          name: datavolumedisk1
      networks:
        - name: default
          pod: {}

Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): Ubuntu 24.04 LTS
Kernel (e.g. uname -a): Linux 6.8.0-40-generic
Install tools: N/A
Others: N/A

/assign

I wonder how this works with RXO, as RWX is required for the LiveMigration no?

I wonder how this works with RXO, as RWX is required for the LiveMigration no?

Libvirt is able to copy the storage while migrating the VM. For "regular" migration we don't copy the storage on PVCs, but for volume migration we mark the volumes affected by the changed to be migrated. In this way, libvirt should fully copy them to the destination independently if they are shareable or local.
The details are explained in the design proposal.

The only combination where StorageMigration worked for me is RWX to RWO.
From RWO to RWO is not possible as LiveMigration requires RWX volumes and the migration has not even gotten started.

RWO to RWO should work since it is the combination we have in the tests. Please, paste the error message

hehe.. You are right RWO to RWO is working if the migration gets triggered automatically by relying on vmRolloutStrategy: LiveUpdate. RWO to RWO is not possible using the virtctl because there it checks that all PVCs are RWX.
my virtctl version is:
Client Version: version.Info{GitVersion:"v1.3.0", GitCommit:"6a4481910c353dc43be36fd1c9a4444ad701d0b7", GitTreeState:"clean", BuildDate:"2024-07-17T15:19:15Z", GoVersion:"go1.22.2 X:nocoverageredesign", Compiler:"gc", Platform:"linux/amd64"}

I got the same error locally, checking the reason

@oujonny this should fix the issue once merged: https://github.com/kubevirt/kubevirt/pull/12818


[Bug]: When creating a DLM table, the table structure synchronization task is not enabled. The task details show that the table structure synchronization is enabled by default.

ODC version
ODC430
OB version
Oceanbase430
What happened?
When creating a DLM table, the table structure synchronization task is not enabled. The task details show that the table structure synchronization is enabled by default.

What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?

Create a table structure synchronization task without enabling it
View task details after creation is complete

Anything else we need to know?
No response

Fixed In Commit fb421a7aef014523b01e66fbc0b9c6b0c88d9922
------
畅晚
Mon May 27 16:36:22 2024 +0800


Express.js example missing

The examples README.md points to a non-existing express.js example: https://github.com/open-telemetry/opentelemetry-js/blame/main/examples/README.md#L19
Considering that Express.js is the most widely used Node.js web application framework, I feel like that example should definitely be present.
Cheers :)

It was moved to the contrib repo https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/examples/express
The examples readme should be updated to remove it and to point to the contrib repo for additional examples.

@dyladan
Can I correct this link? and raise a PR?(If allowed, you can assign to me).

Here is the PR with changes #2437, Please have a look.


Windows Installation needs updated to use Git for Windows

The windows installation is still using msysgit 1.9.5 which is now deprecated (Per https://github.com/msysgit/msysgit/commit/088d25f31e34544c90a3c3f7342ea424333f2805).  The current release of Git for Windows is v 2.5.

https://github.com/jssjr/git/pull/80
if you have a vagrant file locally, would you mind testing it? @kbaltrinic

Sorry I never got around to testing, but I see its been merged.  Thanks for the quick turnaround.

Thanks for confirming @kbaltrinic. Closing this issue.


Add x509(1) reference

Quick fix, add missing x509(1) reference.

Where are we with this PR?

Agree, in master L<a|a> should be written as just L


Add support for RESP3

In case anybody is interested in picking that up, some people implemented a resp3 parser: https://github.com/hverlin/redis/blob/main/src/parser/parser.v3.ts


Want to work on FAQ page .

Please assign this to me @PiyushKalyanpy

Thank you @Smita-Maurya  for your suggestion and interest in Gyanaguru project, this issue is already assigned to another contributor.

No issues.
Thank you for your response.
On Mon, 29 May, 2023, 9:07 pm Piyush Kalyan, @.***>
wrote:

Thank you @Smita-Maurya https://github.com/Smita-Maurya for your
suggestion and interest in Gyanaguru project, this issue is already
assigned to another contributor.
—
Reply to this email directly, view it on GitHub
https://github.com/PiyushKalyanpy/GyanaGuru/issues/169#issuecomment-1567284685,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AY54HFKCHFW73GUTZB5E4JDXIS7FHANCNFSM6AAAAAAYPFPA2U
.
You are receiving this because you were mentioned.Message ID:
@.***>


Fixes #4879 - removes manual next article buttons

Whoops!
There were 161 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L24 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L27 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L30 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L32 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L34 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L38 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L40 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L42 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L44 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L46 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L48 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L50 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L53 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L57 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L61 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L63 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L66 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L72 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L75 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L85 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L90 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L93 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/adding-interactivity-with-javascript.md#L95 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L18 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L20 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L22 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L30 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L33 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L35 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L43 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L45 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L47 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L49 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L54 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L57 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L60 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L70 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L74 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L75 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L77 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L79 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L89 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L91 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L94 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L97 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L107 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L112 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L115 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L119 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L121 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L127 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L130 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L133 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L137 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L142 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L145 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L149 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L154 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L155 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L156 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L166 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L171 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L174 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L176 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L180 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L186 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L188 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L191 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L194 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L201 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L202 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L204 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L209 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L212 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L214 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/analyzing-crp.md#L216 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L12 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L17 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L19 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L25 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L28 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L30 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L34 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L35 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L36 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L37 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L41 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L43 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L47 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L49 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L51 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L55 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L58 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L61 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L63 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L67 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L71 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L73 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L75 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L77 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/constructing-the-object-model.md#L81 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/index.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/index.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/index.md#L31 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L59 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L68 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L69 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L76 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L80 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L87 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L90 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L92 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/measure-crp.md#L96 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md#L22 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md#L24 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md#L26 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md#L31 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/optimizing-critical-rendering-path.md#L33 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L17 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L40 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L42 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L44 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L54 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L56 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L68 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L69 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L70 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-blocking-css.md#L72 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L5 - WF Tag wf_updated_on must be within the last 7 days.
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md - No wf_blink_components field found in metadata. Add if appropriate.
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L31 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L33 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L39 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L40 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L45 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L47 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L49 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L51 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L54 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L57 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L59 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L63 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L65 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L67 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L71 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L72 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L74 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L88 - Line must be at most 100 characters
src/content/en/fundamentals/performance/critical-rendering-path/render-tree-construction.md#L90 - Line must be at most 100 characters