Export view as image doesn't paint every elements correctly (bmp, png)

Version of Archi, Operating System
com.archimatetool.editor.buildid=201901281101
org.eclipse.swt.internal.deviceZoom=200
os.name=Windows 10
os.version=10.0
osgi.arch=x86_64
Expected Behaviour
Export a model view as an image.
Actual Behaviour
Export a model view as an image. All the elements are not equally and correcty painted.
Steps to Reproduce the Behaviour

Export a model view as an image (first uploaded png file)
Copy as Image to Clipboard (second uploaded png file)

Electro Choc.zip

I'm assuming you have a hi-res display.
Can you check whether this happens in the previous version of Archi? I made some changes to the resolution of exported images on hi-res systems. I checked on a Retina MacBook and all seemed OK, unless Windows is different.
@jbsarrodie Can you check this JB on hi-res?

OK, to reproduce this I set the scaling on my Windows machine to 200% and I can the problem, as well as a smaller magic connector cursor and other things.
What I don't understand is why this all works OK on a Retina Mac and not on a Windows hi-res setup?

In order to fix this problem I'm going to need some help from the users.
On a Retina Mac, the device zoom is reported as 200% but images are 2x too big (exported images, the magic cursor, the format painter cursor and the sticky palette icons in the Sketch and Canvas views) so we render these at 100%
On Windows hi-res, the device zoom is reported as 200% but images are too small unless rendered at 200%.
So what's going on? Anyone like to help?

Can you check this JB on hi-res?
So what's going on? Anyone like to help?

Sorry but I don't have access to hi-res monitor (I use full-hd only) :-(

OK. This is going to be a problem. On my Retina Mac the resolution is 1440x900 so it's not really "hi res" (doubles pixels). But Eclipse SWT reports device zoom as 200. This device zoom number is used to calculate image scale. So on WIndows with a resolution of 2880x1800 device zoom is also 200. Seems no way to know if it's HDPI or not.

Seems that Modelio tool has the same problem.

On my Retina Mac the resolution is 1440x900

The physical resolution should be double than that (2 880 × 1 800), thus eclipse reporting device zoom as 200 is normal.

Seems no way to know if it's HDPI or not.

That's maybe because HDPI doesn't really mean anything...
See https://medium.com/elementaryos/what-is-hidpi-and-why-does-it-matter-b024eabea20d and https://medium.com/elementaryos/top-3-misconceptions-about-hidpi-f5ef493d7bf8
I theory I should be able to force pixel doubling on my FullHD Linux laptop to simulate HDPI, but I still don't know how to do it.

OK, so the problem is this:
In order to render an image we do this:

Question: why doing this scaling at all ? Isn't it easier to simply export at 100% and let users display this image the way they want ?
My issue here is that as figures don't have real border width, exporting a view at 200% is not equivalent to double pixels of a 100% export as in both cases borders will be only 1px.

No, because if the user sets the zoom to 200% on Windows exporting at 100% causes the problem.
So, the issue is not about the resolution but the zoom level set in Windows (and Linux?) Mac reports the zoom level as 200% when it's not really 200%

Mac reports the zoom level as 200% when it's not really 200%

If you have a retina display it is 200%. Why do you say it's not?

I mean that if you scaled the images by 200% on the Mac they are double sized.

You can set the scaling to 200% in Windows regardless of your screen resolution (will look a bit big) and then deviceZoom is 200. So it's this setting that's the problem. Mac uses 4 pixels per pixels on Retina display, reports 200%, but it behaves like 100%

