[Bug]: angular import error

Contact Details
No response
What happened?
i have installed the package with the following command
npm i tsparticles

i am running on angular version 13.3
When i declare and import the NgParticlesModule
as shown
import { APP_BASE_HREF } from '@angular/common';
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';

import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { HomeComponent } from './pages/home/home.component';
import { FormComponent } from './pages/form/form.component';
import { ParticlesComponent } from './components/particles/particles.component';
import { NgParticlesModule } from "ng-particles";

@NgModule({
  declarations: [
    AppComponent,
    HomeComponent,
    FormComponent,
    ParticlesComponent
  ],
  imports: [
    BrowserModule,
    NgParticlesModule,
    AppRoutingModule
  ],
  providers: [{provide: APP_BASE_HREF, useValue: '/'},],
  bootstrap: [AppComponent]
})
export class AppModule { }

and under the home component html file i have declared the html tag for the particle library
<ng-particles [options]="options" id="tsparticles"></ng-particles>

i cant build the application and shows me the following error
Error: node_modules/ng-particles/lib/ng-particles.component.d.ts:29:18 - error TS2314: Generic type 'ɵɵComponentDeclaration' requires 7 type argument(s).

29     static ɵcmp: i0.ɵɵComponentDeclaration<ParticlesComponent, "Particles", never, { "options": "options"; "url": "url"; "id": "id"; "particlesInit": "particlesInit"; }, { "particlesLoaded": "particlesLoaded"; }, never, never, false, never>;

tsParticles Version
2.9.3
Which library are you using?
Angular (ng-particles)
tsParticles Configuration
this.options = {
      fpsLimit: 60,
      particles: {
        color: {
          value: "#000"
        },
        links: {
          enable: true,
          color: "#000"
        },
        move: {
          enable: true
        }
      }
    };

What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

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

The latest version uses angular 15, which can’t be used with earlier versions. I’m moving away the components to improve the angular versions support, the angular repository is https://github.com/tsparticles/angular
You can open an issue there so it will be tracked correctly.


Update when Package Already Installed

module_configuration.py checks if a module is already installed, but does not run an update in these cases.
There are a few options for doing this. The first, we can update the initial install to use pip install -e <pkg>. We would then need to run a git pull for any updates to the pkg.
The second option is to run pip install <pkg> on the initial build as we are doing now. Then, if the pkg is already installed, we run pip install -U <pkg> to update it. This will require the version numbers in setup.py be kept up-to-date, which may not be feasible to rely on.
There is a third option that from my perspective is probably the best way to go, at least for now. This would combine the first 2 options. We would default to using pip install -U, but we would add an argument for module_configuration.py that would allow for editable installs via pip install -e, --editable. The script would then handle everything from there.
In the interest in testing and maintaining our options moving forward with this repo, I am going to implement the third option.

module_configuration.py already runs pip install -U pkg. This update was made with PR #8.


Charms to be integrated with grafana

This is a tracker issue to document progress with CKF charms that can be integrated with Grafana (aka provide a functional and useful grafana dashboard)

[ ] admission-webhook
[x] argo-controller There is a grafana dashboard that looks to be working well.
[ ] dex
[ ] envoy Some metrics in the dashboard are working. There are a handful of metrics configures there which I 'm not sure if all are needed in our envoy case.
[ ] istio-gateway
[ ] istio-pilot
[ ] jupyter-controller Its dashboard doesn't seem to work. Exposes two metrics saying "No data".
[ ] jupyter-ui
[x] katib-controller There is a dashboard that shows current experiments and trials. However, it could be improved depending on what decision we will take about grafana dashboards and given that katib-controller provides adequate metrics.
[ ] katib-db-manager
[ ] katib-ui
[ ] kfp-api
[ ] kfp-metadata-writer
[ ] kfp-persistence
[ ] kfp-profile-controller
[ ] kfp-schedwf
[ ] kfp-ui
[ ] kfp-viewer
[ ] kfp-viz
[ ] knative-eventing
[ ] knative-operator
[ ] knative-serving
[ ] kserve-controller
[ ] kubeflow-dashboard
[ ] kubeflow-rofiles(kfam)
[ ] kubeflow-roles
[ ] kubeflow-volumes
[ ] metacontroller
[ ] minio There's a grafana dashbaord that only shows N/A under all metrics.
[ ] mlmd
[ ] oidc-gatekeeper
[ ] pvcviewer-operator
[ ] seldon-controller-manager The grafana dashboard doesn't seem to work. I applied two SeldonDeployments and the Models metric showed "No Data"
[ ] tensorboard-controller
[ ] tensorboard-web-app
[ ] training-operator

I can confirm that jupyter notebooks, minio and seldon controller are missing data, while katib-controller and argo-controller work on the current deployment. If we could also include MLflow to that list: MLflow metrics Dashboard is also missing data.

MinIO
The issue there is that we have a label job=scrabe_jobs which is making the panel not rendering anything. Also, metrics minio_cluster_capacity is not provided by MinIO (anymore I guess).

Closing since these are now tracked in spreadsheet


Support json.RawMessage and json.Decoder.UseNumber

Going along with #12, it seems logical to support these as well to make a drop-in replacement for encoding/json.  I'll admit I'm not sure what the implications of each is but they're exported by the standard library so we'd have to find workarounds if they're not in objconv as well.

UseNumber is tricky because the decoder is generic and supports multiple serialization formats, for text-based formats like JSON and YAML it may make sense, but for binary encodings it may actually lose precision to have a string representation of a floating point value for example.
RawMessage is kind of the same, it needs to make sense in the context of the multi-format support of objconv, couple of reasons:

objconv.RawMessage loses information about the encoding of the byte slice
<format>.RawMessage means duplicating types in each sub-package, designing some ways to decode this in a generic way is quite complex
I'm not sure what the right behavior is if you try to write a raw message in one format to another encoding (for example json.RawMessage into a msgpack.Encoder), should we error? should we decode it and re-encode it on the fly?
On the decoder's performance, RawMessage is a pretty bad API, it requires parsing the content multiple times and adds dynamic memory allocations

In my experience, the need for those APIs is very rare, and can be avoided most of the time by designing code to embrace the zero-copy and strong typing model that objconv encourages.
I'll be happy to take a look at concrete examples that absolutely require those APIs to exist.

I don't think the APIs are absolutely necessary in the context I'm viewing them.
I'm seeing what we can do to convert them.


129c addition mixin dbodor

concatenate should only work if labels match.
this should be overridable if explicitly set (and if so consider requiring explicitly giving a new label).

Concatenation of EITData now checks whether the timing matches (i.e. object a ends before object b starts). We should consider making his optional with a boolean argument.


Gadget traits revamp

Looks good, worth being aware that this may cause merge conflicts with vanchor branch. @mfaghihi if you're ok with mirroring these changes we can merge.

Looks good, worth being aware that this may cause merge conflicts with vanchor branch. @mfaghihi if you're ok with mirroring these changes we can merge.

The only concern is that the Newaleaf implementation is changed in the other PR. The rest are fine


code improvements suggested by clippy

Removed a few needless returns, replaced .iter()s by slice refs, and de-referenced some matches.
Yay for readabiltiy. :smile:

Thanks for the PR!


Unable to run server on any port other than default

💬 Questions and Help
Running using docker-compose, setting port to something like 30002 in the yaml file and also changing it in options.json file, when restarting the image, it resets back to port 30000.  How would I run an instance using a different port?
foundry:
    container_name: fvtt
    image: felddy/foundryvtt:release
    restart: "unless-stopped"
    volumes:
      - '/data/docker/foundryvtt:/data'
    environment:
      - FOUNDRY_PASSWORD=password
      - FOUNDRY_USERNAME=user
      - FOUNDRY_ADMIN_KEY=anotherpassword
    ports:
      - "30002:30002/tcp"
    network_mode: host

Got it to work by removing the
mode:host

Glad you got it working!  🎉
Don't hesitate to me know if you have any other questions about the project.


Serializable

WIP until documentation is done. The branch name is misleading; I intend for this to be for all store types, not just MemoryCookieStore (which is what I started out with).

Add a getAllCookies interface to CookieStore so that stores can export all cookies.  In the case of stores where this is intractable or undesirable, they can elect to not implement getAllCookies.
The serialized format is vaguely:
  var serialized = {
    // The version of tough-cookie that serialized this jar. Generally a good
    // practice since future versions can make data import decisions based on
    // known past behavior. When/if this matters, use `semver`.
    version: 'tough-cookie@'+VERSION,

    // add the store type, to make humans happy:
    storeType: type,

    // CookieJar configuration:
    rejectPublicSuffixes: !!this.rejectPublicSuffixes,

    // this gets filled from getAllCookies after calling `toJSON` on them:
    cookies: []
  };

Importing the cookies repeatedly calls store.putCookie(), so this should work for all CookieStore implementations, in theory.  Cookie.fromJSON is called on each item in the cookies Array before being passed to .putCookie().

@lalitkapoor @inikulin @apsavin initial thoughts? Did I miss some way this might break existing clients? Can someone spot-check this with request and/or domjs?
I'd like to polish this up with documentation, etc. if yall are good with it.

@stash-sfdc looks great! - left one comment above

will give it a whirl with request

all request tests pass. Clone the memory store jar is frequent request in request - this is awesome. :+1:

LGTM :+1:

@apsavin good point. Old habits die hard so I really appreciate you pointing these out!

OK, revisions to retain creation sort order (see a5dfae6) and documentation are in.
Is anyone going to get mad that custom properties are being dropped in .toJSON()? If so, I guess semver says this should go to 2.0.0 since it's an API-breaking change.

I think we should follow semver, and since it's breaking let's do the major bump, followed by a release party :P

Why somebody will want to use custom properties?

Ok, I think we can merge now (but we need to bump version to 2.0.0 first). @stash Something else is left to do?

Nothing left, I think (thanks for the nudge). I'll re-review and tag 2.0 if it's good.

Alright, party like it's Fri, 31 Dec 1999 23:59:59 GMT ;)
https://twitter.com/jstash/status/608759537936367617

:tada:

haha, brilliant! thanks @lalitkapoor :)


runtime: Do not error if only initrd/rootfs image installed

If only initrd or rootfs image is installed,
allow to start Kata Containers without erroring
out.
Fixes:  #1174
Signed-off-by: Nitesh Konkar<EMAIL_ADDRESS>

/retest

/retest

Ping for review. cc @grahamwhaley @jodh-intel
@Pennyzct ARM CI is failing due to non-PR related issues.

@GabyCT @chavafg ping

/retest

Good to merge? @grahamwhaley @jodh-intel

has two acks.
Failed CIs are known issues (ARM, fc)
pullapprove is dead, long live pullapprove
the zuul WIP/SoB have not reported - but, I've manually checked they are present etc.
So, force merging..


