Update taggit.rst docs.

Hi! I ran into this issue and figured out a fix. Maybe this is not the correct change to make or document -- if it isn't, please let me know how to address this in my app + I'd be happy to update the PR to address the underlying code instead if that's the issue.

For taggit the create option is broken, and it is unnecessary.
One of the drop down options includes the new tag. So if you've typed funny and funny does not exist you'll have:
funny
Create 'funny'

Picking funny works as intended -- it creates a new tag properly.
Picking Create 'funny' creates two tags and labels them wonkily.
This change removes the create option entirely from the docs so this works out of the box for end-users.

Seems like there was an issue in 2020 but it manifested itself differently: https://github.com/yourlabs/django-autocomplete-light/issues/1133
In my case, the creation event creates two tags, and the one that ends up being displayed contains a tag ID in the name. I haven't made any changes to my implementation and have done what's in the docs verbatim.
There's also comment in that issue that states the create option probably isn't necessary for taggit.

Great! Thanks a heap!

Please try 3.10.0-rc3 and let me know if it works for you


Port already in use, because proxy keeps binding to the wrong container IP

the device had a service that was trying to bind to port 80 on the host. the engine would fail container creation with <IP_ADDRESS>:80 already allocated.
a balena-proxy process was running tied to a container IP that was used by a different service than the one we would expect
removing the libnetwork state, ip link remove supervisor0, removing the containers and restarting the engine fixed it.

https://github.com/moby/libnetwork/issues/1790 sounds related

I did a normal balena push on the dummy-app repo (react/express), It did work on Josh's end to open in public URL, but not on my end, with the exact code. Then I changed the Docker compose file to map FE from 3000:3000 to 80:3000. It still showed the following error

@inwenc The comment above doesn't really show the connection between your error and the issue described here. What's Josh's app? What's your app? Link to code for both? Differences between both? In this Flowdock thread I commented some steps for documenting your observation of this issue here. I also included some device logs with the command I used. Could you provide more info please


Own Homebrew core formula

Which version of kubefirst are you using?
ALL
Which cloud provider?
None specific
Which installation type?
None specific
Which distributed Git provider?
None specific
What is the issue?
By default, users will try to install kubefirst with Homebrew using the brew install kubefirst which will install the Homebrew formula in homebrew-core, instead of the one we manage. Only people reading the documentation first will use the right formula.
The one in homebrew-core is causing version issue as they don't manage the additional v we added, and need in front of the version number, causing multiples issues (one example here).
We need to either:

Take ownership of the homebrew-core one, and remove the one we host.
Fix the homebrew-core one, and remove the one we host (or keep both).
Any other creative solution I didn't think about :)

Homebrew maintainers are pretty fast to review PR, so the initial concerns may not be an issue anymore.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Fixed by @Claywd !


[Bug]: Code View with syntax highlighting throws React unique key warning

Browser
Chrome
Package version
3.0.5
React version
18.2.0
Description
When using code view with a syntax highlighting function created by createHighlight React throws a warning that not all children in a list are given a unique key prop. This can be particularly annoying if you're running unit tests against code view which are set to fail on warnings.
This seems to be coming from React.Fragments being rendered in the tokens.map(...) loop here without a key explicitly being set to them. Explicitly setting the key like is done a couple lines lower here should suppress the issue.
PR aiming to fix this: #18

Source code
No response
Reproduction
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues on this and main repositories for duplicate problems

Thank you for reporting and for your bias for action on opening the respective pull request. We added a small comment to the PR but we'll gladly merge the changes.

Fixed with https://github.com/cloudscape-design/code-view/pull/18


Print detailed architecture definition and check shapes during network construction

for two reasons:

Save the training output in log files for each experiment and the above information helps users find out the network architectures in question retrospectively.
Fail early if the shapes are inconsistent. The errors in a network definition can be found out before the network starts to run. Otherwise, the program just crashes and emits a huge core dump file which is much less useful for debugging than fine-grained log details.

./dmlc-core/include/dmlc/logging.h:208: [19:50:25] ./mshadow/mshadow/./././dot_engine-inl.h:285: Check failed: dst.size(0) == sleft[0] && dst.size(1) == sright[1] && sleft[1] == sright[0] dot-gemm: matrix shape mismatch
[19:50:25] ./dmlc-core/include/dmlc/logging.h:208: [19:50:25] src/engine/./threaded_engine.h:295: [19:50:25] ./mshadow/mshadow/./././dot_engine-inl.h:285: Check failed: dst.size(0) == sleft[0] && dst.size(1) == sright[1] && sleft[1] == sright[0] dot-gemm: matrix shape mismatch
terminate called after throwing an instance of 'dmlc::Error'
  what():  [19:50:25] src/engine/./threaded_engine.h:295: [19:50:25] ./mshadow/mshadow/./././dot_engine-inl.h:285: Check failed: dst.size(0) == sleft[0] && dst.size(1) == sright[1] && sleft[1] == sright[0] dot-gemm: matrix shape mismatch

Which op generated this? Ideally this should be caught in infershape before forward/backward starts.

All errors are posted. There is no clue to find out the answer. That's why all relevant information should always be printed out.

when things fail in the engine, you can try using NAIVE_ENGINE, and backtrace will give you the call hierarchy.

I had a similar problem when using mx.symbol.FullyConnected(). Changing mx.nd.array([1,2,3,4,5]) to mx.nd.array([[1,2,3,4,5]]) (note the extra level of nesting), seems to have solved it.

Using Flatten in the last layers avoids the error.
  pool = mx.sym.Pooling(data = data, kernel = (8, 8), stride = (1, 1), pool_type = 'avg', name = 'global_pool')
  flatten = mx.sym.Flatten(data = pool, name = 'flatten')
  dropout = mx.symbol.Dropout(data = flatten, p = 0.2, name = 'dropout')
  fc1 = mx.symbol.FullyConnected(data = dropout, num_hidden = num_classes, name = 'fc1')
  softmax = mx.symbol.SoftmaxOutput(data = fc1, name = 'softmax')


Citing Oxigraph

Hi!,
I am wondering how can we cite oxigraph in our academic publication. I think that linking Oxigraph to Zenodo (like RDFlib recently did) and have a DOI would be nice.
Julián

That's a great point! I have made the work for Zenodo to generate DOI for each version. I have also wrote #241 to add a citation file.

Thanks! :)

Done and working: https://doi.org/10.5281/zenodo.7408022


arm: Better debugging for json errors

As seen in #210, it happens.
We should append the body (to be decoded as json) as %q to the errors from the json package. Otherwise they'll be impossible to debug with just a "decoding failed" message.

@ahmetalpbalkan Seems reasonable.

@ahmetalpbalkan Noted and will add in next release.

We don't close issues without fixing them.

@ahmetalpbalkan The latest release includes the JSON in error messages when parsing (or other) errors occur. Please take a look.

Cool. (Fixed in #221)

Changes merged from PR #221


Fix constructor arguments in ParallelReactionModel

One of the more rarely used capabilities of our codebase is running multi-GPU inference during single-step evaluation. Testing this part of code requires having a GPU, and so ParallelReactionModel was not covered by unit tests, and it broke at some point during refactoring of the model classes. This PR adds simple tests for it and fixes the issue.

By the way, with this PR the overall test coverage went from 91% to 92% 😄


replace _ char with . in application tags key

Pull Request Test Coverage Report for Build 908

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 68.947%

Files with Coverage Reduction
New Missed Lines
%

dist/plugins/support/ApplicationSupport.js
1
91.67%

Totals

Change from base Build 902:
0.0%

Covered Lines:
2654

Relevant Lines:
3597

💛  - Coveralls


Play by radio frequency

I have my favorite radio channel frequency but idk what its id.
Play by radio frequency will be useful feature

Dear @WinXPDev,
If you want to listen to a radio by frequency, I think your device is a classic radio.
This command can't do that magic. It uses the internet, not the classic radio dial, so you MUST know at least the streaming url of your favourite radio, then choose an id to add it to the available radios...
radio add -n "My favourite radio" -u http://your-favourite-radio-url my_radio_id
Once you do that, you can play it...
radio play my_radio_id


Change the font of topview month name and year

How to change the font of topview month name and year?
How to change the week title font?

Currently not have property of JKCalendar to change font, You can change font on JKCalendar.xib.


Fix checkbox design

Closes #215.
The checkbox widget now looks like so.

Let me know if that needs tweaking.
cc: @ellisonbg

Thanks @captainsafia !


Oidc4vci : external issuer does not work

as the credential manifest is optional, in that case the wallet should display the defaut card


artsdata-planet-ville-de-laval: Add event location placeholder

User Story
As an admin of the Signé Laval website, I review and publish events from the city of Laval coming from Données Quebec data dump. The events in the Données Quebec data dump are often missing a place.  This prevents the event from getting loaded into Footlight CMS. I would like the events to load into Footlight CMS so I can fix the location and other info during my review so I can then publish the event.
Proposed solution
In the data pipeline that loads the event data dump from Données Quebec, the events missing a location should have the following location Placeholder added.
https://cms.footlight.io/dashboard/63457978637093005071a053/places/663b8d6f0796c300645e2ab9
https://api.footlight.io/places/663b8d6f0796c300645e2ab9
The challenge is to allow the event to pass through Artsdata and into CMS, but WITOUT minting the place with a K-number.

[x] Gregory to modify sparql to allow places to not have Artsdata K-number like this event
[ ] Check if the aggregator can load the event with a location sameAs URI like https://api.footlight.io/places/663b8d6f0796c300645e2ab9.  The place already exists in CMS with a CMS URI instead of an Artsdata URI, so the aggregator should not call back Artsdata to try and create the place.

OTHERWISE a new sparql to load place data using an external URI can be created (and used for all loads from a source without needing to create place K-numbers)
Test Case
Pick an event in the Données Quebec event data dump that is missing a place. Load the data from Données Quebec, and check in Artsdata if the Placeholder was added. Then load into Footlight CMS in staging and check that the event loaded.

@saumier let's update the SPARQL query for this source and add the footlight place URI to the location (https://api.footlight.io/places/663b8d6f0796c300645e2ab9).
Example:
{
name": {
"fr": "Example Event"
},
location": {
"Place": "https://api.footlight.io/places/663b8d6f0796c300645e2ab9"
},
}
So that, the aggregator can identify the location in the response as location in the footlights CMS.

Waiting for Ville de Laval to update their data feed to include places for all events. A couple of meetings with Ville de Laval happened and they are redoing their entire system and website.


dashd crashes with signal 10 (Bus error)

