How can I enable WebGL rendering?

The ArcGIS docs recommend using WebGL rendering rather than default SVG rendering for creating client-side Feature Layers.
https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#webgl-rendering
In order to do this, the docs say:
To enable WebGL rendering for FeatureLayers, paste the following script in your application prior to loading the ArcGIS API for JavaScript:
    <script>
      var dojoConfig = {
        has: {
          "esri-featurelayer-webgl": 1
        }
      };
    </script>

Have you tried doing just that? Place a script like that in your document's <head>?

@shadab08 Did Tom's comment work for you?

It is not working for me. Though I am not sure whether implementing Tom's suggestion had any impact or not. There are other limitation of WebGL which might be preventing it from working in my case as highlighted in below post.
https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-FeatureLayer.html#webgl-rendering
For now, we have dropped the idea of using highlight feature but instead we are playing around with Graphics.
Thanks for helping me out. I will closing this ticket.


handle TERM signal, add a shutdown code path

our shutdown code path needs to close sockets which if they are unix domain sockets causes their socket file to be removed from the filesystem. We need this behavior so that next time the daemon is stated we can recreate the unix domain socket files with the same specified names without conflict... otherwise the startup will fail if the socket files already exist.

The golang unix domain socket listener does remove the socket file is it's Close method is called. This is a pretty good blog post and proof of concept code for listen accept loop shutdown in golang:
http://zhen.org/blog/graceful-shutdown-of-go-net-dot-listeners/

please review
https://github.com/subgraph/roflcoptor/pull/22/files

fixed forever
https://github.com/subgraph/roflcoptor/commit/0866ee83579c3546479e2a030cb144ca4ddf3ea4


Integration of the new schema and KTT support

Hi,
based on our discussions, I have implemented the following:

change the schema of the experiment setup json file
support one input json file per experimental group

user-provided input json file for each application
list of applications and GPUs
within the package, an input json file is created for each experimental group (combination of application, GPU and search strategy) and then loaded and executed by the autotuner

autotuners KernelTuner and KTT supported

we allow to use your own complied executables/libraries of autotuners
but provide abstraction to default (current version) of autotuners, this goes only for KT currently, KTT needs to be built by the user

predetermined directory structure that separates setup files and output files

and makes it possible to run the experiments on a cluster and do the visualization part on local computer

Known TODOs:

get it working with KernelTuner. I'm not sure whether KT already supports input json as a single input for run.
fix visualization part even for KTT. autotuning_experiment finishes fine for all three examples (experiment_files/ktt_*.json), visualization gets stuck on the same error for all three of those.
modify and add tests

I have tried to follow at least some of the contributing guidelines (I think the formatting should be more or less fine and I'm sending you my notes and draft of user guide). I'm sorry to leave this project in this state, ideally I'd like to give it one or two more months to have it more tested and polished for production, but alas, life has its own time frames and I really can't postpone this one :)

Thank you for your major contribution @jhozzova. It's been a pleasure discussing the standardization and extension of the methodology package with you. I've merged this into the standardization branch so I can continue to implement the remaining tasks and test the changes.


doc: update documentation release

:tada: This PR is included in version 1.0.2-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


add list of case studies to README

As the number increases, a list would be helpful. The github.io page includes links to each case study in the navigation bar, but this isn't as clear as a README list.
List could include a column stating the status as in-progress vs complete.
Or maybe incomplete case studies should all be in branches (e.g. https://github.com/NOAA-FIMS/case-studies/tree/NWFSC-petrale).
Relates to #6.

Expanding the README to include more info on the current goals of the case studies
Current goals for the case-studies discussed with @ChristineStawitz-NOAA, @Bai-Li-NOAA, @Andrea-Havron-NOAA, @k-doering-NOAA, and @nathanvaughan-NOAA during sea-side chat include:

provide a way for the FIMS implementation team to learn more about the current ways of interacting with FIMS
help identify ways that the input and output needs to be improved
identifying common model needs across regions to inform prioritization of features

Thanks for capturing @iantaylor-NOAA, and for bringing up your thoughts on purpose of the case studies during the seaside chat!

I just added a list (or table) of case studies to the README in 6f938ad.
I'll leave this issue open in case folks want to suggest additional refinements, such as

add column for point of contact?
add column for name of assessment platform used in status-quo model?
make table available on the quarto site homepage by adding to https://github.com/NOAA-FIMS/case-studies/blob/main/index.qmd (might require R script to modify index.qmd by github action if we want a single table to appear in both places)?

@iantaylor-NOAA and @Bai-Li-NOAA I am happy with the current table and this issue has been stale since April 26th without any further suggestions so I think it should be closed.


FIX: Preview images updated even with the "Download NSFW (adult) prev…

…iew images" unchecked.
Updating to allow preview images to be updated even with the "Download NSFW (adult) preview images" unchecked. It appears that the 'nsfw' value used to be True|False, and is now a string with values like None, Mature, X, etc.

Pada Rab, 17 Jul 2024, 20.57, Luoyi123 @.***> menulis:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/civitai/sd_civitai_extension/pull/120#pullrequestreview-2182847306,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVEAOZJRHD7X5WHBY4UHOTLZMZS3XAVCNFSM6AAAAABLASURMWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCOBSHA2DOMZQGY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I can no longer generate, my regret
ср, 17 июл. 2024 г., 16:46 Luoyi123 @.***>:

Pada Rab, 17 Jul 2024, 20.57, Luoyi123 @.***> menulis:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
<
https://github.com/civitai/sd_civitai_extension/pull/120#pullrequestreview-2182847306>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AVEAOZJRHD7X5WHBY4UHOTLZMZS3XAVCNFSM6AAAAABLASURMWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCOBSHA2DOMZQGY>

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/civitai/sd_civitai_extension/pull/120#issuecomment-2233369354,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIPQOJT6GTZUK5R3JQPKAKLZMZYUHAVCNFSM6AAAAABLASURMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZTGM3DSMZVGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Regression: avoid download dockerize-alpine-linux-amd64-v0.6.1.tar.gz

Looking through issues and merged PRs it seems this has already been fixed once, although it still seems to be an issue:
Issue #136 was fixed by #148

each time build images by executing ./mvnw clean install -PbuildDocker ,it needs download dockerize-alpine-linux-amd64-v0.6.1.tar.gz from github, can you do some optimization?

It looks like the fix is not working or have been breaked.
Does someone has any idea to cache dockerize?

Should be fixed by https://github.com/spring-petclinic/spring-petclinic-microservices/pull/247


Token Assert: normalize whiteSpace assertions to match line assertions

:+1: +1 lgtm

Coverage increased (+0.01%) to 99.09% when pulling b3f2516f1a5fbc60f2ca9cbb33b64564e85729b0 on mikesherov:spaces into f55bbae8bfbd8d57a4f756193d824e6f398ff7a7 on jscs-dev:master.

Coverage increased (+0.01%) to 99.09% when pulling 41042e989f13a894a66a24ec893fc4465a4dd558 on mikesherov:spaces into f55bbae8bfbd8d57a4f756193d824e6f398ff7a7 on jscs-dev:master.

Coverage increased (+0.01%) to 99.09% when pulling 51bd7a57796433372c5bb2199fed4f8ec81b6bf0 on mikesherov:spaces into f55bbae8bfbd8d57a4f756193d824e6f398ff7a7 on jscs-dev:master.

:+1: Yeah, I like it too ;-)

Since there is only concerns with the tests we can improve that later.

I only fear that spacesBetween  might become a some sort of god function, since now it's used by a lot of methods and its cyclomatic complexity is pretty high.

Do you feel differently about linesBetween?

As I see it's just because of BC, I think we shouldn't worry about it because public API is pretty stable and shouldn't drastically change in future.
And because of that we can decrease this complexity by several waves of refactoring.
We just need it to finish giant leap for mankind ;-)

It's complexity is only high because of BC and having tons of varying error messages.
It will get better in 2.0 and I wouldn't worry about it.

Just out of curiosity, I've been seeing it a bunch. What is BC in this context?

Back compatibility ;-)


establish testing against A+ API (A+ image in Travis build)

ensure there's testing (dummy) data
automated integration testing
selection of the integration testing library
update the manual testing environment (this probably needs some changes somewhere)

https://github.com/Mankro/course-templates/blob/test/tools/test-bench-course-mod.py - addition script to populate DB

https://github.com/Aalto-LeTech/intellij-plugin/issues/67#issuecomment-585138468

now this is our own fork of aplus course template repo: Aalto-LeTech/course-templates

https://minus.cs.aalto.fi/


Showcase cmichel io

Showcase for my blog cmichel.io

Looks good. Thank!
Will appear on the website after next release :)


Feat: format internlm2 chat template

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness.
If the modification has a dependency on downstream projects of a newer version, this PR should be tested with all supported versions of downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

pls fix linting error

UT about new added code snippet will be appreciated.

@Harold-lkk pls help review this PR

May provide an example or a unit test.


IAM User Credential Rotation Causes Terraform EKS Provider Connection Refused Error

Description
When IAM user (cicd) credentials rotated that are used for executing Terraform, the Terraform AWS EKS provider fails to recognize the same user with the previous credentials. This issue is observed during the execution of the Terraform plan. The same user (cicd) is used in the aws-auth config map in the mapUsers section.
I'm using Kubernetes provider that looks like the below:
provider "kubernetes" {
  host                   = module.eks.cluster_endpoint
  cluster_ca_certificate = base64decode(module.eks.cluster_certificate_authority_data)
  exec {
    api_version = "client.authentication.k8s.io/v1beta1"
    command     = "aws"
    # This requires the awscli to be installed locally where Terraform is executed
    args = ["eks", "get-token", "--cluster-name", local.cluster_name]
  }
}

aws-auth configmap data block looks like below:
data:
  mapAccounts: |
    []
  mapRoles: |
    - "groups":
      - "system:bootstrappers"
      - "system:nodes"
      "rolearn": "arn:aws:iam::1234567890:role/test_eks_node"
      "username": "system:node:{{EC2PrivateDNSName}}"
    - "groups":
      - "system:masters"
      "rolearn": "arn:aws:iam::1234567890:role/test_eks_user"
      "username": "admin:{{SessionName}}"
  mapUsers: |
    - "groups":
      - "system:masters"
      "userarn": "arn:aws:iam::1234567890:user/cicd"
      "username": "cicd"

