pip install not working due to cuda.h missing error

I have tried pip install pytorch-fft, on two different machines with gpus, and on both I am getting this error:
venv/local/lib/python2.7/site-packages/torch/utils/ffi/../../lib/include/THC/THCGeneral.h:9:18: fatal error: cuda.h: No such file or directory
I tried python 2.7 and 3.6. I also tried to install without using a virtual environment.
P.S.: I first got the error which says the package cffi was missing. I installed that package, and now I am getting this error.
I would appreciate your help!

I had the same issue. I resolved it by exporting some environmental variables:
$ export C_INCLUDE_PATH=${CUDA_HOME}/include:${C_INCLUDE_PATH}
$ export LIBRARY_PATH=${CUDA_HOME}/lib64:$LIBRARY_PATH
$ pip install pytorch-fft

@ycemsubakan hi, could you tell me how did you create this soft link? I tried as:
sudo ln -s /usr/local/cuda-8.0/  /usr/local/cuda/
then a symbolic linkof cuda-8.0 is created under cuda, which means the path to cuda is /usr/local/cuda/cuda-8.0. So the system can't find the correct path.
In my .bahsrc I have set:
$ export PATH="/usr/local/cuda/cuda-8.0/bin:$PATH"
$ export LD_LIBRARY_PATH="/usr/local/cuda/cuda-8.0/lib64:$LIBRARY_PATH"
And it works well such as with tensorflow-gpu.
I'have been being annoyed by this error for days :(

@ycemsubakan , how did you create the soft link? can you give the command please?

the fix for me was to install sudo apt-get install nvidia-cuda-toolkit after sudo apt-get install -y cuda-9.0
all steps from here :
<EMAIL_ADDRESS>and here (change to 3.0.4) :
https://kezunlin.me/post/dacc4196/
now pycuda works (for tensorrt 3.0.4 tar file install on ubuntu 16.04 - cuda 9.0 deb - cudnn 7.0.5 deb)

Could not find any cudnn.h matching version '7' in any subdirectory:
''
'include'
'include/cuda'
'include/*-linux-gnu'
'extras/CUPTI/include'
'include/cuda/CUPTI'
of:
'C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1'
Asking for detailed CUDA configuration..
same error please help

@ycemsubakan , how did you create the soft link? can you give the command please?
Here you go after whole 2 years...!!!
sudo ln -s /usr/local/cuda/ /usr/local/cuda-8.0/

I had the same issue. I resolved it by exporting some environmental variables:
$ export C_INCLUDE_PATH=${CUDA_HOME}/include:${C_INCLUDE_PATH}
$ export LIBRARY_PATH=${CUDA_HOME}/lib64:$LIBRARY_PATH
$ pip install pytorch-fft

Additional, you must set CUDA_HOME and add it to $PATH.
export CUDA_HOME=/usr/local/cuda
export PATH=${PATH}:${CUDA_HOME}/bin


Correct Employee Naming

Example:

Earnest instead of Ernest

Name misnamed in the DB.
NB: In future, User will be able to edit their information.


Add mig-controller deployment role

Based on https://github.com/fusor/mig-controller#mig-controller deployment instructions.
These roles will :

Prepare the destination cluster (OCP4)
Deploy the controller on the hosting cluster (OCP3)
Validate the controller is available on hosting cluster (OCP3)
Dump a summary of the deployment into a variables file to be ingested by test jobs that need to create the appropiate CRs (mig-e2e)

Note:

A logged in session on the hosting cluster (OCP3) is required
Mig controller requires velero to be deployed on both clusters

@fbladilo
We are assuming that the OCP 4 cluster will be the location that the mig-controller is installed.
Technically I think this should work for either cluster, but the normal customer workflow expects:

Customer discovers migration tooling from OperatorHub and installs on OCP 4 cluster
this will install mig-controller and Velero as a pre-requisite onto the OCP 4 cluster
Customer installs Velero on their OCP 3 cluster.
Customer performs migration from OCP 3 to OCP 4.

Just wanted to be sure you were aware, from the original comment sounded like you were using OCP 3 for the cluster to install mig-controller on.

@jwmatthews Yep I'm aware, it could go actually either way, I chose OCP3 to host mig-controller by default for CI purposes but can be easily reversed.


Fix Ci, add go 1.11 to travis and fix linter issues

Coverage remained the same at 100.0% when pulling 459dade6fb4dfa0b9b9c6c74d0dced315e70e509 on hanzei:ci into 3c1074078d32d767e08ab2c8564867292da86926 on blang:master.

@blang ping. If you want, I can try help you merging some of the PRs.

@blang This should be ready to merge.

Thanks for the patience. LGTM


feat: Check that cosign.pub matches private key

This avoids images which can't be updated due to invalid signature errors because cosign.pub doesn't match the private key actually used for signing. The error is caught early in the build process as there's no point creating an image if cosign.pub is wrong.

The error is caught early in the build process as there's no point creating an image if cosign.pub is wrong.

I initially thought that this would make more sense in signing.sh (since this error is rpm-ostree specific and signing.sh can be easily disabled if building for something else), but I guess this reasoning makes sense and this should benefit everyone.

@xynydev I've added the conditionals back in and have made the check output more descriptive. PTAL.

Thanks @mjs , approved. Just resolve the merge conflicts, would ya?

@xynydev Conflicts resolved. A workflow approval is needed to run the actions.

This change breaks my builds with this error:
Run echo "Checking for difference between public key from SIGNING_SECRET and cosign.pub"
Checking for difference between public key from SIGNING_SECRET and cosign.pub
Error: Process completed with exit code 1.

Edit: I replaced public & secret key with the new one & now it works.

Sounds like you may have had a genuine issue with the keys not matching up?

@mjs multiple people have now reported this same problem on the Discord, everything works for me, but we'll have to revert the change ASAP if we can't figure out what's wrong.

Update: @mjs this was my fault. The webui previously let the user to create a cosign.pub without a trailing newline, whereas it is supposed to have one (just like any other plaintext file, really).
Adding a trailing newline fixes this issue.

Phew!


Different shards with same score, the search result will be different

What I have set is 3 nodes of Elasticsearch, and going to use DSL to search products like below

    Product.search query: query_hash, from: @from, size: @size, sort: [{"_score"=>{"order"=>"desc", "mode"=>"avg"}}, {"created_at"=>{"order"=>"desc", "mode"=>"avg"}}]

Everytimes when I search, the result will be so random. The results will have 3 different results. And I found that
https://www.elastic.co/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch
Is that any ways for us to configure DFS Query then Fetch?

Hi, sorry for a delayed response! This frequently happens on a small, testing corpus, with enough data, the scoring should "even out".
You can pass the dfs_query_then_fetch as a second parameter to the search method


Can't connect to piston with local docker image on Mac OS Catalina

Hi,
Thanks for this incredible project - it's awesome
Closest other issue this one: https://github.com/engineer-man/piston/issues/183
I suspect this is just user error on my part.
I'm trying to get piston to work locally as a docker image. I've followed these instructions from the read me:
# clone and enter repo
git clone https://github.com/engineer-man/piston
Installation
# Start the API container
docker-compose up -d api

# Install all the dependencies for the cli
cd cli && npm i && cd -

All of that works, and I can install packages with  cli/index.js ppman install python
Which I can verify with cli/index.js ppman list  and the container is up on port 2000:  <IP_ADDRESS>:2000->2000/tcp
The problem is that I can't connect to piston via chrome or ping.
ping <IP_ADDRESS>:2000/api/v2/piston/runtimes returns ping: cannot resolve <IP_ADDRESS>/api/v2: Unknown host and in chrome just returns the not found message.
I'm running Mac OS Catalina, which may be the problem.
Any help would be greatly appreciated
Thanks
Shane

Also side issue - can anyone help point me in the right direction with the specfiles? I  can't find an example of one to build a custom piston image with
6:    echo "Usage: $0 [specfile] [tag]"
35:    # Evalulate the specfile
47:[ -z "$SPEC_FILE" ] && help_msg "specfile is required"
50:[ -f "$SPEC_FILE" ] || help_msg "specfile does not exist"

cli/commands/ppman_commands/spec.js
6:exports.command = ['spec <specfile>'];
21:exports.handler = async ({ axios, specfile }) => {
22:    const spec_contents = await fs.readFile(specfile);

There's nothing in the docs either: https://piston.readthedocs.io/en/latest/search.html?q=specfile

Take off "piston" from the url. That's only used in the public proxy, not local instances.
All browsers perform a GET request when "going" to a url, so you'd only be able to check the runtimes endpoint there without a proper webapp.
And ping is for host checks . Use something like netcat for checking the port connection, if you need. Else just fire off a request to the right endpoint and see what happens. :)
Hope that gets ya going.

Cheers that's worked - I thought I'd have missed something daft
Thanks again


Unable to install bigchaindb server on ubuntu 18.04 LTS ?

Do you want to:

make a bug report? Then read below about what should go in a bug report.
Yes
make a feature request or proposal? Then read the page about how to make a feature request or proposal.
ask a question about BigchainDB? Then go to Gitter (our chat room) and ask it there.
share your neat idea or realization? Then go to Gitter (our chat room) and share it there.

What Should Go in a Bug Report

What computer are you on (hardware)?

2 CPU
8 GB RAM
 Google Cloud VM

What operating system are you using, including version. e.g. Ubuntu 14.04? Fedora 23?

Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.2 LTS
Release:	18.04
Codename:	bionic

What version of BigchainDB software were you using? Is that the latest version?
Unable to install BigchainDB
What, exactly, did you do to get to the point where you got stuck? Describe all the steps so we can get there too. Show screenshots or copy-and-paste text to GitHub.

Step 1.sudo apt update
Step 2.sudo apt full-upgrade
Step 3.sudo apt install -y python3-pip libssl-dev

Show what actually happened.

    error: command 'x86_64-linux-gnu-gcc' failed with exit status 1

    ----------------------------------------
Command "/usr/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-87jm9mry/gevent/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-gmdh5zyy-record/

Say what you tried to do to resolve the problem.
Tried to install
sudo apt install python3.6-dev
Provide details to convince us that it matters to you. Is it for a school project, a job, a contract with a deadline, a child who needs it for Christmas?
a contract with deadline

We will do our best but please understand that we don't have time to help everyone, especially people who don't care to help us help them. "It doesn't work." is not going to get any reaction from us. We need details.
Tip: Use Github code block formatting to make code render pretty in GitHub. To do that, put three backticks followed by a string to set the type of code (e.g. Python), then the code, and then end with three backticks. There's more information about inserting code blocks in the GitHub help pages.

Try updating pip to the latest version, i.e.
sudo pip3 install -U pip
To understand why that might help, see the comments on pull request https://github.com/bigchaindb/bigchaindb/pull/2645
This is all in the master branch of the docs, but there has been no new release since that update, so it's not in the latest (i.e. the default) docs. See:
http://docs.bigchaindb.com/projects/server/en/master/simple-deployment-template/set-up-node-software.html#install-bigchaindb-server

