BUG: Cannot export Points in COCO Format

Hello everyone,
the issue itself is that, when I export annotations in COCO Format, points are not shown in the json, but polygons are.
I have tried both creating a new task and only annotating points and also combining points and polygons, and neither of them exports the COCO Format with both instances.
Expected Behaviour
The expected behaviour is to be able to export the COCO Format with both points and polygons.
Current Behaviour
The current behaviour is that the COCO Format is not able to export points.
Possible Solution
It would just be a matter of implementing the points inside the COCO Format, so that they can be exported alongside the polygons.
Steps to Reproduce (for bugs)

Create a new task
Set a point
Export in COCO Format

Context
The project that I am actually working in requires both a combination of a mask and a keypoint inside of it, in the most important part of the object. Without the points, the goal cannot be accomplished.
Your Environment

Docker version docker version (e.g. Docker 17.0.05): Docker version 19.03.12, build 48a66213fe
Are you using Docker Swarm or Kubernetes? No, just Docker (required for the application)
Operating System and version (e.g. Linux, Windows, MacOS): Windows
Code example or link to GitHub repo or gist to reproduce problem: https://github.com/openvinotoolkit/cvat

I'm also interested on this.

I am looking for this

COCO keypoints are not supported yet, possible solutions are described here: https://github.com/openvinotoolkit/cvat/issues/1784

COCO keypoints are not supported yet, possible solutions are described here: #1784 and #1421 (comment)

@zhiltsov-max I think those workarounds don't work for me because I have less than 3 keypoints, and masks are only supported with at least 3 points.

@zhiltsov-max Also, I think having keypoints in COCO format should be a very common feature.

Yes, I agree with @claverru, having the keypoints in COCO is a very common feature, and in my opinion is an urgent enhancement

https://github.com/openvinotoolkit/cvat/issues/1421#issuecomment-616576420 describes exactly this topic.


Angular JIT compilation failed: '@angular/compiler' not loaded!

Hello,
after migrating from Angular 8 to 10 some of our applications can't be served anymore. The ng serve process is running without any error (some warnings tho) but when I try to open the app in the browser I'll receive this error:
Angular JIT compilation failed: '@angular/compiler' not loaded!
According to the issues https://github.com/angular/angular-cli/issues/16873 and https://github.com/angular/angular/issues/35788 this might be related to libraries not having the necessary module structure for their ngcc. Debugging this in ng_module_factory_registration.ts showed me that it crashes on the ng-inline-svg library.
Is there any chance you can look into this?

Should be fixed in v11.0.0.
On a side note, I hate how every major Angular change requires libraries to be updated. Maybe I'm doing something wrong...

Hello,
I got this same error too, after updating Angular 8 to 9. (I recommend update step by step. 8 to 9, 9 to 10)

Uncaught Error: Angular JIT compilation failed: '@angular/compiler' not loaded!

JIT compilation is discouraged for production use-cases! Consider AOT mode instead.
Did you bootstrap using '@angular/platform-browser-dynamic' or '@angular/platform-server'?
Alternatively provide the compiler with 'import "@angular/compiler";' before bootstrapping.

It is simply says @angular/compiler not loaded. After very long time search, I tried adding import '@angular/compiler'  to main.ts. And it works for me.
Hope it is help.

My code compiled successfully with Angular 10 (ng build --prod), but I was getting this error when running the app.
It turned out I've messed up one of my libraries, which I was installing from local disk instead of npm. A package.json file was missing from a nested ngx folder. E.g.:
This doesn't work
  node_modules/
    ...
    my_library/
      ngx/  <----------- package.json is missing here
      ...
      package.json

This works
  node_modules/
    ...
    my_library/
      ngx/
        package.json
      ...
      package.json

Also, you may want to double-check the name field in your package.json file. If you've forked/modified a library, then you might have changed its scope or name.
P.S.: Also see: https://github.com/CharlesElGriego/angular-aot-dynamic-components/issues/6,


support numbers

discussion ref: https://github.com/InstantDomain/instant-segment/issues/30

I've published instant-segment 0.10.1 with this change, thanks again!

Thank you too!


"unhide" query.instant.default.max_source_resolution Flag

Hello everyone
We are using thanos ruler for some recording rules which do use offset to compare certain values to historic data. The offset hits a date range where we do not have any raw data, but only downsampled data. As a result, the query does not return any results. After some search we discovered the hidden flag --query.instant.default.max_source_resolution which was introduced in https://github.com/thanos-io/thanos/pull/1431. After configuring this option, our queries do work. I was wondering whether we could make this hidden flag a regular one by "unhiding" it
Describe the solution you'd like
Setting --query.instant.default.max_source_resolution to e.g. 1h resolves our issue but this flag is hidden by default and there is also no documentation for this flag.
Additional context
I am not sure why exactly this feature was implemented as a hidden flag. In my opinion, this feature could be interesting for others as well, and it might make sense to add some documentation for and make it a regular flag. Any opinions on this?
Everyone agrees, I would be happy to add documentation for this flag and "unhide" it.
Thanks,
Reto

Hey @rekup,
Looks like this older comment might give some insight on why https://github.com/thanos-io/thanos/pull/1431#pullrequestreview-279331642, I'd say if those reasons are still valid it makes sense to keep it hidden. Alternatively, we can document this use case and fix and still keep it hidden.


Barback should ensure that assets are properly finalized

When Barback passes Asset objects to Transformers via [isPrimary] and [apply], it's possible for those Transformers to open the Asset's stream for reading without properly closing it afterwards. This can create resource leaks that will become a problem in a long-running "pub serve" process. Since barback knows when an Asset is no longer in use by a transformer, it should close those Assets' streams.

This issue has been moved to dart-lang/barback#15.


[Feature] sc-22600 Implement the upload feature in SDK

Implement SDK upload method
Implement CLI upload command
Support recursive upload files

Signed-off-by: Kent Huang<EMAIL_ADDRESS>Co-authored-by: Ash Wu<EMAIL_ADDRESS>

Need to update docs

https://github.com/InfuseAI/primehub-python-sdk/blob/main/docs/CLI/files.md
https://github.com/InfuseAI/primehub-python-sdk/blob/main/docs/notebook/files.ipynb
Updated file releated documents.


ES search broken for multivalued facets

The facet Architecture; Detroit; Buildings. (18), with the constructed URL (URL quoted in app, but still breaks):
http://<IP_ADDRESS>:9200/j187/_search?q=mods_titleInfo_title:http://<IP_ADDRESS>:9200/j187/_search?q=mods_titleInfo_title:"Architecture; Detroit; Buildings. "

fails with theES error:
{
error: {
root_cause: [
{
type: "illegal_argument_exception",
reason: "request [/j187/_search] contains unrecognized parameters: [ Buildings. "], [ Detroit]"
}
],
type: "illegal_argument_exception",
reason: "request [/j187/_search] contains unrecognized parameters: [ Buildings. "], [ Detroit]"
},
status: 400
}

Looks like the ; is breaking the ES query...

Fixed.


What machine to use for training?

I use A100 40GB, batchsize=1 to train stage2, and CUDA out of memory.

我使用 A100 40GB，batchsize=1 来训练 stage2，并使用内存不足的 CUDA。

您好，请问你能分享一下你的训练代码吗？我最近也在尝试训练这个任务？

We use plenty of A800 80GB GPUs to train the model. Further fine-tuning may not consume that much compute, if parameter-effcient techniques like lora and quantization are applied.

Thanks for your reply. Please tell me if 40GB is not enough for batchsize1 when training motion+audio+audioproj.

Could you share the train code?


How to fine-tune a model?

Hi, your library is very convenient to use and I have a question,
I use market1501 dataset to train a resnet50. Is it able to fine-tune the same model using cuhk03 ?
Thanks,

Yeah, roughly you may just

create the cuhk03 dataset
create the model
load from market1501 pretrained parameters
fine-tune on cuhk03

Thanks a lot ~!!!


This document need updating

This Document mentions Az.Profile module is needed but Az.Profile Module is replaced with Az.accounts . so please update this appropiately. thanks

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

ID: f3d18144-dd03-c659-f0a4-c0ab13d3d343
Version Independent ID: ecdcbda2-259f-4992-57d8-c448a3934011
Content: Send an email from an Azure Automation runbook
Content Source: articles/automation/automation-send-email.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@tigerdeccan Thanks for the feedback. We're investigating this and will get back to you shortly.

@tigerdeccan Thanks for the feedback. We're investigating this and will get back to you shortly.

@tigerdeccan Thank you for catching that error in the docs! I have submitted a PR to fix the issue, the change is merged internally and will go-live in the public docs shortly.

@tigerdeccan Thank you for catching that error in the docs! I have submitted a PR to fix the issue, the change is merged internally and will go-live in the public docs shortly.


proc-macro crate in workspace unexpectently exits

Describe the bug
Workspaces with a proc-macro crate fail to execute tests (The failure happens when execution of the test exe begins, but before any test starts) with the following error:
2024-10-28T15:58:05.678629Z  INFO cargo_tarpaulin::process_handling: running D:\a\rust-ci-testing\rust-ci-testing\target\debug\deps\rust_proc_macro-6ef64dc17f0828ce.exe
2024-10-28T15:58:05.678931Z  INFO cargo_tarpaulin::process_handling: Setting LLVM_PROFILE_FILE
2024-10-28T15:58:05.686895Z ERROR cargo_tarpaulin: Test failed during run
Error: "Test failed during run"
Error: Process completed with exit code 1.

I can only reproduce on a github action windows-latest runner (but 100% of the time). It does not happen on ubuntu-latest image (even with the --engine llvm flag) and it does not happen on windows locally. it fails with or without any tests actually in the crate. It fails with engine llvm and --no-dead-code
I tried adding tests to see if that helped any, but it continued to fail. I also tried adding tests as described in #326 but it continues to fail.
I am currently on:
cargo-tarpaulin 0.31.2
1.80.0
To Reproduce
I have set up a repo with a CI job that hits the issue: Javagedes/rust-ci-testing with an example run here: action/Run Tests
Expected behavior
I would expect the test harness to not unexpectedly fail without running any tests.

