DNM Update VM connectivity test ping destination

This PR is only for tests, based on #3112,
updates ping destinations in 'vmi_networking_test', to destinations that supports ipv6.
There is no IPv6 WAN in my dev environment, if this also the case in prow environment,
the test will ping to the cluster nodes gateway.

/hold tests

/test pull-kubevirt-e2e-k8s-1.16

/test pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6

/test pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6

/test pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6

/test pull-kubevirt-e2e-kind-k8s-1.17.0-ipv6


Please mention 32bit .net runtime is needed in readme file.

I installed x64 .NET and it didn't work.

Alright, will look forward to updating the README file and mentioning that.

Also, when running the .exe manually from a command prompt, there's actually a response here telling me that I need this .NET package, and a working link to  a setup package for it. Perhaps this could be shown instead of the program just exiting without any feedback? I'm guessing a lot of people give up at this point :)

thats what i mean when i refer to C# as a "crappy choice" - im sorry everyone, will get to move everything to C++ asap.

i've just uploaded an update, please let me know if you experience any weird behavior or if everything works as expected. take care y'all!


[top-level,ibex_rnd] Harden rv_core_ibex_rnt test

This test was doing a single attempt of cases where operations should happen in quick succession. It is more reliable to attempt it multiple times and check at least one attempt fails as expected.

This fixes a failure in closed-source.

Merged ignoring the FPGA failure which could not possibly be caused by this.


Please update the nuget package, it was last published 11/20/2019

I would like to access the latest features such as window size and position.

This is being tracked in #54
Currently WebWindow isn't working on Windows

Working on it today. I'll close this issue since it doesn't track anything different.


feat: embed icon of collapsible item as separated element

Should resolve #188
Not the ideal option (and probably not final design), but so far I can't imagine how it should look like. Definitely need to support two versions -- with pseudo element in case of categories without index page (as it was before), and with new use case, when text and icon are represented as separate elements.
Technically, for menu item with category index need to add a new <button> element after the link element. In the case of a "regular" category, everything is unchanged (only the menu__link--sublist class on menu link is required).

Definitely need to support two versions -- with pseudo element in case of categories without index page (as it was before), and with new use case, when text and icon are represented as separate elements.

IMO we should make the category dropdown separate elements in all cases to keep consistency. This could (a) allow users to swap out the chevron with other icons and (b) make redesigning the UX more convenient in the future if there's ever such a need. (more control on the Docusaurus side rather than having to manipulate a monolithic element)

There is no need to always have two separate elements if they are doing the same thing. It's confusing and doesn't make sense.

nuance in the background color when hover

I don't really understand what exactly is wrong?
I would still embed the icon through CSS -- users can replace it with their own in a custom CSS file by targeting on pseudo element, or override default value of CSS var --ifm-menu-link-sublist-icon.

I don't really understand what exactly is wrong?

No, before I thought all category links have the same UI, just those with an index have a different clickable chevron, so I suggested using a unified CSS. Now I realized the two have a whole different styling, it's fine to keep it that way.

users can replace it with their own in a custom CSS file by targeting on pseudo element

It's slightly different from the usual practice on the Docusaurus site, but yes we can educate the users. Maybe it's an even better approach because of reusability? (cf https://github.com/facebook/docusaurus/issues/5865)

I would still embed the icon through CSS -- users can replace it with their own in a custom CSS file by targeting on pseudo element, or override default value of CSS var --ifm-menu-link-sublist-icon.

I'm not sold on what exactly we should do about icons yet, but in any case we'd rather enable a consistent way to override icons, not half CSS half swizzle.
But for now this approach can be fine and unlocks me. We'll think about icons in general as part of https://github.com/facebook/docusaurus/issues/5865

In terms of the design with separate elements, what about the GitBook design? https://docs.gitbook.com/organizations/billing-settings
The category title still as a whole acts as a link, but the chevron is a little clickable button embedded

I don't have a strong opinion on that, we can polish the design later as long as the UX is complete and the design is good enough
This active category design surprised me a bit (not in the current demo) but I don't dislike it:

integration can be seen at https://deploy-preview-5830--docusaurus-2.netlify.app/docs/next/category/guides/

This active category design surprised me a bit (not in the current demo) but I don't dislike it:

You merged too soon... well, never mind. here's revised design, improved to work with hover/active state.  Is that better?

Thanks :) yes that seems better to me.

You merged too soon... well, never mind. here's revised design, improved to work with hover/active state. Is that better?

If you still want to work on the PR, it's better for me if you mark it as draft, otherwise I'll consider ready to merge from your side :)


Added await transaction.finish() inside Transaction.updates

Thanks for sharing this great library with us! Unfortunately I have experienced some problems with auto-renewable subscriptions when calling product.purchase(). The function would return immediately with success but the product wasn't purchased!
I found that I wasn't the only one with this problem when using StoreKit2 as you can see in this thread.
Couple of members suggested that the app should always call transaction.finish() inside Transaction.updates which I did and after that it seems that this problem is gone. If you take a closer look inside Source Code from Apple you can see how they say: "Always finish a transaction.".

