Set up conda package

Fixes #1

[x] Added conda build and dev environments
[x] Added conda recipe for conda package
[x] Added pyproject.toml for pip installation in dev mode
[x] Added versioneer files for package versioning
[x] Added conda build verify to CI
[x] Set up CD for conda package upload to accessnri anaconda.org.

I haven't touched the main scripts in this PR, and the new package has the era5grib_parallel entry point, to be called from the rose suite (to be changed in the nci_era5grib_parallel task rose-app.conf file).

Closed as this PR has been substituted by #3.


Grabbing focus on ProjectList after clicking an item.

The fix is local, in ProjectManager itself (not modyfing line_edit as it was introduced in #37281).
It works like: clicking on an item and then pressing ENTER.
Unfortunatelly - pressing Tab key in ProjectManager is kinda messed up, focus is transmitted kinda random - but that's not introduced/fixed by this PR.
Fixes: #39012

Thanks!

Cherry-picked for 3.2.2.


is test.hurl correct ?

Hi, just wondering. Is test.hurl for CH2 correct ? seems to be missing
GET http://localhost:3000/lowercase {   "value": "RaWKoDe" }
around line #14
I corrected it locally and then correctly parses the local version of my submission.
But then again, when I hurl submit CH2 'officially' it fails with:
Endpoint didn't contain correct Content-Type header!
Thanks in advance, Dennis

Hey @dennisg!
Thanks for raising this, unfortunately there was a typo in the backend test suite.
Could you resubmit and let me know if it's working now, please?

Hi @rawkode , Unfortunately I see the same error, still

Apologies, @dennisg. I've found the bug and will update ASAP

@dennisg Fixed the bug.
My solution passes and is available here:
https://github.com/rawkode/advent-of-spin/tree/main/2022/challenge-2


Update README.md

pq ta errado

Justifique.

From: Yuri Sales<EMAIL_ADDRESS>Sent: Wednesday, April 26, 2017 7:15:26 AM
To: Mazuh/Algs
Cc: Marcell Guilherme Costa da Silva; Comment
Subject: Re: [Mazuh/Algs] Update README.md (#1)
pq ta errado
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Mazuh/Algs/pull/1#issuecomment-297335965, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AF8sVtAOSwxBo8b-EwwixkiM-Xr9pSi4ks5rzxk-gaJpZM4NIM8A.

"and right before I went to college." = e antes de eu fui pra universidade


Remove www folder from Bower package.

As far as I know, there's no need for this folder to be included with bower. You already get rid of a bunch of non-production files, including the test files, so the www folder likely ought to be included in that, no?

implying I have any idea what I'm doing

Thanks!

By the way, just wanted to say: Love Intercooler; spotted it a few days ago on HN and immediately started using it for a couple of different client projects. Love just being able to sprinkle functionality in as needed.

That's awesome to hear

Hahaha that's fantastic, I've gotta use that whenever I tell people about Intercooler.


Failed to minify

The dependancy drag-drop-touch-polyfill that you are using haven't compiled their code to ES5.
I have "forked" their repo to compile it. The original repo is on bitbucket.
With this dependancy react-builds run is working fine!
Here is the repo with the modification applied.
By the way - React-Agenda is awesome.

Hi and thank you for your report and fix , glad you liked it , i forked your repo and updated the main package.json. if you have any further suggestion , feel free to share ;)

I have one! I am using react-agenda for an agenda purpose and a one week schedule.
And the one week schedule starts to create problems. I will probably fork your repo to let your component do it by passing a param. Because the whole thing is there, it's just a UI problem! I am trying to handle it out of the component itself but in the long run, it's not a viable option.
By the way, sympathique les locales en fr dans l'exemple du repo.

can you give some details about the issue ?  if it's not related to this module please fill another issue.


Testing infrastructure not working due to k8s api returning 401

/kind bug
Hi everybody! I keep getting the following error from kubeflow-kfserving-presubmit while testing my PR:
INFO|2021-09-02T06:53:06|/src/kubeflow/testing/py/kubeflow/testing/argo_client.py|48| Parsing ApiException body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Unauthorized","reason":"Unauthorized","code":401}
INFO|2021-09-02T06:53:06|/src/kubeflow/testing/py/kubeflow/testing/argo_client.py|60| ApiException code=401

Links:
PR: https://github.com/kubeflow/kfserving/pull/1780
Build log: http://prow.kubeflow-testing.com/view/s3/aws-kubeflow-jenkins/pr-logs/pull/kubeflow_kfserving/1780/kubeflow-kfserving-presubmit/1433318011783090176
At first I thought it was a problem with my PR, but after looking into the testing code it seems as if a token expired and now the k8s API returns 401.
What did you expect to happen:
No HTTP 401s errors from the K8s API.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version:
Knative Version:
KFServing Version:
Kubeflow version:
Kfdef:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Minikube version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

https://github.com/kserve/kserve/pull/44


[Feed] Smarter ordering of posts to surface relevant content

Problem
Our platform currently does not prioritize the most relevant and engaging content, which makes it difficult for users to discover high-quality posts and stay engaged. This ticket introduces a smarter ordering system for posts on the platform.
User Story
As a user, I want to easily discover the most engaging and relevant posts, so that I can stay up-to-date and participate in discussions without sifting through irrelevant or low-quality content.
Acceptance Criteria

Introduce three tab filters on the homepage: Top, Recent, Unanswered, that allows users to sort posts based on different criteria
The top filter should be the default selection and prioritize posts based on engagement (e.g replies, likes, views) and recency using a simple heuristics algorithm similar to Reddit or other platforms. The algorithm should prioritize recent posts over more stale active posts
The recent filter should order posts by creation date
The unanswered filter should display posts with no replies, sorted by creation date
Ensure that the new filters are performant and do not impact page load or performance

Note

This idea was featured as a bounty at the ETH Denver Hackathon

This one is implemented as part of this team's submission: https://near.social/#/devgovgigs.near/widget/gigs-board.pages.Post?id=288

Hi @nearmax – You mentioned the need for "smarter" ordering of posts. Can you please review this ticket and make any changes or provide feedback to ensure this captures your intention?

@ailisp Estimates around 1-5 days of work, depending on whether the hackathon solution fully meet our acceptance criteria and production board needs. He will update the size and target end date once he get gets more information.

This is not as acute of a problem as before since we recently introduced the search and communities. We can incorporate the hackathon widget.


Fixed refresh tokens to work correctly with kubernetes storage

It was missing connectorData for RefreshToken under Kubernetes storage. Fixed this to allow refresh to work correctly without 500 server error.

Thank you for your fix. Could kindly also update the unit test at https://github.com/coreos/dex/blob/master/storage/conformance/conformance.go#L208 and add a connectorData field.

bump @moosilauke18


refactor!: remove outputEncoding param for pdf routes

BREAKING CHANGE: outputEncoding param removed from pdf/html and pdf/txt routes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
636

Relevant Lines:
636

💛  - Coveralls


Alarm is not created. Asking for ways to debug it.

Hello,
I have followed the steps provided and after creating the tag and restarting the instance I still see that alarm is not created..
Also, the Tag value does not have a time value set.
Can you please provide a way to debug it?
Thanks,
Yogesh

See issue I just opened.  Also the PR.
https://github.com/aws-samples/amazon-cloudwatch-auto-alarms/issues/35


Find out how to unify the path seperator.

The path seperator does not actually matter when binding a folder to a docker-container.


Empty Wallabag Feed shows a ⚠

Describe the bug
Using a valid subscription on a Wallabag feed that has no content shows a ⚠
To Reproduce

create a wallabag feed
read all entries
refresh in Vienna

Screenshots

Please complete the following information:

Vienna version  3.9.1 :a82691eb: (8219)
OS version: Sonoma 14.5 (23F79)

I mentioned Wallabag since I see the issue there but it may or not be related to Wallabag.

Details of feeds are logged in Activity window: that includes reasons for marking them with a ⚠

In the activity window, I see:

Why would a feed with no content raise a warning ?

As far as I remember, the intent was to warn of a stale feed.
I might change this: keep the log message but suppress the ⚠
Opinions @ViennaRSS/maintainers ?

This is my first issue, I take the chance to thank you and congratulate for the very nice piece of software 🙏
I think the log is totally fine as it may in some case be an important info to help spot issues.
Some feeds however may be empty and that's totally fine.
As a (new) user, I saw the warning and concluded that something was wrong with my config (url, auth, etc...) whereas there was nothing wrong at all.
In this case, an option could be to show an ℹ icon instead but I would not even do that. The info is "the feed is empty" which is obvious when looking at the empty list.
An option could be also to specifically show a 0 on the feed counts but that is likely not very aesthetic and again not really useful.
The ⚠ makes sense if the request fails (404, 5xx, etc...) but IMO is more confusing than helpful on empty feeds.
So removing the warning for empty feeds if the request was successful is IMO the best way to go.

Closed by Version 3.9.2


benchmark with Agents.jl

Compare runtime / memory for executing various rewriting recipes to the analogous programs constructible with https://juliadynamics.github.io/Agents.jl/stable/

A crude benchmark is there - but I'll leave this issue up as a reminder for me to adapt more examples from Agents.jl docs as well as try to encode some examples using Agents.jl that are quite natural for AlgebraicRewriting (but unnatural for Agents.jl)


can't remove all manually added users

As the tittle says.

There is a clear button on the top, that will remove all manually added accounts from the list

I've also had issues with this before. Sometimes the clear button just doesn't work.

First of all, it should be impossible to show up twice in the list. If that is possible that is a bug on it's own xD
I think what happens here is: Users that are already tracked as "automatic" cannot be removed with the clear button.

Both bugs fixed in v2.5.1 :)


Paste from elsewhere - OS X

First off, amazing work on this! I've tried a couple of the other self hosted options, but this one works the best by a long shot for me.
I however have strong passwords both on google and PTC, and there's currently no way paste into the fields, same for the coordinates.
If this is considered a bug, consider it submitted. If not, feel free to ignore! :)

Or maybe save the credentials?
Great work!!


"error": "token_not_provided"

here is my koel setup url
http://<IP_ADDRESS>/rana/koel/
email =<EMAIL_ADDRESS>password = rana123456
after successful login it take me back to login screen and it says token_not_provided .
here is code of my
I am using amazon lightsail  instance .

Please don't ignore the issue template.


Coverage

Codecov Report

Merging #38 into master will increase coverage by 8.23%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #38      +/-   ##
=======================================
+ Coverage   41.76%   50%   +8.23%
=======================================
  Files           3     3
  Lines         170   170
=======================================
+ Hits           71    85      +14
+ Misses         76    61      -15
- Partials       23    24       +1

Impacted Files
Coverage Δ

cache/cache.go
56.66% <0%> (+11.66%)
: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 f21fd22...d550e2c. Read the comment docs.


CSV file with "|" delimiter gets data offset to wrong column.

