Add SOCKS proxy support

This work enables Artemis connectors to use a SOCKS proxy, by adding an appropriate netty socks handler to the channel pipeline. The proxy is only enabled for a public remote host.
I tested that it works correctly.
If this is acceptable functionality to be included in Artemis I'm happy to do some more polishing to get it in the right shape.

nice feature!!!
= it needs a test.. (especially one that uses the URI for the connector)
and... how to test this.. any proxy support in Java we can deploy?

Also needs a JIRA and there are a handful of checkstyle violations.

Please open a JIRA for this, squash all of your commits, and amend your commit message to follow what's outlined in the Hacking Guide.

Will do 👍

you could squash all your committs into a single one here:
git rebase -i HEAD~2
squash them, change the tittle
git push origi -f

this is ready for another look @clebertsuconic

I was trying to make a test like this:
https://github.com/clebertsuconic/activemq-artemis/commit/2f7cbc960cc6db4c495425878c9855c84a4c8939
but I'm not sure I will have to time to finish it... if you want to take over this test?

can do, so the point of this test is just to check that NettyConnector can establish a connection when the proxy handler is enabled, right?

Yes, basically I wanted to start a proxy, and make sure it worked through the proxy.
I was looking to assert the proxy was used.. but I didn't have time to finish the test...

@adagys we still need a way to test it though.. I looked at their website and it seems to support SOCKS.. but I didn't figure out how.
I think we should remove the option you added to ignore localhost though. If it's proxy, always proxy...

@clebertsuconic  @adagys This has been open since May.  What needs to happen before we can merge/close?

Test

I couldn't get it to work in the end and don't have time to work on it anymore.., can be closed

@adagys did you at least try the feature alone? was it working? I couldn't get it to work.
I was interested on the feature.. but I couldn't get the test to work.

Yep, I remember seeing it work in an end-to-end scenario, but couldn't get the test to work either.. Which is strange

Can you do one last rebase 👍
(git pull --rebase upstream master)
... resolve conflicts
git push origin -f
and I will work on the tests soon. (kind of last week)

Rebased 👍

@clebertsuconic I'm merging this.

just needs sorting dependencies, seems the project removed netty all here, so just having to add
     <dependency>
        <groupId>io.netty</groupId>
        <artifactId>netty-handler-proxy</artifactId>
        <version>${netty.version}</version>
        <!-- License: Apache 2.0 -->
     </dependency>
     <dependency>
        <groupId>io.netty</groupId>
        <artifactId>netty-codec-socks</artifactId>
        <version>${netty.version}</version>
        <!-- License: Apache 2.0 -->
     </dependency>

@michaelandrepearce, org.apache.activemq.artemis.tests.unit.core.remoting.impl.netty.NettyConnectorTest#testSocksProxyHandlerAdded is failing consistently. This may need to be reverted.

@michaelandrepearce, I think I've got a fix for this. Will send a PR shortly...

Just sent #3010.

    Map<String, Object> params = new HashMap<>();
    params.put(TransportConstants.HOST_PROP_NAME, "localhost");
    params.put(TransportConstants.PORT_PROP_NAME, "61617"); //<acceptor name="netty">tcp://<IP_ADDRESS>:61617</acceptor>
    params.put(TransportConstants.PROXY_ENABLED_PROP_NAME, "true");
    params.put(TransportConstants.PROXY_HOST_PROP_NAME, "localhost");
    params.put(TransportConstants.PROXY_PORT_PROP_NAME, "1080");
    params.put(TransportConstants.PROXY_USERNAME_PROP_NAME, "user");
    params.put(TransportConstants.PROXY_PASSWORD_PROP_NAME, "WRONG_PASSWORD");

    TransportConfiguration transportConfiguration = new TransportConfiguration("org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory", params);
    ActiveMQConnectionFactory activeMQConnectionFactory = ActiveMQJMSClient.createConnectionFactoryWithoutHA(JMSFactoryType.CF, transportConfiguration);

<dependency>
	<groupId>org.apache.activemq</groupId>
	<artifactId>artemis-jms-client</artifactId>
	<version>2.14.0</version>
</dependency>

This is ignoring the proxy conf.
Am I doing something wrong?

@celiovasconcelos, this is an old, closed pull request. It's not really meant for support. Try using the ActiveMQ User Mailing List.

Sorry.
I've posted it in https://stackoverflow.com/questions/63248592/amq-artemis-socks-proxy-support
Thank you.


[SPARK-15271] [MESOS] Allow force pulling executor docker images

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)
Mesos agents by default will not pull docker images which are cached
locally already. In order to run Spark executors from mutable tags like
:latest this commit introduces a Spark setting
(spark.mesos.executor.docker.forcePullImage). Setting this flag to
true will tell the Mesos agent to force pull the docker image (default is false which is consistent with the previous
implementation and Mesos' default
behaviour).

Can one of the admins verify this patch?

Jenkins add to whitelist

Jenkins test this please

Test build #62882 has started for PR 14348 at commit fd03d40.

Test build #62882 has finished for PR 14348 at commit fd03d40.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62882/
Test FAILed.

Jenkins retest this please

Test build #62887 has started for PR 14348 at commit fd03d40.

Test build #62887 has finished for PR 14348 at commit fd03d40.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62887/
Test PASSed.

LGTM. This addresses the compilation error observed in the last PR. Let's try merging to master again.


Image in bootstrap modal does not load

Hi,
Really great plugin !
It works well in a container inside my main section.
But I'm experiencing a weird issue with bootstrap modal :
For example this is the modal :

In fact, nothing happens (i.e image source is still the same) when I launch the modal (via a button).
I've tried to call revalidate() on click but still no result ..
Thank you for your answer.
Jim

hey @JimJames23
Do you have a live example?
Otherwise you can force the image to load on click by calling the public load() function.

Closing due to inactivity

I had a similar issue and found that I had to add the following javascript to activate Blazy on bootstrap modal popup:
$('#modal_id_here').on('shown.bs.modal', function (e) {
  var bLazy = new Blazy();
})

where you replace modal_id_here with the id of your modal div.


MenuButton "switch_on_hover" no longer works now that Popups are windows.

Godot version:
4.0 master 0167bfa
OS/device including version:
Win 10
Issue description:
In the editor, open the File menu, then hover over Project, Debug, etc menus and notice that they do not switch automatically.
If you try this on 3.2.3 then the behaviour is correct and there is automatic switching (since they all have switch_on_hover = true).
Pretty sure this is because Popups are Windows now, so when they have focus their parent no longer gets mouse signals.

Cannot reproduce in the editor v4.0.beta.custom_build [871ddf80c]


Update Firebase Functions 2nd gen to Node 20

https://firebase.google.com/docs/functions/manage-functions?gen=2nd#set_runtime_options
Also considering migrating all Functions to 2nd gen

Remaining all on Node 18 to prevent EBADENGINE while Node 20 not supported (preview only) on Functions 1st gen


Invalid SignedRequest host header derived for Region::Custom

