feat(icons): added bangladeshi-taka icon

What is the purpose of this pull request?

[x] New Icon
[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other:

Description
Adding a new icon: "Bangladeshi Taka"

BDT
৳
ISO 4217
Unicode: U+09F3

Icon use case
A real-life currency — also used as Money, Shopping, Discount
Alternative icon designs
No alternative icon designs. It's the universal "Taka" icon
Icon Design Checklist
Concept

[x] I have provided valid use cases for each icon.
[x] I have not added any a brand or logo icon.
[x] I have not used any hate symbols.
[x] I have not included any religious or political imagery.

Author, credits & license

[ ] The icons are solely my own creation.
[ ] The icons were originally created in # by @
[x] I've based them on the following Lucide icons: indian-rupee, badge-indian-rupee, receipt-indian-rupee
[ ] I've based them on the following design:

Naming

[x] I've read and followed the naming conventions
[x] I've named icons by what they are rather than their use case.
[x] I've provided meta JSON files in icons/[iconName].json.

Design

[x] I've read and followed the icon design guidelines
[x] I've made sure that the icons look sharp on low DPI displays.
[x] I've made sure that the icons look consistent with the icon set in size, optical volume and density.
[x] I've made sure that the icons are visually centered.
[x] I've correctly optimized all icons to three points of precision.

Before Submitting

[x] I've read the Contribution Guidelines.
[x] I've checked if there was an existing PR that solves the same issue.

Hi @mayeenulislam,
I'm afraid these have several guideline violations, please make sure to more closely follow our icon design guidelines.
The main issues that need to be addressed:

Not all elements have 2px gaps between them (especially for the receipt and badge versions), see guideline no. 8
(Not sure, if this makes the small versions feasible or not)
The icons do not stick to the grid, leading to blurry lines, see our DPI preview and guideline no. 13
There are some really uneven curves, can we maybe try a more geometric approach? (guideline no. 12)

More Lucide-ey proposas, based on Google image search (but I'm totally unsure if they're recognisable or good enough):
Open lucide studio
Open lucide studio
Open lucide studio

We should maybe think about the currency icons, we basically have the same issues here as we do with the brand icons where we try to shoehorn existing possibly copyrighted work into our design guidelines.
For example €:
The European Community, represented by the European Commission, owns the copyright for the euro symbol.

@karsa-mistmere I've revised the design, as far as I understood your design guidelines and the previous icons that you already have merged. I did not find any dedicated pull request on "Indian Rupee", hence could not measure the deviations.
With these changes, the stroke widths improved.
BTW, about the DPI (24px) I checked the Rupee symbols in Figma and the symbols that I designed. In the 1px grid, they completely matched in many ways.
Given my current understanding, I believe these modifications will align the design with the guidelines.

@karsa-mistmere I've revised the design, as far as I understood your design guidelines and the previous icons that you already have merged. I did not find any dedicated pull request on "Indian Rupee" (except #1401), and I could not measure the deviations. With these changes, the stroke widths improved.
BTW, about the DPI (24px) I checked the Rupee symbols in Figma and the symbols that I designed. In the 1px grid, they completely matched in many ways.
Given my current understanding, I believe these modifications will align the design with the guidelines.

I'm afraid every concern raised in my original review still stands: the vertical lines are off grid, gaps are too small, curvatures are uneven (especially for the base icon).

@karsa-mistmere I've updated the Icons once again. Pardon me, would love to have another final review.
If not up to the mark, I might discard the pull request by myself.


Update jsoniter-scala-core, ... to 2.13.25

Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.13.10 to 2.13.25.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.plokhotnyuk.jsoniter-scala" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.github.plokhotnyuk.jsoniter-scala" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #435.


added tooltips to icons

Closes #20
Type of Change
Put x inside the square bracket to specify what type of change your PR is:

[x] New Feature
[ ] Bug Fix
[ ] Code Refactor
[ ] Documentation Update
[ ] Other (please specify):

Description of Change
Tooltips have been added to home and create new ticket icon.
Demo
Screencast from 2024-12-28 03-40-43.webm

Hi @disvid ,
I'm sorry, but we will have to close this PR as the issue was not assigned to you. as previously mentioned, contributors are required to discuss their approach and announce their intention to work on an issue before submitting a pull request.
Please ensure to follow this process and then you may reopen the PR.

@AyushDharDubey please review.

nice @disvid,
this is good enough to close #20
but i wonder, was the package update and the react-tooltip package necessary?? it seem to work on my system without the specific change.
in case the change is not necessary, please revert it, a new issue might be created in future to update all the packages.

@AyushDharDubey sir i have reverted the change in package.json file , do i also need to do it in package-lock.json?
If yes, could you please guide.

to restore package-lock.json file
go to the current master branch and download the package-lock.json file and replace the file in your branch with the one from master branch, this should restore the change
otherwise, you may copy the content from master branch and paste it in your branch, this should also work

@AyushDharDubey Done sir

@AyushDharDubey can you please allow me to solve more easy issues ?

hi @disvid,
please note that no more than 3 easy issues per repository will be counted toward the score. solving additional easy issues beyond this limit won't contribute to your score, so it would be better to let others have the opportunity to work on them.
however, if any of these issues remain unresolved by the end of the event, you may be allowed to fix them. yet, the leaderboard will still only account the scores for up to 3 easy issues per repository.

in the meantime, we welcome you to submit your proposals for other open issues.

@AyushDharDubey okay sir


Help with openidconnect-rs

I'm having trouble using openidconnect-rs in an extism plugin. I can't even import the library. I'm getting this error:
Uncaught (in promise) Error: from module "main": cannot resolve import "__wbindgen_placeholder__" "__wbindgen_describe": not provided by host imports nor linked manifest items

Here's a minimal repro:
use extism_pdk::{plugin_fn,FnResult};
use openidconnect;

#[plugin_fn]
pub extern "C" fn test() -> FnResult<()> {
    Ok(())
}

And a full working repro repo: https://github.com/anderspitman/wasmrepro
To run that:
cargo build --target wasm32-unknown-unknown
deno run --allow-all main.js

Any ideas?

it's likely that this library is being "smart" and assuming the target "wasm32-unknown-unknown" is going to run in JS environment. As such, they use wasm-bindgen to access fetch and other functions.
Can you try compiling to the "wasm32-wasi" target instead? And if that doesn't do it, then there may be some features you need to disable to get it compiling correctly.

also, Deno 2 removed wasi support, so if you can, run a Deno 1 version or use Node instead.

node is giving me Error: WASI is not enabled; see the "wasiEnabled" plugin option

Here's my updated SDK code:
//import createPlugin from "jsr<EMAIL_ADDRESS>import createPlugin from '@extism/extism';

const plugin = await createPlugin(
  "./target/wasm32-wasip1/debug/wasmrepro.wasm",
  {
    useWasi: true,
  },
);

const out = await plugin.call("test");
console.log(out);

plugin.close();

@anderspitman Ah, it looks like there was a typo in the js-sdk error message – thanks for catching that! Fixed in https://github.com/extism/js-sdk/commit/269384709e442fbdcd425e9a093c558aa62dbebe
I tried the example sdk code and it worked locally – are you still seeing errors?

Argh I had renamed the file from main.js to main.mjs and was still editing main.js in vim. Definitely the first time I've ever done that... Sorry for wasting your time on that

Ok current problem is that node doesn't support web workers... Trying to get the web-worker module to work but no luck so far

Downgraded to Deno 1.46.3. Now getting:
error: Uncaught (in worker "") (in promise) Error: Unhandled error. ([Object: null prototype] {
  message: 'Uncaught (in promise) Error: WASI is not supported on this platform',
  fileName<EMAIL_ADDRESS>  lineNumber: 188,
  columnNumber: 17
})

I feel like we're so close.

can you try again with the runInWorker property set to true? This is alongside the useWasi setting.
https://extism.github.io/js-sdk/interfaces/ExtismPluginOptions.html#runInWorker

You'll also need to set allowedHosts if there is an outbound HTTP call:
https://extism.github.io/js-sdk/interfaces/ExtismPluginOptions.html#allowedHosts

Yeah I'm using both of those in my actual project. I think the problem with Deno 1.x is that the latest versions of extism disable the wasip1 capability, because Deno 2 doesn't support it.
I'm not sure how to make workers work with Node. It looks like it supports node:worker_threads, but I've never used that before.

I'm not sure how to make workers work with Node. It looks like it supports node:worker_threads, but I've never used that before.

Hm, I don't think you should need to do anything with workers yourself. The JS SDK should handle that for you when you add runInWorker: true. Do you have a more updated snippet you can share from your project and the resulting error you see when you try to call the plugin?

Thanks for all the help. I originally moved the code into a separate web worker because that's the only way I could get it to work with Deno 2, which is my primary runtime. Sounds like maybe I need to focus on node for now. Let me move all the code back out of the web worker and see if the auto worker_threads implementation works in node.

We are working on patching Deno 2 with a WASI implementation, but it's a little tricky. Hopefully you can use Node in the meantime, but feel free to track the issue here: https://github.com/extism/js-sdk/issues/95

Argh I had renamed the file from main.js to main.mjs and was still editing main.js in vim.

Argh, I've definitely been there before – commiserations!

I originally moved the code into a separate web worker because that's the only way I could get it to work with Deno 2, which is my primary runtime.

I'm curious about this– what errors were you seeing that were fixed by running @extism/extism in a worker? (Was it Deno capability permission related, or something else?)

Ok, ditching the separate worker worked for node. I now have my plugin working with openidconnect-rs in JS and Golang hosts, with the library making outgoing HTTP requests perfectly. extism is so cool!
Thanks again for all the help.

I'm curious about this– what errors were you seeing that were fixed by running @extism/extism in a worker? (Was it Deno capability permission related, or something else?)

Honestly I don't remember. I can try to reproduce it if it's helpful.

very glad to hear it! please keep in touch

Oh one more question: is there any hope of getting wasm32-unknown-unknown to work? WASI feels heavy for what I'm doing, and it seems as if it might be less secure since it has a bigger API surface, but those fears might be unfounded.
It seems like I would need to go through the dependency tree and make sure everything plays nice with the other target?

Good question! I think it would be possible to remove the wasi dependency, but you'd have to update the openidconnect crate to conditionally make its HTTP requests using the Extism HTTP implementation (like you've used in your rust-pdk)
However, I'm not sure it's actually that much of a concern from a security standpoint (or a size either) since wasi is only host side code, it doesn't add any meaningful size to your wasm module. Just a few import functions for the wasi calls the module makes.
And, as you've found, you have to explicitly define which hosts, paths, and even enable header support for all external interactions the wasm code makes. So things are intentionally quite locked down even when enabling wasi.
If you'd like to explore converting the openidconnect dependency to use Extism's HTTP stack instead, we'd be happy to guide you -- I'm personally interested in seeing what that would take!

