Error when working with stack projects

Every time I open an *.hs file within stack generated project and save this file, I get such error:

This error exists only when working with project files generated by command stack new project (and followed by stack setup and stack build). When I work with standalone *.hs file I don't get such error.
OSX El Capitan 10.11.1
Atom 1.2.0
haskell-ghc-mod 1.1.3
ide-haskell 1.3.5
stack <IP_ADDRESS> x86_64
ghc-mod version <IP_ADDRESS> compiled by GHC 7.10.2
Here is a log from developer console:
-1447626365072.txt

I;ve tried to install Haskell platform with all cabals, ghc-mod, hlint etc., changed paths to it in settings, but still get the same error. I've also tried to open same files with emacs which works with ghc-mod too, and in emacs everything goes fine.

I get the same error.

@welf, I'm confused about your PATH settings. /Users/AW/.stack/programs/x86_64-osx/ghc-7.10.2/lib/ghc-7.10.2/bin/ghc this doesn't seem like a directory name?..

As for this error, it seems ghc-mod tries to run cabal and fails. Do you have it in your PATH?

I'm confused about your PATH settings. /Users/AW/.stack/programs/x86_64-osx/ghc-7.10.2/lib/ghc-7.10.2/bin/ghc this doesn't seem like a directory name?..

It is the PATH to globally installed by stack GHC. When I change a PATH not to GHC, but to the directory which contains GHC, I get the same error.

As for this error, it seems ghc-mod tries to run cabal and fails. Do you have it in your PATH?

When I've tried to make it work with Haskell Platform, yes, it was the PATHes to Platform's GHC and to cabal in my .bash_profile file (and I changed appropriate PATHes in haskell-ghc-mod settings). After I saw I still get the same error, I've uninstalled Haskell Platform, leaving only stack. But before it I've tried how ghc-mod works in emacs, to define whether the problem is in ghc-mod itself or in haskell-ghc-mod for Atom. It worked fine, including REPL, so emacs saw the PATH to cabal in .bash_profile.

Well, on OSX, Atom doesn't pick up on PATH in .bash_profile unless it's started from terminal (and that's primary reason why additionalPathDirectories setting exists at all). Would that make sense?
As for path to ghc, specifying path to a file instead of directory in additionalPathDirectories can lead to problems on certain platforms. I would advise you remove it. What you actually need to do is to duplicate your .bash_profile PATH there (using comma instead of colon as a separator, and dropping $PATH or other environment variables)
See https://github.com/atom/atom/issues/6956 for more details and other solutions.
Also see https://github.com/kazu-yamamoto/ghc-mod/wiki for more information on ghc-mod with stack. In particular,

Make sure the dist/setup-config file doesn't exist in your project directory (the directory also containing your *.cabal file). When this file exists ghc-mod assumes you want to use cabal-install instead of Stack.

I have set it up like you say. What I find odd now is that when I run Ghc-Mod -> Check, I get this error:

And it creates directory dist in the root of my project.
(this does not happen if I run ghc-mod standalone)

I've tried to start atom from terminal and it works without errors, thanks.
It worked without errors also when Atom started not from terminal, after I've copy-pasted the whole PATH string from my .bash_profile file to the Additional Path Directories field in haskell-ghc-mode settings (replacing : separator to ,  separator). Setting only PATH to GHC in Additional Path Directories field doesn't helped, but when I've set there all PATHes from my .bash_profile file, it started to work without errors.
Thank you a lot again!
@WillSewell Make sure that you have set the right PATH to globally installed by stack GHC, executing
printf '%s\n' ~/.stack/programs/*/ghc-*/bin/
@lierdakil

As for path to ghc, specifying path to a file instead of directory in additionalPathDirectories can lead to problems on certain platforms. I would advise you remove it.

Please change the wording for Additional Path Directories field, because it is confusing at the moment, asking to indicate PATH to ghc, but not to the directory it contains:

@welf, oops. Sorry about that. I'm on it.

Okay, v1.1.5 should have a more clear description. Hope it is satisfactory.

@welf thank you! I did what you said and also installed cabal-install with stack and added its directory to Additional Path Directories. Seems to be working great now!

@WillSewell, in general, you shouldn't need cabal-install with stack. Just saying.

Yes, I've installed cabal-install with stack too a few days ago. Don't know whether it works without it.

I have the same issue as @WillSewell without cabal-install


Update index.html

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign ablazleon
You can assign the PR to them by writing /assign @ablazleon in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

:star: PR built and available in a preview environment ablazleon-mynodejx-pr-5 here


Docker on Mac is slow

The entire development environment is slow for some reason, not sure if this is a Docker problem or something added to LaraDock that makes it that slow!! (By slow I mean the response time is slow, and the commands running in the workspace container are also slow).
We need your help to find out what's slowing it and make it fast again.
This is also mentioned in the following issues #97, #145, #149 & #307.

I am also experiencing some issues on Windows 10 using Docker Toolbox. I am not sure if this is directly related to this container or Docker, or Docker Toolbox per se.
I have hosted a basic dingo api on my Windows 10 Docker Machine using the following stack:

php-fpm php7
nginx
redis
mysql

Average time for requests  to complete is 1.5 seconds. Even for basic authentication requests
I have hosted this on a non-powerful VPS and is geographically far from my region. It sits on a different continent. I am using this stack:

php5.5
apache2
mysql

Average time for requests to complete is 300 ms

I have same trouble, not specially with Laradock but with Docker generally.
My dev environment is based on Mac OSX (10.11.6 (15G1104)). I think, speed has been degraded when i move from Docker Toolbox to the Docker for Mac.

Let's gather more data from all the users to try to find out where is the problem exactly!
@elceka I have the same feeling as I started experiencing this performance problems only using Docker for MAC. However, @geocine is on Windows and still using Docker Toolbox and facing the same problems! So far this tells me that there's a problem with some LaraDock containers!!

@Mahmoudz YOP, I understand, but truth may bee somewhere in the middle. :)

Everything is possible :D I'm excited about this Issue!

I have been having issues with Docker on mac related to performance. I think its due to this... https://forums.docker.com/t/file-access-in-mounted-volumes-extremely-slow-cpu-bound/8076/203. Laradock, and Docker in general runs perfectly for me when im running linux.

@Mahmoudz in this issue https://github.com/LaraDock/laradock/issues/145 Vasiliy says he fixed it by using rsync instead of osxfuse. I think that make sense if the problem is the way OS handle the mounting points. And maybe the same can be true of Windows, specially windows 10. I've been trying to make it work (via rsync), but I'm quite new at docker, so I have not succeed. Will keep trying and update this if I make it work.

I can attest that my native Docker for Linux for Xubuntu runs flawlessly and performs pretty well while my Windows 10 Home that uses Docker Toolbox is pretty slow. I think my issue is more about the virtual machine rather than the workspaces, though I thought I'd share my observations

I'm experiencing some issues too on macOS Sierra and Docker version 1.12.0-rc4, build e4a0dbc, experimental. Every time I update something, an html file, js file, any file, the browser takes forever to reload what I updated, even when deleting the whole file, I can still access to it from the browser for a few minutes -yes, minutes!-. I'm currently using nginx+hhvm on Laravel 5.3. On the other hand, updating files with apache2+php-fpm takes no more than a few seconds, tho.
But still, my whole project takes 1 second to load with nginx+hhvm, and 7 to 9 seconds with apache2+php-fpm.
My teammates are experiencing the same issues on both linux (Ubuntu 16) and windows.

@deleonn please take a look at #355

@philtrep Thanks a lot, I'll try it out later

Take a look at this project: https://github.com/IFSight/d4m-nfs There is a small issue with the script, but if you see the issue comments on the repo there is a simple fix for them. Using this script in conjunction with laradock decreased my api calls from ca. 10 seconds waiting to ca. 1 second waiting.

as @brianvice suggested, nfs definitely speed things up. I used this project to enable nfs mounts on my Mac (technically a Hackintosh, but I'm not sure that's relevant). https://github.com/adlogix/docker-machine-nfs
The performance boost seems to be 13%.

Laravel/laravel from 283ms to 245ms. Blackfire delta
Personal project from 2s to 1.75s No blackfire delta because free plan only enables 1 share at a time

Laradock by itself has no reasons to work slow. In my case it depends on the default Virtualbox driver which uses to mount volumes.

The solution is to use NFS to mount the “Users” directory.

Also there is an important difference between Docker Toolbox & Docker for Mac. Docker Toolbox uses docker-machine with Virtualbox driver to provision a virtual machine whereas Docker for Mac is native app which uses HyperKit. Likely, it's typical for Docker Toolbox with default Virtualbox mount driver.

I also can confirm improved performance with:
https://github.com/IFSight/d4m-nfs
This was with an installation of Statamic which I'm guessing that it does some more file IO than Laravel.

What type of file system are you mounting the shares with? NFS?
On Tue, Nov 22, 2016 at 4:46 AM, João Joyce<EMAIL_ADDRESS>wrote:

I also can confirm improved performance with:
https://github.com/IFSight/d4m-nfs
This was with an installation of Statamic which I'm guessing that it does
some more file IO than Laravel.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/laradock/laradock/issues/353#issuecomment-262207882,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA2C1ejI0YHO6CFB8u9s_G-cJHnOt0WSks5rAsgFgaJpZM4KSKnt
.

Hi guys, I managed to use https://github.com/IFSight/d4m-nfs with a ruby on rails app and it works very well.
I would like to use it for a Laravel project:

How would you update the docker-compose.yml?
How woud you update the d4m-nfs-mounts.txt (d4m-nfs config file)

Many thanks.

