Parallax transition poor on some browsers

Is it possible to add an option to not use CSS transitions for the parallax effects, falling back to using JavaScript + requestAnimationFrame instead? For simple setups CSS transitions suffice well, but more complex ones like this transition very poorly on some browsers, notably Firefox (notice how the background image fails to catch up with the rest of the transition, sometimes even scrolling in the opposite direction). From my testing, only on Safari (both OS X and iOS) and MS Edge on Xbox One does the cited example work smoothly with CSS transitions alone.

Your link leads nowhere.

Weird, the link is working fine here... I could provide a jsfiddle, but in this case it might be better to see a real use case.

No, it is not possible. And actually there is no difference in performance between CSS transitions and requestAnimFrame, and with JS solution you'll got worse peroformance


Cannot use bevy::ui::Size

Bevy version
main branch (25d222b73e57f27cf7f346015c7f554dafab131a)
What you did
Take any example code and add use bevy::ui::Size directive.
Run cargo check --example the_example
What went wrong
error[E0432]: unresolved import `bevy::ui::Size`
 --> examples/2d/rotation.rs:3:5
  |
3 | use bevy::ui::Size;
  |     ^^^^^^^^^^^^^^ no `Size` in `ui`

Additional information
Of course a solution is to use the prelude, but according to the migration guide provided in this PR, we should be able to use bevy::ui::Size as well.

Thank you for the bug report! This problem was caused because the Size was imported twice in the lib.rs of bevy_ui which made it private instead of public.

Thanks for the quick fix!


New-AzureRmPolicyDefinition - category

How to set policy Category for policy definition using New-AzureRmPolicyDefinition cmdlet?

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

ID: 131095f2-56ff-d771-621a-c33973be0684
Version Independent ID: c62f2864-f6a3-515f-0f63-bfde76491842
Content: Programmatically create policies and view compliance data with Azure Policy
Content Source: articles/governance/policy/how-to/programmatically-create.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@JozoSlejko Got confirmation, Category can be used with Metadata.  Metadata takes a string, but that string is JSON that contains the property key/value pairs.  So, something like this:
-Metadata '{"Category":"Virtual Machine"}'
We'll get the ref content updated with an example to cover using Metadata like this that includes Category.  Thanks again for the feedback!
@MicrosoftDocs/azure-cxp-triage #please-close

Azure/azure-powershell#7829 Here's the link to the PR to update the example in the ref content.

If i use the example (New-AzureRmPolicyDefinition -Name 'VMPolicyDefinition' -Metadata '{"Category":"Virtual Machine"}' -Policy '{"if":{"source":"action","equals":"Microsoft.Compute/virtualMachines/write"},"then":{"effect":"deny"}}') to create a policy, the Category is still empty:


Errors in Grav 1.6.13 and Admin 1.9.8

After upgrade Grav from 1.6.11 to 1.6.13 and admin panel to newest version (1.9.8) on my local machine (PHP built-in web server, PHP 7.1.23 (cli)) I can see following errors:
task:getUpdates:
Warning: require(/index.php): failed to open stream: No such file or directory in /Users/marcinochyra/Downloads/default_site_backup--20190817193834/system/router.php on line 38

Fatal error: require(): Failed opening required '/index.php' (include_path='.:') in /Users/marcinochyra/Downloads/default_site_backup--20190817193834/system/router.php on line 38

tast:listmedia:
Warning: require(/index.php): failed to open stream: No such file or directory in /Users/marcinochyra/Downloads/default_site_backup--20190817193834/system/router.php on line 38

Fatal error: require(): Failed opening required '/index.php' (include_path='.:') in /Users/marcinochyra/Downloads/default_site_backup--20190817193834/system/router.php on line 38

tast:addmedia:
Warning: require(/index.php): failed to open stream: No such file or directory in /Users/marcinochyra/Downloads/default_site_backup--20190817193834/system/router.php on line 38

Fatal error: require(): Failed opening required '/index.php' (include_path='.:') in /Users/marcinochyra/Downloads/default_site_backup--20190817193834/system/router.php on line 38

Now I can't add any image and see any image previously added to pages.

@m-ochyra I can confirm this. I have the same issue.

@m-ochyra, @andi1984, to fix that change router.php: https://github.com/getgrav/grav/issues/2627#issuecomment-521784289

Ack, it seems my 1.6.13 release didn't work properly, didn't pick up the fix.  I'll re-release

1.6.14 released with this fix now.

Works great! Thank you.


support raspberry pi

Would you be able to support raspberry pi ? It would be really helpful for drones application. Thank you very much.

Sorry, not get notified somehow when issue was opened. We have library for raspberry pi4 in voxel3d_tools repo, but did not try with ros on pi4.

Hi @jackielee0424 Thank you very much for replying. I will try it.


Command "ceph orchestrator" was renamed to "ceph orch"

Since https://github.com/ceph/ceph/pull/33131 ceph orchestrator was renamed to ceph orch, so ceph-bootstrap must be adapted accordingly.

... and there are some other upcoming CLI renames in the next few days. I guess we have to cope with these as they come.


let's automate the build!

@carloslozano thanx for setting up the base for travis. Unfortunately, I am impatient, so I created the first PR myself :-)


ZFS unstable fails to build with latest Kernel

Issue description
On upgrading my 18.09 zfs encrypted base system with
zfs.enableUnstable = true;
zfs.requestEncryptionCredentials = true;
boot.kernelPackages= pkgs.linuxPackages_latest;

I got the following error:
cc1: some warnings being treated as errors
make[7]: *** [/nix/store/zqcvpqpl1vy3pjiw9imkapj5n1cpp868-linux-5.0.7-dev/lib/modules/5.0.7/source/scripts/Makefile.build:277: /build/source/module/icp/illumos-crypto.o] Error 1
make[6]: *** [/nix/store/zqcvpqpl1vy3pjiw9imkapj5n1cpp868-linux-5.0.7-dev/lib/modules/5.0.7/source/scripts/Makefile.build:492: /build/source/module/icp] Error 2
make[5]: *** [/nix/store/zqcvpqpl1vy3pjiw9imkapj5n1cpp868-linux-5.0.7-dev/lib/modules/5.0.7/source/Makefile:1576: _module_/build/source/module] Error 2
make[4]: *** [Makefile:171: sub-make] Error 2
make[3]: *** [Makefile:15: __sub-make] Error 2
make[3]: Leaving directory '/nix/store/zqcvpqpl1vy3pjiw9imkapj5n1cpp868-linux-5.0.7-dev/lib/modules/5.0.7/build'
make[2]: *** [Makefile:30: modules] Error 2
make[2]: Leaving directory '/build/source/module'
make[1]: *** [Makefile:799: all-recursive] Error 1
make[1]: Leaving directory '/build/source'
make: *** [Makefile:668: all] Error 2
builder for '/nix/store/b811aynkhvf34pgdlhs5y40vc7xphgwg-zfs-kernel-0.8.0-rc3-5.0.7.drv' failed with exit code 2
cannot build derivation '/nix/store/fwiygb7j4d8isajr8znm8qbyd46f5i97-kernel-modules.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/nmwr49gfsq26qm7xzrsa0k75wj9i97d2-nixos-system-home-server-19.03.172205.ea497998e4b.drv': 1 dependencies couldn't be built
error: build of '/nix/store/nmwr49gfsq26qm7xzrsa0k75wj9i97d2-nixos-system-home-server-19.03.172205.ea497998e4b.drv' failed

Full output: https://gist.github.com/Luis-Hebendanz/333ca4eb855cf9d2889b7386a6477456
Steps to reproduce
$ nix-channel --add https://nixos.org/channels/nixos-19.03 nixos
$ nixos-rebuild switch --upgrade

Reason (thanks @Ashy)
https://www.phoronix.com/scan.php?page=news_item&px=ZFS-On-Linux-5.0-Workaround
Workaround
Not using the latest kernel

#boot.kernelPackages= pkgs.linuxPackages_latest;

Technical details

