Cats needs to be GPL v3.0 licensed to distribute mmd tools

mmd tools is licensed GPL v3.0 since Apr 5, 2020 https://github.com/UuuNyaa/blender_mmd_tools/blob/main/LICENSE, which is a copyleft license that requires that any works that include it in distribution to be under the same license. This means that Cats must also be licensed GPL v3.0 if it is to include any of mmd tools (or any other copied or modified GPL v3.0 code) in its distribution. However, Cats is currently MIT licensed, thus violating the copyleft aspect of the GPL v3.0 license.
There's also https://github.com/absolute-quantum/cats-blender-plugin/blob/master/tools/fbx_patch.py which is GPL v2.0 or newer and thus requires Cats to be GPL v2.0 or newer.
There shouldn't be any issues with changing Cats' license to GPL v3.0, since the existing MIT license is compatible with it. Similarly, distributing Immersive Scaler as GPL v3.0 with Cats would be fine too, since it's MIT licensed.
To quote wikipedia on GPL compatibility https://en.wikipedia.org/wiki/License_compatibility#GPL_compatibility

Many of the most common free-software licenses, especially the permissive licenses, such as the original MIT/X license, BSD licenses (in the three-clause and two-clause forms, though not the original four-clause form), MPL 2.0, and LGPL, are GPL-compatible. That is, their code can be combined with a program under the GPL without conflict, and the new combination would have the GPL applied to the whole (but the other license would not so apply).

Done and done!


netdata: remove judy from buildInputs as it is vendored by upstream

Description of changes
See https://github.com/netdata/netdata/pull/13362, unfortunately their decision to do so also breaks cross compilation.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 186554 run on x86_64-darwin 1

1 package marked as broken and skipped:

netdata

Also: maybe we should add broken = stdenv.buildPlatform != stdenv.hostPlatform, to bail out if cross-compiling?


burpsuite: Get a fully working embedded chromium

Describe the bug
Currently burp runs in a FHSEnv. This is good enough to get it opening and browsing the web in software mode. But features that rely on additional libraries such as hardware acceleration will not work. It's also prone to breaking as chrome changes as seen in (#350961).
We should investigate either providing the full list of chrome deps. This can be seen here. Or see if we can swap out the included chrome build with a reference to the chrome binary in nixpkgs.
This is complicated by the current nixpkgs burp derivation running burp just from the jar. This unpacks a copy of the chrome zip from inside the jar. But I'm unsure how or where to.
Steps To Reproduce
Using hardware acceleration as a test

Open burp.
Go to the Proxy tab and select Open browser
Visit chrome://gpu and observe hardware acceleration is disabled

Expected behavior
Hardware acceleration shows as enabled.
Notify maintainers
@bennofs

Add a :+1: reaction to issues you find important.

I might look at this when I have time, but probably won't be for a few weeks


RATIS-1303. Upgrade Ratis Thirdparty to 0.6.0

What changes were proposed in this pull request?
Upgrade ratis-thirdparty to recently released 0.6.0, because 0.6.0-SNAPSHOT is no longer in the repo.
https://issues.apache.org/jira/browse/RATIS-1303
How was this patch tested?
Compiled successfully:
https://github.com/adoroszlai/incubator-ratis/actions/runs/525010715

Thanks @elek for reviewing and merging this.  I just noticed that shaded.protobuf.version and shaded.grpc.version also need to be updated in Ratis to match Ratis Thirdparty: #413.

Thanks @elek for reviewing and merging this.  I just noticed that shaded.protobuf.version and shaded.grpc.version also need to be updated in Ratis to match Ratis Thirdparty: #413.


api - fix wrong post date

Post year always 1970
Example: for instagram user tuan
https://www.instagram.com/p/QmeU/?taken-by=tuan

Before fix:

After fix:

Thanks for your help :smile:

^^ you're welcome


PR: reducing reuse Verify service links

Resolution for issue #326
Before:

After:

@lizziebruce do we want to do this for the CT page as well?

@samuelculley we'll also reduce the reuse Verify service links on CT, but different links will be kept... discussion is in #471 @irinapencheva @sanjaypoyzer

@lizziebruce ah perfect, didn't spot that one


Cleanup leftover tarballs after playbook runs

Several tarballs are still left in /tmp
drwxr-xr-x 15 root    root       4096 May  6 10:25 cmake-3.11.4
-r--r-----  1 root    root    7955301 May  6 10:19 cmake-3.11.4.tar.gz
-rw-r--r--  1 root    root     235553 May  6 10:17 cuda_install_32499.log
-rw-r--r--  1 root    root    1370296 May  6 10:17 cuda-installer-32600
-rw-r--r--  1 root    root         88 May  6 10:17 cuda-installer-32767
drwxr-xr-x  2 root    root       4096 May  6 10:22 hsperfdata_root
drwxr-xr-x  9 jenkins jenkins    4096 May  6 10:14 make-4.1
-r--r-----  1 root    root    1878787 May  6 10:14 make-4.1.tar.gz

cleanup docker images
/ansible
remove ansible depedency
run yum clean all

@d3r3kk Has there been any progress on this?

Thanks @gdams for taking this over. I'd started it locally and then got stalled as I tried to whittle down the size even further.
The image size is still ~6Gb after your cleanup, so it will require further thought to get this down to a more reasonable size for Azure DevOps agents to make use of (the build-time limit on an Azure DevOps agent is ~10Gb).

@d3r3kk can you confirm what the largest files are on the machine still? I thought that removing cuda was going to save a few Gb


Use of  is problematic

Using <aside> for cards is problematic. <aside> semantics are for optional extras, and tooling may be inclined to skip it altogether, or suggest to users that they can just skip it and go on to something else.
<section><section> would be tolerable to indicate this, if you’re really averse to the class attribute. But class=card is quite warranted, I’d say.

I think that the styling here may look card-like, but semantically, these portions are still intended to be indirectly related to the main content. An aside doesn't necessarily imply that it's a sidebar or a call-out box. Remember this is MVP: it gets the job done, and in a nice way. I'd say stick with <aside> for now because it's semantically valid.

I'm inclined to agree w/ @philp on this one. I'd also like to stick to the "no classes" convention.
Here's Mozilla's take on <aside>: The HTML <aside> element represents a portion of a document whose content is only indirectly related to the document's main content. Asides are frequently presented as sidebars or call-out boxes.
I consider cards to be "call out boxes".
@chris-morgan What do you mean by "tooling may be inclined to skip it altogether", a screen reader?

These cards seem to me to be part of the main content, not supplementary content.
By tooling I mostly mean screen readers. Default configurations of screen readers won’t skip asides when going through the document in order, but some configurations may skip things like that especially when navigating by landmark.

OK, thanks for clarifying. I'm going to leave as-is for now, but open to revisiting in the future if there's a semantic way to designate a card without a CSS class.

So if aside is problematic and this project stands on "no class" convention, what about using role="grid" role="row" & role="cell" … ? https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/Row_Role (nice html summary example snippet)
Advantage is it's standardized, working with assistive technologies and its universal
but it also have disadvantages … it cannot be used on most elements (semantic elements) and it's a bit difficult to understand structure (maybe only for me).

The problematic part comes down to the cards should be using <article/> with possible <aside/> as a child, or adjacent like a side informational panel or advertisement.


add package by git url faces rate limits

let's clone the whole repo of the package instead

verified


app folder not working

git clone --recursive https://github.com/webdevops/php-docker-boilerplate.git projectname
etc...
docker-compose up -d
at http://<IP_ADDRESS>:8000/ I see empty Index Of /
app folder not working on my windows 10

Sorry but I have no access to a windows computer and don't know many people who use windows. I'm not sure if we have anybody who could help.

I would recommend setting up Windows Subsystem Linux with Docker for Windows and possibly use Docker-Sync as read/write permissions between windows folders and linux containers is an issue. I have done this setup for my windows machine and it performs quite well but your mileage may vary.
Nick Janetakis has a great blog post for setting this up:
Setting Up WSL with Docker


🧑💻 add extension settings

Current dependencies on/for this PR:

main

PR #13   👈

This comment was auto-generated by Graphite.


Added localized string for various texts in city overview

Changed fixed english strings to localized ones where it should not
conflict with line height.

I had completely neglected to consider localization when I accepted the PR for the amenities overhaul. Thank you for catching that and correcting it!

Might want to look what to do with localized texts over multiple lines, probably splitting and setting it in the function, was able to check (and understand) it in english and german, seemed fine for both. Apparently there's no localization for "Entertainment" though.


Closing the PubSub client does not cleanup grpc connection

Environment details

OS: MacOS 11.1 (20C69)
Node.js version: 14.15.3
npm version: 6.14.9
@google-cloud/pubsub version: 2.8.0

Steps to reproduce
I noticed the issue because jest complains about:

Jest did not exit one second after the test run has completed.
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to troubleshoot this issue.

But the issue can also be observed without a test runner:
import log from 'why-is-node-running'
import pubsub from '@google-cloud/pubsub';

(async () => {
  const client1 = new pubsub.PubSub({
    projectId: 'stub',
  });
  const [topic1] = await client1.createTopic('test');
  await topic1.delete();
  await client1.close();
  log();
})();

Output:
There are 10 handle(s) keeping the process running

# DNSCHANNEL
(unknown stack trace)

# TTYWRAP
/Users/michael/www/node_modules/supports-color/index.js:129 - stdout: getSupportLevel(process.stdout),

# SIGNALWRAP
/Users/michael/www/node_modules/supports-color/index.js:129 - stdout: getSupportLevel(process.stdout),

# TTYWRAP
/Users/michael/www/node_modules/supports-color/index.js:130 - stderr: getSupportLevel(process.stderr)

