i try encrypt a vhdx file,OverflowError

the file size is 5.16GB,VERSION = '1.1.3'
C:\Users\vinso\Desktop\lock_files>lock_files.py -P vinson -vv  --lock D:\360Downloads\Software
INFO:544 lock "D:\360Downloads\Software\vinson.vhdx" --> "D:\360Downloads\Software\vinson.vhdx.locked"
Exception in thread Thread-1:
Traceback (most recent call last):
File "C:\Python27\lib\threading.py", line 801, in __bootstrap_inner
self.run()
File "C:\Python27\lib\threading.py", line 754, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Users\vinso\Desktop\lock_files\lock_files.py", line 455, in thread_process_file
process_file(opts, password, entry, stats)
File "C:\Users\vinso\Desktop\lock_files\lock_files.py", line 588, in process_file
lock_file(opts, password, path, stats)
File "C:\Users\vinso\Desktop\lock_files\lock_files.py", line 548, in lock_file
data = AESCipher(openssl=opts.openssl).encrypt(password, content)
File "C:\Users\vinso\Desktop\lock_files\lock_files.py", line 187, in encrypt
ciphertext_binary = encryptor.update(padded_plaintext) + encryptor.finalize()
File "C:\Python27\lib\site-packages\cryptography\hazmat\primitives\ciphers\base.py", line 149, in update
return self._ctx.update(data)
File "C:\Python27\lib\site-packages\cryptography\hazmat\backends\openssl\ciphers.py", line 124, in update
n = self.update_into(data, buf)
File "C:\Python27\lib\site-packages\cryptography\hazmat\backends\openssl\ciphers.py", line 140, in update_into
self._backend._ffi.from_buffer(data), len(data)
OverflowError: integer<PHONE_NUMBER> does not fit '32-bit int'

Thank you for sending this. I have never tried to encrypt a single file that was that large. Because i originally designed this for source code and document archives. I will look into this as part of the work on handling large files.
Can you please provide the following information? That would really help me.

What OS/version are you using?
What version of python are you using?
How much RAM/virtual memory do you have?


How to get point cloud data of human bodies only

Hi,
The project I am working on requires point cloud data of only human body excluding background and other objects.
I am wondering if it is possible to get a set of point cloud data of human body using Azure Kinect Body Tracking SDK?
Any help would be welcomed!
Thanks!

Hi,
in result object generated by the Body tracking SDK, there is an image called 'body index map', that image will highlight all the points on the depth image that belong to a human body.
You can find more info here https://docs.microsoft.com/en-us/azure/kinect-dk/body-index-map

@DWD3 is correct in that you want to use instance segmentation to isolate the human(s) from the scene. You could use the Azure Kinect Body Tracking SDK to achieve this but it may be overkill. Instead you could use a publicly available semantic or instance segmentation model to process the IR image to isolate the pixels associated with human(s) and use this info in rendering the point cloud.

@DWD3 is correct in that you want to use instance segmentation to isolate the human(s) from the scene. You could use the Azure Kinect Body Tracking SDK to achieve this but it may be overkill. Instead you could use a publicly available semantic or instance segmentation model to process the IR image to isolate the pixels associated with human(s) and use this info in rendering the point cloud.

Hi @qm13  Thanks for the response. Do you have any suggestion on which instance segmentation model to use? Currently I am use the body tracking API to do the job, but as you said, it's a bit of an overkill.

Sorry but I cannot make a specific recommendation.

Thank you guys for your help I used Azure Kinect Body Tracking SDK to solve this problem!

@DWD3是正确的，因为您希望使用实例分割将人员与场景隔离开来。你可以使用 Azure Kinect Body Tracking SDK 来实现此目的，但这可能有些过头了。相反，您可以使用公开可用的语义或实例分割模型来处理 IR 图像，以隔离与人关联的像素，并使用此信息来渲染点云。

嗨@qm13 感谢您的回复。您对使用哪种实例分段模型有什么建议吗？目前，我正在使用身体跟踪API来完成这项工作，但正如你所说，这有点矫枉过正。

@DWD3 Hi,Listen to your tone, you seem to be Chinese?
If so, we can talk about 3D reconstruction. I hope you can tell me your contact information.


Remove byteorder dependency

This can likely be removed once https://github.com/rust-lang/rust/issues/60446 stabilizes. Currently, byteorder is only used for floating point items.

The methods have just been stabilized (for 1.40.0), but they can also be replaced with .to_bits().to_bytes_XX(), which is already stable since a long time.


Compression codec augmentation ?

Hi,
Is there a way to randomly add a codec compression as a data augmentation when training speaker embeddings ? Is it already done in current pre-trained models ?
Things like Opus, MP3 etc.. but also telephony like a-law, mu-law etc.
Thanks.

No, we did not do any codec augmentation in our training data pipeline.
It would be very nice if you can contribute the codes with experimental results!


Import EasyEdit caused "Segmentation fault (core dumped)"

git clone https://github.com/zjunlp/EasyEdit.git
conda create -n EasyEdit python=3.9.7
...
pip install -r  requirements.txt

Following the instructions above in README, after the environments  have been set up, I just tried from easyeditor import MENDHyperParams and it caused a segfault: "Segmentation fault (core dumped)". And I also tried import torch, the same error happened. Importing other packages like transformers won't caused the segfault.
Is there any way to work around this problem? Please advice.

git clone https://github.com/zjunlp/EasyEdit.git
conda create -n EasyEdit python=3.9.7
...
pip install -r  requirements.txt

Following the instructions above in README, after the environments have been set up, I just tried from easyeditor import MENDHyperParams and it caused a segfault: "Segmentation fault (core dumped)". And I also tried import torch, the same error happened. Importing other packages like transformers won't caused the segfault.
Is there any way to work around this problem? Please advice.

Did you run the following command?
like:
source activate
conda activate EasyEdit

Segmentation fault (core dumped) mostly cause by improper memory operations.

git clone https://github.com/zjunlp/EasyEdit.git
conda create -n EasyEdit python=3.9.7
...
pip install -r  requirements.txt

Following the instructions above in README, after the environments have been set up, I just tried from easyeditor import MENDHyperParams and it caused a segfault: "Segmentation fault (core dumped)". And I also tried import torch, the same error happened. Importing other packages like transformers won't caused the segfault.
Is there any way to work around this problem? Please advice.

Did you run the following command? like:
source activate
conda activate EasyEdit

Segmentation fault (core dumped) mostly cause by improper memory operations.

Yes, I did. The segmentation fault happened in the EasyEdit virtual env.
How can I find out what kind of improper memory operations lead to this segfault? All I did was importing.
Please advice.

I cannot reproduce your problem, please check your local computer configuration

If your problem has been resolved, please help close this issue.

Hi, I met the same problem, and I have solved it by setting LD_LIBRARY_PATH="".
Hoping the solution work on your machine.


How to convert the trained results into a point cloud？

Hi，author，after running the program to get the results of synthesized images, they are just PNG depth and rgb images, how can I convert them into point clouds?

same question, do you solve it?


Pkg.test fails

I just ran the tests but one of them failed.
julia> Pkg.test("ApproxFun")
INFO: Testing ApproxFun
Fun tests
ODE tests
Vector tests
Operator tests
Singularities tests
Definite Integral tests
Spaces tests
WARNING: Unable to do JacobiTest.jl since FastGaussQuadrature.jl is not installed
Multivariate tests
ERROR: LoadError: LoadError: TypeError: arrayset: expected ApproxFun.BandedOperator{Any}, got ApproxFun.Derivative{ApproxFun.CosSpace,Int64,Float64}
 in setindex! at array.jl:371
 in getindex at array.jl:154
 in convert at /Users/dom/.julia/v0.4/ApproxFun/src/Operators/calculus.jl:46
 in convert at /Users/dom/.julia/v0.4/ApproxFun/src/PDE/KroneckerOperator.jl:126
 in getindex at array.jl:154
 in + at /Users/dom/.julia/v0.4/ApproxFun/src/PDE/KroneckerOperator.jl:291
 in include at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
 in include_from_node1 at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
 in include at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
 in include_from_node1 at loading.jl:129
 in process_options at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
 in _start at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
while loading /Users/dom/.julia/v0.4/ApproxFun/test/MultivariateTest.jl, in expression starting on line 103
while loading /Users/dom/.julia/v0.4/ApproxFun/test/runtests.jl, in expression starting on line 27

==============================[ ERROR: ApproxFun ]==============================

failed process: Process(`/usr/local/Cellar/julia/HEAD/bin/julia --check-bounds=yes --code-coverage=none --color=no /Users/dom/.julia/v0.4/ApproxFun/test/runtests.jl`, ProcessExited(1)) [1]

================================================================================
INFO: No packages to install, update or remove
ERROR: ApproxFun had test errors
 in error at error.jl:19
 in test at pkg/entry.jl:719
 in anonymous at pkg/dir.jl:29
 in cd at file.jl:20
 in cd at pkg/dir.jl:29
 in test at pkg.jl:69

Hmm this seems like a strange julia 0.4  feature:  typing out the function in  KroneckerOperator.jl:126 does not trigger the bug.  So I can’t actually narrow down what’s going on.