Email server

First setup simple email forward, and later think about it's own mailbox

Created simple email server, now update MX records to redirect traffic there.


Regexp test selector does not seem to work.

I cannot see the regexp flag -goblin.run working unless I comment out the flag.Parsed() check in the Goblin constructor. In my tests it seems to always be true even though I do not see where else the flag.Parse() is called.
func Goblin(t *testing.T, arguments ...string) *G {
	// if !flag.Parsed() {
	parseFlags()
	// }

Removing the check seems to work well though.
The command I run is as follows:
$ go test ./pkg/... -v -goblin.run="regexp"

OR
$ go test ./pkg/... -v -args -goblin.run="regexp"

EDIT: I am using go1.11

Interesting. Maybe something changed in the latest versions of Go which changed this behavior. It's also strange that you changed the code and tests are still passing. I'll check it out in the weekend.

Any update on this? Thanks.

I've migrated from go1.9 to go1.13 and since then I've the same issue. Would appreciate any input or workaround regarding this issue

This fixed the issue for me, but lmk if you think there's a better solution @marcosnils


Latest version of docs docker file stops running

I just ran today on a Windows machine following command:
docker run --rm -it -p 8000:8000 -v C:\Development\Community\pnp\cli-microsoft365\docs:/docs squidfunk/mkdocs-material:7.1.7

The command failed with this exception.

Hi @plamber, apparently the docker image you are using does not include the tags dependency that we use in the repo.
You could just run the devcontainer in our repo, that contains everything you need.

I am using the instructions of our docs. A suggestion how to do tga

Where is this in our docs? Can't find it 😉

https://github.com/pnp/cli-microsoft365/wiki/Minimal-Path-to-Awesome
Under Windows

Yeah... we should change that!

https://github.com/pnp/cli-microsoft365/wiki/Minimal-Path-to-Awesome#preview-docs-using-mkdocs-installed-on-your-machine
This part has also gone out of date...
It should refer to the pip_requirements.txt file to install all the right dependencies.

That's a bit problematic, because so far we've been using the mkdocs-material image. With the introduction of the tags plugin, we need to check if we can keep using the existing image, albeit in a different version/setup or if we need to publish our own, or change the way we work with Docker.

So the good news is, that if we reference a newer version of the image, all works as expected. I'll update the MPA. Good catch @plamber 👏

MPA updated


Added Tableau Public Web Data Connector

Added a Web Data Connector built for Tableau Public. Which means you can analyse your Tableau Public data in Tableau Desktop.

Coverage remained the same at 98.913% when pulling ee7020157e6ddd09fbd164ed8c49e2ec8119aaf5 on andre347:patch-1 into 1ebaaa01737954481c8e0a6bcaeeadb4f0843d39 on tableau:master.


It ' s a great  idea to have addHeader method like ListView

This project is no longer supported and has been replaced by SuperSLiM. While SuperSLiM is still in heavy development, I already consider it much better and more stable than StickyGridHeaders. SuperSLiM also sees regular versioned releases.


Avatar component adds an alternative avatar prop

This function solves the problem (这个功能解决的问题)
Automatically load alternative avatars when the src of the Avatar component loads error
Expected API (期望的 API)
The component adds a'default' attribute, or the src attribute supports passing in a string array, the first item of the array is loaded by default, and the next item of the array is automatically loaded when the loading error occurs

@amadeus711 any update about this?
I'm glad to work on it and give a PR.

@amadeus711 any update about this? I'm glad to work on it and give a PR.

You can create a general image inside _internal folder and use it in avatar. We can finally move it to vueuc later.
The image component should suppport some fallback options.


Improved open_pbr_surface to standard_surface translation

Integrated the logic of coat_darkening from OpenPBR into the calculations of base_color and subsurface_color

Pearl comparisons:

OpenPBR
Standard Surface (original shader translation graph)
Standard Surface (latest shader translation graph)

Generated difference images between the Standard Surface image and the OpenPBR image for both versions. The original average difference was 0.92 (out of 255), and the new average difference is 0.57.

Carpaint comparisons:

OpenPBR
Standard Surface (original shader translation graph)
Standard Surface (latest shader translation graph)

Generated difference images between the Standard Surface image and the OpenPBR image for both versions. The original has an average difference of 1.57 (out of 255), and the new one has an average difference of 1.21.

![open_pbr_carpaint_ss](https://github.com/user-attach

ments/assets/36a5747f-4322-4445-81cb-377ddd68b4e9)

Carpaint comparisons:

OpenPBR
Standard Surface (original shader translation graph)
Standard Surface (latest shader translation graph)

Generated difference images between the Standard Surface image and the OpenPBR image for both versions. The original has an average difference of 1.57 (out of 255), and the new one has an average difference of 1.21.

I see, so this bakes in the darkening factor into the base_color (though coat_affect_color should be off I think, for that to work). That will work for an initial translation, though of course if the user decides to remove the coat afterwards (from the Standard Surface), the darkening persists.
The way we translate should depend on what the intended usage of the translated shader is. If it is assumed to be baked and immutable, then this kind of baking of the darkening is fine. But if the user might want to change the parameters (e.g. remove coat etc.), then it would be better to try to reproduce the structure as well as possible, e.g. keep the base color and just use the coat_affect_color parametrization to approximate the darkening.
I'm not sure what the more appropriate policy would be for these translation graphs.

Thanks for these notes, @portsmouth!
In my own experience, the most important quality of a shader translation graph is its visual parity, since the majority of the artistic work on the material usually occurs before shader translation was applied, and the receiving party is most interested in rendering the material as accurately as possible.
In situations where additional edits are needed, it's also possible to share the unbaked translated graph, in which the original shading model interface of the material remains available for further editing, though in practice it's more common to bake out textures in the new shading model.
From this perspective, I would consider @mkuo-lucasfilm's latest work to be a meaningful improvement, since there's a small but measurable improvement to parity for coated materials, and no reduction of parity for other materials.

Let's move forward with this refinement to the shader translation graph, and there's still time for additional improvements before the release of MaterialX 1.39.1.
Thanks for your great work on this, @mkuo-lucasfilm!


Add href to Links post items on main page.

Add href to post items in PostListItems, so that it renders correctly, even if JS is disabled in browser.

@prank7 not sure I understand, seems to render fine w/js turned off, but then again I just don't think I'm understanding what you're asking for...

@noahlocke Its fixed. This should have been closed.


Password?

After a few minutes, the desktop locks, as is the default behavior.
This requires a password to unlock. What's the password and how do we change it or disable it?

The default password is x11docker.
Since release 6.8.0 you can change it with option --password:
     --password [=WORD]   Change container user password and exit.
                       Interactive input if argument WORD is not provided.
                       Stored encrypted in ~/.config/x11docker/passwd.

What's that an option for? vncconfig?
In addition, I found you can discover the auto screen lock entirely by putting:
gsettings set org.gnome.desktop.screensaver lock-enabled false

in xstartup.

What's that an option for? vncconfig?

Oops, sorry, I've confused the repository. It is an x11docker option, but this repo does not use x11docker.

acoman This is the pass read readme


TODO List

TODO List

[ ] Parents
[ ] Help
[ ] Danger
[ ] Care

I don't think porn is allowed on github...

That's a good point. There's currently no porn on this repo tho.


[DOCS] Addition of no of forks star issue closed open pr to readme.md

Issue Title:
resolve issue: #249
Type of change ☑
What sort of change have you made:

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

Checklist: ☑

[X] My code follows the guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly wherever it was hard to understand.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have added things that prove my fix is effective or that my feature works.
[X] Any dependent changes have been merged and published in downstream modules.

Added Code

             Stars
            🍴 Forks
             Issues
             Open PRs
             Closed PRs

Screenshoot of Changes

@singodiyashubham87 please review the Changes.

@Anjaliavv51 Well Done, Keep contributing :)

@singodiyashubham87 please add Level label

@singodiyashubham87 please add level lavels

@singodiyashubham87 please add level lavels

@Anjaliavv51 According to the gssoc rules, this PR deserves only the gssoc label because it's a README change.


a11y: Focus move to visual panel after selecting dialog

Description

change the focus component after selecting
update the key navigation in project tree

Task Item
refs #2056

Screenshots

I agree with all three of @corinagum 's points. Those should be addressed before we merge this.


Fix typo: verison -> version

This PR is a

[ ] Documentation

What this PR does / why we need it:
Fix typo: verison -> version
Which issue(s) this PR fixes

Fixes #
Please leave this checklist in the PR comment so that maintainers can ensure a good PR.
Merge Checklist:

[ ] New feature

[ ] Tests
[ ] Documentation

[ ] SVCat CLI flag
[ ] Server Flag for config

[ ] Chart changes
[ ] removing a flag by marking deprecated and hiding to avoid
breaking the chart release and existing clients who provide a
flag that will get an error when they try to update

/assign @eriknelson

/ok-to-test
/lgtm

/approve


Search Engine Optimization

Have already tested any Ignite websites for Search Engine Optimization ?

No; you're welcome to test however you wish, then contribute anything you think is missing.


[Navigation] Add mechanism for specifying zOrder in transitions

Description
AnimatedContent supports setting a z-order on the transitions which can be useful for navigation transitions. For example when trying to implement a "slide from bottom" transition, the enter transition slides over the exiting composable (good) but the reverse will slide the exiting (popping) composable under the entering composable. If specifying the z-order could help to explicitly set the desired order for the composables.

How would you expect z-order to be exposed? As a property on each composable destination? Something else?

I think exposing it (somehow) on the definition of the transition would make sense. In the context of the transition (initial and target) I'd know what ordering I want...That might mean the transition block is no longer an AnimatedContentScope but an extension of it maybe?

I have the same issue. Having it inside transition definition would work I suppose.
Having it for each composable destination wouldn't work. If we take @hvisser example of "slide from bottom"

A -> B. B on top of A
A, B -> C. C on top of B
A, B <- C. C on top B
A <- B. B on top of A

any idea if this is something being worked on.  it would be great to have.

I think targetContentZIndex should somehow depend on screen index in backstack

Same issue for me, I just copied AnimatedNavHost and modified like this
val zIndex = backStack.indexOf(backStackEntry).toFloat()
And then changed AnimatedContent
transitionSpec = { finalEnter(this) with finalExit(this) },
to
transitionSpec = {
ContentTransform(
   targetContentEnter = finalEnter(this),
   initialContentExit = finalExit(this),
   targetContentZIndex = zIndex,
},

@SergKlimov Thats cool solution, but sadly, I tried to copy the AnimatedNavHost.kt content to my local package and it wont even compile :)
Can you give tip how you do it ?
Thanks

@SergKlimov Never mind, we must also copy file AnimatedComposeNavigator