But I already do call finish on the transaction. I do this in two places:
In StoreHelper `purchase(_:options:). See line 538:
await validatedTransaction.finish()  // Tell the App Store we delivered the purchased content to the user

And in the StoreHelper handleTransactions() method. See line 895 in handleTransactions():
/// This is an infinite async sequence (loop). It will continue waiting for transactions until it is explicitly
/// canceled by calling the Task.cancel() method. See `transactionListener`.
/// - Returns: Returns a task for the transaction handling loop task.
@MainActor private func handleTransactions() -> Task<Void, Error> {
    return Task.detached { [self] in
        for await verificationResult in Transaction.updates {
            :
            :
            await transaction.finish()
        }
    }
}

But not in all cases because i.e. inside
if let expirationDate = transaction.expirationDate, expirationDate < Date() {
    // The user's subscription has expired
    StoreLog.transaction(.transactionExpired, productId: transaction.productID, transactionId: String(transaction.id))
    await self.updatePurchasedProducts(for: transaction.productID, purchased: false)
    if let handler = transactionNotification { handler(.transactionExpired, transaction.productID, String(transaction.id)) }
    await transaction.finish()
    return
}

There is a return at the end and because of that .finish() never gets called. Maybe this seems like there is no need to call it but after adding .finish() things started working.

Ah yes, I see now. Sorry, for some reason I couldn't see your changes as I was viewing the PR via the Tower client. On GitHub I can see your suggested changes.
That's interesting because I remember when I first wrote this code I did research into whether or not I should call finish on the transaction in those cases where access to the product has been revoked, the subscription has expired or when the user has upgraded the subscription to a higher-value subscription. And I must have decided that it was NOT the correct thing to do :-)
Anyway, before merging your PR I'll do some testing to see if making those changes impacts anything else!!

No worries, the most important is that now we are on the same page. Please do some testing if you have time. I encountered this error couple of times and now I feel relieved when I finally found forum discussion with the same problem as mine. LMK if this worked.

I've done some testing and, for me, it seems that having the extra transaction.finish() calls inside Transaction.updates for all cases (expired, revoked, upgraded, etc.) doesn't make any difference. I've tried with and without and everything seems to work correctly. However, having looked at that Apple developer support thread I'm convinced that you're correct.  So, I'm going to add the extra transaction.finish() calls.
I'm going to close this PR rather than merge it because I'm going to add the transaction.finish() call higher up the method to avoid code repeatition. Thanks!

All done!


connection with named camera

Hello
below is a patch that allows to instantiate PTPy() with a string (camera name):
camera = PTPy('NIKON DSC D70')
without breaking the past behavior.
Thank you for this Python PTP implementation!
Markus Wildi
diff --git a/ptpy/transports/usb.py b/ptpy/transports/usb.py
index 7ee4c5f..12321ec 100644
--- a/ptpy/transports/usb.py
+++ b/ptpy/transports/usb.py
@@ -70,12 +70,16 @@ class USBTransport(object):
         # and get the USB endpoints for the first one that works.
         if device is None:
             logger.debug('No device provided, probing all USB devices.')
-        devs = [device] if (device is not None) else find_usb_cameras()

-        for dev in devs:
-            if self.__setup_device(dev):
-                logger.debug('Found USB PTP device {}'.format(dev))
-                break
+        for dev in find_usb_cameras():
+            if device is None:
+                if self.__setup_device(dev):
+                    logger.debug('Found first USB PTP device {}'.format(dev))
+                    break
+            elif device in usb.util.get_string(dev, dev.iProduct):
+                if self.__setup_device(dev):
+                    logger.debug('Found named USB PTP device {}'.format(device))
+                    break
         else:
             message = 'No USB PTP device found.'
             logger.error(message)

The difference between your diff and 4c7f6e5 is that the latter allows users to get all cameras that match the given name through a function that is already part of the API.
You should find this works as you expect otherwise. Hope this is useful!


Build with @sveltejs/adapter-node does not run correctly

Describe the bug
When creating the skeleton project with TypeScript and using @sveltejs/adapter-node, the build succeeds with warnings and fails to run when using node build.
Logs

Build warning
> Using @sveltejs/adapter-node
 > .svelte-kit/node/index.js:18:31: warning: "import.meta" is not available in the configured target environment ("es2019") and will be empty
    18 │ global.require = createRequire(import.meta.url);
       ╵                                ~~~~~~~~~~~
   tsconfig.json:6:12: note: The target environment was set to "es2019" here
     6 │     "target": "es2019",
       ╵               ~~~~~~~~

 > .svelte-kit/node/index.js:15792:40: warning: "import.meta" is not available in the configured target environment ("es2019") and will be empty
    15792 │ const __dirname = dirname(fileURLToPath(import.meta.url));
          ╵                                         ~~~~~~~~~~~
   tsconfig.json:6:12: note: The target environment was set to "es2019" here
        6 │     "target": "es2019",
          ╵               ~~~~~~~~

  ✔ done
✨  Done in 2.01s.

Run error
╰─$ node build
node:internal/process/esm_loader:74
    internalBinding('errors').triggerUncaughtException(
                              ^

TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received undefined
    at new NodeError (node:internal/errors:363:5)
    at createRequire (node:internal/modules/cjs/loader:1203:11)
    at file:///Users/seth.corker/projects/mfe-example/blog/build/index.js:1566:18
    at ModuleJob.run (node:internal/modules/esm/module_job:175:25)
    at async Loader.import (node:internal/modules/esm/loader:178:24)
    at async Object.loadESM (node:internal/process/esm_loader:68:5) {
  code: 'ERR_INVALID_ARG_VALUE'
}

To Reproduce

Create a new sveltekit project with the skeleton template
Add @sveltejs/adapter-node as a dev dependency
Update svelte.config.js to use the adapter
npm run build
node build

Expected behavior
The server runs as expected when using node build
Stacktraces

Stack trace
node:internal/process/esm_loader:74
    internalBinding('errors').triggerUncaughtException(
                              ^

TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received undefined
    at new NodeError (node:internal/errors:363:5)
    at createRequire (node:internal/modules/cjs/loader:1203:11)
    at file:///Users/seth.corker/projects/mfe-example/blog/build/index.js:1566:18
    at ModuleJob.run (node:internal/modules/esm/module_job:175:25)
    at async Loader.import (node:internal/modules/esm/loader:178:24)
    at async Object.loadESM (node:internal/process/esm_loader:68:5) {
  code: 'ERR_INVALID_ARG_VALUE'
}

Information about your SvelteKit Installation:

Diagnostics
  System:
    OS: macOS 11.4
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 1.07 GB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.3.0 - ~/.nvm/versions/node/v16.3.0/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 7.15.1 - ~/.nvm/versions/node/v16.3.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Chrome: 91.0.4472.101
    Firefox: 86.0.1
    Firefox Developer Edition: 77.0
    Safari: 14.1.1
  npmPackages:
    @sveltejs/adapter-node: next => 1.0.0-next.25
    @sveltejs/kit: next => 1.0.0-next.114
    svelte: ^3.34.0 => 3.38.2

Severity
I found a workaround:
Update the tsconfig.json and change the target to match the target version specified in@sveltejs/adapter-node. I suspect  es2020 should be used for SvelteKit and the adapter to work together as expected.
//tsconfig.json
{
    "compilerOptions": {
-        "target": "es2019"
+        "target": "es2020"
    }
}

I think a better fix for this would be to add esbuild.build({..., target: 'es2020'}), in adapter-node.

Sounds like a plan, I haven't investigated the codebase too much so this was the easiest workaround I could find with my limited knowledge.

Will that work on older versions of Node? https://github.com/sveltejs/kit/pull/772#issuecomment-810369052

Hm. Is there something we could do instead of import.meta.url that works in es2019? Otherwise I'm not sure how to avoid compiling to es2020. It'd be nice if we could target 2019 but still enable import.meta.url but I don't know that esbuild would allow that.

Okay, it is esbuild that's displaying this warning, because it's looking at tsconfig.json and overriding its compilation target based on what's in the file.
We can use the tsconfig option to esbuild.build() point to a different file (say, one embedded in the @sveltejs/adapter-node package) so that esbuild doesn't see the target: 'es2019' in the user's tsconfig.json. This lets the build proceed without warnings (which means it doesn't remove import.meta stuff), and (at least in my tests) the built, adapted app works on Node 12.
This is a little hacky, but I think this is a better solution than changing tsconfig.json to es2020, which would mean the built app wouldn't necessarily work on Node 12. I'll open a PR with this change shortly.

I think there's actually a much simpler way of achieving this same result: by explicitly setting target: 'es2020' when calling esbuild.build(). I think the tsconfig.json's target was only being looked at because adapter-node wasn't specifying one when calling esbuild.build().
The question then is whether that's safe to do. I don't think I have an answer to that. As far as I know, all of the user's code would already be going through TypeScript, and so would be getting compiled to ES2019, and the code being introduced by the adapter works on Node 12 (despite using some ES2020 features, like import.meta), but I don't know about npm dependencies of the user's app. They might be using features that aren't supported in Node 12, and I don't think esbuild would bother transpiling them if it were told target: 'es2020'.
We may have to eventually drop es2019 / Node 12 support, but for now, what we have is definitely broken on all versions of Node because of the es2019/es2020 mismatch and the reliance on import.meta. I think my vote is for now to add an explicit target: 'es2020' to the esbuild.build() call in @sveltejs/adapter-node, and then see what other issues arise or still remain.

Specifying target: 'node12' in the call to esbuild.build() in the adapter might be a reasonable way to handle this. This allows the use of import.meta but will still transpile things that aren't supported in Node 12 - e.g., optional chaining.

I wonder if that would also start letting us convert some SvelteKit code to use ?. which is a common stumbling point for community contributors

Even if we changed the esbuild.build() call in other adapters as well, I think that would still be a problem in development mode. There is (I believe) no build step in the @sveltejs/kit package currently, and so users would still be getting the ?. syntax in what Node is trying to run, which would be a problem for Node 12.

I've opened #1675 with the target: 'node12' change I mentioned above. I'd appreciate it if folks could take a look and try that out with their projects.

Tried it out and can confirm that it fixes the issue for me.
I have "target": "es2018" in my tsconfig.json.

This should be fixed now in version 1.0.0-next.26 of the Node adapter.

@Conduitry I still have the issue 1.0.0-next.27
"devDependencies": {
    "@sveltejs/adapter-node": "^1.0.0-next.27",
    "@sveltejs/kit": "^1.0.0-next.115",
  }

Node: v14.17.0
Build
npm run build

> Using @sveltejs/adapter-node
 > .svelte-kit/node/index.js:18:31: warning: "import.meta" is not available in the configured target environment ("es2019") and will be empty
    18 │ global.require = createRequire(import.meta.url);
       ╵                                ~~~~~~~~~~~
   tsconfig.json:6:12: note: The target environment was set to "es2019" here
     6 │     "target": "es2019",
       ╵               ~~~~~~~~

 > .svelte-kit/node/index.js:15792:40: warning: "import.meta" is not available in the configured target environment ("es2019") and will be empty
    15792 │ const __dirname = dirname(fileURLToPath(import.meta.url));
          ╵                                         ~~~~~~~~~~~
   tsconfig.json:6:12: note: The target environment was set to "es2019" here
        6 │     "target": "es2019",
          ╵               ~~~~~~~~

  ✔ done

Run
node build

internal/process/esm_loader.js:74
    internalBinding('errors').triggerUncaughtException(
                              ^

TypeError [ERR_INVALID_ARG_VALUE]: The argument 'filename' must be a file URL object, file URL string, or absolute path string. Received undefined


🌐 [i18n-KO] Translated guides/manage-spaces.md to Korean

What does this PR do?
Translated the guides/manage-spaces.md file of the documentation to Korean.
Thank you in advance for your review.
Part of https://github.com/huggingface/huggingface_hub/issues/1626
Before reviewing

[x] Check for missing / redundant translations (번역 누락/중복 검사)
[x] Grammar Check (맞춤법 검사)
[x] Review or Add new terms to glossary (용어 확인 및 추가)
[x] Check Inline TOC (e.g. [[lowercased-header]])
[ ] Check live-preview for gotchas (live-preview로 정상작동 확인)

Who can review? (Initial)

Team Hugging Face KREW, may you please review this PR?
@harheem, @cjfghk5697, @seoulsky-field, @nuatmochoi, @boyunJang, @SeungAhSon, @seoyoung-3060, @junejae, @usr-bin-ksh, @fabxoe
Before submitting

[x] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[x] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review? (Final)

@jungnerd, @heuristicwave May you please review this PR?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@Wauplin LGTM! This PR is ready to merge!


Source for the Admin SDKs is not in the github repository

Related to the feature request that I entered: I am confused about where I should get the source code for the Admin SDK components. Is there a reason that the source for the admin components is here: https://developers.google.com/resources/api-libraries/download/admin/directory_v1/csharp rather than in this repo?

The source for the different APIs is programmatically generated using the discovery API.    There is no reason to have the source as part of the repo because any changes made to the repo would just be over written the next time they are generated.

Understood. I think it's the documentation that makes it confusing. If, for some reason, a developer needs to see the auto-generated code, all of the documentation links (Nuget, code comments, project links, etc.) point to this repo. It's not immediately clear that those specific components are not hosted here. It was difficult to track down the code and the custodian for that component. I'm not sure there is a good solution for that.

I put a link in the read me on this repo pointing to the different APIs.  think its still a pull request though.
If you have any other ideas please let us know.     I agree is very confusing.


Doesn't work with Beautified Chat

I don't know if you still support 1.19.2 but on that version, don't know about the others they don't work together. You can link the item and it appears but you cant lick on it or hover over to see the details.

same on 1.20.1


Support security

Codecov Report

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

@@            Coverage Diff            @@
##             master      #22   +/-   ##
=========================================
  Coverage          ?   93.35%
=========================================
  Files             ?        2
  Lines             ?      271
  Branches          ?        0
=========================================
  Hits              ?      253
  Misses            ?       18
  Partials          ?        0

Flag
Coverage Δ

#unittests
93.35% <0.00%> (?)

Continue to review full report at Codecov.

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


Fix management component upgrades and upgrade plan with Cluster using unsupported Kubernetes versions

Issue #, if available:
Context:
The newly introduced sub command upgrade management-components currently has an issue where:
If you have an EKS Anywhere 1.24. You cannot update the management components if the cluster is using Kubernetes version 1.24, because the CLI runs into the following error: while building the new cluster spec
Error: failed to upgrade cluster: unable to get cluster config from file: kubernetes version 1.24 is not supported by bundles
It occurs while building the new cluster spec, when trying to [pick the correct versions bundle](https://github.com/aws/eks-anywhere/blob/4de7cda5ac1e6b571d769df82de2391634b750b8/pkg/cluster/fetch.go#L117) for the cluster’s kubernetes version because Kubernetes 1.24 is not supported v0.19.0, and therefore, does not have an entry in the bundles.Spec.VersionsBundles where it’s selecting from.

Description of changes:
This PR addresses the issue adding a short term building the new cluster spec for the management component upgrades flow without the VersionsBundles field. When building the full cluster.Spec definition, we fetch the eksdReleases for the KubernetesVersions for all unique k8s versions specified in the Cluster for both CP and workers.
If the Cluster object is using an unsupported version of Kubernetes, an error thrown
because it does not exist in the Bundles file. This method allows to build a cluster.Spec without
encountering this problem when performing only a management component upgrade.
Testing (if applicable):

Manually created a vSphere cluster on Kubernetes version 1.24 with EKS-A v0.18.6

Upgrade management-components
Checked upgrade plan management-components

   [ec2-user@ip-172-31-61-197 vsphere-cluster]$ eksctl-anywhere upgrade management-components -f mgmt04/mgmt04-eks-a-cluster.yaml
Performing setup and validations
✅ Vsphere provider setup and validation
✅ Control plane ready
✅ Cluster CRDs ready
Upgrading core components
🎉 Management components upgraded!

[ec2-user@ip-172-31-61-197 vsphere-cluster]$ eksctl-anywhere upgrade plan management-components -f mgmt04/mgmt04-eks-a-cluster.yaml
mgmt04/mgmt04-eks-a-cluster.yaml
Checking new release availability...
All the components are up to date with the latest versions

Ran the following E2E tests:

--- PASS: TestVSphereKubernetes128UpgradeManagementComponents (753.53s)
PASS

--- PASS: TestVSphereKubernetes128UbuntuTo129Upgrade (2140.91s)
PASS

Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


setup/java does not replace env variables in the settings.xml

Description:
I am struggling to setup my settings.xml via setup/java.
I added the username and the password for the server in my github secrets. In my workflow I set the secrets as env variables as setup/java only takes the env variables according https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#yaml-example. But when I log my settings.xml the username and password are not replaced by the value.
Task version:
v2.3.1
Platform:

[X] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[ ] Hosted
[X] Self-hosted

Repro steps:

Add 2 secrets (USERNAME, PASSWORD) in your github repo
Add following workflow to your repository:

on:
  pull_request:
    branches:
      - main

jobs:
  build:
    runs-on: self-hosted
    env:
      USERNAME: ${{ secrets.USERNAME }}
      PASSWORD: ${{ secrets.PASSWORD }}

    steps:
      - uses: actions/checkout@v2
      - uses<EMAIL_ADDRESS>        with:
          distribution: 'temurin'
          java-version: '11'
          server-id: some-server-id
          server-username: USERNAME
          server-password: PASSWORD
      - name: Log Settings.xml
        run: cat ~/.m2/settings.xml
      - name: Build with Maven
        run: mvn clean package -s ~/.m2/settings.xml

Expected behavior:
I expect that the logged settings.xml contains my value of the secret I created for this repo. Like that:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
  <servers>
    <server>
      <id>some-server-id</id>
      <username>ThatsMe</username>
      <password>superSecretPassowrd</password>
    </server>
  </servers>
</settings>

Actual behavior:
The logged settings.xml looks like that:
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 https://maven.apache.org/xsd/settings-1.0.0.xsd">
  <servers>
    <server>
      <id>some-server-id</id>
      <username>${env.USERNAME}</username>
      <password>${env.PASSWORD}</password>
    </server>
  </servers>
</settings>

Hello @TiomanGally. Thank you for your report. It's an expected behaviour because the setup-java action prepends username and password as environment variables for security concerns during build. Username and password will be resolved during mvn commands, because environment variables declared as global in your case.
For now I'm closing the issue, because it's an expected behaviour. If you have any question feel free to contact us.


[WIP] Disallow indexing of preview urls

closes #9749

disallow indexing of /p/ in robots.txt
add meta robots tag to preview pages

robots.txt wont' be applied for blogs not mounted to the root (i.e. https://example.com/blog/)

I went ahead and disabled travis for now since I had a couple of questions 😄

Nice, I was going to say don't forget about robots.txt but you already got it :)


Allow running gtfs_functions with GTFS feeds that have missing optional fields

Fixes #8 and #10
Direction_id is optional (https://developers.google.com/transit/gtfs/reference#tripstxt) and the whole shapes.txt file is optional (https://developers.google.com/transit/gtfs/reference#shapestxt) in the GTFS specification.
Therefore, this pull request will make most of the functions work even if direction_id, shape_id or both are missing.
Also, this pr makes stop_times a geodataframe. Trying to do geometry operations fails in some cases if stops is a geodataframe, but stop_times is a regular (non-geo)dataframe.

Hi, I found out that the commit didn't solve the problem, because a Bogota GTFS file (like the found out in https://storage.googleapis.com/gtfs-estaticos/GTFS-2022-08-24.zip), that also has no direction_id, threw me the following error:

Thank you in advance.


Fix Annotations.Set()

Annotations.Set has been append()ing new Annotation to a private copy of the slice, which had effect only inside the Set function, unless Annotations' capacity has been greater than its length. This causes inconsistent behaviour, and – in most cases – no visible effect of setting a new annotation. If Annotations.Set behaves like append that it uses – i.e. returns an updated slice – the caller is able to replace old annotations slice with the updated one.
 Thanks for catching.
However I'm not really sure why your approach is preferable to just fixing Set - see https://github.com/jonboulle/spec/commit/ebe057b0fbb52b64e3b94983e4607f4678cc8832. This makes it more consistent with the name and other Set functions in the types package.

Yes, your approach seems much better than mine. I haven't thought about that, even though it's scattered all over the code - just solved my immediate issue of annotations not being set. Closing this one.

https://github.com/appc/spec/pull/120


Feature request: bib entry

Be able to directly copy a result's bib entry.

Could we ask AI2 to supply a link to a bibtex file? Seems like it's already in their pipeline and would be a good addition to the metadata

Yes, I think so - this should be lower priority atm.


Feat/flat error events

Test PR to run against unreleased Kong in CI

Codecov Report
Base: 73.7% // Head: 72.6% // Decreases project coverage by -1.2% :warning:

Coverage data is based on head (bf4c1e9) compared to base (4f2aaf7).
Patch coverage: 64.1% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##            main    #189     +/-   ##
=======================================
- Coverage   73.7%   72.6%   -1.2%
=======================================
  Files        111     122     +11
  Lines      13285   14581   +1296
=======================================
+ Hits        9803   10587    +784
- Misses      2852    3318    +466
- Partials     630     676     +46

Impacted Files
Coverage Δ

internal/adminapi/konnect.go
0.0% <0.0%> (ø)

internal/admission/utils.go
81.0% <0.0%> (ø)

...ntrollers/configuration/kongadminapi_controller.go
0.0% <0.0%> (ø)

internal/controllers/reference/reference.go
41.0% <0.0%> (ø)

internal/dataplane/parser/translators/httproute.go
94.9% <ø> (ø)

internal/dataplane/parser/wrappers_refchecker.go
64.4% <ø> (+9.2%)
:arrow_up:

internal/diagnostics/server.go
70.1% <0.0%> (+0.8%)
:arrow_up:

internal/konnect/client.go
0.0% <0.0%> (ø)

internal/konnect/node_agent.go
0.0% <0.0%> (ø)

internal/manager/controllerdef.go
98.7% <ø> (+<0.1%)
:arrow_up:

... and 102 more

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

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


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.18 to before v4.19.217",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a03bb00e50ab4c07107da58a52a0bff7943f360c",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bc51111bf6e8e7b6cc94b133e4c291273a16acd1"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "a03bb00e50ab4c07107da58a52a0bff7943f360c",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "bc51111bf6e8e7b6cc94b133e4c291273a16acd1",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "comedi: ni_usb6501: fix NULL-deref in command paths\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.19.217 by commit bc51111bf6e8e7b6cc94b133e4c291273a16acd1, it was introduced in version v3.18 by commit a03bb00e50ab4c07107da58a52a0bff7943f360c. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001994


In countNonSplicedReads stucked for no error report

When I use countNonSplicedReads, it showed subread logo. And after waited for 1 day, it still keep running, but the cpu usage is very low. Because of no any error showed from it, I can't know what happened. Could you please add more information for better diagnosis。

I have found what problem it have. In countNonSplicedReads, it will generate a temp file as genome in work directory. And I thought you haven't sort it first, therefore when use that temp  file without sort, the disk performance should be very very high so that can hold random access. Therefore a ssd is necessary for using that method. And another way to solve that is change work directory to a ssd, if your ssd is not big enough to put all your data in.


[ignore for now ] input-date-time-range: attempt to fix flaky tests

Opening as draft in order to rerun the tests several times.
Should fix https://github.com/BrightspaceUI/core/issues/1083.
This is likely cause by the same problem as https://github.com/BrightspaceUI/core/pull/1101, which is the timezone not yet being set, and there isn't an event to listen to that I'm aware of so a timeout should help with this.

I have rerun the tests ~6 times and these tests have not flaked


[influxdb] Replace "measurement" config option with "group"

Every collection_group stanza may now have an optional "measurement" attribute. This attribute is used to assist InfluxDB in organizing metrics into groups of "measurements".

Ganglia already supports grouping metrics using the "group" metadata attribute and it is used widely by all Ganglia metric modules. The influxdb integration should make use of this existing feature instead of creating something "influxdb-specific".

Can you point me to the documentation for the "group" metadata attribute, if any?  InfluxDB specifically needs something that is named, and so far as I can tell, none of the existing collection_group configuration
...digging around a bit, I see the "GROUP" XML tag set by the modules, and not the core gmond code.
I'll look into pulling that information.  Regardless, I'll leave the ability to override that setting, as the admin sees fit.

Metric groups are used in every C and Python module ever written for Ganglia.
C examples
https://github.com/ganglia/monitor-core/search?p=1&q=MGROUP&type=Code
Python examples
https://github.com/ganglia/gmond_python_modules/search?q=groups&type=Code
As you can see "groups" is used everywhere and so adding a configuration option like "measurement" is completely redundant and will only confuse new users.

Fixed by 1e251bc9122f0dae6cd90ffbcc356b4524a18c86.  Follow ups in 97ec98c and e6a34a3.

What's the motivation behind e6a34a31718e9704c6901021423be4f174fed2e0 ?

Adjust groups from e6a34a3 with c562037.


Full screen button

Hello Sir,
Is there a way to have a link or button users can click to go full screen?
Currently, users only see the small full-screen icon top right when they mouse over the slider. They often miss it.  I would like to encourage and notify the user that they can go full-screen by giving them a visible button to clock on.
How can I do this?
Thank you so much for your great work!
Wag

https://github.com/bqworks/slider-pro/issues/237
https://github.com/bqworks/slider-pro/issues/187


Binance Spot - Random orders count in client.get_orders

Issue subject
Today morning I found that I get different API answers from client.get_orders on my account. For example LUNCUSDT symbol.
Expected behaviour
When I run this example from github (https://github.com/binance/binance-connector-python/blob/master/examples/spot/trade/get_orders.py) I should get 21 entries. I changed only API keys and symbol = LUNCUSDT
In real I have 21 entries for LUNCUSDT
Actual behaviour
When I run this example I get sometimes 18 and sometimes 21 entries. I can run script for example 10 times per minute and get 5 times 18, 5 times 21 entries. It works like random.
Steps to reproduce
`import logging
from binance.spot import Spot as Client
from binance.lib.utils import config_logging
from binance.error import ClientError
config_logging(logging, logging.DEBUG)
key = "mykey"
secret = "mysecret"
client = Client(key, secret)
try:
response = client.get_orders("LUNCUSDT")
logging.info(response)
except ClientError as error:
logging.error(
"Found error. status: {}, error code: {}, error message: {}".format(
error.status_code, error.error_code, error.error_message
)
)`
Environment
Provide any relevant information about your setup, such as:

Version of binance-connector-python 1.18.0
Python version 3.9
Operating system (tried on Ubuntu and Windows 10)

It's a concern from the API side, not directly related to this library. Let's discuss in this topic.
https://dev.binance.vision/t/api-v3-allorders-returns-random-results/13160


Revert image tag to the dev one

Description
Changes proposed in this pull request:

Revert image tag to the dev one. This was done by the release scripts but it won't happen after https://github.com/kubeshop/botkube/issues/584

Related issue(s)

#595

I assume this will be latest stable tag once we finalize release process, other than that LGTM

@huseyinbabal it's already like that, for each new commit on main we push update ghcr.io/kubeshop/botkube:v9.99.9-dev


deep-link

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: deep-link
Document link: deep-link.md
My Issue/Suggestion
The page does not describe the options on the runtime configuration of a deeplink.  This is also not covered in the marketplace documentation.  For example, what does this mean "If enabled the incoming link argument will be processed as an Object"? What would this look like if I was constructing the deeplink URL string?

Hi @Chris-Karona ,
Thank you for raising this issue. I checked with our developer. Here is the answer to you question:
This is an alternative to Java actions `SetObjectParameterDeeplink` and` SetStringParameterDeeplink`. With these settings, users can control how a URL parameter will be parsed.

https://github.com/mendix/docs/blob/development/content/en/docs/appstore/modules/deep-link.md#351-configuring-deep-links-in-after-startup-microflow

I hope this helps. Please let me know if you have more questions. Meanwhile, we are working to add a section about these settings in the doc. Hopefully, that can be done soon.
Kind regards,
Luyao

Hi @Chris-Karona, we added the description of the Configuration settings and Advanced settings in the doc. Thank you again for your feedback.


Update python-raet for Redhat 6 & 7 Salt 2016.3.5 and 2016.11.0

see https://github.com/saltstack/salt/issues/25858#issuecomment-265498681
[x] 2016.3.5
[x] 2016.11.1

Done for 2016.11.1 build infrastructure, waiting for tag

Done for 2016.3.5 build infrastructure, waiting for tag

closing this since infrastructure is updated and it will be available with 2016.3.5, 2016.11.1 is already released

[DEBUG   ] LazyLoaded config.merge
Process Process-1:
Traceback (most recent call last):
File "/usr/lib64/python2.6/multiprocessing/process.py", line 232, in _bootstrap
self.run()
File "/usr/lib64/python2.6/multiprocessing/process.py", line 88, in run
self._target(*self._args, **self._kwargs)
File "/usr/lib/python2.6/site-packages/salt/scripts.py", line 129, in minion_process
minion.start()
File "/usr/lib/python2.6/site-packages/salt/cli/daemons.py", line 345, in start
self.minion.tune_in()
File "/usr/lib/python2.6/site-packages/salt/daemons/flo/init.py", line 146, in tune_in
consolepath=consolepath,
File "/usr/lib/python2.6/site-packages/ioflo/app/run.py", line 137, in run
skedder.run()
File "/usr/lib/python2.6/site-packages/ioflo/base/skedding.py", line 273, in run
status = tasker.runner.send(tasker.desire)
File "/usr/lib/python2.6/site-packages/ioflo/base/framing.py", line 630, in makeRunner
self.enterAll() #activates, resets .done state also .desire may change here
File "/usr/lib/python2.6/site-packages/ioflo/base/framing.py", line 411, in enterAll
self.enter(self.actives)
File "/usr/lib/python2.6/site-packages/ioflo/base/framing.py", line 423, in enter
frame.enter()
File "/usr/lib/python2.6/site-packages/ioflo/base/framing.py", line 1244, in enter
act() #call entryAction
File "/usr/lib/python2.6/site-packages/ioflo/base/acting.py", line 99, in call
return (self.actor(**self.parms))
File "/usr/lib/python2.6/site-packages/ioflo/base/acting.py", line 524, in call
return self.action(**kwa)
File "/usr/lib/python2.6/site-packages/salt/daemons/flo/core.py", line 292, in action
stackname=name)
File "/usr/lib/python2.6/site-packages/salt/daemons/salting.py", line 62, in init
self.saltRaetKey = RaetKey(opts)
File "/usr/lib/python2.6/site-packages/salt/key.py", line 940, in init
Key.init(self, opts)
File "/usr/lib/python2.6/site-packages/salt/key.py", line 372, in init
listen=False)
File "/usr/lib/python2.6/site-packages/salt/utils/event.py", line 145, in get_event
opts=opts)
File "/usr/lib/python2.6/site-packages/salt/utils/raetevent.py", line 50, in init
self.__prep_stack(listen)
File "/usr/lib/python2.6/site-packages/salt/utils/raetevent.py", line 60, in __prep_stack
self.stack = transport.jobber_stack = self._setup_stack(ryn=self.ryn)
File "/usr/lib/python2.6/site-packages/salt/utils/raetevent.py", line 98, in _setup_stack
name = 'event' + nacling.uuid(size=18)
File "/usr/lib/python2.6/site-packages/raet/nacling.py", line 576, in uuid
return ((front + back)[:size]).decode(encoding='ISO-8859-1')
TypeError: decode() takes no keyword arguments
salt --versions-report
Salt Version:
Salt: 2016.11.1
Dependency Versions:
cffi: 1.9.1
cherrypy: 3.2.2
dateutil: 1.4.1
gitdb: Not Installed
gitpython: Not Installed
ioflo: 1.3.8
Jinja2: 2.2.1
libgit2: Not Installed
libnacl: 1.4.3
M2Crypto: 0.20.2
Mako: Not Installed
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: 1.2.3c1
pycparser: 2.17
pycrypto: 2.6.1
pygit2: Not Installed
Python: 2.6.6 (r266:84292, Jul 23 2015, 15:22:56)
python-gnupg: Not Installed
PyYAML: 3.10
PyZMQ: 14.3.1
RAET: 0.6.6
smmap: Not Installed
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 3.2.5
System Versions:
dist: centos 6.6 Final
machine: x86_64
release: 2.6.32-504.30.3.el6.x86_64
system: Linux
version: CentOS 6.6 Final
I'm install  latest version .but still an issue in CentOS 6.6 .

The changes in saltstack/raet#70 are not reflected in the latest version of raet v0.6.6. To resolve this issue, need to patch raet on Redhat 6 & 5 where python 2.6 is in use.

Patched written, waiting for next release

Now fixed in 2016.11.2 and 2016.3.5 for Redhat 6


optapy-core: Add Testing

optapy-core is currently untested. Investigate various Python testing frameworks and add tests for core functionality.

Update: tox (https://tox.wiki/en/latest/index.html) works well for this project. Pytest and unittest by themselves get confused since jars are created during the build and files does not follow conventional structure. Tox + pytest --import-mode=importlib works.

Closed via #34


#13: scoped rooms

Implements #13
This also allows to scope rooms with id.
I adapted a test to use scopes, but we might want to create separate tests rather than changing the existing one.

disclaimer:

Code is a bit messy: unnamed tuples, using Option .. but I think it show a good approach
I didn't test in real application, I'm trusting tests here 🤞

I guess we'd have to make the query parameter part of the key for the room? Idk, I'm open to suggestions here.

Yeah I think a wss://match.example.com/abcd?next=2 is just a different room from wss://match.example.com/abcd
I'm owrking on it :)

I updated matchbox_demo ; it worked fine locally 🎉 .
I didn't update documentation because I didn't find any place where the "next" logic is mentionned, I guess most information is from your blog and the example. I conclude it probably belong to another issue or Pull Request to add documentation.

Merging. I think moving tests to a separate file is a good idea, and documentation as well. More PRs always welcome ;)


Newsletter 95 (2020-04-29)

[x] Action items, news, release, and any additional commits @harding
[x] Add author info to Suredbits post and perhaps make some small edits to be reviewed by them @harding
[x] StackExchange section @bitschmidty
[x] Bitcoin Core #15761 @adamjonas
[ ] Bitcoin Core #17509 @dongcarl

Pushed edits based on the suggestions of @ariard and @ZmnSCPxj (thanks for the reviews!).

Pushed edits for (hopefully) all comments to date, including bumping the Suredbits article and descriptor wallets merge summary to next week, moving details about package relay to a footnote, and removing the claim that non-routing nodes are unaffected (with a footnote to describe the details).  Thanks @jonatack, @ariard, @jnewbery, and @TheBlueMatt!  (In addition to @ZmnSCPxj again for his previous feedback.)  Also made a few edits of my own to improve flow.
Made a tiny edit to the StackExchange section, otherwise ACK to that section (thanks @bitschmidty!)

Squashed and merged.
Lots of thank yous this week!
Authors: @harding, @adamjonas
Reviewers: @jonatack, @ariard, @ZmnSCPxj, @TheBlueMatt, @jnewbery


Integer keys

Hello. I love the project, thank you. I've played with many Node ORMs and this is the only one I think actually works as I expect.
I have noticed an issue however. Id's are marked as integer, this includes foreign keys. I use Postgres and while integer will work, I think bigint is the industry approach. Granted, you will need over 2bln rows for this to be an issue, but I have had friends create successful projects where they forgot this (tsk tsk on them) limitation and ran into issues.
A work around for my migrations is do to something like
this.type('bigint', 'user_id');

which, luckily I can do. But I can't use the stampable plugin because it is hardcoded with integers. I dug through the code and did not see a bigint datatype, nor did I see integer doing a magic conversion to the 64-bit variant.
I just wanted to raise this issue for discussion - maybe I'm missing something?
Thanks.

Hi @nibarulabs,
you are totally right to use bigint for relations in Postgres.
At the moment there is shared code for migrations wich works in SQLite, MySQL, Postgres and Oracle. The easiest way to get started was to use integer and it seems that I totally forgot to add database specific rules to the migration layer.
I think what we need is a this.references('field_name, 'table_name', {opts...}) method to define relations. Which should also add foreign key constrains to the table.
What do you think?

Hey, quick reply. :)
Totally understandable approach to getting it done and out there. I have run into a few minor issues regarding all this.

primary keys are created using integer
i have no access to a bigint data type when creating migration columns
and you are right, the references will also need some config for bigints (fk constraints sound good too)
the stampable plugin uses integers as well

That's not a ton of work, but it's still a list. I have found work arounds for all of these, so not the end of the world. This is a typical migration for me:
    this.createTable('users', function () {
        this.uuid('uuid');
        this.string('email', {unique: true});
        this.string('password');
        this.string('first_name');
        this.string('last_name');
        this.string('confirm_email_token');
        this.type('bigint', 'activated_ts');

        this.stampable();
    });

So, you can see where I force bigints (I use epoch timetamps quite a bit as well which have to be bigger than integer). I'm guessing an option for bigint to be used as the pk above would work. Somewhere. I'm kinda riffing now, but I'm sure you get the gist.
My project will be going live at the end of the month. This lib was honestly make or break and it's helped me get things over the finish line. Thanks again. 👍

I've published a new version.
this.id('name') will now use bigint.
this.userstamp() will use id('creator_id') and id('updater_id')
where is now a dedicated bigint type
regarding references: I forgot that this feature is already implemented. See references option

Wow, awesome! Thanks so much for all the work you've done.


Enhancement : add an option to enable/disable responses validation

Hello,
I think it might be useful to add an option to enable / disable responses validation ( similar to this option in the previous validator I used )
Why ? Whereas it is useful in development environment, it is a performance killer in production.
Thanks in advance

It is possible to add an option to bypass the validation stage and / or the serialization stage. This functionality does exist in some degree currently using the schema value functionality. You could wrap an entire response in a schema value prior to sending to control validation and serialization.
It would also be pretty easy to add an option to the middleware that just did this for you.

I think the second second option is better ( add an option to the middleware ) ;)

I've published the feature to npm as version 1.2.0. You can see the docs for this feature here: https://byu-oit.github.io/openapi-enforcer-middleware/api#openapienforcermiddleware


eventType: "$>" when subscribing to projections

Using EventStoreDBPersistentSubscriptionsClient#subscribe or EventStoreDBClient#subscribeToStream pointing to an event type projection ($et-com.example.SomeEvent) is rendering the following result.
streamId = "$et-com.example.SomeEvent"
streamRevision = {StreamRevision@9919} "0"
eventId = {UUID@9920} "0336fb99-09fa-4c06-89ec-1e39f78b4bb8"
eventType = "$>"
eventData = {byte[23]@9922} [...]
created = {Instant@9924} "2022-07-26T21:49:37.141969800Z"
position = {Position@9925} "18446744073709551615/18446744073709551615"
contentType = "application/octet-stream"

Any ideas?

You need to enable link resolution when reading events emitted by projections: https://developers.eventstore.com/clients/grpc/reading-events.html#resolvelinktos
May I advise you to reach out on Discuss first? We prefer to restrict Github for confirmed issues.


Extract Python Beam symbols for Playground

This PR:

Adds a Gradle task to do all post-checkout tasks.
Adds a Python script to extract Beam symbols from Python SDK.
Adds a Gradle task to call that script and to place the symbols so that the frontend app can use them.
Updates a frontend Dockerfile to do the same.
Updates the README explaining those changes.

The symbols are not yet used by the app after loading. The app will start using them when the Akvelon editor replaces the old editor. Still this PR is needed for easier testing of the Akvelon editor before the switch and to simplify. It also simplifies post-checkout tasks.

Resolves #23304

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @damondouglas

It's OK to hold this PR until everything builds on any machine. This does not block us because meanwhile we are busy on the editor.
We expect to migrate to Akvelon editor next week. This means we will no longer have a git dependency which means Google Cloud Shell will start working.
Meanwhile I will fix the Python script using your feedback and list pyyaml in the README.

stop reviewer notifications

can you rebase this PR please @alexeyinkin ?

oh I realize this was not lgtmd? @damondouglas should I review this? merge? waqit for your review?

@damondouglas now that we use the editor from pub.dev instead of git, we do not hit the bug of Google Cloud Shell, and it works all the way from ./gradlew :frontend:playground:configure to web preview.

Meanwhile I also did

#23534
in this PR so as not to be blocked by this.

@damondouglas how did you build and run it to get that? My tests:
1.
2. Local debug with Android Studio
cp playground/frontend/lib/config.example.dart playground/frontend/lib/config.g.dart

Flutter 3.3.7, Chrome.

Good thank you.  I executed the commands locally in the playground/frontend/README on a Linux Debian machine.  I'm not remoting into the device currently to inform the flutter version but updated prior to execution.  I'd say then this PR is good to go.

lgtm thanks


fix: updated js-gardener

:tada: This PR is included in version 1.3.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


CloudStorage module, any clue about release day ?

Hi
I saw you planned to release this module some day. I started to develop an app with angularfire2 a month ago and need to store images somewhere, CloudStorage would be perfect match. Do you plan to release this module any time soon ?

@fellz We are working on it and plan to have it out in the next month or so. The regular SDK works quite well with Angular though. For AngularFireStorage we plan on wrapping the UploadTask methods in Observables and providing a directive for download urls.


SDK-37: Java SDK: wait for query to complete after running

Added run method that will: run a command and wait until it completes execution and then return final Command.
Similar to run() in python SDK
Extended the InvokableBuilder for commands with InvokableCommandBuilder and added the run method here so that it is available for all Command types

Why do we need this? Users can always call awaitResult on the ResultLatch?

Was looking to provide a function similar to python run().
This will return a Command object which can be used to get various command properties(end/start time etc).
Not needed if ResultLatch is enough and users have not asked for this.

Yeah, don't think this is needed.


Exit with non-zero status with faulty settings.js

Closes #4121

Bugfix (non-breaking change which fixes an issue)
I have read the contribution guidelines

Should have targeted the dev branch, but let's wait on the discussion in the ticket instead.


Doesn't work on IE11

This component doesn't work on IE11. It crashes when active prop switches from true to false.
Didn't have time to debug it, but it looks like this is because the following code:
css(this.getStyles('wrapper', active && overflowCSS)) for the active={false} returns [{Object}, false] array and later Object.keys() method is called on each item from this array (from _objectSpread(target) method). Calling Object.keys(false) on IE11 throws en exception, however on Chrome it evaluates to [].
To reproduce run the below code on IE11:
<LoadingOverlay
  active={false}
  >

Some content

</LoadingOverlay>

To workaround this you can use below code:
<LoadingOverlay active={loading ? true : undefined}>

Some content

</LoadingOverlay>

It works because _objectSpread(target) method checks if an item is null/undefined and if so, it replaces it with an empty object {}.

Thanks for the details!
If you want to submit a PR it’d be appreciated, otherwise will try to get to it next week 😀

Published as 1.0.1, thanks


Reduce interface dispatch

E.g. in JsonClaimSet.CreateClaims, the code is doing IList<Claim> claims = new List<Claim>();.  If you just change that to List<Claim> claims = new List<Claim>();, interface dispatch in the rest of the method when working with that claims will be removed.  On their own, these won’t move the needle much, but changes here and there can add up.

This has been implemented.


Parsing error on configMap template

Using the development branch of splunk-connect-for-kubernetes in our development cluster, we discovered that the pod stopped sending logs.
Looking at the logs for the splunk-connect-for-kubernetes pod we saw this error:
111:     @type jq_transformer
112:     jq ".record.source = \"namespace:#{ENV['MY_NAMESPACE']}/pod:#{ENV['MY_POD_NAME']}\" | .record.sourcetype = \"fluentd:monitor-agent\" | .record.cluster_name = "cluster_name" | .record"

     -------------------------------------------------------------------------------------------------------------------------------------------------------------------^

It seems to me that there is a problem with not escaped double quotes, or wrapping the line in single quotes instead, in the file /helm-chart/splunk-kubernetes-logging/templates/configMap.yaml on line 212?
https://github.com/splunk/splunk-connect-for-kubernetes/blob/4bbeb829e65996076e9a0e4161c8e174d1ad8190/helm-chart/splunk-kubernetes-logging/templates/configMap.yaml#L212
It looks like it was introduced in this commit: https://github.com/splunk/splunk-connect-for-kubernetes/commit/2addba7458d9e30a31f7bb861f9cdc71cb155dca
And if you look at line 196, a similiar change has been wrapped in single quoutes :)
https://github.com/splunk/splunk-connect-for-kubernetes/blob/4bbeb829e65996076e9a0e4161c8e174d1ad8190/helm-chart/splunk-kubernetes-logging/templates/configMap.yaml#L196

Hey @jarleborsheim thanks for reporting the issue. It would be awesome if you could file a pull request :)

Sure. Will do.


Haproxy startup fails because stats.sock is a directory

In some rare cases we observed that the file /var/vcap/sys/run/haproxy/stats.sock is a directory rather than a socket file:
$ ls -al /var/vcap/sys/run/haproxy/stats.sock
total 0
drwx------ 2 vcap vcap 40 Nov  6 00:04 .
drwxrwx--- 3 vcap vcap 60 Nov  6 00:04 ..

In that case startup of the haproxy monit process failed in the haproxy_wrapper
This results in the following error message in the /var/vcap/sys/log/haproxy/haproxy.stderr.log:
rm: cannot remove '/var/vcap/sys/run/haproxy/stats.sock': Is a directory

Workaround
Manually deleting the /var/vcap/sys/run/haproxy/stats.sock folder mitigated the problem and monit start haproxy started the process again.
/cc @s4heid

We found out that '/var/vcap/sys/run/haproxy/stats.sock' was created as a directory in another bosh-release we deploy to the same vm.


Font download doesn't work

Great add-on - just what I was looking for! Slight bug though sorry:
Specifying a font from the Google Fonts Repository doesn't seem to work correctly. Calling with &font=FrederickatheGreat-Regular.ttf works as expected, but the font is likely already downloaded ins this case.
Example: http://localhost:9845/?text=Hello\nworld!&font=Raleway.ttf
If calling the URL in a browser the response is: ERR_EMPTY_RESPONSE
This should download and use this font: https://fonts.google.com/specimen/Raleway
Console log:
<IP_ADDRESS> - - [14/Dec/2024 02:00:16] "\x16\x03\x01\x06ä\x01\x00\x06à\x03\x03\x1fg·ÖêÃ\x1bÅ¡RóÚxÆ»Ô\x85¯`*7\x9d&\x13¨µ\x88ü÷ªÉÁ \x8f&îþ]@{m¿vkÈè¯Ô\x84+N*aµ\\\x19~\x8d" 400 -
<IP_ADDRESS> - - [14/Dec/2024 02:00:16] code 400, message Bad request syntax ('\\x16\\x03\\x01\\x06Ä\\x01\\x00\\x06À\\x03\\x03÷Z´GáòfÍ\\x07\\x07\\x7fUNR÷Ø\\\\d\\x07îÐ$')
<IP_ADDRESS> - - [14/Dec/2024 02:00:16] "\x16\x03\x01\x06Ä\x01\x00\x06À\x03\x03÷Z´GáòfÍ\x07\x07\x7fUNR÷Ø\\d\x07îÐ$" 400 -
Can't find font

This is not possible to fix, you will have to use the full name of the font because it relies on finding the exact name of the font from the google's github repository.
In your case the font you are looking for is located here which should result in one of the following URLs:

http://localhost:9845/?text=Hello\nworld!&font=Raleway[wght].ttf
http://localhost:9845/?text=Hello\nworld!&font=RalewayDots-Regular.ttf

Hope this clears things up.

That's perfect - thanks for the clarification


Error converting boolean expressions ...

Hi, I am using this plugin, and it is amazing...
But I believe that the Ven's diagram to minify boolean expressions is a bit wrong.
For example:
(($scope.selectedRoles.indexOf('ADMIN') == -1)&&(($scope.selectedCompanies === undefined)||($scope.selectedCompanies.length == 0)))

is minified to:
-1 != a.selectedRoles.indexOf("ADMIN") ||
        void 0 !== a.selectedCompanies && 0 != a.selectedCompanies.length

And they are not the same .... in logic space.
Thanks a lot, Daniel Moraes.

Sorry, my bad ... It works well ...


Add MomentMeanIndicator

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

Project coverage is 100.00%. Comparing base (39d1605) to head (73e25ff).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #82   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           49        49
  Lines          887       897   +10
  Branches        71        71
=========================================
+ Hits           887       897   +10

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


[RFC]: add reduceRight method to array/fixed-endian-factory

Description
This RFC proposes adding support for a reduceRight method to @stdlib/array/fixed-endian-factory.
This method is the equivalent of the TypedArray.prototype.reduceRight method, but for fixed-endian typed arrays.
When adding support, the following tasks should be completed:

The ./lib/main.js file should be updated with the added method.
A new test file should be created which includes unit tests testing against expected behavior.
Two benchmark files should be added: one measuring baseline performance and another measuring performance as the array length increases.
The README should be updated to include documentation for the added method.

To provide a concrete example of what a PR adding the desired method should contain, see https://github.com/stdlib-js/stdlib/commit/956a4624c788689b1bca285856b987ea3aa32eb6, which is a commit adding forEach support. This should provide an idea of what is expected.
For an example of specialized typed arrays having customized methods, see

@stdlib/array/bool
@stdlib/array/complex128
@stdlib/array/complex64

While the method proposed in this RFC will likely not match the implementations found in the above packages, those packages should provide a conceptual idea of what is desired. Do not simply copy-paste the code found in those packages.
Notes

If you are interested in contributing a PR which addresses this RFC and are a first-time contributor or not yet familiar with our project conventions, please do not submit LLM-generated code. Please consult our contributing guidelines and the associated development guide. Failure to respect project conventions will result in your PR being rejected without review. Thank you for understanding!

Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with [RFC]:.

Hey @kgryte i would like to work on this issue.


flutter build ios-framework does not generate obfuscation symbols

Steps to Reproduce

Run flutter build ios-framework --no-debug --no-profile --xcframework --no-universal --cocoapods --obfuscate --split-debug-info=<a_path>.

Expected results:
<a_path> containing ios-framework symbol map files
Actual results:
<a_path> is empty

Logs

Building frameworks for com.[app] in release mode...
 ├─Populating Flutter.framework...                                  3,4s
 ├─Building App.framework...                                       24,7s
 ├─Building plugins...                                             71,3s
 └─Moving to build/ios/framework/Release                            0,1s
Frameworks written to
/Users/timoteoholanda/repos/[app]/build/ios/framework.

Analyzing next_flutter...

   info • Unused import: 'package:flutter/material.dart' •
          test/widget_test.dart:8:8 • unused_import
   info • Unused import: 'package:[app]/main.dart' •
          test/widget_test.dart:10:8 • unused_import

2 issues found. (ran in 6.6s)

[✓] Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.5 19F96, locale pt-BR)
    • Flutter version 1.20.2 at /Users/timoteoholanda/development/flutter
    • Framework revision bbfbf1770c (2 weeks ago), 2020-08-13 08:33:09 -0700
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/timoteoholanda/Library/Android/sdk
    • Platform android-30, build-tools 29.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.1, Build version 11A1027
    • CocoaPods version 1.9.2

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.13.2