Makes sense. Although I think openidconnect-rs already doesn't rely on anything internal for making requests. You can just provide a function that takes a request and returns a response and it will work. See here: https://docs.rs/openidconnect/latest/openidconnect/index.html#importing-openidconnect-selecting-an-http-client-interface
Though it does build in support for reqwest and curl for convenience, and maybe just having them in the crate is what's breaking things.

oh that's a great design!
the it would be pretty straightforward to add a blocking / sync http call there. you'd convert types between the http request and response in that library to those from the extism rust-pdk, making the actual http call via the extism request.
the devils always in the details though ;)


MudDatagrid - Filters doesn't keep the columm select when event call back triggered

Bug type
Component
Component name
MudDataGrid
What happened?
The selected column in filters is reset when the operator changes or if a value is entered in the filter field (event callback).
see example at : https://try.mudblazor.com/snippet/QaQQuiFZzDcLEAgd
Expected behavior
Don't reset the selected column during the callback event.
Reproduction link
https://try.mudblazor.com/snippet/QaQQuiFZzDcLEAgd
Reproduction steps

Create MudataGrid with ServerData load options
use DataGridFilterMode.Simple
try to filter an element
...

Relevant log output
No response
Version (bug)
6.0.15
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi @tjscience,
Could you please take a look at the case? Is this something you've worked on before?
Thanks.

Hi @tjscience
see  herewwith the behaviour when i try to select a seond column to filter (name) then i choose the operator or the field value:

Fixed via pull #5203.

Fixed via pull #5203.

Many thanks @tjscience  for this rapid fix. It was tricky to handle. Looking forard to test it.

Hi @tjscience ,
I tested the fix and so far I don't see any problem :)
However, I noticed a strange behavior every time I add a new filter row: the width of the dialog increases a little bit for each new rw until it reaches 100%. I don't know if this is due to MudDialog or the filter component (see sc below).

Solved in 6.0.16 version


Feature: Settings for different drive train setups

Currently there is a differentiation between Single Motor and Dual Motor models in the configuration of the main power gauge:
    main_power_gage.maxValue = if (appPreferences.consumptionPlotSingleMotor) 170f else 300f
    main_power_gage.minValue = if (appPreferences.consumptionPlotSingleMotor) -100f else -150f

For Performance models, there should be a third option that takes into account the higher power: 350 kW.
New model year models will introduce other maximum power values:
https://www.polestar.com/nl-be/polestar-2/specifications/

There is now a menu for vehicle setup to select power and battery capacity.


the audio player does not stop when another application plays audio

the audio player does not stop when another application plays audio, for example a whatsapp audio

For android, what needs to be done is replace TelephonyManager with AudioManager. I have a custom fork with this implemented. Here is the relevant commit. It has several commits before it, so you won't be able to simply cherry pick it. It also isn't 100% tested yet, but it looks alright so far.


Use CMake's project() function

CMake automatically parses the VERSION arg of project() into PROJECT_VERSION_MAJOR, PROJECT_VERSION_MINOR, PROJECT_VERSION_PATCH
See https://cmake.org/cmake/help/latest/command/project.html

That's a good plan. Let's delete the previous versions.


Wrong Version und Last Download link

Steps to reproduce
See last Release an Match Version with Version you Download
Expected behavior
Download APK with Version 0.2.6
Actual behavior
Wrong Download Release
Mangayomi version
0.2.55
Device
Google Pixel 5
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated all installed extensions.

fixed!


fix in-place dict update

This PR fixes a bug introduced in #149:
rule.get("labels", {}).update(topology.as_dict_with_promql_labels()) won't update rule if "labels" is not in there - the new empty dict is not referenced by rule.
>>> d = {}; d.get("labels", {}).update(k="v"); print(d)
{}
>>> if "labels" not in d:
...     d["labels"] = {}
...
>>> d["labels"].update(k="v"); print(d)
{'labels': {'k': 'v'}}
>>>

I think this deserves a unit test

How could I forget :D
Added!


Keyboard API Support / Windows 10 onscreen keyboard doesn't auto appear when UITextField gains focus

The onscreen keyboard fails to appear when a UITextField gains focus with the TextFieldsViewController in the WOCCatalog app (or any app).
I'm running Windows 10 Pro on a Dell Venue 11 Pro (5130).
I've selected the Devices->Typing setting "Automatically show the touch keyboard in windowed apps when there's no keyboard attached to your device" (and this works for standard applications like Firefox). Maybe the universal WOCCatalog app doesn't count as a "windowed app"?
In either case, it would be nice if the onscreen windows keyboard responded to the UITextField gaining focus (via either touch or call to becomeFirstResponder). It would also be nice if it dismissed in response to e.g. a call to [self.textField resignFirstResponder] (possibly added to the textFieldShouldReturn: UITextFieldDelegate method to support dismissing the on screen keyboard upon press of the return key).
I can confirm that adding e.g.
[textField performSelector:@selector(becomeFirstResponder) withObject:nil afterDelay:10];
to the TextFieldsViewController in WOCCatalog does result in the field gaining focus - but the onscreen keyboard does not automatically appear.

Just as a sanity check I compiled and ran the C++ touch keyboard sample app from
https://code.msdn.microsoft.com/windowsapps/Touch-keyboard-sample-43532fda
The touch keyboard does appear - so a fix for UITextField should be doable.

More or less fixed by #483 (or at least the touch keyboard appears!)


Docs / Refactor Docs

I've split octopus into 3 folders:

octopus which is itself the component library
docs which consumes octopus and provides usage examples
static which deploy static files to zeit now

We will need to add storybook the octopus project for development purposes

@sam I think the octopus folder is too confusing, and this generally feels really convoluted.


Google Pay button unresponsive to click event [Re-open]

Describe the bug Google Pay button isn't reacting on click events performed with WebDriver
I'm reffering to known bug https://github.com/google-pay/google-pay-button/issues/270
To Reproduce Steps to reproduce the behavior:
We use Selenium,
driver().get("https://developers.google.com/pay/api/web/guides/resources/demos?hl=ru");
WebElement iframeWithButton= By.xpath("//iframe[@src='https://gpay-live-demo.web.app/basic.html']");
driver().driver().switchTo().frame(iframeWithButton);
WebElement button = driver().findElement(By.xpath("//button"));
button.click();

Also tried Сlick via JavaScript Executor,
Also tried Click via Actions ( Selenium )

Observations, code works from "scratch" with new browser session, it may spawn window once, but future clicks don't work.
Expected behavior Click event should spawn window for card selection.
Versions:
Windows 11
Chrome is up to date Version 128.0.6613.138 (Official Build) (64-bit)
selenium-java: 4.21.0
Video with Console output
https://github.com/user-attachments/assets/2edeaa47-e210-4dab-9435-817a32518e41
basic.html:244 AbortError: Cannot show PaymentRequest UI in a preview page or a background tab.
(anonymous) @ basic.html:244
Promise.catch
onGooglePaymentButtonClicked @ basic.html:242
demos:1 Cannot show PaymentRequest UI in a preview page or a background tab.
demos:1 Unable to download payment manifest "https://google.com/pay".
demos:1 Unable to download payment manifest "https://google.com/pay".
demos:1 Unable to download payment manifest "https://google.com/pay".

Allright, figured out, click spawns new window only when focus is on browser window.


Can't access storage files publicly

I have recently updated my NHost CLI and migrated to Nhost Config after I deployed to the cloud, I no longer can access files using the public url.
Here is the file

I have set the public select role to only allow access for images:
{"mime_type":{"_in":["image/png","image/jpg","image/jpeg"]}}
Here is the public URL:
https://${NHOST_SUBDOMAIN}.storage.eu-central-1.nhost.run/v1/files/${fileId}
I have even tried to set the select permission without any checks but keep getting
{
"error": {
"message": "you are not authorized"
}
}

what do the logs say?

I disabled the access to metadata since they are always null, after allowing the metadata I can access it already - though it's empty.


Use devDependencies for testing packages

An attempt to make the catalogue Docker build a bit smaller by moving testing packages from dependencies to devDependencies.

Something to remember here is that we need to make sure things keep working in CI.
Maybe we should split it this way

local -> yarn install
test -> yarn install
build -> yarn install prod

I know this sounds sensible, but it's not what we're doing.

Where the devil are we using node-sass?

Where the devil are we using node-sass?

I accidentally deleted node-sass in the previous commit (I was over-eagerly adding things to the devDependencies, then had to move them back to dependencies when I realised I'd misunderstood the purpose of devDependencies again).
We still use sass for our base-level styles. We should probably consider moving everything over to styled-components.

Closing because having talked it through with @gestchild we don't think this approach can work (we need to run the tests against the built app in the Docker container, so there aren't any dependencies that are dev-only).


docs: examples

WIP

PR says WIP, would be useful to have a note that the examples are WIP as well :)

@VictorBjelkholm I started this work today. I like to keep open PRs as I develop stuff. Examples don't exist yet as they require me to change other things to make them work as I want to (i.e improve API, docs, fix errors, etc). Sorry for the confusion!

@VictorBjelkholm it is coming https://github.com/libp2p/js-libp2p/pull/99/commits/19d67b920e0505e847ef117199f51f677de79263 ;)

Let's do an experiment and open these up through reddit for the community to jump on and review :)


Task/aa 3953 prepare information card for clickable icon

https://github.com/user-attachments/assets/4981293a-48c1-4f98-8f3e-5de713eef6ef

Screenshot of the padding reworked


Remove whitespace from k8s generated components

Signed-off-by: ashish<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