@x4080 https://github.com/google/accompanist/issues/1160
transition.AnimatedContent(modifier, transitionSpec = {             val targetIndex = navController.backQueue.indexOf(targetState).takeIf { it >= 0 }                 ?: navController.backQueue.size             ContentTransform(                 targetContentEnter = finalEnter(this),                 initialContentExit = finalExit(this),                 targetContentZIndex = targetIndex.toFloat()             )         }

@codingfd thanks

Maybe it's time to get rid of stale bot?

We've added what we believe is the correct z-ordering in #1384, released as part of v0.27.1 and aren't planning on offering any ability to override it at this time. Please upgrade and try it out!

We've added what we believe is the correct z-ordering in #1384, released as part of v0.27.1 and aren't planning on offering any ability to override it at this time. Please upgrade and try it out!

Hey @ianhanniballake , I had a try but it's not good. I tried the navigation route: A -> B -> C -> B -> A, when the screen transition running from B -> A, the zIndex looks not good. Could you have a try?

Sounds like #1411, please follow along there.


[FEATURE] add ability to reopen results

Description
Problem: The only way to get/see the results is if you click on get results, but a user may want to see the past result after they changed the inputs.
Solution: Add this icon in the top right corner, when clicked it should open the results sidebar
Your Tasks

[ ] add the icon in the top right corner
[ ] when clicked, should open the results sidebar

Before contributing, read 👉🏾 this 👈🏾

It's great having you contribute to this project by creating an issue Make sure you are assigned to this before you work on it and you read the Contributing.md file, Thank you! Welcome to the community :nerd_face:

@Dun-sin I am ready to work on this.

can you shed more light on this. I don't know what the result side bar is.

can you shed more light on this. I don't know what the result side bar is.

Try using the project

I will have to calm down and study the code and get familiar with it.

@Dun-sin Can you assign it to me?

@Dun-sin Can you assign it to me?

Definitely, thanks for wanting to contribute, Make sure you follow the rules here, else your PR will not be accepted
Good Luck

@Ni-vik an upade pls?

@Ni-vik an upade pls?

It took me a while to understand the code base. I have added the icon in the top right corner..

I was not able to figure out the css as I am pretty bad in it as of now..
changes I made in the code

Added a div with class previous-result

Used this css to position the div

Do tell me if you need any changes in this.  I am trying to figure out the way to implement the second task .

@Ni-vik an upade pls?

It took me a while to understand the code base. I have added the icon in the top right corner..  changes I made in the code

Added a div with class previous-result

Used this css to position the div

Looks okay for now, I will make the changes for the positioning myself after you make a PR.
The send task is left and should be pretty simple, just reuse what is used to open the results using get Results to an event listener to this new icon

@Ni-vik an update on this pls

2022-10-19 21-07-10.zip
I have added the logo in each of the generator and then used the same logic as that of getResults so that when user clicks on the new icon it directs it to the results page. I have attached the demo video

2022-10-19 21-07-10.zip I have added the logo in each of the generator and then used the same logic as that of getResults so that when user clicks on the new icon it directs it to the results page. I have attached the demo video

sending me a zip file isn't ideal, i don't know if it contains a virus, you can either send a video or make your pull request

2022-10-19 21-07-10.zip I have added the logo in each of the generator and then used the same logic as that of getResults so that when user clicks on the new icon it directs it to the results page. I have attached the demo video

Also, I think you don't need to add the icon everywhere
Placing it between these two lines, will make it appear everywhere
https://github.com/Dun-sin/Code-Magic/blob/dabbd4658539a4f2429a754138763be6b2ae6e5a/index.html#L214-L215

2022-10-19 21-07-10.zip I have added the logo in each of the generator and then used the same logic as that of getResults so that when user clicks on the new icon it directs it to the results page. I have attached the demo video
sending me a zip file isn't ideal, i don't know if it contains a virus, you can either send a video or make your pull request
Sorry about that. I'll keep that in mind.

2022-10-19 21-07-10.zip I have added the logo in each of the generator and then used the same logic as that of getResults so that when user clicks on the new icon it directs it to the results page. I have attached the demo video

sending me a zip file isn't ideal, i don't know if it contains a virus, you can either send a video or make your pull request

Sorry about the zip file. I'll keep that in mind from the next time.

@Ni-vik also I need it done today at the latest, can you do that?

I won't be able to do that today.

i see, what about before the end of tomorrow?

@Ni-vik also I need it done today at the latest, can you do that?

I won't be able to do that today.

i see, what about before the end of tomorrow?

I can't guarantee you that as I have university exams going on this week.

:tada: This issue has been resolved in version 2.21.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


#10863: Refactor and cleanup namespace / filenames for DeviceMesh

Ticket
Link to Github Issue

Problem description
This PR is entirely a refactor/clean-up on the namespacing for DeviceMesh class.
What's changed

We've now renamed the files tt_metal/impl/device/multi_device.*pp -> tt_metal/impl/device/device_mesh.*pp
We've moved the class underneath the tt::tt_metal namespace to better map the files under the tt_metal directory.

Checklist

[ ] Post commit CI passes
[ ] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

Conceptually I'm confused by this location of device mesh under tt-metal (it's not really a problem with the change itself though). Why is the device mesh a tt_metal component? Doesn't it sit on top of and invoke ttnn operations? Shouldn't it be a purely TTNN concept?
Changing the namespace to reflect where the file is located makes sense to me though.

Conceptually I'm confused by this location of device mesh under tt-metal (it's not really a problem with the change itself though). Why is the device mesh a tt_metal component? Doesn't it sit on top of and invoke ttnn operations? Shouldn't it be a purely TTNN concept?
Changing the namespace to reflect where the file is located makes sense to me though.

I think originally multi_device.hpp was more lightweight, and runtime felt like it was a class that it might need at some point. But there's definitely a lot more functionality added in the last few weeks that are more TTNN and model concepts, maybe we can revisit whether device_mesh.hpp should be namespaced under ttnn.

Understood. I mixed this up with mesh tensor.


Farmer/pool public keys don't match with Chia.

The update several hours ago messed up the public keys... Now the public keys don't match with Chia's, please fix it!

Fixed in last update. Thx


DOC: special: prolate spheroidal docs wrong

Fixes gh-20991

Looking at the original Fortran code: https://people.math.sc.edu/Burkardt/f_src/special_functions/special_functions.f90 it is clear that the "argument of the radial function" (x) should be strictly > 1. See subroutine rswfp over there. Furthermore, we enforce this in the C translation of the code in our codebase--see the prolate_radial1 and prolate_radial2 function error checking in sphd_wave.h.

While in the neighborhood, fix up other docstring problems related to these functions, like copy-pase of characteristic value for functions that don't accept it.

[docs only]
Naturally, I spent quite some time looking for an actual bug first by comparing with the original Fortran, and didn't find one. While the literature related to these functions is untenably complex for me to read, and I see no modern implementation I can compare against, I would note that if you assume that I'm wrong and the F90 code is wrong, and you change the input validation in our code to enforce what the docs currently suggest on main, you'll still get NaN output because you end up with the square root of a negative number at: https://github.com/scipy/scipy/blob/8542c166eb1b0e3845fb7d9a3572af902e4e9b83/scipy/special/xsf/specfun/specfun.h#L4782
as x decreases the likelihood of a negative operand increases there, and when m is 1, you have sqrt of negative number.

As far as > 1 vs >= 1, I don't know if I can comment on that beyond trusting that the original F90 documentation author knows more than I (quite likely), so I went with what they had.

The Wikipedia article says

However, the range of the variable is different: in the radial wave function, ξ ≥ 1 while in the angular wave function, | η | ≤ 1.

That's probably where the mistake came from.

I think I can take a look within the next 5 hours.

Looks like this is the same function as Mathematica SpheroidalS1 except that the first two arguments are reversed there. That does seem to be extended to a wider range of arguments. See gh-5227. This might be considered to close that issue, too, since at least initially it was due to the same confusion about the domain given in the documentation.

OK, I had a chance to look at this. I'll give some background, but anyone who isn't interested can skip to the end for recommendations. The short of it is that the documentation for x is wrong for all of pro_rad1, pro_rad2, obl_rad1, and obl_rad2.
Background
These spheroidal wave functions are challenging to compute, but to understand what the domains should be, it's enough to know about prolate spheroidal and oblate spheroidal coordinate systems.  These are curvilinear coordinate systems, each based on taking an Elliptic coordinate system like below

and rotating it
Prolate: The focal axis (the line through the focii)
Oblate: The non-focal axis.
SciPy's prolate spheroidal wave functions use what Wikipedia calls the alternative definition of the prolate spheroidal coordinates. These are given by
three parameters $(\eta, \nu, \phi)$ where $\eta \in [1, \infty)$, $\nu \in [-1, 1]$.
SciPy's oblate spheroidal wave functions use a similar definition with three parameters $(\eta, \nu, \phi)$ with $\eta \in [0, \infty)$ and $\nu \in [-1, 1]$.
For at least the Prolate case, it's clear how this is based on this alternative definition for Elliptic coordinates which is explained pretty well in the linked article. The parameters $\eta$ and $\nu$ tell you where you are in elliptic coordinates, and then there's a rotational coordinate $\phi$.
A nice thing about these coordinate systems is that the Hemholtz differential equation is separable in each of them, meaning you can find solutions of type
$$\Phi(\phi, \eta, \nu) = f(\phi)R(\eta)S(\nu)$$
where each component function $f$, $R$, and $S$ satisfies an ordinary differential equation. In all of these cases $f(\phi)$ is just $\exp(im\phi)$, so the only functions of interest are $R$ and $S$, which are called the radial and angular components respectively. For each of the Prolate and Radial cases, it's common to look at different types of solutions that are said to be of the first and second kind. We have the following table of functions

Coordinate System
Kind
Component
Function

Prolate
First
Radial
pro_rad1

Prolate
First
Angular
pro_ang1

Prolate
Second
Radial
pro_rad2

Prolate
Second
Angular
pro_ang2

Oblate
First
Radial
obl_rad1

Oblate
First
Angular
obl_ang1

Oblate
Second
Radial
obl_rad2

Oblate
Second
Angular
obl_ang2