[✓] Connected device (1 available)

• No issues found!

Android builds using flutter build aar --obfuscate --split-debug-info=<a_path> does work as intended, but ios-frameworks is not.

I can reproduce the issue on stable & master
logs.txt

flutter doctor -v
[✓] Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.6 19G2021, locale en-GB)
    • Flutter version 1.20.2 at /Users/tahatesser/Code/flutter_stable
    • Framework revision bbfbf1770c (2 weeks ago), 2020-08-13 08:33:09 -0700
    • Engine revision 9d5b21729f
    • Dart version 2.9.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.1
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.13.2

[✓] Connected device (1 available)
    • iPhone 11 (mobile) • A63D6F51-59F3-4A75-961F-3769709F3A92 • ios •
      com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)

• No issues found!

flutter doctor -v
[✓] Flutter (Channel master, 1.22.0-2.0.pre.105, on Mac OS X 10.15.6 19G2021, locale en-GB)
    • Flutter version 1.22.0-2.0.pre.105 at /Users/tahatesser/Code/flutter_master
    • Framework revision cad4d1333e (9 hours ago), 2020-08-27 17:48:05 -0700
    • Engine revision 77dd1c05b9
    • Dart version 2.10.0 (build 2.10.0-67.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.1
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.48.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.13.2

[✓] Connected device (4 available)
    • iPhone 11 (mobile) • A63D6F51-59F3-4A75-961F-3769709F3A92 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)
    • macOS (desktop)    • macos                                • darwin-x64     • Mac OS X 10.15.6
      19G2021
    • Web Server (web)   • web-server                           • web-javascript • Flutter Tools
    • Chrome (web)       • chrome                               • web-javascript • Google Chrome
      84.0.4147.135