Masternode running v<IP_ADDRESS> crashes silently after several hours on FreeBSD. The issue is reproducible.

make sure you have enough ram(512mb)/swap(1gb+)
check syslog for any dashd related messages

Logs say it exited on signal 10.
I'll try to give it more RAM.

Stable so far, appears that it was memory related.
Thanks for your hint.

The problem still persists. I've got a significant amount of free RAM and swap. Occasionally it still exits on signal 11.

Are you have a stable Internet connection? I had a same problem when I used VPN for ext IP, a change to a stable broadband connection solve this.
You can also see a system logs and dash db.log and debug.log for other relevant messages.
As next step you can run dash daemon with debugger and found a function that cause crashes.

I'm using VPN to get a fixed external IP. Dashd should not crash under intermittent network condition.
Logs say dashd exited on signal 10 (Bus error), as before.
I have a core dump if anyone wants to take a look.

@corv89
try get gdb core dump => https://poiuty.com/index.php?title=Linux_gdb_core_dump

I've got a core dump, the file is ~500MB.
gdb gives me this:
Core was generated by `dashd'.
Program terminated with signal 10, Bus error.
#0  0x0000000804236d52 in ?? ()
(gdb) bt
#0  0x0000000804236d52 in ?? ()
#1  0x000000082094ff60 in ?? ()
#2  0x0000000804527bb9 in ?? ()
#3  0x00007fffddfdc000 in ?? ()
#4  0x0000000804236ba9 in ?? ()
#5  0x0000000804c0b000 in ?? ()
#6  0x0000000000000280 in ?? ()
#7  0x000000080453b0e0 in ?? ()
#8  0x000000080453b0d8 in ?? ()
#9  0x0000000804893c48 in ?? ()
#10 0x00000008048938c0 in ?? ()
#11 0x0000000804893c58 in ?? ()
#12 0x0000000000000019 in ?? ()
#13 0x00000008174060c8 in ?? ()
#14 0x00000008174060c8 in ?? ()
#15 0x00000008174060c8 in ?? ()
#16 0x0000000000000000 in ?? ()

This is running on FreeBSD

Are masternodes supposed to be a Linux monoculture or is anyone willing to take a look at the core dump? Let me know where I can upload it.

I am not a programmer, but the next step is to found a function in source code where the daemon crashes. Google, gdb and sources can help you to do it.

If you look above you will notice that the function names are not being shown (except for one)
If there is a way to get more debug information, dash's documentation does not mention it.

@corv89 recompile dashd with debug flags. compiler flags are -g3 for debug symbols and -O0 for non-code-optimizations, in addition you can set -DDEBUG to enable special code. it's a start.
for dash, it should be something like this, you could also enable tests:
./autogen.sh
./configure --without-gui --with-utils --with-libs --with-daemon --enable-debug --enable-tests
make -j $(nproc)

after that, directly attach the daemon to gdb, like gdb ./src/dashd and r -debug -debugnet -printtodebugger -logtimestamps
and now back to work.

@5chdn thanks for your reply, that's what i needed to know. I'll recompile with debug symbols.
Tests haven't compiled since drkcoin times, I reported it way back and never got a reply. I'll try again just for completeness sake.

I ran:
./configure --without-gui --with-utils --with-libs --with-daemon --enable-debug --enable-tests CPPFLAGS="-I/usr/local/include/db48" LDFLAGS="-L/usr/local/lib/db48" CFLAGS="-g3 -O0 -DDEBUG"
gmake -j 4

When I start dashd via gdb ./src/dashd and then r -debug -debug=net printtodebugger -logtimestamps it simply states program exited normally and proceeds to write a fresh core dump. It continues to run normally when invoked directly.

add -daemon ?
i don't know your system setup, so I can only guess.

I tried that without success. daemon=1 is also in dash.conf
What does work however is gdb attach pid, unfortunately symbols are still missing.

Please run without any daemon=1 flag - for gdb to stay attached you need to run dashd undaemonized

Thanks

dashd was running fine for two months whilst gdb was attached.
After 60 days or so I rebooted the system and now without gdb attached dashd has crashed twice within the last few days.
This is really bugging me.

I hear you, i have this problem by myself: some nodes are crashing sporadically, but i was not able to get a coredump yet... frustrating.

Are you saying nodes are also crashing on Linux sporadically or did you replicate my issue on FreeBSD?

Linux - there is a ~1% probability that given node dies during 24h a timeframe. I assume a segfault somewhere in the code...

At least it’s good to know that I’m not the only one getting this.
I will try running it with gdb attached again and see if I catch anything.

On 24 Jan 2016, at 22:44, Holger Schinzel<EMAIL_ADDRESS>wrote:
Linux - there is a ~1% probability that given node dies during 24h a timeframe. I assume a segfault somewhere in the code...
—
Reply to this email directly or view it on GitHub https://github.com/dashpay/dash/issues/624#issuecomment-174310776.

Instead of trying to attach a debugger to the process I suggest you do the following:
Open a shell then type:
ulimit -c unlimited
dashd (Make sure this is a debug enabled build)
Now when (or if) the process crashes there should be a file named core or possibly core. in the directory from which you launched dashd.
Open it with this command (using the appropriate path to dashd):
gdb /usr/local/bin/dashd core
Then in gdb type:
bt
This should hopefully give you a useable stack trace containing function names which you can post here.

Thanks for the tip.
The last core I inspected with gdb was missing the symbol table as per my comment from 13 Nov 2015.
I don't have the masternode anymore so I'm unsure if I can replicate the issue. I will let dashd run and see if I get another core.

I'm not sure if it will work but if you still have the core file you could try opening it in gdb with the debug build of the dashd executable (making sure that the debug build was built from the exact same git commit as the build that produced the core).

Unfortunately I don’t and dashd hasn’t crashed yet.

On 30 Jul 2016, at 13:49, Tim Flynn<EMAIL_ADDRESS>wrote:
I'm not sure if it will work but if you still have the core file you could try opening it in gdb with the debug build of the dashd executable (making sure that the debug build was built from the exact same git commit as the build that produced the core).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dashpay/dash/issues/624#issuecomment-236348477, or mute the thread https://github.com/notifications/unsubscribe-auth/AG3X36RVfwiVnG5y-5hIWZTJAMcRrg6tks5qavPvgaJpZM4GDsfF.

Can you tell me exactly what version of FreeBSD you were running ?  I'd like to do a build on FreeBSD and see if I can match the address layout of your core dump and hence figure out what functions those addresses correspond to.
I tried to do a build on FreeBSD 10.2 but the configure script has a dependency on pkg-config and it seems that no longer exists in recent versions of FreeBSD.

It's 10.2. Thank you for your effort.  I always needed to pass the path to db48 to configure. Possibly installed it from ports, not using pkg. Instead of pkg-config I installed pkgconf.
I can post the list of dependencies I installed.

On 31 Jul 2016, at 10:20, Tim Flynn<EMAIL_ADDRESS>wrote:
Can you tell me exactly what version of FreeBSD you were running ? I'd like to do a build on FreeBSD and see if I can match the address layout of your core dump and hence figure out what functions those addresses correspond to.
I tried to do a build on FreeBSD 10.2 but the configure script has a dependency on pkg-config and it seems that no longer exists in recent versions of FreeBSD.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@tgflynn That worked for me (on fresh new instance) when I tried to compile on FreeBSD not so long ago, should work for 10.2 too afaik:
# FreeBSD 10.1 install instructions

# > uname -a
# FreeBSD freebsd-512mb-ams3-01 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014     root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

# install/remove packages
sudo pkg install wget
# temporary remove gcc if you installed it before, reinstall after build is complete if you need it
# sudo pkg remove gcc

# update ports
sudo portsnap fetch
sudo portsnap update

# install all original Bitcoin Core dependencies
# including gui:
cd /usr/ports/net-p2p/bitcoin/
# daemon only:
# cd /usr/ports/net-p2p/bitcoin-daemon/
sudo make
# optional:
# (CTRL-C when it starts building Bitcoin Core itself if you don't need it)
# sudo make clean

# grab source and compile
mkdir ~/src
cd ~/src/
wget https://github.com/dashpay/dash/archive/v<IP_ADDRESS>.tar.gz
tar zxvf v<IP_ADDRESS>.tar.gz
cd v<IP_ADDRESS>/
setenv CXXFLAGS "-I/usr/local/include -I/usr/local/include/db48"
setenv LDFLAGS "-L/usr/local/lib -L/usr/local/lib/db48"

./autogen.sh && ./configure
gmake

# > ls -la src/dashd
# -rwxr-xr-x  1 freebsd  freebsd  19465233 Jun 26 22:00 src/dashd
# > ls -la src/qt/dash-qt
# -rwxr-xr-x  1 freebsd  freebsd  24306649 Jun 26 22:08 src/qt/dash-qt

@UdjinM6
Thanks, I had already found your instructions and they did basically work for me (though for some reason it seems I needed to set CPPFLAGS in addition to CXXFLAGS).  It seems the information I had seen online that pkg-config no longer exists in FreeBSD was inaccurate.
Unfortunately I cannot reproduce the addresses in the above stack trace.  For me the code loads at much lower addresses.  As far as I can tell FreeBSD does not use ASLR so either there is some factor controlling the load address that I'm not aware of or the core dump has a corrupted stack.

I also would like to mention that original question was about <IP_ADDRESS> and current stable is <IP_ADDRESS> - we fixed few nasty bugs so give it a try and see if you can reproduce the crash now.

I've got another core dump now from <IP_ADDRESS>
Core was generated by dashd'.
Program terminated with signal 10, Bus error.
#0  0x000000080427ad52 in ?? ()`
Going to update to <IP_ADDRESS>

If it happens again with <IP_ADDRESS> I'd like to get the core file from you, if possible, for analysis.
But it's probably not worth doing for a backlevel version.

Got trouble linking the latest version. boost is up to date.
Any ideas?
  CXXLD    dashd
