fontconfig: Enable color emoji as a fallback

Describe the bug
Without this config, many emoji are rendered as black-and-white. This makes me sad.
Enter https://github.com/stove-panini/fontconfig-emoji - see the readme for a full breakdown.
To make it work best, the DejaVu font needs to be disabled, because it has B&W emoji embedded. Vera doesn't, and it is an ancestor of DejaVu, so that could be used as a replacement for the default system font.
So this issue is about if this config should be included by default and if DejaVu should be replaced as a default font.
IMHO, NixOS should default to configurations that most people would pick, and I'd argue that the most common way to see emoji nowadays is in full color.
@jtojnar @matthewbauer
Maintainer information:
module: fonts

We do install a color emoji default, are you not using fonts.fontconfig.enable and fonts.enableDefaultFonts?

What emoji font and what app are you using? At least fonts with embedded PNG (noto-fonts-emoji, twitter-color-emoji and joypixels (non-free)) should work with Pango (GTK) based apps:

Firefox supports SVG in OT type fonts (twemoji-color-font, emojione (unmaintained))).
More about font formats: https://www.colorfonts.wtf/#section4

All I did was use gnome3 as my desktop environment, and I had to change the fontconfig before Google Chrome would use color emoji. Does the link above render color emoji for you?

Is that link actually using color emoji? This link works for me in chromium & firefox: https://guoyunhe.me/demo/noto-color-emoji/index.html (fonts.enableDefaultFonts = true; fonts.enableFontDir = true;).

Yes the link i gave renders color emoji for me on Chrome and on my android phone. If you have B&W emoji, you now know which problem I'd like to fix ;)
Your example link specifically uses an emoji font, which is not the case most of the web.

I agree that the defaults could use improvement here. My fonts configuration is very bespoke, but these excerpts might be relevant to getting colour emoji used more often:
          <!-- fonts of last resort -->
          <match>
            <edit mode="append" name="family"><string>Twitter Color Emoji</string></edit>
            <edit mode="append" name="family"><string>Noto Sans</string></edit>
            <edit mode="append" name="family"><string>Source Han Sans</string></edit>
            <!-- TODO: why does http://www.fileformat.info/info/unicode/block/sutton_signwriting/utf8test.htm use Filling? -->
            <edit mode="append" name="family"><string>SignWriting 2010</string></edit>
          </match>

...

          <!-- multilingual defaults -->

          <alias binding="same">
            <family>sans-serif</family>
            <prefer>
              <family>Noto Sans</family>
              <family>Twitter Color Emoji</family>
              <family>Source Han Sans</family>
            </prefer>
          </alias>

          <alias binding="same">
            <family>serif</family>
            <prefer>
              <family>Noto Serif</family>
              <family>Twitter Color Emoji</family>
              <family>Source Han Serif</family>
            </prefer>
          </alias>

          <alias binding="same">
            <family>monospace</family>
            <prefer>
              <family>Cascadia Code</family>
              <family>Twitter Color Emoji</family>
              <family>Source Han Mono</family>
              <family>Noto Sans Mono</family>
            </prefer>
          </alias>

(I empty defaultFonts.* and set defaults manually to have language-specific default fonts, but this should transfer over to the standard options reasonably.)

Using config snippets from https://github.com/stove-panini/fontconfig-emoji as @wmertens suggested seems to produce excellent results for me.  I've put the following in fonts.fontconfig.localConf:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <!-- Priority:
       1. The generic family OR specific family
       2. The emoji font family (defined in 60-generic.conf)
       3. All the rest
  -->
  <alias binding="weak">
    <family>monospace</family>
    <prefer>
      <family>emoji</family>
    </prefer>
  </alias>
  <alias binding="weak">
    <family>sans-serif</family>
    <prefer>
      <family>emoji</family>
    </prefer>
  </alias>

  <alias binding="weak">
    <family>serif</family>
    <prefer>
      <family>emoji</family>
    </prefer>
  </alias>

  <selectfont>
    <rejectfont>
      <!-- Reject DejaVu fonts, they interfere with color emoji. -->
      <pattern>
        <patelt name="family">
          <string>DejaVu Sans</string>
        </patelt>
      </pattern>
      <pattern>
        <patelt name="family">
          <string>DejaVu Serif</string>
        </patelt>
      </pattern>
      <pattern>
        <patelt name="family">
          <string>DejaVu Sans Mono</string>
        </patelt>
      </pattern>

      <!-- Also reject EmojiOne Mozilla and Twemoji Mozilla; I want Noto Color Emoji -->
      <pattern>
        <patelt name="family">
          <string>EmojiOne Mozilla</string>
        </patelt>
      </pattern>
      <pattern>
        <patelt name="family">
          <string>Twemoji Mozilla</string>
        </patelt>
      </pattern>
    </rejectfont>
  </selectfont>
</fontconfig>

...and the result is that glyphs like ⌛ and 🤔 are rendered correctly using my desired emoji font, and glyphs that should not be covered by emoji (numbers, regular text arrows, etc) are not.  Seems good so far.

@benley That is fantastic. Works a treat for me. I monologued my testing on #nixos-chat -- the short of it being that placing the above snippet in ~/.config/fontconfig/fonts.conf does not work (or rather, starts replacing numbers with their emoji counterparts), while the suggested fonts.fontconfig.localConf NixOS option works a treat. After the recent fontconfig 2.13 bump, I now have color emoji again, with no downsides (or at least, none that I've found in the past 10 minutes)!

As of recently my emoji fontconfig broke. Every space character was replaced with large gaps, numbers were replaced with emoji numbers, and alacritty went a bit insane (left window launched pre-rebuild):

I use 69-emoji.conf from the fontconfig-emoji repo alongside some logic from another emoji override file I found at some point. I'm guessing some of it is redundant, but fontconfig is hard to parse. Anyway, it doesn't work anymore. I had to disable the weakly-bound aliases for serif, sans-serif, and monospace to prefer emoji, and I also had to disable some match append rules.
Commenting out those rules fixed the issue, but I'm left with numbers replaced occasionally with emoji as @cole-h mentions.
Using the system-wide option instead of home-manager works as you describe @cole-h, but it's a bit strange, no? Why should this have to be system-wide? In any case, big thanks for following up with the solution. Fontconfig is a strange beast.