Add appropriate label to this PR.

Task linked: CU-2640mnb Ensure that K8s generated components have whitespace added appropriately.


Homepage of React App Hosted on Amplify Returns a Blank Page Occasionally

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d2so3m8bcmxfn4
Region
us-east-1
Amplify Hosting feature
No response
Describe the bug
I created a React App with route.js and hosted it using the GitHub option for Amplify.
Refreshing the homepage or loading the homepage will result in a blank page occasionally. Sometimes, the page renders correctly and other times it just appears as a blank white page.
This seems to only be occurring on the homepage.
The following errors appear when the website returns a blank page:
TypeError: Cannot read properties of null (reading 'classList')                             react-dom.production.min.js:216
    at a.value (index.js:16:29)
    at yo (react-dom.production.min.js:219:411)
    at Tu (react-dom.production.min.js:259:160)
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
    at Bl (react-dom.production.min.js:122:325)
    at Pu (react-dom.production.min.js:252:279)
    at vu (react-dom.production.min.js:243:371)
    at react-dom.production.min.js:123:115
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
    at Bl (react-dom.production.min.js:122:325)

Uncaught TypeError: Cannot read properties of null (reading 'classList')            react-dom.production.min.js:123
    at a.value (index.js:16:29)
    at yo (react-dom.production.min.js:219:411)
    at Tu (react-dom.production.min.js:259:160)
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
    at Bl (react-dom.production.min.js:122:325)
    at Pu (react-dom.production.min.js:252:279)
    at vu (react-dom.production.min.js:243:371)
    at react-dom.production.min.js:123:115
    at t.unstable_runWithPriority (scheduler.production.min.js:18:343)
    at Bl (react-dom.production.min.js:122:325)

Two other errors are generated by the console, but they seem to appear regardless of whether the website renders properly or not (not sure if these are relevant):
    GET https://charitypitch.texasusit.org/assets/css/style.css net::ERR_ABORTED 403
    GET https://charitypitch.texasusit.org/assets/css/colors/default.css net::ERR_ABORTED 403

Image of blank page:

Expected behavior
The website should be able to get the css resources and not be rendering a blank white page.
Properly rendered site:

Reproduction steps

Go to homepage
Refresh multiple times until blank page appears

OR

Repeatedly open Website URL in new tab
Blank page appears

Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: build
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information

None of these errors or blank page occur when doing a local host in the production build folder of the react project.

Several threads online suggested adding a rewrite for the index.html page, but that didn't work for me:
      Source address: </^[^.]+$|\.(?!(css|gif|ico|jpg|js|png|txt|svg|woff|woff2|ttf|map|json|webp)$)([^.]+$)/>
      Target address/index.html
      Type: 200 (Rewrite)

Tried switching to manual builds and used the compressed build folder. Same issue.

Hi @aaronlee232 👋🏽 we are investigating this error and will report with an update shortly.

Facing same issue with nextjs SSR . Sometimes rending blank page on fast redirections. No errors getting logged in cloudwatch as well

did you guys got any answer to it

I ended up switching to using s3 buckets to host the site.
I still had issues with the blank page, but I think I managed to fix it. I think the error was a combination of missing css files and the trying to access a dom element that hasn't been mounted yet.
I fixed the css errors by explicitly adding the missing css files into the build directory in a github actions workflow step.
as for the DOM error, this line was my problem:
document.getElementById("top-menu").classList.add("nav-light");

The top menu element wasn't rendered in the dom yet, so I was essentially trying to access the classList of a null type.
I found a solution online which was to write an async version of getElementById
const getElementByIdAsync = id => new Promise(resolve => {
  const getElement = () => {
    const element = document.getElementById(id);
    if(element) {
      resolve(element);
    } else {
      requestAnimationFrame(getElement);
    }
  };
  getElement();
  alert("element got");
});

and change my original code to this
const topMenuElement = await getElementByIdAsync('top-menu');
topMenuElement.classList.add("nav-light");

We had to switch to Vercel.  Much faster and no blank issues coming their.
No help from this Amplify team!

same issue here.
It occurs every time after an update.

same issue here. It occurs every time after an update.

Did you fix the issue? I'm getting the same one deploying to S3 with Vite and React?

same issue here. It occurs every time after an update.

Did you fix the issue? I'm getting the same one deploying to S3 with Vite and React?

yes. selfDestroying: true
https://vite-pwa-org.netlify.app/guide/unregister-service-worker

@aaronlee232 the CSS files are not part of the build artifacts but they are referenced in your index.html. Can you please run the build locally and make sure those files generated in the build output.
assets/css/style.css
assets/css/colors/default.css
The 404 issue no longer repro. This could be related to client side transient network issues.
Please create a new Issue if you are still seeing the error.


Give peripherals network access

When attached to a computer, provide that peripheral that computer's network until it becomes detached.
Perhaps an interface that extends IPeripheral and adds
void attachToNetwork(INetworkedComputerAccess computer);

Where INetworkedComputerAccess is extends IComputerAccess, and adds
Map<String, IPeripheral> getAttachedPeripherals();

Alternatively, we could add peripheral attachment handling API, where you can register handlers to do custom behavior on peripheral attach / detach. We could use this to check if peripherals implement an INetworkedPeripheral interface similar to the one outlined for the first suggestion.

I think both would be useful, though I'm not sure how the second one would be used by the user - how would the peripheral get access to the network if it doesn't implement some sort of networking API?
I would love to add a  pushToPeripheral method to OpenPeripheral inventories, which would require a custom provider, but I'm not sure how the IPeripheralAdapter would access the network.

The idea behind the second one would be that we use our own API to register handling of networked peripherals.
registerPeripheralAttachmentHandler(new IPeripheralAttachmentHandler() {
    private Map<IComputerAccess, INetworkedComputerAccess> accessMap = new HashMap<IComputerAccess, INetworkedComputerAccess>();

    @Override
    public void attach(IPeripheral p, IComputerAccess c) {
        if (p instanceof INetworkedPeripheral) {
            INetworkedPeripheral n = (INetworkedPeripheral) p;
            INetworkedComputerAccess access = new NetworkedComputerAccess_Impl(c);
            accessMap.put(c, access);
            n.attachToNetwork(access);
        }
    }

    @Override
    public void detach(IPeripheral p, IComputerAccess c) {
        if (p instanceof INetworkedPeripheral) {
            INetworkedPeripheral n = (INetworkedPeripheral) p;
            INetworkedComputerAccess access = accessMap.remove(c);
            n.detachFromNetwork(access);
        }
    }
});

So I've been looking at this for a bit now, and I'm having a touch of trouble. Issue is, IComputerAccess isn't exactly enough. The object passed needs to give the handler access to the entire peripheral network.
What object should I be trying to pass instead of IComputerAccess, and how should I be getting that object?

Here's an idea, maybe something closer to the BasicModem class? Slightly more abstract though, as it also needs to support giving an object to represent the computer as its own network when a peripheral is attached directly to it.

After derping about with the ideas I've mentioned, I realized they're not exactly coherent. The idea of a peripheral attachment handling API is counter to the idea that a peripheral's network access should be independent of its computer access. The peripheral attachment handling API suggested that the two be invoked in the same manor, but they're fundamentally different services, that are supposed to be invoked at different times.
Computer access is handled when connected to a new computer. Network access is handled when connected to a network. A peripheral can be attached to a single network, and consequently be attached to multiple computers. Or a peripheral can be attached to a single network with no computers at all.
So. After deleting much incoherent code, I think I finally have a solid plan for this. When a modem attaches or detaches its peripheral to the network, it will then call the INetworkAccess attach or detach method on the peripheral. No API abstraction. Just easy code.

I think that makes more sense - and it means we don't need to worry about rewriting IPeripheral.attach. I presume we would still have a custom INetworkedPeripheral interface though, and a custom way of providing them?
One potential issue is that peripheral proxies wrap the peripheral in a wrapper, so we would need a custom provider to work with this.

I suppose peripheral proxies could just implement INetworkedPeripheral, and delegate to the proxied peripheral if it is an INetworkedPeripheral?

Normally yes, but I don't think OpenPeripherals will add that. CCTweaks isn't a large enough mod for them to add support for it. I don't see any harm in additional providers - there is some other stuff I might like to try with OP integration. I know 99% of the time we wouldn't want it.
It would probably be a provider that runs off IPeripherals rather than using the same signature as the normal peripheral provider. It is more of a nice to have feature than a necessity though.

Oh duh. How would a provider be capable of this? Wouldn't it make more sense to do some ASM hacking to implement INetworkedPeripheral on their peripheral proxies?

 What I would love is an interface OP adapters can implement that allows them to use network access, but looking at it I'm not sure how possible that is.
I'm not sure I like either method. ASM seems hacky, and I'm not sure how a provider would work - what would the provider then call to get the peripheral to respond? My natural response would be "add providers to all the things!", though I'm not sure that is appropriate.
ASM is probably the best way to go then. I guess we can switch to a provider if we find we really need to.

I'm honestly surprised that the peripheral proxy tile even acts as an IPeripheral. I would have expected that the peripheral provider for it just deflects to the block its pointing at, rather than actually implementing a proxy object. Unfortunate that it doesn't just deflect. Then we wouldn't have to do anything at all

Also, the fact that it doesn't deflect means we can never fully support it. If a peripheral is accessing other peripherals on the network, it might be checking if some peripherals are instances of certain interfaces and such. The peripheral proxy doesn't implement whatever interfaces the user decides to make use of, and we can't provide a way to make it implement that.

I think the PeripheralProxy doesn't just return the peripheral is because it needs to support the peripheral changing - which isn't supported very well by default - with vanilla CC breaking a modem didn't even remove the peripheral in my testing.
I think I nicer way would be to provide a custom IPeripheralProxy interface which we inject into the peripheral proxy - and other people could use if they implement one. This means custom INetworkedPeipherals could check do:
if(periph instanceof IPeripheralProxy) {
  periph = ((IPeripheralProxy)periph).getPeripheral());
}

I'm wondering if we also want an ITargetedPeripheral interface - a peripheral that isn't a tile entity instance but is targeted at one (such as OpenPeripheral's AdapterPeripheral). I guess we might want a custom helper method of getBasePeripheral which does something like:
while(periph instanceof IPeripheralProxy) {
  periph = ((IPeripheralProxy)periph).getPeripheral());
}
return periph;

