Creating folder through VS Code trying to use "+" in name sends program to Not Responding for a bit

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

VS Code Version: 1.58.2
OS Version: Windows 10 Home 20H2 Build 19042.1110

Steps to Reproduce:

Go to Open Folder under File
Create new folder within Open Folder dialog
Start typing in new name, and then type "+" as part of the name
VS Code freezes up for a bit

Was caused by one of the following extensions:
Better TOML==0.3.2
ESLint==2.1.23
Material Icon Theme==4.8.0
Path Intellisense==2.4.0
Prettier - Code formatter==8.1.0
Rust==0.7.8
TSLint==1.3.3


upgrade all dependencies, mainly to support react-redux 7 and react-router 5

Since I requested it here https://github.com/makeomatic/redux-connect/issues/139
I though I might pull it of myself :)

thanks @badtant
CC @aleksxor could you review the code and make changes if need be / merge to support updates"

so, are you ready to merge? :)

yes, if you can change react peer dep to ^16.8.4 then I'd be happy to merge

Yeah, but it looks like you already did that commit?

did I? oh, totally forgot about it :)


Image Format

Is it possible to use the code for .jog images?

Try to change line 212 in file image_stack.py https://github.com/PolymerGuy/muDIC/blob/c2c54018ed8c9aba2eaf3a82bc79c2cb56878d01/muDIC/IO/image_stack.py#L212 adding also jpg files to the list of supported files and see if it works. imageio used for reading images should support also jpeg.


Designer api

Moved most dynamic-based logic from Perspex.Designer to Perspex
Introduced IWindowingPlatform interface, so we no longer need InitializeDesigner hack in Win32Platform
Implemented scaling


FindUsage doesn't find usages if they're in a macro

MRE
use ide_db::defs::Definition;
use syntax::ast;
use crate::assist_context::{AssistContext, Assists};

pub(crate) fn mre_findusage(_acc: &mut Assists, ctx: &AssistContext) -> Option<()> {
    let item = ctx.find_node_at_offset::<ast::IdentPat>()?;
    let usages = Definition::Local(ctx.sema.to_def(&item)?).usages(&ctx.sema).all();

    assert!(!usages.is_empty());
    dbg!(usages);

    Some(())
}

#[cfg(test)]
mod tests {
    use crate::tests::check_assist_not_applicable;
    use super::*;

    #[test]
    fn no_usages() { // This test will panic
        check_assist_not_applicable(
            mre_findusage,
            r#"
fn func(it<|>: i32) {
    println!("{}", it);
}
"#,
        );
    }

    #[test]
    fn found_usages() { // This test won't panic
        check_assist_not_applicable(
            mre_findusage,
            r#"
fn func(it<|>: i32) {
    my_print_func(it);
}
"#,
        );
    }
}

FindUsages only searches for Name and NameRefs: https://github.com/rust-analyzer/rust-analyzer/blob/c5868a48795c899d43fde773091f0b133bee0a59/crates/ide_db/src/search.rs#L255-L269
The syntax tree for the test with a function has a NAME_REF:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>"my_print_func"
<EMAIL_ADDRESS><EMAIL_ADDRESS>"("
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><-----------
<EMAIL_ADDRESS>"it"
<EMAIL_ADDRESS>")"
<EMAIL_ADDRESS>";"

but the syntax tree for the test with a macro just has an IDENT:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>"println"
<EMAIL_ADDRESS>"!"
<EMAIL_ADDRESS><EMAIL_ADDRESS>"("
<EMAIL_ADDRESS>"\"{}\""
<EMAIL_ADDRESS>","
<EMAIL_ADDRESS>" "
<EMAIL_ADDRESS>"it"  <-------
<EMAIL_ADDRESS>")"
<EMAIL_ADDRESS>";"

Fix should be to just make the macro's syntax tree have a NAME_REF, right?

This is because tests don't have libstd / libcore. If you try
fn func(it: i32) {
    println!("{}", it);
}

in a project with stdlib, it correclty finds usage of ir.


Setup travis and scrutenizer

i also added codeclimate, since they have a free plan for open source projects and scrutenizer does not


HTTP request lost

Bug description
An app with Istio enabled connects to a http service outside the mesh during startup.
Most (or all initial) request fails. In the istio-proxy container log we don't see the request getting logged. With debug enabled we do see the following:
[Envoy (Epoch 0)] [2020-05-18 19:24:09.307][38][debug][filter] [external/envoy/source/extensions/filters/listener/original_dst/original_dst.cc:18] original_dst: New connection accepted
[Envoy (Epoch 0)] [2020-05-18 19:24:09.308][38][debug][filter] [external/envoy/source/extensions/filters/listener/tls_inspector/tls_inspector.cc:78] tls inspector: new connection accepted
[Envoy (Epoch 0)] [2020-05-18 19:24:09.408][38][debug][conn_handler] [external/envoy/source/server/connection_handler_impl.cc:196] listener filter times out after 100 ms
[Envoy (Epoch 0)] [2020-05-18 19:24:09.408][38][debug][conn_handler] [external/envoy/source/server/connection_handler_impl.cc:199] fallback to default listener filter
[Envoy (Epoch 0)] [2020-05-18 19:24:09.408][38][debug][conn_handler] [external/envoy/source/server/connection_handler_impl.cc:330] closing connection: no matching filter chain found
[Envoy (Epoch 0)] [2020-05-18 19:24:09.548][37][debug][connection] [external/envoy/source/common/network/connection_impl.cc:538] [C138] remote close
[Envoy (Epoch 0)] [2020-05-18 19:24:09.548][37][debug][connection] [external/envoy/source/common/network/connection_impl.cc:192] [C138] closing socket: 0
[Envoy (Epoch 0)] [2020-05-18 19:24:09.548][37][debug][pool] [external/envoy/source/common/tcp/conn_pool.cc:124] [C138] client disconnected
[Envoy (Epoch 0)] [2020-05-18 19:24:09.548][37][debug][connection] [external/envoy/source/common/network/connection_impl.cc:101] [C137] closing data_to_write=31 type=0
[Envoy (Epoch 0)] [2020-05-18 19:24:09.548][37][debug][pool] [external/envoy/source/common/tcp/conn_pool.cc:238] [C138] connection destroyed

We're using the scuttle wrapper for this app so the istio-proxy is already running once the app starts.
The service that it's connecting to is running on port 8080 (http).
Looking at the listener on <IP_ADDRESS>:8080 I don't see any reference to the PassthroughCluster cluster in the filters.
Due to an other issue we had with an external httpS service on port 8080 we created a ServiceEntry with the following spec (this SE has nothing todo with the svc the app connects to):
  hosts:
  - host1.domain.com
  location: MESH_EXTERNAL
  ports:
  - name: https-8080
    number: 8080
    protocol: HTTPS
  resolution: DNS

Once we add another host (any dummy host) to this serviceEntry the listener on <IP_ADDRESS>:8080 changes and does includes the PassthroughCluster cluster:
                    {
                        "name": "envoy.tcp_proxy",
                        "typedConfig": {
                            "@type": "type.googleapis.com/envoy.config.filter.network.tcp_proxy.v2.TcpProxy",
                            "statPrefix": "PassthroughCluster",
                            "cluster": "PassthroughCluster",
                            "accessLog": [
                                {
                                    "name": "envoy.file_access_log",
...
                                    }
                                }
                            ]
                        }
                    }

With this change the app is able to startup and connect to the service outside the mesh without any problems. Also the request appears in the access logging in envoy.
To me, this is like a bug in istiod where building the filters doesn't always go well.
Expected behavior
The service should be able to do a http request to the external mesh service.
Steps to reproduce the bug
I'm not sure how to reproduce, we currently have only a single app that is having issues.
It looks like adding the serviceEntry does influence this.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
We tested with Istio 1.5.1 and 1.5.2
How was Istio installed?
istioctl manifest apply
Environment where bug was observed (cloud vendor, OS, etc)
GKE v1.15.9-gke.26

The fix in 1.6 has indeed resolved the issue for us.

Thanks!


Document the .cmaketools.json file

This file showed up in my .vscode folder, but there is no indication of what it is used for and what can appear in it.    If it's the former, it should be documented.  If it's the latter, can a comment be injected into it that indicates that users should not modify it?

Sorry about that. The file is used internally, and I really need to find a better place to store that kind of data. I'm working on a refactor that should get the file out of there.

Actually, this is useful to see what is generated. All I would do is add a comment that it is autogenerated and leave it at that

In the 0.11.0 release, the file is no longer used. Context information is instead stored in a VSCode memento.


fix:  useStyleRegister return function uses useCallback wrapping

@zombieJ 看看，你们自己也检查一下是否还有其他返回值是没有用 useCallback 或者 useMemo 的，这会导致重复渲染

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.82%.  Consider uploading reports for the commit 4235ff4 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #176      +/-   ##
==========================================
+ Coverage   94.80%   94.82%   +0.01%
==========================================
  Files          29       29
  Lines        2619     2629      +10
  Branches      394      394
==========================================
+ Hits         2483     2493      +10
  Misses        136      136

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Mulitple failed Queues

After adding a second queue low, my django_rq now displays two failed Queues as the img below:

Can't reproduce in newer versions.
Probably fixed in a future version.

Same issue here. Failed queue is displayed twice in Django admin.
Django==1.9
django-rq==0.9.3
rq==0.6.0


Update to Coherence Hibernate 2.1.1

spring-data-jpa 2.5.6 does not work any longer with our old Hibernate version in the Hibernate Cache Demo. We need to be able to upgrade to new versions of Hibernate.
See https://github.com/coherence-community/coherence-hibernate/issues/13

Done in commit 374cdef96d0b993574c341aad9cc56c6b4db3815


[run_sk_stress_test] Update sourcekit-xfails.json for recent stress tester changes

xfails the new issues it now finds.

@swift-ci please test


a question on transduction

why instead of
unused = task_metalearn((self.inputa[0], self.inputb[0], self.labela[0], self.labelb[0]), False)
you haven't used the following:
unused = self.forward(self.inputa[0], weights, reuse=reuse)
?

It should work to use unused = self.forward(self.inputa[0], weights, reuse=False)
An older version of the code required it to be task_metalearn instead of forward. Feel free to make a pull request if you'd like.


Dvorak - QWERTY ⌘: show in finder command has wrong shortcut

