bevfusion results

how many epochs have you trained on BEVFusion?  I trained 6 epochs but get lower performance than you. Thanks.

6 epochs. Could you report your results?

2023-06-09 05:54:28,991   INFO  *************** EPOCH checkpoint_epoch_6 EVALUATION *****************
2023-06-09 05:58:03,049   INFO  *************** Performance of EPOCH checkpoint_epoch_6 *****************
2023-06-09 05:58:03,049   INFO  Generate label finished(sec_per_example: 0.0012 second).
2023-06-09 05:58:03,049   INFO  recall_roi_0.3: 0.000000
2023-06-09 05:58:03,049   INFO  recall_rcnn_0.3: 0.798415
2023-06-09 05:58:03,049   INFO  recall_roi_0.5: 0.000000
2023-06-09 05:58:03,049   INFO  recall_rcnn_0.5: 0.593576
2023-06-09 05:58:03,049   INFO  recall_roi_0.7: 0.000000
2023-06-09 05:58:03,049   INFO  recall_rcnn_0.7: 0.266604
2023-06-09 05:58:03,053   INFO  Average predicted number of objects(6019 samples): 200.000
2023-06-09 06:05:55,304   INFO  ----------------Nuscene detection_cvpr_2019 results-----------------
***car error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.17, 0.15, 0.06, 0.31, 0.20 | 79.72, 89.10, 91.66, 92.73 | mean AP: 0.8830172234914054
***truck error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.37, 0.20, 0.10, 0.29, 0.23 | 35.18, 55.36, 66.79, 72.46 | mean AP: 0.5744712429517645
***construction_vehicle error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.69, 0.46, 0.92, 0.14, 0.31 | 2.25, 22.12, 39.97, 47.51 | mean AP: 0.27962523349293067
***bus error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.37, 0.19, 0.09, 0.62, 0.25 | 43.27, 67.62, 84.73, 89.00 | mean AP: 0.7115396726673869
***trailer error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.52, 0.23, 0.69, 0.29, 0.19 | 11.99, 35.72, 52.30, 60.57 | mean AP: 0.4014552906321322
***barrier error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.19, 0.28, 0.06, nan, nan | 59.52, 70.15, 74.13, 75.40 | mean AP: 0.6980134584812474
***motorcycle error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.21, 0.26, 0.47, 0.42, 0.23 | 59.89, 73.01, 75.44, 76.60 | mean AP: 0.7123434972417897
***bicycle error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.18, 0.26, 0.76, 0.21, 0.02 | 50.28, 55.88, 56.49, 58.03 | mean AP: 0.5516955496353284
***pedestrian error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.14, 0.29, 0.43, 0.25, 0.11 | 84.87, 86.12, 87.17, 88.23 | mean AP: 0.8659750823258545
***traffic_cone error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0
0.13, 0.34, nan, nan, nan | 74.63, 75.99, 78.16, 80.48 | mean AP: 0.7731555530648122
--------------average performance-------------
trans_err:	 0.2971
scale_err:	 0.2660
orient_err:	 0.3984
vel_err:	 0.3180
attr_err:	 0.1912
mAP:	 0.6451
NDS:	 0.6755

2023-06-09 05:54:28,991 INFO *************** EPOCH checkpoint_epoch_6 EVALUATION ***************** 2023-06-09 05:58:03,049 INFO *************** Performance of EPOCH checkpoint_epoch_6 ***************** 2023-06-09 05:58:03,049 INFO Generate label finished(sec_per_example: 0.0012 second). 2023-06-09 05:58:03,049 INFO recall_roi_0.3: 0.000000 2023-06-09 05:58:03,049 INFO recall_rcnn_0.3: 0.798415 2023-06-09 05:58:03,049 INFO recall_roi_0.5: 0.000000 2023-06-09 05:58:03,049 INFO recall_rcnn_0.5: 0.593576 2023-06-09 05:58:03,049 INFO recall_roi_0.7: 0.000000 2023-06-09 05:58:03,049 INFO recall_rcnn_0.7: 0.266604 2023-06-09 05:58:03,053 INFO Average predicted number of objects(6019 samples): 200.000
2023-06-09 06:05:55,304 INFO ----------------Nuscene detection_cvpr_2019 results----------------- ***car error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.17, 0.15, 0.06, 0.31, 0.20 | 79.72, 89.10, 91.66, 92.73 | mean AP: 0.8830172234914054 ***truck error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.37, 0.20, 0.10, 0.29, 0.23 | 35.18, 55.36, 66.79, 72.46 | mean AP: 0.5744712429517645 ***construction_vehicle error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.69, 0.46, 0.92, 0.14, 0.31 | 2.25, 22.12, 39.97, 47.51 | mean AP: 0.27962523349293067 ***bus error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.37, 0.19, 0.09, 0.62, 0.25 | 43.27, 67.62, 84.73, 89.00 | mean AP: 0.7115396726673869 ***trailer error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.52, 0.23, 0.69, 0.29, 0.19 | 11.99, 35.72, 52.30, 60.57 | mean AP: 0.4014552906321322 ***barrier error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.19, 0.28, 0.06, nan, nan | 59.52, 70.15, 74.13, 75.40 | mean AP: 0.6980134584812474 ***motorcycle error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.21, 0.26, 0.47, 0.42, 0.23 | 59.89, 73.01, 75.44, 76.60 | mean AP: 0.7123434972417897 ***bicycle error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.18, 0.26, 0.76, 0.21, 0.02 | 50.28, 55.88, 56.49, 58.03 | mean AP: 0.5516955496353284 ***pedestrian error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.14, 0.29, 0.43, 0.25, 0.11 | 84.87, 86.12, 87.17, 88.23 | mean AP: 0.8659750823258545 ***traffic_cone error@trans, scale, orient, vel, attr |<EMAIL_ADDRESS>1.0, 2.0, 4.0 0.13, 0.34, nan, nan, nan | 74.63, 75.99, 78.16, 80.48 | mean AP: 0.7731555530648122 --------------average performance------------- trans_err: 0.2971 scale_err: 0.2660 orient_err: 0.3984 vel_err: 0.3180 attr_err: 0.1912 mAP: 0.6451 NDS: 0.6755

lower 3%, with 6x 3090 gpus, batchsize = 3 per gpu

The NDS you report is lower than that of Transfusion-L. I suggest retraining the model again as the gradient of Transfusion-Head is not stable, and I have encountered similar issue. Additionally, the ckpts provided are trained with spconv 1.0 and I observed performance drop when switching to spconv 2.0.

ok thanks for your clue and quick reply.


Expressions shouldn't return an error for an invalid path

Describe the bug
Looking at the C# adaptive code I noticed that we don't always raise an exception when evaluating an expression that returns error.  Talking to @tomlm, he said it's because the expression engine currently returns an error anytime an invalid path is encountered.  The issue with that is that the user has no way of knowing that their bot isn't working because of a bug in their expression.
I believe, the better approach would be to treat invalid paths internally as null and only return an error if the expression evaluates to something like null + 1. This way we can always throw errors returned from the expression engine. Yes there will still be cases of expressions with typos that don't trigger an exception but catching some/most errors is better than never catching any errors which is the way things are currently coded.
[bug]

I believe the current implementaion for an invalid path access is returning null, which is what this issue says. So @Stevenic do you have an example of the issue here?

this appears to be current behavior.  Please reopen if not so.


Update GitHub Actions workflows to be consistent across branches

Signed-off-by: Mohammad Qureshi<EMAIL_ADDRESS>Issue #, if available:
Description of changes:
Updating GitHub Action workflows to be consistent on all branches since the changes made under main isn't being reflected in old branches because they have a different definition of the workflows under .github
Note: bwc-test-workflow.yml is not included here because BWC tests were not added until 1.2
CheckList:
[x] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

:exclamation: No coverage uploaded for pull request base (1.1@6722347). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             1.1     #290   +/-   ##
======================================
  Coverage       ?   78.80%
  Complexity     ?      215
======================================
  Files          ?      172
  Lines          ?     6964
  Branches       ?      908
======================================
  Hits           ?     5488
  Misses         ?      987
  Partials       ?      489

Continue to review full report at Codecov.

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


Fresh dev install (0.20.4) has out-of-date notification upon first launch

Fresh install has out-of-date notification upon first launch

We also have the same problem

hehe
maybe 'problem' might be a big word
2015-06-04 15:35 GMT+07:00 dittybijil<EMAIL_ADDRESS>
We also have the same problem
[image: last]
https://cloud.githubusercontent.com/assets/12061565/7980144/ae65a6a0-0ac2-11e5-9b2f-41088ced3dd0.png
—
Reply to this email directly or view it on GitHub
https://github.com/TelescopeJS/Telescope/issues/998#issuecomment-108785637
.

Working on it.


ADBDEV-1938-fix

Orca has a bug when a node can have no flow attached to it. The number of rows shown by explain depends on a distribution type, and the absence of a flow affects the correctness of rows number. Due to the complexity of orca, it was decided that fixing explain logic is more reasonable.
The number of rows for each plan is defined by scaleFactor, which differs for every type of distribution. By default, it is 1, but this fix sets it to the number of gangSize if the current slice is not null. The logic of scaleFactor was heavily simplified, so now it can be the number of the segments if a distribution type implies that the data is exchanged over the segments, like with MOTIONTYPE_HASH or MOTIONTYPE_FIXED, and it can equal 1 in that cases when the node is a Gather Motion type, otherwise it will equal the number of receivers.
This fix also changes the number of rows shown in json format. By default, it just shown plan_rows value, but now it uses ceil(plan->plan_rows / scaleFactor) as the normal output does.

The actual PR is #292


Fullscreen toggle doesn't work on Nebula Capsule

