Fix documentation author

Fixes docs to mark NVIDIA as the author.

Testing a script, apologies for the noise. I'll reopen.

/merge

Thanks Bradley! 🙏


Feature request: support nested groups in SSH

My original PR support nested folders.
I don't know how to support nested groups in pug template file.

I would rather not overload the interface with the nested groups and it makes the navigation clunky. I'll leave this ticket open to see whether there are many users who would like this!

+1

+1

+1

+1

+1 here also :)

+1
I'd love to switch to tabby (from mremoteng), but the lack of nested groups makes it impossible for me. I have many (literally hundreds) connections to manage across multiple environments, which is just not possible without nested/hierarchical groups.


react slick slider not working in first render for responsive design

 var settings = {
        dots: false,
        arrows: true,
        infinite: false,
        speed: 500,
        slidesToShow: 4,
        slidesToScroll: 4,
        initialSlide: 0,
        responsive: [
            {
                breakpoint: 1024,
                settings: {
                    slidesToShow: 3,
                    slidesToScroll: 3,
                    initialSlide: 0,
                }
            },
            {
                breakpoint: 768,
                settings: {
                    slidesToShow: 2,
                    slidesToScroll: 2,
                    initialSlide: 0,
                }
            },
            {
                breakpoint: 640,
                settings: {
                    slidesToShow: 1,
                    slidesToScroll: 1,
                    initialSlide: 1,
                }
            }
        ]
    };

Would it be possible to have initialSlide be 1 if the screen is less than 640px wide when the Slider first mounts? slidesToShow will correctly be 1 instead of 3, could we override initialSlide the same way. I want to fix this for both web and mobile. For the first render in the web 4 slides are coming. but when the screen size is below 1024, there are no slides coming in the first render

Hello! I'm running into the same issue were you able to find a solution? Thank you!

Same issue here. Adding more context: I believe responsive attribute is read after mounting with the slidesToShow property.
What I had to do was to choose mobile instead of desktop and I did slidesToShow: 1 and responsive as below. It will first render with 1 slide and then shifts to 3 - giving bad performance results for CLS (and LCP on some cases)
    responsive: [
      {
        breakpoint: 2048,
        settings: {
          slidesToShow: 3,
          slidesToScroll: 1,
        },
      },
      {
        breakpoint: 1024,
        settings: {
          slidesToShow: 3,
          slidesToScroll: 1,
        },
      },
      {
        breakpoint: 991,
        settings: {
          slidesToShow: 2,
          slidesToScroll: 1,
        },
      },
      {
        breakpoint: 576,
        settings: {
          slidesToShow: 1,
          slidesToScroll: 1,
        },
      },
    ],


Update redix.ex

The world's tiniest PR.

Argh, the commit message turned into something generic because I lazily used the "edit through the web" option.

May be tiny but it's still contributing, right? :D thanks a lot @apenney!


Update to Readme.md

Made some changes and introduced Free-Tier, Always-Free

Removed "build" from the 3rd use case.
I have observed further issues that will be addressed in my next review.

Addressed all comments.


AuthFragments are not visible

First of all the concept is great. I tried it in my app but when I start LoginActivity at first time it works fine but after that when I press back button and again open LoginActivity AuthFragment i.e Login and Signup fragments do not appear.

