Virtualization Host Extensions (VHE) support in tf-rmm

We have a question about Virtualization Host Extensions (VHE), which force the host kernel to run in EL2 to reduce virtualization overhead. However, RMM is very similar to a Type 1 hypervisor, and RMM is already running in R-EL2. In your implementation, why do you enable VHE by setting HCR_EL2.E2H? What is the benefit of that? Meanwhile, we found that Hafnium also enables the VHE feature in S-EL2. We are considering enabling the VHE feature in virtCCA, but we are skeptical about whether VHE will improve performance.

Hi @XiangyiXuWashU ,
For RMM, the VHE is enabled mainly for the ability to split the Virtual Address space to High and Low VA spaces. This allows RMM to use the High VA for per CPU private mapping and the Low VA for the global mappings. The private mapping allows RMM to isolate any mappings specific to the Realm to the particular CPU. For more details on how the 2 VA spaces are used, refer here : https://tf-rmm.readthedocs.io/en/latest/design/memory-management.html#rmm-stage-1-translation-regime
This design gives better security properties. Also we have some plans to utilize EL0 of the EL2&0 translation regime to run some parts of RMM at a lower privilege level. So we are seeing this as a capability to enhance security and isolation properties in RMM. I am not sure whether enabling E2H gives any additional performance.

Please feel free to reopen if you have more questions on this topic.


Border theme (theme submission example)

This is an example of what a theme submission could look like. Below is a zip file containing

a CSS file of the theme
a Markdown document with all the necessary front-matter parameters as well as the description of the theme
a border.assets/ folder with screenshots
a thumbnail/ folder with the thumbnail of my theme

border.zip

Closing this issue because due to the pivot to Quarto. This means that the submission file will be slightly different, but I also wanted to redesign the process altogether (to be more seamless).


Use clinfo on linux if found for gpu detection

This is still wip/in testing.
GPU VRAM detection on Linux is very inaccurate: Multiple GPUs are being detected to only have 256 MB of VRAM. By implementing a mix of utilities that can detect GPU information, more accurate system information can be retrieved.
I am using the clinfo command, if found on the user's system, to detect GPUs on the system. Using this allows for a much more accurate VRAM detection, and further opens the option to parse even more graphics information from the system. (Like GPU driver version, core clock, etc.)
@sebhildebrandt Please have a look at this PR and let me know if anything needs to be changed to your preference to create improved GPU information detection on Linux.

@Krish120003 thank you! Well yes, this is a nice approach and I will have a look at it this weekend and return back with comments ;-)

Update: This PR is done.
Limitations: This method is unable to determine thebus and vramDynamic data for each controller.

This PR was created to improve the Graphic Controller detection on Linux systems using the clinfo command line utility if available.
Why use clinfo:

Provides accurate information for graphic controllers compared to lspciFor example, the vram and model properties.  From:
"model": "Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]", "vram": 256
To:
"model": "Radeon RX 580 Series", "vram": 7936
Allows retrieval of additional information that can be appended to the Object.
Allows retrieval of the bus address for a controller without needing sudo access for dmidecode

Changes Made:

A function called parseLinesLinuxClinfo has been added that specifically parses the output from the clinfo --raw command.
The Linux section for the returned Promise has been refactored to compensate for the addition of a new method of controller detection.
Adds the busAddress property to each graphic controller on Linux.

Using clinfo, the value is retrieved from either directly the CL_DEVICE_TOPOLOGY_AMD flag or by converting the CL_DEVICE_PCI_BUS_ID_NV and CL_DEVICE_PCI_SLOT_ID_NV flags into the BDF notation.
Using lspci, the value is retrieved by sub-stringing from the start of the line to the vgapos of the line.

This PR was reviewed by @seniorquico (He mentioned this PR earlier)
@sebhildebrandt The PR is ready for review and ready for merge into the main branch to provide better GPU detection on Linux. Please review it.

@Krish120003 Thank you, will review this the next week. Best regards.

Any thoughts on this PR? We've been using a fork with these changes in our production app for a few weeks now, and it seems to be a big improvement over the previous method of detection. Happy to pitch in with any testing.

@Krish120003 This is now part of the official release ;-) Version 4.32.0 just released


WeightedRandomPrototype is not checked by the yaml linter

It should force users to specify the prototype kind, and then verify that all the given prototypes exist,
See #26579

does yaml even have generics :trollface:

Not AFAIK, it probably needs some custom type serializer to validate it.


When a frame fails to load due to a mixed content issue, the main Page is never considered loaded.

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.0.0
Platform / OS version: ArchLinux (up to date)
URLs (if applicable): https://pste.eu/p/awIC.html
Node.js version: 9.4.0

What steps will reproduce the problem?
Try to load a HTTPS URL including an iframe with a HTTP src (normally blocked with a message like: Mixed Content: The page at '...' was loaded over HTTPS, but requested an insecure resource '...'. This request has been blocked; the content must be served over HTTPS.)
Check this example:
"use strict";
const puppeteer = require("puppeteer");
const url = "https://pste.eu/p/awIC.html";

(async () => {
    const browser = await puppeteer.launch({
        args: [ "--no-sandbox", "--disable-gpu" ]
    });
    const page = await browser.newPage();
    await page.goto(url);
    await browser.close();
})();

Content of https://pste.eu/p/awIC.html
<!DOCTYPE html>
<html>
<head>
    <title></title>
    <meta charset="utf-8" />
</head>
<body>
    <iframe src="http://github.com/"></iframe>
</body>
</html>

What is the expected result?
The page loads. page.goto(...) returns a resolved promise.
What happens instead?
The page never loads. page.goto(...) returns with a rejected promise after a 30 seconds timeout (Error: Navigation Timeout Exceeded: 30000ms exceeded).
Notes
As far as I understand, this is because the iframe never triggers the load event, and the NavigatorWatcher iterates over all iframes to check if a load event occured before resolving the navigationPromise. This issue may need some devtools protocol additions to be fixed.

Shower thought: on top of this, it would be great to have a "requestfailed" event triggered, in the same way loading a script with a mixed content issue fails.

To be honest, I've found the promise returned by goto to be pretty unreliable in general. I've resorted to injecting some code that manually subscribes to events like DOMContentLoaded and load.

I'm having the same issue. You can try this workaround:
"use strict";
const puppeteer = require("puppeteer");
const url = "https://pste.eu/p/awIC.html";

(async () => {
    const browser = await puppeteer.launch({
        args: [ "--no-sandbox", "--disable-gpu" ]
    });
    const page = await browser.newPage();
    await page.evaluate((url)=>{window.location = url}, url);
    await page.waitFor('body > iframe')
    console.log('working!')
    await browser.close();
})();

I'm having the same issue. You can try this workaround:
`"use strict";
const puppeteer = require("puppeteer");
const url = "https://pste.eu/p/awIC.html";

(async () => {
const browser = await puppeteer.launch({
args: [ "--no-sandbox", "--disable-gpu" ]
});
const page = await browser.newPage();
await page.evaluate((url)=>{window.location = url}, url);
await page.waitFor('body > iframe');
console.log('working!');
await browser.close();
})();`
This allow the page to load but there is no way to capture the error.

Same issue, tried --allow-running-insecure-content with no luck.
@GregRos Can you somewhat retrieve a response using this method? What was the status code, the HTTP headers, etc?
How do you navigate without goto? Do you use evaluate(() => window.location = url)?

To be honest, I've found the promise returned by goto to be pretty unreliable in general. I've resorted to injecting some code that manually subscribes to events like DOMContentLoaded and load.

Could u pls share that ?


Super Scaffolding adds "Event" model to roles.yml twice.

config/models/roles.yml

default:
  models:
    Task: read
    Event: read
    Event: read
...
admin:
  ...
  models:
    Task: manage
    Event: manage
    Event: manage
...

It seems to be associated with the word "Event".

Hey @brennanlawrence, thanks for opening the issue. I'm having trouble reproducing, could you tell me what rails g model and Super Scaffolding commands you entered?

@brennanlawrence, any chance you can help with reproduction steps here?

I haven't been able to reproduce this problem, so I'm going to go ahead and close this. Maybe it was fixed somewhere along the way, or maybe it was related to a weird local configuration of some sort. @brennanlawrence feel free to reopen it if you can provide some reproduction steps.


fix: add --force to git push to object pipeline

Overview/Summary
Fix recommendation object creation pipeline
As part of this pull request I have

[ ] Read the Contribution Guide and ensured this PR is compliant with the guide
[ ] Checked for duplicate Pull Requests
[ ] Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
[ ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ ] Ensured PR tests are passing
[ ] Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
[ ] Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

@oZakari Were you able to allow the pipeline to use --force?

Hi @kpoineal, sorry forgot to update you. We need to go a different route as the github-actions bot cannot be added to the list of allowed users to force-push. I have a different route, just need to work through it. Closing this out though and will open separate pr.


[Request] Add seed info tooltip to seed vault

Currently the seed info tooltip doesn't appear when hovering over seeds in the seed vault.
It would be super useful to be able to see this directly from the seed vault, without having to take the seeds out first.

This is a great suggestion I hadn't even thought about, I'll add this to my to-do list!

I have created a Pull Request for this feature to be merged into RuneLite.
Its status can be monitored here: https://github.com/runelite/plugin-hub/pull/2255
I will close this issue once it is successfully merged in.

The update including this feature has been merged into RuneLite, thank you for the suggestion!


Return EINVAL when alignment is not a power of 2 to match posix standard

Dealt with todo in posix_memalign.

I don't think (alignment % 2) != 0 is enough to check whether alignment is a power of 2 or not. Considering alignment is a size_t, which is an unsigned integer type, ((x & (~x + 1)) == x && x != 0) should be sufficient.

I don't think (alignment % 2) != 0 is enough to check whether alignment is a power of 2 or not. Considering alignment is a size_t, which is an unsigned integer type, (x != 0 && (x & (~x + 1)) == x) should be sufficient.

Ah.... I see. I'm too careless to treat a checking of power of 2 as a checking of multiple of 2...

Thank you @JulianATA! I think there is a small mistake still, the test should be (alignment & (~alignment + 1)) != alignment  (i.e. opposite). I merged it in with the latest dev branch (now with a make test target that tests this (among other things)).


Add AWS foundational security standard

This pull request adds support for the AWS Foundational Security Best Practices v1.0.0
standard that was recently added to AWS Security Hub.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@williterate Thanks for the contribution!  Great enhancement that was on the to-do list.


Missing details

Hi,
i want to know which Cuda and CUDNN version this model worked on ??

This code worked for me on Cuda-8.0 and CUDNNv5.0 version since my GPU supported only older versions of CUDNN.


feat: add commitizen and prepare-commit-msg git hook

Adds Commitizen and the prepare-commit-msg git hook.
Suggested by lele3000 via this reddit post: https://www.reddit.com/r/Angular2/comments/1asff4w/comment/kqqk0yb/

Can more be done to enforce better messages via another git hook, perhaps in commit-msg or post-commit?


Request: Print settings