On 18 Apr 2015, at 10:15 pm, idontgetoutmuch<EMAIL_ADDRESS>wrote:
I just ran the tests but one of them failed.
julia> Pkg.test("ApproxFun")
INFO: Testing ApproxFun
Fun tests
ODE tests
Vector tests
Operator tests
Singularities tests
Definite Integral tests
Spaces tests
WARNING: Unable to do JacobiTest.jl since FastGaussQuadrature.jl is not installed
Multivariate tests
ERROR: LoadError: LoadError: TypeError: arrayset: expected ApproxFun.BandedOperator{Any}, got ApproxFun.Derivative{ApproxFun.CosSpace,Int64,Float64}
in setindex! at array.jl:371
in getindex at array.jl:154
in convert at /Users/dom/.julia/v0.4/ApproxFun/src/Operators/calculus.jl:46
in convert at /Users/dom/.julia/v0.4/ApproxFun/src/PDE/KroneckerOperator.jl:126
in getindex at array.jl:154
in + at /Users/dom/.julia/v0.4/ApproxFun/src/PDE/KroneckerOperator.jl:291
in include at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in include_from_node1 at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in include at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in include_from_node1 at loading.jl:129
in process_options at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in _start at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
while loading /Users/dom/.julia/v0.4/ApproxFun/test/MultivariateTest.jl, in expression starting on line 103
while loading /Users/dom/.julia/v0.4/ApproxFun/test/runtests.jl, in expression starting on line 27
==============================[ ERROR: ApproxFun ]==============================
failed process: Process(/usr/local/Cellar/julia/HEAD/bin/julia --check-bounds=yes --code-coverage=none --color=no /Users/dom/.julia/v0.4/ApproxFun/test/runtests.jl, ProcessExited(1)) [1]
================================================================================
INFO: No packages to install, update or remove
ERROR: ApproxFun had test errors
in error at error.jl:19
in test at pkg/entry.jl:719
in anonymous at pkg/dir.jl:29
in cd at file.jl:20
in cd at pkg/dir.jl:29
in test at pkg.jl:69
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/ApproxFun.jl/issues/167.

I would strongly advise against trying to use 0.4 yet:  they are still making changes that will break software.  E.g., I just updated to the latest build and now have to change (S,V) to Tuple{S,V} in a number of places.

On 19 Apr 2015, at 8:50 am, Sheehan Olver<EMAIL_ADDRESS>wrote:
Hmm this seems like a strange julia 0.4  feature:  typing out the function in  KroneckerOperator.jl:126 does not trigger the bug.  So I can’t actually narrow down what’s going on.

On 18 Apr 2015, at 10:15 pm, idontgetoutmuch<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
I just ran the tests but one of them failed.
julia> Pkg.test("ApproxFun")
INFO: Testing ApproxFun
Fun tests
ODE tests
Vector tests
Operator tests
Singularities tests
Definite Integral tests
Spaces tests
WARNING: Unable to do JacobiTest.jl since FastGaussQuadrature.jl is not installed
Multivariate tests
ERROR: LoadError: LoadError: TypeError: arrayset: expected ApproxFun.BandedOperator{Any}, got ApproxFun.Derivative{ApproxFun.CosSpace,Int64,Float64}
in setindex! at array.jl:371
in getindex at array.jl:154
in convert at /Users/dom/.julia/v0.4/ApproxFun/src/Operators/calculus.jl:46
in convert at /Users/dom/.julia/v0.4/ApproxFun/src/PDE/KroneckerOperator.jl:126
in getindex at array.jl:154
in + at /Users/dom/.julia/v0.4/ApproxFun/src/PDE/KroneckerOperator.jl:291
in include at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in include_from_node1 at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in include at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in include_from_node1 at loading.jl:129
in process_options at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
in _start at /usr/local/Cellar/julia/HEAD/lib/julia/sys.dylib
while loading /Users/dom/.julia/v0.4/ApproxFun/test/MultivariateTest.jl, in expression starting on line 103
while loading /Users/dom/.julia/v0.4/ApproxFun/test/runtests.jl, in expression starting on line 27
==============================[ ERROR: ApproxFun ]==============================
failed process: Process(/usr/local/Cellar/julia/HEAD/bin/julia --check-bounds=yes --code-coverage=none --color=no /Users/dom/.julia/v0.4/ApproxFun/test/runtests.jl, ProcessExited(1)) [1]
================================================================================
INFO: No packages to install, update or remove
ERROR: ApproxFun had test errors
in error at error.jl:19
in test at pkg/entry.jl:719
in anonymous at pkg/dir.jl:29
in cd at file.jl:20
in cd at pkg/dir.jl:29
in test at pkg.jl:69
—
Reply to this email directly or view it on GitHub https://github.com/ApproxFun/ApproxFun.jl/issues/167.

Ok I have gone back to 0.3.6 but I haven't tried the tests. If I get chance I will and if they fail I will raise another ticket.


Segmentation fault in multi-threaded code

I have an application that uses up to 7-threads and I randomly get segmentation faults from omnitrace version 1.10.2 coming from:
(gdb) #0  0x000015553b20bcae in std::_Hashtable<unsigned long, std::pair<unsigned long const, long>, std::allocator<std::pair<unsigned long const, long> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::_M_find_before_node () at /usr/include/c++/7/bits/hashtable.h:1551
#1  std::_Hashtable<unsigned long, std::pair<unsigned long const, long>, std::allocator<std::pair<unsigned long const, long> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::_M_find_node ()
    at /usr/include/c++/7/bits/hashtable.h:642
#2  0x000015553b9765dd in std::_Hashtable<unsigned long, std::pair<unsigned long const, long>, std::allocator<std::pair<unsigned long const, long> >, std::__detail::_Select1st, std::equal_to<unsigned long>, std::hash<unsigned long>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<false, false, true> >::find () at /usr/include/c++/7/bits/hashtable.h:1425
#3  std::unordered_map<unsigned long, long, std::hash<unsigned long>, std::equal_to<unsigned long>, std::allocator<std::pair<unsigned long const, long> > >::find () at /usr/include/c++/7/bits/unordered_map.h:920
#4  omnitrace::hip_activity_callback ()
    at /home/omnitrace/source/lib/omnitrace/library/roctracer.cpp:927
#5  0x000015553aff8236 in ?? ()
   from /pfs/lustrep2/projappl/project_462000125/samantao-public/rocm/rocm-5.4.3/lib/libroctracer64.so.4
#6  0x000015553aff944c in ?? ()
   from /pfs/lustrep2/projappl/project_462000125/samantao-public/rocm/rocm-5.4.3/lib/libroctracer64.so.4
#7  0x0000155554fe2a33 in ?? ()
   from /pfs/lustrep2/projappl/project_462000125/samantao-public/rocm/rocm-5.4.3/deps/libstdc++.so.6
#8  0x000015553bfd7d54 in omnitrace::component::pthread_create_gotcha::wrapper::operator() ()
    at /home/omnitrace/source/lib/omnitrace/library/components/pthread_create_gotcha.cpp:276
#9  0x000015553bfd9402 in omnitrace::component::pthread_create_gotcha::wrapper::wrap ()
    at /home/omnitrace/source/lib/omnitrace/library/components/pthread_create_gotcha.cpp:305
#10 0x000015554bed06ea in start_thread () from /lib64/libpthread.so.0
#11 0x000015554bbe8a6f in clone () from /lib64/libc.so.6

This app was executed as:
omnitrace-sample --trace -- neko.exe hemi.case

I believe there might be a race going into this unordered map. This comes from an app that is not trivial to build. Let me know if you'd like to provide more information about the SEGFault or the app itself.

Ah, yeah, I see why/how the data race is happening... there is a lock but on different mutexes. I can get it patched easily and I’ll generate a new release

Good stuff! Let me know how to get the patched version.

Jonathan, this is the Neko code, I was discussing the same with Niclas today. Please inform us when there is a change.

It is being held up by whatever happened to the build system on RedHat in HIP 5.5 and 5.6, seen in #300. Looks like some amdgpu libraries got moved and aren’t being found. I’m trying to get to solving it soon

Ok, I finally found the time to sort out #300. I’ll get that merged shortly and then addressing this will be quick and easy. There should be a release available tomorrow

It’s going to be a little while longer until I figure out how to solve the packaging and code coverage routinely running out of disk space.

