text:
ldapserver crash bug: panic: Expecting 0x30 as first byte, but got 0x4d instead

2022/09/26 12:42:49 Connection client [4] from 192.241.214.147:45002 accepted
2022/09/26 12:42:49 client 4 close()
2022/09/26 12:42:49 client 4 close() - stop reading from client
2022/09/26 12:42:49 client 4 close() - Abandon signal sent to processors
2022/09/26 12:42:49 client [4] request processors ended
2022/09/26 12:42:49 client [4] connection closed
panic: Expecting 0x30 as first byte, but got 0x4d instead

goroutine 20690 [running]:
github.com/forestmgy/ldapserver.readTagAndLength(0x27de25?, 0x236d6530598?)
        C:/GoPath/pkg/mod/github.com/forestmgy/ldapserver@v1.0.9/packet.go:89 +0x2b9
github.com/forestmgy/ldapserver.readLdapMessageBytes(0x30?)
        C:/GoPath/pkg/mod/github.com/forestmgy/ldapserver@v1.0.9/packet.go:54 +0x45
github.com/forestmgy/ldapserver.readMessagePacket(0x30?)
        C:/GoPath/pkg/mod/github.com/forestmgy/ldapserver@v1.0.9/packet.go:18 +0x1d
github.com/forestmgy/ldapserver.(*client).ReadPacket(0xc00016b130)
        C:/GoPath/pkg/mod/github.com/forestmgy/ldapserver@v1.0.9/client.go:58 +0x29
github.com/forestmgy/ldapserver.(*client).serve(0xc00016b130)
        C:/GoPath/pkg/mod/github.com/forestmgy/ldapserver@v1.0.9/client.go:122 +0x365
created by github.com/forestmgy/ldapserver.(*Server).serve
        C:/GoPath/pkg/mod/github.com/forestmgy/ldapserver@v1.0.9/server.go:110 +0x42a

Process finished with the exit code 2

@forestmgy

Fixed by: https://github.com/casdoor/casdoor/pull/1161


text:
Triggering scrolls from presenter

I’ve got some presenter code that would like to scroll its scrollable containers. I imagine APIs like this:

scrollToTop()
scrollToBottom()
scrollToItem(someIdentifier)

What’s annoying about these is they’re more like events than properties, but events that flow the opposite direction from our usual ones.
I could synthesize this with properties in a pinch.

Since everything is fundamentally rooted in Compose, there's not really a mechanism by which you can do this. The closest is how Compose UI does scrolling, which is by allowing you to adjust scroll on the scroll state object either directly or via animation.

source: gharchive/issue

authors: JakeWharton swankjesse

repo: cashapp/redwood

license_type: permissive

license_source: github-api


text:
Outdated cask: Paste

Running brew cask install paste fails due to curl receiving a 404 Not Found when attempting to fetch the download URL in the cask. I even tried to use earlier incarnations of the cask that previously worked for me and they now do not.
I guess for some reason it just disappeared from the HockeyApp API.  I have no idea why that would happen. Not really brew's fault, I know. But am I correct in my understanding that the HockeyApp account being used is something you all control as infrastructure? Never used it before, but that's what I gather from their docs and I see it used in multiple casks.
The newest version of Paste is "Version 2.2.1 (34)".
Debugging info
Output of the command with `--verbose --debug`
sholladay$ brew cask install paste --verbose --debug
==> Hbc::Installer#install
==> Printing caveats
==> Hbc::Installer#fetch
==> Downloading
==> Downloading https://rink.hockeyapp.net/api/2/apps/ee24d1a939cd4ff8b2861eb8c788a995/app_versions/6?format=zip
==> Calling curl with args ["https://rink.hockeyapp.net/api/2/apps/ee24d1a939cd4ff8b2861eb8c788a995/app_versions/6?format=zip", "-C", "0", "-o", "#<Pathname:/Users/sholladay/Library/Caches/Homebrew/Cask/paste--2.2.1,6.incomplete>"]
/usr/bin/curl --remote-time --location --user-agent Homebrew/1.2.1-92-ge931fee7 (Macintosh; Intel Mac OS X 10.12.4) curl/7.51.0 --fail https://rink.hockeyapp.net/api/2/apps/ee24d1a939cd4ff8b2861eb8c788a995/app_versions/6?format=zip -C 0 -o /Users/sholladay/Library/Caches/Homebrew/Cask/paste--2.2.1,6.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
Error: Download failed on Cask 'paste' with message: Download failed: https://rink.hockeyapp.net/api/2/apps/ee24d1a939cd4ff8b2861eb8c788a995/app_versions/6?format=zip
The incomplete download is cached at /Users/sholladay/Library/Caches/Homebrew/Cask/paste--2.2.1,6.incomplete
Error: nothing to install/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:17:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:34:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:98:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:149:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:93:in `<main>'
Error: Kernel.exit
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:154:in `exit'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:154:in `rescue in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:140:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:132:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:8:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:93:in `<main>'

Output of `brew doctor`
Your system is ready to brew.