libbitcoin_server.a(libbitcoin_server_a-init.o): In function `boost::filesystem::path::path<boost::filesystem::directory_entry>(boost::filesystem::directory_entry const&, boost::enable_if<boost::filesystem::path_traits::is_pathable<boost::decay<boost::filesystem::directory_entry>::type>, void>::type*)':
init.cpp:(.text._ZN5boost10filesystem4pathC2INS0_15directory_entryEEERKT_PNS_9enable_ifINS0_11path_traits11is_pathableINS_5decayIS4_E4typeEEEvE4typeE[_ZN5boost10filesystem4pathC5INS0_15directory_entryEEERKT_PNS_9enable_ifINS0_11path_traits11is_pathableINS_5decayIS4_E4typeEEEvE4typeE]+0x48): undefined reference to `boost::filesystem::path_traits::dispatch(boost::filesystem::directory_entry const&, std::string&, std::codecvt<wchar_t, char, __mbstate_t> const&)'
libbitcoin_util.a(libbitcoin_util_a-util.o): In function `SetupEnvironment()':
util.cpp:(.text+0x30f2): undefined reference to `boost::filesystem::path::imbue(std::locale const&)'
util.cpp:(.text+0x3105): undefined reference to `boost::filesystem::path::imbue(std::locale const&)'
libbitcoin_util.a(libbitcoin_util_a-util.o): In function `boost::program_options::detail::basic_config_file_iterator<char>::basic_config_file_iterator(std::istream&, std::set<std::string, std::less<std::string>, std::allocator<std::string> > const&, bool)':
util.cpp:(.text._ZN5boost15program_options6detail26basic_config_file_iteratorIcEC2ERSiRKSt3setISsSt4lessISsESaISsEEb[_ZN5boost15program_options6detail26basic_config_file_iteratorIcEC5ERSiRKSt3setISsSt4lessISsESaISsEEb]+0x3d): undefined reference to `boost::program_options::detail::common_config_file_iterator::common_config_file_iterator(std::set<std::string, std::less<std::string>, std::allocator<std::string> > const&, bool)'
libbitcoin_util.a(libbitcoin_util_a-util.o): In function `boost::program_options::detail::basic_config_file_iterator<char>::getline(std::string&)':
util.cpp:(.text._ZN5boost15program_options6detail26basic_config_file_iteratorIcE7getlineERSs[_ZN5boost15program_options6detail26basic_config_file_iteratorIcE7getlineERSs]+0x7c): undefined reference to `boost::program_options::to_internal(std::string const&)'
libbitcoin_wallet.a(libbitcoin_wallet_a-db.o): In function `CDBEnv::Verify(std::string, bool (*)(CDBEnv&, std::string))':
db.cpp:(.text+0xc58): undefined reference to `Db::verify(char const*, char const*, std::ostream*, unsigned int)'
libbitcoin_wallet.a(libbitcoin_wallet_a-db.o): In function `CDBEnv::Salvage(std::string, bool, std::vector<std::pair<std::vector<unsigned char, std::allocator<unsigned char> >, std::vector<unsigned char, std::allocator<unsigned char> > >, std::allocator<std::pair<std::vector<unsigned char, std::allocator<unsigned char> >, std::vector<unsigned char, std::allocator<unsigned char> > > > >&)':
db.cpp:(.text+0xeb4): undefined reference to `Db::verify(char const*, char const*, std::ostream*, unsigned int)'
collect2: error: ld returned 1 exit status
gmake[2]: *** [Makefile:2619: dashd] Error 1
gmake[2]: Leaving directory '/home/corv/dash-<IP_ADDRESS>/src'
gmake[1]: *** [Makefile:6780: all-recursive] Error 1
gmake[1]: Leaving directory '/home/corv/dash-<IP_ADDRESS>/src'
gmake: *** [Makefile:568: all-recursive] Error 1

It looks like you probably have an incompatible version of Berkeley DB (db_cxx.h and libdb_cxx.a/.so).
You should be using version 4.8 - see doc/build-unix.md.
If this node doesn't need a wallet you could also configure with --disable-wallet since then you wouldn't need db_cxx.

BTW: If you do get another crash and send us a core dump make sure that if there are any coins in the wallet that you move them before uploading the core.  If the wallet is encrypted and locked at the time of the crash they would probably be safe but I wouldn't take the chance.

Using db4.8. --disable-wallet sounds like a good idea but it's not getting better.
What options did you pass to ./configure?

If you're building from git you should do this to reconfigure:
git clean -f -x -d # Note this will delete everything in your working directory that's not checked in
./autogen.sh
./configure --disable-wallet
make
If you're building from a tarball you should just delete the old working directory and re-extract before reconfiguring.
I haven't personally tried this but according to the docs there should be no dependency on bdb when configured with this option.
I'm not sure why you're having trouble with bdb.  You must have had it working before with the older release and I doubt anything major changed in the build process.

When I disable the wallet there are pages of errors.
I've compiled from a clean state, disabled tests, gui, wallet.
Not sure what else to try.

On 14 Aug 2016, at 17:51, Tim Flynn<EMAIL_ADDRESS>wrote:
If you're building from git you should do this to reconfigure:
git clean -f -x -d # Note this will delete everything in your working directory that's not checked in
./autogen.sh
./configure --disable-wallet
make
If you're building from a tarball you should just delete the old working directory and re-extract before reconfiguring.
I haven't personally tried this but according to the docs there should be no dependency on bdb when configured with this option.
I'm not sure why you're having trouble with bdb. You must have had it working before with the older release and I doubt anything major changed in the build process.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@corv89 have you tried install instructions I posted above? https://github.com/dashpay/dash/issues/624#issuecomment-236426865

Those result in the previous error messages.

On 14 Aug 2016, at 18:49, UdjinM6<EMAIL_ADDRESS>wrote:
@corv89 have you tried install instructions I posted above? #624 (comment)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I have a build script that works.  I just need to figure out a way to post it since I have it in a VM.

That would be great, thanks

On 14 Aug 2016, at 18:51, Tim Flynn<EMAIL_ADDRESS>wrote:
I have a build script that works. I just need to figure out a way to post it since I have it in a VM.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Here's the script:
https://gist.github.com/tgflynn/f6bcfcfdd4d555db945b4112c812642d

Thanks, unfortunately same error as before.

One huge issue with linking I can remember of was gcc itself.
# temporary remove gcc if you installed it before, reinstall after build is complete if you need it
# sudo pkg remove gcc

Have you tried removing it and rebuilding from scratch?

If Udjin's suggestion doesn't work (hopefully it will, I do not have gcc installed) could you do the following:
Change the last line of the script to gmake V=1 and rerun it capturing all output to a file.  Then upload the file somewhere (maybe as a gist).
For example:
(If you don't have bash installed, install it with ports.)
bash
../build2.csh 2>&1 | tee ../build-out.txt
In any case make sure you redirect to a file not in the dash directory or git clean will delete it !

@UdjinM6 suggestion did the trick.
I'll upload the core once I have one.

Good.
Note that if you get a core it will be large (ie. several 100 MB) so you should probably compress it.  You may not be able to upload such a large file here but if not I'm sure we can find some way to handle it.

Yes, I’ll find somewhere to put it. Could take several days to catch the crash.
Thanks for the help

On 14 Aug 2016, at 21:52, Tim Flynn<EMAIL_ADDRESS>wrote:
Good.
Note that if you get a core it will be large (ie. several 100 MB) so you should probably compress it. You may not be able to upload such a large file here but if not I'm sure we can find some way to handle it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/dashpay/dash/issues/624#issuecomment-239677664, or mute the thread https://github.com/notifications/unsubscribe-auth/AG3X3-zL1PUArSvWmYW7gCFFkUgwSMi_ks5qfyuhgaJpZM4GDsfF.

https://transfer.sh/ is a good place to temporary store huge blobs

Obsolete


Other FQDN dependencies for clients accessing ADX UI

This there a page that documents all of the FQDN dependencies for clients accessing ADX from a private network including those that are not exposed as private endpoints?
For example when accessing the ADX UI in addition to the private endpoint FQDN I have also noticed the following FQDN being accessed from my browser which means that I would need to allow my clients to have outbound access to them via the internet as they are not accessible via private endpoint. Are the full list of FQDN dependencies documented somewhere?

dc.services.visualstudio.com
dataexplorer.azure.com
web.vortex.data.microsoft.com
graph.microsoft.com
login.microsoftonline.com
amcdn.msftauth.net

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

ID: ec266648-f748-a305-aaf3-6c0bcc565d62
Version Independent ID: ed07efae-8508-d32b-dd02-b7fd25943111
Content: Create a private endpoint for Azure Data Explorer
Content Source: data-explorer/security-network-private-endpoint-create.md
Service: data-explorer
GitHub Login: @shsagir
Microsoft Alias: shsagir

@shsagir Requesting to validate feedback and update document as appropriate. Thank you.

@pnarsi Thanks for contacting us with feedback about our product documentation. Depending on the complexity, it could take from a few business days to a few weeks to look further into your question, issue, or suggestion. We'll contact you if we need further information, and you'll receive an email message each time we "@mention" you in a comment.
Thanks again for submitting your feedback. Your suggestions help improve our documentation.

to the best of my knowledge: no
reason: those are FQDNs which are needed by the portal to connect to ADX. We documented the FQDNs which are needed to run the service in case of vnet injection

Thanks, @cosh.
At this time, I'm closing the issue. If you have further questions, feel free to @mention myself or @cosh
Thanks for your contributions!

#please-close

Thanks @cosh @YaelSchuster - is there a separate page that documents the FQDN required by the portal to connect ADX? e.g. in the context of an end user accessing the ADX UI from a locked down environment where need to whitelist these required FQDN on a corporate Firewall?


Unify metadata representations

Codecov Report

Merging #16 (3cbf751) into main (68e443f) will increase coverage by 0.51%.
The diff coverage is 95.89%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
+ Coverage   96.50%   97.02%   +0.51%
==========================================
  Files          25       31       +6
  Lines        1317     1478     +161
==========================================
+ Hits         1271     1434     +163
+ Misses         46       44       -2

Impacted Files
Coverage Δ

sscutils/metadata/datascript/bases.py
100.00% <ø> (ø)

sscutils/tests/test_pipereg.py
100.00% <ø> (ø)

sscutils/metadata/bedrock/importer.py
83.60% <83.60%> (ø)

sscutils/metadata/bedrock/namespace_metadata.py
88.09% <88.09%> (ø)

sscutils/metadata/bedrock/artifact_metadata.py
89.58% <89.58%> (ø)

sscutils/helpers.py
94.64% <91.66%> (-5.36%)
:arrow_down:

sscutils/validation_functions.py
96.66% <91.66%> (ø)

sscutils/metadata/datascript/to_bedrock.py
97.39% <97.39%> (ø)

sscutils/metadata/bedrock/feature_types.py
98.38% <98.38%> (ø)

sscutils/metadata/bedrock/atoms.py
98.87% <98.87%> (ø)

... and 16 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 68e443f...3cbf751. Read the comment docs.


Migrate the macOS runners label from macos-m1-12 to macos-m1-stable

Cherry pick of
https://github.com/pytorch/vision/pull/8253

@NicolasHug this should already be a part of 0.18 hence we only need it for 0.17


SetFilters does not refresh the current frame.

When paused, setting a new filter will not refresh the current frame.

filters <<"astats=metadata=1:reset=1"<< "delogo=x=20:y=20:w=200:h=200";
p.setFilters(filters);

There will be two frames, one of which has no filter applied.

Hi, thanks for contributing.
Setting new filter does not trigger updating a frame. It is intentionally made only for play(), pause() if not paused, stepBackward(), stepForward()
It is done like this, because current frame before new filter, is already processed and sent, and it is unable to reapply the filter on the same frame, since filters might be complicated too and expect many frames in sequence.


MSCS ignores .jar

Hi.
Recently the MSCS locked me somehow and i was kinda forced to update it, guess it was okay.
It prompted 'cant find process id' it was old java, I updated, works now.
But now everytime I try to run a bungee, mohist, forge, older spigot server, it ignores the config and starts 1.17 vanilla..
Ex of config:
mscs-enabled=true
mscs-server-jar=mohist-1.12.2.jar
mscs-initial-memory=2G
mscs-maximum-memory=3G
mscs-server-command=$JAVA -XX:+AlwaysPreTouch -XX:+DisableExplicitGC -XX:+UseG1GC -XX:+UnlockExperimentalVMOptions -XX:MaxGCPauseMillis=45 -XX:TargetSurvivorRatio=90 -XX:G1NewSizePercent=35 -XX:G1MaxNewSizePercent=60 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=50 -Xms$INITIAL_MEMORY -Xmx$MAXIMUM_MEMORY -jar $SERVER_LOCATION/$SERVER_JAR $SERVER_ARGS
Defaults manifest is untouched too, path is alright.
I did tried puting the .jar path direct in this config, but no success :/
Peace!

Hi @Eisenbahn.  I'm not sure what the issue is without some more info. Please post a copy of the console.out file from a server that is not working as expected. While you are at it, please post the mscs.properties file for that server as well.


Add message ID saving

It would be a good idea to create a file that keep track of the message IDs sent by the bot (to remember which message to check after a bot/system restart instead of having to initiate it everytime - also to remember the opened tickets)
And if it's added, support the deletion of bad IDs (like deleting the IDs of messages that no longer exist)

Thanks so much for the feature Idea this is quite an interesting one.
Now the bot will have the collectors.json where it will save the tickets and other embeds so it will be ok to reboot the bot.
It was added with the latest commit https://github.com/Arisamiga/Discord-Ticket-Bot/commit/ea8977eb156ac440d93847c0a769e3f77340ac0c
If you experience any issues let me know by opening a issue.


Add hoc dataset

Adds HOC dataset https://github.com/sb895/Hallmarks-of-Cancer.
Introduces a dataset folder that aims to standardise downloading standard datasets that we want to experiment on.

Is there anything else to merge this PR?

Is there anything else to merge this PR?

Yes, implementing the change that Liz suggested. Will do that now :P

 Add dataset for biomedical text classification and create a benchmark that gets results on the dataset


tsc -b incorrectly succeeds when there is a problem introduced by a transitive dependency

Bug Report

project references transitive dependency stale

🕗 Version & Regression Information

This changed between versions 3.6.0-dev.20190621 (good) and 3.6.0-dev.20190622 (bad)
The incorrect behavior was observed in many versions since then, including:

4.4.2
4.4.3
4.5.0-dev.20210928

⏯ Playground Link

Reproducing the problem requires transitive project references, and running tsc -b from the command line, so I don't believe it can be done in the TypeScript playground.
💻 Code
My team observed that tsc -b can incorrectly succeed when a problem is introduced by a transitive dependency.  In fact, tsc -b can give two different results (type check passes or type check fails) for the same codebase.  We created a self-contained reproducible example to demonstrate the problem.  This creates 3 projects using project references, where project A depends on project B and that, in turn, depends on project C.  There is one TypeScript file in project A, none in B and one in C.
Step 1: Create the following 5 files, distributed into directories projectA/, projectB/ and projectC/.
// projectA/A.ts
import C from '../projectC/C';

class A extends C {
  constructor() {
    super( {} );
    this.name.arbitraryFakeMethod();
  }
}

// projectA/tsconfig.json
{
  "references": [
    {
      "path": "../projectB"
    }
  ],
  "compilerOptions": {
    "module": "commonjs",
    "target": "es5",
    "composite": true,
    "outDir": "./dist/",
    "incremental": true,
    "allowJs": true
  },
  "include": [
    "A.ts"
  ]
}

// projectB/tsconfig.json
{
  "references": [
    {
      "path": "../projectC"
    }
  ],
  "compilerOptions": {
    "module": "commonjs",
    "target": "es5",
    "composite": true,
    "allowJs": true,
    "outDir": "./dist/",
    "incremental": true
  }
}

// projectC/C.ts
class C {
  name: string;
  constructor( options ) {
  }
}

export default C;

// projectC/tsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es5",
    "composite": true,
    "allowJs": true,
    "outDir": "./dist/",
    "incremental": true
  },
  "include": [
    "C.ts"
  ]
}

Step 2: clean and build project A
The clean step is not necessary on your first run, but we include it here in case you want to run through the steps again.
cd projectA
tsc -b --clean
tsc -b

In this case, the expected result is the same as the actual result, which is a build failure with this message:
A.ts:7:15 - error TS2339: Property 'arbitraryFakeMethod' does not exist on type 'string'.

7     this.name.arbitraryFakeMethod();
                ~~~~~~~~~~~~~~~~~~~

Found 1 error.

Step 3: Fix the error by updating C.ts.
In C.ts, change name: string; to name: any;
Step 4: build project A
tsc -b

Again, the expected result matches the actual result.  tsc succeeds with no output.
Step 5. Reintroduce the problem in C.ts
In C.ts, change name: any; back to name: string;
Step 6. Build Project A
tsc -b

🙁 Actual behavior
There is no output from tsc because the type check and build passes successfully.  This is incorrect because there is
a type error because string does not have a method arbitraryFakeMethod.  Note that Step 6 is building the same code as in Step 2.  However, in Step 2, the type error is correctly identified, but in Step 6 the type error is missed.
🙂 Expected behavior
Step 6 should produce the following error (as it correctly did in Step 2):
A.ts:7:15 - error TS2339: Property 'arbitraryFakeMethod' does not exist on type 'string'.

7     this.name.arbitraryFakeMethod();
                ~~~~~~~~~~~~~~~~~~~

Found 1 error.

Note that changing project A to depend on C directly (not through B) correctly identifies the problem when running tsc -b in project A, so this bug does require the intermediate transitive dependency.  TypeScript correctly caught this error through Version 3.6.0-dev.20190621 (good), but started missing it in 3.6.0-dev.20190622 (bad).  For completeness, we will mention that we first detected the problem when projectC was *.js code, so it seems to affect both *.ts and *.js dependencies.  This problem was discovered in https://github.com/phetsims/chipper/issues/1067

This does look like a bug, but it also sounds like there may be a misconception that projectC is somehow being included as a project reference of projectA through projectB. It looks like that’s not the case here—I think you are directly including projectC/C.ts as a source of projectA/tsconfig.json.

This does look like a bug, but it also sounds like there may be a misconception that projectC is somehow being included as a project reference of projectA through projectB. It looks like that’s not the case here—I think you are directly including projectC/C.ts as a source of projectA/tsconfig.json.

projectA/tsconfig.json only specifies A.ts in its include section:
  "include": [
    "A.ts"
  ]

And if we remove { "path": "../projectB" } from projectA/tsconfig.json, and run tsc -b in projectA, then we get this error:
A.ts:2:15 - error TS6059: File '/path/test-dependencies/projectC/C.ts' is not under 'rootDir' '/path/test-dependencies/projectA'. 'rootDir' is expected to contain all source files.

2 import C from '../projectC/C';
                ~~~~~~~~~~~~~~~

To me, this suggests that the import statement import C from '../projectC/C'; does not establish a dependency on C.ts (at least from a build standpoint). Also, I should mention I'm new to TypeScript, so my apologies if I'm misunderstanding something simple.

And if we remove { "path": "../projectB" } from projectA/tsconfig.json, and run tsc -b in projectA, then we get this error

This is... surprising to me 😅 Could be a clue as to what’s going on.

There are a lot of commits on 21 Jun 2019. I think this was before we started squashing PRs into a single commit. The PRs that are likely relevant are
#32027 (merged on the 21st) and #32028 (lots of commits on the 21st, but not merged until 24 Sep 2019).
#32027 is a really simple bug fix. In getUpToDateStatusWorker, the loop over a project's references previously skipped over references to projects whose status was ComputingUpstream with the comment "it's a circular reference". The PR now also skips references with status ContainerOnly with the comment "ignore container-only projects".
I'll need to repro this myself, but from the commentary above on previous investigation, it sounds like maybe B or C has status ContainerOnly when it shouldn't.

This issue is quickly becoming detrimental to productivity in the project that I work on. Are there any updates on timeline here?
When making changes in a project C, I have to run type checking as tsc -b --clean && tsc -b in order for files in project A to be type checked. This comes at the cost of upwards of four minutes for each type check to complete.

@RyanCavanaugh @sandersn - Anyway we elevate the priority of the bug, and the timing of the fix. It's really causing major problems for our project. Thank you!

I think this is working as intended. projectA does not directly reference projectC so there is no way to know that change to projectA should affect projectC directly. The references are not transitive and that's what determines what gets built again.
Relevant discussion in #30608

If the reference is not transitive (which was my original understanding), why does import C from '../projectC/C'; inside projectA not issue a rootDir/all-files-must-be-listed error?

Thanks, I was unaware of the design decision in https://github.com/microsoft/TypeScript/issues/30608#issuecomment-484303690

Not having references be transitive was an intentional design decision when we wrote project references

Does this mean we are supposed to list all transitive dependencies explicitly at each level in order to achieve accurate type-checking behavior?  For instance, in the example at the top of the page, projectA would change from:
  "references": [
    {
      "path": "../projectB"
    }
  ]

to
  "references": [
    {
      "path": "../projectB",
      "path": "../projectC"
    }
  ]

In practice, our project has transitive dependencies around 10 layers deep, so each level should list everything?

If the reference is not transitive (which was my original understanding), why does import C from '../projectC/C'; inside projectA not issue a rootDir/all-files-must-be-listed error?

That would certainly help us ensure we didn't forget to list a transitive dependency as a direct dependency.

By having project reference, you are telling that any change to these project can affect the project. So it depends on your granularity of the project and what you want the distiction be

@sheetalkamat I still think https://github.com/microsoft/TypeScript/issues/46153#issuecomment-1119857255 either sounds like a bug or (more likely) I’m still not understanding something.
@samreid the way I have always set up project references is if I import directly from another project (as you imported projectC from projectA in your example), I list projectC as a reference of projectA. On the other hand, if I use exports from projectC only indirectly through projectB, I only list projectB as a reference of projectA.

If the reference is not transitive (which was my original understanding), why does import C from '../projectC/C'; inside projectA not issue a rootDir/all-files-must-be-listed error?

Even if you are not directly importing projectC, projectB's types could depend on projectA(and you might not be using those types) in that case your program still needs projectC
When we added project references we didnt have these clever understanding of when and why files are included baked in. Now we have but i think its too late to formulate error as it could affect configurations in wild to report error if you are directly importing projectC but not referencing it in the config,
Note you dont get error because we use d.ts files transitively that is program will have c.d.ts and not .ts

Ah, right, the rootDir restriction only applies to .ts files, since it’s about the output directory structure. That makes sense.

I think its too late to formulate error as it could affect configurations in wild to report error if you are directly importing projectC but not referencing it in the config

It would be really helpful to have more support from the compiler for making sure project references are set up in a way that will result in correct caching behavior from tsc --build.
We recently migrated to project references, and we're now running into some issues with incorrect caching.
I was not previously aware of the requirement to list transitive dependencies in project references in order for build caching to be correctly invalidated. I assumed that if my project type checked, then the references must be set up correctly.
If it's too disruptive to make it an error to fail to list transitive dependencies in project references, perhaps the build caching system should be updated to invalidate its cache correctly without having references to transitive dependencies explicitly listed.


[BUG]: Multi-dub issues

Program version
4.1.0
Operating System
Windows
Type
CLI
Service
Crunchyroll
Command used
.\aniDL.exe --service crunchy --srz GQWH0M1GG -s GRGGCVQGV -e 1 --dlVideoOnce --dubLang jpn spa-419  fra eng --dlsubs es-419 fr en --defaultSub spa-419
Show ID
GQWH0M1GG
Episode
1
Console Output
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

TypeError: Cannot read properties of undefined (reading 'cr_locale')
    at C:\snapshot\multi-downloader-nx\lib\crunchy.js
    at Array.find (<anonymous>)
    at _loop_6 (C:\snapshot\multi-downloader-nx\lib\crunchy.js)
    at C:\snapshot\multi-downloader-nx\lib\crunchy.js
    at Array.forEach (<anonymous>)
    at C:\snapshot\multi-downloader-nx\lib\crunchy.js
    at step (C:\snapshot\multi-downloader-nx\lib\crunchy.js)
    at Object.next (C:\snapshot\multi-downloader-nx\lib\crunchy.js)
    at step (C:\snapshot\multi-downloader-nx\lib\crunchy.js)
    at Object.next (C:\snapshot\multi-downloader-nx\lib\crunchy.js)

Additional Information
No response

This is caused by a language that episode is in not being available, it is fixed in the upcoming 4.2.0 version


Any workaround for pulling the images?

I have same problem with pipelines-visualization, metadata-api.
ubuntu 18.04
microk8s 1.20/stable

Failed to pull image "registry.jujucharms.com/kubeflow-charmers/pipelines-visualization/oci-image@sha256:50a00b4a663c6f79a50add7481ddf9874edf914cb050175315efe75bcc80050f"
Failed to pull image "registry.jujucharms.com/kubeflow-charmers/metadata-api/oci-image@sha256:7bc212e15546e5f6d2ae5c5c5723c71d1679e50edf40a25731fe8eac79a338c2"

inspection-report-20201216_144119.tar.gz

@jidogoon You can pull the images manually:
microk8s.ctr image pull [IMAGE] --user docker-registry:[PASSWORD]

Where the [IMAGE] and [PASSWORD] can be found by searching the image from JAAS Store, then click the oci-image link to get it.

@jidogoon You can pull the images manually:
microk8s.ctr image pull [IMAGE] --user docker-registry:[PASSWORD]

Where the [IMAGE] and [PASSWORD] can be found by searching the image from JAAS Store, then click the oci-image link to get it.

Thanks @zxsimple for the tips. Unfortunately I couldn't see where to find the password. In my case it's this image registry.jujucharms.com/kubeflow-charmers/kfp-viz/oci-image@sha256:c90a5818043da47448c4230953b265a66877bd143e4bdd991f762cf47e2a16d6 :thinking:

@dhassault I have faced an issue with precisely the same image. Running the URL directly in the browser reveals a 404 error, which indicates that the image is currently not uploaded.

Same problem here!


[IOTDB-1736] Error code is not printed in TSServiceImpl's log

Description
related Jira link: https://issues.apache.org/jira/browse/IOTDB-1736
After modified, the log looks like below:
20:50:06.559 [main] WARN org.apache.iotdb.db.service.TSServiceImpl - Status code: INVALID_HANDLE_STATUS(202), MSG: Exception occurred: "SELECT avg(status) FROM root.ln.wf01.wt01". executeStatement failed.

Coverage decreased (-0.01%) to 67.465% when pulling 84c03a6b686d322ba6bd4cd1e377a98e32203fb8 on ruanwenjun:dev_wenjun_patch1736 into bc3b736834b364ce4fddeed3780de8655ec33e03 on apache:master.

Good to see you here, Wenjun!!! 😆😆😆

@SteveYurongSu Hi, Yurong.


Added tests, then added fixes for those tests

This PR updates format-usd to 0.2.0. No functionality has changed, but there are several fixes.
Basically, while looking over this module for use in my next project, I realized the tests weren't covering negative dollar values, and that the code probably wasn't handling them correctly. I added tests for negatives, and I was right, so I fixed the code to handle negatives.
While I was doing that, I also overhauled the code for verbosity and made it much closer to our front-end standards. At @ascott1's suggestion, I moved some functionality into separate ./lib files (and added tests for those functions). Then I fixed the code so that it could handle strings with multiple periods (by assuming the first period is the intended decimal place).
Additions

Extra code and comments to make the code clearer and more verbose

Changes

Variable names, to make them clearer
Some functionality separate into functions and placed in ./lib/[some-function].js

Testing

Tests added for negative numbers
Tests added for comma-separate-number.js and handle-string-input.js

Review

@contolini @ascott1 and anyone else who's interested!

Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the front end playbook
[x] Passes all existing automated tests
[x] New functions include new tests
[x] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Thanks
Thanks to @ascott1 for reviewing the commits and giving feedback!
Animated GIF
Me when I remove ternary operators:

[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

These parts of the checklist aren't really relevant, but rather than just remove them, I wanted to note that they're not really relevant. :smile: :octopus:

Wow it's comical how illegible this codebase was before this PR. Nice work!

Merged! About to publish!

Big improvements all around.


Enable Return for 'executeScript' method

On executescript sometimes we need receive a return of executed script.
In native webview_flutter the executescript (evaluatejs) method return a Future so we can get the return of script.

See #167


docs(CONTRIBUTING): Actually include rebuilding the package in instructions

…

 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.


Page Opens in Edit Mode

Is it possible that using Controller As syntax is causing the page to load with ALL of the tables rows already in Edit Mode ... I am forced to click cancel on each row to get the page to the state it should be when it loads. If Controller As is the culprit, is there a workaround?

I have created a plunker to show my issue -- http://plnkr.co/edit/1jImj2qULqKfQ3pGBzVb?p=preview. I have to click the cancel 'X' of each row before the table is like I need it to be.

Did you find a solution?  I've got the same issue.

You need to name your editable form the same as your form name editable-form="rowform".
See this updated plunker

@eugef this issue has been answered, please close.


Enable offloading for numba.njit in dpctl.deveice_context

Relates to https://github.com/IntelPython/dpctl/pull/678.
Tasks:

[x] docs
[ ] changelog
[x] dppy.offload_to_sycl_device reuses dpctl.device_context
[ ] replace dppy.offload_to_sycl_device with dpctl.device_context in all tests
[ ] dpctl >=0.12 or >=0.11.2

Documentation update is not necessary. Because we have example with dpctl.device_context on the main page.

Ready to be reviewed.
Waiting to be merged after https://github.com/IntelPython/dpctl/pull/678.

Merging based on public CI and local testing.


Type '"esm"' is not assignable to type 'LibraryFormats'

Describe the bug
I'm going to try to make a UI library with Vite v3,but when I run build command something is wrong.
When I use es, instead of generating ESM files, CJS are generated , if I replace es with esm, the ESM file is successfully generated, no CJS file.
But there is an error message, the error is Error: Type '"esm"' is not assignable to type 'LibraryFormats'.
This is my vite.confit.ts
import { defineConfig, type LibraryFormats } from "vite";
import vue from '@vitejs/plugin-vue'
import vueJsx from '@vitejs/plugin-vue-jsx'
import { resolve } from 'path'
console.log(resolve(__dirname, './src/index.ts'), 'ts')
const rollupOptions = {
  external: ['vue', 'vue-router'],
  output: {
    globals: {
      vue: 'Vue'
    }
  }
}
export default defineConfig({
  plugins: [
    vue(),
    vueJsx()
  ],
  build: {
    rollupOptions,
    minify: false,
    lib: {
      entry: resolve(__dirname, './src/entry.ts'),
      name: 'SmartUI',
      fileName: 'smart-ui',
      formats: ['esm', 'umd', 'iife'], // Type error (Type '"esm"' is not assignable to type 'LibraryFormats')
     // formats: ['esm, 'umd', 'iife'] // cannot generate esm file
    }
  }
})

Reproduction
https://github.com/rookie-hhm/vite3-test.git
System Info
Using vite v3 and a config in TypeScript.

Used Package Manager
pnpm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

With lib.formats: ['es', 'umd', 'iife'], ESM is correctly generated as dist/smart-ui.mjs.
// smart-ui.mjs
import { defineComponent, h } from "vue";
const MyButton = defineComponent({
  name: "MyButton",
  render() {
    return h("button", "first button");
  }
});
const entry = {
  install(app) {
    app.component(MyButton.name, MyButton);
  }
};
export {
  entry as default
};

Would use expand "When I use es, instead of generating ESM files, CJS are generated ," more?

With lib.formats: ['es', 'umd', 'iife'], ESM is correctly generated as dist/smart-ui.mjs.
// smart-ui.mjs
import { defineComponent, h } from "vue";
const MyButton = defineComponent({
  name: "MyButton",
  render() {
    return h("button", "first button");
  }
});
const entry = {
  install(app) {
    app.component(MyButton.name, MyButton);
  }
};
export {
  entry as default
};

When I use es, instead of generating ESM files, CJS are generated ,

Would use expand this more?

Oh,sorry! It was my mistake! You are right.


access pico's ram through swd pins using another pico

Okay so I'm trying to write some data to a pi pico using another pico. I know i can use a custom bootloader to achieve this but i want to write a program to a fresh pico (that is not running anything) using another pico.
This can be achieved using openocd and a raspberry pi or another Pico as picoprobe but i don't want to have a Linux machine.
Basically i want to program a pi pico from another pico.
Any suggestions how should I proceed?
My goal is to somehow access the slave pico's ram through the swd pins so i can write data directly to it using the master Pico.

Any suggestions how should I proceed?

Sounds like you'll need to study the picoprobe sourcecode to see how it works, and then adapt it to suit your needs?
@kilograham I guess this ought to be moved to the picoprobe repo?

Thanks for the quick reply, sure I'll check out picoprobe source code. I wanna know if it's even possible to write code like that ?

I've not looked at the picoprobe sourcecode myself, but my (vague) understanding is that the host PC sends data to picoprobe, and picoprobe then writes that data to the secondary Pico using SWD. So I guess you "just" need to modify where picoprobe gets the data from? :shrug:

That's what I thought... I'll try to Modify the Picoprobe code, tho i think it's not an easy task to eliminate the pc and do everything on the picoprobe.


Sidenav blocking toolbar shadow - CSS

I am using the toolbar above the sidenav + sideav layout.
Recently I have noticed that the toolbar shadow does not show up.
I thought I needed to configure it by myself, but after a while I figured that it is the sidenav layout who is blocking me from seeing the shadow.
See this plunker
Tried to understand by myself what is going on over there, and why I can't stop this peculiar scenario, but to no avail.
What I want, obviously, is that the shadow of the md-toolbar to be displayed :)

I'd rather say this is a css problem than a bug. The md-sidenav-layout has a default background-color which is not transparent.
You can override it using inline style (or css, whatever) to make the layout background transparent.
<md-sidenav-layout style='width: 50%; background-color: rgba(255,255,255,0)'>

Or you can make the tool-bar's layer in top of sidenav-layout
<md-toolbar color="primary" style="box-shadow: 0 5px 5px #999;z-index: 1;position: relative;">

Oh, that position: relative solved it.
But how? Why?

@AmirTugi Did you mean why position: relative is needed to make it z-index: 1 work?

closing since this was just a CSS issue


documentation: the Template part of the page is cut

There might be a missing closing div somewhere.

I think it has been fixed with ce32aa9.


TextInput: render endContent exactly in the end of the control

Objective
TextInput locate endContent between cross and error elements. It looks a little bit confusing because:

cross and error elements are dynamically rendered and it makes static endContent be dynamic too
name of property supposes that content should be rendered exactly in the end of the control

Example

Solution Proposal
I suggest to add a new temporal property unstable_endContent:

this property will be render content after cross and error elements
this property will be added in the current 6 major
this property will be renamed to endContent in the next major
old property endContent will be removed in the next major

Hey guys. This change is fine on the design side.

This change is fine on the design side


PushServiceClientException with StatusCode.OK when sending message to Firefox on Android endpoint

Description
When sending a message to an endpoint registered by Firefox on Android an exception is incorrectly thrown.
Reproduction Steps
Using Firefox on Android (tested with 131.0.3), register for push notifications.
Send a push notification to the registered endpoint.
Expected behavior
The mesage is received and no exception occurs.
Actual behavior
The mesage is received but a PushServiceClientException is thrown with no Body and a HttpStatusCode of OK (200)
Possibly cause
It seems the below line, should check for either HttpStatusCode.Created or HttpStatusCode.OK before throwing an exception.
https://github.com/tpeczek/Lib.Net.Http.WebPush/blob/fef97afc3b65b6e43facd37f11fd2199ca5497dd/src/Lib.Net.Http.WebPush/PushServiceClient.cs#L392

I did some digging and it looks like Mozilla Autopush Server is implementing an older (expired) version of WebPush specification (at least this is what they are referring to in their docs: https://mozilla-services.github.io/autopush-rs/http.html#send-notification). That older version wasn't too specific about return codes:

A simple 200 response is sufficient to indicate that the push message was accepted.  This does not indicate that the message was delivered to the user agent.

The current version is a little bit more specific:

A 201 (Created) response indicates that the push message was accepted.

That said, it doesn't seem to forbid other statuses, which means that what Mozilla Autopush Server is doing (returning 202
when message will be delivered at a later time and 200 when message has been delivered to node client is connected to) is valid.
I will adjust the implementation to consider all three (200, 201, and 202) as success.


Mocha 8: Failing async test exits mocha watch mode on reload

Prerequisites

[x] Checked that your issue hasn't already been filed by cross-referencing issues with the faq label
[x] Checked next-gen ES issues and syntax problems by using the same environment and/or transpiler configuration without Mocha to ensure it isn't just a feature that actually isn't supported in the environment in question or a bug in your code.
[x] 'Smoke tested' the code to be tested by running it outside the real test suite to get a better sense of whether the problem is in the code under test, your usage of Mocha, or Mocha itself
[x] Ensured that there is no discrepancy between the locally and globally installed versions of Mocha. You can find them with: node node_modules/.bin/mocha --version(Local) and mocha --version(Global). We recommend that you not install Mocha globally.

Description
mocha --watch exists on second run if async test fails.
Steps to Reproduce
With this test:
describe('mocha watch issue', () => {

  it('async', (done) => {
    setTimeout(() => {
      throw new Error('Fail');
    }, 1);
  });

});

Running:
mocha --watch

And then touching the test file to trigger a second run of the test.
Expected behavior: [What you expect to happen]
The test fails on the second run exactly like on the first run and mocha keeps watching.
Actual behavior: [What actually happens]
Mocha exits on the second test run.
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Versions

The output of mocha --version and node node_modules/.bin/mocha --version: 8.0.1
The output of node --version: v14.4.0
Your operating system

name and version: macOS Catalina 10.15.5
architecture (32 or 64-bit): 64

Your shell (e.g., bash, zsh, PowerShell, cmd): fish
Your browser and version (if running browser tests): –
Any third-party Mocha-related modules (and their versions): –
Any code transpiler (e.g., TypeScript, CoffeeScript, Babel) being used (and its version): –

Additional Information
I have reported the very same issue for mocha 7 in #4143 and it got fixed. Maybe it's the same issue that somehow found its way back 😄

Yes, we've been monkeying with that code path, trying to reduce the chance we leak uncaughtException listeners.

cc @juergba who may have interest in this one.  @mantoni if it's blocking you, adding a test to reproduce this in a PR would be helpful to get us moving.  test/integration/options/watch.spec.js seems reasonable, and add a fixture in test/integration/fixtures/options/watch/

Hit this issue myself recently. I did a little digging & issue seems to be caused by the cloning the suite on L40. If I remove this hooks fire as expected.
https://github.com/mochajs/mocha/blob/02bdb6bc6c029fb0c01389b27797d00faa76ddde/lib/cli/watch-run.js#L38-L66

FYI looks like suite.clone() doesn't copy over any of the hooks.
https://github.com/mochajs/mocha/blob/7d3151d08a3082dd022116d00234caf1600a71b5/lib/suite.js#L117-L127
I did a quick local patch to add these & watch worked as expected.

I think this is closed by #4382.  Please let me know if it isn't.


Lazy Loading

If Lazy loading is caching data in the table why does the loading time remains the same like the data is being requested from the server again ?

Hi @Liahus1996, caching is disabled by default when lazy loading so you need to set caching to true in options.

How does search work in this case , since we are not going to load all the data at once ?

You have to implement search/filtering server-side as the table won't have access to the whole dataset. You can take a look at this mock service   for a rough idea on how to move forward. It's missing information about search/filtering and it's just an example how the response object could look like. But your response object should contain the search term(s) passed to the server, and to highlight the hits in the table you need to set/update info.searchTerms to the actual one returned from the server.
I've added a section in the wiki here with some more info. The example uses the same principle too, although the search terms are fixed.

Am not getting the sorting icons on my Table headers , what do i do ?

@Liahus1996 my guess is that you haven't added any styling for the headings. To get basic styling (small arrows for sort ascending and sort descending) you can add the stylesheet provided with generic table, ex. if you're using sass, you could import the generic-table sass file like this:

@import "~@angular-generic-table/core/scss/generic-table";

or if you prefer plain old css it's available here:
<EMAIL_ADDRESS>
If you'd like custom icons check out the css used in my example here:
https://github.com/hjalmers/angular-generic-table/blob/master/src/examples.scss

What is the difference between filtering and searching? In the advanced example, the search seems to highlight and filter at the same time, whereas applying the predefined filter only shows with record matching the search string. I'm trying to get the idea which one should I use for lazy loading from the server - searchTerms or filter or both.

@psined1, when using lazy loading it’s up to you how you want to use it but the general idea behind it and how it works when filtering and/or searching client side is that filters are applied before search. To make it more performant, the table only looks for matches inside strings after filters have been applied i.e. instead of going through all rows to find matches it only goes through the ones left when the filters have been applied. You might want to differentiate the two so they user knows how many records match the applied filters and how many are left out of those after searching through them using a string. Not sure if that makes any sense but if you want the user to be able to choose between a fixed set of values and filter/search the records using a free text string you’ll want to use both.


Redfish trips in fishin_CHPs

This query:
est_4X5Y_2017<- fishin_CHPs(type="ALL", stock = "4X5Y", dateStart = "2017-01-01", dateEnd= "2017-12-31", returnISDB=FALSE, useLocal = T, data.dir='C:/LocalDataDump', usepkg="roracle", oracle.username=AwesomeUser, oracle.dsn="PTRAN", oracle.password=AwesomePwd)
Results in records like this one: LOG_EFRT_STD_INFO_ID==1282589
In the DB, #1282589 shows up as having a mesh size of 110mm, making it a redfish trip and not a CHP trip. Halp.

Hey - please check your version of the package
est_4X5Y_2017$params$user[est_4X5Y_2017$params$user$PARAMETER=="Mar.fleets version","VALUE"]
I have 2021.11.10, and I expect you have an earlier one.  With the addition of some more advanced gear specificity, fishin_CHPs() no longer allows type="ALL" - it must be either "MOBILE" or "FIXED".
When I run the same query (trying both MOBILE and FIXED, I do not see that set appearing anymore.
Additionally, the gear information associated with each set (e.g. the mesh size) is now visible as part of the est_4X5Y_2017$fleet$FLEET_ACTIVITY object.

Also - for what you're doing, your function call doesn't need all of those parameters.  Assuming you change type from ALL to MOBILE, you could just do:
est_4X5Y_2017<- fishin_CHPs(type="MOBILE", stock = "4X5Y", year=2017, returnISDB=FALSE, useLocal = T, data.dir='C:/LocalDataDump)`