Hi @jrmadsen, I also encounters almost the same bug when profiling my multi-threaded program(this one is unordered map, mine is ordered map's RBTree). Is there any estimation about when this bug fix will be brought to release? Thanks!

I’m tied up with the rocprofiler v2 rewrite. @benrichard-amd is looking into fixing #300 so that the testing can pass. Right now it’s just the code coverage job that is failing. If he cannot find a fix soon, I’ll just disable that job so that I can merge it, fix the bug, and generate a release

Thanks @jrmadsen! waiting for your good news on the fix.

Just generated the new release. Installers should be available shortly, however I haven't updated the installer generation to provide installers for ROCm 5.7 yet, just FYI.


can you share example .json database ?

Hey I am unable to see messages and users in app plz tell my why this is happening  but messages are storing in firebase database but not fetching in app


Fixed typo in FSComp.txt

I see somebody already submitted one of the typos fixed in FCS PR 688, so here is the other one.

Why on earth would that case this test to fail?
@dotnet-bot test this please

+++ Conformance\InferenceProcedures\TypeInference (E_OnOverloadIDAttr01.fs) +++

*** The following necessary lines were never matched:
***	\(10,7-10,17\):.+error FS0039:.+The type 'OverloadID' is not defined
***	\(11,7-11,17\):.+error FS0039:.+The type 'OverloadID' is not defined

*** The following necessary lines were incorrectly matched:

Unexpected Compiler Output


5.8 support?

There are errors right after importing the package in a fresh laravel 5.8.3 installation
Using version ^2.5 for grafite/builder
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 8 installs, 0 updates, 0 removals
  - Installing grafite/crypto (v1.1.1): Downloading (100%)
  - Installing laravelcollective/html (v5.8.0): Loading from cache
  - Installing doctrine/event-manager (v1.0.0): Downloading (100%)
  - Installing doctrine/cache (v1.8.0): Downloading (100%)
  - Installing doctrine/dbal (v2.9.2): Downloading (100%)
  - Installing grafite/formmaker (v1.3.4): Downloading (100%)
  - Installing grafite/crudmaker (v1.4.5): Downloading (100%)
  - Installing grafite/builder (v2.5.1): Downloading (100%)
doctrine/cache suggests installing alcaeus/mongo-php-adapter (Required to use legacy MongoDB driver)
Writing lock file
Generating optimized autoload files
> Illuminate\Foundation\ComposerScripts::postAutoloadDump
> @php artisan package:discover --ansi

In Container.php line 794:

  Class blade.compiler does not exist

Script @php artisan package:discover --ansi handling the post-autoload-dump event returned with error code 1

Sure, either wait or make pr

I guess this has not been fixed yet.

I guess this has not been fixed yet.

i found whats making it fail, the crypto and formmaker packages, ill send a pr for each

I guess this has not been fixed yet.

i found whats making it fail, the crypto and formmaker packages, ill send a pr for each
Did the PRs, hope they accept em soon
If you need to use the package now, just go inside crypto and formmaker service providers and move the blade directives from register to boot, and do a composer dump

Where I can found those files?

Following SaphiLC advice, I'm able to install and use Grafite, but Crudmaker doesn't write table fields in the migration file.


code in val_loader

In https://github.com/DerrickXuNu/v2x-vit/blob/main/v2xvit/tools/train.py,
I just noticed that
train_loader = DataLoader(opencood_train_dataset,
      batch_size=hypes['train_params']['batch_size'],
      num_workers=8,
      collate_fn=opencood_train_dataset.collate_batch_train,
      shuffle=True,
      pin_memory=False,
      drop_last=True)
val_loader = DataLoader(opencood_validate_dataset,
      batch_size=hypes['train_params']['batch_size'],
      num_workers=8,
      collate_fn=opencood_train_dataset.collate_batch_train,
      shuffle=False,
      pin_memory=False,
      drop_last=True)
I'm not sure that it is right, is it intended?

Hi, thanks for using our code! It won't matter here to use train or val dataset as they point to the same static function. But to avoid confusion, I will change it to the correct name later, thanks for pointing out

I got it, thanks!


Adding AllowDownloadingNonWebViewableFiles (Deprecated)

https://github.com/MicrosoftDocs/office-docs-powershell/pull/5005

Docs Build status updates of commit fc4f456:
:clock10: Full build: the average full build time is 12 min(s) 17 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit fc4f456:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 783697c:
:clock10: Full build: the average full build time is 12 min(s) 17 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 783697c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e775d93:
:clock10: Full build: the average full build time is 12 min(s) 18 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit e775d93:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenant.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


feat: upgrade sqlalchemy to 1.4

Closes #181

Summary

[x] Update SQLAlchemy to v1.4.
[x] Update SQLAlchemy-Utils to 0.38.2 (supports SQLAlchemy v1.4).
[x] Add asyncpg to dependencies; this is a required driver to work with SQLAlchemy's create_async_driver.
[x] Update instantiation of session engine with SQLAlchemy's create_async_driver.
[ ] Update tests to connect to database asynchronously.

Questions

Should we explicitly add greenlet as another dependency? It doesn't seem to cause issues in Docker, but may be required in some local contexts.
Would you like me to fix tests to work with the synchronous drivers or update all tests to work with asyncio (i.e., ORM's new async driver and asyncpg)?

Closing due to inactivity.


Access a specific revision

Is it possible to access a specific active revision even when traffic is set to 0?
Or what is best practice when you need to do a 2-phase migration, which does some data migrations (still compatible), but just takes longer to startup?

Deploy a complete new "container app"?

My idea was to use still revisions, but keep them hidden (set traffic to 0) and then when a certain health state is there (like migrated / ready), start adding traffic.

I've found it! 😅
Either in the latestFqdn or in each revision in the fqdn property.


Cannot render razor templates from a referenced project

When upgrading from the preview2 tooling, I've discovered that I now cannot include another project and run its server, and render razor templates from it.
Here's a minimal reproduction: https://github.com/liamdawson/min-razor-repro
I was able to successfully do this in the preview2 tooling. Now, instead, I get this error message:

Still haven't found a solution for this issue - any help?

Changing the working directory, doesn't really changing the application base path. So things like search paths for binaries and the deps file continue to be based off MinRepro.Hosts output path. However, changing the working directory does cause Hosting \ Mvc to treat MinRepro as the entry assembly. Consequently we look for the MinRepro.deps.json in MinRepro.Hosts output path (which does not exist).
You could add a post build step to the host to copy it in cp ..\MinRepro\bin\$(Configuration)\MinRepro.deps.json $(OutputPath) and that should help here.

Okay, thanks.
In the specific case of the project I'm working on, this issue arises when I'm trying to compile a razor view to a string. I'm using the sample from entropy ( https://github.com/aspnet/Entropy/blob/dev/samples/Mvc.RenderViewToString/RazorViewToStringRenderer.cs ), and it comes up with the same errors when trying to render cross-project, despite me copying the deps file over. Any pointers on how to give it the info it needs to render correctly?

@liamdawson explicitly calling the view engine (which is essentially what RazorViewToStringRendered does) shouldn't change the compilation. Could you get me a repro application once you've tried out the post build step I have? Alternatively, you could use Razor precompilation to compile views as part of building \ packing MinRepro. https://github.com/aspnet/MvcPrecompilation#enabling-view-compilation has some instructions on how to compile files as part of build and https://github.com/aspnet/MvcPrecompilation/blob/rel/1.1.1/testapps/ClassLibraryWithPrecompiledViews/ClassLibraryWithPrecompiledViews.csproj shows it working to pack the generated precompiled view as part of the package.

Closing this for now. Feel free to reopen once you've had a chance to look at my suggestions here https://github.com/aspnet/Mvc/issues/5940#issuecomment-315431242

ConsoleRazor.zip
I am getting "One or more compilation failures occurred:
4bbzmoty.fa3(4,41): error CS0234: The type or namespace name 'Razor' does not exist in the namespace 'Microsoft.AspNetCore' (are you missing an assembly reference?)
4bbzmoty.fa3(5,62): error CS0012: The type 'Attribute' is defined in an assembly that is not referenced. You must add a reference to assembly 'netstandard, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'.
4bbzmoty.fa3(4,82): error CS0518: Predefined type 'System.Type' is not defined or imported
etc....
in just this single Console app using DotNet 2.1
I am also trying to get this to work in a DotNet Core 2.1 Library so that I can call it from Test (and from an AWS Lambda Function) but no luck so far.
This is because in a high use scenario (which I have), it takes too long to fire up the whole web server and routing. What is needed is a quick, fast single Razor function page. That way, a component can be created that renders a single page with no routing required (routing is done by API Gateway).
Any help would be greatly appreciated as I have to find a solution.
Ultimately, the pre-compiled Razor page is the solution, but I have yet to find a Console app that can render from a Views.DLL am I missing a sample?
Thanks


Use /etc/redhat-release rather than /etc/issue

We currently use /etc/issue in many places to determine the version of the operating system.
The issue file is meant to be modified
There is also /etc/redhat-release which contains the same contents.
Lets use this instead (or the command lsb_release -d)
Looks like linux_admin needs some changes too.
Any ideas @roliveri @jrafanie @jvlcek @Fryguy
==> /etc/issue <==
CentOS release 6.5 (Final)

==> /etc/redhat-release <==
CentOS release 6.5 (Final)

/etc/issue no longer stores the os version, it uses \r. We're using other mechanisms now


Sometimes the set of C.exp_manager["kwargs"]["uri"] will not take effect

Description

Sometime with R.uri_context(uri=uri_path): will not be worked.
After digging the problem. The yield self is not set uri to the temporaril uri.
Motivation and Context

Bug fix
How Has This Been Tested?

[x] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[x] Fix bugs
[ ] Add new feature
[ ] Update documentation

@you-n-g
Due to the MLFLow API change, the check failed and the message is "qlib/workflow/expm.py:428:15: E1101: Instance of 'MlflowClient' has no 'list_experiments' member (no-member)".
See
https://github.com/mlflow/mlflow/blob/1ee3816840509090e2a18338fcfba146d514ecfc/CHANGELOG.md#1290-2022-09-16 for more infomation.
[Tracking] Add mlflow_search_experiments API to R client and deprecate mlflow_list_experiments (#6576, @dbczumar)
Looks like we need to use mlflow_search_experiments to replace mlflow_list_experiments.
Do you have any suggestion about this issue?
The fastest solution is limit the mlflow to 1.28.0.

@you-n-g
I think I can use mlflow.client serach_experiments to support list_experiments.
In this way, you might need to force the mlflow to > 1.30.
So what is your opinion?

@ChiahungTai  Please check if https://github.com/microsoft/qlib/pull/1364   solves your problem and makes the logic easier.
Thanks


Revert "Remove IsManagedWithBody extension method"

Reverts SamboyCoding/Cpp2IL#400

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 27.487%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Cpp2IL.Core/Utils/AsmResolver/AsmResolverUtils.cs
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>5:
-0.02%

Covered Lines:
3360

Relevant Lines:
10399

💛  - Coveralls


Init operations did not make model ready. When import form .pbtxt

System information

Ubuntu 16.04:
TensorFlow installed from (source or binary): pip binary
TensorFlow version (use command below): 1.13.1
Python version: 3.5.2
CUDA/cuDNN version: 10.0 / 7.5
GPU model and memory: NVIDIA RTX 2080TI

I am trying the tf.io.write_graph() and tf.import_graph_def API to implement model saving and re-building. And I encountered "Init operations did not make model ready" when importing the graph_def into MonitoredSession()
Here is the importing related source code:
# Some code to load graph_def from .pbtxt file
tf.reset_default_graph()
tf.import_graph_def(graph_def, name='')
with tf.train.MonitoredTrainingSession() as sess:

The bug information is:
RuntimeError: Init operations did not make model ready.  Init op: group_deps, init fn: None, local_init_op: name: "group_deps_1"
op: "NoOp"
input: "^init_2"
input: "^init_all_tables"
input: "^init_3"
, error: Variables not initialized: global_step, ......

@HongmingHUANG,
In order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here. Thanks!

@amahendrakar
Thanks for your response, Here is the complete code to reproduce the issue:
The input file is a .pbtxt file exported using
tf.io.write_graph(sess.graph_def, '.', ‘validation.pbtxt')
Here is the code to reproduce the bug (I just reproduced it now)
import tensorflow as tf
from google.protobuf import text_format
with open('validation.pbtxt', 'r') as fdin:
    file_content = fdin.read()
    try:
        graph_def = text_format.Parse(file_content, tf.GraphDef())
    except text_format.ParseError as e:
        raise IOError("Cannot parse file %s: %s."
                        % (filename, str(e)))
tf.reset_default_graph()
tf.import_graph_def(graph_def, name='')
with tf.train.MonitoredTrainingSession() as sess:
        sess.graph.as_default()
# Report error

Was able to reproduce the issue. Please find the Gist here. Thanks!

Apologies for the delay in response. Is this still an issue? Thanks!


Update README.md

added blogpost link

Hi @Dark0d3,
Thanks for the update, it's a great article, but ... unfortunately it was not published in October, and I am afraid the only November contributions we can accept are the ones made during the UK Festival Hackathon on November 7 😬
So, I am very sorry but I will have to close this PR.
But the good news is that it seems you already have 2 other PR's accepted for this year 😁
This means that you qualify for some Umbraco Hacktoberfest swag and that you will hear from us soon 🎉

Thanks @mikecp for the update, I wrote the article on October but was waiting on skrift.io.😅


Think about what API calls to allow in what circumstances

Think properly about which API methods should work only for the admin user or when run in "Hub mode", for security.
See https://docs.google.com/spreadsheets/d/1iSc8hMixsKUhnZ2oZ0eKLH28SLsJWuyaQo1FwoBBsak/edit#gid=0 for a proposed breakdown of API method access rules.

For example, procure could be restricted to only admin users.

I've had to leave the Commit API open, because the frontend tests do something dodgy that depends on it in order to set up test state. So this issue is done apart from Commit, which it's blocked on UI test refactoring for. Pushing it back to the sprint.

This is almost a duplicate of https://github.com/dotmesh-io/dotmesh/issues/577


Error NPM START

Helo Nelderson. Conglatullation from this project.
I have been trying to start server, but this is not work. Appear this message above:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestart, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/share/npm/bin/node-gyp-bin:/home/ubuntu/mv_server/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/ubuntu/mv_server
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node server.js' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: node server.js
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/share/npm/lib/utils/lifecycle.js:232:16)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at EventEmitter.emit (events.js:172:7)
14 verbose stack     at ChildProcess. (/usr/share/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:87:13)
14 verbose stack     at ChildProcess.emit (events.js:172:7)
14 verbose stack     at maybeClose (internal/child_process.js:821:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/ubuntu/mv_server
17 error Linux 4.4.0-98-generic
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
19 error node v4.2.6
20 error npm  v3.5.2
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>start: node server.js
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script 'node server.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the mvonline package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     node server.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs mvonline
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls mvonline
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Please, help me friend.

I solved this. Thanks.


Remove region mapping from TerriaMap

It is provided by terriajs here https://github.com/TerriaJS/terriajs/tree/main/wwwroot/data

Won't impact nationalmap


lighter input tag

Hi,
I was asking myself about the relatoinship of

user interaction (on input , eg cheching a checkbox or entering text), something lighterhtml may not be aware of

and ligherhtml renderer refresh.

While trying to set-up an raw example, I wrote a preliminary one.... that I do not understand.
In the following code

the second input checkbox is set to empty string while displayed a non-expected 'checked' checkbox

At  the opposite the first checkbox filled alternatively with empty string and 'checked', which is ok

So, same input, different behaviour. Can you help? Thank you.
const {render, html} = lighterhtml;
let high=false, checked;
setInterval(update,2000);

function update() {
  checked=high?"checked":"";
  high=!high;
  render(document.body, () => html`
    <input type="checkbox" checked="${checked}"/>
    <input type="text" value="${checked}"/>

    <input type="checkbox" checked=""/>
    <input type="text" value=""/>
`);
}

it's documented in here, checked is a boolean attribute, you don't pass the string checked, you pass true or false directly.
https://viperhtml.js.org/hyperhtml/documentation/#essentials-5

const {render, html} = lighterhtml;
let checked = false;
setInterval(update,2000);

function update() {
  checked = !checked;
  render(document.body, () => html`
    <input type="checkbox" checked="${checked}">
    <input type="text" value="${checked}">
`);
}

Either with checked/true or empty string/false  it is the same output
Original question is that the code has  different outputs for the same input

same input (false)

different behaviour ('non-checked' for first checkbox 'checked' for the second)

const {render, html} = lighterhtml;
let checked=true;
setInterval(update,2000);

function update() {
  checked=!checked;
  render(document.body, () => html`
    <input type="checkbox" checked="${checked}"/>
    <input type="text" value="${checked}"/>

    <input type="checkbox" checked="false"/>
    <input type="text" value=""/>
`);
}

ok, sorry to have been a bit insiting/heavy
As a conclusion as you mention in the doc

special attributes

or

Whenever an attribute has a special meaning

there is a lighterhtml rule saying that we should use a boolean map for those
seems that there is no vocabulary for naming those special attributes. Not found at MDN at least.

Original question is that the code has different outputs for the same input

The code has always predictable output depending on the kind of nodes, and related attributes, you are dealing with.
What is your issue, exactly?

Actually, let me try again: do you understand this fails your expectations ? <input type="checkbox" checked="false"/> it doesn't in hyper/lighterhtml, as documented.
Any better?

P.S. the vocabulary for special attributes is here:
https://html.spec.whatwg.org/multipage/input.html#the-input-element

I think everything is ok now (for that topic).
My confusion was that, for those attributes  ,  writing in HTML (only keys, no value) is different than writing in ligherhtml  , but the HTMLInputInterface is clear, all those types are returning boolean...
Thank you for taking time for such explanation/guidance

next up, <input  onchange=${handler}> doesn't really set a handler directly on the input, it uses addEventListener behind the scene.
Other attribute cases should be described in the docs, let me know if you need any extra clarification 👋

ok, thanks for giving the way lighterhtml implements listener
I have no clear overview of HTML attributes diversity, so I may ring you on a case/case basis.
I think I got now a first understanding of how lighterhtml works which is ok for my current need
It is efficient and an pleasure to work with.
Two other topics I will need to look at are

the "outside lighterhtml" possible interferences (user interaction or changes via third parties)
generic components (seems limited since all is declarative)

I keep you inform on troubles/opportunities
Thank you again.

the "outside lighterhtml" possible interferences

lighterhtml own its own content. If you drop nodes, erase content, etc, you gonna have hard time. Obtrusive libraries are indeed not super welcome here, but that's the same with any other framework, I guess.

generic components (seems limited since all is declarative)

you can either use Custom Elements and keep it declarative in the HTML world, or give Neverland a try (link in the README)

Point 1 : yep thats the current state and lighterhtml is building something in an existing middle. There might be some hard restriction.
Point 2 : custom and generic are different (may be a dream,  but let us go)
Note : currently i am not conviced about neverland (at least useState or for few dedicated cases cause on non persistent locals like label/input with for/id or I miss something) but in lighterhtml.

neverland is based on lightrhtml and dom-augmentor, it just glues these together


[PoC] Update syn crate to version 2

Disclaimer: I don't intend to merge this because it would conflicts with several ongoing pull requests. The main purpose of this is is to show how updating is possible, and (the second purpose is to train myself).
As discussed in https://github.com/extendr/extendr/pull/574, extendr seems to have some motivation to update the syn crate. Here's some code and references:

Release note of Syn 2.0
syn::parse
syn::meta::parser
syn::Attribute
When to choose Attribute::parse_nested_meta or syn::meta::parser

Sorry for no explanations about the changes. I might write some in future if I get some time.

Currently prqlr includes two versions of syn.
https://github.com/cran/prqlr/blob/9b1cb4c827eaf303d5bbbe74df7ec5e5fb320d7d/LICENSE.note#L556-L572
It would be great if this PR is merged.

I have looked at this PR, and looked at doing the upgrade myself, but when I did it, I faced so many more issues. Maybe I choose the wrong way to upgrade the code.
This looks very succinct.

Dear @yutannihilation, I like this and I think we should merge this.
The PRs that are currently up are mostly abandoned (due to inaction from our side), or otherwise
will need attention. I think a good path is to work on the PRs, that we all understand, and value, and then
we can unblock our attention and focus on those larger PRs.
Upgrading syn now is better.
Let me know how I can assist here.

Sure. I think this should work.


Rename file in namespace bucket fails via cyberduck

Environment info

Version: 2.3.1-73a7583
Deployment: AZURE
Customer: QA

Actual behavior

Rename file in namespace bucket fails via cyberduck fails with internal error.

we used azure connection

Expected behavior

We should be able to rename

Steps to reproduce

Create a connection to azure
Use the connection as a namespace resource
Add a namespace bucket
Upload files to it
Rename using cyberduck
See that it fails.

Does not reproduce using Cyberduck.


IOS missing shadows

Is there any reason Card and Toolbar to have overflow: hidden in the theme, because this prevent the shadow to be displayed on iOS.

Temporary solution
Card
<Card key={item}
            style={{
              container: {
                overflow: 'visible',
                shadowOpacity: 0.08,
                shadowRadius: 6,
                shadowOffset: { height: 5, width: 0 },
                shadowColor: '#000'
              }
            }}
          >

Toolbar
<Toolbar
            style={{
              container: { marginTop: 20, backgroundColor: 'white', zIndex: 5 },
              titleText: { color: '#54698d' },
              rightElement: { color: '#54698d' },
              leftElement: { color: '#54698d' },
            }}
            leftElement="menu"
            centerElement="Pending"
            searchable={{
              autoFocus: true,
              placeholder: 'Search',
            }}
          >
          </Toolbar>
          <View style={{
            height: 10,
            backgroundColor: '#fff',
            marginTop: -10,
            shadowOpacity: 0.12,
            shadowRadius: 5,
            shadowColor: '#000',
            zIndex: 4,
            shadowOffset: { height: 5, width: 0 }
          }} />

@ButuzGOL thx I use it like this anyway but I'm just curious if there is a reason behind this.

Thx @ButuzGOL I use it like this anyway, I was just curious if there is something intended in this.


正则问题

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
from typing import Optional
from fastapi import FastAPI
from fastapi import Query

app = FastAPI()

@app.get("/items/")
async def read_item(q:Optional[str]=Query(None,regex="^[a-z]*")):
    results = ["a","b"]
    if q:
        results.append(q)
    return results

Description
http://<IP_ADDRESS>:8000/items/?q=12345
When I access this URL in my browser,12345 can be matched by the re ^[a-z]*
Operating System
Windows
Operating System Details
No response
FastAPI Version
0.75.2
Python Version
3.9
Additional Context
No response

Maybe you need to use regex="^[a-z]$" to match only strings in your query. ^[a-z]* causes it to match 0 or more repetitions of the preceding regex i.e with input abc1, it will only match ab.


createwallet command is not present in dogecoin-cli

There is no command to create multiple wallets in dogecoin-cli like in litecoin and bitcoin there is createwallet command in cli. So is there any way to create and manage multiple wallets in dogecoin-cli? I am using dogecoin-cli 1.14.3. Also, there's a lot of commands that are present in litecoin cli which are not present in dogecoin-cli. Please help. Thanks.

@ftechizPrashant  Specifically, which commands would you like to see implemented?

There isn't with 1.14, no. The command is in 1.21, although there's a backlog of changes for 1.21 to be merged into the main repo.

Yes, I created a build from the branch 1.21-dev and deployed on the server but the node is not sycning
log from debug.log file is given below:
2021-09-02T16:57:13Z Dogecoin Core version v<IP_ADDRESS>-b1a924969 (release build)
2021-09-02T16:57:13Z Assuming ancestors of block 014c0753de886b81dffa11e99f37416930b67d55bda17589d886aeb053414942 have valid signatures.
2021-09-02T16:57:13Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000051737530b00a8ed4e3e
2021-09-02T16:57:13Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2021-09-02T16:57:13Z Using RdRand as an additional entropy source
2021-09-02T16:57:13Z Default data directory /home/ubuntu/.dogecoin
2021-09-02T16:57:13Z Using data directory /home/ubuntu/.dogecoin
2021-09-02T16:57:13Z Config file: /home/ubuntu/.dogecoin/dogecoin.conf (not found, skipping)
2021-09-02T16:57:13Z Command-line arg: daemon=""
2021-09-02T16:57:13Z Using at most 125 automatic connections (1024 file descriptors available)
2021-09-02T16:57:13Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-09-02T16:57:13Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-09-02T16:57:13Z Script verification uses 1 additional threads
2021-09-02T16:57:13Z scheduler thread start
2021-09-02T16:57:13Z HTTP: creating work queue of depth 16
2021-09-02T16:57:13Z Using random cookie authentication.
2021-09-02T16:57:13Z Generated RPC authentication cookie /home/ubuntu/.dogecoin/.cookie
2021-09-02T16:57:13Z HTTP: starting 4 worker threads
2021-09-02T16:57:13Z Using wallet directory /home/ubuntu/.dogecoin/wallets
2021-09-02T16:57:13Z init message: Verifying wallet(s)...
2021-09-02T16:57:13Z init message: Loading banlist...
2021-09-02T16:57:13Z SetNetworkActive: true
2021-09-02T16:57:13Z Using /16 prefix for IP bucketing
2021-09-02T16:57:13Z Cache configuration:
2021-09-02T16:57:13Z * Using 2.0 MiB for block index database
2021-09-02T16:57:13Z * Using 8.0 MiB for chain state database
2021-09-02T16:57:13Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-09-02T16:57:13Z init message: Loading block index...
2021-09-02T16:57:13Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2021-09-02T16:57:13Z Opening LevelDB in /home/ubuntu/.dogecoin/blocks/index
2021-09-02T16:57:13Z Opened LevelDB successfully
2021-09-02T16:57:13Z Using obfuscation key for /home/ubuntu/.dogecoin/blocks/index:<PHONE_NUMBER>000000
2021-09-02T16:57:15Z LoadBlockIndexDB: last block file = 0
2021-09-02T16:57:15Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=232, heights=0...0, time=2013-12-06...2013-12-06)
2021-09-02T16:57:15Z Checking all blk files are present...
2021-09-02T16:57:15Z Opening LevelDB in /home/ubuntu/.dogecoin/chainstate
2021-09-02T16:57:15Z Opened LevelDB successfully
2021-09-02T16:57:15Z Using obfuscation key for /home/ubuntu/.dogecoin/chainstate: 22a757e82757bae5
2021-09-02T16:57:15Z Loaded best chain: hashBestChain=1a91e3dace36e2be3bf030a65679fe821aa1d6ef92e7c9902eb318182c355691 height=0 date=2013-12-06T10:25:40Z progress=0.000000
2021-09-02T16:57:15Z init message: Rewinding blocks...
2021-09-02T16:57:15Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2021-09-02T16:57:15Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2021-09-02T16:57:15Z init message: Verifying blocks...
2021-09-02T16:57:15Z  block index            2004ms
2021-09-02T16:57:15Z block tree size = 370001
2021-09-02T16:57:15Z nBestHeight = 0
2021-09-02T16:57:15Z loadblk thread start
2021-09-02T16:57:15Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2021-09-02T16:57:15Z loadblk thread exit
2021-09-02T16:57:15Z torcontrol thread start
2021-09-02T16:57:15Z Bound to [::]:22556
2021-09-02T16:57:15Z Bound to <IP_ADDRESS>:22556
2021-09-02T16:57:15Z Bound to <IP_ADDRESS>:22557
2021-09-02T16:57:15Z init message: Loading P2P addresses...
2021-09-02T16:57:16Z Loaded 12888 addresses from peers.dat  38ms
2021-09-02T16:57:16Z Loaded 0 addresses from "anchors.dat"
2021-09-02T16:57:16Z 0 block-relay-only anchors will be tried for connections.
2021-09-02T16:57:16Z init message: Starting network threads...
2021-09-02T16:57:16Z net thread start
2021-09-02T16:57:16Z init message: Done loading
2021-09-02T16:57:16Z dnsseed thread start
2021-09-02T16:57:16Z msghand thread start
2021-09-02T16:57:16Z Waiting 300 seconds before querying DNS seeds.
2021-09-02T16:57:16Z opencon thread start
2021-09-02T16:57:16Z addcon thread start
2021-09-02T16:59:50Z New outbound peer connected: version: 70015, blocks=3880534, peer=0 (full-relay)
2021-09-02T17:02:16Z Loading addresses from DNS seed seed2.multidoge.org
2021-09-02T17:02:16Z Loading addresses from DNS seed seed.multidoge.org
2021-09-02T17:02:16Z 0 addresses found from DNS seeds
2021-09-02T17:02:16Z dnsseed thread exit
2021-09-02T17:08:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 630 seconds ago)
2021-09-02T17:18:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1260 seconds ago)
2021-09-02T17:29:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2021-09-02T17:39:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2021-09-02T17:50:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2021-09-02T18:00:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2021-09-02T18:11:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2021-09-02T18:21:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2021-09-02T18:32:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2021-09-02T18:42:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2021-09-02T18:53:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2021-09-02T19:03:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2021-09-02T19:14:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8191 seconds ago)
2021-09-02T19:24:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8821 seconds ago)
2021-09-02T19:35:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9451 seconds ago)
2021-09-02T19:45:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10081 seconds ago)
2021-09-02T19:56:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10711 seconds ago)
2021-09-02T20:06:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11341 seconds ago)
2021-09-02T20:17:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11971 seconds ago)
2021-09-02T20:27:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12601 seconds ago)
2021-09-02T20:38:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13231 seconds ago)
2021-09-02T20:48:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13861 seconds ago)
2021-09-02T20:59:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14491 seconds ago)
2021-09-02T21:09:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15121 seconds ago)
2021-09-02T21:20:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15751 seconds ago)
2021-09-02T21:30:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16381 seconds ago)
2021-09-02T21:41:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17011 seconds ago)
2021-09-02T21:51:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17641 seconds ago)
2021-09-02T22:02:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18271 seconds ago)
2021-09-02T22:12:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18901 seconds ago)
2021-09-02T22:23:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19531 seconds ago)
2021-09-02T22:33:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20161 seconds ago)
2021-09-02T22:44:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20791 seconds ago)
2021-09-02T22:54:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21421 seconds ago)
2021-09-02T23:05:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22051 seconds ago)
2021-09-02T23:15:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22681 seconds ago)
2021-09-02T23:26:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23311 seconds ago)
2021-09-02T23:36:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23941 seconds ago)
2021-09-02T23:47:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24571 seconds ago)
2021-09-02T23:57:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25201 seconds ago)
2021-09-03T00:08:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25831 seconds ago)
2021-09-03T00:18:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26461 seconds ago)
2021-09-03T00:29:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27091 seconds ago)
2021-09-03T00:39:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27721 seconds ago)
2021-09-03T00:50:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28351 seconds ago)
2021-09-03T01:00:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28981 seconds ago)
2021-09-03T01:11:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29611 seconds ago)
2021-09-03T01:21:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30241 seconds ago)
2021-09-03T01:32:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30871 seconds ago)
2021-09-03T01:42:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31501 seconds ago)
2021-09-03T01:53:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32131 seconds ago)
2021-09-03T02:03:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32761 seconds ago)
2021-09-03T02:14:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33391 seconds ago)
2021-09-03T02:24:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34021 seconds ago)
2021-09-03T02:35:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34651 seconds ago)
2021-09-03T02:45:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35281 seconds ago)
2021-09-03T02:56:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35911 seconds ago)
2021-09-03T03:06:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36541 seconds ago)
2021-09-03T03:17:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37171 seconds ago)
2021-09-03T03:27:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37801 seconds ago)
2021-09-03T03:38:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38431 seconds ago)
2021-09-03T03:48:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39061 seconds ago)

