How can I get inner html?

I'm trying to display embedded tweets. I need to show tweets in a webview. Is there a way to get inner html of nodes from a custom renderer?

Same problem. Is there a any solution ?

@saitbnzl : Have you found a solution because I  am facing the same issue in renderer I am only able to get full HTML, not the inner one.
Can you specify how you achieved it?

@jariwalabhavesh Hi, We've made some changes in the source code and we made it a local component (not npm dependent).
As far as I can remember this was the only change related to this issue:
    mapDOMNodesTORNElements (DOMNodes, parentTag = false) {
        const { ignoreNodesFunction, ignoredTags, alterNode, alterData, alterChildren, tagsStyles, classesStyles } = this.props;
        let RNElements = DOMNodes.map((node, nodeIndex) => {
            let { children, data } = node;
            if(node.name=='blockquote'){ // this block is added
                node.innerHTML = htmlparser2.DomUtils.getOuterHTML(node);
            }

Then we access it like below in the renderer:
blockquote: {
    renderer: (htmlAttribs, node, parent, children, innerHTML) => {
      if (htmlAttribs.class == 'twitter-tweet') {
        console.log("twitter", children.rawChildren[1].parent.innerHTML)

@saitbnzl : I had followed your  guide. And able to see embed twitter code. But is covering too many height. Is there any way you had adjusted height of embded. I had rendered inner html inside webview.

@jariwalabhavesh  Yes we had some with height, too. We had a solution with WebView. Try to embed tweets in this.

@saitbnzl : Thanks a lot for providing me webview code. I will try and let you know here.

@saitbnzl : Awesome, Thank you so much it works.

@saitbnzl : One more thing I had noticed that twitter embedded works perfectly in debug mode in both android and ios. But when I tried with release version then twitter embedded was not loading in android in ios it is loading fine.
Have you any idea why is it like that in android??

@jariwalabhavesh Yes, I just have noticed this is happening in our app, too. It was fine a while ago. Idk the reason and have no time to investigate currently. Please let me know, if you can find something.

@saitbnzl : sure, I will let you if I find a solution

@saitbnzl : I put webview back with static height and it is working. So I think issue is either with message or javascript that we are injecting in smartWebView.

@saitbnzl : Finally I found solution. The main issue was window.postMessage. javascript was working fine and height getting fine.
To fix it I had used react-native-webview-bridge . I am using react-native-webview-bridge version 0.40.1.
I had done little bit changes to make it work in android. Code base will be link @saitbnzl  that you provided.
Change injectedScript
const injectedScript = function () {
  function waitForBridge() {
    if (this.WebViewBridge) {
      let height = 0;
      if (document.documentElement.clientHeight > document.body.clientHeight) {
        height = document.documentElement.clientHeight
      }
      else {
        height = document.body.clientHeight
      }
      this.WebViewBridge.send(height.toString())
    } else {
      setTimeout(waitForBridge, 600);
    }
  }
  waitForBridge()
};


Question: abaplint.app Statement Compatibility

Just a question, there is an option to see what statements are [not] compatible in the different versions?
https://abaplint.app/stats/jrodriguez-rc/abap-dev-utilities/statement_compatibility

hi,
not right now, but there will be, sometime
as a workaround, you can clone the files to your local PC, then change the version in abaplint.json, and run abaplint

I imported the project into a 750 system and fix 3 syntax errors (abaplint only shows 2)
https://github.com/jrodriguez-rc/abap-dev-utilities/commit/ec549128e0ca516712f95a8a3efc6edf806dcd9d
After I updated the code, I have the same result, with 2 statements incompatible from 740sp8 to 751, but I didn't find any other error in 750.
Also, in the abaplint config, I specified version 740sp8, but no errors are raised.
https://github.com/jrodriguez-rc/abap-dev-utilities/blob/master/abaplint.json#L10

that sounds like bugs, please raise an issue for each of the findings

the value in the config is wrong, try opening the config in vscode, assuming you have the abaplint extension installed,

issue https://github.com/abaplint/abaplint/issues/1540 created

Thank you @larshp, I could open them yesterday, but I saw almost all problems are fixed (I'll need to check the version in others abaplint configs).
I open a new issue for pending error #1545


Jd inheritance 12/27

adding code comment throughout inheritance project.

Haha, right!?
Encrypted email based in Switzerland.
Sent from ProtonMail for iOS
On Mon, Dec 27, 2021 at 7:55 PM, LaTonia-Mertica @.***> wrote:

@LaTonia-Mertica approved this pull request.
Hello @.***(https://github.com/Jason-Doze) ,
Not only do I see multiple files with comments. The comments are EPIC ... tremendous work! Thank you so much ...
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.Message ID: @.***>


[fix] [auto-recovery] Fix pulsar ledger auditor dead lock problem.

Motivation
After the AutoRecovery cluster is started, it will elect an Auditor Leader to perform its work, while the remaining nodes act as Followers. When the Leader node goes down, the Followers will initiate an election process to select a new Auditor Leader to carry out the tasks. This mechanism ensures high availability of the Auditor component.
In the implementation of PulsarLedgerAuditorManager, the Auditor Follower will continuously loop in a while(true) loop until it becomes the Leader, at which point it will exit the loop. The change in status is notified through LeaderElection.
There is a mechanism in place: when a SessionLost event occurs, AutoRecovery initiates a shutdown, which closes the Auditor.
However, in the implementation of LeaderElection, when a SessionLost event happens, it becomes unable to continue pushing status change notifications to the Auditor Follower. As a result, the Auditor Follower cannot receive the status change notification, causing the thread to remain stuck and preventing the shutdown of the auditor.
The stack info:
"AuditorElector-<IP_ADDRESS>:58641" #257 prio=5 os_prio=31 cpu=0.22ms elapsed=69.67s tid=0x000000013bc23800 nid=0x2a20f in Object.wait()  [0x00000004e3302000]
   java.lang.Thread.State: WAITING (on object monitor)
	at<EMAIL_ADDRESS>Method)
	- waiting on <0x0000200006026150> (a org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager)
	at java.lang.Object.wait(java.base@<IP_ADDRESS>/Object.java:338)
	at org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager.tryToBecomeAuditor(PulsarLedgerAuditorManager.java:77)
	- locked <0x0000200006026150> (a org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager)
	at org.apache.bookkeeper.replication.AuditorElector$3.run(AuditorElector.java:185)
	at java.util.concurrent.Executors$RunnableAdapter.call(java.base@<IP_ADDRESS>/Executors.java:539)
	at java.util.concurrent.FutureTask.run(java.base@<IP_ADDRESS>/FutureTask.java:264)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@<IP_ADDRESS>/ThreadPoolExecutor.java:1136)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@<IP_ADDRESS>/ThreadPoolExecutor.java:635)
	at java.lang.Thread.run(java.base@<IP_ADDRESS>/Thread.java:833)

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

After #21159 merged, I will rebase this branch.

@horizonzy
Could you please help fix this error?
Error:  Medium: Naked notify in org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager.lambda$new$0(SessionEvent) [org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager] At PulsarLedgerAuditorManager.java:[line 56] NN_NAKED_NOTIFY

@horizonzy Why you rollback the lockObj?
while (true) {
            try {
                synchronized (this) {
                    if (leaderElectionState == LeaderElectionState.Leading) {
                        return;
                    } else {
                        wait();
                    }
                }
            } catch (InterruptedException e) {
                throw new RuntimeException(e);
            }

This one is not correct, right? It will only allow the same thread to call notifyAll() because handleStateChanges will acquire the lock  synchronized (this) first.
As you mentioned in the description
"AuditorElector-<IP_ADDRESS>:58641" #257 prio=5 os_prio=31 cpu=0.22ms elapsed=69.67s tid=0x000000013bc23800 nid=0x2a20f in Object.wait()  [0x00000004e3302000]
   java.lang.Thread.State: WAITING (on object monitor)
	at<EMAIL_ADDRESS>Method)
	- waiting on <0x0000200006026150> (a org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager)
	at java.lang.Object.wait(java.base@<IP_ADDRESS>/Object.java:338)
	at org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager.tryToBecomeAuditor(PulsarLedgerAuditorManager.java:77)
	- locked <0x0000200006026150> (a org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager)
	at org.apache.bookkeeper.replication.AuditorElector$3.run(AuditorElector.java:185)
	at java.util.concurrent.Executors$RunnableAdapter.call(java.base@<IP_ADDRESS>/Executors.java:539)
	at java.util.concurrent.FutureTask.run(java.base@<IP_ADDRESS>/FutureTask.java:264)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@<IP_ADDRESS>/ThreadPoolExecutor.java:1136)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@<IP_ADDRESS>/ThreadPoolExecutor.java:635)
	at java.lang.Thread.run(java.base@<IP_ADDRESS>/Thread.java:833)

If there is another thread calling handleStateChanges, it will wait for the lock.

@horizonzy Why you rollback the lockObj?
while (true) {
            try {
                synchronized (this) {
                    if (leaderElectionState == LeaderElectionState.Leading) {
                        return;
                    } else {
                        wait();
                    }
                }
            } catch (InterruptedException e) {
                throw new RuntimeException(e);
            }

This one is not correct, right? It will only allow the same thread to call notifyAll() because handleStateChanges will acquire the lock  synchronized (this) first.
As you mentioned in the description
"AuditorElector-<IP_ADDRESS>:58641" #257 prio=5 os_prio=31 cpu=0.22ms elapsed=69.67s tid=0x000000013bc23800 nid=0x2a20f in Object.wait()  [0x00000004e3302000]
   java.lang.Thread.State: WAITING (on object monitor)
	at<EMAIL_ADDRESS>Method)
	- waiting on <0x0000200006026150> (a org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager)
	at java.lang.Object.wait(java.base@<IP_ADDRESS>/Object.java:338)
	at org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager.tryToBecomeAuditor(PulsarLedgerAuditorManager.java:77)
	- locked <0x0000200006026150> (a org.apache.pulsar.metadata.bookkeeper.PulsarLedgerAuditorManager)
	at org.apache.bookkeeper.replication.AuditorElector$3.run(AuditorElector.java:185)
	at java.util.concurrent.Executors$RunnableAdapter.call(java.base@<IP_ADDRESS>/Executors.java:539)
	at java.util.concurrent.FutureTask.run(java.base@<IP_ADDRESS>/FutureTask.java:264)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@<IP_ADDRESS>/ThreadPoolExecutor.java:1136)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@<IP_ADDRESS>/ThreadPoolExecutor.java:635)
	at java.lang.Thread.run(java.base@<IP_ADDRESS>/Thread.java:833)

If there is another thread calling handleStateChanges, it will wait for the lock.

I think there is no difference between using this or lockObj, and using lockObj just to test the findbugs error.
No, the wait() method will give up the lock resource. The other thread can acquire the lock resource, it won't block.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

Codecov Report

Merging #21181 (509157c) into master (2aa8c3b) will increase coverage by 36.30%.
Report is 5 commits behind head on master.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             master   #21181       +/-   ##
=============================================
+ Coverage     36.92%   73.23%   +36.30%
- Complexity    12203    32385    +20182
=============================================
  Files          1698     1887      +189
  Lines        130400   140099     +9699
  Branches      14251    15427     +1176
=============================================
+ Hits          48153   102596    +54443
+ Misses        75908    29397    -46511
- Partials       6339     8106     +1767

Flag
Coverage Δ

inttests
24.33% <0.00%> (+0.11%)
:arrow_up:

systests
24.74% <0.00%> (-0.40%)
:arrow_down:

unittests
72.52% <100.00%> (+40.52%)
:arrow_up:

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

Files Changed
Coverage Δ

.../bookkeeper/AbstractHierarchicalLedgerManager.java
76.66% <100.00%> (+66.32%)
:arrow_up:

...etadata/bookkeeper/PulsarLedgerAuditorManager.java
95.45% <100.00%> (+95.45%)
:arrow_up:

... and 1447 files with indirect coverage changes


Add jQuery references to top of members.js and update references throughout the code

Consider creating a separate js file?   Or an object if necessary

Done!


Add skip() to ZstdBufferDecompressingStream

Users of ZstdBufferDecompressingStream may have a requirement to skip reading some uncompressed bytes. A similar method exists in ZstdInputStream.
The skip() method should:

Use a BufferPool if provided.
Allocate buffer only once from the BufferSupplier.
Returns the number of bytes skipped.

The interface should be modeled similar to InputStream#skip(long n).

Sounds reasonable, contributions welcome.


Feature Request: Using compile-time constants as array lengths

Hello, it appears that using compile-time constants as array lengths.
For example, the following code
#[flux::constant]
const BUFLEN: usize = 100;
type FixedSizeBuffer = [i32; BUFLEN];

fails with the error:
error[FLUX]: refinement of unsupported type alias
  --> src/main.rs:36:6
   |
36 |type FixedSizeBuffer = [i32; BUFLEN];
   |      ^^^^ this type alias contains unsupported features
   |
   = note: only interger literals are supported for array lengths

You can workaround this by just writing it out as
type FixedSizeBuffer = [i32; 100];

directly, but thats a little ugly.
Presumably, adding support for compile-time constant lengths is pretty straight forward, would you mind either (1) implementing it, or (2) pointing me to the appropriate part of the code so that I can implement it?
Thanks

The easiest way to support this is by opportunistically doing const eval during lifting here https://github.com/flux-rs/flux/blob/main/crates/flux-middle/src/fhir/lift.rs#L540
Handling more complicated cases like const generics is a bit more involved.

Since we implemented the const generics, is this easier now? It seems this should be pretty straightforward now?

this is orthogonal to const generics, but I've been looking at it and it sounds doable. I want to implement it.
I think this is going to be necessary for the eliptic curve stuff because I got this error when running flux on it.


Feat req: support OpenAI official API, or use puppeteer to do ChatGPT auth

Currently this plugin is not usable at all, even with both session key and cloudflare key filled in.
Now the community has solutions like official API, and Puppeteer to do the auth thing. I really hope this plugin could revive some day..

可以细说解决方案么


Passing branch parameter is causing a 404

Pulling a branch with phrase pull --branch branch-name returns a 404. The branch does exist and works with the old CLI

Fixed in 2.0.1


Fixed none push-down geotools filter applied to the relation

@5iFish thanks for the fix! would it be possible to add a unit test showing the issue and solution?

@5iFish thanks for the fix! would it be possible to add a unit test showing the issue and solution?

Glad to receive your message. I will add the unit test tomorrow. Good night.

@5iFish thanks for finding and fixing this issue!


Connectivity using private endpoints

As far as I can tell private endpoints always force communitcation to proxy mode. This should be called out in the documentation.

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

ID: e1a62365-4312-8aad-d2f1-bb5c4184adf1
Version Independent ID: 2ba5b809-8025-d7ee-c756-d6d1bab033fb
Content: Azure SQL Database Connectivity Architecture - Azure SQL Database and Azure Synapse Analytics
Content Source: articles/azure-sql/database/connectivity-architecture.md
Service: sql-database
Sub-service: development
GitHub Login: @rohitnayakmsft
Microsoft Alias: rohitna

@jabbera We are checking this and will get back to you

@jabbera Please elaborate regarding your feedback. The document does provides details regarding the default connection policy. Please see below:

If this is not what you are looking for and looking for in particular for Private link, that information is available here - https://docs.microsoft.com/en-us/azure/azure-sql/database/private-endpoint-overview#limitations
Hope this helps.

@jabbera Please let us know if you need any further help regarding this.

The second link was what I was looking for. Thanks!

@jabbera Thank you for the confirmation. We will go ahead and close the thread for now.


Refine Registration Behaviour / Error reporting for unknown references

By defining a seperate error response, preferably with a well defined error object in the response, for undefined references (such as sources/flows etc) it'd be possible for nodes to more easily resolve missing resouces.
Instead of 400 a registration would then instead respond a registration that references an to the registry unknown resource id with - for example - 412 Precondition Failed.

Falling to register resources in the correct order seems like a logic error to be fixed during development,  not a runtime error which could be automatically recovered from?
FWIW, for debugging the problem, the nmos-cpp implementation includes error details on the 400 response that would identify this class of error.

ARG review of open issues 2023-06-23: this will be closed


palemoon-bin: init at 32.0.0

Description of changes
Due to https://github.com/NixOS/nixpkgs/pull/201859, we won't be able to provide Nix-built binary downloads of Pale Moon past NixOS 22.11:
↪ nix-build . --no-out-link -A palemoon
error: Package ‘python-<IP_ADDRESS>’ in <pwd>/pkgs/development/interpreters/python/cpython/2.7/default.nix:330 is marked as insecure, refusing to evaluate.

The Debian maintainer is in a similar boat. We'll have to make do with the prebuilt binaries for now.
Things done

Built on platform(s)

[x] 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
[x] 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

[x] Fits CONTRIBUTING.md.

That dreadful day has come...

Is Pale Moon even maintained? I'm not sure how I feel about shipping packages in-tree that we can't even build because their build system (by association) is EOL...
Maybe a flake would be best?

Is Pale Moon even maintained?

Latest release is from 2023-01-24 & added "full coverage of the ECMAScript 2016-2020 JavaScript specifications, with the exception of BigInt primitives". There's just no-one on the team with the time & Python(2,3) experience to migrate the build system: https://github.com/NixOS/nixpkgs/pull/204336#issuecomment-1336252606

And they are (correctly, I should say) afraid of another deprecation in the future, given that the less than optimal handling of Python migration.


Add an extra example for queue arg configuration

This is just something I have missed twice now so I wanted to make it clear that the queue can be configured this way as well. And the seconds thing as we discussed on slack @koudelka.
Let me know if you want something else in here added as well.

Hey Rahul, thanks again dude. :)