The Issue
On my Anker Capsule (https://www.anker.com/products/variant/capsule-projector/D4111111), the fullscreen toggle does not work.
Steps to reproduce

Downloaded/installed 1.0 APK.
Opened Odysee app.
Start playing video and try to toggle fullscreen.

Expected behaviour
The video should play in fullscreen.
Actual behaviour
After fiddling around with the mouse pointer, aligning it on the fullscreen toggle, instead of going to fullscreen, the video playback jumps to the position just above the fullscreen toggle.
System Configuration

Device: Anker Capsule
Android version: 7.1

Anything Else

Screenshots

This screenshot shows where I will click the fullscreen toggle:

Instead of going to fullscreen, the timeline was moved to above the fullscreen toggle - see the red line indicating where the time is now:

It looks as if the toggle is offset and instead the timeline responds.
Internal Use
Acceptance Criteria

Definition of Done

[ ]  Tested against acceptance criteria
[ ] Tested against the assumptions of the user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

Screenshots added.

This bug is about the non-native Odysee Android release. Odysee Android video player doesn't show any switch on its interface, while Odysee non-native one does.

I wasn't aware there are two versions. Is https://odysee.com/OdyseeAndroidApp:4 the native or the non-native version? How do I tell the difference? Forgive me if asking n00b questions, as I am not well-versed in the Android world.

That’s the non-native one. That’s the same Odysee published on the Play Store. The non-native one consists of the web pages people can access on their browsers but wrapped under some native code in order to make it work and also in order to perform more like a native one.
Latest native version is 0.0.16.
Non-native one is ok, but a little slower most of the time. Except when problems like yours, it is ok to be used.
Native one performs much much better. But it lacks some features and it is buggy and not yet ready. Unfortunately, there is currently no file available to be installed for tests.


Adds assisted-installer module in stable/prod

Follows up on #282

/ok-to-test

@jkilzi Can this be merged and released?


Fix type in Logout views

At this point we cannot accept PRs for new features, only bugfixes. Thanks!
What issue does this PR address?
Fixes typo in Logout view in sample apps
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[ ] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

thanks!"


CollapsingMergeTree Question

CollapsingFinalBlockInputStream: Invalid sign: 0
How do I solve this?

Sign column should have 1 or -1 values, you need to fix the program that have written 0 there.


A little help on how to configure using ADFS 2.0

Hi
I'm trying to integrate SSO for my Symfony 2 application. Our app should act as Service Provider and the authentication should be handled from our Active Directory ADFS server.
I already installed the latest bundle "lightsaml/sp-bundle":"^1.1" and configured the required classes as per the instruction.
So far the application is already redirecting to the /saml/login and /saml/discovery and the page displays all the available IDP's.
But I'm just confused on how/what to set the configuration based from the information that was gaven to me from our IDP. BTW our IDP I think is ADFS 2.0
Our IDP provided the following

Federation Metadata xml - which I downloaded and path it in the idp party config as follows;

    party:
        idp:
            files:
                - "%kernel.root_dir%/../src/AppBundle/Security/LightSAML/federationmetadata.xml"

Token signing certificate - where shoud I set use this in the config?

-----BEGIN CERTIFICATE-----
MIIDADCCAeigAwIBAgIQBLAHBLAHBLAH...
-----END CERTIFICATE-----

Entity ID URI - where should I set this in the config?
	http://fs2.federation.net/adfs/services/trust

Login URL (For System Configuration)
	https://fs2.federation.net/adfs/ls/idpinitiatedsignon.aspx

Login URL (Clickable, can be used for user login)
	https://fs2.federation.net/adfs/ls/idpinitiatedsignon.aspx?logintorp=<YOUR-URN>

Logout URL
	https://fs2.federation.net/adfs/ls/?wa=wsignout1.0

Now, they are also asking us to provide the following informations;

What federation protocol do you support? I choose "SAML 2.0" againts "WS-Federation".

Please list relying party Identifier’s. This may include a URN, URL or both.
What shoud I provide to them? Our application base URL?

Please list any Claims (assertion attributes) which you will require from us.
For example Email Address sent as NameID
Attribute | Set as

Thank You

Hello @andacu
Any results?
I am especially interested how you managed to handle the attributes. I am struggling to understand how to require IdP to provide attributes (email, first name, last name). I did a lot of googling and code inspections but still no clear vision how it works.


Add ability to set UJS handlers on a different HTML element.

Superglue brings back UJS handers to Rails. In superglue they often look like this
<a href={"/posts"} data-sg-remote>

They're very convenient and adds SPA functionality without the complexity of javascript. Its behavior is overridable in your application_visit.js that gets generated when you start a new superglue project so you can handle all your edge cases.
In superglue, its installed on the same appEl in application.js, also generated into your project.
https://github.com/thoughtbot/superglue/blob/091c076a45927237d8f8cc3dd7574cc70a6169ec/superglue_rails/lib/install/templates/web/application.js#L31
The appEl also gets passed internally to superglue's ApplicationBase (your application.js overrides this) here:
https://github.com/thoughtbot/superglue/blob/091c076a45927237d8f8cc3dd7574cc70a6169ec/superglue/lib/index.js#L158
where the event listeners are added to appEl immediately after that.
    appEl.addEventListener('click', onClick)

In other words, the UJS handers only listen on the appEl, which when considering some component libraries uses react portals to build modals or dropdowns, means that UJS doesn't work on those components because they exist outside the appEl. I'd like to see superglue optionally support passing a custom element to put the listeners on. It can be as simple as allowing a subclass of of ApplicationBase to more easily override. For example:
class Application extends ApplicationBase {
   ujsElement () {
  }

In that scenario `ApplicationBase` would need to define its ujsElement as defaulting to the `appEl` that gets passed to it.

Closing because it seems like it's already works


python312Packages.mkdocs-rss-plugin: 1.13.1 -> 1.14.0

Changelog: https://github.com/Guts/mkdocs-rss-plugin/blob/refs/tags/1.14.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 322717 run on x86_64-linux 1

4 packages built:

python311Packages.mkdocs-rss-plugin
python311Packages.mkdocs-rss-plugin.dist
python312Packages.mkdocs-rss-plugin
python312Packages.mkdocs-rss-plugin.dist


Add possibility to add ebs_volumes for nomad nodes

The current solution does not support to attach ebs_volumes to the nomad nodes.
NEW: With this change it is possible to inject ebs_block_device configuration into the launch configuration for the nomad nodes.
TEST: Tested with running/ self-contained examples setting up a nomad-cluster w. multiple dc's (see: https://github.com/MatthiasScholz/cos/tree/master/examples/root-example and https://github.com/MatthiasScholz/cos/tree/master/examples/nomad-datacenter)

@brikis98 I adjusted the PR:

Ran tf fmt for the files I touched
Fixed the typo
Added a small ebs block device to the nomad-consul-separate-cluster example

Hey @brikis98,
is there still something missing or something that has to be adjusted for this PR?

https://github.com/hashicorp/terraform-aws-nomad/releases/tag/v0.4.5

Perfect thanks.


log/slog: non-top level slog.Value marshals to empty json document

slog.Value always json.marshals to an empty document, "{}", which to me was surprising behavior when using JsonHandler.  If a slog.Value is embedded in a logged non-slog.Value, for example a slice, it will effectively omit data.  On the other hand any tree of Values and Attrs passed directly to the log functions, without an intervening non-slog.Value object, marshals and logs properly.  I expect a slice, or any other non-slog.Value type, containing an slog.Value to marshal to json with the slog.Value's represented value.  TextHandler produces the expected logs for the same pattern.
What version of Go are you using (go version)?
go1.21.0 darwin/arm64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
arm64, darwin (MacOS Ventura 13.5.2)
What did you do?
Original discussion at https://groups.google.com/g/golang-nuts/c/ZvlSL76RNaw/m/N1L_5f0vAQAJ?utm_medium=email&utm_source=footer
Demonstration at https://goplay.tools/snippet/H26amsQBiYG
There are other, arguably simpler ways to achieve my fundamental goals and I'm not blocked; I still find the behavior below to be surprising.
I logged, using slog and a JsonHandler, values containing types other than slog.Value (e.g., slices) which in turn contain slog.Value.  My goal was to use LogValuers to redact object fields by in turn calling LogValue on component objects.  The "outer object" has a slice of the inner objects and so the outer object's LogValue returns something resembling AnyValue([]slog.Value).
I additionally directly marshaled slog.Value.
What did you expect to see?
I expected slog to log the json representation of the "outer object" with a field containing the list of "inner objects".
I expected json-marshaled slog.Value to produce json representing the value.
Alternatively, the slog documentation (or specifically JsonHandler) could state that no non-slog.Value object passed to a log method may contain an slog.Value, and that LogValuers must maintain this invariant.
What did you see instead?
A list of empty objects: [{}, {}, {}]
slog.Value marshals to '{}'

CC @jba

#5901 would be helpful to teach the json encoder about slog.Value

I propose adding the following to slog, so that slog.Values marshal as the Go value they represent:
func (v Value) MarshalJSON() ([]byte, error) {
    return json.Marshal(v.Any())
}

@stevenpelley, does that solve your problem?
@dsnet, do you have any concerns?

I don't have any great answers right now, but recursively calling json.Marshal from Value.MarshalJSON can be O(n²) if v.Any can contain nested Value types. This is a known performance flaw with json.Marshaler (and json.Unmarshaler) and has affected other projects like Kubernetes and us at Tailscale.
I'll be presenting next week at GopherCon on a potential new JSON API that would fix this problem, but even then it would take many Go releases before it hits the stdlib (if ever).
That said, if you add MarshalJSON today, you would be able to backwards compatibly add a hypothetical MarshalJSONV2 method in the future without breaking any semantics.

I propose adding the following to slog, so that slog.Values marshal as the Go value they represent:
func (v Value) MarshalJSON() ([]byte, error) {
    return json.Marshal(v.Any())
}

@stevenpelley, does that solve your problem? @dsnet, do you have any concerns?

@jba I believe this provides the behavior I expect (without testing it or understanding the implementations of slog.Value and json.Marshal terribly well).

I don't have any great answers right now, but recursively calling json.Marshal from Value.MarshalJSON can be O(n²) if v.Any can contain nested Value types. This is a known performance flaw with json.Marshaler (and json.Unmarshaler)

@dsnet the concern makes sense.  Given that when someone logs with this pattern today their data won't be logged properly I'd argue for first producing the correct result and then waiting for feedback about the performance of JsonHandler and MarshalJson.  If I'm the first to report this then maybe it's not that common a pattern.  And in practice, for logging, I suspect "n" will be relatively small (obviously with no data and only my personal experience to back this up).
We could also note this performance business about embedded values somewhere around the documentation for func (*JSONHandler) Handle but I think that's discussing the implementation too much.

I'd argue for first producing the correct result and then waiting for feedback about the performance

Yea, I agree. I'm just saddened we can't do the performant thing today and we'll be adding API that can't be removed when the more performant thing one day arrives. But yes, I don't think we should block this issue for the next year or two on a performance fix.

It's already possible to arrive at an invocation of MarshalJSON by going down this branch of encoding logic in JSONHandler. There might be an argument that the risk of O(n²) marshaling cost is already present in the obvious scenario.
At a glance I was skeptical of Value.MarshalJSON but I have persuaded myself that the behaviors have parity with what happens inside TextHandler, or Value.String outside, in less obvious scenarios.


Support for GCP BigQuery via JDBC

Is your feature request related to a problem? Please describe.
Support for GCP BigQuery via JDBC
Describe the solution you'd like
Support for GCP BigQuery via JDBC
Describe alternatives you've considered
Support for GCP BigQuery via JDBC
Additional context
https://storage.googleapis.com/simba-bq-release/jdbc/Simba JDBC Driver for Google BigQuery Install and Configuration Guide.pdf

BigQuery Authentication Guide
GCP authentication is required for connection.
Here are two methods.
Service Account based Authentication
Download a Key using ServiceAccountEmail in the GCP Console.
Configure properties as follows using the key file path.

OAuth2.0 Authentication
AccessToken and RefreshToken are required to authenticate in this way.
To get the Access Token and Refresh token, we need to:

Create an OAuth ClientID to get ClientID and Client Secret.
Send an Authorization request to Google to get the Authorization Code.
Exchange the Authorization Code to get the Access Token and Refresh Token by sending a Token request to Google.


qpcr: Remove PCR Detection Chemistry as required field

References #180

@cnchengucsd that's for submitting your first PR to Allotropy!
In addition to @nathan-stender comments ☝ one more item we'll need before the PR can merge is a Contributor License Agreement signed per the CONTRIBUTING.md
If you can email me here<EMAIL_ADDRESS>I can send this over to you.
Thanks again for contributing!

Hey @cnchengucsd thank you for taking a stab at this! I went ahead and put this through so I could close out the issue.
https://github.com/Benchling-Open-Source/allotropy/pull/668
If you would like to contribute in the future, don't hesitate to reach out!


loggerd: c++ LoggerState

Can you rebase this?

A lot of the line reduction here is just from removing the thread safety, which is unrelated to the rest of the refactor. That should really be done in its own PR.

Merged anyway since we good tests around this now and it was pretty straightforward. Next time let's break it up though.

Next time let's break it up though.

ok!


Rearranging of menu items

It would make more sense for me to put the 'user-management' left beside 'projects'
The "Settings" should be renamed to simply "User" and placed behind a user icon to the right of the "Welcome, User" message.
"Administration" (now right menu) should be placed left besides "projects".
And the dropdown menu (as it is now) should at least contain the missing "logout"
Menu responsiveness has to be optimized.

Will be included in next pull request.

Looks way better now :) Thanks for adding icons.
Thanks and closed.


fix windows tests

testament (The nim test runner) cannot run the tests on Windows apparently, because the regex doesnt work (?)
This is gonna get fixed once I have access to my Windows machine again.
Originally posted by @froehlichA in https://github.com/froehlichA/pax/issues/45#issuecomment-882088386

fixed already.


Bug 2168032: service name with random chars

📝 Description
When the user selects a different service type, create a service with random chars.
So the service name would not be an issue for fast users

/approve


Bug/fix library jsx use effect issues

This PR resolves issue #160 opened by @gbowne1.
Changes Made:

Added setFilter prop to Library component.
Added clean up function to the useEffect to clean up setMyRows and setFilter functions when component unmounts.
Added 'myRows' to the dependency array of useEffect.

@BlackBond06 That was your 5th successful merge.  I sent you a Collaborator invite.  Thanks so much!for all of your great contributions.  Welcome aboard.

Welcome buddy @BlackBond06 🤝🙌

Yay!!! Thank you @gbowne1 @LOGESH-B

You're welcome! @BlackBond06


[BUG] New Image Assets Are Exceedingly Large

Describe the bug
This is not really a bug, exactly, but rather a performance hinderance.
Hero image assets for the platform pages are much larger than they need to be resulting in file sizes that are also very large, and can reduce page performance.

/assets/media/platform/platform-hero-search.png: 705KB, 5000x1688. The largest width it will ever need to be according to the design is 1280 pixels.
/assets/media/platform/platform-hero-observability.png: 794KB, 5000x1667. Also only requires to be at most 1280 pixels wide.
/assets/media/platform/platform-hero-security-analytics.png: 838KB, 5000x1667. Also only requries to be at most 1280 pixels wide.
/assets/media/platform/Core.png:  651KB, 1200x800. Only required to render at most as 600 pixels wide.
/assets/media/platform/Dashboards.png: 701KB, 1200x800. Only requried to render at most as 600 pixels wide.
/assets/media/platform/Data-Prepper.png. 725KB, 1200x800. Only required to render at most as 600 pixels wide.
/assets/media/platform/platform_hero_simple.png: 111KB, 6001x1459. 1440 pixels is the largest width required.
/assets/media/platform/mobile-platform-simple.png: 202KB 1200x800. Max width rendered is 794px

Downsize the image assets appropriately.

Hi, I would like to contribute to this, please assign this issue to me.

The images look like they are back to a reasonable size. If you see any that are off, feel free to PR a fix.


Add 7050 chip user manual to datasheets folder

The 7050 is part of a family of chips called VIPower by its manufacturer STM. There is a user manual for the family that includes a lot of useful information on how to use an configure the chips. I've put it into the datasheets folder as UM1693.pdf

Also updated power-test-config.odg, and voltage-dividers.odg to reflect changes in 5V current measurement technique.


Bug: Not archiving Twitter correctly

Describe the bug

No screenshot, single file, and output.html are saved.
And not the tweet itself "Hmm...this page doesn’t exist. Try searching for something else.".
Check the screenshot
Steps to reproduce

Open your ArchiveBox instance.
Archive any Twitter tweet.
Check for yourself.

Even in your own demo instance it doesn't work!
 Warning: Missing 1 recommended dependencies
    ! RIPGREP_BINARY: rg (unable to detect version)

btw, I tried to save tweets with headless chromium and i got the same result.

Yup, you should use Nitter or another alternative frontend instead of twitter. Twitter has always been very broken. This is also true for Reddit -> Teddit, Instagram -> Bibliogram, and a couple other big companies that implement advanced bot-detection and blocking.  It's not ideal but it's better than not having any solution.

Yup, you should archive the equivalent Nitter URLs (or use another alternative frontend instead of twitter). Twitter has always been very broken. This is also true for Reddit -> Teddit, Instagram -> Bibliogram, and a couple other big companies that implement advanced bot-detection and blocking, see a longer list of alternative front-ends here: https://hackmd.io/MCpUlTbLThyF6cw_fywT_g?view. It's not ideal but it's better than not having any solution.
Follow here for updates: #345

That's what I thought at first, but I opened an issue so if anyone can help or find out any solution, because I've tried many archiving solutions, and some work arounds, ig the only one worked was pywb. But thanks, I'll take a look at the link in your reply.

Yeah if you're doing a lot of twitter/fb/insta/etc. archiving I highly recommend https://github.com/webrecorder/browsertrix-crawler, it uses the same engine as pywb and is written by the same team.
Check out their whole suite here: https://webrecorder.net/

Okay, thank you so much.


Fix Decimal type category

It may be more useful by using DryTypes::Params::Decimal.  Because DryTypes::Coercible::Decimal fails coercing 45.1 for json reqeust.

Not sure what happened to the bot, but this fixes a bug and needs a changelog entry, please.

Thanks


Comment doesn't work

Get the Error :( when selecting synonyms. We thought this might be related to public vs. private, but some testing indicated an actual code issue.

This problem originates from our hacked code in paleobot/neo4j-graphql-js.
There is a fix for this in
paleobot/neo4j-graphql-js@d847cab096ab77f50148531720904f73e52e3d5e
paleobot/neo4j-graphql-js@cc7f9ea40939b0cc7c8c06974461ec53de3e6528
I am keeping this on the ddm-dev branch for now until we see if there are any side effects. It is running on dev via a temporary mod to package.json.

I made a new synonym and then tried to comment on it. After pressing submit I received the following error message as the Results:
Error: Variable n not defined (line 1, column 9 (offset: 8)) " RETURN n" ^
I also used the search function for the taxon I proposed a synonymy for (and clicked include synonymies), but the results page does not yet show the synonymy.

So it sounds like there was a problem with creating the initial synonym rather than with the comment.
Just for Doug's convenience. I believe the OTU's she is mentioning are "JAY" and "Arial" if you want to look at the logs.

Interesting, I can find the synonymy that I made when I go to make a comment, or when I choose to 'edit' a synonymy. I made the one between Platanites raynoldsii and "Eatibus" anythingus

Regarding all the June 4 comments: what machine were you trying this on? The fix was only running on dev at that time.
It has since been merge to master in paleobot/neo4j-graphql-js and is running on both dev and prod(stage)

I was probably trying it on dev. However I just tried on prod, after making a synonym for "Jose Creek dicot DT26" and "Hack-A-Thon OTU 230808.CC.1".
I was able to make the synonym. But I could not add a comment to it - when I tried to submit the comment it gave this error:
Error: Variable n not defined (line 1, column 9 (offset: 8)) " RETURN n" ^

The "n" issue was a separate problem from the original. This one was due to improperly generated cypher code in the isDuplicate routine of Resolvers.js.
This is fixed in
paleobot/pbot-api@44179fc45b7fd74ce978d218d8780b08fd47b5c5
currently on ddm-dev branch and running nowhere


Remove Provider Name from App Service Endpoints and Database Attribute

Description:
The purpose of this ticket is to remove the 'provider' attribute currently in use throughout the app service endpoints and within the 'offers' database table. The reliance on the 'provider' name should be replaced by using the 'provider_company_id' which references the 'companies' table where the company name is stored. This change involves both database schema updates and modifications to the application's backend logic to ensure a smooth transition and continued functionality.
Acceptance Criteria:

Remove the 'provider' field from the 'offers' table in the database.
Update all backend services and endpoints that currently utilize the 'provider' field to instead use 'provider_company_id' for lookups.
Ensure that the 'companies' table and its 'name' field are correctly referenced wherever the provider's name is required.
Refactor any code, queries, or stored procedures that use 'provider' to adhere to the new schema.
Update all affected API responses to ensure consistency and avoid breaking changes for front-end services.
Conduct a thorough search to confirm that no legacy code remains that references the old 'provider' attribute.
Test all endpoints for functionality to confirm that the correct company names are retrieved and displayed. //please test all the app controller endpoint which include a name, companyName or providerName

Technical Implementation:

Create a migration script to remove the 'provider' column from the 'offers' table.
Update the application's data access layer to stop referring to 'offers.provider' and use 'offers.provider_company_id' with a join to 'companies' to retrieve the 'name'.
Modify any business logic that depends on the 'provider' field.
Search for and refactor any API endpoints that include the 'provider' field in the response.
Update unit tests and integration tests to reflect the changes in the database schema and application logic.

API Changes:

please ensure that this change has no impact on the API payload

@ntruchsess please take over

@MaximilianHauer already developed that one and created a pr.
@ntruchsess fyi


Fixed last updated column in UI for some flux primitives

Closes #2026

What changed?
Sending the right time format from the BE to populate Last Updated column in UI for all flux primitives except Kustomizations and HelmReleases, those are going to be fixed in a follow up PR.

Why was this change made?

How was this change implemented?

How did you validate the change?

Release notes

Documentation Changes

🌞  LGTM 🌞


/xinfo /info report wrong Songbeamer version

Both functions report "6.04" instead of "6.04a" which is installed
system: ** Log cleared **
debug: Sent OSC to <IP_ADDRESS>:10023 with /xinfo and []
debug: Received OSC message from: {"address":"<IP_ADDRESS>","family":"IPv4","port":10023,"size":64}
debug: OSC Content is: {"address":"/xinfo","args":[{"type":"s","value":"<IP_ADDRESS>"},{"type":"s","value":"osc-server"},{"type":"s","value":"SongBeamer"},{"type":"s","value":"6.04"}]}
warn: received a message with an unknown address - not implemented
debug: Sent OSC to <IP_ADDRESS>:10023 with /info and []
debug: Received OSC message from: {"address":"<IP_ADDRESS>","family":"IPv4","port":10023,"size":56}
debug: OSC Content is: {"address":"/info","args":[{"type":"s","value":"V2.08"},{"type":"s","value":"osc-server"},{"type":"s","value":"SongBeamer"},{"type":"s","value":"6.04"}]}

Followup form #20

[ ] Check that songbeamer sends correct version information

[ ] confirm that OSC Server version "v2.08" is set on purpose and is not a leftover from /Xair

v2.08 is indeed a leftover from X32. I'm not sure what do use here for SongBeamer.
I will add the version letter to the response.

do we even need /xinfo ?

The letter will be reported in SongBeamer 6.04c.
v2.08 is still there, I'm not sure what to put there instead.
/xinfo and /info are in the "ancestor class" of the SongBeamer OSC class. I use them for my X32 app. So I prefer to leave them there. I'd recommend using /xinfo because that seems to be the newer command, and it doesn't have the v2.08 in the response.

I believe that v2.08 is the version of the osc server component. I'll leave it there as it is. The SongBeamer version is now correctly reported as the last value.

was fixed in some release.


Custom container validations is not working properly

Custom container validation on fields is not working properly
eg empty string entrypoint for this container here : https://market.oceanprotocol.com/asset/did:op:90b42b379869c2305e4b87bbf307b32cc106930c42c38009e28ca20c816842fb

@bogdanfazakas what is the severity of this, and how much effort would take?


Larval NPF neurons

Added classes for larval NPF neurons from FBrf0229899
fixes #242

See comment on larval pars lateralis.  Otherwise good.

I don't see the comment...

Sorry.  Didn't realise I needed to press 'submit review'.  Have now.


Is this Project Still Alive AND KICKING?

I have been experimenting with swift as a replacement for nodejs micro services. It seems that the server side Swift world has cooled off a lot. As best I can tell only Vapor is in active development. But I’m not sure. Is Zewo still being ACTIVELY developed or will it?

Even though Zewo is a really nice project, unlikely it will have a future. Only Paulo can answer that with 100% of confidence, but since we are not seeing any activity in the last few years, I don't think it should happen soon.
I am going to close this issue, but do not to hesitate if you have any further point.


This takes priority over games

I absolutely love this!! Only issue is that it takes priority over games and shows on Discord instead of the game I'm in. Is there a way to fix this? Thanks for this plugin though 💜💚💙🧡💛

that's how roch presences work. You can disable the foobar addon from foobar settings

Oh ok, thanks!


Add input_instructions, short_title, short_descripton.

Adds input_instructions, short_title, and short description.  Areas where this shows up in the legacy program interface in screenshots below.  Note that short_title wouldn't be in the top progress area because we do not have that in inferno-core, but it is still useful to have this option for our nav menus on the left / and potentially if we use breadcrumbs.
All are optional.  short_title is used in place of title in some places.  If a short_title doesn't exist, title is used instead.  If short_description doesn't exist, the area would be blank in the interface, as description may be very long. It may be a little strange that these two similar concepts behave differently, but I modeled it after our legacy implementation for now.
I updated the ruby backend and swagger.  I did not incorporate this into the front end, as that is mixed in with another visual update I"m working on now.

Codecov Report

Merging #76 (0a4eeb0) into main (9122bd9) will increase coverage by 0.06%.
The diff coverage is 100.00%.

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

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
+ Coverage   94.21%   94.27%   +0.06%
==========================================
  Files          99       99
  Lines        2368     2395      +27
==========================================
+ Hits         2231     2258      +27
  Misses        137      137

Impacted Files
Coverage Δ

...tes/dev_infrastructure_test/infrastructure_test.rb
92.59% <100.00%> (+1.28%)
:arrow_up:

lib/inferno/apps/web/serializers/test.rb
100.00% <100.00%> (ø)

lib/inferno/apps/web/serializers/test_group.rb
100.00% <100.00%> (ø)

lib/inferno/apps/web/serializers/test_suite.rb
100.00% <100.00%> (ø)

lib/inferno/dsl/runnable.rb
95.97% <100.00%> (+0.24%)
:arrow_up:

Continue to review full report at Codecov.

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


GPU-compatible image stream

Data format should support GPU-hosted memory locations. Need to address synchronization issues. NVIDIA's managed memory is a model, but it suffers from sub-optimal performance because it forces synchronization between GPU and CPU memory even when not needed.

I vote for option 2 (at least initially)
I like your last suggestion: keep structure on CPU but allow for the image array to be located on either CPU or GPU.
This scheme can also support multiple GPUs: a variable in the metadata would indicate on which GPU(s) the data is.
We would provide functions to move data from/to CPU/GPU, and it would be quite straightforward to make these memory copies automatic by looking at the values of the memory flag(s)

I agree with you
To be honest, I already started to implement the solution 2

Beta version of GPUIPC  at 0682a97
I didn't do yet any non-regression tests.
You can to a try by compiling CACAO with -DUSE_CUDA=ON and compile make_gpu_tests.sh.c and ImCreate_test_gpuipc2.c (you can modify make_gpu_tests.sh to compile it)
execute first ImCreate_test_gpuipc, it creates a GPU SHM and put some data on it then waits a semaphore. Then execute the ImCreate_test_gpuipc2, it reads the GPU SHM, modify it and post a semaphore which it unlock the first one and it reads read again the SHM.
Again, be careful, I didn't do any non-regression tests

FYI, the feature branch has been tested on bench with keywords (EXPOSURE, ...) and framecounter from metadata. All process use CPU or GPU RAM buffer. I did'nt try mixed installation (using or not USE_CUDA flag)


:)

Hey there, I saw this and I was really impressed! Is it usable on Windows? Also, I can't seem to see the problem_id of a problem, even after inspecting element. Could you help? My email is<EMAIL_ADDRESS>, could we discuss there? Thank you so much!

It works on Linux system. Can be used on Windows using Linux subsystem for Windows.


Fix warning when adding new DynamicCamera in the editor

Fixes #321.
When adding a new DynamicCamera from the Cesium editor utility, it would pop up a warning that the camera wasn't parented to a CesiumGeoreference despite this being the case. By using the overload of Object.Instantiate that supports specifying the new object's parent transform, the DynamicCamera's parent will be set by the time it initializes, avoiding this warning.

Thanks @azrogers !


Uncaught TypeError: Cannot read property 'hasLiquidFire' of undefined dependency-checker.js:5

After installing this plugin I get an error from dependency-check.js.

What versions of ember/ember-cli are you on? Also, does your project's package.json have ember-cli-dependency-checker in its devDependencies?
I guess this assumes it's there but we should really make it part of this addon's dependencies.

I have ember 2.7.0 and ember-cli-dependency-checker ^1.2.0.
It's now fixed. It was an error on my project, my config/environment was wrong.


Update LoadEnvForServers.cfc

Missing dependency and wrong struct calling for setting the JVM.

Sorry, I wasn’t subscribed to this repo.

How are you not subscribed to your own repo? :)  @evagoras can you confirm if your fix is still needed on the latest version of the code.

