Fix/split part compatibility tony

Create a separate BigQuery macro for first and last value aggs. Handles a swap for the use of dbt.split_part and adds working concatenation delimiters in the string value.

Hey @tonytusharjr - I cut a new patch version of the package (0.1.8) which includes Bigquery compatibility fixes and extending my CI tests to run on Bigquery. It includes fixes for the bugs that are addressed in this branch. As such, I'm going to close this PR. Give the new release a try when you have some time, and feel free to ping me on dbt Slack or in a new issue if anything comes up!


Bootstrap layout

A little bootstrap practice for me... nothing amazing, but some improvements on the layout!
-added jQuery script
-added Bootstrap stylesheet
-created a few custom styles
-edited "default.html" to make a slightly better layout.

Wow, this looks great now! I can tell you put some time into it. Maybe this will get more people to check it out.

Also to reference issues you just say #1

Hey David,
Thanks for the merge, and the opportunity to play a bit!
Regards,
Aaron
On Oct 19, 2017, at 05:57 AM, David Gisser<EMAIL_ADDRESS>wrote:
Merged #2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


None appears in post description if no intro have not been set by MiHoYo

Here's an example of what it happens frequently:

Fixed with https://github.com/Themimitoof/genshin-feed/commit/e3b12ef6f14021553bb529a2b9335ffad2c97846


Improve Basel dialect

This commit improves the language by following the holy Baseldeutsch-Wörterbuch (Rudolf Suter, CM Verlag).

🥳🎉
Thanks!

Deployed :)


docs: Traceability-Kit Operation View - fix link to trace-x backend

Description
Fix wrong link to traceability-foss backend.
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

@almadigabor could you please have a look. Thank you!


#19782 fix events reading for quoted schemas for MySQL/MariaDB

Please check the events reading:

[x] in catalog with name data
[x] in the catalog with the name with special characters
[x] in the catalog without special characters

verified


bump datashape version to >=0.5.0, see #437

Python 3.5 support required changes to datashape that were released with version 0.5.0. Update packaging files to ensure that version of datashape gets installed with odo. Closes #437.

Thanks @branning


Programmatically generate the OSN UI widgets

We need to programmatically generate the widgets in the OSN UI in order to properly implement the OSN UI unit tests. Currently, the widgets are being automatically generated using QT's ".ui" files. Unfortunately, we cannot access these widgets from a separate unit test executable. Progammatically generating the widgets should give us access to them from a separate executable so we can properly implement the valid paths UI tests ( #162 #163 #164 #165 )

UI widgets are now programmatically generated to prep for QT test implementation


Utilize DSIGNAlgorithm Ed25519Bip32DSIGN for extended keys in cardano-api

The same as #2227, but reopened to bump it.
At the moment, Shelley extended signing keys are serialized using the cardano-crypto 128 byte binary format. However, these extended signing keys can actually be serialised to a more compact 96 byte format (see the DSIGNAlgorithm Ed25519Bip32DSIGN implementation).
The DSIGNAlgorithm Ed25519Bip32DSIGN implementation allows:

Serialisation of BIP32-Ed25519 extended signing keys to a more compact 96 byte format as opposed to the old cardano-crypto 128 byte format.

Deserialisation of BIP32-Ed25519 extended signing keys in either of the 96 or 128 byte formats.

bump @dcoutts @Jimbo4350

@newhoggy I would also note that I think this PR is still highly relevant

@intricate I added a test and rebased

Still needs further reviews.

Is this in any sense a breaking change?

Okay rebase done.

From what I can gather, these are the golden files of relevance to the PR:
test/data/golden/shelley/keys/converted_cardano-address_keys/byron_signing_key
test/data/golden/shelley/keys/converted_cardano-address_keys/icarus_signing_key
test/data/golden/shelley/keys/converted_cardano-address_keys/shelley_payment_signing_key
test/data/golden/shelley/keys/converted_cardano-address_keys/shelley_payment_signing_key_bip32
test/data/golden/shelley/keys/converted_cardano-address_keys/shelley_payment_signing_key_legacy
test/data/golden/shelley/keys/converted_cardano-address_keys/shelley_stake_signing_key
test/data/golden/shelley/keys/converted_cardano-address_keys/shelley_stake_signing_key_bip32

Is this in any sense a breaking change?
For instance can it still deserialise the 128 byte format?
I'm thinking it might be useful to have a command that converts between these two byte formats as well.

This PR supports deserialisation in either of the 96 or 128 byte formats (see xPrvFromBytes).
I would probably vote against adding a command to convert between the two as the less compact 128 byte format isn't particularly useful. It should be fine to continue being able to deserialize it, but not serialize to it anymore.

Closing because of inactivity


Mapping between annotation tools and MiAIRR/TSV?

Hi All,
I thought I saw mention of a table mapping annotation tool field names and MiAIRR and/or TSV field names. Am I dreaming. We have something like this, but we have an issue with a IMGT/V-Quest mapping that I am hoping I might get some input on... Let me know if a table of mappings does exist...
Here is the problem:
IMGT often annotates V/D/J genes with multiple possibilities...
E.g. IGHV3-2301,IGHV3-2302,IGHV3-23D01
E.g. IGHD2-2102,IGHD6-1901,IGHD6-601
When V-Quest uses this approach, what is the expected value of v_call or d_call?
Would one expect the whole list of V-genes to be returned in the AIRR TSV file? I assume yes, as I think it would be incorrect to choose one, but wanted to confirm...
Brian

It's in the Tables subdirectory for the manuscript labeled Table S1.
Yes, return the whole list in the field. I don't know if we explicitly documented that behavior but that's what ChangeO does.

There's also a YAML version of the mappings in the the changeo source:
https://bitbucket.org/kleinstein/changeo/src/tip/changeo/data/receptor.yaml?at=default&fileviewer=file-view-default


Add mat4 set scaling

Mat4 has getScaling and scale, but no set, and u need to set it by do some "inverse" math.
Nothin complex but just add all the methods, not half of them

Due to how matrices work, setting the scale isn't quite as easy as setting a few components. One first has to calculate the scaling vector and then multiply it accordingly to get the correct result.
https://github.com/toji/gl-matrix/blob/d30bf3ba16449c2228a56754822059dd79d196a4/src/mat4.js#L1152-L1168
I suppose the API, while somewhat inconvenient, reflects on that. My personal suggestion is to

store translation, rotation and scaling as individual parts
operate on those
when it's time to send them to the GPU or something, convert them to matrices

I get that it requires some work to create the fuction, but why not adding it anyway to the api, to make them more complete and coherent

I fully agree that setter methods like mat4.setScale would be convenient. The downside is that I'd have to add all setter methods (consistency) which in turn would increase the file size. And then unit tests for everything would have to be written.
I barely have the time to answer to issues as is.

Of course, don't worry it's still a great work


Duplicated and confused info in file transfer progress

If pc is put to sleep in the middle of file transfer, after resume Syncthing restarts and in file transfer progress bubble there is File: Starting... in Downloading and Same File: Just now/XY ago in Recently Updated. After index exchange is completed, File resume downloading which leads to File: Downloading 7GB/8GB (2MB/s) in Downloading and Same File: ago (there is really only "ago") in Recently Updated. When File finish downloading, there are 2 lines File: ago (also only "ago") in Recently Updated. I will come back today later and test more.

Ah, sounds like fun. We do assume that Syncthing gives us events in a semi-reasonable order... Let me create a Dev build with some better logging in this area: that will let us see exactly what's going on.
I've also seen an issue where, if many (thousands) of files are downloaded in quick succession, some will get stuck on "starting"

Righty that's built. You can grab a build from here: https://ci.appveyor.com/project/canton7/synctrayzor/build/<IP_ADDRESS>/artifacts
I'm going to be on holiday for a week, but I'll be very interested in seeing any relevant logs when I get back!

Have you seen this re-appear with the build I linked to? I also fixed a race condition in that build, and so far it's been behaving itself for me...

Should be fixed in 1.0.23


Workaround GitHub rate-limiting

Requests sometimes fail due to GitHub rate-limiting.  Perhaps cache the objects?

Finnes i Jira...


rest: introduce the concept of stable and unstable apis

Description
Describe the changes or additions included in this PR.
Test plan
How did you test the new or updated feature?

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:
[ ] REST API:

I didn't see it but is it possible to add an endpoint which tells user whether unstable endpoints are enabled on the server.

No and i don't know if we should (although you can technically get this information via the openapi spec/explorer)

I didn't see it but is it possible to add an endpoint which tells user whether unstable endpoints are enabled on the server.

No and i don't know if we should (although you can technically get this information via the openapi spec/explorer)

Makes sense!


Use firebase-debug.js in dev builds

Use the non-minified Firebase lib in dev mode. It seems the original config was accidentally inverted.