Describe the bug
Azure blob storage & Snowflake
I'm able to import the data using standard formatting in snowflake:
COPY INTO CASHIER
FROM
@my_azure_stage
Trying to replace this I get an error message: "String '2015-07-29 15:08:23.0000000' is too long and would be truncated"
when altering the columns i can see that the string has jumped to the next column and the last column is missing.
Steps to reproduce
Failing row of data:
1|2015-07-29 15:08:17.0000000|99|99|1|Extenda Support|0505|0.0000|0.0000|0|5|8388607||0|0x00000000D5EE2845|0.0000|0|0|1||2015-07-29 15:08:23.0000000|False
CSV Format:
create or replace file format lcsv
TYPE = CSV
FIELD_DELIMITER = '|'
SKIP_HEADER = 0
schema.yml
version: 2
sources:

name: dbt_user
tables:

name: tablisimo
external:
location: '@my_azure_stage'
file_format: 'lcsv'
pattern: '.* folder .* tablisimo .*' -- rich text is ruining my pattern.
auto_refresh: false # depends on your Azure setup
columns:

name: HQID
data_type: NUMBER(38)
description: 'ID number'
name: LASTUPDATED
data_type: TIMESTAMP
description: 'Lastupdated date'
name: NUMBER
data_type: VARCHAR(9)
description: 'Number'
name: STOREID
data_type: NUMBER(38)
description: 'StoreID'
name: ID
data_type: NUMBER(38)
description: 'Id'
name: NAME
data_type: VARCHAR(50)
description: 'Name'
name: PASSWORD
data_type: VARCHAR(512)
description: 'Password'
name: FLOORLIMIT
data_type: NUMBER(38)
description: 'Floor Limit'
name: RETURNLIMIT
data_type: NUMBER(38)
description: 'Return Limit'
name: CASHDRAWERNUMBER
data_type: NUMBER(38)
description: 'Cash Drawer Number'
name: SECURITYLEVEL
data_type: NUMBER(38)
description: 'Security Level'
name: PRIVILIGES
data_type: NUMBER(38)
description: 'Priviliges'
name: EMAILADDRESS
data_type: VARCHAR(255)
description: 'Email Address'
name: FAILEDLOGINATTEMPTS
data_type: NUMBER(38)
description: 'Failed Login Attempts'
name: DBTIMESTAMP
data_type: VARCHAR(50)
description: 'SQL Server RowId'
name: MAXOVERSHORTAMOUNT
data_type: NUMBER(38)
description: 'Max Over Short Amount'
name: MAXOVERSHORTPRECENT
data_type: FLOAT
description: 'Max Over Short Percent'
name: OVERSHORTLIMITTYPE
data_type: NUMBER(38)
description: 'Over Short Limit Type'
name: AUTOID
data_type: NUMBER(38)
description: 'Auto ID'
name: TELEPHONE
data_type: VARCHAR(30)
description: 'Telephone number'
name: PASSWORDCHANGEDDATE
data_type: VARCHAR(50)
description: 'Password Changed Date'
name: PASSWORDRESETFLAG
data_type: VARCHAR(50)
description: 'Password Reset Flag'

Expected results
PASSWORDCHANGEDDATE = 2015-07-29 15:08:23.0000000
PASSWORDRESETFLAG = False
Actual results
PASSWORDCHANGEDDATE =
PASSWORDRESETFLAG =  2015-07-29 15:08:23.0000000
System information
packages:

package: fishtown-analytics/dbt_utils
version: 0.6.4
package: fishtown-analytics/dbt_external_tables
version: 0.6.2

Which database are you using dbt with?

