Float types

This PR adds support for float32 through settings.py
Surprisingly, most of GPflow still works with float32. I do anticipate that most users are going to want float64 though, because of the numerical stability.
The only two tests to fail are:

test_method_equivalence where optimization fails because the Cholesky decomposition fails
test_methods where a lengthscale-gradient does not seem to be the same across two similar models (presumably this is a numerical thing)

If someone want to look a these, they'd be welcome, but the immediate question is how much speed this gains us on the GPU.
Before this could be merged, we'd need a better method of controlling float64/32 through a config file -- I think there are lots of things that would be good in a config file, which I'll look at in a separate PR.

@jameshensman Thanks for the PR. I think the Cholesky failure could be tricky to fix. Are you looking into the GPU speed up?

I don't have time to look today, would love to see the timeline-traces using float32 on GPU.
Yeah, chasing down the source of the numerical instability is going to be really hard. We might have to force 64bit precision during matrix decomposition or something.
There's a possibility though that the choice of l-bfgs-b as a default optimizer is compounding the issue. Perhaps a less 'aggressive' optimizer could cope with some numerical instabilities.

@jameshensman your latest commit fixed my mnist bug without needing to merge your other branch. As it didn't come out in the unit tests perhaps we should add a regression test (i.e a test that checks the bug is fixed) for this?

@jameshensman running mnist experiments on this branch:
https://github.com/GPflow/GPflow/tree/mnist_datatypes
to see how we do with reduced numerical precision. I had to remove the "nasty merge" as it was causing a lot of test failures. I'll let you know how it goes.

Current coverage is 99.26% (diff: 95.87%)

Merging #185 into master will decrease coverage by 0.10%

@@             master       #185   diff @@
==========================================
  Files            23         23
  Lines          1596       1630    +34
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1586       1618    +32
- Misses           10         12     +2
  Partials          0          0

Powered by Codecov. Last update b75ac86...166cd36

@jameshensman looks like we're close on this one, no?

yep. We need to make a decision on what to test: do we want the tests to pass in float32?

@jameshensman I have to confess a bias on that one. mnist is seriously fast with the hybrid branch I linked and ends up with the same error of 97.94% . Great work :)
Thoughts:
Maybe if we don't pass tests we give a warning?
How far off passing on float32 do you think we are?

(errors=4, failures=2), 189 tests. Some of those are easily fixed, others
are harder.
On Tue, 13 Sep 2016 at 20:35 Alexander G. de G. Matthews <
<EMAIL_ADDRESS>wrote:

@jameshensman https://github.com/jameshensman I have to confess a bias
on that one. mnist is seriously fast with the hybrid branch I linked and
ends up with the same error of 97.94% . Great work :)
Thoughts:
Maybe if we don't pass tests we give a warning?
How far off passing on float32 do you think we are?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GPflow/GPflow/pull/185#issuecomment-246797918, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJbD9rSv8OwpRKsZK3Ve3MS1vLAgCjhks5qpvr_gaJpZM4JxbXr
.

now (errors=1, failures=2)
One of those failures, in test_data_holder, is a bug and can be fixed easily. Will look at it tomorrow.
The other failure is due to numerical instability: a lengthscale gradient does not match across two equivalent models (hardly surprising, I think we compute and differentiate K^{-1} * K * K^{-1} * y, which I imagine is silly in float32).
The error is in test_method_equivalence, where we optimize a series of models and make sure they do the same thing. numerical badness leads to a linear algebra error (LLT not valid). I've played with the code, and this can be fixed by adding a White kernel to each model: each model optimizes the white noise variance to zero, but the extra-posdefness helps during optimization. FITC, though,  needs special treatment, suggest a fixed white kernel.
For the latter two, I'm not sure if I want to fix them. I'd rather just mark them as 'known to fail for float32'. Agree?

In addition, we should add one extra tests to cover the code in DataHolder.py. This will let the codecov requirement pass too.

Hi James, just out of curiosity, where is Kinv K Kinv y computed? Is this an artefact of the comparison of models, or something that is actually done intentionally?

@jameshensman I guess we wouldn't test float32 on continuous integration anyway because we would then back to the ballooning test times?
Once we have that data holder test so that CI passes, I'm personally inclined towards merging and adding a ticket for any outstanding issues. We would then treat float64 as the supported data type and any change as a user decision that they need to check.
I'd also be interested in the answer to @markvdw 's question about the inverses.

Okay, I'll fix up that last test today.
The numerical instability is in SGPMC when the data points and the inducing points are the same. I guess it's actually
Kfu Kuu^{-1} v.
Of course, tensorflow doesn't know Kfu==Kuu, we just happen to feed a copy of the same data for X and Z. It copes pretty well, only one of the lengthscale gradients is off, and of course it's fine in float64.

@jameshensman What may make the problem worse, is that jitter is added to Kuu, but not Kfu, which should be equal to Kuu. It would be interesting to see if removing jitter (or adding jitter to Kfu if X happens to equal Z) solves this problem.


Battery

I see that you don´t use acpibattery.kext. How do you patch battery?

VirtualSMC/SMCBatteryManager is a new method to show battery percentage.

I have this kext but not show my battery


IOSXE/show redundancy switchover history

Description
Added parser for show redundancy switchover history
Motivation and Context
Turns raw output of show show redundancy switchover history into structured data
Impact (If any)
None
Screenshots:

Checklist:

[X] I have updated the changelog.
[X] I have updated the documentation (If applicable).
[X] I have added tests to cover my changes (If applicable).
[X] All new and existing tests passed.
[X] All new code passed compilation.

ship it.

PR submitted. IOSXE/show redundancy switchover history #290


Feature request - services.zfs.autoSnapshot.enable: warn if no datasets are set up

Describe the bug
While services.zfs.autoSnapshot.enable is set to true, there is no feedback if the configuration does not have any effect - such as the case if the user did not set com.sun:auto-snapshot=true on any of the datasets.
Steps To Reproduce
Steps to reproduce the behavior:

Create a ZFS based install
Forget to set com.sun:auto-snapshot=true on any of the datasets
Add services.zfs.autoSnapshot.enable=true; to your configuration.nix

Expected behavior
nixos-rebuild switch should complain about a configuration that does not make sense.  Probably not be an error, perhaps warn the user they need to take additional action to enable the feature.
Additional context
Documentation and notes about using this feature:

https://search.nixos.org/options?channel=22.05&show=services.zfs.autoSnapshot.enable&from=0&size=50&sort=relevance&type=packages&query=autosnapshot.enable
https://nixos.wiki/wiki/ZFS#How_to_use_the_auto-snapshotting_service

Notify maintainers

Checked git blame, at-ing the two authors that touched zfs.nix recently:

@ElvishJerricco
@grahamc

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
winston@stargate ~ $ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.43, NixOS, 22.05 (Quokka), 22.05.379.08950a6e29c`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.8.1`
 - channels(root): `"nixos-22.05.379.08950a6e29c"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I just ran into this issue today. This would have been helpful.

While we're at it, can we also get the documentation to point to how/where to add com.sun:auto-snapshot? It's certainly not obvious.


Message Key Lost in Retry and DLQ

I noticed that after using ReconsumeLaterAsync, the messages that originally had a value for the key have an empty key when consumed again.
I found that the issue is mainly in the function getOptionalKey in the file src\Pulsar.Client\Internal\DeadLetters.fs. This function only sets the PartitionKey when message.Key is empty.
    let getOptionalKey (message: Message<'T>) =
            if String.IsNullOrEmpty(%message.Key) then
                Some { PartitionKey = message.Key; IsBase64Encoded =  message.HasBase64EncodedKey  }
            else
                None

Thanks for noticing! I've made a fix in 3.5.2, please verify


C# client generator does not generate enum converter attribute for System.Text.Json serializer

One of data schemas in OpenApi spec has property containing array of DayOfWeek enumerations:
    ShiftDto:
      type: object
      properties:
        daysOfWeekActive:
          type: array
          items:
            $ref: '#/components/schemas/DayOfWeek'
    DayOfWeek:
      enum:
        - Sunday
        - Monday
        - Tuesday
        - Wednesday
        - Thursday
        - Friday
        - Saturday
      type: string

I want to use the System.DayOfWeek enum in the generated C# client so I tweaked the generator options:
{
  ...,
  "codeGenerators": {
    "openApiToCSharpClient": {
      "additionalNamespaceUsages": [
        "DayOfWeek = System.DayOfWeek"
      ],
      "excludedTypeNames": [
        "DayOfWeek"
      ],
      ...
    }
  }
}

Actual behaviour:
The generated client code is:
    public partial class ShiftDto
    {
        [System.Text.Json.Serialization.JsonPropertyName("daysOfWeekActive")]
        // TODO(system.text.json): Add string enum item converter
        public System.Collections.Generic.ICollection<DayOfWeek> DaysOfWeekActive { get; set; }
    }

and the deserialisation fails unless the JsonStringEnumConverter is explicitly added to serialiser options.
Expected behaviour:
The object can be deserialised without configuring the serialiser.

@Dietatko, Did you find a solution to your problem? We have a similar issue. THnak you for your help!!

I have the same issue. And since the generated clients all use their own serializer settings (instead of a shared one) adding a customer string to enum converter is a pain.
Multiple clients via: (OperationNameGenerator = new MultipleClientsFromFirstTagAndOperationNameGenerator())


[LV] Use noCap option for Longview Detail breadcrumb

Description
Previously the LV client title was capitalized in the title:

This PR adds the noCap option as we have with other entity detail pages.

This looks good. I was able to see the lv client name with out caps and when renaming the lv client name to have a cap in the beginning of the name it showed the the correct name.
no cap - debian-longview-231256

to cap Debian-longview-231256


Why all fragment in the same adapter effected from process i makes in one of them in my onCreatView?

I'm wondering why all fragment effected if i have some thing to do in one of them in onCreatView method, How i can avoid this from happening?

Hi @ibrahimAlii,
What do you mean exactly by that? Could you share some code and provide steps to reproduce?

@zawadz88  suppose i have 3 fragment F1, F2, F3. and i have a timer or thread i start it in my onCreatView method in F3, Then the time or counter whatever should start after i open F3, but that dosen't happen, It's start after i start F1, is that normal? should i add break or something in my adapter?

Hi @ibrahimAlii,
You shouldn't do that in onCreateView as the underlying ViewPager creates the Fragments next to the currently selected Fragment as well. If you want to do something when the Fragment gets selected I'd do that in Step#onSelected() in that Fragment.


Hostfactorey help alignment

Desired Outcome
Align hostfactory help according to https://ca-il-confluence.il.cyber-ark.com/display/rndp/New+CLI+commands+help+text+review#/expand-hostfactory
Connected Issue/Story
Resolves ONYX-13132
CyberArk internal issue link: insert issue ID
Definition of Done
At least 1 todo must be completed in the sections below for the PR to be
merged.
Changelog

[ ] The CHANGELOG has been updated, or
[ ] This PR does not include user-facing changes and doesn't require a
CHANGELOG update

Test coverage

[ ] This PR includes new unit and integration tests to go with the code
changes, or
[v ] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR
[ ] A follow-up issue to update official docs has been filed here: insert issue ID
[v ] This PR does not require updating any documentation

Behavior

[ ] This PR changes product behavior and has been reviewed by a PO, or
[ ] These changes are part of a larger initiative that will be reviewed later, or
[v ] No behavior was changed with this PR

Security

[ ] Security architect has reviewed the changes in this PR,
[ ] These changes are part of a larger initiative with a separate security review, or
[v ] There are no security aspects to these changes

@hzur  have you also arranged the options and subcommands sections? dont think I saw it in here, just verifying  :)


fixed error in tokenization code for other datasets in readme

In this code sample in the README which helps users tokenize their own data, there is a variable used new, which is not defined in the scope of the function. I believe the intended variable to be used is word_pieces.

Thanks for pointing this typo.


Remove duplicate default poll interval

#51  👈
main

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

Join @vegarsti and the rest of your teammates on  Graphite


Split out a class that takes care of running ZooKeeper server

Need this to simplify the way this will be done when we start supporting
dynamic reconfiguration of ZooKeeper cluster

PR build has not started yet, I give up waiting, merging.


feature-request: overwrite bib file in tool mode

My bib file is under version control (with git, here on github), so I would prefer to overwrite the existing bib file instead of creating a new one when using biber in tool mode as described here
http://tex.stackexchange.com/q/186733/8569
or in section 3.12 of the documentation.
Would that be possible?

Yes, this will be possible for tool mode with bibtex output in 2.1. You can do:
biber --tool --output_file=foo.bib foo.bib

Great, thanks.
With biber 1.9.1 (??) on Kubuntu 14.10 I was getting an empty file.
Looking forward to biber 2.1 then.

Just installed Tex Live 2015 with biber 2.1 and I believe this fix changed the default behavior:
If no output_file is specified, the default was infile_bibertool.bib but now it is _bibertool.bib.

Hmm, that is strange - what about the 2.2 dev version on SF?

Sorry for answering late. I do not have Perl installed and I have never tested one of the dev versions before. Are there instructions anywhere? I have Xubuntu, Windows 7 64bit and OSX running here.

You don't perl installed - these are drop-in binary replacements.

This is strange: I just downloaded the 2.2 beta and it worked as expected. I then switched back to 2.1 and it also worked as expected. I really tested it before, I guess 10 times!
Looks like this can be closed, sorry for bothering.


buttons color and alignment fixes

FYI Updated the base branch to v3, as the new docs are now live.


Pie chart feature

addresses #13

@taras can you review this PR please? The pie chart is fully functional now

I get this error when I click around the pie chart.

I did some googling. It looks like you need a custom tween for this. http://stackoverflow.com/a/21287079/172894

Looks great!

closes #3


fix - login security issue

Check the post #1174

@thareekanvar Please fix the eslint error

@boojack i think i fixed the TS Lint issue


Viva Dashboard Web Part no longer supports section background color

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Describe the bug / error
The Viva dashboard web part is no longer supporting theme variants section background colors after a recent update.

Steps to reproduce

Existing deployed dashboard, worked previously, now white behind cards.

Expected behavior
Viva Dashboard web part supports theme variants and has a transparent background when displaying on section background color.

I can reproduce this issue.

@Annie-Johnson  and @a1mery - We are working on getting this fixed. As this is however not a dev issue, we will close this from here. In general these kind of issues should be reported from the m365 admin UX as it's in the out of the box features. We cannot unfortunately route the input from here to the right channel, so it's better to report the issue from admin UX.


AttributeError: 'NBMasterBar' object has no attribute 'first_bar'

Trying out the following example on Colab:
from fastprogress.fastprogress import master_bar, progress_bar
from time import sleep
mb = master_bar(range(10))
for i in mb:
    for j in progress_bar(range(100), parent=mb):
        sleep(0.01)
        mb.child.comment = f'second bar stat'
    mb.first_bar.comment = f'first bar stat'
    mb.write(f'Finished loop {i}.')

Throws: AttributeError: 'NBMasterBar' object has no attribute 'first_bar'.

you can install  fastprogress==0.1.20
pip install fastprogress==0.1.20

I would love to use the current version. I'm sure @sgugger is busy with all the other awesome libraries he supports, but I'm wondering if the example in the README.md could be updated. I went through the source code for about 20 minutes and couldn't really put it all together.

The doc wasn't synced with API changes, apparently first_bar got renamed to main_bar at some point - should be fixed now.


New tcl apis

all tcl apis for CircuitOps except "is_port", "maxcap", "net_steiner_length", "worst_input_cap", "libcell_leakage", "fo4_delay", and "libcell_delay_fixed_load".

Once you clean up the commented code. Feel free to go ahead and merge your changes.


Backend infrastructure created

DiceRoller: Rolls dice for you
ClassType: Defines a character's class (Wizard, barb, etc.)
Dice: Set of ENUMS which define all the different types of dice rolled in D&D (Used by DiceRoller)
Item: Defines an item from a characters inventory
Modifier: Consists of a characters base ability score and the corresponding modifier
CharacterSheet: The overarching object which brings together all of the previous ones. Stores all information a player would have on their character sheet.

@ngutn24 You've been added to the reviewer list to make sure I didn't mess up any D&D mechanics with my implementation.


Extend "SetIdentifierArgumentFn" interface to support additional parameters like "metadata.name"

What problem are you facing?

Currently, "SetIdentifierArgumentFn" functions can only take "spec.forProvider" and "external-name" parameters. I'd like to pass "metadata.name" field for configuring resources like AWS MQ broker. In this resource, "broker-name" is required and the external name is generated by the cloud provider.
How could Terrajet help solve your problem?

Providing an additional mechanism to configure jet-based resources.

In this resource, "broker-name" is required and the external name is generated by the cloud provider.

How would metadata.name help in this case?

Instead of having a spec field called brokerName, I'd like to use metadata.name for XRM compliance.

When a resource has a name but also queried by an assigned ID, I usually treat the name just like a tag or label since it's not used to identify the resource. XRM suggests that the external name, i.e. the identifier in the external system, should be defaulted to metadata.name so I think it should be fine to keep it in the schema as required. What do you think?

@muvaf I hit the same in https://github.com/crossplane-contrib/provider-jet-datadog/blob/main/examples/monitor/monitor.yaml#L8, I want to use metadata.name without semantical duplication in spec . At the same time I cannot use NameAsIdentifier as the resource is always identified by some integer number https://registry.terraform.io/providers/DataDog/datadog/latest/docs/resources/monitor#import


Shell history not working in cmd.exe or Python REPL

Hi,
With Rez 2.103.4 (Python 3.7) on Windows 10, we are finding that using cmd.exe with Rez doesn't let you step through your command history with the up-arrow key. This issue was reported a couple of years ago but seemed to have been fixed in 2.35.0
https://github.com/nerdvegas/rez/issues/616
$ rez env
> $ echo Hello World!
> $ # hit up-arrow
> $ # no response.. :(

It works as expected in Powershell until you launch a Python REPL process, which it then no longer works inside of.
Any suggestions/help would be very much appreciated! :) Apologies I don't really have the knowledge to look into this myself.
Thanks,
Nikhil

I'm going to regard this as a feature request given current lack of support for managing shell history. Please see https://github.com/nerdvegas/rez/issues/1240

While i agree with the notion that this should be managed actively there is a specific issue with cmd that breaks this. It works with Terminal and Powershell as expected. I THINK Marcus did a fix ages ago and it was choosing different flags when calling cmd. But that might of course have other side effects. I can take a look if i find the time.

Yeah I looked back at that old PR, and it seems like fixing cmd history was
(for whatever reason) a side-effect of removing that interstitial cmd proc.
Not sure what may have changed in the meantime.
I'll reopen this issue but for anyone working on it please refer to #1240
in the fixing branch name, cheers!
Thx
A
On Wed, Mar 2, 2022 at 10:10 AM Thorsten Kaufmann @.***>
wrote:

While i agree with the notion that this should be managed actively there
is a specific issue with cmd that breaks this. It works with Terminal and
Powershell as expected. I THINK Marcus did a fix ages ago and it was
choosing different flags when calling cmd. But that might of course have
other side effects. I can take a look if i find the time.
—
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/1234#issuecomment-1055952960,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMOUSUFTSZXRBWULXYUGLDU52PVNANCNFSM5PFETR2A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Please note that this should be fixed with general solution in mind - https://github.com/nerdvegas/rez/issues/1240

As your link indicates i would argue this is more of a console host and shell issue than necessarily a rez issue. I always forget this was an issue because i use Windows Terminal as by console host and a mix of cmd and powershell and history is just fine even in nested shells.

I don't disagree, it's just not particularly obvious at first, where launching commands from cmd or powershell has a properly working history, but as soon as rez is in the mix it seemingly suddenly stops working. That made me believe that Rez was at fault, and if I'm not mistaken, that's also what others might be believing based on this issue and #616 #1240 and #1320
It could also explain that removing a layer of subprocess via #627 has seemingly made it work a bit better, as that reduced the buffer stack by one, but that going any further down would still break.
If somebody else can confirm that this is indeed the issue that was mentioned, even though it's not a Rez issue, it might be worth mentioning somewhere in the docs how to workaround?

Absolutely should be mentioned in the docs. Shell plugin specific documentation and pitfalls would generally be a good addition to the docs as even just the differences between cmd and pwsh/powershell can be confusing.

Would you mind adding it to the documentation improvement discussion thread?

Hello,
I came across the same issue with Rez 2.111.3 on Windows 10 and cmd.exe.
Setting Number of Buffers to 12 in the cmd properties helps with commands history in a rez context and also in Python REPL.
Attaching screenshot of cmd properties, so that it's easier to find fix in this thread.

Interestingly commands history worked well in IPython even with the default Number of Buffers setting of 4.


⚠ GitLab Server has degraded performance

In 525abd7, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 9097 ms

Resolved: GitLab Server performance has improved in 5fc53c9.


ci(test): add deterministic parallel e2e test

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
As title.
This PR also upgrades madsim. The logging facility was migrated to tracing which provides better contextual information.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

The logging facility was migrated to tracing which provides better contextual information.

Cool. How about also removing all log in our system?


Update cluster-intro.html

Added comma(,) to avoid ambiguity of a sentence.

CLA Done.

/check-cla

Really Done!

/assign @claudiajkang

/lgtm
/approve

@dbgsprw Thank you!!


Running 'ord server' seems to leave the index in bad state, delays next ord launch

Running 'ord server' works as expected. Ctrl-C to exit also seems to behave as expected. However, each time after running 'ord server' and then exiting, the NEXT time I run ord I get a long delay (up to 20-30 min for a with-sats index) before it picks up with indexing and does whatever new command I've given it.
macOS 13.2.1 / M1 Max / 32 GB RAM / SSD
ord 0.5.1

I see exactly the same thing. It takes about 25 minutes before the "listening on" text shows up. If I hit control-C at that point and rerun "ord server" it takes another 25 minutes. While waiting it is constantly reading about 22 MB/s from the drive that holds the index file. That means it's reading around 33 GB of the 116 GB index file.

Same here. With the logs on TRACE, there is literally nothing logged during that period either :/

Exact same issue I am facing..

Fixed by #2275


Chore: updated dependencies

Aim's to resolve #219 from meta #205.

@0xSwapFeeder don't you think the issue was talking about packages like "@massalabs/as-types": "^0.0.3**-dev**", ?

@0xSwapFeeder don't you think the issue was talking about packages like "@massalabs/as-types": "^0.0.3**-dev**", ?
Not sure, could be it, but the issue name talks about dependencies, not package.json configuration for packages, or I didn't understood.

@gregLibert can you help us on this ?

Done ! @Ben-Rey


Build Docker image failed on Raspberry Pi

Expected Behavior
A Docker image should be created
Actual Behavior
Failed to create image
Steps to Reproduce
Running command to build image
$ docker build -t pokemongo-bot .
Sending build context to Docker daemon 5.463 MB
Step 1 : FROM python:2.7-onbuild
# Executing 3 build triggers...
Step 1 : COPY requirements.txt /usr/src/app/
 ---> Using cache
Step 1 : RUN pip install --no-cache-dir -r requirements.txt
 ---> Running in 1cd2b3867cce
rpc error: code = 2 desc = "oci runtime error: exec format error"

Other Information
OS: Arch Linux ARM

Same problem here on my RPi 3..

I got the same problem. Maybe the docker image you are using is built for x86/x64 architecture. And your cpu is based on ARM.


Providing reference for github issues

Providing reference for github issues

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b3b4b526391bf6427224782f3b9ee286ec0a24ad/
Edited pages:

v19.1/contribute-to-cockroachdb.md


RuntimeError: You can't move a model that has some modules offloaded to cpu or disk

Was working yesterday, saw was a new update for lcm_lora. I reinstalled everything including ComfyUI, Manager, AnimateDiff Evolved, Video Helper Suite, using 1.5 model, Loading the default example text2img workflow, AnimateDiff loader, after Ksampler, at VaeDecoder:
Error occurred when executing VAEDecode:
You can't move a model that has some modules offloaded to cpu or disk.
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\execution.py", line 153, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\execution.py", line 83, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\execution.py", line 76, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\nodes.py", line 267, in decode
return (vae.decode(samples["samples"]), )
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\sd.py", line 226, in decode
model_management.load_models_gpu([self.patcher], memory_required=memory_used)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\model_management.py", line 388, in load_models_gpu
free_memory(total_memory_required[device] * 1.3 + extra_mem, device, models_already_loaded)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\model_management.py", line 340, in free_memory
m.model_unload()
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\model_management.py", line 311, in model_unload
self.model.unpatch_model(self.model.offload_device)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved\animatediff\model_injection.py", line 49, in unpatch_model
self.eject_model(device_to=device_to)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved\animatediff\model_injection.py", line 62, in eject_model
self.motion_model.model.to(device_to)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\python_embeded\Lib\site-packages\accelerate\big_modeling.py", line 415, in wrapper
raise RuntimeError("You can't move a model that has some modules offloaded to cpu or disk.")

Thanks for the report, I now pushed a new update that should stop that error from being thrown - can you update AnimateDiff-Evolved, and see if the issue is fixed?

Just updated and:
Error occurred when executing VAEDecode:
You can't move a model that has some modules offloaded to cpu or disk.
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\execution.py", line 153, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\execution.py", line 83, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\execution.py", line 76, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\nodes.py", line 267, in decode
return (vae.decode(samples["samples"]), )
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\sd.py", line 226, in decode
model_management.load_models_gpu([self.patcher], memory_required=memory_used)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\model_management.py", line 388, in load_models_gpu
free_memory(total_memory_required[device] * 1.3 + extra_mem, device, models_already_loaded)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\model_management.py", line 340, in free_memory
m.model_unload()
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\comfy\model_management.py", line 312, in model_unload
self.model.model_patches_to(self.model.offload_device)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved\animatediff\model_injection.py", line 38, in model_patches_to
self.motion_model.model.to(device)
File "C:\stb\new_ComfyUI_windows_portable_nvidia_cu121_or_cpu\ComfyUI_windows_portable\python_embeded\Lib\site-packages\accelerate\big_modeling.py", line 415, in wrapper
raise RuntimeError("You can't move a model that has some modules offloaded to cpu or disk.")
Above was tested with default Txt2Img workflow as well as with LCM_lora and discrete sampler plugged in.

Alrighty, I pushed out a new update that should properly catch that error in the places where it can happen. Let me know if that fixes it, or if there is a new place it creeps up now!

Bingo! Seems resolved. You work fast!


Add tracing support to the VM

Feature request
Allow setting up a callback to the VM, which is called on every instruction, after the instruction is executed
Feature description
This would allow lots of features:
Sample profiling
The callback would collect a sample every ith instruction, extract the frame from the source mapping, and generate a flame graph.
Tracing profiling
Get the current line from source mapping, increment a counter, and report the instruction count on a per line base
Coverage reports
Use the tracing feature to collect information of which lines of code are being hit during test execution, aggregate the data and generate a report in the CI to get coverage testing
Notes
It is probably best to have this feature behind a feature flag, since executing a callback on every instruction has a non trivial overhead cost.

The proposal above is inspired by the tracing api in the CPython interpreter. I have used this API to implement the features I mentioned above, once the tracing API is in-place it is very trivial to implement tooling on top.


Feature request for VS 2017: Folders in F# projects

Dear developers!
Please add IDE support for folders in F# projects by:

adding folders to projects,
adding subfolders to existing folders,
renaming folders,
moving files to folders,
moving folders up/down.

Expected behavior
Please implement new commands in Solution Explorer context menu:
Add Below -> New Folder,
Add Below -> Existing Folder,
Add Above -> New Folder,
Add Above -> Existing Folder.
The Remove, Delete, Move Up, Move Down commands should apply to folders as well as to files.
The Copy, Paste commands should be able to copy and paste the selected files (and folders, subfolders) to another folder of the same or different project.
The Move to Folder command is needed in  Solution Explorer context menu and should be able to move  the selected files (and folders, subfolders) to another folder.
Important note
Folder organization feature is not intended to change the already existing, linear order of compilation for source files in F# projects. The F# files mentioned first in the .fsproj file should be compiled first, as usual.
Known workarounds
I need to edit the .fsproj file manually (in the 21th century!, due to lack of Visual Studio support) to obtain the F# project with the folder organization I need.
For example,
I want to obtain the project with 3 folders, so I need to rewrite:
<ItemGroup>
<Compile Include="type1.fs" />
<Compile Include="type2.fs" />
<Compile Include="type3.fs" />
<Compile Include="type4.fs" />
<Compile Include="type5.fs" />
<Compile Include="type6.fs" />
<Compile Include="type7.fs" />
</ItemGroup>

in the .fsproj file as follows:
<ItemGroup>
<Compile Include="type1.fs" />
<Compile Include="Folder1\type2.fs" />
<Compile Include="Folder1\type3.fs" />
<Compile Include="Folder2\type4.fs" />
<Compile Include="Folder2\type5.fs" />
<Compile Include="Folder3\type6.fs" />
<Compile Include="Folder3\type7.fs" />
</ItemGroup>

The order of compilation remains unchanged: type1.fs, type2.fs, ... type7.fs.
Related information
This feature will help refactoring mid-size and large F# solutions (containing several dozens or hundreds of projects) by introducing meaningful folder organization in F# projects.

@financial-engineer
Please let us make the move to CPS.  Any work on the current project system may well end up not shipping.  The work to move to CPS is just about to start.
Kevin

@kevinransom, if the work is in progress can we have a ticket (with a checklist of work that's been done) and close off the other related project system tickets?
Exciting :)

https://github.com/Microsoft/visualfsharp/pull/2692
https://github.com/Microsoft/visualfsharp/pull/2689
@financial-engineer

@KevinRansom Closed by #2692


Error when switching from one kontra canvas to another

In Trivia Murder Party 2, there's two games that use Kontra. One is a Lotto Scratch Ticket, and the other is a Rotary Phone. When I load the Lotto Scratch Ticket (9 sprites with touch events), and then unload that and load the Rotary Phone (1 sprite with touch events and an animation, a couple other sprites) I get this error:
The index is not in the allowed range. -
drawImage@[native code]
draw@https://jackbox.tv/2.988daa143fbae6dda4f4.js:1:11890
render@https://jackbox.tv/2.988daa143fbae6dda4f4.js:1:11209
forEach@[native code]
render@https://jackbox.tv/18.c4586627de4aaa17eb0e.js:1:13279
y@https://jackbox.tv/2.988daa143fbae6dda4f4.js:1:4617

These should have their own view, their own sprites array, their own gameLoops, so everything should not be in conflict but this error leads me to believe that's not the case. Here's my MarionetteJS onBeforeDestroy function:

onBeforeDestroy() {
        window.removeEventListener('resize', this.onResizeWithContext)
        const self = this
        for (let i = 0; i < self.sprites.length; i++) {
            self.sprites[i].ttl = 0 // reset
        }
        self.gameLoop.update(1 / 60)
        self.gameLoop.stop()
    },

Any hints on what might be causing this?

Oh, this error only happens on iOS devices (iPad and iPhone), but both Safari and Chrome.

I have not heard of this error before, but looking at stackoverflow seems to suggest it happens when the x/y position is outside the canvas range?
I would almost need a working test case to guess what is going on. However, I don't know if kontra is setup to handle multiple instances of itself on the same page.

You have a private form of communcation we could move this to? I can set you up with the test jackbox.tv credentials.

My email steven at sklambert com

Looks like the underlying issue is the image of the sprite isn't loaded into the DOM yet, so the width/height of the image is 0. Safari doesn't like that. Would it be worth adding safeguards to the library to not render when the image width or height are 0?

I guess it depends. Skipping the render cycle entirely may be confusing if you expect your sprite to render but it's not showing up. In a situation like this it would be more helpful if we told the user the problem rather than throwing that unhelpful error from Safari.

I think that in another use case where you want the sprite to be 0px high for a frame. I would imagine just skipping the drawImage line would be fine.

oh, y'know what? I had fixed this in a previous version but didn't make a PR. Now that we've changed the way images are drawn we can remove the 0, 0, this.image.width, this.image.height, line https://github.com/straker/kontra/blob/master/src/sprite.js#L633
This fixes the issue.


Document HybridSystem forecast data

Basically, when creating a HybridSystem from components already that has a time_series, the process requires to:

first get the timeseries from the subcomponents and copy those
remove the subcomponents from the system
create the hybrid system with the subcomponents
attach the forecast to each subcomponent

(I think?)

@rodrigomha You should be able to call add_component!(sys, hybrid) and the the code will do everything required because of the method below, which gets called during the add. These behaviors should definitely be documented.
function handle_component_addition!(
    sys::System,
    subsystem::StaticInjectionSubsystem;
    kwargs...,
)
    for subcomponent in get_subcomponents(subsystem)
        if is_attached(subcomponent, sys)
            IS.mask_component!(sys.data, subcomponent)
            copy_subcomponent_time_series!(subsystem, subcomponent)
        else
            IS.add_masked_component!(sys.data, subcomponent)
        end
    end
end

@rodrigomha You should be able to call add_component!(sys, hybrid) and the the code will do everything required because of the method below, which gets called during the add. These behaviors should definitely be documented.
function handle_component_addition!(
    sys::System,
    subsystem::StaticInjectionSubsystem;
    kwargs...,
)
    for subcomponent in get_subcomponents(subsystem)
        if is_attached(subcomponent, sys)
            IS.mask_component!(sys.data, subcomponent)
            copy_subcomponent_time_series!(subsystem, subcomponent)
        else
            IS.add_masked_component!(sys.data, subcomponent)
        end
    end
end

Thanks Dan. Yeah, I was not aware that adding the hybrid immediately remove the subcomponents for the system.


Govee sensor data showing in Homebridge log but not through Homekit

I'm new to Homebridge but not to home automation.  I added your Govee plugin to my Homebridge server and configured the plugin.  I have a temperature sensor and the sensor is reporting through your plugin Model H5053 and it pulls the data as I can see temperature reading in the Homebridge log.  But when I look on my Ipad there are not any new accessories added.  When I added a plugin for my garage doors there were several accessories automatically added.  Maybe the Govee sensor is not added as I noticed it is not supported.   I figure that I am close since the plugin is reading the data but can't figure out how to get it added on my ipad through the Home app.  Thanks and good work with the plugin.   Lee

I checked and the temperature and humidity are showing up in a Homebridge Accessory but not on the Apple Home app.  I'll keep looking.

Hi @jonnyquest777
The sensors don't appear as typical tiles in the home app, they appear as circles at the top of the screen with the temperature and humidity data. Since they are only sensors, there is nothing to "control" via the home app.
If you are running the plugin in a child bridge through Homebridge UI, have you added the bridge to homekit with the "+" icon in the home app?

Hi Ben,
I'm all good. The sensor appears as you mentioned.  I had never used a sensor with Homekit so they were there as you mentioned.  Thank you for making the plug in.
Sent from my T-Mobile 5G Device
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Ben @.>
Sent: Wednesday, November 24, 2021 5:33:12 AM
To: bwp91/homebridge-govee @.>
Cc: jonnyquest777 @.>; Mention @.>
Subject: Re: [bwp91/homebridge-govee] Govee sensor data showing in Homebridge log but not through Homekit (Issue #148)
Hi @jonnyquest777https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjonnyquest777&data=04|01||714e744cd4cd4998eff108d9af3e33bd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637733503953856640|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=UyyhveChBAit5fYiinn1TS2oMNKgoxzfevLk4W4FI4U%3D&reserved=0
The sensors don't appear as typical tiles in the home app, they appear as circles at the top of the screen with the temperature and humidity data. Since they are only sensors, there is nothing to "control" via the home app.
If you are running the plugin in a child bridge through Homebridge UI, have you added the bridge to homekit with the "+" icon in the home app?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbwp91%2Fhomebridge-govee%2Fissues%2F148%23issuecomment-977792089&data=04|01||714e744cd4cd4998eff108d9af3e33bd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637733503953866596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Ne5X3xEi7VD8e4NQOA5t5lKDqt9%2BlN6OhykCupE68uo%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAWUIPRDRCAIW3KIJMT4E3CDUNTEPRANCNFSM5IUKWXNQ&data=04|01||714e744cd4cd4998eff108d9af3e33bd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637733503953866596|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=rjxXeDck7fp%2BTQVO%2FuN%2BlLsBzzS%2BAPepAT%2BUvFCDpy0%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01||714e744cd4cd4998eff108d9af3e33bd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637733503953876554|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=bqO3ZsHKGpdbOBt%2BR16X%2BogQmdhuAEGkh9GHmp0rvjo%3D&reserved=0 or Androidhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01||714e744cd4cd4998eff108d9af3e33bd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637733503953886509|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=mTJUA6p51rqOjwS8iybjK0UDwaHtl9DEKKY8jZyt%2FEg%3D&reserved=0.


Bug: button tray for external language cells is misaligned

Expected positioning:

This was fixed in #317


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.2 to before v5.10.46",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1d731e731c4cd7cbd3b1aa295f0932e7610da82f",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a7748e021b9fb7739e3cb88449296539de0b6817"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "1d731e731c4cd7cbd3b1aa295f0932e7610da82f",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "a7748e021b9fb7739e3cb88449296539de0b6817",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.46 by commit a7748e021b9fb7739e3cb88449296539de0b6817, it was introduced in version v5.2 by commit 1d731e731c4cd7cbd3b1aa295f0932e7610da82f. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001002


Fix handling of datasets with shape (0,0,...)

Fix #76.
For an HDF5 dataset with shape (0,0,0), no chunks should be written. This was the previous behavior before #68 and seems reasonable.
For an HDF5 dataset with shape (0,0,0), the chunks key in .zarray was being set to (0,0,0). However, that is not allowed in Zarr. Accessing an array with such chunking results in a ZeroDivisionError: division by zero when trying to access the array. I set it to (1,1,1) instead which is what Zarr does for an array of that shape.
>>> import zarr
>>> a = zarr.empty(shape=(0,0,0))
>>> a.shape
(0, 0, 0)
>>> a.chunks
(1, 1, 1)
>>> a[:]
array([], shape=(0, 0, 0), dtype=float64)
>>> a = zarr.empty(shape=(0,0,0), chunks=(0,0,0))
>>> a.chunks
(0, 0, 0)
>>> a[:]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/rly/mambaforge/envs/test4/lib/python3.11/site-packages/zarr/core.py", line 800, in __getitem__
    result = self.get_basic_selection(pure_selection, fields=fields)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rly/mambaforge/envs/test4/lib/python3.11/site-packages/zarr/core.py", line 926, in get_basic_selection
    return self._get_basic_selection_nd(selection=selection, out=out, fields=fields)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rly/mambaforge/envs/test4/lib/python3.11/site-packages/zarr/core.py", line 966, in _get_basic_selection_nd
    indexer = BasicIndexer(selection, self)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rly/mambaforge/envs/test4/lib/python3.11/site-packages/zarr/indexing.py", line 339, in __init__
    dim_indexer = SliceDimIndexer(dim_sel, dim_len, dim_chunk_len)
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rly/mambaforge/envs/test4/lib/python3.11/site-packages/zarr/indexing.py", line 181, in __init__
    self.nchunks = ceildiv(self.dim_len, self.dim_chunk_len)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/rly/mambaforge/envs/test4/lib/python3.11/site-packages/zarr/indexing.py", line 167, in ceildiv
    return math.ceil(a / b)
                     ~~^~~
ZeroDivisionError: division by zero

I also fixed an issue flagged by pyright in LindiReferenceFileSystemStore.__contains__:
error: Method "__contains__" overrides class "Mapping" in an incompatible manner
    Parameter 2 type mismatch: base parameter is type "object", override parameter is type "str"`

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