Segmentation Fault

I met something weird:

Collecting MarkupSafe>=2.0 (from jinja2->lsp-tree-sitter->autotools-language-server==0.1.dev1+geb7064c)
  Using cached MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (3.0 kB)
  ...
Fatal Python error: Segmentation fault

Current thread 0x00007f84f4d7cb80 (most recent call first):
  File "<frozen importlib._bootstrap>", line 488 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 1289 in create_module
  File "<frozen importlib._bootstrap>", line 813 in module_from_spec
  File "<frozen importlib._bootstrap>", line 921 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1331 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1360 in _find_and_load
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/tree_sitter_make/__init__.py", line 3 in <module>
  File "<frozen importlib._bootstrap>", line 488 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 995 in exec_module
  File "<frozen importlib._bootstrap>", line 935 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1331 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1360 in _find_and_load
  File "/home/runner/work/autotools-language-server/autotools-language-server/src/make_language_server/utils.py", line 10 in <module>
  File "<frozen importlib._bootstrap>", line 488 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 995 in exec_module
  File "<frozen importlib._bootstrap>", line 935 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1331 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1360 in _find_and_load
  File "/home/runner/work/autotools-language-server/autotools-language-server/src/make_language_server/finders.py", line 17 in <module>
  File "<frozen importlib._bootstrap>", line 488 in _call_with_frames_removed
  File "<frozen importlib._bootstrap_external>", line 995 in exec_module
  File "<frozen importlib._bootstrap>", line 935 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1331 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1360 in _find_and_load
  File "/home/runner/work/autotools-language-server/autotools-language-server/tests/test_finders.py", line 6 in <module>
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/assertion/rewrite.py", line 178 in exec_module
  File "<frozen importlib._bootstrap>", line 935 in _load_unlocked
  File "<frozen importlib._bootstrap>", line 1331 in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 1360 in _find_and_load
  File "<frozen importlib._bootstrap>", line 1387 in _gcd_import
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/importlib/__init__.py", line 90 in import_module
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/pathlib.py", line 591 in import_path
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/python.py", line 492 in importtestmodule
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/python.py", line 545 in _getobj
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/python.py", line 287 in obj
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/python.py", line 561 in _register_setup_module_fixture
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/python.py", line 548 in collect
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/runner.py", line 389 in collect
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/runner.py", line 341 in from_call
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/runner.py", line 391 in pytest_make_collect_report
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/runner.py", line 567 in collect_one_node
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 837 in _collect_one_node
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 974 in genitems
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 979 in genitems
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 979 in genitems
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 811 in perform_collect
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 349 in pytest_collection
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 338 in _main
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 285 in wrap_session
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/main.py", line 332 in pytest_cmdline_main
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_callers.py", line 103 in _multicall
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_manager.py", line 120 in _hookexec
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/pluggy/_hooks.py", line 513 in __call__
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/config/__init__.py", line 178 in main
  File "/opt/hostedtoolcache/Python/3.12.3/x64/lib/python3.12/site-packages/_pytest/config/__init__.py", line 206 in console_main
  File "/opt/hostedtoolcache/Python/3.12.3/x64/bin/pytest", line 8 in <module>