[ ] redshift
[X ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
installed version: 0.19.0
latest version: 0.19.0
Up to date!
Plugins:

bigquery: 0.19.0
mysql: <IP_ADDRESS>
mysql5: <IP_ADDRESS>
postgres: 0.19.0
redshift: 0.19.0
snowflake: 0.19.0

The operating system you're using:
Ubuntu sub system, ubuntu:latest docker
The output of python --version:
Python 3.8.5

Hey @LagerVegard, I'm not sure exactly what's gone wrong here! I copy-pasted your line of errant data, split it on the | delimiter, and got back the right number of columns (22).
Have you tried copying the create external table DDL from logs/dbt.log and running it yourself in the Snowflake console, to see if the same thing goes wrong?
The dbt-external-tables package exists to compile and execute boilerplate DDL/DML to create and update external tables, based on the table and column information included in your .yml files. It cannot actually guarantee that those DDL/DML statements will properly reflect the data in external storage; that's between you, Azure blob, and Snowflake to figure out. If you find that the package should be templating different DDL/DML, that's something we can make happen with a code change in this repo.

Looking at logs/dbt.log i see that i'm loosing a column in the definition.
- name: MAXOVERSHORTPRECENT
data_type: FLOAT
description: 'Max Over Short Percent'
create or replace external table ADF.dbt_user.table(
HQID NUMBER(38) as (nullif(value:c1,'')::NUMBER(38)),
LASTUPDATED TIMESTAMP as (nullif(value:c2,'')::TIMESTAMP),
NUMBER VARCHAR(9) as (nullif(value:c3,'')::VARCHAR(9)),
STOREID NUMBER(38) as (nullif(value:c4,'')::NUMBER(38)),
ID NUMBER(38) as (nullif(value:c5,'')::NUMBER(38)),
NAME VARCHAR(50) as (nullif(value:c6,'')::VARCHAR(50)),
PASSWORD VARCHAR(512) as (nullif(value:c7,'')::VARCHAR(512)),
FLOORLIMIT NUMBER(38) as (nullif(value:c8,'')::NUMBER(38)),
RETURNLIMIT NUMBER(38) as (nullif(value:c9,'')::NUMBER(38)),
CASHDRAWERNUMBER NUMBER(38) as (nullif(value:c10,'')::NUMBER(38)),
SECURITYLEVEL NUMBER(38) as (nullif(value:c11,'')::NUMBER(38)),
PRIVILIGES NUMBER(38) as (nullif(value:c12,'')::NUMBER(38)),
EMAILADDRESS VARCHAR(255) as (nullif(value:c13,'')::VARCHAR(255)),
FAILEDLOGINATTEMPTS NUMBER(38) as (nullif(value:c14,'')::NUMBER(38)),
DBTIMESTAMP VARCHAR(50) as (nullif(value:c15,'')::VARCHAR(50)),
MAXOVERSHORTAMOUNT NUMBER(38) as (nullif(value:c16,'')::NUMBER(38)),
right here
        OVERSHORTLIMITTYPE NUMBER(38) as (nullif(value:c17,'')::NUMBER(38)),
        AUTOID NUMBER(38) as (nullif(value:c18,'')::NUMBER(38)),
        TELEPHONE VARCHAR(30) as (nullif(value:c19,'')::VARCHAR(30)),
        PASSWORDCHANGEDDATE VARCHAR(50) as (nullif(value:c20,'')::VARCHAR(50)),
        PASSWORDRESETFLAG VARCHAR(10) as (nullif(value:c21,'')::VARCHAR(10))
)
location = @my_azure_stage

Found the issue.
name: OVERSHORTLIMITTYPE
data_type: NUMBER(38)
description: 'Over Short Limit Type'
was missing

name: OVERSHORTLIMITTYPE
data_type: NUMBER(38)
description: 'Over Short Limit Type'


Send file option in chat window

Hi dstpierre,
Thanks for such a nice implementation. I have implemented chat window on my demo application which is working fine. I want to include send file option where visitor can b able to send file to agent or agent can send file to visitor. How can i achieve that can u plz guide me on that ?
By the way, I am using asp.net web forms.
Thanks in advance

You will need to add a file upload capability onto the div.
<input type="file" id="input">
You can then capture this file through some sort of event.

I'm closing this since LCSK is changing to a more robust customer communication app.
Thank you for your interests in LCSK and I hope Parle will be ready soon so you can have a look at it.


Error installing cameradar in Kali

Hello folks,
After following the steps, and installing all the dependencies I stayed in step 6
1- git clone https://github.com/EtixLabs/cameradar.git
2- cd cameradar
3- mkdir build
4- cd build
5- cmake ..
6- make
root@kali:~/Programas/cameradar/build# cmake ..
-- retrieve current git revision SHA1 of cameradar
-- current cameradar git revision SHA1 is b61fe521615d64e234e892b6e739ca965b470500
-- current cameradar build version will be<PHONE_NUMBER>4743
-- Configuring deps.jsoncpp
-- Configuring deps.mysqlconnector
-- Configuring done
-- Generating done
-- Build files have been written to: /root/Programas/cameradar/build

root@kali:~/Programas/cameradar/build# make
[ 18%] Built target deps.jsoncpp
[ 20%] Performing configure step for 'deps.mysql_connector'
CMake Error at /root/Programas/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-configure-.cmake:16 (message):
  Command failed: 1

   '/usr/bin/cmake' '-DBOOST_ROOT=/root/Programas/cameradar/deps/boost/src/deps.boost' '-DCMAKE_INSTALL_PREFIX=/root/Programas/cameradar/deps/mysql-connector' '-DBUILD_TYPE=Release' '-DMYSQL_CXXFLAGS=-fexceptions' '/root/Programas/cameradar/deps/mysql-connector/src/deps.mysql_connector'

  See also

    /root/Programas/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-configure-*.log

deps/CMakeFiles/deps.mysql_connector.dir/build.make:106: recipe for target '../deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-configure' failed
make[2]: *** [../deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-configure] Error 1
CMakeFiles/Makefile2:124: recipe for target 'deps/CMakeFiles/deps.mysql_connector.dir/all' failed
make[1]: *** [deps/CMakeFiles/deps.mysql_connector.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2

See the error:
root@kali:~/Programas/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp# cat deps.mysql_connector-configure-err.log
CMake Error at FindMySQL.cmake:556 (message):
  Could not find "mysql.h" from searching "/usr/include/mysql
  /usr/local/include/mysql /opt/mysql/mysql/include
  /opt/mysql/mysql/include/mysql /usr/local/mysql/include
  /usr/local/mysql/include/mysql /MySQL/*/include /MySQL/*/include"
Call Stack (most recent call first):
  CMakeLists.txt:217 (INCLUDE)

Any ideia to fix the error?
Thanks in advance.

Hi @carlosrodriguesIT.
First, while I try to find what caused your issue, you should probably use the docker image to avoid having to install dependencies on your machine. You can find examples in the README.
Now, about your issue: the build steps in the README have only been tested under Ubuntu 16.04 so it might be because of a package not being in the right version.
The error that occurs with mysql-connector seems like CMake tries to find the package on your machine but doesn't.
How did you install it mysql? Do you manually find mysql.h on your machine?

I followed the quick instructions, but the error persiste, look:
root@kali:~/cameradar/deployment# ls -la
total 820
drwxr-xr-x 3 root root   4096 May 12 10:17 .
drwxr-xr-x 9 root root   4096 May 12 10:17 ..
-rwxr-xr-x 1 root root   1003 May 12 10:17 build_last_package.sh
-rw-r--r-- 1 root root 807331 May 12 10:17 cameradar_1.1.4_Release_Linux.tar.gz
drwxr-xr-x 2 root root   4096 May 12 10:19 conf
-rw-r--r-- 1 root root    512 May 12 10:17 docker-compose.yml
-rwxr-xr-x 1 root root   1040 May 12 10:17 docker-entrypoint.sh
-rw-r--r-- 1 root root    683 May 12 10:17 Dockerfile
root@kali:~/cameradar/deployment# ./build_last_package.sh
Deleting old package ...
OK!
Creating package ...
-- The C compiler identification is GNU 5.3.1
-- The CXX compiler identification is GNU 5.3.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/bin/git (found version "2.11.0")
-- retrieve current git revision SHA1 of cameradar
-- current cameradar git revision SHA1 is 0e7577ed7c10fcef6e33bae4e311ab2c4a781423
-- current cameradar build version will be<PHONE_NUMBER>2012
-- Configuring deps.jsoncpp
-- Configuring deps.mysqlconnector
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29")
-- Checking for one of the modules 'gstreamer-1.0'
-- Configuring done
-- Generating done
-- Build files have been written to: /root/cameradar/build
Scanning dependencies of target deps.jsoncpp
[  2%] Creating directories for 'deps.jsoncpp'
[  4%] Performing download step (git clone) for 'deps.jsoncpp'
-- deps.jsoncpp download command succeeded.  See also /root/cameradar/deps/jsoncpp/src/deps.jsoncpp-stamp/deps.jsoncpp-download-*.log
[  6%] No patch step for 'deps.jsoncpp'
[  9%] No update step for 'deps.jsoncpp'
[ 11%] Performing configure step for 'deps.jsoncpp'
-- deps.jsoncpp configure command succeeded.  See also /root/cameradar/deps/jsoncpp/src/deps.jsoncpp-stamp/deps.jsoncpp-configure-*.log
[ 13%] Performing build step for 'deps.jsoncpp'
-- deps.jsoncpp build command succeeded.  See also /root/cameradar/deps/jsoncpp/src/deps.jsoncpp-stamp/deps.jsoncpp-build-*.log
[ 15%] No install step for 'deps.jsoncpp'
[ 18%] Completed 'deps.jsoncpp'
[ 18%] Built target deps.jsoncpp
Scanning dependencies of target deps.mysql_connector
[ 20%] Creating directories for 'deps.mysql_connector'
[ 22%] Performing download step (download, verify and extract) for 'deps.mysql_connector'
-- deps.mysql_connector download command succeeded.  See also /root/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-download-*.log
[ 25%] No patch step for 'deps.mysql_connector'
[ 27%] No update step for 'deps.mysql_connector'
[ 29%] Performing configure step for 'deps.mysql_connector'
-- deps.mysql_connector configure command succeeded.  See also /root/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-configure-*.log
[ 31%] Performing build step for 'deps.mysql_connector'
CMake Error at /root/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-build-Release.cmake:16 (message):
  Command failed: 2

   '/usr/bin/make'

  See also

    /root/cameradar/deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-build-*.log

deps/CMakeFiles/deps.mysql_connector.dir/build.make:111: recipe for target '../deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-build' failed
make[2]: *** [../deps/mysql-connector/src/deps.mysql_connector-stamp/deps.mysql_connector-build] Error 1
CMakeFiles/Makefile2:124: recipe for target 'deps/CMakeFiles/deps.mysql_connector.dir/all' failed
make[1]: *** [deps/CMakeFiles/deps.mysql_connector.dir/all] Error 2
Makefile:149: recipe for target 'all' failed
make: *** [all] Error 2
KO!
root@kali:~/cameradar/deployment#

The instructions you followed are meant to build the image, so yeah you will have the same issue. What I meant is that there is a precompiled version of Cameradar that runs directly inside of docker, you just have to use 'docker run'.
 Check the environment variables part for more information.
tag allows you to specify a specific version for camerada. If you don't specify any tag, you will use the latest version by default (recommended)

hi i cant find cmakelist.txt
1- git clone https://github.com/EtixLabs/cameradar.git
2- cd cameradar
3- mkdir build
4- cd build
5- cmake ..
when i write this command its error like this:
moh@ubuntu:~/cameradar/build$ cmake ..
CMake Error: The source directory "/home/moh/cameradar" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI
i cant install the program.please help me.

Hi @mammad551368,
That's because you are following a very outdated documentation, from 2 years ago when Cameradar was written in C++. Please refer to the new documentation for installing and using Cameradar :)


Enabled connection to docker daemon with manual setting of docker base url for code interpreter tool. (Issue #1555)

Goal is to avoid the error: CodeInterpreterTool Error while fetching server API version.
See issue #1555 crewai.
solution code:
from crewai_tools import CodeInterpreterTool

Agent(
    ...
    tools=[CodeInterpreterTool(user_docker_base_url="<Docker Host Base Url>",
        user_dockerfile_path="<Dockerfile_path>")],
)

Disclaimer: This review was made by a crew of AI Agents.
Code Review Comment for PR #148
Overview
This PR introduces the functionality to manually set the Docker base URL for the Code Interpreter Tool, aiding macOS users who face connection issues with the Docker daemon.
Summary of Changes
Modified Files:

README.md
code_interpreter_tool.py

Detailed Analysis
1. Documentation Improvements (README.md)

Positive Aspects:

Clear and practical examples are provided to assist users in configuring the Docker host.
The inclusion of specific use cases targeting macOS users enhances relevance.

Suggestions for Improvement:

Consider providing additional context regarding scenarios in which this configuration is necessary to help users understand better.
Adding example values for the placeholder <Docker Host Base Url> would clarify the expected format.

Recommended Example Enhancement
If you encounter challenges connecting to the Docker daemon (a common occurrence for macOS users), you can manually configure the Docker host:

```python
from crewai_tools import CodeInterpreterTool

# Example configurations:
# Unix socket: "unix://var/run/docker.sock"
# TCP: "tcp://localhost:2375"
Agent(
    ...
    tools=[CodeInterpreterTool(
        user_docker_base_url="unix://var/run/docker.sock",
        user_dockerfile_path="<Dockerfile_path>"
    )],
)

### 2. Code Modifications (code_interpreter_tool.py)
- **Identified Issues**:
    - There is a logic error in the initialization of the Docker client:
    ```python
    client = docker.from_env() if self.user_docker_base_url != None else docker.DockerClient(base_url=self.user_docker_base_url)
    ```
    The logic should actually read:
    ```python
    client = docker.DockerClient(base_url=self.user_docker_base_url) if self.user_docker_base_url else docker.from_env()
    ```

    - The new parameter lacks proper type hints which could lead to misunderstandings in expected input:
    ```python
    user_docker_base_url: Optional[str] = None
    ```

    - Absence of validation for the `user_docker_base_url` format raises potential stability and usability concerns.

#### Suggested Improvements
1. **Parameter Validation and Enhanced Error Handling**:
```python
from typing import Optional
import re

class CodeInterpreterTool(BaseTool):
    user_docker_base_url: Optional[str] = None

    def _validate_docker_url(self) -> None:
        """Validate the Docker base URL format."""
        if self.user_docker_base_url:
            valid_patterns = [
                r'^unix:\/\/.*',
                r'^tcp:\/\/[\w\-\.]+(:\d+)?$'
            ]
            if not any(re.match(pattern, self.user_docker_base_url) for pattern in valid_patterns):
                raise ValueError(
                    "Invalid Docker base URL format. Expected formats: "
                    "'unix:///var/run/docker.sock' or 'tcp://localhost:2375'"
                )

Improved Error Messaging:

def _verify_docker_image(self) -> None:
    """Verify if the Docker image is available. Optionally use a user-provided Dockerfile."""
    try:
        self._validate_docker_url()
        client = self._get_docker_client()
        client.images.get(self.default_image_tag)
    except ConnectionError as e:
        raise ConnectionError(
            f"Failed to connect to Docker daemon. If using macOS, try setting "
            f"user_docker_base_url. Error: {str(e)}"
        )

Security Considerations

It’s crucial to ensure that the Docker daemon URL is secured, especially when utilizing TCP connections.
Evaluate the potential inclusion of SSL/TLS support for remote Docker connections to enhance security.

General Recommendations

Implement comprehensive unit tests covering the new Docker URL functionality.
Increase robustness by integrating error handling mechanisms for common Docker connection problems.
Add logging to track Docker connection attempts for better debugging capabilities.
Document all supported Docker URL formats within the class docstring for developer clarity.
Contemplate adding configuration validation at tool initialization to ensure correct usage of parameters.

Conclusion
Overall, the proposed changes are a positive step toward enhancing user experience and addressing connectivity issues. Nonetheless, integrating the suggested improvements will significantly bolster the code's robustness and user-friendliness.

Good Suggestion!


Separate out djvUI?

Was walking through a bunch of the DJV sources... have you ever thought about breaking djvUI out as a separate project? Looks like an interesting little UI layer!

Hi Michael, thanks for the interest! I would definitely like to separate out the libraries so they can be used by other applications, both for myself and others who might find them useful. I actually have another GitHub issue for this, so I'm going to close this one as a duplicate, but feel free to to comment on the other issue if you have any more thoughts you would like to add:
https://github.com/darbyjohnston/DJV/issues/232

Very nice! Sorry for the duplicate!

No problem at all!


Switch to build conventions

Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage remained the same at 100.0% when pulling 9909e933ee71649364e849e7878ac36636f0b7be on conventions into 5c30746f14761e0a0310fec9c5de015094efa45d on main.


my networkx version

ok

@Adebesindedayo thanks for your contribution! Could you please remove the virtual environment files from the pull request? The networkx-dev folder :)


Fixed problem with gs: url if there is a leading slash.

This was failing:
toil.importFile("gs://broad-references/hg38/v0/Homo_sapiens_assembly38.fasta.64.amb")

Jenkins, test this please.

Jenkins, test this please.


fix gf run custom arguments and gf gen dao specify config file path

不知为何gf gen dao工具一直没有把指定配置路径选项完善一下, 不是很常用吗
https://goframe.org/pages/viewpage.action?pageId=3673173 的使用方式示例
gf gen dao -p ./model -c config.yaml -g user-center -t user,user_detail,user_login
-c 一直用不了,  短命令已被 DescriptionTag 占用了  short命令找不到合适的就用了cfg
以下测试没问题
gf gen dao -p ./src  -cfg ./myconf/conf.toml
之前使用 gf run main.go --args "-www ./product debug true" 一直没法把参数传进去
经测试以下两运行方式接收到的参数一致
$ gf run main.go --args "-www ./product -debug true"
$ ./main -www ./product -debug true

Codecov Report

Merging #1879 (7ed4cae) into master (19779cd) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1879   +/-   ##
=======================================
  Coverage   75.56%   75.56%
=======================================
  Files         512      512
  Lines       46373    46373
=======================================
+ Hits        35041    35042    +1
+ Misses       9328     9325    -3
- Partials     2004     2006    +2

Flag
Coverage Δ

go-1.15-386
?

go-1.15-amd64
75.43% <ø> (-0.04%)
:arrow_down:

go-1.16-386
75.48% <ø> (+<0.01%)
:arrow_up:

go-1.16-amd64
75.47% <ø> (ø)

go-1.17-386
75.51% <ø> (+0.03%)
:arrow_up:

go-1.17-amd64
75.49% <ø> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

os/gfsnotify/gfsnotify_filefunc.go
74.02% <0.00%> (-3.90%)
:arrow_down:

os/gcron/gcron_schedule.go
67.52% <0.00%> (+0.42%)
:arrow_up:

os/gfsnotify/gfsnotify_watcher_loop.go
83.19% <0.00%> (+2.52%)
: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 19779cd...7ed4cae. Read the comment docs.


[IMPROVEMENT]

It would be nice to skip a question without solving them

Please explore the app completely first, this functionality isn't needed because you can move forward even after putting a wrong answer. @girish-07


ol.interaction.Select() ?

Hi All!
I have a few questions|problems|enhancements  with/for the ol.interaction.Select.
Problem: Multiple select interactions do not work - but I have a lot of different modules exporting layers to my main map. A few of these layers need to support selection, but only one select is possible, so this can't be implemented in the different modules.
I tried to create kind generic select mechanisms for the main map, but every solution looks a little bit complicated

Styles. I'm using one stylefunc per layer, so the layers stylefunc must also be the interaction style. The different styles for (non-)selected are all handled in my layers stylefuncs.
Problem: How to supply the layers stylefunc to the interaction?
this.selectInteraction = new ol.interaction.Select({
            layers: [this.ANIMOVERLAY.layer_particle],
            pixelTolerance:30,
            style:function(feature, resolution) {
                return this.selectInteraction.getLayer(feature).getStyleFunction()(feature, resolution)

            }.bind(this),
        })

Since the style can't be changed later the function must be supplied in the ctor, so this strange bind() cascade is required.
Idea: Use a "styler" callback function like this:
styler(feature, resolution){
return style or [style] or stylefunc
}

Every time the interactions needs to know the style styler(f,r).bind(this) is called. This would allow more flexible style functions, knowing everything the interactions knows.

Notification
How does a feature know whether it's selected or not? Currently I'm setting my own selected flag:
this.selectInteraction.on('select',function(evt){
    $.each(evt.selected, function(idx, f) {
        f.set('_selected', true, true)
    })
    $.each(evt.deselected, function(idx, f) {
        f.set('_selected', false, true)
    })
})

Is there any way to do this smoother? Maybe firing a 'un-selected' event for the feature?

Interference with map.on('click')
I'm using map.on('click') to place markers on my map. If I select a feature the marker is placed on this feature. I don't know ho to prevent this without establishing my own select mechanism inside the click-handler.
Idea:  The map.on('click')-handler could append an callback function at the end of the event chain. This callback will only be called if nobody else calls .stopPropagation().
Possible problem: There is a small delay (waiting for dblclick?) when selecting with the select interaction...
Any ideas?
Best regards
Michael

To this subject i would like to mention this post https://groups.google.com/forum/#!topic/ol3-dev/Yh7eMfcUFBI and this PR: #5279

About 2: You can check if the feature is in the collection returned by the getFeatures method of the select interaction.

That's true, but I want the feature only to know whether it's selected or not - not more.
Of course I can supply the selected collection to all style functions and/or features - but this is much more information than necessary.
I think it would be better to not let the feature now by which mechanisms it had been selected and how this mechanism works. The feature only should now the answer to "Am I selected?" Or, even better, each feature receives an event notification.

@michaelletzgus It sounds like what you are looking for is not ol.interaction.Select, but ol.Map#forEachFeatureAtPixel. This allows you to handle things the way you desire, including setting an attribute on a selected feature. To be honest, I have stopped using ol.interaction.Select because I find the forEachFeatureAtPixel approach simpler, more flexible, less overhead and 100% predictable.

@ahocevar  Thats excatly what I'm doing now, the only problem was that my on('click') handler is still using forEachFeatureAtPixel() - but for a lot of other things.
I think ol.interaction.Select is quite useless, the same feature can be implemented with a few lines of code, performing better and having more features than.
Maybe ol.interaction.Select would be more useful or easier to use and more intuitive if it fires select and unselect events on the features?

Maybe. I'll leave that to others to decide and implement. As I said elsewhere, I'm done with the Select interaction 😄.

Live is great without ol.Interaction.Select :)
Is it possible to achieve some kind of "per geometry" of "per style" filtering with forEachFeatureAtPixel?
I have a lot of moving Point features, styled by the Layers stylefunc. The style adds a Text style and two additional geometries (a heading indicator line and a trail) to the point.
Is it possible to only retrieve clicks on the point - but not on the text nor the additional geometries?
I tried to find a solution in the ol3 source - but I got lost somewhere in ol.structs.RBush.prototype.getInExtent = function(extent) in rbush.js.
My current solution is an additional distance of click check in my features event handler, this works from the point of view of the feature. But the event dispatching forEachFeatureAtPixel-loop doesn't know anything about the result of this check.
Maybe I should not use dispatchEvent() but mym own event dispatch function with an appropriate  return value...?

Echoing the frustrations about ol.Interaction.Select! With all of it's side-effects, it is a bit of a trap.


[WFLY-10254] Refactoring - preparing for upcomming MSC release.

All tests passed @jmesnil @bstansberry @stuartwdouglas could any of you merge it, please?

@pferraro Please approve.
@ropalka Please ping the relevant component lead for reviews.


@histoire/plugin-svelte: Named export 'globby' not found

Describe the bug
Followed the example config exactly, and gave the error below. I think this is caused by type: module in package.json
Reproduction
vite dev --port 3000 --open
import { globby } from 'globby';
         ^^^^^^
SyntaxError: Named export 'globby' not found. The requested module 'globby' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'globby';
const { globby } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)

