before() in wdio.conf.js is not executing the spec file which I would like to execute before all other spec files.

before() in wdio.conf.js is not executing the spec file which I would like to execute before all other spec files.
code snippet:
wdio.conf.js
before (capabilities, {'./specs/login.spec.js' : login, './specs/socialstudies.spec.js': social}) {
require('babel-register');
},
Please let me know if this is not the right format.
Thanks,
Hemalatha Udattu

Hi
Can someone give me an update on this ticket please.
Thanks,
Hemalatha Udattu


Feature: Convert Grafana dashboards to KubeSphere monitoring templates

Grafana is a successful and widely used observability tool.  In future releases, we should support importing dashboards from Grafana dashboard templates. It can be implemented with a binary handing this conversion.

Contributors are welcomed to create this tool


White lines though images on certain pdfs

On pdfs where the creation software splits the image into smaller chunks, pdf.js will produce a white line between them while adobe reader renders them correctly.
Example pdf:
https://www.dropbox.com/s/gt1b2y9bgf06pam/Doc2.pdf
Edit: may be related to issue #3331 except with images instead of filled rectangles.

Here's another example.  But it includes a solution.
To fix it up, I got the original image, resized it and paste it into the document that I made the pdf with.
I was using MSword, just changing the size in msword didn't help.  But resizing the original image and then pasting it again fixed it.  Below is an example of two different images resized...
http://www.pdf-archive.com/2015/03/07/test2200-2/test2200.pdf
I made the pdf with msword, pdfcreator v2.0.2
This problem doesn't happen in Google Chrome.  But it happens in Firefox, and the evince app in linux.

Has there been any progress made regarding this issue? Could someone point me in the right direction in regards to where PDF.JS begins to attach each object of the pdf onto the canvas?
I assume the issue is caused by incorrectly stitching multiple images together. In the first sample PDF provided, the main image is actually composed of 7 smaller/sliced images.

I think the easiest way to debug this is to use gulp server locally and prepend #pdfBug=Stepper to the URL, for example http://localhost:8888/web/viewer.html#pdfBug=Stepper. This will open the PDF debugging utilities and allow you to step through the drawing operations so you can see which operation causes the defect. More information can be found at https://github.com/mozilla/pdf.js/wiki/Debugging-pdf.js#stepper.