I'll try to make this clearer.
On Windows with resolution 1400x900 and scaling set to 100% the device Zoom is 100%
On Windows with resolution 1400x900 and scaling set to 200% the device Zoom is 200%
On Mac with resolution 1400x900 (can't set the scaling) the device Zoom is 200%
So Mac always reports 200%

On Windows with resolution 1400x900 and scaling set to 100% the device Zoom is 100%
On Windows with resolution 1400x900 and scaling set to 200% the device Zoom is 200%
On Retina Mac with resolution 1400x900 (can't set the scaling) the device Zoom is 200%
So Retina Mac always reports 200%

Ok, this is clearer... and normal: Mac doesn't allow you to change scaling factor as it is built-in. In addition, the resolution reported is not the physical one but the "virtual one" (taking x2 scaling into account). Windows does it the opposite: it always reports (and lets you set) the physical resolution, but lets you choose a scaling factor.
What is unclear to me is which part of the UI are rendered at the physical vs "virtual" resolution.
FWIW, I've just found how it works on Linux and this is exactly the same approach as Windows: you define the physical resolution (1920 x 1080 in my case, i.e. FullHD) and you set the scaling factor (gsettings set org.gnome.desktop.interface scaling-factor 2). So I should be able to test if I know what to test exactly...

What I need to know is when to set the device zoom when getting Image Data:
Normally this would be:
int deviceZoom = ImageFactory.getDeviceZoom();
ImageData imageData = image.getImageData(deviceZoom);

On WIndows this works fine and images are OK.
On Mac this is setting the images 2x too big in the UI and when exporting views.
I wonder if ImageFactory.getDeviceZoom(); should be set to return 100 if on Mac?

So I did some tests on Linux  (set the scale factor using two different methods) and never go an issue in the UI nor in image export.
When using gsettings getDeviceZoom() return according results (ie. 200% with my test) but when using xrandr getDeviceZoom() always return 100%.

Using latest Archi 4.3.2. on Windows with scale factor 200 you'll see:

tiny magic connector cursor
tiny format painter cursor
corrupt exported images

I'm wondering if this device zoom scaling thing is just a Windows thing? But what about hi-res external monitors for Mac?
I think I'll add a preference "Use device zoom" with defaults of WIndows=on, Mac/Linux=off. Then if users get problems they can experiment with it on/off.

(The "Close and Comment" button is too big).

I think I'll add a preference "Use device zoom" with defaults of WIndows=on, Mac/Linux=off. Then if users get problems they can experiment with it on/off.

Might be a good solution

If deviceZoom is 200% on Windows then exported images are 2x bigger than when deviceZoom is 100%. Is this expected behaviour?

My issue here is that as figures don't have real border width, exporting a view at 200% is not equivalent to double pixels of a 100% export as in both cases borders will be only 1px.

And this is actually the cause of the problem where device scaling > 200%.
It's the lines and borders that are not being drawn properly if the device scaling > 200% and the image is exported at 100% scaling. I experimented and set line width to 1 and exported at 100% scaling with Windows set to 200%. The image was OK.
So exporting images at 200% on Windows is actually a workaround for the problem. If we were using actual line widths it would export OK. But then there are other problems with setting line widths (SVG doesn't render properly, zoom diagram not rendering properly).

And this is actually the cause of the problem where device scaling > 200%.

Actually it may not be as simple as using proper line width. Exporting a Zest (Visualiser) image also needs to be scaled up otherwise the connections look bad. But that may be due to Zest not using anti-aliasing on connections.

I've spent a lot of time investigating this.
When creating image data we have to call Image.getImageData(zoom) where zoom is reported by the system to be 100, 200 on Retina Mac, or another number on Windows depending on the scaling.
On Retina Mac and Linux (I think) if we use a zoom of 100 regardless of the zoom reported by the system the exported images look OK.
But not so on Windows, because the image size down-scaling messes up the image. So we have to use the zoom level reported by the system which results in larger image files.
I don't know why this should be.

I've created a "zoom" branch with the changes. This code is a mixture of what we had before I changed things to use 100% zoom in commit bfae973f3ad86075004e7903b2d347baab0b2760 and a check to see if we are on Windows or not and if we are, to use the OS scaling factor.

I guess on Mac retina the resolution is reported as 1400x900 and zoom as 200 so it's not the same as on Windows where the resolution is reported as 2800x1800 and zoom 200?

So this works on my test configurations:
Windows with scaling of 100, 200 and 300
Linux Mint with scaling of "Double"
Mac Retina
But...I don't know about Mac with external hi-res monitor.

But of course this now leads to inconsistencies between platforms with hires systems. On Windows with scaling of 200 or greater images are 2x size, but not on Mac or Linux.
Prior to my changes in bfae973f3ad86075004e7903b2d347baab0b2760 all images were exported at 2x when zoom was reported as 200.

On Windows with scaling of 200 or greater images are 2x size,

IMHO the exact image size is not an issue, but the relative width of figure border is. So can you share image export for the same view, but done on different OS so that I can compare them and check if I see any issue?

The figure border is always the same 1 pixel in all cases. This is a main problem why we have to use 2x export on Windows because it doesn't downscale to 1x very well.

So can you share image export for the same view, but done on different OS

With the new system or at 100% or....?

With the new system or at 100% or....?

Sorry. With the new system and scaling set manually to 200% on windows, Retina on Mac and Linux with "double" scaling..

The figure border is always the same 1 pixel in all cases. This is a main problem why we have to use 2x export on Windows because it doesn't downscale to 1x very well.

I really have to find a Retina or HiDPI laptop to test myself. I really don't understand what this looks like on windows with scaling set to 200% in Archi itself and when exporting...

I set scaling to 200% in Windows on a non hi-res screen to test. Everything is massive and it's hard to work with but OK for testing.

Windows with scaling set to 200%

Mac Retina

Windows with scaling set to 200%

Thank you, so this is what I feared, as borders are only 1px but figures are twice the size, this no more looks like a "normal" view in Archi.
Can I ask you a screenshot of the whole Archi under windows with 200% scaling and this view opened (and set to 100% in Archi, which is the default) please ?
The question I'm asing to myself is how does it look like when someone works with Archi: does  figure border using only one physical pixel (thus really tiny) or is it automatically scaled and rendered on 2 physical pixels to simulate a "LowDPI" rendering ?

Linux Double

Can I ask you a screenshot of the whole Archi under windows with 200% scaling and this view opened (and set to 100% in Archi, which is the default) please ?

OK, this was taken on the MacBook Retina with Windows running in a VM and 2880x1800 and scaling at 200%

OK, this was taken on the MacBook Retina with Windows running in a VM and 2880x1800 and scaling at 200%

Thank you.

The question I'm asing to myself is how does it look like when someone works with Archi: does figure border using only one physical pixel (thus really tiny) or is it automatically scaled and rendered on 2 physical pixels to simulate a "LowDPI" rendering ?

So answer is border is only one physical pixel, thus tiny. So I think we have an issue but are back to borderwidth hack... Don't think we'll solve it anytime soon (for 4.3.3 I mean)

thus tiny.

Bit it looks the same as when using 100% scaling when working in Archi, you don't really know it's any different.
But there are issues around setting the figure line width to an actual amount in Draw2D figures. The line can look different (1) At different zoom levels in Archi (2) When exporting to PNG/BMP/JPG (3) When exporting to SVG. I never could get it working in all cases.

But for now, the fix I've created will work in order to get images looking OK again on Windows with high scaling. It fixes the regression, so we need to get the next maintenance build out soonish.

so we need to get the next maintenance build out soonish.

Yes, just wait for me to fix the html/sql export thing (will do during the week-end)

OK. Let's aim for next week.

More information...
exporting images at 100% zoom level on a Retina Mac is the right thing to do. Before I looked at this issue images were exported at 200% on Retina Mac. But the quality of the image is not even as good as exporting with the image size set to 200% in the Image export dialog.
This is exported with device scaling at 200% and export image dialog set to 100%. View the image at actual size and you can see the fonts are blurred:

This is exported with device scaling at 100% and export image dialog set to 200%. View the image at actual size and you can see the fonts are not blurred:

Fixed in Archi 4.3.3. Feel free to re-open or create another issue if there's still a problem.

Eveverything ok after this upgrade. Thanks.Avec mes meilleures salutationsKind regardsMichel WickyOsima Conseils, conseils en organisation et technologies de l'informationArchitecture d'entreprise et solutions, Accompagnement du changement, Direction et conduite de projetRuelle de Chaucey 21807 BlonaySwitzerlandmobile +41 79 414 94 44email michel.wicky@osima.chhttp://www.linkedin.com/company/osima-conseilhttp://ch.linkedin.com/in/michelwickyThis message may contain confidential and proprietary material for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.-----"Phil Beauvoir"<EMAIL_ADDRESS>a écrit : -----A : "archimatetool/archi"<EMAIL_ADDRESS>: "Phil Beauvoir"<EMAIL_ADDRESS>: 12/02/2019 13:06Cc: "Michel Wicky"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>: Re: [archimatetool/archi] Export view as image doesn't paint every elements correctly (bmp, png) (#439)Fixed in Archi 4.3.3. Feel free to re-open or create another issue if there's still a problem.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.


Clean cache for CI/Nightly

clean cache
remove merged additional PRs

UT failures are not related with this change


Word based suggessions does not respect word separators

VSCode Version: 1.36.0
OS Version: Windows 10 Version 19.03 (OS Build 18362.175)

Steps to Reproduce:

Remove '/' and '-' from editor.wordSeparators setting.
Edit a plain text file, words like snacks/fruits/green-apple are not shown in the suggestion list.

This is useful for editing Scheme language files for which word definition from language is not available.

Does this issue occur when all extensions are disabled?: Yes

That's the design, word based suggestions honour the language specific word definition


Markdown formatting broken in ScrollView Remarks

The markdown formatting for the C# example on https://docs.microsoft.com/en-us/dotnet/api/xamarin.forms.scrollview?view=xamarin-forms#remarks is formatting incorrectly.

I just discovered this on multiple Forms API docs so came to the repo to see if anyone else had noticed it. The content hasn't been published since last year, so this will be due to a back-end change.
Interestingly, the build system tells me that I made a config change on 16th June this year, when I didn't. That also signals a back-end change.
I'll follow up with the team in China.

I've logged a bug with the docs engineering team.

This is fixed!


Failed Instance Resolution for State

If I define
module Foo where

import qualified Control.Monad.State as ST
import qualified Control.Monad.State.Class as ST

ident :: forall a. a -> a
ident a = a
ident' :: Number -> Number
ident' a = a

then
a :: ST.State Number Unit
a = ST.modify ident'

compiles/works fine.
However,
a :: ST.State Number Unit
a = ST.modify ident

complains that
No instance found for Control.Monad.State.Class.MonadState u7 (Control.Monad.State.Trans.StateT Prim.Number Data.Identity.Identity)

.
(Both versions work in Haskell.)

I think the solution to this might be functional dependencies, which would make this a duplicate of https://github.com/purescript/purescript/issues/1580. Not entirely sure, though.

I'm pretty sure this is related to the lack of functional dependencies too, so this should be fixed in the next release.


Error: No QueryClient set, use QueryClientProvider to set one

No idea why this happens, but when I tried to implement react-scan in my React Native / Expo project, I get this error in reference to @tanstack/react-query set-up. When I remove the scan() method from the _layout file, the error goes away. Strange. Appreciate your work on this and excited to use it in the future!
My _layout file looks like this:
import { scan } from "react-scan";
import React, { useEffect, useState } from "react";

scan({
  enabled: process.env.NODE_ENV === "development",
  log: true, // logs render info to console (default: false)
  clearLog: false, // clears the console per group of renders (default: false)
});

export const Providers = () => {
  const [queryClient] = useState(
    () => new QueryClient(DEFAULT_QUERY_CLIENT_OPTIONS),
  );

  return (
    <ConfigProvider config={{ ...config, supabase, nanoid }}>
      <StatusBar style="dark" />
      <QueryClientProvider client={queryClient}>
        {...more providers and the main UI layout}
      </QueryClientProvider>
    </ConfigProvider>
  );
};

export default Sentry.wrap(Providers);

@jhanstra we don't support RN yet!

@aidenybai are you planning to support React Native some time in the future?
also, if you attempted to support, what were main issues/blockers? it'd be good to know if somebody were to consider contributing towards React Native support :)

https://x.com/endlessFrontend/status/1861973405664514328

Going to test the react-native branch :)


Enable shared libraries.

How are the python bindings built with this, they should be statically linked as they don't use the C API.


Add dak.concatenate

Fix for #123

For axis>0, the lengths of each partition does not change.
>>> one = ak.Array([[1, 2, 3], [], [100, 101]])
>>> two = ak.Array([[4, 5], [10, 11, 12, 13], [102]])
>>> ak.concatenate([one, two], axis=1).show()
[[1, 2, 3, 4, 5],
 [10, 11, 12, 13],
 [100, 101, 102]]

You just need to ensure that all of the arrays going into the concatenation, one, two (and maybe more) all have the same length (error if they don't) and can all be partitioned the same way (maybe repartition if not?). Then you can pass partition i of each array to a separate worker that uses Awkward's ak.concatenate on all the arrays for partition i and call the results for each partition the final result.
This isn't one, like ak.flatten, that changes the lengths of each partition, because the length is defined by the number of lists, not the number of elements in them.

Codecov Report

Merging #125 (5c2c404) into main (7fe448a) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #125      +/-   ##
==========================================
+ Coverage   95.55%   95.60%   +0.05%
==========================================
  Files          17       18       +1
  Lines        1686     1708      +22
==========================================
+ Hits         1611     1633      +22
  Misses         75       75

Impacted Files
Coverage Δ

src/dask_awkward/lib/__init__.py
100.00% <100.00%> (ø)

src/dask_awkward/lib/operations.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I'm going to go ahead and merge this in for axis>=0 support; we can expand on this more in the future.


Add blocks space parameter to normalization step

The block_space parameter was being used in the data normalization step.  However it was not being set in that step. Instead it was being carried over from a previous computational step. This adds block_space as a parameter for the normalization step and documents it as one. Should make things a bit clearer.

Failures experienced here should be fixed by PR ( https://github.com/nanshe-org/nanshe_workflow/pull/125 ).


fix: subscription broadcast

Subscriptions aren't rebroadcasted! This PR fixes this and adds a test.

looks like there is a import missing around
 error • The function 'initHiveForFlutter' isn't defined • test/widgets/query_test.dart:[11](https://github.com/zino-hofmann/graphql-flutter/runs/5229431340?check_suite_focus=true#step:6:11)5:11 • undefined_function

@vincenzopalazzo, removed!

Thanks, this is great to have 😁🙏


knex weighs 8.46MB (90% is deps)

Considering using knex in a project and decided to weigh it first.
https://packagephobia.now.sh/result?p=knex
knex.js itself is just 876kB of the 8.46MB, the rest is dependencies.
http://npm.broofa.com/?q=knex
liftoff adds 2.57MB (used only for CLI), bluebird & types add 660kB (can be replaced with native Promise?), lodash adds 1.34MB (can be reduced by only requiring needed functions, or replacing with [1] variants).
some other deps are used only for cli stuff as well. is it possible to split CLI into its own package if some of the weight cannot be reduced?
[1] https://github.com/you-dont-need/You-Dont-Need-Lodash-Underscore

also, src and scripts can probably be removed from the npm distribution, shaving ~400kB or about 50% of knex itself).

Thanks for the analysis. If some day slimming down package size is a priority this info will be helpful.
Closing as there is nothing to do for now. Btw. knex + dependencies to run querybuilder on browser is like 370kB (pretty huge, but it contains all the dialects).

If some day slimming down package size is a priority this info will be helpful.

given how old/mature this lib is, and that it's 8.5MB with 30% being a single CLI dep, i suspect that "some day" === "never". you could just be realistic about it :)
i would actually be interested in helping with this effort if there is a real chance of the work being integrated, given that all tests pass.
the codebase is pretty big and trying to figure out exactly what each dep does in this lib is a bit daunting. can you briefly tell me what liftoff is used for and why Bluebird is used instead of native Promises? Also, is Node 6.x the permanent minimum version? 6.x will EOL in April and 8.x will EOL in Dec. Can we start dropping various polyfills and aim for >= 10.x?

Btw. knex + dependencies to run querybuilder on browser

given that knex is a query builder, i don't see the point of this anyways, besides maybe some demo playground for learning.

If some day slimming down package size is a priority this info will be helpful.

given how old/mature this lib is, and that it's 8.5MB with 30% being a single CLI dep, i suspect that "some day" === "never". you could just be realistic about it :)

If stable version and complete rewrite is done some day I don't see this completely impossible. But... some day probably means distant future... flying cars, hover boards 'n stuff ;)

i would actually be interested in helping with this effort if there is a real chance of the work being integrated, given that all tests pass.

If it doesn't make development / fixing knex harder I don't see any reason why not to accept PRs making it slimmer. But for example dropping bluebird cannot be done yet etc. (there is another issue about it).

the codebase is pretty big and trying to figure out exactly what each dep does in this lib is a bit daunting. can you briefly tell me what liftoff is used for and why Bluebird is used instead of native Promises? Also, is Node 6.x the permanent minimum version? 6.x will EOL in April and 8.x will EOL in Dec. Can we start dropping various polyfills and aim for >= 10.x?

Node 6 support is planned to  be dropped around April.

Btw. knex + dependencies to run querybuilder on browser

given that knex is a query builder, i don't see the point of this anyways, besides maybe some demo playground for learning.

For example knex documentation page uses it to show generated queries for examples for each dialect. Also some mobile frameworks, which are using browser / some other js engine than node to create queries benefits from it. With plain query builder part one can write own glue separately how to pass those queries to database driver.

why Bluebird is used instead of native Promises?

Because this library was started in 2012 when there was no such thing as async/await, or bluebird, and Promises were generally frowned upon but I decided to go with them anyway... first using Q, then when.js and finally Bluebird. I'm currently working on a project where the codebase was started in 2014 using knex and it very much depends on the guarentees of Bluebird. Taking it out of knex wholesale would be a full rewrite for this project and I suspect it wouldn't be the only one. I agree we can dramatically simplify things internally using async/await but at this point I'd rather wait until node 6 is EOL'ed before doing this so we don't need to Polyfill.

can you briefly tell me what liftoff is used

Liftoff is used for the CLI, to allow you to have the knexfile (another concept we should probably do away with), scripts, etc. be specified in different languages other than js. CoffeeScript was quite popular when this project was written and is actually what it what was originally written in. gulp-cli uses Liftoff for the same reason.
Sure, we can split this out into like a knex-cli, but if I take the time do that I'd personally rather do it alongside structuring the project into a multi-package monorepo, clean up the tests, etc.
If you want to open a PR with knex-cli fully split out, tests and all, but within the same codebase I would be open to making that change. I have access to that package on npm since this was something I obviously wanted to do but never got to.

given how old/mature this lib is, and that it's 8.5MB with 30% being a single CLI dep, i suspect that "some day" === "never". you could just be realistic about it :)

It's old, I wouldn't say mature. At some point I would like to get around to doing a proper rewrite, I've started a few in the past and each time have gotten new ideas on how to approach it. Currently leaning toward a sort-of hybrid approach of incremental and full-rewrite, e.g. a fork which I can iterate on with a real-world codebase/test-suite without worrying about needing a solid upgrade path right away, or doing all of the languages at once, and then merging that back in.
I think I have some better ideas for it now but it's just a matter of where my time is best spent. To me knex generally works, so I typically just use it in every-day things without too many complaints. I've also been focused on building http://nexus.js.org lately so I haven't had as much time for knex (you might notice that library has zero dependencies).
Maintaining legacy projects is hard. There's so many things I would have done differently in hindsight but I don't really need to justify all of the choices/mistakes made here. If there's time to get around to fixing these things with a proper migration path then it'll happen, if not, feel free to use or build something else that aligns better with your view of how much a package should weigh.

 IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

For example knex documentation page uses it to show generated queries for examples for each dialect.

It does? Can you give me a example documentation section where this is true? I looked at the .returning() section which I think should produce different queries and there was no change whatsoever when alternating between all the available dialects in the dropdown.

For example knex documentation page uses it to show generated queries for examples for each dialect.

It does? Can you give me a example documentation section where this is true? I looked at the .returning() section which I think should produce different queries and there was no change whatsoever when alternating between all the available dialects in the dropdown.

Its currently broken / fixes are not yet released to live page. There are issues about it in the documentation repo. Page shows some javascript errors, which breaks also the functionality of changing dialect.


Mob Crusher generating stacks of redstone from mobs

Industrial Foregoing Version: 1.7.0
TeslaCoreLib Version: 1.12-1.0.12
Mob Crusher is generating 1-2 stacks of redstone for each mob it kills, in addition to the normal drops
Edit: had the mobs not spawning with the crusher running and redstone was still appearing in the item pick up area

Do you have something that drops redstone nearby?

no the mob farm is separate from the rest of everything.

We're using cursed earth to spawn mobs, so the witches do drop redstone

Yeah, witches drop redstone but stack at a time?

no idea, we are in a sky island map and the mob farm is stand alone on its own island, we haven't had this happen since the other night,

no it hasnt happened again, we did have it running after this incident, but there is no way we had dropped the amount of redstone the thing produced, it is connected to a drawer controller via the ender chest, the first time i noticed it there was 34k redstone blocks, i did not turn the mob crusher off and maybe 5-10 minutes later it was almost at 40k redstone blocks,

I will close the issue now, report if there is more cases

doing the same thing for us but with clay, killing any mobs gives you stacks of clay..
industrialforegoing-1.12.2-1.8.2-121.jar

Can comfirm this is a real issue. Had the same today on a servers, and the admins on the servers couldn't wrap their head around it.
I didn't alter my mob-farm setup for two days, and was checking my drops in the attached chest. All out of a sudden, there were a few redstone in there. Nothing too odd, because witches drop those (and I did get a witch hat a few moments earlier), but them I kept seeing redstone flowing in.
At first I thought it was a mob that dropped a full stack of redstone, so I asked in chat if there was any mob that dropped a full stack of redstone.
But it didn't stop there... it kept generating redstone, and it even seemed as if the rate at which the redstone was generated kept speeding up.
It generated 2 full double chests of redstone, before I cut the power and reapplied it. It then functioned as normal.

What version are you using?

Note sure, I only play occasionally on a server. I'm in no means an expert.
I experienced the bug on FTB Revelation 1.6.0.
Not sure if you can determine the version of Industrial Foregoing with that info.


Feature Request: Add Support for BGP Communities in Feed Processing

Hi @ebarkie,
First off, thank you for creating and maintaining this project! It's a fantastic tool for managing threat intelligence feeds and integrating them with GoBGP for blackholing malicious routes.
I'd like to request a feature enhancement to add support for BGP communities in the feed processing. Currently, the software supports multiple feeds, which is great, but it doesn't allow for the use of BGP communities to tag or differentiate routes based on their source feed. Adding this functionality would enable users to:

Differentiate Feeds: Assign specific communities to routes based on the feed they originate from, making it easier to identify and manage them downstream.
Policy Control: Apply routing policies or filters based on the community tags, allowing for more granular control over how routes are handled.
Scalability: Simplify the management of multiple feeds by leveraging community-based tagging instead of relying solely on feed-specific configurations.

Proposed Implementation:

Add an optional configuration parameter for each feed to specify a BGP community (e.g., 64512:100)
When processing a feed, assign the specified community to all routes derived from that feed
Ensure that the community tags are propagated to the BGP daemon and included in the advertised routes

Example Configuration:
feeds:
  - name: "abuse.ch"
    url: "https://example.com/abusech-feed"
    community: "64512:100"
  - name: "spamhaus"
    url: "https://example.com/spamhaus-feed"
    community: "64512:200"

Benefits:
This feature would greatly enhance the flexibility and usability of the tool, especially for users managing a large number of feeds or complex routing environments. It would also align with best practices for BGP route management by leveraging communities for route tagging and policy enforcement.
Please let me know if this is something you'd consider implementing. I'd be happy to provide further details or assist with testing if needed.
Thanks again for your hard work on this project!

Hey @soakes, apologies for not responding sooner.
Thanks for the detailed and very well thought out feature request!  I'm not actively using this any more but it's a great idea and I think it would be pretty easy to implement, so I'd be willing to give it a shot.
The only tradeoff I can think of is that we would need to summarize the routes per-community, but that's a conscious choice someone would be making by using multiple communities.
I'll try to take a stab at this some time over the next few days..

Hey @soakes, apologies for not responding sooner.
Thanks for the detailed and very well thought out feature request! I'm not actively using this any more but it's a great idea and I think it would be pretty easy to implement, so I'd be willing to give it a shot.
The only tradeoff I can think of is that we would need to summarize the routes per-community, but that's a conscious choice someone would be making by using multiple communities.
I'll try to take a stab at this some time over the next few days..

Hi @ebarkie,
No worries at all about the delay in responding, and thank you so much for taking the time to consider my feature request!
I really appreciate your willingness to give it a shot, especially since you're not actively using the tool anymore. It's such a useful tool, and it's been incredibly helpful for me, so I just wanted to say a big thank you for all the work you've put into it.
The tradeoff you mentioned about summarizing routes per-community makes total sense, and I completely understand that it would be a conscious choice for users. I'm sure whatever approach you take will work great!
Thanks again for your time and effort, and I hope you have a wonderful holiday season. Wishing you a Merry Christmas and all the best for the New Year! 🎄

Released as v0.10.0!


Lambda: removes an unneeded pair of parentheses

In the chapter on lambda calculus, this patch removes an unneeded pair of parentheses in a typing judgment example.

This is showing conflicts, and when I press the "Resolve conflicts" button it loops (possibly due to bad internet connectivity). Marko, can you resolve the conflict?

This is showing conflicts, and when I press the "Resolve conflicts" button it loops (possibly due to bad internet connectivity). Marko, can you resolve the conflict?

Dear Philip, I just resolved the conflict and it should be ready for merging.
On a semi-related note, this is just a reminder that there is an open pull request where I believe no actual changes need to be done so I would appreciate if you could take a look at it again: PR #282.

Dear Philip, this is a gentle reminder of this pull request. There are no more conflicts and the patch is ready for merging.


Set readPending to false when ever a read is done

Motivation:
readPending is currently only set to false if data is delivered to the application, however this may result in duplicate events being received from the selector in the event that the socket was closed.
Modifications:

We should set readPending to false before each read attempt for all
transports besides NIO.
Based upon the Javadocs it is possible that NIO may have spurious
wakeups [1]. In this case we should be more cautious and only set
readPending to false if data was actually read.

[1] https://docs.oracle.com/javase/7/docs/api/java/nio/channels/SelectionKey.html
That a selection key's ready set indicates that its channel is ready for some operation category is a hint, but not a guarantee, that an operation in such a category may be performed by a thread without causing the thread to block.
Result:
Notification from the selector (or simulated events from kqueue/epoll ET) in the event of socket closure.
Fixes #7255

Cherry-picked into 4.0 (687a2e51cfc1019ada2c7116a094cc8a33f73de2)


Icon not displayed

My options

Hi @GengchenXU , is this on Windows or Linux?
Does installing the webfont solve your issue?
https://github.com/ajilderda/joplin-macos-native-theme/raw/main/src/webfont/phosphor.ttf

Hi @GengchenXU , is this on Windows or Linux?
Does installing the webfont solve your issue?
https://github.com/ajilderda/joplin-macos-native-theme/raw/main/src/webfont/phosphor.ttf
on windows

Hi @GengchenXU , is this on Windows or Linux?
Does installing the webfont solve your issue?
https://github.com/ajilderda/joplin-macos-native-theme/raw/main/src/webfont/phosphor.ttf

Thank you, I just saw the https://github.com/ajilderda/joplin-macos-native-theme/issues/21


Optimization phase is unstable and returns nan loss values

Hi
First and foremost, thank you for making this awesome project public for us to play with, i greatly appreciate it.
So I am running this project locally on an Nvidia ampere card using CUDA 11.3.
Everything seems to work, but 9 out of 10 Pictures produce unstable optimization runs.
Also some pictures need multiple runs, or they crash. So it is a big hit or miss, if a picture will process.
By crash I mean the optimization loss values all become "nan". Example:
Optimizing 64x64
face:  nan; eye:  nan; contextual:  nan; color_transfer:  nan; noise:  nan: 100%| 750/750 [08:49<00:00,  1.42it/s]

As you can see in the above picture, the optimizing runs for a while, then the loss values turn into "nan's".
What can I do to troubleshoot this?
My environment:
python 3.8.5
pytorch: 1.10.1 py3.8_cuda11.3_cudnn8_0
torchvision: 0.11.2  py38_cu113
cudatoolkit: 11.3.1

So today I looked at the closed issues and I found a workaround here: https://github.com/Time-Travel-Rephotography/Time-Travel-Rephotography.github.io/issues/7#issuecomment-1051745608
It seems to work flawless.
Big thanks to ialhashim


ReplaceLambdaWithMethodReference operates on groovy.lang.Closures.

Issue discovered on Netflix/astyanax.

@traceyyoshima Is this a regression caused by my recent work on this recipe? I wasn't actually aware that the Java recipes would also get applied to Groovy code. So it looks like the Groovy LST model extends the Java one?

@traceyyoshima Is this a regression caused by my recent work on this recipe? I wasn't actually aware that the Java recipes would also get applied to Groovy code. So it looks like the Groovy LST model extends the Java one?

Ya, the Groovy LST extends J so that common java recipes may be applied to Groovy as well.
Groovy types have a super type of GroovyObject and a GroovyObject has a super type of java.lang.Object.
So, there are a lot of shared types between the two languages.


The package url_launcher 6.2.6 is build with an older kotlin version (expected 1.8, got 1,6)

What package does this bug report belong to?
url_launcher
What target platforms are you seeing this bug on?
Windows
Have you already upgraded your packages?
Yes
Dependency versions
pubspec.lock
# Generated by pub
# See https://dart.dev/tools/pub/glossary#lockfile
packages:
  async:
    dependency: transitive
    description:
      name: async
      sha256: "947bfcf187f74dbc5e146c9eb9c0f10c9f8b30743e341481c1e2ed3ecc18c20c"
      url: "https://pub.dev"
    source: hosted
    version: "2.11.0"
  boolean_selector:
    dependency: transitive
    description:
      name: boolean_selector
      sha256: "6cfb5af12253eaf2b368f07bacc5a80d1301a071c73360d746b7f2e32d762c66"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.1"
  characters:
    dependency: transitive
    description:
      name: characters
      sha256: "04a925763edad70e8443c99234dc3328f442e811f1d8fd1a72f1c8ad0f69a605"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.0"
  clock:
    dependency: transitive
    description:
      name: clock
      sha256: cb6d7f03e1de671e34607e909a7213e31d7752be4fb66a86d29fe1eb14bfb5cf
      url: "https://pub.dev"
    source: hosted
    version: "1.1.1"
  collection:
    dependency: transitive
    description:
      name: collection
      sha256: ee67cb0715911d28db6bf4af1026078bd6f0128b07a5f66fb2ed94ec6783c09a
      url: "https://pub.dev"
    source: hosted
    version: "1.18.0"
  cupertino_icons:
    dependency: "direct main"
    description:
      name: cupertino_icons
      sha256: ba631d1c7f7bef6b729a622b7b752645a2d076dba9976925b8f25725a30e1ee6
      url: "https://pub.dev"
    source: hosted
    version: "1.0.8"
  fake_async:
    dependency: transitive
    description:
      name: fake_async
      sha256: "511392330127add0b769b75a987850d136345d9227c6b94c96a04cf4a391bf78"
      url: "https://pub.dev"
    source: hosted
    version: "1.3.1"
  flutter:
    dependency: "direct main"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_test:
    dependency: "direct dev"
    description: flutter
    source: sdk
    version: "0.0.0"
  flutter_web_plugins:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.0"
  leak_tracker:
    dependency: transitive
    description:
      name: leak_tracker
      sha256: "7f0df31977cb2c0b88585095d168e689669a2cc9b97c309665e3386f3e9d341a"
      url: "https://pub.dev"
    source: hosted
    version: "10.0.4"
  leak_tracker_flutter_testing:
    dependency: transitive
    description:
      name: leak_tracker_flutter_testing
      sha256: "06e98f569d004c1315b991ded39924b21af84cf14cc94791b8aea337d25b57f8"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.3"
  leak_tracker_testing:
    dependency: transitive
    description:
      name: leak_tracker_testing
      sha256: "6ba465d5d76e67ddf503e1161d1f4a6bc42306f9d66ca1e8f079a47290fb06d3"
      url: "https://pub.dev"
    source: hosted
    version: "3.0.1"
  matcher:
    dependency: transitive
    description:
      name: matcher
      sha256: d2323aa2060500f906aa31a895b4030b6da3ebdcc5619d14ce1aada65cd161cb
      url: "https://pub.dev"
    source: hosted
    version: "0.12.16+1"
  material_color_utilities:
    dependency: transitive
    description:
      name: material_color_utilities
      sha256: "0e0a020085b65b6083975e499759762399b4475f766c21668c4ecca34ea74e5a"
      url: "https://pub.dev"
    source: hosted
    version: "0.8.0"
  meta:
    dependency: transitive
    description:
      name: meta
      sha256: "7687075e408b093f36e6bbf6c91878cc0d4cd10f409506f7bc996f68220b9136"
      url: "https://pub.dev"
    source: hosted
    version: "1.12.0"
  path:
    dependency: transitive
    description:
      name: path
      sha256: "087ce49c3f0dc39180befefc60fdb4acd8f8620e5682fe2476afd0b3688bb4af"
      url: "https://pub.dev"
    source: hosted
    version: "1.9.0"
  plugin_platform_interface:
    dependency: transitive
    description:
      name: plugin_platform_interface
      sha256: "4820fbfdb9478b1ebae27888254d445073732dae3d6ea81f0b7e06d5dedc3f02"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.8"
  sky_engine:
    dependency: transitive
    description: flutter
    source: sdk
    version: "0.0.99"
  source_span:
    dependency: transitive
    description:
      name: source_span
      sha256: "53e943d4206a5e30df338fd4c6e7a077e02254531b138a15aec3bd143c1a8b3c"
      url: "https://pub.dev"
    source: hosted
    version: "1.10.0"
  stack_trace:
    dependency: transitive
    description:
      name: stack_trace
      sha256: "73713990125a6d93122541237550ee3352a2d84baad52d375a4cad2eb9b7ce0b"
      url: "https://pub.dev"
    source: hosted
    version: "1.11.1"
  stream_channel:
    dependency: transitive
    description:
      name: stream_channel
      sha256: ba2aa5d8cc609d96bbb2899c28934f9e1af5cddbd60a827822ea467161eb54e7
      url: "https://pub.dev"
    source: hosted
    version: "2.1.2"
  string_scanner:
    dependency: transitive
    description:
      name: string_scanner
      sha256: "556692adab6cfa87322a115640c11f13cb77b3f076ddcc5d6ae3c20242bedcde"
      url: "https://pub.dev"
    source: hosted
    version: "1.2.0"
  term_glyph:
    dependency: transitive
    description:
      name: term_glyph
      sha256: a29248a84fbb7c79282b40b8c72a1209db169a2e0542bce341da992fe1bc7e84
      url: "https://pub.dev"
    source: hosted
    version: "1.2.1"
  test_api:
    dependency: transitive
    description:
      name: test_api
      sha256: "9955ae474176f7ac8ee4e989dadfb411a58c30415bcfb648fa04b2b8a03afa7f"
      url: "https://pub.dev"
    source: hosted
    version: "0.7.0"
  url_launcher:
    dependency: "direct main"
    description:
      name: url_launcher
      sha256: "6ce1e04375be4eed30548f10a315826fd933c1e493206eab82eed01f438c8d2e"
      url: "https://pub.dev"
    source: hosted
    version: "6.2.6"
  url_launcher_android:
    dependency: transitive
    description:
      name: url_launcher_android
      sha256: "17cd5e205ea615e2c6ea7a77323a11712dffa0720a8a90540db57a01347f9ad9"
      url: "https://pub.dev"
    source: hosted
    version: "6.3.2"
  url_launcher_ios:
    dependency: transitive
    description:
      name: url_launcher_ios
      sha256: "7068716403343f6ba4969b4173cbf3b84fc768042124bc2c011e5d782b24fe89"
      url: "https://pub.dev"
    source: hosted
    version: "6.3.0"
  url_launcher_linux:
    dependency: transitive
    description:
      name: url_launcher_linux
      sha256: ab360eb661f8879369acac07b6bb3ff09d9471155357da8443fd5d3cf7363811
      url: "https://pub.dev"
    source: hosted
    version: "3.1.1"
  url_launcher_macos:
    dependency: transitive
    description:
      name: url_launcher_macos
      sha256: "9a1a42d5d2d95400c795b2914c36fdcb525870c752569438e4ebb09a2b5d90de"
      url: "https://pub.dev"
    source: hosted
    version: "3.2.0"
  url_launcher_platform_interface:
    dependency: transitive
    description:
      name: url_launcher_platform_interface
      sha256: "552f8a1e663569be95a8190206a38187b531910283c3e982193e4f2733f01029"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.2"
  url_launcher_web:
    dependency: transitive
    description:
      name: url_launcher_web
      sha256: "8d9e750d8c9338601e709cd0885f95825086bd8b642547f26bda435aade95d8a"
      url: "https://pub.dev"
    source: hosted
    version: "2.3.1"
  url_launcher_windows:
    dependency: transitive
    description:
      name: url_launcher_windows
      sha256: ecf9725510600aa2bb6d7ddabe16357691b6d2805f66216a97d1b881e21beff7
      url: "https://pub.dev"
    source: hosted
    version: "3.1.1"
  vector_math:
    dependency: transitive
    description:
      name: vector_math
      sha256: "80b3257d1492ce4d091729e3a67a60407d227c27241d6927be0130c98e741803"
      url: "https://pub.dev"
    source: hosted
    version: "2.1.4"
  vm_service:
    dependency: transitive
    description:
      name: vm_service
      sha256: "3923c89304b715fb1eb6423f017651664a03bf5f4b29983627c4da791f74a4ec"
      url: "https://pub.dev"
    source: hosted
    version: "14.2.1"
  web:
    dependency: transitive
    description:
      name: web
      sha256: "97da13628db363c635202ad97068d47c5b8aa555808e7a9411963c533b449b27"
      url: "https://pub.dev"
    source: hosted
    version: "0.5.1"
sdks:
  dart: ">=3.3.4 <4.0.0"
  flutter: ">=3.19.0"

Steps to reproduce

Create new project
Add url_launcher: ^6.2.6 to the pubspec yaml
flutter clean
flutter pub get
flutter build apk

Expected results
√ Built build\app\outputs\flutter-apk\app-release.apk
(No errors)
Actual results
App will still be build, but with following output:
e: C:/Users/<YOUR_USER>/.gradle/caches/transforms-3/a3842a17fe7307c5bcdac869078c73a0/transformed/core-1.10.1/jars/classes.jar!/META-INF/core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: C:/Users/<YOUR_USER>/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.8.22/636bf8b320e7627482771bbac9ed7246773c02bd/kotlin-stdlib-1.8.22.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // TRY THIS: Try running your application with "flutter run". You'll see
        // the application has a purple toolbar. Then, without quitting the app,
        // try changing the seedColor in the colorScheme below to Colors.green
        // and then invoke "hot reload" (save your changes or press the "hot
        // reload" button in a Flutter-supported IDE, or press "r" if you used
        // the command line to start the app).
        //
        // Notice that the counter didn't reset back to zero; the application
        // state is not lost during the reload. To reset the state, use hot
        // restart instead.
        //
        // This works for code too, not just values: Most code changes can be
        // tested with just a hot reload.
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // TRY THIS: Try changing the color here to a specific color (to
        // Colors.amber, perhaps?) and trigger a hot reload to see the AppBar
        // change color while the other colors stay the same.
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          //
          // TRY THIS: Invoke "debug painting" (choose the "Toggle Debug Paint"
          // action in the IDE, or press "p" in the console), to see the
          // wireframe for each widget.
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Screenshots or Videos

Screenshots / Video demonstration

Logs
Logs
e: C:/Users/<YOUR_USER>/.gradle/caches/transforms-3/a3842a17fe7307c5bcdac869078c73a0/transformed/core-1.10.1/jars/classes.jar!/META-INF/core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: C:/Users/<YOUR_USER>/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.8.22/636bf8b320e7627482771bbac9ed7246773c02bd/kotlin-stdlib-1.8.22.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.22.1, on Microsoft Windows [Version 10.0.19045.4412], locale de-DE)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[√] Chrome - develop for the web
[X] Visual Studio - develop Windows apps
    X Visual Studio not installed; this is necessary to develop Windows apps.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 2020.3)