System Info
System:
    OS: macOS 13.4.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 30.48 GB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.16.1 - ~/.nvm/versions/node/v18.16.1/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.5.1 - ~/.nvm/versions/node/v18.16.1/bin/npm
  Browsers:
    Chrome: 114.0.5735.133
    Safari: 16.5.1

### Used Package Manager

yarn

### Validations

- [X] Follow our [Code of Conduct](https://github.com/histoire-dev/histoire/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/histoire-dev/histoire/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://histoire.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/histoire-dev/histoire/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/histoire-dev/histoire/discussions).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

Seems its an issue with package.json for globby package. Because it is a devDependency, it gets ignored and only available for the main package histoire and not @histoire/plugin-svelte. Suggest to make it a dependency, or add proper peer dependency. Thanks.


🚨 API key found!

Description
Developers should not have direct access to API keys for sending telemetry data. It is important to store and retrieve the API key using secure methods like environment variables or configuration files. This maintains data security while enabling developers to send telemetry without accessing the keys.
Proposed Solution
Remove direct API key exposure in the code.
Utilize secure storage methods such as environment variables or configuration files.
Update code and documentation accordingly.
Alternatives Considered
...
Importance
High (?)
Here's the issue:
https://github.com/chroma-core/chroma/blob/465495d16298c27c26d81043aa2716a26b221607/chromadb/telemetry/posthog.py#L19

This is necessary and intended https://github.com/chroma-core/chroma/issues/305


Introduce three pid files for three profiles in the place of wso2carbon.pid

Have have three profiles of the server running. So there need to be three process Ids.

Three separate pid files are already created when running iot-server.sh, broker.sh and analytics.sh. Please note that broker.sh and analytics.sh which resides in $IOT_HOME/bin are just intermediate shell scripts that initiate the related startup scripts in relevant folders. Following are the individual paths for the pid files;
IoT Server Core Profile
$IOT_HOME/bin/iot-server.sh
$IOT_HOME/bin/wso2carbon.pid
Analytics Profile
$IOT_HOME/bin/analytics.sh -> $IOT_HOME/wso2/analytics/bin/wso2server.sh
$IOT_HOME/wso2/analytics/bin/wso2carbon.pid
Broker Profile
$IOT_HOME/bin/broker.sh -> $IOT_HOME/wso2/broker/bin/wso2server.sh
$IOT_HOME/wso2/broker/bin/wso2carbon.pid


ImportError: cannot import name 'json' from 'engineio'

I got the below error.

Traceback (most recent call last):
  File "/Users/cpasumarthi/codeBase/chatbot/venv/bin/rasa", line 6, in <module>
    from rasa.__main__ import main
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/rasa/__init__.py", line 9, in <module>
    from rasa.train import train
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/rasa/train.py", line 39, in <module>
    from rasa.core.agent import Agent
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/rasa/core/agent.py", line 15, in <module>
    from rasa.core.channels.channel import OutputChannel, UserMessage
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/rasa/core/channels/__init__.py", line 12, in <module>
    from rasa.core.channels.socketio import SocketIOInput
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/rasa/core/channels/socketio.py", line 10, in <module>
    from socketio import AsyncServer
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/socketio/__init__.py", line 3, in <module>
    from .client import Client
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/socketio/client.py", line 11, in <module>
    from . import packet
  File "/Users/cpasumarthi/codeBase/chatbot/venv/lib/python3.7/site-packages/socketio/packet.py", line 2, in <module>
    from engineio import json as _json
ImportError: cannot import name 'json' from 'engineio'

This error is due to an incompatible version of  python-engineio library as shown below. It worked fine after upgrading the version
ERROR: rasa 2.4.0 has requirement python-engineio<3.14,>=3.11, but you'll have python-engineio 4.2.0 which is incompatible.

Environment:
OS: Big Sur 11.4
Python: 3.7.7

Thanks for the issue, @koernerfelicia will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

Thank you for letting us know. Closing the issue as it seems to have been fixed with the correct version of engineio.


Add j2objc reflection for json and util package

Note to future releaser: BUILD files will need to be modified as part of this import.

Also, this is failing in CI:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project google-http-client: Compilation failure: Compilation failure:
[ERROR] /home/travis/build/google/google-http-java-client/google-http-client/src/main/java/com/google/api/client/json/package-info.java:[27,36] error: package com.google.j2objc.annotations does not exist
[ERROR] /home/travis/build/google/google-http-java-client/google-http-client/src/main/java/com/google/api/client/util/package-info.java:[25,36] error: package com.google.j2objc.annotations does not exist
[ERROR] /home/travis/build/google/google-http-java-client/google-http-client/src/main/java/com/google/api/client/json/package-info.java:[24,1] error: cannot find symbol
[ERROR]  class ReflectionSupport
[ERROR] /home/travis/build/google/google-http-java-client/google-http-client/src/main/java/com/google/api/client/util/package-info.java:[22,1] error: cannot find symbol

It looks like the google-http-client artifact's pom.xml also needs the dependency added.

PTAL, updated the dependency in pom files

Libraries that uses google-http-java-client with J2ObjC enabled can pass in a --strip-reflection flag to improve build and startup performance for iOS apps


No feedback from flutter run when targeting iOS hardware, until "list index out of range"

My iPhone is plugged in, and I ran flutter run. I don't see anything in response, while the tool is running xcodebuild and the other steps.
Then, after many seconds, I see this:
~/Code/flutter/examples/flutter_gallery[master*] $ flutter run
Traceback (most recent call last):
  File "/tmp/fruitstrap_d83d5bc53967baa0ee18626ba87b6254b2ab5418.py", line 35, in run_command
    lldb.target.Launch(lldb.SBLaunchInfo(shlex.split(args[1] and args[1] or '--enable-checked-mode')), error)
IndexError: list index out of range
^C

Can we display some sort of spinner/hint that the tool is working in the background?
Is the error important?

cc @cbracken who was looking at this with me.

The missing log output may be fixed by https://github.com/flutter/flutter/pull/6720

Fixed by #7794


Extra symbol

Hi,
please could you help me with extra symbols? I downloaded Font Awesome and generated fonts from 61440 to 63537. Now, I put instead of the lv_font_symbol_20 and I want use symbols form my extra fonts, but I don't know, how. I wanted change the defines as SYMBOL_AUDIO etc... But there should be something wrong in my definitions. I cannot find my symbols.
Please, could you help me, what numbers should I put into this _SYMBOL_VALUE3(EF,A0,EE) and why ?
Thank you very much

Maybe useful php font_conv_for_lists.php [1]

We use GitHub issues for development related discussions.
Please use the forum to ask questions or suggest enhancements.
It's possible to sign in to the forum with your GitHub account... you don't need to make a separate account.
:clipboard: Reference

https://github.com/littlevgl/lv_utils#list-parameter-specific-utility

Hi, thank you, but I still cannot understand this:
Unicode: f2c5 (is it in hexadecimal?) and now this:
#define LV_SYMBOL_THERMOMETER_EMPTY     "\xef\x8b\x8b"
Why 0xEF 0x8B 0x8B ?
And another question, when I downloaded version 5, then it is ok using unicode from version 5, right?
Thank you

Please read this code part,
  // https://fontawesome.com/v4.7.0/icons/
  // label: unicode
  $unicodes = array(
    "THERMOMETER_EMPTY" => "f2cb",
    "TINT             " => "f043",
    "BALANCE_SCALE    " => "f24e",
    "BARS             " => "f0c9",
    "MICROCHIP        " => "f2db"
  );

And another question, when I downloaded version 5, then it is ok using unicode from version 5, right?

I use v4.7.0. I don't experience fontawesome v5.
:clipboard: Reference

https://github.com/littlevgl/lv_utils/blob/master/font_conv_for_lists.php#L7-L15

Oh thanks. I understand now. Solved my issue :-)

