Jscs has many 'babylon' dependencies and cannot be installed

Jscs has this kind of problematic babylon depency-hell.

npm(babylon) >= 6.7.0
npm(babylon) < 7.0.0
npm(babylon) >= 6.3.0

I tried to fix it with with

%nodejs_fixdep babylon "~6.7"

without success.
package can be found: https://build.opensuse.org/package/show/home:illuusio:nodejs-bundle/jscs

Same sort of problem is with 'postcss-cli' can't full fill commander dependency
https://build.opensuse.org/package/show/home:illuusio:nodejs-bundle/postcss-cli

@illuusio
Hi, I've been AFK for a while. I'll check that soon.

@illuusio
Hi, sorry for the long AFK.
Recently I've been rewriting nodejs-packaging and npkg into standard rubygem (yes over a year my ruby programming capability advanced!)
I re-designed the json structure, made it more reliable and easy to debug. I have resolved the biggest headache which is finding parents in json.
So you'll see an usable nodejs-packaging in one month (I finish the npkg tool now)
Marguerite

As I packaged some Nodejs packages with old one I salut if there will be new dependency parser because it's biggest headache currently.

@illuusio yes...that's why I decide to rewrite it to node2rpm...basically a few headaches in front of node module packaging:

parse module versions

why module versions become a problem since they follow semver.org? because old versions don't. so many weird and laughable old version strings that are hard to believe exist on the npmjs registry server. eg: 7.0.0-beta.0-ranges or 3.0.0-blind-testing or 2.0.0-prerelease-1+build20131010...

break the dependency loop if a module's dependencies and dependencies of the dependencies require the module itself. it's hard to imagine in C/C++ world...but exists everywhere in nodejs. So you need to be able to recognize the parent path (parent, grandparent, ..., till the root element), while finding the parent for a json object is a blank area in Ruby/other languages so no existing module can be used...I just design my own data structure and write my own parser.

@illuusio it may take longer time because I want to have node2rpm produce/update specfiles...so you don't need to do the copy work...

Note if you need some help or testing. It would neat to have some way to back out of npm packages like Atom.

@marguerite,
First of thank you so much for the wonderful program you have created. I recently started re-writing some of this program, I had been under the impression that it was abandoned since it had been a long time you had responded.
Anyhow, I would like to help. Here are some of the issues that I believe need be address or features that need be added, which I was on my way to completing:

Missing minor or patch number = wildcard.
To be more accurate the missing numbers are supposed to be desugar to
zero, like they were but also allow for flexibility. Hence, why
wildcards are better than zero in the code.
https://github.com/npm/node-semver

automatic spec generation, emulate what py2pack does for generation of spec for the various distros:
https://github.com/openSUSE/py2pack/tree/master/py2pack/templates

dedupe the installation tree and flatten, emulating what npm multi-stage install did, see here
https://github.com/npm/npm/issues/5919
https://docs.npmjs.com/cli/dedupe

add unit test to ensure code is working as expected

shrink sizes of functions and methods ---> following clean code philosophy http://swreflections.blogspot.ca/2012/12/rule-of-30-when-is-method-class-or.html

Please do not take this the wrong way. Like I have said, what you accomplished was amazing, I would like to help make it better though. Perhaps we can make a list of issues and features and fixes that need to be applied and we can both work on it.
I also put a lot of thought into the whole dependency tree issue. You are trying to replicate a lot of npm's functionality. So why not consider using npm? Instead of replicating the code and functionality, which ties the project into whatever changes it is that they make, one could just leverage npm like so,

create a temp directory in var for install and cache
install the node package into the temp directory, using verbosity
from the output of the npm install parse the versions of dependency hell
walk the install directory to gather the ideal and dedupe install tree
collect source files from cache directory

@hurricanehrndz
Thanks!
about the features you mentioned:

I wrote a 100% compatible "rubygem-node-semver": https://github.com/marguerite/rubygem-node-semver. so the problem has been identified and solved.

I just add spec generation feature for https://github.com/marguerite/rubygem-node2rpm tonight.

But It will just create from zero. As you know, we bundle nodejs dependencies so there'll be a lot of "SourceN" tags. And they are different among different releases. So an "update specfile" feature is a must. That means I need to write a RPM specfile parser in Ruby first (there's no such gem yet).

I'll take a look at "dedupe"

unit test will be done of course. Any way it's a standard gem and tests with "spec" should be added. I just leave that later.

yes, during the rewrite, I use modules/classes, so the coding style looks good now. but I'll read the post you shared.

And the reasons why I didn't use npm:

Back to when I created this project, the npm for openSUSE is not bundled into nodejs itself. but separately packaged with 200+ modules. and it always broke. so at that time I have no way to install the distribution's npm. That's why I think my program must "can work" without npm from the beginning.
Someday npm for openSUSE might be split and made to a bundle with my tool. I don't want packagers to bother with the chicken & egg problem.

Actually I think having nodejs installed locally to package nodejs stuff that build remotely on the build machine just not sound good. Because we have openSUSE Build Service, the way, build it locally first and then package, hasn't been an option for packagers for a long time.

And npm itself is not clean enough actually. my reworked implementation has these features that npm doesn't have (but you can also get it by you idea because you actually just install the module...):

my implementation has a license tag for every dependency...so I can pick them up, remove the duplicates, and form a license string "MIT AND ISC AND BSD-3-Clause" for the bundle. which is accurate. In you way...you have to unpack every tarball to get that string.

in my implementation, if a dependency with the same version occurs again. the existing one will be deleted. and a new one is created under the common parent of the two. eg: a->b->d->e->minimist and a->b->c->minimist, then minimist will be created under a. I don't know if npm has this, but I'm proud of my flat implementation.

Anyway...I think we should not implement a packaging tool that depends on npm...eg gem2rpm doesn't use the rubygem at all. because no one would like to be like a garbage collector hahaha...

well, seems I have implemented the dedupe feature occasionally...

Yes multi-stage install included a flattening of the dependency tree. So far the work you have done is amazing and I'm really impressed. You should be congratulated for your efforts.
ha ha, I totally feel you on the chicken before the egg scenario, that is why I had forked your project and started writing unit tests. I wanted to safely start refactoring the code. I knew I could write a packaging tool that depend on npm, but it killed me a little inside to do it, so I refrained. I'm glad you felt the same way.

I have read the new code and so far it looks leap and bonds ahead of what you had accomplished before. I'm no ruby programmer and the fact that I can read the code tells me its 100% better. I can start perhaps writing some test for the code, which framework where you hoping to use? Minitest or rspec?

remember to fork the rework project that is node2rpm. In the future nodejs-packaging will contain the RPM macros only...all functional stuff will be moved/ported into node2rpm

Will do, is there a specific test framework you wish to use?

Rspec is the only test framework I am familiar with...
Yes, and I should run RubyCop with my codes and configure my vi...(yes I just write codes with vi)...

I love vim too, and only use vim to write code.  See here:
https://i.redd.it/e9ipexyz6chy.png
Just read the intersect code which is your equivalent to npm's dedupe, really awesome code! I have quite a bit to do in order to learn ruby fully, but I do code in other languages.

Well I have to say, you have everything under control. There is not much I can add.  Please let us know once you have the rpms up on the build service.

Just wondering how close to a release are you?

about one week. you can see the files deleted are the files I implemented in node2rpm.

As this seems to be resolved.. closing


Trouble implementing a modal

Hi!
First of all - amazing project. Love the new API!
A small question, I'm having trouble implementing a modal, i.e. a component that has a sub-path and appears with the previous path "behind it".
Here's an example: https://codesandbox.io/s/nr50qor62j
The problem is: even though a modal component has a path prop (prop is "edit", so the modal should appear at "/clients/edit") that doesn't match the url (url is "/clients") the modal is still rendered.
What am I missing?
Thanks in advance!

NavBar is missing in your sandbox.
Judging by https://reach.tech/router/example/embedded-routers I think you're missing two things:

you need to wrap every Route component (with a path prop) inside a <Router>. Child route components are only automatically picked up when you render in the same component as direct children
you need to specify the path of ClientList as /clients/*, otherwise it won't match "/clients/edit"

I've simplified the code to make it easier to read.
I've also tried to add your suggestion of nested Router - it didn't help, now the route is not recognized at all. I'm probably missing something obvious here :(

It works for me if you navigate directly..
And for the button click, it seems you have to put the onAction callback inside actions object primaryAction={{ content: "Add", onAction: () => navigate("/clients/crap") }}

You are absolutely right. It does work. Silly me :)
Thank you!


📝 Add nextJS app example

This project illustrates how to import the clevertap-web-sdk on a nextJS app.
Since the module is designed for client-side only, for nextJS apps, one can't straightforwardly import the sdk like:
import clevertap from 'clevertap-web-sdk'

due to the library expecting for window object to be defined. See #52
Aside from a workaround, one can asyncly import it when the component mounts or just before an event push:
async function initializeClevertap(): Promise<CleverTap> {
  const clevertap = await import('clevertap-web-sdk')

  // clevertap.default.init(ACCOUNT_ID, TARGET_DOMAIN)
  // clevertap.privacy.push({ optOut: false })
  // clevertap.privacy.push({ useIP: false })
  clevertap.default.setLogLevel(3)

  return clevertap.default
}

This example app does not include the use of react context for simpler implemention or different state / context management.

Did this work for anyone?

yes

yes

Did you call the function inside a useEffect?
useEffect(() => {
initializeClevertap()
}, [])

@maurusrv  Kindly go through the sample Nextjs web app. Let us know if you are facing any issues here.
https://clevertap-next-demo.vercel.app/
Repo Link - https://github.com/KambleSonam/clevertap-next-demo

@maurusrv Kindly go through the sample Nextjs web app. Let us know if you are facing any issues here. https://clevertap-next-demo.vercel.app/ Repo Link - https://github.com/KambleSonam/clevertap-next-demo

@KambleSonam any differences that i miss between the demo repo and this PR? if none, it should be good as i also see the dev logs too on the demo site.

it has been a year or so since i created this PR. i am still new in contributing to open source so i don't know, should i close this now? I realize maintaining setups in this repo might become a hassle and does not really make sense since frameworks like next will always update. And the info in the description above is already good for others to stumble upon.

also, for the same reason that it has been a year, note that the sample is not using the latest next setup. but the clevertap integration still is relevant as this is still how our setup is right now when using the sdk on our nextjs clients. one can also consider just using the clevertap api using fetch instead if they are using custom events and not the system events.

thanks!


MarkDuplicates tested options

This is a tested change on ~5 Exomes, based on comments by @alneberg and @MaxUlysse in the Sarek gitter chat. Having this as a default worked very well for us.
PR checklist

[x] PR is made against dev branch
[ ] PR is a hotfix against master branch
[x] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[x] Ensure the test suite passes (./scripts/test.sh -p docker -t ALL).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: https://github.com/SciLifeLab/Sarek/blob/master/.github/CONTRIBUTING.md

Okay, this should do the trick - let me know if anything else is required, my nf-core knowledge is worthless in the face of Sarek!

I think it should be good, it there's an issue with the params, Travis should fail quickly.
Thanks for making the change, it was much faster than me trying to figure out with git how to make commits to your branch

Looks good to me now, Let's wait for the last tests to finish up!


Correct typo in SQS example

[One line description of your change]
Motivation:
Ran into an issue with a proof-of-concept, and after looking through issues, realized this was just a typo in the readme.
Modifications:
Corrected the comment and code.
Result:
Example in readme now works correctly with SQS!

@swift-server-bot test this please

Looks valid AFAICS, thanks!


Enable Source Link in Cake.Yaml

Requires Cake.Recipe 2.0.0 or newer https://github.com/cake-contrib/Cake.Recipe/releases/tag/2.0.0.
The current build is using Cake.Recipe 1.0.0.

🎉 This issue has been resolved in version 4.0.0 🎉 The release is available on:

GitHub Release
NuGet Package


Update stylesheet.md

This is very confusing to new people that StyleSheet.create doesn't state performance. I think you can achieve better design patters without using it. Only reason I see myself using it is if there are any performance benefits, but it seems not be the case.

Is there a performance hit for using Stylesheet?

Question is "Is there a performance hit for not using Stylesheet?"
There should be description on why thing as Stylesheet exists. If it is legacy thing then users need to know it.
I opened this PR to start a discussion as I couldn't find any other source of info for this.
For example this https://github.com/facebook/react-native/blob/master/Libraries/StyleSheet/StyleSheet.js#L218 is it true? Somewhere else I see that it is not true anymore. We should have this kind of information in docs.

Thanks for thinking of us, but it turns out this is just not in our purview at this moment. We may revisit in the future, but not today. Thanks for bringing it up!


Support for others payment gateway

Hey,
The package is really awesome and handy for make all things so easily workable.
But if there is a way or option to implement or extend to have the others gateway then it will be really incredible. Eg: A common interface to implement the others gateway our self.
Like you did as Illuminate\Contracts thing.
Thanks for the effort.

This package is for Stripe only I'm afraid.


Hi, when will the code be updated?

I have difficulty implementing RevIN on Informer.
I'm confused about what to do with the Decoder input of Informer, so I would like to refer to the official code.

Thank you for your interest in our work.
We have uploaded the official code.
You can use RevIN as following:
>>> from RevIN import RevIN
>>> revin_layer = RevIN(num_features)

>>> x_in = revin_layer(x_in, 'norm')
>>> x_out = informer(x_in) # your model
>>> x_out = revin_layer(x_out, 'denorm')

Hope it works out. :)

Hi again.
I appreciate you taking the time to respond to my question.
I've been able to run RevIN on Informer thanks to your code, but I still
have some questions about how RevIN works.
Did you use RevIN after standardization or just remove the standardization
in Informer?
[image: image.png]
I tried both two methods and the latter turned out to be much less
effective than the former. So I wonder how you deal with that.
ts-kim @.***> 于2022年5月17日周二 22:34写道：

Thank you for your interest in our work.
We have uploaded the official code.
You can use RevIN as following:

from RevIN import RevIN
revin_layer = RevIN(num_features)

x_in = revin_layer(x_in, 'norm')
x_out = informer(x_in) # your model
x_out = revin_layer(x_out, 'denorm')

Hope it works out. :)
—
Reply to this email directly, view it on GitHub
https://github.com/ts-kim/RevIN/issues/1#issuecomment-1128949521, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK5SRBRPXRNWZTAN5LWRRDDVKOU6PANCNFSM5V7CJP4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have difficulty implementing RevIN on Informer. I'm confused about what to do with the Decoder input of Informer, so I would like to refer to the official code.

Hello, I would like to ask how you added the RevIN in the Informer. The effect seems to be not obvious after I added it. Can you show me how you added the RevIN? My email is<EMAIL_ADDRESS>thank you very much.

Hi again. I appreciate you taking the time to respond to my question. I've been able to run RevIN on Informer thanks to your code, but I still have some questions about how RevIN works. Did you use RevIN after standardization or just remove the standardization in Informer? [image: image.png] I tried both two methods and the latter turned out to be much less effective than the former. So I wonder how you deal with that. ts-kim @.> 于2022年5月17日周二 22:34写道：
…
Thank you for your interest in our work. We have uploaded the official code. You can use RevIN as following: >>> from RevIN import RevIN >>> revin_layer = RevIN(num_features) >>> x_in = revin_layer(x_in, 'norm') >>> x_out = informer(x_in) # your model >>> x_out = revin_layer(x_out, 'denorm') Hope it works out. :) — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK5SRBRPXRNWZTAN5LWRRDDVKOU6PANCNFSM5V7CJP4A . You are receiving this because you authored the thread.Message ID: @.>

We used RevIN after z-score standardization in Informer. Since instance normalization is employed when RevIN is performed at the input layer, the normalized samples in a batch stay the same regardless of the presence of standardization. However, performance differences can exist because the value of gradients can still be influenced.

Hello, I would like to ask how you added the RevIN in the Informer. The effect seems to be not obvious after I added it. Can you show me how you added the RevIN? My email is<EMAIL_ADDRESS>thank you very much.

Hello, thank you for your interest in our work.
We have uploaded the RevIN codes for Informer. Please check it.


Thinking refactoring

Codecov Report
Base: 2.38% // Head: 2.38% // No change to project coverage :thumbsup:

Coverage data is based on head (e0bcccf) compared to base (41aa8cf).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@          Coverage Diff           @@
##           master      #6   +/-   ##
======================================
  Coverage    2.38%   2.38%
======================================
  Files           1       1
  Lines          42      42
======================================
  Hits            1       1
  Misses         41      41

Impacted Files
Coverage Δ

lib/app/modules/dashboard/dashboard_page.dart
2.38% <0.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Thoughts on adding a scikit-learn compatible API?

Is there any interest in either modifying the existing model class or adding a "wrapper" class (I'm leaning towards the latter as the better option) to implement the required methods and attributes to make keras more compatible with scikit-learn?  To be clear, I'm referring to the requirements outlined here.  No additional dependencies would be necessary, and it would allow developers already familiar with scikit-learn to use keras out-of-the-box alongside existing code/models.  I don't think any of the current code would have to be touched to achieve this.
Thoughts?  I can spend some time looking at this if there's a decent chance it would be accepted.

It wouldn't really be possible to make the model class sklearn-compatible, since Keras models work under very different constraints from sklearn. But it would definitely be possible to develop a sklearn-compatible wrapper that would give the user access to a subset of the functionality of the model class (under additional assumptions).
There are no immediate plans to build this, but the idea has been raised before... if you would like to give it a try, then you are welcome to do it, it would likely be accepted.

This is a great idea! We just started prototyping keras integration into scikit-neuralnetwork:
https://github.com/aigamedev/scikit-neuralnetwork
I'm wondering if I could make an argument for keeping the wrapper separate/compatible, for a couple reasons:

All NN implementations in Python could be wrapped under compatible APIs, helping the best implementation "win".  Our sklearn-compatible API has been through a couple iterations already.
It's useful for the Python community to help compete with Lua's advantage, also providing some stability.  Most users just want to get a package from PIP and have it just work, as we found out.
I think end-user support requests may be better off separate from the main project; most of the issues we had so far never needed to propagate upward to the underlying library...

I don't mean to hijack the thread, just adding my thoughts. I hope this happens either way :-)

Is this functionality still supported? I can't see any of the tests in the current master.
Also, it would be nice if models supported more of the sklearn workflow. For example, KerasClassifier cannot be used in cross_val_score because the underlying model cannot be cloned (because its get_params method does something different to what sklearn expects). Are there any plans to address this?

+1 on @mbatchkarov comment

There is a PR for this functionality here:
https://github.com/fchollet/keras/pull/1225/files
It wasn't merged because it looks to me like a big hack. If you think of a
cleaner, simpler way to do it, please submit a new PR.
On 11 February 2016 at 11:52, Gustavo De Mari Pereira <
<EMAIL_ADDRESS>wrote:

+1 on @mbatchkarov https://github.com/mbatchkarov comment
—
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/149#issuecomment-183035209.


3D Registration per FOV

@MaksHess Let's discuss the implementation of complex 3D image registration workflows from abbott here

Now being done in https://github.com/MaksHess/abbott


Where can downshift be improved?

Hey friends! I'm looking for feedback. Where can downshift be improved? This is an open-ended question and I'm looking for ideas. How can we improve the docs? What can we improve about the API? How can the implementation be improved?
A few ideas I have:

A legit website with an easier way to add or contribute to examples (I have some ideas here... Maybe it could just be a repo that could be loaded into codesandbox which we'd publish via netlify... Very easy to contribute to via codesandbox's github integration).
Some auxiliary component packages that implement a simpler, more opinionated and intrinsically useful autocomplete/dropdown/etc. on top of the downshift implementation.
Release 2.0.0 which will remove the breakingChanges prop and also bring improved support for TypeScript and Flow.

Any other ideas? Remember that downshift itself is intended to be extremely flexible, so if what you're looking for is a simpler API, then consider whether you could build a component on top of downshift that exposes that API. If that's possible then let's do it and publish that!

Remove jsnext:main field in the next major. It was initiated by rollup and deprecated (just with an issue) in it in favour of module field. It's better to not provide dead stuff which others copy in their projects.

Cool! Go ahead and make a PR for that whenever 👌

I used downshift for the first time today and I had a need to find out what element was changed in my onChange method. I don't know if there's already a way to get this info but I had to get the id from the stateAndHelpers and add -input to the end of the string before going ahead to find the element in the DOM.
If a better solution for this exists, I'd like to know. If not, it'll be cool to have. (I'll be glad to have my first open source contribution 😄  )

Hi @9jaswag, could you describe your use case further? Why do you need to know what element was changed? And what do you mean by "element was changed?"

@kentcdodds I have multiple downshift input fields on a page and in the onChange method, I'm setting selectedItem to state. I want to use the same onChange method for all the for all the input fields on the page.
From my little React knowledge, I do something like this `this.setState({ [event.target.name]: event.target.value }) and it sets the matching item in the state.
So, I wanted to do the same thing and I had to get the "name" attribute of the input field whose value was just selected. I ended up doing something like this:
onChange(selectedItem, stateAndHelpers) {
    const element = document.querySelector(`#${stateAndHelpers.id}-input`)
    this.setState({ [element.name]: selectedItem.name })
  }

So assuming the value of the input field with the name attribute username was changed, this.state.username would be set
I hope I was able to explain it clearly.

Gotcha. Here's what I'd do:
<Downshift onChange={(selectedItem) => this.onChange('first', selectedItem)} />

<Downshift onChange={(selectedItem) => this.onChange('second', selectedItem)} />

Then your onChange could be: onChange(elementName, selectedItem) {. Does that make sense?

Yes, it does. Thanks 😃

Could you file another issue about that please?

I'll do that

get rid of the lamda in the usage example, as lamdas are bad for performance.
I'm in the process of trying to figure out how to work DownShift without a lamda in my render method and it's pretty complicated. I want to pass things such as getInputProps and highlightedIndex down to a method called renderDownShiftChildren

Hi everyone,
I am wondering whether it is a valid use case to render multiple independently dropdown lists inside downshift.
I want to jump between multiple lists and safe the current highlightedIndex. I didn't find an example for that and tried this -> https://codesandbox.io/s/m339x2613p?module=%2Fsrc%2Fordered-examples%2Ftest-multi-dropdown-autocomplete.js but I am wondering whether there is a much simpler solution to that use case. 🤔🙈
Maybe a nice example could be added to the docs.

Some things I'd like to see in future versions are:

Smaller bundle size. Not sure how we'd achieve that but Downshift weights in a ~7kb which is a bit much IMO
Really like the idea of auxiliary component packages. I often use Downshift to implement a <select /> with custom styling. I'd be down to write this package if it comes to that!

It definitely could be smaller, but as far as components like downshift go, it's actually tiny! But we could redesign things a little bit to make it smaller.
I'd really love auxillary packages! We could have many I think that would make things really nice for people.

I love both of those ideas 👍👍

I think we should also make the build-conditional logic more terse. I think we can do this with a custom macro for this project. Anyone want to take that on?

I can do it, could you specify what do u mean by "we should also make the build-conditional logic more terse."?

Here's what I mean @Andarist: https://github.com/paypal/downshift/issues/540
This one will be fun :)

Another thing we should consider is improving composition so we don't have to have so much conditional logic. Perhaps create a base component that has the common logic, then expose dom and native-specific components on top of that for the differences... That may make things more complex though... Not less...

Perhaps create a base component that has the common logic, then expose dom and native-specific components on top of that for the differences

This would be pretty nice from the React Native side. There's a lot of window or document or DOM-specific things that the React Native version can't benefit from (and aria as a whole in this case too).
I know coming up with primitives to expose to both platforms might lead to some more complex code, but I think it might be nice to figure out a better strategy than what we have so far.

I did a local test using ’warning’ and/or ’invariant’ a while back, and the filesize savings was very minimal. I could have done something wrong, although I was using the babel plugin for them.
Anyway, doesn’t hurt to strip the warnings away. But is there a better way than using ‘warning’/‘invariant’ for this?

I don't expect to save a lot from stripping warnings personally, but it's probably not a bad idea. Let's open another issue for tracking that.
@eliperkins, I agree it's worth looking into. Let's open another issue for tracking that as well. I wont personally have time to work on it though.

Another thing I've thought about is to maybe move the typescript typings to the DefinitelyTyped project. Then you'd just import then from @types/downshift.
I'm not a TypeScript user so this won't affect me but here is a relevant comment/explanation from a member of the TypeScript team on why we might want to consider this.

Going to go ahead and close this one now :)


fix(inline-tabs): width of buttons

Describe pull-request
Fixed bug with buttons not being based on the widest one.
Solving issue
Fixes: AB#3291
How to test

Checkout branch
Run storybook for component package
Check that the button width for the inline tabs are based on the widest one.

Suggested test steps

[ ] Browser testing (Chrome, Safari, Firefox)
[ ] Keyboard operability
[ ] Interactive elements have labels.
[ ] Storybook controls
[ ] Design/controls/props is aligned with other components
[ ] Dark/light mode and variants
[ ] Input fields – values should be displayed properly
[ ] Events

Screenshots
Additional context

Tested and works OK. LGTM! Please, if Tegel one has the same logic make another PR to fix it there too if you have time.

Great! No, for tegel I have refactored the tabs to not reassign style in function parameter. Instead I use a method on the child element to reset it: https://github.com/scania-digital-design-system/sdds/pull/816/files#diff-1bea73f1286cce2c875cda337d53058e3e846e8d0f9f087c67ccf8fba0dd0587R54

Checked after the change with putting the tabHeight out of render. Works OK.


Update to zigler 0.13

Resolves #7
Based on E-xyza/zigler#483

coverage: 72.917%. remained the same
when pulling be9619571e3199cacf6f64e9f098bdff1c465702 on zigler_0.13
into 3c3a9e28d76fd23c9203a66e9dbe9fa6c403fe31 on main.


Compilation of references from bibliography file (.bib) not working

Hej, first of all i want to thank you for your contribution. I was really happy to find this plugin! Today, i tried to include a .bib file for referencing. But it seems, that the compilation process is not able to get the references right. File internal labels (\label{} and \ref{}) and also references to the bibliography file are not resolved in the pdf. Is there a quick fix?

The compilation process does not yet support bibtex. However, the next version (b0.5) contains full BibTeX support including compilation using bibtex or biber. @stenwessel is working on this right now. As soon as that is finished we will push b0.5.
For now I would suggest adding custom scripts to the run configuration that executes the commands necessary (see also stackexchange).
Or wait a little while for us to update the plugin :3

Thanks for the super fast reply! Thats great to hear. :) Can you give me an approximate release date? Since i want to write my master thesis with it, it's quite important for me.
Keep up the great work. I'm looking toward the new features.

Ask @stenwessel. He promised to do this part and should be finished soon. We have had some busy weeks at uni, which results in slower development time (we have postponed the due date already).
Considering JetBrains also has an approval time, I'd give it between 1 and 2 weeks. But it could be sooner.

@stenwessel of course, i'd be happy to receive a more precise answer. But one or two weeks is fair enough! Good to hear, that you are already that close to releasing it. Thanks for the fast feedback @RubenSchellekens. And of course good drive for your university projects!

We'll be fine :) You can always follow the development status on the Milestone and Project pages.

@RubenSchellekens Can you give me a hint how to add the bibtex command to the run configuration? Seems like i'm stuck here.

Run config > Before launch > Plus > Run External Tool.
I don't know how it works exactly, I only know it's there.

That is how far i got. But i'm not able to locate the bibtex compilation file.

No idea myself tbh.

@RubenSchellekens is master going to be merged into the bibtex branch anytime soon? Because then you'd have texify with working bibtex?

Won't help, the compilation part is not yet implemented.

@drderkummer status update: we have just released Beta 0.5 with full BibTeX support. You can download and install the ZIP manually (via Settings > Plugins > Install plugin from disk) or wait for a couple of days until it is available via the JetBrains plugin repository.
Hope you like it and good luck with your thesis!


Follower data-original-title is always title of first follower

div data-toggle="tooltip" title="follower100" class="avatar" style="background-image:url()" data-original-title="follower1"

Follow -> Unfollow -> Follow


internal: don't depend on cwd

bors r+
🤖

bors r+

bors r+

Would it make sense to use cap-std in rust-analyzer everywhere instead of std::fs?

Yeah, I am brewing something along those lines:
//! Linear types can change the world!

use std::{ffi::{OsStr, OsString}, fs, io, path::{Path, PathBuf}};

use paths::{AbsPath, AbsPathBuf};

pub struct Io {
    repr: IoRepr,
}

impl Io {
    pub fn new_real() -> Io {
        let repr = IoRepr::RealIo(RealIo);
        Io { repr }
    }

    // region:process
    pub fn utf8_output(&mut self, cmd: Cmd) -> io::Result<String> {
        match &mut self.repr {
            IoRepr::RealIo(repr) => repr.utf8_output(cmd),
        }
    }
    // endregion:process

    // region:fs
    pub fn exists(&mut self, path: &AbsPath) -> bool {
        match &mut self.repr {
            IoRepr::RealIo(repr) => repr.exists(path),
        }
    }
    pub fn read_dir(&mut self, path: &AbsPath) -> io::Result<Vec<io::Result<AbsPathBuf>>> {
        match &mut self.repr {
            IoRepr::RealIo(repr) => repr.read_dir(path),
        }
    }
    // endregion:fs
}

pub struct Cmd {
    pub prog: PathBuf,
    pub current_dir: AbsPathBuf,
    pub args: Vec<OsString>,
}

I've looked briefly at cap-std, but it seems rather complex, and I didn't see immediatelly if it's possible to mock it out.


[WIP] Mapper update

This PR contains a mapper written in the new mapping API in Legate core.

@marcinz The output is much better now: https://github.com/nv-legate/legate.numpy/runs/3466138826?check_suite_focus=true
This PR depends on #47 of the core, so this is somewhat expected. What I think would be useful is a dependency mechanism that could override the CI's default behavior. For example, we could think of making a dummy file in a designated location whose name is used to retrieve the dependent PR or branch of the core (and we should make sure the file is removed before the PR gets merged).


Add example

I am not sure if I have formatted this correctly but I would like to add an example to this page that my students can follow

Updated and merged, thank you!


asciidoctor-pdf -v throws exception (undefined method `checksum')

Hi
I installed ruby 2.7.0 via chocolatey. I tried to install asciidoctor-pdf via gem install but tried also bundle install. However in both cases I get the following error:
PS Z:\> asciidoctor-pdf -v
Traceback (most recent call last):
        10: from C:/tools/ruby27/bin/asciidoctor-pdf:23:in `<main>'
         9: from C:/tools/ruby27/bin/asciidoctor-pdf:23:in `load'
         8: from C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/bin/asciidoctor-pdf:5:in `<top (required)>'
         7: from C:/tools/ruby27/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
         6: from C:/tools/ruby27/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:92:in `require'
         5: from C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf.rb:5:in `<top (required)>'
         4: from C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf.rb:5:in `require_relative'
         3: from C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf/converter.rb:4:in `<top (required)>'
         2: from C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf/converter.rb:4:in `require_relative'
         1: from C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf/ext/ttfunk.rb:3:in `<top (required)>'
C:/tools/ruby27/lib/ruby/gems/2.7.0/gems/asciidoctor-pdf-1.5.0.beta.8/lib/asciidoctor/pdf/ext/ttfunk.rb:4:in `<class:Base>': undefined method `checksum' for class `TTFunk::Subset::Base' (NameError)

The starnge thing is that it runs perfectly well on an older computer. Is Ruby 2.7 compatible with asciidoctor-pdf?
Thanks for any help

This is a duplicate of #1461 and has already been fixed in master.

Thanks a lot!


logging enhancement CLOAK

Currently responses that have been modified by plugins_cloak show up as PASS in the log.  Create a new PluginsReturnCodeCloak so cloaked responses are logged as CLOAK

This is cool, thank you!
Maybe we should have the same for forwarded queries?


support constant [] and {} expression

close: #3043

Pull Request Test Coverage Report for Build 99163

0 of 0   changed or added relevant lines in 0 files are covered.
72 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.8%) to 78.072%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.LanguageGeneration/Extensions.cs
3
86.54%

/libraries/Microsoft.Bot.Expressions/parser/ExpressionEngine.cs
3
97.39%

/libraries/Microsoft.Bot.Expressions/obj/Debug/netstandard2.0/ExpressionBaseVisitor.cs
5
6.67%

/libraries/Microsoft.Bot.Expressions/obj/Debug/netstandard2.0/ExpressionLexer.cs
5
92.37%

/libraries/Microsoft.Bot.Expressions/obj/Debug/netstandard2.0/ExpressionBaseListener.cs
14
0.0%

/libraries/Microsoft.Bot.Expressions/BuiltInFunctions.cs
42
91.48%

Totals

Change from base Build 99136:
-0.8%

Covered Lines:
20867

Relevant Lines:
26728

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3


[FEATURE] integrated NAT-check command

Is your feature request related to a problem? Please describe.
NAT Traversal is not possible for symmetric NATs via UDP holepunching
Describe the solution you'd like
a command to check if your network is capable of establishing a p2p connection
Should be as easy as making 2 stun requests from the same socket and comparing the response

implemented auto check with https://github.com/maxomatic458/quic-send/commit/a739c8e2139d53023626f5eac180570429bf2ccd


Fix Repository stubs

Using something[] in docblocks is a bad practice (in fact I'd very much love to have a rule that would disallow it) because then you don't know if the keys are ints or strings. And in many cases when the syntax is used, it is actually a list<>.
I changed the types according to those found in Doctrine repositories. I find it a bit odd for ObjectRepository to not return list<> but this is how it is currently typed in Doctrine. EntityRepository is typed to return list<> as expected.

CI failure seems to be unrelated.

I explained in the PR description... I used the types from Doctrine repositories:

ObjectReposirory is typed to return array<int, T> instead of list, not sure why
DocumentRepository extends ObjectRepository without changing the type so I used the same
EntityRepository extends ObjectRepository but narrows the type down to list<T> so I did that.
If you want I can change it list everywhere but I can't tell whether such change is correct.


Bundle update

Also updated to latest Bundler.

@jonallured - noticed you've created a few of these. Would you be up for trying out a tool a friend and I have made to automatically bump Ruby dependencies? Obviously totally free for open-source (and always will be). Would really appreciate your feedback if so!


Added create key for admins and link to admin panel on the dashboard

My additions will be included in NANI's PR


docker on azure cloud

Hi have a 2016 server on azure I install docker on it but I am getting error when starts asks me for vt-x enable , it a cloud server I cannot enable it on bios so i tried [ wmic cpu get VirtualizationFirmwareEnabled] but it false so what more can i do plz help

Assuming that's what you're attempting here, you shouldn't use virtualbox driver nested inside other types of virtualization.
You can install Docker directly on Linux using curl get.docker.com | sh.


hideExpression missing formOptions

When evaluating a hideExpression there is no formOptions variable.
This means there is no simple way to reference the formOptions.data field and leads to the odd scenario where to access the form options you use this.options but to access the field options you use just options.
I think the only change required would be to add formOptions: $scope.options to the getFormlyFieldLikeLocals function.

Technically this should have almost everything that this has. I think the only thing that's missing is: originalModel, and formOptions. The other properties are actually properties on the $scope of the formly-form which is where the expression is evaluated and therefore you should have access to it in your expression.
I'd happily accept a (tested) PR to add these properties. If you're keen on it, that's great. If you need help, maybe someone from @formly-js/angular-formly-collaborators or @formly-js/angular-formly-collaborators-read could give you a little guidance. Thanks everyone!

I would like to create a PR for this bug. I am new to this project and have browsed through the formly docs a bit, and I have a basic understanding about this project now.

Great, you might take a look at the CONTRIBUTING.md file as well :+1:

Ok, I dug into the docs and found that adding formOptions: $scope.options probably won't work because hideExpression is evaluated against the form scope instead of the field scope. I will have to try to find if the field scope has been initialized or not and then obtain it's scope via its index.( Or at least, this is how I think it should be :P ).
As for the originalModel property, I am assuming that it will contain the field's model.

Yeah, originalModel can simply be: $scope.model (the form's $scope). formOptions will need to be $scope.options (the form's $scope)...

Ok, got it. Will submit a PR soon.

since it merged, we should close this one?

Yep! Feel free to close it. Thanks!

@kentcdodds maybe i don't get the right? or i missing something. even add label i can't do it. :smile:


Crash when analyzing BTC/USD on bitmex

My config.yml is
settings:
    update_interval: 30
    market_pairs:
        - BTC/USD

exchanges:
    bitmex:
        required:
            enabled: true

and the output is
enabled notifers: []
Starting default analyzer...
Found configured markets: ['BTC/USD']
Using the following exchange(s): ['bitmex']
Beginning analysis of bitmex
Beginning analysis of BTC/USD
Traceback (most recent call last):
  File "app.py", line 45, in <module>
    main()
  File "app.py", line 39, in main
    behaviour.run(settings['market_pairs'], settings['output_mode'])
  File "/app/behaviour.py", line 63, in run
    new_result = self._test_strategies(market_data, output_mode)
  File "/app/behaviour.py", line 89, in _test_strategies
    market_pair
  File "/app/behaviour.py", line 165, in _get_indicator_results
    market_pair
  File "/app/behaviour.py", line 328, in _get_analysis_result
    results = dispatcher[indicator](**dispatcher_args)
  File "/app/analyzers/indicators/mfi.py", line 33, in analyze
    mfi_values = abstract.MFI(dataframe, period_count).to_frame()
  File "talib/_abstract.pxi", line 352, in talib._ta_lib.Function.__call__
  File "talib/_abstract.pxi", line 383, in talib._ta_lib.Function.__call_function
  File "talib/_func.pxi", line 8454, in talib._ta_lib.MFI
Exception: volume is not double

I see the same problem.

If you disable mfi & obv, it is working.


blend O*NET + ESCO green skills list

[ ] generate new green skills list to include skills from both O*NET and ESCO

for next week


按照要求下的，但是提示有个参数和model不匹配。checkpoint不对

Error(s) in loading state_dict for OSTrack:
size mismatch for backbone.pos_embed_z: copying a param with shape torch.Size([1, 64, 768]) from checkpoint, the shape in current model is torch.Size([1, 144, 768]).

It seems that your downloaded model and the config file do not match.


New IDF 5.2.1 i2c driver appears to use busy wating

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
5.2.1
Espressif SoC revision.
ESP32S3
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
own
Power Supply used.
USB
What is the expected behavior?
A relatively slow communication device like i2c should never use busy waiting, when when using a synchronous API.
What is the actual behavior?
In i2c_master.c s_i2c_send_commands I found
'''
// For blocking implementation, we must wait done interrupt to update the status.
while (i2c_master->trans_done == false) {};
if (i2c_master->status != I2C_STATUS_ACK_ERROR && i2c_master->status != I2C_STATUS_TIMEOUT) {
atomic_store(&i2c_master->status, I2C_STATUS_DONE);
}
'''
This looks like busy-waiting until the transfer completes. I have not analyzed the details, so it could not be that bad as it looks.
In any case, if a task needs to wait for more than a couple of microseconds, it should block and not busy-wait to allow other tasks with same or lower priority to run during the wait time.
Steps to reproduce.
I had a glance at the sources of the driver while looking into issue #13398.
Debug Logs.
No response
More Information.
No response

@pggh The fix is already merged.... It will sync to github is several days... thanks

Fixed in https://github.com/espressif/esp-idf/commit/1517d61addbc77d6ba33833126e1ec9f91882dfd

https://github.com/espressif/esp-idf/commit/1517d61addbc77d6ba33833126e1ec9f91882dfd . I will close this issue now, and fix on 5.2 will be sync soon


Missing support for SPIR-V 1.5

With Vulkan 1.2 came a new revision of SPIR-V, revision 1.5.
Currently RGA doesn't support shaders compiled to that version and seem to only support shader compiled as SPIR-V 1.3.
Vulkan 1.2 is required to support SPIR-V from 1.0 to 1.5. However, it makes sense for new shader development to target the latest version of SPIR-V which reduces the number of extensions that need to be declared in a SPIR-V module and seems to brings fixes over the previous revisions.
It would be very appreciated if RGA was updated to support the latest version of SPIR-V.

Hi simondeschenes,
Are you referring to the Vulkan live driver mode (-s vulkan) or the Vulkan offline modes?

I am using the offline mode.

simondeschenes,
Thanks for the details.
SPIR-V 1.5 support would be added in Vulkan offline mode in a future RGA release.

Hi simondeschenes,
Do you still observe this issue with the latest release (version 2.4)?

issue solved


Lower border of text boxes not drawn

Before

After

Relevant config
NODE urano
        LABEL Urano
        LABELOFFSET N90
        NOTES urano
        POSITION 100 70
        ICON 100 110 rbox
AICONFILLCOLOR 220 220 220
AICONOUTLINECOLOR 255 0 0
        MAXVALUE 500000
[...]
NODE urano-cpu
        LABEL CPU {node:this:bandwidth_in:%d}%

        LABELFONTCOLOR contrast
        POSITION urano 0 -20
        TARGET gauge:/opt/cacti/rra/urano_fgsyscpuusage_2886.rrd:fgSysCpuUsage:-
        OVERLIBGRAPH /cacti/graph_image.php?local_graph_id=2102&rra_id=0&graph_nologend=true&graph_height=100&graph_width=300
        INFOURL /cacti/graph.php?rra_id=all&local_graph_id=2102
        MAXVALUE 100

NODE urano-sesiones
        LABEL {node:this:bandwidth_in:%d} sess
        LABELFONTCOLOR contrast
        POSITION urano 0 1
        TARGET gauge:/opt/cacti/rra/urano_session_count_2881.rrd:Session_Count:-
        OVERLIBGRAPH /cacti/graph_image.php?local_graph_id=2098&rra_id=0&graph_nologend=true&graph_height=100&graph_width=300
        INFOURL /cacti/graph.php?rra_id=all&local_graph_id=2098
        MAXVALUE 500000

NODE urano-memoria
        LABEL mem: {node:this:inpercent:%d}%
        LABELFONTCOLOR contrast
        POSITION urano 0 22
        TARGET gauge:/opt/cacti/rra/urano_fgsysmemusage_2887.rrd:fgSysMemUsage:-
        OVERLIBGRAPH /cacti/graph_image.php?local_graph_id=2103&rra_id=0&graph_nologend=true&graph_height=100&graph_width=300
        INFOURL /cacti/graph.php?rra_id=all&local_graph_id=2103
        MAXVALUE 100

NODE urano-rate
        LABEL sess/sec {node:this:bandwidth_in:%d}
        LABELFONTCOLOR contrast
        POSITION urano 0 43
        TARGET gauge:/opt/cacti/rra/urano_sess_setup_rate_1m_2882.rrd:Sess_setup_rate_1m:-
        OVERLIBGRAPH /cacti/graph_image.php?local_graph_id=2099&rra_id=0&graph_nologend=true&graph_height=100&graph_width=300
        INFOURL /cacti/graph.php?rra_id=all&local_graph_id=2099
        MAXVALUE 5000
[...]
NODE root
        LABEL root
        LABELOFFSET N90
        LABELFONTCOLOR contrast
        POSITION urano 200 0
        ICON 100 30 rbox
AICONFILLCOLOR 220 220 220
AICONOUTLINECOLOR 255 0 0
        MAXVALUE 500000
[...]
NODE root-sess
        LABEL {node:this:bandwidth_in:%d} sess
        LABELFONTCOLOR contrast
        POSITION root 0 0
        TARGET gauge:/opt/cacti/rra/urano_fgipsessnumber_3887.rrd:fgIpSessNumber:-
        OVERLIBGRAPH /cacti/graph_image.php?local_graph_id=3194&rra_id=0&graph_nologend=true&graph_height=100&graph_width=300
        INFOURL /cacti/graph.php?rra_id=all&local_graph_id=3194
        MAXVALUE 500000

Before
commit 4b816254defcc4a372c8b232d349180d78f0edf5 (HEAD -> develop, origin/develop, origin/HEAD)
Author: thurban<EMAIL_ADDRESS>Date:   Thu Jan 7 10:08:54 2021 +0100

    Remove CSS changes in favour of latest Map-Scrolling fix

SUSE Linux Enterprise Server 15 SP2
RRDtool 1.7.0
PHP 7.4.6
After
commit 2e3e4aa90e5c436a63c6d3f65dc6aa29c9c32bdd (HEAD -> develop, origin/develop, origin/HEAD)
Author: TheWitness<EMAIL_ADDRESS>Date:   Sat Feb 4 21:18:30 2023 -0500

    Updating CHANGELOG and README

Debian GNU/Linux 11
RRDtool 1.7.2
PHP 7.4.33

Looks off by a pixel.  Thanks for the examples.

Kind of weird.  When I first dropped them in my config, they rendered fine, then I went to switch a few things up and now I'm here:

Crazy you can not Group/UnGroup from the UI.

I dropped some very mild changes in my repo.  The math looks correct between versions.  Maybe get more time by the end of the week.

@nicolatron, any changes on your end?

No change, same behaviour.
This is with cacti-1.2.23 and
git log -1
commit f005cf4a43509d6d836ef91216b88ad4eda8537c (HEAD -> develop, origin/develop, origin/HEAD)
Author: TheWitness<EMAIL_ADDRESS>Date:   Fri Feb 24 17:07:07 2023 -0500

    Fixing #97 - Boost Auto-Detect

    Auto-set the boost setting instead of making it a discrete user setting

@TheWitness I've run some tests, on my side. And I think I missed relevant information in my config file. I think it's related with the font size (and maybe family?).
I'm using this:
FONTDEFINE 100 /opt/cacti/plugins/weathermap/docs/example/Vera.ttf 8
FONTDEFINE 101 /opt/cacti/plugins/weathermap/docs/example/Vera.ttf 7
[...]
NODE DEFAULT
        MAXVALUE 100
        LABELFONT 100
        LABELFONTCOLOR contrast

With that I get:

If I remove the "FONTDEFINE 100 /opt/cacti/plugins/weathermap/docs/example/Vera.ttf 8"
It renders ok:

If I change the 100 font to: "FONTDEFINE 100 /opt/cacti/plugins/weathermap/docs/example/Vera.ttf 9"
It renders ok:

We are also facing the same issue. Please tell me if you need information to help you troubleshoot.


Weird app/res/values/strings.xml issue

With the current code, everything works after building with ant clean debug.

But if I make two additions to app/res/values/strings.xml, something gets
weirdly corrupted.

Specifically, I added license and license_title test strings close to the
beginning as follows:

    <string name="app_name" translation_description="Application Title">Sky Map</string>
    <string name="license_title">This is a
quick test</string>
    <string name="license">This is a quick test
license</string>
    <string name="menu_settings">Settings</string>

Then some of the app data gets corrupted.  One example problem can be seen as
follows: Menu | Gallery | Omega Centauri | Find in sky.  Result: not found!
(In other testing, I had other results, such as its showing Omega Centauri in
the wrong part of the sky, near the Big Dipper.)

I don't know if it's some subtle bug somewhere in the code, or something wrong
with my build environment.

Original issue reported on code.google.com by arpruss on 22 Jan 2012 at 7:07
Attachments:

strings.xml

Hopefully the new gradle build and the cleaned up scripts (especially https://github.com/sky-map-team/stardroid/blob/android-10-release-1.7.0/build_skymap.sh) will make the process easier.  We agree - it's a pain - and we are working on better ways to handle internationalization of the star data.


ClojureScript plus CanvasKit = Browser target?

I have been perusing the next-gen UI toolkit domain for a while, and I think the two most interesting efforts are this project and Makepad.
Makepad is targeting desktop as well as the browser. The browser is a somewhat degraded experience, but plenty good enough to be useful for demos.
Do you think HumbleUI has any chance of supporting the browser as a target? At first glance, it looks like Skija+JWM can be replaced with CanvasKit getting called through ClojureScript...

Yeah, I think there’s a possibility, although I don’t really have it as a goal at this point


Tutorial for ignis logging

Summary
Details and comments

Looks good. @ajavadia might want it to go into terra.

The question I have is whether we include something like logger.log_to_file(qubit='1', t2='0.3') directly into the fitters.

Dave, no calls yet to the new logger have been added to the tomography or other code. If you have specific ideas on what to log let me know. Otherwise I'll look at tomography and offer a few calls that may be used as examples.

I was more musing; I think we would push the core code first because adding those tweaks later.

Sure - when do you plan to have it merged ?

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

This looks good. I'll see if we can do something similar for Terra, but for now let's keep them separate as the needs are a bit different (for terra we would want to log the transpilation or scheduling processes).
Perhaps import IgnisLogger, IgnisLogging and IgnisLogReader at __init__ for easier access.
The next step would be to update the internal codes of fitters, filters, etc. to automatically log, so that when logging is turned on, a lot of useful info is gathered automatically. You can decide what things will be info, debug, etc.

Hi Ali - added the import statements to init.py. Should we merge and then add the actual calls in fitters, filters etc ? I think Dave would also want to add some himself.

Can you write some tests?

Basically just push some of what's into the notebook into the unittest folder.

Can you also move the example log and the notebook as a new PR on https://github.com/Qiskit/qiskit-tutorials/tree/master/qiskit/ignis?
Update the formatting to look like those tutorial files.

David - I've added unit testing to the logging module.
Also copied the tutorial to qiskt-tutorials/qiskit/ignis.
Currently there is a lint issue in test_state_tomography.py:
test/tomography/test_state_tomography.py:100:40: E1101: Module 'numpy.random' has no 'random' member (no-member)
not sure why it is, I didn't try to rectify yet

@eliarbel I also noted the pylint issue. Not sure why it is popping up. numpy.random.random(3) is a valid code line. In the branch I'm working on I disabled the issue by adding # pylint: disable=E1101 (but this is kind of analogous to sticking your head in the sand, I'm still curious as to why this error is showing up at all).

I'll take a look, it might be that add extension-pkg-whitelist=numpy works (based on google search)


Mention keep_pressed_outside caveat in the BaseButton documentation

This closes #37790.

Thanks!

Cherry-picked for 3.2.2.


[FLINK-30669] update recent job status in flinkdeployment object

JIRA: https://issues.apache.org/jira/browse/FLINK-30669
What is the purpose of the change
This pull request fix an issue where incorrect job status is updated in FlinkDeployment resource.

I don't really see the value of this fix as the core operator logic such as observe/upgrades etc won't work when there are multiple jobs in a single application.

I don't really see the value of this fix as the core operator logic such as observe/upgrades etc won't work when there are multiple jobs in a single application.

Are we going to support running multiple jobs in a single application?   There are some use case to submitting multiple pipelines in the loop within the same batch job.  Then using the state field in jobStatus to query whether all the pipeline in that batch job has finished.

@litiliu multiple job support is not on our roadmap. In general we are not focusing on batch processing specific features currently.

Hi @gyfora IMHO, this is very minimalistic change which does not alter any existing flow. As you can see, in ApplicationObserver.java , just added sorting but still picks only one element from list and in JobStatusObserver adding if condition on jobid equality also does not change anything existing.
I have tested these changes. you could initiate workflows to see that it works fine.

I don't really see the value of this fix as the core operator logic such as observe/upgrades etc won't work when there are multiple jobs in a single application.

When there are multiple jobs running in sequence, everything works fine.

I agree @kmozaid if this doesn't affect existing jobs and improves some others then the change makes sense :)
Could you please add a unit test to guard this change against possible future regressions?

I agree @kmozaid if this doesn't affect existing jobs and improves some others then the change makes sense :)
Could you please add a unit test to guard this change against possible future regressions?

sure, let me add a test.

@gyfora 2 workflows awaiting approval. Could you help to approve it?


Compile errors in example customWire_DS3231onSAMD21.ino

Arduino: 1.8.19 (Mac OS X), Board: "Arduino Mega or Mega 2560, ATmega2560 (Mega 2560), Default printf"

customWire_DS3231onSAMD21:23:17: error: 'sercom0' was not declared in this scope
 TwoWire myWire(&sercom0, 6, 5);  // Create the new wire instance assigning it to pin 0 and 1
                 ^~~~~~~
/Users/jfoster/Documents/Arduino/libraries/RTClib/examples/customWire_DS3231onSAMD21/customWire_DS3231onSAMD21.ino:23:17: note: suggested alternative: 'strcoll'
 TwoWire myWire(&sercom0, 6, 5);  // Create the new wire instance assigning it to pin 0 and 1
                 ^~~~~~~
                 strcoll
/Users/jfoster/Documents/Arduino/libraries/RTClib/examples/customWire_DS3231onSAMD21/customWire_DS3231onSAMD21.ino: In function 'void SERCOM0_Handler()':
customWire_DS3231onSAMD21:29:12: error: 'class TwoWire' has no member named 'onService'; did you mean 'onReceive'?
     myWire.onService();
            ^~~~~~~~~
            onReceive
/Users/jfoster/Documents/Arduino/libraries/RTClib/examples/customWire_DS3231onSAMD21/customWire_DS3231onSAMD21.ino: In function 'void setup()':
customWire_DS3231onSAMD21:74:20: error: 'PIO_SERCOM_ALT' was not declared in this scope
   pinPeripheral(6, PIO_SERCOM_ALT);  // PAD[0]   //Assign SDA function to pin 0
                    ^~~~~~~~~~~~~~
customWire_DS3231onSAMD21:74:3: error: 'pinPeripheral' was not declared in this scope
   pinPeripheral(6, PIO_SERCOM_ALT);  // PAD[0]   //Assign SDA function to pin 0
   ^~~~~~~~~~~~~
exit status 1
'sercom0' was not declared in this scope

This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.

It appears from the comment that "this example will work with Arduino Zero, any Arduino MKR board based on SAMD21, Nano 33 IoT and any board by Adafruit, Sparkfun, Seeed Studio based on the same microcontroller" so this is probably expected.


Model validations & Unit testing

In this PR I add the following validations

For the User model:

Name must not be blank.
PostsCounter must be an integer greater than or equal to zero.

For the Post model:

Title must not be blank.
Title must not exceed 250 characters.
CommentsCounter must be an integer greater than or equal to zero.
LikesCounter must be an integer greater than or equal to zero.

Add unit specs for all of your models' methods and validations.

thank you @KayLemba


can I run this code with four 2080Ti GPUs

Hi @mooncakehub, thanks for your interest in this work!
The answer to your question is yes. You can choose a suitable segmentation backbone to fit the memory in your GPU machines. I list several options below for your reference:

Backbone
Backend
Memory
Training Time
FPS

MinkUNet18-W16
torchsparse
3.4 GB
-
-

MinkUNet34-W32
minkowski engine
11.5 GB
6.5 hours
12.2

MinkUNet34-W32
spconv
6.7 GB
2.0 hours
14.6

Cylinder3D
spconv
10.2 GB
-
-

Thank you for  your reply. it's really helpful


Settings Page layout changes

Test

https://kp.odysee.com

Issue

Closes #6363 split settings into separate subareas with navigation
Closes #6395 Advanced settings not persisting

"Advanced settings" page no longer exists.

Comments

I left the individual commits unsquashed to hopefully help the review.  Probably easiest to go through each commit one-by-one.
For medium and small screen layout, the navigation is hidden for now.  I think this is fine since we are now showing all settings (scroll) and the total settings is quite small.  If needed, we can probably display the navigation as a Tab at the top for these layouts.

Debt

"Creator Settings" remained in the old style. Will update the style together in an upcoming PR for "min tips".

Notes
https://www.notion.so/lbry/Settings-Page-Debt-d07a232a03fa469e8bae47ce2bf9e307

2cd691d to 2b53c74 (ready for review)
Notes:  https://www.notion.so/lbry/Settings-Page-Debt-d07a232a03fa469e8bae47ce2bf9e307

[ ] the drop-down carrot seems too close to the right side of the box

[ ] This page looks a bit strange to me with some of the grouped settings (tip) and dual pane (Similar to the other dual pane on system settings). Maybe if we added help test under each category and made the Tip heading > "Tipping with Comments" to fill in the heading (+ some simple help text).

[ ] Bank accounts listed twice

[ ] Center all pages? This should also say "Add a card" - the heading changes.

[ ] navigation steps count when switching settings pages, so the Back behavior is strange - goes back through each. Back should always go back to the previous non settings page right?

2b53c74 to fc4de99

Changed the "Back" button behavior from link-style (ala Chrome) to stack style.
Removed double "Bank Accounts" (merge error).
Moved "Homepages" to the top in [Appearance].
Switched from multi-pane to mult-row style per Tom's feedback.

The multi-pane version aimed to provide visual separation between label and value (left is always label, right is always value), but agree that it could be too clamped for radio buttons.

Added extra top-margin when navigating to a sub-section.


[@remote-dom/react] Fix a bug where props were not updated using react integration

I was testing this library and found possibly a bug in the logic for updating props using the react integration. It appears that directly setting the prop on the custom Element does not update the attribute.
// Does not work
element[prop] = propValue;

// Works
element.setAttribute(prop, propValue);

I was able to reproduce the issue on both Chrome v123 and FireFox v123

My test code

Here's my host code:
export const RemoteBox = ({
  padding = "none",
  color = "base",
  rounded = "none",
  children,
  ...props
}: RemoteBoxProps) => {
  return (
     // ...
  );
};

export const remoteBoxComponentTuple = [
  "ui-box",
  createRemoteComponentRenderer(RemoteBox),
] as const;

And the iframe code:

class BoxElement extends RemoteElement<RemoteBoxProps> {
  static get remoteProperties() {
    return ["color", "padding", "rounded"];
  }

  static get remoteSlots() {
    return ["children"];
  }
}

export const Box = createRemoteComponent("ui-box" as any, BoxElement);

export function Wrapper({
  data,
  componentName,
}: {
  data: any;
  componentName: string;
}) {
  return (
    <Box color="blue" padding="lg" rounded="lg">
      Hello
    </Box>
  );
}

In my example code, the color, padding, and rounded props where not getting applied to the custom element, hence the host mirrored element was not receiving any updates.

Before
After (non-children props are transferred)

This was not needed. I'd actually missed adding customElements.define("ui-box", BoxElement); which caused the issue.


Added option to allow the output files to carry the *.Generated.cs naming convention

Addressing #20

Update this to use -f|--transformfilenames to specify the transform as per first comment suggestion on #20

@hades200082 Thanks, Lee!
@ChristopherJennings will you have time to do a review?

@petrsvihlik I'll take a look at this sometime this week.

Thanks @ChristopherJennings, I'll take a look again this weekend and update the PR once done.

merged, thanks @hades200082 !


Login error

Does this occur consistently? Yes
Repro steps:

Type "azd auth login" or "azd auth login --use-device-code" in terminal.
The following error is displayed.
＊＊＊
ERROR: logging in: failed to authenticate: unable to resolve an endpoint: server response error:
Get "https://login.microsoftonline.com/organizations/v2.0/.well-known/openid-configuration": EOF
＊＊＊

Action: azure-dev.views.workspace.environment.resolve
Error type: Error
Error Message: Timed out waiting for a task to complete.
Version: 0.7.0
OS: win32
OS Release: 10.0.22621
Product: Visual Studio Code
Product Version: 1.84.2
Language: en

Call Stack
Timeout._onTimeout extension.js:2:938994

This may have been transient.  Are you still seeing this issue?

Thank you for your response. No, I don't have this issue anymore, so we  can close it now.

@jongio, Thank you for your response. No, I don't have this issue anymore, so it is closed now.


Next step: The music tracker

A web-based version of OpenMPT (for example) supported by patrons $$$

Yikes, that'd be some major scope-creep. I think I'll rather keep this as just a fun hobby project that I can work on when I feel like it.


RCNN is skipped when getitem?

In your default.yaml, both RPN.ENABLED and RCNN.ENABLED are TRUE.
Also in train_rcnn.py in line 160:

elif args.train_mode == 'rcnn':

    cfg.RCNN.ENABLED = True
    cfg.RPN.ENABLED = cfg.RPN.FIXED = True
    root_result_dir = os.path.join('../', 'output', 'rcnn', cfg.TAG)

But in kitti_rcnn_dataset.py line 231 in getitem,  RPN.ENABLED and RCNN.ENABLED are orgnized in an if-elif logic, where the RCNN part is skipped. Is that a bug?

def __getitem__(self, index):

    if cfg.RPN.ENABLED:
        return self.get_rpn_sample(index)
    elif cfg.RCNN.ENABLED:
        if self.mode == 'TRAIN':
            if cfg.RCNN.ROI_SAMPLE_JIT:
                return self.get_rcnn_sample_jit(index)
            else:
                return self.get_rcnn_training_sample_batch(index)
        else:
            return self.get_proposal_from_file(index)
    else:
        raise NotImplementedError

No, it is not a bug.
RPN.ENABLED and RCNN.ENABLED is set based on the argument --train_mode and --eval_mode in the train_rcnn.py and eval_rcnn.py. You could refer to these files for more details.

So is it that when training in "rcnn" mode, where RPN.ENABLED is always set as True, only get_rpn_sample() is used in the getitem()?


corporate: Add license ledger entry if paid plan is migrated from remote server to remote realm.

Updates handle_customer_migration_from_server_to_realm for:

Prep commit cleans up some of the remaining logic from when legacy plans were migrated to multiple realms on a remote server.
Handles calling update_license_ledger_for_automanaged_plan in the case that a paid plan with automated license management was migrated from a remote server to its single, human realm. This way the billing data is accurate for the realm on the server when the plan is next invoiced.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

This makes sense to me, merged, thanks @laurynmm!


Java CLI

Fixing #231, #265, #266, #267
Documentation: https://serving.konduit.ai/quickstart/quickstart-cli

@AlexDBlack ready for review now. Couldn't get the test coverage to 80% but this much should be fine in my opinion. Let me know if I should change something.
About the python CLI. I've added the logic for downloading the jar file if it's not present and then channeling the arguments to the main java CLI but we still need to figure out hosting the relevant jar files. Can we upload jar files into pip packages?


Add make target for fixing image permissions.

Until we fix the image bucket defaults, we can run this target after pushing new images to make sure they are publicly readable.

This change is


Update of the file CONTRIBUTING.md

Now for 3 years, two headings are missing action texts.
Let's Work on a New Feature
Let's Release a New Version of the papiNet API Standard
Add action texts or remove the headings.

Done, see commit b89579e.


Default value of the plankton.accessibility2fish.plk* parameters

@jhpoelen The plankton.accessibility2fish.plk* parameters are parameters estimated during the calibration process of the OSMOSE model. The value that the bridge should define for these parameters is: 0.

Implemented as suggested. Please verify.

The present issue has been resolved. Therefore, I am closing it today.


Icon Descriptions are missing

Version 2.0.0-beta1

Oh, you're right.
I completely missed it.
Luckily it's only the beta version.


Move separate quiet config value to verbosity

Fixes #520
Moves the separate quiet variable in the Config struct into the existing verbosity field; the Verbosity enum now has a Quiet value. When running, the presence of the quiet flag will set the verbosity to quiet, overriding any number of verbosity flags also in the CLI args.

Awesome, looks good. Thank you!


Footer

We need to make a footer that the admin can edit the image, title and text.
https://cloud.githubusercontent.com/assets/10239547/13799247/f89552b4-eb60-11e5-8051-c585fb0703c7.jpg

I'll do this.


Create "demo" environment

demo.libero.pub and similar URLs.
Problem / Motivation

WHO wants this? The marketing team
WHEN and WHERE do they want it? Before July 10th, as soon as possible
WHAT do they want? An environment with stricter uptime requirements
WHY do they want this? To give out the URL in press releases for external people to use.

Tasks

[ ] Create new instance of Terraform state in infrastructure called demo
[x] Parameterize sample-configuration to work with multiple environments
[x] Deploy to unstable and demo from environments
[ ] Document and test release process with tags
[ ] Investigate 0-downtime deployment
[ ] ...more to come...

Clarification needed and assumptions

How often should we deploy to demo? Just after unstable and its (smoke) tests have passed, or with a lower cadence (daily, weekly)?
Containers should not be turned off during deploy, to avoid downtime
We are still going to deploy to a single node as that's what sample-configuration supports

How often should we deploy to demo? Just after unstable and its (smoke) tests have passed, or with a lower cadence (daily, weekly)?

Probably needs to be stable, so without forcing controlled changes everywhere yet, make it manual?

make it manual?

Sounds like a deploy to trigger only on certain tags of environments. Yet those tags should include a set of versions rather than just latest for everything, to be reproducible.

https://demo.libero.pub/ is there, with just the fixture content, using the linked PRs. Everything ready for review.

https://travis-ci.com/libero/environments/requests helps debugging when builds don't start:
Branch "latest/20190629" not included per configuration.

https://travis-ci.com/libero/environments/builds/117178279 seems to have deployed on demo now.

https://travis-ci.com/libero/infrastructure/builds/117312485 is a similar tag-based build for demo.


Support for web

Hello,
I'm a Kotlin technical writer at JetBrains, currently working on updating the Kotlin Multiplatform samples page. This project is listed there, and as part of the update, I am mapping the samples to the platforms they support. As support for web is announced in this project, we tested it, but we couldn't make it work. For this reason, we couldn't promote NYTimes KMP as web in our samples page.
Given our goal of providing users with the best multiplatform experience, I wonder if there's an opportunity to update this project to include not only proper support, but also clearer instructions so that users can successfully run the app on the web platform.
Thank you in advance for considering this!
Best regards,
Alejandra Pedroza.

Hi @AlejandraPedroza
Currently, NYTimes works only on js target (as seen here https://xxfast.github.io/NYTimes-KMP/) but I'm working on adding the support for the wasm target (for which I had to add wasm support for my other two libraries KStore and Decompose Router - which is now unblocked)
Do you know what issues did you run into running the js client?
Cheers

Hi @AlejandraPedroza
I just added support for wasm targets and updated the readme with run instructions. Let me know if this is suffice

Hi! This is great! Thanks for the update. I'll test support for Kotlin//wasm and update our sample pages to mention that NYTimes KMP has support for the web.
Regarding the Js target, this is the issue we found when testing it:
The "browser" run configuration did not work:
ClassCastException
    at THROW_CCE (webpack-internal:///./kotlin/kotlin-kotlin-stdlib.js:5316:11)
    at CanvasBasedWindow (webpack-internal:///./kotlin/compose-multiplatform-core-compose-ui-ui.js:50163:63)
    at main$lambda (webpack-internal:///./kotlin/NYTimes-KMP-client-web.js:102:5)

Best regards,
Alejandra.


Updating source mapping variables based on issue

See https://github.com/themotleyfool/Klondike/issues/177 please review!!! As I still have no idea why this fixes it :/. Would like to find some documentation on this.

Thanks for investigating and submitting a PR! I'm not sure where I found example code to do this, but I didn't write it from scratch. As far as documentation is concerned, your guess is as good as mine :)


Streched exponential entropy

What is this PR?
This is an implementation of the stretched exponential entropy (Anteneodo & Plastino, 1999).
Contains:

The StretchedExponential entropy type, which implements entropy(e, probs::Probabilities), entropy(e, x, est::ProbabilitiesEstimator), and maximum(e, L::Int).
Analytical tests based on the constraints given in the original paper.
A documentation entropy for the entropy type.
A section in the documentation showing how the entropy behaves as a function of its parameters for a simple example. This is something we could/should include for the other entropy types too.

References
Anteneodo, C., & Plastino, A. R. (1999). Maximum entropy approach to stretched exponential probability distributions. Journal of Physics A: Mathematical and General, 32(7), 1089.

@Datseris Note: The example figure didn't run with the initial commit - it is fixed now.


Update java client integration test to use the embedded server

Change the TerrastoreClientIntegrationTest class so that it uses the embedded
terrastore server, thus making it self-contained.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 31 Oct 2010 at 9:28

Fixed (should be verified). Having trouble getting the tests to fire from
mvn/console.

Original comment by<EMAIL_ADDRESS>on 31 Oct 2010 at 12:00

Changed state: Fixed


Incorporate the following flags into our stack.yaml (and stack_linux.yaml):

-Wall
-Wcompat
-Wincomplete-record-updates
-Wincomplete-uni-patterns
-Wredundant-constraints

See the ghc-options: option in [stack manual](https://docs.haskellstack.org/en/stable/yaml_configuration/.
If some of this warnings break the build and the warnings cannot be easily fixed, then disable the warning in the offending file using the GHC pragma.

I don't mind to include all warnings not in Wall. We have only a few violations and quality improves by not using questionable constructs.


Added gizmos to help align interactable joints

This PR resolves request #584 by adding gizmos to align interactable hinges, sliders, and joysticks. This does cause minor breakage in that:

New origin nodes have been introduced where the ranges are visualized
Testing showed Y-Axis inversion on the slider and joystick

Demonstration Video
https://github.com/GodotVR/godot-xr-tools/assets/1863707/0bf443f5-5b3b-48b5-b953-c7ca4d866196
Slider Gizmo

Hinge Gizmo

Joystick Gizmo

@Malcolmnixon to revisit this, should rebase and see if any changes are required in order to merge.


Install Connman configuration through connman-conf recipe

Hi,
Would it be possible to move the connman configuration out of connman_%.bbappend, and put it in connman-conf.bbappend instead (like installed to tn.conf or similar)? See upstream meta/recipes-connectivity/connman.

@lgrosz
Thanks for the feedback. That's good advice.
Originally, this setting was to enable the WIFI/BT by default. So then it will be moved to the meta-tn-wifi meta layer.
https://github.com/TechNexion/meta-tn-imx-bsp/commit/caf2dcaf06bf01f07888ca945da77a1dcbef0fb7
https://github.com/TechNexion/meta-tn-wifi/commit/76bd6b3342902f8a8f8dffeb13913224debdb6b2
Ray

@lgrosz
Thanks for the feedback. That's good advice. Originally, this setting was to enable the WIFI/BT by default. So then it will be moved to the meta-tn-wifi meta layer.
caf2dca TechNexion/meta-tn-wifi@76bd6b3
Ray

This looks great, thank you!


Remove BinaryOps.SUB, use UnaryOps.NEG/BinaryOps.ADD

Refactored subtraction operations to use unary negation (UnaryOps.NEG) and addition (BinaryOps.ADD) instead of direct subtraction (BinaryOps.SUB). Changes include updates in tinygrad/function.py, adjustments in subtraction tests in test/test_uops.py, and removal of BinaryOps.SUB in tinygrad/renderer/llvmir.py.

Bounty awarded to #4977


[docs]: update docs

update documents

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


[feature] Duration comparison operators

Resolves #5022

Coverage decreased (-0.2%) to 88.247% when pulling 50ca32ebb5c94220285f0623fcda2a69de203c53 on youfoundron:duration-comparison-operators into e1601867b9bc1d86273c08b8d97182e1cf66c689 on moment:develop.

^ bump @marwahaha :)

> var twoDays = moment.duration({ days: 2 })
> var threeDays = moment.duration({ days: 3 })
> var fortyEightHours = moment.duration({ hours: 48 })
> +twoDays == fortyEightHours // true (notice plus sign)
> twoDays < fortyEightHours // false
> twoDays > fortyEightHours // false
> twoDays > fortyEightHours // false
> twoDays < threeDays // true
> twoDays <= fortyEightHours // true
> twoDays <= fortyEightHours // true

This is without even trying...


db: postgres cast int to bigint

Postgres compatibility: Cast columns of type INT to BIGINT. Closes #228

May want a migration specifically for PostgreSQL that does a
ALTER TABLE {table} ALTER COLUMN amount SET DATA TYPE {db.big_int};

for each of the tables having an amount already
(From docs -- I think the query is right but you'd need to check!)

The migrations aren't generated automatically, we would have to do that to make sure postgres continues to work as expected (or we ignore the issue and pretend as if nobody does anyqay)!
The LNbits integration uses its own Compat class where this is already handled so that should be ok without migration (I assume that's the most widespread Postgres usage with Cashu).
I would ignore and pretend all is good until someone files an issue except if you think otherwise! Would be cleaner to not to but maybe not worth it.


Add logging to the library

@zezha-msft,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Magnifying glass search for group members

Group node: Members cannot be a drop-down list as we start getting lots of registered users. Have the magnifying glass search for users.

Duplicate #98


Replace respawn template from MenuPosition to Spectator

GSRI missions are never played with multi-life
Dead players should not respawn and should automatically execute the Spectator template.

Actually not wanted, because spectator template is not compatible with MenuPosition, and this would be a pain to make compatible with OPEX. Let's have the current respawn / spectate menu.


Cholesky decomposition NotImplementedError and test

This is in reference to #852
The first PR is about adding the NotImplementedError and the respective test function, forgive all these PR and branches it is the first time I have worked on this.

Codecov Report

Merging #886 (3ba747f) into master (2d78c61) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #886   +/-   ##
=======================================
  Coverage   98.00%   98.00%
=======================================
  Files         129      129
  Lines       22604    22610    +6
=======================================
+ Hits        22152    22158    +6
  Misses        452      452

Impacted Files
Coverage Δ

tensornetwork/backends/jax/jax_backend_test.py
99.26% <ø> (ø)

tensornetwork/backends/abstract_backend.py
91.87% <100.00%> (+0.10%)
:arrow_up:

tensornetwork/backends/backend_test.py
100.00% <100.00%> (ø)

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 2d78c61...3ba747f. Read the comment docs.

@alewis The function name has been changed.

@alewis Thank you for everything, I will start adding the Cholesky function to the decomposition files, should I open a new issue for this or continue referencing this issue?


table: look at all points in the batch to determine column widths

In progressive mode, look at all the points in the first call to
consume when determining the set of columns and widths instead of
only looking at the first point.
Fixes #33.

@mstemm

lgtm.


chore: code splitting for multiple env feature

code split for EE feature

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

/ok-to-test

Adding test plan approved label for cypress changes.


Enummeration wrong for msoElementPrimaryValueAxisTitleAdjacentToAxis

The enummeration for msoElementPrimaryValueAxisTitleAdjacentToAxis is the same as for msoElementPrimaryValueAxisTitleNone (306)
For msoElementPrimaryValueAxisTitleAdjacentToAxis this should be 307.
Is also wrong in the VBA library.

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

ID: 7caaf1ab-f17a-470d-c7b9-3946451cc40a
Version Independent ID: 693272ff-1b02-56f1-854b-a50099c80259
Content: MsoChartElementType Enumeration (Office)
Content Source: api/Office.MsoChartElementType.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

@Berend-de-Vries
Thanks for this feedback. I changed 306 to 307 on the page you referenced, but cannot find any other instances in our documentation. Please send me links to pages where you want changes. Thanks.


Option to ignore Access Policies?

Discord discussion

Currently there's a checkbox on the repl to disable access policies for a given query.
It would be helpful to broaden this to the rest of the UI, specifically the data viewer.
Running configure session set apply_access_policies := false in the repl throws the following error: DisabledCapabilityError: cannot execute session configuration queries.

Appears fixed in 2.7.


Support pagination in autocomplete api

To support 'show more' button on the bottom of the dropdown menu, pagination must be supported in autocomplete api.
As Is

To Be

To solve this issue, Variable Model is added and pagination is applied to all variable models.


Property "prototype" is missing.

When i'm trying to get a prototype of constructor, which is passed as method option, compiler is throwing error 'Property "prototype" is missing,'.
Link: http://www.typescriptlang.org/Playground#src=declare class Foo {
	bar%3A number
}

class Baz {

    something(Constructor%3A Foo) {

		Constructor.prototype%3B %2F%2F prototype not found

    }

}
declare class Foo {
	bar: number
}

class Baz {

    something(Constructor: Foo) {

		Constructor.prototype; // prototype not found

    }

}

What's wrong? Why it error has appeared?

In your example, the parameter named Constructor is not actually typed as a constructor function, it's an instance of Foo. If you want to access the constructor of Foo itself, you should type the parameter as typeof Foo:
declare class Foo {
    bar: number
}

class Baz {
    something(Constructor: typeof Foo) {
        Constructor.prototype; // works
    }
}

Does that help?

Daniel,
Yes, you right. Thank you.
Please, close this case, it's not a issue.


The cloudant library will deprecate December 2021

Current pom file:
<dependency>
			<groupId>com.cloudant</groupId>
			<artifactId>cloudant-client</artifactId>
			<version>2.19.1</version>
		</dependency>

https://github.com/cloudant/java-cloudant: This library is now deprecated and will be end-of-life on Dec 31 2021.
Need to upgrade to cloudant-java-sdk.

not stale.

Hi! If you don't mind I will take this task.

@eduard-romanyuk it's yours!


Maya Load References - Add Display Handle Setting

Changelog Description
When we load a reference in Maya using OpenPype loader, display handle is checked by default and prevent us to select easily the object in the viewport.

I understand that some productions like to keep this option, so I propose to add display handle to the reference loader settings.

Testing notes:

Using Openpype loader in Maya, load an asset as reference.
Verify that Display Handle is following the settings.

I'm wondering whether we should maybe also add the option to allow enabling/disabling it for certain families/profiles? We mostly disabled it because we really didn't like it on e.g. rigs but did like it on some others. Nevertheless we still ended up disabling it completely just it because was much simpler at the time.

Not sure we need that right now unless you need it?
If someone wants it, they can implement profiles later.

Thanks a lot.

Just need those Hound fixes
Would need some cosmetics cleanup

Oops. Sorry.  vscode issues :)

Is there something missing to be adopted?


[Bug]Patch bundle tar has min version number

Describe the bug
The 1.1.1 bundle tarball, once you extract it, will show 1.1.0 version in the folder name.
This is because the 1.1.1 bundle is using 1.1.0 min, thus does not change the folder name accordingly.

drwxr-xr-x  9 zhujiaxi amazon      4096 Dec  9 23:09 opensearch-dashboards-1.1.0-linux-x64
-rw-r--r--  1 zhujiaxi amazon 201750620 Dec  9 23:11 opensearch-dashboards-1.1.1-linux-x64.tar.gz

To reproduce
Download any of the OpenSearch or Dashboards bundle for 1.1.1 then extract it.
https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/1.1.1/8/linux/x64/dist/opensearch/opensearch-1.1.1-linux-x64.tar.gz
https://ci.opensearch.org/ci/dbc/distribution-build-opensearch-dashboards/1.1.1/7/linux/x64/dist/opensearch-dashboards/opensearch-dashboards-1.1.1-linux-x64.tar.gz
Expected behavior
The internal folder within the tarball should have the same version as the one in tarball name.
Screenshots
If applicable, add screenshots to help explain your problem.
Host / Environment
No response
Additional context
No response
Relevant log output
No response

The version/folder name mismatch is failing the integration test since there is logic to look for the executable inside the extracted folder.