system: "x86_64-linux"
host os: Linux 4.19.34, NixOS, 18.09.2519.2aa505b77c0 (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.3
channels(root): "nixos-18.09.2519.2aa505b77c0"
nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos

This is because zfs-0.8.0-rc3 doesn't support Linux 5:

Supported Kernels
Compatible with 2.6.32 - 4.20 Linux kernels.

Thanks! Maybe adding an "these two options are incompatible with each other" would help. Or a kernel version check in zfs package

They are not always incompatible, just with this specific combination versions. Modules usually don't depend too much on package versions, and the warning would probably be removed soon, possibly before that warning reaches the people who could benefit from it, so I'm not sure that'd be worth it.

Wow, with surprisingly good timing it looks like zfs-0.8.0-rc4 has just dropped and adds support for the 5.0 kernel:
https://github.com/zfsonlinux/zfs/releases/tag/zfs-0.8.0-rc4

Fixed in https://github.com/NixOS/nixpkgs/pull/59791


Gradle v5 deprecations

After updating to Android Studio 3.4 (and thus Gradle v5.1.1), some new deprecation notices show up in the build. These deprecations will be removed in Gradle v6.0, and will need to be resolved by then.
Repro steps:

Create a new Android app via Android Studio 3.4
Add apollo-android 1.0.0-alpha5 to the app
Run ./gradlew help --scan
View the generated report on gradle.com

An example report is here (not sure how long they keep them up): https://scans.gradle.com/s/id2ke3xby26xm/deprecations

1. The DefaultSourceDirectorySet constructor has been deprecated.
  This is scheduled to be removed in Gradle 6.0.
  Please use the ObjectFactory service to create instances of SourceDirectorySet instead.

DefaultSourceDirectorySet usage location

https://github.com/apollographql/apollo-android/blob/706db8d/apollo-gradle-plugin/src/main/java/com/apollographql/apollo/gradle/GraphQLSourceDirectorySet.java#L17

2. The ProjectLayout.directoryProperty() method has been deprecated.
  This is scheduled to be removed in Gradle 6.0.
  Please use the ObjectFactory.directoryProperty() method instead.

ProjectLayout.directoryProperty() usage locations

https://github.com/apollographql/apollo-android/blob/706db8d/apollo-gradle-plugin/src/main/groovy/com/apollographql/apollo/gradle/ApolloClassGenerationTask.groovy#L28
https://github.com/apollographql/apollo-android/blob/706db8d/apollo-gradle-plugin/src/main/groovy/com/apollographql/apollo/gradle/ApolloSystemCodegenGenerationTask.groovy#L16

3. Using method ObjectFactory.property() method to create a property of type Map<K, V> has been deprecated.
  This will fail with an error in Gradle 6.0.
  Please use the ObjectFactory.mapProperty() method instead.

ObjectFactory.property() for a Map usage locations

https://github.com/apollographql/apollo-android/blob/706db8d/apollo-gradle-plugin/src/main/groovy/com/apollographql/apollo/gradle/ApolloClassGenerationTask.groovy#L17
https://github.com/apollographql/apollo-android/blob/706db8d/apollo-gradle-plugin/src/main/groovy/com/apollographql/apollo/gradle/ApolloExtension.groovy#L45

This should be fixed with https://github.com/apollographql/apollo-android/pull/1476

Closing.


Can't access gateway host from inside of pod

fisrt , my ingressgateway name  is "istio.gateway.abd.com"
now i successed deploy the sample of bookinfo and I can visit the "istio.gateway.abd.com/productpage".
But, when i visit the again inside of the "pod/productpage-v1-c7765c886-v8t57", it will be 404.
why ?  can someone help me ?

Please provide more details of what you did or we will not be able to help. Thanks

configuration like this :
`apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
name: myapp
spec:
hosts:

myapp.com # cannot use "*" here since this is being combined with the mesh services
helloworld.default.svc.cluster.local
gateways:
mesh # applies internally as well as externally
myapp-gateway
http:
match:

uri:
prefix: /hello
gateways:

myapp-gateway #restricts this rule to apply only to ingress gateway
route:

destination:
host: helloworld.default.svc.cluster.local
subset: v1

match:

gateways:

mesh # applies to all services inside the mesh
route:

destination:
host: helloworld.default.svc.cluster.local
subset: v1`

Can you get a config dump from the client and the access logs: https://github.com/istio/istio/wiki/Troubleshooting-Istio#collecting-information-2

Closing as required info was not provided

But you probably need a ServiceEntry for myapp.com if you want to access it internally


de-duplicate reporting?

- update reporting queries to use latest db schema (this has already been done)
There is overlap between the reports that dump to csvs and the pgfs reporting functions, can/should this be eliminated?

dump to csv reports updated and redundant reporting removed.


Add music and sounds

The current app provides no music. Create a music controller that plays music throughout the application and attach the sound effects that cake created to the relevnt game objects!
Describe the solution you'd like
When changing a scene in unity the sound should continue playing and once a sound is done the music should shuffle to another random track.
Additional context
In addition to this, we will probably want to start creating the settings page. This would include a "master volume" and "SFX" slider so that players can control the application volume.

Edit: Reopening because the sond FX settings are not created yet.


segmentation fault (core dumped)

Hi, when I try to use deepseek-coder-6.7b-base to construct the datastore for code-related tasks, I also encounter the segmentation fault (core dumped) as mentioned in issue #19 . However, the vocab size of deepseek-coder-6.7b-base is 32000, which is smaller than 65535. I have also tried the solution mentioned there, but it didn't fix the bug. How can I resolve this problem? Thank you!

Hi,
I assume the issue lies in the following code:
writer = draftretriever.Writer(     index_file_path=datastore_path,     max_chunk_len=512 * 1024 * 1024,     vocab_size=tokenizer.vocab_size, )
Here, tokenizer.vocab_size is set to 32,000 for deepseek-coder-6.7b-base. However, the actual vocab_size for deepseek-coder-6.7b-base is 32,000 plus the number of added_tokens, which totals 32,021.
I've change the code vocab_size=tokenizer.vocab_size to vocab_size=tokenizer.vocab_size+len(tokenizer.get_added_vocab()). Sorry for the bug.

Thanks!!


Broken references in PDF for API docs

There are 170+ broken references in the PDF. They only occur for API docs, which are auto-generated. It'd would be worth looking into updating the generation scripts.
LaTeX Warning: Hyper reference `api:nodejs:reference::module_duckdb' on page 296 undefined on input line 19929.
LaTeX Warning: Hyper reference `api:nodejs:reference::module_duckdb..Connection' on page 296 undefined on input line 19934.
LaTeX Warning: Hyper reference `api:nodejs:reference::module_duckdb..Connection+run' on page 296 undefined on input line 19940.
...
LaTeX Warning: Hyper reference `api:python:reference::duckdb.DuckDBPyRelation' on page 757 undefined on input line 44980.

Followup of #1073.

I took a look at this but it seems too much of a hassle. It would require converting, e.g.:

from: api:nodejs:reference::module_duckdb..Database
to:   api:nodejs:reference::duckdbdatabase

which is easy.
But for functions, the function header's label contains the entire signature but the link doesn't. So we would need to turn

from: api:nodejs:reference::module_duckdb..Connection+arrowIPCStream
to:   api:nodejs:reference::databasearrowipcstreamsql-params-callback--codevoidcode

which is difficult and not worth it.


[videa] Fix extraction

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Fixed the Videa extractor, as it seems the parameter that looks like ?f=8.1735598.2138180.0 is now required for two requests. It's extracted automatically from the page.

Please merge this PR ASAP. I can confirm videa.hu is broken on upstream and this PR fixes it.

@csabahenk In meantime you can use yt-dlp where this fix was already merged.

@nyuszika7h thanks, I was not aware of that fork.


Can't open: Unknown error (0xC1)

Hello, just like the above picture error, why is this

Hi,
No idea, and the only thread I found while googling the problem was https://lists.llvm.org/pipermail/cfe-dev/2017-July/054808.html.
However, the bigger issue you have is that, on Windows, the LLVM toolchain used by rustc is not compiled with plugin support. Therefore, using the -Zllvm-plugins/-Cpasses flags of rustc is most likely undefined behavior.
To fix this, I suggest you take a look at this LLVM fork I made for this specific purpose. Instead of using the -Zllvm-plugins/-Cpasses flags, you would use the lld linker (from the fork) on Windows, and use your LLVM plugin as an LTO LLVM plugin.

Thank you for your reply. Is there a more detailed usage document on windows? Because I failed to use it according to the existing information, thank you again

You're welcome!
Last time I checked, the LLVM community doesn't talk much about LLVM plugins support on Windows, and the only useful information I found about it was this patch request: https://reviews.llvm.org/D18826?id=53036.
Also, I'm not sure the rustc maintainers have even bothered to document the fact that '-Zllvm-plugins' and '-Cpasses' won't work on Windows.
So, as you may have noticed, information is very thin on the subject. The way I discovered how to make it all work was by reading the LLVM sources and playing with various linker-related flags of rustc...
On Wednesday, November 13th, 2024 at 3:40 AM, V1rtu0l @.***> wrote:

Thank you for your reply. Is there a more detailed usage document on windows? Because I failed to use it according to the existing information, thank you again
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


client version 1.11 is too old. Minimum supported API version is 1.12

Hi,
I'm getting the following error trying to connect to a remote docker-machine:
Docker API error: Failed to build Image:
client version 1.11 is too old. Minimum supported API version is 1.12, please upgrade your client to a newer version
Does this plugin not support version higher than 1.11? I'm using the latest version of docker.
Thanks!

I just found that the cause is probably due to the docker-java dependency being very old.

We just upgraded to docker-java dependency to version 2.2.0 on master. The change will be in version 1.3.

@mattgruter when can we expect v1.3 release? Waiting eagerly since even I'm getting the same error.

@mattgruter Just checking when can we expect v1.3 ?

@mattgruter This is also a huge show stopper for me - can I help with any open issues that need to go into the 1.3 release?

Can you please fix this?

Any chance to get 1.3 released after over a year now?

Yes very soon. Some final issue to look over and verification to be done

I have the same issue.
Can you release a hotfix?


python3Packages.pywemo: 0.6.5 -> 0.6.6

Motivation for this change
Update to latest upstream release 0.6.6
Change log: https://github.com/pywemo/pywemo/releases/tag/0.6.6
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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.

Result of nixpkgs-review pr 132169 at 56ca1d12 run on aarch64-linux 1

1 package failed to build:

home-assistant

2 packages built successfully:

python38Packages.pywemo
python39Packages.pywemo

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Result of nixpkgs-review pr 132169 run on x86_64-linux 1

1 package failed to build:

home-assistant

2 packages built:

python38Packages.pywemo
python39Packages.pywemo


chore: bump circe-core, circe-generic, ... from 0.14.3 to 0.14.5

About this PR
📦 Updates

io.circe:circe-core
io.circe:circe-generic
io.circe:circe-parser

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

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

Superseded by #211.


upgrade the design of the KYC passbase starter screen

The objective is to be as close as the Figma  design : police size, button design, ...

c

removed


Use full-depth tree

We're currently using two different Tree depth constants for unit tests and general use mode, i.e. 4 or 16.
The actual expected state of a subnet would be rather 2^32, which would require to generate an empty tree directly through hardcoded nodes at each layer, to prevent tree creation time to blow-up. It would be also helpful to test performances in real conditions.
This would be directly implemented in https://github.com/Toposware/winterfell/tree/main/crypto/src/merkle/mod.rs with the other helper methods.

Partially addressed with PR #18. Would need something like RocksDB to manage such a large tree with regular machines.
Will consider reopening depending on the integration path when integrated to our framework.


⚠ Cioos National CKAN Sitemap has degraded performance

In 61f9c24, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 15463 ms

Resolved: Cioos National CKAN Sitemap performance has improved in d274d5d after 15 minutes.


Tiny Grammar Problem

In the first paragraph, there is a tiny grammar problem.

@grabbou I cannot merge PRs due to cricle ci


feat: Attach multiple files in the MessageInput

UIKIT-4405
Feat

Create useHandleUploadFiles hook for handling each case of sending file&files messages

Condition & Behavior

If selected only one file -> send file message
If selected multiple files

If selected only images -> send MFM
If selected several type of files -> send MFM for Images & send file message for the other files

@liamcho
useSendFileMessage and useSendFileMessageCallback are almost the same, they are the custom useCallback hooks that send file messages under the Channel and Thread modules.

I make it possible to send MFM from Thread also!


add hot-reloading to base dockerfile

Removed dev-Dockerfile
Added development stage and production stage. Development stage allows for hot reloading, but requires mounting of the repo root directory. It will also require docker-buildx as a dependency
Updated readme for clarity
Removed swearing from main.py

@bwilhelm42 @Zhenia-Magic , take a look when you get the chance


After browser asks to share location markers disapear

Works great until you answer the share location question. Then the markers disappear and don't come back.

Please create a plnkr for it, I will make the plnkr work for you

closing by inactivity


Remove linking for gesture handler

As from 0.60 modules has to be linked automatically.

Nice, thanks! Are there any other react-native link references in the docs we should remove? Can you also update this in the versioned_docs for 0.60?

Nice, thanks! Are there any other react-native link references in the docs we should remove? Can you also update this in the versioned_docs for 0.60?

Hi, if I'll find some other 'react-native link', i'll let you know.
But wait a moment, where is not only to remove linking, but update an article with this (I made it in my own app based on react-native v0.60.4 and react-native-gesture-handler 1.3.0 for make gesture handler works):
------------------------------------------------
You don't need to execute "react-native link", but you need to add on "app/src/main/java/<your_path/>MainActivity.java:
import com.swmansion.gesturehandler.react.RNGestureHandlerEnabledRootView;

public class MainActivity extends ReactActivity {
...
    @Override
    protected ReactActivityDelegate createReactActivityDelegate() {
      return new ReactActivityDelegate(this, getMainComponentName()) {
        @Override
        protected ReactRootView createRootView() {
         return new RNGestureHandlerEnabledRootView(MainActivity.this);
        }
      };
    }
...
}


MINOR: explain producer naming within Streams

Follow up for 0.11 from #3378
Call for merging @dguy

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5561/
Test PASSed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5577/
Test PASSed (JDK 7 and Scala 2.11).


Give us feedback form Appearance is not in line with Astro Doc Styling

📝 Issue Description
The Give us feedback form seems to be inconsistent with the general styling of the Astro docs. More specifically, the Submit button seems to be missing bordering styling and the Privacy Policy link seems to be the default link tag with default text styling.
📋 On which page(s) it occurs
This is present on all pages since the form is accessed via the RightSideBar.
🤔 Expected Behavior
Change border styling of the submit button to have a transparent background, grey border, and grey text. The Privacy Policy link should have text decoration removed and be centered on the modal with simple white text (and possibly an icon to the left).
👀 Current Behavior
Instead of the above, the submit button has the default HTML border styling and text-decoration. The Privacy Policy button also has the default HTML text-decoration.
🖥 Browser
Arc Version 1.41.0, Chrome Version 124.0.6367.119
📄 Additional Information
Screenshot of the module in question is attached below:

Thanks for flagging @SatanshuMishra!
Here is our reference design:

And a link to the Figma design: https://www.figma.com/file/GrDkcguAR7tSWPFuLVDixq/Theme---Starlight-Docs?type=design&node-id=454-34754&mode=design&t=FMXLtlWkDCNniwh2-4
We added the Privacy Policy link later, so it’s not shown in the design. I think the style for that is OK though — it matches other links on the site.
The submit button probably needs a border: 0 though and if we’re really picky, the issue/idea/other buttons outline should overlap with their container border rather than being inside it.

Adding some help wanted labels here in case anyone wants to help style the submit button closer to our original Figma design!
As Chris said, there isn't a need to change our privacy policy link, which should continue to just have default link styling to match the rest of the page. But the submit button does look a little gloomy right now! Anyone up for giving it some love?


Cleanup: Changed raise_click_exception() to return exc instead

See commit message.
No review needed.

Coverage increased (+0.04%) to 37.569% when pulling a78feda53d4a7dd230dd6676c5247065a2b05c4b on andy/cleanup-raise-click into 25c1521fc1c5a6ae3fdcd659045adb537daa7fd9 on master.


report "ticks" to the tflite-micro profiler as cycles / 1024

In tflite-micro the profiling code uses int32_t to represent ticks,
presumably because it was intended to be fed from a relatively low
precision timer source and not the raw system clock cycle counter.
The HPS model (unaccelerated) has one layer which takes more than 2**31
cycles and so it was being displayed in the profile as taking negative
time.
Report "ticks" as clock cycles / 1024, instead of raw cycles. The choice
of divisor is arbitrary but 1024 can be implemented in a single shift
instruction and still makes the numbers easy to interpret (humans just
have to think of it as "kilocycles").
Also, for completeness sake, use the full 64-bit cycle counter in the
unlikely event that a single profiling event takes more than 2**32
cycles. This implementation of get_mcycle() is taken from OpenTitan:
https://github.com/lowRISC/opentitan/blob/d9dc048680d89bd630ffae673103509e28017709/sw/device/lib/runtime/ibex.h#L28
based on the recommendation in the RISC-V Instruction Set Manual.

I also have a patch to make perf_get_mcycle() return the 64-bit value, and convert all usages to uint64_t... but I forgot that we are still stuck using Litex libbase printf() and it doesn't handle %llu correctly. Which I already discovered weeks ago, and tried fixing in https://github.com/enjoy-digital/litex/pull/910 but never finished. :-(
A nicer solution might be to switch us over to newlib or picolibc (#142) and then we should get a working %llu.

Nit: The cycle counter is restarted when an inference begins rather than as each layer begins. So the problem is not that a single layer takes more than 2^31 seconds, rather that the entire evaluation is longer than 2^31 seconds. See https://github.com/tensorflow/tflite-micro/blob/main/tensorflow/lite/micro/micro_profiler.cc#L62

The profiler code handles 32-bit wraparound, so if the whole evaluation takes more than 231 seconds but each layer takes less than 231 seconds everything would be fine. The issue is specifically with one layer taking more than 2**31 which just makes it print as a negative number (because they have used int32_t instead of uint32_t).

Yes, you're right.
On Mon, Jul 19, 2021 at 11:14 AM Dan Callaghan @.***>
wrote:

Nit: The cycle counter is restarted when an inference begins rather than
as each layer begins. So the problem is not that a single layer takes more
than 2^31 seconds, rather that the entire evaluation is longer than 2^31
seconds. See
https://github.com/tensorflow/tflite-micro/blob/main/tensorflow/lite/micro/micro_profiler.cc#L62
The profiler code handles 32-bit wraparound, so if the whole evaluation
takes more than 231 seconds but each layer takes less than 231 seconds
everything would be fine. The issue is specifically with one layer taking
more than 2**31 which just makes it print as a negative number (because
they have used int32_t instead of uint32_t).
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/google/CFU-Playground/pull/165#issuecomment-882154242,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJ4WASSNEPEJGSKJMKEIULTYN37HANCNFSM5APEFRQQ
.


Rename the package/project/library/etc.

I feel the name "PyTaskManager" does not reflect the goal of the project or the infrastructure. Perhaps we could consider renaming the project/package into something that does.
Options:

DLIpy (It rhymes! And to state the obvious: DLI as acronym for "distributed learning infrastructure)
pyDLI (yes, it can be reversed too ;-)

Snap .. already out of inspiration.
@jvsoest @frankcorneliusmartin suggestions?

I like your suggestions, however distributed learning could be confused with distributed machine learning where distributed stands for distributed workload:
http://www.dmtk.io/ or https://www.tensorflow.org/deploy/distributed
Therefore i would like to suggest something like:

DCIpy (distributed computing infrastructure)
RCIpy (remote computing infrastructure)

I will give this some more thought...

Well, I suppose the infrastructure can be used for both (with a few modifications ;-).
But it’s interesting to see your suggestions and an indication of how difficult naming is, because I associate distributed computing with grid (cluster) computing.
Perhaps we should add “privacy preserving” to the mix? ppD{C,L}Ipy or pyPP{C,D}LI?

Sent from my iPhone - so please forgive any typo's ;-)

On 11 Jun 2018, at 15:03, frankcorneliusmartin<EMAIL_ADDRESS>wrote:
I like your suggestions, however distributed learning could be confused with distributed machine learning where distributed stands for distributed workload:
http://www.dmtk.io/ or https://www.tensorflow.org/deploy/distributed
Therefore i would like to suggest something like:
DCIpy (distributed computing infrastructure)
RCIpy (remote computing infrastructure)
I will give this some more thought...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

A while ago we settled on ppDLI and nobody has complained since. Closing this issue :-).

Reopened this issue as we agreed on the new name but not renamed everything in the package:
[ ] Rename package from pytaskmanager to ppdli

[ ] Rename package from ppdli to Joey

[ ] Rename package from Joey to Vantage

See<PHONE_NUMBER>c09e6077f16aa446b3c5e9e819f4b1


Match iD's relation hover action

Description
When editing an object that is part of a relation, in iD you can hover over the relation box in the side panel and it will highlight the visible members of the relation. In Rapid hovering over it doesn't do anything. I know you can click the zoom button to zoom out and see the whole relation, and edit the relation directly to see all the members, but that isn't really helpful on relations that span entire states.
iD:
https://github.com/facebook/Rapid/assets/5402360/69d6fc93-2aa6-4e13-b058-ec3974750b99
vs Rapid:
https://github.com/facebook/Rapid/assets/5402360/6e518cb3-2dec-4dfd-be2c-ef77c7f81d09
(https://www.openstreetmap.org/node/158191774 is the one in the videos)

Thanks, I agree we should restore this 👍


Unable to verify signature

Trying to sign something with PS256 but failing to verify the signature in either Python or Javascript.
defmodule DynamicClientRequest do
  use Joken.Config

  @impl true
  def token_config do
    default_claims(iss: "ckWBLOKO6yH4mIDL8WLYXP", aud: "0015800000jfwxXAAQ")
    |> add_claim("application_type", fn -> "web" end, nil)
    |> add_claim("grant_types", fn -> ["authorization_code"] end, nil)
    |> add_claim("software_statement", fn -> File.read!("./certs/ssa") end, nil)
    |> add_claim("token_endpoint_auth_signing_alg", fn -> "PS256" end, nil)
    |> add_claim("request_object_signing_alg", fn -> "PS256" end, nil)
    |> add_claim("id_token_signed_response_alg", fn -> "PS256" end, nil)
    |> add_claim("token_endpoint_auth_method", fn -> "tls_client_auth" end, nil)
  end

  def signer do
    signer =
      Joken.Signer.create("PS256", %{"pem" => File.read!("./certs/seal.pem")}, %{
        "kid" => "A3kLpDUm0lcMeuUgCbxlkXkIx3c"
      })
  end
end

I then go to a language say python
jwt.decode(encoded, public_key, algorithms=["PS256"])
ValueError: ('Could not deserialize key data. The data may be in an incorrect format, it may be encrypted with an unsupported algorithm, or it may be an unsupported key type (e.g. EC curves with explicit parameters).', [_OpenSSLErrorWithText(code=151584876, lib=9, reason=108, reason_text=b'error:0909006C:PEM routines:get_name:no start line')])

Or javascript
jwt --decode --algorithms "PS256" --public-key-file A3kLpDUm0lcMeuUgCbxlkXkIx3c.pem (cat jwt)
JsonWebTokenError: invalid signature
    at /home/jakob/.config/yarn/global/node_modules/jsonwebtoken/verify.js:133:19
    at getSecret (/home/jakob/.config/yarn/global/node_modules/jsonwebtoken/verify.js:90:14)
    at module.exports [as verify] (/home/jakob/.config/yarn/global/node_modules/jsonwebtoken/verify.js:94:10)
    at module.exports (/home/jakob/.config/yarn/global/node_modules/jsonwebtokencli/convert.js:15:33)
    at /home/jakob/.config/yarn/global/node_modules/jsonwebtokencli/main.js:43:12

However if I use a JWT generated by a different language, the signatures validate correctly.

PS256 has a known bug as described https://github.com/potatosalad/erlang-jose/issues/121#issuecomment-919072956
Can you see that it resolves for you?

This fix resolves my issue but I would rather not rely on this too much if I can help it.
Is this going to be fixed either downstream or here?

This can only be fixed downstream unfortunately as it is the way JOSE passes options to RSA crypto. I'll be closing the issue here because we can't solve it on Joken side.


Support setting zk chroot path when initialize cluster

Why are the changes needed?
Users may encounter the following exception when trying to set kyuubi.ha.zookeeper.quorum to localhost:2181/lakehouse with chroot path /lakehouse nonexisted:
2021-11-10 10:56:34.510 ERROR server.KyuubiThriftBinaryFrontendService: Error starting service KyuubiServiceDiscovery
org.apache.kyuubi.KyuubiException: Failed to create namespace '/kyuubi'
        at org.apache.kyuubi.ha.client.ServiceDiscovery$.createServiceNode(ServiceDiscovery.scala:225)
        at org.apache.kyuubi.ha.client.ServiceDiscovery.start(ServiceDiscovery.scala:101)
......
Caused by: org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode = NoNode for /kyuubi
        at org.apache.zookeeper.KeeperException.create(KeeperException.java:114)
......

It is wonderful to support this since zookeeper connection with chroot path is generally recommended in production environments. With this feture the znodes in zookeeper likes below:
[zk: localhost:2181(CONNECTED) 28] ls /lakehouse
[kyuubi, kyuubi_USER, kyuubi_USER_SPARK_SQL]

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

localhost:2181/lakehouse

According to the syntax of JDBC URL for service discovery jdbc:hive2://<zookeeper quorum>/<dbName>;ServiceDiscoveryMode=zookeeper;zooKeeperNameSpace=kyuubi
The lakehouse is a dbName or part of <zookeeper quorum>?

localhost:2181/lakehouse

According to the syntax of JDBC URL for service discovery jdbc:hive2://<zookeeper quorum>/<dbName>;ServiceDiscoveryMode=zookeeper;zooKeeperNameSpace=kyuubi
The lakehouse is a dbName or part of <zookeeper quorum>?

The latter, users can use this znode to avoid creating znodes(such as: kyuubi_USER, kyuubi_USER_SPARK_SQ) in root path (/).

Can we make this change directly to ServiceDiscovery.createServiceNode? For example, when makePath for the namespace val ns = ZKPaths.makePath(null, namespace), we can mix the chroot part in?

Codecov Report

Merging #1359 (8e7b5a6) into master (9db2e5c) will decrease coverage by 0.14%.
The diff coverage is 16.66%.

@@             Coverage Diff              @@
##             master    #1359      +/-   ##
============================================
- Coverage     78.98%   78.83%   -0.15%
  Complexity      110      110
============================================
  Files           179      179
  Lines          7513     7531      +18
  Branches        919      921       +2
============================================
+ Hits           5934     5937       +3
- Misses         1086     1100      +14
- Partials        493      494       +1

Impacted Files
Coverage Δ

...che/kyuubi/ha/client/ZooKeeperClientProvider.scala
57.33% <16.66%> (-12.85%)
:arrow_down:

Continue to review full report at Codecov.

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

Can we make this change directly to ServiceDiscovery.createServiceNode?

agree, buildZookeeperClient is too heavy to do such things.

Can we make this change directly to ServiceDiscovery.createServiceNode? For example, when makePath for the namespace val ns = ZKPaths.makePath(null, namespace), we can mix the chroot part in?

@yaooqinn @ulysses-you I have tried this, however the _zkClient is inited by localhost:2181/chroot, if we use val ns = ZKPaths.makePath(chroot, namespace) it will lead to exception NoNode for /chroot/kyuubi, use a  _zkClient  inited by localhost:2181 is correct to create chroot path.

Can we make this change directly to ServiceDiscovery.createServiceNode?

agree, buildZookeeperClient is too heavy to do such things.

I think this step is needed (such as Kafka/Pulsar do) unless users create the chroot path in advance.

How about
--- a/kyuubi-server/src/main/scala/org/apache/kyuubi/server/KyuubiServer.scala
+++ b/kyuubi-server/src/main/scala/org/apache/kyuubi/server/KyuubiServer.scala
@@ -40,6 +40,8 @@ object KyuubiServer extends Logging {
       zkServer.start()
       conf.set(HA_ZK_QUORUM, zkServer.getConnectString)
       conf.set(HA_ZK_AUTH_TYPE, ZooKeeperAuthTypes.NONE.toString)
+    } else {
+      // create the chroot if necessary?
     }

// create the chroot if necessary?

This seems okay to me, I will refine this later, thanks for your tips.

@murong00 Thanks for your contribution and welcome!

@yaooqinn @pan3793 I have addressed above comments, please help to take a look again, thanks.

@yaooqinn @pan3793 PTAL, again.

thank you @murong00 ! do you have a chance to add a test ? I hope we can have a better coverage since the code about zk is important for Kyuubi.

@ulysses-you @pan3793 I have added a test to cover these changes, please take a look again, thanks.

thanks, merging to master

@murong00 Seems the client does not support chroot?
jdbc:hive2://<zookeeper quorum>/<dbName>;ServiceDiscoveryMode=zookeeper;zooKeeperNamespace=kyuubi

use:  jdbc:hive2:///;ServiceDiscoveryMode=zookeeper;zooKeeperNamespace=//kyuubi

I see,  the client should use zooKeeperNamespace=<chroot>/kyuubi


Fix circleci build

Doesn't changing from a fixed version to an LTS version exchange one problem for another?
The old problem: our build failed because our dependencies were outdated
The new problem: our build can now fail because our dependencies can move under us
Hard-coding the image version serves as documentation of the image that worked at the time, and improves reproducibility. It's not perfect (i.e. hard-coding the major and minor version still allows the patch version to shift beneath us) but we have semantic versioning to lean on here.
So I think what I'm saying is: in the absence of another side of the argument that I've not presented here, I think we'd be better off hard-coding the major version of the node docker image to whatever the latest LTS is today. What do you think?

Yeah, make sense, especially for some compile dependencies


Extend serialize

Reworked SerializableNode
The SerializableNode class now preserves relationship properties on .serialize, and imports them with .deserialize. Thus, we can serialize terms and offices, which was previously impossible without losing stakeholder metadata.
Note that this required a change to the JSON format of a serialized node. Where previously, a serialized node would look like this:
{ "name": "My Term",
"definition": "The definition",
"permission_group": "Sample Group",
"reports": [ "Report A", "Report B" ],
"stakeholders": [ "Office 1", "Office 2" ] } <-- no place to indicate what type of stakeholder
It will now look like this:
{ "name": "My Term",
"definition": "The definition",
"permission_group": { "Sample Group": {} },
"reports": { "Report A": {}, "Report B" : {} },
"stakeholders": { "Office 1": { "stake_type": "Responsible" }, "Office 2": { "stake_type": "Inform" } } }

How would we handle the relationship between things created in the portal and the things that are imported from the EDW?
term : column
database : table

I'd recommend changed the SerializeNode inherited class to a module. The only thing it's doing is adding a serialize method, not a constructor or anything require inheritance
module Bar
	def goodbye
		puts 'goodbye world'
	end
end

class Foo
	include Bar
	def hello
		puts 'hello world'
	end
end

f = Foo.new
f.hello
f.goodbye


Planned Features for ModTweaker2 0.9.2

Forestry

[ ] Ore dictionary support for Forestry Carpenter (#192)
[ ] Fermenter fuel support
[ ] Moistener fuel support

Railcraft

[x] Support for BlastFurnace fuels (#193)

Thaumcraft:

[x] Add aspect bracket handler (e.g. <aspect:Vitreus> * 5) (99bd8eaa1ebd563b355e42ef9c8cf97b942a15e8)
[ ] Add possibility to specify the recipe for displaying in Thaumonomicon instead of picking the first recipe which matches the output (#142)

Common:

[ ] Change handlers with chances to use WeightedItemStack

@Zixxl i think we should take about stack equality and stacksize

with the build from Oct 1, I still get a Cannot cast minetweaker.oredict.IoreDictEntry to minetweaker.item.IItemStack error


[Modify]It will not copy Voyager::routes() into routes/web.php, if th…

It will not copy Voyager::routes() into routes/web.php, if that already copied in the file when reinstall voyager.

Great job @rushairer, finally someone does it!

Great job @rushairer


router: allow propagating attempt count in header

Adds the ability to configure x-envoy-attempt-count to be set to the attempt count to allow upstreams to infer how many times the request has been retried.
Risk Level: Medium
Testing: Integration test
Docs Changes: Updated the header documentation to include new header
Release Notes: Added release note
Fixes #4210

looks good to me @ggreenway can you take a look?

This is not my area of expertise. @alyssawilk can you take this one?

@snowp you have merge conflict :(

@alyssawilk is out today. I can take it.

@snowp sorry needs a master merge.

@mattklein123 ptal


GUI: indicate when live transcription ongoing

grey out most user inputs when live transcribe ongoing
change window title when transcribing
mayb popup window when setting up models?

fixed in <IP_ADDRESS> 👍


Leave the Determinate Systems community

Description of changes
Due to a clerical error on my part, it seems I accidentally joined the wrong community! I'm not quite sure how, but I ended up in the Determinate Systems community when I was looking for Nix. Thanks to https://determinate.systems/posts/on-community-in-nix/ for clearing up my confusion!
This does orphan a small number of packages, but I trust that the Determinate Systems community can work that out.

Just to be clear on this, only one shareholder of Determinate Systems is on the board of the NixOS foundation, and no individual has absolute authority over Nix, Nixpkgs or NixOS.
I will not try to negate any of the other issues here, but everyone deserves to know that at least some things are not as bad as they have been presented.
I am not affiliated with Determinate Systems.
If you're interested, here's my perspective on things that were said about the Nix team. (Or CppNix team I guess?)
You are of course free to remove yourself from maintainership; no hard feelings.

and no individual has absolute authority over Nix, Nixpkgs or NixOS.

I imagine that this comment is more appropriately directed at Eelco, given their apparent attempt in the referenced blogpost to imply that Nix is a Determinate Systems project.

I'm confused by your statement. The chair of the foundation board published the link I quoted, and has made it very clear that this github organization, its community, and its future direction are the property of himself alone, and by extension his company Determinate Systems. Not, as I mistakenly thought previously, a collaboration of diverse contributors working to bring about a common ideal. My PR just corrects my mistake, while I go find that collaborative project I'd like to be a small part of.
If that post is not the consensus position, and the foundation chair does not have absolute ownership and authority over the project, why did the foundation chair say otherwise? Why did the foundation chair encourage people to migrate to community spaces that are under the sole control of Determinate Systems?
Looking at Github permissions, the board and its chair seem to hold complete administrative access over the organization. I'm given to understand this is also true of access to infrastructure beyond github. This does seem to indicate that the board has de-facto ultimate authority over the project, and through the chair have clarified how this project operates.
I would certainly be happy to be double-mistaken, as it were! It would save me quite a lot of work. But I don't see how your statement can be reconciled with the empirical ground truth?

their apparent attempt in the referenced blogpost to imply that Nix is a Determinate Systems project.

That was very foolish of him, and certainly counterproductive for what appear to be his goals.

I may not be able to answer everything, but I'll try my best as a community member who's been around for a while, but has not been directly involved with the foundation, or moderation team, or infra team.

The chair of the foundation board published the link I quoted, and has made it very clear that this github organization, its community, and its future direction are the property of himself alone, and by extension his company Determinate Systems.

This is for @edolstra to answer and I really don't want to do his dirty work, but I care about truth, so please bear with me while I share what I know. He's talked about creating these things and leading them, not owning them. Related, but certainly weaker than owning; no absolute power implied.
(skipping ahead and back if you don't mind:)

Looking at Github permissions, the board and its chair seem to hold complete administrative access over the organization

The GitHub organization has four owners (source, not sure if accessible to everyone):

Domen Kozar
Rok Garbas
Jonas Chevalier
Eelco Dolstra

If that post is not the consensus position, and the foundation chair does not have absolute ownership and authority over the project, why did the foundation chair say otherwise?

I believe he wasn't aware that people would read that into it. I would like him to make a statement refuting this.

Why did the foundation chair encourage people to migrate to community spaces that are under the sole control of Determinate Systems?

I don't know the details of this. Is DetSys hosting something? I know https://discourse.nixos.org is hosted by Flying Circus, which is a respectable company. I've never heard of any drama involving them.
This seems like a solvable problem.

I'm given to understand this is also true of access to infrastructure beyond github.

All I know is that we have a team whose work is quite transparent by having a public repo, where we can follow along. I don't know everyone's affiliation, but I recognize plenty non-DetSys handles there.
Example: https://github.com/NixOS/infra/issues/324

The community has largely self-organized into various structures such as the various teams, even before DetSys existed. These teams have most of these responsibilities and privileges that you care about. Any attempt to replace or hijack those would be foolish, leading to backlash from the members of those teams, which is not what has happened.
I hate to say it, but I can understand that sometimes activism can be more important than truth, to reach the activation threshold, but ultimately everyone should know the truth, which is the only reason I'm spending my time apparently trying to convince someone who, frankly speaking after a long week of both work and drama work I really shouldn't care about. Yet I do.

I think you misfiled this PR, given that the post you link clearly says that Nixpkgs community (this one) is not actually «run» by the Foundation or DetSys, and for DetSys communities there are links given (non of them going to https://github.com/NixOS ).
Obviously, everyone has an obvious right to stop maintainership of packages without owing anyone an explanation, but I wanted to inform you that the explanation you give looks inconsistent.

I won't reply point by point as this will turn into another forum debate, and goodness knows there's enough places for that already. I do appreciate you trying to defend what I personally feel has become indefensible, and I'm sorry to have caused you pain.
Where I disagree with you, I think, is on the impact of explicit vs. implicit power. The structures and teams you describe are nominal power structures, who should have authority over things. I agree that those exist and have some amount of authority over their domain.
I am leaving because Eelco's publication states, in no uncertain terms, that an implicit power structure exists, one in which he and DetSys own the direction of the project. And that he is not only aware of this, but actively wishes to keep it so. This is not the first instance of stating or demonstrating this implicit power, and while I don't think it's the sole governance problem that exists, it is a chronic impediment to addressing any governance problem. It's the problem of unbalanced authority vs. responsibility, which sits at the core of many organizational collapses.
You are of course welcome to disagree with my reading. But I've been silently observing the growing governance crisis for a couple of years, and seen not just lack of progress, but repeated and deliberate blockading of progress on the simplest of steps. I was willing to assume good intent and allow time for change to happen, but that goodwill ran out for me with the post I linked. I don't think it's possible to avoid a collapse of the ecosystem any more, although I will continue to hope that I'm wrong.

I don't know the details of this. Is DetSys hosting something?

Quoting from the post I linked:

I remain committed to creating a community where everyone feels seen, heard, and valued, and I will not let unfounded accusations detract from this important work. I encourage everyone reading this who feels that they have not been heard or feels displaced to join the Determinate Systems community as we continue working to make Nix as easy to use and as impactful as possible. Our code of conduct is available here, and you can join our Discord at https://determinate.systems/discord.

It's possible to read this and assume benign intent. But as the culmination of the last several years, I can't read this any other way than the foundation chair undermining existing community spaces in favor of his company's private space. You are, of course, welcome to read this another way.

I wanted to inform you that the explanation you give looks inconsistent.

I decline to play the game you are proposing to play. Please do not interact with me further, unless it's to merge this PR so that we can all move on.

@joepie91

I imagine that this comment is more appropriately directed at Eelco, given their apparent attempt in the referenced blogpost to imply that Nix is a Determinate Systems project.

I really don't see how you arrived at that interpretation, since my post explicitly says the exact opposite:

The assertion that Determinate Systems “owns” Nix or seeks to exert outsized influence over the project, the community, or the foundation is patently false: I am the only member of the Nix team who works for Determinate Systems.

@joepie91

I imagine that this comment is more appropriately directed at Eelco, given their apparent attempt in the referenced blogpost to imply that Nix is a Determinate Systems project.

I really don't see how you arrived at that interpretation, since my post explicitly says the exact opposite:

The assertion that Determinate Systems “owns” Nix or seeks to exert outsized influence over the project, the community, or the foundation is patently false: I am the only member of the Nix team who works for Determinate Systems.

@roberth

Is DetSys hosting something?

I don't believe we are. You can see where all our infrastructure lives in the https://github.com/NixOS/infra repo.

Resign

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/maintainers-leaving-nixpkgs/44192/9

Just to be clear on this, only one shareholder of Determinate Systems is on the board of the NixOS foundation, and no individual has absolute authority over Nix, Nixpkgs or NixOS.
I will not try to negate any of the other issues here, but everyone deserves to know that at least some things are not as bad as they have been presented.
I am not affiliated with Determinate Systems.
If you're interested, here's my perspective on things that were said about the Nix team. (Or CppNix team I guess?)
You are of course free to remove yourself from maintainership; no hard feelings.

@roberth , I think you should publish your post (my perspective) on Discourse. It is very well written. Thank you very much for that.


Feature Improvement

Adding User Search Functionality.
I want to work on this issue can I do it?

@shelcia Hey I was not able to understand the codebase. So, you can assign the issue to someone else :(

i would like to work on this issue ..could you assign this to me..


DatabaseGenerator is concatenating leadingDigits collection from XML source into one pattern string

Perhaps I can start with an example: the GB mobile phone number 07400 123456. If we put that into the libphonenumber online tool (https://rawgit.com/googlei18n/libphonenumber/master/javascript/i18n/phonenumbers/demo-compiled.html), then it returns the formatted national string "07400 123456" (as expected).
If I try to parse that number using GlobalPhone.Parse("07400 123456", "GB"), it returns "074 0012 3456" as the formatted national string, which looks incorrect (note the spacing).
I had a bit of a debug and it seems that the correct format for displaying this number is not being chosen. In the source XML from libphonenumber, the corresponding XML fragment for this case is:
    <numberFormat pattern="(7\d{3})(\d{6})">
      <leadingDigits>
        7(?:
          [1-5789]|
          62
        )
      </leadingDigits>
      <leadingDigits>
        7(?:
          [1-5789]|
          624
        )
      </leadingDigits>
      <format>$1 $2</format>
    </numberFormat>

That is, there are two leadingDigits elements here. Now, if we have a look at how GlobalPhone stores the leadingDigits when it parses the database (here a slight modification of one of your unit tests):
[Test]
public void it_can_generate_data_without_causing_an_exception()
{
var generator = DatabaseGenerator.Load(new WebClient().DownloadString("https://raw.githubusercontent.com/googlei18n/libphonenumber/master/resources/PhoneNumberMetadata.xml"));
var result = generator.RecordData().ToList();
var countryCode44 = result[63];
var leadingDigits = ((IDictionary[]) countryCode44["formats"])[4]["leadingDigits"];
}
...the leadingDigits variable here has the value "7(?:[1-5789]|62)7(?:[1-5789]|624)", i.e. it seems to me that both of the XML node patterns have simply been concatenated into a big long string pattern, which doesn't seem right at all! This seems to be the problem that's causing various formatting issues in an application of ours. Are you able to confirm that this is indeed a bug, or am I missing something? If this is indeed a bug, it probably affects any case where there is more than one leadingDigits XML element, right?

That looks indeed like a bug. Perhaps that we should add your regression test?

Good work on finding this issue.

Thanks :). I'm glad to hear that my description was understandable and that we both agree it's a problem.
To help understand the impact, I did a quick XPath query of the current master PhoneNumberMetadata.xml file on GitHub, and noticed that 22 out of 253 territories have at least one number format definition with more than one leadingDigits element. That means that this bug will potentially manifest in formatting errors for other regions (AR and AU for example). The XPATH query I used to find those is //territory[availableFormats/numberFormat[count(leadingDigits)>1]]
(wrapping that in a count() gives 22 matching territories back).
If I understand correctly, GlobalPhone is only using the leadingDigits information to do formatting. That is, based on a global search for "leadingDigits" in the solution, it seems that the information is only being used in the Format class. This means that parsing should not be affected (good news).
At the moment, the leadingDigits value in the format object is being set in the CompileFormat method of the DatabaseGenerator class. It gets the value from the Pattern method , which in turn calls TextOrNull, which is where the buggy "concatenation" of text from multiple leadingDigits nodes seems to be happening.
I see a two possible ways to fix this...

Appreciate that there may be more than one leadingDigits node, which will probably require a change to the *.json database structure (i.e. leadingDigits would no longer just be a string value, but rather an array of strings or similar). Depending on how this is implemented this may be a breaking change (i.e. consider the case where existing users update GlobalPhone but keep an old *.json database with the old structure).

Keep the leadingDigits property as a string, but do some regex tweaking to represent all the possible formatting alternatives in the one regex. That is, a regex something like this...
(?:leadingDigitsRegex1)|(?:leadingDigitsRegex2)
...where leadingDigitsRegex1 is the regex coming from the first leadingDigits node, leadingDigitsRegex2 is the regex coming from the second leadingDigits node etc.
Seeing as the leadingDigits are only being used for matching purposes in the Format class, this seems like it would work (note that I'm no regex expert...there might be a better way to do it than the way I've described above).

Although approach #2 is perhaps simpler to implement, #1 is perhaps the less-hacky solution. I'll leave it to you guys to decide the appropriate direction. Maybe you also have other approaches that are more appropriate.

I would prefer that we change the database structure. #1 is definitely the less hackish solution. If we do a major version change then an update to the format is more than acceptable.

Fixing the format does not fix the bug.

The format is fixed.


License?

Could a license be added to this repo? I'd like to use this on my projects. :)

Added LICENSE.


Use k8s schemas from our own CDN

Update the logic for downloading schemas to use our own CDN.

Contact @emamihe for details

Things we want to have:

[ ] The list of K8s schema versions should be updated automatically.
[ ] The Desktop should be bundled with the latest version at the moment of packaing, but if a new version is available, it should be updated automatically. A button in the Desktop to find a new one should be ok
[ ] The list should be updated in the server automatically every x days (i.e. daily or weekly)
[ ] The list should recommend versions: latest stable + latest versions
[ ] There should be a list of CRD that we want people to install (i.e. Argo, Flux, Openvela, etc). [See links]

Add out of the box support for:

[ ] ArgoCD CRD
[ ] Flux
[ ] Openvela
[ ] Testkube

We should fix the following issue along with this one: https://github.com/kubeshop/monokle/issues/1351


⚠ API - Lens has degraded performance

In ad7cbe7, API - Lens ($LENS_API_URL) experienced degraded performance:

HTTP code: 503
Response time: 585 ms

Resolved: API - Lens performance has improved in 2798a04 after 12 minutes.


perf: Optimize and reduce size of StringDiffOpKind enum

fixes #25

Can you run Rustfmt with cargo fmt?


Work around issues with black material surfaces

When possible, use the JSON description of the material to improve on the simpler protobuffer color scheme.

I applied 8 metallic materials to 8 rocky shapes, and they came through where one would expect, for all of the shapes defined by a mesh. They look a little different, but the base color differs, and the shininess comes through.
The color is not applied to the spheres, which use some other shader, so that is expected.

Your call @david-bremer if you want to handle spheres the same way.  I only did triangles and went out of my way to avoid lines (on purpose).


The average Episodic Return and Average Loss is nan

Hi Eric,
I am a beginner with PPO and I tried your code with the _log_summary() function implemented with the following main block.
if __name__ == '__main__':
	hyperparameters = {
				'timesteps_per_batch': 2048,
				'max_timesteps_per_episode': 200,
				'gamma': 0.99,
				'n_updates_per_iteration': 10,
				'lr': 3e-4,
				'clip': 0.2
			  }
	env = gym.make('Pendulum-v0')
	model = PPO(env=env, **hyperparameters)
	print(f'Model information ====== {model}')
	model.learn(10000)

The output keeps on giving nan value on Episodic Return and Average Loss. For example
-------------------- Iteration #50 --------------------
Average Episodic Length: 1.0
Average Episodic Return: nan
Average Loss: nan
Timesteps So Far: 50
Can you kindly help with this? The policy network is FeedForwardNN.

Hi Briti!
I just tried your block of code with the repo code, and it works out for me (had to change model = PPO(env=env, **hyperparameters) to model = PPO(policy_class=FeedForwardNN, env=env, **hyperparameters) though).
Output:
Model information ====== <ppo.PPO object at 0x7fa61287c358>
Learning...

Hi Eric,
Thank you for your reply. Attaching my
ppo.zip
ppo.py. I  suspect there is something wrong with the get_action() method. Kindly help.

I resolved the nans :) So the issue was actually in rollout and compute_rtgs; you had some pieces of code on the wrong indent, which were early terminating the two functions before they had a chance to finish their loops.
Specifically in rollout, I shifted:
# Collect episodic length and Rewards
batch_lens.append(ep_t + 1)
batch_rews.append(ep_rews)

one indent left, and
#Reshape data as tensors
batch_obs = torch.tensor(batch_obs, dtype=torch.float)
batch_acts  = torch.tensor(batch_acts, dtype=torch.float)
batch_log_probs = torch.tensor(batch_log_probs, dtype=torch.float)

# ALG STEP 4

batch_rtgs = self.compute_rtgs(batch_rews)

print(f'Batch rewards before logger======={batch_rews}')

# Log the episodic returns and episodic lengths in this batch.
self.logger['batch_rews'] = batch_rews
self.logger['batch_lens'] = batch_lens

# Return the batch data
return batch_obs, batch_acts, batch_log_probs, batch_rtgs, batch_lens

two indents left.
In compute_rtgs, I shifted:
#Convert the reward-to-go into a tensor
batch_rtgs = torch.tensor(batch_rtgs, dtype=torch.float)

return batch_rtgs

one indent left.
Here's ppo.py with the fixes: ppo.py.zip. Let me know if there's anything else I can help with :)

Works :) Thanks a lot..


sinkv2(ticdc): add black hole sink

What problem does this PR solve?

Issue Number: ref https://github.com/pingcap/tiflow/issues/5928
What is changed and how it works?

add black hole sink
extract the sink type

Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/run-all-tests

/merge

/run-all-tests

/run-dm-integration-test
/run-verify

/run-verify


Spinner (loading animation) update

Wonil-Suh1 created the following on Mar 09:
User story
As a user of IBM.com I need to know that the system is loading something, in a consistent way across web and products so that I can work better and be happier.
Notes
The digital loading spinner (https://www.ibm.com/standards/web/components/loading-spinner/) is different from Carbon spinner (https://next.carbondesignsystem.com/components/loading/code). Let's combine the style so that it's consistent.
Acceptance criteria

updated design and animation specs
specs are communicated to Carbon team
The digital design spinners are updated to the specs

Original issue: https://github.ibm.com/webstandards/digital-design/issues/625

On Mar 11, chsanche commented:
Note: Once the component update is done, please create an issue for the website to update the animation as well. Thank you.

On Mar 11, Olivia-Flory commented:
@Wonil-Suh1 are we wanting to update the current design for Northstar v18 and v19 alpha?
Or are you suggesting we propose that Carbon updates their spinner to look like the one we have?

On Mar 25, Wonil-Suh1 commented:
I say we update to match Carbon. I'm looking the speed and line weight.

On Mar 25, chsanche commented:
@Wonil-Suh1 👆👆👆

On Mar 26, Olivia-Flory commented:
Should we close this issue if we agreed to freezing v18/v19a code?

James and I looked into this and this issue is no longer relevant and will be closed.


fix(nav): shrinking the nav content to 100% of the content width

modifying the css rule for the nav-wrapper and nav elements to allow for the background of the nav to be full viewport width, but the nav itself to shrink to the page content width. See the 1800px image below for the real demonstration.
fix #47
Test URLs:

Before: https://main--takeda-ihs--hlxsites.hlx.page/
After: https://--takeda-ihs--hlxsites.hlx.page/

300 px
I didn't style the page content for this test, but you can see the nav and footer respecting the viewport width.

600 px
Same as 300px

900 px
Same as 300 px

1200 px
Same as 300 px

1800px
Notice the margins without the box-shadow.

Lesser priority than the content blocks


Application didn't run

When I was try run this application it said that operation returned an invalid status code 'Not found'

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

ID: 31a7905f-5818-4398-ee39-2842519dc054
Version Independent ID: 7f6a714b-cd88-694e-fd31-ad96fdfe5ed3
Content: Tutorial: Detect and display face data in an image using the .NET SDK - Azure Cognitive Services
Content Source: articles/cognitive-services/Face/Tutorials/FaceAPIinCSharpTutorial.md
Service: cognitive-services
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@sawravchy  Thanks for the feedback! We are currently investigating and will update you shortly.

@sawravchy Can you please provide more information of this error, it will help us to investigate it. Thanks.

When I run this code in Visual Studio and uploading image  system said that operation returned an invalid status code 'Not found' .

@sawravchy Hi I can reproduce the code and it works for me well. So this is not a doc-issue. I would suggest you to post your product question to MSDN forum for deeper help. https://social.msdn.microsoft.com/Forums/en-US/home?forum=AzureCognitiveService
May I ask which step you had the error? "Try the App" or "Detect the face"?

Detect the face

@PatrickFarley Hi Patrick, the document works for me well. But I am not sure if this is a document issue. Can you please check it? If not I will help the customer solve it with the support team's help. Thanks.


useDrag - touches is always 0

Just wanted to let you know, that since the v8 alpha, touches in useDrag is always set to 0.
According to the documentation it should be set to the "number of fingers touching the screen".
Just wanted to check, whether this new behaviour is intended or not.
Since we have "Multi-target-support" now, I also think it would make more sense to be the "number of fingers touching the target".

You're absolutely right, moving to Pointers Events for the drag gesture makes touches harder to calculate as Pointer Events don't have that information like Touch Events do, but that's not intended behavior. It is possible that we drop that attribute in the future.
Note that when touches is calculated properly, it's indeed the number of fingers touching the target, not the screen, I had corrected this a while ago but forgot to update the docs 😅
Looking at the code, this makes me realise that this beahvior triggers a bug with this sandbox: https://codesandbox.io/s/multi-gesture-card-rkgzi which becomes dysfunctional when trying to pinch. I need to work on it.

You're absolutely right, moving to Pointers Events for the drag gesture makes touches harder to calculate as Pointer Events don't have that information like Touch Events do, but that's not intended behavior. It is possible that we drop that attribute in the future.

I you remove completely this information, how we can be able to differentiate between 1 figer to select things and 2 finger to pan the view ?

Indeed you're right. I'll probably have to add state attributes, not sure whether it's going to be a Set of pointerId or just a counter that I can increment / decrement.

Ok I just had a stab at it. Current implementation overwrites touches from onPinch so I may have moved the problem elsewhere, but let me know if this fixes it for you at the moment.
Please install version 8.1.0-beta.3.

touches on useDrag seems to work now, however touches on usePinch is broken now (always 0).
Sadly, for my usecase I need both to work. (1 and 3 finger drag and pinch to zoom/pan)
Lukily I'm not in a hurry, as the only thing not working right now is the 3 finger drag gesture, which likely noone would have discovered, anyways. ;P

@freund17 Can you try beta 8.1.0-beta.6? The touch logic is not perfect but it should work hopefully.

Yeah... touches seems to be set as expected.
However there seem to be other problems, which prevent me from switching to the beta.
It seems related to setPointerCapture...
If that should already be working, I'll create a new issue once I have more information.

@freund17 yes setPointerCapture should be working 😅

It may be me, but pinch and pan are not well distinguished if both moves are done with two fingers. Am I missing something ?

There's no pan movement par say. Pan is just the drag gesture with two fingers which WILL be triggered whenever you pinch.
I'm a bit overwhelmed atm, I've discovered some bugs with pinch conflicting with drag that I need to solve but it's really not easy (at least to me).

Sorry, I would mean drag (not pan) vs pinch, probably the bug you've just mention. I'm not in a hurry, so take your time ;-)

@freund17 yes setPointerCapture should be working 😅

I created https://github.com/pmndrs/react-use-gesture/issues/242.

@freund17 @jrmi please have a look at beta 8.1.0-beta.8 which should solve most issues related to conflicts between drag and pinch.

@dbismut seems much better, touches, drag & pinch at same time. Just a detail, is it normal that distance is always positive even if the finger get closer ?

Thanks for testing! Distance is always positive, it's the distance between the two fingers. What you probably want to look at is the distance displacement which is movement[0].

Hi! I'm trying out 8.1.0-beta.9 and having an issue where when using useDrag the touches value is set to 0 even though the touch did not end. I get a few pixels worth of useDrag callbacks with the correct value, but then touches is reset to 0 again.

Hi @Tarpsvo would it be possible to set up a repro sandbox? Thanks!

Thanks for testing! Distance is always positive, it's the distance between the two fingers. What you probably want to look at is the distance displacement which is movement[0].

I'm not sure, but it doesn't seems to be the absolute distance between finger during my tests (I think da[0] give that distance) but offset distance since the first touch. If you spread the fingers, the value increase from 0 as expected then if you get your fingers closer, the value decrease to zero then increase again (positively) as you get closer. It can increase until the finger are touching.
So if this is the absolute distance, why the distance increase when the finger get closer and why it start to 0 value, and if it's the relative distance, it should be negative when finger are closer to initial touch. I'm missing something ?
But indeed movement[0] was the value i was looking for ;-)  thanks a lot !

Oh ok, you meant state.distance? If so, with the pinch gesture it makes no sense, it's the distance between da[0] (which was what I thought you were referring as distance in your earlier message) and da[1] the angle. I think I'll remove it from the pinch state to avoid any confusion.

Yes that state.distance. It was confusing indeed :eyes: Thanks again.

Alright, here's a reproducible sandbox @dbismut:
https://codesandbox.io/s/frosty-gareth-fjzlb?file=/src/App.js:322-339
The underlying issue is that on an  tag, the gesture ends abruptly. This happens only on version 8 and later. Version 7 works perfectly.

@Tarpsvo Have a look: https://codesandbox.io/s/hardcore-wind-f0qrw
I'm not sure about the problem you're facing exactly, but indeed, dragging an image or a link might result in unwanted behavior if you're not styling it appropriately. I would recommend setting the following attributes on your img tag to make it work as it should:
-webkit-user-drag: none;
user-select: none;

This might not be enough on Firefox (see #188), so you may want to preventDefault(). I don't think this is version-specific.
Now a few notes that could be worth mentioning: down will be true if touches > 0. So the check !down || touches === 0 isn't useful. v9 is also more logical with the down attribute, meaning that a gesture can be canceled and still have down set to true. What you generally want to check is active instead (active === true if the user is dragging AND the gesture wasn't canceled).
Hope this helps.

Thanks for the feedback @dbismut!
How come the exact same Carousel works in version 7 though (without CSS changes)? The older version somehow manages to drag on the images without an issue.

@Tarpsvo if I use your sandbox and switch to v7 I get the same unwanted behavior on Safari, Firefox and Chrome on a Mac. The main difference with v8+ is that it starts using Pointer Event vs Mouse and Touch Event.


Final Cut Pro grinds to a halt when using Metaburner on complex projects

For example, I applied Metaburner to a nearly 2 hour timeline of BRAW clips (using BRAW Toolbox), and Metaburner takes a good 30sec to actually render a frame. I THINK this is because we're storing the entire FCPXML internally - and FCPX is taking a long time to read the FCPXML data (and probably processed data), each frame. Will have to investigate if we can do some caching or something.

@randomeizer - Any recommendations on good Swift profiling frameworks?

This should be fixed in next beta by using caching.


Should we emit iteration_complete for last iteration

Currently the iteration_complete event is not emitted for the last iteration of the solver (i.e. for the iteration where we converged). See CG for an example.
This causes some loggers (e.g. the residual logger we use in benchmarks) to not output the residuals for the final iteration.
Should we consider this a bug, and emit the event for the final iteration?

@gflegar please elaborate, I don't understand yet.

If you converge in 3 iterations, you only get 2 events - for iterations 1 and 2, but not for iteration 3.

I would suggest to duplicate the logger inside the break loop. This is a generic fix that can be applied to all the algorithms. Moving around the logger does not make sense.

I did a pull request doing that, but I feel we have a different problem, and this is just a side effect of it.
The issue seems to be about what constitutes the end of an iteration. Looking at the solvers we have implemented, all of them say that the iteration is done whenever we end the while loop in the implementation. The problem is that this is completely arbitrary - a different implementation can freely move some of the operations from the end to the start of the loop or vice versa. We are not even consistent about that in the implementations we currently have:

CG and FCG consider that the end of iteration is after the SpMV and the solution update, but before applying the preconditioner, computing the residual and checking the stopping criterion
BICGStab and GMRES consider the iteration done after computing everything, but before checking if the stopping criterion completed
CGS on the other hand says that the iteration is completed only once everything is done and the stopping criterion checked

We should probably figure out a reasonable point of saying what constitutes the end of an iteration, independent of the solver - otherwise, it is confusing to the user (and to us).

I agree. But what is the standard? Is there a standard? Is Saad's book the standard? the Matlab implementation? I agree we should be consistent across solvers, but this implies we will not have the optimal runtime for all of them. Becausethey can stop at different points. Right now all implementations are such that the earliest possible stop is used.

I agree we should be consistent across solvers, but this implies we will not have the optimal runtime for all of them. Becausethey can stop at different points. Right now all implementations are such that the earliest possible stop is used.

I don't get this. We're not talking about stopping here, we're only deciding at what point the "iteration completed" event should be emitted (which in turn has nothing to do with the organization of the loops - we can emit that event anywhere in the loop, without touching the rest of the code). Changing that does not impact the convergence or the performance of the solver in any way - it only impacts what the outside user sees.

Understood. Yes, you are right. There is no strict relation - except for we want to log once we have a new residual, maybe. But, I agree. We should log always in the same place. Maybe the solution update is a reasonable point?

Or the convergence test?
BICGStab has 1 solution update every 2 iterations for example, GMRES has 1 solution update per restart, so it may not be the best point.

Or the convergence test? BICGStab has 1 solution update every 2 iterations for example, GMRES  has 1 solution update per restart, so it may not be the best point.
Good point. Convergence test might be a better choice. But it can happen very early in the loop. So, for example, for CG, not even the SpMV is invoked at that point. Which means, we have a different iteration count than SpMV count. (Except for if we count the SpMV outside the loop)


Exiting Deep Power Down on a p25q16h flash chip is not working with QSPI

Describe the bug
I am not able to exit DPD on a p25q16h flash chip (which is used on Seeed Xiao BLE nrf52840) when using the NRF QSPI driver.
Exiting DPD works fine on the same hardware when the NRF SPI driver is used.
I suspect that the QSPI driver is attempting to read a status register of the flash chip when the latter is in DPD mode. The flash chip is not responding, so the MCU gives up on it and never gets to send the RDPD (release deep sleep) command.
I have more detains in https://github.com/zephyrproject-rtos/zephyr/pull/55199#issuecomment-1455195564
To Reproduce
Steps to reproduce the behavior:

Patch in the QSPI pull request https://github.com/zephyrproject-rtos/zephyr/pull/55199
Enter System OFF and wake up (or just put the flash chip in DPD) and try to use flash.

Expected behavior
It should be possible to exit deep sleep with the QSPI peripheral.
Impact
Unable to use QSPI, have to use SPI mode instead.
Logs and console output
Environment (please complete the following information):
Using the nrf sdk v2.3.0
Additional context
Flash datasheet: https://datasheet.lcsc.com/lcsc/2006021534_PUYA--P25Q16H-SUH-IR_C559219.pdf
Seeed ble schematic: https://files.seeedstudio.com/wiki/XIAO-BLE/Seeed-Studio-XIAO-nRF52840-Sense-v1.1.pdf

Yes, same happens with a zephyr workspace (head at d61dcf2f1d)

This is indeed an issue and requires changes both in the Zephyr shim and the nrfx qspi driver. @anangl will propose a solution in the near future.


Azure egress should support more restrictive SAS tokens

Currently if an egress container is pre-created and a container level sas token (such as one created with Storage Explorer) is used, dotnet-monitor fails because it does not have enough permissions to issue the CreateContainerIfNotExists call. This is not an issue with account level SAS tokens (such as those created by the Storage Portal blade). We should consider supporting highly restricted tokens.
Also consider other auth options, such as MSI.

@wiktork It would be great to rely on AAD auth in order to access rather than having a secret to have to manage especially with AKS & pod identity.
From my brief and naive look it seems like this function would just need another egress option to specify to use DefaultAzureCredential rather than using a SAS token or an Account Key credentials, similar to how this guide describes. If that is true, I'm happy to try to spin up a PR that has that change.


Remove unused cython import

This was left over after some experimental work

@certik, @Sumith1896 can you merge this?


更新后，不能面板启动不了

a8d1d71..b40d381  master     -> origin/master
Updating a8d1d71..b40d381
Fast-forward
shell/test.sh   | 3 +++
shell/update.sh | 8 ++++----
2 files changed, 7 insertions(+), 4 deletions(-)
create mode 100644 shell/test.sh
更新/ql失败，请检查原因...
Fetching origin

开始更新仓库：/ql
Fetching origin
HEAD is now at b40d381 修复cron name匹配
Already up to date.
更新/ql成功...
Fetching origin

开始更新仓库：/ql
Fetching origin
fatal: unable to access 'https://github.com/whyour/qinglong.git/': OpenSSL SSL_read: No error information
error: Could not fetch origin
HEAD is now at b40d381 修复cron name匹配
fatal: unable to access 'https://github.com/whyour/qinglong.git/': OpenSSL SSL_read: No error information
更新/ql失败，请检查原因...
Fetching origin
fatal: unable to access 'https://github.com/whyour/qinglong-static.git/': OpenSSL SSL_read: No error information
error: Could not fetch origin
HEAD is now at 3ec8834 copy static at 2021-06-03 16:04:55
更新/ql失败，请检查原因...


Implement 1d convolution

I would like to have an implementation for a Convolution from pytorch down to vhdl.
This includes a part reading the values of the pytorch model, another one mapping the values for a vhdl-template and vhdl templates, one for the kernels shift over the input and one for the kernels operation.

I guess you mean a 1d convolution? I will start working on implementing a 1d convolution.

I think it also thought about 2d-Convolution, but 1d is a good start

@telefonjoker100 Okay. Then I create a separate issue for the 2d convolution, because i would say that this is to much for a single issue.

We have the 1d-convolution ready and should probably create a pull request.

The implementation is already online. Now the hardware needs to be tested


refactor: remove ReadDir in FTP service

I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
It closes #1438.
We merge the functionality of services::ftp::ReadDir into FtpPager, and use std::vec::IntoIter for more compact code.

Great PR! Thank you.


Measure text size for autoscale when rotated

Currently this uses the cos() of the rotation to calculate the width of rotated text.
cos(90) = 0 so the text size is thought to be zero, and no labels are skipped.
Added a check to use the sin() of the width and use that if greater.
sin(90) = 1, so in this case the text height is used as the width taken of the tick text when drawn.

@teroman a quick reminder to rebase this when you get a chance

Hi, I've not rebased a patch before, do you know of a good guide?
I tried cloning my patch branch locally and adding a Chart.js as remote repo, but got stuck when using the hash from merge-base with the rebase command. I thought it'd "just work" but instead I got some picking options and am not sure what to do.
Am I even close to doing the right thing?

@teroman I always do the following (doesn't involve a hash):
git checkout master (switch to main branch)
git remote add upstream git@github.com:chartjs/Chart.js.git (add chartjs as upstream repo)
git fetch upstream (get the latest changes)
git merge upstream/master (apply to your master branch)
git checkout YOURBRANCH (switch to the branch with your changes)
git rebase master (rebase against master)
FIX CONFLICTS
git add . (mark conflicting files as fixed)
git rebase --continue (finish rebase now that conflicts are all fixed)
git push -f (push the changes to this PR)

Well that first commit didn't work! Hopefully the second is okay, if so I'll rebase my other PR.

Thanks @benmccann for the advice, a bit of ssh key tinkering and I got things working.

@teroman would you be able to update this PR to address Simon's comments?

@teroman I'd really love to see this PR get merged. Will you be updating to address the comments? If not, I may have to close this PR at some point


PagerDuty and structured alerts data

I feel there is a need for a new PagerDuty integration in the Alertmanager which would keep alerts data in a structured form when transmitted to PagerDuty as opposed to the currently templated form.
I believe we need this because PagerDuty offers Automation features which allow to take certain actions based on field values. The fact that Alertmanager marshalls annotations and labels values in big chunks of text in the firing or resolved custom details fields limit greatly the possibility of using these data in automation rules.
PagerDuty V2 Event API support has a custom_details field which is currently used like this:
"custom_details": {
  "firing":       `{{ template "pagerduty.default.instances" .Alerts.Firing }}`,
  "resolved":     `{{ template "pagerduty.default.instances" .Alerts.Resolved }}`,
  "num_firing":   `{{ .Alerts.Firing | len }}`,
  "num_resolved": `{{ .Alerts.Resolved | len }}`
}

Unless I'm mistaken, the keys of the custom_details object must be hardcoded in the receiver configuration. There is no possibility to define them dynamically using .Alerts.(Resolved|Firing).Labels or .Alerts.(Resolved|Firing).Annotations.
After some testing it seems that PagerDuty V2 Event API supports at least 1 level of objects in custom_details allowing to do something like that.
PSEUDO CODE that describes valid JSON map[string]map[string]string for custom_details:
"custom_details": {
  "annotations": {
{{ range .Alerts.(Resolved|Firing)[0].Annotations.SortedPairs }}
    "{{ .Name }}": "{{ .Value }}",
{{ end }}
  },
  "labels": {
{{ range .Alerts.(Resolved|Firing)[0].Labels.SortedPairs }}
    "{{ .Name }}": "{{ .Value }}",
{{ end }}
  },
}

In that form, I think it will offer Alertmanager users the possibility to use advanced PagerDuty features.
Regards.

I totally agree that Alertmanager's PagerDuty integration really needs to support structured data for outbound alerts. I also tried customizing my text/template output to capture structured data like you proposed but ended up falling back to another approach.
I configure Alertmanager to output via a generic webhook, and target this to hit a minimal webhook transformer service I wrote running adjacent to Alertmanager. This service listens on localhost and takes the inbound webhook event and creates a PagerDuty V2 Event using the client API library. This way I fully preserve the entire inbound event structure without modifying Alertmanager.


Package request: timeshift (System restore tool for Linux)

Project description
System restore tool for Linux
This program takes snapshots for the root directory periodically or when told to using either rsync or btrfs, and allow the user restore them if need be. It is capable to do cross-distribution restore, or
to work from a live CD/USB.

Not sure if snapshots are important for NixOS, but it saves the day when you need to restore another distribution to the previous state inside NixOS, or if you are using nix package manager on other distributions.
Metadata

homepage URL: https://github.com/teejee2008/timeshift
source URL: https://github.com/teejee2008/timeshift
license: gpl3
platforms: linux

Not sure if snapshots are important for NixOS

from their readme:

It is designed to protect only system files and settings. User files such as documents, pictures and music are excluded.

that is not really usefull since nixos already allows rollbacks

It could be useful with Nix on non-NixOS Linux but you might as well use the native package manager to install Timeshift then.
Being able to offline timeshift non-NixOS distros from your NixOS installation seems like the most sensible use-case.

Being able to offline timeshift non-NixOS distros from your NixOS installation seems like the most sensible use-case.

Actually, my original motivation is to rescue my Debian Testing in the laptop.
It crashed after the system partition was filled up suddenly (probably by the inflating system logs).
I have a working NixOS installation in a USB stick (it  is one of the very distros that can be installed onto a removable storage device, making it boot able elsewhere and not affecting the local boot loader at the same time.), and it seems to be a good idea to rescue it from the USB stick.
It's probably a bit user-specific. :sweat_smile:
BTW, what is the Nixy way to deal with the trouble if something similar (something fills up the disk space suddenly) happen to a NixOS installation?
Thanks you very much for answering, and for this wonderful distro!

BTW, what is the Nixy way to deal with the trouble if something similar (something fills up the disk space suddenly) happen to a NixOS installation?

 Preferably in that order.

Oh and getting rid of stray gcroots can also help a ton. I had one that kept an old 19.09 system closure  around for months.

It might not be needed by most of the NixOS users. But the project itself seems to be easy to build (with well-written make files and simple dependencies). I can write one when I have time.

I hope it's still relevant.

I think this is going to help those who want to upgrade from a previous system's version.

AFAIK, this snapshot tool is commonly seen in Debian-based distros, and is enabled by default on Ubuntu and Linux Mint.
Remaining issues:

The "periodic snapshot" functionality requires crontab access from superuser. This is not enabled by deafult, and can be disabled at run time. If we want to have it on NixOS, it may require special patches and a NixOS module.

timeshift-gtk expects /etc/timeshift/timeshift.json to exist before it starts. I'm not sure how other packages manage that.


Spark Connect Init DSL

What changes were proposed in this pull request?

In this PR, I propose to add a DSL to Spark connect that is similar to dataframe but very lightweight. This DSL use dataframe like API to construct Spark connect proto, then we call re-use server side proto translation to eventually get the analyzed plan.
Why are the changes needed?

Initial Spark Connect DSL to test protobuf protocol.
Does this PR introduce any user-facing change?

No
How was this patch tested?

UT

R: @grundprinzip

Closing this as connect is in spark repo now.