Found the solution: https://github.com/IFSight/d4m-nfs/issues/5
In order to be able to use d4m-nfs you just need to perform the folowing steps.
Clone d4m-nfs repository (in your home directory)
git clone https://github.com/IFSight/d4m-nfs ~/d4m-nfs

Update configuration file (~/d4m-nfs/etc/d4m-nfs-mounts.txt), the following configuration let you use relative paths for volumes in docker-compose.yml
/Users:/Users
/Volumes:/Volumes
/private:/private

Check the system file /etc/exports and clean it up if required (there may be collisions if you come from Vagrant or if you already executed the d4m-nfs.sh script)
Run the d4m-nfs.sh script
~/d4m-nfs/etc/d4m-nfs.sh

Bring your containers up through docker-compose, in my case
cd ~/my_cool_project/laradock
docker-compose up -d nginx mysql phpmyadmin

This approach let me have NFS speed benefits on both laravel (on laradock) and ruby on rails (on passenger-docker) projects.
Hope this can help!
Mauro

@maurosbu I tried your little "how to", but i kept getting errors when docker tried to mount the volumes.

volumes:
- /Users/michael/Sites:/var/www

I have 1 laradock for all my projects and modify the nginx vhost settings accordingly, it works fine when Docker shares the directories. But when i use the steps you used, i just get errors.

@michaelgracious can you please check that:

/tmp is the only shared folder (Docker > Preferences > File Sharing)
there isn't any conflict in /etc/exports (I had problems with old vagrant exports)

For volumes you can use relative path. If you cloned laradock in your home directory then in ~/laradock/docker-compose.yml you can use:

volumes:
- ../Sites:/var/www

Let me know if it works.
Mauro

@maurosbu I did only share /tmp in Docker, i tried both absolute and relative paths.
I keep getting the following:

Starting laradock_redis_1
Starting laradock_applications_1
Starting laradock_mysql_1

ERROR: for applications  Cannot start service applications: Mounts denied:
The path /Users/michael/Sites
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.
ERROR: Encountered errors while bringing up the project.

@michaelgracious did you start the d4m-nfs.sh script?

@maurosbu yes i did, it is running  and i can access with via "screen -r d4m". note that it's only the nginx container that keeps failing

@michaelgracious can you please post the content of /etc/exports ?

@maurosbu

$ cat /etc/exports
# d4m-nfs exports
"/Users" -alldirs -mapall=0:0 localhost
"/Volumes" -alldirs -mapall=0:0 localhost
"/private" -alldirs -mapall=0:0 localhost

Just adding a +1.  We're migrating from homestead to laradock and I'm noticing way slower response times with laradock.  Docker for Mac 1.12.3 (13776) here.  Relatively vanilla laradock config.

@soundsgoodsofar it is a Docker for Mac issue. If you want to speed things up I suggest to using d4m-nfs.

@soundsgoodsofar let us know if it works for you right away, i couldnt get it to work on my Mac Book Air at all, using Sierra. d4m-nfs that is

Yep thanks guys, followed the steps for d4m-nfs from @maurosbu and things have sped up considerably.
Would be great if we could get this pushed up into the core D4M implementation.  I'll add it to our setup instructions, but people on our team use vagrant and other things that probably write to /etc/exports for a variety of reasons, so I'm a little hesitant to automate it.

@soundsgoodsofar @michaelgracious @maurosbu could someone create a PR adding the fix to the docs? This seems like a recurring issue.

Same issue here on OSX, its really slow. I tried (d4m-nfs) , but unable to get it to boot with docker.
With d4m-nfs I keep getting
ERROR: for applications  Cannot start service applications: Mounts denied: r more info.  /Volumes/Development/http is not shared from OS X and is not known to Docker.
Does anyone have d4m-nfs working on OSX sierra ?  Other then the slowness, its great ready to fully switch over to this from homestead.

@pixelone did you follow my guide?
I'm running docker for mac + d4m-nfs on MacOS Sierra successfully.
Did you run d4m-nfs.sh before bringing containers up?
Did you check /etc/exports for conflicts (you have conflicts if you worked with vagrant + nfs before switching to docker).
Mauro

@maurosbu - Yeah tried it step by step even deleted the /etc/exports to ensure it was empty. I have my development code on an external drive mounted as Development.  I think most people are just mounting the Users/ folder, so maybe something with it being on another drive.
My exports file looks correct, the only other issue is private won't mount. I get this when I screen -r d4m
mount.nfs: access denied by server while mounting <IP_ADDRESS>:/private mount: mounting <IP_ADDRESS>:/private on /private failed: Permission denied
Any suggestion would be great.

@maurosbu I'm also running into this issue periodically.  Seems like whenever I restart OS X or just randomly after a while of non-use.  Running d4m-nfs.sh again fixes it, but that's pretty annoying and I hesitate to call it a "solution".

ERROR: for applications  Cannot start service applications: Mounts denied: tps://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.

@michaelgracious I follow your guide but I get the error.
ERROR: for applications  Cannot start service applications: Mounts denied:
The path /Users/lavenkin/www
is not shared from OS X and is not known to Docker.
You can configure shared paths from Docker -> Preferences... -> File Sharing.
See https://docs.docker.com/docker-for-mac/osxfs/#namespaces for more info.
.
ERROR: Encountered errors while bringing up the project.

this is my /etc/export content
# d4m-nfs exports

"/Users" -alldirs -mapall=501:20 localhost
"/Volumes" -alldirs -mapall=501:20 localhost
"/private" -alldirs -mapall=501:20 localhost

and /tmp is the only shared folder in my docker file sharing
@michaelgracious are you solve the problem

when I rebot my mac again and run the script ~/d4m-nfs/d4m-nfs.sh it work success, I check the mount use  screen -r d4m
<IP_ADDRESS>:/Users/lavenkin /mnt nfs nolock,local_lock=all 0 0
<IP_ADDRESS>:/Users /Users nfs nolock,local_lock=all 0 0
<IP_ADDRESS>:/Volumes /Volumes nfs nolock,local_lock=all 0 0
<IP_ADDRESS>:/private /private nfs nolock,local_lock=all 0 0

I think it mount failed before I reboot the mac.

I solved this issue on https://github.com/gagarine/docker-php by using http://docker-sync.io/ . It's in my opinion the best solution for mac.

@gagarine can you share with us a PR of your solution!?

Sure, but after my post I was looking at https://github.com/IFSight/d4m-nfs/issues/7 and it seem d4m use heavy caching than make it perform better than I taught (I already tested other nfs workaround).
I will test it with laradock and see if I can do a PR. Generally, think it make no sens to continue maintaining https://github.com/gagarine/docker-php if this project can provide similar functionalities.

@gagarine Can't wait to close this issue.
You are welcome to join our team of Admins and maintain this project with us, since we are currently looking for a 5th Admin :)

Mahmoud,
I spoke with you when you did the Live feed with Laravel DFW. I would like
to join the admin team if you are seriously looking for a 5th.

Hi @scoutman57 I do remember you very well, hope you are doing good :)
The project is growing everyday and thus we needs more maintainers.. @appleboy, @philtrep and I been maintaining this project lately. Few days ago @mikeerickson has joined us as well.
For the 5th Admin "maintainer", we decided to do the following:

The reason I welcomed @gagarine to join us, is because he has his own docker project and he's helping to solve a major problem in Laradock. Usually people like him will always find time for open source contributions...
Anyway, there is always room for passionate developers to join us anytime, all they have to do contribute, contribute and contribute more :D and we will reach them!
@scoutman57 I will contact you in our next round of recruiting admins. Best,

I need some time to get familiar with laradock, but it seem to take a similar approach to what I did. I'm switching right now a drupal 8 project to laradock to see how it works on a real project.
I'm not sure I have time to take the responsibility of joining the admin team (thanks for asking!), I need to think about it and perhaps do a quick chat with you guys.
In any case I will gladly help with this issue.

I developed docker-sync initially to cope with heavy load PHP projects like Drupal, which have a lot of files and read a lot during every bootstrap ( request ). Those kind of frameworks, also like Magento, tend to basically not work in any proper sense using dockertoolbox (native fusion/vbox share ), d4m ( own sync FS, slower then NFS ) or NFS.

That said, i guess it could be a good match with laradock. Some metrics, we use docker-sync in a
env of:

25.000 files
140 MB PHP code
multi microservices stack ( mecached/redis/nginx/FPM/percona/mongodb )

This is used on daily base in development. This should match the use-cases you have with laradock.
What i recommand:

