Update s3-utils to 0.1.198 in scala-steward-dependencies

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "uk.gov.nationalarchives", artifactId = "s3-utils" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "uk.gov.nationalarchives", artifactId = "s3-utils" }
}]

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

Superseded by #468.


Replace 'binary' encoding with 'utf8' for packets

This fixes failure to resolving qbs projects.
JSON encoder and decoder always expect UTF-8 encoded string.
Moreover, 'binary' encoding is deprecated.

Many thanks.


How to feed box tracking calculator with bitmap frames and get results in Android Mediapipe

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Android 11
MediaPipe Tasks SDK version
No response
Task name (e.g. Image classification, Gesture recognition etc.)
Box Tracking
Programming Language and version (e.g. C++, Python, Java)
Kotlin
Describe the actual behavior
Hello!

I've built AAR for Mediapipe box tracking and integrated to my Android application.
This application already has functions to read every frames of RTSP, Phone camera and videos within Gallery for detecting specific objects from them.
Now what I want is to feed the tracking engine with these frames and get results(boxes).
I've been trying to figure out that for 2 days but what I've done so far is the following.

val imagePacket: Packet = packetCreator.createRgbaImageFrame(rgbFrameBitmap)
   try {
      if (imagePacket.isEmpty == false) {
          processor.graph.addConsumablePacketToInputStream(
              INPUT_VIDEO_STREAM_NAME,
              imagePacket,
              java.lang.System.currentTimeMillis()
          )
      }
      imagePacket.release()
   } catch(e: java.lang.Exception) {
       e.printStackTrace()
}
Besides, this code occurs error "Graph is not started because of missing streams".

Also, I'm not sure how to set INPUT_VIDEO_STREAM_NAME properly.
According to the examples, for hand tracking, "hand_landmarks" is used, etc.
Where can I get the available values for this input/output stream names?
Thank you in advance!

Describe the expected behaviour
Feed bitmap frames to the tracking engine and get results.

Standalone code/steps you may have used to try to get what you need
val imagePacket: Packet = packetCreator.createRgbaImageFrame(rgbFrameBitmap)
   try {
      if (imagePacket.isEmpty == false) {
          processor.graph.addConsumablePacketToInputStream(
              INPUT_VIDEO_STREAM_NAME,
              imagePacket,
              java.lang.System.currentTimeMillis()
          )
      }
      imagePacket.release()
   } catch(e: java.lang.Exception) {
       e.printStackTrace()
}

Other info / Complete Logs
No response

@devveteran,
We have completely ended support of Box Tracking solution as noted here. However, the libraries, documentation, and source code for all the MediapPipe Legacy Solutions will continue to be available in our GitHub repository and through library distribution services, such as Maven and NPM.
You can continue to use those legacy solutions in your applications if you choose But We are not providing support on it.
Thank you!

@devveteran have you solved this problem? I'm running face detector, but rtsp stream is really slow compared to device camera. ~1000ms to ~100ms.


Type-review get_attribute; add wrapper function for typed optional-st…

…ring retrieval

@fabrizio-turchi - This PR introduces a pattern to identify places where a [0..1] cardinality string property is retrieved by, ultimately, your get_attribute function.  To convince us, via the type system, that only a single string is returned instead of the half-dozen type options JSON can return, I introduced a wrapper function and applied it in the one spot where it was called by a type-reviewed function.
There are a few dozen spots where get_attribute could be replaced with this pattern, but each should be spot-checked against the ontology to confirm the property cardinality is [0..1].
So, before anyone takes the step of applying this function replacement, would you mind confirming this seems like a good direction?

Yes, it seems in the right direction!


Test behavior when merging branch with major version bump

Ensure that in the following scenario:

master branch has vN in package.json
next branch has v(N+1) + prerelease string in package.json
PR is opened to merge next branch into master

We should be able to label the PR with "release-current", and the workflow will strip off the prerelease string from the v(N+1) version.

This worked as expected for Zowe V3 😁


Discover devices over the network [WiP]

I selected the wrong base when creating the PR.

Closes #174 #228

I'm sorry @hrueger I forgot again to remove debug lines... 😄

Never mind ;-)


Missing Grpc endpoint to validate phone verification code

Using the zitadel grpc management api implementation is possible via ImportHumanUser to create a new user requesting the phone verification by setting the IsPhoneVerified bool to false. Its also possible to resend the phone verification code using the call ResendHumanPhoneVerification, however I don't seem to find any call that I can use to actually verify the receiving code by the user.
Looking up in the rest api such endpoint exists in the /v2beta path prefix https://zitadel.com/docs/apis/resources/user_service/user-service-verify-phone#verify-the-phone and it works flawlessly. Such endpoint would be quite useful in the grpc implementation as well. Is there already any plan for its implementation already?
Thank you in advance

Hei @dani3lsf
The endpoint that you mention is not only a rest API, but also grpc. So I think you should be able to use it. It's just a different service. User Service instead of management Service.
https://github.com/zitadel/zitadel/blob/main/proto/zitadel/user/v2beta/user_service.proto#L217C71-L217C71
We are slowly migrating to a resource based API, where we started with the endpoints needed for beeing able to build your own login and register UI. So the user service is already from the new resource based API, while the management API, is the old one.
If you want to know more about that you can find it in the following blog: https://zitadel.com/blog/resource-api

@hifabienne thank you for the answer.
Such Grpc endpoint is however not yet incorporated in the zitadel-go package right or am I confusing stuff?

@hifabienne thank you for the answer. Such Grpc endpoint is however not yet incorporated in the zitadel-go package right or am I confusing stuff?

No I was confused 😁 Didn't realize you are asking in the zitadel-go
You are right this is not yet in there.
I think there should be a VerifyMyPhone in the auth api. As the user should verify his phone number byhimself, I guess this API should work. I think that is also the reason, why it is not in the management api.

No worries :). For now I can use the rest implementation of the v2beta path to verify the code on behalf of the user. Just to get a full picture, for the future the plan is to update the language sdks like zitadel-go with the resource based api implementation? Or will you deprecate such repos? because those are really useful.

Yes exactly. We will update the sdks in the future.


Create end user how-to file

Includes what Rob is writing about Clowder, which is aimed at the API protocols
Also should include uploading file and using data, for less technical audience

Here are two attachments to serve as an example of uploading a file via API. Both are .txt so I can attach them here, but the extensions should actually be .py and .sh respectively.
Both are configured to connect to Nebula Clowder instance, but valid username and password should be provided. Directory and filename will obviously need to be adjusted.
TERRAClowderUploadPython.txt

TERRAClowderUploadPython.py will upload file(s) to Nebula Clowder instance via API. One can specify multiple images in a directory to upload. Requires Requests 2.8.1 Python library to issue POST. Written for Python 3.x.

TERRAClowderUploadCurl.txt

TERRAClowderUploadCurl is a bash script that shows how to issue a POST in a single line using cURL, although I break out 3 strings to make modification easier here. In a windows environment cURL binaries can be found here.

@max-zilla Please add these to a /scripts/ directory in this repository. Even if this is just a first draft, it will provide versioning as well as language-aware syntax highlighting (if given .py / .sh extensions).

Just pushed to the repo with the correct file extensions.

Current plan is to collect all documentation in the terraref documentation repo. My example scripts should be integrated into that location for consistency.

dupe of #42?

Migrated from #42...
Prototype.Architecture.pptx (architecture slides from myself and @jdmaloney)

I'm going to close this since files have been created. We should create more issues in the /documentation repo as we have specific needs. I will create one to address action items from this issue -
https://github.com/terraref/documentation/issues/5


grub efi fails on latest nixos-unstable