[!] Android Studio (version 2023.2)
    X Unable to determine bundled Java version.
[√] Android Studio (version 2023.3)
[√] Connected device (3 available)
    ! Device emulator-5562 is offline.
[√] Network resources

! Doctor found issues in 3 categories

Vs Code is installed by the way, I dont know why flutter doctor is not picking that up.

This is an issue with incompatible versions of Kotlin and AGP, you can check https://github.com/flutter/flutter/issues/145288#issuecomment-2003275223 to see if it helps or not.

Thanks for the advice, it was indeed fixable by changing
id "com.android.application" version "7.3.0" apply false
from 7.3.0 to 7.4.2 in the settings.gradle

Thanks for confirming that. Closing the issue as solved.


Various new nodes, with a focus on workflow nodes

This adds various new nodes, among them a lot of new workflow-related nodes, fixes to the Output node, two grunges and a filter.

Any chance we could split this into smaller chunks for ease of review?

I've changed my opinions on workflow nodes (among other reasons because of the separation of normal and height maps, and some of the really cursed blending stuff), so I probably should close this. Also, those nodes are probably mostly significantly outdated as well.
I'm working on a bunch of other stuff for MM whenever I have time, but the current state of workflow nodes is at best only usable for stylized game dev stuff, since they make it really hard to make high detail and realistic textures.