as you could technically chain peripheral proxies together and we aught to support that.


fix babylon_stl_util / splice

Vector iterators become invalid after any insert / erase!

I close this PR, because this fix is incorrect. However, there is a real bug in splice. I will post an issue with a way to reproduce it.


Update font-lekton-nerd-font-mono to 1.1.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] sha256 changed but version stayed the same (what is this?).
I’m providing public confirmation below.

Thank you for the contribution. It was merged directly as 72df9d8193939cbc8b47b7ac6d909bd51c67d91e. Your contribution is still credited to you.


Fwdport 6.2 to master

This brings much needed fixes that will go along with Integration's forward port.

Should update package.json for not be depending of the rel/6.2 dependencies

@ironman-machine let's retry !
SCALITY_INTEGRATION_BRANCH=fwdport/6.2-master

Hello @DavidPineauScality,
Starting end to end procedure using the following payload:
{"SCALITY_INTEGRATION_BRANCH":"fwdport/6.2-master","DEFAULT_BRANCH":"master","SCALITY_S3_BRANCH":"fwdport/6.2-master","REPO_NAME":"S3","PR_NUMBER":230,"ULTRON_URL":"connectore.ringr2.devsca.com:42000"}
Please follow http://ci.ironmann.io/gh/scality/Integration/4262 for circle status.

👍


Send push notification to the user using deviceToken

deviceToken being saved using below mutation:
mutation deviceNotificationTokenCreate($input: DeviceNotificationTokenCreateInput!) {     deviceNotificationTokenCreate(input: $input) {       errors {         message       }       success     }   }

Notification types:

[ ] Ibex USD Payment receive
[ ] Breez BTC Payment receive
[ ] Ibex USD Onchain confirm
[ ] Breez BTC Onchain confirm
[ ] Price change
[ ] Marketing notification

Closing this as we LNURLp notifications are working. For other notification types, let's use https://github.com/lnflash/flash-mobile/issues/172


COO-493: Fix alerts page kebab dropdown

This PR looks to fix an issue which was discovered in ACM Alerting, but also present in the primary monitoring-plugin which creates bad formatting within the kebab dropdown on the alerts page.
This issue stems from the change to using the Patternfly 5 deprecated components for the Dropdown, while missing some of the Patternfly 4 DropdownItems which should also have been migrated.
Before:

After:

/lgtm


Login redirect based on user role

Hello, it's not an issue but a question.
How can I set diferent redirects pages when user logs in according to user role?

Lets have a look at the onSubmitHook
You could do something like:
var mySubmitFunc = function(error, state){
  if (!error) {
    if (state === "signIn" || state === "signUp") {
      // Successfully logged in
      var userId = meteor.userId();
      if (Roles.userIsInRole(userId, ['view-secrets','admin'])) {
        Router.go('/my-secret-stuff');
      }
      // ...
    }
  }
};

AccountsTemplates.configure({
    onSubmitHook: mySubmitFunc
});

Perfect!! Thanks man

I've just realized there's another option: see, e.g., the Routes section for useraccounts:iron-routing and this post on SO
Using the redirect parameter might be clearer...

Nice, I will have a try!


Is AWS_PROFILE being cached?

Hello, I'm new to using this package (and python) and I do see some similar issues (linked at the bottom), but I think this demonstrates some unusual behavior. I hope this is helpful.
FWIW I'm using an S3 Compatible Storage called Scality.
Goal:
I want to be able to set the AWS_PROFILE environmental variable to a particular profile that has a record in my ~/.aws/credentials and ~/.aws/config file. Then I would like s3fs to pick up on that variable and use it for subsequent commands. Then if I change the profile (by overriding the AWS_PROFILE environmental variable), I'd like subsequent s3fs calls to use that one.
Issue:
The first half of my goal works. I can set the AWS_PROFILE to a non-default profile and s3fs will pick it up correctly. However, if I change the environmental variable, s3fs continues to try to use the original profile.
Note:
I'm including pandas S3 reads in here to demonstrate how, while the cache_regions fix (mentioned in the linked issues) does help s3fs its use within pandas doesn't seem to be getting picked up.
import os
import s3fs
import pandas as pd

# IF you have a default profile, this works, otherwise does not work (expected)
# i.e., if you have a default profile it will use it, otherwise it doesn't know so it will error, which is good
s3 = s3fs.S3FileSystem()
s3.ls("first-bucket")
pd.read_csv("s3://first-bucket/file.csv")
# <restart kernel before proceeding>

# works
# here we can see my first attempt at setting the env var is successful for s3fs and pandas
os.environ["AWS_PROFILE"] = "first-bucket-profile"
s3 = s3fs.S3FileSystem()
s3.ls("first-bucket")
pd.read_csv("s3://first-bucket/file.csv")

# does not work
# now when I go to change the env var, s3fs doesn't respect it (pandas doesn't either)
s3.ls("second-bucket") # expected to not work and indeed it does not
os.environ["AWS_PROFILE"] = "second-bucket-profile"
s3 = s3fs.S3FileSystem()
s3.ls("second-bucket")
pd.read_csv("s3://second-bucket/example.csv")
# ClientError: An error occurred (403) when calling the HeadObject operation: Forbidden

# works
# within the same kernel, if I update the profile env var AND say cache_regions=False
# it works for s3fs but not for pandas
os.environ["AWS_PROFILE"] = "second-bucket-profile"
s3 = s3fs.S3FileSystem(cache_regions = False)
s3.ls("second-bucket")
pd.read_csv("s3://second-bucket/example.csv") # does not work (same ClientError)

# works
# alternatively I did find that I could just set profile and of course it works but pandas does not
# unless I give it a profile in storage_options
s3 = s3fs.S3FileSystem(profile = "second-bucket-profile")
s3.ls("second-bucket")
pd.read_csv("s3://second-bucket/example.csv") # does not work (same ClientError)
pd.read_csv("s3://second-bucket/example.csv", storage_options={"profile": "second-bucket-profile"})

In summary, the first case where I set the env var works perfectly. I just wish it would work to simply change that env var a second time so that I can easily switch my pandas reads between profiles.
#701 #754

s3fs does not store the value of the environment variable, but it does store the S3FileSystem instances themselves. Thus, if you do S3FileSystem(...) with the same arguments as a previous instance, you will get that exact same instance back instead of creating a new one (this saves on various connection overheads).
To prevent the behaviour, you can pass skip_instance_cache=True for each instantiation, or set s3fs.S3FileSystem.cachable = False for the duration of the session.
https://filesystem-spec.readthedocs.io/en/latest/features.html#instance-caching

This worked great for me, thanks for the awesome package and quick response!


Drop Down Value with Opostrophe not Selected - Issue with Opostrophe

We need Select Value from Drop Down. So we are using text with apostrophe in it - example EXAMINER'S REPORT We tried all the option like Backlash, putting in Double Quotes but in vain. We hard coded the Index value, but didn't pick up. It picks up other value with normal text.   So we thought it could be Robot Issue.

You need to take this to the selenium2library github

Yeah, wrong issue tracker.


Trouble while installing in Google Colab

Hey Hesther,
Looking at all the appreciation and its presence in various other sources, I feel at loss not being able to use it.
Can you please help me installing it in Google Colab?
Thanks in advance
-Hemant

I haven't used Colab in a while, but can definitely try and get back to you!

You can do (within Colab):
!pip install -q condacolab
import condacolab
condacolab.install()

!conda install -y -c rdkit -c pytorch -c psi4 -c conda-forge rdkit pytorch scikit-learn scipy joblib tqdm psi4 resp
!pip install git+https://github.com/hesther/chemprop-atom-bond.git
!pip install git+https://github.com/hesther/espsim.git

I am not super proficient with Colab, so there might be better ways to do this, but this worked for me. If you reopen the notebook you will have to execute this again to install Conda and the relevant packages (takes a minute or two).
Note: Currently this will fail if you use partialCharges='ml' in GetEspSim() because I forgot to package a file correctly. Will fix that ASAP. But you can already use all other functionalities.

Wow! That was pretty quick.
Thanks a ton.

Just pushed a new version where ML charges now also work on Colab, yay! (By the way, if Colab gives you a warning about previously imported packaged in this runtime when installing Chemprop you may safely ignore it).

That's great. Thank you


Explore Base32 encoding

Thanks Jeffrey

We're going to have to distinguish different encodings. Right now, hex is assumed. We can prefix something like '0x32' or 'x32' or something to tell the other side that it will need to be decoded as base32. That gives us the ability to define other encodings and such.
This is going to be part of the "tunnel protocol".


Sending messages over 438 bytes long

The underlying AMQP implementation has a bug which is currently being investigated here: https://github.com/vcabbage/amqp/issues/54. This issue is a placeholder to raise visibility to consumers of this library.

This should be resolved at this point (upstream in amqp). I'm going to leave this open until I have a chance to verify the changes.


Add an error catch in python on_event when using hot-reloading

Currently, if we introduce a bug within the on_event function during hot-reloading event. The whole dataflow is going to stop because we're not catching the error. With the PR we'll allow errors and just warn the user.

Looks like this includes the commits from #382 now. Was this intended?

Made a typo in the error handling that's why I did not merged it yet. I also removed the unwanted commit.


Unexpected HTML Return for Invalid CrossRef DOIs in generate_citation_from_doi

Problem
The generate_citation_from_doi utility function is returning HTML-formatted strings instead of formatted citation text when provided with invalid (unregistered) HTTPS-prefixed DOI strings. This behavior is problematic because:

Incorrect Schema.org Usage: The HTML content is not suitable for the schema:citation property.
JSON-LD Markup Issues: The HTML can interfere with the escape sequencing of the JSON-LD markup, leading to malformed web pages.

Currently, the function is returning HTML even when the request header specifies a supported content type, see https://github.com/clnsmth/soso/blob/b7a54328ae86116b0622808843779e2506f9d789/src/soso/utilities.py#L215
The generate_citation_from_doi operates on content negotiation defined at https://citation.crosscite.org/docs.html#sec-4-1.
Example
When the function is called with an invalid HTTPS-prefixed DOI, it returns the following HTML:
from soso.utilities import generate_citation_from_doi