@zavovi Please note: for future questions like this, use the forum.


Alert on loki data for error rates in concourse envs

Write an alert against the loki envs that will tell us when concourse is in a bad way. Should be straightforward to write a simple rate expression that does this.

https://github.com/mitodl/grafana-alerts/blob/main/loki-rules/concourse.yaml#L5-L11


Fixed the header on the Home screen

Description
Moved the Sign Out button and add Add a Task to the Home screen. Also fixed the large title issue.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x ] Bug fix (non-breaking change which fixes an issue)

Change Status

[ x] Complete, but not tested (may need new tests)

Checklist

[x ] There are no merge conflicts

looks good!


Fix for repeated fields in OpenAPI spec generation

Codecov Report

:exclamation: No coverage uploaded for pull request head (openapi_repeated_fields@ce7046d).

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 689119b...ce7046d. Read the comment docs.


Seed creation is failing

How to categorize this issue?

/area control-plane
/kind bug
What happened:
While creating a seed, it never gets healthy with the error waiting for required extension to get ready.  This https://github.com/gardener/gardener/pull/7928 PR introduced a check which checks for required extension to get ready for seed before any other things are deployed ref.
But there are provider-extension which need etcd crds ref to present to get healthy.
This creates a deadlock as provider-extension waits for ectd crds to be present to get healthy, whereas etcds crds deployment step is after the check of required extension to get healthy.
Because of above case seed never gets a chance to get healthy.
What you expected to happen:
Seed creation to succeed successfully.
How to reproduce it (as minimally and precisely as possible):

make kind-extension-up
make gardener-extension-up

check for seed status, as it never gets healthy and complains that required extensions are not ready.
Anything else we need to know?:
Environment:

Gardener version: 716d42380275fd13344a5f12466bb824e018d1a9
Kubernetes version (use kubectl version):
Cloud provider or hardware configuration:
Others:

I would recommend splitting the etcd-bootstraping step ref and deploying etcd crds separately.
/cc @timuthy WDYT about the above approach if that is fine I can open PR for it.

/assign


Message loss in spider feed

From here https://github.com/scrapinghub/distributed-frontera/issues/24#issuecomment-181386301

Another issue I noticed recently is that my DW keeps on pushing to all partitions although I have no spider running. When I start up my spiders now, they wait until the DW has pushed a new batch (although he pushed multiple times before that). This means that after running the DW for a while without there being any spider running depletes the queue until there is nothing left to crawl. I have to add new seeds (not the same seed URLs, since multiples get dropped) for the spiders to start again and the DW to push new requests again.

@lljrsr This is mostly done because there is no clear way of controlling consumption rate on producer side in ZeroMQ. Moreover the contents of queue on ZeroMQ side and the way it decides of high water mark, and starts dropping messages is implicit. Client application has no way to track any of this.
We could partially solve this problem, by disabling new batch generation if there are no heartbeats from spiders. Currently, spiders are sending offsets once per every get_next_requests call. So we could try disabling new batch generation until DBW gets first offset. At the moment, all partitions are marked ready after DBW start.

Yes. I think that would be a good idea.
It may increase the startup time for spiders but it would make frontera easier to use because this issue would no longer be there.


[wip] Use swift tablegen instead of llvm tablegen

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

NOTE I am going to improve the commit message in the last commit. I just gotta run to an appointment and wanted to run a smoke test.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test


Github Action to deploy the helm chat to gh-pages

Helm chart is hosted in github pages. Provide a gh action that can build the helm chart and deploy it to gh-pages

Implemented


Broken build?

I'm new to node but I wrote a simple test script then it fails when I called open():
var Aria2 = require('..')
var aria2Options = {host: 'localhost', port: 6800, secure: false}
var aria2 = new Aria2(aria2Options)

aria2.open();

I put the file in the example directory and run node test.js. The result is below:
events.js:0
(function (exports, require, module, __filename, __dirname) { // Copyright Joy
^
RangeError: Maximum call stack size exceeded

However when I use npm package, it seems still has the issue #8 unfixed.
UPDATE:
If I use the npm package(ver 0.0.6) and manually patched commit https://github.com/sonnyp/aria2.js/commit/ee9a18bac020274606f71fd25f91ab199a693cb6, the script works fine.
My aria2 version is 1.18.8.

I published version 1.0.0 on npm. Can you please try with that?

After npm update, it's the current npm list output:
├─┬<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   └─┬<EMAIL_ADDRESS>│     ├──<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>
With the same script (only change is var Aira2 = require('aria2')), it's still the same output:
events.js:0
(function (exports, require, module, __filename, __dirname) { // Copyright Joy
^

what is your node version?
Can you give me the complete error?

The complete error message is:
events.js:0
(function (exports, require, module, __filename, __dirname) { // Copyright Joy
^
RangeError: Maximum call stack size exceeded

node --version gives:
v0.10.37

Guess it's not the latest version, but follow the installation it gives something like:
## Confirming "precise" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_4.x/dists/precise/Release'

## Your distribution, identified as "precise", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support

My linux is Ubuntu 12.04, so might be the version issue?

no no the version is fine

@fengye how do you start ari2c?

I think it's rpc enabled, I greped the ps output:
ps -ef|grep aria2

which gives:
feng_ye   9625 14586  0 23:39 pts/1    00:00:00 grep --color=auto aria2
feng_ye  18899     1  3 Mar12 ?        7-12:27:41 aria2c --enable-rpc --rpc-listen-all=true --rpc-allow-origin-all

reproduced :) gonna send a fix

Okay, please install new version 1.0.1 and try again, should be fixed now; sorry

Great! It works now. Thanks for the quick fix.
However the aria2.send() method seems broken. I'll start another issue.

@fengye yes please do, I made changes a while ago and broke some stuff, I hope to fix them all.


500: INTERNAL_SERVER_ERROR

I have tried several solutions, but they have not worked. How can I solve this?

Try this
https://github.com/memochou1993/gpt-ai-assistant/issues/295#issuecomment-1741986240


fix(footer): add allow list for origins for which the fetching of footer links works

The fetching of footer links is limited to some baloise domains. To avoid unnecessary requests on other domains,  the allow list for origins was introduced.

:rocket: Welcome to Baloise ChatOps based GitOps Bot :tada:
- If you want to enable preview environments for this PullRequest, comment with `/preview`.
- If you want to disable the preview environment for this PR, comment with `/undeploy`.
- If you need help or want to see the docs, comment with `/help`.

Make sure to refresh this page after submitting a command.
Preview environments can be redeployed automatically if you enable the webhook for updates to the source branch. :new:

Have fun building awesome apps! :hammer:  :whale2:  :truck:  :ship:


use with nvimtree

Thank you for creating such an amazing nvim plugin.
I have discovered an issue when using it together with the nvim-tree plugin.
The issue is that when nvimTree is opened on the left or right side, the renderer does not function properly.
I have resolved the issue by writing an autocmd.

Please be aware that my code may not be perfect. maybe need to refactoring

Since many users are likely to use nvim-tree, could you add this as a default feature?
I think it might be necessary to add a feature in intro.nvim that re-renders every time a split window is opened.
If you prefer, I can create a PR.
autocmd("BufUnload", {
  pattern = "NvimTree_*",
  callback = function()
    local win_id_list = vim.api.nvim_list_wins()
    for _, win_id in ipairs(win_id_list) do
      local filetype = vim.bo[vim.api.nvim_win_get_buf(win_id)].filetype
      if filetype == "intro" then
        vim.schedule(function()
          vim.api.nvim_set_current_win(win_id)
          vim.cmd "Refresh"
        end)
      end
    end
  end,
})

autocmd("FileType", {
  pattern = "NvimTree",
  callback = function()
    local win_id_list = vim.api.nvim_list_wins()
    local intro_win_id = nil
    local nvim_tree_win_id = nil

    for _, win_id in ipairs(win_id_list) do
      local filetype = vim.bo[vim.api.nvim_win_get_buf(win_id)].filetype
      if filetype == "intro" then
        intro_win_id = win_id
      elseif filetype == "NvimTree" then
        nvim_tree_win_id = win_id
      end
    end

    if nvim_tree_win_id ~= nil and intro_win_id ~= nil then
      vim.schedule(function()
        vim.api.nvim_set_current_win(intro_win_id)
        vim.cmd [[
          Refresh
          NvimTreeFocus
        ]]
      end)
    end
  end,
})

as-is
to -be

That's intentional. Because it was meant to be used with stuff like telescope & noice(basically things that use semi-transparent floating windows). I actually planned it to act like a background image when you have other stuff on the screen.
I am planning on rewriting the entire plugin(cause it's not particularly good at what it does and I basically did the thing no prior knowledge). So, I will add that as an option there.
Also, there is a BUG that may cause neovim to crash if some other window(e.g. Lazy.nvim) opens instead of the normal window in neovim during startup. So, if you plan on using the plugin you should know about this(though it is a rare thing).
Thanks for trying the plugin(even though it may be a bit unstable in certain cases).


Migrating backplane-cli login & logout

What type of PR is this?
feature
What this PR does / Why we need it?
This PR is for migrating backplane login/logout
Which Jira/Github issue(s) does this PR fix?
OSD-14683
Pre-checks (if applicable)

[ Yes] Ran unit tests locally
[ Yes] Validated the changes in a cluster
[ ] Included documentation changes with PR

/test coverage

/test all

/test coverage

/retest

/test coverage

/retest

Closing this PR due conflicts with branched that merged , due to this tests are failing creating new one


Update Braintree creds for test

← #4614 — #4598 →
I need to add a custom field to our Braintree sandbox account as part of https://github.com/gratipay/gratipay.com/pull/4613, but I don't have access to do that. In the interest of time, here is a PR that rerecords all of our Braintree fixture against an account that I have access to.

[ ] change base to master

Verbose log in https://github.com/gratipay/gratipay.com/issues/4615.

Hmm ... probs w/ TestPages?

Alright, so what's it doing there?

Two of the tests are trying to add calls to the cassette.
test_on_the_fence_can_browse
test_new_participant_can_browse

Back from #4615 ... redid rerecord w/ blanket rerecord on TestPages. Was 0a7213ee3ad755f3e0401c2a065edb7017dc6452.

Rebased on master post-#4614 and base changed, waiting for Travis ...

🚨  Self-merge license 🚨


Update Kubernetes dependencies/CI to 1.27

Kubernetes 1.27 is released https://kubernetes.io/blog/2023/04/11/kubernetes-v1-27-release/ let's make use of it in cephcsi

[ ]  Make Kubernetes E2E test mandatory in CI Run
[ ] Update Mergify rules to consider tests on kube 1.27
[ ] go dependency update
[ ] Readme update

Fix for subtask 2: https://github.com/ceph/ceph-csi/pull/3744

Fix for subtask 3: https://github.com/ceph/ceph-csi/pull/3748

Fix for subtask 4: https://github.com/ceph/ceph-csi/pull/3777

closes-with: https://github.com/ceph/ceph-csi/pull/3752


Replace cubeb_device_collection interface.

In discussion with @kinetiknz, he stated the extending-array-via-mallocing-header+data should be revisited at some point.

If/when you're doing this, there is another problem that we need to think about, is that the lifetime of the device themselves is weird, and we're doing all sorts of weird index mapping in gecko.
It would be good to have stable indexes or devices.

@padenot I've opened Issue #298 to track the problem you've raised. I have patches to improve things.

Fixed by #309


feat(Nightlight): add Nightlight theme

Nightlight Theme
Nightlight is a relaxing and simple theme. Inspired by Nightlight's color pallet.

Can someone please merge this request? It has been 3 months


Upgrade 7.0.1 to 8.1.0 configuration issue

After upgrading from Butterknife 7.0.1 to 8.1.0, I get the following issue when the app starts:
Process: com.couchsurfing.mobile.android, PID: 7976
java.lang.RuntimeException: Unable to create application com.couchsurfing.mobile.CsApp: java.lang.IllegalStateException: Module adapter for class com.couchsurfing.mobile.c could not be loaded. Please ensure that code generation was run for this module.
    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4715)
    at android.app.ActivityThread.-wrap1(ActivityThread.java)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:148)
    at android.app.ActivityThread.main(ActivityThread.java:5422)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Caused by: java.lang.IllegalStateException: Module adapter for class com.couchsurfing.mobile.c could not be loaded. Please ensure that code generation was run for this module.
    at dagger.internal.h.a(FailoverLoader.java:45)
    at dagger.internal.h.a(FailoverLoader.java:40)
    at dagger.internal.q.b(Memoizer.java:58)
    at dagger.internal.g.a(FailoverLoader.java:57)
    at dagger.internal.s.a(Modules.java:43)
    at dagger.d.a(ObjectGraph.java:174)
    at dagger.c.b(ObjectGraph.java:129)
    at com.couchsurfing.mobile.CsApp.d(CsApp.java:289)
    at com.couchsurfing.mobile.CsApp.onCreate(CsApp.java:103)
    at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1013)
    at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4712)
    at android.app.ActivityThread.-wrap1(ActivityThread.java)
    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1405)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:148)
    at android.app.ActivityThread.main(ActivityThread.java:5422)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