Hmm that's super odd, could you add --dump-traces to the tarpaulin flags. Hopefully it's not so long that GHA gives up on printing the logs.
I don't really use windows so this might take me some time to replicate (I need to find a windows machine and setup a dev env or find a friend who can help to get a quicker turnaround)

I'm seeing something similar on Linux, both in CI (GitHub Actions) and locally (Arch).

oh weird/interesting that's very helpful thanks :+1:

Output from --dump-traces: tarpaulin_20241129173337.json

Of course, feel free to split this into a separate issue if it seems unrelated.

Locally (Rust 1.83, Fedora Linux, amd64) I see these messages right before the test failure.
2024-12-02T21:57:21.820615Z  INFO cargo_tarpaulin::process_handling::linux: Launching test
2024-12-02T21:57:21.820661Z  INFO cargo_tarpaulin::process_handling: running /home/jbushart/projects/serde_with/target/debug/deps/serde_with_macros-ae28cd5b53cb79aa
/home/jbushart/projects/serde_with/target/debug/deps/serde_with_macros-ae28cd5b53cb79aa: error while loading shared libraries: libstd-02dc84f49135b6b8.so: cannot open shared object file: No such file or directory
2024-12-02T21:57:23.109267Z ERROR cargo_tarpaulin: Test failed during run
Error: "Test failed during run"

I do not see the link message on GitHub Actions (Source).
test result: ok. 79 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1.25s

Error: "Test failed during run"
Error: Process completed with exit code 1.

Since this is a linking issue, this change sounds relevant: "The sysroot no longer contains the std dynamic library in its top-level lib/ dir." https://github.com/rust-lang/rust/pull/131188

Oh one thing that another person with the issue has confirmed is that --exclude <PROC_MACRO_CRATE> also works to solve the issue as a stop gap


Cannot start dashboard

Hi, vagrant provision returns errors:
 one of [0] at /tmp/vagrant-puppet/manifests-846018e2aa141a5eb79a64b4015fc5f3/default.pp:51
==> default: err: /Stage[main]/Init/Exec[project_prepare]/returns: change from notrun to 0 failed: /home/vagrant/dashboard/prep.sh: line 4: /usr/$ocal/bin/virtualenv: No such file or directory
==> default: /home/vagrant/dashboard/prep.sh: line 5: env/bin/activate: No such file or directory
==> default: /home/vagrant/dashboard/prep.sh: line 6: /home/vagrant/dashboard/env/bin/pip: No such file or directory
==> default:

Apparently it cannot install virtualenv, and indeed if I SSH into it and run manually sudo pip install virtualenv I get:
Downloading/unpacking virtualenv
  Cannot fetch index base URL http://pypi.python.org/simple/
  Could not find any downloads that satisfy the requirement virtualenv
No distributions at all found for virtualenv
Storing complete log in /root/.pip/pip.log

I have updated to the latest python versions. Sorry for taking it long


chore(deps): upgrade runtime dependencies

Upgrades project dependencies. See details in workflow run.

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

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

Questions ?
Please refer to the Backport tool documentation


DBT-11209 warning after applying 19.17.0 Release Update

After building a patched docker image using the GI RELEASE UPDATE <IP_ADDRESS>.0 (Patch 34416665), the DB shows a DBT-11209 warning when running the DB initialization:
ORACLE EDITION: ENTERPRISE

LSNRCTL for Linux: Version <IP_ADDRESS>.0 - Production on 23-JAN-2023 11:00:22

Copyright (c) 1991, 2022, Oracle.  All rights reserved.

Starting /opt/oracle/product/19c/dbhome_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
System parameter file is /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Log messages written to /opt/oracle/diag/tnslsnr/f4b6bea6ad73/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version <IP_ADDRESS>.0 - Production
Start Date                23-JAN-2023 11:00:23
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/oracle/product/19c/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/oracle/diag/tnslsnr/f4b6bea6ad73/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADDRESS>)(PORT=1521)))
The listener supports no services
The command completed successfully
[WARNING] [DBT-11209] Current available memory is less than the required available memory (2,048MB) for creating the database.
    For details check the logfiles at:
 /opt/oracle/cfgtoollogs/dbca/ORCLCDB.
Database Information:
Global Database Name:ORCLCDB
System Identifier(SID):ORCLCDB
Look at the log file "/opt/oracle/cfgtoollogs/dbca/ORCLCDB/ORCLCDB.log" for further details.

SQL*Plus: Release <IP_ADDRESS>.0 - Production on Mon Jan 23 11:26:01 2023
Version <IP_ADDRESS>.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.

Connected to:
Oracle Database 19c Enterprise Edition Release <IP_ADDRESS>.0 - Production
Version <IP_ADDRESS>.0

SQL>
System altered.

SQL>
System altered.

SQL>
Pluggable database altered.

SQL>
PL/SQL procedure successfully completed.

SQL> SQL>
Session altered.

SQL>
User created.

SQL>
Grant succeeded.

SQL>
Grant succeeded.

SQL>
Grant succeeded.

SQL>
User altered.

SQL> SQL> Disconnected from Oracle Database 19c Enterprise Edition Release <IP_ADDRESS>.0 - Production
Version <IP_ADDRESS>.0
The Oracle base remains unchanged with value /opt/oracle

Executing user defined scripts
/opt/oracle/runUserScripts.sh: running /opt/oracle/scripts/extensions/setup/savePatchSummary.sh

DONE: Executing user defined scripts

The Oracle base remains unchanged with value /opt/oracle
#########################
DATABASE IS READY TO USE!
#########################

Executing user defined scripts
/opt/oracle/runUserScripts.sh: running /opt/oracle/scripts/extensions/startup/runDatapatch.sh
Datafiles are already patched. Skipping datapatch run.

DONE: Executing user defined scripts

The warning is strange, since the VM running the docker daemon has 32GB of RAM of which 30 GB are unused and no memory limits are set. The following command has been used to run the container:
docker run --name oracle-db -d oracle/database:19.17.0-ee

Hi @dnl50
This issue is fixed in GI RELEASE UPDATE <IP_ADDRESS>.0
So

You can try with RU 19.20, or
Wait for sometime. We will soon be releasing patched images in container registry.

Thanks!

Get BlueMail for Android 0⁰ mqqqqqqqqkkkkak0
On Sep 9, 2023, 1:11 PM, at 1:11 PM, Daniel Meier @.***> wrote:

Thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/oracle/docker-images/issues/2546#issuecomment-1712557261
You are receiving this because you are subscribed to this thread.
Message ID: @.***>


add a man page

Adds a man page (see: #25)
I know you wanted to use an auto-converter, but I've never had much luck with them and it only took me 10 minutes or so to convert your existing documentation into roff format.

Great! Thank you! Someone had to start this :) I see no problem in updating Markdown docs at the same time with the man page.


feat: avoid subscribing in user token interceptor

closes #3168

To QA: since this is a minor change to our user token interceptor, to test this it's enough to just try to login/logout/login.


Causal Graph  in Member Rewards Notebook

About https://github.com/microsoft/dowhy/blob/master/docs/source/example_notebooks/dowhy_example_effect_of_memberrewards_program.ipynb I'm struggling to understand how the causal graph is correct? How is it possible that "signup_month" has a causal impact on pre_spends (an event which occurred after).
Is the graph correct?

ah, great catch @misclassified. That must have been a typo---fixed it.
The backdoor criterion still outputs the same confounders, so we are good there.


Identify cases where VIEW DATA is not functional or a common reason

Description
As a user, I want to be able to view all available data for the models.
Acceptance criteria

[x] all cases identified
[x] reason(s) determined
[x] solution planned