While building new serverless template for a rusoto based aws lambda websocket application I discovered a bug in the way SignedRequest parses ( or doesn't parse ) the endpoint provided via Region::Custom
As a quick refresher, the endpoint you passed for apigateway endpoints in includes a /{stage} path
https://docs.aws.amazon.com/cli/latest/reference/apigatewaymanagementapi/index.html
The relevant code I'm working on can be find here
I was able to confirm the bug but enabling trace-level logging in the relevant logging RUST_LOG: 'rusoto_core=trace'
and observe the following in my logs
02:50:30
[2019-03-20T02:50:30Z DEBUG rusoto_core::request] content-length:"4"

02:50:30
[2019-03-20T02:50:30Z DEBUG rusoto_core::request] content-type:"application/x-amz-json-1.1"
02:50:30
[2019-03-20T02:50:30Z DEBUG rusoto_core::request] host:"xxx.execute-api.us-east-1.amazonaws.com/dev"

^^ note the /dev in the host header
the current behavior results in a 400 response from aws ( interestingly aws returns an http page )
\r\n<title>400 Bad Request</title>\r\n\r\n
400 Bad Request
\r\n\r\n\r\n

I was able to validate that request with the correct host header ( sans /{stage} ) with another tool.
I'll be sending a patch soon but Im wondering how long It'll be for a patch release before I can see this in a release. I was hoping to demo this at work after adding the support for apigatewaymanagementapi in the last rusoto release but am now blocked. If I could get a patch in soon to add the small change needed to set derive a valid host header, could we do a patch release on rusoto_core 0.37.1 perhaps sooner than the typical release schedule for all crates?

I just saw that the the error refactor in https://github.com/rusoto/rusoto/pull/1313 was merged so its unlikely for a release. I'm working around the issue with a source dependency but ideally I'd like to depend on a release.
Do we have a sense for when we might see something like an 1.38 release?

Unless we get someone stepping up to help with releasing, it'll probably be two to three weeks out for the next release.

I'd be happy to help with that!

Thanks for the offer! There's a couple ways that you (and others!) could help. Two scenarios:
Ideally:
• knock out all issues labeled with 0.38
• have someone else do the releasing including integration tests, rusoto.org changes such as migrations needed
More likely:
• pick up ready to go PRs - https://github.com/rusoto/rusoto/pull/1311 after rebasing?
• have someone else do the releasing including integration tests, rusoto.org changes such as migrations needed
Impediment: while we have seven people with the commit bit, Rusoto is one of many things they do. Perhaps it's time for another call for maintainers!


[Feature Request] Texture dumping/injection

This would solve a lot of problems at the same time:

Lack of Xbox/whatever controller prompts
Stretched HUD/UI elements
Low resolution UI

As a bonust, it would also make it possible to mod the environmental textures for higher quality ones.
@emoose gave this feature a go at #7, said it lacked UI dumping capability and a cache for reducing/eliminating stutters.

Got a little further with UI, seems they just use a slightly different D3DXCreateTextureFromFileInMemory function to load in (as opposed to the D3DXCreateTextureFromFileInMemoryEx that I was modifying before)
Sadly seems UI textures are usually stored in a single texture file all next to each other as a large texture atlas, eg:

Once upscaled the game doesn't seem to have anything to handle texture resolution being different, and just tries loading the texture from whatever original position it was at before, making everything look pretty broken:

Hoping maybe the game keeps the X/Y/width/height of each texture in the atlas somewhere next to the texture itself, could probably just add some code to rescale those based on originalWidthHeight / newWidthHeight, haven't had any luck with it yet though :/

Do you have a test build with dumping/injecting capabilities so I can test?
Hope you can sove the UI scaling issue.

Aha mostly have the texture atlas stuff figured out now:

Seems game used both ways of addressing individual textures, the texture file had x/y/width/height for each sprite inside, but code could also override those (and usually did...)
There's also some alternate way which uses a matrix transform instead of x/y/width/height which I didn't really understand that well, but was able to get something working for it eventually.
Only issue I've noticed so far is pause menu textures break if they're upscaled, seems they do some weird thing with the x/y stuff to stretch those textures out which breaks it, not really sure why yet, haven't noticed anything else broken yet.
Code is still pretty messy for this, but should be fine to test out:
Outrun2006Tweaks-0.2.5-uiTextureReplace.zip
With that DLL it'll write out UI textures into [game folder]\textures\dump[texture-package-name]\ folder as they load in, and loads in any replacements from [game folder]\textures\load\ if they exist.
(UI textures only atm since we don't really need to worry about caching for those.. hopefully can get something working for stage textures soon)
Subfolders in \load\ should work if they match the original texture-package-name that was written into dump (eg. texture that was dumped to dump\spr_sprani_game_cvt_Exst\C4A2937B_1024x1024.dds can load in from either load\C4A2937B_1024x1024.dds or load\spr_sprani_game_cvt_Exst\C4A2937B_1024x1024.dds)
With AutoCrispy you can point it to the dump & load folders and it can upscale textures for you automatically as they dump in, pretty neat, not really sure what the best model to use is though, the one I tried turned some of the O2SP textures into soup:

Cleaned up code a little bit, found a slightly better way to handle looking up scaling amount, and seems that fixed the issue with pause menu textures 😸
New build here (includes 4GB patched exe):
Outrun2006Tweaks-0.2.5-uiTextureReplace-v2.zip

Great, man, you rock!
I have some experience with ESRGAN, I'm gonna give it a try and compare with your results. Thanks!

Oh, that makes sense, I thought it was supposed to dump envirental textures too

The stutter isn't really as bad as I thought, but with uncompressed textures it can dip a lot when going through loading zones,  though recompressing to DXT5 (about 1/5th the size) does seem to help it a bit.
I've only really tried it with SSD, imagine with HDD it would probably be even worse :/
Here's a build which can dump/replace them, INI has some options added about whether to enable replacing/dumping:
Outrun2006Tweaks-0.2.5-allTextureReplace.zip

Which model did you use with autocrispy?
Is it possible to implement a way to toggle between vanilla textures and inject ones on the fly during gameplay?

IIRC it was https://openmodeldb.info/models/4x-HDCube3 & the ESRGAN from https://github.com/WalkerMx/ESRGAN_Python_Embedded/releases/tag/v1.4
If you extract that esrgan into esrgan folder next to autocrispy, and put the HDCube model into esrgan\models, they should show up in the selectors
You might need to download texconv from https://github.com/Microsoft/DirectXTex/releases/latest/download/texconv.exe and put that next to autocrispy.exe too
Folder layout for me was
\autocrispy.exe
\texconv.exe
\esrgan\esrgan.exe
\esrgan\models\4xHDcube3_500k.pth

After that you can go to autocrispy chaining menu, then pick TexConv from dropdown and change it to DDS input, press Add button, then pick ESRGAN and choose the model, Add, then pick TexConv again and set it to DDS Output with Force Dx9 checked & Add
This portable.xml might work too if you extract it next to autocrispy.exe (might need to edit the paths inside it though):
portable.zip
If new textures are added into load during gameplay they should get loaded in whenever game tries to load the texture next, no need to restart.
A toggle between the old & new would be neat, game does have some stuff that re-loads textures when D3D device loss happens, maybe could be repurposed somehow...

I saw you created minimaps for the UI textures, even though the original ones don't have, since it doesn't make sense. Maybe you could save some size by removing them.
Good model, I didn't know it.
About DXT5 compression, if I remember correctly, DXT1 is better for textures with no alpha channel while DXT5 is better for textures with alpha channel. Did you try both algorithms?

Ah looks like texconv defaults to all mipmaps, -m 1 parameter should remove them, maybe can help reduce load time for the UI.
DXT1 seems supported by game, think I saw some textures were using DXT3 as well, haven't really done much texture work before though so not sure how to know which is best, looks like alpha does get used in a lot of textures though.
Had a look into adding caching too, tried copying how game does it by having a separate loading thread and making game skip drawing model till texture was done, but even that still gave stutter with uncompressed stage textures :/
Not sure if much could be done for those, will try checking HDD soon to see if this caching is even helping at all.

Well, I'm going to close this one, thank you for all the hard work =)
The only thing missing is a better caching system, but the main work is done.


cell expended in Interative window by default

Environment data
version 1.63.0 (user setup)
: 7db1a2b88f7557e0a43fec75b6ba7e50b3e9f77e
date: 2021-12-07T06:26:56.179Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19042
Expected behaviour
cell will be collapsed in interactive window when running in jupyter+vscode intervative mode
Actual behaviour
automatically expended, and there is no setting to set it to collapse by default
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

XXX

Logs

Output for Jupyter in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Jupyter)

XXX

Duplicate of https://github.com/microsoft/vscode-jupyter/issues/8203


I created a YouTube video tutorial about Almond and Home Assistant

Hello,
I just published a YouTube tutorial about it and Home Assistant.
This is my video - https://youtu.be/vmNp2RTGY6Q
If you think that the video is helpful you can put the link somewhere.
Either way, keep up the great work :)

Thank you again for the video, I'm closing this issue as there is nothing left to do.


Added code to translate text-to-morse

prefer using 'let' instead of var, it prevents hoisting and redeclaration

prefer using 'let' instead of var, it prevents hoisting and redeclaration

Yeah, will make lot of changes. This was just an initial commit.


Allow dynamically starting strategies + expand GenServer-ness of the DefaultStrategyTemplate

Expaneded the GenServer-ness of the DefaultStrategyTemplate
Changed some of the behavior callback arity
Created DynamicSupervisor and Registry to be used
Added tests to show examples of doing dynamically generating strategies.

I am reviewing this at the velocity of a turtle... but I am looking into it. Sorry for the long delays here!

@lovebes I was reviewing and testing this but I got the conclusion we need some bigger changes here...
For instance, issue #37 . We need to be more compliant with the specification about possible kidless and duplicated kids in a set.
So, I am gathering feedback to a breaking change which would allow us to change the strategies here. Maybe we should rename the current strategy to something like SingleSourceStrategy and then have a MultipleSourcesStrategy that would chain many single sources and then a new DynamicSourcesStrategy. I see the use case for all of them in the wild and would allow us to assume intent behind choosing each of them.
Other than that, an issue with synchronous initialization was caught that simply showed that we are not properly initializing the ETS here. This is some ancient code that I want to refactor properly too and not maintain it like it is now forever.
So, I've pushed a change with the CI exactly like it is currently in Joken and some logging improvements. This broke your PR here but I wanted to tell you that your help will be much appreciated when we start tackling 2.0. Your code here is an eye opener for these different strategies. So, first of all, thanks a lot :) Secondly, let's discuss better what other issues and uses we might want with a breaking change.
Wdyt?

@victorolinasc I like all of your decisions, and yeah having read #37 I see what you mean. I am all for a 2.0 for this very important library. I don't think there's anything like it in the Elixir ecosphere that does Joken and JWKS simply and would like for it to have more support. I like how you want to keep the current strategy as-is, as that was my original intention but wanted to keep the footprint small and not introduce more files ;)
So yeah please ping me when you see I might be of use for 2.0, etc - thank you for this library! Feel free to close this PR, leave it open, whichever you prefer!