Extension modules: markupsafe._speedups (total: 1)
/home/runner/work/_temp/ca54a63b-521b-4765-a8e8-7f69cda6d221.sh: line 1:  1896 Segmentation fault      (core dumped) pytest --cov
Error: Process completed with exit code 139.

https://github.com/Freed-Wu/autotools-language-server/actions/runs/9220219913/job/25366773989

I can't reproduce this issue with the information provided.


question about logic in searching go.mod

Describe the bug
occur error when created a sub project that used a shared go.mod which in root directory.
The module name given by the '-module' option ('base_project/server/cmd/rpc1/') is not consist with the name defined in go.mod ('wecqupt' from /mnt/e/base_project)

Expected behavior
should generate project successfully in this case.
Kitex version:
v0.6.1
Solution
the project directory example is as follows.

展开查看

    ├── server ---------
        ├── cmd --------
            ├── api -------  (api service generated by hz, module name is "project_name/server/cmd/api")
                ├── main.go
            ├── rpc1 ------- (rpc service generated by kitex, module name is "project_name/server/cmd/rpc1")
                ├── main.go
            ├── rpc2 ------- (rpc service generated by kitex, module name is "project_name/server/cmd/rpc2")
                ├── main.go
    ├── go.mod ------------- (module name is "project_name")