thanks!


tcl/tk Not supported

Unable to use tcltk, as capabilities shows it isn't available.
> capabilities()
       jpeg         png        tiff       tcltk         X11        aqua
       TRUE        TRUE        TRUE       FALSE       FALSE       FALSE
   http/ftp     sockets      libxml        fifo      cledit       iconv
       TRUE        TRUE        TRUE        TRUE       FALSE        TRUE
        NLS     profmem       cairo         ICU long.double     libcurl
       TRUE        TRUE        TRUE       FALSE        TRUE        TRUE

There was an issue resolving tclConfig.sh and tkConfig.sh during the build process.
It's fixed in the heroku-buildpack-r-build project.
I'll do some further tests, and then make a new build of R 3.3.1 to include the fix.

Hi could you guys also make a new build of R 3.2.2?
Thank you for your time

Hi Breno
I'm working on updating all the cedar-14 packs, so will include 3.2.2.
Should be another day or so.
Regards
Chris Stefano
On 21 Jul 2016 00:47, "brenocarvalho"<EMAIL_ADDRESS>wrote:

Hi could you guys also make a new build of R 3.2.2?
Thank you for your time
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/virtualstaticvoid/heroku-buildpack-r/issues/73#issuecomment-234107534,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAE05ehfy1aCxKz_g51oa226uJZyES0Wks5qXqVrgaJpZM4JQCZh
.

Hi @brenocarvalho
I've created the builds as requested. You can use the cedar-14-refresh branch to give it a test to confirm.
Also #75 pull request, which I'll merge once testing is complete.

I've merged #75 after much testing.


Escape cython keywords

Append an underscore to any names that would clash with Cython
keywords.
Fixes issue #3:
https://github.com/gabrieldemarmiesse/python-autopxd2/issues/3

Re-done as #9 due to messed up git branches.


Update to newest nebula 1.8.2 release

Thanks for this project. Before I try it, I wanted to understand what is required to catch up to the newest nebula 1.8.2  release . It appears that shieldoo is using  nebula 1.7.2 when I reviewed the git logs

updated to 1.8.2


Your connection is not private

Your connection is not private
Attackers might be trying to steal your information from app.mage244.test (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_AUTHORITY_INVALID

Every time I click on the URL, I get "Your connection is not private" and have to click "Proceed to xxx (unsafe)" link.
FYI, I am using

Ubuntu v20.04
Chrome v99

And already allowed self-signed certificate with
chrome://flags/#allow-insecure-localhost

Let me know how to avoid this annoying issue.

What seems wrong with the issued certificate? Does the common name match with the domain? Is it expired? Or is the Warden CA expired?

@tdgroot
I signed the certificate with
warden sign-certificate mage244.test

When I check on the browser it says "Certificate is not valid"

Please try to answer my questions, it will probably lead you the answer.

You probably want to check out https://docs.warden.dev/installing.html?highlight=certificate#trusted-ca-root-certificate.

What seems wrong with the issued certificate? Does the common name match with the domain? Is it expired? Or is the Warden CA expired?

Does the common name match with the domain?

Yes, mage244.test is the main domain.

Is it expired?

No. It says: Expires On	Thursday, April 20, 2023 at 11:17:55 AM

Or is the Warden CA expired?

Not sure how to validate/check this?

You probably want to check out https://docs.warden.dev/installing.html?highlight=certificate#trusted-ca-root-certificate.

When I tried to import the certificate from Chrome, it says

Certificate Import Error
The Private Key for this Client Certificate is missing or invalid

@MagePsycho The error message mentioning a 'Client Certificate' when attempting to import the CA root certificate seems to indicate you are likely attempting to import as a client certificate instead of importing on the "Authorities" tab in the settings interface.

@davidalger My bad. Now I am able to import the certificate.
But still, I have the same issue


Occasional issue when using with Bubble Card buttons

Describe the bug
See https://github.com/Clooos/Bubble-Card/issues/763. I migrated from Decluttering Card to Streamline Card and have issues for my templates that create a Bubble Card Button for a scene entity. Occasionally the scene entities are returned as undefined to Bubble Card. I switched back some of my buttons from Streamline to Decluttering and while the Decluttering ones work, the Streamline ones don't work.
YAML
If applicable, add any relevant YAML code.
streamline_templates:
  scene_button:
    default:
      color_icon: '#FF9E00'
      color_bg1: ''
      color_bg2: ''
    card:
      type: custom:bubble-card
      card_type: button
      button_type: switch
      entity: '[[entity]]'
      name: '[[name]]'
      icon: mdi:[[icon]]
      tap_action:
        action: call-service
        service: scene.turn_on
        target:
          entity_id: '[[entity]]'
      double_tap_action:
        action: none
      hold_action:
        action: none
      button_action:
        tap_action:
          action: call-service
          service: scene.turn_on
          target:
            entity_id: '[[entity]]'
        double_tap_action:
          action: none
        hold_action:
          action: none
      styles: |
        ha-card > div > div > div > div > ha-icon {
          ${hass.states['[[helper]]'].state === '[[entity]]' ? 'color: [[color_icon]] !important; opacity: 100% !important;' : '' }
        }
        ha-card > div > div > div {
          background: linear-gradient([[color_bg1]], [[color_bg2]]) !important;
        }

- type: custom:streamline-card
  template: scene_button
  variables:
    - entity: scene.wohnzimmer_orange_teal
    - name: Orange & Teal
    - helper: input_text.aktuelle_szene_wohnzimmer
    - icon: fire
    - color_bg1: darkorange
    - color_bg2: deepskyblue

Informations (please complete the following information):

OS: OS-independent
Browser/App: HA Mobile App, Chrome
Streamline Card version: 0.0.5
Home Assistant version: 2024.8.3 (but also on 2024.9.0b2)

It happens randomly (I know the worst case for debugging). I don't think it is about the scenes themselves but maybe about the way I configured scenes in HA (stored in yaml) or my dynamic use of scenes (when there's inactivity in a room I store the current light setup in a scene, that is later recalled when there's motion again).
My configuration yaml contains this include.
scene: !include ../scenes.yaml

Here's one scene in YAML.
- id: 1636221bqz9w8
  name: 'Wohnzimmer: Teal & Pink'
  entities:
    light.stehlampe_gros_wohnzimmer:
      min_color_temp_kelvin: 1901
      max_color_temp_kelvin: 6535
      min_mireds: 153
      max_mireds: 526
      effect_list:
      - blink
      - breathe
      - okay
      - channel_change
      - finish_effect
      - stop_effect
      supported_color_modes:
      - color_temp
      - hs
      friendly_name: Stehlampe groß (Wohnzimmer)
      supported_features: 44
      color_mode: hs
      brightness: 255
      hs_color:
      - 204
      - 100
      rgb_color:
      - 0
      - 153
      - 255
      xy_color:
      - 0.143
      - 0.176
      state: 'on'
    light.stehlampe_klein_wohnzimmer:
      min_color_temp_kelvin: 1901
      max_color_temp_kelvin: 6535
      min_mireds: 153
      max_mireds: 526
      effect_list:
      - blink
      - breathe
      - okay
      - channel_change
      - finish_effect
      - stop_effect
      supported_color_modes:
      - color_temp
      - hs
      friendly_name: Stehlampe klein (Wohnzimmer)
      supported_features: 44
      color_mode: hs
      brightness: 255
      hs_color:
      - 330
      - 95
      rgb_color:
      - 255
      - 12
      - 133
      xy_color:
      - 0.571
      - 0.241
      state: 'on'
    light.deckenlampen_wohnzimmer:
      min_color_temp_kelvin: 2702
      max_color_temp_kelvin: 6535
      min_mireds: 153
      max_mireds: 370
      effect_list:
      - blink
      - breathe
      - okay
     - channel_change
      - finish_effect
      - stop_effect
      supported_color_modes:
      - color_temp
      friendly_name: Deckenlampen (Wohnzimmer)
      supported_features: 44
      state: 'off'
    light.led_streifen_tv_wohnzimmer_rgb:
      min_color_temp_kelvin: 2000
      max_color_temp_kelvin: 6666
      min_mireds: 150
      max_mireds: 500
      supported_color_modes:
      - color_temp
      - xy
      friendly_name: LED Streifen TV (Wohnzimmer)_rgb
      supported_features: 40
      color_mode: xy
      brightness: 255
      hs_color:
      - 204.194
      - 97.255
      rgb_color:
      - 7
      - 155
      - 255
      xy_color:
      - 0.143
      - 0.176
      state: 'on'
    light.led_streifen_hinten_wohnzimmer:
      min_color_temp_kelvin: 2000
      max_color_temp_kelvin: 6535
      min_mireds: 153
      max_mireds: 500
      effect_list:
      - blink
      - breathe
      - okay
      - channel_change
      - candle
      - fireplace
      - colorloop
      - finish_effect
      - stop_effect
      - stop_hue_effect
      supported_color_modes:
      - color_temp
      - xy
      friendly_name: LED Streifen hinten (Wohnzimmer)
      supported_features: 44
      color_mode: xy
      brightness: 255
      hs_color:
      - 329.63
      - 95.294
      rgb_color:
      - 255
      - 12
      - 135
      xy_color:
      - 0.571
      - 0.241
      state: 'on'
  icon: mdi:fireplace
  metadata: {}

I have buttons for all scenes that are static (not the dynamically created ones mentioned above). They all show the error at the same time - so it's not about a particular scene. I think HA reloads the scenes e.g. when dynamic scenes are created through my automations which causes hickups in streamline card. Sometimes when I go over to the scene editor in the HA UI, open a scene there and go back to my Lovelace dashboard, the scene buttons work again. They almost always work again when I activate a scene (either through voice command or through the HA settings).
Some info on how I create the dynamic scenes. I use the scene.create action and provide snapshot entities. These are runtime scenes not stored in the scenes.yaml file - they're not stored in registry and won't survive a HA reboot.
action: scene.create
data:
  snapshot_entities:
    - light.xxx
    - light.yyy
    - ...
  scene_id: wohnzimmer_standby

Looking good so far. The issue seems to be gone.


Invert order of date and time

Is there any way to invert order of date and time?
Currently, the order is time then date, I would like change to date and so time.

I made some changes in my fork. Could this would be a new feature to your theme?
After changes, I just added  this set -g @onedark_date_first true to my .tmux.conf then I got:


cargo-edit: 0.6.0 -> 0.7.0

Motivation for this change
Get the sort-by-default behaviour in the new version :)
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