Project coverage is 79.47%. Comparing base (731fcb5) to head (ffea54a).

Files
Patch %
Lines

...ndi/LindiH5pyFile/LindiReferenceFileSystemStore.py
66.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #77      +/-   ##
==========================================
+ Coverage   79.43%   79.47%   +0.03%
==========================================
  Files          30       30
  Lines        2256     2265       +9
==========================================
+ Hits         1792     1800       +8
- Misses        464      465       +1

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

Looks good to me!

Thanks. Released in version 0.3.9.


Drop jQuery for good

I saw we were loading jQuery just for delegated events, .has, .wrap and minor invisible loops (e.g. .addClass instead of for-of classList.add)
Dropping 70KB is worth the few extra lines.
(untested proposal) Edit: tested and fixed every part, seems to work, except the 2 pre-existing bugs below.

Aside: I wish JS had a few nice features to clean it up common operations:

optional chaining (avoids the many one-operation ifs)
invoke on iterables: e.g. elements[].remove() instead of elements.forEach(el => el.remove())

Mark as unread will need more testing and fixes, I think. Some issues are pre-existing, others may be new.

invoke on iterables: e.g. elements[].remove() instead of elements.forEach(el => el.remove())

This could actually be implemented using Proxy. If a method is called on a decorated array and the method doesn't exist, call it on all the elements.

