Real world experiments

Hi,
thanks for sharing!
I would like to try your method with a franka panda, could you give more details w.r.t the setup?
Also, I am wandering wether the pre-trained cpkt will be available.
Bests

Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.

Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.

Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is<EMAIL_ADDRESS>，Looking forward to your reply! Thank you very much

Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

Hi,
Thank you very much for your reply and for sharing the real world code with me. This will be very helpful to me. I will repeat your experiment and refer to your method. If I could improve your code, I would share it with you and once again express my gratitude to you.
Thanks，
zcs
At 2023-07-18 19:01:32, "Julius Hietala" @.***> wrote:
Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

You may need to edit the code quite a bit to get it running, unfortunately I did not document it very well, just needed to “make it work” for my experiments in our lab setup. However all the building blocks should be there. Also please refer to the blog posts on the paper which may reveal some gotchas: @.***/learning-visual-feedback-control-for-dynamic-cloth-folding-what-the-paper-does-not-tell-you-2-3-e4a8ac72c1e1
Thanks,
Julius

On 19. Jul 2023, at 5.13, zcswdt @.***> wrote:
Hi,
Thank you very much for your reply and for sharing the real world code with me. This will be very helpful to me. I will repeat your experiment and refer to your method. If I could improve your code, I would share it with you and once again express my gratitude to you.
Thanks，
zcs
At 2023-07-18 19:01:32, "Julius Hietala" @.***> wrote:
Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641279029, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH4E7FIMWXCSCDCOASTXQ47D7ANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

Hi:
It's okay, give me your code as a reference to learn how you came up with such a good method and implemented it. My main focus is to learn from your ideas. Also, regarding the blog you mentioned in your email, I couldn't find the desired website address. How can I proceed,
Thanks,
zcs
At 2023-07-19 17:34:33, "Julius Hietala" @.***> wrote:
You may need to edit the code quite a bit to get it running, unfortunately I did not document it very well, just needed to “make it work” for my experiments in our lab setup. However all the building blocks should be there. Also please refer to the blog posts on the paper which may reveal some gotchas: @.***/learning-visual-feedback-control-for-dynamic-cloth-folding-what-the-paper-does-not-tell-you-2-3-e4a8ac72c1e1
Thanks,
Julius

On 19. Jul 2023, at 5.13, zcswdt @.***> wrote:
Hi,
Thank you very much for your reply and for sharing the real world code with me. This will be very helpful to me. I will repeat your experiment and refer to your method. If I could improve your code, I would share it with you and once again express my gratitude to you.
Thanks，
zcs
At 2023-07-18 19:01:32, "Julius Hietala" @.***> wrote:
Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641279029, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH4E7FIMWXCSCDCOASTXQ47D7ANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Sounds great!
Here’s an alternative link to my personal blog: https://www.juliushietala.com/blog https://www.juliushietala.com/blog
Julius

On 19. Jul 2023, at 14.30, zcswdt @.***> wrote:
Hi:
It's okay, give me your code as a reference to learn how you came up with such a good method and implemented it. My main focus is to learn from your ideas. Also, regarding the blog you mentioned in your email, I couldn't find the desired website address. How can I proceed,
Thanks,
zcs
At 2023-07-19 17:34:33, "Julius Hietala" @.***> wrote:
You may need to edit the code quite a bit to get it running, unfortunately I did not document it very well, just needed to “make it work” for my experiments in our lab setup. However all the building blocks should be there. Also please refer to the blog posts on the paper which may reveal some gotchas: @.***/learning-visual-feedback-control-for-dynamic-cloth-folding-what-the-paper-does-not-tell-you-2-3-e4a8ac72c1e1
Thanks,
Julius

On 19. Jul 2023, at 5.13, zcswdt @.***> wrote:
Hi,
Thank you very much for your reply and for sharing the real world code with me. This will be very helpful to me. I will repeat your experiment and refer to your method. If I could improve your code, I would share it with you and once again express my gratitude to you.
Thanks，
zcs
At 2023-07-18 19:01:32, "Julius Hietala" @.***> wrote:
Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641279029, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH4E7FIMWXCSCDCOASTXQ47D7ANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641913047, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH2RJLEEFIAQES2US7DXQ7AMVANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

You are really great. Thank you for sharing your research results with me. This will definitely make me progress quickly in the future. Your academic achievements have impressed me, and thank you for guiding me in the direction.
在 2023-07-19 19:33:39，"Julius Hietala" @.***> 写道：
Sounds great!
Here’s an alternative link to my personal blog: https://www.juliushietala.com/blog https://www.juliushietala.com/blog
Julius

On 19. Jul 2023, at 14.30, zcswdt @.***> wrote:
Hi:
It's okay, give me your code as a reference to learn how you came up with such a good method and implemented it. My main focus is to learn from your ideas. Also, regarding the blog you mentioned in your email, I couldn't find the desired website address. How can I proceed,
Thanks,
zcs
At 2023-07-19 17:34:33, "Julius Hietala" @.***> wrote:
You may need to edit the code quite a bit to get it running, unfortunately I did not document it very well, just needed to “make it work” for my experiments in our lab setup. However all the building blocks should be there. Also please refer to the blog posts on the paper which may reveal some gotchas: @.***/learning-visual-feedback-control-for-dynamic-cloth-folding-what-the-paper-does-not-tell-you-2-3-e4a8ac72c1e1
Thanks,
Julius

On 19. Jul 2023, at 5.13, zcswdt @.***> wrote:
Hi,
Thank you very much for your reply and for sharing the real world code with me. This will be very helpful to me. I will repeat your experiment and refer to your method. If I could improve your code, I would share it with you and once again express my gratitude to you.
Thanks，
zcs
At 2023-07-18 19:01:32, "Julius Hietala" @.***> wrote:
Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641279029, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH4E7FIMWXCSCDCOASTXQ47D7ANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641913047, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH2RJLEEFIAQES2US7DXQ7AMVANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Thanks, let me know how it goes!
Julius

On 19. Jul 2023, at 14.38, zcswdt @.***> wrote:
You are really great. Thank you for sharing your research results with me. This will definitely make me progress quickly in the future. Your academic achievements have impressed me, and thank you for guiding me in the direction.
在 2023-07-19 19:33:39，"Julius Hietala" @.***> 写道：
Sounds great!
Here’s an alternative link to my personal blog: https://www.juliushietala.com/blog https://www.juliushietala.com/blog
Julius

On 19. Jul 2023, at 14.30, zcswdt @.***> wrote:
Hi:
It's okay, give me your code as a reference to learn how you came up with such a good method and implemented it. My main focus is to learn from your ideas. Also, regarding the blog you mentioned in your email, I couldn't find the desired website address. How can I proceed,
Thanks,
zcs
At 2023-07-19 17:34:33, "Julius Hietala" @.***> wrote:
You may need to edit the code quite a bit to get it running, unfortunately I did not document it very well, just needed to “make it work” for my experiments in our lab setup. However all the building blocks should be there. Also please refer to the blog posts on the paper which may reveal some gotchas: @.***/learning-visual-feedback-control-for-dynamic-cloth-folding-what-the-paper-does-not-tell-you-2-3-e4a8ac72c1e1
Thanks,
Julius

On 19. Jul 2023, at 5.13, zcswdt @.***> wrote:
Hi,
Thank you very much for your reply and for sharing the real world code with me. This will be very helpful to me. I will repeat your experiment and refer to your method. If I could improve your code, I would share it with you and once again express my gratitude to you.
Thanks，
zcs
At 2023-07-18 19:01:32, "Julius Hietala" @.***> wrote:
Hi!
Sorry for the delay here!
I added you to the repo, it is not polished at all / does not have clear instructions so I won’t make it public. Let me know if you end up making a more polished version I could make public.
Thanks,
Julius

On 28. Jun 2023, at 12.09, zcswdt @.***> wrote:
Hi! Unfortunately I don't have a polished version of the real-world code available, but you can email me and I can share the code.
Hello, I have sent you an email, but unfortunately I did not receive your reply. I am not sure if the email I sent is your commonly used email! Can you share a copy of this code with me? My email is @.*** ，Looking forward to your reply! Thank you very much
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1611048724, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH46MY2G7WZVIY3J6WDXNPYFNANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641279029, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH4E7FIMWXCSCDCOASTXQ47D7ANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641913047, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH2RJLEEFIAQES2US7DXQ7AMVANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/hietalajulius/dynamic-cloth-folding/issues/2#issuecomment-1641924071, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABAOXH5HKT27QRMH3LJNX2LXQ7BMVANCNFSM6AAAAAAZANFD5Q.
You are receiving this because you modified the open/close state.

Hello,
I hope this message finds you well. I recently sent you an email regarding your impressive project on dynamic cloth folding. I have developed a new and in-depth research idea based on your work and would like to build upon it.
To assist with my scientific research, could you please share a copy of the real-world code used in this project? If my previous email did not reach you or if it was sent to an incorrect address, please feel free to respond to this message. My email address is<EMAIL_ADDRESS>Thank you very much for your assistance. I look forward to your reply.
Best regards

Hello,
I hope this message finds you well. I recently sent you an email regarding your impressive project on dynamic cloth folding. I have developed a new and in-depth research idea based on your work and would like to build upon it.
To assist with my scientific research, could you please share a copy of the real-world code used in this project? If my previous email did not reach you or if it was sent to an incorrect address, please feel free to respond to this message. My email address is<EMAIL_ADDRESS>Thank you very much for your assistance. I look forward to your reply.
Best regards

Hi @foreback! For some reason I did not receive your email. I added you to the repo now, but just as a warning there is no instruction manual on how to run things, but all the code is there in some form or another.

r

Thank you so much for adding me to the repository! I appreciate your quick action on this.


docs: Translation Japanese and Copy

Translation Japanese and copy.
After merging, we will translate the copied file with our friends.
translation
docs/.vuepress/config.js
docs/ja/README.md
copy

docs/ja/config
docs/ja/core-plugins
docs/ja/dev-guide
docs/ja/guid
docs/ja/migrating-from-v3

@tiwuofficial /cc @53able
Hi!
Thank you for your PR!
We would also like to hope that you invite other reviewers. vue-cli has a lot of docs, so it’s hard to review by me only. 🙏