Fontconfig configurations broke recently due to fontconfig being bumped from 2.12 to 2.13. Can't tell you exactly why, but I know that's the root cause.
I'd imagine this cannot be used in h-m config so simply because the system-wide option is affected by the rest of /etc/fonts/conf.d -- the local.conf that the aforementioned NixOS option creates is loaded by 51-local.conf. I don't know exactly how fontconfig uses conf.d and the file prefixes in there, but I imagine it's an ordering of sorts. Maybe if you were to copy /etc/fonts/conf.d to ~/.config/fontconfig/conf.d, as well as both fonts.conf and local.conf, the result will be the same (properly rendered emoji)? I don't have the time to test this (and I'm fine with configuring this system-wide) so it's up to any interested parties to go from there.

Hmm, I've learned enough about the config format, but I'm having a new issue. Using both benley's config and my own slightly simplified version

fontconfig
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<!--
  This config attempts to guarantee that colorful emojis from the system emoji
  family will be displayed, no matter how apps and websites are written.
-->
<!--
  Append the emoji family immediately after default families in the matching
  logic.
-->
<alias>
  <family>sans-serif</family>
  <accept>
    <family>emoji</family>
  </accept>
</alias>
<alias>
  <family>serif</family>
  <accept>
    <family>emoji</family>
  </accept>
</alias>
<alias>
  <family>monospace</family>
  <accept>
    <family>emoji</family>
  </accept>
</alias>
<!-- Reject stubborn fallback fonts -->
<selectfont>
  <rejectfont>
    <!--
      It seems DejaVu is often selected as a fallback font before
      emoji. This will try to remove DejaVu from the list of fallback
      fonts.
    -->
    <pattern>
      <patelt name="family">
        <string>DejaVu Sans</string>
      </patelt>
    </pattern>
    <pattern>
      <patelt name="family">
        <string>DejaVu Serif</string>
      </patelt>
    </pattern>
    <pattern>
      <patelt name="family">
        <string>DejaVu Sans Mono</string>
      </patelt>
    </pattern>
    <!--
      Reject the baked-in Firefox emoji font. Firefox version <= 60 uses
      EmojiOne Mozilla, while newer uses Twemoji Mozilla
    -->
    <pattern>
      <patelt name="family">
        <string>EmojiOne Mozilla</string>
      </patelt>
    </pattern>
    <pattern>
      <patelt name="family">
        <string>Twemoji Mozilla</string>
      </patelt>
    </pattern>
  </rejectfont>
</selectfont>
</fontconfig>

I get pretty much perfect emoji support, except in rofi and dunst, which render emoji extremely small, for some reason. They're both written in C, so maybe they share some strange rendering quirk, but I doubt it. Fontconfig doesn't appear to have changed on nixos-unstable recently, so I'm not sure what changed. If someone else could test benley's config I'd appreciate it. Also, @cole-h my config has returned to functioning the same at the system and user levels. This too makes me think something in the font stack changed recently.
The two yellow dots at the end are emoji.

@hpfr I am also using benley's config, I had been using it globally from the beginning and everything was working great. It seems to have broken after https://github.com/NixOS/nixpkgs/pull/93562 and now I get the same issue you have in rofi (it was working fine previously). It works fine everywhere else (terminal, editor, browser), I have spent some time trying to debug it but I have no clue what the issue is.

I seem to be having the same issues with broken fonts and it seems /etc/fonts/local.conf is no longer being linked, and my localConf no longer seems to be used by fontconfig

Can confirm that the issue @hpfr describes persists on master. I can reproduce it with bemenu and sway. My previously working config is:
{
    fonts = {
     # …

      enableFontDir = true;
      enableGhostscriptFonts = true;
      enableDefaultFonts = true;

      fontconfig = {
        enable = true;
        antialias = true;
        hinting.enable = true;
        defaultFonts = {
          monospace = [ "DejaVu Sans Mono" "Noto Mono" ];
          serif = [ "Vollkorn" "Noto Serif" "Times New Roman" ];
          sansSerif = [ "Open Sans" "Noto Sans" ];
          emoji = [ "Noto Color Emoji" "Twitter Color Emoji" "JoyPixels" "Unifont" "Unifont Upper" ];
        };
      };
    };
}

@sternenseemann can you confirm that ~/.config/fontconfig/fonts.conf does not exist for you either? I honestly have no idea how that's generated, but deleting it just fixed my issue on current master (f14522334077f0dcc98bb9c80353f3cb1b6f1e48).

@ciil Issue persists for me, I've rebuild with the given commit and deleted ~/.config/fontconfig

Quick script for copying the configuration to a directory for easy tweaking:
FONTCONFIG_PATH=$PWD/etc-fonts
cp --dereference -r /etc/fonts/2.11/ "$FONTCONFIG_PATH"
chmod -R +w "$FONTCONFIG_PATH"
sed -i "s#>/etc/fonts/2.11#>$FONTCONFIG_PATH#g" $(rg -l /etc/fonts "$FONTCONFIG_PATH")

Then you can run env FONTCONFIG_FILE=$PWD/etc-fonts/fonts.conf FC_DEBUG=1024 pango-view --text="Příliš 😂" --font='"Noto Color Emoji" 20' and see how much scaled the emoji is.

Commenting out https://gitlab.freedesktop.org/fontconfig/fontconfig/-/blob/e735abcfe139de91fc2e2d323cb4bf16345e1419/conf.d/10-scale-bitmap-fonts.conf#L66-74 seems to fix the scaling issue but the line has been there for ages.
Changing the file to
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<match target="font">
  <test name="outline" compare="eq">
    <bool>false</bool>
  </test>
  <edit name="test-pattern-ps" mode="assign">
      <name target="pattern">pixelsize</name>
  </edit>
  <edit name="test-font-ps" mode="assign">
      <name target="font"   >pixelsize</name>
  </edit>
</match>
</fontconfig>

I got the following metrics:
$ env FONTCONFIG_FILE=$PWD/etc-fonts/fonts.conf fc-match -v 'Noto Color Emoji' | rg test
	test-pattern-ps: 12.5(f)(w)
	test-font-ps: 109(f)(w)

Of course, while I was building fc 2.12.6, I realized the scaling code is not idempotent and is being run twice thanks to
https://github.com/NixOS/nixpkgs/blob/742c7340d2b998065c5e03355e657ee338057658/pkgs/development/libraries/fontconfig/make-fonts-conf.xsl#L35
We will need to revert edf2541f02c6b24ea791710d5cadeae36f9b1a3a. https://github.com/NixOS/nixpkgs/pull/95358

The issue with small emojis is fixed for me on current nixos-unstable (a31736120c5de6e632f5a0ba1ed34e53fc1c1b00).

Persists for me.

Fixed for me (with benley's config from here: https://github.com/NixOS/nixpkgs/issues/86601#issuecomment-670158155).

Fixed also for me (without a local.conf), turns out I had a typo in my NIX_PATH override.
@jtojnar seems like the versioned config directory was indeed the issue.

The config posted by @benley worked for me as well, but it was important to set the defaultFonts and omit the rejectfont blocks instead, because otherwise it would not allow those fonts to be used at all (which would make it unnecessary to put them in the fonts list in the first place).
My config ended up looking like this:
  fonts = {
    fontconfig = {
      localConf   = lib.fileContents ./fontconfig.xml;
      defaultFonts = {
        emoji = ["Noto Color Emoji"];
        serif = ["Bitstream Vera Serif"];
        sansSerif = ["Bitstream Vera Sans"];
        monospace = ["Bitstream Vera Sans Mono"];
      };
    };
    fonts = with pkgs; [
      noto-fonts-emoji
      ttf_bitstream_vera
      font-awesome_4
      unifont
    ];
  };

With fontconfig.xml containing:
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
  <alias binding="weak">
    <family>monospace</family>
    <prefer>
      <family>emoji</family>
    </prefer>
  </alias>
  <alias binding="weak">
    <family>sans-serif</family>
    <prefer>
      <family>emoji</family>
    </prefer>
  </alias>
  <alias binding="weak">
    <family>serif</family>
    <prefer>
      <family>emoji</family>
    </prefer>
  </alias>
</fontconfig>

I think this fontconfig file should be included by default in NixOS, or are there any downsides I haven't discovered yet?

According to https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/136#note_82092 it should be up to applications.
I asked about the downsides https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/111#note_630720

I have tried to follow your example @petabyteboy, but it's not working for me? https://i.imgur.com/1gec58C.png Most of the "numbers" on my desktop now either just don't render (or are too tiny to see), or are rendering as emoji. (This is basically the same result I'd gotten with @benley's config as well.)
I assume it's because I have a different mix of fonts installed (or some other change somewhere I'm not accounting for).
FWIW, I tried to be careful to stop sway, clear ~/.cache and ~/.config/fontconfig*, then re-activate, then start sway.

(try number two on this reply)
I have tried to follow your example @petabyteboy, but it's not working for me? https://i.imgur.com/PXtWYw1.png. Most of the "numbers" on my desktop now either just don't render (or are too tiny to see), or are rendering as emoji. (This is basically the same result I'd gotten with @benley's config as well.)
I assume it's because I have a different mix of fonts installed (or some other change somewhere I'm not accounting for).
FWIW, I tried to be careful to stop sway, clear ~/.cache and ~/.config/fontconfig*, then re-activate, then start sway.

That is precisely what the config is supposed to do – prioritize an emoji font over the font that would be selected normally.
You will either need to find an emoji font that does not include those characters, remove them manually using fontforge (someone must have made a script for that already), or leave it up for applications to choose emoji. The last option should already work by default in most applications and this config will not help applications that do not support emoji.
Really, the only reason to use the config above would be if you want to render old Unicode characters like ⏳ or ⚠ that were retrospectively made emoji to render as emoji.

Thank you so much for the explanation @jtojnar; that helps a lot.

As others have mentioned, jtojnar's regression fix resolved my issue and a system-wide config is no longer necessary. I use the same weak binding config benley listed above in my user fontconfig. @colemickens I don't have your issue.

That is precisely what the config is supposed to do – prioritize an emoji font over the font that would be selected normally.

@jtojnar is this the case with binding="weak"? I thought it would come after the font that would be selected normally. For me, numbers render normally.

The config posted by @benley worked for me as well, but it was important to set the defaultFonts and omit the rejectfont blocks instead, because otherwise it would not allow those fonts to be used at all (which would make it unnecessary to put them in the fonts list in the first place).

@petabyteboy note that the Twemoji Mozilla reject block is necessary if you want to avoid displaying that font in Firefox when sites specifically request it, since it is included with the browser. Furthermore, even when fonts.enableDefaultFonts is false, DejaVu Sans is still installed, hence the second reject block. Some people don't want these fonts to be used at all, since if sites specify them explicitly, they'll override system emoji fonts.

That is precisely what the config is supposed to do – prioritize an emoji font over the font that would be selected normally.

@jtojnar is this the case with binding="weak"? I thought it would come after the font that would be selected normally. For me, numbers render normally.

Hmm, that might be the case. I would just expect the weak binding to be ignored if there is a strong one that matches. But I think that it depends on how the app using fontconfig is implemented.

Yeah, I looked at the docs and it looks like binding has something to do with language. I removed that and it still seemed to work, so I don't even know if that affects anything.

I have this config now, based on @petabyteboy's which seems pretty generic and fully open source. Should we make this the default?
{ config, pkgs, ... }:

{
  fonts = {
    fontconfig = {
      localConf = ''
        <?xml version="1.0"?>
        <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
        <fontconfig>
          <alias binding="weak">
            <family>monospace</family>
            <prefer>
              <family>emoji</family>
            </prefer>
          </alias>
          <alias binding="weak">
            <family>sans-serif</family>
            <prefer>
              <family>emoji</family>
            </prefer>
          </alias>
          <alias binding="weak">
            <family>serif</family>
            <prefer>
              <family>emoji</family>
            </prefer>
          </alias>
        </fontconfig>
      '';
      defaultFonts = {
        emoji = [ "Noto Color Emoji" ];
        monospace = [ "FreeMono" ];
        sansSerif = [ "FreeSans" ];
        serif = [ "FreeSerif" ];
      };
    };
    fonts = with pkgs; [
      noto-fonts-emoji
    ];
  };
}

I have this config now, based on @petabyteboy's which seems pretty generic and fully open source. Should we make this the default?
{ config, pkgs, ... }:

{
  fonts = {
    fontconfig = {
      localConf = ''
        <?xml version="1.0"?>
        <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
        <fontconfig>
          <alias binding="weak">
            <family>monospace</family>
            <prefer>
              <family>emoji</family>
            </prefer>
          </alias>
          <alias binding="weak">
            <family>sans-serif</family>
            <prefer>
              <family>emoji</family>
            </prefer>
          </alias>
          <alias binding="weak">
            <family>serif</family>
            <prefer>
              <family>emoji</family>
            </prefer>
          </alias>
        </fontconfig>
      '';
      defaultFonts = {
        emoji = [ "Noto Color Emoji" ];
        monospace = [ "FreeMono" ];
        sansSerif = [ "FreeSans" ];
        serif = [ "FreeSerif" ];
      };
    };
    fonts = with pkgs; [
      noto-fonts-emoji
    ];
  };
}

@wmertens No, see the discussion above and upstream.

