issues installing on windows

[x] I read the conda-forge documentation and could not find the solution for my problem there.

When installing on windows I get
UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Steps to reproduce
conda create -n test_env python=3.8 --y
conda activate test_env
conda install -c conda-forge explainerdashboard

Full output below
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: \
Found conflicts! Looking for incompatible packages.
This can take several minutes.  Press CTRL-C to abort.|
failed

UnsatisfiableError: The following specifications were found to be incompatible with each other:

Output in format: Requested package -> Available versions

Details about  conda and system ( conda info ):
$ conda info

     active environment : test_env
    active env location : C:\Users\131416\AppData\Local\Continuum\anaconda3\envs\test_env
            shell level : 2
       user config file : C:\Users\131416\.condarc
 populated config files : C:\Users\131416\.condarc
          conda version : 4.9.2
    conda-build version : 3.18.11
         python version : 3.7.7.final.0
       virtual packages : __cuda=10.2=0
                          __win=0=0
                          __archspec=1=x86_64
       base environment : C:\Users\131416\AppData\Local\Continuum\anaconda3  (writable)
           channel URLs : https://repo.anaconda.com/pkgs/main/win-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/win-64
                          https://repo.anaconda.com/pkgs/r/noarch
                          https://repo.anaconda.com/pkgs/msys2/win-64
                          https://repo.anaconda.com/pkgs/msys2/noarch
          package cache : C:\Users\131416\AppData\Local\Continuum\anaconda3\pkgs
                          C:\Users\131416\.conda\pkgs
                          C:\Users\131416\AppData\Local\conda\conda\pkgs
       envs directories : C:\Users\131416\AppData\Local\Continuum\anaconda3\envs
                          C:\Users\131416\.conda\envs
                          C:\Users\131416\AppData\Local\conda\conda\envs
               platform : win-64
             user-agent : conda/4.9.2 requests/2.24.0 CPython/3.7.7 Windows/10 Windows/10.0.18362
          administrator : False
             netrc file : None
           offline mode : False

Thanks @wolfv for his comments (copied from gitter to below)
It comes from dtreeviz which requires xgboost
CONDA_SUBDIR=win-64 mamba create -n abcdefg python=3.8 explainerdashboard -c conda-forge --dry-run
CONDA_SUBDIR=win-64 mamba repoquery depends explainerdashboards -c conda-forge
CONDA_SUBDIR=win-64 mamba repoquery whoneeds py-xgboost -c conda-forge

guess we can close this now?


API Limitations may Render this Unusable in Production

Been following the code extensively on this repo and spent a really long time on V1 of this repo. The basic flaw, in my opinion, of the current V2 implementation is that you are doing everything on the server for basic e-commerce operations. The problem is that every service has API limitations, which generally are calculated based on a request origin. When you hit an API on a client, the request origin is obviously different for each user, so if say your API limit is 60 per client, you will be fine (unless a specific user abuses the service). However, if you hit the API on the server, the request origin will be the same for every single user, which means that for something like the cart, you will quickly hit API limits on many production stores, as the limit will be shared by ALL users (the request origin will be the same for everyone, as the API is hit from the server). I hope the above this makes sense. Honestly, something like the cart should be done on the client, with a library like useSwr (as per V1), and other e-commerce operations can be done on the server (with new App folder). The notion of All or Nothing will likely fail in production, especially for Cart. There will be alot of bugs. I don't see why doing the cart on the client is not the default, as V1 works very well, except for a few slight issues with race conditions, which can be fixed. I think the new App directory is great, but it has specific use cases.

Thanks for pointing this out. Does V1 still work if I dig through the commit history? I'd prefer is cart were kept client side

Yes, V1 still works fine and is proven in production settings. Will it always work? Who knows, but I just don't see Vercel getting rid of the Page router anytime soon, if ever, simply because the amount of apps built on Page far exceeds App, and may for a long time. In V1 the cart is done on the client with useSwr library, and so I think the scalability is much, much better. Personally, I don't see what the benefit of App router is for things like cart (app is useful for other e-commerce features, though), and so I don't see why they refactored the cart, other than prove that App folder works.

Are you sure about this? Seems very broken if it's so. However, in the docs I found that the cart mutations from the Storefront API have no rate limiting
https://shopify.dev/docs/api/usage/rate-limits
https://shopify.dev/docs/api/storefront/2022-04/mutations/cartLinesAdd
so it should be okay right? Can any devs speak to this?

@dannyyu92 Sorry, I am not familiar with shopify API rate limitations. But, I know every other API I've used in e-commerce has rate limits based on the client. I was speaking about the issue, in general. Maybe this won't apply to Shopify, I don't know. And, in general, one of the flaws with RSC is precisely this: API rate limits, because the client is the same across all requests. Developers of these "sample" repos don't take this into consideration, b/c they are not working in real production setting with many users.
In terms of Shopify, they specifically abandoned RSC (react server components) completely in favor of Remix, as they determined that  RSC was not viable in production for Shopify. So Shopify itself won't use RSC, but Vercel is recommending RSC for Shopify? It just doesn't make sense. What do Vercel devs know about Shopify that Shopify's own devs don't know? I'd be interested in seeing someone run this NextJS repo in actual production in a high traffic store.
Anyway, I don't see any benefit whatsoever of doing Cart  queries/mutations on the server vs client. Doing at the client level (like in V1) will be faster and more scaleable, though there are issues with client, as well. There are certainly many benefts of using RSC for product pages, and the e-commerce content in general, but not for user specific actions, like cart, order history (not even developed yet here) I don't see what the benefit is at all.

Although I agree with @osseonews thinking, the BuyerIp header is what Shopify tells us to use to handle rate limits if using server requests:
https://shopify.dev/docs/api/usage/authentication#optional-ip-header
I think we should implement that header into this repo!

Appreciate you bringing this conversation up, @osseonews.
As with many decisions in development, there is usually no universally "right" or "wrong" answer. As engineers, we assess the needs of the application, the constraints in which we need to work within, and pick the best path forward after we evaluate, experiment, and weight the pros and cons of any scenario.
As you mention, some APIs do have rate limits, which would be an important factor to consider in designing your application. In this particular use case, we use Shopify, and more specifically the Storefront API, which does not have a rate limit. Because of this, it makes doing the API communication on the server for this particular template / starter kit a good choice. A different provider with different constraints may yield a different decision or implementation.


Make the dashboard filter bar ignore case

The new repository filter bar implemented in 1.1 is really great but it would be really handy if this bar filtered repos by ignoring case. Right now it seems that you need to match the exact casing on your repositories names if you want a match.

@appleboy maybe you can do this.

@donnex @lunny I will take it.

https://try.gitea.io/appleboy?q=xd I think this bar filtered repos by ignoring case.

I will do this, my fix also fixes my other bug #1205 .

I have opened PR #1207


bitmap_union_int cause 'be' node hang

When I use bitmap_union_int() to replace count(distinct ) for a test, I found that it would cause be nodes hang. So, how can I slove this problem?
ErrMsg:
> 1064 - there is no scanNode Backend
SQL：
select bitmap_union_int(id) from table1;
The type of id is int, and rows of table1 is about 70 million, and the model of table is Agg.
Looking forward to reply! thx!

Yes, all Backend are down.
There is nothing output in the be.WARAING, and this is be.INFO of one of Backends:

I had tried to trun up the exec_mem_limit to 8GB, but it doesn't work.
This is be.out of one of Backends:

@kangkaisen This is fe.warn.log:

@XShun Hi，What's the last commit of your code?
Please give me the create table sql and some raw data(dozens of line is enough)，thanks.
I will try reproducing and solving this issue.

@XShun Hi. How do you load the data to table1?
All bitmap_union_int query will make BE down,  or only select bitmap_union_int(id) from table1 will make BE down ;

@kangkaisen Hi, I just saw your message. I also met the 'be could not start' problem yesterday, so I pulled the latest code this morning and rebuilt it. I load data to table1 through load label ... with broker ... , and the source data is on the HDFS. All bitmap_union_int query will make BE down.
Here are the create table sql and some rows:
CREATE TABLE table1 (   k1 date NOT NULL COMMENT "key1",   k2 varchar(20) NOT NULL COMMENT "key2",   k3 varchar(100) NOT NULL COMMENT "key3",   k4 int(11) NOT NULL COMMENT "key4",   id int(11) NOT NULL COMMENT "id",   flag bigint(20) SUM NOT NULL DEFAULT "1" COMMENT "flag" ) ENGINE=OLAP AGGREGATE KEY(k1, k2, k3, k4, id) COMMENT "OLAP" DISTRIBUTED BY HASH(k1) BUCKETS 6 PROPERTIES ( "storage_type" = "COLUMN" );
Rows:
2018-01-01,主键二,主键三,10000001,1000001,1 2018-01-02,主键二,主键三,10000002,1000002,1 2018-01-03,主键二,主键三,10000001,1000003,2
The last column is used to calculate count(1).
THX!

@XShun I just tried reproducing this issue, but bitmap_union_int work well.
So I want to be confirm again,  If you only load dozens of line raw data to table1, the select bitmap_union_int(id) from table1 will make BE down?

@kangkaisen I just insert into table2 10 rows from table1, the structure of table2 is the
same to  table1. When use bitmap_union_int function, it made BE down. Then I tried the other three bitmap functions, TO_BITMAP and BITMAP_COUNT functions worked well, but BITMAP_UNION function also made BE down.

@kangkaisen I just insert into table2 10 rows from table1, the structure of table2 is the
same to table1. When use bitmap_union_int function, it made BE down. Then I tried the other three bitmap functions, TO_BITMAP and BITMAP_COUNT functions worked well, but BITMAP_UNION function also made BE down.

@XShun
I have tried your case, and be works fine. Can you give more detail about your test? Your Query? And you can create a table with only one column id, then you retry your query on it to see if BE will crash

@imay Only one column id also occurred the problem. Maybe the problem caused by my BE environment, I will rebuild Doris cluster for a try. THX!

@imay Only one column id also occurred the problem. Maybe the problem caused by my BE environment, I will rebuild Doris cluster for a try. THX!

@XShun  Hi, If this issue still exist. please generate the core dump file and show me this bt fullstack.

@imay Only one column id also occurred the problem. Maybe the problem caused by my BE environment, I will rebuild Doris cluster for a try. THX!

@XShun Hi, If this issue still exist. please generate the core dump file and show me this bt fullstack.

OK

@imay Only one column id also occurred the problem. Maybe the problem caused by my BE environment, I will rebuild Doris cluster for a try. THX!

@XShun Hi, If this issue still exist. please generate the core dump file and show me this bt fullstack.

@kangkaisen OK


Feature: il8n nav styles

Straight forward set of updates to add styles to the new language selector and consolidate other react-select elements:

Styles/icon for nav language selector
Set styles for all other react select styles (non dark)
Update styles for search bar