transitive Elm dependencies don't get picked up by --watch

I thought this was working, but empirically it's not.

Cannot reproduce with example. Continuing investigation elsewhere...


1++ should be an error

Describe the bug
If parser is set to js, swc would report error but in ts it won't
Input code
1++

Config
No response
Playground link
No response
Expected behavior
Should be error
Actual behavior
No response
Version
1.2.150
Additional context
No response

What does TsConfig > no_early_errors do? It doesn't seems like to be of any use.

It ignores some early errors.
I think it's used by Deno


Update requirements.txt

choose psycopg2==2.9.3

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

Coverage data is based on head (8d5f187) compared to base (bb00229).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #54   +/-   ##
=======================================
  Coverage   96.68%   96.68%
=======================================
  Files           7        7
  Lines         241      241
=======================================
  Hits          233      233
  Misses          8        8

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.


[FR] - Extend cardano-api's makeSignedTransaction to also allow metadata or payload in Byron case

Internal
Describe the feature you'd like
The Byron case in cardano-api's makeSignedTransaction has no provisions for metadata at all.
The transaction generator needs to insert arbitrary bytestring payload into transactions, but doesn't really cares much about specifics.
The way the generator currently does this for in Byron case is: https://github.com/input-output-hk/cardano-benchmarking/blob/master/cardano-tx-generator/src/Cardano/Benchmarking/GeneratorTx/Tx.hs#L183-L225
A specific API is intentionally not requested here -- only a requirement that the Byron case is extended to allow arbitrary bytestring payload.
Describe alternatives you've considered
The design space for the implementation of this requirement is intentionally left open.