@kazupon /cc @tiwuofficial
HI!
Thanks for Advice!
See also the PR.🙇♂
#4934


Fix the incorrect revoke of a users when users are revoked

Basically when you remove a user from the OpenVPN list the update_users.sh script will run the below commands:
for ovpn_user in ${ovpn_users[@]}
do
  if [[ "$USERNAMES" =~ "$ovpn_user" ]];
  then
    echo "Keeping certificate for user ${ovpn_user}."
  else
    echo "Revoking certificate for user ${ovpn_user}!"

    # Export the corresponding options and revoke the user certificate
    export MENU_OPTION="2"
    export CLIENT="${ovpn_user}"
    export DNS="9"
    searchRegex="${ovpn_user}$"
    export CLIENTNUMBER=$(echo $(tail -n +2 /etc/openvpn/easy-rsa/pki/index.txt | grep "^V" | cut -d '=' -f 2 | nl -s ') '|grep -n $searchRegex)|head -c 1)
    ./openvpn-install.sh
  fi
done

Now the issue comes in with this command:
export CLIENTNUMBER=$(echo $(tail -n +2 /etc/openvpn/easy-rsa/pki/index.txt | grep "^V" | cut -d '=' -f 2 | nl -s ') '|grep -n $searchRegex)|head -c 1)

To break this down, this section of the command will return a list of users in the order they are in OpenVPN as a user with a number assigned to it and then select the one that it’s currently looping through skip or remove the user. To remove a user in OpenVPN you don’t pass in a name you pass in the number the user has assigned to it.
So let’s break this down further, this section of the command returns the list of users and the number:
tail -n +2 /etc/openvpn/easy-rsa/pki/index.txt | grep "^V" | cut -d '=' -f 2 | nl -s ' '
     1 user1
     2 user2
     3 user3
     4 user4
     5 user5
     6 user6
     7 user7
     8 user8
     9 user9
    10 user10
    11 user11
    12 user12

Next we filter down to a user, so let’s take the user1:
tail -n +2 /etc/openvpn/easy-rsa/pki/index.txt | grep "^V" | cut -d '=' -f 2 | nl -s ' ' | grep -n user1

This will return:
1: 1 user1

If we add the head -c 1 to the command it will return:
1

Now the problem comes when you remove a user which lets say is user 12 in the list as an example:
tail -n +2 /etc/openvpn/easy-rsa/pki/index.txt | grep "^V" | cut -d '=' -f 2 | nl -s ' ' | grep -n user12 | head -c 1

This is also going to return 1 due to head -c 1 only taking the first value, if we were using head -c 2  it would return user 12 but that is not scalable and users in the single digits would return number:
like 1: or 8:
With the current design:
If we remove user 12 from the list  what is going to happen is that it’s going to leave user 12 and remove user 1 If there was 20 users and we remove user 20 what is going to happen is it will remove user 2
The solution to this problem is instead of using head -c 1
We filter by column 2 which will always return the correct number by using awk '{print $2}':
tail -n +2 /etc/openvpn/easy-rsa/pki/index.txt | grep "^V" | cut -d '=' -f 2 | nl -s ' ' | grep -n user12 | awk '{print $2}'

Will return:
12

This will allow the users to be able to scale single digits, double digits, triple digits etc…

[chore(release): version 2.4.1 [skip ci]]


Breaking: Remove flattened output documentation paths feature

Removes the UsesFlattenedOutputPaths trait, and the overall feature, as it breaks pages with the same name in different directories. Fixes https://github.com/hydephp/develop/issues/1164
This is unfortunately likely lead to URL breaks in built sites. It means that if you have a page stored as _docs/foo/bar.md it will now be saved to _site/docs/foo/bar.html, instead of _site/docs/bar.html. This means that you can how have two files named _docs/xxx/bar.md.

This broke search. Search index link must be updated to resolve the file based on the root docs path-

Okay gonna try to see if I can add back this as a simple configurable feature.


Change look and feel of auto generated components

Is your feature request related to a problem?
I want to change the look and feel of the auto generated components that are based on the openapi specs.
Describe the solution you'd like
Is there a way of customizing the styling of the auto generated components?
Describe alternatives you've considered
No response
Additional Context
No response

Thanks for the feedback :raised_hands:
Customization is definitely something I want to tackle in the future. I'm not sure yet which direction it'll take but I'm assuming it'll be something to address when getting closer to a v1.0.0 release.
In the meantime, a CSS based approach is probably the best way to go using Starlight custom CSS (note that the experience will be improved when Starlight supports Cascade Layers which is currently in the works).


chore: jsonfmt peering

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@nschonni, I only see the layout modification in the PR, so what is the purpose of this change?

The purpose is to make the spec conform to the other spec's layout. There currently isn't a CI job that properly flags these issues.


Issuer with filter

Hi,
I used this tutorial to use mixitup : http://www.queness.com/post/14577/create-a-simple-responsive-portfolio-page-with-filtering-and-hover-effect
For some reason when I click on one of the button, it filters the items, the move but then come back to their places with all the different items.
Here's the js:
$(function () {
    var filterList = {
        init: function () {
            $('#portfolio-list').mixitup({
                targetSelector: '.portfolio-item',
                filterSelector: '.filter',
                effects: ['fade'],
                easing: 'snap',
                onMixEnd: filterList.hoverEffect()
            });
        },
        hoverEffect: function () {
            // Simple parallax effect
            $('#portfolio-list .portfolio-item').hover(
                function () {
                    $(this).find('.label').stop().animate({bottom: 0}, 200, 'easeOutQuad');
                    $(this).find('img').stop().animate({top: 0}, 500, 'easeOutQuad');
                },
                function () {
                    $(this).find('.label').stop().animate({bottom: 0}, 200, 'easeInQuad');
                    $(this).find('img').stop().animate({top: 0}, 300, 'easeOutQuad');
                }
            );
        }
    };
    filterList.init();
});

The HTML :

        ALL
        CAMPAIGN+PRINT
        WEB+INTERACTIVE
        IMAGING+PHOTOGRAPHY
        MOTION+VIDEO

          <hgroup>

Anna

          </hgroup>

Its rounded edges, right angles and uniform stroke weight create
            unity throughout the typeface. Anna gives the sci-fi world a more elegant font.

            view project

Can anybody help me out and tell me what's wrong?

I just ran into what I think is this issue (I was searching all over for "mixitup items jumping", etc.). Turns out one of the parent divs of the items I was filtering wasn't floated correctly and therefore the calculations done in JS weren't "correct".
Just a note for anyone who might run into this, check your css! 😸

Anybody got a solution for this?
@breadadams how about you?
Iam going over and over my css fixing floats but still happens ><

@alilishan-omniphics This is a very old issue so I suspect whatever issue you're having is not relevant to this thread. If you're having issue with layout, I would recommend using one of the demos as a starting point and then adapting it to your design as needed:
https://demos.kunkalabs.com/mixitup/
As you add in features, check to see at what point the layout becomes broken and that should help you understand the cause of the problem.
Generally speaking, floats are not recommended for use with MixItUp, and flexbox or inline-block is preferred. More information here:
https://www.kunkalabs.com/tutorials/mixitup-grid-layouts/
Hope that helps.


Make distributed mode default.

If neither workers file nor workers is specified, try to read from the wokers.yaml file if it exists.

@merlimat


BI doesn't function properly

Describe the bug
Sorry to spam you! Really looking forward to test driving the addon! I'm getting some odd behaviour where BetterViewer loads but seems to fall over. I can only reproduce the issue on one PC 😑
To Reproduce
Steps to reproduce the behavior:

Open an image to launch BetterViewer

Expected behavior
BetterViewer should load the image normally. Instead, the background blurry image is shown, but the actual image doesn't show and the image controls do not function:
GIF recording here:
https://imgur.com/a/N65YCd0
Screenshots
https://imgur.com/a/N65YCd0
Desktop (please complete the following information):

OS: Windows
Browser: firefox
Version: 102.0a (Nightly)

Additional context
Since it's just one PC that's having the issue, definitely could be something weird on my end.

Thank you @SpitFire-666 for your feedback 👍
Can you disable all addons except "BetterViewer" and test again ? I think this issue is caused by other addons.

I'm seeing something similar but in my case, as soon as I hover over any of the BetterViewer buttons, the image shows up.  (Before that, I can see the image briefly, then the blurred background being shown, and then nothing until I hover over the buttons)
I did try it in a clean profile and everything worked fine.  I have started disabling possible addon conflicts as well, but still narrowing it down on my side.
https://user-images.githubusercontent.com/979729/168647735-b4040cc2-021e-4fe5-96cc-0c5b16325051.mp4
Well drat ... I took another guess and disabled Download Manager (S3) and that resolved it for me.  (It injects code to create a replica of the old status bar on the bottom of a page to show downloads which is very handy)  The problem for me now is that I really need to keep that addon (not a big fan of how FF handles download progress\notification) and that the addon isn't under active development any more.

Since Download Manger (S3) isn't open source, I can't really find why there is an incompatibility.
Both extensions work together if you disable 'Enable Download Bar' (but it seems that is the main reason you use that addon)

I Initially thought it had something to do with this error chrome gives on a BetterViewer image page when having both extensions enabled at the same time.

Deleting all inline-styles from the code base didn't change anything, and disabling Content Security Policies stopped the errors from happening, but it didn't fix the issue.


Hi..when i first run main.py -- eval,appeared [list] no define

As shown in the diagram

Hi, @zouzouwei
I just updated the code.
Please try again.

THX


All containers up and healthy, can't access nothing

Hi.
I followed all the steps and even tried to change the lab.com domain for another one I had accessible.
The containers run and all of them are healthy. I can access them also (exec -it /bin/sh)
But I can't access in any browser or computer any page (minio, outline, nothing)
Host is a macOS (Intel)
Docker updated today to last version
All configuration of docker reset to default
What I can do to test using only localhost without any domain and send you the logs if I still can't access it?

Hi, @rgddev .
I feel that you did not configure traefik.
In this example, Traefik is also used as the service gateway. If you are not familiar with Traefik, you can read the previous content to understand "Easier Ways to Use Traefik 2" and some practical examples of Traefik to deepen your understanding.

https://soulteary.com/2020/12/02/easier-way-to-use-traefik-2.html
https://soulteary.com/tags/traefik.html