kitex go.mod search logic is that search go.mod from the current directory to the root directory.
but when the project use a shared go.mod in root directory which module name is "base_module", and sub project module name is "base_module/sub_module", kitex will not generate code and will throw error above.
hz go.mod search logic is search go.mod in current directory (not recursive) when specified module name.
in this case hz can generate code.
so i think kitex should use hz's logic in order to solve the problem.

I think you may need to do "go mod init" if you want to generate code in a sub directory which has a different module name from the parent.

I think you may need to do "go mod init" if you want to generate code in a sub directory which has a different module name from the parent.

yes, it is a solution, i solved the problem by the steps as follows:

go mod init {sub_module_name}
kitex -module {sub_module_name} {idl_path}
rm go.mod

but it is not elegant, so i hope to improve the gen tools.

why rm go.mod? If you want to add a sub module, you need to do "go mod init" first.

why rm go.mod? If you want to add a sub module, you need to do "go mod init" first.

because all the module shares one go.mod, which is $GOPATH is alway the root directory.

"all the modules share one go.mod". then why do you specify a different module when generate

"all the modules share one go.mod". then why do you specify a different module when generate

because the wrong import path will be filled when generated

cannot get your point...Submodule should have its own go.mod. So "go mod init" and then generate should be fine.


Dropdown: remove dependency to role="menu", role="listbox", a and li elements => fix keyboard navigation

Re-opened #19864 to fix conflicts as for some reason the head branch of the original PR is marked as "unknown" (Sorry for the inconvenience...)
Per migration documentation in https://github.com/twbs/bootstrap/commit/4d8d8bdab4b0e2931fcf92ce30d772b05a989434:

Rebuilt dropdown styles and markup to provide easy, built-in support for <a> and <button> based dropdown items.
Dropdown items now require .dropdown-item.

Per https://github.com/twbs/bootstrap/issues/19034#issuecomment-179749958 role="menu" should have been dropped.
This PR:

Remove the dependency to role="menu" or role="listbox" and rely on the class dropdown-menu instead
Remove the dependency to the a element for the dropdown-item and rely on the class dropdown-item instead
Remove the necessity to wrap dropdown-item in li elements

All this problems affected only the keyboard navigation in the dropdown.
With this modification the javascript now matches the markup in the documentation.
The keyboard navigation works again now in dropdowns.

Update unit test with new markup.
Per comment

@all can you help me with this one http://stackoverflow.com/questions/41645884/accessibility-for-select-fields-in-ie11

@bardiharborow I see that you added a lot of commit on this branch from v4-dev.
Now the branch contains modifications to the dist file and many other that were not in my PR. Also it fails the travis build. Do you know what happened here ?

This PR is a little wonky right now, but any chance for a review from @Johann-S and @bardiharborow on the core changes at https://github.com/twbs/bootstrap/pull/21535/files#diff-bfe9dc603f82b0c51ba7430c1fe4c558?

I merged the last changes from v4-dev and for some reason the diff in the PR show all these changes even though it shouldn't as they are not different from the last v4-dev.
Looking at the diff between v4-dev and my dropdown-keyboard branch show the proper diff: https://github.com/twbs/bootstrap/compare/v4-dev...vanduynslagerp:dropdown-keyboard

It's a very good work thank you @vanduynslagerp 👍
IMO we shouldn't remove dependency to role="menu" or role="listbox" for the accessibility but I'm not an expert in this subject we should call the ARIA guy @patrickhlauke 😄

@Johann-S the PR remove the dependency to role="menu" and role="listbox" in the JS selectors so it's consistent with other JS module and rely on classes for selector.
Like other components in Bootstrap, the use of role="menu", role="listbox" or aria- for accessibility is recommended in the documentation and examples.

Sorry but your branch is out-of-date so can you update ?

Again but I arrived too late and your branch isn't up to date and #21802 too

Can you notice me when you update your branch ? Or can you allow me to update your branch ? Thank you

I gave you permission


Please support Linked Data Proofs / JSON-LD

Per the VC Data Model there are 2 proof formats defined: https://www.w3.org/TR/vc-data-model/#proof-formats
JWTs provide no semantic features, and have no canonicalization support... But given they have been around for long enough to have a number of cryptographic algorithms prohibited https://www.iana.org/assignments/jose/jose.xhtml#web-signature-encryption-algorithms there is an abundance of JOSE tooling to build on.
When we implemented https://identity.foundation/sidetree/spec/#commitment-value-generation
We were forced to require the use of JCS, beyond specifying vanilla JOSE, because, per:
https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-17

Cryptographic operations like hashing and signing need the data to be  expressed in an invariant format so that the operations are reliably  repeatable.  One way to address this is to create a canonical  representation of the data.  Canonicalization also permits data to be exchanged in its original form on the "wire" while cryptographic operations performed on the canonicalized counterpart of the data in the producer and consumer end points, generate consistent results.

In addition to JOSE not having a canonical representation for data, JSON also does not reliably handle big numbers: https://tools.ietf.org/html/draft-rundgren-json-canonicalization-scheme-17#appendix-D
Big Number are incredibly common when handling crypto currency, or mathematical operations...
Also per the VC Data Model Basic Concepts:
https://www.w3.org/TR/vc-data-model/#basic-concepts
@context is required, and is used to define the credential as linked data (JSON-LD).
The JWT variant's embed these credentials as vc and vp.
https://w3c.github.io/vc-data-model/#json-web-token-extensions
But does this implementation check to make sure they are valid JSON-LD? Or do you treat vc and vp as arbitrary JSON attributes? If you don't validate them, I don't see the value in VC-JWT at all, since you can get the same result by just creating a vanilla JWS...
Finally, LD Proofs are 100% compatible with JOSE, and add support for semantic disambiguity, unlocking common vocabularies such as schema.org and google knowledge graph.... And JSON-LD is already being used by Azure IoT: https://docs.microsoft.com/en-us/azure/iot-pnp/overview-iot-plug-and-play

IoT Plug and Play and the DTDL are open to the community, and Microsoft welcomes collaboration with customers, partners, and the industry. Both are based on open W3C standards such as JSON-LD and RDF, which enable easier adoption across services and tooling

Bing also supports Schema.org and JSON-LD... https://blogs.bing.com/webmaster/august-2018/Introducing-JSON-LD-Support-in-Bing-Webmaster-Tools
Here is an example of creating an LD Proof for all the popular JOSE key and signature formats, it leverages the best of JOSE (as popular legacy cryptographic suite), along with support canonicalization and compatibility with RDF / schema.org and JSON-LD.
https://github.com/w3c-ccg/lds-jws2020
If you do not plan to support LD Proofs along with JWTs, might I suggest renaming this repo (and the others) to avoid misleading developers who might assume Microsoft is supporting the same linked data technology currently used by Azure IoT and Bing.

I agree with Orie that not confusing developers is critical. There are two formats that are enclosed within the VC specification that is an official W3C spec. It behooves us to not confuse developers when only one format is supported by the libraries in this repo.