Closing this. If this is still relevant please re-open.


Impro

What article on docs.github.com is affected?

What part(s) of the article would you like to see updated?

Additional information

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

This issue is blank and appears have been opened accidentally. I'm going to close it now, but feel free to open a new issue or ask any questions in discussions!


[Bug] Accesible engine selected have less accessibility

Description
The engines are currently focusable  via keyboard as done by pr #52 however the dashed outline does not seem to be a viable one for the focus , making it solid seems a more viable option
current status

Changes made after PR

@Biki-das this issue has not been triage so submitting a PR is against contribution guidelines....

@possumbilities could you give some feedback on this issue?

@possumbilities i have closed the pr sorry for that , but could you give some feedback is it good to work on this one?

@Biki-das as I earlier mentioned, PR #108 aims on making openverse the default search engine. Meaning it'll be made unique from the rest and even if another engine was to be selected it still has to stand out... Somehow this is a duplicate to #108

I think if anything the focus indicators should be set to the browser default wherever possible, and not explicitly set to a style.
Meaning instead of setting the outline to something, it should likely be removed entirely and let the browser style the focus indicator outline with its own inherent defaults.

@Biki-das are you still working on this....
If not I'll love to resolve it @possumbilities

@Biki-das are you still working on this....
If not I'll love to resolve it @possumbilities

Yup working on it

Resolved in new site merge: https://github.com/creativecommons/search/pull/206


Preventing user jumping back a step? with nav bar enabled

Hi,
With the navigation enabled is there any way of preventing user's jumping back to previous steps?

@johnantoni Sorry, I dont follow. Do you mean you want to prevent users jumping back steps from the header steps? i.e. you enable stepsNavigation but only want to make users for 'front' not back?

@newbreedofgeek yep, as in show the navigation steps (1 --- 2 --- 3 --- 4) but not allow them to jump back to previous steps.

that'll do thanks


Make pending avatars show "pending" everywhere

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go offline
Upload an avatar

Expected Result:
I'd expect to see the Pending avatar UI (grayed out avatar) everywhere we show that avatar
Actual Result:
I only see the pending avatar UI in the Profile page
Workaround:
None needed
Platforms:
Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: Latest
Reproducible in staging?: Y
Reproducible in production?: Y
Notes/Photos/Videos:
https://user-images.githubusercontent.com/3885503/210394025-90cab422-2527-49a8-8998-3f460a447aa7.mov
Issue reported by: Me
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0174784941ed533394
Upwork Job ID:<PHONE_NUMBER>361109504
Last Price Increase: 2023-01-03

PR is here, and already merged: https://github.com/Expensify/App/pull/13185
@thesahindia was the C+ there, so assigning him here so we can pay him out
@lschurr this PR is already in production so let's just pay @thesahindia and close this out?

@thesahindia - can you apply for the job in Upwork? https://www.upwork.com/jobs/~01431b0f3e991c82e6

@lschurr applied, thanks!

Paid! I assume this can now be closed. Reopen if I'm wrong.

Groovy thanks @lschurr 👍


XAML code is missing

XAML code is missing in the section "Attached Properties in XAML"
https://docs.microsoft.com/en-us/dotnet/desktop/wpf/advanced/attached-properties-overview?view=netframeworkdesktop-4.8#attached-properties-in-xaml-

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

ID: 7f6a20c9-f639-43ae-04f1-7bf25d45ab77
Version Independent ID: d96932c9-0a8b-aefe-8a0a-ce6a6a8a32b6
Content: Attached Properties Overview - WPF .NET Framework
Content Source: dotnet-desktop-guide/framework/wpf/advanced/attached-properties-overview.md
Product: dotnet-framework
Technology: dotnet-wpf
GitHub Login: @adegeo
Microsoft Alias: adegeo

Thank you for opening this issue. I'll get this fixed up.


Cannot expand the tree from the beginning

Problems summary
I would like to expand items from the beginning, but it doesn't work.
Expected
The tree structure is displayed correctly.
Environment Information

ddu.vim version (SHA1):
426c150ccc038ef76f5f7220d6fd6f066377672c

denops.vim version (SHA1):
3b489d50ba2e034c829a09475a4002176bffbef7

deno version(deno -V output):
deno 1.34.1

OS:
Ubuntu 22.04 (WSL2)

neovim/Vim :version output:
NVIM v0.10.0-dev-0370e4d

Provide a minimal init.vim/vimrc without plugin managers (Required!)
set runtimepath+=/path/to/denops.vim
set runtimepath+=/path/to/ddu.vim
set runtimepath+=/path/to/ddu-ui-ff
set runtimepath+=/path/to/ddu-kind-file