VSCode Version: Version 1.12.2 (1.12.2)
OS Version: 10.12.5 (16F73)

Steps to Reproduce:

Set keyboard layout to Dvorak - QWERTY ⌘
Press ⌘-option-R, the command listed in the right-click menu

Nothing happens.
However, if I press ⌘-option-O, it opens the file in the finder.
O happens to be the label on the physical keyboard key that that is labeled R in the regular Dvorak keyboard mapping. Dvorak - QWERTY ⌘ means that when ⌘ is down, it should use the regular qwerty keyboard map.

I believe this is the behaviour of this keyboard layout when using both option and cmd modifiers vs when using only the cmd modifier:
cmd+[KeyR] (the key under 4 and 5):

cmd+option+[KeyR] (the key under 4 and 5):

@alexandrudima This is definitely not the correct behavior for Dvorak-QWERTY ⌘. In the Chrome browser, I'm able to use cmd-option-b to open the bookmark manager, though that shortcut is in the macOS menu bar.

@alexandrudima is there a more reduced test case I can add to the bug? I tried adding a onkeypress listener to a random webpage and didn't get keypresses when cmd was held down to try to log them. What's the best way to phrase this bug report to the chromium team?

https://bugs.chromium.org/p/chromium/issues/detail?id=727409

I have added a reduced test case to the Chromium issue.

This is an upstream issue (possibly within Chromium), and there are no known workarounds that we could implement on our side. This means there is no possible code change for us to do in VS Code sources to improve things.
To keep the number of issues in our inbox at a manageable level, we’re closing issues that have been on the backlog for a long time but haven’t gained traction or that are not actionable. Thank you for your time and understanding.


Scan in preview view appears white

Also in your example project, sometimes preview view appears white after pressing Scan in Preview button

Thank you for the report! Are you able to defines a workflow which produce this behaviour each time?
(it will be easier to debug)

Hi yannickl,
It isn’t systematic, randomly preview view appears rotated or totally white.
Not so often, but occurs.
I’m using last Xcode and Swift 4.
Thank you

You noticed 2 different issues:

the camera rotation
the blank screen

For the first one, I have to update the code to determine the initial orientation of the device when it is faced up.
For the second one, it seems to be a wrong workflow initialisation. Indeed the previewLayer have to be already attached to the view before to start the scan else it does not work. :/ I've updated the example project. Is the issue still occurs for you?

Hi @yannickl,
I'll try this new version and I'll report if this issue still occurs.
Thank you!


Add CircleCI Config

CircleCI appears to have been added to this repo. I do not totally understand why: it appears to have been added when I released v1.0.5. You can see the first build failure here on Github and here on CircleCI. @AlyssaKirstine, do you have more context on the latter?
Tagging @K4orta for review to either: (1) Help me figure out how to remove it (if that is more prudent than an extraordinarily simple build + not sure if our CI plan is unlimited projects or not), or (2) Sanction the current circle.yml config.

To be honest, I'm not quite sure how it was added either. This looks to have occurred around the same time I started at Curology though. So maybe this is something that automatically happened when I was setting up everything on my computer? I remember linking my Github and CircleCI accounts.

I'll get someone to remove this from Circle.


CI for example apps

CircleCI should build and test all example apps.

@greg-szabo @zramsay what do you think about this?

fo sho

Sure CI is a good idea for any code you write and CircleCI is good at fulfilling these kind of things. What is this issue for exactly? I don't see any example apps or tests.

there are 2 open PR's with example apps in them.

IMO example apps should be in https://github.com/cosmos/cosmos-sdk/tree/develop/examples

obsolete, examples apps are ~ tested


Bugfix in DCMTrajectoryGeneratorHelper::computeFeetWeight() function

This PR fixes a bug in the weight evaluation in the DCMTrajectoryGeneratorHelper class
It also fixes the indentation in the aforementioned function
cc @bemilio

For reference, here's a sample output after the fix. It makes sense to me.

@S-Dafarra let me know if we can merge the PR


{"message":"Get https://quay.io/v2/: Forbidden"}