Which is from my knowledge a dagger setup issue... However if I add in my proguard.cfg the following:
-keepnames class * { @butterknife.* <methods>; }
-keepnames class * { @butterknife.* <fields>; }

(in the consumer proguard those are set to keepclasseswithmembernames). the issue is fixed...
Well, I have no clue why it look like a dagger configuration issue and after reading the documentation of keepnames vs keepclasseswithmembernames I don't see why keepclasseswithmembernames would be an issue.
I was wondering if anyone can shed some light on what's going on?
build.gradle:
...
  compile 'com.squareup.dagger:dagger:1.2.5'
  provided 'com.squareup.dagger:dagger-compiler:1.2.5'

  compile 'com.jakewharton:butterknife:8.1.0'
  apt 'com.jakewharton:butterknife-compiler:8.1.0'
...

Well I can say that for one, the consumer proguard rules definitely don't guard against obfuscation. As far as I can tell it's impossible to do this with ProGuard so we don't even try.

What is com.couchsurfing.mobile.c? My guess is that you're not preventing enough things from being renamed for Dagger, and by doing so for Butter Knife you magically fix Dagger as well.

This is where it's confusing. com.couchsurfing.mobile.c is a dagger module:
@Module(includes = {
    AppModule.PlatformModule.class, DataModule.class
},
    injects = {
        CsApp.class, AccountAuthenticator.class, PlatformReceiver.class,
        PlatformProcessorService.class, InstanceIDService.class, UploadAnalyticsService.class
    },
    library = true)
public class AppModule {

  private final CsApp application;

  public AppModule(final CsApp application) {
    this.application = application;
  }