Output of `brew cask doctor`
==> Homebrew-Cask Version
Homebrew-Cask 1.2.1
caskroom/homebrew-cask (git revision 33118; last commit 2017-05-24)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (13 files, 663.4MB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3617 casks)
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-core (0 casks)
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services (0 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin16
/Library/Ruby/Site/2.0.0/universal-darwin16
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin16
==> Environment Variables
LANG="en_US.UTF-8"
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/usr/local/bin/bash"

I cannot seem to find a url for paste.rb using the current formatting - I can only find
https://cdn.hockeyapp.net/production/app/builds/016/122/272/original/3ab3bf9b674e06571448e75f59ca10e5/Paste.app.zip

But am I correct in my understanding that the HockeyApp account being used is something you all control as infrastructure?

You are not. We don’t control any source from where we install (unless you count maintainer-made apps, but that’s a different matter).

Best I could find: https://github.com/caskroom/homebrew-cask/pull/34970.

authors: miccal sholladay vitorgalvao

repo: caskroom/homebrew-cask


text:
Update Electron to 0.28.2

Bumped version to 0.28.2.

Looks good, thanks! :+1:

source: gharchive/pull-request

authors: MisumiRize alebcay


text:
Update navicat-for-mysql to 11.2.15

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Merged as 35fad9f0939147d5126905964d0ba84157cb6378.


text:
Add Xonotic

This adds a Cask for Xonotic: The Free and Fast Arena Shooter

Add Xonotic.app v0.8.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Thank you.


text:
Update private-internet-access to 80

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thanks for the PR!

authors: Cellane commitay


text:
Add HackHands v0.1.1

Adds the HackHands desktop app: https://hackhands.com/desktop

Thank you. Merged.

authors: johndbritton vitorgalvao


text:
🛑 Baked Bean is down

In 0b6b87b, Baked Bean (https://baked-bean.co.uk) was down:

HTTP code: 403
Response time: 321 ms

Resolved: Baked Bean is back up in ffe1e55.

license: MIT


text:
Fix add bid

This PR fixes the add bid subcommand of both make-transaction and put-transaction to allow users to specify the minimum and maximum delegation amounts.
Additionally, this PR allows for the optional toggling of the casper-types feature std-fs-io by consumers of the clients library.
Example
For this example command:
casper-client make-transaction add-bid --delegation-rate 10 --public-key /path/to/public_key_hex --transaction-amount 10 --min-amount 10 --max-amount 100 --payment-amount 100 --gas-price-tolerance 10 --secret-key /path/to/secret_key.pem --chain-name test --pricing-mode fixed

We get this output:
{
  "hash": "9781d52fb5580f5a6bbc1680d84273fbfd681a9d1263e638f74de619f5a5fb41",
  "header": {
    "chain_name": "test",
    "timestamp": "2024-06-10T19:51:45.970Z",
    "ttl": "30m",
    "body_hash": "c0c11fa7e097fb5efb394c6bad0b8b1a70ca852d043491fa3e72f4439c1a3b1b",
    "pricing_mode": {
      "Fixed": {
        "gas_price_tolerance": 10
      }
    },
    "initiator_addr": {
      "PublicKey": "012c51e4f064f1b8b05e0a0601a8074295894e29831dee329078bbc8fdf9ff64a4"
    }
  },
  "body": {
    "args": [
      [
        "public_key",
        {
          "cl_type": "PublicKey",
          "bytes": "012c51e4f064f1b8b05e0a0601a8074295894e29831dee329078bbc8fdf9ff64a4",
          "parsed": "012c51e4f064f1b8b05e0a0601a8074295894e29831dee329078bbc8fdf9ff64a4"
        }
      ],
      [
        "delegation_rate",
        {
          "cl_type": "U8",
          "bytes": "0a",
          "parsed": 10
        }
      ],
      [
        "amount",
        {
          "cl_type": "U512",
          "bytes": "010a",
          "parsed": "10"
        }
      ],
      [
        "minimum_delegation_amount",
        {
          "cl_type": "U64",
          "bytes": "0a00000000000000",
          "parsed": 10
        }
      ],
      [
        "maximum_delegation_amount",
        {
          "cl_type": "U64",
          "bytes": "6400000000000000",
          "parsed": 100
        }
      ]
    ],
    "target": "Native",
    "entry_point": "AddBid",
    "transaction_kind": 1,
    "scheduling": "Standard"
  },
  "approvals": [
    {
      "signer": "012c51e4f064f1b8b05e0a0601a8074295894e29831dee329078bbc8fdf9ff64a4",
      "signature": "017bbf2785897b432031753a443e692687c807c013bb62c271b0a25fcda126790386e5ba9b3142b4805c0d914edd6dac19225a476e873b53eaecc2428214612f05"
    }
  ]
}

Should this work both for V1 and V2? as in we provide the parameters for both?

authors: cspramit zacshowa

repo: casper-ecosystem/casper-client-rs


text:
[Suggestions] Five suggestions for the mod

I love the mod and am ecstatic that someone ported what is arguably the second best feature from Ender IO (the first obviously being conduits). I just have a few suggestions that I think would make the mod even better if implemented!

The ability to disguise the travel anchor as another block. This was possible in Ender IO using the painting machine. It’d be nice if you could craft the travel anchor with any block, or sneak-right-click it whilst holding any block, to disguise it as that block. Would make it a lot more aesthetically pleasing.

This has been suggested in #33 and #43, but I just want to say that I, too, would love the ability to associate a specific travel anchor with a block or item rather than a name to make the screen less cluttered and allow you to find certain travel anchors faster.

Change the text colour of a travel anchor. It’d help you find certain travel anchors, and help organize the screen a little bit, by allowing you to change the colour of a travel anchor’s text, perhaps being able to select between any of Minecraft’s sixteen default colours. Would be useful for sure!

With a travel anchor on the same Y level as another, you can teleport to the one above it, regardless of blocks in the way, by jumping, but you can’t teleport to the one below it. It’d be nice if you could teleport to a travel anchor below another one by sneaking on top of a travel anchor, similar to how the elevator from OpenBlocks Elevator works. This would allow the travel anchor to double as an elevator and a standard travel anchor.

A config option to increase the range of the sneak-right-click functionality that allows you to teleport through walls. I find that I often either don’t teleport at all or teleport up to the wall and not through it. It’d be nice to have a config option that allows you to increase the range at which you can teleport through a wall/floor/ceiling.

For 1, put the block you want to use into your off-hand, empty the main hand and right-click the travel anchor. The anchor now mimics this block.

Should already be possible. Might be disabled in your client config though. Maybe take a look there: config/travel_anchors/client.json5

5: has been added.
3: Won't be implemented as the colour is used to highlight which anchor the player is about to teleport to.
This only leaves 2. which is a duplicate of #33, so I'm going to close this issue now.


text:
Organize FERC 1 XBRL metadata with a calculation forest

PR Overview

Add correction records to the processed XBRL metadata dataframe, so that it matches what's found in the calculations and the post-corrected dataframes.
Introduces a tree structure for management of the relationships between nested calculations across different FERC tables.
The XbrlCalculationTreeFerc1 and XbrlCalculationForestFerc1 can be used to modify metadata and propagate it to child calculations so it can be applied to all the XBRL facts that make up the leaves of the tree.

PR Checklist

[x] Merge the most recent version of the branch you are merging into (probably dev).
[x] Make sure you've included good docstrings.
[x] Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.
[ ] All CI checks are passing. Run tests locally to debug failures
[ ] For major data coverage & analysis changes, run data validation tests
[ ] Include unit tests for new functions and classes.
[ ] Defensive data quality/sanity checks in analyses & data processing functions.
[ ] Update the release notes and reference reference the PR and related issues.

The addition of metadata for the calculation correction records seems to have broken something in the table transforms:
dagster._core.errors.DagsterExecutionStepExecutionError: Error occurred while executing op "electric_operating_revenues_ferc1":

  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_plan.py", line 273, in dagster_event_sequence_for_step
    for step_event in check.generator(step_events):
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_step.py", line 369, in core_dagster_event_sequence_for_step
    for user_event in check.generator(
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/execute_step.py", line 90, in _step_output_error_checked_user_event_sequence
    for user_event in user_event_sequence:
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/compute.py", line 192, in execute_core_compute
    for step_output in _yield_compute_results(step_context, inputs, compute_fn):
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/compute.py", line 161, in _yield_compute_results
    for event in iterate_with_context(
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_utils/__init__.py", line 443, in iterate_with_context
    with context_fn():
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/contextlib.py", line 155, in __exit__
    self.gen.throw(typ, value, traceback)
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/utils.py", line 84, in op_execution_error_boundary
    raise error_cls(

The above exception was caused by the following exception:
KeyError: "None of [Int64Index([-2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -1, -1, -1, -1, -1, -1, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2, -2], dtype='int64')] are in the [columns]"

  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/utils.py", line 54, in op_execution_error_boundary
    yield
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_utils/__init__.py", line 445, in iterate_with_context
    next_output = next(iterator)
                  ^^^^^^^^^^^^^^
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/compute_generator.py", line 124, in _coerce_op_compute_fn_to_iterator
    result = invoke_compute_fn(
             ^^^^^^^^^^^^^^^^^^
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/dagster/_core/execution/plan/compute_generator.py", line 118, in invoke_compute_fn
    return fn(context, **args_to_pass) if context_arg_provided else fn(**args_to_pass)
                                                                    ^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/transform/ferc1.py", line 4855, in ferc1_transform_asset
    df = transformer.transform(
         ^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/transform/classes.py", line 1190, in transform
    .pipe(self.transform_end)
     ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/pandas/core/generic.py", line 5839, in pipe
    return com.pipe(self, func, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/pandas/core/common.py", line 513, in pipe
    return func(obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/transform/classes.py", line 1022, in _wrapper
    df = func(self, *args, **kwargs)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/transform/ferc1.py", line 1232, in transform_end
    df = self.reconcile_table_calculations(df).pipe(self.enforce_schema)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/transform/ferc1.py", line 2511, in reconcile_table_calculations
    df = reconcile_table_calculations(
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/code/catalyst/pudl/src/pudl/transform/ferc1.py", line 776, in reconcile_table_calculations
    tbl_meta[~tbl_meta.intra_table_calc_flag].xbrl_factoid.unique()
    ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/pandas/core/frame.py", line 3813, in __getitem__
    indexer = self.columns._get_indexer_strict(key, "columns")[1]
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/pandas/core/indexes/base.py", line 6070, in _get_indexer_strict
    self._raise_if_missing(keyarr, indexer, axis_name)
  File "/Users/zane/mambaforge/envs/pudl-dev/lib/python3.11/site-packages/pandas/core/indexes/base.py", line 6130, in _raise_if_missing
    raise KeyError(f"None of [{key}] are in the [{axis_name}]")

The above error was due to the fact that when creating the metadata records for the corrections, we were producing a dataframe with a mix of bool and boolean types -- which looks like it's fine, but is actually an object column.  It can be used to select records in a dataframe just fine as it is, but if you negate it with the ~ operator, it doesn't behave like a boolean column.  Instead the objects get converted into random integers, which act like an index not a boolean mask.  Ugh.

Okay, an example of a closer to functional calculation tree.
import json
from pudl.output.ferc1 import MetadataExploder, resolve_calculation_components

balance_sheet_asset_tables = [
    "balance_sheet_assets_ferc1",
    "utility_plant_summary_ferc1",
    "plant_in_service_ferc1",
]

exploded_meta = (
    MetadataExploder(balance_sheet_asset_tables).boom(xbrl_meta)
)[[
    "table_name",
    "xbrl_factoid",
    "calculations",
    "intra_table_calc_flag",
    "xbrl_factoid_original",
]]

calculation_tree = resolve_calculation_components(
    exploded_meta=exploded_meta.set_index(["table_name", "xbrl_factoid"]),
    xbrl_factoid="utility_plant_net",
    table_name="balance_sheet_assets_ferc1",
)

print(json.dumps(calculation_tree.dict(), indent=4))

{
    "components": [
        {
            "name": "utility_plant_and_construction_work_in_progress",
            "weight": 1.0,
            "source_tables": [
                "balance_sheet_assets_ferc1"
            ],
            "calculation": {
                "components": [
                    {
                        "name": "utility_plant",
                        "weight": 1.0,
                        "source_tables": [
                            "balance_sheet_assets_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "balance_sheet_assets_ferc1",
                            "xbrl_factoid": "utility_plant",
                            "xbrl_factoid_original": "utility_plant"
                        }
                    },
                    {
                        "name": "utility_plant_in_service_classified_and_unclassified",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [
                                {
                                    "name": "utility_plant_in_service_classified",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "utility_plant_in_service_classified",
                                        "xbrl_factoid_original": "utility_plant_in_service_classified"
                                    }
                                },
                                {
                                    "name": "utility_plant_in_service_property_under_capital_leases",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "utility_plant_in_service_property_under_capital_leases",
                                        "xbrl_factoid_original": "utility_plant_in_service_property_under_capital_leases"
                                    }
                                },
                                {
                                    "name": "utility_plant_in_service_plant_purchased_or_sold",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "utility_plant_in_service_plant_purchased_or_sold",
                                        "xbrl_factoid_original": "utility_plant_in_service_plant_purchased_or_sold"
                                    }
                                },
                                {
                                    "name": "utility_plant_in_service_completed_construction_not_classified",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "utility_plant_in_service_completed_construction_not_classified",
                                        "xbrl_factoid_original": "utility_plant_in_service_completed_construction_not_classified"
                                    }
                                },
                                {
                                    "name": "utility_plant_in_service_experimental_plant_unclassified",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "utility_plant_in_service_experimental_plant_unclassified",
                                        "xbrl_factoid_original": "utility_plant_in_service_experimental_plant_unclassified"
                                    }
                                },
                                {
                                    "name": "utility_plant_in_service_classified_and_unclassified_correction",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "utility_plant_in_service_classified_and_unclassified_correction",
                                        "xbrl_factoid_original": "utility_plant_in_service_classified_and_unclassified"
                                    }
                                }
                            ],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "utility_plant_in_service_classified_and_unclassified",
                            "xbrl_factoid_original": "utility_plant_in_service_classified_and_unclassified"
                        }
                    },
                    {
                        "name": "utility_plant_leased_to_others",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "utility_plant_leased_to_others",
                            "xbrl_factoid_original": "utility_plant_leased_to_others"
                        }
                    },
                    {
                        "name": "utility_plant_held_for_future_use",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "utility_plant_held_for_future_use",
                            "xbrl_factoid_original": "utility_plant_held_for_future_use"
                        }
                    },
                    {
                        "name": "construction_work_in_progress",
                        "weight": 1.0,
                        "source_tables": [
                            "balance_sheet_assets_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "balance_sheet_assets_ferc1",
                            "xbrl_factoid": "construction_work_in_progress",
                            "xbrl_factoid_original": "construction_work_in_progress"
                        }
                    },
                    {
                        "name": "utility_plant_acquisition_adjustment",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "utility_plant_acquisition_adjustment",
                            "xbrl_factoid_original": "utility_plant_acquisition_adjustment"
                        }
                    },
                    {
                        "name": "utility_plant_and_construction_work_in_progress_correction",
                        "weight": 1.0,
                        "source_tables": [
                            "balance_sheet_assets_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "balance_sheet_assets_ferc1",
                            "xbrl_factoid": "utility_plant_and_construction_work_in_progress_correction",
                            "xbrl_factoid_original": "utility_plant_and_construction_work_in_progress"
                        }
                    }
                ],
                "source_table": "balance_sheet_assets_ferc1",
                "xbrl_factoid": "utility_plant_and_construction_work_in_progress",
                "xbrl_factoid_original": "utility_plant_and_construction_work_in_progress"
            }
        },
        {
            "name": "accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility",
            "weight": -1.0,
            "source_tables": [
                "balance_sheet_assets_ferc1"
            ],
            "calculation": {
                "components": [
                    {
                        "name": "depreciation_utility_plant_in_service",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "depreciation_utility_plant_in_service",
                            "xbrl_factoid_original": "depreciation_utility_plant_in_service"
                        }
                    },
                    {
                        "name": "amortization_and_depletion_of_producing_natural_gas_land_and_land_rightsutility_plant_in_service",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "amortization_and_depletion_of_producing_natural_gas_land_and_land_rightsutility_plant_in_service",
                            "xbrl_factoid_original": "amortization_and_depletion_of_producing_natural_gas_land_and_land_rightsutility_plant_in_service"
                        }
                    },
                    {
                        "name": "amortization_of_underground_storage_land_and_land_rightsutility_plant_in_service",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "amortization_of_underground_storage_land_and_land_rightsutility_plant_in_service",
                            "xbrl_factoid_original": "amortization_of_underground_storage_land_and_land_rightsutility_plant_in_service"
                        }
                    },
                    {
                        "name": "amortization_of_other_utility_plant_utility_plant_in_service",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "amortization_of_other_utility_plant_utility_plant_in_service",
                            "xbrl_factoid_original": "amortization_of_other_utility_plant_utility_plant_in_service"
                        }
                    },
                    {
                        "name": "depreciation_amortization_and_depletion_utility_plant_in_service",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "depreciation_amortization_and_depletion_utility_plant_in_service",
                            "xbrl_factoid_original": "depreciation_amortization_and_depletion_utility_plant_in_service"
                        }
                    },
                    {
                        "name": "depreciation_amortization_and_depletion_utility_plant_leased_to_others",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [
                                {
                                    "name": "depreciation_utility_plant_leased_to_others",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "depreciation_utility_plant_leased_to_others",
                                        "xbrl_factoid_original": "depreciation_utility_plant_leased_to_others"
                                    }
                                },
                                {
                                    "name": "amortization_and_depletion_utility_plant_leased_to_others",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "amortization_and_depletion_utility_plant_leased_to_others",
                                        "xbrl_factoid_original": "amortization_and_depletion_utility_plant_leased_to_others"
                                    }
                                },
                                {
                                    "name": "depreciation_amortization_and_depletion_utility_plant_leased_to_others_correction",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "depreciation_amortization_and_depletion_utility_plant_leased_to_others_correction",
                                        "xbrl_factoid_original": "depreciation_amortization_and_depletion_utility_plant_leased_to_others"
                                    }
                                }
                            ],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "depreciation_amortization_and_depletion_utility_plant_leased_to_others",
                            "xbrl_factoid_original": "depreciation_amortization_and_depletion_utility_plant_leased_to_others"
                        }
                    },
                    {
                        "name": "depreciation_and_amortization_utility_plant_held_for_future_use",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [
                                {
                                    "name": "depreciation_utility_plant_held_for_future_use",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "depreciation_utility_plant_held_for_future_use",
                                        "xbrl_factoid_original": "depreciation_utility_plant_held_for_future_use"
                                    }
                                },
                                {
                                    "name": "amortization_utility_plant_held_for_future_use",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "amortization_utility_plant_held_for_future_use",
                                        "xbrl_factoid_original": "amortization_utility_plant_held_for_future_use"
                                    }
                                },
                                {
                                    "name": "depreciation_and_amortization_utility_plant_held_for_future_use_correction",
                                    "weight": 1.0,
                                    "source_tables": [
                                        "utility_plant_summary_ferc1"
                                    ],
                                    "calculation": {
                                        "components": [],
                                        "source_table": "utility_plant_summary_ferc1",
                                        "xbrl_factoid": "depreciation_and_amortization_utility_plant_held_for_future_use_correction",
                                        "xbrl_factoid_original": "depreciation_and_amortization_utility_plant_held_for_future_use"
                                    }
                                }
                            ],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "depreciation_and_amortization_utility_plant_held_for_future_use",
                            "xbrl_factoid_original": "depreciation_and_amortization_utility_plant_held_for_future_use"
                        }
                    },
                    {
                        "name": "abandonment_of_leases",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "abandonment_of_leases",
                            "xbrl_factoid_original": "abandonment_of_leases"
                        }
                    },
                    {
                        "name": "amortization_of_plant_acquisition_adjustment",
                        "weight": 1.0,
                        "source_tables": [
                            "utility_plant_summary_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "utility_plant_summary_ferc1",
                            "xbrl_factoid": "amortization_of_plant_acquisition_adjustment",
                            "xbrl_factoid_original": "amortization_of_plant_acquisition_adjustment"
                        }
                    },
                    {
                        "name": "accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility_correction",
                        "weight": 1.0,
                        "source_tables": [
                            "balance_sheet_assets_ferc1"
                        ],
                        "calculation": {
                            "components": [],
                            "source_table": "balance_sheet_assets_ferc1",
                            "xbrl_factoid": "accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility_correction",
                            "xbrl_factoid_original": "accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility"
                        }
                    }
                ],
                "source_table": "balance_sheet_assets_ferc1",
                "xbrl_factoid": "accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility",
                "xbrl_factoid_original": "accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility"
            }
        },
        {
            "name": "utility_plant_net_correction",
            "weight": 1.0,
            "source_tables": [
                "balance_sheet_assets_ferc1"
            ],
            "calculation": {
                "components": [],
                "source_table": "balance_sheet_assets_ferc1",
                "xbrl_factoid": "utility_plant_net_correction",
                "xbrl_factoid_original": "utility_plant_net"
            }
        }
    ],
    "source_table": "balance_sheet_assets_ferc1",
    "xbrl_factoid": "utility_plant_net",
    "xbrl_factoid_original": "utility_plant_net"
}

