only icons not working except ios-*

i am trying to use login icon but not working
any icon starts with ios- work fine

code :
<Row style={styles.row}>

                            <Text style={styles.login}>
                                <Icon name='login'/> Login
                            </Text>
                        </Row>

That is because login is an invalid icon name. You see that yellow bar down below? That is the warning message. Click on it and it'll give you the names of all the valid icon names.

@sankhadeeproy007  where is the list of valid icons to search in it ? any link

NativeBase uses this for icons. Please check there for the complete list.

@sankhadeeproy007 I cannot understand you and your arrogance. The issue stated is clear, let me quote it again: "i am trying to use login icon but not working, any icon starts with ios- work fine".
So I run into this problem to. And in the link you @sankhadeeproy007 provide there is icon named "login". CTRL+F write "login" and you get it.
If you read the yellow warning it states that the prop types are the icon-set loaded from Ionicons by Ben Sperry, but if you open the list there are more icons there. So if you go to the source code, you will see that if you do not state a theme that uses different icon-set it will default to IonIcons, the one that start with the ios- prefix. But I don't understand why is that. There is no performance gain, all of the icons are required at the top.
Check it here
https://github.com/GeekyAnts/NativeBase/blob/master/Components/Widgets/Icon/index.js
Poor design. We are forking and fixing this soon.

@brankopesevski I cannot understand you but totally understand your ignorance. login is an invalid name because of the incorrect icon family. Is it a mistake that we didn't mention that we have set Ionicons as the default family? Yes. Have we documented it somewhere that we can change the icon family to a different one? Yes.
Did you go through the docs and try changing the iconFamily and then try login? Apparently no.
We set the default to Ionicons because it looks and feels closest to the native icons. You are ofcourse free to change it whatever you wish to.
Poor design? Maybe. There is always room for improvement.
Eagerly waiting for your

forking and fixing

My ignorance? LOL

You closed the issue with the statement

That is because login is an invalid icon name.

and than you gave the link with the icons from which there is icon with the name login

You didn't bothered to explain how the icons work with themes to @hishamkaram

So please, stop it about my ignorance.
Next, about the documentation. If I have to go to NativeBase Theme Variables to discover there is iconFamily variable used in the source code and than to go to the source code to discover that Icons work with switch statement where there is only one possible Icon-set to be used, than call me ignorant. I want to discover that when I am in the icon section of the documentation.
Pardon my ignorance, I am pessimist that the PR for the fix will be accepted as it will break a lot of stuff that I don't need In my use-case but other users of this components maybe will need it. Actually I am not sure if NativeBase will be part of my tools as I was expecting to save me some time in development but from my initial experience with it (less than 8 hours) I am spending more time browsing through the source code than actual product development.
If me and my team came to easy and elegant fix we are happy to contribute and create PR.

I closed it because this issue is a duplicate of #389, #358, #211, #209, #111, #64 and #62. You can LOL all you want to, but if you don't bother to check the previous issues regarding the same question and go all aggressive at me for closing a duplicate (with atleast 5 previous instances), ignorant fits you pretty well.
Still waiting for your elegant fix though!

Not a duplicate, and I did checked all issues related to Icon and Icons keyword. Even if it was a duplicate, you should mention that before closing the issue. Sorry for my aggressive approach, it is just a reaction to a closed issue without proper answer.
As I said before, I will submit PR only if I found an elegant fix that will not break the weird theme related design.

If you did indeed check the aforementioned issues and still think that it's not a duplicate, there's no point in taking this discussion further.
Also I'm curious to know where you get this sense of entitlement from. If you think this design is weird/poor, please suggest an alternative. We'd be happy to fix it and make it more user friendly.
Or better still elegantly fix and fork this soon?