• No issues found!

I thought this was hooked up in https://github.com/flutter/flutter/pull/59874 and https://github.com/flutter/flutter/pull/60041, \cc @jonahwilliams

I have the same problem in v1.22.

I have the same problem in Flutter 2.2.1 stable.
And It seems didn't obfuscate anything because two "App.framework"s builded with/without flags "--obfuscate --split-debug-info=<a_path>" are exactly the same size. and there is only a few differences in binary comparing.

I have the same problem in Flutter 2.2.1 stable.
And It seems didn't obfuscate anything because two "App.framework"s builded with/without flags "--obfuscate --split-debug-info=<a_path>" are exactly the same size. and there is only a few differences in binary comparing.

The fix is in 2.3.0-12.0.pre.

I have the same problem in Flutter 2.2.1 stable.
And It seems didn't obfuscate anything because two "App.framework"s builded with/without flags "--obfuscate --split-debug-info=<a_path>" are exactly the same size. and there is only a few differences in binary comparing.

The fix is in 2.3.0-12.0.pre.

Thanks, it works when I upgrade to 2.3.0-16.0.pre


Pull request for Blog app: add devise

Dear reviewer,
In this PR:

Project requirements

Removed current_user method in ApplicationController, devise will provide us with one.
Installed and setup devise.