I think this actually has to do with issue #2623 rather than with anything incorrect in the metadata.
The utility_plant_summary table:

The plant_in_service table:

Where there is an electric utility type, these values should come from the plant_in_service table. These definitions don't seem to be explicitly defined in the metadata, however, since the values only originate out of table if they refer to an electric utility specifically.

@e-belfer Thank you for checking on the plant_in_service references!  I think I confused myself by doing:
exploded_meta[exploded_meta.calculations.str.contains("plant_in_service")]

which of course DOES find a bunch of metadata records but... that's just because other facts contain that substring.
If I look more specifically for just the "plant_in_service" string as a standalone reference to a source table:
exploded_meta[exploded_meta.calculations.str.contains('"plant_in_service"')]

I find no matching metadata records.

I agree about the flow of the methods not being great. I'm not sure how to structure the class / methods such that the methods are only being called / relied upon when appropriate -- like having propagated the tags / weights before trying to generate a leafy metadataframe, or construct a calculation with the weights.
There are several things we need to do with the leafy metadata:

Need the list of leaf facts, and the root facts that they are associated with, along with all the metadata that is associated with each leaf. This is used to remove irrelevant records from the exploded dataframe and to merge useful metadata onto the exploded dataframe.
Need to be able to calculate the root values based only on the most granular reported leaf values using our existing infrastructure, so that we know we didn't mess anything.
Need to use the propagated / adjusted weights to adjust the values in exploded dataframe.
Will be feeding information into reconcile_table_calcs() to verify the calculations.

