Exposure 157267 for tertiary tile 83219 on night 20221210 should be marked as bad

Exposure 157267 for tertiary tile 83219 on night 20221210 had very low efftime:
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/83219/20221210/tile-qa-83219-thru20221210.png
It's possible we were unguided during this exposure. Regardless, we're going to repeat the observation in full and so exposure 157267 should be marked as bad.

@marcelo-alvarez : I notice that this 157267 exposure is still not flagged as "bad".
it s not super-critical, as:

observing queries are made manually for this tertiary15 program, and we know we should ignore it (so re-observed this tile on 20221214)
I perform on my side the cross-tiles redux, where I can manually discard it.

but it would sound safer to flag it, still (sorry to add more on your plate!)
https://data.desi.lbl.gov/desi/spectro/redux/daily/tiles/cumulative/83219/20221214/tile-qa-83219-thru20221214.png

>>> d[d["FAPRGRM"] == "tertiary15"]["NIGHT", "EXPID", "TILEID", "EFFTIME_SPEC"]
<Table length=25>
 NIGHT   EXPID  TILEID    EFFTIME_SPEC
 int32   int32  int32       float64
-------- ------ ------ ------------------
20221129 155693  83210<PHONE_NUMBER>121094
20221129 155694  83210<PHONE_NUMBER>570312
20221129 155695  83211<PHONE_NUMBER>109375
20221129 155696  83211<PHONE_NUMBER>082031
20221129 155697  83212<PHONE_NUMBER>476562
20221129 155698  83213<PHONE_NUMBER>859375
20221129 155699  83214<PHONE_NUMBER>210938
20221129 155700  83215<PHONE_NUMBER>015625
20221129 155701  83215<PHONE_NUMBER>667969
20221129 155702  83216<PHONE_NUMBER>148438
20221129 155703  83217<PHONE_NUMBER>1875
20221129 155704  83218<PHONE_NUMBER>640625
20221210 157267  83219<PHONE_NUMBER>097656 # <= EFFTIME_SPEC should be zero
20221210 157268  83220 1111.5369873046875
20221210 157269  83221  1173.926025390625
20221210 157270  83222  1196.331298828125
20221210 157271  83223 1166.7371826171875
20221210 157272  83224 1195.4879150390625
20221210 157273  83225<PHONE_NUMBER>554688
20221210 157274  83225<PHONE_NUMBER>4375
20221210 157275  83226<PHONE_NUMBER>976562
20221210 157276  83226<PHONE_NUMBER>234375
20221214 158188  83219 1043.6629638671875
20221214 158189  83227<PHONE_NUMBER>242188
20221214 158190  83228 1011.4068603515625

No worries @araichoor and thanks for the reminder. I am still getting up to speed on how different pipeline activities depend on one another and appreciate your patience as I sort it all out!

This exposure has been marked as bad, i.e.
% grep 157267 exposure_table_20221210.csv
157267,science,83219,ignore,a0123456789,,,1342.749,1038.423218,special,main,tertiary15,1000.0,dark,1.05072474013287,1.435424,-99.0,35.623479,-4.8357,1,1,tertiary15,main survey,59924.107212506,20221210,|,|,low efftime; see desisurveyops-85|

Closing this ticket.

We need this to get propagated to the exposures-daily.csv file; it is currently still assigned 280.9 effective seconds.
$ cat /global/cfs/cdirs/desi/spectro/redux/daily/exposures-daily.csv | grep 157267
20221210,157267,83219,35.617,-4.826,59924.10721249,special,other,tertiary15,specialtertiary15,1342.7,280.9,1000.0,other,0.85,1.435,0.025,0.848,1038.4,36.2,9.6,23.1,31.7,2097.2,3237.4,589.1,5233.2,280.9,311.2,293.6,374.2,271.4,308.2,370.6,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,0.0,20.678,20.338,18.973,0.0,0.0,0.0,0.0

@schlafly I was just about to re-open, I'm doing that now.

Looks good, closing!


Fix alignment props on Button component

The left prop is not implemented correctly. The right border bleeds over Inputs when placed inline.
Also, the z-index hack is, well, hacky. There is probably a cleaner solution.

This is actually an issue with the Input component's middle prop. We need to apply the same z-index and margin-left styles that are on the Input component to the Button component.

Fixed in v0.6.6. Also fixed some issues with the alignment props on the Button component.


Validate value by checking for whitespace in constraint expression

When using operatingsystem standard constraint, it fails when we use the value shown in docker info. For example, if I try to create the following for ubuntu OS,
docker run -d -e constraint:operatingsystem=="Ubuntu 14.04.1 LTS" --name snort glanf/snort
swarm returns
FATA[0000] Error response from daemon: Value 'Ubuntu 14.04.1 LTS' is invalid
however, if I use
docker run -d -e constraint:operatingsystem=="Ubuntu*" --name snort glanf/snort
it identifies the host and creates the container.
This is because while checking for the expression in expr.go, the matchstring does not check for whitespaces. This PR fixes this issue.

Coverage remained the same at 39.33% when pulling 25a57e697fae5387c510f5405b1123def6ab9e33 on snrism:master into e1dac69ccea6436fe5ef83402b7479a118613a03 on docker:master.

@snrism can you add a test ? thanks

Coverage decreased (-0.03%) to 39.31% when pulling cffb5373b15be32364faec999112807522b4cce6 on snrism:master into e1dac69ccea6436fe5ef83402b7479a118613a03 on docker:master.

Coverage remained the same at 39.31% when pulling 0c96c883c2014638684fe3d1f8b0991ceb54b195 on snrism:master into 8d82079dffdb603088a2ffddff9f8b25b7ae3a84 on docker:master.

Can you remove the last commit (merge commit) and do a proper rebase ? Thanks!

Oops..lemme fix that

@vieux Sorry..let me open a new pull request with the changes. I think this is messed up..


Update jena-arq, jena-fuseki-main to 4.7.0

Updates

org.apache.jena:jena-arq
org.apache.jena:jena-fuseki-main

from 4.5.0 to 4.7.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.jena" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.apache.jena" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #337.


Fix issues with apt methods (add_package/remove_package)

Use package status from dpkg to determine if a package is installed.
Handle the case where no packages are removed.

Fixes #40.

Code merged, and updated library published!


More than 1000 records

I'm using pyodata to get data from odata service but but I'm getting only the first 1000 records. help me how to get it:
count = theservice.entity_sets.Resources.get_entities().count().execute()
print(count)

7909

BUT
recursos = theservice.entity_sets.Resources.get_entities().skip(100).top(8000).execute()
df2_recursos = pd.DataFrame(columns=['ResourceId', 'ResourceEmailAddress','ResourceName'])
for i,recurso in enumerate(recursos):
        df2_recursos.loc[i] = {'ResourceId': recurso.ResourceId, 'ResourceEmailAddress': recurso.ResourceEmailAddress, 'ResourceName': recurso.ResourceName}

df2_recursos.shape

(1000, 3)

Hi @rafaela-anjosbarbosa , what is the output without skip() and top()?

Hi @rafaela-anjosbarbosa , what is the output without skip() and top()?

recursos = theservice.entity_sets.Resources.get_entities().execute()
df2_recursos = pd.DataFrame(columns=['ResourceId', 'ResourceEmailAddress','ResourceName'])
for i,recurso in enumerate(recursos):
    df2_recursos.loc[i] = {'ResourceId': recurso.ResourceId, 'ResourceEmailAddress': recurso.ResourceEmailAddress, 'ResourceName': recurso.ResourceName}
df2_recursos.shape
(1000, 3)

Interesting. Thank you very much.
I have just pushed some improvements to pyodata logging.
Do you think you can reproduce the request you made in your python code with bin/pyodata? The following example demonstrates how to use it to get the EntitySet Customer from the service https://services.odata.org/V2/Northwind/Northwind.svc/
cd python-pyodata
PYTHONPATH=. bin/pyodata -v https://services.odata.org/V2/Northwind/Northwind.svc/ ENTITY_SET Customers