if it helps anyone this is the error message from the console. I was using fa-arrows as the icon name instead of just arrows (FontAwesome). This throws a list of icon names to be used.
Failed prop type: Invalid prop name of value fa-arrows supplied to Icon, expected one of ["ios-add","ios-add-circle","ios-add-circle-outline","ios-add-outline","ios-alarm","ios-alarm-outline","ios-albums","ios-albums-outline","ios-alert","ios-alert-outline","ios-american-football","ios-american-football-outline","ios-analytics","ios-analytics-outline","ios-aperture","ios-aperture-outline","ios-apps","ios-apps-outline","ios-appstore","ios-appstore-outline","ios-archive","ios-archive-outline","ios-arrow-back","ios-arrow-back-outline","ios-arrow-down","ios-arrow-down-outline","ios-arrow-dropdown","ios-arrow-dropdown-circle","ios-arrow-dropdown-circle-outline","ios-arrow-dropdown-outline","ios-arrow-dropleft","ios-arrow-dropleft-circle","ios-arrow-dropleft-circle-outline","ios-arrow-dropleft-outline","ios-arrow-dropright","ios-arrow-dropright-circle","ios-arrow-dropright-circle-outline","ios-arrow-dropright-outline","ios-arrow-dropup","ios-arrow-dropup-circle","ios-arrow-dropup-circle-outline","ios-arrow-dropup-outline","ios-arrow-forward","ios-arrow-forward-outline","ios-arrow-round-back","ios-arrow-round-back-outline","ios-arrow-round-down","ios-arrow-round-down-outline","ios-arrow-round-forward","ios-arrow-round-forward-outline","ios-arrow-round-up","ios-arrow-round-up-outline","ios-arrow-up","ios-arrow-up-outline","ios-at","ios-at-outline","ios-attach","ios-attach-outline","ios-backspace","ios-backspace-outline","ios-barcode","ios-barcode-outline","ios-baseball","ios-baseball-outline","ios-basket","ios-basket-outline","ios-basketball","ios-basketball-outline","ios-battery-charging","ios-battery-charging-outline","ios-battery-dead","ios-battery-dead-outline","ios-battery-full","ios-battery-full-outline","ios-beaker","ios-beaker-outline","ios-beer","ios-beer-outline","ios-bicycle","ios-bicycle-outline","ios-bluetooth","ios-bluetooth-outline","ios-boat","ios-boat-outline","ios-body","ios-body-outline","ios-bonfire","ios-bonfire-outline","ios-book","ios-book-outline","ios-bookmark","ios-bookmark-outline","ios-bookmarks","ios-bookmarks-outline","ios-bowtie","ios-bowtie-outline","ios-briefcase","ios-briefcase-outline","ios-browsers","ios-browsers-outline","ios-brush","ios-brush-outline","ios-bug","ios-bug-outline","ios-build","ios-build-outline","ios-bulb","ios-bulb-outline","ios-bus","ios-bus-outline","ios-cafe","ios-cafe-outline","ios-calculator","ios-calculator-outline","ios-calendar","ios-calendar-outline","ios-call","ios-call-outline","ios-camera","ios-camera-outline","ios-car","ios-car-outline","ios-card","ios-card-outline","ios-cart","ios-cart-outline","ios-cash","ios-cash-outline","ios-chatboxes","ios-chatboxes-outline","ios-chatbubbles","ios-chatbubbles-outline","ios-checkbox","ios-checkbox-outline","ios-checkmark","ios-checkmark-circle","ios-checkmark-circle-outline","ios-checkmark-outline","ios-clipboard","ios-clipboard-outline","ios-clock","ios-clock-outline","ios-close","ios-close-circle","ios-close-circle-outline","ios-close-outline","ios-closed-captioning","ios-closed-captioning-outline","ios-cloud","ios-cloud-circle","ios-cloud-circle-outline","ios-cloud-done","ios-cloud-done-outline","ios-cloud-download","ios-cloud-download-outline","ios-cloud-outline","ios-cloud-upload","ios-cloud-upload-outline","ios-cloudy","ios-cloudy-night","ios-cloudy-night-outline","ios-cloudy-outline","ios-code","ios-code-download","ios-code-download-outline","ios-code-outline","ios-code-working","ios-code-working-outline","ios-cog","ios-cog-outline","ios-color-fill","ios-color-fill-outline","ios-color-filter","ios-color-filter-outline","ios-color-palette","ios-color-palette-outline","ios-color-wand","ios-color-wand-outline","ios-compass","ios-compass-outline","ios-construct","ios-construct-outline","ios-contact","ios-contact-outline","ios-contacts","ios-contacts-outline","ios-contract","ios-contract-outline","ios-contrast","ios-contrast-outline","ios-copy","ios-copy-outline","ios-create","ios-create-outline","ios-crop","ios-crop-outline","ios-cube","ios-cube-outline","ios-cut","ios-cut-outline","ios-desktop","ios-desktop-outline","ios-disc","ios-disc-outline","ios-document","ios-document-outline","ios-done-all","ios-done-all-outline","ios-download","ios-download-outline","ios-easel","ios-easel-outline","ios-egg","ios-egg-outline","ios-exit","ios-exit-outline","ios-expand","ios-expand-outline","ios-eye","ios-eye-off","ios-eye-off-outline","ios-eye-outline","ios-fastforward","ios-fastforward-outline","ios-female","ios-female-outline","ios-filing","ios-filing-outline","ios-film","ios-film-outline","ios-finger-print","ios-finger-print-outline","ios-flag","ios-flag-outline","ios-flame","ios-flame-outline","ios-flash","ios-flash-outline","ios-flask","ios-flask-outline","ios-flower","ios-flower-outline","ios-folder","ios-folder-open","ios-folder-open-outline","ios-folder-outline","ios-football","ios-football-outline","ios-funnel","ios-funnel-outline","ios-game-controller-a","ios-game-controller-a-outline","ios-game-controller-b","ios-game-controller-b-outline","ios-git-branch","ios-git-branch-outline","ios-git-commit","ios-git-commit-outline","ios-git-compare","ios-git-compare-outline","ios-git-merge","ios-git-merge-outline","ios-git-network","ios-git-network-outline","ios-git-pull-request","ios-git-pull-request-outline","ios-glasses","ios-glasses-outline","ios-globe","ios-globe-outline","ios-grid","ios-grid-outline","ios-hammer","ios-hammer-outline","ios-hand","ios-hand-outline","ios-happy","ios-happy-outline","ios-headset","ios-headset-outline","ios-heart","ios-heart-outline","ios-help","ios-help-buoy","ios-help-buoy-outline","ios-help-circle","ios-help-circle-outline","ios-help-outline","ios-home","ios-home-outline","ios-ice-cream","ios-ice-cream-outline","ios-image","ios-image-outline","ios-images","ios-images-outline","ios-infinite","ios-infinite-outline","ios-information","ios-information-circle","ios-information-circle-outline","ios-information-outline","ios-ionic","ios-ionic-outline","ios-ionitron","ios-ionitron-outline","ios-jet","ios-jet-outline","ios-key","ios-key-outline","ios-keypad","ios-keypad-outline","ios-laptop","ios-laptop-outline","ios-leaf","ios-leaf-outline","ios-link","ios-link-outline","ios-list","ios-list-box","ios-list-box-outline","ios-list-outline","ios-locate","ios-locate-outline","ios-lock","ios-lock-outline","ios-log-in","ios-log-in-outline","ios-log-out","ios-log-out-outline","ios-magnet","ios-magnet-outline","ios-mail","ios-mail-open","ios-mail-open-outline","ios-mail-outline","ios-male","ios-male-outline","ios-man","ios-man-outline","ios-map","ios-map-outline","ios-medal","ios-medal-outline","ios-medical","ios-medical-outline","ios-medkit","ios-medkit-outline","ios-megaphone","ios-megaphone-outline","ios-menu","ios-menu-outline","ios-mic","ios-mic-off","ios-mic-off-outline","ios-mic-outline","ios-microphone","ios-microphone-outline","ios-moon","ios-moon-outline","ios-more","ios-more-outline","ios-move","ios-move-outline","ios-musical-note","ios-musical-note-outline","ios-musical-notes","ios-musical-notes-outline","ios-navigate","ios-navigate-outline","ios-no-smoking","ios-no-smoking-outline","ios-notifications","ios-notifications-off","ios-notifications-off-outline","ios-notifications-outline","ios-nuclear","ios-nuclear-outline","ios-nutrition","ios-nutrition-outline","ios-open","ios-open-outline","ios-options","ios-options-outline","ios-outlet","ios-outlet-outline","ios-paper","ios-paper-outline","ios-paper-plane","ios-paper-plane-outline","ios-partly-sunny","ios-partly-sunny-outline","ios-pause","ios-pause-outline","ios-paw","ios-paw-outline","ios-people","ios-people-outline","ios-person","ios-person-add","ios-person-add-outline","ios-person-outline","ios-phone-landscape","ios-phone-landscape-outline","ios-phone-portrait","ios-phone-portrait-outline","ios-photos","ios-photos-outline","ios-pie","ios-pie-outline","ios-pin","ios-pin-outline","ios-pint","ios-pint-outline","ios-pizza","ios-pizza-outline","ios-plane","ios-plane-outline","ios-planet","ios-planet-outline","ios-play","ios-play-outline","ios-podium","ios-podium-outline","ios-power","ios-power-outline","ios-pricetag","ios-pricetag-outline","ios-pricetags","ios-pricetags-outline","ios-print","ios-print-outline","ios-pulse","ios-pulse-outline","ios-qr-scanner","ios-qr-scanner-outline","ios-quote","ios-quote-outline","ios-radio","ios-radio-button-off","ios-radio-button-off-outline","ios-radio-button-on","ios-radio-button-on-outline","ios-radio-outline","ios-rainy","ios-rainy-outline","ios-recording","ios-recording-outline","ios-redo","ios-redo-outline","ios-refresh","ios-refresh-circle","ios-refresh-circle-outline","ios-refresh-outline","ios-remove","ios-remove-circle","ios-remove-circle-outline","ios-remove-outline","ios-reorder","ios-reorder-outline","ios-repeat","ios-repeat-outline","ios-resize","ios-resize-outline","ios-restaurant","ios-restaurant-outline","ios-return-left","ios-return-left-outline","ios-return-right","ios-return-right-outline","ios-reverse-camera","ios-reverse-camera-outline","ios-rewind","ios-rewind-outline","ios-ribbon","ios-ribbon-outline","ios-rose","ios-rose-outline","ios-sad","ios-sad-outline","ios-school","ios-school-outline","ios-search","ios-search-outline","ios-send","ios-send-outline","ios-settings","ios-settings-outline","ios-share","ios-share-alt","ios-share-alt-outline","ios-share-outline","ios-shirt","ios-shirt-outline","ios-shuffle","ios-shuffle-outline","ios-skip-backward","ios-skip-backward-outline","ios-skip-forward","ios-skip-forward-outline","ios-snow","ios-snow-outline","ios-speedometer","ios-speedometer-outline","ios-square","ios-square-outline","ios-star","ios-star-half","ios-star-half-outline","ios-star-outline","ios-stats","ios-stats-outline","ios-stopwatch","ios-stopwatch-outline","ios-subway","ios-subway-outline","ios-sunny","ios-sunny-outline","ios-swap","ios-swap-outline","ios-switch","ios-switch-outline","ios-sync","ios-sync-outline","ios-tablet-landscape","ios-tablet-landscape-outline","ios-tablet-portrait","ios-tablet-portrait-outline","ios-tennisball","ios-tennisball-outline","ios-text","ios-text-outline","ios-thermometer","ios-thermometer-outline","ios-thumbs-down","ios-thumbs-down-outline","ios-thumbs-up","ios-thumbs-up-outline","ios-thunderstorm","ios-thunderstorm-outline","ios-time","ios-time-outline","ios-timer","ios-timer-outline","ios-train","ios-train-outline","ios-transgender","ios-transgender-outline","ios-trash","ios-trash-outline","ios-trending-down","ios-trending-down-outline","ios-trending-up","ios-trending-up-outline","ios-trophy","ios-trophy-outline","ios-umbrella","ios-umbrella-outline","ios-undo","ios-undo-outline","ios-unlock","ios-unlock-outline","ios-videocam","ios-videocam-outline","ios-volume-down","ios-volume-down-outline","ios-volume-mute","ios-volume-mute-outline","ios-volume-off","ios-volume-off-outline","ios-volume-up","ios-volume-up-outline","ios-walk","ios-walk-outline","ios-warning","ios-warning-outline","ios-watch","ios-watch-outline","ios-water","ios-water-outline","ios-wifi","ios-wifi-outline","ios-wine","ios-wine-outline","ios-woman","ios-woman-outline","logo-android","logo-angular","logo-apple","logo-bitcoin","logo-buffer","logo-chrome","logo-codepen","logo-css3","logo-designernews","logo-dribbble","logo-dropbox","logo-euro","logo-facebook","logo-foursquare","logo-freebsd-devil","logo-github","logo-google","logo-googleplus","logo-hackernews","logo-html5","logo-instagram","logo-javascript","logo-linkedin","logo-markdown","logo-nodejs","logo-octocat","logo-pinterest","logo-playstation","logo-python","logo-reddit","logo-rss","logo-sass","logo-skype","logo-snapchat","logo-steam","logo-tumblr","logo-tux","logo-twitch","logo-twitter","logo-usd","logo-vimeo","logo-whatsapp","logo-windows","logo-wordpress","logo-xbox","logo-yahoo","logo-yen","logo-youtube","md-add","md-add-circle","md-alarm","md-albums","md-alert","md-american-football","md-analytics","md-aperture","md-apps","md-appstore","md-archive","md-arrow-back","md-arrow-down","md-arrow-dropdown","md-arrow-dropdown-circle","md-arrow-dropleft","md-arrow-dropleft-circle","md-arrow-dropright","md-arrow-dropright-circle","md-arrow-dropup","md-arrow-dropup-circle","md-arrow-forward","md-arrow-round-back","md-arrow-round-down","md-arrow-round-forward","md-arrow-round-up","md-arrow-up","md-at","md-attach","md-backspace","md-barcode","md-baseball","md-basket","md-basketball","md-battery-charging","md-battery-dead","md-battery-full","md-beaker","md-beer","md-bicycle","md-bluetooth","md-boat","md-body","md-bonfire","md-book","md-bookmark","md-bookmarks","md-bowtie","md-briefcase","md-browsers","md-brush","md-bug","md-build","md-bulb","md-bus","md-cafe","md-calculator","md-calendar","md-call","md-camera","md-car","md-card","md-cart","md-cash","md-chatboxes","md-chatbubbles","md-checkbox","md-checkbox-outline","md-checkmark","md-checkmark-circle","md-checkmark-circle-outline","md-clipboard","md-clock","md-close","md-close-circle","md-closed-captioning","md-cloud","md-cloud-circle","md-cloud-done","md-cloud-download","md-cloud-outline","md-cloud-upload","md-cloudy","md-cloudy-night","md-code","md-code-download","md-code-working","md-cog","md-color-fill","md-color-filter","md-color-palette","md-color-wand","md-compass","md-construct","md-contact","md-contacts","md-contract","md-contrast","md-copy","md-create","md-crop","md-cube","md-cut","md-desktop","md-disc","md-document","md-done-all","md-download","md-easel","md-egg","md-exit","md-expand","md-eye","md-eye-off","md-fastforward","md-female","md-filing","md-film","md-finger-print","md-flag","md-flame","md-flash","md-flask","md-flower","md-folder","md-folder-open","md-football","md-funnel","md-game-controller-a","md-game-controller-b","md-git-branch","md-git-commit","md-git-compare","md-git-merge","md-git-network","md-git-pull-request","md-glasses","md-globe","md-grid","md-hammer","md-hand","md-happy","md-headset","md-heart","md-heart-outline","md-help","md-help-buoy","md-help-circle","md-home","md-ice-cream","md-image","md-images","md-infinite","md-information","md-information-circle","md-ionic","md-ionitron","md-jet","md-key","md-keypad","md-laptop","md-leaf","md-link","md-list","md-list-box","md-locate","md-lock","md-log-in","md-log-out","md-magnet","md-mail","md-mail-open","md-male","md-man","md-map","md-medal","md-medical","md-medkit","md-megaphone","md-menu","md-mic","md-mic-off","md-microphone","md-moon","md-more","md-move","md-musical-note","md-musical-notes","md-navigate","md-no-smoking","md-notifications","md-notifications-off","md-notifications-outline","md-nuclear","md-nutrition","md-open","md-options","md-outlet","md-paper","md-paper-plane","md-partly-sunny","md-pause","md-paw","md-people","md-person","md-person-add","md-phone-landscape","md-phone-portrait","md-photos","md-pie","md-pin","md-pint","md-pizza","md-plane","md-planet","md-play","md-podium","md-power","md-pricetag","md-pricetags","md-print","md-pulse","md-qr-scanner","md-quote","md-radio","md-radio-button-off","md-radio-button-on","md-rainy","md-recording","md-redo","md-refresh","md-refresh-circle","md-remove","md-remove-circle","md-reorder","md-repeat","md-resize","md-restaurant","md-return-left","md-return-right","md-reverse-camera","md-rewind","md-ribbon","md-rose","md-sad","md-school","md-search","md-send","md-settings","md-share","md-share-alt","md-shirt","md-shuffle","md-skip-backward","md-skip-forward","md-snow","md-speedometer","md-square","md-square-outline","md-star","md-star-half","md-star-outline","md-stats","md-stopwatch","md-subway","md-sunny","md-swap","md-switch","md-sync","md-tablet-landscape","md-tablet-portrait","md-tennisball","md-text","md-thermometer","md-thumbs-down","md-thumbs-up","md-thunderstorm","md-time","md-timer","md-train","md-transgender","md-trash","md-trending-down","md-trending-up","md-trophy","md-umbrella","md-undo","md-unlock","md-videocam","md-volume-down","md-volume-mute","md-volume-off","md-volume-up","md-walk","md-warning","md-watch","md-water","md-wifi","md-wine","md-woman"].

