More Sections added

Pull Request: Addition of Top Deals and Discount Deals Sections
Description
This PR adds more content to the Flipkart clone project, specifically adding sections for Top Deals and Discount Deals. The Top Deals section showcases featured products with significant discounts, while the Discount Deals section highlights ongoing promotions and discounts across various product categories.
Changes Made

Added HTML and CSS for the Top Deals section
Added HTML and CSS for the Discount Deals section
Updated the main HTML file to include the new sections
Added corresponding images for the new deals sections
Updated styling to ensure consistency with the existing design

Screenshots:

Checklist

[x] Tested locally to ensure the new sections display correctly
[x] Ensured the code follows best practices and is properly commented
[x] Updated documentation and comments to reflect the changes made
[x] Ensured compatibility with different screen sizes and browsers

Additional Notes
This PR is under GSSOC'24
Resolving Issue
#295
How to Test

Checkout this branch locally.
Run the application and navigate to the corresponding sections to view the new Top Deals and Discount Deals.
Verify that the layout is responsive and displays correctly on different devices.
Check for any rendering issues or inconsistencies in styling.

@arghadipmanna101 sir please merge and close the issue #295


Wrong Rigidbody collision behaviour (3.0.3 rc1)

Godot version:
3.0.3 rc1
OS/device including version:
Various Windows versions - the bug doesn't happen on Linux.
Issue description:
3.0.3 rc1 on Windows breaks the Rigibody collisions in my game. Instead of bouncing off a StaticBody, they "slide" along them, sometimes disappearing in or passing through other bodies:

This never happened in 3.0.2. And probably the weirdest thing: The issues seems to be Windows-specific, because it works just fine on Linux (same Godot version, same PC)

@AndreaCatania

Does this happen with the 32bit Windows build?

I've just checked, and it doesn't happen. The issue is limited to the 64 bit Windows build.

3.0.3-rc2 is out. Could you please try with this release? I can't reproduce it here on wine with this build nor on Windows with mesa software renderer.

I did a quick test with Wine and I'm getting the same with rc2. The 32 bit version is fine, but the 64 bit Windows build has this strange bug.

This is indeed very strange. I can't reproduce it at all. This is a video of the 32bit and 64bit windows versions on wine and the native 64bit linux version:

Could this be some Nvidia driver issue perhaps?

I have one more idea, could you please try this binary? https://tmm.cx/nextcloud/s/SgT2ymq2NqYCw6J/download?path=%2F&files=Godot_v3.0.3-rc2_win64.exe.zip

I was able to reproduce it actually, I must have done something wrong previously. Here you see the bug with the released binary but not with the above binary:

This means the problem is caused by the Microsoft compiler in LTO mode. For 3.0.3 I'll disable LTO for the Windows builds again and do a proper benchmark between a non-LTO MSVC build vs an LTO Ming-w64 build for 3.0.4.
Can you please verify that with the above binary the problem is gone for you also?

Yes, I can confirm that the non-LTO build works fine.

I've tried it in a LTO build with windows 64 and it works fine.
@ProbDenis Can you please send me the command that are you using to build it? (The one where you have the error)
Thanks you

I haven't built it. We got the bug with the official 3.0.3 builds (rc1 and rc2).

@AndreaCatania
call "C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\VC\Auxiliary\Build\vcvarsall.bat" amd64 10.0.16299.0
call scons -j8 verbose=no warnings=no progress=no platform=windows builtin_libpng=yes builtin_openssl=yes builtin_zlib=yes gdnative_wrapper=yes debug_symbols=no tools=yes target=release_debug use_lto=yes

Fixed by switching to mingw + lto on 3.0 at least.

What's the state of this issue?

Switching to mingw seems to have fixed the issue. We need to go this anyway for the mono builds. I'm closing this.


Missing upgrade / migration guide for v1.28.0

What is the URL of the document?
https://sdk.operatorframework.io/docs/upgrading-sdk-version/
https://sdk.operatorframework.io/docs/upgrading-sdk-version/v1.28.0/ <-- doesn't exist
Which section(s) is the issue in?
v1.28.0 - missing
What needs fixing?
There is no v1.28.0 upgrade / migration guide.
Additional context
All other versions, even when no migrations are needed, are accounted for on this page. v1.28.0 has notable changes with controller-runtime etc. so I'd expect at least some content to exist here, but there is no guide for this version.

@aharbis Thanks for raising this issue!
So it looks like everything was done correctly for the v1.28.0 release but our Netlify deployment failed for the release. Looking into it now.

Kicked the Netlify deployment process off again and it succeeded. I was able to see the v1.28.0 migration guide live now.
Closing this issue since it should be resolved, but feel free to reopen if you are still encountering this issue.

Thanks for the quick fix!


Question: Leaflet 1.7.1 support (or any higher versions than 1.0.3)

First of all, thank you for this wonderful package which enables the use of different projections in Leaflet.
Right now Proj4Leaflet uses Leaflet 1.0.3.
Will there be any updates for a Leaflet 1.7.1 support or any newer Leaflet versions?
Or is this project terminated and only usable with Leaflet 1.0.3?
I am using Leaflet 1.7.1 for several projects and step down to an older version for different Packages like Proj4Leaflet.
Happy for any answers and information!
Thank you

To my knowledge, proj4leaflet works with latest Leaflet as well. Don't remember the exact latest version I've used it with, but definitely much later than 1.0.3, it's just that the examples aren't updated.

To my knowledge, proj4leaflet works with latest Leaflet as well. Don't remember the exact latest version I've used it with, but definitely much later than 1.0.3, it's just that the examples aren't updated.


client certificate auth via common name

This is an initial proof of concept for implementing authentication using the common name on client certificates, as opposed to the current scheme which requires client certificates in conjunction with http basic authentication.
This is similar to the way kubernetes implements client authentication, using the common name on client certificates as a username.
There are two commits, the first is a small refactor to centralize the existing basic auth code, and the second is an initial implementation of pulling the client username from the certificate.
The approach looks like this:

if an Authorization header exists on the request, do not check the certificate. proceed normally and check credentials.
if the Authorization header is missing, attempt to extract the common name from the presented certificate and authenticate as the specified user (even if the user account specifies a password, the client certificate will bypass that and authenticate)

Wanted to get a bit of review and see if this was something you'd be interested in merging, if so, some considerations before merging..

gate with a flag (it should be entirely backward compatible, so not sure if that's necessary)
re-validate the certificate with the ca during authentication? (the authentication code uses the tls sessions validated chains, so as long as the tls config is set up with the ca properly, this should be unnecessary)
limit user accounts that are accessible via client cert, and/or review the interop with basic auth
documentation

Also need to consider how this will interact with proxy, which terminates the tls connection with the client and makes its own connection using different certs to the server.

re-validate the certificate with the ca during authentication? (the authentication code uses the tls sessions validated chains, so as long as the tls config is set up with the ca properly, this should be unnecessary)

Can you explain this further? I don't follow.
Otherwise this seems good.

@philips sure.
Here I'm using the tls sessions's VerifiedChains, as opposed to PeerCertificates. The verified chains are the result of verification of the supplied peer certificates, verified by the tls transport. I'm making the assumption that we want to use the same verify options for authentication as are being used by the tls server to accept client certificates.
If, for example, we want to verify a specific key usage to allow client auth by common name to continue, we'd have to verify the certificates again in this block using the new VerifyOptions.
Since etcd is already accepting options at the server level to determine client certificate trust, I thought it made sense to piggy back on that rather than accepting (yet another) set of certificate validation flags.

@philips What are your thoughts on proxy authentication? right now this will not pass the user's certificate from the proxy back to the etcd cluster, so the proxy will be authenticated, not the user. Maybe that's acceptable if you assume etcd-proxy as a single tenant proxy, but with multiple consumers of a proxy they are all effectively sharing credentials.

@roboll I think we need to change the proxy to be a L3 proxy. @xiang90 do we have an issue for this yet?

Is there a reason this never got merged? etcd authz is basically broken right now since most applications can't tolerate the 100ms+ latency hit per request. This would very easily solve that issue and enable people to actually use etcd authz.

@roboll @ghodss Sorry! We did not pay a lot attention to the v2 auth thing.
/cc @mitake Can you take a look at this pull request?

@xiang90 @ghodss @roboll  sure, I'll look at it today. But this PR needs huge rebase. So I'd like to review the concept.

@roboll @ghodss @xiang90 the concept seems good to me. I think it can be merged after rebasing. The rebasing would be big but straightforward.
And I'm not sure how the problem of proxy is serious. Just making this feature and proxy mutually exclusive functionalities might be enough, I think. IIUC, v2 proxy is only for easy discovery so giving up the proxy would be not so serious for users who want this feature.

Great to hear, @mitake. Is there any difference in how etcdv2 and etcdv3 handle authentication?

@ghodss yes, there is a big difference. For example, bcrypt password checking is required only when a client connects to servers. So I believe the 100ms+ latency per request can be avoided.

Got it. In any case it would be great to avoid it altogether and enable us to not have to distribute passwords either.

@ghodss hashed password is replicated to every node of the cluster. Is this problem for you? It is required for enabling authentication on all nodes.

That's fine - I meant more distributing the passwords to the etcd clients, and relying on common name instead.

@ghodss ah I see. v3 authentication doesn't support the auth based on common name yet. It would be worth to consider.

@gyuho Can you try to cherry pick this patch set and resolve the conflicts?

Closing in preference to https://github.com/coreos/etcd/pull/5991/.

is there any document on how to use this feature?

@qiujian16 I'll add docs related to auth features. The issue is here: https://github.com/coreos/etcd/issues/7251
I'm finishing jwt token support for now. After it, I'll work on the doc.


Automated cherry pick of #1593: fix: image quota rpc support action and cascade params

Cherry pick of #1593 on release/2.10.0.
#1593: fix: image quota rpc support action and cascade params

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.10.0@b562e99). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release/2.10.0   #1594   +/-   ##
================================================
  Coverage                  ?   7.72%
================================================
  Files                     ?     409
  Lines                     ?   62372
  Branches                  ?       0
================================================
  Hits                      ?    4818
  Misses                    ?   57146
  Partials                  ?     408

Flag
Coverage Δ

#aFlag
7.72% <ø> (?)

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 b562e99...77eb9ee. Read the comment docs.

/lgtm
/approve


⚠ Jenkins Plugins Artifactory has degraded performance

In 90ef44c, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1550 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 5ce0822.


No unit tests

We need some, especially on the CLI part.

We have a lot of specific string parsing/comparison in DebugRelay Python code, definitely need unit tests for those.


Uncaught TypeError: Failed to resolve module specifier "react". Relative references must start with either "/", "./", or "../".

