v0.9.0 unexpectedly justifies text

Here is an example program adapted from piet I wrote in my piet-cosmic-text crate. It is using cosmic-text v0.8.0

Here is the program after I update it to v0.9.0:

It appears that the text has been justified for some reason, despite there being no changes in the inputs to the code. The shaping is in Advanced mode, as this particular text sample does not render properly in Basic mode.
As far as I can tell, this is a problem on the cosmic-text side, as very little actual changes on my end were conducted between the two above samples. Here is the commit: https://github.com/notgull/piet-cosmic-text/commit/d323ede6b6204abac4a388862db907705e89d147
Just to see if it was my alignment system, I manually set each line's alignment to be Some(Align::Left).
diff --git a/src/lib.rs b/src/lib.rs
index caa6e42..07679cb 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -731,12 +731,7 @@ impl piet::TextLayoutBuilder for TextLayoutBuilder {
             let attrs_list = range_attributes.text_attributes(start..end, default_attrs)?;

             let mut line = BufferLine::new(line, attrs_list, shaping);
-            line.set_align(self.alignment.map(|a| match a {
-                TextAlignment::Start => cosmic_text::Align::Left,
-                TextAlignment::Center => cosmic_text::Align::Center,
-                TextAlignment::End => cosmic_text::Align::Right,
-                TextAlignment::Justified => cosmic_text::Align::Justified,
-            }));
+            line.set_align(Some(cosmic_text::Align::Left));

             buffer_lines.push(line);

I did not witness any changes in the text.
I suppose that my usage of PhysicalGlyph could be wrong, but I do not see how this could lead to justified text.

I don't see any of the cosmic-text examples showing this behavior. Please provide instructions on how I can reproduce the issue.

Here is a repository demonstrating the issue, using nothing but cosmic-text as well as tiny-skia for rendering. The first commit uses cosmic-text v0.8.0. It contains an example that builds up an AttrsList, creates a buffer line, inserts it into the Buffer and then renders it using swash. The resulting image is this:

I then upgrade to cosmic-text v0.9.0. The upgrade in its entirety, aside from Cargo.lock upgrades, is contained below:
diff --git a/Cargo.toml b/Cargo.toml
index 077e591..5de006f 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -6,6 +6,6 @@ edition = "2021"
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

 [dependencies]
-cosmic-text = "0.8.0"
+cosmic-text = "0.9.0"
 tiny-skia = "0.11.1"
 tracing-subscriber = "0.3.17"
diff --git a/after.png b/after.png
new file mode 100644
index 0000000..3230e43
Binary files /dev/null and b/after.png differ
diff --git a/src/main.rs b/src/main.rs
index d4f1e65..5c0cdc8 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -1,7 +1,7 @@
 // MIT/Apache2 License.
 //! Reproduction of cosmic text issue #151
-//!
-//! This version uses cosmic_text v0.8.0, which works and does not justify text.
+//!
+//! This version uses cosmic_text v0.9.0, which unexpectedly justifies text.

 use cosmic_text::{self as ct, Buffer, BufferLine, Color, FontSystem};

@@ -102,7 +102,7 @@ fn main() {
     );

     // Create and format the text.
-    let line = BufferLine::new(TEXT, list);
+    let line = BufferLine::new(TEXT, list, ct::Shaping::Advanced);
     buffer.lines = vec![line];
     buffer.set_wrap(&mut fs, ct::Wrap::Word);
     buffer.set_size(&mut fs, 250.0, 300.0);

This is the resulting image:

Oddly, when I comment out the change in the font family...
diff --git a/src/main.rs b/src/main.rs
index 5c0cdc8..750eee7 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -96,7 +96,7 @@ fn main() {
         240..346,
         ct::Attrs {
             color_opt: Some(RED),
-            family: ct::Family::Monospace,
+//            family: ct::Family::Monospace,
             ..default_attrs
         },
     );

...it seems to lay out the text without justifying it.

Maybe there's a bug in the code used to switch fonts?

A bisection reveals that the issue started after https://github.com/pop-os/cosmic-text/commit/e1e9fb5215daa9dbd40998e16210a6ee3a61ff1f. It doesn't seem like this change would cause this? Maybe it just exposed a previously inaccessible bug.


Small documentation fix in Url::remember() / Url::previous()

There is such explanation for $name argument in BaseUrl::remember() / BaseUrl::previous() phpdoc:

The name associated with the URL to be remembered. This can be used later by previous(). If not set, it will use yii\web\User::$returnUrlParam.

But it's not true about yii\web\User::$returnUrlParam. Actually, it will use yii\web\User::getReturnUrl() (https://github.com/yiisoft/yii2/blob/master/framework/helpers/BaseUrl.php#L319), which behavior differs from described behavior of BaseUrl methods.
We expecting null, if there are no information in $returnUrlParam, but actually due to yii\web\User::getReturnUrl() it will return Yii::$app->homeUrl.
I think that the best way is change this behavior of BaseUrl someday, but because of BC break it seems that better way is simply fix documentation.

I don't see any contradicting statements in docs. Could you send a pull request with proposed changes?

@samdark all right, I created pull request, but I had tried to avoid it 'cause of my bad English skills.

If it will be more clarifying, I also can create pull request with changes, that fits current documentation declaration, or create demonstrative tests (there are no any tests for Url::previous() as I see).

The thing is that in the end $returnUrlParam is used a result of calling a getter so I don't see a big issue there.

@samdark yes, but if there are no information in $returnUrlParam, we're expecting null, right? "It just using some predefined parameter name", documentation says, isn't it?
But we will receive Yii::$app->homeUrl, as we can see here:
https://github.com/yiisoft/yii2/blob/master/framework/web/User.php#L371
It's not null at all. It cannot be null.
...Am I still unconvincing? :)

Right. Would you like to send a pull request fixing it?

@samdark if we're talking about fixing documentation to describe such (current) behavior - I'm already send one, #13836 . There are terrible English (maybe), that's why explanation is not perfect at all, and I'm ready for fixing it.
If you mean BaseUrl::remember() / BaseUrl::previous() code fix to improve it's behavior and make it matching documentation - yes, of course, I can do this. (I vote for that.)


[VC] Make Cluster and MultiClusterController generic

This change removes vc specific method (i.e. GetSpec, and GetClusterDomain) from Cluster and MultiClusterController interfaces.  Instead, a GetObject method is added to retrieve the CRD obj. The type casting is done in the caller side when accessing the CRD obj.
Now Cluster and MultiClusterController interfaces are decoupled with VC crd, and the same code framework can be used to manage multiple super clusters.

good job 👍

good job 👍

/lgtm
/approve

/lgtm
/approve


Bug 1777337: employ k8s label value validation when creating build pod build label…

… value
@openshift/openshift-team-developer-experience FYI
/assign @adambkaplan

/retest

/test e2e-aws-upgrade

/retest

/retest

PR updated to use public k8s validation method (which I was too dense to notice before) @adambkaplan PTAL

/test unit

have green e2e's @adambkaplan

original bits cleaned up @adambkaplan

various unrelated flakes e2e-aws-builds
/retest

tests green again @adambkaplan

/cherrypick release-4.4


Search and Upload APIs

Added API Key generation
Lookup by IMDb id for torrent group and torrents
Added new Upload API reusing existing upload handlers

My English is not very good, so the expression may not be very clear(google translate mostly ).

My English is not very good, so the expression may not be very clear(google translate mostly ).

so are you translating all my English texts to Chinese? xD

No, because I can understand you. :)

Should be all done mate :)

staff PM

lgtm

lgtm

Functionally things should be okay. I didn't notice any errors in my dev container

when can i expect the api to be available in GPW site?

when can i expect the api to be available in GPW site?

Will update soon, you can follow the version date of the site footer.


dbeaver/dbeaver#19915 read values as double

Closes dbeaver/dbeaver#19915

Still reproducible  db - https://github.com/dbeaver/pro/wiki/Sample-databases#mysql-8-oracle-cloud schema test  table float
https://github.com/dbeaver/dbeaver/assets/84867187/938fc41b-ab35-4d02-ab15-77d018bbe573

verified


[FEATURE-REQUEST] Device name suffix

Hi,
to reduce my pain, when recommissioning the bridge with Alexa, I would love to have a configurable DeviceName-Suffix.
Currently I rename all devices in the Alexa App by adding " Bridge" to it. Thus I can rename the created sub devices (with random names) afterwards with the real name. This is very time consuming and part of the pain after recommisioning.
Would be great if you could add that feature. If you do not have time to do it but want that feature also, please keep that issue open. I think I understand the code good enough now to add this myself for most device types. Just do not know yet how to enhance the configuration view and will need some time to do it.

Hi,
the option is already available.

But as stated pay attention that changing it will change the uniqueid and so the controllers will see it like a new device.

Unfortunately you got me wrong. I know this options but it is for the device serial number, not the device name (column 4 in the table).
So changing line 492 from
device.name,
to
device.name  + (this.namePostfix ? this.namePostfix : ''),
where "this.namePostfix" comes from a new configuration option.

Ok I get it.

try to explain me why you need it... maybe I can figure out other strategies.
changing the device name has a tons of collateral issues in the whole code so not manageable.

Okay, let me try again to explain why, with some additional context. The only reason to use the matterbridge plugin is to bind it to alexa and be able to use voice commands.
The plugin takes the names as defined in the webapp of the device. So far so good but bad with alexa. Alexa now uses the name as given by the bridge to create a composed device with that name and some subdevices with more or less useless names like "outlet one", "light five" ...
These are the devices, that you usually want to use in a voice command. You don't want to say "Alexa turn on light five" but "Alexa turn on Spock" (lets say "Spock" was the name in the shelly device webapp).
But the name "Spock" is currently used be the useless composed device in alexa, and alexa will respond with "Spock can't do that".
So what I currently do is to rename it to "Spock Bridge" and rename "light five" to "Spock". This must be done with all devices after each recommissioning.
To avoid at least renaming "Spock" to "Spock Bridge" that suffix would help at least for the first part.
Does this help to understand the issue?

Can you explain how this suffix affects the code?
My naive thinking is to just scan for all lines with
createDefaultBridgedDeviceBasicInformationClusterServer
and do the above renaming using the the postfix.
Another approach is to let each shelly device have that name when created. In this case I can even see no side effects, even if the device name is used somewhere else to lookup or update the device?
I just learned how the plugin-config stuff works now and think I could even do that part now.