add sessionheader, extending the handshake protocol

This PR adds the concept of a sessionheader, extending the handshake protocol:

connecting peers are now ensured to share the same genesis blockID;
connecting peers are now ensured not to connect to itself;
pinging between newer clients is no longer a hack;

It does this by having a new connectSessionHandshake that comes right after the connectVersionHandshake, which exchanges the genesisID, gatewayID and if the peer wants to connect (eg this is false when the peer was just pinging).
This is a pretty invasive feature, but should be fully backwards compatible. Well that's the goal at least. Would love feedback on this, and make this a thing into master, together, if possible.
Review Request: @DavidVorick @lukechampine

I ran the test that Travis failed on, and it seems to work here. I think this is one of those cases where muxado acts up, am I right?

Ah yes, I was working from a forked directory at first, but then it kinda broke everything, and I guess it only really works for go libraries with no inter-dependencies. I did exactly what you did, but never realized that those wrong repo links were in there, as my IDE adds them for me. Sorry for that.

Yeah, Travis sometimes fails due to non-deterministic errors, mostly because it runs so slowly that our timeouts get triggered. If that happens, just drop a comment and I will restart the build until it passes.

Ok, and thanks for the review. Will just on it in a minute. When I'm done with my smux branch, would that help the reproducibility a lot, or are there other things causing issues like this?

@lukechampine changed the stuff you requested.
Ran make test && make test-long with success.

Added your requested changes, and bumped version in a separate commit.

Instead of bumping the version number in this PR, you could alter the tests like so:
func TestHandshake(t *testing.T) {
    if build.VersionCmp(build.Version, sessionHandshakeVersion) < 0 {
        t.Skipf("Test requires build.Version >= %v", sessionHandshakeVersion)
    }
}

we usually don't bump the version number until just prior to the release.

I was too hasty re: v1.2.0. We are already pushing out enough major changes in v1.2.0, so the new gateway protocol will be postponed until the release after that, probably v1.2.1.

I mentioned earlier, but this PR touches super critical parts of the code. The QA that we need to do to be certain that nothing breaks and compatibility is preserved is a lot, the bar is really high for touching the gateway.
We have to make sure that it's done correctly before we merge it, and that's going to take time even if there are no bugs.

@DavidVorick how would these QA tests take place?

https://github.com/NebulousLabs/Sia-Ant-Farm
We'll spin up an ant-farm that has 2-3 nodes of v1.1.2, 2-3 nodes of v1.2.0, and 2-3 nodes of [gateway upgrades]. We'll give each of the nodes different jobs, making sure that there's at least 1 renter or host in each batch. Then we'll watch them perform for a few hours and make sure everyone is able to talk to eachother.
We'll repeat without the v1.2.0 nodes, and then again but this time without the v1.1.2 nodes.
Finally, we'll take some of the gateway code and upgrade our servers, and see if they are able to collaborate the network without issues.
Right now our plate is full dealing with bugfixes and stuff in v1.2.0, so the gateway QA is going to have to wait until v1.2.0 is more stable. If you want to start messing around with the antfarm, we can help you get it running in slack. Probably the best channel would be #app-dev, as I believe there are several people in that channel who would be interested in following along. (the ant farm is a great way to test Sia apps as well as Sia itself).

Overall, looks pretty good. I wonder if there's some way we can write an integration test within the package (not needing the antfarm) to demonstrate compatibility between the versions. Only things I can think of right now though either require siad binaries, or some ugly bash scripts that will checkout our release tags and build multiple binaries on the fly.
But that's not necessarily sufficient anyway, because old versions will also be running different dependencies and were compiled with different compilers (namely, older compiler versions). The only real authentic way to do it would be to use our actual release binaries.

seems like this is in pretty good shape (just needs some formatting tweaks), but needs more real-world testing. I would like to see:

Nodes running the new code connecting to old nodes on the mainnet
Nodes running the new code connecting to each other on the mainnet
A mixture of old/new nodes interacting in antfarm tests

I hope to run these tests myself over the next few days, but it would be nice if @GlenDC could independently confirm that this code works on the mainnet.
Higher-level: to minimize the amount of compatibility code, we probably want to merge this and the smux change into the same release. To that end, we should merge both into a feature branch, and then merge the feature branch into a future release. Unfortunately I carelessly deleted the staging branch, so @GlenDC will have to reopen the smux PR. I suggest gateway-proto as the name of the feature branch.

@lukechampine I guess you mean that you guys want to merge this into a new branch called gateway-proto, rather than master? I'll re-open the smux PR, no problem :)

@GlenDC: please fixup the merge conflicts (and the comment formatting) and this should be ready for merge, after which we will run some live tests


Default autologin password is not set.

Default password for default user unknown. Ideas on how to install nomad to hd wont work, because a password will be needed to instal to hd. Since this password is not set or not known ...

Hello @tps800, the password is set at first boot when configuring the default nomad user.

Yes, it is asked for, but later on exactly this password wont work for the
default user …
On Mon, Mar 21, 2022 at 5:53 AM Azrael JD @.***> wrote:

Hello @tps800 https://github.com/tps800, the password is set at first
boot when configuring the default nomad user.
—
Reply to this email directly, view it on GitHub
https://github.com/nomadbsd/NomadBSD/issues/103#issuecomment-1073484360,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFLNTCYYMCD6THJFSNKUCDVA76ENANCNFSM5RGN2KIA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Thomas

Yes, it is asked for, but later on exactly this password wont work for the
default user …

That's odd.
You can change the password for root and nomad as follows:

Reboot into single-user mode
Hit [ENTER] when asked to.
Run mount -a
Run kbdmap and select your keyboard layout.
Run passwd to change the root password.
Run passwd nomad to change the password for nomad.
Press CTRL+D or type exit followed by [ENTER] to exit from the shell to boot into multi-user mode.


Timezone incorrect when displayed on frontend

Timezone for timestamps is not translated to user-agents local timezone when presented on the frontend.

will solve in 5 mins @Mr-Oregano


Parallel Processing with Nightwatch and ChromeDriver without Selenium

Is it possible to use this framework without java and selenium?
Using nightwatch parallel auto feature directly avoiding selenium? Or is selenium a core component of Magellan?

Nope, selenium isn't a must to the magellan eco-system. There is an option to disable selenium auto launch in nightwatch.json. Similarly like http://testarmada.io/#manageAppiumLifecycle, selenium.start_process can be false so that nightwatch won't automatically launch selenium server for you.

I'm running a local executor, if i set start_process: false, obviously it start failing.

Where should be the place to start the chromedriver server? I mean calling chromedriver.start/stop in magellan? This is from the official guide: http://nightwatchjs.org/gettingstarted under ChromeDriver section 3.

i'm afraid you need to follow all the instructions especially this one
We also need to clear the default_path_prefix, as it is set by default to /wd/hub, which is what selenium is using.

I did set "default_path_prefix": "", to be empty under test_settings/default. Still failing

when you see error retrieving a new session ..., it means nightwatch is still looking for selenium server. you may still have selenium.start_process enabled somewhere. use --debug to have local executor to output the actual desiredCapabilities.

I did that:
[DEBUG][Local Executor] executor config: {
	"desiredCapabilities": {
		"browserName": "chrome",
		"chromeOptions": {
			"args": ["--no-sandbox", "start-maximized", "disable-web-security"],
			"prefs": {
				"credentials_enable_service": false,
				"profile.password_manager_enabled": false,
				"profile.managed_default_content_settings.images": 2
			}
		},
		"acceptSslCerts": true
	}
}


fft and ifft call vDSP_create_fftsetupD without calling the corresponding destroy function, resulting in memory leaks

In ndarray/complex-math.swift, fft(x: ndarray) and ifft(yr: ndarray, yi: ndarray) each call vDSP_create_fftsetupD to set up the following call of vDSP_fft_zropD. The system then allocates memory that is never released.
Simply appending a call to vDSP_destroy_fftsetupD at the end of each function would technically fix the leak, but these functions are not meant to be called in a performance-sensitive context anyway. In my own project, I have split the method into two, the first of which is only called once per value of N:
func fftInit(N: Int) -> FFTSetupD {
    var radix: FFTRadix = FFTRadix(FFT_RADIX2)
    var pass: vDSP_Length = vDSP_Length((log2(N.double)+1.0).int)
    var setup: FFTSetupD = vDSP_create_fftsetupD(pass, radix)
    return setup
}

func fft(x: ndarray, withSetup setup: FFTSetupD) -> (ndarray, ndarray) {
    //... (where the contents of fftInit above have been removed)
    vDSP_fft_zropD(setup, &x2, stride, &y, stride, log2n.length, dir)
    //...
}