node is not sycning

this is because it's not ready yet. The protocol completeness in the 1.21-dev branch is currently about the same as what Dogecoin 1.6 was, because it has no AuxPoW. It's also not been tested other than code reviews. A good point to start playing with 1.21 would be when a release candidate (RC) is tagged.

@ftechizPrashant Specifically, which commands would you like to see implemented?

createwallet is needed hoping to see it implemented sooner

Yes, I created a build from the branch 1.21-dev and deployed on the server but the node is not sycning
log from debug.log file is given below:
2021-09-02T16:57:13Z Dogecoin Core version v<IP_ADDRESS>-b1a924969 (release build)
2021-09-02T16:57:13Z Assuming ancestors of block 014c0753de886b81dffa11e99f37416930b67d55bda17589d886aeb053414942 have valid signatures.
2021-09-02T16:57:13Z Setting nMinimumChainWork=00000000000000000000000000000000000000000000051737530b00a8ed4e3e
2021-09-02T16:57:13Z Using the 'sse4(1way),sse41(4way),avx2(8way)' SHA256 implementation
2021-09-02T16:57:13Z Using RdRand as an additional entropy source
2021-09-02T16:57:13Z Default data directory /home/ubuntu/.dogecoin
2021-09-02T16:57:13Z Using data directory /home/ubuntu/.dogecoin
2021-09-02T16:57:13Z Config file: /home/ubuntu/.dogecoin/dogecoin.conf (not found, skipping)
2021-09-02T16:57:13Z Command-line arg: daemon=""
2021-09-02T16:57:13Z Using at most 125 automatic connections (1024 file descriptors available)
2021-09-02T16:57:13Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2021-09-02T16:57:13Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2021-09-02T16:57:13Z Script verification uses 1 additional threads
2021-09-02T16:57:13Z scheduler thread start
2021-09-02T16:57:13Z HTTP: creating work queue of depth 16
2021-09-02T16:57:13Z Using random cookie authentication.
2021-09-02T16:57:13Z Generated RPC authentication cookie /home/ubuntu/.dogecoin/.cookie
2021-09-02T16:57:13Z HTTP: starting 4 worker threads
2021-09-02T16:57:13Z Using wallet directory /home/ubuntu/.dogecoin/wallets
2021-09-02T16:57:13Z init message: Verifying wallet(s)...
2021-09-02T16:57:13Z init message: Loading banlist...
2021-09-02T16:57:13Z SetNetworkActive: true
2021-09-02T16:57:13Z Using /16 prefix for IP bucketing
2021-09-02T16:57:13Z Cache configuration:
2021-09-02T16:57:13Z * Using 2.0 MiB for block index database
2021-09-02T16:57:13Z * Using 8.0 MiB for chain state database
2021-09-02T16:57:13Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2021-09-02T16:57:13Z init message: Loading block index...
2021-09-02T16:57:13Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2021-09-02T16:57:13Z Opening LevelDB in /home/ubuntu/.dogecoin/blocks/index
2021-09-02T16:57:13Z Opened LevelDB successfully
2021-09-02T16:57:13Z Using obfuscation key for /home/ubuntu/.dogecoin/blocks/index:<PHONE_NUMBER>000000
2021-09-02T16:57:15Z LoadBlockIndexDB: last block file = 0
2021-09-02T16:57:15Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=232, heights=0...0, time=2013-12-06...2013-12-06)
2021-09-02T16:57:15Z Checking all blk files are present...
2021-09-02T16:57:15Z Opening LevelDB in /home/ubuntu/.dogecoin/chainstate
2021-09-02T16:57:15Z Opened LevelDB successfully
2021-09-02T16:57:15Z Using obfuscation key for /home/ubuntu/.dogecoin/chainstate: 22a757e82757bae5
2021-09-02T16:57:15Z Loaded best chain: hashBestChain=1a91e3dace36e2be3bf030a65679fe821aa1d6ef92e7c9902eb318182c355691 height=0 date=2013-12-06T10:25:40Z progress=0.000000
2021-09-02T16:57:15Z init message: Rewinding blocks...
2021-09-02T16:57:15Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2021-09-02T16:57:15Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2021-09-02T16:57:15Z init message: Verifying blocks...
2021-09-02T16:57:15Z  block index            2004ms
2021-09-02T16:57:15Z block tree size = 370001
2021-09-02T16:57:15Z nBestHeight = 0
2021-09-02T16:57:15Z loadblk thread start
2021-09-02T16:57:15Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2021-09-02T16:57:15Z loadblk thread exit
2021-09-02T16:57:15Z torcontrol thread start
2021-09-02T16:57:15Z Bound to [::]:22556
2021-09-02T16:57:15Z Bound to <IP_ADDRESS>:22556
2021-09-02T16:57:15Z Bound to <IP_ADDRESS>:22557
2021-09-02T16:57:15Z init message: Loading P2P addresses...
2021-09-02T16:57:16Z Loaded 12888 addresses from peers.dat  38ms
2021-09-02T16:57:16Z Loaded 0 addresses from "anchors.dat"
2021-09-02T16:57:16Z 0 block-relay-only anchors will be tried for connections.
2021-09-02T16:57:16Z init message: Starting network threads...
2021-09-02T16:57:16Z net thread start
2021-09-02T16:57:16Z init message: Done loading
2021-09-02T16:57:16Z dnsseed thread start
2021-09-02T16:57:16Z msghand thread start
2021-09-02T16:57:16Z Waiting 300 seconds before querying DNS seeds.
2021-09-02T16:57:16Z opencon thread start
2021-09-02T16:57:16Z addcon thread start
2021-09-02T16:59:50Z New outbound peer connected: version: 70015, blocks=3880534, peer=0 (full-relay)
2021-09-02T17:02:16Z Loading addresses from DNS seed seed2.multidoge.org
2021-09-02T17:02:16Z Loading addresses from DNS seed seed.multidoge.org
2021-09-02T17:02:16Z 0 addresses found from DNS seeds
2021-09-02T17:02:16Z dnsseed thread exit
2021-09-02T17:08:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 630 seconds ago)
2021-09-02T17:18:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1260 seconds ago)
2021-09-02T17:29:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2021-09-02T17:39:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2021-09-02T17:50:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2021-09-02T18:00:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2021-09-02T18:11:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2021-09-02T18:21:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2021-09-02T18:32:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2021-09-02T18:42:58Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2021-09-02T18:53:28Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2021-09-02T19:03:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2021-09-02T19:14:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8191 seconds ago)
2021-09-02T19:24:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8821 seconds ago)
2021-09-02T19:35:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9451 seconds ago)
2021-09-02T19:45:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10081 seconds ago)
2021-09-02T19:56:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10711 seconds ago)
2021-09-02T20:06:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11341 seconds ago)
2021-09-02T20:17:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11971 seconds ago)
2021-09-02T20:27:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12601 seconds ago)
2021-09-02T20:38:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13231 seconds ago)
2021-09-02T20:48:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13861 seconds ago)
2021-09-02T20:59:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14491 seconds ago)
2021-09-02T21:09:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15121 seconds ago)
2021-09-02T21:20:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15751 seconds ago)
2021-09-02T21:30:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16381 seconds ago)
2021-09-02T21:41:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17011 seconds ago)
2021-09-02T21:51:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17641 seconds ago)
2021-09-02T22:02:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18271 seconds ago)
2021-09-02T22:12:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18901 seconds ago)
2021-09-02T22:23:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19531 seconds ago)
2021-09-02T22:33:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20161 seconds ago)
2021-09-02T22:44:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20791 seconds ago)
2021-09-02T22:54:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21421 seconds ago)
2021-09-02T23:05:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22051 seconds ago)
2021-09-02T23:15:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22681 seconds ago)
2021-09-02T23:26:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23311 seconds ago)
2021-09-02T23:36:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23941 seconds ago)
2021-09-02T23:47:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24571 seconds ago)
2021-09-02T23:57:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25201 seconds ago)
2021-09-03T00:08:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25831 seconds ago)
2021-09-03T00:18:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26461 seconds ago)
2021-09-03T00:29:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27091 seconds ago)
2021-09-03T00:39:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27721 seconds ago)
2021-09-03T00:50:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28351 seconds ago)
2021-09-03T01:00:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28981 seconds ago)
2021-09-03T01:11:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29611 seconds ago)
2021-09-03T01:21:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30241 seconds ago)
2021-09-03T01:32:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30871 seconds ago)
2021-09-03T01:42:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31501 seconds ago)
2021-09-03T01:53:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32131 seconds ago)
2021-09-03T02:03:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32761 seconds ago)
2021-09-03T02:14:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33391 seconds ago)
2021-09-03T02:24:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34021 seconds ago)
2021-09-03T02:35:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34651 seconds ago)
2021-09-03T02:45:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35281 seconds ago)
2021-09-03T02:56:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35911 seconds ago)
2021-09-03T03:06:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36541 seconds ago)
2021-09-03T03:17:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37171 seconds ago)
2021-09-03T03:27:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37801 seconds ago)
2021-09-03T03:38:29Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38431 seconds ago)
2021-09-03T03:48:59Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39061 seconds ago)

