RangeError: Maximum call stack size exceeded when toMatchObject with array circular references

Describe the bug
Similar to https://github.com/vitest-dev/vitest/issues/5533, but the cause of the issue looks slightly different, so I'm creating a separate issue.
The failing case is taken from Jest's issue:

https://github.com/jestjs/jest/issues/14734

import { test, expect } from 'vitest';

function gen() {
  const a: any = {
    v: 1,
  };
  const c1: any = {
    ref: [],
  };
  c1.ref.push(c1);
  a.ref = c1;
  return a;
}

// success
test('toEqual', () => {
  expect(gen()).toEqual(gen());
});

// RangeError: Maximum call stack size exceeded
test('toMatchObject', () => {
  expect(gen()).toMatchObject(gen());
});

Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-ysdtzj?file=test%2Frepro.test.ts
System Info
[stackblitz]

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.3 - /usr/local/bin/pnpm
  npmPackages:
    @vitest/ui: latest => 1.5.0
    vite: latest => 5.2.8
    vitest: latest => 1.5.0

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

In some cases, this chai util is getting into loop:
https://github.com/vitest-dev/vitest/blob/470f56102a7708b7ae5d7375ee2135a26a82c795/packages/expect/src/jest-expect.ts#L167-L176


[Feature Request]provide minimal set of components by default to reduce resource consumption

EdgeX Foundry has include several micro-services, some of which are not necessary by default. Since thelevski version, the inter-communication method changed from REST to message bus which lead to some more unnecessary components.
We hope that Iot-Manager could deploy a minimal set of necessary  components by default to reduce resources consumption. Meanwhile, could allow users to customize add more optional components.

This issue has been solved by this pr.


docs: remove repository transfer statement

The repository is now on on neotest organization

hello @haydenmeade, do you think we can merge this small doc update?

Thanks @mikaoelitiana


Missing instruction to have multiple camera views like in the README.md screenshot

i;ve looked at the wiki pages, but its Missing instruction to have multiple camera views like in the README.md screenshot

https://github.com/kinsi55/CS_BeatSaber_Camera2/wiki

Repositioning the Camera windows can be done via drag and drop, resizing them can be done like one would expect with the bottom right corner on the preview.
Positioning postionable cameras (Third person) can be done from within VR by holding the respective camera with your trigger and moving it around.

Granted, newly created cameras being fullscreen is not very clear, I've already changed it so that newly added cameras become a smaller window instead of taking up the entire screen by default, this will be part of the next update.

sorry, do you have a video how to do it? I;ve traced the in-VR laser to the 8 edges of the preview window and cant resize it

Well yeah thats the only thing that I have not yet figured out if / how I could move it to VR. I dont think theres really any good way to do it.

yeah i imagine on VR you would need to add a "desktop view" window in a "desktop layout" submenu or something. much easier using the desktop view.
btw can the view be adjustable by its 4 sides instead of just from the bottom right?

Technically yes, practically I need to manually implement them all. I'll think about it.

this doesnt work for me at all. I have 3 cameras set up. The "Main" First person camera and two positioned cameras.
Now in the desktop view of the game i cannot drag and drop anything, i can only see the last camera. Left click doesnt do anything and right click shows me:
  ---------------------------
  FYI
  ---------------------------
  There is no desktop settings for Camera2, everything is done ingame!
  ---------------------------
  OK
  ---------------------------

is there anything additional to configure?? Also: is there any possibility for the viewers (on couch, i dont stream) to manually switch between camera views? like hit button 1 for cam 1 and button 2 for cam 2? that would be incredibly awesome.
Cheers
Jan

Yes, all of that is possible and all of it is outlined in the Wiki.

When I set up two cameras, the first person camera is not visible on the screen. Do I need to make it visible and then drag and drop on the desktop? @kinsi55

When you add a new camera it is full screen by default, so you need to resize and position it as you like. This is of the things that changes in the next update.

Massively improved in the current 0.3.8 Beta release: https://github.com/kinsi55/CS_BeatSaber_Camera2/releases/tag/v0.3.8


⚠ Bofrost.es has degraded performance

In a440ab1, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1482 ms

Resolved: Bofrost.es performance has improved in ebd5009 after 11 minutes.


Ignore the changes of status.conditions and useless annotations in svc during service registration

Please provide a description of this PR:
fix #44923

The original issue is saying conditions update.

The original issue is saying conditions update.

@hzxuzhonghu But the change of annotations will make istiod handle the svc also, that is unnecessary.

Don't we already have logic to filter out unneeded service events? #42617?

@howardjohn This PR only handled labels, did not handle annotations and conditions, and I think we can avoid unnecessary processing of istiod from the source.

Don't we already have logic to filter out unneeded service events? #42617?

@howardjohn This PR only handled labels and annotations, did not handle conditions, and I think we can avoid unnecessary processing of istiod from the source.

I don't see how it ignores conditions. model.Service doesn't have conditions, so any conditions change will not impact the equality check done (prev.Equals(curr))

So how can condition changing make this "miss"?

@howardjohn I apologize for any confusion I may have caused. What I meant to say is that, before handling the k8s svc, we can filter out any changes that may not be necessary in order to avoid any unnecessary processing.
For example, when there are changes in conditions, we do not need to convert k8s.svc to model.svc and not need to call addOrUpdateService.

Do you care about conditions? If not, can we strip it calling .SetTransform

If this works, I Think this is better approach.

Do you care about conditions? If not, can we strip it calling .SetTransform

@hzxuzhonghu  This doesn't seem to works. SetTransform can set conditions to nil, but can not prevent updating events.

That's unfortunate, i think the only way is to filter out unrelevant events in onServiceEvent. But keep in mind to be more efficient

Why do we care about the events? They do NOT result in a XDS push, right? Because we filter them later?
Even the original issue says "...triggers istiod to push XDS to the data plane, which is unnecessary..."

I think @miaoyq meant the handler will do some work like service convertion, which is a waste

That's unfortunate, i think the only way is to filter out unrelevant events in onServiceEvent. But keep in mind to be more efficient

@hzxuzhonghu I have refactor the "Equal" code, PTAL again, Thx.

I also thought we are trying to solve XDS pushes as documented here. If it is just events - I think it is not a huge problem. I do not think it is worth complicating this.

I don't think we should do this. It is complicate - this is 800 lines of fragile code with likely no performance benefit.

@howardjohn Most of the code is test cases (620+ lines), but if this would increase the understanding and maintenance cost, I also agree with you. :-)


dependent BAP version is master

I tried to install cbat_value_set pass on ubuntu 18.04 with BAP 2.0.0. And It fails with dependency problem.
Installing /home/hulk/.opam/4.07.0/lib/cbat_value_set/opam
opam pin add -y .
Package cbat_value_set does not exist, create as a NEW package? [Y/n] y
[cbat_value_set.~dev] synchronised from file:///home/hulk/code/bap/cbat_tools/value_set/lib
cbat_value_set is now pinned to file:///home/hulk/code/bap/cbat_tools/value_set/lib (version 0.1)
The following dependencies couldn't be met:
  - cbat_value_set → bap >= master
      no matching version

[NOTE] Pinning command successful, but your installed packages may be out of sync.
$ bap --version
2.0.0

The version of dependent BAP is master. It was failed because my BAP wasn't built from the master repository. I could successfully installed cbat_value_set by replacing master to 2.0.0.
Should BAP version be master? If not, It is better to fill with actual version number.

Hi @jishoon, sorry for the late response! We've created a "release" branch, which depends on bap 2.0.0, and should be suitable for your purposes. Please tell us if you run into further trouble.
The master branch is being used for development, so we're sticking to depending on BAP master for the moment, since some of our features are somewhat experimental.


take parameter is impacting the sort of the results in a findmany query

Bug description
I wanted to create a paginated resource that can be sorted and filtered. and i noticed that the order of the results is varying depending on the value i give to the take param
How to reproduce
when changing the take parameter (varying page size, not offset) I see the top of the list changing (and it should not)
~if i had to guess i would guess that the take parameter is applied to the results before the orderBy and which leads to incorrectly sorted results~
EDIT: It seems to be only when there are multiple identical values in the sorted column
Expected behavior
the take parameter should have no impact on a ordered list
Prisma information

Environment & setup

OS: Manjaro (Arch)
Database: PostgreSQL
Node.js version: v15.10.0
Prisma version: 2.18.0

tl;dr
do you need me to create some repo where the error can be reproduced?
b.t.w. thank you for the great work, it is really a great tool

@Waldbillig-Thomas Yes, please create a reproduction for this so that we can see the problem and use that reproduction to fix the issue. Thanks!

I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.


Is it possible to use it on ROS?

Hello, can this code be used directly in ROS melodic or in Open CV with ROS melodic?

We don't have ROS integration, you can make contributions by adding in to ROS package 😃


Allow palettes to specify a separate hue for uncontained text

Please describe the feature you would like to request.
There is a lot of emphasis on making sure that you choose accessible text colors to ensure readability when your palette color is used in the background but there is no such concern when your palette color itself is used as the text color on a neutral background. This is exacerbated by the fact that @angular/material components will implicitly use the default hue of the palette when selecting this text color - for example in _form-field_theme.scss:
$focused-label-color: mat-color($primary);
it's very hard to pick a palette whose primary is effective both as a strong background color and as a strong text color for small text on a neutral background and conforms to any existing brand guidelines.
One way to fix this would be to extend mat-palette with a fourth argument, $text. For compatibility it could default to $default if not specified, but this would allow you to use a much darker hue on form field labels and so on without making primary backgrounds darker everywhere else.
You can quite easily see the accessibility issues with the current system with some of the prepackaged themes. For instance setting the theme to purple-green on https://material.angular.io/components/form-field/examples gives a contrast ratio of 2.09 for the form field inputs.
What is the use-case or motivation for this proposal?
Improves accessibility
Is there anything else we should know?
No

I've been looking at a few issues (#13905, #15672) with colored text in dark themes.  Defaulting the text value to 500 means that when a theme color (primary/accent) is used for text it will have poor contrast on dark backgrounds.  Ideally you could have the text be a light tone (50/100/200) for dark themes and a dark tone (600/700) on a light theme, but of course when you're constructing a mat-palette you don't know what mat-*-theme function it will be passed to.
I know the PR is already merged, but I have an alternate proposal.  In all the places where the text key is referenced (*-theme.scss), instead of e.g. _mat-button-theme-property($theme, 'color', text);, you could write _mat-button-theme-property($theme, 'color', if($is-dark-theme, lighter, darker));.  This relies on existing light/dark variants while providing accessible contrast on both types of background.  Of course it gives less control than an explicit text value.  I'm not a Sass master but maybe there's a way to have no default value for text and fall back to lighter/darker in context when consuming it (i.e. in the individual -theme files)?
If you don't agree with this change, we're going to either need a fifth hue, for separate light-text and dark-text, or at least we'd need to update theme creation documentation to state that mat-palette always creates palettes that are not suitable for use with mat-dark-theme unless you specify a text, which doesn't seem very developer-friendly.