Ok,
I understand your point about naming in Alexa that are not the best user friendly feature of Alexa.
I will think about your idea to add a postfix on the name too.

I close here since we have a discussion for this.


Diagnostic/evaluation logging

This PR proposes to address several logging issues:

There are several situations in Visual Studio where loggers need to specify precisely the events that they want to receive so that efficient forwarding loggers can be created. Without more fine-grained event lists, forwarding logger creators have to rely on verbosity, which may include many events that the loggers don't need but will get forwarded.

Evaluation profiling is now governed by the project instance creator, but this means that if a logger wishes to receive evaluation profiling it has to have a way to talk to the project instance creator. This PR proposes an alternate method whereby a logger can specify that it wants evaluation profiling without having to state that up front in the build parameters.

In adding a test for the evaluation profiling, I took the liberty of doing a little syntax cleanup in the MockLogger. If that's not OK, or if it looks wrong, I can back it out, no problem. Also, totally open to any suggestions for a better way to do this.

@dotnet-bot test
Windows_NT Build for Full please

Another alternative would be to turn profiling on / off via a new Project API. I guess it depends on what you have more easily access to, logger objects, or project objects.

As it is now, it is possible for API users to create new IDiagnosticLoggers, but then the default forwarding loggers will ignore them, which would be unexpected. This means whenever users create IDiagnosticLoggers, they need to also pass in a forwarding logger which filters. Is too cumbersome? If it is too cumbersome, then some solutions might be:

ship a new DiagnosticForwardingLogger which knows how to filter based on the DiagnosticInformation enum. Users would have to use one of these whenever they use a diagnostic logger. Or maybe we could add one automatically?
Replace the current CentralForwardingLogger (forwards everything, used when no distributed loggers are specified) with a DiagnosticForwardingLogger in the cases where all central loggers are IDiagnostic ones (using the flag union)

We've talked a bit about this:
Requirements

MSBuild does need a new type of logger that specifies a whitelist of capabilities it is interested in. These capabilities need to be queriable, and then the engine would need to activate only the logging capabilities which are specified by the loggers.
these capabilities could be of two major kinds: filters (what subsets of events the logger is interested in) and features (log task inputs, log target outputs)
some capabilities make sense for specific loggers but not all. For example, performance summary is specific to the console and file loggers, but not ILogger in general. So it does not make sense to have everything in one big bucket?
there needs to be some form of backwards compatibility, where old loggers can swim with new loggers.

Implementation considerations

As a way to go forward, it's probably best to implement these requirements in incremental steps instead of all at once. But then we need to make sure the initial types are compatible with the long term needs

rather than specify all capabilities up front now in this PR, only include the ones that are actually listened to

Is a flag enum the best way to represent a set of capabilities? Since there are many classes and subclasses of capabilities, and since some capabilities are specific only to some logger implementations, having a huge single enum for everything might become unmanageable.
Backward compatibility

Ideally, it would be nice if all loggers become this new type of configurable, queriable, capability based loggers, and the engine does a set union of capabilities. I doubt we could use reflection to look at which events are subscribed to, because the loggers could have custom code to further filter events.
one option would be to translate old tasks to a set of capabilities, which probably means enabling all event types
another option would be to turn everything on if old style loggers are detected, and maybe issue a diagnostic level warning saying something better exists?

I don't think this works with out of proc nodes, because there's no mechanism to transmit the IEventSource3 settings to the out of proc nodes' LoggingService.
Out of proc nodes get the forwarding loggers via their LoggerDescriptions, as sent from the BuildManager when a node is created.
One way to do it is to put the serializable state of LoggingService (profile evaluation and log task inputs for now) in a separate data class which implements INodePacketTranslator and make it a field of NodeConfiguration. That way the OutOfProcNode can use it to instantiate its logging service.

@cdmihai You're correct, this doesn't work for out of proc. It seems to me that the simplest way to make it work is to mirror what happens for everything else -- the ConfigurableForwardingLogger takes a property that controls whether or not it sets the properties, just like it takes properties that control whether or not events are forwarded.

@cdmihai Let me know what you think about the changes to the forwarding logger. Also, I'm happy to add a test for the task inputs, is there a good model test that I can use as a base?