I don’t think it was the default for a while. There are a few repos like that for me.

Hi, @evagoras.  Is this still needed?

@elpete it looks like this is no longer needed. Thanks for the automatic fix!


Move Confluence data over for team oboarding

Describe the issue
Julian has a lot of onboarding material in an old NRM confluence page (at risk of going away any day).  We can use this for our onboarding.
Additional context
Add any other context, attachments or screenshots
Definition of done

Julian to copy over our onboarding material to Teams

Onboarding content has been updated and significantly rewritten


Interactions betwen Floating Panel on top of Floating Panel

Ideally would love to present a modal Floating panel, then from that show another Floating Panel - where the top FP can be swiped to dismiss without also dismissing the parent FP.
Is this possible? Thanks

I make sure to understand your condition. Do your app present a panel as modality from a panel(presentingVC) as modality?


Fix: Run sanity and integration tests with kind

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build 958493567

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 37.235%

Totals

Change from base Build 944221410:
0.1%

Covered Lines:
1177

Relevant Lines:
3161

💛  - Coveralls


[Explorer] Some problem for question 5fe43e97-81ec-40d5-b23f-74ce5ef76c0e: Who has similar interests to user @gaearon

Bug Report

Describe the bug
Hi, I have some problems with the question 5fe43e97-81ec-40d5-b23f-74ce5ef76c0e: Who has similar interests to user @gaearon (errorType =error-validate-sql):
The front-end presentation of the bug was not as expected.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context