Nice! 🙌

This could actually be implemented using Proxy

How about .classList.add('class')? I'm not sure that'd work.
lodash' invoke feels more flexible, even though it's string-based:
_.invoke(elements, 'remove');
_.invoke(elements, 'classList.add', 'class');

@bfred-it That would work too. The Proxy could just wrap all nested properties in the Proxy too.

Looking forward to your module for all(elements).classList.add('class') 😄


ENH : Added algos in centrality/reaching.py

[x] docstring
[x] benchmarks(for directed graphs)
[ ] heatmap

Closing because less than 0 speedups obtained.
Will reopen after a decision is made on Issue https://github.com/networkx/nx-parallel/issues/79


Question about balanced sampling

Thanks for your great work!
I wonder the details about "the balanced sampling of images with and without pedestrains " mentioned in your paper's section 4.
Would you kindly describe it more? Or give some code or paper reference about it.
THX :)

Dear nhnhnh,
It is actually fairly simple: For every batch we make sure, that the batch contains the same amount of images with pedestrians and without them. For example for batchsize 16, we sample 8 images from KAIST that contain pedestrians and 8 images from KAIST that do not contain pedestrians, according to the GT annotations.
Best regards,

Thanks for your response!


⚠ Samsung has degraded performance

In 2f7826f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 5139 ms

