HDFS-16024: RBF: Rename data to the Trash should be based on src locations

(cherry picked from commit e18d8062126951b01d04d14374cc04053167735b)
Description of PR
backport of HDFS-16024 from trunk to branch-3.3.
minor conflict resolved. The conflict is due to some code refactoring done in HDFS-15766. Not include HDFS-15766 as part of this PR (That should be done as another backport PR).
How was this patch tested?
mvn test -Dtest="TestRouterRpc"
[INFO] -------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running org.apache.hadoop.hdfs.server.federation.router.TestRouterRpc
[INFO] Tests run: 47, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 33.225 s - in org.apache.hadoop.hdfs.server.federation.router.TestRouterRpc
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 47, Failures: 0, Errors: 0, Skipped: 0

For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
7m  8s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
36m 38s

branch-3.3 passed

+1 :green_heart:
compile
0m 51s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 42s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 54s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 12s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 39s

branch-3.3 passed

+1 :green_heart:
shadedclient
24m 57s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 39s

the patch passed

+1 :green_heart:
compile
0m 34s

the patch passed

+1 :green_heart:
javac
0m 34s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 26s

the patch passed

+1 :green_heart:
mvnsite
0m 41s

the patch passed

+1 :green_heart:
javadoc
0m 57s

the patch passed

+1 :green_heart:
spotbugs
1m 20s

the patch passed

+1 :green_heart:
shadedclient
24m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 44s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

120m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4962/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4962

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 29ab37fcaf3b 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / 278374852bba7adfeb51f7fa3d2fcce709df337b

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4962/1/testReport/

Max. process+thread count
2592 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4962/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

Thanks @dineshchitlangia! I actually think it is better to keep the same jira id and the commit message across branches. Looks more consistent.

@xinglin I have been away from hadoop for a while and just getting back. Let me ask a few others on what is the agreed protocol here.
@aajisaka @jojochuang  - Do we need a new jira for cherry pick to specific branches ?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
7m  9s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ branch-3.3 Compile Tests _

+1 :green_heart:
mvninstall
37m 27s

branch-3.3 passed

+1 :green_heart:
compile
0m 53s

branch-3.3 passed

+1 :green_heart:
checkstyle
0m 43s

branch-3.3 passed

+1 :green_heart:
mvnsite
0m 56s

branch-3.3 passed

+1 :green_heart:
javadoc
1m 16s

branch-3.3 passed

+1 :green_heart:
spotbugs
1m 43s

branch-3.3 passed

+1 :green_heart:
shadedclient
24m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 40s

the patch passed

+1 :green_heart:
compile
0m 33s

the patch passed

+1 :green_heart:
javac
0m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 25s

the patch passed

+1 :green_heart:
mvnsite
0m 38s

the patch passed

+1 :green_heart:
javadoc
0m 56s

the patch passed

+1 :green_heart:
spotbugs
1m 23s

the patch passed

+1 :green_heart:
shadedclient
26m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 52s

hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

123m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4962/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4962

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux c300c2106850 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.3 / b38ef03b3a36bb22859fec94b5bcf1c171a68ab3

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4962/2/testReport/

Max. process+thread count
2473 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs-rbf U: hadoop-hdfs-project/hadoop-hdfs-rbf

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4962/2/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@aajisaka @jojochuang - Do we need a new jira for cherry pick to specific branches ?

I think no. In the past we had to reopen the jira or create a separate jira to run precommit jenkins tests for specific branches, but now we can open a separate PR to test against different branches.

Hi @dineshchitlangia,
Can we merge/commit this PR now?
Here is another small PR related with this change, https://github.com/apache/hadoop/pull/4974. Appreciated if you can take a look as well.

Merged. Thank you @xinglin and @dineshchitlangia


Partially missing title for 'Use cases' page

Clicking on 'Use cases' shows a <title> of 'Use cases | undefined'.

Nice thank you for the heads up. It was a regression.


moment.js official package should be "moment" instead of "momentjs"

modified bower, gruntfile & test config to reflect that

Great, but does this package still need to be updated/reregistered in Bower or something?
Because I just now (2016-040-02) installed angular-timer through Bower:

bower install angular-timer --save

The bower.json file in bower_components/angular-timer/bower.json still shows a momentjs dependency:
"dependencies": {
    "angular": ">= 1.0.7",
    "momentjs": "~2.9.0",
    "humanize-duration": "~2.8.0"
  },

I see that it's fixed in the current master branch. The version I get through Bower also has the same version (v1.3.3, both in package.json and bower.json)
Since I'm also using angular-moment, which does reference moment I now have duplicate folders:
bower_components/moment/ (v2.10.6)
bower_components/momentjs/ (v2.9.0)
Can I perhaps contribute something to fix this? I've already made an npm package once, but never registered it for bower, so I'm not familiar with that process yet.
A quick google indicates that initial registration is done through aL

bower register

But that seems to be only for initial registration (matched to that persons account). But reading this perhaps it's enough to just bump the version number in bower.json artificially (and better keep package.json in sync). I'm willing to try.. :). This was not done in this commit, only the package name changed...


Fix broken reusable workflow reference

Codecov Report

Merging #188 (af5d9f3) into main (85491c7) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #188   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           21        21
  Lines          714       712    -2
  Branches        82        82
=========================================
- Hits           714       712    -2

Impacted Files
Coverage Δ

src/phantom/utils.py
100.00% <0.00%> (ø)

src/phantom/iso3166.py
100.00% <0.00%> (ø)

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 85491c7...af5d9f3. Read the comment docs.


Beta v1

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Get Device IP Address.

I want to fetch IP address, when it is connected to network.

Hm, im not sure if this is a good fit for this framework. I thought of Device providing hardware related information, and while getting the current IP address might be a valid use case it's not really HW related. I'll leave this issue open for a while to let others comment and vote, but I think this is a "won't fix". Sorry to disappoint you :( or maybe you can convince me otherwise :)

No worries pal.

Can you help me for this issue by using other resource?

Sure, see http://stackoverflow.com/a/27709110/1489885 but not Rob's comment:

If by "public IP" you mean "IP address that the Internet will see me as coming from" then that is not possible to know without asking some part of the Internet. NAT does not occur on your device; it occurs on the network. Note that different devices may see you as having a different IP depending on how you route to them (including the possibility that some may see you as having an IPv4 address and other see you with an IPv6 address). "The Internet" is just one particular network; you can be on and route between many different networks w/ different IP mappings.

Thanks ★★


Release Notes v0.36.0