@ftechizPrashant were you able to make this work?

@diadal @ftechizPrashant At the moment, there is no plan to implement createwallet as described  in 1.14.x. This will be available in the 1.21.x version of doge. Unless there is a strong reason, and I cannot see one, to implement it sooner it wont be.
@patricklodder @rnicoll

@ReverseControl there is much strong reason, that depends on the angle in which you looking at

@diadal Make your case.

@ReverseControl
take, for example, some projects that required multiple wallets will need to have multiple servers or users to achieve.
some project also has a backup wallet,
some project also used one wallet for receiving and another for sending to achieve this need multiple Dogecoin Core
it will be great to have the multiple wallet options just like the rest of the BitcoinCore family

This is part of 1.21. Keeping this here so that we can close this once 1.21 is released. We cannot easily backport this to 1.14.

well understood @patricklodder but any idea of the time frame before getting to 1.21?

Good question. With currently only @rnicoll coding the baseline and only me reviewing his work in the little time I currently allow myself to spend on 1.21, I don't think it would be suitable for mainnet use within 6 months, maybe not even if I would make review & testing 1.21 my #1 priority. I have this expectation due to the work that needed to be done this year to stabilize 1.14 in 3 releases and still not being where it's supposed to be.
Can I turn the question around? What is the use case to need this now and is that a custodial or a non-custodial use-case? Are you able to share? Depending on how compelling the use case is, there's a slight chance that it may outweigh the difficulty to backport.