  @Provides
  @Singleton
  CsApp provideSurfingApplication() {
    return application;
  }
 ...

My proguard dagger related
# Dagger
-keep class * extends dagger.internal.Binding
-keep class * extends dagger.internal.ModuleAdapter
-keep class * extends dagger.internal.StaticInjection
-dontwarn dagger.internal.codegen.**
-dontwarn com.squareup.javawriter.**

I really don't see how the @butterknife.* <methods>; and @butterknife.* <fields>;  are related to this module..

Are you able to reproduce this in a small sample? Otherwise I'm not sure what action to take here.

Any update?


'alarmo' calls async_track_state_change instead of async_track_state_change_event

Alarmo Version
v1.10.0
HA Version
2024.5.b0
Bug description
Beta testing 2024.5.b0 produces this error:
Detected that custom integration 'alarmo' calls async_track_state_change instead of async_track_state_change_event which is deprecated and will be removed in Home Assistant 2025.5 at custom_components/alarmo/sensors.py, line 175: self._state_listener = async_track_state_change(, please report it to the author of the 'alarmo' custom integration
Steps to reproduce
Install HA core 2024.5.b0
Relevant log output
No response

It's happening on latest release too (2024.5.1)

Actually I think this is causing an issue that alarm cannot be armed, the workaround that I found is to restart HA and it works again. This is the only thing that I see on logs.

This might help to fix it:
https://developers.home-assistant.io/blog/2024/04/13/deprecate_async_track_state_change/

This may be causing instability due to using the incorrect async call. Thread safety errors can lead to crashes in 2024.5.0 and higher:
https://community.home-assistant.io/t/2024-5-tracking-down-instability-issues-caused-by-integrations/724441
I know for my part, all attempts to update to 2024.5.2 fail and result in a rollback.

@tomlut Thanks for reporting this, I will take care of this change in the next update.
@Omnipius Could you please explain what incorrect call, safety errors and ccrashes you are referring to?
As far as I am aware, the warning reported here is about a deprecated function which will no longer work in a year from now.
If you experience issues with Alarmo when updating HA to 2024.5, I don't think this is related to the deprecated function call. Please create a bug report if you think something is wrong in Alarmo.

For me there is no instability. Just the error logged at start up.

This is issue is resolved with the new v1.10.1 release.


proposal: all custom defined basic types should support composite literals

Often, I change the kinds of some custom types in my custom packages between non-basic types and basic types, back and forth. For example, one custom type declaration:
type MyType struct {
	a, b uint32
}

There are many local variables of this type are used in other packages.
These variables are declared like v := MyType{}
Later, I changed my mind to declare the type as
type MyType uint64

Now, all the variable uses are broken, for the error invalid type for composite literal.
However, if basic types also support composite literals. Those uses will be still legal.
And the proposal will make Go syntax more consistent.

Large changes to the language won't happen in Go1, so labeling as Go2.
Note that both struct and basic types support var v T. If you used that, you wouldn't run into this problem.
The only cases where var v T and v := T{} would differ is in slices and maps, since the former would give nil and the latter would give empty, but non-nil.

Dup of #22647 and/or #19966, so closing this one.

@bradfitz It is not the same. The other two are proposed to take addresses of other values.
However, this proposal is to allow composite literals for basic types.

I agree this is not the same, but I don't see the need for this to be a language change.
If the type was exported, you would not be able to change type since that would be a breaking change.
If the type was not exported, it seems that this a problem better suited for a static analysis tool to do the cleanup for you and not a language level change.


[Addition]:

Hotspot b58 Addresses
115dJE4VwPW1KY8oECXjfFpjAuzFte1KZNMAtAcNQVxqJMrGFNr
112DrUhcEjyze9EN9LSMrncdoZmU34vznNZ9TyAGeokfRhUNrnjU
11HSpwHYKTuUgNtWvzeoVtgWk34ZS2TGPKJDDr3xR4fQYKpeBtP
1184oTWZ92V3dcGNTwSB5QKFPRZPjTuLVMnU7rDWZFyjDVeCaHG
118ys15Y7c7hCnKFoxSnsGcsJLX6PqWHyXdx3hB9s9r4kQnGEXg
11BUb8Mfe8zFqod1ZrydDTKf2GgxtdepAuBcqTjwJmpKj2j9CwH
11D7jYqZTjxYd2paQVnjUUU1ewFgLuF6LJjaCYA55Vq9r7w45R4
11C2DrUKJJHQFYKTtbEVitz7yDavoihE9MibrDq1Ui9fwZc7Z6H
11EuBnKoQKGogJLafSvGWeDZFPi8hWBXJu6818m5cG3vLstmm79
Discord Handle
malder
Reason(s)
This group of hotspots only witness each other, despite there being 403 other online hotspots within 25 KM
They are exclusivey Deeper hotpots which fail to interact with the non-Deeper hotspots around them.

We have taken into account this addition request in the next iteration of the denylist. Some or all of the Hotspots listed may be added to the denylist. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


django 3.x breaks import

Description
Getting ModuleNotFoundError: No module named 'django.utils.six' when django >= 3.x.
Possibly pin django to a lower version or remove/replace the import.
Steps to reproduce

Install dpaste and see that django 3.x is installed
Try to run the django server
Get the import error

Expected result
ModuleNotFoundError: No module named 'django.utils.six'

⏱ Estimated Level of Effort (LOE): unestimated
Developer Checklist

[ ] Estimated LOE
[ ] Tests written (if not include explanation)
[ ] CI tests pass
[ ] Deployed/tested in non-production environment
[ ] Approved for deployment by project owner
[ ] Deployed to production

Could you provide a full traceback? I'm running dpaste.org with Django 3.0 myself.

Interesting- I’m not sure I have the trace back handy unfortunately. I did find this in the release notes for 3.0 https://docs.djangoproject.com/en/3.0/releases/3.0/#removed-private-python-2-compatibility-apis

I forgot about this. I'm pretty sure you run into this with your setup https://github.com/mozilla/django-csp/issues/129
In the Docker setup I currently overcome it with installing the latest master branch. https://github.com/bartTC/dpaste/blob/master/Dockerfile#L46-L48
In your particular setup its probably best to stay on Django 2.2 and once Mozilla pushed out a new release it will basically fix itself and you can upgrade to 3.0


Support rostopic and topic_tools Like Tools in Cyber

Now that apollo is primarily using cyber for communications, there are some basic diagnostic tools missing. ROS, has rostopic and topic_tools. There is cyber_monitor, but it is not as general purpose and does not interoperate with shell.
A simple cyber_echo that takes arbitrary messages without a pb description would be very useful. It seems that protobuf description gets transmitted, but the cyber::Reader needs the explicit type.
Just supporting google::protobuf::Any or google::protobuf::Message in reader would be a good start. Then, users can write these tools easier.
Some of the nice features in shell is echoing a topic, then piping it grep and saving as plain text to a file. The bandwidth feature and info would be nice from rostopic. The relay tool is useful from topic_tools.

@Fla3inH0tCheet0s Thanks for your suggestion. The tools you suggested are already in our plan, and soon you will see related tools like cyber_channel.

Closing this issue currently. Thank you so much for your suggestion @Fla3inH0tCheet0s
We will let you know once we have released the tools.


Update Introducing-Turtlesim.rst

Command sudo apt install ros--rqt-* did not work for foxy on Ubuntu 20.04 --- used sudo apt install ros--rqt instead.

The originally recommended command installs all rqt plugins:

sudo apt install ros--rqt-*

The Foxy specific command this PR recommends only install rqt but not any plugins. So as is this patch isn't helpful.
When you say the original command didn't work for you did you substitute <distro> with foxy when invoking it?

I did... response is:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ros-foxy-rqt-*
Em qua., 10 de jun. de 2020 às 23:28, Dirk Thomas<EMAIL_ADDRESS>escreveu:

The originally recommended command installs all rqt plugins:
sudo apt install ros--rqt-*
The Foxy specific command this PR recommends only install rqt but not any
plugins. So as is this patch isn't helpful.
When you say the original command didn't work for you did you substitute
 with foxy when invoking it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ros2/ros2_documentation/pull/757#issuecomment-642383924,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALO2UJXK7WZFXXYOWRHMM5LRWBFPLANCNFSM4N3AP67Q
.

--
Hebert Azevedo Sá

There are many packages matching ros-foxy-rqt-*: see http://repo.ros2.org/status_page/foxy_default.html?q=ros-foxy-rqt-
Maybe you can post the output of apt search ros-foxy-rqt*.

I find them all. The problem is that somehow the * is not working to install all at once.
The output of apt search ros-foxy-rqt* is:
Sorting... Done
Full Text Search... Done
ros-foxy-rqt/focal,now 1.0.6-1focal.20200604.045736 amd64 [installed]
  rqt is a Qt-based framework for GUI development for ROS.

ros-foxy-rqt-action/focal,now 1.0.1-1focal.20200604.045919 amd64 [installed]
  rqt_action provides a feature to introspect all available ROS action types.

ros-foxy-rqt-common-plugins/focal,now 1.0.0-1focal.20200604.050911 amd64 [installed]
  rqt_common_plugins metapackage provides ROS backend graphical tools suite that can be used on/off of robot runtime.

ros-foxy-rqt-console/focal,now 1.1.1-1focal.20200604.045036 amd64 [installed,automatic]
  rqt_console provides a GUI plugin for displaying and filtering ROS messages.

ros-foxy-rqt-graph/focal,now 1.0.4-1focal.20200604.045103 amd64 [installed,automatic]
  rqt_graph provides a GUI plugin for visualizing the ROS computation graph.

ros-foxy-rqt-gui/focal,now 1.0.6-1focal.20200604.044448 amd64 [installed,automatic]
  rqt_gui provides the main to start an instance of the ROS integrated graphical user interface provided by qt_gui.

ros-foxy-rqt-gui-cpp/focal,now 1.0.6-1focal.20200604.045419 amd64 [installed]
  rqt_gui_cpp enables GUI plugins to use the C++ client library for ROS.

ros-foxy-rqt-gui-cpp-dbgsym/focal 1.0.6-1focal.20200604.045419 amd64
  debug symbols for ros-foxy-rqt-gui-cpp

ros-foxy-rqt-gui-py/focal,now 1.0.6-1focal.20200604.044736 amd64 [installed,automatic]
  rqt_gui_py enables GUI plugins to use the Python client library for ROS.

ros-foxy-rqt-image-view/focal,now 1.0.4-1focal.20200604.050321 amd64 [installed,automatic]
  rqt_image_view provides a GUI plugin for displaying images using image_transport.

ros-foxy-rqt-image-view-dbgsym/focal 1.0.4-1focal.20200604.050321 amd64
  debug symbols for ros-foxy-rqt-image-view

ros-foxy-rqt-msg/focal,now 1.0.2-1focal.20200604.045829 amd64 [installed,automatic]
  A Python GUI plugin for introspecting available ROS message types.

ros-foxy-rqt-plot/focal,now 1.0.8-1focal.20200604.045002 amd64 [installed,automatic]
  rqt_plot provides a GUI plugin visualizing numeric values in a 2D plot using different plotting backends.

ros-foxy-rqt-publisher/focal,now 1.1.0-1focal.20200604.045016 amd64 [installed,automatic]
  rqt_publisher provides a GUI plugin for publishing arbitrary messages with fixed or computed field values.

ros-foxy-rqt-py-common/focal,now 1.0.6-1focal.20200604.044507 amd64 [installed,automatic]
  rqt_py_common provides common functionality for rqt plugins written in Python.

ros-foxy-rqt-py-common-dbgsym/focal 1.0.6-1focal.20200604.044507 amd64
  debug symbols for ros-foxy-rqt-py-common

ros-foxy-rqt-py-console/focal,now 1.0.0-1focal.20200604.045029 amd64 [installed,automatic]
  rqt_py_console is a Python GUI plugin providing an interactive Python console.

ros-foxy-rqt-reconfigure/focal,now 1.0.5-1focal.20200604.045836 amd64 [installed,automatic]
  This rqt plugin provides a way to view and edit parameters on nodes.

ros-foxy-rqt-robot-steering/focal 1.0.0-1focal.20200604.045010 amd64
  rqt_robot_steering provides a GUI plugin for steering a robot using Twist messages.

ros-foxy-rqt-service-caller/focal,now 1.0.3-1focal.20200604.045023 amd64 [installed,automatic]
  rqt_service_caller provides a GUI plugin for calling arbitrary services.

ros-foxy-rqt-shell/focal,now 1.0.0-1focal.20200604.044959 amd64 [installed,automatic]
  rqt_shell is a Python GUI plugin providing an interactive shell.

ros-foxy-rqt-srv/focal,now 1.0.1-1focal.20200604.045922 amd64 [installed,automatic]
  A Python GUI plugin for introspecting available ROS message types.

ros-foxy-rqt-top/focal,now 1.0.0-1focal.20200604.045045 amd64 [installed]
  RQT plugin for monitoring ROS processes.

ros-foxy-rqt-topic/focal,now 1.1.0-1focal.20200604.044927 amd64 [installed]
  rqt_topic provides a GUI plugin for displaying debug information about ROS topics including publishers, subscribers, publishing rate, and ROS Messages.

look at that...
https://askubuntu.com/questions/1233459/apt-install-method-in-ubuntu-20-04-does-not-work

I think this works:
sudo apt install ~nros-foxy-rqt.*

https://askubuntu.com/questions/1233459/apt-install-method-in-ubuntu-20-04-does-not-work

That seems to be the change in Ubuntu 20.04.
Please update the existing command to: sudo apt install ros-<distro>-rqt* (with the dash before the star to also explicitly install rqt itself).
Instead of adding a custom section for Foxy I would suggest to make this a new section for Ubuntu 20.04 (and newer) with: sudo apt install ~nros-foxy-rqt*

Closing in favor of #758.


Issue setting maxcpus with v.2.0.2021115

I just updated to the newest version but I'm having issues with the cpu settings. I've been running the previous versions for a few months now (thanks for your hard work on this!) without issue on a machine with 6 cores + Docker, but now I'm getting errors such as:
Error executing process > 'bwa '
Caused by:
Process requirement exceed available CPUs -- req: 8; avail: 6
I've tried to override the params.maxcpus & params.medcpus and even hard coding -t or --threads to 6 throughout the Cecret.nf file for each process, but so far the error persists and the message starting the run displays:
The maximum number of CPUS used in this workflow is 8
Any ideas on what I should try next?

@keckstrom
I think this issue may be coming up more.
Cecret used to calculate cpu usage automatically depending on what system that it was launched from, but this was causing havoc with those that used cloud computer devices, so it was changed to a fixed value. This is still how Cecret can still operate if you have cloned the github repository and don't use the -profile option.
Something like the following (you can adjust the paths to what is on your system)
nextflow run Cecret.nf -c configs/singularity.config

How have you "overriding" the params.maxcpus and params.medcpus?
Something to the effect of
nextflow run UPHL-BioNGS/Cecret -profile singularity --maxcpus 6

should adjust the maxcpus for your needs.

I was trying to set it in the config file before, but didn't think anything of it with the change to using profiles instead. This works perfectly, thanks!

I'm glad it's now working for you!

I added in some documentation about this issue so that others don't run into problems in the future.
Thank you for brining this to my attention!


Closing all workers

In cases where there are lots of workers stop_workers is slow. This appears to be caused by closing each worker in a for-loop.
As the common case where multiple workers are submitted to be stopped is just submitting all workers to stop, it would be good to special case this and pass JOB_IDS_SESSION_ALL to DRMAA. This would bypass the need for the loop.
There are a few options:

Detect if all workers were passed in (easy, maybe a little hacky)
Make the worker_ids parameter optional and the default value equal to all workers (easy, straightforward)
Integrate this into close (easy, hacky without 1 or 2)

Thoughts?

Should add we need to take PR ( https://github.com/dask/dask-drmaa/pull/85 ) into account. So this would affect scale_down in a similar way.

cc @d-v-b


Not reading npm scripts.

I am running lint-stage as a pre-commit hook of husky.
My .huskyrc:
{
"hooks": {
 "pre-commit": "lint-staged"
}
}

My .lintstagedrc:
{
  "*": "npm run-script format"
}

On making a git commit the following lintstaged error occurs:
⚠ Running tasks...
  ❯ Running tasks for *
    ✖ npm run-script format [FAILED]

I have verified that the script format exists and is working fine.

Hello, please add the --debug option to the pre-commit hook that invokes lint-staged and post the output here:
{
    "hooks": {
       "pre-commit": "lint-staged --debug"
    }
}

` git commit -m "lint"
husky > pre-commit (node v10.19.0)
✔ Preparing...
⚠ Running tasks...
❯ Running tasks for *
✖ npm run-script format [FAILED]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up...
✖ npm run-script format:
[error] No parser could be inferred for file: .lintstagedrc
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>format: prettier --write "src/**/*.{js,jsx}" "/home/rachit/Projects/EOSIS-Hack/.lintstagedrc"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>format script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rachit/.npm/_logs/2020-05-08T06_36_35_219Z-debug.log

<EMAIL_ADDRESS>format /home/rachit/Projects/EOSIS-Hack
prettier --write "src/**/*.{js,jsx}" "/home/rachit/Projects/EOSIS-Hack/.lintstagedrc"

src/index.js 56ms
husky > pre-commit hook failed (add --no-verify to bypass)
rachit@rachit-Lenovo-Y520-15IKBN:~/Projects/EOSIS-Hack$ git commit -m "lint"
husky > pre-commit (node v10.19.0)
lint-staged:bin Running<EMAIL_ADDRESS>+0ms
lint-staged:bin Options parsed from command-line: { allowEmpty: false,
concurrent: true,
configPath: undefined,
debug: true,
maxArgLength: 65536,
stash: true,
quiet: false,
relative: false,
shell: false,
verbose: false } +2ms
lint-staged Loading config using cosmiconfig +0ms
lint-staged Successfully loaded config from /home/rachit/Projects/EOSIS-Hack/.lintstagedrc:
lint-staged { '': 'npm run-script format' } +74ms
lint-staged:cfg Validating config +0ms
Running lint-staged with the following config:
{
'': 'npm run-script format'
}
lint-staged Unset GIT_LITERAL_PATHSPECS (was undefined) +3ms
lint-staged:run Running all linter scripts +0ms
lint-staged:resolveGitRepo Resolving git repo from /home/rachit/Projects/EOSIS-Hack +0ms
lint-staged:resolveGitRepo Unset GIT_DIR (was undefined) +0ms
lint-staged:git Running git command [ 'rev-parse', '--show-toplevel' ] +0ms
lint-staged:resolveGitRepo Resolved git directory to be /home/rachit/Projects/EOSIS-Hack +45ms
lint-staged:resolveGitRepo Resolved git config directory to be /home/rachit/Projects/EOSIS-Hack/.git +0ms
lint-staged:git Running git command [ 'log', '-1' ] +45ms
lint-staged:git Running git command [ 'diff', '--staged', '--diff-filter=ACMR', '--name-only', '-z' ] +20ms
lint-staged:run Loaded list of staged files in git:
lint-staged:run [ '.lintstagedrc' ] +81ms
lint-staged:chunkFiles Resolved an argument string length of 46 characters from 1 files +0ms
lint-staged:chunkFiles Creating 1 chunks for maxArgLength of 65536 +0ms
lint-staged:gen-tasks Generating linter tasks +0ms
lint-staged:gen-tasks Generated task:
lint-staged:gen-tasks { pattern: '*',
lint-staged:gen-tasks   commands: 'npm run-script format',
lint-staged:gen-tasks   fileList: [ '/home/rachit/Projects/EOSIS-Hack/.lintstagedrc' ] } +2ms
lint-staged:make-cmd-tasks Creating listr tasks for commands 'npm run-script format' +0ms
lint-staged:task cmd: npm +0ms
lint-staged:task args: [ 'run-script', 'format' ] +0ms
lint-staged:task execaOptions: { preferLocal: true, reject: false, shell: false } +0ms
lint-staged:chunkFiles Resolved an argument string length of 46 characters from 1 files +5ms
lint-staged:chunkFiles Creating 1 chunks for maxArgLength of 65536 +0ms
❯ Preparing...
lint-staged:git Backing up original state... +0ms
lint-staged:git Getting partially staged files... +0ms
lint-staged:git Running git command [ 'status', '--porcelain' ] +26ms
lint-staged:git Found partially staged files: [] +19ms
lint-staged:git Backing up merge state... +1ms
lint-staged:file Reading file /home/rachit/Projects/EOSIS-Hack/.git/MERGE_HEAD +0ms
lint-staged:file Reading file /home/rachit/Projects/EOSIS-Hack/.git/MERGE_MODE +0ms
lint-staged:file Reading file /home/rachit/Projects/EOSIS-Hack/.git/MERGE_MSG +0ms
lint-staged:file File /home/rachit/Projects/EOSIS-Hack/.git/MERGE_HEAD doesn't exist, ignoring... +0ms
lint-staged:file File /home/rachit/Projects/EOSIS-Hack/.git/MERGE_MODE doesn't exist, ignoring... +1ms
lint-staged:file File /home/rachit/Projects/EOSIS-Hack/.git/MERGE_MSG doesn't exist, ignoring... +0ms
lint-staged:git Done backing up merge state! +3ms
lint-staged:git Getting deleted files... +29ms
lint-staged:git Running git command [ 'ls-files', '--deleted' ] +51ms
lint-staged:git Found deleted files: [] +144ms
lint-staged:git Running git command [ 'stash', 'create' ] +144ms
lint-staged:git Running git command [ 'stash',
'store',
'--quiet',
'--message',
'lint-staged automatic backup',
'6adcb68779c143907af13a69549a007873d78c10' ] +42ms
lint-staged:git Done backing up original state! +69ms
✔ Preparing...
❯ Running tasks...
❯ Running tasks for *
❯ npm run-script format
✖ npm run-script format [FAILED]
✖ npm run-script format [FAILED]
✔ Running tasks...
❯ Applying modifications...
❯ Reverting to original state because of errors...
lint-staged:git Restoring original state... +4s
lint-staged:git Running git command [ 'reset', '--hard', 'HEAD' ] +4s
lint-staged:git Running git command [ 'stash', 'list' ] +259ms
lint-staged:git Running git command [ 'stash', 'apply', '--quiet', '--index', 'stash@{0}' ] +15ms
lint-staged:git Restoring merge state... +324ms
lint-staged:git Done restoring merge state! +0ms
lint-staged:file Removing file /home/rachit/Projects/EOSIS-Hack/.git/lint-staged_unstaged.patch +5s
lint-staged:file File /home/rachit/Projects/EOSIS-Hack/.git/lint-staged_unstaged.patch doesn't exist, ignoring... +0ms
lint-staged:git Done restoring original state! +1ms
✔ Reverting to original state because of errors...
❯ Cleaning up...
lint-staged:git Dropping backup stash... +1ms
lint-staged:git Running git command [ 'stash', 'list' ] +51ms
lint-staged:git Running git command [ 'stash', 'drop', '--quiet', 'stash@{0}' ] +19ms
lint-staged:git Done dropping backup stash! +57ms
✔ Cleaning up...
✖ npm run-script format:
[error] No parser could be inferred for file: .lintstagedrc
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR<EMAIL_ADDRESS>format: prettier --write "src/**/*.{js,jsx}" "/home/rachit/Projects/EOSIS-Hack/.lintstagedrc"
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>format script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rachit/.npm/_logs/2020-05-08T06_37_09_829Z-debug.log

<EMAIL_ADDRESS>format /home/rachit/Projects/EOSIS-Hack
prettier --write "src/**/*.{js,jsx}" "/home/rachit/Projects/EOSIS-Hack/.lintstagedrc"

src/index.js 59ms
husky > pre-commit hook failed (add --no-verify to bypass)`
Here is the output. Also when I changed the "" in my lintstage config to  "**/.+(js|jsx|css|less|scss|ts|tsx|md)" , then its working fine.

So, you're trying to commit the .lintstagedrc file, but your linter cannot detect a parser for it.
I would either add an explicit file extension, or the just commit the file with --no-verify if that's the exact name you need.

Alternative, you could limit your lintstaged glob to match only supported files:
current config:
{
  '*': 'npm run-script format'
}

since the script seems to be using prettier, probably best to limit to the file extensions you actually want to lint, for example:
{
  '*.{js,jsx,json,md}': 'npm run-script format'
}

ok. The limiting file extension is working fine. Thank you.


Suggestion for new sample app

Hi,
I am struggling to get the following architecture up and running and would love to see a sample that describes how to do it.

Angular SPA front end, communicates to a (self-hosted) webapi (both SPA and WebApi share the same native app id)
User login is controlled by adal.js on angular front end.
WebApi receives the bearer token from the SPA api calls
WebApi uses the on-behalf of flow to get a new token to call a downstream API

Would love to know if this scenario is feasible, and worth pursuing as a sample app.
Thanks.

+1
This sample doesn't really work, it's too confusing.  Please create some new sample SPA auth apps.

This sample has been archived.
The newer one can be found at: https://github.com/Azure-Samples/active-directory-javascript-graphapi-v2


Release Google.Analytics.Data.V1Beta version 1.0.0-beta03

Changes in this release:

Commit 391b953:

feat: add kind field which is used to distinguish between response types
feat: add potentially_thresholded_requests_per_hour field to PropertyQuota

Created release for Google.Analytics.Data.V1Beta-1.0.0-beta03


ParMesh global indices

This PR adds new member functons in ParMesh for getting global indices for vertices, edges, faces, or elements. The global indices are meaningless for ParMesh, and their definition is therefore arbitrary. The particular implementation chosen is based on the corresponding ParFiniteElementSpace using lowest-order finite elements in H1 (vertices), Nedelec space (edges), Raviart-Thomas space (faces in 3D), or L2 (elements). Unit tests are also added.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1882
@dylan-copeland
@v-dobrev
@psocratis + @vladotomov
12/09/20
01/19/21
⌛due 01/26/21

Merged in next for testing...

Merged in next for testing...

LGTM

LGTM

Re-merged in next.


Update plugin for Unreal Engine 4.11

I'm pushing this change into the generator today.  I'm closing this request, but the change will make its way into Nightly by tomorrow, and it'll be in master by next week.


每日优鲜电子商务有限公司 + https://www.missfresh.cn/

For English only, other languages we will close it directly.
Please answer these questions before submitting your issue. Thanks!
Which version of Sharding-Sphere do you using?
Expected behavior
Actual behavior
Reason analyze
Steps to reproduce the behavior
Please provide the reproduce example codes (such as a github link).

it is already register in https://github.com/sharding-sphere/sharding-sphere/issues/234


Restructure io and tests modules and add test data

Further adds support for resolving #55.
Changes proposed in this pull request:

Rename asgardpy.io.io to asgardpy.io.input_dl3
Add asgardpy.io.io_dl4 for reading from DL4 dataset files, as serialized by Gammapy, and perform other common functions to support DL4 to DL5 analysis process.

For the addition of test data, the following is done,

Let the CI and the main pytests check for the presence of gammapy-data, and download it if is not the case. This requires consistent dependency on the stable gammapy and current asgardpy versions. This resolves the first part of #118
Have zipped data stored in the package (as defined in here) to add to the gammapy-data to run tests for asgardpy. This resolves the first part of  #117
Start developing pytest fixtures and start testing asgardpy functionalities with the test_data markup. For this the tests module is shifted inside asgardpy main module, and we will start creating tests for each module.

Overall, this will resolve the first parts of  #55


Add Selection To Next Find Match does not work with regex search

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.90
OS Version: Windows_NT x64 10.0.19045

Steps to Reproduce:

Make a new temporary file with this as the contents:

001
002
003

Enter search with Ctrl+F and enable regex mode, then put \d{3} as the pattern and select the next match until 001 is selected
Press Ctrl+D or run Add Selection To Next Find Match from the commands menu manually

Current behaviour:

Nothing happens

Expected result:

There is now a multi-cursor selection - one selecting 001 and another selecting 002

Note: This works as expected when the goal is to select all regex occurrences - Ctrl+Shift+L works fine in that case, but Ctrl+D seems to only work with non-regex selections.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.90.2. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!