Microsoft.DotNet.DesktopRuntime.8 dependencies not installed

Brief description of your issue
When installing WHONET.AMRIE package, Microsoft.DotNet.DesktopRuntime.8 dependency is not installed.
Steps to reproduce
winget install WHONET.AMRIE
Expected behavior
Install package & required dependency
Actual behavior
Only package is installed which does not function without dependency.
Terminal showing that dependency is not installed automatically. In next command I installed it manually when program failed to open.

Environment
PS C:\Users\drsht> winget --info
Windows Package Manager v1.7.10661
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22631.3296
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10661.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Enabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Enabled

These appear to be present int he most recent PR: https://github.com/microsoft/winget-pkgs/pull/139824/files

@stephengillie I think the real issue is that if either DotNet 6 or 7 are installed then winget does not install DotNet 8 even if it is mentioned as required dependency.
You can see that in last screenshot (I manually installed DotNet 8 because it was not installed)
PS C:\Users\drsht> winget install Microsoft. DotNet.DesktopRuntime.8
Found an existing package already installed. Trying to upgrade the installed package...
Found Microsoft .NET Windows Desktop Runtime 8.0 [Microsoft.DotNet.DesktopRuntime.8] Version 8.0.3
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
https://dotnetcli.azureedge.net/dotnet/WindowsDesktop/8.0.3/ windowsdesktop-runtime-8.0.3-win-x64. exe
Downloading
55.8 MB / 55.8 MB
Successfully verified installer hash
Starting package install...
Successfully installed
PS C: \Users\drsht>


Compare node roles correctly

Comparing roles against empty map always causes node roles to update,
which changes role order causing spec to unnecessarily change.
Resolves: #14914

LGTM

LGTM


Update gomod

This updates gomod and removes the replace directive.
Signed-off-by: Thomas Hipp<EMAIL_ADDRESS>

Glad to see this is building without the replace line now. Please can you separate the commits to show the removal of replace and general updates as there are some new imports there.

@tomponline I've split this into two parts, the first one allowing the removal of the replace directory, and the other just doing an update.

Ah, finally! That will have taken long enough for everyone to move away from that mess :)


ffmpeg-headless: enable OpenCL by default

Apparently this is commonly used for hardware-accelerated tone-mapping and it doesn't cost us much to enable.
Closure size diff:
/nix/store/m5ghr321rsxpfl001c5fdh56y9f42lpd-ffmpeg-headless-7.1-bin	 233072648
/nix/store/6gk6cll5y1g50m6z4dd384a4q5r59fgn-ffmpeg-headless-7.1-bin	 233817848
About 800K is next to nothing.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

https://github.com/NixOS/nixpkgs/pull/354952


Escrow: move assets from storage to data_structures::EscrowInfo

Within the storage block in escrow-contract/src/main.sw a previously blocked TODO is now unblocked. The assets storage variable can now be moved into EscrowInfo within escrow-contract/src/data_structures.sw and any associated refactoring can now be completed.

I think we may need to bump before this can be implemented otherwise bumping and refactoring would be mixed into 1 PR.


Fix some missing OBJ_dup failure checks.

Fix some missing OBJ_dup failure checks.
Merged from
https://boringssl.googlesource.com/boringssl/+/0ce78a757d815c0dde9ed5884229f3a5b2cb3e9c^!

It's a quick and short change.

+1

+1

Ping @richsalz, as this PR is ready to commit...
There at least 5 staging PR's label'ed "second-review", is there any particular reason ?

My $DAYJOB is taking precedence right now, others from the team now they have to step up :)

Ok, I get it. I understand now, why your commit-rate has dropped ;)

Merged!


[SMALLFIX] Configuration for disabling ufs path cache

@calvinjia

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15632/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15635/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15648/
Test PASSed.


Interoperability tests wakaama/Leshan

I think that both projects could benefit to share efforts about interoperability tests between Leshan/wakaama. (and maybe more libraries)
I didn't think too much of this but I create this ticket to centralize discussion/idea about it.
I don't know if we can define a minimalist interface which could allow us to write test one for any combination of interoperability tests :thinking:

For Californium I added such Californium - Interoperability Tests.
These test are mainly focus on several DTLS libraries (tinyDTLS, openssl, mbedtls, gnutls) and libcoap. Currently the tests are rather basic than advanced. That helped to localize some issues ahead (e.g. tinydtls ecc encoding).
I considered to extend them to the "ETSI plugtest", but I didn't find the time to do so.

In the OMA we are thinking about combining our next testfest with the IETF hackathon in March 2022.
In time for the testfest we would like to update our test specifications (see http://www.openmobilealliance.org/release/LightweightM2M/ETS/). Since we are currently reviewing the test object contributed by Simon (see https://github.com/OpenMobileAlliance/lwm2m-registry/pull/639), the test spec might get augmented by it.
I am wondering whether it would make sense to have some of the interoperability tests between Wakaama & Leshan be based on automatic tests based on the LwM2M specification.

I  had planned to refer the TestObject here too. @hannestschofenig thx for doing this. :pray:

I am wondering whether it would make sense to have some of the interoperability tests between Wakaama & Leshan be based on automatic tests based on the LwM2M specification.

Just to be sure when you say  "based on the LwM2M specification", you talk about :

the LWM2M specification in a general way
or you specifically refer to ETS - Enabler Test Specification (Interoperability)for Lightweight M2M)?