Regarding the log task inputs test, as far as I can tell, we have no test for it :(. You can use the BuildManager tests as a test example to force out of proc nodes, and then use the mock logger to assert task inputs were logged. This would be useful to test for event profiling as well. As for the test class, you can create a new one.
Regarding out of proc logging, I don't think that persisting the settings just in the ConfigurableForwardingLogger is sufficient, because not all logging scenarios end up using the configurable logger:

Degenerate case: when no loggers are subscribed, MSBuild still creates a ConfigurableForwardingLogger to get ProjectStarted / Finished events from the out of proc nodes, which are needed by the scheduler in the central node.
When all loggers are central loggers (no IForwardingLoggers), then there is no ConfigurableForwardingLogger used. Rather, in this case MSBuild creates a CentralForwardingLogger which forwards all events back. For IEventSource3, maybe it would be better to just delete the central logger and replace it with a configurable one which has everything turned on.
When all loggers are distributed loggers (pairs of central and forwarding loggers), then MSBuild uses the user forwarding loggers (which can be of any user defined type) on top of which it adds a minimal configurable logger as in case 1. (because it can't be sure the forwarding loggers would forward project started / finished). This means that if there's distributed loggers setting state in their IEventSource3, there's no mechanism in MSBuild to serialize that state. This means that every user with custom forwarding loggers needs to duplicate the changes you did in ConfigurableForwardingLogger. I'd rather we make a mechanism where MSBuild handles this.
When there's both central loggers and distributed loggers, then MSBuild mixes 2. and 3. which is the most inefficient thing one can do, as it leads to rampant event multiplication over the pipes.

I think there's two main ways to go:

Loggers are responsible to serialize IEventSource3 state: In both the central and out of proc nodes, the logging service aggregates it's state from the loggers. Not sure how to achieve this with user custom loggers, as they only have an interface to implement, and sadly interfaces don't have default implementations. Maybe the BuildManager can create yet another configurable logger to capture and aggregate the state from all user distributed loggers? But this leads to event multiplication and worse perf.
LoggingService is responsible for serializing IEventSource3 state. Since the LoggingService knows the final state after querying all loggers, it can transfer that state over the pipe to the out of proc nodes' LoggingServices. The downside here is that the out proc nodes wouldn't be able to tell which logger asked for something, they'd only get the aggregated result. But I don't think we'll ever need that level of resolution.

@cdmihai I updated the PR based on our conversation, can you take a look? Also, should this PR be targeted against master or vs15.8?

@dotnet-bot test OSX10.13 Build for Mono please

@dotnet-bot test Ubuntu14.04 Build for CoreCLR please

@panopticoncentral Mono builds aren't passing at the moment and won't block your merge.

@rainersigwald What about the CoreCLR for Ubuntu14.04? It says it's triggered but nothing happening...?

@dotnet-bot test Ubuntu14.04 Build for CoreCLR please


Issue while scrolling down in the grid with grouping

While expanding one group when all groups are in collapsed state, I am getting lesser rows in the group than it actually contains. This seems happening bcz of virtual scrolling.
http://mleibman.github.io/SlickGrid/examples/example-grouping
Steps to reproduce:

choose 500k rows
Collapse all groups
Expand one group in bottom of grid view (current viewport)
Expand one group from top
Scroll down

You can see lesser rows in the group than it contains. And its working good if we scroll little more and scroll up back to the previous position.

There have been a number of grouping bugs identified and fixed in my repo, give it a try: https://github.com/6pac/SlickGrid
You should be using that repo anyway, the MLeibman branch is getting very out of date now..

Thank you @6pac ..


Expo managed react native app

Hello everyone,
I couldn't find this information anywhere else, I think it's maybe not available but I'm looking for a way to use Pusher in my expo managed react native app. When I try to install it with npm install @pusher/pusher-websocket-react-native, and run the app, I got an error related to pod install. I tried to run it, and got a different error saying no podfile' found in the project directory`

@benw-pusher
Oh, this is an expo managed react native app, so there's no ios directory.

Apologies, your screenshot with the complete error message didn't load when I last commented.
To solve the 'this package doesn't seem to be linked' error you need to follow the build instructions at https://docs.expo.dev/workflow/customizing/#adding-custom-native-code-with-development-builds. See https://github.com/pusher/pusher-websocket-react-native/issues/108 for more info on this.


logseq: add aarch64-darwin target

Description of changes
logseq is packaged, but not for aarch64-darwin! I went ahead and did so
Note, though, that the developers don't sign the .app using xcode. As such, MacOS (at least Ventura) will quarantine this app when downloaded via Nix (when downloaded/installed via .dmg directly, MacOS will just warn the user that the publisher can't be verified). I couldn't find a way to work around this, so 🤷
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

hi, so I just released ( was reviewing one of PRs) that there are 3 PRs releated to adding logseq darwin
https://github.com/NixOS/nixpkgs/pull/268249
https://github.com/NixOS/nixpkgs/pull/248090
https://github.com/NixOS/nixpkgs/pull/191091
can I ask you to collaborate on a new PR ? feel free to reach out for help
looking forward on getting this merged !

Closing as #331824 has been merged, which adds darwin support


[Manila CSI] add support for CephFS snapshots

Current situation:
Currently, CephFS backends in Manila are limited to only creating snapshots - Manila does not offer create_share_from_snapshot_support capability for CephFS just yet. From CSI side of things, the spec doesn't allow advertising CREATE_DELETE_SNAPSHOT without supporting snapshot volume source in CreateVolumeRequest - which means that csi-manila must forbid CephFS snapshots altogether.
Proposed solution:
Given this is one of the more sought-after features, csi-manila tries to fill out this gap with in-driver functionality (i.e. a compatibility layer) until it's supported natively by Manila. The driver checks for Manila capabilities by reading extra specs from the share type of the source share. Based on those the driver either chooses to use Manila's native support or a compatibility layer, if one exists.
In order to create a share from a CephFS snapshot, the data needs to be copied over from the snapshot into a new share. CSI Manila will therefore create a blank (destination) share, mount it, mount the source share containing the snapshot and copy the data to destination using rsync.
Implementation:

https://github.com/gman0/cloud-provider-openstack/tree/csimanila-compat-caps : basis for recognizing Manila capabilities and using compatibility layers when needed
https://github.com/gman0/cloud-provider-openstack/tree/csimanila-cephfs-snap-compat : create_share_from_snapshot_support compatibility layer for native CephFS

The code is finished and ready for PRs. I can post those right after https://github.com/kubernetes/cloud-provider-openstack/issues/714 is done.

/kind feature

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale
This is still ongoing...

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle rotten

/remove-lifecycle rotten

/remove-lifecycle stale


Ability to select git branch from the user interface

Describe the solution you'd like
Currently the only way for a git branch to be selected is through the deployment parameters (karavan.git-branch). This does not provide a lot of flexibility - the only way to switch a branch is through a re-deployment of Karavan (or re-config / restart if working locally).
This feature may need to be extended to be actually quite a bit more complete (maybe entire repository management). Repository management is a much bigger ask, however, as it requires the storage and handling of secrets.
Variant
Web Application
Container Management (if applicable)
None
Operating System (for VS Code Extension)
None

Apache Camel Karavan was specifically designed to simplify the development of integration microservices. Initially, Karavan supported multiple repositories to allow for separate project management. However, this approach made the project creation process cumbersome and time-consuming. It required creating separate repositories, generating and uploading keys, and configuring each repository in Karavan.
To streamline this process, Karavan now uses a single repository per instance. This change significantly reduces the complexity and time involved in project creation, allowing integrators to create and start implementing integration projects in just two clicks.


Doesn't handle HTTP response code 204

According to the VT documentation at https://www.virustotal.com/en/documentation/public-api/ HTTP response code 204 is the "API request limit reached" response code, not 429.  When 204 is returned, it's raised as an Unknown Server error. instead of Virustotal limit reached. Try again later.

I merged your pull request. Does that solve this problem for you?

Hey, thank you for your quick response and considering my pull request.
It certainly does help.  I’ve had to go into my application and implement some self-throttling and this will help.
Have you considered raising custom errors instead of StandardError so that a developer could more easily handle the various exception scenarios?  So instead of just raise “Virustotal limit reached. Try again later” it could be raise VirusTotalLimitError.new().  With this change, code that uses uirusu could handle that error specifically, and throttle their API calls.
I’d be happy to make a pull request for it if you’d like. :)
—JP
From: Jacob Hammack
Reply-To: arxopia/uirusu
Date: Monday, August 31, 2015 at 1:27 PM
To: arxopia/uirusu
Cc: Jason Poll
Subject: Re: [uirusu] Doesn't handle HTTP response code 204 (#3)
I merged your pull request. Does that solve this problem for you?
—
Reply to this email directly or view it on GitHubhttps://github.com/arxopia/uirusu/issues/3#issuecomment-136454274.

Feel free to submit a pull request. I haven't done much with the code
lately.
-Jacob
On Monday, August 31, 2015, Jason Poll<EMAIL_ADDRESS>wrote:

Hey, thank you for your quick response and considering my pull request.
It certainly does help. I’ve had to go into my application and implement
some self-throttling and this will help.
Have you considered raising custom errors instead of StandardError so that
a developer could more easily handle the various exception scenarios? So
instead of just raise “Virustotal limit reached. Try again later” it could
be raise VirusTotalLimitError.new(). With this change, code that uses
uirusu could handle that error specifically, and throttle their API calls.
I’d be happy to make a pull request for it if you’d like. :)
—JP
From: Jacob Hammack
Reply-To: arxopia/uirusu
Date: Monday, August 31, 2015 at 1:27 PM
To: arxopia/uirusu
Cc: Jason Poll
Subject: Re: [uirusu] Doesn't handle HTTP response code 204 (#3)
I merged your pull request. Does that solve this problem for you?
—
Reply to this email directly or view it on GitHub<
https://github.com/arxopia/uirusu/issues/3#issuecomment-136454274>.
—
Reply to this email directly or view it on GitHub
https://github.com/arxopia/uirusu/issues/3#issuecomment-136484471.

--
Jacob Hammack
<EMAIL_ADDRESS>(210) 355-0036
http://www.hammackj.com

I think this got resolved by your PR. If not please re-open.


Improve regexp equivalent class

Added more characters matching regexp equivalent classes [[=x=]].
Also removed REGMBC() and CASEMBC() macros that are no longer
relevant given that the multi_byte feature is now always true.

Is this ready to include now?

@brammool wrote:

Is this ready to include now?

Yes.  I rebased.  Failing tests in CI look unrelated (flaky test Test_out_cb on mac).


Native removed from 8.x?

Getting following error if native is set in hooks
rangeValue.replace is not a function

they're native by default, the flag doesn't exist anymore, essentially you're trying to animate a boolean, that's why it complains.

@drcmda I suspected that thanks :smile:

Please add this info to the release notes, and maybe also a native?: never to the typescript definition, so it will prevent people from using it.

Still confused about this issue. I get the error:
rangeValue.replace is not a function when using React Native Web.
import { useSpring, animated } from 'react-spring'
import { useDrag } from 'react-use-gesture'

const AnimatedView = animated(View)

function DraggableCard() {
  const [{ x, y }, set] = useSpring(() => ({ x: 0, y: 0 }))
  const bind = useDrag(({ down, movement: [mx, my] }) => {
    return set({ x: down ? mx : 0, y: down ? y : 0 })
  })

  return (
    <AnimatedView {...bind()} style={{ x, y }}>
      <Text>Hello</Text>
    </AnimatedView>
  )
}

Same error when I import from react-spring or react-spring/native. I'm using Expo Web.

@brunolemos

Try with v9 and open a new issue if you're still having trouble. Thanks! 👍
npm install react-spring@next


getDuration() returning Infinity for webm videos

Be sure to search for your issue before opening a new one.
Current Behavior
handleDuration = (duration:any) => {
this.setState({ duration })
}
Returning  Infinity as duration
Expected Behavior
Duration in seconds must be returned
Environment

"react": "^17.0.1",
Used with Ionic framework

Hello, you should set video current time to the finally (1e101). and then set video current time to 0, wow,you can get duration, just for webm format,questionVideoDom.current.seekTo(1e101, 'seconds');                       questionVideoDom.current.seekTo(0, 'seconds');


Handle JSON decode error

Prevents client crash, though root server cause needs to be addressed.
@benghaziboy

lgtm

Hey Mike, Looks like this one can be closed as it seems to be handled by some other changes I made recently. I'm gonna close it unless you see a reason otherwise.
Bless, Cam

That's fine -- the client really should be validating the JSON but not high priority now


build: update libuv version

@nodejs/tsc

Anything that we should do about this in Node?

I'll update the core repo once this release goes out.


Remove cards

This PR fixes #12118
We're currently using them extensively in the ML extension, so once they're removed there we can go ahead and merge this.

Closing old PRs


wirb requires Ruby version ~> 2.0.

According with Readme Wirb supports the following rubies: 2.2, 2.1, 2.0, jruby, rubinius.
but gemspec only supports Ruby ~> 2.0, see https://github.com/janlelis/wirb/blob/master/wirb.gemspec#L12
please make it >= 2.0

Hey @DanielBlanco,
please clarify which Ruby version does not work with the current WIRB.
~> 2.0 should cover 2.0, 2.1, as well as 2.2 and newer (below 3.0)

Closing, it works fine.
Sorry for the troubles.


Font size evaluation

There is a request to increase the base/standard text font size to 14pt for ALM.  We need to evaluate how this would affect the UI, and how it would affect users moving from one Red Hat product to another.  The goal is to consider whether this change would create a jarring experience for cross-product users especially, as the is the main reason to maintain consistency.
Verification Criteria:

We understand which areas of the current ALM design would change with a font increase, mock it up, and define anything that should not follow base font that previous had if needed
Mock up/prototype of moving from ALM with 14pt base font to another product UI with 12pt base font to "test" cross-product font change.  OpenShift should be used for test.

I would defer to some of the visual and PF folks on this. Are we also
staying with the same font, or is that changing too, as that cold determine
more of the impact than changing the size of the same font.
My 2 cents based on having to recently address this in a product is... if
the font is the same, this should not present a huge problem across
product, as most of our screens are not yet too content heavy. There will
be lot's of spacing tweaks that will happen, and depending on how our
interface is crafted will determine how vast the tweaks are. The left pane
on the planner is at the most risk.
It will surface if we have all of our overflow stories solidified for sure,
which is good to see early on.
Are we also increasing our base screen size along with increasing the font
size?
-Monica
On Thu, Feb 23, 2017 at 7:33 PM, catrobson<EMAIL_ADDRESS>wrote:

There is a request to increase the base/standard text font size to 14pt
for ALM. We need to evaluate how this would affect the UI, and how it would
affect users moving from one Red Hat product to another. The goal is to
consider whether this change would create a jarring experience for
cross-product users especially, as the is the main reason to maintain
consistency.
Verification Criteria:

We understand which areas of the current ALM design would change
with a font increase, mock it up, and define anything that should not
follow base font that previous had if needed
Mock up/prototype of moving from ALM with 14pt base font to another
product UI with 12pt base font to "test" cross-product font change.
OpenShift should be used for test.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ux/issues/218, or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwqwifhjXLz6oLwAFl7FqXTwdaYnRvks5rfiVmgaJpZM4MKrwc
.

I'm curious what the issue is that we would address by increasing the font size.  Is it in preparation for if/when PF increases the base text size?  Is there an accessibility requirement?  Is it so the UI will show better in demos?  Knowing what is driving the request will help us provide an appropriate solution.

Good question... is it aiming for higher res systems? If so we should also
be increasing our base screen dimensions....
On Fri, Feb 24, 2017 at 11:58 AM, Sarahjane Clark<EMAIL_ADDRESS>wrote:

I'm curious what the issue is that we would address by increasing the font
size. Is it in preparation for if/when PF increases the base text size? Is
there an accessibility requirement? Is it so the UI will show better in
demos? Knowing what is driving the request will help us provide an
appropriate solution.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fabric8io/fabric8-ux/issues/218#issuecomment-282343834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwq1l1jEhgLiHpM_dn6tQVW-pyflKlks5rfwwhgaJpZM4MKrwc
.


On focus make dot active

Hi!
My challenge is:
When the dot has focus via keyboard tab - make the dot active so the user can start navigating the slider without having a mouse.
I guess my question becomes: is it possible to through my focus event listener make the dot active? I've tried simulate a click in my event listener without success.
This is how the code looks:
<div @focus="myClickEvent" tabindex="3" slot="dot" slot-scope="{ value }" class="vue-slider-dot-handle dot-outer">
         <span class="dot-inner" ref="myBtn">
                {{ value }}
            </span>
</div>

myClickEvent($event) {
  console.log('Dot is now in focus');
  const elem = this.$refs.myBtn
  elem.click() // Does not work. Can we call some other function to make the dot active?
}

Try this
this.$refs.slider.focusSlider = 0
this.$refs.slider.focusFlag = true

Works like a charm, thank you!!

@NightCatSama  @creativejeff  Where does this code go? There's absolutely no context.

Hey @3zzy , it goes to the function you've binded to the element. In my case it goes to my focus event conveniently called myClickEvent()
myClickEvent($event) {
  this.$refs.slider.focusSlider = 0
  this.$refs.slider.focusFlag = true
}

@3zzy If you are using the v3.x version, you can use the focus method.
https://nightcatsama.github.io/vue-slider-component/#/api/methods?hash=focusindex

@creativejeff @NightCatSama  Great, thanks, that helped! Just wondering how to make it work for a range slider (two handles)?

@3zzy The first parameter of focus is the index of the slider.


New Maintainer Wanted

Greetings, all!
I know a lot of you are wondering about the status of this project and are perhaps (and understandably) annoyed about turn around time and status of issues.
First, I still feel the use cases and implementation pattern of this module (and ng-idle) are distinct and useful from other solutions out there. However, I have an admission to make: I've been cheating on you (the Angular community). Most of my work in the past year and a half has been with React. This means that I'm just not invested into Angular like I might have been in the past, which I suppose makes me a bit of a liability to the project. So, in the short term, it's a good idea for the project to be handled over to a new lead contributor that can keep it maintained and grow it alongside Angular.
Second, I mentioned my interest in the architecture. So much so that I've replicated it a few times now (original was jQuery, then AngularJS, and then Angular... I've even got a stripped down version for React). I'm still interested in it! However, I'm thinking that maybe we can create a new org (IdleJS or something like that) where the core functionality is defined as vanilla JS, and we have framework-specific adapter modules for things like Angular and React. That way the entire community can enjoy a consistent implementation pattern for these use cases, and fans of a particular framework can concentrate on adapting it for their environment. I suppose the biggest hitch would be whether or not we can make a consistent core that works for popular frameworks that isn't encumbered, dependency-heavy, or too large.
Anyways, I'm interested to hear what you think. Also, those that are interested in helming the current project, definitely speak up.

Hey. Although IdleJS is a great idea (not kidding, having ideology and architecture of solution and multiple implementations are just great in my books) I do think you should handle over the control if you lack the time or desire to continue. I saw there's PR with updated required for use with version 6 of RxJS and Angular and there's no response for some time already.
So, my vote is — get org going, while handling keys to someone willing to too.

@plisovyi Yes, that was my intention was regardless, hand over ng-idle as-is and work on a cross platform version later.

I'd be more than willing to help, not necessarily as maintainer, but I'd love to contribute as best I can

Hey, all. I just wanted to bump this up again to get visibility. I had been working with a group to take over maintenance but I think we both fizzled out and the main contact I had left that original group.

Thanks for stepping up! Fortunately i think version updates aren’t too bad. I believe the CLI has a task to handle deps for you. The rest is just dealing with breaking changes and releasing. We should also consider Greenkeeper or something to automate this and relieve some of the burden.
We can discuss in an email or chat on how to proceed if you’re still interested.

Greenkeeper is losing all support. It's moving its current userbase over to https://snyk.io/. Would rather using that over something that's no longer accepting no users haha.

Whoops, well fair enough. Well anyway, let me do a little housekeeping here, then I think perhaps we can work out a targeted list to attack with you added as a maintainer, then figure out what to do what you’ve got a handle on it.

Sounds good! Looking forward to this (=
I'm excited to be helping the open source community.

@moribvndvs I'm interested in helping to maintain this library as well. Currently working with a client who has a need for this library in an Angular 11 SSR scenario. Beyond that, I have been looking for an open source project to contribute to in my spare time and I have ~5 years of real world Angular experience to bring to the table.

@moribvndvs I'm interested too for helping to maintain the library.
We use your library in our framework NationalBankBelgium/stark and we're currently updating it to Angular 12 😊
I have ~5 years of Angular experience.

Hey sorry about my negligence to the interested parties. I'm really glad to hear about the interest in maintaining the project. Full disclosure: I've never handed off maintenance in an OSS project before, so bear with me.
Here are some general thoughts I have:

I would prefer not to just transfer the whole repo to someone else. My concern there is purely that if that person no longer wants to work on the project, it'll be hard to get it back and the project could get abandoned. My preference is to keep on as an owner in its current place and provide guidance on the history and spirit of the project, but get out of the way of maintainers who would otherwise operate self sufficiently. I am open to the idea of moving it to an ng-idle organization as a neutral ground, as long as I can still be an owner and not get kicked out (again, purely just so the project doesn't get abandoned and lost).
Multiple maintainers sounds like a good idea at this point, to share the load. I think we probably still need a lead maintainer. I'm not sure how to go about this in a fair way other than asking for people to a) state whether or not they're interested in being lead maintainer b) pick or elect from those still interested based on 1. OSS project maintenance experience 2. ability to commit to the role 3. Angular experience 4. ng-idle project experience. It maybe feels like I'm overthinking it, but I do feel it's a good idea to make a solid choice in this matter before I hand over keys to publish packages. Thoughts?
Once I can get a feel for who's the lead vs who's a maintainer, here are the things I think need to get done:

Ensure lead can manage repo settings, CI/coverage, and publish to npm
Get releases for the newer versions of Angular out
Fix high priority bugs
Update demos (move to in-repo so they're up to date and easier to maintain) and documentation
Get snyk or whatever working to automated updating deps and submitting PRs to help alleviate the burden

Hello,
I think it's a good idea that you keep the ownership on the project for multiple reasons. This can also be done through an "ng-idle" organization 😊
For my part, I can help to implement CI/CD with GitHub Actions, coveralls, dependabot, snyk, SonarCloud,... as I have some experience with them. I'll do a first implementation and share it through a PR this week or the week after.
For the rest, I can help to update the project with Angular updates with other people 👍

I'm interested in being the lead maintainer. I maintain a couple of my employer's own private npm packages so addressing high priority bugs, documenting everything, and publishing to npm is peanuts to me. =)

Hey @bh3605 @worksoncloud @moribvndvs
As promised last week, I created a 1st PR to switch from Travis CI to GitHub Actions. Could you have look? 😊

@worksoncloud I've kicked this off by adding you as a collaborator. I'm not ignoring everyone else that volunteered, I just don't want to throw everyone at it at once and create chaos.
I did cover above the first things I think need to be tackled to get this moving, copied again for your convenience:

Ensure lead can manage repo settings, CI/coverage, and publish to npm

Get releases for the newer versions of Angular out

Fix high priority bugs

Update demos (move to in-repo so they're up to date and easier to maintain) and documentation

Get snyk or whatever working to automated updating deps and submitting PRs to help alleviate the burden

I created a Discord server to facilitate discussions needed to get these things done, hopefully that's acceptable. Just join and shout out in #general if you were one of the collaborator volunteers and I'll add you to the collaborators channel.
https://discord.gg/6ndEd7tf

Thanks, @SuperITMan for the GH Actions, nice to have that taken care of.

@moribvndvs @worksoncloud
Could you add me as collaborator too? 😊
Like this, I could configure correctly GitHub Actions, Snyk, Dependabot...

@moribvndvs Hi, did you move forward with idleJS ? Looks like to be a great idea btw.

Currently using this in my company application and found this project interesting, can I become a maintainer?

Hi @moribvndvs 👋
I hope you are doing great! If you are still looking for new maintainers i'd like to become one. Just wanted to first ask for guidence about what to do around the project. Tried to join the discord server but link was outdated I guess :)
I've been working with Angular 2+ since 2016 and in the last 1-2 months I've been looking into Angular projects to contribute to and give back to the community somehow  more actively, but I've failed to find good active projects and I'm not confident enough (yet) to build something from scratch 😀
If you'd be okay to move forward and guide me on what to the next I could work on things at least 5-6hrs per week

Wondering what the status is on this, has new maintainers been found?
There's a couple PR's open that would be very nice to fix, mainly one that addresses when browsers/tabs are put to 'sleep' and has been open for 4 years now
Also support for Angular 16

@moribvndvs help is still needed?


pull request for e2e test at 01/11/2017 07:15:10

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


Keep screen on when using screen saver

The screen should remain on when using the screen saver.  Currently a third party application is required to keep the screen on.   Add FLAG_KEEP_SCREEN_ON flag and move screensaver from a dialog to an activity (required for flag to work).

Added in v0.8.0

Have to press screen 3 times to get out of screensaver mode..

@mvoosten you need to fill out an issue in the issue tracker if you think you've discovered a bug.


Tabler Icons not showing correctly

I downloaded tabler icons (https://github.com/tabler/tabler-icons/releases/download/v1.78.1/tabler-icons-1.78.1.zip), unzipped it, and put the "icons" folder (where SVG icons are located) in the plugin folder (.obsidian/plugins/obsidian-icon-folder/icons/). The settings work fine and all 2160 icons are detected, but they don't show up correctly:

I tried changing the theme to default one, but no luck 😕
What could be the problem?

I found the problem: some attributes are being deleted:
For example, bell.svg:
Actual Icon SVG
<svg xmlns="http://www.w3.org/2000/svg" class="icon icon-tabler icon-tabler-bell" width="24" height="24" viewBox="0 0 24 24" stroke-width="2" stroke="currentColor" fill="none" stroke-linecap="round" stroke-linejoin="round">
  <path stroke="none" d="M0 0h24v24H0z" fill="none"/>
  <path d="M10 5a2 2 0 0 1 4 0a7 7 0 0 1 4 6v3a4 4 0 0 0 2 3h-16a4 4 0 0 0 2 -3v-3a7 7 0 0 1 4 -6" />
  <path d="M9 17v1a3 3 0 0 0 6 0v-1" />
</svg>

Obsidian Output
<svg width="24px" fill="none" height="24px" viewBox="0 0 24 24">
    <path stroke="none" d="M0 0h24v24H0z" fill="none"></path>
    <path d="M10 5a2 2 0 0 1 4 0a7 7 0 0 1 4 6v3a4 4 0 0 0 2 3h-16a4 4 0 0 0 2 -3v-3a7 7 0 0 1 4 -6"></path>
    <path d="M9 17v1a3 3 0 0 0 6 0v-1"></path>
</svg>

Seems like all attributes starting with stroke- are being deleted. (class and xmlns aren't important here, so no problem)

[  if (foundIcon) {
let fileContent: string;
if (typeof foundIcon.svgPath === 'object') {
const doesStrokeExists = foundIcon.svgPath.filter((path: any) => path.match(/stroke=".*"/g)).length !== 0;
fileContent = <svg width="16" ${doesStrokeExists ? 'fill="none"' : 'fill="currentColor"'} height="16" ${         foundIcon.svgViewbox.length !== 0 ? foundIcon.svgViewbox : 'viewbox="0 0 24 24"'       }>${foundIcon.svgContent}</svg>;
} else {
fileContent = <svg width="16" height="16" ${foundIcon.svgPath.includes('fill=') ? '' : 'fill="currentColor"'} ${         foundIcon.svgViewbox.length !== 0 ? foundIcon.svgViewbox : 'viewbox="0 0 24 24"'       }>${foundIcon.svgContent}</svg>;
}
icon = fileContent;
}
return icon;
};](https://github.com/FlorianWoelki/obsidian-icon-folder/blob/f3915a626f80349fbcb91acde1a2d2c5750b625a/src/iconPackManager.ts#L368-L384)

I'll take a look at it as soon as I have the time. Thank you for the detailed analysis!

This is fixed in the newest release. Thanks for reporting!


I can't watch anime

When I click on the anime I wanna watch it say "No link found"
When I try to get into the Anime page (clicking on the info icon) its says "Error loading anime page"

AllAnime links aren't working so any favorites you've got using that site won't work until the dev updates the app, but you're still able to watch anime from gogoanime. Just search for the anime you want and switch to gogo at the top of the search page. But you're either gonna have to re-favorite everything on gogo or wait for an update.
There haven't been any updates in a while so I'm not sure if it's been abandoned or what.
But there's two other amazing apps i highly recommend checking out:
CloudStream (for streaming regular movies, series AND anime. Almost daily updates on the beta version)
https://github.com/recloudstream/cloudstream
Saikou (for streaming anime and reading manga, it's amazing. You should get a anilist or MAL account to get the most out of the app since it lets you organize what you're watching, plan on watching or completed. It also tracks what you've watched and updates everything to your account automatically)
https://github.com/saikou-app/saikou
Personally I'm currently using cloudstream for regular movies and series, and I'm using saikou for anime


fix: prevent audio source reset in disabled mode

Suneditor in disabled (read-only) mode.
Before:

After:

P.S. @JiHong88 Another solution was to add e.stopPropagation() to audio element onInput(e) on its creation, but I thought that in the future this problem may affect other plugins, or we may need to handle some events in onInput_wysiwyg, so I decided to place handler in onInput_wysiwyg. You may reconsider it ;)
P.P.S. Cool 'editMode' button I have, don't you think so? ;)

@SystemChanger Sorry, for the late reply.
First of all thanks for your contribution.
I checked too late.
This is a really useful.
Can you please re request PR at current master version?
All PR are conflicting with the master version.


Fix misnamed coveragerc file

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+53.3%) to 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
53.3%

Covered Lines:
63

Relevant Lines:
63

💛  - Coveralls


Pulldown fixes and creation of transformation methods

This is misnamed... it became more than a quick fix following comments from Gail. In brief:

vioscreen survey template IDs were being fetched but we don't have those data in the database right now so that "presented problems"
there is at least one fermented food survey that appears to be somehow a duplicate, so a duplicate protection was put in place
the missing value used was the wrong one
column names were a mix of upper and lowercase
the scientific_name value for humans was fixed
transformation methods to create age_years, age_cat, and more were added

Thanks, @AmandaBirmingham!


use android key store

Description:
closes #45
closes #204
Tasks:

[ ] Build CI Runs
[ ] Code Analysis up to standards

abandoned


Never ending sync loop when closing app while syncing

Couldn't find any related, already reported bugs. I'm sorry if I missed something!
Expected behavior
When the app is closed while manually syncing all accounts, the sync should still be completed or interrupted on closing the app.
Actual behavior
Syncing is never completed/is stuck, notification doesn't go away, new e-mails are not found -> app needs to be shut down hard in settings
Steps to reproduce

Open app
Go to Unified Inbox/All messages
Swipe down/Click on sync button
Close app

Environment
K-9 Mail version: 5.600
Android version: 9
Account type (IMAP, POP3, WebDAV/Exchange): IMAP on all accounts
--
I'll try to attach a debug log later today.

k9-log.txt
Debug Log. I've put  wherever my actual adress appeared.

Looks like K-9 Mail is trying to listen to new messages in a folder that doesn't exist on the server. Go to the folder list screen and refresh the folder list.


hiding Aragon DAC job listings

these 2 positions are filled for the time being

Closing due to changes already made in https://github.com/aragon/aragon-wiki/commit/817577d6a2d521956ee0ef8163b28e297fad3ed6

hi tatu! @Smokyish
Its true that most places this was already fixed, but the problem remains that you can see the PM and UX role from the "Jobs Overview" page. I have just gotten applications in the past 2 days from somebody who just saw it on the wiki. So I hope you can merge this!


gas price issue on registration

When executing fdp-cli account register [accountName]
The following error will be thrown:
ERROR Failed to register account: insufficient funds for gas * price + value

When executing fdp-cli account register [accountName] The following error will be thrown: ERROR Failed to register account: insufficient funds for gas * price + value

On the account with which there is a registration of finances?

yeah, my bad, it was an account that was not funded before


Window scrolls while selecting text, causing selection to jump

I've never seen this before, so I suspect this is regression in 1.9.0.

VSCode Version: 1.9.0
OS Version: Windows 10 Pro

I'm editing a markdown file that contains both text and code blocks. I have the preview open on the right (split screen). When I drag my mouse to highlight text in the editor on the left, it randomly scrolls, causing my selection to go the opposite way to where I was dragging from the start point.
It's really random; it took me 10-15 drags to repro for this GIF, however it seemed to be happening more frequently when I wasn't trying to repro.
I don't know how well this GIF will illustrate the issue, but I start dragging from line 217 (items.sort();) and drag upwards. After my selection gest to line 211, the editor suddenly scrolls down, (across two frames of this GIF) resulting in my selection running from line 217 to 227 (the opposite direction).

I don't seem to be able to repro without the preview open; so wonder if it may be related to the new feature that tries to sync the windows (though I don't think it's expected that the left window ever scrolls for this?).

I just realised that it is intended that the left pane can be scrolled - scrolling the left pane causes the right to scroll.
So I suspect what's happening is cursor is being moved around on left pane, which is causing the right pane to scroll, which for some reason is then causing the left pane to scroll.

Looks like markdown scrolling is causing this?


Runner.xcodeproj vs Runner.xcworkspace

There's a Runner.xcodeproj and a Pods/Pods.xcodeproj now. Should we change all the documentations that refers to Runner.xcodeproj to refer to Runner.xcworkspace instead so that the user can build directly from xcode if needed?
cc @cbracken

Yeah. The workspace is the way to go.

Cool, thanks

Just ran into this issue too. I had an issue running on an attached device (not enough device management trust), so flutter tools suggested opening Runner.xcodeproj and running from within there. That failed because of linking issues with libPods-Runner.a. Opening Runner.xcworkspace instead made it work. Thanks to @jakobr-google for unblocking me here :)


Fixing menu page

The menu page does not look good and could use some improvement.

Please assign me to fix this issue.

@Harshitha-Annam present menu page is fine not required.


Bumping jackson.version to 2.12.1 because the used version is vulnera…

…ble to CVE-2020-28491
More information here: https://github.com/FasterXML/jackson-dataformats-binary/issues/186

@googlebot I signed it!

@googlebot I signed it!


Publish Extension on Open VSX Registry

Let's also allow the extension to be consumed by other VS Code like IDEs like Theia or VSCodium.

Raised an issue: https://github.com/open-vsx/publish-extensions/pull/633

Released https://open-vsx.org/extension/stateful/issue-explorer


Fix Helm chart default configuration

Why are these changes needed?
There are 3 problems in current helm chart default configurations.

[Q1] There is a mismatch between labels in ray-head pod and selector in ray-head ClusterIP service. See https://github.com/ray-project/kuberay/issues/495 for more details.

[Solution]: I updated the value of nameOverride from ray to kuberay as mentioned by @jeethridge.

[Q2] When I solved Q1, I found dashboard could not be launched successfully. The root cause is that dashboard_agent would round down the CPU request config (200m) to 0.

[Solution]: Increase CPU request from 200m to 1.

[Q3] After I solved Q2, the dashboard still could not be rendered on my browser. The root cause is that the image rayproject/ray:latest points to a very old version. Thank @hckuo for pointing this out!

[Solution]: Updated the image

Related issue number
https://github.com/ray-project/kuberay/issues/495
Checks
# Step1: Install operator
kubectl create -k "github.com/ray-project/kuberay/ray-operator/config/crd?ref=v0.3.0&timeout=90s"
helm install kuberay-operator --namespace ray-system --create-namespace $(curl -s https://api.github.com/repos/ray-project/kuberay/releases/latest | grep '"browser_download_url":' | sort | grep -om1 'https.*helm-chart-kuberay-operator.*tgz')

# Step2: Install ray-cluster
cd helm-chart/ray-cluster
helm install ray-cluster --namespace ray-system --create-namespace .

# Step3: port-forwarding
kubectl port-forward -n ray-system services/ray-cluster-kuberay-head-svc 8265:8265

# Step4: Type <IP_ADDRESS>:8265 in your browser to check dashboard. I added a screenshot for dashboard below.

# Step5: Submit a job to your ray cluster. The result is as shown in the following screenshot.
ray job submit --address http://localhost:8265 -- python -c "import ray; ray.init(); print(ray.cluster_resources())"

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

cc @DmitriGekhtman


Consider adding support for https://github.com/eto-ai/lance

To quote the GitHub description:

Alternative to Parquet. 100x faster for random access, automatic versioning, optimized for ML data. Apache Arrow and DuckDB compatible.

https://github.com/eto-ai/lance

Consider it considered 🙂
Typically for a format to be included in the dask library itself we'd want to see lots of people asking for it.  If folks happen upon this issue and want Lance support I recommend adding a 👍 to the opening comment.
Until then, it's also pretty easy to create a dask-foo package that adds support as a third party library. This is, for example, what we did with dask-snowflake.  Once third party packages get enough use outside of the main repository then it's easy to bring them in with confidence.


[RNMI] What is the impact of MNRET instruction on the value of MNSTATUS.MNPP?

Should .MNPP be set to the least-privileged supported mode on MNRET instruction as .MPP on MRET instruction?

Because the spec is silent on the matter, the implication is that MNPP is left unchanged.

@aswaterman Thanks for confirming this!


Add CSRF_COOKIE to prevent csrf when using JWT_AUTH_COOKIE

To prevent Cross-Site Request Forgery when using JWT_AUTH_COOKIE, the csrftoken cookie will also be set when issuing the JWT authentication token.

I think this changes are not enough for CSRF protection when JWT_AUTH_COOKIE option is enabled.  Your patch adds csrf cookie, but looks like it's value will be never checked, because django-rest-framework explicitly wraps every view in csrf_exempt().
https://github.com/encode/django-rest-framework/blob/master/rest_framework/views.py#L134
I believe that BaseJSONWebTokenAuthentication authentication class should enforce csrf validation when needed. Like in rest_framework.authentication.SessionAuthentication, which explicitly call CSRFCheck?

@bmpenuelas Thanks for writing this patch! Is this PR a comprehensive fix (with using the csrf decorator)? Is there any reason why I shouldn't make a custom .whl for this before merge? Is there a timeline for merge?

Yes @jheld , using the csrf decorator this fix alone can provide the desired protection.

Does this protect against login csrf?

Hi @bmpenuelas , what I mean is the CSRF token is not set until the JWT is issued, i.e. after the user has logged in. Therefore an attacker could log in via CSRF and the user would think they were logged in to their own account. The user would then unwittingly be performing actions on the attacker's account. Or is there some protection against this that I am missing?

Protection is generally geared toward avoiding forging user requests. That protection is provided by the Anti-CSRF token and the JWT token working together.
In the particular case you mention, at no time is the user session compromised. It's not a threat like user-impersonating CSRF, but it's true it can have privacy implications. I don't want to go off-topic here since this isn't related to the pull-request itself, but CSRFToken can protect your application from this situation too. For example, you can issue an Anti-CSRF token for the login process, and store it as both: a hidden form value, and a cookie. To validate the login request, both values must match, and since an attacker can't read them both, the login will fail.

It's a different type of csrf to the more common session riding, but it's still a security flaw we need to protect against.
This is where I think it has relevancy to the pull request: To protect against login-csrf we need to decorate our login view with csrf_protect. We then need to create a view that will set the csrftoken cookie, so that we can fetch it prior to login and our login request is not blocked. This being the case, we no longer need to set the csrftoken cookie when we issue the JWT, because it is already set.
Basically, if we follow the approach of protecting ourselves from login-csrf we will also automatically be protecting ourselves from 'normal' csrf (provided we guard all unsafe views with csrf_protect). Whereas if we follow the approach of protecting from 'normal' csrf, we are still leaving ourselves open to login-csrf.

Yes, this PR already does that. CSRF tokens are issued for every request, not only after login, so you can use them for login, or to protect other requests, the same principles apply.
The problem before this PR was that when you used the JWT token for authentication, the CSRF token was ignored.

Any ideas when this PR is going to be merged into the package? Does it need work, can I help in any way getting this out the door?

@pc-trent offer sacrifices to @gcollazo and @jpadilla . c.f. https://github.com/GetBlimp/django-rest-framework-jwt/issues/449

@pc-trent offer sacrifices to @gcollazo and @jpadilla . c.f. #449

I'll take that as a "this project is dead"

We should hope not. Maybe we can ask for maintainer privileges? Including PyPI. We've been waiting for this fix for a year.


Upload of files larger than 100 Mb fails via the UI

Environment info

Version: 2.3.0-5904f07*
Deployment: **AZURE ** (West US 2)

Actual behavior

After several retries file fails to upload
Same file uploads via Cyberduck without failure

Expected behavior

File uploads without issues

Steps to reproduce

Open bucket tab on UI
Select any bucket (default first.bucket will fit)
Start uploading file with size > 100 Mb
Open File Uploads window

Reproduced with spillover only bucket, disabled spillover bucket and bucket both with nodes pool and spillover
Screenshots or Logs or other output that would be helpful

nbfedump.2018_03_21-18_27_13.json.zip

Irrelevant, wont fix


I can't create the new user in oracle;

Run the Container
docker run --name oracle-19c -p 1521:1521 -e ORACLE_SID=orcl -e ORACLE_PWD=123456789 -v D:/Researchs/Oracle/oracle-19c/oradata/:/opt/oracle/oradata doctorkirk/oracle-19c

When i want to create the new user
sqlplus / as sysdba
CREATE USER mars IDENTIFIED BY 123456789;

An error appears:
SQL> CREATE USER mars IDENTIFIED BY 123456789;
CREATE USER mars IDENTIFIED BY 123456789
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

This isn't an error creating the user. The database wasn't created successfully. Try running:
docker logs oracle-19c

That should show the error generated during container and database creation.

@oraclesean
The docker log
==> /opt/oracle/diag/rdbms/orcl/orcl/trace/alert_orcl.log <==
2023-09-18T14:06:55.522324+00:00
Adjusting the default value of parameter parallel_max_servers
from 640 to 72 due to the value of parameter processes (150)
Starting ORACLE instance (normal) (OS id: 637)
2023-09-18T14:06:55.528147+00:00
WARNING: You are trying to use the MEMORY_TARGET feature. This feature requires the /dev/shm file system to be mounted for at least<PHONE_NUMBER> bytes. /dev/shm is either not mounted or is mounted with available space less than this size. Please fix this so that MEMORY_TARGET can work as expected. Current available is 67108864 and used is 0 bytes. Ensure that the mount point is /dev/shm for this directory.
2023-09-18T14:06:55.530589+00:00
memory_target needs larger /dev/shm


Lazily initialize Swift LinkingObjects instances

LinkingObjects instances were being initialized eagerly by RLMInitializeSwiftAccessorGenerics, which was resulting in a backlinks TableView being created for every Swift instance of a type that contained a LinkingObjects property. Lazily initializing these properties means that the work of building the backlinks view is deferred until the property is first accessed. This significantly reduces the cost of allocating a Swift object that has a LinkingObjects property.
/cc @tgoyne @jpsim @austinzheng
This was visible in an Instruments trace a user provided via email.

Why RLMWeakObjectHandle over just a weak pointer to the object?

There's no guarantee that anything will keep the object alive long enough. Consider:
let linkingObjects = realm.objects(SomeClass).first.linkingObjects
print(linkingObjects.count)

Should that class be called RLMLazyObjectHandle instead? The point is that the object is instantiated on demand, right?

That makes sense. I'm mostly just concerned that the extra row accessor could be expensive due to that it needs to grab a lock, but I suppose the TableView was doing that anyway.

Now that I think about it, RLMWeakObjectHandle could also hold a weak reference to the original object to sometimes allow skipping the allocation of a new instance within -object. It wouldn't avoid the need for it to hold a row accessor itself though, so it may not be worth it.
@austinzheng, I used "weak" in the name since the important part of its behavior is that it doesn't keep the object accessor alive. "lazy" doesn't feel like a good fit for the semantics it provides.

The CI failure is only the pre-existing testRealmCreationCached regression in Swift device tests. Moving to Review.

👍
CI failure unrelated.


[Bug] Change the landing page text of a new app

Description
The landing page of a new app is misleading since there is no widget one can drag unless they click on the + icon next to widgets

Closing this since we haven't seen any real problems with users figuring out drag and drop


Remove unsafe in testing helper

This PR removes some unnecessary unsafe from the testing helpers. While it was not technically unsound, the same result can be achieved with safe code and less lines.

Thanks!


Active jobs are not deleted when the job finishes if TTLSecondsAfterFinished is set

What happened:
When TTLSecondsAfterFinished is not set, the active jobs get deleted right away to free up resources. However, when TTLSecondsAfterFinished is set, the active jobs and the completed jobs all get deleted after the TTL expires when the jobset itself gets deleted.
What you expected to happen:
TTLSecondsAfterFinished should control jobset cleanup but active jobs should be deleted regardless when a jobset is failed or complete to release resources.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

Kubernetes version (use kubectl version):
JobSet version (use git describe --tags --dirty --always):
Cloud provider or hardware configuration:
Install tools:
Others:

Hey @CecileRobertMichon
Thank you for the issue and the PR to fix it. We have a few CI issues I’m trying to fix this week so I’ll get to reviewing your PR soon.


Feat/project tools

Description
Allows the user to include tools used in projects.
The logic adds the tools under the affiliation. If the affiliation is none, it replaces the affiliation.
Relevant Pull Requests
This contains the pull requests:
Pull request 14
Pull request 15

Thank you for your contribution, @Aparaxium. I have some thoughts on this PR. I think we could consider including the mention of tools in the bullet points, rather than having a separate line just for tools. This would help save valuable space.
Having a line for "Tools used" also seems specific for tech-oriented resumes (I try to make template as general as possible to apply to also other engineering fields). One can argue that for other engineering fields (or other non-STEM fields) that you could include tools like Aspen HYSYS, Figma, AutoCAD, IBM SPSS, etc. but it's not really the main point to highlight most of the time in a CV or résumé and can be relegated to the bottom section or briefly in the bullet points.
As of now, I don't see enough of a rationale to merge this but thank you for your PR.

Thank you for your contribution, @Aparaxium. I have some thoughts on this PR. I think we could consider including the mention of tools in the bullet points, rather than having a separate line just for tools. This would help save valuable space.
Having a line for "Tools used" also seems specific for tech-oriented resumes (I try to make template as general as possible to apply to also other engineering fields). One can argue that for other engineering fields (or other non-STEM fields) that you could include tools like Aspen HYSYS, Figma, AutoCAD, IBM SPSS, and etc. but it's not really the main point to highlight most of the time in a CV or résumé and can be relegated to the bottom section or the bullet points.
As of now, I don't see enough of a rationale to merge this but thank you for your contribution. Feel free to fork if you would like to create a more specialized template.

Hello,
I appreciate the feedback, after considering it, I believe you are correct in that the bullet points should explain the tools used.
I did try to make this as optional as possible. If the tools are omitted they will not be displayed. I understand if this pull request is not needed.

Closing because I don't like this implementation and I will be making changes to it.


osu-lazer: 2020.1017.0 -> 2020.1121.0

Motivation for this change
Bump version.
Things done

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

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

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

549.1M

[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 104669 1

1 package built:

osu-lazer

Result of nixpkgs-review pr 104669 1

1 package built:

osu-lazer


Issues #8 and #10 - UI test for search bar

This UI test focuses on the search bar.
Touches issues #8, #10

Made the requested changes and pushed them to  search2.0 branch.

Applied the requested changes and modified the test to be in sync with master branch


Vim commands should repeat if command includes a number

Check for existing issues

[X] Completed

Describe the feature
In vim, if I type something like d2d, it will delete two lines (where dd deletes the current line). This works for arbitrary integers (e.g. d57d).
Zed should support this. Right now, the number causes the command to not resolve/execute.
If applicable, add mockups / screenshots to help present your vision of the feature
No response

Thanks for reporting this, it should be fixed in the latest build (v0.104)


fix: prettier_build unavailabe

This PR fixed prettier_build function. we covered default cargo build console and make it more concise.

What issue does this fix with the prettier_build function?

prettier_build will cover default cargo build print, but currently prettier will use old build print. so it useless yet.

prettier_build will cover default cargo build print, but currently prettier will use old build print. so it useless yet.

I'm still not entirely sure what the PR does. When running the CLI in both versions, the cargo build output flashes on the screen and then is covered up by the status screen.
Does this PR start to implement a prettier build function but doesn't actually add any new functionality yet?

prettier_build will cover default cargo build print, but currently prettier will use old build print. so it useless yet.

Sorry, I'm still not entirely sure I understand what the PR changes. When running the CLI in both versions, the cargo build output flashes on the screen and then is covered up by the status screen so it looks like the build function doesn't cover up the cargo build yet.
Does this PR start to implement a prettier build function but doesn't add any new functionality/bug fixes yet?

I just replace the default cargo build information, just have one line build info, and new building project will cover finished.
https://github.com/DioxusLabs/dioxus/assets/41265098/cc68925d-f589-4654-8702-127c20d35ee4
this style is better for hot-reload (rebuild), the console page will be not scroll down, so we can keep display service information.

prettier_build will cover default cargo build print, but currently prettier will use old build print. so it useless yet.

Sorry, I'm still not entirely sure I understand what the PR changes. When running the CLI in both versions, the cargo build output flashes on the screen and then is covered up by the status screen so it looks like the build function doesn't cover up the cargo build yet.
Does this PR start to implement a prettier build function but doesn't add any new functionality/bug fixes yet?

I just replace the default cargo build information, just have one line build info, and new building project will cover finished.
2023-09-<IP_ADDRESS>.mov
this style is better for hot-reload (rebuild), the console page will be not scroll down, so we can keep display service information.

I see now, thank you! That looks much better!


CLOUDSTACK-9204 Do not error when staticroute is already gone

When deleting a static route fails because it isn't there any more (KeyError), it should succeed instead.
Error seen:
[INFO] Processing JSON file static_routes.json.1451560145
Traceback (most recent call last):
File "/opt/cloud/bin/update_config.py", line 140, in <module>
process_file()
File "/opt/cloud/bin/update_config.py", line 52, in process_file
qf.load(None)
File "/opt/cloud/bin/merge.py", line 258, in load
proc = updateDataBag(self)
File "/opt/cloud/bin/merge.py", line 91, in _init_
self.process()
File "/opt/cloud/bin/merge.py", line 131, in process
dbag = self.process_staticroutes(self.db.getDataBag())
File "/opt/cloud/bin/merge.py", line 179, in process_staticroutes
return cs_staticroutes.merge(dbag, self.qFile.data)
File "/opt/cloud/bin/cs_staticroutes.py", line 26, in merge
del dbag[key]
KeyError: u'<IP_ADDRESS>'

Trivial fix indeed. We can ignore this since our goal has been reached.
LGTM

LGTM based on these tests:
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced,required_hardware=true \
component/test_vpc_redundant.py \
component/test_routers_iptables_default_policy.py \
component/test_routers_network_ops.py \
component/test_vpc_router_nics.py \
smoke/test_loadbalance.py \
smoke/test_internal_lb.py \
smoke/test_ssvm.py \
smoke/test_network.py

Result:
Create a redundant VPC with two networks with two VMs in each network ... === TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network and check default routes ... === TestName: test_02_redundant_VPC_default_routes | Status : SUCCESS ===
ok
Create a redundant VPC with two networks with two VMs in each network ... === TestName: test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName: test_02_routervm_iptables_policies | Status : SUCCESS ===
ok
Test iptables default INPUT/FORWARD policies on VPC router ... === TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_01_isolate_network_FW_PF_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_02_isolate_network_FW_PF_default_routes_egress_false | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true | Status : SUCCESS ===
ok
Test redundant router internals ... === TestName: test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test nics after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS ===
ok
Create a VPC with two networks with one VM in each network and test default routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS ===
ok
Check the password file in the Router VM ... === TestName: test_isolate_network_password_server | Status : SUCCESS ===
ok
Check that the /etc/dhcphosts.txt doesn't contain duplicate IPs ... === TestName: test_router_dhcphosts | Status : SUCCESS ===
ok
Test to create Load balancing rule with source NAT ... === TestName: test_01_create_lb_rule_src_nat | Status : SUCCESS ===
ok
Test to create Load balancing rule with non source NAT ... === TestName: test_02_create_lb_rule_non_nat | Status : SUCCESS ===
ok
Test for assign & removing load balancing rule ... === TestName: test_assign_and_removal_lb | Status : SUCCESS ===
ok
Test to verify access to loadbalancer haproxy admin stats page ... === TestName: test02_internallb_haproxy_stats_on_all_interfaces | Status : SUCCESS ===
ok
Test create, assign, remove of an Internal LB with roundrobin http traffic to 3 vm's ... === TestName: test_01_internallb_roundrobin_1VPC_3VM_HTTP_port80 | Status : SUCCESS ===
ok
Test SSVM Internals ... === TestName: test_03_ssvm_internals | Status : SUCCESS ===
ok
Test CPVM Internals ... === TestName: test_04_cpvm_internals | Status : SUCCESS ===
ok
Test stop SSVM ... === TestName: test_05_stop_ssvm | Status : SUCCESS ===
ok
Test stop CPVM ... === TestName: test_06_stop_cpvm | Status : SUCCESS ===
ok
Test reboot SSVM ... === TestName: test_07_reboot_ssvm | Status : SUCCESS ===
ok
Test reboot CPVM ... === TestName: test_08_reboot_cpvm | Status : SUCCESS ===
ok
Test destroy SSVM ... === TestName: test_09_destroy_ssvm | Status : SUCCESS ===
ok
Test destroy CPVM ... === TestName: test_10_destroy_cpvm | Status : SUCCESS ===
ok
Test Remote Access VPN in VPC ... === TestName: test_vpc_remote_access_vpn | Status : SUCCESS ===
ok
Test VPN in VPC ... === TestName: test_vpc_site2site_vpn | Status : SUCCESS ===
ok
Test for port forwarding on source NAT ... === TestName: test_01_port_fwd_on_src_nat | Status : SUCCESS ===
ok
Test for port forwarding on non source NAT ... === TestName: test_02_port_fwd_on_non_src_nat | Status : SUCCESS ===
ok
Test for reboot router ... === TestName: test_reboot_router | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_1_static_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_2_nat_rule | Status : SUCCESS ===
ok
Test for Router rules for network rules on acquired public IP ... === TestName: test_network_rules_acquired_public_ip_3_Load_Balancer_Rule | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 34 tests in 16299.579s

OK

And:
nosetests --with-marvin --marvin-config=${marvinCfg} -s -a tags=advanced,required_hardware=false \
smoke/test_routers.py \
smoke/test_network_acl.py \
smoke/test_privategw_acl.py \
smoke/test_reset_vm_on_reboot.py \
smoke/test_vm_life_cycle.py \
smoke/test_vpc_vpn.py \
smoke/test_service_offerings.py \
component/test_vpc_offerings.py \
component/test_vpc_routers.py

Result:
Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS ===
ok
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok
Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
ok
Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS ===
ok
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS ===
ok
Test to create service offering ... === TestName: test_01_create_service_offering | Status : SUCCESS ===
ok
Test to update existing service offering ... === TestName: test_02_edit_service_offering | Status : SUCCESS ===
ok
Test to delete service offering ... === TestName: test_03_delete_service_offering | Status : SUCCESS ===
ok
Test for delete account ... === TestName: test_delete_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for admin account ... === TestName: test_public_ip_admin_account | Status : SUCCESS ===
ok
Test for Associate/Disassociate public IP address for user account ... === TestName: test_public_ip_user_account | Status : SUCCESS ===
ok
Test for release public IP address ... === TestName: test_releaseIP | Status : SUCCESS ===
ok
Test create VPC offering ... === TestName: test_01_create_vpc_offering | Status : SUCCESS ===
ok
Test VPC offering without load balancing service ... === TestName: test_03_vpc_off_without_lb | Status : SUCCESS ===
ok
Test VPC offering without static NAT service ... === TestName: test_04_vpc_off_without_static_nat | Status : SUCCESS ===
ok
Test VPC offering without port forwarding service ... === TestName: test_05_vpc_off_without_pf | Status : SUCCESS ===
ok
Test VPC offering with invalid services ... === TestName: test_06_vpc_off_invalid_services | Status : SUCCESS ===
ok
Test update VPC offering ... === TestName: test_07_update_vpc_off | Status : SUCCESS ===
ok
Test list VPC offering ... === TestName: test_08_list_vpc_off | Status : SUCCESS ===
ok
test_09_create_redundant_vpc_offering (integration.component.test_vpc_offerings.TestVPCOffering) ... === TestName: test_09_create_redundant_vpc_offering | Status : SUCCESS ===
ok
Test start/stop of router after addition of one guest network ... === TestName: test_01_start_stop_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test reboot of router after addition of one guest network ... === TestName: test_02_reboot_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to change service offering of router after addition of one guest network ... === TestName: test_04_chg_srv_off_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test destroy of router after addition of one guest network ... === TestName: test_05_destroy_router_after_addition_of_one_guest_network | Status : SUCCESS ===
ok
Test to stop and start router after creation of VPC ... === TestName: test_01_stop_start_router_after_creating_vpc | Status : SUCCESS ===
ok
Test to reboot the router after creating a VPC ... === TestName: test_02_reboot_router_after_creating_vpc | Status : SUCCESS ===
ok
Tests to change service offering of the Router after ... === TestName: test_04_change_service_offerring_vpc | Status : SUCCESS ===
ok
Test to destroy the router after creating a VPC ... === TestName: test_05_destroy_router_after_creating_vpc | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 41 tests in 7962.397s

OK

We successfully run this on a production cloud.

Ping @remibergsma
LGTM, please proceed with merge.
Cheers,
Wilder


index seems to be marked as returning bool instead of number

Thank you for opening an issue.
In this template paragraph text could be removed, however please retain headers.
Prerequisites

[x] Ensure you have latest version of plugin installed
[x] Search for possible issue duplicates

Installation details

[x] IDE version (Help->About->Copy to Clipboard)

in details block below

[x] intellij-hcl plugin version (Settings->Plugins)

0.7.14

[x] Terraform version (terraform -v)

1.0.3

IDE version
IntelliJ IDEA 2021.2.2 (Ultimate Edition)
Build #IU-212.5284.40, built on September 14, 2021
Licensed to Gareth Jones
Subscription is active until June 21, 2022.
Runtime version: 11.0.12+7-b1504.28 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 2988M
Cores: 12
Registry: ide.remote.interpreters.rsync.enabled.on.windows=true, show.affected.tests.in.changelists=true
Non-Bundled Plugins: Statistic (4.1.7), org.sylfra.idea.plugins.linessorter (1.0.1), org.toml.lang (<IP_ADDRESS>14-212), com.jetbrains.plugins.ini4idea (212.4746.57), com.alayouni.ansiHighlight (1.2.4), lermitage.intellij.battery.status (1.19.201), CMD Support (1.0.5), net.seesharpsoft.intellij.plugins.csv (2.17.1), com.intellij.ideolog (<IP_ADDRESS>), name.kropp.intellij.makefile (212.4746.52), com.sburlyaev.terminal.plugin (0.4.4), com.intellij.javafx (1.0.3), Dummy Text Generator (1.2.0), Key Promoter X (2021.2), com.intellij.plugins.watcher (212.5080.8), org.intellij.plugins.hcl (0.7.14), PsiViewer (212-SNAPSHOT), com.intellij.apacheConfig (212.4746.57), uk.co.ben-gibson.remote.repository.mapper (3.3.5), mobi.hsz.idea.gitignore (4.2.0), net.vektah.codeglance (1.5.4), AWSCloudFormation (212.4746.57), org.jetbrains.plugins.go-template (212.4746.52), org.jetbrains.plugins.slim (212.5080.8), org.intellij.plugins.postcss (212.4746.57), com.intellij.kubernetes (212.5284.17), org.elixir_lang (11.13.0), com.perl5 (2021.2), com.intellij.plugin.adernov.powershell (2.0.7), org.jetbrains.plugins.vagrant (212.4746.57), String Manipulation (<IP_ADDRESS>.3), mdx.js (1.2.212), jones.restarteslintaction.restart-eslint-action (0.0.1), com.intellij.lang.jsgraphql (3.0.0), com.dmarcotte.handlebars (212.4746.57), com.intellij.plugins.webcomponents (212.4746.57), com.jetbrains.lang.ejs (212.4746.57), org.jetbrains.plugins.node-remote-interpreter (212.5080.8), Dart (212.5284.31), io.flutter (60.1.4), com.intellij.plugins.html.instantEditing (212.4746.57), com.jetbrains.php (212.5284.49), com.jetbrains.twig (212.4746.57), com.kalessil.phpStorm.phpInspectionsEA (<IP_ADDRESS>), net.king2500.plugins.PhpAdvancedAutoComplete (1.1.0), com.raket.silverstripe (<IP_ADDRESS>), com.jetbrains.php.blade (212.5080.8), de.espend.idea.laravel (0.15.4), org.jetbrains.plugins.phpstorm-remote-interpreter (212.4746.52), org.jetbrains.plugins.phpstorm-docker (212.4746.52), com.jetbrains.php.wordPress (212.4746.52), com.jetbrains.php.behat (212.4746.52), org.jetbrains.plugins.ruby (212.5284.19), jones.foldcallblocks.fold-call-blocks (0.0.7-beta), org.jetbrains.plugins.ruby-chef (212.5080.8), intellij.prettierJS (212.5080.8), org.jetbrains.plugins.vue (212.5284.22), cucumber-javascript (212.4746.57), com.deadlock.scsyntax (212.4746.57), com.jetbrains.plugins.jade (212.5080.8), org.jetbrains.plugins.go (212.5284.31), Pythonid (212.5284.44), ru.meanmail.plugin.requirements (2021.4.1-212), aws.toolkit (1.32-212), org.jetbrains.kotlin (212-1.5.31-release-546-IJ4638.7), ru.adelf.idea.dotenv (2<IP_ADDRESS>), org.jetbrains.plugins.phpstorm-wsl (212.5080.8)
Kotlin: 212-1.5.31-release-546-IJ4638.7

Terraform Configuration Files
resource "aws_subnet" "load_balancer" {
  for_each = toset(data.aws_availability_zones.available.names)

  vpc_id            = aws_vpc.main.id
  availability_zone = each.key
  cidr_block        = "${var.vpc_ip_range_prefix}.${96 + index(data.aws_availability_zones.available.names, each.key) * 16}.0/20"
}

Expected Behavior
No error
Actual Behavior
The index function call is marked in red, with the message "Number expected instead of bool".

I think the issue is with the index function rather than the arguments as if I remove those (e.g. have just index()) the error remains.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:

Have a .tf file with the contents shown above
Open in IntelliJ

This started happening in the new versions that were released this month - I think starting with 0.7.11, but it could have been introduced in a later version. It was definitely not happening before 0.7.11 :)

Fixed in upcoming update (0.7.15)


maplibre-demo: Problem when building for web

When building for web, I encounter an error.
🤔 Expected Behavior

The build should finish with no problems.
😯 Current Behavior

This is the error message:
   Compiling web v0.1.0 (/home/myuser/Projects/maplibre-rs/web)
error: failed to run custom build command for `web v0.1.0 (/home/myuser/Projects/maplibre-rs/web)`

Caused by:
  process didn't exit successfully: `/home/myuser/Projects/maplibre-rs/target/wasm-dev/build/web-9ac762a1a95b882a/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=./flatbuffer

  --- stderr
  thread 'main' panicked at 'flatc: Custom { kind: NotFound, error: "failed to spawn `\"flatc\" \"--version\"`: No such file or directory (os error 2)" }', web/build.rs:25:6
  stack backtrace:
     0: rust_begin_unwind
               at /rustc/42325c525b9d3885847a3f803abe53c562d289da/library/std/src/panicking.rs:575:5
     1: core::panicking::panic_fmt
               at /rustc/42325c525b9d3885847a3f803abe53c562d289da/library/core/src/panicking.rs:65:14
     2: core::result::unwrap_failed
               at /rustc/42325c525b9d3885847a3f803abe53c562d289da/library/core/src/result.rs:1791:5
     3: core::result::Result<T,E>::expect
               at /rustc/42325c525b9d3885847a3f803abe53c562d289da/library/core/src/result.rs:1070:23
     4: build_script_build::main
               at ./build.rs:13:5
     5: core::ops::function::FnOnce::call_once
               at /rustc/42325c525b9d3885847a3f803abe53c562d289da/library/core/src/ops/function.rs:510:5
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Failed to start building: Failed to execute cargo build
error: Recipe `web-lib` failed on line 91 with exit code 1

🌍 Your Environment

Desktop

Operating System: Linux (Manjaro)

FlatBuffers compiler was recently added as a dependency (flatc).
I did not yet update the documentation. Let's use this issue to update the docs and explain how to fix this.
I think you can just execute pacman -S flatbuffers

Thanks, after also installing wasm-bindgen, it builds. Firefox Nightly doesn't display anything, but most WebGPU demos don't work either, so the fault probably lies there.


Fix 'setStoresSnapshot with lazy option' doc example

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/datorama/akita/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

Thanks, but you should follow our commit guidelines. Create it again, and use npm run commit. Choose docs.


Add a troubleshooting guide for authentication issues

Add to the documentation the steps to fix authentication issues during deployments

one issue that needs to be address is this error message when deploying
INFO:deploy:checking if RBAC already exists
INFO:deploy:deploying arm template: azuredeploy.json
INFO:deploy:assigning the user managed identity role
Traceback (most recent call last):
  File "deploy.py", line 857, in <module>
    main()
  File "deploy.py", line 851, in main
    state[1](client)
  File "deploy.py", line 410, in assign_scaleset_identity_role
    assign_scaleset_role(
  File "/tmp/release/deploy/registration.py", line 371, in assign_scaleset_role
    query_microsoft_graph(
  File "/tmp/release/deploy/registration.py", line 66, in query_microsoft_graph
    raise GraphQueryError(
registration.GraphQueryError: request did not succeed: HTTP 403 - {
  "error": {
    "code": "Authorization_RequestDenied",
    "message": "Insufficient privileges to complete the operation.",
    "innerError": {
      "date": "2020-11-17T16:57:10",
      "request-id": "d3e59410-5b15-4cf0-b129-35ff1daea420",
      "client-request-id": "d3e59410-5b15-4cf0-b129-35ff1daea420"
    }
  }
}


[Deepcast] Please add an option to clear the context after copying

Extension
https://www.raycast.com/mooxl/deepcast
Description
When translating and then copying the translated text with Deepcast, I usually trigger Raycast then immediately again to launch a different app, but then Raycast is still in the Deepcast "area" at this point—so I have to hit esc a number of times to get back to the base state before I can launch something else.
It would be nice if it was possible to set an option that would "reset" Raycast to the starting state after I copy the translated text
Who will benefit from this feature?
Anyone who rapidly translates text and copies the translation in order to work with it in another application, I would think
Anything else?
No response

@raycastbot assign me


Css bundling support outside jspm

Would be nice to use it via SystemJS, not jspm

The result from bundling js and CSS files together is in due time consumed by systemjs.
Also, when you bundle using jspm-cli you're actually delegating to systemjs-builder.


Implicit type promotion for arithmetic operators

It may be best not to approach this issue specifically, but rather as part of a broader piece of work.
However, this specifically is something we want for Qiskit 1.1

Some of this was done in #171


LANG-1520 spring clean .gitignore

Handles https://issues.apache.org/jira/browse/LANG-1520

I think you tagged won't ticket

Coverage remained the same at 95.101% when pulling 73cf2a5c5a36ce3d95c5eac0989b299815baa05b on nhojpatrick:LANG-1520 into 94b3784fdec5d0e9d63e4aec6772144b68283790 on apache:master.

I think you tagged won't ticket

cheers, working on 4 projects at once