Can register a new user.
User logs in with a combination of email and password.
Hashed password should be stored in the database.
Ask for confirmation of email.
Can reset password.

Modified the views in devise for registration and login to match the wireframes from the Sneak Peek and styling.

Thank you!
Regards,
@zuhebahmed88091 @YoutLone

Thank You @julie-ify @topeogunleye


Module/controlfreec/1.0

Pull Request Checklists
Important: When opening a pull request, keep only the applicable checklist and delete all other sections.
Checklist for New Module
Required

[x] I used the cookiecutter template and updated the placeholder rules.

[x] The snakemake rules follow the design guidelines.

[ ] All references to the rules object (e.g. for input files) are wrapped with str().

[x] Every rule in the module is either listed under localrules or has the threads and resources directives.

[x] Input and output files are being symlinked into the CFG["inputs"] and CFG["outputs"] subdirectories, respectively.

[x] I updated the final target rule (*_all) to include every output rule.

[ ] I explained important module design decisions in CHANGELOG.md.

[x] I tested the module on real data for all supported seq_type values.

[x] I updated the default.yaml configuration file to provide default values for each rule in the module snakefile.

[ ] I ensured that all symbolic links are relative and self-contained (i.e. do not point outside of the repository).

[ ] I replaced every value that should (or might need to) be updated in the default configuration file with __UPDATE__.