for 1. it totally makes sense.
for 2. f I didn't look at ETS recently, but it probably make sense too.
In all case, TestObject could be a good start to think about that (so review at  OpenMobileAlliance/lwm2m-registry#639 are welcomed :pray: )
Finally, I guess we will quickly come the question how this should looks technically looks like ?

@sbernard31 The scope of testing is indeed an interesting topic. The LwM2M ETS focuses on testing LwM2M functionality -- not TLS, CoAP or any other of the referenced specs. The assumption is that the IETF specs we make use provide their own test cases and the implementations of those IETF specifications already have their test strategy. In practice, this is a somewhat bold assumption. While many authors of IETF specifications (or others in the working group) write implementations of their specifications, there is in general no test description published with RFCs nor is there a structured test approach used in general. Hence, the level of testing varies hugely throughout the IETF.
If we just focus on LwM2M-specific testing, then there is the question about how those tests should be done automatically. I have been working with the IETF OAuth community and they have created automated test (see https://github.com/rohe/oidctest). I was thinking about learning something from that test framework.
I am, of course, open to other suggestions.

If we just focus on LwM2M-specific testing, then there is the question about how those tests should be done automatically. I have been working with the IETF OAuth community and they have created automated test (see https://github.com/rohe/oidctest). I was thinking about learning something from that test framework.

I looked at this very quickly, for now this is not really clear to me how this tool looks like ? or how is it supposed to be used.
(E.g. how we add test ? how you test your implementation against it ? is it a kind of interoperability check  or more spec validation test ?).
About testing LWM2M automatically, I can imagine several solutions
(:warning:  I didn't think too much of this :warning: )
1. Test API
Define a kind of common API  that client, server and bsserver should implements. (I don't know what could be the best ? CLI API ? REST API ? any more simple socket  API ? ...)
We write our LWM2M automatic tests using only the defined API.
Then implementer need to provide binary which respect the defined API.
Pros :  you can run your tests with any combination of Client / Server / Bsserver
Cons:  All project implementation need to provide binaries which implement the common API defined.
2. Testing Service
Another solution would be to try to write tests which are only based on LWM2M API. Meaning you just need to provide something which support the LWM2M spec/API. You take your implementation and just connect it to a kind of testing service.
Pros: no need to implement a test dedicated binary.
Cons :

I feel we can easily imagine a Testing Service which acts as a LWM2M server and BS server to easily test clients. But testing server or BS server this way seems more complicated to me.
You don't really test interoperability but just validity against one Testing Service.

This Zephyr PR reuse leshan-server-demo and leshan-bsserver-demo to do some interoperability tests :
https://github.com/zephyrproject-rtos/zephyr/pull/64013
Reusing demo REST API is not really recommended but what could be the right way to do that ? :thinking:


React v19 rc support

Would we include react v19rc support in the upcoming v2? https://github.com/connectrpc/connect-query-es/pull/475

We haven't tested the library with react 19, though it probably won't have any problems assuming react-query doesn't have any react 19 issues. @rinarakaki have you noticed any specific issues?

I have a problem as
# npm run build

...

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
   Collecting page data  ...Error: Failed to collect configuration for /_not-found
    at <unknown> (/path/to/my-project/node_modules/next/dist/build/utils.js:1131:23)
    at async Span.traceAsyncFn (/path/to/my-project/node_modules/next/dist/trace/trace.js:153:20) {
  [cause]: TypeError: (0 , i.createContext) is not a function
      at 47394 (/path/to/my-project/.next/server/chunks/44076.js:3:104807)
      at t (/path/to/my-project/.next/server/webpack-runtime.js:1:127)
      at 19611 (/path/to/my-project/.next/server/app/_not-found/page.js:1:3703)
      at Function.t (/path/to/my-project/.next/server/webpack-runtime.js:1:127)
      at async getLayoutOrPageModule (/path/to/my-project/node_modules/next/dist/server/lib/app-dir-module.js:33:15)
      at async collectAppPageSegments (/path/to/my-project/node_modules/next/dist/build/segment-config/app/app-segments.js:50:45)
      at async (/path/to/my-project/node_modules/next/dist/build/utils.js:1129:28)
      at async Span.traceAsyncFn (/path/to/my-project/node_modules/next/dist/trace/trace.js:153:20)
}

> Build error occurred
Error: Failed to collect page data for /_not-found
    at <unknown> (/path/to/my-project/node_modules/next/dist/build/utils.js:1234:15) {
  type: 'Error'
}

I should also try the latest rc.3 so could you resolve https://github.com/connectrpc/connect-query-es/issues/481?

I haven't had any problems so far. Also better to try the latest rc.3 so could you please resolve https://github.com/connectrpc/connect-query-es/issues/481?

Let's reopen this as "React v19 support".
I think it's possible to relax the peer dependency constraint to include the v19 rc to make it easier for users to try out.
I'm not sure TanStack Query works well with the new use though, see this blog post for context. React 19 is still a release candidate, and it's possible that there will be another one with breaking changes.

Fixed in 2.0.1

Thanks!


Understanding the export command

I'm not sure to fully understand the what the export command need as arguments to properly work:
# baremaps  export  \
--database 'jdbc:postgresql://'${HOST}':'${PORT}'/'${POSTGRES_DB}'?user='${POSTGRES_USER}'&password='${POSTGRES_PASSWORD} \
--config "${config_file}" \
--log-level=DEBUG \
--repository=./data/tiles

[INFO ] 2021-03-09 08:22:58.654 [main] Export - 56 processors available
[INFO ] 2021-03-09 08:22:58.681 [main] Export - Reading configuration
[DEBUG] 2021-03-09 08:22:58.795 [main] FileBlobStore - Read
java.io.IOException: Is a directory
...

Here is the help:
Usage: baremaps export [--enable-s3] [--mbtiles] [--batch-array-index=READER]
                       [--batch-array-size=BATCH_ARRAY_SIZE] --config=YAML
                       --database=DATABASE [--log-level=LOG_LEVEL]
                       --repository=URL [--tiles=TILES]
Export vector tiles from the database.
      --batch-array-index=READER   The index of the batch in the array.
      --batch-array-size=BATCH_ARRAY_SIZE
                                   The size of the batch array.
      --config=YAML                The YAML source configuration file.
      --database=DATABASE          The JDBC url of the Postgres database.
      --enable-s3                  Enable Amazon S3 integration.
      --log-level=LOG_LEVEL        The log level.
      --mbtiles                    The repository is in the MBTiles format.
      --repository=URL             The tile repository URL.
      --tiles=TILES                The tiles to export.

Why is the --repository expecting a URL? Can't we just simply save the tiles to the file system? How do we achieve that then?
And what exactly are the --tiles and --mbtiles flags doing? Maybe I must use one of those instead, but the --repository flag seems mandatory and if I set a path to the -mbtiles one I got:
Invalid value for option '--mbtiles': './data/tiles' is not a boolean

which seems  to suffer a tiny offset in what I understand from the documentation.
Maybe it could be nice to also print out the expected values for each args, as many bash command help pages are actually doing.
Thanks for having a look!

The command enables you to save tiles in different locally and remotely, hence the URL (s3://..., https://...).
The --mbtiles is a just a flag without parameters (boolean) that tells baremaps to create a mbtiles file instead of a directory structure.
The clarity of these parameters could be improved. If you have some ideas on how to structure these commands and parameters, let me know. I would like them to be intuitive but struggle at naming things.


All templates are blank

screenshot

@aster2709 It might be your internet issue , so try the reoload the page.

happens with me on firefox but works on chrome

happens with me in chrome too...refresh couple of times and it will be okay

Duplicate of #139 and #128
This will be fixed in the next major release. The Templates will be rendered with sandpack from codesandbox ✌


#2319 Added functionality to show a download link to Keptn Bridge CLI

This PR introduces a download-link for Keptn CLI.
In addition, I added the rel="noopener noreferrer" in the app-header component.
Other changes:

Updated deploy.yaml with the download link
Updated bridge installer manifest to also contain the download link to the github releases page based on appVersion
Moved the index api endpoint of bridge/api/ to bridge/api/bridgeInfo (this goes along with what it is called in the Angular UI)
Whatever has been done to the package.lock.json is beyond my knowledge

I tested the new feature and it works fine!


Create a new TKr for unmanaged-cluster usage in the v0.11.0 release

Once the official v0.11.0 bill of materials (BOM) is created (based on TKG 1.5.1). We should resolve the most recent (via k8s version) TKR that is compatible with that release.
You can see an example of how the TKR can be derived here:
https://github.com/vmware-tanzu/community-edition/issues/3286#issuecomment-1055541743
Based on this, the TKR we'd use would be v1.22.5+vmware.1-tkg.3.
With the above, the following needs to happen to resolve this issue:

[ ] Build a new kind image based on the k8s version in the TKR
[ ] Push the kind image to our registry (same location as existing image)
[ ] Pull the TKR down
[ ] Mutate the TKR to include the kind image we built and pushed
[ ] Push the modified TKR (to the same location as the existing TCE-unmanged TKR)
[ ] Change the default TKR in the unmanaged-cluster code to push to this TKR

@jpmcb assigning this to you for v0.11.0. Let me know if you want to hop on a zoom to go over any of these steps (these are things I've done in the past)
Thanks!

@jpmcb, your now unblocked to start this process.
You can access the BOM at projects-stg.registry.vmware.com/tkg/tkr-bom:v1.22.5_vmware.1-tkg.3-tf-v0.11.2.

Made new image and pushed with
$ ./cli/cmd/plugin/unmanaged-cluster/hack/create-kind-image.sh v1.22.5

Verified with
$ crane ls projects.registry.vmware.com/tce/kind/node
v1.20.4_vmware.1
v1.21.2_vmware.1
v1.21.5
v1.22.2
v1.22.5

Pushed a new TKR:
$ crane ls projects.registry.vmware.com/tce/tkr
sha256-2fd337282cf17357c6329f441dc970ec900145faef9e2ec6122f98fa75d529c3.imgpkg
sha256-33f63314fb72ead645715f6ac85128c0fe0fd380d14f0a79eddba3dd361b73dd.imgpkg
sha256-ac6566268e0f113a4b91bab870a34353685e886f97e248633bb2c2fcf6490dc8.imgpkg
v1.21.5
v1.21.5-1
v1.21.5-2
v1.21.5-3
v1.22.2
v1.22.5

Verified contents:
$ crane export projects.registry.vmware.com/tce/tkr:v1.22.5 - | tar xv
tkr-bom-v1.22.5.yaml

$ rg -C 3 repository
tkr-bom-v1.22.5.yaml
137-      kindNodeImage:
138-        imagePath: kind/node
139-        tag: v1.22.5
140:        repository: projects.registry.vmware.com/tce
141-  load-balancer-and-ingress-service:
142-  - version: v1.6.1+vmware.2
143-    images:


Aplha  for cutmix

for my dataset how do i  choose value of alpha  for cutmix to get best performance?

@mobassir94
It depends on the dataset type, model size, etc.
In my experience, usually alpha=1 works well for many datasets.
But when we use small datasets or small models, a small alpha (e.g., ~0.2) works better than a larger one.
So I would like to recommend that if you have computational resources to try the same experiments several times, try two or three alphas (e.g., 1.0, 0.5, 0.2) and find the best one.


Empire daemon

Still testing this, but this upgrades ECS and docker and removes empire to prep running as a daemon.

At this point, the AMI is almost identical to the official Amazon ECS AMI (granted, that one isn't ubuntu). The only real difference here is that we include logspout.
I wonder if it would be better for us to just open source an ansible role for installing logspout. Thoughts?

@ejholmes So are you suggesting that we drop default logging support in the open source AMI, and make people build their own AMI with logspout, etc if they want that feature?

Pretty much. Just not sure how much value this AMI actually provides now that almost everything is stripped out.

I think getting rid of logspout is kind of a big deal - it means that a really cool feature of empire won't exist for most users, and people aren't likely to want to build their own AMI. The good news is that the AMI should be much simpler after getting Empire off it, so I don't think maintaining it will be as big a deal

Also, if we eventually go to the logstash based logger, we'll need to install dnsmasq as well, so we'll need some level of customization anyway.  Not sure using the ECS image is going to work well for us going forward.

Yeah that's true. Although, I was thinking we could just give some example cloudconfig to run logspout for emp logs support.
Logging is such a specific thing, it's hard to keep it generic enough to warrant maintaining it.

Yeah, I would agree if it weren't a feature of Empire itself, and one that I think a lot of users would be bummed to lose.
The problem with using cloudconfig is that it's done on boot, so you're just asking for it to fail every once in a while and end up with hosts not behaving how you like.

Yeah true. If we stick with this, then we should aim to replace the Amazon ECS AMI in https://github.com/remind101/empire/blob/master/docs/cloudformation.json#L59-L63

Yeah, fair - having them be different does sort of suck, and it'd be cool to get logging working in the demo env.

@mhahn, can you take a look at this?
https://github.com/remind101/empire_ami/pull/20/files#diff-c478b6b4b86b0ea4f627fd66bf6eef25R2
Thanks @gswallow

@phobologic yea done
working as expected now

actually, @gswallow, i'm still seeing the same issue when i reboot using /var/lib. can you verify that it's not happening for you guys even when using /var/lib?

Which version of the agent are you using?  There's a known issue that was
fixed in ECS agent version 1.8.1.

On Thu, Jun 23, 2016 at 9:03 PM, Michael Hahn<EMAIL_ADDRESS>wrote:

actually, @gswallow https://github.com/gswallow, i'm still seeing the
same issue when i reboot using /var/lib. can you verify that it's not
happening for you guys even when using /var/lib?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/remind101/empire_ami/pull/26#issuecomment-228229855,
or mute the thread
https://github.com/notifications/unsubscribe/AEB7qAyq2186LbygImKCS7_Jl2R427o3ks5qOyzugaJpZM4I4yv_
.

I'm running: 1.10.0

👍

@gswallow 🙈 i hadn't swapped the ecs_agent docker image from using /var/run. thanks!

verified that reboot doesn't reregister the instance


POPUP_IFRAME - no way to close window with iframe content

when content from POPUP_IFRAME goes full window (e.g. youtube movie) nice "X" from left top corner disappearing, so there is no way to close such window and the only what we can do is to reload the page.
Would be great to force this "X" to be permanent or any click outside of the iframe window could close it.

I'm not sure I understand how you could not un-fullscreen a movie so that the toolbar appears.
Or maybe I don't see the problem because it was already fixed?


Swiper goes back on slide 1 on key press (with t comb form native)

Which OS ?
Version
Which versions are you using: OS-X High Sierra / iOS 11

react-native-swiper v1.5.*
react-native v0.55.2
https://github.com/gcanti/tcomb-form-native

Expected behaviour
When i'm writing in a Form with tcomb form native library, it should stay on the same slide.
Actual behaviour
When I'm writing in a Form with tcomb form native library, the swiper shows back the first slide on keypress (after the keyboard shows up). When I click back on the screen it goes back on the 2nd slide.
Steps to reproduce

Create a swiper with 2 or 3 slides
Put in the swiper slide 2 an input
When editing this input (on simulator) you'll see the swiper going back to slide 1.

any update on this?

Same issue. Any solution?

Here is the issue when I focus on a TextInput


Fix upgrade zipkin2

Motivation:
1、resolve parentSpanId in Zipkin version 2.1.X report is blank .
2、adapter SOFARpc span to zipkin span
3、upgrade zipkin version to 2.11.3
Result:
Fixes #57 .
If there is no issue then describe the changes introduced by this PR.

Pull Request Test Coverage Report for Build 114

7 of 8 (87.5%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.08%) to 63.484%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tracer-sofa-boot-starter/src/main/java/com/alipay/sofa/tracer/boot/zipkin/ZipkinSofaTracerSpanRemoteReporter.java
7
8
87.5%

Files with Coverage Reduction
New Missed Lines
%

tracer-core/src/main/java/com/alipay/common/tracer/core/reporter/digest/DiskReporterImpl.java
1
84.62%

tracer-core/src/main/java/com/alipay/disruptor/BlockingWaitStrategy.java
1
89.47%

tracer-core/src/main/java/com/alipay/disruptor/PhasedBackoffWaitStrategy.java
1
91.3%

Totals

Change from base Build 107:
-0.08%

Covered Lines:
2241

Relevant Lines:
3530

💛  - Coveralls


Update baseimages.md

Proposed changes
Documentation update
Replaced "you you" with "you will"

@BrandonBoone thanks for the contribution but it seems someone fixed it first #6132. I'll close this PR but I'm sure you'll have tons of other opportunities to fix the docs 🙌


[Docs] Config file for nginx

Is your feature request related to a problem? Please describe.
No. I just upgraded to version 2.x and noticed the docs do not have a sample nginx config file.
Describe the solution you'd like
Update the docs with typical nginx config file.
Describe alternatives you've considered
n/a
Additional context
Please add a sample nginx config file to the docs site, I remember it was very difficult to get it working when I first deployed portainer.
My config file from version 1.x worked as is, see below.
server {

  listen      443 ssl http2;
  listen      [::]:443 ssl http2;
  server_name portainer.example.com;

  include     conf.d/includes/foo.conf;      # include whatever extra custom config you need
  include     conf.d/includes/ssl.conf;      # include your custom SSL config, certificates etc.

  set         $upstream service_name:9000;   # use service name from docker-compose.yml file, e.g. "portainer"

  location / {
    proxy_http_version 1.1;
    proxy_set_header   Connection "";
    proxy_pass         http://$upstream;
  }

  location /api/websocket/ {
    proxy_http_version 1.1;
    proxy_set_header   Connection "upgrade";
    proxy_set_header   Upgrade $http_upgrade;
    proxy_pass         http://$upstream/api/websocket/;
  }

}

If you decide not to add it, then please close this issue. At least other users will find it.
Future reader: if you find a better config, please post yours below. Though this works for me 100% for both 1.x and 2.x.

Thank you, we will look at adding this to our documentation.
If you would like to contribute to the docs repo please feel free to check out this link .

Hi @lonix1 Thanks, will check this soon and update

This should be added to help other users.

bump

The example configuration provided in the documentation you linked uses the jwilder/nginx-proxy image which has everything you need pre-configured, and will work out of the box without needing to add a nginx config. I've pushed a slight update to the docs just now to make this a bit clearer and remove some unneeded parameters from the docker-compose.
We will consider expanding the documented examples for those that might want to use their own configs with a base nginx image.

It's your product you can do as you see fit, but I think most people don't use jwilder/nginx-proxy (which is a kind of crutch for beginners) - and in other products which use nginx, the real nginx config is always shown, which as I've posted above is quite simple.
That said, it does keep things simple for you, as there would be less support queries.


Automatic updating of imported cluster configs

We have Kubernetes clusters that use OIDC for authentication. So, anytime it refreshes the token or reauthenticates I have to either manually update the config within kube-forwarder or delete and recreate.
An example of the part of our config that changes.
  user:     auth-provider:       config:         access-token: <access_token         apiserver-id: <apiserver-id>         client-id: <clientid>         expires-in: "3599"         expires-on: "1562692749"         refresh-token: <refresh_token>         tenant-id: <guid>       name: azure
It would be nice if kube-forwarder did one of two things:

Detect the file change and automatically update the stored config.
Or, don't do a full import of the config. But instead, just create a pointer to the actual ~/.kube/config and fetch it on startup so it's always current.

Hi @dbarentine, we will read more about how OIDC works, so if I understand you correctly there is external sort of daemon that refreshes your token in kubeconfig periodically.

@lnikell Yeah essentially. It's not so much a daemon but a webook token authentication that gets called when you try to make an authenticated call via kubectl.
This causes one of two things to happen:

It forces an authentication (in our case using Microsoft's device login)
It transparently refreshes the token using the refresh_token in the configuration.

Both result in an updated .kube/config file as the access-token value will be updated. Token expiration I think is 60 minutes so our .kube/config will be updated every 60 minutes if we are actively working with kubectl.
For more information, you can see the AAD Integration here: https://docs.microsoft.com/en-us/azure/aks/concepts-identity#azure-active-directory-integration
Or the Webhook Token Authentication here: https://kubernetes.io/docs/reference/access-authn-authz/authentication/#webhook-token-authentication

@dbarentine Thank you for clarification, we will try to come up with solution for that.

Hi, @dbarentine. We have released a new version. Now it's possible to set a path to a file instead of copying its content. I hope the feature will fix your issue. Please, feel free to try the update and share feedback with us. Thanks!

Closing the issue, It should be resolved in the latest version as Alexandr mentioned.


Discussion: HtmlString has been moved from Microsoft.AspNetCore.Mvc.Rendering => Microsoft.AspNetCore.Html

We removed the HtmlString class from Mvc and renamed the HtmlEncodedString in HtmlAbstractions to HtmlString. Mvc now depends on the HtmlAbstractions HtmlString that exists under the Microsoft.AspNetCore.Html namespace.
If you were using HtmlString directly in your Razor views you will now need to add a using statement for Microsoft.AspNetCore.Html.
Announcement issue: https://github.com/aspnet/Announcements/issues/178

What's the label of this issue? RTM?

@Bartmax Correct.

Or to be more specific: 1.0.0.
The milestone is on the original issue.

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


support gitpod 1 click dev environment

Related to this post:
https://diamondapp.com/posts/a87e6e48f16bc01a2e5c34609c65e38a7b9ec0bec5d51c6ff7a271037eb58daa?tab=posts
This small addition adds easier gitpod support with pre-build images on the main branch so people can click a link and start developing. No need even to do npm init && npm start.
There is 1 addition I left out here which is to add an environment for gitpod which would also set an external lastLocalNodeV2 automatically.
Note - gitpod is a bit slow launching this evening. Usually its instant.

Love this!

I noticed the repo URL was pointing to DeSo repo rather then diamond. Fixed in #70


Patch update ghost version and add support for ingress

support for replicas
support certmanager
support for existing PVC
support for updateStrategy (RollingUpdate or Recreate)
add in support for SSL and type of azure mysql db deployment
Update notes with ingress hostname output
Update Notes with how to get wordpress database connection details
Update version of ghost to 2.1.4-debian-9
Update mariadb dep version
Align this chart version to stable/ghost version, while maintaining obsa and service catalog support
bump chart version

Do most or all of these changes come from the upstream Kubernetes charts repo? Our preference has been that the charts in this repo implement the minimal changes to adapt upstream charts for use with svc cat and OSBA. (I guess it's also worth noting that we only want a handful of such examples as well-- i.e. we have no intentions of forking all the upstream charts.)

Repo is no longer maintained and is being archived.


fix casting for int64/uint64 and long long types

Some minor fixes in docs.
needs testing. Comments?

fixes #116

Not closing it now so the typo can be merged once #124 is merged.

@wolfv do you want to rebase and merge the doc corrections ? So it can be in next release.


Show target if file could not be renamed because the target file exists.

it was a little strange to know the source file but not the target file after uploading a file.
before: "File '/tmp/php9XZSCg' could not be renamed. It already exists."
after: "File '/tmp/php9XZSCg' could not be renamed to /new/path/fileName. It already exists."
thanks in advance.

@wolxXx

"File '/tmp/php9XZSCg' could not be renamed to /new/path/fileName. It already exists."

Do you really want to show all your pathnames and also all non-public pathnames?!

yes. there is no usable information..
i want to know, what file could not be overwritten.
just knowing the name of the temporary file is useless.

any news here?

and now?

Thanks, @wolxXx


useSWRConfig mutate function doesn't cause cache revalidation when component unmounted

Bug report
Description / Observed Behavior
I'm using useSWRImmutable and at one moment I need to revalidate cache and request the data from the api. For this purpose I'm using mutate function from the hook useSWRConfig:
const { mutate } = useSWRConfig();
return <button onClick=() => mutate(REQUEST_KEY)}>revalidate</button>

I have Component that using swr with this key:
const Component = () => {
  const { data } = useSWRImmutable(REQUEST_KEY, apiRequest);
  return <>{data}</>;
};

If component was mounted at the moment mutate function was called, then data revalidating and re-requested from the api (as expected).
But if component wasn't mounted at that moment, then the data returning from the cache and doesn't re-requested from the api.
Expected Behavior
I expect that data will be re-requested from the server after revalidation regardless of whether the component, using that data,  was rendered at the time of the mutate function call or not.
Repro Steps / Code Example
CodeSandbox
Additional Context
SWR version 2.0.3.

This is expected behaviour. Once component is unmounted,  global mutate can't find a valid fetcher to revalidate the cache. You have to provide a valid fetcher here.
const { mutate } = useSWRConfig();
return <button onClick=() => mutate(REQUEST_KEY, fetcher)}>revalidate</button>

@promer94 Thanks for the answer, but when I do as you answered new problems appear:

When show === true (component mounted). The api request is executed twice on one click of the revalidate button (why?). And when the first request is executed there is no data in cache, only on the second one. It behavior is repeated on every click.
When show === false (component unmounted).  After click on the revalidate button  apiRequest is executed  despite the fact that there is not a single mounted component using swr on page. Is this behavior correct?


Feat/cl improve ci

* [GA] try to fix the cargo cache, which obviously did not work. It might be due to conflicting keys. Could not fix that, the problem is most likely due to building inside docker.

update rust-toolchain -> rust-toolchain.toml, which automatically installs the wasm32 toolchain now.
simplified CI script after the update.

Closing this for now, it became slightly outdated and the changes to improve the CI are minimal anyhow.


My faithfulness and context_recall is incorrect。

I set OPENAI_API_BASE to my own deployed model, and then there were some errors in the data evaluated by Ragas.
First, the same data produces different results each time it's evaluated. Second, there are values outside the range, like -1, in faithfulnessn.
Is there something wrong with my model?how can i locate the bug

Hi @PurpleLikeNero , the quality of results is highly dependent on the quality of the model. The default prompts in Ragas are tuned for OpenAI, you might want to tune it for your model. Are you using any opensource model?

Hi @PurpleLikeNero , the quality of results is highly(高度) dependent(依赖) on the quality of the model. The default prompts in Ragas are tuned for OpenAI, you might want to tune it for your model. Are you using any opensource model?

yes, my using opensource model named Qwen-7B

It's an interesting model. Do you use Langsmith along with ragas? In that case, it would be easier to debug and change the prompt appropriately for your model.

It's an interesting model. Do you use Langsmith along with ragas? In that case, it would be easier to debug and change the prompt appropriately(适当) for your model.

ok,i will try this later.

@PurpleLikeNero did you manage to get better results? I am facing the same issue using as model Llama-2-13B-chat-GGUF (q6) and I think the problem could be with the prompts

I had an error in ContextRecall in _score_batch where the model (non-gpt) response didn't conform to the downstream processing requirements (Attributed vs [Attributed]). I would like to use a Pydantic output parser so that the responses can be better guided. i want to put it in _score_batch immediately after responses are collected or deeper in the LangchainLLM generate code which generates those responses. Any ideas or hints? Thanks

@AbsoluteGravity we actually made some improvements to reproducibility by using forcing the evaluator LLM to output it in json. @tinomaxthayil is the one working on this. @tinomaxthayil we could also look into Pydantic Output Parser and see how it compares to json output parser.
i think json would be better though because the model will have been trained on json outputs and error messages (more likely than pydantic). would that be the case @shahules786 ?


manage-bde/changekey: hyphen instead of en dash

Description:
As reported in issue ticket #4068 (Incorrect characters used in example text.),
the en dash instead of regular hyphen in the example may not work as expected.
Thanks to Scott (@S-T-S) for reporting this specific character issue.
Proposed change:

Replace en dash with a regular hyphen (copied from the command name)

Ticket closure or reference:
Closes #4068

#sign-off

F.Y.I. : This is the only change on the page (1 single character):
- manage-bde –changekey C: E:\
+ manage-bde -changekey C: E:\

(Depending on your monitor resolution, you might want to zoom in on 200%, 300% or even 400% to see the difference between the en dash and the hyphen.)


[sw.build] Support Meson build on MacOS.

Use brew to install build tools.
build riscv toolchain from source. (Install under /opt/tools)
Meson build configuration:  ./meson_init.sh -t toolchain-darwin-x86.txt

Signed-off-by: Daniel Beitel<EMAIL_ADDRESS>

Could you please clean  up the commits? OpenTitan repo does not allow merged commits.


PDF merge protected

I have an issue with a specific pdf (Kbis of https://monidenum.fr/) on PDF Engine merge.
The pdf generated can't be open! I see that the pdf seems protected in edit. It's not possible to merge pdf protected?

@ytilotti It makes sense because the PDF engines are not able to open a protected PDF. A workaround would be to send an unprotected version of the PDF you want to merge.

I don't know if it is possible to check that a downloaded pdf file is protected.

What do you mean by snapshot? 😅

What do you mean by snapshot? 😅

A print in pdf of the pdf 😊

My first guess would be that it won't work either, but you should try and let me know 😊


feat: config for insecure server registry connection

Description
Related issues

Close #1799

Checklist

[X] I've read the guidelines for contributing to this repository.
[ ] I've added tests that prove my fix is effective or that my feature works.
[ ] I've updated the documentation with the relevant information (if needed).
[X] I've added usage information (if the PR introduces new options)
[ ] I've included a "before" and "after" example to the description (if the PR is a user interface change).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Marcel Meier seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@seekermarcel you'll have to run mage generate:docs and commit changes in order to update helm docs

@seekermarcel lgtm 🚀  thanks for the contributions


fix(s2s-utils): use slash

What:

Why:

How:

Checklist:

[ ] Documentation
[ ] Tests
[ ] Ready to be merged
[ ] Added myself to contributors table

Coverage remained the same at 100.0% when pulling 287982a234031d348e9118134940fb16ce2dc1f1 on use-posix into eba67303093072d6449cf5f0caf49858bbb57c35 on master.

Coverage remained the same at 100.0% when pulling 63c2764240a1ffb04e293dbf62b12ba39eb1131e on use-posix into eba67303093072d6449cf5f0caf49858bbb57c35 on master.

Coverage remained the same at 100.0% when pulling 0d1e4bd2e4394866bf2d34a430d1ba7b4a577f3e on use-posix into eba67303093072d6449cf5f0caf49858bbb57c35 on master.

Coverage remained the same at 100.0% when pulling 8abd0a5ff72ee7c90bbf4e309c361dad2acbf015 on use-posix into eba67303093072d6449cf5f0caf49858bbb57c35 on master.


[AutoPR sql/resource-manager] Fixed spelling mistake in SQL documentation

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4313

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/3121


Update sharing-git-repositories.md

Summary

Labels

Test Plan

Checklist

[ ] If required, I have updated the Plural documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have added a meaningful title and summary to convey the impact of this PR to a user.
[ ] I have added relevant labels to this PR to help with categorization for release notes.

this is no longer necessary


index.mjs is missing?

$ npm run start --vkversion=1.1.101

<EMAIL_ADDRESS>start /home/johnathan/nvk-examples
node --inspect --experimental-modules ./index.mjs

Debugger listening on ws://<IP_ADDRESS>:9229/2eb99809-407d-4fdf-881c-b967ae190f36
For help, see: https://nodejs.org/en/docs/inspector
(node:10869) ExperimentalWarning: The ESM module loader is experimental.
internal/modules/cjs/loader.js:798
internalBinding('util').triggerFatalException(e);
^
Error: Cannot find module /home/johnathan/nvk-examples/index.mjs
at search (internal/modules/esm/default_resolve.js:29:12)
at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:65:11)
at Loader.resolve (internal/modules/esm/loader.js:58:33)
at Loader.getModuleJob (internal/modules/esm/loader.js:113:40)
at Loader.import (internal/modules/esm/loader.js:99:28)
at asyncESM.loaderPromise.then (internal/modules/cjs/loader.js:795:27)
at processTicksAndRejections (internal/process/next_tick.js:81:5)
at process.runNextTicks [as _tickCallback] (internal/process/next_tick.js:51:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:804:11)
at internal/main/run_main_module.js:21:11
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: node --inspect --experimental-modules ./index.mjs
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/johnathan/.npm/_logs/2019-03-05T11_29_36_664Z-debug.log

As the README states, you have to navigate into an example and run npm run start.. from there, not from the root folder

Yeah whoops sorry eventually figured it out ;)
On Wednesday, March 6, 2019, Felix Maier<EMAIL_ADDRESS>wrote:

Closed #1 https://github.com/maierfelix/nvk-examples/issues/1.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maierfelix/nvk-examples/issues/1#event-2185374944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHYixKy_pe0m-tY8-GXrD6Ep8L-68Gzks5vUCs3gaJpZM4beZd6
.


Implement hashCode for QuadEdgePartner

Fix #62

I have a question regarding efficient hash codes. I'm not all that familiar with the inner workings of HashMap.
As implemented in the pull request, the hashCode will always be an integer in the range 77+0 to 77+2*N where N is the number of edge-pairs in the TIN.
Is it necessary to use some kind of hashing scheme to make sure that their values are distributed over the range of integers?  I seem to recall that the basic idea of a hash is to "randomize" a key so that it isn't monotonically increasing for a data set.
On the other hand, I note that as implemented, the hashCodes have the advantage of being always unique.

To my knowledge distribution over a range doesn't matter. What matters is deriving unique hashcodes for objects that may share many fields in common. This is why hashing schemes generally blow up and scatter the hash values for multiple fields to minimise collision with similar instances.
Since IDs of quadedges (for a given graph) are unique, they make fines hashcodes, even though they are monotonic and tightly packed.

Commit merged.  Thank you for your contribution.


Is device_apps plugin deprecated?

When I try to use it my project, it is showing this plugin is deprecated. So is there any alternate method?

No the plug-in is still supported
Don't worry about the warnings
Le ven. 3 juil. 2020 à 04:19, Sankalp jadhav<EMAIL_ADDRESS>a
écrit :

When I try to use it my project, it is showing this plugin is deprecated.
So is there any alternate method?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/g123k/flutter_plugin_device_apps/issues/42, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB4INTCIAO4OCDHOXJ22XTRZU54PANCNFSM4OPM325Q
.

Thank you for the response!


Add dimension sliders

Description
This pull request introduces a nearly feature complete dimension model and view.
Moreover, it showcases a more modular design for the model and view hierarchies
that minimises arbitrary cross-talk between classes.
Philosophy
Here are the main design patterns that are illustrated in this PR:

First, all classes/files have a corresponding test file that is written as the code of
the class is written. This ensures that the class is testable in isolation. The less dependencies
the test file has to other files and classes, the better.
Models can be instantiated in isolation. For example, the dimension model can be now instantiated without a viewer, a qt view, etc...
Models do not have any dependencies on UI classes (Qt). Views take the corresponding model as the one and unique parameter of their constructor and register listeners so as to be notified about any events in the model, so that the view can change if the model is externally changed. Since the view knows about the model, it can trivially change the model when it itself changes.
Models (also true for views) are organised in a tree. A model such as the napari viewer knows about the dimension model, the layers list, etc... but, these child objects must not know about their parent or siblings. To solve this apparent challenge, the parent registers listeners to the child components, so that these child components can notify their parent of a change. A parent can directly modify a child, but a child notifies a parent via listeners (same machinery that a view uses to listen to a model).
When two siblings (e.g. layers list and dims) need to talk to each other, they do not do this directly, because they don't have a reference to the parent. Instead, they exchange events through the intermediary of the parent. For example: when a new layer is added, the layers model notifies the parent (viewer), which then applies the necessary changes to the dimension model. In practice, a method _on_change_layers is executed as part of the listener to the layers list, and in turn, this method directly changes the dimensions model.
Not every thread can directly touch Qt objects (for example, setting the state of a button). This is a recipe for very difficult to debug stochastic crashes. Only the Qt event dispatch thread should be allowed to touch any Qt object. If another thread tries to touch UI objects, it might be fine 99% of the time, but sometimes updates will fail or worse the whole thing will crash and burn. Hence, Qt signals must be used to translate any event coming from the model so as to make sure that it really runs on the Qt thread. In many situations the event is triggered from the UI and hence runs on the Qt thread, but in other cases (jupyter notebook, animation thread, etc...) it won't be the case.

Type of change

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

How has this been tested?
Tests have been written for all new classes
Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[NA] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

Hello @royerloic! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file napari/_qt/range_slider/range_slider.py:

Line 195:38: E231 missing whitespace after ','
Line 197:13: E265 block comment should start with '# '
Line 206:16: E111 indentation is not a multiple of four
Line 207:16: E111 indentation is not a multiple of four
Line 209:16: E111 indentation is not a multiple of four
Line 210:16: E111 indentation is not a multiple of four
Line 213:13: E265 block comment should start with '# '
Line 228:30: E221 multiple spaces before operator

In the file napari/_qt/range_slider/tests/range_slider_tests.py:

Line 27:5: E303 too many blank lines (2)
Line 28:5: E301 expected 1 blank line, found 0
Line 32:5: E303 too many blank lines (2)
Line 37:1: W391 blank line at end of file

In the file napari/components/_dims/dims.py:

Line 17:80: E501 line too long (97 > 79 characters)
Line 69:19: E225 missing whitespace around operator
Line 203:80: E501 line too long (83 > 79 characters)
Line 207:80: E501 line too long (82 > 79 characters)
Line 224:80: E501 line too long (83 > 79 characters)
Line 230:80: E501 line too long (90 > 79 characters)
Line 242:80: E501 line too long (104 > 79 characters)
Line 249:51: E225 missing whitespace around operator
Line 250:46: E231 missing whitespace after ','
Line 262:80: E501 line too long (88 > 79 characters)
Line 269:80: E501 line too long (88 > 79 characters)
Line 276:1: W391 blank line at end of file

In the file napari/components/_dims/qtdims.py:

Line 22:5: E303 too many blank lines (2)
Line 22:42: E251 unexpected spaces around keyword / parameter equals
Line 22:44: E251 unexpected spaces around keyword / parameter equals
Line 32:9: E303 too many blank lines (2)
Line 45:9: E265 block comment should start with '# '
Line 49:9: E303 too many blank lines (2)
Line 49:80: E501 line too long (85 > 79 characters)
Line 51:80: E501 line too long (80 > 79 characters)
Line 61:40: E225 missing whitespace around operator
Line 67:9: E303 too many blank lines (2)
Line 67:80: E501 line too long (85 > 79 characters)
Line 68:80: E501 line too long (92 > 79 characters)
Line 69:80: E501 line too long (86 > 79 characters)
Line 72:9: E306 expected 1 blank line before a nested definition, found 0
Line 76:80: E501 line too long (83 > 79 characters)
Line 84:80: E501 line too long (86 > 79 characters)
Line 105:24: E225 missing whitespace around operator
Line 113:24: E225 missing whitespace around operator
Line 116:23: E225 missing whitespace around operator
Line 119:25: E225 missing whitespace around operator
Line 123:80: E501 line too long (84 > 79 characters)
Line 123:83: E203 whitespace before ':'
Line 151:32: E225 missing whitespace around operator
Line 153:13: E265 block comment should start with '# '
Line 156:13: E265 block comment should start with '# '
Line 157:13: E265 block comment should start with '# '
Line 159:13: E265 block comment should start with '# '
Line 159:80: E501 line too long (84 > 79 characters)
Line 190:23: E231 missing whitespace after ','
Line 190:27: E231 missing whitespace after ','
Line 192:26: E231 missing whitespace after ','
Line 195:9: E303 too many blank lines (2)
Line 199:38: E225 missing whitespace around operator
Line 228:80: E501 line too long (88 > 79 characters)

In the file napari/components/_dims/tests/dims_tests.py:

Line 12:5: E303 too many blank lines (2)
Line 12:25: E231 missing whitespace after ','
Line 12:30: E231 missing whitespace after ','
Line 18:34: E231 missing whitespace after ','
Line 18:39: E231 missing whitespace after ','
Line 19:34: E231 missing whitespace after ','
Line 19:39: E231 missing whitespace after ','
Line 20:34: E231 missing whitespace after ','
Line 20:39: E231 missing whitespace after ','
Line 21:31: E231 missing whitespace after ','
Line 21:36: E231 missing whitespace after ','
Line 23:1: E302 expected 2 blank lines, found 1
Line 71:29: E711 comparison to None should be 'if cond is None:'
Line 72:29: E711 comparison to None should be 'if cond is None:'
Line 73:29: E711 comparison to None should be 'if cond is None:'
Line 99:1: E303 too many blank lines (3)
Line 112:28: E231 missing whitespace after ','
Line 113:28: E231 missing whitespace after ','
Line 120:23: E711 comparison to None should be 'if cond is None:'
Line 124:25: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 125:25: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 126:25: E712 comparison to True should be 'if cond is True:' or 'if cond:'
Line 127:25: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 129:1: E302 expected 2 blank lines, found 1
Line 143:23: E225 missing whitespace around operator
Line 144:25: E225 missing whitespace around operator
Line 146:1: E302 expected 2 blank lines, found 1
Line 156:29: E225 missing whitespace around operator
Line 161:80: E501 line too long (81 > 79 characters)
Line 164:31: E225 missing whitespace around operator
Line 173:34: E225 missing whitespace around operator
Line 179:21: E231 missing whitespace after ','
Line 185:1: W391 blank line at end of file

In the file napari/components/_dims/tests/qtdims_tests.py:

Line 18:21: E231 missing whitespace after ','
Line 19:21: E231 missing whitespace after ','
Line 25:80: E501 line too long (102 > 79 characters)
Line 45:5: E303 too many blank lines (2)
Line 45:80: E501 line too long (85 > 79 characters)
Line 46:5: E301 expected 1 blank line, found 0
Line 50:13: E265 block comment should start with '# '
Line 51:13: E265 block comment should start with '# '
Line 58:17: E225 missing whitespace around operator
Line 65:5: E303 too many blank lines (2)
Line 66:5: E265 block comment should start with '# '
Line 69:1: W391 blank line at end of file

In the file napari/components/_viewer/qtviewer.py:

Line 102:5: E303 too many blank lines (2)

In the file napari/components/_viewer/tests/qtviewer_tests.py:

Line 2:80: E501 line too long (86 > 79 characters)
Line 13:1: E302 expected 2 blank lines, found 1
Line 15:38: E251 unexpected spaces around keyword / parameter equals
Line 15:40: E251 unexpected spaces around keyword / parameter equals
Line 32:11: E221 multiple spaces before operator
Line 50:5: E265 block comment should start with '# '
Line 50:5: E303 too many blank lines (3)
Line 53:5: E265 block comment should start with '# '

In the file napari/components/_viewer/tests/viewer_tests.py:

Line 11:5: E265 block comment should start with '# '
Line 11:80: E501 line too long (115 > 79 characters)
Line 13:11: E221 multiple spaces before operator
Line 28:47: E231 missing whitespace after ','

In the file napari/components/_viewer/viewer.py:

Line 25:9: E303 too many blank lines (2)
Line 38:9: E266 too many leading '#' for block comment
Line 39:9: E266 too many leading '#' for block comment
Line 169:5: E303 too many blank lines (2)
Line 179:23: E201 whitespace after '['
Line 179:30: E231 missing whitespace after ','
Line 179:33: E231 missing whitespace after ','
Line 179:39: E231 missing whitespace after ','
Line 179:49: E231 missing whitespace after ','
Line 179:60: E231 missing whitespace after ','
Line 179:62: E231 missing whitespace after ','
Line 179:65: E231 missing whitespace after ','
Line 179:68: E231 missing whitespace after ','
Line 179:70: E231 missing whitespace after ','
Line 179:80: E501 line too long (100 > 79 characters)
Line 179:87: E231 missing whitespace after ','

In the file napari/components/component.py:

Line 9:5: E303 too many blank lines (2)

In the file napari/components/tests/component_tests.py:

Line 5:1: E302 expected 2 blank lines, found 1
Line 23:1: W391 blank line at end of file

In the file napari/layers/_base_layer/model.py:

Line 129:9: E265 block comment should start with '# '
Line 131:19: E231 missing whitespace after ','
Line 131:23: E231 missing whitespace after ','

In the file napari/layers/_image_layer/model.py:

Line 176:13: E265 block comment should start with '# '
Line 397:31: E221 multiple spaces before operator

Still working on the integration into the viewer and making sure that slicing and projections still work well... There are still some bugs. Projection already works, sort of.

test_napari_application.py does not pass
python napari/app/tests/test_napari_application.py
Traceback (most recent call last):
  File "napari/app/tests/test_napari_application.py", line 4, in <module>
    from napari_application import NapariApplication
ModuleNotFoundError: No module named 'napari_application'

@royerloic - I've finally had a chance to look through this. I really like the high level principles you lay out in 1. - 6. and am glad to see them implemented for the Dims object in this PR. There is still a lot of work to be done though to integrate these changes with the rest of the viewer. (Right now none of our main examples run, and some of the tests you created also don't run). This PR also adds some new capabilities around slicing / cropping / range sliders to the viewer. I found how these are currently working slightly confusing (i.e. the two sliders for cropping) and think we should wait to implement all that stuff until we do the refactoring and integration laid out in your high level goals. A reason is that I think it will take a while to get the dims sliders max projection / cropping / slicing etc. the way that we like it (including UI elements) and we shouldn't hold up all development until that is done.
I propose that we do a minimum amount of this PR to ensure that we preserve all functionality from before but now using the refactor approach (and the new range slider, but set to be only single slider capability). Once this is merged we can then in parallel on refactoring and testing the rest of the Qt stuff (like the layer list etc.) and on implementing the max projection / cropping / slicing. How does that sound to you?

@sofroniewn your plan sounds good to me. Assuming @royerloic doesn't veto our intervention, we should take this PR, using only single sliders, get it runnable and mergeable, and merge it. The projection modes can definitely come later.

I am fine with it, we can have a flag in the view that deactivates the 'expandability' of the slider.
I would nevertheless avoid modifying the Dims model though, as it should be possible to minimally change other layers to receive the 'slicing' info from the new Dims model... The image layer shows the minimal changes required to make this happen.

I see my work on the Dims more from a didactic perspective, as an example of how the rest of the UI could be designed, as long as these new principles are applied, there should be no issue in easing a path to integrate the new dims code... :-)

@sofroniewn @kne42 What about we work on fixing all this together on thursday after the meeting?

Ok - I have fixed what I think is the last major bug around getting the dims working in the new @jni approved order! There are still some minor bugs that I know of that I need to fix, so this is not ready for review yet, and there are lots of pep8 / style / docstring issues that need to be fixed before it is worth looking at again, but I at least now see a path towards getting this done

This PR is now ready for some review. It achieves two things - it seperates the model and the view for the dims object as dims and qtdims - and - it reorders the displayed dimensions so that the last two dimensions are the ones displayed. It also switches the dims object to use the range_slider. The dims object has some machinery for supporting a range mode and a point mode, but currently only the point mode is enabled. Similarly only having the last two dimensions as the displayed dimensions is supported. Hopefully adding these features in the future will be easier after this refactor.
For people reviewing the PR I would focus on the dims.py and qtdims.py files as these are the important ones here. We should make sure we like them. A lot of the other changes in viewer and the layers themselves are more minor and to accommodate the new dims object. They will be changed and updated themselves as the refactor continues, but that will be new PRs.
Finally this PR adds some tests for the rangeslider, the dims, qtdims, viewer and qtviewer. These probably need some editing / cleanup and currently are not being run as part of the actual testing suite (I'm not even sure they are up to date now, but will look at them a little myself too). At this point I trust the code more than I trust those tests as all the examples run.
I'd also keep a look up for bugs in the interactivity, this PR affected a lot of stuff and there could still be some that slipped through!

Fantastic @sofroniewn !
Thanks for taking care of this.
I will review when back from week end!

I have made some changes requested by the other reviewers, including reverting to the model and view filenaming like we had before and removing some of the changes in this PR that had nothing to do with the Dims model.
I have also cleaned up the testing file for the Dims model and removed the testing of the view files as they weren't really tests but more examples. We should probably revisit our testing of view files in future PRs and get the tests to run automatically like we test our main examples.
If @royerloic and @jni can give this the ok then I'd like to merge it, as I am worried if we wait too long it will just keep backing everything else up

@jni this is ready for a final review and then merge. You might want to try some of the examples, move some of the sliders around etc one last time to check if there are any bugs. I changed to adding / trimming ordering that you flagged above and simplified some stuff inside the ndim setter. It should all be good to go, so feel free to merge when you are ready. I'll be glad when this is in and we can press on with more refactoring etc

There's at least one more issue: in examples/annotate-2d.py, if I click on the top-right corner, that coordinate should be close to [0, 512] (0th row, 512th column). It is instead close to [512, 0].
This problem is also present in the status bar. This is a problem with the markers layer only! In the image layer, in examples/add_image.py, the coordinates are correct. Needless to say, the coordinates in the markers and image layer should correspond to each other!
Another problem: I am unable to move the layers with drag and drop to the start or end of the list (at least in annotate-2d.py).

I take it back: layer reordering is broken everywhere, not just at the edges. Using examples/layers.py, no reordering from the UI can happen.

examples/nD_markers.py makes the coordinate problem more explicit: the final dimension only counts up to 10 and then gets clipped. This happens to be the max value of the 0th dimension. So somewhere in markers, all the dims are still inverted.

The shapes coordinates are also inverted: if I delete all the shapes but one, and then move the remaining shape (in this case the ellipse) to the top right corner (0th row, 500th column), I get the following out:
your shapes are at:
[array([[474.53997229,  -2.17129747],
       [515.65247683,  29.19340657],
       [496.22172921,  54.53785999],
       [455.10922467,  23.17315594]])]

@jni I have switch the dim ordering on the vectors / markers / shapes layer so that they match the your expected dimensions ordering, but it does make some things weird internally because vispy and things like the svg spec expect a (x, y) ordering for 2D objects, not (y, x).

The layers reordering also works fine now, was unclear to me what was broken before. Make sure you don't have all the layers selected when you are trying to reorder them

Finally though I have identified one more bug, when adding a 3D image to a bunch of 2D images a new dimensions slider no longer appears. I will work on fixing that now

Ok this is ready for re-review and testing by @jni. I had to make one change to some of the iterators to allow for layers with more dimensions to be added to a viewer. It should all work now

@sofroniewn the sliders don't seem to be working correctly for me on examples/dask_nD_image.py... Both appear to have way more stops than they should, and they only take values 0 and 1...

Ah, nothing to do with dask, examples/nD_image.py suffers from the same problem.

I think it has something to do with the initialization of the dims object, since it appears to vary from 0 to 1 with some 128 or 256 levels.

@jni fixed that issue - just popped in on the last commit and didn't appear in the nD_markers.py which I was testing with!! We should we all good to go now :-)

@sofroniewn I'm still getting the problem on d532f7a ... And I see no reason why it would fix the problem!

@jni if I load examples/nD_images.py I'm now able to scroll through both axes properly - there are 128 acceptable values for the top slider and 10 acceptable values for the bottom slider. If I do print(viewer.dims) I now get
[(0, 10, 1), (0, 128, 1), (0, 128, 1), (0, 128, 1)]~~[0.0, 0.0, 0.0, 0.0]~~[(0.3, 0.7), (0.3, 0.7), (0.3, 0.7), (0.3, 0.7)]~~[<DimsMode.POINT: 0>, <DimsMode.POINT: 0>, <DimsMode.POINT: 0>, <DimsMode.POINT: 0>]~~[False, False, True, True]

which is correct.
Before making the change in this PR if I did print(viewer.dims) I now got
[(0.0, 1.0, 0.01), (0.0, 1.0, 0.01), (0, 10, 1), (0, 128, 1), (0, 128, 1), (0, 128, 1)]~~[0.0, 0.0, 0.0, 0.0]~~[(0.3, 0.7), (0.3, 0.7), (0.3, 0.7), (0.3, 0.7)]~~[<DimsMode.POINT: 0>, <DimsMode.POINT: 0>, <DimsMode.POINT: 0>, <DimsMode.POINT: 0>]~~[False, False, True, True]

which was causing the error. You can see there were 2 extra items in that first list that should not have been there. Changing the order of
self.ndim = len(range)
self._range = range

fixes that as it prevents extra values getting inserted into the list.
Can you please look again and let me know more specifically what is still not working and the results of print(viewer.dims). Thanks!

@sofroniewn my bad! There was some weird caching going on — even deleting the branch and pulling again didn't work, I had to uninstall and reinstall napari.
Anyway! All good now! Here we go!!!!

Great!


android build doesn't  Sync  in android studio

axmol version: latest clone
devices test on:
developing environments

NDK version: r23c
Xcode version: 14.2+
Visual Studio:

VS version: 2022 (17.9+)
MSVC version: 19.39+
Windows SDK version: 10.0.22621.0+

cmake version:
android studio : 2023.2.1
Steps to Reproduce:

create a sample project and open proj.android  in android studio Gradle sync error

same project works in command Line for  Android: axmol build -p android -a arm64 but not in android studio  can anyone help with this

The android studio runs on macos or windows?

build sync success and built app successfully thank you
what was the issue ?

The macos launchpad not share env var AX_ROOT in ~/.zshrc , need use launchctl set env


Integrate Mapbox uploader for outputs

blocked by https://github.com/mapbox/mapbox-cli-py/issues/67

https://github.com/wboykinm/tribes/commit/ba681bdcf7408346d2a3128e48b68f6488c56c54


Ability to set response headers / cookies after yield

It feels inconsistent that we can change headers / cookies in dependencies before yield, but can't do this afterwords. E.g. in the following example only before=yield cookie will be set:
def set_cookie(response: Response):
    response.set_cookie("before", "yield")
    yield
    response.set_cookie("after", "yield")

@app.get("/")
def index(_=Depends(set_cookie)):
    return {}

The possibility of setting them "after request" would eliminate a need for middlewares in cases when their order is not important.
Alternatively we can at least throw an exception to make the behavior explicit.

How would that work? Context manager dependencies are only closed once the response has been fully rendered, I believe, at which point it's already far too late to add headers. Is there any reason why you wouldn't be able to set both headers before yielding?

Is there any reason why you wouldn't be able to set both headers before yielding?

I found it when I tried to automatically save cookie-based session.

As @sm-Fifteen says, the section after yield in dependencies is executed after the response has been sent. In fact, after the background tasks have been executed. This is intentional, that's the main point of dependencies with yield, to be able to run code after the response is sent.
If you want to set cookies no matter what else happens in the path operation function, you can do it in the normal dependency or in the part before yield.
Those headers are combined with any other headers you set in your dependencies or path operation and then are returned together.

Right, and if feels solid until you have Response as a dependency. Anyway if this stuff about background tasks is intentional it will involve even more inconsistency to do any exception for dependencies with Response. Thanks, for your answers, guys :)

I'm guessing @imbolc were talking codes something like this.
It looks quite useful.
app = FastAPI()

def get_session_store(
    response: Response,
    FASTAPI_SESSION: Optional[str] = Cookie(None),
):
    store = {}
    if FASTAPI_SESSION is not None:
        store = json.loads(FASTAPI_SESSION)
    yield store
    response.set_cookie(key='FASTAPI_SESSION', value=json.dumps(store))

@app.get
def index(store: dict = Depends(get_session_store)):
    store['n'] = 42 # store will be automatically saved in cookie

@app.get
def clear(store: dict = Depends(get_session_store)):
    store.clear() # will work
    store = {'n': 42} # will not work

Is it possible to do something like this?
Anyway, Thank you very much for the nice framework!


Log in broken on Safari

Users don't get redirected to their Portal on Safari when trying to log in with Blockstack.
Underlying cause: bug in blockstack 0.2.22 blockstack/blockstack.js#205

This was fixed.


How to add numbers into sms24.me

Hi Team,
Atlas that I represent is a telecom operator able to supply you numbers in several EU countries such as France, NL, UK, Sweden, ...
how can we upload them into your system?
contact<EMAIL_ADDRESS>

We are not affiliated with sms24.me. And this project aims to provide people a list of disposable phone numbers for spam protection reasons.

we could help people by providing disposable phone numbers, for privacy and protection reasons.
let me know if you're interested in this project.

Sounds like the opposite of what this project is about. But my employer may be interested. Send an email to<EMAIL_ADDRESS>

I've tried to reach you out but in vain. could you pass the info and ask your employer to contact me by email?
<EMAIL_ADDRESS>Thank you!


[BUG] Failed to load Huggingface native library.

Describe the bug

EmbeddingModel embeddingModel = new BgeSmallZhV15EmbeddingModel();
An error occurs when executing the above code
Log and Stack trace
11:14:42.733 [main] INFO ai.djl.util.Platform -- Found matching platform from: jar:file:/Users/jackie/.m2/repository/ai/djl/huggingface/tokenizers/0.30.0/tokenizers-0.30.0.jar!/native/lib/tokenizers.properties
11:14:42.740 [main] INFO ai.djl.huggingface.tokenizers.jni.LibUtils -- library not found in classpath: native/lib/osx-x86_64/cpu/libtokenizers.dylib
Exception in thread "main" java.lang.ExceptionInInitializerError
	at com.jiuwei.tcmsp.thridapi.digitalhuman.service.impl.handler.InputEmbeddingHandler.main(InputEmbeddingHandler.java:108)
Caused by: java.lang.RuntimeException: ai.djl.engine.EngineException: Failed to load Huggingface native library.
	at dev.langchain4j.model.embedding.onnx.OnnxBertBiEncoder.<init>(OnnxBertBiEncoder.java:41)
	at dev.langchain4j.model.embedding.onnx.AbstractInProcessEmbeddingModel.loadFromJar(AbstractInProcessEmbeddingModel.java:48)
	at dev.langchain4j.model.embedding.onnx.bgesmallzhv15.BgeSmallZhV15EmbeddingModel.<clinit>(BgeSmallZhV15EmbeddingModel.java:31)
	... 1 more
Caused by: ai.djl.engine.EngineException: Failed to load Huggingface native library.
	at ai.djl.huggingface.tokenizers.jni.LibUtils.<clinit>(LibUtils.java:56)
	at ai.djl.huggingface.tokenizers.HuggingFaceTokenizer.newInstance(HuggingFaceTokenizer.java:185)
	at dev.langchain4j.model.embedding.onnx.OnnxBertBiEncoder.<init>(OnnxBertBiEncoder.java:38)
	... 3 more
Caused by: ai.djl.engine.EngineException: Unexpected flavor: cpu
	at ai.djl.huggingface.tokenizers.jni.LibUtils.copyJniLibrary(LibUtils.java:195)
	at ai.djl.huggingface.tokenizers.jni.LibUtils.loadLibrary(LibUtils.java:82)
	at ai.djl.huggingface.tokenizers.jni.LibUtils.<clinit>(LibUtils.java:54)
	... 5 more

To Reproduce

public static void main(String[] args) {

        EmbeddingStore<TextSegment> embeddingStore = new InMemoryEmbeddingStore<>();
        EmbeddingModel embeddingModel = new BgeSmallZhV15EmbeddingModel();

        // refresh(embeddingModel, embeddingStore);

        Embedding queryEmbedding = embeddingModel.embed("hello").content();
        EmbeddingSearchResult<TextSegment> relevant = embeddingStore.search(
                EmbeddingSearchRequest.builder()
                        .queryEmbedding(queryEmbedding)
                        .maxResults(10)
                        .build());
        EmbeddingMatch<TextSegment> embeddingMatch = relevant.matches().get(0);

        System.out.println(embeddingMatch.score()); // 0.8138435
        System.out.println(embeddingMatch.embedded().text()); // I like football.
    }

Expected behavior

Please complete the following information:

LangChain4j version: 0.36.0
LLM(s) used: BgeSmallZhV15EmbeddingModel
Java version: 17
Spring Boot version (if applicable): 3.2.3

Additional context

Same problem here. Works fine with version 0.34.0.

Thanks for reporting!
I would really appreciate any help with this issue (investigation/fixing).
Could someone please take care of it? 🙏

@langchain4j I will take a look

It seems that this version of the package doesn't have this directory.
ai/djl/huggingface/tokenizers/0.30.0/tokenizers-0.30.0.jar!/native/lib/osx-x86_64
<dependency>
      <groupId>ai.djl.huggingface</groupId>
      <artifactId>tokenizers</artifactId>
      <version>${ai.djl.version}</version>
  </dependency>

Is it not supported? @langchain4j @omarmahamid

Same problem here, had to downgrade the LangChain4j version

@stardyun
I assume u are mac user with intel processor ?
I can see that djl change the build between the versions
can you add this in your dependency and make sure every thing will work fine ?
        <dependency>
            <groupId>ai.djl.huggingface</groupId>
            <artifactId>tokenizers</artifactId>
            <version>0.28.0</version>
        </dependency>

@langchain4j
upgrading to 0.30 djl tokenizer can block the mac intel users
https://github.com/langchain4j/langchain4j-embeddings/commit/88de236910d7584939115cc24f2fbd3e0300d56d
so I will try seeing why they block this , and may open an issue for them

@stardyun
From djl maintainer
https://github.com/deepjavalibrary/djl/issues/3488
macos intel is no longer supported from djl version 0.29.0

@stardyun
From djl maintainer
deepjavalibrary/djl#3488
macos intel is no longer supported from djl version 0.29.0

If so, is that the only option to downgrade the version? Or will compatibility processing be considered at the LC4J framework level ?

@misselvexu unfortunately we do not have capacity to support this on our side

djl commit removing support of mac intel.
deepjavalibrary/djl@d2b854e
@langchain4j this should be a release note to langchain4j-embedding versions

OK, Thank U

maven Management djl version 0.28.0 is supported
<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>ai.djl.huggingface</groupId>
            <artifactId>tokenizers</artifactId>
            <version>0.28.0</version>
        </dependency>
    </dependencies>
</dependencyManagement>


Add this list to the Unified list

d1wix2gc2cgqis.cloudfront.net appeared in NoScript today so I Googled it. It turned up in a trackers blocklist hosted here, so I permanently blocked it.
The url is not listed in the Unified hosts + fakenews + gambling + porn list I use. Since the Unified list is an amalgamation of several other lists but none of them included that tracker, there are probably countless others on that list that are missing from the Unified list.
Therefore the ShadowWhisperer list should be included in the merged Unified list.

Hi @GitTheHellOutaHere thank you for this.
The list you recommend has only been active since August 10th, barely three weeks.
Nonetheless, here is the breakdown, comparing it to our base list using ghosts.
 ghosts -c https://raw.githubusercontent.com/ShadowWhisperer/BlockLists/master/Lists/Tracking
----------------------------------------
Base hosts file summary:
----------------------------------------
Location: https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
Domains: 90,152
Bytes: 2.8 MB
----------------------------------------
----------------------------------------
Compared hosts file summary:
----------------------------------------
Location: https://raw.githubusercontent.com/ShadowWhisperer/BlockLists/master/Lists/Tracking
Domains: 34,726
Bytes: 733 kB
----------------------------------------
Intersection: 3,003 domains

Therefore this inclusion would add (34,726 - 3,003) 31,723 domains to oir base list.  This seems suspect to me.  Out of nowhere, this random list would increase our base list size  by 34%.
Looking at the TLD breakdown of this list we get (see below).  This seems very euro-centric in terms of TLD.  I don't sense that we're weak in european TLD.  I wonder what this curator knows that all our seasoned reliable curators don't?
$ ghosts -tld -m https://raw.githubusercontent.com/ShadowWhisperer/BlockLists/master/Lists/Tracking
----------------------------------------
Base hosts file summary:
----------------------------------------
Location: https://raw.githubusercontent.com/ShadowWhisperer/BlockLists/master/Lists/Tracking
Domains: 34,726
Bytes: 733 kB
TLD tally:
   com: 13,590
   de: 6,178
   net: 2,118
   fi: 1,320
   fr: 970
   org: 969
   ch: 907
   jp: 695
   nl: 578
   io: 573
   eu: 495
   at: 454
   uk: 367
   ca: 280
   cn: 277
   pl: 272
   it: 272
   cz: 252
   co: 195
   be: 188
   au: 173
   me: 166
   se: 134
   ru: 112
   es: 107
   dk: 100
   cloud: 95
   tv: 91
   br: 73
   ro: 65
   dev: 65
   ai: 64
   in: 63
   pt: 60
   us: 57
   no: 56
   gr: 49
   app: 48
   ir: 43
   tech: 42
   ovh: 41
   hu: 41
   cc: 39
   digital: 38
   info: 38
   nz: 38
   sk: 37
   id: 33
   si: 32
   one: 30
   lu: 29
   media: 29
   za: 29
   ua: 28
   bg: 26
   network: 26
   mx: 25
   ie: 25
   vn: 25
   li: 25
   nu: 24
   tw: 24
   ee: 23
   is: 22
   pw: 21
   kr: 21
   systems: 21
   solutions: 20
   edu: 19
   ly: 18
   cl: 18
   ar: 18
   shop: 18
   hk: 16
   lv: 16
   to: 16
   name: 16
   rocks: 16
   il: 15
   gov: 15
   lt: 15
   hr: 15
   biz: 15
   im: 15
   tr: 14
   xyz: 14
   ws: 14
   al: 14
   rs: 13
   events: 13
   tools: 13
   pro: 12
   asia: 12
   la: 12
   coop: 12
   link: 12
   services: 11
   re: 11
   group: 11
   live: 11
   studio: 10
   berlin: 10
   icu: 10
   fm: 10
   tk: 10
   design: 10
   st: 9
   site: 9
   sh: 9
   software: 9
   agency: 9
   consulting: 8
   sg: 8
   by: 8
   world: 8
   team: 8
   tokyo: 8
   land: 8
   gg: 8
   news: 8
   ma: 8
   cat: 7
   nrw: 7
   ag: 7
   bzh: 7
   mobi: 7
   ms: 7
   th: 7
   wiki: 7
   host: 7
   email: 6
   pe: 6
   ph: 6
   swiss: 6
   works: 6
   guru: 6
   eus: 6
   company: 6
   life: 6
   blue: 6
   hosting: 6
   my: 6
   codes: 5
   pm: 5
   gmbh: 5
   mc: 5
   bz: 5
   so: 5
   kz: 5
   ke: 5
   store: 5
   photo: 5
   ae: 5
   social: 5
   cx: 5
   ac: 5
   press: 5
   ba: 5
   mk: 4
   marketing: 4
   hamburg: 4
   as: 4
   fan: 4
   travel: 4
   lol: 4
   ad: 4
   tn: 4
   zone: 4
   md: 4
   tirol: 4
   business: 4
   space: 4
   sa: 4
   pub: 4
   su: 4
   law: 4
   technology: 4
   art: 3
   community: 3
   uz: 3
   watch: 3
   ink: 3
   page: 3
   wien: 3
   cologne: 3
   earth: 3
   ltd: 3
   monster: 3
   aws: 3
   ooo: 3
   bayern: 3
   plus: 3
   ninja: 3
   ax: 3
   cool: 3
   website: 3
   coach: 3
   aero: 3
   club: 3
   gl: 3
   delivery: 3
   hn: 3
   report: 3
   academy: 3
   bi: 3
   am: 3
   az: 3
   tf: 3
   pk: 3
   supplies: 3
   cf: 3
   ge: 3
   saarland: 3
   sm: 3
   ec: 3
   rw: 2
   fun: 2
   spreadbetting: 2
   global: 2
   kg: 2
   cu: 2
   cv: 2
   sr: 2
   bike: 2
   buzz: 2
   dz: 2
   sncf: 2
   int: 2
   training: 2
   ga: 2
   jetzt: 2
   mu: 2
   cr: 2
   uy: 2
   inc: 2
   af: 2
   best: 2
   care: 2
   fail: 2
   gy: 2
   video: 2
   tl: 2
   gm: 2
   online: 2
   gd: 2
   saxo: 2
   style: 2
   ht: 2
   cm: 2
   mo: 2
   abbott: 2
   pics: 2
   education: 2
   garden: 2
   yt: 2
   koeln: 2
   coffee: 2
   haus: 2
   bs: 2
   finance: 2
   gift: 2
   ve: 2
   click: 2
   wtf: 2
   np: 2
   cafe: 2
   scot: 2
   games: 2
   work: 2
   domains: 2
   photos: 2
   lk: 1
   bauhaus: 1
   jobs: 1
   tcs: 1
   film: 1
   na: 1
   organic: 1
   photography: 1
   bo: 1
   gq: 1
   trade: 1
   bj: 1
   gent: 1
   download: 1
   sn: 1
   vin: 1
   lighting: 1
   support: 1
   kaufen: 1
   bid: 1
   solar: 1
   cab: 1
   expert: 1
   cards: 1
   paris: 1
   td: 1
   eco: 1
   ng: 1
   gf: 1
   ne: 1
   africa: 1
   ml: 1
   rip: 1
   radio: 1
   fo: 1
   do: 1
   immo: 1
   archi: 1
   pg: 1
   place: 1
   bt: 1
   dm: 1
   ps: 1
   solution: 1
   stream: 1
   enterprises: 1
   farm: 1
   tz: 1
   tg: 1
   schule: 1
   qa: 1
   pictures: 1
   audio: 1
   iq: 1
   party: 1
   vodka: 1
   investments: 1
   dj: 1
   mn: 1
   mv: 1
   sc: 1
   xn--j1amh: 1
   cd: 1
   mg: 1
   contact: 1
   top: 1
   center: 1
   bio: 1
   pf: 1
   ruhr: 1
   nr: 1
   llc: 1
   cash: 1
   cy: 1
   legal: 1
   foundation: 1
   wf: 1
   nyc: 1
   mw: 1
   promo: 1
   mil: 1
   vc: 1
   wine: 1
   dvag: 1
   cg: 1
   gp: 1
   gt: 1
   ki: 1
   tm: 1
   bd: 1
   army: 1
   game: 1
   help: 1
   pr: 1
   tt: 1
   family: 1
   jo: 1
   insure: 1
   fyi: 1
   forex: 1
   je: 1
   gal: 1
   sb: 1
   pink: 1
   health: 1
   py: 1
   exchange: 1
   bot: 1
   apple: 1
   energy: 1
   kh: 1
   gallery: 1
   reisen: 1
   vu: 1
   tc: 1
   london: 1
   pn: 1
   city: 1
   ci: 1
   money: 1
   ug: 1
   vg: 1
   clinic: 1
   tips: 1
   sx: 1
   wedding: 1
   observer: 1
   directory: 1
   mba: 1
   sale: 1
   moe: 1
   dental: 1
   tel: 1
   graphics: 1
   science: 1
   win: 1
   capital: 1
   build: 1
   dog: 1
   comm: 1
   bf: 1
----------------------------------------

@GitTheHellOutaHere looking a little deeper, here's a tally comparison for european TLD in the suggested list.
TLD comparison, selected european TLD

TLD Our list  suggested list
    (90,152)   (34,726)
=== ========  ==============
de   964        6,178
eu   772          495
fr   712          970
uk   682          367
nl   442          578
it   348          272
es   208          107
be   201          188
ch   134          907

I don't buy this.
Thank you for the suggestion, but I decline.
Closing.

I don't understand what you're talking about. The Unified list is a merged list of several others, right?
None of those lists contained the url I posted, and are no doubt missing many other urls from the ShadowWhisperer list. That being the case, why not merge one more list into the Unified list?
I would think you'd be eager to add a list that helps make the Unified list more complete and more useful.

Thank you @GitTheHellOutaHere.
We only accept lists with a proven track record.  The list you suggest doesn't demonstrate that.
I think I've shown quantitatively that the list you suggest doesn't smell right.
There's no possible way a list with a third the number of our domains can have 6.7 times greater number of .ch entries (entries with  Switzerland TLD).  That's off by a factor of 20.  I happen to know, we're not weak in .ch domains.
Same story for domains from Germany, .de domains. That's off by a similar factor.  I know we aren't weak in German domain coverage.
So thank you for that, but I decline. I think our list might not be made for you.  And you know what?  That's ok.


⭐ 01 - Weather Forecasting Bot (Hacktoberfest Demo)

Follow This Link to Get Started!🎉
🤩 Thank you for participating in the CopilotKit Hacktoberfest event.
Please show your support and give a ⭐ to the CopilotKit repository.
Demo:
Weather Forecasting Bot
Description
Build a chatbot that gives real-time weather updates using CopilotKit's AI interaction capabilities.
Technology Requirements
Using CopilotKit

Required: Your project must utilize CopilotKit as a core component.
Installation: Include CopilotKit by following the installation guide at CopilotKit Quickstart.
Documentation: Familiarize yourself with CopilotKit's features through the Official Documentation.

Styling with Shadcn-UI

Required: All UI components in your project should be styled using Shadcn-UI.
Installation: Install Shadcn-UI documentation

Hi @NathanTarbert
I am interested in this task. Can you please assign me ?
Also can you please share documentation or how to build a chatbot? How to submit it ?

@nooras, thank you for your interest.
We will start assigning tomorrow when Hacktoberfest officially kicks off.
I will add a link to the instructions from our Hacktoberfest rules later today.

@SGCODEX & @nooras, please follow the link at the top to get started!

Thank you @NathanTarbert Sir, will get started.

Hi @NathanTarbert
there is no such file as template here
https://github.com/CopilotKit/CopilotKit/blob/main/.TEMPLATE.md

Also it would be great if u could provide any example.

Hi @nooras, apologies, there was a typo that affected the route. Please try again

The demo folder is at the root of the community folder - https://github.com/CopilotKit/CopilotKit/tree/main/community

I will fix it

I want to work on this issue :) , please assign it to me .
Thank you.

Hi @NathanTarbert
I'd like to work on this

Hey, I'd like to work on this too

Hey @NathanTarbert , Please assign this task to me.


ERROR: Signature extraction failed

Hi, I'm trying to download a video with 6h length of meditation music, and I'm getting this error:
~ % youtube-dl --extract-audio --verbose --audio-format mp3 https://www.youtube.com/watch?v=TekWIV0e16Q
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--extract-audio', u'--verbose', u'--audio-format', u'mp3', u'https://www.youtube.com/watch?v=TekWIV0e16Q']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.10.24
[debug] Python version 2.7.10 - Darwin-15.0.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.8.1, ffprobe 2.8.1
[debug] Proxy map: {}
[youtube] TekWIV0e16Q: Downloading webpage
[youtube] TekWIV0e16Q: Downloading video info webpage
[youtube] TekWIV0e16Q: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {22} signature length 40.42, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfl5u6mls/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfl5u6mls/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfl5u6mls/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 661, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 291, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1345, in _real_extract
    encrypted_sig, video_id, player_url, age_gate)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 827, in _decrypt_signature
    'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfl5u6mls/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfl5u6mls/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

 Read our FAQ if you have troubles updating.

Well, that was weird, I did $ brew update and the error persisted.
After doing $ brew upgrade youtube-dl it did work!
Thanks


Drop Database Additional Arguments

The additional argument adds dashes and extra space when using the "Drop Database" feature in a project with multiple contexts.

This is by design, because "Additional arguments" stands for the arguments list for your startup project, not for the dotnet ef.
See https://learn.microsoft.com/en-us/ef/core/cli/dotnet#aspnet-core-environment:

The -- token directs dotnet ef to treat everything that follows as an argument and not try to parse them as options. Any extra arguments not used by dotnet ef are forwarded to the app.

The context class should be configurable from the dialog itself as a field "DbContext", but seems like it's missing due to a bug, I'll fix it in the next release.

Thank you for the quick response. I greatly appreciate your hard work on this awesome plugin for Rider.


Added support for MetaEvent Time Signature see #7

first of all sorry about the empty spaces deletion, apparently my editor did it ^^'
This should add support to the Time Signature Meta Event, I added it as a Track method (just like the set tempo).
Please note that in MIDI 1 file format every time related meta event should be defined in the first track.
I used default parameter in the function signature (I am not really comfortable with javascript).

Could you please add usage example, it will be very helpful.

Here you go =)
var track = new MidiWriter.Track();
tracks.setTimeSignature(3, 4);

setTimeSignature(numerator, denominator)

Hi @lplume,
Looks great, I will try this out later today and merge.  Thanks for the help,
-Garrett

Looks good, thanks again.  This has been merged,
-Garrett


Extension is configured as formatter but it cannot format php files

Hello,
I get this error when i try to format a selection of code with vscode and this extension.
I do have the extension configured in settings.json, with the following snippet. No other settings collide with this in global config.
  "[php]": {
    "editor.tabSize": 4,
    "editor.formatOnSave": false,
    "editor.defaultFormatter": "open-southeners.laravel-pint",
  },

I also have a pint.json in the root of the project.
The error shown is the following, and only happens when i select text, and then right click and format selection

this is not my extension brother.
this is another one from open southerners. wrong repo.

Lol, sorry dude, i dont know how could this happen.
sry


Class-Conditional Free Text-Guided Generation

Thank you for your great work. Your implementation is based on class-conditional MAR models, which are limited. Is there a plan to train an MAR model with class-conditional free text guidance?

It seems that the shape of the noise tensor is constrained by the token embedding dimension during inference, so the MAR model can only generate images with a size of 256x256?

Thanks for your interest. Our models are trained on ImageNet, which is a class-conditional image generation benchmark. Text-to-image generation requires training on large-scale image-text dataset and is an interesting future direction.
MAR could be potentially used for image outpainting as it is based on AR (similar to MaskGIT). In this way, you can generate images with any size by keeping outpainting existing image.

Thanks for your interest. Our models are trained on ImageNet, which is a class-conditional image generation benchmark. Text-to-image generation requires training on large-scale image-text dataset and is an interesting future direction.
MAR could be potentially used for image outpainting as it is based on AR (similar to MaskGIT). In this way, you can generate images with any size by keeping outpainting existing image.

In the sample_tokens function of the MAR class, the seq_len is set to 256, which determines the generation resolution to be 256. Can the seq_len be set to others value to generate images beyond 256?

The seq_len is set to 256 and cannot be changed because it is correlated with the learned position embeddings. One trick you can play (similar to MaskGIT) is that once you generate a 256x256 image, you can take the right half of it as the unmasked left half of a new image and generate the right half of the new image again. This will extend your image to 256x384, and this is what I meant by "keeping outpainting existing image".