Okay, I have the exploded data, pruned to include only the most granular values (leaves) for the balance sheet assets tables. The tables I'm including:
balance_sheet_asset_tables = [
    "balance_sheet_assets_ferc1",
    "utility_plant_summary_ferc1",
    "plant_in_service_ferc1",
    "electric_plant_depreciation_functional_ferc1",
]

Caveats:

The plant_in_service_ferc1 table still isn't connected to the rest of the tree by a calculation. I'm including it by adding its root node explicitly.
The calculations and tree relationships are not yet aware of additional dimensions like utility_type
We need more robust internal consistency checks on our edits to the calculations. They're hand compiled and likely to contain some errors.
There's one instance in which the same facts really do show up in two different calculations, which means the tree isn't really a tree:

The facts being calculated:
[
    NodeId(source_table='balance_sheet_assets_ferc1', xbrl_factoid='current_and_accrued_assets'),
    NodeId(source_table='balance_sheet_assets_ferc1', xbrl_factoid='other_property_and_investments'),
]

The duplicated components:
[
    NodeId(source_table='balance_sheet_assets_ferc1', xbrl_factoid='noncurrent_portion_of_allowances'),
    NodeId(source_table='balance_sheet_assets_ferc1', xbrl_factoid='derivative_instrument_assets_long_term'),
    NodeId(source_table='balance_sheet_assets_ferc1', xbrl_factoid='derivative_instrument_assets_hedges_long_term')
]

There's one real node that is being orphaned -- it shows up in the metadata, but is never referenced in any calculation -- is this expected and desired? NodeId('utility_plant_summary_ferc1', 'depreciation_amortization_and_depletion_utility_plant_in_service')
There's one node NodeId(source_table='utility_plant_summary_ferc1', xbrl_factoid='accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility') that is part of a redirect, and it's also involved in a calculation with a negative sign, so it shows up twice in the construction of the tree, but with different signs, which creates a conflict. Somehow we need to identify the passthrough nodes preemptively and just not add them during construction, rather than removing them after the fact.

NodeId('utility_plant_summary_ferc1', 'depreciation_amortization_and_depletion_utility_plant_in_service') is currently being orphaned -- it shows up in the metadata but not in any calculation. Is this expected / desired?

**This is the desired outcome -- it is being replaced by its constituent parts.

There's one node NodeId(source_table='utility_plant_summary_ferc1', xbrl_factoid='accumulated_provision_for_depreciation_amortization_and_depletion_of_plant_utility') that is part of a redirect, and it's also involved in a calculation with a negative sign, so it shows up twice in the construction of the tree, but with different signs, which creates a conflict. Somehow we need to identify the passthrough nodes preemptively and just not add them during construction, rather than removing them after the fact.

I'm setting the weight to -1.0 if the weights are not the same, and they multiply to equal -1.0.*

I think I have responded to all of your comments and made some minor changes.  Bigger questions and higher level responses:
Other than breaking out the visualization, I'm not a fan of breaking the class up into smaller pieces, because those pieces will still be very tightly coupled to each other. The difference between the full, seeded, and pruned (forest) graphs isn't just what nodes and edges they contain -- there are relationships between them and they get used together in several methods, and having all those methods in the same class, which knows how to produce those different graphs based on the relatively simple top level inputs seems simpler to me than having a bunch of that logic outside of the class, and working with multiple simpler instances of graphs.
TODO:
I think it makes sense to pull the plotting / visualization out into a standalone function that takes one of the output digraphs as an argument, so I'll do that.
QUESTIONS
What should we do about the fact that the ratio of valid calculations is apparently quite variable by year, and the most recent years (including the XBRL data that the calculations are derived from...) do worse than the historical average, to the point where the CI fails?
Do you want me to go ahead and define database table schemas for the new exploded_* assets in this PR?
I looked at making the index columns an attribute of the XbrlCalculationForest class, so that as we move that indexing / definition further upstream we can pass it in. However, at the moment refactoring the class to use a generic index attribute looks kind of painful for 2 reasons:

We're still dealing with two different sets of names for these columns (source_tables, name) and (table_name, xbrl_factoid)
In a variety of contexts we use just one element of the index for other purposes, and those would still be hard coded, or we would need to add other attributes that indicate what value to look at for what's currently the table name or the fact columns.
Should I just go ahead and store the index columns in the class for now and not worry about those other hard-codings?

@cmgosnell:

I've simplified the plotting so there's just one method
I've stored the exploded metadata index columns in the calculation forest class -- we'll need to revisit this and migrate it up into other higher level classes as we deal with the dimensions and refactor.
I've bumped the calculation error tolerances for the income statement and balance sheet liability tables so that they pass CI -- I think, anyway.  I'm getting the same divide by zero error that @e-belfer was getting now, since I merged in her changes from upstream.  So I don't know if the thresholds are actually high enough.
Holding off on defining the DB tables until we're ready to merge into dev
Still need to merge the multi-parent fixes from @e-belfer in the balance sheet liabilities table.

authors: e-belfer zaneselvans

repo: catalyst-cooperative/pudl

license: mit

license_source: bigquery


text:
Reading RDB files

From what I can tell there are two ways to read data from RDB files:

Actually run a Redis server with that file as the database. The server needs to be started outside of Python (though ofc we can use like os.system() or something) but once it's running, we can query it through a Python package Redis provides. However, I can't get Redis running on my machine with their RDB file because I run out of RAM - it seems to need more than 12 GB. Presumably they are able to run it though, so that might not be an issue?
Parse the raw RDB file directly. There is one Python package for this but it's no longer maintained and does not support the newest RDB file version (which is the file version we have). So, we'd probably have to make the necessary modifications for that ourselves, and maintain it as Redis continues to update its file format.

If this is a tool they want to use themselves, then probably best to go with option 1. In that case, best step might be to ask them for a smaller RDB file?

However, I can't get Redis running on my machine with their RDB file because I run out of RAM - it seems to need more than 12 GB. Presumably they are able to run it though, so that might not be an issue?

For better computational resources, check out the DANDI Hub. See if you can spin up the server there
However, #2 is greatly preferred if at all possible. That way we can ensure completely lazy access at all times
Wow, the repo has 700+ forks lol
Did you check out this PR by someone's fork that extended the version? https://github.com/sripathikrishnan/redis-rdb-tools/pull/186

Also curious is https://pypi.org/project/rdb-cli/ allows you do extract every data stream and map it to JSON (either a pre-step to get a JSON version of the file, or if there are utility functions for parsing contents via an API?)

Quick update:

DANDI Hub worked for running the Redis server with the RDB they provide, and I can access the data, etc.
rdb-cli has implemented some of the changes to support RDB file version 10, so its in better shape than redis-rdb-tools, but it still can't open the file we received. Specifically, it's failing on a data type they're calling REDIS_RDB_TYPE_STREAM_LISTPACKS_2. Have to dig more deeply into the code to see what kind of work addressing these issues would entail.

OK, #1 can work then if we can confirm that is how they are used to running the system; can you check with them on that?

Yeah sure! Could you (or Ben) loop me in on the email thread?

Ok, so we'll move ahead with running a Redis server and querying through their official Python interface, since the Stavisky lab should have the server running (or can easily get it running) whenever they use our conversion scripts. Closing this for now...

repo: catalystneuro/stavisky-lab-to-nwb


text:
[FEAT] Add asset pack

Is your feature request related to a problem? Please describe.
Add asset pack to the module
Describe the solution you'd like
A clear and concise description of what you want to happen.
Create svgs for each macro and item and add it to an asset group that will be loaded into foundry
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

 Add Asset Pack


text:
Error while linting

I got this error on the console:
DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo bar:has(baz)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo.x bar.y:has(baz.z)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .foo:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip .bap

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip:has(.bap)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: x:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: y:has(.bap)