Describe the bug
Uncaught TypeError: Failed to resolve module specifier "react". Relative references must start with either "/", "./", or "../".

感谢帮忙🙏
Reproduction
https://github.com/Jairwin-L/ant-mobile-demo
System Info
{
  "name": "vite-demo",
  "version": "0.0.0",
  "scripts": {
    "dev": "vite",
    "build": "tsc && vite build",
    "serve": "vite preview"
  },
  "dependencies": {
    "@types/hoist-non-react-statics": "^3.3.1",
    "indexof": "^0.0.1",
    "react": "^18.0.0",
    "react-dom": "^18.0.0",
    "react-router-dom": "^5.2.0"
  },
  "devDependencies": {
    "@types/node": "^15.6.0",
    "@types/react-router-dom": "^5.1.8",
    "@vitejs/plugin-legacy": "^1.4.0",
    "@vitejs/plugin-react-refresh": "^1.3.1",
    "less": "^4.1.1",
    "typescript": "^4.1.2",
    "vite": "^2.8.6",
    "vite-plugin-compression": "^0.3.0",
    "vite-plugin-externals": "^0.1.5"
  }
}

yarn build
yarn serve

Used Package Manager
yarn

I can't access the repro, but according to the error message. Did you install dependencies before building?

sorry, my mistake, it's ok

I can't access the repro, it seems to be private. But according to the error message, did you install dependencies before building?

sorry, my mistake, it's ok

Thanks for updating this @Jairwin-L. This looks like the same as #3001, there's some workarounds listed there which might help with your setup. I'll close this for now so we can keep the discussion there. Thanks again for updating the repro too.


i18n: added and correction of translation P1s-p3s

There was a large duplication of German translations. I fixed this and corrected the translation which was in Japanese (De and Fr).

Thanks for the fixes and the translations!


Cannot solve merge conflict with notebook (ipynb) in VSCODE