maintiners: @Gerschtli @Gerschtli @jb55 @filalex77 @killercup


Missing Icon for Not built (aborted builds)

<img title="Not built" src="/static/c82d2d81/images/16x16/nobuilt.png" alt="Not built" tooltip="Not built" style="width: 16px; height: 16px; " class="icon-nobuilt icon-sm">

Thanks a lot for filing this issue! I'll take a look at it as soon as possible!
:smile:

Would you like to write a patch for this? We'd be more than happy to walk you through the steps involved.

Yes, unless that involves creating icons (I'm no designer :) ).
But it will be a few hours before I can take a look at that...

@cobexer I'd rather use the same icon we are using for not started builds. What do you think?

Maybe, I also considered using the stop build icon.
Reusing the icon you propose would use it for three states already, but I'm not sure how important the distinction really is...

The stop build icon is different. This one:

Jenkins uses the same icon for "never build" and "aborted"so I think we should use too.

Fixed. Version 1.1.6


Add rule for sorting imports

Why are these changes needed?

Unsorted imports often cause merge conflicts that must be resolved manually. It slows down the process of merging new pull requests by making it difficult to merge them in batches.
Existing imports have been sorted and cleaned up using the ruff linter with an additional rule.
Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: Patch coverage is 90.90909% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 27.88%. Comparing base (dd61eaa) to head (3b322e2).

Files
Patch %
Lines

autogen/cache/redis_cache.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #2183       +/-   ##
===========================================
- Coverage   37.97%   27.88%   -10.09%
===========================================
  Files          75       75
  Lines        7587     7587
  Branches     1634     1768      +134
===========================================
- Hits         2881     2116      -765
- Misses       4463     5223      +760
- Partials      243      248        +5

Flag
Coverage Δ

unittests
27.81% <90.90%> (-10.15%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Specify the How-to section #2

The section 2 doesn't sufficient to start, is needed more specific information like:
.container must have a height.
.content is the content in the box of image
-

---

----

-----some text
----

---

---

----

---

-

I am posting the suggestion, because your parallax helped me a lot, thanks!

After test, 90% of I said is strong (the HTML), sorry


Cannot edit gems in a character's gem bag

I created a new gem directly on my character sheet, in the gem bag. When I try and right-click to edit it, nothing happens and I get the following error in the browser's console.
GemBagSD.mjs:97 Uncaught TypeError: Cannot read properties of undefined (reading 'actor')
    at canEdit (GemBagSD.mjs:97:19)
    at Object.condition (GemBagSD.mjs:109:27)
    at ContextMenu.render (foundry.js:64818:67)
    at HTMLFormElement.<anonymous> (foundry.js:64742:19)

Found this on Foundry 11.313 and Shadowdark RPG 1.7.3

Can you right click on the affected character, then export. Then upload that JSON file. We'll take a look.

Right-clicking to edit other items on the sheet work fine. It's just gems in the bag.
fvtt-Actor-ethel-lochlainn-z9FnuhnEIqT9fENR.json

The character and gem load and work perfectly for me. It's probably a mod you're running that's causing the error. Try loading your character into a new blank world and see if the issue persists. Here's a copy of the character with the gem removed:
fvtt-Actor-ethel-lochlainn-gem-removed.json

@kaelad02 Did you get this figured out? Can this be closed out?

I'm not the GM in the game and I didn't get a chance to ask the GM to try turning modules off before our session ended. I setup a test world and couldn't reproduce the bug either. None of their modules jumped out as a possible culprit either. Let's close it for now. If I get a chance to debug it more and find out it is a system bug, I'll reopen it.

My GM updated the Shadowdark system to version 3.0.0 and we were admiring the new sheet layout. I brought up this error again and it was still reproducible by me and another player but not the GM. I suspect there's some difference between GM vs Player. I asked the GM and he said he gave us the Trusted Player role, in case that matters.
And on the off-chance the line numbers have changed, here's the stack trace I saw with version 3.0.0:
TypeError: Cannot read properties of undefined (reading 'actor')
    at canEdit (GemBagSD.mjs:108:19)
    at Object.condition (GemBagSD.mjs:120:27)
    at ContextMenu.render (foundry.js:64818:67)
    at HTMLFormElement.<anonymous> (foundry.js:64742:19)


Reading delta log Table Checkpoint  files should fallback the entire plan

Is your feature request related to a problem? Please describe.
I'm seeing queries on Databricks where the query reads delta logs Table Checkpoint files (from the delta_log directory) which runs on the CPU:
Scan ExistingRDD Delta Table Checkpoint with Stats
and then after that it goes to run a filter operation on the GPU which request row to columnar and then columnar to row and those transition look like they just take more time than its worth.   It will also cause the use of the gpu semaphore which means it blocks something else from getting on there.
Based on this we should have it fall back to the CPU for the entire plan after seeing the read of delta log table checkpoint parquet files.

Note that when we see these queries it actually does a parquet scan, filter,project and then maps to do the Scan ExistingRDD Delta Table Checkpoint with Stats. The first parquet scan we leave on the GPU, but after we go to the Scan ExistingRDD Delta Table Checkpoint with Stats we leave it off the gpu at that point:


Add experimental XJSON entry server.

LGTM

He's modified the serializer code as well. I'm trying to think of a good joke about merge conflicts but failing so far.

Other than Deserializer::ReadMerkleTreeLeaf, it's mostly adding code, shouldn't be too bad... Smaller PRs are easier to rebase and fix conflicts? :wink:

Maybe. I think this is going to conflict though where I've changed the same
methods. We'll see.
Martin
On 30 October 2015 at 11:20, Pierre Phaneuf<EMAIL_ADDRESS>wrote:

Other than Deserializer::ReadMerkleTreeLeaf, it's mostly adding code,
shouldn't be too bad... Smaller PRs are easier to rebase and fix conflicts? [image:
:wink:]
—
Reply to this email directly or view it on GitHub
https://github.com/google/certificate-transparency/pull/1003#issuecomment-152499201
.


Save metadata in-place in limited cases

This enables the save button and makes it overwrite the existing metadata file associated with the layer. The motivation is to allow metadata changes that don't require rewriting all the layer data, which could be achieved through the standard Save selected layer ... option in napari.
But it's also a potentially dangerous/lossy operation, so it is only enabled if all the following conditions hold.
1. The layer was read with this plugin. This way we know it's an ome-zarr, we know what file to overwrite (the multiscale image group's zattrs), and can do so with ome-zarr's write_multiscales_metadata function.
2. The layer's file path is writable. I'm assuming this won't typically apply for ome-zarr stored on remote cloud services like S3.
3. The number of axes is the same in the layer and original file. In particular, napari-ome-zarr splits multi-channel images into multiple layers.
In the case that it is not supported, the tooltip of the save button gives a reason why.
Closes #31

Codecov Report

Merging #36 (e5c1db3) into main (180867b) will decrease coverage by 1.02%.
The diff coverage is 80.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #36      +/-   ##
==========================================
- Coverage   93.72%   92.71%   -1.02%
==========================================
  Files          16       16
  Lines        1371     1469      +98