Try updating pip to the latest version, i.e.
sudo pip3 install -U pip
To understand why that might help, see the comments on pull request #2645
This is all in the master branch of the docs, but there has been no new release since that update, so it's not in the latest (i.e. the default) docs. See:
http://docs.bigchaindb.com/projects/server/en/master/simple-deployment-template/set-up-node-software.html#install-bigchaindb-server

This solution worked for me.


[IAC-1677] Replace gofmt with goimports

Replace gofmt with goimports in the pre-commit configuration. Note: This PR was opened using git-xargs.

Danke! Merging now!


feat: improve script quality (#778)

Fixes some small (potential) issues in scripts pointed out by shellcheck.

:+1:

👍


Bind to <IP_ADDRESS> for cql unless flag set (matching other services)

It's not passing the format check. mvn fmt:format. Also need to merge master for this commit 54817dced635c9dede0c397449e01a3f97f267de.

Tried it locally. It's binding correctly based on that flag.


Bind dropdown list dynamically

How can we bind dropdown list dynamically? I am getting following error.. I have used multiselect in *ngFor:
this.selectedItems.forEach is not a function
I have used multiselect as follows:
<div *ngFor="let input of Task.inputArr; let parentIndex = index">
       <angular2-multiselect [data]="input.list" [(ngModel)]="input.outputValue"
                   [settings]="dropdownSettings2" [disabled] = "viewTaskFlag" class="input-sm">
          <c-item>
                 <ng-template let-item="item">
                             <label style="color: #333;min-width: 150px;">{{item.itemName}}</label>
                   </ng-template>
           </c-item>
      </angular2-multiselect>
</div>

This is an implementation issue and not a bug with the component. Please drop a mail for any queries. Hence closing.


walkpath not functioning

Type
Incorrect behavior
Operating System
MacOS
OS Version
No response
Bug description
WorldPoint[] path = {
new WorldPoint(3028, 3844, 0),
new WorldPoint(3027, 3840, 0),
new WorldPoint(3024, 3834, 0),
new WorldPoint(3019, 3830, 0),
new WorldPoint(3009, 3827, 0),
new WorldPoint(3003, 3825, 0),
new WorldPoint(2997, 3822, 0),
new WorldPoint(2991, 3821, 0),
new WorldPoint(2980, 3821, 0),
new WorldPoint(2968, 3818, 0),
new WorldPoint(2964, 3818, 0),
new WorldPoint(2957, 3821, 0),
new WorldPoint(2950, 3819, 0),
new WorldPoint(2947, 3820, 0)
};
Microbot.getWalker().walkPath(path);
burning amulet to lvl 41 wildy --> walking to chaos altar
run that from the lvl 41 wildy spot
Screenshots or videos
No response
RuneLite version
latest microbot
Logs
No response

This should be fixed in the latest dev version
Fixed in commit https://github.com/chsami/microbot/commit/8a0afbee846bc139c1343190b726de478050ff42


Use Segoe Fluent Icons for window controls when available

Use Segoe Fluent Icons for window controls on Windows 11 and fallback to  Segoe MDL2 Assets on the others. In addition, change code points to correct values.

Hi, this change is not necessary as the font icons will be replaced with SVGs: https://github.com/lapce/lapce/pull/768

Hi, this change is not necessary as the font icons will be replaced with SVGs: https://github.com/lapce/lapce/pull/768

That's pretty nice. Close this.


Making updates to the node resource

Added a custom edit
Made a few modifications to the detail
Converted into a virtualType to remove import and create from the list page
rancher/dashboard#241
The spec.displayName for custom name and kubernetes.io/hostname for hostname are both going to need to be looked into further (I believe by the backend).
displayName is not getting returned by steve and I don't believe rancher currently uses kubernetes.io/hostname even though it appears to be the appropriate annotation.

I've updated the code per the requests.
Would you like to open a new issue to resolve issues where NameNsDescription shouldn't allow the user to edit the name via RBAC or something?

I already changed NameNsDescription to not allow changing names in edit mode in my tree, so that should be taken care of soon.  Technically it could be read from schema but metadata.name is never editable in k8s...


fix bangladeshi taka symbol

fix bangladeshi taka symbol , Like 'Tk' == '৳'

@rahman-cmd Thank you for your contribution. Bangladeshi Taka was fixed here #85 and released in v2.0.17.


Doc: spelling correction from 'allot' to 'a lot'

Description
Some statements that use the word allot don't fit right into its context.
How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] The PR is submitted to the correct branch (dev).
[ ] My code follows the code style of this project.
[ ] I've added relevant tests.

Someone else just PR'd the same thing sorry that i merged that one since you where first.

Sure, no problem


[DETECTION] CP932 containing half-width kana characters cannot be detected correctly.

About hankaku half-width kana.  https://en.wikipedia.org/wiki/Half-width_kana
Notice
I hereby announce that my raw input is not :

Too small content (<=32 characters) as I do know that ANY charset detector heavily depends on content
Encoded in a deprecated/abandoned encoding that is not even supported by my interpreter