[ ] I recursively searched for all comments containing TODO to ensure none were left. For example:
grep -r TODO modules/<module_name>/1.0

If applicable

[ ] I added more granular output subdirectories.

[ ] I added rules to the reference_files workflow to generate any new reference files.

[ ] I added subdirectories with large intermediate files to the list of scratch_subdirectories in the default.yaml configuration file.

[ ] I updated the list of available wildcards for the input files in the default.yaml configuration file.

Checklist for Updated Module
To be completed.

It works, but currently only has one output directory (all output dependent on the config_WGS.txt file).
Bedtools, samtools, sambamba are currently dependent on the user's local versions of these programs. (i.e. when generating the initial config_WGS.txt file, I use "which bedtools" , "which samtools", and "which sambamba" to define the path to these programs in the config.

Updated reference files in module.
It will now download/extract .gem mappability files, split genome.fa into the individual chr components, and also generate a chromLength txt file from the genome.fa.fai
Performed test-runs to completion for WGS files under grch37 and grch38

@Jwong684 can you try to address the conflicts?

I fixed the conflicts for the three files and pushed them to my branch.
I think I pulled everything from master into my branch (I used git checkout master, then git pull -ff-only) so all additional files were then staged into my latest commit. I don't think it had any effect other than writing a bunch of files from master into my local repo.