==========================================
+ Hits         1285     1362      +77
- Misses         86      107      +21

Impacted Files
Coverage Δ

src/napari_metadata/_writer.py
76.54% <68.85%> (-23.46%)
:arrow_down:

src/napari_metadata/_widget.py
94.11% <84.61%> (-0.54%)
:arrow_down:

src/napari_metadata/_tests/test_widget.py
99.65% <100.00%> (+0.04%)
:arrow_up:

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


Match module name with file name

This change is

Coverage remained the same at ?% when pulling 422fb972cc03db456d5610aad835a83b5351f136 on rename-file into 384ce16cde9f1cd1678f6695077fa3b56bbb825b on master.


Can't compile because of rustc error

To track: https://github.com/reem/rust-error/issues/9 https://github.com/rust-lang/rust/issues/19056

This error was fixed, but #10 is still present.


Refs #27468 -- Included algorithm in Signer signature.

This commit prepares the way for different algorithms.

Like @charettes I would want to see support in unsign() and loads() for specifying the expected algorithm, and I think it's important to have that happen as part of this PR. I also wonder whether that should just become the interface, skipping the valid_algorithms attribute altogether.
The thing I mostly want to avoid is a situation where we do negotiation on the algorithm, because that puts the ultimate choice in the hands of an attacker: if they know a Django install accepts any out of a list of algorithms, they can choose the worst/weakest one and craft a value to exploit it. Which is generally why things like cipher negotiation are frowned on in cryptography.
So what would people think about making the signatures of unsign() and loads() start taking the extra parameter now, and default it to SHA-1? Then when we're ready we could change the default, do a short deprecation cycle in which we still support SHA-1 fallback even though it's no longer the specified allowed algorithm, and then drop it altogether.

Thanks ubernostrum for your input.
I'll rework this patch. In fact, my plan is to set the algorithm in the Signer.__init__ signature. In this way, the unsign process can limit the accepted algorithm to this selected algorithm only. The question is whether we should provide some sort of legacy algorithm support to ease algorithm changes from API clients.

@ubernostrum, is #12454 more in line with what you imagined?

We'll concentrate on PR #12454.


New Theme: DevResume

Theme submission
Please make sure that you have read the theme submission guidelines before submitting a theme. The guidelines provide all relevant information and requirements that have to be fulfilled before the submission. Please tick the relevant boxes for your theme in the checklist below:
Link to my theme repository: https://github.com/cowboysmall-tools/hugo-devresume-theme
I made sure that...

[x] the repository contains a good README.md describing my theme
[x] an open source license has been added to LICENSE.md
[x] all metadata have been added to theme.toml
[x] screenshots have been added in the images/ folder with the required dimensions
[x] in case I'm using a customized demo via the exampleSite folder that

[x] https://example.com is set as base url in exampleSite/config.{toml, yaml, json} to avoid the abuse of unused domains
[x] I tested that my theme's demo works with the content directory of gohugoio/HugoBasicExample

[x] I tested my theme against the gohugoio/HugoBasicExample

[x] I've checked the developer tools' console in my browser for error messages

[x] in case my theme is using Hugo Pipes features like toCSS and PostCSS that I have committed the /resources directory with all generated assets, for my theme to work in the basic version of Hugo

N.B. By submitting a theme to the Hugo Themes Showcase you understand that you need to maintain your theme. You will need to keep an eye on whether your theme's demo generates on the Hugo website, whenever there is a new release. We are a very small team and we just cannot keep up opening issues in the various theme repositories to notify authors. Whenever a theme demo breaks and remains broken then at some point it will be removed from the list without prior warning. If you no longer wish to maintain a theme please let us know.
Feel free to ask questions. We're glad to help.

@cowboysmall
Thank you for submitting this theme. Everything looks fine on my end.
Once the tests for pull request #745 succeed, I will add the theme to the Hugo website.

@digitalcraftsman
This is a one page resume theme.

I've promoted your theme on Hugo's official Twitter account.

@cowboysmall
Thank you for submitting this theme. Everything looks fine on my end.
Once the tests for pull request #745 succeed, I will add the theme to the Hugo website.
@digitalcraftsman
This is a one page resume theme.

My pleasure. Thanks very much!
J.K.

I've promoted your theme on Hugo's official Twitter account.

Very cool! Thanks so much for that!
J.K.


Add jq and curl to container for use with EA command type alerts

Couple of very useful apps for use with Elasticsearch and Elastalert command type alerts.  With jq we can munge the output of pipe_match_json of the command alert as an example.

This would be a good addition to the alt branch as well, for users that prefer the newer alt fork of Elastalert.


Where to configure payload to be transferred to the device in TO2 protocol

Hi,
I followed the guide for aio and device components installation but I can't figure out how to make the device download a payload decided by me. Is there a configuration file? Do I have to insert an entry in the db? Where do I have to set ServiceInfo objects?
Thank you.

Yes, you have to upload the file to the db first. More info here https://github.com/fido-device-onboard/pri-fidoiot/tree/master/component-samples/demo#enabling-serviceinfo-transfer


Write a review icon fades gray after highlight

If this is to denote “clicked” maybe we switch it to after the cell was selected instead of highlighted

Bug Report Dump (Auto-generated)

Version 1.22.0<PHONE_NUMBER>)
Device: iPhone 6s (iOS 11.4.1)
TestFlight: true

🤔 can you explain this a bit more? The cell should have a selection state. What’s the actual issue here?
Sent with GitHawk

So if you were to press the cell but not click it.

Press cell (but don’t click it)
Move finger off cell.

The icon turns gray as if you had actually pressed it.
Not major on the least bit but I assume it’s a quick fix. I can look into it.
Sent with GitHawk

@rnystrom Looking at the settings VC it seems that its caused by the image being set to render as template and the tint color being set to a gray.
Not sure why it doesn't render gray in the beginning.

Oh strange, it’s always gray to me
Sent with GitHawk

Here’s what I get. Doesn’t really make a difference but just thought I’d log it so it’s known.

Sent with GitHawk

@Huddie do you have some accessibility options enabled? Why do your switches have extra icons? iOS 11.4?
Sent with GitHawk

@rnystrom Ya I have the accessibility for switches. Idk I kinda like it. Is that what’s causing it?
Sent with GitHawk

I’m not sure tbh
Sent with GitHawk

Settings > General > Accessibility > On/Off Labels. Supported by all UISwitches. Been there since iOS 7 I think?

I turned it off , didn’t change anything. Not sure if that helps.
Sent with GitHawk

Don't think that is related

We need a "bug?" label


Latex/Mathjax Support