The non-memory-leaking alternative closest to the original would be:
func fft(x: ndarray) -> (ndarray, ndarray) {
    //...
    var setup:FFTSetupD = vDSP_create_fftsetupD(pass, radix)
    //...
    vDSP_fft_zropD(setup, &x2, stride, &y, stride, log2n.length, dir)
    vDSP_destroy_fftsetupD(setup)
    //...
}

The reason I have not submitted a pull request is that clearly there is a decision to be made here: performance vs flexibility. My project requires performance, so I create the FFTSetupD structure once and reuse it over and over. Swix, as I understand it, is meant to emulate the NumPy model, where the flexibility of being able to use one single function call to compute the FFT is preferred over potential speed gains.
In summary, I would like to draw the maintainer's attention to the memory leak caused by repeated calls of fft or ifft, and introduced by vDSP_create_fftsetupD. I would also like to start a discussion on the limits of emulating the elegance of NumPy in Swift, and making number crunching in Swift fast and flexible at the same time.

I would be inclined to say by default it should be slow but not leak. If speed is desired, it would be advantageous to create an optional performance parameter. Maybe something like fft(x, setup:FFTSetup?) which would require the user to run another function for the setup. This jives with my internal compass; more work is required for more speed (and we should make that work easy).
Before we do that, are we sure that this is a significant performance hit? I'm inclined to believe it's not. Yeah it might take 10 times as long but the FFT is surprisingly fast and there is often other computation to be done. Numpy seems to follow this model; I can't detect any fft.init or equivalent anywhere.
To be clear, I would recommend simply inserting conditionals at the beginning and end of the function where the setup and destroy functions go. If the condition is not met and setup == nil we could assume (and document!) that fft_setup(N) (and a destroy function if necessary).
Feel free to submit a pull request for anything -- I can always them down. It could just add the destroy function or include the optional parameter as described. I would implement what you describe but am running short on time and am not incentivized to devote significant time to this project. Please, I will gladly test and test appropriate requests.

Closed by PR #10 (implemented in PR #11)


sub-datasets with different perspectives

How do I run the code if I have multiple sub-datasets with different perspectives? (putting all the data together takes up too much memory)

@heyikou Hi, do you mean GPU memory or CPU memory? For GPU OOM, you can turn off --preload. For CPU OOM, you may need to modify the data loader (provider.py) to load the image on-the-fly from the hard disk.

@ashawkey Thanks for the reply. My question is, suppose I have 4 sub datasets like image1, image2, image3, image4 and they represent 4 different regions in a large scene. How do I iteratively train them (there are about 1000+ 6000*6000 photos in total)

That is a really large dataset! I think the only way is to modify the provider to load images on-the-fly from all datasets (unless you have very large CPU memory too). Also, 6000x6000 seems not necessary at the initial training stages. You may try to downsample the images to e.g., 1024x1024.


Implement layouts for tablets, laptops, and desktops

add your media queries in sequence from small to large
add more details to portfolio item cards (date, type)

yerrrr


Amazon Bedrock and Authropic Claude issue with indenting model_name

How to set model name so that LangFuse can get it. I have errors:
'model_name'
Traceback (most recent call last):
File "/opt/conda/lib/python3.10/site-packages/langfuse/callback.py", line 479, in __on_llm_action
model_name = kwargs["invocation_params"]["model_name"]
KeyError: 'model_name'
run not found
Traceback (most recent call last):
File "/opt/conda/lib/python3.10/site-packages/langfuse/callback.py", line 541, in on_llm_end
raise Exception("run not found")
Exception: run not found

quick fix: https://github.com/langfuse/langfuse-python/pull/134

@kobrinartem thanks for the contribution. PR is merged. Please re-open in case of issues.


update to upstream v0.49.3

This PR updates to the latest upstream v0.49.3 controller image

FYI I want to bring other improvements from other releases into this.


Coverage support with test cases for skeleton code

This fixes #7

There seems to be an issue in lemurheavy/coveralls-public#522 because of which our repo's stats aren't being taken up by coveralls. Lets wait for that to be fixed before we merge.

The coveralls folks don't seem to be responding so once you give a :+1: I'll merge this. Builds would anyway work.


Allow for use with react version 17

Changes proposed in this Pull Request:

Update peer dependencies to allow for react version greater than 16

closing in favor of #265


People 138 update user skill rate content if exists

Ticket
https://netguru.atlassian.net/browse/PEOPLE-138
Description

user is able to edit his user_skill_rate multiple time during the day. We don't want to create new history each change during one day. Instead of that we find user_skill_rate_content from today and update it.

Before merge checklist

[ ] CircleCI is passing
[ ] Proper labels are set

Wrong branch. We should merge it with skills not with master so far


cdrtools: Update to 3.00

Update cdrtools and unmark as broken.
Only tested building under linux. Although it should build for darwin, etc. I have no means by which to test this.
Should add a license to the package as well. It contains parts that are licensed under CDDL, GPL2 and LPGL2, what do we do in the case of multiple licenses? Note that this is a package where there has been plenty of disagreement regarding the legality of it's licensing (package maintainers point of view). Could always just mark as unfree and move on, lol.

Yes let's mark it unfree, after all it was broken before so people won't have any problem.

Added the unfree license, and a note regarding why it has it.

What's that libbluray patch change?

Whoops, Rip Travis.
Accidentally commited a patch from something else I was working on. Fixed it. Thanks! :)

Built locally thanks.


New version break Code Blocks function

Describe the bug
The code blocks no longer scroll-able x-axis, if the line getting longer, it will increase the width of the code block instead. As you can see in the screenshot below, the entire page now align to the right.
To Reproduce
Steps to reproduce the behavior:

Create a code block with ```
Make a line a bit longer than usual
Notice how the entire page layout is broken

Expected behavior
It suppose to be scroll-able
Screenshots and Source

Desktop (please complete the following information):

Quartz Version: 4.4.0
node Version: 22.8.0
npm version: 10.8.2
OS: MacOS
Browser Zen-browser

Hey, can you check if the workaround in https://github.com/jackyzha0/quartz/issues/1353 fixes the issue?
If it does, I'll implement a pull request, but I want to make sure you're experiencing the same issue.

Unfortunately not, seems like a different problem.


In an HTML document, HTML features disappear within

In an HTML document HTML features† disappear within <script> tags.
† features = intellisense, highlighting, emmet, auto matching tag editing
simple use-case
<script>
myElement.innerHTML = `<div class="Html-Features-Should-Still-Work-Here"> ${asJavascriptFeaturesDoHere} </div>`
</script>

possible solution
Tag the backtick string, as follows:
myElement.innerHTML = /* html */`<div class="commentTaggedTemplateLiteral"> ${ haveCakeAndEatToo } </div>`

For example, see the extension "comment tagged templates," (VSCode Marketplace  / Github )
which adds highlighting (no other features) based on the comment tags the backtick string, and supports multiple languages.
Basically, instead of switching to JS language features in

In response to the VSCode Bot, I don't believe this is a duplicate of #77977 (<script type="text/html">), because it's more generally about HTML features within template strings within regular

@mjbvz @aeschli I'm not sure how we want to support this.

This can be done by that extension. Please open a feature request there. Thanks!

Okay, thanks for considering it!


Add Meta Data for each Stub

The ability to provide a specific title, description, and additional class information on a per stub basis would provide a number of benefits when using the style guide:

The title would provide clear, shared, terminology for the team to use with each component example
The description can be used to provide use instructions for when and how each component should be used within the site, or other relevant information for each variant.
The class option would give you the ability to showcase a component that otherwise would have display issues.  For example, we have a button that is used on dark backgrounds, it is very light and cannot be seen without a dark background on the parent div.

Example stub file:
:meta:
  'Buttons are available in 4 types: primary, secondary, outline, and outline_inverse.
  Method can be get (will generate a link with a role of button) or post, submit, cancel, reset (will generate a button/formtastic button).
  If a form object is provided for the location, formtastic action will be used.
:stubs:
-
  :mv_title: 'Primary Get Button'
  :mv_description:
    'This button should be the default, unless you are specifically instructed to use a different button, use this one.'
  :type: 'primary'
  :name: 'My Primary Link Button'
  :method: 'get'
  :location: 'javascript:void(0)'
-
  :mv_title: 'Outline Get Button'
  :mv_description:
    'This button will only be used according to the rules set forth by the UX team.'
  :type: 'outline'
  :name: 'My Outline Link Button'
  :method: 'get'
  :location: 'javascript:void(0)'
-
  :mv_title: 'Outline Inverse Get Button'
  :mv_description:
    'This button will only be used only on dark backgrounds.'
  :mv_classes: 'mv_item_background--dark'
  :type: 'outline_inverse'
  :name: 'My Outline Inverse Link Button'
  :method: 'get'
  :location: 'javascript:void(0)'

See PR #72
Here is an example using all 3 keys.  Note that the rounded corners are now visible due to the change in class, the title change, and the additional description information

+1 for the ideas!
Implementation moved to #73 instead of #72.


Add the option to have an interval when opening multiple articles at once

Newsboat 2.33.0
If there are many unread articles in a feed and the user wants to open them in a browser, it's easiest to open them all at once. However this comes with the side effect of potentially being blocked by the domain for having too many requests at once. It would be nice to have a feature that when executing open-all-unread-in-browser-and-mark-read that instead of opening all articles at once, the user can change the config file to add an x second delay when opening each article to avoid being blocked or having to solve captchas. This would be more convenient than forcing  the user to open all articles individually.

I reckon you could use a macro with a a custom script that delays opening URLs, something along those lines:
macro x set browser "echo %u >> /tmp/urls"; \
    open-all-unread-in-browser-and-mark-read; \
    set browser "~/bin/open-delayed.sh &"; \
    open-in-browser-noninteractively; \
    set browser "firefox"

~/bin/open-delayed.sh:
#!/bin/sh

n=0
while read -r url; do
	n=$((n + 1))
	if [ $((n % 3)) -eq 0 ]; then
		sleep 3
	fi
	firefox "$url"
done < /tmp/urls

rm /tmp/urls

However, I currently get an error in Newsboat that the browser aborted with exit code 127. Not sure what's going on here. You might figure that out and get it fully working, though.

This works perfectly for me. Thank you.


Support for applications without exposed ports or k8s services

It looks like when you use the 'metaparticle' runner that it assumes a service port will be provided when creating the pods:
Successfully tagged timfpark/metaparticle-example:latest
2017/12/08 15:33:11 Service "metaparticle-example" is invalid: spec.ports: Required value
==> Detected container metaparticle-example-3000602432-cqpx8:metaparticle-example-0
and also that a service exists when you exit:
^Cexec: internal error
F1208 15:40:41.905327   31945 mp-compiler.go:122] services "metaparticle-example" not found
goroutine 1 [running]:
github.com/golang/glog.stacks(0xc42045ce00, 0xc4201e00b0, 0x5c, 0xa9)
/home/bburns/gopath/src/github.com/golang/glog/glog.go:769 +0xa7
github.com/golang/glog.(*loggingT).output(0x20655a0, 0xc400000003, 0xc4201e0000, 0x1fef790, 0xe, 0x7a, 0x0)
/home/bburns/gopath/src/github.com/golang/glog/glog.go:720 +0x36b
github.com/golang/glog.(*loggingT).printf(0x20655a0, 0xc400000003, 0xc4204c6330, 0x29, 0x0, 0x0, 0x0)
/home/bburns/gopath/src/github.com/golang/glog/glog.go:655 +0x14f
github.com/golang/glog.Fatalf(0xc4204c6330, 0x29, 0x0, 0x0, 0x0)
/home/bburns/gopath/src/github.com/golang/glog/glog.go:1148 +0x67
main.main()
/home/bburns/gopath/src/github.com/metaparticle-io/metaparticle-ast/cmd/compiler/mp-compiler.go:122 +0x438
Is it possible to make this an optional element?
PS.  Happy to provide a PR if you can point me in the right direction.

PR would be awesome!  The code is in the metaparticle compiler, approximately here:
https://github.com/metaparticle-io/metaparticle-ast/blob/master/compiler/kubernetes-compiler.go#L272


Update TileMap to use new navigation polygon baking

Updates TileMap to use new navigation polygon baking from https://github.com/godotengine/godot/pull/80796.
Fixes TileDataEditor error when building Godot with deprecated=no since NavigationPolygon make_polygons_from_outlines() is depr.
Baking the TileMap cell navigation polygons should eliminate cases where users by accident place 10+ vertices stacked up hidden in the same TileMapEditor corner breaking the mesh.
Replaces some old NavigationServer3D includes no longer necessary as the NavigationServer2D has received the same debug functions and is needed for the navmesh baking anyway.

Thanks!


Extra letter spacing in terminal when open a directory

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

VS Code Version: 1.56.2
OS Version: Windows_NT x64 10.0.18363

Steps to Reproduce:

Open VS Code normally (by default, open with the directory that I was working)
Open a terminal

Expected:

Actual:

When I open VS Code without directory, the terminal works as normal.
Once I open a directory, the problem comes back.
Also, when I edit the setting and save it, all extra space removed immediately.
But it didn't solve the problem because any newly open terminal still have that problem.
Ways I tried but didn't solve it:
Disable all extensions
Changing the terminal to PowerShell or other shells

/duplicate #120004
Should be fixed in Insider build https://code.visualstudio.com/insiders/


from STIX information

Issue with functionality for loaded json file, official showing 2 of 16 but has only 1 of 16 (artifact), also custom STIX should show 1 (x-autonomous-system) of 2 (artifact and x-autonomous-system),
Official STIX objects percentage = Number of unique official objects in mapping out of number of total unique official objects in current selected STIX version
Custom STIX percentage = Number of unique custom STIX object in mapping / (Number of unique custom STIX objects in mapping + Number of unique official STIX objects in mapping)
{
  "artifact": {
    "fields": {
      "mime_type": [
        "1"
      ]
    }
  },
  "x-autonomous-system": {
    "fields": {
      "number": [
        "1"
      ],
      "name": [
        "3"
      ]
    }
  },
  "directoryit": {
    "fields": {
      "path": [
        "1",
        "1"
      ]
    }
  }
}


Fix typo in CONTRIBUTING.md

Signed-off-by: Gareth Clay<EMAIL_ADDRESS>Signed-off-by: George Lestaris<EMAIL_ADDRESS>

Thanks @glestaris !


New Japan Sources

https://saigai.gsi.go.jp/jusho/download/index.html

new vs current
red current black new

@justinelliotmeyers Here is a brief summary of the available address dataset in Japan region.
Japanese addressing structure
Wikipedia has a nice reference for this.

Wikipedia: Japanese addressing system

Available Open dataset
In Jukyo Hyoji Jusho area

Osaka City #877

Out of Jukyo Hoji Jusho area (Chiban area)
Some datasets are published from the municipality as Open Dataset.
Those Chiban addresses are from cadastre, so it has polygon to represent their coverage.
Each dataset has its own attribute structure.

Hokkaido, Muroran-shi direct link:
Aichi, Handa-shi direct link
Hyogo, Kawanishi-shi direct link

Frontage point by GSI
Frontage point is the reference points to define the address when a new building/house is built. Available for Jukyo Hyoji Jusho area. (means urban)
This is not an actual address. But they are available as "quasi" addresses.
This dataset is protected by Survey law in Japanese, so cannot used as Open (prohibited re-distribution and publishment. It need an application to GSI)

I don't know if the data from the Japan postal office is of any use.
Check this project: https://github.com/polm/posuto


Don't redeclare BSON variable

This fixes a problem that arises when using Rollup to bundle an application that uses this library.
[!] Error: Identifier 'BSON' has already been declared
node_modules/mongodb-core/lib/auth/plain.js (11:4)
 9:   , MongoError = require('../error');
10:
11: var BSON = retrieveBSON();
        ^
12:
13: var AuthSession = function(db, username, password) {

If anyone else has this problem and this PR doesn't get merged, I solved my problems temporarily by using rollup-plugin-replace as such:
import replace from 'rollup-plugin-replace'

export default {
  plugins: [
    ...
    replace({
      delimiters: ['', ''],
      'var BSON = retrieveBSON();': 'BSON = retrieveBSON();'
    }),
    ...
  ]
}

@denizdogan Hi, thanks for this!  I actually think the code block should look like this:
var f = require('util').format
  , retrieveBSON = require('../connection/utils').retrieveBSON
  , Query = require('../connection/commands').Query
  , MongoError = require('../error');

var BSON = retrieveBSON()
  , Binary = BSON.Binary;

@mbroadst Thanks for the swift response, much appreciated! I've updated my branch accordingly :)

@denizdogan looks good, thanks for your contribution!


Surface document deletions through the API.

What?
To expose deleted OSM documents through the API in a way that corresponds to the underlying structure of the data model as closely as possible.
Why?
osm-p2p-db makes no assumption about providing a single, "true" answer. The underlying data model is messy: forks and multiple versions of documents are both possible and valid states.
The OSM API itself assumes a linear history, which brings complication. A modular approach, with clear division of responsibilities makes sense:

osm-p2p-db can provide a raw view into the true, messy data model
downstream models, like osm-p2p-server, can perform transformations
on the forking data to produce a linear view of history, depending on
its parameters & preferences

This PR is to make this possible: expose forks and deletions in an explicit way in order to let downstream modules get a more honest view of the forking data they're working with.
Changes?
Look at the diff for README.md; deleted documents are presented alongside non-deleted documents, via hyperkv.
These changes are breaking, and will require a major version bump.
What's Next?
Start to break apart non-server logic in osm-p2p-server that does data linearization into a new module, osm-p2p-api.
From there, ripple these API changes out to osm-p2p-api, which can be solely responsible for making sense of non-linear data and explicit deletions, and express them to further downstream modules, like osm-p2p-server.

Re unhandled errors: I added error reporting for the "easy" cases. For some of the others -- like in the indexer and during node collection for streaming kdb queries -- I still want to think a bit more deeply about the failure modes.
For the indexer, we can either skip on failure or fatally terminate the program. Neither is very appealing: potentially incorrect data vs program won't run.
For the node collector, hard failure means the kdb queries are impossible if some data is bad, whereas skipping bad data might actually be acceptable.

I think I've handled everything that we discussed on this PR. Another look-over would be appreciated: I'm eager to move onto the next big PR. ;)

Revisions pushed.
Yes, let's do changeset_id on deletions in a separate (but very soon) PR.


Db crashes when large data is inserted

Hi Team,
We tried to insert 5M records, the db crashed.
Is there any settings to move the data into disk when overflow happens?
Please help us with the solution.
Arun.

I suppose this is a duplicate of #17572


Allow unlocking specific names, expand /unlockip to work for mods, and clarify which names are locked on /ip

Hopefully fixed


allow to mount host volumes in AWS Batch

What does this PR do?
Adds an option to @batch decorator to mount host volumes inside the container. @batch(mount_host_volumes="/mnt/"). This way, /mnt from host will be mounted at /mnt inside the container. This (partially) addresses #441
In this release this is considered an advanced feature due to less friendly UX and the fact that troubleshooting this requires a decent knowledge of AWS Batch.
I've tested this on Batch and Step Functions and it seems to work!
Potential improvements in future PRs, not included here

First class support for per-job EFS mounts. Not included this because the configuration is pretty hairy, needs some extra thinking. However, you should be able to use this PR as is to expose EFS volumes mounted at host to containers, as described here.

Support for customizing mount points inside a container. Right now /mnt from host always gets mounted as /mnt inside the container.

While a good start, I think this implementation falls short for a couple of reasons:

as mentioned, not being able to set the mount path inside the container seems like a strange limitation, and will likely place a burden on application developers to change their applications to fit the details of the infrastructure.
including this in @batch means it can only be used in flows that are forced to run a particular step on Batch (or else in every step if using with syntax)

it seems a more natural way for this to work would be some mechanism to specify these Batch-specific resource definitions in @resources (either as nested configs, or else as part of an @batch_resources decorator).

Combined with the ability to set the container mount path, this should make it easy to have local runs (e.g. for integration tests) that work seamlessly with remote runs in production.
This desire to define Batch-specific resources arises in other contexts, e.g. the desire to set a per-step job queue without forcing the step to run on Batch.  Figuring out the idiom for this configuration in Metaflow and embracing it for all such configs would really increase the flexibility.

Good points, tbh this PR was intended to solve a pretty narrow (advanced) use case of mounting EFS/FSx volumes from host into the container.
Re: local runs, wouldn't you have to fork the logic? You'd have to remember that the step may run in local mode and make sure to branch, something like:
@resources(batch_mount_points=["/mnt"])
def step_foo(self):
    if os.path.exists("/mnt"):
         # running on Batch
        model = load_model("/mnt/foo.tar.gz")
    else:
        # running locally
        model = MockLocalModel()
...

In this sense, one benefit of keeping it in @batch like in this PR that the UX is more foolproof; you're guaranteed that the step will run on Batch and /mnt will be there. I do see the benefit of being able to run the code locally without changing the annotation though.

Thanks @oavdeev. I am hoping this PR gets merged as I need this feature for similar use case. Were you able to test this on AWS metaflow deployment? If yes, Kindly share the steps so I can replicate it. Thanks


Error on npm install

When running npm install I got the following error:
npm install

><EMAIL_ADDRESS>postinstall /Users/ben/workspace/travis-handlers/.atomist/node_modules/@atomist/rugs
> tslint **/*.ts

sh: tslint: command not found
npm WARN .atomist No description
npm WARN .atomist No repository field.
npm WARN .atomist No license field.
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/Cellar/node/7.9.0/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.9.0
npm ERR! npm  v4.2.0
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn

npm ERR<EMAIL_ADDRESS>postinstall: `tslint **/*.ts`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'tslint **/*.ts'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the @atomist/rugs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     tslint **/*.ts
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs @atomist/rugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls @atomist/rugs
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/ben/.npm/_logs/2017-04-28T10_02_25_819Z-debug.log