+1 to the points raised above. In addition to this a feature that might be of interest is support for selectively revealable assertions (e.g via zero knowledge proofs). JWS (JSON Web Signatures) treat the signed payload as a single blob, this limitation prevents using selective reveal compatible digital signatures such as BBS signatures without applying some form of normalization process to the payload, a feature that is already built into linked data proofs, current spec here and reference implementation.

Thanks for sharing. We are currently in private preview so prioritized on one format. We take this into account for future releases.

If you want test vectors for both JWT and LD Proof VCs, we have some here:

https://github.com/transmute-industries/vc.js
https://github.com/transmute-industries/vc.js/tree/master/packages/vc.js/src/__fixtures__/test-vectors/vc-jwt
https://github.com/transmute-industries/vc.js/tree/master/packages/vc.js/src/__fixtures__/test-vectors/vc-ld

Cool. Thanks

@OR13 ,  @tplooker , @Identitywoman
I wanted to let you know that the development of json ld proofs have started.
Thanks


Updated test for libsdformat behavior change

Summary
https://github.com/ignitionrobotics/sdformat/pull/872 changes emitted floating point numbers to be maximum by default when converting to a string. I've updated the test so that the precision is set to 6, which is std::ostream's default since modifying this expectation: https://github.com/ignitionrobotics/ign-gazebo/blob/f5bb284884de9c5d4d7fa5614e53b528654b6611/src/SdfGenerator_TEST.cc#L831
to:
"1 2 3 0.099999999999999992 0.20000000000000001 0.29999999999999999"

may be more difficult to read.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[x] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I don't believe the failing tests are related, can I go ahead and merge?

Yes, I think this is safe to merge.


Heading levels

In the show notes, the episode title and section headings are all <h2>s. I checked out the site recently looking for the show notes and scrolled right past. I guess I was looking for a visually distinct heading to mark the title. (And I'm sure there are accessibility issues you know about better than me.)
There's no <h1> on the page. An <h1> was added around the logo in #126 but removed in #190.

@bripmccann feel free to submit a PR to make the show notes title an h1 - pages definitely need an h1 for accessibility and defining the page structure and content hierarchy, not sure what to do about visually making the Show Notes more distinct

@416serg would this amount to changing the Show Notes from "##" to "#" in each show's markdown file?

Nope, should be simple, just editing the https://github.com/wesbos/Syntax/blob/master/components/ShowNotes.js file and changing the h2 for show.title

That works for the show's title, but I thought the idea was to change it for the "Show Notes" header, too. Looks like that is pulled into ShowNotes.js in the dangerouslySetInnerHTML at https://github.com/wesbos/Syntax/blob/master/components/ShowNotes.js#L32


fix broken link

Fix broken link caused by text escaping

@daxianji007,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

Thank you @rpetrusha for reviewing! I have updated the msdn links now.

@daxianji007,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

@daxianji007 @rpetrusha Note that many of the external links contain en-us. Is this something we want to address later?

I apologize -- in listing the replacement URLs, I'd included "en-us" in the URL. They should all be removed.

@daxianji007,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot

Update again to remove en-us in the links


Issue 475 profile page not working

Here is what is contained in this pull request:

Updated environment specific paths in maapprofile.php
Fixed setting of request method in maapprofile.php when fetching User profile.
Added deployment notes to README, including how to create the plugin ZIP file.
Merged in a change that was found in DIT, but not saved in the repo.

@anilnatha everything is working correctly except for the public SSH key upload. I tried uploading a new SSH key after logging into https://dit.maap-project.org/profile/ but the file was not saved.

Thanks for reviewing this.  I'll take a look at the SSH key upload issue and report back.

Hey @bsatoriu I've committed the final changes we spoke of earlier today resolve the issues with the proxy granting ticket.  These changes are rolled out on DIT and functional. Once you have had an opportunity to review this, I'll push out the changes to UAT for Sri to review.

Thanks @anilnatha, looks good.

@bsatoriu Thank you.  I'll push this out to UAT tomorrow.


Introduce error handling

There is no way for applications using NXT to know if an object creation was successful. Introduce error handling as outlined in the overview doc.

This has been done.


Update CODEOWNERS

Updates CODEOWNERS.
/cc @koba04

Codecov Report

Merging #632 (8cd0773) into master (bbe9c58) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #632   +/-   ##
=======================================
  Coverage   51.39%   51.39%
=======================================
  Files          24       24
  Lines        1043     1043
  Branches      198      198
=======================================
  Hits          536      536
  Misses        459      459
  Partials       48       48


Error because of empty Title in Pronouns Setup window

When i try and click "Add Pronouns" or delete a pronoun (aka call the render function) it shows me an error.
And after which the window isnt usable anymore:

After trying a few things out i found just adding a title to the window works without a problem:

@Paukler thanks for the detailed analyses and debugging. I'll have this fix in by tomorrow night... I never tested the setup screen in version 10 :(

@Paukler new release has been made with the fix. Thanks again!


[cluster test] Honor cooldown during downscaling

This should help to prevent spurious 'pod not found' issue we've seen
It should also allow to reduce run time of cluster test in 'peak hours', as instances would not downscale

@bors-libra r+

:pushpin: Commit 3fbe2e3 has been approved by changyonghu

:hourglass: Testing commit 3fbe2e34be3c98bee2ce76a898ac6cb220e5c6d2 with merge cf0587e3ec49ad1feb4243d363ccad9add78fcf6...

@bors-libra r-

I'm not sure if this is what we want. With this flag, the scale down or the scale up action can be ignored if we are within the cooldown period.

:broken_heart: Test failed - checks-actions_land_blocking_test

Yeah, looks like cooldown does not work as expected and just returns
An error occurred (ScalingActivityInProgress) when calling the SetDesiredCapacity operation: Scaling activity 0685cb16-898e-25fe-d43c-fc9f97233857 is in progress and blocks this action


[KS-44] Transparently wrap values

Still planning to merge this?

ping - I think this could be useful

Yes, definitely planning on merging this as soon as I get back :) This took
the back seat while I was trying to wrap up the OCR3 capability.
On Wed, 21 Feb 2024 at 19:38, Bolek @.***> wrote:

ping - I think this could be useful
—
Reply to this email directly, view it on GitHub
https://github.com/smartcontractkit/chainlink-common/pull/333#issuecomment-1957666476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENQ44CXYPWJED56FEHUIHTYUY5LFAVCNFSM6AAAAABDB4PWF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGY3DMNBXGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


company page - Swap contact and postion option in company detail view

Describe the bug

change contact option postion to postion and position option to contact option position

https://www.berrycast.com/conversations/a9d15fa1-4063-50b0-9801-ab6fcf9083d5

duplicate #1852


Increasing localization for every element on Dashy

Category:

One of: Feature / Translation

Overview

I've seen that some elements are not translatable. Therefore, for the sake of accessibility, I'll try to map Vue components and localization files to allow people to translate Dashy. This is a draft, I'll contribute to it until every element is done.

New Vars

New strings in en.json file (and fr.json as my mother language is French 🥖 ). I tried to follow the current naming convention.

Screenshot (if applicable)
Footer done (It was initially just to test if I could be able to make it)
In English, no change (just one bug):

In French, It is (almost) correctly translated 😄