I need set print settings but there are no functions on this API to achieve it.
I think that the implementation could be like worksheet.tabcolor() function.
Exceljs (https://github.com/guyonroche/exceljs) has implemented this by this PR: https://github.com/guyonroche/exceljs/pull/105

i'll work on this if @dtjohnson does not have time :) i could use it in my project as well anyway

Yes me too.
I would appreciate your help :)

My editor is deciding to screw with the formatting.. so I'll have to do
this at home haha
On Sep 25, 2017 11:49 PM, "Francisco Javier Viejo"<EMAIL_ADDRESS>wrote:

Yes me too.
I would appreciate your help :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dtjohnson/xlsx-populate/issues/84#issuecomment-332103100,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF7q0RhkmF2s8z5fcTdQUaz-opBX9Dxjks5smJ6FgaJpZM4Pi7_T
.

@alandoyle95 Ok, don't worry. This is an enhancement and it is not urgent ;)

Would it also be possible to add setting the Print Area as an Enhancement?

Has this been implemented in the meantime, esp. the print area?

Can you please help me add a header and footer to all pages while printing?


Fixed typo in index.html

We auto-generate the documentation in the gh-pages branch.  This is already fixed and will go away the next time the docs are deployed/


Remove msgClient global variable for core-data

Fix #2027
Remove the msgClient global variable in favor of using the DI container
for passing around an instance during bootstrap. Update functions which
were referring to the global variable to instead accept an instance as
function arguments.
Update tests to work with the changes to the production code.
Signed-off-by: Anthony M. Bonafide<EMAIL_ADDRESS>

These changes where verified with passing blackbox tests.

Codecov Report

Merging #2209 into master will increase coverage by 0.01%.
The diff coverage is 27.77%.

@@            Coverage Diff             @@
##           master    #2209      +/-   ##
==========================================
+ Coverage   39.33%   39.35%   +0.01%
==========================================
  Files         175      175
  Lines       12626    12630       +4
==========================================
+ Hits         4967     4970       +3
- Misses       7392     7395       +3
+ Partials      267      265       -2

Impacted Files
Coverage Δ

internal/core/data/router.go
4.35% <0%> (-0.01%)
:arrow_down:

internal/core/data/init.go
0% <0%> (ø)
:arrow_up:

internal/core/data/event.go
62.42% <100%> (+1.91%)
:arrow_up:

Continue to review full report at Codecov.

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


add text provider for chinese simplified

@pigfly88 bump, can we rebase this with latest so we can review?

I am going to close this PR since it is stale. Feel free to reopen it if needed later on.
Thanks for contributing!


Bump function-runner to 6.2.1

WHY are these changes introduced?
Related issue: https://github.com/Shopify/shopify-functions/issues/394
We released a small update to the function-runner.
WHAT is this pull request doing?
This PR bumps the function-runner version so that it is using the latest version.
How to test your changes?

Run a function with the app function run --verbose command. Verify that the debug log line states version 6.2.1.
Run the downloaded binary with the --version flag and verify it's 6.2.1.

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[ ] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes

Failed merging due to a test, but it shouldn't be related to this and CI is green here. Going to try again.


stm32/exti: Add get_level() to ExtiInput

This seems straightforward. Not sure if the method was left out intentionally.

LGTM. Can you fix CI?

thanks!


A11Y in f4: workspace search

see #89111

@roblourens taking this

thanks!

@JacksonKearl nice work, thanks! Adding verified label
As follow up I have created https://github.com/microsoft/vscode/issues/94359


Map mutation efficiency with regard to minimization of copying.

Hi,
They say the so-called persistent hash array mapped trie is used to efficiently implement immutable maps (e.g. in Clojure).
How does this compare to dartz' maps?
See also:
https://github.com/vacuumlabs/persistent-1
https://github.com/google/built_collection.dart/issues/44

Hi @foodchaining!
Yep, Clojure and Scala both used to use HAMT for some of their data structures. At least Scala now uses CHAMP structures by default instead, which improves upon HAMT especially in respect to memory footprint and locality.
IMap, IVector, ISet and some other structures in dartz currently use AVL trees, which are very similar to red-black trees. AVL trees support decently fast and memory efficient lookup, insertion and removal operations. They are also relatively easy (at least for me) to implement and maintain correctly compared to HAMT/CHAMP.
Both HAMT/CHAMP as implemented in clojure/scala and the AVL trees in dartz are persistent data structures, in the sense that derived instances will share structure/memory with their respective original instances. When inserting or removing a leaf node in an AVL Tree, only the log(n) tree nodes on the path between that leaf and the root will be re-allocated, plus possibly a handful of neighbouring nodes if rebalancing is required.
A good and efficient CHAMP implementation in Dart would likely improve the efficiency of certain operations (union, intersection, etc) in some dartz structures and might also prove better overall. I remember the vacuum persistent package you mentioned as being quite sluggish for basic operations though, so it might prove tricky to get good performance.

Thanks for the clarification,
The remaining detail is transients (as defined by Clojure). As far as I can see dartz doesn't have them; would they be useful here if implemented for persistent AVL trees?

Hi again! No, there is nothing resembling transients in dartz at the moment and I can't say I've missed them much personally. Do you have use cases where you believe transients or scala style Buffers/Builders would be significantly more convenient and/or performant?

The use case is a series of inserts, updates and removals where intermediate states are not needed. I don't know whether transients if added to dartz could significantly improve performance. There is however an AVL tree based collection library for Clojure (data.avl). It could be used to estimate the performance difference between persistent and transient variants of batch mutations. I may come up with a test at some point.

Sounds great! I would be very interested to know if transients or similar tricks would enable performance improvements significant enough to justify the associated impurities. If you get somewhere in your investigations before I do, please let me know!

Closing this for now – feel free to reopen!


Deprecate set_state_vector and set_density_matrix

It was accepted at cirq sync that these are vestigial functions from a time when we didn't have initial_state or custom gates or classical controls that could be used for this. Now that we have all these, we can remove this function.
Fixes #4830

LGTM, would you mind adding _deprecated to the end of the test function names so that when we come back later we know we can just delete the test outright ?

Done


Moved taplo back to the default feature in pixi.toml