Oh, and I guess cc @benelliott and @josephperrott

@thw0rted The problem with not defaulting to 500 is that it will be a huge breaking change that invalidates a lot of screenshot diffs for apps inside Google (I know because I accidentally did it with this PR initially 😄). AFAIK because of how Angular is deployed inside Google it would then be the Material team's responsibility to go in and "fix" each of these independently.
Moving forward though I definitely agree - this PR goes some way to helping the situation but it's quite easy to find situations where it still falls down. I think this will always be true however just due to the sheer number of text/background colour combinations you can end up with even within the theming engine.

If I understand the situation correctly, the text key didn't exist a few months ago, so anybody referring to it must have added such references quite recently.  I think this is a good opportunity to reconsider how all of us use color and make sure we're always doing it in a background-sensitive way, to make sure we meet a11y requirements.  Dark is becoming more popular and also more widely supported, so anything we can do to get away from treating light as "default" is a real improvement.
All that to say: if it continues to default to 500, text doesn't really mean "text", it means "text in a light theme". And actually, thanks to snackbar, it's even more specific than that: it's "text on a standard background in a light theme, or on an inverted background e.g. snackbar, in a dark theme". Either kind of theme actually needs the inverse as well, so that a dark-theme snackbar (with a white background) can have a more-saturated tone for its action text.
How would you feel about that?  I don't know what name would be appropriate, or if it's too late to change the name of the current fourth-argument key, but it sounds increasingly likely that either we need 3 keys (default, darker, lighter) or 5 (those plus "dark-tone text" and "light-tone text").

So, having thought about this for a while and looking at the comments in https://github.com/angular/components/blob/master/src/material/core/theming/_theming.scss#L12, I feel like an invocation of mat-palette needs to be interpreted as being specific to a
(light or dark) theme rather than an invariant set of colors.
The base palette is the invariant but the mat-palette configuration (the base palette plus the selection of hues for light/dark/text) is not.
This means that when you build a light or dark theme you need to create a mat-palette with hues that are selected for that particular theme. So if you are building a dark theme, you should pick paler hues from your base palette for the text hue and so on.
Obviously this doesn't mean that there will be a good contrast ratio in all cases - you might still override the "dark grey" background color with a pale background color in some of your components' CSS for example. But there is no real way for the theming engine to detect that at build time.
The above suggests that there should be light and dark variants of any predefined palettes in order to ensure a decent contrast ratio in all cases. So the pink mat-palette in the dark "pink-bluegrey" theme should have a different text hue than a pink "mat-palette" in a light "pink-bluegrey" theme.
Coming back to setting 500 as the default - this is purely for backwards compatibility currently. I don't disagree that 500 will be suboptimal for text contrast in a lot of (most?) cases but changing it would mean that apps inside Google break unless they start explicitly defining a text hue in their own palettes. I don't know what the appetite for such a big change would be within the Material team.
Snackbar is currently a bit of an outlier because its theme colors are very hard-coded, even going as far as having an inline hex value in the theme.scss: https://github.com/angular/components/blob/master/src/material/snack-bar/_snack-bar-theme.scss#L13
This pushes me towards the idea that inverted components (like snackbar) should be themed by a separate inverted theme property. It would get rid of any hard-coded values and would also mean we could avoid workarounds like https://github.com/angular/components/blob/master/src/material/snack-bar/_snack-bar-theme.scss#L10. Plus, it would mean that users could further customize their theme if, for example, they wanted a dark snackbar on a dark theme (e.g. for a night mode UI).

I get your point about having a theme-specific palette, and it makes sense.  Are you suggesting a fifth palette argument for inverted?  If so, would that fall under this issue, or would it merit a separate issue?  Unfortunately that keeps us thinking "light as default", but maybe that's not a fight I can win.  It would have to default to a light tone, maybe 100, I guess.
You mention Snackbar: adding an explicit inverted tone would make it easy to resolve #13905. As you point out, that hard-coded inline hex is a spec violation.