Release Note
This release contains 2 new features, 4 bug fixes, 1 performance improvement and 1 Documentation improvement.
🆕 Features
JAX Integration  (#1646)
You can now use JAX computations within Docarray. To do this, we introduce JaxArray as a new typing option for your documents. This type ensures that any array-like data in your Docarray documents can be processed using JAX's powerful numerical computation capabilities. Here's how you can make use of it:
from docarray import BaseDoc
from docarray.typing import JaxArray
import jax.numpy as jnp

class MyDoc(BaseDoc):
    arr: JaxArray
    image_arr: JaxArray[3, 224, 224] # For images of shape (3, 224, 224)
    square_crop: JaxArray[3, 'x', 'x'] # For any square image, regardless of dimensions
    random_image: JaxArray[3, ...]  # For any image with 3 color channels, and arbitrary other dimensions

As you can see, the JaxArray typing is extremely flexible and can support a wide range of tensor shapes.
Creating a Document with Tensors
Creating a document with tensors is straightforward. Here is an example:
doc = MyDoc(
    arr=jnp.zeros((128,)),
    image_arr=jnp.zeros((3, 224, 224)),
    square_crop=jnp.zeros((3, 64, 64)),
    random_image=jnp.zeros((3, 128, 256)),
)

Redis Integration (#1550)
Leverage the power of Redis in your Docarray project with this latest integration. Here's a simple usage example:
import numpy as np
from docarray import BaseDoc
from docarray.index import RedisDocumentIndex
from docarray.typing import NdArray

class MyDoc(BaseDoc):
    text: str
    embedding: NdArray[10]

docs = [MyDoc(text=f'text {i}', embedding=np.random.rand(10)) for i in range(10)]
query = np.random.rand(10)
db = RedisDocumentIndex[MyDoc](host='localhost')
db.index(docs)
results = db.find(query, search_field='embedding', limit=10)

In this example, we're creating a document class with textual and numerical data. Then, we initialize a Redis-backed document index and use it to index our documents. Finally, we perform a search query.
Supported Functionalities
Find: Vector search for efficient retrieval of similar documents.
Filter: Use Redis syntax to filter based on textual and numeric data.
Text Search: Leverage text search methods, such as BM25, to find relevant documents.
Get/Del: Fetch or delete specific documents from the index.
Hybrid Search: Combine find and filter functionalities for more refined search. Currently, only these two can be combined.
Subindex: Search through nested data.
🚀 Performance
Speedup HnswDocumentIndex by caching num docs (#1706)
We've optimized the num_docs() operation by caching the document count, addressing previous slowdowns during searches. This change results in a minor increase in indexing time, but significantly accelerates search times.
⚙ Refactoring
Put Contains method in the base class (#1701)
We've moved the contains method into the base class. With this refactor, the responsibility of checking for a document's existence is now delegated to individual backend implementations, using the new _doc_exists method.
More robust method to detect duplicate index (#1651)
Implemented more robust method to detect existing index for WeaviateDocumentIndex
🐞 Bug Fixes
QdrantDocumentIndex unable to see index_name (#1705)
We've resolved an issue where the QdrantDocumentIndex was not properly recognizing the index_name parameter. Previously, the specified index_name was ignored and the system defaulted to the schema name.
Fix search in InMemoryExactNNIndex with AnyEmbedding (#1696)
From now on, you can perform search operations in InMemoryExactNNIndex using AnyEmbedding
Use safe_issubclass everywhere (#1691)
Use safe_issubclass instead of issubclass as it supports non-class inputs too that helps us avoid unexpected errors
Avoid converting DocLists in the base index (#1685)
We added additional check in order to avoid passing DocLists to a function that converts list of dictionaries to a DocList.
📗 Documentation Improvements

Add docs for dict() method (#1643)
We improved documentation for BaseDoc's dict() method

🤟 Contributors
We would like to thank all contributors to this release:

Puneeth K (@punndcoder28)
Joan Fontanals (@JoanFM)
Saba Sturua (@jupyterjazz)
Aman Agarwal (@agaraman0)
samsja (@samsja)
Shukri (@hsm207)

We recommended upgrading to this version because it contains security updates.

Where are the security updates?

JaxArray is extremely flexible and can support a wide variety of tensor shapes.
You can also easily create documents with tensors. Here is an example:

In this example, we're creating a document class with both textual and numerical data. Then, we initialize a Redis-backed document index and use it to index our documents. Finally, we perform a search query.

Redis functionality supported directly in DocArray:

We now use safe_issubclass instead of issubclass because it supports non-class inputs, helping us to avoid unexpected errors


Test_recover_corrupted_swap_file is broken on 32bit systems

Describe the bug
Test_recover_corrupted_swap_file is broken on 32bit systems like x86 and 32bit arm
To Reproduce
run vim testsuite
Expected behaviour
test pass
Screenshots
From test_recover.vim:
Executed Test_nocatch_process_still_running()      in   1.010242 seconds
Executed Test_noname_buffer()                      in   0.004784 seconds
Executed Test_recover_corrupted_swap_file()        in   0.058540 seconds
Executed Test_recover_empty_swap_file()            in   0.005846 seconds
Executed Test_recover_encrypted_swap_file()        in   0.115394 seconds
Executed Test_recover_invalid_cursor_pos()         in   0.007951 seconds
Executed Test_recover_multiple_swap_files()        in   0.018030 seconds
Executed Test_recover_root_dir()                   in   0.002785 seconds
Executed Test_recover_symbolic_link()              in   0.017381 seconds
Executed Test_recover_unmodified_file()            in   0.007047 seconds
Executed Test_recover_unreadble_swap_file()        in   0.014217 seconds
Executed Test_swap_file()                          in   0.809606 seconds
Executed 12 tests                        in   2.082277 seconds
1 FAILED:
Found errors in Test_recover_corrupted_swap_file():
command line..script /home/abuild/rpmbuild/BUILD/vim-8.2.3075/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_recover_corrupted_swap_file line 69: Expected ['???LINES MISSING'] but got ['???MANY LINES MISSING']
command line..script /home/abuild/rpmbuild/BUILD/vim-8.2.3075/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_recover_corrupted_swap_file line 95: command did not fail: recover Xfile1
command line..script /home/abuild/rpmbuild/BUILD/vim-8.2.3075/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_recover_corrupted_swap_file line 97: Expected ['???'] but got ['']

Environment (please complete the following information):

8.2.3075
OS: openSUSE Tumbleweed
Terminal: linux console

Additional context

I do not have a 32 bit Unix system to try this on.  Perhaps you can check the code that's added using "little_endian" and add something similar for 32 bit systems?

I think patch 2981 is the cause of this problem ...
in my builds, 2980 and older run tests without problems, after including 2981 fails in this test

@brammool  wrote:

I do not have a 32 bit Unix system to try this on.

For information, I can build for 32-bits x86 on Ubuntu-18.04.05 x86_64 by adding -m32 in CFLAGS and LDFLAGS and by configuring without a few libs (canberra, sodium and acl) for which I do not have 32 bits versions (maybe those libs have 32-bits package, I did not bother checking, I disabled them instead):
$ cd vim/src
$ git diff Makefile
diff --git a/src/Makefile b/src/Makefile
index 0efee5195..53fe66b5d 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -619,7 +619,8 @@ CClink = $(CC)
 # Add -Wpedantic to find // comments and other C99 constructs.
 # Better disable Perl and Python to avoid a lot of warnings.
 #CFLAGS = -g -Wall -Wextra -Wshadow -Wmissing-prototypes -Wpedantic -Wunreachable-code -Wunused-result -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
-#CFLAGS = -g -O2 -Wall -Wextra -Wshadow -Wmissing-prototypes -Wpedantic -Wunreachable-code -Wno-cast-function-type -Wunused-result -Wno-deprecated-declarations -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
+CFLAGS = -g -m32 -O2 -Wall -Wextra -Wshadow -Wmissing-prototypes -Wpedantic -Wunreachable-code -Wno-cast-function-type -Wunused-result -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
+LDFLAGS = -m32
 #PYTHON_CFLAGS_EXTRA = -Wno-missing-field-initializers
 #MZSCHEME_CFLAGS_EXTRA = -Wno-unreachable-code -Wno-unused-parameter

$ ./configure
CC=gcc ./configure --with-features=huge --enable-gui=none  --disable-canberra   --disable-libsodium --disable-acl
$ make -j9
$ make test
...snip...
$ Executed:  4072 Tests
 Skipped:    66 Tests
  FAILED:     1 Tests

Failures:
	From test_recover.vim:
	Found errors in Test_recover_corrupted_swap_file():
	command line..script /home/pel/sb/vim/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_recover_corrupted_swap_file line 69: Expected ['???LINES MISSING'] but got ['???MANY LINES MISSING']
	command line..script /home/pel/sb/vim/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_recover_corrupted_swap_file line 95: command did not fail: recover Xfile1
	command line..script /home/pel/sb/vim/src/testdir/runtest.vim[473]..function RunTheTest[44]..Test_recover_corrupted_swap_file line 97: Expected ['???'] but got ['']

TEST FAILURE
Makefile:43: recipe for target 'report' failed
make: *** [report] Error 1

So I can at least reproduce the issue.
I don't have time to look at it further, but I can look further this coming weekend.

Hi,
On Wed, Jun 30, 2021 at 6:16 AM Bram Moolenaar @.***>
wrote:

Ondřej Súkup wrote:

I think patch 2981 is the cause of this problem ...
in my builds, 2980 and older run tests without problems, after
including 2981 fails in this test

That makes sense, it added the little-endian check. So the solution is
probably to disable little-endian when detecting a 32 bit system.
Not sure how to reliable do that. Or the test for little endian should
check with "!=" instead of "==", instead of:
let little_endian = b[1008:1015] == 0z33323130.00000000
use:
let little_endian = b[1008:1015] != (big-endian value)

I have created PR #8485 to address this issue.
Regards,
Yegappan


Can't start TQVault cause of System.IO.FileLoadException (tried FAQ solution)

Am i blind or something?
Auto config does not work ofc.
But what is wrong with my manual setup based on github FAQ?
I've done some resarch on closed issues but with no result.

Hi !
These placeholders are for the "Game Install Directory" Path, not the "Game Saves Directory" Path. That's the problem.

ok, it works in this config!
Can i convert somehow old .vault to .json ? :>

hi bro
i have same issue but i can not fix it
i uninstall and install but problem did not solve
it happen after i uninstall my game and install new patch in different drive
i am not pro can you help me fix this


[Bug]: Unable to download v1.4.0

NetBox access-list plugin version
v1.4.0
NetBox version
v3.6.5
Steps to Reproduce
source /opt/netbox/venv/bin/activate
(venv) ubuntu@ip-172-31-1-111:~$ sudo pip install netbox-acls==1.4.0
ERROR: Could not find a version that satisfies the requirement netbox-acls==1.4.0 (from versions: 1.0.0, 1.0.1, 1.1.0, 1.1.1, 1.2.0, 1.2.1, 1.2.2, 1.3.0)
ERROR: No matching distribution found for netbox-acls==1.4.0
Expected Behavior
Download and install version 1.4.0
Observed Behavior
Error says version 1.4.0 is not available

It appears you have to using python 3.10 or greater to use this plugin from version 1.4.0 and up. Not sure if that is right.

@jairoito cannot reproduce. I think this was a transient issue around timing. Please open a new bug if you continue to experience this problem.


Auto manage all compliant servers. Should leverage https://github.com/dell/omivv/issues/22

Requirement Breakdown
Details

Objective
The script should be able to get the required details of hosts to be managed on Compliance status of the servers and manage them for further monitoring.

Authentication/Authorization
Authenticate using vCenter credentials (Basic Authorization) and "x_omivv-api-vcenter-identifier" (UUID of the vCenter) as a mandatory header.

List of the tasks in the workflow (in   order)
Get the servers list using /Consoles/{uuid}/Compliance URICheck for servers with compliant stateGet the host ids of the server which are compliant and pass as the input for omevvServerManagement.py/createpayload

Module type: Library and/or executable
Executable

Input and format
OME IP/Name and creds, VC IP/Name and credentials

Expected output and format   Export required
Manage Job Id, Export not required

Concurrency requirement.
None

Execution model: synchronous or   asynchronous
synchronous

Applicable timeouts and retries
Attempt reaching the OME/VC upto 3 times only when the failure is on account of a network timeout. On any other types of error for instance, providing invalid input parameters, no retry should be attempted.

Expected error handing
Handle all the network and non network related errors and log them in a user friendly way.

Expected domain specific validation
As specified above

Refer PR for more details to call the function - https://github.com/dell/omivv/pull/28/files

Complete. Needs changes from branch /usr/abhishek14-Dell/omevvservermanagement before PR to master


refactor(vnode): use for-of loop instead of a for loop

Expected a for-of loop instead of a for loop with this simple iteration.

I think there are some mistakes in this test.

The use of plain for loops is intentional for better performance according to earlier benchmarks. Thank you.

The use of plain for loops is intentional for better performance according to earlier benchmarks. Thank you.
Ok, I get it! Thank you.

File Changed


Error: while building appsensor ui

I am facing error while running 7 step.

I don't familiar with the error it might be some sort of exception being generated when i run this command.I have followed all step clearly and completely. Kindly, give solution, i am setting the screenshot of the error below.

I'm honestly not sure what the error is. Can you paste the exception as text instead of a screenshot?

sure.
first a fall this came

[WARNING]

java.lang.reflect.InvocationTargetException
then

Caused by: java.lang.AbstractMethodError: ch.qos.logback.classic.pattern.EnsureExceptionHandling.process(Lch/qos/logback/core/Context;Lch/qos/logback/core/pattern/Converter;)V

after that build failure

Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:1.2.6.RELEASE:run (default-cli) on project appsensor-ui: An exception occured while running. null: InvocationTargetException: ch.qos.logback.classic.pattern.EnsureExceptionHandling.process(Lch/qos/logback/core/Context;Lch/qos/logback/core/pattern/Converter;)V


optimize images

Running all images through ImageOptim saves 1.1 MB out of 3.6 MB without losing any quality.

Nice, thanks


Deprecates EnableZipkinServer to explain custom servers are unsupported

Especially lately, we have had a large number of people having problems
with unnecessarily custom servers. Some are due to not knowing Sleuth's
stream server is obviated by our rabbit support. Some are due to blogs
which unfortunately recommend starting Zipkin in the IDE via a custom
server.
Through discussion, we decided the easiest way to let users know custom
servers are unsupported is by deprecation. Deprecation shows up in the
IDE and will alert those doing blogs or otherwise that they are
suggesting discouraged practice. It also sends a clear signal to those
who need to make custom servers that while doing so is possible, it is
something the customizer needs to accept support responsibility of.
See https://github.com/openzipkin/zipkin/issues/1962#issuecomment-375872410

thx for having a look, tommy


RepetierServer Adapter

Überarbeiteter Adapter in Version V0.0.8.

RE-CHECK!

@Baumert7269 Can you please solve the merge conflucts - and please also sort the adapter entry alphabetically in the file?

Here are my review comments. Please check and adjust them:

Please cleanup the package.json. This is one from an "installed folder". All the items with "_" needs to be removed and so
please put the admin depenednec into common.globalDependencies unless you really need admin adapter in this version on the same host as the adapter (https://github.com/Baumert7269/ioBroker.repetierserver/blob/master/io-package.json#L67-L69)
is that a common default api key or yours? if yours it should not be in io-package because wpuld be then default for all users https://github.com/Baumert7269/ioBroker.repetierserver/blob/master/io-package.json#L78
should the api key be stored encrpyted? If yes please check readme here with the dev-best-practices for instructions
your testing all fails. Please fix https://github.com/Baumert7269/ioBroker.repetierserver/actions
you maybe want to adjust the Template name? https://github.com/Baumert7269/ioBroker.repetierserver/blob/master/main.js#L110
please check the roles. value.indicator (as example) is no valid role. https://github.com/Baumert7269/ioBroker.repetierserver/blob/master/main.js#L1439 --> see here https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/stateroles.md

@Baumert7269 and please also rebase the PR. Do you need any help?

@Baumert7269 can I help you with the points in the review comment from Apollon?

@Baumert7269  How we should continue? Can we help somehow? Should we do a PR with relevant changes? But that would still require you to verify and test and release it afterwards because the changes can only be done "blind".

@Baumert7269 Happy new year, how we should proceed?

@Baumert7269 Any news on how we should continue?

Please update testing to current status. You should add git workflow test-and-release using node 16 / 18 und (optional) 20.
And please REMOVE file sources-dist-stable from this PR. Adapters MUST be available at latest some time before they are accepted at stable repository. So changeing latest and stable within one PR is not appropiate.
I would suggest to close this PR an create a new request after updateing the adapter to current status (i.e workflow, standard github test, ...)

No reaction since 2022
PR has merge conflicts
Closing this PR for now.
Please open a new PR to add this adapter to latest if desired.


Windows Real Time Scanner Driver

Hello I want to Real Time Scanner Driver Source Code for Developing Any Buddy Help Me ?

Hi @AkshayUsha
Can you please explain a little more. I am sorry, but I don't understand your request.

i want to real time antivirus scanning driver source code

After extensive enquiry, I am afraid I can only say that we don't currently have this.


instrumentation/urllib3: fix urllib3 2.0.1+ crash with many args

What does this pull request do?
In c1dd69e0a5b9d1ec020666a97e0b7cb788b86c4f we changed the logic of update_headers taking into account a new body arg before the one for headers.
The problem is that HTTPConnectionPool.urlopen did not change at all, only HTTPConnectionPool.request did so the old login update_headers was fine.
Related issues
Closes #1928

@tonyman19 need a couple more commits to get in and then I'll cut a new release


 title shows "M0#" for the month

Found this bug right here on GitHub:

Could be tied to Chrome 58.0.3029.110, but I honestly don't know.

It appears to have been fixed, so I'm closing this issue.


.NET July 2024 Update - .NET 8.0.7, .NET 6.0.32

.NET July 2024 Update
Release Notes

8.0.7
6.0.32

Status

Asset Type
8.0.7
6.0.32
Notes

Installers/Binaries
✅
✅

Snaps
✅
✅

Linux Packages (Microsoft distribution)

The list below refers to the Microsoft-provisioned feeds (packages.microsoft.com) and does not in any way represent direct availability in distros (eg RHEL, Fedora).

     Centos 7
NA
✅

     Centos 8
✅
✅

     Debian 10
✅
✅

     Debian 11
✅
✅

     Debian 12
✅
✅

     Fedora 37
✅
✅

     Fedora 38
✅
✅

     Fedora 39
✅
✅

     Fedora 40
✅
✅

     OpenSUSE 15
✅
✅

      Ubuntu 20.04
✅
✅

     Ubuntu 22.04
✅
✅

     Ubuntu 23.04
✅
✅

     Ubuntu 24.04
✅
✅

Issues
Please report any issues you find either by responding to this issue, creating a new issue or creating a new issue in one of the following repos:

ASP.NET Core: dotnet/aspnetcore
Entity Framework Core: dotnet/efcore
.NET CLI/SDK dotnet/sdk
.NET runtime dotnet/runtime
Winforms: dotnet/winforms
WPF: dotnet/wpf
NuGet: nuget/home
Containers: dotnet/dotnet-docker
Winget: microsoft/winget-pkgs

Known Issues

Hi,
dotnet-runtime-deps-8.0 has not been updated to 8.0.7 on the RHEL 9 repository https://packages.microsoft.com/rhel/9/prod:
nothing provides dotnet-runtime-deps-8.0 >= 8.0.7 needed by dotnet-runtime-8.0-8.0.7-1.x86_64 from packages-microsoft-com-prod
It is a dependency for aspnetcore-runtime and dotnet-runtime

Hello,
The sdk docker images are still on 8.0.303, is there an ETA on those?
Thanks

The latest SDK is 8.0.303, which contains the 8.0.7 runtime.
https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Currently trying to upgrade from <IP_ADDRESS>80 to <IP_ADDRESS>14 on a Windows Server 2019 standard build 17763.6054 and getting the error below:

I am using the hosting package (dotnet-hosting-8.0.7-win.exe)
I can uninstall and reinstall version <IP_ADDRESS>80 without any issues. Any ideas what is causing the issue?

closing in favor of https://github.com/dotnet/core/issues/9447


⚠ ClamAV has degraded performance

In 16f6cc1, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 84 ms

Resolved: ClamAV performance has improved in 820c16f.


Ask; Why don't build directly, not copying go module file?

Current Dockerfile:
FROM golang

ENV CGO_ENABLED=0
ENV GO111MODULE=on

WORKDIR /go/src/flog

COPY go.mod go.sum ./
RUN go mod download

COPY . ./
RUN go build -o /bin/flog

FROM scratch
COPY --from=0 /bin/flog /bin/flog
ENTRYPOINT ["flog"]

But we can build binary file directly like this:
FROM golang

ENV CGO_ENABLED=0
ENV GO111MODULE=on

WORKDIR /go/src/flog

COPY . ./
RUN go build -ldflags="-w -s" -o /bin/flog

FROM scratch
COPY --from=0 /bin/flog /bin/flog
ENTRYPOINT ["flog"]

Is there any problem to build binary file directly? I know it's not essential or critical point, but I want to make it simpler. Thanks for reading.

Pre-downloading the modules makes the image layer with Go module caches. With the module cache, we don't have to re-download the modules if there are no module changes, then we can only build source code.


Understanding to the "SampleNetwork" module

Hi there, really nice work!
And I'm trying to understand this line code, it looks different from Eq.3 of the main paper,  the "surface_output, surface_sdf_values" seems are the same value and it would be really helpful if you could explain it more. Thank you in advance!

Hi, thanks :)
You are right, it is a small issue (can be viewed as some implementation detail) which we did not describe in the paper.
First, note that : surface_sdf_values = surface_output.detach()
Meaning only one variable is in the computational graph.
Plug in :  surface_output - surface_sdf_values
Instead of surface_output
Will give us the desired property of the function x(theta, c, v) (described in equation 3) which is:
x(theta0, c0, v0) = x0
Meaning the function is correct with respect to the current state.
This handles the case when surface_output is not exactly zero, meaning that the point x is on some s-levelest, so this correction will lead to the correct derivation.
Differentiate f(x;theta) = s ,as shown in section C in the appendix, will result the same.
Partially, it is not always guaranteed that s=0, but we do know it is very close as a result of our ray-marching algorithm.
In fact, this idea based on a former paper from our lab (https://arxiv.org/abs/1905.11911) where we developed the formula of how to control general s-levelsets of the network f.
It might have seen only as a numeric issue, since really the values surface_output are indeed close to zero, but this kind of correction is a more accurate implementation to eq 3.
Hope it clears your concern!

Hi lioryariv, thanks for your timely reply, sounds really interesting, I will take a look at the paper.


Type-safe way to force caller to check Ok/Err Result values

Hi,
In the static languages that inspire this package, the default way of accessing values is only allowed once you've checked a Result is Ok:
return actuallyAnErr.value # type error!

However, in this package, because Ok and Err both share .value, this is by default allowed, and the user is not forced to check that a result is ok.
return actuallyAnError.value # fine, but will confuse the hell out of the caller because we just swallowed an error!

Could you consider "blessing" an accessor for value that only exists on Ok, to allow this usage? (Or rename .value on Err to .value_err or something, but that would be another big breaking change...)
Thanks for all your work on this package, I use it in a bunch of places.

return actuallyAnErr.value # type error!

 Or are you merely hinting that actuallyAnErr is an Err type?
Either way, so the suggestion is
anError = Err('this is an error')
anOk = Ok('this is okay')

# Remove `.value` accessor on Err -- should be instead throw TypeError here as opposed to just removing?
anError.value

# Add `.value_err` accessor
anError.value_err

anOk.value_err # this doesn't exist or should it throw TypeError?
anOk.value === 'this is okay'

Would definitely impact anyone relying on current .value behavior.

return actuallyAnErr.value # type error!

 Or are you merely hinting that actuallyAnErr is an Err type?

Library should throw a type error or attribute error, more importantly the definition should be written in a way that mypy flags this as an error.
As an alternative to breaking everybody's .value usage, you could create accessor properties e.g. .ok_value, .err_value that people could opt into using.  .value could potentially be deprecated at a later date.

Actually perhaps what you're after is already implemented,
# These two are for the Err variant, you can imagine the Ok variant being just the flipping of the implementation of these two

    def unwrap(self) -> NoReturn:
        """Raises an `UnwrapError`."""
        raise UnwrapError(self, "Called `Result.unwrap()` on an `Err` value")

    def unwrap_err(self) -> E:
        """Return the inner value"""
        return self._value

Very nearly - it's implemented in terms of throwing an error, but it's not implemented in a way that mypy can prevent you doing that in the first place. Maybe to step back a bit, what I want is that
res = getResult()
value = res.value # mypy should flag this line as not ok

res = getResult()
if isinstance(res, Ok):
  value = res.value # mypy should let me do this.

where .value can be replaced by any method of accessing the contents, .unwrap, .val, etc.
This is how results works in Rust, F#, etc - they use the type checker to force you to check if they are ok before accessing.

This is how results works in Rust, F#, etc - they use the type checker to force you to check if they are ok before accessing.

value = res.value # mypy should flag this line as not ok

+1
sounds like a general type checking improvement then. I have no idea how to do that with mypy off the top of my head, I'd have to dive into the docs and experiment. But if you know mypy better, please feel free to throw up a PR

Sound like type narrowing/discriminated union/tagged union. Does mypy handle that?

It actually does, but we don't get to benefit from it here because .value exists on both Ok and Err so mypy allows it to be called on Union[Ok, Err].
So if we used (bikeshedding names) .ok_value and .err_value on Ok and Err, respectively, mypy would disallow res.ok_value if you hadn't already checked that isinstance(res, Ok).

I've taken the discussions here, because I've had the same annoyance with type checkers complaining about Ok being of type str | None instead of str, and created a fork that is breaking compatibility with the upstream repo in many ways.
https://github.com/felixhammerl/resultify
Since Python does not have the pattern matching capability of Rust, Python's intepretation of Optional is not compatible with Rust's and it does not quite make sense in my opinion to treat them equally.

ok, let's try to get this one into motion 🙃
rust and its std::Result type (https://doc.rust-lang.org/std/result/) have two crucial properties:

special syntax to propagate Err results to the caller: ? (question mark)
#[must_use] to force callers to actually check the value.

neither are available in python, so this cannot be translated directly.
but having a type-safe way to use Result (mypy rejecting it as the rust compiler would reject it) is definitely useful. one step in that direction is

#69

...but it is not currently usable, and while this would achieve type narrowing, it would not cover all use cases: the .value accessor currently works on both Ok[T] and Err[E], and they may be the of the same type (or the attempted operation would work on both T and E), so this would not force callers to do the right thing.
this means this would still not provide a way to  guarantee that the Result return value is correctly checked by the caller.
i see a few paths forward:

add additional separate accessors

e.g. .ok_value and .err_value as suggested in https://github.com/rustedpy/result/issues/37#issuecomment-809814134
(note: exact names bike-sheddable)
the .value accessors on both Ok and Err raise a Warning, encouraging users to use .ok_value and .err_value instead, while keeping existing code working
pro: explicit
con: verbose and (ok, subjectively) ugly and not so elegant
con: .value would still be there; users will (accidentally) keep (ab)using it even though they shouldn't because warnings are just that, and not everyone has them show up (or reads them) in their CI systems, and even fewer downstream consumers would turn warnings into actual errors in their CI builds.

only have Ok.value, not Err.value, and have Err.err_value instead.

(note: exact names bike-sheddable)
pro: clean API that leaves no doubt what is intended
pro: no opportunity to not do the right thing: Err.value would simply not work anymore, and type checkers will tell you that.
con: breaks API compatibility, which will break for many existing users. sure, (pre-1.x) version numbers don't mean anything and semver is mostly moot anyway, but it's still a very breaking change
the Err.value accessor could raise DeprecationWarning for a while before it goes away, but tbh i think it's not the worth the hassle and planning ahead for a small and not-very-new-anymore-and-actually-used-in-practice project like this.

wild idea: ‘special semi-syntax trick’:

make Ok instances callable, but not Err instances:res = do_something()
do_something_with(res())  # only typechecks for `Ok`, fails for `Err`

pro: very short, bit like the special ? syntax in rust (but for the happy path, not the error path)
con: confusing
con: not that different from less confusing but more verbose .ok_value

personally i think that option 1 is the most reasonable, but i am not overly enthusiastic to encourage using the rather verbose and slightly ugly res.ok_value as the best pattern to use this library.

In my opinion, the reason many people love rust is because the compiler forces you to do the right thing. The closest thing Python has to that experience is via typing analysis. If the intention of this library (and the rustedpy org) is to bring the joys of coding in rust to the Python ecosystem, I think our target audience is probably also people using mypy/pyright or some other sort of type checking analysis.
For these users, the best developer experience is unfortunately the one that will break existing API compatibility:

only have Ok.value, not Err.value, and have Err.err_value instead.

I think its worth it

Okay, so the proposal in #99 is,

Deprecate value, deprecation warning for 1 or more releases, then raise exception on usage, then total removal
Add value and err_value properties that exist only on Ok and Err respectively

Any objections to this? Any better ideas?

Ending up with value and err_value sounds great, deprecating Err.value in the interim makes sense. (deprecating Ok.value doesn't make sense of course :)). You'd still need a major version bump when you finally remove Err.value as well if you follow semver.

when you make Err.value raise an exception on usage

nope, it wouldn't even exist. python will raise AttributeError at runtime, but type checkers will just complain that .value doesn't exist

It's now possible to force people to check errors using Python 3.10 and Pyright. This combination enables true exhaustiveness checking.
Here's a very simple Result implementation that does force the user to always handle the error case:

Making the value private: https://github.com/dogweather/python-exhaustiveness-adts-monads/blob/master/src/adt_3_result_monad.py
Accomplish the same thing w/out private variables: https://github.com/dogweather/python-exhaustiveness-adts-monads/blob/master/src/adt_2_result.py#L93-L110

Is there a reason we've decided to keep value around at all?
Isn't the idiomatic thing to force callers to use ok/err? Given they are variant specific, they're returning an Ok or Err in a type safe manner already.
Introducing a ok_value/err_value...what exactly is that giving us that ok/err aren't already.
If anything, value, which looking at the history of this library, is a artifact from the very first version of this library, should be deprecated-and-removed or removed right away since most people would be using a type checker with this library -- you'd hope so.
@wbolster does what I've said make sense? Let's just deprecate/remove value and let callers use ok/err.

I've made a preview release with this included, if everything looks okay, it will be made into 0.11.0 in the near future
https://pypi.org/project/result/0.11.0rc1/


Add Field class

Fixes #9
@roll, @pwalsh - Does this chime with your expectations in #9?

Coverage increased (+0.05%) to 98.705% when pulling fbe476483532f863bc553aab917fd3081dc37133 on feature-add-field into d03825ef403d2961fd000e103987343ba978ab1d on master.

Coverage increased (+0.05%) to 98.705% when pulling 98b9a309abad6dacc08653f58e34498e112d6492 on feature-add-field into d03825ef403d2961fd000e103987343ba978ab1d on master.

Coverage increased (+0.05%) to 98.705% when pulling 993c9fe8b8f4f3853e267a0934d1b9d3743291dd on feature-add-field into d03825ef403d2961fd000e103987343ba978ab1d on master.

@roll The schema and field connections are defined in https://github.com/theodi/jsontableschema.rb/blob/feature-add-field/lib/jsontableschema/model.rb - which is a Ruby module which is included in schema.rb - I've split a lot of things out into modules, which keeps things neater.


feat: MLOPS-288 - use kaniko to improve wanna-ml cloud builds

Describe your changes
Update cloud build step to use the recommended kaniko flow that leverages cached layer in the registry
Issue ticket number and link
MLOPS-288
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] If it is a core feature, I have added thorough tests.

Codecov Report
Patch coverage has no change and project coverage change: -0.03 :warning:

Comparison is base (8b9d240) 74.16% compared to head (448523c) 74.14%.

:exclamation: Current head 448523c differs from pull request most recent head c793d49. Consider uploading reports for the commit c793d49 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #84      +/-   ##
==========================================
- Coverage   74.16%   74.14%   -0.03%
==========================================
  Files          57       57
  Lines        2795     2796       +1
==========================================
  Hits         2073     2073
- Misses        722      723       +1

Impacted Files
Coverage Δ

src/wanna/core/services/docker.py
64.45% <0.00%> (-0.31%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add old map item

The old map can be discovered in the Study Room after correctly answering the quiz question. The old map hints at secret pathways within the ZDD.

The story doesn't start after entering the room.

You are only asked whether you want to exit the room or inspect it.

@Marcel-H1 now it shall function (hopefully i tried and it worked) . sorry for the inconvenience. i apprarently edited the room branch and forget to edit the item branch.

@Jonah-gr Ready to be merged


How to limit the time in showTimePicker

Can you help a way to limit yourself as time? no data picker exists the predicate day selectable, but I did not find anything like it in the time picker.

What do you mean by "limit the time picker"? Do you want to limit the user to only pick a time between, say, 7am and 6pm? Or something different?

any news on this?

This is a must. Hope we get news soon.

Hi, is there any new updates for this?

Bump on this, trying to create two timer pickers that are linked. If I pick a date on the start time, it needs to affect the end time options.
If I select the time on time A @ 4pm then time B must not be able to select 3pm - there is also cases where one time selector is required but it cant be earlier than the current time

Bump this, i'm using this to let the user schedule a notification, but anything past 3 hours breaks business rules on this case.

Any updates on this? There should be a way to limit selected time to only times before current time.

Functionality is really necessary.

There is a selectableDayPredicatefor showDatePicker, so a selectableTimePredicate for showTimePicker would be really great.

Maybe something like a list of allowed hours and a list of allowed minutes would be good.
like
showTimePicker(
        context: context,
        initialTime: TimeOfDay.now(),
        allowedHours: [8,9,10,11,12, 15,16,17],
        allowedMinutes: [0,10,20,30,40,50],
        displayDisabledValues: true
);

Then we can restrict users also to a minimum time resolution (every 15 minutes, half an hour or alike).
displayDisabledValues would be a bool to either hide disabled hours or minutes, or display them (greyed out = unselectable).

I copied the source and adapted it to show only a given List of TimeOfDay and changed some logic around converting the angle to a time. It’s both in code and visually a mess because restricting for example to a range from 08:00 to 18:00 in 15 minute intervals distributes the am hous and pm hours equally around its ring and that looks really odd in the material time picker.
Nevertheless, the approach I built for my company works but I think I could make a PR with the predicate solution in my spare time since I would like to do it completely different.
@Chris1234567899 what if you want to restrict the time range from 09:15 to 16:30? In your approach that wouldn’t work.

@sclausen Would you be willing to share your code?  I'm currently trying to limit the time selection to 15 minute increments using the time picker. It would be nice to see what you've done.

@sclausen Would you be willing to share your code? I'm currently trying to limit the time selection to 15 minute increments using the time picker. It would be nice to see what you've done.

Sorry for the long delay. I needed permission from my superior and I let it slide a litte.
I warned you about the quality! https://gist.github.com/sclausen/b97e96f33373b8cdc33fcd7bb6f6dfe7

great!  thank you very much!
On Thu, May 28, 2020 at 10:09 AM Sebastian Clausen<EMAIL_ADDRESS>wrote:

@sclausen https://github.com/sclausen Would you be willing to share
your code? I'm currently trying to limit the time selection to 15 minute
increments using the time picker. It would be nice to see what you've done.
Sorry for the long delay. I needed permission from my superior and I let
it slide a litte.
I warned you about the quality!
https://gist.github.com/sclausen/b97e96f33373b8cdc33fcd7bb6f6dfe7
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/23717#issuecomment-635409892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSJF4WNWOCMI62X6HRTZ5DRTZ5A5ANCNFSM4GAFAGUQ
.

long time.! still issue not fixed. this is really needed functionality

@sclausen Thanks for your code, but there is a problem with it, when you enter the whole hours of the day, the number 12 will repeat twice

@sclausen Thanks for your code, but there is a problem with it, when you enter the whole hours of the day, the number 12 will repeat twice

That’s bad. Do you have a fix for this?

I am still looking for a solution to this problem, this is a must-have feature in this library. Please, mates, add this feature.

Bump! 🙄

Bump!

Yep would be a great feature to be implemented

Bump!!!

Bump!!!!!

Please mates, add this feature.

Bump!

using this temporal solution...
https://pub.dev/packages/time_picker_widget

Bump!

Bump!

Bump!

Bump!

Bump!

Bump!

Bump!

Bump!

Bump!
Just as DatePicker, I need a firstDate and lastDate parameters, but for TimePicker.

Bump!
Just as DatePicker, I need a firstDate and lastDate parameters, but for TimePicker.

Bump!

Bump!

A really necessary feature. Hope this will get added soon!

When to expect this man??!!!!!!
Basic feature.

Bump!

Yes, this is a very neccessary feature to schedule ranged timetables.  To create something like this:-

Without this, I'm forced to show popups to users showing that the selected time can't be set which creates bad UX.
I hope that the team is already working on a solution as the issue is quite old. Bump!

Bump!

Bump!

any updates?

Bump!

Another bump!

bump!

Bump!

Bump!

I'd love this too

Bump, please!

bump!

This is necessary!

There isn't any guidance for this from Material unfortunately. It does seem like a tricky problem to solve.
An alternative could be building something custom with a dropdown menu that only shows the allowed times for hours/minutes.

So long

An alternative could be building something custom with a dropdown menu that only shows the allowed times for hours/minutes.

I don't think a dropdown would look so good -

juste hide the times outside of intervals or snap like so ?

Hey folks,
After speaking with designers on the Material team, it's been decided that limiting selection on the TimePicker is not something we want to support officially. We see the time picker UI as something similar to a slider, so having disabled values within that would be confusing.
My recommendation is to either handle the validation of the time after the user taps OK or to build something custom (using dropdowns or existing packages or whatever).
The Material team is in the early phases of designing/creating a more desktop appropriate time picker selection UI (that might involve dropdown-like behavior). Once that is in a more solidified state, it could be something we add to Flutter as a new widget.
That being said, I'm going to close out this issue. Thanks for all the feedback and important discussion!

Hey folks,
After speaking with designers on the Material team, it's been decided that limiting selection on the TimePicker is not something we want to support officially. We see the time picker UI as something similar to a slider, so having disabled values within that would be confusing.

I don't see how it would be confusing to the user not being able to pick hours outside of working hours if it fits the context - what is confusing is being able to pick a dentist appointment at midnight making TimePicker unusable for many use cases...

@rami-a
I don't understand the use of the Slider widget as an example. It contradicts the point you want to make. When we create a Slider we can literally set a min-max value with divisions. So for example:
Slider(
  value: _currentSliderValue,
  min: 0,
  max: 100,
  divisions: 5,
  label: _currentSliderValue.round().toString(),
  onChanged: (double value) {
    setState(() {
      _currentSliderValue = value;
    });
  },
),

Here we limit the user by not allowing it to pick a value below 0 or above 100. And within the set range we limit the user to only pick 0, 20, 40, 60, 80 or 100. Which is what we also want for the TimePicker widget.
Allowing users to only pick in intervals of 5 or 10 minutes is UI wise very clear. Don't grey out the options you can't pick, but simply don't show them. Sof or the 10 minutes interval option you would omit the 5, 15, 25, etc labels and let the picker snap to the closest 10 minute interval.
For the selectable range I can understand it can look weird in the current TimePicker widget. However, isn't that up to the developer to manage functionality and visuals?
Other widgets don't limit the developer to make them visually unpleasing or hard to use for users:
I.e. I can take a ListTile widget and add huge or no paddings to it making it look bad. I can use the same highlightColor as backgroundColor for the ListTile widget; making it unclear for the user the ListTile is tappable.

Hey folks,
After speaking with designers on the Material team, it's been decided that limiting selection on the TimePicker is not something we want to support officially. We see the time picker UI as something similar to a slider, so having disabled values within that would be confusing.
My recommendation is to either handle the validation of the time after the user taps OK or to build something custom (using dropdowns or existing packages or whatever).
The Material team is in the early phases of designing/creating a more desktop appropriate time picker selection UI (that might involve dropdown-like behavior). Once that is in a more solidified state, it could be something we add to Flutter as a new widget.
That being said, I'm going to close out this issue. Thanks for all the feedback and important discussion!

That is very wrong thinking. I dont think the design team really understand the logic behind the TimePick widget. By compare this with slider. I'm 100% sure you guys DO NOT know about the need of this widget to Developers and also users. Why does a neccesary function would be confusing?? I dont get it


Added support for linear color space PNG writing

I noticed that if srgb is not set for the texture formet, the PNG writer will still put an sRGB/RenderingIntent into the PNG header, and will not have a correct gamma value of 1.0. I added code that works for my application.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

We haven't needed to test other image type code paths. We are using DirectXTex to test our rendering pipeline by dumping out various intermediate render stages and comparing to reference images as part of an automated test suite.  I believe that most viewers, in absence of an explicit gAMA chunk, will assume sRGB gamma. (Some, like IE and the windows photo viewer, always assume sRGB gamma, even with the gAMA chunk)
I may have some spare cycles this week to test, so to make sure I'm testing what you want, I'll list what I think I should test this week, please let me know if there are other test cases you want explored.

Test removing the sRGB chunk but no gAMA chunk in PNG
see what existing functionality does with jpeg and tiff output with a 16 bit linear texture input.
Is that right?

I will try to run some tests in the next few days and will get back to you with the results.
Ideally we would be able to specify the gamma value, but for our usage, we know it's supposed to be gamma 1.0, and our reference images do have a gAMA 1.0 chunk set.


WIP: db model ports

Can you check over what I've got so far with factory bot and if it's in-line with how y'all normally do things? Specifically linting the factories vs putting an expectation in the spec? I prefer the latter because linting all the factories before the test run can prevent the tests from running if a factory is invalid—which sometimes is undesirable if you're actively working on validations and associations

Adam and I talked about this over chat, no need for this PR anymore


command executes successfully. But proxy doesn't work

@ArtixZ - could you provide more details as to what commands you ran and the output you are seeing (I don't have an issue template setup for this repo unfortunately)? Also, if you could test the previous version https://github.com/dan-v/awslambdaproxy/releases/tag/0.0.7 that would help rule out a lot of things.

@dan-v Thanks for replying really quick.
[ec2-user@ip-172-31-16-116 ~]$ ./awslambdaproxy run -r us-west-2,us-west-1,us-east-1,us-east-2 2019/07/12 22:13:02 Setting up Lambda infrastructure
2019/07/12 22:13:02 Setting up Lambda function in region: us-west-2
2019/07/12 22:13:05 Setting up Lambda function in region: us-west-1
2019/07/12 22:13:08 Setting up Lambda function in region: us-east-1
2019/07/12 22:13:09 Setting up Lambda function in region: us-east-2
2019/07/12 22:13:11 Starting sshManager
2019/07/12 22:13:11 Generated SSH key:  ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCy6vdyP4AZPVPWikQldT3YYzR1WeZAsMsnmVYBVleVj+kZUpiOhHHN4w8IyDluClcud4BEsezi+9G2riZVBcn9Na/1v6v83PMz379nRCyVXGp1HoNxer7cyaLgMWqZL/yhzf/n9g/F9NiCLqnGogNVs2/ezhE81mHIxeVPEGCwv/4yfEWMejxZhYftS+W74N1B1lbCcxBoZ+JNTgIZJt0dz+OBISxlW2la1/CT96IkHjcpxw1vA1QEIpC/wbQ0ZpTOjI688Gn9JitJfq9DkUBpt0pnzKALZamFG+bK6ge7joXrSmyHTKlQFY/XfpTWSEuvbpxVBeC2xBt35GZZTjVr
2019/07/12 22:13:11 Added entry to authorized keys file  /home/ec2-user/.ssh/authorized_keys
2019/07/12 22:13:11 Starting connectionManager
2019/07/12 22:13:11 Started user listener on port 8082
2019/07/12 22:13:11 Started tunnel listener on port 8081
2019/07/12 22:13:11 Starting lambdaExecutionManager
2019/07/12 22:13:11 #######################################
2019/07/12 22:13:11 Proxy IP:  <IP_ADDRESS>
2019/07/12 22:13:11 Listeners:  [admin:awslambdaproxy@:8080]
2019/07/12 22:13:11 #######################################
2019/07/12 22:13:11 Using public IP <IP_ADDRESS>
2019/07/12 22:13:11 Lambda execution frequency 14m20s
2019/07/12 22:13:11 Executing Lambda function in region us-west-2
2019/07/12 22:13:12 Waiting for tunnel to be established..
2019/07/12 22:13:12 Accepted tunnel connection from <IP_ADDRESS>:44606
2019/07/12 22:13:12 Established session to <IP_ADDRESS>:44606
2019/07/12 22:13:12 Active tunnel count:  1
2019/07/12 22:13:12 ---------------
2019/07/12 22:13:12 Connection: <IP_ADDRESS>:44606
2019/07/12 22:13:12 Start Time: 2019-07-12 22:13:12.811664585 +0000 UTC m=+10.283300012
2019/07/12 22:13:12 Total Streams: 0
2019/07/12 22:13:12 ---------------

This is the log I see. I tried admin:awslambdaproxy@<IP_ADDRESS>:8080 proxy. But no internet connection.
I'm going to try 0.0.7 version.
Thanks again for this amazing project!

One way to validate if proxy is working or not would be to use curl from the same host where the proxy is running, something like curl -x socks5://admin:awslambdaproxy@<IP_ADDRESS>:8080 http://checkip.amazonaws.com. This should give you a different IP address than the EC2 instance you are running.

It's fixed now. Actually it's because I didn't open 8080 port in the security group.
I observed another issue - the program hangs at here:
2019/07/13 17:25:15 ---------------
2019/07/13 17:25:31 Tunnel <IP_ADDRESS>:49274 is safe to close
2019/07/13 17:25:31 Removing tunnel <IP_ADDRESS>:49274

It likely is not hanging there, but by default it will only execute a new function ~15 minutes, so you won't see much activity in the output.


Startup failed on Windows with check_model failed

Startup failed with following error

The format of the pathlib is different on Linux and Windows.

Try the latest commit.


Promoting a TestFlight build to App Store Review hangs on "Selecting build"

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

In our process, we always use an existing TestFlight build to be submitted to App Store review after final testings. Part of this process is to submit a specific existing TestFlight build to App Store review using Deliver.
This worked perfectly until some months ago, but stopped working with a recent release (unfortunately I don't know which Fastlane version worked last).
When the deliver command is executed, everything works fine until the build becomes selected. This is where the script stops. The script does not confirm the selection of the build with the expected "Successfully selected build" message.
I already tried changing the parameters that are given to the deliver command and reduced them to the minimum, but it always stops when it is about to select the build.
After executing the command all information is right in App Store Connect, even the build is correctly selected, but somehow Deliver does not recognize it, so it cannot "push the submit button" for us.
Command executed

deliver(
    app_version: <version>,
    build_number: <build_number>,
    phased_release: <phased_release_option>
)

other options are taken from Deliverfile:
app_identifier <bundle_id>
submit_for_review true
automatic_release false
skip_screenshots true
skip_binary_upload true
platform "ios"
metadata_path "fastlane/metadata/appstore"
team_id <our_team_id>
dev_portal_team_id <our_dev_portal_id>

Complete output when running fastlane, including the stack trace and command used

[20:15:23]: ---------------------
[20:15:23]: --- Step: deliver ---
[20:15:23]: ---------------------
[20:15:23]: Successfully loaded '/Users/#REDACTED#/fastlane/Deliverfile' 📄
+--------------------+----------------------------+
|  Detected Values from './fastlane/Deliverfile'  |
+--------------------+----------------------------+
| app_identifier     | #REDACTED#                 |
| submit_for_review  | true                       |
| automatic_release  | false                      |
| skip_screenshots   | true                       |
| skip_binary_upload | true                       |
| platform           | ios                        |
| metadata_path      | fastlane/metadata/appstore |
| team_id            | #REDACTED#                 |
| dev_portal_team_id | #REDACTED#                 |
+--------------------+----------------------------+
[20:15:23]: Login to App Store Connect (#REDACTED#)
[20:15:25]: Login successful
+--------------------------------------+----------------------------+
|                      deliver 2.175.0 Summary                      |
+--------------------------------------+----------------------------+
| app_version                          | 7.10.1                     |
| build_number                         | 50214                      |
| phased_release                       | true                       |
| screenshots_path                     | ./fastlane/screenshots     |
| username                             | #REDACTED#                 |
| app_identifier                       | #REDACTED#                 |
| platform                             | ios                        |
| edit_live                            | false                      |
| use_live_version                     | false                      |
| metadata_path                        | fastlane/metadata/appstore |
| skip_binary_upload                   | true                       |
| skip_screenshots                     | true                       |
| skip_metadata                        | false                      |
| skip_app_version_update              | false                      |
| force                                | false                      |
| overwrite_screenshots                | false                      |
| submit_for_review                    | true                       |
| reject_if_possible                   | false                      |
| automatic_release                    | false                      |
| reset_ratings                        | false                      |
| team_id                              | #REDACTED#                 |
| dev_portal_team_id                   | #REDACTED#                 |
| run_precheck_before_submit           | true                       |
| precheck_default_rule_level          | warn                       |
| ignore_language_directory_validation | false                      |
| precheck_include_in_app_purchases    | true                       |
+--------------------------------------+----------------------------+
[20:15:29]: Making sure the latest version on App Store Connect matches '7.10.1'...
[20:15:30]: '7.10.1' is the latest version on App Store Connect
[20:15:30]: Loading 'fastlane/metadata/appstore/de-DE/release_notes.txt'...
[20:15:31]: Verifying the upload via the HTML file can be disabled by either adding
[20:15:31]: force true to your Deliverfile or using fastlane deliver --force
/usr/local/lib/ruby/gems/2.7.0/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
[20:15:31]: Does the Preview on path './fastlane/Preview.html' look okay for you? (y/n)
/usr/local/lib/ruby/gems/2.7.0/gems/highline-1.7.10/lib/highline.rb:624: warning: Using the last argument as keyword parameters is deprecated
y
[20:15:34]: HTML file confirmed...
[20:15:37]: Will begin uploading metadata for '7.10.1' on App Store Connect
[20:15:37]: Uploading metadata to App Store Connect for version
[20:15:41]: Uploading metadata to App Store Connect for localized version 'de-DE'
[20:15:44]: Uploading app review information to App Store Connect
[20:15:45]: Running precheck before submitting to review, if you'd like to disable this check you can set run_precheck_before_submit to false
[20:15:45]: Making sure we pass precheck 👮♀ 👮 before we submit  🛫
+--------------------------+-----------------------+
|           Summary for precheck 2.175.0           |
+--------------------------+-----------------------+
| default_rule_level       | warn                  |
| include_in_app_purchases | true                  |
| app_identifier           | #REDACTED#            |
| username                 | #REDACTED#            |
| platform                 | ios                   |
| team_id                  | #REDACTED#            |
| use_live                 | false                 |
+--------------------------+-----------------------+
[20:15:45]: Checking app for precheck rule violations
[20:15:59]: Reading in-app purchases. If you have a lot, this might take a while
[20:15:59]: You can disable IAP checking by setting the include_in_app_purchases flag to false
[20:16:00]: Done reading in-app purchases
[20:16:01]: ✅  Passed: No negative  sentiment
[20:16:01]: ✅  Passed: No placeholder text
[20:16:01]: ✅  Passed: No mentioning  competitors
[20:16:01]: ✅  Passed: No future functionality promises
[20:16:01]: ✅  Passed: No words indicating test content
[20:16:01]: ✅  Passed: No curse words
[20:16:01]: ✅  Passed: No words indicating your IAP is free
[20:16:01]: ✅  Passed: Incorrect, or missing copyright date
[20:16:01]: ✅  Passed: No broken urls
[20:16:01]: precheck 👮♀ 👮  finished without detecting any potential problems 🛫
[20:16:01]: Selecting existing build-number: 50214
[20:16:02]: Selecting build 7.10.1 (50214)...
^C <--- here we cancel with CTRL+C as the script stucks.
+----------------+---------------------+
|             Lane Context             |
+----------------+---------------------+
| PLATFORM_NAME  |                     |
| LANE_NAME      | submit_to_app_store |
| VERSION_NUMBER | 7.10.1              |
| BUILD_NUMBER   | 50214               |
+----------------+---------------------+
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | ensure_bundle_exec         | 0           |
| 3    | git_branch                 | 0           |
| 4    | get_version_number         | 0           |
| 5    | get_build_number           | 0           |
| 6    | git_branch                 | 0           |
| 7    | deliver                    | 50          |
+------+----------------------------+-------------+
[20:16:14]: fastlane finished with errors
Cancelled... use --verbose to show the stack trace

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
11.2.1

Ruby
2.7.2

Bundler?
true

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/lib/ruby/gems/2.7.0/bin/fastlane

Host
macOS 11.2.1 (20D75)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.7.2/lib

OpenSSL Version
OpenSSL 1.1.1g  21 Apr 2020

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.4

System Locale

Variable
Value

LANG
de_DE.UTF-8
✅

LC_ALL

LANGUAGE

fastlane gems

Gem
Version
Update-Status

fastlane
2.175.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.4.0

bundler
2.2.7

uri
0.10.0

rake
13.0.3

CFPropertyList
3.0.3

public_suffix
4.0.6

addressable
2.7.0

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.1.0

aws-partitions
1.428.0

aws-sigv4
1.2.2

jmespath
1.4.0

aws-sdk-core
3.112.0

aws-sdk-kms
1.42.0

aws-sdk-s3
1.88.1

babosa
1.0.4

claide
1.0.3

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.20

declarative-option
0.1.0

digest-crc
0.6.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.6

emoji_regex
3.2.2

excon
0.79.0

faraday-net_http
1.0.1

multipart-post
2.0.0

ruby2_keywords
0.0.4

faraday
1.3.0

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.2

gh_inspector
1.1.3

jwt
2.2.2

memoist
0.16.2

multi_json
1.15.0

os
1.1.1

signet
0.14.1

googleauth
0.15.1

httpclient
2.8.3

mini_mime
1.0.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.38.0

rexml
3.2.4

webrick
1.7.0

google-apis-core
0.2.1

google-apis-iamcredentials_v1
0.1.0

google-apis-storage_v1
0.2.0

google-cloud-env
1.4.0

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

google-cloud-storage
1.30.0

json
2.5.1

mini_magick
4.11.0

naturally
2.2.1

plist
3.6.0

rubyzip
2.3.0

security
0.1.3

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

generated on: 2021-02-22

If it gets suck at some point of the process you can Ctrl+c from the terminal to end the process and you'll get the traceback of the interruption signal so we have more information about the issue.
Thanks!

Apple changed a few bits and piece when it comes to the build section and TestFlight (i.e. there is no more "builds section"). My guess it that this change broke a few fastlane things as well.

@minuscorp Sorry for the delay, here is the full stacktrace:
INFO [2021-03-26 18:01:51.82]: precheck 👮♀ 👮  finished without detecting any potential problems 🛫
INFO [2021-03-26 18:01:52.22]: Selecting existing build-number: 50220
INFO [2021-03-26 18:01:53.65]: Selecting build 7.11.0 (50220)...
^C
WARN [2021-03-26 18:02:05.18]: Lane Context:
INFO [2021-03-26 18:02:05.18]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"submit_to_app_store", :GIT_REPO_WAS_CLEAN_ON_START=>true, :VERSION_NUMBER=>"7.11.0", :BUILD_NUMBER=>"50220"}
INFO [2021-03-26 18:02:05.18]: Successfully generated documentation at path '/#REDACTED#/fastlane/README.md'

+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | ensure_bundle_exec         | 0           |
| 3    | ensure_git_status_clean    | 0           |
| 4    | git_branch                 | 0           |
| 5    | get_version_number         | 0           |
| 6    | get_build_number           | 0           |
| 7    | git_branch                 | 0           |
| 8    | deliver                    | 58          |
+------+----------------------------+-------------+

ERROR [2021-03-26 18:02:05.19]: fastlane finished with errors
Traceback (most recent call last):
	81: from /usr/local/opt/ruby/bin/bundle:23:in `<main>'
	80: from /usr/local/opt/ruby/bin/bundle:23:in `load'
	79: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/exe/bundle:37:in `<top (required)>'
	78: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/friendly_errors.rb:130:in `with_friendly_errors'
	77: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/exe/bundle:49:in `block in <top (required)>'
	76: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/cli.rb:24:in `start'
	75: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	74: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/cli.rb:30:in `dispatch'
	73: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	72: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	71: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	70: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/cli.rb:494:in `exec'
	69: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/cli/exec.rb:28:in `run'
	68: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/cli/exec.rb:63:in `kernel_load'
	67: from /usr/local/lib/ruby/gems/2.7.0/gems/bundler-2.2.7/lib/bundler/cli/exec.rb:63:in `load'
	66: from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in `<top (required)>'
	65: from /usr/local/lib/ruby/gems/2.7.0/bin/fastlane:23:in `load'
	64: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/bin/fastlane:23:in `<top (required)>'
	63: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/cli_tools_distributor.rb:122:in `take_off'
	62: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	61: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/commands_generator.rb:352:in `run'
	60: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	59: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	58: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	57: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	56: from /usr/local/lib/ruby/gems/2.7.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	55: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/commands_generator.rb:108:in `block (2 levels) in run'
	54: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/command_line_handler.rb:36:in `handle'
	53: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/lane_manager.rb:47:in `cruise_lane'
	52: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:45:in `execute'
	51: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:45:in `chdir'
	50: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:49:in `block in execute'
	49: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/lane.rb:33:in `call'
	48: from Fastfile:221:in `block in parsing_binding'
	47: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/fast_file.rb:159:in `method_missing'
	46: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:157:in `trigger_action_by_name'
	45: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:229:in `execute_action'
	44: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:229:in `chdir'
	43: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:255:in `block in execute_action'
	42: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in `execute_action'
	41: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/runner.rb:263:in `block (2 levels) in execute_action'
	40: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/fastlane/lib/fastlane/actions/upload_to_app_store.rb:18:in `run'
	39: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/deliver/lib/deliver/runner.rb:68:in `run'
	38: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/deliver/lib/deliver/runner.rb:202:in `submit_for_review'
	37: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/deliver/lib/deliver/submit_for_review.rb:20:in `submit!'
	36: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/deliver/lib/deliver/submit_for_review.rb:51:in `select_build'
	35: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/connect_api/models/app_store_version.rb:205:in `select_build'
	34: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/forwardable.rb:235:in `patch_app_store_version_with_build'
	33: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/connect_api/tunes/tunes.rb:922:in `patch_app_store_version_with_build'
	32: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/connect_api/api_client.rb:128:in `patch'
	31: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/connect_api/api_client.rb:162:in `with_asc_retry'
	30: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/connect_api/api_client.rb:129:in `block in patch'
	29: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/client.rb:726:in `request'
	28: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/client.rb:882:in `send_request'
	27: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/client.rb:646:in `with_retry'
	26: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/client.rb:883:in `block in send_request'
	25: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-1.3.0/lib/faraday/connection.rb:279:in `patch'
	24: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-1.3.0/lib/faraday/connection.rb:492:in `run_request'
	23: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-1.3.0/lib/faraday/rack_builder.rb:154:in `build_response'
	22: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday_middleware-1.0.0/lib/faraday_middleware/response_middleware.rb:36:in `call'
	21: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday_middleware-1.0.0/lib/faraday_middleware/response_middleware.rb:36:in `call'
	20: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-cookie_jar-0.0.7/lib/faraday/cookie_jar.rb:24:in `call'
	19: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/helper/rels_middleware.rb:17:in `call'
	18: from /usr/local/lib/ruby/gems/2.7.0/gems/fastlane-2.179.0/spaceship/lib/spaceship/stats_middleware.rb:45:in `call'
	17: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:64:in `call'
	16: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-1.3.0/lib/faraday/adapter.rb:60:in `connection'
	15: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:66:in `block in call'
	14: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:122:in `perform_request'
	13: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:131:in `request_with_wrapped_block'
	12: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:146:in `request_via_request_method'
	11: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http.rb:933:in `start'
	10: from /usr/local/lib/ruby/gems/2.7.0/gems/faraday-net_http-1.0.1/lib/faraday/adapter/net_http.rb:152:in `block in request_via_request_method'
	 9: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http.rb:1492:in `request'
	 8: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http.rb:1519:in `transport_request'
	 7: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http.rb:1519:in `catch'
	 6: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http.rb:1528:in `block in transport_request'
	 5: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http/response.rb:31:in `read_new'
	 4: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/http/response.rb:42:in `read_status_line'
	 3: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/protocol.rb:201:in `readline'
	 2: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/protocol.rb:191:in `readuntil'
	 1: from /usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/protocol.rb:217:in `rbuf_fill'
/usr/local/Cellar/ruby/2.7.2/lib/ruby/2.7.0/net/protocol.rb:217:in `wait_readable': Interrupt

Have you tried to run your lane with DEBUG=1 environment variable set? It seems that the connection hangs, so maybe trying with another network might work as well.


Documentation and Schedule Training Updates: 2019-Chicago

Now that the Salmon version issue has been temporarily settled, and the newest training docker image has been pushed: ccdl/training_rnaseq:2019-chicago; This PR addresses the issues #34 and #37 in this repository.
Last thing we need to hammer out is what the exact file name will be for the machine-learning exercise notebook. I temporarily put what I think should be its url, based on following convention, however, we shouldn't merge this until that is finalized.

I believe this also addresses #36


Fix typo in sqlite build tag

The docs says sqlite3 is an available build tags but the correct one is sqlite. It's correctly referenced further in the guide but this typo made me rebuild gogs quite a few times before I read the whole page.

Thank you!


Refactoring

The prefixer got a quite important tool for css-in-js after all. As I consume it myself, I want to provide the best experience possible. Therefore I am going to refactor the code, modularize API and improve perfomance making it at least 2,5x faster than the current version.

Seems like this is slowly getting into shape. I already achieved an average performance improvement boosting the static version up to 4x faster.
What is open?

[x] refactor static version
[ ] refactor dynamic version
[ ] ensure Autoprefixer compliance
[ ] custom browser version configuration

this is basically done by outsourcing the generator
there will be a simple web tool, to generate the prefix data

[ ] improve the documentation
[ ] check caniuse-db for new prefix information keywords

We are also saving 0.5kb (static) and 1kb (dynamic) in gzipped mode!


Use paginated collections as default

Instead of dumping the whole content of a query in a collection, we should paginate them accordingly.
This means improving the activitypub.go collection pages support.

Progressed in this in the fact that we're now loading the page from the API URL and passing it to the Repository object we're using.
Next step is to use CollectionPage and OrderedCollectionPage objects instead of plain Collection and OrderedCollection.


feat(Popup): show on contextmenu (replacement to fix the screener issue)

https://github.com/stardust-ui/react/pull/1524

abondoning


Signum name system

Proposing a DNS like name resolving standard

@ohager can you also add sip-47 to the main page (readme) please


RuntimeError: Error compiling objects for extension

When I run ‘python setup.py build_ext --inplace’, it made an error:
running build_ext
/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/utils/cpp_extension.py:813: UserWarning: The detected CUDA version (11.2) has a minor version mismatch with the version that was used to compile PyTorch (11.3). Most likely this shouldn't be a problem.
warnings.warn(CUDA_MISMATCH_WARN.format(cuda_str_version, torch.version.cuda))
Emitting ninja build file /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/build/temp.linux-x86_64-3.7/build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
[1/1] c++ -MMD -MF /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/build/temp.linux-x86_64-3.7/src/deform_conv_cuda.o.d -pthread -B /home/coop/anaconda3/envs/v2xvit/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes /home/coop/gyt/software/ncurses/include -fPIC -DWITH_CUDA -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include/TH -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/coop/anaconda3/envs/v2xvit/include/python3.7m -c -c /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp -o /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/build/temp.linux-x86_64-3.7/src/deform_conv_cuda.o -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=deform_conv_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
FAILED: /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/build/temp.linux-x86_64-3.7/src/deform_conv_cuda.o
c++ -MMD -MF /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/build/temp.linux-x86_64-3.7/src/deform_conv_cuda.o.d -pthread -B /home/coop/anaconda3/envs/v2xvit/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes /home/coop/gyt/software/ncurses/include -fPIC -DWITH_CUDA -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include/TH -I/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/include/THC -I/usr/local/cuda-11.2/include -I/home/coop/anaconda3/envs/v2xvit/include/python3.7m -c -c /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp -o /home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/build/temp.linux-x86_64-3.7/src/deform_conv_cuda.o -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=deform_conv_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp: In function ‘void shape_check(at::Tensor, at::Tensor, at::Tensor*, at::Tensor, int, int, int, int, int, int, int, int, int, int)’:
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:66:3: error: ‘AT_CHECK’ was not declared in this scope
AT_CHECK(weight.ndimension() == 4,
^~~~~~~~
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:66:3: note: suggested alternative: ‘CHECK’
AT_CHECK(weight.ndimension() == 4,
^~~~~~~~
CHECK
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp: In function ‘int deform_conv_forward_cuda(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, int, int, int, int, int, int, int, int, int, int, int)’:
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:194:3: error: ‘AT_CHECK’ was not declared in this scope
AT_CHECK((offset.size(0) == batchSize), "invalid batch size of offset");
^~~~~~~~
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:194:3: note: suggested alternative: ‘CHECK’
AT_CHECK((offset.size(0) == batchSize), "invalid batch size of offset");
^~~~~~~~
CHECK
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp: In function ‘int deform_conv_backward_input_cuda(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, int, int, int, int, int, int, int, int, int, int, int)’:
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:301:3: error: ‘AT_CHECK’ was not declared in this scope
AT_CHECK((offset.size(0) == batchSize), 3, "invalid batch size of offset");
^~~~~~~~
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:301:3: note: suggested alternative: ‘CHECK’
AT_CHECK((offset.size(0) == batchSize), 3, "invalid batch size of offset");
^~~~~~~~
CHECK
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp: In function ‘int deform_conv_backward_parameters_cuda(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, int, int, int, int, int, int, int, int, int, int, float, int)’:
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:417:3: error: ‘AT_CHECK’ was not declared in this scope
AT_CHECK((offset.size(0) == batchSize), "invalid batch size of offset");
^~~~~~~~
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:417:3: note: suggested alternative: ‘CHECK’
AT_CHECK((offset.size(0) == batchSize), "invalid batch size of offset");
^~~~~~~~
CHECK
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp: In function ‘void modulated_deform_conv_cuda_forward(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, int, int, int, int, int, int, int, int, int, int, bool)’:
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:497:3: error: ‘AT_CHECK’ was not declared in this scope
AT_CHECK(input.is_contiguous(), "input tensor has to be contiguous");
^~~~~~~~
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:497:3: note: suggested alternative: ‘CHECK’
AT_CHECK(input.is_contiguous(), "input tensor has to be contiguous");
^~~~~~~~
CHECK
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp: In function ‘void modulated_deform_conv_cuda_backward(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, int, int, int, int, int, int, int, int, int, int, bool)’:
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:579:3: error: ‘AT_CHECK’ was not declared in this scope
AT_CHECK(input.is_contiguous(), "input tensor has to be contiguous");
^~~~~~~~
/home/coop/gyt/OpenCOOD-main/det3d/ops/dcn/src/deform_conv_cuda.cpp:579:3: note: suggested alternative: ‘CHECK’
AT_CHECK(input.is_contiguous(), "input tensor has to be contiguous");
^~~~~~~~
CHECK
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1814, in _run_ninja_build
env=env)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "setup.py", line 19, in
cmdclass={'build_ext': BuildExtension})
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/init.py", line 155, in setup
return distutils.core.setup(**attrs)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 148, in setup
return run_commands(dist)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 163, in run_commands
dist.run_commands()
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands
self.run_command(cmd)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
cmd_obj.run()
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 765, in build_extensions
build_ext.build_extensions(self)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
_build_ext.build_extension(self, ext)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/Cython/Distutils/build_ext.py", line 135, in build_extension
super(build_ext, self).build_extension(ext)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 534, in build_extension
depends=ext.depends)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 595, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1492, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/home/coop/anaconda3/envs/v2xvit/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1824, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension

In deform_conv_cuda.cpp, replace all "AT_CHECK" as "TORCH_CHECK "


Release Google.Cloud.Optimization.V1 version 2.5.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)

Created release for Google.Cloud.Optimization.V1-2.5.0