What
Taplo now supports linux-aarch64 so we no longer need to special-case it (https://github.com/conda-forge/taplo-feedstock/issues/3)
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested the web demo (if applicable):

Using newly built examples: app.rerun.io
Using examples from latest main build: app.rerun.io
Using full set of examples from nightly build: app.rerun.io

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Docs preview
Examples preview
Recent benchmark results
Wasm size tracking

Testing a build run that makes uses of pixi on linux-aarch64: https://github.com/rerun-io/rerun/actions/runs/8355261184


Use new structure for Apt::Source

This puppet module uses the puppetlabs-apt module for installing rabbitmq through Apt.
The apt-module renders warnings about deprecation.
Warning: Scope(Apt::Source[rabbitmq]): $include_src is deprecated and will be removed in the next major release, please use $include => { 'src' => false } instead
Warning: Scope(Apt::Source[rabbitmq]): $key_source is deprecated and will be removed in the next major release, please use $key => { 'source' => https://www.rabbitmq.com/rabbitmq-release-signing-key.asc } instead.
Warning: Scope(Apt::Key[Add key: 0A9AF2115F4687BD29803A206B73A36E6026DFCA from Apt::Source rabbitmq]): $key_source is deprecated and will be removed in the next major release. Please use $source instead.

These deprecations are put in place for the upcomming 2.x release of the apt module, see:
https://github.com/puppetlabs/puppetlabs-apt/commit/396f308e6ad4798461a6471ee8bb8e764d8b03cb

Any progress on this? With the new puppetlabs/apt module released this should be fixed asap.

This needs to be reworked, and may need some additional work after #493 is merged. In addition, the lint warnings and test failures would need to be resolved, and it should be squashed (since it's affecting apt, should also verify that both regular Debian and Ubuntu acceptance tests look Ok).
@dennisdegreef - are you willing to rework this?

Sorry, but I'm not using RabbitMQ anymore :) so there is little incentive for me. I guess I should close this?

Hopefully someone can rework it after we get the other updates for switching over to Voxpupuli done. I will close this one for now.


Using another Formatter Class

I understand that the formatter class acts parsing the data to improve the readibility.
If I want to extends the formatter and use a improved version that I made I can't use the method of the builder setResponseFormatterClass. I needed to change the ClientBuilder.php and add a return $this;
But my formatter class was not being used.
Am I missing something?

Hi, nice catch about the $this, I will fix it.
Can you post the code of your formatter class ?


Links towards bottom don't work in tall labels

In characterIndexAtPoint:, the label calls textRectForBounds:limitedToNumberOfLines::
CGRect textRect = [self textRectForBounds:self.bounds limitedToNumberOfLines:self.numberOfLines];

This is not correct. First, textRectForBounds:limitedToNumberOfLines: will return a measurement based on the unattributed text property, not the attributed string currently in the label. The label should override textRectForBounds:limitedToNumberOfLines: and return an appropriate measurement.
This also means the vertical-alignment code in drawTextInRect: should be pulled out into an appropriately generic method to get the text rect for a given bounds rectangle. Right now links don't take vertical alignment into account at all.
This bug manifests as links towards the bottom of a tall label failing to respond to taps. This is because they are outside the rectangle returned by textRectForBounds:limitedToNumberOfLines:.

+1 for this issue. It's very hard to tap on the links.

I've extracted the verticalAlignment stuff out of drawTextInRect:, so I'm most of the way there to getting this addressed.

Side note, seems like most people use this class for links.  Am I the only one using it to color different substrings different colors?  I guess I have a unique use case...

I am using it for both and I like it because of good performance (comparing with OHAttributedLabel). It's awesome that you could specify custom link handling delegate, this makes possible to parse custom links such as "user://<USER_ID>".

@LongWeekend thanks! that's indeed a very good start at fixing this bug, 1/2 way there.

@adamjernst I have a "dev" branch on the LongWeekend fork.  Try it out if you have a moment -- I've probably introduced some issues, but I also believe I've addressed this issue by providing a textRectForBounds:numberOfLines: implementation.

@adamjernst Update, I've put it on master.


Update MD file on new branch 2017-20-14_12-11-33

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

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.


Is there a possibility to draw chart with dashed lines?

See issue #527.

I saw it, but it wasn't merged.

Is there any possibility that this will be merged?

@tannerlinsley & @etimberg : This seems like something that shouldn't be too tough as long as our config object will support line styles.

@derekperkins definitely possible not sure if it works out of the box now. We can try and see

Fixed in the v2.0-dev branch in #1232


sliding when using step doesn't adhere to the step value and slides by only 1 slide at a time

As the title suggests, if you include step and click the buttons to navigate you step through the number of slides equalling the step value. however if you swipe to navigate you navigate by only 1 at a time. not sure if this is an intentional implementation however it would be nice to have it adhere to the step value when navigating.
https://codesandbox.io/s/vqnq33qwny <- example of the issue.. navigate using the buttons navigates 2 at a time but swiping only navigates 1 at a time.

@NathanGostelow Interesting. This seems like it should maybe be a prop you need to set. It could default to the number of "step" but that may break people's existing implementations?

could have a prop called slideStep, which defaults to 1 which would be additive and not break current implementations of pure-react-carousel?

@NathanGostelow Thanks for the suggestion. I implemented it today using dragStep as a new optional prop on CarouselProvider. This will let you set dragStep={2} and the small drags will navigate 2 at a time the same way the arrows do. The optional prop defaults to 1, so there will not be any changes to existing implementations.
I updated your code sandbox with the change below so you can check it out.
https://codesandbox.io/s/5nkpv2o84


[docs] Update mmdet/models/detectors/base.py

The description of imgs in forward_train is not correct.
Fix #6793

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Jest test failing

Issue description

components: any
reactstrap version #5.0.0-beta.2
import method es(typescript) (if umd, are you using the "full" version (only for v5+)?)
react version #16.2.0

What is happening?
Any Jest test in app created by create-react-app fail to run.
Steps to reproduce issue

create-react-app my-app --scripts-version=react-scripts-ts
npm install --save<EMAIL_ADDRESS>@types/reactstrap
import and use any reactstrap component to App.ts, for ex. Container
npm run test

Error message in console
  ● Test suite failed to run

    C:\temp\my-app\node_modules\react-popper\lib\react-popper.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){export { default as Manager } from './Manager';
                                                                                ^^^^^^

    SyntaxError: Unexpected token export

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/ScriptTransformer.js:289:17)
      at Object.<anonymous> (node_modules/reactstrap/dist/reactstrap.cjs.js:14:19)
      at Object.<anonymous> (src/App.tsx:15:20)

I don't think the reason is typescript.
As I understood, Jest runs as node process, and create-react-app setup jest to not transpile any files under node_modules folder. Since react-popper/package.json conains  "main": "lib/react-popper.js", and version under /lib contains es6' export statements, node finally gets those export statements and fails. If I change react-popper/package.json to point main to dist:  "main": "dist/react-popper.js", tests pass.

I can only confirm I have the very same issue. My app is created using create-react-apps
`
src/App/App.test.js
● Test suite failed to run
/Users/venelin/projects/stylbum-web-v2/node_modules/react-popper/lib/react-popper.js:1
({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){export { default as Manager } from './Manager';
                                                                                ^^^^^^

SyntaxError: Unexpected token export

  at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/ScriptTransformer.js:289:17)
  at Object.<anonymous> (node_modules/reactstrap/dist/reactstrap.cjs.js:14:19)

`

I am also seeing the same issue.

So do I(

Quick fix - revert to "reactstrap": "5.0.0-beta". It has older react-popper version.

Same issue

same cause, but made my react projects cannot run in node.js for server rendering
i saw once that #835 has upgraded the react-popper to ^0.8.2, in which the release of the<EMAIL_ADDRESS>has correctly transformed babel-fied JSX code in lib/, but for some reason the ^0.8.2 description in package.json is being rewritten back as 0.8.1

https://github.com/reactstrap/reactstrap/commit/b515e6bbb137443550f9ea7b0b2ba48113ebd169
reverted the updated react-popper down to 0.8.1.  That commit claims to fix the broken build, so I'm not sure what is going on as it does the opposite for me.

Same issue here. Reverted my reactstrap version to 5.0.0-beta and it is resolved. Thanks @sinxwal

Same here, any news?

The PR in react-popper has been merged, just waiting on it to be published in a release.


Returning strings from server functions with some specific characters causes hydration errors (e.g '`')

Which project does this relate to?
Start
Describe the bug
Returning strings with some specific characters causes hydration errors e.g:
import { Outlet, createFileRoute } from "@tanstack/react-router";
import { createServerFn } from "@tanstack/start";

export const Route = createFileRoute("/")({
  loader: async () => {
    return await getSomeDataWithError();
  },
  component: LayoutComponent,
});

const getSomeDataWithError = createServerFn("GET", async () => {
  return {
    test: "test",
    error: "`", // This will cause hydration errors
  };
});

function LayoutComponent() {
  const { test } = Route.useLoaderData();
  return (

{test}

        <Outlet />

  );
}

Your Example Website or App
https://stackblitz.com/edit/tanstack-router-2feezb?file=app%2Froutes%2Freproduce.tsx
Steps to Reproduce the Bug or Issue
Check the /reproduce route
Expected behavior
We should be able to return any kind of valid strings from our server functions.
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

this is fixed now


[FLINK-6569] flink-table KafkaJsonTableSource example doesn't work.

This PR makes the proposed changes on the document and changes the Java unit tests to reflect the suggested usages of the API.

Thank you for addressing this so quickly.
+1 from my side.

-1
@haohui The examples are correct if you use Types class of the Table API: org.apache.flink.table.api.Types

My understanding is that the snippet should only depend on the Java version of the API (ROW_NAMED in flink-core) instead of the one written in Scala that resides in flink-table. Correct?

The Java version of the API also depends on the Scala classes of flink-table. Everything in org.apache.flink.table.api is used in both languages. org.apache.flink.table.api.scala/java contain language specific classes.

@haohui can you close this PR?


Object.assign polyfill is not being transformed correctly

Prerequisites

[X] I have read the documentation.

Description
When loading the form in an ES5 browser, I get the standard "Undefined is not a function" due to the Object.assign in https://github.com/mozilla-services/react-jsonschema-form/blob/3f36b18cb3a5c233def17747bc4145142ec3d955/src/components/Form.js#L125
In issue #206 it sounds like there is a consensus that babel should be transforming those polyfills, but I .babelrc doesn't seem to have any plugin that tackle Object.assign.
Prob this is the reason you had to load a polyfill specifically.
I wonder if that's intentional. I could use a polyfill library, but I'd prefer if your official npm build transforms that polyfill as well.
I'm using babel with babel transform-runtime on my side, but not recompiling any of the nodes_modules.
Steps to Reproduce

Create a simple react component that uses Form
Run it without any polyfill libraries in an ES5 browser (I'm using an old chromium version)

Expected behavior
The form actually loading
Actual behavior
"Undefined is not a function" due to the Object.assign (and no polyfill being loaded)
Version
0.40 (latest)

Any workaround for this?

@makosblade  Maybe you can try the babel-plugin-transform-object-assign work around here https://github.com/react-toolbox/react-toolbox/issues/45 .

Considering that most users of react-jsonschema-form will have to support IE11 for still some time, doing a transform of Object.assign is simply a no-brainer. It will save everyone a good deal of frustration and unnecessary complexity with no appreciable downsides.
It seems to only be a matter of prepending this to the list of plugins in .babelrc:
    "transform-object-assign",

I encourage you to just get it over with, so you can close this issue 🙏

We've fixed it already @dalgard

That's great news 👍👍
I was just about to make the concession that IE11 appears to need several other things besides Object.assign to run react-jsonschema-form.
I'll look for the latest version, then. How did you fix it?

You should probably bump the minor version number, since supporting IE11 is a new feature.

https://github.com/mozilla-services/react-jsonschema-form/pull/982

I guess we can close this.

try to reset IE11 cache,
i got the same problem.
Included
"transform-object-assign" in .babelrc file
tryed npm start, and.. it didnot transpiled also, i upset, went drink coffee,
get back and i started work! Suddenly!

Considering that most users of react-jsonschema-form will have to support IE11 for still some time, doing a transform of Object.assign is simply a no-brainer. It will save everyone a good deal of frustration and unnecessary complexity with no appreciable downsides.
It seems to only be a matter of prepending this to the list of plugins in .babelrc:
    "transform-object-assign",

I encourage you to just get it over with, so you can close this issue 🙏


input-date-time-range: change test to no longer flake

Problem:
Between 5 - 6 pm some of the tests end up being run on a machine that has its timezone set to Central Europe Time. In 2020, CET had Daylight Savings time end on Oct 25. Since our difference calculation for shifting dates is done using Date, because of the time change it becomes off by 1 hour (https://github.com/BrightspaceUI/core/blob/master/components/inputs/input-date-time-range.js#L34).
"Solution":
I shifted all the tests to be further from that time shift.
What does this mean:
This is how our old date picker behaved as well and is not new. How it normally exhibits itself is that when a user picks a date that moves start to one side of daylight savings and end to the other side, the end time shifts by an hour. This usually should seem fine to a user since they would in theory have their system set to the same timezone as their LMS. This does bring up the interesting case where if the system timezone is different than the LMS timezone then they would see that weird shifting on a different date than potentially expected. In practice I don't think this would cause any user error as the user is likely to change the time anyways.

Wow crazy, awesome digging to figure that out! So they actually run the tests on different machines at different times of the day?!
I agree it doesn't sound like this is going to result in user errors, and just shifting the times around to fix the "flake" (I guess not really since it's consistent) makes sense to me.

😮


Overhaul libp2p-crypto

Version: N/A
Platform: N/A
Subsystem: N/A

Type: Enhancement
Description:
One of the pain points of development within a browser context is the bundle size of a web app, which easily gets quite big and makes web pages take longer times to run. In js-libp2p land, we have been working over the last months on reducing the bundle size of the library to the minimum possible, so that js-libp2p users in the browser don't need to have a large bundle size just for using this library.
One of the outstanding issues to have our bundle size in a considerably good shape is the crypto libraries that we need to carry. The JS ecosystem around cryptography is far from perfect, which has made us use several different libraries to achieve different cryptographic primitives.
Taking into account that libp2p is a composable and modular stack, most of the times js-libp2p bundle contains heavy crypto code that is not needed. In this context, js-libp2p crypto should be modular and pluggable, so that the users can bring just what they need instead of the all thing.

Closing as duplicate of https://github.com/libp2p/js-libp2p/issues/2086


Testability | Missing getter setter methods

Hi,
I wanted to use your class in a project, because it provides a convenient object oriented wrapper around the php curl functions, which would make unit testing my code easier. At least i thought so. Now that I started to get my test coverage up, I found the problem, that accessing the response etc. is just done by accessing the attributes on the curl object directly. I wanted to mock out your class from my code to test my class. My function looks like this:
public function request()
  {
    /** @var \Curl\Curl $curl */
    $curl = $this->handler;

    $curl->setOpt(CURLOPT_CUSTOMREQUEST, 'POST');
    $curl->setOpt(CURLOPT_POST, true);
    $curl->setOpt(CURLOPT_HTTPHEADER,     array("Content-Type: application/json","Content-Length: " . strlen($this->request)));
    $curl->setOpt(CURLOPT_POSTFIELDS, $this->request);
    $curl->setURL($this->url);
    $curl->exec();

    $this->response = $curl->rawResponse;
  }

Because there is no getter function for the response I'm not able to mock out your curl class. Could you provide a fix for that issue or should I create a pull request for you (since its just generate getter/setters in the IDE)?

Hi. A pull request would be great. Are you looking for something like this?
public function getResponse() {
    return $this->response;
}

Exactly

Hi, I'm revisiting this issue. If you'd like to test things you can pull in #529. Thank you


How to calculate depth in Meters from the depth map in numpy

Hello, I  have been working on a project of object detection and depth estimation. This model aligns to the my project requirements. I am using your pretrained model to test model accuracy on my own dataset. Can you please provide formula or method on how to calculate exact depth in meters from the depth map generated using your model. I cannot find any information in the research paper too related to this.
Please provide sufficient information so that I can contine to use this model for my project. Thanks!

Have you implemented any techniques or formula to convert the generated depth map into exact distance values ?

Hi, the prediction is up to unknown scale and shift factors. If you need metric depth (in meter), you can use other information as guidance to align, e.g. lidar point measurement, or taking other metric depth prediction and align our prediction to it.

Hi, the prediction is up to unknown scale and shift factors. If you need metric depth (in meter), you can use other information as guidance to align, e.g. lidar point measurement, or taking other metric depth prediction and align our prediction to it.

Actually, I've found that even after aligning the data using this method, the results are still not ideal. The estimated affine-invariant depth is not consistently accurate. I've tested this approach on several autonomous driving datasets, and even after applying proper scale and shift adjustments, the geometric results are still not correct. I believe that if the method could be fine-tuned for specific datasets, the metric performance could be significantly improved. Therefore, I'd like to ask how I can fine-tune this method to achieve better metric results.


Autocomplete: Disable browser autocomplete.

Prerequisites

[X] I have searched for duplicate or closed feature requests
[X] I have read the Modus style guidelines

Proposal
Add a new property to allow users to disable the browser autocomplete in the input.
<input type="text" autocomplete="off">
Motivation and context
No response
What is the issue regarding ?
@trimble-oss/modus-web-components
Priority
Medium
What product/project are you using Modus Components for ?
e-builder
What is your team/division name ?
e-builder
Are you willing to contribute ?
Yes
Are you using Modus Web Components in production ?
No response

Looks like you have exposed a 'autocomplete' property to the AutoCompleteInput. Trying to understand the issue here. Does this mean, the user can have a AutoComplete component with the 'autocomplete' property disabled?

@rthanga1 We want to disable the browser autocomplete/autofill behavior in the input element inside the modus-autocomplete.

@yohernandez I don't think the autocomplete should have the option for setting this, but I can see potential value in the setting for the textbox.  So the autocomplete would just set it manually to false without giving the user a choice.  I will need to check a few other libraries to see how they handle this.


support slider color

Small change to allow a color property string to be passed in.

Bit more work than I thought to fully test with reverse, vertical, etc...


[gui error report] Error: Initializing daemon...

👉 Please describe what you were doing when this error happened.
Enabled PubSub
Enabled IPNS over PubSub
Specifications

OS: darwin 19.6.0
IPFS Desktop Version: 0.24.0
Electron Version: 19.0.9
Chrome Version: 102.0.5005.167

Error
Error: Initializing daemon...
Kubo version: 0.15.0
Repo version: 12
System version: amd64/darwin
Golang version: go1.18.5

Error: lock /Users/glenn/.ipfs/repo.lock: someone else has the lock

    at errorTemplate (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:78:49)
    at loadWindow (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:129:26)
    at showMigrationPrompt (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/migration-prompt.js:134:3)
    at startIpfsWithLogs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:193:9)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async startDaemon (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/daemon.js:216:27)
    at async startIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:48:17)
    at async IpcMainImpl.restartIpfs (/Applications/IPFS Desktop.app/Contents/Resources/app.asar/src/daemon/index.js:102:5)

Thanks for submitting this issue.
We have instructions in our FAQ for getting passed repo.lock errors, can you try to follow the instructions at https://github.com/ipfs/ipfs-desktop#i-got-a-repolock-error-how-do-i-resolve-this and let us know if you're still experiencing issues?


Better handling of namespaces to be ignored

The code currently handling the ignored namespaces can be improved by using a Set.
The Go SDK doesn't offer this type yet, but there's this library that does that: https://github.com/deckarep/golang-set
The main function should build a Set populated with all the namespaces to be ignored, and then use the ignoredNamespacesSet.Contains function to quickly determine whether a namespace has to be ignored.
As bonus points, using a Set built in a dynamic fashion would allow the code to be extended to allow the user to provide his own list of namespaces to ignore

Makes sense to build a set. I'll look into it.
For the users own list of namespaces, a label instead of name of the namespaces could be implemented.
meaning that the user could purposely label the namespace and match that label in the manifest for exclusion.
sounds good?

For the users own list of namespaces, a label instead of name of the namespaces could be implemented.
meaning that the user could purposely label the namespace and match that label in the manifest for exclusion.
sounds good?

Yes and no... someone could abuse this system to have his namespace unrestricted. It's all up to you how to implement that.
You could just start with an environment variable that takes a comma separated list of names


Revert "[CONTP-312] duplicate pod and deployment metadata with address aliasing (#27506)"

What does this PR do?

This reverts commit e1ae6d8e4c5c68cc66946426ebd3fed11953770d.
Motivation

We noticed significant memory increase on nightlies.
Reverting before the freeze to have more time to investigate.
Additional Notes

This PR is only reverting duplicating pod and deployment metadata into kubernetes_metadata entities in workloadmeta.
Other changes done in the reverted PR are preserved. Examples:

Storing deployments annotations in deployments entities
Storing GVR by reference

Possible Drawbacks / Trade-offs

Reverting has no impact on any other component in the agent.
Describe how to test/QA your changes

Sanity Check and E2E should be enough.

/merge


No file

The Github repository did not contain Python file.

It's just the start, I am currently working on the main file and resolving the debug errors and I just don't want to mess this up. In the upcoming versions you'll be able to make use of this tool.


[Swift] Made SortDescriptor conform to Equatable & StringLiteralConvertible

This makes it much cleaner to sort by multiple properties:
// before
results.sorted([SortDescriptor(property: "a"), SortDescriptor(property: "b"), SortDescriptor(property: "c")])
// after
results.sorted(["a", "b", "c"])

/cc @tgoyne @segiddins @bdash

:+1:

:+1:
Changelog stuff will be in the wrong section.


GEP: Add Timeouts GEP first cut

What type of PR is this?
/kind gep
What this PR does / why we need it:
This PR adds a first attempt at systematizing the discussion around timeouts in Gateway API.
It also adds support for Markdown tables and MermaidJS diagrams to our mkdocs installation.
Which issue(s) this PR fixes:
Updates #1742
Does this PR introduce a user-facing change?:

NONE

I'd recommend checking the preview at https://deploy-preview-1744--kubernetes-sigs-gateway-api.netlify.app/geps/gep-1742/ to see the diagrams properly.

This GEP definitely needs some more information to be viable, but could be merged as-is because it's provisional anyway.

/hold for multiple review

oh, actually, we already have another maintainer review, sorry @Xunzhuo.
/unhold


push_notifs: Make push_notifications_enabled more resistant to flapping.

Fixes #28403
Uses redis to remember the last time push notifications were experienced working. This needs to work across processes, so can't be done just in memory.

Overall strategy lgtm, posted a few comments.

@timabbott Addressed the above comments.

Uses redis to remember the last time push notifications were experienced
working. This needs to work across processes, so can't be done just in
memory.

One thing I would like to hear more about is why we're using Redis for this.  Most of the time, when we want to store something that we reference across processes, we use PostgreSQL.  Why Redis, here?

One thing I would like to hear more about (in the commit message, if nowhere else) is why we're using Redis for this. Most of the time, when we want to store something that we reference across processes, we use PostgreSQL. Why Redis, here?

@alexmv  Hmm the idea was that this is a pretty transient data structure, and we've sometimes used redis for that. like for rate limiting or for the transient authentication state in social auth flows. And it's a "single row only" kind of data that doesn't require a db table for storing many rows. I wouldn't mind tweaking this to just use a db table if that feels like it'll be significantly cleaner.

I think all of that logic is fine, I'd just like it recorded for posterity. :)
Specifically, it's useful to have explicitly recorded that we believe this to be transient data which is fine if we lose it.  From the services management standpoint, we currently manage redis in a way which is compatible with that (e.g. it is explicitly marked as non-durable) so when we introduce a new use-case for it (which is rare!) it's helpful to reiterate that this is compatible with that property.

Oops, I forgot to update the commit message and re-push. Done now.

edit: Which also somewhat begs the question "is this better in memcached?" but I don't think that we have any good arguments for one over the other, so there's no "wrong" answer

Yeah. As far as I'm aware we only use memcached for traditional caching, and not for storing arbitrary transient data structures like this - so this is just about consistency for me. But the choice feels pretty arbitrary. I suppose we'd prefer to do memcached if we thought it's valuable to decrease (or avoid increasing) our dependency on redis over time - but I'm not aware of such concerns or plans to phase it out.

Tagging this with integration review given that all the feedback has been addressed I think

Merged, thanks @mateuszmandera! Glad to have this finished.


[BUG] WithCalculatedFormulas does not work with OnEachRow

Prerequisites

[x] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[x] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[x] Checked that your issue isn't already filed.
[x] Checked if no PR was submitted that fixes this problem.
[x] Filled in the entire issue template

Versions

PHP version: 7.2
Laravel version: 6.x
Package version: 3.1

Description
WithCalculatedFormulas doesn't appear to work with OnEachRow.
Steps to Reproduce

Create an Import class
add implements OnEachRow, WithCalculatedFormulas to class
Run the import and observe the formula is not calculated
Then open ~/vendor/maatwebsite/excel/src/Cell.php and find public function getValue($nullValue = null, $calculateFormulas = false, $formatData = true). Force $calculateFormulas = true
Run the import and observe the formula is now calculated

Expected behavior:
Implementing WithCalculatedFormulas should set $calculateFormulas = true
Actual behavior:
The original Excel formula is imported

If you could provide a failing tests that would be useful to understand what's going wrong

I got same issue.

Hi @949mac ,
I think in the function onRow, you have to pass the $calculateFormulas option to $row->toArray(null, true).

Hello @ngocongcan,
Ah, beautiful! Thank you very much.
Best Regards,
Mike

Thats not really intuitive. I would definitely expect, that I get the row with calculateFormulas by default.
Thanks @ngocongcan


uploading PDF and doc

Could you please let me know the file type string to be used with fileRestrictions("myFileUploads", {
allowedFileTypes:[]}  to upload a word document or a PDF .

You can restrict it by mime type. Just find your mime type here for the files you need.
https://www.sitepoint.com/web-foundations/mime-types-complete-list/

Thank you .

I just had a bear of a time getting MS Word docs recognized. Turns out that the file I was using didn't have the MIME type set properly. Tested it on a different machine with a newly saved file and it worked. But it took me a long time going through a bunch of variants on the massive openxml mime type until I got it. One thing that helped was outputting the error when the file wasn't allowed by Slingshot. Then I just used the value that slingshot reported back to me as the mimetype. Hope this helps someone.


[Bug][Cosmetics][2.2.0.rc.2] Compilation progress indication is not being displayed cleanly in Windows Command Prompt.

Do you want to request a feature or report a bug?
A bug.
If the current behavior is a bug, please provide the steps to reproduce.
0. You probably need Windows to reproduce it. Problem is reproducible with the Command Prompt and with Cmder.

git clone https://github.com/d-ph/bugreport-webpack-cli-progress-windows.git
cd bugreport-webpack-cli-progress-windows
npm install
npm run build

Result:
During compilation, the progress indication is not being cleanly displayed. See the following gif:

What is the expected behavior?
During compilation, the progress indication is being cleanly displayed.
Please mention other relevant information such as the browser version, Node.js version, Operating System and programming language.
Windows 10, Ms Command Prompt or Cmder

Thanks for your clear bug report. Would you be interested in doing a PR for this? We can certainly use help for this. The relevant code can be found here.

I can try. Let me see.

As I mentioned in the PR, the problem isn't solved entirely by that PR. Now the progress indicator stays in one place, but still isn't right:

I found, that the problem lies in the fact, that virtually anything can console.log() during the progress output, which breaks Windows' terminal. Long story short: This is something nothing can be done about.
But there is a workaround: don't use prescripts in npm. I.e. instead of this:
"scripts": {
    "clean": "rimraf dist",
    "prebuild": "npm run clean",
    "build": "webpack --progress --hide-modules"
  },

use this:
"scripts": {
    "clean": "rimraf dist",
    "build": "npm run clean && webpack --progress --hide-modules"
  },

which will work in any terminal, any OS. Seems like this is npm's problem and not webpack's.
Bottom line: it's a Won't Fix


Svelte is listed in the compatible languages

My .svelte files don't ever pull in the highlights.
If I copy and paste the javascript in the svelte file to a .js file it colors it immediately.
Is there anything special we need to do enable code highlighting inside

Hey, sorry to say but if you are referring to a language inside of another, like how you can have JavaScript code in a html file, those are embedded languages and as per Issue #6 there is not support for that yet. Only comments in the native language of the document is supported. I am looking to rework this extension soon so who knows, I may find a solution to that problem.

As I have been working on other fixes I have become more confident that embedded languages may be possible to support, I will start work on that soon. If I can manage this It will be the only extension that I know of that's able to handle embedded language comment highlighting for any language instead of being hard coded to support specific ones. In the meantime I will close this issue as a duplicate of #6.


Istio 1.20 | http/1.1 protocol error: INVALID_HEADER_FORMAT

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Hi Team,
after upgrading Istio 1.20 from version 1.19.4 , we started observing that istio sidecars is closing upstream connection,
We are using nginx as edge application server and we have found this issue while nginx is trying to connect with other upstream server deployed on same eks cluster.
I have attached log in addition details, for now we have downgraded istio to 1.19.4 and our services are healthy now.
Version
istio helm chart version: 1.20

kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.27.2
Kustomize Version: v5.0.1
Server Version: v1.28.3-eks-4f4795d

Additional Information
2023-12-07T11:50:35.815878Z     debug   envoy router external/envoy/source/common/router/router.cc:520  [Tags: "ConnectionId":"17","StreamId":"11382593540940922209"] cluster 'inbound|8443||' match for URL '/api/user-agreement/v1/screen/ping'  thread=23
2023-12-07T11:50:35.815916Z     debug   envoy upstream external/envoy/source/common/upstream/upstream_impl.cc:426       transport socket match, socket default selected for host with address <IP_ADDRESS>:8443   thread=23
2023-12-07T11:50:35.815922Z     debug   envoy upstream external/envoy/source/extensions/clusters/original_dst/original_dst_cluster.cc:81        Created host inbound|8443||<IP_ADDRESS>:8443 <IP_ADDRESS>:8443.     thread=23
2023-12-07T11:50:35.815982Z     debug   envoy router external/envoy/source/common/router/router.cc:732  [Tags: "ConnectionId":"17","StreamId":"11382593540940922209"] router decoding headers:
':authority', 'api.dev.huru.co'
':path', '/api/user-agreement/v1/screen/ping'
':method', 'GET'
':scheme', 'https'
'x-forwarded-for', '<IP_ADDRESS>,<IP_ADDRESS>'
'x-forwarded-proto', 'https'
'x-forwarded-port', '443'
'x-amzn-trace-id', 'Root=1-6571b18b-329daa99109999bb51621b89'
'accept', '*/*'
'accept-encoding', 'deflate, gzip'
'content-type', 'application/json'
'device-id', '3832323432393936'
'user-agent', '{appVersion:1.0.0,browser:NA,browserVersion:NA,deviceId:3832323432393936,ipAddress:,macAddress:,osVersion:,platform:Android}'
'x-envoy-external-address', '<IP_ADDRESS>'
'x-request-id', 'da33f67b-3929-42d1-9898-f88decdea89f'
'x-envoy-attempt-count', '1'
'x-b3-traceid', '8840d265f51110b737fbb237aae99fa8'
'x-b3-spanid', '37fbb237aae99fa8'
'x-b3-sampled', '0'
'x-forwarded-client-cert', 'By=spiffe://cluster.local/ns/dev/sa/default;Hash=36d32cb942a7578c5248589c402a09a3506be7408950eade636f9060ebe20e4a;Subject="";URI=spiffe://cluster.local/ns/istio-system/sa/istio-ingressgateway'
        thread=23
2023-12-07T11:50:35.816013Z     debug   envoy pool external/envoy/source/common/http/conn_pool_base.cc:78       queueing stream due to no available connections (ready=0 busy=0 connecting=0)   thread=23
2023-12-07T11:50:35.816021Z     debug   envoy pool external/envoy/source/common/conn_pool/conn_pool_base.cc:291 trying to create new connection thread=23
2023-12-07T11:50:35.816026Z     debug   envoy pool external/envoy/source/common/conn_pool/conn_pool_base.cc:145 creating a new connection (connecting=0)        thread=23
2023-12-07T11:50:35.816091Z     debug   envoy connection external/envoy/source/common/network/connection_impl.h:98      [Tags: "ConnectionId":"48"] current connecting state: true      thread=23
2023-12-07T11:50:35.816101Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:57       [Tags: "ConnectionId":"48"] connecting  thread=23
2023-12-07T11:50:35.816106Z     debug   envoy connection external/envoy/source/common/network/connection_impl.cc:1009   [Tags: "ConnectionId":"48"] connecting to <IP_ADDRESS>:8443       thread=23
2023-12-07T11:50:35.816170Z     debug   envoy upstream external/envoy/source/extensions/clusters/original_dst/original_dst_cluster.cc:231       addHost() adding inbound|8443||<IP_ADDRESS>:8443 <IP_ADDRESS>:8443. thread=14
2023-12-07T11:50:35.816177Z     debug   envoy connection external/envoy/source/common/network/connection_impl.cc:1028   [Tags: "ConnectionId":"48"] connection in progress      thread=23
2023-12-07T11:50:35.816208Z     debug   envoy connection external/envoy/source/common/network/connection_impl.cc:746    [Tags: "ConnectionId":"48"] connected   thread=23
2023-12-07T11:50:35.816222Z     debug   envoy upstream external/envoy/source/common/upstream/cluster_manager_impl.cc:1474       membership update for TLS cluster inbound|8443|| added 1 removed 0      thread=22
2023-12-07T11:50:35.816223Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:88       [Tags: "ConnectionId":"48"] connected   thread=23
2023-12-07T11:50:35.816229Z     debug   envoy upstream external/envoy/source/common/upstream/cluster_manager_impl.cc:1480       re-creating local LB for TLS cluster inbound|8443||     thread=22
2023-12-07T11:50:35.816234Z     debug   envoy pool external/envoy/source/common/conn_pool/conn_pool_base.cc:328 [Tags: "ConnectionId":"48"] attaching to next stream    thread=23
2023-12-07T11:50:35.816240Z     debug   envoy pool external/envoy/source/common/conn_pool/conn_pool_base.cc:182 [Tags: "ConnectionId":"48"] creating stream     thread=23
2023-12-07T11:50:35.816243Z     debug   envoy upstream external/envoy/source/common/upstream/cluster_manager_impl.cc:1474       membership update for TLS cluster inbound|8443|| added 1 removed 0      thread=14
2023-12-07T11:50:35.816247Z     debug   envoy upstream external/envoy/source/common/upstream/cluster_manager_impl.cc:1480       re-creating local LB for TLS cluster inbound|8443||     thread=14
2023-12-07T11:50:35.816251Z     debug   envoy router external/envoy/source/common/router/upstream_request.cc:563        [Tags: "ConnectionId":"17","StreamId":"11382593540940922209"] pool ready        thread=23
2023-12-07T11:50:35.816280Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:141      [Tags: "ConnectionId":"48"] encode complete     thread=23
2023-12-07T11:50:35.816318Z     debug   envoy upstream external/envoy/source/common/upstream/cluster_manager_impl.cc:1474       membership update for TLS cluster inbound|8443|| added 1 removed 0      thread=23
2023-12-07T11:50:35.816331Z     debug   envoy upstream external/envoy/source/common/upstream/cluster_manager_impl.cc:1480       re-creating local LB for TLS cluster inbound|8443||     thread=23
2023-12-07T11:50:35.816563Z     debug   envoy filter external/envoy/source/extensions/filters/listener/original_dst/original_dst.cc:69  original_dst: set destination to <IP_ADDRESS>:8443    thread=22
2023-12-07T11:50:35.816653Z     debug   envoy filter external/envoy/source/extensions/filters/listener/http_inspector/http_inspector.cc:139     http inspector: set application protocol to http/1.1    thread=22
2023-12-07T11:50:35.816735Z     debug   envoy conn_handler external/envoy/source/extensions/listener_managers/listener_manager/active_tcp_listener.cc:159       [Tags: "ConnectionId":"49"] new connection from <IP_ADDRESS>:34424        thread=22
2023-12-07T11:50:35.816769Z     debug   envoy http external/envoy/source/common/http/conn_manager_impl.cc:391   [Tags: "ConnectionId":"49"] new stream  thread=22
2023-12-07T11:50:35.816871Z     debug   envoy http external/envoy/source/common/http/conn_manager_impl.cc:1194  [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] request headers complete (end_stream=true):
':authority', 'identity.dev.svc.cluster.local'
':path', '/api/user-agreement/v1/screen/ping'
':method', 'GET'
'x-forwarded-for', '<IP_ADDRESS>,<IP_ADDRESS>'
'x-forwarded-proto', 'https'
'x-forwarded-port', '443'
'x-amzn-trace-id', 'Root=1-6571b18b-329daa99109999bb51621b89'
'accept', '*/*'
'content-type', 'application/json'
'device-id', '3832323432393936'
'user-agent', '{appVersion:1.0.0,browser:NA,browserVersion:NA,deviceId:3832323432393936,ipAddress:,macAddress:,osVersion:,platform:Android}'
'x-envoy-external-address', '<IP_ADDRESS>'
'x-request-id', 'da33f67b-3929-42d1-9898-f88decdea89f'
'x-envoy-attempt-count', '1'
'x-forwarded-client-cert', 'By=spiffe://cluster.local/ns/dev/sa/default;Hash=36d32cb942a7578c5248589c402a09a3506be7408950eade636f9060ebe20e4a;Subject="";URI=spiffe://cluster.local/ns/istio-system/sa/istio-ingressgateway'
'x-b3-traceid', '8840d265f51110b737fbb237aae99fa8'
'x-b3-spanid', '517793f4bae4b6f2'
'x-b3-parentspanid', '37fbb237aae99fa8'
'x-b3-sampled', '0'
        thread=22
2023-12-07T11:50:35.816891Z     debug   envoy http external/envoy/source/common/http/conn_manager_impl.cc:1177  [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] request end stream        thread=22
2023-12-07T11:50:35.816912Z     debug   envoy connection external/envoy/source/common/network/connection_impl.h:98      [Tags: "ConnectionId":"49"] current connecting state: false     thread=22
2023-12-07T11:50:35.816967Z     debug   envoy filter source/extensions/filters/http/alpn/alpn_filter.cc:92      override with 3 ALPNs   thread=22
2023-12-07T11:50:35.816981Z     debug   envoy router external/envoy/source/common/router/router.cc:520  [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] cluster 'outbound|8443||identity.dev.svc.cluster.local' match for URL '/api/user-agreement/v1/screen/ping'   thread=22
2023-12-07T11:50:35.817024Z     debug   envoy router external/envoy/source/common/router/router.cc:732  [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] router decoding headers:
':authority', 'identity.dev.svc.cluster.local'
':path', '/api/user-agreement/v1/screen/ping'
':method', 'GET'
':scheme', 'https'
'x-forwarded-for', '<IP_ADDRESS>,<IP_ADDRESS>'
'x-forwarded-proto', 'https'
'x-forwarded-port', '443'
'x-amzn-trace-id', 'Root=1-6571b18b-329daa99109999bb51621b89'
'accept', '*/*'
'content-type', 'application/json'
'device-id', '3832323432393936'
'user-agent', '{appVersion:1.0.0,browser:NA,browserVersion:NA,deviceId:3832323432393936,ipAddress:,macAddress:,osVersion:,platform:Android}'
'x-envoy-external-address', '<IP_ADDRESS>'
'x-request-id', 'da33f67b-3929-42d1-9898-f88decdea89f'
'x-envoy-attempt-count', '1'
'x-b3-traceid', '8840d265f51110b737fbb237aae99fa8'
'x-b3-spanid', '517793f4bae4b6f2'
'x-b3-parentspanid', '37fbb237aae99fa8'
'x-b3-sampled', '0'
'x-envoy-decorator-operation', 'identity.dev.svc.cluster.local:8443/*'
'x-envoy-peer-metadata-id', 'sidecar~<IP_ADDRESS>~apigateway-775dfbf8d7-qpkvg.dev~dev.svc.cluster.local'
'x-envoy-peer-metadata', 'CiIKDkFQUF9DT05UQUlORVJTEhAaDmFwaWdhdGV3YXktYXBwChoKCkNMVVNURVJfSUQSDBoKS3ViZXJuZXRlcwocCgxJTlNUQU5DRV9JUFMSDBoKMTAuMTEuODguOAoZCg1JU1RJT19WRVJTSU9OEggaBjEuMjAuMAq6AQoGTEFCRUxTEq8BKqwBChMKA2FwcBIMGgphcGlnYXRld2F5CiQKGXNlY3VyaXR5LmlzdGlvLmlvL3Rsc01vZGUSBxoFaXN0aW8KLwofc2VydmljZS5pc3Rpby5pby9jYW5vbmljYWwtbmFtZRIMGgphcGlnYXRld2F5CiwKI3NlcnZpY2UuaXN0aW8uaW8vY2Fub25pY2FsLXJldmlzaW9uEgUaA2RldgoQCgd2ZXJzaW9uEgUaA2RldgoaCgdNRVNIX0lEEg8aDWNsdXN0ZXIubG9jYWwKJQoETkFNRRIdGhthcGlnYXRld2F5LTc3NWRmYmY4ZDctcXBrdmcKEgoJTkFNRVNQQUNFEgUaA2RldgpKCgVPV05FUhJBGj9rdWJlcm5ldGVzOi8vYXBpcy9hcHBzL3YxL25hbWVzcGFjZXMvZGV2L2RlcGxveW1lbnRzL2FwaWdhdGV3YXkKiQEKEVBMQVRGT1JNX01FVEFEQVRBEnQqcgooChVhd3NfYXZhaWxhYmlsaXR5X3pvbmUSDxoNbWUtY2VudHJhbC0xYQooCg9hd3NfaW5zdGFuY2VfaWQSFRoTaS0wZWQ1ZDcwYzE2NzVmOWMyZgocCgphd3NfcmVnaW9uEg4aDG1lLWNlbnRyYWwtMQodCg1XT1JLTE9BRF9OQU1FEgwaCmFwaWdhdGV3YXk='
        thread=22
2023-12-07T11:50:35.817050Z     debug   envoy pool external/envoy/source/common/conn_pool/conn_pool_base.cc:265 [Tags: "ConnectionId":"14"] using existing fully connected connection   thread=22
2023-12-07T11:50:35.817056Z     debug   envoy pool external/envoy/source/common/conn_pool/conn_pool_base.cc:182 [Tags: "ConnectionId":"14"] creating stream     thread=22
2023-12-07T11:50:35.817068Z     debug   envoy router external/envoy/source/common/router/upstream_request.cc:563        [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] pool ready        thread=22
2023-12-07T11:50:35.817095Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:141      [Tags: "ConnectionId":"14"] encode complete     thread=22
2023-12-07T11:50:35.821163Z     debug   envoy router external/envoy/source/common/router/router.cc:1479 [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] upstream headers complete: end_stream=false       thread=22
2023-12-07T11:50:35.821227Z     debug   envoy http external/envoy/source/common/http/conn_manager_impl.cc:1863  [Tags: "ConnectionId":"49","StreamId":"18335380440767085209"] encoding headers via codec (end_stream=false):
':status', '200'
'content-type', 'application/json'
'date', 'Thu, 07 Dec 2023 11:50:35 GMT'
'x-envoy-upstream-service-time', '4'
'server', 'envoy'
        thread=22
2023-12-07T11:50:35.821389Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:170      [Tags: "ConnectionId":"48"] **Error dispatching received data: http/1.1 protocol error: INVALID_HEADER_FORMAT**     thread=23
2023-12-07T11:50:35.821428Z     debug   envoy connection external/envoy/source/common/network/connection_impl.cc:146    [Tags: "ConnectionId":"48"] closing data_to_write=0 type=1      thread=23
2023-12-07T11:50:35.821434Z     debug   envoy connection external/envoy/source/common/network/connection_impl.cc:278    [Tags: "ConnectionId":"48"] closing socket: 1   thread=23
2023-12-07T11:50:35.821476Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:107      [Tags: "ConnectionId":"48"] disconnect. resetting 1 pending requests    thread=23
2023-12-07T11:50:35.821488Z     debug   envoy client external/envoy/source/common/http/codec_client.cc:158      [Tags: "ConnectionId":"48"] request reset       thread=23
2023-12-07T11:50:35.821500Z     debug   envoy router external/envoy/source/common/router/router.cc:1323 [Tags: "ConnectionId":"17","StreamId":"11382593540940922209"] upstream reset: reset reason: protocol error, transport failure reason:      thread=23
2023-12-07T11:50:35.821533Z     debug   envoy http ext

is this related https://github.com/envoyproxy/envoy/issues/31009

@hzxuzhonghu : I am facing similar kind of problem with istio 1.20, but I am to sure if both are same or not.

We are experiencing the same issue with version 1.20.0 and 1.20.1 with our only Nginx application. We have no issue with the others (varnish, apache, ...). For now, we will only upgrade to 1.19.4.

does your header value contains CR LR

We found the guilty header, indeed there were some new lines in it (LF)... so I think any headers with any new line type may be impacted by this new parser. It's now working fine. Thanks for the help!

NP, @kyessenov @zirain could we cherry pick the envoy patch https://github.com/envoyproxy/envoy/issues/31009

Hi @kyessenov , @zirain :  any update here?

https://github.com/envoyproxy/envoy/pull/31168#issuecomment-1874204705
wait for upstream backport


Thread leak

An instrumented boot classpath revealed a mistake in this plugin that can cause thread leaks. See https://github.com/jenkinsci/datadog-plugin/pull/9 for the fix.

Hi @jglick Thanks for opening this issue. I am currently working on some big refactoring and I included it as part of it. See https://github.com/DataDog/jenkins-datadog-plugin/pull/169. I keep this issue open until I make a new release.

Note that for plugins hosted on the Jenkins update center, we urge maintainers to do development in, and cut releases out of, the repository in @jenkinsci and in fact to delete any original clone. Recent discussion

Thanks for the feedback, we are currently in the process of getting rid of this fork.


Add functionality for bulk extension handling

Please add and option to run actions on all selected extensions like uninstall, enable, disable.
For example: There is a lot of default installed extension that i don't need and it's very annoying to disable one by one by hand on every PC.
(Maybe add a config option to the user settings file to easily transfer disabled extension list to another PC?)

There is a command line option to install or uninstall a single extension. Perhaps this could be extended to install multiple extensions.

code --install-extension

There are some workarounds for this https://stackoverflow.com/questions/35773299/how-can-you-export-vs-code-extension-list

/duplicate of #27147
Please add your upvotes to #27147


How do you find the swat.CAS connection host?

How do you find the host for CAS? We have tried what we think it is using port 5570 for SWAT but it doesn't work.
conn = swat.CAS(host, port, username, password)

We are following https://sassoftware.github.io/python-swat/getting-started.html and at the step:
In [1]: import swat
In [2]: conn = swat.CAS(host, port, username, password)
And we need to know how to get the host details for this - conn = swat.CAS(host, port, username, password).

First thing you'll need to do is read the CAS documentation on how to open up the API endpoint in the cluster. Once you've done that you'll then have the information needed. This may be the best place to start.

If you look here you'll also see the V4_CFG_CAS_ENABLE_LOADBALANCER entry. This item does create an external endpoint which would be your host and port if that's no documented on the SAS side of things.


npm release

could you release to 8.4.0?

Done, but if you need the latest release you can point npm at the github repo

yeah was doing that but ran into yarn issues where my lock file had a different checksum built locally than my build server >_<


Cannot strip data-test-* attribute when binding the attribute to differently named property

For instance, we add below snippet in a component
attributeBindings: ['testAttr:data-test-selector'],
testAttr: computed('dataAttrPrefix', {
  get() {
    const prefix = get(this, 'prefix');
    return `${prefix}_my_selector`;
  }
}).readOnly()

In prod env, the 'data-test-selector' still exists.

try this instead:
'data-test-selector': computed('dataAttrPrefix', {
  get() {
    const prefix = get(this, 'prefix');
    return `${prefix}_my_selector`;
  }
}).readOnly()

@Turbo87  Thanks for the prompt reply.
I was wondering if the strip feature would also support the differently named property.

no, we only strip properties that start with data-test-

@Turbo87 Fair enough.


updated code is not there in npm

I just saw in lib/index.js ```
import { NativeModules } from 'react-native'
// import ShareExtension from 'react-native-share-extension'
// const { type, value } = await NativeModules.ShareExtension.data()
// NativeModules.ShareExtension.close()
export default {
data: () => NativeModules.ReactNativeShareExtension.data(),
close: () => NativeModules.ReactNativeShareExtension.close()
}

but in the git repo the latest code is
`import { NativeModules } from 'react-native'

// import ShareExtension from 'react-native-share-extension'
// const { type, value } = await NativeModules.ShareExtension.data()
// NativeModules.ShareExtension.close()
export default {
  data: () => NativeModules.ReactNativeShareExtension.data(),
  close: () => NativeModules.ReactNativeShareExtension.close(),
  openURL: (url) => NativeModules.ReactNativeShareExtension.openURL(url),
}`

Thats the reason openURL is not working. Can admin push the latest code into repo?

Since the latest code is not there in the npm repository i manually downloaded from github and used that ReactNativeShareExtension xcode as a library and imported the ShareExtension from the local copy. After a week time spent Now everything is working fine without any issues in the simulator.
However when i run it in the real device app hangs. I am trying to share photo from photo gallery app to my app as soon as i click on mysharex app nothing is happening.

I have the exact same problem

@dfabarbosa I fixed it by adding the scripts in the extension build phase. Now i don't have any more issues. Great Repo! Very big thanks to the developer.

@theone3nu I'm not being able to make it work. Did you choose shared or separated bundle? I chose shared and the appShareExtension target's "Bundle React Native code and images" phase doesn't appear, did you have any problem like this?

Check the screenshot

Well it's working and I did nothing... The problem was that the extension takes a lot of time to appear on the device on debug mode. Thanks for your help @theone3nu !!!

NP @dfabarbosa

hey, what about "react-native-share-extension": "github:alinz/react-native-share-extension" in dependencies in package.json?

@AndrewHenderson I propose releasing v1.3.0 immediately with everything that is currently on master since the last release on Aug 2, 2017, so that we can deploy these changes to npm. We can bump future changes to v1.4.0 or otherwise.
Please let me know ASAP if you agree.

@isaachinman I experienced issues using master, last week. I was unable to successfully complete network requests from the Share Extension — particularly uploading images. Switching back to NPM version resolved the issue immediately. It seems there is a bug that was introduced since the 1.2.1 release.

@AndrewHenderson Ouch... there are 19 commits in that release. Anyone feel like doing a git blame?

@isaachinman It was only on iOS, so that should help narrow it down.

@isaachinman This looks like it could be the cause: https://github.com/alinz/react-native-share-extension/commit/1e98f58991a892fd941a809f9564fb5181693ba0#diff-cd365a662ae840f4beb6a01a1c8ffa1f

@AndrewHenderson Does reverting just that file fix the bug?

Any update on this? Would really like to be able to use the openURL method.

@isaachinman Please review. Reverting changes in https://github.com/alinz/react-native-share-extension/commit/1e98f58991a892fd941a809f9564fb5181693ba0 seems to have fixed issues: https://github.com/alinz/react-native-share-extension/pull/132/files.
Perhaps we can get things openURL in NPM after this.

@AndrewHenderson Looks good, glad to hear that the bug was indeed (hopefully) isolated to 1e98f58. Let's focus on putting together a stable release, and then getting out the "stable" features (like openURL) which have been sitting in PRs for a long time.

@isaachinman Agreed.
I just merged https://github.com/alinz/react-native-share-extension/pull/132. We should now have a stable version of the app.
I'll start outlining a roadmap for the next version. You and I have collaborator permissions on the repo, but do not have NPM permissions to release new versions. We'll need to either have @alinz grant us access or review our release candidate once we've finalized our changes.

@AndrewHenderson I believe I do already have npm permissions - I spoke to @alinz via email. We should get you on there as well, for sure.

Any update on this? :-)

@jvandenaardweg As far as I know, we don't have an rc yet. v1.2.1 is on npm.

Thanks for the update. I've then decided to use the last commit in master npm install https://github.com/alinz/react-native-share-extension.git\#3db5320135c154c367d72c44688a29ce41b210e7 --save
Seems to be working fine in my app 👍

I am happy to just release the latest master as v2.0.0 (I assume there are breaking changes). What do you think @AndrewHenderson?

@jvandenaardweg  Does the openUrl method work in your app on Android?
also thanks for the advice on installing from commit vs master

@chiaberry haven't had the time to build and test the Android side, currently only working on an iOS app. Sorry!

I Make react-native-file-share-intent it's Work perfectly on both platforms. It supports all media to share our App


docs: Fix broken links in Quick Start guide

@uid1000 I think you are exploring docs from github .md files, them are compiled using docsify so the links are good, check: https://zwave-js.github.io/zwave-js-ui/#/getting-started/quick-start


Add statusor words to spellcheck dictionary

Description: The pedantic spellcheck when run manually doesn't catch words in third party files (ie the statusor); however on trying to update our Envoy fork from master I got spellcheck errors on pushing. This PR adds the words that fixed this to the dictionary.
Risk Level: Low
Testing: None
Docs Changes: None
Release Notes: None

I working on the proper solution to this problem.


Type mismatch

https://github.com/QSI-BAQS/Jabalizer.jl/blob/e62385765c57cee81d850f163226ee33267a89fb/src/icm.jl#L218-L222
https://github.com/QSI-BAQS/Jabalizer.jl/blob/e62385765c57cee81d850f163226ee33267a89fb/src/icm.jl#L1
https://github.com/QSI-BAQS/Jabalizer.jl/blob/e62385765c57cee81d850f163226ee33267a89fb/src/cirq_io.jl#L20-L27
Describe the bug
Importing a json file with Jabalizer.load_circuit_from_cirq_json seems to result in a circuit of type
Vector{Tuple{String,Vector{String}}}
But using Jabalizer.compile requires type
Vector{Tuple{String,Vector{Int}}}()
This can be fixed manually but it would be nice to not have to do that.

OS: Windows
Python version 3.7.4
Julia 1.9.0

This problem continues a bit further:
If one compiles a circuit with Jabalizer.compiler, and then converts the resulting circuit to json using save_circuit_to_cirq_json, then at least cirq.read_json doesn't like the Int-type qubit names. Again, this can probably be fixed manually but it would be nice to not have to do that.
This could be solved by just a small fix at:
https://github.com/QSI-BAQS/Jabalizer.jl/blob/e62385765c57cee81d850f163226ee33267a89fb/src/cirq_io.jl#L90


Remove that damn injection message

Useless messages and taking a lot of the console view when a lot of players joins

a better option would be to add it to the debug option.

it would be better to add it to the debug option.


important update -- must merge

👀

LGTM

Yup, LGTM.

LGTM, ship it 🚀

Any updates here?
we've run into the same situation and this LGTM!

Any updates here? we've run into the same situation and this LGTM!

still waiting for maintainer to review. will keep you posted on this

any update?

Sorry no tests, no merge

Tests work on my local, LGTM


Fix code scanning alert - Replacement of a substring with itself

Tracking issue for:

[x] https://github.com/Infinizhen/react-webpack-babel-boilerplate/security/code-scanning/1

Fixed the issue by removing the line in question.


Second step, reduce the complexity of the code.
Thirds step, merge.


Console parameter and multi parameter log v3

Short description of the problem:
I have two questions or bugs to communicate, perhaps the first one we already discussed it some months ago, I think it should be resolved but to my side it was never resolved and is still there, so I'm not sure if it is or it is not a bug or if it is by design.

Should we are able to call ionic cordova run -c and ionic cordova emulate -c without passing the -l for livereload? Passing the console parameter without livereload parameter seems to have no impact.
If we can not call console without livereload it is much more difficult debugging app on device in production mode, so without IonicDevServer launched and others. Is this by design, is this a bug?
In ionic console docs, there is nothing written about if the -l is mandatory for -c

the Other problem which is a little bit annoying, if we have a console log with two parameter like that console.log('First part', 'Second part'); the output in the console for emulator is like that
[14:18:34]  error opening ws message: {"category":"console","type":"log","data":["First part","Second part"]}
So in this case the output is not readable and that's annoying, is this by design, is this a bug or can we do something to prevent this?

Post the output of ionic info below please
ionic info

global packages:
    @ionic/cli-utils : 1.0.0
    Cordova CLI      : 7.0.0
    Ionic CLI        : 3.0.0

local packages:
    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.0.0
    @ionic/cli-plugin-ionic-angular : 1.0.0
    Ionic Framework                 : ionic-angular 3.0.1

System:
    Node       : v6.10.2
    OS         : Linux 4.10
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed

For part 1: -l should be required for -c to work. This was not communicated well and is an easy fix.
For part 2: You're probably using Android, because you're on Linux. I'm assuming console.log being quirky with multiple arguments is due to this: https://cordova.apache.org/docs/en/latest/reference/cordova-plugin-console/#android-quirks

Okay thx it would be better if you document the parameter and their combination better.
I can't remember but I wasn't sure if the log was never working on device.
BTW perhpase you can help us.
What is the best way to debug on real devices? Often we need to debug and to log.
We want use a mail or db logging so for now we simple use toast messages.
But for sure there is a better method, which is the best in your opinion?

@mburger81 I did some digging and I think I'm wrong on both accounts. Sorry. I myself am still unfamiliar with the magic behind the scenes.
@jthoms1 Can we clear things up here?

@dwieeb
The bug is not show in Milestone CLI 3.1.0? When do you think you will release this?
If I can I will call your attention to another bug for which I'm waiting to have an response: #2263 I think this is very urgent too.
thx

This is not resolved in version 3.1 and also not in version 3.2

Hi @mburger81 sorry for the huge delay. I finally got around to fixing this. It'll be fixed with the next version of app-scripts.

Hi @dwieeb ok good news to hear :)
On your old post you wrote "I think I'm wrong on both accounts", so this commit is resolving the parameters problem, whats about the second one with the console log on android? I think in meantime for my one this is really a problem of android and you can't resolve it? :) Or can you?
thx

@mburger81 Correct, both were our fault. 😂


Ideas for 2.0.0 version

[ ] Disable IE8 support.
[ ] Add ES6 with webpack/browserify/systemjs.
[ ] Add pre-processors.
[ ] Add templaters.
[ ] Another workflow for SVG. Use sprite of symbols instead usual svg-sprite.

English only in this discussion.

Add post-processors.
Add Angular/Ember/Backbone support.

@alexHlebnikov what does Angular/Ember/Backbone support mean? Boilerplate for that frameworks?

@alexHlebnikov post-processors have to be implemented before 2.0 version.

@artem-malko @alexHlebnikov I think this issue for bower. TARS is a builder, not a framework.

@alexHlebnikov @TrySound of course not for bower. These frameworks need special file structure for theirs special entities. So, we could download source code for that libs from bower, but TARS need to have ready FS for them.
@alexHlebnikov I've understood you correctly?

@artem-malko yes, I'm talking about file structure.

@artem-malko Okay. For this will be helpful file structure with .gitignore files. So no need to have create-fs task. The other way is using yo-gen.

@artem-malko But the lib must be loaded by bower.

@TrySound :+1:
I'm not sure about yo-gen in that place, i think, that there could be some problems with it.

@artem-malko Tasks not for this.

@TrySound why not? It can create fs too.
If there will not be any problems with yo, so it'll be yo.

Add support sass @imports

Is it possible add a partition sprites into groups?
Example
Static
static/
    └── img/
        └── sprite/
            └── 96dpi/
                └── ui/
                    └── ui_1.png
                    ...
                    └── ui_∞.png
                └── social/
                    └── social_1.png
                    ...
                    └── social_∞.png

Ready build
dev/
    └── static/
        └── img/
            └── png-sprite/
                └── sprite_ui.png
                └── sprite_social.png

@vova-white it is quite specific issue, so you have to implement it by yourself by using user-tasks


Fix support for recursive constraints in iftype conditions.

By defining the shadowing TK_TYPEPARAM on the entire iftype clause, which
contains both the constraint and the body, the appropriate definition
of the type variable is used when it appears in the constraint.
Fixes #1960

Iftype is implemented by creating a new definition of the typeparameter with a constraint which combines both the original constraint and the RHS of the iftype. This TK_TYPEPARAM shadows the original definition inside the iftype body.
The third commit moves the shadowing constraint from the body to the entire iftype, so it gets picked up by the constraint as well. This allows recursive constraints such as the examples in #1960.
However we don't want it to get used by the else clause of the iftype. The second commit creates a new AST node, TK_IFTYPE_CLAUSE, containing the constraint and the body. This isolates the various branches of the iftypes in individual scopes.
Finally the reification used subtyping of constraints to compare if a typeparam was shadowing the other one. I ran into issues with this since the two constraints are defined in separate scopes now.
Instead, the first commit changes it to have the ast_data always point to the original typeparam.
This way, even if a typeparam is an iftype shadowing of another, their data pointers will be equal.
I believe this matches @sylvanc's original intention in cb5c611bcce7533c5862efcfefb04030c55596a2.
cc @jemc for #1960. This should allow my examples with recursive constraints in that issue
cc @Praetonus who implemented iftypes

This is marked "DO NOT MERGE" until the aforementioned name change is done, which @plietar will get to after he wraps up some other responsibilities.

This should be good now @jemc

Thanks!


[englishbreakfast] Disable riscv32 bitmanip

To save gates, the Ibex on English Breakfast does not have bitmanip enabled. In https://github.com/lowRISC/crt/pull/24 we introduce a toolchain feature to control the bitmanip feature which will be enabled by default.

I had to re-run “CW310 Test ROM Tests” since the first time around spi_host_smoketest_fpga_cw310_test_rom failed. It has now passed, so this can be safely merged.


how to insert one document to a index with automatic _ID

You can just leave the ID argument out when calling the Index API:
es.Index("myindex", mybody)

Or, when using the request struct, like this: https://github.com/elastic/go-elasticsearch/blob/36b236c0f9d7508ee34826303a67fba36f38810c/_examples/main.go#L67-L72
leave out the DocumentID field.

You can just leave the ID argument out when calling the Index API:
es.Index("myindex", mybody)

Or, when using the request struct, like this:
go-elasticsearch/_examples/main.go
Lines 67 to 72 in 36b236c
req := esapi.IndexRequest{
Index:      "test",
DocumentID: strconv.Itoa(i + 1),
Body:       strings.NewReader({"title" : " + title + "}),
Refresh:    "true",
}
leave out the DocumentID field.

thank you. this helps me a lot


Issue in ChatVertexAI Generation: Cannot read properties of undefined (reading 'text')

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
A very basic chain:
  const runnable = RunnableSequence.from<ChainInputs, DecomposeChainOutput>([
    {
      input: (i: ChainInputs) => i.input,
      chat_history: (i: ChainInputs) =>
        i.chat_history?.length
          ? formatChatHistoryForPrompt(i.chat_history)
          : [],
      customizationPrompt: () => {
        return fullConfigs.customizationPrompt;
      },
    },
    promptTemplate,
    model,
    new StringOutputParser(),
    }),
    ```

    Only potential relevant callout is using a custom safetyHandler:
    ```
        return new ChatVertexAI({
      modelName: modelParams.modelName,
      safetyHandler: {
        handle: (response) => {
          // eslint-disable-next-line @typescript-eslint/ban-ts-comment
          // @ts-ignore
          if (response.data?.candidates[0].finishReason === "SAFETY") {
            throw new InvalidRequestError(
              "Safety error - Gemini blocked response",
              response.data,
            );
          }
          return response;
        },
      },
      ...devAuthOptions,
      ...modelParams,
    });
    ```

### Error Message and Stack Trace (if applicable)

TypeError: Cannot read properties of undefined (reading 'text')
at ChatVertexAI.generate (file:///Users/user/code/projects/internal1/node_modules/.pnpm/@langchain+google-common@0.1.1@langchain+core@0.3.0_zod@3.23.5/node_modules/@langchain/google-common/dist/chat_models.js:275:64)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Promise.allSettled (index 0)
at async ChatVertexAI._generateUncached (file:///Users/user/code/projects/internal1/node_modules/.pnpm/@langchain+core@0.3.0_openai@4.40.0/node_modules/@langchain/core/dist/language_models/chat_models.js:182:29)
at async ChatVertexAI.invoke (file:///Users/user/code/projects/internal1/node_modules/.pnpm/@langchain+core@0.3.0_openai@4.40.0/node_modules/@langchain/core/dist/language_models/chat_models.js:56:24)
at async RunnableSequence.invoke (file:///Users/user/code/projects/internal1/node_modules/.pnpm/@langchain+core@0.3.0_openai@4.40.0/node_modules/@langchain/core/dist/runnables/base.js:1144:33)
at async RunnableSequence.invoke (file:///Users/user/code/projects/internal1/node_modules/.pnpm/@langchain+core@0.3.0_openai@4.40.0/node_modules/@langchain/core/dist/runnables/base.js:1150:27)
at async RunnableSequence.invoke (file:///Users/user/code/projects/internal1/node_modules/.pnpm/@langchain+core@0.3.0_openai@4.40.0/node_modules/@langchain/core/dist/runnables/base.js:1150:27)
at async forward (file:///Users/user/code/projects/internal1/node_modules/.pnpm/langsmith@0.1.41@langchain+core@0.3.0_langchain@0.3.5_openai@4.40.0/node_modules/langsmith/dist/evaluation/_runner.js:670:9)
at async RetryOperation._fn (/Users/user/code/projects/internal1/node_modules/.pnpm/p-retry@4.6.2/node_modules/p-retry/index.js:50:12)

### Description

Encountering an issue with ChatVertexAI where the above error is thrown.

This is after bumping to google-common 0.1.1.

Appears to be coming from this line: https://github.com/langchain-ai/langchainjs/blob/main/libs/langchain-google-common/src/chat_models.ts#L350

Unclear what the conditions are that cause this, it happens intermittently.

Context from Allen: If you want to hack it, I'd change it to ret?.generations?.[0]?.text ?? "" but I'll have a slightly better fix in (hopefully) a few days

cc @afirstenberg

### System Info

    "@langchain/community": ">=0.3.0 <0.4.0",
    "@langchain/core": "^0.3.16",
    "@langchain/google-vertexai": "0.1.0",

    Node v21.7.3

@jacoblee93 - Please assign this to me, but I hope to have the fix in place as part of #6999

Thank you @afirstenberg!


Swan:Link is breaking when try to sign in.

User was trying to sign up and grab the $10 for signing up to Swan thru Hexa wallet. He had one-password and 2FA set up through his account. The link was broken when he tried to sign into his account thru Hexa.

https://user-images.githubusercontent.com/62699947/146888752-4bf3b334-e8ae-48eb-86e5-3f6564ab3a63.MP4

Unable to reproduce this issue.


Memory Leak Problem

When I run ResNet Demo I findthe program use too many memory(up to nearly 9GiB)

windows10 20H2(19042.685)
.Net Core 3.1
TensorFlow.NET 0.31.1
TensorFlow.Keras 0.2.1
SciSharp.TensorFlow.Redist 2.3.1

@ijrys Are you saying this example ResNet?

@ijrys Are you saying this example ResNet?

I copy the code from readme.md(homepage of the project), it looks a little different from ToyResNet.cs, but major parts are same

Please try latest version v0.4.0.


m365 spo homesite list

Usage
m365 spo homesite list
Description
Returns details of all homesite.
Refer to #6488 for additional cmdlet to add an additional home site.
I can work on it once peer reviewed.
Options

Option
Description

Examples
Returns all configured home sites
m365 spo homesite list

Default properties

Title
Url

Additional Info
No response

Looks good to me!


Convert to custom elements v1

Implementation is heavily based on polymer's polyfill; I mostly just made it compatible with domino and removed unneeded events (mutation observations, attachedCallback reaction, etc.).
I also added in support for components that are intended to run server-side only. It's a feature I plan to make heavy use of, but I can separate it out if you want.

Oops, actually there is much more to think about.


Update README roadmap section

It's a better visual experience to the readme with that space betweeen brackets, creating a fillable checkbox.


Tags fixtures with doctrine.fixture.orm.

^3.0 releases of DoctrineFixturesBundle treats services as fixtures when they're tagged with doctrine.orm.fixture.
Not sure if this is the most optimal way to do it.
Before:
php bin/console doctrine:fixtures:load -n

In LoadDataFixturesDoctrineCommand.php line 95:

  Could not find any fixture services to load.

After:
php bin/console doctrine:fixtures:load -n
  > purging database
  > loading App\DataFixtures\UserFixtures
  > loading App\DataFixtures\TagFixtures
  > loading App\DataFixtures\PostFixtures

Closing since this is fixed in scope of - https://github.com/symfony/demo/pull/725


Add signature based authentication and jwt authorization

closing this to re-open on a separate branch. having issues with gh pr checkout ..., probably because this is old and went through a rename


stats: emit cluster upstream rq status code counters

Description: this enables emitting stats for calculating SR.
Risk Level: low
Testing: local emission
Signed-off-by: Jose Nino<EMAIL_ADDRESS>

Created #769 to track verification of the regexes in CI


Separated Compile for android architectures

For example, I want to compile only arm64 and I don't want to compile armv7, what do I do to get this because when I compile android for some reason it compiles armv7 too

The documentation appears to be severely out of date, but <architecture exclude="armv7" /> should still work.

But if I don't want to compile it, what do I do?

By default it compiles armv7 and arm64. The code I posted should exclude armv7. Not sure what you're asking.

A i got it now

Thanks foe the info