The output should be the following:
[Initializing HTTP session ...]
[Fetching $metadata ...]
INFO:pyodata.client:Fetching metadata
INFO:pyodata.client:Creating OData Schema (version: 2)
INFO:pyodata.client:Creating OData Service (version: 2)
INFO:pyodata.service:Fetched 20 entities
K CustomerID = ALFKI
+ ContactTitle = Sales Representative
+ Country = Germany
+ ContactName = Maria Anders
+ CompanyName = Alfreds Futterkiste
+ Region =
+ City = Berlin
+ Fax =<PHONE_NUMBER>
+ Phone =<PHONE_NUMBER>
+ PostalCode = 12209
+ Address = Obere Str. 57
--------------------------------------------------------------------------------
...

Where we are interested in the line INFO:pyodata.service:Fetched 20 entities (don't forget that I have added the logging part in the last commit which I pushed few moments ago).

I am afraid that your service just refuses to send more than 1000 records, hence you probably need to fetch the entire entity set per partes:
count = theservice.entity_sets.Resources.get_entities().count().execute()
skip = 100
top = 1000
start = 0
df2_recursos = pd.DataFrame(columns=['ResourceId', 'ResourceEmailAddress','ResourceName'])

while skip < count:
    recursos = theservice.entity_sets.Resources.get_entities().skip(skip).top(top).execute()
    for i,recurso in enumerate(recursos, start=start):
        df2_recursos.loc[i] = {'ResourceId': recurso.ResourceId, 'ResourceEmailAddress':   recurso.ResourceEmailAddress, 'ResourceName': recurso.ResourceName}
     skip = top
     top += 1000
     start += len(recursos)

Something like above could work.

Interesting. Thank you very much.
I have just pushed some improvements to pyodata logging.
Do you think you can reproduce the request you made in your python code with bin/pyodata? The following example demonstrates how to use it to get the EntitySet Customer from the service https://services.odata.org/V2/Northwind/Northwind.svc/
cd python-pyodata
PYTHONPATH=. bin/pyodata -v https://services.odata.org/V2/Northwind/Northwind.svc/ ENTITY_SET Customers

The output should be the following:
[Initializing HTTP session ...]
[Fetching $metadata ...]
INFO:pyodata.client:Fetching metadata
INFO:pyodata.client:Creating OData Schema (version: 2)
INFO:pyodata.client:Creating OData Service (version: 2)
INFO:pyodata.service:Fetched 20 entities
K CustomerID = ALFKI
+ ContactTitle = Sales Representative
+ Country = Germany
+ ContactName = Maria Anders
+ CompanyName = Alfreds Futterkiste
+ Region =
+ City = Berlin
+ Fax =<PHONE_NUMBER>
+ Phone =<PHONE_NUMBER>
+ PostalCode = 12209
+ Address = Obere Str. 57
--------------------------------------------------------------------------------
...

Where we are interested in the line INFO:pyodata.service:Fetched 20 entities (don't forget that I have added the logging part in the last commit which I pushed few moments ago).

How to use when you need authentication?

I am afraid that your service just refuses to send more than 1000 records, hence you probably need to fetch the entire entity set per partes:
count = theservice.entity_sets.Resources.get_entities().count().execute()
skip = 100
top = 1000
start = 0
df2_recursos = pd.DataFrame(columns=['ResourceId', 'ResourceEmailAddress','ResourceName'])

while skip < count:
    recursos = theservice.entity_sets.Resources.get_entities().skip(skip).top(top).execute()
    for i,recurso in enumerate(recursos, start=start):
        df2_recursos.loc[i] = {'ResourceId': recurso.ResourceId, 'ResourceEmailAddress':   recurso.ResourceEmailAddress, 'ResourceName': recurso.ResourceName}
     skip = top
     top += 1000
     start += len(recursos)

Something like above could work.

Same result. = (

How to use when you need authentication?

If HTTP Basic Authentication is enough, you can add the command line parameter --user USERNAME and the tool will ask for password (or you can add --password PASSWORD but that means that the password will be stored in command history).
If you need OAuth or something else, then we cannot use bin/pyodata for debugging.

I am afraid that your service just refuses to send more than 1000 records, hence you probably need to fetch the entire entity set per partes:
count = theservice.entity_sets.Resources.get_entities().count().execute()
skip = 100
top = 1000
start = 0
df2_recursos = pd.DataFrame(columns=['ResourceId', 'ResourceEmailAddress','ResourceName'])

while skip < count:
    recursos = theservice.entity_sets.Resources.get_entities().skip(skip).top(top).execute()
    for i,recurso in enumerate(recursos, start=start):
        df2_recursos.loc[i] = {'ResourceId': recurso.ResourceId, 'ResourceEmailAddress':   recurso.ResourceEmailAddress, 'ResourceName': recurso.ResourceName}
     skip = top
     top += 1000
     start += len(recursos)

Something like above could work.

Same result. = (

It worked!
My failure to indent the code.
Thanks!

It worked!

I tested the code with https://services.odata.org/V2/Northwind/Northwind.svc/Customers?$format=json and it turned out that the value of top must be changed.
The algorithm is the following:
count = theservice.entity_sets.Resources.get_entities().count().execute()
skip = 100
top = 1000
start = 0
df2_recursos = pd.DataFrame(columns=['ResourceId', 'ResourceEmailAddress','ResourceName'])

while skip < count:
    recursos = theservice.entity_sets.Resources.get_entities().skip(skip).top(top).execute()
    for i, recurso in enumerate(recursos, start=start):
        df2_recursos.loc[i] = {'ResourceId': recurso.ResourceId, 'ResourceEmailAddress':   recurso.ResourceEmailAddress, 'ResourceName': recurso.ResourceName}
    skip += top
    start += len(recursos)

My failure to indent the code.

Sorry about that. I wrote that code in my browser without testing and did some typos.


BUG: User set repay to 5% at 1% health, but bot repaid entire loan?

User created a leverage bot:  bot was supposed to repaid as per the parameters in the picture below:

1% Health Level
Repay 5%.
Bot creation: https://etherscan.io/tx/0x8615b0786260539b93618560cb2e8d418363d26e5ab84194aaea45b29fc58cba
Bot repaid leverage here: https://etherscan.io/tx/0x513900231a45a33a8698d30cced44d35a9ef855a674c55027d85af24f277378d
User appeared to lose a good leverage position.

Name
Type
Data

Name
Type
Data

-------------
-------------
-------------

2
collateral	address
0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2

3
debt
uint256

4
N
uint256

5
callbacker
address

5
callback_args
uint256

6	callback_args
uint256
1955657217315385400

8	leverage
uint256
883

9	deleverage_percentage
uint256
500

10	health_threshold
uint256
100

11	expire
uint256
33242514575

12	number_trades
uint256
1

13	interval
uint256
30

Logs from the bot before repayment:
id health health_threshold:  729 0 100. It appears this bot erroneously has set 100 for the repayment threshold
approximently 2 hours ago..
Jan 30 01:42:12 bots-server start.sh[4126489]: id health health_threshold:  729 0 100
Jan 30 01:42:23 bots-server start.sh[4126489]: minRecv:<PHONE_NUMBER>260013305462n
Jan 30 01:42:23 bots-server start.sh[4126489]: minRecv.toString():<PHONE_NUMBER>260013305462
Jan 30 01:42:23 bots-server start.sh[4126489]: tx: {"body":{"messages":["{\"@type\":\"/paloma.wasm.v1beta1.MsgExecuteContract\",\"coins\":[],\"contract\":\"paloma1lwyg9cj80ffrwedgtflcs5uc2g8kjj7kg8s740l3sp8sfz82e9gs2c9rmy\",\"execute_msg\":{\"repay_bot\":{\"bot_info\":[{\"bot\":\"0xE7b97FC7669a6B6633b5F1a4176BD9F9e7f3c09a\",\"callback_args\":[\"1\",\"2206237846118303356\",\"5116555497260013305462\"],\"callbacker\":\"0x9bE82CdDB5c266E010C97e4B1B5B2DF53C16384d\"}]}},\"sender\":\"paloma18efhhzcvskradeqgslmaqgsgxhpaxepz884mn3\"}"],"memo":"","timeout_height":0},"auth_info":{"signer_infos":[{"public_key":"{\"@type\":\"/cosmos.crypto.secp256k1.PubKey\",\"key\":\"AzaXjuN0g0YBveouceO09AjMDiNXurYyhZrlUZdkQauq\"}","sequence":12236,"mode_info":{"single":{"mode":1}}}],"fee":"{\"amount\":[{\"amount\":\"71898\",\"denom\":\"ugrain\"}],\"gas_limit\":\"4793167\",\"granter\":\"\",\"payer\":\"\"}"},"signatures":["dQs214N++72PiTaJRSLxXJuaSAEhrMHl8l0uQAP9+HFGhFxBGFtDJCe+LUu9cjz53W95syBs4ohXup45KaS1tw=="]}

health was 0 and threshhold was 100.. then we sent a repay_bot

Conclusion:

The bot did not use the deleverage_percentage, but repaid the entire loan. This is a bug for @rootedbox.
It's not clear what is the health_threshold of 100 when the user set the Health Threshold for repayment at 1%. @wc117 will you explain this?
@verabehr Did we not already test delverage or is this the first time we are actually testing it in production?
@wc117 the bot appeard to repay the loan even when the price of bitcoin was increasing. Why was the health 0? Is the query for that correct?

Moved to ticket https://github.com/VolumeFi/paloma/issues/1229

noting that we should have repaid at health 1% though not only at 0%


MWPW-136133

Resolves MWPW-136133
https://mwpw-136133--dc--adobecom.hlx.page/acrobat/online/pdf-to-ppt

Codecov Report

Merging #408 (154273c) into stage (9d0e600) will increase coverage by 0.09%.
Report is 8 commits behind head on stage.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##            stage     #408      +/-   ##
==========================================
+ Coverage   93.44%   93.53%   +0.09%
==========================================
  Files          26       26
  Lines        2988     2987       -1
==========================================
+ Hits         2792     2794       +2
+ Misses        196      193       -3

Files
Coverage Δ

acrobat/scripts/scripts.js
96.91% <100.00%> (+0.55%)
:arrow_up:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[C++][Parquet] ParquetFileReader::Contents PIMPL missing a virtual destructor

As ParquetFileReader::Contents  does not have a virtual destructor, the destructors of the child classes, i.e. SerializedFile are not called and thus all member of it leak memory.
Reporter: Uwe Korn / @xhochy
Assignee: Uwe Korn](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=uwe) / @xhochy
Note: This issue was originally created as PARQUET-561. Please see the migration documentation for further details.

Uwe Korn / @xhochy:
PR: https://github.com/apache/parquet-cpp/pull/77

Wes McKinney / @wesm:
Issue resolved by pull request 77
https://github.com/apache/parquet-cpp/pull/77


ZCU104: adas_detection not working with prebuild SD_card image

When I try to run  the VART adas detection demo on the prebuild SD card image I get the following error:
root@xilinx-zcu104-2020_2:~/Vitis-AI/demo/VART/adas_detection# ./adas_detection adas.webm /usr/share/vitis_ai_library/models/yolov3_adas_pruned_0_9/yolov3_adas_pruned_0_9.xmodel
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1226 12:43:46.814553  4316 main.cc:379] create running for subgraph: subgraph_layer0-conv
W1226 12:43:57.409380  4322 xrt_cu.cpp:195] cu timeout! device_core_idx 1  handle=0xaaaaefeecea0 ENV_PARAM(XLNX_DPU_TIMEOUT) 10000 state 1 ERT_CMD_STATE_COMPLETED 4 ms 10042  bo=1 is_done 0
I1226 12:43:57.409515  4322 xrt_cu.cpp:105] Total: 10042876us   ToDriver: 15us  ToCU:<PHONE_NUMBER>4291202us       Complete: 0us Done:<PHONE_NUMBER>us
F1226 12:43:57.409552  4322 dpu_control_xrt_edge.cpp:177] dpu timeout! core_idx = 1
LSTART 18  LEND 16  CSTART 1  CEND 1  SSTART 0  SEND 0  MSTART 0  MEND 0  CYCLE_L<PHONE_NUMBER>  CYCLE_H 322
I found similar reports on the Xilinx forum, but no reply.

