add help text to gen/, +help to query it

I like this convention...
On Fri, Oct 21, 2016 at 6:00 PM, Anton Dyudin<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/urbit/arvo/pull/285
Commit Summary

added one-line info to all generators
added +help command summary lister
+help %hood
+help %solid

File Changes

M gen/ask/admins.hoon
https://github.com/urbit/arvo/pull/285/files#diff-0 (3)
M gen/cat/pretty.hoon
https://github.com/urbit/arvo/pull/285/files#diff-1 (1)
M gen/code.hoon
https://github.com/urbit/arvo/pull/285/files#diff-2 (1)
M gen/curl-hiss.hoon
https://github.com/urbit/arvo/pull/285/files#diff-3 (1)
M gen/curl.hoon
https://github.com/urbit/arvo/pull/285/files#diff-4 (1)
M gen/curl/url.hoon
https://github.com/urbit/arvo/pull/285/files#diff-5 (1)
M gen/gmail/list.hoon
https://github.com/urbit/arvo/pull/285/files#diff-6 (1)
M gen/gmail/send.hoon
https://github.com/urbit/arvo/pull/285/files#diff-7 (1)
M gen/hello.hoon
https://github.com/urbit/arvo/pull/285/files#diff-8 (1)
A gen/help.hoon
https://github.com/urbit/arvo/pull/285/files#diff-9 (64)
M gen/hood/ask.hoon
https://github.com/urbit/arvo/pull/285/files#diff-10 (1)
M gen/hood/autoload.hoon
https://github.com/urbit/arvo/pull/285/files#diff-11 (1)
M gen/hood/begin.hoon
https://github.com/urbit/arvo/pull/285/files#diff-12 (1)
M gen/hood/bonus.hoon
https://github.com/urbit/arvo/pull/285/files#diff-13 (3)
M gen/hood/breload.hoon
https://github.com/urbit/arvo/pull/285/files#diff-14 (1)
M gen/hood/cancel.hoon
https://github.com/urbit/arvo/pull/285/files#diff-15 (1)
M gen/hood/claim.hoon
https://github.com/urbit/arvo/pull/285/files#diff-16 (1)
M gen/hood/cp.hoon
https://github.com/urbit/arvo/pull/285/files#diff-17 (1)
M gen/hood/deset.hoon
https://github.com/urbit/arvo/pull/285/files#diff-18 (1)
M gen/hood/exit.hoon
https://github.com/urbit/arvo/pull/285/files#diff-19 (1)
M gen/hood/hi.hoon
https://github.com/urbit/arvo/pull/285/files#diff-20 (1)
M gen/hood/init-auth-basic.hoon
https://github.com/urbit/arvo/pull/285/files#diff-21 (1)
M gen/hood/init-oauth1.hoon
https://github.com/urbit/arvo/pull/285/files#diff-22 (1)
M gen/hood/init-oauth2.hoon
https://github.com/urbit/arvo/pull/285/files#diff-23 (1)
M gen/hood/init-oauth2/google.hoon
https://github.com/urbit/arvo/pull/285/files#diff-24 (1)
M gen/hood/invite.hoon
https://github.com/urbit/arvo/pull/285/files#diff-25 (1)
M gen/hood/label.hoon
https://github.com/urbit/arvo/pull/285/files#diff-26 (1)
M gen/hood/link.hoon
https://github.com/urbit/arvo/pull/285/files#diff-27 (1)
M gen/hood/load.hoon
https://github.com/urbit/arvo/pull/285/files#diff-28 (1)
M gen/hood/manage-old-key.hoon
https://github.com/urbit/arvo/pull/285/files#diff-29 (1)
M gen/hood/manage.hoon
https://github.com/urbit/arvo/pull/285/files#diff-30 (1)
M gen/hood/mass.hoon
https://github.com/urbit/arvo/pull/285/files#diff-31 (1)
M gen/hood/merge.hoon
https://github.com/urbit/arvo/pull/285/files#diff-32 (1)
M gen/hood/mount.hoon
https://github.com/urbit/arvo/pull/285/files#diff-33 (1)
M gen/hood/mv.hoon
https://github.com/urbit/arvo/pull/285/files#diff-34 (1)
M gen/hood/overload.hoon
https://github.com/urbit/arvo/pull/285/files#diff-35 (1)
M gen/hood/rc.hoon
https://github.com/urbit/arvo/pull/285/files#diff-36 (1)
M gen/hood/reboot.hoon
https://github.com/urbit/arvo/pull/285/files#diff-37 (1)
M gen/hood/reinvite.hoon
https://github.com/urbit/arvo/pull/285/files#diff-38 (1)
M gen/hood/rekey.hoon
https://github.com/urbit/arvo/pull/285/files#diff-39 (1)
M gen/hood/release-ships.hoon
https://github.com/urbit/arvo/pull/285/files#diff-40 (1)
M gen/hood/release.hoon
https://github.com/urbit/arvo/pull/285/files#diff-41 (1)
M gen/hood/reload-desk.hoon
https://github.com/urbit/arvo/pull/285/files#diff-42 (1)
M gen/hood/reload.hoon
https://github.com/urbit/arvo/pull/285/files#diff-43 (1)
M gen/hood/replay-womb-log.hoon
https://github.com/urbit/arvo/pull/285/files#diff-44 (3)
M gen/hood/reset.hoon
https://github.com/urbit/arvo/pull/285/files#diff-45 (1)
M gen/hood/rf.hoon
https://github.com/urbit/arvo/pull/285/files#diff-46 (1)
M gen/hood/rm.hoon
https://github.com/urbit/arvo/pull/285/files#diff-47 (1)
M gen/hood/save.hoon
https://github.com/urbit/arvo/pull/285/files#diff-48 (1)
M gen/hood/schedule.hoon
https://github.com/urbit/arvo/pull/285/files#diff-49 (1)
M gen/hood/serve.hoon
https://github.com/urbit/arvo/pull/285/files#diff-50 (1)
M gen/hood/start.hoon
https://github.com/urbit/arvo/pull/285/files#diff-51 (1)
M gen/hood/sync.hoon
https://github.com/urbit/arvo/pull/285/files#diff-52 (1)
M gen/hood/syncs.hoon
https://github.com/urbit/arvo/pull/285/files#diff-53 (1)
M gen/hood/track.hoon
https://github.com/urbit/arvo/pull/285/files#diff-54 (1)
M gen/hood/transfer.hoon
https://github.com/urbit/arvo/pull/285/files#diff-55 (1)
M gen/hood/unlink.hoon
https://github.com/urbit/arvo/pull/285/files#diff-56 (1)
M gen/hood/unmount.hoon
https://github.com/urbit/arvo/pull/285/files#diff-57 (1)
M gen/hood/unsync.hoon
https://github.com/urbit/arvo/pull/285/files#diff-58 (1)
M gen/hood/verb.hoon
https://github.com/urbit/arvo/pull/285/files#diff-59 (1)
M gen/ls/subdir.hoon
https://github.com/urbit/arvo/pull/285/files#diff-60 (1)
M gen/moon.hoon
https://github.com/urbit/arvo/pull/285/files#diff-61 (1)
M gen/pope.hoon
https://github.com/urbit/arvo/pull/285/files#diff-62 (1)
M gen/solid.hoon
https://github.com/urbit/arvo/pull/285/files#diff-63 (1)
M gen/talk/federate.hoon
https://github.com/urbit/arvo/pull/285/files#diff-64 (1)
M gen/talk/load.hoon
https://github.com/urbit/arvo/pull/285/files#diff-65 (1)
M gen/talk/log.hoon
https://github.com/urbit/arvo/pull/285/files#diff-66 (1)
M gen/talk/save.hoon
https://github.com/urbit/arvo/pull/285/files#diff-67 (1)
M gen/talk/unlog.hoon
https://github.com/urbit/arvo/pull/285/files#diff-68 (1)
M gen/ticket.hoon
https://github.com/urbit/arvo/pull/285/files#diff-69 (1)
M gen/twit/as.hoon
https://github.com/urbit/arvo/pull/285/files#diff-70 (4)
M gen/womb/balance.hoon
https://github.com/urbit/arvo/pull/285/files#diff-71 (1)
M gen/womb/balances.hoon
https://github.com/urbit/arvo/pull/285/files#diff-72 (1)
M gen/womb/shop.hoon
https://github.com/urbit/arvo/pull/285/files#diff-73 (1)

Patch Links:

https://github.com/urbit/arvo/pull/285.patch
https://github.com/urbit/arvo/pull/285.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/285, or mute the thread
https://github.com/notifications/unsubscribe-auth/AALyAZM19aXyhY6uGmIqnZuM3HRkw8Jbks5q2WA4gaJpZM4Kdtnd
.

Woah. I have to try this.

On Oct 21, 2016, at 6:00 PM, Anton Dyudin<EMAIL_ADDRESS>wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/urbit/arvo/pull/285
Commit Summary
added one-line info to all generators
added +help command summary lister
+help %hood
+help %solid
File Changes
M gen/ask/admins.hoon (3)
M gen/cat/pretty.hoon (1)
M gen/code.hoon (1)
M gen/curl-hiss.hoon (1)
M gen/curl.hoon (1)
M gen/curl/url.hoon (1)
M gen/gmail/list.hoon (1)
M gen/gmail/send.hoon (1)
M gen/hello.hoon (1)
A gen/help.hoon (64)
M gen/hood/ask.hoon (1)
M gen/hood/autoload.hoon (1)
M gen/hood/begin.hoon (1)
M gen/hood/bonus.hoon (3)
M gen/hood/breload.hoon (1)
M gen/hood/cancel.hoon (1)
M gen/hood/claim.hoon (1)
M gen/hood/cp.hoon (1)
M gen/hood/deset.hoon (1)
M gen/hood/exit.hoon (1)
M gen/hood/hi.hoon (1)
M gen/hood/init-auth-basic.hoon (1)
M gen/hood/init-oauth1.hoon (1)
M gen/hood/init-oauth2.hoon (1)
M gen/hood/init-oauth2/google.hoon (1)
M gen/hood/invite.hoon (1)
M gen/hood/label.hoon (1)
M gen/hood/link.hoon (1)
M gen/hood/load.hoon (1)
M gen/hood/manage-old-key.hoon (1)
M gen/hood/manage.hoon (1)
M gen/hood/mass.hoon (1)
M gen/hood/merge.hoon (1)
M gen/hood/mount.hoon (1)
M gen/hood/mv.hoon (1)
M gen/hood/overload.hoon (1)
M gen/hood/rc.hoon (1)
M gen/hood/reboot.hoon (1)
M gen/hood/reinvite.hoon (1)
M gen/hood/rekey.hoon (1)
M gen/hood/release-ships.hoon (1)
M gen/hood/release.hoon (1)
M gen/hood/reload-desk.hoon (1)
M gen/hood/reload.hoon (1)
M gen/hood/replay-womb-log.hoon (3)
M gen/hood/reset.hoon (1)
M gen/hood/rf.hoon (1)
M gen/hood/rm.hoon (1)
M gen/hood/save.hoon (1)
M gen/hood/schedule.hoon (1)
M gen/hood/serve.hoon (1)
M gen/hood/start.hoon (1)
M gen/hood/sync.hoon (1)
M gen/hood/syncs.hoon (1)
M gen/hood/track.hoon (1)
M gen/hood/transfer.hoon (1)
M gen/hood/unlink.hoon (1)
M gen/hood/unmount.hoon (1)
M gen/hood/unsync.hoon (1)
M gen/hood/verb.hoon (1)
M gen/ls/subdir.hoon (1)
M gen/moon.hoon (1)
M gen/pope.hoon (1)
M gen/solid.hoon (1)
M gen/talk/federate.hoon (1)
M gen/talk/load.hoon (1)
M gen/talk/log.hoon (1)
M gen/talk/save.hoon (1)
M gen/talk/unlog.hoon (1)
M gen/ticket.hoon (1)
M gen/twit/as.hoon (4)
M gen/womb/balance.hoon (1)
M gen/womb/balances.hoon (1)
M gen/womb/shop.hoon (1)
Patch Links:
https://github.com/urbit/arvo/pull/285.patch
https://github.com/urbit/arvo/pull/285.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