Catch warnings and error on warnings

The system call errors on stuff like missing gh cli but not if something inside the gh cli goes wrong, e.g. lost internet connection or incorrect tag name. In these cases, system just throws a warning message and our workflows don't fail.
It's better to throw an error in these cases because we want to be altered with failing workflows. That's why I catch warnings with purrr::quietly and error if a warning has been thrown. The message returns both the R warning and the gh cli message.

Based on https://github.com/nflverse/nflverse-data/issues/47#issuecomment-2305996503


Add npm install instructions to readme

Thanks for a great product. You should add "npm install notifyjs-browser" to the readme under the download header - took me a while to find it.

Fixed at #62 pull request.


[Propose] Add Task.leftShift has been deprecated caution message.

Due to Task.leftShift(Closure) method has been deprecated, a plugin developer needs to modify build.gradle.
It is hard to implement this change in the embulk migrate subcommand.
Instead, I add the following guide.
What do you think this idea?
Add example warning (a message may needs modify.)
** CAUTION **

If you see this message, you need to modify build.gradle.
Please see more detail at this URL: https://github.com/embulk/embulk/pull/698#issuecomment-312422241

"The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead."

Plugin developer will see this warning.
./gradlew classpath

> Configure project :
The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead.
        at build_49laod645hpyts1dwsiwbop80$_run_closure2.doCall(/Users/hsato/OpenProjects/embulk/embulk-output-jdbc/build.gradle:95)