Hi!
I have used testcontainers to run a Postgre for our tests.
In my local works like a charm.
The issue starts when running in our bamboo, when we get the next error:
3-Nov-2018 11:35:02	11:35:02.884 [main] DEBUG org.testcontainers.utility.RegistryAuthLocator - Looking up auth config for image: quay.io/testcontainers/ryuk:0.2.2
23-Nov-2018 11:35:02	11:35:02.885 [main] DEBUG org.testcontainers.utility.RegistryAuthLocator - RegistryAuthLocator has configFile: /home/bamboo/.docker/config.json (exists) and commandPathPrefix:
23-Nov-2018 11:35:02	11:35:02.896 [main] DEBUG org.testcontainers.utility.RegistryAuthLocator - registryName [quay.io] for dockerImageName [quay.io/testcontainers/ryuk:0.2.2]
23-Nov-2018 11:35:02	11:35:02.898 [main] DEBUG org.testcontainers.utility.RegistryAuthLocator - no matching Auth Configs - falling back to defaultAuthConfig [null]
23-Nov-2018 11:35:02	11:35:02.898 [main] DEBUG org.testcontainers.dockerclient.auth.AuthDelegatingDockerClientConfig - Effective auth config [null]
23-Nov-2018 11:35:02	11:35:02.963 [tc-okhttp-stream-89468176] ERROR com.github.dockerjava.core.async.ResultCallbackTemplate - Error during callback
23-Nov-2018 11:35:02	com.github.dockerjava.api.exception.InternalServerErrorException: {"message":"Get https://quay.io/v2/: Forbidden"}
23-Nov-2018 11:35:02
23-Nov-2018 11:35:02	        at org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.execute(OkHttpInvocationBuilder.java:279)
23-Nov-2018 11:35:02	        at org.testcontainers.dockerclient.transport.okhttp.OkHttpInvocationBuilder.lambda$executeAndStream$1(OkHttpInvocationBuilder.java:295)
23-Nov-2018 11:35:02	        at java.lang.Thread.run(Thread.java:748)
23-Nov-2018 11:35:02	[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.847 s <<< FAILURE! - in es.openbank.notifications.repositories.MessageRepositoryTest
23-Nov-2018 11:35:02	[ERROR] es.openbank.notifications.repositories.MessageRepositoryTest  Time elapsed: 2.847 s  <<< ERROR!
23-Nov-2018 11:35:02	java.lang.ExceptionInInitializerError
23-Nov-2018 11:35:02	Caused by: com.github.dockerjava.api.exception.InternalServerErrorException:
23-Nov-2018 11:35:02	{"message":"Get https://quay.io/v2/: Forbidden"}

Why the library is trying to connect to that URL?
I think it would be difficult that our testing environment have connection with this URL...
Thanks!!!!

Quay.io is a docker registry where the Ryuk image is pulled from: https://quay.io/repository/testcontainers/ryuk
For what it’s worth, quay.io is operated by CoreOS (now part of Red Hat).
If you or your secops team need to block access to quay then you can, as @neetkee mentioned, tell Testcontainers to pull the ryuk image from your own private registry server (somewhere that you have mirrored the image to). Hopefully this helps unblock you!
Sent with GitHawk

We have the same issue. Everything runs behind a proxy. If users configure the proxy within the docker deamon or have an internal repository that mirrors quay.io, then everything is fine. If this is not the case, then this code in ResourceReapder seems to be the issue:
String ryukContainerId = client.createContainerCmd(ryukImage)
    .withHostConfig(new HostConfig().withAutoRemove(true))
    .withExposedPorts(new ExposedPort(8080))
    .withPublishAllPorts(true)
    .withName("testcontainers-ryuk-" + DockerClientFactory.SESSION_ID)
    .withLabels(Collections.singletonMap(DockerClientFactory.TESTCONTAINERS_LABEL, "true"))
    .withBinds(binds)
    .withPrivileged(TestcontainersConfiguration.getInstance().isRyukPrivileged())
    .exec()
    .getId();

client.startContainerCmd(ryukContainerId).exec();

@remmeier I don't think setting an HTTP_PROXY env var will work I'm afraid.
I think you're trying to set a proxy that Docker should use when pulling images.
The change in your branch will just set an env var that is present in the running container (i.e. after pull).
As far as I know, there is no way for us to tell Docker what proxy to use when pulling. The only options are:

Change your docker daemon settings to use an HTTP proxy for all pulls
Host the Ryuk container image on your internal docker registry, and configure Testcontainers to pull from that

As far as I can tell there's nothing else we can do, I'm afraid.

yes, I noticed this morning as well. Second way seems the way to go. It would maybe interesting to have support for system properties and environment variables in TestcontainersConfiguration since we are getting into environment-specific properties. Or in my case I would actually like to inject the properties from a Spring Boot configuration.

and regarding this ticket those two hints could be added to the documentation and then closed

Yep, we'll update the docs. Thanks.


bump version to 3.8.1

@ZhuoxiLi There are some versions in the object annotation, let's replace them as well.

@horis233 I believe CICD will still pick up the changes from master branch, right? We may need to cherry-pick this change to master branch.

@horis233 bump the version in object annotation, please review.
@Daniel-Fan if we are going to remove release-3.8 branch, I think I am going to merge this pr to the master branch.


hostapp-update: Run the update container as privileged

Because as part of a host OS update we need to update the bootloader also,
for some boards we need to be able to write the bootloader directly to a
specific /dev entry. Hence we need the update container be able to have access
to /dev of the host.
Change-type: patch
Changelog-entry: Run the update container as privileged
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

Build finished.


npx folio returns Timeout of 30000ms exceeded

Expected Behavior
3 passed
Current Behavior
Timeout of 30000ms exceeded
Steps to Reproduce
I used the example given here. Then run :

npx folio

Detail

Environment

@playwright/test:  0.162.0
Operating System: Windows 10
Node.js version: 12.18.3
Browser: [Chromium]

The example test is actually broken. If you go to https://playwright.dev/ and inspect the page you will find that there isn't and element with the class home-navigation. What is happening here is the page.innerText(".home-navigation") actually waits for the element to become visible. So, innerText times out after 30 seconds (by default), but by then the test times out too.

Good catch @nrhoffmann, created a corresponding patch here which fixes that #192


windows_share is currently broken on Windows 2016

The legacy way we determine the share state does not work on Windows 2016. We need to migrate this resource entirely to PowerShell which will speed things up and give us greater Windows release compatibility.

New version works on 2k16 as well


Tighten pin on libunwind

Checklist

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

In conda-forge/libunwind-feedstock#19 we decided to tighten the pin on libunwind from 'x' to 'x.x'. This PR introduces the corresponding repodata patch.
cc @jakirkham

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

@jakirkham, is that about what you had in mind? I must say I feel a little out of my depth here, but happy to learn.

@conda-forge-admin, please rerender

Thanks @zklaus! 😄
Yes this is a good start. Had a suggestion above
@mkitti also flagged a line we might need to take a closer look at

Let's take a step back from "How can we patch this?" to look at "What do we want to patch?".
I used show_diff.py as described in readme.md to check which pins would be affected by the _pin_stricter solution. I believe those are a superset of the pins we want to change, i.e. all the pins we might want to change are here, but there might be some here that we don't want to change.
Below, you will find a table with all the packages and their respective pin changes, but really, only two changes occur:

libunwind >=1.4.0,<2.0a0 gets changed to libunwind >=1.4.0,<1.5.0a0
libunwind >=1.5.0,<2.0a0 gets changed to libunwind >=1.5.0,<1.6.0a0.

Now, the question is whether these are the right changes.

Do you agree with these changes?
Do you think these should be changed differently?
Do you think there are other pins that should be taken into account?

Finally, here is the promised table. Thanks for helping figure this out!

Package
old pin
new pin

linux-64::heaptrack-1.2.0-h1b472f0_0.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::heaptrack-1.2.0-h1b472f0_1.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::heaptrack-1.2.0-h26731d4_1.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::julia-1.6.1-h96f571d_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.2-h438a1c7_3.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.2-h96f571d_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.2-hbb0e23a_1.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.3-h2a39549_1.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.3-h438a1c7_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.4-h2a39549_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.4-h34dcedf_1.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::julia-1.6.4-h34dcedf_2.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::py-spy-0.3.10-h2547a8a_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::py-spy-0.3.10-h2547a8a_1.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::py-spy-0.3.11-h2547a8a_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::py-spy-0.3.3-h17340ac_2.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::py-spy-0.3.3-ha1d6e82_1.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::py-spy-0.3.4-h17340ac_0.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::py-spy-0.3.5-h17340ac_0.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::py-spy-0.3.6-h17340ac_0.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::py-spy-0.3.7-h17340ac_0.tar.bz2
libunwind >=1.4.0,<2.0a0
libunwind >=1.4.0,<1.5.0a0

linux-64::py-spy-0.3.8-h2547a8a_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-64::py-spy-0.3.9-h2547a8a_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-aarch64::py-spy-0.3.10-h48fc1f3_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-aarch64::py-spy-0.3.10-h48fc1f3_1.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-aarch64::py-spy-0.3.11-h48fc1f3_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-aarch64::py-spy-0.3.8-h48fc1f3_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-aarch64::py-spy-0.3.9-h48fc1f3_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-ppc64le::py-spy-0.3.10-h9b295ce_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-ppc64le::py-spy-0.3.10-h9b295ce_1.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-ppc64le::py-spy-0.3.11-h9b295ce_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-ppc64le::py-spy-0.3.7-he1f5e9e_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

linux-ppc64le::py-spy-0.3.8-h9b295ce_0.tar.bz2
libunwind >=1.5.0,<2.0a0
libunwind >=1.5.0,<1.6.0a0

Thank for including that detail Klaus! 😄 That looks good to me.
Right the filtering is more about making sure we are not trying to patch package that don't need patching. So a simple if has_dep(record, "libunwind") should do the trick.
As to @mkitti's point above we have some old code here that is relaxing a libunwind dependency to only depend on major version in some cases (see PR https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/85 for history cc @xhochy). That seems to be the opposite of what we are doing here and so likely needs to be dropped, but will let others comment on that.

Thanks @jakirkham. As for the filtering, I have nothing against it, but note that _pin_stricter has this check integrated, so I think it would be a bit redundant.

cc @conda-forge/core (in case others have thoughts here)

Perhaps I should explain myself a bit better.
The first thing _pin_stricter does is build a list of indices into the depends list where fix_dep (here libunwind) appears (see here). The rest of the function traverses the list, so if it's empty, nothing happens.
The list comprehension that builds the list is equivalent to the generator comprehension used in has_dep (see here), hence I think it is ok to only do _pin_stricter.

The idea of this kind of filtering is to not spend time processing things that don't need it. FWIW the rest of the calls to _pin_stricter do some conditional filtering first (for example). So think it is reasonable for us to do something similar here. Is this something you would be able to do @zklaus? 🙂 I think after that we can merge.

Done. Thanks for helping out @jakirkham.

Thanks Klaus! Also thanks Mark for the review 😄

This is wrong. The previous patch made sure the packages built with 1.2, 1.3, 1.4, 1.5 were installable at the same time. With this patch, this is not possible. The correct patch is to make sure there's a <1.6 upper bound for packages built with 1.2, 1.3, 1.4, 1.5.

The correct patch is to make sure there's a <1.6 upper bound for packages built with 1.2, 1.3, 1.4, 1.5

I concur. We need a <1.6 upper bound since Julia with libunwind 1.6.x is not working. How do we do that?
Do you mean this should be done on a per-package basis?
https://github.com/conda-forge/julia-feedstock/pull/136

See https://github.com/conda-forge/conda-forge-repodata-patches-feedstock/pull/203


Add container as possible volume type

There's the notion of a data volume container in Docker. The idea being a container exists solely to provide data volumes to other containers.
Add a container as another possible type of volume would be beneficial to users that leverage the "data volume container" concept.

@eparis Docker data volume containers aren't meanly to be RO only.


config: Use only one set of default values for risingwave.toml

Currently we have config/risingwave.toml (used by risedev -> used by ci) and default value defined in code. They did intentionally have some different values, e.g., https://github.com/risingwavelabs/risingwave/pull/6553. The reason is that we want to use different defaults for ci/dev & cloud.
https://github.com/risingwavelabs/risingwave/blob/533b9a966873ee06a754ca42a882e54e425845f3/src/config/README.md#L11-L15
This may be confusing and cause risedev need to merge config-path with the base one, which is a little bit hacky.
If we can only keep one set of defaults, things can be more straightforward. But I'm not sure how to decide the values.

How about only keeping the default values in the code(binary) and merging all customized config during the runtime? 🤔

How about only keeping the default values in the code(binary) and merging all customized config during the runtime? 🤔
https://xuanwo.io/reports/2022-16/ https://github.com/Xuanwo/serfig

Agree.
In theory, we should even delete the risingwave.toml because it's a duplication of the defaults in RwConfig. But I still kept it in #6814 because it's a handy example 🤣


Hadoop logo #713

Deploy preview for landscape failed.
Built with commit d5daf1c84665eaeaa08207d3cef45052e08469ff
https://app.netlify.com/sites/landscape/deploys/5b372a6802ed8305270e2248


Extremely high CPU usage on ambassador-chart v6.5.17

Describe the bug
After upgrading from ambassador chart v6.5.11 to v6.5.17 I have noticed very high CPU usage. The deployment scaled up to max. pods instantly and CPU usage almost reached the CPU limit. The actual traffic was very low (~100 req/s), as the upgrade was done in a maintenance window, much lower from the usual traffic. After downgrading to v6.5.11 the deployment scaled down to minimum pod number and CPU usage decreased a lot.
To Reproduce
Steps to reproduce the behaviour:

Upgrade to ambassador-chart v6.5.17
Observe increased CPU usage

Expected behaviour
CPU usage on the same level as in v6.5.11
Versions (please complete the following information):

Ambassador: 1.11.0
Kubernetes environment: on-prem
Version 1.13.3

Additional context
I was able to see lots of logs like these mentioned in https://github.com/datawire/ambassador/issues/3229. After downgrading to v6.5.11 these logs were gone.

It turns out that my HPA was misconfigured. No issue here.

@MateuszCzubak what was the issue with HPA?
We actually seeing the High CPU utilization at pods level


Add language localization options.

In my opinion, enabling localization will help a lot of people to understand more. Since this is related to not only geeks but also normal users. It will be a good idea if we add it. Can I take this issue? If can I take it, may I know the checklist for making a pull request?

I'd like to help with the Spanish localization. Any pointers on where to start?

I started with the infrastructure work here: https://github.com/gnunicorn/security-checklist/tree/ben-i18n
It is set up to have separate namespaces for pages and components, can already toggle the language and update on the fly. Next up (but I am not sure when I have time for that):

[ ] extract all inline text and put them into locale files
[ ] extract all text from apps, make app-namespaces available
[ ] add feature to flag data(-entry) to not-show/only-show in certain lang
[ ] provide a proper language-toggle (currently detects browser)

If anyone wants to help work on this, let me know and I'll grant you access!

If anyone wants to help work on this, let me know and I'll grant you access!

I won't have time to help on this for a while, but if you add me I might try to dip in and out to help :)


BatchBALD implementation

It just selects a permutation of points present in the batch but not all combinations as mentioned in the paper. The number of combinations would be c^b according to the paper but according to your code it will have b or b[max_size] combinations. Am I missing anything?
Lets say there are total 100 points , 4 classes and 10 iterations
so prediction tensor would be of shape (100,4,10)
now lets say I am creating a set of points and I have 4 points in the history = [3,18,45,60]
now selected in your code would be predictions[np.random.permutation(history[:MAX_SELECTED]]
it would jusr randomly permute these indices in history and subset prediction tensor for those values. These are not combinations in my opinion. I would assume to sample combination I will need to create a tensor of size 4^5 x 10 (4 is num classes and 5 is the batch size)
https://github.com/ElementAI/baal/blob/377ea8ed1bb78936f79d2a343bfe6835668446a3/src/baal/active/heuristics/heuristics.py#L287
I looked at author's original implementation and they seem to have implemented the sampling logic as expected. (https://github.com/BlackHC/BatchBALD/blob/master/src/joint_entropy/sampling.py)
Thanks in advance!

Yes the fix is currently in a PR. https://github.com/ElementAI/baal/pull/50
It should be merged shortly. Sorry

Sure. I can review it.

Fixed in BaaL 1.2. Thank you for your help!


Improve speed of the IDE model

Motivation / Current Behaviour
Currently, simulation with the IDE model takes a long time, especially with small time step sizes, e.g. 1e-4.  (several hours for a simulation time of 35 days in release mode)
Enhancement description
We should try to reduce the runtime. An experiment in Valgrind has demonstrated that a significant proportion of the runtime is allocated to the evaluation of the StateAgeFunctions. As the same StateAgeFunction is currently evaluated several times at the same time point, the potential for saving runtime could be highest here.
Additional context
No response
Checklist

[X] Attached labels, especially loc:: or model:: labels.
[X] Linked to project

@annawendler Is this actually also resolved by #1129 ?

I would say so for now.

As the run time of the IDE model was reduced significantly in #1129, we consider this issue resolved for now.


Provide a means for defining erred responses

Along the lines of #132, it would be useful to identify important or interesting error responses in a blueprint.

I would think this refers to the error code they will receive. If a user passes in an invalid value, will they get a 400? 404?
Some examples from Spree Commerce:
Not Found
STATUS: 404 NOT FOUND
{
  "error": "The resource you were looking for could not be found."
}

Authorization Failure
STATUS: 401 UNAUTHORIZED
{
  "error": "You are not authorized to perform that action."
}

Invalid API Key
STATUS: 401 UNAUTHORIZED
{
  "error": "Invalid API key ([key]) specified."
}

They also return 422 when things can't process. Being able to include these in the documentation can be very helpful.

You can always write these in the description section of the API. Or do you want to add these when describing every action?

Here is an example api blueprint which adds the error descriptions and other stuff in API description section.

hey @MisinformedDNA
Would something like this work for you?
# API

## Resource [/r]

### Retrieve [GET]

+ response 404

    Not Found

    + Body

            {
              "error": "The resource you were looking for could not be found."
            }

+ response 401

    Authorization Failure / Invalid API Key

    + Body

            {
              "error": "The resource you were looking for could not be found."
            }

hey @zdne & @pksunkara ,
The resource model above looks like the start of something that might work, though I see you combined the 401 responses. It would be a shame if an API had to limit it's ability to return different error messages for a 401 response just because the documentation tool didn't support it. Obviously, the API could diverge, but that's not really the goal.
So we should be able to define certain requests that lead to certain error responses. So if the header is missing, the response should be able to give one error message. And if the parameter is the wrong type, a different error message and if the parameter leads to a resource that does not exist, another error. Similar to how we can specify different content-types and get different responses.
The goal is to be able to do testing with the docs, right? So we should want and be able to do negative testing as well.
I'm still very new here, so if I'm missing anything, I do apologize. But this looked like an interesting issue that I didn't see covered in the docs.

Would it not make sense to have this tied into the Trait system in someway?
Such that if I apply the Trait "Protected" one possible response to the endpoint becomes the Authorization Failure response, if defined with the Trait.

I would say the solution to this would be #58 (#132)  perhaps in combination with support for authentication #11

Please reopen if you think #58 / #132 / #11 are missing the point.


Frontpage not working

Hi,
The front page additions don't seem to be added. Is it related to the summer sale?
Tried with both latest Chrome 114 and latest Firefox 115.
It also doesn't work for category pages, although not sure if that counts as searches
https://store.steampowered.com/category/action/
It does work for actual search pages like
https://store.steampowered.com/search/?term=civilization

Yeah this is because of the sale. It is hard to update the extension for every sale. When the sale is over it should work again.

The sale is over, the plugins works again on the default store front.


FHSTwitterEngineController is hanging when the user doesnt have twitter installed on the device

The issue is in the below method in the FHSTwitterEngine.m line 1726

(void)showOAuthLoginControllerFromViewController:(UIViewController *)sender withCompletion:(void(^)(BOOL success, UIViewController *twitterEngineViewController))block {
FHSTwitterEngineController *vc = [[FHSTwitterEngineController alloc]init];
UINavigationController *navController = [[UINavigationController alloc] initWithRootViewController:vc];
vc.modalTransitionStyle = UIModalTransitionStyleCoverVertical;
objc_setAssociatedObject(vc, "FHSTwitterEngineOAuthCompletion", block, OBJC_ASSOCIATION_COPY_NONATOMIC);
[sender presentViewController:navController animated:NO completion:nil];
}

Do you have sample code ?

// use FHSTwitterEngine if user didn't setup twitter account on device
NSString *twitterConsumerKey    = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"TwitterConsumerKey"];
NSString *twitterSecretKey      = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"TwitterSecretKey"];
[[FHSTwitterEngine sharedEngine] permanentlySetConsumerKey:twitterConsumerKey andSecret:twitterSecretKey];
dispatch_async(dispatch_get_main_queue(), ^{
    [[FHSTwitterEngine sharedEngine] showOAuthLoginControllerFromViewController:self withCompletion:^(BOOL success, UIViewController *twitterEngineViewController) {
        if (success) {
            TwitterFollowController *twitterController = [[TwitterFollowController alloc] initWithNibName:@"TwitterFollowController" bundle:nil];
            UINavigationController *navController = [[UINavigationController alloc] initWithRootViewController:twitterController];
            navController.navigationBar.barStyle = UIBarStyleBlack;
            [twitterEngineViewController presentViewController:navController animated:NO completion:nil];
        }
    }];
});