In Tableau 2019.2 set actions cause the extensions to reload it's content

Hello,
We got a report stating that when using set actions with Tableau 2019.2 this was causing issues with the usage of our extensions.
I looked into this and what is happening is that every click on the marks that trigger the set action also trigger a reload on the extension frame causing it to lose its context or content. In our case, we have a login token and it is lost, making it so that we have to login every time the extension reloads.
Have you ever come up with this, is a known issue or is there any way to prevent the extension from reloading?
Best regards,
Bruno

Hrmm, we have a report of this happening when using Parameter Actions and we have some scheduled work to understand the cause of that and fix it. I will add set actions as something to explore as well.

I did some testing with Set Actions. I used the example described here:
https://onlinehelp.tableau.com/current/pro/desktop/en-us/actions_sets.htm#color-scaling
Using this set action, the extension does not get reloaded. Can you share more about your workbook or actions? Do you have other actions on the dashboard? I'm assuming you are using server?
Thanks for the additional information,
John

Hello John.
I'm doing it on the desktop version.
I tested in that example as well, and indeed it does not trigger a reload.
The example that I was using was the asymmetric drill down (available here), and there, whenever selecting a mark for drill down a refresh is performed.
Thanks,
Bruno

The issue with the asymmetric drill down example is that changes the data source / summary data without any notification to the extension, so we must reload. We need to add a "summary data changed" notification, but need to figure out how to do that without breaking existing extensions.

See also https://github.com/tableau/extensions-api/issues/167

I'm going to close this one as we track 167 and 368.


Added testimonials; improvements on the documentation

Checklist
GitHub

[ ] I've given this PR a concise, self-descriptive, and meaningful title
[ ] I've linked relevant issues in the PR body
[ ] I've applied the relevant labels to this PR
[ ] I've applied a release milestone (major, minor, patch) in line with Semantic Versioning guidelines
[ ] I've assigned a reviewer

PR contents

[ ] I've consulted SCT's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

Linked issues

Adding this line to our custom.css file:
.admonition.important p.admonition-title::before{content:""}

Can change the icon for specific admonition types:

(I chose important +  but these can be changed, of course.)

your script is amazingly helpful @kousu, thank you 🙏 !!
i'll tweak it a little bit

@jcohenadad I have made some small corrections in e97d36c, hopefully they are minimal enough. :)
As an aside, I have to say, reading through each testimonial carefully was a very good (inspiring!) experience. These testimonials give a lot of insight into our userbase (and the things that they value most).
It's much clearer to me why so much care and dedication is spent towards the forums; SCT has fostered a small/niche but very dedicated userbase (compared to for-profit software/apps which might be trying to get 1000s and 1000s of users). Each individual interaction with someone on the forums carries so much more weight, which feels very unique.
I think reading these testimonials would be a very good onboarding exercise for devs (especially those who might be used to working for private companies or on products with a larger userbase).

@jcohenadad I have made some small corrections in e97d36c, hopefully they are minimal enough. :)

yes! exactly the type of corrections i was thinking about, thank you!
and thank you for sharing your feedback on the testimonials-- yes, i am glad you are feeling that way. And your analysis of the type of users and importance of the forum is absolutely correct.

If someone backports e97d36c0b4a288e5be1596d3f71702cb30fa57ac into the google spreadsheet then next time you export the spreadsheet into .rst it will retain the patches. And you should also be able to backport sorting the testimonials in the same way, just rearrange the rows in the spreadsheet.

If someone backports e97d36c into the google spreadsheet then next time you export the spreadsheet into .rst it will retain the patches. And you should also be able to backport sorting the testimonials in the same way, just rearrange the rows in the spreadsheet.

the problem is that gform answers are not editable

@joshuacwnewton i'm quite happy with how it looks like-- can we approve so i can reach out to our sponsors?

If someone backports e97d36c into the google spreadsheet then next time you export the spreadsheet into .rst it will retain the patches. And you should also be able to backport sorting the testimonials in the same way, just rearrange the rows in the spreadsheet.

the problem is that gform answers are not editable

I just put 'fsdf' into this one:

If someone backports e97d36c into the google spreadsheet then next time you export the spreadsheet into .rst it will retain the patches. And you should also be able to backport sorting the testimonials in the same way, just rearrange the rows in the spreadsheet.

the problem is that gform answers are not editable

I just put 'fsdf' into this one:

it saved just fine:

It seems like it's only one way though, form -> spreadsheet -> export -> script -> rst. The spreadsheet can't edit the results listed on the form:
 !=
should be fine for your purposes though?

exactly, and that’s the problem. The ‘fsdf’ only appeared in your exported gsheet. If i was to export the gform to update the RTD i would see the ‘fsdf’. Gforms are not editable.


Reverse feature

Per the PyPI page, attempting to reverse a folder I added earlier with the "beet -r noimport "D:\Music" command. I'm getting the following error-
Usage:
beet-script.py COMMAND [ARGS...]
beet-script.py help COMMAND
beet-script.py: error: no such option: -r
Is there something I need to add/edit in my config to get the reverse function working?
All other features working great. Thank you!

Hi @n8er11, what are you attempting to do exactely?
What this plugin will do is add a file or directory to the incremental import ignore list, meaning those files will be ignored the next time you do an incremental import that would otherwise include them, it doesn't have any flags that you can use.


can not get the use element correct bbox

this is my test https://jsfiddle.net/xiaozhu2018/hss9o6ct/1/
the rect element bbox is correct,but
why the use element bbox width is 0,

Does seem a bit odd...couple of workarounds in the meantime may be to either call element.node.getBBox() or put the use element inside a g element and call getBBox() on that.

@ibrierley  but when i use elem.node.getBBox() , the width and height  not 0,but is also not the attribute value in document.look at here:https://jsfiddle.net/xiaozhu2018/h5s5hnxq/
in document the use height is 300,but getBBox().height is 452.
it confused me


在weex中用vue语法如何获取当前的时分秒？

var date = new Date();
var hours=date.getHours();
这样获取小时不对，我在中国，少了8小时

new Date()获取的是操作系统上的时间，你检查一下系统的时区和时间看看

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Hide Banner without losing back button & reduce overlap with content

We haven't been able to effectively hide the banner without losing the back button. Also the back button - as we have styled it -  overlaps and distorts text on scroll

@slowbot

@slowbot Did we ever get the back button white space fix in?


Remove key management setting in wpa_cli examples

When manually setting the key management, this will actually cause wifi to not connect if a different type is used by the access point.
WPA supplicant typically can detect the key management from the access point's broadcast, and not overriding it has a bigger chance of succeeding.
As a wpa_cli newbie, I just followed the instructions in the manual on the minimal install disk and they didn't work. I tried setting key_mgmt what was shown in the scan results, but wpa_cli barfed at the string (quoted or unquoted). Only when dropping the set key_mgmt line entirely, it worked. So I think this would provide a better help for people using the minimal install disk.
NOTE: IMO a better approach would be to provide something like wicd-curses or nmtui in the minimal installation disk instead, as they're a little bit more user-friendly than wpa_cli.

@bobby285271 Any further comments? Is this related to security concerns?

Looks good, please reword commit to nixos/doc: remove key management setting in wpa_cli examples

Done


Mounting directories r/w

#592 describes the way (actual at lest for 0.10) to mount directories read only:
lxc config device add contname sharename disk source=$PWD path=/home/pathinside

How to mount them with write privileges?

This command above mounts the folder nobody:nobody, and it is impossible to create anything in it.
@stgraber mentions that this command supports three types of mounts:

partitions - `source=
block devices - source=/dev/blockdevice
file or dir - source=/host/file

The actual for this issue (3) is mounted using "bind mount", and it looks like LXC requires some kind of access control like ownership to enable r/w for that. So, LXD needs to map directory owner from host to guest. So, how to do this?
And also, from the user point of view that mapping is not always necessary. I'd be happy to operate with directory that has write and execution permissions for everybody. Is it possible to teach LXD/LXC to share directory in this way?
Or it is possible to make automatic mapping from current user to root? Like:
lxc config device add contname sharename disk source=$PWD path=/home/pathinside rwmap=$USER:root

?
Ideally, there should be something that is easy to memorize, and what could have dedicated help page.
lxd mount host=$PWD guest=/root/somename

So, can anybody tell me how to make a shared folder writable with LXD? =(

That's actually harder than it may seem and short of having some kind of uid/gid switching in-kernel filesystem, there's no single good solution for LXD to do that.
For now, what you need to do is setup a bind-mount as explained before, then make the folder on the host writable by the uid/gid in the container. You can do so with:

Changing the file/dir mode to allow writes by all users/groups
Chowning the file/dir to the uid/gid in the container
Setting up POSIX ACLs, allowing the uid/gid in the container access to the folder.

@stgraber thanks for clarification. Does ACL work on this level - can I use it?
How can I get UID/GID of container programatically for my chmod command? (I need to get root user)

The uid/gid will be the base allocation for the lxd user (can be found in /etc/subuid and /etc/subgid) + the uid/gid inside the container.
So here the "lxd" user has "lxd:100000:65536" which puts the first uid at 100000, so root will be 100000 and uid 100 would be 100100.
As for setting the ACLs, you can do that with setfacl, using those uid/gids.

So here the "lxd" user has "lxd:100000:65536" which puts the first uid at 100000, so root will be 100000 and uid 100 would be 100100.

This is only true if you have one container running, but what if you have several? Is there a way to query running container about its uid/gid mappings?

We do not currently do per-container uid/gid maps, all containers run by LXD share the same map, so what I said above will work fine.

I have found a slightly different solution by just setting the uid and gid flag when bind-mounting. It does not change the hosts permissions.
My current entry in lxd looks like this:
raw.lxc: lxc.mount.entry =   none bind,create=dir,rw,uid=10000,gid=100000
as there is no native support in lxd to set these flags as far as I have seen.

what filesystem are you bind-mounting? I can see how this may work with vfat but I'm not sure how a uid/gid aware filesystem would work.

I tried ext4, although it did not work.
I could also try btrfs if you'd like to hear the results.

Both ext4 and btrfs are uid/gid aware. So both of them don't work without ACL's.
This is my setfacl line which i use for a container data directory:
setfacl -Rm user:lxd:rwx,default:user:lxd:rwx,user:100000:rwx,user:101000:rwx,default:user:100000:rwx,default:user:101000:rwx /cdata/saltmaster

It gives the container root (100000) and the default container user (101000) permanent access to this directory.

Is there a way to ensure that any newly created files (from outside the container) in the shared directory inherit the ACLs?

That's what the "default:" keyword does, or at least that's my (limited) understanding of POSIX ACLs.

Oh. Okay, that would have been useful to know one or two days ago.
Thank you for that.

I'm trying to follow the instructions here: https://github.com/lxc/lxd/issues/592#issuecomment-99904045
I created a group lxd-share with gid 1001 and added my user on the host machine. chowned the directory to that group.
host /etc/subgid
jason:100000:65536
lxd:165536:65536
root:165536:65536
root:1001:1

id_map
name: trusty-01
profiles:
- default
config:
  raw.lxc: |
    lxc.id_map = g<PHONE_NUMBER> 1

guest /etc/group: http://paste.ubuntu.com/13071847/
Calling id inside guest: uid=0(root) gid=0(root) groups=0(root)
Calling sudo id inside guest: uid=0(root) gid=0(root) groups=0(root),400000(lxd-share)
So I can edit the shared files if I do it as sudo, but I can't edit the files without sudo. How do I get it to work without sudo?

Add lxd-share (400000) to your user's list of groups in the container (using /etc/group) so that 'id' inside the guest shows lxd-share.

Maybe I'm misunderstanding your instructions, but I've already added lxd-share:x:400000:root to my /etc/group file inside the container as seen here: http://paste.ubuntu.com/13071847/.
When I /bin/bash into a clean container my user is root. But using lxd-share:x:400000:root doesn't add the group to root as indicated by id. It only adds the group to sudo for some reason hence why sudo id shows the lxd-share group.

Oh, sorry, I though the first 'id' in your previous output was as the user.  It's as root.
I'm actually not clear why the first shell isn't enabling your supplementary groups.

No problem. When I create a standard container and enter it via lxc exec trusty-01 /bin/bash, the default user is root correct?
Also continuing to look into this, I'm seeing some very odd behavior.
# starting as the host
jason@ubuntu:~$ lxc exec trusty-01 /bin/bash
root@trusty-01:~# id
uid=0(root) gid=0(root) groups=0(root)
root@trusty-01:~# id root
uid=0(root) gid=0(root) groups=0(root),400000(lxd-share)
root@trusty-01:~# sudo id
uid=0(root) gid=0(root) groups=0(root),400000(lxd-share)

Somehow this is the cause of my issue, but I don't know how?

That'd be because LXC doesn't setup your groups on attach.
Unfortunately doing so requires knowledge of the distribution inside the container which LXC doesn't have, so I expect it's just not bothering to do nss initialization (init_groups()).
We could probably update LXC to attempt nss initialization using the same location as the host it's running on (so using the nss functions of glibc) and if that fails, then continue without the group initialization.
@hallyn thoughts?

  Obviously just running bash won't call the pam session plugin, which is the one which does this.
Manually reaching into the container to poke nss seems like begging for trouble or container security breaches.
Doing
lxc exec container -- su - root
gets you the list of groups.  So if we cared, the simplest thing would be to have a simple alias for that, or something like
lxc login container [@user - root by default ]
which is hard to keep semantically clean.

So if I understand this correctly by calling su - root we "switch" to root even though it's already the default, but by doing so it triggers the group initialization?
Aside from triggering the group initialization, is it any different than /bin/bash? All I'm trying to do is use lxd/lxc for creating development environments that don't pollute my host. If I start installing things after using su - root everything will run the same as if I had entered /bin/bash the difference is the supplementary groups will be there?
And from a security perspective is the lxc exec container -- su - root ok to use? Thanks for all your help.

On Thu, Nov 05, 2015 at 05:10:12PM -0800, Jason Blalock wrote:

So if I understand this correctly by calling su - root we "switch" to root even though it's already the default, but by doing so it triggers the group initialization?

Right, the 'su' program  in the container itself will call its PAM plugin
to setup groups.  Then run the user's default shell or the specified command.

Aside from triggering the group initialization, is it any different than /bin/bash?

Root may well have another shell as its default shell, i.e. dash.  So
you may need to tell su to run bash if that's what you need, i.e.
su - root -c bash

And from a security perspective is the lxc exec container -- su - root ok to use? Thanks for all your help.

(sorry skipped htis in last reply) - yes, it is ok to use afaik.

That'd be because LXC doesn't setup your groups on attach.

It may be just me but I have to admit I would except LXC doing this for me.

Unfortunately doing so requires knowledge of the distribution inside the container which LXC doesn't have, so I expect it's just not bothering to do nss initialization (init_groups()).

That sounds like another hook to me. Each image/container should tell the hypervisor where to find the triggers for group initialization.
(Disclaimer: I am honestly surprised that group initialization is some sort of a separate/optional module; when I consider all the scripts/modules I know which simply assume proper setup of all additional groups...)

@stgraber

We do not currently do per-container uid/gid maps, all containers run by LXD share the same map, so what I said above will work fine.

Can this be abused (aka security hole)?

All containers sharing the same map, makes resource starvation DoS possible, yes. That is, anything covered by ulimits will be counted together for all containers using the same uid/gid.

As for initializing the group list, the problem is that this is a purely userspace thing, Android does it differently from other distros and even within distros things may vary widely.
Having LXC or LXD parse a file from inside the container and then call a bunch of syscalls from outside the container is a security risk and one we've been unwilling to take for LXD so far (that's also why we don't allow script/binary hooks inside LXD).

Having LXC or LXD parse a file from inside the container

I thought hooks/templates are not part of the container but a mere description of where to find things inside.

call a bunch of syscalls from outside the container

Correct me if I am wrong but how does "su - root" do it then? It runs inside the container and changes things inside, right?

So there are a few things:

We don't ever want to parse a container file from outside the container as if we screw up the parser, you'd be running code as root on the host. That concern is about parsing /etc/passwd and /etc/group specifically, not about parsing container metadata (which can't be modified from inside the container).
The location and syntax of the files to parse varies between Linux distributions.
Anyone using libnss plugins in /etc/nsswitch.conf for passwd or group wouldn't get the right groups as those plugin need to be loaded and executed and may then depend on network connection.

su -u root runs entirely inside the container through the LXC attach interface, so hits the container's C library which may then talk to libnss which will then parse /etc/nsswitch.conf and call the relevant plugins.
We could extend the attach interface in liblxc, though that may well be an ABI break so we'd need a new library symbol for it... Such an extension would have liblxc make a good guess and parse /etc/passwd, /etc/group and /system/etc/passwd and /system/etc/group from inside the container so avoiding the big security issue. That still wouldn't work for anyone using libnss-extrausers, sssd or any other nss plugin though.

@stgraber Thanks for you detailed response. I am not so deep into that matter, however, I feel that all tools which do the parsing already (like "su -") are available in the container. Otherwise, the container does not support proper group setup.
Thus, why not having a "pre-attach" hook that basically call a predefined cmd (available in the container) to setup the group initialization (such as "su-")?
So, no extension that guesses and parses things (which I generally dislike).

You may be able to do something with the lxc command aliases, basically aliasing "lxc exec container COMMAND" to "lxc exec CONTAINER su - COMMAND".
@tych0 does the aliasing stuff allow for re-organizing arguments like that? ^

On Tue, Dec 01, 2015 at 09:19:23AM -0800, Stéphane Graber wrote:

You may be able to do something with the lxc command aliases, basically aliasing "lxc exec container COMMAND" to "lxc exec CONTAINER su - COMMAND".
@tych0 does the aliasing stuff allow for re-organizing arguments like that? ^

I think so, something like:
aliases:
  command: su - command

should work.

Reply to this email directly or view it on GitHub:
https://github.com/lxc/lxd/issues/714#issuecomment-161038137

So, this needs to be part of the container's metadata, right?

Seems like a lot of the things discussed in there have been addressed through fixes or workarounds, the rest is mostly design decision, closing this catch all issue.
If there are specifics that still need addressing, please file specific issues.

@stgraber how does it handle multiple containers mounting the same path, does it allow it?


Add isRounded as Image props

Fix #128

Coverage remained the same at 100.0% when pulling 833cc8fc563f06d3ca2ead5fca0922068c782f2f on gaillota:feat(image)/is-rounded-props into b9af8271840c9a52ecf493f3b1f919d8cd3e5fc1 on AlgusDark:master.