I was actually thinking that the inverted theme would have to be a whole theme in its own right (so, a level or two up from the palette) - but still thinking about if/how this would actually work (+ without massively bloating everyone's CSS!)


Consider: Use Firaxis's Gossip Dialogs

These:

instead of what we have now in the game (the centered message on the blue background)
We could probably continue to use the shortened gossip strings with the dialogs that are off-center on the screen

How is this popup behaving when the yield banners are fully open? Does it move down automatically or does it overlap?
I am using my Better Leader Icon mod and my yield  banners are much smaller, so I am curious.

don't know offhand, but that's a good point.  There had to be an adjustment made with CQUI's banners a while back so those didnt' overlap

I did a test and took screenshot. I am using Concise UI, but the banner expanding still function like vanilla:
[img]https://i.imgur.com/BvTxXFF.jpg[/img]
[img]https://i.imgur.com/DxypBze.jpg[/img]

I have been playing around with this.  I like the Gossip screens, but the tiny font and tiny box with the default status type is just rough.  I propose the change be at least to make the not-Gossip boxes more readable:

Font and width of the box in "Default" status message box is the same as Gossip.
Also, the code to trim the gossip string also appears to be out of date because CQUI\Assets\Text\Gossip_Text.xml exists, so at least for the time being we have CQUI doing work it doesn't need to do.
Regarding the look, it'd be nice to make the box size configurable... however that's only possible if all of statusmessagepanel.lua is replaced, and the presence of NovaGossipPanel.lua implies that statusmessagepanel.lua may not be around for much longer...

Implemented in #140


Design defense in depth for interpolation hazards

A significant percentage of security issues across the software industry are caused by interpolation hazards: cases where a bad actor can influence the content of variables interpolated or concatenated into strings.  The most well-known of these is probably the SQL injection ("Bobby Tables") attack, but a fairly large number of attacks are possible against TUIs directly.  This includes the insertion of unexpected escape sequences and misleading line breaks, among many others.
It is expected that T-W apps will be rendering a LOT of strings, many of which will be partially or totally controllable by an attacker.  Thus to be a good citizen, T-W itself should provide significant defense in depth against these attacks, and make sure that the easy way of operating with strings is also the correct and safe way to do so.

[x] Strings in the Raku source should be single (or q/Q) quoted (completed as of c63bc1a)
[ ] Translated strings cannot interpolate unless the source string is marked explicitly as interpolatable
[ ] Strings are not parsed for span markup unless explicitly requested
[ ] Any displayed string must be defanged of control characters of all sorts (including e.g. rendering direction overrides)
[ ] Any displayed string must not allow invalid or unassigned Unicode codepoints
[ ] A single render span either contains only a single interpolation (and no other content), or no interpolation at all
[ ] Content of any type must be defanged before conversion to render spans
[ ] The renderer must not allow non-defanged content through (and thus semantic spans and render spans must be different)
[ ] String markup syntax should make it difficult to make mistakes that break the above
[ ] All of the above should be codified as part of a Coding Standards doc (see https://github.com/japhb/Terminal-Widgets/issues/10)

Sketch of new text content model that addresses several of this issue's tasks: https://github.com/japhb/Terminal-Widgets/blob/main/lib/Terminal/Widgets/TextContent.rakumod .  This still needs to be tied into the rest of the codebase before those tasks can be considered complete.

Did a pile more work on the new TextContent model, but can't push yet because I'm finding some downstream issues that I need to clear up first.  Still, progress continues.

A bunch more work done on this one today.  I was able to push at least, but I'm still not ready to make a release based on it -- it's going to require some minor compat-breaking, and I'd rather get it closer to right than break compat two releases in a row if I can avoid it.


Fix false positive for Naming/BlockForwarding

This change fixes a false positive for Naming/BlockForwarding with anonymous style, in the case where the method body just consists of the block argument, like so:
def foo(&block)
  block
end

The actual change simply replaces each_descendent with each_node. This works because the method body in the problematic case consists just of the lvar node that should prevent an offense from being registered.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!

Thanks @koic


FileContext.rename does not always throw FileAlreadyExistsException

FileSystem.rename(HDFSLogStore) can also throw IOException when the destination File already exists:
https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/FileSystem.java#L1594
So we can not handle this when in OptimisticTransaction.doCommit to checkAndRetry
https://github.com/delta-io/delta/blob/778cc6923bb3985122062f7ce4af4cd58a15f849/src/main/scala/org/apache/spark/sql/delta/OptimisticTransaction.scala#L397
We should use the same logic in HadoopFileSystemLogStore.writeWithRename
https://github.com/delta-io/delta/blob/778cc6923bb3985122062f7ce4af4cd58a15f849/src/main/scala/org/apache/spark/sql/delta/storage/HadoopFileSystemLogStore.scala#L103-L107
If I missing something, please correct me, thanks!

HDFSLogStore uses the new FileContext implementation for HDFS, not the FileSystem implementation.

HDFSLogStore uses the new FileContext implementation for HDFS, not the FileSystem implementation.

Yes, but in FileContext ,it also call FileSystem.rename by DelegateToFileSystem.renameInternal
https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/DelegateToFileSystem.java#L206

Maybe I am misunderstanding something. As far as I understand,

the default AbstractFileSystem implementation (FileContext delegates to AbstractFileSystem) used for hdfs scheme is org.apache.hadoop.fs.Hdfs as shown in the default conf file for conf fs.AbstractFileSystem.hdfs.impl.

HDFSLogStore calls FileContext.rename(... Options.Rename.OVERWRITE) which calls AbstractFileSystem.rename(...).

AbstractFileSystem.rename(...) always delegates to AbstractFileSystem.renameInternal(...) which is overridden by org.apache.hadoop.fs.Hdfs to call DFSClient.rename().

DFSClient.rename(...) can only throw only a few types of exceptions of which FileAlreadyExists is only type of exception that is concretely worth retrying.

Am I missing something in this tracing of the call?

@windpiger do you have any other concerns about this?

@windpiger do you have any other concerns about this?
no ,thanks very much!!


chore(main): release 1.3.0

:robot: I have created a release beep boop
1.3.0 (2024-07-09)
Features

c3: temperature step as customize (#209) (4da6e3e)

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

New Features

Added functionality to customize the temperature step.

Version Update

Updated application version from 1.2.0 to 1.3.0.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 30.35%. Comparing base (4da6e3e) to head (d8cc05c).

Files
Patch %
Lines

midealocal/version.py
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #211   +/-   ##
=======================================
  Coverage   30.35%   30.35%
=======================================
  Files          79       79
  Lines        6911     6911
=======================================
  Hits         2098     2098
  Misses       4813     4813

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

:robot: Created releases:

v1.3.0
:sunflower:


[MISC] Adding qMRI BIDS article reference (BEP001)

Dear BIDS maintainers,
I am glad to announce that our article for BEP001 has been published in Scientific Data.
This PR is to add this article to the list of references.
Thank you for your great support to make this possible.

Thanks for adding this @agahkarakuzu


Use Readme.md in library home doc

They should contain almost identical information, so it's better to update the readme and obtain the same updated in the doc home page using: #![doc = include_str!("../README.md")]

done in https://github.com/RCasatta/bitcoin_slices/commit/12e84d862249d6860eb0a100a7c976425f2908b5


lzma: make decompression optional

Logs a warning if LZMA is disabled and we encounter it
Disabling it can be done by calling htp_config_set_lzma_memlimit with a 0 limit
Modifies #255 by fixing compilation

Merged after rebasing. Thanks!


nuxt kit not up to date, cannot auto import useColorMode()

Version
@nuxtjs/color-mode: 3.1.8
nuxt: 3.0.0
Reproduction Link

Steps to reproduce
Try to autoimport useColorMode in any composable or component
What is Expected?
It should be imported
What is actually happening?
IDE warns that it is not defined. And a page calling useColorMode will throw an error
Why
in @nuxt/kit rc9, it adds autoimport using autoImports:extend which is deprecated
Can this be exported by the package ? We would be able to import it manually using
import { useColorMode } from "@nuxtjs/color-mode"

@Atinux https://github.com/nuxt-modules/color-mode/pull/161 would resolve this issue

give it a go with v3.2.0 and let me know if it's resolved for you.

solved with 3.2.0 ❤


This error keeps popping up when i try to run your NLI_evaluation

Traceback (most recent call last):
File "NLI.py", line 2, in
from NLI_models import *
File "/content/drive/My Drive/logicnlg/NLI_models.py", line 6, in
from allennlp.nn import util
ModuleNotFoundError: No module named 'allennlp'
I am running on google colab using the command,
CUDA_VISIBLE_DEVICES=0 python NLI.py --model bert-base-multilingual-uncased --do_verify --encoding gnn --load_from NLI_models/model_ep4.pt --fp16 --verify_file outputs/GPT_gpt2_C2F_13.35.json --verify_linking data/test_lm.json
Do i need to install allennlp seperately? and which version?

Sorry that I somehow missed this issue, which causes the late reply. The version that I used is "allennlp 0.9.0", I use the allennlp library to do some masking function. Sorry again for the late reply.


Load new PDFs

there are all new PDFs for the website. I am almost positive that they have the same file names as the current PDFs. They are all here: \Terra\GIS\projects\projects2012\USFWS_Update\util\docs\Final\website

There is a small chance that one of these PDFs will be updated next week. If it's easier for you to wait until all of the versions are completely final, please do.

I've copied them over. Please check that the expected updates are reflected and close the ticket.


Godot UI

Goal of this task is to create a UI that fits our game theme.

Dimosthenis took care of this issue


Is this package still alive?

Hey Guys,
just wanted to drop in and see if this package is still being worked on?

I believe it is, there is a lot of traffic on the email...
However, I followed this guide and implemented another way
https://blog.laravel.com/deploying-soketi-to-laravel-forge
On Tue, May 16, 2023 at 5:45 PM billy @.***> wrote:

Hey Guys,
just wanted to drop in and see if this package is still being worked on?
—
Reply to this email directly, view it on GitHub
https://github.com/beyondcode/laravel-websockets/issues/1124, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAWLV7F24AVWWBCLVJEHZVLXGOHJFANCNFSM6AAAAAAYDYREVY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

i already have it set up.
just wondering if it is still being maintained.

Sadly but no. No one check the issues anymore. just look here
https://github.com/beyondcode/laravel-websockets/issues/1122
And here, the last update was in oct last year https://github.com/beyondcode/laravel-websockets/discussions/1038#discussioncomment-3793477

Already abandoned

So bad


Fix(depth limit)/allow introspection

Codecov Report

Merging #112 (fed8bbe) into main (a0578bb) will decrease coverage by 0.50%.
The diff coverage is 50.00%.

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

@@             Coverage Diff             @@
##              main     #112      +/-   ##
===========================================
- Coverage   100.00%   99.50%   -0.50%
===========================================
  Files           15       15
  Lines          198      200       +2
  Branches        45       46       +1
===========================================
+ Hits           198      199       +1
- Misses           0        1       +1

Impacted Files
Coverage Δ

packages/plugins/max-depth/src/index.ts
96.77% <50.00%> (-3.23%)
:arrow_down:

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


fix body parser

This doesn't work.
server.use(function (req, res, next) {
  if (req.method === 'POST') {
    req.body.createdAt = Date.now()
  }
  // Continue to JSON Server router
  next()
})

The PR fixes is.
@typicode

Thank you :+1:


Don't select item on key down/up

Would be nice to have a setting to only select on pressing Enter, currently, when you press up/down arrows it changes the selection.

Thanks. It would be nice.
Modifying the behavior of SelectedItem seems difficult.
Instead, it may be easy to make a property to hold the committed item, and update the property by watching Enter/Click events.
This mechanism can be implemented outside the library by using attached dependency property. I will try when I feel like doing.

https://github.com/dotnet/wpf/issues/1044


use sqlalchemy 1.3.x for mautrix-telegram

Motivation for this change
The author seems to have no intentions of upgrading (source: https://github.com/tulir/mautrix-python/issues/46).
If they remove the feature that needs sqlalchemy, we can remove the 1.3.x version.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 127486 at 06e3c6b8 run on x86_64-linux 1

24 packages marked as broken and skipped:

cassandra_2_1
cassandra_2_2
gnuradio3_7
gnuradio3_7Packages.ais
gnuradio3_7Packages.gnuradio
gnuradio3_7Packages.gsm
gnuradio3_7Packages.limesdr
gnuradio3_7Packages.nacl
gnuradio3_7Packages.osmosdr
gnuradio3_7Packages.rds
hadoop
hadoop_2_7
hadoop_2_8
hadoop_2_9
impressive
linuxPackages_hardkernel_4_14.virtualbox
linuxPackages_hardkernel_latest.virtualbox
natron
ocropus
odpdown
opentsdb
pig
rainbowstream
spark

1 package failed to build:

python38Packages.pymatgen-lammps

1283 packages skipped due to time constraints:

DisnixWebService
R
abcl
adapta-gtk-theme
adoptopenjdk-icedtea-web
aiodnsbrute
alloy (alloy5)
alloy4
amidst
ansible (ansible_2_11 ,python38Packages.ansible-core)
...

127 packages built successfully:

acd-cli
anki
ankisyncd
clevercsv (python38Packages.clevercsv)
cum
graph-cli
jre8
liberation_ttf (liberation_ttf_v2)
mailman
mautrix-telegram
python38Packages.APScheduler
python38Packages.ColanderAlchemy
python38Packages.Quandl (python38Packages.quandl)
python38Packages.aiocontextvars
python38Packages.aioinflux
python38Packages.alembic
python38Packages.apptools
python38Packages.azure-core
python38Packages.azure-storage-blob
python38Packages.bkcharts
python38Packages.celery
python38Packages.dask
python38Packages.databases
python38Packages.factory_boy
python38Packages.flametree
python38Packages.flammkuchen
python38Packages.flask_sqlalchemy
python38Packages.fonttools
python38Packages.geoalchemy2
python38Packages.google-api-core
python38Packages.google-api-python-client
python38Packages.google-auth
python38Packages.google-auth-httplib2
python38Packages.google-auth-oauthlib
python38Packages.google-cloud-core
python38Packages.google-cloud-iam
python38Packages.google-cloud-kms
python38Packages.google-cloud-storage
python38Packages.google-cloud-testutils
python38Packages.google-resumable-media
python38Packages.gtts
python38Packages.httplib2
python38Packages.httpretty
python38Packages.huggingface-hub
python38Packages.influxdb
python38Packages.kombu
python38Packages.mailman
python38Packages.mailman-hyperkitty
python38Packages.marshmallow-sqlalchemy
python38Packages.mautrix (python38Packages.mautrix-appservice)
python38Packages.monty
python38Packages.msrest
python38Packages.oauth2client
python38Packages.orm
python38Packages.pandas
python38Packages.partd
python38Packages.pecan
python38Packages.phik
python38Packages.pyathena
python38Packages.pygtfs
python38Packages.pymatgen
python38Packages.pymysqlsa
python38Packages.pytest-randomly
python38Packages.pytest-regressions
python38Packages.python-telegram-bot
python38Packages.pytrends
python38Packages.seaborn
python38Packages.sqlalchemy (python38Packages.sqlalchemy_1_3)
python38Packages.sqlalchemy-citext
python38Packages.sqlalchemy-i18n
python38Packages.sqlalchemy-utils
python38Packages.sqlalchemy_1_4
python38Packages.sqlsoup
python38Packages.starlette
python38Packages.telethon-session-sqlalchemy
python38Packages.tld
python38Packages.tqdm
twine (python38Packages.twine)
python38Packages.vega_datasets
python38Packages.vidstab
python38Packages.yfinance
python39Packages.ColanderAlchemy
python39Packages.aiocontextvars
python39Packages.alembic
python39Packages.azure-core
python39Packages.azure-storage-blob
python39Packages.databases
python39Packages.factory_boy
python39Packages.flask_sqlalchemy
python39Packages.geoalchemy2
python39Packages.google-api-core
python39Packages.google-api-python-client
python39Packages.google-auth
python39Packages.google-auth-httplib2
python39Packages.google-auth-oauthlib
python39Packages.google-cloud-core
python39Packages.google-cloud-iam
python39Packages.google-cloud-kms
python39Packages.google-cloud-testutils
python39Packages.google-resumable-media
python39Packages.httplib2
python39Packages.httpretty
python39Packages.kombu
python39Packages.msrest
python39Packages.oauth2client
python39Packages.pymysqlsa
python39Packages.pytest-randomly
python39Packages.sqlalchemy (python39Packages.sqlalchemy_1_3)
python39Packages.sqlalchemy-citext
python39Packages.sqlalchemy-i18n
python39Packages.sqlalchemy-utils
python39Packages.sqlalchemy_1_4
python39Packages.sqlsoup
python39Packages.starlette
python39Packages.telethon-session-sqlalchemy
sourcehut.buildsrht
sourcehut.coresrht
sourcehut.dispatchsrht
sourcehut.hubsrht
sourcehut.listssrht
sourcehut.mansrht
sourcehut.metasrht
sourcehut.pastesrht
sourcehut.todosrht
truvari
vorta
yokadi

7 suggestions:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/servers/mautrix-telegram/default.nix:74:0:
   |
74 |     description = "A Matrix-Telegram hybrid puppeting/relaybot bridge";
   | ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/servers/mautrix-telegram/default.nix:24:15:
   |
24 |   patches = [ ./0001-Re-add-entrypoint.patch ./0002-Don-t-depend-on-pytest-runner.patch ];
   |               ^

warning: unused-argument
Unused argument: pytest_xdist.
Near pkgs/development/python-modules/sqlalchemy/1.3.nix:5:3:
  |
5 | , pytest_xdist
  |   ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/servers/mautrix-telegram/default.nix:24:46:
   |
24 |   patches = [ ./0001-Re-add-entrypoint.patch ./0002-Don-t-depend-on-pytest-runner.patch ];
   |                                              ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/sqlalchemy/1.4.nix:47:3:
   |
47 |   meta = with lib; {
   |   ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/development/python-modules/sqlalchemy/1.3.nix:40:3:
   |
40 |   meta = with lib; {
   |   ^

warning: unused-argument
Unused argument: pytest_xdist.
Near pkgs/development/python-modules/sqlalchemy/1.4.nix:12:3:
   |
12 | , pytest_xdist
   |   ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

This was not supposed to change the default version. Fixed that.


LIKE doesn't seem to support escaping SQL wildcards

A query like:
SELECT * FROM table WHERE col LIKE '%2\_2%'
gets translated to
SELECT * FROM table WHERE REGEXP_LIKE(col, '2\\.2')
Is this the right syntax for escaping SQL wildcards?
If so, this issue looks to be because likeToRegexpLike doesn't handle escaped wildcards.

@Jackie-Jiang @atris I've raised a fix for this - please review.

Good catch. Reviewing.


Adding in correlation metrics (continuing #1782)

Please complete the following checklist:

[x] I have read the guidelines in CONTRIBUTING.md.

[x] I have documented all public-facing changes in CHANGELOG.md.

[x] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied. It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[ ] This pull request does not include code, documentation, or other content derived from external source(s).

Note: REVIEWING.md may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.
This pull request implements the VLR and robust versions of it.  This continues from #1782

Hi @wasade it looks like I'm getting some odd checklist errors, thoughts?
flake8 skbio setup.py checklist.py
./checklist.py
./checklist.py:215: ChecklistWarning: File skbio/metadata/tests/test_intersection.py has IGNORE directive. Ignoring scikit-bio copyright header validation.
  ChecklistWarning)
Files non-conforming to standard headers as described in
http://scikit-bio.org/docs/latest/development/new_module.html:
    skbio/stats/composition.py

make: *** [Makefile:23: test] Error 1
Error: Process completed with exit code 2.

It looks like skbio/stats/composition.py has an issue with its header, maybe the removed whitespace? I don't know what checklist does -- if you can, recommend running it locally until the module passes

I'm no longer getting that error locally -- let's see what the CI says...

Hi @wasade I think this PR is going to need a lot more work - and I don't think I can squeeze this in the near future.
I recommend we push this in for the next iteration.  That will also buy us more time to look at the numerical issues with the robust_pairwise_vlr

Sounds good, thanks for confirming

ok, I'm seeing that some of the runs are passing -- but there are a bunch of errors due to filelock? I guess we'll wait until  #1858 is fixed before merging this in?

Just added the changelog. Thanks!

...conflicts :/

Hi @wasade it looks like the tests are now passing :)

@qiyunzhu @wasade want to merge? :)

@mortonjt Sounds good to me! I don't have the privilege to merge. @wasade you merge? Or grant me permission?


Update BRT for thumb condition

Recode condition column so that thumb conditions get renamed to dominant/non-dominant as appropriate

This looks like it should work! Good catch on the recoding on the internal trialwise condition column that comes in the BRT data, not on the handedness column (which will only have one value per subject, and should indeed only be used as the if-else test).


Support  _=Expr initializer for records

If several fields are to be assigned the same value, the following construction can be used:
#Name{Field1=Expr1,...,FieldK=ExprK, _=ExprL}

Omitted fields then get the value of evaluating ExprL instead of their default values. This feature is primarily intended to be > used to create patterns for ETS and Mnesia match functions.

This is not implemented in EIR:
stderr:    Compiling /Users/runner/work/lumen/otp/lib/common_test/src/ct_config.erl
error: unrecognized token
    ┌─ /Users/runner/work/lumen/otp/lib/common_test/src/ct_config.erl:301:19
    │
301 │                      config=File,_='_'}),
    │                                  ^ expected: "atom"

error: parsing failed

      Failed /Users/runner/work/lumen/otp/lib/common_test/src/ct_config.erl

Affects the following files in OTP:

lib/common_test/src/ct_config.erl
lib/common_test/src/ct_util.erl
lib/common_test/src/ct_util.erl

Per Dec 9 standup, @hansihe will check to see if this is resolved or not


terminal_check_solaris.go doesn't have a build tag and is breaking the build on AppEngine

https://github.com/sirupsen/logrus/blob/9b3cdde74fbe9443d704467498a7dcb61a79de9b/terminal_check_solaris.go#L1
I think this file should have a build tag like:
// +build solaris

similar to https://github.com/sirupsen/logrus/blob/9b3cdde74fbe9443d704467498a7dcb61a79de9b/terminal_check_unix.go#L1
I believe this is the reason logrus currently fails to build on AppEngine standard projects (where we can't use golang.org/x/sys/unix).

I don't fix it will fix the build break because the _<platform_name>.go is an implicit +<platform_name> build constraint.
You can try that fix anyway and we will see what happens.

Just curious how do you build for appengine ? Cross-compile from a linux host ?

@dgsb sorry, looks like my proposed fix wouldn't solve the problem, but bisecting led me to the real culprit that is also related to terminal: #943 , which moved terminal package into the root logrus package.
My AppEngine project imports the github.com/sirupsen/logrus package but not terminal. Before #943 my project deploys fine but once I check out past #943 I'm seeing this error:
2019/04/05 08:35:03 go-app-builder: Failed parsing input: parser: bad import "unsafe" in golang.org/x/sys/unix/affinity_linux.go

I'm not exactly familiar with the underlying implementation of AppEngine Go. The SDK actually bundles in a special go toolchain to build the binary. Any unsafe stuff (for example in golang.org/x/sys/unix, which is imported by various terminal_check*.go) can't be used on AppEngine. Previously things worked since the terminal package was separate and I never import it.


simpler sort ports

we recently introduced enforce_port_ordering flag but we already had the sort_ports flag with served for the same purpose
How about we use sort_ports only?
@tvt173

Yes, I still maintain the view that enforce_port_ordering should never be false. If we get rid of the flag and use only the "True" case in all the code, it will make things simpler.
To be clear though, they don't serve the same purpose. sort_ports specifies whether or not to sort ports on one side of the bundle to prevent routes from crossing, etc. enforce_port_ordering prevents the error where connections form between the wrong ports, creating essentially a different circuit than what was specified (assuming the intention is that ports 0,1,2,... of ports1 should connect to ports 0,1,2... of ports2). This is the issue detailed here: https://github.com/gdsfactory/gdsfactory/issues/1992
Currently if enforce_port_ordering is set to False, it is saying instead "connect ports 0,1,2,... of ports1 to any one of ports 0,1,2... of ports2".

I see, I closed the PR
how about naming it keep_port_order ?

how about something like swappable_ports? I think this is common term in LVS for example. you can specify that pins are swappable, which is basically the same concept as here.
in this case, however, the boolean would need to be flipped. swappable_ports = True would be equivalent to enforce_port_order = False


Undocumented feature: Multiple buttons in same swipe

In the example picture in the readme it is possible to have two buttons revealed in one swipe ("Right 1" and "Right 2"). However, after looking through the documentation I do not see how this is accomplished. If someone could provide example code that would be much appreciated!

Hey @nferrara100 if you have a look at the example in example.js you can see how that is achieved with some sample code. See here for the 2 buttons in the hidden row: https://github.com/jemise111/react-native-swipe-list-view/blob/master/SwipeListExample/example.js#L124
Thanks!


[AutoPR datafactory/resource-manager] [Datafactory] DatabricksSparkJarActivity, DatabricksSparkPythonActivity and other D…

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3391

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2293


Automate ci running of vttest Test of screen features

Description

TestMain runs GUI unit tests funcs received from channel in main goroutine
Running of vttest "Test Screen Features" test

Related to #160
Type of change
Please delete options that are not relevant.

[ ] New feature (non-breaking change which adds functionality)

@liamg changes rebased, thanks


error

MacBook-Pro-de-Renzo:samples Mac$
MacBook-Pro-de-Renzo:samples Mac$ python hello-world-bot.py "/Users/Mac/PycharmProjects/btcetest2/btce-keys.txt" 4.0 4.1
Traceback (most recent call last):
File "hello-world-bot.py", line 141, in
run(args.key_file, args.buy_floor, args.sell_ceiling, args.live_trades)
File "hello-world-bot.py", line 92, in run
handler = btceapi.KeyHandler(key_file)
File "build/bdist.macosx-10.6-intel/egg/btceapi/keyhandler.py", line 111, in init
File "build/bdist.macosx-10.6-intel/egg/btceapi/keyhandler.py", line 48, in init
File "build/bdist.macosx-10.6-intel/egg/btceapi/keyhandler.py", line 115, in _loadKeys
File "build/bdist.macosx-10.6-intel/egg/btceapi/keyhandler.py", line 133, in _parse
ValueError: invalid literal for int() with base 10: ''
MacBook-Pro-de-Renzo:samples Mac$
i don't know what is wrong

It looks like your btce-keys.txt file is missing the initial nonce value for the last key in the file.  Each key should have three lines in  that file: the key, the secret, and a nonce value.  So it should look something like this:

GZGQE3IY-8WHYJANV-S5DSYB5Z-BERG3J79-8K8NSSP6
a034b00c827a84400956d697a7da0a216cb6cde9818ccf5346b3e0979a34fdfa
1

I should add: if you've never used the API key before, a nonce value of 1 should be fine.
Also, thanks for mentioning this, because I hadn't noticed that step 8 in the documentation here didn't show three lines; the nonce was included on the second line and was easy to miss.

/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/btce_api-0.3.1-py2.7.egg/btceapi/trade.py:180: UserWarning: The nonce in the key file is out of date; attempting to correct.
i use the key before.

You will have to choose a nonce value that is larger than any you've used before.  Because there is no way to ask the API what the next nonce should be, you can either just try larger numbers until it works, or create a new set of keys and then use 1 as the nonce (which is probably easier if you've used the key a lot).


whats wrong with line 16 on pot_step.py

import RPi.GPIO as GPIO
import time, math
C = 0.33 # uF
R1 = 1000 # Ohms
GPIO.setmode(GPIO.BCM)
Pin a charges the capacitor through a fixed 1k resistor and the thermistor in series
pin b discharges the capacitor through a fixed 1k resistor
a_pin = 18
b_pin = 23
empty the capacitor ready to start filling it up
def discharge():
GPIO.setup(a_pin, GPIO.IN)
GPIO.setup(b_pin, GPIO.OUT)
GPIO.output(b_pin, False)
time.sleep(0.1)
return the time taken (uS) for the voltage on the capacitor to count as a digital input HIGH
than means around 1.65V
def charge_time():
GPIO.setup(b_pin, GPIO.IN)
GPIO.setup(a_pin, GPIO.OUT)
GPIO.output(a_pin, True)
t1 = time.time()
while not GPIO.input(b_pin):
pass
t2 = time.time()
return (t2 - t1) * 1000000
Take an analog reading as the time taken to charge after first discharging the capacitor
def analog_read():
discharge()
t = charge_time()
discharge()
return t
Convert the time taken to charge the cpacitor into a value of resistance
To reduce errors, do it 100 times and take the average.
def read_resistance():
n = 10
total = 0;
for i in range(1, n):
total = total + analog_read()
t = total / float(n)
T = t * 0.632 * 3.3
r = (T / C) - R1
return r
try:
while True:
print(read_resistance())
time.sleep(0.5)
finally:
GPIO.cleanup()

Warning (from warnings module):
File "/home/hackertalkz/Desktop/pot_step.py", line 18
GPIO.setup(a_pin, GPIO.IN)
RuntimeWarning: This channel is already in use, continuing anyway.  Use GPIO.setwarnings(False) to disable warnings.

I've seen that message before when the script doesn't clean up after itself. The last line of that file, GPIO.cleanup(), should take care of it though.
It's possible the script died unexpectedly, such as killing it with ctrl+c, and it didn't get a chance to run that last line.


Failing to include packages when starting a project with the CUDA Toolkit project template

I am using Windows 10 and VS2017 (version 15.6.0). Also, I installed CUDA toolkit (9.1).
I started a new project using the CUDA 9.1 template (from CUDA Toolkit). Then, I installed freeglut.
The integration with VS2017 is working when using VC++ templates. But it is not working with CUDA 9.1 template. When I try to include GL/freeglut.h, it is not available.
I know it is problem something basic. But, I have no ideia how to get it working.

Hi @ElemarJR, here is documentation.
And if you want to use static library, this documentation will answer your question.
Thanks.


Fix throwing on invalid fingerprints

This makes tests pass on current Node.js versions.
The test in question is https://github.com/joyent/node-sshpk/blob/v1.14.0/test/fingerprint.js#L117-L120 — it fails on Node.js 8 and 9 without this patch.
This is alternative approach to #41 (which just changes the test for some reason).

Codecov Report

Merging #47 into master will decrease coverage by 0.12%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
- Coverage   86.16%   86.04%   -0.13%
==========================================
  Files          24       24
  Lines        3680     3682       +2
==========================================
- Hits         3171     3168       -3
- Misses        509      514       +5

Impacted Files
Coverage Δ

lib/fingerprint.js
79.16% <100%> (-4.88%)
:arrow_down:

lib/signature.js
88.4% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6edb37c...2bef475. Read the comment docs.

Fixed in fe7c161a8efb2a89438af346b9508395fad23d81.


[Bug Report]  YOUTUBE LIVE does not play properly

Uses Google Translate.
Describe the bug
No sound comes out when playing YouTube Live.
If you use the "nowplaying" command, the song name will be displayed.
There are no errors on the console.

I’ve been experiencing this problem for a while now too, but I just tried it again and it seems to be working now c:

Closing stale & already fixed issue. If it happens again, open a new issue.


Sort map pool maps by display name

Fixes #2178

This does sort on all the results because for the map pools we have to get and combine them all then the pagination is done locally on the return line of the function

Oh so we are just faking a page result. Hmm. Weird.

Yes it is done that way currently just because we dont show the individual rating pools and instead show them all which we can't paginate from the api.


Homebrew warnings stop script from running

We had a homebrew warning around not having latest Xcode.

Ensuring you have a healthy Homebrew environment...
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
Warning: Your Xcode (7.3) is outdated
Please update to Xcode 7.3.1.
Xcode can be updated from the App Store.

The script stops running, even though there are no Xcode updates available for us in the App Store. It would be great to have an option to continue in spite of the warning.

Is xcode even needed?  We were setting up a new client machine where we saw
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
We resolved it by preventing the scripts/xcode-license.sh script from being called, and saw no issues/errors from installation

We also saw a similar issue; our solution was to comment out brew doctor

Maybe we don't need command line tools installed anymore.
Which script are you running? It's possible that the labs-engineer script needs those to be installed but that the other scripts don't. If so we should move it out of the shared code.

We were running the engineer one in my comment
On Nov 28, 2016 5:13 PM, "Grant Hutchins"<EMAIL_ADDRESS>wrote:

Maybe we don't need command line tools installed anymore.
Which script are you running? It's possible that the labs-engineer script
needs those to be installed but that the other scripts don't. If so we
should move it out of the shared code.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pivotal/workstation-setup/issues/64#issuecomment-263411436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMCRQBXDYLAqkyF1HIQnNt27q4MvqPg5ks5rC1IdgaJpZM4I52S2
.

Maybe we don't need command line tools installed anymore.

The last time I checked, ruby and ruby gems needed Xcode command line
tools. Maybe for compiling code / libraries.


Fix typo and missing variable

Fixes the issue in #17

hi @Baspa thanks for your support.

Thank you for creating the packages :)


chore(key_repo): add key repo

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Return error codes according to the spec for token introspection

Following behavior should be corrected

NPE is logged for a bearer header with invalid access token and returns 200 [1]. The NPE can be prevented by doing a null check at [2]
Returns 403 for insufficient permission [3]

[1] - https://tools.ietf.org/html/rfc7662#page-8
[2] - https://github.com/wso2-extensions/identity-carbon-auth-rest/blob/master/components/org.wso2.carbon.identity.auth.service/src/main/java/org/wso2/carbon/identity/auth/service/handler/impl/OAuth2AccessTokenHandler.java#L91
[3] - https://tools.ietf.org/html/rfc6750#section-3

NPE fixed with https://github.com/wso2-extensions/identity-carbon-auth-rest/pull/55/files#diff-1645ea526ca2b20b7a5b87b47070b69eR91

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Working ac not in the list

Not really an issue just reporting a working ac.
AC model Daikin FTXL35J2V1B is working with code 1101. All modes are working and there is one temperature sensor reporting status.
Standard config as per manual. With homeassistant 0.117.1 and included broadlink integration.


Add pawn.json for sampctl version control

This is an early version for testing, and since the MySQL plugin is probably one of the most used I figured I'd use it as the first live plugin for testing.
The format shouldn't change so I shouldn't need to pull any changes again!

^mysql-.*-[Debian|CentOS].*$

Is this regex syntax? If yes, shouldn't these be parentheses instead of square brackets?
You should also add "Linux" to this, as my Debian releases are often meant for all other Linux distributions, so I probably will be doing only "CentOS" and "Linux" releases in the future.
And keep in mind that the CentOS and Linux releases differ slightly in the way the MySQL/MariaDB clients are linked (Linux is /usr/lib/libmysqlclient.so and CentOS is /usr/lib/mysql/libmysqlclient.so), thus people running for example Debian and using the CentOS release will probably encounter a "library not found" error on server start.

Ah, good catch yes those should be brackets.
And yeah the Centos thing is kind of an awkward situation for me. sampctl has a concept of operating systems but not individual distributions, I'm not sure if I want to introduce distribution checking into the tool. I always did wonder why there was a separate Centos release though, thanks for the clarification!
I'm going to try and figure out a good solution for this that doesn't rely too much on the package maintainer to add lots of special edge cases to their package definitions. I'm thinking of just allowing package consumers to specify a specific resource for their platform instead of trying to be clever and auto detecting it all.

I think it's okay to let package maintainers specify this by themselves. I doubt that sampctl users would want to take care of this (package name changes -> every user has to adjust his config file vs. package name changes -> maintainer has to update package name once).
Try using the static release:
^mysql-.+-([Dd]ebian[0-9]|[Ll]inux)-static.*$

That one should work on most distributions out of the box without any problems.

So the static release is actually just for any distro, not debian? That would simplify things a lot, thanks!

Yes, the static release has the MySQL/MariaDB client library statically linked (it's basically directly incorporated into the plugin file). This has the drawback that you can't use the latest client library distributed through your package manager, but I think that this is not really a huge concern for SA-MP server owners.


Use sass instead of node-sass

@ShynRou - it went surprisingly smooth and without style changes so take a look at it if it's ok. I went through the whole app and everything looks as it should (I also went through all of the .scss files and there are no errors or anything).

@JoeStorm99 - this will need thorough testing once @ShynRou and @creed-victor finish their review. You will need to go through the whole app if you don't find some broken styles (but only after their review).

@tiltom Build is not working anymore, you need to migrate some stuff, because of the different APIs of DartSass and LibSass.
Please also fix the deprecation warnings.

view build output
yarn run v1.22.10
$ node scripts/build.js
Creating an optimized production build...
DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($pt-grid-size * 1.8, $pt-font-size)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷
35 │ $pt-line-height: ($pt-grid-size * 1.8) / $pt-font-size + 0.0001 !default;
   │                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   ╵
<EMAIL_ADDRESS>35:18  @import
<EMAIL_ADDRESS>9:9            @import
    src/styles/sass/styles.scss 7:9                                  root stylesheet

DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($pt-grid-size, 3)

More info and automated migrator: https://sass-lang.com/d/slash-div

   ╷
47 │ $pt-border-radius: floor($pt-grid-size / 3) !default;
   │                          ^^^^^^^^^^^^^^^^^
   ╵
<EMAIL_ADDRESS>47:26  @import
<EMAIL_ADDRESS>9:9            @import
    src/styles/sass/styles.scss 7:9                                  root stylesheet

DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($pt-grid-size, 2)

More info and automated migrator: https://sass-lang.com/d/slash-div

    ╷
342 │     margin-right: $pt-grid-size / 2;
    │                   ^^^^^^^^^^^^^^^^^
    ╵
<EMAIL_ADDRESS>342:19  @import
<EMAIL_ADDRESS>13:9      @import
    src/styles/sass/styles.scss 7:9                             root stylesheet

DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($pt-grid-size, 2)

More info and automated migrator: https://sass-lang.com/d/slash-div

    ╷
411 │     margin-bottom: $pt-grid-size / 2;
    │                    ^^^^^^^^^^^^^^^^^
    ╵
<EMAIL_ADDRESS>411:20  @import
<EMAIL_ADDRESS>13:9      @import
    src/styles/sass/styles.scss 7:9                             root stylesheet

DEPRECATION WARNING: Using / for division is deprecated and will be removed in Dart Sass 2.0.0.

Recommendation: math.div($pt-grid-size, 2)

More info and automated migrator: https://sass-lang.com/d/slash-div

    ╷
417 │     margin-top: $pt-grid-size / 2;
    │                 ^^^^^^^^^^^^^^^^^
    ╵
<EMAIL_ADDRESS>417:17  @import
<EMAIL_ADDRESS>13:9      @import
    src/styles/sass/styles.scss 7:9                             root stylesheet

Failed to compile.

./src/styles/sass/styles.scss
SassError: (path: (fill: #5c7080)) isn't a valid CSS value.
   ╷
39 │       background: svg-icon("16px/chevron-right.svg", (path: (fill: $pt-icon-color)));
   │                                                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   ╵
<EMAIL_ADDRESS>39:54  @import
<EMAIL_ADDRESS>5:9                      @import
<EMAIL_ADDRESS>16:9                             @import
  src/styles/sass/styles.scss 7:9                                                    root stylesheet

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

We decided not to continue on this, see the comment - https://github.com/DistributedCollective/Sovryn-frontend/issues/1492


Publish on crates.io

It would be cool if this could be published on crates.io which is the common way to distribute dependencies for rust/cargo projects.
The old bindings by @code-disaster currently use the sokol name on crates.io, but they have expressed that they would be willing to transfer ownership https://github.com/floooh/sokol/issues/802#issuecomment-1474808163

I believe that in order to publish a new version of the same crate its version label in Cargo.toml indeed has to be semantically larger than the previous one in accordance with SemVer.
Simply incrementing the patch number would be valid. I don't know if there is a limit as to how large the patch number can become.
https://doc.rust-lang.org/cargo/reference/resolver.html

You could try to increment the version's patch level in Cargo.toml during binding generation. I don't think it's a good idea to auto-publish though. If that's even possible, or deemed ok by the Cargo people.

We could also update the sokol-rust github repo on each commit, but trigger crate.io releases 'manually' by pushing a version tag to to the sokol-rust repo whenever there's noteworthy changes or bug fixes (a bit of a hassle though and I don't really want to commit to semver versioning of the sokol headers - especially since each header would actually needs its own version number).
...alternatively: run a weekly or monthly CI job which just bumps the patch version number ;)


Trouble Pushing 1.1.0 to CocoaPods

CocoaPods 1.0.1 with Xcode 8 Beta 3 seems to be rebasing the git repository for some bizarre reason:
Davids-Air:swiftgraph dave$ pod trunk push SwiftGraph.podspec
Updating spec repo `master`

CocoaPods 1.1.0.beta.1 is available.
To update use: `sudo gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.1.0.beta.1

Validating podspec
 -> SwiftGraph (1.1.0)
    - ERROR | [iOS] unknown: Encountered an unknown error (Must be in the root of the repo (/Users/dave/.cocoapods/repos/master), instead in /Users/dave/Documents/Projects/SwiftGraph.) during validation.

[!] The spec did not pass validation, due to 1 error.

@davecom I think this is caused by a cocoapods bug where pod repo update changes your git remote for the repository.
Try git remote -v and removing the cocoapods specs repo as a remote if it exists (git remote remove)

@peterjenkins Thanks for the insight! I'll try this as well as using the latest CocoaPods (1.1.0 RC 2).

SwiftGraph 1.1.1 should now be live on CocoaPods.


Utility to draw regions of the world map

Includes an example developer plugin called "Map Test" to demonstrate how to use the map image functionality.
Example of drawing a 100 by 100 px image of Lumbridge at 100% zoom

Example of the developer example usage configuration

Shouldn't this be closed in favour of #2064 ?

Closed in favor of #2064


Keyboard Manager Crashes on Open

Microsoft PowerToys version
0.66.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
I opened the powertoys app,
Enabled keyboard manager
Then clicked "remap a key"
The popup window opens, then immediately closes.
Log files and error attached
Power Toys Error.txt
2023-01-15.txt
✔ Expected Behavior
Keyboard manager to open to allow remapping of keys.
❌ Actual Behavior
The popup window opens, then immediately closes.
Other Software
No response

Not able to repro this, going to close. Let us know if you see this again!


[Question] Update to android 34 or 35

Hi, I have an question about update android version
From August 31, 2024, if your target API level is not within 1 year of the latest Android release, you won't be able to update your app.

How to fix
Your highest non-compliant target API level is Android 13 (API level 33).

To ensure that you can continue to make updates to your app you must:

Update your app to target Android 14 (API level 34) or higher.
Publish a new version of your app to production. Before you do this, you can test your app using internal, closed, or open testing.

@jbroma can you help me to resolve this issue.

@doiya46 I can't really see how this is connected to super-app-showcase and I'll close this issue for now
My take on the issue is that all you need to do become compliant is to to upgrade react-native within your own app - or just bump the target API level within the host app.


Modify Velum workflow for Kubernetes external FQDN name

Velum will now have a new setup step after the roles have been chosen,
with the selected master as the kubernetes external FQDN name that will
contain its FQDN by default, allowing the customer to modify it to fit
their needs.
Fixes: bsc#1047284

Automation needs to be adapted as well as openQA tests. Will work through it after other PR's that I have pending.

Automation changes need to be adapted, that's why that test is failing, however with https://github.com/kubic-project/automation/pull/93 automation changes along with this change is green.

Automation has been adapted to this change: kubic-project/automation#93 and I could verify locally that the run is green.

me too

Merging with https://github.com/kubic-project/automation/pull/93 which is needed to pass the tests.


Update nanopb repo URL

@peplin ,
Thanks for your effort!
I find that you are in uber now, I tell you that today morning I get one car via uber app.
Thanks you again for improving our life and study again!

@peplin I think the build is failing b/c of this upgrade https://blog.travis-ci.com/2015-11-27-moving-to-a-more-elastic-future and nothing from the code. I noticed it last month when a build of a branch failed and I couldn't figure out why. Haven't had a chance to look into it more yet.

There we go, fixed the CI issue with this PR as well. It was a few things:

The protobuf library doesn't pin a version for its setuptools dependency, and since we ran pip with the "upgrade all packages to latest version if not pinned" option, it was trying to update pip while using it, and that must have made it unhappy.
Digilent moved all of their URLs around so I had to update the URL for the network shield libraries and agreement.
Digilent's SSL cert bundle also seems messed up so I've temporarily disabled SSL cert checking when we download dependencies. Yes, I know this is not cool :sunglasses:


(a) Make it more clear what language the coding window is in and (b) Not clear that 's' should be treated as a string.

I'm fine with (a), but let's get @rabidbit's opinion because I think we had something like this before and removed it when we realized that it was causing confusion due to our currently supporting only one language.
For (b), str is a keyword in Python. I actually think s is a reasonably standard name for a string, though we could also call it input_string if we wanted to be super explicit. But that's a bit clunky. @rabidbit do you have any suggestions for what to do here, or more clarification on the underlying problem?

Drop-down with only one language (whether or not other languages listed are disabled) is an undesirable UX because it only serves to note to the user our language limitation. This issue may go away if/when we support multi-lang for both server and stand-alone.
How about adding comments, like this?...
# Python version 2.7

def reverseWords(s):
    # This reverseWords method processes a string (s)

    return ""

@seanlip
Per #575 thread... OK, how about we do the below (keep info on input as a comment but add language name next to the Reset Code button)? It will be simple enough to change when we implement multi-lang. Re: having to add a comment for each question with specs on the input, that seems OK to me, since every question will be different and will use different input specs.

Yes, I'm fine with having the input specs comment be per-question.
In general I think the suggestion you have here works fine from a technical perspective. Not totally sure about UI though -- seems a bit weird to have different font sizes next to each other, and I don't know if more delineation between the bold text and the link next to it is needed. Might want to double-check quickly with Amy?

SGTM


reference links added

There were a few reference links missing in the VE theory which I now added.
Fixes #504
Type of change

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[x] Bug fix (non-breaking change which fixes an issue)

Key checklist

[x] Make sure you've run the pre-commit checks: $ pre-commit run -a
[ ] All tests pass: $ poetry run pytest

Further checks

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works
[x] Relevant documentation reviewed and updated

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.91%. Comparing base (c406599) to head (cdbe4bc).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #505   +/-   ##
========================================
  Coverage    94.91%   94.91%
========================================
  Files           70       70
  Lines         3857     3857
========================================
  Hits          3661     3661
  Misses         196      196

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


Create documentation for testing patterns and standards

Problem statement
As a team we need to standardize the way we write tests on the frontend. As we address troubles with testing, discrepancies in patterns used, what needs coverage / how much, etc. we should add them to a living document of testing patterns and standards.
What you need to know
Some key areas to focus on:

when we write unit vs integration vs e2e tests
mocking
coverage standards
...

Acceptance criteria

[ ] a complete document regarding RS frontend testing norms. Use this discussion notes doc as a guide where helpful. https://cdc.sharepoint.com/:w:/r/teams/USDSatCDC/Shared Documents/PRIME ReportStream/Team Documents/Experience Team/Engineering/Frontend Testing Guidelines - ReportStream Experience.docx?d=w52e9908d03264df59d337ca6e206a0d9&csf=1&web=1&e=o2cr6j

To do

[ ] Create a "testing-patterns-help.md" in front-end/docs
[ ] Create a "testing-requirements-help.md" in front-end/docs
[ ] Migrate information from sharepoint doc into md so it can live in our project (it should be non-sensitive information, needed by any contributor including open source)

@stephenkao Would love to sync and pair on this one!

@kevinhaube It'd be my pleasure! :)

I'm going to hijack this ticket to finalize the testing doc but also the "best practices" doc we've been discussing as a team.  I've update the estimation accordingly.


A format! like macro to create nvim_oxi::Strings

Currently, to create formatted nvim_oxi::Strings, we first need to create an std string, and then convert that to nvm_oxi::String. That's two allocations where ideally only one should be necessary. This is important for example when passing a large number of formatted strings to Buffer::set_lines.

I'd be happy to create a PR if you're open to merging it.

Yes, I'd merge a nvim_oxi::string! macro that produces nvim_oxi::Strings.

Great, I'll try to do it this weekend.


feat: refactor register interface to allow unregistering an updater

Adds tests to make sure the register interface works as expected
Adds an example to the tests on how one might register a new updater to scape older firmware since this library is ADR004 compliant and does not support webscraping

thanks


How to get facial landmarks？

In the demo codes, facial landmarks have already been extracted and saved as pkl files.
However, the algorithms used to get those landmarks are not mentioned in both papers and readme.
Could you please give some advices？thx

@KleinXin
I found you can run the  python -u demo_motion_sync.py
and it will create a folder named to your test image in animation_pose.yaml
e.g. if you run python -u demo_motion_sync.py  with no modify to the yaml
it will produce a "d" folder with all the .pkl files you need since the default image is named d.png

In this paper they extracted video landmark by MediaPipe.

thx


plyr 3.5.3 Encountered error fullscreen in mobile

I've just upgraded plyr 3.5.2  to plyr 3.5.3 for the project 102tube and have discovered a bug fullscreen in mobile error.
And this error causes from the Plyr JS Library when manually adding
padding-bottom: 216.533%
In div class: .plyr__video-wrapper, .plyr__video-embed
And the way I can fix that is to add to this CSS snippet
.plyr__video-wrapper, .plyr__video-embed {        padding-bottom: 56.25% !important; }
Video bug : https://www.youtube.com/watch?v=zS584wonJDk
If anybody is being like me or referencing Nhé, and am looking forward to plyr sharing fix this error because Plyr is an amazing library!

I've got a fix lined up for this. I can probably deploy later today or tomorrow.

Fixed in [v3.5.4](https://github.com/sampotts/plyr/releases/tag/v3.5.4) 👍

Fixed in v3.5.4 👍

Awesome! Please update readme file to use version 3.5.4.

Awesome! Please update readme file to use version 3.5.4.

Good point. That's supposed to be automated. Whoops 🤦♂


Adjust Paginator Number of Elements.

It over flows on mobile causing page side scrolling and a hidden page 2. Can this be set lower?

Hi @CarlJKashnier
Thanks for notifying us. We will check & update it.

Hi @CarlJKashnier
We have fixed it. Thanks.

Framework Version: 0.1.6

Fixed


which pytorch version do you use?

python tools/llama/generate.py \

--text "要转换的文本" \
--prompt-text "你的参考文本" \
--prompt-tokens "fake.npy" \
--checkpoint-path "checkpoints/text2semantic-400m-v0.2-4k.pth" \
--num-samples 2

Traceback (most recent call last):
File "xxx/fish-speech/tools/llama/generate.py", line 22, in
torch._inductor.config.fx_graph_cache = True  # Experimental feature to reduce compilation times, will be on by default in future
File "xxx/fish-speech/lib/python3.10/site-packages/torch/_dynamo/config_utils.py", line 72, in setattr
raise AttributeError(f"{self.name}.{name} does not exist")
AttributeError: torch._inductor.config.fx_graph_cache does not exist
which pytorch version do you use?

comment it seems to work

I will add some code to check if the inductor config exists.

Fixed.


Add OldFilmFilter

@finscn could you change randomValue to seed to match NoiseFIlter?

@bigtimebuddy , done.

@finscn this is an awesome filter. It is well designed and the options are great!


Functions which cast reference to pointer are not unsafe.

... it's the later usage of that pointer that's unsafe! 😄

cc @kngwyu - I just want to check you agree with me on this one? Best to have a reviewer other than me as it's changing "unsafe" code...

Thanks!


GNNs as surrogate models

Additionally to our projects regarding the surrogate models for modelling the spread of Covid 19 in one population, we want to introduce Graph Neural Nets (GNNs). GNNs are usefool tools for graph-like data.
We want to model the spread of Covid19 among all counties in Germany. The spatial information about the counties and its neighbors can be modelled by a Graph. We want to include the mobiliy between the counties.
The task of predicting the spread among 400 counties and condsidering the mobility between them is different and more complex that predicting for only one population. This is why we don't continue the previous work, but rather replicate the process. However, we skipped the step where we do not differentiate between age groups. (Maybe add that ?? )
GNNs with no damping  -> issue #850
grid search for GNNs --> issue #851
GNNs with dampings --> issue #852

@AgathaSchmidt Most of these tasks have already been started or even completed? Could you update the status on the right bar and link the branch to the particular issues (also on the right bar)?


Add a document describing our GitHub labels

Update the CONTRIBUTING doc to talk about help wanted and link to the labels doc

:+1:


Handle missing refresh tokens in the quickstarts

Significant changes to the logic around handling access tokens. Ensures that fetchAccessTokenWithRefreshToken() is only called when a refresh token is present, and falls back to requesting a new token when one isn't. Sets the prompt OAuth2 parameter to ensure that the user sees the select account and consent screens, to ensure a refresh token is returned.
Prototyping on the Calendar quickstart, and will replicate out to the others once approved.
Fixes #16.

@erickoledadevrel Let's follow up on this.

Updated the rest of the quickstarts, tested them each by hand. Made some small fixes to the Apps Script quickstart, since the curly braces in the strings were being interpreted as variables.


Add support for expanding volumes

Checklist before merging:

[ ] Make any changes needed for the operator based deployment.
[ ] Documentation: Has documentation been added for new functionality? Does any existing documentation need to be updated or removed?

Update documentation to indicate support for volume expansion, emphasizing this is essentially a no-op as far as the driver and BeeGFS are concerned.

[ ] Tests: Is there adequate test coverage for new functionality? Do any existing tests need to be updated?
[ ] Dependencies: Does this PR rely on any changes to dependencies? If so has the go.mod or equivalent been updated to point at a version that contains the related changes?
[ ] Git Hygiene: Is the commit history squashed down reasonably?

Which issue(s) does this PR address?
Resolves https://github.com/ThinkParQ/beegfs-csi-driver/issues/29
Does this PR depend on any other PRs to be merged first?
No
What does this PR do / why do we need it?
While currently volume "capacity" has no meaning as far as the driver is concerned, some\ applications rely on the capacity of the PV/PVC in the K8s API to make certain decisions. For these applications it is helpful to support volume resizing.
Are there any specific topics we should discuss before merging?

Are there any downsides to enabling this behavior?
Does adding support for expanding volumes now have any implications in the future if volume capacity has meaning (i.e., the driver/BeeGFS begin enforcing the requested capacity)?

Looks about right to me. I was thinking the ControllerExpandVolume call should at least check whether the entirety of the BeeGFS file system was big enough to handle the requested capacity, but it looks like CreateVolume doesn't do this either. That check should be introduced in both locations simultaneously if it ever is.

Thanks for the review! I also considered a check to verify the available/total capacity was less than the requested capacity, but since there is currently never any checking around capacity I thought it better not to. Agreed if this is added it should be done universally.
By the way, after reviewing the first test failure I realized even though this is a no-op, we must still check we got a valid volume ID so I fixed that and also set CapControllerExpansion: true in the test driver setup. Last piece is to make all this work with the operator based deployment (which seems to be the reason tests are failing now). Will try and carve out some time later this week to wrap that up.

It took a little longer than I intended to get back to this, but volume expansion now works when the driver is deployed using the operator. If you have time, would definitely welcome a second set of eyes on those changes!

Looks like I can't resolve the conversations, but the answers are good. Feel free to resolve them and merge when convenient.

Looks like I can't resolve the conversations, but the answers are good. Feel free to resolve them and merge when convenient.

Good to know, I went ahead and invited your as a collaborator for next time :) Thanks again!


Issue fixes for 0.12

Description
SP and SPT fixes for TF 0.12
Issues Resolved
#238
#267
#268
Check List

[ ] New functionality includes testing.

[ ]  All tests pass for go 1.11 + gofmt checks.

[ ] New functionality has been documented in the README if applicable.

[ ] New functionality has been thoroughly documented in the examples (please include helpful comments).
[ ] New endpoints supported are updated in the endpoints-support.md file.

[ ] Changes are documented in the CHANGELOG.

I did some early testing on this branch against TF12 and it worked without any issue!  This is gonna be awesome!  Thank you guys!


CPU可以训练这个模型吗？

老师，作者你们好，我想用笔记本电脑的cpu试着运行一下训练的代码。结果报错，错误如下：
(YOLOP) csn@dominant-yoga-4:~/Project/VScode/python/YOLOP$ python tools/train.py
=> creating runs/BddDataset/_2022-11-22-16-42
Namespace(conf_thres=0.001, dataDir='', iou_thres=0.6, local_rank=-1, logDir='runs/', modelDir='', prevModelDir='', sync_bn=False)
AUTO_RESUME: False
CUDNN:
BENCHMARK: True
DETERMINISTIC: False
ENABLED: True
DATASET:
COLOR_RGB: False
DATAROOT: /home/csn/Dataset/BDD/BDD100K/images
DATASET: BddDataset
DATA_FORMAT: jpg
FLIP: True
HSV_H: 0.015
HSV_S: 0.7
HSV_V: 0.4
LABELROOT: /home/csn/Dataset/BDD/BDD100K/det_annotations
LANEROOT: /home/csn/Dataset/BDD/BDD100K/ll_seg_annotations
MASKROOT: /home/csn/Dataset/BDD/BDD100K/da_seg_annotations
ORG_IMG_SIZE: [720, 1280]
ROT_FACTOR: 10
SCALE_FACTOR: 0.25
SELECT_DATA: False
SHEAR: 0.0
TEST_SET: val
TRAIN_SET: train
TRANSLATE: 0.1
DEBUG: False
GPUS: (0, 1)
LOG_DIR: runs/
LOSS:
BOX_GAIN: 0.05
CLS_GAIN: 0.5
CLS_POS_WEIGHT: 1.0
DA_SEG_GAIN: 0.2
FL_GAMMA: 0.0
LL_IOU_GAIN: 0.2
LL_SEG_GAIN: 0.2
LOSS_NAME:
MULTI_HEAD_LAMBDA: None
OBJ_GAIN: 1.0
OBJ_POS_WEIGHT: 1.0
SEG_POS_WEIGHT: 1.0
MODEL:
EXTRA:
HEADS_NAME: ['']
IMAGE_SIZE: [640, 640]
NAME:
PRETRAINED:
PRETRAINED_DET:
STRU_WITHSHARE: False
NEED_AUTOANCHOR: False
PIN_MEMORY: False
PRINT_FREQ: 20
TEST:
BATCH_SIZE_PER_GPU: 24
MODEL_FILE:
NMS_CONF_THRESHOLD: 0.001
NMS_IOU_THRESHOLD: 0.6
PLOTS: True
SAVE_JSON: False
SAVE_TXT: False
TRAIN:
ANCHOR_THRESHOLD: 4.0
BATCH_SIZE_PER_GPU: 24
BEGIN_EPOCH: 0
DET_ONLY: False
DRIVABLE_ONLY: True
ENC_DET_ONLY: False
ENC_SEG_ONLY: False
END_EPOCH: 240
GAMMA1: 0.99
GAMMA2: 0.0
IOU_THRESHOLD: 0.2
LANE_ONLY: False
LR0: 0.001
LRF: 0.2
MOMENTUM: 0.937
NESTEROV: True
OPTIMIZER: adam
PLOT: True
SEG_ONLY: False
SHUFFLE: True
VAL_FREQ: 1
WARMUP_BIASE_LR: 0.1
WARMUP_EPOCHS: 3.0
WARMUP_MOMENTUM: 0.8
WD: 0.0005
WORKERS: 8
num_seg_class: 2
begin to bulid up model...
/home/csn/anaconda3/envs/YOLOP/lib/python3.7/site-packages/torch/cuda/init.py:52: UserWarning: CUDA initialization: Found no NVIDIA driver on your system.
Killed
请问如何解决这个问题。

已经解决该问题，原因是bach_size太大了，调小一些就好。


Updated title

Update from test

You should delete your api keys and regenerate them since you accidentally posted them here. Be careful not  to commit your .env with live data to your repository.


copying with wrapper_fn

Is there a reason why the copy call here is necessary when wrapper_fn is not None?  It seems like it's just for safety; if so is it possible to remove or add a kwarg to remove?

Hey @ahalev Thanks for the question! It is not needed, it was added for safety, because one of the most frequent ways people would use wrapper_fn is to pass something like torch.tensor or similar there, which would result in a warning because the underlying numpy array (which is a section of the memory map on disk) is not writeable.
I'm guessing your concerns are about performance?
Your suggestion sounds reasonable, people should be able to opt-out of the copy if they are going to only read the array.

@ahalev
I just released a new version v0.7.0, which contains such an option for both Wrapped and RaggedMmap classes. The option is called copy_before_wrapper_fn, it is documented here:
http://microlib.org/mmap_ninja/#open-an-existing-raggedmmap
By default it keeps the current behavior, as otherwise a lot of users would suddenly get a ton of warnings.

Yes it's about performance, there's a lot of overhead in this copy call. That should do it though! It is a little unclear in e.g. the torch documentation what operations are in place so I agree removing it entirely is not a good idea.


Fixed Delta Time potentially not working right

Problem
Currently, in slower pcs, the simulation seems to explode, stability is really poor and the objects go through each other. On another hand, on fast pcs, all movement looks faster. This seems to indicate that the fixed delta time has an issue, and is not executing the systems a fixed number of times per second. We should further investigate this.
Note: for more robust testing we might need a way to fix the framerate to a certain number

I think if you have movement based on a time delta based on the clock you will always have collision problems (at least if collision is just checking if two boxes are intersecting) because there's no upper limit to the distance covered in a single tick.
If you base distance covered on frames instead of time delta, the collision problems should stop varying with performance right?
And if you try to "fix the framerate" the movement should be less variable with performance (movement will be even worse for computers that can't handle that framerate but otherwise it should be the same)

I think if you have movement based on a time delta based on the clock you will always have collision problems (at least if collision is just checking if two boxes are intersecting) because there's no upper limit to the distance covered in a single tick.
If you base distance covered on frames instead of time delta, the collision problems should stop varying with performance right? And if you try to "fix the framerate" the movement should be less variable with performance (movement will be even worse for computers that can't handle that framerate but otherwise it should be the same)

In theory, we have movement based on a 'fixed delta time', which means all simulation steps use the same exact delta time. So that should not be a problem.
The way it is implemented is pretty much the standard way to approach it, which is:

each 'graphics frame':

you add time that passed since the last frame to an accumulator.
as long as accumulator > physics fixed delta time

accumulator -= physics fixed delta time
update physics and collisions

draw stuff

Maybe some of the physics systems are not repeating correctly and thus we get the weird behavior, but i'm not sure

Exactly, at the moment the physics simulation is set to run at 30 fps.
What should happen is on PCs where the game runs at 60fps on the 'graphics frame' we should have 1 physics update every 2 frames so we get 30fps, this is the easy part, and should be working although it seems like it doesn't in some ocasions.
When the framerate is lower than 30, we should execute multiple physics updates in one frame, which is counter intuitive since if the PC is slower it's going to get stuck doing this infinitely, since we don't have a failsafe yet. This is why our current target is a conservative 30 updates per second, it can handle it dropping a couple of times below that, but not for a long time. However, even like this, it always steps the same amount of time.
The current explosive behavior on lower frame rates, from my understanding, indicates an overcompensation which should only happen when the collision of objects is detected only when they already too much inside of each other, which shouldn't happen if the multiple updates per one frame part was working. If the problem lies exactly in this part, I'm not sure, but it's a good starting point, and it's good to make sure the fixed delta is working well.

I assigned myself to this issue, since I'm the one who added repeatWhile to systems :fearful:. If that is the problem this is gonna be more of core issue then.

I think it doesn't make sense for this to be an issue with the ECS: the only way, I think, for us to get the behavior we are getting, would be for different PCs to have somehow have different step times. If the problem was on the ECS, some PCs would run faster/slower, but with the same step. The step time should be fixed... is it possible there's some system which affects the physics simulation which is using the standard DeltaTime instead?


Use TerriaJS's regionmapping.json and regionids/ instead of TerriaMap's.

Fixes TerriaJS/TerriaJS#1227

We should synchronize the TerriaMap and TerriaJS copies as part of this, too.

We should synchronize the TerriaMap and TerriaJS copies as part of this, too.

Yes, that should be done, although it doesn't strictly have to be done at the same time, because everything will just keep working without it.

Closing in favour of #284 .


Adapt the CONCERT capsules

Adapt the concert capsules so that all robot parts are encapsulated.
Also add the drill as an optional end-effector.

By changing
<arg name="modular_description" default="$(find concert_examples)/concert_example.py"/> to <arg name="modular_description" default="$(find concert_examples)/concert_example_with_drill.py"/>
in concert_description/concert_gazebo/launch/concert.launch, the drill can be added. Rerunning the capsule generation script is enough for a capsule that is big enough:

With the new version of the script, the capsules also encapsulate the robot in the starting position perfectly. Only after moving, problems occur. Since that problem is already mentioned in #5, I will close this issue


In which IDE program do you make your projects?

IntelliJ IDEA ?
NetBeans ?

@ivmsflash
Not NetBeans.
I build mainly with gulp.
there are details to the following.
https://github.com/ykob/sketch-threejs/blob/master/package.json

vs code works


Polygon cannot be drawn on Safari

When 'allowSelfIntersection' parameter is set to false, the polygon cannot be drawn (on the screenshot). It's only reproducible on Safari. Also, we've found this only after we upgraded the react-leaflet to 3rd version.
https://codesandbox.io/s/elated-villani-q0gei?file=/src/map/MapWithGeoman.tsx

I think this has something to do with leaflet core: https://github.com/Leaflet/Leaflet/issues/7255
I tried it, on every click two vertexes are created and then it has a self intersection.
You can test this, when you click Remove Last Vertex then it is working until the next click.
Can you please try to use not the lastest Version of leaflet, try to use one of 1.6.x

I think this has something to do with leaflet core: https://github.com/Leaflet/Leaflet/issues/7255
I tried it, on every click two vertexes are created and then it has a self intersection.
You can test this, when you click Remove Last Vertex then it is working until the next click.
Can you please try to use not the lastest Version of leaflet, try to use one of 1.6.x

I tried 1.6.x and it worked as expected. I am gonna close this one and will track the leaflet core bug. Thanks 🤝

I tried 1.6.x and it worked as expected. I am gonna close this one and will track the leaflet core bug. Thanks 🤝


Updated proto definitions

Sorry, meant to open this PR against our own fork for now, please ignore :)


Site coin exploit

Modified by Two: Don't put exploits on GitHub Issues.

Hello a mee6 named guy came to my host and for free users there is only 2 slots available and they created 5 servers instantly and there is a way by which users can set their coins themselves and explain is above ↑

You literally put an exploit report on GitHub issues- (refer https://github.com/real2two/dashactyl/blob/main/SECURITY.md next time)
DM me a demonstration, since I don't really know what you mean.

Add a rate limit.


Problems minifying sass

Hi, i'm having some problems on minifying the sass in version 6.4 (tested in 6.4.2 and 6.4.3, with chrome on macOs)
They add this on styles (example below) and every div on hover they change the background. Besides that I had another problem with links. I've tried to comment some files to see the problem and they are in the files @include foundation-button-group; and @include foundation-button;.
:focus, :hover {
background-color: #cbcbcb;
color: #0a0a0a;
}
Anyone has this problem?
Best,
Hélio

When do you see this happening?
What series of steps do you take to replicate it?

Forget, I discover the problem, I was using LoaderOptionsPlugin on web pack but i discover that I need to minify the css on the css-loader with an option

Forget, I discover the problem, I was using LoaderOptionsPlugin on web pack but i discover that I need to minify the css on the css-loader with an option


Lack of removeEventListener in unmount event

As title, the eventListener would never be removed once added.

Added.
df238ef