Code Quality Checklist (Please complete)

[x] All changes are backwards compatible
[ ] All lint checks and tests are passing
[ ] There are no (new) build warnings or errors
[ ] (If a new config option is added) Attribute is outlined in the schema and documented
[ ] (If a new dependency is added) Package is essential, and has been checked out for security or performance
[ ] Bumps version, if new feature added

Ready to review. It's already a good start.


Modifying installation for bootstrap 5.0 and above

`<!--module Boring
module Bootstrap
class InstallGenerator < Rails::Generators::Base
desc "Adds Bootstrap to the application"
source_root File.expand_path("templates", dir)
  def add_bootstrap_package
    say "Adding bootstrap packages", :green
    run "yarn add bootstrap jquery  popper.js **popper.js/core**"
  end

  def add_jquery_plugin_provider_to_webpack_environment
    say "Adding jQuery and popper JS plugin in the webpack", :green
    if File.exist?("config/webpack/environment.js")
      insert_into_file "config/webpack/environment.js", <<~RUBY, after<EMAIL_ADDRESS>        const webpack = require("webpack")

        environment.plugins.append("Provide", new webpack.ProvidePlugin({
          $: 'jquery',
          jQuery: 'jquery',
          Popper: ['popper.js', 'default']
        }))
      RUBY
    else`

Please provide enough information so that others can review your pull request. The three fields below are mandatory.
Before submitting a pull request, please make sure the following is done:

Fork the repository and create your branch from master.
Run bundle install in the repository root.
If you've fixed a bug or added code that should be tested, add tests!
Ensure the test suite passes (rake test).
-->

@pipolo23 can you rebase the PR with master?