Recommendations
I checked through the docs for all of these in SciPy, and it looks like all of the radial ones are wrong. All of them say x should be restricted to |x| < 1.0 but pro_rad1 and pro_rad2 should both be restricted to x > 1 (although prolate spheroidal coordinates would allow x = 1, our functions don't handle that case currently so I think we should document the functions as they are.)
obl_rad1 and obl_rad2 should both be restricted to x >= 0.
I think one potential source of this confusion is that the parameter is called x in all cases. I'd support renaming it to eta for the radial functions and nu for the angular functions. I also think it would be a good idea to give more info on what these functions are about. In this PR I think it's fine just to fix the docs for pro_rad1, pro_rad2, obl_rad1, and obl_rad2.
Addendum
Also, I took a quick look at the Mathematica function SpheroidalS1 that @mdhaber pointed out, and played around with it a little using Wolfram Alpha. It can be used to compute both the prolate and the oblate spheroidal wave functions. You can go to the oblate case with the mapping $c \rightarrow -i c$, $\eta \rightarrow -i \eta$. They analytically continue the function into the whole complex plane, in this case, it ceases to have a physical meaning in terms of an intuitive coordinate system, but is probably useful in some other contexts. I really want to translate Arnie Van Buren's implementations into C++ and use those in SciPy. Those have more expansive domains and there are even complex versions. It will be a tough job, but I'm hoping to budget some time to do it.

I really want to translate Arnie Van Buren's implementations into C++ and use those in SciPy.

Want me to write a SDG proposal for it?

In this PR I think it's fine just to fix the documented domain for x for pro_rad1, pro_rad2, obl_rad1, and obl_rad2.
obl_rad1 and obl_rad2 should both be restricted to x >= 0

Ok, I pushed in a revision to include the x domain doc changes for obl_rad* functions.

argh, the mistakes are duplicated in various places, I'll try to fix a few more like the one Matt pointed out...

I really want to translate Arnie Van Buren's implementations into C++ and use those in SciPy.

Want me to write a SDG proposal for it? There is a call open.

Thanks for the offer, but I think the  extra funding wouldn't impact the time I have available. I actually put this as a milestone on the last SDG, https://github.com/scipy/scipy/issues/20223, but that was when I still thought it would be OK to just wrap the existing Fortran. If we could find someone else who could use the SDG funds to help them buy time to either translate or review, that could work though.


Update graphql peer dependency

I didn't want to touch the other dependencies given the open Greenkeeper PRs, but they should probably be updated as well.

Oh duh, this isn't that easy. Oops.

Oh this is really not that easy. I'm going to close this out for the moment because it's not really clear to me what the right strategy for doing type checking in consumers of graphql looks like.


Fix query_string syntax in writing_filters.rst

I tested correct syntax with elastalert == 0.2.0b2.
Using syntax from documentation(with additional query: key on top) produces errors:
WARNING:elasticsearch:GET http://<IP_ADDRESS>:9200/syslog-nginx__access_json-2019.06.03/_search?ignore_unavailable=true&size=0 [status:400 request:0.004s]
ERROR:root:Error running query: RequestError(400, u'parsing_exception', u'[query] query malformed, no start_object after query name')
INFO:elastalert:Skipping writing to ES: {'message': "Error running query: RequestError(400, u'parsing_exception', u'[query] query malformed, no start_object after query name')", 'traceback': ['Traceback (most recent call last):', '  File "/usr/local/lib/python2.7/dist-packages/elastalert/elastalert.py", line 559, in get_hits_aggregation', '    body=query, size=0, ignore_unavailable=True)', '  File "/usr/local/lib/python2.7/dist-packages/elasticsearch-7.0.1-py2.7.egg/elasticsearch/client/utils.py", line 84, in _wrapped', '    return func(*args, params=params, **kwargs)', '  File "/usr/local/lib/python2.7/dist-packages/elastalert/__init__.py", line 244, in deprecated_search', '    "GET", _make_path(index, doc_type, "_search"), params=params, body=body', '  File "/usr/local/lib/python2.7/dist-packages/elasticsearch-7.0.1-py2.7.egg/elasticsearch/transport.py", line 353, in perform_request', '    timeout=timeout,', '  File "/usr/local/lib/python2.7/dist-packages/elasticsearch-7.0.1-py2.7.egg/elasticsearch/connection/http_requests.py", line 143, in perform_request', '    self._raise_error(response.status_code, raw_data)', '  File "/usr/local/lib/python2.7/dist-packages/elasticsearch-7.0.1-py2.7.egg/elasticsearch/connection/base.py", line 168, in _raise_error', '    status_code, error_message, additional_info', "RequestError: RequestError(400, u'parsing_exception', u'[query] query malformed, no start_object after query name')"], 'data': {'rule': 'Example rule: nginx access status 200 > 1% for 60 sec'}}

elastalert == 0.2.4
There seems to be no problem with the latest version.
There seems to be no problem with the latest version. I tried it with the following description.
filter:
  - query:
      query_string:
        query: 'message:Quit'

elastalert == 0.2.4
There seems to be no problem with the latest version.
There seems to be no problem with the latest version. I tried it with the following description.
filter:
  - query:
      query_string:
        query: 'message:Quit'


npm install webtorrent-app -g

[x] Make bin script (https://github.com/feross/webtorrent-app/issues/247)
[ ] Publish to npm
[ ] Package the app in postinstall script

Just launching Electron is not sufficient. Arguments are handled differently in dev vs. production mode. And on OS X, the app will show up as "Electron" in the menu bar, not "WebTorrent" because there's no Info.plist.

You may want to look at https://github.com/brave/electron-prebuilt/commit/80392709b5a3221b22d63006041245602e1545be regarding naming the application binary without building for production.

Works fine on Linux as is

Mac and Windows have working auto updaters & should be installed the standard way


IPINIP support

Device-specific, config-based IPINIP support for v2. (#88)

PR needs updating

Updated.

Needs to be implemented for lbaas v1 as well

I added lbaas v1 support and tests: https://github.com/Cedev/a10-neutron-lbaas/commit/23a5247741d2dd489bf7f0a86df2f6eaf35d7059


Update MobileViT

Hi @lucidrains
I appreciate your fantastic work and have used it in my implementation a few times.
Recently, I accidentally found my implementation of MobileViT was merged into this repo, which was good, but I get annoyed that @murufeng is stating himself as the one who reimplemented.
https://github.com/lucidrains/vit-pytorch/blob/891b92eb749f441c308121d582e92431efd4d2a5/vit_pytorch/mobile_vit.py#L5
Moreover, there are some error settings in the model, redundant functions, and missing credits to be given. Therefore I followed your style to clean up the code and made this PR.
Thank you!

oh wow, i'm sorry this happened, if it is true
@murufeng do you have anything to say about this?

Hi @lucidrains  I'm very sorry, I did learn from the implementation of @chinhsuanwu  and made some slight modifications, and then submitted it to this project without making any statement. I'm very sorry for this caused you unnecessary trouble. Since it is the first time to submit PR, I will pay more attention to it in the future! Thank you!
Hi @chinhsuanwu  Thank you very much for your work. I just made some slight modifications of your implementation of MobileViT and submitted it to this project with a sharing mentality. I did not expect to cause a misunderstanding on your side.  I am very sorry for this. I have made a statement in my project, and also I will pay more attention to it in the future!  Thank you!


Update records.json

Please go the the Preview tab and select your preferred language | 请点击上方的 Preview 并选择你的语言

English
简体中文

Welcome! Please select one of the Pull Request templates as the current pull request told you to:

English
[简体中文](/.github/PULL_REQUEST_TEMPLATE/pull_request_template.zh-CN.md

Where is your website? You only post the subdomain name you want. Without the original URL to your website we can't point the CNAME record for you.

We are closing this application because you haven't provide your website link within one month. We always welcome you to apply for a subdomain again, simply by creating a new pull request.


Pane shouldn't steal focus from its children

This was removed in #14175 in order to solve #14173 (editors not being
focused when clicking tabs). However, it means that the pane steals
focus from its children. The solution is to add the guard back and to
solve #14173 in another way: by delaying the activation of the item
(see atom/tabs#439).

Thanks!


Rewrite ExtendedRequest filtering

Rewrite filtering to use Spring Condition and support "attributes" or
"operators" in the query param filtering.
Signed-off-by: Niels Thykier<EMAIL_ADDRESS>

Before merging this we need to bump version


Update java-jwt to 3.19.0

Updates com.auth0:java-jwt from 3.10.3 to 3.19.0.
GitHub Release Notes - Changelog - 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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.auth0", artifactId = "java-jwt" } ]

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

Superseded by #118.


[Request] brush add some event  API like OnTriggerEnter?

brush add some event  API like OnTriggerEnter OnTriggerMove or something else that can easy to know
relationship between brushs?
what's the easy way to know  the samething like that  for current version ?

Do you mean you want some sort of event to determine when a brush touches another brush in the editor? .. can you give me an example where you'd like to use this? maybe there's a better option?

yes,you're right
current I want to add an door to wall at the top view ,so I have to know brush touch event
and onDestory,Awake, OnTriggerExit.OnTriggerMove,will be pleasure.

Okay, this one will take a bit of work to implement. I'm thinking about putting this functionality outside of brushes though, for performance reasons. Perhaps another component that can be added to either an operation or brush..

sound great!


Task/auth add mobile

Added mobile number field for following screens

Create account
Edit Profile
Add User (Admin)

Thanks for offering this but this isn't a feature I'd be looking to include in the core project.
There's also a massive amount of unrelated changes in this PR.
Therefore I'll close this off.
Was this PR perhaps supposed to be opened against a custom fork, instead of the official bookstack project?

This was accidentally pushed to the BookStack repo. It was supposed to against custom fork repo. Sorry for the inconvenience.


Have Dns_forward operate on ipv4 and udpv4 modules, not an entire stack

Users will no longer have to construct additional modules and records which won't be used by Dns_forward.

Reducing the dependence on the whole Tcpip_stack seems like a good idea to me!

It looks like the CI builds failed for unrelated network errors. I've restarted the CircleCI one but I don't have access to the appveyor rebuild button-- I think the only way to trigger it is by pushing new commits :/

belated lgtm


Should the package names include the version?

Description of the new feature/enhancement
Should the package names include the version?

Proposed technical implementation details (optional)
I think that the version column is enough.

I don't think it should, simply because there's already a field for that.

I don't think it should, simply because there's already a field for that.

Exactly, I will make a PR to remove versions from current package names.

I'm the author of Royal TS and while I agree that the version should not be in the package name, it would be good to have at least an option to put the "major" version name in the package name somehow. The reason for that is, a new major version may require a new license key and users may not want to upgrade from an older major version to a newer major version using a package manager (automatically using a script) without getting a new license key first. In Chocolatey I maintain two packages at the moment: Royal TS V4 and Royal TS V5.

@StefanKoell I suppose that makes sense, especially since upgrading between two major versions (to take an extreme example, MS Word '97 and MS Word 365) can break a lot of existing workflows.
This should be determined on a case by case basis where the major version has a direct impact on the functionality/licensing/compatibility of the software, because some publishers/developers treat majors differently from others.

I also think that for some apps it's important to distinguish mayor versions. GNU/Linux distros put it sometimes, especially for programming languages.


Reboot test-suite

Design top-down approach to testing
Run all tests on MongoMock on sqlite in-memory
Test cases should be the minimal amount of boilerplate required to test all code (don't need to test VectorIndex, Listener and Model, for example.

[ ] #1151
[ ] #1170
[ ] #1171
[ ] #1172
[ ] ...

Here is the plan which resulted from the #1151:
Why
Write unittests which are super fast, clean (with mocks to separate concerns), and reflect the structure of the code
Important Features:

Reusable, simple fixtures
Parallelizable, faster execution
Ensures UT structure mirrors code structure
Utilizes MongoMock and Sqlite in-memory as database substitutes
Aiming for a long-term test coverage target of 90%

related to: #1150
Task List
This is the first step about the plan of Unittest, we just add the unit tests for importent classes.

For source code:

[ ] backend

[ ] base
[ ] filesystem
[ ] ibis
[ ] mongodb
[ ] sqlalchemy

[ ] base

[ ] artifact
[ ] config
[ ] config_dict
[ ] https://github.com/SuperDuperDB/superduperdb/issues/1171
[ ] document

[ ] cli

[ ] config
[ ] info

[ ] components

[ ] component
[ ] encoder
[ ] listener
[ ] #1172
[ ] vector_index

[ ] ext

[ ] openai
[ ] sklearn
[ ] tourch
[ ] transformers

[ ] jobs

[ ] job
[ ] task_workflow

[ ] misc

[ ] superduper

[ ] vector_search(all)

No for source code

[ ] #1170
[ ] #1179
[ ] #1180
[ ] Parallel test

After we finish that, we can continue to add the rest of the unit tests for the source code.

Why
Write unittests which are super fast, clean (with mocks to separate concerns), and reflect the structure of the code
Important Features:

Reusable, simple fixtures
Parallelizable, faster execution
Ensures UT structure mirrors code structure
Utilizes MongoMock and Sqlite in-memory as database substitutes
Aiming for a long-term test coverage target of 90%

related to: #1150
Task List
This is the first step about the plan of Unittest, we just add the unit tests for importent classes.

For source code:

[ ] backend

[ ] base
[ ] filesystem
[ ] ibis
[ ] mongodb
[ ] sqlalchemy

[ ] base

[ ] artifact
[ ] config
[ ] config_dict
[ ] https://github.com/SuperDuperDB/superduperdb/issues/1171
[ ] document

[ ] cli

[ ] config
[ ] info

[ ] components

[ ] component
[ ] encoder
[ ] listener
[ ] #1172
[ ] vector_index

[ ] ext

[ ] openai
[ ] sklearn
[ ] tourch
[ ] transformers

[ ] jobs

[ ] job
[ ] task_workflow

[ ] misc

[ ] superduper

[ ] vector_search(all)

No for source code

[ ] #1170
[ ] #1179
[ ] #1180
[ ] Parallel test

After we finish that, we can continue to add the rest of the unit tests for the source code.

Here is the plan which resulted from #1151.
Important Features:

Reusable, simple fixtures
Parallelizable, faster execution
Ensures UT structure mirrors code structure
Utilizes MongoMock and Sqlite in-memory as database substitutes
Aiming for a long-term test coverage target of 90%

Task List
This is the first step about the plan of Unittest, we just add the unit tests for importent classes.

For source code:

[ ]  backend

[ ]  2 base
[ ]  2 filesystem
[ ]  1 ibis
[ ]  1 mongodb
[ ]  2 sqlalchemy

[ ]  base

[ ]  2 artifact
[ ]  2 config
[ ]  2 config_dict
[ ]  1 Unittests for base.datalayer.Datalayer #1171
[ ]  1 document

[ ]  cli

[ ]  3 config
[ ]  3 info

[ ]  components

[ ]  1 component
[ ]  2 encoder
[ ]  1 listener
[ ]  1 Unittests for Model #1172
[ ]  1 vector_index

[ ]  ext

[ ]  1 openai
[ ]  1 sklearn
[ ]  1 tourch
[ ]  1 transformers

[ ]  jobs

[ ]  3 job
[ ]  3 task_workflow

[ ]  misc

[ ]  1 superduper

[ ]  2 vector_search(all)

No for source code

[ ]  1 Key pytest fixtures for setting up unittests #1170
[ ]  1 Move the existing unittest to the updated structure #1179
[ ]  3 Parallel test

The numerical prefix represents the priority, 1 represents the highest
After we finish that, we can continue to add the rest of the unit tests for the source code.

Plan about unittests

[ ] Reorganizing structure
[ ] Refactoring/ renaming fixtures


af_setImage doesn't work well with iOS 13

What did you do?
I'm having problems with Alamofire image with iOS 13, some images are loaded and placed, but other not. Is this a known problem with iOS 13? How can I fix it?
Alamofire Environment
**Alamofire version: 4.8.2
**Alamofire Image version: 3.5.2
**Xcode version: 11
**Swift version: 4
**Platform(s) running AlamofireImage: iOS 13
macOS version running Xcode:
Demo Project
ℹ Please link to or upload a project we can download that reproduces the issue.

Same problem
**Alamofire version: 4.8.2
**AlamofireImage version: 3.5.0
**Xcode version: 11
**Swift version: 5
**Platform(s) running AlamofireImage: iOS 13

Same problem. iOS 13 is releasing in a couple of weeks and our app is totally unusable due to this issue. We either need to stop using AlamofireImage or someone needs to give us more info.
Thank you very much
**Alamofire version: 4.8.2
**Alamofire Image version: 3.5.2
**Xcode version: 11
**Swift version: 4
**Platform(s) running AlamofireImage: iOS 13

All of our tests and demo project are working fine on iOS 13, so please provide additional information and, most helpfully, a demo project that reproduces the issue in the simulator.
This includes:

Any errors seen.
Kinds of images which sometimes don't load.
Any customizations you've made to the default ImageDownloader instance.
Code samples showing how you use af_setImage.

You should also be retesting on the new betas as you go, as this year's beta process has been particularly buggy.

Are you testing with iOS 13 SDK? Because the App developed for iOS 13 in Xcode 11 doesn't work well with Alamofire, instead, the same app that is already on the store for iOS 11 or superior, works fine.
We've have not customised the ImageDownloader istance;
sample of code using af_setImage:
imageToPlace.af_setImage(withURL: URL(string: artworkImage)!)
 There isn't a rule that make the images not loading, for example, sometimes it doesn't load the heavy images and sometimes it doesn't load the lights images.
We've have also checked the urls that are passed to af_setImage and they are valid

Yes, the testing was performed with Xcode 11 beta 6 on the iOS 13 simulator.
If you could perform some investigation on your side to narrow down why images might not be showing up, we could think investigate a fix. It could be a few things:

It's not actually downloading the image.
The image is downloaded, but is never rendered.
It's rendered but never appears in the image view.

Answering those questions would help narrow down a fix.

I've tried and I found that this part of code in the af_setImage function is never called
 // Generate a unique download id to check whether the active request has changed while downloading
        let downloadID = UUID().uuidString

        // Download the image, then run the image transition or completion handler
        let requestReceipt = imageDownloader.download(
            urlRequest,
            receiptID: downloadID,
            filter: filter,
            progress: progress,
            progressQueue: progressQueue,
            completion: { [weak self] response in
                guard
                    let strongSelf = self,
                    strongSelf.isURLRequestURLEqualToActiveRequestURL(response.request) &&
                    strongSelf.af_activeRequestReceipt?.receiptID == downloadID
                else {
                    completion?(response)
                    return
                }

                if let image = response.result.value {
                    strongSelf.run(imageTransition, with: image)
                }

                strongSelf.af_activeRequestReceipt = nil

                completion?(response)
            }
        )

Where does it return before then? From the initial guard, or the cache check?

sometimes, after let downloadID = UUID().uuidString, it goes directly to af_activeRequestReceipt = requestReceipt, sometimes it stops at let downloadID = UUID().uuidString without returning anything

That doesn't make much sense. Are you building with optimization?

yes, it's stetted to Optimize for speed [-O]

Please turn that off and test again, as it prevent breakpoints from working correctly.

I turnet all the optimizations to No Optimization, but it doesn't work anyway

Right, but you should now be able to trace the path more accurately.

ok, now it enter in the code and the response.result.value is nil, so it doesn't run  strongSelf.run(imageTransition, with: image)

Right. You should be able to check the response in that closure and make sure it has the appropriate response code, data, etc.

if I do a po response when I put the breakpoint the result is
error: Couldn't materialize: can't get size of type
error: errored out in DoExecute, couldn't PrepareToExecuteJITExpression

Yes, you must turn off optimizations for debugging to work correctly.

it's off

There are other settings that can interfere with debugging. At this point this doesn't look like an AlamofireImage bug. Please continue debugging until you discover the cause, and if it is a bug, please comment and I can reopen the issue.

In my case, I add support to the "application/octet-stream" into the acceptableImageContentTypes fix my problem
DataRequest.addAcceptableImageContentTypes(["application/octet-stream"])

Hi
also have the same problem. the af_setImage cause my app to crash.
in xcode 10 it worked fine. also after i updated my iphone to ios13
with xcode11 (official) it crashes.
the debugger points on
public static func af_threadSafeImage(with data: Data, scale: CGFloat) -> UIImage? {
lock.lock()
let image = UIImage(data: data, scale: scale)
lock.unlock()
return image
}
and in the console i see
seek:285: *** IIOScanner::seek reached EOF
getVal16:139: *** IIOScanner::getVal16 reached EOF
i tried the octet-stream from previous comment. didn't help

In my case, I add support to the "application/octet-stream" into the acceptableImageContentTypes fix my problem
DataRequest.addAcceptableImageContentTypes(["application/octet-stream"])
In iOS 13 Release note have the following statement:
To enhance security, URLSession no longer sniffs the MIME type when the server sends Content-Type: application/octet-stream. (7820658)
https://developer.apple.com/documentation/ios_ipados_release_notes/ios_13_release_notes

I found myself having this issue when I recently upgraded to Xcode 11. I can confirm the above was the actual issue, and adding the image content type fixed it for me. Not sure if ImageDownloader should have a default configuration for this, or the developer should always need to add this image content type. Either way, I feel it should be explained in the readme file. Thanks.

@jshier Hey, I believe @carlosh is right... can you reopen the issue?

We've added the application/octet-stream content type in f48f8cfe. It will be released shortly as part of AFI 4.0.0.
Cheers. 🍻

This is just for record and may help other developers in future.
The AWS S3 server we were connecting to download images was sending content type "image/*" and AF was throwing error.
We could get around this problem by using 'ImageResponseSerializer' :
 var imgSer = ImageResponseSerializer.self
        imgSer.addAcceptableImageContentTypes(Set(arrayLiteral: "image/*"))
        mView!.af.setImage( withURL: url,
                placeholderImage: mPlaceholderImage,
                **serializer: imgSer.init()**,
                filter: self,
                progress: nil,  imageTransition: imgTransition!, runImageTransitionIfCached: true, completion: { dr in  .....

AlamofireImage (3.6.0), Alamofire (4.9.1)

I faced this issue(even in iOS 15, AlamofireImage 4.2.0). I was using af.setImage to download and set images. The images were perfectly downloading from every url, other than the images in aws s3 bucket. The s3 bucket images weren't downloading and displaying properly.
After much debugging, I see that following are the acceptable content types in AFI.
acceptableContentTypes: ["application/octet-stream", "image/bmp", "image/gif", "image/heic", "image/heif", "image/ico", "image/jp2", "image/jpeg", "image/jpg", "image/png", "image/tiff", "image/webp", "image/x-bmp", "image/x-icon", "image/x-ms-bmp", "image/x-win-bitmap", "image/x-xbitmap"]
But the images in s3 have response content type "binary/octet-stream", so although the images are downloading perfectly and can be further retrieved from response data, they're getting AlamofireImage.AFIError.alamofireError(Alamofire.AFError.responseValidationFailed(reason: Alamofire.AFError.ResponseValidationFailureReason.unacceptableContentType(..)) and so they are unable to set in the imageview.
AFAIK AFI should include "binary/octet-stream" in the acceptable content-type as well!

@shreyadc
Yes had same issue and I solved it this way
`import AlamofireImage
ImageResponseSerializer.addAcceptableImageContentTypes(["image/jpg"])`

AlamofireImage 4.2.0 should have both application/octet-stream and image/jpg in the default Accept header.


[FLINK-17375][hotfix] Fix print_stacktraces multiline-behavior

What is the purpose of the change
echo $VAR   # does not preserve newlines
echo "$VAR" # does print newlines as well

Thanks! merging


Test: QuickOpen with ripgrep

Testing #24074
Complexity 2

[x] Windows - @bpasero
[x] Linux - @octref
[x] Mac - @sandy081

Use QuickOpen on a few workspaces and make sure it still works.
Use QuickOpen on a large workspace (e.g., Linux kernel, Chromium sources) and make sure the performance is not much different from 1.16.1 and is "acceptable". (It should improve on Windows.)

Seems to work quite nicely, good stuff 👍

Using VSCode on Ubuntu against newly cloned Chromium source, QuickOpen actually hangs the editor. Most searches cause visible lag in typing, and results often do not come out even after waiting 15 seconds. Guess we can have a sync tomorrow @chrmarti

I did give it a try on macOS, speed is leagues apart.

OK the issue was

I only assigned 2GB memory to Ubuntu VM, now I changed that to 8GB.
I was accessing a project on macOS using Parallel's sync feature (since git clone Chromium source actually failed when I only had 2GB memory). Guess that slows things down.


Contribute

Jrestless look be a interesthing project and is very use full for me.
I I would like to contribute with jrestless.
Exist a roadmap ?
What is your pretension for the future of the project ?

Hi @klebermagno ,
I am happy to hear this.
No, I don't have a real roadmap. I extend JRestless once API Gateway offers new features (binary support, etc.), bugs are opened or features are requested. At the moment I am trying to work on the remaining open issues and to document the framework.
I would love to see JRestless growing but at the moment I am the only developer and work on it in my spare time, only.
I hope this answers your questions - if not, let me know.

just in case this wasn't clear: I would highly appreciate contributions ;)

closing since inactive... feel free to re-open


importScriptsViaChunks not supported with InjectManifest

Library Affected:
workbox-webpack-plugin
Browser & Platform:
Node
Issue or Feature Request Description:
Hello, I was attempting to use the importScriptsViaChunks parameter on the InjectManifest constructor, but got the following error:
Please check your InjectManifest plugin configuration:
"importScriptsViaChunks" is not a supported parameter.

According to the documentation this should be possible, but perhaps this is just a documentation issue as the code doesn't seem to indicate any such functionality with InjectManifest?

Apologies, the JSDoc is in fact incorrect.
In InjectManifest mode, you should be able to just pull in any code you want added to your service worker via ES module imports, without having to use importScriptsViaChunks. webpack will compile your swSrc file and translate the ES module imports into the ready-to-use swDest file.

Thank you for your response, @jeffposnick.
My issue was that I wanted to pull in NextJS' build manifest file which is generated at compilation time, and I thought that it might've been possible with importScriptsViaChunks.
What I ended up doing was defining build id via webpack's DefinePlugin and calling importScripts inside the service worker file to get NextJS' build manifest definition. Can have a look here.


Feature Serial full stream control

This library should support all streams equally, it would make it more useful.
It is often useful to have both tethered and ip logging interfacing

[ ] add serial input listener and sessions (or any stream to be bind)
[ ] allow stripping ansi from serial

#23
#62
Several other requests for similar

Hi,
I also do need the serial input listener
Debug.available()
Debug.read()


go 1.12 binaries rejected from mac app store due to ___getdirentries64

The release notes mention something clever with regards to iOS, but not with regards to macOS. Here's a rejection I just received from Apple:

Guideline 2.5.1 - Performance - Software Requirements
Your app uses or references the following non-public APIs:
Symbol: ___getdirentries64
From framework: /usr/lib/libSystem.B.dylib
In binary: Contents/PlugIns/WireGuardNetworkExtension.appex/Contents/MacOS/WireGuardNetworkExtension
The use of non-public APIs is not permitted on the App Store, because it can lead to a poor user experience should these APIs change.
We are constantly reevaluating and identifying non-public APIs that you may have been using for an extended period of time. You should always use public APIs and frameworks and ensure they are up-to-date to prevent this issue in the future.

It then goes on with the usual boiler plate.
Note that this is for the macOS app store.
As I'm not using getdirentries64 (at least, I don't think I am...), I'll probably patch the runtime in some grotesque and heavy-handed way to make the problem go away in the short term. But Go really needs a proper solution to this. I imagine they're something like one of these:

Find a different syscall that isn't getdirentries, or
When being built for the app store, make the actual syscall instead of going through libsystem, or
Load the symbol with dlsym lazily as needed, rather than declaring it in the ELF, so that only users who use this get flagged, or
Remove this from go all together.

These are somewhat grotesque, but I just resubmitted using these:
https://git.zx2c4.com/wireguard-ios/tree/wireguard-go-bridge/goruntime-syscall-remove-getdirentries.diff
https://git.zx2c4.com/wireguard-ios/tree/wireguard-go-bridge/sys-unix-remove-getdirentries.diff

This appears to be an unforeseen extension of https://github.com/golang/go/issues/28984 . CC @eliasnaur

It seems that my fix for iOS needs to cover all of Darwin. I don't have the bandwidth right now, so I'm hoping someone else will take this up. Perhaps @randall77 can take a look.

Was your iOS fix something beyond just ENOSYS'ing those syscalls? If so, those two patches I linked above basically do that, and I can submit them to gerrit. Or did you actually wind up wrapping libc's readdir as a replacement?

Yes, I had to replace getdirentries in the directory listing code in the runtime. See https://go-review.googlesource.com/c/go/+/153338/. There was also an issue with the "64" suffixed system calls, but that might be different for macOS.

I think we'll need to do the same thing as CL 153338 for macOS.

Thanks for making it as cherrypickcandidate. I assume that means it'll wind up in 1.12.2, as this is sort of a significant regression.

@zx2c4, if you could patch the above CL in and try it, that would help.

I'll give it a go and report back. Note that you'll also need a corresponding one in x/sys, because that also links to the symbol.

@zx2c4: right.

@zx2c4 any word on trying the patch?

The CL still has crashes, last I read. Meanwhile I'm just ENOSYSing it out, which is suitable for my purposes.

@gopherbot please consider this for backport to 1.12.

Thanks @randall77! I've just received a rejection from the Mac App Store for this very issue. I'll use version 1.11 until this makes it into an official release.

If you submitted to AppStore for review was it with BITCODE = YES?
I cannot compile gomobile bind -target=ios  ... in a way when imported
in Xcode to compile with BITCODE = YES
How we solve this issue?


[Logs ] Electrum server issue

This is only on testnet and that is because of the current issue on testnet we have turned off our testnet server for the time being.


Set environment variable for doctests

Describe the problem you are trying to solve

Currently, it's possible to detect whether  a procedural macro is being used in a normal context (i.e. library or binary crate) or integration test depending on whether the CARGO_TARGET_TMPDIR environment variable is set. This is very useful for proc-macro-crate, which allows usage of a proc macro using types from a crate in the crate defining those types. However, there appears to be no way to distinguish between being used in a "normal context" and being used in doctests.
Describe the solution you'd like

In order to allow this, I think either CARGO_TARGET_TMPDIR should be set for doctests if that makes any sense, or a new environment variable should be introduced that indicates that the current build is for a doctest.
Notes

See also this issue: https://github.com/bkchr/proc-macro-crate/issues/10

Oh sorry, I actually meant to close this once I found https://github.com/rust-lang/rust/issues/54363 but forgot about it. It seems to me like the solution proposed in https://github.com/rust-lang/rust/issues/54363#issuecomment-1237544924 might fix this problem? In any case I think that issue is better in that it's about solving the underlying problem instead of applying random bandaids like suggested here.


T1 Add unit tests

Please review.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (bd9716a) 79.88% compared to head (2b2c7ec) 83.21%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #97      +/-   ##
==========================================
+ Coverage   79.88%   83.21%   +3.32%
==========================================
  Files          67       74       +7
  Lines        3350     3651     +301
==========================================
+ Hits         2676     3038     +362
+ Misses        674      613      -61

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Floyd Warshall Algorithm

@ayushagrawal41 contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


Failed to download media resources using 'downloadMedia', causing the process to stop

WA-JS Version
v3.8.2
WhatsApp Version
2.3000.1015802715
Browser Version
127.0.6533.120
Operation System
win11
Steps to reproduce
When a certain image in the chat history cannot be viewed due to "Can't view this photo because it's no longer on your phone.". Using downloadMedia to download this resource again will cause an error in the browser, which will stop my operation of downloading other media resources.
What is expected?
I hope to catch this error
What is actually happening?

Any additional comments?
No response

After checking the source code, it was found that it is most likely caused by this "await"

This await will not block continuously, it will take about one or two minutes to continue

What should I do to obtain the result of this' await '

Thanks for reporting the error, I will check and resolve it


Unable to create route when publishing a new webpack project

Deploying a webpack-type script returns an unknown error, seemingly at the Route::publish stage. I don't have a ton of awareness of what's going on past the stacktrace, but here's my wrangler.toml if it's helpful:
name = "workers-slack-bot"
account_id = "<redacted>"
zone_id = "<redacted>"
route = "https://workers-slack-bot.signalnerve.com/*"
type = "webpack"

And the stacktrace:
simple-slack-bot $ RUST_BACKTRACE=1 wrangler publish
⬇  Installing wasm-pack...
audited 8600 packages in 1.611s
found 0 vulnerabilities

Hash: c2b5f99171195a035acb
Version: webpack 4.30.0
Time: 123ms
Built at: 05/23/2019 1:22:40 PM
  Asset      Size  Chunks             Chunk Names
main.js  12.9 KiB       0  [emitted]  main
Entrypoint main = main.js
[0] ./node_modules/qs/lib/utils.js 6.06 KiB {0} [built]
[1] ./node_modules/qs/lib/formats.js 387 bytes {0} [built]
[2] ./node_modules/qs/lib/index.js 211 bytes {0} [built]
[3] ./node_modules/qs/lib/stringify.js 8.04 KiB {0} [built]
[4] ./node_modules/qs/lib/parse.js 8.29 KiB {0} [built]
[5] ./index.js + 6 modules 5.43 KiB {0} [built]
    | ./index.js 477 bytes [built]
    | ./src/handlers/lookup.js 946 bytes [built]
    | ./src/handlers/webhook.js 802 bytes [built]
    | ./router.js 1.95 KiB [built]
    | ./src/utils/github.js 445 bytes [built]
    | ./src/utils/slack.js 772 bytes [built]
    | ./src/config.js 113 bytes [built]

WARNING in configuration
The 'mode' option has not been set, webpack will fallback to 'production' for this value. Set 'mode' option to 'development' or 'production' to enable defaults for each environment.
You can also set it to 'none' to disable any default behavior. Learn more: https://webpack.js.org/concepts/mode/
🥳 Successfully published your script.
Error: Error("invalid type: null, expected a string", line: 21, column: 20)

stack backtrace:
   0: failure::backtrace::internal::InternalBacktrace::new::h899423eefab5fdf4 (0x10c06d418)
   1: <failure::backtrace::Backtrace as core::default::Default>::default::h2619c04ef0e2f942 (0x10c06d614)
   2: wrangler::commands::publish::route::Route::publish::hb105a10d1c4866aa (0x10bd244e0)
   3: wrangler::commands::publish::publish::h0fefecff7c7bec3b (0x10bd5329c)
   4: wrangler::main::h02840f944fb1a0a7 (0x10bd1f4f8)
   5: std::rt::lang_start::{{closure}}::hf83f8c2f8ba22f6f (0x10bd2726a)
   6: std::panicking::try::do_call::hf09ae321d60b9a09 (0x10c0e74d7)
   7: ___rust_maybe_catch_panic (0x10c0f0c9e)
   8: std::rt::lang_start_internal::h5162fc1065feec16 (0x10c0e7fbd)
   9: _main (0x10bd21f38)

Turns out that this might be happening with non-webpack projects, too. I'm deploying a different worker with project type javascript and getting this error:
assets-on-workers $ RUST_BACKTRACE=1 wrangler publish
⚠ JavaScript project found. Skipping unecessary build!
🥳 Successfully published your script.
Error: Error("invalid type: null, expected a string", line: 21, column: 20)

stack backtrace:
   0: failure::backtrace::internal::InternalBacktrace::new::h899423eefab5fdf4 (0x10c752d98)
   1: <failure::backtrace::Backtrace as core::default::Default>::default::h2619c04ef0e2f942 (0x10c752f94)
   2: wrangler::commands::publish::route::Route::publish::h28226564daaa540a (0x10c40d249)
   3: wrangler::commands::publish::publish::h8e72dac64475e3e4 (0x10c4391bc)
   4: wrangler::main::hea7dc5c1a0e03c38 (0x10c405119)
   5: std::rt::lang_start::{{closure}}::h768c74ced068225e (0x10c401a5a)
   6: std::panicking::try::do_call::hf09ae321d60b9a09 (0x10c7cd587)
   7: ___rust_maybe_catch_panic (0x10c7d738e)
   8: std::rt::lang_start_internal::h5162fc1065feec16 (0x10c7ce06d)
   9: _main (0x10c405748)

And my wrangler.toml:
name = "hugo-workers"
account_id = "<redacted>"
zone_id = "<redacted>"
route = "https://hugo-workers.signalnerve.com/*"
type = "javascript"

closed by #134


Make the directories' names look better

Make the directories' names look better
Added description for "Install in VS 2019"

Changes made.

Thanks!


Upgrade decimal library to 2.0

Hi,
Can you upgrade decimal dep to 2.0 ? It's impossible to use this driver with latest versions of jason and ecto.
Thanks!

Done! See new version 0.7.1

Done! See new version 0.7.1

Thanks!

Thanks!


FieldUserRenderer

Category
[ ] Enhancement
[ ] Bug
[ X] Question
Version
Please specify what version of the library you are using: [     1.8.0    ]
Expected / Desired Behavior / Question
Is it possible to use the 'FieldUserRenderer' Control in a SPFx WebPart or is its usage reserved for list (item) rendering?
Observed Behavior
I tried to include the Control like dokumented but now nothing gets rendered.
Source:
import * as React from "react";
import styles from "./HelloWorld.module.scss";
import { IHelloWorldProps } from "./IHelloWorldProps";
import { escape } from "@microsoft/sp-lodash-subset";
import { FieldUserRenderer } from "@pnp/spfx-controls-react/lib/FieldUserRenderer";

export default class HelloWorld extends React.Component<IHelloWorldProps, {}> {
  public render(): React.ReactElement<IHelloWorldProps> {
    return (

              Welcome to SharePoint!

Customize SharePoint experiences using Web Parts.

{escape(this.props.description)}

                Learn more

              <FieldUserRenderer context={this.context} />

    );
  }
}

Steps to Reproduce

Create a SharePoint SPFx Project for a WebPart, use the react template.
Install the necessery libraries
Copy the code from above

Thanks for the help!

Hello @FrediLehmann,
Yes, it's possible to use FieldUserRender react component on your WebPart. But it has a visible effect (makes sense) only if you provide at least one user there.
As for example, you can create a list with a user column(field), create an item there and set it with any user. Afterwards if you open DispForm of the created item you will see a user field value. It's similar to FieldUserRenderer control.
If you want to have PeoplePicker control on your WebPart, please use an appropriate component.

Hei Oleg
Good to hear, this would solve some future requirements.
Do you have an working example on how tho correctly use this component?
We have already put some time into it but weren't able to make it work correctly.
Thanks in advance.
Greetings
Fredi

Hi Fredi,
Yes, I did a WebPart for testing purposes, just for looking at spfx react components.
I hard-coded an array of users with only one item(as mentioned in a documentation, an user object must be IPrinciple type):
var myUsers = [];
myUsers.push({
  "id":"9",
  "title":"ABTO ABTO",
<EMAIL_ADDRESS><EMAIL_ADDRESS>  "picture":""
});

and put it to a state of a react component:
this.state = {
  users: myUsers,
};

Then I just imported a component:
import { FieldUserRenderer } from "@pnp/spfx-controls-react/lib/FieldUserRenderer";
and used it in a render function:
<FieldUserRenderer users={this.state.users} context={this.context}  />
Hope it will help you.

Is it still an issue/question or can be closed?

Can be closed


Play sound when answer is marked correct

The MITMH 2020 hunt website (https://pennypark.fun/) would play a sound every time you got an answer correct. It would be nice for Small Board to (optionally) play a sound when an answer is marked correct on Small Board.

It would also be nice for Cardi T to do something when puzzles or meta are solved, maybe message announcements or go into every voice channel and play victory music? Something hype that's not annoying.

@rawxfish , what does the "T" in Cardi T refer to?

+1 was wondering the same thing - I assumed it was from Cardinality

Re: the sound on solve, thoughts a coin drop or cash register sound?

I assumed it was from Cardi_nali_ty

Yeah that's right. Or maybe Cardi P for Cardinality Puzzles

Ooh that's nice too 👍

The easiest (or at least nicest) way to do this might be to use Django Channels to keep open a websocket connection to every smallboard user, then push a message to them and the front-end can play the sound.

The easiest (or at least nicest) way to do this might be to use Django Channels to keep open a websocket connection to every smallboard user, then push a message to them and the front-end can play the sound.

Reopening this Issue since we reverted the original implementation and would like to have this feature.

Reopening this Issue since we reverted the original implementation and would like to have this feature.


sanitycheck: check for deprecated variant variable

For those still using old variable ZEPHYR_GCC_VARIANT. raise an error if
the variable is not defined.
platform_whitelist does not deal with comma separated strings. Also remove
build_only option, this should also run on those devices.

Codecov Report

Merging #6220 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6220      +/-   ##
==========================================
+ Coverage   52.91%   52.92%   +<.01%
==========================================
  Files         414      414
  Lines       40355    40355
  Branches     7807     7807
==========================================
+ Hits        21355    21356       +1
+ Misses      15784    15783       -1
  Partials     3216     3216

Impacted Files
Coverage Δ

samples/philosophers/src/main.c
98.43% <0%> (+1.56%)
:arrow_up:

Continue to review full report at Codecov.

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


group by - all maps comparison

Relates to https://github.com/crate/crate/issues/11413

GroupingStringCollectorBenchmark will be updated as well as we use JDK map for String (and other non numeric types) and would be interesting to compare it with fastutil's Object2ObjectOpenHashMap and koloboke's HashObjObjMaps::newMutableMap - currently not in PR as I wanted to get feedback first.

Will not include baseline benchmarks for all maps as it would be repeat of http://java-performance.info/hashmap-overview-jdk-fastutil-goldman-sachs-hppc-koloboke-trove-january-2015/ and probably can find more comparisons - would rather focus on maps behaviour in our concrete case (collector).

Checklist

[ ] Added an entry in CHANGES.txt for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[ ] Touched code is covered by tests
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Hi @mfussenegger, could you please provide an early feedback before I make further changes (may be add more maps, update GroupingStringCollectorBenchmark)?

Can you provide us the current results?

Sure:
Benchmark                                                               Mode  Cnt     Score    Error  Units
GroupingLongCollectorBenchmark.measureGroupBySumLong                    avgt   10   789,063 ± 11,900  ms/op
GroupingLongCollectorBenchmark.measureGroupBySumLongFastutil            avgt   10   858,033 ±  9,494  ms/op
GroupingLongCollectorBenchmark.measureGroupBySumLongFastutilCustomHash  avgt   10  2217,310 ±  6,310  ms/op
GroupingLongCollectorBenchmark.measureGroupBySumLongJDK                 avgt   10   945,989 ±  1,632  ms/op
GroupingLongCollectorBenchmark.measureGroupBySumLongKoloboke            avgt   10   824,733 ± 21,479  ms/op
GroupingLongCollectorBenchmark.measureGroupingOnLongArray               avgt   10   240,444 ±  0,399  ms/op

Will add StringCollector once it's ready - so far both JMH and crate-benchmark shows that our current approach (Netty Map) is fine. But I still have some old spec to run.


copy: create (pseudo copy) empty source directories to destination - fixes #1837

This PR only creates empty directories rather than all the directories, reworked an earlier PR.
Reworked as highlighted in 74cbdea0.

@ncw I'm using fs.List to check if a directory is empty. Is there a better way of confirming empty directories?

This issue also addresses #1766


Unable to replace logo and profile images

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have searched for relatived questions
[X] I have read documentations

Describe the issue
@razonyang How to change the logo and picture of the website? I put logo.webp and profile.webp under static/images folder but it still does not work.
Steps to reproduce
@razonyang How to change the logo and picture of the website? I put logo.webp and profile.webp under static/images folder but it still does not work.
Expected behavior
@razonyang How to change the logo and picture of the website? I put logo.webp and profile.webp under static/images folder but it still does not work.
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of theme are you using?
require github.com/razonyang/hugo-theme-bootstrap v1.2.2 // indirect
What version of Hugo are you using?
hugo v0.117.0-b2f0696cad918fb61420a6aff173eb36662b406e+extended windows/amd64 BuildDate=2023-08-07T12:49:48Z VendorInfo=gohugoio
What version of Node.js are you using?
v18.18.0
What version of Git are you using?
git version 2.38.1.windows.1
Additional context
No response

Seems you're doing it right, does CTRL + F5 to force refresh helps?
It would be helpful to reproduce this issue if you can provide a public repo.

Okay, I managed to resolve it @razonyang, thank you! :)


Index out of range possible in merge program

The merge sort program here:
pp4fpgas/examples/merge_sort.cpp
has the following test statement that can fail:
if((f1 < i2 && in[f1] <= in[f2]) || f2 == i3)
When f2 == i3, the in[f2] test fails for array index out of range.  The code appears to work if the in[f2] test is separated and not performed when the values are equal.

Thanks for pointing this out.  I've updated the code to avoid it.


proposal: spec: generics: Anonymous generic aggregate types

I decided to implement some common functional programming primitives in Go2 and immediately was faced with a drawback of the design.
Given:
func Map[F, T any](f func(F) T, vs ...F) []T

I would like to write an idiomatic "table" test like this:
func TestMap(t *testing.T) {
	for _, tc := range []struct[F, T any] {
		Name     string
		Func     func(F) T
		Values   []F
		Expected []T
	}{
		{
			Name:     "strconv.Itoa",
			Func:     strconv.Itoa,
			Values:   []int{1, 2, 3},
			Expected: []string{"1", "2", "3"},
		},
		{
			Name:     "append string",
			Func:     func(s string) string { return s+"test" },
			Values:   []string{"1", "2", "3"},
			Expected: []string{"1test", "2test", "3test"},
		},
	} {
		t.Run(tc.Name, func(t *testing.T) {
			if ret := fungo.Map(tc.Func, tc.Values...); !reflect.DeepEqual(ret, tc.Expected) {
				t.Errorf(`Got:
%v

Expected:
%v`,
					ret, tc.Expected)
			}
		})
	}
}

Which does not work.
What actually works is this:
(from https://github.com/rvolosatovs/fungo/blob/13515ac078aa5099896ec57bbb7ad050e996c653/fungo_test.go2)
type MapTestCase[F, T any] struct {
    Name     string
    Func     func(F) T
    Values   []F
    Expected []T
}

func runMapTest[F, T any](t *testing.T, tc MapTestCase[F, T]) bool {
	return t.Run(tc.Name, func(t *testing.T) {
		if ret := fungo.Map(tc.Func, tc.Values...); !reflect.DeepEqual(ret, tc.Expected) {
			t.Errorf(`Got:
%v

Expected:
%v`,
				ret, tc.Expected)
		}
	})
}

func TestMap(t *testing.T) {
	for _, tc := range []MapTestCase[int, string]{
		{
			Name:     "strconv.Itoa",
			Func:     strconv.Itoa,
			Values:   []int{1, 2, 3},
			Expected: []string{"1", "2", "3"},
		},
	} {
		runMapTest(t, tc)
	}
	for _, tc := range []MapTestCase[string, string]{
		{
			Name:     "append string",
			Func:     func(s string) string { return s+"test" },
			Values:   []string{"1", "2", "3"},
			Expected: []string{"1test", "2test", "3test"},
		},
	} {
		runMapTest(t, tc)
	}
}

Observations:

Current type Name[<parameters>] struct{...} syntax does not support anonymous structs. A workaround could be to define a type TestCase[<parameters>] struct{...} right above the loop, but anonymous struct is cleaner IMO. Note that type declaration within a function does not work in go2go tool atm, but I assume that is a temporary thing.
~Currently go2go tool requires the type to be instantiated for range, that means that in order to test this, multiple loops would be required, which is not desirable.~

Proposal:

Allow struct[<parameters>]{...} syntax for definition of anonymous structs (or better refactor the proposed syntax to type Name struct[<parameters>] {...} for consistency). This also concerns anonymous functions etc.
~Allow range over generic structs as seen above~

Allow struct[]{...} syntax for definition of anonymous structs (or better refactor the proposed syntax to type Name struct[] {...} for consistency)

There's no obvious reason why structs should be special in permitted type parameters, when other types don't.  Why not permit type parameters for the other aggregate types?

Allow range over generic structs as seen above

I don't think this can be implemented.  You are relying on type inference when calling fungo.Map.  If we can make that call in a loop over a slice of parameterized structs, we have to instantiate fungo.Map separately each time through the loop.  But the current proposal only supports instantiation at compile time.  So we would have to break up the loop.  While we could do that for this particular example, we couldn't do it if the slice of parameterized structs were passed by another function in a different package.  So this seems impossible.

FTR, ended up with following structure:
https://github.com/rvolosatovs/fungo/blob/c21e889863bfa3f241f0522a8633ecbfad33027c/fungo_test.go2
Once go2go supports type declaration within function scope and anonymous generic functions are supported, this is "good enough" for me.

In the handful of statically-typed languages I'm aware of that support these kinds of loops (namely OCaml and, they are generally modeled as “existential types”. I see a few resources about existential types on the Internet,¹ but the best introduction I'm aware of is chapter 24 of Pierce's Types and Programming Languages.
Existential types are very closely related to Go's “interface types”: they define operations on abstract types, and at run-time they pack a descriptor for a concrete type together with a value that supports the defined operations on those types.
I think it would be possible in principle to extend Go's interfaces with generic types as proposed to produce something equivalent (or at least very close) to existential types. However, I don't have the bandwidth to look at that extension at the moment. (If there is a compelling use-case for this sort of extension, I might give it some more thought after ordinary type parameters are released. 😅)

¹

https://www.cs.cornell.edu/courses/cs4110/2018fa/lectures/lecture26.pdf has a very brief overview of the theory.
https://en.wikibooks.org/wiki/Haskell/Existentially_quantified_types has a good overview of existential types in Haskell.
https://ocaml.org/manual/gadts.html describes existential types in OCaml
https://stephenebly.medium.com/an-introduction-to-existential-types-25c130ba61a4 gives an overview of existential types in Standard ML, but notes that they can only be used at “module” boundaries. (Note that SML “modules” are analogous to Go “packages”, not Go modules.)
https://homepages.inf.ed.ac.uk/gdp/publications/Abstract_existential.pdf is the theoretical foundation for existential types in Standard ML, if you want more detail.

Based on the discussion above this is a likely decline.  Leaving open for four weeks for final comments.

Note you can also do this with interfaces, although you still have to put the test case details in a separate function.  To your example, add a method
func (MapTestCase[F, T]) runMapTest(t *testing.T) {
  // same as runMapTest you have
}

func TestMap(t *testing.T) {
  for _, tc := range []interface{ runMapTest(t *testing.T) }{
    MapTestCase[int, string]{...},
    MapTestCase[string, string]{...},
  } {
    tc.runMapTest(t)
  }
}

@benjaminjkraft awesome idea, that's what I ended up doing (different function, same idea)
https://github.com/rvolosatovs/fungo/blob/87e1d650160196a7037ce1f91dc9f0c43cfe2d23/maps/maps_test.go2#L11-L57
with the help of little shared interface https://github.com/rvolosatovs/fungo/blob/87e1d650160196a7037ce1f91dc9f0c43cfe2d23/internal/test/test.go2#L9-L11

No change in consensus.


Data Science with Python: Flask for Data Science

Description
Welcome to the 'DSWP' Team, good to see you here.
With this issue, readers will get introduced to the core information about 'Flask for Data Science' along with sample code completely in an effective way.
To get assigned to this issue, add your serial numbers mentioned in the spreadsheet of "Data Science with Python", the approach one would follow and the choice you prefer (Documentation, Audio, Video). You can go with all three or any number of options you're interested to work on.
If you had referred any resources, add them up in "DS Resources". Similarly, if you had used datasets, include them in "DS Datasets".
Domain: Machine Learning
Mentors Assigned: Dhruv Bajaj / Aishani Singh
Points to Note :
The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include the issue number along with it.
Changes should be made inside the Datascience_With_Python/ directory & Datascience_With_Python branch.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'GWOC' contributors of the 'DSWP' domain.
All the best. Enjoy your open source journey ahead. 😎
Domain
Datascience with Python
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[ ] I follow Contributing Guidelines & Code of conduct of this project.

@prathimacode-hub , Mam
I am M. Ashish Reddy. I would like to do video on this issue.
Batch number: 5
serial number:174.
Approach: A detailed explanation with examples and real life uses

Issue assigned to @ashish-reddy-20-08 for video contribution


Set datepicker date to current date

How do I set datepicker to current date

But date picker is not a question. It is one of the column in matrix dynamic

You can handle the onMatrixCellCreated event and access the options.cellQuestion

its working. Thanks  :)


Provide a telemetry story for extensions

Refs: #93604
Currently we don't have a good telemetry story for extensions. We do provide a telemetry library for Application Insights, but it explicitly talks about "first-party" extensions, and might have GDPR issues because of its opt-in being based on the VS Code opt-in.
It would be great if extension authors could just get access to certain telemetry on the marketplace dashboard (or something like that) without requiring any specific instrumentation. It would also be great for extensions that wanted to go above and beyond that, we provided an API for this purpose. To help avoid every extension having a home grown (and bundled) solution, both bloating extension size and performance (as reporting can't be effectively batched).

Related: https://github.com/microsoft/vscode/issues/14800

Dup of https://github.com/microsoft/vscode/issues/14800