what version of FHSTwitterEngine are you using

there is no error to be logged, the last line of code that is being called is the below:
[sender presentViewController:navController animated:NO completion:nil];
which is not opening any page.
I am using the latest FHSTwitterEngine.h/.m which is old already
//  Created by Nathaniel Symer on 8/22/12.

Well.. the date there is the date when the code was created.. not updated
Few things

Twitter app has nothing to do with this library
Please get the most recent code, currently 2.0.1 https://github.com/fhsjaagshs/FHSTwitterEngine/releases/tag/2.0.1 or cocoapods https://cocoapods.org/pods/FHSTwitterEngine
Change your code to log something

if (success) {
  NSLog("yay");
}
else {
  NSLog("noooo");
}

Better yet you could add logging to showOAuthLoginControllerFromViewController
Please report back

Well.. the date there is the date when the code was created.. not updated
Few things

Twitter app has nothing to do with this library
Please get the most recent code, currently 2.0.1 https://github.com/fhsjaagshs/FHSTwitterEngine/releases/tag/2.0.1 or cocoapods https://cocoapods.org/pods/FHSTwitterEngine
Change your code to log something

if (success) {
  NSLog("yay");
}
else {
  NSLog("noooo");
}

Better yet you could add logging to showOAuthLoginControllerFromViewController
Please report back

i got the code from the link you added, but didnt find the method showOAuthLoginControllerFromViewController anymore
is it replaced with another one?

Please refer to the documentation http://cocoadocs.org/docsets/FHSTwitterEngine, looks like you are looking for loginControllerWithCompletionHandler

can we have skype call so i can describe the issue i m facing and the result i m hoping to have with the library?


chore(ReleaseInfo): update to v5.12.0

I like the selection a lot. It goes without saying (and we link to the changelog) that there is loads of other things we worked on :).

LGTM

@barmac :arrow_right: :heavy_check_mark: :smile:


Dissasemble regexes in rules 941210 and 941220

Motivation
All regexes should be generated using regexp-assembly.
Proposed solution
Dissasemble the regexp in rules 941210 and 941220.

This should stay on the todo list.


Variables can't be used in asset globs

This is what I'm attempting to do:
{
  "buildCommand": "yarn dist",
  "github": {
    "release": true,
    "assets": [
      "dist/*${version}.exe",
      "dist/*${version}-mac.zip"
    ],
    "tokenRef": "RELEASE_IT_TOKEN"
  }
}

WARNING octokit releases#uploadAssets: assets not found (glob "dist/*${version}.exe,dist/*${version}-mac.zip" relative to /Users/beau/p/tracking-tool)

Hi, @beaugunderson. That is expected behavior. Only in command hooks (and soon commits messages and tags) variables are substituted.
Not sure whether adding this feature as you're trying to use it is a good idea as it may get muddy or conflict with glob syntax/characters.