Type: Bug
I use notebook (ipynb) and keep track of version using git. However, when I want to merge a change in a feature branch to my main branch (the change is done in notebook ipynb). The view of merge conflict is in text editor, not in notebook viewer. It is very difficult to read and solve the merge conflict. Furthermore, I cannot open the merge editor in this case.
VS Code version: Code 1.86.2 (903b1e9d8990623e3d7da1df3d33db3e42d80eda, 2024-02-13T19:40:56.878Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12800H (20 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.64GB (17.88GB free)

Process Argv
--crash-reporter-id fdbab940-1ecb-4f29-a04b-3a0da7a9618c

Screen Reader
no

VM
0%

Extensions (17)

Extension
Author (truncated)
Version

copilot
Git
1.166.0

copilot-chat
Git
0.12.2

theme-monokai-pro-vscode
mon
1.2.2

black-formatter
ms-
2024.0.1

debugpy
ms-
2024.0.0

flake8
ms-
2023.10.0

python
ms-
2024.0.1

vscode-pylance
ms-
2024.2.2

jupyter
ms-
2024.1.1

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

material-icon-theme
PKi
4.34.0

tabnine-vscode
Tab
3.72.0

intellicode-api-usage-examples
Vis
0.2.8

vscodeintellicode
Vis
1.2.30

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30968133
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
d34g3935:30971562
edj9j583:30969295

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Duplicate of https://github.com/microsoft/vscode/issues/160941

. The view of merge conflict is in text editor, not in notebook viewer. It is very difficult to read and solve the merge conflict. Furthermore,

By design, for now we will continue to fallback to text editor.

I cannot open the merge editor in this case.

Fixed in duplicate issue.

Given this issue has only received just 1 upvote since this issue was created and the fact that we now have a way to open the diff editor to resolve merge conflicts, i'm closing this as done.
At the moment, resolving merge conflicts for Notebooks directly in notebook diff editor is not planned.


Remember view preference

I really like working with the table view instead of the key value view. Right now mongotron does not remember my preference. For example If I select one collection and then change the view to table view, and then later go to another collection it is displays it in the key value view instead of table view view .
I hope I have described my problem clearly.
And also If you are busy maybe you can point me in the right direction and I will give it a try!
Thank you for the awesome app!

Fixed in version 1.0.0-alpha.5


augur-node: add end date filter to getMarkets

Suggest we implement this fully front end as follows

hardcode cut-off date in UI
filter markets by hardcoded cut-off date using market.endTime

I'm open to a getMarkets filter, eg. on endTime, but I think this particular need might be better served doing it fully on the front end.

@andrewdamelio

@ryanberckmans 👍

Per Andy's point we may support this in augur-node if there's an interaction with pagination. Andy will decide

@ryanberckmans Yeah, I think we need to add this to augur-node...
Otherwise, we will get strange UI behavior,  for example, the total market count (in the pagination label)

wouldn't be correct since we can't exclude markets past the expire date until we load the marketData.

You got it, will do


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for vakumposeti processing.
🔨 Explore the source changes: 9294ef82858c2366958e042217fb7e708eec4b82
🔍 Inspect the deploy log: https://app.netlify.com/sites/vakumposeti/deploys/61d37418f75e5200077e1af4


Visual Studio Test Explorer integration

I just tried this package, it's great.    I like this style, and have existing JUnit tests I'll be porting, so this should save me some time and reduce frustration. Thank you.
I'm using Visual Studio Community Edition with the latest TypeScript for Visual Studio extension.   It integrates nicely with Mocha's describe/it style tests, even displaying a margin icon next to them to make it easy to run a particular test or suite.   Unfortunately, it doesn't recognize the mocha-typescript tests, and is initially surprised by the results.  (It does seem to adapt to their presence.)
Are you aware of this, any plans to enhance the integration?

This is an interesting feature request. I don't have plans to implement it, but if I have some available time I will at least research if it can be done. I am not using Visual Studio any more. I moved to VSCode. It works well for TypeScript projects.

Cool, thanks.   I'm using both VSCode and VS, and agree VSCode is nice environment.   But there are still some add-in packages only available for the full VS, e.g. Resharper, that don't (yet) seem to have open-source replacements.

Text decoration extension for VSCode: https://github.com/Microsoft/vscode-extension-samples/blob/master/decorator-sample/extension.ts
Bootstrapping TypeScript project with AST traversal for test exploratio: https://github.com/FireSt-dead/tsc-native/blob/master/compile.java.ts

It should be possible to setup test exploration tool that takes a typescript project and figures out describe/it @sute/@test cases and decorates the it and the @test with red/green background color based on whether some tests passed failed. Also probably providing tooltips for errors with stack traces?

@BurtHarris I tried with VS2015 with node tools 1.2 I think. I only needed:
<TypeScriptExperimentalDecorators>true</TypeScriptExperimentalDecorators>

In the project and the VS was discovering new tests on save even with the @suite and @test decorators.
Double clicking on test was opening the test.js though but that was so even for tests created with describe and it.
I am closing this issue.


Added linear search code

This pull request solves issue #2 .

Hey @yuvika09
Please claim the issue and try to work on the same.


add beam_dataflow_task to luigi/contrib

#2665
Adds a task for Beam Dataflow jobs to luigi/contrib, mostly as a wrapper for DF execution params and formatting of input/output URIs, with callbacks on successful/unsuccessful execution. Also provides an (overridable) runner to monitor job execution after submitting the job.
CC @daikeshi

@Tarrasch Thanks for looking at this. We will take over and continue with the review.

LGTM! 👍
@ClaireMcGinty thanks for putting it into luigi.contrib!


Updates PassClient to expose the incoming links for a URI.

Implements Map<String, Collection<URI>> getIncoming(URI passEntity) for the PassClient interface.
Updates Jackson type handling so that exceptions are thrown when readResource(URI, Class<? extends PassEntity>) retrieves a resource of a type that differs from the supplied type.

The @JsonTypeInfo(use = JsonTypeInfo.Id.NAME) annotation is added to the PassEntity class, and @JsonProperty("@type") annotations were removed from sub classes.
Test JSON resources were updated to carry an "@type": "Type" property.
type member variable of PASS model classes was removed
The Fedora crud client is updated to use Class.simpleName() when looking up the pluralized container name for creating resources.

There's some import clean-up I can do on this PR.  Let me know if there's any other feedback!

@emetsger The Travis issue is the one we were seeing yesterday with oapass/fcrepo:4.7.5-2.0-SNAPSHOT-2. I haven't seen it on this version before. Try switching to oapass/indexer:0.0.6-2.0-SNAPSHOT in the integration test pom.xml - it fixed it in my local tests.


[10.0] Update Stripe API version

Since there are no changes that affect Cashier we could use the latest Stripe API version (2019-08-14).

@driesvints ?

Yeah I think it's safe to update the API now and then. But since it would require us to do minor releases and since there's no real benefit in doing so I'd advice at doing this only when there's new features we can make use of.


Add match? predicate

@solnic I did this, but I'm very unsure now, this looks like too generic. Anyway, my class has a custom === method and I want to match values with that, soooo, can we have it? If not, just close :)

I find this very confusing, as you pointed out this feels too generic. ie when I see match? I think about regex, in fact I had no idea there's Regex#=== that can be used against a string.

I wonder if it'd be clearer if we called it #case?

Yeah, I like this idea Tim. This does require you to understand how case statements work, but that's OK.

OK, I like the idea, I updated the name. Range also has #=== btw :)


pause() function not enabled

pause() doesn't work if installed with npm as the dist files were not changed to include it, but you can add it manually.

Just release that: https://github.com/xkeshi/vue-countdown/releases/tag/v0.6.0


music xml parser (partial measure indicator)

noticed that in the Music XML Parser there's a simple error- mxl file being used when it should be an xml file.  "testdata/flute_scale_with_png.mxl",

Hi @Lizzard13, I'm not very familiar with this part of the code, but are I believe it that particular test is for the compressed version of MusicXML (http://www.musicxml.com/tutorial/compressed-mxl-files/). Please re-open if I'm wrong. Thanks!


Add time2backup version in info files

add a new section:
[time2backup]
version = 1.4.0

done in commit 0c0d6a245518e4144cc3d42a8862321bc149ee1a


OIDC - HTTP 404 after redirect to client app

I made a sample IdentityServer host + MVC client application that use OIDC based on https://identityserver4.readthedocs.io/en/release/quickstarts/3_interactive_login.html.
That works ok.
When I copy the relevant startup code to my actual MVC app, things don't work as well anymore. First, a controller is hit that is decorated with the Authorize attribute and is redirected to the IdentityServer login page. After the user logs in and is redirected to my app again, a HTTP 404 error occurs.
The post to signin-oidc of my MVC client seems to be going well. After that the 404 happens.
How can I debug this further?
Relevant code of the IdentityServer host:
public void ConfigureServices(IServiceCollection services)
        {
            services.AddIdentityServer()
                .AddDeveloperSigningCredential()
                .AddTestUsers(TestUsers.Users)
                .AddInMemoryClients(Config.GetClients())
                .AddInMemoryIdentityResources(Config.GetIdentityResources())
                .AddInMemoryApiResources(Config.GetApiResources());

            services.AddMvc();
        }

Relevant code of the MVC client:
public void ConfigureServices(IServiceCollection services)
        {
            services.AddMvc();
            JwtSecurityTokenHandler.DefaultInboundClaimTypeMap.Clear();

            services.AddAuthentication(options =>
            {
                options.DefaultScheme = "Cookies";
                options.DefaultChallengeScheme = "oidc";
            })
                .AddCookie("Cookies")
                .AddOpenIdConnect("oidc", options =>
                {
                    options.SignInScheme = "Cookies";

                    options.Authority = "http://localhost/Webshop.IdentityServer";
                    options.RequireHttpsMetadata = false;

                    options.ClientId = "webshop";
                    options.SaveTokens = true;
                });
        }

Relevant parts of the log file
Application Insights Telemetry (unconfigured): {"name":"Microsoft.ApplicationInsights.Dev.Message","time":"2018-09-22T19:20:19.2813334Z","tags":{"ai.internal.nodeName":"CLT-NGRUSON","ai.internal.sdkVersion":"aspnet5c:2.1.1","ai.operation.parentId":"|ef582de1-4b89990c129dc875.","ai.location.ip":"<IP_ADDRESS>","ai.cloud.roleInstance":"CLT-NGRUSON","ai.operation.name":"POST /Webshop.Web/signin-oidc","ai.operation.id":"ef582de1-4b89990c129dc875","ai.application.ver":"<IP_ADDRESS>"},"data":{"baseType":"MessageData","baseData":{"ver":2,"message":"Request finished in 56.0594ms 302","severityLevel":"Information","properties":{"ElapsedMilliseconds":"56,0594","CategoryName":"Microsoft.AspNetCore.Hosting.Internal.WebHost","AspNetCoreEnvironment":"Development","DeveloperMode":"true","StatusCode":"302"}}}}
Application Insights Telemetry (unconfigured): {"name":"Microsoft.ApplicationInsights.Dev.Request","time":"2018-09-22T19:20:19.2212392Z","tags":{"ai.internal.nodeName":"CLT-NGRUSON","ai.internal.sdkVersion":"aspnet5c:2.1.1","ai.location.ip":"<IP_ADDRESS>","ai.cloud.roleInstance":"CLT-NGRUSON","ai.operation.name":"POST /Webshop.Web/signin-oidc","ai.operation.id":"ef582de1-4b89990c129dc875","ai.application.ver":"<IP_ADDRESS>"},"data":{"baseType":"RequestData","baseData":{"ver":2,"id":"|ef582de1-4b89990c129dc875.","name":"**POST /Webshop.Web/signin-oidc","duration":"00:00:00.0636929","success":true,"responseCode":"302","url":"http://localhost/Webshop.Web/signin-oidc"**,"properties":{"AspNetCoreEnvironment":"Development","httpMethod":"POST","DeveloperMode":"true"}}}}
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 GET http://localhost/Webshop.Web/Basket/AddToBasket
Application Insights Telemetry (unconfigured): {"name":"Microsoft.ApplicationInsights.Dev.Message","time":"2018-09-22T19:20:19.3147304Z","tags":{"ai.internal.nodeName":"CLT-NGRUSON","ai.internal.sdkVersion":"aspnet5c:2.1.1","ai.operation.parentId":"|ef582de2-4b89990c129dc875.","ai.location.ip":"<IP_ADDRESS>","ai.cloud.roleInstance":"CLT-NGRUSON","ai.operation.name":"GET /Webshop.Web/Basket/AddToBasket","ai.operation.id":"ef582de2-4b89990c129dc875","ai.application.ver":"<IP_ADDRESS>"},"data":{"baseType":"MessageData","baseData":{"ver":2,"message":"Request starting HTTP/1.1 GET http://localhost/Webshop.Web/Basket/AddToBasket","severityLevel":"Information","properties":{"CategoryName":"Microsoft.AspNetCore.Hosting.Internal.WebHost","AspNetCoreEnvironment":"Development","Protocol":"HTTP/1.1","DeveloperMode":"true","Scheme":"http","Method":"GET","Host":"localhost","Path":"/Webshop.Web/Basket/AddToBasket"}}}}
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request finished in 32.8847ms 404
Application Insights Telemetry (unconfigured): {"name":"Microsoft.ApplicationInsights.Dev.Message","time":"2018-09-22T19:20:19.3231198Z","tags":{"ai.internal.nodeName":"CLT-NGRUSON","ai.internal.sdkVersion":"aspnet5c:2.1.1","ai.operation.parentId":"|ef582de2-4b89990c129dc875.","ai.location.ip":"<IP_ADDRESS>","ai.cloud.roleInstance":"CLT-NGRUSON","ai.operation.name":"GET /Webshop.Web/Basket/AddToBasket","ai.operation.id":"ef582de2-4b89990c129dc875","ai.application.ver":"<IP_ADDRESS>"},"data":{"baseType":"MessageData","baseData":{"ver":2,"message":"**Request finished in 32.8847ms 404**","severityLevel":"Information","properties":{"ElapsedMilliseconds":"32,8847","CategoryName":"Microsoft.AspNetCore.Hosting.Internal.WebHost","AspNetCoreEnvironment":"Development","DeveloperMode":"true","StatusCode":"404"}}}}
Application Insights Telemetry (unconfigured): {"name":"Microsoft.ApplicationInsights.Dev.Request","time":"2018-09-22T19:20:19.2865317Z","tags":{"ai.internal.nodeName":"CLT-NGRUSON","ai.internal.sdkVersion":"aspnet5c:2.1.1","ai.location.ip":"<IP_ADDRESS>","ai.cloud.roleInstance":"CLT-NGRUSON","ai.operation.name":"GET /Webshop.Web/Basket/AddToBasket","ai.operation.id":"ef582de2-4b89990c129dc875","ai.application.ver":"<IP_ADDRESS>"},"data":{"baseType":"RequestData","baseData":{"ver":2,"id":"|ef582de2-4b89990c129dc875.","name":"GET /Webshop.Web/Basket/AddToBasket","duration":"00:00:00.0399890","success":false,"responseCode":"404","url":"http://localhost/Webshop.Web/Basket/AddToBasket","properties":{"AspNetCoreEnvironment":"Development","httpMethod":"GET","DeveloperMode":"true"}}}}
The program '[16388] dotnet.exe: Program Trace' has exited with code 0 (0x0).

IIS logs:
2018-09-22 21:11:04 ::1 POST /Webshop.Web/signin-oidc - 80 - ::1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/64.0.3282.140+Safari/537.36+Edge/17.17134 http://localhost:81/Webshop.IdentityServer/connect/authorize?client_id=webshop&redirect_uri=http%3A%2F%2Flocalhost%2FWebshop.Web%2Fsignin-oidc&response_type=id_token&scope=openid profile&response_mode=form_post&nonce=636732474645581393.MjFmY2I3ODAtOGQ4OC00NTAxLWE5MzgtNWVjMzg2NDZjZmRiYWRmMTE3ZmYtOWE5Ni00ZDBiLWFmM2EtN2VkNDRjNTQxZTI4&state=CfDJ8AhcSnwTTTBBgtPSuVfCJdvRQ_yasFBwSUi4WWA55Inhdj7g3DbQANa_EC6f3Xp8P2IT8bA5arHpFB1gCe6wdIFfCynr1nX_IFwkjx0UGb3gKXjGHlRR6ZjHCnkWA3hw_B07ZyjuWVjN7rQmbcbIjMjvBBxg4pxPTJEpW23UpwSnkf5gS2BEtotqx41rL1UBmtEkGtqk7goj23m8B0yhPOM2rPAUrPpa-LI5mYjah9KqA6axeEEckq6Jo4J0gkML_1dajVB1heOT6a0ekcK0_g1PYP2P4nNsP5QV7evzqJ4U0N1EOHTf2GS10N1lE2O_6hl3d4T4IknroYhdEDJAWKQNS4egY__bZ1Kvz_OgMEEl&x-client-SKU=ID_NET&x-client-ver=<IP_ADDRESS> 302 0 0 24
2018-09-22 21:11:04 ::1 GET /Webshop.Web/Basket/AddToBasket - 80 - ::1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/64.0.3282.140+Safari/537.36+Edge/17.17134 http://localhost:81/Webshop.IdentityServer/connect/authorize?client_id=webshop&redirect_uri=http%3A%2F%2Flocalhost%2FWebshop.Web%2Fsignin-oidc&response_type=id_token&scope=openid profile&response_mode=form_post&nonce=636732474645581393.MjFmY2I3ODAtOGQ4OC00NTAxLWE5MzgtNWVjMzg2NDZjZmRiYWRmMTE3ZmYtOWE5Ni00ZDBiLWFmM2EtN2VkNDRjNTQxZTI4&state=CfDJ8AhcSnwTTTBBgtPSuVfCJdvRQ_yasFBwSUi4WWA55Inhdj7g3DbQANa_EC6f3Xp8P2IT8bA5arHpFB1gCe6wdIFfCynr1nX_IFwkjx0UGb3gKXjGHlRR6ZjHCnkWA3hw_B07ZyjuWVjN7rQmbcbIjMjvBBxg4pxPTJEpW23UpwSnkf5gS2BEtotqx41rL1UBmtEkGtqk7goj23m8B0yhPOM2rPAUrPpa-LI5mYjah9KqA6axeEEckq6Jo4J0gkML_1dajVB1heOT6a0ekcK0_g1PYP2P4nNsP5QV7evzqJ4U0N1EOHTf2GS10N1lE2O_6hl3d4T4IknroYhdEDJAWKQNS4egY__bZ1Kvz_OgMEEl&x-client-SKU=ID_NET&x-client-ver=<IP_ADDRESS> 404 0 0 29

Any update?

I didn't have a HttpGet controller method matching the URL that IdSrv redirects to after logging the user in. I just added that to my code, that prevents the 404 from happening, but the user experience gets a little bit weird. Because I have an Authorize attribute on a HttpPost action, the user gets redirected to IdSrv to log in, but that's when I lose the state of the original Post request. Any way that you know of to extend the functionality of the signin-oidc method of ASP.NET Core in my client app? Maybe somewhere in the OIDC middleware? I need to add some code after the user has logged in, but in this scenario the SignIn method of my AccountController doesn't get hit.

Yea, the MSFT OIDC plumbing has some events you'd need to handle to take control. Since we've established that this is a client issue and not an IdentityServer issue, I'll close.


add manpage and Makefile

I created a manpage based on your README.
I do not know how to make cargo install it, so I left that out for now.
Pull request checklist

[X] The tests are passing locally as well as on CI -> man displays it correclty
[ ] The changelog was updated (in CHANGELOG.md) not a feature, so does not apply
[ ] If commands were added/modified, the documentation was adapted

Thank you very much for your contribution!
First of all: The manpage itself looks great!
But what I worry more about is, how we can create a nice install workflow. As discussed here, cargo install does not support installing manpages.
This effectively means we need an alternative way of installing trackie. I think we have a few possibilities here:

Distribute trackie as a .deb package. Afaik Ubuntu/Debian are widely used distros and I am sure .deb packages are able to bundle man-pages. I have to admit though, that I have no idea on how to create such a package. But I guess it can't be too hard
Provide a trackie install command so that trackie can install itself. It could then also copy the manpage in the correct directory and I guess we would be fine then? This would probably be a linux-only command as Windows doesn't really have a nice location to put binaries into.

What is your opinion on that? What is the better alternative? Do you have another solution in mind?

I personally think the best option is to wrap cargo in make. A simple Makefile is simple to create (I can add one if you like) and can install all files in an idiomatic way that makes it straight-forward for package maintainers to package trackie for their repositories.
I advise against creating a .deb package, that really is the job of the packagers, not the project developers, and it would add an unnecessary hurdle for packaging trackie into other distributions repositories.

Just to be sure: Even if we would add such a Makefile, windows uses still would be able to directly use cargo, right?

Adding a Makefile would leave everything as it is right now, it simply adds an additional way to initiate the build and install the files.

Sounds great! Thanks so much for all your help on this!

So if you could add a Makefile to this PR and maybe update the README, we can merge your PR into master :)

Makefile has been added

Works like a charm! Thank you so much! Will merge this as soon as the checks are done.


Sjkayle feature/badge component

Moved title in React component to children

👋 Thanks for creating a pull request! 🚀 Checkout the storybooks we've created for it: reactangular

@JohanObrink and @sjkayle I took the liberty to refactor the angular version a bit. Mainly shifting from using a typical component selector <ngg-badge> to an attribute selector ngg-badge so instead of this:
<ngg-badge>Text</ngg-badge>

You now use it like this:
Text

The main reason for this is that Angular wraps the html in a custom selector (just like other web components). One benefit with this is that it allows angular to scope styles to individual components with and without the use of shadow dom, it also allows angular components to be compiled to native web components. One drawback is that it affects the use of standard css rules on these components (in some cases).
Consider the following css rule:
.badge + .badge {
  margin-left: 1rem;
}

The following markup would produce two badges and the second badge would have left-margin set to 1 rem since our css rule states that .badge preceded by .badge should have a left margin.
Text
Text

Using a standard component selector with angular these rules wouldn't be applied as the result would look like this:
<ngg-badge>Text</ngg-badge>
<ngg-badge>Text</ngg-badge>

One final note is that I think we have to consider how badges are used. For example how will the consumer know that a badge has been removed now as close will just remove it from the dom? Perhaps it should be implemented as a form control, i.e.expose an array of badges were the state could be tracked by looking at the state of the form control (similar to a multi select).
If you're not borred already and want to keep on reading;)
Some thoughts on creating components
Styling components with angular is typically not a problem as these kind of css rules are often applied to native elements i.e. buttons, anchors (links), divs etc since we don't write css for web components that are meant to be self contained (they should include their own logic, styling and expose css variables to allow custom theming). Personally I tend to avoid wrapping native components for this reason. E.g. creating a button component for a button doesn't really make sense if we're only interested in controlling which attributes (like classes) that should applied to the element (that's what directives are for). With directives we can extend the behaviour for native elements. If we on the other hand want to manipulate the markup of native elements such as adding other components or child elements or add additional logic, we have the option to use other selectors to create/extend existing ones. eg. instead of creating a new button component using <ngg-button> we could use a class or an attribute as selector to alterer or extend the native behaviour as well as its' markup. You typically create angular components for things that natively doesn't exist or when you invent something new (eg. dropdown, datepicker etc.).