# Timeout
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/backoff-timeout.js:63 - this.timerId = setTimeout(() => {
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:189     - this.backoffTimeout.runOnce();
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:397     - this.startBackoff();
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:554     - if (!this.transitionToState([channel_1.ConnectivityState.IDLE], channel_1.ConnectivityState.CONNECTING)) {

# TCPWRAP
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:261 - return net.connect(this.subchannelAddress);
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:283 - const session = http2.connect(addressScheme + targetAuthority, connectionOptions);
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:361 - this.createSession(result);

# HTTP2SESSION
(unknown stack trace)

# Immediate
/Users/michael/www/node_modules/google-gax/build/src/call.js:70                    - setImmediate(this.callback, ...args);
/Users/michael/www/node_modules/google-gax/build/src/normalCalls/retries.js:82     - callback(null, response, next, rawResponse);
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/client.js:173              - callProperties.callback(null, responseMessage);
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:334 - (_b = listener === null || listener === void 0 ? void 0 : listener.onReceiveStatus) === null || _b === void 0 ? void 0 : _b.call(listener, status);

# TickObject
(unknown stack trace)

# TickObject
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:411     - process.nextTick(() => {
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:441     - this.transitionToState([
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:496     - this.checkBothRefcounts();
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel.js:500     - this.unref();
/Users/michael/www/node_modules/@grpc/grpc-js/build/src/subchannel-pool.js:56 - const refedSubchannels = subchannelObjArray.filter((value) => !value.subchannel.unrefIfOneRef());

while this works fine:
import log from 'why-is-node-running'
import pubsub from '@google-cloud/pubsub';

(async () => {
  const client1 = new pubsub.PubSub({
    projectId: 'stub',
  });
  /// nothing is done
  await client1.close();
  log();
})();

@michaelwittig Thanks for the report! This seems like it might be an issue with gax or grpc, looking at the list of handles, so I will defer to @alexander-fenster or @murgatroid99.

@michaelwittig Thanks for the report! This seems like it might be an issue with gax or grpc, looking at the list of handles, so I will defer to @alexander-fenster or @murgatroid99.

any other alternative way to solve this thing?

That output shows that there is a pending setImmediate and a couple of pending process.nextTick. Those would be resolved very soon after that. So, what is the output if you run the same thing a couple of seconds later?

If I await the close I expect the close to be done once the promise is resolved? and yes, I saw that thing close in the background.

grpc-js does not provide a way to wait for all resources to be released, so whatever that close function is doing, it isn't that.

Looks like Pub/Sub is calling close() on each gax client it has a handle on.

@michaelwittig Just to clarify, is the issue that the test doesn't exist fast enough, or that it never exits? It would be ideal for close() to actually wait for all resources to close out, but given how much of the stack it looks like that would have to touch, it's something we'd probably rather say "increase the jest timeout" for the moment. If it never exits, that's something we should probably look at sooner.

It's not only about jest (we only noticed it because of jest).
We have the same issue when we receive a SIGTERM from CloudRun. Our code listens to the signal and cleans up all resources (close db connections, close keep alive pools, ...). But, the pubsub client does not (at least within 10 seconds) do what it claims to do. Therefore, we get hard killed after 10 seconds by CloudRun.
My understanding of the problem: The resolved promise returned by close does not indicate that the close is done.
I still believe that is a bug.

I have published a new version of grpc-js that might help with this. Can you update your dependencies and try again?

@murgatroid99 thanks, I have tried with the latest (grpc-js 1.2.10), (pubsub 2.10.0), (google-gax 2.11.2)
one last timer remains
[WTF Node?] open handles:
- File descriptors: (note: stdio always exists)
  - fd 1 (tty) (stdio)
  - fd 2 (tty) (stdio)
- Timers:
  - (298065 ~ 4 min) (anonymous) @ /home/ttancos/test/node_modules/@grpc/grpc-js/build/src/channel.js:304
  - (2000 ~ 2 s) (anonymous) @ /home/ttancos/test/main.js:23

That timer is for a call to Channel#watchConnectivityState, which is generally called by Client#waitForReady. That intentionally keeps the process running, but it looks like there's supposed to be some special handling for calling that on a closed channel that currently isn't there. I can patch that, but there also isn't really a reason for it to be called at that point at all.

I was testing the shutdown code for my process and admittedly without consuming anything, just setup the subscription handlers, then calling close on interrupt to remove the handlers and let the remaining events run out and expecting that node will exit soon.
Thanks for the quick action, I've tried your patch locally and it behaves as expected, no more timers. :smile:

It sounds like we can close this, then? This patch looks like it went into a recent @grpc/grpc-js release, so anyone having the problem should be able to pull in the newest version of that.
Please feel free to ping if it needs reopening.


Mac OS?

It will be great if VideoCore will work in OS X too!

Any updates or pointers on how to get this going? thanks!

+1

This would be great, if we can get videocore working in mac os x el capitan and yosemite

+2


AnnotationSet should point to VariantSet instead of DataSet

Currently the structure makes it difficult to retrieve the variantSet since we must go all the way up to the DataSet and match (possibly more than one) the VariantSet:
record AnnotationSet {
  /** The ID of the annotation set record */
  string id;
  /** The ID of the dataset to which this annotation set belongs */
  string datasetId;

A simple change to a variantSet handle instead of a dataSet handle would improve the situation:
record AnnotationSet {
  /** The ID of the annotation set record */
  string id;
  /** The ID of the variantSet to which this annotation set belongs */
  string variantSetId;

I definitely disagree with changing it, though a variant set ID field could certainly be added to the annotation set provenance. It would not make sense in general for an annotation set to belong to a variant set.

Could you elaborate on why "it would not make sense"?
Everyone in today's call seemed to agree that it would be best to change it.

I assumed this was referring to the annotations branch which models arbitrary sequence annotations, e.g. Genes (which clearly won't necessarily 'belong to' a variant set). Could you link to a specific line to clarify?

Actually this refers to the "variant annotations" branch.
Apologies for the confusion, I should have clarified it in the title.

Changed the issue's title, I hope it is less confusing now.

in general, `AnnotationSet' is a confusing name.  I would encourage naming this VariantAnnotationSet.  Annotation is a very general term that means different things in different genomics contexts.

I'm OK with changing the name, but this should probably
be discussed as a separate issue...

Hi Pablo,
I've had a look at this, and querying for annotation across many variant
sets was the original intention.
The proposed change would make the use case of 'I'm interested in this
gene - what variants are in the region?' more tedious for the client.
You would need to issue multiple queries for each 1KG, ClinVar, ESP,
ExAC, etc VariantSet and filter through them all though the results from
each query would overlap heavily.
That said, the change gives the user a clearer idea of provenance/data
quality and fits better with the concept of a dataset as a container for
reads which can be submitted to different calling proceedures to make
different variant sets.
Out of interest - how does the backend you are planning relate to the
model? Is a VCF with annotation an annotation set?
On 20/10/2015 18:14, Pablo Cingolani wrote:

Currently the structure makes it difficult to retrieve the variantSet
since we must go all the way up to the DataSet and match (possibly
more than one) the VariantSet:
|record AnnotationSet { /** The ID of the annotation set record /
string id; /* The ID of the dataset to which this annotation set
belongs */ string datasetId; |
A simple change to a variantSet handle instead of a dataSet handle
would improve the situation:
|record AnnotationSet { /** The ID of the annotation set record /
string id; /* The ID of the variantSet to which this annotation set
belongs */ string variantSetId; |
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/schemas/issues/439.

We would still have access to dataSetId, it's just indirectly accesses using
VariantSet instead of directly accesses using AnnotatiaonSet:
AnnotationSet -> VariantSet -> DataSet

So the queries across variantSets within a dataSet can still be performed.
In the current schema, a Variant belongs to one and only one VariantSet. So
the case you mention would not be affected. E.g. if a variant (e.g. "chr1:1000_A/T")
is in all VariantSets (e.g. 1KG, dbSNp, ExAC, etc.), then you would need to represent
it as unique variants in each VariantSet (since each of them has a different
'variantSetId' field). Thus you would have to create a VariantAnnotation record
for each of them, despite the fact that they are exactly the same except for the
'variantId' field. This means that the case you mention would not differ at all
using this implementation (please correct me if I'm wrong or misunderstood
your case).
The reference server is backed by an annotated VCF file since we cannot
implement "on the fly annotations". Obviously this is a severe limitation on
what we can implement in the reference server.

@pcingola - I agree - it is cleaner even if it generates more searches as they will be more targetted and smaller.
A new filter by VariationSet when searching for annotation sets makes sense now too. I think the filter by Dataset is probably still useful  - what do you reckon?
I'll add these updates as a PR against our branch to give you the chance to review.

Great, thank you.

Was included in a later PR and now part of master:
https://github.com/ga4gh/schemas/blob/master/src/main/resources/avro/alleleAnnotations.avdl#L82


ToggleGroup

Almost identical to Radix:
https://www.radix-ui.com/docs/primitives/components/toggle-group
But instead of <ToggleGroup.Root> it should be <ToggleGroup>.
Requirements:

No using Radix libraries, Tamagui has equivalent libraries for most.
Add docs page to the site.
Simple tests would be appreciated.

I'd like to work on this one!

@glocore sounds good, open a draft PR that references this and we can consider it yours.

With some initial real progress

Hey @natew can I work on this.

@azeez1776 go for it I’ll reserve for you for next 48 hours. So long as you show decent progress within then it will be yours.

Thanks @natew , got it


Import backend api in main.py

In the reformat import api was never re-added, so the api wasn't working. Fixed with this commit

@IreTheKid need to wait for this to be reviewed (but it should be soon)

@IreTheKid need to wait for this to be reviewed (but it should be soon)

I can't work on my CSS 'till this is merged T~T

I can't work on my CSS 'till this is merged T~T

I can't work on my CSS 'till this is merged T~T

:(

I can't work on my CSS 'till this is merged T~T

:(


[CLI]: resume from step can only resume once

Describe the bug
Hi, I wanted to play around with the resume_from introduced in #7711.
For info, I am experimenting with this feature for cases of pre-emption. I checkpoint once per epoch but since I might get pre-empted in the middle of an epoch, I need to resume from the step of the checkpoint.
I tried to play around with a toy example. Let's say I have a batch size of 16 and 2 batches per epoch.
Here is my manual experiment.
import wandb

_id = "dummy_id_bananas"
batch_size=16
wandb.init(resume_from=f"{_id}?_step=0")

# First epoch
wandb.log({'bananas': 1}, step=batch_size)
wandb.log({'bananas': 2}, step=2*batch_size)

# Start of second epoch - we checkpoint
wandb.log({'bananas': 3}, step=3*batch_size)

# Pre-emption occurs.
wandb.finish()

# Job is relaunched, we resume from the start of the second epoch
wandb.init(resume_from=f"{_id}?_step={2*batch_size}")
wandb.log({'bananas': 6}, step=3*batch_size)
wandb.log({'bananas': 7}, step=4*batch_size)

# So far so good.
# First run was [1,2,3]
# Second run was: [1,2] (from save) + [6,7]
# We observe [1,2,6] in UI -> PROBLEM: Missing entry at step=64 for banana=7

# We start the third epoch
wandb.log({'bananas': 8}, step=5*batch_size)

# But we get pre-empted
wandb.finish()

# Third time relaunching. we relaunch at the start of the third epoch
wandb.init(resume_from=f"{_id}?_step={4*batch_size}")
wandb.log({'bananas': 10}, step=5*batch_size)
wandb.log({'bananas': 11}, step=6*batch_size)

# End of third epoch, let's say the job is done.
wandb.finish()
# We expect to see in the UI: [1,2,6,7,10,11]
# But PROBLEM: We still only see [1,2,6]

I ran this experiment several times with different ID to make sure it was consistent and I get this issue every time.
Additional Files

Environment
WandB version: 0.17.3
OS: Ubuntu 22.04.2 LTS
Python version: 3.10.13
Versions of relevant libraries:
Additional Context
No response

Some additional testing led me to find that the summary metrics are not synced with the plots. Here is what I get for the above run.

It seems like all the logs from the second run were uploaded which is better (but it is still missing the third run).
I guess this is both an UI and a CLI bug then.

Hi @JosselinSomervilleRoberts, thanks for writing in.
I ran the script that you provided with wandb version 0.17.4 and I got the expected output:
https://wandb.ai/dannygoldstein/core/runs/xh3zocgv/overview
This run has [1,2,6,7,10,11] in the UI. In the overview page, you can navigate to the run's other versions and they have the correct metric values.
Did you write in to us to have rewind enabled for you? Are you using wandb-core (our new go backend) in your client?
Also, could you provide me with a link to your project/runs that you used for this experiment?

Hi @JosselinSomervilleRoberts thank you for reaching out. Could you please provide us with your wandb username so we can check if rewind has been enabled for you? If it hasn't, we will proceed with enabling it accordingly. You may email us at<EMAIL_ADDRESS>if you don't wish to publicly disclose this info.

Hi @JosselinSomervilleRoberts I wanted to follow up on this, do you still see any issues and have you reached out to us to get the rewind feature activated? thank you!

Hi @JosselinSomervilleRoberts, since we haven't heard back from you, we will be closing this request for now. However, please feel free to reach out once you've had time to look into it, and we will be more than happy to assist you further.


Added support for reading blowing snow parameters in image driver

This closes #327.
This is a branch off of PR #388.  Thus at present it contains the commits from that PR.  But as soon as that PR is taken, the diff for this PR should collapse down to a single file: vic/drivers/image/src/vic_init.c.

Rebased this branch against my PR for lake parameter support.

@tbohn - it doesn't seem like your rebase did anything.  In fact, it may have made things worse.  I'm still getting the full diff from #388.

Haven't rebased yet due to dew being down (as I mentioned in my other
email).  I'll let you know when it's ready.
On Wed, Feb 17, 2016 at 10:51 PM, Joe Hamman<EMAIL_ADDRESS>wrote:

@tbohn https://github.com/tbohn - it doesn't seem like your rebase did
anything. In fact, it may have made things worse. I'm still getting the
full diff from #388 https://github.com/UW-Hydro/VIC/pull/388.
—
Reply to this email directly or view it on GitHub
https://github.com/UW-Hydro/VIC/pull/389#issuecomment-185568731.

Rebased against develop, which now incorporates the previous PR.

Looks good.  Thanks @tbohn.  Merging now...


rbd-provisioner pod "CrashLoopBackOff"

[root@master ~]# kubectl get pods
NAME                               READY   STATUS             RESTARTS   AGE
rbd-provisioner-85578d4dbd-qb422   0/1     CrashLoopBackOff   6          9m52s
[root@master ~]# kubectl describe pod rbd-provisioner-85578d4dbd-qb422 |tail -8
Events:
Type     Reason     Age                   From               Message

Normal   Scheduled  10m                   default-scheduler  Successfully assigned default/rbd-provisioner-85578d4dbd-qb422 to node1
Normal   Pulled     6m44s (x5 over 10m)   kubelet, node1     Container image "quay.io/external_storage/rbd-provisioner:latest" already present on machine
Normal   Created    6m43s (x5 over 10m)   kubelet, node1     Created container rbd-provisioner
Normal   Started    6m43s (x5 over 10m)   kubelet, node1     Started container rbd-provisioner
Warning  BackOff    12s (x32 over 9m14s)  kubelet, node1     Back-off restarting failed container

[root@master ~]# kubectl logs rbd-provisioner-85578d4dbd-qb422
F0815 15:39:01.856313       1 main.go:80] Error getting server version: Get https://<IP_ADDRESS>:443/version?timeout=32s: dial tcp <IP_ADDRESS>:443: i/o timeout


-Filter parameter missing from "Parameters" section

I'm trying to see what I can do with the -Filter parameter; from memory, I can't use Regex, but wanted to confirm it here.  The only info about filter syntax is to run "Get-Help about_ActiveDirectory_Filter", which just gives me a list of ActiveDirectory cmdlets, presumably that use the filter syntax?  Either way, it doesn't tell me much about how to use the -Filter parameter.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6b8337d2-8c17-df81-3184-128e17d9d163
Version Independent ID: fa6e2a23-2a2d-16f7-079b-e2f5bdd8d938
Content: Get-ADComputer (addsadministration)
Content Source: docset/windows/addsadministration/get-adcomputer.md
Product: w10
Technology: powershell-windows
GitHub Login: @andreabarr
Microsoft Alias: v-anbarr

@JakeMoe Thank you for your feedback.
I can see the -Filter parameter section in the article. You can see it here in github as well:
Get-ADComputer F-ilter
Here is a version of the article about_ActiveDirectory_Filter

Hi @velkovb ,
For the -Filter paramter, yes, I can see info there now, but the history of that page cuts off a month after my comment, so I can't tell you what I saw then.
The only other comment I'd say is that it'd probably be worth linking that "Get-Help about_ActiveDirectory_Filter" to the link you shared.  Otherwise, I'm ok if you close this now.
Cheers,
Jake Moe

@JakeMoe Hi Jake,
That is a good idea I will include it in the article. Otherwise, it seems like the file is not present in the help files of recent versions of Windows but I found examples where people were able to find it in Server 2012.


[WIP] Add compose method for combining two graph objects

This commit adds a compose() method to the PyDiGraph object and PyGraph
object. This method takes in another PyDiGraph or PyGraph object respectively
and a dictionary on where to add edges between the nodes. The keys are node
indicies in the first graph and the value is a tuple of the node indices in
the other graph and the weight to use for that edge.
This is a first implementation and is not that efficient since it
requires looping over the graph structure of the other graph to manually
reconstruct it in the original graph. Ideally in the future we should be
able to do this primarily as memory/vector operations and only adjusting
the graph structure on the boundaries. However, there is no support in
doing this via petgraph yet (see petgraph/petgraph#276) so for a first
pass this just iterates over the graph strucutre which should still be
significantly faster than doing it in python.
Related to #61
TODO:

[ ] Add more tests

Coverage decreased (-1.3%) to 89.081% when pulling 72dc9ddc20cf98e19418d8234fcf3f0a2174ef87 on mtreinish:add-compose-inefficient into 12ecedfed7d5e053a1b3016f3336bd4244365938 on Qiskit:master.


Teams is missing "permissions" field

It appears the Repositories.ListTeams(Docs) API call returns a field permissions on each team which includes the more detailed set of permissions with triage/maintain.
A similar field is currently populated on User when calling Repositories.ListCollaborators([Docs].(https://docs.github.com/en/rest/reference/repos#list-repository-collaborators))
Example
Tested on Github Enterprise v3.0.6
https://<github-host>/api/v3/repos/test-org/test-repo/teams
[
  {
    "name": "Example Team",
    "id": 99,
    "node_id": "...",
    "slug": "example-team",
    "description": "",
    "privacy": "closed",
    "url": "...",
    "html_url": "...",
    "members_url": "...",
    "repositories_url": "...",
    "permission": "push",
    "permissions": {
      "pull": false,
      "triage": false,
      "push": false,
      "maintain": true,
      "admin": false
    },
    "parent": null
  },
]

Docs
This endpoint appears to be the same in Enterprise 3.0 and Github.com.
Proposal
Add a Permissions field identical to what exists on User to the Team type.

Thanks for all the help @gmlewis!


Polish the alignment of text widgets

Related thread — https://theappsmith.slack.com/archives/C04P60V0VQE/p1707843288118089

Hey team! Please add your planning poker estimate with Zenhub @ichik @jsartisan


Remove dist-newstyle -> dist hack

The hack is no longer needed because we have moved to ghc-8.10.4.
The hack was necessary because ghc-8.6.5 suffered MAX_PATH issues for haskell source code.

But we still have the "Haskell CI / build (8.6.5, windows-latest)" job, wouldn't this PR break that?

I didn't realise we were still building for ghc-8.6.5 for cardano-node.  Yeah, let's not merge this until we drop support for ghc-8.6.5.  I'll convert this PR to a draft.

Having dropped support for ghc-8.6.5, this workaround can now be removed.

bors merge


Support/Changes for v<IP_ADDRESS>

It seems that v<IP_ADDRESS> introduces a lot of changes in the custom resource definitions.
Will we see and update for v<IP_ADDRESS> or can this chart be used for the new version?
https://www.ibm.com/docs/en/scalecontainernative?topic=overview-whats-new
Thank you.

Unfortunately, the <IP_ADDRESS> chart cannot be used for the <IP_ADDRESS> version. There are significant changes that were applied to <IP_ADDRESS> with a combined deployment of IBM Spectrum Scale CNSA and IBM Spectrum Scale CSI. Clients already running CNSA <IP_ADDRESS> need to follow the official documentation for the upgrade procedure here.  I will look into the effort of updating the Helm charts.

Update: Instead of working on CNSA <IP_ADDRESS> I was waiting for the release of CNSA <IP_ADDRESS> with CSI 2.3.1 and am now finalizing a release of a single Helm chart for it. As the resources for CNSA <IP_ADDRESS> have changed considerably compared to CNSA <IP_ADDRESS> the Helm chart will be a completely new one. It will be released soon.

Since we were forced by the storage team to upgrade to <IP_ADDRESS>, we already created a custom chart for us, which only contains the new CR objects.
For the installation of the operator / CRDs i would prefer the OLM (Operator Lifecycle Manager) instead of an helm chart. This would simplify the lifecycle/update management of the operator even more.

Closing this issue with the release of a new Helm chart for CNSA <IP_ADDRESS>.


PlatformTabScaffold overflows PlatformNavBar in Material 3 [Android only]

The following is my HomeView:
PlatformTabScaffold(
        tabController: PlatformTabController(),
        bodyBuilder: (context, tabIndex) => AppRouter.tabs[tabIndex],
        iosContentBottomPadding: true,
        iosContentPadding: true,
        appBarBuilder: (_, __) => AdcAppBar(),
        material: (_, __) => MaterialTabScaffoldData(
          drawer: const SideMenu(),
          drawerEnableOpenDragGesture: true,
          resizeToAvoidBottomInset: true,
          primary: true,
        ),
        cupertino: (_, __) => CupertinoTabScaffoldData(
          resizeToAvoidBottomInset: true,
          resizeToAvoidBottomInsetTab: true,
        ),
        items: [
          BottomNavigationBarItem(
            icon: Icon(
              PlatformIcons(context).home,
            ),
            label: context.strings.home,
          ),
          BottomNavigationBarItem(
            icon: PlatformWidget(
              material: (_, __) => const Icon(
                Icons.history,
              ),
              cupertino: (_, __) => const Icon(
                CupertinoIcons.time_solid,
              ),
            ),
            label: context.strings.history,
          ),
        ],
      ),

This uses the default sizes for everything, yet, on Android, it overflows by 2.0 pixel at the bottom, with the following stackTrace:
======== Exception caught by rendering library =====================================================
The following assertion was thrown during layout:
A RenderFlex overflowed by 2.0 pixels on the bottom.

The relevant error-causing widget was:
  Column Column:##################################/packages/flutter/lib/src/material/bottom_navigation_bar.dart:610:12
The overflowing RenderFlex has an orientation of Axis.vertical.
The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and black striped pattern. This is usually caused by the contents being too big for the RenderFlex.

Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size.
This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView.

The specific RenderFlex in question is: RenderFlex#bb33f relayoutBoundary=up8 OVERFLOWING
...  parentData: offset=Offset(0.0, 7.0) (can use size)
...  constraints: BoxConstraints(0.0<=w<=189.7, 0.0<=h<=42.0)
...  size: Size(189.7, 42.0)
...  direction: vertical
...  mainAxisAlignment: spaceBetween
...  mainAxisSize: min
...  crossAxisAlignment: center
...  verticalDirection: down
◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤◢◤
====================================================================================================
Reloaded 1 of 1195 libraries in 558ms (compile: 21 ms, reload: 245 ms, reassemble: 190 ms).

Sorry for the late response, this is/was a problem in flutter_platform_widgets


Add reason to skip

@xush6528 I just realized support for #43  was already there, lol, but there was no proper docs.
This adds docs and support for a simpler syntax.
Closes #43.

Where is the docs?

Sorry, wrong PR, this is the correct one: #46 .


missing support for valid xsd:gYear values

based on xsd spec values like -20000, 20000 and 0000 should be accepted by RDF4J for the xsd:gYear datatype but are currently not.
Quoting https://www.w3.org/TR/xmlschema-2/#gYear

<IP_ADDRESS> Lexical representation
[...] To accommodate year values outside the range from 0001 to 9999, additional digits can be added to the left of this representation and a preceding "-" sign is allowed.

A related PR that adds these values to the test suite and verifies they are not supported is in  https://github.com/eclipse/rdf4j/pull/931

wrt to value 0000, see
https://www.w3.org/TR/xmlschema11-2/#vp-dt-year

[...] Note: In version 1.0 of this specification, the ·year· property was not permitted to have the value zero. [...]
In this version of this specification, two changes are made in order to agree with existing usage. First, ·year· is permitted to have the value zero. [...]

WRT year zero, RDF4J uses the JVM's validation that is based on XMLSchema 1, which does not have a lexical representation for year zero.
That being said, the values "-20000" and "20000" should be a simple change to support in a future version.


.cue sheet support

Hi James,
Great v.4.14 release, thanks a lot for your work! VUPlayer is my one and only audio player since 2007, and will continue to be :)
I have a request, for a future realease: I'll be possible add back cue sheet support? That already existed in v.2.4x but not in v4, and would help for FLAC, APE or WV one-archive rips with a .cue sheet file with the tracks info.
Thanks & regards
Emilio.

Hi, it's good to hear from a long time user.
Cue sheet support is one of the things I never got round to adding to the new version, but it's on the list of things to do.
I'll probably have to limit support to the playlists, as I don't see a nice & easy way of adding .cue file support to the folder browser.
Thanks,
James

Hi,
It took awhile, but I finally added support for cue sheets in the latest 4.18 release.
Specifically, the 'Import Playlist' menu option now allows you to import .cue files.
I also included support for retrieving metadata from the MusicBrainz service if the cue sheet is a suitable type, i.e. it has a single source file, and continuous cues, with a start cue of zero. These are the only type of cue sheets I had available for testing, so hopefully it's the most common type.
Thanks,
James


bulk_create_with_history acts incorrectly with duplicate objects

Describe the bug
When using bulk_create_with_history, if there is an item that is a duplicate (either created earlier in the same batch or already existing in the database) the returned object includes both the newly created and the existing duplicated object.
In addition, history will be generated for both items, even though only the newer item should have generated history. This will happen multiple times if the duplicates are created in the same batch.
In summary:
If a duplicate item already exists in the database:

All duplicate items will be returned
History will be generated for all duplicate items

To Reproduce

Use a database which doesn't return ids
Save an object to the database
Create duplicate object(s) using bulk_create_with_history
Inspect returned result and historical entry

Expected behavior

Only items that were created should be returned
Duplicated objects that were not created should not be returned
History should be generated only for objects that were created

Environment:

Django Simple History Version: 3.0.0
Django Version: 3.2.15
Database Version: MySQL 8.0.29

It's possible that this is the intended way for this function to work, in which case I would appreciate adding more information to the docstring.

This issue seems to be fixed by PR #975.

I thought this issue was completed with PR #975 but this problem still exists.

PR #975 seems to fix creating duplicates, but the issue still persists when there are pre-existing duplicate items. I have updated the description.

Deleted this issue and recreated it for #1037 so I could add a PR.


Modify Long header packets

The data view generated from long header packets should use an untrue source connection ID to avoid de-anonymizing attacks.

Upgrade to new ReplyPath frame:
ReplyPath Frame {
	Frame Type (i),
	Fields Present (8),
	Source IP Address Version (8),
	Source IP Address Bytes (..),
	Source Port Bytes (16),
	Source Connection ID Length (8),
	Source Connection ID (0..160),
	Reply As Source IP Version (8),
	Reply As Source IP Address Bytes (..),
	Reply As Source Port bytes (16),
	Reply As Source Connection ID Length (8),
	Reply As Source Connection ID (0..160)
}


How to run example app?

I have code in app.tsx:
import { Box, Label, Window, exit, render } from "../bundled/react-gjs-renderer";

const App = () => (
  <Window onDestroy={exit}>
    <Box>
      Hello World!
    </Box>
  </Window>
);

render(<App />);

I have included react-gjs renderer: #222
I can't run this via cjs/gjs because I have errors:
(gjs:622742): Gjs-CRITICAL **: 23:27:40.683: JS ERROR: SyntaxError: import declarations may only appear at top level of a module @ app/app.tsx:1:0

(gjs:622742): Gjs-CRITICAL **: 23:27:40.684: Script app/app.tsx threw an exception

So first things first, that example from README is a little bit outdated, it should look something more like this:
import Gtk from "gi://Gtk?version=3.0";
import * as React from "react";
import { Box, Label, render, Window } from "./src/index.ts";

Gtk.init(null);

const App = () => {
  return (
    <Window
      quitAppOnClose
      minWidth={200}
      minHeight={200}
    >
      <Box>
        Hello World
      </Box>
    </Window>
  );
};

render(<App />, {
  appId: "com.example.app",
});

imports.mainloop.run();

Also I think you misunderstood that thing about bundling, what I am recommending is to bundle the application not the library, in other words if the above example is inside a App.tsx file, then you should run this command to bundle it:
 esbuild ./App.tsx --bundle '--external:gi://*' --external:system  --format=esm --outfile=./out.js
And this is assuming that react-gjs-renderer is inside the node_modules directory.
I've just tried exactly this setup and executing gjs -m ./out.js works as expected, a window with a "hello world" message appears.

I have no idea how the shell extensions differ from regular desktop apps, and what you'd need to do to make it work. I am guessing that a shell extension doesn't use Gtk.Application, and probably you don't create a window for them either, so a separate render() function would be needed, one that doesn't initiate a new Gtk.Application, if that's all then I would see no problem adding support for that.

Ok, i will think about it later, now, did i can create my own component with my own logic and style like in the web app?


remove async box macro

Description
Removes the box_async macro.
Motivation and Context
Removes the box async macro, removing indirection from the code.
How Has This Been Tested?
Tests pass
Types of changes

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

Checklist:

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

Heh, rustfmt is not happy with you revealing the code that was hiding behind the macro.

hah, applied rustfmt. Hope tests pass :crossed_fingers:

Looks good to go, thanks!


Link to repo

Should we have a link to the repository anywhere on the website? Does one exist already that I missed?
A 'Fork me on Github!' thing might be a bit much, but it couldn't hurt to tell people how they can contribute.

Not exactly what you're looking for, but I've added a link to the GitHub page, #17

https://github.com/MUNComputerScienceSociety/Website/pull/22


Change/update the used account

I created several integrations a while ago. Suddenly I get the message "This connection has to be removed and recreated.".  Please tell me there is a way to update the used account instead of having to delete and recreate all the integrations.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1cddc0ae-93af-297c-2e71-334143ebee1e
Version Independent ID: cb76e516-8471-c3e1-45f4-0a20a223f32a
Content: Create a service hook Microsoft Teams - Azure DevOps Services, TFS 2017
Content Source: docs/service-hooks/services/teams.md
Product: devops
Technology: devops-collab
GitHub Login: @chasewilson
Microsoft Alias: phwilson

@Expecho  Thank you for the feedback.
Unfortunately, since this is a documentation forum our support options are limited.
Please start an issue here (or let us know and we can start one for you) and provide a link back to this issue.
There the product team can diagnose the problem and, if needed, issue a fix and we will update the article accordingly.
For further support options, please also refer to:

Azure DevOps Support
Azure DevOps on StackOverflow

Closing this issue now, please comment below if there are additional questions.


EventHub: updated for GEO DR

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[X] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

APIs added -- requiring ARM signoff (@ravbhatnagar)

@v-Ajnava any update s here?
Have all Gaurav's feedbacks been addressed here?

@salameer, Yes, Gaurav's feedback are addressed.

 https://github.com/Azure/azure-sdk-for-ruby/pull/1000

 https://github.com/Azure/azure-sdk-for-python/pull/1479

No modification for AutorestCI/azure-sdk-for-node


Added checksums to common files in makefile

This PR fixes issue #676

@howdyjessie please review this pull request.

@hongsudt I did; I commented on this thread earlier in the day.


Expose SLURM-account selection for user-editing and for job execution

This is a placeholder, that depends on the corresponding fractal-server feature:

https://github.com/fractal-analytics-platform/fractal-server/issues/956

As of 1.4.1a0, the API is now up-to-date (even if this doesn't have any actual effect on job execution yet, waiting for https://github.com/fractal-analytics-platform/fractal-server/issues/1076).
Changes that already make sense with 1.4.1a0

In the admin-area, GET /auth/users/{id} and PATCH /auth/users/{id} now also include the slurm_accounts property (in the request and/or response bodies). This is a non-nullable property, which is made by an array of strings. In case it's not relevant, it should be set to an empty array, and not to null.
In the "edit" modal, it would be useful to specify that  the first account in the list will be used as a default for job execution.

Changes that will make sense after another fractal-server update

The same as point 1, but for GET /auth/current-user and PATCH /auth/current-user. It's not yet relevant to have this in-place, since the user could try to use it but it has no effect.

The job-execution prompt should include an optional choice of the slurm_account to use, which would then be included as a new (optional string) property in the request body. The UI could be e.g. as follows:

If user.slurm_accounts is an empty array, then this feature is not relevant and we could either hide it or keep it there but in a shadowed area
If user.slurm_accounts has some values, then we should show them as a dropdown menu. Should this menu also include the possibility of not setting any account? I think so. Should this menu come with a pre-selected option? I think so (the first one in the list).

This issue is now ready to be tackled. I updated the previous comment with the required changes.

I see that the server allows to add an empty string inside the slurm accounts list (e.g. [ "account1", "" ]). Should this be allowed?

I see that the server allows to add an empty string inside the slurm accounts list (e.g. [ "account1", "" ]). Should this be allowed?

No, it should not (cc @ychiucco)

Is it useful to have the slurm account inside the workflow job modal?

Some screenshot from #391

Some screenshot from https://github.com/fractal-analytics-platform/fractal-web/pull/391

I've not tested it myself, but the screenshots look very reasonable to me. Thanks!
Note on backend updates
There may be some updates in the backend (ref https://github.com/fractal-analytics-platform/fractal-server/issues/1146), but I think this first PR should be part of a fractal-web 0.8.1 that co-exists with fractal-server 1.4.2 (the current version). If/when the backend gets relevant updates, we'll target them in future fractal-web PRs/versions.


update linkwarden to v2.5.0

Thanks for the PR. The README needs to be updated.

Thank you, and this has been merged! Feel free to start more PR if you see anything else!


高精地图咨询

请问高精地图的生成，必须是采用apollo的硬件平台方案，还是只需要相同的数据格式？另外，地图的生成是在百度做吗？收费还是免费？

@riskeverything There is a online guide, I think it's all right to collect a map by yourself. If you record the bag with the some format.
The hardware may be a bit redundant for map acquisition, and also need to be calibrated. I think there may be a deprecated version of the hardware and software solution in the future. It may work only by mailing a device.

Closing this issue as it appears to be resolved. Feel free to reopen if you have additional questions.
Thanks!


New token always created

Hi, I am currently using your package to authenticate users from Facebook. I have a uniquely occuring issue where a new token is always created for thesame user whenever they log in.
My current setup is a frontend powered by react and a backend built in django. A test request using curl gives the same outcome. Is this the normal functioning of the package or am I do something wrong?

same here with Google OAuth2 authentication

Hi all.
My team and I are constantly using this framework and it seems it has died out there. I contacted the owner by email asking if he would add some of us as maintainers so we could continue to improve it. However we didn't get a response.
I am publishing the project under my profile and we are going to continue to invest time in it.
So I would like to gently ask you to contribute to this project on: https://github.com/wagnerdelima/drf-social-oauth2.
Thank you for understanding.


Extend Size calculation to all the transaction types

Problem
Closes #177
...
Solution
Follow C# implementation and added tests cases. The result of the test cases matches with neo-python and neo-C# implementation.
...

Closed PR due to inactivity.


[Gardening] Remove validateExtension's Interface

Killed this API so fast we forgot to remove the interface...

@swift-ci please smoke test and merge


[Peek] Optimize file querying for large folders

Description of the new feature / enhancement
Make file querying faster when navigation has folder-wide scope.
Scenario when this would be used?
Peek's navigation feature can be take a very long time to be enabled upon peek activation in folders with 1000s of items.
Supporting information
No response

If I'm not seeing this wrong, I would tend to prefer the macOS quickview's and QuickLook's approach to file browsing which is the fact that it doesn't need to load anything, you can keep using the directional keys to move forward to an item even with the explorer out of view.
For example, you can only load image files like the current implementation, whereas with Quicklook you can quickly scan a folder's content regardless of the files there, without having to press anything other than the arrow keys.
This is the only think that will make me still prefer QuickLook over peek.


io: Bump version to 0.1.1

We attempted to release with the current 0.1.0 version forgetting that we had previously released an empty crate with that version to reserve the name on crates.io.
Bump the version to 0.1.1 and release the actual code.

This is what #2441 should have been.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.995%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
19433

Relevant Lines:
23136

💛  - Coveralls

Tagged and published.


Synchronise master and kilo branches

There are a number of commits that went into master that we did not backport to kilo.  Rather than have a mass of individual pull requests with a single cherry-pick in each one, this is a single pull request with all commits.

+1 the two branches appear to be the same except for the rpc_release variable because that is still r11.1.0rc5 in master.

NB: rpc-aio is currently a WIP and so it's comments shouldn't be used as a basis for decision making.

ah, that's good to know, was holding back the other PRs too

also, given that 11.1 is the last kilo I think this should merge, not sure if all at once though.

:+1:

:+1:


User profile updates should be only allowed by admin or bots

Fixed in https://github.com/open-metadata/OpenMetadata/pull/1765


Question about pedestrian detection on waymo

Have you tried to train a model for pedestrian on waymo?
Though I'm trying to train a CenterPoint/PointPillars model for pedestrian on waymo, the model gets a poor result (about 20% AP).
Do you have any ideas to improve the result?

I haven't yet. 20 map sounds too low. Can you reproduce the car result?

The car AP was about 60%.
It was lower than your result because I have changed the layer strides in rpn and total epochs.

well, then my only suggestion is to use the original network + number of epochs. Ped may be more sensitive to tthis.

I have two questions.

What gpu do you use?
ds_layer_strides=[1, 2, 2] and us_layer_strides=[1, 2, 4] requires a lot of memory capacity.
Additionally, you set batch size=4.
So out of memory occurs in my gpu (1080ti).

How long did it take to train the model for 30 epochs.

We use V100. Yeah, I understand that it takes a lot of memory. I am not able to train Waymo models on Titan XP / V. If you use a larger stride, I guess you need to slightly decrease the voxel size. Otherwise, there will be some center collisions.

On 4 V100, it takes about 2.5 days.

Thank you for your reply.
I have reproduced the results.

Congrats!

@tianweiy
Hi, the performances of Vehicle and Pedestrian in paper are trained using one model with two class or two separate model? I found 3% mAP drop of my reproduced results compared with the paper.

Hi, we trained a single model for veh / ped.

@tianweiy  Are there any other tricks that we should pay attention? There is always 3 mAP_L1 gap between our reproduced and paper, i.e., 73 vs 76 on vehicle : (

No tricks as far as I know. We use the same code as the one here.
Actually, what result do you get for one stage model? Is it normal?
Additionally, the result in paper is single frame

@tianweiy we train a model with two class. One stage model with 2-frame is 72.3 mAP, with 1-frame is only 70.9. Here is my config
import itertools
import logging
from det3d.utils.config_tool import get_downsample_factor

extra_tag = 'full-1_frame-nms07-input_5-2_cls-wo_velo'
DOUBLE_FLIP = False

tasks = [
    dict(num_class=2, class_names=['VEHICLE', 'PEDESTRIAN']),
]

class_names = list(itertools.chain(*[t["class_names"] for t in tasks]))

# training and testing settings
target_assigner = dict(
    tasks=tasks,
)

# model settings
model = dict(
    type="PointPillars",
    pretrained=None,
    reader=dict(
        type="PillarFeatureNet",
        num_filters=[64, 64],
        num_input_features=5,
        with_distance=False,
        voxel_size=(0.32, 0.32, 6.0),
        pc_range=(-74.88, -74.88, -2, 74.88, 74.88, 4.0),
    ),
    backbone=dict(type="PointPillarsScatter", ds_factor=1),
    neck=dict(
        type="RPN",
        layer_nums=[3, 5, 5],
        ds_layer_strides=[1, 2, 2],
        ds_num_filters=[64, 128, 256],
        us_layer_strides=[1, 2, 4],
        us_num_filters=[128, 128, 128],
        num_input_features=64,
        logger=logging.getLogger("RPN"),
    ),
    bbox_head=dict(
        type="CenterHead",
        in_channels=128*3,
        tasks=tasks,
        dataset='waymo',
        weight=2,
        code_weights=[1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0],
        common_heads={'reg': (2, 2), 'height': (1, 2), 'dim':(3, 2), 'rot':(2, 2)}, # (output_channel, num_conv)
        share_conv_channel=64,
    ),
)

assigner = dict(
    target_assigner=target_assigner,
    out_size_factor=get_downsample_factor(model),
    dense_reg=1,
    gaussian_overlap=0.1,
    max_objs=500,
    min_radius=2,
)

train_cfg = dict(assigner=assigner)

test_cfg = dict(
    post_center_limit_range=[-80, -80, -10.0, 80, 80, 10.0],
    nms=dict(
        nms_pre_max_size=4096,
        nms_post_max_size=500,
        nms_iou_threshold=0.7,
    ),
    score_threshold=0.1,
    pc_range=[-74.88, -74.88],
    out_size_factor=get_downsample_factor(model),
    voxel_size=[0.32, 0.32],
    double_flip=DOUBLE_FLIP
)

# dataset settings
dataset_type = "WaymoDataset"
nsweeps = 1
data_root =

db_sampler = dict(
    type="GT-AUG",
    enable=False,
    db_info_path=
    sample_groups=[
        dict(VEHICLE=15),
        dict(PEDESTRIAN=10),
        dict(CYCLIST=10),
    ],
    db_prep_steps=[
        dict(
            filter_by_min_num_points=dict(
                VEHICLE=5,
                PEDESTRIAN=5,
                CYCLIST=5,
            )
        ),
        dict(filter_by_difficulty=[-1],),
    ],
    global_random_rotation_range_per_object=[0, 0],
    rate=1.0,
)

train_preprocessor = dict(
    mode="train",
    shuffle_points=True,
    global_rot_noise=[-0.78539816, 0.78539816],
    global_scale_noise=[0.95, 1.05],
    db_sampler=None,
    class_names=class_names,
)

val_preprocessor = dict(
    mode="val",
    shuffle_points=False,
)

voxel_generator = dict(
    range=[-74.88, -74.88, -2, 74.88, 74.88, 4.0],
    voxel_size=[0.32, 0.32, 6.0],
    max_points_in_voxel=20,
    max_voxel_num=[32000, 60000],
    double_flip=DOUBLE_FLIP
)

train_pipeline = [
    dict(type="LoadPointCloudFromFile", dataset=dataset_type),
    dict(type="LoadPointCloudAnnotations", with_bbox=True),
    dict(type="Preprocess", cfg=train_preprocessor),
    dict(type="Voxelization", cfg=voxel_generator),
    dict(type="AssignLabel", cfg=train_cfg["assigner"]),
    dict(type="Reformat"),
]
test_pipeline = [
    dict(type="LoadPointCloudFromFile", dataset=dataset_type),
    dict(type="LoadPointCloudAnnotations", with_bbox=True),
    dict(type="Preprocess", cfg=val_preprocessor),
    dict(type="DoubleFlip") if DOUBLE_FLIP else dict(type="Empty"),
    dict(type="Voxelization", cfg=voxel_generator),
    dict(type="AssignLabel", cfg=train_cfg["assigner"]),
    dict(type="Reformat", double_flip=DOUBLE_FLIP),
]

train_anno =
val_anno =
test_anno = None

data = dict(
    samples_per_gpu=4,
    workers_per_gpu=8,
    train=dict(
        type=dataset_type,
        root_path=data_root,
        info_path=train_anno,
        ann_file=train_anno,
        nsweeps=nsweeps,
        load_interval=1,
        class_names=class_names,
        pipeline=train_pipeline,
    ),
    val=dict(
        type=dataset_type,
        root_path=data_root,
        info_path=val_anno,
        test_mode=True,
        ann_file=val_anno,
        nsweeps=nsweeps,
        class_names=class_names,
        pipeline=test_pipeline,
    ),
    test=dict(
        type=dataset_type,
        root_path=data_root,
        info_path=test_anno,
        ann_file=test_anno,
        nsweeps=nsweeps,
        test_mode=True,
        class_names=class_names,
        pipeline=test_pipeline,
    ),
)

optimizer_config = dict(grad_clip=dict(max_norm=35, norm_type=2))

# optimizer
optimizer = dict(
    type="adam", amsgrad=0.0, wd=0.01, fixed_wd=True, moving_average=False,
)
lr_config = dict(
    type="one_cycle", lr_max=0.003, moms=[0.95, 0.85], div_factor=10.0, pct_start=0.4,
)

checkpoint_config = dict(interval=1)
# yapf:disable
log_config = dict(
    interval=5,
    hooks=[
        dict(type="TextLoggerHook"),
        # dict(type='TensorboardLoggerHook')
    ],
)
# yapf:enable
# runtime settings
total_epochs = 36
device_ids = range(8)
dist_params = dict(backend="nccl", init_method="env://")
log_level = "INFO"
work_dir = './work_dirs/{}/{}/'.format(__file__[__file__.rfind('/') + 1:-3], extra_tag)
load_from = None
resume_from = None
workflow = [('train', 36), ('val', 1)]

that sounds weird and I don't have much clue at the moment (the config looks right).
Have you tried the three class config  (single frame) https://github.com/tianweiy/CenterPoint/blob/master/configs/waymo/pp/waymo_centerpoint_pp_two_pfn_stride1_3x.py
The main difference is that we use gt sampling once we also need to detect cyclist.
This one already gets much higher performance in comparison to yours . Various other papers can also reproduce this results e.g. https://arxiv.org/abs/2110.06049

@tianweiy  Hi, we still have 3% gap... Would you mind sharing the training log with us? For instance, the single-frame two-cls point-pillar on waymo datasets

I only back up pretrained models and detection prediction when I left ut (for 3 class pp). You can send me an email if you need them. Unfortunately, I don't have the log anymore

@tianweiy  Hi, we found another validation gt.bin in this. With this bin, we could perfectly reproduce the mAP in your paper.
Is the above bin that used in your paper?
We also confuse that why our own step-by-step generated bin following your doc has 3% gap ...

Oh interesting. I used the gt bin generated in this repo. I guess there were some code changes in the waymo devkit that may cause the problem?
To be 100 percent sure, you can use the online server for evaluation which is what I did for paper numbers.


Question: What's the impact of enabling XMVECTOR overloads?

I use the XMVECTOR overloads in some of my 2D calculations, as I've merged some of the DXTK code into my own library, I'm wondering what the impact of removing #define XM_NO_XMVECTOR_OVERLOADS might be on the DXTK library?

The XM_NO_XMVECTOR_OVERLOADS define is there to make sure I maintain compatibility with clang/LLVM. For details on what that's about, see this issue.  If you don't care about portability to non-Microsoft Visual C++ compilers then it's fine to remove in your code.


allowing mounting azure file share with SMB protocol by adding the package 'cifs-utils'

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

@jiasli for awareness

Please provide more description for your request.


In Level_7, the player can get stuck in an infinite death screen

Repro
Start game from preloader
Reach Level 7
touch the yellow circle
fall into the spikes
Actual Result
the player dies, the death screen appears and simply stays there while the death sound can be heard constantly playing
Expected Result
The player dies, the death screen appears, the player respawns, and the game goes on normally.

Issue has been fixed on future patch. Player Death "should" not be able to crash the game in the majority of cases.


Added Domain name check for AbstractAuthenticator

The AbstractAuthenticator now checks if the tenantLessUserName has
the Domain name and adds it if absent
This was added to support logging in without adding the DomainName
in-front of the username when Server URL is used

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Related Issue : https://github.com/wso2/product-ei/issues/4647

Please refer new PR for 4.5.x : https://github.com/wso2/carbon-kernel/pull/2301


Added save button placeholder [#171333030]

NOTE: the save button does nothing, its just there to make the user feel good.

@dstrawberrygirl I'm going to hold off merging this until we start on the manual table entry work.


started to edit mapconfig content, added reviewer question for Raul

For Docs issue#570
@rochoa , is is possible to break up this content by arguments/returns/examples, or is the flavor of the content different since it is a configuration file? I am trying to determine the best format to describe this content for end-users (is there another CartoDB example of configuration descriptions?)
Also, I entered a comment to you about what to do with the TODO and History sections.  Seems weird to display that to the public documentation audience.

Have in mind that there are several versions of this spec, this is just one of them.
I wouldn't change the titles as they might be linked from other places and we will break those links.

If we want to make this part of the public CartoDB docs we should think how to include them, but please do not modify this files directly as they are specifications and we need to keep history and todo for future versions.

Okay, agreed, we need to re-strategize how to share this content then?
I know there are several versions so we need versioning control.  Additionally, we need to provide this MapConfig content for end-users, but not all the internal content from this page should appear.  And to match the format of the rest of the documentation, I would have to edit the format, but completely understand your point about how they are linked. So how can we use some of this internal doc for the public docs and maintain it consistently? Ideally, single-source doc content would be ideal but I know the file structure set-up is unique here.

How about this @rochoa? I can create a public version of this content (and store locally within the Docs file structure), but every time you edit or change something, you will have to add a Docs issue so that I am notified to update the public docs. Does that work for you?

Previous versions should not be modified, if we need to add some new behaviour we need to create a new version. That's why we have https://github.com/CartoDB/Windshaft/blob/46c56495073adcd56016f4d85124a8a1c5d50a67/doc/MapConfig-specification.md pointing to latest version.
I really want to keep history and todo in these documents. As I said, this is internal documentation and the actual Maps API doesn't follow this very same spec but an extended version from Windshaft-cartodb as stated in https://github.com/CartoDB/Windshaft-cartodb/blob/45acdd9f39b8fb4aced43dda1e8a1e1c1cf85da1/docs/MultiLayer-API.md. It also adds another extension: https://github.com/CartoDB/Windshaft-cartodb/blob/45acdd9f39b8fb4aced43dda1e8a1e1c1cf85da1/docs/MapConfig-NamedMaps-extension.md which should be documented in the final/end-user documentation.
In conclusion if we want to make this public/end-user friendly we should do it with the rest of the documentation in Windshaft-cartodb.

I'm going to be proactive and delete this PR and related Docs repo PR#614. As we are not going to edit Windshaft content directly. See Docs PR#622 as the suggested alternative.


Timeline is missing row separators

This is the same separator as on Mail's message list.
If I'm recalling this correctly, it should be enough to set gridStyleMask = . solidHorizontalGridLineMask on the table view.
The logic related to the separator in TimelineTableRowView can also (should?) be removed.

Apple's three column apps (Mail.app & Notes.app) has row separators on the second column. It might be reasonable to add it on NetNewsWire. I'll spend some time on this topic.

We have a hidden preference to turn these on. They’re not on by default just because I don’t like them.

Closing since this is functioning as it should.

We have a hidden preference to turn these on. They’re not on by default just because I don’t like them.

Fair enough.
In any case, I would suggest to remove the separator code from TimelineTableRowView since it’s doubly unnecessary.


repositories: add raisedevs/raise-dev-library.

Submitting the raisedevs/raise-dev-library. Happy to answer any questions!
Thanks for running this open source project ❤

@ArduinoBot can you take another look? I've released 0.0.4. Thanks robot! 🤖 ❤


Unturned LAG

Hello all,
It's been a while of waiting for an official solution to the lag problem. Which lag problem? 3 TPS problem. Server owners like my self should know immediately what I'm talking about.
Server specs:
2x Xeon 5620
48 GB ram
2x 2TB RAID 0
gigabit Ethernet.
So far after years of hosting Unturned since back in version 2, I realize version 3 is much more efficient and I love how server files are not in the reg anymore. But WHY SO MUCH LAG?  After a ton of experimenting and doing research I've come to a 100% conclusion that after so many structure and barricade data saved, no matter if its 24 players or 12 players, without a level wipe there is absolutely no fix. Lag is 100% caused by level data. What I can't seem to understand is why??
This game has a HUGE focus on building yet building is what causes the server to lag?!?! Hey dev, don't you think it should be your number 1 priority to make it so that building does not cause lag? If I made a game where 1/3 or more of the game is about building awesome bases, I would make it so buildings don't cause lag.  It's an awesome game but I can't play it my self because I'm too busy monitoring how old my level data gets, and responding to calls about lag this lag that... [End meaningful rant]
For anyone that stumbles on this article, if you have a solution please let me know but please remember I am an experienced server admin. I have tried different locations, different hardware, every plugin and configuration, so please don't ask me if I have enough internet or if I've tried restarting the servers.
For anyone looking for a solution, here is what I have. Having too many bases causes lag, especially in combination with lots of players. I have noticed that after a map wipe, it does NOT matter how many players join, there is no lag. I can have 30 players on a server and player ping will slightly increase just as long as it is a fresh wipe. After weeks of not wiping the server (if your server is popular), anything close to 20 players will cause... you guessed it, LAG!
I believe having a CPU better optimized for single core performance will definitely help but it does not fix the problem. I can have the worlds fastest Intel single core performance and still get crazy lag if the server fills up on 1 month of level data.
My current setup (don't judge, this isn't where I make my conclusion of lag): I have 12 Unturned servers on my dual Xeon server. I may be pushing limits here but surprisingly, my cpu usage has not hit over 70-80%. Ram usage is usually around 5-6 GB. To my knowledge I can probably host more on this server but my other 6 servers are on another machine and location, with 20Mb upload which is quite alright for 6 Unturned servers. I have monitored and my bandwidth is not close to capped on either server.

Many have complained about this. It is a real problem. But its not a Rocket one. And therefore does not belong here as a Rocket issue.
https://github.com/SmartlyDressedGames/Unturned/issues


[Draft] Cookie Appears on Landing Page

Overview
Should the cookie button appear on the current landing page?
Action Items
Resources/Instructions

Cookies pop-up appears on landing page

@smsada the landing page will go away after site launch.  Do we need to address this issue?

Closing because this is the intended state. No longer need to address the issue, thanks Bruce


Why just support swift?

pls support Objective-C

The UI component is pretty much outdated, since similar functionality can be found natively in the SDK.


Using the coraza.conf-recommended configutarion causes dangerous requests to show a warning instead of returning 403

I've followed the README, and noticed that when using the 3 include statements in README causes dangerous request to show a warning in caddy's logs, but the request itself is executed as normal, without being blocked.
when using just the include caddypath/coreruleset/rules/*.conf - evereything is blocked, and a warning shows
ModSecurity Core Rule Set is deployed without configuration! Please copy the crs-setup.conf.example template to crs-setup.conf, and include the crs-setup.conf file in your webserver configuration before including the CRS rules. See the INSTALL file in the CRS directory for detailed instructions

So I've included the crs-setup.conf and everything seems to work as expected, Is there something I'm missing, or perhaps the README should be updated?

Hey @WildHagai, could you share yous Caddy configuration and logs?
IT should look like this:
coraza_waf {
  include caddypath/coraza.conf-recommended
  include caddypath/coreruleset/crs-setup.conf.example
  include caddypath/coreruleset/rules/*.conf
}

Also, can you confirm you downloaded the Coraza default configurations? (caddypath/coraza.conf-recommended)
When you don't include the crs-setup.conf you will receive that message and your request will be blocked. Once you succeed with the configurations you may update your engine settings by setting SecRuleEngine On

I guess that's what I missed, I thought SecRuleEngine On was already pre-configured. I didn't notice it was set on DetectionOnly

Glad to help, feel free to send any feedback or report any other issue


Add support for openSUSE

The PR is for issue: https://github.com/hwdsl2/wireguard-install/issues/6 to support openSUSE
The changes are tested on openSUSE Leap 15.4

@rim99 Thank you for contributing!


Port "Issue 54: Insert a trailing space when alias is a simple key"

https://bitbucket.org/snakeyaml/snakeyaml-engine/commits/089376b4d2bbd7a0ee66808b7c1be8acc99feb04

Depends on https://github.com/krzema12/snakeyaml-engine-kmp/issues/280


feature: registry fetch asset information from chain registry

Related to: #157
Overview
Currently assets are not properly structured, and are incorrect. registry service should be able to fetch assetList of a denom from base and populate itself.
Proposal

Fetch infomation directly from chain registry via call to github chain-registry
Use a go client, which already has chain information baked in. Similar to the npm package of chain-registry
Mention information in default.yaml

Default
If the chain or denom does not exist on chain-registry, we keep using the current default asset.

Can we do both?
Fetch from defaults.yaml file, if not specified, then fetch from chain registry


[FEATURE REQUEST] separate bark setting to potentially improve long form generation

Basically, because quality degrades the longer the input is, making continuations from worsening quality outputs will severely impact the overall output. I've found this to be true while using Strict long and short.
I believe stitching together multiple, independent outputs would keep the output quality consistent rather than continuing from degrading outputs.

Yeah, i was actually kind of planning to add something for that, a setting that lets you choose between using the same history over and over, and looping the history back.
Since putting the same clip over and over causes inconsistencies with emotions etc. While looping it back has issues with it gaining noise, but having a more realistic, but also slowly degrading output.
I'm wondering if there's a way I could get the best of both worlds, like some denoiser to improve the audio quality throughout loopbacks, which would allow it to be consistent, but not lose the quality.

what does 'history' mean in this context?

Bark uses a system called "history prompts" which are basically context for the language model, It allows it to retain the same voice. These history prompts are stored in .npz files, containing 3 .npy files. The coarse, fine and semantic prompts.

ahh ok, what if for the whole prompt, they use the first sentence as history, then the rest of the paragraph uses that first sentence's history.
or the webui can detect whether a "[]" pops up and treats that as it's own history, which it uses for that one sentence.

Custom formatting for controlling the prompts could be useful. I'll think about it.

is there also a way to use multiple voices in one prompt?

Not currently but custom formatting could make it possible


Flaky client test on appveyor (x86)

+ Failure [1.135 seconds]
Client Dialing [It] uses the tls.Config.ServerName as the hostname, if present
c:/gopath/src/github.com/lucas-clemente/quic-go/client_test.go:159
  Timed out after 1.004s.
  When passed a matcher, ReceiveMatcher's channel *must* receive something.
  c:/gopath/src/github.com/lucas-clemente/quic-go/client_test.go:157
  Full Stack Trace
  	c:/gopath/src/github.com/onsi/gomega/internal/asyncassertion/async_assertion.go:147 +0x357
  github.com/onsi/gomega/internal/asyncassertion.(*AsyncAssertion).Should(0x12bcb1d0, 0xa0fe20, 0x12bd0d80, 0x0, 0x0, 0x0, 0x12bcb1d0)
  	c:/gopath/src/github.com/onsi/gomega/internal/asyncassertion/async_assertion.go:48 +0x4e
  github.com/lucas-clemente/quic-go.glob..func4.4.6(0x12bd8000)
  	c:/gopath/src/github.com/lucas-clemente/quic-go/client_test.go:157 +0x23b
  reflect.Value.call(0x7be4a0, 0x12844d48, 0x13, 0x83aa9d, 0x4, 0x12954fbc, 0x1, 0x1, 0x3, 0x7bb9a0, ...)
  	C:/go/src/reflect/value.go:434 +0x752
  reflect.Value.Call(0x7be4a0, 0x12844d48, 0x13, 0x12954fbc, 0x1, 0x1, 0x1285c1e0, 0x4268fe, 0x12ba9b1c)
  	C:/go/src/reflect/value.go:302 +0x7f
  github.com/onsi/ginkgo/internal/leafnodes.newRunner.func1(0x12bd8000)

@lucas-clemente : Do you have any idea what could be going wrong here? I don't see anything that could possibly block in that code path, and I can't reproduce the failure locally.


[sysrst_ctrl] Debounce for input detection

Description
This enhancement is based on a previous issue: https://github.com/lowRISC/opentitan/issues/17319
If there is a single-cycle dip in the input, the detection will not count it as a trigger. Although this may not be a problem in some or most instantiations, I think it would be good to debounce the de-triggering as well.

@moidx We should discuss whether this is needed for stability reasons.

Discussed this with @vogelpi. Debounce logic is not too difficult, but we need to be careful when making changes to sysrst_ctrl_detect because it is pretty essential to the functionality of the block.

Here's an untested diff of the functionality that I intended with this issue:
diff --git a/hw/ip/sysrst_ctrl/rtl/sysrst_ctrl_detect.sv b/hw/ip/sysrst_ctrl/rtl/sysrst_ctrl_detect.sv
index 310c60950c..19b9bbcb05 100644
--- a/hw/ip/sysrst_ctrl/rtl/sysrst_ctrl_detect.sv
+++ b/hw/ip/sysrst_ctrl/rtl/sysrst_ctrl_detect.sv
@@ -83,22 +83,26 @@ module sysrst_ctrl_detect
   // Timer Logic //
   /////////////////

-  // Take the maximum width of both timer values.
-  localparam int unsigned TimerWidth =
-      (DetectTimerWidth > DebounceTimerWidth) ? DetectTimerWidth : DebounceTimerWidth;
+  // Take the maximum of both widths and add 1 because we need to add the two
+  // together.
+  localparam int unsigned TimerWidth = (DetectTimerWidth > DebounceTimerWidth) ?
+                                       DetectTimerWidth + 1 :
+                                       DebounceTimerWidth + 1;

   logic cnt_en, cnt_clr;
   logic [TimerWidth-1:0] cnt_d, cnt_q;
   assign cnt_d = (cnt_clr) ? '0           :
-                 (cnt_en)  ? cnt_q + 1'b1 :
+                 (cnt_inc) ? cnt_q + 1'b1 :
+                 (cnt_dec) ? cnt_q - 1'b1 :
                              cnt_q;

   logic cnt_done, thresh_sel;
   logic [TimerWidth-1:0] thresh;
   assign thresh = (thresh_sel) ? TimerWidth'(cfg_detect_timer_i) :
-                                 TimerWidth'(cfg_debounce_timer_i);
+                                 TimerWidth'(cfg_debounce_timer_i + cfg_detect_timer_i);
   assign cnt_done = (cnt_q >= thresh);
+  assign cnt_zero = (cnt_q == '0);

   always_ff @(posedge clk_i or negedge rst_ni) begin : p_cnt_reg
     if (!rst_ni) begin
@@ -126,7 +130,8 @@ module sysrst_ctrl_detect

     // Counter controls (clear has priority).
     cnt_clr = 1'b0;
-    cnt_en = 1'b0;
+    cnt_inc = 1'b0;
+    cnt_dec = 1'b0;

     // Detected outputs
     event_detected_o = 1'b0;
@@ -157,17 +162,26 @@ module sysrst_ctrl_detect
       // correct level. If so, we move on to the
       // detection stage, otherwise we fall back.
       DebounceSt: begin
-        cnt_en = 1'b1;
         // Unconditionally go back to idle if the detector is disabled.
         if (!cfg_enable_i) begin
           state_d = IdleSt;
           cnt_clr = 1'b1;
-        end else if (cnt_done) begin
-          cnt_clr = 1'b1;
-          if (trigger_active) begin
+        end else begin
+          if (cnt_done) begin
+            // Do not clear timer because detect state builds on top of the
+            // debounce counter.
             state_d = DetectSt;
+          end else if (trigger_active) begin
+            // Stay in debounce state.
+            cnt_inc = 1'b1;
           end else begin
-            state_d = IdleSt;
+            if (cnt_zero) begin
+              cnt_clr = 1'b1;
+              state_d = IdleSt;
+            end else begin
+              // Stay in debounce state.
+              cnt_dec = 1'b1;
+            end
           end
         end
       end
@@ -179,19 +193,29 @@ module sysrst_ctrl_detect
       // back to idle.
       DetectSt: begin
         thresh_sel = 1'b1;
-        cnt_en = 1'b1;
         // Go back to idle if either the trigger level is not active anymore, or if the
         // detector is disabled.
-        if (!cfg_enable_i || !trigger_active) begin
+        if (!cfg_enable_i) begin
           state_d = IdleSt;
           cnt_clr = 1'b1;
-        // If the trigger is active, count up.
-        end else begin
+        end else if (trigger_active) begin
+          // If the trigger is active, count up.
           if (cnt_done) begin
             state_d = StableSt;
             cnt_clr = 1'b1;
             event_detected_o = 1'b1;
             event_detected_pulse_o = 1'b1;
+          end else begin
+            // Stay in detect state.
+            cnt_inc = 1'b1;
+          end
+        end else begin
+          if (cnt_zero) begin
+            state_d = IdleSt;
+            cnt_clr = 1'b1;
+          end else begin
+            // Stay in detect state.
+            cnt_dec = 1'b1;
           end
         end
       end
@@ -204,9 +228,26 @@ module sysrst_ctrl_detect
         // to go back to the idle state.
         if (!cfg_enable_i || (!trigger_active && !Sticky)) begin
           state_d = IdleSt;
-        // Otherwise keep the event detected output signal high.
+          cnt_clr = 1'b1;
         end else begin
+          // Otherwise keep the event detected output signal high.
           event_detected_o = 1'b1;
+          if (!Sticky) begin
+            if (trigger_active) begin
+              // Stay in stable state.
+              if (!cnt_done) begin
+                cnt_inc = 1'b1;
+              end
+            end else begin
+              if (cnt_zero) begin
+                state_d = IdleSt;
+                cnt_clr = 1'b1;
+                event_detected_o = 1'b0;
+              end else begin
+                // Stay in stable state.
+                cnt_dec = 1'b1;
+              end
+          end
         end
       end
       ////////////////////////////////////////////

We have discussed this enhancement with the CrOS customer and determined that this will not be needed.
If signal integrity is poor, enabling the Schmitt triggers in the associated pads is sufficient.
CC @moidx @jesultra @johngt @vogelpi @andreaskurth


don't reset selectionStart on repeat visit to start container, add test

Ah, figured out how to make a PR from a fork. Here's the proposed fix, although I was not able to get the test suite running locally due to dependency issues.
Which issue does this PR address?
Closes #3

v4.0.0 should hopefully allow you to run the test suite locally (again).
You can test against (local) firefox also by executing npm run dev and pointing your firefox to http://localhost:9876/debug.html.
If you rebase your PR on the latest main then we can see if the issue is fixed (also via CI).

Update: I rebased myself. Let's see what CI says.

Passes tests for both browsers, good job!

Awesome, thanks @nikku ! Appreciate it.


carryforward

incomplete pull req
cool extension for live, smooth movement using second order differential equations !!

if someone who has write access could, please change the extension picker menu in the dev site to have this thumbnail for the extension:

note: all this really is, is a complex version of variables made for interpolation and calculating different, very specific things

if someone who has write access could, please change the extension picker menu in the dev site to have this thumbnail for the extension:

...
you change that in the gui, and you have write access to your fork

omg rainworld iterator refrence!??!?!?!?!??1?1?1?!?!?!?!?!?!/!?!?!?!@

crazy./..

if someone who has write access could, please change the extension picker menu in the dev site to have this thumbnail for the extension:

... you change that in the gui, and you have write access to your fork

i still have no idea how to do it lmao


bug(expr): format of float of Jsonb

Describe the bug
Currenly, we print a float keeping at least one digit after the decimal point.
One example of to_jsonb:
select to_jsonb(1.0000::float);

# PG:
 to_jsonb
----------
 1

# RW:
 to_jsonb
----------
 1.0

We need to fix the formating function of the float of Jsonb. It may require some modification in the jsonbb repo.

After a quick investigation here's reason:
Our dependency chain on this is: risingwave -> jsonbb -> serde_json -> ryn.
Here's the line of the code adding the ".0". Based on the developer's answer, it's intentional.
As jsonbb is under control, so to solve this problem, we can either fork serde_json and ryn and modify the corresponding codes or switch to another repo providing similar json serialization function. As currently this misalignment has not become a big problem, let's table this issue temporarily.


Improved Crawly.fetch/2 to accept fetching with a spider

for #52, implements a :with option that allows the passing of the spider name.
Breaking changes includes moving of the headers and options parameters to the opts parameter, as keyword lists instead of positional args.

Updated, tests passes on my side, should be ok to merge.

Looks extremely good. The question is: "Can we move it outside of the main module? E.g. I want to shrink the crawly.ex"
@Ziinc could you fix the test, alternatively, I can pick it up if you don't have time right now.

We could move to Utils, but Utils is also getting quite fat

Yeah. I have the same feelings. I was thinking of splitting parts related to Crawly from parts related to spiders into separate modules.
Maybe it could make these modules small. In any case, can be done later on separately. Could you rebase it, so I will check again.

@Ziinc I am about to cut off a new release. Could you please rebase this change, so I can include it as well?

Done!


Add excludes for plugins 98 and 115

Plugin 98: Add regex for switch or portgroup names to exclude from reporting.
Rationale: Some environments have networks with security settings intentionally enabled, such as a promiscuous port group for network monitoring tools. Also, the Dell iDRAC Service Module creates a standard vSwitch with the old default security settings, and since it's recreated at every bootup this becomes spam in the report.
Plugin 115: Add regex for datastore clusters to exclude from reporting.

Resolved conflict


V5 Offcanvas - Option to disable auto hide when offcanvas loses focus.

Currently in v5.0.0-beta 3:
Offcanvas will autohide when it loses focus. IE you click anywhere other than the offcanvas area.
What I'm suggesting:
Add data-bs-autohide boolean value to config options for Offcanvas.
Default for data-bs-autohide is true; to maintain existing compatibility.
Disable event registration for EVENT_CLICK_DISMISS when data-bs-autohide is set to false.
Alternatively, to allow changing of this property via the data attribute, allow the event to still be registered, but change the event handler to respect the autohide property.
Examples of the modifications required to implement change follow.
`
const Default = {
backdrop: true,
keyboard: true,
scroll: false,
autohide: true
}
const DefaultType = {
backdrop: 'boolean',
keyboard: 'boolean',
scroll: 'boolean',
autohide: 'boolean'
}
`
      if (!this._config.autohide) {         EventHandler.on(this._element, EVENT_CLICK_DISMISS, SELECTOR_DATA_DISMISS, () => this.hide())       }

If I understand what's being proposed, would this allow the offcanvas to be used more as a drawer in the user interface? The Material UI guidelines have drawer as a component that can be on-screen all the time:
https://material.io/components/navigation-drawer#standard-drawer

It is a valid feature.
We will try to take it into consideration or you may do a PR,
However keep it for now, till #33545 is merged. I will have it in mind too

#33605
@GeoSot Please review this PR and if anything is left let me know.
https://deploy-preview-33605--twbs-bootstrap.netlify.app/

Hi, @GeoSot :slightly_smiling_face:
I created the PR at that time when the issue could be reproduced. Although now the behavior has been changed, you should keep the ability to close the offcanvas by clicking outside it and keep it configurable. And it is just my opinion you guys are the maintainer it is definitely your call to make the proper decision.

I would say that the new behavior is what would be desirable and is an acceptable alternative to what I suggested.


Added clean target and solution to asan example

@hageboeck can you check that the solution is what you expect. In particular for cases 2 and 3, that's how I would write it for this simple example, but maybe you were expecting a usage of move semantic returning a unique_ptr ?

I've finally stopped the loop earlier, as it gives 2 opportunities : showing people std::size as you mention and also mentioning again that C strings are 0 terminated.


pod  no  0.02

Maybe the author forgot to update.
You can use:
pod 'InterposeKit', :git => 'git@github.com:steipete/InterposeKit.git'

Bad news. Trying to use this in a Flutter plugin. Can't add git or version in myproject.podspec because of some arbitrary limitation by the Pod authors, because well, no one would ever want to specify a version in a podspec, even when there is no "main" Podfile. All docs regarding prepareHook are therefore moot! Please update!


How to extend to planar bilateral solver?

how to implement the planar filter in paper 'Depth from Motion for Smartphone AR, SIGGRAPH Asia, 2018'?

https://github.com/jonbarron/planar_filter


Live character app added

Have you read the Contributing Guidelines ?
(Write your answer here.)
Description
(Write your answer here.)
Fixes #issue_no

Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[ ] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

@Srishtihere Update on this else we will close the PR .

yeah yeah sure sorry I was caight in exams


Why does cargo-rpm scan for files in src/bin instead of reading the Cargo.toml spec?

Cargo.toml has these fields right?
[lib]
name = "hal"
path = "src/lib.rs"

[[bin]]
name = "hal"
path = "src/bin/hal/main.rs"

This information is typically inferred from the project structure.
As I suggested in #53, using cargo metadata (perhaps parsed via the cargo_metadata crate) for this allows us to source this information from cargo itself.

Note that #46 added an initial integration with cargo_metadata. That said, right now it's only used to locate the target/ directory.
However, it can also be used to introspect the targets for a particular package:
https://docs.rs/cargo_metadata/0.10.0/cargo_metadata/struct.Package.html#structfield.targets
To address this issue, the existing code that enumerates TargetType::MultiBin using fs::read_dir should be replaced by enumerating the cargo_metadata::Target entries for a particular cargo_metadata::Package.


chore: fix config for Experimental Kafka Scaler

Provide a description of what has been changed
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO)

Relates #1187

You can probably also add about gssapi / kerberos. This I will take a dig at later on.


BREAKING CHANGE: Remove Dropdown and Tooltip non-flow-relative placements #DS-1138

Description

Additional context

Issue reference

coverage: 96.371%. remained the same
when pulling 7b6d127a4a3ff987c49d40d1594ab9ee54861718 on bc/remove-non-flow-placements
into fb78e61ecb0f2913e63b9ba59f81152dda77138e on integration/release-v2.


Automatically detect common attributes from the request

StackdriverExporter was doing this because the attributes were known.
Common attribute labels were recently added to the spec: https://github.com/census-instrumentation/opencensus-specs/blob/master/trace/HTTP.md#attributes
This PR moves the common attribute detection to the RequestHandler and now the StackdriverExporter maps those common attributes to the Stackdriver equivalents.

@tmatsuo Rebased and fixed the documentation comment.