7/10 PM Publish

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Error when get composition container: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information., loader exceptions: Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
[Error] System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeAssembly.get_DefinedTypes()
at System.Composition.Hosting.ContainerConfiguration.<WithAssemblies>b__0(Assembly a)
at System.Linq.Enumerable.<SelectManyIterator>d__162.MoveNext() at System.Composition.TypedParts.TypedPartExportDescriptorProvider..ctor(IEnumerable1 types, AttributedModelProvider attributeContext)
at System.Composition.Hosting.ContainerConfiguration.CreateContainer()
at Microsoft.DocAsCode.Common.CompositionContainer.GetContainer(IEnumerable1 assemblies) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder..ctor(IEnumerable1 assemblies, ImmutableArray`1 postProcessorNames, String templateHash, String intermediateFolder, String commitFromSHA, String commitToSHA, Boolean cleanupCacheHistory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Error when get composition container: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information., loader exceptions: Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040), Could not load file or assembly 'DotLiquid, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=82e46016ecf9f07c' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
[Error] System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeAssembly.get_DefinedTypes()
at System.Composition.Hosting.ContainerConfiguration.<WithAssemblies>b__0(Assembly a)
at System.Linq.Enumerable.<SelectManyIterator>d__162.MoveNext() at System.Composition.TypedParts.TypedPartExportDescriptorProvider..ctor(IEnumerable1 types, AttributedModelProvider attributeContext)
at System.Composition.Hosting.ContainerConfiguration.CreateContainer()
at Microsoft.DocAsCode.Common.CompositionContainer.GetContainer(IEnumerable1 assemblies) at Microsoft.DocAsCode.Build.Engine.DocumentBuilder..ctor(IEnumerable1 assemblies, ImmutableArray`1 postProcessorNames, String templateHash, String intermediateFolder, String commitFromSHA, String commitToSHA, Boolean cleanupCacheHistory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument(BuildJsonConfig config, TemplateManager templateManager, String baseDirectory, String outputDirectory, String pluginDirectory, String templateDirectory)
at Microsoft.DocAsCode.SubCommands.DocumentBuilderWrapper.BuildDocument()

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

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-autogen/azure.common.credentials.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.batch.operations.ApplicationOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.batch.operations.ApplicationPackageOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.batch.operations.BatchAccountOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.cognitiveservices.operations.CognitiveServicesAccountsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.compute.compute.v2015_06_15.operations.VirtualMachineExtensionImagesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.compute.compute.v2015_06_15.operations.VirtualMachineImagesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.compute.compute.v2016_03_30.operations.VirtualMachineExtensionImagesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.compute.compute.v2016_03_30.operations.VirtualMachineImagesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.compute.compute.v2016_04_30_preview.operations.VirtualMachineExtensionImagesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.compute.compute.v2016_04_30_preview.operations.VirtualMachineImagesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.containerregistry.v2017_03_01.operations.RegistriesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.analytics.account.operations.ComputePoliciesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.analytics.account.operations.DataLakeStoreAccountsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.analytics.account.operations.FirewallRulesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.analytics.account.operations.StorageAccountsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.analytics.catalog.operations.CatalogOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.analytics.job.operations.JobOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.store.operations.AccountOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.store.operations.FirewallRulesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.datalake.store.operations.TrustedIdProvidersOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.ArtifactSourcesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.FormulasOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.GlobalSchedulesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.NotificationChannelsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.PoliciesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.SchedulesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.SecretsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.ServiceRunnersOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.devtestlabs.operations.VirtualMachineSchedulesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.dns.operations.RecordSetsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.documentdb.operations.DatabaseAccountsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.eventhub.operations.ConsumerGroupsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.eventhub.operations.EventHubsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.eventhub.operations.NamespacesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.iothub.operations.IotHubResourceOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.keyvault.operations.VaultsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.AgreementsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.CertificatesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.IntegrationAccountsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.MapsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.PartnersOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.SchemasOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.SessionsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.WorkflowRunsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.WorkflowTriggerHistoriesOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.WorkflowTriggersOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.logic.operations.WorkflowsOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.media.operations.MediaServiceOperations.yml
:white_check_mark:Succeeded

docs-ref-autogen/azure.mgmt.monitor.operations.ActionGroupsOperations.yml
:white_check_mark:Succeeded

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


Create Yaml parsing checks on case study repos

As a shepard, I want Travis to automatically run integrity checks on the Yaml for parse errors.
Something like this: https://github.com/andymeneely/chromium-vulnerabilities/commit/1dca5d488ca98564d3501d558b9e0d65d60de100
But with something that can hook into Travis and looks nicer. Rspec?
Put this in chromium-vulnerabilities

I've got the basics of this pushed now: https://github.com/andymeneely/chromium-vulnerabilities/commit/7733f2d5678276db2310fd6a9f5fd8542da795be
It all builds on Travis and will give people feedback on their pull request automatically


Personal Theming

roam/css applies at the graph level
could be very useful to define multiple themes in one graph and let users choose
[[roam/js/themes]]

David Vargas

((blockuid1))

David Bieber

((blockuid2))

Brandon Toner

((blockuid3))

Each blockuid points to a roam/css code block. Load the appropriate theme accordingly

From David Bieber on discord

Audit: Won't do


Support USE [database] for MySQL

Sharding-JDBC use one logic data source.
Execute
USE [database]

will ignore the SQL and do nothing.

fixed at 2.1.0


GUI

gooey
web interface

Added to core, we need a more consistent manner to interact with the SQLite db.


Helm2: commit sha App Version getting converted to scientific notation

Output of helm version -c:
Client: &version.Version{SemVer:"v2.16.0", GitCommit:"e13bc94621d4ef666270cfbe734aaabf342a49bb", GitTreeState:"clean"}
When app version is a commit sha, it gets converted to a scientific notation when packaging. And package creates a tar ball even though the command errors out with errors in the output.
See below for more details on how to reproduce and about the issue:
$ helm create test

$ # change appVersion to 72225e2
$ vi test/Chart.yaml

$ cat test/Chart.yaml
apiVersion: v1
appVersion: 72225e2
description: A Helm chart for Kubernetes
name: test
version: 0.1.0

$ # notice how it errors out but still creates the tar ball
$ helm package test
Successfully packaged chart and saved it to: /Users/karuppiahoss/oss/helm-issues/issue-6833/dummy-repo-local/test-0.1.0.tgz
Error: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal number into Go struct field ChartVersion.entries.appVersion of type string

$ # check Chart.yaml contents in tar ball
$ vi test-0.1.0.tgz

Chart.yaml contents in the tar ball:
apiVersion: v1
appVersion: "7.2225e+06"
description: A Helm chart for Kubernetes
name: test
version: 0.1.0

The issue is similar to #6921 (v3 issue), in this case it's present in v2 too

The behavior is correct. If you provide 72225e2 as a field value, that should be rendered as a number in scientific notation. To fix this, wrap the string in quotes. That way the YAML parser will treat it as a string.
We should probably ask helm create to wrap the string fields in quotes. That way these fields are treated as strings.
In other words, the output of helm create test's Chart.yaml should be changed from this:
apiVersion: v2
name: test
description: A Helm chart for Kubernetes

# A chart can be either an 'application' or a 'library' chart.
#
# Application charts are a collection of templates that can be packaged into versioned archives
# to be deployed.
#
# Library charts provide useful utilities or functions for the chart developer. They're included as
# a dependency of application charts to inject those utilities and functions into the rendering
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
type: application

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: 0.1.0

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
appVersion: 1.16.0

to this:
apiVersion: "v2"
name: "test"
description: "A Helm chart for Kubernetes"

# A chart can be either an 'application' or a 'library' chart.
#
# Application charts are a collection of templates that can be packaged into versioned archives
# to be deployed.
#
# Library charts provide useful utilities or functions for the chart developer. They're included as
# a dependency of application charts to inject those utilities and functions into the rendering
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
type: "application"

# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
version: "0.1.0"

# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application.
appVersion: "1.16.0"

Closing in favour of https://github.com/helm/helm/issues/6921 to keep the conversation in one place. The codepaths are identical. Thanks.

@bacongobbler we still need to put a fix in dev-v2, which is not exactly identical code path / code base right? Also, I was putting it separate so that when it's fixed, people can already create proper repo index through this linting and packaging errors, for not putting double quotes, way before doing repo index and repo index will just work and helm3 repo add will not give issues. In fact we can close issue #6849 and have this and #6921 open and fix em

I closed this issue because it's the same issue. Issues can span multiple versions. Opening multiple tickets describing the same issue only confuses the community, as there will be simultaneous conversations occurring at the same time in two issues. It's best to keep conversations that are closely related in one ticket so the community can all discuss solutions in a single ticket, rather than repeating the same conversation twice.

Makes sense!


Fix line break disappearing with pasted text in IE11 under contentEditable mode

Problem
Line breaks disappear when pasting plain text from nodepad/textarea/command prompt in IE11 in contentEditable mode.
Specifically, this is because in domTextBetween a fromNode like1
2
3
4
5 is handled with addText(node.textContent); return, ignoring the
s inside.
This PR does a few things:

only addText & return if cm-text has value
otherwise walk the child nodes
treat br along with table, li as blocks
ignore empty elements (except for br which should be empty) to avoid unnecessary line breaks
add extra line breaks for p and pre

FWIW this issue reportedly is also on archlinux/debian in Firefox 52/58, but I have yet been able to reproduce them.

As far as I can see changes to this method effects IME input in modern browsers and IE11 plus pasting in IE11. I've manually tested for the IME issues I sent PR for previously (#5379, #5354) and they're still OK.
Before (IE11)
Text flashes, line breaks disappear.

Expected behavior (Chrome)

After (IE11)
Line breaks preserved.

That looks reasonable. Thanks!


Dropdown in Modal

Summary
the possibility of using a dropdown component in a modal
What is the feature request for?
The core library
The Problem
I have not managed to get modals with dropdown to work so i assume the functionality does not yet exist (i am not sure if maybe discords api doesnt have it or it its just disnake)
The Ideal Solution
the ideal solution would be me just doing the Implantation wrong
The Current Solution
No response
Additional Context
No response

Currently, Select Menus in Modals haven't been officially released. They work fine on Desktop but have problems on Mobile.

Okay and how would I retrieve the values from a dropdown inside a modal?

#611

ahh so its not actually supported yet

You can technically access the raw component data already, assuming you're using the master branch.
Nevertheless, support for selects in modals on mobile is still wip - #611 is primarily waiting for Discord to implement the feature on all platforms.

okay tyvm

https://github.com/DisnakeDev/disnake/pull/611#issuecomment-1463770255


Fix use strict as expression statement

Should fix #536.

Seems like my test is wrong somehow: Error: No message was provided... @vjeux / @jlongster how can I fix that, I couldn't find anything related to that for Jest?

// Parentheses around expression statement should be preserved in this case.
("use strict");

Flow dies in agony while trying to parse the file:
[ 0,
  [ 248, aw { t: 0, c: 'Failure', l: 7 }, -3 ],
  aw { t: 0, c: 'Nooo: T_LPAREN\n', l: 15 } ]

@vjeux wow, ok... what should we do then? Bypassing flow and only using Babylon in this case?

Yeah, let's just run babylon

For reference, here's the flow bug: facebook/flow#3234

Oh cool, there's already a fix in. So in a couple of days when 0.39 ships it'll work :)

Thanks!


Determine where Carbon patterns should live