Other: add draw error styles to polygons, and fix bug allowing user to save areas that is too large when editing. Achieved by abstracting the area check to a helper and using more liberally within both DrawControl and AreasManage components.

Thanks buddy. Well noticed on the border 😎 . Couldn't see it on my screen.


[BUG] v0.2.2 pip install error

0.2.2 cannot be installed via pip:
ERROR: Command errored out with exit status 1:
     command: /home/user/PycharmProjects/columbus/venv3.8/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-ea6fq8dy/dash-uploader/setup.py'"'"'; __file__='"'"'/tmp/pip-install-ea6fq8dy/dash-uploader/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-install-ea6fq8dy/dash-uploader/pip-egg-info
         cwd: /tmp/pip-install-ea6fq8dy/dash-uploader/
    Complete output (5 lines):
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-install-ea6fq8dy/dash-uploader/setup.py", line 8, in <module>
        with open('docs/README-PyPi.md', encoding='utf-8') as f:
    FileNotFoundError: [Errno 2] No such file or directory: 'docs/README-PyPi.md'
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

it seems the README-PyPi.md is missing from the package

I have the same issue.
A workaround is cloning the repository and running python setup.py install
This same setup.py is the one that refers to the 'docs/README-PyPi.md' which triggers the error.

Thanks for reporting! I will fix it when I get back on my computer. The 0.2.0 version is identical to 0.2 2. and should be working with pip. The only difference in 0.2.1  and 0.2.2. is that I included documentation for PyPi, and those needed version bumps (can not update readme on PyPi without changing the package version. How convenient..)