use unison as a sync_strategy
probably either plan to use the daemon mode ( 0.2.0 ) or think about using docker-sync as a library https://github.com/EugenMayer/docker-sync/wiki/7.-Scripting-with-docker-sync to orchestrate your own bootstrap, if you need that.
Depending on your needs, you might use docker-sync (only sync, docker-compose is your duty ) or docker-sync-stack ( docker-compose integration build in https://github.com/EugenMayer/docker-sync/wiki/2.2-sync-stack-commands
you can easily provide docker-sync as a alternative solution using portable docker-compose.yml files https://github.com/EugenMayer/docker-sync/wiki/Keep-your-docker-compose.yml-portable .. you could use docker-compose-docker-sync.yml in case someone wants to run with docker-sync. This keeps your usual docker-compose files untouched
consider looking at https://github.com/EugenMayer/docker-sync-boilerplate yourself and creating such a starting point for testers if needed. I guess laradock is a "boilerplate" generator by default, so having this repo is either temporary or not needed

If anyone is interested there is an active issue on the docker for mac github here https://github.com/docker/for-mac/issues/77
I finally got d4m-nfs to work after some hassles. The one thing I discovered is that you should not the script as root, if you happened to run it as root in the past you may need to remove the files under /tmp/d4m*
sudo rm -rf /tmp/d4m*
Hope that helps someone, thanks for the hard work.

Don't know about php, but for ruby and node mounting .bundle and node_modules using named volumes instead of through osxfs fixes performance. Is it vendor in php? Here's how:
php-compose:
  volumes:
    vendor:/src/vendor

php-app:
  volumes:
    .:/src
    vendor:/src/vendor

volumes:
  - vendor_dir

Some speed improvements solutions http://laradock.io/documentation/#improve-speed-on-macos

I had problems with Laravel being slow on Docker for Mac like everyone else here. I looked at the possible solutions listed here but I also found some interesting information on https://blog.docker.com/2017/05/user-guided-caching-in-docker-for-mac/ and https://docs.docker.com/docker-for-mac/osxfs-caching/
My api calls were taking between 1.0 to 1.2 seconds at minimum. I decided to try the :cache option for the www volume and now the API calls take between .3 and .4 seconds. It isn't as fast as it is on our linux boxes but it is certainly usable for dev. Just wanted to throw it out there in case  someone else finds this thread as a quick option they can try.
I didn't use :cache for the mysql or mongo mounts though as I believe those systems do their own memory caching once loaded anyway so they shouldn't be hitting the hard drive much. I did try with them cached but it resulted in no increase plus I'm not 100% sure what issues it would cause anyway.
I did some testing where I made changes to the laravel/php code and instantly did the api call and the code was used so I'm pretty sure you don't have to worry too much about old code running.
YMMV but again I wanted to share because it was a quick easy fix for me. I haven't compared it to nfs but I would have to think that since the container itself has a copy of the files that it should be just as fast but hopefully others can chime in.

@MatthewDrouin - Where exactly did you add :cache? To the docker-compose.yml?

@MatthewDrouin would like to know as well.
Unfortunately docker-sync doesn't appear to make any difference in my projects. My laravel pages still take 0.8-1.5 seconds to load wether I'm using docker-compose or ./sync commands. Any ideas?

@glaesser either you configured docker-sync the wrong way ( which i highly suggest ) e.g. by missing the limitation docker-compose allows you to override volumes, e.g. see https://github.com/EugenMayer/docker-sync/issues/479 ....
or you are using opache with stat=1 so files are not read directly on bootstrap, which is pretty nonsense for development ( since you would need to restart  fpm or flush opcache cache each time you change a file to be in affect ).
We use Laravel ( lumen ) and docker-sync has an significant impact (positiv ), so there is for sure a gain, but those numbers should speak for themself: https://github.com/EugenMayer/docker-sync/wiki/4.-Performance

@EugenMayer thanks for the comment! I simply followed the laradock instructions (http://laradock.io/documentation/#improve-speed-on-macos), meaning I installed docker-sync and then ran laradock's included ./sync.sh script to start docker-sync & subsequently docker.
Laradock works fine out of the box, and docker-sync seems to install + start fine, I'm just not seeing any performance improvements in my laravel app at all - so clearly something is not right. Any suggestions on how I can I go about debugging this?
OSX 10.13.0
Laradock 0.5.8
Docker 17.09.0 CE
Docker-Sync 0.4.6

Same here. Zero change in query time. I think for the other loss in speed I'm seeing is just that laravel, through laradock, is only serving one request at a time. If I run it through homestead it serves multiple chunks of them at once. Maybe I've configured something wrong.
But again, using sync.sh I'm still seeing 2 second requests that take milliseconds when using laravel through vagrant or any other VM.

@flexgrip Following @MatthewDrouin :cache tip I added :cached to my volume parameter in docker compose:
services:
  applications:
    build:
      context: ./docker-containers/applications
    volumes:
      - ./www-workspace:/var/www:cached

@samthomson strange, I added the :cached flag into docker-compose.yml, rebuilt my docker images, but it made no difference in script execution time, still 1-1.5seconds to load any page:
    applications:
      image: tianon/true
      volumes:
        - ${APPLICATION}:/var/www:cached

Am I missing something?

@glaesser cached is for reading. Maybe you're writing?
Are there any temporary files being created at ${APPLICATION}?
You might want to use delegated for these folders.
E.g.:
applications:
  image: tianon/true
  volumes:
    - ${APPLICATION}:/var/www:cached
    - ${APPLICATION}/tmp:/var/www/tmp:delegated

Thanks for the suggestion @Vanuan, I'm def. reading, i.e. just rendering standard laravel views that take <0.1s to generate on nginx/mac, but 1-1.5s with nginx/laradock. I tried your suggestion anyways but unfortunately it made no difference in speed.
@flexgrip where you able to try the :cached option?

:cached will not help you - you struggle with the read performance, and that one is not affected by :cached.
docker-sync will help you to go down to the speed you have with the mac native.

Just looked at the setup to help you out guys - would be good if you did not simply ignore my comment above, its all in there already.
i created https://github.com/laradock/laradock/issues/1226 which is basically what i already wrote in https://github.com/laradock/laradock/issues/353#issuecomment-340504119
Now its up to you guys to fork this repo, test what i have done there and then make a pull request.
You can also quick-test that by simply removing this line https://github.com/laradock/laradock/blob/master/docker-compose.yml#L10
Then stop docker-sync: docker-sync clean
And start it again using ./sync.sh

I would even advise, for all of you really relying on that, do not use sync.sh at , just do
Installing docker-sync once
gem install docker-sync
then for your daily tasks
docker-sync clean
to cleanup and stop your stack, start from scratch, and
docker-sync start
to start your stack. That it is, not need for a wrapper for that, it usually overcomplicates things. Use the documentation  https://github.com/EugenMayer/docker-sync/wiki - maybe more specifically https://github.com/EugenMayer/docker-sync/wiki/2.1-sync-commands

:cached will not help you - you struggle with the read performance, and that one is not affected by :cached.

Why not? https://docs.docker.com/docker-for-mac/osxfs-caching/

cached: the host’s view is authoritative
(permit delays before updates on the host appear in the container)

So it is specifically to improve the read performance (mac -> virtual machine -> container).
Does laradock override the :cached option in some way so it is not used?

@glaesser what command do you use to start containers?
Is it docker-compose up? Or is it sync.sh? Do you have docker-compose.override.yml file?

@Vanuan :cached - sorry!. I mixed it up with delegated, which is the other side of the island. :cached could potentially help, i yet see that i never benchmarked it, since it has yet implemented very lately. I will add this to my performance tests. At least i remember people already tried a very early implementation and it was worth basically nothing.
to be honest, i would be glad if cached + delegated would fix the issue overall - and thus every need of docker-sync in general.

I'll try using docker-sync directly instead of the sync.sh script (shouldn't it be identical though?). But so far, cached or the sync.sh script are still giving be incredibly slow response times. Reading or making API get reqs seem to get served in 3 seconds average. The same requests through vagrant take milliseconds.

As of 2018 docker for mac has native support for nfs:
<EMAIL_ADDRESS>https://forums.docker.com/t/nfs-native-support/48531
https://github.com/IFSight/d4m-nfs
But I can't get it to work with laradock. Has anyone already done?

By now means this is native, you will get a cold shower :)
Beside that, there are way to many issues with that so a fear, thats still not solution ;/

Hmm perhaps I could get it to work for the mysql & the php-fpm container with adding / editing this in docker-compose.yml
volumes:
  mysql:
    driver: ${VOLUMES_DRIVER}
    driver_opts:
      type: nfs
      o: addr=host.docker.internal,rw,nolock,hard,nointr,nfsvers=3
      device: ":${DATA_PATH_HOST}"
  php-fpm:
    driver: ${VOLUMES_DRIVER}
    driver_opts:
      type: nfs
      o: addr=host.docker.internal,rw,nolock,hard,nointr,nfsvers=3
      device: ":${APP_CODE_PATH_HOST}"

and running this bash script, as described in<EMAIL_ADDRESS>#!/usr/bin/env bash

OS=`uname -s`

if [ $OS != "Darwin" ]; then
  echo "This script is OSX-only. Please do not run it on any other Unix."
  exit 1
fi

if [[ $EUID -eq 0 ]]; then
  echo "This script must NOT be run with sudo/root. Please re-run without sudo." 1>&2
  exit 1
fi

echo ""
echo " +-----------------------------+"
echo " | Setup native NFS for Docker |"
echo " +-----------------------------+"
echo ""

echo "WARNING: This script will shut down running containers."
echo ""
echo -n "Do you wish to proceed? [y]: "
read decision

if [ "$decision" != "y" ]; then
  echo "Exiting. No changes made."
  exit 1
fi

echo ""

if ! docker ps > /dev/null 2>&1 ; then
  echo "== Waiting for docker to start..."
fi

open -a Docker

while ! docker ps > /dev/null 2>&1 ; do sleep 2; done

echo "== Stopping running docker containers..."
docker-compose down > /dev/null 2>&1
docker volume prune -f > /dev/null

osascript -e 'quit app "Docker"'

echo "== Resetting folder permissions..."
U=`id -u`
G=`id -g`
sudo chown -R "$U":"$G" .

echo "== Setting up nfs..."
LINE="/Users -alldirs -mapall=$U:$G localhost"
FILE=/etc/exports
sudo cp /dev/null $FILE
grep -qF -- "$LINE" "$FILE" || sudo echo "$LINE" | sudo tee -a $FILE > /dev/null

LINE="nfs.server.mount.require_resv_port = 0"
FILE=/etc/nfs.conf
grep -qF -- "$LINE" "$FILE" || sudo echo "$LINE" | sudo tee -a $FILE > /dev/null

echo "== Restarting nfsd..."
sudo nfsd restart

echo "== Restarting docker..."
open -a Docker

while ! docker ps > /dev/null 2>&1 ; do sleep 2; done