Carbon's website has 14 patterns: https://carbondesignsystem.com/patterns/overview. The Pattern and Asset Libraries (PALs) have additional portfolio and product-specific patterns that have been created and documented.
Carbon Next (https://next.carbondesignsystem.com/assets/patterns) has a patterns catalog where you can filter indexed patterns by sponsor, status, framework, and platform.
License
All of Carbon's 14 patterns are open source.
Design kits
One of the patterns has a Sketch design kit (text toolbar).
Page tabs
Per this issue (https://github.com/carbon-design-system/carbon-platform/issues/485#issuecomment-1101656076), if the pattern doesn't have code, style, or accessibility guidance, each pattern would have two page tabs.

Overview (the standardized dashboard and content)
Usage (existing content gets migrated here)

Schema
Per the schema (https://github.com/carbon-design-system/carbon-platform/blob/main/docs/resource-schemas.md), patterns are assets, and all assets need to belong to a library.
Versioning isn't incredibly important to design-only patterns, but having patterns live in libraries provides growth potential so a pattern could get a coded implementation, etc.
Coded patterns
This doesn't happen often, but Carbon Angular is an example of where there are coded examples of the loading, dialogs, filtering, and forms patterns documented in the Carbon website: https://angular.carbondesignsystem.com/?path=/story/patterns-loading--large-loading.

Proposal B
Create a new library called Carbon Patterns that lives at a new folder: https://github.com/carbon-design-system/carbon/tree/main/packages.
No need to publish that as a package to NPM.
All indexing would be the same as proposal A.
A benefit to this is that the breadcrumb and pattern detail page would both say Carbon Patterns instead of Carbon Core as recommended above.
I see a few negatives to this approach.

The Carbon Angular library has patterns that we need to index. It already inherits Carbon Styles (https://github.com/IBM/carbon-components-angular/blob/master/src/carbon.yml#L7). We'd either need to add functionality so a library could inherit multiple libraries (which is messy), or add inheritance overrides so even if the library inherits library A, assets in that library could instead inherit an asset from library B (also messy).
It's hard to know what happens in the future, but if we end up shipping pattern-specific styling (Sass), it'd sure be nice for the pattern to live in the Carbon Core library (https://github.com/carbon-design-system/carbon/tree/main/packages/styles) to take advantage of that existing Sass build and publishing.

Recommendation
Don't pursue this proposal.

@mattrosno I can see why you’re leaning towards proposal A. There are a few things that I am trying to wrap my head around with this one though.
The first is that is seems a little disjointed to have all other assets living together except patterns. As a designer, I would expect to find those things together. And styles and patterns feel like different types of things to me. Patterns more closely align with components.
Secondly, as we think about indexing PALs, would they have the same issues potentially? I know that IBM products have a mix of coded and non-coded components (although they are all in react I think?) but we would also suggest proposal a to other teams with the same issue potentially? As a side note, some of IBM products patterns have style and code tabs in their PAL.

Libraries have assets; assets never live in isolation. Assets can be 1 of 4 types. That means that a library can have assets of type component and pattern, for example.
Libraries can inherit other libraries (where we match assets by id in inherited libraries.) The Carbon Styles library is used as the base library that Carbon React, Carbon Angular, etc. to inherit. This allows the framework collapsing in the catalogs:

It also allows one source of truth for content used by all libraries/assets that inherit it. The Carbon Styles library currently have these assets: https://web-app-prototype.j73b4w218e4.us-south.codeengine.appdomain.cloud/libraries/carbon-styles/latest/assets
Right now, the Carbon Styles library specifies content for asset:

Name
Description
Thumbnail
Type
Platform
Tags

With this, for example, Carbon React, Carbon Angular, Carbon Svelte, Carbon Vue, etc. don't have to specify those above properties. They are inherited from Carbon Styles.
But in the near future, additional content will be added to this library:

Usage docs
Style docs
Accessibility docs

The Carbon Styles library is more than styles. But, when determining indexing strategy with the System Squad, we agree this to be the best candidate for the base library to use for inheritance. Because this library will contain more than styles, that's why proposal A recommends that we rename it to Carbon Core or Carbon Common.

Patterns more closely align with components.

Proposal A does this. Components (the base component with no JavaScript implementation) live alongside our universal patterns (which also don't have coded implementation).

Secondly, as we think about indexing PALs, would they have the same issues potentially? I know that IBM products have a mix of coded and non-coded patterns (although they are all in React I think?)

Proposal A can support this in a couple different scenarios.

An asset can be of type pattern and framework react, meaning the pattern has a coded implementation.
An asset can be of type pattern and framework design-only. That's the current state of our universal patterns. But also, the Carbon Angular library has coded implementations for four patterns. With our current inheritance model, we can state that the Angular-implemented pattern inherits the design-only pattern. Just like that screenshot above, in the patterns catalog, you'd be able to see that the pattern exists as design-only or Angular so you can filter and determine what you want to view. Because proposal A works for our universal patterns that are both design-only and coded, this model should work for PALs as well where there are coded and non-coded patterns.

As a side note, some of IBM products patterns have style and code tabs in their PAL.

That's great. Per our asset detail page tabs, a pattern will by default only have Overview and Usage page tabs. As patterns are assets, and as assets can also have Style, Code, and Accessibility page tabs, we'll support patterns who have those additional page tabs.

Thanks for writing this all out. I think proposal A is making more sense after this explanation—and I agree, we would need to rename styles.
A question about Libraries inheriting other libraries. I have where design kits live at the top of mind. If Carbon react inherits Carbon styles, does that mean that you could find the carbon pattern kits and the react components kit in the Carbon react library assets? I'm trying to understand how inherited assets would show up in the library asset pages and design kit pages.

@kingtraceyj good question. If you look at the proposed schema changes to add design kits, each library can specify a designKits array that is inheritable.
https://github.com/carbon-design-system/carbon-platform/blob/2415072d12b9df7d734777e26f017279f637d0bf/docs/resource-schemas.md#library-keys
That means the carbon-styles is indexed like:
library:
  id: carbon-styles
  name: Carbon Common
  description: Common components and patterns, as well as Sass styles when those assets have coded implementations.
  noIndex: true
  designKits:
    - carbon-white-sketch
    - carbon-g10-sketch
    - carbon-g90-sketch
    - carbon-g100-sketch
    - carbon-white-figma
    - carbon-g10-figma
    - carbon-g90-figma
    - carbon-g100-figma
    - carbon-white-adobe-xd
    - carbon-g10-adobe-xd
    - carbon-g90-adobe-xd
    - carbon-g100-adobe-xd
    - carbon-g10-axure
    - carbon-mid-fi-sketch
    - carbon-wireframe-invision-freehand

Then, Carbon React and the other libraries for Angular, Vue, etc. are indexed like:
library:
  id: carbon-react
  name: Carbon React
  description: React implementation of Carbon Components.
  inherits: carbon-styles

Since designKits gets inherited, then Carbon React, Carbon Angular, etc. have this after keys are inherited:
library:
  id: carbon-react
  name: Carbon React
  description: React implementation of Carbon Components.
  externalDocsUrl: https://react.carbondesignsystem.com
  inherits: carbon-styles
  designKits:
    - carbon-white-sketch
    - carbon-g10-sketch
    - carbon-g90-sketch
    - carbon-g100-sketch
    - carbon-white-figma
    - carbon-g10-figma
    - carbon-g90-figma
    - carbon-g100-figma
    - carbon-white-adobe-xd
    - carbon-g10-adobe-xd
    - carbon-g90-adobe-xd
    - carbon-g100-adobe-xd
    - carbon-g10-axure
    - carbon-mid-fi-sketch
    - carbon-wireframe-invision-freehand

And that's how the design kits page in each library would get populated. E.g., that list of above design kits would show up here for Carbon Components: https://web-app-prototype.j73b4w218e4.us-south.codeengine.appdomain.cloud/libraries/carbon-components/latest/design-kits
And Carbon React: https://web-app-prototype.j73b4w218e4.us-south.codeengine.appdomain.cloud/libraries/carbon-react/latest/design-kits
As well as Carbon Angular, Carbon Vue, etc.


prop paginatorLabels in gridConfig options

Now we can pass to grid config the paginatorLabels object with this (key: 'value default'):

stepBack: '‹'
stepAhead: '›'
jumpBack: '«'
jumpAhead: '»'
first: 'First'
last: 'Last

I can't commited the angular-table.js and angular-table.min.js in dist folder… Ok?

Hi @thotty, thanks for the PR.
There seems to be a merge conflict, please resolve it so i can pull.
Also, please note the comment above about proper camel case naming.
Thanks :)

Oh, man.. My bad! I used a "replace all" functionality and not saw this..
I will correct to send again :smile:

@samu, now is ready to pull... You agree?

@thotty Thanks, great work :smile:

Thank you, @samu.