Provide the file
https://github.com/competitive-verifier/competitive-verifier/blob/89102a878a9081f72bd3450065bcf7d9fd536a5f/examples/tests/encoding/cp932.txt
Verbose output
Using the CLI, run normalizer -v ./my-file.txt and past the result in here.
normalizer -v ../competitive-verifier/examples/tests/encoding/cp932.txt
2023-10-06 02:56:01,424 | Level 5 | override steps (5) and chunk_size (512) as content does not fit (485 byte(s) given) parameters.
2023-10-06 02:56:01,424 | Level 5 | Code page ascii does not fit given bytes sequence at ALL. 'ascii' codec can't decode byte 0x89 in position 0: ordinal not in range(128)
2023-10-06 02:56:01,424 | Level 5 | Code page utf_8 does not fit given bytes sequence at ALL. 'utf-8' codec can't decode byte 0x89 in position 0: invalid start byte
2023-10-06 02:56:01,425 | Level 5 | Code page big5 does not fit given bytes sequence at ALL. 'big5' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,425 | Level 5 | Code page big5hkscs does not fit given bytes sequence at ALL. 'big5hkscs' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,425 | Level 5 | cp037 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 93.600000 %.
2023-10-06 02:56:01,426 | Level 5 | cp1006 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 521.200000 %.
2023-10-06 02:56:01,426 | Level 5 | cp1026 is deemed too similar to code page cp037 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,426 | Level 5 | cp1125 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 115.300000 %.
2023-10-06 02:56:01,426 | Level 5 | cp1140 is deemed too similar to code page cp037 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,426 | Level 5 | Code page cp1250 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x83 in position 2: character maps to <undefined>
2023-10-06 02:56:01,426 | Level 5 | cp1251 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 102.400000 %.
2023-10-06 02:56:01,427 | Level 5 | Code page cp1252 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x90 in position 26: character maps to <undefined>
2023-10-06 02:56:01,427 | Level 5 | Code page cp1253 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x90 in position 26: character maps to <undefined>
2023-10-06 02:56:01,427 | Level 5 | Code page cp1254 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x90 in position 26: character maps to <undefined>
2023-10-06 02:56:01,427 | Level 5 | Code page cp1255 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x90 in position 26: character maps to <undefined>
2023-10-06 02:56:01,427 | Level 5 | cp1256 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 25.000000 %.
2023-10-06 02:56:01,427 | Level 5 | Code page cp1257 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x83 in position 2: character maps to <undefined>
2023-10-06 02:56:01,428 | Level 5 | Code page cp1258 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x90 in position 26: character maps to <undefined>
2023-10-06 02:56:01,428 | Level 5 | cp273 is deemed too similar to code page cp037 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,428 | Level 5 | Code page cp424 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x76 in position 54: character maps to <undefined>
2023-10-06 02:56:01,428 | Level 5 | cp437 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 107.800000 %.
2023-10-06 02:56:01,428 | Level 5 | cp500 is deemed too similar to code page cp037 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,428 | Level 5 | cp720 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 156.500000 %.
2023-10-06 02:56:01,429 | Level 5 | cp737 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 115.300000 %.
2023-10-06 02:56:01,429 | Level 5 | cp775 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 25.100000 %.
2023-10-06 02:56:01,429 | Level 5 | cp850 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,429 | Level 5 | cp852 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 104.400000 %.
2023-10-06 02:56:01,430 | Level 5 | cp855 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 127.500000 %.
2023-10-06 02:56:01,430 | Level 5 | Code page cp856 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xe1 in position 27: character maps to <undefined>
2023-10-06 02:56:01,430 | Level 5 | cp857 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 107.800000 %.
2023-10-06 02:56:01,430 | Level 5 | cp858 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,430 | Level 5 | cp860 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,431 | Level 5 | cp861 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,431 | Level 5 | cp862 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,431 | Level 5 | cp863 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,431 | Level 5 | Code page cp864 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xa6 in position 325: character maps to <undefined>
2023-10-06 02:56:01,431 | Level 5 | cp865 is deemed too similar to code page cp437 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,431 | Level 5 | cp866 is deemed too similar to code page cp1125 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,432 | Level 5 | Code page cp869 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x83 in position 2: character maps to <undefined>
2023-10-06 02:56:01,432 | Level 5 | Code page cp874 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x89 in position 0: character maps to <undefined>
2023-10-06 02:56:01,432 | Level 5 | cp875 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 75.200000 %.
2023-10-06 02:56:01,432 | Level 5 | Code page cp932 is a multi byte encoding table and it appear that at least one character was encoded using n-bytes.
2023-10-06 02:56:01,433 | Level 5 | cp932 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 48.600000 %.
2023-10-06 02:56:01,433 | Level 5 | Code page cp949 does not fit given bytes sequence at ALL. 'cp949' codec can't decode byte 0x83 in position 6: illegal multibyte sequence
2023-10-06 02:56:01,434 | Level 5 | Code page cp950 does not fit given bytes sequence at ALL. 'cp950' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,434 | Level 5 | Code page euc_jis_2004 does not fit given bytes sequence at ALL. 'euc_jis_2004' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,434 | Level 5 | Code page euc_jisx0213 does not fit given bytes sequence at ALL. 'euc_jisx0213' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,434 | Level 5 | Code page euc_jp does not fit given bytes sequence at ALL. 'euc_jp' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,434 | Level 5 | Code page euc_kr does not fit given bytes sequence at ALL. 'euc_kr' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,434 | Level 5 | Code page gb18030 does not fit given bytes sequence at ALL. 'gb18030' codec can't decode byte 0xc9 in position 247: illegal multibyte sequence
2023-10-06 02:56:01,435 | Level 5 | Code page gb2312 does not fit given bytes sequence at ALL. 'gb2312' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,435 | Level 5 | Code page gbk does not fit given bytes sequence at ALL. 'gbk' codec can't decode byte 0xc9 in position 247: illegal multibyte sequence
2023-10-06 02:56:01,435 | Level 5 | hp_roman8 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 484.800000 %.
2023-10-06 02:56:01,435 | Level 5 | Code page hz does not fit given bytes sequence at ALL. 'hz' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,435 | Level 5 | Code page iso2022_jp does not fit given bytes sequence at ALL. 'iso2022_jp' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,435 | Level 5 | Code page iso2022_jp_1 does not fit given bytes sequence at ALL. 'iso2022_jp_1' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,436 | Level 5 | Code page iso2022_jp_2 does not fit given bytes sequence at ALL. 'iso2022_jp_2' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,436 | Level 5 | Code page iso2022_jp_2004 does not fit given bytes sequence at ALL. 'iso2022_jp_2004' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,436 | Level 5 | Code page iso2022_jp_3 does not fit given bytes sequence at ALL. 'iso2022_jp_3' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,436 | Level 5 | Code page iso2022_jp_ext does not fit given bytes sequence at ALL. 'iso2022_jp_ext' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,436 | Level 5 | Code page iso2022_kr does not fit given bytes sequence at ALL. 'iso2022_kr' codec can't decode byte 0x89 in position 0: illegal multibyte sequence
2023-10-06 02:56:01,437 | Level 5 | iso8859_10 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 484.800000 %.
2023-10-06 02:56:01,437 | Level 5 | Code page iso8859_11 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xfc in position 195: character maps to <undefined>
2023-10-06 02:56:01,437 | Level 5 | iso8859_13 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 484.800000 %.
2023-10-06 02:56:01,437 | Level 5 | iso8859_14 is deemed too similar to code page iso8859_10 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,437 | Level 5 | iso8859_15 is deemed too similar to code page iso8859_10 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,437 | Level 5 | iso8859_16 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 484.800000 %.
2023-10-06 02:56:01,438 | Level 5 | iso8859_2 is deemed too similar to code page iso8859_16 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,438 | Level 5 | Code page iso8859_3 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xae in position 264: character maps to <undefined>
2023-10-06 02:56:01,438 | Level 5 | iso8859_4 is deemed too similar to code page iso8859_10 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,438 | Level 5 | iso8859_5 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 521.200000 %.
2023-10-06 02:56:01,438 | Level 5 | Code page iso8859_6 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xfa in position 122: character maps to <undefined>
2023-10-06 02:56:01,438 | Level 5 | Code page iso8859_7 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xae in position 264: character maps to <undefined>
2023-10-06 02:56:01,439 | Level 5 | Code page iso8859_8 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xc4 in position 33: character maps to <undefined>
2023-10-06 02:56:01,439 | Level 5 | iso8859_9 is deemed too similar to code page iso8859_10 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,439 | Level 5 | Code page johab does not fit given bytes sequence at ALL. 'johab' codec can't decode byte 0x83 in position 2: illegal multibyte sequence
2023-10-06 02:56:01,439 | Level 5 | koi8_r was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 251.600000 %.
2023-10-06 02:56:01,439 | Level 5 | Code page koi8_t does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0x8f in position 36: character maps to <undefined>
2023-10-06 02:56:01,439 | Level 5 | koi8_u was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 251.600000 %.
2023-10-06 02:56:01,440 | Level 5 | kz1048 is deemed too similar to code page cp1251 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,440 | Level 5 | latin_1 is deemed too similar to code page iso8859_10 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,440 | Level 5 | mac_cyrillic was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 115.300000 %.
2023-10-06 02:56:01,440 | Level 5 | mac_greek was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 243.600000 %.
2023-10-06 02:56:01,440 | Level 5 | mac_iceland was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 243.500000 %.
2023-10-06 02:56:01,441 | Level 5 | mac_latin2 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 200.100000 %.
2023-10-06 02:56:01,441 | Level 5 | mac_roman is deemed too similar to code page mac_iceland and was consider unsuited already. Continuing!
2023-10-06 02:56:01,441 | Level 5 | mac_turkish is deemed too similar to code page mac_iceland and was consider unsuited already. Continuing!
2023-10-06 02:56:01,441 | Level 5 | ptcp154 is deemed too similar to code page cp1251 and was consider unsuited already. Continuing!
2023-10-06 02:56:01,441 | Level 5 | Code page shift_jis is a multi byte encoding table and it appear that at least one character was encoded using n-bytes.
2023-10-06 02:56:01,441 | Level 5 | shift_jis was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 48.600000 %.
2023-10-06 02:56:01,442 | Level 5 | Code page shift_jis_2004 is a multi byte encoding table and it appear that at least one character was encoded using n-bytes.
2023-10-06 02:56:01,442 | Level 5 | shift_jis_2004 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 48.600000 %.
2023-10-06 02:56:01,442 | Level 5 | Code page shift_jisx0213 is a multi byte encoding table and it appear that at least one character was encoded using n-bytes.
2023-10-06 02:56:01,442 | Level 5 | shift_jisx0213 was excluded because of initial chaos probing. Gave up 1 time(s). Computed mean chaos is 48.600000 %.
2023-10-06 02:56:01,442 | Level 5 | Code page tis_620 does not fit given bytes sequence at ALL. 'charmap' codec can't decode byte 0xfc in position 195: character maps to <undefined>
2023-10-06 02:56:01,442 | Level 5 | Encoding utf_16 won't be tested as-is because it require a BOM. Will try some sub-encoder LE/BE.
2023-10-06 02:56:01,442 | Level 5 | Code page utf_16_be does not fit given bytes sequence at ALL. 'utf-16-be' codec can't decode bytes in position 258-259: illegal encoding
2023-10-06 02:56:01,442 | Level 5 | Code page utf_16_le does not fit given bytes sequence at ALL. 'utf-16-le' codec can't decode bytes in position 150-151: illegal UTF-16 surrogate
2023-10-06 02:56:01,442 | Level 5 | Encoding utf_32 won't be tested as-is because it require a BOM. Will try some sub-encoder LE/BE.
2023-10-06 02:56:01,443 | Level 5 | Code page utf_32_be does not fit given bytes sequence at ALL. 'utf-32-be' codec can't decode bytes in position 0-3: code point not in range(0x110000)
2023-10-06 02:56:01,443 | Level 5 | Code page utf_32_le does not fit given bytes sequence at ALL. 'utf-32-le' codec can't decode bytes in position 0-3: code point not in range(0x110000)
2023-10-06 02:56:01,443 | Level 5 | Encoding utf_7 won't be tested as-is because detection is unreliable without BOM/SIG.
2023-10-06 02:56:01,443 | DEBUG | Encoding detection: Unable to determine any suitable charset.
Unable to identify originating encoding for "../competitive-verifier/examples/tests/encoding/cp932.txt". Maybe try increasing maximum amount of chaos.
{
    "path": "/home/kzrnm/workspace/competitive-verifier/examples/tests/encoding/cp932.txt",
    "encoding": null,
    "encoding_aliases": [],
    "alternative_encodings": [],
    "language": "Unknown",
    "alphabets": [],
    "has_sig_or_bom": false,
    "chaos": 1.0,
    "coherence": 0.0,
    "unicode_path": null,
    "is_preferred": true
}

Expected encoding
CP932
Desktop (please complete the following information):

OS: Ubuntu (WSL on Windows11)
Python version : 3.10
Package version: 3.3

Additional context
If all the characters are kanji or full-width kana as shown below, charset_normalizer can detect correctly.
https://en.wikipedia.org/wiki/Ame_ni_mo_makezu
雨ニモマケズ
風ニモマケズ
雪ニモ夏ノ暑サニモマケヌ
丈夫ナカラダヲモチ
慾ハナク
決シテ瞋ラズ
イツモシヅカニワラッテヰル
一日ニ玄米四合ト
味噌ト少シノ野菜ヲタベ
アラユルコトヲ
ジブンヲカンジョウニ入レズニ
ヨクミキキシワカリ
ソシテワスレズ
野原ノ松ノ林ノ蔭ノ
小サナ萓ブキノ小屋ニヰテ
東ニ病氣ノコドモアレバ
行ッテ看病シテヤリ
西ニツカレタ母アレバ
行ッテソノ稻ノ朿ヲ負ヒ
南ニ死ニサウナ人アレバ
行ッテコハガラナクテモイヽトイヒ
北ニケンクヮヤソショウガアレバ
ツマラナイカラヤメロトイヒ
ヒデリノトキハナミダヲナガシ
サムサノナツハオロオロアルキ
ミンナニデクノボートヨバレ
ホメラレモセズ
クニモサレズ
サウイフモノニ
ワタシハナリタイ

Good catch, indeed.
Fixed in #366
soon to be available.


How to get success or error response after upload is done ?

@badunk
I have this issue.
I'm using following code as you have mentioned.
app.post('/upload', upload.array('upl',1), (req, res, next) => {
    // console.log(req.file.location);
    res.send("UPLOADED");
});

I need to take a response (error or success) based on the response from S3.
How can I do that ?
Specially I need to check the error if exists.
Please help me.

@badunk
I have the same problem as above
Is branching to err / succ working fine after file upload?
Where should I check the callback in the key function?
my sources
var upload = multer({
    storage: multerS3({
        s3:s3,
        bucket: 'xxx',
        contentType: multerS3.AUTO_CONTENT_TYPE,
        key: ( req, file, callback ) => {
            var file_originalname = file.originalname.split('.');
            var file_extension = file_originalname[1];
            var moment_date = moment().format('YYYYMMDDHHmmss');
            var new_fileName = 'file/admin/admin'+"_"+moment_date+'.'+file_extension;
            var check_type = file_extension.toLowerCase();
            if( check_type == 'jpg' || check_type == 'png' || check_type == 'jpeg'){
                return callback(null, new_fileName);
            }else{
                return callback(`not image TYPE >> ${check_type}`);
            }
        }
    }),
    limits : { fileSize: 2 * 1024 * 1024 }
})
var singleUpload = upload.single('file');

router.post('/upload', (req, res, next) => {
    var result = {};
    singleUpload(req, res, function(err, data){
        if( err ){
            console.log( err );
            result.code = '0009';
        }
        else{
            console.log( data );
            console.log('destination >> ', req.file.location );
            result.code = '0000';
        }
    });
    res.json(result);
});


feat(cli): add --keepalive option to specify model load duration

Added a new command line option --keepalive to allow users to specify the duration for which a model should remain loaded. This option accepts a duration value (e.g., 5m).

Tip : to unload a model, simply run ollama run --keepalive 0 <model>

Thank you, please ensure README.md includes details of the option. Especially the parsable time formatting allowed

Gven this should be covered in the Ollama CLI docs, let's merge this.


Problem with 'Get started on GOV.UK'