Hi @NorbertBeck
The log shows DPU timeout. It's abnormal. Since we have tested it many times and can't reproduce this issue on our side, we need more information.
1 Could you please reboot the board and run the other samples to see if the DPU works normally, such as resnet50 sample. Execute the following command
./resnet50 /usr/share/vitis_ai_library/models/resnet50/resnet50.xmodel
2 Provide the detail steps after you download the zcu104 image. (md5: 308f91cd95f88d0c08fcbccd4272ad00  xilinx-zcu104-dpu-v2020.2-v1.3.0.img.gz)

Hello,
I can confirm that resnet50 is working means the following output is generated
WARNING: Logging before InitGoogleLogging() is written to STDERR
I1229 07:13:56.149976  1201 main.cc:285] create running for subgraph: subgraph_conv1
Image : 001.jpg
top[0] prob = 0.980779  name = brain coral
top[1] prob = 0.008485  name = coral reef
top[2] prob = 0.008485  name = jackfruit, jak, jack
top[3] prob = 0.000542  name = sea urchin
top[4] prob = 0.000422  name = puffer, pufferfish, blowfish, globefish
I verified that the md5sum of the image which I write to SD Card using etcher is correct.
After writing the image I copy the videos/images tarball and extract it in the VART directory.
I do nothing else before launching the commands
I found a similar report here: https://forums.xilinx.com/t5/AI-and-Vitis-AI/CU-timeout-DPU-aborts-while-running-demo/td-p/1203567
Thanks in advance and Best Regards,
Norbert
Von: qianglin-xlnx<EMAIL_ADDRESS>Gesendet: Freitag, 26. Februar 2021 18:48
An: Xilinx/Vitis-AI<EMAIL_ADDRESS>Cc: Beck, Norbert (DI SW STS RTD AT<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [Xilinx/Vitis-AI] ZCU104: adas_detection not working with prebuild SD_card image (#309)
Hi @NorbertBeckhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNorbertBeck&data=04|01|Norbert.Beck%40siemens.com|8dc056a95c534cd43eeb08d8da7ea6f1|38ae3bcd95794fd4addab42e1495d55a|1|0|637499584793884116|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=26offtEBIbdQCuija0pSXy6PvxUDpuPLXh%2FQNPzbroc%3D&reserved=0
The log shows DPU timeout. It's abnormal. Since we have tested it many times and can't reproduce this issue on our side, we need more information.
1 Could you please reboot the board and run the other samples to see if the DPU works normally, such as resnet50 sample. Execute the following command
./resnet50 /usr/share/vitis_ai_library/models/resnet50/resnet50.xmodel
2 Provide the detail steps after you download the zcu104 image. (md5: 308f91cd95f88d0c08fcbccd4272ad00 xilinx-zcu104-dpu-v2020.2-v1.3.0.img.gz)

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FXilinx%2FVitis-AI%2Fissues%2F309%23issuecomment-786796119&data=04|01|Norbert.Beck%40siemens.com|8dc056a95c534cd43eeb08d8da7ea6f1|38ae3bcd95794fd4addab42e1495d55a|1|0|637499584793884116|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=i30o%2B8vvOr7xipdJmY%2FLGxKXEeEUMzSOTPRY6oJsn%2FY%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEVFCOZZ3ZNUWUWNGII4D4DTA7NEVANCNFSM4YIXRSPA&data=04|01|Norbert.Beck%40siemens.com|8dc056a95c534cd43eeb08d8da7ea6f1|38ae3bcd95794fd4addab42e1495d55a|1|0|637499584793894109|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=YxM7Z1Trck9ZOOIGVYQuSuflfRlwW484MpLEHtyBYJk%3D&reserved=0.

Hi @NorbertBeck
I'm sorry, I still can't reproduce the issue on my board.
It looks like a hardware issue, such as power consumption, memory, etc. I'm not sure. Are there any other peripherals connected to the board.  If so, can you temporarily remove them.
Beside, can you run the other video vart samples, such as:
./video_analysis video/structure.webm /usr/share/vitis_ai_library/models/ssd_traffic_pruned_0_9/ssd_traffic_pruned_0_9.xmodel
./segmentation video/traffic.webm /usr/share/vitis_ai_library/models/fpn/fpn.xmodel
Or you can try the following:

change another SD card and tyr again;
Reduce DPU frequency, such as: dpu_clk 80

Hello
video_analysis and segmentation also fail with the cu timeout! Device_core_idx 1
Regarding your proposals:
Re 1.: Currently I do not have another SD card but I will bring one tomorrow
Re 2.: How can I change the dpu_clk when using the prebuild SD image?
Best Regards,
Norbert
From: qianglin-xlnx<EMAIL_ADDRESS>Sent: Montag, 1. März 2021 13:05
To: Xilinx/Vitis-AI<EMAIL_ADDRESS>Cc: Beck, Norbert (DI SW STS RTD AT<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Xilinx/Vitis-AI] ZCU104: adas_detection not working with prebuild SD_card image (#309)
Hi @NorbertBeckhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNorbertBeck&data=04|01|Norbert.Beck%40siemens.com|9d369373d0a24d2ea0bb08d8dcaa39e4|38ae3bcd95794fd4addab42e1495d55a|1|0|637501970959932110|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=%2Bj35bcgnzEdSvDSFrwXqSOI%2BT%2BqJGLDb09USse3j23E%3D&reserved=0
I'm sorry, I still can't reproduce the issue on my board.
It looks like a hardware issue, such as power consumption, memory, etc. I'm not sure. Are there any other peripherals connected to the board. If so, can you temporarily remove them.
Beside, can you run the other video vart samples, such as:
./video_analysis video/structure.webm /usr/share/vitis_ai_library/models/ssd_traffic_pruned_0_9/ssd_traffic_pruned_0_9.xmodel
./segmentation video/traffic.webm /usr/share/vitis_ai_library/models/fpn/fpn.xmodel
Or you can try the following:

change another SD card and tyr again;
Reduce DPU frequency, such as: dpu_clk 80

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FXilinx%2FVitis-AI%2Fissues%2F309%23issuecomment-787897534&data=04|01|Norbert.Beck%40siemens.com|9d369373d0a24d2ea0bb08d8dcaa39e4|38ae3bcd95794fd4addab42e1495d55a|1|0|637501970959942108|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=HdRYo0gJtmUahZr9lGy22MC%2FV6j1Z7BfGzdIkZhvcR0%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAEVFCOYIUP3EJ32VE5SP3ETTBN7GHANCNFSM4YIXRSPA&data=04|01|Norbert.Beck%40siemens.com|9d369373d0a24d2ea0bb08d8dcaa39e4|38ae3bcd95794fd4addab42e1495d55a|1|0|637501970959942108|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=LIMLjS4wzwdWa9dAWuswBv6RHV%2BX6DSazYjGa2yE8mc%3D&reserved=0.

@NorbertBeck
Run the following command to set the DPU clock to 80%
root@xilinx-zcu104-2020_2:~# dpu_clk 80 root@xilinx-zcu104-2020_2:~# dpu_clk Real PL0_CLK 83333333 DPU Performance 83.3% root@xilinx-zcu104-2020_2:~#

re1.: Changing the SD card has no effect
re2: Reducing the DPU frequency has no effect
I suspect that there is something wrong with the display as I get a lot of drm related logs in dmesg after I run the command:
[  791.115077] [drm] Pid 1188 opened device
[  791.115104] [drm] Pid 1188 closed device
[  791.115192] [drm] Pid 1188 opened device
[  791.115202] [drm] Pid 1188 closed device
[  791.118175] [drm] Pid 1188 opened device
[  791.118187] [drm] Pid 1188 closed device
[  791.118201] [drm] Pid 1188 opened device
[  791.118211] [drm] Pid 1188 closed device
[  791.124391] [drm] Pid 1188 opened device
[  791.124525] [drm] Pid 1188 closed device
[  791.142282] [drm] Pid 1188 opened device
[  791.142297] [drm] Pid 1188 closed device
[  791.142324] [drm] Pid 1188 opened device
[  791.151494] [drm] get section DEBUG_IP_LAYOUT err: -22
[  791.151503] [drm] get section AIE_METADATA err: -22
[  791.151529] [drm] zocl_xclbin_read_axlf f0bb3934-5df0-4c3d-ba52-852e904e4245 ret: 0
[  791.155500] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=1
[  791.155534] [drm] No ERT scheduler on MPSoC, using KDS
[  791.155640] [drm] scheduler config ert(0)
[  791.155642] [drm]   cus(2)
[  791.155644] [drm]   slots(16)
[  791.155646] [drm]   num_cu_masks(1)
[  791.155648] [drm]   cu_shift(16)
[  791.155650] [drm]   cu_base(0x80000000)
[  791.155652] [drm]   polling(0)
[  791.155679] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  791.155828] [drm] Pid 1188 opened device
[  791.155842] [drm] Pid 1188 closed device
[  791.155945] [drm] Pid 1188 opened device
[  791.156190] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=1
[  791.156210] [drm] Pid 1188 opened device
[  791.156220] [drm] Pid 1188 closed device
[  791.156461] [drm] Pid 1188 opened device
[  791.156595] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=2
[  791.156616] [drm] Pid 1188 opened device
[  791.156626] [drm] Pid 1188 closed device
[  791.156647] [drm] Pid 1188 opened device
[  791.156702] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=3
[  791.157255] [drm] Pid 1188 opened device
[  791.157265] [drm] Pid 1188 closed device
[  791.157287] [drm] Pid 1188 opened device
[  791.157329] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=4
[  791.237379] [drm] Pid 1188 opened device
[  791.237410] [drm] Pid 1188 closed device
[  791.237454] [drm] Pid 1188 opened device
[  791.237569] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=5
[  791.238128] [drm] Pid 1188 opened device
[  791.238139] [drm] Pid 1188 closed device
[  791.238161] [drm] Pid 1188 opened device
[  791.238205] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=6
[  791.288493] [drm] Pid 1188 opened device
[  791.288525] [drm] Pid 1188 closed device
[  791.288572] [drm] Pid 1188 opened device
[  791.288684] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=7
[  791.289243] [drm] Pid 1188 opened device
[  791.289253] [drm] Pid 1188 closed device
[  791.289275] [drm] Pid 1188 opened device
[  791.289319] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=8
[  791.339270] [drm] Pid 1188 opened device
[  791.339304] [drm] Pid 1188 closed device
[  791.339348] [drm] Pid 1188 opened device
[  791.339466] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=9
[  791.340020] [drm] Pid 1188 opened device
[  791.340031] [drm] Pid 1188 closed device
[  791.340054] [drm] Pid 1188 opened device
[  791.340101] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 locked, ref=10
[  802.036318] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  802.560180] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  803.072177] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  803.584175] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  804.096176] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  804.608175] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  805.120174] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  805.632168] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  806.144170] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  806.656175] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  807.168174] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  807.680175] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  808.192177] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  808.704174] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  809.216165] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  809.728173] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  810.240176] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  810.752174] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  811.264186] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  811.776175] [drm] pid(1188) waiting for outstanding 1 cmds to finish
[  812.288186] [drm:zocl_client_release [zocl]] ERROR Please investigate stale cmds
[  812.288195] [drm] addr 0x80010000, status 0x1
[  812.288198] [drm] addr 0x80000000, status 0x4
[  812.288205] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288210] [drm] Pid 1188 closed device
[  812.288240] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288242] [drm] Pid 1188 closed device
[  812.288257] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288259] [drm] Pid 1188 closed device
[  812.288275] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288277] [drm] Pid 1188 closed device
[  812.288291] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288293] [drm] Pid 1188 closed device
[  812.288306] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288308] [drm] Pid 1188 closed device
[  812.288322] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288324] [drm] Pid 1188 closed device
[  812.288337] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288340] [drm] Pid 1188 closed device
[  812.288346] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.288348] [drm] Pid 1188 closed device
[  812.293688] [drm] bitstream f0bb3934-5df0-4c3d-ba52-852e904e4245 unlocked, ref=0
[  812.293692] [drm] Pid 1188 closed device
[  812.293721] [drm] Pid 1188 closed device
This looks very similar to the report, that I linked earlier:  https://forums.xilinx.com/t5/AI-and-Vitis-AI/CU-timeout-DPU-aborts-while-running-demo/td-p/1203567