SCSSLint::Linter::BangFormat raised unexpected error linting file node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass-todo-tests/libsass/lists/input.scss: '[BUG] Unknown operator nil'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/parser.rb:206:in `precedence_of'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/tree/list_literal.rb:33:in `block in to_sass'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/tree/list_literal.rb:32:in `map'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/script/tree/list_literal.rb:32:in `to_sass'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/prop_node.rb:132:in `val_to_sass'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/prop_node.rb:109:in `declaration'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/convert.rb:233:in `visit_prop'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:36:in `visit'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/convert.rb:10:in `visit'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/node.rb:201:in `to_sass'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter/bang_format.rb:9:in `visit_prop'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:36:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:127:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:138:in `block in visit_children'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `visit_children'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:38:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:127:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:138:in `block in visit_children'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:136:in `visit_children'
/Library/Ruby/Gems/2.0.0/gems/sass-3.4.6/lib/sass/tree/visitors/base.rb:38:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:127:in `visit'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/linter.rb:21:in `run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:58:in `run_linter'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:39:in `block in find_lints'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:37:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:37:in `find_lints'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:21:in `block in run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:20:in `each'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/runner.rb:20:in `run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/cli.rb:52:in `scan_for_lints'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/cli.rb:46:in `act_on_options'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/lib/scss_lint/cli.rb:25:in `run'
/Library/Ruby/Gems/2.0.0/gems/scss-lint-0.33.0/bin/scss-lint:6:in `<top (required)>'
/usr/bin/scss-lint:23:in `load'
/usr/bin/scss-lint:23:in `<main>'
Report this bug at https://github.com/causes/scss-lint/issues

This is my .scss-lint.yml file:
scss_files: "public/style/scss/**/*.scss"

linters:
  BorderZero:
    enabled: true
    convention: 0

  ColorKeyword:
    enabled: true

  ColorVariable:
    enabled: true

  Comment:
    enabled: true

  DeclarationOrder:
    enabled: true

  DuplicateProperty:
    enabled: true

  EmptyLineBetweenBlocks:
    enabled: true

  EmptyRule:
    enabled: true

  FinalNewline:
    enabled: true

  HexLength:
    enabled: true
    style: long

  HexNotation:
    enabled: true
    style: lowercase

  IdSelector:
    enabled: true

  ImportantRule:
    enabled: true

  ImportPath:
    enabled: true

  Indentation:
    enabled: true

  LeadingZero:
    enabled: true

  MergeableSelector:
    enabled: true
    force_nesting: true

  NameFormat:
    enabled: true
    allow_leading_underscore: false

  NestingDepth:
    enabled: true
    max_depth: 2

  PropertySpelling:
    enabled: true
    extra_properties:
      - will-change

  QualifyingElement:
    enabled: true

  Shorthand:
    enabled: true

  SingleLinePerProperty:
    enabled: true
    allow_single_line_rule_sets: false

  SingleLinePerSelector:
    enabled: true

  SpaceAfterComma:
    enabled: true

  SpaceAfterPropertyColon:
    enabled: true

  SpaceBeforeBrace:
    enabled: true

  SpaceBetweenParens:
    enabled: true

  StringQuotes:
    enabled: true

  TrailingSemicolon:
    enabled: true

  TrailingZero:
    enabled: true

  UnnecessaryMantissa:
    enabled: true

  UnnecessaryParentReference:
    enabled: true

  UrlFormat:
    enabled: true

  UrlQuotes:
    enabled: true

  VariableForProperty:
    enabled: true
    properties:
      - color
      - font
      - box-shadow
      - border

  VendorPrefixes:
    enabled: true

  ZeroUnit:
    enabled: true

It took about 30 seconds for the error to appear, and it was the first and only output I received.
OSX 10.10.2, Ruby 2.0.0p481

Tested with Ruby 2.2.0, same result

Thanks for the report @albertorestifo! It seems to be blowing up on this file: https://github.com/sass/sass-spec/blob/master/spec/libsass-todo-tests/libsass/lists/input.scss
I'll need some more time to look into this, but in the meantime it would be helpful if you could whittle it down to a small repro case.
Also, it looks like you are linting your node_modules directory which contains third-party code that you probably don't really want to be linting. You probably want to add this to your configuration file:
exclude:
  - 'node_modules/**'

@sds do you think it would make sense to add this exclusion to the default.yml config?

@lencioni I'm really sorry but it's a private project, and also a quite big one (there are 41 different SCSS files).
If you see any specific file that's causing the bug I can post it

As I mentioned, it seems to be blowing up on this file, which is already public: https://github.com/sass/sass-spec/blob/master/spec/libsass-todo-tests/libsass/lists/input.scss

@lencioni  by the way, about the node_modules question, the behaviour I was expecting was the following:
I have specified the files I wanted to lint, using:
scss_files: "public/style/scss/**/*.scss"

What I expect is that only those files are going to be considered. I think this should be the correct behaviour

The originally reported issue is a bug with the to_sass method of the Sass::Tree::Node class of the sass gem. In other words, not a problem on scss-lint's end.
However, I was able to work around the problem on scss-lint's side by removing our use of to_sass from a few linters in c72392b7e59f029be96ba8ee518b9a7403c9aff9.

Unfortunately v0.39.0 doesn't fix the problem for me.
The following errors occur:
$ /bin/sh -c scss-lint /path/to/some/scss/file.scss --config=/path/to/scss-lint/config/scss-lint.yml --format=XML
DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo bar:has(baz)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: foo.x bar.y:has(baz.z)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .foo:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip .bap

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: .bip:has(.bap)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: x:has(.bar)

DEPRECATION WARNING on line 1, column 1:
The subject selector operator "!" is deprecated and will be removed in a future release.
This operator has been replaced by ":has()" in the CSS spec.
For example: y:has(.bap)

SCSSLint::Linter::LeadingZero raised unexpected error linting file node_modules/becklyn-gulp/node_modules/gulp-sass/node_modules/node-sass/test/fixtures/spec/spec/libsass-todo-tests/libsass/propsets/input.scss: 'undefined method `[]' for nil:NilClass'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter/leading_zero.rb:18:in `visit_script_number'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:36:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:142:in `block in visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:140:in `visit_children'
/usr/local/lib/ruby/gems/2.1.0/gems/sass-3.4.14/lib/sass/tree/visitors/base.rb:38:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:131:in `visit'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/linter.rb:25:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:48:in `run_linter'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:29:in `block in find_lints'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:27:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:27:in `find_lints'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:17:in `block in run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:16:in `each'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/runner.rb:16:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/cli.rb:54:in `scan_for_lints'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/cli.rb:48:in `act_on_options'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/lib/scss_lint/cli.rb:27:in `run'
/usr/local/lib/ruby/gems/2.1.0/gems/scss_lint-0.39.0/bin/scss-lint:6:in `<top (required)>'
/usr/local/bin/scss-lint:23:in `load'
/usr/local/bin/scss-lint:23:in `<main>'
Report this bug at https://github.com/brigade/scss-lint/issues

To help fix this issue, please include:
- The above stack trace
- SCSS-Lint version: 0.39.0
- Sass version: 3.4.14
- Ruby version: 2.1.2

even though the refernced scss-lint.yml file has the following settings
exclude:
    - '/**/vendor/**'
    - '/**/node_modules/**'
    - 'node_modules/**'
    - '../node_modules/**'
    - '**/node_modules/**'
    - '*/node_modules/**'

The massive amount of glob patterns were just a test to really make sure it's not a configuration issue on our side. It seems like scss-lint is still scanning the directories it shouldn't want which makes it slower as needed and more importantly cause exceptions.
I've already tried removing everything that is related to ruby (by executing rvm implode) and then re-installed it via rvm again to make sure it's a fresh installation.
Any ideas what I could try in order to fix the issue?

Hey @cH40z-Lord,
The following configuration excludes all files in the node_modules directory from all linters. I've tested it locally with scss-lint 0.39.0 and it works as expected.
exclude:
  - node_modules/**

authors: albertorestifo cH40z-Lord lencioni sds

repo: causes/scss-lint


text:
chore: bdd-spring-1582612821 to 0.0.1

chore: Promote bdd-spring-1582612821 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
chore: bdd-gh-1582908980 to 0.0.1

chore: Promote bdd-gh-1582908980 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
chore: bdd-sbhg-1584420149 to 0.0.1

chore: Promote bdd-sbhg-1584420149 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
chore: bdd-nh-1574165139 to 0.0.1

chore: Promote bdd-nh-1574165139 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


text:
libfuse high level bindings

libfuse offers two APIs: a "high-level", synchronous API, and a "low-level" asynchronous API. The current fuser offers bindings to the latter one and works with inodes. However, that's not particularly convenient for simple fs.
Is there any plan for the high level API binding? That would be very useful.

Not at this time. fuser is mainly in maintenance mode at the moment.

repo: cberner/fuser


text:
Modernizr not found on cardinalcss.com

It was brought to my attention that Modernizr is not being loaded correctly on http://cardinalcss.com.
...soooo, fix that! :metal:

Removed Modernizr for now since I wasn't even using it. Problem solved!

repo: cbracco/cardinal


text:
Is there a way to cap width of widget?

It looks like a similar ask was raised in https://github.com/cbrooker/MMM-Todoist/issues/27, so close this if it's the same answer.
Is there a max width I can apply?  I'm not super familiar w/ how MMirror does all it's layouts and width calculations for the grid, but it looks like the do not put a hard limit on width?
I have one really long task in Todoist/Inbox.  It's not a common thing, just a kinda occasional edge-case.  This really long task is stretching out the widget so it's clobbering others.  I'll get this task cleaned up / organized soon, so it'll stop being an issue soon... I just wanted to ask while i still noticed / could take a screenshot.

Is there something that i can do w/ the API to limit this or should i get a quick PR in?
JS is ... not a core strength of mine, so it'd be dirty / look something like:
item.length >= 60 ? item.substring(0,60) : item
(where 60 should probably be something users can override...)
somewhere around here:
https://github.com/cbrooker/MMM-Todoist/blob/master/MMM-Todoist.js#L95
-K

Hello,
I just propose a pull request to allow to display tasks on several lines (as the official module "calendar").
You can check it on the "Pull request" tab or here

repo: cbrooker/MMM-Todoist


text:
Runtime issues with the example

After the migration to rescript-react has been merged, @jsiebern noticed a problem with the example.
I am opening an issue mainly to discuss what is happening, what could be involved and, in case, how this could be fixed.

Using the debugger, it is possible to see that module @material-ui/styles/esm/useTheme/useTheme.js imports ThemeContext from './ThemeContext'. However this is undefined, causing the hook error inside useTheme. This function is called from useStyles, which, if I am not wrong, is called from AppLayout.res:15.
What I don't get is the fact that ThemeContext.js exists inside @material-ui/styles/esm/useTheme. This makes me think that the issue could be related to some strange behavior of webpacking...? Let me know what you think.

Just built version 2.1.0 together with @jsiebern, and we did not encounter any problem with the examples.

Fantastic!!! I just finished checking, and I did not encounter the issue anymore as well. Probably you fixed the issue during the refactory you made since I opened the issue.
Thank you for your awesome work!

authors: cknitt dodomorandi

repo: cca-io/rescript-material-ui


text:
model folder problem, and code modifications

Hi.
While running the code at https://github.com/ccoreilly/vosk-browser/tree/gh-pages using Firefox and local server, the index.html file would not run. I inspected the source code, and the relative path of model given was "vosk-browser\models\vosk-model-small-en-us-0.15.tar.gz", which I corrected to "models\vosk-model-small-en-us-0.15.tar.gz".
I corrected the code in index.html, and the code ran, and generated Speech-to-text through given audio file (Direct audio through mic still didn't worked, though mic worked, but all it did was sending audio chunks and never display the results in the textarea).
If I need to modify the code, I am unable to do that. How do I modify it. Can you provide the source code?
thanks.

The code in the gh-pages branch is the build result of the react code found here https://github.com/ccoreilly/vosk-browser/tree/master/examples/react

authors: awaisnaz ccoreilly

repo: ccoreilly/vosk-browser


text:
关于索引搭建问题

按照教程已经成功搭建了appspot的网页，但是my一直显示internal server error，查了一下是索引没搭建好。但是我的索引一直处于编制过程，并且按照FAQ手动更新quese和重新部署好几次，依然是这种一直在搭建索引的情况。请教大神如何处理？

日志是这样显示的

打开logs下的日志详情是这样的

@miaowm5

@cdhigh 求大神帮忙

repo: cdhigh/KindleEar


text:
Add Syntax Template Capability

See DDF-RA #16

This will not be part of the 2.1 branch.

@dih-cdisc We are discussing this item and we are uncertain if you are hoping for this to be delivered this Sprint.  The other option is that we are still refining this item to be delivered in maybe the next Sprint.
Comment?

@dih-cdisc We are discussing this item and we are uncertain if you are hoping for this to be delivered this Sprint. The other option is that we are still refining this item to be delivered in maybe the next Sprint.
Comment?

Not for this sprint.

Hi @cupkes, @MarkPAndrews and @dih-cdisc ,
I have some questions based on the information in ticket 16

I now understand that you can have 1 or more dictionaries linking to a list of syntax templates? Would that then be a dictionary for each kind of data? For example an Objectives dictionary, an endpoints dictionary, an eligibility dictionary etc?
Are you including JSON as content of the attribute parameterMap to define the different references in the templates?
Do those references then link to the corresponding place in the USDM model? For example if I link to interventions do I then get the content of InvestigationalIntervention? And how does the system know which one to take? Because may be multiple.

authors: BSnoeijerCD dih-cdisc drewcdisc

repo: cdisc-org/DDF-RA


text:
Test Endpoint support rules involving Library Standards and Codelists

Acceptance criteria

Library standards and code lists metadata are available
A single version of the IG standard should be provided
A list of CT package versions should be provided

Me and developer @nhaydel worked on this one but were unable to find a way to run the azure function locally, I will end review on this issue as soon as we are able to get to run the function from azure locally.

The code modifications pertaining to this matter have undergone a comprehensive review process. The alterations effectively adhere to the Acceptance Criteria (AC) defined for this particular issue. Furthermore, manual testing has been conducted, employing a JSON payload that encompasses the necessary standards and an array of code lists. The payload has been meticulously designed to align with the specified acceptance criteria requirements. As a result of this testing, successful responses were obtained when utilizing POST commands. Visual evidence of these successful responses can be observed in the accompanying screenshot.
Consequently, the issue has successfully passed the quality assurance validations and is now ready for closure.

Validation Summary
Validation Methodology:
The validation process incorporated rigorous testing methodologies to ensure the accuracy and reliability of the system. This included:
Manual Testing:
Manual Testing was done to verify the implementation of the Acceptance criteria. A JSON payload with necessary requirements were sent to the rules engine, and the responses were checked to verify proper working.
Code Review:
The code changes in the code files were reviewed and were found to be in accordance with the Acceptance criteria. Also, the code was reviewed for following:

Code Quality Evaluation
Logic and Functionality Review
Error Handling and Exception Handling Assessment
Security Considerations

Regression Testing:
Regression tests were run to validate that the changes did not affect any functionality of the overall system.
Test Execution:

The Tests were run manually by sending a JSON payload using insomnia. The recommended checking was running the system locally, But QA computer architecture was not supported by azure functions, for local running.
To cope with this, tests were run using the azure web deployment.

Results:
After successful running of manual and regression tests and careful validation, the issue was found to be good to close as the Acceptance criteria was fulfilled and all validations passed.
Deviations and Non-conformances:
No deviations or non-conformances were observed.
Summary of Findings:
Test Results: All tests conducted during the validation process passed successfully, indicating that the system functions as intended and meets the specified requirements. The tests covered various scenarios and edge cases, providing confidence in the system's reliability and correctness.
Unit Regression: The unit regression tests were executed, and no regressions or issues were identified. This indicates that the changes made during the development or modification of the system did not introduce any unintended side effects or break existing functionality.
Code Reviews: The code reviews conducted by both development and QA teams were completed, and no major issues or concerns were identified. The code adheres to coding standards and best practices, demonstrating good code quality, readability, and maintainability.

authors: RamilCDISC gerrycampion

repo: cdisc-org/cdisc-rules-engine


text:
chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-runtime-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2691

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-k8s-26-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 3984

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4832

Questions ?
Please refer to the Backport tool documentation


text:
How to get hot-reloads working with pnpm dev?

Hi,
I don't know if I missed something but pnpm dev at the project's root does not seem to pick up changes you make in the component files. ...and launching the pnpm build each time is kind of unproductive.
It's even described here: https://github.com/cdmoro/bootstrap-vue-3/blob/main/CONTRIBUTING.md#developing
Did I miss something or is this the normal workflow to build the whole thing each time before you visualize your change?

Open the one for bootstrap vue 3, and add modify the app. Vue for what you're trying to watch.
The wording is poor there, I'll make it better later today

Ah, thanks for updating the message, the previous version was quite puzzling. 👍 😅 Since editing a message does not send a notification, writing a new message might help making the participants aware of the update
This helps, I'll follow that route, working with ./packages/bootstrap-vue-3/src/app.vue is just fine too. ...now let's see if I can do something to fix this carousel, no guarantees.  😅

authors: VividLemon dagnelies


text:
Debounce added to BFormInput

Hey BV3 team :) I've been using a lot of form elements lately, and have noticed that debounce is a todo item but is yet to be implemented. I was wondering if there is a timeline for this feature, and if it would be possible to implement?

It usually comes down to "when I get around to it", as I am the only person majorly active, with perhaps one person at any given time pushing some small change every now and again. So, it is quite difficult to implement a large feature that requires a large amount of time to research, implement, and test, that only affects a small handful of components.

authors: VividLemon alexdohm


text:
Confused of loss=nan

I have some trouble happening with loss=nan. I am confused why it happened by using my own data.
I modify the "batch size" from 100 to 1, and then, modify the param of "Dummydata" shape dim from 100 to 1. But I don't know whether should I modify Reduction loss_weight. Is that the key factor influencing the mistake result loss=nan?

Sorry CJEQ, I think StackOverflow would be a better place for a question like this.  I want to keep the github issues for this project focused on potential changes to the codebase that's hosted here.

authors: CJEQ cdoersch


text:
3.0.2-arm64 Docker build broken?

I believe that the 3.0.2-arm64 Docker build is broken. I am running this on a Raspberry Pi4 using 64-bit Ubuntu.
When I try to to run the container, I get the following error:
$ docker run -it codercom/code-server:3.0.2-arm64
/usr/local/bin/fixuid: 2: /usr/local/bin/fixuid: Syntax error: word unexpected (expecting ")")

To check into this a bit further, I built a test Dockerfile based on codercom/code-server:3.0.2-arm64 that is just this:
FROM codercom/code-server:3.0.2-arm64
RUN sudo apt-get update; sudo apt-get install -y file
ENTRYPOINT file /usr/local/bin/fixuid

When I run this container, I get this message:
/usr/local/bin/fixuid: setuid ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, Go BuildID=2zxEqkKfJJwnveNVKDuQ/1ZwU6fMfvcIshc5qwXRB/xOrQ0MI5H54iHr712aDz/hF8w_99k9vhIr1ncU3Pq, with debug_info, not stripped

This leads me to think that the binary that got loaded into the arm64 Docker container is actually an x86-64 binary. Or am I doing something wrong?

If you rebuild a version of fixuid for arm64 (attached), and slip this into the build, then things work as expected. This is a little difficult because the upstream fixuid doesn’t automatically build arm64 packages. I manually built this version.
Dockerfile.txt
fixuid-0.4-arm64.gz

Thanks @mbreese! We'll definitely fix this.

I'll close https://github.com/cdr/code-server/issues/1481 in favour of this.

@code-asher is this fixed in latest?

Negative, we need to build fixuid in the CI for arm64 or perhaps better would be to submit a PR to fixuid so they can have arm64 builds.

Should be really easy: https://github.com/boxboat/fixuid/blob/0ec93d22e52bde5b7326e84cb62fd26a3d20cead/pack.sh

Should be really easy: https://github.com/boxboat/fixuid/blob/master/build.sh

A PR for fixuid might not be as easy as you'd think. They hard code amd64 all over their build scripts and expect their filenames to match. Building fixuid in CI would probably be the quickest option... but this is should be do-able.

https://github.com/boxboat/fixuid/pull/23

Let's give them a few days to respond.
If not you can go ahead and work on this @mbreese
The travis servers do not have Go but have docker.
You'd want to build fixuid in a docker container in https://github.com/cdr/code-server/blob/8608ae2f08ef1d4cc8ab2bc1d90633b018a4f41b/ci/release-image/push.sh#L16 and inject it into the image and adjust the image to use it instead of the fixuid binary it fetches from the releases.

I revamped the fixuid CI & release process in https://github.com/boxboat/fixuid/pull/25, if you need any more arch released it should be real easy going forward!

Awesome thanks @caleblloyd

Fixed in latest docker image.
You don't need the extra -arm64 anymore, the latest image is multi arch!

authors: caleblloyd code-asher kylecarbs mbreese nhooyr

repo: cdr/code-server


text:
Create a new terraform module for ECS

Create a new terraform ECS module.

The new ECS module is now live.

authors: patheard sylviamclaughlin

repo: cds-snc/terraform-modules


text:
Added a modal that will show up in the noscript tag with a hard link …

…to the all-benefits page
Solves #90

Closes #90

repo: cds-snc/vac-poc


text:
UI needs work

Hey,
Love your work. I'm using BB to track my 3week old sons <dad joke>poo-gress</dad joke>. We were very into it during the first week but as we get less and less sleep we're finding the UI is a bit too fiddly (particularly the date/time entry).
I'm a frontender these days (was a Django man myself) and was thinking of redoing the forms to make them easier for tired parents who forget when/what the timer is on/for... you know what i mean.
I see you have a good API setup (have you looked into GraphQL yet?) so i might try and write a frontend app using that. Do some interactive D3.js charts.  Maybe even some DTW clustering (as feedings are a bit staccato for us).
Anyway, do you think its worth having the front & back in the same repo or should they be separate projects? I'm deploying to Heroku and  not sure how to combine a Django + Create React App (at work we keep them separate but that's a big project and parents would want the simplest deploy i guess?).
word
alex
p.s. these are big words as i might get an hour or two a day in while he's sleeping (if i'm not too sleep deprived myself :)
p.p.s If you have another plan for the frontend? Otherwise i can work independently for now and just talk to the API.

The date/time entry is definitely fiddly when you need to make manual changes. What other issues have you run in to?
Ultimately I would prefer to sort out and make improvements to the existing UI without a big rebuild at this point. But if you want to go big, I think it would make sense to do this on a fork. My intention is to create a 1.0 release with a simple frontend and make (or merge!) improvements further down the road. In our three months of usage so far we have largely found the UI to be good but certainly not perfect.
A simple deploy is definitely a big focus here. I already think it’s a bit complicated (:
Good luck with the little ones! It’s damn stressful with just one (:

What, having more makes it less stressful...?

😭😭
👶👶
💩💩
💤💤
😭😭
👶👶
💩💩
💤💤
😭😭
👶👶
💩💩
💤💤
🕐 🕜 🕙 🕥 🕚 🕦 🕛 🕧 🕑 🕝 🕒 🕞 🕓 🕟 🕔 🕠 🕕 🕡 🕖 🕢 🕗 🕣 🕘 🕤

:D
I feel ya!
We have stopped tracking all together as the interface is too hard for my partner and i'm not awake all of the time. She tends to input stuff after it happens as shes too frantic while 💩  is going down and the time inputs are too hard to use on a phone (the popup calendar doesn't disappear after you choose a day, you have to click to calendar button again). Also the mother-in-law is here and i havne't even tried to explain it to her.
I'm thinking of making all the combinations of inputs (i.e. left breast, right breast, formula, bottle breast milk, sleep, pooh, wee) into a list of buttons which start/stop the time. If you click one while another is going it ends the previous timer and starts a new one with the new activity. The concept of a timer should be transparent to the user (i.e. they don't need to know about it). This would also help us with the sporadic nature of the: feed -> suck finger -> wind -> feed cycle we go though to get him to feed.
Also, the reporting isn't motivating enough to keep up with the tracking (which adds extra pain). I guess the point is to see if the sleeping patterns ( for me).
Having said that the dashboard is quite useful! To be able to check when the last diaper change was is handy or the last feeding.

I would certainly love to see your ideas for improving the time entry. My wife and I mostly input things as they happen so we rarely ever end up modifying a time, it's very interesting to hear that others use it differently and that is a pain point.
Combination buttons for timers seem like a good idea. Do you have a vision for how it might be organized? I'm just worried about jamming too much in to the timer detail interface.
Re: timers being transparent, do you not use multiple timers at once with more than one child? I set them up this way so that multiple children could be tracked with multiple timers going at once. How would this work if timers were transparent? I think it would require more data (e.g. the child and activity) at the start, right?
And yes, I agree that the reporting is pretty bleh. Actually, my biggest motivation for building this app was to create the "sleep pattern" graph, which is kind of neat to see now (3.5 months in) but really not super valuable. I agree that the dashboard is the most useful part of the app, and it's something I want to improve on for customization in the long (e.g. allowing users to enable/disable and re-order cards).

Although I see this is an old thread, and I'm not sure how much work is still being put into this, I'd like to re-ignite/continue the discussion to see if there are any improvements I might be able to help with in the few months I have left with decent sleep. I'm trying to practice/get my wife to practice using the app so it is familiar when we do need it.
Here are some of my thoughts:
*Possibility of changing how inputs are done for 'duration' inputs (like length of nap, length of playtime, etc) to have the stop time be current time (like currently coded) then the ability to enter either start time OR duration if you already know how long (my wife loves to set timers for everything so she'll already know if they played for 30 minutes, etc). This could eliminate some of the messing with the finicky calendar.
*Possibility of having start and stop buttons (similar to timer functions) to start and stop a feeding.... Although thinking about this more, the timer function seems to accomplish this.
Also my API game is a little weak, and I'd like to know if there is a way to accomplish my second thought via the API... I plan to create a raspberry pi device with buttons so we can just push a button and have it log the info into the app so we don't have to fumble with/find our phones, just push the button and be done. I'm planning to have a button for diaper changes, one to start feeding and one to stop feeding, but I'm not sure the best way to accomplish this with the API so any guidance would be appreciated there.
Thank you for making such an awesome app!

FYI I moved your API questions in to #76 and I'll give some thoughts on them there.
Not a great deal has changed since this thread, and I'm always happy to accept PRs or detailed thoughts on UI changes.
The datetime selection has indeed been a pain point for some so if you can come up with a good way to handle multiple types of input there, I'm all for it. I have never taken the time to really look in to options for that. All the form interfaces are pretty "dumb" right now so changes can be a little tricky.
The timer should essentially do what you want. You can create any type of timed entry directly from a timer instance. Generally, our process with the little one was to start a timer for whatever we were doing and then initiate the new entry (diaper change, sleep, or breast feeding) from the timer itself. This will auto-fill both the start and end times (and that's part of why I have never put deep effort in to changing the datetime select interface).

authors: TheEagle13 awhillas cdubz

repo: cdubz/babybuddy