I had to run npm install typescript tslint to fix.
Could this be added to the install script somehow? The error is actually a little hard to spot in the output.
@ddgenome Any thoughts on this?

Please use yarn to install packages.
I'm not sure what the best approach here is. Should we be adding things like tslint and typescript to the package.json of every file so they get installed properly?
What do you think @kipz and @claymccoy ?

Looks like this error is actually caused by a problem with the @atomist/rugs package.json. I'll create a ticket there and fix that.

https://github.com/atomist/rugs/issues/12


Issue with the mist_site_setting resource provider

I am trying to import the site settings using the following command
Site Setting can be imported by specifying the site_id
terraform import mist_site_setting.site_setting_one 17b46405-3a6d-4715-8bb4-6bb6d06f316a..however i am encountering the following issue
Error: State Write Error
│
│ An unexpected error was encountered trying to retrieve type information at a given path. This is always an error in
│ the provider. Please report the following to the provider developer:
│
│ Error: AttributeName("id") still remains in the path: could not find attribute or block "id" in schema

Hi @Lava2014 , this should have been fixed in the new versions.
FYI, I made a change in the mist_org_inventory.devices structure. Please see the provider documentation for more details.

closed for inactivity


add forums for divisions into one category for SC

Star Citizen Divisions

Division 1

2 etc

Work progession
ongoing

| Created 2 Division spaces more will be added

Section restructured with a test phase for Forum i need @meckleunn to approve this idea if not i will revoke changes

im not seeing it? Can you link me to forum

Im gonna close this issue it will be condensed with issue #30


Gstreamer version discrepancy in rel-2020.1

When checking the bbappends for the gstreamer recipes i realized that the version is set to 1.16.0
However in the gstreamer mirror repos of xilinx itself it says it is release 1.16.1
And on the poky zeus release it is version 1.16.2.
Seems a bit messy. Which version is the one really targeted with the xilinx 2020.1 release?

A bit disappointing that this problem is still the same in the 2020.2 release and this issue not even got an answer since June...

Hi, for 2020.1 and 2020.2 the xilinx gstreamer versions are set to 1.16.1. Thank you for pointing out the issue with PV. We will update it in our next release.

Great news, thank you for your time.


Fix problem with ui-bootstrap modal

When used together with ui-bootstrap modal, ngNotify notification displayed below the modal dialog. This commit fixed the problem by adding z-index on .ngn
I assume that the CSS file are generated by the sass file, so I only add z-index to sass file, and not to the css.

Hey @mgoku, thanks for the suggestion.  I just merged in a pull request with the same exact adjustment, so I'll close this one out and setup a new release.  Thanks again!


Balance acceptance tests across partitions

Acceptance tests generally take longer to run than unit/integration tests, so spread them evenly across partitions when splitting.

@trentmwillis what are your thoughts? Just an idea that I had that seemed almost as fast to code up and PR than file an issue for discussion. So let me know if you think this makes sense or not.

Thanks for the PR!
 Additionally, the partitioning algorithm is very naive and puts every nth module into partition n. Therefore, you should actually wind up with a fairly balanced split of acceptance, integration, and unit tests by default.
That said, an earlier iteration of this addon attempted to "weight" each type of test by doing something similar to what you have proposed here; acceptance tests weighed more than integration tests weighed more than unit tests. This proves to be very fragile and just as easily becomes unbalanced, because each module can have varying numbers of tests within them. Thus, an acceptance test module with 1 test is much less costly than a module with 10 or even 100 tests.
I do want to support "weighted" splitting at some point in the future, but it needs to be a robust solution that is actually based on the historical runtime of each module. I discuss and am tracking this feature in https://github.com/trentmwillis/ember-exam/issues/31.
Closing this for now; would love help with #31 though if you're interested! I'm not 100% sure how to solve it at this point in time.


Release/8.0.0

Pull Request Test Coverage Report for Build 2697

1955 of 2004 (97.55%)  changed or added relevant lines in 60 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.6%) to 97.421%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

eventsourcing/domain/model/entity.py
130
131
99.24%

eventsourcing/infrastructure/sqlalchemy/datastore.py
36
37
97.3%

eventsourcing/infrastructure/sequenceditemmapper.py
45
47
95.74%

eventsourcing/utils/transcoding.py
136
138
98.55%

eventsourcing/application/process.py
152
155
98.06%

eventsourcing/infrastructure/popo/manager.py
54
57
94.74%

eventsourcing/application/notificationlog.py
61
65
93.85%

eventsourcing/system/multiprocess.py
38
42
90.48%

eventsourcing/domain/model/decorators.py
56
64
87.5%

eventsourcing/system/runner.py
159
180
88.33%

Files with Coverage Reduction
New Missed Lines
%

eventsourcing/infrastructure/popo/manager.py
1
95.52%