BUILD SUCCESSFUL in 1s
21 actionable tasks: 21 up-to-date

Proposed example,
embulk-0.8.31.jar migrate .

2017-09-05 19:56:27.940 +0900: Embulk v0.8.31
Detected Java plugin for Embulk 0.8.22...

** CAUTION **

If you see this message, you need to modify build.gradle.
Please see more detail at this URL: https://github.com/embulk/embulk/pull/698#issuecomment-312422241

"The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead."

  Modified ./build.gradle
  Modified ./embulk-output-db2/build.gradle
  Modified ./embulk-output-mysql/build.gradle
  Modified ./embulk-output-oracle/build.gradle
  Modified ./embulk-output-sqlserver/build.gradle
Done. Please check modified files.

@hiroyuki-sato Hmm, do we really need this in embulk migrate? If I understand correctly,

Even if embulk migrate does not warn, the plugin's Gradle warns every build.
The warning in this PR does not seem checking existence of leftShift. It means that the warning is shown even if the plugin does not need changes.

@dmikurube  Thank you for the reply.
As you said, It's not a proper implementation.
If a developer looks up the keyword The Task.leftShift(Closure) method has been deprecated  , will find a solution easily


Move the wiki to here

I need to move the wiki documentation to this repo

today install ，fund error：
Problem 1
- Root composer.json requires api-ecosystem-for-laravel/dingo-api ^4.0 -> satisfiable by api-ecosystem-for-laravel/dingo-api[v4.0.0, v4.0.1, v4.0.2].
- api-ecosystem-for-laravel/dingo-api[v4.0.0, ..., v4.0.2] require dingo/blueprint ^0.4.4 -> found dingo/blueprint[dev-chore/laravel-7-compat, dev-master, v0.1.0, ..., v0.4.3] but it does not match the constraint.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require api-ecosystem-for-laravel/dingo-api:*" to figure out if any version is installable, or "composer require api-ecosystem-for-laravel/dingo-api:^2.1" if you know which you need.
need help