>>> doi = 'https://doi.org/10.5072/FK2/8b98e4f8c25bccc7263eda701c6969e8'
>>> citation = generate_citation_from_doi(doi, style="apa", locale="en-US")
>>> print(citation)

<!doctype html><html itemscope="" itemtype="http://schema.org/WebPage" lang="en"><head><meta content="Search the world's information, including webpages, images, videos and more ...

This results in a broken webpage when used in the Schema.org markup for the dataset.

Proposed Solution
Use lxml or a similar parsing library to check if the returned content is HTML-formatted.

If the content is HTML, return None or an appropriate error indicator.
If the content is a formatted citation, return the citation text as expected.

@clnsmth The crossref citation you generate differs from what is generated on the Data Portal landing page. The citations indexed by Google and others should be consistent with what we display on the Data Portal.

Hi @servilla,
Thanks for reaching out!
When generating citations, you have a couple options:

Use the built-in format: The generate_citation_from_doi function in the utilities module provides a default citation format. You can customize this by modifying its parameters (see here).
Define your own format: If you need a specific citation style, you can create your own format.

For both built-in and custom formats, you can overwrite the default behavior by generating the citation content and passing it to the kwargs parameter of the convert function in the main module (see here).


Any idea why this is error.

This code get an error: Value of type '(UIView) -> () -> UIView' has no member 'window'
@AssociatedObject(.OBJC_ASSOCIATION_RETAIN_NONATOMIC)
private var autoMaskView: UIView = {
    let view = UIView()
    view.bk_(whenTapped: { [weak self] in
        self?.window?.endEditing(true)
    })
    return view
}()

But after I replace the code with the macro expaned code, the error goes away.🤣
static var __associated_autoMaskViewKey: UInt8 = 0
private var autoMaskView: UIView
{
    get {
        if let value = objc_getAssociatedObject(
            self,
            &Self.__associated_autoMaskViewKey
        ) as? UIView {
            return value
        }
        let value = {
            let view = UIView()
            view.bk_(whenTapped: { [weak self] in
                self?.window?.endEditing(true)
            })
            return view
        }()
        objc_setAssociatedObject(
            self,
            &Self.__associated_autoMaskViewKey,
            value,
            .OBJC_ASSOCIATION_RETAIN_NONATOMIC
        )
        return value
    }
    set {
        objc_setAssociatedObject(
            self,
            &Self.__associated_autoMaskViewKey,
            newValue,
            .OBJC_ASSOCIATION_RETAIN_NONATOMIC
        )
    }
}

Regardless of Macro, it should not be possible to capture self before Self is initialized.
How about modifying it to assign after initialization as follows?
import UIKit

extension UIView {
    func bk_(whenTapped: () -> Void) {}
}

extension UIViewController {
    @AssociatedObject(.OBJC_ASSOCIATION_RETAIN_NONATOMIC)
    private var autoMaskView: UIView?

    func setup() {
        autoMaskView = { [self] in
            let ss = self
            let view = NSView()
            view.bk_(whenTapped: { [weak ss] in
                self?.window?.endEditing(true)
            })
            return view
        }()
    }
}

So the Macro is build before Self is initialized. It's different from just using a computing property, right?
So if I want to capture self, I can't use @AssociatedObject.


Don't use throw new errors when original error was throw by us (we lose original error information)

We have 3 places where we rethrow the original error, but as a new error with additional information.
We had 2 places in the extension where this caused issues, basically:

We are throwing exception of type A
Then we handle this and rethrow this as a new error type B (but retain some of the original error information)
Further up, we check if the error is type A, and do something
However the error is no longer of type A, its a new error.

Again, this was fixed recently in a PR, but we still have at least 3 areas that still do this.
Solutions:

Ensure we do not throw new errors if we had thrown the original error

E.g. instead of
throw new WrappedError(localize.DataScience.jupyterNotebookFailure().format(err), err);
We change this to
if (err instanceof BaseError){
	throw err;
} else
	throw new WrappedError(localize.DataScience.jupyterNotebookFailure().format(err), err);
}

This can be converted into a single liner as follows:
	throw WrappedError.from(err);

Where WrappedError.from can do the necessary checking.

Validated.


For in range with variable syntax not parseable