It's too hard for TiDB to resolve such questions... a graph database would be better


Fixed typo in http_client (IDFGH-11675)

Corrected the module name in the error log.

 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.

@s1tnk

Please squash the commits
Please update the commit to something like fix(esp_http_client): correct the typo in the error log string

Thanks for the advice.
I've resent it as #12796


first translations with the latest changes from the dev branch

New PR with the latest dev changes and the first translations

Summary by CodeRabbit

New Features

Dynamic content fetching for About, Security Tips, and Privacy Policy pages based on selected language.
Added dictionary support for Spanish translations of various components (about, auction, footer, home, security, terms, whitepaper).

Enhancements

Updated AuctionCard and Upcoming components to display dynamic text values from dictionaries.
Modified content structure to support dynamic updates based on fetched dictionary data.

Refactor

Adjusted type definitions to accommodate new dynamic content fetching mechanisms.

closing in favor of #227


Improve rule attribute chooser dialog

Jira: https://zrh-jira.esri.com/browse/CE-9280
This PR improves the rule attribute chooser dialog with the following features:

Two columns are added to the list of attributes: Attribute type, and default value.
Attributes are also separated by groups.
A text field to filter attributes by their name is added at the top of the window.

@bneukom I did address you comments and also added a check when the OK button is clicked, to count as a Cancel instead of Ok if no attribute was selected.
Would you like to have a last look before I merge ?


