suggestions

1st, very well done script!
2nd, some suggestions for enhancements

add an option to clone to an usb connected drive, useful for those who have boot fs on sd and root one on hd or usb dongle, for example...
add an option for unattended cloning, no pause at the end waiting for mods in /etc folder...
add an option to do a SYNC backup, so adding the --delete switch to rsync to remove stuff from DST sd that's not anymore on SRC sd...

thanks in advance

Yes  -u for unattended would be good for me...

@billw2 we added 2 of the suggestions to this fork, in case you want to pull them back to main repo:
https://github.com/scargill/rpi-clone/blob/master/rpi-clone

On Thu, 31 Aug 2017 16:13:29 +0000 (UTC)
fragolinux<EMAIL_ADDRESS>wrote:

@billw2 we added 2 of the suggestions to this fork, in case you want to pull them back to main repo:
https://github.com/scargill/rpi-clone/blob/master/rpi-clone

Thanks, I'll have them added along with other changes I'm currently working on for the
next release.
Bill

Thanks - just to let you know - in total I have 3 items
1 - optional change of hostname - one of the guys has submitted this but I think only updated HOSTNAMES - wheres I normally update both HOSTS and HOSTNAMES.
2  -  -d DELETE option - which I think is essential for cloning - if you need an exact copy.
3 -  -u for unattended...
HOWEVER right now (hence I'm writing as it isn't out there) - I had an issue - I have a NEO2 which has it's ROOT partion on a hard drive (SDA1).
So I altered your 	SRC_ROOT to say SDA1
And it worked - I have successfully backed up an SD+HD Neo2 to an SD - popped the new SD in and it all works - the ONLY issue I'm having is that the SD (which I cleared completely - removing all partitions) is a 32GB SD  and for some reason - the script has only created a 14GB partition for ROOT -  I'd have expected it to use up all the space. We'll look at this but if you know better PLEASE do tell.   If all of this goes into the next version I'll happily scrap my fork - no point in having two separate versions....
Thoughts on the disk size (the original SD was 16G - the hard disk holing the root partition was 56GB yet my new 32GB SD ends up with the boot partition and a 14GB root partition....

On Fri, 01 Sep 2017 18:39:35 +0000 (UTC)
Peter Scargill<EMAIL_ADDRESS>wrote:

Thanks - just to let you know - in total I have 3 items
1 - optional change of hostname - one of the guys has submitted this but I think only updated HOSTNAMES -
wheres I normally update both HOSTS and HOSTNAMES. 2  -  -d DELETE option - which I think is essential for
cloning - if you need an exact copy. 3 -  -u for unattended...

1 - There will be ways to set the hostname:  by option or by script.   2 - rpi-clone has
always been using --delete.  It's hardwired at the spot where the rsync command is
run, so that option is redundant, unless I'm missing something?
3 - I've added in your unattended.

HOWEVER right now (hence I'm writing as it isn't out there) - I had an issue - I have a NEO2 which has it's
ROOT partion on a hard drive (SDA1).
So I altered your 	SRC_ROOT to say SDA1

The new version will automatically figure out the root partition number and it won't
be hardwired to partition 2.  Please test that when I get the next release out.

And it worked - I have successfully backed up an SD+HD Neo2 to an SD - popped the new SD in and it all works

the ONLY issue I'm having is that the SD (which I cleared completely - removing all partitions) is a 32GB
SD  and for some reason - the script has only created a 14GB partition for ROOT -  I'd have expected it to
use up all the space. We'll look at this but if you know better PLEASE do tell.   If all of this goes into
the next version I'll happily scrap my fork - no point in having two separate versions....

Only the last partition can be resized to fill the disk.  So if your root is partition 1 you will
only get the same size as the source if there are more partitions.  I'll look at if there can
be an option to pick the partition to resize.  How is that disk organized, is boot partition 2?
Can you show me Neo2 output from these commands:
sudo parted print
sudo parted -m print
findmnt -o source,target,fstype -l | grep "^/dev/"
Also, how does the Neo2 boot?  Is just files in a /boot directory or does a bootloader
like grub (or what?) need to be installed.  rpi-clone will have an alternate way to
clone if a boot loader can be separately installed like grub.  In this case a destination
disk can be prepared manually with partition sizes you want (and even different numbers
of partitions) as long as partitions and file systems are created on the destination to match
the booted disks mounted partitions.  So far I've only been able to test this on my Debian
desktop that uses grub.

Hi
Ok, we missed DELETE and so added it. I've just been told it is there. Oh, well, only wasted 10 minutes :-)
Hostname - we only added it as I update both hosts and hostname files and only one was implemented in the other fork.. Good to know...
Partitions - GREAT - looks like I can relax and wait for update...
You asked for NEO output - here it is (I've gone back to the original setup, not the SD I made...
First first request - sudo parted print...
Error: Could not stat device print - No such file or directory.
Second one returned exactly the same.
Third one returns:
/dev/sda1      /                               ext4
/dev/mmcblk0p1 /boot                 vfat
As for Neo booting - there is a fat boot partition - and it has a file called boot.scr - there is a text version called boot.cmd which you alter the name of the partition if you've set up for hard disk - and you recompile that file...
These are the files I can see in the boot partition. I've attached an image.

If you need more info or want me to test something - my email is pete at scargill dot org - by all means get in touch - I've a variety of board - NEO2 NEO PLUS2 - OODROID C2 etc which I can test.
Good work - I'm used to the SD backup on the Pi and it is sorely missed elsewhere so these changes are most welcome.

Antonio suggested I give you this info... the output from these 4 commands
sudo parted /dev/sda -m print
sudo parted /dev/sda print
sudo parted /dev/mmcblk0 -m print
sudo parted /dev/mmcblk0 print
Here they are in order...
BYT;
/dev/sda:60.0GB:scsi:512:4096:msdos:JMicron Tech:;
1:1049kB:60.0GB:60.0GB:ext4::;

Model: JMicron Tech (scsi)
Disk /dev/sda: 60.0GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number  Start   End     Size    Type     File system  Flags
1      1049kB  60.0GB  60.0GB  primary  ext4

1:25.2MB:130MB:105MB:fat16::;
2:130MB:16.0GB:15.9GB:ext4::;

Model: SD 00000 (sd/mmc)
Disk /dev/mmcblk0: 16.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number  Start   End     Size    Type     File system  Flags
1      25.2MB  130MB   105MB   primary  fat16
2      130MB   16.0GB  15.9GB  primary  ext4

On Sat, 02 Sep 2017 09:56:25 +0000 (UTC)
Peter Scargill<EMAIL_ADDRESS>wrote:

Antonio suggested I give you this info... the output from these 4 commands
sudo parted /dev/sda -m print
sudo parted /dev/sda print
sudo parted /dev/mmcblk0 -m print
sudo parted /dev/mmcblk0 print
Here they are in order...

That info was what I needed, thanks.
But one more thing, does the Neo2 use PARTUUID in /etc/fstab and /boot/cmdline.txt
like recent Raspbians do?  Or does it just use device names like previous Raspbians.
Maybe if I could I see those files (or the Neo2 equivalent of cmdline.txt if any)?
I want to be sure of what to expect so I can cover my bases for the various use cases
of rpi-clone I want to work.

FSTAB contains
/dev/mmcblk0p1    /boot vfat defaults 0 0
There is no /biit.cmdline.txt - just the file boot.cmd which compiles to boot.scr. Here is the content of my boot.cmd
Recompile with:
mkimage -C none -A arm -T script -d boot.cmd boot.scr
setenv fsck.repair yes
setenv ramdisk rootfs.cpio.gz
setenv kernel Image
setenv env_addr 0x45000000
setenv kernel_addr 0x46000000
setenv ramdisk_addr 0x47000000
setenv dtb_addr 0x48000000
fatload mmc 0 ${kernel_addr} ${kernel}
fatload mmc 0 ${ramdisk_addr} ${ramdisk}
fatload mmc 0 ${dtb_addr} sun50i-h5-${board}.dtb
fdt addr ${dtb_addr}
setup MAC address
fdt set ethernet0 local-mac-address ${mac_node}
setup boot_device
fdt set mmc${boot_mmc} boot_device <1>
setenv bootargs earlyprintk root=/dev/sda1 rootfstype=ext4 rw rootwait fsck.repair=${fsck.repair} panic=10 ${extra}
booti ${kernel_addr} ${ramdisk_addr}:500000 ${dtb_addr}

Anything else I can get?

On Sat, 02 Sep 2017 13:06:53 -0700
Peter Scargill<EMAIL_ADDRESS>wrote:

Anything else I can get?

That's good for me to get done what I want to do.  Now it's just a case of your
giving it a test run when I get the next version out.  If any issues pop up then it
shouldn't be a problem to deal with them.

Can't wait....

Should be resolved in new version 2.0


Reproducer for JGRP-2293

https://issues.jboss.org/browse/JGRP-2293

Looks like ASYM_ENCRYPT_LeaveTest, how do you reconcile the two?

@belaban That's correct, however, there is also issue with ASYM_ENCRYPT which ASYM_ENCRYPT_LeaveTest reproduces (WIP), so I can reconcile the two once we fixed both issues.


feat: add plugin-bundle-types

This PR adds a new plugin to generate a bundle of TS definitions, it makes a big sense for web and node builds.

/cc @FredKSchott

This is great! I was actually looking for something like this a while ago, but couldn't get it to work. How stable is dts-bundle-generator? Does it run successfully 100% of the time? Is there anything that can go in a type definition file that it can't handle?

https://www.npmjs.com/package/dts-bundle-generator#known-limitations
They have an own list of limitations, for small packages that I have tried with this plugin works like a charm.
https://github.com/Swatinem/rollup-plugin-dts/issues/5 - this issue contains some compassion on issues

Ah, yes that's right. I ran into similar problems when I tried this originally.
This is something that I very much want, but right now I'd be against publishing an official bundler with so many caveats. I would definitely point to it as a community plugin (currently working on a page on pikapkg.com to highlight these better).

Okay, I understand your concern there 👍
I will publish it as own package.

Great, thanks for understanding.
And please do publish it yourself! And once you do, link it here so that we can add it to the README (or feel free to create that PR yourself)


[nrf fromlist] samples: boards: nordic: system_off: Run on nrf54l20pdk

Add overlays to execute system_off tests on nrf54l20pdk.
Upstream PR #: 82957
manifest-pr-skip

Commit tag will fail until
https://github.com/zephyrproject-rtos/zephyr/pull/82262
is merged. Changes are already in the NCS.


CA1816 in NamedPipeClient.Dispose()

In PowerShell-CI-linux: https://dev.azure.com/powershell/PowerShell/_build/results?buildId=111689&view=logs&j=8579d1dd-da9d-5760-afc4-fb4c05cf5d6d&t=236f801b-8fac-50c5-f817-425a182daa54&l=6000
/home/vsts/work/1/s/test/tools/NamedPipeConnection/src/code/NamedPipeConnection.cs(61,13): warning CA1816: NamedPipeClient.Dispose() calls GC.SuppressFinalize(object), a method that is typically only called within an implementation of 'IDisposable.Dispose'. Refer to the IDisposable pattern for more information. [/home/vsts/work/1/s/test/tools/NamedPipeConnection/src/code/Microsoft.PowerShell.NamedPipeConnection.csproj::TargetFramework=net7.0]

cc: @PaulHigin

Present since #17011?

NamedPipeClient should implement IDisposable and it does not.
Presumably this warning has been present since #18338.

open software


Is puppeteer-core / puppeteer installed with chrome-aws-lambda

Hello,
Thanks for your work on this, saved me a lot of time already :)
Im using chrome-aws-lambda in a layer, i was wondering if I have to install puppeteer-core separately?
If i dont install it separately on my lambda, it doesnt find puppeteer-core, but i can see it in chrome-aws-lambda dependencies, so i was just wondering if im doing something wrong.
My concern is that those dependencies can desynchronize and as you probably know, any puppeteer version if guaranteed to work only with certain chromium version (more on that here: https://github.com/GoogleChrome/puppeteer#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy ) - thats why im trying to invent a way to avoid breaking it when i update one and forget about the other.
Thanks,
Pawel

+1. It seems puppeteer-core is only a devDependency to this package so you should install yourself.

@pavelloz No, it's not. This project started before puppeteer-core was released and with standard puppeteer additional tweaking was necessary to prevent the download of the default binary.
I'm not sure if puppeteer-core should be bundled tho, as that can become kinda restrictive. Even listing it in peerDependencies in this case is not ideal, as you may still prefer to use puppeteer (for local testing).

Any thoughts on https://github.com/GoogleChrome/puppeteer#q-why-doesnt-puppeteer-vxxx-work-with-chromium-vyyy ?

@pavelloz To put it in PPTR terms: I see chrome-aws-lambda as a divisible entity of puppeteer / puppeteer-core (the simple fact that there's two puppeteer packages kinda mandates that).
As in, you could use the executablePath getter to get a binary that you could use with other libraries, like CRI for instance. The fact that there are puppeteer-specific helper methods within this package is merely a acknowledgment that PPTR is the de-facto library for Chrome interaction, but not necessarily the only one.
I started this project following Chromium version numbers as release tags, but soon switched to puppeteer versions in order to make it easier for users to sync puppeteer and chrome-aws-lambda dependencies.
Any major/minor version of puppeteer will have a corresponding major/minor version of chrome-aws-lambda (patch number is reserved to fix issues in this package). To me, that seems simple enough to keep in sync.

There's a few more reasons why I think bundling is a bad idea, the first of which I already mentioned: chrome-aws-lambda started before puppeteer-core was released, so that would mean if puppeteer-core was bundled now, backwards expectations would fail.
Another one is that I'd have a lot more overhead following puppeteer releases: 3 patch versions of puppeteer were released in the last 9 days, but they all kept the same Chromium version. So far, all Chromium version bumps have been followed by a minor version bump, but that might not always be the case, so tracking that with semver could become very manual.
Another reason is drifts in versions that would just create confusion; puppeteer 1.11.0 was followed by chrome-aws-lambda 1.11.0, but there would have unmatched versions with upstream:

chrome-aws-lambda 1.11.1 introduced typings and a minor improvement
chrome-aws-lambda 1.11.2 introduced support for Google Cloud Functions


add decorator and policy to storage_files and propagate context for it

For reviewers, there are two things to look for.

I add the @distributed_trace or @distributed_trace_async for every function that will lead to a network call.
I have added the DistributedTracingPolicy to the correct place.
I propagate the context with tracing_context.with_current_context any time a new thread is created. This should work with both threading and ThreadPoolExecutor. An example is the following:

future = executor.submit(tracing_context.with_current_context(uploader.process_chunk), chunk)

Can one of the admins verify this patch?

/azp run python - storage - ci (Generic_Tests Linux_Python36)

/azp run python - storage - ci


Small improvements to README

You were using direct HTML links to the project's files before, I replaced them with relative links that use Markdown. This makes the raw README easier to read and makes it so it doesn’t load a new page when clicking on the navigation links.

@QazCetelic Thanks alot for this PR. I am new to opensource!! Your changes look good. Merging it. Thank you contributing to BlocklyML


Add a way to set the default loading and error components

Agreed, also it's not possible to pass a loading element into composeAll right now.

This is documented and works just fine for me using

import React from 'react';
const MyLoading = () => React.createElement("div", null, "Hmm...");

export default composeAll(
  composeWithTracker(composer, MyLoading),
  useDeps()
)(CampaignPreviewTemplate);

@TimFletcher yea i later discovered that too. It works fine but I think a better way of writing it would be
import React from 'react';
const MyLoading = () => React.createElement("div", null, "Hmm...");

export default composeAll(
  composeWithTracker(composer),
  useDeps()
)(CampaignPreviewTemplate, MyLoading);

I actually think it makes sense to have each composer function have it's own loading component since it's possible that you would want to show a different loading screen depending on what data is being fetched.
I have another requirement though that doesn't seem to currently be in scope. I would like to be able to render my loading component using props that are passed into it.
My example is that I would like to render a user's profile photo in the loading component while I am loading other user data, however I only have access to that user as a passed in prop.

+1

+1

+1
please

Implement this and released with v1.11.0.
See docs: https://github.com/kadirahq/react-komposer#change-default-components

Where is the best place to define and set this components?
Inside client/modules/core/configs I have created a file called react-komposer-configs.js, where I define and set the loading and error component. Then this is imported and called in the configs folder index.js, which is imported and called from the index.js core folder. However it is NOT working
I made a gist https://gist.github.com/PolGuixe/42c572704986b79ea3ce2a8f80ad2409 with the code.

I'm also facing issues with this. I set the default components but I get an error telling me that I "Should provide a loading component in react native"

There's a bug in the current implementation that doesn't allow for setting of default loading and error components in React Native.
https://github.com/kadirahq/react-komposer/blob/master/lib/compose.js#L22
I would open a separate issue for this.

@clayne11 yes. Would love to see a PR as well for that.

Is it working for normal react as well? I am having issues.

@PolGuixe: maybe related to this? https://github.com/kadirahq/react-komposer/issues/114

@macrozone: most likely it is. Have you found a solution?

A simple PR would fix it. Move the fetching of the loading element into render.


Is there any plan to support txid transmission across thread pool WITHOUT wrapping the runnable task or executor service?

Currently, we must/should change the biz code if we want to pass the txid from one thread to another pooled thread. See the link
So, Is there any plan to support txid transmission across thread pool WITHOUT wrapping the runnable task or executor service? (eg, decorating thread pool implementation class in the agent)
There is a opensource implementation - Transmittable-Thread-Local, pls check the document.

This implementation also requires code modifications. I don't know of a better advantage.

I find this PR #6710 answered my question. Thanks!

我发现这个 PR #6710回答了我的问题。谢谢！

嗨，您好，我想请问这个异步线程追踪插件启用后有效吗？
您是如何开启插件的？


RemoteSeek event not triggering on Android 13 notification.

Describe the Bug
On Android 13, the notification seek slider is always active even when it is not included in the Media Controls Capabilities array.
Also, when you use the slider on the notification to seek to a new position, the RemoteSeek event is never fired.
Steps To Reproduce
I tested on Android 13, not sure about older android versions.
Make sure that Capability.SeekTo is not included in the capabilities array.
capabilities: [
     Capability.Play,
     Capability.Pause,
     Capability.SkipToNext,
     Capability.SkipToPrevious,
    // we DON'T want to seek from remote
    //  Capability.SeekTo,
   ]

Rebuild and observe that the seek slider is always active and functioning.
Now add the seekTo capability.
capabilities: [
     Capability.Play,
     Capability.Pause,
     Capability.SkipToNext,
     Capability.SkipToPrevious,
    // we want to seek from remote
    Capability.SeekTo,
   ]

Rebuild, then Observe that the Event.RemoteSeek is never fired although the seek is actually functioning.
Code To Reproduce
NA
Replicable on Example App?
Yes
Environment Info:
System:
    OS: macOS 12.6
    CPU: (8) arm64 Apple M1
    Memory: 163.78 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.15.1/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.15.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.4, iOS 16.0, macOS 12.3, tvOS 16.0, watchOS 9.0
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.2 AI-202.76<IP_ADDRESS>86908
    Xcode: 14.0.1/14A400 - /usr/bin/xcodebuild
  Languages:
    Java: <IP_ADDRESS> - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.0.0 => 18.0.0
    react-native: ^0.70.6 => 0.70.6
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found
info React Native v0.71.0 is now available (your project is running on v0.70.6).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.71.0
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.70.6
info For more info, check out "https://reactnative.dev/docs/upgrading".

How I can Help
What can you do to help resolve this?
Have you investigated the underlying JS or Swift/Android code causing this bug?
Can you create a Pull Request with a fix?

Interesting – have you tested this using the nightly version?

I did test with nightly version installed today, still not working

I was able to fix  the issue where the Event.RemoteSeek event was not being emitted through the following pr https://github.com/doublesymmetry/KotlinAudio/pull/63

I believe the rest of your issue is a duplicate of https://github.com/doublesymmetry/react-native-track-player/issues/1775


impossible to login with long email

Expected behavior
you can enter the email entirely during login
Actual behavior
you cannot enter the email entirely during login (maximum number of characters is reached)
Information about the Issue
when you try to login with a long email, the maximum number of characters can be reached
Steps to reproduce the behavior

... try to enter a long email at login
...

This has been fixed in a recent PR, which has yet to be released.
https://github.com/docker/kitematic/pull/2574
Thanks for the issue!


Update stylesheets

This updates TEI Stylesheets to latest version 7.55.0.

A note on whether you've tested it and found it OK is always appreciated.

tested it on the pdf-guidelines-test branch
closed with 885b3f425371298fb4bdebdb90735896eda2cfaf


refine, document, and redistribute code for profile page

code refined and commented happy with it for the moment, further functionality(update/delete/view post) to be added through post branch


Not able to use doc.text and the new doc.html method together in a page

If i try to use both the jspdf methods i.e doc.text and doc.html , the .html method overrides everything and doc.text things don't appear in the generated pdf.
Can't we use these two together ?
let doc = new jsPDF('p' , 'pt' , 'letter');

 doc.setTextColor(0, 0, 0);
 doc.setFontType("normal");
 doc.setFontSize(12);

 const specialtySubTitle = `Take the hassle out of payments, scheduling, and charting.` ;
 let specialtySubTitleLine = doc.splitTextToSize(specialtySubTitle, (130-15-15));
 doc.text(105,78,specialtySubTitleLine, null, null, 'center');

   doc.html(bodyElement, {
     callback: function (doc) {
       doc.save();
     }
   });
}

Why closed?


nix-bisect: init at 0.4.1

Description of changes
Package up https://github.com/timokau/nix-bisect for nicer bisects.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

nix-bisect


Support Vuze as downloader

Would it be possible to support Vuze as a downloader? It's the only torrent client I've found that's easy to configure to bind to my VPN interface.

If I recall correctly Vuze doesn't have proper post processing script execution or support labels/categories which is essential for the process to be able to work.
That being said using Radarr and Sonarr you don't necessarily need any scripts to run after the download component of the process and they can monitor Vuze themselves and then do all the processing after they move the file
Let me know if I am mistaken and Vuze has updated but a quick search doesn't show anything

I'll take a look and reply back here. I'm just setting everything up for the first time so it's all new to me (labels, post-processing scripts, etc).
I thought the same but I configured the postSonarr and postRadarr scripts to run after download but they weren't kicked off after the download completed, so I assumed downloader script was needed.

I never followed up on this. Following the instructions to disable completed download handling in Sonarr after the file finishes downloading nothing happens. I tried turning that option back on and then the post-processing to convert works but then both the original file and converted get copied to the season directory.


Plugin for fetch instrumentation

Is your plugin request related to a problem? Please describe.

We already have a plugin for XHR and as I understand it's suitable for libraries like axios. But many people use fetch as a modern alternative. It would be nice to have plugin for fetch instrumentation
Is it applicable for Node or Browser or both
browser only
Do you expect this plugin to be commonly used
It's hard to say in numbers but wahtwg-fetch polyfill has 25m downloads per month. And also there are different polyfills and people who are not use polyfill at all.
https://yarnpkg.com/package/whatwg-fetch

can take it

Think this probably makes sense as a core plugin @mayurkale22 wdyt?


CI sometimes is broken

@Furisto Can I ask you to write down what you know?

Hey, which part is broken? I see that the run on master is working
Although there is an issue, where there is a daily run of podman_tests on my fork's master, and it constantly fails, even even though the commit that it is currently at passed it here

@YJDoc2 cc; @adrianreber
I'm not sure but why rust-criu build failed 😭
https://github.com/containers/youki/pull/1123

In the CI logs, it is showing that rust-criu version 0.2.0 is used? even though all cargo.toml and lockfile has version 0.5.7 specfified in it?
   Compiling procfs v0.14.0
   Compiling rust-criu v0.2.0
error[E0583]: file not found for module `rpc`
 --> /home/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/rust-criu-0.2.0/src/proto/mod.rs:1:1

The crates.io only has v 0.2 published : https://crates.io/crates/rust-criu , so there might be some mismatch somewhere, although I can't see why it is failing now, and didn't fail before

I think the CI was fixed with https://github.com/containers/youki/pull/1125

@stefins Thanks for your effort! I tried to rebase #1123 , but still failed 😭

I think the CI was fixed with https://github.com/containers/youki/pull/1125

I believe this is regarding to one of my previous comments :

Although there is an issue, where there is a daily run of podman_tests on my fork's master, and it constantly fails, even even though the commit that it is currently at passed it here

That is fixed by the PR they have mentioned. but as you have said, the PR CI is still broken for some reason. As I have mentioned, the CI is still using rust-criu v0.2.0 , even though the github has release v0.5.7, as crates io still only has release 0.2.0 , maybe that is causing the issue.

Again :sob:

Hey @utam0k , if you are talking about podman tests, it is due to the rust 1.64 changes, which should be fixed in #1211 . I tried to re run the workflow, but that still uses older commit, so is still failing at build stage, I think when it will run tomorrow,  it should work again.

@YJDoc2 Thanks for your comment. I think we have trouble with the cache of ci.
https://github.com/containers/youki/pull/1206

I cleared all caches.


fix(search): update the search index when changing version

Before when we changed the version during the dropdown the search
would happen on the previous version.
This is done as a hack in Vue but couldn't find another way ;)
Fix #855
Signed-off-by: Charly Molter<EMAIL_ADDRESS>

It's part of the this.$page which is a standard vuepress way for page metadata


Support Swift Package Manager

Is your feature request related to a problem? Please describe.
We set up a Capacitor app with SPM instead of Cocoa pods. Therefor this library doesn't work for us.
Describe the solution you'd like
A Package.swift file/ SPM support
For now i forked this library and somehow managed to get this working, but honestly I don't feel super safe about it, as I also had to mess with SQLCipher. Links I followed:

https://www.youtube.com/watch?v=iVrD854cFYM
https://github.com/sqlcipher/sqlcipher/issues/371

This would be a great addition

@marius-se Do you mind sharing your fork? Would offer a good starting place for investigating this feature.


ClientSideInstance.xml referencing within package-solution.json

With regard to this quote:

ClientSideInstance.xml file is also referenced in the package-solution.json, so that it's included inside of the *.sppkg file, when you package your solution.

It sounds as though it should be there, by default. In fact, it must be added to the elementManifests array.

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

ID: 7e41df74-a651-cfa5-a538-9397e6793f52
Version Independent ID: 9f272325-fdb3-68e3-634b-e7428128f75b
Content: Tenant Wide Deployment of SharePoint Framework Extensions
Content Source: docs/spfx/extensions/basics/tenant-wide-deployment-extensions.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @VesaJuvonen
Microsoft Alias: vesaj

Can you be more specific when you aren't seeing it? I just tested creating a SPFx extension in a new project (SPFx v1.11) & it's definitely added to that file:
{
  "$schema": "https://developer.microsoft.com/json-schemas/spfx-build/package-solution.schema.json",
  "solution": {
    "name": "test-ext-client-side-solution",
    "id": "5846d90c-83bf-42a8-8246-dce4b9b3f2ec",
    "version": "<IP_ADDRESS>",
    "includeClientSideAssets": true,
    "isDomainIsolated": false,
    "developer": {
      "name": "",
      "websiteUrl": "",
      "privacyUrl": "",
      "termsOfUseUrl": "",
      "mpnId": ""
    },
    "features": [
      {
        "title": "Application Extension - Deployment of custom action.",
        "description": "Deploys a custom action with ClientSideComponentId association",
        "id": "2255c8c7-f180-4bbe-a8a9-9aef9d749a45",
        "version": "<IP_ADDRESS>",
        "assets": {
          "elementManifests": [
            "elements.xml",
            "ClientSideInstance.xml"
          ]
        }
      }
    ]
  },
  "paths": {
    "zippedPackage": "solution/test-ext.sppkg"
  }
}

Here's what I run:

Here's the output:

Story story: this is by design... I've submitted a PR that will get merged to add some clarification to the docs. Take a look at the linked PR above if you want to see the specifics...
The reason: you picked SP2019 (that only has SPFx v1.4) as your target env. If you include that file in the package-solution.json (which is only used for tenant-wide deployment, introduced in SPFx v1.6), the generated *.sppkg will throw an exception if deployed to SP2019. That's why it isn't added when you pick SP2019 as a target environment. If you pick SP Online, it will be present.


Change the menu layout

Describe your problem here.
Hello, i'm a new developer and i'm making a mod with a few friends.
We're struggling to change the menu layout, and the tutorial we've seen so far have only worked on earlier versions of Psych Engine.
We only want to move the menu buttons to the side and also change the scale of them.
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No

//in this code
for (i in 0...optionShit.length)
{
	var offset:Float = 108 - (Math.max(optionShit.length, 4) - 4) * 80;
	var menuItem:FlxSprite = new FlxSprite(0, (i * 140) + offset);
	menuItem.antialiasing = ClientPrefs.data.antialiasing;
	menuItem.frames = Paths.getSparrowAtlas('mainmenu/menu_' + optionShit[i]);
	menuItem.animation.addByPrefix('idle', optionShit[i] + " basic", 24);
	menuItem.animation.addByPrefix('selected', optionShit[i] + " white", 24);
	menuItem.animation.play('idle');
	menuItems.add(menuItem);
	var scr:Float = (optionShit.length - 4) * 0.135;
	if (optionShit.length < 6)
		scr = 0;
	menuItem.scrollFactor.set(0, scr);
        // changing scale (all buttons)
        menuItem.scale = (scaleX, scaleY) // your values instead of scaleX and scaleY (1.5, 1.5 for example)
        // moving buttons (all buttons. and btw if you do this with Y, then all the buttons will be in the same place on Y)
        menuItem.x(value) // your X value
	menuItem.updateHitbox();
	menuItem.screenCenter(X);
        // move buttons code (separately). add so if you need to
        switch [i]
        {
                case 0: // story_mode
                        menuItem.x = 0
                        menuItem.y = 0
                        // you can change the scale also here with 'menuItem.scale' but separately for each button
                case 1: // freeplay
                        menuItem.x = 0
                        menuItem.y = 0
               // with the rest also up to 6 (0 - 6)
               // you can do for example 0, 2 and not write other values
               // 0 - story_mode, 1 - freeplay, 2 - mods, 3 - awards, 4 - credits, 5 - donate, 6 - options
         }
}

THANK YOU SO MUCH
I've been struggling to find help anywhere, but yeah this helps a lot
Appreciate you wanting to help, but the mod's supposed to be an inside joke between my group of friends, so yeah lol
Thanks again!

Reopening this again, because it didn't work, i managed to make the positions of the menu buttons work. but not to scale it.

try menuItem.scale.set(x, y)

Thank you!

//in this code
for (i in 0...optionShit.length)
{
	var offset:Float = 108 - (Math.max(optionShit.length, 4) - 4) * 80;
	var menuItem:FlxSprite = new FlxSprite(0, (i * 140) + offset);
	menuItem.antialiasing = ClientPrefs.data.antialiasing;
	menuItem.frames = Paths.getSparrowAtlas('mainmenu/menu_' + optionShit[i]);
	menuItem.animation.addByPrefix('idle', optionShit[i] + " basic", 24);
	menuItem.animation.addByPrefix('selected', optionShit[i] + " white", 24);
	menuItem.animation.play('idle');
	menuItems.add(menuItem);
	var scr:Float = (optionShit.length - 4) * 0.135;
	if (optionShit.length < 6)
		scr = 0;
	menuItem.scrollFactor.set(0, scr);
        // changing scale (all buttons)
        menuItem.scale = (scaleX, scaleY) // your values instead of scaleX and scaleY (1.5, 1.5 for example)
        // moving buttons (all buttons. and btw if you do this with Y, then all the buttons will be in the same place on Y)
        menuItem.x(value) // your X value
	menuItem.updateHitbox();
	menuItem.screenCenter(X);
        // move buttons code (separately). add so if you need to
        switch [i]
        {
                case 0: // story_mode
                        menuItem.x = 0
                        menuItem.y = 0
                        // you can change the scale also here with 'menuItem.scale' but separately for each button
                case 1: // freeplay
                        menuItem.x = 0
                        menuItem.y = 0
               // with the rest also up to 6 (0 - 6)
               // you can do for example 0, 2 and not write other values
               // 0 - story_mode, 1 - freeplay, 2 - mods, 3 - awards, 4 - credits, 5 - donate, 6 - options
         }
}

just add the code you need. btw I am an new developer too and I can help if I can.

what do i do with this? where do i put it.


Ignite-cli requests react-native-cli even though it is installed

Hey there! Ignite CLI seems to be having a problem, eh?

What's going on?
running ignite in windows always outputs the next text
Ignite requires react-native-cli >=2.0.0 to be installed.

To install: npm i -g react-native-cli

Checking for 'react-native' npm package conflict...

And then... nothing happens, process closes. Unable to use cli in any way, and yeah I'm sure I have react-native-cli installed

npm list -g react-native-cli
C:\Program Files\nodejs
--<EMAIL_ADDRESS>

Steps to reproduce
ignite,
or
ignite new Anything,
or
ignite doctor
Everything ignite related outputs that

ignite doctor results:
Can't run it
Additional notes: running node 7.8.0 on nvm4w

Many users have reported issues when trying to use NPM with NVM, so that may be the source of the problem.

@kevinvangelder i think this is your version matching function issue
Poor programming....

@kevinvangelder NPM installed yarn and a few other things, they work as expected, nvm is not the problem or so it would seem, yet I found that the solution shown at #1007 did the trick, the sanity checks and related that use shell.exec, without quoting the path (because it includes white spaces) fail.
I'm still waiting to actually test ignite output and make sure there are no problems with nvm though, that would be for another time.

@Graren Thanks for the update. We'll be releasing a new beta version soon.


zqd api renaming: s/Packet/Pcap

Based on the decision to refer to packet captures as pcaps, replace
the parts of the zqd api that incorrectly refer to packets with pcaps.
closes #562

Should this get approved I will create a brim issue to update the client library over there.

Going to merge this after the next release is cut.

accompanying brim pr: https://github.com/brimsec/brim/pull/752


sms plugin not compatible with map_view

hello when I install  sms: "^0.0.9" with  map_view: "^0.0.12" I have this issue.
dependencies:
flutter:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^0.1.0
map_view: "^0.0.12"
sms: "^0.0.9"

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:preDebugBuild'.

Android dependency 'com.android.support:support-v4' has different version for the compile (25.2.0) and runtime (27.1.0) classpath. You should manually set the same version via DependencyResolution

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Get more help at https://help.gradle.org

BUILD FAILED in 1s
Finished with error: Gradle build failed: 1

C:\flutter\bin\flutter.bat --no-color doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, v0.2.8, on Microsoft Windows [version 10.0.16299.309], locale fr-FR)
[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[√] Android Studio (version 3.0)
[√] VS Code, 64-bit edition (version 1.21.1)
[√] Connected devices (1 available)
• No issues found!
Process finished with exit code 0

Hi,
I have pushed a new version, can you test it?

yes it's ok :) thank you


Single source generation for dev

Single source dev.

Bump jekyll-generator-single-source which adds support for dev as a version.
Add missing pages to the nav file under unlisted so they get generated but not rendered in the sidenav.

Did you sign your commit? Instructions Yes
Have you read Contributing guidelines? Yes

@fabianrbz Okay, I just tested all of the following in the single source files and everything rendered correctly:
{% if_version eq:2.1.x %}
Should display for 2.1.x eq
{% endif_version %}

{% if_version gte:2.1.x %}
Should display for 2.1.x gte
{% endif_version %}

{% if_version lte:2.1.x %}
Should display for 2.1.x lte (and probably also versions lte than 2.1.x)
{% endif_version %}

{% if_version eq:1.8.7 %}
Should NOT display for 2.1.x (it's eq 1.8.7)
{% endif_version %}

{% if_version lte:1.8.7 %}
Should NOT display for 2.1.x (it's lte 1.8.7)
{% endif_version %}

{% if_version gte:1.8.7 %}
SHOULD display for 2.1.x (it's gte 1.8.7)
{% endif_version %}

@fabianrbz one thing I see is that generated versions are single sources too which is not possible.
The generated docs are coming straight from Kuma (see this action) so we should have one folder per version and have the sidebar reference the matching version.
Also this can be done outside of this PR but it would be good as @slonka mentionned to have these part of the sidebar auto-generated.

@fabianrbz @cloudjumpercat looks like it's ready can I merge to unblock other PRs?


How to change programmatically the current displayed month in the Calendar component

Hi there.
I'm using Calendar with numberOfMonths={2} and range props for custom range selection.
I have 2 text field inputs to manually enter the start and end dates. I want to change the Calendar current month displayed to the start date month entered, but I don't see a way to do it.
I tried changing the currentDate prop, but it didn't work (I looked into the repo code later and noticed that the value is stored in a ref and is not updated afterward).

Hello @felixbores,
I am also facing this same issue.
Did you ever find a solution for this?

Hello @felixbores, I am also facing this same issue. Did you ever find a solution for this?

Hey
To be honest I don't remember if, in the end, I implemented a solution. But one way this can be achieved would be by using  key, so that if the start date changes (month or year), the key could be updated to force the component to be recreated again. I didn't test that idea, but I think it might work.

Thanks a lot for your response.
I'll try using the key.


Wikiless

A free open source alternative Wikipedia front-end focused on privacy - Wikiless - Codeberg.org
https://codeberg.org/orenom/Wikiless

Thanks for the suggestion -- added in 21646f8f29117735712179b338d566b8c73f30d8


Change Pairing.ComplementTable to pre-compute the table.

It improves the performance of RevComp, etc.  It also reduces heap pressures.
Before:
BenchmarkRevComp-56      1000000              1518 ns/op
After:
BenchmarkRevComp-56      2000000               704 ns/op
It causes the ComplementTable to return a shared table instance. All the uses found in biogo aren't affected by this change.

Please gofmt the code.

Thanks


FATAL: Error, call to 'otool' failed

Nuitka version, full Python version, flavor, OS, etc. as output by this exact command.

1.8.4
Commercial: None
Python: 3.10.13 (main, Sep 11 2023, 08:39:02) [Clang 14.0.6 ]
Flavor: Anaconda Python
Executable: /Users/louis/anaconda3/envs/cutkit/bin/python
OS: Darwin
Arch: x86_64
Version C compiler: /usr/local/opt/llvm/bin/clang (clang).

How did you install Nuitka and Python
Anaconda.

The specific PyPI names and versions

anyio==3.7.1
astor==0.8.1
attrdict==2.0.1
Babel==2.12.1
bce-python-sdk==0.8.87
beautifulsoup4==4.12.2
blinker==1.6.2
cachetools==5.3.1
certifi==2023.7.22
charset-normalizer==3.2.0
click==8.1.6
colorama==0.4.6
contourpy==1.1.0
cssselect==1.2.0
cssutils==2.7.1
cycler==0.11.0
Cython==3.0.0
decorator==4.4.2
et-xmlfile==1.1.0
exceptiongroup==1.1.2
fire==0.5.0
Flask==2.3.2
flask-babel==3.1.0
fonttools==4.42.0
future==0.18.3
h11==0.14.0
httpcore==0.17.3
httpx==0.24.1
idna==3.4
imageio==2.31.1
imageio-ffmpeg==0.4.9
imgaug==0.4.0
itsdangerous==2.1.2
Jinja2==3.1.2
kiwisolver==1.4.4
lazy_loader==0.3
Levenshtein==0.21.1
lmdb==1.4.1
lxml==4.9.2
MarkupSafe==2.1.3
matplotlib==3.7.2
moviepy==1.0.3
networkx==3.1
Nuitka==1.8.4
numpy==1.25.2
opencv-contrib-python==<IP_ADDRESS>
opencv-python==<IP_ADDRESS>
openpyxl==3.1.2
opt-einsum==3.3.0
ordered-set==4.1.0
packaging==23.1
paddle-bfloat==0.1.7
paddleocr==<IP_ADDRESS>
paddlepaddle==2.5.1
pandas==2.0.3
pdf2docx==0.5.6
Pillow==10.0.0
premailer==3.10.0
prettytable==3.9.0
proglog==0.1.10
protobuf==3.20.2
psutil==5.9.5
pyclipper==1.3.0.post4
pycryptodome==3.18.0
PyMuPDF==1.20.2
pyparsing==3.0.9
PySide6==6.5.2
PySide6-Addons==6.5.2
PySide6-Essentials==6.5.2
python-dateutil==2.8.2
python-docx==0.8.11
python-Levenshtein==0.21.1
pytz==2023.3
PyWavelets==1.4.1
rapidfuzz==3.2.0
rarfile==4.0
requests==2.31.0
scikit-image==0.21.0
scipy==1.11.1
shapely==2.0.1
shiboken6==6.5.2
six==1.16.0
sniffio==1.3.0
soupsieve==2.4.1
termcolor==2.3.0
thefuzz==0.19.0
tifffile==2023.7.18
tqdm==4.66.1
tzdata==2023.3
urllib3==2.0.4
visualdl==2.5.3
wcwidth==0.2.8
Werkzeug==2.3.6
zstandard==0.21.0

Many times when you get an error from Nuitka, your setup may be special
Always.

Provide in your issue the Nuitka options used

FATAL: Error, call to 'otool' failed: ['/usr/bin/otool', '-L', '/Users/louis/anaconda3/envs/cutkit/lib/python3.10/site-packages/paddle/libs'] -> b"error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/otool-classic: can't map file: /Users/louis/anaconda3/envs/cutkit/lib/python3.10/site-packages/paddle/libs (Invalid argument)\n".

This has no reproducer unfortunately.

demo project:
https://github.com/oliverfei/videocr-PaddleOCR.git
#example code or example.py:
from videocr import save_subtitles_to_file
if name == 'main':
save_subtitles_to_file('example_cropped.mp4', 'example.srt', lang='ch', time_start='7:10', time_end='7:34',
sim_threshold=80, conf_threshold=75, use_fullframe=True,
brightness_threshold=210, similar_image_threshold=1000, frames_to_skip=1)

I wasn't quite able to get that to run with anything from PyPI, so I assume these are conda packages. Nuitka does have detection of where a package is from in its compilation report with --report but I guess, for reporting, we kind of need something that outputs what pip freeze does, but with that information added. Right now I am to guess what kind of Anaconda config I would need to run this.

The report has be uploaded, thanks!
report.xml.zip

I think the issue caused by "otool -L" a directory, but not a file in macos.
The directory is "site-packages/paddle/libs" in which incuding some .dylib files.

I experience the same problem, on a Mac M1. Nuitka worked before. Problem started after upgrading mac to Sonomo, so maybe Mac dropped a library or something?

Installing XCODE fixes 1 problem,  but then a new problem occurs:
In file included from static_src/CompiledFunctionType.c:2785:
In file included from /Users/my_user_name/Code/my_little_project/venv/lib/python3.9/site-packages/nuitka/build/static_src/CompiledCodeHelpers.c:2097:
/Users/my_user_name/Code/my_little_project/venv/lib/python3.9/site-packages/nuitka/build/static_src/HelpersConstantsBlob.c:1183:29: error: call to undeclared function 'getsectdatafromheader_64'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    unsigned char *result = getsectdatafromheader_64(header, "constants", "constants", &size) + (uintptr_t)header;
                            ^
1 error generated.

@ideogram please don't hijack unrelated issues, and don't expect Nuitka 1.2.2 to work as well as 1.8.4 you are wasting my time

@xuqiang-idotools I noticed that it's a directory too, and it's probably some form of incompatiblity of Nuitka's dependency scan that doesn't support that, or just some garbage left by random build tools, that it's supposed to ignore. That has happened too in the past, since a directory dependency is very strange, unless of course it would be a framework.

I was probably not clear, but the report didn't yet contain the feature to provide the installer tool name, now it will say pip or conda in the distribution names on factory which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
With a new report, I should be able to get the tool to reproduce an environment from a report to support conda, and then reproduce the issue almost exactly as you see it hopefully.

The change is now on develop, and I would need a new report made with it.

This problem was temporarily circumvented by the following modifications:

I need a reproducer though, and for that it seems, I need the new report. Just let me know if you are able to provide it.

Closing for lack of feedback


Rename project name

The command name sslcert-compose is a bit long, and the inclusion of 'compose' might lead one to associate it with Docker Compose or container-related tool.
The candidates for the name change are as follows.

sslcert : https://github.com/search?q=sslcert&type=repositories
sslcert-cli : https://github.com/search?q=sslcert-cli&type=repositories
sslcertcli : https://github.com/search?q=sslcertcli&type=repositories

I have decided to rename it to sslcert-cli.


Update updating-credentials-from-the-macos-keychain.md

Cloning public repositories does not prompt for credentials.

Why:

Current documentation is not accurate.
What's being changed:

Clarify that cloning only private repositories will prompt authentication.

current: https://docs.github.com/en/github/using-git/updating-credentials-from-the-macos-keychain
staging: https://docs-3610--patch-1.herokuapp.com/en/github/using-git/updating-credentials-from-the-macos-keychain

Check off the following:

[x] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

@victorlin Thanks so much for opening a PR! I'll get this triaged for review ✨

Yes  #3861


Auto-uncollapse above minimum breakpoint width

Just curious about collapse breakpoints like .collapse-xs, .collapse-sm and  .collapse-md. I know the same result can be achieve by using the the .navbar-toggleable-xs and so on. But it doesn't feel right(i think) to use it outside .navbar component.
// Collapse breakpoint
// scss-lint:disable ImportantRule
.collapse-xs,
.collapse-sm,
.collapse-md {
  display: none;
}

.collapse {
  &-xs {
    @include media-breakpoint-up(sm) {
      display: block !important;
    }
  }
  &-sm {
    @include media-breakpoint-up(md) {
      display: block !important;
    }
  }
  &-md {
    @include media-breakpoint-up(lg) {
      display: block !important;
    }
  }
}
// scss-lint:enable ImportantRule

Feel free to close it if this already asked or not relevant.
Thanks

Do you know whether any other libraries with collapse/accordion components offer such a feature?

@cvrebert I'm not aware of that because all of my app is base on Bootstrap. Here is an example usecase.
It's more cleaner(i think) to use .collapse.collapse-{breakpoint} instead of .collapse.navbar-toggleable-{breakpoint}.
Possible for single collapse. But for accordion, i'm not sure :confused: . If you think this feature will not gonna bring any issue with accordion, it will be a great enhancement for the collapse component.
Thanks

I'll take a look at generalizing the navbar collapse stuff I've built to see if it makes sense to do this.

Not going this route given the more specific nature of these styles coming in #21390.


[TACHYON-409] Make tachyon.example a module

https://tachyon.atlassian.net/browse/TACHYON-409

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


Should we add a description column to the tables?

I am thinking about adding a description column in between the name and URL columns. It will be good for a brief summary of what the package does, but will also make the table more crowded.
What do you think?

How about:

Name
URL

ClassImpl
https://github.com/pipe01/classimpl

=>

Title
Description

ClassImpl
Like a faking library, but oriented towards dynamic modification at runtime.

I am strongly in favor of @favoyang 's proposal.
@starikcetin , I can do this if you're pressed for time right now.

I like @favoyang 's proposal as well. Let it be our new format, then.
Thank you @JimmyCushnie , please feel free to do so.

OK, I've finished doing this. I did my best to create a markdown format that keeps things nicely lined up, which has made the source file a whopping 254 characters wide.
Many of the descriptions are editorialized by yours truly. I tried to sum up the package's function more nicely than the official tagline.
I also took the liberty of removing Cinemachine, as that's now an official Unity package.


Command history

Maybe 3 panes(narrowed down targets, preview, history) and a input element are needed.
Like below.

Or

It might be better to use https://github.com/ratatui-org/ratatui.
Also, file that stores command history is needed.
I'm not sure about ratatui and skim works fine together.
It might be better to select which to focus on, the input element or the history pane on launch via config file.

TODO

[ ] Run on ratatui
[ ] Read history file on init. And store history to it.

Or it may be useful for the time being to simply sort the history so that the commands with the highest number of uses are displayed first.

https://github.com/atuinsh/atuin can be helpful for implementation of fuzzy finder.

https://github.com/kyu08/rust-playground_/blob/0d3073758b41db3de31b70a378ab19a052680517/src/main.rs#L19


[Bug]: Home Page Starts from the Bottom on Direct Load

🐞 Bug Report
Title:Home Page Starts from the Bottom on Direct Load
Description:
When the homepage is opened directly, the page scrolls to the bottom by default instead of starting from the top.
This creates a confusing experience for users, as they are automatically taken to the footer rather than seeing the intended content at the top of the page.
Steps to Reproduce:
Open the homepage directly (e.g., by refreshing the page or navigating through a link).
Notice that the page loads at the bottom instead of the top.
Expected Behavior:
The page should start from the top when opened, ensuring users see the main content first.
Additional Information:
This bug was noticed while investigating another issue related to the timer lap button (which is now resolved by someone else although it was assigned to me) #178 .
The behaviour is consistent across different browsers and can be reproduced consistently.
Suggested Fix:
Ensure that the page starts from the top upon load.
Screen Recording of the bug
https://github.com/user-attachments/assets/0c81b286-2682-4f5f-b589-adecfec142b2

@param-code
Please check the issue and assign it to me as I have already raised a Pull request for the same #227


onpointerenter, onpointerleave doesn't support currently at blazor.

Blazor (server hosted) doesn't support events onpointerenter, onpointerleave, but documentation mentioned it as supported.

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

ID: aa724f22-3a49-c7f6-1500-ac2d8dde5894
Version Independent ID: 5e8ef502-ccf9-659d-f25a-0f8f3c75f6e0
Content: ASP.NET Core Blazor event handling
Content Source: aspnetcore/blazor/components/event-handling.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @pkostaki ... Those should be supported ...
https://github.com/dotnet/aspnetcore/blob/main/src/Components/Web/src/Web/EventHandlers.cs#L75-L76
Open this for the product unit for investigation. Be sure to show your code tho ... either post the Razor component code in the issue or place it into a repro app in GH that they can pull down and run.
Please add ...
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/26194

... to the bottom of your opening comment so that I follow along. I might re-open this for doc work depending on what they say.


Double spinners

It seems odd to see 2 spinners when refreshing content on a given screen. This is not how refreshing/loading indicators work across most apps, at least on iOS, probably for the reason that refreshing content shouldn’t hide that which is already displayed.

Thanks. I think ideally the top spinner would only be used. Usually the top spinner just shows for a second and then the middle loading pane is for the real progress, so they should barely be on the screen at the same time. But good point.

Two things are happening here.

We show a generic "Loading posts..." screen, in the Webview, when loading the content within. This is due to the fact that we cannot, as far as I know, keep a loading spinner going for the "pull to refresh" – it'll only trigger quickly.

Normally you shouldn't see both at the same time.
I'm going to close this one for now. But thank you for bringing it up.


Disable animation bouncing

Possibility to have a prop to disable the rows bouncing when they are swiped or when they return to their normal position

Hey @robcalcroft I added the tension / friction props to the SwipeListView. You should be able to stop the animation by playing with those values.
Higher friction seems to do the trick. See the Spring animation here for more: https://facebook.github.io/react-native/docs/animations.html#core-api
Thanks!

As an FYI, I found
tension={-2}
friction={5}

to work well to stop the rows bouncing on their way back.


Install command-line tools pop-up on every single app open

Describe the bug
I get this pop-up every single time I start Orb Stack.

To Reproduce
Steps to reproduce the behavior:
Open Orb Stack 😂
Expected behavior
I see it once, give it permissions, and never see it again.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Attach log files by opening OrbStack's Help menu and clicking “Show Logs”, or email them for privacy.
vmgr.log
Info report
OrbStack info:
  Version: 0.14.0 (140000)
  Commit: 9a20727a93c7b42eb2e7b23cf815c2ecef334c76 (v0.14.0)

System info:
  macOS: 13.4.1 (22F2083)
  CPU: arm64, 8 cores
  CPU model: Apple M2

---------------- [ cut here ] ----------------

Please copy and paste the above information into your bug report.
Open an issue here: https://github.com/orbstack/orbstack/issues/new/choose

I think I know why — can you run ls -l /usr/local/bin?

This looks like a duplicate of #399 which should now be fixed for the next version, but it'd be great if you could run the command to confirm that it's caused by the same bug. Thanks!

"ls: /usr/local/bin: No such file or directory"
it's still the same after upgrading to v0.14.1.

@rakexue v0.14.1 has not been released yet. You can work around the bug in v0.14.0 by running sudo mkdir /usr/local/bin.

Same for me, the directory doesn't exist.

/usr/local/bin should be in your PATH by default, but OrbStack also modifies ~/.zprofile so that ~/.orbstack/bin is preferred. This isn't ideal but it currently works this way so that:

Commands work in existing shell instances immediately after installation, because /usr/local/bin was already in your path
If you don't have root or move stuff around, the preferred copies in ~/.orbstack/bin will keep working
(Only applies to Linux machines) In the future, it will be possible to "link" commands between macOS and Linux, and linked commands must be in ~/.orbstack/bin. Otherwise every link/unlink operation would require authentication.

If ~/bin or ~/.local/bin are already in your PATH, then it won't touch /usr/local/bin at all.

Fix released in v0.14.1.


test quick edit

Type: Other
Summary:
test quick edit
Details:
test quick edit
Resolution:
test quick edit
Affected definitions:

external-dns-management ae804dcb1b3a49ded12169c694130993c68ced9f

You can review the change introduced to the full definition at ClearlyDefined.


popovers: Flatten nested lists for better accessibility.

This refactors popover list structure to use a flattened ul > li structure along with aria-related additions, enabling screen reader accessibility and announcing menu length and position (# of n).
Added ARIA roles:

role="menu" to the parent <ul> element, indicating it is a widget offering a list of choices.
role="menuitem", role="menuitemcheckbox", orrole="menuitemradio" to child elements based on their function.
role="group" to the theme switcher and topic visibility switcher, identifying them as containers for related menu items.
role="none" to <li> elements, removing the implied listitem role that conflicts with the parent menu structure.

CZO Discussion

NVDA Speech Viewer Output:

Focus Mode
Browse Mode

Message Actions
scrollable content  tool tipscrollable content  regionQuote and reply > 1 of 8Message actions   MessagesMove messages M  2 of 8Delete message  3 of 8Mark as unread from here ⇧ U  4 of 8Collapse message -  5 of 8View original message E  6 of 8View read receipts ⇧ V  7 of 8Copy link to message  8 of 8
clickable  scrollable content  region    menu    menu item    Quote and reply >separator  menu item    Edit message Emenu item    Move messages Mmenu item    Delete messageseparator  menu item    Add emoji reaction :separator  menu item    Mark as unread from here⇧Umenu item    Collapse message -separator  menu item    View read receipts⇧Vmenu item    Copy link to message

Gear Menu
tool tipscrollable content  regionZulip Server dev environment  linkChannel settings  1 of 10Organization settings  2 of 10Group settings  3 of 10Personal settings  4 of 10Usage statistics  5 of 10Desktop & mobile apps  6 of 10Integrations  7 of 10API documentation  8 of 10Support Zulip  9 of 10Invite users  10 of 10
clickable  scrollable content  region    Zulip Devlocalhostlink    Zulip Server dev environmentmenu    menu item    Channel settingsmenu item    Organization settingsmenu item    Group settingsmenu item    Personal settingsmenu item    Usage statisticsseparator  menu item    Desktop & mobile appsmenu item    Integrationsmenu item    API documentationmenu item    Support Zulipseparator  menu item    Invite users

Help Menu
tool tipscrollable content  regionHelp center  1 of 6Keyboard shortcuts ?  2 of 6Message formatting  3 of 6Search filters  4 of 6About Zulip  5 of 6Contact support  6 of 6
clickable  scrollable content  region    menu    menu item    Help centermenu item    Keyboard shortcuts ?menu item    Message formattingmenu item    Search filtersmenu item    About Zulipmenu item    Contact support

Personal Menu
scrollable content  tool tipscrollable content  regionnavigation landmarkSet status  1 of 10Go invisible  2 of 10App theme  groupingSelect automatic theme  radio menu item  not checked  3 of 10Select light theme  radio menu item  not checked  4 of 10Select dark theme  radio menu item  not checked  5 of 10View your profile  6 of 10View messages with yourself  7 of 10View messages sent  8 of 10Settings  9 of 10Log out  10 of 10
clickable  scrollable content  region    navigation landmark    DesdemonaOwnermenu    8:44 AM local timeseparator  menu item    Set statusmenu item    Go invisibleseparator  App theme  grouping    Select automatic theme  radio menu item  not checked  Select light theme  radio menu item  not checked  Select dark theme  radio menu item  not checked  out of grouping  separator  menu item    View your profilemenu item    View messages with yourselfmenu item    View messages sentseparator  menu item    Settingsseparator  menu item    Log out

Topics Popover
scrollable content  tool tipscrollable content  regionMark all messages as unread  4 of 8Copy link to topic  5 of 8Move topic  6 of 8Mark as resolved  7 of 8Delete topic  8 of 8
clickable  scrollable content  region    menu    blue nas wasn't loading quicklyseparator  separator  menu item    Mark all messages as unreadmenu item    Copy link to topicseparator  menu item    Move topicmenu item    Mark as resolvedmenu item    Delete topic

Streams popover
scrollable content  tool tipscrollable content  regionChannel settings  1 of 7Pin channel to top  2 of 7Mark all messages as read  3 of 7Mute channel  4 of 7New topic  5 of 7Unsubscribe  6 of 7Change color  7 of 7
clickable  scrollable content  region    menu    Romeseparator  menu item    Channel settingsmenu item    Pin channel to topmenu item    Mark all messages as readmenu item    Mute channelmenu item    New topicmenu item    Unsubscribemenu item    Change color

Screenshots and screen captures

Popover Name
Before
After

Help Menu

Gear Menu

Personal Menu

Message Actions Menu

Stream Actions Menu

Topic Actions Menu

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

I haven't tested yet, but the changes look good on sight. Can you add before & after screenshots? Having side-by-side evidence that there's no visual changes introduced here will be a big help (though I love the comparisons of screen-reader output).

Please add the integration review label once you've added those, and I'll try to integrate this tomorrow to head off merge conflicts.

I have added the before and after screenshots. FYI @timabbott @karlstolley.
( And yes, the before and after SS are indeed different. I just matched the cursor positions a little too much. 🙂 )

Merged after fixing the above and also the commit message for topic_actions_popover: Remove redundant data-* attributes missing a description for why it's correct.
Thanks for all the work on this @sayamsamal!


Add boot diagnostics to session host template

Successfully enabled with a custom storage account. Bicep threw an error with the managed storage account option.


5.7 toolchain from 5. July reports warning if non-sendable local function is passed to a @preconcurrency marked method

Describe the bug
The Swift 5.7 toolchain from 5. July for Xcode and Ubuntu produce a new warning:
/src/Sources/NIOHTTP1Server/main.swift:234:67: warning: converting non-sendable function value to '@Sendable () throws -> ()' may introduce data races
                        context.eventLoop.scheduleTask(in: delay, doNext)

Code can be found here: https://github.com/apple/swift-nio/blob/f1d62128c4587a06bee9f5455eef282694b71288/Sources/NIOHTTP1Server/main.swift#L234
EventLoop.scheduleTask(in:_) is marked with @preconcurrency and therefore (AFAIK) should not produce a warning in 5.7 without -warn-concurrency.
Steps To Reproduce

Clone swift-nio from https://github.com/apple/swift-nio.git
open Package.swift with Xcode and build the package (or just NIOHTTP1Server)

Or with docker:
git clone https://github.com/apple/swift-nio
cd swift-nio
docker run --rm --volume "$(pwd)/:/src" --workdir "/src/" swiftlang/swift:nightly-5.7-focal swift build

Expected behavior
No warning should be emitted
Screenshots

Environment (please fill out the following information)

OS: 13.0 Beta (22A5266r)
Xcode Version 14.0 beta 3 (14A5270f) with Swift 5.7 Development Snapshot 2022-07-05 (a)

or Docker with swiftlang/swift:nightly-5.7-focal on arm64
Additional context
Didn't produce these warnings in previous 5.7 snapshots
Other issues new in the 5.7 2022-07-05 snapshot:
https://github.com/apple/swift/issues/59909
https://github.com/apple/swift/issues/59911
https://github.com/apple/swift/issues/59913

The actual issue here is that the closure to whenSuccess is known to be @Sendable based on context, but the solver itself isn't tracking that the @Sendable comes from a @preconcurrency call. This is likely to be the same problem as https://github.com/apple/swift/issues/59911.

Reduction:
struct Scheduled<T> { }

@preconcurrency
func doPreconcurrency(_: @Sendable () -> Void) { }

class EventLoop {
  @discardableResult
  @preconcurrency
  func scheduleTask<T>(deadline: Int, _ task: @escaping @Sendable () throws -> T) -> Scheduled<T> { fatalError("") }
}

class C {
  var ev: EventLoop? = nil

  func test(i: Int) {
    func doNext() {
      doPreconcurrency {
        self.ev?.scheduleTask(deadline: i, doNext)
        return
      }
    }
  }
}

Fixed in the latest 5.7 toolchain from July 17, 2022


Adding Source Code for Journey to the Moon in C++

Related Issue
Solved issue number: #281
Describe the changes you've made
Adding Source Code for Journey to the Moon problem in C++
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
C++
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] New and existing unit tests pass locally with my changes.

Please review the code ;)

Nice :)


Is keeping the same onion url on the wish list?

Also is an onion version 2 coming? Version one isn’t really safe anymore.

I released support for persistent onion addresses in v0.2.0 -- see releases. You use an @ to alias it. There's an example now in the README (the @my-app and @minecraft ones). In v0.3.0 I added a subcommand that lets you manage the service keys (oniongrok service --help for details).
In order for addresses to be persistent, oniongrok has to keep track of the services' private keys. For now, they're stored in a mode 600 file,  ~/.local/share/oniongrok by default, which you can change using the --secrets flag. I'm not super thrilled with this arrangement tbh.
I have a really strong aversion to any sort of private keys on my filesystem. I'd like to find a way to have onion keys stored in a hardware device. There are many that can do ed25519 now. A YubiKey could do it. Or maybe a Trezor? What if an eth address was also an onion? :exploding_head: This is an area of research, which might get me into Tor's internals. Should be fun!
oniongrok only uses v3 onion services. v2 are insecure and Tor doesn't even support them anymore, they're past sunset.
I'm going to mark this closed as I think it addresses your question & concern.

Even a simple recommendation to store it in a “ram disk” is some degree reasonable. However if the box is owned and you’re storing this key on the machine anywhere memory or otherwise you’re somewhat likely to assume that everything is done and dusted anyways.


Hopefully this fixes the session issues with the deployment server

Need to create an actual data folder in the same folder as application, and for the path ../data instead of /tmp

You should put a dummy file in the data folder so that it wont be ignored

I don't think it will work if you gitignore the file, to be honest it doesn't matter if its on there, shouldn't affect anything. But the path needs to be "../data" instead of just "/data", or it won't work. The idea is that the data folder should be one level up from public. As in, in the same file as public and application.

Fixed


Add query string overrides for extension loading: extraExtensions and disabledExtensions

I want a way for Thimble (or whatever hosting app) to be able to alter the set of extensions we load, either by turning some on, or turning some off.  This adds query string handling in the extension loader, which looks for extraExtensions and disabledExtensions.  If either is found, the set of default extensions is modified.
This will let us easily land extensions and test them without turing them on by default, or quickly disable a failing extension on production.

+1 Looks good, this will be very useful for user modes.

r+ w/ minor nits.


migrated device_info to device_info_plus

Goal
Device info package is discontinued. Migrate to Device info plus.
Design

For new gradle plugins, namespace is required.
A problem occurred configuring project ':device_info'.

Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

Changeset

Specify a namespace is mandatory now.
Testing

Hi @AnkitBose1472
Thank you for raising this with us.
We have added a task to investigate this further and address the issue. We don't currently have an ETA on when this could be implemented, but we will make sure to keep this thread updated.

Hi @AnkitBose1472,
We have released v1.1.0 of bugsnag-flutter-performance, in which we have replaced the dependency on device_info with the new device_info_plus package. As such we are going to close this PR out now.
Thanks again for raising this with us.


Documentation changes from 4.14 release for docs migration

PR to support documentation migration.  Content here taken from this commit.  Does not include upgrade guide changes from the same commit.

These docs have already been published for 4.14, closing this PR out.  We can re-open if we need to for some reason.


Add a try catch to getting the time tuple

@nataliejpg This was committed to the wrappers as part of your post t2 branch. Can you remember why it was needed?

oh gosh yes I remember this. It was part of the horror of trying to use the alazar branch and the newer version of qdev-dk/qcodes and for some reason the monitor started breaking and it would throw a key error here (I think it was) but whenever I did any digging I couldn't see why that would happen especially as it hadn't happened before so I just made it not care and then the monitor worked fine but this should definitely die as it was a late night; need monitor to work tomorrow change to solve exactly the sort of problems which I hope will go away when I'm not mixing and matching so many versions of things. I would just kill it and I can always redo it and record the error message so it can be fixed in a more sane way if it comes up again but I hope it won't

Closing this then. Will revisit if needed


add test coverage for contains function

This is ugly. See https://github.com/graphhopper/graphhopper/pull/1742#issuecomment-535915756


No slash ("/") in node path

Line 83 in fs-node.js
I think you forgot to add the slash between node names, therefore all the name are stuck together like this for example : "Iamanode" instead of "I/am/a/node"

Just fixed it and released a new version. Thank you


Add version command

@rubenvp8510 Since we add this nice way to package the version with the binary, I suggest to drop by default a log line when some starts this container anyway? WDYT?

@rubenvp8510 Since we add this nice way to package the version with the binary, I suggest to drop by default a log line when some starts this container anyway? WDYT?

I think that will be a good idea! I'll update the PR with that change.

@periklis Thanks for the review, I've already added the changes requested. Please give it another review when you get a chance.

@periklis Can you also review this one please? I did the same changes we agreed on the api gateway.


SQL logging during seeding

Discussed in https://github.com/loco-rs/loco/discussions/959

Originally posted by felipesere November  3, 2024
Not sure if I'm holding it wrong 🤷♂
I'm trying to move my PostsgreSQL backed app to use Sqlite (for "reasons") and my current hurdle is that I get the following error when seeding the users:
called `Result::unwrap()` on an `Err` value: DB(Json("premature end of input"))
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Is there a way to turn on SQL logging for seeding? I have it turned on in my test config but I see nothing.
It's hard to tell which column gives me grief :)

I’m on my phone so can’t check this. But given that migrations are a separate crate with its own Cargo.toml, il pretty sure we would have to turn on the logging feature in the SeaORM dependency there…
I haven’t checked if it can be turned on at the crate level and then turned back off at runtime to be able to control it from the loco config.

no worries, i'll take a look as well

I did some checking, looks like logging and its flag wiring is good. Migration crate will get an already-initialized connection from the main Loco set up, so it will share what ever configuration were given initially.
I'm wondering if configuration on your end is really in sync with what you're running. For example, if you're running tests and expect to see these logs - your test.yaml might contain different flags, and also test.yaml has different log levels. I'd start with development.yaml for this.
The error itself follows from Sqlite requiring a Z to parse properly, indeed.

closing for now, please reopen if needed


Unsure how to enable DMA interrupts

I'm working on a library (my first serious embedded project) which needs to write to a PIO FIFO continuously. I'm trying to do this with DMA, using an interrupt to re-enqueue the buffers whenever a write finishes, but I'm unsure how to enable an interrupt for a double-buffered DMA transfer in the way I would with, say, a, ADC or PWM. The documentation is a bit confusing and from what I understand some features it mentions are maybe not actually implemented?
I'm initializing DMA like this:
let transfer = unsafe {
    double_buffer::Config::new((dma.ch0, dma.ch1), &mut BITSTREAM, tx)
        .start()
        .read_next(&mut TX_BUF)
};

unsafe {
    TRANSFER_HANDLER = Some(transfer);
    BUFFERS = Some((bitstream, tx_buf));
    rp_pico::pac::NVIC::unmask(rp_pico::pac::Interrupt::DMA_IRQ_0);
}

/* unrelated code ... */

#[hal::pac::interrupt]
unsafe fn DMA_IRQ_0() {
  if let Some((transfer, bufs)) = TRANSFER_HANDLER.take().zip(BUFFERS.take()) {
      loop {
          if transfer.is_done() {
              let (tx_buf, next) = transfer.wait();
              let transfer = next.read_next(tx_buf);
              let bufs = (bufs.1, bufs.0);
              TRANSFER_HANDLER = Some(transfer);
              BUFFERS = Some(bufs);
              break;
          }
      }
  }
}

With the buffers (BITSTREAM and TX_BUF) being [u32; N] and 'tx' being the PIO FIFO.
Do you think this should work as is? Is there something I'm missing? Here's the repo for context: https://github.com/FayCarsons/cosmic-unicorn-rs, the file in question is src/cosmic_unicorn.rs
Any help at all would be deeply appreciated!!!!!

I see two issues with your code:

You busy loop within the interrupt. That doesn't look useful. Either busy loop (then you don't need an interrupt), or quickly do the needed work and return from the interrupt
The DMA interrupts are never enabled. rp_pico::pac::NVIC::unmask(rp_pico::pac::Interrupt::DMA_IRQ_0) only unmasks them in the NVIC, but that doesn't help if the DMA peripheral doesn't generate interrupts in the first place. Something like dma.ch0.enable_irq0(); dma.ch1.enable_irq0(); could help.

Sorry, I don't have a complete example available, and don't know the DMA interrupts well enough to quickly write one.
As a rough sketch, I'd try something like this (pseudocode):
fn interrupt_handler() {
  if check_irq0() && transfer.is_done() {
     [your processing here]
  }
}

check_irq0() checks if the dma interrupt is pending, and if so, clears it.
Then, transfer.is_done() is checked. If the transfer is not yet done (which would mean that the interrupt was triggered by something else - should not happen, but who knows?) the handler just returns. Note that there is no loop involved: If the DMA finishes after check_irq0() was called, the interrupt is triggered again and the handler will be called once more.
And yes, both channels need interrupts enabled, because they will be used  alternately by the double buffering transfer.


Roll chromium 	48.0.2564.82

From 48.0.2564.79

lgtm, but you need to change the hash: #3500 has landed first. I've already cherry-picked crosswalk-project/chromium-crosswalk#310 into chromium-crosswalk's master branch, so you just need to adjust chromium_crosswalk_rev.

LGTM


replace literal-include with the actual code in a code-block::python3

replace literal-include with the actual code in a code-block::python3 in the case where the file isn't used somewhere else
Python

[x] - py_source/about_py.rst
[x] - py_source/additive_functionals.rst
[x] - py_source/aiyagari.rst
[x] - py_source/amss.rst
[x] - py_source/amss2.rst
[x] - py_source/amss3.rst
[x] - py_source/arellano.rst
[x] - py_source/arma.rst
[x] - py_source/calvo.rst
[x] - py_source/career.rst
[x] - py_source/chang_credible.rst
[x] - py_source/chang_ramsey.rst
[x] - py_source/classical_filtering.rst
[x] - py_source/coleman_policy_iter.rst
[x] - py_source/debugging.rst
[x] - py_source/discrete_dp.rst
[x] - py_source/dyn_stack.rst
[x] - py_source/egm_policy_iter.rst
[x] - py_source/estspec.rst
[x] - py_source/finite_markov.rst
[x] - py_source/getting_started.rst
[x] - py_source/harrison_kreps.rst
[x] - py_source/hist_dep_policies.rst
[x] - py_source/ifp.rst
[x] - py_source/jv.rst
[x] - py_source/kalman.rst
[x] - py_source/lake_model.rst
[x] - py_source/linear_algebra.rst
[x] - py_source/linear_models.rst
[x] - py_source/lln_clt.rst
[x] - py_source/lqcontrol.rst
[x] - py_source/lqramsey.rst
[x] - py_source/lu_tricks.rst
[x] - py_source/lucas_model.rst
[x] - py_source/markov_asset.rst
[x] - py_source/markov_perf.rst
[x] - py_source/matplotlib.rst
[x] - py_source/matsuyama.rst
[x] - py_source/mccall_model.rst
[x] - py_source/mccall_model_with_separation.rst
[x] - py_source/mle.rst
[x] - py_source/multiplicative_functionals.rst
[x] - py_source/numba.rst
[x] - py_source/numpy.rst
[x] - py_source/odu.rst
[x] - py_source/ols.rst
[x] - py_source/oop_intro.rst
[x] - py_source/opt_tax_recur.rst
[x] - py_source/optgrowth.rst
[x] - py_source/orth_proj.rst
[x] - py_source/pandas.rst
[x] - py_source/pandas_panel.rst
[x] - py_source/perm_income.rst
[x] - py_source/perm_income_cons.rst
[x] - py_source/python_advanced_features.rst
[x] - py_source/python_by_example.rst
[x] - py_source/python_essentials.rst
[x] - py_source/python_oop.rst
[x] - py_source/rational_expectations.rst
[x] - py_source/rob_markov_perf.rst
[x] - py_source/robustness.rst
[x] - py_source/samuelson.rst
[x] - py_source/schelling.rst
[x] - py_source/sci_libs.rst
[x] - py_source/scipy.rst
[x] - py_source/short_path.rst
[x] - py_source/smoothing.rst
[x] - py_source/stationary_densities.rst
[x] - py_source/uncertainty_traps.rst
[x] - py_source/wald_friedman.rst
[x] - py_source/writing_good_code.rst

@natashawatkins some of these are VERY long. Do we definitely want all code in the RST?

I think this should have been done in separate PRs... I'm worried because I've made substantial edits in other PRs and I don't want them to cause merge conflicts...

I agree. let's leave this to the end and put it on hold for now.

This has been generally done across the lectures. Will close now.


Deployed Resource Cleanup

Adds the following tag/metadata/description to resources deployed by ALZ-Monitor to ensure they can effectively be cleaned up.
- Metric and Query Rule Alerts:
	○ Tag: _deployed_by_alz_monitor: true
- Policy definitions:
	○ Metadata: source: 'https://github.com/Azure/ALZ-Monitor/'
- Policy set defintions:
	○ Metadata: "source": "https://github.com/Azure/ALZ-Monitor/"
- Policy assignments:
	○ Metadata: _deployed_by_alz_monitor: true
    - Policy assignment role assignments:
            ○  Description contains '_deployed_by_alz_monitor'

Adds the script src\scripts\Start-ALZMonitorCleanup.ps1 to execute the cleanup. The script uses Resource Graph to gather resources across all accessible Management Groups for removal. Includes -WhatIf and -ReportOnly functionality for dry runs and evaluation.

@jfaurskov My fork of the repo seems to have become disassociated with the main project--perhaps because I added Mahesh and Sacha with access? I think I need to close this PR and open a new one from a new fork. I did make some changes following feedback...

@mbrat2005 as we've just gone public with the repo one of the side effects is it breaks your fork so you will need to re fork i'm afraid

Created a new PR from a new fork (required after alz-monitor went public). See: https://github.com/Azure/alz-monitor/pull/139

Thanks Paul, I recreated the PR from a new fork and closed the old one.

From: Paul Grimley @.>
Sent: Thursday, April 27, 2023 14:44
To: Azure/alz-monitor @.>
Cc: Matthew Bratschun @.>; Mention @.>
Subject: Re: [Azure/alz-monitor] Deployed Resource Cleanup (PR #114)
@mbrat2005https://github.com/mbrat2005 as we've just gone public with the repo one of the side effects is it breaks your fork so you will need to re fork i'm afraid
—
Reply to this email directly, view it on GitHubhttps://github.com/Azure/alz-monitor/pull/114#issuecomment-1526416522, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGBW6WDWLYD7IH342TGX663XDLLBBANCNFSM6AAAAAAWMBPPHA.
You are receiving this because you were mentioned.Message ID: @.***>


Camera status update is not working

Need help with this one. The app has an "Update" button on a camera page - when it's clicked the temperature of the sensor is updated. None of known endpoints does that - temperature is always taken from cache by sync module. Need to sniff mobile app https traffic and find out what the endpoint is.

so I set up mitmproxy to try to help out on this.  I can't seem to get Blink to connect through the proxy -- probably some cert pinning?  All of my other SSL android apps will pass traffic through the proxy, but Blink just spins when the app loads and the proxy doesn't report any traffic.
If you have Blink running on a proxy let me know and I'll try to help out further with reverse engineering.

Another approach could be to use strings to scan the apk for rest endpoints, then hit those using curl

➜  blink-apk strings classes.dex|grep -i immedia-semi
.immedia-semi.com/
 http://apphelp.immedia-semi.com/
 https://rest.%s.immedia-semi.com
Qhttps://rest.{tier}.immedia-semi.com//network/{network}/command/{command}/update/
,https://rest.{tier}.immedia-semi.com/account
=https://rest.{tier}.immedia-semi.com/account/change_password/
4https://rest.{tier}.immedia-semi.com/account/delete/
<https://rest.{tier}.immedia-semi.com/account/reset_password/
3https://rest.{tier}.immedia-semi.com/account/update
;https://rest.{tier}.immedia-semi.com/api/v1/account/options
Hhttps://rest.{tier}.immedia-semi.com/api/v1/account/resend_verification/
Ahttps://rest.{tier}.immedia-semi.com/api/v1/account/video_options
8https://rest.{tier}.immedia-semi.com/api/v1/camera/usage
?https://rest.{tier}.immedia-semi.com/api/v1/fw/app/update_check
Whttps://rest.{tier}.immedia-semi.com/api/v1/network/{network}/camera/{camera}/calibrate
`https://rest.{tier}.immedia-semi.com/api/v1/network/{network}/camera/{camera}/temp_alert_disable
_https://rest.{tier}.immedia-semi.com/api/v1/network/{network}/camera/{camera}/temp_alert_enable
Ghttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/programs
Nhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/programs/create
Xhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/programs/{program}/delete
Yhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/programs/{program}/disable
Xhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/programs/{program}/enable
Xhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/programs/{program}/update
Fhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/
Ohttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/activate/
Jhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/add/
Qhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/deactivate/
Lhttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/update
Whttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/{siren}/activate/
Thttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/{siren}/delete
Thttps://rest.{tier}.immedia-semi.com/api/v1/networks/{network}/sirens/{siren}/update
3https://rest.{tier}.immedia-semi.com/api/v1/sirens/
3https://rest.{tier}.immedia-semi.com/api/v1/version
<https://rest.{tier}.immedia-semi.com/api/v2/account/register
1https://rest.{tier}.immedia-semi.com/api/v2/login
Vhttps://rest.{tier}.immedia-semi.com/api/v2/network/{network}/camera/{camera}/liveview
Phttps://rest.{tier}.immedia-semi.com/api/v2/network/{network}/sync_module/{type}
8https://rest.{tier}.immedia-semi.com/api/v2/notification
=https://rest.{tier}.immedia-semi.com/api/v2/support/ob_phone/
:https://rest.{tier}.immedia-semi.com/api/v2/videos/changed
9https://rest.{tier}.immedia-semi.com/api/v2/videos/delete
>https://rest.{tier}.immedia-semi.com/api/v2/videos/page/{page}
Ihttps://rest.{tier}.immedia-semi.com/api/v3/accounts/{account}/homescreen
5https://rest.{tier}.immedia-semi.com/app/logs/upload/
+https://rest.{tier}.immedia-semi.com/logout
,https://rest.{tier}.immedia-semi.com/logout/
0https://rest.{tier}.immedia-semi.com/network/add
:https://rest.{tier}.immedia-semi.com/network/{network}/arm
Ahttps://rest.{tier}.immedia-semi.com/network/{network}/camera/add
Fhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}
Mhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/config
Nhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/delete/
Nhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/disable
Mhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/enable
Nhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/signals
Mhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/status
Phttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/thumbnail
Mhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/update
Mhttps://rest.{tier}.immedia-semi.com/network/{network}/camera/{camera}/{type}
>https://rest.{tier}.immedia-semi.com/network/{network}/cameras
Hhttps://rest.{tier}.immedia-semi.com/network/{network}/command/{command}
Mhttps://rest.{tier}.immedia-semi.com/network/{network}/command/{command}/done
Shttps://rest.{tier}.immedia-semi.com/network/{network}/command/{command}/terminate/
Phttps://rest.{tier}.immedia-semi.com/network/{network}/command/{command}/update/
=https://rest.{tier}.immedia-semi.com/network/{network}/delete
=https://rest.{tier}.immedia-semi.com/network/{network}/disarm
Ahttps://rest.{tier}.immedia-semi.com/network/{network}/homescreen
Vhttps://rest.{tier}.immedia-semi.com/network/{network}/syncmodule/{syncmodule}/delete/
Bhttps://rest.{tier}.immedia-semi.com/network/{network}/syncmodules
=https://rest.{tier}.immedia-semi.com/network/{network}/update
=https://rest.{tier}.immedia-semi.com/network/{network}/{type}
-https://rest.{tier}.immedia-semi.com/networks
,https://rest.{tier}.immedia-semi.com/regions
6https://rest.{tier}.immedia-semi.com/regions?locale=US
/https://rest.{tier}.immedia-semi.com/ujet/sign/
)https://rest.{tier}.immedia-semi.com/user
➜  blink-apk

Yeah, they check for the certificate in their code. I wasn't able to sniff the traffic because of that. But(!) I disassembled the apk and found the right endpoint - POST to /status. It's already in the latest build ;) Thanks for your help @tonymet !


[BUG] Fugue SQL does not handle valid Pandas Column names

Minimal Code To Reproduce
mydf1 = pd.DataFrame([{"a":1, "c":2},{"a":10, "c":20},{"a":11, "c":22}]
mydf2 = pd.DataFrame([{"a-b":1, "c":2},{"a-b":10, "c":20},{"a-b":11, "c":22}]

This works
SELECT *
FROM mydf1
PRINT

This does not
SELECT *
FROM mydf2
PRINT

Due to the - in the Column name
I am guessing there are multiple others too (spaces, ~, other characters that work as pandas column names)

Describe the bug
Not handling certain (valid in Pandas) characters in column names
Expected behavior
Handle the column names, consider using backticks as SQL does
Environment (please complete the following information):

Backend: pandas

Sure, closed per request