Hey @soulteary. I could get it working with Traefik, was using another way.
But now, after enter username/password in SSO, I'm getting this (attach).

Even using Authy or Keepass as OTP (the initial code matches), I still can't login. I don't know if it's a Traefik problem as well.

@rgddev could you please explain roughly how you did with Traefik ?
I can't see where I'm supposed to configure it ?
Thanks

I'm using a dedicated vps with all urls (file.myurl.com, file-admin.myurl.com, sso.myurl.com, attachment.myurl.com, docs.myurl.com) pointing to it through the myurl.com DNS zone

Sorry, @Limezy. I think because this is closed I didn't got any notification.
I did with Traefik, but can't use outline yet because the OTP error.
So probably the config is not going to be too much helpful...

No worries !


Patched TermSrv.dll to allow multiple connections on Windows 10 Pro 1909

Does anyone have a Patched TermSrv.dll to allow multiple users to be logged on in Windows 10 Pro 1909.?

rdpwrap is the solution to skip termsrv.dll


graphql-plugin: Middle handler?

Can someone pls. explain the "middle handler" of GraphQLOptions?
As there is no real documentation and my kotlin skills are very limited: I assume this is a kind of requset interceptor where I can add f.i. authentication information?! at least from here https://github.com/tipsy/javalin/blob/javalin-parent-3.13.3/javalin-graphql/src/main/java/io/javalin/plugin/graphql/GraphQLHandler.kt#L27 it looks like the middlehandler/context is invoked before the graphql execution runs. But the example (https://javalin.io/plugins/graphql#getting-started) only shows how to acess the context during query/mutation, but the invokation of the context object to enrich it with stuff from the javalin context is mysterious.
Can someone pls. explain? maybe with java code example?
br,
Alex

I even installed IntelliJ to be (hopefully) able to narrow down the problem. But result is the same as with my netbeans.
No matter how I try, I get strange errors...
// "options" is a java instance of GraphQLOptions ...
options.setMiddleHandler(context -> { /* do something */ });

gives me:
java: incompatible types: bad return type in lambda expression
    missing return value

And (I don't know how to return a kotlin "Unit"  instance, so I just try with "null" for now)
options.setMiddleHandler(context -> { return null; });

gives me:
java: reference to setMiddleHandler is ambiguous
  both
method setMiddleHandler(kotlin.jvm.functions.Function1<? super io.javalin.http.Context,kotlin.Unit>) in io.javalin.plugin.graphql.GraphQLOptions and
method setMiddleHandler(kotlin.jvm.functions.Function1<? super io.javalin.http.Context,kotlin.Unit>) in io.javalin.plugin.graphql.GraphQLOptions match

No idea what this strange error means. Why "both methods"? In GraphQLOptions is only one. Where does the 2nd come from?!
I'm running out of ideas. Pls. help.

Google'd a bit... Found this:
https://developer.android.com/kotlin/interop#lambda_arguments
There they say one should return "Unit.INSTANCE". Sounds okay, but does of course not fix the "ambigous issue".

Found out why java is complaining about identical methods:
If I open the kotlin GraphQLOptions class in Netbeans, it shows indeed two methods with same name, but they are not 100% identical:
public final void setMiddleHandler(@NotNull Function1<? super Context, Unit> <set-?>) {
        // <editor-fold defaultstate="collapsed" desc="Compiled Code">
        /* 0: aload_1
         * 1: ldc           #20                 // String <set-?>
         * 3: invokestatic  #26                 // Method kotlin/jvm/internal/Intrinsics.checkParameterIsNotNull:(Ljava/lang/Object;Ljava/lang/String;)V
         * 6: aload_0
         * 7: aload_1
         * 8: putfield      #13                 // Field middleHandler:Lkotlin/jvm/functions/Function1;
         * 11: return
         *  */
        // </editor-fold>
    }

@NotNull
public final GraphQLOptions setMiddleHandler(@NotNull Function1<? super Context, Unit> middleHandler) {
    // <editor-fold defaultstate="collapsed" desc="Compiled Code">
    /* 0: aload_1
     * 1: ldc           #130                // String middleHandler
     * 3: invokestatic  #26                 // Method kotlin/jvm/internal/Intrinsics.checkParameterIsNotNull:(Ljava/lang/Object;Ljava/lang/String;)V
     * 6: aload_0
     * 7: astore_2
     * 8: iconst_0
     * 9: istore_3
     * 10: iconst_0
     * 11: istore        4
     * 13: aload_2
     * 14: checkcast     #2                  // class io/javalin/plugin/graphql/GraphQLOptions
     * 17: astore        5
     * 19: iconst_0
     * 20: istore        6
     * 22: aload         5
     * 24: aload_1
     * 25: putfield      #13                 // Field middleHandler:Lkotlin/jvm/functions/Function1;
     * 28: nop
     * 29: aload_2
     * 30: checkcast     #2                  // class io/javalin/plugin/graphql/GraphQLOptions
     * 33: areturn
     *  */
    // </editor-fold>
}

I have no idea why this is the case. Maybe the kotlin source is not 100% interop with java code?! Where are the kotlin experts?
Looks like this has never been tested or used with java ....

Found a way around it:
import io.javalin.http.Context;
import kotlin.Unit;

/**
 *
 * @author alexander
 */
public class MiddleHandler implements kotlin.jvm.functions.Function1<Context, Unit> {

    @Override
    public Unit invoke(Context p1) {
        System.out.println("foo!!!");
        /* do something */
        return Unit.INSTANCE;
    }

}

            try {
                Method[] methods = GraphQLOptions.class.getMethods();
                for (Method method : methods) {
                    if (method.getName().equals("setMiddleHandler") && method.getReturnType().equals(void.class)) {
                        System.out.println("->: " + method);
                        method.invoke(options, new MiddleHandler());
                    }
                }
            } catch (IllegalAccessException ex) {
                Logger.getLogger(App.class.getName()).log(Level.SEVERE, null, ex);
            } catch (IllegalArgumentException ex) {
                Logger.getLogger(App.class.getName()).log(Level.SEVERE, null, ex);
            } catch (InvocationTargetException ex) {
                Logger.getLogger(App.class.getName()).log(Level.SEVERE, null, ex);
            }

That way I get the "foo!!!" output whenever a query runs. But can only be a temporary workaround...
Would be great to get some feedback from kotlin devs...
br,
Alex

It looks like it's just not compatible with Java (thought it's not likely super compatible with Kotlin either). Two functions with the same signature only differentiated by return type tends to cause problems in both languages, though less so in Kotlin.

All in all: It's more like a "beta" state than a "production ready" state.
I would really like to use this graphql-plugin and combine it also with https://github.com/pac4j/javalin-pac4j.
But for now this remains "under construction"
I will try to digg into and maybe provide a java version that (hopefully) also integrates with pac4j... But this will take some time.

@tuxedo0801 is this something you are still planning on working on?

I did a rewrite/port in java-only which is currently mich like a proof of concept. Needs some polishing before I publish it.

Cool, thanks for the update!

@tuxedo0801 do you think you'll get this done within the next few months?

I'm planning to finish my 1st draft for the implementation. How should I proceed? Separate project that is mentioned/linked in the documentation, or should I create a fork + pull-request? @tipsy

Source is now online: https://gitlab.com/alexanderchristian/javalin-graphql-javaplugin

@tuxedo0801 please go ahead and make a PR for adding it to the GraphQL module :)

@tuxedo0801 are you still interested in this?


Rails completion

Unfortunately, I don't have Rails installed on this machine to test this.  Anyone else able to step in and test it out?

What is your bash version?

 $ bash --version
GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin11)
Copyright (C) 2007 Free Software Foundation, Inc.