While an entirely different approach to changing the color of the text would be needed, I think that mathjax support meaning that a user could color using \textcolor{#}{#} would be AWESOME!
Cool plugin btw! Excellent use for html.

Hi, this is a really cool idea. I want to expand ways to colorize the texts, thanks for the idea! I will look into it

This is the shortcut that I am currently implementing:
{\color{"color-name"}"math"}
Example:
$$ \frac{{\color{red}q}_{\color{yellow}x}}{\color{blue}A}=-{\color{purple}k}\frac{d{\color{black}T}}{d{\color{yellow}x}} \tag{15-1} $$


used proper naming conventions in the shop.route.py and product route URL. Used camelCase and hyphen instead of underscore

used proper naming conventions in the shop.route.py url.used camelcased and hiphen instead underscore

Description
used proper naming conventions in the shop.route.py url.used camelcased and hiphen instead underscore

Motivation and Context
its necessary to use proper naming conventions for best practices
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
< Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!
-[x ] My code follows the code style of this project.

[ x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@zxenonx

all done already


⚠ Bofrost.de has degraded performance

In 9e2cdad, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1724 ms

Resolved: Bofrost.de performance has improved in 74667cf.


Fix python2.7 compatibility in setup.py

Got the following when running tests under python2.7:
Traceback (most recent call last):
  File "setup.py", line 11, in <module>
    with open('README.rst', encoding='utf-8') as f:
TypeError: 'encoding' is an invalid keyword argument for this function

Reference: https://stackoverflow.com/questions/25049962/is-encoding-is-an-invalid-keyword-error-inevitable-in-python-2-x

It seems like tests are flaky and not related to this PR.

Yes, indeed, master is now failing: I think it must be because of scikit-learn's recent update to 0.20. I'll raise an issue for that.
Running your PR with 0.19.2 version, it passes, so I guess we can merge it and fix the tests in another PR

Merged.


Add command line interface

Dear Benjamin and Daniel,
as outlined within #50, we wanted to start bringing the features of this library to the command line similar to what users have been accustomed with dwdweather2.
Thanks again for the ongoing efforts you are putting into this library. Being able to acquire data across historical+recent data sets using the new DWDStationRequest.collect_data() method without having to assemble them manually in any way is really powerful.
While we haven't tested any other combinations of parameters other than those listed within the examples section of dwd --help yet, you might want to merge these updates right away when pulling in the stationdata-request-definition branch to master. Saying that, there might well be some fixups required in this matter to remedy quirks with more parameter combinations.
Cheers,
Andreas.

Dear Benjamin,
thanks for your suggestions. Please let me know whether this needs more work for the initial merge.
Also, please take notice that this is currently heading towards the stationdata-request-definition branch. After you have merged #49 and #57, do you believe we should direct it towards the master branch already?
Cheers,
Andreas.

Dear Benjamin,
thanks for your suggestions, I've adjusted the PR accordingly at some spots. Please let me know whether this needs more work for the initial merge.
Also, please note that this is currently heading towards the stationdata-request-definition branch. After you have merged #49 and #57, do you believe we should direct it towards the master branch already?
Cheers,
Andreas.

Please redirect the PR to master, as it as of now includes all the recent changes!

Hi Benjamin,

Please redirect the PR to master, as it as of now includes all the recent changes!

I have just done so. However, I recognized that the specific feature to acquire data across the {historical,recent} data sets:
# The real power horse: Acquire data across historical+recent data sets
dwd readings --station=44,1048 --parameter=kl --resolution=daily --period=historical,recent --date=1969-01-01/2020-06-11

does not work based on the current master branch. Saying that, I am 100% sure it worked on top of the stationdata-request-definition branch.
Currently, invoking that command croaks with
Error: 'start_date' must be smaller or equal to 'end_date'.
Traceback (most recent call last):
  File "/Users/amo/dev/panodata/sources/python_dwd/.venv3/bin/dwd", line 11, in <module>
    load_entry_point('python-dwd', 'console_scripts', 'dwd')()
  File "/Users/amo/dev/panodata/sources/python_dwd/python_dwd/cli.py", line 89, in run
    request = DWDStationRequest(
  File "/Users/amo/dev/panodata/sources/python_dwd/python_dwd/dwd_station_request.py", line 70, in __init__
    self.period_type = sorted(self.period_type)
TypeError: '<' not supported between instances of 'PeriodType' and 'PeriodType'

With kind regards,
Andreas.

I've just investigated a few commits from the named branch and found 0f1faa7 to be probably the one which is missing in order to make PeriodType sortable.

Re-added on behalf of you through #62. When using that,
dwd readings --station=44,1048 --parameter=kl --resolution=daily --period=historical,recent --date=1969-01-01/2020-06-11

works flawlessly again.

Thanks for merging this!


Fix uncompress error

Remove the "-a" option in tar since it's for compressing.

@sykuang Thanks for the fix!


:construction_worker: fix(ci): Fix typos in build github action

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #130   👈

This comment was auto-generated by Graphite.


bug: successor market proposals failing in overnight runs

In overnight fuzz tests after multiple successive children market-sim new market proposal fails:
Can be reproduced locally with:
python -m vega_sim.scenario.fuzzed_markets.run_fuzz_test -s 2440

2023-08-09 00:31:09,972 - root - INFO - Removing volume 7d7c728610dfa77f9ad68f2c1264b38fbdcf96c19318368699af54bebc083fba

Traceback (most recent call last):

  File "<frozen runpy>", line 198, in _run_module_as_main

  File "<frozen runpy>", line 88, in _run_code

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/scenario/fuzzed_markets/run_fuzz_test.py", line 95, in <module>

    _run(steps=args.steps, console=args.console, output=True)

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/scenario/fuzzed_markets/run_fuzz_test.py", line 44, in _run

    scenario.run_iteration(

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/scenario/scenario.py", line 102, in run_iteration

    outputs = self.env.run(

              ^^^^^^^^^^^^^

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/environment/environment.py", line 166, in run

    return self._run(

           ^^^^^^^^^^

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/environment/environment.py", line 236, in _run

    self.step(vega)

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/environment/environment.py", line 420, in step

    agent.step(state)

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/scenario/fuzzed_markets/agents.py", line 844, in step

    self._create_latest_market(parent_market_id=self.market_id)

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/scenario/fuzzed_markets/agents.py", line 799, in _create_latest_market

    self.vega.create_market_from_config(

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/service.py", line 502, in create_market_from_config

    proposal_id = gov.propose_market_from_config(

                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/api/governance.py", line 129, in propose_market_from_config

    return _make_and_wait_for_proposal(

           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/jenkins/workspace/common/vega-market-sim-reinforcement/vega_sim/api/governance.py", line 544, in _make_and_wait_for_proposal

    raise ProposalNotAcceptedError(

vega_sim.api.helpers.ProposalNotAcceptedError: Your proposal was STATE_REJECTED due to PROPOSAL_ERROR_INVALID_SUCCESSOR_MARKET. Any further info: market to succeed does not exist

Closed as stale issue and no longer an active bug.


Not an issue, but wrote a tutorial referencing this repo

hey @erikras, I wrote this tutorial heavily utilizing the patterns and principles utilized in this repo. I'd love your thoughts!

Love it! Thanks for sharing.
I don't really understand the gorilla, but... :monkey_face:

haha thanks!

amazing, thanks for the link in the readme!

:monkey_face: :banana: :monkey_face: :banana: :monkey_face: :banana: :monkey_face: :banana:


Filesystem / Create-React-App issue causing majority of styled-components to break.

I'm not sure this belongs here, but...

Environment

npx envinfo --system --binaries --npmPackages styled-components,babel-plugin-styled-components --markdown --clipboard
System:

OS: macOS High Sierra 10.13.3
CPU: x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 732.56 MB / 16.00 GB
Shell: 5.3 - /bin/zsh

Binaries:

Node: 8.11.1 - /usr/local/bin/node
npm: 5.6.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman

npmPackages:

styled-components: ^2.2.3 => 2.2.3

Reproduction

Unable to reproduce, seems like a filesystem issue.
Steps to reproduce
npm start inside my create-react-app I've been successfully working on / deploying|building to production since November 1st.
I have extensive use of styled components throughout the app. On friday, the 27th of April, I npm run build our application and deployed to production with no issues. Monday I came in to work, launched our application development environment yesterday, and a majority of styled-components are not rendering their styles properly. It's the same with the two interns who started who were the first to see this issue.
My simplest example as seen in the example below is a simple "Card" component that renders a hovering card.
import styled from 'styled-components';

console.log('File is parsing.');

export default styled.div`
  position: relative;
  background-color: white;
  border: 1px solid #E3E3E3;
  box-shadow: ${({ flat }) => flat ? (
    'none'
  ) : (
    '0 3px 6px 0 rgba(0,0,0,0.16)'
  )};
  padding: 16px;
  margin: 64px 0 0 0;
`;

This component gets put in the dom, has the class="sc-jibber isherr" but none of it's styles are properly applied. I see the console log, File is parsing..
Upon making any change in the file, the next page reload then renders all Cards properly in the application for the rest of the npm start session. When I cancel ctrl + c the process and restart, the Card component is gone again. It's only specific components that are failing though, some other components in the same component library are working and appearing exactly as expected.
Expected Behavior
Styled-components applies it's styles to components the first time they're loaded.
Actual Behavior
I'm uploading a video to show what is happening, but basically 85% of my app components aren't rendering. Please hold.
https://www.youtube.com/watch?v=DLGGgkGvrTE&feature=youtu.be
For the love of god, been at this for the last 14 hours, if anyone figures this out ... I owe you atleast 4 beers.

Do you have a any subdependency (be it your own or external) that also depends on styled-components and is incorrectly set up so that two copies of styled-components are being bundled?

Good question, definitely not my own, I will investigate my existing dependencies, but the brutal part here is that no matter how far back I roll my commits, all my components have broken. Also have rolled back:
All package.json versions,
All node / npm versions ( as low as v4 )
Git history right back to january which was still broken.
I attached a video in the original ticket.

@kitten no sir, just checked all my packages dependencies. Nothing else is using styled-components.

Just to double check - you mind running this, and pasting the output? This will recursively crawl the whole node_modules tree looking for SC.
npx envinfo --npmPackages styled-components --duplicates --fullTree --clipboard

npx: installed 1 in 1.832s

  npmPackages:
    styled-components: ^3.2.6 => 3.2.6

andrew@ubuntu:~/code/test$```

npx: installed 1 in 1.531s

  npmPackages:
    styled-components: ^2.2.3 => 2.4.0```

From y mac, interesting, why is it actually changing versions here.

In my original question, it says ^2.2.3 => 2.2.3

Yeah not at the same time, sorry, I've been going crazy here with trying idfferent stuff, but in each environment the issues are happening, regardless of version. I might download yarn and try with that but i'm not feeling confident about it.

If I mount my  component in our PrimaryView.js area, the Card renders properly, and if in the same session I click to the backend admin area (seen in the video), the card is not rendering correctly. It's like it has to do with the view hierarchy. Is there anything regarding context that could be breaking styled components? Is there a list of keys that i should stay away from? Obviously theme is one of them.

Well, I don't have an explanation for it, but it's a code-splitting issue. One which I can not explain. The gains are not worth th esacrifice obviously, and as such I am removing code-splitting from our application.

My god gentleman, I found it.

const Item = styled.div`
  display: flex;
  align-items: center;
  justify-content: space-between;
  cursor: ${({ onClick }) => !!onClick ? 'pointer' : 'auto'};
  color: rgba(255,255,255,0.8);
  transition: border 0.1s ease-in-out, background-color 0.1s ease-in-out;

  width: 100%;
  height: 80px;

  min-height: ${({ isChild }) => isChild ? '20px' : '40px'};

  &:hover {
    background-color: 'rgba(0,0,0,0.1);
  }

  margin-left: 0.5208vw;
  padding-right: 16px;

  ${media.portrait`
    margin-left: 15px;
    padding-right: 75px;
  `}

  ${media.mobile`
    margin-left: 5px;
    padding-right: 65px;
  `}
`;

Check out that &:hover. That code has been in there for as long as I can remember. I can't understand why it only just started causing issues. I was able to restore code-splitting into my application after removing the apostraphe from the background-color property. Maybe this is my reproducible bug?
@tabrindle @kitten


Tag releases and make release script more resilient

This changes the release.sh script to create releases.

The release commit is tagged
The rustler_mix documentation points to that tag
If an error occurs during packaging, the commit is reverted. This is not done when publishing is already underway!

The PR adds two environment variables for the script to simplify testing:

DRYRUN: Do not publish, even if publish is requested.
DONTREVERT: Do not revert the changes if an error happened

As of 06e7f96, this does not yet work, as cargo fails to select a matching version of rustler_codegen for the rustler crate:
$ DRYRUN=1 ./release.sh 1.2.3
Bumping versions..
Committing version..
[tag-on-release 72a39f5] (release) 1.2.3
 5 files changed, 6 insertions(+), 6 deletions(-)
Tagging version..
~/tools/rustler/rustler ~/tools/rustler
   Packaging rustler v1.2.3 (/home/mo/tools/rustler/rustler)
   Verifying rustler v1.2.3 (/home/mo/tools/rustler/rustler)
    Updating crates.io index
error: failed to verify package tarball

Caused by:
  failed to select a version for the requirement `rustler_codegen = "^1.2.3"`
  candidate versions found which didn't match: 0.21.0, 0.20.0, 0.19.0, ...
  location searched: crates.io index
required by package `rustler v1.2.3 (/home/mo/tools/rustler/target/package/rustler-1.2.3)`
Reverting changes..
Deleted tag 'rustler-1.2.3' (was 72a39f5)
HEAD is now at 5d952d6 allow dirty
[2]    48994 exit 101   DRYRUN=1 ./release.sh 1.2.3

Maybe dropping the separate cargo package step and publishing rustler_codegen first helps?

Maybe dropping the separate cargo package step and publishing rustler_codegen first helps?

Then, we might publish some of the crates before a later crate fails to be packaged. I think the extra step is useful, but I don't know yet how to resolve the problem.

I think this could be the problem when packaging (docs):

Cargo will ignore the path key for dependencies in published packages.

rustler_codegen is published already, so the path key is ignored.

Maybe dropping the separate cargo package step and publishing rustler_codegen first helps?

I applied that suggestion to release.sh.


[bug]: Problem installing InvokeAI 2.2.4 after successfully installed and deleted InvokeAI 2.2.3

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
24GB
What happened?
I have successfully installed version 2.2.3, an then decided to ty and install 2.2.4. I have manuali deleted folders of 2.2.3. Installation was located in user folder  ( I was planning to move installation to another drive because of space on drive C: ) and try to install 2.2.4. but constantly get errors. I have tried automatic installation, and manula conda installation but without success.
After installation collects all packages I get this error:
Successfully built k-diffusion pypatchmatch clip
Installing collected packages: torch, tifffile, sentry-sdk, scipy, rich, requests, PyWavelets, pytz-deprecation-shim, python-socketio, python-dateutil, pypatchmatch, pyarrow, pudb, promise, opencv-python-headless, opencv-python, omegaconf, numba, jsonschema, Jinja2, importlib-metadata, imageio, gitdb, flaskwebgui, eventlet, docker-pycreds, contourpy, click, aiosignal, tzlocal, torchvision, torchsde, torchmetrics, torchdiffeq, scikit-learn, scikit-image, requests-oauthlib, pydeck, pandas, matplotlib, kornia, jsonmerge, huggingface-hub, google-auth, gitpython, flask, aiohttp, accelerate, wandb, transformers, torch-fidelity, qudida, google-auth-oauthlib, flask_socketio, flask_cors, filterpy, diffusers, clip, clean-fid, altair, tensorboard, tb-nightly, streamlit, k-diffusion, facexlib, clipseg, albumentations, test-tube, pytorch-lightning, basicsr, taming-transformers-rom1504, gfpgan, realesrgan
ERROR: Exception:
Traceback (most recent call last):
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\cli\base_command.py", line 160, in exc_logging_wrapper
status = run_func(*args)
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\cli\req_command.py", line 247, in wrapper
return func(self, options, args)
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\commands\install.py", line 494, in run
installed = install_given_reqs(
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\req_init_.py", line 73, in install_given_reqs
requirement.install(
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\req\req_install.py", line 792, in install
install_wheel(
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\operations\install\wheel.py", line 729, in install_wheel
_install_wheel(
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\operations\install\wheel.py", line 589, in _install_wheel
file.save()
File "C:\Users\rober\invokeai.venv\lib\site-packages\pip_internal\operations\install\wheel.py", line 388, in save
shutil.copyfileobj(f, dest)
File "C:\Python310\lib\shutil.py", line 195, in copyfileobj
buf = fsrc_read(length)
File "C:\Python310\lib\zipfile.py", line 925, in read
data = self._read1(n)
File "C:\Python310\lib\zipfile.py", line 1015, in _read1
self._update_crc(data)
File "C:\Python310\lib\zipfile.py", line 943, in _update_crc
raise BadZipFile("Bad CRC-32 for file %r" % self.name)
zipfile.BadZipFile: Bad CRC-32 for file 'torch/lib/torch_cuda_cu.dll'
Requirements installation failed. See above for errors and check https://invoke-ai.github.io/InvokeAI/installation/INSTALL_AUTOMATED/#troubleshooting for potential solutions.
The installer will exit now.
Press any key to continue . . .
Screenshots
No response
Additional context
No response
Contact Details
No response

I managed to solve the problem with
pip cache purge
after that the installation went fint


Damn!

This could be a powerful classroom tool for reading fluency - in fact, I found it on an educational website - but I would be very hesitant to use it in my third grade classroom when the word "damn" pops up every time they finish reading. Is there a way to get that changed?
Cathi Palmer

I agree, this should be changed.

@notolaf, this project is no longer maintained (thanks to legal threats from Spritz), so I don't think this will be changed.
If you're looking for something to use in class, jetzt works very well, although it's less polished.
Good luck.


--query argument fails with: Unsupported operand type(s) for 'dict'

After the recent changes in 310b32c for:

#3

✅ Filepath as the only argument works normal
$ get_dropbox_link.py ~/Dropbox/Public/test-2023-08-15a.txt
https://www.dropbox.com/s/zk0z1wbblfh0e23/test-2023-08-15a.txt?dl=0

Note: Luckily I'm getting the classic /s/ style links again.
❌ Custom arguments result in error
$ get_dropbox_link.py ~/Dropbox/Public/test-2023-08-15a.txt --query 'raw=1'
ERROR:root:unsupported operand type(s) for |: 'dict' and 'dict'

All possible permutations I tried failed with the same error:

Arguments before/after filepath
--query value in no quotes, single quotes, double quotes.

Environment

get_dropbox_link -- latest one: ad71584eb4c3
macOS 11.7.8 Big Sur
Python Env: Worked before, nothing changed AFAIK

This is an issue with a newer Python feature, the union operator. In my testing, lower versions of Python 3.8 doesn't support this, whereas later versions of 3.8 and all versions of 3.9+ do.
I've changed to using the more broadly-supported {**a, **b} dict merging syntax.

Tested and now worked with Python 3.11.4 on macOS 11.8.8 Big Sur.


Notification don't work on android 12 when app close from background after change flag to PendingIntent.FLAG_IMMUTABLE notification appear but when click on button app does'nt open

We are use connectycube_flutter_call_kit 2.0.2 on android 10 and it's working fine but when we switch to android 12 when app is close with homePage button or back button notification don't work but after change all "PendingIntent.FLAG_UPDATE_CURRENT" to "PendingIntent.FLAG_MUTABLE or PendingIntent.FLAG_UPDATE_CURRENT" in NotificationManager.kt file this issue fix and notification work but when click on buttons for example accept for incoming call , its did'nt work and do nothing but in android 10 open app and working fine.
this is my log here :
D/FLTFireMsgReceiver(19693): broadcast received for message
W/FirebaseMessaging(19693): Unable to log event: analytics library is missing
D/NotificationsManager(19693): customRingtone
D/NotificationsManager(19693): ringtone 2 content://settings/system/ringtone
W/FlutterJNI(19693): FlutterJNI.loadLibrary called more than once
W/FlutterJNI(19693): FlutterJNI.prefetchDefaultFontManager called more than once
I/ResourceExtractor(19693): Found extracted resources res_timestamp-55-1652177938650
W/FlutterJNI(19693): FlutterJNI.init called more than once
I/FLTFireBGExecutor(19693): Creating background FlutterEngine instance.
I/FLTFireMsgService(19693): Service has not yet started, messages will be queued.
D/DeviceInfoPlugin(19693): Use TaskQueues.
D/PathProviderPlugin(19693): Use TaskQueues.
I/EventReceiver(19693): NotificationReceiver onReceive Call ACCEPT, callId:<PHONE_NUMBER>368
D/ConnectycubeFlutterCallKitPlugin(19693): callEventMap: {caller_name=IrancellMan, user_info={"uid":"0:bfe1a3aa-ed7f-46c4-aeebdea","callEventJson":"{"1":"1652179600520-65i90815h5","2":0,"3":"1652179600520","4":"0","5":1}"}, caller_id=123456789, session_id=1652179602368, call_opponents=1, call_type=0}
W/FlutterJNI(19693): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: connectycube_flutter_call_kit.callEventChannel. Response ID: 321
D/FLTFireMsgReceiver(19693): broadcast received for message
W/ConnectycubeFlutterBgPerformingService(19693): A background message could not be handled in Dart as no onBackgroundMessage handler has been registered.

سلام راه حلی براش پیدا کردی؟ من هم همین مشکل رو دارم

@AmirhosseinShk @rezadevelopers2 we made some fixes in the new version 2.0.3, please try it.
Pay attention, if you need to start the app by clicking the Accept button, you should provide the permission SYSTEM_ALERT_WINDOW first. You can use the plugin permission_handler for requesting needed permissions.

@TatankaConCube I have another problem related to this issue and its about get SYSTEM_ALERT_WINDOW permission when my app on background and didn't receive permission request and get error  :
Unhandled Exception: PlatformException(PermissionHandler.PermissionManager, Unable to detect current Android Activity., null)
are u have any idea for this problem can be helpful? please share with me.

@TatankaConCube I have another problem related to this issue and its about get SYSTEM_ALERT_WINDOW permission when my app on background and didn't receive permission request and get error :
Unhandled Exception: PlatformException(PermissionHandler.PermissionManager, Unable to detect current Android Activity., null)
are u have any idea for this problem can be helpful? please share with me.

@AmirhosseinShk please create the new ticket for this issue


Missing beacon node <-> validator client API

We need to solidify the latest validator API exposed by the beacon node (active discussion here: https://github.com/ethereum/eth2.0-APIs/issues/12) and implement it in the beacon node. There are stubs API methods/functions in the validator client as of #1482.

One important thing to do here is to fetch the Fork data from the beacon node so that the validator client can create the proper BLS domain when making a signature.


API Authentication Not working with API Key

Please see my local settings
{
  "IsEncrypted": false,
  "Values": {
    "OpenApi__ApiKey": "SFJCbG9jay5PY2UuU2VydmljZXMuRm9ybVJlbGVhc2UuQXBp",
    "OpenApi__AuthLevel__Document": "Function",
    "OpenApi__AuthLevel__UI": "Function"
}

[FunctionName("FormStatus")]
        [OpenApiOperation("FormStatus")]
        public new async Task<IActionResult> GetAllFormStatus(
            [HttpTrigger(AuthorizationLevel.Function, "get", Route = "formstatus")] HttpRequest req)
        {

            return result;
        }

When I trigger this, it is getting called without any api key auth

@bnlakshmibn Thanks for the issue! If you're running on your local machine, you'll see all the UI and doc regardless how you set the auth level. But, if you deploy it to Azure, you'll see the difference.

[@justinyoo  So you mean the authentication works only after deployment to Azure?
What I exactly did is

I created an azure functions app (v3) (Used dotnet and visual studio 2019)
I added the azute function class and added the method as shown in the previous message
Then installed the Microsoft.Azure.WebJobs.Extensions.OpenApi extension
Added the open api key and settings in local.settings.json
Started (debug mode) the function and triggered the function (tried both from swagger and postman)
I didnt provide the api key in either the header or as query
So what my expectation was, the function will not get called without providing the api key (similar to how we  handle auth in web api's)
But even without providing the api key in the request, the function is getting executed
So I am confused here.

@bnlakshmibn Yes, that's expected behaviour. Please refer to this document. It says:

When running functions locally, authorization is disabled regardless of the specified authorization level setting. After publishing to Azure, the authLevel setting in your trigger is enforced.

Hope it makes you clear.

@bnlakshmibn Yes, that's expected behaviour. Please refer to this document. It says:

When running functions locally, authorization is disabled regardless of the specified authorization level setting. After publishing to Azure, the authLevel setting in your trigger is enforced.

Hope it makes you clear.

@justinyoo Oh yes. Now its clear. This was where I got confused. Thank you so much for the clarification.


Suppress benign FindBugs warning DM_STRING_CTOR

Fixes a subset of #241. Suppresses FindBugs complaining about calling the String() constructor. All the warnings are due to strings being concatenated with "+".
Adds a FindBugs dependency in build.gradle too (using 'compile' instead of 'testCompile' as the latter doesn't seem to work). Uses version 3.0.1.
No DM_STRING_CTOR at all from now on for all the projects. One minor concern is that an annotation applies to an entire method. (No finer granularity is possible when using annotations.)

The test fails because of the 3.0.1 FindBugs version.

I have inspected a few bytecode files. For the reported cases, "+" eventually calls String.concat(), and a fresh String is "new"ed as a result. I think this is exactly where FindBugs is complaining. Weird enough, I wasn't able to find documents or discussion online about this correlation between string concat and the FindBugs warning.
I believe we don't have any control over how javac generates bytecode and don't have much option left: we either blank disable this warning once and for all, or suppress it by annotating each method for finer granularity, or just ignore and live with it.

let's blanket disable this.

I will close this PR and put some configuration in build.gradle (possibly with an addition of an XML file) to disable this String()-constructor-calling warning.

thanks!
On Wed, Mar 9, 2016 at 2:52 PM, Chanseok Oh<EMAIL_ADDRESS>wrote:

Closed #481
https://github.com/GoogleCloudPlatform/gcloud-intellij/pull/481.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-intellij/pull/481#event-583832223
.


Can't automatically create the day planner file for today.

After the update to the latest version, my obsidian can't create the file automatically. And the status bar always shows: no plan for day, even I manually create the day plan file.
More info:

obsidian version: 1.4.8
OS: macOS
related plugins: calendar?

the same here

Hello, @neuromaancer, please update and re-check.

Unfortunately, it is the same.

when you say "day plan file", do you mean your daily note, or the 'day planner' file that this plugin used to generate? With the release of 0.7.0 the behavior of this plugin changed. The timeline is now generated from a specific header in your daily note, rather than a separate file

when you say "day plan file", do you mean your daily note, or the 'day planner' file that this plugin used to generate? With the release of 0.7.0 the behavior of this plugin changed. The timeline is now generated from a specific header in your daily note, rather than a separate file

I mentioned the "day planner" file that used to be generated automatically. I got it! I just checked the new README.md. So basically now I need to add the # Day planner header to my template of daily note, if I understand well. Very interesting interaction between 2 plugins  🎉


Running without known-variants

Thank you for making these workflows!
In many cases I work with samples without previously known variants available. Is it possible to configure this workflow to skip steps that rely on having known-variants? I attempted this by making an empty file. Unsurprisingly, this failed.

Hi, same use case here...
Did you manage to find a workaround?
Thanks!

I did not! You might give this new pipeline a try. The recalibration step appears to be optional.
https://arxiv.org/abs/2103.15167

Thanks @silastittes for mentioning my pipeline here! Indeed, it does not require known variants, and also offers a lot of other tools and settings. Maybe it helps @knokknok  as well ;-)


Remove the modules attribute support in the junit package

The junit package defines methods and annotations that take a "modules" attribute to toggle whether to use Java 8 or Java 9 for the minimum version.
This is deprecated and the support can be removed for v1.0 as a breaking change. The "modules" parameter for the minimum supported version on JavacJctCompiler can be removed as well.

Fixed by 1ad2c70a695f28485a9782f96e569d32daf31f44


Periodic curve: parameter sensitivity

Corrected parameter sensitivity for periodic curve. Unit sensitivity now represent the sensitivity of the zero-rate to the curve parameter. Improved tests.
Clarified quantile calculation javadoc.

For completeness we also need a proper implementation of zeroRatePointSensitivityWithSpread.


Add mochi.gg extension

Description
A Raycast extension to interact with mochi
Available commands

Ticker View token details with chart and price change in the range of 1 hour, 24 hours and 7 days
Coin market: View top coin market data
Watchlist: View and manage your watching list (Discord login required)

Screencast

Supported light theme

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@pernielsentikaer thank you for your response.
For your context, the mochi extension is our org contest to create an extension for Raycast.
The #6488 and mine are one of top the selected extensions. We decided that mine will be the official one, so mine PR should be base and #6488 should be an enhancement.
Please help me review mine first, I'll contact #6488 owner to see if he can rebase on mind base.

@pernielsentikaer Thank you for your review, I have updated based on your recommendation, please help me review it again.


Reconstructing LabelModel object does not reset config in notebook

This is a pretty annoying and confusing silent failure mode... I guess the defaults config dict is overwritten somehow, and then loaded then upon class instantiation?  @bhancock8 any ideas?

Hmm, that's surprising, because when we load a model, the init method isn't ever run. It just unpickles the object and you carry on your way (ideally). What do you mean by it does not reset config? Is config none, or is it just set to the default values?

I mean that if I just create a new LabelModel (not load one), it doesn't seem to reset the default config dictionary, so I end up with the same configs that I had set in the previous LabelModel I was using- which is very unintuitive behavior.  It's because the defaults are loaded from another file as a separate object I suppose?

Just to leave a little more information here: the issue was that the imported default config was getting modified. We were copying it in recursive_merge_dicts, but not deep copying it.

Awesome!  Want to push a patch to 0.1.6 :)?
On Sat, Sep 8, 2018 at 1:00 PM Braden Hancock<EMAIL_ADDRESS>wrote:

Just to leave a little more information here: the issue was that the
imported default config was getting modified. We were copying it in
recursive_merge_dicts, but not deep copying it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/metal/issues/37#issuecomment-419669129,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABgw_Vj86jqGh0hOSeffGM-Y-t75Fdchks5uZCHKgaJpZM4WWZPD
.

Patched and updaed to 0.1.7 in 7eea4c2e42adf8b5d97a979376c65977fe244029.


Is only google cloud cluster supported?

No, any Kubernetes cluster should work, including other Kubernetes service hosts (EKS, AKS, etc), standard Kubernetes installations, and minikube.
If you find something that doesn't work please file an issue.


[Dev Tool] Improve samples check-node-versions command:

Feedback from @joheredi:

[x] the logs when pulling docker images are red and I freaked out when I first saw those. It may be a good idea to hide those logs behind a log-level flag
[ ] The step of adding secure_path for sudo to be able to use node feels a bit fragile since it points to a specific nvm_node version. I would think most people in our team use nvm and jump between versions often so keeping this up to date may be frustrating.
[x] It would be really cool to support URLs for the --artifact-path that way you can just grab the link from the pipeline run. I know that npm install supports it so it may not be difficult to do.

Feedback from @maorleger:

[ ] color the output of every node version in a different color
[x] allow multiple of the versions parameter

@joheredi I created a wiki page here that shows how to use this command: https://github.com/Azure/azure-sdk-for-js/wiki/Run-your-Azure-TS-JS-samples-with-multiple-node-versions
It does not have the fragile instructions to use the command with sudo.


⚠ Jenkins Plugins Artifactory has degraded performance

In 2e2417e, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1795 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 41891b3 after 46 minutes.


Complete support for System.Linq.Expressions

http://forums.bridge.net/forum/general/feature-requests/1161
http://forums.bridge.net/forum/community/help/2168
Missed expressions are:

[ ] Expression
[ ] MemberExpression
[ ] UnaryExpression
[ ] LambdaExpression
[ ] ParameterExpression
[ ] ExpressionVisitor - bridgedotnet/Bridge2#44

Support added in Bridge 15.


Issue#9 collect sample data

Looks good @pbvarga1!
Though we should not be including large binary files in the repository, so we don't want to include things like docs/sample_images/FLB_431397159EDR_F0141262FHAZ00323M1.IMG
I accidentally accepted it too :(
Other than that, its a great start!


Source/line data missing in some windows

Callstack window, for instance, never seems to display file/line data, even though it is loaded when you select Visualize and see the dump in the output window.

Tracking internally: http://b/159311038


SUTD Ultimate Frisbee

Name of Student Organisation*
Ultimate Frisbee
Cluster
Sports
Classification
Fifth Row
Description
A family running and chasing after discs together. We welcome Frisbee players of all skill levels to join us; from training to just having fun together, the Ultimate Club goes far together.
Training / Meeting Timings
Competitive team: Wednesdays 1930 - 2230
Recreational: Fridays 1600 - 1900
Student Organisation Introduction Video
Promotional Video
Name / Contact of President
Tan Jia Yue / @tanjiayue (Telegram)
Other Relevant Links
Instagram

This is good!


Preview fully parsed YAML document without committing or running the pipeline

I can't get the API to return YAML. Is there further documentation on the use of this feature?
https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-165-update#preview-fully-parsed-yaml-document-without-committing-or-running-the-pipeline

This is a product support question. Please file a ticket at Developer Community. When you do, please incude details about what you tried and what results you got.

Sorry, I should have worded this differently:
There is no documentation on how to use "Preview fully parsed YAML". Documentation should be added.

@MisinformedDNA That is a valid question, there is an internal PR going to get some REST PI documentation going for this feature and we'll add links when that is ready. In the meantime if you post what you tried over at Developer communities we'll take a look and see if we can help you get it going.


Update config.md

Line 48 is currently generating a 404 and I think it is because it is missing the extension (md) of the arguments file.

Also referencing here #720 and #736


Use images to get registry pods using the registry instead of running it.

Description
Currently, number of pods is the number of pods that run the registry-service.
It makes more seance that  number of pods will count the number of pods using the registry-service.
This PR changes the meaning of Container Pods from running the registry to using it.
Screenshot

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1599696

@cben @Ladas @agrare please review

@yaacov IDK about changing the meaning of an existing field, though I agree I would have expected this to be the number of pods using not running the registry.
Can we add another association for the old meaning?
has_many :service_container_groups, :through => :container_services, :as => :container_group or something?  Not sure what best to call it.

@agrare @cben please re-review

container_groups should definitely match containers, so :+1: to this change.
I don't think number of pods serving the registry would be useful for anyone, only increasing confusing (if one really needs, click the services).  But adding an association is harmless as long as we don't show it :-)
I'd be in favor of renaming container_services to a better name, at least in the UI.  But not in this PR.

I don't think number of pods serving the registry would be useful for anyone

Yeah this might very well be true, I just don't want someone to have e.g. built a report and now they can't get at the data at all.

@agrare @cben update the inline docs, please re-review

@miq-bot add_label blocker

Blocker?  @yaacov this isn't a regression right?

@agrare

Blocker?

the BZ is blocker: https://bugzilla.redhat.com/show_bug.cgi?id=1599696

@yaacov this isn't a regression right?

Yes not a regression, Dave Johnson asked it to be registered as one here: https://bugzilla.redhat.com/show_bug.cgi?id=1599696#c2

Okay thanks @yaacov I'll comment on the BZ.

@yaacov @agrare hammer/yes ?

@simaishi updated

Hammer backport details:
$ git log -1
commit 707c21e3477e06ab39b6ee420633bf9de9c2b4ef
Author: Adam Grare<EMAIL_ADDRESS>Date:   Wed Oct 31 10:31:58 2018 -0400

    Merge pull request #18148 from yaacov/get-pods-from-images-instead-of-services

    Use images to get registry pods using the registry instead of running it.

    (cherry picked from commit 22f6e0974bd4960b4c40a4fc53a5403b48a174a0)

    https://bugzilla.redhat.com/show_bug.cgi?id=1599696


ydotool: minor fixes

Description of changes

Fix the ExecReload= on the systemd service to point to the proper
kill binary to send the HUP signal for ydotoold to reload.
Don't use pkg-config (it doesn't seem to be necessary).
move scdoc to nativeBuildInputs= as it is executed during
the build process to create the manapages, so it should be
installed in the native build-machine arch.

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

based on previous work in my personal overlay