Updated sort.ts to remove more problematic properties from sfdx-project.json

When using SfdxCommand's function this.project.resolveProjectConfig(), additional properties are added to the in-memory representation of sfdx-project.json. Previously, I already had a list of extra properties to delete before saving sfdx-project.json. This PR removes some new-ish properties from the JSON:

disable-telemetry
org-metadata-rest-deploy
target-dev-hub
target-org

Long term, there's probably a much better way to deal with this, and this plugin should eventually be converted to an sf plugin (instead of using the legacy sfdx plugin framework). But this PR should hopefully work as a quick fix for this issue.

@jamessimone I've published v0.0.20<EMAIL_ADDRESS>


dashboard: show source throughput on data source page

are we going to draw a fold line diagram on the webpage?

Directly import the Grafana dashboard

I gonna take the issue, any details?

a simple idea is to put a Grafana panel in RisingWave dashboard.


Align jsdoc with openui5

Coverage: 94.609%. Remained the same when pulling aba8edca175802fe9c86ec9f8db3024a3ab71d45 on align-jsdoc-with-openui5 into 9aa8b1c0aa2826d42fe44d1bb1d11dc7f2bc8242 on main.


docs: init docusaurus documentation

Codecov Report

Merging #44 (35f8ada) into master (3a1a04a) will not change coverage.
The diff coverage is n/a.


Use HTML inside comment

Is there any way to use HTML inside the comment?
To do this i changed the following line:
1593: content.html(this.linkify(this.escape(commentModel.content)));
to
1593: content.html(this.linkify(commentModel.content));

The content of the comment is escaped for purpose. If you insert the content into DOM without escaping it, malicious users may inject javascript to the site. For example, if you post a comment "" and insert it to DOM straight up, all the users be prompted with "Hi there!".

Yes i thought about that.
But should we stop a feature for such triviality? If so, what's the solution? Should i perform a server-side validation?

The issue is not that trivial you may think, please check out the list of possible vulnerabilities at: https://www.owasp.org/index.php/XSS_Filter_Evasion_Cheat_Sheet. There's a good reason why Facebook, Google and even Github won't support pure html comments, if you wish to implement something like this, I recommend using a Markdown approach like it's implemented here in Github

Ok i see.
However, there isn't any possible way to change server-side data. These are client-to-client actions.
I know it's bad anyway, but i'm using it on a intranet portal, no one inside a single company wants to inject some JS in a comment. If he wants to do it, he will suffer some consequences because i use comment history.
In the future i will implement that markdown approach.
Thank you, that's the right solution.

I feel same as you LESARQ. Instead of force escaping the comment, it might be given as an option such as escapeContent: true with a warning.


[terra-demographics-banner] Preferred Name displayed within parentheses

Summary
Changes to display Preferred First Name within parentheses instead of quotes.
Additional Details
Updated wdio screenshots for terra-overlay and terra-search-field, to fix the master build
Resolves #2775

I think keeping this PR limited to demographics banner changes will help us to track down changes in future and Also PR's logged to fix issues in master build should be prioritized among other PR's for Merge.

I think keeping this PR limited to demographics banner changes will help us to track down changes in future and Also PR's logged to fix issues in master build should be prioritised among other PR's for Merge.

I agree, i have created a separate PR to fix the Travis wdio failure.


🚀 Feature: Investigate GitHub's new rulesets feature instead of branch protections

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
Thanks @voxpelli for throwing this my way! https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#creating-a-branch-or-tag-ruleset
Looks like there's API support: https://docs.github.com/en/rest/repos/rules?apiVersion=2022-11-28
Is this something that we should replace the existing branch protection features with?
Additional Info
Co-authored-by: @voxpelli

The feature is looking pretty stable now and seems to have all the parts I need. Plus, unlike classic branch protections, rulesets don't require the branch to already exist. This will be helpful for the create engine onboarding to let the script run before the repository has had its initial commit pushed. I'll take this on now.

@all-contributors please add @voxpelli for ideas.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


CREST endpoint documentation format

We should look into introducing a new documentation format for CREST endpoint pages. Currently, we just have newer pages imitating the format of previously written pages, resulting in a format (if it can even be called one) which is implemented very inconsistently. I'll base this on the format I used for documenting the fleet endpoints, and is currently only used for them.
Top-level documentation categories
Pages should be organized into categories based on their general theme and functionality.
Currently, we have four categories: Character, Map, Eve, Fleet. Additional ones could be Corporation, Market, Remote UI...
Multiple endpoints on a single page
I'd suggest keeping multiple endpoints on a single page only when they handle the same kind of resource, meaning that a collection and its corresponding resource should be on the same page, but different collections/resources should have their separate pages. I'd like to hear if anyone thinks there are certain endpoints which should be exceptions to this.
Endpoint route
Instead of providing a URL with ID placeholders, which is not the way things should be done in CREST, we should provide directions for walking through endpoints to get the full URL.
I've opted for a JavaScript inspired syntax describing navigation within an endpoint, and arrows for indicating an HTTP request.
Also, for those who decide to go against best practices by hardcoding and building URLs themselves, an example URL should be provided, preferably the one of the sample response included.
Sample responses/requests
For each endpoint and every method it supports, a sample request/response should be included, along with the exact content type of the included sample.
The samples should be pretty formatted, be valid JSON (no { ... } placeholders) and use two spaces for indentation (Four or eight spaces take up a lot of horizontal width, which combined with many levels of indentation can ruin the reading experience, especially on mobile devices.)
If there are multiple versions available, only the latest one should be present. Deprecated versions shouldn't be documented.
Response/request details
Every sample response/request should also have a section detailing properties of the sample. Not every property should be described, as many of them are self-evident and their descriptions wouldn't be much more than clutter.
Notes and references
If there is any additional information relevant to the use of the endpoint, it should be placed in the notes section.
Any references (dev blogs, patch notes, forum posts...) should be listed at the bottom of the page, under a L2 References header.
That's it for my proposal. Consider #220 and changes in #227 to be the reference implementation of the format. If there are any question or suggestions, please comment here.

Top-level documentation categories
Pages should be organized into categories based on their general theme and functionality.
Currently, we have four categories: Character, Map, Eve, Fleet. Additional ones could be Corporation, Market, Remote UI...