Resolved: Samsung performance has improved in 8794e14.


improve tests

this allows the typical bundle install; rake flow to work on this project.
I am also opening this as a chance to ask what you think would be a good testing strategy for a gem like this. I thought about adding some, but realized a lot of the work happens either in other threads or as side effects. the actual login in this gem seems fairly light.

Most of the Gem is just message passing. Data comes from one place gets pushed to another. If anything though probably some simple unit tests that at least verify the message is being sent.


"command 'rust-analyzer.*' not found" in vscode with remote SSH

I encountered the following error when I used rust-analyzer on a remote host.
Command 'Rust Analyzer: Status' resulted in an error (command 'rust-analyzer.analyzerStatus' not found)

I installed rust-analyzer from vscode marketplace. I tried every command defined in rust-analyzer, but none of them worked and I got the same error popups. Removing caches and reinstalling vscode didn't help. On the local mache, it works as expected.
What's wrong with my installation?

My environment

rust-analyzer 0.2.182
rust 1.43.1 stable
VSCode 1.45.1
Remote SSH extension 0.51.0
local machine: macOS 10.14.6
remote machine: amazon linux 2018.03

Have you also installed the extension on the remote machine? I believe that is required.

yes, I installed both remote and local machine.
But I confirmed it works on another host, so I check the difference between them.

The problem is the version of glibc installed on the system.
glibc 2.18 is required by precompiled rust-analyzer binary while there is only glibc 2.17.
I solved the issue by installing it from source.


Add debugging help

Description
This is some guidance on how to debug common problems. This was first written in the wiki and is hereby being transferred to the normal documentation.

Closes #issue_number
Link to documentation:

Before you get started

[ ] ☝ Create an issue to discuss what you are going to do

Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

[ ] 🛠 This pull request has a descriptive title
[ ] 🛠 Code is written according to the code quality guidelines
[ ] 🛠 Documentation is available
[ ] 🛠 Tests run successfully
[ ] 🛠 The list of authors is up to date
[ ] 🛠 Any changed dependencies have been added or removed correctly
[ ] 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

[ ] 🧪 Recipe runs successfully
[ ] 🧪 Recipe is well documented
[ ] 🧪 Figure(s) and data look as expected from literature
[ ] 🛠 Provenance information has been added

New or updated data reformatting script

[ ] 🛠 Documentation is available
[ ] 🛠 The dataset has been added to the CMOR check recipe
[ ] 🧪 Numbers and units of the data look physically meaningful

To help with the number of pull requests:

🙏 We kindly ask you to review two other open pull requests in this repository

I loves it heart_eyes_cat Pinging @rswamina and @SarahAlidoost if they want to include (maybe there are already?) such easter eggs in the Tutorial? PS - approved it, even if you want to add more, I reckon that'll do for now?

Thanks for tagging me. @zklaus great addition. There is a "Debugging" lesson in the Tutorial. I am not sure if the lesson is still up to date, but when this PR is merged, we should refer to the FAQ page in the lesson. I made an issue https://github.com/ESMValGroup/ESMValTool_Tutorial/issues/233


lightos: a volume may not have a project name in some cases

Fix 'Terminate volume connection failed: 'InstrumentedList' object has
no attribute 'get': AttributeError: 'InstrumentedList' object has no
attribute 'get' where the InstrumentedList is the volume's
extra_types.
Signed-off-by: Muli Ben-Yehuda<EMAIL_ADDRESS>

2022-01-19 16:53:09,823 5613<PHONE_NUMBER>63776  INFO root Tempest finished succesfully (105 xfails).  run systests/racktests/904_openstack_tempest.py:111
@yuval-lb pls merge for the next patchset


Revert "move test artifacts to a single dir (#50)"

This reverts commit c39277e424a171cf68f4f52fd8aef379c881a08b.
Description
After thinking through the change, this will require all plugin teams to make the same Cypress configuration change. This will be an extra effort for all the teams.
Thus I want to revert this change and make the logic in infra complicated. I thought we could just copy cypress/results and now we will need to copy 3 times cypress/results cypress/screenshots cypress/videos
Issues Resolved
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

could we add instruction how develop leverage this for troubleshooting to readme/contribution doc?


Adding 'Lilith' to const.py

Hi @joaoventura. I'd like to request a feature - adding 'Lilith' to const.py.
Can you imagine implementing this?

Maybe I should start, does anyone know?


test: using the same set of longhorn resources throughout the 2 stage upgrade test

Which issue(s) this PR fixes:

Issue https://github.com/longhorn/longhorn/issues/9306
What this PR does / why we need it:
using the same set of longhorn resources throughout the 2 stage upgrade test
Special notes for your reviewer:
Additional documentation or context

@mergify backport v1.7.x

@mergify backport v1.6.x

@mergify backport v1.6.x


Add defensive coding around reconciling deleted resources.

We were concerned that the distributed KafkaChannel could potentially hit an extremely rare (if even possible?) race condition whereby it is doing a normal Reconciliation on a resource that exists in K8S but was "being" deleted.  Therefore we'd like to add a small check for the resources Deletion Timestamp and force a re-reconciliation just in case.

Note - The Dispatcher resources (Service / Deployment) are "cross-namespace" and thus have their own Finalizer in place and will not be modified to force re-reconciliation if the user removes the Finalizer.  Some additional state logging was added to be explicit about the handling of the resource during reconciliation.

/LGTM


[master-qa] Expose libp2p_helper metrics via daemon

Tested with _build/default/src/app/cli/src/mina.exe daemon -seed -proof-level none -libp2p-metrics-port 6666 -metrics-port 7777 and observing that the libp2p_helper metrics are included in http://localhost:7777/metrics.
Checklist:

[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them:

!approved-for-mainnet


Document API Umbrella developer integraiton options

There may be multiple options for developing custom code based on, and/or extending, API Umbrella functionality. Document available options including risks and benefits for each.
Deliverable

[ ] Wiki page describing integration options

User Stories
As a developer
I need to know options available to integrate my code with API Umbrella
so that I can decide on which strategy to take when extending API Umbrella functionality
As a project manager
I need to understand how to integrate custom code with API Umbrella
so that I can create a development plan and specification

@GUI will you validate my assertions in the [Integration options] wiki document, and possibly expand a bit on the possibilities?

This all looks good, except I made a couple small adjustments, since our configuration is stored in Mongo, not Redis. Assuming I understand what config you're talking about, most everything like API backend configuration and API user accounts gets stored in Mongo. Redis is only used for tracking rate limits.
In terms of overall integration, though, if you're looking to build a dashboard on top of API Umbrella, then I think you'll predominantly be interacting with APIs exposed by the api-umbrella-web component. The APIs the web component provides should facilitate reading or writing the various bits of config out of the entire API Umbrella system. So while the APIs live in the web component, they typically have an effect on the other components, since all the components read and write out of Mongo for shared configuration. So for example, the web component provides APIs to read or write API users or API backends, but both of those end up impacting the router and gatekeeper components automatically, since those other components read config immediately from the Mongo database when changes are detected.
Does all that make sense and help with your integration planning? If not, definitely feel free to give me a holler, and I'd be glad to talk about things in more detail.

This looks good. I am interested in learning more about how to access the Gatekeeper directly, if possible. We also need to access analytics data, and are not sure how to do that.


Best way to log caught errors?

I want to swimlane my JS, so if one function fails, the next will run regardless. When there is an error, I want to capture it with Raven, and log it to the console.
var swimlane = function (options, fn) {
    try { fn(); } catch(e) {
        raven.captureException(e, options);
        // optionally console log the error
        // console.error(error);
    }
};

swimlane({ tags: { module: 'foo' } }, foo());
swimlane({ tags: { module: 'bar' } }, bar());

To do this, I have written a function similar to raven.wrap, exception it does not re-throw, thus allowing execution to continue.
However, I'm finding that logging the error the console is not easy. Each browser has its own way of logging the error to the console. For example, you might try:
console.error(error);

In Chrome, console.error creates a new error object and the argument is the message. So you end up with an error nested in an error:

http://jsbin.com/vimuxu/1/edit?js,output
In browsers that support the error.stack property (non-standard), I would like to log that. Otherwise, I would like to log the file name, line number, and column number. This logging is essentially what the browsers do automatically for uncaught exceptions.
Because of this, I would much rather let the browser automatically log my errors to the console as uncaught exceptions.
To do that, I could write a swimlane function that just catches the error and throws it in the next turn so it doesn't halt the current execution stack:
raven.install();

var swimlane = function (options, fn) {
    try { fn(); } catch(e) {
        setTimeout(function () { throw e; });
    }
};

swimlane({ tags: { module: 'foo' } }, foo());
swimlane({ tags: { module: 'bar' } }, bar());

The trouble then is I have no way of specifying my options (in this case, tags). I could use raven.setExtraContent/setTagsContext, but that just permanently updates the global options with the new tags.
The best of both worlds would be to capture the error and throw it in the next turn (for browser logging), but then it would be logged twice because raven is also listening for uncaught exceptions:
raven.install();

var swimlane = function (options, fn) {
    try { raven.context(options, fn); } catch(e) {
        setTimeout(function () { throw e; });
    }
};

swimlane({ tags: { module: 'foo' } }, foo());
swimlane({ tags: { module: 'bar' } }, bar());

Is there a happy medium? Perhaps you might be able to shed some light on where I'm going wrong. Or, perhaps you know of a good way to manually log errors across all browsers (stack in modern, file + line and col numbers in non-modern (i.e. IE 9)).

You could call the context methods within setTimeout, but you're still going to likely see issues.
There's not really a solution here as JavaScript is a single interpreter and there's no way for us to understand your concept of a callstack (which is effectively what you're tweaking with the setTimeout).
The only real situation would be something like:

Preserve the current context values
Override with context in setTimeout
throw error
Restore context values'

We dont have an API for that, and tbh I'm not sure it's a good enough solution to warrant one upstream as re-throwing errors in such a fashion doesn't seem to be very standard.

Something like this, perhaps?
raven.install();

var swimlane = function (options, fn) {
    try { fn(); } catch(e) {
        setTimeout(function () {
            // 1. copy global options
            // 2. update global options with new options
            throw e;
            // 3. restore the copied global options from 1
        });
    }
};

swimlane({ tags: { module: 'foo' } }, foo());
swimlane({ tags: { module: 'bar' } }, bar());

Not sure how crazy this is.

Yeah. Thats how you could solve it.


multipleJson

As a user I want to download multiple JSON parse results so I can save time

Done in the develop branch


[BUG] Docker Local Repo

Docker build (Dockerfile in the project root) fails with:
 => [ 8/10] RUN yarn install                                                                                208.6s
 => [ 9/10] COPY . .                                                                                0.3s
 => ERROR [10/10] RUN yarn build                                                                                1.0s
------
 > [10/10] RUN yarn build:
#15 0.630 yarn run v1.22.19
#15 0.750 $ turbo run build
#15 0.945 thread 'main' panicked at 'Failed to execute turbo.: Os { code: 2, kind: NotFound, message: "No such file or directory" }', crates/turborepo/src/main.rs:50:10
#15 0.945 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
#15 0.980 error Command failed with exit code 101.
#15 0.980 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------
executor failed running [/bin/sh -c yarn build]: exit code: 101

Try adding this line RUN apk add --update libc6-compat
https://stackoverflow.com/questions/75174308/turbo-crashes-with-any-command-in-official-node-docker-image-alpine

@HenryHengZJ thanks! yes, tried it already, but had another error in this case. I assume that project repository should contain a working Docker that runs everywhere...

let me resolve this issue.

Put up the fix here - https://github.com/FlowiseAI/Flowise/pull/183
Also for windows make sure files inside packages/server/bin are all LF endings instead of CRLF:

@morfeusys let me know if this is still an issue.
and also thanks @tao12345666333 for taking a stab on this!


Remove pyqt

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

https://github.com/hippover/palmari/issues/1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Add support to get index settings

https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-get-settings.html
esctl index settings
"settings": {
            "index": {
                "creation_date": "1588545932934",
                "number_of_replicas": "2",
                "number_of_shards": "1",
                "provided_name": "indexName",
                "uuid": "asdasdasd-adasdads",
                "version": {
                    "created": "7050099"
                }
            }
        }

If there are multiple indices, we'd need a flag/parameter to filter by index right? Should the command return all indices by default?

@jijotj we can add a flag to specify the index of interest.
Returning all might be noisy in certain cases. But if that is needed we can specify the target as _all
What do you think ?

Yea, sounds good 👍

@jijotj are you picking this up ?

Yea missed assigning it to me. I can do #21 as well as both deal with indexes.

Go for it


Add feature for disabling panning

I also subscribe to this.
An option to stop panning and zooming would be very nice. And make sure to allow events to pass throught to other components.

Great, thank you @mihaiserban for the PR.
Could I ask how you are using the component? It is always helpful to see examples so we can get a better idea of what features to prioritize. A screen shot or just a description would be awesome. Thanks!

I've used react-map-interaction to add zooming and dragging to a html5 canvas (KonvaJS).
I needed when an element was selected on the canvas to disable the zoom/drag on react-map-interaction for a quick demo.
In the end I'll use KonvaJS own scaling properties and translate the elements on drag/scroll.

Hey! I also need prop  to disable dragging.
I  use 'react-map-interaction' in my slider, this lib is the best for touch devices and also works with a mouse or trackpad (what I need).
When I use a default value (transform: none) to controll the 'translation' zoom doesn't work. Or when I  limit translation by translationBounds={({ xMax: 0, yMax: 0, xMin: 0, yMin: 0 })}
dragging is disable, but zoom has only one direction  -  to left top :(

@NataliBILAN Could you describe a bit more how you are using this, maybe with a screenshot? I'm having trouble understanding how you use this for a slider.
I'm working now on props for disabling panning/zooming. However I'm still considering how the UX should work for the case of disabling translation, but not disabling zooming. You can get into a weird position where you have zoomed in and out several times such that the content has gone off screen (or out of your container) but then cannot drag it back in because you've disabled translation. I'm looking for inspiration from around the web but I haven't really found anything.
Some possibilities:

Ignore the issue above, and just add disableTranslation and disableZoom props
Add the props, but handle the case above by letting the user translation only when the zoom is at a scale other than 1 (e.g. when they are zoomed in or out, they can translate the content)
Add the props, but when disableTranslation is true, force the translation to be (0, 0) whenever the scale is 1. This will solve the issue that the user may accidentally zoom the content off screen, however it does cause a slightly janky interaction -- the point beneath your cursor will now longer stay beneath the cursor as you zoom (because we force the translation to coincide with (0, 0)).

@NataliBILAN Could you checkout PR #11 and test that out locally to see if it fits your use case?


v3 s390x release checksum busted

curl https://get.helm.sh/helm-v3.0.0-linux-s390x.tar.gz.sha256
yields "Blob not found" sadness

Good catch. It looks like we don't cross-compile for  s390x builds of Helm 3. I recall that only being PR'd against Helm 2 so it wasn't picked up. I'll remove it from the release notes in the meantime.
Would you like to add it back? Link is https://github.com/helm/helm/blob/master/Makefile#L3


Fact Checks - Filter by Category and Tag is not working - Fact check has Multiple Categories and if we have matching Category in fact-check, it should display the Fact check

Fact Checks - Filter by Category and Tag is not working - Fact check has Multiple Categories and if we have matching Category in fact-check, it should display the Fact check
Two issues here:

When we select one Category, it is not displaying the Result even though Fact check has that Category selected.
When we select all Categories of the Fact check, also it is not displaying the Result.
When we select one Tag, it is not displaying the Result even though Fact check has that Tag selected.

Closing the issue as we are not able to replicate it. Confirmed with @sshankaramanchi that it is working as expected.


[Bug]: unable to see devices after update

What happened?
I am unable to see all my eufy devices after updating my Hoobs hardware. Please advise. Thanks.
Device Type
other (UnSupported)
Plugin Version
v1.0.x (Supported)
HomeBridge Version
other (UnSupported)
NodeJS Version
v14 (Supported)
Operating System
Raspbian
Relevant log output
19/10/2021, 1:17:09 PMeufysecuritybridge stopping
19/10/2021, 1:17:13 PMEufy Security Bridge starting
19/10/2021, 1:17:23 PMEufy Security BridgeLoaded plugin 'homebridge-eufy-security'
19/10/2021, 1:17:23 PMEufy Security BridgeLoading 1 platforms...
19/10/2021, 1:17:23 PMEufy Security BridgeEufySecurityFinished initializing Eufy Security Platform
19/10/2021, 1:17:23 PMEufy Security BridgeEufySecurityERRORError refreshing data from Eufy:  TypeError: client.refreshData is not a function
    at EufySecurityPlatform.refreshData (/var/lib/hoobs/eufysecuritybridge/node_modules/homebridge-eufy-security/src/platform.ts:418:22)
    at EufySecurityPlatform.discoverDevices (/var/lib/hoobs/eufysecuritybridge/node_modules/homebridge-eufy-security/src/platform.ts:151:16)
    at HomebridgeAPI.<anonymous> (/var/lib/hoobs/eufysecuritybridge/node_modules/homebridge-eufy-security/src/platform.ts:119:7)
19/10/2021, 1:17:23 PMEufy Security BridgeBridge is running on port 53826.

Seems to be the same issue as : #263
Try to increase permission on your guest account

Thanks, problem solved!

thanks for your feedback. I've updated the doc


Support GHC 9.2

I'm not sure it's just bumping the bounds, because LambdaHack with allow-newer compiles, but crashes. I can investigate whether it's witch-caused, if that helps.

Seems like it works fine with GHC 9.2: #42. Do you know what exactly crashed?

Let me test.

Yes, it all seems to work fine. I think the crashes I'm seeing are from sdl2: https://github.com/haskell-game/sdl2/issues/233


Allow postcss

This PR adds support to adding postcss argument to tailwind cli

Hi, thanks for proposing these changes.
Big picture question: does this need to be something that the user has to opt-in to? If the postcss.config.js file is present would it be better to have this gem silently pass the --postcss option? Put another way: is there a reason users wouldn't want to pass --postcss if that file was present?
If the answer to the above is "this should be a user option" then there are some things going on in this PR that I'd like to ask you to change:

do not bump the version number, that's something we do during the release process and not in a feature or bugfix PR
please add test coverage for this command variation in test/lib/tailwindcss/commands_test.rb
please remove the "contributing" section from the readme, there's a separate CONTRIBUTING.md document you can add to if you like
please clean up the commit history

Hi @flavorjones  thanks for your comments. I think it is a good idea, but it does not follow the principle of least surprise IMO.  I can imagine people having old postcss files in their repos where this could break.
No strong opinion though, as this could be railsy "convention over configuration" way
If you agree I can make the proposed changes and update the PR.
cheers

I've never used postcss files, so I don't have an opinion either way. Why would someone have an "old postcss file" and not want to use it? I'm asking questions in order to understand.

Of course, no worries.
I came from a webpacker/postcss rails installation (which was default a few years ago) and migrated to a nodeless environment in production with tailwindcss-rails and importmap. In my case I had deleted the postcss.config.js , but I can imagine folks who forgot to do this in the migration, and after a gem update that would break.
But all of this is speculative

Any chance of moving this forward? Can I help doing so?

@muriloime As I mentioned above, I'm not very familiar with postcss, so I don't understand why a postcss.config.js file would exist if people didn't want to use it.
From the standpoint of "convention over configuration" it feels like we should detect its presence and pass the appropriate options automatically to tailwindcss ... but if you feel strongly that this would surprise people and the workaround isn't simply deleting the file, then I'll trust your judgement.

Regarding @flavorjones comment, I'd follow the convention over configuration paradigm. Old configurations will probably blow up anyway if there's a postcss configuration in place which shouldn't.
What I found the last days playing around with the postcss integration in a rails 7 project using importmaps is the following.
I got errors from postcss stating that it couldn't be found in the node_modules folder. I am going the default importmap route in my rails 7 project, thus not having npm / yarn by default.
To make postcss work I had to bring in yarn. This has to be considered when for the convention over configuration way.
In fact it's the configuration file (postcss.config.js) and the postcss package.
@muriloime how did you manage to have postcss in place? also using yarn?

Hi there, I've just made the proposed changes. Because the way this gems works ( producing cli versions for each platforma), I don't have an easy way to test it, other than publish a gem like https://rubygems.org/gems/tailwindcss-rails-alt , but I realized I lost my 2FA rubygems credentials.
@basiszwo I use heroku, and use a node buildpack and a very clean package.json to run postcss

@muriloime for the README part. Isn't it that the postcss.config.js needs to require the already existing tailwind config at config/tailwind.config.js?
module.exports = {
  plugins: [
    require('tailwindcss')('./config/tailwind.config.js')
  ]
}

If so, maybe covering this aspect in the README would be very helpful.

hey @muriloime 👋
do you need help to get this PR to the mainline? If so I can try help you. Would be nice to have postcss supported on this gem

closing in favor of #316


Added CLI options with argh and implemented cli capturing

As mentioned in #136, it should be possible to operate packetry via the terminal. This PR tries to address that and a bit more :P
A little warning first: I'm a total rust newbie, and the code is probably highly unoptimized and may contain flat-out bad code. The capturing stuff was pieced together by reading ui.rs. I've tested this on Linux and with the newest branch, the one which already has packetry-cli.
New Stuff

First, I implemented cli arguments using argh. (It was the first simple-looking crate I found)
The optional argument of a pcap file will still open in the GUI
The version and test-cynthion commands were ported from your code
The command devices will search for and list all Cynthions found in a table. For this, the dependency tabled was added. (technically optional)
The capture command does what it says. For stopping captures with CTRL+C, the dependency ctrlc was added.

Previews
Here are some CLI previews:
$ ./target/debug/packetry --help
Usage: packetry [<filename>] [<command>] [<args>]

packetry - a fast, intuitive USB 2.0 protocol analysis application for use with Cynthion

Positional Arguments:
  filename          recording (pcap) to open in the GUI

Options:
  --help            display usage information

Commands:
  capture           Start packetry in CLI mode
  devices           List capture devices
  version           Print version information
  test-cynthion     Test an attached Cynthion

$ ./target/debug/packetry capture --help
Usage: packetry capture [-d <device>] [-s <speed>] [-o <output>]

Start packetry in CLI mode

Options:
  -d, --device      device (default: auto)
  -s, --speed       usb speed (default: low)
  -o, --output      output file (use '-' for stdout, default: cynthion.pcap)
  --help            display usage information

./target/debug/packetry-cli devices
+----------+------------------+---------+-----+---------+-----------------+
| name     | serial           | useable | bus | address | speeds          |
+----------+------------------+---------+-----+---------+-----------------+
| Cynthion | xxxxxxxxxxxxxxxx | Yes     | 3   | 20      | High, Full, Low |
+----------+------------------+---------+-----+---------+-----------------+

Changes

I had to make some minimal changes. All println needed to become eprintln as the piping to, for example, Wireshark would not work. (stderr vs. stdout)
I added some implementations to Speed, which enables me to look up the speed in a nicer fashion from the CLI argument.

Thanks for the feedback. I really appreciate it.
Regarding the command line parsing, I can totally understand why this needs to be a separate PR, as your system right now works for you. For CLI capturing, however, I need a separate crate (from the beginning) as my code does not create a GTK app for obvious reasons, and your has_argument() only gives out booleans. Doing CLI parsing by hand with, for example, a get_argument() when there are perfectly working crates seems a bit too hacky. Based on rosetta-rs/argparse-rosetta-rs, I choose argh for this. However, I'm open to your suggestions.
Seeing your latest work with packetry-cli, I moved all my parsing to cli.rs.

packetry works fully independently with the same arguments as before.
packetry-cli contains all the arguments used for cli capturing and works independently.

If packetry-cli open file.pcap is executed, the GUI opens with the code you recently added by forwarding the filename as arg[1].

Please tell me if this is a direction that works for you.
Additionally:

I've optimized the capturing (only one writer)
I've removed the watchdog for the CTRL+C handler
I've optimized the table generation

I had to modify the exception list in rust_licenses.py to accommodate for a higher version number

I changed the indentation to spaces.

Looking forward to your feedback. I'm gonna change this PR to a draft in the meantime.

This breaks the version and test-cynthion arguments via packetry-cli on Windows as those arguments only exist in packetry GUI. I could forward all args to the child process if no subcommand is applicable but then the CLI version would not list those as available commands.
I'll look into your suggestion of not using subcommands but rather --option tomorrow. Maybe there is an easy way of not having to maintain arguments in two different files.

This looks a lot better with the changes you've made already - nice!
On the issues about how to structure this going forwards, there's a few reasons behind the way things are done right now that really won't be obvious from just reading the code, so I should probably start by explaining the history a bit.
Backstory
The key thing to understand is that we'd been trying for a while to avoid having more than one binary target in the package. That was specifically due to some limitations of the Rust tooling, as follows.
Previously, we had multiple binary targets. Both test_cynthion.rs and test_replay.rs used to be standalone programs. To share code between main.rs and those additional programs, we had two options. Either:

Import the modules used by each program directly in its main file, with e.g. mod foo.
Import the modules by multilpe programs into a src/lib.rs, make them public, and use that library in each program.

Option 1 turned out not to work well, because it produced a lot of spurious dead_code warnings whenever some code in those common modules wasn't used by whichever binary was currently being built. And we didn't want to just turn off all dead_code warnings, because they're actually very useful.
So we went with option 2 instead. But that required us to have a library crate, with a public API. And we learned that would automatically end up on docs.rs as soon as we made a release, whether we wanted it there or not! That would include a lot of internal things, that are still too in flux for us to commit to a public API for them yet. And we didn't really trust people not to start using that, and demand support for it, even if we documented it as unstable and unsupported.
So as the deadline approached for the initial 0.1.0 release, I did a big push to get us down to a single binary target and get rid of the unwanted library target:

#100 made test_replay.rs into a normal unit test.
#105 moved test_cynthion.rs into the main binary, and removed the library target.

But that still left us with the problem of Windows, where we couldn't have command-line functionality on a GUI binary. So I wrote #154 to add packetry-cli as a purely standalone wrapper program; one that wouldn't have to share any actual code, but just provided a way to attach a console to the main GUI binary on Windows.
Next steps
The question of how things should be done in packetry and packetry-cli is entangled with those previous issues.
I quite like your approach of importing just mod pcap and mod backend into cli.rs, so that command-line capture can be implemented in that program, and so far at least, that seems to have worked without triggering the dead_code issue.
But invoking the wrapping code in the case of packetry-cli open is the wrong thing to do. We don't need any of that if we just want the GUI to open a file. We can just spawn the GUI without any console in that case, and at that point there's no need to have packetry-cli open filename, the user can just run packetry filename instead.
The case in which we need that wrapping code is where we want to get console output from the GUI binary. And currently that's only necessary when we want to run it with --help, --version or --test-cynthion.
So I think there's two basic options for how to proceed:

We recognise those options in packetry-cli, wrap the GUI binary, and forward the necessary arguments.
We put the code that implements those options into packetry-cli itself.

In the case of --help and --version, we're going to want those options to exist on both binaries. For Windows users, those options won't be usable on the GUI binary. But the version information is available in the About dialog in the GUI, so that's fine.
In the case of --test-cynthion, I think the aim should ultimately be to move that to packetry-cli. It's console-only functionality, and it's only part of the GUI binary for the historical reasons outlined above. The main issue I see with moving it is that we may run into the dead_code issue again.
If we can successfully move all the console functionality to packetry-cli, we can get rid of the wrapping code entirely.
As far as the argument handling goes, I think it makes sense to split this up, such that we use a Rust-native solution for packetry-cli, but the GUI program continues using the glib/gio argument parsing. The latter is important as it takes care of correctly parsing various location types into a gio::File that can be opened by the application. This already works nicely with loading captures from HTTPS URLs, SMB shares, MTP devices, etc - and we don't want to have to reimplement all that.
I've had a look at the other options listed on that rosetta-rs page, and I agree that argh looks like a good choice for the CLI side of things.

Thanks for the backstory. It helped me understand the current problems.
I've removed open and added version to packetry-cli again.
You mentioned you didn't get dead_code issues. Even before my changes, I saw some, so I don't know why you didn't get any. Right now, they are definitely present. If I move test-cynthion to packetry-cli, I get even more, as I have to mod a lot more crates. I don't really know how to go forward here without changing some major stuff.
For me, the state that the CLI version is in works, as I only needed the Wireshark piping for a project, and I'd be more than happy if a developer with more Rust experience would take it from here. I honestly didn't open the PR to be an active developer on this project/feature as I don't really like Rust and don't have the time to like it more. There was just no excuse not to share the code. I hope this is somewhat understandable.


Api search redirection not working properly

What happens?
when I search api from search box first time it will redirect to me to the api, when I try same step second time it's not redirect to the api.
What did you expect to happen?
when I search the api and select that api so need to move to the api documentation.
How can we reproduce the issue?
1.Go to scalar and search for api and click on it. it will move to the api.
2. Go above and close all api dropdown then again search the api and click on it.(Try most last api in swagger docs).
3.see the video
https://github.com/scalar/scalar/assets/55544548/4994f8f6-e98f-4984-be9a-b78123298504
Swagger/OpenAPI Example
No response

@amritk Do you know that’s going on here? 🤔

I think it might not be waiting until the element exists before scrolling. Might need a mutation observer here

Hi @jatingajera31 I believe we wait for the element to exist now! Please re-open if its still an issue on the latest version


[now dev] getting stuck and never finishes

I have a problem with now dev getting stuck in this state for several minutes trying to build static assets with Parcel.
$ now dev
> Now CLI 15.2.0 dev (beta) — https://zeit.co/feedback/dev
> Setting up 2 Builders
⠦ Setting up Builder for package.json: ✨  Built in 5.37s.

After a couple of minutes, the process fails like this:
$ now dev
> Now CLI 15.2.0 dev (beta) — https://zeit.co/feedback/dev
> Setting up 2 Builders
downloading user files...
installing to /var/folders/z6/cw3bj9990rv4c4_n12_f31ph0000gn/T/co.zeit.now/dev/workPaths/oplvjl7g
yarn run v1.15.2
$ parcel watch index.html
✨  Built in 5.63s.

> Error! Failed to detect a server running on port 52001

My setup:

MacOS X Mojave - 10.14.4
Now 15.2.0
Node 10.15.3
parcel-bundler 1.12.3

You can simulate this issue on my repository.

The problem is that your now-dev script is not binding to the port specified by the $PORT environment variable. Please see the @now/static-build local development documentation for more details and an example.

In your case (parcel), I believe the proper now-dev script should be: parcel serve --port $PORT. Let me know if that works for you please 🙏

That works, now the job finishes. I just have to adjust parcel to serve the file in the right format.
Thanks!


Incompatible with Create Trains

Description
Trains have a unique third person perspective while in the driver seat to allow you to see properly in third person. This mods camera overrides that.
Minecraft version
1.20.1
Incompatible mod name
Create Fabric
Incompatible mod version
Any/Newest
Game Logs
https://mclo.gs/wb5j7GO

Thank you for the report. I will look into it. I made some changes literally yesterday that could help solve this issue. However, while testing, I noticed more serious issues when using create mod and shulder surfing reloaded together, such as the ray casting of the player not working correctly for create trains.


[Enhancement] Add support for model compilation

AutoGluon-Tabular currently trains many models. Each of these models adhere to the AbstractModel API.
Add a new method: AbstractModel.compile which can be called after AbstractModel.fit. AbstractModel.compile will perform an operation which creates a new model artifact that is able to perform inference on new data faster than before compilation.
This must be implemented separately for each model, as the way to compile each model can differ (and some models will not support compiling).
Models in order of priority for adding compilation support:

Random Forest / Extra Trees
LightGBM
TorchNN
FastAINN
XGBoost
CatBoost

Known packages that could provide CPU compilation support:

ONNX
TreeLite
TVM
Intel sklearnex
lleaves

Accelerated Models:

KNN -> Intel sklearnex
Linear -> Intel sklearnex

Extra: Average training time, inference time, and model quality on 1040 datasets as of v0.4.0, which we see that RF/XT/NN are the slowest models during inference by a large margin.
           framework  loss_rescaled  time_train_s_rescaled  time_infer_s_rescaled
0           CatBoost       0.051178            2300.807620               4.059308
1         LightGBMXT       0.069720             129.668734               5.967802
2            XGBoost       0.094320             134.763325               2.704312
3           LightGBM       0.118972              87.351193               4.118561
4      LightGBMLarge       0.141573             221.466008               6.134407
5   RandomForestEntr       0.139603             126.959287              36.647381
6     NeuralNetTorch       0.156578             799.706151              17.693657
7   RandomForestGini       0.147252              92.553456              36.738299
8    NeuralNetFastAI       0.196004             423.930844              19.812870
9     ExtraTreesEntr       0.173157              66.854415              34.559691
10    ExtraTreesGini       0.176122              65.440872              45.290199
11    KNeighborsDist       0.898552               1.000000               8.141010
12    KNeighborsUnif       0.917718              11.649699               7.620200

Ping also @bryanyzhu @zhiqiangdon . This is related to adding ONNX-graph exporting / TVM exporting support in AutoMM.
This is a really good proposal! For the compile flag, should we aim at option-1 or option-2?
# Option-1

predictor = XXXPredictor()
predictor.fit(train_data)
predictor.compile()
predictions = predictor.predict()

# Option-2

predictor = XXXPredictor()
predictor.fit(train_data)
inference_only_predictor = predictor.compile()
predictions = inference_only_predictor.predict()

Option-2 has the advantage that we can get multiple inference_only_predictors for different devices.

I like option-2, the same reason as you mentioned.

@sxjscience I prefer option-2 in the long-term because it has obvious benefits of flexibility and avoids non-reversibly changing the original artifact, however option-1 is easier to implement in regards to AutoGluon's stacking logic without major code changes. (I've already done working PoCs for lleaves and ONNX in <100 lines via option-1, would be a lot more code for option-2).
For short-term, we can simplify by saying that we always replace model with its compiled version on disk and return the compiled version, while internally simply updating the model artifact itself, then later we can remove the assumption that we replace the model artifact and can instead save compiled model to a new location and treat them as separate models.
One hack to get option-2 with less code is to link it to Predictor.clone functionality (#1755) and simply clone the predictor and perform option-1 on the clone (effectively the same as doing option-2 on the original)