echo ""
echo "SUCCESS! Now go run your containers 🐳"

I looks right when I inspect the volume
➜  toportal git:(master) ✗ docker volume inspect laradock_toportal_php-fpm
[
    {
        "CreatedAt": "2018-11-28T10:33:24Z",
        "Driver": "local",
        "Labels": {
            "com.docker.compose.project": "laradock_toportal",
            "com.docker.compose.version": "1.23.1",
            "com.docker.compose.volume": "php-fpm"
        },
        "Mountpoint": "/var/lib/docker/volumes/laradock_toportal_php-fpm/_data",
        "Name": "laradock_toportal_php-fpm",
        "Options": {
            "device": ":../",
            "o": "addr=host.docker.internal,rw,nolock,hard,nointr,nfsvers=3",
            "type": "nfs"
        },
        "Scope": "local"
    }
]
➜  toportal git:(master) ✗ docker volume inspect laradock_toportal_mysql
[
    {
        "CreatedAt": "2018-11-28T08:58:51Z",
        "Driver": "local",
        "Labels": {
            "com.docker.compose.project": "laradock_toportal",
            "com.docker.compose.version": "1.22.0",
            "com.docker.compose.volume": "mysql"
        },
        "Mountpoint": "/var/lib/docker/volumes/laradock_toportal_mysql/_data",
        "Name": "laradock_toportal_mysql",
        "Options": {
            "device": ":~/Code/toportal/.docker/data",
            "o": "addr=host.docker.internal,rw,nolock,hard,nointr,nfsvers=3",
            "type": "nfs"
        },
        "Scope": "local"
    }
]

But I doesn't feel like it's faster..

Hello, @ndberg
Do you resolve your issue with docker speed on the mac os? Could you say how you improve your docker speed?

Hmm I'm not shure but I don't think so. I changed back to laravel/homestead and am still working with it.


Adding a new gradient

{
"name": "Hazel",
"colors": ["#77A1D3", "#79CBCA", "#E684AE"]
},
"name": "Evening Night",
"colors": ["#005AA7", "#FFFDE4"]

Please add your changes to the gradients.json file. Make sure that is the only file you change.
Closing this for now.


[ms-connector] Read and store connector config

fixes #5740
Description
Read / set config by creating entries in microsoft_configuration_roots
Migrate to resources
Risk

Deploy Plan

The use of the resource pattern looks good to me. While I don't have the full picture, I trust your judgment on the necessity of having those two resources be distinct. Generally, a single resource CAN abstract more than one Sequelize model if it aligns with the business logic.
I strongly advocate for "resource" to remain a keyword that exclusively defines our resource pattern.

I'll refactor to use one single resource in another PR, that's probably enough for this use case.


Implement process_crosslink

What was wrong?
Fix #147
How was it fixed?
NOTE: Epoch transition rule is still subject to change in https://github.com/ethereum/eth2.0-specs/pull/492.

Implement helper functions

[x] get_current_epoch_attestations/get_previous_epoch_attestations
[x] get_attesting_validator_indices
[x] get_winning_root
[x] tests

Implement process_crosslinks

[x] process_crosslinks
[x] test

Fix

bitfield length check in get_attestation_participants

Cute Animal Picture

@djrtwo I'm going ahead to merge this. Please let me know if there's anything still needs to be corrected and I will fix them in another PR.

looks good!


Delete dead code in unit tests

Coverage remained the same at 61.965% when pulling 989428dd38a41ed1efd1e4159fe635cc391b486b on intgr:delete-dead-code into 3f9d66bd51538736485fd2b84e8c23af15c97bc8 on Netflix:master.

lgtm thanks!


[Feature Request] Formatting

Description
Formatting with identical spacing between the title and the info, like lscpu.
Example from lscpu:
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
Address sizes:       43 bits physical, 48 bits virtual
CPU(s):              12

I achieved this in Python with this over complicated function:
  neofetch = "neofetch grabbed by subprocess or the such would go here"
  neolist1 = neofetch.split('\n')
  neolist1 = ([i.split(':', 1)[0] for i in neolist1])
  width = 20
  iterator = 2
  neolist2 = neofetch.split('\n')[1:-2]
  neolist2 = ([i.split(':', 1)[1] for i in neolist2])
  print(neolist1[0]  + '\n' +  neolist1[1]) ##first 2 lines
  while(iterator<len(neolist2)-2):
        line = neolist1[iterator] + ':'.ljust(width - len(neolist1[iterator])) + neolist2[iterator]
        print(line)
        iterator+=1

This is the only workaround I have currently (probably due to my awful coding skills), it would be ideal to have this built into neofetch.

The info system we currently have cannot accommodate, I think. But you can set it manually.
e.g.
print_info() {
    info "Shell     " shell
    info "Resolution" resolution
    info "DE        " de
    info "WM        " wm
    info "WM Theme  " wm_theme
}

and it'll show up properly.

I may be able to add alignment to the current info system. Will look into it.


 This is more user friendly and also solves the purpose

added the translation keys

added the translation keys

Conflicts...

added the translation keys

Conflicts...

fixed :+1:

Should there be a ? at the end of the translation sentence

@jamesql i added the ? in the react component itself as i couldn't understand how do interpolate 😅

@amitojsingh366 Can you please merge this? As there are conflicts every time a translation file is updated.... And i need to fix them

@amitojsingh366 Can you please merge this? As there are conflicts every time a translation file is updated.... And i need to fix them

Unfortunately not many people like this idea so ill be closing this


Ship map results in a Error (null) message

When editing a ship in the plugins and clicking on "Ship Map" will open a screen with the following message in the top left corner "Error
Cannot read properties of null (reading 'useMemo')"
Must close client and reload to exit view (escape button and reload does not help).
Screenshots

Additional context
Running Windows 10 on latest Thorium version: 1.0.0-alpha.11

I believe this has been fixed in the develop branch (though not the latest alpha)


code completion for notify should not have ensure

From:
https://github.com/lingua-pupuli/puppet-editor-syntax/issues/5
Originally created by @TJM

What Versions are you running?
Editor Name and Version: VSCode 1.26.1
Theme: (dark?)
Document: test.pp
What You Are Seeing?
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'ensure' (file: /etc/puppetlabs/code/environments/production/site/profile/manifests/test.pp, line: 106) on Notify[testing]
What is Expected?
the message I tried to notify out
How Did You Get This To Happen? (Steps to Reproduce)
in a puppet file type "notify" and hit "tab" when the code completion dialog comes up... resulting output is:
notify { 'title':
  ensure => 'present'
}

The "ensure" parameter is not valid.

This is indeed a bug in PES.
https://github.com/lingua-pupuli/puppet-editor-services/blob/9b19f6b6b576b1d0bdc7d56ff8971f60b171862a/lib/puppet-languageserver/manifest/completion_provider.rb
This naively adds ensure.  We have information in the object cache now to know which resource properties are required, so we could just populate those now.


[2.x] Tenant & Domains timestamps

Why does tenants & domains database tables doesn't have created_at & updated_at columns? This information could be very useful.

Hmm, good point. I agree, I'll add timestamps.

https://github.com/stancl/tenancy/commit/6b103cd2cb8a92c87a061890326e8c3b3f4f9a8a

@antonkomarev Actually, this is a bit harder than just making the models use the timestamps. The data should be consistent in all storage drivers, so this functionality should be handled by the TenantManager. I will add this in a future release.

This is relatively easy to implement using TenantManger hooks, so it can be implemented easily in the app. But since it's not a big maintenance burden and it can be useful to have a general implementation, I'll make this part of the package as an opt-in Feature.


Type inconsistency in 'private-route' address-prefix.