Host strain name not visible for PIVOT models: https://www.cancermodels.org/data/models/PIVOT/ES-6
Copy number data for IRCC-CRC targeted NGS: (molecular data removed).
Mutation data from MISEq platform for LIH not visible.
mutation data for few samples in PDMR not visible. (https://www.cancermodels.org/data/models/PDMR/241356-047-R): (no molecular data available)

above mentioned issues should get fixed with the next release


[SPARK-33640][TESTS] Extend connection timeout to DB server for DB2IntegrationSuite and its variants

What changes were proposed in this pull request?

This PR extends the connection timeout to the DB server for DB2IntegrationSuite and its variants.
The container image ibmcom/db2 creates a database when it starts up.
The database creation can take over 2 minutes.
DB2IntegrationSuite and its variants use the container image but the connection timeout is set to 2 minutes so these suites almost always fail.
Why are the changes needed?

To pass those suites.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

I confirmed the suites pass with the following commands.
$ build/sbt -Pdocker-integration-tests -Phive -Phive-thriftserver package "testOnly org.apache.spark.sql.jdbc.DB2IntegrationSuite"
$ build/sbt -Pdocker-integration-tests -Phive -Phive-thriftserver package "testOnly org.apache.spark.sql.jdbc.v2.DB2IntegrationSuite"
$ build/sbt -Pdocker-integration-tests -Phive -Phive-thriftserver package "testOnly org.apache.spark.sql.jdbc.DB2KrbIntegrationSuite"

Test build #132095 has started for PR 30583 at commit 7444a08.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36694/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36694/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36694/

retest this please.

Test build #132095 has finished for PR 30583 at commit 7444a08.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #132104 has started for PR 30583 at commit 7444a08.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132095/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36704/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36704/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36704/

retest this please.

Test build #132118 has started for PR 30583 at commit 7444a08.

Test build #132104 has finished for PR 30583 at commit 7444a08.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132104/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36717/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36717/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36717/

Test build #132118 has finished for PR 30583 at commit 7444a08.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132118/

retest this please.

Test build #132135 has started for PR 30583 at commit 7444a08.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36736/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/36736/

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/36736/

Test build #132135 has finished for PR 30583 at commit 7444a08.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/132135/

cc: @gaborgsomogyi

cc: @dongjoon-hyun and @HyukjinKwon too.

Late LGTM. Thanks for notifying.


Implementing fastbtm

Hi @markoarnauto ,
I have tried implementing variant of btm namely fastbtm, i have tried to implement it but it is not performing well, i can share the paper by which i have done the same.
Requesting your help in code review and implementation of it.

Hi @BurakaKrishna , I'm curious to read your paper! I also had troubles with performance, it would be great to have a faster sampling procedure.

Actually it is paper written by somebody else, i can share the paper pdf can you share your email  at<EMAIL_ADDRESS>These are the reference i used one article and another the paper
[1] https://engineering.flipboard.com/2017/02/storyclustering Article
[2] https://www.sciencedirect.com/science/article/abs/pii/S0950705117302782 Paper


Unable to pull docker image

I'm unable to pull the docker image, seeing this permission error:
Error response from daemon: pull access denied for ghcr.io/whittlem/pycryptobot/pycryptobot, repository does not exist or may require 'docker login': denied: permission_denied: read_package
I've setup a personal access token with the required read package and I've also verified I'm logged in.

Similar issue:
:~$ docker pull ghcr.io/whittlem/pycryptobot/pycryptobot:latest
Error response from daemon: Head https://ghcr.io/v2/whittlem/pycryptobot/pycryptobot/manifests/latest: unauthorized

I had the same issue, to solve it you can build the image in your pc, got to where you have the Dockerfile and execute the command below:
docker build -t pycryptobot

Thanks for answering this. Does this need to be added to the documentation?
@lvlie kindly added the Docker functionality. Maybe he can confirm?

Oh cool I was still using my own version. That is "pullable" for unauthenticated users because the package is set to public.
Did you make sure to set it to public in your Profile > Packages section. On mobile it should look something like this:

Hi @whittlem I think yes, you can add the both information, how to buiild a image and how to run a image.
Build your won image if necessary:
docker build -t pycryptobot_xx_yy .
where xx = ADA
where yy = EUR
Running a docker image:
docker run -d --rm --name pycryptobot_xx_yy_container pycryptobot_xx_yy

Thank you. I will improve the instructions as per your message.

Thanks @lvlie, I made the package Public now.
Can you all try again please? It should work now.

@lvlie and @alexandreafc, does this article look okay to you:
https://whittle.medium.com/pycryptobot-docker-container-cffe38a344bf?sk=4d4ea66e5f1af74cf675b78ace3b73e8

Looks good to me, good write up :-)

Great, thanks.


Image Permission Denied

I am trying to run the image on Google Cloud Run but it seems that the permission to read the image is denied. I am getting this error in Google Cloud Run console.
_

Google Cloud Run Service Agent must have permission to read the image, gcr.io/cyrildiagne-ml/basnet-http. Ensure that the provided container image URL is correct and that the above account has permission to access the image. If you just enabled the Cloud Run API, the permissions might take a few minutes to propagate. Note that the image is from project [cyrildiagne-ml], which is not the same as this project [playground-amardeep]. Permission must be granted to the Google Cloud Run Service Agent from this project.

_

Sorry, the image wasn't correctly configured. It's public now so you should be able to pull!

Thanks. I was able to deploy it on Cloud Run but I am getting memory limit errors.

Memory limit of 2048M exceeded with 2307M used. Consider increasing the memory limit
Cloud Run does not have GPU .. is that the reason?
What is the best way to deploy it on Google Cloud/AWS? If you could give some directions that would be great! Thanks

I've added more details about the memory requirements in the basnet-http repo.
But adding detailed informations on how to deploy to a cloud instance is beyond the scope of this prototype. Would make sense to have then in the basnet-http repo though!


Split built in functions into "packages"

Is your feature request related to a problem or challenge?
Right now, DataFusionhas 104 built in functions: https://docs.rs/datafusion/latest/datafusion/logical_expr/enum.BuiltinScalarFunction.html