@wmertens No, see the discussion above and upstream.

@jtojnar ah right. How about moving forward with a useColorEmoji attribute with a documented caveat that it can impact rendering? It looks like we're at an impasse otherwise.

@jtojnar ah right. How about moving forward with a useColorEmoji attribute with a documented caveat that it can impact rendering? It looks like we're at an impasse otherwise.

Maybe if it were named forceColorEmoji. But really, the emoji support works as intended and when it does not, it is a bug of individual applications’ rendering stacks and should be fixed there.

Maybe if it were named forceColorEmoji. But really, the emoji support works as intended and when it does not, it is a bug of individual applications’ rendering stacks and should be fixed there.

@jtojnar What would such a fix look like for Chrome + friends?

@jtojnar What would such a fix look like for Chrome + friends?

No idea. I would expect Chromium to just work, based on https://chromium.googlesource.com/chromium/src.git/+/671511b00e2d6c374a3079c1c379d2d0dfad32fe (via https://wiki.archlinux.org/index.php/fonts#Emoji_and_symbols)

No idea. I would expect Chromium to just work, based on https://chromium.googlesource.com/chromium/src.git/+/671511b00e2d6c374a3079c1c379d2d0dfad32fe (via https://wiki.archlinux.org/index.php/fonts#Emoji_and_symbols)

@jtojnar indeed, Chrom(e|ium) just works now! I only have
{
    fonts = with pkgs; [
      noto-fonts-emoji
      // unrelated others
    ];
}

now. I'll close this.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/kde-doesnt-render-nerd-font-glyphs/30153/5

@wmertens Your snippet from https://github.com/NixOS/nixpkgs/issues/86601#issuecomment-757959059 was still required for me to have emoji support in KDE (despite having Noto Color Emoji in place beforehand).
Can we reconsider to have it as part of the fonts module (disabled by default)? - It would've saved me many hours of digging. And judging by the Discourse thread I'm not alone.


Add an Adopting Pulumi user guide

This adds an "Adopting Pulumi" user guide which will talk through the nuts and bolts of converting to Pulumi from an existing solution, including coexisting with infrastructure, importing existing infrastructure into Pulumi, as well as conversion, across Terraform, AWS CloudFormation, Azure Resource Manager (ARM) templates, and Kubernetes and Helm YAML configuration.
This fixes #1454.

@lukehoban I'm getting close to ready to check this in. The two things remaining are to finish the Kubernetes and Helm YAML guide and, afterwards, to do a general editorial pass over the content. Any early eyeballs and feedback would be great.


Creation of CONUS404 cutouts for calibration of nat'l WRF-Hydro application