The type of 'var.address_space' is string and the type of data.azurerm_virtual_network.vnet_data[count.index].address_space is list, which results in an error.
# ====================== Private RT =========================== #
resource "azurerm_route" "private-route" {
  count               = var.private_network ? 1 : 0
  address_prefix      = var.vnet_name == null ? var.address_space : data.azurerm_virtual_network.vnet_data[count.index].address_space
  name                = "${var.prefix}-internal-rt"
  next_hop_type       = "VnetLocal"

Private RT is using for private network, address_prefix is taken from vnet resource .
We have two options:

from the existing vnet-> data.azurerm_virtual_network.vnet_data[count.index].address_space using vnet_data resource
from var var.address_space

I tested the two cases, did not got any error


Remove kr_easter_egg

Since pipenv is an official PyPA project, and is recommended by packaging.python.org, it should not discriminate against or promote any specific packages, since that is unprofessional and may be discouraging to some (i.e. yours truly).

Just curious, why does the submitter matter?

FYI: https://github.com/pypa/pipenv/commit/9a0aceee2f334b624f56c6b20ebeace4a8dcbeb9


Add autocomplete phrase

I added security.protection.delete as seen in the code change, it seems simple but I don't know if I did it properly.
Signed-off-by: Eric Wolf<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

@19wolf you need to include Signed-off-by: Firstname Lastname <email> in your commit message (per CONTRIBUTING.md)

Signed-off-by: Eric Wolf<EMAIL_ADDRESS>

Updated


Error facebook video downloading

root$ youtube-dl 'https://www.facebook.com/3dfirstaid/videos/1066536763356764/' --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'https://www.facebook.com/3dfirstaid/videos/1066536763356764/', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.10.18
[debug] Python version 2.7.6 - Linux-3.14.32-xxxx-grs-ipv6-64-x86_64-with-Ubuntu-14.04-trusty
[debug] exe versions: avconv 11.3-6, avprobe 11.3-6, ffmpeg N-74748-gbaeb8f5, ffprobe N-74748-gbaeb8f5, rtmpdump 2.4
[debug] Proxy map: {}
[facebook]<PHONE_NUMBER>356764: Downloading webpage
ERROR: An extractor error has occured. (caused by KeyError(0,)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 291, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/facebook.py", line 145, in _real_extract
video_data = params['video_data'][0]
KeyError: 0
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 661, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 297, in extract
raise ExtractorError('An extractor error has occured.', cause=e)
ExtractorError: An extractor error has occured. (caused by KeyError(0,)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

This issue is already fixed and will be available in the next version of youtube-dl.


Add license to package.json. Correct HTTP headers.

Signed-off-by<EMAIL_ADDRESS>

LGTM!


Update swift-tools-support-core

Fix for https://github.com/marinofelipe/swift-package-info/issues/27.

Thanks for your Pull Request @fritzfr! I'm merging it!


chore(vendor): update @lightbasenl/backend

This PR is created by sync and will be force-pushed daily. Overwriting any manual changes done to this PR.

chore(deps): update dependencies (lightbasenl/platform-components#1256) (lightbasenl/platform-components@9f50687d82afbbc742c96eea0f7c0b953fdb0023)
feat(auth): implement impersonate sessions (lightbasenl/platform-components@79e95a7ac3e6b3b861b88ae977f38f73d0f6768c)

🚀


Rya 135 collection name

Description

What Changed?

Merging existing content into master.  Already reviewed and merged into 3.x

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/780/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/781/Build result: FAILURE[...truncated 92.71 MB...][INFO] ------------------------------------------------------------------------[INFO] Total time: 01:06 h[INFO] Finished at: 2018-10-01T17:56:20+00:00[INFO] Final Memory: 418M/2808M[INFO] ------------------------------------------------------------------------Waiting for Jenkins to finish collecting data[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project rya.kafka.connect.mongo: Compilation failure[ERROR] /home/jenkins/jenkins-slave/workspace/incubator-rya-master-with-optionals-pull-requests/extras/kafka.connect/mongo/src/main/java/org/apache/rya/kafka/connect/mongo/MongoRyaSinkTask.java:[106,18] cannot find symbol[ERROR] symbol:   method setMongoDBName(java.lang.String)[ERROR] location: variable ryaConfig of type org.apache.rya.mongodb.MongoDBRdfConfiguration[ERROR] -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :rya.kafka.connect.mongochannel stoppedSetting status of c7406d70d512334216923eaab6c55ea1f1a568eb to FAILURE with url https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/781/ and message: 'FAILURE 'Using context: Jenkins: clean package -Pgeoindexing

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-rya-master-with-optionals-pull-requests/786/Failed Tests: 3incubator-rya-master-with-optionals-pull-requests/org.apache.rya:rya.prospector: 3org.apache.rya.prospector.mr.ProspectorTest.testCountorg.apache.rya.prospector.service.ProspectorServiceEvalStatsDAOTest.testCountorg.apache.rya.prospector.service.ProspectorServiceEvalStatsDAOTest.testNoAuthsCount


[BUG]: drizzle-kit introspect generates CURRENT_TIMESTAMP without sql operator on date column

What version of drizzle-orm are you using?
0.33.0
What version of drizzle-kit are you using?
0.24.2
Describe the Bug
When I run drizzle-kit introspect, generated schema.ts is broken on the date type column because CURRENT_TIMESTAMP is not quoted with sql operator.
// broken
export const metrics = pgTable("metrics", {
	date: date("date").default(CURRENT_TIMESTAMP).notNull(),
})

// expected
export const metrics = pgTable("metrics", {
	date: date("date").default(sql`CURRENT_TIMESTAMP`).notNull(),
})

Only occurs on the date column, not on timestamp columns.
Expected behavior
Generate this instead:
sql`CURRENT_TIMESTAMP`

Environment & setup
Using pg v8.12.0

Was fixed in<EMAIL_ADDRESS>


Replacing duoshuo with GitHub Comments

Inspired by http://donw.io/post/github-comments/.
I add a github comments prototype in my blog theme. If nico add a official version, i think it's very useful when using nico to build gh-pages.

Looks good. PR is welcome.

Simply read a github issue id/url from the meta of post, so we can use the id/url to fetch comments in themes.
I will open a PR in the nico one theme as soon as possible.

Already created a PR to the one theme.


queue_specific_queue is missing its do_push vtable entry

Also reorder all vtable entries to be in the same order (push, invoke,
wakeup).
Reenable dispatch_context_for_key.
SR: SR-4039

@swift-ci please test


Package `mode-compile-2.29' is unavailable

When I installed kibit-mode via package-install :
Package `mode-compile-2.29' is unavailable

Since mode-compile is not available in http://melpa.org/#/ .

I can confirm this error.

see milkypostman/melpa#2824


set kubelet defaults for --cgroups-per-qos &  --enforce-node-allocatable

What this PR does / why we need it:
This PR fixes the following kubelet error discussed here: https://github.com/Azure/acs-engine/issues/2263
Warning  FailedNodeAllocatableEnforcement  34s (x5787 over 4d)  kubelet, k8s-agent-41758893-0  Failed to update Node Allocatable Limits "": failed to set supported cgroup subsystems for cgroup : Failed to set config for supported subsystems : failed to write<PHONE_NUMBER>12 to memory.limit_in_bytes: write /var/lib/docker/overlay2/fe259a690a2ff4ec750072fe76a64af2c85acfeb2ff4ac1752a245e2503896af/merged/sys/fs/cgroup/memory/memory.limit_in_bytes: invalid argument

@lachie83 are you able to weigh in on any gotchas w/ statically setting --cgroups-per-qos=true and --enforce-node-allocatable=pods for all built clusters?

After doing some further reading, this change looks to be idiomatic with current defaults (1.8 and 1.9). I'm 👍 with this change.

@yastij Are you speaking to the Windows concern? It looks to me like our Windows build script is producing images that explicitly override the defaults for Linux in this PR. @JiangtianLi to confirm

@jackfrancis cgroups-per-qos doesn't apply to windows kubelet.

enforce-node-allocatable is associated with cgroups-per-qos.

Thanks @JiangtianLi, we'll proceed with this PR w/ the understanding that there is no Windows impact.
Though it would be nice to figure out why those references are here:
https://github.com/Azure/acs-engine/blob/master/parts/k8s/kuberneteswindowssetup.ps1#L288

@jackfrancis --cgroups-per-qos & --enforce-node-allocatable is by default true in 1.6 (maybe 1.7).

@JiangtianLi that's true, but the line in the windows powershell script is explicitly setting it to false

@jackfrancis Correct. For windows kubelet, if we don't explicitly set to false, for some k8s version, it will be true and it doesn't apply to windows.

@jackfrancis - I was speaking about this change, not the script


Add "search_url" and collection type to theme-predictive-search

Purpose
The goal of this PR is to add an optional parameter when querying the predictive search suggestion. Currently, it is always default to /search/suggest.json. This would open allow international stores to use in their native languages. Example: /ja/search.suggest.json (reference: https://github.com/Shopify/debut/issues/1705)
I'm also adding "collection" type to be supported.
Approach

Add optional search_url to the original config parameter when we instantiate new PredictiveSearchComponent.
Add optional searchUrl to the request function. At first, I wanted to put it at the end of the list of parameters, but it looked strange after the onError function callback. The best solution would be converting into ES6 and use default values

If nothing is put in the search_url options, it would default to /search/suggest.json

Add PredictiveSearch.TYPES.COLLECTION: "collection" to support collection type

Testing

Run yarn link from this branch for both theme-predictive-search-component and theme-predictive-search folders.
From the theme repo, open the branch and run yarn link "@shopify/theme-predictive-search-component" and yarn link "@shopify/theme-predictive-search"
In your theme, create a new instance of predictive search with the new search_url parameter. Example:

  const searchDataConfig = {
      search_url: "/ja/search.suggest.json",
      resources: {
        type: [PredictiveSearch.TYPES.PRODUCT, 'collection'],
        limit: 4,
        options: {
          unavailable_products: PredictiveSearch.UNAVAILABLE_PRODUCTS.LAST,
          fields: [
            PredictiveSearch.FIELDS.TITLE,
            PredictiveSearch.FIELDS.VENDOR,
            PredictiveSearch.FIELDS.PRODUCT_TYPE,
            PredictiveSearch.FIELDS.VARIANTS_TITLE,
          ],
        },
      },
    };

    this.predictiveSearchComponent = new PredictiveSearchComponent({
      selectors: {
        input: selectors.input,
        reset: selectors.clear,
        result: selectors.mount,
      },
      // ...
      PredictiveSearchAPIConfig: searchDataConfig,
    });

this is related to #139


Support try from anyhow::Error to carli::error::Error.

The following checks have been done.

[X] I could not find another enhancement request that covers what I need.
[X] This request does not cover existing functionality.

What existing feature needs to be enhanced?
The ability to convert into carli::error::Error.
What problem is being solved?
Supporting ? operator conversions from anyhow::Error to carli::error::Error.
How would you like to see this problem solved?
Implement From<anyhow::Error> for Error.
Some additional context.

anyhow::Error

I plan on modifying From<T> for Error to support all std::error::Error implementations, so unfortunately this cannot be done until Rust supports specialization.


Add description for watermark transparency

I am closing this PR since the README is updated.

Please refer to https://github.com/elsa-lab/NTHUthesis#adjusting-watermark-opacity


how i can change colore ?

Hi, I just started with GOOI and checked the main.lua and saw the button can change color, but in the wiki there is no indication and when I try myself, there is no change.
If anyone knows how to change colors with GOOI, that would be very helpful. 😊
Thank you ! 😀

Also, Gooi makes my mobile game laggy, I just used buttons and when I remove them there is no lag.
The lag I'm experiencing is due to the Gooi button, if you have any tips on how to optimize Gooi, that would be helpful too.
Sorry for the inconvenience 😣


Migrate to the HL7 official validator

Ref: https://github.com/hl7au/au-fhir-core-inferno/issues/110

Migrate to the official HL7 validator by these steps: https://github.com/inferno-framework/us-core-test-kit/pull/168/files

Notes:

Changes do not include any work on the DevOps side. Works only on the local environment right now (2024-06-13)
After the merge you should regenerate tests to actualize suite files

https://github.com/inferno-framework/inferno-core/tree/main/validator

Use an old name in the docker-compose file;
Use .env variable for the tx server URL;
Update documentation to keep the correct link to the validator UI;
Delete prev validator UI from the Terraform;
Set tx server URL variable in terraform.


feat: expose commitment computation using Grumpkin elements (PROOF-887)

Rationale for this change
In an effort to support the Grumpkin curve this PR exposes computing commitments using Grumpkin elements. The Grumpkin curve forms a cycle with the bn254 curve. Its base field is the scalar field of the bn254 curve.
What changes are included in this PR?

Methods to support computing Pedersen commitments using Grumpkin elements are added.
Grumpkin element encodings are added.
A multiexp handle is added for Grumpkin.

Are these changes tested?
Yes

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


Multiple pods per job

Is your feature request related to a problem? Please describe.
I was recently testing armada job services and had a question: the API currently rejects a JobSubmitRequestItem when more than one pod is specified with the rationale presented in the code here.
This seems to imply the need at present to run pods as separate jobs and coordinate service discovery across jobs, but adds a complication: services are named armada-<job-id>-<pod-index>-<service-type>  but job id is a value that is not known at submission time. There are several ways to work around this to find the job id at runtime when pods are all running under separate job ids, but if I had the choice my preference would be to run multiple pod specs within the same job so that service discovery can be done in the way that the APIs seem to be suggesting that I do it.
The need to do out of band k8s lookups to find other "gang members" is not ideal because it 1) adds some level of load to the executor cluster k8s API where the gang is running, and 2) adds a small amount of complexity to gang application code to perform the out of band k8s lookup. All of this is to just find the job id to form a service name, and perform a DNS lookup once formed. If multiple pods could be submitted within the same JobSubmitRequestItem, the out of band k8s lookup wouldn't be necessary since each pod could use its own job id for service discovery, thus skipping directly to the DNS lookup. This way there wouldn't be any load or code complexity induced by out of band k8s lookup.
Describe the solution you'd like
The solution I would like is to submit multiple pod specs in a single JobSubmitRequestItem. Are there any roadmap plans for supporting multiple podSpecs per job? The comment in code I linked to above seems to express concern about ingress setup when multiple pods are part of the same job?
Describe alternatives you've considered
Another alternative I have considered is to write my own service controller that will watch pods and create services which use gang id instead of job id, since every member of the gang knows this value.
┆Issue is synchronized with this Jira Task by Unito

@jpoler thank you for this detailed feature request! This is not currently on the 2023 roadmap, but it is a very interesting idea. Do you have thoughts about what sort of API you'd like to see here?

FYI - more info on the above (per @samclark): we had basic gang scheduling via the use of the PodSpecs property. This never worked very well and was never used in production. Because it was a breaking API change the property was left but it's use was restricted to a single pod spec in the array


[Sema] Fix an issue with the ordering of effects checking and actor isolation checking.

Effects checking for async needs actor isolation to have been computed, but currently effects checking happens first for initializers expressions. This change moves effects checking for initializer expressions to the primary decl checker, after the actor isolation checker runs. This change also fixes an issue where the actor isolation checker would walk into the bodies of sending closures when computing the required isolation of a default initializer expression.
Resolves: https://github.com/swiftlang/swift/issues/73892

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test


Add average transfer speed info to history

beta code sample, compiles + shows the result
not sure though about the text format "9900.999" of "id/sync_history_list_view_transfer_speed"

hope you can review and merge


version: 2.4.0

New argument
New scripts

Waiting for https://github.com/confluentinc/confluent-kafka-python/issues/1842


Create TimedOut

Hi everybody, because I don't have enough space in my local environment, I changed the openshift_parameters.yaml, and I have one master and one node, and set the docker volume size of both master and node to 10G.
and when I execute below command:
heat stack-create my-openshift -t 180 \
-e openshift_parameters.yaml \
-f openshift-on-openstack/openshift.yaml

after 3 hour, the Create TimedOut in infra_host section appears.
please help me to understand what is my problem.

Hi, changing volume_size is fine. If it hangs in infra_host, most probably cloud-init didn't failed on infra node (and no notification has been sent back), could you ssh to the infra host and check /var/log/cloud-init.log if there is a hint?

Closing this, if the problem still occurs please reopen (more information like /var/log/cloud-init.log will be needed).


Tutorial improvements

Check changes carefully before accepting the pull request.

Codecov Report

Merging #6 (e5e21cf) into master (f461026) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #6   +/-   ##
=======================================
  Coverage   98.81%   98.81%
=======================================
  Files           4        4
  Lines         253      253
=======================================
  Hits          250      250
  Misses          3        3

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 f461026...e5e21cf. Read the comment docs.


UP-4431 Search auto-suggest defaults to portlet list

https://issues.jasig.org/browse/UP-4431
Pre-populating the search auto-suggest with the portlet list gives a much better user experience.  Suggest including in uPortal 4.2.0.

Coverage decreased (-0.03%) to 22.81% when pulling 2b21fa43e68c1af9399ac20de636149cf8b4c50c on UP4431SearchAutosuggestPortletList into 6619b61023aaaa86b8b4cbd0327af773130fa08f on master.


Equirectangular images are not shown in 360 viewer

As I remember it used to show equirectangular images in 360 viewer.
I am not sure what I am missing now or something changed?

Equirectangular images are still shown in the viewer and you can pan around with SHIFT+DRAG. If you are not seeing them, it could be that the reconstruction failed. Let's follow this in #203


Update v2-compatibility.md on which types are recognized as parameter types.

/lgtm
Thank you for the fix!

/approve


Add python3 support

Hey,
It seems sys.maxint is the only thing that should be fixed to support python3.
Cheers

Nice try.
Thank you guy， i would update the README these days for python3 supported.


[FIX] Fixed responsiveness of News Carousel

So I have fixed the responsiveness of news carousel section. Also I have made styles consistent.
First fix was making the styles consistent and you can check the results below:-
Before

After

Second fix was making the section responsive. Earlier the text flowed outside the image. You can check the results below:-

Palanikannan1437 You can check it now.

@muneeb-i-khan
Awesome job on explaining the PR with all the screenshots and gifs 🙏!
Please refrain from changing the default styles of our component drastically(height, width, etc)...it was by design and well thought of by our contributors, please try to fix the responsiveness while keeping the current styles intact! Thank you! 😊

Okay I will try it👍

@Palanikannan1437 I restored all the default styles at places where it was possible. Tell me if there are any other changes required.

This fixes the following issue:- https://github.com/RocketChat/RC4Community/issues/205

Is it fine now or I need to make more changes? @Palanikannan1437

Hey, it still doesn't keep the original changes... this was closed in this
Would love to see your contributions on the other open issues!! Thank you 🚀🚀


Support searching in section headers by default

I find it a bit cumbersome to type h: in order to search for a keybinding related to a specific app.
Can it be done so you search in both the section titles and items by default?

I very much agree with you.
However, more than a year later, I'm still struggling to find a good UX to combine searching in both section headers and items. For example, how should we prioritize search results when there exists a header and item with the same text? If the section header has many constituent rows, it would drown out the rest of the results that are not in the same section.
Two approaches I can think of:

Toggle between showing matches of sections headers (and their items) and non-sections with a hotkey
Prioritize showing matches of section headers over non-sections


Grimoire.js + glTF Loader does not support glTF 1.1.

I tried the glTF 1.1 sample with some glTF Loader.
https://github.com/cx20/gltf-test#gltf-11-tutorial-models
https://cx20.github.io/gltf-test/
Related: https://github.com/javagl/JglTF/issues/10#issuecomment-269810809
I would like each library to be all green.

Should we support glTF 1.1 yet?

glTF 1.1 has been renamed to 2.0.
Since there is no model of glTF1.1 also in the following repository, support of glTF1.1 is unnecessary.
https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/1.0


weird shape when resize the button!

hi
when i change the size to 50x50 it's getting a weird shape...
why that happens?

Thanks!
<jp.co.recruit_lifestyle.android.widget.PlayPauseButton
        android:layout_width="50dp"
        android:layout_height="50dp"
        android:layout_centerInParent="true"
        android:id="@+id/main_play_pause_button"
        />

Sorry, I do not understand about it.
Please give more information or sample code, project.


Rule idea: disallow async-await function in server-side code.

While async-await functions are quite handy on the client side, their usage could bring unexpected behavior to server-side code.

Thanks for the suggestions :)
We don't know whether code is going to run on the server or on the client, so this is not possible
with the current architecture. I want to keep that complexity out of the plugin.
See https://github.com/dferber90/eslint-plugin-meteor/issues/259#issuecomment-228960339 for a more detailed explanation.


HADOOP-16794. S3A reverts KMS encryption to the bucket's default KMS …

1875

 Quality gate: Failed
24 Issues

 1 Vulnerabilities
 23 Code issues

Details

 Quality gate: Failed
23 Issues

 1 Vulnerabilities
 22 Code issues

Details


Storage-file-datalake tests failing

Test run - https://dev.azure.com/azure-sdk/internal/_build/results?buildId=463587&view=logs&j=bbd7d436-e05d-51a8-99a8-0701dc9dffeb&t=b35bd286-0ff8-5789-8141-60cce3239968

Probably happening due to the resources not being created with the arm-template test-resources.json
@jeremymeng  @ljian3377

I created the pipeline recently. But haven't got the time to dig in the ARM documentation to get the ARM template right for storage-file-datalake.


fix: analyze implicit cast because reset can't reset implicit cast

Proposed changes
analyze implicit cast because reset can't reset implicit cast

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Fix for show vindexes, not picking the correct stat

Description
Fixes small bug where is show vitess_tablets is not fetching tablet type from the right source.

LGTM


Does anyone have the opcode for 6.1?

{
"C2S_ActionRequest": "0x00b8",
"C2S_ActionRequestGroundTargeted": "0x00b8",
"S2C_ActionEffect01": "0x021b",
"S2C_ActionEffect08": "0x030e",
"S2C_ActionEffect16": "0x0153",
"S2C_ActionEffect24": "0x00e1",
"S2C_ActionEffect32": "0x0356",
"S2C_ActorCast": "0x006f",
"S2C_ActorControl": "0x02e7",
"S2C_ActorControlSelf": "0x028f",
"S2C_EffectResult5": "0x02e7",
"S2C_EffectResult6": "0x02e7",
"S2C_EffectResult6Basic": "0x02e7",
"Server_IpRange": "<IP_ADDRESS>/0",
"Server_PortRange": "1-65535"
}

These are the ones I found that seem to be working for me

Working for me, thx!


Fix CSS bug with status message

This styling regressed in https://github.com/studentinsights/studentinsights/pull/2274

selfie


ngspice: 34 -> 36

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@Luz if none of the maintainers respond, feel free to ping me in a few days and I'll merge this.


Keep-alive upstream requests

Being able to keep-alive the connections to the upstream services while proxying.

Any updates on when this might be ready? It seems like an important feature from the performance perspective. Is this something that can be contributed by a 3rd party?

Will show up in 0.9 and it's related to #1225

Awesome! Do you have an ETA for 0.9?

Currently working on it. We need to merge refactor/cli into next first, and then we can start working on this issue.

Any update on this #1225 is closed now.

See #1587

part of 0.10, waitng to be released. Avaialble in the RC for 0.10. Closing this


Move to a SCSS based model for CSS

This patch refactors the CSS of the site to be based on Jekyll's built-in SASS/SCSS compilation system. Nothing should change on the front-end as a result of this change.
On the upside, we'll end up with a single minified CSS file at the end of the day in the head. We'll also be able to take advantage of SCSS shorthand in the future. I also cut out some crufty CSS files along the way.

No objections. I merged things a bit out of orders from my phone, so this conflicts now.

@Carreau, I believe this conflict has been resolved.

I like scss (and even more sass). I think it is useful to use it.
I don't know if bundling bootstrap together with custom styles is a good idea though:

when it is standalone (and everything is configured properly) it can be cached by browsers more efficiently
we do not end up mixing styles that have different licences together in a single file

Bundling other common styles is an improvement

I bundled bootstrap here as an intermediate step. Provided this merged, a follow on goal I have is to trim down the bootstrap file that now includes 100% of the framework to only the parts that the site actualy uses. Once that next step is taken, we will significantly reduce the amount of CSS packaged with every page, helping to speed page load at the low low price of cutting cruft.

Per @krassowski's request, I've broken out the bootstrap CSS into a separate file.

Thanks @krassowski. Once this ticket gets merged, it will be a lot easier to address other CSS bugs. I'll also look to trim down the bootstrap file to only the CSS classes that are actually in use on the site. I think that will drive down the file sizes even further.

I might be missing it, but I don't think I can merge. I see something like this on approved PRs.

Ok, sorry about all of that. I though you had merge privileges, so I bumped you and @krassowski permissions.
I'll do the same with @jupyter/designers so that they all can merge.


Support Ember Changeset v4

Ember Changeset v4, which has been released recently, should be supported. It is currently locked to v3: https://github.com/kaliber5/ember-bootstrap-changeset-validations/blob/d11f9cf84c467f9bcfa001763fb13613f50244d1/package.json#L31
We might be able to widen the SemVer range to allow v3 and v4 at the same time. That would be the best solution in my perspective. When doing so we should ensure that we run our tests for both versions.
If that is not possible, we should drop support for v3 and release a new major.

@jelhan we have a major update scheduled for this addon. Which is needed to support the upcomming release of ember-bootstrap 5.1. So do we want to cut another major a bit later, for this issue? Or do you have time to work on this in the near future? (I won't)

Thinking about this again, I guess it is not a good idea to require users to update to ember-changeset-validations v4 at the same time as requiring ember-bootstrap v5, and fixing the BsForm class issue for 5.1, as that would impose greater upgrade pain. So I'll release what we have now, and when we choose to drop ember-changeset-validations v3 in favor of v4, we can just do another major bump. It's not that we run out of version numbers... :wink:

I now force v4 via a package resolution option, but it would be nice if I could drop that.

ember try:each
Error!
Error: Cannot copy '../../../errno/cli.js' to a subdirectory of itself, '../../../errno/cli.js'.
Error: Cannot copy '../../../errno/cli.js' to a subdirectory of itself, '../../../errno/cli.js'.
    at /Users/bas/Sandbox/ember-bootstrap-changeset-validations/node_modules/ember-try/node_modules/fs-extra/lib/copy/copy.js:210:21
    at FSReqCallback.oncomplete (node:fs:188:23)

Which seems fixed via one of; https://github.com/jprichardson/node-fs-extra/issues?q=is%3Aissue+to+a+subdirectory+of+itself+is%3Aclosed
however setting a resolution to "10.1.0" (latest) does not fix it... (on MacOS).

Support for Ember Changeset v4 has landed in v5.0.0.


Add Contact us label to conversation icon on help and about app pages

Type

[ ] Bug fix
[ ] New feature
[x] Improvement to existing feature

Related JIRA Issue(s)
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1455
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1454
Description
A clickable text link needs to appear in the same style as in other apps in the Help and About us page
Deployment URL
http://contact-icon-label.review.ensembl.org/
Views affected
Help and About us page
Other effects
NA

[ ] I have checked any requirements for Google Analytics
[ ] I have created any required tests
[ ] The PR has as its final commit a WASM/JS update commit if any Rust files were updated.

Possible complications
NA

We noticed that when you switch between the help page and the about page, the communication icon shifts vertically. The reason is that the app bar on the help page has a height set to 86 px, whereas on the about page (an on other pages as well) it is set to 80px. Could you change the height of the app bar on the help page to 80px as well?

Another thing we noticed is that on the home page the help and communication icons are positioned a bit lower than on the rest of the pages. Andrea says that the vertical position of these icons should be the same on all pages. Could you take a look at that as well, or do you think it should go in a separate ticket?

Another thing we noticed is that on the home page the help and communication icons are positioned a bit lower than on the rest of the pages. Andrea says that the vertical position of these icons should be the same on all pages. Could you take a look at that as well, or do you think it should go in a separate ticket?

Could you please check if the vertical heights are ok?

Help page is great. For the home page, I think I am measuring a 3-pixel difference (the buttons start 3 pixels lower on the home page than on the species selector page):

Hi @azangru I think it is the problem with species selector page species lozenges margin. Can this be done in a design review ticket?


MS max charge in meta json

Hi Niels and Yasset @nielshulstaert @ypriverol
When I convert a thermo raw file to mgf, the result meta.json file contains {"accession":"PRIDE:0000473","cvLabel":"PRIDE","name":"MS max charge","value":"2"}.
However, the charge values in mgf contains 3+ and 4+. Is there anything that I get it wrong or this is a real issue?
Thanks
Da
Below is part of mgf file:
BEGIN IONS
TITLE=controllerType=0 controllerNumber=1 scan=4
SCANS=4
RTINSECONDS=0.555008863
PEPMASS=367.069610595703
CHARGE=3+
102.9147415<PHONE_NUMBER>234
103.0570450 1049.8944091797
111.1171875 1026.8439941406
120.2493973<PHONE_NUMBER>344
124.1555634<PHONE_NUMBER>813
135.8387756<PHONE_NUMBER>883

Hi Da, indeed there's a bug in the code. It should be fixed in the latest release (v1.1.7). Thanks for pointing this out!


update code to interact with parse server

add api keys and everything else needed for the app to interact with the parse server

done, also tested successfully. Repo updated.


Google Auth app and system generated codes are different

I entered secret in google authenticator app. It generates random code in every few seconds. But, when I match with my code it's different.
$this->load->library('GoogleAuthenticator');
$oneCode = $this->googleauthenticator->getCode($secret);

$oneCode is different than I see in google app.

Most often it's a time problem, so the clock is not synchronized between the mobile phone and the server. Please check if both systems have the same time, then they should generate the same code (with the same secret used).

that is a problem indid. When the secret is long(maybe morethan 16length),The code is different from google app.


Update screenshot in the Metrics doc for Kubeflow 0.5 UI

https://github.com/kubeflow/website/blob/master/content/docs/pipelines/metrics/pipelines-metrics.md
(Part of issue https://github.com/kubeflow/website/issues/505.)

/assign


TypeError: t.indexOf is not a function

Describe the bug
A money property passed createMoneyIntlFormatter causes an exception.
To Reproduce

Create a money object.
Pass it into createMoneyIntlFormatter().format()

The current behavior
Uncaught TypeError: t.indexOf is not a function
at o (number.ts?3110:111)
at eval (money.ts?a69b:18)
at eval (money.ts?a69b:36)
at UITerminalItem.render (index.tsx?8387:61)

Hi, thanks for the bug, can't reproduce by myself, needs a little bit more information

Could you provide a snippet of code?
And also, please share versions of the libs

Closed, because no additional info was provided


Only upload results if there are any

This will need to be merged after https://github.com/github/vscode-codeql/pull/2736 has shipped (has been included in a released version of the extension)

Code change LGTM but (as posted on internal issue) we might need to look at the API methods and make sure they'll accept us calling them without uploading the artefact.

Abandoning this change for now until we make some changes in the monolith that will help us have more correct data.


[test](data type)

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall


Run
  git config --global user.email<EMAIL_ADDRESS>  git config --global user.name "Your Name"
to set your account's default identity.

https://travis-ci.org/GoogleCloudPlatform/google-cloud-node/jobs/163785024#L1085

Windows probs:
exec: internal error
C:\projects\google-cloud-node\scripts\helpers.js:260
  if (response.code) {
              ^
TypeError: Cannot read property 'code' of null

I think I fixed it with my last commit.

Dang, must be a quirk of the submodule..? So there's already a line that tries to set the user, can we just add the --global flag to that?
https://github.com/GoogleCloudPlatform/google-cloud-node/blob/master/scripts/helpers.js#L318

Woops, didn't see that. Added the global flag there.


Warning: div was passed a style object that has previously been mutated

Hi.
We started having this react warning with react-slider, and I am not sure what is causing it, as our implementation has not changed, neither did we update something, and it was working fine with the current react version (0.14.1)
Any ideas? Is it rather a problem on our side, or is it something to be considered within react-slider?
Our implementation/usage:
<ReactSlider className='RangeSlider'
    value={[this.state.rangeStart, this.state.rangeEnd]}
    min={this.props.min}
    max={this.props.max}
    withBars={true}
    onChange={onSliderChange}
    onAfterChange={this.setFilterWithApi}
    snapDragDisabled={false}
    pearling={false}
    minDistance={this.props.stepSize}
    step={this.props.stepSize}
>

</ReactSlider>

The full warning
Warning: `div` was passed a style object that has previously been mutated.
Mutating `style` is deprecated. Consider cloning it beforehand.
Check the `render` of `ReactSlider`.
Previous style: {position: "absolute", willChange: "", left: 0, right: NaN}.
 React seems to have a problem with the slider's style prop containing right: NaN. Had the same problem because one of the values was undefined.

yes I do see NaNs with devtools. Hmm should have figured that it's some math operation with undefined. Thanks for the hint!

Experienced the same issue. Passing 0 instead of other falsy values solved the issue.

This issue should be fixed now that https://github.com/mpowaga/react-slider/issues/85 has been merged.


subcommand to repair slashing protection files that are corrupted

as a validator, I want corrupted files to be able to be repaired
so that I don't have to manually find and delete corrupt files.

should warn about clock skew, and once accepting the risk we can update the slashing protection files

update invalid files by default (files that can't be parsed, eg 0 sized files), values should be written to the next epoch

potentially have a -a option to update all the valid files as well

potentially require a flag to cleanup lock files, and should respect file locking by default in case someone tries to run the subcommand while teku is online.

potentially allow user to set a (future) epoch

Yep definitely should use keystore file locking for safety. I would default to listing which valets will be updated and why and requiring confirmation of that for safety. Particularly important to confirm the epoch/slot being recorded is actually safe.
Probably should default to picking values that are two epochs in the future for safety as well.

and flatly refuse to go 'below' whats in a file if it's already a valid file...

related to #3800


Listener is not invoked when transaction commit

Hi Team,
I am trying to use addcommitlistener in following way,but i am not getting events while transaction is committed.
pls let me correct.
========================================
 const transaction =  contract.createTransaction("createCar");
        const listener = (error, event) => {
           console.log("event is called................");
      if (error) {
        console.log("error========================",error);
    } else {
      console.log("event.eventName=========",event.eventName);
    }
}
const peers = network.getChannel().getEndorsers("Org1MSP");
await network.addCommitListener(listener, peers, transaction.getTransactionId());
await contract.submitTransaction('createCar' ,'CAR1112', 'Honda', 'Accord', 'Black', 'Tom' );
========================================

Also for another issue: **Getting two transaction against a insertion #580**
what key/value provided in checkpoint.json file?
===================
await contract.addContractListener(listener, {
    checkpointer: await DefaultCheckpointers.file('checkpoint.json'),
});
===================

Thanks

Calling contract.submitTransaction() submits a new transaction, with a different transaction ID to the one you created when you called contract.createTransaction(). You are never calling transaction.submit() so the transaction ID you are listening for is never submitted.
 You might just be duplicating work that is already happening.


Your dataset are all returning null values now

curl -X GET "https://wuhan-coronavirus-api.laeyoung.endpoint.ainize.ai/jhu-edu/brief" -H "accept: application/json"
{"confirmed":0,"deaths":0,"recovered":0}%

Hi, @andersot72
I think it is a kind of timing issue. This api refer 3 csv files at CSSEGISandData/COVID-19. When new date's column has been created, every cells according to the column would be 0.
I will fix it soon, thank you for reporting it 😎!

Maybe, this was caused by #9 issue.

thanks much and thanks very much for providing this, I signed up for the Ainize as well :-)

@andersot72 Oh thank you!!
Did you get a "Welcome to Ainize beta" mail?


Define cxx_library for git_fetched sources

Is using git_fetch to define a cxx_library supported? I've had trouble with adding a party dependency without simply vendoring it (which I understand is the preferred method, but is also often unpopular for open source projects). If not, I'll just vendor the third party sources that I need in my repo, but it seems to me that this would be unsatisfying for open source adoption at large.
I've seen some helpful comments on https://github.com/facebook/buck2/discussions/387, which show how http_archive has convenient options for defining sub-targets, which git_fetch misses.
Besides that, I haven't found how to easily/conveniently:

avoid having to use weird include paths
get the headers within the library to successfully include each other without patching the source

See a rather contrived example (which doesn't attempt to get a full build going, just getting the headers right for now) at https://github.com/cbarrete/buck2_git_fetch.
Any pointers would be greatly appreciated!

Two things:

git_fetch should probably also take a sub_targets argument like http_archive does, for use cases like this.
In this case, because you're cloning a repo from github (that does not use submodules!), you can just use http_archive instead as an immediate workaround for git_fetch not supporting sub targets i.e. just download https://github.com/axboe/liburing/archive/298c083d75ecde5a8833366167b3b6abff0c8d39.tar.gz instead of using git_fetch at all.

As for the headers thing, the ultimate answer is you need to read the source code, and then use a combination of a few features from cxx_library:

Use exported_headers for header files that dependent targets should be able to #include
Use headers for header files that only the built target needs, i.e. this is where private headers goes
header_namespace controls the "directory" all headers are under when setting up the compiler, i.e. header_namespace = "foo" means all headers from exported_headers and headers appear as foo/... in the source code.

exported_headers and headers also can not only take a list, but a mapping, so you can map raw source files to the right include path, i.e. something like the following:
cxx_library(
    header_namespace = "foobar",
    headers = {
      "private/test.h": ":srcdir[include/test.h]",
    },
    exported_headers = {
      "api.h": ":srcdir[include/usr/api.h]",
    },
)

would mean:

Dependent, downstream targets can include foo/api.h in order to import the public API
When compiling the cxx_library itself, the api.h header can be imported as foo/api.h just like external cases
It can also include foo/private/test.h as well, which is not exported to downstream consumers, and only available internally

Some details might be slightly off here but I think the combination of these behaviors should mostly allow you to craft the include paths to your liking.

Thanks for the detailed response. This all makes sense, I was having issues with the headers because I couldn't refer to them as sub-targets with git_fetch, but getting them via HTTP fixes that, so I guess I'll go that way for now.
It's a shame that I have to manually list out all files in the mappings (or write some starlark/bxl to automate that), but that will work for me for now, as I don't have too many dependencies at the moment.


loan.py: adding currency symbol

Change to add a currency symbol to summarize.

This looks great! Thanks for sending a PR


Retrieve mins/maxes/ranges of values from api requests to eliminate client-side calculations

closing this, this is not necessary right now


Even more compact packing of random bytes in session_id

The previous pull request was merged too quickly. I've made some improvements. More correct fix #430.

Haha😅Thank you!


operator [R] [CI] percona-server-mongodb-operator (1.10.0 1.11.0 1.12.0 1.13.0)

Signed-off-by: Natalia Marukovich<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@J0zi could you have a look at kiwi error?
`fatal: [localhost]: FAILED! => changed=true
cmd: podman pull percona/percona-server-mongodb-operator:1.13.0
delta: '0:00:00.040913'
end: '2022-10-20 09:28:32.379055'
msg: non-zero return code
rc: 125
start: '2022-10-20 09:28:32.338142'
stderr: 'Error: short-name resolution enforced but cannot prompt without a TTY'
stderr_lines:
stdout: ''
stdout_lines:
...ignoring
TASK [check_image_availability : Print err message on Kubernetes] **************
fatal: [localhost]: FAILED! => changed=false
msg: Unable to pull percona/percona-server-mongodb-operator:1.13.0, please check permissions or path.
`

/merge possible

/merge possible

/merge possible


Detects remote url from local git repo.

PR for #43
If the TargetUrl is not set then the new code determines if the solution is in a local git repository.
If so it uses the head for the SHA, and the current branch's remote for the TargetUrl.
If the current branch is detached, it looks for a branch with the current SHA as a commit, and uses that branches remote instead.
If no branches have a remote, then it doesn't set the TargetUrl and the application fails as per normal.

Looks good, thanks for this! I will make a few minor changes, but this is really nice, thanks!

Prerelease is now available on chocolatey / nuget with this feature.