do not fail the whole test if the curl command returns a non-zero status

we expect if to fail, and want to retry it until it is successful.  it
can fail because the web app has not had time to start up yet.  the
current code throws a runtime exception on a non-zero return code, which
causes this test to fail too fast and incorrectly.
I was investigating the failure in test  oracle.kubernetes.operator.ItDomainInImage.testDomainInImageUsingWdt.  Here is the relevant part of the log:
<04-26-2020 09:39:52> <INFO> <oracle.kubernetes.operator.BaseTest testAdminT3Channel> <Inside testAdminT3Channel>
<04-26-2020 09:39:52> <INFO> <oracle.kubernetes.operator.utils.TestUtils kubectlexecNoCheck> <Command to call kubectl sh file kubectl -n itdomaininimage-domainns-2 exec -it itdomaininimage-domain-9-admin-server  -- mkdir -p /u01/oracle/apps>
<04-26-2020 09:39:53> <INFO> <oracle.kubernetes.operator.utils.TestUtils kubectlexecNoCheck> <Command to call kubectl sh file kubectl -n itdomaininimage-domainns-2 exec -it itdomaininimage-domain-9-admin-server  -- bash -c 'cat > /u01/oracle/apps/testwebapp.war' < /home/opc/jenkins/workspace/weblogic-kubernetes-operator-nightly-full-test/integration-tests/../src/integration-tests/apps/testwebapp.war>
<04-26-2020 09:39:53> <INFO> <oracle.kubernetes.operator.utils.TestUtils kubectlexecNoCheck> <Command to call kubectl sh file kubectl -n itdomaininimage-domainns-2 exec -it itdomaininimage-domain-9-admin-server  -- bash -c 'cat > /u01/oracle/apps/deploywebapp.py' < /home/opc/jenkins/workspace/weblogic-kubernetes-operator-nightly-full-test/integration-tests/../integration-tests/src/test/resources/deploywebapp.py>
<04-26-2020 09:39:53> <INFO> <oracle.kubernetes.operator.utils.TestUtils kubectlexecNoCheck> <Command to call kubectl sh file kubectl -n itdomaininimage-domainns-2 exec -it itdomaininimage-domain-9-admin-server  -- bash -c 'cat > /u01/oracle/apps/callpyscript.sh' < /home/opc/jenkins/workspace/weblogic-kubernetes-operator-nightly-full-test/integration-tests/../integration-tests/src/test/resources/callpyscript.sh>
<04-26-2020 09:39:54> <INFO> <oracle.kubernetes.operator.utils.TestUtils callShellScriptByExecToPod> <Command to call kubectl sh file kubectl -n itdomaininimage-domainns-2 exec -it itdomaininimage-domain-9-admin-server -- bash -c 'chmod +x -R /u01/oracle/apps  && /u01/oracle/apps/callpyscript.sh /u01/oracle/apps/deploywebapp.py weblogic welcome1 t3://itdomaininimage-domain-9-admin-server:31009 testwebapp /u01/oracle/apps/testwebapp.war cluster-1'>
<04-26-2020 09:40:09> <INFO> <oracle.kubernetes.operator.utils.Domain callWebAppAndVerifyLoadBalancing> <Curl cmd with response code curl --silent --noproxy '*'  -H 'host: itdomaininimage-domain-9.org' http://<IP_ADDRESS>:30305/testwebapp/ --write-out %{http_code} -o /dev/null>
<04-26-2020 09:40:09> <INFO> <oracle.kubernetes.operator.utils.Domain callWebAppAndVerifyLoadBalancing> <Curl cmd curl --silent --noproxy '*'  -H 'host: itdomaininimage-domain-9.org' http://<IP_ADDRESS>:30305/testwebapp/>
<04-26-2020 09:40:44> <INFO> <oracle.kubernetes.operator.utils.TestUtils exec> <
Command curl --silent --noproxy '*'  -H 'host: itdomaininimage-domain-9.org' http://<IP_ADDRESS>:30305/testwebapp/ --write-out %{http_code} -o /dev/null
return value: 7
stderr =
stdout = 000>
<04-26-2020 09:40:44> <INFO> <oracle.kubernetes.operator.utils.TestUtils exec> <
Command docker rmi -f phx.ocir.io/weblogick8s/itdomaininimage-dominimage:2020-04-26-1587893612794
return value: 0
stderr =
stdout = Untagged: phx.ocir.io/weblogick8s/itdomaininimage-dominimage:2020-04-26-1587893612794

you can see that as soon as it gets that curl rc=7, which is coming from BaseTest.java:617
domain.callWebAppAndVerifyLoadBalancing(TESTWEBAPP, verifyLoadBalancing);
it immediately goes on to the finally/cleanup which starts by deleting the image
      testBasicUseCases(domain, false);
      testClusterScaling(operator1, domain, true);
      testCompletedSuccessfully = true;
    } finally {
      // if (domain != null && (JENKINS || testCompletedSuccessfully)) {
      if (domain != null && testCompletedSuccessfully) {
        TestUtils.deleteWeblogicDomainResources(domain.getDomainUid());
        TestUtils.verifyAfterDeletion(domain);
      }
      if (domain != null) {
        domain.deleteImage();
      }
    }
    LoggerHelper.getLocal().log(Level.INFO, "SUCCESS - " + testMethodName);
  }