@patricklodder just the feature make work easier for developer and cost efficiency for wallet providers


Self-Hosted IR Cluster - Dispatcher specs?

Does the dispatcher node in the IR need more resources than one of the worker nodes? Its not clear to me from the documentation whether or not the individual worker nodes are sending data up to Azure or if they only feed data to Azure through the dispatcher node. Thx

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 32785d15-8202-6e44-f1d2-420ef0600f3f
Version Independent ID: 3af5fa49-7bd4-18ce-f8dc-aa4a2b8c6478
Content: Create a self-hosted integration runtime - Azure Data Factory
Content Source: articles/data-factory/create-self-hosted-integration-runtime.md
Service: data-factory
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@mwc360  Thanks for the question! We are investigating and will update you shortly.

@nabhishek Can you please look into this?

What I have observed is the role of dispatcher can be taken up by any node at any given point of time and is not fixed. So, I feel all the nodes should fulfill the minimum requirements of hardware.

@mwc360 Good practice is to use similar sized compute for all nodes since job distribution happens in a round-robin fashion. Though Dispatcher plays an additional role of fetching the jobs from queue and distributing them, but this is a fairly light-weight activity as compared to actual data movement.
Moreover, if dispatcher node goes down then another node is selected as dispatcher which can be even more problematic if the machines are not alike. Hence have all nodes of the same config!