Tree view in rtl

#18853

[x] I have followed (at least) the PR section of the contributing guide.

Duplicate


fix: wait for initialize properly

Includes a few other small fixups as well:

Better name resolution (using gix)
(... more soon)

Closed in favor of #129


Unable to change color of blog icon

Issue
When right clicking on an icon from the Ghost Desktop app and selecting "New Icon Color" I am unable to change the color of the icon associated with the publication.

Additional Information
OS: macOS High Sierra v10.13.3
Ghost Desktop Version: version 1.5.2 (1.5.2)
Have also had confirmation of same issue from a Ghost(Pro) user running Windows 10, using the latest Ghost Desktop App for Windows.

Thank you for the report! The issue here is that the blog already has an icon, and thus, the color just isn't visible. I'll fix this somehow.


autotools: removed creation of "config.h" file

I removed the creation of config.h file, so that all the preprocessor symbol definitions go on the command line of the compiler.  The alternative is to include config.h in all the source files as internal header; this is not needed right now.

:+1:


Default GAU allocation amount is incorrectly calculated if there are multiple allocations to the default GAU in one Opportunity

Steps to reproduce:

Enable default allocations and set a default GAU.
Create a new Opportunity and set amount to $1000 (It will be automatically allocated to default GAU)
Click manage allocations and add an allocation for $500 (or any other amount) to the the default GAU (from step 1).
Click save and return to the list of allocations. There will be two allocations for $1000 each even thought the Opportunity total amount is $1000.
If you try editing the records using the standard UI, only one can be modified, the other one keeps getting reset to $1000.

Suggested solution:

Allow only 1 allocation to the default GAU on the same Opportunity.
Detect and delete duplicate default GAU allocations, and combine all amounts into one allocation.

This is fixed with https://github.com/SalesforceFoundation/Cumulus/pull/3513

Included in beta release 3.136 (Beta 2)

Included in production release 3.136


Revisit if order_by should concat or discard existing values

What conclusion did you come to?

Everything concats, we should concat here too and have an operator to clean up a field, like exclude/2 or discard/2.

Everything concats except the ones that raise (like select).


[Fix] prop-types: handle RestElement in destructured param

Summary
This pr fixes: #2804 .
Function parameter will have RestElement which do not have property value.
It will cause undefined property error.

Thanks!

Thank you for the quick review!

Same problem with ExperimentalRestProperty

@alexfdz an issue, or better, a PR with a failing test case, would be appreciated (and would be fixed the fastest)

Not fixed yet, e.g. property.type === 'ExperimentalRestProperty'

@minwe https://github.com/yannickcr/eslint-plugin-react/pull/2805#issuecomment-698896658 → https://github.com/yannickcr/eslint-plugin-react/pull/2805#issuecomment-699432511

@ljharb I have fixed error got when property.type === 'ExperimentalRestProperty'. Please review the PR, and release a new version if it's ok.


Cache dimension snakecase

It turns out that this piece of code gets run very frequently and accounts for quite a lot of runtime for xbrl extraction. In the test scenario, this improvements seems to produce ~15% reduction in extraction time.

Cool! I bet there are other speedups lurking in here too. Thanks for finding this.

Yep, I would like to test this in the full PUDL ETL before committing this PR, so I'm trying to figure out the right (and low effort) way to go about that as I'm assuming that this may not be the last such change.
I should probably also do a write-up/wiki doc for how to do profiling of the code to find stuff like this. It turns out that the multi-processing is kind of annoying and use of process executors here definitely got in the way of getting clean profiles.

For testing the altered ferc-xbrl-extractor is there a reason not to just check it out alongside the main pudl repo and then install it within your pudl-dev environment?
pip install --no-deps --no-cache-dir --editable ../ferc-xbrl-extractor

That should replace the version of ferc-xbrl-extractor that you've got in the pudl-dev environment locally with whatever version of ferc-xbrl-extractor you have checked out.  Then you can edit either repository as needed and re-run the tests or the full ETL with dagster and they'll reflect any changes in both pudl and ferc-xbrl-extractor.

Thanks, that definitely sounds like the easiest way to go about testing this.

I have tested this in the context of ferc_to_sqlite, sadly the benefits are minimal at that point. I suppose the multi-processing must be making the caches less effective or the bottlenecks are different in that scenario. I have avoided multi-processing for cpu profiling as it was more difficult to obtain the profile across process boundaries. I will try to look into this some more. We could submit this, but the benefits are likely not going to be as good as initially promised :-/

Seems like we might as well merge it in. It doesn't really add complexity and it'll improve performance in some computational contexts even if it doesn't right now, so why not?

I would like to re-run the analysis and that would be harder once this is merged in. In general, I'm a bit wary of optimizations that actually don't help :-/

Haha, okay well I'm fine with just closing it PR too. Splitting off the FERC extractions in our CI reorganizations will be a much much larger performance boost.

Let's merge. It may not help but it won't hurt and realistically, I don't have enough cycles to dig into this before I free up my plate of other things. You're right that more significant speedups will likely be brought by the sharding of ferc_to_sqlite


Unexpected reset of arglist when opening file from LF

Issue Description:
Upon opening a file from LF, the arglist unexpectedly resets to only contain the opened file's name, disregarding any previous entries.
Steps to Reproduce:

Create two test files, one.md and two.md, using the command:

touch one.md two.md

Open one.md with Neovim:

nvim one.md

Within Neovim, run the command :arg which outputs [one.md].

Open LF using the :Lf command.

With LF open, highlight two.md and press enter to open it.

Now run :arg command again. This outputs [/home/mroavi/lf-bug/two.md], meaning the arglist has been reset to contain only two.md.

Problem:
This behavior of resetting the arglist to contain only the newly opened file from LF becomes problematic for users who rely on the arglist for various purposes. Ideally, the arglist should retain its previous entries and add any new file opened from LF, rather than completely resetting.

This bug was introduced in ffcacf5dbbda7f523b5450c9c221e04070ab0e6a

All you have to do is change your default command from drop to argedit.

I added a keybinding for it in the latest commit. It is <C-g>


please help me with this issue raised on stack overflow

https://stackoverflow.com/questions/73560409/how-do-i-get-indices-if-theres-overlaps-and-nan-if-not-with-pyranges

I replied in Stack Overflow


Prevent draws when there are no visible views

Closes #12

In JS we use an IntersectionObserver to keep track of the visibility of the widget views.
We use this to set the new has_visible_views trait.
In Python we only actually draw if has_visible_views is true.

Also adds a notebook to test this behavior.
This can be a major performance boost in cases where you have multiple widgets that are continually updating, because these share the available IO and CPU resources. With this PR, when one widget goes out of visual scope, the others become faster.

Ready for review BTW :)

nothing looks really wrong

Awesome :)
I also added some comments and tried to clarify the top post of this PR a bit.


Added Moralis to data indexers

What changed? Why?
Added Moralis to the data indexers page in docs.
Notes to reviewers
How has it been tested?
Does this PR add a new token to the bridge?

[x] No, this PR does not add a new token to the bridge
[ ] I've confirmed this token doesn't use a bridge override
[ ] I've confirmed this token is an OptimismMintableERC20

Please include evidence of both confirmations above for your reviewers.

Left minor comments wrt wording.

Review Error for taycaldwell @ 2024-03-19 21:59:12 UTC
User cannot review their own commit


[V4.25.0] CreateViewGenerator issue

Search first

[X] I searched and no similar issues were found

Description
CreateViewGenerator.generateSql is not creating the correct SQL when isFullDefinition is false and replaceIfExists is true.
Code should read something like this around line 81:
.prepend("VIEW")
.prepend(" ");
if (statement.isReplaceIfExists()) {
viewDefinition.prepend("CREATE OR REPLACE");
}
else {
viewDefinition.prepend("CREATE");
}
Steps To Reproduce
use fullDefinition false and replaceIfExists true on a view that exists
Expected/Desired Behavior
SQL should be CREATE OR REPLACE
Liquibase Version
4.25.0
Database Vendor & Version
Oracle 19.3
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
Oracle 19.3
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

@adamjones0101 - thank you for this issue. Since you already identified the code that would need to change, would you be willing to submit the change as a PR?

I could.  I had to make a little more change to CreateViewGenerator.java to get it to work right.  However, I have not been able to fully test our changesets because of https://github.com/liquibase/liquibase/issues/5359 which is a serious regression.  Therefore I hesitate to submit the PR at this time.

I do not have a Git environment from which I can create a PR, I only download the zip, build it and use it within our product.
However, I am attaching my changed file for anybody to review and push
CreateViewGenerator.zip

Hi @adamjones0101,
I think this issue could have already been fixed by #5304. Would you mind trying on the latest liquibase version?
Thanks,
Daniel.

It's not a high priority because we are still blocked by Issue 5359.  In fact we are considering using Version 4.15.0 with the hope that the issue had not yet been introduced.

If it becomes something required to fix, could you please expand a little bit more on the steps performed to reproduce this issue? Which command were you trying to execute when you faced this issue, changelog example, etc? If you were trying to execute a generate-changelog or diff command I would recommend you to try with latest version when you have some time.
Thanks,
Daniel.

I'm going to close this issue as possibly fixed by #5304 in a more recent version. If this issue persists, please reopen 👍