@webpro makes sense to me! i worked around by adding rm -rf dist/ in my package.json script.dist entry so that prior versions will never exist, and then just used dist/*.exe and dist/*-mac.zip for the globs :+1:


feat: add known Metro Symbols

These symbols should be easily used with Image(metroName: "name") in the same manner as Image(systemName: "name") provides access to system symbols.
Fixes #28

This is draft as the SVGs in this library are not rescaling the way SVGs provided by Apple do.

Codecov Report

Merging #31 (5734c56) into main (a3506d4) will increase coverage by 2.63%.
The diff coverage is 38.46%.

@@            Coverage Diff             @@
##             main      #31      +/-   ##
==========================================
+ Coverage   61.74%   64.37%   +2.63%
==========================================
  Files           4        5       +1
  Lines         149      160      +11
==========================================
+ Hits           92      103      +11
  Misses         57       57

Impacted Files
Coverage Δ

Sources/WMATAUI/WMATAUI.swift
39.43% <20.00%> (+7.69%)
:arrow_up:

Sources/WMATAUI/Image+Extension.swift
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a3506d4...5734c56. Read the comment docs.


Drop the requirement for square-shaped inputs

Currently DARTS and STEPS require the inputs to have a square shape. However, the FFT can be computed from inputs of any shape, and therefore this requirement could be relaxed. This would require implementing more general versions of the bandpass filters and noise generators.

Commit c930fbe5b33ef862b72308602765dad55650c743 closes this issue.


windows compat

removes termios
#59

Hey thanks for this, can you describe the before and after behavior of this for someone who doesn't have access to Windows (me)?

You mind if I do it to speed things up?
current behavior
trying to run this application on windows fails with an ModuleNotFoundError: No module named 'termios' error.
expected behavior
the application should start without errors.
p.s. @Akababa interesting work on your fork ❤

You mind if I do it to speed things up?
current behavior
trying to run this application on windows fails with an ModuleNotFoundError: No module named 'termios' error.
expected behavior
the application should start without errors.
p.s. @Akababa interesting work on your fork ❤

Thank u @oafx

Thanks @oafx and @ben-bay ! I was busy today so I'm grateful for your help.


presenceStatusIndicator: Subscribe presence to more deeper in the state.

Presence state changes in every few minutes. So to make sure that this
components only gets re-rendered when presence of relevant person
changes, subscribe it deeper in the presence state.

Thanks @jainkuniya !

This is an example where createSelector doesn't do us any good:

The selector isn't doing any work.
It isn't making a new object.

So let's leave that bit out.

Let's name this ...ForEmail. That helps us keep a consistent pattern:

getFooByBar gets a map of all foo, indexed by bar.
getFooForBar takes bar as a second parameter, and gets just the one foo that corresponds to that bar.

We only recently started having selectors of that second type; see narrowsSelectors for existing examples.

Hmm, but actually: given that createSelector isn't helpful, we can just write something like this:

  presence: getPresence(state)[props.email],

That's what we have in ActivityText now, for example.

Want to do the same thing for usersByEmail while you're here?


How to convert MASConstraint to NSLayoutConstraint?

Hi,
How to convert MASConstraint to NSLayoutConstraint?
I would like use JHChainableAnimations:
self.topConstraint = [NSLayoutConstraint ...];
myView.makeConstraint(self.topConstraint, 50).animate(1.0);
Thanks

@RobertNNms we don't really support this, a MASConstraint can represent several layout constraints and its not advisable to mess with the underlying NSLayoutConstraints.
What are you trying to accomplish?

I would like use "JHChainableAnimations" (https://github.com/jhurray/JHChainableAnimations) rather than "UIView animateWithDuration" with Mansory, for animation resize.


Use private VPC link between Elastic Cloud and our pipeline

In order to reduce pipeline costs we should route requests via a VPC endpoint, rather than via our NAT gateways.
TODO:

[ ] Configure access credentials using existing scripts
[ ] Ensure access/credentials are configurable in the pipeline stack
[ ] Run a test reindex demonstrating that requests are being routed correctly

In order to reduce pipeline costs we should route requests via a VPC endpoint, rather than via our NAT gateways.
TODO:

[ ] Configure access credentials using existing scripts
[ ] Ensure access/credentials are configurable in the pipeline stack
[ ] Run a test reindex demonstrating that requests are being routed correctly

Quick back-of-the-napkin calculation: the works index is ~30GB, and the images index is ~20GB. Total is ~50GB.
We know a reindex will typically ingest the same Work/Image multiple times (due to embedding relations, merging, etc.) so the data we sent over NAT Gateway during a reindex was probably several times that.
Meanwhile, the logging data from across the entire platform in a week with two reindexes is only ~60GB.
I've got PrivateLink working for the catalogue services, but I'm going to skip doing it for logging for now. It's a bigger infra change for a smaller saving.

Quick back-of-the-napkin calculation: the works index is ~30GB, and the images index is ~20GB. Total is ~50GB.
We know a reindex will typically ingest the same Work/Image multiple times (due to embedding relations, merging, etc.) so the data we sent over NAT Gateway during a reindex was probably several times that.
Meanwhile, the logging data from across the entire platform in a week with two reindexes is only ~60GB.
I've got PrivateLink working for the catalogue services, but I'm going to skip doing it for logging for now. It's a bigger infra change for a smaller saving.


Selected  option set by v-model not working in IE

Version
2.4.2
Reproduction link
http://jsfiddle.net/yMv7y/3267/
Steps to reproduce
Set a select element's v-model to one of its options value objects in a component mounted callback.
What is expected?
The selected option should match the  tags v-model value
What is actually happening?
Dropdown value remains empty

dup of #6209


Allow easier title customization

We currently hardcode a BRANDLESS_DOCSET_TITLE title identifier that consumers of this theme are expected to replace. When https://github.com/realm/jazzy/pull/1077/ lands in a release, we should adopt that instead.
Here’s an example of how we currently replace BRANDLESS_DOCSET_TITLE, from the Maps SDK.
/cc @captainbarbosa

This theme currently needs two different titles, one branded and the other unbranded (substituting the logo for the brand name).  Neither quite matches the module name.

Fixed in #9.


Update sap_checklist.en.json

I modified about "Identity and Access"

Hey @NaokiIgarashi thanks for your update! Unfortunately there are some conflicts with your PR, could you resolve them? Otherwise I cannot merge...

@erjosito Please marge my request.


Installing Openai-dotnet to a .NET Standard project gives error

Installing Openai-dotnet package to a .NET Standard 2.0 project gives following error
NU1108: Cycle detected.
OpenAI -> OpenAI (>= 2.0.0-beta.2).
Package restore failed. Rolling back package changes for 'OpenAI'.
It is detecting some cyclic dependency

Hello, @cjkarande! Can you share a bit more on how you set up the netstandard2.0 project to reproduce this? Creating a new one myself just now (dotnet new console, dotnet add package OpenAI --prerelease, modify .csproj for <TargetFramework>netstandard2.0</TargetFramework>), I see restore and build working as intended. Is there more detail about the reported cycle in the output?

@cjkarande do you have another version of this package OpenAI or another package that references the older version of this package included in the project? We're going to need more information about what else is in your package graph in order to be helpful.

@trrwilson sorry for the incomplete info. I am trying to install it in a .Net Standard 2.0 project which is part of Xamarin.Forms Mobile App solution. I am not using a Console App
@Petermarcu I am installing this package for the 1st time in a newly created Xamarin.Forms project.

That is strange. The cycle has nothing in the middle, it just says the package is referencing itself. How are you adding the reference? Can you share what's in your csproj?

Does your project happen to also be named OpenAI?

Superb @Petermarcu, that was the problem....Thanks a ton.

Does your project happen to also be named OpenAI?


Is authentication safe client-side?

'Blazor WebAssembly apps run on the client. Authorization is only used to determine which UI options to show. Since client-side checks can be modified or bypassed by a user, a Blazor WebAssembly app can't enforce authorization access rules.'
I previously asked a question (https://docs.microsoft.com/en-us/aspnet/core/security/blazor/webassembly/standalone-with-authentication-library?view=aspnetcore-3.1 Blazor WASM with Auth Lib groups and roles) regarding authorization client-side.
From this, I assume no authorization should be conducted client-side. If the [Authorize] tag can be bypassed, then is authentication itself secure client-side? Perhaps someone can manipulate GetAuthenticationStateAsync() to create a new claims principal with IsAuthenticated set to true? Should Blazor WASM only be used for displaying insensitive content to unauthenticated users?

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

ID: c9942b0a-a7fb-0d34-9201-af0963affa9e
Version Independent ID: 19770710-5225-a1ea-e082-65da6ba4a49a
Content: ASP.NET Core Blazor authentication and authorization
Content Source: aspnetcore/security/blazor/index.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @guardrex
Microsoft Alias: riande

Unless a check is made server-side (e.g., typically server-side checks made via an API) before sending content to the client, yes, that's right. Content sent to the client can't be secured after it's sent. Further details are in the WASM Overview topic.
https://docs.microsoft.com/aspnet/core/security/blazor/webassembly/


Fix #114

As mentioned in https://github.com/resin-io/resin-cli/pull/127, let's move this checking to the SDK!


Misc web

preload fonts
muck about with the manifest.json (not really useful)
fix a couple linting warnings (object missing alt)
add the heart emoji shape.

add a second search interface (copying the FCB)
add a pan galactic tool search

neat! :tada:


KAFKA-4575: ensure topic created before starting sink for ConnectDistributedTest.test_pause_resume_sink

Otherwise in this test the sink task goes through the pause/resume cycle with 0 assigned partitions, since the default metadata refresh interval is quite long

@ewencp for review

@shikhar The idea for the fix seems sound, but should we update VerifiableSourceTask to implement commitRecord and check for properly acked messages? My concern is that just seeing a message generated by the task isn't actually enough to be sure the topic has been created. (In practice, I'm pretty sure we'd not see an issue with this, but as we're closing a few correctness gaps in system tests that came back to bite us, it seems better to get a fix that properly guarantees correctness.) VerifiableProducer logs ack info to do validation like this, but VerifiableSourceTask currently doesn't...

@ewencp that makes sense, I made this update and verified the test passes locally.

@shikhar This looks good. The only issue is that we also use VerifiableSource.messages() in test_bounce as well to do validation of sequence numbers. Since we record each twice now, I think we might need to tweak that test or change it to use the new committed_messages() method.

@ewencp good catch, I will update that.

@ewencp updated

LGTM


cannot stat 'build-server/server/scrcpy-server': No such file or directory make: *** [Makefile.CrossWindows:100: dist-win32] Error 1

I am getting below error while building crosswindows distribution file on ubuntu 19.10 please help:
Configuring config.h using configuration
Build targets in project: 2
Found ninja-1.9.0 at /usr/bin/ninja
ninja -C "build-win32-noconsole"
ninja: Entering directory `build-win32-noconsole'
[25/25] Linking target app/scrcpy.exe.
mkdir -p "dist/scrcpy-win32"
cp "build-server"/server/scrcpy-server "dist/scrcpy-win32/"
cp: cannot stat 'build-server/server/scrcpy-server': No such file or directory
make: *** [Makefile.CrossWindows:100: dist-win32] Error 1

I had the same problem, but you can find scrcpy.exe in scrcpy/build-win32/app, it means that complise server fail

What command did you execute exacly?

make -f Makefile.CrossWindows

cp "build-server"/server/scrcpy-server "dist/scrcpy-win32/"

It looks like it failed to build the server.
Do you have any failure related to gradle before the logs you posted? (did you install the Android SDK?)
But even if this is the case, it should fail before, without continuing…
What are the results of:
ls build-server
find -name scrcpy-server

cp "build-server"/server/scrcpy-server "dist/scrcpy-win32/"

It looks like it failed to build the server.
Do you have any failure related to gradle before the logs you posted? (did you install the Android SDK?)
But even if this is the case, it should fail before, without continuing…
What are the results of:
ls build-server
find -name scrcpy-server

Yes I got the error as SDK location not found. Define location with an ANDROID_SDK_ROOT environment variable or by setting the sdk.dir path in your project's local properties file at '/home/lamarca/Downloads/scrcpy/local.properties'.
Then I made a local. Properties file in scrcpy directory and tried to compile the project using
make -f Makefile.CrossWindows
Then I got the above error. My Android sdk location is set in env variables of ubuntu still I got the above error.

Then I made a local.properties file in scrcpy directory and tried to compile the project using
make -f Makefile.CrossWindows

Do you have gradle logs when executing that command (suggesting that the server build have either succeeded or failed)?

Then I made a local.properties file in scrcpy directory and tried to compile the project using
make -f Makefile.CrossWindows

Do you have gradle-related logs when executing that command (suggesting that the server build have either succeeded or failed)?

here is the complete log after i run the makefile command:
Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details
BUILD SUCCESSFUL in 51s
2 actionable tasks: 2 up-to-date
rm -rf "build-server" "build-win32" "build-win64"
"build-win32-noconsole" "build-win64-noconsole" "dist"
[ -d "build-server" ] || ( mkdir "build-server" &&
meson "build-server"
--buildtype release -Dcompile_app=false )
The Meson build system
Version: 0.51.2
Source dir: /home/jhachandan/scrcpy-master
Build dir: /home/jhachandan/scrcpy-master/build-server
Build type: native build
Project name: scrcpy
Project version: 1.12.1
C compiler for the host machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Program ./scripts/build-wrapper.sh found: YES (/home/jhachandan/scrcpy-master/server/./scripts/build-wrapper.sh)
WARNING: Project targetting '>= 0.37' but tried to use feature introduced in '0.48.0': console arg in custom_target
DEPRECATION: build_always is deprecated. Combine build_by_default and build_always_stale instead.
Build targets in project: 2
WARNING: Project specifies a minimum meson_version '>= 0.37' but uses features which were added in newer versions:

0.48.0: {'console arg in custom_target'}
Found ninja-1.9.0 at /usr/bin/ninja
ninja -C "build-server"
ninja: Entering directory build-server' [0/1] Generating scrcpy-server with a custom command. (not invoking gradle, since we are root) make -C prebuilt-deps prepare-win32 make[1]: Entering directory '/home/jhachandan/scrcpy-master/prebuilt-deps' SDL2-2.0.10: found ffmpeg-4.2.1-win32-shared: found ffmpeg-4.2.1-win32-dev: found platform-tools: found make[1]: Leaving directory '/home/jhachandan/scrcpy-master/prebuilt-deps' [ -d "build-win32" ] || ( mkdir "build-win32" && \  meson "build-win32" \  	--cross-file cross_win32.txt \  	--buildtype release --strip -Db_lto=true \  	-Dcrossbuild_windows=true \  	-Dcompile_server=false \  	-Dportable=true ) The Meson build system Version: 0.51.2 Source dir: /home/jhachandan/scrcpy-master Build dir: /home/jhachandan/scrcpy-master/build-win32 Build type: cross build Project name: scrcpy Project version: 1.12.1 C compiler for the build machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008") C compiler for the host machine: /usr/bin/i686-w64-mingw32-gcc (gcc 9.2.0 "i686-w64-mingw32-gcc (GCC) 9.2-win32 20191008") Host machine cpu family: x86 Host machine cpu: i686 Target machine cpu family: x86 Target machine cpu: i686 Build machine cpu family: x86_64 Build machine cpu: x86_64 Library SDL2 found: YES Library SDL2main found: YES Library avcodec-58 found: YES Library avformat-58 found: YES Library avutil-56 found: YES Library mingw32 found: YES Library ws2_32 found: YES Configuring config.h using configuration Build targets in project: 2 Found ninja-1.9.0 at /usr/bin/ninja ninja -C "build-win32" ninja: Entering directory build-win32'
[25/25] Linking target app/scrcpy.exe.
[ -d "build-win32-noconsole" ] || ( mkdir "build-win32-noconsole" &&
meson "build-win32-noconsole"
--cross-file cross_win32.txt
--buildtype release --strip -Db_lto=true
-Dcrossbuild_windows=true
-Dcompile_server=false
-Dwindows_noconsole=true
-Dportable=true )
The Meson build system
Version: 0.51.2
Source dir: /home/jhachandan/scrcpy-master
Build dir: /home/jhachandan/scrcpy-master/build-win32-noconsole
Build type: cross build
Project name: scrcpy
Project version: 1.12.1
C compiler for the build machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008")
C compiler for the host machine: /usr/bin/i686-w64-mingw32-gcc (gcc 9.2.0 "i686-w64-mingw32-gcc (GCC) 9.2-win32 20191008")
Host machine cpu family: x86
Host machine cpu: i686
Target machine cpu family: x86
Target machine cpu: i686
Build machine cpu family: x86_64
Build machine cpu: x86_64
Library SDL2 found: YES
Library SDL2main found: YES
Library avcodec-58 found: YES
Library avformat-58 found: YES
Library avutil-56 found: YES
Library mingw32 found: YES
Library ws2_32 found: YES
Configuring config.h using configuration
Build targets in project: 2
Found ninja-1.9.0 at /usr/bin/ninja
ninja -C "build-win32-noconsole"
ninja: Entering directory `build-win32-noconsole'
[25/25] Linking target app/scrcpy.exe.
mkdir -p "dist/scrcpy-win32"
cp "build-server"/server/scrcpy-server "dist/scrcpy-win32/"
cp: cannot stat 'build-server/server/scrcpy-server': No such file or directory
make: *** [Makefile.CrossWindows:100: dist-win32] Error 1

Is it generated somewhere else?
From your scrcpy root directory:
find -name scrcpy-server

Is it generated somewhere else?
From your scrcpy root directory:
find -name scrcpy-server

only meson logs are available:
Build started at 2020-02-29T08:33:56.735396
Main binary: /usr/bin/python3
Python system: Linux
The Meson build system
Version: 0.51.2
Source dir: /home/jhachandan/scrcpy-master
Build dir: /home/jhachandan/scrcpy-master/build-server
Build type: native build
Project name: scrcpy
Project version: 1.12.1
No CFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc -pipe -D_FILE_OFFSET_BITS=64 /home/jhachandan/scrcpy-master/build-server/meson-private/sanitycheckc.c -o /home/jhachandan/scrcpy-master/build-server/meson-private/sanitycheckc.exe
Sanity check compile stdout:

Sanity check compile stderr:

Running test binary command: /home/jhachandan/scrcpy-master/build-server/meson-private/sanitycheckc.exe
No CFLAGS in the environment, not changing global flags.
No LDFLAGS in the environment, not changing global flags.
No CPPFLAGS in the environment, not changing global flags.
Sanity testing C compiler: cc
Is cross compiler: False.
Sanity check compiler command line: cc -pipe -D_FILE_OFFSET_BITS=64 /home/jhachandan/scrcpy-master/build-server/meson-private/sanitycheckc.c -o /home/jhachandan/scrcpy-master/build-server/meson-private/sanitycheckc.exe
Sanity check compile stdout:

Sanity check compile stderr:

Running test binary command: /home/jhachandan/scrcpy-master/build-server/meson-private/sanitycheckc.exe
C compiler for the host machine: cc (gcc 9.2.1 "cc (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008")
Build machine cpu family: x86_64
Build machine cpu: x86_64
Program ./scripts/build-wrapper.sh found: YES (/home/jhachandan/scrcpy-master/server/./scripts/build-wrapper.sh)
WARNING: Project targetting '>= 0.37' but tried to use feature introduced in '0.48.0': console arg in custom_target
DEPRECATION: build_always is deprecated. Combine build_by_default and build_always_stale instead.
Build targets in project: 2
WARNING: Project specifies a minimum meson_version '>= 0.37' but uses features which were added in newer versions:

0.48.0: {'console arg in custom_target'}
Found ninja-1.9.0 at /usr/bin/ninja

only meson logs are available

What is the result of find -name scrcpy-server? It does not return anything?
This is weird because you get BUILD SUCCESSFUL in 51s for the gradle build.

only meson logs are available

What is the result of find -name scrcpy-server? It does not return anything?
This is weird because you get BUILD SUCCESSFUL in 51s for the gradle build.

yes i am getting empty response i think the server file is not generated is it possible to use prebuilt server while using the make -f Makefile.CrossWindows command to make distribution for windows.

problem is solved i solved the problem by defining ANDROID_SDK_ROOT in my environment variables and removing ANDROID_HOME from the environment variables.
Thanks


thinking about allowing factories to extend others

This would mostly be for polymorphic models.
My first thought was to do something like this:
  FactoryGuy.define('bread', {
   default: {
   },
  });
  FactoryGuy.define('wheat', {
   extends: 'bread',
   default: {
   },
  });

 If anyone has other ideas, let me know.

Version 1.1.0 allows for extending .. voila!


Rewrite congestion controller

This PR removes use of the TCP-based congestion controller with a newer simpler one that is written for QUIC.
A few caveats: (1)  I've spot tested with simulations, but need to write new tests in t, (2) persistent congestion is not yet handled, and (3) app-limited periods are not yet handled.
(This is based off PR #100, so I would recommend diff-ing against that, if github doesn't automagically do it.)

Merged PR #100, the base of this PR is change to master.


updated bitbar (1.9.1)

Changes to a cask
Editing an existing cask

[x] Commit message includes cask’s name (and new version, if applicable).
[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.

Merged as cfc6757b81ba17a0e53ad9385ebf058153a048e8.


more consistent CentComm naming

About the PR
this pr changes a lot of the public-facing instances of "centcom" to"centcomm"
Why / Balance
i wanted to start learning git and this seemed like an easy first pr.
Changelog
:cl:

fix: Fixed inconsistent naming of CentComm.

CentCom is the correct spelling though.

https://github.com/space-wizards/space-station-14/pull/21108#issuecomment-1771962208 i got it from here

I think we should go with "CentComn" instead. An n is kinda like half of an m, so it's a good compromise that everyone will surely be happy with.

https://en.wikipedia.org/wiki/United_States_Central_Command

We in command are saving up cents with 1 letter shorter name, think about the budget!

Why would CentCom have a second M?

Everyone hush, I'm trying to talk on the centercom.

wtf actually merged, that's crazy


Data clean

@LinguList the data is now ready. CLDF run and errors taken car of.

Can you please delete all files that don't belong to the repo? That is: pycache DS_Store, etc.


Moving pseudopotential functionality to a different package

Currently I've included some pseudopotential functionality, but in order to make the package relatively modular and avoid introducing scope creep, I think it's probably best to remove some of the pseudopotential functionality from here and create a new package that can work with pseudopotentials as a standalone.
I think the amount of pseudopotential functionality is minimal and nobody here is actually using it yet, so removing it from here should not be a concern in terms of breaking changes. However, I would not like to introduce a pseudopotential package as a dependency of Xtal.jl - it should be fully usable without pseudopotential features (I anticipate some people just need to convert files or do some datagrid math not involving potentials at all).

PR #66 will resolve this issue.

This change is going into version 0.2.0 (see the next branch for all development there).


Add Necromancer Ascendancy offerings support.

For example Duskdawn unique staff + block from Bone Offering. Cast speed from Flesh offering and extra chaos damage from Spirit offering.

The next update will add support for these.


[TextField] Type password - duplicate icon in Edge

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯

I just made my login form using TextField with type password
But then I found these bug in my program
I thought thats my program error, but when I checked it in MUI documentation i found the same problem
Link : https://mui.com/components/text-fields/
Expected behavior 🤔

expected: eye icon in left doesnt appear
Steps to reproduce 🕹
Steps:

Leave the eye icon opened
Type something

Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

As far as I can see it works in https://mui.com/components/text-fields/#input-adornments

Can you share the steps you did to get to that state? I can't reproduce

@antonichandra  You can fix this by manually adding this to the <GlobalStyles>:

Try it out

according to the edge document

By default, the password reveal button is inserted into the Shadow DOM of all HTML input elements that have the type set to "password". Starting with Microsoft Edge Version 87, users or enterprises can disable this feature globally. Web designers and developers should expect most Microsoft Edge users to have the default experience.

just like HelpMe-Pls's saying, you can add below code and remove the password reveal control
::-ms-reveal {
    display: none;
}


Support composite query keys.

I have just started using this package. It works great. And I noticed that the query keys are not identical to react-query. For now I am building query key strings with different ids like 'posts-$id'. And I would like to propose feature for supporting composite keys like react-query. I think this will be beneficial for searching and filtering logic. I want to have something like
`
var filter = {
'query': 'food',
'page': 1,
'limit': 10,
'filters': [
{
'rating': 3.5
}
]
};
var query = Query(['posts', filter], queryFn: fetchPosts);
`

I have thought about adding this type of key as I agree it is useful in react query. However, I also find that it adds some hidden magic and is more difficult to understand and reason about.
In react query I use the composite keys mainly for invalidating or updating a group of queries at once. In this package, Cached Query, you can achieve the same effect by passing a "filter function" parameter to the update function.
CachedQuery.instance.updateQuery(
  updateFn: (dynamic oldData){
    if(oldData is Todo){
      return oldData?.copyWith(complete: true);
    }
  },
  filterFn: (unencodedKey, key) => key.startsWith("todos/"),
);

This gives the flexibility of filtering queries to the user of the package. You can add your keys in any way that can be converted using jsonEncode.
For example, using your filter map as the query key, you can update only queries where page is equal to 10.
CachedQuery.instance.updateQuery(
  ...
  filterFn: (unencodedKey, key) => unencodedKey["page"] == 10,
);

Are there any other areas you use react query keys that the approach I mentioned doesn't work?


Move some V2 items into zedcloudCtx, etc

Signed-off-by: Naiming Shen<EMAIL_ADDRESS>
move some of the V2 variables into context
handle the cloud cert change in diag getting config

updated the signingcert names

yetus failed on "Artifact not found", not sure what that is.

Just re-trigger the build.. These are usually intermittent issues.
Thanks,
Kalyan
On Mon, Mar 16, 2020 at 11:53 AM naiming-zededa<EMAIL_ADDRESS>wrote:

yetus failed on "Artifact not found", not sure what that is.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lf-edge/eve/pull/746#issuecomment-599705011, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AK4GJOLSR4SSVLTXJUCKYK3RHZYSJANCNFSM4LGYTXIA
.


[Nessus Export] Allow the ability to export all scans from a single day (not just the latest)

Sometimes a scan is run more than once a day. This issue will track how this can be accomplished and implemented.
It may be best to add some additional flag to make this doable and easy to understand:
-Nessus_Export_All_Scan_History : null
Works as designed today, where only the latest scan for the scan ID is exported (using -Nessus_Export_Day).
-Nessus_Export_All_Scan_History : "within_date_scope"
Exports all scans based on the -Nessus_Export_Day. Example is if there were 4 scans completed on a single day, this will export all 4 scans for that day if supplied using the Nessus Export Day parameter.
-Nessus_Export_All_Scan_History : "unlimited"
Export all scans for the given scan name. This will export the entire history of scans across multiple days. Typically this option wouldn't be used frequently if used in scheduled fashion.
Other considerations:
Today scan names when exported are as follows - 2024_04_23-Credentialed scan-12.nessus- [Year_Month_Day-Scan Name-Scan ID-optionally configurable text.nessus]
This is a problem for when exporting scans over and over again because the name will already exist. To overcome this obstacle the history ID must be included in the file name so there won't be any future collisions.
Also, change the current -Export_Day to -Nessus_Scan_Export_Day for better alignment to the Nessus Scan feature set of the script.

[ ] Rename Export_Day to Nessus_Scan_Export_Day
[ ] Add Nessus_Export_All_Scans option

Simplified export all scans by using a simply true or false/null for the new variable.

Also added unlimited or within scan date options for more use cases.


won't load netatmo and sonos

Hi,
neither do I know if its plugin specific issues nor if these two are related.

Something was stuck in the cache somehow. A fresh os makes it work now.


WIP: Storage migration

What this PR does / why we need it:
This PR implements the proposal for storage migration. For the design details, please, take a look at the design document.
This work is in early stage but it is an example implementation for the design document
TODOs:

[ ] feature gate for Storage Migration
[ ] webhook admission for validating the storage migration request
[ ] current, implementation only covers manual specification of PVCs. In a second round, KubeVirt should be able to cr eate automatically the PVC based on the destination storage class
[ ] implement the reclaim policy for the source PVC on a successful migration
[ ] a couple of commits are lefts as TODOs
[ ] implementation of unit and functional tests
[ ] maybe something else based on the design discussion

Example how this works:
VM:
---
apiVersion: kubevirt.io/v1
kind: VirtualMachine
metadata:
  labels:
    kubevirt.io/vm: vm-dv
  name: vm-dv
spec:
  dataVolumeTemplates:
  - metadata:
      creationTimestamp: null
      name: src-pvc
    spec:
      pvc:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 2Gi
        storageClassName: local
      source:
        registry:
          url: docker://registry:5000/kubevirt/alpine-container-disk-demo:devel
  running: true
  template:
    metadata:
      labels:
        kubevirt.io/vm: vm-dv
    spec:
      domain:
        devices:
          disks:
          - disk:
              bus: virtio
            name: datavolumedisk1
          interfaces:
          - masquerade: {}
            name: default
        resources:
          requests:
            memory: 128Mi
      terminationGracePeriodSeconds: 0
      volumes:
      - dataVolume:
          name: src-pvc
        name: datavolumedisk1
      networks:
      - name: default
        pod: {}

Storage migration:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: dest-pvc
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 2Gi
  storageClassName: local
  volumeMode: Filesystem
---
apiVersion: storage.kubevirt.io/v1alpha1
kind: StorageMigration
metadata:
  name: sc-mig
spec:
  vmiName: vm-dv
  migratedVolume:
  - sourcePvc: src-pvc
    destinationPvc: dest-pvc

As result, after the migration, the VM and VMI spec will be updated with the destination PVC.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A storage migration was considered and is present (link)
[ ] Community: Announcement to kubevirt-dev was considered

Release note:

Ability to migrate the storage while the VM is running

This PR needs to modify the migrate XML to add the slices and replace filesystem and block volumes. This PR contains the changes in https://github.com/kubevirt/kubevirt/pull/10847

@vasiliy-ul @awels I have updated this PR based on our recent discussion on the volume migration proposal. This is ready for a first round of review.

/test pull-kubevirt-unit-test

Rechanged to draft to fix flakiness in the storage tests

/test pull-kubevirt-e2e-k8s-1.27-sig-storage

It seems the new commit solves the flakes. I'll move this to ready for review

/test pull-kubevirt-e2e-k8s-1.28-sig-storage

Closing in favor of https://github.com/kubevirt/kubevirt/pull/11533 and the new design proposal


Hi, and few remarks about minmea lib =)

Hi guys! You're doing awesome project, but here's some small troubles i've got on windows platform with code::blocks & mingw (dunno what about stm32, but i think that iar will get the same troubles):

Loop variables was declared inside of loop header
Such construct requests at least C99 mode. It's better to declare all necessary variables before function's code for compability with C89 so the code looks like:

int foo(void) {
    int i = 0;
    for (i = 0; ...; ...) {
        ...
    }
}

Seems like timegm function isn't presented in windows libraries, so here it's code (which is obviously very bad for embedded because of multiplication):

static int is_leap(unsigned y) {
    y += 1900;
    return (y % 4) == 0 && ((y % 100) != 0 || (y % 400) == 0);
}

time_t timegm(struct tm *tm) {
    static const unsigned ndays[2][12] = {
            {31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31},
            {31, 29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31}
    };

    time_t res = 0;
    int i;

    for (i = 70; i < tm->tm_year; ++i)
        res += is_leap(i) ? 366 : 365;

    for (i = 0; i < tm->tm_mon; ++i)
        res += ndays[is_leap(tm->tm_year)][i];

    res += tm->tm_mday - 1;
    res *= 24;
    res += tm->tm_hour;
    res *= 60;
    res += tm->tm_min;
    res *= 60;
    res += tm->tm_sec;
    return res;
}

Look at me. Now look at your compiler. Now look at me. Now look at the calendar. It's 2014. C89 is 25 years old. Everything is possible when your IDE's default settings suck. I'm on a horse.

C99 is widely supported, and writing in that 1989 dialect is no fun at all. Here's how to set it under Code::Blocks:

Have you tried building with -Dtimegm=_mkgmtime or -Dtimegm=mktime?

Add Dtimegm=mktime worked for STM32 platform compiled by ARMCALNG.


Add additional test cases for bill and validation message

Accidentally merged the previous PR without fixing the requested changes. Changes added in this PR.

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

Coverage data is based on head (5cffc86) compared to base (8260ab4).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #103   +/-   ##
=========================================
  Coverage     76.14%   76.14%
  Complexity      451      451
=========================================
  Files            71       71
  Lines          1283     1283
  Branches        132      132
=========================================
  Hits            977      977
  Misses          277      277
  Partials         29       29

Impacted Files
Coverage Δ

src/main/java/seedu/guest/model/guest/Bill.java
84.61% <ø> (ø)

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

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


[docs] Delete embedded documentation in favor of docs/

After discussion, we've determined that maintaining the documentation inside the port where fixing typos requires republishing the port, is problematic.
This PR performs one final regenerate run (including the missing port helpers vcpkg-qmake and vcpkg-get-python-modules) and then purges all embedded documentation in the script helpers and port helpers.
This PR does not touch any of the content of this documentation -- that will be done in follow-up PRs.
Drive-by for the helper ports:

"documentation": "https://vcpkg.io/en/docs/README.html"
"license": "MIT"
Use include_guard(GLOBAL) in all script files
Make sure any persistent variables are saved to the cache

strictly speaking you cannot have the docs of scripts ports in docs/ since the docs probably depend on the version which gets installed.

We did discuss that as well (it was one of my concerns).
Our approach moving forward will be to include "Added in version x-y-z" annotations where appropriate in future documentation changes. We won't be "backdating" any existing documentation.

Rather than adding an empty regenerate.ps1 can you just delete this block that was calling it?
https://github.com/microsoft/vcpkg/blob/203f5f3bef28ffccb667fdce97bcde7a88aba4e6/scripts/azure-pipelines/windows/azure-pipelines.yml#L49-L56

I'm going to go ahead and merge since the previous c645bad passed.

From draft to world rebuild in less than 24 hours... But I'm glad this documentation update barrier is removed.


Azure: make endpoints resources

This better handles command timeouts - the call to create the endpoint
may time out but eventually succeed in creating the endpoint. Using a resource
allows the test to proceed if the endpoint exists, even if the last attempt to
create the endpoint failed.

@hildrum / @ehankland  - could you take a look?

LGTM


[AutoPR sqlvirtualmachine/resource-manager] [Portal Generated] Review request for Microsoft.SqlVirtualMachine to add version 2017-03-01-preview

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4740

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/3641


Integrate Internet Speed Indicator

Description of the new feature / enhancement
The integration of an Internet Speed Indicator directly into the Windows Taskbar would be a highly useful feature for users who want real-time insights into their internet connectivity. This simple but powerful addition could greatly benefit individuals in various scenarios, including remote work, online gaming, and general internet usage.
Scenario when this would be used?
The Internet Speed Indicator in the Windows Taskbar would provide users with a quick and easily accessible display of their current internet speed. This feature would enable users to monitor their internet connection without the need for third-party applications, enhancing the overall usability of PowerToys.
Supporting information
No response

/dup #828


[Navigator] Guard navigator.state.routeStack from accidental mutation

A minor improvement suggestion: Navigator.getCurrentRoutes() probably shouldn't return its routeStack backing array as-is, because the caller may mutate it, causing the internal state of the navigator to go out of sync. Instead a shallow copy of the routes should be returned.
I stumbled on this problem in my app by attempting to read the navigator state as follows:
let routes = Navigator.getCurrentRoutes();
let current = routes.pop();
let previous = routes.pop();

Which led to an exception at next navigation event.
CLA signed.

Seems reasonable to me, up to @ericvicenti :smile:

@facebook-github-bot import


Eliminate hardcoding from submission

e.g.

Do you remember what this was for? You have been working on submission, so maybe you are addressing it as part of #277 ?

I think this was in reference to May23.jsx, at the time I thought that was how each contest was uploaded. We should actually try to save that in Contests proper... is that not an option though for some reason?

If you mean the Contests table, the prompt column stores Reddit markdown, which is generally enough to show a formatted prompt (and easy enough to copy from the prompt they post to Reddit).
For this contest, they wanted collapsible sections for each city of the 25 in the contest, and IIRC some images, which is beyond the capabilities of markdown, so I ended up having to build a custom thing just for this contest and was planning on deleting afterwards, but never got around to it.
I have #149 open to investigate getting some CMS solution that we can use for any content like prompts, the instructions at the top of the voting thread, contest submission rules, etc. One option is just adding HTML files to firebase and reading them from there, but long term I want some WYSIWYG editor, so the mods can update the prompt themselves and I won't have to add it manually to the table. If you have any thoughts on that, feel free to add them to that issue.

I completely agree, I think my initial comment was to suggest storing HTML styling.
My only thought is to not use the same editor Reddit uses.


Make sure we propagate 'async' down to inherited designed initializes.

Fixes a crash reported via rdar://80353441.

@swift-ci please smoke test and merge

@swift-ci please smoke test Linux


Unable to open characters in V10 Prototype 3

Click the character, nothing happens. Error log:
Foundry VTT | Rendering DCCActorSheetCleric
commons.js:4889 Error: You are accessing the DCCActor#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.
at logCompatibilityWarning (commons.js:4878:19)
at Function._logV10CompatibilityWarning (commons.js:5716:14)
at DCCActor.get data [as data] (commons.js:5616:24)
at DCCActorSheetCleric.getData (actor-sheet.js:60:28)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logV10CompatibilityWarning @ commons.js:5716
get data @ commons.js:5616
getData @ actor-sheet.js:60
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing the DCCActor#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.
at logCompatibilityWarning (commons.js:4878:19)
at Function._logV10CompatibilityWarning (commons.js:5716:14)
at DCCActor.get data [as data] (commons.js:5616:24)
at DCCActorSheetCleric.getData (actor-sheet.js:61:27)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logV10CompatibilityWarning @ commons.js:5716
get data @ commons.js:5616
getData @ actor-sheet.js:61
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing the DCCActor#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.
at logCompatibilityWarning (commons.js:4878:19)
at Function._logV10CompatibilityWarning (commons.js:5716:14)
at DCCActor.get data [as data] (commons.js:5616:24)
at DCCActorSheetCleric.getData (actor-sheet.js:62:29)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logV10CompatibilityWarning @ commons.js:5716
get data @ commons.js:5616
getData @ actor-sheet.js:62
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing DCCActor#data which has been migrated to DCCActor#system
Deprecated since Version 10
Backwards-compatible support will be removed in Version 12
at logCompatibilityWarning (commons.js:4878:19)
at Function._logDataFieldMigration (commons.js:5705:14)
at Object.get (commons.js:5669:18)
at DCCActorSheetCleric.getData (actor-sheet.js:62:34)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logDataFieldMigration @ commons.js:5705
get @ commons.js:5669
getData @ actor-sheet.js:62
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing the DCCActor#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.
at logCompatibilityWarning (commons.js:4878:19)
at Function._logV10CompatibilityWarning (commons.js:5716:14)
at DCCActor.get data [as data] (commons.js:5616:24)
at DCCActorSheetCleric.getData (actor-sheet.js:63:27)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logV10CompatibilityWarning @ commons.js:5716
get data @ commons.js:5616
getData @ actor-sheet.js:63
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing the DCCActor#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.
at logCompatibilityWarning (commons.js:4878:19)
at Function._logV10CompatibilityWarning (commons.js:5716:14)
at DCCActor.get data [as data] (commons.js:5616:24)
at DCCActorSheetCleric.getData (actor-sheet.js:67:42)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logV10CompatibilityWarning @ commons.js:5716
get data @ commons.js:5616
getData @ actor-sheet.js:67
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing the DCCActor#data object which is no longer used. Since V10 the Document class and its contained DataModel are merged into a combined data structure. You should now reference keys which were previously contained within the data object directly.
at logCompatibilityWarning (commons.js:4878:19)
at Function._logV10CompatibilityWarning (commons.js:5716:14)
at DCCActor.get data [as data] (commons.js:5616:24)
at DCCActorSheetCleric.getData (actor-sheet.js:68:41)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logV10CompatibilityWarning @ commons.js:5716
get data @ commons.js:5616
getData @ actor-sheet.js:68
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
commons.js:4889 Error: You are accessing DCCActor#data which has been migrated to DCCActor#system
Deprecated since Version 10
Backwards-compatible support will be removed in Version 12
at logCompatibilityWarning (commons.js:4878:19)
at Function._logDataFieldMigration (commons.js:5705:14)
at Object.get (commons.js:5669:18)
at DCCActorSheetCleric.getData (actor-sheet.js:68:46)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
logCompatibilityWarning @ commons.js:4889
_logDataFieldMigration @ commons.js:5705
get @ commons.js:5669
getData @ actor-sheet.js:68
getData @ actor-sheets-dcc.js:16
_render @ foundry.js:4102
_render @ foundry.js:4826
render @ foundry.js:4061
render @ foundry.js:5324
_onClickDocumentName @ foundry.js:52625
dispatch @ jquery.min.js:2
v.handle @ jquery.min.js:2
foundry.js:386 TypeError: Cannot set properties of undefined (setting 'img')
at DCCActorSheetCleric.getData (actor-sheet.js:73:27)
at DCCActorSheetCleric.getData (actor-sheets-dcc.js:16:24)
at DCCActorSheetCleric._render (foundry.js:4102:29)
at DCCActorSheetCleric._render (foundry.js:4826:17)
at DCCActorSheetCleric.render (foundry.js:4061:10)
at DCCActorSheetCleric.render (foundry.js:5324:18)
at ActorDirectory._onClickDocumentName (foundry.js:52625:16)
at HTMLOListElement.dispatch (jquery.min.js:2:43064)
at HTMLOListElement.v.handle (jquery.min.js:2:41048)

Sheets now open on the v10 branch (v0.34.0 ).


Add Mono-enabled builds

Is it possible to enable the mono module so we can use C# scripts with these builds?

As the Mono module must be statically built into the editor binary, no. I may add Mono-enabled builds one day, but it would still be difficult to add.

I would really appreciate the mono builds.

Well my PC can build it, it just takes almost 2 hours for the whole process.
It would definitely be better if I could just download it.

Mono support would be a huge help!

with 4.0 shaping up, it would be awesome to be able to test mono builds easily

Please don't bump issues without contributing significant new information. Use the :+1: reaction button on the first post instead.

Edit: Mono builds will have to wait until headless support is implemented so that Mono glue can be generated on CI.

Can you explain this?

Can you explain this?

To build a Mono-enabled binary, you need to generate Mono glue first using a special-purpose Godot binary. This special-purpose Godot binary spawns a window, and that means it requires a X server with hardware acceleration to be available at the time you're generating the Mono glue.