so testClusterScaling() is failing silently and it goes to the finally
callWebAppAndVerifyLoadBalancing calls into callWebAppAndWaitTillReady which does this
private void callWebAppAndWaitTillReady(String curlCmd) throws Exception {
    for (int i = 0; i < maxIterations; i++) {
      ExecResult result = TestUtils.exec(curlCmd, true)
      String responseCode = result.stdout().trim();
      if (result.exitValue() != 0 || !responseCode.equals("200")) {

that TestUtils.exec() does this:
  public static ExecResult exec(String cmd, boolean debug) throws Exception {
    ExecResult result = ExecCommand.exec(cmd);
    if (result.exitValue() != 0 || debug) {
      LoggerHelper.getLocal().log(Level.INFO,
          "\nCommand "
              + cmd
              + "\nreturn value: "
              + result.exitValue()
              + "\nstderr = "
              + result.stderr()
              + "\nstdout = "
              + result.stdout());
    }
    if (result.exitValue() != 0) {
      throw new RuntimeException(
          "FAILURE: Command "
              + cmd
              + " failed with stderr = "
              + result.stderr()
              + " \n stdout = "
              + result.stdout());
    }
    return result;
  }

so you can see, since it got a rc=7 here, it just throws a RuntimeException and so the test fails
this is not what we want, we want to capture the rc and return it to the caller so they can decide whether or not to fail
of course this method is used everywhere - 45 callers :disappointed: -- so this is going to take some work to fix without breaking other things
a quick guess might be to change it to this
  public static ExecResult exec(String cmd, boolean debug) throws Exception {
    ExecResult result = ExecCommand.exec(cmd);
    if (result.exitValue() != 0 || debug) {
      LoggerHelper.getLocal().log(Level.INFO,
          "\nCommand "
              + cmd
              + "\nreturn value: "
              + result.exitValue()
              + "\nstderr = "
              + result.stderr()
              + "\nstdout = "
              + result.stdout());
      return result;
    }
    if (result.exitValue() != 0) {
      throw new RuntimeException(
          "FAILURE: Command "
              + cmd
              + " failed with stderr = "
              + result.stderr()
              + " \n stdout = "
              + result.stdout());
    }
    return result;
  }

but we will need to work through what all those 45 callers do...
a quick look tells me a lot of the set debug to true, so this wont work :disappointed:
we probably have to introduce a new argument to determine whether to fail on a non-zero rc
I am going to put in a hack for now to try to fix this one test

test run queued up https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-quicktest/1375

I have fixed this issue a while ago in this PR - https://github.com/oracle/weblogic-kubernetes-operator/pull/1385.
Looks like there was a bad merge which got the old code and created these issues/failures. I see this PR has the bad merge - https://github.com/oracle/weblogic-kubernetes-operator/pull/1478.
As you can see in my PR#1385, Domain.java has
  private void callWebAppAndWaitTillReady(String curlCmd) throws Exception {
    for (int i = 0; i < maxIterations; i++) {
      ExecResult result = ExecCommand.exec(curlCmd);

PR#1478, replaced this with old code
  private void callWebAppAndWaitTillReady(String curlCmd) throws Exception {
    for (int i = 0; i < maxIterations; i++) {
      ExecResult result = TestUtils.exec(curlCmd, true);

TestUtils.exec() throws exception for non-zero exit code, ExecCommand.exec() returns ExecResult in all cases.

test run with new code https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-quicktest-6/6/console


Convert all API endpoints from .io to .com

Since, devrant has successfully acquired devrant.com which promises to provide more stable endpoints compared to devrant.io , all API endpoints needs to be pointed to .com version

@aayush26 let me do it!

Check #22


Can you add an option to save the calculation history to a text file or an MD file?

When using my calculator, I need to save the history in a text file. However, since the only way to save it is by copying and pasting, it becomes impractical if the number of operations in the history is large. Additionally, only the result is copied, not the entire calculation.

I would like to take this request


A lot of Intune icons are missing, can these be added?

As the title suggests, can the Intune icons be added to?

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

ID: 6624d44c-f9f6-02f8-2c67-0f0637fed62e
Version Independent ID: 9346a8ff-bab5-be2c-9dc1-d546fda1efa9
Content: Azure Icons - Azure Architecture Center
Content Source: docs/icons/index.md
Service: architecture-center
GitHub Login: @doodlemania2
Microsoft Alias: pnp

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 413974

Just curious if MS is going to link up with this guy.
His stencil range is updated by scrips routinely, grabs the SVG from Azure icons then generates the icons.
https://github.com/David-Summers/Azure-Design
Scales, anchor points, and vision index searching work for his stencils.

The current version of the Azure icons pack contains eighteen updated Intune icons.
If you believe there are more missing icons, please create a new ticket and specify more details about the required icons. Thanks!
#please-close


How train model on other dataset with satellite images?

Hello, I'm interested in training your model on satellite images. Is this even possible? Or is the network created only for pictures of streets and premises?
If this is possible, please tell me how best to do this

Hi,

If you hope to train a relative disparity model, similar to Depth Anything, you are suggested to load the entire Depth Anything pre-trained parameters (including the encoder and decoder) for fine-tuning with your own satellite images.
If you hope to train a metric depth model, you are suggested to load the pre-trained encoder parameters of Depth Anything, and randomly initialize the decoder for fine-tuning with your own satellite images. We also use this principle to fine-tune foundation Depth Anything models for metric depth estimation. Please refer to here for details.

So if I need a metric depth model, then I should try training a zoedepth model with your checkpoints?
Or use the model that is in the link?  how will this model differ from the zoedepth model internally?
And how to initialize the decoder for fine tuning? In which file and line should this be done?

hi！i am also trying to train one depth model on satellite images, can we have a discussion about this?

Hi, yes, of course. Now i work with the network ZoeDepth (network
Depth-Anything based on this) and use URBAN SEMANTIC 3D DATASET. I need to
train ZoeDepth to get depth using only one image. To achieve this,
i've written code for image processing for DataLoader, added config and
changed the loss function (= 1 - r2).
If you have any questions, you can write me using this email address
ср, 3 апр. 2024 г. в 09:11, nabinanaa @.***>:

hi！i am also trying to train one depth model on satellite images, can we
have a discussion about this?
—
Reply to this email directly, view it on GitHub
https://github.com/LiheYoung/Depth-Anything/issues/123#issuecomment-2033493999,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL6A4IZQNKI3XQYGAQQRDMLY3N6ONAVCNFSM6AAAAABER3KMNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGQ4TGOJZHE
.
You are receiving this because you commented.Message ID:
@.***>

--
Валерия. Хорошего дня!

Hi all. Did you manage to get some good results when training on satellite data? And do you know of any avail. datasets that suite this usecase? I'm currently planning a project that requires high quality depth maps of buildings. The base model seems promising , and is useable for single buildings. But the height difference between neighbouring buildings is often not right.
Kind regards!


Emoji panel not opened when pressing CTRL-CMD-SPACE on macOs 12.x

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

VS Code Version: 1.64.2
OS Version: macOS 12.2.1

Steps to Reproduce:

In any VSCode window other than keyboard shortcuts, try pressing CTRL-CMD-SPACE to open the emoji picker. This doesn't do anything.

The shortcut in the edit window is defined as:

My keyboard does not have a function key. I am using a Mac Mini, and the original magic keyboard with num pad from 2017.

The system keyboard settings show as follows:

I was unable to find a way to customize the shortcut in VSCodes keyboard bindings.

I have reviewed some of the other bugs regarding similar issues, but none described my problem exactly, and the solutions offered there didn't apply to me, because of different OS, hardware, etc.

The keybinding for this menu entry comes from the OS and not from us. See https://github.com/microsoft/vscode/issues/135480#issuecomment-963946617 for how macOS settings would change the keybinding to a "globe" on a laptop with a touch bar. All of this happens outside of our application's control.

@alexdima This does not appear to be the case. I read that thread you referenced extensively. This is not the globe shortcut. macOS has the shortcut set to CTRL-CMD-SPACE, yet that does NOT work in VSCode.

@mikebronner VS Code doesn't have any code to handle the keybinding ctrl+cmd+space. VS Code doesn't have any code to change it to a "globe" on laptops with a touch bar. VS Code also doesn't have any code to change it to fn + E as it is in your screenshot. I acknowledge that you run into this (it is clear from your screenshot), and I'm sorry about it, but there's nothing we can do on our side to improve things. To my knowledge, it is the OS that assigns that keybinding.
Actually, it looks like even on my machine it is using sometimes the same unrealisable fn+E keybinding. I am using an external keyboard without a fn key. Here is for example Safari:

@alexdima Thank you for the update! I didn't realize this, my safari and other apps do the same! This was not that way some time ago, it must be something with macOS. arggg
Thanks for the clarification!


scipy.optimize.curve_fit would benefit from an option to use only monotonic functions

I would like to know if it is possible to get an option added to curve_fit that forces it to stick to monotonic functions (i.e. I am trying to get the best fitting monotonic polynomial for a given set of data).

curve_fit fits parameters in user-defined functions, and it does not
know anything about the structure of the function or meaning of the
parameters. What you ask is outside the scope of the routine (at least
in the problem formulation in the question above).
To do monotonic fitting, the responsibility of providing a suitable
parameterized function (possibly under specified bound constraints)
rests on the user.

I'm going to close this, but the discussion can continue of course.


fix(browser): Close browser targets before closing browser itself

This PR fixes #3673 by adding logic to browser.close to close the browser targets first before the browser. This seems to ignore the beforeunload dialog on the page and succesfully closes the browser.

Closing this PR in favor of upstream fix.

Ah yes that makes sense.


data handler shouldn't care if base-data isn't registered

https://github.com/node-base/base-compose/blob/master/lib/composition-handler.js#L40
@doowb this is more of a reminder, since we just talked about how app.cache.data is created on base, not by base-data

meaning it should probably just do merge on the *.cache.data objects

Should we check for *.data being an object and use that, or only merge *.cache.data?

could the implementor just do that in a custom iterator fn?


Once wasm-pack RFC #6 is completed, simplify bundling process

Until wasm-pack RFC #6 is implemented there is no available option to generate a single amalgamated JavaScript file

Related issues: https://github.com/rustwasm/wasm-pack/issues/699, https://github.com/rustwasm/wasm-bindgen/issues/1525, https://github.com/rustwasm/wasm-bindgen/pull/1295, https://github.com/rustwasm/rfcs/pull/6


Pop-up is blank

Do you want to request a feature, a new application detection or report a bug?
Report a bug
Is your issue about WebExtension driver (Chrome & Firefox), the website, the NPM driver or the bookmarklet ?
Don't know
What is the current behavior ?
When i click on the adress bar icon, it give me a blank with no information other than the app name.
If the current behavior is a bug, please provide the steps to reproduce and if possible a demo of the problem.
See here above.
What is the expected behavior ?
The information promised by the extension.
Which versions of Wappalyzer, and which browser / OS are affected by this issue ? Did this work in previous versions ?
Firefox 68.0.2
Trisquel 8 (based on ubuntu xenial)

Can you provide a screenshot please? Also, any particular reason why you're using the Bookmarklet over the extension?

I can't take a screenshot, the box disappears when i open the screenshot manager. The exact look of the box is a black header with the icon and the name of the app and the rest is blank.
I wanted to use it by curiosity.

I just realized, I think I read that as you were using the Bookmarklet, but that was a misread. Are you using the Firefox extension or the Bookmarklet?
If it's the Bookmarklet, it could be a CORS issue, but you'd have to open your developer console and tell us what errors you see.

The firefox extension.

Same problem here using Firefox 71.0b9 (64 bits)

Probably the same bug as https://github.com/AliasIO/wappalyzer/issues/2624

Probably the same bug as #2624

It is. Thanks.


Implementation of PyLayout::get_ptr is totally broken

It's returning the address of the local variable self, which then is destroyed when the function returns:
https://github.com/PyO3/pyo3/blob/fee755adbea01504d12cd858e2705608c10163a4/src/pycell.rs#L28-L30
Several of the other implementations appear to be broken in the same way.
Demo code:
pub struct S(u64);
pub struct PyAny;

impl S {
    pub unsafe fn get_ptr(&self) -> *mut PyAny {
        // body copied from implementations of PyLayout::get_ptr
        (&self) as *const &Self as *const _ as *mut _
    }
}

fn main() {
    let a = [S(0), S(0)];
    for i in &a {
        let i: &S = i; // i is of type `&S`
        // note objects' address is different
        dbg!(i as *const _);
        // totally broken: note same address printed for different objects
        // also, address computed is before the beginning of either object
        dbg!(unsafe { i.get_ptr() });
    }
}

(Playground)
Output:
   Compiling playground v0.0.1 (/playground)
    Finished release [optimized] target(s) in 0.45s
     Running `target/release/playground`
[src/main.rs:16] i as *const _ = 0x00007ffe69ee9cf0
[src/main.rs:19] unsafe { i.get_ptr() } = 0x00007ffe69ee9ce8
[src/main.rs:16] i as *const _ = 0x00007ffe69ee9cf8
[src/main.rs:19] unsafe { i.get_ptr() } = 0x00007ffe69ee9ce8

This can be regression tested for by seeing if get_ptr() returns an in-bounds pointer.

Thanks for reporting.
I'm a little concerned that the existing regression tests did not pick this up. From what you're showing above, any test that exercises this code reads the wrong memory, so I would hope that at least one test would have gone awry as a result..

The key point is PyCell is always on Python heap.
So &PyCell always refers an address of Python heap.

The problem is &PyCell simply a pointer but &PyAny is a pointer to a pointer, so when trying to make them have the same method, this kind of confusion happens.


contract read doesn't use default for durability like help said it does

What version are you using?
38d86504
What did you do?
$ soroban contract read --help
...
      --durability <DURABILITY>
          Storage entry durability

          [default: persistent]

          Possible values:
          - persistent: Persistent
          - temporary:  Temporary
...

$ soroban contract read --id C... --key hello

What did you expect to see?
$ soroban contract read --id C... --key hello
hello,world,1643,2075242

What did you see instead?
$ soroban contract read --id C... --key hello
error: the following required arguments were not provided:
  --durability <DURABILITY>

$ soroban contract read --id C... --key hello --durability persistent
hello,world,1643,2075242

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
With over four years in blockchain and backend development, I’ve worked across different ecosystems, handling everything from smart contract design to on-chain interactions and protocol integration. I focus on building secure, scalable, and reliable blockchain applications, managing both on-chain and off-chain infrastructure.
How I plan on tackling this issue
I'd check the logic behind the soraban contract read call to identify what’s causing it to malfunction, then proceed with implementing a fix.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have experience working with JavaScript, TypeScript, and Go, including CLI tools and command handling. My background in debugging and improving developer tools will allow me to effectively identify and resolve the issue in this project
How I plan on tackling this issue
I would start by inspecting the command-line argument parsing within the project, specifically focusing on how default values for --durability are handled. After identifying the root cause of why the default isn't being applied, I would correct the behavior to ensure the CLI adheres to the documented defaults, followed by adding tests to prevent future regressions

@gregemax Hi, I'm Emilie from OnlyDust, can you please reach out to me on telegram? @blumebee


Add netlink-based management interface support

This PR is the first of many that will come that aim to provide full netlink support to govdpa.
The VDPA management interface is netlink-based and should be used instead of inspecting the sysfs manually.
This PR:

Introduces a mock-able netlink layer that is able to interact with the kernel
Adds a MgmtDev entity that represents vdpa management devices and adds List and Get operations
Adds both integration and unit tests to MgmtDevs. Integration tests require a minimum kernel version and some modules installed and they are skipped if not available.

@Billy99 , want to take a look?

@lmilleri Can you take a look at this?

@lmilleri PTAL


Add a section to end of README with advice on updating Protobuf messages

@bocon13 Thanks for the proposed edits.  They all looked good to me, and I've merged them in.


Support symmetric NAT connections in Thin ICE

Thin ICE currently breaks connections that involve a symmetric NAT, because the cone-NAT side will only try to send traffic to the announced public endpoint, which is actually only accessible to the STUN server.
To make this work, we should make Churn accept incoming packets from any address, so long as they have the right credentials/encryption/etc., and then direct subsequent outbound packets to the new source address.
This does create a security concern: any attacker who can monitor packets on the link and replay them from a different source address could break the link.  To reduce the impact of this, we could ignore duplicate packets, so that the attack would only work if there were also subsequent packet reordering in the network.

Just so I'm clear: you're talking about cases where one side is behind a symmetric NAT? Is it true that this would have worked pre-Thin ICE?

Yes, that's what I'm talking about.  Pre-Thin ICE, and in WebRTC generally, a user with Address-Restricted Cone NAT, Full-Cone NAT, or a public IP address, can establish a connection to a peer behind Symmetric NAT.  With Thin ICE, that will currently not work.

This is important to support the same combinations of NAT types as we do without obfuscation. I believe the pull request is under review.


spdx: Handle reporting for empty license metadata

If no license metadata is found (i.e. debian-based images) Tern
does not generate reports that can be validated by SPDX
(http://<IP_ADDRESS>/app/validate/). This commit adds a few checks in
tern/formats/spdx/spdxtagvalue/generator.py to make sure that a license
value exists before trying to report the license information. Prior
to this commit the values for PackageDeclaredLicense and LicenseID
would report with "LicenseRef-" and no actual license value.
Additionally, this commit wraps the PackageCopyrightText value in
 in the case that the copyright statement is more than one
line.
Resolves #431
Signed-off-by: Rose Judge<EMAIL_ADDRESS>

If no license metadata is found (i.e. debian-based images) Tern
does not generate reports that can be validated by SPDX
(http://<IP_ADDRESS>/app/validate/).

Suggestion: "does not generate valid SPDX" and then list the reasons per SPDX spec 2.1

I found a couple of fixes for just the debian image that will pass validation:
This one gets rid of the SPDXRef error
def get_package_spdxref(package_obj):
     '''Given the package object, return an SPDX reference ID'''
-    return 'SPDXRef-{}'.format(package_obj.get_package_id())
+    return 'SPDXRef-{}'.format(
+        package_obj.get_package_id().replace(':', '-', 1))

This one gets rid of the dangling license block at the end:
@@ -130,7 +131,7 @@ def update_license_list(license_list, license_string):
     string is not in the list, add it'''
     licenses = get_package_licenses(license_string)
     for l in licenses:
-        if l not in license_list:
+        if l and l not in license_list:
             license_list.append(l)

Meanwhile, I have uncovered a bug in the debian based golang image. I'll file a bug on that one.

I found a couple of fixes for just the debian image that will pass validation:
This one gets rid of the SPDXRef error
def get_package_spdxref(package_obj):
     '''Given the package object, return an SPDX reference ID'''
-    return 'SPDXRef-{}'.format(package_obj.get_package_id())
+    return 'SPDXRef-{}'.format(
+        package_obj.get_package_id().replace(':', '-', 1))

Can you imagine any situation where changing the : to - might misrepresent the version for users who want to extract the version info directly from the Tern SPDX document? Or are we not worried about potential corner cases like that right now?

If no license metadata is found (i.e. debian-based images) Tern
does not generate reports that can be validated by SPDX
(http://<IP_ADDRESS>/app/validate/).

Suggestion: "does not generate valid SPDX" and then list the reasons per SPDX spec 2.1

I updated the commit message.

Can you imagine any situation where changing the : to - might misrepresent the version for users who want to extract the version info directly from the Tern SPDX document? Or are we not worried about potential corner cases like that right now?

The package version is whatever the package manager says it is. So in dpkg's case, that's the full debian version with epoch and everything. This is just for package id. The problem with changing this in the class's get_package_id method is that, as far as I can see, Debian is the only one that uses the :.  Perhaps a more long term solution would be to make get_package_id an SPDX format specific thing (as it is the only format that asks for a reference id for a package).

Can you imagine any situation where changing the : to - might misrepresent the version for users who want to extract the version info directly from the Tern SPDX document? Or are we not worried about potential corner cases like that right now?

The package version is whatever the package manager says it is. So in dpkg's case, that's the full debian version with epoch and everything. This is just for package id. The problem with changing this in the class's get_package_id method is that, as far as I can see, Debian is the only one that uses the :. Perhaps a more long term solution would be to make get_package_id an SPDX format specific thing (as it is the only format that asks for a reference id for a package).

Ah, I was confusing the package ID and package version. If this is just for the package ID it makes sense to me to change inside the spdx plugin generator.py since we still capture the epoch inside  PackageVersion.

If we supported other SPDX formatting in the future, would the colon after the epoch be an issue in the SPDXRef-* value or is the issue isolated to tag:value validation?

I think it is the tag-value parser. There is no space between the strings and the : so I don't see why the parser can't handle it. However, for unblocking us on validation, such as it is, I would rather have this change.
If all SPDX formatting would have an issue with the colon inside the SPDXRef-* value, I think we should do the string manipulation inside get_package_id. If the colon is only an issue for spdxtagvalue reporting, then I think we should localize the manipulation inside the respective plugin.

Thoughts?

Perhaps there is a different way of creating a "package identifier" for documents that can be constant for all types of formats. If not, I would rather if this whole function get removed from the class and moved to the formats.

Thoughts?

Perhaps there is a different way of creating a "package identifier" for documents that can be constant for all types of formats. If not, I would rather if this whole function get removed from the class and moved to the formats.

As was discussed on the Tern slack channel, if SPDX formats are the only formats requiring a unique package identifier we should move the get_package_id functionality to tern/formats/spdx/formats.py. I pushed a change for you to take a look at that also removes the get_pacakge_id code in tern/classes/package.py.


Modsecurity1.9 + nginx An unsolved problem

This is a particularly interesting question，When I use the nginx reverse proxy function,If you only add a server, and the port is used 80，Modsecurity works very well（Of course, early to solve a lot of problems, for example, can not upload more than 8K pictures such as the problem），But when I add a second server, the problem arises，When I add the second server to use the port is also 80，Can not post request, that post request will be blocked，

When the second server port is modified to non-80，Everything is fine，But the reverse proxy is the use of different domain names, the use of the same port, why use modsecurity will be such a problem, I hope we can help solve，

Hi @houhuijian,
Please have a try on ModSecurity-nginx connector -
https://github.com/SpiderLabs/ModSecurity-nginx


[Apps & Marketplace V2] Add or update annotations to support RKE2 clusters to all charts

Background
Before RKE2, on defining a cluster Rancher knew exactly what OSs are going to be contained in it; if it was a normal cluster, it was all Linux and if it was a Windows cluster, it was always Linux + Windows.
Therefore, we initially built an annotation on charts called catalog.cattle.io/os that would indicate whether this chart should be shown on a Linux or Windows cluster and that's what the catalog would show.
We never dealt with having to switch what charts are shown on the catalog; since the list of OSs is fixed on defining a cluster, the view on the catalog also used to be fixed.
We never dealt with any issues where a chart was installed but the cluster no longer supports it; it would never have been shown on the catalog to install in the first place.
Problem
In RKE2, the list of OSs that will be contained within a cluster is ambiguous; it is always possible to add or remove Windows / Linux nodes.
This is identical to the same issue we have in Apps & Marketplace V2 around node architectures; we don't have any mechanism for indicating a chart is supported or is permitted in a cluster that contains nodes with a given architecture.
Therefore, we currently have an undefined UX on the Rancher catalog for RKE2. Namely:

How do we know which charts are currently deployable onto or fully functional in a cluster?
If a chart is installed and the definition of a cluster switches (e.g. you introduce or remove OSs or archs from the cluster), how should the Rancher UI reconcile this behavior?

Solution
Every chart in rancher/charts should now add and support the following annotations:

catalog.cattle.io/deploys-on-os: indicates that a chart needs global.cattle.OS.enabled to be set for the OSs provided by a comma-separated list

No default

catalog.cattle.io/deploys-on-arch (NEW): indicates that a chart needs global.cattle.ARCH.enabled to be set for the archs provided by a comma-separated list

No default

catalog.cattle.io/permits-os: indicates that the chart is deployable onto clusters who have nodes with OSs provided by a comma-separated list

Default if not exists: catalog.cattle.io/permits-os: linux

catalog.cattle.io/permits-arch: indicates that the chart is deployable onto clusters who have nodes with archs provided by a comma-separated list

Default if not exists: catalog.cattle.io/permits-arch: amd64

This will be a two-step process:

Modifying all existing charts in the dev-v2.6 branch to add these annotations
Modifying annotations on all already released charts in the release-v2.6 branch to add these annotations, e.g. Monitoring

UI Integration
In coordination with these backend fixes, several tickets will be filed in rancher/dashboard in order to implement banners or different UXs based on the existence of these annotations:

https://github.com/rancher/dashboard/issues/5054
https://github.com/rancher/dashboard/issues/5055
https://github.com/rancher/dashboard/issues/5056
https://github.com/rancher/dashboard/issues/5057
https://github.com/rancher/dashboard/issues/5058

Note: UI should not blocked on backend to introduce these fixes since defaults for the annotations are outlined, however QA will be blocked on testing till UI and backend fixes are in.

https://github.com/rancher/rancher/issues/34057 will require us to do an OOB release for charts to update annotations anyways, so they should be done together in one PR

https://github.com/rancher/rancher/issues/36403 will be additional work we need to do anyways to get all of our charts tolerated on Windows clusters, so the first action item should be done in conjunction with these chart changes.

note: I edited the PR description to use catalog.cattle.io/deploys-on-os instead of catalog.cattle.io/os since catalog.cattle.io/os has an older definition that would break older Rancher setups if we choose to modify what it means.
Description should be up-to-date now with the expectations.

Talked to @PennyScissors about the default for catalog.cattle.io/deploys-on-os and we decided that there should be no default since it's only an annotation you need to add if you want to set the global.cattle.*.enabled field.
cc: @mantis-toboggan-md

Rancher Wins Upgrade has been dev validate. No upgrade needed to occur and the upgrader deamon did a noop. Everything installed and the card is displaying correctly.

Rancher Loggin Chart has been dev-validated. The card is displaying correctly, and everything has installed without error.

Harvester charts are displaying correctly.

Rancher Monitoring Chart has been dev-validated.

Longhorn card looks directly, and it only designates that it works for Linux only. If a Windows node is present it fails to deploy correctly, if the Windows node is cordoned, then everything installs without error.

SRIOV card looks correct. It installed just fine without a Windows node using the correct CNI. With a Windows node it partially installs and fails because multus isn't available.

Alerting card looks correct and installs without error.

GMSA card is correct and installed without error.

@sirredbeard looks like the changes we have made for the CIS Benchmark chart will be able to close this issue. https://github.com/rancher/rancher/issues/36265

External IP Webhook card looks correct and installs.

CIS chart card and installation are working.

Istio card and chart are working.
![istio-card](https://use

r-images.githubusercontent.com/1568133/155566565-e19561b8-02e6-4bd1-8070-7c4327a6f38f.png)

vsphere-cpi installation is working through helm install only. The vsphere-cpi chart cannot be deployed to an rke2 cluster that has the cluster cloud provider set to external, which is required for the out-of-tree vsphere charts as far as I am aware. If an rke2 cluster is provisioned with the cloud provider set to external it will not show the nodes as active until a cloud provider is deployed through helm that removes the following taint.
 taints:
  - effect: NoSchedule
    key: node.cloudprovider.kubernetes.io/uninitialized
    value: "true"

vsphere-csi card and chart is working.

This issue is going to be superceded by a previous dashboard issue which captures everything and has all PRs linked up. You can see context https://github.com/rancher/dashboard/issues/5137#issuecomment-1062323770

Awaiting updates from Arvind and PR https://github.com/rancher/charts/pull/1813

Unblocked. Pending dev validation by Team 3.


ERROR: Unable to communicate with master!

When running the following code in a ROS melodic package:
https://boschresearch.github.io/pcg_gazebo_pkgs/tutorials/simulation/model_generator/
I'm getting the following error even though Gazebo starts and master is running in another terminal:
~/ros/world_generator$ rosrun testing testing.py
ERROR: Unable to communicate with master!
2020-10-13 23:09:42,801 | WARNING | __init__ | Error testing Gazebo server, message=Command '['rostopic', 'list']' returned non-zero exit status 1
['gazebo']
Is Gazebo running: False
ERROR: Unable to communicate with master!
ERROR: Unable to communicate with master!
2020-10-13 23:09:43,169 | WARNING | __init__ | Error testing roscore, message=Command '['rostopic', 'list']' returned non-zero exit status 1
2020-10-13 23:09:43,170 | WARNING | __init__ | Error testing Gazebo server, message=Command '['rostopic', 'list']' returned non-zero exit status 1
ERROR: Unable to communicate with master!
2020-10-13 23:09:43,578 | WARNING | __init__ | Error testing roscore, message=Command '['rostopic', 'list']' returned non-zero exit status 1
Traceback (most recent call last):
  File "/home/andrestoga/ros/world_generator/src/packages/testing/scripts/testing.py", line 62, in <module>
    create_and_spawn(config)
  File "/home/andrestoga/ros/world_generator/src/packages/testing/scripts/testing.py", line 47, in create_and_spawn
    2 * random.random()])
  File "/home/andrestoga/.local/lib/python2.7/site-packages/pcg_gazebo/generators/world_generator.py", line 329, in spawn_model
    reference_frame)
  File "/home/andrestoga/.local/lib/python2.7/site-packages/pcg_gazebo/task_manager/gazebo_proxy.py", line 372, in spawn_sdf_model
    reference_frame)
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 442, in __call__
    return self.call(*args, **kwds)
  File "/opt/ros/melodic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 532, in call
    raise ServiceException("transport error completing service call: %s"%(str(e)))
rospy.service.ServiceException: transport error completing service call: receive_once[/gazebo/spawn_sdf_model]: DeserializationError cannot deserialize: unknown error handler name 'rosmsg'

The same error happens in a Jupyter notebook and a stand-alone python script with python2.7

Have you solved this problem?


'Brackets' middleware not nearly as trivial as node variant

If one wanted to write a "brackets" middleware that surrounded each bot response in a starting bracket ({) and an ending bracket (}) it looks like this in the node SDK (typescript):
public async receiveActivity(context: BotContext, next: () => Promise<void>): Promise<void> {
context.reply("{");
await next();
context.reply("}");
}

but in the .Net SDK, something this trivial isn't possible. You might think it'd look like this:
public async Task ReceiveActivity(IBotContext context, MiddlewareSet.NextDelegate next)
{
    context.Reply("{");
    await next();
    context.Reply("}");
}

but when you execute that you get:

So then you might start playing with TPL and try something like this:
public async Task ReceiveActivity(IBotContext context, MiddlewareSet.NextDelegate next)
{
    context.Reply("{");
    await next().ContinueWith(t => context.Reply("}"));
}

but to no avail.
The only way I was able to get this to work properly was to make the middleware both a Receive and a Send middleware like so:
public class Brackets : IMiddleware, IReceiveActivity, ISendActivity
{
    public async Task ReceiveActivity(IBotContext context, MiddlewareSet.NextDelegate next)
    {
        context.Reply("{");
        await next();
    }

    public async Task SendActivity(IBotContext context, IList<IActivity> activities, MiddlewareSet.NextDelegate next)
    {
        await next();
        context.Reply("}");
    }
}

which is far more complex than what we see in node.
This leads me to believe our middleware pipeline in dotnet still isn't quite right.
cc @cleemullins @ryanvolum @tomlm

Interesting. I'll look into this.

Not only is this an issue of complexity, but the C# workaround that Brandon wrote has different functionality. SendActivity gets called every time responses are flushed, so if a developer flushes responses mid-turn, you'd have multiple close brackets in this scenario.

I know what the bug here is. All the middleware in that pipeline is being run to completion, THEN the receive handler is called.
The receive handler should be called when the decent is completed, not when the ascent is completed.
Easy fix, fortunately.
I’ll have the fix + tests in by Monday.

From: Ryan<EMAIL_ADDRESS>Sent: Saturday, February 24, 2018 7:37:48 AM
To: Microsoft/botbuilder-dotnet
Cc: Chris Mullins; Assign
Subject: Re: [Microsoft/botbuilder-dotnet] 'Brackets' middleware not nearly as trivial as node variant (#184)
Not only is this an issue of complexity, but the C# workaround that Brandon wrote has different functionality. SendActivity gets called every time responses are flushed, so if a developer flushes responses mid-turn, you'd have multiple close brackets in this scenario.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fbotbuilder-dotnet%2Fissues%2F184%23issuecomment-368236640&data=04|01|cmullins%40microsoft.com|97418822edd3415bc10508d57b9c8f64|72f988bf86f141af91ab2d7cd011db47|1|0|636550834739047585|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=j9Pw4tTLQcyj%2BHoIoqvaRJAs9BMgQB2gm2O%2BnsL7kIs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABHICY9h0NrSsGfn2G5s4p9UZUMB7k3vks5tYCzMgaJpZM4SRkdJ&data=04|01|cmullins%40microsoft.com|97418822edd3415bc10508d57b9c8f64|72f988bf86f141af91ab2d7cd011db47|1|0|636550834739047585|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=Ya4ca1hGIjsEFY0DurhkRJ2Z3KBY3F6s1FTpLVY0Aqc%3D&reserved=0.

@cleemullins the single pipe middleware approach makes this a lot clearer as well. You run the leading edge for all of the middleware plugins, then execute the bots logic, and when that completes all of the trailing edges for plugins will run.
In the current multiple pipe model your left guessing a bit as to what the sequence should be. It's not intuitive for instance that you should hold open the ContextCreated() pipe until after OnReceive() completes.

@stevenic, you don't have to convince me the Single Pipeline model is cleaner. I'm there! :)

This has been fixed.


Pressing the up or down arrow on output channels change channel and focus

Currently if you keyboard focus to the output channel dropdown and press the up or down arrow, it will select the previous/next channel, but then also move focus into the channel. I would rather the focus to stay on the dropdpwn, so I could continue to use the up/down arrows.

Yeah I think this makes sense. Especial since the output is read only.  Current jumping focus behavior is weird and unexpected for keyboard users. I can look into fixing this.
fyi @sandy081

@eamodio can you please verify this? Thanks!

Perfect! Thanks!


Refactored yii\base\Theme. Added tests

Q
A

Is bugfix?
yes

New feature?
no

Breaks BC?
no

Tests pass?
yes

| Fixed issues  | comma-separated list of tickets # fixed by the PR, if any

Merged with adjustments.


Prepare release 3.0.0-beta.3

This isn't on PyPi atm

This isn't on PyPi atm

Not yet, we have problem in building
https://github.com/jazzband/django-auditlog/actions/runs/6860523927/job/18654499858

@jgillard it has been released!

Thank you 🙌


Websocket singnaling server.

Typically, Android development uses the websocket protocol to access the signaling server.(In web browser use WHIP)

@zoujiaqing In atm0s-media-server it not p2p then we use HTTP for signaling.


PowerToys - Plugin Loading Error

Microsoft PowerToys version
0.76.2
Installation method
GitHub
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
PowerToys - Plugin Loading Error
Fail to load plugin: Everything
Please report the bug t0 https•//aka.ms/powerToysReportBug. (For third-party plugins, please contact the plugin author.)

✔ Expected Behavior
Using Everything continually
❌ Actual Behavior
Computer displays "PowerToys - Plugin Loading Error"

"Fail to load plugin: Everything"
Other Software
No response

/bugreport

This is a community plugin and chances are due to we upgraded to .NET 8 and the version you may have installed isn’t.

PowerToysReport_2024-01-21-16-07-59.zip

Hi there!We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here?  Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
PowerToysReport_2024-01-21-16-07-59.zip

PowerToysReport_2024-11-12-21-48-33.zip


Issue with terminal plus

It is not working in Atom 1.23.6 X64. Terminal opens but it only shows blinking curser.

platformio-ide-terminal has thesame problem now. Remember that platformio-ide-terminal is a fork of terminal-plus.


Invalid Argument warning appearing when pressing tab.

VSCode Version: 1.18.1
OS Version: Windows 10 Pro Build 15063.726

Steps to Reproduce:

Attempt to autocomplete a parameter name when writing up a cmdlet call in a Powershell script by pressing tab. This was after a restart.

Screenshot of workspace attached, errors from console below.
ms-vscode.PowerShell] Cannot read property 'text' of undefined: TypeError: Cannot read property 'text' of undefined
	at HelpCompletionFeature.onEvent (C:\Users\james.woodbridge.SFS\.vscode\extensions\ms-vscode.powershell-1.5.1\out\src\features\HelpCompletion.js:34:100)
	at e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:84411)
	at e.fire (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:86133)
	at e.$acceptDirtyStateChanged (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427735)
	at t.e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:509443)
	at e._invokeHandler (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354786)
	at e._receiveOneMessage (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354476)
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:353503
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:355422
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:85128
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 [ms-vscode.PowerShell] Cannot read property 'text' of undefined: TypeError: Cannot read property 'text' of undefined
	at HelpCompletionFeature.onEvent (C:\Users\james.woodbridge.SFS\.vscode\extensions\ms-vscode.powershell-1.5.1\out\src\features\HelpCompletion.js:34:100)
	at e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:84411)
	at e.fire (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:86133)
	at e.$acceptDirtyStateChanged (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427735)
	at e.$acceptModelSaved (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427518)
	at t.e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:509443)
	at e._invokeHandler (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354786)
	at e._receiveOneMessage (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354476)
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:353503
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:355422
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 [ms-vscode.PowerShell] Cannot read property 'text' of undefined: TypeError: Cannot read property 'text' of undefined
	at HelpCompletionFeature.onEvent (C:\Users\james.woodbridge.SFS\.vscode\extensions\ms-vscode.powershell-1.5.1\out\src\features\HelpCompletion.js:34:100)
	at e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:84411)
	at e.fire (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:86133)
	at e.$acceptDirtyStateChanged (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427735)
	at t.e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:509443)
	at e._invokeHandler (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354786)
	at e._receiveOneMessage (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354476)
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:353503
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:355422
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:85128
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 [ms-vscode.PowerShell] Cannot read property 'text' of undefined: TypeError: Cannot read property 'text' of undefined
	at HelpCompletionFeature.onEvent (C:\Users\james.woodbridge.SFS\.vscode\extensions\ms-vscode.powershell-1.5.1\out\src\features\HelpCompletion.js:34:100)
	at e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:84411)
	at e.fire (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:86133)
	at e.$acceptDirtyStateChanged (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427735)
	at e.$acceptModelSaved (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427518)
	at t.e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:509443)
	at e._invokeHandler (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354786)
	at e._receiveOneMessage (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354476)
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:353503
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:355422
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 [ms-vscode.PowerShell] Cannot read property 'text' of undefined: TypeError: Cannot read property 'text' of undefined
	at HelpCompletionFeature.onEvent (C:\Users\james.woodbridge.SFS\.vscode\extensions\ms-vscode.powershell-1.5.1\out\src\features\HelpCompletion.js:34:100)
	at e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:84411)
	at e.fire (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:86133)
	at e.$acceptDirtyStateChanged (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:427735)
	at t.e.invoke (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:509443)
	at e._invokeHandler (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354786)
	at e._receiveOneMessage (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:354476)
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:353503
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:355422
	at c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:4:85128
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 Cannot read property '_placeholderDecorations' of undefined: TypeError: Cannot read property '_placeholderDecorations' of undefined
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1012928
    at t._changeDecorations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:951992)
    at t.changeDecorations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:951213)
    at t.changeDecorations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1308339)
    at e.merge (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1012782)
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1016800
    at e.pushEditOperation (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:426645)
    at t._pushEditOperations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:963461)
    at t.pushEditOperations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:962458)
    at e.merge (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1016691)
e.onUnexpectedError @ /C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10
/C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:10 Cannot read property 'startLineNumber' of null: TypeError: Cannot read property 'startLineNumber' of null
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1011239
    at t._changeDecorations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:951992)
    at t.changeDecorations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:951213)
    at e.move (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1011003)
    at e._move (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1017225)
    at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1016877
    at e.pushEditOperation (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:426645)
    at t._pushEditOperations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:963461)
    at t.pushEditOperations (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:962458)
    at e.merge (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:9:1016691)

This issue was moved to PowerShell/vscode-powershell#1118


Add use offset and length to copy read data.

add Read2 function to each platform.

Can you elaborate on why this should be part of the package?
If the caller wants to discard the first few bytes, then the caller can do that.  Add this point I don't understand why this should be part of the package.

Easy to read multiple and sequentially into the slice.

example:

I want this function because of the pcomm library in windows: PCOMM.H Line105
May be my solution not perfect.

If I understand the problem correctly, instead of doing Read2(buf, start, length), you can do Read(buf[start:start+length])

Oh, you are right.  It seems this pr can be closed


[WIP] Fedora packaging

Creating a fedora spec file to install spideroak through the package manager.
First time packaging a rust program so comments/critique would be appreciated

Need to also fix up where the binary is moved.


Invite code box is broken on web

The invite code box can't be clicked or typed into on web after the latest update (I'm using chrome)

Confirmed by https://www.reddit.com/r/BlueskySocial/comments/16cmkvv/bluesky_not_accepting_new_users

same here


fetching looking_for.ages sometimes fails

Changing line 34 of looking_for.py from:
_ages_re = re.compile(u'Ages ([0-9]{1,3})\u2013([0-9]{1,3})')

to:
_ages_re = re.compile(u' *Ages ([0-9]{1,3})\u2013([0-9]{1,3})')

seems to fix it.

I think OKCupid changed their html recently. This issue only showed up with a few profiles (out of 1000s).

Also, I just now came across a profile where p.looking_for.raw_fields['ages'] was '  Age 41  '. This can be accommodated by adding:
_ages_re2 = re.compile(u' *Age ([0-9]{1,3})')

near the top of looking_for.py, and editing the definition of ages later in that file like this:
  def ages(self):
      """The age range that the user is interested in."""
      match = self._ages_re.match(self.raw_fields.get('ages'))
    + if not match:
    +     match = self._ages_re2.match(self.raw_fields.get('ages'))
    +     return self.Ages(int(match.group(1)),int(match.group(1)))
      return self.Ages(int(match.group(1)), int(match.group(2)))

Cool, nice finds. Do you have an example profile that this happens with
Do you want to make a pull request? I'm happy to fix things I guess if not, but it would be greatly appreciated.

Ehh, I don't want to publish my own copy of the repository just for a few tiny patches. I can email you patches if you prefer.


Always getting NaNs in long training

I've been experimenting with the LION optimizer in your other (great) Imagen repository. I can share my anecdotal experience and combinations:

Models of different sizes 0.2B, 0.7B and 1B params.
Betas such as beta1 0.95 and beta2 0.98
Learning rates 1e-4, 3e-5 and 1e-5.
Triton kernel turned both True and False.

Training was indeed fast but unfortunately in the end always ended up yielding NaNs.
I think a potential issue could be how LION interacts with a warmup schedule; I am not sure if you're supposed to do warmup with this optimizer or not (which I always did).

I have same problem :(

same NaN issue with CosineAnnealing scheduler after the first epoch.

I've been experimenting with the LION optimizer in your other (great) Imagen repository. I can share my anecdotal experience and combinations:

Models of different sizes 0.2B, 0.7B and 1B params.
Betas such as beta1 0.95 and beta2 0.98
Learning rates 1e-4, 3e-5 and 1e-5.
Triton kernel turned both True and False.

Training was indeed fast but unfortunately in the end always ended up yielding NaNs.
I think a potential issue could be how LION interacts with a warmup schedule; I am not sure if you're supposed to do warmup with this optimizer or not (which I always did).

May I know the learning rate schedule you are using?

same issue,  i set a big weight decay to avoid it.  i suppose that  'update=symbol * lr' enlarging abs(parameter) while symbol not changing.

same here. sudden nan losses during 100 e training with onecyclelr


[Bug]: CITATION file cannot be parsed

Is there already an issue for this?

[X] I found no existing issue for this bug.

Describe the bug
The recent PR #135 did not work as expected:
"Your CITATION.cff file cannot be parsed. Make sure the formatting is correct. Learn more about CITATION files."
Screenshot
No response
Steps to reproduce
No response
Relevant log output
No response
Environment
- OS:
- Python:
- ampycloud:

Code of Conduct

[X] I agree to follow the ampycloud Code of Conduct.

@regDaniel: well .... 😭
I'll take a look and fix this asap.

oh no! but not overly urgent from my side of course.

Solved in #138.


v3 - trouble getting Background Sync to work (on mobile safari 11.3.1)

Have read #1222 but unable to get background sync working on mobile safari.
In service-worker.js I have:
const bgSyncPlugin = new workbox.backgroundSync.Plugin("req-queue", {
    maxRetentionTime: 24 * 60 * 1,
    callbacks: {
      queueDidReplay: showNotification
      // other types of callbacks could go here
    }
  });

  const networkWithBackgroundSync = new workbox.strategies.NetworkOnly({
    plugins: [bgSyncPlugin]
  });
  console.log("in service-worker. registering routes to bgsync queue");
  workbox.routing.registerRoute(/\/*/, networkWithBackgroundSync, "POST");
  workbox.routing.registerRoute(/\/*/, networkWithBackgroundSync, "PUT");
} else {
  console.log(`Boo! Workbox didn't load 😬`);
}

In index.html:
<script>
    if ('serviceWorker' in navigator) {
      navigator.serviceWorker.register('service-worker.js')
        .then(() => console.log('service worker installed'))
        .catch(err => console.error('Error', err));
    }
  </script>

When starting the app, console reports that service worker is installed, but I'm not getting the workbox message. True enough, fetch requests are not being queued in IndexedDB. I can cinform that an object store req-queue is created.
Also opened an SO question
Help please? 😄

@jeffposnick, is it true that there's a fallback strategy in place as mentioned in the docs? And if so, is it expected to work on iOS Safari 11.4+?

It also implements a fallback strategy for browsers that don't yet implement BackgroundSync.
https://developers.google.com/web/tools/workbox/modules/workbox-background-sync

And reading further:

Browsers that don't support the BackgroundSync API will retry the queue every time the service worker is started up.

I believe I see this strategy used in Firefox 62 when reloading the page after a failed fetch event and subsequent storage in the queue. From the console:

workbox Background sync replaying without background sync event

However, this same behavior is not observed in iOS Safari 11.4 (whereas other Workbox plugins are working normally).
For Reference, here's the code (working in Chrome and Firefox):
  const bgSyncExample = new workbox.backgroundSync.Plugin('exampleQueue', {
    maxRetentionTime: 2 * 24 * 60 // Retry for max of 48 Hours
  });

  workbox.routing.registerRoute(
    /\/api\/.*\/*.json/,
    workbox.strategies.networkOnly({
      plugins: [bgSyncExample]
    }),
    'POST'
  );

CC: @philipwalton

Any updates on this? I'm running into the same issue with Android chrome not creating an indexdb database.

@kdesimini, Are you specifically referring to the BackgroundSync module not creating an IndexedDB on a failed fetch event?
If not, please open a new issue with more details on your problem.
If yes, which browser/version is failing? (Chrome for Android or Android Browser?)
If you haven't already, you can check browser support for IndexedDB and Background Sync.

As I reported in https://github.com/GoogleChrome/workbox/issues/1908, the Safari-specific issue reported here may be due to IndexedDB bugs in Safari. If that's the case this problem will hopefully be solved when we make that change.

I'm going to close this as I believe the issue has been resolved. Please feel free to ping this thread if you're still having issues and I can re-open.


How does one use the sessions feature to resume transporter to resume tailing data from mongodb after crash

Hi, it seems #116 has been merged into master which implements the sessions feature to store the progress of sync.
If my transporter is closed during a sync, how can I use this feature to resume it?

:+1:

right now none of the adaptors have implemented the functionality to make use of the session store, we hope to have that work going soon.

@jipperinbham any updates here? anything we can do to help contribute?

+1 happy to contribute as well.

Any updates here ?

the work needed to make this possible is being tracked in https://github.com/compose/transporter/issues/33 but the current focus is still getting adaptor stability in place.


Previous hand rays are visible when blooming out and back in

Describe the bug
Hand rays getting stuck if you "bloom" out of the app and going back.  So you can see 3 or more hand rays at the same time.
To reproduce
On device, in app, if you hit the home button with hand rays visible and then bloom to shell. And open the app the previous hand rays are visible and new ones come up.
Expected behavior
Only new hand rays are visible
Your Setup (please complete the following information)

Unity Version 2019.1.1
MRTK Version v2.0.0

Target Platform (please complete the following information)

HoloLens 2

Marking as Urgency-Soon because it is a user-visible defect.

@julenka  is this something you can fix, or should this go to luis?

I caaI think either of us could do it, I'm happy to do it. I've got quite a number of issues on me, I'm currently doing this one: https://github.com/microsoft/MixedRealityToolkit-Unity/issues/4176. Might be good to give to Luis if he is not actively working on urgency-soon issues. But otherwise I can keep it on me.

This seems to happen also with finger pointers, not just hand rays.
There is a KeyAlreadyExists exception thrown in OnSourceDetected in MixedRealityInputModule (refresh version), changing the file to version from mrtk_development branch prevents exception but pointers are still stuck.

Great! It's on me right now, I'm currently on #4176 but will look at this as soon as that PR is out. If it's P0 urgency-now issue, we may want to try finding somebody else to look at it, since I'll probably only have the PR for #4176 out by mid-day today.

Started on this.

Hi @mgrman I am actually not able to repro this on the latest mrtk_development branch, on my particular HoloLens 2 device. Could you please verify that you are seeing this behavior in the HandInteractionAllExamples scene in the latest mrtk_development? You could also send me your application package and I can test if it is fixed in my OS version (perhaps there was an OS level change to fix application on pause not working that may have fixed this issue).

this is happening in v2 refresh for us. would you recommend then updating to mrtk_development?

I will test with mrtk_development update and report back

Also verified that the finger cursors correctly disappear in the handinteractionallexamples scene

mrtk_development did not help, I will try with default profile

Can you confirm that in your mrtk_development branch that in the HandInteractionExamples scene the rays do not disappear? If we can verify that then we know there is a difference between the example implementation and your implementaiton.

Marking this as no repro because it does not reproduce in the MRTK example scene, however it does reproduce in the customer application. The issue might be with the mgrman's application itself, not MRTK.

ok, I will do further investigations on our side. Seem we can reproduce it with Unity 2018.3 and 2019.1.

I further verified that this does not repro in 2018.3 IL2CPP release build, I think the issue is unfortunately with the customer application, not MRTK.


add state to ingress list and describe

Signed-off-by: Stephanie<EMAIL_ADDRESS>What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/area url
/kind feature
/area devfile

Documentation changes: Please include [skip ci] in your commit message as well
/kind documentation
[skip ci]

What does does this PR do / why we need it:
This PR adds state for ingresses when runningurl list and url describe.
This PR also modifies the existing integration tests since the expected output has been change for url list and url describe
Which issue(s) this PR fixes:
Fixes #2787
Fixes https://github.com/openshift/odo/issues/2983
How to test changes / Special notes to the reviewer:
Automation Tests:
simply run make test-cmd-devfile-url
$ make test-cmd-devfile-url
ginkgo  -randomizeAllSpecs -slowSpecThreshold=120 -timeout 7200s -nodes=2 -focus="odo devfile url command tests" tests/integration/devfile/
Running Suite: Devfile Suite
============================
Random Seed:<PHONE_NUMBER> - Will randomize all specs
Will run 53 specs

Running in parallel across 2 nodes

SSSSSSSSSSSSSSSSSSSSSSSS•SS•SSSSS•SS•SSSSSSSSSSS•S•••
Ran 8 of 53 Specs in 223.524 seconds
SUCCESS! -- 8 Passed | 0 Failed | 0 Pending | 45 Skipped

Ginkgo ran 1 suite in 3m46.272474203s
Test Suite Passed

Manual Tests
odo preference set experimental true
odo create java-spring-boot
odo url create ingressurl1 --host <IP_ADDRESS>.com --ingress --secure

Run odo url list should see the state of the url is Not Pushed
$ odo url list
Found the following URLs for component java-spring-boot
NAME            STATE          URL                                 PORT     SECURE
ingressurl1     Not Pushed     https://ingressurl<IP_ADDRESS>.4.com     8080     true

There are local changes. Please run 'odo push'.

Run odo url list -o json should see the json format
odo url list -o json
{
    "kind": "List",
    "apiVersion": "odo.dev/v1alpha1",
    "metadata": {},
    "items": [
        {
            "kind": "url",
            "apiVersion": "odo.dev/v1alpha1",
            "metadata": {
                "name": "ingressurl1",
                "creationTimestamp": null
            },
            "spec": {
                "tls": [
                    {
                        "hosts": [
                            "ingressurl<IP_ADDRESS>.4.com"
                        ],
                        "secretName": "java-spring-boot-tlssecret"
                    }
                ],
                "rules": [
                    {
                        "host": "ingressurl<IP_ADDRESS>.4.com",
                        "http": {
                            "paths": [
                                {
                                    "path": "/",
                                    "backend": {
                                        "serviceName": "java-spring-boot",
                                        "servicePort": 8080
                                    }
                                }
                            ]
                        }
                    }
                ]
            },
            "status": {
                "state": "Not Pushed"
            }
        }
    ]
}

run odo push, and then list the url, should see state as Pushed
$ odo url list
NAME            STATE      URL                                 PORT     SECURE
ingressurl1     Pushed     https://ingressurl<IP_ADDRESS>.4.com     8080     true

run odo url delete ingressurl1, and then list the url, should see state as Locally Deleted
$ odo url delete ingressurl1
? Are you sure you want to delete the url ingressurl1 Yes
 ✓  URL ingressurl1 removed from the env file

To delete the URL on the cluster, please use `odo push`
$ odo url list
Found the following URLs for component java-spring-boot
NAME            STATE               URL                                 PORT     SECURE
ingressurl1     Locally Deleted     https://ingressurl<IP_ADDRESS>.4.com     8080     true

Manual tests for describe are similar.

@yangcao77 does this PR also solve showing unpushed urls in experimental mode as well?

@girishramnani Yes. With this PR, list and describe shows the state of Not Pushed and Locally Deleted.
$ odo url list
Found the following URLs for component java-spring-boot
NAME            STATE          URL                                 PORT     SECURE
ingressurl1     Not Pushed     https://ingressurl<IP_ADDRESS>.4.com     8080     true

There are local changes. Please run 'odo push'.

added https://github.com/openshift/odo/issues/2983 in the issue description as that gets fixed too

/approve

@mik-dass @amitkrout I have added more tests to this PR, and addressed the review comments as well.
Can you help review this PR again? Thanks.

/retest

/retest

@mik-dass I have addressed your review comments. Can you help review again?

@mik-dass I have addressed your review comments. Can you help review again?

One last suggestion. Rest looks good and works for me.


refactor layout and add layout props

Off of #1637
Refactors the base layout to a much smaller and easier to work with footprint.
New +layout file:
<script>
	import<EMAIL_ADDRESS>	import '../app.css';
	import { EvidenceDefaultLayout } from '@evidence-dev/core-components';
	export let data;
</script>

<EvidenceDefaultLayout {data}>
	<slot slot="content" />
</EvidenceDefaultLayout>

EvidenceDefaultLayout has props for:

Overriding the project logo with a text title
Overriding the project logo with an image
Setting the width of the project to full width
Never showing queries in prod - removes the show queries option from the drop down when deployed (leaves it during dev)
Hiding the sidebar
Github Repo
Slack Community
X Profile
Built With Evidence - adds a small link to our homepage below the sidebar

Ultimately, I'd like to expose these props as options in evidence.config.

Very cool!
If possible, I think any slack and github icons should be left of the kebab page menu.
I can also believe you might want to link to a more generic place.

Your company marketing site

Your data dictionary

etc

Could have a more generic "link" icon for this purpose

This is sweet. Only other thing it may be worth considering is bringing a toggle for SQL queries out of the kebab menu - we've had a lot of people ask about how to show/hide their queries.
One other option for that is creating a "dev toolbar" which appears at the top of the page only in dev mode and includes anything that would help people when developing their project - SQL toggle, schema explorer, link to deploy, etc.

dev toolbar is nice, but we'd still have to have a show/hide queries button elsewhere

I'm also interested in looking at a command k menu for dev controls. There's a few things that will end up in the header though, even in prod (dark mode toggle, arbitrary links etc.) where we may end up needing the kebab as the overflow for smaller screens. If you guys are good, can I get an approval and we can revisit this in another PR?


Cineon cleanup

The cineon and dpx codepaths share many common chunks of code. However, the dpx has had many bugfixes that were not ported to cineon.
For example, if we compare cineon.imageio/libcineon/BaseTypeConverter.h dpx.imageio/libdpx/BaseTypeConverter.h  we see the dpx has code to preserve white point scaling.  However, cineon does not have that code (and it should!).
Additionally, cineon has a compile warning that should be addressed:
In file included from /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/Writer.cpp:41:                                                                    /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/WriterInternal.h: In function ‘void cineon::WritePackedMethod(IB*, IB*, int, bool, cineon::BufferAccess&) [with IB = unsigned int, int BITDEPTH = 32]’:                                                                                /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/WriterInternal.h:273:   instantiated from ‘int cineon::WriteBuffer(cineon::OutStream*, cineon::DataSize, void*, cineon::U32, cineon::U32, int, cineon::Packing, bool, int, char*, bool&) [with IB = unsigned int, int BITDEPTH = 32, bool SAMEBUFTYPE = true]’                /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/Writer.cpp:286:   instantiated from here                                                                /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/WriterInternal.h:145: warning: right shift count is negative                                            /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/WriterInternal.h: In function ‘void cineon::WritePackedMethod(IB*, IB*, int, bool, cineon::BufferAccess&) [with IB = long unsigned int, int BITDEPTH = 64]’:                                                                                /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/WriterInternal.h:273:   instantiated from ‘int cineon::WriteBuffer(cineon::OutStream*, cineon::DataSize, void*, cineon::U32, cineon::U32, int, cineon::Packing, bool, int, char*, bool&) [with IB = long unsigned int, int BITDEPTH = 64, bool SAMEBUFTYPE = true]’           /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/Writer.cpp:293:   instantiated from here                                                                /net/homedirs/jeremys/git/oiio.js/src/cineon.imageio/libcineon/WriterInternal.h:145: warning: right shift count is negative
I am marking this as a bug, due to the issue that at least one of these changes (the bit depth 10->16 promotion) will affect image results.

another issue with Cineon is that standard Cineon files such as the Kodak Digital LAD http://motion.kodak.com/motion/support/technical_information/lab_tools_and_techniques/digital_lad/default.htm ar read as:
    oiio:ColorSpace: "GammaCorrected"
    oiio:Gamma: 0

The following condition, which appears twice in cineoninput.cpp:
if (!isinf (m_cin.header.Gamma ()))

should probably be:
if (!isinf (m_cin.header.Gamma ()) && m_cin.header.Gamma () != 0.)

@devernay , see #1466 for the minor fix you pointed out with the gamma.
Did you just append here because it was related to Cineon, or are you having trouble corresponding to the original reason for this issue? Because it's a rather old ticket and nobody has complained about it in years (Jeremy, who opened this issue, worked for my employers, so if I'm not getting complaints internally, Jeremy's original concerns are essentially theoretical, I don't think we use Cineon extensively enough to spend time on it). I'd be happy for somebody to fix, but without any serious complaints I can't justify spending the time on it myself.

I append here because I always search for old open issues before opening a new one, but finally thought it deserved its own issue (#1463), because after this first Cineon failure (which happened with Kodak DLAD), I stumbled on more failures with Nuke-create cineon files from the Nuke tutorial assets. I'm still not sure about what "gamma" means in Cineon files, which seem to always be log-eencoded. Is this gamma supposed to replace log encoding, or to be applied afterwards?

From the DPX spec it suggests that Gamma is for a undefined video signal (ie not Log) and requires other header values.

For the undefined video signal standard, it is necessary to specify the following fields that would otherwise be fully specified by selecting one of the video signal standards:
68 Gamma
69 Black level code value
70 Black gain
71 Breakpoint
72 Reference white level code value

4.38 gamma: Defines the power law expo- nent that represents the gamma correction applied to a video image. In the expression Y = X1/gamma, the default gamma for NTSC is 2.2. [68]

From how I read the DPX spec these headers values are mutually exclusive and don't get applied together. Also these header fields are apart of the 'Television information' industry specific header section.

This is what it says in the DPX spec, I would suggest that for CIN that the headers by in large behave the same.

Well, then as a practical matter, are all Cineon files in the real world encoded as log, and so our cineon reader should just always declare the color space to be "KodakLog" and forget about the gamma value?

It sounds reasonable. That's what Nuke, ImageMagick and GraphicMagick do, e.g.:
http://hg.code.sf.net/p/graphicsmagick/code/file/7fa54cb64ff8/coders/cineon.c#l1141
According to GraphicsMagick, the gamma is this of the capture device, not of the encoded values, which makes sense since it's in the "Origination Info" header, and not in the "Image Info" header.
Another important information: it seems like the header data is bigendian, and thus all 32-bit values have to be swabbed on x86, but the libcineon source code seems to only swabs the image data, not the header data (thus the crazy values read from nuke-encoded cineons). Did I miss something?
GraphicsMagick swabs the header members too:
http://hg.code.sf.net/p/graphicsmagick/code/file/7fa54cb64ff8/coders/cineon.c#l512
ImageMagick also swabs header members (it sets image->endian, and then uses ReadBlob*() which swabs):
https://github.com/ImageMagick/ImageMagick/blob/master/coders/cin.c#L450

I think this was fixed in #1466, but this issue didn't auto-close.


Fix single autocomplete select inputs

I want to merge this change because:

it fixes the auto complete select input displaying id instead of label
adds the logic where on input blur it selects / displays proper item

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Translated strings are extracted.
[ ] Number of API calls is optimized.
[ ] The changes are tested.
[ ] Data-test are added for new elements.
[ ] Type definitions are up to date.
[ ] Changes are mentioned in the changelog.

Test environment config

API_URI=https://test-deployment.api.saleor.rocks/graphql/

Task linked: SALEOR-1368 [Create Product] Search Product Type puts incorrect value


Issue/65/indy prove attrs validator bug

closes #65

Fixed by https://github.com/didx-xyz/aries-cloudcontroller-python/pull/69


HIVE-24337: Cache delete delta files in LLAP cache

Changes:

Added new method in LLAP IO API so that a cached LLAP record reader can be created for arbitrary files
Made ColumnizedDeleteEventRegistry make use of this when LLAP is available and the feature is turned on
Removed some unnecessary / inefficient code parts in LlapInputFormat and AcidInputFormat

Functional testing: existing testing already covers this change:

TestVectorizedOrcAcidRowBatchReader unit test covers the code paths of this change when the feature is off (no LLAP present)
TestMiniLlapCliDriver/acid_direct_update_delete.q qtest covers the code paths where LLAP is present and ACID delete deltas are cached into LLAP IO (since the feature flag is by default turned on)

Performance testing: used S3 to see performance gains on a small (6 rows) table read that had ~20 delete events.

query duration decreased from ~17s to ~7s

Tested with hive.llap.io.cache.deletedeltas=all.
Jenkins found 1 failed test:
org.apache.hadoop.hive.cli.split19.TestMiniLlapLocalCliDriver.testCliDriver[results_cache_invalidation2]
Re-run manually and passed, thus it is flaky.

Tested with hive.llap.io.cache.deletedeltas=all.
Jenkins found 1 failed test:
org.apache.hadoop.hive.cli.split19.TestMiniLlapLocalCliDriver.testCliDriver[results_cache_invalidation2]
Re-run manually and passed, thus it is flaky.

Tested with hive.llap.io.cache.deletedeltas=metadata.
All tests passed.

Tested with hive.llap.io.cache.deletedeltas=metadata.
All tests passed.

Tested with hive.llap.io.cache.deletedeltas=none.
All tests passed.

Tested with hive.llap.io.cache.deletedeltas=none.
All tests passed.


Support for .NetCore

Hi..do we have a roadmap to support .Net Core framework
https://www.microsoft.com/net/core#windows
Tried to compile against the .Net Core its breaking due to DATSET usage in fastJSON
https://github.com/yojimbo87/ArangoDB-NET/tree/master/src/Arango/Arango.Client/ExternalLibraries/fastJSON
PS: DATSET is no longer avail in System.Data in .Net Core

Project Arango.Client (.NETCoreApp,Version=v1.0) will be compiled because expected outputs are missing
Compiling Arango.Client for .NETCoreApp,Version=v1.0
C:\Program Files\dotnet\dotnet.exe compile-csc @C:_Projects\Arango.Client\src\Arango.Client\obj\Debug\netcoreapp1.0\dotnet-compile.rsp returned Exit Code 1
C:_Projects\Arango.Client\src\Arango.Client\ExternalLibraries\fastJSON\JSON.cs(922,17): error CS0246: The type or namespace name 'DataSet' could not be found (are you missing a using directive or an assembly reference?)
C:_Projects\Arango.Client\src\Arango.Client\ExternalLibraries\fastJSON\JsonSerializer.cs(257,41): error CS0246: The type or namespace name 'DataSet' could not be found (are you missing a using directive or an assembly reference?)
C:_Projects\Arango.Client\src\Arango.Client\ExternalLibraries\fastJSON\JsonSerializer.cs(288,35): error CS0246: The type or namespace name 'DataSet' could not be found (are you missing a using directive or an assembly reference?)
Compilation failed.
0 Warning(s)
3 Error(s)

Any pointers get away from DATASET which will work right now till we get best solution out?
Thanks
Raj

Hi,
in the future, when velocypack serialization is implemented in ArangoDB then fastJSON won't be needed therefore I think the transition to .NET Core might be easier. Another option is to get rid of parts of the code where dataset is being used. I'll try to look into it.

looks like the following fork has done the same (removed System.Data from fastJSON)
https://github.com/Panaetius/ArangoDB-NET-core
As you said till velocypack is not avail..we can get away with remove stuff.
.Net Core compatibility is key for C# to be more mainstream in Linux apps/webapps ..hope future versions support it fully.
Cheers..

Hi,
I'm working the Velocypack .NET implementation for ArangoDB .NET drivers, based on java driver. if you interested it, please check out my project.
nevermind main project called ArangoDB.NET, it's just Java driver migration and no plan to solve yet.
Thanks.
Composite

Hi,
thanks for the effort of porting the Java version. I recently started working on my own implementation of the velocypack format, so it might be interesting to see for example the performance comparison in the future.

@yojimbo87 oh that's so interesting.

Any updates on this?

Hi, sorry but no plans for this yet.

@yojimbo87 ok thanks for the answer

Do u have plans to migrate to .net core 2.0? Any activity in this repo?


Bug: unexpected output from Tile::getQuadTree()

Hi!
First of all thank you for this library. I need it to generate a quadkey from latitude and longitude values. I know about your pyGeoTile library, but for my purpose i prefer to use C++.
The first unexpected output come from the Tile::getQuadTree() function. The code, infact, seems to be unable to generate quadkey with the "3" value in the generated string. Doing many test i can't obtain the right value of quadkey, also compared with pyGeoTile library.
I think that the trouble is in the rounding of value when the TMS is generated (it appears in my case with zoom > 16). Another problem come from the iterator osstream :
if (digit > 2)         {             digit %= 2;         }
In this way it is impossible to have the  digit "3".
For this reason i changed some part of code in this way: 2a03b7c.
Let me know about it. It is my first contribution at all. Do I have to make a pull request?

Hi, cool that this repo gets used.
A PR would be great and maybe you can add a test that covers the bug you found.

@Murthy10 Thank you for the very quick answer. I added a test how you said.

Solved here: #10


Fix commandblocks not able to change command on update

In 1.8, the server sent PLAY_UPDATE_BLOCK_ENTITY every time some commandblock get's updated. But if you opened a commandblock window, it wouldn't get updated
In 1.9, it only updates when you open it. The commandblock window get updated every time PLAY_UPDATE_BLOCK_ENTITY is sent. This would mean, if some commandblock somewhere changed. It would change in your window to that. Even if it was not the commandblock you opened.
Before: https://fileserver.matsv.nl/media?id=0ea0808544239fb7debf084c226ac132
After: https://fileserver.matsv.nl/media?id=12c66ee1bcc30b2e53a4d7155028feb3

Looks good!


Cannot update identity column 'id' in mssql

In this line
https://github.com/tgriesser/knex/blob/master/src/dialects/mssql/query/compiler.js#L77
There is bug in update for identity primary key. It geneterated following error:
"update [events] set [created_at] = @p0, [description] = @p1, [id] = @p2, [name] = @p3, [updated_at] = @p4, [user_id] = @p5 where [id] = @p6;select @@rowcount - Cannot update identity column 'id'."

Quick read of the description makes it look to be a duplicate of https://github.com/tgriesser/bookshelf/issues/1259

@basir I suppose you are trying to set id column implicitly why that error is thrown. Please add steps to reproduce (if bookshelf issue, then this is wrong tracker).


Removed Facebook keys

How we can set our Facebook keys: http://stackoverflow.com/questions/11648620/setting-environment-variables-in-rails-3-devise-omniauth

:+1:


Cleanup some stuff

[ ] Structure requirements format by adding requirements/ directory
[ ] Adds code coverage
[ ] Adds setup.cfg with command configurations

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cec6cf2). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master     #57   +/-   ##
========================================
  Coverage          ?   38.2%
========================================
  Files             ?       5
  Lines             ?     479
  Branches          ?       0
========================================
  Hits              ?     183
  Misses            ?     296
  Partials          ?       0

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 cec6cf2...956ca27. Read the comment docs.


Add example for firestore considering V9

🗄 Docs report
Description
 While there is example for blog, it is not sufficient to be considered for various use cases.
Considering Angular's relation, several guide for firebase will be helpful various developers. Especially novice as like me.
I have tried to implement custom plugin for firestore as below snippet. But it is not able to expect what needs to be corrected.
My representative references were below.
https://github.com/jorgeucano/started-scully-firebase
https://scully.io/docs/learn/getting-started/manualInstallation/
https://github.com/scullyio/scully/blob/main/scully/plugins/sampleFromTS.ts
🔬 Minimal Reproduction
What's the affected URL?**

https://scully.io/docs/learn/create-a-blog/generate-new-blog-posts/
https://scully.io/docs/Reference/plugins/overview/
Expected vs Actual Behavior**

📷Screenshot

🔥 Exception or Error

// scully.{{my project name}}.config.ts

import { ScullyConfig } from '@scullyio/scully';
import '@scullyio/scully-plugin-puppeteer';
import { firestorePlugin } from "./scully/plugins/plugins"

export const config: ScullyConfig = {
  projectRoot: './src',
  projectName: 'cloudrun-angular',
  outDir: './dist/static',
  routes: {
    '/article/:docId': {
      type: 'firebasePlugin',
      manualIdleCheck: true
    },
    '/blog/:slug': {
      type: 'contentFolder',
      slug: {
        folder: "./blog"
      }
    },},
};

// ./scully/plugins/plugins.ts

import { registerPlugin } from "@scullyio/scully";
import { collection, getDocs, getFirestore, query, where } from "@angular/fire/firestore";
import { getApp } from "@angular/fire/app";

const app = getApp()
const firestore = getFirestore()
const dbPath = `/dev_CommunityBoard`
const fsCollection=collection(firestore,dbPath)
const fsQuery=query(
    fsCollection,
    where('published',"==",true),)

export const firestorePlugin = "firestorePlugin";

async function firestorePluginFunction(route: any, config: any){
    let docs = new Array;
    const querySanp = await getDocs(fsQuery);
    querySanp.forEach((doc) => {
        docs.push({ route: `/article/${doc.id}` });
    });
    return docs;
}

const validator = async () => [];
registerPlugin(
    'router',
    firestorePlugin,
    firestorePluginFunction,
    validator);

npx scully && npx scully serve

  ✔ Folder "./scully" used for custom plugins
  x Unknown type "firebasePlugin" in route "/article/:docId"
  ✔ Starting servers for project "cloudrun-angular"
  ✔ Started Scully static server on "http://localhost:1668/"
  ✔ Started Angular distribution server on "http://localhost:1864/"

🌍 Your Environment
Angular CLI: 15.1.4
Node: 18.13.0
Package Manager: npm 8.19.3
OS: darwin x64
Angular: 15.1.3
... animations, cdk, common, compiler, compiler-cli, core
... elements, forms, material, platform-browser
... platform-browser-dynamic, router
Package                         Version
@angular-devkit/architect       0.1501.4
@angular-devkit/build-angular   15.1.4
@angular-devkit/core            15.1.4
@angular-devkit/schematics      15.1.4
@angular/cli                    15.1.4
@angular/fire                   7.5.0
@schematics/angular             15.1.4
rxjs                            7.5.7
typescript                      4.8.4
"@scullyio/init": "^2.1.41",
"@scullyio/ng-lib": "^2.1.0",
"@scullyio/scully": "^2.1.0",
"@scullyio/scully-plugin-puppeteer": "^2.1.0",

Regarding above, below error appears after revision of scully.{{my project name}}.config.ts.
'firestorePlugin' -> firestorePlugin
Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>not supported. Instead change the require of<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.

howdy! I have the same exact problem with ERR_REQUIRE_ESM, have you found a fix for it ?

No.. I moved Angular + NestJS.


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
init

✅ Succeeded
17 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
16 seconds
deprecated-base-image-check

✅ Succeeded
11 seconds
sanity-inspect-image

✅ Succeeded
59 seconds
clamav-scan

✅ Succeeded
17 seconds
clair-scan

✅ Succeeded
10 seconds
sbom-json-check

✅ Succeeded
7 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
sanity-label-check

✅ Succeeded
7 seconds
show-summary


Update azure-cli-configuration.md

corrected a small typo ;)

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-configuration.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

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

Thank you for your contribution!

Thanks Stephen for merging it.
Le 15 mai 2018 11:55 AM, Stephen Tramer<EMAIL_ADDRESS>a écrit :
Thank you for your contribution!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-docs-cli-python/pull/809#issuecomment-389218858, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Ae8NwWjB5H0ybagNlulpizWdd8grP87_ks5tyvpZgaJpZM4T-w48.


Add size-plugin

What kind of change does this PR introduce?
Adds size-plugin for pretty output size tracking & display.

CI failure was a Node 8 requirement, bumping the build to get a new version of size-plugin that polyfills.

pretty sure it's still the certificate problem thing

might do.

Won't git cry about the history if we do that?

Closing this in favour of https://github.com/developit/preact-cli/pull/630