#please-close


implement size management for class Window

This is a subtask of #6

Completed.
Fixed a bug in module oglfw::utils about class SizeT<>.


Added input image as a button

I Added the html5 input image as a type of button since it acts like one).
I just extended the current button tests and everything works.
Partial fix for Issue #612

@wkoch Thanks for thr PR!


This page need update for 21.10

Ubuntu 21.10 is release last week. Able to use this docs without any trouble. It's just need to 21.10 on the page.
[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 80707602-f283-e796-d3b8-3287fbc011dc
Version Independent ID: 1d732b15-9e64-633a-000c-ad96d9d3818a
Content: Install .NET on Ubuntu - .NET
Content Source: docs/core/install/linux-ubuntu.md
Product: dotnet
Technology: dotnet-install
GitHub Login: @adegeo
Microsoft Alias: adegeo

Thank you for reporting this. I'll have this update published with the .NET 6 updates next week.


gvrf-physics: convert the build to cmake and externalNativeBuild

use useLocalDependencies=true
build fw and extensions with this change in
open gvr-simplephysics separately (edit GearVRf-Demos/settings.gradle first line to be new File(".").eachDirMatch(~"gvr-simplephysics") {)
in the symbols section for gvr-simplephysics add these two: <your-path-to>/GearVRf/GVRf/Framework/framework/build/intermediates/bundles/debug/jni/armeabi-v7a and <your-path-to>/GearVRf/GVRf/Extensions/gvrf-physics/build/intermediates/bundles/debug/jni/armeabi-v7a
from within AS navigate to the physics source files and open whichever you need
place breakpoints and debug launch

It can be flaky with buildGvrfAndDemos=true so this is why I recommend useLocalDependencies. The described procedure worked reliably for me. Your mileage can vary.

I tested this on Linux using AS 2.2.3. I was not able to get it to set breakpoints in the physics code. I built the Framework in one instance of AS and the demo in another. I opened the physics source files with the same AS instance I used to build the demo.

I assume you also built the physics extension, right?

Tried again after git clean -fdx and still worked for me. I am with AS 2.4 Preview3, should not matter but who knows. Can you hit breakpoints in the framework then (after adding the symbols)? If you hit a native breakpoint then in the Debugger tab there is a LLDB sub-tab. Enter there "image list" and let me know what the output is. It will show where lldb is getting the symbols for libgvrf-physics from.

Tried the procedure on my other desktop. Worked again. As long as you give AS the right symbols for the binary in the apk, it works quite reliably.

Planning to merge Friday morning.


Land Ownership Tokenization

Tokenize each land block as an NFT. Whoever owns each land NFT will be its owner.
Types
New Types

Enums:

OwnerId

Token (AssetId)
AccountId

Estate Pallet Changes

Storage

EstateOwner doubleMap(OwnerId,EstateId) => ()

Calls

mint_estate: the beneficiary will be OwnerId instead of AccountId; add implementation that covers the case in which the OwnerId is Token(AssetId)
create_estate : the beneficiary will be OwnerId instead of AccountId; add implementation that covers the case in which the OwnerId is Token(AssetId)
transfer_estate: add implementation for transfering the estate NFT if OwnerId is Token(AssetId)
dissolve_estate: add implementation for burning the estate NFT if OwnerId is Token(AssetId)

@justinphamnz Do we want to tokenize both lands and estates or estates only?

@justinphamnz Do we want to tokenize both lands and estates or estates only?

Thanks @chexware. Ideally for both.

In term of implementation of the change from AccountId to TokenId, we only need tokenize function to cover AccountId to Token


Duplicate Instruction in Enc and Dec for HumanEval

Hi, great work! Why are you feeding the instruction both into the encoder & decoder? I would have expected only the encoder to receive the instruction, however, for HumanEval you do:
           prompt_batch = [INSTRUCTION.format(extract_text(prompt))]
           prompt_batch_decoder = [INSTRUCTION.format(extract_text(prompt)) + prompt]

Hi there, by doing this, we also feed the text prompt to decoder to better provide the prefix contexts for the models. We find that this is very helpful for CodeT5+ models >=2B, as these models have a deep decoder initilized from frozen GPT-style LLMs, doing this can have a better compatibility with the default behaviours of GPT models. Noth that for CodeT5+ 220M and 770M, they do not need such additional prefix prompts as they are pretrained from scratch.


MudDateRangePicker: Add StartDateClicked event

start date click event trigger in date range picker

this code provides additional functionality in date range picker to fire a event once start date is clicked, if required

@umesh2096 can you explain the use-case for this please?

Hi,
There is a business scenario which I came across.
In a range selection calendar if you want to implement enable disable
specific dates of calendar on the click of start date so that user can’t
select those disable dates as a end date then this change will fire that
event which is not available currently.
As of now as per my analysis, event triggers only after range gets selected
in calendar.
Please let me know if you have any questions
On Sat, 5 Oct 2024 at 6:28 PM, Meinrad Recheis @.***>
wrote:

@umesh2096 https://github.com/umesh2096 can you explain the use-case
for this StartDateClicked event please?
—
Reply to this email directly, view it on GitHub
https://github.com/MudBlazor/MudBlazor/pull/9886#issuecomment-2395045166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEK7TMYLE3YUDJX46NUGGLTZZ7NGBAVCNFSM6AAAAABPDWI2LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGA2DKMJWGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi,
There is a business scenario which I came across.
In a range selection calendar if you want to implement enable disable
specific dates of calendar on the click of start date so that user can’t
select those disable dates as a end date then this change will fire that
event which is not available currently.
As of now as per my analysis, event triggers only after range gets selected
in calendar.
Please let me know if you have any questions
On Sat, 5 Oct 2024 at 6:29 PM, Meinrad Recheis @.***>
wrote:

@.**** commented on this pull request.
In src/MudBlazor/Components/DatePicker/MudDateRangePicker.razor.cs
https://github.com/MudBlazor/MudBlazor/pull/9886#discussion_r1788583038:

         {

             _secondDate = null;
             _firstDate = dateTime;

           await StartDateClicked.InvokeAsync(dateTime);
           return;
       }

I am not sure about this:
if (_firstDate == null || _firstDate > dateTime || _secondDate != null)
{
_secondDate = null;
_firstDate = dateTime;
await StartDateClicked.InvokeAsync(dateTime);
return;
}
Why is the event only fired under certain circumstances?
—
Reply to this email directly, view it on GitHub
https://github.com/MudBlazor/MudBlazor/pull/9886#pullrequestreview-2349561130,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEK7TM4BOS5G6GEKWQMH4M3ZZ7NLJAVCNFSM6AAAAABPDWI2LCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDGNBZGU3DCMJTGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

OK. Your email comment showed up twice so I deleted the second copy. We also need a test case.

Unit test case required?
On Sat, 5 Oct 2024 at 6:49 PM, Meinrad Recheis @.***>
wrote:

OK. Your email comment showed up twice so I deleted the second copy. We
also need a test case.
—
Reply to this email directly, view it on GitHub
https://github.com/MudBlazor/MudBlazor/pull/9886#issuecomment-2395051484,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEK7TM7XMBFRELM3RFMG7OTZZ7PVFAVCNFSM6AAAAABPDWI2LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGA2TCNBYGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yes. To protect the feature against being broken by future PRs touching this code.

Sure will add this. Thanks for letting me know
On Sat, 5 Oct 2024 at 6:53 PM, Meinrad Recheis @.***>
wrote:

Yes. To protect the feature against being broken by future PRs touching
this code.
—
Reply to this email directly, view it on GitHub
https://github.com/MudBlazor/MudBlazor/pull/9886#issuecomment-2395052614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEK7TMZDNUOVCZSARPI2SQ3ZZ7QDJAVCNFSM6AAAAABPDWI2LCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGA2TENRRGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


No return path in emails

I can not see fails

Some hosting not enabled by default return path with sendmail.


ATAK 4.9

Is there an apk coming that is comparable with atak 4.9 ?
Thanks so much

Support for 4.9.x will come in the next month or so, after which the plugin won't support earlier versions anymore.

Hello! Do you have any ETA for now?

Could we have a compiled version of Forwarder 2.0.7 for ATAK 4.8.1? Currently the latest release only supports up to ATAK 4.7.  Or was there some particular reason why the 4.8.1 release of 2.0.7 does not exist?
Btw, when do you think you would be able to get the Forwarder 2.0.8 supporting ATAK 4.9 out? Will that also support ATAK 4.8.1 then?

@Tahkis  I think you missed the part from the 2.0.7 release note
For now the plugin will not support ATAK versions after 4.7.0.x. The plugin API changed in 4.9.x and I don't
want to maintain two versions of the plugin codebase for now, so likely we will migrate to the new plugin API
in the next month or so. There is also an issue in later versions where the plugin cannot connect to the
Meshtastic service that I need to sort out before supporting those versions.

I know people love this project, but have some patience

Hi Paul,
No problem, fully understand! Pitty the pipe has broken :-(
But as you said, lots of people seem to love this project :-)
If you need any help in testing I'm happy to contribute!
Cheers,
Tatu
ps. I also got the Samsung Xcover 4s QR code reader to work w/ Forwarder.
Not sure why it is so picky in scanning but requires a bit of vertical
movement over the code to scan -> makes sharing of the code possible.
pps But there clearly seems an issue in comms between the MT app and
Plugin. Eg configuring MT client using plugin does not work even in Android
11. I'm able to get the green CFG icon on but only if I conf from MT app
itself (and have the setting Plugin Manages Device = OFF). Yet no data gets
transfered over MT between ATAKs via Forw nor does the device discovery
work. And I am 100% sure the channel conf is equal in both radios. And all
this in A11 w/ ATAK 4.8.1, Forw 2.0.6 and MT 2.1.15.
On Thu, Jul 20, 2023, 10:42 SCWhite @.***> wrote:

@Tahkis https://github.com/Tahkis I think you missed the part from the
2.0.7 release note
For now the plugin will not support ATAK versions after 4.7.0.x. The plugin API changed in 4.9.x and I don't
want to maintain two versions of the plugin codebase for now, so likely we will migrate to the new plugin API
in the next month or so. There is also an issue in later versions where the plugin cannot connect to the
Meshtastic service that I need to sort out before supporting those versions.
I know people love this project, but have some patience
—
Reply to this email directly, view it on GitHub
https://github.com/paulmandal/atak-forwarder/issues/177#issuecomment-1643435725,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMYEKDNYGKJVB7IPDIDUQYTXRDOOTANCNFSM6AAAAAAYAJYCCM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Not asking for an eta. just curious if this is still being worked on or 4.10 now that is has been released. Thank you!


Data classification roles are unclear for Synapse

This page is listed as applying for Synapse, but there are two problems under the permissions section that I can see:

First, the built-in role SQL Security Manager does not apply to Synapse since the object does not contain a logical SQL server that is modifiable by the user. As a result, that role will not appear for users when trying to modify RBAC permissions for the workspace. The only workaround that I have found (since there doesn't appear to be a pre-built role for Synapse for this) is to create a custom role for the specific permissions needed for Synapse (simply replacing the Microsoft.SQL/etc, path):
Microsoft.Synapse/workspaces/sqlPools/currentSensitivityLabels/*
Microsoft.Synapse/workspaces/sqlPools/recommendedSensitivityLabels/*
Microsoft.Synapse/workspaces/sqlPools/schemas/tables/columns/sensitivityLabels/*

To modify:
Microsoft.Synapse/workspaces/sqlPools/schemas/tables/columns/sensitivityLabels/*

Second, the permissions I mentioned above don't make sense. It seems like more permissions are needed to read the sensitivity labels than are needed to modify them? Is this a mistake or am I missing something?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9ca439af-510f-303c-e72c-424b78ac0ac7
Version Independent ID: 616d8cf5-1631-1179-0c59-f8b4f6c1f7bb
Content: Data Discovery & Classification - Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse
Content Source: articles/azure-sql/database/data-discovery-and-classification-overview.md
Service: sql-db-mi
Sub-service: security
GitHub Login: @DavidTrigano
Microsoft Alias: datrigan

@willcotton-msft Thank you for the detailed feedback. This is being assigned to the content author to evaluate and update as appropriate.

Are you referring to standalone Azure SQL Server (dedicated SQL pool - formerly SQL DW) or Synapse Analytics ?

Hi, I haven't tested this on the standalone SQL server-I think it would work there since the object type is correct. My comments apply to Synapse Analytics only (as far as I know).
Thanks
Will
From: Madhumitatripathy @.>
Sent: Thursday, February 10, 2022 7:35 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Will Cotton @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Data classification roles are unclear for Synapse (Issue #87768)
Are you referring to standalone Azure SQL Server (dedicated SQL pool - formerly SQL DW) or Synapse Analytics ?

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F87768%23issuecomment-1034928558&data=04|01|willcotton%40microsoft.com|9d64b4ffd1d345ac7b0208d9ec9a152f|72f988bf86f141af91ab2d7cd011db47|1|0|637800968798295663|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=Mz6Dun3QEFdDk2LbKqYVGAMa6yxmrr1v%2BZgpN5Mo%2BXg%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FASPMEOUK3JLT5WAQQVZNKRTU2O5G3ANCNFSM5N6V6DLQ&data=04|01|willcotton%40microsoft.com|9d64b4ffd1d345ac7b0208d9ec9a152f|72f988bf86f141af91ab2d7cd011db47|1|0|637800968798295663|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=j9Caka93%2BWopKhcm6jk80KxrhgLL4vTkPjxheC%2FjnuQ%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|willcotton%40microsoft.com|9d64b4ffd1d345ac7b0208d9ec9a152f|72f988bf86f141af91ab2d7cd011db47|1|0|637800968798345062|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=G1AKhIxA3DYe0ATiWiVTBuZX8%2FV%2BnfvBs%2FzGlw%2ByUas%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|willcotton%40microsoft.com|9d64b4ffd1d345ac7b0208d9ec9a152f|72f988bf86f141af91ab2d7cd011db47|1|0|637800968798345062|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=yxnubR1Bgh1lxHtmb%2BdhuZGOvpL6pIrRKTdJGP53wSw%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

#assign:WilliamDAssafMSFT
#assign:nanditavalsan

Users williamdassafmsft are already assigned.

#assign:nanditavalsan

Thanks @willcotton-msft for pointing this out. We've got a doc update in flight to clarify. The Azure SQL built-in roles in this doc's Permissions section apply to a dedicated SQL pool (formerly SQL DW) but are not available for dedicated SQL pools and other SQL resources within Azure Synapse workspaces. For SQL resources in Azure Synapse workspaces, use the available actions for data classification to create custom Azure roles as needed for labelling. For more information on the Microsoft.Synapse/workspaces/sqlPools provider operations, see Microsoft.Synapse.
#please-close


about authentication

how does this tool support authentication? does it have any documents?

Authentication is implemented in Ilogtail-C (open source soon), we will provide more documents about this with coming ilogtail-C :)

Welcome further discussion, close first .


spec: improve util tests

Codecov Report

Merging #12 (da09a89) into main (8f8e09f) will increase coverage by 0.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   98.70%   98.91%   +0.20%
==========================================
  Files           7        7
  Lines         155      185      +30
==========================================
+ Hits          153      183      +30
  Misses          2        2

Impacted Files
Coverage Δ

lib/eth/key.rb
100.00% <100.00%> (ø)

lib/eth/utils.rb
93.33% <100.00%> (+0.22%)
:arrow_up:

spec/eth/key_spec.rb
100.00% <100.00%> (ø)

spec/eth/utils_spec.rb
100.00% <100.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 8f8e09f...da09a89. Read the comment docs.


Update india.md

Added Local toll-free to the phone number in the document.

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/2918


failed to get message with attachment on iOS

Perhaps related, the server complained about TOP command (not currently supported).

TOP command should be quite easy to implement in popgun

Fixed by supporting TOP command (both in ubikom and popgun clone).