hi @NorbertBeck ， could you please try the same command with zcu102 or zcu104 v2021.2 ?

Hi @NorbertBeck
Since we haven't received your reply for a long time, we assume you have solved this issue and I'm going to close it. If you still have any questions, please feel free to reopen it. Thank you very much.


Support semantic token highlighting

Closes #342
How to test
Run the Grammar Extension and assert that the assignments, actions, and return types of grammars are correctly colored.

Not related to this change, but could you fix this as well (should be easy)? When I write Foo returns string: ''; one of the validation rules throws an error.

Not related to this change, but could you fix this as well (should be easy)? When I write Foo returns string: ''; one of the validation rules throws an error.

This was in error in the old isDataType rule function and was accidentally fixed by #341 :)


A way to visualize overall value going up exponentially

As in, captured value of the system (minus cost) goes up in a compounding way. (Assuming captured cells continue to create value per time step.) Presumes some cost of building a new cell.
Would be visualized in a little dashboard graph to the side or something.


Nominating Zsolt Borbely (bzsolt) for Committer status

Hi,
I would like to nominate Zsolt Borbely to becoma a committer. His non-trivial patches are:
#78 Implemented Array.prototype.slice().
#86 Implement Array.prototype.splice().
#99 Implement Object.prototype.propertyIsEnumerable().
#138 Implement String.prototype.slice()
#163 Implement Function.prototype.apply()
#196 Fix the indexing of Array builtin functions.
#321 Implement Function.prototype.bind function
#386 Implement String.prototype.localeCompare function
#530 Implement String.prototype.split function
#729 Add option to enable all-in-one build mode
Any seconds?