Fixed in v. 0.2.3 (https://github.com/np-8/dash-uploader/commit/029aa557db2b068f2f545f3f7687144a944c12cb). The docs/README-PyPi.md was missing from the MANIFEST.in.


fix: lower log level for message on initialization

Codecov Report

Merging #57 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #57   +/-   ##
=======================================
  Coverage   98.76%   98.76%
=======================================
  Files           7        7
  Lines          81       81
  Branches        7        7
=======================================
  Hits           80       80
  Misses          1        1

Impacted Files
Coverage Δ

lib/index.js
97.22% <100%> (ø)
: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 9a6f728...143351e. Read the comment docs.


Impossible to read KMZ file

GeoPandas 1.0+ is not able to read KMZ files with pyogrio's engine, when setting engine=fiona works:
With fiona:
gpd.read_file(
    "AOI_kmz.kmz", driver="KMZ", layer="General Information", engine="fiona"
)
>>>   Name  ...                                           geometry
>>> 0   03  ...  MULTIPOLYGON Z (((-72.31143 -36.56225 0, -72.5...
>>> [1 rows x 13 columns]

With pyogrio:
gpd.read_file(
    "AOI_kmz.kmz", driver="KMZ", layer="General Information"
)
>>>   pyogrio.errors.DataSourceError: 'AOI_kmz.kmz' not recognized as a supported file format. It might help to specify the correct driver explicitly by prefixing the file path with '<DRIVER>:', e.g. 'CSV:path'.

Here is the file:
AOI_kmz.zip

Versions:
geopandas.__version__
'1.0.1'
pyogrio.__version__
'0.9.0'
fiona.__version__
'1.9.6'

Hi, how did you install geopandas and pyogrio? In my installation from conda-forge, the snippet above works. Can you also show thew output of pyogrio.list_drivers()?
import pyogrio

pyogrio.list_drivers()

The install is done via pip in a Docker (without conda) on Debian 11
The drivers are:
{'PCIDSK': 'rw', 'PDS4': 'rw', 'VICAR': 'rw', 'PDF': 'rw', 'MBTiles': 'rw', 'EEDA': 'r', 'OGCAPI': 'r', 'ESRI Shapefile': 'rw', 'MapInfo File': 'rw', 'UK .NTF': 'r', 'LVBAG': 'r', 'OGR_SDTS': 'r', 'S57': 'rw', 'DGN': 'rw', 'OGR_VRT': 'r', 'Memory': 'rw', 'CSV': 'rw', 'GML': 'rw', 'GPX': 'rw', 'KML': 'rw', 'GeoJSON': 'rw', 'GeoJSONSeq': 'rw', 'ESRIJSON': 'r', 'TopoJSON': 'r', 'OGR_GMT': 'rw', 'GPKG': 'rw', 'SQLite': 'rw', 'WAsP': 'rw', 'OpenFileGDB': 'rw', 'DXF': 'rw', 'FlatGeobuf': 'rw', 'Geoconcept': 'rw', 'GeoRSS': 'rw', 'VFK': 'r', 'PGDUMP': 'rw', 'OSM': 'r', 'GPSBabel': 'rw', 'OGR_PDS': 'r', 'WFS': 'r', 'OAPIF': 'r', 'EDIGEO': 'r', 'SVG': 'r', 'Idrisi': 'r', 'ODS': 'rw', 'XLSX': 'rw', 'Elasticsearch': 'rw', 'Carto': 'rw', 'AmigoCloud': 'rw', 'SXF': 'r', 'Selafin': 'rw', 'JML': 'rw', 'PLSCENES': 'r', 'CSW': 'r', 'VDV': 'rw', 'MVT': 'rw', 'NGW': 'rw', 'MapML': 'rw', 'GTFS': 'r', 'PMTiles': 'rw', 'JSONFG': 'rw', 'TIGER': 'r', 'AVCBin': 'r', 'AVCE00': 'r', 'HTTP': 'r'}

KML are read fine, only KMZ fail

I think that the reason is that the PyPI wheels contain the KML driver while the conda-forge contain LIBKML driver.

Is there a workaround to replicate the conda behaviour natively with pypi?

You can prepend the filename with "/vsizip/" to use the virtual filesystem feature of GDAL.
I wonder if there is something wrong with the test file you uploaded... because for another .kmz the above works, but not for your test file.

This file has been part of the test suite for years and worked :'(
I have other KMZ that fails too, so maybe there is an issue inside that is weird?

This file has been part of the test suite for years and worked :'(

Hmm... indeed, I can open it without problems in e.g. QGIS, so apparently the "KML" driver doesn't only limit the support to uncompressed .kml files but also to a subset of them... so it seems you'll really need the "LIBKML" driver.


Null-checks using mixed index

Currently Titan doesn't use a mixed index for null-checks.
gremlin> g = TitanFactory.open("conf/titan-cassandra-es.properties")
==>titangraph[cassandrathrift:[<IP_ADDRESS>]]
gremlin> GraphOfTheGodsFactory.load(g)
==>null
gremlin> g.V().has("age")
18:21:19 WARN  com.thinkaurelius.titan.graphdb.transaction.StandardTitanTx  - Query requires iterating over all vertices [(age <> null)]. For better performance, use indexes
==>v[1024]
==>v[2048]
==>v[1536]
==>v[1792]
==>v[1280]
==>v[256]

However, it's possible using a direct index query:
gremlin> g.indexQuery("vertices", "v.age:*").vertices()*.getElement()
==>v[1536]
==>v[256]
==>v[1280]
==>v[1024]
==>v[1792]
==>v[2048]

I guess the same query syntax could be used for .has("property"). .hasNot("property") seems to be trickier, I haven't found a solution for it yet.

As an implementation note, it seems that on an elasticsearch index _exists_:v.age is faster than v.age:*.


Fetch URLs Remotely?

What does it mean and how does it work?

@liquidx What type of input does the project expect?
Is this JSON or some CSV structure?

I've also been curious about this. It looks like it's expecting json, based on the code I've been able to parse, but my Objective-C isn't good enough to tell you what that json object should look like...

+1
@liquidx can you at least chime in to tell us if this feature even works?

I don't know objective c  but I looked at https://github.com/liquidx/webviewscreensaver/tree/master/WebViewScreenSaver and it appears that it wants JSON array so...
I've tried JSON off an AWS box with format like this:
[
{
"url": "http://s.codepen.io/z3vin/debug/bdqwyv",
"duration": 10
},
{
"url": "http://s.codepen.io/z3vin/debug/YwqvLR",
"duration": 10
}
]
Doesn't work :(

Yea, I tried the same thing without any success. Either this doesn't work at all or the format is not obvious.

I ended up with my own workaround. For my case, I just wanted to loop through youtube/vimeo videos at random. So I built an app for it and I just point webviewscreensaver to my app. Here's the repository: https://github.com/WattyRev/screen-saver

Nice solution 👍🏻 @WattyRev

After looking at @WattyRev and along with my quest to practice and learn more Python I decided try and build a "as simple as possible" similar workaround using Python and this is what I got (https://github.com/moisesber/fun_random_videos). Works for me so it might work for other people out there :)

Hasn't been working since 9adb30d3fe518a8c8471c02f145b4942e55e389b .
Converted the examples list to this format for testing.
Fix is now available in v2.4


[GLUTEN-6995][Core] Limit soft affinity duplicate reading detection max cache items

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
Fixes: #6995
How was this patch tested?
UT.

This patch doesn't fix the performance problem for SoftAffinityListener, the Spark Events still can be discarded, which may cause user problem if they also use Listeners. We need a comment to explain this problem so that users can know the possible problems with this configuration when using it. BTW, maybe it's a better choice to change it to false by default, and users can turn it on as needed.

This patch doesn't fix the performance problem for SoftAffinityListener, the Spark Events still can be discarded, which may cause user problem if they also use Listeners. We need a comment to explain this problem so that users can know the possible problems with this configuration when using it. BTW, maybe it's a better choice to change it to false by default, and users can turn it on as needed.

Do you mean is the SoftAffinityListener cause of the slowness, I don't observe this, can you help tp share how this is repro in your env?

Do you mean is the SoftAffinityListener cause of the slowness, I don't observe this, can you help tp share how this is repro in your env?

This is how I reproduced the problem locally.

Start spark-sql with --conf spark.hadoop.parquet.page.size=1024 --conf spark.hadoop.parquet.block.size=2048 --conf spark.sql.files.maxPartitionBytes=2048
Then, run below sqls.

create table test(a string) using parquet;
create table test1(a string) using parquet;
insert into test values(0); // make sure there is 10000 values in it
insert into test1 select /*+ REPARTITION(10000) */ * from test;

finally, restart spark-sql with SoftAffinity and run bellow sql

select count(*) from test1;

Do you mean is the SoftAffinityListener cause of the slowness, I don't observe this, can you help tp share how this is repro in your env?

This is how I reproduced the problem locally.

Start spark-sql with --conf spark.hadoop.parquet.page.size=1024 --conf spark.hadoop.parquet.block.size=2048 --conf spark.sql.files.maxPartitionBytes=2048
Then, run below sqls.

create table test(a string) using parquet;
create table test1(a string) using parquet;
insert into test values(0); // make sure there is 10000 values in it
insert into test1 select /*+ REPARTITION(10000) */ * from test;

finally, restart spark-sql with SoftAffinity and run bellow sql

select count(*) from test1;

From above I actually can't repro the issue. I think maybe this is because of the hardware differences, but with more partitions, we actually observe the latency increasing. From the code, there are only the cache get / put operations in the event handling logic. I thought the memory pressure (GC) is more like the cause.
10K values

120k values

From above I actually can't repro the issue. I think maybe this is because of the hardware differences, but with more partitions, we actually observe the latency increasing.

Did you final get 10000+ FilePartitions for sql or only have one partition?

From above I actually can't repro the issue. I think maybe this is because of the hardware differences, but with more partitions, we actually observe the latency increasing.

Did you final get 10000+ FilePartitions for sql or only have one partition?

6k+ partitions for 10K values, and 60k+ partitions for 120k values.

From above I actually can't repro the issue. I think maybe this is because of the hardware differences, but with more partitions, we actually observe the latency increasing.

Did you final get 10000+ FilePartitions for sql or only have one partition?

6k+ partitions for 10K values, and 60k+ partitions for 120k values.

Greate, could you try 30 sqls in one Application to check if you can reproduce?

From above I actually can't repro the issue. I think maybe this is because of the hardware differences, but with more partitions, we actually observe the latency increasing.

Did you final get 10000+ FilePartitions for sql or only have one partition?

6k+ partitions for 10K values, and 60k+ partitions for 120k values.

Greate, could you try 30 sqls in one Application to check if you can reproduce?

OOM happens with 120K values, but there is no event dropped logs.

OOM is not related, even SA is disable, it still happens.

OOM happens with 120K values, but there is no event dropped logs.

Hm, perhaps it is related to hardware performance. I tried ./bin/spark-sql --master local[192] with the default the gluten configs and above sqls, the problem can be stably reproduced in our environment.

BTW, maybe it's a better choice to change it to false by default, and users can turn it on as needed.

Since this pr has already closed the duplicate reading detection by default, It's ok to me now.


Docs

I wrote an init command example for the Postgres backend in the Overview doc, and a link for the Postgres site in README.
I didn't edit the Configuration doc because the database section contains technical information that I don't know about, I didn't know what to write in the db_path section, and I don't know if there are any Per-Database Options for Postgres databases.
I signed the CLA.

In which way is your PR different from #324 ?

I don't remember if it was necessary. It solved the problem I was having at
http://stackoverflow.com/questions/33769116/how-to-use-cayley-with-a-postgres-backend.
Back then init didn't create the necessary tables, I don't know if they
changed something at cayley or libpq since then. As an opinion, I think
that referencing the libpq godocs is nice, because it took me a while to
discover libpq starting from the cayley docs.
On Wed, Feb 17, 2016 at 8:22 PM, Markus Mahlberg<EMAIL_ADDRESS>wrote:

In which way is your PR different from #324
https://github.com/google/cayley/pull/324 ?
—
Reply to this email directly or view it on GitHub
https://github.com/google/cayley/pull/341#issuecomment-185433617.

@marcusmonteiro Thanks so much for the PR, we added it to the other one (specifically the important bit about where dbpath comes from).


Generate SDK contract wrappers

Is your feature request related to a problem? Please describe.
I'm using the neotest package to test my smart contract and noticed the need to manually configure the hash and method names. This process is error-prone and reduces development efficiency. Neo Go already generates contract bindings, but these cannot be used with neotest.
Please consider adding support to generate an 'offchain' SDK.
Describe the solution you'd like
Enhance the generate-wrapper command to create 'offchain' contract bindings.
Describe alternatives you've considered
This feature is implemented in my TS SDK but generates TypeScript, not Go code.
Additional context
Adding this feature would save significant development time, reduce errors, and minimize frustration. It will enable auto-complete, preventing common issues such as incorrect method names, parameter counts, orders, and types. Return type conversion is also important, but may be harder to implement.
Don't forget to add labels!

CLI
feature

We provide contract bindings that work via RPC (generate-rpcwrapper). But neotest is not RPC-based, so they can't be easily reused. Also, there is a question of these bindings usability specifically for testing, sometimes you want to make abnormal calls in tests and they can not provide this.

But neotest is not RPC-based

BTW, we have https://github.com/nspcc-dev/neo-go/issues/3245 for that. But in general I agree, neotest is a testing tool, so we need to keep these non-contract-specific APIs anyway.

Is there any example that I can check? (using a generated rpc file)

You can't use auto-generated RPC bindings with neotest because neotest doesn't work over RPC. But if you're looking for RPC bindings usage examples by their own, then it's a bit different story, the usage pattern is similar to Actor/Invoker pattern but with contract-specific methods:

https://github.com/nspcc-dev/neo-go-sc-wrkshp?tab=readme-ov-file#step-1-5 contains a set of useful links to documentation
https://github.com/nspcc-dev/neo-go-sc-wrkshp/blob/master/dApp/rpc_wrapper/storage.go is an auto-generated RPC wrapper of a simple storage contract and https://github.com/nspcc-dev/neo-go-sc-wrkshp/blob/c0d3328aa423d84767eee4089fe47f47410c8fe0/dApp/dApp.go#L495 contains a tiny piece of example on how to use this wrapper
https://github.com/nspcc-dev/neo-go-sc-wrkshp/blob/c0d3328aa423d84767eee4089fe47f47410c8fe0/dApp/dApp.go#L266 contains examples of Actor/Invoker usages as far as native contract-specific bindings provided by NeoGo.


Add mocked utility (a la ts-jest)

Clear and concise description of the problem
When you mock a function in a module, TypeScript doesn't know that this function has been mocked:
import {vi} from 'vitest'
import {thing} from 'module'

vi.mock('module', () => {
  return {thing: vi.fn()}
})

test('thing', () => {
  // TypeScript doesn't like this line:
  thing.mockImplementation(() => 'hi')
  // etc...
})

Suggested solution
With jest, we could use mocked from ts-jest test helpers (which apparently has been included in jest recently: https://kulshekhar.github.io/ts-jest/docs/guides/test-helpers
I would like something similar for vitest:
import {vi, mocked} from 'vitest'
import * as mod from 'module'

const thing = mocked(mod.thing)

vi.mock('module', () => {
  return {thing: vi.fn()}
})

test('thing', () => {
  // TypeScript can auto-complete this line now:
  thing.mockImplementation(() => 'hi')
  // etc...
})

Alternative
Could install jest and use it's mocked utility.
Additional context
I'm more than happy if there's an alternative solution to the problem that I haven't considered. I'm not married to the mocked utility. Seems like useful prior art though.
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Awesome, thanks. I've now found the docs for that here: https://vitest.dev/api/#vi-mocked

The link by @kentcdodds is now https://vitest.dev/api/vi.html#vi-mocked


Set up team chat for QA

Group has been created on Discord for the QA team.
All team members have been sent the link to join.
This link to join is:
https://discord.gg/8kXfWyzM

Closing issue since we have a chat room already :)


fixing kubectl download url

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-665

Yes, I've tested it and if you look  further in the page, the full script
example has the same syntax as the one I proposed.
On Mon, Feb 13, 2023 at 5:56 AM kat-enos @.***> wrote:

EXTERNAL EMAIL - Use caution when opening attachments, clicking links,
or responding.
@.**** commented on this pull request.
In
docs/platform/2_Delegates/customize-delegates/build-custom-delegate-images-with-third-party-tools.md
https://github.com/harness/developer-hub/pull/665#discussion_r1103997310
:

@@ -68,7 +68,7 @@ The final RUN block retrieves the Kubernetes kubectl command-line tool that

RUN mkdir /opt/harness-delegate/tools && cd /opt/harness-delegate/tools \

-  && curl -LO "<https://dl.k8s.io/release/$(curl <https://dl.k8s.io/release/$(curl>> -L -s<https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl <https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl>>" && chmod +x kubectl

+  && curl -LO "https://dl.k8s.io/release/$(curl <https://dl.k8s.io/release/$(curl>> -L -s https://dl.k8s.io/release/stable.txt <https://dl.k8s.io/release/stable.txt>)/bin/linux/amd64/kubectl" && chmod +x kubectl

@fbreton <https://github.com/fbreton>, I got this off of Kubernetes.io
<http://Kubernetes.io>
curl -LO "https://dl.k8s.io/release/$(curl
<https://dl.k8s.io/release/$(curl>
-L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl
<https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl>
"

—
Reply to this email directly, view it on GitHub
<https://github.com/harness/developer-hub/pull/665#discussion_r1103997310>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABK2FVAOOI6PPET5BPIX4MLWXG5IRANCNFSM6AAAAAAUXRSKEM>
.
You are receiving this because you were mentioned.Message ID:
<EMAIL_ADDRESS>

--
Frederic Breton | Sr Enterprise Sales Engineer
@.*
+33 6 17 16 39 49
https://harness.io/


Test coverage for additional file formats

Tests are missing coverage for .jpg and a number of other formats.

Good point, we'll add this when we address https://github.com/treeform/pixie-python/issues/19

Adding some basic coverage in https://github.com/treeform/pixie-python/pull/21 to get us started.


Add another open for read flag

What changes are proposed in this pull request?
Filebench will use 0xc002 open flag to open the file for reading.
Why are the changes needed?
Support using 0xc002 to open file for reading
Does this PR introduce any user facing changes?
NA

https://github.com/warrenfalk/fuselaj/blob/master/src/warrenfalk/fuselaj/FileInfo.java
https://github.com/cbrumgard/jFUSE-ll/blob/master/src/jFUSE/lowlevel/fuselib.java
@LuQQiu  FYI

@maobaolong Appreciate! Will take a look those parameters

Error: 9.956 [ERROR] Failures:
Error: 9.956 [ERROR] alluxio.client.fs.io.FileOutStreamIntegrationTest.cancelWrite[0]
Error: 9.958 [ERROR]   Run 1: FileOutStreamIntegrationTest.cancelWrite:248 expected:<0> but was:<4000>
Error: 9.958 [ERROR]   Run 2: FileOutStreamIntegrationTest.cancelWrite:248 expected:<0> but was:<2000>

Error: 1.141 [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 71.87 s <<< FAILURE! - in alluxio.client.cli.fs.command.ChecksumCommandIntegrationTest
Error: 1.165 [ERROR] alluxio.client.cli.fs.command.ChecksumCommandIntegrationTest  Time elapsed: 71.862 s  <<< ERROR!
java.lang.RuntimeException: Timed out waiting for process Alluxio job worker to start

alluxio-bot, merge this please


[Feature] Support drop task

Fixes #24015

[FE PR Coverage Check]
:disappointed: fail : 0 / 33 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
0
10
00.00%
[1466, 1467, 1468, 6410, 6411, 6412, 6413, 6414, 6416, 6417]

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[245]

:large_blue_circle:
com/starrocks/sql/ast/DropTaskStmt.java
0
5
00.00%
[25, 26, 27, 30, 35]

:large_blue_circle:
com/starrocks/analysis/TaskName.java
0
11
00.00%
[30, 31, 32, 33, 34, 37, 41, 42, 45, 49, 50]

:large_blue_circle:
com/starrocks/qe/DDLStmtExecutor.java
0
6
00.00%
[868, 869, 870, 871, 875, 876]


Error to read HLS in ondemand mode from RTSP H.265 source

Which version are you using?
v0.22.0
Which operating system are you using?

[ ] Linux amd64 standard
[x] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[ ] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
Try to convert RTSP H.265 stream from HikVision to HLS in OnDemand mode. After open browser i have error 404 to open /stream502/init.mp4. If i set in video recorder codec type H.264, stream is working correctly.
Google Chrome log
GET 200 /stream502/index.m3u8
GET 200 /stream502/stream.m3u8
GET 404 /stream502/init.mp4

HLS config
hlsDisable: no
hlsAddress: :8888
hlsEncryption: no
hlsServerKey: server.key
hlsAlwaysRemux: no
hlsVariant: fmp4
hlsSegmentCount: 7
hlsSegmentDuration: 1s
hlsPartDuration: 200ms
hlsSegmentMaxSize: 50M
hlsAllowOrigin: '*'
hlsTrustedProxies: []

Config source config
paths:
  stream502:
    source: rtsp://login:password@<IP_ADDRESS>:554/ISAPI/Streaming/Channels/502
    sourceProtocol: tcp
    sourceAnyPortEnable: no
    sourceOnDemand: yes
    sourceOnDemandStartTimeout: 60s
    sourceOnDemandCloseAfter: 10s
    disablePublisherOverride: no
    runOnInitRestart: no
    runOnDemandRestart: no
    runOnDemandStartTimeout: 60s
    runOnDemandCloseAfter: 10s
    runOnReadyRestart: no
    runOnReadRestart: no

Describe how to replicate the issue

start the server
read stream from video recorder
open in Google Chrome

Did you attach the server logs?

yes log.txt
Did you attach a network dump?

no

solved as reported in #1706


remove getColorFromScheme usage in histogram

in favor of CategoricalColorNamespace's getScale()
@williaster @graceguo-supercat @conglei

Codecov Report

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

@@           Coverage Diff           @@
##           master    #5878   +/-   ##
=======================================
  Coverage   63.83%   63.83%
=======================================
  Files         381      381
  Lines       23449    23449
  Branches     2615     2615
=======================================
  Hits        14968    14968
  Misses       8468     8468
  Partials       13       13

Impacted Files
Coverage Δ

superset/assets/src/visualizations/Histogram.jsx
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Clarify value of KACHERY_P2P_API_PORT

Current README includes this line:
export KACHERY_P2P_API_PORT="some-port-number"`  # (optional)

Two issues:

This variable is required for the spike sorting tutorial notebook (tutorial 1).
Not sure how this port number should be chosen. At first I tried an arbitrary number (actually the port number that was in the tutorial notebook), and it did not work. What worked for me was to first start a kachery p2p daemon (using the kachery-p2p-start-daemon … command), look at the port number from its output, and match this variable KACHERY_P2P_API_PORT to the port number of the running daemon.

This has been updated. Please set KACHERY_P2P_API_PORT environment variable to be 14747. This should allow you to access the kachery daemon running on typhoon from any computer connected to our network.


ODIS k8s on-call informational session

Once we have migrated ODIS to k8s we should have another informational session to go over the new setup and any changes to the runbook.

Runbooks are updated with relevant info. Will lean on team where there's missing info and add it to runbook.


bug: useWaitForTransaction returns IsSuccess true even if transaction fails after pending

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.6.0
Current Behavior
im using usePrepareContractWrite --> useContractWrite and then useWaitForTransaction.
I am able to submit a transaction using metamask and explorer show pending. Im intentionally sending a transaction i know will fail. thus after a while the explorer reports transaction failed with status showing why. However useWaitForTransaction returns isSuccess  and the callback OnSucess fires  for the failed transaction hash.
Expected Behavior
I expected the useWaitForTransaction to return an error with the status of the error i can display to the user. I'm I using this hook incorrectly?
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

This is more of an Ethereum RPC constraint than a wagmi bug.
See more here:
https://github.com/ethers-io/ethers.js/discussions/2819

See https://github.com/wagmi-dev/wagmi/discussions/428#discussioncomment-2730175


regression: jasmine.clock() inside fakeAsync() doesn't work anymore since 0.8.21

This happens in an Angular application.
Simple steps to reproduce

install Angular CLI
generate a project with ng new
write the following clock.spec.ts test

import { fakeAsync } from '@angular/core/testing';

fdescribe('clock test', () => {

  afterEach(() => jasmine.clock().uninstall());

  it('should fake the clock in fakeAsync', fakeAsync(() => {
    const fakeTime = 12345678;
    jasmine.clock().mockDate(new Date(fakeTime));

    expect(new Date().getTime()).toBe(fakeTime);
  }));
});

Run ng test to execute the test. It fails when zone.js version 0.8.21 is being used (default dependency to zone.js in package.json is ^0.8.19, which now resolves to 0.8.21. If you change it to 0.8.20 and execute npm installor yarn install to make sure the previous version of zone.js is used, the test passes.

@jnizet , in 0.8.21, if you use jasmine.clock(), you don't need to call fakeAsync, zone.js will call it for you. could you try
it('should fake the clock in fakeAsync', () => {
    const fakeTime = 12345678;
    jasmine.clock().mockDate(new Date(fakeTime));

    expect(new Date().getTime()).toBe(fakeTime);
  });

@JiaLiPassion this is a dumb-down version of my real test. In the actual test, I also use tick(). In fact I use this helper class:
class FakeNow {
  private now = DateTime.local(); // this is just luxon delegating to new Date()

  constructor() {
    jasmine.clock().mockDate(this.now.toJSDate());
  }

  tickSeconds(seconds: number) {
    this.now = this.now.plus({ seconds });
    jasmine.clock().mockDate(this.now.toJSDate());
    tick(seconds * 1000);
  }
}

And call fakeNow.tickSeconds() several times in my test. Everything works fine in 0.8.20.
Since 0.8.21, this doesn't work anymore.
Based on your comments, I tried:

to remove the fakeAsync() wrapper as you suggest, and leave the FakeNow class as is: angular complains that tick() shouldn't be called outside of the fakeAsync zone
to remove the fakeAsync() wrapper as you suggest, and remove the call to tick(seconds * 1000) in FakeNow: doesn't work, because I use RxJS interval() in my code, and without the call to tick(), the interval observable doesn't emit anything.

Please tell me if you need more information, and when I have some time, I'll try to provide a reproduction of the actual problem.

@jnizet , please provide a reproduce repo, in new version, you don't need to Fakenow yourself.
But current version have some issue, it will be fixed in next version, but if you can provide a reproduce repo, I can verify my fix is correct or not. thank you.

@JiaLiPassion Here's a repo reproducing the issue: https://github.com/jnizet/zonejsbug
The bug is illustrated in https://github.com/jnizet/zonejsbug/blob/master/src/app/clock.spec.ts.
Switching back to 0.8.20 in package.json, then executing yarn, and re-executing ng test shows that the test passes with 0.8.20.
The app.component.spec.ts file illustrates another regression, for which I'll post another issue.

@jnizet, thank you for posting the issue, I will post a sample after https://github.com/angular/angular/pull/23108 issue is fixed.

OK, thanks.
BTW, I had the impression that 0.8.21 was supposed to support the RxJS delay operator (see https://github.com/angular/angular/issues/10127)
but this simple test doesn't pass:
import { fakeAsync, tick } from '@angular/core/testing';
import { delay } from 'rxjs/operators';
import { of } from 'rxjs/observable/of';

describe('delay', () => {
  it('should support delay', fakeAsync(() => {
    let done = false;

    const obs = of(true).pipe(
      delay(300)
    ).subscribe(() =>{
      done = true;
    });

    // window.setTimeout(() => done = true, 300);

    expect(done).toBe(false);
    tick(350);
    expect(done).toBe(true);
  }));
});

and I haven't been able to understand how to use your example at https://github.com/angular/angular/issues/10127#issuecomment-366109418. Native support, without having to import a ts file out of the project, would be nice.

@jnizet , you need to import an additional file import 'zone.js/dist/zone-patch-rxjs-fake-async' to make rxjs/scheduler/asap/async to support fakedate. I will post a sample based on your repo after those issues are stable.

@ohjames, please provide a reproduce repo .

@JiaLiPassion The reproduction is simple, merely call jasmine.clock().mockDate(...) inside of your beforeEach along with your jasmine.clock().install() and it has no effect. You have to call it inside of the test now, but if you have say 100 tests grouped in the same describe block which should all use the same mocked date, now you have one hundred extra lines in your source code.

@ohjames , you mean
beforeEach(() => {
  jasmine.clock().install();
  jasmine.clock().mockDate(2017, 1,1);
});

it (() => {
  expect(Date.now.getFullYear()).toBe(2017); // will fail
});

this case will fail,
beforeEach(() => {
  jasmine.clock().install();
});

it (() => {
  jasmine.clock().mockDate(2017, 1,1);
  expect(Date.now.getFullYear()).toBe(2017); // will success
});

this will success.
is that right ?
And you are using fakeAsync?
Please paste some sample test codes here, it will help a lot.

I ported all our tests over to fakeAsync and use tick() with a negative number to set the time to what I need: tick(desiredTime - Date.now()) so I'm not worried about this issue anymore, but I suppose someone else will report it.

@ohjames , thanks for the update, I will check jasmine.clock with Date in beforeEach.

@JiaLiPassion
I found an interesting issue with jasmine.clock with beforeAll and fakeAsync.
I just use this specs fakeAsyncTest should work without patch jasmine.clock(Line 968) in the  test\zone-spec\fake-async-test.spec.ts to reproduce the issue.
then just add one test case at the first after the beforeEach and AfterEach
it('should mock date correctly', () => {
  const result = Date.now();
  console.log(new Date(result));
  expect(result).toEqual(baseTime.getTime());
});

Then can reproduce as following(with changes just for the beforeEach, AfterEach and the test case above(not focused)):
// change the 'beforeEach' to 'beforeAll', 'afterEach' to 'afterAll', then the added test case will fail because the date isn't mocked
beforeAll(() => {
    spy = jasmine.createSpy('timer');
    jasmine.clock().install();
    baseTime = new Date(2013, 9, 23);
    jasmine.clock().mockDate(baseTime);
 });

 afterAll(() => {
    jasmine.clock().uninstall();
 });

then move the jasmine.clock().mockDate(baseTime) to the added case, the added case will be passed. like this:
beforeAll(() => {
 spy = jasmine.createSpy('timer');
 jasmine.clock().install();
 baseTime = new Date(2013, 9, 23);
});

afterAll(() => {
 jasmine.clock().uninstall();
});

it('should mock date correctly', () => {
 jasmine.clock().mockDate(baseTime);           // move to this place
 const result = Date.now();
 console.log(new Date(result));
 expect(result).toEqual(baseTime.getTime());
});

While, if with beforeEach and AfterEach, this case can always pass no matter the position of this jasmine.clock().mockDate()
But when I want to test the added spec only with 'fit', this added spec can always pass, but if with one case with fakeAsync, just the one after the added spec. This added spec sometimes pass and sometimes fail.

@Teamop see my previous comment, you can't use those methods anymore. Write your own that uses tick with a negative number to reach your target date. It's simple. I went through this pain so you don't have to :P

@ohjames yes, but for me, this just happens with beforeAll and afterAll with fakeAsync, besides, just want to elaborate on them to provide some information. Hope it can help to identity the real issue.

Yeah it can't be used in any hook other than the test itself since angular 6.

@ohjames, @Teamop, I will check this issue again, thank you for posting the issue.


Add enemy NP detection

Before opening an issue:

[ yes] No one has asked for this feature before in other issues (even the closed ones)

If you open unnecessary/dumb issues, you'll be rewarded with appropriate tags.

Such that if an enemy has its np bar at red use a skill like merlin's invincible or waver's np

@minhducsun2002 want to send a PR? 😆

@MathewSachin this isn't critical hits detection :huh:.


Provide direct navigation from the check results modal to the catalog

On the check results modal, when a user sees a failing test, he is probably going to be interested in the detailed and references that we provide in the checks catalog page.

Right now, he was to make several clicks and navigate to a different section, as well as remembering the name of the check to be able to get that information. We could instead provide a direct link to the check catalog by maybe using anchors in the catalog page?

We could link them from the check results page with e.g.:
demo.trento-project.io/catalog#156F64
Which would save the users quite a bit of interaction

thanks to @fabriziosestito for the anchor idea :-)

@rtorrero  this should be the same as https://jira.suse.com/browse/CFSA-266 ?

I think so @lee-martin though the issue in CFSA-266 doesn't specify anything about linking explicitly though I think it's the best approach!
Thanks for pointing this out, I didn't notice :-)


In the admin panel, setting an install date of today should also select "Active" as the status

Do this on the frontend with a little event hook
https://nycmesh.slack.com/archives/C06GW3Q92TY/p1732577273203379

Actually it may make sense to do it the other way around, selecting active should make the active date today: https://nycmesh.slack.com/archives/C06GW3Q92TY/p1733711980618169


Revert "grpc_handshaker, grpc_handshaker_mgr C++ implementations"

Reverts grpc/grpc#17740

Other alternative could be: a small PR to fix 17740 (it's just moving a single method out of a namespace it is in, erroneously)

This would be a fixup PR instead: https://github.com/grpc/grpc/pull/18024

Closing this in favor of #18024.


Authentication Successful But With Error Message.

Your browser has been opened to visit:
https://goo.gl/fEJhX6

If your browser is on a different machine then press CTRL+C and
create a file called nobrowser.txt in the same folder as GYB.
Authentication successful.
Error: you did not authorize the OAuth token in the browser with the<EMAIL_ADDRESS>Google Account. Please make sure you are logged in to the correct account when authorizing the token in the browser.
I enter correct password and authentication gets successfull but when i try to initiate backup it gives me this error.
Thanks

This happened to me when I had signed in to more than one Google account in the same browser. Switching accounts by signing out of one account and into the next using the google "add account" from top right avatar icon wasn't good enough.
However after going to accounts.google.com, signing out of all accounts, then starting GYB again I was able to get authentication to work all the way through.

+1 even after trying maphew's suggestion


dbeaver/pro#2370 Add support for script variables to query model and outline

For QA

Please check that these parameters and variables are correctly parsed, highlighted and appeared in outline for more complex queries than on the screenshot.
Try changing color of the @var variable

Verified


chore(requirements): update requests and requests-toolbelt

See http://docs.python-requests.org/en/latest/community/updates/#release-history
and https://pypi.python.org/pypi/requests-toolbelt

Jenkins, test this please.


Web page is not being navigated sequentially with the Tab key, Admin issue.

Web page is not being navigated sequentially with the Tab key, Admin issue.
Describe the bug
Web page is not being navigated sequentially with the Tab key, Admin issue. The sequence of focus is unordered.
To Reproduce
Steps to reproduce the behavior:
Go to Admin  (http://localhost:9992/cm/app/?view=workflow&pathType=unknown)
Use Tab key to focus on different components of the screen.
Focus is not moving in sequence on Create Site, Create Folder, Create Page and under Workflows/Roles/Users/Categories tab etc.
Expected behavior
Web page should be navigated sequentially with the Tab key.
Additional context
Navigate all the options available for similar issue and fix.

Fixed with https://github.com/percussion/percussioncms/issues/781


Cosmetics to improve way reports are generated

Tests pass locally and on one of the python versions, consider the rest flakiness


How can I draw a chart like this.

How can I draw a chart like this.

Use the callbacks found in options.scales.xAxes[0].ticks.callback and same for the yAxes[0].  For insteance, suppose your y-values are decimals and you want to show 0.3919 as 39.19%, you would set the following option:
var options={
    scales: {
        xAxes: [
            {
                ticks:{
                    callback:function(v){return 100*v + "%"}
                }
            }
        ]
        yAxes: [
            {
                ticks:{
                    callback://TODO: point to your transform function
                }
            }
        ]
    },
};

You then use those options to create your chart

@RoxKilly is correct.


Dollar equivalent: fiatValueInput is currently hardcoded to 0

fiatValueInput = {data: 0, isLoading: true}//useUSDPrice(parsedAmounts[Field.INPUT]) //TODO: create USDPrice function when available method to get this, for now it will be shown as loading

In the future we'll need a "dollar equivalent" function that for a pair (token, amount) will give us a dollar equivalent that we can use in out sections.


Use github actions via sbt-github-actions

Codecov Report

Merging #91 (7019e2f) into master (b0c667a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #91   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines           35        35
  Branches         2         2
=========================================
  Hits            35        35

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 b0c667a...7019e2f. Read the comment docs.


Devcontainer volume permissions issue

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
The newly updated devcontainer setup mounts the db as user root, and the server as user vscode.
The Docker-compose file is structured such that the server has the db as a dependency.
The Postgres DB mounts in ../dev/database/
The Server sets its data dir to be ../dev/
Because the Server depends on the db, postgres gets installed first.
Running as root, it creates the ../dev/ dir as root:root 755.
This leaves the server unable to write to it, leading to the postCreateCommand.sh script to fail, no venv setup, and no InvenTree install being performed.
Pre-creating the dev/ folder before building the containers will solve this issue. But that's a manual step that you need to "know" about.
Steps to Reproduce

Delete dev/ including the directory itself
Delete the previously used containers (Not sure if needed, but reduces chances of errors)
Open and build the devcontainer

This error message appears:
[7925 ms] Start: Run in container: /bin/sh -c .devcontainer/postCreateCommand.sh
Error: [Errno 13] Permission denied: '/home/inventree/dev/venv'
.devcontainer/postCreateCommand.sh: line 10: /home/inventree/dev/venv/bin/activate: No such file or directory

Then this:
ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: '/usr/bin/pip'
Consider using the `--user` option or check the permissions.

Expected behaviour
I haven't found any way to control what permissions are set when creating the host folder, and it appears like that's something Docker doesn't do.
One (albeit undesirabla) fix is to change   "containerUser" in devcontainer.json to root. Then the Server will mount as root too. Along with all terminals run in VSCode...
Deployment Method

[X] Docker
[ ] Bare metal

Version Information
0.14.0-dev
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

Another option would be to not store the database data locally at all - just in a docker volume?

It looks like this is potentially an issue with the production docker image as well, but does not exhibit in the same way when running outside of the devcontainer context


Turndown fails on non-autoscaling clusters when PodDisruptionBudget(s) exist and eviction is possible

Description
On non-autoscaling clusters where eviction is available, cluster-turndown attempts to evict Pods as part of the "Drain" process. After draining is finished, the node pool is supposed to be scaled down. If a PDB exists in the cluster with a minReplicas > 0, there will be at least one un-evictable pod, meaning draining will never finish.
The eviction logic has an infinite loop which continuously retries eviction that fails with a non-nil, non-IsNotFound, or non-IsTooManyRequests error status. I added a log statement and got this error on my dev cluster from the PolicyV1beta1().Evictions().Evict() call:
I0216 16:12:35.055635       1 draininator.go:396] Evicting in namespace 'guestbook-with-pdb' pod 'frontend-6b6c9c585d-chsvc' failed: Cannot evict pod as it would violate the pod's disruption budget.

Cannot evict pod as it would violate the pod's disruption budget is the error being returned from .Evict().
Reproduce
Create GKE cluster
gcloud container clusters create \
    turndown-pdb-bug \
    --region "us-central1-b" \
    --project "---PROJECTIDHERE---" \
    --num-nodes 3

Create a deployment with a non-zero minReplicas PDB
SETUPYAML=$(cat <<EOF
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-deployment
  labels:
    app: nginx
spec:
  replicas: 3
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx:1.14.2
        ports:
        - containerPort: 80
---
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata:
  name: nginx-pdb
spec:
  minAvailable: 2
  selector:
    matchLabels:
      app: nginx
EOF
)

echo $SETUPYAML | kubectl apply -f -

kubectl get deployment

NAME               READY   UP-TO-DATE   AVAILABLE   AGE
nginx-deployment   3/3     3            3           42s

kubectl get pdb

NAME        MIN AVAILABLE   MAX UNAVAILABLE   ALLOWED DISRUPTIONS   AGE
nginx-pdb   2               N/A               1                     43s

Put turndown in the cluster
bash ./scripts/gke-create-service-key.sh <yourproject> <servicekeyname>

kubectl get secret -n turndown

NAME                           TYPE                                  DATA   AGE
cluster-turndown-service-key   Opaque                                1      27s
default-token-vspf9            kubernetes.io/service-account-token   3      28s

kubectl apply -f ./artifacts/cluster-turndown-full.yaml

kubectl get pod -n turndown

NAME                                READY   STATUS    RESTARTS   AGE
cluster-turndown-7c7c7bcc74-2k5g4   1/1     Running   0          20s

Create a turndown schedule that will trigger soon
SCHEDULE=$(cat <<EOF
apiVersion: kubecost.k8s.io/v1alpha1
kind: TurndownSchedule
metadata:
  name: turndown-pdb-bug-test-schedule
  finalizers:
  - "finalizer.kubecost.k8s.io"
spec:
  start: 2022-02-16T17:35:00Z
  end: 2022-02-16T18:00:00Z
  repeat: daily
EOF
)

echo $SCHEDULE | kubectl apply -f -

kubectl get tds

NAME                             STATE             NEXT TURNDOWN          NEXT TURN UP
turndown-pdb-bug-test-schedule   ScheduleSuccess   2022-02-16T17:35:00Z   2022-02-16T18:00:00Z

Wait for turndown to start and finish.
Note in the logs that at least one node never finishes draining.
date -u --rfc-3339=seconds
echo

kubectl logs -n turndown -l app=cluster-turndown --tail=-1 | \
    grep -i 'Draininator' | \
    grep 'Draining Node\|Cordoning Node\|Drained Successfully'

2022-02-16 18:04:53+00:00

I0216 17:37:30.466494       1 namedlogger.go:24] [Draininator] Draining Node: gke-turndown-pdb-bug-default-pool-75d619d4-2wt5
I0216 17:37:30.466827       1 namedlogger.go:32]   [Draininator] Cordoning Node: gke-turndown-pdb-bug-default-pool-75d619d4-2wt5
I0216 17:37:46.155634       1 namedlogger.go:24] [Draininator] Node: gke-turndown-pdb-bug-default-pool-75d619d4-2wt5 was Drained Successfully
I0216 17:37:46.155643       1 namedlogger.go:24] [Draininator] Draining Node: gke-turndown-pdb-bug-default-pool-75d619d4-4msm
I0216 17:37:46.155647       1 namedlogger.go:32]   [Draininator] Cordoning Node: gke-turndown-pdb-bug-default-pool-75d619d4-4msm
I0216 17:38:11.992618       1 namedlogger.go:24] [Draininator] Node: gke-turndown-pdb-bug-default-pool-75d619d4-4msm was Drained Successfully
I0216 17:38:11.992975       1 namedlogger.go:24] [Draininator] Draining Node: gke-turndown-pdb-bug-default-pool-75d619d4-s2h9
I0216 17:38:11.993227       1 namedlogger.go:32]   [Draininator] Cordoning Node: gke-turndown-pdb-bug-default-pool-75d619d4-s2h9

Note in “kubectl get pods” that 2 of the deployment pods are still running and one is unschedulable.
kubectl get pods

NAME                                READY   STATUS    RESTARTS   AGE
nginx-deployment-66b6c48dd5-9ct6l   0/1     Pending   0          26m
nginx-deployment-66b6c48dd5-lzs74   1/1     Running   0          26m
nginx-deployment-66b6c48dd5-wnqpp   1/1     Running   0          27m

Note in “kubectl get nodes” that after scaleup should have happened, we still have
a turndown node and the 3 regular nodes are sitting around marked as noschedule.
date -u --rfc-3339=seconds
echo

kubectl get nodes

2022-02-16 18:05:16+00:00

NAME                                                  STATUS                     ROLES    AGE   VERSION
gke-turndown-pdb-bug-cluster-turndown-2ecd8eb5-pp8t   Ready                      <none>   29m   v1.21.6-gke.1500
gke-turndown-pdb-bug-default-pool-75d619d4-2wt5       Ready,SchedulingDisabled   <none>   58m   v1.21.6-gke.1500
gke-turndown-pdb-bug-default-pool-75d619d4-4msm       Ready,SchedulingDisabled   <none>   58m   v1.21.6-gke.1500
gke-turndown-pdb-bug-default-pool-75d619d4-s2h9       Ready,SchedulingDisabled   <none>   58m   v1.21.6-gke.1500

Possible solutions
At the very least, we should have a retry limit on evictions so there isn't an infinite loop that makes the turndown pod hang.
Real solutions could involve some sort of "force deletion" or notifying the user of the PDB's presence and asking them to make a modification.

Ok, when I wrote the drain functionality, I referenced kubectl source code for cordoning a node. My guess is that the code just needs updating to support the newer kubernetes features/functionality. For reference, here's the latest kubectl drain code that would relevant for this fix (hint: it looks like there were some changes to handle a magnitude more error conditions).
https://github.com/kubernetes/kubectl/blob/a4aec62157e9fd73a038c9aab36822707277f00c/pkg/drain/drain.go#L272-L377

A related problem, which explains why drain loops forever instead of timing out like its supposed to (nice find, Bolt):
https://github.com/kubecost/cluster-turndown/blob/578ef725bde8620e1beb08ebab684a7127a260e8/pkg/cluster/draininator.go#L50

I think the solution here is two-fold:

Update eviction logic to include new conditions noted from the kubectl repo link above
Use a reasonable timeout for each eviction.

I believe the globalTimeout addition was based on the older kubectl evict logic that didn't work properly. At least, that's what I'm going to tell myself 😞

This issue has been marked as stale because it has not had recent activity. It will be closed if no further action occurs.

This still feels relevant, if nothing else as documentation


Add eslint rule to force devs to memoize values sent to context providers

Relates to https://github.com/visgl/react-google-maps/pull/287
Also added a very basic, not so opinionated settings.json and extensions.json file with prettier correctly configured.
Sounds like a good thing to have on the git repo without causing issues

Thanks a lot! I wasn't even aware of that rule.

Yep, it's pretty awesome. We added it at my company's codebase and it has caught a lot of perf regressions. Should be more wildly used for sure!
@usefulthink
Removed the vscode files and set the exhaustive deps rule to error.
Cheers


Set up noir_wasm to be built by dispatching the nix flake from noir

Part of https://github.com/noir-lang/noir/pull/1208 and of https://github.com/noir-lang/noir_wasm/pull/9

@jonybur whats the status of this?

Done and merged as well. Closing.


Revert back to min/max representation of empty AABB

[x] I agree to follow the project's code of conduct.
[x] I added an entry to rstar/CHANGELOG.md if knowledge of this change could be valuable to users.

This reverts back to the min/max representation of empty AABB due to regressions introduced by the numerically more tame but not invariant for merging representation.
To avoid regressing #161, it also adds a single check to avoid computing the distance to an empty envelope (of the root node of an empty tree). Integer coordinates are always prone to overflow but in the empty case we are forcing this onto the caller whereas every non-empty tree will have AABB where that the caller controls and where we can reasonably ask them to control for overflow or use a custom Point impl based on saturating arithmetic.

This would be my personally preferred alternative to #181 and #182 trying to keep #161 working.
Generally speaking, I am really unsure whether the problems caused by fixed-precision integer coordinates are worth it, but this fix seems to be rather targeted and should not add measurable costs to the majority of floating-point coordinate users.

(Whatever choice we make, we should probably yank 0.12.1 after releasing 0.12.2 to crates.io.)

OK – shall we merge this, release a patch version, and yank?

OK – shall we merge this, release a patch version, and yank?

If there are no objections from elsewhere, yes, I think that would be best to provide a quick resolution for affected projects.
I think the risk of an error in the fix is small for most users (as we are going back to the previous behaviour) and we'll just have to deal with any fallout from fixed-precision integer coordinate users. I tried to avoid it but I am admittedly not confident that it can be avoided.

0.12.1 is yanked

0.12.1 is yanked

I think it is customary to yank only after an upgrade is available. Otherwise, the degree of eyebrow raising can be problematic. But I suspect you'll push 0.12.2 soon as well?

Released!

I think it is customary to yank only after an upgrade is available.

At first I thought this made sense, but now I'm not sure.
Assuming the fix is patch compatible (0.0.x++), if you wait to have the fix published before running cargo yank, it seems like the only practical consequence of cargo yank is to annotate what's shown on crates.io (and other indexes).

If you already have the patch-compatible version published, cargo update will update to that fixed version, skipping the broken one anyway, right?
So it can be used to prevent people from updating. But it's not useful for "skipping" the broken one, since cargo already installs the most recent semver compatible one when running cargo update.

To summarize, it's my conclusion that cargo yank should be used precisely in the time after you know you have a problem, but before a fix is available.

Delightfully, we can unyank.

A lot of CI runs tools like cargo audit or cargo deny which will warn about yanked dependencies. Warnings which are not actionable because no semver-compatible replacement is available is what I was referring to. Admittedly, this is not so bad if an earlier patch release is available because you can most likely downgrade successfully, but for example yanking 0.12.0 is significantly worse.

Delightfully, we can unyank.

I would not recommend that due to as written, cargo update is not the only concern. Yanking sends a relevant signal to different tools and also users with existing locked dependencies.

It's my conclusion that cargo yank should be used precisely in the time after you know you have a problem, but before a fix is available.

I phrased this poorly — In case there was confusion, I'm not recommending unyanking in this case.
I'll again:
You should yank as soon as you know there is a problem, to keep people from updating to the broken version, even before a fix is available, ensuring legacy users stay on the old version until the fix is available.
yanking after a fix is published isn't harmful it's just not very useful.
As @adamreichold points out, there is some utility to yanking, even if you've already shipped the fix.


Delete no-longer used endpoints

We've been carving away the need for the x-api. The only endpoints that
are still being used are the ones that the CLI calls.

:+1: for deleting unused endpoints/code.
(I've not done any checking of what is being deleted here, I trust you know what you're doing.)

I'm going to close this.
This API will be superseded by the v2 project, and I've decided not to try to make changes to v1 that will smooth the transition.


Cannot access 'NestedIntFilter' before initialization

I followed all the step showed on README, but when I run the application, I'm getting this error
/workspaces/nest-demo/src/generated/common/inputs.ts:28
not?: NestedIntFilter | undefined;
^
ReferenceError: Cannot access 'NestedIntFilter' before initialization
at Object. (/workspaces/nest-demo/src/generated/common/inputs.ts:28:9)
at Module._compile (node:internal/modules/cjs/loader:1103:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/workspaces/nest-demo/src/generated/article/inputs/ArticleScalarWhereWithAggregatesInput.input.ts:2:1)
at Module._compile (node:internal/modules/cjs/loader:1103:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1157:10)

Thanks!
The cause is that NestedIntFilter is used before the declaration.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Errors/Cant_access_lexical_declaration_before_init
I will fix that immediately.
You can now address this by moving the location of the NestedIntFilter declaration.

Done in 223cbcc, released in v1.0.3


minor travis-ci improvements

Moving the travis-ci build to their new docker container based infrastructure should be slightly faster and allows caching (maven) in public repos.

I signed it!

Seems to be failing due to this issue. https://github.com/travis-ci/travis-ci/issues/3396

Thanks for this. I'll try setting an explicit heap size.


Support for H7060 Floodlights

Please explain your feature request in a one or two sentences.
Would like to have the H7060 Floodlights added for control

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

Any particular Govee devices that this relates to?
H7060

Anything else?
Hopefully this is supported by the Govee API.

The H7060 model is now supported by the Govee API and with the beta version of the plugin you will be able to control this device without depending on bluetooth control.

Thanks!  Is there a way to tell that the lights are using the API instead of Bluetooth?  Or does the switch happen automatically?

With debug logging on, you can see which commands are being sent via which method.
The plugin will initially attempt bluetooth for supported commands, otherwise if bluetooth fails or it’s an unsupported command then the plugin will revert to the API


Update Viewport on resize in all of the GL tutorials.

Fixes #1964

@dotnet-policy-service agree

I have run every demo, although to get them to build I referenced the live NuGet packages (rather than project references which wouldn't build at the moment.)


Call raise_for_exception() when fetching url

At the moment, if the response contains an error status (400, 500, etc), the code will not raise the proper exception. Instead, it will raise a pydantic missing field error from this line: return response_class(**r.json()), which is misleading.
This pull request makes the code raise an exception if there was an issue in requests.get(), and will also include the exception object (raise LnurlResponseException(e)) which contains the response text, instead of just containing a one line error message like it has at the moment (raise LnurlResponseException(str(e))).

ACK

this was addressed in the latest merge https://github.com/lnbits/lnurl/commit/7cffcb9c24521d429d2fb275d236d13690e79325


Clearing Errror Function + Test - Forsthuber, Liu

#5 solved

good job! 👍

bonus question: tell me why this windows build is failing. no fix needed.


istioctl install --set profile=demo y Keep waiting for Deployment/istio-system/istiod

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
When Install istio, I run command : istioctl install --set profile=demo y
After installed istio core, istiod install keeps waiting
# root @ VM-96-189-centos in ~ [18:59:58]
$ istioctl install --set profile=demo -y
✔ Istio core installed
- Processing resources for Istiod. Waiting for Deployment/istio-system/istiod

[ ] Docs
[ X ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
How was Istio installed?
Environment where the bug was observed (cloud vendor, OS, etc)
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

We need more information, look at kubectl describe and kubectl logs of istiod deployment. Or attach http://istio.io/help/bugs/#generating-a-cluster-state-archive

We need more information, look at kubectl describe and kubectl logs of istiod deployment. Or attach http://istio.io/help/bugs/#generating-a-cluster-state-archive

Thanks, Problems solved. Maybe network error


controlnet_aux disables StableSwarmUI from right-clicking in the Comfy Workflow Editor

Install https://github.com/Fannovel16/comfyui_controlnet_aux
Will cause StableSwarmUI to fail when he clicks the right mouse button in the Comfy Workflow Editor. Is there any conflict

You can right-click normally in the comfyui interface

哼？

I am sorry, because it is found that a plug-in is incompatible with comfyui. Then I was ready to delete the problem feedback, and the error caused the content to be deleted


[desktop_webview_window] How to call the dart layer interface in javascript in windows？

@liujing1 what is your usage case, maybe I can help you?

How to call the dart layer interface in javascript in windows？
@a-eniou-pvotal  When is registerJavaScriptMessageHandler(String name, JavaScriptMessageHandler handler) and  setPromptHandler(PromptHandler? handler) available in windows

Aha, got it
/// available: macOS those methods are not supported for Windows OS
I can’t help in that case, I use Mac OS

if it is very important for you maybe you could add it by vscode or visual studio for .net on windows

@boyan01 can you help me?

what?! windows not support call dart in js? only support mac os?

any update on this to java Script handler to  support windows?


on windows, can we use URLs only, to open templates and Views in our IDES?

Hi Robert, could you give that a go? cheers.  Am thinking we may be able to launch these files even within the browser.
See django-debug-toolbar issue with our approach https://github.com/jazzband/django-debug-toolbar/issues/1564

I'll give it a look!

Hey,
I investigated this a little and IntelliJ IDEs don't have an easy protocol such as pycharm://path/to/file so I don't think it can be done for them. I can have a look and how I can implement our own protocol to open files in the desired IDE, as maybe that is a future proof solution.
In other good news, vscode://path/to/file works..

It looks like IntelliJ IDEs have some support for this, I'm not sure if pycharm is included, and Linux may need adding:
https://youtrack.jetbrains.com/issue/IDEA-65879?_gl=1*kcrbpi*_ga*MTYzMDM4NDM2MC4xNjk3Mjg4MTU2*_ga_9J976DJZ68*MTY5NzI4ODE1Ni4xLjAuMTY5NzI4ODE1Ni4wLjAuMA..&_ga=2.241725761.237417566.1697288156-1630384360.1697288156

Some info on the jetbrains IDEs and opening files here
https://docs.sourcegraph.com/integration/open_in_editor#jetbrains-ides-on-windows
From the bug report above I think MacOS may be covered too.. Linux, may be a matter of asking upstream - I'll probably know relatively quickly as I use Linux myself.


Email Subscriptions for New Features

The news section contains a lot of information that could help staying up-to-date with new developments in Web APIs.
It would be a nice addition if users could subscribe to it and get notified via email.

There's an RSS feed at https://caniuse.com/feed with that news, you can use a feed reader for that or look for RSS to email tools if you'd prefer it as email. :)

Closing as per my last comment


As a K8s Warden customer, I need to be provided backups and a disaster recover plan built into the offering

Ben found this https://expertinsights.com/insights/the-top-kubernetes-backup-and-storage-solutions/ if it presents some things to explore.

We're anticipating allegedly a demo on next Thursday October 10th.


error-handling: ensure Close is called only once

Related to #1939 .
The exercise requires the usage of defer (the code can panic). This in turn raises a questions about some inner workings of defer.
Answering to the comment in PR: https://github.com/exercism/go/pull/1939#issuecomment-961216677

Is there any motivation behind this? Did you see any particular solution calling Close() more than once?

In one of the solutions I have mentored there was something like this:
...
defer r.Close()
defer func() {
   if recover() != nil {
      ...
      r.Close()
   }
}

I don't believe this adds much or solves any problem with the exercise.

Knowing how multiple defers are executed in case one of them handles panic with recover is something worth learning IMO.
If r.Close closes some channel we want to be sure it is called exactly once. So I think it is a reasonable requirement.

Thanks for clarifying!
I'm now convinced this is a good change.


Issue with AzureBlobTranscriptStore.GetTranscriptActivitiesAsync if the blob have been created with NodeJS with AzureBlobTranscriptStore class

Version
What package version of the SDK are you using:  Latest
Describe the bug
Give a clear and concise description of what the bug is.
Log Transcript with AzureBlobTranscriptStore in a NodeJs Bot. Then try to consume the Transcript with a C# Bot. The issue is the name of the timestamp field with a T in C# & a t in NodeJs. And also the value in the timestamp is very strange : ex<PHONE_NUMBER>574
Expected behavior
Save behavior in C# & NodeJs classes write & Read
Screenshots

[bug]

@didaskein thank you for opening the issue.  We'll take a look at it.  the earliest we'd get a fix out is our 4.6 release.

@tomlm, IIRC you wrote both side of the Transcript store and this was one of your design goals. Could you take a quick look and see if you can fix?


Parse Error with PHP 5.3

I am getting a php parse error with PHP 5.3.X:
Parse error: syntax error, unexpected '[' in /~myserverpath/craft/plugins/httpreq/variables/HttpReqVariable.php on line 14
Any thoughts on how to make this backwards compatible with Craft's minimum supported version?

Hi,
It should not be an issue, we simply used the short notation for creating arrays, but it is indeed only available as of PHP 5.4.
What I can do is replace them with the classic array notation. I'll mark this ticket as closed once it is done.

Cool. Thanks.

You're welcome ^^

Looks like on line 60 of HttpReq_RestClientService.php also needs to be updated to = array();
Thanks

Sorry, I don't have a PHP 5.3 environment to test it unfortunately.
Line 60 seems to use the classic notation though: https://github.com/Tcheu/craftcms-httprequest/blob/master/httpreq/services/HttpReq_RestClientService.php#L60

Sorry looks like my file is outdated. Nevermind.


GIT Repository Management

add git repository management features
Details
each repository be placed within a group (organization on github). this will then be used to build repository url for the relevant provider.
groups will be able to hold settings as well as repositories. If the provider is Github, the nested groups will no be allowed.

[ ] No nested groups for Github (Validator)

Models

[ ] Groups

id

parent

provider (Github/Gitlab)

methods

url. get group URL

[ ] Repository

id

group

path

name

description

tags

provider (Github / Github)

private. is repo public

credentials Foreign Key pk of api credential.

Methods

[ ] url. build complete repo url.

Features

[ ] add/change/delete/view repo
[ ] config renders for role git_configuration as part of config management

Requirements

[ ] Uses ansible role git_configuration

Addition Features new issue??

[ ] ~Feature Sync issues

[ ] ~Feature sync MR

[ ] ~Feature sync milestones

[ ] ~Feature Scrum Board

[ ] Labels
[ ] Links to Gihub/Gitlab labels
[ ] links to Github/gitlab milestones

[ ] ~Feature Issue/MR as project Management task

marked this issue as blocked by #128

added 3m of time spent

marked this issue as related to #113

marked this issue as blocked by #129

marked this issue as related to #33

marked this issue as related to #68

marked this issue as related to #158

added 15m of time spent

marked this issue as related to #168

marked this issue as related to #14

marked this issue as related to #138

marked this issue as related to #167

marked this issue as blocking #96

marked this issue as related to #149


Some guy is selling your Software

Hey, i saw a guy wich is selling scripts and interiors on discord ( https://discord.gg/S5sTU3C ) and your txAdmin is he selling for 15€ its names admin control v2 or something
just for your information ^^

He removed it.


Put a flat list of terminal quick fixes in the failed command's SI decoration

Why not show these:

In the red menu too?

Happy side effect of this is it'll be possible to use the quick fixes after other commands have run.


Make backporting process easier on Mac OS users

Currently, we require users to spin up a dev VM if they're on Mac OS because our backporting scripts require Linux. Ideally, we should not have to dictate a user's dev environment to handle weekly duties. The scripts should be usable on all relevant platforms. The only incompatibility that I can see is the use of sed in the backporting scripts. One approach would be to write a Go script that replaces the functionality that we need from sed and use it as go run ./contrib/backporting/blah-script.go.

With some recent additions to the team some folks have already actively started chipping away at similar problems which is awesome to see.
The main issue with forcing a dev VM usage is the inability to use the primary development environment. Resolving conflicts (using stock vim), running git commands (no aliases), etc.
The current middle ground is using a combination of running commands locally (to edit/merge files) and in VM (cherry-pick/tag editing/etc) which sort of works, but still results in quite sub-optimal experience.

Additional data point: I accidentally sent it to my local terminal and not the VM and this error popped up, so it may be more than just sed that's blocking.
❯ ./contrib/backporting/cherry-pick 69f10edf21ad5d012c300ae9d2d3b9ca78c1bf16
readlink: illegal option -- e
usage: readlink [-n] [file ...]
usage: dirname path
./contrib/backporting/cherry-pick: line 4: /common.sh: No such file or directory

This has been on my to-do list for some time now. I'll take a stab at it. Not assigning the issue to myself until I've committed some cycles to it. @christarazi suggested a good option - https://github.com/cilium/cilium/pull/16016#discussion_r626193078.

Resolving conflicts (using stock vim)

Isn't directory sharing enabled on macOS for the development VMs? That should allow you to edit files on the host with whatever editor you prefer, no?

running git commands (no aliases), etc.

Maybe https://github.com/cilium/cilium/pull/14272 would be useful here? (Documented at https://docs.cilium.io/en/latest/contributing/development/dev_setup/#option-1-using-the-provided-vagrantfiles-recommended.)

I've started looking into this. Parking it in my queue.


java: fix wrong filename-based guessed archive version

Fixes #2130
Also switch slices usage to standard library's instead of relying to golang/x/exp/slices

Closing this as I wasn't able to halt parsing filename of nested JAR files to fix the RC; there were too many breakges

@hainenber thanks for making the attempt! If you'd like to work with one of the maintainers on getting this unstuck, feel free to let us know on slack or at our community meeting / office hours.


These changes make it so Baker working with django 3.0

I really don't have the time to look through these pull requests anymore.  It seems like you might.
Would you be interested in taking over this project entirely?

@krisfields Yes I would be happy to. I use baker quite a bit in my projects.


$controllerProvider.register() is not annotated

First, thank you for the great work, Olov.
I noticed that ng-annotate does not understand $controllerProvider.register(). Example:
angular.module('test', [])
.config(function( $controllerProvider ){
  // NOT annotated:
  $controllerProvider.register('FooCtrl', function( $scope ){
    $scope.foo = "FOO";
  });
});

I guess it just flew under the radar?

Thanks. This should be added to the next release.

released in 1.1.0


All unmerged commits from dev branch

Prep for eliminating two-branch system.
This is a rebase of dev onto main. There were no conflicts.

entirely covered by #105


CollectD plugin not portable across CollectD versions

developing the plugin in C definitely has a performance advantage, as well as, perhaps access to internal data structures of CollectD that may not be exposed otherwise.
however, patching the collectd source means that it needs to be patched at every collectd release, especially if one is to use the distro's provided collectd
we tried using .so lib compiled for 5.4.1 with 5.5.1 and it caused a SIGSEGV
if performance is not a concern, perhaps using something like python/perl plugin, would be preferable and more portable across CollectD versions

MAD supports the Collectd HTTP source and the file output plugin is now deprecated. You can find example configuration of the Collectd HTTP source here:
https://github.com/ArpNetworking/metrics-aggregator-daemon/blob/master/config/pipelines/pipeline.conf#L85
We also support a Telegraf input source as well. Example:
https://github.com/ArpNetworking/metrics-aggregator-daemon/blob/master/config/pipelines/pipeline.conf#L67


How to save the obj files

Is there any way to continuously save the 3d face models so that I can get a 4d obj file?i can see the rendering but cant save them

Hi, sorry for the late reply. You can use eos's write_obj(...) or write_textured_obj(...) function - it's already used in the current example (https://github.com/patrikhuber/4dface/blob/70d4d5f77c3240be9412521b1d92d5701381e8ab/apps/4dface.cpp#L253), you could just call that every frame.


comments to describe serialized layout

Coverage remained the same at 98.572% when pulling 04b59ead6d5a49d3a7ad463d008839c646768010 on layout-comments into 92b069883efb42f4aad75f012c025c80927e9dcc on master.


[AUTOPATCHER] Patches CVE-2021-35942 for glibc

        Patches CVE-2021-35942 for glibc.
        This patch and PR was automatically generated and needs human verification before merging.

Issue already resolved.  Closing autopatch issue.


How to make time show as AM and PM, or can i use custom string for time?

ya, I noticed that too.

@sami-bre Thank you.


cmd: add snapproc command

Add new command to take a snapshot of /proc.
We copy only the minimal set of files we care about to run the cpuaff
command.
Signed-off-by: Francesco Romani<EMAIL_ADDRESS>

/retest

ping

ping

Looking

we will re-evaluate later


document r8.im registry in YAML reference

This PR updates the cog.yaml reference page to mention the r8.im registry.

Nice! I wonder whether this could be the only one mentioned for simplicity...

You mean instead of the existing hoolio thing?

Yep. "r8.im is Replicate's registry, but this can be any Docker registry." or somesuch. No big deal though.


Changes required for Cryptography Deprecation

Keylime was experiencing the following deprecation warning:
"CryptographyDeprecationWarning: signer and verifier have been
deprecated. Please use sign and verify instead."
This resolves the warning by updating to useing verify instead
of verifier
Resolves: #222

Tested this with no issues.


"incompatible library version" when upgrading Ruby

So, i have upgraded my ruby version to ruby 3.0.1. I have a rails application with rspec.
When i try to run the command
bundle exec rspec spec

i get the following error
oadError:
  incompatible library version - /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/nokogiri.bundle
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:25:in `require'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:25:in `rescue in <top (required)>'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:4:in `<top (required)>'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri.rb:11:in `require'
# /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri.rb:11:in `<top (required)>'
# ./spec/spec_helper.rb:3:in `require'
# ./spec/spec_helper.rb:3:in `<top (required)>'
# ------------------
# --- Caused by: ---
# LoadError:
#   cannot load such file -- nokogiri/3.0/nokogiri
#   /Users/ahmed/.rvm/gems/ruby-3.0.1/gems/nokogiri-1.11.3/lib/nokogiri/extension.rb:6:in `require'

I've tried fixing everything with rvm, but still this bug didint fix, any issues ?
Environment:

ruby : 3.0.1
nokogiri 1.11.3
rails:  6.1
Thanks

Hi @A7madXatab, sorry you're having problems. I'll try to help.
The error you're seeing is similar to errors I've seen when Nokogiri has been copied across versions of Ruby (which it sounds like might be the case?). Because Nokogiri has a compiled C extension, a version compiled with Ruby 2.7 is not able to run with Ruby 3.0 -- the extension must be re-compiled.
Please uninstall Nokogiri and re-install it, following the instructions at https://nokogiri.org/tutorials/installing_nokogiri.html. If you're still having problems, please provide us with some more information (below).
I'd also like to suggest that you try to use the precompiled native gem if possible, which avoids this problem entirely by providing precompiled libraries for Ruby 2.5, 2.6, 2.7, and 3.0. You can read more about that at https://nokogiri.org/tutorials/installing_nokogiri.html as well.

What is the complete output of gem install or bundle install?

the output goes here

If installation completed but is broken, what is the complete output from nokogiri -v?

the output of "nokogiri -v" goes here

If installation failed during compilation, what are the complete contents of the mkmf.log file generated during the failed installation?

the mkmf.log file contents go here

Tell us about your system!
What is the output from ruby -v?
What is the output from gem -v?
What is the output from gem env?
the output of "gem env" output goes here

If you're using Bundler:

what is the output from bundle version?
what is the output from bundle config? (Take care to redact any credentials)

the output of "bundle config" goes here

If you're on MacOS, please note:

the version of XCode you have installed (if you know)
the output of gcc -v or clang -v

@flavorjones thank you very much, previously i have tried uninstalling and reinstalling the gem but no luck. Then

Please uninstall Nokogiri and re-install it, following the instructions at https://nokogiri.org/tutorials/installing_nokogiri.html. If you're still having problems, please provide us with some more information (below).

I have followed the installation process and installing the ruby platform for MacOS, specificlly this part.
All things said, thank you very much. Have a great day!.

OK, I'm glad you were able to figure it out.
I just want to recommend again that you try to use the precompiled native gem for MacOS, which should avoid the majority of installation and compatibility issues you might have. Good luck and happy coding!


wont open

i downloaded the most recent version and imported it and i think 2.201 is messing it up but it staight up wont boot up anymore

2.201 messed it up wait for a new update


Fetch card content individually

Instead of fetching the entire list of cards with content, consider

Fetching just the Card without the content (compare payload size difference first).
Fetch fewer cards.

Instead of fetching card content individually, #20 fetches 50 cards at once and refetches if the cached data size is small.


AKS Learn feedback: api-server-authorized-ip-ranges is not functional with service tags

Type of issue
Code doesn't work
Feedback
Executing the AKS creation command
az aks create --resource-group myResourceGroup --name myAKSCluster --api-server-authorized-ip-ranges AzureCloud,<IP_ADDRESS>
results in an exception:
--api-server-authorized-ip-ranges should be a list of IPv4 addresses or CIDRs
Page URL
Create an AKS cluster with Service Tag authorized IP ranges
Content source URL
Create an AKS cluster with Service Tag authorized IP ranges

Author
@schaffererin
Document Id
b3124556-4672-d2aa-aab1-64d2cd3ac354

hi, @Shawn-StatRecovery! thank you for your feedback. i've just run through the commands with no issues. i didn't receive any exception messages. we've identified no issues with the documentation itself, so i'm going to go ahead and close out this issue.
i'd recommend retrying the steps, making sure you install the preview extension and register the service tag feature flag.
thanks again! #please-close

Thank you @schaffererin


Open project view file after auto import of project

Checklist

[ ] I have filed an issue about this change and discussed potential changes with the maintainers.
[ ] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Description of this change
The change here is to open the project view file the first time the project is open if the auto import processor imported the project. The idea here is to provide a quick way for the user to customize the project since they did not go through the wizard.

Good catch @tpasternak!
I noticed what I was doing wrong, I was setting the userData on the project after the call to ProjectManagerEx.getInstanceEx().openProject which would explain the issue. Let me do some more testing and get back.

Yep, that seems to have been the problem. I was able to have the bazel project view file open for projects using a non-sandbox environment

Let me add invokeLater back. Weird that I was not getting that error! Are we testing the same? I'm using idea 2023.1.4, starting the app and opening the project through the welcome screen. Are you using a different entry point?

Thanks, this was my bad, I must have been testing with a stale build because I was hitting it too when testing again this morning. Sorry to cause such trouble 😥!


Add excludeModules settings for Node targets

What does this PR do?
This PR doesn't actually add any new executable code but just documents a new setting. The actual code that implements this will come from the build engines.
While working with the webpack plugin and express, I found out that if I implemented the plugin middleware, which inclusion path is projext-plugin-webpack/express, projext wouldn't find it on the package.json dependencies and it would try to bundle the whole thing.
Well, while this is will be fixed by the webpack plugin itself, what if this happens to you with a module like colors? Where you, most of the times, include colors/safe instead of just colors. This is where the new setting enters: excludeModules.
This new setting is a list of modules/inclusion paths that you don't want the build engine to include on your bundle.
How should it be tested manually?
Reading?

Pull Request Test Coverage Report for Build 69

0 of 0 (NaN%) 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 67:
0.0%

Covered Lines:
1390

Relevant Lines:
1390

💛  - Coveralls