Take the following template:
{% for point in maxPoints-1..1 %}
    {# something #}
{% endfor %}

which produces the parsing error:
error[SyntaxError]: The parser encountered a syntax error
   ┌─ ./storefront/component/listing/filter/filter-rating-select.html.twig:44:25
   │
44 │         {% for point in maxPoints-1..1 %}
   │                         ^^^^^^^^^^^ expected twig expression but found word

After investigating this, I will unfortunatly close this as "won't do".
The simple solution to this problem looks like this

{% for point in maxPoints - 1..1 %}
    {# something #}
{% endfor %}

just use whitespace between variables and minus.
Reason
Ludtwig depends on WORD tokens which are allowed to contain -. This is done to parse all the HTML tags, but also ludtwig ignore statements for example.
This leads to maxPoints-1 be the WORD token, which is wrong in this twig context.
It is possible to just remove - form the WORD token lexer and this issue wouldn't occur, but that would break almost all HTML parsing and there isn't an easy workaround as far as I can see now.
Nice to know
{% for point in maxPoints+1..1 %}
    {# something #}
{% endfor %}

parses just fine, because + isn't part of a WORD token and thus maxPoints is the WORD again.


elasticsearch 8 upgrade

Elastic\Elasticsearch\Client client is Final with elasticsearch-php:8.0.x. So we could not use mocking for that class. We need to mock the ElasticSearchEngine class and count the search method of this function on the test_pass_client_to_callback and test_pass_search_builder_to_callback tests. Not finished yet.

I'm not sure in value of these tests. If you remove them code coverage changes?

That would be great if we could fix the tests here. We are trying to understand how many times we are going to search method in this test, and it can be good to understand the wrong calling for the search method.

Let's see coverage after removing that tests.

We can replace deleted tests with e2e test https://github.com/matchish/laravel-scout-elasticsearch/blob/master/tests/Feature/SearchTest.php that run search with callback
$results = Product::search('zonga', function($client, $body) {
    return $client->search(['index' => 'products', 'body' => $body->toArray()]);
})->raw();

And just check results.

We can replace deleted tests with e2e test https://github.com/matchish/laravel-scout-elasticsearch/blob/master/tests/Feature/SearchTest.php that run search with callback
$results = Product::search('zonga', function($client, $body) {
    return $client->search(['index' => 'products', 'body' => $body->toArray()]);
})->raw();

And just check results.

Ahh, that would be awesome. Mocking final class is a nightmare at this stack for now without external libraries and solutions. I had totally forgotten the feature tests. I will update my PR with feature tests.

The response of the elastic client is implementing the ResponseInterface of Psr now. I could not be sure all the cases would work correctly. I could not check everything end to end.  But as you see, tests passed. 💯

Could you update changelog and readme please?

Sure. 👍


Show status bar

Hi,
Is there a better way for showing status bar? Right now I am using:
getWindow().clearFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN);
I was wondering if any such method is included in library for showing status bar.

+1...would like to see a feature like this.


fix: rename useThrottleCallback and useDebounceCallback

What is the current behavior, and the steps to reproduce the issue?
useDebounceCallback and useThrottleCallback are not correctly named.
What is the expected behavior?
It should be useDebouncedCallback and useThrottledCallback
How does this PR fix the problem?
Renames tese hooks and ther import\use occurrences.
Checklist

[x] Have you read contribution guideline?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Is there an existing issue for this PR?

#129

[x] Have the files been linted and formatted?
[x] Have the docs been updated to match the changes in the PR?
[x] Have the tests been updated to match the changes in the PR?
[x] Have you run the tests locally to confirm they pass?

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Issues Testing open_kill.yaml example.

Initial Issue
I ran through your readme to an dincluding the priviliged execution. After this I try to apply the open_kill.yaml without result. https://raw.githubusercontent.com/cilium/tetragon/main/crds/examples/open_kill.yaml. Writing to /etc/passwd in the xwing pod is  still viable.
Restarting the tetragon service with kubectl rollout restart -n kube-system ds/tetragon still left me with write options in the folder.
Slack debugging
I posted the issue on slack and tested the following things:
Restart the service and tetragon and just applying the open_kill.yaml
  389  kubectl delete -f https://raw.githubusercontent.com/cilium/cilium/v1.11/examples/minikube/http-sw-app.yaml
  390  helm uninstall tetragon -n kube-systemhelm install tetragon cilium/tetragon -n kube-system
  391  helm install tetragon cilium/tetragon -n kube-system
  392  kubectl rollout status -n kube-system ds/tetragon -w
  393  kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.11/examples/minikube/http-sw-app.yaml
  394  kubectl apply -f https://raw.githubusercontent.com/cilium/tetragon/main/crds/examples/open_kill.yaml

This still gave no effect changing the password in the xwing container.
Remove other policies and restart the tetragon service.
  421  kubectl delete -f https://raw.githubusercontent.com/cilium/cilium/v1.11/examples/minikube/http-sw-app.yaml
  422  helm uninstall tetragon -n kube-system
  427  k delete tracingpolicies syswritefollowfdpsswd
  428  k get tracingpolicies
  430  helm install tetragon cilium/tetragon -n kube-system
  431  kubectl rollout status -n kube-system ds/tetragon -w
  432  kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.11/examples/minikube/http-sw-app.yaml
  433  k get all
  434  kubectl apply -f https://raw.githubusercontent.com/cilium/tetragon/main/crds/examples/open_kill.yaml
  436  k get tracingpolicy
  437  kubectl rollout restart -n kube-system ds/tetragon
  438  kubectl logs -n kube-system ds/tetragon -c tetragon

After restart it still does not affect output. The syswritefollowfdpsswd is the only active policy at this time.
For additional info you can check the slack entry by me (Andreas Joelsson) for the date 2022-09-23

This should be resolved by now.


Trace log level

Fixes #112, by adding trace to the possible log level values.
The underlying logging library, zap, will accept "custom debug levels" (i.e., levels numerically less than debug -- its levels are in ascending order of importance). It logs these with e.g., LEVEL(-2), but there's no way around that. At least the mechanism works.

We’ll need to allow trace in here https://github.com/fluxcd/flux2/blob/main/internal/flags/log_level.go


[frontend] 2023: Description & locale buttons are transparent if user is not logged in

getter activeLocale added into the header component

#2023

I see one test failure

we should not have locale query param here

ah, let it be here, but we have to fixt test to not fail


neon-cli: Unit tests

[ ] Cluster

[ ] Base
[ ] Prepare
[ ] Setup
[ ] Print
[ ] Verify

[ ] Login

[ ] Base
[ ] Export
[ ] Import
[ ] List
[ ] Remove
[ ] Logout

[ ] Scp
[ ] Ssh
[ ] Version

Closing: We have a decent number of neon-cli unit tests.


Better Dimming with Markdown Files?

I am loving using Twilight, but I have noticed that in markdown files Twilight does not proper see the see the beginning or end of each block. For example here you can see it highlight two blocks instead of just one. Is there anything I can do to get it to only highlight one block?

Have you tried tweaking the context config option?

Have you tried tweaking the context config option?

The issue is sometimes I have more than X lines I need to highlight around the current line.

I have also experienced a bit awkward dimming in markdown. I have set context to 0 and you can see results below.
I found out that using tree-sitter playground setting I could provide sensible values to expand option in Twilight config. These three values fix make entire paragraph, code block, and list highlighted.
require("twilight").setup({
  context = 0,
  expand = {
    -- markdown
    "paragraph",
    "fenced_code_block",
    "list",
  }
})

I am a bit concerned about possible naming collision in tree-sitter nodes, but I have no clue if it is a valid concern. If it is, then perhaps expand could be extended to provide values per filetype?
Default config with context = 0
Section and paragraph

Code block

List


Update openfga's entity_reconcile and remote_repo_get to require the editor role

Summary
The following PR updates openfga's entity_reconcile and remote_repo_get to require the editor role instead of admin.
The reason is we want the editor to be able to also manage repositories (based on our documentation) and currently this is not possible.
Fixes https://github.com/stacklok/minder/issues/3975
Thanks to @mesembria for flagging this! 🚀
Change Type
Mark the type of change your PR introduces:

[x] Bug fix (resolves an issue without affecting existing features)
[ ] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.338% (+0.009%) from 54.329%
when pulling d570755abb627163fe8e3ab0c2272afb4953c1fb on change-authz
into ad4fb4e7cb869386a0005d6e3de8aad472fbc965 on main.


Allow user to specify Telos endpoint

The user should be able to specify another endpoint in the UI.  The user should be able to save it in local storage to be used for future sessions.

@dappdever Is this an admin/configuration setting for the entire DHO? Not sure if  a user would understand this.

It would be at the user level. It's an advanced feature. The UI will have default endpoint(s) available also, as it does today, or even allow the user to choose from a drop down list.
The Light Wallet, as an example, comes with a list of endpoints, pings each one on startup, and then uses that one for the user.

Can we implement a heuristic like in the Light Wallet to determine what is
the best (e.g. most responsive) endpoint?
On Sun, Nov 22, 2020 at 12:08 PM Max Gravitt<EMAIL_ADDRESS>wrote:

It would be at the user level. It's an advanced feature. The UI will have
default endpoint(s) available also, as it does today, or even allow the
user to choose from a drop down list.
The Light Wallet, as an example, comes with a list of endpoints, pings
each one on startup, and then uses that one for the user.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/hypha-dao/dho-web-client/issues/204#issuecomment-731778363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF4UQTQ3C2XWDJZOT74FGZTSRFAPBANCNFSM4T6QO4XA
.

https://github.com/JoinSEEDS/seeds_light_wallet/blob/88b39c95d8f2bb841d34a14f3b5ef979313ab5eb/lib/providers/notifiers/connection_notifier.dart
We can replicate this process.
At the start of the app I ping all the endpoints and pick the fastest.
We can either let the user choose after if he's not OK with the selected network or simply keep this choice hidden from the user


Support for ES5 class patterns

Many libraries have functions like React.createClass which create classes that are "subclasses" of some main abstract class from that library. Although React now has ES6 class support, for other libraries we aren't that fortunate. It would be awesome to have some way to use these functions in a type safe way. This might come pretty close to being solved by #3694, but I don't think it will completely work:
interface ClassSpec<Instance> { [name: string]: ()<this: Instance> => any }
declare function createClass <Instance extends ClassSpec<Instance>>(spec: Instance); // Recursive type parameters don't work

Actually, I think you can do it.  In 1.6 it is possible to infer and intersect that types:
interface GenericClass<T> {
	new (...args: any[]): T;
}

function createClass<A, B>(baseClass: GenericClass<A>, extensionClass: GenericClass<B>): GenericClass<A&B>;
function createClass(baseClass: GenericClass<any>, extensionClass: GenericClass<any>): GenericClass<any> {
	/* do mixin */
	return baseClass;
}

class Foo {
	foo: string = 'bar';
}

class Bar {
	bar: number = 1;
}

let FooBar = createClass(Foo, Bar);

let foobar = new FooBar();

foobar.bar = 2;

@kitsonk That's a slightly different problem than the one I'm facing.my problem is that many libraries designed for ES5 require you to say var Person = SomeORM.createClass({...}) instead of class Person extends SomeORM.Model {...}. TS supports the latter, but not the former.

Ok, I guess why wouldn't this work?
interface GenericClass<T> {
    new (...args: any[]): T;
}

interface CreateClass {
	<T>(proto: T): GenericClass<T>;
}

declare var createClass: CreateClass;

let Foo = createClass({ foo: 'bar' });

let myFoo = new Foo();

myFoo.foo = 'bar';

Really what would help here is being able to return the value of this, which has a pull request out and is slated for TypScript 1.8 (the next version).

Come to think of it, this is completely solved by this typing. Yay!
P.S. Why is TS 1.7 going the way of Windows 9?

It's running around in a sunny field somewhere with TypeScript 1.2 :wink:

based on popular demand 1.7 is back... :D


PEP-517 build does not match poetry.lock

[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[ ] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

OS version and name: MacOS 10.14.4
Poetry version: 0.12.12
Link of a Gist with the contents of your pyproject.toml file: https://gist.github.com/ipmb/7acf540e1bad06c4812ad329326c0ad3

Issue
If I try to pip install . a project with this pyproject.toml I get the error:

ERROR: requests 2.21.0 has requirement urllib3<1.25,>=1.21.1, but you'll have urllib3 1.25.1 which is incompatible.

poetry.lock is correctly pinned to urllib3==1.24.2, but pip installs urllib3==1.25.1.
Should I expect the pip build-system to use dependencies from poetry.lock or can it only work against the dependencies as defined in the pyproject.toml?

Pip only understands build systems specified in pyproject.toml and has no notion of what's inside poetry.lock


Tooltip Arrow custom placement

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Hello.
I have a Tooltip using placement="bottom-start". This produces the following results:

I was wondering, if it's possible to reposition the arrow to the left, like this?

Examples 🌈
No response
Motivation 🔦
No response

Please share a CodeSandbox that demonstrates your tooltip. You can check how the tooltip appears with the bottom-start position at https://codesandbox.io/s/cold-monad-qgp56v?file=/demo.js. In that example, the arrow is positioned on the left side for long text.

Please share a CodeSandbox that demonstrates your tooltip. You can check how the tooltip appears with the bottom-start position at https://codesandbox.io/s/cold-monad-qgp56v?file=/demo.js. In that example, the arrow is positioned on the left side for long text.

Hello, thanks for the response. In the example you sent, the arrow is positioned to the center of the child element, which is not an elegant solution when working with dynamically changing widths. It would be great to set the position of the arrow using props.
https://codesandbox.io/s/tooltip-arrow-left-position-9gtv86?file=/demo.js

You can override the arrow Popper styles with the .MuiTooltip-arrow class. See https://codesandbox.io/s/tooltip-arrow-left-position-forked-sj2hz8?file=/demo.js. Use the !important rule on the left property to override the inline popper calculated styles. I hope this helps!

You can override the arrow Popper styles with the .MuiTooltip-arrow class. See https://codesandbox.io/s/tooltip-arrow-left-position-forked-sj2hz8?file=/demo.js. Use the !important rule on the left property to override the popper's calculated inline styles. I hope this helps!

thank you very much, I was searching for this. Really appreciate your contribution.

Appreciate the concept, but when you have more content in the tooltip, the arrow still doesn't display nicely at the "start". (In some more extreme cases, it literally displays at the end.)
https://codesandbox.io/p/sandbox/tooltip-arrow-left-position-forked-dpkwg9?file=%2Fdemo.js%3A23%2C1

Appreciate the concept, but when you have more content in the tooltip, the arrow still doesn't display nicely at the "start".
https://codesandbox.io/p/sandbox/tooltip-arrow-left-position-forked-dpkwg9?file=%2Fdemo.js%3A23%2C1
In some more extreme cases, used in a grid for instance, it literally displays the arrow at the end, and points to the wrong field entirely. In this case my cursor was at the highlighted U.

When there's less content, then it displays in a useable fashion (centered on the data), yet I'm using the placement='bottom-start'

Hello,
Test this solution: https://codesandbox.io/p/sandbox/tooltip-arrow-left-position-forked-7gzq7z?workspaceId=ws_SzhXwxFRYxciKVso4R9bwN

Thanks @hdale94 I changed it to slotProps because of the deprecation, and this works great for me now:
  <Tooltip
  title="Tip"
  arrow
  placement='bottom-start'
  slotProps={{
    tooltip: {
        sx: {
          marginTop: "10px !important",
        },
      },
      arrow: {
        sx: {
          position: "absolute",
          left: "6px !important",
          transform: "translate(0px, 0px) !important",
          marginTop: "-8px !important",
        },
      },
  }}
  >


fix(food-explorer): improve heuristic for region metrics computation

This PR improves the heuristic for metric computation for regions. Details about the heuristic are explained in https://github.com/owid/owid-issues/issues/258.
Additionally, it makes sure that values for Total are always shown for all regions.
In the notebook, basically, section 9.5 is new. Note that the order of subsections 9.X has changed (e.g. 9.6 has been moved)

Hm, it currently doesn't run

Thanks for the review @marcelgerber.
I just ran this etl locally and no error was raised:
.venv/bin/etl fbs
Detecting which steps need rebuilding...
Running 3 steps:
1. data://meadow/faostat/2021-04-09/faostat_fbs...
OK (7s)

2. data://garden/faostat/2021-04-09/faostat_fbsc...
OK (62s)

3. data://garden/explorers/2021/food_explorer...
OK (164s)

I am now trying to think where the desync might be occurring, but not sure at the moment

Hm, I ran it on owid-analytics, and you can try it there too:
ssh owid-analytics
cd etl-staging
.venv/bin/etl food_explorer

Maybe it's #76 again? Because you have different FAO API data locally than what is on etl-staging and my own machine (which are both pretty new installations of the etl)?

I slightly relaxed the validation check, the ETL should run now.
There is a mismatch in the output between staging and my local machine. Hence I was not able to detect this error. This is due to some error in my local data files (at ~/.owid/walden).


Begin modernizing install / build/ test

Modernizing to use setup.cfg for most install settings. This is great for automation/templating and simpler than dumping everything in setup.py. setup.cfg is the modern way to do things.
Python 3.4 is dropped by xarray and soon by other major packages. 3.4 is an increasingly deprecated pain to support; 3.4 will be very difficult to support past year end 2018.
Future pull request will begin switch from nose to pytest.  In general test code will become shorter and simpler to do the same things via @pytest decorators. I use pytest extensively in my packages.

Coverage decreased (-14.7%) to 68.889% when pulling 380d721b1df8f233914e256c6b06ddb8839a1057 on scivision:master into 9ecdf725378db6c833c1bacd51f6591a0a6ceb3d on rstoneback:master.

Dear @scivision , thank you for your interest in contributing to pysat.  Before your contributions can be considered, however, they must meet the guidelines outline in our documentation.  I do hope you will read it (https://github.com/rstoneback/pysat/blob/master/CONTRIBUTING.md), reformat your request, and continue to contribute.
Best regards.


MNT: Re-render the feedstock

Hi! This is the friendly conda-forge-admin automated user.
I've re-rendered this feedstock with the latest version of conda-smithy (0.10.0) and noticed some changes.
If the changes look good, then please go ahead and merge this PR.
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.
Thanks!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Simple re-rendering so merging. 😄

BTW, I was not awake 5 hours ago. (heroku scheduler) 😉

That's awesome, @pelson. So, how frequently does it go through the feedstocks?

Ask me in the meeting :stuck_out_tongue_winking_eye:

Sure we will have time? 😄

Sure we will have time? 😄

⌚ - I'm going to need to be pretty strict aren't I? My problem is that it is all so interesting and I get sucked in. I should spin off more discussions from the main hangout...
P.S. You have access to the scheduler for conda-forge-maint at https://dashboard.heroku.com/apps/conda-forge-maint/resources.
There is an hourly feedstock rerender job (limited to 5 PRs), and a daily linting job (just started it, and may need to reconsider depending on how it behaves).


[10.x] Add up option to make:migration command to omit the down method

It's seemingly becoming more popular to omit the down method in migrations and only migrate forwards.
Recently I saw a thread - https://twitter.com/ianlandsman/status/1705276749842424025 and thought perhaps this could be added to the make:migration command in Laravel by default as I always delete the down method once generated manually and it seems others are doing so as well.
I wasn't sure on the "by default" part but I figured the first step would at least have the command support "up-only" migrations.
Initially I had the option name be --up-only but figured --up would be clear enough.
php artisan make:migration add_external_id_to_users_table --up

return new class extends Migration
{
    /**
     * Run the migrations.
     */
    public function up(): void
    {
        Schema::table('users', function (Blueprint $table) {
            //
        });
    }
};

Happy to PR to the docs for this addition if merged.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Remove alt postfix in rpm assemble

Signed-off-by: Peter Zhu<EMAIL_ADDRESS>Description
Remove alt postfix in rpm assemble
Issues Resolved
#1545
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

UT https://github.com/opensearch-project/opensearch-build/runs/5685297062?check_suite_focus=true shall be updated as well.

more context for the fix
2022-03-25 00:08:09 INFO     Execute rpmbuild -bb --define '_topdir /tmp/tmphb0_r3b0' --define '_version 1.3.0' --define '_architecture_alt aarch64' opensearch.rpm.spec in /tmp/tmphb0_r3b0
error: Architecture is not included: aarch64
Traceback (most recent call last):
  File "./src/run_assemble.py", line 58, in <module>
    sys.exit(main())
  File "./src/run_assemble.py", line 49, in main
    bundle.package(output_dir)
  File<EMAIL_ADDRESS>line 102, in package
    self.min_dist.build(self.bundle_recorder.package_name, dest)
  File<EMAIL_ADDRESS>line 82, in build
    self.__build__(name, dest)
  File<EMAIL_ADDRESS>line 118, in __build__
    BundleRpm(self.filename, self.path, self.min_path).build(name, dest, self.archive_path, self.build_cls)
  File<EMAIL_ADDRESS>line 108, in build
    subprocess.check_call(bundle_cmd, cwd=ext_dest, shell=True)
  File "/usr/local/lib/python3.7/subprocess.py", line 363, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'rpmbuild -bb --define '_topdir /tmp/tmphb0_r3b0' --define '_version 1.3.0' --define '_architecture_alt aarch64' opensearch.rpm.spec' returned non-zero exit status 1.

Codecov Report

Merging #1829 (b6ad5ef) into main (c96aff0) will increase coverage by 5.46%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##               main     #1829      +/-   ##
=============================================
+ Coverage     94.53%   100.00%   +5.46%
=============================================
  Files           176         6     -170
  Lines          3622       105    -3517
  Branches         27        19       -8
=============================================
- Hits           3424       105    -3319
+ Misses          194         0     -194
+ Partials          4         0       -4

Impacted Files
Coverage Δ

src/assemble_workflow/bundle_rpm.py

src/system/os.py

...est_workflow/test_result/test_component_results.py

src/ci_workflow/ci_input_manifest.py

...ensearch_dashboards/build_artifact_check_plugin.py

src/manifests/manifests.py

src/ci_workflow/ci_check_list_source.py

src/run_sign.py

...orkflow/integ_test/integ_test_runner_opensearch.py

src/manifests/manifest.py

... and 160 more

Continue to review full report at Codecov.

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


chore: add sitemap audit to the API spec

Please ensure your pull request adheres to the following guidelines:

[x] make sure to link the related issues in this description
[x] when merging / squashing, make sure the fixed issue references are visible in the commits, for easy compilation of release notes

Related Issues
Ticket: https://jira.corp.adobe.com/browse/SITES-18817
Adding sitemap detection functionality in the audit API spec.

:tada: This PR is included in version 1.26.0 :tada:
The release is available on:

v1.26.0
GitHub release

Your semantic-release bot :package::rocket:


Check stubMappings before record again

When the record-mapping option is enabled, after restarting the WireMock server or resetting its requests. The first requests that were previously stored would be re-registered, resulting in duplicate mappings. With these changes, we prevent this from happening.

Could you add a test case that clearly articulates what this is doing?

Of course, the test case is already pushed but I needed to use an external URL to storage the JSON mapping file to check that it does not duplicate after a second client request. So feel you free to suggest me another manner to reproduce it, please.

Can I suggest setting up a second WireMock instance as the proxy target as the other record/playback tests do?
I'd prefer not to introduce external dependencies to the unit test suite.

Thank you for your tips! I hope to clarify it with the test case

Closing this as there's a new recorder in the works: #674


Cannot connect to service running in WSL2 from Windows

Windows Build Number
Microsoft Windows [Version 10.0.22000.168]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
4.19.128
Distro Version
Ubuntu 20.04
Other Software
No response
Repro Steps

Install Python 3 and pip
Install uvicorn: pip3 install uvicorn
Save the text below in a file named example.py and run uvicorn example:app from the same directory

async def app(scope, receive, send):
    assert scope['type'] == 'http'

    await send({
        'type': 'http.response.start',
        'status': 200,
        'headers': [
            [b'content-type', b'text/plain'],
        ],
    })
    await send({
        'type': 'http.response.body',
        'body': b'Hello, world!\n',
    })

In a windows command terminal, run curl http://localhost:8000; or go to http://localhost:8000 in a browser

Expected Behavior
Should see the text Hello, world! in the terminal or browser
Actual Behavior
Browser says connection reset, Powershell does this:
PS C:\Users\henxi> curl http://localhost:8000
curl : The underlying connection was closed: An unexpected error occurred on a receive.
At line:1 char:1
+ curl http://localhost:8000
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebException
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand

Diagnostic Logs
This seems to be a networking issue, because if I run curl localhost:8000 from another WSL terminal, I get the expected behavior.

This could be port forwarding issue. try shutting down wsl:
wsl --shutdown
check wsl instances are down:
wsl --list --verbose
Now restart you wsl.

Thanks for the suggestion @osamakhanedu, but been there done that after reading dozens of other posts here regarding similar issues. Just to be sure, I did this one last time:

Interesting, if I change the port to something much higher, like 60000, it works. I recall stumbling across something that discussed which ports WSL reserves, let me see if I can find that again...

@henxing - WSL doesn't reserve any ports, could you check if something in Windows is already using that port?

@benhillis it looks like the iphlpsvc possibly makes use of that port, but after disabling it, I don't see any changes. See below for the output of netstat -ab, in case that helps:
Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    <IP_ADDRESS>:135            orion:0                LISTENING
  RpcEptMapper
 [svchost.exe]
  TCP    <IP_ADDRESS>:445            orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:2179           orion:0                LISTENING
 [vmms.exe]
  TCP    <IP_ADDRESS>:2343           orion:0                LISTENING
 [lkads.exe]
  TCP    <IP_ADDRESS>:3580           orion:0                LISTENING
 [nisvcloc.exe]
  TCP    <IP_ADDRESS>:3582           orion:0                LISTENING
 [SystemWebServer.exe]
  TCP    <IP_ADDRESS>:5040           orion:0                LISTENING
  CDPSvc
 [svchost.exe]
  TCP    <IP_ADDRESS>:5357           orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:6000           orion:0                LISTENING
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:7680           orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:8080           orion:0                LISTENING
 [ApplicationWebServer.exe]
  TCP    <IP_ADDRESS>:49664          orion:0                LISTENING
 [lsass.exe]
  TCP    <IP_ADDRESS>:49665          orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:49666          orion:0                LISTENING
  Schedule
 [svchost.exe]
  TCP    <IP_ADDRESS>:49667          orion:0                LISTENING
  EventLog
 [svchost.exe]
  TCP    <IP_ADDRESS>:49668          orion:0                LISTENING
 [spoolsv.exe]
  TCP    <IP_ADDRESS>:49724          orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:59110          orion:0                LISTENING
 [nidmsrv.exe]
  TCP    <IP_ADDRESS>:59111          orion:0                LISTENING
 [lktsrv.exe]
  TCP    <IP_ADDRESS>:59112          orion:0                LISTENING
 [tagsrv.exe]
  TCP    <IP_ADDRESS>:5901         orion:0                LISTENING
 [wslhost.exe]
  TCP    <IP_ADDRESS>:6000         kubernetes:54217       ESTABLISHED
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:6000         kubernetes:54218       ESTABLISHED
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:6000         kubernetes:54219       ESTABLISHED
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:9999         orion:0                LISTENING
 [conveyor-svc.exe]
  TCP    <IP_ADDRESS>:49671        kubernetes:49672       ESTABLISHED
 [nimxs.exe]
  TCP    <IP_ADDRESS>:49672        kubernetes:49671       ESTABLISHED
 [nimxs.exe]
  TCP    <IP_ADDRESS>:49675        orion:0                LISTENING
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49675        kubernetes:49728       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49676        kubernetes:49677       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49677        kubernetes:49676       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49682        orion:0                LISTENING
 [niDiscSvc.exe]
  TCP    <IP_ADDRESS>:49682        kubernetes:49756       ESTABLISHED
 [niDiscSvc.exe]
  TCP    <IP_ADDRESS>:49683        orion:0                LISTENING
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49698        kubernetes:49699       ESTABLISHED
 [tagsrv.exe]
  TCP    <IP_ADDRESS>:49699        kubernetes:49698       ESTABLISHED
 [tagsrv.exe]
  TCP    <IP_ADDRESS>:49700        kubernetes:61900       ESTABLISHED
 [tagsrv.exe]
  TCP    <IP_ADDRESS>:49701        orion:0                LISTENING
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49701        kubernetes:49713       ESTABLISHED
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49701        kubernetes:49716       ESTABLISHED
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49701        kubernetes:49717       ESTABLISHED
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49701        kubernetes:49719       ESTABLISHED
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49701        kubernetes:49722       ESTABLISHED
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49701        kubernetes:49737       ESTABLISHED
 [nimdnsResponder.exe]
  TCP    <IP_ADDRESS>:49702        kubernetes:49703       ESTABLISHED
 [nimxs.exe]
  TCP    <IP_ADDRESS>:49703        kubernetes:49702       ESTABLISHED
 [nimxs.exe]
  TCP    <IP_ADDRESS>:49713        kubernetes:49701       ESTABLISHED
 [niDiscSvc.exe]
  TCP    <IP_ADDRESS>:49716        kubernetes:49701       ESTABLISHED
 [niDiscSvc.exe]
  TCP    <IP_ADDRESS>:49717        kubernetes:49701       ESTABLISHED
 [niDiscSvc.exe]
  TCP    <IP_ADDRESS>:49719        kubernetes:49701       ESTABLISHED
 [niDiscSvc.exe]
  TCP    <IP_ADDRESS>:49722        kubernetes:49701       ESTABLISHED
 [lkads.exe]
  TCP    <IP_ADDRESS>:49726        kubernetes:49727       ESTABLISHED
 [niroco.exe]
  TCP    <IP_ADDRESS>:49727        kubernetes:49726       ESTABLISHED
 [niroco.exe]
  TCP    <IP_ADDRESS>:49728        kubernetes:49675       ESTABLISHED
 [niroco.exe]
  TCP    <IP_ADDRESS>:49729        kubernetes:49730       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49730        kubernetes:49729       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49732        orion:0                LISTENING
 [niroco.exe]
  TCP    <IP_ADDRESS>:49737        kubernetes:49701       ESTABLISHED
 [NIWebServiceContainer.exe]
  TCP    <IP_ADDRESS>:49756        kubernetes:49682       ESTABLISHED
 [niroco.exe]
  TCP    <IP_ADDRESS>:49768        kubernetes:49769       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49769        kubernetes:49768       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49784        kubernetes:49785       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:49785        kubernetes:49784       ESTABLISHED
 [nipxism.exe]
  TCP    <IP_ADDRESS>:53107        kubernetes:53108       ESTABLISHED
 [GoogleDriveFS.exe]
  TCP    <IP_ADDRESS>:53108        kubernetes:53107       ESTABLISHED
 [GoogleDriveFS.exe]
  TCP    <IP_ADDRESS>:54217        kubernetes:6000        ESTABLISHED
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:54218        kubernetes:6000        ESTABLISHED
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:54219        kubernetes:6000        ESTABLISHED
 [vcxsrv.exe]
  TCP    <IP_ADDRESS>:56605        kubernetes:56606       ESTABLISHED
 [GoogleDriveFS.exe]
  TCP    <IP_ADDRESS>:56606        kubernetes:56605       ESTABLISHED
 [GoogleDriveFS.exe]
  TCP    <IP_ADDRESS>:56790        kubernetes:56793       ESTABLISHED
 [GoogleDriveFS.exe]
  TCP    <IP_ADDRESS>:56793        kubernetes:56790       ESTABLISHED
 [GoogleDriveFS.exe]
  TCP    <IP_ADDRESS>:61900        orion:0                LISTENING
 [nimxs.exe]
  TCP    <IP_ADDRESS>:61900        kubernetes:49700       ESTABLISHED
 [nimxs.exe]
  TCP    <IP_ADDRESS>:139       orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:139       orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:139      orion:0                LISTENING
 Can not obtain ownership information
  TCP    <IP_ADDRESS>:49422    <IP_ADDRESS>:https   ESTABLISHED
  WpnService
 [svchost.exe]
  TCP    <IP_ADDRESS>:49777    <IP_ADDRESS>:https    ESTABLISHED
 [msedge.exe]

As for my comment about "reserving ports", it's just some wording I vaguely recall from another issue I had found. I'll see if I can dig it up.

@benhillis it looks like the iphlpsvc makes use of that port, after disabling it, this works. Thanks for the suggestion to check for other services using that port from the windows side, hadn't run in to that before. Now that my toy example works, off to figure out why it doesn't work the same when running in docker. That's a separate issue, though, so I'll close this and open a new one.


JavaScipt Heap out of Memory while Running Nuxt.js on Development for a Long Time

Version
v2.3.4
Reproduction link
-
Steps to reproduce
Take a look this screencapt:

I'm running nuxt.js in development mode for more than 5 hours, suddenly that error arise.
What is expected ?
Nuxt.js running in development mode smoothly regarding how long it has ran.
What is actually happening?
JavaScipt Heap out of Memory error arise.

This bug report is available on Nuxt community (#c8264)

@jefrydco Can you try it with latest nuxt-edge? Unfortunately there are memory leaks (due to dev middleware, HMR, ...) that can't be easily avoided on our side.
https://github.com/nuxt/nuxt.js/pull/4439 should mitigate it.
This does not affect production mode

@manniL Oke, gotcha, thanks for explaining. Let me try nuxt-edge vesion.

Should be fixed in #5399


Eliminate error caused by typo

Currently when "pinapberries" is specified in the item list under UpdateLiveInventory in config.json, the following exception is raised:
File "./pokemongo_bot/cell_workers/update_live_inventory.py", line 200, in get_item
    raise ConfigException("item '{}' isn't available for displaying".format(item))
pokemongo_bot.tree_config_builder.ConfigException: item 'pinapberries' isn't available for displaying

It turns out "pinapberries" is misspelled as "pinabberries"; this update serves to eliminate the typo.

👍

merged #5954


Support InfoBox (styled InfoWindow)

Provide a way to pass the Node element for easy customization.

+1 would like this feature

@jlcarvalho @SebastianM  I have aded InfoBox Support i will be making pool request next week

@jlcarvalho @Dzivo sorry guys for the late answer. will review your stuff after rc.1 update. Thanks!

++++

@Dzivo Can you show me how you used the infoBox library in angular2?

Is this coming soon?

We should use infoBubble (https://github.com/googlemaps/js-info-bubble) for styling info windows. This should be also a new component: <sebm-google-map-info-bubble> because the official InfoWindow does not allow to style the container.

It was pretty easy to add support for infobox. As soon as i get some free time from projects i will make a pull request here is what i got.

If you could do it asap it will be great

Is this feature already supported ?

+1 would like this feature

+1

Hi Sebastian,
Any idea when we can use this feature?
Thanks

Is there any news on this case?

Any news?

@Dzivo Could you provide an example of how you were able to interpolate the template content for the content property for the options object for InfoBox? Are you still planning to push a pull request too?
Any insight would be much appreciated!

@Dzivo can you please share on how to style the info box?

For those that it interest, here is a work around that I found to customize the infowindow box size using the css.
div[style^="cursor"] {
width: 240px !important;
}
div[style^="display"] {
width: 240px !important;
}
div[style^="cursor"] > div > div[style^="position"]  {
width: 240px !important;
}
.gm-style-iw {
width: 240px !important;
top: 15px !important;
left: 0px !important;
}
and then using that you can stylize whathever you want to put in the sebm-google-map-info-window accordingly
Hope it helps

@efstathiosntonas @anthonypinskey  my example is just 2 complicated i forked the repository and changed a lot of it to make it work we need a way to do this it is one of the most common things you do with a map

We now support styled info windows with #1051 - that is not a solution with the help of InfoBox but it solves the problem. Feel free to contribute a version with InfoBox if you want to (we could ship it as another package e.g. agm/info-box)

@SebastianM This is awesome! Appreciate your hard work. When do you think beta.1 version will be released to NPM?

It is released :)