@boyadmin can you create a new issue and add your composer.json? This would help finding out what's wrong.

boyadmin

I have the same problem. How can I solve it

@yulin1115 could you create a new issue and add your composer.json? This would help to find out what's going on.

@boyadmin can you create a new issue and add your composer.json? This would help finding out what's wrong.

OK，commit new isuse

i wait the right answer

Can you guys please create a new issue if you are having it, this issue is for wiki docs.

Wiki moved.


Nom nom ugc

What's in this PR?
Additional diluting of logs :(
I understand that this makes our logs less valuable but rules are rules. no UGC/PII

:sadpotato:


Unable to reproduce behaviour of TimeGAN

Hi @birdx0810 !
Thank you for your great work. The code is clean, classy and neat. I come here not for addressing an issue, but more for seeking for some guidance.
We have been working for a long while with both TimeGAN and your code, and have addressed the issues you mentioned in your open issue #1 and made all the necessary changes to make the code behave the same both in TimeGAN and your implementation (the noise generation, and we even reintroduced a "bug" you noticed and cleaned: the sigmoid activation function as the last layer of the recovery network that doesn't make sense to us).
I explain myself a little bit so you can gain some context: we're trying to generate alibaba2018 machine usage data-center trace. We have been able to obtain good results with TimeGAN with a particular hyperparameterisation (3 GRU layers, 10 hidden dimensions, 100 of batch size, 288 sequence length, and the rest of parameters by default). However, with your implementation we cannot get the same behaviour as that of TimeGAN, and the "problem" is particularly focused: the G_loss_V is way higher (1 order of magnitude), and the model seems to be unable to catch the patterns and the inherent variance.
Seen that you have a vast knowledge on this topic, I gently ask you for some intuitions you may have on why pytorch behaves differently than TF1: we're blocked as we don't really know if it's some internals of the loss functions, optimisers (and backpropagation) and/or Pytorch's RNN implementations.
I would be very grateful if you could share some hints (if you may have some) on why this discrepancy in the behaviour of the G_loss_V happens.

Thank you very much for your reply.
It's a pity you abandoned academia, your skills and expertise are great and I'm sure that they are now in good use.
We'll stay in the trenches, and, if we find something relevant out I'll let you know (even though it would be just out of curiosity).
Again, let me congratulate you for this great work. If you feel the call for research again, we'll be grateful to collaborate with you, hahaha.
Best!


Rebalancing an upsert table causing high GC and failure to reconnect to ZK

Follow up from https://github.com/apache/helix/issues/2951 which provides more detail.
We performed a rebalance on an upsert table using low-disk mode that led to high GC on a server and the server constantly trying to reconnect to ZK. The server never recovers until we manually restart it.
@Jackie-Jiang had a theory this might be tied to the metadata manager for old partitions not getting released even after the segments were all dropped and thus there's a large empty concurrent hash map still on heap causing GC.

cc @klsince @tibrewalpratik17

#11626 also might be related where we have seen similar behaviour after long GC pause and helix-pending-messages metric spikes up and doesn't recover.


[docs] Remove StyledEngineProvider usage on the top of the App

Updates done in the PR:

removes the usage of the <StyledEngineProvider injectFirst> at the top of the app
uses custom cache provider only if rtl is on
uses enhanceApp in favor of enhanceComponent

Tested:

rtl is working
dark mode is working
global styles are not leaking

Preview: https://deploy-preview-27358--material-ui.netlify.app/

We need to first not have any makeStyles usages on the docs in order for this to work.

Does it mean we can close https://github.com/mui-org/material-ui/issues/16947? cc @vicasas

Are we done?

@oliviertassinari From what I remember, some module files are missing from the onepirate template. And all the others that don't have a check.

Does it mean we can close #16947? cc @vicasas Are we done? I'm not sure

There are few occurrences, I will remove them as part of this PR

There are few occurrences, I will remove them as part of this PR

@mnajdova I had a quick look. I could find the following components that are using JSS and that override emotion:

Pro
Quotes
Sponsors
Steps
Users
TopLayoutCompany
TopLayoutBlog
Ad
ReactVirtualizedTable
Team
Onepirate/Snackbar
Onepirate/TextField
Onepirate/Typography

Regarding the broken search bar and drawer, it looks like this PR is not based on HEAD, so likely why we have issues.

@mnajdova Do you plan to resume the work on this PR or will it be delayed to post v5? If it's later, I propose we close. We can use the GitHub issues to keep track of the work that is left to be done #16947.

As a general note (not directly related to this PR, but it could be). We don't really have to use PRs as a personal bookmark, it could be done like on Google Keep, Evernote, etc. Would it make sense to enforce an automatic PR close logic for PRs inactive after, say 30 days, more? Maybe it would set a healthy constraint to stay in sync with what we wish our bandwidth would be, what its in reality, and what our true priorities are?
It would close all PRs that we have deprioritized (inactive for a while), it would lead to having the open PRs for ongoing work. My assumption is that it could 1. make it reviewing work more appealing (why? to know where to focus). 2. communicate to others what's up for grab (why? seeing something open doesn't open somebody else to work on the same problem).