Thanks.  Having this fix is good.  Unfortunately it isn't sufficient for us
because we have over 600 createView replaceIfExists changesets with SQL
that starts like this:
-- CREATE OR REPLACE VIEW VIEWNAME_XXX AS
It may have been done as a pseudo comment, I don't know but because the
query already contains CREATE OR REPLACE, CreateViewGenerator doesn't think
it needs to make any changes.
I replaced the check with this:
if (viewDefinition.contains("CREATE") {
viewDefinition.replace("CREATE", "CREATE OR REPLACE");
}
and this resolves our issue.
On Wed, Aug 28, 2024 at 12:07 PM Adam Murray @.***>
wrote:

Closed #5353 https://github.com/liquibase/liquibase/issues/5353 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/liquibase/liquibase/issues/5353#event-14049612291,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQSMROYTMA4VLRIU34KHZTZTXYTPAVCNFSM6AAAAABAQQONV2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGA2DSNRRGIZDSMI
.
You are receiving this because you were mentioned.Message ID:
@.***>


Remove the PDSHole class duplicate and use the outter one.

The inner class PDSHole in the outer class PDSLayer is not necessary anymore. We can use the PDSHole class in Padstack directly.
Fix #574.

LGTM. Maybe in the future we can make PDSHole indipendent from any Class

@maxcapodi78 Agreed. I think that is something we could do.


++WATCHLIVE]TV!] Tim Tszyu vs Murtazaliev Live Streams Free TV CHANNEL ON 20 OCT 2024

Tim Tszyu's ascent toward boxing superstardom was slowed in his last outing when he dropped a split decision to Sebastian Fundora in a bloody war, losing the WBO junior middleweight title in the process. Tszyu looks to get back on track on Saturday when he faces IBF champion Bakhram Murtazaliev.
🔴🌍📺📱👉GO LIVE==►► CLICK HERE TO STREAMING
🔴🌍📺📱👉STREAMING==►► CLICK HERE TO WATCH LIVE
🔴🌍📺📱👉GO LIVE==►► CLICK HERE TO STREAMING
🔴🌍📺📱👉STREAMING==►► CLICK HERE TO WATCH LIVE
TBakhram Murtazaliev will defend his IBF super welterweight title against Tim Tszyu in a Prime Video main event tonight at 8 pm ET.
Tszyu is looking to bounce back from a bloody loss to Sebastian Fundora in March, while Murtazaliev is stepping up his competition in a big way and looking to join the elite ranks at 154.
Wil Esco will be here with the live coverage in the stream below, including round-by-round for the main event, plus results and highlights. Join us!
Main Card (Prime Video, 8:00 pm ET)
Bakhram Murtazaliev (22-0, 16 KO) vs Tim Tszyu (24-1, 17 KO), super welterweights, 12 rounds, for Murtazaliev’s IBF title
Mateo Tapia (17-0, 10 KO) vs Endry Saavedra (16-1, 13 KO), middleweights, 10 rounds
Yoenis Tellez (8-0, 6 KO) vs Johan Gonzalez (35-3, 34 KO), super welterweights, 10 rounds
Dainier Pero (8-0, 6 KO) vs Willie Jake Jr (11-5-2, 3 KO), heavyweights, 8 rounds
Justin Viloria (6-0, 4 KO) vs Diuhl Olguin (16-40-7, 10 KO), super featherweights, 8 rounds
This is a fight that has every chance of being on Fight of the Year lists when the dust settles. Tszyu should be able to weather some tough spots in an exciting bout to regain a status as world champion. Pick: Tim Tszyu via UD
Bakhram Murtazaliev: A rising star in the boxing world, Murtazaliev is known for his explosive power and unyielding determination. Hailing from Uzbekistan, he has worked tirelessly to hone his skills, often training in the mountains, where the altitude builds his endurance. Bakhram is not just fighting for himself; he carries the hopes of his family and country on his shoulders.
Tim Tszyu: The Australian boxing sensation, Tszyu is the son of the legendary Kostya Tszyu. With a mix of technical prowess and innate instinct, he has become a household name in the sport. Tim’s journey is driven by a desire to prove himself outside of his father’s shadow, carving his own path in the boxing world.
The Fight:
As the bell rings, Bakhram comes out strong, utilizing his agility and quick footwork to evade Tim’s initial jabs. The crowd roars as Bakhram lands a powerful right hook, sending a message to Tim: he’s not here to play.
Tim, however, is unfazed. With his experience and tactical approach, he begins to adapt, using his superior reach to keep Bakhram at bay. As the rounds progress, both fighters exchange blows, their faces showing the signs of a hard-fought battle. Bakhram’s relentless energy clashes with Tim’s strategic composure, creating a mesmerizing dance of skill and heart.
In the fifth round, the tide turns. Bakhram, feeling the adrenaline surge, goes for a knockout. He charges forward, but Tim counters with a perfectly timed uppercut that connects with Bakhram’s chin. The arena gasps, the impact reverberating through the crowd. Bakhram stumbles, but the fire within him ignites. He recovers quickly, proving his resilience.
With each passing round, the intensity builds. The fighters are pushed to their limits, exchanging punishing blows that echo like thunder in the arena. Bakhram’s speed meets Tim’s strategy in a relentless back-and-forth. As the final round approaches, both warriors know that victory is within reach.
The Climax:
In the last round, the atmosphere is electric. The crowd is on its feet, chanting the names of their champions. Bakhram, fueled by the roar of his supporters, unleashes a flurry of punches. Tim, feeling the pressure, retaliates with his signature combinations.
The final moments are a blur—a whirlwind of fists flying, sweat dripping, and hearts racing. The bell rings, and the fight comes to an end. Both fighters stand, battered but unbroken, knowing they have given everything they have.
The Aftermath:
As the judges’ scores are tallied, the atmosphere is thick with tension. Fans from both sides hold their breath, waiting for the announcement. The decision is finally revealed, and regardless of the outcome, both fighters embrace in mutual respect, acknowledging the heart and soul poured into the ring.
In the end, Bakhram Murtazaliev and Tim Tszyu walk away as champions in their own right. They may belong to different stories, but tonight, they wrote a new chapter in boxing history—a testament to the spirit of competition, perseverance, and the unbreakable bond between warriors in the ring.
Bakhram Murtazaliev will defend his IBF super welterweight title against Tim Tszyu in a Prime Video main event tonight at 8 pm ET.
Tszyu is looking to bounce back from a bloody loss to Sebastian Fundora in March, while Murtazaliev is stepping up his competition in a big way and looking to join the elite ranks at 154.
Wil Esco will be here with the live coverage in the stream below, including round-by-round for the main event, plus results and highlights.


Add establish tests

Addresses #360
Main changes:

2 new unit tests to the Amount struct

one for testing negative numbers
one for testing zero

Tests were added to Amount struct rather than integration test suite because establishing channels with negative/zero balance errors out before ever attempting to run the command

Admin note: Github will automatically close issues if you link them with the words "fixes", "closes" or "resolves" in the PR description.
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword
You can also manually add them in the "development" tag on the sidebar.


Detect kubelet and container runtime frequent crashes

This PR adds customer plugin that watch systemd logs for frequent kubelet and container runtime crashes. It reuses log counter for frequent crash detection. Notice that kubelet and container runtime restart logs are actually in systemd logs, not in kubelet or container runtime logs.
Noticeable changes:

Change log counter to watch journald instead of kmsg.
Update docker monitor to use dockerd as the source name.
Fix vet errors
Update README on injecting systemd logs

/assign @Random-Liu
/cc @dashpole
/cc @jiayingz

@Random-Liu, I have updated this PR with delay option. PTAL

/retest

Rebased

/lgtm

/approve


Reflection API Wasm Bindings Part1

This PR does 2 main things:

Exposes many more Reflection API functions to the WASM API
Adds support for typescript definition generation using embind

 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.

/format


Weekly Scrum - March 6, 2022

Last week:

N/A

Next week:

#3

Blockers:

None

Last Week:

N/A

Next Week:

Front-end design, design page with use of CSS

Blockers:

None

Last Week:

N/A

Next Week:

Diagram and Controller

Blockers:

None

Last Week:

N/A
Next Week:
Frontend HTML and CSS for Login and Signup pages
Blockers:
None


Draw brightness curve data as line chart

Parses the (timestamp,brightness) data from WALT and draws it as a line chart
Chart can be zoomed/panned

Future work: add ability to save chart

@adlr

Looks good. Merging.


[Project] URL based enhancements send invitations to contribute

Related with https://github.com/opencollective/opencollective/issues/4893
Todo:

[ ] URL should be updated with amount when it's changed. router.replace, not router.push
[ ] URL should be updated with quantity when it's changed.
[ ] quantity should be supported
[ ] URL should be updated with interval when it's changed (month, year). Introduce an interval value for one-time.
[ ] URL should be updated with platformTip? But maybe we don't want. Ignore it if not supported by the collective.
[ ] Check behavior of interval if not supported by a specific tier. Enforce API side.
[ ] Check behavior of amount if it's invalid on a specific tier and we pass a contributeAs
[ ] URL should be updated with contributeAs when it's changed. It should be simply ignored if not supported for the user.
[ ] Rename interval to frequency?
[ ] skipStepDetails doesn't seem useful, linking to /profile is enough
[ ] Linking to /payment directly should be supported
[ ] People should be able to pass a default email and name.
[ ] Use shallow=true when replacing route (see https://nextjs.org/docs/routing/shallow-routing)
[ ] Ability to link directly to summary?

Will not be supported with this work:

[ ] Invite an Organization (or non individual) to contribute to a Collective
[ ] Draft Contribution? At payment step, decide to not pay now and receive a notification or a link
[ ] Do something similar to Order confirmation (Strong Customer Authentication)
[ ] Change or select a tier in the middle of the contribution flow
[ ] Change or select a sub-account in the middle of the contribution flow
[ ] Introduce an Order page?

[ ] Start implementation (@Betree)

Status = Paused

I have started a PR in https://github.com/opencollective/opencollective-frontend/pull/7992 to update the URL with the state. I'm however facing an unanticipated constraint that increases the complexity of this issue: the state is currently decoded from the URL in getInitialProps. However, shallow routing (which we want to use to prevent unnecessary refetchs), skips those methods.
We could implement quick hacks, but the proper solution to resolve this is to move the state decoding (e.g. in contribution-flow/index) which will have other benefits such as improved code sharing between embed and regular flow.
Another challenge that I faced is that we'll need to keep supporting the legacy routes, which adds some more complexity to this issue: https://github.com/opencollective/opencollective/issues/5716.
For these reasons, and because updating the URL doesn't seem like the most impactful thing to do for people who are requesting this feature, I'm going to focus on the other aspects and will eventually come back to the state thing later.

All done & released!
Feature documented in https://docs.opencollective.com/help/collectives/contribution-flow#custom-contribution-amounts


Remove -fbackslash requirement

Use escape character char(27) to print colours instead. See FEH.

Fixed in 8ad60f2.


Archive lab.

Archived labs are read-only, and they can be moved back out of the archives, if there is interest in reviving them.
Signed-off-by: Tracy Kuhrt<EMAIL_ADDRESS>

Hi Tracy,
We are still developing on this repo locally and will be pushing our changes here in the coming weeks/months. So, not merging this pull request to archive the lab.
Thanks,
Haris

Got it, will keep this in mind going forward. Thanks.


Add login hint to msal-angular when using HttpInterceptor

Core Library
@azure/msal or msal
Wrapper Library
@azure/msal-angular
Description
It can be useful to add a login hint (in my case if the app runs in MS Teams and some basic user info is known)
How can a login hint be added easily when using msal for angular with an Interceptor?
I am talking about this function: https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal.html#authenticationparameters.__type-1.loginhint
So there is a parameter in MSAL - I just have no idea where to add this when using a wrapper library with interceptor.
Source
External (Customer)
https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal.html#authenticationparameters.__type-1.loginhint

@web265p3 Unfortunately, this is not possible in MSAL Angular v1. It is possible in MSAL Angular v2 via the authRequest property which enables you to pass additional parameters to the underlying acquireTokenSilent call: https://azuread.github.io/microsoft-authentication-library-for-js/ref/modules/_azure_msal_angular.html#msalinterceptorconfiguration
You can use the setActiveAccount API to set which account is used in the interceptor. And when #3281 is released, you will be able to set those properties dynamically at runtime.

Closing, as this is addressed in v2.


Fix Rubocop Errors in ServiceTemplate / ServiceTemplateAnsibleTower

Fixing rubocop errors in ServiceTemplate and ServiceTemplateAnsibleTower. Kept encountering these as worked on these files - thought it was time that they go ✂ !
@miq-bot cleanup/rubocop
@miq-bot assign @gmcculloug

🤖 👮 knows best.  Thanks.


Add .pipeline to .gitignore

Motivation
The .pipeline folder keep information needed only for CI/CD automation. Not related to project functionality or structure. Such files need to be ignored and not stored in repository.
Approach
Adding folder to .gitignore
Pull Request status

[x] implementation

Coverage remained the same at 86.053% when pulling 18b29fd40e992d275dc84910dccac61f48b4a9a1 on gitignore into 46e9bc3c10bd7cb8966e142559d24d7c433d3e4b on master.


Fix: add % method to BigDecimal (reviving dead PR)

From ghosted PR #9784. The branch is no longer accessible, but I've applied the patch and confirmed that the spec passes and adheres to the style.
This should fix #9782.

Looks like ARM 64bit is failing on the stdlib. Any way to see the error or reproduce it?
See https://github.com/crystal-lang/crystal/actions/runs/4577670506/jobs/8083403907?pr=13255

It's unrelated to this PR


firebase_messaging: changing getToken to rely on platform's getToken

intends to fix flutter/flutter#17699 and fix flutter/flutter#20378
Removing local cache of getToken() in the dart part of the plugin. Now getToken() calls directly its counterparts in the iOS and Android implementations. This enables obtaining its value without calling configure() or having to wait for a new token refresh.

@kroikie  BTW, there's this one too. it closes two issues! 😀

This PR fixes the hanging getToken() call for me in simulator as well.

gentle ping
@bparrishMines @kroikie

Can also confirm that this has fixed the getToken() hanging issue for me. Another respectful ping to @kroikie to accept this.

yeah, i messed up this branch/PR.  :(
sorry about that, I'll have to recreate it in another PR.

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@ffeu Please do and make sure you reference it from this Pull Request so I can come and show my support. Cheers!

@ffeu Are you planning on submitting a new PR as per your comment above?

@Hixie yes, give me just a few minutes

replaced by #869


How to convert the path to a blob or base64 on iOS?

On iOS I cant seem to fetch or read the file using fetch or the capacitor filesystem.
File is always "Not found".
On Android it returns: result.videoFilePath
On iOS it returns: result.videoUrl (with file://)
This can't be fetched since it only supports http.
The filesystem also says it's not found.
Any idea on how to solve this?
I've tried:
 const result = await Filesystem.readFile({
            path: filePath,
            directory: FilesystemDirectory.Library,
            encoding: Encoding.BASE64
        });

A normal fetch(result.videoUrl) won't work.
EDIT
This should work according to the capacitor docs:
const res = await CameraPreview.stopRecordVideo();

const base64 = await Filesystem.readFile({
        path: res.videoUrl
});

console.log(base64)

But this isn't working for me. File not found.

func captureVideo() throws {
        guard let captureSession = self.captureSession, captureSession.isRunning else {
            throw CameraControllerError.captureSessionIsMissing
        }
        let path = FileManager.default.urls(for: .cachesDirectory, in: .userDomainMask)[0]
        let identifier = UUID()
        let randomIdentifier = identifier.uuidString.replacingOccurrences(of: "-", with: "")
        let finalIdentifier = String(randomIdentifier.prefix(8))
        let fileName="cpcp_video_"+finalIdentifier+".mp4"
        let fileUrl = path.appendingPathComponent(fileName)
        try? FileManager.default.removeItem(at: fileUrl)
        // Start recording video
        // ...
        // Save the file URL for later use
        self.videoFileURL = fileUrl
    }

Not sure, but is the video deleted on capture?

@WcaleNieWolny did you say this kind of issue ?

@riderx no, but I did write an app that uploaded the recorded video into s3.
  async function record() {
    if (!isRecording.value) {
      isRecording.value = true
      await CameraPreview.startRecordVideo({ storeToFile: true })
    } else {
      isRecording.value = false
      const fileUrl = await CameraPreview.stopRecordVideo()
      console.log(fileUrl.videoFilePath)
      // const contents = await Filesystem.readFile({
      //   path: fileUrl.videoFilePath,
      // });
      // console.log(contents.data.length)

      const randomId = makeid(8)
      console.log(`Attempt to upload ${randomId}`)

      const urlReq = await fetch(`https://[redacted]/${randomId}.mp4`, {
        headers: {
          'Authorization': 'Bearer [removed]'
        },
        method: 'GET'
      })

      const uploadUrl = (await urlReq.json() as any).url as string
      console.log('upload url', uploadUrl)

      const { id } = await Uploader.startUpload({
        filePath: fileUrl.videoFilePath,
        serverUrl: uploadUrl,
        method: 'PUT',
        // parameters: fields,
        headers: {},
        // notificationTitle: 'Uploading to S3'
      });

      console.log(`Plugin returned ${id}`)

    }
  }

From what the user shared, I think it's an issue on the user's end. The proper way would be to read res.videoFilePath, but the user uses res.videoUrl which is undefined.
const base64 = await Filesystem.readFile({
        path: res.videoUrl // <--- here, please put "videoFilePath"
});


Dialog applies backdrop to itself

Greetings,
I am using the same code as provided in documentation (for custom dialog). When I open dialog, it applies backdrop to itself. Tested on Chrome Version 55.0.2883.75 m
By that I mean that it looks like:

My current workaround is that I apply custom css style to dialog.
CSS:
.dialog-fix {
  .md-dialog {
    background: #fff;
  }
}

HTML:
<md-dialog md-open-from="#custom" md-close-to="#custom" ref="dialog1" class="dialog-fix">
...
</md-dialog>

Also, I'd like to use this chance to thank you for the great job you are doing on this project :)

This is strange. Are you using the theme correctly?

It seems I have been applying it wrongly the whole time, although this is first time I had issue with it:
The way I was applying it was:

    <first-component ref="sidenav" v-md-theme="'firstTheme'"></first-component>

    <first-component v-md-theme="'secondTheme'"></first-component>

        <router-view></router-view>

When I applied theme to the wrapping div, it worked fine:

    <first-component ref="sidenav"></first-component>

    <first-component></first-component>

        <router-view></router-view>

Sorry for bothering you with this issue

@Sarpedion Don't worry. I will make some improvements over themes in the nexts versions, so issues like that will be fixed.


Add duster

Great, thanks @rissajackson! I'm guessing the tests are failing because you'll have to modify the composer install step to account for Nova, which you can probably see an example for in the "test" GitHub action for this repo. LMK if you need any help.

Waiting on changes to Duster to go through before getting back to this.


Add image autocleaner

This option is created in order to clean old images after update

Looks good to me! Although personally I'd rather just use docker system prune.
It would be good to have an explaining sentence in the README, like for the other options. Can you add that? Otherwise I will do it.
Also, I will probably squash your commits into one.

Looks good to me! Although personally I'd rather just use docker system prune.
It would be good to have an explaining sentence in the README, like for the other options. Can you add that? Otherwise I will do it.
Also, I will probably squash your commits into one.

Good day! I added explanation to README; squashing commits seems like a good idea. About docker system prune - at first we decided to go that way, but we found that unsafe because you might unintentionally delete something you wanted to keep. This script ensure you clean only images of this exact service, which was updated, and no others will be affected.

Thanks!


Update MD file on new branch 2017-25-30_07-11-29

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


DSB modulation?

Hi there, thanks for working on this mod of F4HWN, I like your priorities for using the available memory.
I was just wondering if there is free space to enable DSB mode transmission? I'm not sure if it's a build variable or if it requires applying patches, but it's available on these two firmwares:

https://github.com/spm81/MCFW_UV-K5_Open_Source_Firmware
https://github.com/phdlee/uvk5cec

Thanks again, have a good one.

Looks like it'll need a good chunk of changes, but unfortunately I don't know enough about this firmware yet to attempt such an undertaking :disappointed:...

Hi there, thanks for the reply. I see, I thought it would maybe just be an easy build option. Thanks anyway! Do you want me to close this request or leave it open?


Merge dispatch

I would like to use parts of the dask.dataframe merge codebase for dask-cudf merge.  To do this, I need to replace instances of pd.merge with some generic dispatchable merge function.
We do this today in many places throughout the codebase for systems like cudf, sparse, and cupy.  For those we use our custom singledispatch implementation.  The merge function is different in that we probably want to dispatch against two inputs.
The natural thing to do here from my perspective is to use the multipledispatch library.  How do people feel about this?  We would have dask[dataframe] depend on multipledispatch, and add a dispatch definition in the dask codebase that included just the pandas case.  Other libraries would then import and extend this dispatched implementation.
cc @jcrist @martindurant

What kind of dispatch do you think needs to be done here?
For a function merge(df, df) -> df with 2 types (pandas, cudf), the following might take place:
merge(pandas, pandas) -> pandas
merge(pandas, cudf) -> cudf
merge(cudf, pandas) -> cudf
merge(cudf, cudf) -> cudf

This pattern could be implemented easily in code by adding a priority dispatch. I'd argue that this would be simpler to understand, and wouldn't require an additional dependency. A simple version might look like (works with existing dask code):
from dask.utils import Dispatch
import pandas as pd
import cudf

priority_to_type = {}
type_to_priority = {}

def register_priority(type, value):
    priority_to_type[value] = type
    type_to_priority[type] = value

def type_to_use(*values):
    priority = max(type_to_priority.get(type(v), -1) for v in values)
    return priority_to_type[priority]

register_priority(pd.DataFrame, 0)
register_priority(cudf.DataFrame, 1)

merge_dispatch = Dispatch('merge')

@merge_dispatch.register(pd.DataFrame)
def merge_pandas(df1, df2):
    ...

@merge_dispatch.register(cudf.DataFrame)
def merge_cudf(df1, df2):
    ...

def merge(df1, df2):
    df_type = type_to_use(df1, df2)
    func = merge_dispatch.dispatch(df_type)
    return func(df1, df2)

I'd argue that in most cases:

The number of types we'd be dispatching on would be low
Functions taking disparate types would likely upcast to some common type before continuing
The number of arguments we care about would be low (in merge's case it's just 2)

As such I think my preference would be to roll a simple custom dispatch like the above (which works with the existing dask.utils.Dispatch and is only a few lines of code), and only move to multipledispatch if necessary.

I've pushed up https://github.com/dask/dask/pull/4522 with an initial implementation with multipledispatch (started this before @jcrist 's recent comment) just to get a sense of how invasive this is.

Happy to do something like what is proposed.  The main argument I could see for something like multipledispatch is that we've spent some non-trivial amount of time tweaking our custom Dispatch object over the last few years.  At some point we might want to punt and use something used and maintained by others as well (though admitedly, not by that many).

I'm happy either way though.  They're both easy to do.

I think for now I'd prefer not to add a new dependency, and see how doing this with a priority feels. If more complicated behavior is needed at some point then I'd be open to using multipledispatch.

OK, so I'm curious about how best to implement your suggestion above.  Do people who want to register a new type register both to merge_dispatch and to the register_priority function?  Or is there some extension to Dispatch that you're proposing?

Right now I'm suggesting a hack like the above to make what you need now work. So yes, new register_priority function. My guess is the prioritization will be the same for all functions that take disparate types, so the priority lookup could be shared between merge, etc...

OK, in my PR I've now switch to using Python's standard method dispatch, which should work in all cases except for merge(pandas, cudf).
I'm inclined not to add in something like register priority for just this case, just because I would like to avoid making a new system.
I find myself preferring multipledispatch long term, which I view as a stable and lightweight dependency.  That's probably just because I'm more familiar with it though.


integrations_docs: updated integrations css.

Added a rule for unordered list elements inside
an ordered list element.
Fixes zulip#29669

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Thanks for the fix!

Done! @alya let me know if it could be clearer :+1:

Can you add before/after screenshots for this?

Merged, thanks @PieterCK! @laurynmm FYI as maintainer of this code.


Update numpy version in setup.py

Currently tf-nightly is not compatible with numpy <=1.22.* versions. Its working only with numpy versions >=1.23 . But Required_packages in setup.py file mentioned numpy>=1.22. Hence I am updating numpy to numpy>=1.23.
Attaching the gist also for reference to check the behaviour.

You need to update the requirements.txt files used in all CI too, they have to test with a numpy that matches what is in setup.py

Thanks. tf-nightly is broken in Colab right now (workaround: pip install -U numpy). This will fix it.
@mihaimaruseac Here? https://github.com/tensorflow/tensorflow/blob/0ed8e904f4cb58826e2bd861ae508e38f49d3ea8/tensorflow/tools/tf_sig_build_dockerfiles/devel.requirements.txt#L13-L16

I think so, unclear what are the current files being used by hermetic Python and all CIs. Tagging @angerson and @vam-google to confirm.

"I have found below requirements.txt files.
I can see numpy version as >=1.22 in requirements.in file.
https://github.com/tensorflow/tensorflow/blob/9fa5e774d4f86c2e41b04a6ac326578bdd516691/ci/official/requirements_updater/requirements.in#L1
Apart from this requirements_lock_3_10.txt and others (requirements_lock_3_11.txt, requirements_lock_3_9.txt, requirements_lock_3_8.txt) have numpy version set to 1.24.3 .
https://github.com/tensorflow/tensorflow/blob/9fa5e774d4f86c2e41b04a6ac326578bdd516691/requirements_lock_3_10.txt#L265
But here in ci_build/release/requirements_common.txt requirements mentioned as below.
https://github.com/tensorflow/tensorflow/blob/9fa5e774d4f86c2e41b04a6ac326578bdd516691/tensorflow/tools/ci_build/release/requirements_common.txt#L12-L13
Under Docker SIG build:
https://github.com/tensorflow/tensorflow/blob/aa7fbf11a7581009f08933273bde7a0bc2490aff/tensorflow/tools/tf_sig_build_dockerfiles/devel.requirements.txt#L15-L16

Thanks @SuryanarayanaY , i think those are the 4 primary locations,  and to my knowledge all should be updated to >= 1.23 given what you have said above.  Normally the requirements lock files would need recomputed but given they are already locked above that value it should be fine to leave as is.  If you can update the PR to include those today I can pull internal and make sure the requirement locks are fine, if not i will likely pull it in and adjust myself to fix the next build of tf-nightly.

I am going to hold this till Monday, @georgiyekkert pointed out that this upgrade seems required due to when we build tf-nightly we are using numpy headers from CI, so our nightly is packed with 1.24.3 headers no matter what user has installed on their machine.
We will first try to modify and make 1.22 work again and discuss a 1.23 upgrade separately

Looks like there's a conflict wth this commit: https://github.com/tensorflow/tensorflow/commit/d9962234b8a33eb3b351ce69498f1671a832b98a

Hi @SuryanarayanaY Can you please resolve conflicts? Thank you!

The issue should have been fixed in https://github.com/tensorflow/tensorflow/commit/2c5f35e7e23c3298babf2227ea0ae128d1e6fb8e
The requirements files you are changing are outdated and not used in the build any more. Please let me know if you still have any issues otherwise please close.

Perfect, then this can gen closed. Thanks @georgiyekkert


Upgrade Jackson to 2.15.0

Description
Upgrade Jackson to 2.15.0
it aligns with Camel Kamelets catalog
https://github.com/apache/camel-kamelets/pull/1465
Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[ ] I formatted the code using mvn -Pformat,fastinstall install && mvn -Psourcecheck

jackson 2.15 is just released. Keep in mind that quarkus/spring-boot may need to upgrade as well (in case jackson it does not run with 2.14.x)

We can only upgrade to jackson 2.15.x on main branch for Camel v4 as SB 3.1 is upgraded as well.
Camel v3 releases are on 2.14.x for now (I upgraded them to 2.14.3)
https://issues.apache.org/jira/browse/CAMEL-19351

@apupier we can upgrade now, you are welcome to resolve this PR.
PS: I think there is even a 2.15.1 release

Conflict resolved
Upgraded to 2.15.1 (previously 2.15.0 in this PR)


Update free-podcasts-screencasts-en.md

I apologize for any english mistakes in advance.
What does this PR do?
Add Resources
For resources
Courses, and mainly Screencasts.
Description
Replaced the "Intro to Elixir" Screencast for a better one with a better approach to the theme.
I also added new contents to the Haskell Screencast (both English and Portuguese — this one I had to create),  same with Vim screencast sub-theme, and a free linux course (English).
Why is this valuable (or not)
These resources either didn't exist, weren't used or simple were too old, that's why I replaced some of them.
How do we know it's really free?
Some these resources are either in GitHub, or under GPL, or aren't monetized.
For book lists, is it a book?
No.
Checklist:

[x]  Not a duplicate
[x]  Included author(s) if appropriate
[ ]  Lists are in alphabetical order
[x]  Needed indications added (PDF, access notes, under construction)

I also have a question, can we have a Linux sub-theme on Screencast? I am not going to be picky to the point of creating myself it, but I would recommend adding some of the Luke Smith videos — since I don't know if you accept just channels instead of playlist/videos.

Hi. All these changes look good, but we need the lists to be in alphabetical order. (titles start with "the" begin with 't')
Create an issue if you want to suggest an addition. we have linux sections on other lists.

Hi. All these changes look good, but we need the lists to be in alphabetical order. (titles start with "the" begin with 't')
Create an issue if you want to suggest an addition. we have linux sections on other lists.

I think I did it right now, it should be all good.

Hi. All these changes look good, but we need the lists to be in alphabetical order. (titles start with "the" begin with 't')
Create an issue if you want to suggest an addition. we have linux sections on other lists.

I think I did it right, it should be good now.

I apologize for my mistakes. Thank you for your comprehension and patience.


Villagers multiplying

Villagers seem to multiply every 24hrs(roughly) by the number of beds there. Do you know if this is supposed to be a feature? Every time I log into the server for the day a new pair has spawned, so I have about 14 villagers with 2 beds. I have not changed any settings in the .dll or .cfg files

Are you in an multiplayer scenario? if yes then that is the issue, this mod is not currently working in multiplayer

Yes on a dedicated server so it is multiplayer. Is there anything on my end I can do to help it work or is it something I have to wait for the mod to be updated to fix?

Villagers will not be spawned anymore from the next update. That should at least fix the infinite spawning villagers and although no where close to being supported should work in multiplayer without any serious bug


Dockerfile config copy issue

Fixed issue with config file missing before COPY able to be executed. Added potential VOLUME mount for config files from external source.
Within the RUN there is a removal for the checked out repo directory, thereafter there is a COPY command which should have copied the docker.drachtio.conf.xml  to the /etc/ folder which fails due to the file no longer being in the path it is being copied from.
I added an entry for a VOLUME to be mounted if your config lives on persistent storage outside of the container. I currently use this with my kubernetes deployments to bundle up different storage volumes for production, staging and development. Might be a nice :smile:
In my kubernetes deployment I have:
...
spec:
      containers:
      - image: drachtio/drachtio-server:latest
        name: drachtio-server
        command:
          - drachtio
          - "-f /config/drachtio.conf.xml"
        volumeMounts:
          - name: config-storage
            mountPath: /config
      volumes:
        - name: config-storage
          hostPath:
            path: /storage/drachtio-server-production

Thanks!