Did you use the app that I provided?Or you just created your own app with the same implementation? If you have your own app, make sure that you properly handle the activity lifecycle. When you navigate to another screen and then go back to the app, your activity gets recreated(sometimes it doesn't on my phone). I tried the same with my app and everything works fine.

Have you resolved the issue?If so, what was the problem?

@vpaliyX I cloned the project and ran it on emulator and device. Also, I integrated it in my app. The behaviour is same. But I've found the workaround for it. Just comment out line in LoginActivity.
//                            background.scrollTo(-background.getWidth() / 2, 0);
This may be a issue of the backround scaling and srcolling. I don't know what will be the good solution but it works.

@peswanibros What device did you use to run the app? And what API?(for both an emulator and real device)
If you remove this line, the background image will be different. That line just scrolls to the very left of the image, it has noting to do with setting up the fragments. But if it works for you, I'm glad it does.

@vpaliyX  OnePlus3, emulator API 24. Even I tried app from play store also. Same is happening. You start the app and press back button and again open the app from App Menu not from recents.

That's a good catch! I just ran the app on a device with API 24 and happened exactly what you said. The fragments are not being shown after the app has been launched from the app menu one more time.
But I've figured this out. The problem here is that I'm trying to initialize the adapter before the ViewPager has been laid out. In this case when we call  the pager.getWidth() method in the constructor, it returns 0. Which affects the factor value, it simply turns out to be infinity. As a result, our fragment's width is always zero.
Check out my . The solution is to initialize the adapter after the ViewPager has been laid out using the ViewPager.post() method.

I guess the issue has been resolved so I'm closing this.

Thanks for your time and effort really appricated.

Thank you for the issue. I should have definitely tested that on a lower API.


enable ci for arm

enable drone ci for arm builds and update dapper to not check for processor types
Problem:

Solution:

Related Issue:
https://github.com/harvester/harvester/issues/371
Test plan:

CI failure on the upgrade is a known issue. I already fixed on https://github.com/harvester/node-disk-manager/pull/60


Authen to google problem

 Issue by tntkhang
Friday Jun 16, 2017 at 03:18 GMT
Originally opened as https://github.com/googlesamples/android-fit/issues/23

When I run app the pop-up select email to authen to Google, I select the email but the app always throw StatusCode = CANCEL. Does the authen funtion out of date ? Do we need to switch to this authen guide: https://developer.android.com/training/wearables/apps/auth-wear.html#configure-google-sign-in

 Comment by Kagetsuki
Wednesday Sep 20, 2017 at 09:04 GMT

I'm having the same issue, did you ever figure it out?

 Comment by yoshimaa
Friday Oct 20, 2017 at 02:48 GMT

@tntkhang  @Kagetsuki
this android-fit sample is  too bad, but anynone dont fix that problem.

 Comment by Kagetsuki
Friday Oct 20, 2017 at 02:52 GMT

I ended up using a bunch of different guides. Everything from Google is outdated. The permission names are different, you have to ask for permission with a method at run-time, a bunch of the method names have changed. The library version in samples is 3 major versions out of date. If Google is wondering why there's so few apps with Google Fit integration - this is the reason why.Your official documentation and samples are garbage.

 Comment by thisisjatinrana
Friday Aug 17, 2018 at 09:33 GMT

Check if internet connectivity is there. I was facing same issue later found out that wifi was off.

 Comment by paul-ridgway
Tuesday Feb 12, 2019 at 14:40 GMT

Make sure you have associated an OAuth 2.0 client id with your keystore - https://developers.google.com/fit/android/get-api-key


[SUG] Help menu can be redesigned (non-JWoC)

Description :
The help menu displays enough info to run CODEIt on a system. But it'd be great if anyone suggests a new design for that.
Examples: Here the logo used is called ANSI logo. Instead of that some logo can be introduced to the script.
Any color codings can be changed here a bit for readability.
This issue isn't a fixed one from my side. Anyone can take up and suggest new design for menu. After seeing them, I'll take the best one for menu and have you assigned.

I want to contribute, what changes are you looking for?

I want to contribute, what changes are you looking for?

Hello @Kushagrabainsla sorry for late reply. If you want to contribute to this one, I need some suggestions first for the help menu. You can run this project and see what kind of work is needed. For now, it's good. But you can suggest what is needed. Example: color changes, logo change etc

Hello @Kushagrabainsla sorry for late reply. If you want to contribute to this one, I need some suggestions first for the help menu. You can run this project and see what kind of work is needed. For now, it's good. But you can suggest what is needed. Example: color changes, logo change etc

Hey, Assign this to me, I'll make the help menu look more professional.

Hey, Assign this to me, I'll make the help menu look more professional.

Hey, Assign this to me, I'll make the help menu look more professional.

@Kushagrabainsla are you doing this for JWoC? If so, I can assign you soon before JWoC starts. Please be patient. Don't worry I'll assign you for sure

Hey, Assign this to me, I'll make the help menu look more professional.

@Kushagrabainsla are you doing this for JWoC? If so, I can assign you soon before JWoC starts. Please be patient. Don't worry I'll assign you for sure

I’m sorry if I’m being impatient, but it’s my first time contributing and
what’s jwoc, I only know about gsoc.
On Wed, 20 Jan 2021 at 6:45 PM, Aadhitya A<EMAIL_ADDRESS>wrote:

Hey, Assign this to me, I'll make the help menu look more professional.
@Kushagrabainsla https://github.com/Kushagrabainsla are you doing this
for JWoC? If so, I can assign you soon before JWoC starts. Please be
patient. Don't worry I'll assign you for sure
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Arch2x/codeit/issues/15#issuecomment-763598582, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARINTNF3QLARMMVG2MAUACDS23JPRANCNFSM4WFLXCIQ
.

I’m sorry if I’m being impatient, but it’s my first time contributing and
what’s jwoc, I only know about gsoc.
On Wed, 20 Jan 2021 at 6:45 PM, Aadhitya A<EMAIL_ADDRESS>wrote:

Hey, Assign this to me, I'll make the help menu look more professional.
@Kushagrabainsla https://github.com/Kushagrabainsla are you doing this
for JWoC? If so, I can assign you soon before JWoC starts. Please be
patient. Don't worry I'll assign you for sure
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Arch2x/codeit/issues/15#issuecomment-763598582, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARINTNF3QLARMMVG2MAUACDS23JPRANCNFSM4WFLXCIQ
.

Oh wait. Okay. So, wait. I'll unassign this issue as it's meant for a contest. Then, just a moment. I'll remove tags and assign to you. @Kushagrabainsla

Oh wait. Okay. So, wait. I'll unassign this issue as it's meant for a contest. Then, just a moment. I'll remove tags and assign to you. @Kushagrabainsla

You're assigned @Kushagrabainsla. You can start doing the work

You're assigned @Kushagrabainsla. You can start doing the work

BTW answer this one Q, how did you come across this repo? Through goodfirstissues.com ??

BTW answer this one Q, how did you come across this repo? Through goodfirstissues.com ??

I’m sorry if I’m being impatient, but it’s my first time contributing and what’s jwoc, I only know about gsoc.
…
On Wed, 20 Jan 2021 at 6:45 PM, Aadhitya A @.***> wrote: Hey, Assign this to me, I'll make the help menu look more professional. @Kushagrabainsla https://github.com/Kushagrabainsla are you doing this for JWoC? If so, I can assign you soon before JWoC starts. Please be patient. Don't worry I'll assign you for sure — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARINTNF3QLARMMVG2MAUACDS23JPRANCNFSM4WFLXCIQ .

No issues! You should have said this first. No problem. This issue was meant for JWoC participants. Don't worry if you don't know about JWoC (registration is closed and it's a beginner friendly contest). I thought you're a participant and said like that. No problem! You're assigned and you can start your work ASAP now! :)

I’m sorry if I’m being impatient, but it’s my first time contributing and what’s jwoc, I only know about gsoc.
…
On Wed, 20 Jan 2021 at 6:45 PM, Aadhitya A @.***> wrote: Hey, Assign this to me, I'll make the help menu look more professional. @Kushagrabainsla https://github.com/Kushagrabainsla are you doing this for JWoC? If so, I can assign you soon before JWoC starts. Please be patient. Don't worry I'll assign you for sure — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARINTNF3QLARMMVG2MAUACDS23JPRANCNFSM4WFLXCIQ .

No issues! You should have said this first. No problem. This issue was meant for JWoC participants. Don't worry if you don't know about JWoC (registration is closed and it's a beginner friendly contest). I thought you're a participant and said like that. No problem! You're assigned and you can start your work ASAP now! :)

If you've any doubts, contact me @Kushagrabainsla I'll help

If you've any doubts, contact me @Kushagrabainsla I'll help

BTW answer this one Q, how did you come across this repo? Through goodfirstissues.com ??

NO, I just used the explore section to find good first issues.

BTW answer this one Q, how did you come across this repo? Through goodfirstissues.com ??

NO, I just used the explore section to find good first issues.

I see! Anyways, good luck? 👍

I see! Anyways, good luck? 👍

Just a heads-up @Kushagrabainsla you need to make changes on a file called "codeitHelp.py". You need to see that file and decide what changes can be done on help menu...

Just a heads-up @Kushagrabainsla you need to make changes on a file called "codeitHelp.py". You need to see that file and decide what changes can be done on help menu...

Issue solved. Closing now...

Issue solved. Closing now...


fix(zepto): make zepto.js a commonJS file

We will then need to upgrade docsearch. This is somehow a breaking change for everyone relying on the fact that we inserted Zepto in window. Amazing how simple decisions like "Zepto will not be compatible with npm/umd" have such consequences.

This is somehow a breaking change for everyone relying on the fact that we inserted Zepto in window.

I'm convinced no one is using that. And even if it was the case, for me that's just a bug fix and not a major change.

Coverage decreased (-0.1%) to 88.631% when pulling ffb5d4fd51bc50b6a14fa94dedf7f0d248b91519 on fix/no-more-window.Zepto into 428e862570df97cbd98a63528a38cc6312c77739 on master.

And even if it was the case, for me that's just a bug fix and not a major change.

yep yep, its mostly a breaking change for us. If someone uses the new autocomplete.js (because of auto update while building) then it will break the build

@vvo I'm very worried about this because it will break WordPress implem again

@vvo I'm very worried about this because it will break WordPress implem again

Why @rayrutjes? it shouldn't change anything except if someone was using the leaked window.Zepto.

@redox The problem is that some plugins will use Zepto if available and fallback to jQuery otherwise.
We had the case were a user was using owlCarousel, and when importing the autocomplete.js lib, his whole script would crash because owlCarousel was no longer available under jQuery but was in fact attached to the Zepto instance.
IMHO opinion, leaking Zepto is not a good idea, and can lead to very hard debugging sessions /cc @vvo

@rayrutjes Those plugins here will never see that we use zepto internally, I removed all references to window.zepto. So it basically mean we are gonna use zepto internally and no one will ever know it. (no plugin will see window.Zepto etc..).

I will do a release tomorrow morning of autocomplete.js/docsearch and places

Ah OK @vvo I thought that it leaked the Zepto in the same fashion as before. All good for me!
Sorry for the noise!


Error deploying to Now

When trying to run serve inside a Now deployment I'm getting this error:
> /home/nowuser/src/node_modules/serve/node_modules/chalk/index.js:65
> ansiStyles.color.closeRe = new RegExp(escapeStringRegexp(ansiStyles.color.close), 'g');
>                                                                          ^
> TypeError: Cannot read property 'close' of undefined
>     at Object.<anonymous> (/home/nowuser/src/node_modules/serve/node_modules/chalk/index.js:65:74)
>     at Module._compile (module.js:573:30)
>     at Object.Module._extensions..js (module.js:584:10)
>     at Module.load (module.js:507:32)
>     at tryModuleLoad (module.js:470:12)
>     at Function.Module._load (module.js:462:3)
>     at Module.require (module.js:517:17)
>     at require (internal/module.js:11:18)
>     at Object.<anonymous> (/home/nowuser/src/node_modules/serve/bin/serve.js:13:17)
>     at Module._compile (module.js:573:30)
>     at Object.Module._extensions..js (module.js:584:10)
>     at Module.load (module.js:507:32)
>     at tryModuleLoad (module.js:470:12)
>     at Function.Module._load (module.js:462:3)
>     at Function.Module.runMain (module.js:609:10)
>     at startup (bootstrap_node.js:158:16)
> npm ERR! code ELIFECYCLE
> npm ERR! errno 1
> npm ERR<EMAIL_ADDRESS>now-start: `serve --single --silent -n ./build`
> npm ERR! Exit status 1
> npm ERR!
> npm ERR! Failed at the<EMAIL_ADDRESS>now-start script.
> npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
> npm ERR! A complete log of this run can be found in:
> npm ERR!     /home/nowuser/.npm/_logs/2017-09-03T18_01_21_728Z-debug.log

Here's a public deployment with the error -> https://zeit.co/sergiodxa/test-cra/qtoxnwjtwk
This started to happen with v6.0.3 and keep with every version since then (it works with older versions).

I am seeing the same issue with ^6.1.0.

I'm also seeing this issue

Is there a yarn.lock or package-lock.json? If so, remove it and try your deployment again. We see this at Chalk every so often because NPM likes to mess up ansi-styles versions from time to time.
Please let me know if that is/isn't the case so I can continue to debug. We haven't seen reports like this on the Chalk end so I'm pretty convinced this is a version mis-match.

@Qix- I ended up fixing with yarn add<EMAIL_ADDRESS>

@mattfysh not really a fix, though. Downgrading shouldn't be the fix.
Did you have a lockfile prior to downgrading?

Agreed, just not sure whether its a serve or chalk issue. Are you having issues reproducing? I could probably give you a few steps for repro if you need it - lmk

Yeah exact steps for reproduction would be great @mattfysh :) Thank you in advance!

create-react-app qix
cd qix
yarn add serve
add to scripts: "now-start": "serve -s build"
now

Closing this now, since it's not fixable by serve or Now.

This seems strange, since it works locally. Downgrading to an old version
of serve also works.
Possibly an issue with now using npm when there is a yarn lock file?
On Tue, 17 Oct 2017 at 3:13 am, Leo Lamprecht<EMAIL_ADDRESS>wrote:

Closed #262 https://github.com/zeit/serve/issues/262.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zeit/serve/issues/262#event-1296560485, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAcs8nUPIKLk5OPTFf-vIifb7dPLEq4Iks5stH3dgaJpZM4PLQrH
.

@sergiodxa @leo @Qix- just learnt that now deploy uses a custom dependency installer that is not npm or yarn. If that custom installer is the cause of this issue, where would I raise this?

Have you tried deploying it again with everything freshly generated and installed? It's working for the team. 😊

@mattfysh To wit, I followed your repro steps and got this successful deployment: https://qix-eochhxpnlv.now.sh/

Yea I just did the same and it worked... I was however able to reproduce this consistently 3 times in a row ~12 hours ago, would be handy if there were some type of tool to highlight recently released libs in a lockfile - but seems to me to have been a dependency tree issue

Oh - this library (serve) was updated 3 hours ago? https://libraries.io/npm/serve

I'm using serve as a local npm package, so it return serve not found error.
The path in /node_modules/serve/bin/serve doesn't resolve.


[OpenAI] Fix samples

Fixes https://github.com/Azure/azure-sdk-for-js/issues/27564

API change check
API changes are not detected in this pull request.


feat: remove binary, fix makefile build/install

@sanchez2210 I'd grab your changes if you don't mind. This is my first project with Makefile and I didn't expect many forks around, but I'm happy to see your fixes and plug them back in. :)

@maricn Go for it, glad you found these useful!


fix(curriculum): fixed typo in TODO step 30

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

HI @KhushiSharma0313 !
Thank you for your interest in contributing to freeCodeCamp.
It looks like you have changed a few files but I am not sure what this PR is supposed to be about.
I updated your title of your post but you mentioned this issue originally.
If you are interested in working on that issue, then you should only be updating one file.
Please revert your changes back to the way they were and only make changes to the file listed in the issue.
Thanks 👍

Hey @KhushiSharma0313
This PR seems to make similar changes as the existing PR #53615. As such, we are going to close this as duplicate.
If you feel you have additional changes to expand upon this PR, please feel free to push your commits and request this PR be reopened.
Thanks again! 😊

If you have any questions, feel free to ask questions on the 'Contributors' category on our forum or the contributors chat room.


Feature/behaviour tree no json

[ ] The tests are passing

Summary
Give a short summary of what the changes are and why you made them. If applicable, apply screenshots as well.
Related issues
If there are related issues, reference them here.
fixes #693
Comments for the reviewer
If there are comments for the reviewer, leave them here
Checklist for the reviewer
This acts as a guide to help you and/or the reviewer to analyze the code.
functionality

Is the code is properly tested?
Is the code working as expected
Is the code is understandable and easy to read
Are proper abstractions made? (no duplicate code, nice use of functions/objects)

style

Variables/objects/classes have proper names
Proper use of variables: nu unused vars, no magic numbers
No possible memory leaks. Mutexes properly used when multithreading? possible pointer issues?
Are smart pointers used?
unused variables?
magic numbers?
well documented?
No unused imports?
No leftover code / unused comments
Proper indentation
Proper use of namespaces

If anyone would like to, please review the changes I made to the ProtoTypeTree class. I am mostly interested in the design of this class. I am aware that outside of this class, there are quite a few issues, which I am fixing now. You can also comment on these if you want, but I am still fixing them anyways.

As @rolfvdhulst mentioned, creating roles within the strategy class is messy. Haico and I discussed this, and we are thinking about creating both the tactics and the strategy in the tree class, which implemenents a strategy interface. The roles will be separate classes. This is because the roles can be used by different tactics. Also I think it would be nice to make some base roles like AttackerRole etc, and then a variation of this, for example, AgressiveAttackerRole, can inherit from this class and only override the functionalities needed. However, I think these classes need to be made when they are necessary and not pre-engineered.


Added embed parameter to iframe src so that the aside is not shown

Requirements for a pull request

[ ] Unit tests related to the change have been updated
[ ] Documentation related to the change has been updated

Description of the Change
The problem was that the aside (left nav) of the card was showing when the card was displayed in MFGUI.
There is a corresponding change to the metaflow card-generating code that checks for the embed parameter and adds a class to the HTML that already triggers CSS to hide the aside.
Alternate Designs
Sending a post message to achieve this seemed overkill.
I looked into having the CSS detect whether it was embedded, without javascript but could not find a solution.
Possible Drawbacks
Users may like the aside and see that what is displayed in MFGUI is different from the downloaded card (which will show the aside with a wider screen)
Verification Process

Run a flow with the changes in https://github.com/Netflix/metaflow/pull/877 e.g. python3 dummyflow.py run --with card
Navigate to the task in MFGUI
Ensure that the aside is not shown for the card.

Release Notes
Adds a param to the card iframe to hide the aside in the card.

Looks all good


Add documentation for reverse-proxy with Ambassador

Pull Request Test Coverage Report for Build 6282

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 44.83%

Totals

Change from base Build 6278:
0.0%

Covered Lines:
17407

Relevant Lines:
38829

💛  - Coveralls


Antialiasing in output

Currently, when converting the graphic to a bitmap image the result is not anti-aliased.
Moreover, applying anti-aliasing techniques manually is rather difficult.
For instance, to apply supersampling, one could create a scaled-up version of the graphic, and then resize down the Image using Pillow's resize with LANCZOS resampling. Due to the lack of a scaling combinator, this requires tedious manual scaling of all dimensions used in the graphic by the user.
Personally, I would suggest adding either:

an antialiasing boolean parameter to the various functions that convert graphic to bitmap (show_graphic, save_graphic, graphic_to_image, graphic_to_pillow_image, ...), maybe leveraging skia ?
a scale parameter to the same output functions.

Hi! Thanks for the suggestion!

an antialiasing boolean parameter to the various functions that convert graphic to bitmap (show_graphic, save_graphic, graphic_to_image, graphic_to_pillow_image, ...), maybe leveraging skia ?

Skia definitely supports antialiasing (via SkPaint), we could easily support it in PyTamaro. I wonder why you are suggesting a parameter, instead of enabling it by default (I could think about performance reasons, but that is quite out of scope for our educational context). I'd like to minimize the number of parameters, in general. Do you have an example in mind for which you would want to have it off?

a scale parameter to the same output functions.

This is deliberately not in PyTamaro because we want to nudge learners to parameterize their own functions and with a scaling function they can avoid doing the work and actually learn (more on this in this research paper that explains PyTamaro's design).

Do you have an example in mind for which you would want to have it off?

Related and opposite question: which situation/graphic prompted you to need anti-aliasing?

Hi @lucach ! Thank you very much for the quick response!
I am not opposed to having antialiasing on by default, of course.
On the contrary, I think this would be great.
For the context, I was trying PyTamaro for the first time this weekend (after a great presentation last Saturday by @hauswirth) and coded the SBB clock from scratch. Unfortunately, when I displayed the result, the image was not as beautiful as I would have expected. To obtain a crisp output, I had to manually scale all dimensions used by a factor 2 and then resize the image using Pillow. SVG output was also a solution, but is more cumbersome to use.
I have read your awesome paper and I totally understand and fully support the argument not to include scaling as a combinator for the definition of graphics.
I would only suggest that it is added as a parameter to the functions producing the final output.
This way, students (and other users) still need to learn parameterize to their graphics if they need to scale shapes to create their graphic, but can zoom in to see the final result.
Now that I think about it, having this scaling parameter for display could also be helpful for visually impaired students that may need to produce a larger version of their graphic to better see it, without needing to tweak the instructions.

After some testing and some performance improvements, I say we can always enable antialiasing.
Rendering 10K characters with antialiasing takes ~750ms, as opposed to ~530ms without. Given that this is a rather extreme test for our purposes, we can afford to have it always enabled.
Change introduced in cb78384e0c15b6b2298162f62c0112f36abb74db (curiously enough, the change itself is one line, but some of our testing assumptions no longer hold -- due to antialiasing, the rendering of a red ellipse no longer only contains purely red pixels).
Thanks for the suggestion @redelmann , it's something we overlooked so far!

I would only suggest that it is added as a parameter to the functions producing the final output.
This way, students (and other users) still need to learn parameterize to their graphics if they need to scale shapes to create their graphic, but can zoom in to see the final result.

I see, that indeed would not be as problematic as the combinator. But my experience suggests that learners would still exploit it: just last week an otherwise excellent project done by a couple of students still did not have proper parameterization for the graphics. They were rendering cards for the game of UNO, and they couldn't produce bigger renderings of a card because of some hardcoded sizes. I totally feel you for the inconvenience (which can be bypassed with SVG, in any case), but I still maintain that it is a valuable learning opportunity. Not including it, at least for the time being  :-)

Thank you very much for the quick implementation! It's great that anti-aliasing can be always on. Just tested it myself and the rendering is beautiful! Thanks for the great work!


UnboundLocalError: local variable 'final_res' referenced before assignment

import jionlp as jio
jio.recognize_location('你好吗')
UnboundLocalError: local variable 'final_res' referenced before assignment

when target text no address info, reponse UnboundLocalError

I have fixed this bug

Got


revel run -a myapp doesn't work(From Creating a new Revel application)

Creating a new Revel application
I tried running the above in a docker golang container.
However, the result is different from what I expected.
Is there any solution?
Thank you for the great development.
root@f7db23552294:/home/me/gostuff#  revel run -a myapp
Revel executing: run a Revel application
Change detected, recompiling
Parsing packages, (may require download if not cached)...panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x6daa4f]

goroutine 323 [running]:
go/types.(*Checker).handleBailout(0xc000552800, 0xc000717c60)
        /usr/local/go/src/go/types/check.go:367 +0x88
panic({0x950300?, 0xdf3660?})
        /usr/local/go/src/runtime/panic.go:770 +0x132
go/types.(*StdSizes).Sizeof(0x0, {0xabc7e8, 0xdfb680})
        /usr/local/go/src/go/types/sizes.go:228 +0x30f
go/types.(*Config).sizeof(...)
        /usr/local/go/src/go/types/sizes.go:333
go/types.representableConst.func1({0xabc7e8?, 0xdfb680?})
        /usr/local/go/src/go/types/const.go:76 +0x9e
go/types.representableConst({0xabe668, 0xdd1be0}, 0xc000552800, 0xdfb680, 0xc0007168f0)
        /usr/local/go/src/go/types/const.go:92 +0x192
go/types.(*Checker).representation(0xc000552800, 0xc000025740, 0xdfb680)
        /usr/local/go/src/go/types/const.go:256 +0x65
go/types.(*Checker).implicitTypeAndValue(0xc000552800, 0xc000025740, {0xabc7e8, 0xdfb680})
        /usr/local/go/src/go/types/expr.go:375 +0x2d7
go/types.(*Checker).assignment(0xc000552800, 0xc000025740, {0xabc7e8, 0xdfb680}, {0x9dd95e, 0xa})
        /usr/local/go/src/go/types/assignments.go:52 +0x2e5
go/types.(*Checker).assignVar(0xc000552800, {0xabce90, 0xc00013eab0}, {0xabcdd0, 0xc00053ab80}, 0x0, {0x9dd95e, 0xa})
        /usr/local/go/src/go/types/assignments.go:260 +0x1d8
go/types.(*Checker).assignVars(0xc000552800, {0xc0003a0360?, 0x1, 0xc000594ff0?}, {0xc0003a0370, 0xc00070c7e8?, 0x2?})
        /usr/local/go/src/go/types/assignments.go:455 +0x310
go/types.(*Checker).stmt(0xc000552800, 0x0, {0xabd700, 0xc0002e0e40})
        /usr/local/go/src/go/types/stmt.go:476 +0x1628
go/types.(*Checker).stmtList(0xc000552800, 0x0, {0xc0002e0e80?, 0x0?, 0xe?})
        /usr/local/go/src/go/types/stmt.go:121 +0x85
go/types.(*Checker).funcBody(0xc000552800, 0xabc950?, {0xc0004f22dc?, 0xc0003a1b50?}, 0xc0000b1740, 0xc000595140, {0x0?, 0x0?})
        /usr/local/go/src/go/types/stmt.go:41 +0x331
go/types.(*Checker).funcDecl.func1()
        /usr/local/go/src/go/types/decl.go:852 +0x3a
go/types.(*Checker).processDelayed(0xc000552800, 0x0)
        /usr/local/go/src/go/types/check.go:467 +0x162
go/types.(*Checker).checkFiles(0xc000552800, {0xc0000a00b8, 0x1, 0x1})
        /usr/local/go/src/go/types/check.go:411 +0x1cc
go/types.(*Checker).Files(...)
        /usr/local/go/src/go/types/check.go:372
golang.org/x/tools/go/packages.(*loader).loadPackage(0xc0001e4000, 0xc0002b0700)
        /root/src/pkg/mod/golang.org/x/tools@v0.1.10/go/packages/packages.go:966 +0x76f
golang.org/x/tools/go/packages.(*loader).loadRecursive.func1()
        /root/src/pkg/mod/golang.org/x/tools@v0.1.10/go/packages/packages.go:803 +0x1a9
sync.(*Once).doSlow(0x90a226f672e6563?, 0x6e674922090a2c5d?)
        /usr/local/go/src/sync/once.go:74 +0xc2
sync.(*Once).Do(...)
        /usr/local/go/src/sync/once.go:65
golang.org/x/tools/go/packages.(*loader).loadRecursive(0x726f732209090a2c?, 0x315f6c706d695f74?)
        /root/src/pkg/mod/golang.org/x/tools@v0.1.10/go/packages/packages.go:791 +0x4a
golang.org/x/tools/go/packages.(*loader).loadRecursive.func1.1(0x65746e692209090a?)
        /root/src/pkg/mod/golang.org/x/tools@v0.1.10/go/packages/packages.go:798 +0x26
created by golang.org/x/tools/go/packages.(*loader).loadRecursive.func1 in goroutine 262
        /root/src/pkg/mod/golang.org/x/tools@v0.1.10/go/packages/packages.go:797 +0x94

root@f7db23552294:/home/me/gostuff# go env
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/root/.cache/go-build'
GOENV='/root/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/me/gostuff/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/me/gostuff'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.4'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build92698888=/tmp/go-build -gno-record-gcc-switches'

root@f7db23552294:/home/me/gostuff#  revel version
Revel executing: displays the Revel Framework and Go version
Revel Framework :       Unknown (1.1.0 remote master branch)
Revel Cmd       :       1.1.2   (1.1.2 remote master branch)
Revel Modules   :       Unknown (1.1.0 remote master branch)

Go Location:/usr/local/go/bin/go

go version go1.22.4 linux/amd64

I get the same error. Two weeks and no response suggests this is yet another dead Go web framework. What has happened to this language?

I had the same issue starting the revel app using golang 1.22.x
Using 1.21 or 1.23 seems to work though so please try that.

From my knowledge fully fledged webframeworks in golang are simply no longer needed. The standard library provides everything you need as detailed in this article.
More discussions around all of this can be found here.

The issue seems to be with the golang.org/x/tools. Upgrading that in the go.mod file of the revel/cmd seems to fix the issue.
https://github.com/revel/cmd/issues/224

The issue seems to be with the golang.org/x/tools. Upgrading that in the go.mod file of the revel/cmd seems to fix the issue.
revel/cmd#224

Thank you. Unfortunately the bigger issue appears to be that the project was abandoned more than two years ago, and using an abandoned framework for anything important would be unwise.

Hello all. I'll take a look at revel/cmd/issues#224 today.
@baylf2000 I'd like to get into a predictable release cycle for Revel. The challenge has always been coordinating volunteer effort. We lost our last volunteer over a year ago and I have not had the time to do anything myself.
The focus should be stability at this point. New features are not currently a priority, though the last major changes we mad to the code was to increase modularity of the various drivers, so we can extend functionality in the future.
If anyone wants to join the core team, let me know.

@brendensoares Thanks for the reply. I completely understand the difficult issues around resourcing for open source projects such as this. It's a difficulty that every project has to deal with at some point. Some with success. Others not.
At the same time, it's unfortunate that a brilliant project such as this is left in a state where beginner users are presented with a simple tutorial to begin using the project which is now completely broken. It leaves users wondering if they're doing something wrong, and potentially spending large amounts of time trying to fix something that they cannot.
Can I suggest perhaps a large note on the landing page for the project stating that the tutorial instructions are currently broken and should not be attempted?


Fill out README with new sections and add deployment notes

Description
Rewrites the README for better information and structure, with deployment notes.
View as actual document.
Issues fixed
Fixes #9.
Checklist

[x] npm test returns no warnings or errors.

Rebased onto master


maxDate doesn't work as expected if set to 31-Jan-YYYY.

Describe the bug
The date picker is customised to use a month picker

If the maxDate value is set to 31-Jan-2022 (Issue exists for any year, but date set as 31-Jan). The month picker doesn't show the other months of the year 2022 as disabled. Only the months from 2023 are disabled.
Expected behavior
I would expect the months (Feb-Dec) from the year 2022 to be disabled.
Screenshots

Desktop & mobile (please complete the following information):

Chrome, Safari, Brave
3.2.1

Thanks for fixing this @Jasenkoo


Add support for phylorefs with apomorphies

This PR will add support for phylorefs with apomorphies. It will do that by:

[ ] Adding an "apomorphy" field after "Internal specifiers" and "External specifiers" in the "Specifiers" box (see below).
[ ] Allowing the user to choose the field specified in the Phyx manuscript, table 5:

[ ] bearingEntity
[ ] phenotypicQuality
[ ] definition (required)

WIP: this currently only contains the Testudinata phyloref from Phylonym. The actual code still needs to be written.

@gaurav did you merge this by accident or was there something else going on? I feel like I reviewed part of this PR, but not the full PR, and oddly there's no record of anyone having done or approved a review. Can you demystify?

Aha, I figured it out! I was initially working on this as part of PR #278, but there were issues with Testudinata, so I deleted it before I submitted that PR for review and created this PR to keep a copy of Testudinata around so I could continue working on that here. However, because every commit in this PR is also part of PR #278, merging that PR automatically marked this as merged and closed it. So, there's no code here that needs reviewing or merging.
Last night I looked for this PR, didn't find it, and created a new PR #291 to work on Testudinata with. I'll continue working on that PR and submit it for review once it's done.


Running configure with key/user/endpoint and no-interaction arguments ends in endless loop

Hello.
I tried to script insight configuration and run the following command:
insight.phar configure --api-token=TOPSECRET --user-uuid=ALSOSECRET --api-endpoint=https://insight.sensiolabs.com --no-interaction

I expected, that the ~/.sensiolabs/insight.json would be created.
Instead the error message Your must answer this question. is printed in an endless loop.
Seems, the arguments for user/key are not recognized by this command.
Best regards
Lukas

Hello @slde-rorschach ; Thanks for this report. Are you able to open a PR in order to fix this issue? If not, let me know, and I will take care of it.


croc: 6.1.3 -> 6.1.4

Motivation for this change
croc utility minor version bump from 6.1.3 to 6.1.4.
GitHub release tag: v6.1.4
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @ self

Thanks!


Suddenly issues with st_paywall

Hello! Are there any known issues with the st_paywall at the moment?
My App is suddenly not booting anymore and I gett the error message
ModuleNotFoundError: This app has encountered an error. The original error message is redacted to prevent data leaks. Full error details have been recorded in the logs (if you're on Streamlit Cloud, click on 'Manage app' in the lower right of your app).
Traceback:
File "/home/adminuser/venv/lib/python3.9/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 534, in _run_script
    exec(code, module.__dict__)
File "/mount/src/promptfactory/1_HOME.py", line 2, in <module>
    from st_paywall import add_auth

hey @roland71 what version of st_paywall are you using?

@roland71 and what is the actual issue? Can you show the logs?


Report memory usage at the end of the build step (fix #363)

closes #363 - added linker options as described in the ticket

Hi @stephenhensley,
happy to help! I have implemented the tweaks you suggested.
The size command is no longer used in the Makefile now, but I left the code settings the path to the command ( $(SZ) variable). Let me know if you want me to remove them as well.

@zeroisnan Thanks!
Yeah, I'm fine with leaving the $(SZ) variable in place anyway. It's nice to have the typical compiler commands added into the top of the Makefile


storage: check prefix in unsynced

Current syncWatchers method skips the events that have
prefixes that are being watched when the prefix is not
existent as a key. This fixes https://github.com/coreos/etcd/issues/4191
by adding prefix checking to not skip those events.

/cc @xiang90 @heyitsanthony
Thanks!

@xiang90 PTAL. Just addressed comments. Thanks

@xiang90 Just moved. PTAL.

@xiang90 All addressed. PTAL. Thanks!

LGTM

Thanks. Just changed the test logic (if). Will merge after CI passes.


Does not does not show even if the browsers are outdated

Does not does not show even if the browsers are outdated

Can you detail on this a bit more. Which browser on which system?


checking tags across autoconf generated files reveals many as EBCDIC

Ideally, everything should be ASCII - this likely is highlighting a problem:
find . -name "*" | xargs chtag -p 2>/dev/null | grep IBM-1047
t IBM-1047    T=on  ./autoconf-2.71/bin/autoreconf
t IBM-1047    T=on  ./autoconf-2.71/bin/autom4te
t IBM-1047    T=on  ./autoconf-2.71/bin/autoconf
t IBM-1047    T=on  ./autoconf-2.71/bin/autoheader
t IBM-1047    T=on  ./autoconf-2.71/bin/autoupdate
t IBM-1047    T=on  ./autoconf-2.71/bin/autoscan
t IBM-1047    T=on  ./autoconf-2.71/bin/ifnames
t IBM-1047    T=on  ./autoconf-2.71/build-aux/config.guess
t IBM-1047    T=on  ./autoconf-2.71/lib/autoconf/general.m4
t IBM-1047    T=on  ./autoconf-2.71/lib/autoconf/status.m4
t IBM-1047    T=on  ./autoconf-2.71/lib/autoscan/autoscan.list
t IBM-1047    T=on  ./autoconf-2.71/lib/m4sugar/version.m4
t IBM-1047    T=on  ./autoconf-2.71/lib/autom4te.cfg
t IBM-1047    T=on  ./autoconf-2.71/tests/local.at
t IBM-1047    T=on  ./autoconf-2.71/tests/atlocal
t IBM-1047    T=on  ./autoconf-2.71/tests/atconfig
t IBM-1047    T=on  ./autoconf-2.71/tests/autoconf
t IBM-1047    T=on  ./autoconf-2.71/tests/autoheader
t IBM-1047    T=on  ./autoconf-2.71/tests/autom4te
t IBM-1047    T=on  ./autoconf-2.71/tests/autoreconf
t IBM-1047    T=on  ./autoconf-2.71/tests/autoscan
t IBM-1047    T=on  ./autoconf-2.71/tests/autoupdate
t IBM-1047    T=on  ./autoconf-2.71/tests/ifnames
t IBM-1047    T=on  ./autoconf-2.71/configure
t IBM-1047    T=on  ./autoconf-2.71/config.log
t IBM-1047    T=on  ./autoconf-2.71/config.status
t IBM-1047    T=on  ./autoconf-2.71/Makefile

I think this stems from the fact that 'patch' will create an IBM-1047 tagged file even if the input files are ISO8859-1 and so that IBM-1047 tag ends up getting propagated. With the shift to use 'git diff' for patch management, this should 'fix itself'.
@IgorTodorovskiIBM fyi...


Subgraph fails on event trigger with unclear error

Running a subgraph on a local graph node. The subgraph correctly detects an event but fails to process it with this error:
graph-node_1  | May 30 17:58:53.341 INFO 1 trigger found in this block for this subgraph, block_hash: 0x5cee4cfc9420421e0a01e9e72f2b587a2dc79856ae21e91331a042260eef5b17, block_number: 47, sgd: 4, subgraph_id: QmNPLV8VuAbQy6q8UosBhRww4URZ7Lf4gqVh7DZFXZXRMF, component: SubgraphInstanceManager
graph-node_1  | thread 'mapping-QmNPLV8VuAbQy6q8UosBhRww4URZ7Lf4gqVh7DZFXZXRMF-3dfe9afa-7b7a-41e4-be1b-376146cfdbf1' panicked at 'assertion failed: `(left == right)`
graph-node_1  |   left: `-1`,
graph-node_1  |  right: `0`: registering new sigaltstack failed', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/wasmtime-runtime-0.27.0/src/traphandlers/unix.rs:238:9
graph-node_1  | May 30 17:58:53.391 ERRO Subgraph instance failed to run: failed to process trigger: block #47 (0x5cee…5b17), transaction 46294df5d0b88da42976b739297f6aad2ed71e761ef868618ba4aae8df8ae48a: Mapping terminated before handling trigger: oneshot canceled, code: SubgraphSyncingFailure, sgd: 4, subgraph_id: QmNPLV8VuAbQy6q8UosBhRww4URZ7Lf4gqVh7DZFXZXRMF, component: SubgraphInstanceManager

Thanks @peripheralist ! Are you running the graph-node in a docker container? cc @otaviopace

Yep, using the docker image from this repo without any changes. Running on a M1 Mac

@peripheralist I think you'll have to use this Docker tag for now: https://hub.docker.com/layers/graphprotocol/graph-node/2c23cce/images/sha256-9182194b742c2c1a70658f7f01aa49a30a8ecd2353f7ae1e7cfd43be73f7c262?context=explore
If you're using our docker-compose just change this line to:
image: graphprotocol/graph-node:2c23cce

For some reason images we've built after this hash are breaking on M1 Macs, maybe because of some weird linking issue or something, we haven't figured it out yet.

You can also compile the source code directly, it is working on M1 Macs, me and @azf20 use them as well 😄
But since you're already trying with docker, it might be easier.

I just switched to that Docker tag and problem solved 😄 Thanks for the quick help!


What's the proper way to select the Python Environment.

I'm using Preview of Visual Studio 2017 Community and trying out the Sample Machine Learning projects.
I would think that you set the Python Environment by clicking on it so it's selected in the Python Environments window but that doesn't appear to actually set the active environment.
What is the correct way to set the Python Environment?
I found I need to go into the Projects Setting and I have to select Anaconda 4.3.0 as the Interpreter in place of the .
Shouldn't selecting the Python Environment in the Python Env. window select the corresponding interpreter for the project and set that Environment for the Solution?
Here's the Python diagnostic info (in this case, it's prior to setting Anaconda as the interpreter under Project Settings)
https://gist.github.com/DaveSprague/e50f82d70af1c145b67ba2efe73b02f9

A project can have references to multiple environments. They will appear in Solution Explorer under Python Environments.  Right-click on it and choose Add/Remove Python Environments.  Then you can right-click on one and Activate Environment.  This is handy if you want to quickly switch back and forth.  As you've noticed, the active environment can also be changed in project settings page.
If a project doesn't have any active environment, it will use the global default.  To change that default, you select it from the Python Environments window, and click on Make this the default environment...

The documentation at https://docs.microsoft.com/en-us/visualstudio/python/python-environments#project-specific-environments has more information and screenshots.

Yeah, I think the missing piece here is that the list in the environments window is just that - a list. To activate an environment, you need to take an extra step (this is pretty standard for lists in Windows - selection and activation are rarely the same gesture).

Got it. Thanks to all for help with this


As a db administrator I want to know if there are faulty data entries in my supplied dataset

Should be handled by Knime workflow