User needs to make many small subsets from the CONUS404 for a handful (~10) variables. Operating on their (NCAR Cheyenne) HPC is more time-intensive than desired.  100 basins and it took about 7k core hours. So total would be about 100 K core hours, which would probably delay project timelines.
Looking for ways to speed this up either on Cheyenne or on USGS Denali HPC.
Seems like the technical challenge is how to parallelize millions of ncks commands to subset netcdf files and do so without really inefficiently consuming nodes on the platform.
Jeff Falgout offered a few suggestions , via USGS Team for "Denali Help" (today, 11/7; can't provide URL):

to wrap srun in a for loop and send the srun command to the background
Use the --multi-prog option. https://slurm.schedmd.com/srun.html#SECTION_MULTIPLE-PROGRAM-CONFIGURATION
Use job packing. https://slurm.schedmd.com/heterogeneous_jobs.html and https://slurm.schedmd.com/SLUG16/Job_Packs_SUG_2016.pdf

@arezoorn is looking into Jeff's suggestions now. @gochis and @ishita9 also part of this thread.

@arezoorn @rsignell-usgs @amsnyder,
should we be talking to the Denali folks about reserving some nodes/getting queue priority for this short-term burst of work?

That would be great if possible. I am IO bound right now in this pre-calibration task, so I cannot do many jobs at once, but I think it would be helpful to get dedicated resources so I this could continue without interruption at least. Right now, one problem is that since the queue is unexpected, the jobs are remaining in the queue and getting submitted at once and therefore putting lots of IO on the system and results in slow down.

A update, I made modification to my script to submit a big job instead of many tiny ones. This will help with management of the jobs in the queue.

@rviger-usgs Update, the modified workflow is doing a decent job. I can finish the subsetting of the forcing files by next week with this speed. It is pushing the calibration start to next week, but that is fine since I would need time to test the calibration workflow on Denali after Ishita is done with the testing. So I think we can now close this issue.

I am not sure if I get your question correctly but let me try to answer and if it does not, let me know. I have already cutout some of the forcing on Cheyenne (about 300 basins), and the rest is happening on Denali (150 basins done so far). The rest of the basins will be done by next week and they are running on Denali.
According to my schedule, I was going to start the calibration mid this week, but it is now pushed to early next week. There is some time that I could save in the calibration phase (with optimization of our calibration workflow) and that should compensate for the delay in the start of the calibration due to our problems in the preparation phase.
I hope this helps to clarify things.

that's perfectly clear. thanks @arezoorn.
should we close this issue?

Yes, we can close this issue. Thanks!

closed.


fix: treat git bash as un-interactive

Closes #1139
✅ Checklist

[ ] I have followed every step in the contributing guide (updated 2022-10-06).
[ ] The PR title follows the convention we established conventional-commit
[ ] I performed a functional test on my final commit

Changelog
[Short description of what has changed]

Screenshots
[Screenshots]
💯

perfect, thanks julius!


[Meta] DataPipes for PP Production Checkllist

Overview of what needs to be done for PP production with Datapipes
Detailed Description
These will be made into issues, the ones that are not already done
Base steps of getting the data:

[x] Load Satellite Data
[x] Load NWP Data
[x] Load GSP Data
[x] Load Topo Data
[x] Load Passiv PV Data
[x] Select location in data
[x] Load GSP database data
[x] https://github.com/openclimatefix/ocf_datapipes/issues/31
[x] https://github.com/openclimatefix/ocf_datapipes/issues/30
[x] ?Validation on data sources?In nowcasting_dataset
[ ] Add Diagram of whats going on  to readme - https://docs.google.com/presentation/d/1JScci-Ye982vfZqxdCDF7EeuS26V5D4wYcS99KY_56o/edit#slide=id.p
[x] Move end2end test to 'Production datapipe'. Make folder called production
[x] https://github.com/openclimatefix/ocf_datapipes/issues/33
[x] https://github.com/openclimatefix/ocf_datapipes/issues/34
[x] https://github.com/openclimatefix/ocf_datapipes/issues/36
[x] https://github.com/openclimatefix/ocf_datapipes/issues/57

Some Data Transformations that need to be done, the xr_ and np_batch_processors in PP:

[x] PVRollingWindow transform for PV data
[x] EncodeSpaceTime
[x] SaveT0Time
[x] AddTopography
[x] All timestamps have to cover history and future for _time_utc parts of NumpyBatch
[x] Downsample NWPs
[x] Normalize Data
[x] AlignGSPTo5Min
[x] SunPosition to add sun position
[x] GSP and PV System IDs (potentially just set to 1)

Post Data Transform ones

[x] Make data into NumpyBatch
[x] Optionla to save NumpyBatch to save out

Other issues

#24
#20
#3
#2
https://github.com/openclimatefix/ocf_datapipes/issues/38
https://github.com/openclimatefix/ocf_datapipes/issues/39

Possible Implementation
Right now, the majority of this is happening in #14

SunPosition is somewhat there, just need to add the location picker to the test
NWP doesn't like the NumpyBatch at the moment, but the rest all load and form the full NumpyBatch successfully.
Still need to figure out how to actually call the datapipes functional form, would be cleaner, although the current method still works.

NWP target time UTC adding and selecting for the live system is a bit broken and currently a bit stuck on that. But selecting all the other data types for the live environment works in testing

The target time now works, although does mix a bit the selecting and adding of the target time

End2End test now works! Only missing thing is the setting system_ids to 1, and some PV filtering. For now, might put the PV filtering in the loader just to keep it a bit simpler right now, and then refactor it out as we go along

The saving out of the data can be accomplished with the built in datapipe https://pytorch.org/data/main/generated/torchdata.datapipes.iter.FSSpecSaver.html#torchdata.datapipes.iter.FSSpecSaver

Closing this now, as we aren't using PP


Some bugs about mol_graph.py

Hello,
I have met a bug about

mol_graph.py", line 79, in graph_from_smiles
raise ValueError("Could not parse SMILES string:", smiles)
ValueError: ('Could not parse SMILES string:', 'CCCCCCCCCCCCN(C)CC(=O)O')"

As described above, the "[N]" in the smiles couldn't be parsed. I wonder if this question is mainly due to the limitation of rdkit package.
Or would you have any better solutions about this bug?
Best regards,
YJ

This is definitely pure rdkit.
To try directly:
import rdkit.Chem.AllChem as Chem

Chem.MolFromSmiles(your_str)

Writing in my phone so maybe a bug or typo in there.
Hope that helps,
Tim

On Nov 12, 2015, at 05:25, Xu Youjun<EMAIL_ADDRESS>wrote:
Hello,
I have met a bug about
mol_graph.py", line 79, in graph_from_smiles
raise ValueError("Could not parse SMILES string:", smiles)
ValueError: ('Could not parse SMILES string:', 'CCCCCCCCCCCCN(C)CC(=O)O')"
As described above, the "[N]" in the smiles couldn't be parsed. I wonder if this question is mainly due to the limitation of rdkit package.
Or would you have any better solutions about this bug?
Best regards,
YJ
—
Reply to this email directly or view it on GitHub.

Dear Tim,
Thank you very much.
Best regards,
YJ


Add go install to README

At least in my small team, we all agree that go install is the easiest way to install command line tools.

LGTM!


iTunes Backup Broken.

When trying to backup an iPhone 6s (10.2) through the latest iTunes the process doesn't start. I can click it over and over it does nothing. iTunes recognizes the device, but will not back up data.
I tried a clean non-jb iPod 5 on iOS 9.3.1. It went through the backup process successfully.
I read the issue posting guidelines.

Interesting. Did you try with no-substrate mode?

Yes. Rebooting into no-substrate has the same result.

Weird.

Yes, I have backups from Pangu 933 up to my update with clean 10.2. Updated to newest iTunes just in case but it persists.

This is a very strange error. I did a backup after using Yalu, and it worked just fine (until I got an error about authorization, which is vShare's problem).

No cracked app stores or appsync.
I written a generator to nvram, that's about it with drastic changes.

Is working now with latest iTunes


parallell-letter-frequency tests are missing some assertions

The tests for the cases that expect an empty map as result are missing the assertions.
The script that I used to generate that code would iterate over the dict and was missing the "empty dict" special case. :(

Fix is here: https://github.com/exercism/cpp/pull/830 (I only opened this because I expected that issues would not be automatically closed ...)


I want to know how can I upload multiple files at the same time?

Thank you for your this tool !
If you upload a file separately, it works well.
But I don’t know how to upload a folder, these configurations are not effective:
 source: "dist"
 source: "./dist"
 source: "./dist/"
 source: "./dist/*"

But I don’t know how to upload a folder

So far this action only works for files, but as soon as possible I add support for directories.

Thanks.

Fixed by 6681a6d4596e23b96314c6c4ae2c154d4c4d346c, version v1.1.0


package-lock: npm audit fix

npm audit fix was run to upgrade vulnerable packages

@akarve i'm going to merge this change, since it's trivial


make dist fails make: *** [jre_emul_jars_dist] Error 2

Followed this guide here: https://developers.google.com/j2objc/guides/building-j2objc#install_protobuf
Here is the terminal output:
Building j2objc annotations
mvn -q generate-resources dependency:sources
building j2objc jar
Note: src/main/java/com/google/devtools/j2objc/pipeline/InputFilePreprocessor.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
building jre_emul.jar
javac: invalid flag: --patch-module=java.base=.
Usage: javac
use -help for a list of possible options
make[1]: *** [/Users/bryananderson/DOMO/JDK/j2objc/jre_emul/build_result/jre_emul.jar] Error 2
make: *** [jre_emul_jars_dist] Error 2

We don't use Java 8 any more, just Java 11. So instead of "export JAVA_HOME=/usr/libexec/java_home -v 1.8", do:
export JAVA_HOME=`/usr/libexec/java_home -v 11`

I'll update the doc.

Okay now running Java 11
bryananderson@Bryan-Anderson-XVXXDK6V7P j2objc % java --version
openjdk <IP_ADDRESS> 2023-08-24
OpenJDK Runtime Environment Homebrew (build <IP_ADDRESS>+0)
OpenJDK 64-Bit Server VM Homebrew (build <IP_ADDRESS>+0, mixed mode)
bryananderson@Bryan-Anderson-XVXXDK6V7P j2objc % make clean
bryananderson@Bryan-Anderson-XVXXDK6V7P j2objc % java --version
openjdk <IP_ADDRESS> 2023-08-24
OpenJDK Runtime Environment Homebrew (build <IP_ADDRESS>+0)
OpenJDK 64-Bit Server VM Homebrew (build <IP_ADDRESS>+0, mixed mode)

Ends up the same though:
bryananderson@Bryan-Anderson-XVXXDK6V7P j2objc % make dist
Locale: en_US.UTF-8
Darwin Bryan-Anderson-XVXXDK6V7P.local 23.0.0 Darwin Kernel Version 23.0.0: Thu Aug 17 21:23:05 PDT 2023; root:xnu-10002.1.11~3/RELEASE_ARM64_T6000 arm64
Xcode 15.0 Build version 15A240d
Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
Target: arm64-apple-darwin23.0.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Environment:
HOME=/Users/bryananderson
HOMEBREW_CELLAR=/opt/homebrew/Cellar
HOMEBREW_PREFIX=/opt/homebrew
HOMEBREW_REPOSITORY=/opt/homebrew
INFOPATH=/opt/homebrew/share/info:
J2OBJC_ARCHS=macosx iphone64 iphone64e watchosv7k watchos64 watchsimulator watchsimulator64 simulator simulator64 maccatalyst appletvos appletvsimulator macosx64 maccatalyst64
LANG=en_US.UTF-8
LOGNAME=bryananderson
MAKEFLAGS=
MAKELEVEL=1
MANPATH=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/share/man:/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/usr/share/man:/Applications/Xcode.app/Contents/Developer/usr/share/man:/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/share/man:/opt/homebrew/share/man::
MFLAGS=
PATH=/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin
PWD=/Users/bryananderson/DOMO/JDK/j2objc
SHELL=/bin/zsh
SHLVL=2
SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.q7StSfsvok/Listeners
TERM=xterm-256color
TERM_PROGRAM=Apple_Terminal
TERM_PROGRAM_VERSION=450
TERM_SESSION_ID=A4B0BB33-E706-47DC-835A-D9B188426E9F
TMPDIR=/var/folders/dg/m7p8ljs52vv5phhm44r9bb7h0000gn/T/
USER=bryananderson
XPC_FLAGS=0x0
XPC_SERVICE_NAME=0

Building j2objc annotations
mvn -q generate-resources dependency:sources
building j2objc jar
Note: src/main/java/com/google/devtools/j2objc/pipeline/InputFilePreprocessor.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
building jre_emul.jar
javac: invalid flag: --patch-module=java.base=.
Usage: javac <options> <source files>
use -help for a list of possible options
make[1]: *** [/Users/bryananderson/DOMO/JDK/j2objc/jre_emul/build_result/jre_emul.jar] Error 2
make: *** [jre_emul_jars_dist] Error 2

--patch-module=java.base=. is a valid javac flag for JDK 11, but since it isn't for 1.8, you're likely still running javac 1.8.
To verify this, run javac -version, which should have the same version as java -version. If they aren't, run which java javac; their paths should be the same, and if they aren't, then your PATH and/or JAVA_HOME environment variables need to change.

First of all thank you, @tomball, for your help and congrats on your near retirement. I find myself desperately wishing for that future date even though I'm likely 30 years away!
bryananderson@Bryan-Anderson-XVXXDK6V7P j2objc % javac -version
javac <IP_ADDRESS>
bryananderson@Bryan-Anderson-XVXXDK6V7P j2objc % which java javac
/opt/homebrew/bin/java
/opt/homebrew/bin/javac
It does appear that Javac is the correct version and the paths do match.

@bryan1anderson: The output in your comment (here) appears to be missing a JAVA_HOME environment variable. Try export-ing the JAVA_HOME environment variable before running the make dist command.

Updated the Building J2ObjC doc.

Here's the "script" (it's actually in my ~/.bash_profile) I use to set the JAVA_HOME and PATH correctly (so they don't step on each other):
function setjdk() {
  if [ $# -ne 0 ]; then
   removeFromPath '/System/Library/Frameworks/JavaVM.framework/Home/bin'
   if [ -n "${JAVA_HOME+x}" ]; then
    removeFromPath $JAVA_HOME
   fi
   unset JAVA_HOME
   export JAVA_HOME=`/usr/libexec/java_home -v $@`
   export PATH=$JAVA_HOME/bin:$PATH
  fi
}
function removeFromPath() {
  export PATH=$(echo $PATH | sed -E -e "s;:$1;;" -e "s;$1:?;;")
}
setjdk 11

This may not work with HomeBrew installed JDKs (HomeBrew often lags behind on Java-related packages), but I always use distributions from Oracle and Azul Systems.
To use, run setjdk <major-release-number>, like the setjdk 11 above. To see which JDK versions you have installed, run /usr/libexec/java_home -V.

I love HomeBrew, BTW, so I wasn't dunking on it. Java engineers frequently need to directly use the core Java tools, so I use HomeBrew for everything else.


Add travis build for 1.16.x golang

Need to be testing against the latest versions

Travis failing

Yeah there is something in golang 1.16 that doesn't like our go.sum or go.mod... haven't had time to check it yet.


Quick question [Styled Player List vs Ordered Player List]

Hey, I'm assuming ordered player list replaces Styled Player List?
Or can you have them together?
Just want to avoid having to configure everything again.

OPL is just another mod, almost exclusively taking care of ordering
It's meant to be used alongside SPL, though it can probably work without it

Right. Thanks for your time


Narrow operand does not support IntList as operand

Problem addressed:
Fixing issue with getting dm messages by userId:
        List<Message> dm = zulip.messages().getMessages(50, 50, Anchor.NEWEST)
                .withNarrows(Narrow.of("dm", "14"))
                .withAnchor(834373)
                .withGravatar(true)
                .execute();

will fail with:
com.github.jamesnetherton.zulip.client.exception.ZulipClientException: Invalid narrow operator: unknown user in 14

Example call from web UI:
https://chat.foxminded.ua/json/messages?anchor=834373&num_before=50&num_after=50&narrow=[{"negated"%3Afalse%2C"operator"%3A"dm"%2C"operand"%3A[14]}]&client_gravatar=true
narrow here is:
[
    {
        "negated": false,
        "operator": "dm",
        "operand": [14]
    }
]

fix in PR tested with 8.2 and successfully fetches messages as
        List<Message> dm = zulip.messages().getMessages(50, 50, Anchor.NEWEST)
                .withNarrows(Narrow.of("dm", List.of(14)))
                .withAnchor(834373)
                .withGravatar(true)
                .execute();

Thanks for reporting this! I missed the note about it in the Zulip API docs.

Prior to Zulip 8.0, the message ID operand for the id operator needed to be encoded as a string.

Not sure if you've tried, but you may be able to work around the issue by passing the raw String representation of the int array. E.g like [1,2,3].

@jamesnetherton I tried, but it will encode it as "[14]" and will give same error Invalid narrow operator: unknown user in [14]


(#113) Add windows nasm target

Close #113
Sorry for closing previous PR (#372), didn't think it's a bad idea. I'll try to not close PRs for no reason in future.

@kolumb looks goode to me! :+1: Thank you for your contribution! :kissing:


Timeouts during interview with Allegion/Schalge BE469ZP

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
Interview a Schalage BE469ZP
What do you observe?
Repeated timeouts during interview
2022-06-26T18:36:30.791Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-06-26T18:36:30.791Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:30.791Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-06-26T18:36:30.811Z SERIAL « 0x011d00a97600000100ac7f7f7f7f01010300000000020100007f7f7f7f7fef    (31 bytes)
2022-06-26T18:36:30.812Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:30.812Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            118
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -84 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1
2022-06-26T18:36:31.844Z CNTRLR   [Node 090] Timed out while waiting for a response from the node (ZW0201)

What did you expect to happen?
Interview to complete without errors.
Steps to reproduce the behavior:

Include or trigger a re-interview of a BE469ZP.

Device information
Manufacturer: Allegion
Model name: BE469ZP
Node ID in your network: 90 and 91 (I have two different devices showing the same results)
How are you using node-zwave-js?

[X] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
version:
node-zwave-js branch: 9.4.0
zwavejs2mqtt branch: 6.12.1
Did you change anything?
yes (please describe)
If yes, what did you change?
I finally upgraded the firmware on my Zooz 700 series controller and moved my network back to it. I was getting issues with repeated notifications from the locks when the door was locked or unlocked so I decided to try excluding and re-including the device. This did solve the multiple notification issue, but now I'm having trouble interviewing the device.
Did this work before?
Yes (please describe)
If yes, where did it work?
At some point in the past the device had interviewed properly.
Attach Driver Logfile
zwavejs_current.log

I suspect the issue is related to the Beaming frequency for the locks. It wakes up once every second, and it looks like the timeout is occurring at 1 second. I've found if I refresh all values on the device, and trigger a re-interview while the refresh is happening it completes more of the interview. Just to see if I could increase the timeout value, I added the following to /usr/src/app/lib/ZwaveClient.ts in the zwavejs2mqtt container before restarting the container:
                        // extend options with hidden `options`
                        const zwaveOptions: utils.DeepPartial<ZWaveOptions> = {
                                timeouts: {
                                        report: 2000,
                                },
                                storage: {

It didn't make any difference however.

Honestly, I believe this is just the lock acting up. I can't remember how many issues I've seen related to this exact model and its always the lock doing something strange.
The timeout is computed automatically from (round-trip-time + report timeout). The round-trip-time (RTT) is the time delta between sending the request and receiving the node's acknowledgement - meaning the node did already answer, so it cannot be asleep.
During the stretch of commands you quoted, it consistently had a RTT of 30-40 ms and replies in ~300-400 ms:
2022-06-26T18:36:29.575Z DRIVER » [Node 090] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      115
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 22
                                    └─[NotificationCCEventSupportedGet]
                                        notification type: Access Control
2022-06-26T18:36:29.581Z SERIAL « [ACK]                                                                   (0x06)
2022-06-26T18:36:29.582Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-06-26T18:36:29.582Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:29.582Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-06-26T18:36:29.603Z SERIAL « 0x011d00a97300000200ad7f7f7f7f01010300000000020100007f7f7f7f7fe8    (31 bytes)
2022-06-26T18:36:29.604Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:29.604Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            115
                                    transmit status:        OK, took 20 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -83 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1
2022-06-26T18:36:29.907Z DRIVER « [Node 090] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -83 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 237
                                    └─[NotificationCCEventSupportedReport]
                                        notification type: Access Control
                                        supported events:
                                        · Manual lock operation
                                        · Manual unlock operation
                                        · Keypad lock operation
                                        · Keypad unlock operation
                                        · Auto lock locked operation
                                        · Lock jammed
                                        · Keypad temporary disabled
                                        · New program code entered: unique code for lock configuration

2022-06-26T18:36:29.909Z DRIVER » [Node 090] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      116
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 23
                                    └─[NotificationCCEventSupportedGet]
                                        notification type: Home Security
2022-06-26T18:36:29.916Z SERIAL « [ACK]                                                                   (0x06)
2022-06-26T18:36:29.916Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-06-26T18:36:29.916Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:29.917Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-06-26T18:36:29.937Z SERIAL « 0x011d00a97400000100ad7f7f7f7f01010300000000020100007f7f7f7f7fec    (31 bytes)
2022-06-26T18:36:29.937Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:29.938Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            116
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -83 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1

2022-06-26T18:36:30.340Z DRIVER « [Node 090] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -83 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 238
                                    └─[NotificationCCEventSupportedReport]
                                        notification type: Home Security
                                        supported events:
                                        · Intrusion

...etc, but suddenly it takes over 5 seconds to respond, despite the same low RTT:
2022-06-26T18:36:30.784Z DRIVER » [Node 090] [REQ] [SendDataBridge]
                                  │ source node id:   1
                                  │ transmit options: 0x25
                                  │ callback id:      118
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 25
                                    └─[NotificationCCEventSupportedGet]
                                        notification type: System
2022-06-26T18:36:30.791Z SERIAL « [ACK]                                                                   (0x06)
2022-06-26T18:36:30.791Z SERIAL « 0x010401a90152                                                       (6 bytes)
2022-06-26T18:36:30.791Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:30.791Z DRIVER « [RES] [SendDataBridge]
                                    was sent: true
2022-06-26T18:36:30.811Z SERIAL « 0x011d00a97600000100ac7f7f7f7f01010300000000020100007f7f7f7f7fef    (31 bytes)
2022-06-26T18:36:30.812Z SERIAL » [ACK]                                                                   (0x06)
2022-06-26T18:36:30.812Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            118
                                    transmit status:        OK, took 10 ms
                                    routing attempts:       1
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -84 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1

... more communication, each time with almost immediate ACKs

2022-06-26T18:36:35.534Z DRIVER « [Node 090] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -84 dBm
                                  └─[Security2CCMessageEncapsulation]
                                    │ sequence number: 240
                                    └─[NotificationCCEventSupportedReport]
                                        notification type: System
                                        supported events:
                                        · System hardware failure

You should be able to get around most of this by upping the report timeout to 10000. 2000 is not enough for these hiccups.
You can also do that in the settings.json, so you don't have to edit the code:
https://zwave-js.github.io/zwavejs2mqtt/#/usage/setup?id=z-wave -> Hidden settings. Basically you need to add
"timeouts": {
  "report": 10000
}

inside the "zwave" key in the settings.json (you can reformat it to be readable).

And for anyone else who might find this issue in the future while trying to get these stupid locks working, here's the "zwave" portion of settings.json with the increased timeout. I have removed the "securityKeys" section, you should obviously leave yours intact. The part I added is the entire "options" section. After the interview is complete, I think the section should be removed, to not cause unnecessary delays.
    "zwave": {
        "port": "/dev/zwave",
        "commandsTimeout": 60,
        "logLevel": "silly",
        "logEnabled": true,
        "deviceConfigPriorityDir": "/usr/src/app/store/config",
        "logToFile": true,
        "serverEnabled": true,
        "enableSoftReset": true,
        "enableStatistics": true,
        "serverPort": 3000,
        "nodeFilter": [],
        "disclaimerVersion": 1,
        "options": {
            "timeouts": {
                "report": 10000
            }
        }
    }


Test fix for release 0.21.0-rc1.  Updated test to use invalid account

Description:
This PR updates the rcp_batch3.spec, "007 'data' from request body with wrong encoded parameter" to use an invalid address in the "wrong encoded parameter" as the old address on previewnet was getting used accumulating a balance.

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Patch and project coverage have no change.

Comparison is base (66753ae) 74.63% compared to head (3015a06) 74.63%.

:exclamation: Current head 3015a06 differs from pull request most recent head f9a9372. Consider uploading reports for the commit f9a9372 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1032   +/-   ##
=======================================
  Coverage   74.63%   74.63%
=======================================
  Files          30       30
  Lines        2030     2030
  Branches      386      386
=======================================
  Hits         1515     1515
  Misses        410      410
  Partials      105      105

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Run clang-format on all pending PRs continiously.

Fixes #7.

One more PR after this, then I should be done with the merge bot for today.

@wally-the-cartographer merge

Merge requested by authorized user SirVer. Merge queue now has a length of 1.


Added autoscanline option to make autotiles as wide as the whole image.

If autoscanline is off, to load a 64x64 tile that has been purged you need to read in again the whole 4096x64 scanlines.
With it on, auto-tiles are set, for example, to 4096x64. This forces the cache to work with batches of 64 scanlines.
This corresponds better with the loading costs of untiled images and
improves cache performance, specially when more threads are accessing the same image.

To fill people in (there has been off-list discussion leading up to this), the idea here is that in many situations, "autotile" is not performing well at all, in part because when a 'tile' leaves the cache and is needed again, the whole row of tiles must be read (because it's a scanline-oriented file).  This solution gives a way to make the auto-tiles be the full image width wide.
Ramon reports scenes where this improves performance by 5-7x!

LGTM!
I'll give people a little while to comment or discuss, but as far as I'm concerned, this is great -- it can't hurt, it's off by default, and you guys report very big performance improvements.  In the absence of anybody bringing up any important issues, I'll merge it tomorrow.

Merged into the trunk, and currently backporting to 0.10.


Please Add Support for Learned Devices

I've been using this integration and its fantastic - one issue I've noticed though is that some AC settings are not supported by switchbot (silent mode, turbo mode, certain types of oscillation) and a workaround I have used is to create these using 'Learn Buttons' instead of smart matching or selecting a device manually.
For example I have a setting for rapid cooling which maxes out the fan and chooses some settings not supported by switchbot, after learning the signal it is available as a basic On/Off switch which would be great for use in automations.
However, these types of remotes don't appear to be discovered by the integration currently - is it possible to add support for these?
Some of the code, specifically the configure flow already appears to see these, but they don't show up as devices or entities
Custom Remote Type:

Appearance when Configured:

Learned Remotes in Config Flow:

But not present in devices:

Hello @atxnyc thanks for support.
Tra, i'll try to implements this asap.

@atxnyc unfortunately I guess this features will be delivered in September. I'm on vacation in my parent's town and I did not bring with me the switchbot hub that is necessary in order to get the response body with this learned device and integrate it in HA.
Otherwise you should send the api response (if you are able to get it by yourself) and paste it here and I'll try to analyze.

@KiraPC no worries at all -- I'll see if I can get the response out, but otherwise I'll look forward to September

@atxnyc I released the 0.2.1-beta.1 version. Could you please check if it is working?

@atxnyc please can you test the 0.2.2-beta.2 version?


Fix TypeError in XcodeVersion()

Fixes: #1917
Recent changes have resulted in improper encoding of versions in the XcodeVersion() function.
This PR is meant to streamline the logic and properly encode versions that have single digit as well as double digit major versions.
Checklist

[ ] npm install && npm test passes
[ ] tests are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Description of change

I'm not sure that this is a solution to the issue I posted:
If XcodeVersion returns a tuple, and gets used in a comparison function, like these:

https://github.com/nodejs/node-gyp/blob/e6108382f9852ef4a1945e5a37fcd6547a96bc94/gyp/pylib/gyp/xcode_emulation.py#L858

https://github.com/nodejs/node-gyp/blob/e6108382f9852ef4a1945e5a37fcd6547a96bc94/gyp/pylib/gyp/xcode_emulation.py#L1524

Then surely it will error, like it did for me.
By comparison, if you look at the others uses of it, where I believe its used properly. The properly deconstruct the tuple for use in comparisons.

https://github.com/nodejs/node-gyp/blob/e6108382f9852ef4a1945e5a37fcd6547a96bc94/gyp/pylib/gyp/xcode_emulation.py#L122-L145
https://github.com/nodejs/node-gyp/blob/e6108382f9852ef4a1945e5a37fcd6547a96bc94/gyp/pylib/gyp/xcode_emulation.py#L1091-L1104
https://github.com/nodejs/node-gyp/blob/e6108382f9852ef4a1945e5a37fcd6547a96bc94/gyp/pylib/gyp/xcode_emulation.py#L1129-L1131

These previews are rendered from your commit.

@Lavoaster You are correct.  Thanks for this very precise review.  I have made appropriate changes.

@bdon

@gengjiawen these commits needed metadata before merging, PR-URL and Reviewed-By at a minimum, and the middle one is missing the subsystem prefix. Please don't merge using the GitHub UI so this can be avoided.
I'll address it and force-push.

sorry, there's two commits at fault here, one is from #1937 and this one got squashed (thanks), but they're both missing subsystem, in this case gyp: from the commit messages plus the metadata. We do this mainly for nice changelogs.

see 9c0f3404f and bb2eb72a for the modified forms, force pushed to master

@gengjiawen these commits needed metadata before merging, PR-URL and Reviewed-By at a minimum, and the middle one is missing the subsystem prefix. Please don't merge using the GitHub UI so this can be avoided.
I'll address it and force-push.

Sorry for this trouble. Is https://github.com/nodejs/node-core-utils/blob/master/docs/git-node.md#git-node-metadata can generate the meta info ?

that's the metadata we need but I don't know if it'll work on this repo, I just do it manually, but keeping to nodejs/node conventions is the aim (also no merge commits)

Hate merge commits too :)


feat(starknet_monitoring_endpoint): add config for collect metrics

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2472  👈 (View in Graphite)
#2469
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 9, 7:18 AM EST: A user merged this pull request with Graphite.


Feature/macos compile instructions

Took the liberty to add some build instructions for MacOS to reaffirm the fact that Solar System works on MacOS :)

Thanks - I've got a lot of people asking how to do that. I made a little change (capitalising headers)


[5.5] string helper to remove widow in string

Widows are an annoyance to designers, so this pull request attempts to make it easier to ensure widows don't end up in your page copy.
This string helper prevents widows at the end of a line by adding   between the last two words.

This looks really messed up.
Nothing else in the Str helper does html stuff, why whould this? Why is this something that should be in the Laravel framework, and not something your ui fixes with some css?
https://developer.mozilla.org/en-US/docs/Web/CSS/widows
https://developer.mozilla.org/en-US/docs/Web/CSS/orphans

No tests, formatting does't match, not sure what it does.


[Heroicons] ...

Extension
https://www.raycast.com/johndoe123789/heroicons
https://github.com/raycast/extensions/tree/f30ca36f8da62ca7682ec516c8ab6d1d84d08d12/extensions/heroicons/
Description

Heroicons doesn't load and just shows this message
Steps To Reproduce
just open it
Current Behaviour
it doesn't allow search and then it closes
Expected Behaviour
it should allow search and show icons

We could not find the extension related to this issue. Please update the issue with the correct link to the extension.

added the gh link as well


Add iot-lab_A8-M3 board support

adds bsp/board/iot-lab_A8-M3 (based on iot-lab_M3)
tested to work on iot-lab A8-M3 nodes (with openwsn-sw installed on A8 node)

@fambon, thanks a million for the port to this new platform!
And sorry for the late action :(

Hi Thomas, thanks for your message.  Back in december I threw in some notes about using the port here: https://github.com/iot-lab/iot-lab/wiki/Running-openwsn-on-A8-nodes ;  feel free to enhance.

@fambon, this is fabulous, thanks for your contribution. I will merge your PR and have created https://openwsn.atlassian.net/wiki/display/OW/IoT-lab_A8-M3. if you sign up for an account on that website, you can further edit the page.
About https://github.com/iot-lab/iot-lab/wiki/Running-openwsn-on-A8-nodes, the patch in openwsn-sw might be something you want to contribute directly to the code?


Can't set LuisRequest to use Staging Endpoint Slot for LuisDialogs

I noticed within the LuisService.cs code that the "staging" parameter isn't included when building the query URI for LuisDialogs (via LuisRequests).  Since we can't specify the staging parameter to be true, it appears our development application is making requests to the production endpoint slot rather than the staging endpoint.
Could we have the LuisModelAttribute updated to include a flag stating if the LuisRequests should use the staging endpoint slot for LuisDialogs?
Thank you!

@Andrea-Orimoto

Same issue logged here: https://github.com/Microsoft/BotBuilder/issues/2534
This is currently a roadblock for us.

Looks like @chrimc62 added the Staging parameter as an option in develop.  That should resolve this issue.

This commit af2b62b will fix this issue.


app not installed

I tries to install trough rootmy.tv but I got error message as attached
I have LG tv UF6407 with Webos 2 V 03.16.00

Same issue,
Software; 04.40.08
Model: 75UN9070AUD
webOS TV Version 5.4.1-8 (jhericurl-jebil)

Check this: https://github.com/RootMyTV/RootMyTV.github.io/blob/troubleshooting-guide/docs/TROUBLESHOOTING.md


Add additional_ldap_filter suport.

I found myself having to filter out certain users during the initial
user lookup in LDAP.
This is because for some attributes like "mail" we
had duplicate user entries in our directory of over 30k Users.
This commit adds the capability to add a RFC2254 formatted String as an
optional additional filter.
This is joined using (&) to the default filter constructed.

Just what I need, ty @dimitertodorov!  +1 to integrate this PR.


Different initial selected value in

Hi, first of all, thanks for this fantastic work.
I note that <select> has a different behavior when using template from DOM element than template string options on Vue initialization.
When use template from DOM element, Vue render select with no value selected (v-model = null).
When using template from a string options, Vue render select with first value selected (v-model = null too).

http://jsfiddle.net/8gv321no/

This is caused by some browsers' default behavior that whenever a <select> element is appended to a new parent, and its selectedIndex is -1, the browser resets it to 0. It seems Firefox is the only browser that persists the -1 value properly.
Ideally all browsers should persist the value, but I guess I can't change that so we can only add more ugly patches to Vue :(


Tweak UMD / global semantics

The behavior for UMD declarations is now that you cannot use UMD symbols from external modules. This removes the confusing concept of "was this file referenced or not?".
I've also renamed GlobalModuleExportDeclaration to NamespaceExportDeclaration because it was confusing.
Fixes #8255

I've also renamed GlobalModuleExportDeclaration to NamespaceExportDeclaration because it was confusing.

Still confusing, but better. :smile:

Any other comments?

Fixes https://github.com/Microsoft/TypeScript/issues/7843

The message is a bit vague, and can be enhanced, other than that :+1:


cannot use doc  as type *"golang.org/x/net/html"

I'm not familiar with go
After performing go get on all the dependencies in server.go's import statement I get this when tryin to do go run server.go
# github.com/guregu/relay/fourchan
../../.go/src/github.com/guregu/relay/fourchan/4chan.go:352: cannot use doc (type *"code.google.com/p/go.net/html".Node) as type *"golang.org/x/net/html".Node in argument to goquery.NewDocumentFromNode
# github.com/guregu/relay/eti
../../.go/src/github.com/guregu/relay/eti/eti.go:460: too few values in struct initializer
../../.go/src/github.com/guregu/relay/eti/eti.go:608: cannot use doc (type *"code.google.com/p/go.net/html".Node) as type *"golang.org/x/net/html".Node in argument to goquery.NewDocumentFromNode
../../.go/src/github.com/guregu/relay/eti/thread.go:115: cannot use "code.google.com/p/go.net/html".ElementNode (type "code.google.com/p/go.net/html".NodeType) as type "golang.org/x/net/html".NodeType in assignment
../../.go/src/github.com/guregu/relay/eti/thread.go:117: cannot use "code.google.com/p/go.net/html/atom".Image (type "code.google.com/p/go.net/html/atom".Atom) as type "golang.org/x/net/html/atom".Atom in assignment
../../.go/src/github.com/guregu/relay/eti/thread.go:119: cannot use []"code.google.com/p/go.net/html".Attribute literal (type []"code.google.com/p/go.net/html".Attribute) as type []"golang.org/x/net/html".Attribute in assignment

very interesting project btw!

Lots of this code is really old... I will try to fix it up this weekend. Thanks for the interest!
Basically Google abandoned Google Code so we need to replace import "code.google.com/p/go.net/html" with import "golang.org/x/net/html"

I've replaced remotes as per your suggestions in the relay repo:
https://github.com/97-109-107/relay/commit/ff2f553f9c096dadf0b848fcd23ad0102cfc7a0f
and updated a http client call:
https://github.com/97-109-107/relay/commit/7c6663c2d3a21968507cecf840ec1640a16b780d
and similiarly subsituted the remotes in the bbs repo:
https://github.com/97-109-107/bbs/commit/60ecd5acc1dd9a5898d57f35d7ad88eb24073a68
I managed to get the relay running by doing (provided eti is disabled in the config file):
github.com/guregu/relay (master⚡) go run server.go config.go
2015/06/21 19:26:38.049073 /index.json
2015/06/21 19:26:38.049208 Starting Goji on [::]:8000

I'm now stuck trying to connect the clients to my local endpoint.

Alright, that should do it. You should be able to POST stuff to localhost:8000/4chan
You can get a web client by git cloning this somewhere: https://github.com/guregu/bbs-client
And changing the [web] configuration for relay to point to that.
However the web client doesn't support 4chan very well (no images, I think the board list may have been broken as well).
Might be easier to play around with limbo: https://github.com/guregu/limbo
Or use the command line client, bbs-test-client, in this repo (which is really bad).
It's all very rough around the edges though. I really need to just re-do everything.  The protocol itself could be improved too.


Double Split

Hi,
it seems that in Lnbits Versions 0.11.2 and 0.11.3 the Split plugin sometimes runs twice for the same transaction leading to double bookings.
The double booking in this image is from verison 0.11.3, the single booking after downgrading to 0.11.1

Upon further checking:
The 0.11.1 version later also doubled the split. Downgrading the plugin to version 1 seems to help, will test further.

Ok, upon further testing this issue is really dangerous for all Lnbits as a service users. It doubles the transactions and actually takes funds from the underlying node, falsifying the wallet balance in LNBits.

UPDATE: I cannot recreate the error currently on my devserver neither on legends, will post updates if I manage to recreate it.

Managed to recreate it:
Downgrade to 0.11.1 with Split 0.1.2 installed. Reupgrade to 0.11.3, issue appears.
After uninstalling and reinstalling the plugin, error disappears, just like with plugin downgrade.
The beahviour where the wallet balance goes negative does not constantly happen.
To test, here is my faulty setup: https://lnbitsdev.opago-pay.com/wallet?usr=20c245c3431d46778df93eea94cd18cb&wal=33f7db34094043a98a9b9e1f3d605ab2

Does the lnbits server start with SSL certificates by default ("--ssl-keyfile=... --ssl-certfile=.... flags)?

What helped me https://github.com/lnbits/scrub/issues/7#issuecomment-1945646044

lnbits 0.12.2 will fix this


Bug Fix

Bug Fix
The link on prospect overview not rendering correctly on IE5 browser. This has been fixed and will look the same in all browsers.

Howdy from Release Ninja! You should write a release note targeted at a semi-technical end user who is
not familiar with the code base. Include at least 1 image, wherever possible. Review the help article if
you are not familiar with Release Ninja.
When your pull request is ready, do one of the following:

Notify Release Team
Don't notify anyone because it's a small change or doesn't concern them
Whatever you do though, make sure you :tada:

Howdy from Release Ninja! You should write a release note targeted at a semi-technical end user who is
not familiar with the code base. Include at least 1 image, wherever possible. Review the help article if
you are not familiar with Release Ninja.
When your pull request is ready, do one of the following:

Notify Release Team
Don't notify anyone because it's a small change or doesn't concern them
Whatever you do though, make sure you :tada:

Howdy from Release Ninja! I just sent out emails to
:tada:

Howdy from Release Ninja! I just sent out emails to<EMAIL_ADDRESS>:tada:


Ensure CancellableQueue doesn't keep references to logically removed objects

Keeping the references around means that memory usage can grow as the queue is reused, even if the queue is being drained regularly.
Fixes #27401

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @Abacn
test failures looked unrelated but rerunning

Tested this fix indeed eliminate the heavy memory usage by BeamFnApi$Element on Dataflow runner


HDDS-6529. Adding Unit-Test cases for S3-Gateway Object-Endpoint Metrics

What changes were proposed in this pull request?
Added Unit Tests for Object Endpoint Metrics for S3-Gateway
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6529?filter=-1
How was this patch tested?
Wrote Unit tests for existing Object Endpoint metrics

@jojochuang @adoroszlai @siddhantsangwan @aryangupta1998 It would be great if you guys could review this !!

@ArafatKhan2198 there's code conflict, can you rebase the PR?

@ArafatKhan2198 please avoid rebasing and force-pushing to PR after review.  It is more difficult to compare changes since last review after force-push.  Please prefer incremental commits and merge from target branch if necessary.

Thanks @ArafatKhan2198 for the patch, @kerneltime for the review.

Thanks @ArafatKhan2198 for updating the patch. There are a few items we could further improve, but I think it can be done in followup jiras.

Thanks for the review @adoroszlai @kerneltime @jojochuang , yes we can definitely add more improvements in subsequent JIRAs !!


Shows info when you don't have access

When your IP is not whitelisted it will still show the user who doesn't have access the free space of the website.
http://83575.aoweb.nl/u/B6aW9gc4DO.png

Ah I know what you're describing,
I don't think it was intended as a bug, as was more of a 'what is the harm in showing it'
But yeah you're right I'll open up a PR to address it soon.

#70

Now fixed thanks to @Jespertastesen Apologies for the delay reviewing


Release build error

I am getting following error while try to sign the app. Its working in debug mode but in release mode in application class I am getting following error. I have checked #22 but not able to resolve it. I am using target SDK 30
JNI DETECTED ERROR IN APPLICATION: JNI RegisterNatives called with pending exception java.lang.ClassNotFoundException: Didn't find class "com.trinity.record.TrinityRecord" on path: DexPathList[[zip file "/data/app/packagename-zrA4TygNqudIuL_hAw-pwA==/base.apk"],nativeLibraryDirectories=[/data/app/packagename-zrA4TygNqudIuL_hAw-pwA==/lib/arm64, /data/app/packagename-zrA4TygNqudIuL_hAw-pwA==/base.apk!/lib/arm64-v8a, /system/lib64, /system/product/lib64]]

set minify enabled to false in app level gradle file

minifyEnabled false
shrinkResources false


Feat / Statistic - Create statistic-type selection collapse

🗒NOTES
🏁PREREQUISITES

[x] DOR
[ ] DOD
[ ] End users validation
[ ] Customer validation

📜CONTEXT (User Story)
As a dev
I want to allow the yaki's ui components available to the entire world
In order to do this, i need to create a design for a collapse use to select a statistic-type
🪜STEPS TO FOLLOW

[x] Step 1: Design the collapse
[ ] Step 2: Ask the end user feedback
[ ] Step 3: Make changes if needed
[ ] Step 4: Make a presentation to the customer
[ ] Step 5: Create the collapse in yaki_ui
[ ] Step 6: Make a yaki_ui release
[ ] Step 7: Upgrade yaki_ui version in yaki_mobile and yaki_admin

✅ACCEPTANCE CRITERIA

✅ The collapse follows the same idea as Basti UI's yaki design
⛔ The collapse follows exactly its initial design

📛BLOCKERS
🔍AFFECTED COMPONENT(S) (Scope)
⛓LINK TO OTHER ISSUES
🪟SCREEN SHOTS & MOCKUPS

Current state of progress. Only a sliding transition and a functionnal scroll bar remains. Tests with selecting API call parameters will follow, along comments.


QBSelect, QBFrom, other properties cannot be accessed, modified from the model.

I think is relevant to not have that big limitation anymore.

What do you want to do from the model?

Why do you need to access the DB's internals from the model?

Please provide your use case of exposing those to the public API. Closing for now.


Bug: npx prisma generate doesn't write anything to file on Mac

Bug description
Running npx prisma generate doesn't generate any files on my Mac. I've located the problem and found the fix already, just need it to be verified and the code updated. Note that when I ran the npx prisma generate in a Node:16 docker container, it worked fine, but it just doesn't work on my Mac.
The codegen process seems to be exiting before it can finish writing the files. An await Promise.all() surrounding each of the two options.dmmf.datamodel.[enums/models].map calls fixes this for me.
Expected behavior
Running "npx prisma generate" produces files
Environment & setup

OS: Mac OS
Database: PostgreSQL
Node.js version: 16.16.0

Prisma  Version
4.2.1

@CatastrophiClam were you able to get a workaround? I am running into the same (see https://github.com/YassinEldeeb/prisma-tgql-types-gen/issues/138) and about to start debugging but just in case you already found a solution

is there any update on this issue?


message.token can send bot token

I accidentally try for bot to send token using this library and it sent real, no hide bot token

I accidentally try for bot to send token using this library and it sent real, no hide bot token

Sorry for this we will fix it now. Thank you for submitting to us about an issue you or anyone else may be experiencing. We appreciate you for these small actions.

Just Fixed!

Just fixed


v2 Part 2 1/2 (or 3):  Scoped, inheritable and dynamic configuration handling changes

Why:

For users it's helpful to define a variable and use it across a whole testset, or set it ONCE at the command line
Currently to add a new option at command line, testset config and test level, you need to add code in 8 places (parsing in 3, variables in 3 objects, actual use plus docs... and with tests for each).  Fixing the parsing in part 1 will fix ONE part of this (reducing it to parsing in one place, docs, and variables in 3 places).  This reduces it to 3 places total (docs, parsing, and)  which is about as good as it gets.
By allowing automatic templating, everything is dynamic if needed (much more powerful), easy to add pluggable templating
Greatly reduces codebase complexity, I hope and increases flexibility (similar to contexts and the validator registries).

Problems

Current gen of extensions cannot consume this.  New extension APIs will need to be defined to use it (probably want to add kwargs/args support so extensions can grow organically)
Need to clearly document scoping rules and parsing rules with regards to scoping

What:

Templating: any configuration element can be defined as dynamic, allow more than one templating option
Future enhancement: allow use of a pre-compile pass on a run to optimize away un-needed dynamic-ness for performance

Nested context structure
I've got full architecture notes on this now, but the gist is:

Configuration context will be passed in as a list of dictionaries, with each dictionary being a scope
Current scopes will be: command-line, testset, test, with priority increasing towards the right
Overall, configuration will be a tree (command line, testsets, and tests under testsets)
There will be a number of reserved keywords for configuration elements, to support built-in and special items

Contexts

Configuration context (generated during test parsing) - may be specially modified in tests, but discouraged -- SCOPED
Execution context (caching, information needed for run state, optimization info) - SCOPED
Test context - variables in tests, etc - redefinable easily  - NOT SCOPED, GLOBAL

(This will be edited some after the parsing rearchitecting in https://github.com/svanoort/pyresttest/issues/75 is done)
Link on templating performance:
http://stackoverflow.com/questions/1324238/what-is-the-fastest-template-system-for-python

CAVEAT: Some fields can accumulate values additively, for example multiple headers can be added.


Error - object Object with object details

subcription Data null
{ error:
{ code: 'ExtensionError',
message: 'Operation: Create; Exception: [Status Code: NotFound; Reason: Not Found]',
innerError:
{ 'request-id': 'f5af4895-9c74-46fe-a395-aacdff2d61ea',
date: '2018-06-18T19:09:28' } } }
Any response will be appreciated.

Not a whole lot of information or context to go on here, such as when you see this error, etc. Not Found would make me think you don't have an Exchange Online mailbox, but I'm really just making guesses.
I'd suggest trying logging in to Graph Explorer and see if you can access your inbox messages there.

Yes. I am able to access my inbox messages from graph explorer.


package installation in non-editable mode: pip install ./cli

The goal is to make medperf client installable from pypi. This PR is the first part that allows installing package not from repository
A few changes were implemented:

Totally removed git branch check updates: as client installed in non-editable mode would not have any connections with source folder where it was installed from, it knows nothing about git branch.
During deployment, local server places cert.crt, cert.key and mock_tokens/tokens.json to ~/.medperf_config/.local_server/ so detached medperf client can use it. NB: this change breaks the behavior for existing developers (as path to local server cert is already defined in user config). You should update local config's certificate path to ~/.medperf_config/.local_server/cert.crt.
pip install -e ./cli replaced with pip install ./cli everywhere

Folks, I'm thinking. Do we need to pack local server to the pip package at all? I mean, it is used only for development purposes. What do you think if we leave it in a repo? so every developer who needs local server would have to check out repo.

TODO:

return git update check
fetch only current branch instead of all of them?


aws_future keeps channel alive until callback fires

Issue:
The future_register_channel_callback test was failing occasionally.
Description of changes:
Previously, the future released its hold on the channel after the task was scheduled. Now, it doesn't release its hold until the task has actually run.
There's still stuff about channel lifetime and tasks that doesn't seem 100% kosher, but this fixes the issue for aws_future.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (cbea39a) 79.80% compared to head (2062b1e) 79.81%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #574   +/-   ##
=======================================
  Coverage   79.80%   79.81%
=======================================
  Files          26       26
  Lines        5750     5752    +2
=======================================
+ Hits         4589     4591    +2
  Misses       1161     1161

Impacted Files
Coverage Δ

source/future.c
92.39% <100.00%> (+0.08%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Missing down command

There is create and destroy, start and stop, but there is up (which is create + start) and no down (which could be stop + destroy).

destroy already does stop if there are machines running
But we might add a alias just for completeness sake


Features/update announcements to match spec 178933309

Problem
We've updated the announcement spec since the SDK announcement module was written, so now the SDK is out of sync with the spec. Specifically, we're missing createdAt on all announcements.
#178933309
Solution
Added createdAt to all announcement types and updated tests accordingly
Change summary:

Added createdAt to all DSNP announcement types
Added an optional createdAt arg to DSNP factories
Updated tests accordingly

Steps to Verify:

Call a create method from the announcements module
Check that the resulting object has a createdAt field

looks good to me except for the duplicate createdAt's that github found 👍

Fixed


youtube-dl violation of protocal

Input:
youtube-dl https://www.youtube.com/watch?v=fIHH5-HVS9o
Output:
[youtube] Setting language
WARNING: unable to set language: <urlopen error [Errno 8] _ssl.c:510: EOF occurred in violation of protocol>
[youtube] fIHH5-HVS9o: Downloading webpage
ERROR: Unable to download webpage: <urlopen error [Errno 8] _ssl.c:510: EOF occurred in violation of protocol>

Carefully read new issue template and provide all requested information.


Add TI J721e R5 and BeagleBone AI64 R5 initial support

This PR adds SoC support for TI J721e, specifically the R5 cores found in the MAIN domain (there is an R5 in the MCU domain we will add support for later). We also add board support for the Beaglebone AI64 which uses the J721e SoC.
TRM for J721e: https://www.ti.com/lit/zip/spruil1
BeagleBone AI-64: https://beagleboard.org/ai-64
Note: this is the continuation of the PR #59191 which went stale and was closed. Updates include HWMv2 and other small bug fixes. This is based on #71526 which is the first patch here (included here also so this series can still build).

Adding DNM as the dependency is yet to be merged and the PR needs to drop the DM timer commits : https://github.com/zephyrproject-rtos/zephyr/pull/71526

@glneo Now that the DM timer series is merged, removing DNM, can you please drop those commits from here? Also this is going to be accepted only after 3.7.0 release.

@glneo Now that the DM timer series is merged, removing DNM, can you please drop those commits from here? Also this is going to be accepted only after 3.7.0 release.

As we have some time, I've made a couple additional changes. Since we have AM6x devices that also have the same R5 cores, making a new SoC series just for J7x makes it harder to later add the AM6x R5 devices. I'm just going to add this SoC to the existing SoC series. (I'd argue that K3 is the series and so having a AM6x "series" is unneeded also, but that is a cleanup for later).
Also, since the J721e SoC has 6(!) R5 cores, the naming needed updating so we can specify which we are targeting. When all core support is added soc.yml will look like:
    - name: j721e
      cpuclusters:
      - name: main/r5f0_0
      - name: main/r5f0_1
      - name: main/r5f1_0
      - name: main/r5f1_1
      - name: mcu/r5f0_0
      - name: mcu/r5f0_1

These names match what we call them in Linux also.

LGTM. We probably want to wait for @tejlmand regarding the blocking comment.

I replied to that comment months ago, then pinged it again 4 weeks back, still no update from @tejlmand. I'd hope we don't block indefinitely. Worst case we take this now and then have to later change the cluster name from main/r5f0_0 to main_r5f0_0 which wouldn't be a big deal at all.

I guess @andyross can decide what to do here.
I would also prefer to get this merged now since it is also blocking beagley-ai support. And I personally also prefer the current naming.

Sure, if we think it makes sense to change the name will change it.

@glneo there is a message about clang-format that says it has not been addressed.  Did you look at that?
https://github.com/zephyrproject-rtos/zephyr/actions/runs/11060123536/job/30729987820?pr=71527
Perhaps this is one thing holding up this PR

@microbuilder @andyross This PR looks like it should be assigned to Kevin instead of Andy.  Do you guys agree?

@microbuilder @andyross This PR looks like it should be assigned to Kevin instead of Andy. Do you guys agree?

Hey Bill. Not sure there's anything here I'd be particularly expert at. The basic PR looks fine to me, though.
@carlescufi Can you ping Torsten on this one?

@carlescufi @nashif @cfriedt Can we please merge this PR?

@vaishnavachath - it's in the queue and will get pulled soon.

Thank you @cfriedt

@vaishnavachath - it's in the queue and will get pulled soon.
https://merge-list.zephyrproject.io/

Not until assignee approves, no :)

This should be assigned to @jadonk as Beagle maintainer but this doesn't seem possible. @jadonk can you confirm you are a collaborator in the GitHub org? Looks like you might not based on the grey, not green, checkmarks next to your reviews?

@nordicjm @gmarull have you reviewed since latest push? Do we have a good pattern for PINCTRL? I'll be working with @Ayush1325 and all to get fixes for other Beagles.

@nordicjm @gmarull have you reviewed since latest push? Do we have a good pattern for PINCTRL? I'll be working with @Ayush1325 and all to get fixes for other Beagles.

Drivers that need it must select it, it must not be in any defconfig files. If a board needs it for a board's .c file then it must be selected by the board Kconfig file

@gmarull  it seems the updates were made. Any changes remaining?


add  support laravel 6

anyone will help us

Now. the package is working well with Laravel 6. Please update to the latest version.