@amanthegreatone Please check #389 for you use case. Also the README has been updated for <Icon /> configuration.

This way it work for me !
.
Set type attribute depend on Bundled Icon Sets(list below)
Example
.
Bundled Icon Sets
Entypo
EvilIcons
Feather
FontAwesome
Foundation
Ionicons
MaterialIcons
MaterialCommunityIcons
Octicons
Zocial
SimpleLineIcons
.
Nativebase use: react-native-vector-icons
See full docs here: https://github.com/oblador/react-native-vector-icons

@waritthornnudee thank you. Saved me so much time.


Get tool ids for all tools in a suite

Add tool ids to the list,
allows matching with galaxy instance.
Not tested yet, need better wifi in train.

Thanks @paulzierep


Apply the optimizer automatically

Closes issue #170
Allows you to control what optimizer (if any) is used when executing a pipeline, defaulting to the current Optimizer object
@etrain

This looks pretty reasonable to me. You went the "reoptimize every time" route which is probably OK for now but something we'll need to keep on our radar for the future.
Have you tested locally and verified that the examples run?

Yeah, if you don't want to reoptimize every time you can manually optimize and then apply the pipeline using no optimizer. And yes I've tested this locally.


Replace tests that evaluate stdout output

Some of the integration tests evaluate that certain words are present in the stdout output, which can break or change with updates to the logging verbosity. The following tests specifically do this:
integration/update/empty-deps
integration/update/github-leaf
integration/fetch/empty-deps
integration/fetch/local-direct
integration/fetch/mutually-recursive
integration/fetch/self-referential
integration/fetch/local-git
integration/fetch/github-deep
integration/fetch/remote-gits
integration/help
integration/info
integration/run
integration/run/without-bundle
integration/version

See #137 for more information.
@SeanTAllen would you like for these checks to just be removed from all of these tests? In help / info / version we would essentially just be testing exit 0.

I'd like to replace the tests that are using output to determine if an action happened with creating tests that use test-doubles to verify the correction interactions like for example, these that I recently wrote:
https://github.com/ponylang/corral/pull/132/files
https://github.com/ponylang/corral/pull/134/files

Did some work on this today, learned a bunch from this commit (https://github.com/ponylang/corral/commit/7f00b2ba4fd20fdf56b305f616967654b4f821e5). Hoping to have some updates landing soon :+1:

@hasheddan are you interested in working on this? if yes, i can add you as a "contributor" to the ponylang org which basically allows you to be assigned to issues and not much else, then I can assign you to this.

@SeanTAllen Definitely! Thanks :+1:

ok @hasheddan once you accept the invite, you should be able to assign yourself as you will have "triage" level access to all the organization repos.


error code 503 on sending the message

This was spotted on Xabber client, when two buddies communicate. From certain point only one of them is able to send the messages , the other one is getting error and cannot send any more message. Subscription is both,both in the DB.
error-503-red-cross.txt
Still cannot reproduce what possibly could cause this issue.

Ok. According to the log file seems pretty clear that messages are being sent to an already disconnected stream. Is there any way I can reproduce this very same issue? Also, maybe this has something to do with the recently added 'resource conflict' policy feature. Playing with different values changes this behavior? Thanks in advance!

I have tried changing the 'resource conflict' even before I have submit this issue. It has no effect on it.
This one is tough to reproduce, I do not even know how does it happen. Suddenly my friend and I were connected via mobile data with Xabber and it happens right there.

Mmmmmm, may this happen while one of you has the Xabber application in background???

@ortuman well we both have Xabber in the background most of the time, so it is very possible

and do you see any previous disconection in the logs?

I have found this
[DBG] stream:838 - SEND: <failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><malformed-request/></failure>
attaching full log:
full-503-error.txt

very useful! thanks!
I see why these messages are being resent as error
<message<EMAIL_ADDRESS>id="wf3GR-1872" type="chat"><body>still-cannot-deliver</body><thread>lA2BJhSAmwCX</thread><active xmlns="http://jabber.org/protocol/chatstates"/><request xmlns="urn:xmpp:receipts"/></message>
notice that resource is in lowercase, though previously the stream was authenticated like Xabber_DNdsar61

Else if the JID is of the form <user@domain/resource> and no available resource matches the full JID, the recipient's server (a) SHOULD silently ignore the stanza (i.e., neither deliver it nor return an error) if it is a presence stanza, (b) MUST return a <service-unavailable/> stanza error to the sender if it is an IQ stanza, and (c) SHOULD treat the stanza as if it were addressed to <user@domain> if it is a message stanza.
so in case the JID doesn't match any active resource, the message SHOULD be delivered to all available resources... :)
I fix it asap!
(BTW, later I'll tackel the malformed-request issue)
Thanks for the report!!!

Fixed on 0.1.9 release


fix: unminified build breaks __vitePreload

Description
close #5753

When there are comments in dynamic import, e.g.
import(/*not following dependency*/'./App.vue')

We will get url =  /*not following dependency*/ "./App.vue" ,  which does not meet the conditions:
if (url[0] === `"` && url[url.length - 1] === `"`) {

In fact es-module-lexer will return a .n field containing the escaped url,  which is ./App.vue in this example.
So we can use the .n field first.
Additional context
https://github.com/guybedford/es-module-lexer/blob/c5cdb28d848c91e9296bbcf9a17196f230f68a5f/types/lexer.d.ts#L2-L22
 /**
   * Module name
   *
   * To handle escape sequences in specifier strings, the .n field of imported specifiers will be provided where possible.
   *
   * For dynamic import expressions, this field will be empty if not a valid JS string.
   *
   * @example
   * const [imports1, exports1] = parse(String.raw`import './\u0061\u0062.js'`);
   * imports1[0].n;
   * // Returns "./ab.js"
   *
   * const [imports2, exports2] = parse(`import("./ab.js")`);
   * imports2[0].n;
   * // Returns "./ab.js"
   *
   * const [imports3, exports3] = parse(`import("./" + "ab.js")`);
   * imports3[0].n;
   * // Returns undefined
   */
  readonly n: string | undefined;

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

I love your PRs @ygj6 ❤

I love your PRs @ygj6 ❤

⬆  What @patak-js says ❤


[Kernel] Compilation error of conv3x3.s

I am using develop of miopen, the command line as follows:
MIOpenDriver conv -n 2 -c 64 -H 192 -W 288 -k 128 -y 3 -x 3 -p 1 -q 1 -u 1 -v 1 -l 1 -j 1 -m conv -g 2 -F 1 -t 1 -V 0

Then I get errors list in the picture:

The following lines in conv3x3.s seems to cause the error.

Then I modify the file, the error is eliminated:

@Slimakanzer @Kirpich30000 Please review this, thanks.


mDNS response is not sent out over STM32U575zi-WiFi

Discussed in https://github.com/zephyrproject-rtos/zephyr/discussions/71540

Originally posted by VineetaNarkhede-eaton April 16, 2024
Hi,
I am facing an issue in running mDNS over STM32U575zi on WiFi interface. Device (Dev board) is in AP mode and connected with Laptop over WiFi. Enabled the mDNS responder in zephyr. Hostname configured is "zephyr"
When I send mdns query from Laptop i.e zephyr.local, the query is successfully reaching the device from the laptop. However, the response from the device does not appear to be reaching the laptop. I have verified that the response is reaching till WiFi driver and the response data is valid. Wireshark logs on the laptop shows query but no response visible. Interestingly, mDNS query-response works sometimes suddenly(very rare) without any code changes.
I tried the solution provided on this issue https://github.com/zephyrproject-rtos/zephyr/discussions/48327, but no improvement in the result.
Setup:
Dev board: NUCLEO-U575ZI-Q
WiFi chip:1YN-CY43439
zephyr OS : v3.2.0
infineon_zephyr_connectivity commit id : 272e2b8da908c7d796ec62757cc8abbe03a91e4c
I would appreciate any help with this matter.

I was hoping a proper issue instead of pressing the "convert to issue" button as this just copies the first question to an issue. Lot of relevant information missing now.
Anyway, lets start by first figuring out what wifi driver are you using, mentioning chip does not really help here.

Can we replace NET_IF_LOWER_UP with NET_IF_UP in net_if_tx() function to solve this issue?

No, you should not do that. NET_IF_UP presents admin state of the interface i.e., it is set when the application or user turns on the interface. The NET_IF_LOWER_UP is set when the carrier is turned on. For wifi this means that when the wifi connection is "ready". So it looks like the wifi interface carrier status is turned "ON" too early by the driver when the interface in fact is not yet ready for the connection.

Can we replace NET_IF_LOWER_UP with NET_IF_UP in net_if_tx() function to solve this issue?

No, you should not do that. NET_IF_UP presents admin state of the interface i.e., it is set when the application or user turns on the interface. The NET_IF_LOWER_UP is set when the carrier is turned on. For wifi this means that when the wifi connection is "ready". So it looks like the wifi interface carrier status is turned "ON" too early by the driver when the interface in fact is not yet ready for the connection.

Hello @jukkar,
We have noticed one change in NET_IF_INIT() macro which is getting called by NET_DEVICE_DT_INST_DEFINE() macro. It is setting flag bit for NET_IF_LOWER_UP as highlighted in following image:

This sets the flag as carrier ON. As mentioned earlier we are initializing WiFi in application and not before main. So carrier must be turned on only after Network Link is Up and Valid IP is assigned. Since carrier flag is set before wireless network is setup, so iface will not have Valid IP address. When mDNS is initialized from init_listener() using SYS_INIT() so it finds iface src address as null and gives bus fault.
What is the significance of setting flag to NET_IF_LOWER_UP in NET_IF_INIT()? Found one commit where this change was done. Link is here.

cc: @VineetaNarkhede-eaton

@jukkar ,
We are waiting for your response.
Above issue can be resolved if we change NET_IF_LOWER_UP flag to NET_IF_NO_AUTO_START.

You have out of tree driver and application, it very difficult to understand what your code is doing.
cc: @rlubos if you have any extra ideas

This sets the flag as carrier ON. As mentioned earlier we are initializing WiFi in application and not before main. So carrier must be turned on only after Network Link is Up and Valid IP is assigned.

The carrier is set to ON by default, for legacy reasons (and we don't push to change it as Linux does the same). If the particular interface is not ready to use after system initialization, it should be changed to off.
Every network interface has possibility to run boot-time initialization by registering init() function from struct net_if_api (the API struct is statically provided when registering interface with NET_DEVICE_DT_INST_DEFINE() or similar). You should set carrier to OFF there.
You can take ESP driver as a reference here, it seems to be a similar case:
https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/wifi/esp32/src/esp_wifi_drv.c#L681

You can take ESP driver as a reference here, it seems to be a similar case:
https://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/wifi/esp32/src/esp_wifi_drv.c#L681

Hello @rlubos,
Thanks for the reference, we have tried it and it seems Bus Fault issue is resolved. Will add an update here once testing is completed.
cc: @VineetaNarkhede-eaton

Closing since it seems resolved. Please reopen if this is not the case.


[FEATURE] - use bat pager instead of moins

see https://github.com/dandavison/delta

I'd take a look into this one as well 😊


Fix oversights from 735f2d9

Description
Bug found by Kimci86 here.
I recently learned about MSVC's C4365 warning which unlike -Wconversion or -Wsign-conversion in GCC and Clang can actually detect instances of assigning a signed integer to an unsigned integer optional. This won't help with DRM code which of course does compile with MSVC but may catch this same issue elsewhere in the codebase.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.213%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/SFML/Window/DRM/InputImpl.cpp
0
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
11664

Relevant Lines:
19693

💛  - Coveralls


[Feature request] Enable notifications without wrist overlay/general overlay

Hello!
I would like to be able to enable notifications on the desktop without having to enable the overlay on SteamVR (completely disable all overlays).
But also that it's possible to enable desktop notifications and/or VR notifications without having the overlay on the wrist (or that it's possible to disable this overlay).
Thank you!
Lupsoris

Hello there, it's not possible to disable the wrist overlay and have desktop notifications at the same time with this current version, it should be possible in the future but will require moving a lot of code around.

Hello there, it's not possible to disable the wrist overlay and have desktop notifications at the same time with this current version, it should be possible in the future but will require moving a lot of code around.

I would like to see this fixed as well. Hoping to see it in the future!

I would like to see this fixed as well. Hoping to see it in the future!

I hope it will be possible, yes! Because I really like the idea of having desktop notifications (as a priority), but also having them in VR. But I don't use the wrist overlay, and I even find it rather annoying because it's activated with "keys" that I use often, it's rather big ^^`

I hope it will be possible, yes! Because I really like the idea of having desktop notifications (as a priority), but also having them in VR. But I don't use the wrist overlay, and I even find it rather annoying because it's activated with "keys" that I use often, it's rather big ^^`


adds isAbsolute

this pr adds isAbsolute to ensure that globs are absolute. (TODO: I haven't had a chance to get appveyor running, will do that next along with windows tests. I just wanted to push this up to start discussing).
slashes
I spent quite a bit of time exploring different approaches to normalizing slashes, but I arrived at the conclusion that it's not a good idea - probably for the same reasons that node-glob disallows backslashes as path separators in globs.
escaping
Since most glob characters are perfectly valid path characters when used in normal file paths, there are too many scenarios where backslashes would indicate escaping, and not path separators.
If we muddy the waters on this, we will never be 100% correct, and users won't have a surefire way to tell us that they're escaping a character.
On that same point, I believe the main place where it really matters is if a path has a leading slash (since we need to know if it's absolute or not). But in windows, an absolute path shouldn't being with a slash or backslash, it would begin with a drive letter. Hopefully this check resolves any issues you were having regarding absolute paths with windows.
(also, fwiw in node-glob, most of the usage of makeAbs is on actual file paths I believe. I only saw one place where it seems to be used on globs. IMHO - if there is no good reason to do that in glob-stream, I'd leave it to node-glob)
cc @phated

Sounds good, yea. Looks great, if i remember, i'm using this lib in few places.
I've done something similar here https://github.com/tunnckoCore/unrelative (the "temp", haha), but with normalize-path and in bonus resolve-dir to handle ~ and @ which would be cool in patterns too.
Or lookup at GitHub releases v1 from march previous year, or http://npm.im/unrelative readme.

The code for isAbsolute looks fine but I'd like you to elaborate on your slashes section.  Are you saying you don't want to replace the \\ with / in paths generated by path.* methods?  I'm also pretty confused on the escaping section.

K, I pushed up suggested changes. I think this will resolve what you're getting at. It's not how node-glob does it, but I believe this makes more sense for what I understand the problem to be (this ensures / in non-glob parts of the path. if we follow node-glob and bash conventions, glob patterns themselves should never have backslashes defined as path separators, since \\ is reserved for escaping)
let me know if this works for you. I don't mind exploring other options.

@jonschlinkert any word on if you are going to ship this PR?  I'm currently trying to get path normalization wrapped up in glob-stream and was just looking at the base path stuff where this is used.

any word on if you are going to ship this PR?

I was just waiting on your feedback. If you're good with it, I'll ship it

@jonschlinkert going to test the branch in glob-stream and I'll follow up.  I like what I've seen in reviewing the code but want to test actual usage.

@jonschlinkert this is working great; however, I did encounter the tangential issue at https://github.com/es128/glob-parent/issues/8

Added a couple of inline questions here.

@jonschlinkert you can see some Windows failures with my usage at https://ci.appveyor.com/project/gulpjs/glob-stream/build/1.0.48

you can see some Windows failures with my usage at

awesome that will be really helpful. thanks

Thank you both so much!

you are of course very welcome, and thank you as well. it was a very much team effort @phated, yourself included!


the server is currently unable to handle the request

What happened:
I set up a kubemark cluster. Like this:
root@vm1:~# kubectl get node
NAME                STATUS   ROLES                  AGE     VERSION
hollow-node-4pp62   Ready    <none>                 3d21h   v1.23.0-alpha.0.510+fe099b2abdb023-dirty
hollow-node-7nfz7   Ready    <none>                 3d21h   v1.23.0-alpha.0.510+fe099b2abdb023-dirty
hollow-node-8d4b8   Ready    <none>                 3d21h   v1.23.0-alpha.0.510+fe099b2abdb023-dirty
hollow-node-dllwb   Ready    <none>                 3d21h   v1.23.0-alpha.0.510+fe099b2abdb023-dirty
hollow-node-wgg5b   Ready    <none>                 3d21h   v1.23.0-alpha.0.510+fe099b2abdb023-dirty
vm1                 Ready    control-plane,master   3d21h   v1.21.1

root@vm1:~# kubectl get po -A
NAMESPACE     NAME                          READY   STATUS    RESTARTS   AGE
kube-system   etcd-vm1                      1/1     Running   0          3d21h
kube-system   kube-apiserver-vm1            1/1     Running   0          3d21h
kube-system   kube-controller-manager-vm1   1/1     Running   0          3d21h
kube-system   kube-proxy-crnrz              1/1     Running   0          3d21h
kube-system   kube-proxy-gkbgm              1/1     Running   0          3d21h
kube-system   kube-proxy-jqbcw              1/1     Running   0          3d21h
kube-system   kube-proxy-lb6v5              1/1     Running   0          3d21h
kube-system   kube-proxy-qnj9k              1/1     Running   0          3d21h
kube-system   kube-proxy-xxr9v              1/1     Running   0          3d21h
kube-system   kube-scheduler-vm1            1/1     Running   0          3d21h

I run this density test:
root@vm1:~/go/src/k8s.io/perf-tests/clusterloader2# go run cmd/clusterloader.go --testconfig=testing/density/config.yaml --provider=kubemark --kubeconfig=/root/.kube/config --v=2 --report-dir=/root/report

It runs into this error:
E0913 05:51:55.078990 2677429 clusterloader.go:227] --------------------------------------------------------------------------------
E0913 05:51:55.079096 2677429 clusterloader.go:228] Test Finished
E0913 05:51:55.079105 2677429 clusterloader.go:229]   Test: testing/density/config.yaml
E0913 05:51:55.079121 2677429 clusterloader.go:230]   Status: Fail
E0913 05:51:55.079126 2677429 clusterloader.go:232]   Errors: [measurement call TestMetrics - TestMetrics error: [action start failed for SchedulingMetrics measurement: the server is currently unable to handle the request (get pods https:kube-scheduler-vm1:10259)]
measurement call TestMetrics - TestMetrics error: [action gather failed for SchedulingMetrics measurement: the server is currently unable to handle the request (get pods https:kube-scheduler-vm1:10259)]]
E0913 05:51:55.079133 2677429 clusterloader.go:234] --------------------------------------------------------------------------------