+1 (also afaik he also worked on the CBC parts)

+1

If there isn't any other opinions, let's go for next(put his name on committer list).

Added to: https://github.com/Samsung/jerryscript/wiki/Assigned-people


Application Crashing

Viewing the logs from local, it looks like most pages are timing out..  However, I did just see this error pop up:
/app/controllers/news.js:483
4/1/2014 8:59:12 AMweb.1 newsItems.forEach(function (item) {
4/1/2014 8:59:12 AMweb.1 ^
4/1/2014 8:59:12 AMweb.1TypeError: Object # has no method 'forEach'
4/1/2014 8:59:12 AMweb.1 at sortByScore (/app/controllers/news.js:483:13)
4/1/2014 8:59:12 AMweb.1 at /app/controllers/news.js:384:19
4/1/2014 8:59:12 AMweb.1 at Promise. (/app/controllers/votes.js:146:5)
4/1/2014 8:59:12 AMweb.1 at Promise. (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
4/1/2014 8:59:12 AMweb.1 at Promise.EventEmitter.emit (events.js:95:17)
4/1/2014 8:59:12 AMweb.1 at Promise.emit (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:84:38)
4/1/2014 8:59:12 AMweb.1 at Promise.fulfill (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:97:20)
4/1/2014 8:59:12 AMweb.1 at Promise.resolve (/app/node_modules/mongoose/lib/promise.js:108:15)
4/1/2014 8:59:12 AMweb.1 at Promise. (/app/node_modules/mongoose/node_modules/mpromise/lib/promise.js:177:8)
4/1/2014 8:59:12 AMweb.1 at Promise.EventEmitter.emit (events.js:95:17)
4/1/2014 8:59:12 AMweb.1app.js has exited after 3 restarts
4/1/2014 8:59:12 AMweb.1/app/controllers/news.js:483
4/1/2014 8:59:12 AMweb.1 newsItems.forEach(function (item) {

I don't think this is an issue any more, feel free to re-open if I'm wrong.


Cannot return BLOB from created function

There is no way to return a BLOB value from a created function (i.e. db.create_function). There is no call to sqlite3_result_blob. Returning TEXT does not work when there are embedded null bytes in the data.
I implemented a change which is to return BLOB if the encoding of the string is ASCII-8BIT and submitted a pull request. cf. the pull request.
There is a failure in the Travis integration test, but I can build and run the tests with Ruby 1.8.7 locally so I don't understand the issue there.

What can I do to get this fix accepted and merged? Should I prepare a test case to show the issue, and a test to show that it is fixed?
For example:
require 'sqlite3'
require 'base64'

db = SQLite3::Database.new("test.db");

db.create_function("echo", 1) do |func, str|
    func.result = str.force_encoding('ASCII-8BIT') # return BLOB -- may have embedded null bytes
end

text = "hello\u0000world"
puts db.execute("select ?", text)[0][0].bytes.inspect
puts db.execute("select echo(?)", text)[0][0].bytes.inspect
puts db.execute("select echo(echo(?))", text)[0][0].bytes.inspect

blob = "hello\u0000world".force_encoding('ASCII-8BIT')
puts db.execute("select ?", blob)[0][0].bytes.inspect
puts db.execute("select echo(?)", blob)[0][0].bytes.inspect
puts db.execute("select echo(echo(?))", blob)[0][0].bytes.inspect

db.close

The broken output is:
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]
[104, 101, 108, 108, 111]
[104, 101, 108, 108, 111]
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]
[104, 101, 108, 108, 111]

The null byte causes the data to be truncated. It's not apparent in the trivial case, but just work with the value in the SQL a bit, and you'll see where SQLite3 is mislead because it sees the output of the user-defined function as TEXT. A simple test of feeding the result back into the function one extra time shows the problem clearly. The last line of output should still be "[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]".

Also, can anybody help me with the Travis test that fails? I can't reproduce this on my own system -- I don't know how. I can run all tests in Ruby 1.8.7 from the repo.

I think this was fixed with 220c1947976770a0a12401a467899b79f1900640 and 1.8 tests were fixed with c204cb9fbf8bf99e8b239c3365108204ba2914f8

Yes, I just tried the sample ruby above with the fix gem, and the output is now correct:
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]
[104, 101, 108, 108, 111]
[104, 101, 108, 108, 111]
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]
[104, 101, 108, 108, 111, 0, 119, 111, 114, 108, 100]


Opening links on Safari with Adblock has a long delay

And for some reason whitelisting the website does not work too. Everything works well on Chrome however.
Perhaps we can rewrite the functions for catching link presses to fix this.

It's not really a bug. Adblock is blocking requests to GA, so the callback (for opening links) is called after a timeout.
The solution for this would be removing the async callback, and open the new tab right after the GA call is made. It would be pretty similar to how GA calls are made on client/containers/SearchBar.jsx, on the onSuggestionSelected function.

Thanks @nglgzz 💚


parametirize the repo path

Got my gitlab on /, and I want it on a diffrerent partition, say /data. going over the code I don't see a way to pass that parameter to the omnibus. I'd move and symlink it, but gitlab would not run on a path with any part of the path being a symlink.
On that matter, can I get the entire /var/opt/gitlab move into /opt/gitlab/githome or any random path as needed?

Do you have some more details here? Documentation to the Gitlab Omnibus configuration parameter for that? What parameter are you looking for?

Here you are: https://github.com/vshn/puppet-gitlab/blob/master/manifests/init.pp#L101
And here: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/629def0a7a26e7c2326566f0758d4a27857b52a3/README.md#storing-git-data-in-an-alternative-directory

Oh duh. I was grepping for "repos_path"... Sorry.


Bulk Deletion of Circuits Fails

Environment

Nautobot version (Docker tag too if applicable): 1.4.4
Python version: 3.9
Database platform, version: Postgres, 13
Middleware(s):

Steps to Reproduce

Create a bunch of circuits (ping me, I have a script that will do so)
Navigate to Circuits in UI, select all of the circuits
Attempt to bulk delete
Get message back that no circuits were selected

Expected Behavior
Deleted circuits

Observed Behavior
No circuits deleted

Note, when trying to delete the first screen of circuits (not selecting the additional button) all of the circuits will delete just fine.

https://user-images.githubusercontent.com/22228848/193711920-dd9fa786-a1fb-403c-9d7f-11226f7bd9d9.mov

I was able to reproduce this.

"Regular" bulk delete done by clicking the checkbox to select all circuits, works as expected.
"Global" bulk delete done by checking the additional checkbox to "Select all X circuits matching query" that appears at the top of the list view does not work and results in the "No circuits were selected for bulk_destroy".

It appears that the value of the _all checkbox is not being properly handled in the NautobotViewSet code, specifically in nautobot.core.views.mixins.ObjectBulkDestroyViewMixin.perform_bulk_destroy().

CC @HanlinMiao


Staveless runes: find better character to represent "b"

The "b" rune uses simple comma as a placeholder. Should find better alternative.
Dig deep: https://en.wikipedia.org/wiki/List_of_Unicode_characters

Maybe "Modifier Letter Low Acute Accent", if works independently


Actualize data

[x] Download all maps by single download functional.
[x] Download all maps by multiple download functional.
[x] Correct mistakes in Seed data for Data Base.

Done


Add support for target attribute on base tag

Fixes #404

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

@cwelch5 I'm good with this one, thoughts?


Allow fileending *.h for mocked classes

Is your feature request related to a problem? Please describe.
Currently I am playing with FSeam. And in my test project I use the fileending *.h for header files.
E.g. I have the class component2 which shall be mocked for class component1. And When I compile the tests, I get the errormessage:
Traceback (most recent call last):
  File "/usr/local/bin/FSeamerFile.py", line 490, in <module>
    generateFSeamFile(_args[0], _args[1], _forceGeneration)
  File "/usr/local/bin/FSeamerFile.py", line 452, in generateFSeamFile
    raise NameError("Error file " + filePath + " is not a .hh file")
NameError: Error file /workspaces/Basic_Cpp_Project/tests/component1/../../application/component2/component2.h is not a .hh file

The CMakeLists.txt of the tests contains the test:
addFSeamTests(
        DESTINATION_TARGET component1Tests
        TARGET_AS_SOURCE component2
        TST_SRC
                ${CMAKE_CURRENT_SOURCE_DIR}/component1Tests.cpp
        TO_MOCK
                ${CMAKE_CURRENT_SOURCE_DIR}/../../application/component2/component2.h
)

When I change the name of the file component2.h to component2.hpp, then the error doesn't appear.
Describe the solution you'd like
Because of that this framework shall be used with ancient legacy code, and *.h is a very often fileending for header files, it would be nice if you would disable the filter for the filename of the headerfiles.

Hello,
Will do the change right away. I may also add a way to register manually any type of extension file to handle in the future.

Sounds good. I will test it on the weekend.

Did you give it a try?

Hi sorry for the very late reply,
yes I have tried it and yes now the fileending .h works.


logstash add directory and file into container,  the owner is root , not logstash, cause logstash has no permission to execute pipeline

Problem description
logstash add directory and file into container,  the owner is root , not logstash, cause logstash has no permission to execute pipeline
Extra information
Stack configuration
ELK_VERSION = 7.6.0
ARG ELK_VERSION

# https://www.docker.elastic.co/
FROM docker.elastic.co/logstash/logstash:${ELK_VERSION}

COPY mysql mysql
COPY test test

Docker setup
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:27:04 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:25:42 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

docker-compose version 1.25.5, build 8a1c60f6
docker-py version: 4.1.0
CPython version: 3.7.5
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

Docker logs
logstash_1       | 2020-05-08T15:27:31.697921977Z [2020-05-08T15:27:31,697][ERROR][logstash.javapipeline    ][main] Pipeline aborted due to error {:pipeline_id=>"main", :exception=>#<Errno::EACCES: Permission denied - /usr/share/logstash/test/user.txt>, :backtrace=>["org/jruby/RubyFile.java:1295:in `delete'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-integration-jdbc-5.0.0/lib/logstash/plugin_mixins/jdbc/value_tracking.rb:112:in `clean'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-integration-jdbc-5.0.0/lib/logstash/plugin_mixins/jdbc/value_tracking.rb:56:in `common_set_initial'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-integration-jdbc-5.0.0/lib/logstash/plugin_mixins/jdbc/value_tracking.rb:65:in `set_initial'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-integration-jdbc-5.0.0/lib/logstash/plugin_mixins/jdbc/value_tracking.rb:34:in `initialize'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-integration-jdbc-5.0.0/lib/logstash/plugin_mixins/jdbc/value_tracking.rb:18:in `build_last_value_tracker'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-integration-jdbc-5.0.0/lib/logstash/inputs/jdbc.rb:240:in `register'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:200:in `block in register_plugins'", "org/jruby/RubyArray.java:1814:in `each'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:199:in `register_plugins'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:310:in `start_inputs'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:270:in `start_workers'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:154:in `run'", "/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:109:in `block in start'"], "pipeline.sources"=>["/usr/share/logstash/pipeline/logstash.conf", "/usr/share/logstash/pipeline/test-user.conf"], :thread=>"#<Thread:0x6aa0d005 run>"}
logstash_1       | 2020-05-08T15:27:31.706244026Z [2020-05-08T15:27:31,705][ERROR][logstash.agent           ] Failed to execute action {:id=>:main, :action_type=>LogStash::ConvergeResult::FailedAction, :message=>"Could not execute action: PipelineAction::Create<main>, action_result: false", :backtrace=>nil}

Extra info
[vagrant@localhost docker-elk]$ docker exec -it b2851e8fc6f1 /bin/bash
bash-4.2$
bash-4.2$
bash-4.2$ ls -l
total 524
drwxrwsr-x. 2 logstash root       4096 Feb  6 01:51 bin
drwxrwsr-x. 1 logstash root        142 Feb  6 01:51 config
-rw-rw-r--. 1 logstash root       2276 Feb  6 01:43 CONTRIBUTORS
drwxrwsr-x. 1 logstash root         69 May  5 15:56 data
-rw-rw-r--. 1 logstash root       4028 Feb  6 01:44 Gemfile
-rw-rw-r--. 1 logstash root      22676 Feb  6 01:45 Gemfile.lock
drwxrwsr-x. 6 logstash root         84 Feb  6 01:51 lib
-rw-rw-r--. 1 logstash root      13675 Feb  6 01:43 LICENSE.txt
drwxrwsr-x. 4 logstash root         90 Feb  6 01:51 logstash-core
drwxrwsr-x. 3 logstash root         86 Feb  6 01:51 logstash-core-plugin-api
drwxrwsr-x. 4 logstash root         55 Feb  6 01:51 modules
drwxr-sr-x. 2 root     root         45 May  5 15:50 mysql
-rw-rw-r--. 1 logstash root     480537 Feb  6 01:43 NOTICE.TXT
drwxrwxr-x. 2 logstash logstash     27 May  8 15:33 pipeline
drwxr-sr-x. 2 root     root         22 May  5 15:50 test
drwxrwsr-x. 3 logstash root         30 Feb  6 01:51 tools
drwxrwsr-x. 4 logstash root         33 Feb  6 01:51 vendor
drwxrwsr-x. 9 logstash root        193 Feb  6 01:51 x-pack

you can see the mysql & test directory's owner are root , not logstash.

COPY --chown=logstash mysql mysql is what you need here.
https://docs.docker.com/engine/reference/builder/#copy

rebuild the image, docker build logstash, not working, still is root:root

the strange thing is , same command works fine on elasticsearch, not using --chown option, why logstash has this issue?

Works perfectly fine for me:
$ docker-compose exec logstash ls -l
total 568
drwxrwsr-x 2 logstash root       4096 Mar 26 09:01 bin
drwxrwsr-x 1 logstash root       4096 Mar 26 09:02 config
-rw-rw-r-- 1 logstash root       2276 Mar 26 08:51 CONTRIBUTORS
drwxrwsr-x 2 logstash root       4096 Mar 26 08:51 data
-rw-rw-r-- 1 logstash root       4028 Mar 26 08:53 Gemfile
-rw-rw-r-- 1 logstash root      22676 Mar 26 08:53 Gemfile.lock
drwxrwsr-x 6 logstash root       4096 Mar 26 09:01 lib
-rw-rw-r-- 1 logstash root      13675 Mar 26 08:51 LICENSE.txt
drwxrwsr-x 4 logstash root       4096 Mar 26 09:01 logstash-core
drwxrwsr-x 3 logstash root       4096 Mar 26 09:01 logstash-core-plugin-api
drwxrwsr-x 4 logstash root       4096 Mar 26 09:01 modules
drwxr-sr-x 2 logstash logstash   4096 May  8 16:24 mysql    <------------------- owned by logstash
-rw-rw-r-- 1 logstash root     480537 Mar 26 08:51 NOTICE.TXT
drwxr-xr-x 2 logstash logstash   4096 Apr 21 07:30 pipeline
drwxrwsr-x 3 logstash root       4096 Mar 26 09:01 tools
drwxrwsr-x 4 logstash root       4096 Mar 26 09:01 vendor
drwxrwsr-x 9 logstash root       4096 Mar 26 09:01 x-pack

$ ls -l logstash
total 16
drwxr-xr-x 2 acotten acotten 4096 Apr 21 09:30 config
drwxr-xr-x 2 acotten acotten 4096 May  8 18:22 mysql
drwxr-xr-x 2 acotten acotten 4096 Apr 21 09:30 pipeline
-rw-r--r-- 1 acotten acotten  241 May  8 18:21 Dockerfile

diff --git a/logstash/Dockerfile b/logstash/Dockerfile
index 6a444e7..f71e6c8 100644
--- a/logstash/Dockerfile
+++ b/logstash/Dockerfile
@@ -5,3 +5,5 @@ FROM docker.elastic.co/logstash/logstash:${ELK_VERSION}

 # Add your logstash plugins setup here
 # Example: RUN logstash-plugin install logstash-filter-json
+
+COPY --chown=logstash mysql mysql

You need to run docker-compose build logstash, not docker build logstash. Not sure if that's what you meant.

[vagrant@localhost docker-elk]$ docker-compose build logstash
Building logstash
Step 1/4 : ARG ELK_VERSION
Step 2/4 : FROM docker.elastic.co/logstash/logstash:${ELK_VERSION}
 ---> 799d4bde3bdd
Step 3/4 : COPY --chown=logstash mysql mysql
 ---> Using cache
 ---> b9e41e367033
Step 4/4 : COPY --chown=logstash test test
 ---> Using cache
 ---> 20dd233b4cda
Successfully built 20dd233b4cda

could it be cache? how to disable cache, or build a new one?

I think your cache is working just fine. You need to recreate the container with docker-compose up, that's it.

thank you so much, run docker-compose down, then docker-compose up, problem solved.
and btw,  the strange thing is , same command works fine on elasticsearch, not using --chown option, why logstash has this issue?

My guess is that the Elasticsearch container runs with the root GID (Dockerfile), whereas the Logstash container runs with the user's GID, which is logstash (1000) in this case (Dockerfile).


Proposal: Move references to definitions or $defs

In ref.json:
https://github.com/json-schema-org/JSON-Schema-Test-Suite/blob/master/tests/draft7/ref.json#L78

Closed in #433. Thanks!


Option to use TLSv1.2 instead of TLSv1.3

Is your feature request related to a problem? Please describe.
Not a problem with nginx-proxy-manager, but Home Assistant and SmartThings integration not working with TLSv1.3.
Describe the solution you'd like
Option use TLSv1.2 instead of 1.3 under settings for any given proxy-host.
Describe alternatives you've considered
I tried to add ssl_protocols TLSv1.2; to the "Custom Nginx Configuration" section under Advanced for a given proxy-host but the result is that TLSv1.3 is still used.
Additional context
https://www.home-assistant.io/integrations/smartthings/#webhook-troubleshooting-checklist

It looks like this is an issue with nginx itself.
A workaround would be to set all of your sites to v1.2.  You can do that by modifying the ssl_protocols portion of the /etx/nginx/conf.d/include/ssl-ciphers.conf file in the app container.


idea - nether waypoint copy

say you have a waypoint in the overworld there would be a button in ur edit section that lets you make a copy of your waypoint for the nether auto changes the cords for you.

I recommend using the Prefer Overworld Waypoints setting in XaeroPlus.
it will make it so waypoints are shown in both OW/nether and but stored only in overworld coordinates. so it kinda prevents this problem from occurring in the first place.
i'll leave this feature request issue open but i probably won't get to it anytime soon


how to prevent accelerate from concatenating tensors in batch?

My collate_fn in dataloader returns a list of image tensors with different height and width. After using accelerator.prepare(model, optimizer, dataloader), I noticed that accelerate seems to automatically concatenate the tensors during for step, batch in enumerate(train_dataloader) iteration, and the size-mismatch leads to Exceptions.
Is there any parameter to prevent the auto-concatenating?
Or, should I remove dataloader from accelerator.prepare params?

You need to remove it, or try setting dispatch_batches=False in the Accelerator() init.

You need to remove it, or try setting dispatch_batches=False in the Accelerator() init.

Seems dispatch_batches=False works. While it's still bewildering me that some elements returned now are wrapped with an additional list ... maybe there's still bug in my code? Anyway there's no information lost so I currently solve the problem by adding a [0] index to them

You need to remove it, or try setting dispatch_batches=False in the Accelerator() init.

both methods work. thanks


Another C1202: recursive problem in VS2017

Hi,
I'm trying to use lua sol for not so long and i like it. But i get few problem and didnt find solution for almost few days. So i'm here.
I got two strange problem, so i split them in separate issues.
I use qt creator + mingw and it is compile correctly, but when i go to
qt creator + VS2017 compiler i've got the following problem.
C1202: recursive type or function dependency context too complex
in the following place of my code
        lua_.new_simple_usertype<Flags::flag2>                 (                     "flag",                     sol::meta_function::multiplication, sol::resolve<Flags::flag2(const Flags::flag2&, const Flags::flag2&)>(&Flags::operator*)                 );
with error in this place in sol.hpp
template <typename F, typename U = meta::unqualified_t<F>>                 inline constexpr auto resolve_f(std::true_type, F&& f)                         -> decltype(resolve_i(types<meta::function_signature_t<decltype(&U::operator())>>(), std::forward<F>(f))) {                         return resolve_i(types<meta::function_signature_t<decltype(&U::operator())>>(), std::forward<F>(f));                 }
As you can see, there is only one operator overload, and it fail. I'm trying to reproduce this error with almost the same class in test project but it's compile.
I know its impossible to propose solution by this, but maby i miss somthing and there was an issue like this or documentation says what to do. I will keep trying to localize the core of the problem.
Thanks for any advice, and sorry for my english.

Remove the resolve, or use an explicit static cast to a member function (this is a member function, right?).

Hi! Your so fast to responde. I shoul say i'm fun of sol once again!
Nope, operators were overloaded out of class
flag2 operator!(const flag2 &f); flag2 operator*(const flag2 &f1, const flag2 &f2); flag2 operator+(const flag2 &f1, const flag2 &f2); flag2 operator-(const flag2 &f1, const flag2 &f2);
Sorry, i dont get about static cast. There is no member overload of operators.

Try:
lua_.new_simple_usertype<Flags::flag2> ( "flag",
     sol::meta_function::multiplication, static_cast<Flags::flag2(*)(const Flags::flag2&, const Flags::flag2&)>(&Flags::operator*)
);

Or something like that.

Wow, its compile!
But what this code actually do? And why resolve didnt help?

Who knows; MSVC is weird, but resolve is even more weird and is only meant to be one tool used. I should add some docs about using static_cast when resolve fails.
Either way, it takes the name &Flags2::operator* and explicitly requests that it be turned into a known function pointer. sol2 knows what to do with a function pointer, so it works.

Amazing!
I test another places with the same error and they too worked!
Thank a lot!


Enforce ID.me verification in order to request mentorship

Feature
Why is this feature being added?

Our site stipulates:

In order to take advantage of resources such as Mentorship and Scholarships, we require that you verify your military affiliation status. We use Id.Me for verification, a highly secure and specialized platform that will protect your information.

However, this is not enforced.  A non-verified (potentially non-veteran) user can request mentorship through the airtable form.
This puts the mentors in the uncomfortable position of inquiring if their mentees are, in fact, veterans.
What should your feature do?
The Request a mentor link should only be available/clickable for verified users:

I'd also like to see ID.me status used to determine whether a new member gets a link to the Airtable Mentor Request form in their welcome email.  If someone is not verified, if we go down this route, we wouldn't want to share the link with them


I am getting this error when i try to download.

Command I had entered:
anime dl --episodes 78:102 --download-dir D:\Harsh http://kissanime.ru/Anime/Fairy-Tail-2014-Dub

I have released a bug fix version. Can you please try it out and report back?
pip install -U anime-downloader[cloudflare]

You have to install with cloudflare support if you want kissanime to be supported. If clouflare is not available, it will just search using that url.
I would suggest using 9anime, because it would be faster and is more tested. (Search is available using 9anime)

Okay so this was weird. I uninstalled the normal one with this cloudfare supported one. After installing it gave a weird message saying anime-downloader 2.4.1 didn't support cloudfare even though i had pasted the exact same code. Nevertheless I tried downloading through 9anime but it gave another error saying 'No connection adapters were found for [URL]'. So I instead tried using KissAnime and well instead of using that link it showed me a bunch of different anime and movies(though all of them were related to the anime whose link i had originally tried to search..in this case Fairy Tail). I chose the one I wanted. Another thing is that all these options were definitely from 9anime( Kissanime calls it Fairy Tail 2014 while 9anime calls it Fairy Tail Series 2 or something and i got the latter as an option). And it worked. Still it's a bummer it didn't use KissAnime since 9anime(which I'm guessing uses playercdn or something) has like 1.5x bigger video file sizes for the exact same quality as compared to KissAnime(which uses RapidVideo).
TL;DR - Not working when directly tried 9anime but when trying Kissanime it instead uses 9anime.
Sorry for the long read. Thanks for all the effort you've made trying to make this but the bigger file sizes of 9anime can be a real downer, especially when downloading whole anime seasons.

Okay. So yeah, this was indeed weird. Can you paste the traceback or the error you received when trying to download directly from 9anime? Also use -ll DEBUG argument while you are at it.
BTW, this tool downloads uses rapidvideo servers for both 9anime and kissanime.
Also I know this is too much to ask, but can you run the following commands and paste their results?
anime dl http://kissanime.ru/Anime/Kochin-Pa --url -ll DEBUG

anime dl https://www5.9anime.is/watch/steinsgate.1rx --url -ll DEBUG

This is what I get from trying to download directly via 9anime. Sorry I couldn't properly use -11 DEBUG as you can see.

This is after trying out the KochinPa command. I entered 3 when it asked me to choose since that looked the most similar.

After that it started downloading the URLs properly

Hmm it worked properly this time even with 9anime. Could I know what you did differently that it worked now while it didn't for me?

From what I can see the two things different were that your 9anime link doesnt have the weird number that changes for every episode which it usually does since 9anime directly opens up an episode instead of some kind of anime page. Also your link is a ww5.9anime while i was using ww6.9anime.

Hmm. Seems like 9anime worked. I didn't change anything. Perhaps you could share what url you were trying?
As for kissanime, can you do, python -c "import cfscrape" and paste the output. If I had to guess, I think it is because you don't have node js installed, which is a dependency for cfscrape.
As for -ll, you have to use the alphabet l not the number 1 (I know some monospace fonts can be confusing :P).

From what I can see the two things different were that your 9anime link doesnt have the weird number that changes for every episode which it usually does since 9anime directly opens up an episode instead of some kind of anime page. Also your link is a ww5.9anime while i was using ww6.9anime.

It shouldn't matter, if I remember correctly. If you could share the url, I can try it on my machine.

Also its working now, that my w6.9anime link i.e. Guess I was making some noobish mistake. Sorry :P
Though Kissanime links still redirect to 9anime, but ive realized the file sizes are only small for Fairy Tail, and even then the quality is drastically low as compared to 9anime. Sorry again for arguing about that. 9anime is good as any other.

Ah. Good to know it's working. :)
I'll close this issue now. If you run into anything else, feel free to open an issue.

Also, if you still want kissanime, you can do pip install cfscrape and make sure you have node-js installed.

Thanks for that. I'll keep that in mind. And I'm so sorry again for all this ruckus. In the end it was probably some noobish mistake i made. Maybe your updated 2.4.1 version fixed it but i doubt that. Thanks a lot for bearing with me man.


Possible Enhancement: Schedule deployment to environments

The ask would be to be able to schedule a deployment action based on environment. This would be important, if you want to deploy PTEs into production environments, since you don't want to deploy them when users are in the system.
I am not sure what the best way would be, but one possibility would be to separate the Deploy into "Deploy" and "Deploy Production" and "hardcode" the "Deploy Production" to run only for "(Production)" environments. Then allow the definition of a cron schedule in the settings file, like it is possible for Current, NextMinor, and NextMajor. The problem with this approach would be that it would always deploy, but maybe that's not a big deal - as soon as the release turns from a "preview" into a release, it could be deployed.
Not sure, if this could also be a property of the environment where you can define "run hours".
The main issue is, in my eyes, that we would have a lot of scheduled jobs running or consuming minutes just to check, if something needs to be published or not.
Don't know, if you can define "on release creation after a certain time" (aka, execute deploy when a new release is created (not preview) and run the action after 6 pm).
Currently, I am using an outside tool that triggers the execution of a workflow through the GitHub API and it's manageable, but it would be great to have this all within GitHub/AL-Go and I would think that this could be useful for partners.

The on schedule trigger in GitHub only allows us to make workflows, which are triggered repeatedly, following this syntax: https://crontab.guru/
We have discussed many solutions to this problem:

Allow DevOps pipelines to publish the app to an environment without installing it and schedule the install of an app inside Business Central.
Allow Business Central to directly pull the new version from a NuGet package created from your workflows.
Allow creation of a specific publish workflow for a production environment, which would trigger during "run hours" and publish if a new version was released. These workflows would be disabled after the version was deployed and enabled again by the release workflow.
Investigate whether a tool like https://posthook.io could be used easily to have an external service trigger a workflow run in your repository with a defined set of parameters.

Will move the suggestion to the backlog and investigate close when time allows.


Navigation Improvements

Replaces BottomAppBar with BottomNavigationView.
Reworks app-wide navigation for easier usage.
Adds ActionBar to handle back navigation from top level menu items.
Minor improvements.

I am aware of the hidden back button that was previously at the bottom bar. The BottomAppBar has been replaced with a BottomNavigationView which functions differently. The navigation change requested involved removing it from the bottom and having it at the top as is. Check here.

Which back button are you referring to? The one in the actionbar?

As for the fonts, you can go ahead and make the update.

@alexosugo

Yes I understand the changes on the BottomNavigation which works really great.

Yes the back button on action bar. From the notion doc "Please add the back navigation arrows back to the top left corner of the relevant cards"; Instead of creating a back navigation, it's meant to be inside the StaxNavCard, which already exists but has default of GONE visibility.

Sawa Sawa

Nav isn't working for me, pressing e.g. Balances from the send money screen goes home instead of to balances. This branch also causes text input placeholders to be black. Finally, the back arrow should def go in the card, having it outside is really weird.

New changes looks good codebase wise. However, there are 3 functional issues.

Back buttons closes the app, instead of going to the previous screen. I  guess this is caused when activity.finish was added to the nav logic.

Summary cards and Link account card does not show the back button

This bounty screen has a margin space between content and bottom nav. Also active item on nav is home instead of settings

@alexosugo Still one issue: When you go to a view that isn't in the global nav such as send money or the bounty list then it's parent shouldn't be highlighted in the nav and tapping it's parent option in the global nav should take you to that parent page. So for example if I'm on send money, the home nav should not be blue and pressing it should take me home.

also missing back from new request


Truly fix the colors

While the current colors look good, they don't exactly match the spec which happens to mess up vim.
My refactor commit which converts colors from an array to object helps clarify the discrepancy from the spec. (the default Hyperterm config now uses a color object) It helps clarify the problem because the colors in this theme are now named according to the terminal color names.
Below is the spec table. The br... colors correspond to light... colors in the color object. This is because generally the lighter colors are used as text highlights (or background).

#2 only fixed the colors partially. The reason it fixed it for him is because he is using let g:solarized_termtrans = 1 which should not be needed when the terminal is using the correct solarized colors.
Before

After

This is great! I've been meaning to fix this for a while. Thanks for contributing 👍


[move] Bug fixes and improvements for move-analyzer v0.0.2

This fixes a few issues in the Move VS Code extension:

For one thing, it turns out VS Code only performs some validations when publishing an extension, and not when packing it. This means our current CI missed a few issues, like the fact that we have a invalid version number, 0.0.1-dev. rust-analyzer also uses a -dev suffix in their package file, but strips it out before publishing. This pull request removes the suffix.
@tnowacki pointed out a few issues with hexadecimal number matching, this fixes that.
I also improved hex string matching, x"zzz" matches the zs as invalid characters now.

In addition to the above changes, I bumped the version number for the next release, from 0.0.1 to 0.0.2.

/land