Problem with 'Get started on GOV.UK' (https://docs.publishing.service.gov.uk/manual/get-started.html)
Is this https://docs.publishing.service.gov.uk/manual/get-started.html and others
intended to be open widely to the public?

Hi @kdziubacaci, that's correct. At GDS we work try to work in the open as much as possible.
You can read more about the approach here:
https://gds.blog.gov.uk/2017/09/04/the-benefits-of-coding-in-the-open/


Added apple developer sign in CI

This PR will add apple developer signature steps in CI workflow for mac

With the same certificate it can be signed more than one app right?

With the same certificate it can be signed more than one app right?

yes
https://developer.apple.com/forums/thread/657993


Fix resize collision shape for tile when vertex outside of tilesheet

Complements pull request #42150 which did not completely resolve the issue.

Version: v3.2.4.rc.custom_build.4f891b706
Bugsquad edit: Fix #34970

The issue is still not fixed in 3.2.4 RC5.

@dszhblx Obviously, because this PR that would fix it is not merged yet. Please don't bump issues and PRs with such comments, you can express your approval of the change by adding a :+1: to the PR, and you can build the PR locally to confirm that it fixes your issue and help accelerate its review and merge.

cc @groud

Superseded by #73218.


Update node to v22 in package.json

I ran npx create-epic-app@latest this morning, then ran npm run test:e2e:run as the first thing in my newly generated app. It failed with this error:
> test:e2e:run
> cross-env CI=true playwright test

TypeError [ERR_INVALID_ARG_TYPE]: The "parentURL" argument must be of type string or an instance of URL. Received an instance of Object
    at new NodeError (node:internal/errors:405:5)
    at throwIfInvalidParentURL (node:internal/modules/esm/resolve:937:11)
    at Hooks.resolve (node:internal/modules/esm/hooks:241:5)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:337:35)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:220:38)
    at ModuleLoader.import (node:internal/modules/esm/loader:307:34)
    at Hooks.register (node:internal/modules/esm/hooks:138:51)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:168:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:807:20)
    at exports.emitMessage (node:internal/per_context/messageport:23:28) {
  code: 'ERR_INVALID_ARG_TYPE'
}

After some digging and trial-and-error, I found that the problem was that I was running with node 20. The most concerning part is: not even switching to node 22 fixed it. I had to re-run npx create-epic-app@latest using node 22 also. Using the version of the app created with node 20 did not work, even if I switched to node 22 afterward.
Test Plan

Checklist

[ ] Tests updated
[ ] Docs updated

Hmmm... CI is running node 20 and working ok. I'm not sure this is the correct solution to your problem

I can close it, but I'm sure it solved my problem. I can consistently reproduce. And since it's happening on a fresh project, I doubt it is anything I did locally. But anyway…


MEGA2560 support added

I added mega 2560 support in the mega folder. I added README.md file with all changes.

Hi Baron,
Thanks for the PR. As I intent the master branch to be hardware/platform agnostic, can you send another PR as separate branch (something like)“arduinomega” instead. At least we can point Arduino Mega users to this useful resource until the issues highlighted are resolved and merged in the master branch which also works for all platform. Cheers! Closing this until re-PR

Hii
Can u pl share link to folder, for arduino mega am not able to locate in readme.
Thanks a lot
Regards


deletion bug

Describe the bug
bruh why deletion text leave ? before totally deleted!
To Reproduce
Steps to reproduce the behavior:

type a single word or msg with any style
then try to delete it with irregular keyboard
deletion leave ? mark before is completely deleted (Bruh 🗿🗿🗿🗿🗿 that's annoying)

Expected behavior
text should completely deleted
Android version
10
Additional context
confused? okay i will add video demonstration

ℂ𝕝𝕒𝕣𝕚𝕗𝕚𝕔𝕒𝕥𝕚𝕠𝕟 & 𝔻𝕖𝕥𝕒𝕚𝕝𝕤
The bug:
Advanced UTF-8 Symbols get only half deleted, leaving inv�lid characters behind. This doesn't happen on any other keyboard I've tried (not even the dead old Hacker's Keyboard) -> therefore it can be considered a real bug in the deletion mechanism.
This should be considered as high priority as it's a very annoying bug which directly interferes with the UX.
I'm not a developer - but as long as this isn't a bug within the core part of the application, it shouldn't be hard to fix it.
Thank You for this awesome little tool 😊
⪩ 𝓑𝓮𝓵𝓪 ⪨ ~ NA0341

This is a duplicate issue!
Any information to the bug should be posted in #16 instead!

This is a duplicate issue! Any information to the bug should be posted in #16 instead!

My apologies either i not search them carefully or i can't found it due to search index such problem
Closed!


Expand user prefix in dest dir

While the user's home directory is /home/username/ on linux, it is /Users/username/ on MacOS. This change allows smoother reuse of config files between linux and mac.

@igordertigor awesome, thank you. It seems master is a bit broken CI wise, but I'll merge anyway.

@esc: I had trouble running the cram tests.


fix bug: listResources with one more null element returned

Codecov Report

Merging #315 into release-rc4 will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@                Coverage Diff                @@
##             release-rc4     #315      +/-   ##
=================================================
- Coverage          21.71%   21.70%   -0.01%
  Complexity           388      388
=================================================
  Files                130      130
  Lines               5228     5230       +2
  Branches             402      403       +1
=================================================
  Hits                1135     1135
- Misses              4012     4014       +2
  Partials              81       81

Impacted Files
Coverage Δ
Complexity Δ

.../wecross/restserver/response/ResourceResponse.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)


learning to render statci files in django

@ssd71 @biswajitpatra please verify before merging

Are you using cdn? Please use cdn

Currently not used cdn, I was just testing whether static files are being rendered or not.Some static files are being rendered but some others are not being.Please verify the project folder structure management is correct or not


Re-organize sensors on the device page

With the latest changes, we've exposed more attributes of the panel as entities, which is great. What isn't great is that it clutters up the device screen, and we now mix alarm sensors and alarm entities. While it does seem like there is some sort of logical order, I think we should break up the alarm panel sensors themselves from the zone sensors.
I'm thinking that any binary sensor relating to a zone stays in the Sensor section, and then anything related to the alarm panel itself, like Keypad, AC power, etc, moves to the Diagnostic section.

In release v0.8.2.
I left the panel ready, alarm, and fire sensors where they were because they did not feel like diagnostics.


Modify workflow.py to allow skipping the copy step

For re-running weekly releases, the file is eventually deleted from clinvar's ftp site, but we have the copy in GCS already. We should be able to easily re-run the workflow on the file in GCS without needing to do the copy.
Can auto-detect that the copy step should be skipped from the input values. Two options:

we can accept different input values for the host, like gs://<bucket-name>, which would indicate that the file is already in a bucket, not on an ftp/http site, and if the bucket name matches the bucket we are copying to, skip the copy.
accept the same input values, like:host="https://ftp.ncbi.nlm.nih.gov"
directory="/pub/clinvar/xml/VCV_xml_old_format"
name="ClinVarVariationRelease_2024-02.xml.gz"
size=3298023159
last_modified="2024-01-07T15:47:16"
released="2024-02-01T15:47:16"
release_date="2024-02-01"

but when we construct the copy destination location (e.g. gs://bucket/path/ClinVarVariationRelease_2024-02.xml.gz) we can check if it already exists and skip the copy if so, which both satisfies #63 and makes it so the workflow doesn't break for re-running past runs, by omitting the copy step.

This is pretty high priority actually because we can't re-run on a past file like https://ftp.ncbi.nlm.nih.gov/pub/clinvar/xml/VCV_xml_old_format/weekly_release/ClinVarVariationRelease_2024-0603.xml.gz since it no longer exists.

Closed by #181
See https://github.com/clingen-data-model/clinvar-ingest/blob/0c842d8acf0b333f33f30573bbd6b6604a307b95/misc/bin/execute-job.sh#L66-L73
as an example of input args


map search

Subject: map search
Description:
map search seems different. unfortunately it doesn’t work anymore. i habe tried it with different browsers.
Results:
i can‘t choose more than one of the filters and it won’t search for anybody on the map. i won‘t find any users.
Backend version: develop-2a028020
Frontend version: develop-2a028020
User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 17_6_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.6 Mobile/15E148 Safari/604.1
Page: https://couchers.org/search#loc=10.29/38.8939/-77.0146
User: lottticarottti (43123)

maybe it's due the server bug which makes the map super slow

we have another ticket for this


[EC-134] Investigate if blocks.head in RegularSyncController is 'safe'.

It is not safe because we can get empty response from peer

this fix is already in block sync


Python3 support

some syntax correction for python3 (plugins not tested except osc)
switch from pyOSC to python-osc as the latter is maintained frequently (https://github.com/OpenBCI/OpenBCI_Python/issues/30)

maybe it should be merged to another branch, not master?

The code seems legit to me, I did not test the new OSC implementation, but I trust you @micuat that it is working ;) Thanks for the pull request :)


Observability addon install failed

Describe the bug

Observability addon install failed.
It say: Fetch repository successfully, Delivery helm release in progress, message: install retries exhausted, Helm install failed: timed out waiting for the condition Last Helm logs: creating 15 resource(s) beginning wait for 15 resources with timeout of 10m0s Service does not have load balancer ingress IP address: vela-system/grafana

helm list -n vela-system

NAME                          	NAMESPACE  	REVISION	UPDATED                                	STATUS  	CHART                     	APP VERSION
grafana                       	vela-system	1       	2022-02-05 08:35:54.010193888 +0000 UTC	failed  	grafana-6.14.1            	8.0.5
grafana-registration          	vela-system	1       	2022-02-05 04:59:00.383012921 +0000 UTC	deployed	grafana-registration-0.0.7	0.0.6
loki                          	vela-system	1       	2022-02-05 08:29:04.143591336 +0000 UTC	deployed	loki-stack-2.4.1          	v2.1.0
vela-system-kube-state-metrics	vela-system	1       	2022-02-05 08:32:29.775759376 +0000 UTC	deployed	kube-state-metrics-3.4.1  	2.1.0

kubectl get pod -n vela-system

NAME                                              READY   STATUS    RESTARTS   AGE
grafana-844464d494-76hfw                          1/1     Running   0          21m
grafana-configuration-68845b6bdb-xrmkb            1/1     Running   0          5h2m
loki-0                                            1/1     Running   0          28m
loki-promtail-75lt7                               1/1     Running   0          28m
vela-system-kube-state-metrics-688454d44f-ndgjp   1/1     Running   0          25m

kubectl get svc -n vela-system

NAME                             TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
grafana                          LoadBalancer   <IP_ADDRESS>   <pending>     80:31269/TCP   23m
loki                             ClusterIP      <IP_ADDRESS>    <none>        3100/TCP       29m
loki-headless                    ClusterIP      None            <none>        3100/TCP       29m
vela-system-kube-state-metrics   ClusterIP      <IP_ADDRESS>     <none>        8080/TCP       26m

To Reproduce

refer to https://kubevela.io/docs/install .

Install k8s cluster with kind.
Install ingress controller to enable service route
Install KubeVela Core
Install KubeVela CLI
Install VelaUX
enable addon fluxcd
enable addon observability-assets
enable addon observability  (can't)

Expected behavior

enable addon observability
Screenshots

KubeVela Version

both 1.2.2 and latest in master
Cluster information

Kubernetes Version 1.21.2
Additional context

I found the reseaon :)
Because I running on kind cluster, and it's not support LoadBalancer type service, and in the addon repo, it's the fixed LoadBalancer (https://github.com/oam-dev/catalog/blob/8dc0f1c9392cc4720b04362f8798286ffeec6388/experimental/addons/observability/resources/grafana.cue#L13) .
And then I modify LoadBalancer to ClusterIP, it became successful~
Thus, should we make the type of service configurable for user?

Yes, in fact the default type should be ClusterIP


Useful CLI tools

Some tools I want to look at

monit
lsof

Rarely need these tools for my workflows, but they are useful.


Support for Ventura

Modified CISBenchmark.sh to allow for Ventura
Line 26  - added
&& [[ "$osVersion" != "13."* ]]
Added 3 lines  (lines 277-279)
elif [[ "$osVersion" = "13."* ]]; then
echo "*** Current version - macOS Ventura ${osVersion} (${buildVersion})"
echo "" 1>&2
Added 2 lines (CISBenchmarkReport) - lines 2785-2786
elif [[ "$osVersion" = "13."* ]]; then
echo "Security report - $(date) - macOS Ventura ${osVersion} (${buildVersion});;;;;;" >> "${CISBenchmarkReport}"

Any update on this? The script still doesn't support Ventura


Include --analyze compiler option for macOS and resolve warnings

The following should be done for all native Node packages:

The "--analyze" compiler option should be added to the binding.gyp file for macOS.
Any warnings that come up during compilation should be resolved.

[x] clipboard-files
[x] se-osx-keychain
[x] system-format

See https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1444528.

For some reason, including the --analyze flag in the binding.gyp interferes with the context-awareness property Node modules require to run in Electron. This is a shame, because static analysis did in fact find some potential memory leaks that needed plugging up. We should find a way to run analysis separate from the "functional" build.

Moving to 1.25.0 in case we can come up with a relatively quick solution. Re-triage as necessary.


Converter is dropping final letter of cell if directly adjacent to next cell delimiter

If a table cells ends with a letter, and that letter is directly adjacent to the next cell delimiter, that letter is being dropped during conversion.
Consider the following case:
|===
|foo|bar|baz
|===

This results in:
|     |     |     |
| --- | --- | --- |
| fo | ba | ba |

We expect the result to be:
|     |     |     |
| --- | --- | --- |
| foo | bar | baz |

What's happening is that the last letter is being consumed as the cell style. The cell style must be preceded by a space or newline.

Resolved by d06cddd035fa7b17ea23fd244faa78fcf9e06496

Related to this issue, the converter should consume the alignment modifiers that precede style cell style (e.g., >s). Note, however, that these settings are not honored. We just don't want them to be treated as content.


Any modelling of user role, ie admin? With perhaps a registered users overview?

I'd like to see if there is any modelling of user roles [user, admin] etc
It would be great if a user admin could see an overview of all registered users via an /admin type path
Does this exist? (Doesn't look like it at first glance). IS it against your philosophy to add it?

Sorry wrong repo


Add eventuallyWithT around windows secret e2e

What does this PR do?
Try to fix a e2e test on windows
Motivation
Flakiness
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes

/merge

/merge


Some problem with Data Package viewer

Hi,
I have seen that it's possible to use the path of a github folder that contains a datapackage.json file, to view a Data Package. This is an example:
http://data.okfn.org/tools/view?url=https%3A%2F%2Fgithub.com%2Fdatasets%2Fex-geojson
But it's impossible to use a folder URL for one of my repository. The viewer works only if I use the URL of my datapackage.json.
In this way it does not work:
http://data.okfn.org/tools/view?url=https%3A%2F%2Fgithub.com%2Fspaghetti-open-data%2Fbeni-confiscati-aperti%2Ftree%2Fgh-pages%2Fdati%2Fbeni_immobili
In this way it works:
http://data.okfn.org/tools/view?url=https%3A%2F%2Fraw.githubusercontent.com%2Fspaghetti-open-data%2Fbeni-confiscati-aperti%2Fgh-pages%2Fdati%2Fbeni_immobili%2Fdatapackage.json
What's wrong in my files/procedures?
Thank you

The answer here is simple: the current viewer setup does not work with repo branches if you just provide the github url (if you provide the direct url to the raw data it works because there is no need to compute anything - it just works off that direct url). It would not be hard to improve the viewer to support this:
https://github.com/okfn/data.okfn.org/blob/master/routes/index.js#L181

@rgrp it works only with the master branch?
Thank you

@aborruso if you don't use the raw link then yes it only works with the master branch atm. Would not be hard to fix - see https://github.com/okfn/datapackage-identifier


how to forbid slide when only one item?

I added ImageView to layout with visibility:Gone;
and When is one item to display Im showing ImageView and loading image -> and setting slider gone


Delete variation selectors

When converting some emojis to images emojis (such as ❤ ), it leaves a trailing square character just after the image.
According to https://apps.timwhitlock.info/unicode/inspect?s=❤ some emojis have an extra variation selector character. Deleting that character from the remaining text looks like solving the issue.

Hey @hidakatsuya,
what do you think about this?

@erdemgezer
Thank you for your PR! I've confirmed this problem.

Deleting that character from the remaining text

Certainly this fix can solve this problem, but i think that it has too wide influence range. So i would like to fix with another approach.
I will close this PR and try to fix this problem.

great!
thanks @hidakatsuya

@erdemgezer 2.1.0 has been released now!
https://github.com/hidakatsuya/prawn-emoji/releases/tag/2.1.0


soc: openisa_rv32m1: Implement sys_arch_reboot()

Implements sys_arch_reboot() on the openisa_rv32m1 soc to enable zephyr
micropython on the rv32m1_vega board.
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>

Codecov Report

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

@@            Coverage Diff            @@
##             master   #13959   +/-   ##
=========================================
  Coverage          ?   52.25%
=========================================
  Files             ?      307
  Lines             ?    45431
  Branches          ?    10507
=========================================
  Hits              ?    23740
  Misses            ?    16900
  Partials          ?     4791

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 846dfd4...b2bfee0. Read the comment docs.


Uniformization of preprocessor macros for targets

See issue #440.
Replaced TARGET_AMD64 by TARGET_AMD64
Replaced TARGET_X64 by TARGET_AMD64
Replaced TARGET_X86 by TARGET_X86
Replaced TARGET_ARM by TARGET_ARM
Let me know if you want me to squash the commits.
Note that I changed X64Emitter.cs and CorInfoHelpFunc.cs and I'm not sure if this is appropriate. In the first file the code is commented, but not in the second.

LGTM

It would be nice to remove these from the CMakefiles as well...

I was looking for them and I could not find them defined in the corert source tree. It is after calling build.cmd that the VS solutions are filled with TARGET_... macros. Is this cmake that generates them?

It is here: https://github.com/dotnet/corert/blob/master/src/Native/CMakeLists.txt#L129

Thanks. I was grepping on "<TARGET" and thus missed them. I'll put a new PR.


Workshop to plan initial development

As prep for a chat with Tony:

Results from software planning meeting
Main deliverable to aim for until June meeting
Dipayan and dev time discussion

Hi, @anu-shiva @ESapenaVentura
Workshop has been planned for Thursday 10.30.


ppc64le tests fail with gcc-4.8.5 with -O2 and some flags

The built environment is same with https://github.com/nemequ/simde/issues/202 except the flags. EPEL7 environment.
https://gist.github.com/junaruga/c667aec32a8978c41946d76903f21bb5
...
/arm/neon/vdup_n_s8/emul/c           [ ERROR ]
/arm/neon/vdup_n_s16/emul/c          Error: ../../test/arm/neon/vdup_n.c:67: assertion failed: ((const int8_t*) &(r))[8] == ((const int8_t*) &(test_vec[i].r))[8] (0 == -8)
Error: child killed by signal 6 (Aborted)
...
/arm/neon/vdup_n_u8/emul/c           [ ERROR ]
/arm/neon/vdup_n_u16/emul/c          Error: ../../test/arm/neon/vdup_n.c:215: assertion failed: ((const uint8_t*) &(r))[8] == ((const uint8_t*) &(test_vec[i].r))[8] (0 == 248)
Error: child killed by signal 6 (Aborted)
...
/arm/neon/vdup_n_f32/emul/c          [ ERROR ]
/arm/neon/vdup_n_f64/emul/c          Error: ../../test/arm/neon/vdup_n.c:355: assertion failed: ((const simde_float32*) &(r))[2] == ((const simde_float32*) &(test_vec[i].r))[2] (0.0 ==<PHONE_NUMBER>1864977309761536.0)
Error: child killed by signal 6 (Aborted)
...
981 of 990 (99%) tests successful, 0 (0%) test skipped.

All the log is here.
Thank you.

Should be "fixed" by the same changes as #202


[Feature] Localization: auto OS language detection

Purpose

Automatically detect OS language if OS language is supported by Contoso app localization and supported by Composite

Will check languageCode ll-CC (language-region) if supported
If ll-CC not supported, fall back to check languageCode ll (language) if supported
Default language is en (English)

When specified languageCode in LocalizationConfiguration will override the auto detected OS language
Added localization for Demo app with languages: en, zh-Hant, fr, fr-CA (currently fr-CA is not yet supported by Composite)

Does this introduce a breaking change?

[ ] Yes
[ x ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ x ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

What to Check
Verify that the following are valid

Switch system OS language to French or Traditional Chinese, then open the app, go too Settings page select Language as auto (Detect OS locale)
Should see Join Call label in setup screen to show Join Call (override <language>) for French and Traditional Chinese because both Contoso (Demo app) and Composite supports French and Traditional Chinese

Other Information

There is some inconsistency in reading the customized string from System and our LocalizationPrvoider. Is this scenario expected? I add a new language Hebrew inside the demo App. I set my device preferredLanguageId to he-CA. Add localization string of hebrew for demo app's Start Experience button and Join call button.
Result: The demo app's Start Experience button would be replaced with word in the Localizable.strings. The composite Join Call button wouldn't read the string from the Hebrew Localizable.strings but reading the default english string

Remove the logic to check if language is also supported by Composite, makes more sense if whatever the system language is, as long as Contoso supports, they could be directly providing key-value in associated Localizable.strings file for overriding strings.


Logstash chart should support pod topologySpreadConstraints

Feature
The Logstash chart should support specification of topologySpreadConstraints on the pods created by the statefulsets template.
I will file a PR that supports this feature.
Justification
In many cases, we deploy Logstash releases that create a number of pods that exceed the number of nodes in the target cluster.  This is the case when using Logstash to process large workloads from a message queue.  In the interest of not overloading any one node of the cluster, we want to spread out the scheduling of these pods evenly across all worker nodes in the Kubernetes cluster.
The existing affinity: podAntiAffinity rules are not helpful under these circumstances.  podAntiAffinity effectively will spread out the pods only as long as the number of pods does not exceed the count of worker nodes in the cluster.  After that, podAntiAffinity actually blocks scaling of the statefulSet.
topologySpreadConstraints , by contrast, allow us to more flexibly inform the scheduler how we want workloads distributed on the cluster, and allow us to specify the whenUnsatisfiable: ScheduleAnyway option to signal to the scheduler that the workload should be deployed even if the ideal pod distribution cannot be achieved.
References

https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/

A PR implementing this feature has been submitted.  I have created a few releases in my own cluster off of this code branch, and it seems to be working effectively.
See: #1514


NullReferenceException in UMAExpressionPlayer

Describe the bug
When creating the DynamicCharacterAvatar component in runtime and then adding a UMAExpressionPlayer to it, it throws a NullReferenceException in the Initialize method, particularly in these two lines below.
72: avatar.CharacterBegun.AddListener(CharacterBegun);
73: avatar.CharacterUpdated.AddListener(UmaData_OnCharacterUpdated)

The thing is that those events in the avatar component are never properly initialized (apparently it relies on the UI inspector to initialize them), thus accessing them without checking if they're null first is a bad idea.
For the moment, we have avoided the exception by commenting out the code that subscribes to the events in the avatar, and instead use the ones in the UMAData component, which are properly initialized.
Environment (please complete the following information):

Unity Version: 2019.4.28
UMA Version: 2.12
Rendering Pipeline: Unity Default
Platform Build (if not editor): Editor

To Reproduce
Steps to reproduce the behavior:
In runtime, add a DynamicCharacterAvatar script to a GameObject, and then add a UMAExpressionPlayer to it.
Expected behavior
No exception thrown.

Replacing expression player in #423


Added support for requiring multiple strategies

If you need to require few strategies on one request just add {requiredAll: true} for options.
Example:
passport.authenticate(['auth-user', 'auth-project'], {requiredAll: true})

Coverage decreased (-0.3%) to 99.107% when pulling 6911b27c86674dfb46ef03eccfc23f39459723b1 on siginur:patch-1 into 5d22e4e916a3d01702189c3a3ffcb3869acaed81 on jaredhanson:master.

Coverage decreased (-0.3%) to 99.107% when pulling 6911b27c86674dfb46ef03eccfc23f39459723b1 on siginur:patch-1 into 5d22e4e916a3d01702189c3a3ffcb3869acaed81 on jaredhanson:master.

Coverage decreased (-0.3%) to 99.107% when pulling 6911b27c86674dfb46ef03eccfc23f39459723b1 on siginur:patch-1 into 5d22e4e916a3d01702189c3a3ffcb3869acaed81 on jaredhanson:master.

Can't you just run these as multiple middleare?
passport.authenticate('auth-user'),
passport.authenticate('auth-project'),

I'm also curious what the use case is behind this?  At the end of this there is a single authenticated user, what does it mean that her credential passed two different authentication checks?  Would there be two databases where the password was expected to be the same?

Yes, of course you can to use two different middlewares. But my solution is more elegant and it's not conflict with basic logic of "passport".
For example in my project available few authentication grants: users(user auth), master-user(user and project auth), developers(developer auth), moderators(developer and project auth), viewers(project auth)
And instead to use 5 different middlewares, I use only 3. (user, developer and project auth)
Also If it will be required I add support for save two or more authenticate users. By just adding parameter 'userPropery' option for the strategy. And of course it is not be conflict with 'master branch' (people can use or not to use new features without hoping for support old projects)

I still want to understand the use case here.  Let's take a "developer auth" and "viewer auth".  Is there a single database of users who authenticate, and they exist in different roles (ie, viewer or developer)?  If that is the case, that seems more related to authentication rather than authorization.  For example, could you do something like:
app.get('/developer',
   passport.authenticate('users'),
   function(req, res, next) {
     if (req.user.role === 'developer') { return next(); }
     return res.end('Not a developer');
   },
   ...);

app.get('/viewer',
   passport.authenticate('users'),
   function(req, res, next) {
     if (req.user.role === 'viewer') { return next(); }
     return res.end('Not a viewer');
   },
   ...);

Are you doing these sort of checks in the authentication strategy, and that is why you want to satisfy multiple strategies?

This is authorization-related functionality, that is best handled after authentication and thus outside the scope of this module.  Closing.


Remove client-side libs panel

It's not really a thing.

@Mitzi-Laszlo - you merged this?  Before I even get a chance to respond to the suggestion to remove that was posted while I was asleep and acted on before I got up?  One reason I believe that this should not be removed is the question of repos - currently tools are scattered everywhere, isn't there an advantage to having them in one repo?  I would also like to hear from some of the other tool developers before closing this as a panel - @0tto_aa, @bourgeoa, @noeldmartin, @jucole who posted in the forum just yesterday that he thought this panel was a good idea.   I would also like to hear what the reason for the panel was to begin with and why those reasons no longer apply.  Is it because there has been no action so far?  It's August and many people, including me, are temporarily away or otherwise occupied.

Another reason I believe it is important to have a panel on libraries is that choosing libraries is a critical for app developers and rather than each library developer saying "use mine, use mine" it makes more sense to have a coordinated approach listing the strengths and weaknesses of the various tools.

I would also like to hear what the reason for the panel was to begin with

My impression was that it had emerged from a misunderstanding, namely me trying to organize the repositories at https://github.com/solid/information/blob/master/repo-overview.md by tagging leftovers with "client-side library". That seemed to have been understood as me proposing a client-side library panel.
There is definitely a need for organizing the repositories we have, but that might be broader than just client-side libs.
So good idea, and my suggestion for closing this panel was not related to that.

Thanks for the explanation.  I think that combining "leftovers" with client-side libraries is part of the problem.  I believe we want to encourage app developers to use standard libraries where possible and the only way to do that is by being clear what libraries are available and what the differences are between them are.  As a library developer, I'm always unsure whether my projects are useful in a bigger picture or just distractions and I could use the guidance of people like @RubenVerborgh and the other developers.  I also believe that there are many spots where we would want multiple libraries to work e.g. multiple kinds of fetch libraries or apps that can take either rdflib or comunica as parsers.   To get those kinds of plug-and-play scenarios takes coordination among projects and this seems like the place that coordination should happen.

OTOH, if these things are better discussed elsewhere, I'm open to that too.

I'm not sure a "panel" would be appropriate for this group of people discussing client side libraries, but I am def interested in discussions/plans/etc. around that topic.
I think the "panels" are meant to be more official and focused around document proposal sort of work though.

Good point about documentation, @JordanShurmer.  I think an "intro to Solid tools and libraries" is a much needed documentation piece.  I've made some starts at it but it is hard to even know what all the tools are and how they relate so it should be a group project.   Seems to me that the questions are unique to tools and distinct from a more general apps panel.

The main reason why I posted in the forum that I thought it was a good idea was because I was hoping that a panel, either in the formal or informal sense would recon / plan / prioritise / avoid lib duplication of the most needed libraries,  and also for the other reasons @jeff-zucker  puts forward.
And Jeff your work on your libraries is spot-on!

Another reason I believe it is important to have a panel on libraries is that choosing libraries is a critical for app developers

I think it's a good idea for library authors to coordinate. When it comes to helping app developers pick, however, that might be more relevant to/require alignment with the Teaching Material Panel?


Building Nuxt with compressPublicAssets fails when in a Bun docker container

Environment

Operating System: Windows_NT
Node Version:     v20.14.0
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr, devtools, modules, shadcn, content, colorMode, googleFonts, monacoEditor, compatibilityDate, nitro
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction

Create some Nuxt projects with some routes
In the nuxt.config.ts file, enable the compressPublicAssets in the nitro category, with brotli set to true. Also set the nitro preset to bun.
Add the dockerfile mentioned in the Additionnal context category
Run the docker build command : docker build --pull --rm -f "Dockerfile" -t project:latest "."
Try to run the container. It's not supposed to work

Describe the bug
The docker nuxt build step runs fine until the nitro prerender route step, after which it exits instantly, without any errors repported and without finishing generating the production server. (Compare the output of the docker build with the output outside of Docker in the additional contexts).
Additional context

My dockerfile
# use the official Bun image
# see all versions at https://hub.docker.com/r/oven/bun/tags
FROM oven/bun:1 AS base
WORKDIR /usr/src/app

# install dependencies into temp directory
# this will cache them and speed up future builds
FROM base AS install
RUN mkdir -p /temp/dev
COPY package.json bun.lockb /temp/dev/
RUN cd /temp/dev && bun install --frozen-lockfile

# install with --production (exclude devDependencies)
RUN mkdir -p /temp/prod
COPY package.json bun.lockb /temp/prod/
RUN cd /temp/prod && bun install --frozen-lockfile --production

# copy node_modules from temp directory
# then copy all (non-ignored) project files into the image
FROM base AS prerelease
COPY --from=install /temp/dev/node_modules node_modules
COPY . .

# [optional] tests & build
ENV NODE_ENV=production
RUN bun test
RUN bun run build

# copy production dependencies and source code into final image
FROM base AS release
COPY --from=prerelease /usr/src/app/.output .

# run the app
USER bun
EXPOSE 3000/tcp
ENTRYPOINT [ "bun", "run", "./server/index.mjs" ]

My nuxt config file
export default defineNuxtConfig({
  ssr: false,
  devtools: { enabled: true },

  modules: [
    '@pinia/nuxt',
    'shadcn-nuxt',
    '@nuxtjs/tailwindcss',
    'nuxt-monaco-editor',
    '@nuxt/content',
    '@vueuse/nuxt',
    'nuxt-lucide-icons',
    '@nuxt/image',
    '@nuxtjs/color-mode',
    '@nuxtjs/google-fonts',
  ],

  shadcn: {
    /**
     * Prefix for all the imported component
     */
    prefix: '',
    /**
     * Directory that the component lives in.
     * @default "./components/ui"
     */
    componentDir: './components/ui',
  },

  content: {
    highlight: {
      theme: {
        // Default theme (same as single string)
        default: 'github-light',
        dark: 'github-dark',
      },
      langs: ['c', 'cpp', 'java', 'python'],
    },
  },

  colorMode: {
    classSuffix: '',
  },

  googleFonts: {
    families: {
      Inter: '300..800',
      'JetBrains+Mono': '200..800',
    },
    display: 'swap',
  },

  monacoEditor: {
    locale: 'fr',
  },

  compatibilityDate: '2024-07-04',

  nitro: {
    preset: 'bun',
    compressPublicAssets: {
      brotli: true
    }
  },
});

Here are the log files (Because the issue is otherwise too large apparently) :
Docker_output.txt
Output outside of docker.txt
Logs
No response

a repo (with the dockerfile and all) is fine. But also check if this can be reproduced with Nitro only first 👍🏻

Here's a (reproduction sandbox for Nitro). 🙏


Unable to upload metadata

Hi,
I'm trying to upload metadata with a target.
The target gets uploaded and parsed by Vuforia, but no metadata is attached. Any idea?
Here is a snipped from my code which doesn't work properly
# getting a connection to Vuforia
connection = Vws::Api.new(VUFORIA_KEY, VUFORIA_SECRET)
# getting text from metadata file into metadata_content
metadata_content = File.open(Rails.root.join('public',uploaded_io.original_filename)).read
# building the new target on Vuforia
result =<EMAIL_ADDRESS>Rails.root.join('public','targets', @target.image_file_name), 100.0, true, metadata_content))

Hi
Try this fork https://github.com/goodwinproject/vws until I get a better look at this.
Thanx

Hi nkokkos,
thanks for the info, it works fine now.

Sent you a PR which fixes the metadata issue.

Merged Fixed metadata uploading and updating.
Thank you @c0m3tx !


Use pre-trained weights on custome dataset

💡 Your Question
Hi! I trained YOLO-NAS on custom dataset but my notebook crashed, now I want to train it again, but I want to use latest weights (ckpt_best.pth) . How shold I do.. hear I use
from super_gradients.training import models
model = models.get('yolo_nas_l',
num_classes=len(dataset_params['classes']),
pretrained_weights= "coco"
)
It take pretrained_weights= "coco" as arguments . how to use my checkpoints/my_first_yolonas_run/ckpt_best.pth as weight for train the model again.
Versions
No response

@Gaurav2912 Use the following command
yolo detect train resume model=/content/runs/detect/train/weights/last.pt
and also ensure that you have a complete runs folder and a custom dataset folder.

Hi @Gaurav2912, you can follow the documentation for Loading model Weights from a Checkpoint here.


recommend function in GRU4REC RNN - use only the last itme?

Hi,
Thanks for this wonderful tutorial as a beginner in this field I found it very helpful.
A question about the predict function, I suppose in sequence models like RNN the items and the direction has a meaning.
But I saw in the RNN recommender recommend function that the "pred" variable learn only from one item at a time?  and save the prediction of the last one.
    def recommend(self, user_profile, user_id=None):
        if not self.personalized:
            **for item in user_profile:
                pred = self.model.predict_next_batch(np.array([self.pseudo_session_id]),
                                                     np.array([item]),
                                                     batch=1)**
        # sort items by predicted score
        pred.sort_values(0, ascending=False, inplace=True)
        # increase the psuedo-session id so that future call to recommend() won't be connected
        self.pseudo_session_id += 1
        # convert to the required output format
        return [([x.index], x._2) for x in pred.reset_index().itertuples()]

Thanks

Hi @eveTu , happy to hear that you find this tutorial helpful! :-)
Regarding your question, the predict_next_batch in the RNN models that we considered in this codebase (GRU4Rec and HGRU4Rec) update the hidden state of the network every time an item in the sequence is passed to it.
Different sequences of items will lead to different hidden states and hence to different predictions.
The recommend() function in this case is "manually unrolling" the sequence of items in the user profile, passing each of them to predict_next_batch() in their original order to update the inner state of the RNN, and finally return the predictions returned after the last item in the user profile.
The hidden state of the RNN is automatically reset when the session identifier changes, for this reason we resorted on "pseudo session ids" to ensure that different calls to the recommend function are in fact independent.
That said, this way of operating depends heavily on the aforementioned two libraries and their batching mechanism. I suggest to take a look at the corresponding two papers to understand how and why they were built in such way.
* Recurrent Neural Networks with Top-k Gains for Session-based Recommendations, Hidasi and Karatzoglou, CIKM 2018
* Personalizing Session-based Recommendation with Hierarchical Recurrent Neural Networks, Quadrana et al, Recsys 2017

Hope that helps!

Thanks a lot
The answer really helped me


support @ suggester trigger in addition to [@

I would expect the markdown citation dropdown to be triggered by the @, but in reality, it requires [@ which is a bit cumbersome to type for every citation.
See this demo:

Another related issue is that shift+enter just goes to the next line, rather than insert the secondary markdown citation.

Any update on this, @aidenlx ?

With the recent updates, I think this and #117 are two of the main friction points remaining before Zotlit becomes the obvious choice for integrating Zotero with Obsidian. The field template, and bug resolutions, have made the literature note feature quite satisfactory, but I think due to the aforementioned issues, the citation workflow can still be improved.

Bumpy

Bump

bump

Agreed, having this option and a bit more customisability for the citation templates would be fantastic!


Accommodate new lighting and color management

We've upgraded three.js from 0.149 to 0.156. This led to changes in how colors are managed and lighting calculations are performed. To account for those changes and give a qualitatively similar experience with the default values, we've made the following changes:

Light intensity controls now have units (candela) displayed.
The old (non physical) light intensity values have been boosted to be more or less equivalent to what they were before (see documentation in code).
The color space of the background images has been corrected (to sRGB).

This change is

I would like to point out that this also affects the companion repositories.


 cannot appear as a descendant of .

I get the following two warnings when using react-portable-text:
> Warning: validateDOMNesting(...): <p> cannot appear as a descendant of <p>.
>     at p
>     at block (webpack-internal:///./node_modules/react-portable-text/dist/index.js:1:3129)
>     at BlockSerializer (webpack-internal:///./node_modules/react-portable-text/node_modules/@sanity/block-content-to-hyperscript/lib/serializers.js:14:22)
>     at div
>     at SanityBlockContent (webpack-internal:///./node_modules/react-portable-text/node_modules/@sanity/block-content-to-react/lib/BlockContent.js:19:89)
>     at v (webpack-internal:///./node_modules/react-portable-text/dist/index.js:1:1215)

and:
Warning: validateDOMNesting(...): <div> cannot appear as a descendant of <p>.
>     at div
>     at SanityBlockContent (webpack-internal:///./node_modules/react-portable-text/node_modules/@sanity/block-content-to-react/lib/BlockContent.js:19:89)
>     at v (webpack-internal:///./node_modules/react-portable-text/dist/index.js:1:1215)

I am using react-portable-text as follows:
<PortableText
  // Passing in block content straight from Sanity.io
  content={_rawBody}
  projectId={process.env.SANITY_PROJECT_ID}
  dataset={process.env.SANITY_DATASET}
/>

My content is just plan text with some line breaks.
Any suggestions on how to avoid the warning?

Without seeing either the input (_rawBody) or output JSX it's a bit hard to diagnose, but I suspect this is a case where the issue lies with something other than this library. Perhaps you have something like the following happening?
<p>
  <PortableText {…props} />
</p>


Read jsconfig.json when running .jsx files?

Feature request
Read jsconfig.json when running .js/.jsx files.
Why?
Having to rename every .jsx file to .tsx when using preact/solid/inferno just for the jsx pragma to work is a waste of time especially when in most cases its the exact same script/logic.
Alternatives

Additional context
No response

What configuration in the jsconfig.json would you like to passed in to tsx?

I think this should be looked up as a fallback if tsconfig.json doesn't exist for paths aliasing


question: how to chain an io::Error ?

Hi,
This is more a question than an issue. From reading the docs, I don't really understand how to chain errors from other crates, use foreign_links. Here, I'm trying to chain an io::Error, but this example fails to compile with a rather cryptic error. Here is the code:
#![recursion_limit = "1024"]
#[macro_use]
extern crate error_chain;

use std::net::{TcpListener, TcpStream, SocketAddrV4};
use std::time::Duration;

mod errors {
    use std::io;
    error_chain! {
        foreign_links {
            Io(io::Error);
        }

        errors {
            ConnectionFailed {
                description("Connection failed")
                display("Connection failed")
            }
        }

    }
}

use errors::*;

fn main() {
    if let Err(ref e) = run() {
        println!("error: {}", e);
        for e in e.iter().skip(1) {
            println!("    caused by: {}", e);
        }
        if let Some(backtrace) = e.backtrace() {
            println!("backtrace: {:?}", backtrace);
        }
        std::process::exit(1);
    }
}

fn run() -> Result<()> {
    let stream = connect()?;
    // do tcp stuff
    Ok(())
}

fn connect() -> Result<TcpStream> {
    let mut stream = TcpStream::connect("<IP_ADDRESS>:500").chain_err(|| ErrorKind::ConnectionFailed.into())?;
    stream.set_read_timeout(Some(Duration::from_millis(100))).chain_err(|| ErrorKind::ConnectionFailed.into())?;
    stream.set_write_timeout(Some(Duration::from_millis(100))).chain_err(|| ErrorKind::ConnectionFailed.into())?;
    Ok((stream))
}

Now the error:
error[E0282]: unable to infer enough type information about `EK`
  --> src/main.rs:47:58
   |
47 |     let mut stream = TcpStream::connect("<IP_ADDRESS>:500").chain_err(|| ErrorKind::ConnectionFailed.into())?;
   |                                                          ^^^^^^^^^ cannot infer type for `EK`
   |
   = note: type annotations or generic parameter binding required

Am I trying to do some non-sense, here?

Try the quick_main macro ;)
you don't need ErroKind::Variant.into(), you can just return ErrorKind::Variant. The closure must returns an Into<ErrorKind>,  but you do something like returning Into<Into<ErrorKind>>, so the compiler doesn't know what's the type should be after the first into()
If you use error_chain, you don't need foreign_error

Thanks @Yamakaky !

quick_main is pretty cool, adopted!
removing into() does fix my problem.
I don't understand your third point. But that's because I don't really understand that foreign_error/foreign_links are.

Mostly, your foreign_error just adds an impl From<io::Error> for Error.

All right. Simple enough. Thanks a lot :) I'm closing this.


sunrise and sunset times timezones incorrectly handled

Sunrise and sunset times from owm appear to be ISO8601 formatted times (at least loosely), but they don't specify a timezone (they are UTC).
When datetime objects are created from these timestamps, no timezone is explicitly specified, and php assumes it's my localtime.

Fixed by #21.


Input_number no longer persistent

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.57.3
Python release (python3 --version):
3.6
Component/platform:
Input_number
Description of problem:
Input_number is no longer persistent and resets all input_numbers after a reboot. This appears to have broken somewhere in 0.57
Expected:
Numbers should be persistent and survive reboots of HASS.
Problem-relevant configuration.yaml entries and steps to reproduce:
  wakeupjared_timer:
    name: Wake up Jared - Timer
    min: 0
    max: 3600
    mode: box
    unit_of_measurement: s
    icon: mdi:timer-sand

Traceback (if applicable):

Additional info:

@boojew is history enabled in your configuration.yaml?

Yes

@boojew interesting, I have just tried it with the following config and it worked:
homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets

# Show links to resources in log and frontend
introduction:

# Enables the frontend
frontend:

input_number:
  wakeupjared_timer:
    name: Wake up Jared - Timer
    min: 0
    max: 3600
    mode: box
    unit_of_measurement: s
    icon: mdi:timer-sand

# Enables configuration UI
config:

http:
  # Uncomment this to add a password (recommended!)
  # api_password: PASSWORD
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123

# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
  # Optional, allows Home Assistant developers to focus on popular components.
  # include_used_components: true

# Discover some devices automatically
#discovery:

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time
history:

# View all events in a logbook
logbook:

# Track the sun
sun:

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml

Can you give this one a try and see if it works?

Hmm. ok, not sure I quite understand why, but after removing the inputs, and re-adding them, it's working and surviving a restart. Yesterday, I was testing some configs and the values were resetting to 0 on all my input_numbers (I have 6 total) after a restart from the HASS ui or from docker, but today I can not replicate. :-/

Is the issue gone reliably? If so, would you close the issue?

Yea, totally fair


uuid in annotation

We add a UUID to annotations for payload-taskrun and signature-taskrun
"annotations": {
      "chains.tekton.dev/payload-taskrun-8c0e9bbc-192b-4ea3-8a6d-26d2ac1e0024": "eyJjb25kaXRpb25zIjpbeyJ0eXBlIjoiU3VjY2VlZGVkIiwic3RhdHVzIjoiVHJ1ZSIsImxhc3RUcmFuc2l0aW9uVGltZSI6IjIwMjEtMDUtMjFUMDk6NDI6MTFaIiwicmVhc29uIjoiU3VjY2VlZGVkIiwibWVzc2FnZSI6IkFsbCBTdGVwcyBoYXZlIGNvbXBsZXRlZCBleGVjdXRpbmcifV0sInBvZE5hbWUiOiJzYW1wbGUtcGlwZWxpbmUtcnVuLWVjaG8tc29tZXRoaW5nLWJqOHI3LXBvZC1zd3J3cyIsInN0YXJ0VGltZSI6IjIwMjEtMDUtMjFUMDk6NDI6MDRaIiwiY29tcGxldGlvblRpbWUiOiIyMDIxLTA1LTIxVDA5OjQyOjExWiIsInN0ZXBzIjpbeyJ0ZXJtaW5hdGVkIjp7ImV4aXRDb2RlIjowLCJyZWFzb24iOiJDb21wbGV0ZWQiLCJzdGFydGVkQXQiOiIyMDIxLTA1LTIxVDA5OjQyOjEwWiIsImZpbmlzaGVkQXQiOiIyMDIxLTA1LTIxVDA5OjQyOjEwWiIsImNvbnRhaW5lcklEIjoiY29udGFpbmVyZDovL2JkNzBkNDBkMGU4NThkNjc0ZDM3ZjIyMDg3NGIzODI3NzExZmE3YzEyYzBmM2I0Yjk0YTE4YTkwNDQxZTc2NjYifSwibmFtZSI6ImVjaG8iLCJjb250YWluZXIiOiJzdGVwLWVjaG8iLCJpbWFnZUlEIjoicmVnaXN0cnkuYWNjZXNzLnJlZGhhdC5jb20vdWJpOC1taW5pbWFsQHNoYTI1NjpmYzc1NTMyYTIwYzFlN2ViMDUxMmEwM2ZlYWM0NjU1NDI3OGJjZTk0NmNmNDU0YTc4ZTExNDMzZTM5YTY2ZDJkIn1dLCJ0YXNrU3BlYyI6eyJzdGVwcyI6W3sibmFtZSI6ImVjaG8iLCJpbWFnZSI6InJlZ2lzdHJ5LmFjY2Vzcy5yZWRoYXQuY29tL3ViaTgtbWluaW1hbCIsImNvbW1hbmQiOlsiZWNobyJdLCJhcmdzIjpbImhlbGxvIHdvcmxkIl0sInJlc291cmNlcyI6e319XX19",
      "chains.tekton.dev/signature-taskrun-8c0e9bbc-192b-4ea3-8a6d-26d2ac1e0024": "MEQCIHOOgvkybfaea7moBVHfhyH+BZTBVtdDkxrqiBghWkWFAiBOLuNtvR6nML7TsgddcfKRB+fnbpBpjcr+NLn/vGrFrA==",
      "chains.tekton.dev/signed": "true",
      "pipeline.tekton.dev/release": "devel"
    },

I guess there is a reason for this? I ask as it might it more cumbersome for folks to parse out the values as they will need to find the UUID or use some sort of regex or wildcard to ignore the appended uuid.

Looks like it was added in https://github.com/tektoncd/chains/pull/66! @dlorenc might know more about how necessary it is to include the UID in the annotation

It was more laziness and lack of creativity on the proper interfaces.
Objects (Taskruns and OCI artifacts right now) get signed and stored somewhere
The signatures can get stored in the Taskrun yaml itself OR a document database, etc.
The signatures need a unique key to identify them in the storage namespace.
When signatures for a taskrun get stored in the same taskrun - they don't need a unique name because it's already unique.
I couldn't figure out how to special case that cleanly.

Is it any particular storage system that needs this? Putting my database head on, there would normally be a primary key that is the unique element and requiring key constraints.
Another option would be to use the taskrun name:
tkn taskrun list
NAME                                       STARTED          DURATION    STATUS
pipeline-example-bj8r7   11 seconds ago   7 seconds   Succeeded

"annotations": {
      "chains.tekton.dev/payload-taskrun-pipeline-example-bj8r7": "payload",
      "chains.tekton.dev/signature-taskrun-pipeline-example-bj8r7": "sig",
      "chains.tekton.dev/signed": "true",
      "pipeline.tekton.dev/release": "devel"
    },

This way people have a look up value they can know the key in advance to perform a look up.

+1 to using the taskrun name, it would probably be easier for users

The taskrun name isn't necessarily unique, you can delete one and create it again, that's kind of the issue there.

understood, this is not a high prio so we can try to figure this out later. From what I can see most users will try to regex / wildcard around this, as I don't believe they can query for the UUID and then construct a value by concat'ing the taskrun name + uuid to retrieve the entry, it looks like we are adding this uuid just so its able to be stored in docdb (I might have all this wrong, so pls do correct me if so).


how to deal with merging of default dex connectors, user connectors and secrets vs configmaps

dex-operator manages connectors in the default-dex-config secret which it creates for each dex-app instance. This secret contains customer.connectors and giantswarm.connectors arrays where the default connectors are defined.
The secret is added as an extraConfig to the dex-app CR.
However, configuration can also be defined in configmaps or secrets that are referenced in config and userConfig fields of the CR.
This includes connectors.
How all these configurations are merged together is described here https://github.com/giantswarm/rfc/tree/main/multi-layer-app-config#merging-algorithm
Based on this document we were under the assumption that the userConfig (prio 100) would always take priority over the extraConfig (prio 25) created by the dex-operator. However, we have seen that in some cases where the userConfig consists of a configmap and not the secret, that the extraConfig secret can override connectors specified by the user.
We should be able to combine connectors defined in various ways without worrying that they will be overridden. This will be needed in order to offer dex-operator automation to customers who also want to have manually maintained configuration.
Includes:

[x] #1813

notes from chat with @vvondruska
possible short term action to avoid configmap being overwritten:

inspect config and if configmap exists do not reconcile / delete previously created secret - manually disable dex-operator and delete secret on installation with connectors configmap

possible long term solutions:

detect type of configuration and adapt to it. Need to think about what to do if it changes, tho
raise this in general for apps since we can have this problem with configmaps and secrets also elsewhere
tell people to define their connectors in a secret because that makes more sense anyway
create a different attribute for default dex connector configuration. this way it won't overwrite anything. this would need to be done in both dex-operator and dex-app and we would need to make sure it's updated everywhere
-we could copy and paste the user connectors to the secret managed by the operator

Let's refine our fix here and only cancel reconcillation if there is a configmap AND it contains connectors.

Added the fix, moving back to backlog for now

This might be done, Zach will take another look


Implement eth_sign RPC calls

Describe the feature
ref #1225
similar to anvil's signer impl:
https://github.com/foundry-rs/foundry/blob/master/anvil/src/eth/sign.rs
TOD

add sign trait
impl signer endpoints

Additional context
No response

yeh, for signtypeddata, we probably need to use some ethers types.
and for eth_signTransaction I'd appreciate a separate PR that basically converts a CallRequest into a signed typed tx.

Ok, so if I understood correctly, ideally this issue would be split in
2 prs? 🙂

1 PR for eth_sign + eth_signedTypedData
1 PR for eth_signTransaction, which turns a CallRequest into a Signed Typed Tx?

I've Opened a draft to check if I'm on the right track on implementing this and to get some feedback :slightly_smiling_face:

closed via #1665


Normal un-rotation

Hello! Thanks for sharing your excellent project. I found a small bug in how you correct for the rotation the algorithm applies to the sampling of the normal map.
On this line:
https://github.com/mmikk/hextile-demo/blob/main/hextile-demo/hextiling.h#L89
	d1 = mul(rot1, d1); d2 = mul(rot2, d2); d3 = mul(rot3, d3);

The code applies the same rotation to the derivatives as to the st parameter. This will have the net effect of showing a doubly-rotated normal. What you really want is to apply the inverse rotation. Since the rot matrix is orthogonal, you can simply take the tranpose of the rot matrices like so:
	d1 = mul(transpose(rot1), d1); d2 = mul(transpose(rot2), d2); d3 = mul(transpose(rot3), d3);

This seemed to work for me in my local testing.

I think I'm making a mistake somewhere else, sorry for the bother.


Create POST /primary_validator_upgrade_request endpoint

Background information
Some useful background information, banks will always set their primary validator to the node that is the:

most trusted
online
configured as a primary validator

Overview of task
When a bank alters the trust levels of their validators, if the results indicate that there are now confirmation
validators that are more trusted than the banks primary validator, the bank will send out a request to the confirmation
validators requesting one of them upgrade to a primary validator. This is because the banks always would prefer that the
most trusted validators are also the primary validator for the network.

Validator
Trust

CV_001
98.21

CV_002
93.87

PV
86.04

A confirmation validator will accept the request if they themselves have the requesting bank set as their most trusted
bank. Confirmation validators will always follow the guidance of their most trusted bank.
In order to prevent multiple confirmation validators from upgrading to primary validators at the same time (in the case that multiple CV's view that bank as their most trusted), the bank
will send out these request one by one rather than sending out several requests to all CV's simultaneously.
Starting with the most trusted CV and continuing until their current PV is reached, the bank will send out an
/primary_validator_upgrade_request where the following logic will be performed:

if the CV does not have that bank set as their most trusted bank, the CV will respond "no" to the upgrade request and
the bank will continue along with their next most trusted CV
if the CV does have that bank set as their most trusted bank, the CV will respond "yes" to the upgrade request and upgrade themselves to a PV

If and when a CV responds "yes", the requesting bank will:

break out of the loop (stop sending /primary_validator_upgrade_request)
wait for that CV to upgrade themselves to a PV
switch to their new PV

Technical details
The CV's response of "yes" and "no" will be a response with HTTP status of HTTP_200_OK for yes and HTTP_400_BAD_REQUEST for no. This will simplify the response handling of the bank due to the fact that any error (whether it be a 400 HTTP response or the CV being offline) will result in the bank moving on to the next CV in their list.

can I work on this?