Version Information
Terraform version: v1.1.4
AWS EKS provider version: v4.67.0
Steps to Reproduce
Rotate IAM user credentials associated with the AWS EKS cluster.
Run Terraform plan or apply.
Expected Behavior
Terraform should successfully recognize the IAM user with the updated credentials and apply changes accordingly.
Actual Behavior
Terraform fails with the following error:
│ Error: Get "http://localhost/api/v1/namespaces/kube-system/configmaps/aws-auth": dial tcp <IP_ADDRESS>:80: connect: connection refused
│
│   with module.eks.kubernetes_config_map.aws_auth[0],
│   on .terraform/modules/eks/main.tf line 453, in resource "kubernetes_config_map" "aws_auth":
│  453: resource "kubernetes_config_map" "aws_auth" {

Workaround
I have to update the Kubernetes provider to use config_path instead of exec plugin from my local and fix this error before running it on the cicd pipeline.

this is not related to the module


Updated support email

Your changes look good to me. I added a few more tweaks, please double check.


feat(standalone): added fetchye provider and headless

Added FetchyeProvider. Standalone Provider based on useReducer for cache store
Added fetcher option to both FetchyeProvider and FetchyeReduxProvider
Added Headless mode via using the new useFetchyeContext hook  that includes useReducer based fallbacks when context is empty. Hooks can function provider-less now.
Added new Cache abstraction where the reducer, getCacheByKey, and  optional cacheSelector fields are set. Opens door for easy custom cache writing. Storage is managed by Redux or useReducer  inside the Provider layer. Cache is more a function that returns  a configuration
Added ImmutableCache and SimpleCache that works for either Redux or useReducer based Providers or Headless mode.

Todos

[ ] Updated the README with API updates and examples
[ ] Add Codesandbox examples

@mtomcal so it looks like it works with Next.js https://codesandbox.io/s/jamessingletonfetchye-nextjs-forked-ry9jf?file=/pages/index.js
However, I had to remove const cache = SimpleCache() becuase I was getting the following
TypeError: Object(...) is not a function
    at eval (webpack-internal:///./pages/index.js:15:74)
    at Module../pages/index.js (/sandbox/.next/server/static/development/pages/index.js:278:1)
    at __webpack_require__ (/sandbox/.next/server/static/development/pages/index.js:23:31)
    at Object.3 (/sandbox/.next/server/static/development/pages/index.js:289:18)
    at __webpack_require__ (/sandbox/.next/server/static/development/pages/index.js:23:31)
    at /sandbox/.next/server/static/development/pages/index.js:91:18
    at Object.<anonymous> (/sandbox/.next/server/static/development/pages/index.js:94:10)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at requirePage (/sandbox/node_modules/next/dist/next-server/server/require.js:2:457)
    at loadComponents (/sandbox/node_modules/next/dist/next-server/server/load-components.js:1:967)
TypeError: Object(...) is not a function
    at eval (webpack-internal:///./pages/index.js:15:74)
    at Module../pages/index.js (/sandbox/.next/server/static/development/pages/index.js:278:1)
    at __webpack_require__ (/sandbox/.next/server/static/development/pages/index.js:23:31)
    at Object.3 (/sandbox/.next/server/static/development/pages/index.js:289:18)
    at __webpack_require__ (/sandbox/.next/server/static/development/pages/index.js:23:31)
    at /sandbox/.next/server/static/development/pages/index.js:91:18
    at Object.<anonymous> (/sandbox/.next/server/static/development/pages/index.js:94:10)
    at Module._compile (internal/modules/cjs/loader.js:778:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at requirePage (/sandbox/node_modules/next/dist/next-server/server/require.js:2:457)
    at loadComponents (/sandbox/node_modules/next/dist/next-server/server/load-components.js:1:967)

Closing this PR in favor of a fresh one due to all the changes required at this Draft PR.


Fix readme

PR Checklist

[ ] A description of the changes is added to the description of this PR.
[ ] If there is a related issue, make sure it is linked to this PR.
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] Documentation in docs is updated

Description of changes

Codecov Report

Merging #69 (bb652d9) into main (40f256b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head bb652d9 differs from pull request most recent head e9196ec. Consider uploading reports for the commit e9196ec to get more accurate results

@@          Coverage Diff          @@
##            main     #69   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          1       1
  Lines          5       5
=====================================
  Misses         5       5

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


Accessibility: Search menu responses to keyboard input

Example A

boot from hello-0.3.0_0C160-FreeBSD-12.1-amd64.iso
type rest
observe selection of every character that was typed
key Down

Expected:

selection of System → Restart

Actual result:

selection bounces away from the required action
up to the Search field, with the entire phrase selected

Workaround:

key Left does move the selection down, however this is wrong because at step (3) above there should be a text cursor

– key Left should move the vertical line one step to the left, to between the characters s and t

This is because we virtually press Down whenever there is only one match left, to get the remaining match selected automatically. We need to find a better way indeed!

This is because we virtually press Down whenever there is only one match left, to get the remaining match selected automatically. We need to find a better way indeed!

Needs a text cursor in the Search menu, agreed?

Needs a text cursor in the Search menu, agreed?

I do have a cursor here and it even blinks...

I do have a cursor here and it even blinks...


Dependent Dropdown

This is  a question.

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
[x] Did you check the documentation?
[x] Did you perform a cursory search?

Description

Can this create dependent dropdown?
Steps to Reproduce

Expected behavior

Actual behavior

Define dependent dropdown.
Check the examples if you didn't by now


How to get redirected arguments?

Please help me with the argument redirection.
I am sure that I missed out something, or is it something that has to be done by hand?
# runs as expected result is: test: foobar
dotnet run test foobar

# does not work, displays the result with an empty Message
echo "foobar" >> test.txt
dotnet run test < test.txt

Same on powershell
# runs as expected result is: test: foobar
dotnet run test foobar

# does not work, displays the result with an empty Message
 Get-Content .\test.txt | dotnet run test

Source:
using System;
using McMaster.Extensions.CommandLineUtils;

namespace TestTools
{
    [Command(Name = "tools", Description = "Tool collection ")]
    [HelpOption("-?")]
    [Subcommand("test", typeof(TestCommand))]
    class ToolProgram
    {
        public static int Main(string[] args)
            => CommandLineApplication.Execute<ToolProgram>(args);

        public int OnExecute(CommandLineApplication app)
        {
            app.ShowHelp();
            return 1;
        }
    }

    [Command(Description = "testing")]
    class TestCommand
    {

        [Argument(0,"message")]
        public string Message { get; private set; }

        public int OnExecute(CommandLineApplication app)
        {
            Console.WriteLine($"test: {Message}");
            return 1;
        }

    }
}

Hi @frdani is this a new feature request? If you're looking for support on the McMaster.Extensions.CommandLineUtils project, Nate's work is located here 🙂

Thanks! I'm using Nate's lib, I totally should have posted it there.


full db-sync sync tests on Mainnet and Testnet

Scope:

allow running the sync from snapshot tests after the full sync from a clean state

Details:

considering that at the end of the sync from clean state we have both the fully synced node and db-sync, we would everything we need to sync db-sync also from snapshot

Steps:

fully sync node
fully sync db-sync from clean state
if everything is ok --> write the sync test values o db
if everything is ok --> generate a snapshot for the selected environment
write the values into the db (related to the snapshot creation)
remove the state of db-sync
restore db-sync from the previously created snapshot
write the values into the db (related to the sync from snapshot)

Notes:

ideally, the script would be parameterizable --> if a parameter is provided it will run the sync from snapshot too, if not, it will run only the sync from a clean state

Scope/goal:

[X] allow running the sync from snapshot tests after the full sync from a clean state

is completed.
We gather and send results to AWS database. Adjustments & improvements can be made in the future in regards of what else we can track. There is an option (checkbox) that determines whether only full sync from clean state should be run or the whole cycle - that will, after full sync is completed, create snapshot then restore it and finally start cardano-db-sync in order to check if restoration was succesfull from service POV and there are no rollbacks or errors.
GitHub Actions flow: https://github.com/input-output-hk/cardano-node-tests/actions/workflows/db_sync_full_sync.yaml

Artifacts we expose:


use snappy1 from hdp-utils when hdp on ubuntu16

fix libsnappy-dev installation on ubuntu16.  HDP-Utils provides libsnappy1, which conflicts with ubuntu's libsnappy1v5.
(or maybe we just specify only libsnappy-dev and let apt sort it out).

I say we merge this, then simply switch to multi-package installs to avoid these dependency issues.

Merging this to unblock some other work.


support classfile new syntax project/class

https://github.com/goplus/gop/issues/1370
project [.projExt ProjClass] pkgPath ...
class .workExt WorkClass

Codecov Report
Patch coverage: 71.92% and project coverage change: -7.90 :warning:

Comparison is base (8c8dbe2) 100.00% compared to head (84b06be) 92.10%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@             Coverage Diff             @@
##              main       #9      +/-   ##
===========================================
- Coverage   100.00%   92.10%   -7.90%
===========================================
  Files            3        3
  Lines          336      380      +44
===========================================
+ Hits           336      350      +14
- Misses           0       22      +22
- Partials         0        8       +8

Impacted Files
Coverage Δ

modfile/rule.go
92.02% <71.92%> (-7.98%)
:arrow_down:

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


How to run New-ServicePrincipal

It could be a simple question, but I didn't find a way to run New-ServicePrincipal, I've imported various exchange module but still got
New-ServicePrincipal: The term 'New-ServicePrincipal' is not recognized as a name of a cmdlet, function, script file, or executable program.

How can I run that cmdlet?

Hi @alkampfergit I think you figured this out, correct?


GaussNoise does not work correctly on small images

🐛 Bug
Hi Vladimir!
The error lies in the fact that the GaussNoise method does not work correctly on small pictures (i tested 128*64), since the argument var requires an integer value:  GaussNoise(var_limit=(1, 1), always_apply=False, p=1)
https://files.slack.com/files-pri/T040HKJE3-FGMFW433R/image.png
It helped for me:
def add_gaussian_noise(image_in, noise_sigma):
    temp_image = np.float64(np.copy(image_in))

    h = temp_image.shape[0]
    w = temp_image.shape[1]
    noise = np.random.randn(h, w) * noise_sigma

    noisy_image = np.zeros(temp_image.shape, np.float64)
    if len(temp_image.shape) == 2:
        noisy_image = temp_image + noise
    else:
        noisy_image[:,:,0] = temp_image[:,:,0] + noise
        noisy_image[:,:,1] = temp_image[:,:,1] + noise
        noisy_image[:,:,2] = temp_image[:,:,2] + noise

    return noisy_image

looks like it does not work for float32 but works correctly for uint8


foundry contracts remapping to contracts dir

Description
Update the remapping where the contracts live, keeping it similar to hardhat and it will also help us in frontend for blockexplorer for finding contract's metdata like bytecode in CLI
https://github.com/scaffold-eth/scaffold-eth-2/blob/ae2f4b654e105b5ec7eb603513d0d43c550dcf6c/packages/nextjs/pages/blockexplorer/address/[address].tsx#L182
References #394 , #406 (comment)

I have tested but just cc @jrcarlos2000 incase I missed something


Extra string tags to image_stamp_tag, update codeowners[OC-1439]

Optionally add a list of extra string tags to either the image_tag or image_stamp_tag output.
At least for my use case, I would like to use image_stamp_tag to tag not only the git version but add in a "latest-master" tag to the target image.
I could see value in extending the image_stamp_tag to apply the regex functionality to extra tags, but I'll leave that up to a future user.
As far as I understand, because I use a default value, this feature should be backwards compatible.

this looks fine. Hopefully you are correct about it being backwards compatible.

Fortunately any users have to manually uprev rules_swiftnav so I think it is safe


Query Page, Back button is not working while create new Query

Query Page, Back button is not working while create new Query

#390


Rhino error: Changing attributes not supported for Function prototype property

When I try to run compiled JS and Rhino (to run Autoprefixer into Java) it fall with:
Rhino::JSError:
       InternalError: Changing attributes not supported for Function prototype property
     # at <eval>:13904 (createClass)
     # at <eval>:14295
     # at <eval>:14279
     # at <eval>:13557

Line 13904 from this backtrace contains:
$defineProperty(ctor, 'prototype', {
  configurable: false,
  writable: false
});

Hi All
we are upgrading to jQuery version 3.2.1
We have Rihno version 1_7R3  and we are getting error  Object.defineProperty is not a function.
The reason may be Object.defineProperty is defined in JS 1.8 and rihno is in JS 1.7
can anyone of you help me to solve this ?


M2.2: Ensure the data browser can handle the expected number of concurrent requests from online users

@tburdett commented on Tue Dec 04 2018
┆Issue Number: HCAB-372

Superseded by databiosphere/azul#698.


e2e test - click on href="javascript:void(0)" actually takes the browser to that URL

JS urls should be evaluated instead and then to follow the link if any. Unable to test such URL. Fix need to be applied in angular-scenario.js, the method is named "chain.click" about line 25951.

The ngScenario module is deprecated and we are not accepting further code changes for it. Please look at using Protractor for your e2e testing.


Clean up UIWindow/UIView point/rect conversion - get rid of [UIWindow _convertPoint]

Many classes were calling [UIWindow convertPoint:(CGPoint) fromView:(UIView*) toView(UIView*)] to do point conversion, but this isn't a public API.  We moved it to UIWindowInternal.h and renamed it to _convertPoint, but we should get rid of it altogether.  The fact that there are 3 views used in the API makes it confusing.

These are closer to what UIView's APIs should look like, but are not yet validated:
/**
@Status Interoperable
*/

(CGRect)convertRect:(CGRect)rect toView:(UIView*)toView {
UIWindow* ourWindow = [self _getWindowInternal];
if (!ourWindow ) {
return rect;
}
if (!toView) {
toView = ourWindow;
}
CGPoint pt1 = rect.origin;
CGPoint pt2 = rect.origin;
pt2.x += rect.size.width;
pt2.y += rect.size.height;
pt1 = [ourWindow convertPoint:pt1 toView:toView];
pt2 = [ourWindow convertPoint:pt2 toView:toView];
CGRect ret;
ret.origin.x = pt1.x < pt2.x ? pt1.x : pt2.x;
ret.origin.y = pt1.y < pt2.y ? pt1.y : pt2.y;
ret.size.width = fabsf(pt1.x - pt2.x);
ret.size.height = fabsf(pt1.y - pt2.y);
return ret;
}

/**
@Status Interoperable
*/

(CGRect)convertRect:(CGRect)rect fromView:(UIView*)fromView {
UIWindow* ourWindow = [self _getWindowInternal];
if (!ourWindow) {
return rect;
}
if (!fromView) {
fromView = ourWindow;
}
CGPoint pt1 = rect.origin;
CGPoint pt2 = rect.origin;
pt2.x += rect.size.width;
pt2.y += rect.size.height;
pt1 = [ourWindow convertPoint:pt1 fromView:fromView];
pt2 = [ourWindow convertPoint:pt2 fromView:fromView];
CGRect ret;
ret.origin.x = pt1.x < pt2.x ? pt1.x : pt2.x;
ret.origin.y = pt1.y < pt2.y ? pt1.y : pt2.y;
ret.size.width = fabsf(pt1.x - pt2.x);
ret.size.height = fabsf(pt1.y - pt2.y);
return ret;
}

/**
@Status Interoperable
*/

(CGPoint)convertPoint:(CGPoint)point toView:(UIView*)toView {
UIWindow* ourWindow = [self _getWindowInternal];
if (!ourWindow) {
return point;
}
if (!toView) {
toView = ourWindow;
}
return [CALayer convertPoint:point fromLayer:[self layer] toLayer:[toView layer]];
}

/**
@Status Interoperable
*/

(CGPoint)convertPoint:(CGPoint)point fromView:(UIView*)fromView {
UIWindow* ourWindow = [self _getWindowInternal];
if (!ourWindow) {
return point;
}
if (!fromView) {
fromView = ourWindow;
}
return [CALayer convertPoint:point fromLayer:[fromView layer] toLayer:[self layer]];
}


Respect update serial in bosh manifest

Fixes #636
This introduces an initContainer waiting for another instance group to be reachable via service if the update: serial is set accordingly in the manifest.
This results in faster startup times since there are fewer crashes and CrashLoopBackOffs. Also the startup phase looks a bit smoother.
There are still some crashes left (e.g. one container of api crashes if the database is not migrated yet, this is done by another container)
There is a special handling of the eirini instance group inside manifest.go, because eirini is patched at the wrong position inside the manifest. We will prepare a PR for scf to fix this (https://github.com/SUSE/scf/pull/2980). Afterward, this special handling can be removed.
We tried to write an e2e test. But we had several problems to run e2e tests with multiple instance groups (#645 ).

There are still some crashes left (e.g. one container of api crashes if the database is not migrated yet, this is done by another container)

I suppose this will be handled in https://github.com/SUSE/scf/issues/2975

There are still some crashes left (e.g. one container of api crashes if the database is not migrated yet, this is done by another container)

I suppose this will be handled in SUSE/scf#2975

I think this is another issue, because this focuses on uaa (I assume).
We have at least 3 types of crashes left

One container of api crashes because another container did not migrate the database yet
cc-worker crashes because the database is not migrated yet. But cc-worker has no update: serial, so I wonder how this works in BOSH
Even WITH the database migrated api crashes, but "only" 2 times or so.

Hi Team,
EasyCLA check indicates all authors are covered by a signed CLA.

Current functionality does not update the initial failure comment (CLA Not Signed) when check passes subsequently.  This was done to reduce comments made to PRs, but we're working on a change to update the comment if one exists on the PR.
https://github.com/communitybridge/easycla/issues/269

@f0rmiga @manno Could you have a look? Any comments?

I reopened https://github.com/SUSE/scf/pull/2980 as https://github.com/SUSE/kubecf/pull/60

It would be great to get this merged for 3 reasons

It shortens the startup times - mainly because there are less CrashLoopBackOff
It brings some order to the startup removes some race conditions - see https://github.com/SUSE/kubecf/issues/3
The startup  looks  much smoother without many crashes that are "normal" because some pod is not ready yet.

Is there any downside?

@c0d1ngm0nk3y we haven't been able to review this yet, it will probably happen next week

@c0d1ngm0nk3y we haven't been able to review this yet, it will probably happen next week

It would be great to get some feedback on this to get this hopefully merged soon. The fewer CrashLoopBackOffs would be great to have imho.

Hi,
Would love to see that, but I'm focusing on #663 and would prefer that one first. However conflicts are minimal.
Could you squash the commits a little?
I'm going to ask around in our daily about the manifest name, I don't think we need LoadYAMLByName as we enforce the name to be the BDPL resource name.

The enforcement is done at a later point in time (I think after one serialise/deserialise cycle). For this PR, we need the correct name immediately.

We moved this PR upwards in the backlog: https://www.pivotaltracker.com/n/projects/2192232

cmd/cf-operator/cf-operator binary file is added in one of the commits. You will need to interactively rebase the commits and edit the commit that introduced it, otherwise, it will pollute master once we merge.

Good catch. I will have a look.

@viovanov,
simply reverting our change in LoadYAML will not work.
Our feature only works, if you don't change the corresponding unit tests!
The problem is that the service names will be wrong.

@viovanov,
simply reverting our change in LoadYAML will not work.
Our feature only works, if you don't change the corresponding unit tests!
The problem is that the service names will be wrong.

I think that's because existing test data didn't care about our 'convention'. Let me try to clean that up.

e60f266

I think that's because existing test data didn't care about our 'convention'.

@manno By 'convention' you mean that bdpl name == manifest name? At  least 3 weeks ago, this was not true for kubecf/scf. So the code constructed the wrong service names (e.g. cf-database instead of scf-database.
3 weeks ago, this was definitely  a bug imho. The manifest name was later changed, but too late depending on when you call it. If the 2 should be the same, why synch them at all?
@viovanov Maybe, kubecf or cf-operator changed in the meantime, so that this is no longer needed. But it was needed when we opened the  PR. Most pods waited for non existing services. So we  should test it with the latest kubecf.

@c0d1ngm0nk3y yes, I think I remember that - it was a bug in kubecf.
I think fixing the test is ok for this PR, we can merge, and afterwards we can properly fix this code in https://www.pivotaltracker.com/story/show/169575453
Sorry this took so long 😅

I tried to fix all the places, so this doesn't turn into a game of whack-a-mole...
https://github.com/cloudfoundry-incubator/cf-operator/commit/8d4635f7f8252b41805ea26ae60d187369cf79c1

I think I remember that - it was a bug in kubecf.

I think you are refering to a different bug. For kubecf it is normal that the manifest name (cf) is different from the name o the bdpl (kubecf), isn't it???
I had my doubts  that this still works after reverting this part and tested installing kubecf and nearly no  pod is getting ready because the pods are waiting for a service cf-xxx instead of kubecf-xxx.
So for kubecf, the "convention" that manifest name = bdpl name is still not true. But kubecf is the main reason for cf-operator, right?
Summary kubecf cannot be installed with the master of cf-operator after this modified PR.
@kramerul , @viovanov , @manno I would suggest we re-add the missing code on Monday to make it work again and figure then out how to continue.


API question about ForeignError

Currently ForeignError is quite limiting in what kinds of error a read operation can produce, that is, it covers type errors, but it only covers a parse error (say when parsing a String) IF it's parsing JSON.
In my case, I have a Type field which is parsed from a simple Haskell style string "Concrete -> Concrete". If the parse fails for any reason there isn't a ForeignError that covers this case, as it's not a type error but a syntax error. JSON gets special treatment in this case, but perhaps the JSONError should be generalized to cover other cases?
It seems like TypeMismatch isn't going to be useful in terms of implementing new Foreign instances because all the primitive types are already covered by the Foreign library.

Are you trying to use purescript-foreign to parse strings? That's really not what it's for, it's just for trying to turn untyped, untrusted data into typed data. Parsing would be better handled by a specific library, and it's not the sort of thing we'd add errors for here.

That's really not what it's for, it's just for trying to turn untyped, untrusted data into typed data.

That is parsing though, just as reading JSON is parsing. I'm using Text.Parsing.StringParser to parse the string. I'm saying, Foreign is a useful abstraction for importing data, but it's not particularly extensible at the moment.
newtype Part = Part
    { id :: String
    , name :: String
    , "type" :: Type
    , exec :: Foreign
    , autocomplete :: Maybe Foreign
    , args :: Array Part
    }

instance partIsForeign :: IsForeign Part where
    read fo = do
      n <- readProp "name" fo
      t <- readProp "type" fo
      e <- readProp "exec" fo
      auto <- runNullOrUndefined <$> readProp "autocomplete" fo
      pure $ Part {id:"", name:n, "type":t, exec:e, autocomplete:auto, args:[]}

instance typeIsForeign :: IsForeign Type where
  read fo = read fo >>= (\str ->
              unParser parseType {str, pos:0}
                (\pos err -> Left ... ) -- No sane way to return error
                (\typ _ -> Right typ))

Swapping out JSONError for ParseError would make it more useful. The alternative is not implementing Foreign for Type or Part, in which case I need to invent something else to contain that.

Actually this isn't that well suited to reading JSON either, I should update the readme to reflect that. For JSON you're better off using something like purescript-argonaut.

Actually this isn't that well suited to reading JSON either, I should update the readme to reflect that. For JSON you're better off using something like purescript-argonaut.

Why is that? It's at least not the case if you are dealing with foreign JS code, since Argonaut is designed to go from "native" (or Generic) data representation, to Argonaut JSON types, to a JSON string, which doesn't include a Foreign representation anywhere.

This library doesn't deal with any of the usual parsing concerns like backtracking or alternation.

https://github.com/libscott/purescript-foreign/blob/6afc9f049bda74ac0e0c6c0168020b13d9e9a349/src/Data/Foreign.purs#L48
> import ParseErrors
> main
Left (Error parsing JSON: SyntaxError: Unexpected token o)
Left (Type mismatch: expected Boolean, found Number)
Left (Error at array index 0: Type mismatch: expected Boolean, found Number)
Left (Error at property "y": Type mismatch: expected Number, found Boolean)

That's what I'm suggesting; personally I think it's an easy win from an API perspective, as the Foreign interface is a nice way to implement data exchange between Purescript and Javascript.


Improve docs for

Summary
Make it clear how to use the .toThrow method.
Test plan
Just docs.

Codecov Report

Merging #4478 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4478   +/-   ##
=======================================
  Coverage   56.84%   56.84%
=======================================
  Files         186      186
  Lines        6298     6298
  Branches        3        3
=======================================
  Hits         3580     3580
  Misses       2717     2717
  Partials        1        1

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 c4844a6...9c0d129. Read the comment docs.


importerror: no deafultdict

When i run imfer_simple.py, I meet this error in "utils/misc.py" in line
from collections import defaultdice,Iterable
so how to solve this problem?

Did you use python 2 or 3 ?
It seems that utils/collections.py shadow the collections package in python standard library.

@roytseng-tw  ,thank u ,yes, i use python 2 ,i find collections  in python standard library but in lib/utils/ also have a collections so what should i do?

It's recommend to use python3 for this code. However, add the line from __future__ import absolute_import to the top of lib/utils/collections.py can solve this particular issue, but you probably will encounter another issue afterwards. Hence, the recommended way is to setup a virtual environment for python3.


vscode 1.54.1 Terminal Ctrl+click on file link NOT navi to the line in Editor when project path include "space" char

VS Code Version: 1.54.1
OS Version: Win10 Enterprise

This is bug in 1.54.1, query from stackoverflow, can't  find a resolution.
When the terminal show syntax error, the ctrl+click on file link WON'T navi to the error line inside Editor when project path includes "space" char, it behaviors as two unexpected cases:
Steps to Reproduce:
3 test cases.
Test #1 project path without space char.   - OK

c:/Users/garyzhao/test_vscode/a.py
put a syntax error like prxxxint("hello")
The terminal works fine, and ctrl+click on the file link successfully navi to the error line in editor.
when mouse hover on the file, it tips with "open with editor" as expected.

Test #2 project path with space char        -NOK

c:/Users/garyzhao/AAA BBB/test_vscode/a.py
Run same code as above
The terminal ctrl+click NOT able to navi to the editor
When mouse hover on the file link, the "c:/Users/garyzhao/AAA BBB/test_vscode/a.py" is split as two links: "c:/Users/garyzhao/AAA" and "BBB/test_vscode/a.py", mouse hover has NO any tips,  ctrl+click jump to the top input dialogue show "no matching"

Test #3 project path put into One-Drive folder (with default space char)        -NOK

C:\Users\garyzhao\OneDrive - gary\test_vscode/a.py
Run same code as above
The terminal ctrl+click always open a new vscode window, this is NOT expected
When mouse hover on the file link, it tips with "open with new windows" always.

The workaround can be:

Not put the project in the default "OneDrive - xxx" folder
Not put the project in folder with "space" char
Put the project in a folder without "space" char.

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

/duplicate #97941


SetCreationTimeUtc blocked and throwing exception on locked stream in TryCreateDirectoryFileStream

NLog version: 5.2.6
Platform: .Net 4.8
Current NLog config (xml or C#, if relevant)
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      internalLogFile="C:\Logs\Nlog\interface.log.txt"
      autoReload="true">
  <variable name="logDirectory" value="C:\Logs\" />
  <variable name="archiveDirectory" value="${logDirectory}\Archives\Interface" />

  <targets async="true">
    <target name="fullrolling" xsi:type="File"
            layout="${longdate} - ${message}"
            fileName="${logDirectory}\log.txt"
            archiveFileName="${archiveDirectory}\{#}.log.txt"
            archiveEvery="Day" archiveNumbering="Date" archiveDateFormat="yyyyMMddHHmm" maxArchiveFiles="31"
            concurrentWrites="true" keepFileOpen="false" encoding="utf-8"
            header="${processname} - ${assembly-version}" />
  </targets>

  <rules>
    <logger name="*" writeTo="fullrolling" enabled="true" />
  </rules>
</nlog>

The new fixWindowsFileSystemTunneling behavior causes strange behaviour with our nlog configuration.
The problem seems to be cause in BaseFileAppender.cs in the new (in 5.2.6) method TryCreateDirectoryFileStream
var fileStream = TryCreateFileStream(allowFileSharedWriting, overrideBufferSize); line is called with allowFileSharedWriting set to false. this cause the finally clause to fail as the file is locked.
Theorizing on this it seems to cause issues when the file is archived on for example 23:59:59 all new log message (or at least a set of them every minute) are archived to a new file because the system thinks the creationdate is too old and should do a rollover (as it couldn't update it on the creation).
It seems .net core reimplementation is a little different and either doesn't have the locking issue and handles the internals differently as a similar project running in .net 8.0 didn't show this issue (yet) but the logging intensity is also a lot lower.

What is the current result?
Archiving is borked and every minute files are archived.

What is the expected result?
Archiving working as intended only archive one a day. No exception on the creation time update would probably solve the problem.

Did you checked the Internal log?
Yes, because of a locked filestream the SetCreationTimeUtc can not be executed.

2023-11-28 11:41:55.7015 Debug FileTarget(Name=interface_wrapped): Failed to update File.SetCreationTimeUtc for FileName: C:\Logs\log.txt Exception: System.IO.IOException: The process cannot access the file 'C:\Logs\log.txt' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
at System.IO.File.OpenFile(String path, FileAccess access, SafeFileHandle& handle)
at System.IO.File.SetCreationTimeUtc(String path, DateTime creationTimeUtc)
at NLog.Internal.FileAppenders.BaseFileAppender.TryCreateDirectoryFileStream(Boolean allowFileSharedWriting, Int32 overrideBufferSize)

Are there any workarounds? yes/no
Deleting the log file and manually recreating it seems to (sometimes?) fix the issue when I was messing with the configuration. As it sets a new creation time this seems a plausible reason. I.e. the exception is no longer happening.

Is there a version in which it did work?
5.2.5 and earlier

Thank you for reporting this bug. Can see the implementation of SetCreationTimeUtc expects to open FileStream like this:
FileStream fs = new FileStream(path, FileMode.Open, FileAccess.Write, FileShare.ReadWrite, 1);

Which doesn't work together with NLog opening file like this:
FileShare fileShare = allowFileSharedWriting ? FileShare.ReadWrite : FileShare.Read;

Will try and make an unit-test that reproduces the issues, and then make the bug-fix.

Thank you again for providing this very detailed bug-report.
NLog v5.2.7 has now been released - https://www.nuget.org/packages/NLog/5.2.7


System log: make firing event optional

Description:
Make firing events for new logged system events optional and opt-in. If users don't know about the component, they won't use it anyway. Since all events are stored in the database, we're probably filling DBs up with errors that people don't really care about.
Breaking change: System log no longer defaults to firing events. Update your config to re-enable this feature:
system_log:
  fire_event: true

Related issue (if applicable): fixes #13957
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
system_log:
  fire_event: true

Checklist:

[ ] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

CC @postlund

@ballob Looks good to me, but maybe we should have a test for this?

Done. Had to restructure the fixture the tests because it was hardcoded with a default config.


Page Not found Error for link to docs page

This page contains a link to the docs page in the first couple of lines; which I suspect might have been moved. If I'm right, this should be pointing to the docs here.

fixed


Device Plugin CR webhook error

Summary:
When creating a [Sgx/Qat/Gpu]DevicePlugin CR after the Intel Device Plugins operator is installed, a webhook error is observed. This error is observed via OpenShift web console as well as through CLI.
Error message:
Error "failed calling webhook "vsgxdeviceplugin.kb.io": failed to call webhook: Post "https://inteldeviceplugins-controller-manager-service.openshift-operators.svc:443/validate-deviceplugin-intel-com-v1-sgxdeviceplugin?timeout=10s": dial tcp <IP_ADDRESS>:9443: connect: connection refused" for field "undefined".
Analysis:
A webhook is called to validate [Sgx/Qat/Gpu]DevicePlugin CR yaml input parameters when user creates the DevicePlugin. Initial evidence suggests this issue is network or environment related.
Impact:
User is unable to consistently create [Sgx/Qat/Gpu]DevicePlugin CR on OpenShift cluster. User experience impacted. The error is not consistent, on the first try, the error may appear and then continue to appear for subsequent retries. If the user keeps clicking the "Create" button on web console, the DevicePlugin CR is eventually created without error.

Hi @mythi, any thoughts on this issue? Have you seen this before? Thanks in advance.

Initial evidence suggests this issue is network or environment related.

Can you think of what has changed since it worked? I know webhook errors can occur if https gets routed through a proxy but this looks different.

Is there a way to reproduce this? Something we have improved recently is that the operator now uses readiness probes, also for the webhooks. Could it be this error triggers if the webhook is not yet up properly?

It is reproducible. The operator bundle and container images are based on v0.26.0. Anything particular we can check to ensure webhook is setup and running properly? I can see in the logs that the webhook is registered successfully, started the webhook server and the health probe running. We are creating the DevicePlugin CR and noticing the webhook error after all this setup happens in the below log.
 Didn't find any errors in logs, as it restarts.
inteldeviceplugins-controller-manager-7d8b6cd565-fdm2g            2/2     Running     4 (11m ago)   78m

can you try increasing the pod cpu/mem resources if that helps?

This issue was not observed on another OpenShift cluster. Low priority and not a gating item.


DW1000Ranging_Tag/Anchor

Firstly, many thanks for the great work you have done in maing this technology more available. I am very grateful!
I am trying to implement the DW1000Ranging_Tag/Anchor example but cannot get it to work. I am driving the Anchor with an Arduino Uno and the tag with a TinyShield (AT328P).
Once the sketches are done uploading, I open the Serial Monitor for the Anchor and see:
device address: 82:17:.......
"### ANCHOR ####"
but nothing else. Is some further initiation required? I have checked wiring errors with no joy.
Your thoughts would be very welcome. Thank you.

Scratch that. It WAS a wiring issue and the code works perfectly, thank you once again for your work.

Could you please be more specific about the wiring issue, i am having similar problems.  Any help will be greatly appreciated.

Sure. I had incorrectly wired DWM1000 pin 22 (IRQ) to the arduino I/O pin 8. The schematic clearly shows that this should be connected to I/O pin 2 for the interrupt. I am not using the adapter board so had messed up my pin outs. I hope your issue is as easy to fix.

Has anyone else had this issue despite having the wiring correct? I and a friend double checked our wiring but we are still only getting
device address: 82:17:.......
ANCHOR
and no other data or ranges. We are also unable to get any of the basicSender and basicReceiver code to send and receive messages. We are using two Pro Mini's 3.3V and the breakout board.

I have the same setup, same problem.

It sounds like the modules are either not getting power, or are asleep. Check the following:

Does the module get warm after being powered for a few minutes? If not, it is not getting power.
Check your external interrupt (Arduino Pin 2 -> Adapter Board Pin 17 -> Module Pin 22).

It does not sound like an communication (SPI) issue as you should see more on your serial monitor.

I have double checked and I made sure that my modules are drawing power (about 125 mA a piece) and that the interrupt wires are connected correctly. Has anyone had trouble with the two modules not being able to communicate between one another? I know my SPI connection is working because the Basic Connectivity script is working.
Also, is anyone else having trouble with the serial prints sometimes getting corrupted?

Hi ! Can you check if the frameFiltering is desactivate ?
line 1093 of the DW1000.cpp. must be setFrameFilter(false); if you want to communicate without adding mac address in front of your message...
(But the DW1000Ranging.cpp do this for you)
regards

Hi. I had the problem @zach401 is commenting, in my case i am using arduino 1. I did not check if it was due to the maximum current that can be drawn. Actually, I am not sure if arduino 1 mini pro provides more current than arduino 1 (that sounds odd to me).
In the data sheet of arduino 1 you can read that the maximum current is 50 mA. https://www.arduino.cc/en/Main/ArduinoBoardUno
That can be a problem when powering the decawave chip. However, I also read that tha maximum current from the 3.3 V output is 150 mA, which should be enough:
http://electronics.stackexchange.com/questions/67092/how-much-current-can-i-draw-from-the-arduinos-pins
Can someone give a confirmation on this?
You can read about what we discussed here: https://github.com/thotro/arduino-dw1000/issues/6
When the problem happened, I plugged off and then on the arduino power. But still I didnt figure out where the problem is.
PS: I have to test it with the last version of the libraries.
Cheers!!

We just got our setup working. It must have been a wiring issue, because once we unplugged everything and reset it up, everything worked well. We also made the change that leosayous21 suggested, but it did not work until we rewired.
We are at a university, so we are powering the DWM1000 from a 3.3 V power supply instead of from the arduino's regulator. In our test each DWM1000 was drawing about 150 mA, which when combined with he current draw of the arduino itself might be too much for the onboard regulator (or at least near its limits). If you have access to another power supply or an external regulator that might help.

Ok, @zach401 . It seems then there may be issues with the 3.3 V output powering the DW1000. The conclusion is that it might be possible that the 3.3 V maximum current from some arduinos is not enough.
Cheers!

@MarioRuz  you didnt count for the current Arduino use,use external power supply

Hi! Please tell me what we do wrong?
We connect decawave dw1000 to arduino Uno by SPI connection, upload this sketch
DW1000Ranging_TAG
https://github.com/thotro/arduino-dw1000/blob/master/examples/DW1000Ranging_TAG/DW1000Ranging_TAG.ino
But when we open arduino monitor, we see nothing, as if Decawave receive nothing... And on the Decawave led "ERROR INIT FAIL".
What we miss, where our mistake? Help please. Thank u.


Usage without Docker?

I've never used Docker before and noticed that it basically downloads Ros again and creates its own workspace which is not desirable in my case.
I did manage to bypass it by generating the godot-cpp bindings manually and then successfully build the package with catkin.
I then imported it into Godot and tried to run it but got an error that libxmlrpc.so could not be found. How should my setup look like to get this working?

I did manage to bypass it by generating the godot-cpp bindings manually and then successfully build the package with catkin.

Please give me more detailed information to reproduce.

I have a standard catkin workspace with multiple ROS packages.
I cloned your godot_ros_pcviz package, and updated the git submodules.
Then i compiled the godot-cpp bindings library with the following command:
scons platform=linux bits=64 generate_bindings=yes
Next i had to remove tf2_sensor_msgs from CMakeLists.txt and package.xml since that package doesn't exist under ROS-Melodic.
After this i successfully build my workspace with catkin build. I then downloaded the newest Godot executable, ran it and imported the project.godot file.
When executing the project i get the following errors:
Can't open dynamic library: /home/user/catkin_ws/devel/lib/godot_ros_pcviz/libgodot_ros_pcviz.so. Error: libxmlrpcpp.so: cannot open shared object file: No such file or directory
No valid library handle, can't get symbol from GDNative object
No nativescript_init in "res://libgodot_ros_pcviz.so" found

Looks like im missing something here but looking at your entrypoint.sh i basically did the same thing just without a docker volume.

I fixed the problem by sourcing the workspace in a terminal first and then running Godot from it.


NameError when deploy on testnet :  private_key = get_private_key(private_key)

when deploy contract on testnet
I follow the step on readme,and on second step:
python -m raiden_contracts.deploy raiden --rpc-provider http://<IP_ADDRESS>:8545 --private-key /path/to/your/private_key/file --gas-price 10 --gas-limit 6000000
I've annotated the statements that depend on raiden-libs according the link .
https://github.com/raiden-network/raiden-contracts/issues/354
but  I get an error
File "/usr/local/lib/python3.6/dist-packages/raiden_contracts/deploy/main.py", line 179, in setup_ctx
private_key = get_private_key(private_key)
NameError: name 'get_private_key' is not defined .

I've noticed your code on github had been updated,but I use the command on your github readme.md
pip install raiden-contracts
I got outdated code .

I assume that you installed raiden contracts with pip install raiden-contracts. That would install only the non-dev requirements and currently raiden-libs is part of the dev requirements.
For now as a workaround for the issue do pip install -r requirements-dev.txt and you will also get raiden libs in your venv.

This was discussed in raiden's gitter channel and fixed by pip install -r requirements-dev.txt, as mentioned in the docs. I am closing this issue.
Another issue popped up though: https://github.com/raiden-network/raiden-contracts/issues/389


Integrate rich to make cli output pretty

The current default output from treelib isn't bad, but I think it could be more visually appealing.
Things I've thought about incorporating:

[x] Dimmed/greyed output for subvolumes that aren't reachable
[x] Bold output for subvolumes that are mount points
[ ] #5
[x] Better delineation between different filesystems
[x] Limiting long output
[ ] Maybe emojis or something because that's what the kids like

Right now I think the easiest way to accomplish much of this would be via the rich library. While the rich library does have support for trees, its support is more for visualizing them, not interacting with them, so treelib would still be a dependency. If I had to guess, rich would just act as a layer between the library and the cli, meaning most of it's code would live in btrview.py, or maybe I'll create a separate module for it as btrview.py is getting a bit crowded.

This is pretty much done. There are a few things that could still be improved upon, but the vision that I set forth when I created the issue is complete.


Identifier typo in ModelicaTest.MultiBody.Parts.Rotor1D.Beveal1d

Reported by beutlich on 12 Nov 2014 08:10 UTC
ModelicaTest.MultiBody.Parts.Rotor1D.Beveal1d should correctly be named Bevel1D.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1604

Is backwards-compatibility also an issue for ModelicaTest?

No (ModelicaTest needs not be backwards compatible)

Resolved by 1bb12fac7021fac8887223c2269b495dd4914939 in master.


New Icon

If anyone is interested in designing a new icon for vimari... as much as I am nostalgic about the current one, its not the most visually appealing.
Open to any ideas.

New icon added in https://github.com/guyht/vimari/commit/f7619c51efd0efe32462d86cb959cb8261c74311.


--no-sound-null-safety doesn't seem to work with package hosted within the app

I have a flutter app which is too big to migrate to null safety in one go, so I changed some libraries to packages, still located in the same repo under app /lib folder.
I can migrate a single package to null safety and run the tests within the package.
However, when I try to run the main app (which is NOT migrated to null safety), I get an error "Null safety features are disabled for this library.", even though I run with flutter run --no-sound-null-safety.
Not sure if this is related to the fact that package is referenced by path or not, but I just can't figure out what I am doing wrong.
A reproducible example is here. It was created on flutter stable and then the package was uopgraded to null safety on Flutter 1.25.0-8.2.pre • channel beta.

It seems that:

app sdk version must be set to >=2.12.0-0
//@dart = 2.7 must be added in main.dart

Need to check on my real app now

It seems that:

app sdk version must be set to >=2.12.0-0
//@dart = 2.7 must be added in main.dart

Need to check on my real app now

Ahh, I had to add //@dart = 2.10 to more or less every non-null-safe file - all libraries and all parts. I don't think I've seen that mentioned in the documentation?

Ahh, I had to add //@dart = 2.10 to more or less every non-null-safe file - all libraries and all parts. I don't think I've seen that mentioned in the documentation?


adding code_of_conduct.md

A Code of Conduct ensures inclusivity, prevents harassment, clarifies behavioral expectations, encourages professionalism, and fosters a safe, welcoming community for contributors.
plz assisn me this issue under gsoc-extended , level 1 , hacktoberfest-accepted tag

This issue is already opened.

I want to work on it. Can you please assign it to me?
And please add gssoc-ext label

@jyothimanoj12 @AnujSaha0111 Sorry, I am not the owner of this repo. This is a duplicate request. I have already requested the issue 3 days ago.


Check path len of extracted files on Windows

Windows has a max path length of 260 chars. Throw an
error if the path length is exceeded when a file is
extracted.
Resolves ENGT-7861.

LGTM


Remove Github and Wiki links from header

Remove Github and Wiki links on the header

@KarishmaBothara can you check and resolved the build failed

Closing this cause of https://github.com/futureversecom/trn-substrate-portal/pull/16


[ENH] Tidy up unequal length collection transformers

fixes #1156
We have three transformers to make unequal length series equal length. One pads, one truncates and one stretches. This PR renames then Truncator, Padder and Resizer, makes the files private and reworks the  associated notebook, which could ultimately be merged with the one on unequal length series.

Looks good, but needs deprecation. Pretty sure everything can stay as it is now just add the old classes and __init__ with a warning

I thought that collections was experimental? Conflicted with deprecation in any case, might just leave this until after the next release

Series is but collection is not. Have it listed in the README


Unit-test result upload

Hi!
Is there an easy way to upload unit-test results to test-results addon from gradle task the same way it is done in your Android unit test step?
I've read the custom script guide  but want to make sure I'm not missing an easier way to do it before heavy scripting.
My app has the following modules each with unit-tests:

domain (pure Java module)
data (Android module)
app (Android module)

I run all of them using a single gradle task that depend on individual tests.
The output is standard for junit in each module.
Unfortunately the step does not include same report collecting features as Android one.
Why Android step does not work for me?

It doesn't test pure-java module as there are no variants. It evaluates to Classes variant that runs my domain:testClasses task (which only compiles) rather then domain:test.
I'd like a single task for all of the tests to speed up things (in comparison with dedicated task per module).
I'd like to control tests to run combining gradle tasks inside project build.gradle rather than step config - it's more robust for me and makes possible for branch-to-branch different test scenarios

HI @motorro!
Unfortunately, there isn't an easier way to accomplish this. The Test Reports add-on is working with the default test steps only - otherwise, you can only make use of it via the guide you're referencing here, which indeed involves scripting.

Hi @bitce!
Thanks for your answer!
Are there any plans on "copy-pasting" the report-packing logic from Android tests here? That would be great as the report format and location is the same across all of the modules.

Sure thing!
I do not believe we have specific plans to do this as of now, but it would make perfect sense, feel free to create a feature request about this!

Thanks a lot!
Found the feature request already issued.


Add Keynotes and Speaker to the menu

Closes #73

What do you think if we present it like this @Mariatta  ? or you believe it should be on 'About' section?


SW-5742 Added organization name to application model and controller

#2220  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite

Merge activity

Jul 31, 8:02 PM EDT: @tommylau523 merged this pull request with Graphite.


Release/kedro airflow/0.5.1

Description
Release version 0.5.1 of kedro-airflow.
Checklist

[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[x] Updated the documentation to reflect the code changes
[x] Added a description of this change in the relevant RELEASE.md file
[ ] Added tests to cover my changes

@deepyaman let me know if you're happy for me to merge the changes from https://github.com/kedro-org/kedro-plugins/pull/51 for this release.


Brush scale

G2 Version:
v4.0.7

Platform:
MacOS, Firefox 76.0

Mini Showcase(like screenshots):

CodePen Link:
https://codepen.io/pen/?&editable=true=https%3A%2F%2Fplotly.com%2Fjavascript%2Fline-and-scatter%2F

Currently, G2 brushes "snap" to data. This causes issues for column charts. Ideally, a user should be able to change the scale independent of data contained inside the scale change. I've included an example from plotly.js that demonstrates how the interaction should occur.
Related may be that brush-y doesn't seem to work on Firefox.

Here is how it works on firefox using brush-x. I would like to only move x-axis scale, not snap to data. Additionally, no box is drawn when holding down mouse to select range

Sorry, due to problems in the program's architecture design, we are unable to effectively fix the issues. You can have a try with G2 v5.


Add AES GCM encrypt & decrypt services with start, process and finish steps

I removed AES ECB decryption by chunks, PR is ready to be merged


Use make's builtin RM variable

At least as far as removing individual files goes, this is the best pattern for removing. I can't say the same for removing directories, but I went ahead and changed those to $(RM) -r anyway.

No objection, but what's the advantage of this over rm?  What prompted the change?

No objection, but what's the advantage of this over rm? What prompted the change?

Good question. I saw https://github.com/neondatabase/neon/pull/9464 was merged today, which was caused by me. Then I remembered that make(1) has a builtin variable for this that I believe is specified by POSIX, so I thought it would be the best solution.


Fix the parsing of the timestamps

The timestamps of creation, access and modification were parsed
based on the raw output of the "/bin/stat" command.
This parsing was dependant of the text in the output, like the
"Access" word.
On non-English systems this parsing didn't work and the "touch" command
didn't show the timestamps.
The parameter "--printf='%w\n%x\n%y'" has been added to the "/bin/stat"
command so we only get the timestamps of creation, modification and
access. It simplifies the parsing rules and make the parsing
language-agnostic.

Hey @nalysius, thank you for the PR, nice work! I am merging this now, I think I have to add the ctime to the GET command output as well. And sorry for the late response. :raised_hands:

Hey, I've reverted this change for now because it seems that the ordering is not accurate. The order of stat --printf='%w\n%x\n%y' FILENAME seems to be 0 => Birth, 1 => Access, 2 => Modify.

Hey, sorry to learn this didn't work as expected.
I confirm the order is birth, access and modification. I made a mistake in the loop. I fix it and submit a new PR.


[Errno 99] error while attempting to bind on address：cannot assign requested address

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[ ] I already checked if it is not related to FastAPI but to Pydantic.
[ ] I already checked if it is not related to FastAPI but to Swagger UI.
[ ] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[ ] I commit to help with one of those options 👆

Example Code
from fastapi import FastAPI, File, UploadFile

# API for single wav file uploading
@app.post("/uploadfile/")
def create_upload_file(upload_file: UploadFile = File(...)):
    uuid = uid.uuid4()
    file_folder = f"files/{uuid}"
    file_location = f"files/{uuid}/{upload_file.filename}"
    if not os.path.exists(file_folder):
        os.makedirs(file_folder)
    with open(file_location, "wb+") as file_object:
        file_object.write(upload_file.file.read())

    logger.info("file {} saved!".format(upload_file.filename))
    return {"info": f"file '{upload_file.filename}' saved at '{file_folder}'",
            "uuid": uuid}

if __name__ == '__main__':
    uvicorn.run(app=app, host="<IP_ADDRESS>", port=8090)

Description
I tested my code at local and the api service runs good. For some reason I need to set the service in a docker for usage. So I created a docker image by Dockerfile. However when I run the docker I got the following error:
INFO:     Started server process [7]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
ERROR:    [Errno 99] error while attempting to bind on address ('<IP_ADDRESS>', 8090): cannot assign requested address
INFO:     Waiting for application shutdown.
INFO:     Application shutdown complete.
I checked the port and for sure it is not token by other process. The service could run on the same address while start in the local.
Operating System
Linux
Operating System Details
No response
FastAPI Version
0.75.1
Python Version
3.8.0
Additional Context
No response

I assume you solved your problem, thanks for coming back to close the issue!

Sorry for the long delay! 🙈  I wanted to personally address each issue and they piled up through time, but now I'm checking each one in order.


[Dialogflow] Reenable samples tests, they keep reaching quota.

Even after #936, quota is still being reached. I can't reproduce this in local. Will disable samples again until I hava enough time to properly look into it.

Include looking into the test on #933 which timesout.

Assigning to @telpirion so he can keep or reassign to the person responsible for Dialogflow samples.

Looks like limit is already increased up to 120.
I will re-enable tests and investigate them further.


Make a query to a sharepoint site in a multi-tenant scenario

Hi thank you for you work, I found some useful resources particularly on your mgwdev-m365-helpers repo.
So I wanted to use the sp-react application in a multitenant scenario.
Context :

The application in Azure is registered in the 1234xx tenant and configured in multitenant mode
The site collection in Sharepoint was created in public mode (so members of the organization can access the site)
Added in the site collection a user from another tenant

Scenario :

With any account from 1234xx tenant, I can authenticate myself and make requests to sharepoint within the sharepoint Rest API.
With a user from another tenant, I can authenticate myself but not make requests to SharePoint, I get this error:
{"error_description":"Exception of type 'Microsoft.IdentityModel.Tokens.AudienceUriValidationFailedException' was thrown."}

Have you any ideas, do you think it's possible ?

Hi Mate :)
Great to hear someone finds it useful.
When it comes to guests in such scenario, there is one thing You have to consider - even if Your app is registered as a multitenant, You have to know to which tenant You want to authenticate at runtime level, in other words - when navigating to /auth page, You have to already know to which tenant You want to authenticate to. If not - MS login page will always assume You want to authenticate to Your "main" tenant.
This of course presents a small problem - if You want to keep Your app functioning as multi tenant You have to figure out when user is using the app as a guest, and when as a internal user. I would suggest using link with ?tenantid=<tenant_id> when sharing the link to Your app, than if Your app detects tenant-id in query parameter - it uses it in auth endpoint, if not - go with common (or organizations).
If You are building an app for one customer (or You can handle that with subdomains) - there is no problem :)
Hope that helps :)


Unable to select local folders to backup.

When I go to select the backup folders, all I see is the below. Any ideas?
I have a folder /storage that I've mapped to the container folder /storage and have validated that this works by browsing to it via console.

How did you created the container?
Could you also provide the output of the following commands:

docker inspect [container name]
docker exec [container name] df -h
docker exec [container name] ls -l /

I created it using the following:
docker run -d
--name=cloudberry-backup
-p 5800:5800
-v /docker/containers/cloudberry-backup/config:/config:rw
-v /storage:/storage:ro
-e USER_ID=1000 -e GROUP_ID=1004
--restart=always
-e TZ="TZ=Europe/London"
--network=media
jlesage/cloudberry-backup
Outputs attached.
Thanks for helping. I have worked around it by adding a symlink into the config folder to my storage folder, but its a strange issue.
Mark.

From: Jocelyn Le Sage<EMAIL_ADDRESS>Sent: Friday, August 31, 2018 2:43:07 PM
To: jlesage/docker-cloudberry-backup
Cc: cloudymark; Author
Subject: Re: [jlesage/docker-cloudberry-backup] Unable to select local folders to backup. (#4)
How did you created the container?
Could you also provide the output of the following commands:

docker inspect [container name]
docker exec [container name] df -h
docker exec [container name] ls -l /

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/jlesage/docker-cloudberry-backup/issues/4#issuecomment-417668274, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AZsLI2Y_r0r32k4sHMQPJzQ9yDmS7zjzks5uWT1rgaJpZM4WVLsw.
root@media:/tmp# docker exec cloudberry-backup df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  29.4G     19.4G      8.5G  70% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                     2.9G         0      2.9G   0% /sys/fs/cgroup
/dev/sda2                29.4G     19.4G      8.5G  70% /config
mergerfsPool              4.5T   1012.3G      3.3T  23% /storage
/dev/sda2                29.4G     19.4G      8.5G  70% /etc/resolv.conf
/dev/sda2                29.4G     19.4G      8.5G  70% /etc/hostname
/dev/sda2                29.4G     19.4G      8.5G  70% /etc/hosts
shm                      64.0M         0     64.0M   0% /dev/shm
tmpfs                     2.9G         0      2.9G   0% /proc/acpi
tmpfs                    64.0M         0     64.0M   0% /proc/kcore
tmpfs                    64.0M         0     64.0M   0% /proc/keys
tmpfs                    64.0M         0     64.0M   0% /proc/timer_list
tmpfs                    64.0M         0     64.0M   0% /proc/sched_debug
tmpfs                     2.9G         0      2.9G   0% /proc/scsi
tmpfs                     2.9G         0      2.9G   0% /sys/firmware
[
{
"Id": "81bc0982e97d295a92dce6bb9553261949d49e2c69a1991888d1dca41ae61203",
"Created": "2018-08-31T13:45:28.211306719Z",
"Path": "/init",
"Args": [],
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 8055,
"ExitCode": 0,
"Error": "",
"StartedAt": "2018-08-31T13:45:29.252210847Z",
"FinishedAt": "0001-01-01T00:00:00Z"
},
"Image": "sha256:ac0439efdc1d3da475886f99ff9b38f97f9fc036f2754a2fdbecc44dc6d05673",
"ResolvConfPath": "/var/lib/docker/containers/81bc0982e97d295a92dce6bb9553261949d49e2c69a1991888d1dca41ae61203/resolv.conf",
"HostnamePath": "/var/lib/docker/containers/81bc0982e97d295a92dce6bb9553261949d49e2c69a1991888d1dca41ae61203/hostname",
"HostsPath": "/var/lib/docker/containers/81bc0982e97d295a92dce6bb9553261949d49e2c69a1991888d1dca41ae61203/hosts",
"LogPath": "/var/lib/docker/containers/81bc0982e97d295a92dce6bb9553261949d49e2c69a1991888d1dca41ae61203/81bc0982e97d295a92dce6bb9553261949d49e2c69a1991888d1dca41ae61203-json.log",
"Name": "/cloudberry-backup",
"RestartCount": 0,
"Driver": "overlay2",
"Platform": "linux",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "docker-default",
"ExecIDs": null,
"HostConfig": {
"Binds": [
"/docker/containers/cloudberry-backup/config:/config:rw",
"/storage:/storage:ro"
],
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"NetworkMode": "media",
"PortBindings": {
"5800/tcp": [
{
"HostIp": "",
"HostPort": "5800"
}
]
},
"RestartPolicy": {
"Name": "always",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": null,
"CapDrop": null,
"Dns": [],
"DnsOptions": [],
"DnsSearch": [],
"ExtraHosts": null,
"GroupAdd": null,
"IpcMode": "shareable",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 67108864,
"Runtime": "runc",
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": [],
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": [],
"DeviceCgroupRules": null,
"DiskQuota": 0,
"KernelMemory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": null,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0,
"MaskedPaths": [
"/proc/acpi",
"/proc/kcore",
"/proc/keys",
"/proc/latency_stats",
"/proc/timer_list",
"/proc/timer_stats",
"/proc/sched_debug",
"/proc/scsi",
"/sys/firmware"
],
"ReadonlyPaths": [
"/proc/asound",
"/proc/bus",
"/proc/fs",
"/proc/irq",
"/proc/sys",
"/proc/sysrq-trigger"
]
},
"GraphDriver": {
"Data": {
"LowerDir": "/var/lib/docker/overlay2/113ebf8662fd466d30e782c1e35bca45e54269cadcd2ffc6b62bcff64f35b711-init/diff:/var/lib/docker/overlay2/46502fa70c03bca4e751c7505731f882ac736f9b424baecd35a4917c5a3c74f4/diff:/var/lib/docker/overlay2/a557a382538554b68b89d46ded5f07ef52c52fd2f4daf096640bcc044ca81fc0/diff:/var/lib/docker/overlay2/f45b8956e97550dee63f27cd0f2b1ff9307feb7a0d26b948f55902d4e148fae2/diff:/var/lib/docker/overlay2/8f63d2a82017e973933fb92e8230a684d2a86655ab74ad18f16a5d60c3cab0de/diff:/var/lib/docker/overlay2/fb3addc6fe532db2e9b8dcaaea674ab536f29c6ebb2a3bfbabb7a0110016c229/diff:/var/lib/docker/overlay2/17de3fba4cba06aa9d0f5db17e8ce122e76b74aaedabf65425878345bef028f2/diff:/var/lib/docker/overlay2/f94a383fa6c6c1b811b5a6eee888484e560e9f57764e5c25579a6e855fa35824/diff:/var/lib/docker/overlay2/07fde89d8a66aec1dc6169156367c056ff3ec3ddbb9fa949f9a331bfa9805e48/diff:/var/lib/docker/overlay2/afe2411f8ea913aac77ad8fe81fbadd4a57cc429c45748ebccc5f492a408e434/diff:/var/lib/docker/overlay2/26bece2475b6447668411cc9520ea70375d96b8bca677975053432235cf1bcac/diff:/var/lib/docker/overlay2/78d7b3fbce7cee4858af2017bf30e846e204b052d60cd34dbcb9e8ea789e2a0c/diff:/var/lib/docker/overlay2/9033f6da810ba56125950f0973e9a88817e0968468229a96ff8633850c643497/diff:/var/lib/docker/overlay2/34462b672ee77383fad85af9928c8907c8b5484b5981578149fe7c4944343dd4/diff:/var/lib/docker/overlay2/15e6f8490a6596a522547e52a781ac3862297f9e86a21c2dcd52aa32f797a974/diff:/var/lib/docker/overlay2/6f1ecd1d0fc2592869e8748b7e7fea609ec0bc712df2736506d5575249cacd16/diff:/var/lib/docker/overlay2/89304b8b1108b9818219e692f9c1f0952da3a16a7256c53f70d846ecef55c7f4/diff:/var/lib/docker/overlay2/eb549e58738d864c9a4a53d588248e63dcd5825b37f968696dcb29946e18bef3/diff:/var/lib/docker/overlay2/ac6ce7721ab2e902fb75379afa61759839bc71cad01be462493dd67d7d9672b1/diff:/var/lib/docker/overlay2/4cc63c03b1276c79ac58a7ea6bad6e780e78172777e15498e10c05c72f3e66da/diff:/var/lib/docker/overlay2/f75dfe3e4a62ac3686dc49cd57f4482ba0bfb536ded69cefc8ffed2367060cce/diff",
"MergedDir": "/var/lib/docker/overlay2/113ebf8662fd466d30e782c1e35bca45e54269cadcd2ffc6b62bcff64f35b711/merged",
"UpperDir": "/var/lib/docker/overlay2/113ebf8662fd466d30e782c1e35bca45e54269cadcd2ffc6b62bcff64f35b711/diff",
"WorkDir": "/var/lib/docker/overlay2/113ebf8662fd466d30e782c1e35bca45e54269cadcd2ffc6b62bcff64f35b711/work"
},
"Name": "overlay2"
},
"Mounts": [
{
"Type": "bind",
"Source": "/docker/containers/cloudberry-backup/config",
"Destination": "/config",
"Mode": "rw",
"RW": true,
"Propagation": "rprivate"
},
{
"Type": "bind",
"Source": "/storage",
"Destination": "/storage",
"Mode": "ro",
"RW": false,
"Propagation": "rprivate"
}
],
"Config": {
"Hostname": "81bc0982e97d",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"43210/tcp": {},
"43211/tcp": {},
"5800/tcp": {},
"5900/tcp": {}
},
"Tty": false,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"USER_ID=1000",
"GROUP_ID=1004",
"TZ=TZ=Europe/London",
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"LANG=en_US.UTF-8",
"S6_BEHAVIOUR_IF_STAGE2_FAILS=3",
"S6_SERVICE_DEPS=1",
"APP_NAME=CloudBerry Backup",
"APP_USER=app",
"XDG_DATA_HOME=/config/xdg/data",
"XDG_CONFIG_HOME=/config/xdg/config",
"XDG_CACHE_HOME=/config/xdg/cache",
"XDG_RUNTIME_DIR=/tmp/run/user/app",
"DISPLAY=:0",
"DISPLAY_WIDTH=1280",
"DISPLAY_HEIGHT=768",
"CBB_WEB_INTERFACE_USER=",
"CBB_WEB_INTERFACE_PASSWORD="
],
"Cmd": [
"/init"
],
"ArgsEscaped": true,
"Image": "jlesage/cloudberry-backup",
"Volumes": {
"/config": {},
"/storage": {}
},
"WorkingDir": "/tmp",
"Entrypoint": null,
"OnBuild": null,
"Labels": {
"org.label-schema.description": "Docker container for CloudBerry Backup",
"org.label-schema.name": "cloudberry-backup",
"org.label-schema.schema-version": "1.0",
"org.label-schema.vcs-url": "https://github.com/jlesage/docker-cloudberry-backup",
"org.label-schema.version": "0.1.0"
}
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "5998daa5d76bd9636419f14d19caa14f6404a4ca129257c140aa252a0645b545",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"43210/tcp": null,
"43211/tcp": null,
"5800/tcp": [
{
"HostIp": "<IP_ADDRESS>",
"HostPort": "5800"
}
],
"5900/tcp": null
},
"SandboxKey": "/var/run/docker/netns/5998daa5d76b",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "",
"Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "",
"IPPrefixLen": 0,
"IPv6Gateway": "",
"MacAddress": "",
"Networks": {
"media": {
"IPAMConfig": null,
"Links": null,
"Aliases": [
"81bc0982e97d"
],
"NetworkID": "e2a3efb09ed4b7f81668e3a2d37cb4af5d542cadddfdb79d43f6148d615c019a",
"EndpointID": "084dcb54bb5041fcab93db3e40bc2870a72d367565262fcabb63bcf5e761c009",
"Gateway": "<IP_ADDRESS>",
"IPAddress": "<IP_ADDRESS>",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:14:00:07",
"DriverOpts": null
}
}
}
}
]
root@media:/tmp# docker exec cloudberry-backup ls -l
total 12
drwxr-xr-x    2 root     root          4096 Aug 31 13:45 CloudBerry Backup
drwxr-xr-x    7 root     root          4096 Aug 31 13:45 nginx
drwxr-xr-x    3 root     root          4096 Aug 31 13:45 run

Apologies.
df.txt
inspect.txt
ls.txt

My guess is that the software doesn't display the folder because of its filesystem:
mergerfsPool              4.5T   1012.3G      3.3T  23% /storage

I will try to contact CloudBerry team to see if this can be fixed.

Well that was my assumption, but when I added a link in the config folder to storage, i am able to browse to it fine and then select it for backup.
Also, why do I not see the local files system within the docker image? Or is that by design?

Well that was my assumption, but when I added a link in the config folder to storage, i am able to browse to it fine and then select it for backup.

Yes so it's in fact just a UI bug.  The /storage folder is not shown even if it exists and accessible.

Also, why do I not see the local files system within the docker image? Or is that by design?

What do you mean exactly be the "local files system" ?

The file system in the docker image itself. It doesn't even show those folders.  It just targets the config folder and some other random files.

Any update on this issue? I have the same problem. My /storage docker volume is mapped to a ZFS pool on the host. When I start this docker image, I can see /storage and browse it and see all my files within the ZFS pool. However when trying to setup a backup, this storage folder does not exist in the UI. Even if I place a symbolic link in the config folder to /storage, it still doesn't show up. Any ideas?

Unfortunately I didn't get answers yet from CloudBerry about this issue.  I pinged them again yesterday.
To document unsupported filesystems, can you post the output of docker exec [container name] df -h?

Having the same issue as well all of a sudden. The GUI was still working two weeks ago, then after a reboot of the host I'm not seeing the paths anymore. However, since the configuration is still in tact, I can still perform backups using the same backup plan. Unable to make any changes to it though.

Looks like an issue where the mounts on the host were not ready at the time the container was started.  Did you try to restart the container again to see if you still get the issue ?

Looks like an issue where the mounts on the host were not ready at the time the container was started. Did you try to restart the container again to see if you still get the issue ?

I have tried restarting and still get the issue.


Timesheet - 18/06/2021 - James Pang

Task 1
Review PRs, create issues
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1875#pullrequestreview-687393027
https://github.com/thenewboston-developers/Website/issues/1877
https://github.com/thenewboston-developers/Website/issues/1878

Time Spent
1 hours

Task 2
Researched, worked on ways to have a blurred placeholder image like medium posts
Proof of Work

https://github.com/thenewboston-developers/Website/pull/1879

Time Spent
3.5 hours

Total hours: 4.5
Account Number
3443227b5f81d2e2e595c52fe0fafce0870c4c4d837a550ef084d44cb95aa4be

Total hours should be 4.5hrs @jamessspanggg ?

Total hours should be 4.5hrs @jamessspanggg ?

Whoops, edited


[bug] FileDialogBuilder.set_directory doesn't set the initial directory of the dialog

Describe the bug
Calling .set_directory on the blocking version of the FileDialogBuilder doesn't set the initial directory of the dialog
Reproduction
In this case, default_mount_directory is set to C:/Riot Games/League of Legends/Game/DATA/FINAL
When the dialog opens, the initial directory is set to the one from which I opened another file/directory previously using a different dialog.
#[tauri::command]
pub async fn mount_wads(
    mounted_wads: tauri::State<'_, MountedWadsState>,
    wad_hashtable: tauri::State<'_, WadHashtableState>,
    settings: tauri::State<'_, SettingsState>,
) -> Result<MountWadResponse, ApiError> {
    let mut mounted_wads_guard = mounted_wads.0.lock();

    let mut dialog =
        dialog::blocking::FileDialogBuilder::new().add_filter(".wad files", &["wad.client"]);

    if let Some(default_mount_directory) = &settings.0.read().default_mount_directory {
        dialog = dialog.set_directory(Path::new(default_mount_directory));
    }

    if let Some(wad_paths) = dialog.pick_files() {
       // rest of the code...
    }

    Err(ApiError::from_message("Failed to pick file"))
}

Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 120.0.2210.91
    ✔ MSVC:
        - Visual Studio Build Tools 2019
        - Visual Studio Community 2022
    ✔ rustc: 1.77.0-nightly (fb5ed726f 2023-12-28)
    ✔ Cargo: 1.77.0-nightly (ac6bbb332 2023-12-26)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (default)
    - node: 16.11.0
    - pnpm: 8.7.6
    - yarn: 1.22.15
    - npm: 8.0.0

[-] Packages
    - tauri [RUST]: 1.5.4
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.6
    - tao [RUST]: 0.16.5
    - cargo-tauri [RUST]: 1.0.0-beta.7
    - @tauri-apps/api [NPM]: 1.5.0 (outdated, latest: 1.5.3)
    - @tauri-apps/cli [NPM]: 1.5.0 (outdated, latest: 1.5.9)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
No response
Additional context
No response

This works fine on my end using your snippet, can you please share a minimal repro?


Refactor summary hidden span text change

What is the context of this PR?
This PR changes and reverts some of the changes made in #2679.
This is because looking at the issue it addressed it didn't actually make the changes needed. The issue didn't call for getting rid of the ariaLabel param so I have reintroduced that and renamed it. Also there was some hardcoding of content that we want to avoid to make it as customisable as possible for the user and give them the option to translate the text into other languages.
Ive also added a aria-hidden span around the link text in order to make the text set in the visuallyHiddenText param to make more sense and allow the user to set exactly what will be read out by screen readers but also not repeat the link text.
THIS IS STILL A BREAKING CHANGE
Services upgrading that use ariaLabel will now need to rename that param to visuallyHiddenText.
How to review
Test with voiceover and that the correct text is read out in the correct context

 Update DS to v65


fix: use cds.root as location for package.json

process.cwd() is dependent on the location of the process, while cds.root always points to the project root.
Most often and by default cds.root points to process.cwd() but in the context of cds.test the depending on the directory of the process, the wrong package.json might be read.

Thanks for the fix. What I don't understand, how this causes a regression in your tests. Because this just enables the plugin, and that option was not existing before. So I cannot imagine what did break...

PRs based on a fork from different repo/org will not pass integration-tests, as secrets are not injected:
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/

Fixed with https://github.com/cap-js-community/odata-v2-adapter/commit/67dc513c2e762267d26321104e361de58af4d4cf

@johannes-vogel next time just open PR based on cap-js-community, then it can be directly merged...

@johannes-vogel next time just open PR based on cap-js-community, then it can be directly merged...

will do so next time. Richard only recently added me to the community org.
The issue popped up in our (maybe not ideally written) tests and cwd was != cds.root and cwd did not contain a package.json which resulted in a crash.

OK, I See, I will make that more robust as well.