I think there should be two top level guides  one is a Programmers Guide and the second is a Technical Reference Guide.
The users guide should contain all of the common/generic information that pertains across all endpoints and/or groups of endpoints.  There should be an index in this section that is organized by functionality per carbon's suggestion.
The Technical Reference Guide should be the actual endpoint post, get, put and delete data formats.  It should have an index page laid out alphabetically based on the endpoint's name with indented links to the individual data structures UID's that endpoint supports.  There should be an individual page per unique UID.

Multiple endpoints on a single page

Each "endpoint" has the potential of having four unique data structure UID's  (post, get, put, delete) As mentioned above, the Technical Reference Guide should have a unique .md page per unique UID.  Individual UID pages should conveniently link their sibling UID pages.

Sample responses/requests

I disagree that the json should be valid and not contain ... only enough to show the pattern should be given.  Also a pseudo data structure is more important than the sample and should be provided above the sample.
The auto generated documentation I'm creating is based on Carbon's template.  We should declare a boilerplate template and agree on it before proceeding much further on this.

Proposed boiler plate templates:
The Group page template page is typically an endpoint or a group of common endpoints page.  These are the pages that a Programmers Guide->Functionally grouped index would want to link to.
This template contains the $title which is the replacement macro that gets the human friendly name given to the endpoint.  The post, get, put and delete UID's are replaced with the UID's value.  The children of the group are automatically bullet item listed and linked to.  See Group: Characters for an example.
The leaf node template was patterned after Carbon's fleet examples.  This temple is heavy on the idea of leaving "(TBD)"  under all required labels for which values are not yet known, thus making it easy for other authors to quickly fill in information as it is determined.
The current autogen determines the titles, post, get, put and delete data UIDs, example url's and several of the cache times (all those not requiring id segments and/or authentication).
See the auto-gened Technical Reference index page.  Note some links are still broken.

Team,
With CCP being swamped with the current mobile work, it’s not likely for arbitration on this issue to happen anytime soon.  If nothing comes of my documentation auto-gen work I can only hope that what caused this push will become a priority for CREST.  I would just like to capture that cause here and note that the whole concept of the restructuring of the documentation was based on this cause.  The basic restructuring concept is to map the actual URL tree of all possible endpoints and their leaf mime type data structure definitions.  The “cause” spoken of above is the current lack of this information being available from CREST.
History of this PR ...
I wanted to write a proper REST client that dynamically generated endpoint URL's and was able to identify if it's current implementation of versions of the mime identified structures were out of date.
This was not possible to do with the existing GET/OPTIONS requests against the root endpoint.  This is not currently possible because only about one half of all of the endpoints (which I have been able to identify) are being reported.
I needed my own static structure to identify/compare my current implementation version against that reported with a combination of a GET request on the root and OPTIONS requests on each of the reported endpoints of the GET request.  (BTW the X-DEPRECATED header is broken; I’ll write a bug on this soonish).  Thus I filled in the holes of missing data from the get of the root with what I discovered from other sources and browsing around the namespace.
Now that I assume I have a full list of all possible endpoints and their possible post, get, put and delete mime types it is easy for me to kick out two things:

A json object graph of what I would expect to get from an HTTP get request to the root url.  See [sisi-root-endpoints.json] (https://github.com/timpanogos/crestj/blob/master/crest-core/config/sisi-root-endpoints.json)
Auto-generated documentation based on group and leaf .md templates so as to identify what I have hard-coded as a static representation of the endpoint tree. Namely an endpoint name, endpoint url example, endpoint relative uri segment, post, get, put and delete mime types and version,  tree relationships to other endpoints and mime types (i.e. groups, but more, full URL map),  some cache times (could do all with more effort).  See auto-gened Technical Reference index page

Thus my whole documentation push evolved from my desire/need to have a full URL mapping of all CREST endpoints for dynamic URL building in my client and realizing this would be a preferred method of also laying out the documentation, encouraging people to dynamically build their url’s and by the way, here is a url based map/index to all mime types currently in the tree.


Add missing Tests

Cover test suites
Redirect, SmartCollection, Collect, Custom Collection tests

Thanks for the tests!

Ping me when you update those newlines and I'll merge this.

Thanks for the tip! @kevinhughes27
The PR is updated!

Oops! I added the missing newlines. :sweat:
Quick question: I have seen a lot of tests using unit and spec style. Which one should I use?

I believe most of the tests here follow the test ... pattern so stick with that


[Feature][SQL]  SQL task enhanced verification

In the current version, when writing SQL statements, the SQL task type cannot contain semicolon ";". Otherwise, an error will be reported when executing
It is recommended to enhance the verification in the front end. If there is a semicolon ';' in the SQL, you will be prompted
Note: just give prompt, don't fail verification. For example, the comment contains semicolon, which makes it impossible to save

目前版本, sql任务类型 写sql语句的时候,不能包含分号";" . 否则执行的时候报错.
建议在前端增强校验, 如果sql中存在 分号";"  给与提示.
注意: 只给与提示就行不要校验不通过, 比如注释中包含分号,导致不能保存这是不合理的.

please assign me,  i'll try

where do I have to fix the error ?
I have just created an account on GitHub and just know basic details of it but i have knowledge of Java!


Fix pytest coverage subprocess bug

Currently, if we have a test that, in a subprocess, starts python in a different working directory, then this will crash when running with coverage. This happens because coverage is run in that directory without branching enabled, because that it doesn't pick up our config file, I believe.

most subprocess calls that affect coverage were removed. Closing this because coverage isnt a metric at this point and if it becomes one, the entrypoint tests that do use subprocess calls can be skipped.


Use class data with hidden classes

Calling setExact on a hidden class can prevent it from being unloaded. When finishing the class, define the objects as class data and call defineHiddenClassWithClassData. The ConstantsRegistry class should then call the classData or classDataAt methods.

Resolved: https://github.com/cojen/Maker/commit/61d03bba0c92439d87c9eee52698c7c7824eb096


Consolidate setCreatedAt and setUpdatedAt hooks to a more generic hook

It's weird to do setCreatedAt({ fieldName: 'archivedAt' }). It also doesn't make sense to do 2 hooks that do the same thing. We should consolidate them in to a single setCurrentDateTime or setNow hook. It would behave pretty much the same but you have to pass at least one field.
{
  before: {
    create: [setNow('createdAt', 'updatedAt')],
    update: [setNow('updatedAt')],
    patch: [setNow('updatedAt')],
    remove: [setNow('archivedAt')]
  }
}

Closed with https://github.com/feathersjs/feathers-hooks-common/pull/181 and will be published with v3.3.0.


Path Stroking is Hideous

I'm testing with converting Glyph to PathData and drawing the paths to the screen and then stroking, but I'm ending up with really ugly stroking:

This is using Open Sans from GoogleFonts. Is there something I need to do to make this stroke properly?

Oops...I just figured out the problem.  I'm shifting values at render-time to always be floor(value) + 0.5 for better pixel rendering and that seems to be causing the trouble.  Sorry for blaming OpenType. :)

floor(value) + 0.5 is horrible. Note that opentype.js does support fonthinting which will align values for you on grid (if you want to do strokes instead of fills, you still might want to do +0.5, but you shouldn't ever use floor())

@axkibe Why is using floor horrible?  The whole point of the 0.5 offset is everything draws consistently if it's always at n.5. For things like the font paths it's always dealing with whole numbers, so floor makes no difference. However, if you're dealing with a number like 500.25 you wouldn't want to just add 0.5 because you'll end up with 500.75, but if you floor(500.25) + 0.5 you'll end up with the an ideal 500.5.

Because font hinting is a way more sophisticated way to round properly to the grid.
https://blog.idrsolutions.com/2013/12/what-is-font-hinting/
Or simply said, a deliberate way that decides for each value to round down or up for minimal errors due to rasterization. (rounding)

@axkibe you're right regarding drawing text, but the adjustment was a global one applying to all contextual drawing.


Fix issue 1303: Server crashes on executing SELECT * FROM agtype(null);

This PR is a fix for #1303
- Add additional checks for Const expression nodes for which the
  walker code would crash.

- The server crashes for few other expr types too including Const,
  OpExpr, Var, BoolExpr and CoerceViaIO for which checks are added

- Add regression tests

@Zainab-Saad Now you can move it to PG14, 13, 12, & 11 :)
Keep up the good work!


SAK-43611 Chat : fix synoptic filters

 Here is an overview of what got changed by this pull request:

Complexity decreasing per file
==============================
+ chat/chat-impl/impl/src/java/org/sakaiproject/chat2/model/impl/ChatManagerImpl.java  -3

See the complete overview on Codacy


Forum/Feed

Problem: Teams don't have a way to share their progress, ideas, questions, and more with other teams. This is a problem students have repeatedly told us when asked for feedback.
#6 also seeks to solve this problem
Solution: A general forum/feed/discussion board for all teams to use.

How do we make something that fosters engagement? I feel like we've all seen forums on different platform that aren't widely used. Is forum the best solution to this problem, or is there another way, such as through events?

Priority: High

• What do you think about adding a feature where the user can suggest new ideas for projects and have other users like them, that way we can learn more about the demand for specific partnerships for the future

I think this is something that we should re visit the prioritization of


Mock out requests in panoramas tests

Resolve #276 by mocking out calls to requests.get and os.environ.get

Thanks a bunch for this!


feat: add support for .net recognition (#51)

it resolves #51
I changed the way to detect a devfile. Now it first uses component detection and then, if nothing is found, language detection.
This way i give priority to languages with frameworks and it seems the results are more stable.
P.S: Many of those 213 changed files are projects (c#/vb.net) for testing.

Hey folks!
I have some thoughts and suggestions on this.
For some background, the ".NET" umbrella includes a bunch of different things, and it's easy to mix them up. I am still not sure I understand all the moving parts myself, especially for older (proprietary, not cross platform) .NET.

Language, eg C# and VB.NET, but also F#. For a Java analogy, think of this as Java ecosystem supporting multiple languages: Java, Clojure, Kotlin and Scala among others.
Runtime, eg .NET Framework 4.x, .NET Core 3.1, .NET 6. As an analogy think of this as Java ME vs Java 8 vs Java 11 vs 17. Some Runtimes are compatible with others, some are not.
SDK, which roughly corresponds to the Runtime. Think of the JDK here, except if one JDK could target multiple, possibly incompatible versions of Java (ME and 17).
Project Build System (msbuild) which is roughly along the lines of a hybrid ant/maven system.
Project Type, eg, ASP.NET ("Classic"), ASP.NET Core. Think of JBoss AS vs Spring. But also includes things like "Desktop Application" and Android applications.

You can probably guess the language from the file extension. .cs is C#, .vb is VB.NET and .fs is F#.
There's only one build system: msbuild.
Project files use a bit of a flexible extension system. They pretty much always end with proj suffix, but the part before that is flexible. C# mostly uses .csproj, VB.NET mostly uses .vbproj and F# uses .fsproj. But those are not set in stone and people often use other extensions like .dockerproj or even .publishproj.
.sln (solution) files are a group of projects. They just include a path to other projects to build and don't really contain any logic other than that. slnf files (solution filters) allow narrowing down a .sln file further.
The Runtime is specified in the project file with things like TargetFrameworkVersion and TargetFramework. I see that the PR already handles that well.
The older runtime versions (.NET Framework 3.x and 4.x) are proprietary and Windows only. They are not supported on Linux. If you wanted to build/run this on OpenShift, you would need to run Windows, somehow. The cross-platform versions are .NET Core (all versions) with the TargetFramework of netcoreappX.Y and .NET version 5 and later (TargetFramework of net5.0, net6.0). There's suffixes possible in the TargetFarmework version to indicate project types too (see below).
The project type is a little tricky. It might be listed in the project file as a simple dependency, but the most common framework for recent .NET projects (ASP.NET Core) is implied by <Project Sdk="Microsoft.NET.Sdk.Web"> in the project file (docs). There's also the "Desktop Application" and other types, which are indicated by a suffix to the TargetFramework. See https://docs.microsoft.com/en-us/dotnet/standard/frameworks#supported-target-frameworks.

I have some thoughts and suggestions on this.

After sleeping on this, a few other things to watch out for.:
It's possible to have a single project that target multiple runtimes. The SDK will build your source code multiple times, each time targeting a different runtime. This generally involves using a semicolon-delimeted list in the TargetFrameworks (note the extra s) element in the project file. docs.
Project files can contain embedded snippets of code, such as Property Functions. A very common use looks like this:
<Import Project="$([MSBuild]::GetPathOfFileAbove(dir.props))" Condition=" '$([MSBuild]::GetPathOfFileAbove(dir.props))' != '' " />

Which uses [MSBuild]::GetPathOfFileAbove(dir.props) to find the path to a dir.props file somewhere up above in the parent file system.
And that brings me to Import. It works like #include in C, embedding another project file (which is often not a .csproj-style file, but commonly uses .props or .targets extensions). It's common to, for example, define a Directory.Build.props file which contains some constants and then use them in individual project files, for example, to define TargetFrameworks being targeted by all the different projects in a repository.
If you really want to fully parse project files, I am not sure you can do that without either calling msbuild (dotnet msbuild /pp to fully parse, expand and dump, but not evaluate/build the project) or duplicating much of the parsing logic.

@jeffmaury i updated the PR and I added almost everything suggested by @omajid but the Property functions. This requires a deeper investigation and i think this is not required for a first release and for the current state of .net devfiles. I'm going to opena
new issue for it. WDYT? Can you give this PR a look again and see if it work for you? Thanks!!
Thanks @omajid for all your useful infos, really appreciated!! :pray: I'm going to look at your comments again and again in future to improve the detection.


[SPARK-50373] Prohibit Variant from set operations

What changes were proposed in this pull request?

Prior to this PR, Variant columns could be used with set operations like DISTINCT, INTERSECT and EXCEPT. This PR prohibits this behavior since Variant is not orderable.
Why are the changes needed?

Variant equality is not defined, and therefore, these operations are also undefined.
Does this PR introduce any user-facing change?

Yes, users will now no longer be able to perform set operations on variant columns.
How was this patch tested?

Unit tests
Was this patch authored or co-authored using generative AI tooling?

No

@gene-db @cloud-fan Can you please look at this? Thanks!

@dtenedor This PR prohibits select distinct, and GROUP BY was already disabled. It was believe that this code path would also disable other operations which require grouping but apparently not.

thanks, merging to master!


Can't Import Files in PXT for Micro:bit

Selecting Projects/Import File should open the file browser to select your hex file. IT DOESN'T ANYMORE on this Latest Version! Previous versions were fine. I've tried with Chrome and Edge browsers. Both are BROKEN. I've cleared the browser's cache, but no different.
PLEASE FIX ASAP as package is UNUSABLE as it is.
Thanks.

We looking it right now

As a workaround, you can drag & drop the hex file into the editor. (Until we fix the issue)

Fixed in beta.


Ripple directive : height() undefined is not a function

Hi,
i have an error when  I click on an item that has the directive lx-ripple.
lumx.js : 725 : if (!ripple.height() && !ripple.width())

            <button class="btn btn--l btn--white btn--icon" lx-ripple>

            </button>

Maybe because of the section brand, it's a flex item
HTML generated :
<button class="btn btn--l btn--white btn--icon" lx-ripple="" style="position: relative; overflow: hidden;">

</button>

Maybe an error with angular.element function here ?
ripple = angular.element('', {
                                class: 'ripple'
                            });

I tried to manually add a class 'ripple', and the script continues to add objects as if he did not find the ripple.

Solved :
I included jquery before angularjs


Minecraft 1.15.X compatibility

Could you add Minecraft 1.15 compatibility? I could do a merge request but I don't really know about NMS D:

(as posted in #51):
I have been very busy with my degree, luckily @MrMicky-FR created a PR (#52) and added the necessary code for 1.15.
I'll soon be posting a compiled JAR file on both the repo and SpigotMC.
Sorry for the long wait!


Variables not shown when debugging with LLDB on macOS

Hi,
I've installed the latest LLVM + lldb via https://afnan.io/2018-10-01/using-the-latest-llvm-release-on-macos/, using:
brew install llvm
echo 'export PATH="/usr/local/opt/llvm/bin:$PATH"' >> ~/.zshrc

And now lldb's --version is at v8.x.
I also did:
# pointed to /Applications/Xcode.app/Contents/Developer/usr/bin/lldb-mi before
rm /usr/local/bin/lldb-mi

ln -s /usr/local/opt/llvm/bin/lldb-mi /usr/local/bin/lldb-mi

However when debugging I still don't see any variables listed in the debug window. Breakpoints work ok, as to stack traces.
I'm not sure if the issue is vscode still using the older LLDB or if there's another reason the variables don't show up. Any tips?

Actually, it seems that breakpoints only work with the older version, not the one I try to use after installing with homebrew. So that's two separate issues.
sigh.. it really sucks how broken D's ecosystem is. Sorry to rant out loud but it's giving a really bad impression on my coworkers.

Logging output: https://gist.github.com/AndrejMitrovic/059d5a5128e2cdb0f9f4887d6ca06d96
From this simple dub app:
import std.stdio;

class C
{
	int x;
}

void main()
{
	int x = 100;
	int y = 200;
	int z = x++ + y++;

	auto c = new C();

	c.x = x;
	c.x++;

	writeln(z++);
}

And the debug config:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb-mi",
            "request": "launch",
            "name": "Launch Program",
            "target": "./vstest",
            "cwd": "${workspaceRoot}",
            "valuesFormatting": "parseText",
            "printCalls": true,
            "showDevDebugOutput": true,
            "preLaunchTask": "build"
        }
    ]
}

Ah maybe this is an issue unrelated to code-debug. I can't seem to print the variables even using lldb directly in the terminal:
~/dev/vstest $ lldb ./vstest
(lldb) target create "./vstest"
Current executable set to './vstest' (x86_64).
(lldb) info locals
error: 'info' is not a valid command.
(lldb) b app.d : 11
Breakpoint 1: where = vstest`_Dmain + 19, address = 0x0000000100001607
(lldb) r
Process 11988 launched: '/Users/andrejmitrovic/dev/vstest/vstest' (x86_64)
Process 11988 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x0000000100001607 vstest`_Dmain at app.d:11
   8   	void main()
   9   	{
   10  		int x = 100;
-> 11  		int y = 200;
   12  		int z = x++ + y++;
   13
   14  		auto c = new C();
Target 0: (vstest) stopped.
(lldb) p x
error: use of undeclared identifier 'x'


✨(frontend) Basic LTI rendering

Purpose
Integrate the Web app using the Django LTI server for rendering.
Proposal
This has been influenced by Marsha's approach, but please keep in mind that this implementation is not yet finalized. Our upcoming plans involve substantial code refactoring to incorporate app routing and refine the initialization logic.

[X] Output frontend build in Django static files.
[X] Inject the JS bundle and stylesheet in Django base template.
[X] Render the SPA in a dedicated div.
[X] Implement data transmission to the frontend through the DOM.

Dev environment
Running make run would start the development server, namely the Django app. Then, you could access the frontend through two paths:

The dashboard navigating through http://localhost:8090/dashboards/
The development interface refined by @jmaupetit navigating through http://localhost:8090/develoment/.

Anticipated Improvements and Features:
In the upcoming iterations, we aspire to set up the frontend app initialization process and content loading. Our app's capabilities, while limited, will allow users to:

Select specific resources (Dashboard or plot) through deep linking.
Render a selected dashboard.
Render a selected plot.

The forthcoming enhancements will set the bare minimum user interactions to play with Warren.

@kernicPanel I totally agree with you. I am trying to bootstrap quickly the LTI project, and then focused mostly on connecting parts altogether. Please be sure, I'll give an extra focus in the coming weeks to make the codebase stable and reliable, by adding testing.


IPMX Name

Hi @andrewstarks - The proposed IPMX standard references AMWA-NMOS APIs as underlying APIs.  Gareth raised a good point that if we use the name IPMX in our NMOS IPMX Device Controller then we are referring to a spec/API that is one level up from our NMOS Spec.  Recursive dependency.
EDID Device Controller seems a bit restrictive and refers to the technology and not the actual thing - a bit like calling something a RS-232 Device Controller.
Link to IPMX for reference:
https://ipmx.io/about-2/
I'd vote we pull in issue-14 so we can at least resolve the XYZ Device Controller and the API and use this issue to decide whether EDID Device Controller, (one of several new types of devices that will be added in the future?)
Here is a list of things that use EDIDs so we can perhaps think of a general name for them:
Physical Interfaces
HDMI
Display Port
DVI
Software Virtual Interface
Types of Devices
Monitors
Switches
Repeaters
Gaming Consoles
Video Cards
Software Devices for Recording, Playback, Transformations
What are these? EDID and some associated HDCP data elements define how these can be interacted with.  So in that sense these are all EDID type Devices.
I'd like to have an example of something that is IPMX but not EDID to clarify.

EDID Device Control
EDID Negotiation
Display Negation.
EDID Connection
IS-EDID-CM
Display Device Control


Data Saturday Denmark

eventname
Data Saturday Denmark
date
2023-03-25 09:00:00 -00:00
description
Data Saturday Denmark is a free one-day event for professionals who use the Microsoft data platform. This community event offer content across data management, cloud and hybrid architecture, analytics, business intelligence, AI, and more.

The community revolves around Microsoft Data Platform and Cloud (SQL Server, Power BI, Synapse, Azure, PowerShell, etc), but we invite other topics as well (other cloud vendors, interesting technologies).At this point, we are not able to cover any travel/accommodation expenses.The event is a free in-person event.
registrationurl
No response
rooms
No response
scheduleurl
https://sessionize.com/api/v2/ztilolfa/view/GridSmart
sponsors
No response
speakerlisturl
https://sessionize.com/datasatdk23
volunteerrequesturl
No response
organizers
Jens Vestergaard;https://twitter.com/vestergaardj;jv@t-sql.dk,Brian Bønk Rueløkke;https://twitter.com/brbonk;brianbonk@gmail.com,Mathias Halkjær<EMAIL_ADDRESS>

Yo @brianbonk - If you need to update your event - please update this yaml file
https://github.com/dataplat/DataSaturdays/blob/main/_data/events/datasaturday0032.yml
and raise a PR instead of a new event :-)
I have fixed this one for you - It looks like you have not announced your schedule in sessionize yet - Is that correct?


Command not found ( power-shell )

Hello, I just did a clean install of Arch and have been attempting to install powerline-shell onto my system with little success. I am running the latest version of Arch with zsh as the terminal. I have attempted to install several times, all of which have resulted in the error below.

Any help in resolving this issue would be much appreciated.
Thanks!

Same issue on ubuntu bash on windows 10, after running pip install powerline-shell and adding the necessary setup to .bashrc I get powerline-shell: Command not found

Never mind installing it with git clone and sudo seemed to fix the problem on my side

export PATH="$PATH:$HOME/.local/bin"

@FLY1NN I would try the suggestion from @jD91mZM2 or try to install globally with
pip install powerline-shell

If installing with --user is causing this issue I'm going to change the default suggested installation method.

@b-ryan when I re-installed the tool I omitted the user switch as well. Maybe it helps in general

It helps because it installs it in a different location, which is added into the .profile by default

Thanks for all the suggestions, I will try these out tonight.

You guys are amazing! I completely uninstalled powerline-shell and then reinstalled using
pip install powerline-shell
without --user and it worked like a charm!

I just updated the README to remove --user as the recommended install method.


fail to create feed trigger on explicit 403

the error returned when checking messagehub credentials may not necessarily be due to a 403. this add an explicit check for 403. if the error is not a 403, then continue on as if though we'd received a 200 and let the provider disable the trigger if, when it does its check before creating the consumer, it fails with 403


Essence paragraph

Documentation Is:

[X] Missing or needed?
[ ] Confusing
[ ] Not sure?

Please Explain in Detail...

[x] Assess the team against the Essence standard(v1.2)

What is the current state
Why?
What are the obstacles to reach the next state

[x] Document how you improved during the course, and where further improvement can be made
[x] (P+) Argue critically about the benefits, drawbacks, and limitations of your work carried out, in
the context of current software engineering practice, such as the SEMAT kernel (covering alphas other
than Team/Way of Working).

Your Proposal for Changes
N/A
Example
No response

Closed as completed via #6.


Compile Error for Local Dependencies on Windows

deps.zig fails to compile with a message like so:
$ zig build run-simple
C:\Users\Alexis Brodeur\Projects\github.com\brodeuralexis\webgpu\deps.zig:67:129: error: invalid escape character: 's'
        .pkg = Pkg{ .name = "webgpu-backend-dummy", .source = .{ .path = dirs._5lfigtl33bkz ++ "/./modules/webgpu-backend-dummy\src/backend.zig" }, .dependencies = null },

Both of these snippets of code make it so deps.zig generated on Windows does not compile if local dependencies are used:
https://github.com/nektro/zigmod/blob/6a2d664e1236c62f55f02f74b51c067e57a81b63/src/common.zig#L287
This uses the primary separator, which is \ on Windows.
https://github.com/nektro/zigmod/blob/6a2d664e1236c62f55f02f74b51c067e57a81b63/src/cmd/fetch.zig#L287-L293
This does not escape special characters.

Found a workaround.
From:
dependencies:
  - src: local package-name package-path

To:
dependencies:
  - src: local package-name package-path/

Note the / at the end of the package path.


Hello could I be a tester please?

Hello I would like to test out your skill my email address is
<EMAIL_ADDRESS>

Added


/nekocfg command does nothing, gear icon just opens /neko

Title, /nekocfg gives me an error that it doesn't exist. /neko works fine.
Good plugin btw :3

I suspect that you have version 1.0.7 installed. That is the version which is currently in the official dalamud repository.  Version 1.1.0 will be pushed to the official repo sometime after the launch of FFXIV 6.2
The /nekocfg command and the configuration menu was only added in version 1.1.0 which you can (for now) only download by adding https://raw.githubusercontent.com/Meisterlala/NekoFans/master/repo.json as a custom repository in the experimental settings.
If the description of the plugin in the plugin installer contains the sentence: Multiple Image APIs are supported, allowing you to look at Catboys, Waifus, Cats, Dogs and more, then you have version 1.1.0.
If you don't see that and the plugin description also doesn't show you the /nekocfg command under the /neko command then you still have version 1.0.7

Ah, that's definitely what I have, which is odd because I did add the repo before I installed it. Guess I'll wait till it's pushed to the official repo. Thank you!


[R] CSVIter parsing strings in R

I found that CSVIter doesn't take strings. I have fake.csv:
99,0.9,'good',"This is good"
77,0.7,'bad',"This is bad"

If I use CSVIter:
it <- mx.io.CSVIter(
  data.csv = 'fake.csv',
  data.shape = c(1,4),
  batch.size = 1
)
it$iter.next()
dlist <- it$value()
dlist$data

I get:
, , 1

     [,1] [,2] [,3] [,4]
[1,]   99  0.9    0    0

Is there a workaround to parse strings?
 If is NULL, all labels will be returned as 0}

Since that seems to accept strings?

Example of a similar solution can be found in https://github.com/dmlc/mxnet/issues/4105


(maint) quote file path in file_contents_on and file_exists_on

To give more background, puppet-code acceptance failed with bellow error. It looks that if the "c:\" path is passed as parameter from directly from cygwin to powershell without " it gets messed up.
I updated in this PR the two cases hit by my tests (while I still think file_exists_on is not really working, as it never fails, with or without the change)
    naval-racetrack.delivery.puppetlabs.net (windows2012r2-64-1) 15:38:23$ powershell.exe -ExecutionPolicy Bypass -InputFormat None -NoLogo -NoProfile -NonInteractive -Command Test-Path C:\Windows\TEMP\install-puppet-2020-05-15_15.38.14.log
      False

    naval-racetrack.delivery.puppetlabs.net (windows2012r2-64-1) executed in 0.92 seconds

    naval-racetrack.delivery.puppetlabs.net (windows2012r2-64-1) 15:38:24$ powershell.exe -ExecutionPolicy Bypass -InputFormat None -NoLogo -NoProfile -NonInteractive -Command Get-Content -Raw -Path C:\Windows\TEMP\install-puppet-2020-05-15_15.38.14.log
      Get-Content : Cannot find path 'C:\cygwin64\home\Administrator\WindowsTEMPinsta
      ll-puppet-2020-05-15_15.38.14.log' because it does not exist.
      At line:1 char:1
      + Get-Content -Raw -Path C:WindowsTEMPinstall-puppet-2020-05-15_15.38.14.log
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          + CategoryInfo          : ObjectNotFound: (C:\cygwin64\hom...15_15.38.14.l
         og:String) [Get-Content], ItemNotFoundException
          + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo
         ntentCommand

This looks very similar to https://github.com/puppetlabs/beaker/pull/1626#issuecomment-590594406 are you using a beaker-puppet with this change https://github.com/puppetlabs/beaker-puppet/pull/135

@donoghuc , I will recheck as the PR you mention was not merged/released at that time.

Problem is already solved in beaker 4.23.1


BF: make sorting case sensitive

Previously, sorting was case insensitive, so that the words would actually be grouped together. However, within a word, it was not sorted.
GROUPLETTERS does not do what we want, but using LOCALE does (at least with 'en_US.UTF-8').
For now, I am choosing to use whatever the user has configured on their OS. That makes sense to me, respecting their choice. If this ends up biting us in practice, then we'll simply hardcode it or make it a configurable option in .onyo/config.
fix #651

RTD failure is unrelated.

I filed #653 to unblock that task from this PR.

+1 from Ben on Matrix. Merging!


removing underscore from partials properly

Apparently I didn't do it right the first time, this one actually works.

Thanks Aaron. The test looks a lot more solid too :)