eventsourcing/infrastructure/sqlalchemy/manager.py
3
96.21%

Totals

Change from base Build 2690:
0.6%

Covered Lines:
4872

Relevant Lines:
5001

💛  - Coveralls


BUG: use newer cinit syntax for cython 0.15

Was raising an error when cythonizing with cython 0.15.  Tested as still
working on cython 0.13 with this change.

Pushed, thanks Matthew.


Compression: Add threshold for compression

There are instances where compression is a detriment by comparison to the benefit. Where the time to compress and gzip payload is higher than the original payload.
ngnix defaults to all content with the gzip_min_length setting used to set the minimum length of a response to that will be gzipped.
expressjs compression module is 1k by default, uses threshold option to set globally.

As content-length is optional and only set by a few components, this would require buffering the response body up to that threshold before enabling compression. That's doable, but it can cause un-expected delays for streaming scenarios.

For the streaming scenarios the threshold should be set to 0, by passing the need to for check/routine.

Except that streaming done for some requests, where this setting would be for all requests.

So is the use case for the compression middleware only for streaming? Considering that Kestrel is not a web facing server and should be proxied. So typically, compression would be handled by IIS, nginx or apache for requests.  Trying to find to use case, or is this in an effort to get to a public facing server?

Yes, the main use case is for when Kestrel or WebListener are used independently. Kestrel will eventually be safe for edge deployments, and WebListener already is.
Streams are not the main use case, but the middleware should not break streaming with too much buffering like the IIS implementation does.

When the static file middleware is being used, the size of the content is known. Can't that scenario be optimized?


Adds composition lesson translation to spanish

Title's very straight :shipit:

Wow @setzer777, you're fast!  Could @erickgnavar or @jesusangelm take a peek at this?

Hi, @setzer777 I added some notes to the commit.
Thanks for your work

Hi @erickgnavar, thanks for the review, really helpful c: working on the comments

Done haha :shipit:

Awesome!  Thank you @setzer777 and @erickgnavar, I appreciate both your help :grinning:

@setzer777 what is your twitter handle btw?  I like to give credit when I tweet about new lessons/translations.
Thanks again

@doomspork and to everyone else, you can find me on twitter as @AlbertooRomeroo.
I was thinking you should be talking more about String in Elixir, from how do they work, simple operations and manipulation, how are they handled inside the BEAM, etc., if you need some help with that, please let me know!
Another suggestion is to add some exercises at the end of the modules, so ElixirSchool can turn into a real school where people's evaluating student's work c: I'd also be glad to help you on that.
I'm about to start using Elixir in production in a few months in my organization, and I've found Elixir super interesting thanks to the tremendous power of the BEAM and the beautiful functional-programming paradigm and the beauty of Ruby. Keep in touch guys!


UK regions for Northern Ireland are incorrect

These are the six official region/counties/states for Northern Ireland (under United Kingdom):
Antrim
Armagh
Down
Derry/Londonderry
Fermanagh
Tyrone
https://en.wikipedia.org/wiki/Counties_of_Northern_Ireland#:~:text=Northern Ireland is divided into,its 1921 creation until 1973.

I think the list is from https://en.wikipedia.org/wiki/Reform_of_local_government_in_Northern_Ireland#Second_scheme:_eleven_districts


Remaining phantom updates

Describe the bug
Phantom updates still occur (See the related discussion at https://github.com/solidjs/solid/discussions/505, even after the recent fix)
To Reproduce
https://playground.solidjs.com/?hash=-1391246675&version=1.0.0
https://gist.github.com/cynecx/1cc32b7b2eafc47d8b696cdfd518056b
To reproduce, add some nodes, then click reset.
Expected behavior
The Expand component should not be updated when its parent should've disposed that component.

Yeah I see it. This issue is specific to the array helpers. Nested roots are not properly tracing upwards. This is is a tricky one. The current implementation for tracing came out of a different bug fix so I need to make sure that I fix this and won't break that one either. I need a better general solution for this case.

Thanks for looking into this. I've tested this out on my actual code base and it doesn't seem fixed. However the reproduction seems to be fixed. I am currently trying to extract a reproduction case :/

Okay. Reducing the code to something small and reproducible was harder than anticipated.
https://playground.solidjs.com/?hash=-1903645007&version=1.0.2
https://gist.github.com/cynecx/d58f4f1b1387c24182157b36e27e38f9
To reproduce: Click "Load" -> "Add Button" -> "Load"

I really appreciate it. These are really hard to track down. And I thought I had nailed the generic case with the last case. Most of the problem is that in attempts to optimize I've been cutting out necessary behavior. It's really easy when I am missing cases to have optimizations break certain behavior.

Ok I see it. I walk up to check potentially stale owners. However, I was just going up to the topmost one. This works in most cases as they are shallow. But if the topmost doesn't actually cause the disposal (it's a false alarm) it continues on its way. And we run into the error.
I actually need to resolve all the potential ones down the tree. I figured out a quick fix but want to look at how to optimize this more given the implications on the core. Thank you so much for helping me find this case.

Thanks a lot! I really appreciate it. The most recent release (1.0.3) seems to have fixed our production code :)

That's great to hear. And this exploration also led to a slight improvement in reactive update propagation performance.


Allow project to be uploaded to pypi

Added pyproject.toml, which is required to upload project
Removed setup.py, since it is replaced by pyproject.toml
Made lazy deberta setup, since right now import lm_polygraph downloads 1.2G model

Resulting page: https://test.pypi.org/project/lm-polygraph/0.0.2.dev0/

Need to add https://setuptools.pypa.io/en/latest/userguide/entry_point.html to pyproject.toml to expose our executable scripts.

Need to add https://setuptools.pypa.io/en/latest/userguide/entry_point.html to pyproject.toml to expose our executable scripts.

Done

@SpeedOfMagic can you also check that installing of LM Polygraph into clean environment succeeds and produces a working installation - i.e. all executable scripts are accessible and tests pass?

@SpeedOfMagic can you also check that installing of LM Polygraph into clean environment succeeds and produces a working installation - i.e. all executable scripts are accessible and tests pass?

Done, everything seems fine to me


chore: upgrade charts

updated chart jx3/jxboot-helmfile-resources from 1.0.41 to 1.0.42
updated chart jx3/lighthouse from 1.0.3 to 1.0.7

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign rajdavies
You can assign the PR to them by writing /assign @rajdavies in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test gsm

kube
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test gsm

kube
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test kube

vault
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test gsm

kube
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test kube

vault
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test vault

gsm-kapp
7bdac7ca0da6cdfe388f53fd0bf37f65e50fedab
link
/test gsm-kapp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


#11453: Add options to enable compilation with sanitizers

Ticket
https://github.com/tenstorrent/tt-metal/issues/11453
Problem description
We want the ability to compile C++ with sanitizers to verify code's safety
What's changed
This pull request adds options for MemorySanitizer, ThreadSanitizer, and UndefinedBehaviorSanitizer to CMake and the build_metal.sh script, and ensures that they're mutually exclusive during configuration.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

@TT-billteng thanks for pinging me. The problem was that I didn't expand the CMake variables in the generator expressions, I've fixed that this time around.


Azurestack: az vm images list  returns a cached response which is not applicable for azurestack

Description
az vm images list right now lists a cached response. The images listed in this are not likely available in azure stack instance.
In azure stack the admin uploads the images as part of the initial setup and he may upload only a specific set of images.
az vm images list --all actually makes the api call and gets the right set of images. May be the solution is to make --all as the default and use the cached data only for TabTab completion

Not sure if --all is default behavior or having user pass profile or make a call in the context of profile they are in. @yugangw-msft and @derekbekoe to discuss as well

@derekbekoe, @tjprescott
I suggest we detect under azure stack, and if yes, we do not expose --all and always makes api call. We should not use cached data under all circumstances

agree with Yugang,  a complicated solution would be to maintain a per cloud on demand cache
we could do the following.

Keep an empty cache of per cloud images, instead of prepopulating with a standard  set(cache may be persisted in file)
If the cache is empty,  make the api call and populate the per cloud cache
If the cache is not empty, show it from the just like we do now
With this only the first call is going to be costly. I am not sure how often these set of images are changed in azure and if so often we may need to force invalidate the cache. Or I am fine with making the –all default and incurring the cost every time instead of showing the wrong list of images for azurestack.


Iterable SDK hanging my app

About 1/2 of my production crashes right now are from my app hanging on startup, on this line of code which is called when starting the Iterable SDK:
https://github.com/Iterable/swift-sdk/blob/master/swift-sdk/Internal/IterableAppIntegrationInternal.swift#L29
(I have to add, your spelling of semaphore is not inspiring a lot of confidence, lol.)
This affects less than 0.5% of my sessions, but it is still high enough to get my attention.  Crashes occur on iPhone & iPad devices running various versions of iOS 14 & 15.  My app was running Iterable iOS SDK v6.3.3 for all of these crashes.
Here is a full stack trace from my crash reporter:
App Hang: The app was terminated while unresponsive

