Add support for openconfig/magna to KNE.

Add support for openconfig/magna to KNE. magna is a lightweight OTG
implementation that can be used as a traffic generator. It is defined as a
separate node type than HOST as it needs to be separated in ONDATRA to
distinguish it as an ATE impementation.
commit 356945c967b2a5cba7e544753384225386c75f97
Author: Rob Shakir<EMAIL_ADDRESS>Date:   Thu May 25 11:30:57 2023 -0700

    Add testing for magna node definition.

     * (M) topo/magna/magna_test.go
       - Add testing for a new node definition.

commit c377555d04172eb196818ac67f611ad8a26c3fa2
Author: Rob Shakir<EMAIL_ADDRESS>Date:   Thu May 25 11:02:20 2023 -0700

    Add support for openconfig/magna containers to KNE.

     * (M) proto/topo.proto
       - Add MAGNA as a node vendor
     * (M) proto/*(_grpc)?.pb.go
       - Regenerate protobufs.
     * (M) topo/topo.go
       - Link in the magna node definition.
     * (M) topo/node/magna/magna.go
       - Create a node definition for magna.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

40 of 40 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.2%) to 65.501%

Files with Coverage Reduction
New Missed Lines
%

topo/node/ceos/ceos.go
1
66.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
3541

Relevant Lines:
5406

💛  - Coveralls

This is blocked on https://github.com/openconfig/kne/pull/382

@alexmasi PTAL! I think this works as you described above -- I made sure that ondatra-role is always set for both types, and this should support both. I haven't tested it actually creates a lemming or magna yet - and it does require that users that have vendor OPENCONFIG specify a model in their config to get a lemming. (@DanG100 / @wenovus are probably most concerned with this at this point :-))

Also forgot to mention that all files besides openconfig{_test}.go can now be rolled back

LGTM, handing over to Daniel for review of lemming changes. Should we default to model lemming if none is provided to not break existing textprotos? @DanG100

I'd encourage us to be more explicit here and require these to be updated. Given where lemming is in its deployment, I would expect that these references are probably internal to the OpenConfig org on GitHub :-)

Also forgot to mention that all files besides openconfig{_test}.go can now be rolled back
The example (+presubmit) textprotos should also be updated, as of now the presubmit will fail

ACK - can you /gcbrun here so that I can see which presubmits fail? :-)

/gcbrun

LGTM, handing over to Daniel for review of lemming changes. Should we default to model lemming if none is provided to not break existing textprotos? @DanG100

I'd encourage us to be more explicit here and require these to be updated. Given where lemming is in its deployment, I would expect that these references are probably internal to the OpenConfig org on GitHub :-)

I don't believe many users outside of google are using lemming as of now so it should be a relatively small blast radius. We do have some internal textprotos checked in that would need updating. As adding a model before this change gets merged doesn't break anything I will handle those now.

@wenovus Looping in Wen because Daniel is OOO this week

OK, should be good-for-review.

/gcbrun

@alexmasi PTAL! I think this works as you described above -- I made sure that ondatra-role is always set for both types, and this should support both. I haven't tested it actually creates a lemming or magna yet - and it does require that users that have vendor OPENCONFIG specify a model in their config to get a lemming. (@DanG100 / @wenovus are probably most concerned with this at this point :-))

Making this explicit sounds good to me, and I agree with Alex that it makes sense to make this breaking change earlier rather than later.
Changes to lemming-related code also LGTM.

/gcbrun


Feature/1236 non applicable

What does this PR do?
Jira ticket number?
ISPGBSS-1236
Changes

Add not-applicable to the Status choices
Add remarks column to the ProjectControl table

Testing

Assuming you have created a Project:
[ ] in Postman create a Patch request to localhost:8000/api/projects/[PROJECT ID]/controls/ac-1/
[ ] In the Body, add Form-fields status: not_applicable, and remarks: This is the remarks
[ ] Send the Request
[ ] The response should show the updated status and the remark.

Setting this to a draft until #113 is done.

Setting this to a draft until #113 is done.

^^^


optimized(region): qcloud bucket policy set and get operation

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[x] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.5

/area region
/cc @zexi

Codecov Report

Merging #9677 (fbd5be2) into master (2b47be4) will increase coverage by 9.93%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9677       +/-   ##
===========================================
+ Coverage    5.99%   15.93%    +9.93%
===========================================
  Files         844      124      -720
  Lines      131395    12773   -118622
===========================================
- Hits         7879     2035     -5844
+ Misses     122815    10547   -112268
+ Partials      701      191      -510

Flag
Coverage Δ

aFlag
15.93% <ø> (+9.93%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/baremetal/nic.go

pkg/multicloud/esxi/hostnic.go

pkg/cloudcommon/db/fetch.go

pkg/monitor/alerting/rule.go

pkg/compute/models/networks_id_change_handlers.go

pkg/cloudcommon/db/domainresource.go

pkg/compute/models/cloudimages.go

pkg/mcclient/options/inter_vpc_network.go

pkg/mcclient/options/k8s/fed_clusterrolebinding.go

pkg/hostman/system_service/sdnagent.go

... and 708 more

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 2b47be4...fbd5be2. Read the comment docs.

/lgtm
/approve


[VR] Motion controller pointer ray (white) disappears after failing teleport

(Ported to GitHub, reference 20223654)
Initiate a teleport, but aim the parabolic ray somewhere you can't go (e.g. where there's no floor).
On releasing the stick, there will be no ray from the controller axis proxy.

I was unable to repro this on the latest MRTK


Exclude from Random | Poster network

We should have a way to exclude groups from the full random mode, so that those that don't want their posters to be in the full random (without parameters) who may not want their content randomized into the rest of the randomization. Perhaps we do this per poster, or on a group-basis, but the random mode without parameters should have a way to exclude posters from it.

@itsitrio My take on this is that unless you specify a group explicitly, random mode on posters should only include the community posters, not the ones associated with specific groups. That's fairly easy for us to implement code-wise and would avoid us picking up any group-specific posters in the general rotation.

The problem with just going "exclude groups" is that we (being waterwolf), want our group to be in the general rotation in most cases, and so would groups like EUFuria or i.W.A.I.T., but a group like New Eden might have stuff in their group they don't want to just have in the rotation, and just want their group in their worlds and nowhere else.
Definitely open to discussion though. I'm eepy, can talk more about tomorrow.


Miscellaneous changes

There will undoubtedly be merge conflicts when other works in progress are merged.
This PR contains:

Enhancements

IPython notebooks with preliminary demos
Addressed #52
Implemented Video -> Audio converter
Modifications to ClarifaiAPIExtractor: made select_classes handle lists, extractor only uses tempfile when provided stim does not have an associated file name

Bug fixes

Saving data in VideoFrameStims
None columns bug fix in diagnostics
Bug fix and added test to graph interface (likely merge conflicts here)
Error handling for Google extractors

General Refactoring

Moved TesseractConverter from converters/api.py to converters/image.py
Cleaned up un-used imports on several files

Coverage decreased (-3.9%) to 72.603% when pulling a258f0b642b48b14fb45c1a75d25f58af4e6d370 on qmac:random into 8d4a9290090da6421b404f4c497f290fb1b5d706 on tyarkoni:master.

I haven't had a chance to review this closely, but I'm merging it anyway because I'm going to merge a branch with major revisions shortly and will probably need to resolve a bunch of conflicts anyway.


Unit tests for crossover, mutation

Hello @DenisSidoren! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file gefest/core/opt/operators/crossover.py:

Line 57:7: E271 multiple spaces after keyword


question: what is this grey horizontal line

When yabai service is running i have a grey horizontal line below menu bar. What is it? I would disappear after stopping yabai service.

Sounds like https://github.com/koekeishiya/yabai/issues/74


Switch from TravisCI to SnabbBot

Related to #259.  More urgent now that the lwaftr is upstream.

SnabbBot has been deployed in our servers for some time now and it seems to be working fine. Closing this issue.


Bluetooth: Reassemble periodic advertising reports

Adds a buffer to the host to reassemble potentially fragmented
periodic advertising reports.
The buffer size is configurable through BT_PER_ADV_SYNC_BUF_SIZE.
Signed-off-by: Bernhard Wimmer<EMAIL_ADDRESS>

This PR is similar to https://github.com/zephyrproject-rtos/zephyr/pull/39352, and should follow the same pattern, e.g. only sending complete report to the upper layers.

This PR is similar to #39352, and should follow the same pattern, e.g. only sending complete report to the upper layers.

That sounds ok to me. It will result in changed behavior from the current version, but it will make the code a bit simpler.

@bewi-nordic seems like you forgot to squash the fixup commit?

@bewi-nordic seems like you forgot to squash the fixup commit?

Not really. I'm used to squashing at the end when there are no more changes.
Is that not how it's usually done in this repo?

Is that not how it's usually done in this repo?

Not in my experience, at least. I'm fine with looking at updated original commits. I agree though that GitHub could do a better job at showing diffs between PR revisions (e.g. like gitlab does), but it hasn't been a major bottleneck so far.

Is that not how it's usually done in this repo?

Not in my experience, at least. I'm fine with looking at updated original commits. I agree though that GitHub could do a better job at showing diffs between PR revisions (e.g. like gitlab does), but it hasn't been a major bottleneck so far.

@jhedberg Agreed. GH can do it to some extent if the PR is not rebased between revisions though.

@bewi-nordic I had a call on Friday with @alwa-nordic . He will follow up on this.

@bewi-nordic I had a call on Friday with @alwa-nordic . He will follow up on this.

Sorry, I was confusing this with #40280 . Let me take another look.


[BUG] shelley-from-scratch creates alonzo transaction.

cardano-cli transaction build-raw probably should include --shelley-era.  Otherwise I get invalid era error.

Hi @phadej,
Are you reporting that documentation needs updated?

@phadej can you please provide more details?

I don't remember the details anymore. We moved away from using those scripts.


Add max_item_levels as optional block variable key

Problem:
Theme developers can set up nested arrays as block variables. In app/views/company/sites/form_builder/_array_input.html.erb we currently sets max_nesting_level to a default of 1 for all array rows, so Creators cannot rearrange the nested items, they can only rearrange the top level items.
By providing theme developers with an additional max_item_levels key, they can define the nesting level of each array, which we will shortly use in the _array_input partial. This will allow/prevent nesting on each level as necessary. We are naming this key max_item_levels to match the name of the key with similar behaviour used in the header and footer templates.
max_item_levels is to be used in conjunction with array: true to support nested arrays in block schema.
In an ideal world only one key would be needed to define this array behaviour. E.g. array: true resolves to a max_items_level of 1, and array: false continues to not render arrays. But a separate key seems the most easily backwards compatible. Thoughts here welcome.
Arbitrarily chosen to allow up to 3 levels of nesting.

 Issue dragging/re-ordering on custom variant block


GEODE-5298: User Guide - Document Transactions + Functions Limitation

Documented the requirement that a function within a transaction must operate on colocated data.
Reinstated some cross-ref targets for improved navigation.

Oops - thanks for catching the bad JIRA number, Karen. I'll correct that.

Approvals complete. Merging manually in order to correct a typo in the original commit message (incorrect JIRA ticket number).


Refactor storage to remove circular dependencies with auth

auth.ts and userSession.ts both have dependencies on storage. Either all storage functions should be accessed through userSession or storage functions should be separate and take a userSession object as input.

https://github.com/blockstack/blockstack.js/issues/795

I'd be open to talking about the pros and cons of the user session in general and if it's still something we want. Anyone else?

I think userSession essentially represents the state of an authenticated user, and it makes sense to be defined by the auth lib. If we take that approach, the storage functions should be separated out.


NixOS on ARM documentation

Now that the wiki has been shut down, there is no official or semi-official source for NixOS on ARM documentation. Previously, the wiki was the best (only?) source:
https://nixos.org/wiki/NixOS_on_ARM
The best we have for now is archive.org, though the last capture was Sept 11 2016, so I'm not sure if anything changed between then and the shutdown time:
https://web.archive.org/web/20160911022116/https://nixos.org/wiki/NixOS_on_ARM
Anyway, now that the wiki is gone, this critical information should be added to the NixOS manual as soon as it's feasible. In the meantime, since support for the platform is still somewhat experimental (esp. for aarch64), perhaps we can use GitHub Issues as a documentation dump.
/cc @dezgeg

duplicate of: https://github.com/NixOS/nixpkgs/issues/13290

Is it a dupe? That issue refers explicitly to the wiki, and as such I would expect all such issues to be closed soon. This issue should track the adding of the ARM documentation to the manual.

Yes, every wiki page has had a ticket open for a long time, but reviewing and migrating the content doesn't seem very popular thing todo.  Let's concentrate the information in a single thread.


wishlist sync notes to grauphel

This is a feature request, i may start working on it once I familiarized with FreePascal.
Why?

grauphel is an owncloud app that syncs with tomboy, tomdroid anf conboy (and replaces snowy)
enables users to share note trees between Linux, Mac, Windows, Nokia and Android devices

Steps

[ ] create JSON objects
[ ] establish TLS connections (Ararat Synapse, ML)
[ ] implement REST API (See also tomboy-notes/tomboy#75)

Oh, that would be so cool !
Its obviously on the list but I must confess I'm not overly keen to start it myself.
Please have a look at https://github.com/tomboy-notes/tomboy-ng/blob/master/tomboy-ng/tb_sync.pas
You will see it implements a class, TTomboySyncCustom, that I designed (in my ignorance) to be usable to make any sync model. I inherent from it to make FileSync, suggest thats its a good start.
We might (ie probably) need to change TTomboySyncCustom as a network sync evolves. But I did try to think REST as I did it. It has no GUI, thats done in SyncGui and dead easy.
Be more than happy to assist in any way I can but I don't see me tackling it by myself in the immediate future.
Kardan is working on some auto installs of a full Lazarus environment but my guess is you would not need much cross platform testing, so a simple install from https://sourceforge.net/projects/lazarus/files/
I'd suggest reading http://lazarus-ccr.sourceforge.net/fpcdoc/ref/ref.html
The wiki has a lot of valuable info, a lot of out of date info and a lot missing. ie, typical wiki. The forum is full of very helpful and experienced people.
And I'd suggest working in the IDE, its hand holding is invaluable with syntax and other help always there.

The wiki has a lot of valuable info, a lot of out of date info and a lot missing. ie, typical wiki.

Regarding the sync: The Tomboy wiki is accurate.

Christian, I was referring to the FPC/Lazarus wiki.
If in doubt, please re-read my post.
David

Another issue listed on the (long term) todo list. Right now, I don't see any significent need or demand so I am unlikely to put the considerable effort in. Therefore will close, just to tidy up.  Feel free to reopen if you wish.

Sorry to reopen this issue.  Using Grauphel has allowed me to sync cross-platform (Linux, Windows, Android).  This is a rather important feature in terms of usability.  I initially choose Tomboy over GNote for this cross-platform sync feature.  Could Grauphel support be back on the roadmap?

Long Vu, no, I am sorry but I don't see the return on the effort necessary to work with Grauphel.  A few of the reasons -

Grauphel is dependent on Nextcloud and installing and maintaining a NextCloud system is not a lightweight task.
Its not an app that commercial NextCloud operators support. So you must DIY.
Tomdroid is no longer maintained, has not been for a long time. Sadly, the build process is not documented, so no one wants to take it on. As its so old, I expect getting a new version acceptable to the PlayStore would be quite a task. My own experience with Tomdroid is it has some limitations that need fixing. Sync crashes when working with Rainy (while Tomboy itself worked fine), its inability to work with notebooks....
Christian is indicating he is looking to disengage from Grauphel.
The new release of tomboy-ng provides a cross platform (Windows, Linux and MacOS) sync using Github that also allows reading and writing to your notes from any device with a browser. That's what I use to access my notes from my phone and I find it vastly preferable to the quite ugly Tomdroid sync solutions I have made previously.

My thoughts are that the problems with Tomdroid mean its very unlikely to get new users and very few people would be willing to put the efforts into building a NextCloud install just to support Grauphel.
Sorry Long Vu.
Davo


crl -out /dev/null gives permission denied

It seems to me I have to report regression in master branch in a separate issue instead "https://github.com/openssl/openssl/issues/5590#issuecomment-373502637 "
Following command ${OPENSSL} crl -out /dev/null -in "${FILE}" -hash works fine in my regression test for about 15 years. For protocol you could see command in diffs for http://roumenpetrov.info/openssh/download-20040819.html#get_f (2003-01-30 12:14:15+0200)
Reverting commits related "Check directory is able to create files for various -out option" restores previous functionality.

I am sorry, it seems like I closed #5590 prematurely. I forgot about your comments in #3709.

My understanding is that with #6033 this should be fixed. I just tried it and it seems to be ok now. Closing.


Stricter name field

closes #463

This PR bumps model RDF to 0.4.7 and other RDFs to 0.2.3, which do not allow any forward or backward slash in name fields other than run_mode:name

@oeway you can merge this if you need this. I'm off on vacation tomorrow, so I can't help with any unintended side effects. I'm careful here, because we have not bumped the general/collection/dataset RDF often yet...

No hurry, let's wait when you get back.


Add collective trainning examples and demos

The document will add later.

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


testGameEndedOrNot&changeStatusWhenAfterRollingThePlayerReachesTheEnd

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+17.6%) to 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
17.6%

Covered Lines:
151

Relevant Lines:
151

💛  - Coveralls


Add BLAS3 and LAPACK routines

This brings in operators that wrap certain BLAS3 and LAPACK routines in particular
trsm
trmm
potrf
potri
gemm
(in addition a 2-operator version of gemm and an operator for getting the sum of logs of a matrix diagonal).
The goal is to bring in enough operators in order to support specific commonly important applications, for example Gaussian Processes. With this set of operators, it is possible to

Use MxNet as a computing framework for lot of Gaussian Process work
Develop new applications that combine neural networks and Gaussian processes

An example was given at AMLC. There is a lot of active work ongoing in this area. In addition, there are other groups that are interested specifically in the Cholesky factorization (potrf).
All operators provide proper backward gradients such that they can be integrated easily into custom loss-layers of neural networks. Getting gradients is nontrivial specifically for matrix factorization, so this PR is  more than a simple wrapper around linear algebra routines.
This PR defines a framework into which we can add other LAPACK/BLAS-related operators in the future.
The plan is to first release these CPU versions and afterwards bring in the GPU ones (we are already working on that). Based on the outcome of the GPU work
The documentation for the operators is in line with the most recent general doc-updates (verified the layout on a local webserver).

@zhenwendai

I may have eventually pass a flag from config.mk down to the compile-step that enables me to detect whether compilation happens osx (but not sure yet). In case that is needed, do I have to pass such things downto mshadow (it to me as if its make finally sets all relevant "-D" flags in the compile)?

does all the blas libraries include lapack by default? Does this PR support all lapack variants?
Is lapack support turned on by default? Is there an option to turn it off?

IMO this should be all done now. I have squashed all the commits into a single one and pushed again. Unfortunately there are some build failures but they seem to be all unrelated (scala, some github issue with cub etc). They seem to pop up by today when I incorporated the latest MXNet code. Eric, can you take a look? May be you have an idea. Has something pushed recently that explains that?
Summary of the changes:

Added a set of BLAS3/LAPACK based operators. This set is rich enough to support a set of interesting linear algebra applications including Gaussian processes (standalone or integrated with deep learning strategies for parameter estimation). There is already interest from several other sides specifically on the Cholesky factorization.

The operators are currently avail only for CPU but we are working on GPU support already and are committed to supply it based on cuSolver.

For the LAPACK operators (potrf,potri), a low level MXNet-specific abstraction has been implemented that enable us to switch the underlying LAPACK integration easily without going through the entire MXNet code. This abstraction currently supports only potrf/potri but can be extended easily whenever there is the need to make more lapack-functions available.

This low level abstraction is currently just for CPU. We may combine GPU and CPU together into a higher level abstraction when bringing in GPU-support.

The LAPACK-abstraction interfaces directly with the core Fortran-libraries on all platforms. This is the only consistent way as C-wrappers for lapack differ heavily between platforms and all lapack-packages that are relevant for us (and likely all other ones as well) use anyway the underlying Fortran library.  This is also the way numpy integrates lapack (just that numpy uses an extra utility to generate the C-declarations from the fortran library automatically).

Above method should be stable as the LAPACK-fortran interfaces are unlikely to change ever.

All of the usual BLAS-packages that we integrate with MXNet (openblas,apple,atlas,mkl) include lapack already by default. Smaller differences: On Ubuntu, the lapack library is not installed automatically with openblas, it must be installed explicitly. On Windows, blas and lapack are mangled into a single library. apple/atlas/mkl contain lapack  automatically. When using openblas, we have to add a linker flag to include liblapack. Makefiles, configuration files etc have been updated accordingly, also the installation documentation.

Whenever MXNet is compiled with one of the BLAS libraries openblas/atlas/mkl/apple as well as for all compiles on windows, a compiler flag -DMXNET_USE_LAPACK is set that will activate the LAPACK-abstraction in the C++ code and add the lapack library to the linker step (if necessary for the platform). If the compiler flag is not present, then dummy stubs will be generated in the C++ abstraction  that will cause a runtime error with appropriate error message whenever a lapack-function is called. This ensures that MXNET can always be compiled even when no lapack is available. Though as lapack will likely become soon a vital part of MXNet and is also available on all platforms, I think we will only use that for some potential special "lightweight" builds.

Once again, I would be happy if someone else can look into the mysterious build errors. I got all compiled clean before but now they pop up.

Sorry what build errors exactly?

In c_lapack_api.h, all functions follow the same signature. It'd be great if we have a couple of more lines of code to illustrate how the MXNet abstraction interface will be like for LAPACK functions with different signature?

Jenkins failed on some nodes immediately with this:
[build-cpu] Running batch script
c:\jenkins_slave\workspace\build-cpu>git submodule update --init
error: no such remote ref 01347a797c620618d09e7d2d90bce4be4c42513e
Fetched in submodule path 'cub', but it did not contain 01347a797c620618d09e7d2d90bce4be4c42513e. Direct fetching of that commit failed.
script returned exit code 1
Any ideas?

So apt-get install libopenblas-dev won't install lapack? In that case we probably should add an USE_LAPACK option in config.mk and turn it off by default for openblas.
Also maybe we should turn off lapack for amalgamation. How big is lapack lib?

I thought that Dockerfile is only for CI test? Just wished to point out 'liblapack-dev' may not be the LAPACK binaries of OpenBLAS. If we consider it OK things are fine with me.

I think this is done now.
I added an additional flag to the configs USE_LAPACK which is 1 by default. So there is always an easy option to turn it off.
In the default mode (USE_LAPACK=1), it will add lapack support whenever we use one of the blas distributions that contain lapack (apple/atlas/openblas/mkl). Concerning Ubuntu, the state is that 14.04 and 16.04 are almost equivalent: In both cases, lapack is part of the official packages. The difference is that on 14.04, installing openblas will not automatically install the lapack library while in 16.04 it does. In both cases,
sudo apt-get install -y libopenblas-dev liblapack-dev
will get all necessary pieces (just that in 16.04 there would be no need for referencing liblapack explicitly, but it will work either way). Tested that explicitly on the different images.
So our docker container can happily stay at 14.04 with the small change that it also installs liblapack-dev now. No need to migrate to 16.04.
In my most recent run, one of the travis-ci builds times out when doing some tests on neural networks (not related to the new functionalities herein). Seen this happen in the past from time to time, may be we want to give this tests a bit more time by default. So all is clean.
I will work on integrating cuda support for these operators  as soon as this PR gets integrated. Don't want to pile up more stuff on top of this. This will result in a small bit of internal restructuring. The goal would be to provide a common internal abstraction layer that handles the different DTypes and CPU vs. GPU automatically for the blas3/lapack functions (as suggested by the reviews).
Let me know what you think.

Alternatively, could we merge this PR with CPU code first so that I could submit my PRs on tensors? I'll need to put more LAPACK interfaces in 'c_lapack_api.h'.

A tiny clarification: on Ubuntu 16.04 the official build 'libopenblas.so' mangled in both BLAS/LAPACK symbols but the one on 14.04 only BLAS symbols. Always linking against the Netlib's version is a viable way to get it work. It really just depends on what we intend to do.

This was what I wanted to say as well: First merge this PR with CPU code before adding anything else.

Let's either make USE_LAPACK=0 by default or automatically turn it of when we cannot detect lapack.
In short, we shouldn't break build for people who don't have lapack installed.

I think we have then to do the "detection" flow eventually in which we dynamically turn it off and issue a warning message. Though I rather would submit this flow with a separate PR soon to keep us going here and not complicate things further.
So I will make the default not to use lapack (but for a short period). The downside of this is that I then have to disable also all the tests for these operators in test_operator.py, so we won't run automatic regressions (unless we would modify Jenkins setup). I think this is bad, but tolerable for a short time.
Ok with that approach Eric?

Cool

Can I ask what did you mean "We cannot break user's build" exactly, say, for this PR? For my sense, the repo evolves naturally as long as we update the source files, Makefiles in a way that the build and test succeed?
Could you confirm the the storage space for a Tensor is contiguous or not? For CPU code, I often saw the stride different from the number of columns; whilst it seems much of the GPU code supposed the storage space is contiguous?

Concerning stride: I'm looking into how we can support this in general. Should be easily possible using lda/ldb arguments. If this is the case, there may be a small change to the signatures of the abstractions. This should all be rolled in when adding the CUDA-support.
Concerning build stability, leave this to Eric to answer.


server: no way to gracefully shut down connection

This doesn't fit your demands? https://github.com/mirage/awa-ssh/pull/52

No, it closes the connection somewhat abruptly (as noted in PR).  Goodbye!" and have that arrive to the client before shutting down.

You probably can do something into the Lwt_switch hook.


Change Client Role

ENHANCEMENT

Describe the enhancement you are requesting. Enhancements include:
change the role of clients clients.Role == admin / user. As referenced here https://github.com/absmach/magistrala/blob/a5fd7b037aeaf96d439157fa864583cb8ea675ec/users/service.go#L511C1-L547C2

Indicate the importance of this enhancement to you (must-have, should-have, nice-to-have) - nice-to-have

@rodneyosodo , Could you please explain more about this Ticket. ?


No RF5Fix.cfg file generated

Hi!
my RF5Fix.cfg don't generate when I launch the game. Only a BepInEx.cfg. I tried to open the game without the launcher, deleting the config folder, dowload the newest and latest version and " Copying my plugins from the BepinEx/plugins into Rune Factory_5_Data/Plugins" ( wich is the "official" solution) and still not working...
Can someone help ?
Thanks.

Can you upload your log? You can find it in <GameDir>\BepInEx\LogOutput.log.

Rune_Factory_5_Data/Plugins is only used for Unity and its associated tools so that should not be touched

Hi ! I'm confused but I don't have the LogOutput.log in my BepInEx folder.

that means you didnt "install" everything correctly
extract everything in RF5fix into your RF5 install directory
your RF5 install directory must look like something like this

Extracted all to installation directory.
Now my install directory just like above, and it did not work. And there is no log file in BepInEx dir.

Did you run the game? Without the launcher booting?

Yeah I've disabled launcher and run the game multiple times.
But it seems didn't work, config and log didn't created.

Try restarting your computer after extracting the files from RF5Fix into your game folder. I was getting the same thing but after a restart it worked first try for some reason.


Uncaught TypeError: Cannot destructure property 'url' of 'h[y]' as it is undefined.

I am unable to use the "Search documentation" option for Transformers.js due to the above error.
Steps to reproduce:

Visit https://huggingface.co/docs/transformers.js/index
Click search documentation
Enter text
Press enter

This error is produced in the console:

cc @mishig25

Whoops - wrong repo


[MAPNIK] new port added

Describe the pull request

What does your PR fix? Fixes #
Adds new port for mapnik https://github.com/microsoft/vcpkg/issues/7526
Which triplets are supported/not supported? Have you updated the CI baseline?

mapnik:arm-uwp=fail
mapnik:x64-uwp=fail

Does your PR follow the maintainer guide?
Yes

This port has a dependency to the following package
https://github.com/microsoft/vcpkg/pull/11652

It seems the review suggestions are not been resolved yet.
Could you please check them again?

It seems the review suggestions are not been resolved yet.
Could you please check them again?

Hi, I had addressed them but I was trying to figure out the reason why it fails on x64-windows and Linux but I found out this error for Linux build.
https://github.com/microsoft/vcpkg/issues/11780
and on my machine x64-windows builds with no issues but I think here it fails.

OK. You can push them after you solved the failures. I will try to review this PR again when you have done all work for this PR.

Thanks. I pushed almost all of the changes. however still waiting for the results of the checks for x64-windows and linux.

@am2222
Could you please resolve the conflicts?

@NancyLi1013 Thanks. I did not notice that conflict. I resolved it.

Could you please resolve the conflicts again?

Could you please resolve the conflicts again?

Sure, thanks. I am trying to make a set of patches. I will push it soon. I found the reason why it is breaking on windows tests

Hi @am2222
Could you please resolve the conflicts?

Hi @am2222
Could you please resolve the conflicts?

Hi @NancyLi1013 ,
Thanks for the comments, I will fix them ASAP, I have a deadline by the end of this month and after it I will finish this port, I had some difficulties with making patches and I had to learn how to make them for a package.
Thanks,
Majid

@am2222
Sorry for the late response.
Please let me know if you need any any from us.

@am2222
Sorry for the late response.
Please let me know if you need any any from us.

@NancyLi1013  Hi Nancy,
Thanks so much, Actually I had a question, I wanted to know if there is any tuturials for making patches for vcpkg packages? I am facing errors in making patches and they are mainly because of vcpkg is failing in applying patches.

You can refer to this doc .
Hope it can help you some.
Please don't hesitate to ask for help from us if we do can help you.

@am2222
Could you please resolve the conflicts?

@am2222
Could you please resolve the conflicts?

Hello @NancyLi1013
Yes I am working on it. will update it today

/azp run

The regressions on x64-windows and x64-windows-static are like this:
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(115): error C2061: syntax error: identifier 'string'
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(132): note: see reference to class template instantiation 'mapnik::box2d<T>' being compiled
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(118): error C3646: 'to_string': unknown override specifier
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(118): error C2059: syntax error: '('
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(118): error C2238: unexpected token(s) preceding ';'

Could you please look into this?

The regressions on x64-windows and x64-windows-static are like this:
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(115): error C2061: syntax error: identifier 'string'
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(132): note: see reference to class template instantiation 'mapnik::box2d<T>' being compiled
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(118): error C3646: 'to_string': unknown override specifier
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(118): error C2059: syntax error: '('
D:\buildtrees\mapnik\src\mapnik\include\mapnik/geometry/box2d.hpp(118): error C2238: unexpected token(s) preceding ';'

Could you please look into this?

@NancyLi1013  Hi,
Yeah sure I will fix it. I was looking for the link of log files to see the errors, but I have lost that link. Thanks

@NancyLi1013 Hi,
Sorry for my late reply. Is it possible to share me the full log files? Since I am still trying to find a solution for the errors and could not find any. The even don't happen on my machine with the vcpkg that I have.
Thanks

/azp run

It seems there are some problems on CI now. I will provide the latest log once it is normal.

For x64-windows, vcpkg was giving a command parse error for install mapnik[proj4,input_shape]. I had to change all the input_* features to input-* in the CONTROL and portfile.cmake to allow install mapnik[proj4,input-shape].
For x64-windows using Visual Studio 16.7.5 for vcpkg to compile I had to:
Add #include  in src\mapnik\include\mapnik\util\char_array_buffer.hpp
Add #include  in src\mapnik\include\mapnik\box2d.hpp
For linking errors from including mapnik headers in my code:
In src\mapnik\include\mapnik\enumeration.hpp disable the #ifdef _MCS_VER at line 278. This might be because I was using /Zc:preprocessor when compiling my code.

For x64-windows, vcpkg was giving a command parse error for install mapnik[proj4,input_shape]. I had to change all the input_* features to input-* in the CONTROL and portfile.cmake to allow install mapnik[proj4,input-shape].
For x64-windows using Visual Studio 16.7.5 for vcpkg to compile I had to:
Add #include <algorithm> in src\mapnik\include\mapnik\util\char_array_buffer.hpp
Add #include <string> in src\mapnik\include\mapnik\box2d.hpp
For linking errors from including mapnik headers in my code:
In src\mapnik\include\mapnik\enumeration.hpp disable the #ifdef _MCS_VER at line 278. This might be because I was using /Zc:preprocessor when compiling my code.

Thanks I will apply the changes you mentioned and will push request again. Thanks

@am2222
Could you please resolve the conflicts?

@NancyLi1013 I think so far it does not work on the x64_linux,x64_osx,x86_windows,arm_uwp. I think there is an issue with one of the dependencies. Can I have the logs?

You can get the log here:
https://dev.azure.com/vcpkg/public/_build/results?buildId=42695&view=artifacts&type=publishedArtifacts

For x64-windows, vcpkg was giving a command parse error for install mapnik[proj4,input_shape]. I had to change all the input_* features to input-* in the CONTROL and portfile.cmake to allow install mapnik[proj4,input-shape].

These changes are (still) needed. I also needed to add boost-msm to the dependencies.
I was building x64-windows with dependencies as static (however gdal, icu, boost-regex, libpq and openssl need to be dynamic).

For x64-windows, vcpkg was giving a command parse error for install mapnik[proj4,input_shape]. I had to change all the input_* features to input-* in the CONTROL and portfile.cmake to allow install mapnik[proj4,input-shape].

These changes are (still) needed. I also needed to add boost-msm to the dependencies.
I was building x64-windows with dependencies as static (however gdal, icu, boost-regex, libpq and openssl need to be dynamic).
After those changes the build was successfull though (haven't linked against it yet).

Are you working with latest version of mapnik? Since I could not make it work with the latest version

Are you working with latest version of mapnik? Since I could not make it work with the latest version

I'm using the version you have used in this pull request i.e.:
set(GIT_URL "https://github.com/am2222/mapnik-windows.git")
set(GIT_REV "cfa268fa6ab438568b9b5320f6fce4317f0e3d8e")

@SNiLD  Can you please let me know what other changes did you made that it worked? It works on my local machine but breaks here

Well first of all I compiled with Visual Studio 2017 Express Edition in x64 mode (from command prompt started with C:\Program Files (x86)\Microsoft Visual Studio\2017\WDExpress\VC\Auxiliary\Build\vcvarsall.bat x86_x64).
I used following triplet (named x64-windows-mapnik):
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE static)
if(PORT MATCHES "mapnik|gdal|icu|boost-regex|libpq|openssl")
    set(VCPKG_LIBRARY_LINKAGE dynamic)
endif()

The build command I used was: vcpkg install mapnik[input-csv,input-gdal,input-geobuf,input-geojson,input-ogr,input-pgraster,input-postgis,input-raster,input-shape,input-sqlite,input-topojson,proj4] --triplet=x64-windows-mapnik
I didn't need to do other changes than mentioned in my other post.

Now that I tried to use mapnik I faced couple of problems with this build. First you need to apply https://github.com/mapbox/variant/pull/182 and https://github.com/mapnik/mapnik/pull/4184 to fix MIN/MAX macro incompatibility with Visual Studio.
Also the dependency headers are not installed by your CMakeLists.txt. I can't provide you a pull request because Github doesn't support me to have fork of fork when I already have fork of the main project. 💯
So here is a diff what I needed to add to your CMakeLists.txt:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 3e6f4049c..8ae6a09a1 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -163,7 +163,9 @@ set(mapnik_include_paths
     deps/mapbox/polylabel/include
     deps/mapbox/variant/include)

-
+install(DIRECTORY deps/agg/include/ DESTINATION include CONFIGURATIONS Release)
+install(DIRECTORY deps/mapbox/geometry/include/ DESTINATION include CONFIGURATIONS Release)
+install(DIRECTORY deps/mapbox/protozero/include/ DESTINATION include CONFIGURATIONS Release)

 include_directories(${mapnik_include_paths}  ${thirdparty_include_paths})

Btw. I have made CMake support for mapnik long time ago based on their SCons scripts (version 3.0.11). Maybe those could help you as well: https://github.com/SNiLD/mapnik/tree/cmake

@SNiLD Thanks for the information, I am currently doing my comp exam until mid Dec, I will try to fix them then,
thanks so much,

@am2222
Is work still being done for the PR? I noticed that mapnik  was also added in another PR #14628.

Hi @NancyLi1013 , I could not manage to fix the issues with it yet. I had to take my comp exam and could not spend much time on it. I am not sure if the other PR has solved it or not. If yes we can use it, However I will update the forked mapnik repo with the latest mapnik version

@am2222 yes, I have resolved the issues.
There is now a PR @ mapnik for the cmake build https://github.com/mapnik/mapnik/pull/4191
Additionally mapbox/geometry and mapbox/polylabel were added to vcpkg to not to fetch the contents in the port

@mathisloge Hi, That is great, so it seems we will finally have it on windows and its nodejs package will also work. that is perfect, probably we need also port its python package as well

@am2222 that's right. But unfortunately I don't have any spare time to do the node build.
But it might be easy with https://github.com/cmake-js/cmake-js

@am2222
Thanks for the PR. I'm closing this for now since there's been no progress for a long time. If you'd like to continue working on it, please reopen and ping us!

@am2222 if you still using node-mapnik I've added a proof of work https://github.com/mapnik/node-mapnik/pull/976

@mathisloge Thanks, are you using the github repo of mapnik for building it? if we can fix this port it will be perfect.

@am2222
https://github.com/microsoft/vcpkg/pull/14628 in conjunction with https://github.com/mapnik/mapnik/pull/4191 are working pretty well.

@am2222 the cmake support is now merged into mapnik@master.

@mathisloge thanks man, That is a great new. We finally are able to have windows version alive


Nothing happened after "Start local client"

Describe the bug
Run 'RemoteStart' and everything works well, but after Start Local Client, A float window and show up and disappear, then nothing changed.
I can run 'RemoteSessionInfo' to check the remote servers info, it looks well, but I can't connect it using :RemoteStart
To Reproduce
Steps to reproduce the behavior:

Go to RemoteStart
Choose yes in Start Local Client
An empty windows shows up and disappear
Nothing changed

Expected behavior
After I chose Start Local Client, I should connect the remote nvim.
System Info

Your local OS:  Mac OS X 13.4.1
Local Neovim version: neovim 0.9.0
Remote host OS (if applicable): Debian 11
Remote Neovim version (if applicable):  neovim 0.10.0

Additional context
Should I open the firewall port? But afaik, the port is dynamic in different sessions.

Could you verify this with a version lower than 0.9.2 on remote or upgrade your local to > 0.9.1? There was a breaking change in 0.9.2 (you can read more about it in the release) that makes 0.10.0 incompatible with 0.9.0.

After upgrading to 0.9.4, everything is working fine.
I'm delighted to have a plugin like this. I'm eagerly looking forward to even greater enhancements in the future!


VS Code 1.57 no longer picks up environment from ~/.bashrc on Linux

Does this issue occur when all extensions are disabled?: No
But this is a red herring! To run with extensions disabled, I had to launch VS code from a terminal which affects the environment code was launched in.

VS Code Version: 1.57
OS Version: Ubuntu 20.04

Steps to Reproduce:

Add this line to ~/.bashrc:
export GCC_10_ARM_NONE_EABI_BIN=/opt/gcc-arm-none-eabi-10-2020-q4-major/bin/

Install VS Code using the debian package.

Launch VS Code using the GNOME Activities menu or some other launcher - not from a terminal.

Start a new workspace and add this to the workspace settings:
"terminal.integrated.env.linux": {
    "CROSS_COMPILE": "${env:GCC_10_ARM_NONE_EABI_BIN}arm-none-eabi-"
},

Restart VS Code and open the workspace again.

Open a terminal in VS Code

Run echo $CROSS_COMPILE in the VS Code terminal. The result is arm-none-eabi-. Prior to VS Code 1.57, the result was /opt/gcc-arm-none-eabi-10-2020-q4-major/bin/arm-none-eabi-

Close VS Code

Launch VS Code from an external terminal.

Repeat steps 5 to 7. The result is /opt/gcc-arm-none-eabi-10-2020-q4-major/bin/arm-none-eabi- as expected. This is because the external terminal set the environment from ~/.bashrc and code inherited it.

I'm guessing this is fallout from #108804? e.g. the config options are now resolved before the user environment is resolved. Maybe a solution is to reevaluate config options after that?

Do you set the terminal.integrated.inheritEnv setting?

Yes, terminal.integrated.inheritEnv is enabled in my user settings.

Variable resolution may be working off the wrong environment

Report of "args": [ "new-session", "-A", "-s", "${workspaceFolderBasename}" ] not working in https://github.com/microsoft/vscode/issues/120667#issuecomment-875182389

/duplicate https://github.com/microsoft/vscode/issues/115560


New package: BumpStdlibs v1.0.0

Registering package: BumpStdlibs
Repository: https://github.com/JuliaPackaging/BumpStdlibs.jl
Created by: @DilumAluthge
Version: v1.0.0
Commit: 9036dd98c90c4088f6ad034b2af4917c8d984925
Reviewed by: @DilumAluthge
Reference: https://github.com/JuliaPackaging/BumpStdlibs.jl/commit/9036dd98c90c4088f6ad034b2af4917c8d984925#commitcomment-44753262

temporary block


Added support for PHP 8.4

Thanks!

There's some weird CI failure with checking "box" requirements (seems it doesn't support 8.4 yet). I'll let you figure it out. Can we get a tag now anyway?


synapses file + changes to dataset/sample

I made a new synapse file (with edits).

not tested tho (will try tmr but as said earlier but connecting to fido from my end has given me problems)

Also made changes to dataset

not all changes i wanted to make have been uploaded yet (commenting + reworking)

anything also you can let met know

made a new file (semantic3.py) which flows better with semanticdataset.py and synapses (might make further changes to semanticdataset.py for my current project testing).


Update @carbon/icons-angular to not have a default entrypoint

Due to size concerns of our icon library, we're going to initially default to requiring the full path for an icon component. For example:
// Not preferred, bundle size problems
import { SomeIcon } from '@carbon/icons-angular'

// Preferred
import SomeIcon from '@carbon/icons-angular/es/some-icon/size';

This issue is for implementing this pattern in @carbon/icons-angular.

cc @cal-smith, do you think you'll have some time over the next week or two to help out with this? Locked the package as private in the meantime so we don't publish over existing packages 👍

Yep 👍 I'll make some time to take a look
I can't seem to assign myself to the issue, but my name should be on this one


Downloads boost in search

~Fixes~ Helps with #3932

Pull the packages monthly downloads as part of the BigQuery trending query.
Add the monthly downloads to the database and index.
Refactor the Elasticsearch logic into its own module
Remove hardcoded sorting in the template in favor of "search modes"
Include an additional "Popularity" mode applying a function score modifier to the search to allow more popular packages to score higher

The boost modifier to the query is implemented in a fairly naive way, I am by no means an Elasticsearch expert and would very much welcome some feedback on how to improve it.
I've tested it locally by:

running the BQ query manually,
exporting the results as a CSV,
modify the code in the compute_trending task to read from the CSV as a source of results
trigger compute_trending manually and reindexing

@yeraydiazdiaz Is this ready to be reviewed?

@brainwane It’s probably out of date on many areas, the migration probably won’t work for a start. I’ll update it when I get a chance, shouldn’t be hard.

@yeraydiazdiaz I think that's also in sync with the suggested splitting of this PR into migration / feature-implementation PRs, since ISTM that the frontend+cleanup work here wouldn't need too many changes. :)

Thanks for reviewing @pradyunsg and @ewdurbin, I'll be splitting this into different PRs


Small changes to CLUtil to make it more extensible. Added build options.

I thought you might be interested in these changes:
I added a CLBuildOption data constructor that allows any OpenCL build parameter to be passed to new functions kernelFromSourceWOptions and loadProgramWOptions
I made some datatypes available by importing CLUtil/KernelArgs, these are needed (I think to define polymorphic kernel calls).
I added a typeclass called OpenCLSource that allows on to define instances for other types of source such as various bytestreams.

Oh yeah also updated Monoids to use Semigroups.

Looks great. Thank you!


routing 2.2

I'm a beginner in cyclejs, so sorry for maybe dumb questions. And my english)
I'm searching routing solutions. Encore i'm looking for answer on question: "Can i create spa with cyclejs".
I tried to use cyclic-router, everything is working, but page is always refreshing on click link. I.e. as i think it's not spa approach.
Later i found your repository and examples in routing. I thought that I found what I was looking for. But i found one detail: when i refresh page in "some_link" in app, server gives me "Cannot GET /some_link".
Can you explain me why it causes and tell how to create spa using cyclejs?

I tried to use cyclic-router, everything is working, but page is always refreshing on click link. I.e. as i think it's not spa approach.

If page is refreshes at click – it basically means click is not intercepted and default browser behavior is applied. Different routers provide different techniques and APIs to enable this interception but it should be there in one way or another.

But i found one detail: when i refresh page in "some_link" in app, server gives me "Cannot GET /some_link".

This is intentional and correct. I leave one link to demo that links which are not declared in router are not intercepted (thay may lead for external site or app).

Thanks for answer.

But i found one detail: when i refresh page in "some_link" in app, server gives me "Cannot GET /some_link".

I meant that when i refresh localhost:8080/about or something declared in router link my browser gives me "Cannot GET /about" whatever. Why it causes?

I meant that when i refresh localhost:8080/about or something declared in router link my browser gives me "Cannot GET /about" whatever. Why it causes?

Absence of backend. As we have only public/index.html the only possible entry point is /.
After entry JS is used to control stuff but with direct access (or refresh) there is no JS because page itself is absend.
"Workarounds":

add public/about.html or public/about/index.html etc. pages with the same content as index.html. Drawback: DRY violation
add backend part


Fix binder

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read and understand the Code of Conduct.
[x] Read and understood the licensing terms.
[x] Searched for existing issues and pull requests before submitting this pull request.
[x] Filed an issue (or an issue already existed) prior to submitting this pull request.
[x] Submitted against master branch.

Description

What is the purpose of this pull request?

Fixes binder builds and updates binder pin
Related Issues

Does this pull request have any related issues?

Addresses an item listed in https://github.com/jupyterlab/jupyterlab-data-explorer/issues/113
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

LGTM. Merging.


[backport] Add header file generated by Cython to gitignore

Backport of #1700

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit a05776c2630e6859503540dfae9d084faec1da25, target branch v5) succeeded!


More building Exceptions

When building controlgallery i got  no error, but when i run/debug it throws a runtime Exception.

Exception thrown: 'System.BadImageFormatException' in SkiaSharp.dll
Exception thrown: 'System.TypeInitializationException' in Avalonia.Skia.dll

Its probebly me, but if someone have a hint, please let me know.
I realy want to contribute to this awesome project, but somehow Fork and build does not work for me.
Win 10
VSCE 16.5.5
Regards,
Remco

Try running .net core version of the control catalog. I think desktop one has issues at least on win32.

duh!!!!
Sometimes i am such a dork haha
Tnx,
Remco


Password cannot be changed

Describe the bug
I changed the password in the .env file. But it was wrong.
To Reproduce
Steps to reproduce the behavior:
git clone --depth 1 https://github.com/brocoders/nestjs-boilerplate.git my-app
cd my-app/
cp env-example .env (change password: secret ---> sec333ret)
docker compose up -d

check status run

root@iZ2ze8qk0bio1k49bk5lrrZ:~/project/my-app# docker compose logs
my-app-postgres-1  |
my-app-postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
my-app-postgres-1  |
my-app-postgres-1  | 2023-08-07 14:34:50.619 UTC [1] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
my-app-postgres-1  | 2023-08-07 14:34:50.619 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
my-app-postgres-1  | 2023-08-07 14:34:50.619 UTC [1] LOG:  listening on IPv6 address "::", port 5432
my-app-postgres-1  | 2023-08-07 14:34:50.624 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
my-app-postgres-1  | 2023-08-07 14:34:50.639 UTC [23] LOG:  database system was shut down at 2023-08-07 14:33:42 UTC
my-app-postgres-1  | 2023-08-07 14:34:50.647 UTC [1] LOG:  database system is ready to accept connections
my-app-postgres-1  | 2023-08-07 14:35:00.787 UTC [28] FATAL:  password authentication failed for user "root"
my-app-postgres-1  | 2023-08-07 14:35:00.787 UTC [28] DETAIL:  Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"
my-app-adminer-1   | [Mon Aug  7 14:34:51 2023] PHP 7.4.27 Development Server (http://[::]:8080) started
my-app-maildev-1   | MailDev using directory /tmp/maildev-1
my-app-maildev-1   | MailDev webapp running at http://<IP_ADDRESS>:1080
my-app-maildev-1   | MailDev SMTP Server running at <IP_ADDRESS>:1025
my-app-api-1       | wait-for-it.sh: waiting 15 seconds for postgres:5432
my-app-api-1       | wait-for-it.sh: postgres:5432 is available after 1 seconds
my-app-api-1       |
my-app-api-1       | ><EMAIL_ADDRESS>migration:run
my-app-api-1       | > npm run typeorm -- --dataSource=src/database/data-source.ts migration:run
my-app-api-1       |
my-app-api-1       |
my-app-api-1       | ><EMAIL_ADDRESS>typeorm
my-app-api-1       | > env-cmd ts-node -r tsconfig-paths/register ./node_modules/typeorm/cli.js --dataSource=src/database/data-source.ts migration:run
my-app-api-1       |
my-app-api-1       | Error during migration run:
my-app-api-1       | error: password authentication failed for user "root"
my-app-api-1       |     at Parser.parseErrorMessage (/usr/src/app/node_modules/pg-protocol/src/parser.ts:369:69)
my-app-api-1       |     at Parser.handlePacket (/usr/src/app/node_modules/pg-protocol/src/parser.ts:188:21)
my-app-api-1       |     at Parser.parse (/usr/src/app/node_modules/pg-protocol/src/parser.ts:103:30)
my-app-api-1       |     at Socket.<anonymous> (/usr/src/app/node_modules/pg-protocol/src/index.ts:7:48)
my-app-api-1       |     at Socket.emit (node:events:514:28)
my-app-api-1       |     at Socket.emit (node:domain:489:12)
my-app-api-1       |     at addChunk (node:internal/streams/readable:324:12)
my-app-api-1       |     at readableAddChunk (node:internal/streams/readable:297:9)
my-app-api-1       |     at Socket.Readable.push (node:internal/streams/readable:234:10)
my-app-api-1       |     at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
my-app-api-1       |   length: 100,
my-app-api-1       |   severity: 'FATAL',
my-app-api-1       |   code: '28P01',
my-app-api-1       |   detail: undefined,
my-app-api-1       |   hint: undefined,
my-app-api-1       |   position: undefined,
my-app-api-1       |   internalPosition: undefined,
my-app-api-1       |   internalQuery: undefined,
my-app-api-1       |   where: undefined,
my-app-api-1       |   schema: undefined,
my-app-api-1       |   table: undefined,
my-app-api-1       |   column: undefined,
my-app-api-1       |   dataType: undefined,
my-app-api-1       |   constraint: undefined,
my-app-api-1       |   file: 'auth.c',
my-app-api-1       |   line: '326',
my-app-api-1       |   routine: 'auth_failed'
my-app-api-1       | }
root@iZ2ze8qk0bio1k49bk5lrrZ:~/project/my-app#

Expected behavior
change password.
Desktop (please complete the following information):

OS: ubuntu 20
NodeJS Version 18

@hankaibo you need to change password in database directly or remove .data/db folder and run docker compose up -d again

@Shchepotin thanks replying.
✔ Container my-app-adminer-1   Started                                                                                2.1s
 ✔ Container my-app-api-1       Started                                                                                2.2s
 ✔ Container my-app-maildev-1   Started                                                                                2.2s
 ✔ Container my-app-postgres-1  Started                                                                                2.2s
root@iZ2ze8qk0bio1k49bk5lrrZ:~/project/my-app# docker compose logs
my-app-postgres-1  | The files belonging to this database system will be owned by user "postgres".
my-app-postgres-1  | This user must also own the server process.
my-app-postgres-1  |
my-app-postgres-1  | The database cluster will be initialized with locale "en_US.utf8".
my-app-postgres-1  | The default database encoding has accordingly been set to "UTF8".
my-app-postgres-1  | The default text search configuration will be set to "english".
my-app-postgres-1  |
my-app-postgres-1  | Data page checksums are disabled.
my-app-postgres-1  |
my-app-postgres-1  | fixing permissions on existing directory /var/lib/postgresql/data ... ok
my-app-postgres-1  | creating subdirectories ... ok
my-app-postgres-1  | selecting dynamic shared memory implementation ... posix
my-app-postgres-1  | selecting default max_connections ... 100
my-app-postgres-1  | selecting default shared_buffers ... 128MB
my-app-postgres-1  | selecting default time zone ... UTC
my-app-postgres-1  | creating configuration files ... ok
my-app-postgres-1  | running bootstrap script ... ok
my-app-postgres-1  | sh: locale: not found
my-app-postgres-1  | 2023-08-08 01:01:45.795 UTC [31] WARNING:  no usable system locales were found
my-app-postgres-1  | performing post-bootstrap initialization ... ok
my-app-postgres-1  | syncing data to disk ... ok
my-app-postgres-1  |
my-app-postgres-1  | initdb: warning: enabling "trust" authentication for local connections
my-app-postgres-1  | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
my-app-postgres-1  |
my-app-postgres-1  | Success. You can now start the database server using:
my-app-postgres-1  |
my-app-postgres-1  |     pg_ctl -D /var/lib/postgresql/data -l logfile start
my-app-postgres-1  |
my-app-postgres-1  | waiting for server to start....2023-08-08 01:01:47.139 UTC [37] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
my-app-postgres-1  | 2023-08-08 01:01:47.142 UTC [37] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
my-app-postgres-1  | 2023-08-08 01:01:47.153 UTC [40] LOG:  database system was shut down at 2023-08-08 01:01:46 UTC
my-app-postgres-1  | 2023-08-08 01:01:47.159 UTC [37] LOG:  database system is ready to accept connections
my-app-postgres-1  |  done
my-app-postgres-1  | server started
my-app-postgres-1  | CREATE DATABASE
my-app-postgres-1  |
my-app-postgres-1  |
my-app-postgres-1  | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
my-app-postgres-1  |
my-app-postgres-1  | 2023-08-08 01:01:47.356 UTC [37] LOG:  received fast shutdown request
my-app-postgres-1  | waiting for server to shut down....2023-08-08 01:01:47.360 UTC [37] LOG:  aborting any active transactions
my-app-postgres-1  | 2023-08-08 01:01:47.364 UTC [37] LOG:  background worker "logical replication launcher" (PID 43) exited with exit code 1
my-app-postgres-1  | 2023-08-08 01:01:47.364 UTC [38] LOG:  shutting down
my-app-postgres-1  | 2023-08-08 01:01:47.367 UTC [38] LOG:  checkpoint starting: shutdown immediate
my-app-postgres-1  | 2023-08-08 01:01:47.483 UTC [38] LOG:  checkpoint complete: wrote 918 buffers (5.6%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.082 s, sync=0.021 s, total=0.119 s; sync files=250, longest=0.004 s, average=0.001 s; distance=4222 kB, estimate=4222 kB
my-app-postgres-1  | 2023-08-08 01:01:47.489 UTC [37] LOG:  database system is shut down
my-app-postgres-1  |  done
my-app-postgres-1  | server stopped
my-app-postgres-1  |
my-app-postgres-1  | PostgreSQL init process complete; ready for start up.
my-app-postgres-1  |
my-app-postgres-1  | 2023-08-08 01:01:47.584 UTC [1] LOG:  starting PostgreSQL 15.3 on x86_64-pc-linux-musl, compiled by gcc (Alpine 12.2.1_git20220924-r10) 12.2.1 20220924, 64-bit
my-app-postgres-1  | 2023-08-08 01:01:47.585 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
my-app-postgres-1  | 2023-08-08 01:01:47.585 UTC [1] LOG:  listening on IPv6 address "::", port 5432
my-app-postgres-1  | 2023-08-08 01:01:47.591 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
my-app-postgres-1  | 2023-08-08 01:01:47.599 UTC [53] LOG:  database system was shut down at 2023-08-08 01:01:47 UTC
my-app-postgres-1  | 2023-08-08 01:01:47.606 UTC [1] LOG:  database system is ready to accept connections
my-app-postgres-1  | 2023-08-08 01:01:56.490 UTC [58] FATAL:  password authentication failed for user "root"
my-app-postgres-1  | 2023-08-08 01:01:56.490 UTC [58] DETAIL:  Connection matched pg_hba.conf line 100: "host all all all scram-sha-256"
my-app-adminer-1   | [Tue Aug  8 01:01:43 2023] PHP 7.4.27 Development Server (http://[::]:8080) started
my-app-api-1       | wait-for-it.sh: waiting 15 seconds for postgres:5432
my-app-api-1       | wait-for-it.sh: postgres:5432 is available after 4 seconds
my-app-api-1       |
my-app-api-1       | ><EMAIL_ADDRESS>migration:run
my-app-api-1       | > npm run typeorm -- --dataSource=src/database/data-source.ts migration:run
my-app-api-1       |
my-app-api-1       |
my-app-api-1       | ><EMAIL_ADDRESS>typeorm
my-app-api-1       | > env-cmd ts-node -r tsconfig-paths/register ./node_modules/typeorm/cli.js --dataSource=src/database/data-source.ts migration:run
my-app-api-1       |
my-app-api-1       | Error during migration run:
my-app-api-1       | error: password authentication failed for user "root"
my-app-api-1       |     at Parser.parseErrorMessage (/usr/src/app/node_modules/pg-protocol/src/parser.ts:369:69)
my-app-api-1       |     at Parser.handlePacket (/usr/src/app/node_modules/pg-protocol/src/parser.ts:188:21)
my-app-api-1       |     at Parser.parse (/usr/src/app/node_modules/pg-protocol/src/parser.ts:103:30)
my-app-api-1       |     at Socket.<anonymous> (/usr/src/app/node_modules/pg-protocol/src/index.ts:7:48)
my-app-api-1       |     at Socket.emit (node:events:514:28)
my-app-api-1       |     at Socket.emit (node:domain:489:12)
my-app-api-1       |     at addChunk (node:internal/streams/readable:324:12)
my-app-api-1       |     at readableAddChunk (node:internal/streams/readable:297:9)
my-app-api-1       |     at Socket.Readable.push (node:internal/streams/readable:234:10)
my-app-api-1       |     at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
my-app-api-1       |   length: 100,
my-app-api-1       |   severity: 'FATAL',
my-app-api-1       |   code: '28P01',
my-app-api-1       |   detail: undefined,
my-app-api-1       |   hint: undefined,
my-app-api-1       |   position: undefined,
my-app-api-1       |   internalPosition: undefined,
my-app-api-1       |   internalQuery: undefined,
my-app-api-1       |   where: undefined,
my-app-api-1       |   schema: undefined,
my-app-api-1       |   table: undefined,
my-app-api-1       |   column: undefined,
my-app-api-1       |   dataType: undefined,
my-app-api-1       |   constraint: undefined,
my-app-api-1       |   file: 'auth.c',
my-app-api-1       |   line: '326',
my-app-api-1       |   routine: 'auth_failed'
my-app-api-1       | }
my-app-maildev-1   | MailDev using directory /tmp/maildev-1
my-app-maildev-1   | MailDev webapp running at http://<IP_ADDRESS>:1080
my-app-maildev-1   | MailDev SMTP Server running at <IP_ADDRESS>:1025
root@iZ2ze8qk0bio1k49bk5lrrZ:~/project/my-app#

Above is the log from my rebuild, still reporting the error.

@hankaibo I can't reproduce your problem. Please try install nest-boilerplate from scratch ant let me know if this help you

Have you changed your password?

@hankaibo sorry, nestjs-boilerplate really had problem with .env file on docker compose up.
Please make changes to your project as in these files and try again.

You are my God, thanks.


After doing the "enable" action in compound DAI card, the withdraw/supply screens haven't recognized the change

To use Compound tokens you must "approve" the compound contract to move the underlying asset.
E.g. to use compound dai, you must send a transaction to the dai contract to allow you to move the funds.
The tokenscripts I wrote for compound require the user do this first and if they have done so, the screen will refresh and allow them to deposit/withdraw from compound.
The app does not do this refresh however, meaning users can never use compound tokens even if they have approved the contract.
Example: https://etherscan.io/address/0x6ef06a30B895bA2f7407028D99ad7C2dD4B330a7#

Seems to be fixed in the current master branch

Solved in #912


Re-Exported Type Should Come From Closest Module

Let's consider something like redux-saga/effect. This may be used as an "import", but the package would look like
export * from 'saga-core/types/effect';

From dets perspective the original type, however, comes from saga-core, i.e., if saga-core is not part of the imports we'll just include it directly.
This is not desired. Instead, we'll should actually know that it was also exported from an imported module and use it from there - this way not including the typings, but rather just referencing the import.

Available in latest version (0.5).