call ddu#custom#patch_global(#{
      \ sources: [#{ name: 'expand' }],
      \ ui: 'ff',
      \ uiParams: #{
      \   ff: #{
      \     displayTree: v:true,
      \   },
      \ },
      \})

augroup my-ddu-ff
  autocmd!
  autocmd FileType ddu-ff call <SID>ddu_ff_mapping()
augroup END

function! s:ddu_ff_mapping() abort
  nnoremap <buffer><silent> <Esc> <Cmd>call ddu#ui#do_action('quit')<CR>
endfunction

And place this source under stdpath('config').

<EMAIL_ADDRESS>
import { BaseSource, Item } from<EMAIL_ADDRESS>import { ActionData } from<EMAIL_ADDRESS>
type Params = Record<never, never>;

export class Source extends BaseSource<Params> {
  kind = "file";

  gather(): ReadableStream<Item<ActionData>[]> {
    return new ReadableStream({
      start(controller) {
        controller.enqueue([
          {
            word: "foo",
            isTree: true,
            treePath: "/foo",
            isExpanded: true,
          },
          {
            word: "bar",
            isTree: false,
            treePath: "/foo/bar",
          },
        ]);
        controller.close();
      },
    });
  }

  params(): Params {
    return {};
  }
}

How to reproduce the problem from neovim/Vim startup (Required!)

call ddu#start({})
You can already see that it's not a tree.

Screenshot (if possible)

Upload the log messages by :redir and :message (if errored)

Fixed.  Please update ddu-ui-ff.

Not fixed.
The bar is not a child of foo.

I have confirmed the correction of the attribute-level. This issue has been resolved.


Backport to 3.1: HIVE-24797: Disable validate default values when parsing Avro schemas #2670

This cherry-picks the commit from #1994 (addressing HIVE-24797).
#2670 is the matching PR for version 3.

@findepi : Sure thing! 😄
Thanks for taking care of this!


invalid yaml?

Trying to apply the example yaml i get
* spec.podTemplateSpec.apiVersion: Required value: must not be empty
* spec.podTemplateSpec.kind: Required value: must not be empty

This was caused by https://github.com/evryfs/github-actions-runner-operator/commit/7d978f3639e49c5dc9a067fb86e668226ee5fc26.
For now you can add:
apiVersion: v1
kind: Pod

until I figure out if this should be like this or not.
Asked for advice in https://kubernetes.slack.com/archives/CAW0GV7A5/p1611319003018100

This was caused by https://github.com/evryfs/github-actions-runner-operator/commit/7d978f3639e49c5dc9a067fb86e668226ee5fc26.
For now you can add:
apiVersion: v1
kind: Pod

until I figure out if this should be like this or not.
Asked for advice in https://kubernetes.slack.com/archives/CAW0GV7A5/p1611319003018100

Maybe @sabre1041 has advice?

Maybe @sabre1041 has advice?

Fixed in latest release. Sorry for the noise.
Be sure to apply the updated CRD to avoid this problem:
kubectl replace -f https://github.com/evryfs/github-actions-runner-operator/blob/v0.8.3/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml

Fixed in latest release. Sorry for the noise.
Be sure to apply the updated CRD to avoid this problem:
kubectl replace -f https://github.com/evryfs/github-actions-runner-operator/blob/v0.8.3/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml

thanks, I installed the 0.8.3 via helm still having the same issue?

thanks, I installed the 0.8.3 via helm still having the same issue?

error: error parsing https://github.com/evryfs/github-actions-runner-operator/blob/v0.8.3/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml: error converting YAML to JSON: yaml: line 88: mapping values are not allowed in this context

error: error parsing https://github.com/evryfs/github-actions-runner-operator/blob/v0.8.3/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml: error converting YAML to JSON: yaml: line 88: mapping values are not allowed in this context

Use the raw url https://raw.githubusercontent.com/evryfs/github-actions-runner-operator/v0.8.3/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml

Use the raw url https://raw.githubusercontent.com/evryfs/github-actions-runner-operator/v0.8.3/config/crd/bases/garo.tietoevry.com_githubactionrunners.yaml

Thanks, i'm using a PAT and have my secret set (using GH_TOKEN var). My runners are failing to launch.
ouput from a pool runner
``Must define RUNNER_TOKEN variable
Has something else changed?
Thanks for the assistance

Thanks, i'm using a PAT and have my secret set (using GH_TOKEN var). My runners are failing to launch.
ouput from a pool runner
``Must define RUNNER_TOKEN variable
Has something else changed?
Thanks for the assistance

got it fixed, thanks

got it fixed, thanks

@jcputter could you please share your fix?


Simulate backtest with existing strategies/param combo to find highest profit?

So say I have a dataset from date range A to B.  I want to backtest this same data set with each built in strategy and parameter configuration and output the parameters that would return the highest profit on the data set over A to B.  Ideally it would test the multiple thousands of combinations and return which configurations return the highest profit on the dataset.  Is it possible to do this? And if so, how?
Thanks.

Gekko is quite basic, however it does provide an API you can script against. I would recommand reading these issues:

#1302
#1095
#997
#1102

GA (genetic algorithms) is most likely the closest to what you describe (you are talking about simply brute forcing parameters). Whatever you want: you need to script this yourself on top of Gekko or use an GA tool available for Gekko (see issues above). Closing this as a dup, since further questions are most likely better answers in these issues :) But feel free to ask questions here nonetheless.


Run path/to/php path/to/composer

Hi,
I read that I could set up php and composer path in the config file :
MY CONFIG FILE
public function configure()
    {
        return $this->getConfigBuilder()
<EMAIL_ADDRESS>            ->deployDir('/kunden/homepages/9/d77835205/htdocs/des-hauts-debats')
            ->repositoryUrl('git@gitlab.com:antoine1003/des-hauts-debats.git')
            ->remotePhpBinaryPath('/usr/bin/php7.1-cli')
            ->remoteComposerBinaryPath('/kunden/homepages/9/d77813505/htdocs/composer.phar')
            ->repositoryBranch('prod')
        ;
    }

But when I run php bin/console deploy it use just /kunden/homepages/9/d77813505/htdocs/composer.phar update for example and I want it to use the full syntax /usr/bin/php7.1-cli kunden/homepages/9/d77813505/htdocs/composer.phar update because the default server php version is outdated and I can't change it (mutualised server).
Is there any way to do it?

I have the same issue.
remotePhpBinaryPath is ignored when run composer. Just composer is called without certain PHP interpreter.
In my opinion, the expected behavior is: php binary path is used for composer as well.
  [Symfony\Component\Process\Exception\ProcessFailedException]
  The command "ssh -A<EMAIL_ADDRESS>'(export APP_ENV=prod; cd /storage/home/srv115367/project/releases/20190417184522 && /storage/home/srv115367/project/composer.phar install --no-dev --prefer-dist
  --no-interaction --quiet)'" failed.

  Exit Code: 2(Misuse of shell builtins)

  Working directory: /var/www/project

  Output:
  ================

  Error Output:
  ================
  Your requirements could not be resolved to an installable set of packages.

You can avoid this by specifying something like:

->remoteComposerBinaryPath('/usr/local/bin/php7.3 /usr/local/bin/composer')

in your DefaultDeployer (deploy.php file):
public function configure()
    {
        return $this->getConfigBuilder()
            ...
            ->remoteComposerBinaryPath('/usr/local/bin/php7.3 /usr/local/bin/composer')
            ->repositoryBranch('prod');
    }

@kordax , probably, yes:)
But we have the method remotePhpBinaryPath which should be responsible to set PHP binary path, otherwise, we do it twice (remotePhpBinaryPath and remoteComposerBinaryPath as in your example)


lang: add type aliases

Summary
Add the TypeDecl declaration to the source language, for introducing
type aliases.
Details

implement the TypeDecl declaration and identifiers in type
expressions
add the Entity type and adjust lookup to be able handle different
kinds of entities (instead of just procedures)

instead of a case object, the separate entity kinds use separate
types and separate sequences
this allows for faster and easier access and a more terse memory
layout

change declToIL to not return anything. Querying the return type
of procedure has to be done separately now
adjust the tester and REPL to the declToIL change
fix source2il crashing for erroneous type expressions in return
type positions

Notes For Reviewers

the Entity-related changes are also a prerequisite for local variables and parameters

An observation regarding the tests: the number prefix naming system for language tests doesn't seem like it'll work out. Grouping by feature seems better, and the dependencies are also not clear (e.g., what language feature does/can a t06_x test actually rely on?).
Of course, it could also be that I'm just holding it wrong and that a feature-centric language testing would actually be worse -- I'm not fully sure.


D_ERROR ChangeHwndIcon (Unable to Access File: nbs.ico)

I downloaded nbs-irc*.zip and extracted to %appdata%\nbs-irc
I created a shortcut to: "C:\Program Files (x86)\mIRC\mirc.exe" -r%appdata%\nbs-irc
I launch the application and get the following error:

To fix this error I ran SysInternals ProcMon and realised that I need to change the Start In directory in the properties of the shortcut from, to:

Now everything is peachy!

Looks more or less like "intended behaviour". I have a look if that can be avoided.


New bucket layout

This fixes https://github.com/Amanieu/thread_local-rs/issues/55

@Amanieu i addressed all your comments.


@conda-forge-admin, please re-render

@conda-forge-admin, please re-render.

@conda-forge-admin, please re-render.

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/libcxx-feedstock#23.

Repurposing this issue to try and figure out why re-rendering this feedstock disables all CI.

Thoughts @conda-forge/core?


Unable to set a variable using SetVariable activty

[Enter feedback here]
Unable to select the dropdown value for Variable Name

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

ID: c5180c2b-1ea6-3924-dc01-3f7c9296774b
Version Independent ID: f040eee7-35fb-676c-ad36-d354af14ecc2
Content: Set Variable Activity in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/control-flow-set-variable-activity.md
Service: data-factory
GitHub Login: @chez-charlie
Microsoft Alias: chez

@vishnurajnr Thanks for the question. Github forum is dedicated for docs related issues. For any technical queries or clarifications, we encourage to utilise Microsoft Q & A platform. Kindly raise your query on Microsoft Q&A Platform

Thanks. I have raised it in the Microsoft Q&A Platform
https://docs.microsoft.com/en-us/answers/questions/438272/azure-data-factory-set-variable-not-working-no-opt.html
I think the documentation can be improved to state the usage of the Set Variable- like if this activity can not be used at the beginning of a pipeline or put some common usage.