Issue description
After upgrading bootloader breaks with
error: symbol `grub_file_filters' not found
Entering rescue mode

Steps to reproduce
Technical details

system: "x86_64-linux"
host os: Linux 4.19.44, NixOS, 19.09.git.2439b30 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2

Hi  gnidorah,
I recently had the same issue.
A nixos-rebuild switch failed with some error about a full filesystem.
In my case the cause was a full efivars partition. This left me a broken boot like you have.
This is how I restored my system:

Put the NixOS installer on a usb stick
Boot into the NixOS installer
rm /sys/firmware/efi/efivars/dump-* (don't delete anything else in that directory)
Reboot again into the NixOS installer
Mount your partitions to the correct locations in /mnt/
nixos-enter
echo 'nameserver <IP_ADDRESS>' >> /etc/resolv.conf to fix network access.
nixos-rebuild boot --install-bootloader (install-bootloader might be optional, no idea)
This command should complete successfully.
reboot

This is all I had to do. However, for now I also disabled boot.loader.efi.canTouchEfiVariables which was initially set by nixos-generate-config. I have no idea what this setting does when enabled. It might be related.
I hope this helps,
Tom

@TomSmeets Unfortunately its not the case. My config is the following:
  fileSystems."/boot/efi" =
    { device = "/dev/disk/by-uuid/58D0-2B0F";
      fsType = "vfat";
      options = [ "defaults,noauto" ];
    };
  boot.loader.efi.efiSysMountPoint = "/boot/efi";
  boot.loader.grub = {
    efiSupport = true;
    device = "nodev";
  };

So fat partition only stores
/boot/efi
└── EFI
    ├── BOOT
    │   └── BOOTX64.EFI
    └── grub
        └── grubx64.efi

3 directories, 2 files

While system partition (/boot folder) stores everything else so I never run into #23926
It worked great for year or so until I got above issue. The latest nixos-unstable that worked for me is bc94dcf500286495e3c478a9f9322debc94c4304 Perhaps its a time for bisect :disappointed:

Also a small hint. If you use recent NixOS installation usb stick, then you could boot from it, choose refind in menu, then choose bootx64 entry it will load directry to your nixos installation, so there is no real need for nixos-enter tricks

Done bisect. This is the commit that broke my layout:
https://github.com/NixOS/nixpkgs/commit/df4d0fab2f62fc1ce1d904dbbfd29e5c66da67bf
grub: 2.02 -> 2.04-rc1
cc @volth @NeQuissimus

Then the next step should be either bisecting grub or reviewing its changelog.
Probably some configuration options need to be adjusted to reflect the version update.

I have this error as well. I had to boot from a stick and rescue my system about a week ago.
I just tried today to update channels and the exact same bug popped up. Luckily I haven't shut down my machine yet. Did anybody find a fix?

Follow up:
I accidentally updated yet again and had to go through the annoying rescue process another time.
I finally just cut grub out altogether and now it boots fine.

My new boot.loader looks like:

boot.loader = {
    systemd-boot.enable = true;
    efi.canTouchEfiVariables = true;
    efi.efiSysMountPoint = "/boot";
};

nixos-install --root /mnt
Go get a coffee.

@BadDecisionsAlex
There is no need in steps 2,4 if you're booting using unstable live USB

Remove grub and fall back to the minimal loader

Sorry, but no. I want to keep EFI partition as small as possible and I also want to run garbage collection as seldom as possible. For now I just reverted commit https://github.com/NixOS/nixpkgs/commit/df4d0fab2f62fc1ce1d904dbbfd29e5c66da67bf locally
TBH I don't understand why we are pulling release candidates for such critical components as boot loaders.

@gnidorah I completely agree that our repo should roll back.
If you have other notes about my rescue process please let me know. I was just hoping to leave breadcrumbs for anybody else who bumps into the issue; but I am by no means an expert here.

2.04 released, if it is reproducible on the released version, then the fix should be somewhere in configs

@volth Once there, I will test it using following configuration https://nixos.wiki/wiki/Bootloader#Keeping_kernels.2Finitrd_on_the_main_partition

Tryed grub 2.04 locally and it didn't work too.
I'm leaving this issue open, but since there is now a solution for out of space problem for systemd-boot https://github.com/NixOS/nixpkgs/issues/23926#issuecomment-504687391 I've switched to that

I use grub on EFI and can't repro this bug.
My boot.loader.efi.canTouchEfiVariables is set to false.

I just did a fresh install on unstable (on ZFS root).
@obadz setting boot.loader.efi.canTouchEfiVariables to false initially resulted in no boot devices.
But essentially what was on the wiki worked:
  boot.supportedFilesystems = [ "zfs" ];
  boot.tmpOnTmpfs = true;
  boot.loader.systemd-boot.enable = false;
  boot.loader.efi.canTouchEfiVariables = true;
  boot.loader.efi.efiSysMountPoint = "/boot/efi";
  boot.loader.grub.efiSupport = true;
  boot.loader.grub.device = "nodev";

partition scheme
DISK=/dev/disk/by-id/<my disk>
sgdisk --zap-all $DISK
sgdisk -n2:1M:+512M -t2:EF00 $DISK
sgdisk -n1:0:0 -t1:BF01 $DISK

mkfs.vfat $DISK-part2

zpool create ...

And boot with grub efi seems to work fine

I switched yesterday from 19.03 to the 19.09-release channel on my tablet and the boot now complains with the same message. This is one of those x64 tablets that has a i686 EFI and thus requires boot.loader.grub.forcei686.
In the meantime, I'm booting via 32-bit USB grub with
configfile (hd1,3)/grub/grub.cfg

I tried the rm /sys/firmware/efi/efivars/dump-*, same result.
What does grub 2.04 offer? Couldn't it just be rolled back to 2.02 in the release-19.09 branch?

Same problem on debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931896

I fixed my boot by just moving all files in /boot and nixos-rebuild --install-bootloader switch.

I just had the same issue after switching to 19.09 and switching back to 19.03.
Timeline:

nix-channel --remove nixos
nix-channel add https://nixos.org/channels/nixos-19.09 nixos
nixos-rebuild switch
reboot now
booted fine, but there was an unrelated problem, so decided to rollback
nixos-rebuild switch --rollback
reboot now
got the error: symbol 'grub_file_filters' not found" error

I don't use EFI.

In order to avoid breaking boots on the 19.09 release, I'm in favour of rolling back to 2.02 on 19.09 before the release (but leaving 2.04 on master).
I'm unsure how to address this problem in general. A naive solution based on my incomplete understanding of the issue seems to me to have versioning for grub's module directories, e.g. have /boot/grub-2.02/x86_64-efi and /boot/grub-2.04/x86_64-efi distinct so that both versions of GRUB can work. Overall though, this seems like another case of bootloaders being hard to upgrade, a problem that @samueldr has been thinking about a fair bit iirc. Maybe you can say something about this?

Reverted to 2.02: 4eb9725, 862f05c

I can't reproduce this. Using EFI on latest master has no issues. I'm going to close this and if someone else can reproduce they can re-open and provide details for reproduction.

okay this is happening to be me right now after switching to unstable and running
sudo nixos-rebuild switch --upgrade
this is my complete configuration:
{ config, pkgs, ... }:

{
  imports =
    [ # Include the results of the hardware scan.
      ./hardware-configuration.nix
    ];
  boot.loader = {
    efi = {
      canTouchEfiVariables = true;
      efiSysMountPoint = "/boot";
    };
    grub = {
       devices = [ "nodev" ];
       enable = true;
       version = 2;
       useOSProber = true;
       efiSupport = true;
       efiInstallAsRemovable = false;
    };
  };
  networking.hostName = "gestalt"; # Define your hostname.
  networking.networkmanager.enable = true;
  networking.useDHCP = false;
  networking.interfaces.eno1.useDHCP = true;
  console.font = "Lat2-Terminus16";
  console.keyMap = "us";
  i18n.defaultLocale = "en_US.UTF-8";
  time.timeZone = "Europe/Berlin";
  nixpkgs.config.packageOverrides = pkgs: {
    nur = import (builtins.fetchTarball "https://github.com/nix-community/NUR/archive/master.tar.gz") {
      inherit pkgs;
    };
  };
  environment.systemPackages = with pkgs; [ wget vim curl git firefox python3 ntfs3g alacritty ark unzip ];
  programs.gnupg.agent = { enable = true; enableSSHSupport = true; };
  services.pcscd.enable = true;
  services.udev.packages = [
    pkgs.yubikey-personalization
    pkgs.libu2f-host
  ];
  services.openssh.enable = true;
  services.printing.enable = true;
  sound.enable = true;
  hardware.pulseaudio.enable = true;
  services.xserver.enable = true;
  services.xserver.layout = "us";
  services.xserver.xkbOptions = "eurosign:e";
  services.xserver.videoDrivers = [ "amdgpu" ];
  services.xserver.displayManager.sddm.enable = true;
  services.xserver.desktopManager.plasma5.enable = true;
  services.xserver.windowManager.i3.enable = true;
  users.users.xxxx = {
    isNormalUser = true;
    extraGroups = [ "wheel" "networkmanager" ];
    openssh.authorizedKeys.keys = [
      "ssh-rsa xxxxx"
    ];
  };
  system.stateVersion = "19.09";
}

i am currently booted into this system using the installer and refind.

@disassembler did you test on an installation that was using 2.02 before 2.04?

I've tested in a VM, starting with the following config:
{ config, pkgs, ... }: {
  imports = [ ./hardware-configuration.nix ];
  boot.loader.grub = {
    enable = true;
    efiSupport = true;
    device = "nodev";
  };
  boot.efi.canTouchEfiVariables = true;
  system.stateVersion = "19.09";
}

Installing 19.09 (grub 2.02)
Booting said 19.09
Upgrading to 20.03beta (nix-channel --add https://nixos.org/channels/nixos-20.03 && nixos-rebuild boot --upgrade)
Rebooting
Going back to 19.09 with grub installed as removable (add efiInstallAsRemovable = true; and remove canTouchEfiVariables, rm -r /boot/* && nix-channel --rollback && nixos-rebuild boot)
Rebooting
Going to 20.03beta again (nixos-rebuild boot --upgrade)
Rebooting

tl;dr, I've been unable to reproduce this. @ZerataX do you still have this problem if you upgrade to the beta or unstable again?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-03-markhor/6495/16

just tried again to upgrade to unstable and again get the grup_file_filters not found error

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/go-no-go-meeting-nixos-20-03-markhor/6495/19

That was probably already discussed somewhere, but:
Is there any problem with rolling back to 2.02 again? That version works, right?
elementary OS actually still uses 2.02 (5.1.2 release from 2020-02-07) also Fedora 31 from 2019-10-29, but even the two last debian releases use 2.04. but having a broken bootloader is worse than using older versions than debian
We could also implement this logic
IF efiSupport = true; THEN package 2.02 ELSE 2.04

True, or it could be based on stateVersion.

I just upgraded 19.09 -> 20.03 this morning and ran into this issue. I attempted to reinstall the bootloader using the little script on https://nixos.wiki/wiki/Bootloader, but no luck.
Here's my relevant config:
https://gist.github.com/emptyflask/7aa04f800321c2483574f8985e26bea0

Still trying to restore my system...
I noticed that /boot/EFI/NixOS-boot/grubx64.efi hasn't been touched -- it still has a timestamp of Mar 15 2019. Shouldn't that be replaced?

@emptyflask in case it helps:
Workaround for booting with GRUB 2.04:

Boot the NixOS installation image (or something else that has/is rEFInd) via e.g. an USB stick

Select rEFInd in the boot menu

Select Boot Fallback boot loader from EFI
Now you should see the usual GRUB boot menu (with all NixOS generations, etc.)

At least that worked for me (but: This is from my memory and online screenshots, therefore I might have missed some steps). I think these steps where posted in a related issue, but I didn't find the link again :o
Regarding the GRUB regression (2.02 -> 2.04)
The issue is most likely hardware related. E.g. in my case Boot Fallback boot loader from EFI should boot the same EFI binary as without rEFInd (but I forgot to verify that last time). So this might actually be some weird issue during the transition to GRUB during the boot process (and therefore only affecting some devices).

That actually does help, I was able to boot into my normal system using rEFInd. Thanks!

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931896#10 offers some explanation

So to summarize the issue above, there are 3 components:

the firmware (BIOS or UEFI)
the grub core image
grub modules

This boilds down to your firmware and your OS disagreeing about where the grub core image is.
The firmware points to the grub core image. The core image loads modules. The interface between core and modules is not stable.
If your OS is installing modules to location A, but your firmware is loading grub from location B, then at some point the grub version at location B is not able to load the grub modules at location A.

It does appear that there might be some duplication in /boot, maybe from attempting to use boot.loader.grub.efiInstallAsRemovable? I'm particularly wondering about /boot/EFI/NixOS-boot/grubx64.efi, nothing seems to touch it, and it's got a timestamp from a year ago.
.
├── background.png
├── converted-font.pf2
├── EFI
│   ├── Boot
│   │   └── bootx64.efi
│   ├── grub
│   │   └── grubx64.efi
│   ├── Microsoft
│   │   └── Boot
│   ├── nixos
│   │   ├── 09iivcwr1b2ijxxa4z7bcnpfjwq9cap7-initrd-linux-4.19.101-initrd.efi
│   │   ├── 502dhxra32pxv99zm63m2si006bdaijc-linux-4.19.109-bzImage.efi
│   │   ├── aqdfl1zp8d767nng5w3wh3wv54npjb8y-initrd-linux-5.4.33-initrd.efi
│   │   ├── dpp68ayvn1xmx9d8wld1fjp8ax6lz2k5-initrd-linux-4.19.109-initrd.efi
│   │   ├── h9w801h7y09a315xi7x4pskpn8y4i7xf-initrd-linux-4.19.113-initrd.efi
│   │   ├── ia4zbwrkcigbiil3vhhfwjji0gn7m9yr-linux-4.19.96-bzImage.efi
│   │   ├── jg9gfc84svh76nkj2am2jxq977bqd2k8-linux-4.19.113-bzImage.efi
│   │   ├── k7f7l104af1ny3sliwpxybzf6dy5060l-linux-4.19.101-bzImage.efi
│   │   ├── l3389n3q8cas7z5ybbwga251hwx9m6gv-initrd-linux-5.4.33-initrd.efi
│   │   ├── li3v6p9mqsspm0zgglzba2szab2zdmiv-linux-5.4.33-bzImage.efi
│   │   ├── w8yq408lfmszipyjxl9swbajjmsmkyza-initrd-linux-4.19.113-initrd.efi
│   │   └── xmknk1cjh8kgpl6j1n95a7b2fhmk7saz-initrd-linux-4.19.96-initrd.efi
│   └── NixOS-boot
│       └── grubx64.efi
├── grub
│   ├── fonts
│   ├── grub.cfg
│   ├── grubenv
│   ├── locale
│   ├── state
│   └── x86_64-efi
│       ├── core.efi
│       └── grub.efi
├── kernels
│   ├── aqdfl1zp8d767nng5w3wh3wv54npjb8y-initrd-linux-5.4.33-initrd
│   ├── jg9gfc84svh76nkj2am2jxq977bqd2k8-linux-4.19.113-bzImage
│   ├── l3389n3q8cas7z5ybbwga251hwx9m6gv-initrd-linux-5.4.33-initrd
│   ├── li3v6p9mqsspm0zgglzba2szab2zdmiv-linux-5.4.33-bzImage
│   └── w8yq408lfmszipyjxl9swbajjmsmkyza-initrd-linux-4.19.113-initrd
├── loader
│   ├── entries
│   │   └── nixos-generation-154.conf
│   └── loader.conf
└── System Volume Information

If you're not dual-booting, it should be safe to remove all of /boot (keep a backup in order to be able to reproduce the error again), then rerun nixos-rebuild boot. AFAIU, that should either (a) make everything work correctly, since the grub image will only be in one place or (b) break your boot (have your rEFInd USB stick at the ready!). The latter should only happen if either (i) both canTouchEfiVariables and efiInstallAsRemovable are set to false or (ii) your firmware is broken (disregards the boot order specified by the OS) or (iii) your firmware is not configured to use the fallback path (bootx64.efi). In any case, I'd consider removing the bad state as the right solution here.

Ok, the next time i just smash my laptop out of the window. Maybe this is faster!

@lheckemann I removed all of /boot and then nixos-rebuild boot. I am not able to boot anymore without usb. If boot with usb i stuck at grub (GNU GRUB version 2.04 Minimal BASH-line editing is supported. ...).
At this point it tried:
grub > set root=(hd1,gpt1)
'grub > linux /boot/hash-linux--bzImage.efi .... root=LABEL=NIXOS_ISO(i set this label to my usb)grub> initrd /boot/initrd-linux- .... grub> bootI end up at this problem https://github.com/NixOS/nixpkgs/issues/6265: timed out waiting for device /dev/root, trying to mount anyway.
mounting /dev/root on /iso...
mount: mounting /dev/root on /mnt-root/iso failed: No such file or directory
An error occurred in stage 1 of the boot process, which must mount the root filesystem on /mnt-root' and then start stage 2. Press one of the following keys:   r) to reboot immediately   *) to ignore the error and continue
Any ideas?

@saggzz sorry about that! Do you have either or both of canTouchEfiVariables or efiInstallAsRemovable set?
As for reinstalling: you don't have to do a totally fresh install. You can boot the installation ISO, mount the filesystems, and run nixos-install. It will rebuild the system profile and set up the bootloader etc. without wiping anything. If you pass -I nixpkgs=channel:nixos-20.03 it should directly install NixOS 20.03, even from the 19.03 installer image. The one thing you may need to do after installation is make sure that the channel is set correctly (sudo nix-channel --add https://nixos.org/channels/nixos-20.03 nixos && sudo nix-channel --update) so that you don't accidentally downgrade later.

@saggzz when I had problems with GRUB, I followed the steps here to re-install.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/nixos-grub-doesnt-see-windows/6811/4

@lheckemann thank you for the hints. Either canTouchEfiVariables nor efiInstallAsRemovable had been set. I tried to nixos-install and mount the filesystems, but no filesystems were found. This brought me to the conclusion that something was totally messed up there. I fresh installed nixos und used the  -I nixpkgs=channel:nixos-20.03 option - worked!
@asymmetric thank you, i switched to systemd-boot for now!

so I finally now have it booting normally and all I did afaik is change efiInstallAsRemovable to true
and canTouchEfiVariables to false instead of the inverse.
Seems like I can perfectly dual boot now and I'm on 20.03

I do confirm that grub2 2.04 boots NixOS in the following scenario:

nixos-version: 19.09.1320.4ad6f1404a8

{
  boot.loader.systemd-boot.enable = false;
  boot.loader.efi.efiSysMountPoint = "/boot/efi";
  boot.loader.efi.canTouchEfiVariables = false;
  boot.loader.grub.efiInstallAsRemovable = true;
  boot.loader.grub.device = "nodev";
}

zstd btrfs compression affected files: init, initrd
packageOverrides: grub2 from unstable

Notably, I was unable to boot with grub2 2.02 until adding the override. zstd compression support appeared in grub2 2.04.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/good-filesystem-for-the-nix-store/3566/10

Today I got this upgrading to 20.03. I tried a couple times following @lheckemann steps:

boot the installation ISO
mount the filesystems
run nixos-install

with no success until I removed the content of /boot(recreating it anew).
Does this kind of error happen also in unstable channels or it is solved there?

Glad to hear removing all of /boot helped. This isn't fixed anywhere because it's a bit difficult to detect — on EFI systems, where it's most likely to occur, we could check the BootCurrent EFI variable and the corresponding boot entry, then throw a warning if it doesn't match the current bootloader installation path. Someone™ would need to implement that though :)

In fact, after recreating it, I had to fix it manually (it created EFI/EFI/etc). Not sure if this is strictly related to the issue or I just messed it during attempts :)


Update Remove-SmbShare.md

Corrected syntax

Docs Build status updates of commit dfb496e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/smbshare/Remove-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit a1d89f5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/smbshare/Remove-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit c4930c4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docset/winserver2012-ps/smbshare/Remove-SmbShare.md
:white_check_mark:Succeeded

docset/winserver2012r2-ps/smbshare/Remove-SmbShare.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@dariomws306 @get-itips @tseward
Peer review needed for this PR. Thanks.


Getting error "409 - Received an unexpected response for handshake"

I have created a slack bot in GCP Kubernetes environment. The bot is written in bolt python and uses socket mode. We are running 10 pods simultaneously. Lately, we are facing the following issue -
Received an unexpected response for handshake (status: 409, response: HTTP/1.1 409 Conflict
via: envoy-wss-iad-txewoffa
date: Tue, 05 Nov 2024 19:55:36 GMT
server: envoy
connection: close
content-length: 0, session id: 6414fcdf-e0c8-4cc3-913b-94e05d6f2904)

Could you help me understand what the issue is and how to resolve it

Hi @PrajwalNaik07, thanks for taking the time to report this. This is a known issue on the API server side, and this is the latest status: ahttps://github.com/slackapi/node-slack-sdk/issues/2094#issuecomment-2483179967 Please subscribe to the issue thread to receive more updates to come.

Thank you for being patient with this issue. Upgrading slack-sdk 3.33.4 should resolve it: https://github.com/slackapi/python-slack-sdk/releases/tag/v3.33.4

Sorry, never mind about the above comment


The References field is null when adding a schema

HI @xnuinside
First of all, I just wanted to tell you how amazing this parser is. I was testing the parser and noticed that the references fields in the Json output returns a value of "none" when adding a schema name to the table. For example if added the following values after REFERENCES, not returns:
other_schema.other_table
"other_schema".other_table
However, if just add the table name other_table, the references field does produce an out. Below is an example of the code that will reproduce the issue.
from simple_ddl_parser import DDLParser

parse_results = DDLParser("""

 create table prod.super_table
(
    data_sync_id bigint not null default 0,
    id_ref_from_another_table int REFERENCES other_schema.other_table (id) --- this will product a null output.
    primary key (data_sync_id, sync_start)
);

);

""").run()

print(parse_results)

@geob3d, thank you for the feedback! I will fix it today and release new version little bit later :) you correct, I did not add schema support to references, need to fix it

@geob3d, I added support - https://github.com/xnuinside/simple-ddl-parser/pull/2, I plan to do several more things today and will release 0.4.0 with updates

@geob3d fix was released in 0.4.0 version, pls check

Hi @xnuinside
I just tested the changes on 0.4.0.  The schema support for references works as expected. I love the addition of the alter table statement to the parser.
Thank you for the hard work as the project.  This parser is one of the best I've seen so far.

@geob3d  thank you :)


update heytech to 0.2.0 in stable

Is already user feedback there or is it a hotfix?

There are only 2 users, one has done the last changes and the other give me feedback that it works perfect.

Thank you


fix non-deterministic test

add .gitignore
add pry as dev dep
fix the test which was intermittently failing.  Traced this to finagle-thrift method should_sample? method which had a rand in it.  Stubbed it out.

LGTM


Check if --alertmanagers.url is configured in rule

This case is use to ensure we have --alertmanagers.url configured in rule. we found that it is broken by upstream code changes.
Signed-off-by: clyang82<EMAIL_ADDRESS>

/assign @songleo


Zeus Namespace Rspec

Zeus can't find Rspec class when using Rspec's shared examples feature. It looks like spec_helper.rb drops the Rails class.
Edited
Worked Around it by...
Added
require 'rspec/rails'
to spec_helper.rb
https://github.com/burke/zeus/issues/474
Edited #2
The workaround is causing a new error.
uninitialized constant ActionView::Template::Handlers::ERB::ENCODING_FLAG (NameError)
Work around to that.
http://stackoverflow.com/questions/4429068/getting-an-unitialized-constant-error-with-rspec-have-no-idea-whats-causing-it
require 'rails/all'

Not sure the 2nd part is really a zeus issue, shouldn't require 'rails/all' be what you do? Sorry if I'm confused here but at least this is what I have in my apps, unless I explicitly require only parts of rails.
For the first part, this is really not nice, but I think the best way to fix this is some documentation for now, I find it awkward how rspec generates the helper in a way which makes it dependent on the Rspec being defined before the helper is loaded, but I guess it is how it is, as there is already issue #474 to keep track of this I would close this for now, feel free to reopen if you think there is a difference to #474


Added NOBEL.cpp

Question Link: https://www.codechef.com/submit/NOBEL

Kindly add the relevant labels and then merge the pull request.
Thank you, Happy Hactober :)

Good job, Happy Hacktober!


Add support for nREPL 0.6.0

nREPL now has the set!-able dynamic var nrepl.middleware.print/*print-fn* so tools like Whidbey can set a session-wide default printer, but clients can still override this on a per-request basis by including the relevant option in the request.
To be able to set! this, we need to switch from using :init to :custom-init. The former is evaluated only once when the REPL server starts, but the latter is evaluated each time a new client session is created (with set!-able bindings in place).
I have left the :nrepl-context code in place so nREPL 0.5.x still works.
Additionally, because of technomancy/leiningen#878, there's a bit of a sharp edge around using :init or :custom-init – they aren't merged in the way you might expect. Instead splice any existing form into our init code and overwrite the existing configuration with ^:replace.
Fixes #27.

@cichli to be more explicit about next steps - I think this is mergeable, but I'd like to understand the answers to my two questions above. In particular, it'd be nice not to have the extra newline in the new approach, but if it turns out to be too difficult we can move forward with this.

Sorry for the delay in coming back to this @greglook. I've pushed a new version and addressed your inline comments above.

I gave this a shot with leiningen 2.9.0 and can confirm that it pretty-prints now, but I also note that it's printing an additional newline that wasn't present before. render-str was returning newline-trimmed strings, whereas pprint output has a trailing newline.

This is tricky (but not impossible) when nrepl.middleware.print/*stream?* is true, and I didn't want to introduce any difference in rendered output between setting that on or off. It's also possible that some *print-fn* adds whitespace at the end intentionally, so it might be surprising if it were all unconditionally trimmed. I wonder if this could be solved more naturally in the client? It only needs to add a newline before the prompt if the current line isn't blank.

Pushed again with a fix for find-ns pointed out by @johannesloetzsch.

I wonder if this could be solved more naturally in the client? It only needs to add a newline before the prompt if the current line isn't blank.

Yeah, this feels like the right behavior to me. I'm thinking of the behavior of shells like zsh, which will render an extra newline before the prompt when needed. For now this can ship with some extra line spacing. 🤷♂

Thanks! 🙌


better npath complexity documentation with example

Type: documentation update
Breaking change: no
A long time ago I wrote a blog post on the topic which is very popular. I was asked to make a PR to update this documentation to clarify npath complexity a bit. So here it is, short and sweet!

Very nice expansion :+1:

@modess thanks for the addition, your blogpost is a very good to read 👍

@tvbeek thank you! Guess I have to update the post now, removing the part where I say the documentation sucks :joy:


searchkit/constraints: rewrite of binary search algorithm

Implemented a new binary search algorithm that no longer needs filemarkers or knowing the lines beforehand, which reduces the time spent applying a SearchConstraintSearchSince to a file, especially if the file is large in size.
Removed the following classes which are no longer necessary:

SkipRange
SkipRangeOverlapException
BinarySearchState
FileMarkers (and respective unit tests)
SeekInfo

Removed test_logs_since_junk_not_allow_unverifiable test case since we're no longer parsing all lines in the file.
Removed following functions from BinarySeekSearchBase:

_seek_and_validate
_check_line
_seek_next

Introduced the following new classes:

LogFileDateSinceOffsetSeeker (the main binary search class)
DateSearchFailedAtOffset (exception type)
NoLogsFoundSince (exception type)
NoDateFoundInLogs (exception type)

@dosaboy pinging you just in case you might have missed this one

@mustafakemalgilor apologies i had missed this. i will try to dedicate some time to testing it.

Some initial observations. I definitely prefer the approach of bisecting without having to rely on markers as that will save a lot of time and resources. I ran it against a sosreport (using hotsos) with lot of log history and I hit some exceptions e.g.
.. code-block:: console
Traceback (most recent call last):
  File "/home/user1/git/dosaboy/searchkit/searchkit/search.py", line 1039, in execute
    fd.read(1)
  File "/usr/lib/python3.10/gzip.py", line 301, in read
    return self._buffer.read(size)
  File "/usr/lib/python3.10/_compression.py", line 68, in readinto
    data = self.read(len(byte_view))
  File "/usr/lib/python3.10/gzip.py", line 488, in read
    if not self._read_gzip_header():
  File "/usr/lib/python3.10/gzip.py", line 436, in _read_gzip_header
    raise BadGzipFile('Not a gzipped file (%r)' % magic)
gzip.BadGzipFile: Not a gzipped file (b'20')

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/user1/git/dosaboy/searchkit/searchkit/search.py", line 1044, in execute
    stats = self._run_search(fd)
  File "/home/user1/git/dosaboy/searchkit/searchkit/search.py", line 976, in _run_search
    offset = self.constraints_manager.apply_global(search_ids, fd)
  File "/home/user1/git/dosaboy/searchkit/searchkit/search.py", line 1140, in apply_global
    _offset = c.apply_to_file(fd)
  File "/home/user1/git/canonical/hotsos/hotsos/core/search.py", line 63, in apply_to_file
    return super().apply_to_file(*args, **kwargs)
  File "/home/user1/git/dosaboy/searchkit/searchkit/constraints.py", line 705, in apply_to_file
    result = seeker.run()
  File "/home/user1/git/dosaboy/searchkit/searchkit/constraints.py", line 550, in run
    bisect.bisect_left(self, self.constraint._since_date)
  File "/home/user1/git/dosaboy/searchkit/searchkit/constraints.py", line 496, in __getitem__
    ) = self.try_find_line_w_date(item)
  File "/home/user1/git/dosaboy/searchkit/searchkit/constraints.py", line 370, in try_find_line_w_date
    raise ValueError("Could not find ending line feed offset")
ValueError: Could not find ending line feed offset

I didnt go through them all yet but I suspect they were a result of invalid characters being hit during searches (i remember having to do some .decode('unicode_escape') to get around this kind of thing).
Another thing I notice it that this implementation will always result in a full bisect, even if the first line in the file is valid or last line is invalid. The existing code will do a pre-check of the first and last lines to avoid this which would save further time.
Regarding the code changes themselves, it is quite hard to debug due to high use of abbreviated var names for which it isnt immediately obvious what they refer to. That combined with the very complex returns from methods makes it even harder. I think if you can implement a class to represent the state returned by try_find_line_w_date() and pass that around as an object it would really help. Nice work though!

Hi Ed, thanks for the review, much appreciated!

Some initial observations. I definitely prefer the approach of bisecting without having to rely on markers as that will save a lot of time and resources. I ran it against a sosreport (using hotsos) with lot of log history and I hit some exceptions e.g.

Can you send me an example sosreport? hotsos's test suite is all green with the latest revision of this branch, so I'd like to add a test for whatever making this fail.

Another thing I notice it that this implementation will always result in a full bisect, even if the first line in the file is valid or last line is invalid. The existing code will do a pre-check of the first and last lines to avoid this which would save further time.

Well, I don't know what "valid" stands here for but the new algorithm will find the nearest valid line if it lands on an "invalid" line, e.g.:
01.01.1970 foo
01.01.1970 bar
nodate

Assuming that the lookup hits line "nodate", the algorithm will yield the previous valid line, "01.01.1970 bar". This is in place due to the fact that some logs span multiple lines, for example:
2019-04-04T14:47:35.023075Z 0 [Note] WSREP: Current view of cluster as seen by this node
view (view_id(PRIM,0256ddd2,2)
memb {
	0256ddd2,0
	947dd30b,0
	}
joined {
	}
left {
	}
partitioned {
	}
)
2019-04-04T14:47:35.023099Z 0 [Note] WSREP: Save the discovered primary-component to disk

Regarding the code changes themselves, it is quite hard to debug due to high use of abbreviated var names for which it isnt immediately obvious what they refer to. That combined with the very complex returns from methods makes it even harder. I think if you can implement a class to represent the state returned by try_find_line_w_date() and pass that around as an object it would really help.

I agree, I refactored and simplified the code quite a bit, should be easier to reason about now :)

I have done some testing on sosreports with large log files and this seems to work well with even a small performance improvement. I have proposed some style consistency tweaks at https://github.com/mustafakemalgilor/searchkit/pull/2 but on the whole I think it's good!

i think this is good now, i have a branch with some tweaks and cleanups that I will apply once this is landed.


Hello, Is this project still active? Thanks

No -- monthly dumps are still going to BQ though.

Are monthly dumps still happening? I am only able to get comments from 2018-05-23 to 2018-06-26.

Yes they are. Why are you only able to get data through 06-26 though? The
entire month should be in the dumps. What files are you using?
On Wed, Aug 14, 2019 at 7:26 AM brucelangford<EMAIL_ADDRESS>wrote:

Are monthly dumps still happening? I am only able to get comments from
2018-05-23 to 2018-06-26.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pushshift/google_bigquery/issues/5?email_source=notifications&email_token=ADAFG7JLHRIQNNSSSQIADLDQEPTX7A5CNFSM4IFYZPO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4IP57Q#issuecomment-521207550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADAFG7L4H2SR3I6QWMFWFPTQEPTX7ANCNFSM4IFYZPOQ
.

--
Jason Michael Baumgartner
pushshift.io http://pushshift.io

This is my query:
SELECT author, parent_id, body, created_utc, score FROM pushshift.rt_reddit.comments
WHERE subreddit = 'investing'
GROUP BY author, parent_id, body, created_utc, score
ORDER BY created_utc
And it only returns comments between those dates. I am new to sql and bigquery, so I might be doing something wrong.

I'm seeing the same problem. I ran this query
SELECT
  MIN(DATE(created_utc)),
  MAX(DATE(created_utc))
FROM
  `pushshift.rt_reddit.submissions`

the result is :
2018-05-23 | 2018-08-27


Update installation instructions for Arch Linux

cargo-msrv is now moved to Arch Linux community repository, meaning that it can be installed with pacman:

https://archlinux.org/packages/community/x86_64/cargo-msrv/

This PR updates README.md to reflect these changes.

Thanks 🙏!
bors r+


Add BC prefix to the data from colin

Issue #: /bcgov/entity#13556
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the PPR license (Apache 2.0).

/gcbrun

hey lekshmi were you able to test loading a solr instance locally? If not I will pull this down and do a load on mine

Pulled it down and tested it -- works great

Thanks a lot for testing this Kial :)


Spatial Object Mesh Observer can't be deployed to HoloLens 2

Describe the bug
The MRTK document Configuring Observers for Editor suggests using Spatial Object Mesh Observer for testing spatial awareness while in the editor. This works, however when the application is deployed to HoloLens 2 the following error is produced:

A scripted object (probably Microsoft.MixedReality.Toolkit.SpatialObjectMeshObserver.SpatialObjectMeshObserverProfile?) has a different serialization layout when loading. (Read 64 bytes but expected 152 bytes)
Did you #ifdef UNITY_EDITOR a section of your serialized properties in any of your scripts?
(Filename: C:\buildslave\unity\build\Runtime/Serialize/SerializedFile.cpp Line: 2136)

Expected behavior
My expectation is that any service in MRTK that is designed to support the editing experience would not get deployed to the final device. If an editor-specific service is deployed to the device, I would expect that it would remain dormant and would not generate errors.
Your setup (please complete the following information)

Unity Version: 2019.2.21f1
MRTK Version: 2.4

Target platform (please complete the following information)

HoloLens 2

@davidkline-ms is this one you could take a look at? I know you were working on this system at one point.

Ah sent too soon, I'm fixing this in a way that should hopefully prevent any of these errors from a happening again in the future as well

facing the same error, it seems to be deployed to the device only on a Release build though. I don't get the error while deploying a Debug build.

#8072 was closed but not resolved. @RogPodge you interacted with a recent issue involving serialization of these profiles. Is this fixed now?

Unfortunately this is not yet fixed and is probably on hold for a bit. The error itself has does not impact or cause any functional issues on runtime to out knowledge, and properly squashing it would take quite a bit of effort to refactor our folders. Looking to revisit this during early 3.0 timeframe.

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority security issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


fastlane match installs an expired WWDRC certificate

New Issue Checklist

[X] Updated fastlane to the latest version
[X] I read the Contribution Guidelines
[X] I read docs.fastlane.tools
[X] I searched for existing GitHub issues

Issue Description

When running fastlane match to install certs/profiles from a private repo OR create new ones after nuking, an expired WWDRC cert is added to my local keychain, causing issues as cited in https://stackoverflow.com/questions/45050902/no-signing-certificate-ios-distribution-found
This occurs for match development and match appstore, whether or not the private git repo storing the encrypted certs/profiles has anything in it.
I would expect match to only install valid WWDRC certificates...
Screenshot from BEFORE running fastlane match appstore

Screenshot from IMMEDIATELY AFTER running fastlane match appstore

Command executed

fastlane match appstore
Complete output when running fastlane, including the stack trace and command used

 Command Output
% fastlane match appstore

[✔] 🚀
[18:29:51]: fastlane detected a Gemfile in the current directory
[18:29:51]: However, it seems like you didn't use `bundle exec`
[18:29:51]: To launch fastlane faster, please use
[18:29:51]:
[18:29:51]: $ bundle exec fastlane match appstore
[18:29:51]:
[18:29:51]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[18:29:52]: Successfully loaded '/Users/jhale/git/BinaryClock/fastlane/Matchfile' 📄

+-------------------+--------------------------------------+
|       Detected Values from './fastlane/Matchfile'        |
+-------------------+--------------------------------------+
| git_url           | REDACTED                             |
| storage_mode      | git                                  |
| type              | development                          |
| app_identifier    | dev.jhale.BinaryClock                |
| keychain_password | REDACTED                             |
+-------------------+--------------------------------------+

+--------------------------------------+--------------------------------------+
|                          Summary for match 2.212.2                          |
+--------------------------------------+--------------------------------------+
| type                                 | appstore                             |
| readonly                             | false                                |
| generate_apple_certs                 | true                                 |
| skip_provisioning_profiles           | false                                |
| app_identifier                       | ["dev.jhale.BinaryClock"]            |
| username                             | REDACTED                             |
| team_id                              | REDACTED                             |
| storage_mode                         | git                                  |
| git_url                              | REDACTED                             |
| git_branch                           | master                               |
| shallow_clone                        | false                                |
| clone_branch_directly                | false                                |
| skip_google_cloud_account_confirmat  | false                                |
| ion                                  |                                      |
| keychain_name                        | login.keychain                       |
| keychain_password                    | ********                             |
| force                                | false                                |
| force_for_new_devices                | false                                |
| include_mac_in_profiles              | false                                |
| include_all_certificates             | false                                |
| force_for_new_certificates           | false                                |
| skip_confirmation                    | false                                |
| safe_remove_certs                    | false                                |
| skip_docs                            | false                                |
| platform                             | ios                                  |
| derive_catalyst_app_identifier       | false                                |
| fail_on_name_taken                   | false                                |
| skip_certificate_matching            | false                                |
| skip_set_partition_list              | false                                |
| verbose                              | false                                |
+--------------------------------------+--------------------------------------+

[18:29:52]: Cloning remote git repo...
[18:29:52]: If cloning the repo takes too long, you can use the `clone_branch_directly` option in match.
[18:29:53]: Checking out branch master...
[18:29:53]: 🔓  Successfully decrypted certificates repo
[18:29:53]: Verifying that the certificate and profile are still valid on the Dev Portal...
Available session is not valid any more. Continuing with normal login.
[18:29:56]: Installing certificate...
[18:29:56]: $ security find-certificate -a -c 'Apple Worldwide Developer Relations' -p /Users/jhale/Library/Keychains/login.keychain-db
[18:29:56]: ▸ -----BEGIN CERTIFICATE-----
[18:29:56]: ▸ REDACTED
[18:29:56]: ▸ -----END CERTIFICATE-----
[18:29:56]: ▸ -----BEGIN CERTIFICATE-----
[18:29:56]: ▸ REDACTED
[18:29:56]: ▸ -----END CERTIFICATE-----
[18:29:56]: ▸ -----BEGIN CERTIFICATE-----
[18:29:56]: ▸ REDACTED
[18:29:56]: ▸ -----END CERTIFICATE-----
[18:29:56]: ▸ -----BEGIN CERTIFICATE-----
[18:29:56]: ▸ REDACTED
[18:29:56]: ▸ -----END CERTIFICATE-----
[18:29:56]: ▸ -----BEGIN CERTIFICATE-----
[18:29:56]: ▸ REDACTED
[18:29:56]: ▸ -----END CERTIFICATE-----

+-------------------+----------------------------------------------+
|                      Installed Certificate                       |
+-------------------+----------------------------------------------+
| User ID           | REDACTED                                     |
| Common Name       | Apple Distribution: Joseph Hale (REDACTED)   |
| Organisation Unit | REDACTED                                     |
| Organisation      | Joseph Hale                                  |
| Country           | US                                           |
| Start Datetime    | 2023-05-12 01:08:15 UTC                      |
| End Datetime      | 2024-05-11 01:08:14 UTC                      |
+-------------------+----------------------------------------------+

[18:29:56]: Installing provisioning profile...

+---------------------+------------------------+------------------------+
|                    Installed Provisioning Profile                     |
+---------------------+------------------------+------------------------+
| Parameter           | Environment Variable   | Value                  |
+---------------------+------------------------+------------------------+
| App Identifier      |                        | dev.jhale.BinaryClock  |
| Type                |                        | appstore               |
| Platform            |                        | ios                    |
| Profile UUID        | sigh_dev.jhale.Binary  | REDACTED               |
|                     | Clock_appstore         |                        |
| Profile Name        | sigh_dev.jhale.Binary  | match AppStore         |
|                     | Clock_appstore_profil  | dev.jhale.BinaryClock  |
|                     | e-name                 |                        |
| Profile Path        | sigh_dev.jhale.Binary  | /Users/jhale/Library/  |
|                     | Clock_appstore_profil  | MobileDevice/Provisio  |
|                     | e-path                 | ning                   |
|                     |                        | Profiles/REDACTED      |
|                     |                        | .mobileprovision       |
| Development Team ID | sigh_dev.jhale.Binary  | REDACTED               |
|                     | Clock_appstore_team-i  |                        |
|                     | d                      |                        |
| Certificate Name    | sigh_dev.jhale.Binary  | Apple Distribution:    |
|                     | Clock_appstore_certif  | Joseph Hale            |
|                     | icate-name             | (REDACTED)             |
+---------------------+------------------------+------------------------+

[18:29:57]: All required keys, certificates and provisioning profiles are installed 🙌

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
13.3.1

Ruby
3.1.4

Bundler?
false

Git
git version 2.39.2 (Apple Git-143)

Installation Source
/usr/local/Cellar/fastlane/2.212.2/libexec/bin/fastlane

Host
macOS 13.3.1 ((a))

Ruby Lib Dir
<EMAIL_ADDRESS>

OpenSSL Version
OpenSSL 3.1.0 14 Mar 2023

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
14.3

Swift Version
5.8

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

desc "Make sure to copy the `.env.dist` to `.env` and fill all values before running any lanes"

platform :ios do

  desc 'Fetch certificates and provisioning profiles'
  lane :certificates do
    match(type: 'development', keychain_password: ENV['MATCH_PASSWORD'])
    match(type: 'appstore', keychain_password: ENV['MATCH_PASSWORD'])
  end

  desc 'Build the iOS application.'
  lane :build do
    # certificates
    increment_build_number(xcodeproj: "ios/BinaryClock.xcodeproj")
    gym
  end

  desc "Publish a beta release to the App Store"
  lane :beta do
    build
    app_store_connect_api_key(
      key_id: ENV["IOS_APP_STORE_CONNECT_KEY_ID"],
      issuer_id: ENV["IOS_APP_STORE_CONNECT_ISSUER_ID"],
      key_filepath: ENV["IOS_APP_STORE_CONNECT_KEY_FILE_PATH"],
    )
    pilot
  end

end

platform :android do

  desc "Build the Android application."
  lane :build do
    gradle(task: 'clean', project_dir: 'android/')
    gradle(task: 'bundle', build_type: 'Release', project_dir: 'android/')
  end

  desc "Publish an internal release to the Play Store"
  lane :internal do
    build
    supply(track: 'internal', track_promote_to: 'internal')
  end

  desc "Publish a alpha release to the Play Store"
  lane :alpha do
    build
    supply(track: 'alpha', track_promote_to: 'alpha')
  end

  desc "Publish a beta release to the Play Store"
  lane :beta do
    build
    supply(track: 'beta', track_promote_to: 'beta')
  end

  desc "Publish a production release to the Play Store"
  lane :production do
    build
    supply(track: 'production', track_promote_to: 'production')
  end

end

`./fastlane/Appfile`
# iOS
app_identifier("dev.jhale.BinaryClock") # The bundle identifier of your app
apple_id(ENV["IOS_APPLE_ID"]) # Your Apple Developer Portal username

itc_team_id(ENV["IOS_ITC_TEAM_ID"]) # App Store Connect Team ID
team_id(ENV["IOS_TEAM_ID"]) # Developer Portal Team ID

# Android
json_key_file(ENV["ANDROID_GOOGLE_PLAY_JSON_KEY_FILE_PATH"]) # Google Play Console Credentials
package_name("dev.jhale.binaryclock") # Google Play App Identifier

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.212.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.3.0

did_you_mean
1.6.1

atomos
0.1.3

rexml
3.2.5

CFPropertyList
3.0.6

claide
1.1.0

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.22.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

plist
3.7.0

public_suffix
5.0.1

addressable
2.8.4

multipart-post
2.0.0

word_wrap
1.0.0

optparse
0.1.1

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

artifactory
3.0.15

babosa
1.0.4

colored
1.2

highline
2.0.3

commander
4.6.0

excon
0.99.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

gh_inspector
1.1.3

mini_magick
4.12.0

naturally
2.2.1

rubyzip
2.3.2

security
0.1.3

xcpretty-travis-formatter
1.0.1

dotenv
2.8.1

bundler
2.4.10

simctl
1.6.10

jwt
2.7.0

uber
0.1.0

declarative
0.0.20

trailblazer-option
0.1.2

representable
3.2.0

retriable
3.1.2

mini_mime
1.1.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.5.2

httpclient
2.8.3

webrick
1.8.1

google-apis-core
0.11.0

google-apis-playcustomapp_v1
0.13.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.1

google-cloud-core
1.6.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.19.0

rake
13.0.6

digest-crc
0.6.4

google-cloud-storage
1.44.0

emoji_regex
3.2.3

set
1.0.2

json
2.6.3

google-apis-androidpublisher_v3
0.41.0

aws-eventstream
1.2.0

aws-sigv4
1.5.2

aws-partitions
1.760.0

jmespath
1.6.2

aws-sdk-core
3.171.1

aws-sdk-kms
1.64.0

aws-sdk-s3
1.122.0

forwardable
1.3.2

logger
1.5.0

pathname
0.2.0

shellwords
0.1.0

cgi
0.3.6

date
3.2.2

timeout
0.2.0

stringio
3.0.1

securerandom
0.2.0

uri
0.12.1

openssl
3.0.1

digest
3.1.0

io-nonblock
0.1.0

ipaddr
1.2.4

io-wait
0.2.1

zlib
2.1.1

resolv
0.2.1

time
0.2.2

open-uri
0.2.0

mutex_m
0.1.1

net-http
0.3.0

net-protocol
0.1.2

ostruct
0.5.2

english
0.7.1

erb
2.2.3

strscan
3.0.1

abbrev
0.1.0

io-console
0.5.11

tempfile
0.1.2

delegate
0.2.0

fileutils
1.6.0

tmpdir
0.1.2

base64
0.1.1

singleton
0.1.1

open3
0.1.1

nkf
0.1.1

prettyprint
0.1.1

pp
0.3.0

find
0.1.1

yaml
0.2.0

psych
4.0.4

generated on: 2023-05-11

We're having the same issues. It seems to me that this certificate is the culprit:
{     alias: 'G1',     sha256: 'ce057691d730f89ca25e916f7335f4c8a15713dcd273a658c024023f8eb809c2',     url: 'https://developer.apple.com/certificationauthority/AppleWWDRCA.cer'   },
Also it is no longer listed on the Apple PKI site

We’re having the same issue. Looks like the SHA-256 of the expired certificate as shown in Keychain Access matches the one listed here:
https://github.com/fastlane/fastlane/blob/b3ae1b07c80d0a3355078f894f20131960711ea7/fastlane_core/lib/fastlane_core/cert_checker.rb#L9-L13

I’ve opened a PR #21271 to remove the certificate.
I originally found this issue looking for a solution for our expired App Store certificates not getting updated by Match, and I thought this might somehow be related. Unfortunately removing the G1 certificate did not fix this issue, but we worked around it by just deleting the "appstore" folder from the Match repo and running Match again. I just wanted to leave this here in case someone else is seeing the same.

Ok, good job.
I'm finishing up an PR that'll have the cert-checker validate the expiry, and only installing the certificate if it passes

Nice, thank you.

I've added an PR with a check. Any help with re-writing/adding specs is really appreciated.


Add platform variant to image inspect

Hi,
I tried to look up the variant property on images where this value is set and it failed. When looking into it I saw that it was missing in the library. So here you get a PR. :wink: I also added a test case to verify the change.
Thanks for your efforts on this project. It's truly awesome!

This awesome project is largely done by contributors (I think the ratio of contributors/users is quite high judging by the numbers haha), so thank you for your efforts on this project :)


JBDS-3889 Remove JBoss from Platform Installer full name

Fix updates name to 'Red Hat Developer Studio PLatform Installer'

npm install fails with error "Error: Cannot find module 'electron'" on CI host local build works fine

Something interrupted the electron-prebuild download so the unit tests failed. As for the UI tests the path is currently hardcoded in the protractor config and I assume it needs adjusting. Could you do that as well?

@jrichter1 thanks for pointing that out :) haven't run ui-tests.

pr updated and all checks are good.


Style updates

I've had good results with this branch so far. As mentioned in your PR, there are some touch-ups to do on the styling. Here is what I think so far.
I thought the multiline toolbar buttons made sense to keep at the top right instead of split. This way if you have a large output you still have easy access to each button.
Here is a gif of how this looks on the atom-light theme:

And in atom-dark:

One issue I'm a bit stuck on is how to get json transform output to use the active atom theme for styling. I think this styling is being imported from @nteract/transforms, but I'm not sure what to do about it. Possibly add a no theme argument or maybe just unset the styling somehow.

@BenRussert Thanks a lot for taking a look at this branch.
Just a quick note upfront: Atom Dark is the old default which was replaced with One Dark and One Light which is probably the theme most users use. I think we should probably use it as a reference for styling.
For me personally this kind of styling looks a bit too prominent and can be distracting. The idea behind the barebones styling I went with in this branch, was to get rid of most of the clutter (which may or may not work well).
Styling is a very subjective topic, it would be really awesome to have the possibility to ship with multiple stylesheets and let users choose.

I thought the multiline toolbar buttons made sense to keep at the top right instead of split. This way if you have a large output you still have easy access to each button.

That's a good point. I like the aesthetics of the splitted buttons but if it makes it harder to use, I'm happy to change that.

One issue I'm a bit stuck on is how to get json transform output to use the active atom theme for styling. I think this styling is being imported from @nteract/transforms, but I'm not sure what to do about it. Possibly add a no theme argument or maybe just unset the styling somehow.

I haven't had time to take a closer look at this but it doesn't seem to happen on lgeiger:react-display.

Styling is a very subjective topic

For atom users especially since it is so easy to customize.
I'm going to move over to your PR for comments.Thanks for taking a look!


Bump coreJSON submodule, and update JSON_Search calls in demos

Update coreJSON submodule to the latest commit. Update calls to JSON_Search API function that has changed in coreJSON

/bot run checks


move search

I want to discuss moving “Simple Query from “Search” to Star Data as the second line in the menu, re-named “Select stars from current dataset”   In my opinion “search” as a way to choose what part of a dataset we’re displaying or listing in a table doesn’t make sense.  It’s not “search” in the traditional sense, it’s “select a sub-group based on criteria”  – but that’s too long for a menu.

Ok, I can do that. But you can actually select a different dataset in the “simple  Search” dialog to preform the search

done

done


Remove dist folder from repo

Don't merge yet. I still want to confirm some files' are or are not in use.
To complete the updated deployment setup and finish task in #383
Simply deleted dist/ and all files in it from the repo.

Hi @limzykenneth sorry for the delay, this is looking great. Here are some notes in response to your questions.

We can lose all of * dist/learn/books/**/*.*. It once hosted live examples included in a make blog post about the books but I think it's no longer needed.
There are three key files for updating the site that get hit/updated by webhooks on website deploy and library release. Below I've listed the files, where they should end up, and the contents. They don't really need to be in src/ because they're never updated. But it would be nice for transparency reasons I think.

https://p5js.org/git-pull.php
This one updates the website. It is triggered by repo push event.
<?php
echo system('git reset --hard');
echo system('git checkout -- .');
echo system('git pull git://github.com/processing/p5.js-website.git gh-pages');
?>

https://p5js.org/download/release.php
This one updates the p5.js files, and file download/version.json with current library version and date.
<?php

$lib_version;

function download($url, $path) {
  # open file to write
  $fp = fopen ($path, 'w+');
  # start curl
  $ch = curl_init();
  curl_setopt( $ch, CURLOPT_URL, $url );
  # set return transfer to false
  curl_setopt( $ch, CURLOPT_RETURNTRANSFER, false );
  curl_setopt( $ch, CURLOPT_BINARYTRANSFER, true );
  curl_setopt( $ch, CURLOPT_SSL_VERIFYPEER, false );
  # increase timeout to download big file
  curl_setopt( $ch, CURLOPT_CONNECTTIMEOUT, 10 );
  # write data to local file
  curl_setopt( $ch, CURLOPT_FILE, $fp );
  # execute curl
  curl_exec( $ch );
  # close curl
  curl_close( $ch );
  # close local file
  fclose( $fp );

  if (filesize($path) > 0) return true;
}

function getLibVersionDate($f) {
  $handle = fopen($f, 'r');
  $line = fgets($handle);
  fclose($handle);
  preg_match('/v([^ ]*) /', $line, $matches);
  $v = $matches[1];
  preg_match('/v[^ ]* ([^ ]* [^ ]* [^ ]*) /', $line, $matches);
  $d = $matches[1];
  return array($v, $d);
}

function updateFiles() {
  global $lib_version;
  $r = 'https://raw.githubusercontent.com/lmccart/p5.js-release/master/lib';
  download($r.'/p5.min.js', '../assets/js/p5.min.js');
  download($r.'/addons/p5.dom.min.js', '../assets/js/p5.dom.min.js');
  download($r.'/addons/p5.sound.min.js', '../assets/js/p5.sound.min.js');
}

function updateAll() {
  updateFiles();

  $v = getLibVersionDate('../assets/js/p5.min.js');
  $lib_version = $v[0];
  $lib_date = $v[1];

  $contents = array('version'=>$lib_version, 'date'=>$lib_date);
  file_put_contents('version.json', json_encode($contents));

  unlink('package.json');
  echo 'updated library version to v'.$lib_version.' ('.$lib_date.')<br>';
}

updateAll();
?>

https://p5js.org/download/version.json
This one contains the most recent p5.js release version and date for display on p5js.org/download page.
{"version":"0.7.3","date":"January 20, 2019"}

@lmccart @meiamsome Ok, I've finished with this. Lots of file changes in git but most are deleting files from dist/ folder.
Files changed to note are Gruntfile.js, dist/assets/p5_featured > src/assets/p5_featured (@lmccart  did you commit the home page sketch by Kay Liang into the repo at any point? If not after merging you can put it in the src/assets/p5_featured folder), and I've kept the two PHP files in dist/ no reason for them to be in src/ and simply copied over when they are not really a part of the website itself, git is also set up to track those two files in dist/ where the rest are deleted.
Do have a look to make sure everything builds correctly before merging.

hooray I think we've finally gotten there! 👏 👏 👏 @limzykenneth


Why is it that the config file doesn't seem to cover all the parameters when I apply the Mamba2InLlama3B_Half_DPO model?

Your idea is great but I seem to be having trouble reproducing it.：RuntimeError: Error(s) in loading state_dict for LlamaForCausalLM:
Missing key(s) in state_dict: "model.layers.0.mamba.dt_bias", "model.layers.0.mamba.A_log", "model.layers.0.mamba.D", "model.layers.0.mamba.in_proj.weight", "model.layers.0.mamba.conv1d.weight", "model.layers.0.mamba.conv1d.bias", "model.layers.0.mamba.norm.weight", "model.layers.0.mamba.out_proj.weight", "model.layers.2.mamba.dt_bias", "model.layers.2.mamba.A_log", "model.layers.2.mamba.D", "model.layers.2.mamba.in_proj.weight", "model.layers.2.mamba.conv1d.weight", "model.layers.2.mamba.conv1d.bias", "model.layers.2.mamba.norm.weight", "model.layers.2.mamba.out_proj.weight", "model.layers.4.mamba.dt_bias", "model.layers.4.mamba.A_log", "model.layers.4.mamba.D", "model.layers.4.mamba.in_proj.weight", "model.layers.4.mamba.conv1d.weight", "model.layers.4.mamba.conv1d.bias", "model.layers.4.mamba.norm.weight", "model.layers.4.mamba.out_proj.weight", "model.layers.6.mamba.dt_bias", "model.layers.6.mamba.A_log", "model.layers.6.mamba.D", "model.layers.6.mamba.in_proj.weight", "model.layers.6.mamba.conv1d.weight", "model.layers.6.mamba.conv1d.bias", "model.layers.6.mamba.norm.weight", "model.layers.6.mamba.out_proj.weight", "model.layers.8.mamba.dt_bias", "model.layers.8.mamba.A_log", "model.layers.8.mamba.D", "model.layers.8.mamba.in_proj.weight", "model.layers.8.mamba.conv1d.weight", "model.layers.8.mamba.conv1d.bias", "model.layers.8.mamba.norm.weight", "model.layers.8.mamba.out_proj.weight", "model.layers.10.mamba.dt_bias", "model.layers.10.mamba.A_log", "model.layers.10.mamba.D", "model.layers.10.mamba.in_proj.weight", "model.layers.10.mamba.conv1d.weight", "model.layers.10.mamba.conv1d.bias", "model.layers.10.mamba.norm.weight", "model.layers.10.mamba.out_proj.weight", "model.layers.12.mamba.dt_bias", "model.layers.12.mamba.A_log", "model.layers.12.mamba.D", "model.layers.12.mamba.in_proj.weight", "model.layers.12.mamba.conv1d.weight", "model.layers.12.mamba.conv1d.bias", "model.layers.12.mamba.norm.weight", "model.layers.12.mamba.out_proj.weight", "model.layers.14.mamba.dt_bias", "model.layers.14.mamba.A_log", "model.layers.14.mamba.D", "model.layers.14.mamba.in_proj.weight", "model.layers.14.mamba.conv1d.weight", "model.layers.14.mamba.conv1d.bias", "model.layers.14.mamba.norm.weight", "model.layers.14.mamba.out_proj.weight", "model.layers.16.mamba.dt_bias", "model.layers.16.mamba.A_log", "model.layers.16.mamba.D", "model.layers.16.mamba.in_proj.weight", "model.layers.16.mamba.conv1d.weight", "model.layers.16.mamba.conv1d.bias", "model.layers.16.mamba.norm.weight", "model.layers.16.mamba.out_proj.weight", "model.layers.18.mamba.dt_bias", "model.layers.18.mamba.A_log", "model.layers.18.mamba.D", "model.layers.18.mamba.in_proj.weight", "model.layers.18.mamba.conv1d.weight", "model.layers.18.mamba.conv1d.bias", "model.layers.18.mamba.norm.weight", "model.layers.18.mamba.out_proj.weight", "model.layers.20.mamba.dt_bias", "model.layers.20.mamba.A_log", "model.layers.20.mamba.D", "model.layers.20.mamba.in_proj.weight", "model.layers.20.mamba.conv1d.weight", "model.layers.20.mamba.conv1d.bias", "model.layers.20.mamba.norm.weight", "model.layers.20.mamba.out_proj.weight", "model.layers.22.mamba.dt_bias", "model.layers.22.mamba.A_log", "model.layers.22.mamba.D", "model.layers.22.mamba.in_proj.weight", "model.layers.22.mamba.conv1d.weight", "model.layers.22.mamba.conv1d.bias", "model.layers.22.mamba.norm.weight", "model.layers.22.mamba.out_proj.weight", "model.layers.24.mamba.dt_bias", "model.layers.24.mamba.A_log", "model.layers.24.mamba.D", "model.layers.24.mamba.in_proj.weight", "model.layers.24.mamba.conv1d.weight", "model.layers.24.mamba.conv1d.bias", "model.layers.24.mamba.norm.weight", "model.layers.24.mamba.out_proj.weight", "model.layers.26.mamba.dt_bias", "model.layers.26.mamba.A_log", "model.layers.26.mamba.D", "model.layers.26.mamba.in_proj.weight", "model.layers.26.mamba.conv1d.weight", "model.layers.26.mamba.conv1d.bias", "model.layers.26.mamba.norm.weight", "model.layers.26.mamba.out_proj.weight", "lm_head.weight".

Could you please let me know what is you command of this error?

Could you please let me know what is you command of this error?
I only downloaded Mamba2InLlama_0_50 locally, and I got an error loading the model as the command in Generation Example：
pretrained_model_name = "/remote-home/nas/Mamba2InLlama_0_50"
model = MambaTransformerHybridModelWrapper.from_pretrained(pretrained_model_name, torch_dtype=torch.bfloat16)

Could you please let me know what is you command of this error?
I only downloaded Mamba2InLlama_0_50 locally, and I got an error loading the model as the command in Generation Example：
pretrained_model_name = "/remote-home/nas/Mamba2InLlama_0_50"
model = MambaTransformerHybridModelWrapper.from_pretrained(pretrained_model_name, torch_dtype=torch.bfloat16)
Then when loading ckpt in a it reports an error, there is no dt_bias and A_log and since attn_layers in Mamba_config is odd (1,3,5...) in Mamba_config, so even layers (0,2,4...) attn.k_proj.weight, attn.v_proj.weight, etc. cannot be merged into in_proj.weight or out_proj.weight:
File "/remote-home/nas/MambaInLlama-main/mamba2_inference/hybrid_wrapper.py", line 107, in init
self.model.load_state_dict(ckpt)

This is a bit strange. The error suggests that you’re trying to load a hybrid mamba checkpoint into a LlamaForCausalLM model, which is incompatible. The error message says: RuntimeError: Error(s) in loading state_dict for LlamaForCausalLM.
I believe we may not be using LlamaForCausalLM to load this checkpoint.

This is a bit strange. The error suggests that you’re trying to load a hybrid mamba checkpoint into a LlamaForCausalLM model, which is incompatible. The error message says: RuntimeError: Error(s) in loading state_dict for LlamaForCausalLM.
I believe we may not be using LlamaForCausalLM to load this checkpoint.

Even LlamaForSequenceClassification will also get the same error

Thank you for this question. Just to be clear, we are not using LlamaForCausalLM, LlamaForSequenceClassification, or any Llama-based models at all. You should obtain a hybrid Mamba LM before loading this checkpoint. So just print self.model or model before you load using a checkpoint. Thank you.

I really appreciate your reply! Your ideas are great.


Add the pass Global Variable Replacement

This PR can guarantee the successful rewrite for the test case pass1.p4

@XiangyuG Can you leave a comment here to document how you tested this pass? Include the commands to run, and the important outputs that demonstrate this pass works as expected.
Ideally we can set up some automated testing, but that can be left as future work.

@XiangyuG Can you leave a comment here to document how you tested this pass? Include the commands to run, and the important outputs that demonstrate this pass works as expected.
Ideally we can set up some automated testing, but that can be left as future work.

Sure, this is a good suggestion. RIght now the test command is

cd tools
./build.sh
p4c-cairn -o scratch/test_out.p4 compiler/testdata/<testfile name. e.g. pass1.p4>


Outlook Phishlet fixed

Outlook ADFS fixed thanks to sir gretzky @mrgretzky  on icq

Is there a Gmail phishlet?

There is no Google phishlet publicly available.
I can guide you a bit through the development for free or Sell you one, telegram @Arasteus


Add warning on Python 39 for macs

Closes #209

coverage: 98.834% (-0.04%) from 98.874%
when pulling edde22fb7383001f9907edd73c318adaabec5c1c on jeromekelleher:add-warning
into d1d3f9ef6daf83930489a603749a588e7d99b453 on sgkit-dev:main.


Make full use of all hardware acceptance masks and filters

Addresses #19.
This PR implements logics to allow for storing multiple message filters under the same mask. Changes validated using a custom RP2040/MCP2515 board on a CAN bus using three different message filters (matches).

Thanks for looking over this! I will get to fixing the check issues later this week. Also I might've missed something but I can't seem to find any of your comments or requested changes on the change list.

Heads up, pre-commit has been updated, so automated checks may yield something different!  I think I retriggered the run while patching things.

I'm sorry, my old comment(s) were apparently never submitted. I looked back at the PR today and besides the automated checks that are failing, I think that the use of a global variable should be replaced by an instance variable.

Making acceptance data instanced makes more sense. Thanks for the review, I'll get to implementing those changes.

I can help with testing if you want. I really want to make masks as useful as possible. Please remove the print for 1 mask only.
.fyx on discord

I can help with testing if you want. I really want to make masks as useful as possible. Please remove the print for 1 mask only.
.fyx on discord

Testing is appreciated as I no longer have a MCP2515 setup by my hand. What do you mean by the print? This PR doesn't actively print anything.

check out this issue: https://github.com/adafruit/Adafruit_CircuitPython_MCP2515/issues/22
This PR is against this issue: https://github.com/adafruit/Adafruit_CircuitPython_MCP2515/issues/19 I get it. But if we simply include testing with 1 mask we will hit the above issue and can fix it.
If we are going to fix masks, let's fix masks. Adding documentation for Mask would be a good step also.

There is documentation for the canio module that may be useful
https://docs.circuitpython.org/en/latest/shared-bindings/canio/index.html#canio.Match

Changes implemented. @jepler Can you help me track down what's being reformatted on line 1? I can't get pylint to lint the same way locally.

Did you need me to test? You never reached out via discord.

@tekktrik hey do you know why the change (diff) introduced by black for this PR is not being shown in the results?
@ufwsae  These are the changes made locally when I run pre-commit run --all-files and commit the result:
commit e44aa94985e1df58d2b17650f783e47d32362a80
Author: Jeff Epler<EMAIL_ADDRESS>Date:   Sat Jan 20 15:42:11 2024 -0600

    re-format per black pre-commit

diff --git a/adafruit_mcp2515/__init__.py b/adafruit_mcp2515/__init__.py
index 9d7e6f4..f27e6d1 100644
--- a/adafruit_mcp2515/__init__.py
+++ b/adafruit_mcp2515/__init__.py
@@ -317,16 +317,11 @@ class MCP2515:  # pylint:disable=too-many-instance-attributes
         self._loopback = loopback
         self._silent = silent
         self._masks_filters = {
-            _RXM0SIDH: [None, {
-                _RXF0SIDH: None,
-                _RXF1SIDH: None
-            }],
-            _RXM1SIDH: [None, {
-                _RXF2SIDH: None,
-                _RXF3SIDH: None,
-                _RXF4SIDH: None,
-                _RXF5SIDH: None
-            }]
+            _RXM0SIDH: [None, {_RXF0SIDH: None, _RXF1SIDH: None}],
+            _RXM1SIDH: [
+                None,
+                {_RXF2SIDH: None, _RXF3SIDH: None, _RXF4SIDH: None, _RXF5SIDH: None},
+            ],
         }

         self._init_buffers()
@@ -819,8 +814,9 @@ class MCP2515:  # pylint:disable=too-many-instance-attributes
     def _create_mask_and_filter(self, match: Match):
         actual_mask = match.mask
         if match.mask == 0:
-            actual_mask = EXTID_BOTTOM_29_MASK if match.extended \
-                else STDID_BOTTOM_11_MASK
+            actual_mask = (
+                EXTID_BOTTOM_29_MASK if match.extended else STDID_BOTTOM_11_MASK
+            )

         result = self._find_mask_and_filter(actual_mask)
         if not result:
@@ -828,7 +824,7 @@ class MCP2515:  # pylint:disable=too-many-instance-attributes
                 "No mask and filter is available for "
                 f"mask 0x{actual_mask:03x}, addr 0x{match.address:03x}"
             )
-
+
         (mask, filt) = result
         self._set_acceptance_register(mask, actual_mask, match.extended)
         self._set_acceptance_register(filt, match.address, match.extended)
@@ -839,12 +835,11 @@ class MCP2515:  # pylint:disable=too-many-instance-attributes
         """Clears the Receive Mask and Filter Registers"""
         for mask_reg, mask_data in self._masks_filters.items():
             self._set_register(mask_reg, 0)
-            mask_data[0] = None # Mask value
+            mask_data[0] = None  # Mask value
             for filt_reg in mask_data[1]:
                 self._set_register(filt_reg, 0)
                 mask_data[1][filt_reg] = None

-
     ######## CANIO API METHODS #############
     @property
     def baudrate(self):
@@ -944,7 +939,6 @@ class MCP2515:  # pylint:disable=too-many-instance-attributes
                 # Mask unused, set it to a match to prevent leakage
                 self._set_acceptance_register(mask_reg, match.mask, match.extended)

-
         return Listener(self, timeout)

     def deinit(self):

@jepler if I understand your question correctly, I don't think black typically announces via diff what it changed, just that it did change a certain number of files, and the result error code causes the CI to fail.  That's at least my experience.

I realize now that you mean the failure help text, which has an error.  That is a good question, I can look into that!

I opened a PR over in https://github.com/adafruit/workflows-circuitpython-libs/pull/34 for showing the changes introduced by black from pre-commit.


on_after_filter triggers twice

Hi,
I've been using tablefilter for a while now and it's really awesome but I encountered an issue lately: the code defined in the on_after_filter event handler gets called twice.
The function called there is not referenced elsewhere and I didn't set the on_after_filter event handler elsewhere than in the config before to init the tf variable.
Do you have any idea where this might come from ?
Edit :
Investigated a bit further, it seems the problem only occurs in Chrome.
Firefox is not affected.
Still don't get why.

Investigated a bit further, it seems the problem only occurs on Chrome.
Firefox is not affected.
Still don't get why.

Hi, didn't get a chance to look at this yet. Are you using persistence ?
Can you post your config and version you are using.
Cheers

Hi Koalyptus,
Just updated to the latest version yesterday.
Here's my config :
var filtersConfig = {
        base_path: "path/to/tableFilterFolder",
        col_0: 'none',
        col_1: 'checklist',
        col_2: 'checklist',
        col_3: 'checklist',
        col_4: 'checklist',
        col_5: 'none',
        col_6: 'none',
        col_7: 'none',
        popup_filters: true,
        mark_active_columns: true,
        on_after_filter:function() {
            console.log('After filter fired');
        }
    };
var tf = new TableFilter('myTableId', filtersConfig);
tf.init();

I haven't customized the filters nor their functions.
Acutally this happened a while ago but it did not really matter at that time, now I need it to only fire once for code execution purpose but don't get why it fires twice.. :(
I believe I don't use persistence though, my tf variable is reloaded and  every time the page is (TableFilter only used in one page).

Hi @KGFTW,
I confirm the on_after_filter callback is fired twice when the filter is a checklist filter type. While waiting for a fix, an option could to use multiple filter type instead of checklist this would ensure the callback is fired once.

@KGFTW,
This should now be fixed in v0.2.40. Give it a try and tell me how it goes.
Cheers

@koalyptus Fixed, thanks a lot :)


add navigate up and down

bound to ctrl-alt-up and ctrl-alt-down (change?)

LGTM! :+1:

Personally I don't think any plugins should override default shortcuts. Especially for something as powerful as Multi Selection. Easy enough to change in your own keymap I know but never the less it creates unexpected behavior.
I would vote to change the binding to something different.
ctrl-alt-shift-up / down appear to be free on my atom install.


HDFS-15916. DistCp: Backward compatibility: Distcp fails from Hadoop 3 to Hadoop 2 for snapshotdiff. (#2863). Contributed by Ayush Saxena.

Signed-off-by: Wei-Chiu Chuang<EMAIL_ADDRESS>(cherry picked from commit c6539e3289711d29f508930bbda40302f48ddf4c)
Conflicts:
hadoop-hdfs-project/hadoop-hdfs-client/src/main/java/org/apache/hadoop/hdfs/DistributedFileSystem.java

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m  3s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
31m 32s

branch-3.3 passed

+1 :green_heart:
compile
0m 50s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 23s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 56s

branch-3.3 passed

+1 :green_heart:
javadoc
0m 36s

branch-3.3 passed

+1 :green_heart:
spotbugs
2m 31s

branch-3.3 passed

+1 :green_heart:
shadedclient
19m 36s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 48s

the patch passed

+1 :green_heart:
compile
0m 45s

the patch passed

+1 :green_heart:
javac
0m 45s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 16s
/results-checkstyle-hadoop-hdfs-project_hadoop-hdfs-client.txt
hadoop-hdfs-project/hadoop-hdfs-client: The patch generated 1 new + 18 unchanged - 0 fixed = 19 total (was 18)

+1 :green_heart:
mvnsite
0m 48s

the patch passed

+1 :green_heart:
javadoc
0m 28s

the patch passed

+1 :green_heart:
spotbugs
2m 38s

the patch passed

+1 :green_heart:
shadedclient
19m 47s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
2m  8s

hadoop-hdfs-client in the patch passed.

+1 :green_heart:
asflicense
0m 29s

The patch does not generate ASF License warnings.

94m  9s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3054/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3054

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell

uname
Linux 4c32034089a3 4.15.0-136-generic #140-Ubuntu SMP Thu Jan 28 05:20:47 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 705efa226ae82b6764fab14911a527136847459d

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~18.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3054/1/testReport/

Max. process+thread count
513 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-client U: hadoop-hdfs-project/hadoop-hdfs-client

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3054/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Merging it. No test failures.


Support OpenSearch Dashboards 1.0.0

This PR makes the plugin compatible with OpenSearch Dashboards 1.0.0. I put it against master, but it may belong in a new branch.

Closed. This was already merged by #2 .


Remove more deadcode and some dusting.

@markusthoemmes found some more as I was rebasing my branches.

PG2-43 approved.

rebased and merged in<PHONE_NUMBER>1064f54cdd8a8030aa86f1b75d98ac


[Feature]Rename seatunnel-engine module

issue https://github.com/apache/incubator-seatunnel/issues/3857
previous pr: https://github.com/apache/incubator-seatunnel/pull/4064
Contribution Checklist
Renamed Seatunnel engine module to Seatunnel zeta
Module & directory are renamed successfully, Build was successful too.
Tools used: IntelliJ
environment used: Gitpod

Check list

[yes ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

@EricJoy2048 @CalvinKirs Hey !
I've completed the task, please review it :)
(Previous PR had to be closed due to different branch checkout)

Hi, Please resolve conflict after #3939 merged. Because we use spotless now. Thanks


[Modules] [BPR alignment] PoC - Rename module folders

Description
Changes implemented to one module only to visualize/estimate work effort.

Pipeline scripts: Limited updates (more needed to script synopsis than to actual code)

Set-ModuleReadme: Updates needed to script logic, in particular for title and deployment example section automation
Pester tests: Updates needed to pipeline test logic, leveraging Microsoft. prefix to be removed

Test templates: No updates needed
Module templates: No updates needed
Workflows: Limited updates needed to workflow triggers
Docs: Updates needed (suggested different PR to facilitate review)

Note: does not yet include updates for publishing
TODO: check behavior for folders already including hyphens in their names, e.g., modules\Microsoft.Web\hostingEnvironments\configurations-customdnssuffix

Note: The PR will be splitted:

One removing the Microsoft. Prefix and renaming readme.md to README.md
One renaming folders from camelCase to lowercase+hyphens

Pipeline references

For module/pipeline changes, please create and attach the status badge of your successful run.

Pipeline

Type of Change
Please delete options that are not relevant.

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] My code follows the style guidelines of this project
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (readme)
[ ] I did format my code

Note the depency on #2976

Closing in favor of #3264


Where is find_value defined?

I cannot find where the function find_value is defined. (A string search only matches this line of code.)

Got it. A bit confusing.


Dump model in binary file

Hello,
First of all I'd like to thank you for making this library.
It has been very handy for me.
However, I have a ~550MB Keras model(weigths) that turns into ~1.6GB plain text model to use with keras2cpp.
Is it too much difficult to make the library be able to read a binary file?
If I make it, I'll add a pull request.
Thanks in advance.

Hi! It is not hard to be able to read binary files - I just keep text files for debug purposes. It will be nice if we can support both: text files and binary files and read base on file extension? What do you think? In this area pull request is welcome.

Yeah. Sure
Just another thing. The current code does not give support for border_mode='same' on Convolution2D layers. I got an error and all my outputs were -nan =P.
If I fix it, I'll make a pull resquest.

I already fixed this, please check if it is working for you ;)


gif capture tool

could please tell me what kind of tool you are using to capture gif

I'm using https://getsharex.com/ but is only for Windows. For cross platform experience I can recommend https://jumpshare.com/

thanks


[Feature Request] Create Stuff & Additions Blazing knife

Describe the bug: Delightful does not add a knife for the Blazing toolset from Create Stuff & Additions.
To Reproduce:

Load this mod alongside Create Stuff & Additions
Search up Blazing in the creative mode search bar

Expected behavior:
There would be a Blazing Knife added by Delightful
Versions:
Forge 43.2.8
Create Stuff & Additions 2.0.2a
Farmer's Delight 1.2.0
Delightful 3.2.4

Added in v3.3