Removal of dependencies to geneinfo app

Is your feature request related to a problem? Please describe.
The geneinfo app isn't used much anymore, expect for resolving gene panels. This can be done with a call to annonars. Double check for other usages of the app.

@stolpeo Could you check for current usage of the geneinfo app and how these can be modeled using annonars? Potentially in discussion with manuel.

annonars can help here, example of public reev

https://reev.cubi.bihealth.org/internal/proxy/annonars/genes/lookup?q=BRCA1
https://reev.cubi.bihealth.org/internal/proxy/annonars/genes/lookup?q=HGNC:1100
https://reev.cubi.bihealth.org/internal/proxy/annonars/genes/lookup?q=ENSG00000012048
https://reev.cubi.bihealth.org/internal/proxy/annonars/genes/lookup?q=672

Will be discussed between @stolpeo and @holtgrewe

Remaining todo

resolution of HPO-Terms

@stolpeo Will complete currently remaining work to reduce dependencies to geneinfo app.


radare2-cutter: 1.10.3 -> 1.10.3

Motivation for this change
Things done

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

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

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

Wrong commit message?

@GrahamcOfBorg build radare2-cutter


Overcrit/OverDH multipliers from stat

Attached is an image of the 6.2 patch notes for context.
I am aware that the simulator attempts to resolve the first point regarding chance increasing buffs, however I am under the impression that it is currently incorrect.
Furthermore, I do not believe the simulator accounts for the second point at all.

From the small amount of testing that I had done in 6.2, I had found the following regarding these changes to crit/dh.
I will be using 2300 crit substat and 1091 dh substat which correspond to (25%, 1.6) and (20%, 1.25) respectively.
1.) Crit substats apply 10% of their rate into crit damage/bonus under "Overcrit" actions.  For example, a guaranteed crit will have a multiplier of (1.6 + 0.25*0.1).
2.) DH substats apply 20% of their rate into DH damage/bonus under "OverDH" actions.  For example, a guaranteed DH will have a multiplier of (1.25 + 0.2*0.2).
3.) Crit Buffs apply exactly their rate into the crit damage/bonus under "Overcrit" actions.  For example, Chain Strategem increases critical hit rate by 10%.  This means a guaranteed crit will have a multiplier of (1.6 + 0.25*0.1 + 0.1)
4.) DH Buffs apply half their rate into the direct hit damage/bonus under "OverDH" actions.  For example, Battle Voice increases direct hit rate by 20%.  This means a guaranteed DH will have a multiplier of (1.25 + 0.2*0.2 + 0.2*0.5)
While the data I have is not extensive, there is a relative error of ~1% when using these methods to calculate "Overcrit" and "OverDH".
I will be easiest to reach through discord where my handle is "lial" if there are any extensive questions that are more easily resolved off of this platform.
Enjoying the simulator 👍 and hope it only gets better from here.