@mnajdova Do you plan to resume the work on this PR or will it be delayed to post v5? If it's later, I propose we close. We can use the GitHub issues to keep track of the work that is left to be done #16947.

We can close, I planned to work on it last week, but other things came up. I will re-open once I get back to this, or start from scratch...

As a general note (not directly related to this PR, but it could be). We don't really have to use PRs as a personal bookmark, it could be done like on Google Keep, Evernote, etc. Would it make sense to enforce an automatic PR close logic for PRs inactive after, say 30 days, more? Maybe it would set a healthy constraint to stay in sync with what we wish our bandwidth would be, what its in reality, and what our true priorities are?

Agree, it makes sense. If someone haven't work on a PR for a month, it's likely that we can close.

A fun one in the OSS landscape https://github.com/odoo/odoo, more PRs open than issues 😁


Dockerfile update

What this PR does / why we need it:
People outside caicloud can't build docker image locally due to dependency with private base image. This PR to solve that issue. Also, this change helps to reduce image size.
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @your-reviewer

Release note:

NONE

/assign @ddysher

@supereagle @anoopwebs When can this new image be released? Can it have a release label?

@anoopwebs  I think you need to rebase this PR, then it will not included the code of #9.

@emillg  Will release one version after this PR merged.

@anoopwebs I think you need to rebase this PR, then it will not included the code of #9.

@supereagle  done!

/lgtm

/approve

@emillg Have create release v0.1.0

Thanks @supereagle

hi @supereagle, it looks like the Docker image doesn't have that release version?
$ docker pull cargo.caicloud.io/sysinfra/event-exporter:v0.1.0
Error response from daemon: manifest for cargo.caicloud.io/sysinfra/event-exporter:v0.1.0 not found


Enhanced link in MD preview isn't standard