What you expected to happen:
I hope it can get SchedulingMetrics normally. How did it happen?

/area clusterloader

I met the same problem with you, may I ask you now have you been solved.

met the same problem

@Azipro @zushaohua have you been solved the promblem?

No....

@Azipro @zushaohua have you been solved the promblem?

No....


Question about different results when trying to reproduce

Thank you for sharing your work, your paper was very interesting and the results are also very impressive!
I had a question regarding the evaluation on MSLS-val. I attempted to reproduce your results by following the repository, downloading the data, and training the model as described in the README. Initially, I trained the model solely on the MSLS dataset. I attempted to evaluate the results on MSLS by executing the following command for both my trained model and the provided trained model:
python3 eval.py --datasets_folder=/path/to/your/datasets_vg/datasets --dataset_name=msls --resume=/path/to/finetuned/msls/model/SelaVPR_msls.pth --rerank_num=100

However, these were the results that I obtained:

Model
R@1
R@5
R@10

Claimed performance in README
90.8
96.4
97.2

Self-trained model
87.0
94.0
95.6

Downloaded model
86.6
93.8
95.6

Further fine-tuning the model on Pitts30k and evaluating it gave the same results as you had in your README for evaluation on Pitts30k. Therefore, I'm wondering if you could help me understand why there's a difference for the MSLS-val. Am I evaluating with the wrong data, or is there something else I might be missing?