Hey, thanks for the report!
Hmm, can you share with me what logged damage you have + gearset you used? Like an fflogs url or something, so I can compare? Those particular functions are regression tested, and the sim is verified using 25+ savage and ultimate logs, with auto-crit/dh skills under full raid buffs (each logged damage instanced is checked against the sim's theoretical, unsampled damage ranges). I would like to be able to reproduce your findings and check to make sure it's not like a potency change between 6.2 and 6.55, or gear difference! I'm not aware of the 10%
On DH: https://github.com/Amarantine-xiv/Amas-FF14-Combat-Sim_source/blob/main/ama_xiv_combat_sim/simulator/calcs/compute_damage_utils.py#L38
bonus_dh_rate_add = status_effects[0].dh_rate_add + status_effects[1].dh_rate_add
return GameConsts.DH_DAMAGE_MULT_BONUS*bonus_dh_rate_add
On Crit: https://github.com/Amarantine-xiv/Amas-FF14-Combat-Sim_source/blob/main/ama_xiv_combat_sim/simulator/calcs/compute_damage_utils.py#L42
And their combination: https://github.com/Amarantine-xiv/Amas-FF14-Combat-Sim_source/blob/main/ama_xiv_combat_sim/simulator/calcs/compute_damage_utils.py#L47
damage_spec = skill.get_damage_spec(skill_modifier)

forced_dh = ComputeDamageUtils.__get_forced_dh_status(damage_spec, skill_modifier, status_effects)
forced_crit = ComputeDamageUtils.__get_forced_crit_status(damage_spec, skill_modifier, status_effects)

bonus_dh_multiplier = ComputeDamageUtils.get_guaranteed_dh_bonus_dmg_multiplier(status_effects) if forced_dh else 0
bonus_crit_multiplier = ComputeDamageUtils.get_guaranteed_crit_bonus_dmg_multiplier(stats, status_effects) if forced_crit else 0
return (bonus_dh_multiplier, bonus_crit_multiplier)

If you could provide a log and gearset, I can take a look! Thanks!


ES6 Cleanup

This mostly cleans up code a bit:

Update babel-loader + babel-core to most recent version
Add stage=0 to babel-loader
Move static method fetchData into class definition.
Clean up module loading in Routers

Coverage decreased (-0.24%) to 97.5% when pulling 29b2eb1a6b25ab4421e4b15a1012cdcc38effc59 on StevenLangbroek:es6_cleanup into cb5f0bdb6cd7a14a7998d4ee812dd8d96bcdd67d on pheuter:master.

awesome :+1:


Node token example does not work

Hey there,
I would like to use the sdk to upload files programmatically via node, but when I run the examples/node/token.js example, after I open the provided link and input the access code, I get:
Invalid 'code' provided.

Both client_id and app_secret are provided in app.json.

Good luck with the project and I hope you overcome the security issues easily. As a pCloud user I appreciate any efforts to create a decent pCloud remote-file uploader/account manager. Cheers! -Jeff

AFAIK token isn't working, also not via the API directly


Add *User param to GetUserInfo to avoid read replica issue

Summary
There is an issue where we update user info in the kv store, and immediately try to read the info, resulting in a data inconsistency.
Ticket Link
Fixes https://github.com/mattermost/mattermost-plugin-jira/issues/694

Codecov Report

Merging #723 (f9491fe) into master (88e91f3) will decrease coverage by 0.06%.
The diff coverage is 13.33%.

@@            Coverage Diff             @@
##           master     #723      +/-   ##
==========================================
- Coverage   32.53%   32.46%   -0.07%
==========================================
  Files          52       52
  Lines        5361     5363       +2
==========================================
- Hits         1744     1741       -3
- Misses       3418     3423       +5
  Partials      199      199

Impacted Files
Coverage Δ

server/command.go
15.60% <0.00%> (ø)

server/instances.go
30.73% <0.00%> (ø)

server/info.go
52.50% <16.66%> (-2.77%)
:arrow_down:

server/user.go
23.37% <33.33%> (ø)

server/kv.go
19.88% <0.00%> (-0.86%)
:arrow_down:

Continue to review full report at Codecov.

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

2/5 I really want to see a "request-time write-through" cache implemented as part of the KV interface, so Set/Get can be used indiscriminately while handling a request. Optionally, writes can be combined/written out once if appropriate. This is a separate idea, for all plugins, cc @larkox. This is probably a 2-4 mana to implement in experimental and we can then migrate plugins to use it.

/update-branch

Tested and passed

From what I can tell, this does seem to solve the issue.
Testing on HA server compared to the  3.0.0 release the problem appears resolved
We should merge this to master so we can deploy to community where more conclusive testing will take place
I will create a follow-up issue if I can repro on community which has read replicas

Note I did find a separate issue in testing where the post menu options for Jira are occasionally missing. Created https://github.com/mattermost/mattermost-plugin-jira/issues/729 to address this.
LGTM!

@jfrerich can you please review this so we can have it in master branch and request a temp release for community?


Livestream.com plugin bug:stops at 2GB

Capturing a live stream from livestream.com using livestream plugin stops (with no error) at exactly 2GB.
I have tested this 4 times, and each time it stopped capturing with no error (even with -l debug on) exactly at 2.0GB capture file (there is no variation in the size of the file whatsoever -- all captures, of different live streams have stopped at exactly the same number of bytes).
On the other hand, if I run a simultaneous capture by grabbing the .m3u8 URL from the page source (NOT using the livestream plugin), no issue is found -- the capture continues cleanly until the webcast completes, yielding a file much larger than 2GB.
I'm running the latest standard distribution, using the Windows installer.

I have this issue as well.
My Azubu recordings always ends with 2GB. :(

@scottbernstein
chrippa commented on 17 May 2015

The HTTP streams from livestream.com sends a Content-Length header with the value 2GB, and the server is probably closing the connection after that amount of data has been read. You can try using the HLS streams (use --stream-types hls to filter out the other ones) instead.

Thanks -- yeah that's exactly what I've been doing to get around the issue.

Sorry guys, but how do I apply this canche "(use --stream-types hls to filter out the other ones)" here?
I'm still lernaing. :)

@NeoFahrenheit
Which website are you trying to access? Azubu.tv? Livestreamers Azubu.tv plugin does not support HLS streams. In this case your attempt would be useless. They are using Akamai HD streams (similar to Livestream.com) and this may be the reason why you are experiencing the same problems: The server closes the connection after a certain amount of data has been send. I'm not sure if there are other stream types available, which could be implemented in the plugin. I haven't looked into it.

@0880
Yes, it's Azubu. :(
Ok, then, I'll wait for the solution. :)
I'll test to see if this problem happens on Twitch as well.
If yes, can you say how do I use that fix?
Thanks for the support!

@0880
Yeah, It's not happen on twtich.
The video file exceeds 2GB.
Any progess on the fix?
Thanks so much for the support!

@NeoFahrenheit
HLS streams are available too. Could be useful to bypass the 2GB limit.
youtube-dl -F "http://www.azubu.tv/Starfire"
[AzubuLive] Starfire: Downloading JSON metadata
[AzubuLive] Starfire: Downloading JSON metadata
[AzubuLive] Starfire: Downloading m3u8 information
[info] Available formats for 190049:
format code  extension  resolution note
meta         mp4        multiple   Quality selection URL
250          mp4        480x270     250k , mp4a.40.2,  avc1.42001e
500          mp4        640x360     500k , mp4a.40.2,  avc1.4d001e
1000         mp4        854x480    1000k , mp4a.40.2,  avc1.42001e
2400         mp4        1280x720   2400k , mp4a.40.2,  avc1.4d001f
3300         mp4        1920x1080  3300k , mp4a.40.2,  avc1.640028 (best)

youtube-dl -g "http://www.azubu.tv/Starfire"
http://azubuhlslivesp2-i.akamaihd.net/hls/live/223591/hls-saopaulo-2_2/video190049CHStarfire/3300/azevinho.m3u8

livestreamer "hls://http://azubuhlslivesp2-i.akamaihd.net/hls/live/223591/hls-saopaulo-2_2/video190049CHStarfire/3300/azevinho.m3u8" best -o Azubu.ts
[cli][info] Found matching plugin stream for URL hls://http://azubuhlslivesp2-i.akamaihd.net/hls/live/223591/hls-saopaulo-2_2/video190049CHStarfire/3300/azevinho.m3u8
[cli][info] Available streams: live (worst, best)
[cli][info] Opening stream: live (hls)

@0880
Thanks so much for your great support, but I have no idea what to do with those codes. :(
Sorry. :(
Thanks again!


broken models

I just want to inform that some models are not being correctly compiled or are prompting error when compiling.
Some other noticed problems were: shark crashing after printing 20+ images.
I noticed that the last version that some old models where beign correctly used was release 511.

please add required information like:
Which model does not work?
What is the output in the terminal when SHARK crashes?
What GPU do you use?
Which version are you using when all of this happens?


fitToCoordinates does not work properly on iPhone 11 Pro Max

Summary
fitToCoordinates does not work as expected in iPhone 11 Pro Max
Environment info
react-native: 0.63.4
react: 16.13.1
react-native-maps: 0.31.1
Target Platform:  iOS
Device in which issue is reproduced : iPhone 11 Pro Max, iOS 15.4
Steps to reproduce
Call fitToCoordinates once when screen is mounted using a set of coordinates, works fine
Navigate to another screen, return back to the first screen and call fitToCoordinates  using the same set of coordinates, we will get the bug.
Describe what you expected to happen:
Map should be show correct area
Describe what actually happens:
Map does not stays within the required coordinates
Reproducible sample code
`fitAllMarkers = (coords = []) => {
    let edgePadding =
        Platform.OS == "android" ?
            {
                top: PixelRatio.getPixelSizeForLayoutSize(80), right: PixelRatio.getPixelSizeForLayoutSize(20), bottom: PixelRatio.getPixelSizeForLayoutSize(80), left: PixelRatio.getPixelSizeForLayoutSize(Metrics.screenWidth * .45)
            } :
            {
                top: initialWindowSafeAreaInsets.top + 80 + getStatusBarHeight(), right: 20, bottom: 80, left: Metrics.screenWidth * .45
            }

    let coordinates = [
        {
            latitude: parseFloat(this.props.currentLocation.latitude),
            longitude: parseFloat(this.props.currentLocation.longitude),
        },
        {
            latitude: parseFloat(this.props.objStoreDetails.latitude),
            longitude: parseFloat(this.props.objStoreDetails.longitude)
        }
    ]

    if (coords.length !== 0)
        coordinates = coordinates.concat(coords)

    if (this.mapView !== undefined && this.mapView !== null) {

        this.mapView.fitToCoordinates(coordinates, {
             edgePadding: edgePadding,
             animated: true
        })
    }

}

.......
<MapView
ref={ref => this.mapView = ref}
                provider={PROVIDER_GOOGLE}
                zoomControlEnabled={false}
                zoomEnabled={false}
                pitchEnabled={false}
                scrollEnabled={false}
                zoomTapEnabled={false}
                showsUserLocation={false}
                zoom={100}
                customMapStyle={myMapStyle}
                style={[styleMapView.mapView, { height: this.props.mapHeight + (Platform.OS == "ios" ? initialWindowSafeAreaInsets.top : 0), marginTop: Platform.OS == "ios" ? -initialWindowSafeAreaInsets.top : 0 }]}
                moveOnMarkerPress={false}

            >

`

Having the same issue described here

It seems that the ref callback does not work.
<MapView
ref={ref => console.log(ref}
does not result in any output

It seems that the ref callback does not work.
<MapView ref={ref => console.log(ref}
does not result in any output

It certainly works, wait till map is ready

Just some clarification for the bug, it malfunctions only while using Google maps on iOS, in default apples map it works as expected.

I am getting the same issue with GOOGLE maps but, It's working perfectly with apple maps. Any suggestions please for google maps.

Thanks for the suggestion @XeeshanAnsari! will try it and hopefully it will work!

Same issue here

When are you calling the fitAllMarkers function?

I'm closing for now. If anyone is still experiencing this, please comment with an up to date reproducible example and I'll be happy to re-open :)

I have same issue. I use ani iphone 12 emulator with ios 16 in xcode 14 and props provider: google. If i change to apple maps, y dont have this issue.


Add right-click Manual Extraction

User needs to be able to right-click to add a new data item marked as a "manual extraction".

Looks good!


Add precision to datetime field, datetime field internally expressed in microsecs.

@evanxg852000 can you edit this ticket with your plans?

closing... this was meant to be in tantivy.


feat(frontend): show open rooms sidebar

🍰 Pullrequest

Issues

fixes #709

Todo

[X] None

I can't comment in the code, because there was no change. But in DefaultLayout.vue line 17, we should remove the class="d-md-none" to avoid a warning, as BottomMenu doesn't have a single root element anymore to pass on the class property. The class is included in that file now, which is fine.
Besides, we could think about refactoring the code so that ListWithNavigationDrawer is only used once and not in both menus in the same way.


Use the id of the account instead of the application id

Fix for issue: https://github.com/ParsePlatform/parse-server/issues/3106

See: https://github.com/ParsePlatform/ParseTwitterUtils-iOS/blob/master/ParseTwitterUtils/Internal/PFTwitterAuthenticationProvider.m#L21

@jonas-db can you force the authData.id to be a string by using? ''+authData.id We'll be able to merge after that.

@jonas-db Many thanks for the fix!


🐞 - Angular library takes way too long to build after updating to angular v14

Which @taiga-ui/* package(s) are the source of the bug?
Don't known / other
Please provide a link to a minimal reproduction of the bug
https://github.com/arndwestermann/update-to-angular-v14
Is this issue blocking you?
Blocking
Description
After updating my nx workspace to 14.2.x which included angular v14.x one of my libraries took around 15 minutes to build, I finally could reproduce it in a clean workspace.
There is on library called test, which only contains the NativeDateTransformerDirective from your example.
Steps to reproduce

Clone the provided repo
Run npm i
Run npx nx build test --prod

My output
Projects/update-to-angular-v14 % npx nx build test --prod

> nx run test:build:production

Building Angular Package

------------------------------------------------------------------------------
Building entry point '@my-org/test'
------------------------------------------------------------------------------
⠋ Compiling with Angular sources in Ivy partial compilation mode.Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
⠙ Compiling with Angular sources in Ivy partial compilation mode.Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
Warning: Entry point 'angular2-text-mask' contains deep imports into '/Users/awestermann/Projects/update-to-angular-v14/node_modules/text-mask-core/dist/textMaskCore'. This is probably not a problem, but may cause the compilation of entry points to be out of order.
✔ Compiling with Angular sources in Ivy partial compilation mode.
✔ Generating FESM2020
✔ Generating FESM2015
✔ Copying assets
✔ Writing package manifest
✔ Built @my-org/test

------------------------------------------------------------------------------
Built Angular Package
 - from: /Users/awestermann/Projects/update-to-angular-v14/libs/test
 - to:   /Users/awestermann/Projects/update-to-angular-v14/dist/libs/test
------------------------------------------------------------------------------

Build at: 2022-06-13T07:48:03.441Z - Time: 799425ms

 ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Successfully ran target build for project test (13m)

If you delete the directive and run the build again it takes about 6 seconds
Projects/update-to-angular-v14 % npx nx build test --prod

> nx run test:build:production

Building Angular Package

------------------------------------------------------------------------------
Building entry point '@my-org/test'
------------------------------------------------------------------------------
✔ Compiling with Angular sources in Ivy partial compilation mode.
✔ Generating FESM2020
✔ Generating FESM2015
✔ Copying assets
✔ Writing package manifest
✔ Built @my-org/test

------------------------------------------------------------------------------
Built Angular Package
 - from: /Users/awestermann/Projects/update-to-angular-v14/libs/test
 - to:   /Users/awestermann/Projects/update-to-angular-v14/dist/libs/test
------------------------------------------------------------------------------

Build at: 2022-06-13T08:06:16.346Z - Time: 1827ms

 ———————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

 >  NX   Successfully ran target build for project test (6s)

Projects/update-to-angular-v14 % npx nx report

 >  NX   Report complete - copy this into the issue template

   Node : 16.13.2
   OS   : darwin x64
   npm  : 8.1.2

   nx : 14.2.4
   @nrwl/angular : 14.2.4
   @nrwl/cypress : 14.2.4
   @nrwl/detox : Not Found
   @nrwl/devkit : 14.2.4
   @nrwl/eslint-plugin-nx : 14.2.4
   @nrwl/express : Not Found
   @nrwl/jest : 14.2.4
   @nrwl/js : 14.2.4
   @nrwl/linter : 14.2.4
   @nrwl/nest : 14.2.4
   @nrwl/next : Not Found
   @nrwl/node : 14.2.4
   @nrwl/nx-cloud : Not Found
   @nrwl/nx-plugin : Not Found
   @nrwl/react : Not Found
   @nrwl/react-native : Not Found
   @nrwl/schematics : Not Found
   @nrwl/storybook : 14.2.4
   @nrwl/web : Not Found
   @nrwl/workspace : 14.2.4
   typescript : 4.7.3
   ---------------------------------------
   Community plugins:
         @taiga-ui/cdk: 2.48.0
         @taiga-ui/core: 2.48.0

Angular version
14.0.0
Taiga UI version
2.48.0
Which browsers have you used?

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[X] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

This would have to wait for 3.0, which is coming rather soon. I'm closing it in favor of https://github.com/Tinkoff/taiga-ui/issues/980


enhancement: Integrate CRDT

If you're looking for a CRDT library, might I suggest using Loro, which is written in Rust and recently hit its v1.0 release ...
It seems like a solid option, and I'm looking at using it for a similar use case.
Just thought it might save you a little time looking around ..

Yeah! Thanks for the suggestion @diversable !


Splash: gentle ux to notify user splash screen is not broken rendering

Refs: #54937
Currently our splash screen is very minimalistic and it can easily be confused by rendering being broken. I personally really like how Slack just adds a gentle ux so it is immediatly clear to the user that the whole thing is acutally loading.
Can we be inspired by them and add a similar notion in the sidebar and in the editor area. The goal is that the user does not get puzled if rendering is broken but gets the clear indication that vscode is starting up

Not a fan - the goal should be to be able to render the UI as fast as possible and we should move more into the pre-start phase, e.g. (disabled) buttons and titles

Sure rendering the UI as fast as possible makes sense. But not sure how adding some ux will slow things down and affect this.
The only downside of this approach that I see is that there can be a "mini flash" when content changes, but due to that we should use light colors.

no action planed


Add direct resume

Remove all experience/involvement/education components
Create resume component which just displays PDF version of my resume

This reduce need to update other things other than just my resume. It also keeps formatting consistent.

Coverage remained the same at 100.0% when pulling 3417a18ccb04d3a08a706131b577b18da9013e55 on add-direct-resume into 076117f0ba9b88e03ca03637681481b0cf4aecd2 on master.


Discord Webhooks should hide multiline commit details

Description
While #31668 was resolved (thanks!), the messages of Discord webhooks is still hard/harder to read in some cases like this one :

Now, the message is truncated after 50 characters like GitHub, but I think that only the first line of the message should be displayed. See GitHub for comparison (these are also multiline commits) :

Gitea Version
1.22.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.30.2
Operating System
Linux
How are you running Gitea?
Official docker image
Database
PostgreSQL

Thanks for the report! This is unattended behavior... https://github.com/go-gitea/gitea/pull/31970 should have removed the commit description and just kept the summary:
https://github.com/go-gitea/gitea/blob/41b4ef825dba14f11b2e9454692b999f92ee1a42/services/webhook/discord.go#L159
Here we split the commit message with \n as the delimiter and we only choose the first line. It also removes any trailing /r if it exists.
Looking at the Go docs further, I may have misused SplitN() and should have done:
strings.SplitN(commit.Message, "\n", 2)[0]

... since the last element would be the "unsplit remainder" that the docs talk about. Currently we seem to be using the unsplit remainder (which would just be the message). Reading the code of strings.SplitN() also points to this being the case. That PR also had a unit test, but didn't catch this edge case since the commit summary was > 50 (while yours is < 50).
Not sure how I missed this. I'll be making a PR to correct this.


pull request for e2e test at 01/31/2017 08:45:12

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[FIX] Wrong language on Chrome

The bug is described here: https://github.com/stefalda/react-localization/issues/36

The thing that fixed that bug was to move checking existence of navigator.language as first.
added tests cases for this function
mocked navigator in test file the main code is cleaner :)

@stefalda Please tell me if you have questions for this PR. When this is ready I am going to do tests for the stringFormat with React components :)

I was wondering if moving the "utils" part to a different file could lead to the unification with the react-native-localization project...

Hmm when I looked at https://github.com/stefalda/ReactNativeLocalization I did not see react-localization as its dependency?

No unfortunately they are different plugins even if they share 80% of the code...

Hmm have you thought unifying them? If yes what is blocking to use this library as dependecy for RN version of this library?

Because it started the other way around... first the react-native version then this one :-)
It should be feasable anyway...
The only problem is how to check for the interface language, maybe the constructor could accept a method or a class that implements the getLanguageInterface method...
I have to make some tests...

Ahaa so in React Native you check interface language from native side. Otherwise functionality is almost same? Btw I made new PR :D https://github.com/stefalda/react-localization/pull/40

Exactly.


Add @resource decorator for marking resource model types

This PR fixes Azure/cadl-azure#1768 which requests a new @resource decorator used for marking a model type as a resource.  The initial goal of the decorator is to simplify the pattern for how a spec author creates a new resource type.
Previously, one would write a resource type like so:
model Widget {
  @key("widgetId")
  @segment("widgets")
  id: string;
}

After this change, it now looks like:
@resource("widgets")
model Widget {
  @key("widgetId")
  id: string;
}

The improvement here is that the resource type is more clearly marked and the user no longer has to know to use the @segment decorator directly on the key property to define the collection name for route generation.
This decorator can later be expanded to add other functionality, but we're keeping it simple for now to solve this one problem.  Also worth mentioning that the previous approach with @segment still works, the new @resource decorator is not required at this time (and probably shouldn't ever be if we can avoid it).

Default pluralization of the model name to get the resource name would be pretty sweet!

I can hear Nick groaning from Montreal :)


pull request for e2e test at 12/13/2016 05:26:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Portal 1666/add dropdowns

Connect to this ticket: https://cdc-dexops.atlassian.net/browse/PORTAL-1666

added Routes to Track Submissions Page
added DataStream, Routes, and Timeframe to Dashboard
added getPastDate help function and tests
added Enum and Static values for Timeframes

I need to refactor a bit to get around the SonarCloud repeated code quality gate.


Correct docker container link

@randy-armstrong thanks for merging #36
After that it would make sense that you enable automated docker container builds for your own OPCF account. Otherwise the Readme still links to my docker builds:
https://github.com/OPCFoundation/UA-ModelCompiler/blame/master/README.md#L34
Its very easy and can be done in 5 minutes.

Create a personal account for you
Create a new organization on docker cloud: https://hub.docker.com/orgs OPCFoundation would make sense here as a name
Create a new repository UA-ModelCompiler
Link that docker repo to the github repo: https://docs.docker.com/docker-hub/builds/link-source/
Enable automated builds or just use the settings below: https://docs.docker.com/docker-hub/builds/

Here are the Settings I'm using, you can just use the same and you are done:
Branch: master
Tag: latest

Update the readme link
Just push to your repository, and it will automatically build a new docker container

You can also contact me directly if you have further issues or if I can support you in that direction
https://opcua.rocks/contact/

The OPC-F has a policy to not provide pre-compiled binaries for code made available as samples.
The link to your docker image is fine.
You will obviously need to help anyone who has problems with it.


Kotlin revolution

I don't think we want the src/main/java vs src/main/kotlin style. I'd like it to be .kt and .java files in the same folders preferably.

Yeah I'm not against the first part.
I didnt touch VRServer tho, only touched Main in purpose to give an example Kotlin file

how is this?

This looks good to me.
As an aside: I know things like syntax don't truly matter. But I look at this code and the var my_var: Type = asdf is really nice to look at :)

Related to #398


FAQ: How to stop printing on Rmarkdown and only send to the console

I've gotten a million questions about this. Let's add to the FAQ


Loot tracker - move most recent loot source to the top + drag n drop reorder

Loot tracker is great. I like to save the loot of everything I kill. I don't like that my monsters/clues are all over the place though. It would be nice if the most recently looted things went to the top. Additionally, if possible, have the option to drag and drop reorder them and tidy up/group things together myself.

First part is a duplicate of #8519.


Feature: Display different memory used during emulation (RAM...)

GhidraEmu is very interesting plugin to emulate code and check what happen in stack or register but unfortunately it does not allow to see change in RAM (not in stack)
Could you add that feature to display different section (RAM, SRAM....) ?

PCode instruction emulation really allows you to see where any bytes are written.
It's possible to create something similar to Ghidra's ByteViewer that will reflect all the changes that the write-to-mem instructions have made, are you talking about that?

Yes just to have a way to view all "memory" written with data value in HEX, ASCII ... like your view for the Stack memory

Hi!
I worked on improvements, including this idea. It was possible to implement this in the new release.
https://github.com/Nalen98/GhidraEmu/releases/tag/2.0
Very briefly:

Changed bytes during emulation will be displayed in the Ghidra's classic ByteViewer. GUI will be updated in this case too. The most of the time was spent handling/updating pointers and references.
If you want to change some bytes before/during emulation, don't forget to select them and press "Apply patched bytes". This will make it possible for the emulator to know about the changes that have occurred in memory and not to conflict in the future.

Thanks for that amazing feature implemented so quickly


Add support for customizing the Authorization header

When ROS is running behind a proxy or a firewall that already attaches meaning to the Authorization header, users want to be able to supply a token with the header.
In addition, based off ROS/sync changes, need to expose the ability to change the name used to supply the ROS auth token in the header.

@fealebenpae This has been done, but need to be included in an official release still?

@tgoyne can we merge this to master?

Merge what? This isn't a PR.


テンプレートの例を追加

Codecov Report

Merging #136 (02cb394) into master (10a3895) will increase coverage by 0.08%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #136      +/-   ##
==========================================
+ Coverage   97.53%   97.61%   +0.08%
==========================================
  Files          36       37       +1
  Lines        1661     1721      +60
==========================================
+ Hits         1620     1680      +60
  Misses         41       41

Impacted Files
Coverage Δ

source/template_example.d
100.00% <100.00%> (ø)

source/sync_example.d
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Queue for download and show progress in notification.

I want set queue download because internet very slow.  And i want show progress in notification when use download.
Please help me,
Thank bro.

This feature will be added later. You can now fork a project and add a global callback listener to the DownloadResponseImpl file.


Setting "jdk: oraclejdk8" for Travis builds

See #57

Merged with 3caa8e41fee2fe451342aaa7afbcc0e34d7c2ea7. Thanks @covex-nn!
Not sure why the tests aren’t running but this gets us one step closer.

I think that could happened because of incompatibility between nativescript versions:

You code require<EMAIL_ADDRESS>https://github.com/NativeScript/sample-Groceries/blob/master/package.json#L41)
npm install -g nativescript in .travis.yml file installed<EMAIL_ADDRESS>https://travis-ci.org/covex-nn/sample-Groceries/builds/140325602#L1108

3 days ago, after<EMAIL_ADDRESS>release, all tests were successfully passed:

https://travis-ci.org/NativeScript/sample-Groceries/builds/141649113#L1107
https://travis-ci.org/NativeScript/sample-Groceries/builds/141649113#L1619


[SMALLFIX] Add javadoc for MasterClientAuthenticationIntegrationTest#NameMatchAuthenticationProvider

Add javadoc for MasterClientAuthenticationIntegrationTest#NameMatchAuthenticationProvider

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13367/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.master.MasterFaultToleranceIntegrationTest.deleteFileFault
Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

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


Sports endpoint errors

I was trying out the Sports API earlier and found a bug. Tried it on the server and locally.
/apis/sports/football according to the source code should return a array of upcoming matches but at the moment it returns a array with about 50 instances of the same object
{
      "counter": "1",
      "date": "mán. 09. maí",
      "time": "19:00",
      "tournament": "Borgunarbikar karla",
      "location": "Vivaldivöllurinn",
      "homeTeam": "Kría",
      "awayTeam": "KB",
      "undefined": "Fram 3"
}

Also notices that when making API requests to the following endpoint you get outdated results
/sports/football/male-leagues/pepsi/
The url thats being used to fetch the data for that endpoint is the results of the league last year.
Current url: http://www.ksi.is/mot/motalisti/urslit-stada/?MotNumer=33503
New url: http://www.ksi.is/mot/motalisti/urslit-stada/?MotNumer=35586
This is probably a error on all the specific endpoints for each division as it looks like KSI creates a new tournament each year for all divisions.

Should be fixed in #293


Improve install instructions to point to Releases

The default install instructions point to the zip of the master branch, this could be an unknown version, I suggest instead linking to the Releases URL, https://github.com/markmikkelsen/Gannet/releases and note that development code can be downloaded via git.

The instructions in the README have been updated to make it clearer that stable releases are found on the Releases page.


Feature/client path module component

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Fixed issues (PRs without this will not be accepted)

Fixes #92

Changes

Add PathModule folder by adding PathModule component
Note: mock data need to be replaced when API ready.

PR Checklist

[x ] Does your PR contain relevant tests that pass?
[x ] Is your code linted? yarn lint or yarn lint:fix
[x ] Does your code build correctly in ALL projects? yarn build

Hi @Ellie-2020
This is open 11 days.
Can you give me an update on this?
Do you need any support with it?

This is waiting for review.

Hi @Ellie-2020
Can I have an update on this PR?
Last activity seems to be 7 days ago and there's open review change request from @tristanMatthias


KYLIN-3935 ZKUtil acquire the wrong Zookeeper Path on windows

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Pull Request Test Coverage Report for Build 4346

0 of 3 (0.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.002%) to 27.865%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-common/src/main/java/org/apache/kylin/common/util/ZKUtil.java
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

core-job/src/main/java/org/apache/kylin/job/impl/threadpool/DefaultScheduler.java
2
80.23%

Totals

Change from base Build 4342:
-0.002%

Covered Lines:
22609

Relevant Lines:
81139

💛  - Coveralls


GPU unavailability issues

The objective of this issue is to summarize GPU unavailability issues to notify each issue when GPU is back.
If you encounter the "There is no runtime available right now. Please change the compute type or try again later." message, you do not need to raise an additional issue because we understand the problem and fighting to solve it 💪
The issues are ordered by time line.
2023

March

https://github.com/aws/studio-lab-examples/issues/202

February

https://github.com/aws/studio-lab-examples/issues/202

2022

September

https://github.com/aws/studio-lab-examples/issues/144

August

https://github.com/aws/studio-lab-examples/issues/141

July

https://github.com/aws/studio-lab-examples/issues/133

June

https://github.com/aws/studio-lab-examples/issues/115

May

https://github.com/aws/studio-lab-examples/issues/110

Requests about GPU

https://github.com/aws/studio-lab-examples/issues/98
https://github.com/aws/studio-lab-examples/issues/121

I cannot access to studio lab neither via CPU or GPU. No runtime available on both. I have tried to access for a week and the problem persists.

I now have access to a GPU instance but tensorflow is unable to list GPUs. I am able to see the GPU for my instance using !nvidia-smi but tf.config.list_physical_devices() doesn't list any GPUs, neither does adding the 'GPU' param. I've spent two days just trying to play with TensorFlow and this Studio Labs has made it impossible.

@RaistlinD2x If you have the TensorFlow specific problem, could you please raise an another issue? If nvidia-smi works, GPU itself is available.

Still facing this issue with low availability of GPUs.

Hey all, hope you are enjoying the improvement in GPU capacity.

The objective of this issue is to summarize GPU unavailability issues to notify each issue when GPU is back.
If you encounter the " @**There is no runtime available right now. Please change the compute type or try again later.**"

To confirm, GPUs are just NOT available anymore?


Netflix 1080p extension?

Would it be possible to add the Netflix 1080p extension? To get Full HD 1920x1080 video stream instead of only 1280x720 max.
https://github.com/jangxx/netflix-1080p

The cast-labs electron release that Quark Player uses includes VMP and should enable 1080p streaming, are you sure you're not being throttled?

In Quark Player in Netflix when I press Shift+Ctrl+Alt+D during a movie supporting 1080p then it shows "Playing bitrate (a/v): 128 / 662 (1280x720)". So I can only get 720p. The mentioned extension enables 1080p in Chrome Browser. I wish it could also be used in Quark Player

Looks like these extensions do actually accomplish things, did some testing. This should be implemented

Maybe I see this issue "no 1080p but 720p", because I use the Windows 7 version?


We shouldn't rely on the existence of "module.paths" (Meteor)

According to CommonJS specs, the paths property is optional. Depending on its existence, e.g.
https://github.com/mochajs/mocha/blob/master/lib/mocha.js#L28
may cause unnecessary runtime errors, for example:
https://github.com/benjamn/install/issues/9
We should probably test against the property existence before modifying module.paths.

In this case, I think we can try / catch some require() statements when loading local UIs and reporters.

Hi, is there any movement around this?
At the moment this is causing an issue. I am running mocha in a bundled file (I packed mocha using rollup) to he executed in a serverless environment.
I get an error in the following snippet:
if (!process.browser) {
  var cwd = process.cwd();
  module.paths.push(cwd, path$2.join(cwd, 'node_modules')); // <= here
}

Does the serverless environment not support module.paths?
As this is marked help wanted, if a contributor can find an alternative, we’d accept a PR to address.

I take a guess: could it be empty because there's no node_modules folder?
Would bypassing that lines of code break the framework? I could help if pointed to the right direction


You need to require lodash as well.

If lodash is a dependency, it should be required by the package. This will have problems with Webpack and native ES Modules implementations that are very strict about scope.

It isn't added as a dependency in an intentional way to avoid being stuck in a specific version.
Instead, just install it
npm install lodash map-values-deep --save

The thing you are saying is an issue related to the bundle tooling, not a problem with this project itself.


add coding style paragraphs for shell scripts and markup files

As noted in #2347 and and #2411, the other significant "languages" in use in Deis are (Bourne) shell scripting and markup (Markdown and reStructuredText). We have preferences for spacing and formatting for those file types as well that we have not clarified yet, but should.

I don't think this is worth documenting actually. There aren't any overall preferences on shell spacing, and Markup is Markup.


can we auth against or integrate with SoundCloud and Vimeo?

Suggested by @ssutch in IRC.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Re-ticketed to support more ways to login for further discussion and planning. After deciding on concrete implementation plan and dev work starts, this will be reopened for tracking purpose.


Export CNN graph as JSON

is there a way to export the CNN graph using netron as Json or Panda data frame?

Duplicate of #731


Baby Bear params for benchmarking

Stark and params in the Plonky3 backend for Baby Bear after trouble with implementing generic types.

Closing as we figured out a way with generic types


Cursor pos is incorrect after deleting text in visual mode

V
select 10 lines down
d

the cursor pos should stay, but shifted by 10 lines down

should be fixed in 0.0.46


add security checks and test stages to CICD pipeline construct

Features
-Adding Security Lint option for 'add_stage()'
Relates

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Sorry, didn't notice it's a draft and that the methods to add security lint etc on the pipeline class haven't been added yet


Terminal renders extra % (percent / percentage) character on new window

Issue Type: Bug

Open a new vscode window, with no folder open
Go to explorer and select a folder to open
Terminal shows an extra % character above the initial line.

Yeah sorry, I often use them interchangeably. In this case I used folder because when VS code doesn't have a workspace open it shows an "Open Folder" button.

We often get this issue reported but I can't seem to find the original. Anyway I did find https://superuser.com/a/1391570/205226 which may help solving the issue/writing up an FAQ. I believe the issue is related to the initial dimensions being wrong sometimes and/or the fact that our resize is not synchronous (ie. block the process pipe, resize, unblock the process pipe).

I think this is fixed by https://github.com/microsoft/vscode/issues/117188

Apparently still not fixed https://github.com/microsoft/vscode/issues/122297

Oh yes, I've been seeing this a lot more often now (almost every startup), but I always just forget it's a bug and clear my terminal.

Unfortunately the SuperUser link doesn't help me. I've also been able to fix the problem by quitting and re-opening the terminal every time I open VS Code, but it's a bit annoying. What's weird too is that this issue happened for the first time a month or so ago - I never experienced it before March of this year. Perhaps something was changed recently about how the terminal is rendered that caused this issue?
At the same time that the tearing/extra %s started to happen, I also noticed a formatting issue with my PS1 where the characters don't line up properly. Restarting the terminal fixes the tearing but my PS1 just perpetually has some weird gaps that aren't present in Windows Terminal:

@ddhorstman the alignment problems are fixed in the upcoming release: https://github.com/microsoft/vscode/issues/120129

@ddhorstman the alignment problems are fixed in the upcoming release: #120129

Great! Thanks :)
As for the text rendering issues, they really come to the forefront if I turn on extensions. Here's what my screen looks like when I try to use zsh-autosuggestions in the integrated terminal:

Does this behavior provide any more insight into the underlying issue?

@ddhorstman that's probably the local echo feature, it will probably go away when you set:
"terminal.integrated.localEchoLatencyThreshold": -1

@ddhorstman that's probably the local echo feature, it should go away when you set:
"terminal.integrated.localEchoLatencyThreshold": -1

That did it, thanks @Tyriar!

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.
Happy Coding!


Create tecnm.txt

the email domain is
@tecnm.mx
the university official website URL
http://www.tecnm.mx/
a URL of a page on the official website where a long-term (>1 year) IT related course is offered by the university
http://www.tecnm.mx/licenciatura_2009_2010/ingenieria-en-sistemas-computacionales
http://www.tecnm.mx/images/areas/docencia/licenciatura_2009_2010/noviembre2012/Reticula_Ingenieria_en_Sistemas_Computacionales_ISIC-2010-224.pdf
a URL of a page or some other proof (.pdf or a screenshot are OK) showing that the university recognizes the domain which you are submitting as an official email domain for the enrolled students. In this case faculty staff
http://intranet.dgest.gob.mx/telecom/directorio/
-Under "Seleccione un filtro para el tipo de Institución" choose "Dirección General"
-Under "Seleccione el Área que desea que se muestre" choose "TecNM"
-You can verify the email domain by clicking over any "contactar" registry, under the "email" column.

file.zip
tecnm.txt

@jcarlosfelix This organization's email domain is known to JetBrains and it is in the repository already. I close this request without merging as a duplicate. If you have any issues with requesting free licenses using email addresses in this domain, please email<EMAIL_ADDRESS>Thank you.


Action rules not applied to all listeners.

My ALB has 2 listeners (80, 443). Added some action redirect rules but they applied only to first listener. Am I missing something? Is there a way to apply to all listeners, or be able to choose?

Hi,
What's your action configuration?
There are some hacks to make https redirection work, which basically ignore rules that cause infinite redirection

  - host: example.me
    http:
      paths:
      - path: /*
        backend:
          serviceName: exampleme-redirect-all-ssl
          servicePort: use-annotation

As I said I have 2 listeners on my alb one on 80 and one on 443. I expected when I add a rule for port for 443 port to be applied on the 443 listener, but unfortunately is applied on 80 Listener and for this reason I experience the following behavior.
https://example.me -> KO gives 404
http://example.me -> OK redirects me to the place I instructed
@M00nF1sh Appreciate any feedback.

Hi, so you want to both 80 & 443 to be redirected to somewhere(suppose it's not example.me?)
What's your exampleme-redirect-all-ssl looks like? can you paste it here(replace sensitive domain name with fake one like xxx.example.com)

@M00nF1sh I was put it there initially, but lost on some wrong editing of mine :) Sorry, fixing.

@M00nF1sh Want me to share the 80 port rule too? Is very similar with the one I shared above.

@M00nF1sh Want me to share the 80 port rule too? Is very similar with the one I shared above.

sure, the full ingress spec with sensitive information replaced will be best(so i can reproduce and fix it)

Currently i cannot reproduce the error. e.g. both
http://d560e4e0-testcase-echoserv-456e-466865106.us-west-2.elb.amazonaws.com
and https://d560e4e0-testcase-echoserv-456e-466865106.us-west-2.elb.amazonaws.com
will be redirect to https://example.com

@M00nF1sh
My full spec
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: "example-alb-ing"
  annotations:
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/load-balancer-attributes: idle_timeout.timeout_seconds=300
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80, "HTTPS": 443}]'
    alb.ingress.kubernetes.io/subnets: 'subnet-xxx1, subnet-xxx2'
    alb.ingress.kubernetes.io/security-groups: "sg-xx1, sg-xx2"
    alb.ingress.kubernetes.io/certificate-arn: xxx
    kubernetes.io/ingress.class: "alb"
    alb.ingress.kubernetes.io/actions.exampleme-redirect-slash: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTP", "Port": "80", "Host": "example.com", "Path":"/", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.exampleme-redirect-all: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTP", "Port": "80", "Host": "example.com", "Path":"/person/#{path}", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.exampleme-redirect-slash-ssl: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "Host": "example.com", "Path":"/", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.exampleme-redirect-all-ssl: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "Host": "example.com", "Path":"/person/#{path}", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.yelp-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTP", "Port": "80", "Host": "port.example.com", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.yelp-redirect-ssl: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "Host": "port.example.com", "StatusCode": "HTTP_301"}}'
  labels:
    app: example
spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /yolo1
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /static/yolo2
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /*
        backend:
          serviceName: example-backend
          servicePort: 80
  - host: yelp.example.com
    http:
      paths:
      - path: /*
        backend:
          serviceName: yelp-redirect
          servicePort: use-annotation
      - path: /*
        backend:
          serviceName: yelp-redirect-ssl
          servicePort: use-annotation
  - host: '*.example.com'
    http:
      paths:
      - path: /
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /yolo1
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /static/yolo2
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /*
        backend:
          serviceName: example-backend
          servicePort: 80
  - host: yelp.example.co.su
    http:
      paths:
      - path: /*
        backend:
          serviceName: yelp-redirect
          servicePort: use-annotation
      - path: /*
        backend:
          serviceName: yelp-redirect-ssl
          servicePort: use-annotation
  - host: example.me
    http:
      paths:
      - path: /
        backend:
          serviceName: exampleme-redirect-slash
          servicePort: use-annotation
      - path: /*
        backend:
          serviceName: exampleme-redirect-all
          servicePort: use-annotation
      - path: /
        backend:
          serviceName: exampleme-redirect-slash-ssl
          servicePort: use-annotation
      - path: /*
        backend:
          serviceName: exampleme-redirect-all-ssl
          servicePort: use-annotation

The only really obvious difference with your  spec I can notice is the following
     alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80},{"HTTPS":443}]'

Another thing that might be relevant is that I am using the 1.0-beta.7 and not the 1.0.0 version of controller, might this be the root of my problem?

@stafot
Are you tring to achieve below effect?
http://example.com to  http://another.example.com
and https://example.com to  https://another.example.com
If so, there is currently no way to achieve the above effect, since we cannot specify action/backend per listener for now.
All action/backend you specified will be applied to all listeners, except an special case that when you redirect from http to https with same domain/path, that redirect action is only applied to http listener, which is an trick to support http->https use case)

@M00nF1sh
Sorry for my late response but I was on my Christmas vacations. No the effect I want to achieve is all to redirect to https

@stafot
Hi, I believe your desired effect can be achieved by below:
The diffs from your version is

removed all your **-ssl actions.
Changed protocol from HTTP to HTTPS in your redirect actions.
I guess you misunderstood the "Protocol/Host/Port" in "RedirectConfig", it's specify "where to redirect user to" instead of "whether to redirect for current request if matching the protocol/host/port".
By default, the redirect action will be applied to all protocol/port(all listeners).

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: "example-alb-ing"
  annotations:
    kubernetes.io/ingress.class: "alb"
    alb.ingress.kubernetes.io/scheme: internet-facing
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTP":80, "HTTPS": 443}]'
    alb.ingress.kubernetes.io/certificate-arn: arn:aws:acm:us-west-2:283511030707:certificate/21e7282a-cede-42b4-a1be-b9811dde14a9
    alb.ingress.kubernetes.io/actions.exampleme-redirect-slash: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "80", "Host": "example.com", "Path":"/", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.exampleme-redirect-all: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "80", "Host": "example.com", "Path":"/person/#{path}", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.yelp-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "80", "Host": "port.example.com", "StatusCode": "HTTP_301"}}'
  labels:
    app: example
spec:
  rules:
  - host: example.com
    http:
      paths:
      - path: /
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /yolo1
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /static/yolo2
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /*
        backend:
          serviceName: example-backend
          servicePort: 80
  - host: yelp.example.com
    http:
      paths:
      - path: /*
        backend:
          serviceName: yelp-redirect
          servicePort: use-annotation
  - host: '*.example.com'
    http:
      paths:
      - path: /
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /yolo1
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /static/yolo2
        backend:
          serviceName: example-frontend
          servicePort: 80
      - path: /*
        backend:
          serviceName: example-backend
          servicePort: 80
  - host: yelp.example.co.su
    http:
      paths:
      - path: /*
        backend:
          serviceName: yelp-redirect
          servicePort: use-annotation
  - host: example.me
    http:
      paths:
      - path: /
        backend:
          serviceName: exampleme-redirect-slash
          servicePort: use-annotation
      - path: /*
        backend:
          serviceName: exampleme-redirect-all
          servicePort: use-annotation

@M00nF1sh
Thanks for your support. It almost worked the way you suggested. But I think there was a typo on your rules.
    alb.ingress.kubernetes.io/actions.exampleme-redirect-slash: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "Host": "example.com", "Path":"/", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.exampleme-redirect-all: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "Host": "example.com", "Path":"/person/#{path}", "StatusCode": "HTTP_301"}}'
    alb.ingress.kubernetes.io/actions.yelp-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "Host": "port.example.com", "StatusCode": "HTTP_301"}}'

The above syntax solve my problem and worked as expected.
Again, appreciate all your effort to debug my issue.


Calibration for LabelManager 280, 6mm tape

Hello,
Thanks again for Labelle!  It is working well on this device with the 12mm tape, but with 6mm tape, the text prints too far down and cuts off the bottom edge.
I am not entirely sure how to run the calibration on this tape, but I ran labelle --sample-pattern 64  and it gave this output:

Oh, this looks really odd. Usually the bottom edge starts with 0.
Could you please try:
labelle --sample-pattern 32
labelle --sample-pattern 34

Is this the full height of the printable area?

Hi,
Thanks for looking into this!
I should have mentioned: the widest tape the 280 can handle is a 12mm tape, and that tape works fine.  It is only the 6mm tape that is giving trouble.  The 6mm tape works from the Windows app.
Here's a photo with a bunch of samples:

From top to bottom, they are:

12mm tape with h=64 (works fine)
6mm tape with h=64 (the same sample as above)
6mm tape with h=32
6mm tape with h=34

Is that helpful?

That is very helpful, but I still don't understand what's going on. As far as I know, for all other printers we've seen the cartridge is irrelevant to the behavior of the printer. The printer just utilizes the full print head regardless of which type of tape is underneath.
Curiously the 12mm tape shows only rows 4-61, not 1-64, so there are 3 pixels missing from both the top and bottom of what would normally be a 64 pixel head.
The 6mm tape prints rows 18-47. Intriguingly this is 17 missing pixels from both the top and bottom.
@tomek-szczesny, do you have any thoughts on what could be going on with the hardware here?

Assuming that both tape sizes are centered around the same line (which we pretty much take for granted for sizes at or below 12mm) , these test prints match what we would expect from 6mm printout without bottom side padding.
Padding used to be handled by the LUT that I introduced eons ago, but can't seem to find it now in the code..
Wasn't there some discussion about removing it in favor of some other solution?
Missing pixels on 12mm printout may be related to tape quality, and width of its inking ribbon.

@tomek-szczesny sorry I think there may have been some missing context. The test pattern should not be software-clipped, so row 1 of the test pattern should always correspond to pixel 1 of the print head in the sense of the raw data that we send to the printer.
So it seems to me like the device itself is clipping the printable area which I don't think I've ever seen before. Other printers would just print those pixels outside the borders of the tape.

@maresb I forgot that test patterns are not padded, in which case these test prints are completely fine. I don't see anything suspicious about them.
All three test prints on the 6mm tape consistently have 17 dots missing on the bottom, which is what we expect.
The missing dots are a result of smaller tape, and even smaller ink ribbon.
@jgoerzen could you show us an example of a print that you attempted and was clipped from the bottom?
What brand of tape do you use?
Perhaps we just assumed too wide margins of error for this size of tape.

All three test prints on the 6mm tape consistently have 17 dots missing on the bottom, which is what we expect.
The missing dots are a result of smaller tape, and even smaller ink ribbon.

@tomek-szczesny I am confused why you expect this. My expectation based on previous experience (for example see here) is that there are no dots missing unless they physically extend past the boundary of the tape. Thus when the tape is smaller than the print head I expect no margin.

Also all the printed labels in the photo are clipped from the bottom since row 1 is missing despite that it would always fit on the tape.

Missing pixels on 12mm printout may be related to tape quality, and width of its inking ribbon.

I have tried another 12mm cartridge and got the same result.  It is possible I have a defective unit, I guess?  I tried cleaning the printhead and that made no difference.  These are Dymo D1 12mm labels, PN 1926208 as in https://www.dymo.com/labels-tapes/labelmanager-d1-tapes/dymo-d1-standard-labels-2-count/SAP_1926208.html
The 6mm cartridge is Dymo 43613 as from https://www.amazon.com/DYMO-Standard-LabelManager-cartridge-43613/dp/B000067SPT?th=1

@jgoerzen could you show us an example of a print that you attempted and was clipped from the bottom?

Here is a photo from running:
labelle --tape-size-mm 6 ABCDEFGQ
on the 6mm tape:

Okay, now I think we're discussing two different things, that's why we cannot find a common ground. :)
Indeed there is a gap between the lowermost dots and the lower edge of the printout. I think that this may be a result of either misaligned, or physically smaller ink tape inside the cartridge. @jgoerzen, could you take a look at the back side of a tape in the cartridge and see if the black ribbon isn't narrower than the tape?
What happens if you try to print text on 6mm tape, but with 12mm set in labelle?
The second issue is that the printout is too low and doesn't fit. the "ABCDEFGQ" print looks like it misses padding, which should be about 17 dots. Even if the whole tape was printable, this text wouldn't fit.

could you take a look at the back side of a tape in the cartridge and see if the black ribbon isn't narrower than the tape?

Ohhhh, yes, that could explain it perfectly! I'm very curious now.

I have a faint recall of this happening to someone in the past. I looked my only original Dymo cartridge and it doesn't seem to display such property.

could you take a look at the back side of a tape in the cartridge and see if the black ribbon isn't narrower than the tape?

Interesting!
On the 6mm cartridge, the black ribbon is wider than the tape.
On the 12mm cartridge, the black ribbon is narrower than the tape.
This may explain the missing top/bottom pixels on the 12mm test image, I guess.  But the black ribbon is actually wider than the 6mm tape.
Here is a photo from a 6mm cartridge with labelle --tape-size-mm 12 ABCDEFGQ:

Now things get super weird. There seemingly is no physical limitation for printing across the full width of a 6mm tape, and yet, no matter what you do the edges remain blank.
I just googled LabelManager 280 and it's a hand held that you connect to a PC through USB, correct?
Then I suppose it is aware of the tape size because it asks the user about it after the lid is closed (at least my model 160 does that).
If this is true, then it may do some internal padding and cropping magic on its own. Our desktop label managers don't know what tape size they're dealing with, which made things easier for us.
I wonder if you could do the following and see if it works: Put 6mm cartridge, but tell the printer it's actually 12mm. If my line of thought is correct then this should work.

So I put in the 6mm cartridge, told the printer it was 12mm, and told labelle it was 6mm.  The text moved up a bit -- an improvement -- but not enough:

Now things get super weird. There seemingly is no physical limitation for printing across the full width of a 6mm tape, and yet, no matter what you do the edges remain blank.

Now we're on the same page about this. :smiley:

Put 6mm cartridge, but tell the printer it's actually 12mm.

Another brilliant idea, thanks @tomek-szczesny! And it looked to me like it worked, since it now goes to the lower edge!
@jgoerzen, could you please use the following command for the test pattern from now on?
labelle --sample-pattern 34

I'm pretty sure that will reach the upper edge of the 6mm tape and we'll be good on that.
The margins on the 12mm tape are still a mystery to me though.

OK, with the 6mm tape loaded, device set to 12mm, here are the 34 and 64 sample patterns:

Thanks for your help and patience, @jgoerzen.
Now when we understand what is going on, we've got to decide on the solution to this problem.
The users will expect Labelle to work correctly with 6mm tape and the printer configured to 6mm. We can make this work through LUT or whatever we have right now, but with a big margin imposed by the printer's firmware.
Or we can instruct the users to putposefully misconfigure their devices and allow them to print larger content. Personally I don't like this idea at all.
I expected the 12mm mode to work correctly though, I'm not sure why it doesn't.
At the moment I'm taking care of my cat that had a surgery today so I can't inspect the samples more carefully.

Awesome!!! The 6mm tape corresponds to rows 10-51. :heavy_check_mark: Now it's possible to handle this correctly with offsets.
@jgoerzen, no need to print any more size 34 sample patterns.
The only major remaining mystery is the 3 missing pixels on each side for the 12mm tape.

The only major remaining mystery is the 3 missing pixels on each side for the 12mm tape.

John said that the inking ribbon is narrower than the tape, I would blame that.

Awesome!!! The 6mm tape corresponds to rows 10-51. ✔ Now it's possible to handle this correctly with offsets.

If the printer is misconfigured to our advantage. Like I said I wouldn't want us to support this mode of operation, because it breaks compatibility with the official software and handheld operation of the device.
I believe we should stick to the capabilities offered by the device when it is configured properly, even if it means limited dot range.
This means different range and offsets for this particular printer model... Like I said before, I didn't find my LUT in the code, so I don't know how to handle that.

For reference, here's a photo of the tape in my 12mm cartridge:

Due to perspective and the black tape not being flush against the white tape, the gap looks much bigger than it is. It is actually roughly 0.5mm on each side, which is way smaller than the margin on the 12mm tape pictured above. Moreover, I have always been able to use the full 64 pixels of my LabelManager PnP print head.
@jgoerzen, in your 12mm printer cartridge, where the black ribbon is narrower than the tape: how does the width of the black ribbon compare with the printable height?
If the black ribbon is bigger than the printable area (like if it's within 1mm of each edge of the white tape), then the black ribbon is not the limiting factor.
If the black ribbon does coincide with the printable area, then we have different types of 12mm D1 cartridges and mine is not like @jgoerzen's.

If not the tape limitations, this might as well be another restriction imposed by LM260 firmware. Nothing we can deal with I'm afraid.

Like I said I wouldn't want us to support this mode of operation, because it breaks compatibility with the official software and handheld operation of the device.
I believe we should stick to the capabilities offered by the device when it is configured properly, even if it means limited dot range.

Further commenting on that, unless we find a way to read and write printer's settings through USB to hack our way around their cropping habits. That would improve the situation for tapes under 12mm at least.

Why not offer the option to access unsupported operation? For me this stuff is about giving people full access to the hardware, regardless of artificial restrictions imposed by the manufacturer.
BTW your LUT is here: https://github.com/computerlyrik/dymoprint/pull/91/files
We couldn't merge it because the code was too flaky to get it to work correctly. The code is less flaky, but still not ready to merge. There's an independent attempt at implementing a LUT in #65 but it still needs more work, started in #66, to avoid breaking stuff.

I believe we should stick to the capabilities offered by the device when it is configured properly, even if it means limited dot range.

I should note that, with the 6mm tape, the Windows software prints correctly.
In an ideal world, yes, having Labelle work with the device set to 6mm mode would be best...  but I can live with whatever works, if it's documented.  Who am I to argue with some great Free Software? :-)

The only major remaining mystery is the 3 missing pixels on each side for the 12mm tape.

To be clear, I have no complaints about the 12mm mode with Labelle.  Dymo's Windows software, in its default configuration, is cutting off on the top and the bottom in 12mm mode.  Labelle isn't!  Maybe it's just because fonts and QR code are different sizes by default, but in any case, I'm not having problems with the 12mm mode.

@jgoerzen, in your 12mm printer cartridge, where the black ribbon is narrower than the tape: how does the width of the black ribbon compare with the printable height?

I believe the black ribbon is indeed wider than the printable height.

If not the tape limitations, this might as well be another restriction imposed by LM260 firmware

I have a 420P on order and can test with it.  I'll have a few days to test with them both side-by-side, so hopefully that will be enough to narrow down all of these and make both work (I note some similar conversation about it in #62)
Thanks again!

I have swapped the 280 for a second one, in case mine was faulty.  The result from it seems to be the same.
I also have a 420P to test with (I will need to return one of the 280 or the 420P to the shop soon).  I did a test with it as you can see.  It looks to me that the 280 is unable to use the full width of the 12mm tape.  Maybe that is really a 9mm printhead?
Here is a photo with both, with the 280 on top:

I'll try to summarize my current beliefs on this topic, although to keep it brief I'll omit some explanation.
Even though the print related hardware between all mentioned Dymo models is largely the same (because they work with the same tape family D1), I think that 260P has limitations imposed by firmware or Windows software, or a combination of both.
PnP has 64-dot print head, or so we think as of today. I suspect that 260P has the same print head, because developing a slightly narrower model doesn't make much sense. Also our tests indicate that the print head is the same, because they accept data formatted the same way we send to PnP. I bet it's the firmware that crops away unwanted data. This is possible just because this printer IS aware of the tape size (provided by the user).
420P has larger 128-dot print head to support 19mm tapes. It also seems to have firmware level cropping mechanisms, as seen on the h=130 test print seen above. There are many possible explanations why this model allows for more content on 12mm tape. It could have been developed by a separate team that made different engineering decisions. It might have been a marketing decision to limit capabilities of 260P to justify higher price of other models - it's a standard practice these days.
To me it is clear that we cannot expect the users to use any of these printers with wrong settings to work around the firmware limitations. When the user unplugs the USB and goes into the field, they will have to reconfigure their printer each time.
Passing instructions to the user will be troublesome as well. How would they be supposed to know they should misconfigure their device to get Labelle to work?
The user will still be able to perform the same trick at their own discretion even if Labelle won't support it directly.
Based on all test prints collected above, we can figure out LUT values to support these printers. In other Issue someone had already posted a test pattern on a 19mm tape.

I also just bought some 9mm tape to test with this.  Results are encouraging.  Here's the calibration:

When I leave Labelle at the default 12mm mode, it prints fine, though a little off-center towards the top.  In 9mm mode, it prints off center towards the bottom, enough that it crops off a bit of the bottom.  Both are with the labeler in 9mm mode.
Thanks again!

@maresb, perhaps we should just let the users use custom offsets that override the built in ones, as a command line flag and GUI "advanced" option? Then more determined users could experiment on their own. :)

@maresb, perhaps we should just let the users use custom offsets that override the built in ones, as a command line flag and GUI "advanced" option? Then more determined users could experiment on their own. :)

Maybe have some sort of interactive calibration process, to guide users. It will print a sample, ask you which rows you see, what is the top and bottom gaps, etc., then it will print again, until the sample would align perfectly.
Could you write a document about this process, and I'll try to write such wizard?

You got it, @tomers!
I created a new branch with my vision of the calibration wizard workflow.
Feel free to take over this branch.
All comments are welcome, especially correcting my inevitable grammar errors in the messages for the user.
https://github.com/labelle-org/labelle/blob/calib_wizard/doc/calibration-wizard.md

Curiously the 12mm tape shows only rows 4-61, not 1-64, so there are 3 pixels missing from both the top and bottom of what would normally be a 64 pixel head.

My 280 does the same thing on 12mm tape. How sure are we that it's supposed to be capable of 0.35" print height (64 pixels @180dpi)?
Additional measurements from my 280:

Printing from the printer itself, max print height is 1/4" on a 1/2" (12mm) tape.
Printing via labelle, max height print height is 5/16" (on a 1/2" (12mm) tape).

Looks like the official dymo cups driver PPD for the 280 sets the max height to exactly 58 pixels. Probably not a coincidence.
Spec from PPD:
*ImageableArea w35h4000/12 mm (1/2") Continuous: "5.60 30.00 28.80 3970.00"
...
*DefaultResolution: 180dpi

Math:
(<right margin> - <left margin> / <points per inch>) * <DPI>

((28.8-5.6)/72)*180 = 58

Thanks a lot @ccdunder! That's a great idea to look in the PPDs. It's great to have confirmation that it's an apparent limitation. I didn't know the meanings of those numbers, so showing your math was extremely helpful!
The biggest obstacle at the moment is that we're working on a legacy codebase and we don't have the abstractions in place to support margins in a coherent way. There are intermittent efforts at getting there, currently contained in #82 and #65.


RPC E2E test for Futurenet

Conduct CLI end to end testing for the core soroban support against Futurenet.
(This is an analog to https://github.com/stellar/go/issues/4623 for Futurenet)
Sub tasks :

[x] Run the existing integration tests against the updated quickstart docker to see if any breaking changes were introduced.
https://github.com/stellar/go/issues/4647
[x] Use the CLI to deploy contract.
https://github.com/stellar/go/issues/4648

Use Soroban Examples, Hello world : sample from soroban-example, addi32 contract

[ ] Invoke a contract using JS
https://github.com/stellar/go/issues/4649
[x] Invoke a contract using Soroban CLI
https://github.com/stellar/go/issues/4650
[x] Use the CLI to create token
https://github.com/stellar/go/issues/4651

for anyone doing e2e tasks against futurenet, the soroban docker image of quickstart to run for this is:
docker pull stellar stellar/quickstart:pr-373-soroban-dev
docker run --platform linux/amd64 --rm -it -p "8000:8000" --name stellar stellar stellar/quickstart:pr-373-soroban-dev --futurenet --enable-soroban-rpc --protocol-version 20

any test must create a new account on Futurenet first to use as source account:

First generate a KeyPair using Laboratory's page and save the pub/private key - https://laboratory.stellar.org/#account-creator
curl --location --request GET 'https://friendbot-futurenet.stellar.org?addr=<pub key>'

for reference on hosted futurenet deployment configuration, here is the ops ticket that performed it - https://github.com/stellar/ops/issues/1832
soroban-rpc service URL entrypoint will be reachable from the locally run container at:
http://localhost:8000/soroban/rpc
Quickstart soroban dev readme

@jcx120 , after fix to horizon ingestion https://github.com/stellar/go/pull/4653 was pushed, I reran these futurenet tests, and they passed, steps to reproduce each test are on the sub-tickets. the only one I didn't retest was #4649 for 'invoke contract using JS on futurenet'  as it's more complex, left comment


Show banner on scale page with last scale operation info

Before any scale operations have been created:

While a scale operation is in progress:

Scale operation succeeded:

TODO:

[x] Periodically fetch operations for the service to keep the banner up-to-date

This is almost perfect, only note i have is to use our pretty UTC date formatter to remove the TZ letters from the timestamps:
import { prettyDateTime } from "@app/date";

@joeclayallday I noticed that the height of the banner changes between progress and info because the LoadingSpinner defaults to the sm icon variant whereas icons normally default to the base variant. It was bothering me so I overrode the variant to base in Banner in order to keep the height the same. Let me know if you want me to change that back.

https://app.shortcut.com/aptible/story/21535/adjust-test-order-grouping-to-improve-the-stability-of-tests

@joshraker Banner icon changes look good! Thanks


Make assertion logging for compairsons more helpful?

This may not even be possible at the screenpy level and perhaps it's something we pass along to hamcrest.....
It sure would be nice if the failed assert comparing two strings would line up the strings to make it easier to identify where the difference lies.
Here is a current example of two large strings that do not match.
AssertionError:
Expected: a string containing 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'
     but: was 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\neditable category\nEdit\nACTIVE'

It'd be nice if it looked something more like this:
AssertionError:
Expected: 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'
     got: 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\neditable category\nEdit\nACTIVE'
          ^ line up here

Ironically, the "current example" was easier for me to find the error in because the substring was closer to the almost-matching substring in the non-matching string. But i do get what you're getting at.
Removing the "a string containing" part of the failed assertion message will lose valuable information, though. In your changed example, i would assume we were looking for an exact match.
You're right, we'd probably have to make that change in Hamcrest, or make custom versions of all of the matchers we want this to affect. Then we could sub in the changed mismatch string, maybe just have the objects under test on their own lines?
AssertionError:
Expected: a string containing
        'Category Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'
     but: was
         'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\neditable category\nEdit\nACTIVE'

I updated the example to illustrate a little better.

Or something like this:
AssertionError:
Expected: a string containing 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'
     but: was actually this   'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\neditable category\nEdit\nACTIVE'
                              ^ line up here

I would guess two lines might be a better solution though.

Maybe for strings we could make something even more tester-friendly and use ndiff?
That could produce output like this:
AssertionError:
    Expected: a string containing 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'
     but: was

Ironically, the "current example" was easier for me to find the error in because the substring was closer to the almost-matching substring in the non-matching string. But i do get what you're getting at.

Removing the "a string containing" part of the failed assertion message will lose valuable information, though. In your changed example, i would assume we were looking for an exact match.

You're right, we'd probably have to make that change in Hamcrest, or make custom versions of all of the matchers we want this to affect. Then we could sub in the changed mismatch string, maybe just have the objects under test on their own lines?

AssertionError:
Expected: a string containing
        'Category Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'
     but: was 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\neditable category\nEdit\nACTIVE'
         which has: editable category
         instead of: Job Category to be edited

This is what i did:
>>> ndiff('editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\nJob Category to be edited\nEdit\nACTIVE'.splitlines(keepends=True), 'editable category\nCategory Code: EDITCAT\nClass Type:\nClass Code:\nDescription:\nIndirect\nEDITCLASS\neditable category\nEdit\nACTIVE'.splitlines(keepends=True))
<generator object Differ.compare at 0x105269f80>
>>> [x for x in _]
['  editable category\n', '  Category Code: EDITCAT\n', '  Class Type:\n', '  Class Code:\n', '  Description:\n', '  Indirect\n', '  EDITCLASS\n', '- Job Category to be edited\n', '+ editable category\n', '  Edit\n', '  ACTIVE']

We could then check which entries in the diff results start with + and - and use that information to fill out the "which had" and "instead of" lines, respectively.

Using diff tools can be really tricky depending on the differences especially when it comes to patterns etc.  I started to suggest we opt for displaying the visual differences to avoid possible confusion, but I got to wondering if this is something that should be able to customize to their need?

Users can already customize it to their need by doing the exact thing that i'm suggesting we do, haha. :P

I submitted a ticket to hamcrest: https://github.com/hamcrest/PyHamcrest/issues/235

Since we've got the issue open in PyHamcrest, i'll close this one here. They have it marked as a "good first issue," maybe i'll take it on or something!


Can't see "dot"

Using the code as it is from demo example, I am unable to see the dots.
var Swiper = require('react-native-swiper');
...
       <Swiper style={styles.wrapper} showsButtons={false} loop={ false } showsPagination={ true } >
          <View style={styles.slide1}>
            <Text style={styles.text}>Hello Swiper</Text>
          </View>
          <View style={styles.slide2}>
            <Text style={styles.text}>Beautiful</Text>
          </View>
          <View style={styles.slide3}>
            <Text style={styles.text}>And simple</Text>
          </View>
      </Swiper>
...
// Stylesheet
 wrapper: {
    height: 90,
  },
  slide1: {
    height: 90,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#9DD6EB',
  },
  slide2: {
    height: 90,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#97CAE5',
  },
  slide3: {
    height: 90,
    justifyContent: 'center',
    alignItems: 'center',
    backgroundColor: '#92BBD9',
  },
  text: {
    color: '#fff',
    fontSize: 30,
    fontWeight: 'bold',
  }

Am I missing something?

I figured out that the "dot" is visible when the swiper is in fullscreen mode. (flex: 1), however, if I set the height of swiper and it's parent container manually, the dots do not appear.

You have to send height as a property. not as a style property.
Look at line 50 on https://github.com/leecade/react-native-swiper/blob/master/examples/examples/swiper.js

Thanks, it worked.


Add unsafe constructor for AnyPin

Fixes: https://github.com/embassy-rs/embassy/issues/2577

can you rustfmt?

Rust analyzer wasn't working on my fork :(. Fixed the formatting


[Contextual Cursor] override default OS cursor

This issue is for the external plugin: Contextual Cursor
An option to override the default OS cursor with a more fitting one. Currently the plugin only overrides on interaction options, so it keeps changing between my windows cursor and a contextual one.
The Rs3 Gold cursor from the Custom Cursor plugin might fit better.

Custom Cursor support was added in 1.2


Add MSK Connect support

I would be good to have support for AWS MSK. Cloudformation template

Thanks for the issue. Added via a19fb78a9016b99d1e0d623e2a682eb6f37ee507.

@markpeek thanks :), do you know when new version of troposphere will be released.


[ERROR] No matches for kind "Deployment"

Hi there,
I'm trying to follow the repository tutorial, but I received this error:
service/static-example-service created
error: unable to recognize "/home/runner/work/example-doctl-action/example-doctl-action/config/deployment.yml": no matches for kind "Deployment" in version "apps/v1beta1"
##[error]Process completed with exit code 1.

Could you guys help me?

Unfortunately, in Kubernetes 1.16, the Deployments API changed so there are some differences in what the config should look like. This example is running on a previous version. We should flesh out the README with more docs around this.
I've tested these changes on a 1.16.6 cluster:
-apiVersion: apps/v1beta1
+apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: static-example
+  labels:
+    app: static-example
 spec:
   replicas: 1
+  selector:
+    matchLabels:
+      app: static-example

Check out these docs for more details:
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#creating-a-deployment

Thanks @andrewsomething, It solved my problem.


0.3.7 fails to compile with PGI 19.4

After adding HOSTCC=cc I was able to build 0.3.7 with PGI version 18.10.  However, for PGI version 19.4, the build fails with compiler error:
pgcc -c -O2 -DMAX_STACK_ALLOC=2048 -mp -tp p7-64 -DF_INTERFACE_PGI -fPIC -DNO_AVX512 -DSMP_SERVER -DUSE_OPENMP -DNO_WARMUP -DMAX_CPU_NUMBER=80 -DMAX_PARALLEL_NUMBER=1 -DVERSION=\"0.3.7\" -DASMNAME=drot_k -DASMFNAME=drot_k_ -DNAME=drot_k_ -DCNAME=drot_k -DCHAR_NAME=\"drot_k_\" -DCHAR_CNAME=\"drot_k\" -DNO_AFFINITY -I.. -DDOUBLE  -UCOMPLEX -UCOMPLEX -UCOMPLEX -DDOUBLE  ../kernel/x86_64/rot_sse2.S -o drot_k.o
PGC-F-0249-#error --  "MMX instruction set not enabled" (/apps/pgi/linux86-64-llvm/19.4/include/pgi/mmintrin.h: 27)
PGC/x86-64 Linux 19.4-0: compilation aborted
make[1]: *** [sgemm_oncopy.o] Error 2
make[1]: *** Waiting for unfinished jobs....
PGC-F-0249-#error --  "MMX instruction set not enabled" (/apps/pgi/linux86-64-llvm/19.4/include/pgi/mmintrin.h: 27)
PGC/x86-64 Linux 19.4-0: compilation aborted
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/amax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/amax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/iamax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/amax_sse2.S: -1)
make[1]: *** [sgemm_beta.o] Error 2
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/amax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/copy_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/iamax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/iamax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/iamax_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/rot_sse2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/nrm2.S: -1)
PREPRO-I-0222-Redundant definition for symbol __extension__ (../kernel/x86_64/asum_sse2.S: -1)
make[1]: Leaving directory `/path/to/OpenBLAS/0.3.7/pgi/19.4/kernel'
make: *** [libs] Error 1

My build command was:
make USE_OPENMP=1 CC=pgcc CXX=pgc++ FC=pgfortran F90=pgfortran F77=pgfortran HOSTCC=cc

Any hints would be appreciated.

Apparently it needs different instruction sets enabled in the way different from gcc and clang
Here is the list in whole:
https://gcc.gnu.org/onlinedocs/gcc-9.2.0/gcc/x86-Options.html#index-mmmx

I've tried forcing builds with -Mvect=simd and -tp skylake -fastsse.  No luck.  I did find this somewhat related post in a PGI forum:
https://www.pgroup.com/userforum/viewtopic.php?t=6686&p=25800

Thats MMX missing (Actually from filename - SSE2 that every AMD64/x86_64 supports)
Since documentation is not public - ask their support what to do with that error. Sort of source file with full command is in your hands.

You need to build OpenBLAS  with the "nollvm"  version of PGI at least for now - seems the llvm-based one does not handle the full power8 instruction set

See also #2217

You need to build OpenBLAS with the "nollvm" version of PGI at least for now - seems the llvm-based one does not handle the full power8 instruction set

Unfortunately, the PGI compilers for POWER are LLVM-only.  There is no "nollvm" variant for POWER, only x86_64.

sorry for any confusion - the "power8" probably crept in as I had just read a comment related to build trsting on that architecture, this should obviously have been x86_64 above

I have filed a bug on the PGI compilers for this particular issue, as I can reproduce it here.
Note that this issue even exists with 18.10, but you did not notice it there, as 18.10 was the last version of PGI in which the "nollvm" compilers were the default on x86_64.  If you explicitly use the 18.10 "llvm" compilers instead, you will likely see this same issue there, as well.

Just spoke a developer, who fixed the issue internally last week.  Fix should appear in an upcoming PGI release very soon.

Thank you all for your assistance.  I will try out the "nollvm" version and let you know how it goes.  Glad to hear a fix from PGI is on the way.

Error 0249 should go to PGI. Absent MMX in cone without any MMX is sort of dead end.

Sorry, I cannot reproduce my "assumed" earlier success with the changes from #2219 either, seems I had some ugly hack in place. :-(
While I assume that the "MMX not enabled" thing is what cparrott73 already reported to PGI, a sufficient workaround appears to be to add -D__MMX__  to the PGI defines in Makefile.system.
(And I also found out that my recent zdot.c "improvement" from #2222 does not work with PGI - nor the Sun compiler - due to their implementations of the CREAL and CIMAG macros. Luckily this only affects the current develop branch and not 0.3.7...)

NB the "llvm" build still fails at compiling files like dscal_microk_haswell-2.c as it mishandles some inline assembly: it substitutes "%dl" in instructions like " "vmovups        %%xmm5  ,-112(%1) " and subsequently complains that "-112(%dl)" is an "invalid base+offset expression".

Also, the SkylakeX checks currently in OpenBLAS are gcc-centric (which is why your log snippet shows "-DNO_AVX512" which will make this a "Haswell" build). I have patches for this, but AVX512 support in 19.4 appears to be very sketchy anyway - I get "illegal use of symbol, __m512" when I try to compile the SkylakeX SGEMM kernel with it. (see also https://www.pgroup.com/userforum/viewtopic.php?t=6686)

FYI - the "instruction set not enabled" error should now be fixed as of the PGI 19.9 release.  If you are using the PGI CE, the fix should be available when the PGI 19.10 CE is released.

I see that PGI Community Edition 19.10 was released yesterday, so this issue should now be resolved for all users.


Serde development blog

From @erickt in #483:

think it'd be worthwhile starting a proper serde development blog? Talking about the json benchmarking could be nice, and if we want to talk through our thought process developing some feature.

I am not much of a blogger myself but I could chip in. For now I would prefer to focus on improving our existing web presence (readme and rustdoc) before investing in another.

I am not planning to pursue this.