Noticed this while using this extension in code-server
The enhanced link will just direct the web url out of vscode.
As a reference:
[[page]]    =>    generates a link like "/absolute/path/to/page"
[page](./page.md)    => generates a link like "/webview/vscode-resorce/file///absolute/path/to/page"

I quickly checked just following the pattern doesn't work in normal VS Code.
(Nor does it just use the adjacent getImgUrlForMarkdownPreview)
Probably related to https://github.com/microsoft/vscode/issues/97962

Sure:)
My current propose is to replace the hand-crafted HTML in extendMardownIt with MarkdownIt.render(translatedMarkdownSource).
(haven't verify it's fixing the problem on code-server but it seems not breaking the usage in vscode)
What do you think?

I assume this code along with this part should be compatible with code-server env?

Actually after digging it a little I think the problem is with code-server(the link doesn't work if it's an absolute path, while the same content works on VSCode).
Filing https://github.com/cdr/code-server/issues/3124
I'm closing this issue for now hoping they can fix this in code-server and there's no work left to be done in this extension.
Thanks.


Add migrate at startup prop

Add migrate at startup prop

@gabriel-farache care to bump chart version?

@gabriel-farache care to bump chart version?
@masayag done

https://github.com/parodos-dev/workflow-software-templates/pull/43 will set the properties at creation


KTX export/encoding support

Hi! Thanks a lot for this great resource! It is really helpful! I was wondering if there is a way to directly save RenderTexture data as .ktx file.
Currently, I am using Texture2D.EncodeToPNG() that converts the texture into a .png image and then using ktx command line operation to get the corresponding .ktx file. I wanted to directly save it into a .ktx file.

Thanks @atteneder! I look forward to having this functionality soon! If I come up with anything useful, I will ofcourse share with you! I would also appreciate if you let me know when this new feature is available to use! 😄

@oaishi Sure! Let's keep this issue open. You're subscribed already and will get notified when someone posts a comment or it is closed.

Thanks again, @atteneder!


Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)

I am using<EMAIL_ADDRESS>(currently the lastest version).
When running my gulp task I get this:
/Users/samthilmany/<Project>/node_modules/gulp-sass/node_modules/node-sass/lib/binding.js:13
      throw new Error(errors.unsupportedEnvironment());
      ^

Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.5.2
    at module.exports (/Users/samthilmany/<Project>/node_modules/gulp-sass/node_modules/node-sass/lib/binding.js:13:13)
    at Object.<anonymous> (/Users/samthilmany/<Project>/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/Users/samthilmany/<Project>/node_modules/gulp-sass/index.js:187:21)

I'm using macOS 10.13 and am running<EMAIL_ADDRESS>

You need<EMAIL_ADDRESS>delete your node_modules to get the latest
node-sass.
On 27 Sep. 2017 1:48 am, "Sam Thilmany"<EMAIL_ADDRESS>wrote:

I am using<EMAIL_ADDRESS>(currently the lastest version).
When running my gulp task I get this:
/Users/samthilmany//node_modules/gulp-sass/node_modules/node-sass/lib/binding.js:13
throw new Error(errors.unsupportedEnvironment());
^
Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:https://github.com/sass/node-sass/releases/tag/v4.5.2
at module.exports (/Users/samthilmany//node_modules/gulp-sass/node_modules/node-sass/lib/binding.js:13:13)
at Object. (/Users/samthilmany//node_modules/gulp-sass/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
at Module.require (module.js:517:17)
at require (internal/module.js:11:18)
at Object. (/Users/samthilmany//node_modules/gulp-sass/index.js:187:21)
I'm using macOS 10.13 and am running<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dlmanning/gulp-sass/issues/628, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWOPbdn4N2Eg7v42vj_lVdb4DVbG7ks5smRzngaJpZM4PkeJI
.

@xzyfer  Hi , i have the same issue but with windows 10 how can i solve the problem using cmd commands
thnks for help

Delete node_modules and npm install
On 19 Dec. 2017 8:26 pm, "BasmaRadadi"<EMAIL_ADDRESS>wrote:

@xzyfer https://github.com/xzyfer Hi , i have the same issue but with
windows 10 how can i solve the problem using cmd commands
thnks for help
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dlmanning/gulp-sass/issues/628#issuecomment-352686893,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWHwVQL_xgmZIwl_d5KNzNr5f663Gks5tB4FNgaJpZM4PkeJI
.

Updated node-sass package to 4.7.2 version and it works for me.


Tags in Posts

Just found this. Are you still working on getting tags to show up in posts?? It would sure be nice.

I do think about this ever time I use til. It’s partially done, I should finish it some time….


Dev tools

Here are some other useful flake8 plugins which could be useful to our project:

https://github.com/best-doctor/flake8-class-attributes-order
https://github.com/nhoad/flake8-unused-arguments
https://github.com/best-doctor/flake8-variables-names

Static Type Checking:

Mypy
Pyright

Please take a look at them and comment.

All the flake8 plugins you suggested seem really useful. As the type checker, I would go with mypy (that's what I've always used).
My only concern is that they might be too strict and slow down the development a bit.

They should all be really helpful with keeping our code maintained and well checked. We don't have to add them to pre-commit either to enforce them, just remember to do them manually every now and then if we don't want the strictness


Babel for tests

Would love to see babel used for tests, especially for projects that deal with decorators or other features that would require babel for the tests.

actually, tests in generated modules are already running through babel https://github.com/bucaran/generator-rise/blob/master/app/templates/package.json#L15

Sweet, didn't notice. Great generator!

=) you also can take a look at another tiny es generator


set Bandage XDG_RUNTIME_DIR to user writable folder

e.g. XDG_RUNTIME_DIR=~/tmp
This is horrible but I don't see a workaround for the bandage image command to still run
Qt is a dependency, and it will look in /run/user/[d+]/ if not specified as an environmental variable 🤦♀

addressed (although poorly) here 775ed4feeb209c9ab2d8e4e3d3cfa9a8a874bcff


import and relations of fields

Version information

Laravel: v6.5.0
Voyager: v1.4
PHP: 7.4
Database: MySQL

Description of problem
Hello and thank you for your help. I have my laravel/voyager application ready. My problem is that I have to import 8000 records. When I imported the tables into the database (by MySQL), I didn't know how to relate the fields.
For example:

The "item" field in the "doc_certifications" table is related to "aux_items" in the "item" field. The records I have to import already have "item" assigned.
I don't know how to import the records, at the same time that they are related.
There are several related fields and I feel lost.
Proposed solution
I really looked and didn't find a smart solution. I was about to use "Macro Recorder" and load one record at a time.
Alternatives considered
That's a lot of tables with more records. I only showed one as an example.
Additional context
It will be an import of several tables. In the future it would not be necessary to do it again.

This is not a feature request it's a question, please ask questions in Voyager Slack chat.


Adding optional parameter to mysqli::store_result

https://www.php.net/manual/en/mysqli.store-result.php

@maxal Is there something wrong with the pull request?

No, it's fine, thank you! I had to close/reopen it to trigger a new Travis build since it was failing due to the Docker image update for PHP.
We will review and merge it shortly!


Missing Nan::SetCallAsFunctionHandler?

Hi,
I have an ObjectTemplate and trying to set its function handler via SetCallAsFunctionHandler:
tmpl->SetCallAsFunctionHandler(MyClass::New);

MyClass::New is just a regular NAN_METHOD. But the above doesn't compile of course:
error: invalid conversion from ‘Nan::NAN_METHOD_RETURN_TYPE (*)(Nan::NAN_METHOD_ARGS_TYPE) {aka void (*)(const Nan::FunctionCallbackInfo<v8::Value>&)}’ to ‘v8::FunctionCallback {aka void (*)(const v8::FunctionCallbackInfo<v8::Value>&)}’ [-fpermissive]

There should be Nan::SetCallAsFunctionHandler() for that puropse, right? I cannot find it. If it's missing could someone please suggest me a quick workaround?

Yes, it seems to be missing. There is no quick workaround, short of actually implementing the missing function.

Do you have plan to support it in a next release? There is a +1 for that.

I can see some progress on this, but it's really hard to follow from there. Does it landed in a release yet?

Not yet. 2.1
On September 11, 2015 8:06:17 AM GMT+03:00, "Gábor Mező"<EMAIL_ADDRESS>wrote:

I can see some progress on this, but it's really hard to follow from
there. Does it landed in a release yet?

Reply to this email directly or view it on GitHub:
https://github.com/nodejs/nan/issues/427#issuecomment-139453330


New release?

There have been quite a few changes since the last release: https://github.com/snc/SncRedisBundle/compare/3.1.0...master
Could you cut a new tag please, @B-Galati ? :slightly_smiling_face:

Yes it's on my to-do for tomorrow morning ;)


./startup.sh failing on WebApi .Net 5

Hi, I'm new to docker and trying to trying to run the solution with the commands listed in the readme. When running the startup.sh I get the below error. Not sure how the errors throwing since the WepApi docker file is targeting the 5.0 sdk. Any advice?
Step 5/6 : RUN dotnet restore "src/WebApi/WebApi.csproj"
---> Running in 8023c614b74b
Determining projects to restore...
Restored /src/src/Domain/Domain.csproj (in 14.45 sec).
Restored /src/src/Application/Application.csproj (in 14.45 sec).
Restored /src/src/Infrastructure/Infrastructure.csproj (in 35.78 sec).
Restored /src/src/WebApi/WebApi.csproj (in 35.89 sec).
Removing intermediate container 8023c614b74b
---> 845124d2d746
Step 6/6 : RUN dotnet build "src/WebApi/WebApi.csproj" --no-restore
---> Running in 8182e54e95bb
Microsoft (R) Build Engine version 16.7.2+b60ddb6f4 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.
/usr/share/dotnet/sdk/3.1.406/Microsoft.Common.CurrentVersion.targets(1177,5): error MSB3971: The reference assemblies for ".NETFramework,Version=v5.0" were not found. You might be using an older .NET SDK to target .NET 5.0 or higher. Update Visual Studio and/or your .NET SDK. [/src/src/WebApi/WebApi.csproj]
Build FAILED.
/usr/share/dotnet/sdk/3.1.406/Microsoft.Common.CurrentVersion.targets(1177,5): error MSB3971: The reference assemblies for ".NETFramework,Version=v5.0" were not found. You might be using an older .NET SDK to target .NET 5.0 or higher. Update Visual Studio and/or your .NET SDK. [/src/src/WebApi/WebApi.csproj]
0 Warning(s)
1 Error(s)

Hey @IsaacCalligeros it has been a long time but I kindly ask you to check the latest version.