Hello, thanks for your interest in our work.  I guess you used this repository (https://github.com/gmberton/VPR-datasets-downloader) to format the MSLS dataset and used all query images (about 11k) in MSLS-val for testing. However, the official version of MSLS val (https://github.com/mapillary/mapillary_sls) only contains 740 query images (i.e. a subset). The vast majority of VPR works use the official version of MSLS-val for testing. You can get these 740 query images through the official repository, or get the key (name) of these images here.

Hello, thanks for your interest in our work. I guess you used this repository (https://github.com/gmberton/VPR-datasets-downloader) to format the MSLS dataset and used all query images (about 11k) in MSLS-val for testing. However, the official version of MSLS val (https://github.com/mapillary/mapillary_sls) only contains 740 query images (i.e. a subset). The vast majority of VPR works use the official version of MSLS-val for testing. You can get these 740 query images through the official repository, or get the key (name) of these images here.

The keys (names) of official MSLS-val images aren't follow the form "path/to/file/@utm_easting@utm_northing<EMAIL_ADDRESS>which is used in the code. Could you kindly give the names like "path/to/file/@utm_easting@utm_northing<EMAIL_ADDRESS>

Hello, thanks for your interest in our work. I guess you used this repository (https://github.com/gmberton/VPR-datasets-downloader) to format the MSLS dataset and used all query images (about 11k) in MSLS-val for testing. However, the official version of MSLS val (https://github.com/mapillary/mapillary_sls) only contains 740 query images (i.e. a subset). The vast majority of VPR works use the official version of MSLS-val for testing. You can get these 740 query images through the official repository, or get the key (name) of these images here.

The keys (names) of official MSLS-val images aren't follow the form "path/to/file/@utm_easting@utm_northing<EMAIL_ADDRESS>which is used in the code. Could you kindly give the names like "path/to/file/@utm_easting@utm_northing<EMAIL_ADDRESS>
@HUSTNO1WXY Hello, you can directly run the code in VPR-datasets-downloader to format the image name.


Please explain how to get normal text output

When I try to read data, I receive abnormal text decoded. I tried many encoding but result is same.

The problem was in the cp2102


HBASE-26919 Rewrite the counting rows part in TestFromClientSide4

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 13s
Docker mode activated.


Hugo: Add optionality to search for authors

Add authors to algolia search results
Add author search optionality to ts
Extend algolia settings > 'searchableAttributes' and 'attributesForFaceting' with authors

For testing:

set up a testing index in Algolia > follow walkthrough in hugo > readme
change the environments to your test index in the search-results.ts
run the project and eg go to /blog/example/ and click on an author

search all content by this author

-> you are redirected to the search results page with the author query, and will see all the pages by this author.
For example: /search/?q=author:pauljolly
For https://linear.app/usmedia/issue/CUE-266

Closed via ff5f268586d08cea60022124776e10cf179e2b29


Upload to PyPI

Hello,
I really like this project but could you please push it on pypi? it would help installation on our part.
Thanks

Hey! I just tried to pip install this. :-) It doesn't have to be perfect to upload to pypi.

@jackiekazil Thanks for the nudge :)
mplleaflet is now on PyPI! Thanks.

:+1:


License

Hi, this dataset looks very interesting. Could you please add a license to the code and annotations, such that it can actually be used? Ideally both in the github and on the website.

Added in 948224688f685148e6fe9f7710a8fd91fffe2c8d thank you, closing.


Protect master branch

Maybe you have already enabled, this, but it would put my mind at ease on the terminal if the master branch was protected: https://help.github.com/articles/configuring-protected-branches/

Agree, thanks for the pointer. I enabled protection.


Very bad performance in insert mode

Hi,
First of, thanks for this great plugin! It's so much more straight forward compared to other solutions.
Unfortunately, I've noticed some quite bad performance problems in insert mode with NCM. Here's what this looks like when I'm pressing and holding the DEL key. I experience the frequent stops and delays when typing as well.

I've tried increasing the g:cm_complete_delay setting. It seems to have helped somewhat, but not really. Setting g:cm_auto_popup to 0 mostly helps fixing these performance issues. But I get the feeling that some completion source is just really bad.

Thanks a lot! Would really love to keep using NCM!

OK, just to try what that would do, I deleted ultisnips. Performance is great now. Any recommendations how to fix ultisnips performance? Or should I just switch to a different snippet manager?

NCM get ultisnips candidates by sync API call, which is kind of heavyweight.
You don't need to delete ultisnips, though, use this to disable the built-in ultisnips source.
let g:cm_sources_override = {
    \ 'cm-ultisnips': {'enable':0}
    \ }

Future work (maybe):

Considering ultisnips candidates are not changing for the same buffer, I will try improving the caching feature of NCM. By then, you don't need to disable ultisnips to use NCM.
g:cm_complete_delay does not supress candidate calculation. Maybe we need to change  the behavior, or add another config for this.

Awesome! Thanks.

A new option  g:cm_complete_start_delay is added. Set it to non-zero value when you have to deal with slow, sync completion source.
see #119

Sweet. Thanks. Now that I know I can disable UltiSnips, I think I prefer having a quickly showing menu without ultisnips.


Update GeoServer versions for CI testing

This updates the GeoServer versions for tests in CI (2.19.2 and 2.18.4).

Right, would be a good thing to automate this. I created an issue (#35).
Thanks for the review, I'll merge now.


MdDialog opens additional dialogs when enter or space key is pressed during opening transition

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The initial dialog being opened should close returning the user to the state before dialog open was triggered
What is the current behavior?
After each press of either enter or spacebar a new dialog is opened on top of the initial dialog. The users is then required to close all these windows
What are the steps to reproduce?
Create an event causing an mddialog to open then immediately press enter or space key multiples times until this opening transition is finished.
This behaviour can be viewed in the current example page https://material.angular.io/components/dialog/examples
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
angular: 4.3.3, material: 2.0.0-beta.8, typescript: 2.4.2, browsers checked firefox 54.0.1 (64-bit) and chrome 60.0.3112.78 (Official Build) (64-bit)
Is there anything else we should know?

Should be sorted one by https://github.com/angular/material2/pull/5769 in the next release.


Env directory is ignored in .gitignore

Hey, I don't know if this is supposed to be a public thing but it seems like according to your README.md, you want people to be able to check out your project. In which case, I'd like to point out that your ./env directory is ignored in .gitignore so nothing inside it is uploaded to GitHub... that includes the UnityEnvironment executable that you mention multiple times in your setup/installation documentation, so basically there isn't any executable.

Hello, this is normal yes, as we support several platforms we let users download the correct version for either linux, mac or windows.
Have a look at the requirements in the readme, it contains links to these three executables.


Create an SBOM from Gemfile.lock

In order to allow chelsea to ultimately work with Nexus IQ Server, we would need to output an SBOM that we can send to the Nexus IQ Third Party API.
Steps in this work are largely to see if we could use this library:
https://github.com/CycloneDX/cyclonedx-ruby-gem
If we can't, then we can take what we need and craft our own, but we should definitely take a look at this lib first.
From there, we'd want likely a new method off of deps.rb to "craftSBOM` or something akin, that would give us the XML to send to IQ Server.

This is done.


Prisma thinks "did:ethr:0xe378374c8A932Ba42f81C3c8AACB43D96F6c5824" is a JSON and refuses to use it as string

Bug description
Error:
  of:gql Invalid `prismaClient.users.findUnique()` invocation in
  of:gql /home/capaj/work-repos/official/official-graphql/graphql/src/models/api/NotificationModel.ts:47:29
  of:gql
  of:gql   44 }
  of:gql   45
  of:gql   46 const getUserPicture = (userId: string) => {
  of:gql → 47   return prismaClient.users.findUnique({
  of:gql          where: {
  of:gql            aws_user_id: {
  of:gql              aws_user_id: 'did:ethr:0xe378374c8A932Ba42f81C3c8AACB43D96F6c5824'
  of:gql            }
  of:gql            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  of:gql          },
  of:gql          select: {
  of:gql            picture: true
  of:gql          }
  of:gql        })
  of:gql
  of:gql Argument aws_user_id: Got invalid value
  of:gql {
  of:gql   aws_user_id: 'did:ethr:0xe378374c8A932Ba42f81C3c8AACB43D96F6c5824'
  of:gql }
  of:gql on prisma.findUniqueusers. Provided Json, expected String.
  of:gql
  of:gql
  of:gql     at Document.validate (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:27181:20)
  of:gql     at PrismaClient._executeRequest (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29694:17)
  of:gql     at middleware (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29603:60)
  of:gql     at consumer (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29618:24)
  of:gql     at /home/capaj/work-repos/official/official-graphql/graphql/node_modules/@sentry/tracing/cjs/integrations/node/prisma.js:65:16
  of:gql     at middleware (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29600:55)
  of:gql     at consumer (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29618:24)
  of:gql     at /home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29622:135
  of:gql     at AsyncResource.runInAsyncScope (node:async_hooks:203:9)
  of:gql     at callback (/home/capaj/work-repos/official/official-graphql/graphql/node_modules/@prisma/client/runtime/index.js:29622:113) +3ms

How to reproduce
I have schema like this:
model users {
  aws_user_id                                               String                         @id @unique(map: "users_aws_user_id_unique") @db.VarChar(255)
    picture                                                   String?                        @db.VarChar(255)
}

and running:
prismaClient.users.findUnique({
      where: {
        aws_user_id: "did:ethr:0xe378374c8A932Ba42f81C3c8AACB43D96F6c5824"
      },
      select: {
        picture: true
      }
    })

Gives me the error I have in the bug description.
Expected behavior
you can use json as string. JSON is a string. Why is prisma even checking whether a string is a json?
Prisma information
model users {
  aws_user_id                                               String                         @id @unique(map: "users_aws_user_id_unique") @db.VarChar(255)
    picture                                                   String?                        @db.VarChar(255)
}

Environment & setup

OS: ubuntu
Database: PG
Node.js version: 18.6.0

Prisma Version
prisma                  : 4.1.0
@prisma/client          : 4.1.0
Current platform        : debian-openssl-3.0.x
Query Engine (Node-API) : libquery-engine 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 8d8414deb360336e4698a65aa45a1fbaf1ce13d8 (at<EMAIL_ADDRESS>Default Engines Hash    : 8d8414deb360336e4698a65aa45a1fbaf1ce13d8
Studio                  : 0.467.0

actually I retested this and it seems to work fine, will try to find out more about the previous case and I may reopen if I find out why it is failing


Problem in reception of some stations

During reception of a station which was connecting with many other stations. My K5 radio was receving comunitions with cuts even  signals were strong. With monitor on there were no cuts. I m testing again and again. This isue is with few stations. My Kenwood has no any isue like that .  I have tried old FWs but isue was present even  in stock FW.
Now I m testing on other stations, even on strongest signal the RSS bar is also fluctuating. This is happening with particular stations.

Need to see and hear a short video of it happening, ignore the RSSI bar for now, that's purely cosmetic.

How can I post video?

https://github.com/OneOfEleven/uv-k5-firmware-custom/assets/149041689/792c7448-fa89-4a28-b462-15d6c2de12bf

Above video is with squel on- squelch off- squelch on.

ah, set the channel to WIDE mode, the signal looks to be too wide for narrow mode (you have that channel set to NARROW mode).
Let me know how it goes.

I m so 😜


Update OBSStudio.json to match with new download URL

Update OBSStudio.json to match with new download URL https://cdn-fastly.obsproject.com/downloads/OBS-Studio-30.2.3-Windows-Installer.exe. The current old URL is https://cdn-fastly.obsproject.com/downloads/OBS-Studio-30.2.3-Full-Installer-x64.exe which is not valid now.

It fixes bug #733


Internal SMTP relay

Is it possible to relay from one postal mail server with some verified domains to another one by condition? In other words is it possible to configure outgoing routes?

You can add a smarthost as per #251 but this is for all email.

Yes, I have seen this, but the idea is to route messages inside postal.

The outgoing message from postal will always use the MX for the domain. All message scan go to a remote host in the config but there isn't anyway to selectively do this as far as I can see.
Incoming messages to postal can go to any other SMTP host but probably not want you want.

Well I think this idea can be an enhancement of some kind. For example if you wish to send letters from subdomains and make special route for these messages.

Hello, and thanks for the awesome piece of software.
Is it possible to use Postal as a mail-relay only host without mailboxes ?
Thanks in advance.
Rod

Postal doesn't whitelist (or blacklist for that matter), it only blocks sending if it is unsure whether the email will be delivered.


Fixes an error in redis

In some scenarios redis will send without a callback, and prior to this change that would result in attempting to access a property on undefined.

@MSLaguana,
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

Hmm, perhaps in this scenario we should attach a callback even if one was not initially provided, so we can report the redis invocation? E.g. if (!cb || !cb.pubsubBound) instead.

perhaps in this scenario we should attach a callback even if one was not initially provided, so we can report the redis invocation? E.g. if (!cb || !cb.pubsubBound) instead.

Agree w/ this.  Also would be good to see a test added to cover this scenario.  How hard is that?

Changed to add a callback if one was not provided, and added a new test for that scenario.


Whitelist for postbuild verification

The PostBuildLint process checks for export of dlls which in some port cases are counter-productive (e.g. osg). The plugin libraries actually do not export any symbols, so this post-verification fails and makes the build fail.
Currently, the port file moves the affected libraries out of the bin folder which is some kind of workaround. A better solution would be to skip the verification for these libraries on a port basis. Are there any ways I have not seen yet that enable that approach?
Otherwise I would propose to add a whitelist that takes a list of library names that should be skipped in the verification process (especially check_exports_of_dlls).

It's by design. You can move them to tools/plugins or share/${PORT}/plugins.


Improve dx around type checking/autocomplete of objectType etc.

Originally raised here https://github.com/prisma-labs/nexus/issues/77#issuecomment-478286731.
Possible Problems

name needs to be given before being able to work on definition with backing types active. This is not encoded by the API.

Asymmetrical API between object and field level
objectType({ name: "foo", ... })
t.field("foo", { ... })

Solution
Allow user to pass name as first argument to function.

Forces user to supply name before attempting work on definition block, required anyways.

Harmonizes API across type and fields
objectType("foo", { ... })
t.field("foo", { ... })

Notes
Assuming we think this is a good API, I think we might want to see it as an addition, meaning we preserve the object style API too. Then, would also propose that t.field grow to accept object style too e.g. t.field({ name: 'foo', ... }). Full symmetry, backwards compatible. One con I can imagine is that autocomplete becomes potentially less ergonomic. But actually it seems alright:

We may want to preserve object passing to support machines (easier for them to build up and pass objects).

Can you give an example of what this looks like?
My only comment here is that there's a lot of history/thought put into why the API is the way it is, so before we try to make any changes, it'd be worth confirming that it will in-fact work well with the limitations of TypeScripts' type-system, generics, etc. But I definitely agree there's a lot of room for improvements to be made.

@tgriesser Just that we preserve the current API too. Issue description revised for clarity.

I'm always wary of overloading APIs unnecessarily.

@Weakky was too I think. I'll let him speak for himself 😄 but wanted to mention he had an observation that, if one overload is intended for machines, then simply expose it somehow differently.
Of all dx issues its probably safe to say this one is not top 5 or even 10. But it was real feedback we got and I personally find it burdensome to go between the different name passing styles. So I captured an issue to formalize it.

This change is welcoming! Sometimes I do have to wonder where I should declare the name.

honestly think it may have been due to the way Prettier formats w/ longer type names

@tgriesser I remember we spent a while discussing that part of the API but I couldn't remember why we went for the current one. I remember the prettier issue now, and even though I'm sure there were more, it's already enough for me to discard the proposal again.
I see @Ericnr likes it, let's keep it open for a while and see if more people find it better

Yeah this sucks
export const _ = objectType(
  "something",
  {
	// ...

This would be ok:
export const _ = objectType("something", {
	// ...

But yeah... not happening

FWIW I think going the contrary route might be even better. Make it so mutationField and queryField take only one object argument, and a name field in it.
const CreateWorker = mutationField({
  name: 'createWorker',
  type: CreateWorkerResponse,
  args: {
    input: arg({
      type: createWorkerInput,
      required: true,
    }),
  },
  resolve: () => {}
})

Now we don't have to guess the number of arguments and no bad prettier formatting. It's a simple and clear convention. Some people will even push for all functions only taking one argument, which is a valid opinion imo. > See swyx's tweet

e.g.:
objectType({ name: "foo", ... })
t.field({ name: "foo", ... })

I guess the problem now is that you will see different api's when defining a type
const User = objectType({
  name: "User",
  definition(t) {
     t.int('id');
     t.field({ name: "Role", type: "Role", resolver: () => {} })
  }
})

For scalars the name is just a string argument, for fields it's inside the object. Which is one of the things that annoys me about typeORM.

Overall, I am currently in favour of the how the API is. fields often fit on one line where objects would never. It's a case where prettier behaviour is a real shame, and interesting how much influence it has over the api design. imo

One reason the current API fares OK is that field level functions are likely to break out into a resolve function quickly, a natural new line break.
And thanks to type inference, the resolve function signature should stay short all the time, pretty much.


Made SFGUI use the new SFML function

sf::Text::setColor :arrow_forward: sf::Text::setFillColor
sf::Text::getColor :arrow_forward: sf::Text::getFillColor
sf::Shader::setParameter :arrow_forward: sf::Shader::setUniform
Deprecation warnings be gone!

Merged, thanks.


Enable Discussions on GitHub repository

@arielhernandezmusa I don't have the permissions to do so - can you turn on Discussions for this repository please?

Thanks @thomasvidas !


Error occur when infering. FileNotFoundError config.yaml

(pyenv310) ➜  SOME git:(main) python infer.py --model /home/tong/Desktop/core/core/project/llm/rmvpe.pt --wav /home/tong/Desktop/temp/demo.mp3
Traceback (most recent call last):
File "/home/tong/Desktop/core/core/project/llm/SOME/infer.py", line 47, in
infer()
File "/home/tong/Desktop/core/core/project/llm/pyenv310/lib/python3.10/site-packages/click/core.py", line 1157, in call
return self.main(*args, **kwargs)
File "/home/tong/Desktop/core/core/project/llm/pyenv310/lib/python3.10/site-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
File "/home/tong/Desktop/core/core/project/llm/pyenv310/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/tong/Desktop/core/core/project/llm/pyenv310/lib/python3.10/site-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/home/tong/Desktop/core/core/project/llm/SOME/infer.py", line 21, in infer
with open(model_path.with_name('config.yaml'), 'r', encoding='utf8') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/tong/Desktop/core/core/project/llm/config.yaml'

--model accepts checkpoint path of SOME, not RMVPE

潼收到


Migrate Beam benchmark to use Gradle for Java runs

Since there is an ongoing maven -> gradle migration in beam, the mvn commands located in beam_benchmark_helper.py should be migrated to gradle's equivalents.
More on that matter here: https://issues.apache.org/jira/browse/BEAM-3942. The beam's part was done, now it's time to change what's necessary in PerfKit.
@asaksena could you take a look? If you don't mind, I'd also like @DariuszAniszewski to take a look before merging this, as he also works very closely with this benchmark.

Sorry, this PR was incorrect. I'll submit another one.


Update [Windows Driver Kit]

Tool name
Windows Driver Kit
Tool license
Proprietary
Add or update?

[ ] Add
[X] Update

Desired version
10.1.22621.2428
Approximate size
No response
Brief description of tool
No response
URL for tool's homepage
https://download.microsoft.com/download/7/b/f/7bfc8dbe-00cb-47de-b856-70e696ef4f46/wdk/wdksetup.exe
Provide a basic test case to validate the tool's functionality.
No response
Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Runner images where you need the tool

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[X] Windows Server 2022

Can this tool be installed during the build?
No response
Tool installation time in runtime
No response
Are you willing to submit a PR?
No response

Hey @NeoAdonis!
We'll check compatibility. Thanks for the highlight.

Deployed


Update to k8s libraries to 1.17.0

Signed-off-by: André Martins<EMAIL_ADDRESS>

This change is

test-me-please

Coverage decreased (-0.02%) to 45.921% when pulling 0ab227a78afd7b20c4a1eeae0c2f58788941bda3 on pr/update-k8s-1.17.0 into 9d3374d12af94d1888cfde1de2318774a8b0ebb9 on master.

test-missed-k8s

test-missed-k8s


Pre-Generate the Archive

Many projects are quite large - 5MB, 20MB, 100MB, and all the way up to 500MB. It's unrealistic to expect the entire project to be compressed on-demand. The compression is slow and an on-demand approach results in a request timeout.
A better approach is to generate the archive on startup, before the server starts. As files are added, removed, or changed, then the archive can be augmented. On server shutdown, we can then delete the archive.
This approach isn't perfect, but I think it will go a long way is helping provide people with a more responsive experience.

@timkim and I ran a few tests on this.
10MB, 50MB, 150MB, 650MB, 1.3GB, and 2.5GB apps with up to 850 files all served okay on OS X and Windows. On Windows, the server can take up to half a minute to startup on the extremely large projects - OS X took a few seconds. Both were capable of serving the app archive immediately upon request, since the implementation streams the archive rather than generating it upfront. Additionally, we tested doubling the project size / files while the server was running (up to 2.5GB) and the server continue to serve the project successfully.
At this point, we feel that a larger performance gain can be found elsewhere.


Client receives interleaved sensor messages

With 0.9.x versions, the streaming server may interleave messages while sending, e.g. image of frame 3 arrives before images of frames 1 and 2. This happens if the server-client communication is slower than the sensor.
This happens because the server currently enqueues a message again when a writing operation is currently being executed by another thread. This opens a window for a newly created message to enter the queue before this one.
Shall we ignore messages while the socket is busy or shall we keep a message queue?

If we ignore messages, as it's usually done in video-games, we will reduce lag at the cost of missing some of the messages. This will remove too the problem of having a message queue able to grow indefinitely.
If we keep a queue, we may introduce a small performance overhead (possibly negligible, should be tested) but we reduce the number of messages lost and we can put a limit on the number of messages that are stored at any given time.

You should probably do either depending on an option setting. There will be some users who don't want any dropped frames, while others may just want the best performance.

We opted for discarding the messages if the connection/client is too slow. Once we add the synchronous mode to the new API this shouldn't be a problem since you can force the simulation to wait for the client each frame.

Hi,
I am facing this problem of interleaved sensor messages. I tested the issue#815 branch, but using cameras with the basic client examples (manual_driving.py and example.py) does not work. For example, executing the example.py with add_a_camera=True produces the following error:
$ python example.py
client version: 0.9.0-158-g0f16fed
server version: 0.9.0-158-g0f16fed
spawning vehicle 'vehicle.mini.cooperst' with 4 wheels
Vehicle(id=34, type=vehicle.mini.cooperst)
Traceback (most recent call last):
File "example.py", line 115, in
main(add_a_camera=True, enable_autopilot=True)
File "example.py", line 88, in main
camera_bp = blueprint_library.find('sensor.camera')
IndexError: _Map_base::at
Without adding a camera the example runs fine.

Hi @jhanhiro,
That's actually a different issue, we changed the name of the cameras but forgot to update the examples, just replace
camera_bp = blueprint_library.find('sensor.camera')

with
camera_bp = blueprint_library.find('sensor.camera.rgb')

it will be fixed when these commits go to master. Thanks for reporting!


CSS properties don't get saved in the same order they are written and saved.

For example:
Imagine there is a CSS file with the selector below. The CSS file is saved.
.card .dimmable.image .imga,
.card .dimmable.image .imgb,
.card .dimmable.image .imgcs {
  background-position: 50% 20%;
  background-repeat: no-repeat;
  border-radius: inherit;
}

Then edit the CSS file in Brackets, in this case I moved the border-radius property from the bottom to the top.
.card .dimmable.image .imga,
.card .dimmable.image .imgb,
.card .dimmable.image .imgcs {
  border-radius: inherit;
  background-position: 50% 20%;
  background-repeat: no-repeat;
}

I save the CSS file in Brackets, open the file in another editor, and I notice that that the above changes have not been made to the CSS file. It seems as if Brackets is intelligently not writing to the the file or prefers its own selector ordering. I can't find any documentation on this, hope someone knows what is going on and how to turn off this behaviour.

Do you have any extensions installed?

No, no extenions installed. I tested this by temporarily removing all extenions to the "disabled" folder and rebooting Brackets. Using Mac OS X 10.6.8

Are you running any postprocesses (Grunt, Gulp, PostCSS...)? Is Brackets actually saving the file in general?

Thanks for your help. I was running Brunch, the "brunch w -s" command. The culprit was https://github.com/garetht/csscomb-brunch, which affects source files upon saving. Issue can be closed.

Closing as extension problem.


1.18.2 crash in Ponder

Crash with Exit code: -1
crash-2024-01-20_22.59.45-client.txt

should be fixed now

Thanks


Should follow redirections but not cache against the redirected path

I'm working on a flexible badge service, Umbo, that allows user to update the badge with any values.
Example: https://github.com/uzyn/umbo-weather/blob/master/README.md
To not reinvent the wheel, I'm relying on the great service, shields.io, for badge generation (for example: https://img.shields.io/badge/Singapore%2C Singapore-27.47°C-yellow.svg)
For the example at umbo-weather, there's a background process that updates the value every 5 minutes.
The badge URL for Singapore weather is http://umbo.zynesis.com/singaporeio8gg0ok8ckwcck8.svg and it redirects to a different shields.io badge URL based on the value.
(Try going to http://umbo.zynesis.com/singaporeio8gg0ok8ckwcck8.svg in 5 minutes interval or so)
Camo, however, returns the final redirected URL and caches against that, of which the value never changes.
It would be great if Camo caches the original requesting URL instead. If not, what do you recommend that I should be doing for such service?

What headers are you setting? GitHub uses camo/fastly and respects caching headers.

@atmos Here are the headers.
$ curl -i http://umbo.zynesis.com/singaporeio8gg0ok8ckwcck8.svg
HTTP/1.1 303 See Other
Server: Cowboy
Connection: keep-alive
X-Powered-By: Umbo 1.0.0 <umbo.io>
Access-Control-Allow-Origin:
Access-Control-Allow-Credentials:
Access-Control-Allow-Methods:
Access-Control-Allow-Headers:
Cache-Control: no-cache
Etag: 5732d227b1eaf5545a786fbdadaafccc812ab55f
Content-Type: image/svg+xml;charset=utf-8
Location: https://img.shields.io/badge/Singapore%2C%20Singapore-28.99%C2%B0C-yellow.svg
Set-Cookie: sails.sid=s%3AcZYsIV2YEOldVY8IG-WhoizndUGLiZfS.afH%2Fp%2Bg6eq904jAAFDGU%2Fq6DmdEdeyLx2aRo9GSV6Ac; Path=/; HttpOnly
Date: Sat, 11 Jul 2015 16:06:22 GMT
Transfer-Encoding: chunked
Via: 1.1 vegur

ETag is set too.
My case is rather unique in the sense that the redirected URL changes, ie, for the same URL:
http://umbo.zynesis.com/singaporeio8gg0ok8ckwcck8.svg
The generated badge is updated every 5 minutes, via different redirection URL, instead of via content changes.

Camo, however, returns the final redirected URL and caches against that, of which the value never changes.
It would be great if Camo caches the original requesting URL instead. If not, what do you recommend that I should be doing for such service?

Why not both? Perhaps the hash could compare the Content-Length, then depends passing cached or renew the hash for being a new image?

Sorry but anything new?


Ethereum logs base logic

I guess parsing should look something like:

let ethereumLogs: [EthereumLog] = {fetch data}
let events = ethereumLogs.map { (log) -> ABIEvent in
 //switch over different contract logs here and check for contract address and topic
 return event
}

Let's define a protocol for contract events like:
protocol Transfer: ABIEvent {
  var from: EthAddress {get}
  var to: EthAddress {get}
  var value: EthNumber {get}
}

Probably we could use reflection to parse data from the log?


So which standards version is it?

This plugin version, when used for WordPress-Core coding standards does not agree with the latest version of phpcs and the WordPress-Core standards installed as a standalone program on my dev site.
Which standard should be used? Seems the two should agree. Since this plugin hasn't been updated in some time, I suspect the standards have gotten out of sync. Need to know which to trust.
And, by the way, phpcbf  totally broke my code when trying to "fix" a file. It seems it left out several lines of real code. This isn't exactly relevant to this, but when one tries to use that to fix the errors in the WordPress-Core coding standard as reported by this plugin, one doesn't want code broken!

Hi! Which plugin version are you using? The 0.1.5 version is old and out of date. You should try the 1.0.0-RC1 (https://github.com/WPTRT/theme-sniffer/releases/download/1.0.0-RC1/theme-sniffer.zip). This version has the latest phpcs and the latest wpcs standards built in.
Also the plugin doesn't offer phpcbf capability so this is not the place to ask for this issue. I'd recommend asking it in the WPCS repo.
Aside from that, I don't like to use phpcbf, as it's known to break the formatting when you have deeply nested multidimensional arrays 🙂

The version 1.0.0 has been released so I'll close this issue 🙂


In AEM, ACS Commons getting overridden by custom configuration under path /apps/cq after build

We are working on AEM SDK 2023.1.10912.20230130T173736Z version & ACS Commons version is 5.0.10.
In our project we have a custom config which is residing under the same path /apps/cq/core/content/nav/tools where ACS Commons gets installed. So whenever we are giving the build the ACS Commons getting overridden by custom configuration, even after we have added  in ui.apps (filter.xml).
Please recommend any solution on this issue?

We have tried the below changes but still ACS Commons is getting overridden,
Updated the ui.apps/src/main/content/META-INF/vault/filter.xml

<filter root="/apps/cq/core/content/nav/tools/xyz"/>

Added overlay paths to the ui.apps.structure/pom.xml

                    <filter><root>/apps/cq/core</root></filter>
                    <filter><root>/apps/cq/core/content</root></filter>
                    <filter><root>/apps/cq/core/content/nav</root></filter>
                    <filter><root>/apps/cq/core/content/nav/tools</root></filter>
                    <filter><root>/apps/cq/core/content/nav/tools/xyz</root></filter>

Try  using the "merge" mode:   <filter root="/apps/cq/core" mode="merge"/>
this way the existing content should be preserved

@psm1420  what @YegorKozlov  suggested.
Also, your ui.apps.structure only needs the ANCESTORS of the subtree youre providing - since youre providing the xyz node/sub-nodes -- it doesnt need to be in the structure def (the structure is telling the installation what nodes it can expect to exist when installing this package).
<filter><root>/apps</root></filter>
<filter><root>/apps/cq</root></filter>
<filter><root>/apps/cq/core</root></filter>
<filter><root>/apps/cq/core/content</root></filter>
<filter><root>/apps/cq/core/content/nav</root></filter>
<filter><root>/apps/cq/core/content/nav/tools</root></filter>

Try using the "merge" mode:  <filter root="/apps/cq/core" mode="merge"/> this way the existing content should be preserved

its working...thanks for the solution!


VRAM requirements?

Cant fit into 24gb vram. This is sd1.5, why is it so big?

Enable xformers may solve your problem (https://github.com/OpenTexture/Paint3D/blob/main/controlnet/diffusers_cnet_txt2img.py#L23)

Same problem here. Installing xformers and enabling it leads to problems with kaolin because the torch version gets updated to 2.3. I can't find a xformers version that support pytorch 1.12


Time standardization and slope priors

This is part PR, part investigation.
Background
As noted in #47, the priors I implemented in #41 didn't match the way we handle time. I calibrated priors in terms of days, our model was working in terms of standardized time (time with mean 0 and variance 1). This model worked, in that MCMC ran acceptably, but did not work, in that the priors were too informative and the posteriors of the independent divisions model were too strongly influenced.
Previous work
Simply removing the standardization on time, however, led to less than stellar MCMC mixing of the Independent Divisions model, and pathological behavior of the Hierarchical Divisions model.
Previous experimentation suggested that standardizing time improved MCMC mixing. However, attempting to mix-and-match scales (set priors on real time, infer on standardized, #55) also led to apparently pathologically bad mixing. In hindsight, this is likely because the transformation induces a strong correlation, where we can otherwise parameterize things more orthogonally.
This PR
TL;DR
We can make MCMC work by using a dense mass matrix instead of a diagonal mass matrix.
I renamed the HierarchicalDivisonModel the HierarchicalCorrelatedDeviationsModel and implemented a MVN-free, simpler HierarchicalDivisonModel. Both of these have "dynamic pooling" as below, and have one small parameter removed from the previous HierarchicalDivisonModel.
What I tried
To debug the hierarchical model, I made a version which could be set to be mathematically equivalent to the Independent model. This required a minor simplification, removing the free parameter sigma_beta_0 (a scalar on intercept variances allowing some lineages to vary more in intercepts than others), and was facilitated by removing the correlated deviations in slopes (where the independent model was only recovered in a limit as we take a fixed hyperparameter to infinity).
This enabled me to rewrite the model as described below. Using that, I was able to get a version of the Hierarchical model which could have parameters fixed to recapitulate the Independent Divisions model. I found that when I re-wrote this model to use plates (plating first over lineage, then division) I could obtain MCMC which mixed as well as the Independent Divisions model. Which is to say, not well, but not so poorly that we couldn't just run it longer and obtain satisfactory convergence diagnostics.
As I increased the strength of the pooling (either letting the model infer it, where it is very strong, or fixing it to 0.5, which is what we implicitly had before), mixing got worse. I tried using numpyro.infer.reparam.LocScaleReparam but this did not appear to have any effect. I imagine that is because the model was already written in the space that parameterization seeks (location 0, common scale 1).
I then tried altering the NUTS settings to use a dense mass matrix, which can account for posterior correlations in parameters. With this turned on, both the Independent and stripped-down Hierarchical models work much better, if slower. (I think the efficiency is worth the tradeoff, such that to get equivalent ESS we'd need to spend more time running the model. But I did not check.)
Lastly, I tried adding back in the correlated deviations of the slopes. With a dense mass matrix, this model can also be sampled.
I did not try adding back sigma_beta_0 as while it is perfectly sensible, the uncorrelated-deviations, dynamic pooling hierarchical model seems to be the simplest starting point for pooled model development and we might as well test what works and doesn't in comparison.
What I think I learned
Partial pooling makes the posterior geometry gnarlier, plates can be useful where applicable, noncentered parameterizations are good, and a good (bad) prior can be bad (good) for mixing.
Dynamic pooling
All slopes and intercepts here are taken to be on the logit scale and absent a reference category, as we have been doing.
For a model with uncorrelated slope deviations, for location $g$ and lineage $\ell$, both intercepts $\boldsymbol{\beta}_0$ and slopes $\boldsymbol{\beta}_1$ can be written as
\beta_{g \ell} := \mu_{\ell} +Z_{g \ell}

with
\mu_{\ell} \sim \text{Normal}(0, \sigma_{\mu}^2)

and
Z_{g \ell} \sim \text{Normal}(0, \sigma_Z^2)

and fixed $\sigma$.
The marginal prior variance is $\text{V}[\beta_{g \ell}] = \text{V}[\mu_{\ell}]  + \text{V}[Z_{g \ell}] = \sigma_Z + \sigma_{\mu}$.
As #41 shows, it is really $\text{V}[\beta_{g \ell}]$ that we have any intuition about.
We can recover the Independent Divisions model by fixing $\mu_{\ell}$ to 0, such that all of the variance in $\beta_{g \ell}$ is due to $Z_{g \ell}$. We can also imagine on the other side a fully pooled model, in which  all of the variance in $\beta_{g \ell}$ is due to $\mu_{\ell}$. The "strength" of the pooling then can be described by how much of the variance comes from either component, which suggests that we can in fact re-write all three models (unpooled, fully pooled, partially pooled) as
\beta_{g \ell} := \mu_{\ell} + Z_{g \ell}

with
\mu_{\ell} \sim \text{Normal}(0, \rho \sigma_{\beta}^2)

and
Z_{g \ell} \sim \text{Normal}(0, (1 - \rho) \sigma_{\beta}^2)

and fixed $\sigma_{\beta}$.
We can set $\rho = 1$ to get a fully pooled model, let $\rho$ be inferred, or fix $\rho = 0$ to recover the Independent Divisions model. I have implemented this model with separate pooling for the slopes and intercepts.
We can also apply this framework to the original Hierarchical formulation where differences in slopes from the grand mean are correlated. We have a number of length $\ell$ vectors instead of scalars (bold is not rendering for some reason)
\boldsymbol{\beta}_g = \boldsymbol{\mu} + \boldsymbol{Z}_{g}

with (as in the non-correlated model)
\mu_{\ell} \sim \text{Normal}(0, \rho \sigma_{\beta}^2)

and
\boldsymbol{Z}_{g} \sim \text{MultivariateNormal}(0, \Sigma)

where $\Sigma = \text{diag}((1 - \rho) \sigma_{\beta}, L) \mathbf{R} \text{diag}((1 - \rho) \sigma_{\beta}, L)$, $R$ is a correlation matrix, $\text{diag}((1 - \rho) \sigma_{\beta}, L)$ is an $L x L$ diagonal matrix with all elements equal to $(1 - \rho) \sigma_{\beta}$, and
R \sim \text{LKJ}(\eta)

As we were already working with our covariance matrix decomposed into a diagonal matrix of standard deviations and a correlation matrix, the $\rho, (1 - \rho)$ formulation is plug and play here too.

I'm running all three time points in retrospective_forecasting with all the models including both hierarchical ones. So far both Early and Late 21L have run, and in both the non-correlated model produces slightly (like, on the order of a percent or so) better evaluation scores for all 4 metrics.

And on Mid 21L, the tally is 2 where the correlated hierarchical model is substantially better, 2 where it scores NaN (the proportions are NaN, the counts aren't), and the uncorrelated hierarchical loses to the Independent on both count scores. So, nothing's simple.

I had missed the fact that in Mid 21L, the non-correlated model also failed to mix, with 1 chain very stuck and 1 chain slow-mixing.


Non admins cannot add procedures

Expected behavior:
A non-admin with the capability to add a procedure (such as a doctor), should be able to add a procedure
Actual behavior:
A non-admin with the capability to add a procedure (such as a doctor) doesn't see a button to add a procedure.
Steps to reproduce:

Login as doctor
Go to patient
Add visit
Click on Add Procedure
Add button does not appear at bottom of screen
Screenshots (if applicable):

OS and Browser:
All

I can look into this one


[bug] tree-sitter-php 0.22.4 should not have tree-sitter 0.21 as dep

Did you check existing issues?

[X] I have read all the tree-sitter docs if it relates to using the parser
[X] I have searched the existing issues of tree-sitter-php

Tree-Sitter CLI Version, if relevant (output of tree-sitter --version)
No response
Describe the bug
Bumping tree-sitter dependency to 0.21 is a breaking change. So the version number should also be bumped to 0.21.0+
https://github.com/ast-grep/ast-grep/actions/runs/8975845192/job/24651378412
Proposal
Release a new version of 0.22.5 to downgrade tree-sitter dep and then release a new version of 0.23.0 to bump the dep version.
Steps To Reproduce/Bad Parse Tree
https://github.com/ast-grep/ast-grep/actions/runs/8975845192/job/24651378412
Expected Behavior/Parse Tree
Not available
Repro
See reported link above

I get the sentiment, but tree-sitter does not strictly follow Rust's guideline on semver, which deviates from the official semver spec with regards to zerover, in that we may introduce incompatible changes between patch versions, because we do not only provide a Rust crate binding, but as well as a pypi package, npm package, C binding, Go binding, Swift binding, etc. So until we're 1.0, we're not going to follow Rust's semver since it deviates.

I'll try to be more mindful going forth though, e.g. we are going to introduce a tree-sitter-language crate to expose the Language ptr without needing tree-sitter as a dependency - I'll bump the minor version for every grammar for this of course

thanks for the explanation!


Add option to skip all zeros in SparseMatrix

Currently, SparseMatrix::AddSubmatrix() will not add zeros to the sparse matrix "unless this breaks the symmetric structure." However, I have encountered problems where this desire to preserve symmetry doubles the memory requirement and makes the problem unwieldy to solve. Therefore, I have proposed a change that will allow users to set skip_zeros=2 to skip all zeros regardless of symmetry.
I looked into implementing this choice as an enum but it would change the signature of many functions.
Thanks!

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#2087
@wcdawn
@tzanio
@cjvogl + @acfisher
03/07/21
⌛due 03/21/21
⌛due 03/28/21

Please document in sparsemat.hpp

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

I've added the documentation. I won't be force pushing the branch. Sorry for any inconvenience :)

I won't be force pushing the branch. Sorry for any inconvenience :)

We started putting this (automatically) as a general statement on all active PRs :)

@homijan and @cjvogl, the reviews for this PR are due

I think it's problematic that skip_zeros in this method now works differently than skip_zeros in the other methods in this class.  I think we should make this the behavior in all of the methods that have it.  Thoughts?

Restarted Travis CI -- it looks like it crashed randomly on the first try.

@acfisher Thanks for the notes. Could you describe where else the code needs to be changed so that the behavior within the class would be consistent?

@wcdawn There are 3 more methods in SparseMatrix that have skip_zeros:
SetSubMatrix
SetSubMatrixTranspose
Finalize
It would be best to add similar logic to those 3 as well.

Currently, SetSubMatrix, SetSubMatrixTranspose, and Finalize all skip all zeros regardless of symmetry (i.e. if (skip_zeros)). I could change them to check if the operation would break symmetry by default but this would mean storing more zeros in the default case (i.e. skip_zeros == 1). Thoughts?

I discussed it at a team meeting today and everyone agreed that it would be best to add the new behavior to the other 3 methods.  We also got a suggestion to put an enum in there to represent it in all 3 cases, but leave the parameter as an int to avoid cascading the change everywhere.  @wcdawn do you mind updating the the other 3 methods so they have the same skip_zero behavior as AddSubMatrix?  I'll handle the enum as there is some specific doxygen syntax to get that to look right in our documentation.

I can work on this. The default behavior will be to preserve symmetry and, for now, skipzeros==2 will skip all zeros. It can be chagned to an enum later.
@acfisher I started implementing an enum on the branch wcdawn/SparseMatrixZeros but gave up after I saw how many function signatures changed. Keeping the parameter as an int should be helpful.

Sounds like a plan.

Implementing this "preserve symmetric" nature is simple with AddSubMatrix, SetSubMatrix, and SetSubMatrixTranspose as all of them are using DenseMatrix as input.
Finalize proved difficult as it required traversing a linked list to check if the matrix is symmetric. Computer science is not my main job so I may have made a mistake in the list traversal.

LGTM

Merged in next for testing...


[test] protobuf to 3.25.4 for v3.5.1

This is for lts7.x test only.

test-samples-java-bigquerystorage fails with:
Step #3: [ERROR] Errors:
Step #3: [ERROR]   QuickstartArrowSampleIT.testQuickstart:52 » ExceptionInInitializer
Step #3: [INFO]
Step #3: [ERROR] Tests run: 8, Failures: 0, Errors: 1, Skipped: 0

re-running


Add Project to https://www.binarydoc.org/ ?

Hi,
would it be possible to add Apache Isis to the projects hosted on binarydoc.org?
See: https://mvnrepository.com/artifact/org.apache.isis/isis-parent
Best regards
Jörg

Hi @joerg-rade , Sure, we will add this project also.

THX !

Binary 5.x (2022 Q1) will support single maven artifacts (instead of a complex application like Eclipse, Tomcat, etc) so will fit for apache isis.