You invented this convention :3
(It was in the post-ford Hoon style guide that introduced comment tildes)
On Tuesday, 25 October 2016, Galen Wolfe-Pauly<EMAIL_ADDRESS>wrote:

Woah. I have to try this.

On Oct 21, 2016, at 6:00 PM, Anton Dyudin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/urbit/arvo/pull/285
Commit Summary
added one-line info to all generators
added +help command summary lister
+help %hood
+help %solid
File Changes
M gen/ask/admins.hoon (3)
M gen/cat/pretty.hoon (1)
M gen/code.hoon (1)
M gen/curl-hiss.hoon (1)
M gen/curl.hoon (1)
M gen/curl/url.hoon (1)
M gen/gmail/list.hoon (1)
M gen/gmail/send.hoon (1)
M gen/hello.hoon (1)
A gen/help.hoon (64)
M gen/hood/ask.hoon (1)
M gen/hood/autoload.hoon (1)
M gen/hood/begin.hoon (1)
M gen/hood/bonus.hoon (3)
M gen/hood/breload.hoon (1)
M gen/hood/cancel.hoon (1)
M gen/hood/claim.hoon (1)
M gen/hood/cp.hoon (1)
M gen/hood/deset.hoon (1)
M gen/hood/exit.hoon (1)
M gen/hood/hi.hoon (1)
M gen/hood/init-auth-basic.hoon (1)
M gen/hood/init-oauth1.hoon (1)
M gen/hood/init-oauth2.hoon (1)
M gen/hood/init-oauth2/google.hoon (1)
M gen/hood/invite.hoon (1)
M gen/hood/label.hoon (1)
M gen/hood/link.hoon (1)
M gen/hood/load.hoon (1)
M gen/hood/manage-old-key.hoon (1)
M gen/hood/manage.hoon (1)
M gen/hood/mass.hoon (1)
M gen/hood/merge.hoon (1)
M gen/hood/mount.hoon (1)
M gen/hood/mv.hoon (1)
M gen/hood/overload.hoon (1)
M gen/hood/rc.hoon (1)
M gen/hood/reboot.hoon (1)
M gen/hood/reinvite.hoon (1)
M gen/hood/rekey.hoon (1)
M gen/hood/release-ships.hoon (1)
M gen/hood/release.hoon (1)
M gen/hood/reload-desk.hoon (1)
M gen/hood/reload.hoon (1)
M gen/hood/replay-womb-log.hoon (3)
M gen/hood/reset.hoon (1)
M gen/hood/rf.hoon (1)
M gen/hood/rm.hoon (1)
M gen/hood/save.hoon (1)
M gen/hood/schedule.hoon (1)
M gen/hood/serve.hoon (1)
M gen/hood/start.hoon (1)
M gen/hood/sync.hoon (1)
M gen/hood/syncs.hoon (1)
M gen/hood/track.hoon (1)
M gen/hood/transfer.hoon (1)
M gen/hood/unlink.hoon (1)
M gen/hood/unmount.hoon (1)
M gen/hood/unsync.hoon (1)
M gen/hood/verb.hoon (1)
M gen/ls/subdir.hoon (1)
M gen/moon.hoon (1)
M gen/pope.hoon (1)
M gen/solid.hoon (1)
M gen/talk/federate.hoon (1)
M gen/talk/load.hoon (1)
M gen/talk/log.hoon (1)
M gen/talk/save.hoon (1)
M gen/talk/unlog.hoon (1)
M gen/ticket.hoon (1)
M gen/twit/as.hoon (4)
M gen/womb/balance.hoon (1)
M gen/womb/balances.hoon (1)
M gen/womb/shop.hoon (1)
Patch Links:
https://github.com/urbit/arvo/pull/285.patch
https://github.com/urbit/arvo/pull/285.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/285#issuecomment-256124828, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhi8I8VWXUfgwM--ABOvLXS8UTucRks5q3kljgaJpZM4Kdtnd
.


Architecture diagram for azure

https://miro.com/app/board/uXjVPpaKJ1c=/

It is ✅ for Dev, but prod is missing. Either create a new issue for prod or update this one.

Added architecture diagram for prod

@nilsml

I have been through it. Looks good!
One minor thing we could improve would be to have a separate storage account for storybook, but it is not so important. This setup works too. We just have to make sure we do not clear or delete the SA if static content is removed OR the storybook is removed.


Add SEO to releaser page

📝 Changed routes:

/[networkOrAddress]

(view full size)