fix broken layout issues

Closing since Durandal has been superseded by Aurelia just shy of four years ago.


add pfocr to BTE

involves updating the smartapi yaml for pfocr + adding up-to-date x-bte annotation.
May involve deleting and registering pfocr again into the registry?

Done, with BioThings PFOCR registered again and ingested by BTE.
Ongoing issue to fix edge-attributes from PFOCR
But I think the main part of this issue is done


Error: Cannot find module 'C:\index-config'

I just installed coinx and when trying to configure it with my API keys, I get the following error message:
C:\>coinx config poloniex
module.js:487
    throw err;
    ^

Error: Cannot find module 'C:\index-config'
    at Function.Module._resolveFilename (module.js:485:15)
    at Function.Module._load (module.js:437:25)
    at Function.Module.runMain (module.js:605:10)
    at startup (bootstrap_node.js:158:16)
    at bootstrap_node.js:575:3

I'm using Windows 10 64-bit with node v8.0.0

Is coinx installed globally?

Yes; I installed it globally. After opening this bug, I saw the comment from @jgfaust on issue #4 about renaming all coinx-.js files to index-.js in the root directory. I forked your project and gave that a shot. This fixed the problem in Windows, but when I tested it in Linux, I'm now getting an error message saying coinx-config(1) does not exist, try --help.

Interesting. I don't have access to a Windows machine - would you mind trying something for me?

Change the files back to coinx-.js
Rename index.js to coinx.js
In package.json, change main to coinx.js, and change bin:coinx to './coinx.js'

Seems to work ok on linux, perhaps it will help on windows too?

If that doesn't work, can you try changing package.json to use commander 2.6.0? Looks like the issue may be related.

Renaming the index.js file seemed to work great. Thank you!


feat: update 'published' and 'reviewedDate' to use 'firstPublished'