I have looked into this and I think I have found the problem, although, I am not 100% sure how drawing works when width is more accurate than pixels can account for, but i have an idea.
It appears that when calling .drawImage on our canvas object, we do so given the exact height and width of the object that we wish to draw (image, rectangle, etc). By doing this, without taking pixel width into account, it seems that we are leaving some pixels partially colored. When stitching multiple parallel images together, this leaves a visible gap between them.
Ex. Given a pixel width of 0.5 and an image with width 1.02, we are coloring 2 full pixels and then leaving the 3rd pixel partially transparent. The next image to be stitched then starts at the 4th pixel, leaving the gap that the 3rd pixel has generated.
Using this sample file (CompWiz_Page1.pdf), which draws many rectangles on the canvas to create a gradient effect, I have came up with the following solution.
In Canvas.constructPath(), we are creating the rectangle's that we wish to attach to our canvas. In order to account for Pixel Size, I made the following modifications (see comments):
BEFORE
    constructPath: function CanvasGraphics_constructPath(ops, args) {
      var ctx = this.ctx;
      var current = this.current;
      var x = current.x, y = current.y;
      for (var i = 0, j = 0, ii = ops.length; i < ii; i++) {
        switch (ops[i] | 0) {
          case OPS.rectangle:
            x = args[j++];
            y = args[j++];
            var width = args[j++];
            var height = args[j++];
            if (width === 0) {
              width = this.getSinglePixelWidth();
            }
            if (height === 0) {
              height = this.getSinglePixelWidth();
            }
            var xw = x + width;
            var yh = y + height;

AFTER
    constructPath: function CanvasGraphics_constructPath(ops, args) {
      var ctx = this.ctx;
      var current = this.current;
      var x = current.x, y = current.y;
      var origX, origY, pixelSize = this.getSinglePixelWidth();
      for (var i = 0, j = 0, ii = ops.length; i < ii; i++) {
        switch (ops[i] | 0) {
          case OPS.rectangle:
            origX = args[0];
            origY = args[1];
            //Round down to the nearest multiple of our pixel width
            x = Math.floor(args[j++]/pixelSize)*pixelSize;
            y = Math.floor(args[j++]/pixelSize)*pixelSize;
            var width = args[j++];
            var height = args[j++];
            if (width === 0) {
              width = this.getSinglePixelWidth();
            }
            if (height === 0) {
              height = this.getSinglePixelWidth();
            }
            //Use the non rounded original x/y values to round up to nearest pixel width multiple.
            var xw = Math.ceil((origX + width)/pixelSize)*pixelSize;
            var yh = Math.ceil((origY + height)/pixelSize)*pixelSize;

Doing this ensures that each pixel is fully colored and there is no transparency between stitched images.
I was able to fix the line issue that Doc2 (first example file attached in OP comment) has with his image using the same logic and modifying Canvas.paintJpegXObject() and Canvas.paintInlineImageXObject(). The following lines were added before writing the images to the canvas:
var pixelSize = this.getSinglePixelWidth();
h = Math.ceil(h/pixelSize)*pixelSize;
w = Math.ceil(w/pixelSize)*pixelSize;

If this is a viable solution, I think that it would need to be implemented before each drawing interaction with our canvas. If that is the case, I'd be happy to work on its implementation.

this.getSinglePixelWidth();
If this is a viable solution, I think that it would need to be implemented before each drawing interaction with our canvas. If that is the case, I'd be happy to work on its implementation.

Please note that that particular method may be "expensive" (performance wise), so using it everywhere would probably require very careful benchmarking; please refer to e.g. the discussion starting in https://github.com/mozilla/pdf.js/pull/4615#discussion_r11567342 and the results in https://github.com/mozilla/pdf.js/pull/4615#issuecomment-40874837.

If you're interested in benchmarking this, you can use our benchmarking tool as described on https://github.com/mozilla/pdf.js/wiki/Benchmarking-your-changes.

Interesting, I just got caught up on the topic, I was unaware that this solution has already been thought about.
Is it possible to see at what number of calls to .getSinglePixelWidth() we start to see a regression in performance? I am not familiar with how the #pdfbug=Stepper works, but if pdf.js has access to the load operations and can count the number of calls to Restore/Transform/ShowText (the methods resetting our cache), we can determine the amount of times we would need to call .getPixelWidth().
If that value falls under our performance regression threshold, we can proceed to load the document with accurate pixel measurements.
Something like this would allow for higher quality document display in standard cases while avoiding the performance regression seen in extreme cases.

I think the stepper should provide you with that. It shows you when and in which order it performs a drawing operation, for example restore/transform since they are native PDF commands.

Is it possible to see at what number of calls to .getSinglePixelWidth() we start to see a regression in performance?

That sounds really difficult, since it seems like it'd be highly dependant on e.g. the complexity and the ordering of rendering OPS of particular PDF files; not to mention dependent on general computer/device performance.

but if pdf.js has access to the load operations and can count the number of calls to Restore/Transform/ShowText (the methods resetting our cache),

There would be overhead/complexity related to counting the operations as well, especially considering that only some ShowText commands are resetting the cachedGetSinglePixelWidth cache.

Something like this would allow for higher quality document display in standard cases while avoiding the performance regression seen in extreme cases.

That seems immediately problematic, since it would introduce inconsistent rendering behaviour for different kinds of PDF files. (Some files rendering correctly, and others not, doesn't seem like great UX.)

It might happen that it's deemed OK to make use of getSinglePixelWidth() more in canvas.js, even if it would result in a slight regression in edge-cases (such as e.g. PDF files containing complex maps).
In the past, slight regressions have been accepted for significant rendering improvements; but without actual benchmarking results[1], especially with larger and more complex PDF files, it's mostly speculation at this point :-)
I didn't mean to deter you from looking into this with https://github.com/mozilla/pdf.js/issues/3351#issuecomment-410348027; sorry if it came off that way!
Finally, one piece of advice (based on experience): Before you put a lot of time and effort into doing multiple benchmarks runs, make sure that you run the entire test-suite first to check that there aren't any obvious regressions from your changes.[2]

[1] One small advice regarding https://github.com/mozilla/pdf.js/wiki/Benchmarking-your-changes. The example contains "rounds": 20, however in practice you often need to use at least "rounds": 50, to get statically significant results.
[2] There's nothing worse than having to re-do entire benchmark runs just because of some simple error in code you wrote yourself. Don't ask me how I know this ;-)

Thank you for the through reply. I have started to mess around with the benchmark testing. Are there specific files which are noteworthy? Or is it best to run the benchmark on the whole list of test PDF's?

I think the PDF file in #2813 may be a good one for your benchmark since it's a complicated PDF with a lot of drawing operations. Other than the PDF files in this issue, I think taking a subset of let's say 20 random PDF files from the existing suite should be sufficient. Perhaps @Snuffleupagus has more ideas though.

Here are the results when testing 50 rounds on the above document:
-- Grouped By browser, stat --
browser | stat         | Count | Baseline(ms) | Current(ms) | +/- |    %  | Result(P<.05)
------- | ------------ | ----- | ------------ | ----------- | --- | ----- | -------------
Firefox | Overall      |    50 |        16139 |       16974 | 834 |  5.17 |
Firefox | Page Request |    50 |           10 |          10 |   0 | -2.53 |
Firefox | Rendering    |    50 |        16129 |       16963 | 834 |  5.17 |

What exactly is it that I am looking for from these results? Is there a rule of thumb as to what range of values from the baseline are acceptable?

What exactly is it that I am looking for from these results? Is there a rule of thumb as to what range of values from the baseline are acceptable?

Usually we look at the t-test column Result(P<.05). In this case it looks like the change isn't statistically significant since it's not labeled 'slower' or 'faster'. It's is kind of interesting that the mean of rendering is 5% worse and it's still not significant. Can you attach the json file that the benchmark  generates?

browser | stat         | Count | Baseline(ms) | Current(ms) |  +/- |     %  | Result(P<.05)
------- | ------------ | ----- | ------------ | ----------- | ---- | ------ | -------------
Firefox | Overall      |    50 |        17427 |       16954 | -474 |  -2.72 |
Firefox | Page Request |    50 |           11 |           9 |   -2 | -14.34 |
Firefox | Rendering    |    50 |        17416 |       16944 | -472 |  -2.71 |

browser | stat         | Count | Baseline(ms) | Current(ms) |   +/- |     %  | Result(P<.05)
------- | ------------ | ----- | ------------ | ----------- | ----- | ------ | -------------
Firefox | Overall      |    50 |        18640 |       15158 | -3481 | -18.68 |        faster
Firefox | Page Request |    50 |           11 |          10 |    -1 |  -5.59 |
Firefox | Rendering    |    50 |        18629 |       15148 | -3481 | -18.69 |        faster

I ran the benchmark 2 more times and above are the results. It seems strange to me that they differ so much from one another. Is this normal?
Here is the resulting json from the last current run (Renamed to .txt because .json uploading is not supported).
current.txt

Is this normal?

Yes, benchmarking browser's can be very fickle. One issue with the current benchmark setup is that it basically just re-runs rendering a page many times in the same browser page, which is not a realistic scenario in the real world (usually we'll just render a page once, so first time paint is the most important). What we really should probably do is restart the browser on each round or run reach round under a different domain so the caches are clean. This is all beyond the scope of this bug, but if you're interested in working on it, I'd be happy to help.
Just to be clear on your above results, did you run it so baseline = no changes and current = with your changes? It seems odd that now it is showing up as faster vs your previous results.

That is a great point about the testing. After this is solved, I may dive into that to see what can be done.
For testing:
Baseline = Original code w/ no changes
Current = code w/ changes
For each test, I regenerated both the baseline and current results.

Are there any other tests that I should be running to check performance results?

Doesn't look like it's causing issues, so feel free to open up a PR.

There are different issues here:

one with images;
one with paths.

The underlying problems are slightly different.
About images, we must draw them at integer coordinates and with integer dimensions, according to MDN, it should help to improve performance and in the pdf context it should remove the thin lines we have between two tiles.
Anyway it should help to fix pdfs like:
Doc2.pdf
About paths, the situation is slightly different, after apply current transformation we must round and add 0.5.
The 0.5 will guarantee that 1px lines are really 1px lines: there is an explanation on MDN to explain how lines are drawing in a canvas:

The extra transparency added around lines can lead to some wrong color rendering with very close thin lines see bug 1657838.
So we probably need to round correctly coordinates ourselves which should induce a perf penalty but it could be more or less offset by a perf improvement when drawing, so for sure, we need to measure that.

Any progress ?

Another way to reproduce this bug, but with rectangles again instead of images;

Write some code in Sublime Text, using a non-white background
Edit->Copy as HTML
Paste into a Word doc
Export as PDF

The Word doc renders the background of the pasted text as a solid color, and the resulting PDF looks correct in Adobe and Chrome, but Firefox is bleeding through some of the background color in between each line of the code.

issue_3351_sample.pdf


Project health

This isn't ready yet, but while I peck at it I want some other computer to run the tests so I don't have to.

Build failed https://gradle.com/s/sf4gw7v5vzu6c

Build failed https://gradle.com/s/ddrhglwtucone

Build failed https://gradle.com/s/2nqyxf3bjvitq


Thoughts on the Form component

Hi @shadcn,
This is the best project I have come across really appreciate the work, I would like to highlight performance-related stuff on the form component, which works perfectly but due to React Context on top of the Input component renders the Input again and again on every change in the HTML input which defies the react-hook-form working which works on ref
Solution and Changes:

Refactor FormField to use the useController hook
Remove the React Context which rerenders child components

@tushar1998 can you provide an example?

Yep here in code sandbox
https://codesandbox.io/s/goofy-cori-l9pxzh

Yep here in code sandbox
https://codesandbox.io/s/goofy-cori-l9pxzh

This example is still rerendering on every keystroke to me.

@mnpqraven I have added a render count on the top right corner in codesandbox example

@tushar1998 Totally agree with you. I want to read your solution, but it did not proceed from loading page. Did you remove the codesnadbox?

Since this discussing is getting attention I will make a repository for this and attach it in the issue itself
cc: @isac322

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


[WIP] Initial changes to Parser

Some points:

The update syn crate isn't compatible with error_chain, so we aren't using that now in parse.rs. Need inputs on current error handling code in parse.rs on ways to improve it.

Also in the current parsing code, its an error to not have a comma after the very last field-value pair declaration of any struct type construct in app! { }. Wondering how to parse an optional comma at the end ?

I am currently working on refactoring things inside cortex-m-rtfm. Will update soon on that !

@creativcoder thanks for working on this. Sorry that I haven't been able to comment earlier.

The update syn crate isn't compatible with error_chain

You mean because Synom returns Result<Self, ParseError> and we can't convert other errors into a ParseError?
I think we could split the parsing in two stages: the first one is a Synom implementation that turns the contents of the app! macro into a list of key value pairs. In the second stage we turn that list into an App struct. In the second stage we can use error-chain / failure along with custom error types.
The thing is that, for example, having two keys named device is not a parsing error, per se, but a well-formedness error that should be caught after parsing. So it makes sense to split what used to be the parsing in two stages.

Wondering how to parse an optional comma at the end ?

Hmm, I have used Punctuated for that purpose before, instead of many0!.

I am currently working on refactoring things inside cortex-m-rtfm. Will update soon on that !

Let me know if have time to continue working on this. I'll likely need the parser in place (very) soon as I want to prototype some new RTFM features that require new syntax.

Okay, i'll make progress over your suggestions this weekend. I'll let you know if by Sunday if i got time to continue working on this :)

into a list of key value pairs

@japaric I am a bit unclear on this. So do you mean that values (in the list of key value pairs) have to be of the same type ? But when parsing they won't be of the same type (device's value is Path, idle's value is Idle). Are you suggesting i would store a Box<Synom> as values ?

I was thinking of first parsing the contents of app! (using Synom) into Vec<(Ident, TokenStream)>, do some well formedness checks on that (e.g. error on a duplicate "device" key, which is not a parser error so this doesn't involve the Synom trait) and then proceed to parse the values (using synom).

Tried pinging you on irc #rust-embedded. Anyways posting it here; Need a quick help in my new changes on parsing the value as a TokenStream. Made a gist which elaborates the issue:
https://gist.github.com/creativcoder/4ecb40f2a3853341fe3348238184cb4b#file-parse-rs-L12

I suppose there's no parser for "parse until comma". As the value will either be some delimited by braces or a path (for the device key). How about parsing the value into a Either<TokenStream, Path> where the TokenStream is the full contents inside the braces? Does that sound doable?


Fix swallowed error

Looks like the return nil that was there before was probably a typo.

Good catch. +1. Add a note to the CHANGELOG to.

If only golint would catch that lol.  Doh!  Good catch!


[LG & Expression] Switch Antlr.Runtime to Antlr.Runtime.Standard

Fixes #4776
Description
Change the Antlr library
Specific Changes

Remove the dependency of "Antlr4.Runtime" and "Antlr4.CodeGenerator" in Adaptive.Expressions and LanguageGeneration.
Add "Antlr4.Runtime.Standard" library instead
Add Lexer/Parser/Visotor/Listener files generated by the Antlr command-line tool.

Somehow CI is failing.
Also, can you add a readme.md file to description the process of generating the Generated folder


Additional local mod handling options

I have a handful of mods repos/locally developed ones that i need to symlink every time i update, it would be nice if the program kept track of symlinks and recreated them after updating

I have a handful of mods repos/locally developed ones that i need to symlink every time i update, it would be nice if the program kept track of symlinks and recreated them after updating

Think about it. Why have links been available in the NTFS system for a long time and at the same time, Microsoft does its best to prevent users from using the links. It's not just like that. Right?


"exec format error"

I installed (using the instructions per #8 - I think that should probably be corrected in the README) and am getting "zsh: exec format error". A bit of googling implies that this means the executable that was installed was somehow intended for a different chip architecture? (I'm on OSX 12.2 on Apple silicon, if that matters).
Is there any way I can run this program without becoming a go developer?
Edit: screen shot of install process in case it's helpful, no errors though.

Can you execute go env command in your shell and post here the output?

using the instructions per https://github.com/strang1ato/tibivi/issues/8 - I think that should probably be corrected in the README

Sure, I will correct that soon in the future.


Enable devmode liveness test

@aludvik When I ran this test locally it would produce blocks too quickly, and so only 1 batch would be in every block. I set the min_wait_time to 3 and the max_wait_time to 5. I had good results with that.


panic: Should never need to recheck imports/constraints from root during solve

What version of dep are you using (dep version)?
1963157
What dep command did you run?
I have a library (github.com/F21/some-lib) in my GOPATH. I then imported the library and used it in my app. After doing so, I used dep to add the library:
$ dep ensure -v -add github.com/F21/some-lib
Root project is "github.com/F21/some-app"
 1 transitively valid internal packages
 8 external packages imported from 8 projects
(0)   ✓ select (root)
(1)     ? revisit github.com/F21/some-lib to add 1 pkgs
panic: Should never need to recheck imports/constraints from root during solve

goroutine 1 [running]:
github.com/golang/dep/internal/gps.(*solver).getImportsAndConstraintsOf(0xc042398600, 0xc0421d6060, 0x21, 0x0, 0x0, 0xb13a00, 0xb67000, 0xc04228a200, 0x1, 0x1, ...)
        D:/work/src/github.com/golang/dep/internal/gps/solver.go:617 +0xeb6
github.com/golang/dep/internal/gps.(*solver).check(0xc042398600, 0xc0421d6060, 0x21, 0x0, 0x0, 0xb13a00, 0xb67000, 0xc04228a200, 0x1, 0x1, ...)
        D:/work/src/github.com/golang/dep/internal/gps/satisfy.go:43 +0x1f7
github.com/golang/dep/internal/gps.(*solver).solve(0xc042398600, 0x0, 0x0, 0xc042381ad0)
        D:/work/src/github.com/golang/dep/internal/gps/solver.go:540 +0x33a
github.com/golang/dep/internal/gps.(*solver).Solve(0xc042398600, 0x38, 0xb0f040, 0xb667d0, 0xc04216e330)
        D:/work/src/github.com/golang/dep/internal/gps/solver.go:442 +0xb1
main.(*ensureCommand).runAdd(0xc0420e95e0, 0xc04208ee60, 0xc042072040, 0x1, 0x4, 0xc04203b440, 0xb13f80, 0xc0422d01e0, 0xc04215c040, 0x38, ...)
        D:/work/src/github.com/golang/dep/cmd/dep/ensure.go:597 +0x15f3
main.(*ensureCommand).Run(0xc0420e95e0, 0xc04208ee60, 0xc042072040, 0x1, 0x4, 0x0, 0x0)
        D:/work/src/github.com/golang/dep/cmd/dep/ensure.go:186 +0x56b
main.(*Config).Run(0xc04203ef00, 0xc04203ef00)
        D:/work/src/github.com/golang/dep/cmd/dep/main.go:159 +0x7a9
main.main()
        D:/work/src/github.com/golang/dep/cmd/dep/main.go:45 +0x203

What did you expect to see?
There should be no panic.
What did you see instead?
There was a panic

I was running dep in the wrong directory.

OH, hah! yeah, this should be a simple case to guard against. just need to reject arguments to dep ensure -add that come back to the same project as we're currently in. i...guess? hmm. it's actually kinda weird we can get here at all.
well, this'll take a little tracing to see how we reach this path, but the fix should be pretty straightforward.

this'd be a really good first PR - if someone's interested, drop a note, and i'll provide more guidance.

@sdboyer I can take it up

@vedhavyas woot!
so basically, i think this should just amount to one more check in this loop, comparing the parsed root to the current project's root and failing out if they're the same.
we'll want to add another harness test to capture this specifically, too. there's a README on how to write those in general, and then lots of examples to work from. though this case may be a bit tricky, as i can't recall what the root of the project in the harness tests actually ends up being - we might have it hardcoded to github.com/golang/notexist.


develop

bump_version スクリプトをバイナリに含めないように、とりあえず examples に移動
Python の example も同じディレクトリに入れる
example からのスクレイピングが失敗したので設定を追加
Add make bump-version
coverage 取得コマンドは独立させる
Bump version from v0.1.2 to v0.1.3

Codecov Report
Base: 62.50% // Head: 83.33% // Increases project coverage by +20.83% :tada:

Coverage data is based on head (f612c82) compared to base (dc50856).
Patch has no changes to coverable lines.

Additional details and impacted files
@@             Coverage Diff             @@
##             main       #8       +/-   ##
===========================================
+ Coverage   62.50%   83.33%   +20.83%
===========================================
  Files           2        1        -1
  Lines          16       12        -4
===========================================
  Hits           10       10
+ Misses          6        2        -4

Impacted Files
Coverage Δ

examples/bump_version.rs

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

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


Support for Shields / Totem

It would be useful to automatically equip shields (or totems) if one is available, as this is usually also equipped alongside armor.

Hey @TheDudeFromCI, thanks for raising the issue, it would be a very useful feature indeed! I'm not sure if I will have time to implement this in the near future but if you have any ideas on implementations, PRs are always welcome 🙂


Set tab property

Questions
Answers

Description?
Set tab property.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes PrestaShop/Prestashop#27075.

@PrestaEdit But you needs a rebase


Adding pagination

Added pagination for GET requests to the StoreEndpoint (as discussed in GitLab).
Documentation added under GET File in docs/src/index.adoc.
End-To-End tests added. After you reviewed the code and it's fine for you, I'll also add the integration tests and 1-2 more End-To-End tests.

ToDos

Mention the new configuration georocket.index.pagination in the docs.

Thanks for the PR. We're currently reviewing it and will get back to you if necessary.

Superseded by #121


[SUGGESTION] Something to let you know a sound isn't on the server in the sound replacer

After some changes a while ago to fix server console error spam relating to sounds the server doesn't have, I've realized that there's no way to determine whether the server actually has a sound until you put it on an ACF entity and realize it's silent. It would be nice to have either:

Some kind of warning in the menu if the sound currently selected isn't available on the server
A fix for the server side error spam that still allows you to use sounds available to your client, but not the server (don't know if this is possible without moving all sounds to the client side)

Ideally, #165.


ImageHandlerError: The image request you provided could not be decoded. Please check that your request is base64 encoded properly and refer to the documentation for additional guidance

I am using it with cloudformation with the provided template file at here, Created the Lamda function successfully, But when i check in the logs it shows me the above errors.
Can anyone have solution for this issue ?

@devtushar thank you for contacting us. Could you please provide the request you sent to the Serverless Image Handler? Do you see a response (image) when you make a request?

Hi @fisenkodv I am using https://<xyz>.cloudfront.net/fit-in/400x400/image.jpg in the URL and I am getting a response as well (Image).

@devtushar thank you. You can ignore that error in the logs, please refer to https://github.com/aws-solutions/serverless-image-handler/issues/325.


增加校验登录密码的方法:ResourceServlet.checkLoginParam(request),允许单次调用鉴权

根据温少的建议,对 #1501  重新修改了单次调用鉴权逻辑。更简单和直接,同时尽量不改动原来的逻辑。

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


[BEAM-1047] Add getRegion to DataflowPipelineOptions

Coverage decreased (-0.01%) to 69.311% when pulling af9cf4bbef695fa6abbc9d23dc1788a295923122 on dhalperi:r13n-options into ede77c1b5c86bbc5947be77fdbe03bdf82088608 on apache:master.

R: @tgroh or @kennknowles

Coverage decreased (-0.008%) to 69.313% when pulling 05f21e2073ac3be8f12ee1d61adb6f497c35d2dc on dhalperi:r13n-options into ede77c1b5c86bbc5947be77fdbe03bdf82088608 on apache:master.


Trace server started externally cannot be stopped

And yet, the "Stop trace server" button is available to click on. Clicking on it writes a the following message: "Failed to stop the trace server on port: 8080.", without further reason.
Either do not allow to click on the "stop trace server" and just replace by a "Trace server running" status, or else, write in the error message that the server was not started by the application and it cannot be stopped this way.

Yes, external started server cannot be stopped anymore. In the recent updates for start/stop the trace server is stopped by using npm package tree-kill using the PID that was obtained when starting the server by the extension's Theia back-end code. Before the back-end was deleting the process that was holding the port configured in the preferences which could be the trace server process or not. Also, tree kill is platform independent that previous implementation.
However, the current start/stop procedure for the local needs as well as the connection monitoring to be revised in the future.

Yes, external started server cannot be stopped anymore. In the recent updates for start/stop the trace server is stopped by using npm package tree-kill using the PID that was obtained when starting the server by the extension's Theia back-end code. Before the back-end was deleting the process that was holding the port configured in the preferences which could be the trace server process or not. Also, tree kill is platform independent that previous implementation.
However, the current start/stop procedure for the local needs as well as the connection monitoring to be revised in the future.


fix: add a describe object method and response struct

:tada: This PR is included in version 1.0.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[question] what is the difference between annotation and tag?

版本
8.5.0
复现步骤
None
当前效果
None
预期效果
None
环境
- 系统:
- 浏览器:
- 框架:

补充说明
No response

This is a good question, so v9 has been merged, and there is no doubt about it.


add piecewise logistic growth with constant capacity

Closes #2
Added piecewise logistic growth and tested with some data. I have tested with the example data at prophet docs

I had to add a MaxScaler to get the model working properly. I am not sure if it's okay. Fbprophet does something like this:

        if self.growth == 'logistic' and 'floor' in df:
            self.logistic_floor = True
            floor = df['floor']
        else:
            floor = 0.
        self.y_scale = (df['y'] - floor).abs().max()

        if 'y' in df:
            df['y_scaled'] = (df['y'] - df['floor']) / self.y_scale

I have added a test case following other examples.
Currently we have a constant capacity and no floor.

Thanks for this, it looks nice! I haven't had a chance to explore it fully, but I'll merge it anyway for now

Thanks for this, it looks nice! I haven't had a chance to explore it fully, but I'll merge it anyway for now


DRY shader creation via helper lambda

Should not change any existing behavior, just DRY refactoring. Useful to clearly demonstrate that there are no difference between the creation/attachment of different shader types.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

16 of 16 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 56.957%

Totals

Change from base Build<PHONE_NUMBER>2:
0.02%

Covered Lines:
11883

Relevant Lines:
19876

💛  - Coveralls

SFMLBuildMaster: Build this please.


Support Puppet 6

Coverage remained the same at 92.647% when pulling 25c3c9f8d32812f9a86f2f7ea6ac20d500227264 on raphink:puppet6 into 4e9ff96f1fc919fb96e59d03a3180bcb70c9cf65 on hercules-team:master.

Coverage remained the same at 92.647% when pulling 25c3c9f8d32812f9a86f2f7ea6ac20d500227264 on raphink:puppet6 into 4e9ff96f1fc919fb96e59d03a3180bcb70c9cf65 on hercules-team:master.


randoop: 4.2.5 -> 4.2.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/randoop/randoop/releases.
meta.description for randoop is: "Automatic test generation for Java"
meta.homepage for randoop is: "https://randoop.github.io/randoop/"
meta.changelog for randoop is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.2.6 with grep in /nix/store/s7vhj8zp599bkvqm7l2rvl1fwd3ynkx6-randoop-4.2.6

found 4.2.6 in filename of file in /nix/store/s7vhj8zp599bkvqm7l2rvl1fwd3ynkx6-randoop-4.2.6

directory tree listing: https://gist.github.com/9c3c106f344a71c0d10d673b947f498f

du listing: https://gist.github.com/2b348ff54f0fe37844142105108a496d

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
randoop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s7vhj8zp599bkvqm7l2rvl1fwd3ynkx6-randoop-4.2.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A randoop https://github.com/r-ryantm/nixpkgs/archive/e771f181e17a5fef10e977e368ce2698ce7e9052.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s7vhj8zp599bkvqm7l2rvl1fwd3ynkx6-randoop-4.2.6
ls -la /nix/store/s7vhj8zp599bkvqm7l2rvl1fwd3ynkx6-randoop-4.2.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

randoop

Maintainer pings
cc @pSub for testing.

Result of nixpkgs-review pr 134491 at e771f181 run on x86_64-linux 1

1 package built successfully:

randoop

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/tools/analysis/randoop/default.nix:14:3:
   |
14 |   installPhase = ''
   |   ^


Add Oracle Linux 5.11 i386 & x86_64 templates

Update Oracle Linux 5 templates to 5.11 which is believed to be the last minor release for EL 5.
For those who may still need to work with EL 5 ;-D
Please merge.

can you consider merging templates like this: https://github.com/jedi4ever/veewee/blob/master/templates/CentOS-5.10/definition.rb


Add Exoscale instance type Module

This module provides predifined human readable exoscale instance types.
I built it up like the region modules to be able to exclude instance types.
Types are splitted up in categories like standard, cpu, gpu, storage, ...

You'll need to run bun fmt to meet the formatting CI requirements and merge.


Update AWS Java SDK to 1.11.90

Doing some work in Spinnaker that is pushing up to update to a newer, although not newest (1.11.93) version of the AWS SDK.

@brharrington can you take a look at this when you have a chance?

Any reason not to go to 1.11.93?


Edit CSPROJ context menu option shouldn't appear if XML content already open

The "Edit CSPROJ" context menu option which appears when right-clicking an ASP.NET Core project shouldn't appear if I've already selected it and have the CSPROJ XML open. Here are the steps to reproduce in VS 2017 RC:

Create a new project using the ASP.NET Core 1.1 / .NET Core project template
Right-click the project in Solution Explorer, and select "Edit <project_name_here>.csproj"
Repeat step 2, and notice that you can still select this option from the context menu. The option shouldn't appear, since the XML content of the CSPROJ file is already open in the IDE.

Why do you think that's the correct behavior?
This is exactly the same behavor as "editing" (open) a source file. If it's not already open, open it, otherwise, make it the current editor.

Scott and I talked a bit offline. The design of this feature is that we want to open the editor if it's not open, and switch to it if it's already open. The editor itself reloads in the background as necessary, so it can be open for a long period of time.


fix(posts): sanitize chars in all occurrences

Issue 66 📐

I onionSequences have worked for 66

Guidelines 🔐
I accept the fact that i have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #66

Screenshots 📷
Here are the pictures of changes that i have made 🔽

Great to see your enthusiasm towards this project @onionSequences 🎊.

However, our contributor Guidelines clearly state that any Issue must be solved only after getting assigned to them first.
Hence it is required by the contributor to get assigned to this issue first.
This PR will be automatically closed after some time if the author is not assigned to the issue first.
Else the PR will be reviewed by the repo maintainers and then merged if all requirements are met.


python38Packages.dash-html-components: 1.1.3 -> 1.1.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.dash-html-components is: "HTML components for Dash"
meta.homepage for python38Packages.dash-html-components is: "https://dash.plot.ly/dash-html-components"
meta.changelog for python38Packages.dash-html-components is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.1.4 with grep in /nix/store/mmlqm01nn7k93a6501lnyq6i90223fm4-python3.8-dash_html_components-1.1.4

found 1.1.4 in filename of file in /nix/store/mmlqm01nn7k93a6501lnyq6i90223fm4-python3.8-dash_html_components-1.1.4

directory tree listing: https://gist.github.com/daa090f0f8560737b642c1a0d8b46878

du listing: https://gist.github.com/08e2a186d67daee946e88b66778fa092

Rebuild report (if merged into master) (click to expand)

16 total rebuild path(s)

4 package rebuild(s)

4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
python38Packages.dash
python38Packages.dash-html-components
python39Packages.dash
python39Packages.dash-html-components

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mmlqm01nn7k93a6501lnyq6i90223fm4-python3.8-dash_html_components-1.1.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.dash-html-components https://github.com/r-ryantm/nixpkgs/archive/d9284653a75b39caaa0f69be9a683206c8619f30.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mmlqm01nn7k93a6501lnyq6i90223fm4-python3.8-dash_html_components-1.1.4
ls -la /nix/store/mmlqm01nn7k93a6501lnyq6i90223fm4-python3.8-dash_html_components-1.1.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @antoinerg for testing.

Result of nixpkgs-review pr 134108 at d9284653 run on aarch64-linux 1

2 packages failed to build:

python38Packages.dash
python39Packages.dash

2 packages built successfully:

python38Packages.dash-html-components
python39Packages.dash-html-components

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/dash-html-components/default.nix:19:0:
   |
19 |     description = "HTML components for Dash";
   | ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

addressed in #133866


Add session method to enable Brotli compression

This is needed for https://github.com/brave/browser-laptop/issues/2890.
Maybe it should just be on by default instead of as a session method, not sure.
Auditors: @bbondy

++


WSL2 doesn't support masked watchpoints

Please fill out the below information:

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.18990.1]
What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem
WSL doesn't seem to support masked watchpoints, even though the x86-64 architecture supports them.
Open up gdb (I'm personally using pwndbg) and write a command such as the following:
watch *0x6c0000 mask 0xff0000
This command fails with:
This target does not support masked watchpoints.
What's wrong / what should be happening instead:
The watchpoint should be successfully set.
This may have something to do with #2609, which has conflicting claims that hardware watchpoints aren't supported in WSL at all.

Same behavior Real Linux, on a stock Ubuntu kernel, anyway.

This may have something to do with #2609,

Unrelated. That is WSL1.

@therealkenc Can confirm. Just tried it out on an old machine. Sorry for wasting your time. It seems x64 doesn't support masked watchpoints after all.

It seems x64 doesn't support masked watchpoints after all.

No x64 does, AFAIK, anyway. TBH I didn't dive why your particular repro results in the error. Just know it does. [Also if we're being completely honest, I'm more of a caveman guy if I need a watch.]

can be tagged as "fixed in WSL2"?

You'd think so. Not sure how that works, precisely. There are lots of open issues that could be marked fixed-in-wsl2.


Custom scalars

Houdini needs a way to specify how to marshal/unmarshal scalars found in documents

I'm trying to come up with the right API for this. In general, the user needs to provide a few pieces of information:

A function to massage the API's response into the corresponding javascript type
The corresponding typescript type (so generated type definitions can have the correct types)

This information needs to be made available in a way that both the generate function and the runtime have access to. Ideally it would also be portable enough for a third-party package to provide common types. I played around with having it embedded in the config file, however that would prevent things modules like path from being imported  as well as global objects like process.env from being accessed. The first is not such a big deal - the only bit of config that currently uses path is schemaPath which could easily be changed into a string denoting a relative path. However, the second limitation is much bigger since it would prevent any kind of switch for config values like static.

I've started this work in the custom-scalars branch. Here is the API I am putting in place:
// houdini.config.js

export default {
	// ...

	scalars: {
		// the name of the scalar we are configuring
		DateTime: {
			// the corresponding typescript type (what the typedef generator leaves behind in the response and operation inputs)
			type: 'Date',
			// turn the api's response into that type
			unmarshal(val) {
				const date = new Date(0)
				date.setMilliseconds(val)

				return date
			},
			// turn the value into something the API can use
			marshal(date) {
				return date.getTime()
			},
		},
	},
}

hey @AlecAivazis , thanks a lot for you work on this topic.
I am wondering: is there a way to define complex scalar types? And maybe even some that are imported from a third party library? Such as
import {MyDate} from "my-date-library"

export default {
  scalars: {
    DateTime: {
      // ❌ this does not seem to work
      type: MyDate,

      unmarshal(val) { /* ... */},
      marshal(date) { /* ... */},
    },
  },
}

@jycouet @AlecAivazis are you interested in a PR for the docs?

It's always good to improve the doc yes 👍.
You can probably suggest something and we tweak it before merging if needed 🎉


Upgrade clojurescript and beicon dependencies

I have tested it with my biggest project and everything seems to be ok.

Thanks!


common: trim space from appPrComment output

To avoid an extra newline when pr comment url is printed.

Revision 1
Compare

0..1


added note about sdk 2.1

@KathleenDollard see if this works for now until we don't have the new version in place
Related to #4352

I've addressed your feedback @rpetrusha. Thanks!

@Petermarcu @karelz since I'm touching this topic, the other day I saw on gitter someone asking about what line 182 means and I wasn't exactly sure how to explain that to him:

A host (also known as muxer): dotnet.exe with hostfxr policy libraries.

Is there a way we can write this using layman's terms?

@steveharter can you please help while I am OOF?

@mairaw here's the line you are asking about:

A host (also known as muxer): dotnet.exe with hostfxr policy libraries.

If we want to keep it short I think this is fine:

A host: either dotnet.exe for framework-dependent applications, or <appname>.exe for self-contained applications.

If we want to elaborate a bit more:

A host that will launch the application: either dotnet.exe for framework-dependent applications, or <appname>.exe for self-contained applications. The dotnet.exe host can also be used to return environment information and forward commands to the SDK.

+1 on the first suggestion from @steveharter .

Thank you @steveharter and @Petermarcu. That makes things a lot clearer.


Rename file.Location.VirtualPath to AccessPath

Closes #1835
Note: must be merged after #2287

#2287 merged and this refactor does not break any current tests - LGTM


Need valid geocode service URL

I am having trouble setting a valid geocode service URL. I followed the steps over here, but I'm not sure why the URL isn't working. I can insert the widget, but I can't see the locator which I had previously set up. I'm right around the bullet point in the README for

Then click on your Locator, scroll down to the bottom of the page, on the right-hand

Can someone help me debug? I have my node server and client running and I think I must be close.

Hi, I am working on fixing this issue. currently, The widget picks up the top locator that has been added to the utility services of your organisation as it is shown in this screenshot, in this example it is the what3words_EN_English dev
.
I update the widget asap. thanks for reporting this issue. I am keen to hear any feedback from you. thanks

Thanks, that's a big help. I moved the w3w locator to the top of that list and now I can add it.


Bosh::Template::Test does not support link.address

When trying to write a test around our bosh template we get the following error:
1) Metron Agent JSON Bosh DNS is enabled uses bosh links to populate DopplerAddr and DopplerAddrWithAZ
     # Links are not supported by bosh-template
     Failure/Error: rendered = template.render(properties, spec: spec, consumes: links)

     NotImplementedError:
       link.address requires bosh director
     # /home/pivotal/.gem/ruby/2.4.2/gems/bosh-template-2.0.0/lib/bosh/template/evaluation_link.rb:45:in `address'
     # (erb):7:in `get_binding'
     # /home/pivotal/.gem/ruby/2.4.2/gems/bosh-template-2.0.0/lib/bosh/template/test/template.rb:22:in `render'
     # ./spec/metron_agent/templates/metron_agent.json.erb_spec.rb:227:in `render_template'
     # ./spec/metron_agent/templates/metron_agent.json.erb_spec.rb:215:in `block (3 levels) in <top (required)>'

We are seeing this when using the new link property address:
link("doppler").address(azs: [spec.az])

Agreed, perhaps we can implement some fake value generator. Typically it's a very derived value from the director, but we could probably approximate it for tests.
Would you expect to be able to test that spec.az was actually embedded into the returned address? That will diverge from actual director behavior and DNS name generation, but would retain testability.

@dpb587-pivotal I don't think we have an opinion spec.az being embedded.

Going to close and reopen this issue to create a tracker story.


tbb: fix pcTemplate url

Motivation for this change
hash mismatch in fixed-output derivation '/direct/star+u/veprbl/nix/store/lxgk1p1163vk3a14pp6ci7pzf4pb6b24-tbb.pc.in':
  wanted: sha256:14nyp6rg0wbl3wdqjscjvhf7nz33sngvwd57rmdr6jkivdvrm46s
  got:    sha256:1z4377051l3wmpr3f6xs2yknwwmm0mvlm79b3axhwk67ry5758h9

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Oops, thanks for fixing this.


[Event Request] Codeunit 12 "Gen. Jnl.-Post Line" - OnBeforeCreateGLEntrySalesVAT

Hi, would it be possible to add an event in codeunit 12 "Gen. Jnl.-Post Line", in procedure InsertVAT right before calling CreateGLEntry?
We would like to extend Sales with deductible VAT, as it happens with Purchases, so we need to have access to CreateGLEntry parameters beforehand.
As it is now:
"Gen. Posting Type"::Sale:
    case VATPostingSetup."VAT Calculation Type" of
        VATPostingSetup."VAT Calculation Type"::"Normal VAT",
      VATPostingSetup."VAT Calculation Type"::"Full VAT":
            CreateGLEntry(GenJnlLine, VATPostingSetup.GetSalesAccount(UnrealizedVAT),
              GLEntryVATAmount, SrcCurrGLEntryVATAmt, true);
        VATPostingSetup."VAT Calculation Type"::"Reverse Charge VAT":
            ;
        VATPostingSetup."VAT Calculation Type"::"Sales Tax":
            InitGLEntryVAT(GenJnlLine, TaxJurisdiction.GetSalesAccount(UnrealizedVAT), '',
              GLEntryVATAmount, SrcCurrGLEntryVATAmt, true);
    end;

Example with event OnBeforeCreateGLEntrySalesVAT:
"Gen. Posting Type"::Sale:
    begin
        OnBeforeCreateGLEntrySalesVAT(VATEntry, GenJnlLine, VATPostingSetup, TaxJurisdiction, UnrealizedVAT,
          GLEntryVATAmount, SrcCurrGLEntryVATAmt);
        case VATPostingSetup."VAT Calculation Type" of
            VATPostingSetup."VAT Calculation Type"::"Normal VAT",
          VATPostingSetup."VAT Calculation Type"::"Full VAT":
                CreateGLEntry(GenJnlLine, VATPostingSetup.GetSalesAccount(UnrealizedVAT),
                  GLEntryVATAmount, SrcCurrGLEntryVATAmt, true);
            VATPostingSetup."VAT Calculation Type"::"Reverse Charge VAT":
                ;
            VATPostingSetup."VAT Calculation Type"::"Sales Tax":
                InitGLEntryVAT(GenJnlLine, TaxJurisdiction.GetSalesAccount(UnrealizedVAT), '',
                  GLEntryVATAmount, SrcCurrGLEntryVATAmt, true);
        end;
    end;

Thank you.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


what is load_image doing internally and how to apply the same operation to frames from video

Doing some testing I noticied that doing inference returns very different results for the same image but loaded with different methods:

Method 1: the official load_image function from the library(it reads the image using the path passed as argument)
Method2:  using cv2 to read the image, then converting to tensor and then swapping axis to have depth as first axis.

As I said, both methods give you a tensor to pass to the model, but they return very different results(method2 usually are bad), I inspected the shape of the image returned by both cases and they are different so defintelly there are transformations going on inside load_image, my question is: what is happening inside load_image? so I can replicate it in other scripts
My end goal is to run the model on video, I mean running the model on frames in the video, so I cannot use load_image because they are not images from disk, they are obtained from the video, so I need to understand what is happening inside_load image so I can emulate that behavior on the frames of the video.
Thanks

Ignore my message, for some moment I forgot the code is avaialble for me to see: https://github.com/IDEA-Research/GroundingDINO/blob/856dde20aee659246248e20734ef9ba5214f5e44/groundingdino/util/inference.py#L39


rootston: no initial cursor on startup

If the pointer is not on top of  client surface when rootston starts there's no cursor displayed. If one starts a client and the pointer moves over a client's surface the pointer is displayed (and stays visible from there on).
Rootston should display an initial cursor (iff there's a pointing device attached, if there's only touch and/or keyboard then better not)

If the pointer is not on top of  client surface when rootston starts there's no cursor displayed.

Is this specific to one backend? I don't understand the "client surface" part since on startup there's no client yet.

It should better read "if one starts up a client and the pointer moves over on of it's surfaces the pointer is displayed". I can't tell whether X11 is affected as well since there's already a cursor from the outer X11/Wayland present. It surely happens on DRM.


Deploy/Upgrade mechanism for QGB contract

Context
This PR https://github.com/celestiaorg/quantum-gravity-bridge/pull/177 implements the UUPS pattern in the QGB smart contract.
This changes how the QGB contract will be deployed from now on.
Previously, we were using a deploy command from the orchestrator-relayer to deploy the contract as it was straightforward.
Now that it's upgradable, to deploy it, we need to do the following:

Deploy the implementation
Deploy the proxy
Link the proxy to the implementation

Doing these steps, when deploying, and also when upgrading doing something similar, can be a bit tricky to implement/maintain correctly.
Proposals:
Hardhat project
Create a deploy folder inside the QGB repo, which would contain a hardhat project and a Makefile. This project will have already implemented scripts for deploying/upgrading, and will use the contracts in the root QGB repo.
This would allow keeping using foundry as a dev environment, and hardhat for deployment/upgrades.
The Makefile and a few scripts will help automate the whole process.
Also, we can incorporate some static code analyzers to be executed to check for known issues.
The upside is that we will use the hardhat abstractions directly, and not have to maintain them:
  const qgb = await hre.ethers.getContractFactory("QuantumGravityBridge");
  let qgbInstance = await hre.upgrades.deployProxy(qgb, [12443, 12344, "0x1234567890abcdef1234567890abcdef1234567890abcdef1234567890abcdef"], {
    initializer: 'initialize',
    kind: 'uups'
  });
  await qgbInstance.waitForDeployment();

  console.log(
      `deployed to ${await qgbInstance.getAddress()}`
  );

  const qgbV2 = await hre.ethers.getContractFactory("QuantumGravityBridgeV2");
  console.log("Upgrading QGB...");
  await hre.upgrades.upgradeProxy(await qgbInstance.getAddress(), qgbV2);
  console.log("QGB upgraded successfully");

Note: we will still have a go command to deploy so that we use it in E2E tests and others. However, it will contain an experimental implementation not advised for production.
Maintain our own implementation
Update the deploy go command to do all the steps done by hardhat deployProxy and also provide an upgrade command to perform the upgrades. And then having to maintain them for any changes, etc.
Decision
TBD.

cc @adlerjohn @evan-forbes


UNMET PEER DEPENDENCY when using with Angular v4

Hello 😀
This code is awesome! You saved my life 😆 👍
Except one thing,
When installing this package, npm is telling me warning.
Anyway, this package works fine with Angular v4.
Do you have any plans to update package.json to make this warning clear?
pc:awesome-project pittan$ npm install --save ng2-inline-href
<EMAIL_ADDRESS>/Users/pittan/Dev/awesome-project
├── UNMET PEER DEPENDENCY<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

Hey @Pittan! Thanks for letting me know about. this, I have been pretty busy lately, but I am updating one of projects to Angular 4 soon and should be able to get the update rolled out to this package this week.

@Pittan I have updated the peer dependency to Angular 4. Note that the package has been moved from ng2-inline-href to ng-inline-href.
Cheers!


Typo in function initial_step_size in jax/experimental/ode.py

Description
The function initial_step_size is based from an algorithm in this book (page 169). This is the algorithm:

In step e, we need to compute max(d1, d2), but in the initial_step_size function you compute max(d1 + d2).
What jax/jaxlib version are you using?
jax v0.4.1, jaxlib v0.4.1
Which accelerator(s) are you using?
CPU
Additional system info
No response
NVIDIA GPU info
No response

Thanks for noticing this and bringing it to our attention! Amazing!


Resolves #147 Form is submitted when required checkboxes are not checked

Here is the plunker.

Hey @indrimuska,
Thanks for sharing this idea. I can't merge it as-is however, since it's only a change to the dist file and not the source. Also if I'm reading it correctly, it would break fields with values like 0 or false or '' (empty string).
Going to need to give this some more thought.

Hi @bvaughn, you're right, next time I'll make my changes also to source files.
Just one question: I don't understand why you're saying that it would break fields with values like 0 or false or ''. Is there any way to set the two values of a single checkbox? I haven't found anything into the documentation site. Maybe I'm missing something.

My apologies. I was only able to glance at your PR briefly because I was at work. For some reason I thought you had made your change to the FieldHelper (which is used by all of the input types). Looking again, this is obviously not the case so you can disregard the second half of my earlier statement. :)

Ah ok, don't worry, no problem! :smile:
Maybe you misunderstood the comment I made in #147, or maybe it was not so clear as I think (this proposal is about option n.2 - adding a specific watcher to checkbox-field directive).
If you like this solution I can update the PR.

If you've tested it and it seems to work- let's go for it. I'll give it another test myself once you've got a PR with source+dist modifications. :)

Oh hi. I haven't been intending to ignore this, I just didn't get a notice that you'd updated your branch.
Let me take a look here... :)


legion_prof_rs: multiple nodes merged in archive viewer

This profile was generated from a 2 node run, but its only showing 1 node with twice as many processors:
https://legion.stanford.edu/prof-viewer/?url=https://sapling2.stanford.edu/~seshu/viz/subranks/legion_prof/
The log files are here: http://sapling2.stanford.edu/~seshu/viz/subranks/

Do you have a local patch that changes the Realm ID format? Legion Prof has to parse the proc/mem/etc. IDs:
https://gitlab.com/StanfordLegion/legion/-/blob/master/tools/legion_prof_rs/src/state.rs#L441-452
https://gitlab.com/StanfordLegion/legion/-/blob/master/tools/legion_prof_rs/src/state.rs#L689-699

Oh yeah I do. I dont think we need that anymore. It was for when we were trying to scale rank/gpu to the full machine. I will remove it.

Either that or change Legion Prof to match. They just need to be in sync.


Hubot/slack adapter times out?

After about a day's worth of connected uptime, the hubot seems to crash. Sort of.
It ran flawlessly for days on end with the Slack adapter when I was running Ubuntu 14.04 on an older machine. Now on a newer machine running Linux Mint 17.3 Rosa, after about 12 to 24 hours it seems to stop working.
I'm using the same upstart script, but my node/hubot/adapter installations are all fresh ones.
I still get a green light for the bot in Slack, but he doesn't respond to commands, even ones that his own server curls to him.
Thoughts? The logs didn't seem to include anything useful. Is this a hubot problem or an adapter problem?
I got a similar problem with a cloud VM and the twitter adapter, but my only solution was to write a script to restart the server with cron.

I couldn't find other discussion about this earlier, now I have. :/
https://github.com/slackhq/hubot-slack/issues/203
Here's the solution that I'm trying, which is replacing slack.coffee with this updated file:
https://github.com/eriklindebratt/hubot-slack/blob/master/src/slack.coffee

This is the reply that got me this info: https://github.com/github/hubot/issues/1013#issuecomment-131013071

About a day of using the updated slack.coffee files and I have had no problems.

This should be fixed in https://github.com/slackhq/hubot-slack/pull/309


Match with Wikidata items

Example : EagleCoin -> https://www.wikidata.org/wiki/Q20639637
Note: use sameAs: "https://www.wikidata.org/wiki/Q20639637"

@Manu1400, can you be more specific about your request? I am not sure what you mean. Thanks!

I am going to close this issue, since this list of just meant to be a simple JSON reference from the currencies that are collected by the cryptocompare API. But anyone is welcome to submit a PR with extended functionality if they want to help add value to this resource. 👍


WKT Geometries reverting lng lat

Just trying the GIS features in <IP_ADDRESS>904211926 and looks like rendering of a WKT POINT is reversing the input coords. Take a look at this example which should be rendering in Brookline, Boston

What is your database?

Please post sample SQL query in plaintext.

mysqld  Ver 5.7.22 for Linux on x86_64 (MySQL Community Server (GPL))
select st_geomfromtext("POINT(42.33118 -71.11777)")

This is already fixed in 6.0.4 EA (https://dbeaver.io/files/ea)
Thanks for the report anyway.

just downloaded EA <IP_ADDRESS>905011413, issue still present

verified

@pfazzino Super weird. This is how it works on my machine:
(note that in text format coordinates are also flipped)

Have no clue so far..

What MySQL driver do you use?

@serge-rider not sure if you're saying it's fixed. your screenshot is showing the same issue I'm reporting. The text coords should not be flipped and the map is rendering the flipped coords not the ones provided in the query. The problem is in the render, run
select st_astext(st_geomfromtext("POINT(-71.11777 42.33118)"));
and you'll see the correct output as input.
Driver...

You just flipped coordinates in your source query (originally it was 42.33118 -71.11777: https://github.com/dbeaver/dbeaver/issues/5832#issuecomment-488264333)
As you can see on my screenshot that map is rendered correctly for query
select st_geomfromtext("POINT(42.33118 -71.11777)")

MySQL stores GIS coordinates in a flipped form. We use OpenStreetMap engine which uses different coordinates notation. As well as Postgis (PostgreSQL).
So DBeaver flips coordinates in MySQL geometry data type to render it correctly.

The question is: what MySQL format is correct:

The native MySQL format you posted originally in https://github.com/dbeaver/dbeaver/issues/5832#issuecomment-488264333
Or OSM/Postgis format you posted in https://github.com/dbeaver/dbeaver/issues/5832#issuecomment-488301616

As some particular databases may keep coordinates in flipped/inverted form I've added special coordinates toggle in the map viewer. Check it in the new EA version build.

The correct format is as defined by the WKT standard which defines POINT(x y). Your example correctly rendering the map is passing (POINT y x). It doesn't matter how MYSQL stores this internally as that is opaque to the user experience as long as the spatial functions operate correctly.
select st_geomfromtext("POINT(-71.11777 42.33118)")
should return the POINT as entered in the query into the results grid and be rendered on the map in the correct position, not at latitude -71.11777 longitude 42.33118 but at latitude 42.33118 longitude -71.11777. Wrapping this query in st_astext and rendering a string into the resultsgrid gives the correct output thus I believe showing that this issue is in how dbeaver is rendering the spatial type and how mysql is storing the coordinates is not a factor.

As some particular databases may keep coordinates in flipped/inverted form I've added special coordinates toggle in the map viewer. Check it in the new EA version build.

thanks. Will give it a try. Not sure I understand the justification but if it fixes the issue then great...

@pfazzino Unfortunately it matters how MySQL stores data.
https://forums.mysql.com/read.php?23,209566,209566
https://stackoverflow.com/questions/29935651/postgis-latitude-longitude-read-out-reversed
https://postgis.net/2013/08/18/tip_lon_lat/
So, if some database engine stored coordinates in inverted form then its DBeaver's job to flip them.
WKT itself (being a simple text format representing coordinates as a sequence of numbers) doesn't define lat/lon or lon/lat order.

It matters to the developer of dbeaver but it shouldn't matter to the user of the product. If I store and query a WKT POINT geometry I expect the output to match my input. It looks as though whatever dbeaver is doing in terms of inverting or not inverting the x,y, it is incorrect for the mysql/driver combination that I'm using.
WKT specification does in fact specify lat/long order. See http://portal.opengeospatial.org/files/?artifact_id=25355 section 7 which clearly defines a POINT as x,y (lng, lat).
In the end, if I store a point based geometry, I expect the rendered output to match what I input. I don't care how it's stored. If I query based on the specification a coordinate represented as POINT(-71.11777 42.33118) then the output should match the x, y inputs.

DBeaver flips coordinates only to render them on a map viewer. This weird side-effect when they are also flipped in text form is actually a bug. This transformation must be invisible for users. This issue will be fixed before 6.0.4 release.
General thoughts:
It doesn't matter what X and Y mean inside a application. At least if this application has a  consistent data model. But any application must integrate with outer world (get source data in some format from source systems and pass data in other format to target systems). So it is still important what X and Y mean in a real world app.

WKT specification does in fact specify lat/long order. See http://portal.opengeospatial.org/files/?artifact_id=25355 section 7 which clearly defines a POINT as x,y (lng, lat).

In your example (POINT(42.33118 -71.11777)) 42 is latitude and -71 is longitude so it is POINT(lat,lon).
WKT specification doesn't strictly define what is X and what is Y. This topic is described in details in the first article I posted above. By historical reasons MySQL format (lat/lon) differs from the most of other geospatial storage systems (lon/lat).

I appreciate we've now agreed this is a bug in the text form rendering and look forward to the fix.
However in all WKT examples, x = lat, y = lng. If it's required to flip this internally for map rendering that's fine but the default expectation is that POINT(-71.11777, 42.33118 ) renders in the Boston area. My latter examples where this is flipped were to demonstrate the issue and this is what I was doing to get this to render before you added the new toggle option. With that new feature I guess this is no longer a factor once the text form is fixed.
thx for your help.

btw, just noticed that the toggle option is resetting on every execution. Can we either flip the default so it works without flipping or save the selected option.

Can we fix the above (the toggle setting not saving and having to keep selecting it) or fix the default? The co-ord ref system dialog shows the order as lon lat so really this should be the default imho.

@pfazzino Agreed, this makes sense. Could you create a separate ticket for that?


update-org-quotas is not working as expected

Describe the bug
cf-mgmt update-org-quotas is failing and not working as expected and throwing the below error
yaml_config.go:562] No org quotas found.  Create directory org_quotas and add org quota defintion(s)
To Reproduce
Steps to reproduce the behavior:
try to change the instance memory limit in org definition.yaml and try to run the cf-mgmt update org-quotas command
Expected behavior
it should update the org configurations
Screenshots
Additional context
Add any other context about the problem here.

@aakashvalluru can you validate in the the org in question you have enabled the feature flag in orgConfig.yml to turn this on
Value should be enable-org-quota: true

@calebwashburn  we have several org config.yaml files for several customers and in that i am seeing that enable-org-quota: true is not there . so you are suggesting to add this so it will not throw this error yaml_config.go:562] No org quotas found. Create directory org_quotas and add org quota defintion(s) ?

@aakashvalluru you can use the cf-mgmt-config cli to update the configs cf-mgmt-config org --org <your org> --enable-org-quota true this will opt you in to having that org's quotas managed by cf-mgmt if that isn't working as expected please provide debug output from cf-mgmt

@aakashvalluru - Let me know if there is any update on this otherwise closing as completed.

Closing issue as completed


IconMenu positioning not working since 1.0.0?

Not sure if I've missed something but the IconMenu demo (http://react-toolbox.com/#/components/menu) seems broken, the menu does impact the flow of DOM elements when closed (eg. hidden but still there in the DOM), shouldn't the position be absolute-like?
Also tried to play with the position attr/prop, and nothing changes.
Is it a regression or has it always behaved like this? Is this open for a PR?

I believe it's because they renamed all the position constants in 1.0.0, and don't validate against them.
Essentially, if you're using top-left, you should be using topLeft.

Submitted a PR, so we can be the last to be affected by this issue. :)


categories fixes

remove summary and by source
stylize by category
check gene count in by category

redistribute table rows

link rows to gene, drop name links

do button thing


Refactoring transform functions: Remove defaults and add type hinting

Description
Please include a summary in English, of the changes in this pull request. If it closes an issue, please mention it here.
Closes: #(issue)
You should link at least one existing issue for PR. Before your create a PR, please check to see if there is an issue for this change.
PRs from forked repository not accepted.
Change(s)

Remove antialias → PIL doesn’t need antialias flag
Remove default values and add type hinting

Changelog
If you PR to dev branch, please add a brief summary of the change to the Upcoming Release section of the CHANGELOG.md file and include a link to the PR (formatted in markdown) and a link to your github profile.
For example,
- Added a new feature by `@myusername` in [PR 2023](https://github.com/Nota-NetsPresso/netspresso-trainer/pull/2023)

Code Formatting
If you PR to either master or dev branch, you should follow the code linting process. Please check your code with lint_check.sh in ./scripts directory.
For more information, please read the contribution guide in CONTRIBUTING.md.

This pull request contains #264


Updating link build for Artifactory 7.x

[ ] All tests passed. If this feature is not already covered by the tests, I added new tests.
[ ] This pull request is on the dev branch.
[ ] I used gofmt for formatting the code before submitting the pull request.

Testing


Position+Attitude complex message

I have added baro height and linear_acceleration to the proposed message

Added distance to ground if aircraft is equipped with LIDAR or radalt

Sorry to keep you hanging Eugene. I suggest to move this message away from the AHRS namespace into a new second level namespace uavcan.navigation.. Do you think that makes sense? I am not comfortable with keeping this definition in the equipment namespace because it is not pertaining to any specific kind of equipment.

Fully agree. Will do.

Hey Eugene, it is just a reminder that we're one commit away from merging this.

Moved and added QNH parameter as an essential information on baro altitude calculation

Superseded by https://github.com/UAVCAN/dsdl/pull/23. I had to open a new pull request because I can't push to the fork owned by @EShamaev.


feat: Add versioned releases

How possible would it be simply copy the release workflow of Open WebUI over here:
https://github.com/open-webui/open-webui/blob/main/.github/workflows/build-release.yml
For the image build, I'd guess there are a few tweaks to do.


Attempting to play blocked song prevents resuming current displayed song

Describe the bug
If you attempt to play a blocked song (it's grayed out in the official Spotify interfaces), it won't play. It won't update the interface, it will simply stop whatever you're playing currently. However, the progress bar may continue.
To Reproduce

Play a blocked song while another song is 'active' (playing or not).
Attempt to unpause and continue the current song.

Expected behavior
The current song should resume no matter what song was attempted prior. Better, the interface should update and shown that no song is currently playing.
Log and backtrace
spotify-player-23-06-23-16:02.log
Screenshots

I attempted to play 'Bookbag' but the interface remains unchanged. Also not shown in the screenshot is the progress bar progressing normally, despite nothing playing.
Environment

OS: Pop!_OS 22.04 LTS
Application version: 0.12.1

Related: https://github.com/aome510/spotify-player/issues/158. Look like this issue should also be fixed with https://github.com/aome510/spotify-player/pull/207.
@rileyallyn do you have any updates on the PR or do you have any helps with that?

Ideally, unavailable/blocked/unplayable songs should be filtered out from the UI, so such confusion should not happen.


not seeing all the build timings

I clean my project (even the derived data). Startup the build time analyzer and hit build. I see different source code files popping up with their timing in the build time analyzer window, but then quickly the screen gets cleared and after the build finished only timings are displayed of one particular file (in my case PaintCode.swift).

Hmmm... That sounds odd. Almost as if a second build process starts after the main one.. I'm not sure how to help out without being to able to reproduce it myself. Perhaps one way would be to go to your derived data path and have a look.
~/Library/Developer/Xcode/DerivedData/XXX/Logs/Build/
(where XXX is the product name follow by some identifier by Xcode)
If you sort by date and see two recent log files, one being smaller and more recent than the other, then something is up with the build process. If not, at least then that has been ruled out.

One more thing to check. Does the build duration label (to the upper right) match your actual build duration or is it shorter?

A1: I cleaned my logs directory, did a clean in XCode as well, and started a build. After the build I found the following files in the folder you specified :
B804C842-5888-4FE8-B44C-AE5D5B5CB1BA.xcactivitylog => 08:36 and 267K
4FCA2CF3-3A25-455B-BE19-3315C6F849B2.xcactivitylog => 08:34 and 1K
Cache.db => 08:36 and 1K
A2: the build B.T.A. window says 93 seconds top right, that is correct

Also noticed that if I shutdown the B.T.A. window and start it again (from xcode menu) that also the issue happens being (1) first I see more logs and functions (2)screen clears and is overwritten by only logs from one source file (being PaintCode.swift in my case)

Ok, so the files and build process is fine. If you would be willing to share your 267K log file, I could have a closer look. I haven't encountered this issue myself and don't know how to reproduce it.

Sure I can send you the log file, but privately (not on this public forum), how can I do this?

Drop me an email at<EMAIL_ADDRESS>and I'll have a look when I have a moment.

done!

Hi. I'm having the same issue, cleaned Derived Data and have only 2 files: Cache.db and XXXX.xcactivitylog. Also, the build duration in the plugin window is wrong, it says 0s.
Either way, thanks for creating / sharing the plugin!

Ok, there is nothing wrong with the log file so I'm not sure why this happens. I'm going to mark this one with 'Help Wanted' by someone who experiences the bug.
To debug this, clone the project and open it up in Xcode. Then go Edit Scheme -> Run. In the Executable field, add Xcode (by navigating to the Applications folder). Then Run the plugin project.
Some process appears to be causing the result to be wiped out. Probably on or after completion (suggested break point on line 26 of CMLogProcessor.swift).

@RobertGummesson if I increase func entries: [CMRawMeasure]) -> [CMRawMeasure] inner limit, more results are displayed. Don't know the best way to fix it, though.

There is no function called entries AFAIK. Did you mean capEntries(entries: [CMRawMeasure]) and then the limit on line 82?
If so, what happens exactly? If the limit is 20, no results are displayed and if you increased it you see a few results?

...and I better direct that to @amg1976 in case you are not a watcher of the project.

Sorry, that was probably auto-correct and I didn't notice it. Yes, if I increase the limit, then more results are displayed.

Interesting. Almost sounds like something goes wrong on line 87. The code in the method looks fine to me though. Not sure what to suggest...

Ah, I have reread this bug with a fresh mind. Maybe this isn't a bug after all (correct me if I am wrong, @hixfield , @amg1976 ). Here is what is happening.

The log file is being parsed
You see multiple files while it's processing
Eventually you see 20 results from the same file.

Correct?
The idea with the plugin is to get an overview of the 20 most time consuming issues. In your case, the entire top 20 is in one file. You will eventually see other files if refactor and improve the build times for these function.
In @hixfield case, it makes sense to refactor PaintCode.swift because that's where the largest issues are and likely the largest contributor to why the project builds so slowly.
If you need to see more results, you can adjust the limit in the capEntries function just as @amg1976 did.
Does that make any sense?

It does make sense, but we are displaying the results in a scrollable table, in my opinion it would be more interesting to display the complete list, but sort it based on time for example (or even better by default on the time column, but user can click any column to sort after this).
Note: PaintCode.swift is an auto generated file and I cant alter this, so this makes the current build of the B.T.A. unusable for me :(

As a quick fix for me I have put the limit = 20000 in the capEntries function, now I am seeing all the entries.

I'll keep that under consideration. The limit has been added to keep the log processing time to a minimum but I haven't benchmarked the process. Perhaps the limit could optional. Will have a think...

Or maybe set it as an end user parameter on the UI?
On Wed, May 11, 2016 at 8:07 AM, Robert Gummesson<EMAIL_ADDRESS>wrote:

I'll keep that under consideration. The limit has been added to keep the
log processing time to a minimum but I haven't benchmarked the process.
Perhaps the limit could optional. Will have a think...
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/RobertGummesson/BuildTimeAnalyzer-for-Xcode/issues/10#issuecomment-218379374

Yep, that's an option...

https://github.com/RobertGummesson/BuildTimeAnalyzer-for-Xcode/issues/10#issue-153759377
This one also can be handled in #17  :)


New lint: disallow pin-depends to be present.

The opam-repository should not carry any pin-depends. Sometimes such opam packages are submitted since they come from development repositories where related libraries need to be pinned. It is tedious (and error-prone) to rely on humans checking for the not-occurence of pin-depends.

Thanks. Any chance this and the earlier check could be pushed to production?

Done. Let me know if you see any issues.


Extract messages

Alternative for https://github.com/yiisoft/yii2/pull/19996.
In addition to https://github.com/yiisoft/yii2/pull/19996:

I tried to fix some translations that has changed placeholder name (see this diff).
Forced order - this PR is hard to review mostly because phrases changed their position. On long run it would be easier to review any change here if all messages will be ordered. Untranslated messages can be easily found by searching for => ''.

BTW: please use "squash and merge" while merging this PR, I used really bad commit messages...

It seems to be merged but I just wanted to clarify.
Two default parameters in config.php have been changed, while it was applied with command line parameters and only for this order.

The sort of untranslated items is not very interesting and if they are at the same end, they will be seen much better instead of searching through all the files.
Deleting @@ items is also good, but not as a default, and if they exist by default, and if the user wishes, he can delete them with the relevant parameter.
Anyway, this was my personal opinion.

@NabiKAZ With fixed order it is much easier to review diff, since it is clear which messages were added, changed or removed. It is not so clear if you start moving messages across the file.

I agree with @rob006 - sorted is better

@bizley
They will sort!
The subject of sort is the untranslated items that used to appear at the end of all translations and were separated so that they were easily visible to the translator.
But now they are mixed with all other translated and untranslated expressions, which makes it difficult to find untranslated items.

I don't think this is a big problem. Easy to find with quick search.


Replace deprecated method use

Pretty straightforward as it effectively inline the code from the deprecated method in Gradle.

Thanks for this @ljacomet!
@yahavi is currently working on gradle 6 compatibility of the plugin. He'll soon test your suggested fix as part of this task.


Allow to stop and resume neural network training

Fixes #309
Syntax is:
inference = SNPE(prior=prior)
inference = inference.append_simulations(theta, x)
inference.train(max_num_epochs=300)  # Pick `max_num_epochs` such that it does not exceed the runtime.

# Save `inference` and load it...

inference.train(resume_training=True, max_num_epochs=600)  # Run epochs 301 until 600.
posterior = inference.build_posterior()

Using the above syntax will be identical up to seeding to:
inference = SNPE(prior=prior)
_ = inference.append_simulations(theta, x).train()
posterior = inference.build_posterior()

Codecov Report

Merging #431 (f450d54) into main (5e71a43) will decrease coverage by 13.03%.
The diff coverage is 90.44%.

@@             Coverage Diff             @@
##             main     #431       +/-   ##
===========================================
- Coverage   79.77%   66.74%   -13.04%
===========================================
  Files          54       54
  Lines        3397     3482       +85
===========================================
- Hits         2710     2324      -386
- Misses        687     1158      +471

Flag
Coverage Δ

unittests
66.74% <90.44%> (-13.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sbi/inference/snle/snle_a.py
100.00% <ø> (ø)

sbi/inference/snpe/snpe_c.py
23.33% <ø> (-72.00%)
:arrow_down:

sbi/inference/snre/snre_a.py
50.00% <ø> (-50.00%)
:arrow_down:

sbi/inference/snre/snre_b.py
100.00% <ø> (ø)

sbi/utils/__init__.py
100.00% <ø> (ø)

sbi/utils/get_nn_models.py
76.19% <ø> (ø)

sbi/inference/posteriors/ratio_based_posterior.py
83.82% <60.00%> (-13.20%)
:arrow_down:

...inference/posteriors/likelihood_based_posterior.py
78.43% <75.00%> (-19.53%)
:arrow_down:

sbi/inference/posteriors/base_posterior.py
68.21% <87.09%> (-15.65%)
:arrow_down:

sbi/utils/sbiutils.py
82.92% <89.47%> (-3.74%)
:arrow_down:

... and 23 more

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 24f8a77...b8438a2. Read the comment docs.

any idea why this will decrease the test coverage by 13 percent?

not yet, I'll have to check.

Since the commit, coverage decreased especially due to the introduction of the analysis module. I can think about writing a test for this module later on.

Why does this help with large memory issues? We still load all data. Am I missing something?

Ah, then I was missing something. So when continuing training all the data from previous training is still used and one epoch runs over the old and new data? If yes, then never mind my comment :)

Yes, exactly! The only purpose of the commit is to be able to "interrupt" training and resume it later.


Refactor interfaces between modules

Refactor interfaces between modules so that it makes it easier to create unit tests for each module.

#26 solved this issue


Phantom wallet immidiately times out after the transaction confirmation request

Describe the bug
The phantom wallet times out when I try to send a transaction giving me no time to sign it.

To Reproduce

Desktop (please complete the following information):

OS: [macOS Monterey]
Browser [Brave]
Version [1.44.105]

Have you tried setting the blockhash you get back from getLatestBlockhash on the transaction?

Alternatively don't call getLatestBlockhash at all, because sendTransaction will do this for you (and set the blockhash) if you don't set it.

Hi @jordansexton
Thanks for your suggestions! I have tried not calling getLatestBlockhash at all, but it didn't help. It's probably worth mentioning that this code (without calling getLatestBlockhash):

was working before and then stopped after some time (as far as I remember). So I also suspect some API change there, which could have led to this error.
Here are my adapter-related package versions. Maybe the issue is there?
    "@solana/wallet-adapter-base": "^0.9.5",
    "@solana/wallet-adapter-react": "^0.15.5",
    "@solana/wallet-adapter-react-ui": "^0.9.7",
    "@solana/wallet-adapter-wallets": "^0.19.1",

Posting screenshots of code makes this harder than pasting your formatted code into Github.
Try this:
const { connection } = useConnection();

const transaction = new Transaction().add(
    new TransactionInstruction({
        data: Buffer.from('Hello, world!'),
        keys: [],
        programId: new PublicKey('MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr'),
    })
);

const signature = await sendTransaction(transaction, connection);

OR this:
const { publicKey } = useWallet();
const { connection } = useConnection();

const {
    context: { slot: minContextSlot },
    value: { blockhash },
} = await connection.getLatestBlockhashAndContext();

const transaction = new Transaction({
    feePayer: publicKey,
    recentBlockhash: blockhash
}).add(
    new TransactionInstruction({
        data: Buffer.from('Hello, world!'),
        keys: [],
        programId: new PublicKey('MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr'),
    })
);

const signature = await sendTransaction(transaction, connection, { minContextSlot });

I think the issue with your code may be that you're doing a bit of both. Either you can set the transaction's feePayer and recentBlockhash and provide the minContextSlot you used to obtain it OR you can let the adapter / wallet do this stuff for you. It's perfectly fine to not call getLatestBlockhashAndContext at all, because the adapter will do this.

Closing this as resolved since there hasn't been a response. Please let me know if the code in the comment above doesn't work for you.


pyodbc uses odbc 3.x features instead of 3.8

When connection pooling is on in unixodbc there is a connection reset procedure that needs to be run: https://github.com/lurcher/unixODBC/blob/9b31cd228d01e768a7ad9126d5da8860f1ed72a9/DriverManager/SQLConnect.c#L3904 Not running this causes connections in the pool to be left tainted will all sorts of badness such as the following not being done:
It resets all error states and numbers (like @@error)
It stops all EC's (execution contexts) that are child threads of a parent EC executing a parallel query
It will wait for any outstanding I/O operations that is outstanding
It will free any held buffers on the server by the connection
It will unlock any buffer resources that are used by the connection
It will release all memory allocated owned by the connection
It will clear any work or temporary tables that are created by the connection
It will kill all global cursors owned by the connection
It will close any open SQL-XML handles that are open
It will delete any open SQL-XML related work tables
It will close all system tables
It will close all user tables
It will drop all temporary objects
It will abort open transactions
It will defect from a distributed transaction when enlisted
It will decrement the reference count for users in current database; which release shared database lock
It will free acquired locks
It will releases any handles that may have been acquired
It will reset all SET options to the default values
It will reset the @@rowcount value
It will reset the @@identity value
It will reset any session level trace options using dbcc traceon()

This feature is only enabled if the environment is set to 3.8 or higher.  In pyodbc it's hard coded to 3.X which doesn't include this vital behavior. https://github.com/mkleehammer/pyodbc/blob/ee0ad21e7ab00c4ab974f332ab0ce22bb7ad776d/src/pyodbcmodule.cpp#L299
I'm happy to author a PR to enable this if it's something you would be open to.

Not all drivers support ODBC 3.8, but it does seem like a good idea to make this configurable.

I think each connection can have its own environment, which means its own odbc version. That seems like a major change versus allowing the default to be optionally 3.8.


[Task] We hope to add WeChat application messages for message push

Description
消息推送希望可以新增微信应用消息（微信就可以接收消息了，可以不用在下载企业微信app了）
开放API：
https://developer.work.weixin.qq.com/document/path/90236#接口定义
Task List
No response

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑🤝🧑👫🧑🏿🤝🧑🏻👩🏾🤝👨🏿👬🏿

Description
Message push hopes to add WeChat application messages (WeChat can receive messages, and you don’t need to download the enterprise WeChat app)
Open APIs:
https://developer.work.weixin.qq.com/document/path/90236#接口定义
Task List
No response

please assign this task to me

this feature has supported! 👍 thanks @hudongdong129


Theano-cuda: init at 0.8.2

Motivation for this change
This is an extension of the existing python package Theano-0.8.1 to add a functionality of running the code on an NVIDIA GPU. The minor upgrade to version 0.8.2 is required to provide compatibility with libgpuarray--9998.0. The libgpuarray package has a dependency on clblas which requires OpenCL 1.2. For this reason one needs to use cudatoolkit-7.5 in place of cudatoolkit-7.0.
The package builds fine with python-3.5, but many unit tests on GPU encounter a Cannot allocate memory problem error. The tests if one installs the package as python34Pacakges.Theano-cuda pass successfully:
nix-shell -p pkgs.python34Packages.Theano-cuda
rm -rf ~/.theano
theano-test

Note that the cuDNN part of the tests requires a GPU of compute capability >= 3.0.
Things done

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

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Let's use nix-prefetch-url to register the cuDNN library in the nix store. I have switched the versions of numpy and scipy to the default selections and squashed the commits.


camel.main.routes-include-pattern with a "*" wildcard may end up loading a route builder twice

When a camel-quarkus application is using camel.main.routes-include-pattern with a * wildcard, some
routebuilders/routeconfigurations resources might be loaded twice. Users may face error messages like below:

Failed to start route xyz because of Multiple consumers for the same endpoint is not allowed
Route configuration already exists with id: xyz

The simplest way to reproduce might be to amend the main-yaml/src/main/resources/applications.properties file with camel.main.routes-include-pattern = classpath:routes/*.yaml
Then, running the tests will show that route loading fails because of multiple consumers on a given endpoint. It might be due to the fact that a route is loaded twice.
The DefaultPackageScanResourceResolver seems guilty as a DefaultPackageScanResourceResolver.findInClasspath("routes/", resources, "*.yaml") returns a collection of 4 routes while only 2 are expected. It looks like the same underlying resource loaded from different class loaders are not equal. As such, the given resource can be returned twice in the Set<Resource>.
Not sure yet whether we could consider the issue to be in camel or camel-quarkus.

This is only an issue when the application is under test where multiple Quarkus class loaders are in play:

Quarkus base runtime class loader
Quarkus runtime class loader

At runtime there is just the RunnerClassLoader.
Maybe there should be an else clause added here to add the BasePackageScanResolver ClassLoader only if the TCCL was null:
https://github.com/apache/camel/blob/main/core/camel-base-engine/src/main/java/org/apache/camel/impl/engine/BasePackageScanResolver.java#L44
That way you avoid adding multiple ClassLoader instances.

Great to see that @jamesnetherton. Many thanks for handling it.


Handle closing {noformat} tags at the end of the line

If there's a {noformat} tag at the end of the line, it doesn't get processed and close the <pre> block.

I tested this out by viewing MANTA-3559 which has a block of text like this.

The Gerrit CR is here.

Abandoning in favor of #32.