variableName	Name of the variable that is set by this activity

Here variable name appears to be a dropdown in the Set Variable action. but nothing mentioned about it in the documentation how this name lookup is populated.


Add stellar cyber partner

Description
Added Stellar Cyber as partner
Issues Resolved
N/A
Check List

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Hello @sjones100 - changes look good. However, you need to fix the DCO on your commit for this to progress forward https://github.com/opensearch-project/project-website/pull/814/checks?check_run_id=6475852461

@krisfreedain apologies, just rebased and fixed, looks like DCO check has passed now

thanks @sjones100 - glad to add you to the partners page! https://opensearch.org/partners/


repo cleanup

The Anchor Platform project currently exists in (at least?) two repos:
https://github.com/stellar/java-stellar-anchor-sdk
https://github.com/stellar/stellar-anchor-platform
initially the project was going to be multiple repos. since then mono-repo java-stellar-anchor-sdk
stellar-anchor-platform  repo still holds some documentation
this work item is to align repos and ensure its not confusing which repo belongs to the anchor platform project.

jake 5 minutes ago
Yea we can move any documentation we want to keep into the public repository.
jake 5 minutes ago
And then we should probably delete the other one.


Unit tests for ds & algo

This is a test issue for the purpose of testing.
https://errors.ai/my-project/A-1234

https://github.com/Zomato/web/pull/67030

https://angular.io/guide/styleguide

https://angular.io/guide/styleguide


object-ui-list - need size options (o-bolt-ui-list--small)

Similar to issue #132, but for ui lists. The default spacing is too large with no options.

Fixed with #147!


feat request: add reading calls msg data and value

It'd be great to know when a mock is called, what was the raw shape of the msg structure.
In our case, we need to check that a payable function was called with the correct amount of funds.

Same here, I'm trying to test a contract that sends assets to another, and depending if the token is ERC20 or native coin I need to check the value to see if it's correct. I didn't find a way to do it :/

Could you guys read the PR I just linked and tell me what you think? Does that solve the issue?

@0xGorilla that looks indeed amazing!
Thanks for solving this :pray:


add -F / --follow options to shp buildrun logs

Changes
Fixes #80
/kind feature
A user can now run commands like
$ shp buildrun create --buildref-name buildpack-nodejs-build foo ; shp buildrun logs -F foo

and tail logs in real time.
Submitter Checklist

[ /] Includes tests if functionality changed/was added
[ /] Includes docs if changes are user-facing
[ /] Set a kind label on this PR
[ /] Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes
Added log following / tailing of active buildruns to 'shp buildrun logs' via the '-F' or '--follow' arguments

self approving
/approve

/assign @otaviof

thanks @otaviof
yeah with that e2e "nuance" I believe you are referring to I could not come up with an "easy" change to address last time this came up and @coreydaley and I agreed to open https://github.com/shipwright-io/cli/issues/57 to track.
I'll see if I can take another crack at that today, and report back here with what if any progress I made.

OK I almost have things working end to end in the e2e's.  Interestingly, some of the log prefixes are different for the buildstrategy when I run locally vs. in CI (I probably have stale strategies locally??)
Gonna tweak and retry

So update on my flurry of activity this weekend.

while make test-e2e works consistently for me locally (on my fedora laptop), it hangs with some regularity on CI
have run into an initial negative with BATS (or at least I have not yet found they way to change this) .... can't get the output from the tests to display in real time, success or failure ... if something hangs, it just sits there until the github actions kills it, but we get no debug data as a consequence.
I temporarily bypassed BATS in my latest run, and with the concurrent k8s 1.20.7 and 1.21.2 runs going in parallel, I finally got some useful debug data
1.20.7 passed; but 1.21.2 hung during the buildah build at [buildah-bud] Copying blob sha256:0b5f424b4861965012dff74550080ba16e033b3a1eaa9b6fa658f035780d3e18
either buildah did in fact complete and we've got some event processing issue in the pod watcher / log following, or buildah hung running in our github action VM / ubuntu ENV.  If I had to guess, it is the latter, but will try to add some debug that runs in parallel.
the whole reason I switched to buildah was because I was attempting the buildpack crankiness per https://github.com/shipwright-io/cli/blob/main/test/e2e/run-follow.bats#L31 that I have been unable to work around in this repo's CI.  Circling back to trying to resolve that might be a work around.  Still not seeing what is different here and in the build rpo.  Or we punt full build success for this PR.

OK verdict in .... kubectl get pods -w & provided what I needed.
This time, v1.12.2 passed and v1.20.7 hung.  Good to know the hang is not k8s dependant.
And sure enough, when buildah hung at [buildah-bud] Copying blob sha256:0b5f424b4861965012dff74550080ba16e033b3a1eaa9b6fa658f035780d3e18 there were no more pod events.
So it is not our pod watcher tail code.  Buildah is hung.
I may tinker with some background threads that also dump disk usage ... see if it is something relatively simple like the filesystem buildah is using for the image build fills up or something.
Short term, if we want this change into v0.7.0, may have to punt on addressing #57

Might also want to think about a separate log following timeout option independing of the request timeout option (that does not have an effect on our watch wrt exiiting it out).

with some quick tips during the community meeting I may have the buildpack log following build in a state where it works correctly in CI
about to submit a separate PR for that .. if that change works, will address #57 there and then rebase this PRs e2e to mimic that, and we'll ditch our foray into running buildah here with its possible memory constraints, intermittent hangs, etc.

Yep got the buildpack working end to end in #83
will start adjusting this PR accordingly

Sigh ... looks like resource constraints, even with buildpacks:
#
# -- output does not contain substring --
# substring (1 lines):
#   [source-default]
# output (5 lines):
#   Pod "obzagenwlmfqfqxb-7ww6w-dkd4v-pod" is in state "Pending"...
#   Pod "obzagenwlmfqfqxb-7ww6w-dkd4v-pod" is in state "Pending"...
#   Pod "obzagenwlmfqfqxb-7ww6w-dkd4v-pod" is in state "Pending"...
#   Pod "obzagenwlmfqfqxb-7ww6w-dkd4v-pod" in "Running" state, starting up log tailPod "obzagenwlmfqfqxb-7ww6w-dkd4v-pod" has failed!
#   ERROR: build pod "obzagenwlmfqfqxb-7ww6w-dkd4v-pod" has failed

OK green e2es ... I believe if I break it up into 2 shell scripts it should keep ... will push that in a moment

ok all green e2e's @adambkaplan @otaviof @coreydaley @SaschaSchwarze0 where the new log following e2e's employ a build which completes successfully in CI and we are able to confirm it
do we want to try and review / iterate on this prior to getting it into v0.7.0, or do you all want me to remove it from the milestone, and we engage with review / iteration after v0.7.0 is cut?
thanks

updates from your comments pushed as a separate commit @SaschaSchwarze0 thanks

ok all e2e's still green after pushing the updates to @SaschaSchwarze0 's comments

I'll squash the sasha-* commits into a single commit name concurrency/misc or some such when we are good to go

all green e2e's

@gabemontero looks fine for me. Can you squash ?

commits squashed @SaschaSchwarze0

all e2e's still  green after squash


Fix check for text property in user message content output

Just a small fix for the profiler output. Without the is defined twig is throwing an exception it cannot access a text property. Which is correct in fact but can be catched.

Thanks @DZunke!


upload-cache-to-github.py: Use upload URL received from GitHub

https://github.com/ruslo/hunter/releases/tag/v0.19.109


More fixes and updates

More pep8 fixes
Add env variables handling
Add some defaults for cli args
Add support for older docker py API

@isimluk thoughts?

Would you be willing to use FALCON_CLIENT_ID, FALCON_CLIENT_SECRET, and FALCON_CLOUD as environment variables?
I am trying to get us towards some consistency, so I always use these 3 names.

Would you be willing to use FALCON_CLIENT_ID, FALCON_CLIENT_SECRET, and FALCON_CLOUD as environment variables?
I am trying to get us towards some consistency, so I always use these 3 names.

Works for me... I just hate typing those in... that's all. :D

Would you be willing to use FALCON_CLIENT_ID, FALCON_CLIENT_SECRET, and FALCON_CLOUD as environment variables?
I am trying to get us towards some consistency, so I always use these 3 names.

Works for me... I just hate typing those in... that's all. :D

Updated the variables. Failing tests can be ignored until we can determine the best fixes for them.

LGTM. 👍 💯

Thanks @isimluk !


improve documentation for "dapr run" standalone