Should we support legacy bash versions provided with darwin?
bash --version
GNU bash, version 4.2.10(1)-release (i686-pc-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.

Well, I'm definitely +1 on supporting what's on Lion at least, but that's for selfish reasons. :-)

Oh. Lion is so old. Maybe we need some os detection layer inside bash-it ?

Ok. bash 3.2 will be forever on macos koz Apple has strong GPL3 phobia after incident with App Store. I think we should provide this file and just disable it if bash version < 4.0. What do you think?

@nwinkler I vote for closing this and waiting for someone to submit a new PR that uses a package manager installed version, instead of continuing to embed copy written works. I think you know idgaf, but your project is popular and it seems people want to tackle that now.

Agreed, @cornfeedhobo - closing this for now. Thanks for suggesting this!


Sync our dev branch with upstream

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 8 committers have signed the CLA.:x: pelenthium:x: polarising-java:x: tchiotludo:x: yanayita:x: mredjem:x: twobeeb:x: gquintana:x: ankonYou have signed the CLA already but the status is still pending? Let us recheck it.


Improve seeding output

Issue/Task Number: T126, T127
Overview
Make output of mix seed and mix seed --sample more consistent. Add --verbose option to list out the actual data inserted by the seed.
Changes

Prepend mix seed --sample output with mix seed
Add --verbose option so that users can see what is inserted

Implementation Details
The seed output could be much leaner but since the seed is still working in place of the admin panel (e.g. API key creation), we still need the seed output. Once the admin panel has all the features that the seed does, then we can simplify the output much more.
Usage

Run mix seed --sample to see the prepended seed output.
Run mix seed --verbose or mix seed --sample --verbose to show the data inserted by the seed.

Example screenshot (ran locally, credentials are no longer valid):

Full output (mix seed)
vagrant@ewallet:/vagrant$ mix seed
What email address should we set for your first admin user?
This email is required for logging into the admin panel.
If a user with this email already exists, it will escalate the user to admin role.

E-mail (admin@example.com<EMAIL_ADDRESS>
                     Setting up the OmiseGO eWallet Server

This seeder seeds the minimum amount of data needed to start a production environment.

If you would like to seed the database with sample data so that you can play around with the
system, we recommend running mix seed --sample instead.

## Manage your eWallet system via the Admin Panel

We have just seeded your eWallet system with an API key and an Admin Panel user. To save your time,
we have also configured the Admin Panel with the seeded API key. If you want to, you can look up
the configuration file at apps/admin_panel/assets/.env.

Now it's your turn to login to your Admin Panel with the following credentials:

  • Login URL : http://localhost:4000/admin
  • Email<EMAIL_ADDRESS>  • Password  : ZLiwRiWhylwEYCj2HQ7gJQ

Please take note of the above password. We won't be able to retrieve it again after the initial
seed, as it will be one-way encrypted for your security.

Now that you are logged in to the Admin Panel, you can:

  • Change your password immediately! The password will show in the seed only once.
  • Create other Admin Panel users
  • Manage access and secret keys for your application servers to connect to OmiseGO eWallet
    API
  • Manage API keys for your mobile apps and the Admin Panel
  • Always come back and access your Admin Panel at http://localhost:4000/admin
  • etc.

## Manage your eWallet system via the Admin API

The Admin API is the entry point to manage the entire OmiseGO eWallet system. Follow the steps
below to authenticate your Swagger UI requests:

  1. Browse to http://localhost:4000/admin/api/docs and click Authorize
  2. Use the value below for ClientAuth and click Authorize:
         OMGAdmin MDMyYjE2NTktZWJlNS00ZTIzLWFkNGEtOWIzNDY5ZDBkYTU5Om96bU9NaGtERkc4RmRoZUJIclRiUWpTZlFjVEcyaWFmcV9SY3k0MUhPWlk=

     Note: You can also make requests from your favorite API client by building your own
     Authorization header:

     • Authorization header : OMGAdmin base64(api_key_id:api_key)
     • API key ID           : 032b1659-ebe5-4e23-ad4a-9b3469d0da59
     • API key              : ozmOMhkDFG8FdheBHrTbQjSfQcTG2iafq_Rcy41HOZY

  3. Now you can call the /login endpoint with the above Authorization header and the
     following request body:
         {
          "email"<EMAIL_ADDRESS>          "password": "ZLiwRiWhylwEYCj2HQ7gJQ"
         }

     Please take note of the above password. We won't be able to retrieve it again after the
     initial seed, as it will be one-way encrypted for your security.

  4. To get started quickly, we have seeded the user's authentication token and generated the
     Authorization header for you. Browse to http://localhost:4000/admin/api/docs again and click
     Authorize. This time, use the value below for UserAuth:
         OMGAdmin MDMyYjE2NTktZWJlNS00ZTIzLWFkNGEtOWIzNDY5ZDBkYTU5Om96bU9NaGtERkc4RmRoZUJIclRiUWpTZlFjVEcyaWFmcV9SY3k0MUhPWlk6NDI4OWMzMmEtMGJkMC00YzVjLTlmMTktZWU0NjY0ZDE1MDIzOk1BX0pCTzZGRlBTSy1ZajQzQzhFTmRWM0ZCal94dzlHdlNoa0JmYzROM0U=

     The above header is for you to get started quickly. To integrate the eWallet SDK to your
     application, you must build your own Authorization header using the information below:

     • Authorization header : OMGAdmin base64(api_key_id:api_key:user_id:auth_token)
     • API key ID           : 032b1659-ebe5-4e23-ad4a-9b3469d0da59
     • API key              : ozmOMhkDFG8FdheBHrTbQjSfQcTG2iafq_Rcy41HOZY
     • User ID              : <the returned user_id in step 3>
     • User's auth token    : <the returned authentication_token in step 3>

  5. Test your authentication by calling /me.get. You should see your user information.

## Using the eWallet API

Now that you are authenticated, you have the full access to the eWallet system via the Admin API.
You can now use the Authorization header above with the rest of the Swagger specification at
http://localhost:4000/admin/api/docs to:

  • Generate a pair of access/secret key for your application servers via /access_key.create
  • Generate a pair of API key for your clients such as your mobile app, via /api_key.create
  • Use the API key generated above to make requests to the eWallet API. Learn more at
    http://localhost:4000/api/docs
  • etc.

Database seeded completed. Enjoy!

Full output (mix seed --verbose)
vagrant@ewallet:/vagrant$ mix seed --verbose
What email address should we set for your first admin user?
This email is required for logging into the admin panel.
If a user with this email already exists, it will escalate the user to admin role.

E-mail (admin@example.com<EMAIL_ADDRESS>
                      Verbose mode: Displaying seeded data

Seeding the master account:

  Name : master_account
  ID   : 8dc0712e-87b9-443e-a72b-e01f27039110

Seeding an Admin Panel API key:

  Account ID : 8dc0712e-87b9-443e-a72b-e01f27039110
  API key ID : ac5cd4ea-7d74-4e1f-bb79-5cc54d314723
  API key    : YD-UdZ4xrNTOnyLA1lcy3FoiRbHwJIX_QZKzwpj-4ro

Seeding roles:

  Name         : admin
  Display name : Admin

  Name         : viewer
  Display name : Viewer

Seeding the initial admin panel user:

  ID       : f45e3962-f2bf-41ea-873b-890f93fc94ef
  Email<EMAIL_ADDRESS>  Password : BtziE1wDM0ubhxZ_TnLL3w

  Email<EMAIL_ADDRESS>  Account : master_account
  Role    : admin

                     Setting up the OmiseGO eWallet Server

This seeder seeds the minimum amount of data needed to start a production environment.

If you would like to seed the database with sample data so that you can play around with the
system, we recommend running mix seed --sample instead.

## Manage your eWallet system via the Admin Panel

We have just seeded your eWallet system with an API key and an Admin Panel user. To save your time,
we have also configured the Admin Panel with the seeded API key. If you want to, you can look up
the configuration file at apps/admin_panel/assets/.env.

Now it's your turn to login to your Admin Panel with the following credentials:

  • Login URL : http://localhost:4000/admin
  • Email<EMAIL_ADDRESS>  • Password  : BtziE1wDM0ubhxZ_TnLL3w

Please take note of the above password. We won't be able to retrieve it again after the initial
seed, as it will be one-way encrypted for your security.

Now that you are logged in to the Admin Panel, you can:

  • Change your password immediately! The password will show in the seed only once.
  • Create other Admin Panel users
  • Manage access and secret keys for your application servers to connect to OmiseGO eWallet
    API
  • Manage API keys for your mobile apps and the Admin Panel
  • Always come back and access your Admin Panel at http://localhost:4000/admin
  • etc.

## Manage your eWallet system via the Admin API

The Admin API is the entry point to manage the entire OmiseGO eWallet system. Follow the steps
below to authenticate your Swagger UI requests:

  1. Browse to http://localhost:4000/admin/api/docs and click Authorize
  2. Use the value below for ClientAuth and click Authorize:
         OMGAdmin YWM1Y2Q0ZWEtN2Q3NC00ZTFmLWJiNzktNWNjNTRkMzE0NzIzOllELVVkWjR4ck5UT255TEExbGN5M0ZvaVJiSHdKSVhfUVpLendwai00cm8=

     Note: You can also make requests from your favorite API client by building your own
     Authorization header:

     • Authorization header : OMGAdmin base64(api_key_id:api_key)
     • API key ID           : ac5cd4ea-7d74-4e1f-bb79-5cc54d314723
     • API key              : YD-UdZ4xrNTOnyLA1lcy3FoiRbHwJIX_QZKzwpj-4ro

  3. Now you can call the /login endpoint with the above Authorization header and the
     following request body:
         {
          "email"<EMAIL_ADDRESS>          "password": "BtziE1wDM0ubhxZ_TnLL3w"
         }

     Please take note of the above password. We won't be able to retrieve it again after the
     initial seed, as it will be one-way encrypted for your security.

  4. To get started quickly, we have seeded the user's authentication token and generated the
     Authorization header for you. Browse to http://localhost:4000/admin/api/docs again and click
     Authorize. This time, use the value below for UserAuth:
         OMGAdmin YWM1Y2Q0ZWEtN2Q3NC00ZTFmLWJiNzktNWNjNTRkMzE0NzIzOllELVVkWjR4ck5UT255TEExbGN5M0ZvaVJiSHdKSVhfUVpLendwai00cm86ZjQ1ZTM5NjItZjJiZi00MWVhLTg3M2ItODkwZjkzZmM5NGVmOjRvRGtDeTZqZTQwYndJVU5OQV8wLUhaU2k5NkExZ3E3VnB6Sk1ULWh1cm8=

     The above header is for you to get started quickly. To integrate the eWallet SDK to your
     application, you must build your own Authorization header using the information below:

     • Authorization header : OMGAdmin base64(api_key_id:api_key:user_id:auth_token)
     • API key ID           : ac5cd4ea-7d74-4e1f-bb79-5cc54d314723
     • API key              : YD-UdZ4xrNTOnyLA1lcy3FoiRbHwJIX_QZKzwpj-4ro
     • User ID              : <the returned user_id in step 3>
     • User's auth token    : <the returned authentication_token in step 3>

  5. Test your authentication by calling /me.get. You should see your user information.

## Using the eWallet API

Now that you are authenticated, you have the full access to the eWallet system via the Admin API.
You can now use the Authorization header above with the rest of the Swagger specification at
http://localhost:4000/admin/api/docs to:

  • Generate a pair of access/secret key for your application servers via /access_key.create
  • Generate a pair of API key for your clients such as your mobile app, via /api_key.create
  • Use the API key generated above to make requests to the eWallet API. Learn more at
    http://localhost:4000/api/docs
  • etc.

Database seeded completed. Enjoy!

Full output (mix seed --sample --verbose)
vagrant@ewallet:/vagrant$ mix seed --sample --verbose
What email address should we set for your first admin user?
This email is required for logging into the admin panel.
If a user with this email already exists, it will escalate the user to admin role.

E-mail (admin@example.com<EMAIL_ADDRESS>
                      Verbose mode: Displaying seeded data

Seeding the master account:

  Name : master_account
  ID   : 50d901d5-3cac-4e37-b097-67be0a88833b

Seeding an Admin Panel API key:

  Account ID : 50d901d5-3cac-4e37-b097-67be0a88833b
  API key ID : 35c3fa8c-69a6-4892-924f-fd38d33674b5
  API key    : I9SgyO5l30ftBeS_Y5a4Is3u60mTNZFOZRSklKZz2Sk

Seeding roles:

  Name         : admin
  Display name : Admin

  Name         : viewer
  Display name : Viewer

Seeding the initial admin panel user:

  ID       : 965eb181-6e83-442d-adce-4b68f4d0374f
  Email<EMAIL_ADDRESS>  Password : HfhFsCyQfBb-dwjajeND9A

  Email<EMAIL_ADDRESS>  Account : master_account
  Role    : admin

                     Setting up the OmiseGO eWallet Server

This seeder seeds the minimum amount of data needed to start a production environment.

If you would like to seed the database with sample data so that you can play around with the
system, we recommend running mix seed --sample instead.

## Manage your eWallet system via the Admin Panel

We have just seeded your eWallet system with an API key and an Admin Panel user. To save your time,
we have also configured the Admin Panel with the seeded API key. If you want to, you can look up
the configuration file at apps/admin_panel/assets/.env.

Now it's your turn to login to your Admin Panel with the following credentials:

  • Login URL : http://localhost:4000/admin
  • Email<EMAIL_ADDRESS>  • Password  : HfhFsCyQfBb-dwjajeND9A

Please take note of the above password. We won't be able to retrieve it again after the initial
seed, as it will be one-way encrypted for your security.

Now that you are logged in to the Admin Panel, you can:

  • Change your password immediately! The password will show in the seed only once.
  • Create other Admin Panel users
  • Manage access and secret keys for your application servers to connect to OmiseGO eWallet
    API
  • Manage API keys for your mobile apps and the Admin Panel
  • Always come back and access your Admin Panel at http://localhost:4000/admin
  • etc.

## Manage your eWallet system via the Admin API

The Admin API is the entry point to manage the entire OmiseGO eWallet system. Follow the steps
below to authenticate your Swagger UI requests:

  1. Browse to http://localhost:4000/admin/api/docs and click Authorize
  2. Use the value below for ClientAuth and click Authorize:
         OMGAdmin MzVjM2ZhOGMtNjlhNi00ODkyLTkyNGYtZmQzOGQzMzY3NGI1Okk5U2d5TzVsMzBmdEJlU19ZNWE0SXMzdTYwbVROWkZPWlJTa2xLWnoyU2s=

     Note: You can also make requests from your favorite API client by building your own
     Authorization header:

     • Authorization header : OMGAdmin base64(api_key_id:api_key)
     • API key ID           : 35c3fa8c-69a6-4892-924f-fd38d33674b5
     • API key              : I9SgyO5l30ftBeS_Y5a4Is3u60mTNZFOZRSklKZz2Sk

  3. Now you can call the /login endpoint with the above Authorization header and the
     following request body:
         {
          "email"<EMAIL_ADDRESS>          "password": "HfhFsCyQfBb-dwjajeND9A"
         }

     Please take note of the above password. We won't be able to retrieve it again after the
     initial seed, as it will be one-way encrypted for your security.

  4. To get started quickly, we have seeded the user's authentication token and generated the
     Authorization header for you. Browse to http://localhost:4000/admin/api/docs again and click
     Authorize. This time, use the value below for UserAuth:
         OMGAdmin MzVjM2ZhOGMtNjlhNi00ODkyLTkyNGYtZmQzOGQzMzY3NGI1Okk5U2d5TzVsMzBmdEJlU19ZNWE0SXMzdTYwbVROWkZPWlJTa2xLWnoyU2s6OTY1ZWIxODEtNmU4My00NDJkLWFkY2UtNGI2OGY0ZDAzNzRmOmlrYWs1Q2dyN2Utd3VIb2prZTJEOUJvRXRjLVVaWG9yZG5DbDVRWjdVbFk=

     The above header is for you to get started quickly. To integrate the eWallet SDK to your
     application, you must build your own Authorization header using the information below:

     • Authorization header : OMGAdmin base64(api_key_id:api_key:user_id:auth_token)
     • API key ID           : 35c3fa8c-69a6-4892-924f-fd38d33674b5
     • API key              : I9SgyO5l30ftBeS_Y5a4Is3u60mTNZFOZRSklKZz2Sk
     • User ID              : <the returned user_id in step 3>
     • User's auth token    : <the returned authentication_token in step 3>

  5. Test your authentication by calling /me.get. You should see your user information.

## Using the eWallet API

Now that you are authenticated, you have the full access to the eWallet system via the Admin API.
You can now use the Authorization header above with the rest of the Swagger specification at
http://localhost:4000/admin/api/docs to:

  • Generate a pair of access/secret key for your application servers via /access_key.create
  • Generate a pair of API key for your clients such as your mobile app, via /api_key.create
  • Use the API key generated above to make requests to the eWallet API. Learn more at
    http://localhost:4000/api/docs
  • etc.

                  Verbose mode: Displaying seeded sample data

Seeding Accounts:

  Name   : brand1
  ID     : 2a311097-7690-4f45-811b-1e7fd2568221
  Parent : 50d901d5-3cac-4e37-b097-67be0a88833b

  Name   : branch1
  ID     : c957604c-9b67-49f1-846f-b3a5ca602a08
  Parent : 2a311097-7690-4f45-811b-1e7fd2568221

  Name   : brand2
  ID     : 601622d7-5516-4bad-9a0c-e78df61f4240
  Parent : 50d901d5-3cac-4e37-b097-67be0a88833b

  Name   : branch2
  ID     : 66c20fd5-8121-4f2e-ba22-26720b610890
  Parent : 601622d7-5516-4bad-9a0c-e78df61f4240

Seeding the minted tokens:

  Friendly ID     : OMG:85c479a9-c246-4d85-8d55-3ec5fab29cb8
  Subunit to unit : 10000
  Account         : 50d901d5-3cac-4e37-b097-67be0a88833b

  Friendly ID     : KNC:7e12e77d-319e-48c5-8445-403e8dee52c7
  Subunit to unit : 1000
  Account         : 50d901d5-3cac-4e37-b097-67be0a88833b

  Friendly ID     : BTC:62dfb823-0a2e-4b91-8042-c6e05f3f46b8
  Subunit to unit : 10000
  Account         : 50d901d5-3cac-4e37-b097-67be0a88833b

  Friendly ID     : OEM:6c2798ef-34eb-4462-ab1f-2606a07eef3c
  Subunit to unit : 100
  Account         : 50d901d5-3cac-4e37-b097-67be0a88833b

  Friendly ID     : ETH:66ff7ca6-0829-473e-9c62-2932518787ce
  Subunit to unit :<PHONE_NUMBER>000000000
  Account         : 50d901d5-3cac-4e37-b097-67be0a88833b

Minting the seeded minted tokens:

  Minted Token ID  : OMG:85c479a9-c246-4d85-8d55-3ec5fab29cb8
  Amount (subunit) :<PHONE_NUMBER>0
  Confirmed?       : true
  From address     : genesis
  To address       : c51bc034-a0fb-40e1-a36f-ce330cd36feb

  Minted Token ID  : KNC:7e12e77d-319e-48c5-8445-403e8dee52c7
  Amount (subunit) :<PHONE_NUMBER>
  Confirmed?       : true
  From address     : genesis
  To address       : c51bc034-a0fb-40e1-a36f-ce330cd36feb

  Minted Token ID  : BTC:62dfb823-0a2e-4b91-8042-c6e05f3f46b8
  Amount (subunit) :<PHONE_NUMBER>0
  Confirmed?       : true
  From address     : genesis
  To address       : c51bc034-a0fb-40e1-a36f-ce330cd36feb

  Minted Token ID  : OEM:6c2798ef-34eb-4462-ab1f-2606a07eef3c
  Amount (subunit) : 100000000
  Confirmed?       : true
  From address     : genesis
  To address       : c51bc034-a0fb-40e1-a36f-ce330cd36feb

  Minted Token ID  : ETH:66ff7ca6-0829-473e-9c62-2932518787ce
  Amount (subunit) :<PHONE_NUMBER>000000000000000
  Confirmed?       : true
  From address     : genesis
  To address       : c51bc034-a0fb-40e1-a36f-ce330cd36feb

Seeding eWallet users:

  User ID          : 4cec7574-8327-4b34-838a-3af6f08602ed
  Provider user ID : provider_user_id01
  Username         : user01

  User ID          : 081b16c9-e419-4c24-a87a-ec7c9e58c04e
  Provider user ID : provider_user_id02
  Username         : user02

  User ID          : 57df7bde-968d-4e26-bf49-5f60e3998c6c
  Provider user ID : provider_user_id03
  Username         : user03

  User ID          : 4819abb8-29bf-47dc-aa4a-b289fd05a2a3
  Provider user ID : provider_user_id04
  Username         : user04

  User ID          : e3eb0672-1625-4030-9dc6-0a94c1353f9d
  Provider user ID : provider_user_id05
  Username         : user05

Seeding admin panel users:

  Email<EMAIL_ADDRESS>  Password : P1wVht3lQSgPEBGnJ6ECzA
  ID       : cefa496a-a902-4e43-9460-7e956480e63b

  Email<EMAIL_ADDRESS>  Password : d7XLP3RKMAHWPIz1G4nKdg
  ID       : f6f7792b-86f1-4488-998c-7072b4e3a329

  Email<EMAIL_ADDRESS>  Password : L_wn_QHqsDU32Nb1Fp1bEQ
  ID       : 63eb352f-9f3c-4978-a976-24e070a42f84

  Email<EMAIL_ADDRESS>  Password : SFy6aGAWcjcWqnJyyXCkPQ
  ID       : 7cc92e85-ab2d-4d94-b75f-b2b6265a3ccd

  Email<EMAIL_ADDRESS>  Password : nPhdvReUE7nqTmLgarF8bw
  ID       : 3dc49a9b-1531-4f0f-b3c3-82fd775bdbe4

Assigning roles to admin panel users:

  Email<EMAIL_ADDRESS>  Role  : admin at brand1

  Email<EMAIL_ADDRESS>  Role  : admin at branch1

  Email<EMAIL_ADDRESS>  Role  : viewer at master_account

  Email<EMAIL_ADDRESS>  Role  : viewer at brand1

  Email<EMAIL_ADDRESS>  Role  : viewer at branch1

Seeding Access/Secret Keys:

  Account    : master_account
  Access key : orgKE14U6eH-v-qL3IATAxhwCJsK_t36INJ_EROZQI0
  Secret key : XsLduV_L5vbEippXuC3lm5_5y5LGTRGysHUL3XSjaQU

Seeding API Keys:

  Owner app  : ewallet_api
  Account    : master_account (50d901d5-3cac-4e37-b097-67be0a88833b)
  API key ID : 0f50c2c4-fcbe-404f-9249-bb2713b16ac9
  API key    : qM5lSwlGb8ThqXyhJGBIzuNG26JvMVPMOdYReodgrjY

Seeding Auth Tokens:

  Owner app        : ewallet_api
  User ID          : 4cec7574-8327-4b34-838a-3af6f08602ed
  Provider user ID : provider_user_id01
  User email       : <nil>
  Auth token       : anjePBrx-3mi8vRffKFIfy_OYlwhr8-JOxWjID9M6xI

  Owner app        : admin_api
  User ID          : 965eb181-6e83-442d-adce-4b68f4d0374f
  Provider user ID : <nil>
  User email<EMAIL_ADDRESS>  Auth token       : x1kMkX02XLH4Gf5jdr05ZN4wIYFMm-8TVeo8vp0XCgA

               Trying out OmiseGO eWallet Server with sample data

As you have just run the seed with --sample option, we have generated some credentails below for
you to try the endpoints easily.

If you would like to seed the database with the minimum amount needed to start a production
environment, we recommend running mix seed instead.

## Try eWallet API's Server endpoints

  1. Browse to http://localhost:4000/api/docs
  2. Click the Authorize button
  3. Use the value below for ServerAuth:

    OMGServer b3JnS0UxNFU2ZUgtdi1xTDNJQVRBeGh3Q0pzS190MzZJTkpfRVJPWlFJMDpYc0xkdVZfTDV2YkVpcHBYdUMzbG01XzV5NUxHVFJHeXNIVUwzWFNqYVFV

  4. Try out Server endpoints such as /login, /user.create, /transfer, etc.

## Try eWallet API's Client endpoints

  1. Browse to http://localhost:4000/api/docs
  2. Click the Authorize button
  3. Use the value below for ClientAuth:

    OMGClient cU01bFN3bEdiOFRocVh5aEpHQkl6dU5HMjZKdk1WUE1PZFlSZW9kZ3JqWTphbmplUEJyeC0zbWk4dlJmZktGSWZ5X09ZbHdocjgtSk94V2pJRDlNNnhJ

  4. Try out Client endpoints such as /me.get, /me.list_transactions, /logout, etc.

## Try Admin API's Client endpoints

  1. Browse to http://localhost:4000/admin/api/docs
  2. Click the Authorize button
  3. Use the value below for ClientAuth:

    OMGAdmin MzVjM2ZhOGMtNjlhNi00ODkyLTkyNGYtZmQzOGQzMzY3NGI1Okk5U2d5TzVsMzBmdEJlU19ZNWE0SXMzdTYwbVROWkZPWlJTa2xLWnoyU2s=

  4. Try out Client endpoints such as /login, /password.reset, /password.update, etc.

## Try Admin API's User endpoints

  1. Browse to http://localhost:4000/admin/api/docs
  2. Click the Authorize button
  3. Use the value below for UserAuth:

    OMGAdmin MzVjM2ZhOGMtNjlhNi00ODkyLTkyNGYtZmQzOGQzMzY3NGI1Okk5U2d5TzVsMzBmdEJlU19ZNWE0SXMzdTYwbVROWkZPWlJTa2xLWnoyU2s6OTY1ZWIxODEtNmU4My00NDJkLWFkY2UtNGI2OGY0ZDAzNzRmOngxa01rWDAyWExINEdmNWpkcjA1Wk40d0lZRk1tLThUVmVvOHZwMFhDZ0E=

  4. Try out User endpoints such as /account.create, /account.assign_user, /access_key.create,
     etc.

Database seeded completed. Enjoy!

Impact
Usual deployment.

Good idea. Let me do that.

@T-Dnzt Please try again.
Note that there's a bit of flickering when typing the password because there's no built-in implementation for password input so we need to repeatedly clear the input in a loop :(

@unnawut Can we specify that the password needs to be 8 chars long and not crash the seeds if they enter an incorrect password? :)
Also, I guess we can't get rid of the ^R when deleting characters?
E-mail (admin@example.com<EMAIL_ADDRESS>Password (autogenerate if not given): ^R
Password (autogenerate if not given): ^R
Password (autogenerate if not given): ^R
Password (autogenerate if not given): ^R
Password (autogenerate if not given):
The password must be 8 characters or more.

@T-Dnzt Now the seeder would re-ask for inputs rather than exiting.
As for ^R, I can't reproduce either on Terminal nor iTerm2 on macOS 10.13.3 :(


Download link on https://github.com/cpp-netlib/cpp-netlib is not up to date

At https://github.com/cpp-netlib/cpp-netlib it says

You can find official release packages of the library at:
http://github.com/cpp-netlib/cpp-netlib/downloads

but that page does not contain releases newer than 0.9.4 while the current release is 0.12.0.
So either update http://github.com/cpp-netlib/cpp-netlib/downloads to include newer releases or update the download link.

You're right -- we host the links on the website now (http://cpp-netlib.org/) from where you can get the latest downloads. This documentation for the project is included in the README.rst file at the root of the project directory.
Note that we don't allow listing all the packages available for download (they're hosted on Google Cloud Storage), but we try and regularly update the website whenever there's a new release out.
I think we should just point to the official website and let users download the officially-released tar-balls from there.
What do you think?

Linking to the official website for downloads is perfectly fine I think, although I would like there to be a simple way to download older releases for those times when that is what you want. Having this "hidden away" on a separate old releases page is fine.
When someone tries to compile a program with an older version of cpp-netlib as dependency (and which does not compile with the latest version), then it is frustrating if the project website does not have those available.
I just needed to compile with version 0.11.2, and copying and changing the link from http://downloads.cpp-netlib.org/0.12.0/cpp-netlib-0.12.0-final.tar.bz2 to http://downloads.cpp-netlib.org/0.11.2/cpp-netlib-0.11.2-final.tar.bz2 worked fine, but that was just guessing and luck on my part, it is not a solution that scales since for instance http://downloads.cpp-netlib.org/0.9.4/cpp-netlib-0.9.4-final.tar.bz2 is not a valid link. So please do provide access to older releases.

Good points -- we should make the following two changes:

Make a change to the website so we have a list of all the previous releases and how to get them.
Host all the downloadable binaries in Google Cloud Storage, and use a sane/consistent naming scheme for the URLs so those could be deduced mechanically (like how we have it now).

I don't think I can get to it anytime soon (been swamped recently with other things) but I do think this is important to address.


On iOS the mail app opens but cursor sets on first position of mail body

Hello, I like to report an issue that whenever I open the email app via :
Email(to =<EMAIL_ADDRESS>subject = 'Query', body = 'lorem ipsum is a dummy text', cc = false, bcc = false)
Current behaviour : the mail app opens but the cursor sets on first position and keyboard opens out. Need to know if this can be changed or not.
Expected : cursor should placed on the end of body, keyboard not opens as in rest of the apps I checked out, their keyboard not opens.
Thanks
prashant

Interesting - I don't think there is much control because it depends on the actual email program (this lib just opens it) - I will leave this open as a potential feature request


Be able to import usage data from csv or json

I like(d) the possibility to import usage data from google analytics. Sadly this feature will be no longer available for us, because we switch to a different tracking technology.
It would be nice to also support some generic data format like csv or json, which could be used to import usage data.
Surprisingly I could not find any mentions in the repo or issue tracker about that.

Because Simple Analytics uses json, would be something like this by just including browser_names array be enough? https://simpleanalytics.com/simpleanalytics.com.json?version=5&fields=browser_names


switch interactive dataset to positive/unlabeled/negative

this is a functional change to the interactive approach, and should not be merged until we confirm that we didn't break anything (else) during refactoring.
the functional changes are in active learning:
(1) previously, we would ignore any "negative" responses from the teacher, rather than treating them as known negatives. this actually didn't make a difference though because...
(2) previously, all of the ground atoms that we did not ask about would be treated as negative examples (because they're unlabelled). that's bad, especially because we generally ask about one or a few ground atoms out of many possible, so there would be a whole lot of false negative ground atoms collected during active learning, and active learning could ultimately be harmful. so this change is somewhat of a bug fix.

code changes lgtm. but i don't understand what the functional change is, exactly -- it looks like a cosmetic change to me. could you expand the comment at the top of the PR?

thanks, updated

I see. The functional change is that you're not looping over all possible ground atoms during the setup of the classifier anymore. It's only happening once during offline learning. Which makes the difference occur in active learning. Right?

I see. The functional change is that you're not looping over all possible ground atoms during the setup of the classifier anymore. It's only happening once during offline learning. Which makes the difference occur in active learning. Right?

yeah exactly


Image processing example

This is what I came with to introduce tasks and workflows with a "real" example.  The workflow is a bit contrived; if anyone has any better ideas, let me know.  This example even has embedded doctests ensuring they continue working.  It is probably worth considering doing something similar to the facebook graph example as well.
Also, the build will fail until #166 is pulled in.

I really like the idea of testing our tutorials, I thought about it but didn't know sphinx.ext.doctest existed. I'll add tests to mine afterwards.

Good idea for testing your example @danlamanna. I really like these examples - I suggest we link to them directly from the main page - maybe a blurb between the first and second paragraphs? Currently we only link to the API and plugins docs.

@jbeezley ready for final review? @kotfic: cool, sounds like a good mechanism for specifying analysis code in Python. Are you using a code serialization library? @ronichoudhury: The run function @kotfic is talking about sounds similar to the tangelo entry point - could we somehow normalize the two so a tangelo endpoint could be run through romanesco remotely automatically, perhaps with a decorator? Not an immediate need but that would be super cool.

@jeffbaumes Yes, I think everything brought up has been addressed.

@jbeezley Could you put a 1-sentence link to the examples page on the main docs page? Once that is there LGTM.

:clap:


support micro timestamp

Fix #310

thanks for making this change, do you have a chance to add a ut?

#310

@pan3793   let me take a look.
By the way,  how to build the java tar locally?
https://housepower.github.io/spark-clickhouse-connector/developers/01_build_and_test/
this said it should occur in build/,  but I don't find it

Oh, I forget to update the docs when switching the default Spark version from 3.4 to 3.5, the jar should be at spark-3.5/clickhouse-spark-runtime/build/libs/
➜  Projects cd spark-clickhouse-connector
(scc) ➜  spark-clickhouse-connector git:(master) ./gradlew clean build -x test
Starting a Gradle Daemon (subsequent builds will be faster)

> Task :clickhouse-core:compileScala
[Warn] : two feature warnings; re-run with -feature for details
one warning found

> Task :clickhouse-spark-3.5_2.12:compileScala
[Warn] /Users/chengpan/Projects/spark-clickhouse-connector/spark-3.5/clickhouse-spark/src/main/scala/org/apache/spark/sql/clickhouse/ExprUtils.scala:159:21: non-variable type argument Any in type pattern org.apache.spark.sql.connector.expressions.LiteralValue[Any] is unchecked since it is eliminated by erasure
one warning found

BUILD SUCCESSFUL in 29s
33 actionable tasks: 32 executed, 1 up-to-date
(scc) ➜  spark-clickhouse-connector git:(master) ll spark-3.5/clickhouse-spark-runtime/build/libs/
total 2688
-rw-r--r--  1 chengpan  staff   261B May 10 13:59 clickhouse-spark-runtime-3.5_2.12-0.8.0-SNAPSHOT-empty.jar
-rw-r--r--  1 chengpan  staff   261B May 10 13:59 clickhouse-spark-runtime-3.5_2.12-0.8.0-SNAPSHOT-javadoc.jar
-rw-r--r--  1 chengpan  staff   261B May 10 13:59 clickhouse-spark-runtime-3.5_2.12-0.8.0-SNAPSHOT-sources.jar
-rw-r--r--  1 chengpan  staff   1.3M May 10 13:59 clickhouse-spark-runtime-3.5_2.12-0.8.0-SNAPSHOT.jar

you can skip changes for spark-3.4 and spark-3.3, just focus on clickhouse-core and spark-3.5, there is a half-auto script to backport the patch to older spark versions.

There is no test suite that I can easily extend....  (and I am not familiar with java/scala..
Probably I'll do a system test with the generated tar..

Okay~

you can construct a simple case and leave it in the comments, I will find time to add it to UT later

Previous
.config(
    "spark.jars.packages",
    # "com.github.housepower:clickhouse-spark-runtime-3.4_2.12:0.7.3,com.clickhouse:clickhouse-jdbc:0.4.6"
    "com.clickhouse:clickhouse-jdbc:0.4.6"
)

With this fix
 .config(
    "spark.jars",
    "/home/ubuntu/spark-clickhouse-connector/spark-3.5/clickhouse-spark-runtime/build/libs/clickhouse-spark-runtime-3.5_2.12-0.8.0-SNAPSHOT.jar"
)

can try both json and binary for spark.clickhouse.read.format?

.config("spark.clickhouse.read.format", "json")
in pyspark?
tested,  same.

the default value is "json", if "binary" works too, it's good

yea I tried both

Thanks, merged to master

when will we release?


Proposing the fixed announcement for CommunityNFT contract deployment

This retweeted tweet isn't loading for me for reveiw, Anyone else experiencing a dead link?
https://twitter.com/Dexaran/status/1567900923279835136

checked from mobile - it seems that everything works fine for me

This retweeted tweet isn't loading for me for reveiw, Anyone else experiencing a dead link?
https://twitter.com/Dexaran/status/1567900923279835136
Pulled from Dexaran's feed, links match. Weird- not sure why it wasn't loading in any browser for me. https://twitter.com/Dexaran/status/1567900923279835136

It doesn't seem to load on PC, same issue here.

This retweeted tweet isn't loading for me for reveiw, Anyone else experiencing a dead link?
https://twitter.com/Dexaran/status/1567900923279835136
Pulled from Dexaran's feed, links match. Weird- not sure why it wasn't loading in any browser for me. https://twitter.com/Dexaran/status/1567900923279835136

It doesn't seem to load on PC, same issue here.

yeah i'm on PC as well.

This retweeted tweet isn't loading for me for reveiw, Anyone else experiencing a dead link?
https://twitter.com/Dexaran/status/1567900923279835136

checked from mobile - it seems that everything works fine for me

Did you adjust something? it appears to be loading now. Strange.

Appears to have worked
https://twitter.com/ETC_Network/status/1567935931176321029

While it shouldn't... 👉 https://github.com/ethereumclassic/twitter-together/issues/19

This tweet's formatting was incorrect.
It should be
---
retweet: blah
---

Text

Instead it was
retweet: blah

Text

Hence you an see "retweet" at the top of the tweet when it was published.


Proper way to import markercluster

Hi guys, what's the proper way to include markerclusterer in an angular project in order to make the type definition work?

Google found this https://github.com/Asymmetrik/ngx-leaflet-markercluster
We don't do support for angular here sorry.


Feat #791 mobilefirst changes

fixes #791
fixes #795
this pull request is to heighten the gui support for mobile devices, this can be tested directly on your mobile device or with the use of most browsers (chrome, and firefox) when you set a specific device. another useful "tool" is the blisk browser (https://blisk.io/)
Be aware that this pull request also fixed the headers so make sure that none of the views we have is broken due to it before merging

i tried it on the mobile phone, where it seems to look nice, but afterwards i tested in the normal browser and now i have a wrong display-mode there:


[Deprecated] this.pickFiles - Ember-cli 0.2.6

Upgrading from Ember-cli 0.2.5 to 0.2.6 causes this deprecation warning followed by the error described blow while trying to start the ember server.
[Deprecated] this.pickFiles is deprecated, please use broccoli-funnel directly instead  [addon: ember-cli-jquery-ui]

Cannot read property 'rebuild' of undefined
TypeError: Cannot read property 'rebuild' of undefined
    at Builder.wrapIfNecessary (/home/me/project/name/node_modules/ember-cli/node_modules/broccoli/lib/builder.js:136:18)
    at readAndReturnNodeFor (/home/me/project/name/node_modules/ember-cli/node_modules/broccoli/lib/builder.js:44:17)
    at /home/me/project/name/node_modules/ember-cli/node_modules/broccoli/lib/builder.js:92:24
    at lib$rsvp$$internal$$tryCatch (/home/me/project/name/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:489:16)
    at lib$rsvp$$internal$$invokeCallback (/home/me/project/name/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:501:17)
    at /home/me/project/name/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1095:13
    at lib$rsvp$asap$$flush (/home/me/project/name/node_modules/ember-cli/node_modules/rsvp/dist/rsvp.js:1290:9)
    at process._tickCallback (node.js:355:11)

Thanks Roberto. Looks like I have some work cut out for me.

Strangely, I'm not using pickFiles.

i catch the same error.

Still having the issue. I'd appreciate anyone's help on this.

The issue is in ember-cli. Reported here: https://github.com/ember-cli/ember-cli/issues/4205

This bug has been fixed in ember-cli master branch. Please use Ember-CLI master for now; otherwise wait for Ember-CLI 0.2.7

Ember CLI 0.2.7 is now available. Upgrading fixes this issue.


boards: arm: nrf: remove note about board name change

Nordic Dev Kit board names were changed in Zephyr
v2.3 release, following the standard Board deprecation
policy. Two releases later we do not need to keep
references to the old names in the boards' documentation.
Signed-off-by: Ioannis Glaropoulos<EMAIL_ADDRESS>

There's one more such note to be removed. See thingy52_nrf52832.

Yeap, we keep forgetting this one. I think it would actually be good to have a page describing which boards each individual/company maintains.

There's one more such note to be removed. See thingy52_nrf52832.

updated

There's one more such note to be removed. See thingy52_nrf52832.

Yeap, we keep forgetting this one. I think it would actually be good to have a page describing which boards each individual/company maintains.

Those should be all. ;)
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_programming.html#boards-included-in-sdk-zephyr

There's one more such note to be removed. See thingy52_nrf52832.

Yeap, we keep forgetting this one. I think it would actually be good to have a page describing which boards each individual/company maintains.

Those should be all. ;)
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_programming.html#boards-included-in-sdk-zephyr

Thanks @ru-fu


Switch to C++17

Description
This PR switches CppMicroServices to build with -std=c++17 (and equivalents on other platforms). Additionally, minimum compiler versions, both tested and recommended are updated to reflect c++17 support.
Signed-off-by: The MathWorks, Inc<EMAIL_ADDRESS>

Codecov Report

Merging #654 (c863b4d) into development (d955a42) will decrease coverage by 1.90%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           development     #654      +/-   ##
===============================================
- Coverage        90.57%   88.67%   -1.91%
===============================================
  Files              250      132     -118
  Lines            13428     6453    -6975
===============================================
- Hits             12163     5722    -6441
+ Misses            1265      731     -534

Impacted Files
Coverage Δ

compendium/LogService/src/LogService.cpp
0.00% <0.00%> (-100.00%)
:arrow_down:

...mework/include/cppmicroservices/ServiceException.h
0.00% <0.00%> (-100.00%)
:arrow_down:

framework/include/cppmicroservices/detail/Log.h
50.00% <0.00%> (-47.15%)
:arrow_down:

...mework/include/cppmicroservices/ServiceReference.h
60.00% <0.00%> (-40.00%)
:arrow_down:

framework/include/cppmicroservices/Any.h
65.38% <0.00%> (-28.44%)
:arrow_down:

...ework/include/cppmicroservices/detail/ScopeGuard.h
80.00% <0.00%> (-20.00%)
:arrow_down:

framework/src/bundle/BundleRegistry.cpp
81.02% <0.00%> (-10.55%)
:arrow_down:

framework/src/service/ServiceListeners.cpp
93.72% <0.00%> (-6.28%)
:arrow_down:

...mework/src/service/ServiceReferenceBasePrivate.cpp
86.69% <0.00%> (-6.25%)
:arrow_down:

framework/src/util/LDAPProp.cpp
89.33% <0.00%> (-4.69%)
:arrow_down:

... and 189 more


Firefox - jsTree is stuck on Loading

Hi I noticed that in Firefox I'm running into this issue (#1490) even though my Firefox is updated to 47.0.1, and I'm using Windows 7.    In the demo, and the application I'm using it for, in Firefox it gets stuck on "Loading" without producing any errors.

I had a coworker run it, and they were able to successfully load it.


Fix attribute error in read_checks function

Closes https://github.com/fastai/fastdownload/issues/11
I tried the first example on the fastdownload README page, using the url of one of the standard fastai datasets available on S3. It raised an attribute error, because variable fmod was an empty dictionary instead of the expected pathlib object.
from fastdownload import FastDownload

url = 'https://s3.amazonaws.com/fast-ai-sample/mnist_tiny.tgz'
d = FastDownload()
path = d.get(url)

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-50-389349d26777> in <module>
      3 url = 'https://s3.amazonaws.com/fast-ai-sample/mnist_tiny.tgz'
      4 d = FastDownload()
----> 5 path = d.get(url)

~/anaconda3/envs/napari-dev/lib/python3.9/site-packages/fastdownload/core.py in get(self, url, extract_key, force)
    119             data = self.data_path(extract_key, urldest(url, self.arch_path()))
    120             if data.exists(): return data
--> 121         self.download(url, force=force)
    122         return self.extract(url, extract_key=extract_key, force=force)

~/anaconda3/envs/napari-dev/lib/python3.9/site-packages/fastdownload/core.py in download(self, url, force)
     94         "Download `url` to archive path, unless exists and `self.check` fails and not `force`"
     95         self.arch_path().mkdir(exist_ok=True, parents=True)
---> 96         return download_and_check(url, urldest(url, self.arch_path()), self.module, force)
     97
     98     def rm(self, url, rm_arch=True, rm_data=True, extract_key='data'):

~/anaconda3/envs/napari-dev/lib/python3.9/site-packages/fastdownload/core.py in download_and_check(url, fpath, fmod, force)
     61     "Download `url` to `fpath`, unless exists and `check` fails and not `force`"
     62     if not force and fpath.exists():
---> 63         if check(fmod, url, fpath): return fpath
     64         else: print("Downloading a new version of this dataset...")
     65     res = download_url(url, fpath)

~/anaconda3/envs/napari-dev/lib/python3.9/site-packages/fastdownload/core.py in check(fmod, url, fpath)
     47 def check(fmod, url, fpath):
     48     "Check whether size and hash of `fpath` matches stored data for `url` or data is missing"
---> 49     checks = read_checks(fmod).get(url)
     50     return not checks or path_stats(fpath)==checks
     51

~/anaconda3/envs/napari-dev/lib/python3.9/site-packages/fastdownload/core.py in read_checks(fmod)
     40 def read_checks(fmod):
     41     "Evaluated contents of `download_checks.py`"
---> 42     if not fmod.exists(): return {}
     43     txt = fmod.read_text()
     44     return eval(txt) if txt else {}

AttributeError: 'dict' object has no attribute 'exists'

This PR avoids that error, by checking whether fmod is an empty dictionary before continuing.

I'm not super familiar with nbdev, so if there's anything about the process I should have done differently please let me know.
I looked at both:

the fastdownload contributing guide, and
the nbdev tutorial

...but I don't think I had things working properly (for example, running nbdev_test_nbs on the master branch didn't pass cleanly, which might indicate something is wrong with my setup)

Note: I think this is probably unrelated to https://github.com/fastai/fastdownload/issues/16

I have the same issue

Many thanks @GenevieveBuckley !

@jph00 Just wanted to note that the latest version of fastdownload on PyPI (0.0.5) still has this bug. A new release would be amazing 😄 I'm happy to help where I can.
For interest sake, I'm currently working around it by installing from GitHub (pinned to the latest commit):
pip install git+https://github.com/fastai/fastdownload.git@2ec6563fef7c92ea975871c8cbcea1a0b02917a1

Oh sorry @seeM my bad! Thanks for letting me know. Just pushed a release.

Thank you, very much appreciated. I really love the library! It's such a pleasure to use 😌


Enhancement/Feature Request: date and forKSP fields

So just two more informative fields:
VERSION
{
  version = x.y.z
  versionName = Bad Banana!
  versionDate = 2020 Mar 15
  versionKSP = 1.9.1
  change = thank you in advance.
  change = that darn zer0Kerbal!
  CHANGE
  {
    change = added two new fields
    subchange = versionDate: text field for version release date
    subchange = versionKSP: text (or version) field for version KSP version target
  }
}

@zer0Kerbal So sorry I didn't see this until now!
I'd be happy to add those fields in, just as long as you know that I'm not going to be able to lock anyone out of the game (it would only display along side the other information about the mod). I think that if a mod truly requires a certain game version, that should be up to the mod to implement the lock.

Added in commit e96cfd4a8415bd20d8922b07ac4118663e72084a


Fixing broken stationcollector test

I can't figure out why github is trying to generate a PR with all of my changes when both of our branches are up to date - what's going on?

Ah, it's probably because I squashed and merged the PR.
Whenever I fork a repo, I try to keep my master in sync with the upstream master, just in case they end up doing squashing or rebasing that might conflict.


Has many through , attributes not working

I have my associations as
Report
       has_many :projects
       has_many :project_milestones, through: :projects
       has_many :members, through: :projects

        accepts_nested_attributes_for :key_activities , :reject_if => :all_blank, :allow_destroy => true
	accepts_nested_attributes_for :risks , :reject_if => :all_blank, :allow_destroy => true
	accepts_nested_attributes_for :projects , :reject_if => :all_blank, :allow_destroy => true
	accepts_nested_attributes_for :project_milestones , :reject_if => :all_blank, :allow_destroy => true
	accepts_nested_attributes_for :members , :reject_if => :all_blank, :allow_destroy => true

and i try to deep clone
r = Report.last.deep_clone :include => [:key_activities, :risks, {:projects => [:project_milestones, :members]}]

i am getting all attributes except project_milestones and members
r.projects.last.members.last
=> #<Member:0x007f8234394ed8 id: nil, name: "", worked_hrs: "", created_at: nil, updated_at: nil, project_id: nil>

what could be wrong here? :o

At first sight it doesn't look like this issue is caused by deep_cloneable. The code eventually calls 'dup()' on the record, which should copy the member attributes. It might of course be related to your environment (ruby/rails version). Could you provide a failing test? The current test for hm-through is defined here: https://github.com/moiristo/deep_cloneable/blob/master/test/test_deep_cloneable.rb#L322.

Sorry it was an error with my code. Its working like a charm
Thanks a lot


Support velox user exception log config to gain performance

Description
Currently, velox throw  and log exception per row regardless that the case  in line with expectations.
Let's see pseudocode for example
get_json_object(strCol, '.key').cast(Integer)

It may cause VeloxUserError contains message Failed to cast from VARCHAR to INTEGER
Many cases similar with above example are line with expectations, however they are inevitable to cause user exception, the process of generating and logging error message result in significant performance issue

Just saw this , we fix this as part of optimizing casts. thanks for reproting and closing the issuel

Yeah, I closed it when realizing it
Could you help to review https://github.com/facebookincubator/velox/pull/6239
This may gains performance by avoid generating traceStack when VeloxUserError happens


changed initialization of slots to match official

In slot attention.py I changed the initialization of slots to match official implementation (fixed a typo in previous pull request)

@Horse7354 ok, i released this in 1.1.0!

@Horse7354 ok, i released this in 1.1.0!


volumio 3 upgrade

Not sure if this has been tested - haven't upgraded yet...
Will there be any problems if an upgrade is done to volumio 3?
Thanks in advance

I'm successfully running pypPiper in Volumio 3.173.
I made a full reinstall of Volumio on a fresh formatted SD card and therefore also reinstalled pydPiper.
Do not know if it will work if you use the Volumio upgrade function...

Hi,
The music data form and API haven't changed, so in theory yes. :smile:


Remove bullet left-margin override

Bug/issue #, if applicable: 101632086
Summary
Removes the extra bullet left-margin override for docs only, making bullet lists flush to the left.

Dependencies
NA
Testing
Use the provided archive to test:
build.zip
Steps:

Visit - http://localhost:8081/documentation/simple
Assert the list is rendered properly

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests - NO, css only
[ ] Ran npm test, and it succeeded
[ ] Updated documentation if necessary

@swift-ci test


Reorganize the Linux module to reuse more code

This issue is a follow-up of the discussion started with #368 trying to be more general. The main idea is that the separation between different libc as a first branching inside the Linux module actually leads to much more code duplication as could be possible by branching by platform first, and maybe (we shall see if it is possible) have the libc and the platform be orthogonal.
In this issue, I wish to propose a working plan for this severe refactoring, to get approval before anybody, me included, starts working.
Step 0: the MIPS module
The recently created MIPS and MIPS64 modules are actually MIPS-glibc and MIPS64-glibc. Maybe, to make that clearer, we should put them in their logical place, that is inside other/b32 and other/b64 module. Maybe it will induce too much changes to be worth the effort, so let this be optional.
Step 1: get an appropriate test platform for MIPS(64)
@alexcrichton expressed concern on this matter, and it should be solved before any great amount of work is done. Question: is #369 enough or do we need more?
Step 2: set up the working space
We can than create a common submodule, with its own submodules b32, b64 and every necessary platform, to receive everything that is common to every one of the three libc. This submodule would be included alongside the remaining musl and other and mips(64) modules, to make sure nothing is lost while the work is in progress.
Step3: put in common everything that can be put in common
To make this easier, a few recommendations.
Type definitions
As much as possible, use the C types in the right part of the definition. For instance, clock_t is defined as i32 in mips and other/b32, as i64 in other/b64, and as c_long in musl. These are actually all longs. Using ::c_long for all of them would make it possible to have a single definition for all Linuxes, that would actually be in notbsd given that android has the same definition.
Structure definitions
It might not always be possible, but the apparent discrepancies in definitions between different libc are generally less than they seem. An example is given here.
To make this work, it might be necessary to have some cfg elements to mimic the macros like __USE_FILE_OFFSET64. How exactly would that be possible?
Macros and functions
Apart from a few exceptions, these should really be the same across the different libc and only differ in the platforms.
Step 4: see if libc and platform are orthogonal
That is, make sure that all the definitions remaining in other and musl are platform independent. if this has been achieved, merge common/mod.rs into linux/mod.rs, and have a separate if cfg for platforms and for libc.
Step 5: bonus
See if some of the definitions now in linux/mod.rs can be pulled further up in the tree.

Note that most of the directory structure and hierarchy of this crate is explicitly not optimized for sharing code. Rather it's optimized for readability and clarity of definitions themselves.
In that sense it's totally fine to make copies of entire modules when adding new platforms, it's no skin off our backs!