This commit updates the 'published' and 'reviewedDate' properties in the 'reviewedPreprintSnippet' function to use 'firstPublished' instead of 'published'. Also, it adds 'firstPublished' as a new property in the 'EnhancedArticleNoContent' type. Additionally, it changes the import path of 'Author' in the 'reviewed-preprints.page.test.ts' file.

This shouldn't be deployed until after: https://github.com/elifesciences/enhanced-preprints-server/pull/923


bin setup

the tool tip on Receipt Bin Code comes to this page.
how do we setup Receipt Bin Codes?
Can you expand on the Bin setup too please siting an example?
[Enter feedback here]

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

ID: b90de8f3-c15f-8c3a-975a-152251db24bf
Version Independent ID: 32f5d631-6591-a74f-25eb-dffbfd1d73ce
Content: Set Up a Location Card and Define Transfer Routes - Business Central
Content Source: business-central/inventory-how-setup-locations.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: edupont

Hello Ben,
Thank you for your feedback! You're right that the article is a bit too simplistic, but there are hints in the embedded video. There are also good learnings in the walkthrough for basic warehousing that we updated last week. The walkthrough for advanced warehousing will be updated later this week.
Essentially, bins are a way to group inventory in a location. You can choose to create separate bins for receipts, shipments, and other warehouse operations. Once bins are defined for a location, you can then assign them on the location card. For example, create a bin for receiving inventory, and then specify that bin in the Receipt Bin Code field.
You can read about the background in the design details here (not yet updated to reflect current demo data): https://docs.microsoft.com/en-us/dynamics365/business-central/design-details-warehouse-setup
We're in process of updating the docs for warehousing and will roll out updates over the coming months.

Now live.


Armchair & UIAlertView

I've just installed Armchair and found that it uses UIAlertView which was deprecated in IOS9. Do you plan on upgrading it?

There is no UIAlertView in the source. There is UIAlertController though, and it also uses SKStoreReviewController if you set it that way.


Live queries (push notifications)

I am moving this into a separate issue from a broad issue of #111.
@mjjansen mentioned push notifications. And @jonhoo replied:

Push notifications (basically, pushing parts of the data-flow to the client) is something that's definitely on our radar, and was actually one of the motivations for using data-flow in the first place. Data-flow is so amenable to distribution that in theory this should just be a matter of moving some of the data-flow nodes to a client machine. In practice it gets a little more tricky though. We don't have an implementation of it currently, and it's not at the top of our roadmap, but it is a feature we'd love to see!

I commented:

So +1 for push notifications (or I would say live query, I think this is the more common term). I do not think Noria has to provide any web API here, just expose things through Rust API, and then users can hook their own logic in Rust to push them to websockets or whatever.

And @jonhoo replied:

So, push notifications are tricky because they imply full materialization everywhere, which comes at a steep cost. There might be a good way to register interest in keys and then subscribe to updates for those keys, but that's not something we're actively working on. Might be a neat additional feature to add eventually though — it shouldn't be too hard, as most of the infrastructure is already there.

push notifications are tricky because they imply full materialization everywhere

Hm, I am not sure if I follow here. Why would that be the case. It only implies full materialization for active "live queries"?
But couldn't we see the client as where the fully materialized view should happen, while Noria does not have to even store the materialized view itself, just keep computing any changes and pushing them to the client?
One common use case I have seen with live queries where it becomes tricky (and why I got interested in Noria's support for changing queries at runtime) is pagination and infinity scroll. With existing systems which support live queries you have to re-create a live query with new page limits. With Noria you would only update the limits on existing query. In this way you would also limit what has to be fully materialized only to what is really shown to the user in the browser window (plus maybe a bit extra just to compensate for latency). So as you would scroll Noria could be told which values is it able to forget about and which ones to keep up-to-date. And for UI this would translate great: the displayed values outside of the visible area could be kept shown but would not be updating anymore. (Of course if you want to allow ctrl+f search in the browser over latest values you would have to keep updating them.)
One important aspect in practice is that not everything has to update in real-time. To my understanding you are already doing updates in batches inside Noria. And similarly would be for a live query. You would batch updates send to the client. If I could then for each subscription to a live query define the expected interval for this batching, I could control and limit the resource utilization. If I need refresh every 10 seconds, then you do not have to really update the materialized view more often (except if some other query comes in from another client, for same data/view).
I think another question here is about backpressure. What happens when the client (or connection to the client) cannot consume updates as fast as you are generating them. With internal materialized views you maybe do not encounter that. You can write updates to underlying database store, but over the network such limits might happen. Noria could detect this in that case and also slow down in how much it has to keep materialized views up-to-date.
I find this an interesting read. It is a completely opposite design that you have though. :-)

Sorry, when I say "full materialization", I mean full materialization for the live query, not full materialization as in "all results of all queries". Where this distinction comes up is if you have a query like
SELECT x FROM y WHERE z = ?

Full materialization implies that the results are kept for all values of z, whereas partial materialization would mean that results are only kept for the values of z that the application has queried for. Noria's partial materialization discards writes for keys that have not been read, which means that it does not produce any deltas for them, so the output stream of updates would not have all changes! The reason for this is that we need the current state for many operators in order to produce the delta. Consider something like a count operator. If the count for z = 7 isn't known, then we cannot produce the updated count when we receive a new input with z = 7.
As for pagination and infinite scroll, that's somewhere where I think we'll need support for cursors. In theory this shouldn't be too hard to add to Noria, but it's not something that we currently have.
The other concerns you list (batching and backpressure) are both good points, and would become relevant once we add support for client-side streams. This is something that's been on our roadmap for a while, but the research interests just haven't quite lined up with them yet. That is, there are more important issues to fix first from a research perspective (like fault tolerance and more robust sharding).

Thanks for this explanation. I am not sure though why would then full materialization be needed and not just partial materialization for particular values of z the user is requesting in their query? So at least, why live queries imply full materialization everywhere? I think it applies non-partial materialization only when using aggregation operators which might require also information about rows not directly exposed to the user in their query (like min and max).
From my experience from other similar systems in fact the hardest problem is handling order + limit. Because every time any other row changes outside of the limit you still have to check if it now falls inside the limit, given the order. So in that case I think you would need something like full materialization for the whole unlimited query, even if just a small subset is really part of the result. Not sure if you are implementing it this way though, it looks inefficient. :-)

As for pagination and infinite scroll, that's somewhere where I think we'll need support for cursors.

Hm, are you sure? I thought that the nature of Noria is that cursors would not really be needed. It would just be a change to an existing query? To increase the limit for example.

Right, so that was my proposal — a mechanism would have to be added for the application to register interest in particular values for z. Once that's in place, then they could listen for a stream of updates to the materialization of z. I guess my phrasing wasn't great: I meant to say that currently streaming implies full materialization, or we'd need some mechanism for saying "materialize this key and then give me its stream".
Yup, order + limit is tricky, and requires at the very least some kind of support for range indices, which Noria does not currently have (although it is work in progress — cc @jonathanGB). I think effectively the way to implement it is using cursors. The external interface might not need to mention cursors (like in DB2 and friends), but internally it'd likely be implemented as such. You need some kind of representation of how far through a resultset a query has gotten, and where it should continue for subsequent reads.

I think effectively the way to implement it is using cursors.

I agree. Given how common such use case (pagination or infinity scroll) is in my experience with live queries, I agree that having a special case for that would be probably useful.

One thing I remembered now is that there is a middle ground here: maybe live queries could work that you just notify the client that the view has changed without having to compute the whole thing. And then the client could go back and simply re-query. Given how Noria works, that re-query would be fast/cheap (in comparison with other systems where you have to recompute the whole thing). That would also allow clients to throttle how often they want updates from the server.

@mitar It's true that Noria could provide that feature too, though that still has the same issue: Noria won't know when a key that hasn't been materialized changes, and so also couldn't inform clients of that case.


Remove unregistered camera_gi provider

gi and pygst providers were removed (#4224) but camera_gi still remains in the repository.
It was apparently disabled in favor of pygst (also removed) in https://github.com/kivy/kivy/commit/de22f3aef91edad371ab4ea38dff7fd68212e5e4 (2013), and https://github.com/kivy/kivy/commit/61fd64d98854804a8af1d893d5a5ac69b63fd210 removes the last relic in __init__.py.
I guess this should just be removed, and Kivy no longer supports camera via gstreamer at all?
Edit: or is it intended that you import this explicitly if you want to use it? It seems like pygst and the others would have been left as well if that was the philosophy, plus the file has no code updates since late 2013.
(reported by user C_D on IRC)

Yes, the gi camera provider was left there because there was no other alternative left for gstreamer.
There is also a leftover at https://github.com/kivy/kivy/blob/68793c0669ef14c78768a3560e2012449c966693/kivy/init.py#L223.
It could be tested if it still works with a recent Gstreamer version, if not, let's remove it. Otherwise it could be listed again in camera/__init__.py.

Just an FYI, I've been using camera_gi successfully with gstreamer version 1.10.5 (latest available for Fedora 25) for a couple of months now. It's been perfectly solid for me, and I've found the code is easy to extend as needed.

Yes, don't remove it :)


This customer has no attached payment source

So I was reading about the cards vs. sources and using old stripe api's.  But, the old api isn't working for me.  Are there any links about manually switching this?  Maybe I'm just having some misordering problems?  Hell I don't know.  In my gem file stripe is before koudoku, but both initialize Stripe.api_version = '2015-01-11'.  I'm using figaro, but that's all set up right because I have app/views/charges/new setup and its working for one time payments.  It's creating customers on my dashboard.  But I'm just befuddled.  Anyone still having this issue?

I am running into this issue as well.

I'm same this exp:


[RESTEASY-1746] Provide support for multi valued resource method array type arguments

This PR is about providing support for custom conversion between multi valued param (queryParam, MatrixPartam, headerParam...) and array type arguments as it has been done in https://github.com/resteasy/Resteasy/pull/1251

This looks ok to me. @ronsigal , do you want to have a look too, given you reviewed RESTEASY-1566 previously?

@asoldano, it looks OK to me.
@NicoNes, I've attached a version of Chapter 25 "String marshalling for String based @*Param" of the Resteasy User Guide with an array example. Could you take a look, correct it if necessary, and include it with your pull request? Thanks.


Blank results

I use this field in Nova 3.6 like this:
           Multiselect::make('searchtags')
                ->placeholder('Search tag...')
                ->groupSelect(true)
                ->belongsToMany(\App\Nova\AnimalSearchtag::class),

Its showing the name of the already selected tags, but all the results when searching for new tags do not display key or value. (they are just blank results)
How do I define the name of the key and value fields to be displayed?

Hi! The belongsToMany and groupSelect are incompatible options, please try removing the groupSelect and see if it works then.