Describe the proposal
I'm testing out the 1. hello worldsample.
I notice that when I run dapr run it auto-creates a 'components' folder and places some files in it. From what I can see, it looks like it defaults to a redis state store and a redis pubsub. I'm assuming these are "builtin defaults" since I can't find any config files telling dapr to set itself up that way.
I tried editing one of those files to be using NATS instead of redis, and I could, as long as the name of the file remains redis_messagebus.yaml. this struck me as weird. (like, what decides the name of that file? Or even that it should default to redis if it doesn't exist?)
Needless to say, I'm having a hard time understanding how this pieces together. It would be really good to have robust documentation explaining in detail what happens when dapr run is executed, what the defaults are, what files dapr looks for, and how to control the behavior of it (I see there's a dapr run --config flag, but I can't find any information about the type of config this pertains to)
Sorry about all the doc issues I'm posting. Dapr looks really promising, I'm just having a hard time figuring out stuff whenever I stray a little bit from the "hello world" exxamples.

Don't be sorry, docs are what make or break a project.
I'll respond later about the question at hand, and we'll issue more docs about dapr run.

Totally agree... I started my journey with actors as I'm familiar with Service fabric. I'm not familiar with redis, node, javascript, go, rust, Linux, python, or whatever else is in the startup examples.  I get it that you want a open environment, but from a sample perspective very few understand that scope of tech.

For me its not a problem that its using redis and python etc, those are the tools I work with every day. But I need to understand how dapr behaves when dapr run is executed, and how I can adjust the default functionality.

I tried editing one of those files to be using NATS instead of redis, and I could, as long as the name of the file remains redis_messagebus.yaml. this struck me as weird. (like, what decides the name of that file? Or even that it should default to redis if it doesn't exist?)

Yes, today in standalone (local) mode, the dapr CLI reads in component configurations from
[dir you're running the CLI from]\components
If \components is not present, it creates it and creates 2 default yamls:

a state store component (redis - redis.yaml)
a pubsub component (again redis - redis_messagebus.yaml).

The names of the files in \components are not inspected, only the contents of the files.  So, as you described, if you simply overwrite the contents of redis_messagebus.yaml with that of a different type of pubsub (e.g. NATS), but keep the file name, it will use NATs instead of Redis.
If these files are already present, they are not overwritten on a dapr run.  If any are not present, then the missing ones are recreated.
See https://github.com/dapr/cli/blob/eeea3d5a1b9042974731294c5d10d4829706f01b/pkg/standalone/run.go#L273 for the beginning of where the code described above begins.

I've assigned this to myself to add some docs on what happens on a dapr run.

If these files are already present, they are not overwritten on a dapr run. If any are not present, then the missing ones are recreated.

@LMWF this was bizzarre behaviour for me - when I was working on the Azure Service Bus PubSub provider - if I had redis.yaml and a servicebus_messagebus.yaml and ran darp run ... it would automatically create the missing redis_messagebus.yaml and load it as a message bus even when I don't want or need it. This also seems to conflict with the "use what you want" principle of dapr - if dapr run requires atleast a redis connection and will automatically configure a state store and a message bus, we are not giving a path to iteratively adopt features i.e. service invocation only.

this was bizzarre behaviour for me
I completely agree. It would be much less confusing if the filenames were more generic. The fact that I have to have a file called "something something redis" even if I use some other pubsub technology is just.... bizarre.

We've created a doc describing what happens on a dapr run for a local cluster.  Please let us know if this helps or what can be clarified:
https://github.com/dapr/docs/blob/master/walkthroughs/darprun.md

looks good!!

@trondhindenes I am closing this one, please feel free to reopen if still have questions


Use GPS as time source

Added chrony to the edgefarm image.
Added option -n to the gpsd options that it polls the gps without a client is connected with it.
Specified new reference clock for GPS in chrony.conf and prefer it as time source

created new branch to fix history


Ml/tmp/investigate kdsl issues

Fixes #25686.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


UI Redesign - Mobile - Terms & Conditions

Description
The task is to implement the new design for the screens displayed on the Terms & Conditions navigation in the mobile app.
Assets and Design Screens
All assets and design screens have already been created.

The Figma TERMS & CONDITIONS design can be found here under SETTINGS https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=2%3A3
The Assets required can be found here https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=0%3A1

For help with using Figma please watch this short tutorial video
https://user-images.githubusercontent.com/69275762/192322842-2ac40f88-c396-4a66-933b-3c8abae516c3.mov
Additional context

This work should be done on the UI_Redesign branch https://github.com/atsign-foundation/atmosphere_pro/tree/ui_redesign

@ksanty I would like to work on this UI

I would love to redesign settings UI

@ksanty I would like to work on this UI

Great.  Thanks so much.  Let us know if you have questions.

I would love to redesign settings UI

Hi there, the screens posted are already redesigned and ready for implementation.  What enhancements are you proposing?  Thank you!

@ksanty  in the sigma design I can see that only one screen it there the page when we navigate to using T&C button is not present. can you help me with this

@tanmoy27112000 that's correct.  All the assets are under the Design Systems link as stated above - https://www.figma.com/file/gnhrfcg8OYvAz0zJXZz2r3/Atmosphere-Pro?node-id=0%3A1

Can you assign this to me @tinashe404? Seems there is only a person working on this... thank you


MyfirstGIT

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

@szlyh what is your problem?


Add rust no_std + alloc support

Just noticed that the Rust version used in your CI setup predates alloc stabilization. Do you make any minimum supported Rust version guarantees or is it OK if I just bump it?

This will require Rust version 1.36? I am not very familiar with the Rust ecosystem but that is probably okay to change. You will need to change the version in .travis.yml and in the readme to that.

The error message from 3a6759b043f3011ea242dfb0352644952d450b1b (https://travis-ci.org/github/anyascii/anyascii/jobs/716090140) can be ignored.
https://github.com/rust-lang/rust/issues/54010
It doesn't cause the build to fail and doesn't stop any tests from running.


Update README.md

updated readme

A single word change is usually not enough to justify a pull request.
In this case, I don't think this contribution is a benefit; it's not correct English How-To-do examples is not accepted English. The existing is ok.

Agreed with @KastanDay !


Figure out why we need JSON processing. And remove it if it's unnecessary.

I've also seen a part of it in the js-processor

ref #5

B237743. Vestiges of the past.

What about https://github.com/superroma/testcafe-hammerhead/blob/master/src/processing/js/index.js#L130 ?

I'm working on it

jsProcessor was removed from the client API. hammerhead.navigateTo(url) was introduced.


error Cannot read properties of undefined (reading 'stdin')

After upgrading to nodist 0.10.3 and switching to node 18.19.0 with the following commands, I am unable to execute "npm start".
nodist use 18.19.0
nodist npm match

I get the error
PS C:\src\Angular\REDACTED> npm start

><EMAIL_ADDRESS>start
> ng serve --host REDACTED.com --port 4200 --disable-host-check

npm ERR! Cannot read properties of undefined (reading 'stdin')

npm ERR! A complete log of this run can be found in: C:\Users\REDACTED\AppData\Local\npm-cache\_logs\2023-12-18T20_45_49_353Z-debug-0.log
PS C:\src\Angular\REDACTED>

Here is the log:
0 verbose cli C:\Program Files (x86)\Nodist\v-x64\18.19.0\node.exe C:\Program Files (x86)\Nodist\npmv\10.2.3\bin\npm-cli.js
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 timing npm:load:whichnode Completed in 69ms
4 timing config:load:defaults Completed in 4ms
5 timing config:load:file:C:\Program Files (x86)\Nodist\npmv\10.2.3\npmrc Completed in 9ms
6 timing config:load:builtin Completed in 9ms
7 timing config:load:cli Completed in 3ms
8 timing config:load:env Completed in 2ms
9 timing config:load:file:C:\src\Angular\REDACTED\.npmrc Completed in 0ms
10 timing config:load:project Completed in 2ms
11 timing config:load:file:C:\Users\REDACTED\.npmrc Completed in 15ms
12 timing config:load:user Completed in 15ms
13 timing config:load:file:C:\Program Files (x86)\Nodist\bin\etc\npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:setEnvs Completed in 2ms
16 timing config:load Completed in 38ms
17 timing npm:load:configload Completed in 39ms
18 timing config:load:flatten Completed in 6ms
19 timing npm:load:mkdirpcache Completed in 25ms
20 timing npm:load:mkdirplogs Completed in 28ms
21 verbose title npm start
22 verbose argv "start"
23 timing npm:load:setTitle Completed in 17ms
24 timing npm:load:display Completed in 1ms
25 verbose logfile logs-max:10 dir:C:\Users\REDACTED\AppData\Local\npm-cache\_logs\2023-12-18T20_39_56_015Z-
26 verbose logfile C:\Users\REDACTED\AppData\Local\npm-cache\_logs\2023-12-18T20_39_56_015Z-debug-0.log
27 timing npm:load:logFile Completed in 19ms
28 timing npm:load:timers Completed in 0ms
29 timing npm:load:configScope Completed in 0ms
30 timing npm:load Completed in 521ms
31 silly logfile start cleaning logs, removing 1 files
32 timing command:run-script Completed in 101ms
33 timing command:start Completed in 121ms
34 verbose stack TypeError: Cannot read properties of undefined (reading 'stdin')
34 verbose stack     at promiseSpawn (C:\Program Files (x86)\Nodist\npmv\10.2.3\node_modules\@npmcli\promise-spawn\lib\index.js:60:18)
34 verbose stack     at spawnWithShell (C:\Program Files (x86)\Nodist\npmv\10.2.3\node_modules\@npmcli\promise-spawn\lib\index.js:123:10)
34 verbose stack     at promiseSpawn (C:\Program Files (x86)\Nodist\npmv\10.2.3\node_modules\@npmcli\promise-spawn\lib\index.js:12:12)
34 verbose stack     at runScriptPkg (C:\Program Files (x86)\Nodist\npmv\10.2.3\node_modules\@npmcli\run-script\lib\run-script-pkg.js:79:13)
34 verbose stack     at runScript (C:\Program Files (x86)\Nodist\npmv\10.2.3\node_modules\@npmcli\run-script\lib\run-script.js:9:16)
34 verbose stack     at RunScript.run (C:\Program Files (x86)\Nodist\npmv\10.2.3\lib\commands\run-script.js:121:13)
34 verbose stack     at async module.exports (C:\Program Files (x86)\Nodist\npmv\10.2.3\lib\cli-entry.js:61:5)
35 verbose cwd C:\src\Angular\REDACTED
36 verbose Windows_NT 10.0.14393
37 verbose node v18.19.0
38 verbose npm  v10.2.3
39 error Cannot read properties of undefined (reading 'stdin')
40 verbose exit 1
41 timing npm Completed in 1202ms
42 verbose code 1
43 error A complete log of this run can be found in: C:\Users\REDACTED\AppData\Local\npm-cache\_logs\2023-12-18T20_39_56_015Z-debug-0.log

There is not an .npmrc in either the application or in the user's home directory.

I tried to reproduce the problem, after a clean installation of Nodist and using the commands you have provided I have no problems.
As sample project I used https://github.com/gothinkster/angular-realworld-example-app.
It is working using PowerShell, normal Cmd and Git Bash (where I used nodist local 18.19.0 to select the node version).
Has this worked with older versions of Nodist for the same project?


register execution time better

For now we capture in Zafira only test execution time. At the same time we don't track correctly execution/queue time. As result I can't say exactly how much time we were waiting in queue, how much time was spend on building/compilation etc phases.
Such information should be calculated automatically

Very specific functionality, not sure it is interesting info.


Outdated "Feedback" tool screenshot in CONTRIBUTING.md

Hi, SQL Server doco folks,
In your CONTRIBUTING.md guide, in the ["Reporting Bugs and Suggesting Enhancements" section](Reporting Bugs and Suggesting Enhancements), it shows this for me:

I think the Microsoft SQL Server docs web site has changed, and this is out of date. When I go there (today in Google Chrome on macOS), the Feedback section looks like this for me:

That seems like a substantial difference. Maybe the Contributing guide should be updated?

@apjanke -- Andrew, thank you for your close reading.  I am updating the article.


Decide what to do about the scipy dependency

Status quo is that asking for correlation p-value will attempt to import scipy, which is not declared as a dependency.  We should either

declare a dependency on scipy, or
make the error message nicer

This does not affect the probcomp stack overmuch, because other stack packages depend on scipy (Venturecxx, iventure via seaborn, and cgpm)

Declared dependency.