Commit 2a3a9ed7da5efd6a097cbd3b9d777e23b55a4ca5 (https://thirdweb-erj892km1-thirdweb.vercel.app).


Present new stack modally when not in a mode: modal stack

At the moment you need to create two stacks; a parent for modal transitions and a child for everything else.
Ideally we'd be able to add an option when performing navigate()
I'd like to tackle this but it'd be great to get some thoughts on how best to implement it from core developers before I start.

Ideally we'd be able to add an option when performing navigate()

In fact it may be better if we simply have a modal: true or mode: 'modal' in the navigation options of whichever screen or navigation stack we wish to present. The navigate()  method would check for this and perform the intended animation.

I think having 2 navigators is the way to go. All applications I'm currently working on all start with a StackNavigator in modal mode. This makes it possible to always display a screen on top of everything else.
Also if it would be possible to present a modal screen in the middle of a stack, that would also mean that the modal becomes part of the stack, which I believe is not what a "Modal" defines.
Or it would be that a StackNavigator is automatically "wrapped" with a modal StackNavigator. But then again that's unnecessary for people who do not use modal screen.
Why do you think is the problem with having 2 navigators? You probably end up having more than 1 anyway.

I think having 2 navigators is the way to go. All applications I'm currently working on all start with a StackNavigator in modal mode.

The reason to do something a particular way shouldn't be because you're already doing it that way.

This makes it possible to always display a screen on top of everything else.

As a modal we'd of course still need this to be the case

Also if it would be possible to present a modal screen in the middle of a stack, that would also mean that the modal becomes part of the stack, which I believe is not what a "Modal" defines.

Being a part of the stack would be more natural. It would allow you to navigate through a stack like a timeline rather than ad hoc.
How you would develop it natively e.g. on iOS:
UINavigationControllerA -> Root UIViewController -> Push UIViewController -> Push UIViewController -> Present UINavigationControllerB Modally -> Root UIViewController  Push UIViewController -> Push UIViewController
UINavigationControlerB is dedicated to that stack, which you'd expect
As it stands we have to jump around navigation stacks which feels incredibly unnatural and also makes us have to think about hiding headers:
ModalStackNavigator -> Root CardStackNavigator  -> Root View -> Navigate to View -> Navigate To View -> Call back to Modal Stack Navigator -> Root View -> Navigate to View -> -> Navigate to View

Omg, I don't get it. React-Native got like 6 iterations of navigators and I have the feeling we start every time from the beginning how to do things and always have the same problems (modal, header, ...), over and over again.
I'm not complaining because I know I could also help making it better because it is open source and I really appreciate every person who is working on things like this! Just telling my thoughts here :)

@ms88privat there's many ways to do one thing and people have differing opinions on how to implement them.
On top of the 50 existing issues relating to problems with nesting (not all of them directly solvable by this change) I'll be specifying issues I come across to further push my case as I continue to try make react-navigation work for me in its current state

Dismissing a modal that has a nested stack nav navigator (#686)
Dismissing multiple modals

Pinging OP @dkpalmer since this issue is quite old and related to an old version of the lib. If no answer I'll close in 7 days.
Moreover, I think this PR #2308 will provide a feature related to this issue (but I may be wrong, in which case let me know)

@kelset Wrong mention, or different GH issue?

Whoops! Sorry, wrong autocomplete X_X

(update: not going to close until the PR is merged)


[WIP] Improvement to the write path

Addresses:
https://tachyon.atlassian.net/browse/TACHYON-1070
https://tachyon.atlassian.net/browse/TACHYON-1071

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5516/Failed Tests: 2org.tachyonproject:tachyon-integration-tests: 2tachyon.master.file.FileSystemMasterIntegrationTest.concurrentRenameTesttachyon.master.file.FileSystemMasterIntegrationTest.createFilePerfTest
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5521/
Test FAILed.


Ac kubernetes

@snsansom @IanSudbery @nickilott @david-cgat @jscaber (and all). This is a big change. I have refactored the code to introduce a new base class called the Executor that is inherited by Slurm, Torque, SGE, Kubernetes and local (it replaces make_runner()). The main aim was to implement kubernetes functonality which I couldnt do with the current framework. I introduced a new class function in base_executor.py that is inherited in executor.py (There is also a kubernets.py which I will move into executor.py before merging). I have tested it locally and on slurm on my end and it works, but if others could give it a go that would be great. It also defaults to LocalExecutor if you dont specify it to run locally, but now I think about it, I think im going to make it raise an error as that keeps it consistent with the current behaviour when it complains if DRMMA API isnt found if its ran for cluster config but is ran locally. Thinking of implementing a lot more functionalities in my free time (when i travel on trains and planes) so would be happy to accept suggestions on what to implement next.

Thanks Adam for keeping going with cgat-core! I'm happy to test it out on existing pipelines and will let you know here how it goes

Planning on merging this soon

Hey Adam, I just pulled the branch and tried to run a pipeline and got the following error:
File /gpfs3/well/powrie/users/utu691/devel/venv/Python-3.10.8-GCCcore-12.2.0/skylake/lib/python3.10/site-packages/cgatcore/pipeline/executors.py, line 69, in run
self.monitor_job_completion(job_id)
AttributeError: 'SlurmExecutor' object has no attribute monitor_job_completion
I haven'[t had a chance to look into the source of the error in any detail at all but wanted to flag before the merge...

Thanks for this! I have no idea why the tests are not picking this up. Will investigate further. May need some more tests to capure this


Added script to visualize directory structure

script name - tree.py
Brief about script
A script to visualize directory structure using Python
Issue no.(must) - #489
Screenshots

Self Check(Tick After Making pull Request)

[x] This issue was assigned to me.
[x] One Change in one Pull Request
[x] My file is in proper folder (Name of folder should be in lowercase with no space in between) (E.g. meet_schedular)
[x] I am following clean code and Documentation and my code is well linted with flake8.
[x] I have added README.md and requirements.txt (Include version numbers too e.g. pandas==0.0.1) with my script

@pawangeek I did add an issue number but it is not getting linked.

@pawangeek I did add an issue number but it is not getting linked.

No issues, I done that

@pawangeek I did add an issue number but it is not getting linked.

No issues, I done that

Thank you :)

Hey, @pawangeek I guess I should not be asking this but can you please add my profile as well in the contributor's image section?

Hey, @pawangeek I guess I should not be asking this but can you please add my profile as well in the contributor's image section?

Hey it's automated, you will be there from next day

Hey, @pawangeek I guess I should not be asking this but can you please add my profile as well in the contributor's image section?

Hey it's automated, you will be there from next day

Oh Okay! Thank you.


[$injector:modulerr] Error

Hello,
I'm trying to get this working locally with the node.js example, but I am getting a client error:
Uncaught Error: [$injector:modulerr] Failed to instantiate module MyApp due to:
Error: [$injector:nomod] Module 'Satellizer' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.

I think this is because in app.js the injected Satellizer module is capitalized, e.g.
angular.module('MyApp', ['ngResource', 'ngMessages', 'ngRoute', 'Satellizer', 'mgcrea.ngStrap'])

If I use satellizer, It works, i.e.
angular.module('MyApp', ['ngResource', 'ngMessages', 'ngRoute', 'satellizer', 'mgcrea.ngStrap'])

Is this just a typo?
P.S. thanks so much for your work on this!

I would like to comment on this issue,
I had a similar problem while using Satellizer. I have installed Satellizer using Bower. When we install with bower (bower install satellizer --save), an entry should be added to the bower.json file "satellizer": "^0.15.5"
This is the reference where the app checks for I guesss..
However, during my satellizer installation, I noticed that when I keep the bower.json file open in my editor or didn't provide the --save switch (bower install satellizer --save), satellizer was not getting installed. When I provided the switch, an entry was added to the bower.json and my app was able to detect satellizer module.
Hope this helps someone..


Repo sync for protected CLA branch

The pull request is created from master637569542577788557 to master to fix git push error for protected CLA branch

@ghogen : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Clarifications and improvements to Kafka manual testing documentation

Address feedback from #290
Add note about automated Kafka tests, which didn't exist at time the document was first written
Fix spelling errors

Fixes #322

I wonder if the testing instructions should just stop at the basic copy, partition tests instead of the pipelines which are covered elsewhere.

I think there is some truth to this, when I wrote the document I wanted to mimic each of the four pipelines in the scripts/validation directory. However the Kakfa version of those four pipelines have been codified into tests that are now run as a part of CI.

@gpucibot merge


Cannot see the new message text box.

My Setup

windows 8.1:
2.9.0:

[x] I have tested with the latest version
[x] I can simulate the issue easily

Description

I can't see the "message" text box at the bottom.  I've tried zooming way in and way out, but no luck.  This seems to have happened after a basic Windows reboot, but might also coincide with a recent update to chrome 61.
Current Behavior

Expected Behavior

Same bug in Ubuntu 17.04.

Same bug on MacOS 10.13.4

Please test if the problem persists with our latest release. I will be closing the issue but if there is any problem yet, we will open it again.


New ProgressBar component that renders a horizontal progress bar on iOS and Android

In order to render a horizontal progress bar, a user must choose between ProgressViewIOS and ProgressBarAndroid depending on the platform the app is running on. Both of these components are similar enough in functionality that it makes sense to build a new cross-platform component, ProgressBar.
ProgressBar renders a horizontal progress bar on both platforms using the existing React Native component for the targeted platform. On iOS, this would use ProgressViewIOS, and on Android it would use ProgressBarAndroid.

We are cleaning up the Known Issues doc as part of this week's React Native Documentation Lockdown.
A handful of issues are flagged in that document which belong in the issue tracker, not in the docs.

@hramos Any update about this? Thanks!

@AgtLucas this is still up for grabs

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/new-progressbar-component-that-renders-a-horizontal-progress-bar-on-ios-and-andr

This issue should be Open again, it makes more sense to provide a Horizontal ProgressBar component out of the box that works with both platforms.

@hramos I'd like to re-open this so my colleague @jhampton can do this work. We discussed this a few months ago.


Bump version to 1.3.8

Description
Bump version to 1.3.8
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #498 (0d7b809) into 1.3 (ed48832) will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              1.3     #498      +/-   ##
==========================================
- Coverage   63.48%   63.32%   -0.17%
==========================================
  Files         153      155       +2
  Lines        4431     4447      +16
  Branches      696      738      +42
==========================================
+ Hits         2813     2816       +3
- Misses       1402     1415      +13
  Partials      216      216

Impacted Files
Coverage Δ

...ex-management-dashboards-plugin/utils/constants.ts
100.00% <0.00%> (ø)

...ndex-management-dashboards-plugin/public/plugin.ts
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


subscriptions: Use table/panel GUI instead of accordion panes

Description
Taken from https://github.com/kumahq/kuma-gui/issues/2164

Finally each subscription should have a copy raw button to just get the json/yaml of the subscription.

We should switch from using accordion panes for subscriptions to using a table/summary panel layout like the rest of the GUI.
In the summary panel we can have 2 tabs, [Overview] and [YAML]. Overview shows the information that is currently showing in the accordion panes, and the YAML tab can contain the YAML for the subscription (along with copy buttons etc)

See https://github.com/kumahq/kuma-gui/pull/2664 for part of this

xref for 2 other implems:
https://github.com/kumahq/kuma-gui/issues/2920
https://github.com/kumahq/kuma-gui/issues/2921


Indicate which pane is focused with the Accent color on the pane border

Summary of the Pull Request
Adds a small border with the accent color to indicate a pane is focused

PR Checklist

[x] Closes #994
[x] I work here
[😢] Tests added/passed
[n/a] Requires documentation to be updated

Detailed Description of the Pull Request / Additional comments
I've removed the simple Grid we were using as the pane separator, and replaced it with a Border that might appear on any side of a pane.
When we add a split, we'll create each child with one of the Border flags set (each child with one of a pair of flags). E.g. creating a horizontal split creates one child with the Top border, and another with the Bottom.
Then, if one of those panes is split, it will pass it's border flag to is new children, with the additional flag set. So adding another Vertical split to the above scenario would create a set of panes with either (Top|Left, Top|Right) or (Bottom|Left, Bottom|Right) borders set, depending on which pane was split.
Validation Steps Performed
Some playing with it, but honestly it needs more for me to be totally confident.

(I don't intend to get this in before I leave on vacation)

I bet there's a way to bind this that doesn't require us to propagate bitfields of border sizes down, down, down.

On your screenshots, under the window there is thin strip of what appears to be accent color. Is this right?

@DHowett-MSFT and I resolved the discussion offline - there was some confusion on how I implemented this. Panes only have borders on the sides that are adjacent to other panes. Case in point:

The bottom-right pane only have top and left borders, so when it's focused, only those sides are highlighted.

(I spoke with Dustin - he's fine with this, his comments were answered)


scripts/bootstrap.sh execution error while building the ESP32 temperature-measurement-app

While i'm trying to build the ESP32 in docker follow the steps below:
(1) docker run --rm -v E:/MATTER/connectedhomeip:/project -w /project -it connectedhomeip/chip-build-esp32
(2) source ./scripts/bootstrap.sh
(3) source ./scripts/activate.sh
(4) cd examples/temperature-measurement-app/esp32
(5) source idf.sh
(6) idf make menuconfig Demo->Device Type -> ESP32-DevKitC Demo->Rendezvous Mode->BLE
(7) idf make all
During step2, it always failed with "ConnectionRefusedError: [Errno 111] Connection refused"
------------------------------------------------ Log start ---------------------------------------------
root@9ceba836e995:/project# source scripts/bootstrap.sh
WELCOME TO...
▄███▒  ░▓█  ░▓█ ░▓█▓ ▒█████▄
██▒ ▀█▒  ▒█   ▒█  ░█▒  ▒█░  █░
█▓░      ▒██████  ░█▒  ▒█▄▄▄█░
▓█   █▒  ▒█   ▒█  ░█░  ▒█▀
░▓███▀  ░▓███░▓█▒ ░█░  ▒█
BOOTSTRAP! Bootstrap may take a few minutes; please be patient.
Downloading and installing packages into local source directory:
Setting up CIPD package manager...Traceback (most recent call last):
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 610, in
sys.exit(main())
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 602, in main
return EnvSetup(**vars(parse())).setup()
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 331, in setup
result = step(spin)
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/env_setup.py", line 390, in cipd
cipd_client = cipd_wrapper.init(install_dir, silent=True)
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py", line 335, in init
bootstrap(client, silent)
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py", line 294, in bootstrap
tmp.write(client_bytes())
File "/project/third_party/pigweed/repo/pw_env_setup/py/pw_env_setup/cipd_setup/wrapper.py", line 231, in client_bytes
conn.request('GET', path)
File "/usr/lib/python3.8/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/lib/python3.8/http/client.py", line 950, in send
self.connect()
File "/usr/lib/python3.8/http/client.py", line 1417, in connect
super().connect()
File "/usr/lib/python3.8/http/client.py", line 921, in connect
self.sock = self._create_connection(
File "/usr/lib/python3.8/socket.py", line 808, in create_connection
raise err
File "/usr/lib/python3.8/socket.py", line 796, in create_connection
sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

------------------------------------------------ Log end ---------------------------------------------
Firstly i suppose it's the proxy setting problem, but after i added the proxy setting while starting the docker:
docker run --env HTTP_PROXY="http://<IP_ADDRESS>:19180" --env HTTPS_PROXY="https://<IP_ADDRESS>:19180" --rm -v E:/MATTER/connectedhomeip:/project -w /project -it connectedhomeip/chip-build-esp32
the error still showed up, can anyone give a hint on this issue? Have been stucked on this issue for weeks :(

@jayjayhust Are you still facing the issue?

We're in progress of reviewing older issues. Is this still an issue given how old the SDK this was tested against? Please re-open if so. Thanks!


adding base path support for local files.

Hello, it was hard to manage multiple bots in my automation tool due to filename collisions, so I added a base_path feature, so everyone can set a base_path instead of adjusting all the file names when instantiating.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0636f6e). Click here to learn what that means.
The diff coverage is 88.23%.

@@            Coverage Diff            @@
##             master     #861   +/-   ##
=========================================
  Coverage          ?   49.15%
=========================================
  Files             ?       26
  Lines             ?     2616
  Branches          ?        0
=========================================
  Hits              ?     1286
  Misses            ?     1330
  Partials          ?        0

Impacted Files
Coverage Δ

instabot/bot/bot_checkpoint.py
27.5% <0%> (ø)

instabot/bot/bot.py
76.96% <100%> (ø)

instabot/api/api.py
57.25% <100%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0636f6e...7f40b32. Read the comment docs.

Thank you for your contribution!!! May I ask you to add some lines about your new functionality to our docs pages? That would definitely help our users. Thanks.


Decide GeV cuts for pt & mass

How small GeV values should we accept in the pre processing for the particle physics data? Some issues caused with the response for values very close to zero leading to responses of order 10^6 GeV.

@gallenaxel Can you post the answer as a comment and we can close?

The cuts decided upon are:

For mass: 1 MeV
For p_T: 1 GeV

Closing the issue with this comment.


Switch to an internationalization strategy and decouple technical writings from implementation

Description
Right now the codebase (both frontend and backend) uses string constants or inline strings for displayed text, Error messages are also implemented in the same way.
This causes the birth of issues deriving from the lack of a centralized place to handle all authored content by either our technical writers or our ux designers.
Lack of centralized control over contents also causes a lack of uniformity in displayed text since some words may appear spelled or capitalized in a different way based on who wrote the code, since it is not easy to go through the whole codebase and look for the preferred way to present some text.
Having a centralized file (or set of files) will allow us to work way more efficiently when it comes to interaction with technical authors and designers.
I'm writing this with these issues in mind since in the recent months we've been having issues like these, but we should not forget that solving this problem also allows us to introduce ("for free") translation support infra we will need when the company asks us to add real internationalization support.
Proposed solution
My proposed solution is to:

adopt the react-i18next library to leverage the useTranslation hook throughout the frontend code
centralize the string contents of the whole app in a single file (or a set of files, but one file is a great starting point), it's easier than it sounds like, speaking from experience
remove string constants from the codebase and switch to the corresponding translation keys

First main basic implementation in the frontend
To start things off right, we would only need to add this to the frontend code
import enStrings from '../../locales/en/strings.json' // single file with the string contents for the app

i18n.use(initReactI18next).init({
  resources:  {
    en: {
      translation: enStrings,
    },
  },
  lng: 'en',
  react: {
    transKeepBasicHtmlNodesFor: ['br', 'strong', 'i', 'code', 'p'],
  },
})

and then in App.tsx use the React context provider:
  <I18nextProvider i18n={i18n}></I18nextProvider>

Pros

string constants can be moved over to the i18n infra incrementally after the first main implementation in the frontend code (see above)
technical authors and UX designers would have full indipendence in refactoring strings or introducing new ones so their contribution would speed up things without causing conflicts with the rest of the dev team PRs
last but not least, we open the door for internationalization

Cons

needs a little effort to move contents over to the new structure, but as said, it does not have to be done in one pass, it can be done iteratively or opportunistically

I think a translation layer adds a lot of complexity, and we should only pull in that extra complexity if we have to.
Also, we don't have a list of all text used in the app. Because a lot of copy is coming from the API. For instance, node labels or error messages are not owned directly by the UI code.
I suggest pushing this to a point in the future, where we want to start supporting i18n with more than one language.


Interface for data properties causes type incompatibility with props in child component

Metadata
vue-tsc version: 1.8.22
System: macOS Sonoma 14.1.1
chip: Apple M1 Pro
Node versions: tried 16.9 and 20.9.0
The issue
The following example uses a reproduction environment example, but stems from a larger project where the error appears in the exact same way. I have a component, App.vue, where I define an interface for my data properties, such as:
data(): {
    filterCriteria: FilterCriteria
  } {
    return {
      filterCriteria: {
        dateRange: { start: undefined, end: undefined },
        timeRange: { start: undefined, end: undefined },
        variants: [],
        customFilterWeekday: CustomFilterWeekday.ENTIRE_WEEK
      },
    }
  }

In that same component, I pass my filterCriteria to a child component, ChildComp. In ChildComp, I receive the prop like:
props: {
    filterCriteria: {
      type: Object as PropType<FilterCriteria>,
      required: true
    }
  },

The type that I'm passing, contains typings from the two classes LocalDate and LocalTime from @js-joda/core. But I'm using the exact same type both in the data properties interface, and the prop declaration in the child component. Here is the type:
export type TimeRange = {
  start: LocalTime | undefined;
  end: LocalTime | undefined;
}

export type DateRange = {
  start: LocalDate | undefined;
  end: LocalDate | undefined;
}

export type FilterCriteria = {
  timeRange: TimeRange;
  dateRange: DateRange;
  variants: VariantChannelWrapper[];
  customFilterWeekday: CustomFilterWeekday;
}

When I run vue-tsc, I get this error:
 error TS2322: Type '{ timeRange: { start: { adjustInto: (temporal: Temporal) => Temporal; atDate: (date: LocalDate) => LocalDateTime; atOffset: (offset: ZoneOffset) => OffsetTime; ... 35 more ...; range: (field: TemporalField) => ValueRange; } | undefined; end: { ...; } | undefined; }; dateRange: { ...; }; variants: { ...; }[]; customF...' is not assignable to type 'FilterCriteria'.

25   <ChildComp :filter-criteria="filterCriteria" />
                ~~~~~~~~~~~~~~~~

  src/components/ChildComp.vue:13:5
    13     filterCriteria: {
           ~~~~~~~~~~~~~~~~~
    14       type: Object as PropType<FilterCriteria>,
       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    15       required: true
       ~~~~~~~~~~~~~~~~~~~~
    16     }
       ~~~~~
    The expected type comes from property 'filterCriteria' which is declared here on type 'Partial<{}> & Omit<{ readonly filterCriteria: FilterCriteria; } & VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly<...>, never> & Record<...>'

A workaround
If I, however, delete the interface for my data properties above in App.vue, and rely on inference like in the example below, the error is gone:
data() {
    return {
      filterCriteria: {
        dateRange: { start: undefined, end: undefined },
        timeRange: { start: undefined, end: undefined },
        variants: [],
        customFilterWeekday: CustomFilterWeekday.ENTIRE_WEEK
      },
    }
  }

A reproduction example can be found here: https://github.com/tomosterlund/tsc-error-repro
Steps to reproduce:

clone repo
run npm i
run vue-tsc

Another fix is to change the type to:
export type TimeRange = {
  start: LocalTime | undefined;
  end: LocalTime | undefined;
}

export type DateRange = {
  start: LocalDate | undefined;
  end: LocalDate | undefined;
}

export type FilterCriteria = {
  timeRange: TimeRange;
  dateRange: DateRange;
  variants: VariantChannelWrapper[];
  customFilterWeekday: CustomFilterWeekday;
}

But as far as I know, it is not disallowed in TS to use classes in types and interfaces, please correct me if I'm wrong.

Please check if this issue has been resolved in version 2.x. If not, feel free to create a new one.


Raspberry Pi wire connections

Hi,
Can you share your connection from the remote to the Raspberry Pi, so I can copy?
Thanks

I understand the wire scheme.
 MY RASPBERRY DIED


Decompressing public key

Hi,
decompressPublickey doesn't work at this moment. Actually, it is equal to undefined. This is due to the following commit in https://github.com/bitcoin/secp256k1
https://github.com/bitcoin/secp256k1/commit/23cfa914d2d17dfc3d28ae3b10d95385dac5d835#diff-0d77700fa6e05639431c962ffaa5365aL285
Here secp256k1_ec_pubkey_decompress was removed from the code, so decompressPublickey references nothing.
After all, I just want to decompress a compressed public key in node to encrypt a message with ECIES encryption having just a compressed key.
What should I do in this situation?
Thanks in advance, Hovhannes.

This is the solution if someone is interested
var elliptic = require('elliptic');
var ec = new elliptic.ec('secp256k1');
var publicKeyUncompressed = ec.keyFromPublic(PublicKeyCompressed, 'hex').getPublic(false, 'hex');

@h0vhannes thanks for the solution. I'm going to leave this open till I get a chance to write a better API for the keys.

Thanks @wanderer, will wait for it !

@h0vhannes with v2.x you can use publicKeyConvert

thanks


Match Data with SGPC Nitnem Gutka

Brings Sri Dasam Granth Baanis in SGPC's Nitnem Gutka up to parity

Keep in mind, for the first Pauri of Chandi Di Vaar, SGPC Das Granthi is also used.


Remove warning about compound tags deprecation

Remove warning about compound tags deprecation. Since the warning message here is not currently easily actionable by users. And prints a message every time a ColumnSchema is created, resulting in distracting messages in logs.
After discussions about this we are considering keeping the compound tags for backwards compatibility for now.
If we reach a point where we're using the narrower tags only across Merlin, we can revisit the deprecation approach for these

Providing a way to simplify selecting by all tags was one of the outcomes. However we also discussed two other things. Keeping the compound tags around as a convenient shortcut and removing the warning.
The current state of things seems to be that the warning is not actionable. Which suggests that it would likely be clearer to users of our packages if it wasn't printed/logged.


WARN[0003] certificate with CN ABC DEF is near expiry

Got the following when running make all on a clone repo:
WARN[0003] certificate with CN Justin Cormack is near expiry
WARN[0003] certificate with CN  is near expiry
WARN[0003] certificate with CN  is near expiry
WARN[0003] certificate with CN<EMAIL_ADDRESS>is near expiry
WARN[0003] certificate with CN Ian Campbell is near expiry
WARN[0004] certificate with CN  is near expiry
WARN[0004] certificate with CN  is near expiry
WARN[0004] certificate with CN<EMAIL_ADDRESS>is near expiry
WARN[0004] certificate with CN Ian Campbell is near expiry
WARN[0004] certificate with CN Justin Cormack is near expiry
WARN[0004] certificate with CN Justin Cormack is near expiry

This is a known issue with LinuxKit's use of notary for code signing and certificate rotation, it's not specific to the kubernetes sub-project.
I couldn't find an existing issue so I've raised https://github.com/linuxkit/linuxkit/issues/2911 to track the underlying problem, I'll close this one now, thanks for your report.


Various UI fixes

Numerous small UI fixes:

Fix double border in collaborator list
Fix system notice table background
Mute links in repo and org lists
Downsize projects edit buttons
Improve milestones and project list rendering
Condense milestone list entry to a single line of "metas"
Mute ".." button in repo files list

As expected, https://github.com/go-gitea/gitea/pull/25315 caused a number of conflicts as it incorporated some of the changes done here.

One more fix added, milestone overdue icon now matches issue overdue:


Module level 'doc' attribute is automatically added to 'all'

🐛 Bug Reports
🌍 Environment

Your operating system and version: Arch Linux-5.11.4 x86_64 with glibc-2.33
Your python version: 3.9.2
How did you install python (e.g. apt or pyenv)?: pacman Did you use a virtualenv?: yes
Your Rust version (rustc --version): 1.50.0
Your PyO3 version: 13.2
Have you tried using latest PyO3 main (replace version = "0.x.y" with git = "https://github.com/PyO3/pyo3")?: no

💥 Reproducing
I created a new PyO3 project from the module template.
Running the following code in the Python REPL yields:
>>> import rust2py
>>> rust2py.__all__
['__doc__', 'sum_as_string']

I expect only sum_as_string to be included in __all__, mainly because
that's what users expect when they do from rust2py import *.

From a cursory glance, it seems like
https://github.com/PyO3/pyo3/blob/c0d49052b5f8d84a68b4d5d6c71c5def0bdc66a2/src/derive_utils.rs#L323
should be setattr instead of add and this should be fixed.
Sorry for the drive-by comment, this just happend to show up in https://github.com/mitmproxy/pdoc/issues/235. 😇

Thank you both for reporting!


Bug with translations

After changing the language type in the settings and restarting the server, the plugin continues to use the default language (US).
config.properties:
#BuycraftX configuration file
#Sat Sep 21 12:02:31 EDT 2019
server-key=
push-commands=true
disable-buy-command=true
verbose=false
check-for-updates=false
is-bungeecord=false
buy-command-name=vip
language=pt_BR

Hi there,
Thanks for taking the time to report this issue, I'm sorry it's been slow to get resolved — we're working on it!
Unfortunately, this issue is old enough that we've had to close it. But if you see any other issues (especially ones with the same or similar symptoms), please reply here and I'll look into getting them fixed.
We are currently planning a recode of the Buycraft plugin at some point in Q2 of this year, and we would love to know what issues still exist so they can be fixed for the new plugin.
Apologies for the issues you have faced!


Quantize Per-Trained model Using QLoRa or LoRa , PFET Technique

I would like to ask how can I use QLoRa or Parameter-Efficient Fine-Tuning thin a model does not register at Hugging face instead is Based on OFA
i am trying to Quantize the Tiny version but I don’t know if I need to use Lora in which way for Parameter-Efficient Fine-Tuning
i thought if i reconstruct the model BioMedGPT_Tiny from Unify_Transfomer.py following fie ofa.py and indicate to Config parameters to have BiomedGPT_tiny  in separation file then apply Quantization Techniques but the problem is that the tokenizer Pet-Trained model not available i think

I'd second this. Would be wonderful to have instructions on this.


Add a --shallow flag to go mod vendor

Meaning: only vendor child dependencies. I will write more about this, but jut create this to remember it, will need to test this if it works.

No, this will not work.


Allow packaging from a zip package to allow for signing

Include a serialized version of PSOptions in an includesymbols zip
Add a function which will create a zip package from the expanded includesymbols zip and a folder of signed files
add a function to restore an includesymbols zip as a build and populated PSOptions with the options
update related files

rebased due to merge conflict

started a build at: https://mscodehub.visualstudio.com/PowerShellCore/_build/index?buildId=5706&_a=summary to verify


fix: fix FileTree type issue

This PR...
Changes

Fixes

How to test it

Screenshots

Checklist

[ ] tested locally
[ ] added new dependencies
[ ] updated the docs
[ ] added a test

could this interfere with @jmelnych's work in the find & replace PR? maybe she should add this there if it's still needed


Silent removal does not work

The -Confirm parameter does not work. The command ask for confirmation whether you put it on or not. The only way I found to avoid the confirmation is with -Confirm:$false

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

ID: 62e48887-984b-9df7-893a-8f11b2ec8a7e
Version Independent ID: 542878a5-9211-fc68-6ee6-1a88949b5a0f
Content: Remove-IISSiteBinding (IISAdministration)
Content Source: docset/winserver2019-ps/iisadministration/Remove-IISSiteBinding.md
Product: w10
Technology: windows
GitHub Login: @JasonGerend
Microsoft Alias: jgerend

Hi @gabrielgt,
Thank you for trying to make MicrosoftDocs a better place.
By default switch parameters are always false. unless explicitly specified - Switch Parameters. Here you are not prompted because of the -Confirm parameter but because the impact of the cmdlet is High. You could read more about cmdlet confirm impact and preference - $ConfirmPreference, ConfirmImpact
Furthermore, you could check the following article to understand confirmation requests - users-requesting-confirmation
Let me know if you have any questions.

Thank you for the explanation @velkovb


please add a destroy function to rowGrid.js

Hello brunjo,
i like your tool, but i have problems to destroy your resize layout function if i change the view. On mobile i working with a slider, and I want to switch off all functions of row grid.
Thanks a lot :-)

There's no method to disable rowGrid but you could do it manually like this:
$(window).off('resize.rowGrid');
$('.container .item').removeAttr('style').removeClass('first-item last-row');

@brunjo: thanks a lot :-)


add a simpeg badge!

👍

oh I like that.
i m gonna put one of those right now

ooops. Travis is not happy with the external file
Warning, treated as error:
/home/travis/build/ubcgif/gpg/content/magnetics/magnetics_interpretation.rst:None: WARNING: nonlocal image URI found: https://img.shields.io/badge/powered by-SimPEG-blue.svg

https://github.com/simpeg/simpeg/blob/master/docs/conf.py#L268
On Fri, 23 Sep 2016 at 11:15 dfournier<EMAIL_ADDRESS>wrote:

ooops. Travis is not happy with the external file
Warning, treated as error:
/home/travis/build/ubcgif/gpg/content/magnetics/magnetics_interpretation.rst:None:
WARNING: nonlocal image URI found:
https://img.shields.io/badge/powered by-SimPEG-blue.svg
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/simpeg/website/pull/6#issuecomment-249250159, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA3vYVxNLGozs3L06Y8JwUFvhU15nKqGks5qtAkcgaJpZM4KFJtp
.


Add tree sitter to auto api

What is it?

[x] Feature / enhancement
[x] Bug

Why is it needed?
Current auto api cannot handle nested object-like structures.
The solution does add two new dependencies: tree-sitter and tree-sitter-typescript
Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have ran pnpm change and documented my changes
[x] I have add necessary docs (if needed)
[x] Added new tests to cover the fix / functionality

Okay I'm merging as is, I'll make a follow up PR to cleanup a bit.


add AMD compilation and run instruction

@asroy  This PR should ONLY change the README. Please fix.


How to match with date fields?

Hi team, I am trying to add DOB as a date field and use it for matching.
I have set up a custom DOB field on the user object, and the query references it (several times, the client wants a 3 of 5 match)
but the error is "Invalid bind expression type of String for column of type Date" It is passing the date yyyy-mm-dd into the query successfully by my understanding, but presumably it is in the wrong format? I don't see anyway to set the format on a date input
I know how to do it with some apex, but I don't have that option here. Any ideas would be welcome!
The log message is as follows
Form Values: {Birthdate=1987-12-10<EMAIL_ADDRESS>password=HIDDEN}
There was a problem executing the specific query in the Custom Query property. Query used:
SELECT id FROM Account WHERE (firstname = :firstName AND lastname = :lastName AND personemail = :email) or...[trimmed]... or(firstname = :firstName AND lastname = :lastName and PersonBirthdate = :Birthdate) or ...[trimmed]... or (personemail = :email AND phone = :MobilePhone and PersonBirthdate = :Birthdate).

Error: Invalid bind expression type of String for column of type Date

Hi @Mike-Cleaver-LB - This should work fine. I'm using a date match for my client. How is the date field configured? It is a date on the user object and in the form?
My example so you can compare configuration:
Log record:
Searching for record with query:SELECT Id,AccountId FROM Case WHERE Crime_Ref_Number__c = :Crime_Ref_Number__c AND Contact_Date_of_Birth__c = :Contact_Date_of_Birth__c AND (ContactEmail = :Email OR Mobile_Phone_Unformatted__c = :Mobile_Phone_Unformatted__c) LIMIT 1.
Submitted Values: {Contact_Date_of_Birth__c=2001-01-01, Crime_Ref_Number__c=21240000219<EMAIL_ADDRESS>FirstName=JACK, LastName=TEST, Mobile_Phone_Unformatted__c=07448411354, confirmPassword=HIDDEN, password=HIDDEN}
Form setup:

Field in SF:

Let me know and might be able to identify if there is an issue to fix.

So the value I'm comparing to in the record is a date
it's called personBirtdate on the account object (we're using person accounts)

it's called birthdate on the user record

is how the metadata is setup for this field.
I might just temporarily to one check on date only and see if that behaves differently

I corrected my metadata to be the user api name for birthdate and the error is similar
...
Username valid.
An error occurred whilst trying to update the User Object:Illegal assignment from String to Date
Form Inputs: {Birthdate__c=1987-12-10,

I had a look at the changes, it seems that you're using convertFormDataToCorrectDataType to parse the data, but it doesn't seem to handle strings? it should also be a 'switch on' rather than cascading if statements, it will only be one, no need to keep matching on the remaining ifs when you have parsed the value already?
Schema.DisplayType dataType = objectMetadata.get(key).getDescribe().getType();
becomes
string dataType = SiteUtilities.convertToString( objectMetadata.get(key).getDescribe().getType() );

switch on (datatype){
when 'DATE' {
}
when....{
}
when else {
// handle all different basic strings, like multiselect or whatever here
}

as I read it, basic strings won't get added to the list anymore?

I tried creating a PR for this, I dunno if it worked, i got an error about the CLA which I signed already. Are you able to see it from your side?

Oh damn, old habits sorry, I used to use Java before moving to SF a few years ago. Ok, that's disappointing, I will update my code and send it through.
And i see that you're using the passed in map to do the transforming. I didn't realise that, again from learned history I don't tend to manipulate the values I am going through. But you're right, we only need to modify the values we are actually  changing. I can update my code to reflect that.
PR updated/sent and Linkdin request sent!

This is turning out to be more complex than originally planned!
Where I removed the checkFieldExists() check at multiple points, and had it in the convertFormDataToCorrectType() method, it was removing the 'Email' field from the submitted values when using Person Accounts (which was expected). The issue with this is that the Custom Query then doesn't work because it might expect :Email as part of the query and then fails.
This works fine, as long as the user configures custom metadata appropriately i.e. when setting things up and using Person Accounts, create a new entry for PersonEmail and disable the included out the box one. Ensure that any query references the correct value and you're good to go. The issue is that this is a change in behaviour and may break orgs where they upgrade.
Therefore, I've reverted this part of the change and removed the checkFieldExists from convertFormDataToCorrectType() instead.

Fixed and released.

Thanks! Sorry I was AWOL!


basic example doesn't return data

just following the basic example in jupyter.
Current Behavior
online_features = client.get_online_features(
feature_refs=[
f"daily_transactions",
f"total_transactions",
],
entity_rows=[
GetOnlineFeaturesRequest.EntityRow(
fields={
"customer_id": Value(
int64_val=1001)
})
],

)
print(online_features)
produces:
field_values {
fields {
key: "customer_id"
value {
int64_val: 1001
}
}
fields {
key: "customer_project2/daily_transactions"
value {
}
}
fields {
key: "customer_project2/total_transactions"
value {
}
}
}
note that there does appear to be data in the kafka features topic.  I'm not sure if that is where the online feature service is getting the data or whether it is in redis.

Hello @BenMacKenzie
Last time some other people find the same issue, but I cannot replicate it yet.
May I know your Platform specification?
OS
Docker Version

Thanks

note that there does appear to be data in the Kafka features topic. I'm not sure if that is where the online feature service is getting the data or whether it is in Redis.

Normally the data will be pushed to Kafka, and the Ingestion Job is going to Ingest the Data from Kafka to Redis

@BenMacKenzie Have you made any changes to the max_age?

I just re-did everything and it works fine.  Maybe while struggling with the pandas issue more than 432000 seconds elapsed (5 days)?
thanks!


ScrollViewPager -- simplified infinite/paged scrolling

Implements ScrollViewPager
This PR contains:

[x] Changelog
[x] Documentation
[x] Tests

@Duckers There's also a ReachedStart. The user could in theory use both in they want to unload data from the other end. However, my assumption is that the actual JS objects involved are not a significant size and there's no real need to discard them.
Unrooting/discarding of the actual node's is handled within the Each. There's only ever a small window of items that are rooted.


Tweak generate command

This commit improves the generate useability by
providing output in case neither print nor clip are
selected and defaulting to true for clip.
Signed-off-by: Dominik Schulz<EMAIL_ADDRESS>

Codecov Report

Merging #948 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #948      +/-   ##
==========================================
+ Coverage   63.66%   63.67%   +0.01%
==========================================
  Files         171      171
  Lines        9865     9870       +5
==========================================
+ Hits         6280     6284       +4
- Misses       2798     2799       +1
  Partials      787      787

Impacted Files
Coverage Δ

commands.go
90.44% <ø> (ø)
:arrow_up:

pkg/action/mount.go
60.38% <100%> (ø)
:arrow_up:

pkg/action/generate.go
61.88% <100%> (+0.51%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ccc3fff...59414b6. Read the comment docs.


NSKeyedUnarchiver methods should take Data (instead of just NSData)

What's in this pull request?
We missed a few NSKeyedUnarchiver methods during our original renaming for Swift — some of these methods still take NSData when they can take Data. We can add Data variants which bridge to NSData to fix this in a backwards-compatible way.

@swift-ci Please test

@swift-ci Please smoke test Linux


Embedded pdbs are not generated for .NET Framework projects

Steps To Reproduce:

Create a new ClassLibrary project for .NET Framework (not .NET Core)

Compile
pdb is generated

Set under Build - Advanced - Debugging Information: Portable

Compile
pdb is generated

Set under Build - Advanced - Debugging Information: Embedded
pdb is missing and never generated. No error indication.

Expected Output:
Embedded pdb should be generated for .NET Framework pdbs.
Actual Output:
No pdb and no error or warning is printed.

@Alois-xx, I don't understand why you opened that issue here.

@ctaggart: Sorry if you do not contribute to Visual Studio. I was under the impression that SourceLink is part of VS. Where should this issue go to?

@Alois-xx, https://developercommunity.visualstudio.com/ looks like the right spot probably.


Updated C# sample code for a simpler game.

Now prints prime numbers from 1 to 100.

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


Converted Analog Camera not detected in CameraGetPreviewFrame and other Camera samples

Hi there,
I would like to use the samples to show input from an Analog camera which is converted via an ION Audio VIDEO 2 PC MKII Digital Video Converter. For some reason this camera is not detected in any of the camera samples while freeware software can detect this camera and output it in a correct way.
The device is listed in Sound, Video and Game Controllers...
Is there an DeviceCapability that I need to add in the appxmanifest or is what I ask just not possible in UWP Apps?
Any help would be greatly appreciated.
Tx in advance.

This is something that the driver manufacturer needs to implement.


The first exercise does not have the right layout

It is the default layout and not the exercise layout

The solution seems weird. Duplicating the data (and the answer is wrong in this duplicate in fact). Why can you not use the previous files and locations ?
This bug is related to https://github.com/cheminfo/nmr-displayer/issues/325


Parameterized symbolMap Function

I created this function maker to shorten some parts where we call Things like:
(Definition swhsSymbMap . Data)
Just check the commit: 4fb480c
I defined the SWHS functions needed in my Data Defs.

[x] GlassBR

[x] SSP

[x] Game Physics

[x] SWHS

GlassBR updated as of commit d9d1df4.

d702eea7b8479c31c218aa60327e80e0c715cdea

b3f74644


AMBARI-26243: refactor(ambari-contrib): convert .format() to f-strings

What changes were proposed in this pull request?

Replace legacy .format() syntax with modern f-strings throughout the codebase
Update string formatting to improve code readability

Examples
Before:
message = "Hello, {}".format(name)
After:
message = f"Hello, {name}"
How was this patch tested?
All existing tests pass
No functionality changes, only syntax improvements

@JiaLiangC Can you help review this PR? Thanks.


add logo to webpage

theres no logo for hackathon manager on the browser. Makes it really hard to find it in a lot of tabs.

Do you mean the favicon?
Hmm. Either way HM doesn't have a particular logo yet, although we could just put the codeRIT logo in the tab bar for now.
Ive been talking with @cbaudouinjr about rebranding HM to something a bit more "brand-y".
Rebrand might take a while, so how about we just put the codeRIT logo as favicon?

Also rebrand is #397

Favicon's are configured in Hackathon Settings on a per hackathon basis.


how to install on ps4

how do I install on ps4 already tried save mounter and copying direct but it doesn't work....
Thanks

I don't know. I never had playstation.


Build Timing out using latest Amplify CLI v12.12.6 and Amplify Studio Gen 1

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
16.13.0
Amplify CLI Version
12.12.6
What operating system are you using?
Ubuntu
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made.
Describe the bug
I am unable to deploy my Amplify App using the latest Amplify CLI v12.12.6. I am working in a Gen 1 Amplify Project with Amplify Studio enabled. And I am deploying using the Amplify CI/CD pipeline and default build image (Amazon Linux 2023). The issue is that the build keeps timing out without any errors being shown even after setting the build timeout to its max at 2 hrs. So I am unable to deploy the app.
Build consistently times out at this point below:
2024-08-02T20:04:50.408Z [WARNING]: ✔ Successfully pulled backend environment staging from the cloud.
2024-08-02T20:04:50.488Z [INFO]: ✅
2024-08-02T20:04:52.219Z [INFO]: Note: It is recommended to run this command from the root of your app directory

Expected behavior
The Amplify App should have completed its build and be deployed successfully using the latest Amplify CLI version.
Reproduction steps

Create a Gen 1 Amplify project and enable Amplify Studio.
Add Amplify resources - api & auth.
Trigger CI pipeline build and deploy using latest CLI in build settings.

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
In troubleshooting, I was able to deploy by downgrading the Amplify CLI in the build settings to a previous version v12.0.3 in order for the app to build and deploy successfully.
So it seems the issue is with the latest versions of the Amplify CLI where they don't build Gen 1 Amplify Studio projects.
Before submitting, please confirm:

[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

Hi @ykethan, please see requested information:
App ID: d3gljibf5lo8bp
Region: us-east-1
When pulling the app, I don't experience any errors. Upon enabling the variable given, I see some additional warning outputs below both locally and in the deploy build:
[WARNING] @aws-cdk/aws-apigatewayv2-alpha.WebSocketApiKeySelectionExpression is deprecated. This API will be removed in the next major release.  [WARNING] @aws-cdk/aws-apigatewayv2-alpha.WebSocketApiKeySelectionExpression is deprecated. This API will be removed in the next major release.  [WARNING] @aws-cdk/aws-apigatewayv2-alpha.MappingValue is deprecated. This API will be removed in the next major release.
Please see full deploy build output when using latest CLI version (v12.12.6) below:
BUILD.txt

Hey @kimberlyas, thank you for the information. With the latest versions of Amplify you will need to update the CDK libraries and the extensibility package . Refer to migration documentation: https://docs.amplify.aws/gen1/react/tools/cli/migration/aws-cdk-migration/#how-do-i-migrate
On updating this, could you retry the build with the latest version of Amplify CLI and let us know if this mitigates the issue.


add offset method to compute offsets relative to base-year values

Please confirm that this PR has done the following:

[x] Tests Added
[x] Documentation Added
[x] Name of contributors Added to AUTHORS.rst
[x] Description in RELEASE_NOTES.md Added

Description of PR
This PR introduces an offset() method which allows a user to compute offsets relative to base-time-periods in the same style as normalize().
    For example, offsetting from `year=2005` will provide data
    *relative* to `year=2005` such that the value in 2005 is 0 and
    all other values `value[year] - value[2005]`.

    Conceptually this operation performs as:
    ```
    df - df.filter(**kwargs) + padding
    ```

Thanks @coroa for suggesting the high-performance implementation alternative!
I don't mind adding the function directly for now. If discoverability becomes an issue, we could delegate methods operating only on the timeseries data to a submodule, similar to what I did with the compute module...

Hi both - have updated based on your suggestions. Should be ready.

LGTM

Given positive response here, will go ahead with merge. See #662 for an issue on expanding documentation further.


fix: Replace chatdown package from botbuilder-core tests

#minor
Description
This PR replaces chatdown by the @microsoft/bf-chatdown package to avoid the use of request.
Specific Changes

Replaced  chatdown by the @microsoft/bf-chatdown  in transcriptUtilities.

Testing
The following image shows one of the transcripts tests running after the changes.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
82 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.4%) to 84.496%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

libraries/botframework-streaming/src/utilities/createNodeServer.ts
1
78.57%

libraries/botframework-streaming/src/namedPipe/namedPipeServer.ts
12
50.68%

libraries/botframework-streaming/src/namedPipe/namedPipeClient.ts
17
34.09%

libraries/botframework-streaming/src/namedPipe/namedPipeTransport.ts
51
3.92%

Totals

Change from base Build<PHONE_NUMBER>:
-0.4%

Covered Lines:
20053

Relevant Lines:
22485

💛  - Coveralls

/promoted 4516


"box-shadow" is parsed wrong

Not sure if this is an issue of sass-loader but it looks so.
For some reason box-shadow returns value that is considered Invalid by browser. Why does it happen? How to fix?
In my .scss:
@include box-shadow(0px 1px 5px 1px #c4c3c3);

Returns this:
-webkit-box-shadow: compact(0px 1px 5px 1px #c4c3c3, false, false, false, false, false, false, false, false, false);
-moz-box-shadow: compact(0px 1px 5px 1px #c4c3c3, false, false, false, false, false, false, false, false, false);
box-shadow: compact(0px 1px 5px 1px #c4c3c3, false, false, false, false, false, false, false, false, false);

In a browser dev tools:

In a <script> tag:

This is definitely not a sass-loader problem.
Why are you using a mixin for the box-shadow anyway? It's supported in all major browsers.


Hierarchical Placement Injection fails with a high number of variants

The following results in a crash:
mkdir -p work/cascode_current_mirror_ota
cd work
export ALIGN_WORK_DIR=`pwd`
cd cascode_current_mirror_ota
schematic2layout.py ../../examples/cascode_current_mirror_ota/ -n 40

@854768750 I think this should work. The error is:
PnR.placer.SeqPair.SeqPair INFO : Enumerated search
PnR.placer.Placer.setPlacementInfoFromJson ERROR : instance_name: X_M1 concrete_template_name: PMOS_4T_86154205_X3_Y1 not found.
Segmentation fault

The following results in a crash:
mkdir -p work/cascode_current_mirror_ota
cd work
export ALIGN_WORK_DIR=`pwd`
cd cascode_current_mirror_ota
schematic2layout.py ../../examples/cascode_current_mirror_ota/ -n 40

@854768750 I think this should work. The error is:
PnR.placer.SeqPair.SeqPair INFO : Enumerated search
PnR.placer.Placer.setPlacementInfoFromJson ERROR : instance_name: X_M1 concrete_template_name: PMOS_4T_86154205_X3_Y1 not found.
Segmentation fault

Okay I can look into this.

@854768750 Every routing run now uses the placement injection. The placer is run using one PnRDB instance. The router is run using a different PnRDB instance.
If you want to just iterate on the placement injection you can try this:
mkdir -p work/cascode_current_mirror_ota
cd work
export ALIGN_WORK_DIR=`pwd`
cd cascode_current_mirror_ota
schematic2layout.py ../../examples/cascode_current_mirror_ota/ -n 40

then you can redo the router stage (were the error is happening) by running
schematic2layout.py ../../examples/cascode_current_mirror_ota/ -n 40 --flow_start 3_pnr:route

The main information carried between the placer and router is in: 3_pnr/__placer_dump__.json

Yes, there is only one variant given for each internal hierarchy. There is a new map file where all the abstract template names for internal hierarchies have been replaced with a concrete template name. (Or put another way, we don't need to have more than one variant for each internal hiearchy.)

Yes, there is only one variant given for each internal hierarchy. There is a new map file where all the abstract template names for internal hierarchies have been replaced with a concrete template name. (Or put another way, we don't need to have more than one variant for each internal hiearchy.)

okay that is because the required variant is removed. I will use the new map file.

After the first run, the node "CASCODED_CMC_PMOS_31196023_PG0" block 3 chooses the variant "PMOS_4T_86154205_X1_Y3". But the external placement json file uses "PMOS_4T_86154205_X3_Y1".
Also in the second run, there are 2 nodes called "CASCODED_CMC_PMOS_31196023_PG0" in the hiertree. However, only the second node (index 2) is used, because the its parent node has "child" value 2. And in the second run, the placer got 2 "CASCODED_CMC_PMOS_31196023_PG0" node. Should there be only one?

Also this example is time-consuming. When I set the placer_sa_iterations==100 or 1000, there is no error.

You should use the --flow_start technique above to fix the long runtime. There error is when we run the router on stored data from the placer.
Let me look that the particular example above. What the placer did before is not very important. It needs to follow what is being specified in the placement verilog. I'll look through to make sure usage of CASCODED_CMC_PMOS_31196023_PG0 makes sense.

After you running routing (and in this case get a crash) two files get created in 3_pnr/inputs. One called: CASCODE_CURRENT_MIRROR_OTA.abstract_verilog.json and a second called: CASCODE_CURRENT_MIRROR_OTA.scaled_placement_verilog.json.
These two files are used to specify the problem for the router. The first is the verilog file used to build the PnRDB model. The second has the particular placement and selection assignment for all the instances. There are two concrete instances of CASCODE_CMC_PMOS_31196023_PG0 in the .scaled_placement_verilog.json file because to there are two instances in the netlists (which came from topological identification on different transistors). The placer selected different implementations so that is why there are two. There were forty generated by the placer. Only the two that are used are specified in these two files now.

How to make the second PnRDB the corresponding to the selection assignment? Use scaled_placement_verilog.json to build PnRDB?

More findings:
During the second run of PnRDB constrcution, the first "CASCODED_CMC_PMOS_31196023_PG0" uses "PMOS_4T_86154205_X3_Y1", the second "CASCODED_CMC_PMOS_31196023_PG0" uses "PMOS_4T_86154205_X1_Y3". This looks the same as scaled_placement_verilog.json.
But at the beginning of the placer, the nodeVec has two "CASCODED_CMC_PMOS_31196023_PG0" with "PMOS_4T_86154205_X1_Y3"

I guess it may be some something between the second PnRDB and the second placer. Is the second PnRDB built based on scaled_placement_verilog.json?

You need to build the PnRDB with:
CASCODE_CURRENT_MIRROR_OTA.abstract_verilog.json

Then you feed in the placement and selection information from
CASCODE_CURRENT_MIRROR_OTA.scaled_placement_verilog.json

This is all happening for you when you run:
schematic2layout.py ../../examples/cascode_current_mirror_ota/ -n 40 --flow_start 3_pnr:route

The python code also creates the map file (in memory) and the lef file. You should be able to debug just using this.

@854768750 I don't know what you mean by "At the beginning of the placer". Placer variant numbers have been reassigned from the original numbering when the placer was run. Only the variant that are needed are included and if they where _25 and _36 during placement then will still be _0 and _1 in the ".abstract_verilog.json" and ".scaled_placement_verilog.json" files. We only need to build up the variants that are need for this particular design.
We want to be able to import design that were generated by other placers so we need functionality like this.

I need the module's concrete name in https://github.com/ALIGN-analoglayout/ALIGN-public/blob/fix/multi_variant_placement_injection/align/pnr/manipulate_hierarchy.py#L164

What should be do now for this? I'm not sure I understand what you need here. The concrete template names are in the scaled placement verilog files (the verilog that is being parsed by your C++ code) so you should be able to do what you need from that.
I don't think the concrete names should be in the "abstract verilog file" (the one being used to build the PnRDB).
They can be in a map file if you need it. Let me know if you want to meet.

What should be do now for this? I'm not sure I understand what you need here. The concrete template names are in the scaled placement verilog files (the verilog that is being parsed by your C++ code) so you should be able to do what you need from that. I don't think the concrete names should be in the "abstract verilog file" (the one being used to build the PnRDB). They can be in a map file if you need it. Let me know if you want to meet.

Okay, I think the C++ code needs to parse concrete template names (now it does not). Is this your point?

The PnRDB in the second run is built in align/pnr/manipulate_hierarchy.py ?

Yes. It is there just to prepare the design for reloading into the router.
We can do it differently, but we want to allow other placement engines to inject a placement here.
That is why I generated the abstract_verilog and the scaled_placement_verilog from the data in the placer.
What is the exact problem? Doesn't the scaled_placement_verilog provide a legal assignment of hierarchical templates for the given abstract_verilog.
Do you want to generate a smaller failing testcase? I can probably do that if it is necessary (and if I know more about want exactly is causing the crash.)

Yes. It is there just to prepare the design for reloading into the router. We can do it differently, but we want to allow other placement engines to inject a placement here. That is why I generated the abstract_verilog and the scaled_placement_verilog from the data in the placer. What is the exact problem? Doesn't the scaled_placement_verilog provide a legal assignment of hierarchical templates for the given abstract_verilog.
Do you want to generate a smaller failing testcase? I can probably do that if it is necessary (and if I know more about want exactly is causing the crash.)

The problem is when building the Hiernode in function gen_abstract_verilog_d, some informarion such as concrete_name is not parsed. Because there are two nodes both have the same name CASCODED_CMC_PMOS_31196023_PG0, we need to have some other things to identify them.

This test case is a good one. No need to have another one at now.

@854768750 I don't know what you mean by "At the beginning of the placer". Placer variant numbers have been reassigned from the original numbering when the placer was run. Only the variant that are needed are included and if they where _25 and _36 during placement then will still be _0 and _1 in the ".abstract_verilog.json" and ".scaled_placement_verilog.json" files. We only need to build up the variants that are need for this particular design.
We want to be able to import design that were generated by other placers so we need functionality like this.

I also see the postfix "_0" or "_1" but they are in the "concrete_name".

This is the scaled_placement_verilog:
"modules": [
{
"abstract_name": "CASCODED_CMC_PMOS_31196023_PG0",
"concrete_name": "CASCODED_CMC_PMOS_31196023_PG0_0"
...
},
{
"abstract_name": "CASCODED_CMC_PMOS_31196023_PG0",
"concrete_name": "CASCODED_CMC_PMOS_31196023_PG0_1"
},
...
]

I think the way to identify them is to have the concrete name in the hiernode.

I guess I thought you could collect the concrete names from the scaled_placement_verilog and either extract the suffix number or keep your own table and assign the consecutive variant numbers when you copy (create an internal variant) for the PnRDB.

I guess I thought you could collect the concrete names from the scaled_placement_verilog and either extract the suffix number or keep your own table and assign the consecutive variant numbers when you copy (create an internal variant) for the PnRDB.

Because the hiertree and hiernode are built in _ReadVerilogJson, I think the only I can get concrete names is inside this function.

I could make it so that every concrete name in the scaled placement verilog has a unique verilog module in the abstract verilog. That ought to work, but why can't you copy the module in the placement loader part of the code. That must be what the placer is doing when you generate a new placement variant.

Because the only thing to identify the two nodes is concrete name. If concrete name in heirnode is missing, the placer cannot identify two hiernodes with the same name. Even though the placer gets the complete json string (each module has a different concrete name), it cannot assign one module's placement to the correct hidenode.

Seems like you topologically sort the modules (with unique concrete names) in the scaled placement verilog,and build them up one by one
When you reach a new concrete name, you make a copy of the module associated with the abstract name (already built in the PnRDB). I don't think you really need a copy either. You just need the placement datastructure (selection of which concrete template names for the instances, and the translation and flipping of the instances.)
Isn't this what you are doing anyway.

Let me describe what the placer can see now:
node1.name="CASCODED_CMC_PMOS_31196023_PG0"
node1.concrete_name=""
node2.name="CASCODED_CMC_PMOS_31196023_PG0"
node2.concrete_name=""

and
"modules": [
{
"abstract_name": "CASCODED_CMC_PMOS_31196023_PG0",
"concrete_name": "CASCODED_CMC_PMOS_31196023_PG0_0",
"X":1234560...
},
{
"abstract_name": "CASCODED_CMC_PMOS_31196023_PG0",
"concrete_name": "CASCODED_CMC_PMOS_31196023_PG0_1",
"X":2345670...
},
...
]

I do not think the placer can know which module is node1.

Seems like you topologically sort the modules (with unique concrete names) in the scaled placement verilog,and build them up one by one When you reach a new concrete name, you make a copy of the module associated with the abstract name (already built in the PnRDB). I don't think you really need a copy either. You just need the placement datastructure (selection of which concrete template names for the instances, and the translation and flipping of the instances.) Isn't this what you are doing anyway.

When the placer reache a new concrete name, it first search for the corresponding hiernode. Then it copies every value in the placement data structure into the hiernode.

Seems like you topologically sort the modules (with unique concrete names) in the scaled placement verilog,and build them up one by one

And I am not quite sure which "topologically sort" are you referring to. I guess is that deep first search to generate the traverse order?

I think there is an existing topoorder method in the PnRDB.

I looked through the abstract_verilog_json file and it seems that I'm giving you two things incorrectly.

There are two copies of the module CASCODED_CMC_PMOS_31196023_PG0 There should only be one.
The leaf cells have an abstract_template_name that seems to be a concrete_template_name. That should be changed to the abstract version.

I'll see if I can fix that up.

This latest change makes the abstract names and concrete names always be the same when we set up the problem from the router.
The names in the abstract_verilog_json are names with "_0" and "_1" suffixes. Each module in this file should have a unique module in the PnRDB.
There is crash now probably due to not have the constraint files named correctly. I'll work on that next.

okay, just let me know when it is solved. Maybe I also need to do some changes in PnR.

You shouldn't need to do any parsing of the names. Concrete and abstract names should be the same.

topcell in "CASCODE_CURRENT_MIRROR_OTA.scaled_placement_verilog.json" still has "_0"

No, it is important that the top level name include the "_0". This is to be consistent with the intermediate levels of hierarchy that definitely need the "_0" (or "_1").
Is there some other name that needs to be changed to include an "_0"? Something else in the call to create the PnRDB.

I think this works now.

@854768750 This looks good. I need to fix up some naming issues in the checker but it looks like the placement creation is good.

@854768750 I'm ready for you to look at this again. There are a number of failing testcases:
================================================================================ short test summary info =================================================================================
FAILED tests/constraints/test_constraint.py::test_donotroute - AssertionError: ckt_donotroute (CKT_DONOTROUTE_0_0):Number of DRC errorrs: 3
FAILED tests/constraints/test_constraint.py::test_netpriority - AssertionError: ckt_netpriority (CKT_NETPRIORITY_0_0):Number of DRC errorrs: 2
FAILED tests/constraints/test_constraint.py::test_placecloser - AssertionError: ckt_placecloser (CKT_PLACECLOSER_0_0):Number of DRC errorrs: 2
FAILED tests/pdk/finfet_pdk/test_placement_grid.py::test_scalings - AssertionError: ckt_scalings (CKT_SCALINGS_0_0):Number of DRC errors: 2
FAILED tests/pdk/finfet_pdk/test_placer.py::test_cmp_fast - AssertionError: ckt_cmp_fast (CKT_CMP_FAST_0_0):Number of DRC errors: 2
FAILED tests/pdk/finfet_pdk/test_placer.py::test_sub_1 - AssertionError: ckt_sub_1 (CKT_SUB_1_0_0):Number of DRC errors: 2
FAILED tests/pdk/finfet_pdk/test_placer.py::test_cmp_slow - AssertionError: ckt_cmp_slow (CKT_CMP_SLOW_0_0):Number of DRC errors: 2

They are all routing failures. A number of them are power routing related.

okay let me see
------------------ Original ------------------
From: "Steve @.>;
Date: 2022年6月1日(星期三) 凌晨2:28
To: @.>;
Cc: @.>; @.>;
Subject: Re: [ALIGN-analoglayout/ALIGN-public] Hierarchical Placement Injection fails with a high number of variants (PR #1083)
@854768750 I'm ready for you to look at this again. There are a number of failing testcases:
================================================================================ short test summary info ================================================================================= FAILED tests/constraints/test_constraint.py::test_donotroute - AssertionError: ckt_donotroute (CKT_DONOTROUTE_0_0):Number of DRC errorrs: 3 FAILED tests/constraints/test_constraint.py::test_netpriority - AssertionError: ckt_netpriority (CKT_NETPRIORITY_0_0):Number of DRC errorrs: 2 FAILED tests/constraints/test_constraint.py::test_placecloser - AssertionError: ckt_placecloser (CKT_PLACECLOSER_0_0):Number of DRC errorrs: 2 FAILED tests/pdk/finfet_pdk/test_placement_grid.py::test_scalings - AssertionError: ckt_scalings (CKT_SCALINGS_0_0):Number of DRC errors: 2 FAILED tests/pdk/finfet_pdk/test_placer.py::test_cmp_fast - AssertionError: ckt_cmp_fast (CKT_CMP_FAST_0_0):Number of DRC errors: 2 FAILED tests/pdk/finfet_pdk/test_placer.py::test_sub_1 - AssertionError: ckt_sub_1 (CKT_SUB_1_0_0):Number of DRC errors: 2 FAILED tests/pdk/finfet_pdk/test_placer.py::test_cmp_slow - AssertionError: ckt_cmp_slow (CKT_CMP_SLOW_0_0):Number of DRC errors: 2
They are all routing failures. A number of them are power routing related.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@854768750 @soneryaldiz All of them seem to not be doing power routing. (Or there are opens in the power and ground nets.)
@soneryaldiz What is test_donotroute suppose to check? There are three DRC errors now. I think there is supposed to be one, but I don't know how it gets passed the run_example check.

@stevenmburns , This test is supposed to check that a signal net is not routed given a DoNotRoute constraint. I will look into why it is failing.

@stevenmburns , when I run the test, it fails due to opens. However, the nets not to be routed should be excluded from the open check (see align/pnr/checkers.py line 300 and below. Debugging the code, hN.name is pointing to a concrete_name but not to the abstract name. This is breaking the code. Why is hN.name no longer the abstract name? hN also has concrete_name attribute.

For routing there doesn't need to be a distinction between abstract and concrete name (that is a placement concept.)
They are being set to the same thing in the placement verilog file. I'll look at what you are doing and see why we need a distinction between the two.

pnr_const_ds uses abstract names.

@soneryaldiz We are going to have to think about the right thing to do here. We might need to generate a second pnr_const_ds for the routing phase (separate from the placement phase.) [There are two different DBs now, and we are making changes to the design.] Then the names could be correct.

Do I need to do anything here now? Naming issue?


Get Ruby bindings to work with Tree class

Needs:

[x] Support for void return type
[ ] Support for sub-object return type
[x] Support for method arguments
[x] Support for constructors of base classes
[ ] Running multiple Ruby tests from CMake
[x] A TestTree.rb file

Work in progress in branch n140-enhanced-ruby-bindings


[Flash CC 2015] Bug during export images in different folders with the same name

An image worth a thousand words:

I guess it's a Flash CC bug.

Interesting. Flash Pro should rename to 02_1.png or something similar. It does this for symbol and instance names, but it seems like that may not be getting applied for media items. I'll let Adobe know.
I'm sure you already know, but the workaround is just renaming one of the two images.


Culqi\Error\UnableToConnect - Unable to connect to Culqi API

Hi i have done a culqi payment gateway by the guidelines of github -  https://github.com/culqi/culqi-php . Now i faced an error of Unable to connect to Culqi API.
What is the problem with this.? Please let me know if anybody knows. Its urgent.

I confirm.
he strangest thing is that the request is executed, the payment goes through (this can be seen in the personal account of culqi), but instead of a response about successful payment, the error Imposible conectar a Culqi API comes.


How can I get the training data?

Hi,
You can download and process images from the Oxford RobotCar dataset yourself here:
https://robotcar-dataset.robots.ox.ac.uk/datasets/
I used only cloudy/overcast weather conditions for my daytime images (due to sun overexposing the camera) and non-rainy weather for nighttime images (for consistency).

Hope you are doing well!
I think it is too hard  for me to process such many images by myself. Then I think I can't train the network without the training data. Can you package the training data you use for us to download? I will thank you very much!

I wish I could, but there’s licensing issues with me redistributing it.
Also it was on a university server, from which I graduated over a year ago, so I couldn’t even access it for you if I tried.

You don't need to download them all, of course.
Just like 2000-5000 per domain.

Wish you a bright future！
I think it is a interesting and valuable work! Should I download 2000-5000 cloudy/overcast weather images as daytime images  and 2000-5000  non-rainy weather images as nighttime images?

Exactly.
You'll also need to run their undistortion script to turn the images flat from fisheye lenses.
Thank you!


12.0 fix 780

Preliminary PR (fixes #780 ) to update pos_debt_notebook to v12. We are doing some functional tests. It is installing OK and everything is working so far.

The travis configuration is for v11 on the repo, so the tests will not succeed. I suppose that you are changing this on another PR/commit, right?

Yes, I'll take care about CI tools

I've merged 11.0 to 12.0 branch, so you need to rebase or resolve conflicts via github UI

I rebased the PR on the current v12 branch.

Thanks for contributing,
The module was ported to 12.0 here https://github.com/it-projects-llc/pos-addons/pull/815


Issue with analyseWGCNA

Hi I'm using human expression (694, 60504)
I'm getting this issue:
ValueError                                Traceback (most recent call last)
/tmp/ipykernel_459/790637460.py in
----> 1 pyWGCNA_5xFAD.analyseWGCNA()
2 #need to mod and get less times and samples
~/.local/lib/python3.8/site-packages/PyWGCNA/wgcna.py in analyseWGCNA(self, order, geneList, show)
386
387         if self.save:
--> 388             self.module_trait_relationships_heatmap(metaData=self.datExpr.obs.columns.tolist(),
389                                                     show=show,
390                                                     file_name='module-traitRelationships')
~/.local/lib/python3.8/site-packages/PyWGCNA/wgcna.py in module_trait_relationships_heatmap(self, metaData, show, file_name)
2761
2762         sns.set(font_scale=1.5)
-> 2763         res = sns.heatmap(self.moduleTraitCor.T, annot=labels, fmt="", cmap='RdBu_r',
2764                           vmin=-1, vmax=1, ax=ax, annot_kws={'size': 20, "weight": "bold"},
2765                           xticklabels=xlabels, yticklabels=ylabels)
~/.local/lib/python3.8/site-packages/seaborn/_decorators.py in inner_f(*args, **kwargs)
44             )
45         kwargs.update({k: arg for k, arg in zip(sig.parameters, args)})
---> 46         return f(**kwargs)
47     return inner_f
48
~/.local/lib/python3.8/site-packages/seaborn/matrix.py in heatmap(data, vmin, vmax, cmap, center, robust, annot, fmt, annot_kws, linewidths, linecolor, cbar, cbar_kws, cbar_ax, square, xticklabels, yticklabels, mask, ax, **kwargs)
551     if square:
552         ax.set_aspect("equal")
--> 553     plotter.plot(ax, cbar_ax, kwargs)
554     return ax
555
~/.local/lib/python3.8/site-packages/seaborn/matrix.py in plot(self, ax, cax, kws)
334
335         # Possibly rotate them if they overlap
--> 336         _draw_figure(ax.figure)
337
338         if axis_ticklabels_overlap(xtl):
~/.local/lib/python3.8/site-packages/seaborn/utils.py in _draw_figure(fig)
93     """Force draw of a matplotlib figure, accounting for back-compat."""
94     # See https://github.com/matplotlib/matplotlib/issues/19197 for context
---> 95     fig.canvas.draw()
96     if fig.stale:
97         try:
~/.local/lib/python3.8/site-packages/matplotlib/backends/backend_agg.py in draw(self)
392     def draw(self):
393         # docstring inherited
--> 394         self.renderer = self.get_renderer()
395         self.renderer.clear()
396         # Acquire a lock on the shared font cache.
~/.local/lib/python3.8/site-packages/matplotlib/_api/deprecation.py in wrapper(*inner_args, **inner_kwargs)
382             # Early return in the simple, non-deprecated case (much faster than
383             # calling bind()).
--> 384             return func(*inner_args, **inner_kwargs)
385         arguments = signature.bind(*inner_args, **inner_kwargs).arguments
386         if is_varargs and arguments.get(name):
~/.local/lib/python3.8/site-packages/matplotlib/backends/backend_agg.py in get_renderer(self, cleared)
409         reuse_renderer = (self._lastKey == key)
410         if not reuse_renderer:
--> 411             self.renderer = RendererAgg(w, h, self.figure.dpi)
412             self._lastKey = key
413         elif cleared:
~/.local/lib/python3.8/site-packages/matplotlib/backends/backend_agg.py in init(self, width, height, dpi)
82         self.width = width
83         self.height = height
---> 84         self._renderer = _RendererAgg(int(width), int(height), dpi)
85         self._filter_renderers = []
86
ValueError: Image size of 1440x102708 pixels is too large. It must be less than 2^16 in each direction.
Error in callback <function _draw_all_if_interactive at 0x7f703079bdc0> (for post_execute):

Hi,
Thanks for using PyWGCA.
To me, it seems you have too many traits and because of that, it couldn’t render the plot properly! but If you send me your pickle file, I can investigate it more deeply.
one quick way to solve it is by using module_trait_relationships_heatmap() and passing the subset of your trait (metaData)
more information about this function: https://mortazavilab.github.io/PyWGCNA/html/api.html?highlight=module_trait_relationships#PyWGCNA.wgcna.WGCNA.module_trait_relationships_heatmap

Thanks, that helped me trace the problem to the first column name. I didn't know that both sample columns have strict naming as "sample_id". I changed both column names, and it works
regards
J


Keep autocomplete menu open to prevent flickering

The autocomplete menu continually flicker in and out whilst typing whilst an arguably minor bug and not knowing what actions causes it to appear or disappear, I think keeping it open until:
a. a selection is made
b. it is closed using a key like escape
c. a user leaves insert mode
would improve the UX. I dimly recall an issue regarding this or something closely related so think the flickering might be recurring aka a regression.

Would it be possible to get a gif or a recording, @Akin909 ?
In addition, I'm assuming which editor.completions.mode are you using?
Thanks! 👍 , there definitely shouldn't be flickering. The behavior you described is the design and it's a bug if it isn't working like that. I'm just wondering if it's a specific case or if we can get more info.
There is one case I'm aware of - it seems to flicker frequently in the path-completion case:

But it'd be helpful to know if there are other manifestations too.

@Akin909 Does the problem still persist?


Expose zmq_z85_encode and zmq_z85_decode

Hi,
I would like to use the Z85 encoding (https://rfc.zeromq.org/spec:32/Z85/) in my project and I was wondering how much effort would it be to expose these functions. I see that a related function (zmq_curve_keypair) is already exposed, which internally uses Z85 encoding. I am willing to help, but I am completely new to node-gyp, and I do not have much c++ knowledge.
It seems to me that it is an easy win and not a lot of work, but I may miss something and I have limited time to spend on this, so any guidance is more than welcome.
Thanks in advance

you should check out some of @msealand's stuff on this and #414 has some background on the curvekeypair function

Thanks @reqshark I'll take a look at it


Reenable helix payload

See if we can skip a few tests instead of disabling the entire project on helix

Changes look good adding these to https://github.com/aspnet/AspNetCore/pull/7763


⚠ Samsung has degraded performance

In 21b37d3, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2372 ms

Resolved: Samsung performance has improved in 5d0371e.