As we add new features and functions (most recently, date_diff https://github.com/apache/arrow-datafusion/issues/7097#issuecomment-1653466104 or all the arary functions) this number will keep growing
This growth means that the size of the  DataFusion  library will keep growing even if users do not use those features
Describe the solution you'd like
Given that DataFusion has all the machinery to register user defined functions, and they are mostly handled the same way, I propose we split up the datafusion built into scalar function packages
Perhaps like

string_functions (upper, hex, etc)
crypto_functions (hash, etc)
array_functions (make_array, array_contains, etc)
date_time functions (date_trunc, etc)
...

Not only would this give users better control over their binary size it would also ensure that the extensibility APIs of DataFusion were sufficient for all functions (and we could enhance the extension points if this was not the case)
This would replace the existing somewhat haphazard feature flags like crypto_functions:
https://github.com/apache/arrow-datafusion/blob/11b7b5c215012231e5768fc5be3445c0254d0169/datafusion/physical-expr/src/lib.rs#L21-L22
I would imagine these functions would be in their own crates like datafusion_functions_crypto with an entry point like
let ctx = SessionContext::new();
ctx.sql("select hash('foobar')");// would error

// register all functions in the `datafusion_functions_crypto` package
datafusion_functions_crypto::register(&ctx)
ctx.sql("select hash('foobar')");// would now succeed

Describe alternatives you've considered
We could continue to use feature flags
If this works out, we could do the same thing for aggregate and window functions
Additional context
No response

what about namespaced enums? it would still use feature flags, but it'd make it much more compartmentalized & able to easily split into sub crates.
so something like
// this could easily live in it's own crate.
pub enum StringFunctions {
    // string related functions
}

pub enum BuiltinScalarFunction {
    #[cfg(feature = "string_expressions")]
    StringNamespace(StringFunctions),
    #[cfg(feature = "list_expressions")]
    ListNamespace(ListFunctions),
    #[cfg(feature = "crypto_expressions")]
    CryptoNamespace(CryptoFunctions),
    Abs,
    // ...other non namespaced functions
}

what about namespaced enums? it would still use feature flags, but it'd make it much more compartmentalized & able to easily split into sub crates.

That is a neat idea @universalmind303   -- I was even thinking there is no reason to have BuiltInScalarFunction at all in theory -- the same effects can be achieved using the ScalarUDFI think
This would also make things like serialization simpler as well (as there is already a name --> function mapping)

I think it would be really nice to implement these packages as crates (possibly with feature flags in datafusion core) rather than just feature flags in datafusion core. cc @tustvold


[FEATURE] Blog Views Functionallity

Detailed description
Blog Views Functionallity
when user visits any blogs, then blog count should increate by 1

backend: https://github.com/thecyberworld/api.thecyberhub.org
code is on the dev branch:

fork this repo
clone this repo
add your mongo creds in the env file
npm run server

frontend: https://github.com/thecyberworld/thecyberhub.org

npm run dev

Context
If you need any help or having doubts, let us know
Possible implementation
No response
Additional information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey I am having trouble connecting the backend. I have added the mongo_uri

I have reached till here but I have no idea how to proceed further inorder to design.
Can anyone help me with the setup?

hello @nidhiparab

wait a minutue

go to connect
then you will get multiple options
first you can connect that with mongodb compass (you have to download the compass app then have to paste that url in it)

and for connecting with the application
you have to click on the Connect with the application
then you will get a url
add your details and database name over there
then add it into backend env file

If you face any issues let us know

and for connecting with the application you have to click on the Connect with the application then you will get a url
add your details and database name over there then add it into backend env file

I have already done this step. I am not able to see the create blog or profile section, a little help with that please?

and for connecting with the application you have to click on the Connect with the application then you will get a url
add your details and database name over there then add it into backend env file

I have already done this step. I am not able to see the create blog or profile section, a little help with that please?

Nice
profile section is in the

you can create blogs via clicking on create blog button:

i am just uploading the latest structure of the blogs

so make sure to keep fetching the new changes before working on the code..

Sorry but I don't see the profile option anywhere

Even the navbar in Readme is different than what I cloned. Could you look into that?

okay got it

You have to clone the dev branch
when you fork the repo, there is option

[ ] copy only main branch

uncheck that button while forking

if you are using github desktop, then maybe you can change the branch from the eaily

backend branch: dev
frontend branch: dev

and make sure to

uncomment the localhost one in vite.js config file in frontned
if you don't, you will get the backed of the main website, not the local

and env file too

hey @nidhiparab
Just fetch the new changes from dev branch
you don;t have to make any changes to env or config file after that
...


[CMake] Remove TARGET_LIBRARY option from add_swift_target_library

If you're calling add_swift_target_library, you already know it's a
target library.
This is a follow up to what was discussed in #26312.
cc @compnerd @Rostepher @gottesmm

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please test Linux platform

Build failed
Swift Test Linux Platform
Git Sha - a16c71cc86bb568d123de658cbf30a9112af8755

@swift-ci please smoke test and merge


Added Health Expense Sample

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Solution Details

Q
A

Solution requires premium license
yes

Solution uses experimental features
no

Which connectors are used?
OpenAI Connector

Solution uses on-premises connectors?
no

Solution uses custom connectors?
yes

Layout
Tablet

What's in this Pull Request?
This is a new sample.
Sample Summary: This sample allows the user to predict their Health Expense using a Machine Learning Model and then get a detailed personalized plan to save for it.

Hi,
I can't process your PR, because there is a flow referenced in the canvas app that's not included. It's called "AzureAutoMLFlow". Can you please follow the following instructions and update your sourcecode folder with the solution that you cloned via these instructions?
https://github.com/pnp/powerapps-samples/wiki/How-to-submit-a-Power-App-sample
Thanks,
Daniel

Oh,ok. I will make the changes and let you know
Thanks!

Can I get some help on this? Even after going to the right environment any of my power apps are not showing up in the solutions...

@Laskewitz I have used the instructions given above and updated the source code folder. Let me know if it is fine now
Thank you

@aaryan2134 - one final thing: can you add instructions on how to setup the Azure ML instance as well? This will help others to make the sample work.

@Laskewitz I have added the instructions for setting up Azure ML instance as requested
Please have a look and let me know in case any further changes are required
Thank you

@Laskewitz Hi
Any updates on this?

@Laskewitz


Dataset compression

I would suggest compressing the CSV files to avoid this repo to become to bloated. E.g., tools like pandas can conveniently read gzip-ed files, and the difference for text data is typically huge, like 20x - 50x smaller file sizes.
Edit: that is, if you use the --best flag in gzip

Cool. Btw. did you remove the old CSV files from the git history? If not, just wanted to drop a handy script here:
#!/bin/bash
set -o errexit

# Author: David Underhill
# Script to permanently delete files/folders from your git repository.  To use
# it, cd to your repository's root and then run the script with a list of paths
# you want to delete, e.g., git-delete-history path1 path2

if [ $# -eq 0 ]; then
    exit 0
fi

# make sure we're at the root of git repo
if [ ! -d .git ]; then
    echo "Error: must run this script from the root of a git repository"
    exit 1
fi

# remove all paths passed as arguments from the history of the repo
files=$@
git filter-branch --index-filter "git rm -rf --cached --ignore-unmatch $files" HEAD

# remove the temporary history git-filter-branch otherwise leaves behind for a long time
rm -rf .git/refs/original/ && git reflog expire --all &&  git gc --aggressive --prune

Okay, I think that's done. Thanks!


Add Auto Splitter Support

This allows specifying an auto splitter.

This is blocked waiting on a new wasmtime release.


Updated frontend: fixed debug port not read from URI.

Please fix brackets style (missed spaces).
We use next syntax in node-inspector:
if (statement) {

}

function(args) {

}

I don't see the reason to use RuntimeQueryParamsObject  (one long name instead of one other).
It may be reasonable to use short and readable params.

Ok ;)

Looks better. I'm ready to merge this one. Please squash changes.

squashed

Landed as 88921eb8d097df9e20864fa5b0a38c0e0bd7bbc6


"FLEXLM"  -103 	 Terminal Server remote client not allowed.

RDPWRAP should have a way to allow bypassing Terminal Server application verification.

Each third-party software may use different ways for verification, this is too complex to implement and totally out of range.


redeploy and verify source code for baobab smart contracts

related repos:
https://github.com/Bisonai/vrf-consumer
https://github.com/Bisonai/data-feed-consumer
https://github.com/Bisonai/request-response-consumer

Already verified, and configure on baobab:
VRF:
Prepayment: 0x75e604c28b7e90af3019ae6982b294a70adc3581
VRFCoordinator: 0xfa605ca6dc9414e0f7fa322d3fd76535b33f7a4f
VRFMock: 0x7C73afa6CffC5A2F641C0bfB4E49178ce0ea731b
Request-response:
RequestResponseCoordinator: 0x402ab86A36686980F47C7097483d3ff1EAd5efE9
RequestResponseConsumer: 0x2ce551c4ddebcb70f6c88ec421f312069ebffeb6


Can you convert weights with stylegan1 tensorflow

Hello,
you can convert the weight from the official nvidia stylegan2 implementation. Is it also possible for stylegan1 tensorflow implementation?
Thanks!

Currently coverter for stylegan 1 was not implemented.


scripts: cleanup / add error codes

all scripts have been cleaned up with shellcheck, unnecessary parts are removed and all aborts are handled with an error code.
The following new error codes are introduced:
generic

SCRIPT_INVALID_ARG

ssd autosetup

SSDSETUP_NO_TARGET
SSDSETUP_TOO_MANY_TARGETS
SSDSETUP_ABORTED_MANUALLY

lightningd / electrs

BITCOIND_DEPENDENCY_NOT_ACTIVE
BITCOIND_IN_IBD

bbb-systemctl.sh

SYSTEMD_NOT_ALL_SERVICES_RUNNING

systemd-bitcoin-startpre.sh

BITCOIND_DIRECTORY_NOT_ACCESSIBLE

redis.sh.inc

REDIS_REQUIRED_BUT_NOT_RUNNING

systemd-startup-checks.sh

SSD_NOT_MOUNTED

systemd-update-checks.sh

MENDER_UPDATE_SYSCONFIG_FAILED

I like the effort. Make script failures and logs cleaner, but we should probably not confuse App<->Middleware RPC ErrorCode`s with system error codes that probably won't be transmitted to the App in a response to a RPC call faliure.

Do you think we should treat these errors differently, or use a prefix or something? Or not have these error codes at all?

More just fyi that I see no point in implementing them in e.g. the middleware errorcodes.go.
If we wan't to parse logs, then these probably will work best/easiest. Not sure when and where that parsing should happen though.

Ok, thanks. Waiting for your official approval before merging.


Create empty output directories with no files

No particular reason that this should be an error. Someone could use this to set up a directory structure (envs/, modules/) that they'll populate later.

LGTM


[joss-review] Fix installation instructions in README

README installation instructions direct the users to the "User guide" section of documentation for detailed instructions. However, these instructions are under "Getting Started". Please consolidate the differences between the github instructions and documentation.
I would advise providing either complete installation steps in the README or directing users to the documentation page. The way it stands currently, the steps provided in README are incomplete.

Thank you for pointing this out, it has now been corrected!
https://github.com/IPESE/REHO/commit/2528ccbc279cf3e0028ef1561118901ed65e7637


Update manage-creation-of-groups.md

Made some changes adding "-All" parameter to the Get-MgBetaGroup cmdlet, in order to retrieve all groups to ensure the capability to read over 100 elements in group lists. Also, I deleted the entire hash table that contains the 'EnableMSStandardBlockedWords' function since it is deprecated and retired. I only left the templateId.

Hello @MikePlumleyMSFT,  I see you've made an update. Is there something wrong with my contribution? It just I'm learning how to contribute, and I surely tested the code before and I wanted to fix it for others to use it if the case applies to them. I apologize for any inconvenience since I am very new at this. Thanks!

@danttelucorem you had updated some of the metadata at the top of the article which is something that we maintain internally.
@rahulnayakmicrosoft can you review this PR?


Remove tap/tester/ directory

Related to https://github.com/up9inc/mizu/pull/353 and https://github.com/up9inc/mizu/commit/2944493e2d04f49cf8c4c531950e6b5301904395#commitcomment-58346452
Use Local Machine Development Workflow instead. Don't maintain duplicate code.

I asked @dvdlevanon  to check that https://github.com/up9inc/mizu/wiki/Development-Workflows#local-machine-development-workflow is working for him well and then he can approve and we will merge..

Hi @mertyildiran
This tester helps us to test the tapper without using Docker/Minikube or spawning three different processes in order to test one (api-service, ninebase and tapper).
I'm aware of this snippet, https://github.com/up9inc/mizu/wiki/Development-Workflows#local-machine-development-workflow
And yet, running a single process in foreground instead of three in the background seems like a simpler solution to me.
Would you like to elaborate about the motivation to remove the tester?

Hi @mertyildiran
This tester helps us to test the tapper without using Docker/Minikube or spawning three different processes in order to test one (api-service, ninebase and tapper).
I'm aware of this snippet, https://github.com/up9inc/mizu/wiki/Development-Workflows#local-machine-development-workflow
And yet, running a single process in foreground instead of three in the background seems like a simpler solution to me.
Would you like to elaborate about the motivation to remove the tester?

we understand it can be removed, David will keep those file in his laptop if he needs to and we might bring better solution to run only tapper (because this is what the "tester" folder gave us


ENH: Add quadratic penalization to OSEM algorithm

Implement the quadratic penalization describes in [De Pierro, IEEE TMI,
1995].

Looks great, I have added a few style suggestions to follow the elvolving ITK style. Can you add a simple test? I guess you only need to set a beta in rtkosemtest.cxx...

By default the regularization is applied with a hyperparameter of 0.01, so rtkosemtest.cxx take already into account the regularization. Would you prefer to set the hyperparameter to 0 by default ?

By default the regularization is applied with a hyperparameter of 0.01, so rtkosemtest.cxx take already into account the regularization. Would you prefer to set the hyperparameter to 0 by default ?

Sorry, I missed that. It's fine like this, thanks!

I will fix the typo, sorry.


App Service balancing not working with per app scaling feature enabled

I have an ASP isolated with three instances and have deployed one App Service. I wanted to check if my app requests were balanced across all three instances, but it looks like it is only running on one instance. This is not what I was expecting based on the documentation.

My configuration:
Per site scaling = on numberOfWorkers = 1

What happens if I have 10 app services deployed in my ASP with 3 instances. Will my apps be balances between the 3 instances?

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

ID: b3fc1b23-aac2-8b7d-cca7-2da897059ab0
Version Independent ID: 12a2b1e7-43ad-97ea-4757-c69b407ea7ba
Content: Per-app scaling for high-density hosting - Azure App Service
Content Source: articles/app-service/manage-scale-per-app.md
Service: app-service
GitHub Login: @msangapu-msft
Microsoft Alias: msangapu

@jmayorga94
Thanks for your feedback! We will investigate and update as appropriate.

Hi @jmayorga94 It depends on your configuration of workers set by per-app scaling. If you want to use all 3 instances, set the workers to 3. I hope this was helpful.
#please-close
For further support please open a support ticket.


Add Getting Started section to README

README Update
Please add a getting started section to the README, so people would know how to start the project

Added Getting Started section to README file


Tuples

Remove dependency on tuples from SpacePinVisualizer.
Also, lower Unity dependency from Unity 2019.4 to Unity 2018.4 for Core and Examples.
Note that ASA still has U2020 dependency.

/azp run

/azp run


stylelint-order not applied

stylelint is working in sublime and the warnings are properly shown in the gutter, including the porperty order according to the following .stylellinrc I have:
{
  "plugins": [
    "stylelint-order"
  ],
  "rules": {
    // ...
    "order/declaration-block-properties-specified-order": [
      "float",
      "display",
      "position",
      // ...
    ]
  }
}

When I run the stylelintfmt command, the right order is not applied though. Anything I missed?
The console spits out only the warning, that are shown in the gutter, but nothing else happens:
{"line":306,"column":5,"rule":"order/declaration-block-properties-specified-order","severity":"error","text":"Expected margin-bottom to come before line-height (order/declaration-block-properties-specified-order)"}

Stylefmt does not support stylelint plugins yet. It is planned to land on v6 (current version is v5) according to https://github.com/morishitter/stylefmt/issues/216#issuecomment-259831538.
In the meantime you can probably still use the declaration-block-properties-order rule

Working since updated to stylefmt 6. Tested with:
{
  "plugins": [
    "stylelint-order"
  ],
  "rules": {
    "order/properties-order": [
      "padding",
      "color"
    ]
  }
}


Fold nested div with const

Fold (x//c+a)//d -> (x+ac)//(cd)
Fix the point from #7996

So this is failing because of vectorized ops and ranges, have to look more at it. Its lines like if u.op is Ops.CONST: const += f that are not written properly for this

vec=False to avoid vectorized const

Yeah I thought that but Upat.var doesn't have a vec keyword, and the cvar in the divisor is already a scalar


Forgot Password

Describe the feature you'd like
There should be an option to reset user password in case user forget his/her password. Currently, there is no support for that in the app
Would you like to work on the issue?

[x] Yes

Already have this feature. Check  #29


Support domain attribute for cookies

Sometimes we need to set a cookie for a specific domain, such as *.example.com. This allows the cookie to be valid across all subdomains.

It is already supported in HTTP proxy config: https://github.com/ytsaurus/ytsaurus/blob/main/yt/yt/library/auth_server/config.h#L406-L407


use events method of doing callbacks on client website with bundle

in addition to the current way of passing callbacks via the fn name

dispatchEvent('ProcaptchaBlah')

addEventListener('ProcaptchaBlah')

Low priority as we have a way of doing it already.

Closing as we can do this if asked.


Fixes for initialization of overlays returned from DynamicMaps

As the title says, makes sure that initialization of DynamicMaps returning Overlays doesn't get confused.

Ready to merge, bit of a hacky fix though, so I might file an issue to rethink how Overlays in DynamicMaps could be handled better.

Merging.


Add missing methods from serializer interface

This PR adds methods available  in the symfony serializer to the SerializerInterface such as denormalize and supportsDenormalization and similar

@lotyp please review

@coderabbitai review

@michaelcozzolino Thank you for your contribution! 🙏 And sorry for taking so long to review it.
I see that you had issue with missing methods on Manager class.
Currently for 1.x version original Symfony Serializer can be accessed by asking Laravel's container for it like this:
$serializer = $app->make(\Symfony\Component\Serializer\SerializerInterface);

https://github.com/wayofdev/laravel-symfony-serializer/blob/1.x/src/Bridge/Laravel/Providers/SerializerServiceProvider.php#L146
Right now I'm doing massive package refactor to release 2.x version.
Work is happening in this PR: https://github.com/wayofdev/laravel-symfony-serializer/pull/199
In 2.x version I've also added 2 Facades:
https://github.com/wayofdev/laravel-symfony-serializer/blob/2.x/src/Bridge/Laravel/Facades/Manager.php
https://github.com/wayofdev/laravel-symfony-serializer/blob/2.x/src/Bridge/Laravel/Facades/Serializer.php
To access Manager and original Serializer, that is already configured in Service Provider.
I will check your changes, and think, how Manager class can be improved, and does it need those methods, as normalization is done automatically, by calling serialize() method.
This was changed here, so no more manual normalization calls:
https://github.com/wayofdev/laravel-symfony-serializer/blob/2.x/src/Bridge/Laravel/Http/ResponseFactory.php#L72
And test is located here:
https://github.com/wayofdev/laravel-symfony-serializer/blob/2.x/tests/src/Functional/Bridge/Laravel/Http/ResponseFactoryTest.php#L92


Cannonical Evidence examples by ID

A request to dr1 IM or do1 IM with a CannonicalEvidenceId referring to one of the pilot's example CanonicalEvidence should use that CanonicalEvidence in the response.

The feature has been merged into main


ASR HUGGINGFACE_BACKBONES use AutoModel

What does this PR do?
This PR replaces the huggingface wav2vec for ctc with their automodel for ctc
Fixes # (issue)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

This is great :) ping us when this is ready @flozi00

Failing tests are caused by other reasons, for example 404 error from HF hub
@SeanNaren


[Feature request] Markdown Preview - Fullscreen

Describe the solution you'd like
An additional mode to preview the Markdown Pane in fullscreen, now there's only the split view
Additional context
Everything about this app is beautiful with fluent styling etc, so I'd love to be able to use the app with markdown in a presentation / fullscreen mode

Instead of a full preview, if the markdown compiles line by line, then it could be helpful.
Like in a line we write # Heading 1, after pressing enter or switching to any other line, the markdown converts the line into the Type 1 heading format(as in a regular markdown file). This feature could be more useful.


[WIP] Refactor import library to minimize duplication between importers, forms

Closing, will pick this back up in the future hopefully, but prioritising other work over this


GraphQLJSON type not exposed for use in custom endpoints

Link to reproduction
https://github.com/geisterfurz007/payload-3.0-graphql-repro
Payload Version
3.0.0-beta.43
Node Version
20.14.0
Next.js Version
15.0.0-rc.0
Describe the Bug
It's not possible to use a JSON type in custom GraphQL endpoints because payload uses an internal class that is not exposed. Using either of these imports (the upper one being what had worked in previous (stable) versions of payload) will lead to the same error:
import GraphQLJSON from "graphql-type-json";
import {GraphQLJSON} from 'graphql-scalars';

The error being:
 ⨯ Error: Schema must contain uniquely named types but contains multiple types named "JSON".
    at new GraphQLSchema (E:\Projects\Private\payload-3.0-graphql-repro\node_modules\graphql\type\schema.js:219:15)
    at configToSchema (webpack-internal:///(rsc)/./node_modules/@payloadcms/graphql/dist/index.js:101:20)
    at eval (webpack-internal:///(rsc)/./node_modules/@payloadcms/next/dist/routes/graphql/handler.js:68:95)
    at new Promise (<anonymous>)
    at getGraphql (webpack-internal:///(rsc)/./node_modules/@payloadcms/next/dist/routes/graphql/handler.js:67:26)
[...snip]

Poking about, it seems that graphql-type-json was copied over here but it's not exposed anywhere for users to consume when building custom endpoints.
Reproduction Steps

Clone the repo git clone git@github.com:geisterfurz007/payload-3.0-graphql-repro
Install dependencies yarn
Start the database ./start-database.sh
Launch next: yarn dev
Send a POST request to the endpoint to trigger a build of the schema: curl -X POST http://localhost:3000/api/graphql

Adapters and Plugins
No response

@geisterfurz007 a fix will be available in the next beta release. Check out this PR for more details: https://github.com/payloadcms/payload/commit/a26d03190e16fed3f526821f91ce998c1c2d4e99


Wire amount formatting; winning bidder fix; media gallery fixes

git cherry-pick'd a bucket-list of items. Need to verify some of the image stuff in the morning, seems some commit competition that's direction rather than syntax; so I'll check in on that & ping here when GTG.
New PR from origin instead of lefnire (https://github.com/deptagency/algomart/pull/371)

This PR is getting a bit crusty. If I'm not mistaken it just needs to be updated from main and to have one small Image update that Simon suggested.

@afraser I think I've got the simon points squared, and I just rebased to origin/main

Thanks @lefnire !


[alerting] Add pagerduty notifications

This PR adds an initial thin slice of functionality for PagerDuty alert support.
TODO:

[x] Add pagerduty client, with event v2 support
[x] Add configurations for pagerduty, example
[x] Add notify functionality from cloudprober to notify pagerduty

This PR adds:

pagerduty integration through the pagerduty routing key configuration in the probe/notifiers config.
trigger events (alarms) for probe alarm configs, using the events v2 API.

It also provides the basis for further development on the following functionality, which I will follow up with as feature requests in the issue tracker, for myself or others to pick up:

Enrich events with images.
Resolve events, once that functionality is included in cloudprober.

Thanks so much, @robpickerill!


Florida Test File Creation Updates

This PR does is a set of changes to make the creation of the FL test file go more smoothly.
Changes

Changes the FL schema to use more codes for fields where it makes sense
Added some Florida-specific value sets. I'm not crazy about a file per state for their own value sets, but having a single file for all states might be unwieldy. I'm open to suggestions
Updated the FakeReport generator to take alternate values into account for other schemas and return logical values for some of the FL AOE fields
Tests

Checklist

[x] Tested locally?
[ ] Added new dependencies?
[x] Updated the docs?
[x] Added a test?
[x] Did you check for sensitive data, and remove any?
[ ] Are additional approvals needed for this change?
[ ] Are there potential vulnerabilities or licensing issues with any new dependencies introduced?

Fixes

#109

@RickHawesUSDS I've added a BLANK type for Elements now to always pass a blank column for SSN. Can you approve my PR so we can get this in before any more big changes come in? Thank you!

@RickHawesUSDS I've added a BLANK type for Elements now to always pass a blank column for SSN. Can you approve my PR so we can get this in before any more big changes come in? Thank you!


Fixed inconsistent input spec in anatomical.py CNR computation

Fixes issue #919.

Apologies, I accidentally closed the issue by force-pushing to your repo. I have replaced this PR with the one linked above.


WIP: new screenshots after feedback

Added a couple of new screenshots adjusted according to feedback.
Unfortunately the hover tooltip shows the trace name as "trace 0" instead of trace name specified in the options. Thus there are 2 different screenshots with and without the hover.
The README is not yet modified, because some more feedback is needed on which picture to choose.

I think we got this merged -- but submit again (or just post the images and I will merge)


build: fix failing builds

It's been failing for over a week
https://travis-ci.org/GoogleCloudPlatform/gcloud-golang/builds
/cc @zombiezen @jba @adams-sarah @shantuo

I enabled the Vision API on the project. The other failures are real test failures or flaky tests that should be addressed.

We should make CI integration with Gerrit a priority.
I'm happy to finish your work on this @broady once I finish datastore entity_values.

Awesome. For reference - https://github.com/broady/travis-tools
My suggestion is using the Container Builder API to execute the tests.
https://cloud.google.com/container-builder/docs/quickstart
Sample implementation of that API:
https://github.com/broady/cdbuild/blob/master/main.go
Not sure about integration with Gerrit (ala Go's TryBot), but I think it works via web hooks.

Awesome @broady I'll start on this ASAP.

I'll make a change to loosen the deadline for that test.
On Tue, Aug 30, 2016, 5:00 PM Sarah Adams<EMAIL_ADDRESS>wrote:

Awesome @broady https://github.com/broady I'll start on this ASAP.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-golang/issues/335#issuecomment-243579173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACTr9sfTFHyKqgYc_8DLEt7E4fPEBUpks5qlJnXgaJpZM4Jw9Fr
.

I cannot reproduce the pubsub test failure. I ran multiple times for all the pubsub tests with race flag when I fixed the pubsub unit tests and never saw this one.
--- FAIL: TestAll (7.20s)
integration_test.go:71: CreateSub error: googleapi: Error 503: Authentication backend unavailable., backendError
integration_test.go:87: subscription subscription-1472558298 should exist, but it doesn't
integration_test.go:121: error constructing iterator: googleapi: Error 404: Resource not found (resource=subscription-1472558298)., notFound

I am working on the storage test failure:
--- FAIL: TestCondition (0.06s)
storage_test.go:395: 5. RequestURI = "GET /storage/v1/b/buck/o/obj?alt=json&ifMetagenerationNotMatch=1234&projection=full"; want "GET https://www.googleapis.com/storage/v1/b/buck/o/obj?alt=json&ifMetagenerationNotMatch=1234&projection=full"
storage_test.go:395: 6. RequestURI = "PATCH /storage/v1/b/buck/o/obj?alt=json&ifMetagenerationMatch=1234&projection=full"; want "PATCH https://www.googleapis.com/storage/v1/b/buck/o/obj?alt=json&ifMetagenerationMatch=1234&projection=full"
storage_test.go:395: 7. RequestURI = "DELETE /storage/v1/b/buck/o/obj?alt=json&generation=1234"; want "DELETE https://www.googleapis.com/storage/v1/b/buck/o/obj?alt=json&generation=1234"
storage_test.go:395: 8. RequestURI = "POST /upload/storage/v1/b/buck/o?alt=json&ifGenerationMatch=1234&projection=full&uploadType=multipart"; want "POST https://www.googleapis.com/upload/storage/v1/b/buck/o?alt=json&ifGenerationMatch=1234&projection=full&uploadType=multipart"
storage_test.go:395: 9. RequestURI = "POST /storage/v1/b/buck/o/obj/copyTo/b/dstbuck/o/dst?alt=json&ifMetagenerationMatch=5678&ifSourceGenerationMatch=1234&projection=full"; want "POST https://www.googleapis.com/storage/v1/b/buck/o/obj/copyTo/b/dstbuck/o/dst?alt=json&ifMetagenerationMatch=5678&ifSourceGenerationMatch=1234&projection=full"

@shantuo, that latest one is related to @okdave's recent change: https://github.com/google/google-api-go-client/commit/bb198ac8a40e08503277ebd527a8898bbfbe27fb
You should just be able to remove the https://www.googleapis.com/storage part of the "want" values.

@bradfitz Thanks for the pointer!

For the failure in the new logging package we got:
2016/08/30 11:57:06 creating prod client: google.DefaultTokenSource: google: could not find default credentials. See https://developers.google.com/accounts/docs/application-default-credentials for more information.
FAIL	cloud.google.com/go/preview/logging	0.049s

Do I need some special credentials for this preview/logging API?

Sounds like a bad test. Check the other tests to see how to create a TokenSource suitable for integration tests.

No special creds. Should work if you've configured your environment as per
CONTRIBUTING.md.
On Tue, Aug 30, 2016 at 8:03 PM Chris Broadfoot<EMAIL_ADDRESS>wrote:

Sounds like a bad test. Check the other tests to see how to create a
TokenSource suitable for integration tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-golang/issues/335#issuecomment-243619559,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARoHZb537RQWlZEbo3BiBdniu2efiX8Uks5qlMTigaJpZM4Jw9Fr
.

Sent CL 7271 for the logging credentials. option.WithGRPCDialOption doesn't override the application default credentials.
Basically, no one should ever use option.WithGRPCDialOption(grpc.WithPerRPCCredentials(...)).
Also, WithClientTLSFromCert(nil, "") is the default.

Logging is better now, but still fails:
Sink: name:"GO-CLIENT-TEST-SINK-1472621764-0013" destination:"storage.googleapis.com/dulcet-port-762" filter:"logName = \"projects/dulcet-port-762/logs/GO-LOGGING-CLIENT-TEST-LOG\"" output_version_format:V2
--- FAIL: TestCreateDeleteSink (0.11s)
	sinks_test.go:72: rpc error: code = 7 desc = The caller does not have permission
=== RUN   TestUpdateSink
--- FAIL: TestUpdateSink (0.08s)
	sinks_test.go:107: rpc error: code = 7 desc = The caller does not have permission
=== RUN   TestListSinks
Sink: name:"GO-CLIENT-TEST-SINK-1472621764-0015" destination:"storage.googleapis.com/dulcet-port-762" filter:"logName = \"projects/dulcet-port-762/logs/GO-LOGGING-CLIENT-TEST-LOG\"" output_version_format:V2
--- FAIL: TestListSinks (0.08s)
	sinks_test.go:150: Create("GO-CLIENT-TEST-SINK-1472621764-0015"): rpc error: code = 7 desc = The caller does not have permission

@jba - that bucket has given the logs service account Owner permission. What's this failure? I reproduce this locally with my cbro-scratch project, too.

Chris,
First let's fix your local project.
Did you do
$ gsutil acl ch -u cloud-logs@system.gserviceaccount.com:O gs://cbro-scratch
On Wed, Aug 31, 2016 at 1:43 AM Chris Broadfoot<EMAIL_ADDRESS>wrote:

Logging is better now, but still fails:
Sink: name:"GO-CLIENT-TEST-SINK-1472621764-0013" destination:"storage.googleapis.com/dulcet-port-762" filter:"logName = "projects/dulcet-port-762/logs/GO-LOGGING-CLIENT-TEST-LOG"" output_version_format:V2
--- FAIL: TestCreateDeleteSink (0.11s)
sinks_test.go:72: rpc error: code = 7 desc = The caller does not have permission
=== RUN   TestUpdateSink
--- FAIL: TestUpdateSink (0.08s)
sinks_test.go:107: rpc error: code = 7 desc = The caller does not have permission
=== RUN   TestListSinks
Sink: name:"GO-CLIENT-TEST-SINK-1472621764-0015" destination:"storage.googleapis.com/dulcet-port-762" filter:"logName = "projects/dulcet-port-762/logs/GO-LOGGING-CLIENT-TEST-LOG"" output_version_format:V2
--- FAIL: TestListSinks (0.08s)
sinks_test.go:150: Create("GO-CLIENT-TEST-SINK-1472621764-0015"): rpc error: code = 7 desc = The caller does not have permission
@jba https://github.com/jba - that bucket has given the logs service
account Owner permission. What's this failure? I reproduce this locally
with my cbro-scratch project, too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-golang/issues/335#issuecomment-243664208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARoHZWczrQeERxh_pvI0fv1KpvDkWU7sks5qlRR2gaJpZM4Jw9Fr
.

Yup, I have those permissions. Same failures.
Also ran gsutil acl ch -g cloud-logs@google.com:O gs://cbro-scratch
TestLogSync looks flaky, too. First run:
logging_test.go:226: got 1 entries, want 2
Second run:
logging_test.go:226: got 3 entries, want 2
On Wed, Aug 31, 2016 at 4:31 AM, Jonathan Amsterdam <
<EMAIL_ADDRESS>wrote:

Chris,
First let's fix your local project.
Did you do
$ gsutil acl ch -u cloud-logs@system.gserviceaccount.com:O
gs://cbro-scratch
On Wed, Aug 31, 2016 at 1:43 AM Chris Broadfoot<EMAIL_ADDRESS>wrote:

Logging is better now, but still fails:
Sink: name:"GO-CLIENT-TEST-SINK-1472621764-0013" destination:"storage.
googleapis.com/dulcet-port-762" filter:"logName =
"projects/dulcet-port-762/logs/GO-LOGGING-CLIENT-TEST-LOG""
output_version_format:V2
--- FAIL: TestCreateDeleteSink (0.11s)
sinks_test.go:72: rpc error: code = 7 desc = The caller does not have
permission
=== RUN TestUpdateSink
--- FAIL: TestUpdateSink (0.08s)
sinks_test.go:107: rpc error: code = 7 desc = The caller does not have
permission
=== RUN TestListSinks
Sink: name:"GO-CLIENT-TEST-SINK-1472621764-0015" destination:"storage.
googleapis.com/dulcet-port-762" filter:"logName =
"projects/dulcet-port-762/logs/GO-LOGGING-CLIENT-TEST-LOG""
output_version_format:V2
--- FAIL: TestListSinks (0.08s)
sinks_test.go:150: Create("GO-CLIENT-TEST-SINK-1472621764-0015"): rpc
error: code = 7 desc = The caller does not have permission
@jba https://github.com/jba - that bucket has given the logs service
account Owner permission. What's this failure? I reproduce this locally
with my cbro-scratch project, too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/GoogleCloudPlatform/gcloud-golang/issues/335#
issuecomment-243664208>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARoHZWczrQeERxh_
pvI0fv1KpvDkWU7sks5qlRR2gaJpZM4Jw9Fr>

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-golang/issues/335#issuecomment-243736766,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABhlq6tnnGQ9lUMJbGfyPnm0POuih08ks5qlWYZgaJpZM4Jw9Fr
.

Nice work, everyone! We're down to two failures.
The permissions error for the log sink integration test (@jba and @cbro investigating), and the change related to the Google API client (@shantuo - are you fixing this?).

@jba and I initially missed one thing in the log export directions: the account performing the export must be an Owner or have the Logs Configuration Writer IAM role.
@jba added that to the service account used on Travis. I've kicked off another build to verify.

Logging permissions work now, but the test fails with this error:

Sinks with different output formats cannot share destination. There already is a project sink with V1 output format.

I've tried to fix that but can't. Asked for help from cloud logging folks.
On Wed, Aug 31, 2016 at 12:36 PM Chris Broadfoot<EMAIL_ADDRESS>wrote:

Logging permissions work now, but the test fails with this error:
Sinks with different output formats cannot share destination. There
already is a project sink with V1 output format.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/gcloud-golang/issues/335#issuecomment-243823197,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARoHZSMKfl4e_cY-k26c3MlTMydPIuRlks5qla1zgaJpZM4Jw9Fr
.

Yeah, not so great. How about creating a new bucket for each test?

@okdave @cbro Are you okay with having logging tests depend on the storage client?

Yep!

Yeah, that's fine.


feat: Updated README.md

#1379  Revamped Readme with improved grammar, corrected typos, and enhanced readability for an optimal user experience.
Closes #1408

Description

Used the typing animation for the declaration of GSSoc'23, and a welcome note by Free-Hit.
Fixed the typos and indentations.
Presented the content in a more reasonable manner.
Updated the hyperlinks and bind them into the attached text.
Used some attractive animated separators to beautify the Readme and enhance readability.

Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

@JasonDsouza212 Please have a look and if need any further edits, please mention it.


Add support for feature set updates and remove versions

What this PR does / why we need it:
Addresses #386, and implemented in accordance with this RFC.
For backward compatibility, user facing code still allows users to provide versions, but they will be ignored.
This PR is built on top of #655.
Which issue(s) this PR fixes:

Fixes #386
Does this PR introduce a user-facing change?:

Elements in the DB will have to be migrated to only retain the latest feature sets.

Elements in the DB will have to be migrated to only retain the latest feature sets.
Should we add the note that versions will be ignored hence forth?

/retest

Pending fix for #677 to pass end to end tests

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end-batch

/test test-end-to-end

/lgtm


feat: setup terraform provider

Motivation and Context
See:  https://github.com/wundergraph/cosmo/blob/45d7f599b63f38a019f37a202d9b93bb924120d8/terraform-provider/README.md which contains links to the referenced resources and datasources.
for further details
TODO

[ ] Tests or benchmark included
[ ] Documentation is changed or added on https://app.gitbook.com/
[ ] PR title must follow conventional-commit-standard

For further comments see: https://github.com/wundergraph/terraform-provider-cosmo/pull/1
Will incorporate the rest of the feedback there.


Docs ref glossary fundamental 0

Update fundamental glossaries
Signed-off-by: Loc Mai<EMAIL_ADDRESS>

Hi @locmai Please resolve all the defects detected by @sftim. Thanks!

@locmai, I'm afraid you'd also need to rebase this PR.

@locmai here's some feedback.
Please bear in mind: I don't speak any Vietnamese. I'm commenting based on how this looks to me as an English speaker. So, I might be making wrong judgements.

Hi guys, sorry for the delayed, I'm gonna update this PR soon in the next 1-2 days :D

Hi @sftim @truongnh1992 , I have fixed the issues above.
Some terms could be simply translated like Annotation => "Chú thích", but the usage of the word might be different, so I left it as Tim suggested - "Chú thích (Annotation) for Label, Controller, Annotation, Selector.
For terms like Service, Pod, Deployment, etc (mostly k8s resources), we might want to keep the original terms.
Thanks for reviewing the PR guys :D please help me double-check again!


Allow parseOptions to be on load metadata

This will allow different files to have different Traceur compilation options.

:+1:

I don't see how this is practically useful. I don't think we should make specific code transpile assumptions.


feat: use output.txt files to refer to command outputs

Identify all places where we manually insert the output of a command
Create a output.txt at the root of the listing package
first line should be $ command-to-run, e.g.: $scarb build

next, run the rust script
cargo run --bin cairo-listings --output to generate the outputs
Replace the hand-written output by a reference to the output file.

Hi @enitrat, is this issue up for grabs?

Yes, go ahead


BetterHUD crashing when interacting wirh raw silicone ore from Galacticraft 4

Hey,
BetterHUD is crashing when I look with BetterHUD (all features enabled) at a block of raw silicone ore, (this article is quite old, it doesn't look exactly the same)
, with the result java.lang.ArrayIndexOutOfBoundsException: -1. I'm quite sure that's it.
Logs are quite messed with buildcraft errors, sorry about that, the main problem sits in the end.
Thanks
2020-01-24-6.log

This appears to be a Galacticraft issue, and only 1.12.2 is supported currently. 1.8.9 is unlikely to receive a backport.


New version: JetBrains.IntelliJIDEA.Community.EAP version 222.2680.4

Result: Installation Failed

Manifest
Add/Remove Programs

Name
IntelliJ IDEA Community Edition (EAP)

Version
222.2680.4

Publisher
JetBrains s.r.o.

ProductCode
IntelliJ IDEA Community Edition 221.5787.3

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1750
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


Lookup error issue in nltk even with new version 3.9.1, similar to PR #3308

I'm getting this error, which is similar to the error that caused this PR except it's with the resource punkt_tab.
raise LookupError(resource_not_found)
LookupError:
Resource punkt_tab not found.
Please use the NLTK Downloader to obtain the resource:

>>> import nltk
>>> nltk.download('punkt_tab')

For more information see: https://www.nltk.org/data.html

@kirupang-code have you tried to download punkt_tab as suggested?

So to be clear, this was an intentional breaking change that wasn't documented? This indeed broke our app https://github.com/paperless-ngx/paperless-ngx/issues/7519 so just trying to figure out if this will change again

Nobody should depend on Nltk 3.8.1 because that exposes their users to potentially lethal "sleepy pickle" attacks.
Everybody needs to update their Nltk version to 3.9.1.

I would say the breaking change is that the code below doesn't work following a 3.8 to 3.9 update and requires changing what is pre-downloaded from punkt to punkt_tab:
>>> from nltk.tokenize import word_tokenize
>>> s = '''Good muffins cost $3.88\nin New York.  Please buy me
... two of them.\n\nThanks.'''
>>> word_tokenize(s)

The change from #3283 from to require punkt_tab instead of punkt is not documented.  I assume it is the line about pickled models, but there is no warning the data name required changed or migration steps.

raise LookupError(resource_not_found)
LookupError:
Resource punkt_tab not found.
Please use the NLTK Downloader to obtain the resource:

import nltk
nltk.download('punkt_tab')

For more information see: https://www.nltk.org/data.html

@kirupang-code, the message is clear: you need to  download punkt_tab:
import nltk
nltk.download('punkt_tab')

@stumpylog, more documentation could certainly be useful, and you are very welcome to contribute some.


DBZ-7947 Check for read-only mode incompatibility

closes: https://issues.redhat.com/browse/DBZ-7947

This failure are fixed with https://github.com/debezium/debezium/pull/5624/files#diff-262dfe4690606ccae9bae002aea572b8750007242d5a7628efb8052c69dff047R206.
It is related to the recent change on the PostgreSQL version used in the tests (10 -> 12).

@mfvitale Applied, thanks!


Wooden decoratives from Dectorio leave ash when burned

Mod source
Factorio Mod Portal
Which mod are you having an issue with?

[ ] pyalienlife
[ ] pyalternativeenergy
[X] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system
GNU/Linux
What kind of issue is this?

[X] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[X] Balance
[ ] Pypostprocessing failure
[ ] Other

What is the problem?
The wooden floorboards + wooden barriers introduced by Dectorio leave ash when burned, despite being crafted exclusively from wood. I assume this might pose a balance issue, as other wood items don't leave ash behind when burned?

Steps to reproduce
Install e.g. the full pY+AL suite with Dectorio; verify that the Dectorio wooden items leave ash behind when burned.
Additional context
No response
Log file
(not relevant)

Thanks for the report. Can you list the internal item names of these wooden items? Then I can add them to the blacklist.

I was about to post that in a comment myself when I realized that'd be useful information. :)
The items are dect-wood-floor and dect-wood-wall.

Thanks for the report, but this is intended.
There is no rule against wooden items leaving ash. For example the wooden chest leaves ash:

Our only rule is that items with a fuel value cannot be voided. Logs not being voidable is just an application of the rule and not the rule itself.


Drop outdated numpy_compat functions

These functions (nancumsum and nancumprod) have been removed as part of bumping the NumPy requirement to 1.13.0. So drop these fallback imports as these functions don't exist any more.

[ ] Tests added / passed
[ ] Passes flake8 dask

Hooray for dropping things!  +1 from me if tests pass.

Will merge on green

Thanks @jakirkham

Thanks for all the timely feedback 😄


Fix bug when #! ends with carriage return

Fixes #2996
Fixes the second issue here:
TestRubyOptions#test_shebang [/Users/alex/src/github.com/Ruby/ruby/test/ruby/test_rubyoptions.rb:514]:
pid 49518 exit 0.

1. [1/2] Assertion for "stdout"
   | <["\"あ\""]> expected but was
   | <["\"\\u3042\""]>.

2. [2/2] Assertion for "stderr"
   | Expected /shebang line ending with \\r/ to match "".

Finished tests in 0.030572s, 32.7097 tests/s, 359.8064 assertions/s.
1 tests, 11 assertions, 1 failures, 0 errors, 0 skips

ruby -v: ruby 3.4.0dev (2024-08-22T14:01:55Z master 56a34b5af5) +PRISM [arm64-darwin23]
make: *** [yes-test-all] Error 1

@kddnewton Makes sense.
Just to clarify, the last "valid" index of this slice is at [length - 1], and [length] is one past the end (at least the part of it that we're guaranteed to exist), right?


Evaluate performance impact of debug dependency

Throughout the repo there are usages of debug. We should follow up here and make sure we want to keep this dependency vs leveraging the logger more thoroughly and adding some "verbose" local debugging capabilities.
Here are some things to think about:

Bundle size - debug + it's dependency ms are actually pretty small, coming in at ~6KB before compression. This is about 5% of our current minimal bundle that has just a container runtime. Would be nice to shave off that ~6KB, but there are bigger opportunities for bundle size alone, like lodash which is about 17KB uncompressed
Runtime cost - I don't have a ton of evidence of heavy resource usage at runtime, but my expectation is that debug should have no cost unless it is opted in to. I do see it having an impact at runtime below (t.useColors is coming from debug, cost is <.2 ms in this sample), but I don't see it frequently enough to be considered a serious problem. It may be a one time initialization cost from evaluating the module, in which case it is not a big concern. If we do see it frequently, then I it would raise the priority of this.

As a summary, there isn't a huge known issue here, but would be good with someone in the telemetry space on Fluid Framework to define the direction here for local debugging vs internal logger and to be confident that we aren't seeing any runtime cost when users have not opted in

I have looked at the code and these are initial cost only.  There should be very small performance hit, as long as the caller doesn't do heavy computation to create the debug message.


Smtp tests lf conditions/v4

Redmine tickets:

https://redmine.openinfosecfoundation.org/issues/5981
https://redmine.openinfosecfoundation.org/issues/5989
https://redmine.openinfosecfoundation.org/issues/6053

Previous PR: https://github.com/OISF/suricata-verify/pull/1405
Changes since v3:

cleanup history
keep minimal settings
rebase

Merged in #1409, thanks!


bugfix: AccountPermissions was not returning the proper type

The __or__ and __add__ methods on AccountPermissions were returning ResourceTypes instead of AccountPermissions

Codecov Report

Merging #365 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master     #365   +/-   ##
=======================================
  Coverage   85.13%   85.13%
=======================================
  Files          56       56
  Lines        4332     4332
  Branches      463      463
=======================================
  Hits         3688     3688
  Misses        506      506
  Partials      138      138

Impacted Files
Coverage Δ

...zure-storage-common/azure/storage/common/models.py
90.68% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Widget form component

To be done:

[x] Start using backbone-forms.
[x] Create schema for each widget type (structure and specs).
[x] Render all form attributes for each widget type (neither tab-pane nor stack-views, TBD).
[x] If widget type changes, form should be recreated.
[x] If widget type changes, widget definition model attributes should change, removing unnecessary properties for the new type. For example, 'bins' property within a Histogram is not necessary for Formula widget.
[x] Generate formModel within widget definition model.
[x] When widget type changes, remove widget definition model and create a new one.
[x] When the widget definition form is edited, widget should be updated (This issue shold be done first -> https://github.com/CartoDB/deep-insights.js/issues/106).
[x] Decide how and where to update the data of the select(s) when a previous one has changed?

Managed within each widget form model.

[x] Improve saving of attributes from the widget form model to the widget def model.

Eg: this.widgetDefinitionModel.saveAttributes(this.widgetFormModel.changed);
Also, important to take into account the deep-insights widget update.
- Eg: this._widgetModel.update(changed);

[x] Review all "commented" specs + new ones.
[x] Some widget attributes are not being updated in Deep-Insights widgets (https://github.com/CartoDB/deep-insights.js/pull/138). #6546
[x] Make use of new table&user data models within widget form values -> #6551
[x] cast sync_on_*_change params to booleans, to be applied on widgets as expected

Branch: editor3-form-component

For this component, I have some ideas that I'd like to discuss, perhaps later today?
For starters, I recommend reading http://blog.codeclimate.com/blog/2012/10/17/7-ways-to-decompose-fat-activerecord-models/ and in particular 3. Extract Form Objects. The article is intended for Ruby/Rails but I think the conceptual ideas can just be applied just as well on Backbone models and collections.

Adding some documentation I'm finding:

https://github.com/powmedia/backbone-forms

A work on progress with @javierarce (TM)

@juanignaciosl was the assignment on purpose or a mistake? :sweat_smile:

I can't remember having assigned this (or anything) to you today, maybe my laptop was kidnapped :P

Moving to @viddo and @javierarce.

closing, since was finished as part of merging #6561


Redis on TravisCI setup as PECL extension

Redis doesn't require to be installed on TravisCI but only enabled.

ping @Ocramius

@EmanueleMinotto :+1:


Is the file renaming feature supposed to take so long?

When trying to use the 'rename existing files' option on a folder with a few hundred (300) images and danbooru as a source, it takes hours to get to a few dozen of the total. It's actually faster for me to delete the images and download it again.
OS:Linux

No, it shouldn't, especially for only 300 images.
There are two possible situations though:

In one case the renaming should be almost instantaneous: if the tokens in the new filename are the same as in the original (or a subset), for example %artist%/%md5%.%ext% => %md5%.%ext%.
The other case would be if Grabber needs to re-download missing image meta-data, for example %md5%.%ext% => %artist%/%md5%.%ext%. In that situation, it should only take as long as loading 300 small HTML pages (the images' information).

What were you renaming from/to?
I'll check tonight if I can reproduce any speed issues.

I'm keeping the same filename pattern %artist%.%copyright%.%character%.%md5%.%ext%, but I wanted to increase the number of copyright and character tags (previously only one for each) because I have a lot of images with crossover because it had 2 copyright tags.
It would be nice if the GUI gave more information about what Grabber was doing and where it was getting stuck, because all I have is a progress bar with a x/total besides it.


Incorrect/Update Information Required for N GANESHKUMAR

What is the issue about?
N GANESHKUMAR's information is incorrect/needs to be updated...
What Information needs to be updated or corrected?
In the profile links are missing (i.e) Instagram,Github,LinkedIn,mail,etc.
Internal Usage [DO NOT DELETE]

Profile Slug: n-ganeshkumar

Hey @Ganesh5757, the details have been updated 👉 https://0xsrmist.xyz/team/n-ganeshkumar
If everything is alright feel free to close this issue as completed.


WAF ACL does not show up in CloudFront

I have run this as per the readme file, and it successully created a WAF ACL. However that WAF ACL is not visible in CloudFront when creating a new distribution. I think the WAF ACL (and related settings) need to be created in the global region, whereas this cdk uses the default user's default region (ie. us-east-1), however global is not a valid region for cdk so doing export AWS_DEFAULT_REGION=global before running cdk bootstrap does not work.
Perhaps there is another setting required in the cdk call to create the WAF ACL.

Thank you for the feedback.  We will take a look and get back to you as soon as we can.

OK, we've had a little time to research the issue.  The particular use case for this project is to attach a WAF Web ACL to an Application Load Balancer located in a region.  The Web ACL would have an IP Set rule attached to it, and that IP Set would be populated with the current CloudFront service endpoint CIDRs.  The goal here is to restrict traffic on the ALB to traffic coming from CloudFront only.  In this way, the WAF IP Set and Web ACL are both regional resources, as they are ultimately associated with an ALB running in the region.

Oh of course, the WAF ACL in Cloudfront is for traffic inbound to cloudfront. Where as controlling traffic from cloudfront to an internal resource would require an ALB to run the WAF ACL your tool creates. Apologies for the daft question.


[macOS, Windows] Add support for excluding windows from a screenshot.

Adds flag to exclude window for screenshots taken by DisplayServer, allowing it to stay on to of the screen part that is captured.
Intended for better color picker and similar overlays (e.g., magnifier, color blindness simulator tool).
TODO:

[ ] Use it for the Godot color picking controls.
[ ] ~Check if it's possible to implement on X11 and Wayland as well.~

https://github.com/godotengine/godot/assets/7645683/4a5514b4-ed37-4e3c-93d6-e73ec1edaaa0

Updated to incorporate #98411 changes (for both native and legacy picker):
https://github.com/user-attachments/assets/8acb5a1c-8eca-417c-ac83-a27a9dbf4e87

Thanks!


Integrate the grpc-libp2p when instantiating the grpc server

Use the centID from the config as the protocol ID.

no longer required after removing P2P GRPC
cc @mikiquantum @lucasvo


feat: Enable caching functionality on appsmith-server module

Server workflow running at : https://github.com/appsmithorg/appsmith/actions/runs/2809732977

Server workflow after fixing compilation issue : https://github.com/appsmithorg/appsmith/actions/runs/2809917503

/ok-to-test sha=c4aa09a

Appsmith Server workflow : https://github.com/appsmithorg/appsmith/actions/runs/2819760673

Server workflow running at : https://github.com/appsmithorg/appsmith/actions/runs/2831766377

Got a go ahead to merge from @sidhantgoel. Merging.


Don't identify SRP groups solely by their size

Although at the moment we use DH groups exclusively from RFC 3526, which specifies only one group of each size, we may find ourselves seeking out different 4096 groups. So we shouldn't be identifying groups in our code exclusively by their size as we do with GetGroupName().
Copied from https://github.com/agilebits/op/issues/144

Old, no longer applicable issue.