0  libsystem_kernel.dylib _semaphore_wait_trap
1  libdispatch.dylib      __dispatch_sema4_wait
2  libdispatch.dylib      __dispatch_semaphore_wait_slow
3  Trala                  notificationsEnabled.get (IterableAppIntegrationInternal.swift:29:24)
4  Trala                  notificationsEnabled.get (<compiler-generated>)
5  Trala                  register (InternalIterableAPI.swift:152:31)
6  Trala                  register (IterableAPI.swift:208:33)
7  Trala                  application (AppDelegate.swift:126:21)
8  Trala                  application (<compiler-generated>)
9  libdispatch.dylib      __dispatch_call_block_and_release
10 libdispatch.dylib      __dispatch_client_callout
11 libdispatch.dylib      __dispatch_main_queue_callback_4CF
12 CoreFoundation         ___CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
13 CoreFoundation         ___CFRunLoopRun
14 CoreFoundation         _CFRunLoopRunSpecific
15 GraphicsServices       _GSEventRunModal
16 UIKitCore              -[UIApplication _run]
17 UIKitCore              _UIApplicationMain
18 Trala                  main (main.swift:29:1)
19 <unknown>              0x105315a20

Please let me know if you need more info.

Apple's documentation for UNUSerNotificationCenter's getNotificationSettings(completion:) method says the completion block "may execute [the completion] block on a background thread" (my emphasis on "may".)
I would read this to imply that the completion block may be called on the main thread under some circumstances, which would explain the deadlock that apparently is happening in my app.
In any case, it's poor practice to wait the main thread on a semaphore while stuff happens on other threads, and this code should be changed to not block the main thread that way.

@jbelkins Thank you for brining this to our attention. We have not seen this issue locally.
We will greatly appreciate if you can try our solution and provide feedback once we commit this to a branch.

@jbelkins Agreed. Our code earlier was non-blocking and this code was introduced via due to some other problems. We will be looking at this issue with high priority.

Thanks for your prompt attention.  Please tag me when you publish a fix and I'll ship it as soon as I can.
FYI I just filed an Iterable support ticket citing this Github issue as well.

Thanks. The ticket is implemented and is being reviewed. We will be publishing a fix soon.

@jbelkins We have the fix merged in master branch. Would you be able to try that?

@tapashmajumder Might be middle of next week before I can put up a new app release.  If you can get this tested at your end, you should go ahead & release it.
And if I do ship this fix before it's published, rather than take everything in master, I'll lock to this commit: https://github.com/Iterable/swift-sdk/commit/bccfb50c8a9be06446de340f139a439420f0aa80 Would that work?

@jbelkins Yes that is the right commit if you can release.
Master currently has a security fix which we would like to release together with other security tickets that we are currently working on. So it may take us some time (probably around 7-10 days or so) to publish our next release.

@tapashmajumder Just shipped this fix today.  I should be able to say whether this is fixed in about a week or so.

Hi @jbelkins Thank you so much. Please keep us updated. We will be releasing a new version with this and a few other fixes in a week or two.

I’ve had this fix in production for about 9 days now and no reoccurrences thus far.  I think this can be closed now.
Please let me know when this ships in a stable release.

@jbelkins That is great news. I will update when we ship this change.

This issue is fixed in latest release 6.4.0. Closing.


Adds optional rect property to sprite layer class

Can we document that the layer rect is just used as a hint. Otherwise lgtm

Certainly will add documentation to all sprite classes! :)


feat: remove GKEHubv1alpha2

GKEHubv1alpha2 protos are removed. This PR removes those modules and updates the .OwlBot.yaml file to ensure they are not copied over from googleapis-gen in the future.

Adding do not merge until confirmation from the team that this is the correct thing to do in order to remove this package.


Nested Perms Results in unecessary queries (N+1?)

Describe the Bug
Nesting permissions i.e private_details checked by HasSourcePerm yields unnecessary queries that could be optimized.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.

this may be a more performant workaround
    @strawberry_django.field(
        annotate={
            "_private_details": lambda info: Case(
                When(
                    Exists(
                        filter_for_user(
                            models.Note.objects.all(),
                            info.context.request.user,
                            [PrivateNotePermissions.VIEW],
                        )
                    ),
                    then=F("private_details"),
                ),
                default=Value(None),
            ),
        }
    )
    def private_details(self, root: models.Note) -> Optional[str]:
        return root._private_details

Hey @vecchp ,
The main difference between the 2 codes is that in the first one you are checking for HasSourcePerm, which will check permissions on top of the root object itself when resolving private_details, and in the second one you are doing the prefetch with the permissions.
This is a similar issue to https://github.com/strawberry-graphql/strawberry-django/issues/337 in which the optimizer is not currently able to optimize some more complex nested lists/connections, specially when they are using pagination, filtering, permissioning (like this), etc
Thanks for reporting this! I'll soon try to take a look at that nested issue and will try to solve this issue together :)

Seems like a similar library for graphene has worked around this issue
https://github.com/MrThearMan/graphene-django-query-optimizer/issues/62
https://github.com/MrThearMan/graphene-django-query-optimizer/commit/355b50783cc239c76ca1dbeb11ab515d87197c2c

Seems like a similar library for graphene has worked around this issue. At least with nested queries maybe unrelated to perms.
MrThearMan/graphene-django-query-optimizer#62 MrThearMan/graphene-django-query-optimizer@355b507

Hrmm thanks for linking those :), I'll take a look at that for inspiration!


Updated logbook function

Updated version to allow basic stats functionality as written in https://github.com/lemeryfertitta/Climbdex/issues/55

extended the logbook_entries to allow AUTH with username/password and user_id/token
added climb_uuid and climb_angle_uuid to the results
removed climb_uuid and climb_angle_uuid from the csv export to keep the structure as it was before making the changes board,angle,climb_name,date,logged_grade,displayed_grade,difficulty,tries,is_mirror,sessions_count,tries_total,is_repeat,is_ascent,comment

hope this is fine now :)


CUDA windows

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@jaimergp : CUDA is now correctly detected but I am now running into the original issue:
"CMakeCUDACompilerId.cu" failed.
# ...
'cl.exe' is not recognized as an internal or external command,

@jaimergp it fails the same with the CMake patch on Windows. I am out of ideas here.


fix(submodules): location

Added [submodule "packages/contracts/lib/Uniswap/v3-periphery"]

@hashedMae I accidentally included my full codebase formatting/prettier run squashed with my attempt at fixing the slither errors, which adds noise to the diff. It would be helpful if you do it on your branch before this is merged so you can see a clean diff.


Fix for issue 211

Added a Boolean variable in events.js which check to see if JS is enabled by the user's browser or not. If JS is enabled and there are no events, a message saying "Loading" or "There are no events scheduled!" will be displayed. If JS is disabled and there are no events, nothing will be displayed.

Closed #211.


MGMT-16815: add missing services to install ignition

When 'StopLocalRegistry' is enabled in ApplianceConfig, the stop-local-registry service should be added to the install ignition. Since the service is under 'data/services/install' folder, adding its content to the install ignition.

/retest

/retest

/test images

/retest-required


[euphoria-beam] wip

The Travis build was restarted without changes. And it was surprisingly enough to make the build successful.


Fix fork tests to not run into compliation issues when running coverage report

Current dependencies on/for this PR:

main

PR #167   👈

This comment was auto-generated by Graphite.


How can i hide y and x axis on radar

Hi all,
How can i hide this two lines on radar chart :

i tried with grid options and show false and some kind of parameters without success.
Do you have an idea ?
Thx
I use the last apexcharts's version and vue-apexcharts

Hi, I used the pure JavaScript version of apexcharts and the y-axis labels disapears using
yaxis: { show: false }
However I face the same issue as piolet when trying to hide the yaxis label using angular-apexcharts . Please help


issue-614 resolve version from model properties if necessary

new branch name

Please squash commits when done.

@slachiewicz Could you please approve the workflow? Thanks.

Sorry for asking, but how to squash existing commits? Isn't this done during merge into master?
Another question, no hurry, just for my further planing, when can I expect the next release with this fix?

You can force push the commits to origin.

Another question, no hurry, just for my further planing, when can I expect the next release with this fix?

A question to @slawekjaranowski probably ;)

@TorstenKruse thanks for PR.
In mentioned issue we have that display-dependency-updates are also affected.
As I see you fix in dependency-updates-report - can you also check display-dependency-updates?

Another question, no hurry, just for my further planing, when can I expect the next release with this fix?

A question to @slawekjaranowski probably ;)

Lat release was at 23 Oct,
As I see how many changes we have and how many contributors I'm very happy ...
So to have valuable feedback I have plan to release about once a month or two.

Fixed for display-dependency-updates too.
I'm still not sure, if my version interpolation is sitting at the right place, perhaps someone with deeper knowledge of the project checks again.

@TorstenKruse please also rebase with current codebase and resolve conflicts.

@slawekjaranowski Done. Hoping for a quick merge before more codebase changes. ;)