Unable to create service instance - Google postgressql

Hi - I am using beta version of cloud service broker, and am getting the following error when I try to create the service instacne of the service broker.
Tile version: beta -> https://network.pivotal.io/products/cloud-service-broker-gcp/
Since I could not find the correct documentation, I tried with the documentation reference of gcp broker as it is similar in implementation.
Command used for create service:
cf create-service csb-google-postgres small debug11-postgressql -c '{"role":"cloudsql.editor"}'
Result: create failed.
cf service
Showing info of service debug11-postgressql in org pvt-internal / space sandbox as admin...
name:             debug11-postgressql
service:          csb-google-postgres
tags:
plan:             small
description:      PostgreSQL is a fully managed service for the Google Cloud Platform.
documentation:    https://cloud.google.com/sql/docs/postgres
dashboard:
service broker:   cloud-service-broker-gcp
Showing status of last operation from service debug11-postgressql...
status:    create failed
message:   Error: Error, failed to create instance csb-postgres-21c5e67d-78e2-4786-8301-f77667155fcb: googleapi: Error 400: Invalid request: At least one of Public IP or Private
IP connectivity must be enabled.., invalid  on brokertemplate/definition.tf line 69, in resource "google_sql_database_instance" "instance":  69: resource
"google_sql_database_instance" "instance" { exit status 1
started:   2021-03-18T20:36:29Z
updated:   2021-03-18T20:37:33Z
There are no bound apps for this service.
Upgrades are not supported by this broker.
Please reply back on this.

Hi @deiveehan, there was also a fix to the tile to accept authorized_network_id instead of name. If you have shared vpc networks then the last version of the tile (released last week) should fix your issues.


Fix the footer link to TSConfig Options page

Fixed the TSConfig Options link in the footer [Popular documentation pages section].
Issue #1291
as suggested by @orta

Hey cool, congrats - this is perfect 👍🏻 💯


Migrate to jupyterlab 3

See https://jupyterlab.readthedocs.io/en/stable/extension/extension_migration.html#jupyterlab-2-x-to-3-x

Additional resources:

https://jupyterlab.readthedocs.io/en/latest/extension/extension_migration.html

https://jupyterlab.readthedocs.io/en/stable/extension/extension_dev.html

https://github.com/jupyterlab/extension-examples

https://github.com/jupyterlab/extension-cookiecutter-ts


add badges in readme

also test our first PR travis build

I'm going to merge this. The travis is failing due to the e2etests not quite passing with our dummy data. I'll be working on this..
Also, we probably shouldn't have python 2.6 as a test target as we've made incompatible changes for 2.7 (dict/set comprehensions, etc)


feat: add github action for publishing to JSR

need to be able to use a github action to publish

Documentation is here


IA32_APIC_BASE misemulated

Currently you folks seem to emulate it with
        case IA32_APIC_BASE: {
            *val = default_mem_addr;
            break;
        }

This does not deal with the bitflags in the low 12 bits of the register.  In particular, there's the BSP flag (bit 8), which should read 1 on the bootstrap CPU

You're right. The IA32_APIC_BASE MSR is described in detail in the IA SDM Vol. 3A section 10.4.4 Local APIC Status and Location. There are multiple issues with HAXM's virtualization of this MSR, but we can fix the initial BSP flag first.
Please feel free to contribute a patch if you want to see this fixed soon :) We are a small team and don't have the bandwidth to get every issue closed as quickly as people would like to see...


Can't change water tiles

When I try to change a water tile it says it can't find the path

Ill second that!
On Sat, Dec 29, 2018 at 7:48 PM Rob<EMAIL_ADDRESS>wrote:

When I try to change a water tile it says it can't find the path
[image: image]
https://user-images.githubusercontent.com/3431318/50543602-d061f900-0c41-11e9-92ad-2c6fb1f2f202.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GrapeshotGames/ServerGridEditor/issues/24, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Ah5OQ1XTkXqrNyyOf3xkZmr54GjjQu3Tks5u-BthgaJpZM4ZkxwA
.

I'll see what I can do!

Fixed the water tile picker and put in a pull request, if you can't wait that long see my fork on my github. https://github.com/wartech0/ServerGridEditor.git

@wartech0 I think the other paths do it to, like foreground etc, but  I'm not sure what they are for anyway

Should be working on the latest now :)


[CI] Add standlone workflow

In this PR, the standalone workflow is added.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@L-jasmine Thanks for the review!


error: 'memref.alloca' op expected no stack allocations with dynamic shapes

Describe the bug
core-input.mlir:18:12: error: 'memref.alloca' op expected no stack allocations with dynamic shapes
    %6:2 = linalg.generic {indexing_maps = [#map0, #map1, #map1], iterator_types = ["parallel", "parallel", "reduction"]} ins(%arg0 : tensor<?x?x?xf32>) outs(%5, %3 : tensor<?x?x1xf32>, tensor<?x?x1xi64>) {
           ^

Full error log: https://gist.github.com/f499dc448652054f9eae68f8dfbc1489
To Reproduce
iree-compile --iree-hal-target-backends=dylib repro.mlir

#map0 = affine_map<(d0, d1, d2) -> (d0, d1, d2)>
#map1 = affine_map<(d0, d1, d2) -> (d0, d1, 0)>
module attributes {torch.debug_module_name = "SoftmaxIntModule"} {
  func @forward(%arg0: tensor<?x?x?xf32>) -> tensor<?x?x?xf32> {
    %c0 = arith.constant 0 : index
    %c1 = arith.constant 1 : index
    %c2 = arith.constant 2 : index
    %cst = arith.constant 0.000000e+00 : f32
    %cst_0 = arith.constant 1.000000e+00 : f64
    %cst_1 = arith.constant -3.40282347E+38 : f32
    %c0_i64 = arith.constant 0 : i64
    %0 = tensor.dim %arg0, %c0 : tensor<?x?x?xf32>
    %1 = tensor.dim %arg0, %c1 : tensor<?x?x?xf32>
    %2 = linalg.init_tensor [%0, %1, 1] : tensor<?x?x1xi64>
    %3 = linalg.fill ins(%c0_i64 : i64) outs(%2 : tensor<?x?x1xi64>) -> tensor<?x?x1xi64>
    %4 = linalg.init_tensor [%0, %1, 1] : tensor<?x?x1xf32>
    %5 = linalg.fill ins(%cst_1 : f32) outs(%4 : tensor<?x?x1xf32>) -> tensor<?x?x1xf32>
    %6:2 = linalg.generic {indexing_maps = [#map0, #map1, #map1], iterator_types = ["parallel", "parallel", "reduction"]} ins(%arg0 : tensor<?x?x?xf32>) outs(%5, %3 : tensor<?x?x1xf32>, tensor<?x?x1xi64>) {
    ^bb0(%arg1: f32, %arg2: f32, %arg3: i64):
      %16 = linalg.index 2 : index
      %17 = arith.index_cast %16 : index to i64
      %18 = arith.cmpf ogt, %arg1, %arg2 : f32
      %19 = arith.select %18, %arg1, %arg2 : f32
      %20 = arith.select %18, %17, %arg3 : i64
      linalg.yield %19, %20 : f32, i64
    } -> (tensor<?x?x1xf32>, tensor<?x?x1xi64>)
    %7 = tensor.dim %arg0, %c2 : tensor<?x?x?xf32>
    %8 = arith.cmpi eq, %0, %0 : index
    cf.assert %8, "mismatched size for broadcast"
    %9 = arith.cmpi eq, %1, %1 : index
    cf.assert %9, "mismatched size for broadcast"
    %10 = linalg.init_tensor [%0, %1, %7] : tensor<?x?x?xf32>
    %11 = linalg.generic {indexing_maps = [#map0, #map1, #map0], iterator_types = ["parallel", "parallel", "parallel"]} ins(%arg0, %6#0 : tensor<?x?x?xf32>, tensor<?x?x1xf32>) outs(%10 : tensor<?x?x?xf32>) {
    ^bb0(%arg1: f32, %arg2: f32, %arg3: f32):
      %16 = arith.truncf %cst_0 : f64 to f32
      %17 = arith.mulf %arg2, %16 : f32
      %18 = arith.subf %arg1, %17 : f32
      linalg.yield %18 : f32
    } -> tensor<?x?x?xf32>
    %12 = linalg.generic {indexing_maps = [#map0, #map0], iterator_types = ["parallel", "parallel", "parallel"]} ins(%11 : tensor<?x?x?xf32>) outs(%10 : tensor<?x?x?xf32>) {
    ^bb0(%arg1: f32, %arg2: f32):
      %16 = math.exp %arg1 : f32
      linalg.yield %16 : f32
    } -> tensor<?x?x?xf32>
    %13 = linalg.fill ins(%cst : f32) outs(%4 : tensor<?x?x1xf32>) -> tensor<?x?x1xf32>
    %14 = linalg.generic {indexing_maps = [#map0, #map1], iterator_types = ["parallel", "parallel", "reduction"]} ins(%12 : tensor<?x?x?xf32>) outs(%13 : tensor<?x?x1xf32>) {
    ^bb0(%arg1: f32, %arg2: f32):
      %16 = arith.addf %arg1, %arg2 : f32
      linalg.yield %16 : f32
    } -> tensor<?x?x1xf32>
    cf.assert %8, "mismatched size for broadcast"
    cf.assert %9, "mismatched size for broadcast"
    %15 = linalg.generic {indexing_maps = [#map0, #map1, #map0], iterator_types = ["parallel", "parallel", "parallel"]} ins(%12, %14 : tensor<?x?x?xf32>, tensor<?x?x1xf32>) outs(%10 : tensor<?x?x?xf32>) {
    ^bb0(%arg1: f32, %arg2: f32, %arg3: f32):
      %16 = arith.divf %arg1, %arg2 : f32
      linalg.yield %16 : f32
    } -> tensor<?x?x?xf32>
    return %15 : tensor<?x?x?xf32>
  }
}

Ugh, more stack allocations.

Agreed. We have a reasonable body of such tests from xla, because it has been there for a while.
My only thought in doing this is that such tests are not guaranteed ir stable and may need manual fixups. We should document how to regenerate them, as in some extreme events, it may not be feasible to manually fix up.

hmm, I enabled the check this week. We accept small stack allocation, but not unknown size stack allocation. I'll take a look at this case. In the meantime, you can compile with -iree-codegen-check-ir-before-llvm-conversion=false flag if you want to test correctness. This is the flag to bypass the check.

This is the same issue about https://github.com/google/iree/issues/8592
We address the issue for ARM codegen for static shapes, which reduce the stack allocation to 16 KB. I have an improved PR to infer the upper bound of dynamic sizes.


{Linked:Bug2509196}[Adaptive Card-Schema Explorer- Input.Date]: Text Spacing is not getting applied for the content in calendar pop-up.[Rendering] Bug Title Here

Target Platforms
Other
SDK Version
1.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
OS Build: Windows 11 Version Dev(OS Build 22523.1000)
Browser: Edge Dev Version 98.0.1108.13 (Official build) dev (64-bit)
URL: Schema Explorer | Adaptive Cards
Tool: Stylus
Repro Steps:
Open the above URL.
Schema Explore Input.Date Page will be appear.
Turn on the Stylus tool.
Navigate to Date Input field in Adaptive Card and activate it.
Calendar Pop-up will be appear.
Verify that text Spacing is getting applied for the content in calendar pop-up or not.
Actual:
Text Spacing is not getting applied for the content in calendar pop-up.
Expected:
Text Spacing should get applied for the content in calendar pop-up.
User Impact:
Users with dyslexia and low vision who need to increase space between text to make a better experience will be impacted if text get hidden after applying such techniques.
MAS Reference:
MAS 1.4.12 - Text Spacing
“Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “
Screenshots

Card JSON
NA

Sample Code Language
No response
Sample Code
No response

Hi @anna-dingler
could you please provide us update regarding bug fixing as issue is still repro.

Hi @anna-dingler
any update on this bug as this issue is still repro'ing at our end?

Hi @vagpt,
No, we do not have an update on this bug.


NIFI-9470 Allow creation of Parameter Context without any Inherited Parameter Contexts

Summary
NIFI-9470 allow creation of Parameter Context without any Inherited Parameter Contexts - addition of Parameter Context nesting in 1.15 broke the ability for NiFi Toolkit to create-param (also affects 3rd Party clients such as NiPyApi with https://github.com/Chaffelson/nipyapi/issues/305).
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[x] Apache NiFi Jira issue created

Pull Request Tracking

[x] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[x] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[x] Pull Request based on current revision of the main branch
[x] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[x] Build completed using mvn clean install -P contrib-check

[x] JDK 8
[x] JDK 11
[x] JDK 17

Licensing

~[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy~
~[ ] New dependencies are documented in applicable LICENSE and NOTICE files~

Documentation

~[ ] Documentation formatting appears as expected in rendered files~

@ChrisSamo632 if you're gonna set about fixing bad stuff all quietly at least wave your arms or something.  This is an important fix and the only reason I noticed it was DanC came asking whether we were going to include...Had no idea!   Anyway thanks again!


Bump hac-dev, chrome service, chrome frontend tags

Mainly to get https://github.com/openshift/hac-dev/pull/926 in, but bumping the others as well.

/ok-to-test

Thanks @hugares, since I don't have the permissions, you may have to force push like last time https://github.com/redhat-appstudio/infra-deployments/pull/3632

Thanks @hugares, since I don't have the permissions, you may have to force push like last time #3632

Sure, I can do that. There is an issue with kustomize build of prod overlay:
Error: invalid Kustomization: json: cannot unmarshal number into Go struct field Image.images.newTag of type string

Yeah looks we we got the tag as all numbers https://quay.io/repository/cloudservices/chrome-service?tab=tags

when you're force pushing, can you use the tag before this one, thats alpha-numberic so should be good

when you're force pushing, can you use the tag before this one, thats alpha-numberic so should be good

Can you comment in the file with the exact tags I should use, so I put the right ones

updated PR, pushed the new tag

Thanks @hugares, since I don't have the permissions, you may have to force push like last time

Looks like this will not be needed. Since I put the /ok-to-test and you pushed again, the check that used to block things is not there

/retest

looks like appstudio-e2e-tests failure is not a flake. any ideas @hugares

/hold
Since @sahil143 had mentioned that there are other big changes that were merged this week, which are still yet to be tested on staging.

/unhold
Since testing has finished


Training with custom data

Hi, thanks for the awesome work. Is there a way to generate training data from existing 3D meshes? Thank you.

Hi,
Thanks for your interest. We have provided the detailed instructions to train CAP with your own data as described in 'Use Your Own Data' of README.  To start from meshes, you can easily sample a point cloud from a mesh using Trimesh, and then put the point cloud to the data folder to training CAP.
Best,

Hi @junshengzhou thank you for the info. Appreciate it.


fix PR template

Changes
Delete extra space between three backticks ``` and release-note tag. This is causing all new PRs with a bright red label do-not-merge/release-note-label-needed. The PR author has to go and fix it in the PR description. This fix is not easy to spot for any new contributor.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[ ] Has Docs included if any changes are user facing
[ ] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[ ] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/kind misc

/test pull-tekton-pipeline-build-tests

/hold
This all stems from @vdemeester's change in #4929, and #5105 is also trying to make a similar change to this PR. I think some discussion is needed - I'd like to hold off on merging this or #5105 until we've had a discussion in the Pipeline WG.

It's becoming very difficult to review pipeline PRs, most of the new PRs created with various red labels.
I am with you and @vdemeester on mandating PR authors to update release-note but not with such syntax error. I am sure @dibyom on the same page with his PR to fix the same syntax 🤣
It's not just confusing to the new contributors - https://github.com/tektoncd/pipeline/pull/5260#issuecomment-1203273037 🙃
We have pipeline WG in two weeks on 08/23, I have added this to the agenda for further discussion.
An alternate could be to not include release note section at all but include instructions on how to add it and if not added, specify consequences. All this does not have to be part of PR template but somewhere if it can be documented and add a reference to the PR template.

Thanks @pritidesai - yeah my motivation was the same. I find the extra space confusing. Open to any ideas to improve this - removing the space just seemed easiest 😆

An https://github.com/tektoncd/pipeline/pull/5105#issuecomment-1191208011 could be to not include release note section at all but include instructions on how to add it and if not added, specify consequences. All this does not have to be part of PR template but somewhere if it can be documented and add a reference in the PR template.

This could work - one issue I see is that our release note has to be a block that contains the backticks and then the release-note string [```release-note] - I've found it hard to convey this info via docs and have seen folks just use the notes within the three back ticks without the release-note string leading to more confusing release note failures.

An alternate could be to not include release note section at all but include instructions on how to add it and if not added, specify consequences. All this does not have to be part of PR template but somewhere if it can be documented and add a reference in the PR template.

I would vote for that approach then. I will keep the "red" labels (for a good reason), but at least we won't merge PRs that should have release-note with empty release notes.. which them make the release work harder…
Kubernetes uses an empty release note (so not red label) but not commented as well, see https://raw.githubusercontent.com/kubernetes/kubernetes/master/.github/PULL_REQUEST_TEMPLATE.md. The only benefit I can see is that at least we see the empty code block so it should "warn" us that the release-note is missing.
Something change between #4929 and now (https://raw.githubusercontent.com/tektoncd/pipeline/main/.github/pull_request_template.md). It was commented before, now it is no more commented, which I agree makes it very confusing.
In all honesty I am fine going both ways:

k8s ways, which is what that PR proposes
no release-note code block at all (which I prefer)

This could work - one issue I see is that our release note has to be a block that contains the backticks and then the release-note string [```release-note] - I've found it hard to convey this info via docs and have seen folks just use the notes within the three back ticks without the release-note string leading to more confusing release note failures.

Another way could be to update our script gather release-note to look for a code block below a given title (release note), which would make it not require the release-note code block. But then the release-note prow plugin automation cannot be used 🙃.
In the end it's a battle (and a balance) between authoring, reviewing and releasing 😝.
For example, I'd rather have some "red" label that state that the release-note is not set properly (by not being there), and the comment that tells you why, than anything else. Of course it requires contributors to read those comments, which I feel is a decent ask 👼🏼.
But I can be convinced otherwise as well.

I don't feel too strongly about either approach. I'm fine with the no release-note code block

/lgtm
Discussions around whether to keep the release-note section aside, can we submit this? I was about to make the same PR because we ran into this in #5643.
Having the non-obvious space in the current template is causing friction for contributors - it looks like a bug with the release notes check, especially since there's no perceivable difference in the rendered GitHub PR markdown.

Having the non-obvious space in the current template is causing friction for contributors - it looks like a bug with the release notes check, especially since there's no perceivable difference in the rendered GitHub PR markdown.

+1, this has proven to be confusing and hostile to new contributors, and is repeatedly a stumbling block even for repeat contributors, myself included.

/hold cancel
/approve

/test pull-tekton-pipeline-alpha-integration-tests


⚠ Jenkins Plugins Artifactory has degraded performance

In 75f42ce, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1183 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 2ed8925 after 17 minutes.


Please add abilities to override default API_PATH and SCHEME (endpoint) for testing.

I cannot test it without monkey-patching like this:
module Pina
  class Configuration
    def base_url
      "http://localhost:3339/api/#{api_version}/"
    end
  end
end

Thank you

Fixed


to_datetime returns NaT for epoch with errors='coerce'

xref #11760
Parsing unix epoch timestamps give NaT with errors='coerce' while they can be parsed correctly without it:
>>> pd.to_datetime(1420043460, errors='coerce', unit='s')
NaT
>>> pd.to_datetime(1420043460, unit='s')
Timestamp('2014-12-31 16:31:00')

pandas: 0.17.1
numpy: 1.10.1
Python 2.7.7

hmm, that does seem like a bug...
pull-requests welcome!

I will take this one.

@engelmav want to do the PR?

hey Jeff, sure. I don't have the fix yet. had to pause due to issues at
work.
On Sunday, January 24, 2016, Jeff Reback<EMAIL_ADDRESS>wrote:

@engelmav https://github.com/engelmav want to do the PR?
—
Reply to this email directly or view it on GitHub
https://github.com/pydata/pandas/issues/11758#issuecomment-174345613.

Similarly, this is also not working as desired
>>> pd.to_datetime(11111111, unit='D', errors='ignore')
OverflowError: long too big to convert

@jreback I was looking at this, and some questions:
It seems this is deliberate, given the comment here: https://github.com/pydata/pandas/blob/084391126cc4edda35b41378d2905c788e5b573a/pandas/tslib.pyx#L2041 ("if we are coercing, dont' allow integers"). And I suppose this is to deal with the case of mixed types. For example, if you are parsing strings: pd.to_datetime(['2012-01-01', 1]), you want the integer to be coerced to NaT.
But, of course when having only integers, this behaviour is not correct.
But, I  was also wondering, is there a reason we don't have a special path specifically for converting epochs (integers with unit specified), instead of using the general tslib.array_to_datetime where the types are checked for each element?
def to_datetime(arg, ...):

    ....
    elif com.is_integer(arg):
        _epoch_to_datetime(arg, unit)
    ....

def _epoch_to_datetime(vals, unit):
    return vals.astype('datetime[{}]'.format(unit))

@jorisvandenbossche so it could be in a routine. What you could do is multiply then feed it back to to_datetime with the same coerce option. you can directly astype if only if errors='raise'. I think ignore you might have to iterate as well.

further I suspect we can error out on the above example as unit doesn't make sense when you don't have integers/floats (though you can allow mixed things as long as you can astype them to ints/floats) eg.
In [1]: pd.to_numeric(['1.0',2,3.0])
Out[1]: array([ 1.,  2.,  3.])

in fact could be a pre-processing step assume we pass thru the errors, because that's the rub you have to potentially iterate here.

I think I can fix this shortly.


New-StoredCredential returns object with password in plain text

Please remove the Password property from the object returned from New-StoredCredential.  This has massive security issues and most Enterprises will not be able to use the module because of it.

Ideally the New-StoredCredential cmdlet should return an actual PSCredential object (or something shaped like it). That way we could do something like:
$cred = (Get-Credential | New-StoredCredential -Target 'foo')
... and then use $cred as credentials later in the same script. The password would be a SecureString then, I think, which would resolve this issue.
The easy answer is to change PSCredentialManager.Cmdlet/Cmdlets.cs line 316 to:
WriteObject(nativeCredential);
... but I'm not sure if that would break any tests. It certainly could break some existing code.

Is this module still being maintained, this issue was opened years ago...


add rule: should explicitly define collection format #336

Closes #336
first time kotlin, so I am thankful for every improvement hint :)
Not ready jet I have to add tests for fromPaths cases.

👍

@maschleg could you please also rebase it and I'll merge it afterwards

👍


feat(networks): Add network details (#1717)

Implements feature requested in #1717:

visibility of "--internal" and "--attachable" network options in the network list view
visibility of "--internal" and "--attachable" network options in the network details view

Closes #1717

Thanks @lucamaro :+1:


Grag2021

Can you disclose the code of the Grag2021 detection method?

Hi, what is precisely that you are looking for? In the repository you can find the code to launch the tests present in the paper of the retrained Grag2021 architecture, and now also the training code. If you are looking for the original repository, you can find it here https://github.com/grip-unina/GANimageDetection


Foundation._activePlugins object remains empty

In 6.1.1
The _activePlugins object doesn't store any active plugins.
Comment on registerPlugins function in foundation.core.js:

Creates a pointer to an instance of a Plugin within the Foundation._activePlugins object.

But I couldn't find it manipulating _activePlugins at any point.

Yeah, that object is no longer being used. I'll pull it out.

Removed in d1f79fd515c719106e4d43c02865fe8b743b3468


Add uglifyjs plugin

Simply use UglifyJs plugin instead of Webpack built-in version which allows us to configure it. I'm including one useful feature to drop console.log statements to avoid eslint errors on build:production
Related to discourse discussion: https://discourse.roots.io/t/uglifyjs-error-on-production-build/12419/4?u=jasonbaciulis

Thanks!


[WIP] 1.8

It begins! Shouldn't be merged: there is going to be a lot of functionality removed.
Removed functionality

Multipart modems/network

Probably won't work

OpenPeripheral - hasn't updated to 1.8 yet
Peripherals++ - hasn't updated to 1.8 yet

Roadmap

[x] Code compiles/tests passes
[x] Test/fix ASM/patches

Turtle rendering ASM - Not implementing as it is much more of a pain.

[x] Test/fix mod blocks

[x] Correct metadata/block state handling

[x] Resources/models
[x] Turtle tool host
[x] Network visualiser
[x] Generate JSONs

Useful links
Mostly on block states/rendering. In case I forget

http://bedrockminer.jimdo.com/modding-tutorials/basic-modding-1-8/blockstates-and-metadata/
http://greyminecraftcoder.blogspot.co.uk/2015/03/troubleshooting-block-and-item-rendering.html

Pushed pr0. Currently the tool host is broken, but everything else appears to work.

Everything works!


Correct copyright notices to reflect Copyright OpenSearch Contributors

Coming from https://github.com/opensearch-project/.github/issues/21.
The correct copyright for open-source projects in opensearch-project is "Copyright OpenSearch Contributors". Please correct any places that say otherwise, especially where it says copyright Amazon. Make sure NOTICE.txt and README match. See https://github.com/opensearch-project/.github/pull/24 for an example.

The correct header for files like this one is:
# Copyright OpenSearch Contributors
# SPDX-License-Identifier: Apache-2.0

For files that contain attribution to an external project, place this long version above those of the external project(s).
# Copyright OpenSearch Contributors
# SPDX-License-Identifier: Apache-2.0
#
# The OpenSearch Contributors require contributions made to
# this file be licensed under the Apache-2.0 license or a
# compatible open source license.
#
# Modifications Copyright OpenSearch Contributors. See
# GitHub history for details.

Here is a rough list of files that need to change:
https://github.com/opensearch-project/opensearch-build/search?q=copyright+amazon.com+reserved


Is there downtime when changing plans?

I need to move a Windows Web App to another plan: same region, same resource group, both S1.  Will there be any downtime?

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

ID: 25ec88c2-d5ff-e727-cbe1-69bac94141ae
Version Independent ID: 0b6d31a9-7767-73cb-857b-ad8aa81cdce5
Content: Manage App Service plan - Azure
Content Source: articles/app-service/app-service-plan-manage.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Hi @markarnolditpro, generally there is no downtime. Scaling up should only take seconds to apply and affect all apps in your App Service plan. You can always turn On the “Always On” feature for your app. By default, web apps are unloaded if they are idle for some period of time. This lets the system conserve resources. In Basic or Standard mode, you can enable Always On to keep the app loaded all the time. If your app runs continuous web jobs, you should enable Always On, or the web jobs may not run reliably.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Internal storage API revamp

Now going through initial testing phase :)

Hi @craigzour
Does any of the new implementation support anything with Keychain Access groups on iOS?
I'm looking to support sharing between widgets and the app and hoping to find a way to reuse existing code rather than have to write up a custom widget service with iOS/Android implementations. Disclaimer - I have yet to look at codepaths for how widgets on Android can access data from the host app

Hi @feralbob
The new implementation just provides a unique and centralized wrapper on top of two storage libraries (https://github.com/pradeep1991singh/react-native-secure-key-store ; https://github.com/react-native-async-storage/async-storage) that were already used by the application. The RNSecureKeyStore provides a way to define an accessibility level but we are only using the ALWAYS_THIS_DEVICE_ONLY option so I am not sure if that helps.

Hi @feralbob
The new implementation just provides a unique and centralized wrapper on top of two storage libraries (https://github.com/pradeep1991singh/react-native-secure-key-store ; https://github.com/react-native-async-storage/async-storage) that were already used by the application. The RNSecureKeyStore provides a way to define an accessibility level but we are only using the ALWAYS_THIS_DEVICE_ONLY option so I am not sure if that helps.

Ok thanks for the info.
Relevant to this might be #1444 - I have a draft PR #1445 that updates from @react-native-community/async-storage to @react-native-async-storage/async-storage - I don't see that this PR actually makes that dependency change.

PR has been rebased on top of the latest master. Going through initial testing

Integrated @feralbob 's PR https://github.com/cds-snc/covid-alert-app/pull/1446


Implementation of Rod cutting problem (C++)

Includes Recursive , Memoized and Bottom - up implementations
Cheers

good job!


[ARI] Add temp autoscaler team for managing GitHub secrets

Without admin access we can no longer maintain GitHub Actions secrets.
Prior art for admin override teams: #441 + #691

/easycla

/easycla


Please use pypi

I used this at my raspberry pi.
I want use pip install this application, can you add it to the pypi?
followed this project from v2ex.
既然你用的英文写README，我也就用英文写issuse喽，语句不通请不要介意。

Hi tkliuxing,
Since it's just a toy project, I'm not intent to submit it to PyPi.
Using Raspberry Pi, you can just use git to get it : )

Just have fun.


BE: User tools

Adding tools to the User model
Extending the API
User tools take priority over agent tools
AI Description

This PR introduces the ability for users to have associated tools, enhancing the user model and impacting various backend components.
Code Changes:

Adds a tools attribute to the User model, allowing users to have a list of associated tools.
Updates the UserBase schema to include an optional tools attribute.
Introduces a new function, get_user_by_email, in the user.py module, enabling retrieval of a user by their email address.
Enhances the create_user and update_user functions in user.py with transaction validation.
Modifies the create_user and update_user functions in routers/user.py to include request validation dependencies.
Extends the create_user and update_user tests to cover scenarios with and without tools.
Updates the process_chat function in services/chat.py to incorporate user tools and introduces new functions for processing user and agent tools.
Adds a new function, validate_user_request, in services/request_validators.py to validate create user requests.
Includes a new module, services/user.py, with a function to validate the existence of a user.
Adjusts the User factory in tests/unit/factories/user.py to include a tools attribute.

Reasoning:
The primary purpose of this PR is to enable users to have associated tools, enhancing the user model and related functionality. This change involves modifying the User model to include a tools attribute, represented as a list of strings. This addition allows users to have a customizable set of tools associated with their account.
To support this new feature, various backend components have been updated. The create_user and update_user functions have been enhanced with transaction validation, ensuring data integrity during user creation and modification. Request validation has also been introduced to the corresponding router functions, providing additional input validation for user creation and updates.
The testing infrastructure has been expanded to cover scenarios involving user tools. This includes creating users with specific tools and updating user toolsets, ensuring that the new functionality behaves as expected.
Additionally, the process_chat function has been refactored to incorporate user tools, introducing new functions to handle tool processing for both users and agents. This change allows user tools to influence the chat process, potentially customizing the chat experience based on the user's associated tools.
Overall, this PR introduces a significant enhancement to the user model and related functionality, providing users with the ability to have and utilize associated tools.

Codecov Report
Attention: Patch coverage is 65.30612% with 51 lines in your changes missing coverage. Please review.

Project coverage is 77.01%. Comparing base (f9ec818) to head (6380110).

Files
Patch %
Lines

src/backend/tests/unit/routers/test_chat.py
14.70%
29 Missing :warning:

src/backend/services/chat.py
52.94%
16 Missing :warning:

src/backend/services/user.py
55.55%
4 Missing :warning:

...versions/2024_08_12_67f8e730f578_add_user_tools.py
90.90%
1 Missing :warning:

src/backend/services/request_validators.py
91.66%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #664      +/-   ##
==========================================
- Coverage   77.10%   77.01%   -0.09%
==========================================
  Files         238      240       +2
  Lines       10455    10585     +130
==========================================
+ Hits         8061     8152      +91
- Misses       2394     2433      +39

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

Couple suggestions

Thanks TJ, everything is resolved


Calculate measurement errors, handling missing data along with outliers

How are the measurement errors, missing data along with outliers handled within Robyn? Could you point me to the documents if there are any?

Robyn doesn't really take care of these and expects users to clean the data before feeding it in. Outliers are partially dealt with due to the normalisation and nonlinear transformation.


Add version option to display UC version on command line

When executed with --version, start-uc-server and uc command should display the UC version:
❯ ./bin/start-uc-server --version

Parsing Failed. Reason: Unrecognized option: --version

❯ ./bin/uc --version
Error occurred while parsing the command. Please check the command and try again. Missing argument for option: version

take


Publish to NPM

This is a reminder that 1.4.6 isn't published to NPM right now.
cc @kylestetz If you see this before Friday, would you mind pulling and pushing to NPM? My computer for the week is too old :cry:

Done :+1:


Debugging multiple files in node.js from one window - selection option disappears after restarting one of the debugged processes

VSCode Version: Code 1.10.2 (8076a19fdcab7e1fc1707952d652f0bb6c6db331, 2017-03-08T13:56:35.908Z)
OS Version: Darwin x64 16.5.0
Extensions:

Extension
Author
Version

beautify
HookyQR
1.0.2

vscode-github
KnisterPeter
0.12.1

start-git-bash
McCarter
1.2.1

vscode-docker
PeterJausovec
0.0.9

vscode-tidyhtml
anweber
1.5.0

git-easy
bibhasdn
1.9.1

vscode-eslint
dbaeumer
1.2.8

vscode-instant-markdown
dbankier
1.1.0

githistory
donjayamanne
0.2.0

javadebugger
donjayamanne
0.0.2

python
donjayamanne
0.5.5

vscode-npm-script
eg2
0.1.9

json-tools
eriklynd
1.0.2

javac-linter
faustinoaq
1.2.1

vscode-npm
fknop
3.3.0

docker-linter
henriiik
0.3.0

vscode-auto-open-markdown-preview
hnw
0.0.4

restructuredtext
lextudio
0.0.22

MagicPython
magicstack
1.0.9

copy-github-url
mattlott
0.1.0

vs-keybindings
ms-vscode
0.1.3

debugger-for-chrome
msjsdiag
3.0.1

git-add-remote
samschneller
0.0.2

git-common-commands-suite
samschneller
0.2.2

git-pull-upstream
samschneller
0.0.7

preview-vscode
searKing
1.1.5

ignore-gitignore
stubailo
1.0.1

rst-vscode
tht13
2.0.0

Steps to Reproduce:

Start to debug multiple apps in one window
After both start up, the debug tool palette has a selector to choose which app to pause/stop/restart
After restarting one, the selector disappears and you can only control the most recently restarted debug session
The processes also disappear from the sidebar

I can not reproduce this with latest VSCode insiders.
Please try with latest vscode insiders which you can find here https://code.visualstudio.com/insiders
If you can still reproduce please try with a minimalstic node project and share that project here so I can investigate on my machine

Trying it with 1.11.2 and so far it seems to be solved...
On Mon, Apr 24, 2017 at 6:26 AM, Isidor Nikolic<EMAIL_ADDRESS>wrote:

I can not reproduce this with latest VSCode insiders.
Please try with latest vscode insiders which you can find here
https://code.visualstudio.com/insiders
If you can still reproduce please try with a minimalstic node project and
share that project here so I can investigate on my machine
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/25091#issuecomment-296667055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXZaTmzg3fPzaJaPgwc-FWlaR50zfEZ_ks5rzKMSgaJpZM4NDdCq
.

--
Gyuri

Closing until @gordody confirms he can still reproduce and till he provides more details

Some more granular steps to repro, in all current versions, including
Version 1.12.0-insider (1.12.0-insider)
d8a1d8b8a7c886547ba6bc0d81fc2ff639d4c9f5
2017-04-27T06:02:48.818Z

Create a new project with a main file (index.js) that has a server (a simple web server should do) in it and some tests
Create debug configurations for both
Set a breakpoints in the tests
Start to debug your main app
Start to debug your tests
Both should show up in the dropdown of the debugger toolbar
Have your test hit a breakpoint in the app
Restart the test using the Debugger toolbar restart button
Your test will disappear from the dropdown of the debugger toolbar

This is now fixed in the latest insiders (2hours ago)
Can you please try again @gordody
Dup of https://github.com/Microsoft/vscode/issues/24979


ApproxEq trait enhanced with ULPs method of specifying closeness:

See issue #60.
Background reading:  https://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/
approx_eq_ulps() allows specification of epsilon as an integer number
of Units in the Last Place (ULPs) difference between the two floating
point values
default approx_ulps() is set to 8.
approx_eq() function continues to use epsilon method, although I
recommend further commits and a migration towards the ULPs method.

Looks good. See #60 for my comment about mighating approx_eq to the ulps method.


Training file error when using initModel

Hello, I am trying to train a StarSpace classifier while initializing the algorithm with a fastText model (which I converted to a tsv format). When I try to run StarSpace on the training file without the initModel option, everything runs ok:
./starspace train -trainFile training.txt -model wiki
Arguments:
lr: 0.01
dim: 100
epoch: 5
maxTrainTime: 8640000
saveEveryEpoch: 0
loss: hinge
margin: 0.05
similarity: cosine
maxNegSamples: 10
negSearchLimit: 50
thread: 10
minCount: 1
minCountLabel: 1
label: __label__
ngrams: 1
bucket: 2000000
adagrad: 1
trainMode: 0
fileFormat: fastText
normalizeText: 0
dropoutLHS: 0
dropoutRHS: 0
Start to initialize starspace model.
Build dict from input file : training.txt
Read 0M words
Number of words in dictionary:  395
Number of labels in dictionary: 105
Loading data from file : training.txt
Total number of examples loaded : 608
Training epoch 0: 0.01 0.002
Epoch: 98.5%  lr: 0.010000  loss: 0.025505  eta: <1min   tot: 0h0m0s  (19.7%)
 ---+++                Epoch    0 Train error : 0.01774764 +++--- ☃
Training epoch 1: 0.008 0.002
Epoch: 98.5%  lr: 0.008000  loss: 0.000451  eta: <1min   tot: 0h0m0s  (39.7%)
 ---+++                Epoch    1 Train error : 0.00089402 +++--- ☃
Training epoch 2: 0.006 0.002
Epoch: 98.5%  lr: 0.006000  loss: 0.000014  eta: <1min   tot: 0h0m0s  (59.7%)
 ---+++                Epoch    2 Train error : 0.00013078 +++--- ☃
Training epoch 3: 0.004 0.002
Epoch: 98.5%  lr: 0.004000  loss: 0.000107  eta: <1min   tot: 0h0m0s  (79.7%)
 ---+++                Epoch    3 Train error : 0.00006586 +++--- ☃
Training epoch 4: 0.002 0.002
Epoch: 98.5%  lr: 0.002000  loss: 0.000005  eta: <1min   tot: 0h0m0s  (99.7%)
 ---+++                Epoch    4 Train error : 0.00002807 +++--- ☃
Saving model to file : wiki
Saving model in tsv format : wiki.tsv

However, when I use the same with the initModel, it looks like the model is loaded fine, but for some reason the algorithm throws and exception for the training file:
./starspace train -trainFile training.txt -model wiki -initModel wiki_50k.tsv -dim 300
Arguments:
lr: 0.01
dim: 300
epoch: 5
maxTrainTime: 8640000
saveEveryEpoch: 0
loss: hinge
margin: 0.05
similarity: cosine
maxNegSamples: 10
negSearchLimit: 50
thread: 10
minCount: 1
minCountLabel: 1
label: __label__
ngrams: 1
bucket: 2000000
adagrad: 1
trainMode: 0
fileFormat: fastText
normalizeText: 0
dropoutLHS: 0
dropoutRHS: 0
Start to load a trained embedding model in tsv format.
Loading dict from model file : wiki_50k.tsv
Number of words in dictionary:  50016
Number of labels in dictionary: 0
Loading model from file wiki_50k.tsv
Model loaded.
Loading data from file : training.txt
Total number of examples loaded : 0
ERROR: File 'training.txt' does not contain any valid example.
Please check: is the file empty? Do the examples contain proper feature and label according to the trainMode? If your examples are unlabeled, try to set trainMode=5.

Any idea why this happens?

@Tiriar Hi, thanks for reporting. Yes, StarSpace does not add new vector once the initModel is set, so that's why it gives error since there's no label presented in initModel. I'd suggest you to add some dummy / random vectors as your label vector in addition to what you have from fastText. That way StarSpace can carry on training from there.

@ledw Thank you, adding the label vectors to the pretrained model works :+1: . Closing the issue.

@Tiriar @ledw how to add the training label vectors?

Sorry @rilut , this was over 2 years back and I do not remember how exactly I did it. But as long as you have the file with pre-trained vectors in txt/tsv format, adding new vectors should be as simple as adding new rows to the file - just generate a random vector for each label and add them as new rows in the same format as the other word vectors that are already present.

@Tiriar no worries, thank you


Added backfill migration for members created events

closes https://github.com/TryGhost/Team/issues/1836

Uses the timestamps from the members table to determine the timestamps for the events
Clears the table when downgrading to prevent having multiple rows for the same member

@daniellockyer I think this is ready for final review


Footer 37

Adding responsive footer Issue  #37

Close #37

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[] I have commented my code, particularly in hard-to-understand areas
[] I have created a helpful and easy to understand README.md

can we also add a new file with code included in it?


Join&SplitFunction

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

Carbon Requirements
| Detail Carbon Settings

[x] Select Dracula Theme

[x] Select right programming language

[x] Set largest font size

Commit requirements

[x] Image should be added to screenshots folder

[x] Code snippet should be added to codes folder

[x] Image and code snippet have the same name for their files

We loved this PR! Thanks for contributing. Today's tip is from @Wrapperss


Need ability to attach prefix-list to peer-group or neighbor without route-map

Is your feature request related to a problem? Please describe.
The tmsh commands for routing bgp and prefix list can be attached to neighbors directly or to a peer group. The DO schema however does not show a prefix-list option in the object class for peer-group. There is a route-map option but that only applies to peer-group.
Describe the solution you'd like
Need ability to attach prefix-list to neighbor and/or peer-group directly. This way if I only have one bgp peer, I'm not required to create a peer-group simply to get a prefix-list attachment. This should be attachable to the neighbor just like in imish or in tmsh command.
Example...
tmsh create net routing prefix-list myPrefixList1 { entries add { 10 { action permit prefix <IP_ADDRESS>/8 prefix-len-range 16: } } route-domain 0 }
create net routing bgp myBGP local-as 65530 neighbor add { <IP_ADDRESS> { address-family { ipv4 { prefix-list { out myPrefixList1 } } } remote-as 65515 } }
show run...
router bgp 65530
neighbor <IP_ADDRESS> remote-as 65515
neighbor <IP_ADDRESS> prefix-list /Common/myPrefixList1 out
Describe alternatives you've considered
I have to run tmsh commands to apply prefix list directly to neighbor. If I use DO, then I'm forced to create a peer-group first. Also, peer-group in tmsh can have a prefix list attached whereas in DO you have to use a routemap which links to prefix list.
Additional context
none

Thank you for your feedback. This request has been added to our internal product backlog as AUTOTOOL-2760.


ghidra.program.database.code.InstructionDB does not return complete/correct/consistent operand data for ARM:LE:32:v8 add instruction

Describe the bug
ghidra.program.database.code.InstructionDB does not return complete/correct/consistent operand data for ARM:LE:32:v8 add instruction e.g.
>>> insn = getInstructionAt(currentAddress)
>>> print(insn.getAddress(), insn)
(000157c4, add r2,sp,#0x10)
>>> for i in range(insn.getNumOperands()):
... 	print(i, insn.getOpObjects(i))
...
(0, array(java.lang.Object, [r2]))
(1, array(java.lang.Object, [sp]))
(2, array(java.lang.Object, [0x10]))
>>>
>>>
>>>
>>> insn = getInstructionAt(currentAddress)
>>> print(insn.getAddress(), insn)
(00011f36, add r7,sp,#0xc)
>>> for i in range(insn.getNumOperands()):
... 	print(i, insn.getOpObjects(i))
...
(0, array(java.lang.Object, [r7]))
(1, array(java.lang.Object, [sp, 0xc]))

To Reproduce

Load and analyze https://www.virustotal.com/gui/file/ec834074b81a536a44f903619a1fcae76c3cf35309d6a394d9fbb5d4479b6ba0
Execute code shown above for listed instructions:

(000157c4, add r2,sp,#0x10)
(00011f36, add r7,sp,#0xc)

Expected behavior
I'd expect ghidra.program.database.code.InstructionDB to behave the same for both instructions, specifically, in the case of the former example where the number of operands equals three, resulting in:
>>> insn = getInstructionAt(currentAddress)
>>> print(insn.getAddress(), insn)
(000157c4, add r2,sp,#0x10)
>>> for i in range(insn.getNumOperands()):
... 	print(i, insn.getOpObjects(i))
...
(0, array(java.lang.Object, [r2]))
(1, array(java.lang.Object, [sp]))
(2, array(java.lang.Object, [0x10]))
>>>
>>>
>>>
>>> insn = getInstructionAt(currentAddress)
>>> print(insn.getAddress(), insn)
(00011f36, add r7,sp,#0xc)
>>> for i in range(insn.getNumOperands()):
... 	print(i, insn.getOpObjects(i))
...
(0, array(java.lang.Object, [r7]))
(1, array(java.lang.Object, [sp]))
(2, array(java.lang.Object, [0xc]))

Environment:

OS: Ubuntu 24
Java Version: 17
Ghidra Version: 11.1
Ghidra Origin: GitHub distro

The operand list is based entirely on the slaspec constructor and subcontractor breakdown of instruction print-pieces.  For x86 the enclosed group within brackets constitutes a single operand which may consist of multiple op-objects.  Using the instruction info display you can see how a selected instruction breaks down to specific subconstructors within the slaspec.  What you are observing is not a biug.

You may want to consider examining the default representation list which will give access to those registers, scalars and addresses visible in the instruction rendering.  The opObject lists that you are using can return anything used by pcode fragments for a specific operand index.  Issues with this approach include unpredictable operand numbering based on sleigh instruction breakdown, and inclusion of opObjects not shown in rendering.  Representation list are more about what you see.


Update registration from link in ESDS event announcement

Thanks @kafitzgerald ! I updated the form to allow non-NCAR submissions


Deploy gutendex on heroku.com

Hello
I try to deploy gutendex on heroku.com. But I don't know exactly how to do it. What I did so far:
Create "Procfile" file:
release: pip install gunicorn && python manage.py migrate && python manage.py updatecatalog && python manage.py collectstatic web: gunicorn gutendex.wsgi
Catalog (DB) is now generated. But somehow Server always crash on start up:

Maybe someone can help me?

Hello @garethbjohnson
Thank you for your help.
I did exactly what you advice me. It run through processes but in end somehow server not really run (crashing). Any idea what else I could try?

Ah, I think you now just need to add the line gunicorn==20.1.0 to your "requirements.txt". (Also make sure you have django-heroku==0.3.1.)

@garethbjohnson
YES! Thank you very much, now is working!


Filter tables by date and time interval

Please describe the problem that your request should resolve.

Describe the solution you'd like

Is it already possible to achieve the same outcome in any other way? If so, how?

Additional context

Duplicate of https://github.com/aeternity/aescan/issues/615


add configuration setting for ctrl-a/x number regexps

fixes #641

Thanks @jacekkopecky , for me, I tested your code by copy&paste, as @maxbrunsfeld said, explicit fallback wasn't necessary.
It might test(spec) related issue(since I didn't run spec) or your environment issue.
Anyway thanks for this, and I hope this PR will be merged.

@t9md without the fallback, the new specs were failing for me – it seems when running specs, atom.config.get doesn't return the proper defaults. I don't have the brain cycles now to look into that, so I've included a workaround in the specs now instead of in the main code.
@maxbrunsfeld – is this better now?

:+1: Thanks!


BulkData Export produces FHIROperationException

Describe the bug
When using the fhir-operation-bulkdata module within my IBM FHIR Server by accessing the URL url:9080/$export (no matter if with or without Query-Parameters), the Response is a simple FHIROperationException: Error while processing the $export request.
The Logs only contain the same Error Message, but no stacktrace or other hints on the error-source.
Is there a special log for the bulkdata-module?
To Reproduce
Steps to reproduce the behavior:

curl -k -u "fhiruser:change-password" -H "Content-Type: application/fhir+json" -X GET 'http://localhost:9080/fhir-server/api/v4/$export?_outputFormat=application/fhir%2Bndjson&_type=Patient' -v
or alternatively using Postman
See error

Expected behavior
Should export the content to COS or at least show more usefull error messages.
Additional context
I'm using IBM FHIR 4.3.0 in combination with PostgreSQL via Docker-Compose. In Order to enable the bulkdata-module, i configured the files configDropins/defaults/bulkdata.xml, /config/default/fhir-server-config.json, and server.xml according to the Guide.

Possibly related to Issue #1161 (at least wider OperationOutcomes could give hints on the error-source)

There are two locations to look for log files:
fhir-server/logs/ which has messages.log and trace.log
trace.log is populated when you change your server.xml to add the following:
<logging traceFormat="BASIC" traceSpecification="*=info:com.ibm.fhir.*=finest"/>
You should not run with the traceSpecification com.ibm.fhir.*=finest in production.
The second spot is related to JavaBatch. in the fhir-server/logs folder you'll see another folder joblogs, and you'll navigate down to the date folder fhir-server/logs/joblogs/bulkexportchunkjob/2020-07-17.  That will have even more information.  If the request succeeded to generate the java batch job.
Regarding the comment, #1161 is not directly related, it's on the javabatch operationoutcomes when acting on the import or export data.  What you are seeing is the Operation failing which mediates the interaction between the REST operation and the JavaBatch.
If you can grab the trace.log, I can help you figure out the issue.  Right now it looks like it's in the creation of the job that is failing.

my fhir-server/logs/ folder only contains state/com.ibm.ws.jmx.local.address and state/plugin-cfg.xml
Does the logging-configuration above belong underneath the <server drescription="fhir-server"> tag in server.xml?

Yes, under server.xml (it's actually commented out in the default server.xml as an example)
in the case of fhir-server/logs the default is to log out to the docker console, if you enable the trace.log, you should see that folder populated.  (I think on some docker containers, it might be mapped from /logs

Hi @corneliusknopp checking in... were you able to get your issue addressed with the additional logs?

Moved to Review/QA (will close at end-of-iteration).

I've not managed to populate either messages.log or trace.log.
The given line (<logging traceFormat="BASIC" traceSpecification="*=info:com.ibm.fhir.*=finest"/>) does not make any difference.
Within the Docker Logs i've found the following Warnings regarding bulkdata:
[WARNING ] CWNEN0048W: Resource annotations on the fields of the com.ibm.fhir.jbatch.bulkdata.export.patient.ChunkReader class will be ignored. The com.ibm.fhir.jbatch.bulkdata.export.patient.ChunkReader class is being processed for annotations because it is referenced by the com.ibm.fhir.jbatch.bulkdata.export.group.ChunkReader application class. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0049W: Resource annotations on the methods of the com.ibm.fhir.jbatch.bulkdata.export.group.ChunkReader class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0047W: Resource annotations on the fields of the com.ibm.fhir.jbatch.bulkdata.export.system.ChunkReader class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0049W: Resource annotations on the methods of the com.ibm.fhir.jbatch.bulkdata.export.system.ChunkReader class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0047W: Resource annotations on the fields of the com.ibm.fhir.jbatch.bulkdata.load.ChunkWriter class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0049W: Resource annotations on the methods of the com.ibm.fhir.jbatch.bulkdata.load.ChunkWriter class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0047W: Resource annotations on the fields of the com.ibm.fhir.jbatch.bulkdata.export.patient.ChunkReader class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException
[WARNING ] CWNEN0049W: Resource annotations on the methods of the com.ibm.fhir.jbatch.bulkdata.export.patient.ChunkReader class will be ignored. The annotations could not be obtained because of the exception : java.lang.NoClassDefFoundError: com.ibm.fhir.exception.FHIRException```

Besides this, there are some Warnings on missing `derbyLocale_XX_XX.jar` within `fhir-server-webapp.war/WEB-INF/lib/...` which should not affect the functionality as PostgreSQL is used.

The derbyLocale warnings are expected as we do not bundle the locale jars.  This is a benign warning.
The logs indicate you are missing a fhir-config entry.
Are you on the 4.4.0 release? I'd suggest moving up to the latest release. As it sounds like you have an older version on searching the annotations (note that above is just a warning).

ok, so the derbyLocale warnings can be ignored

Missing entry within fhir-server-config.json ? I pasted the bulkdata Configuration into the 2nd leven (same level as core, audit & persistence)

I've already moved on to version 4.3.3

The Error when running the curl-command of original post is still present.
There is no messages.log or trace.log created which i could send to you.

The warning above was a missing Annotation in the javacode that produces that warning. It was fixed in an earlier version maybe 4.2.*, it shouldn't be there in 4.3.3.
If you are using the docker image, are you checking /logs ?

I'd be happy to do a screenshare and diagnose with you next week, you can ping me on Zulip - https://chat.fhir.org/#narrow/stream/212434-ibm

If you are using the docker image, are you checking /logs ?

Do you mean /opt/ol/wlp/usr/servers/fhir-server/logs/?
There is only the state/ folder containing com.ibm.ws.jmx.local.address & plugin-cfg.xml. Nothing else.
Or do you mean the docker logs for the FHIR-Container?

I'd be happy to do a screenshare and diagnose with you next week, you can ping me on Zulip - https://chat.fhir.org/#narrow/stream/212434-ibm

Thank you! I will do this.

We remap the logs to /logs if you check there the logs should be in that folder.
Yes, please reach out, I'm a bit preoccupied this week, but would be happy to work with you.
@lmsurpre also might be available.


Ceil evaluation

Reviewer checklist

[ ] Test coverage: stack test --coverage
[ ] Public API documentation: stack haddock
[ ] Style conformance: stylish-haskell

Still needs tests.


Ci setup

WIP created to trigger github ci
do not merge

For now windows wheels are excluded, see #4.


Don't set image pull policy by default

This PR does not set the imagePullPolicy by default.
Like this the manager can set the imagePullPolicy when defaulting BatchTransfer and StreamTransfer.
The current policy is IfNotPresent which will reuse images that are already downloaded in a cluster. When updating the image behind the tag (Currently we're still using latest) this will result in still using the old image.
Like this the installation of the-mesh-for-data decides the policy.

From https://kubernetes.io/docs/concepts/containers/images/#updating-images it seems to not be equivalent when latest tag is used.


Incorrect env name port in DaemonSet example

According to the documentation, there is no variable named port. Do you mean lb_port  here?
https://github.com/kube-vip/website/blob/12398baf5ae07e3143a1125f054f3cf42c19895e/content/docs/installation/daemonset.md?plain=1#L116-L117
https://github.com/kube-vip/website/blob/12398baf5ae07e3143a1125f054f3cf42c19895e/content/docs/installation/daemonset.md?plain=1#L222-L223

Oh, maybe port is right and lb_port is wrong? I see that the generated pod spec uses port here:
https://github.com/kube-vip/kube-vip/blob/f7666067a49f04922c469198924b200dc8405084/pkg/kubevip/config_generator.go#L31-L34

Looks like port is the right name: https://github.com/kube-vip/kube-vip/blob/f7666067a49f04922c469198924b200dc8405084/cmd/kube-vip.go#L77


Rename reconilers to align with API types

Depends on #28
The corev1.ObjectReference exists to reference objects across namespaces. This replaces the existing MachineRef to use the standard library and reduce the Rufio API surface area.
Closes #25

Codecov Report

Merging #29 (456548f) into main (e75290f) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Current head 456548f differs from pull request most recent head 886b53d. Consider uploading reports for the commit 886b53d to get more accurate results

@@           Coverage Diff           @@
##             main      #29   +/-   ##
=======================================
  Coverage   18.98%   18.98%
=======================================
  Files           4        4
  Lines         316      316
=======================================
  Hits           60       60
  Misses        249      249
  Partials        7        7

Impacted Files
Coverage Δ

controllers/job_controller.go
0.00% <0.00%> (ø)

controllers/task_controller.go
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Enable Tensorflow image recognition saved model examples using new API

Signed-off-by: Lv, Liang1<EMAIL_ADDRESS>Type of Change
feature
API not changed
Description
detail description
JIRA ticket: ILITV-2598
Expected Behavior & Potential Risk
Tensorflow image recognition saved model examples using new API enabled successfully.
How has this PR been tested?
Pre-CI and examples test.
Dependency Change?
No.

extension test

https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/4166/artifact/report.html

extension test: https://inteltf-jenk.sh.intel.com/blue/organizations/jenkins/intel-lpot-validation-top-mr-extension/detail/intel-lpot-validation-top-mr-extension/4201

Extension test is good.
https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/4302/artifact/report.html


hierarchical JSON in log

Hi,
Our log message looks like
{
  "message": "som message"
  "context": {some json}
}

Problem is, with current fluentd configuration, context goes to clickhouse as a plain text (with => symbol in place of :), and there is no way to filter logs against fields in context.
Is there way to fix it?
Thanks.

PR #115  contains a workaround for hierarchical JSON problem. It is applicable if json log contains a specific key.
I think we need a more generalized approach to this problem. For example implement mapping with like this:
original:
{
  "message": "som message"
  "context": {
    "path":"/",
    "username":"admin"
  }
  "params": ["green", "red", "blue" ]
}

resulting string_fields:

message = "som message"
context.path = "/"
context.username="admin"
params.0 = "green"
params.1 = "red"
params.2 = "blue"

Any news about the issue?


Using Foundation-apps on a different stack

I'm a big fan of Foundation, so was keen to use Foundation Apps as I am using Angular JS. However I am struggling to adapt it to use with my project and directory structure and my own server (Java not NodeJs).
For example, I installed the bower version of this framework and then made links to "foundation-apps.min.js", however then I get errors about not finding the components folder (as the framework assumes the component folder is in the root). So I had to copy the entire components folder into the root of my directory, which I really did not want to do, as now all bower updates are no longer in sync.
I'm sure other problems will soon crop up later, so I wish to find out is there an easier way to use Foundation for Apps using your own directory structure. I.e. is there like some kind of config property to allow me to specify my directories.
If not, can anyone give me some pointers in how to use FA using my own directory structure the "correct" way. Should I have copied the entire components folder into my directory for example?
Please note, I am not concerned with using the the Gulp stuff.

We've got a big improvement coming in v1.1, which will hopefully be out tomorrow. For the directive templates, we're using ng-html2js to pack them all into a single JavaScript file, meaning you won't need to copy those HTML files from the Bower package.
We also added a new feature to the Iconic directive which allows you to specify the path your icon files are in.
Are there any other specific concerns you have related to directory structure?

Awesome. Please do. I think FA can be a really good project, but there's definitely a lot of improvements that can be made, and not forcing how the user uses FA I think is key!

Definitely! Thanks for your feedback. Other than which Angular add-ons we use (namely ui-router and ngAnimate), we want to avoid being prescriptive with regards to how people design or code. That'll always be a goal for all three of the Foundation frameworks.
Also, 1.1 got pushed to tomorrow (Monday), but it'll get there.


:memo: harmonize version in CHANGELOG.md

There is additional configurations: https://github.com/anton-yurchenko/git-release?tab=readme-ov-file#configuration


K8S testing: test parallel execution of multiple tests

Run tests 6 times
Check how pods are created.
Run kubectl get pods

Executions 306, 311, 312, 318 and 319 have already been running in parallel


Check Formatting not working

It seems that the yapf (python) process hangs when checking the format. I was able to solve the problem by passing the --style parameter, as is done when calling formatCode (which should be done anyway?).
I'm running yapf version 0.2.0 with Python 2.7 under Windows 7.

Hmm, I am using a fully updated Mac with python 2.7.10 and atom 1.0 and it isn't hanging.  I will try and get a Windows VM set up and test this there too.  So are you saying that if nothing is in the style setting (which means the style flag won't get set that causes the hang?

Atom itself doesn't hang, but the python process does. Every time I call the check format from Atom, a new python process is spawned, which never returns and continually consumes CPU. I tried running yapf from the command line, the same happens. When I provide a style, it works. However, I tested on a Linux machine, and it works fine there. But shouldn't the style be also passed to  yapf when checking the format anyway?

This appears to be a problem with yapf itself and not my atom plugin.
See https://github.com/google/yapf/issues/159
Once they fix that it should also fix the issue you are seeing.


Bloomsky issues

The camera snapshot is zoomed in and missing a large portion of the image that is saved.
Also adding the api key through the ui would not save for me. I had to manually add it to blue mix-settings.

Hi. Yes camera images on the screen are cropped but it still saves full image. I will address this later since it happens for all cameras. Regarding api key - I am not able to reproduce this. I deleted it from ui and re added and it works. Make sure you have latest flows imported for integration tab.

fixed image cropping.


Add more event handlers to State

I've somewhat stubbornly tried to keep the State trait as minimal as possible up until this point - that approach is starting to break down, I think.
For example, the camera and scaling APIs need to be kept updated on changes to the window size - the only way to do that with the 0.2 API is to constantly poll for it in update or draw, which isn't great.
So I'm thinking I might expose more 'hooks' on the State trait, for things like resizes, input events, etc. This would be in addition to the existing APIs, rather than replacing anything (e.g. the existing polling input methods will still be available).

That's exactly what I missed in my last game. At the moment you just can't change the window size. :smile:

I've slightly changed the interface for this - there's now a single event method, which gets called whenever a window/input event gets fired. There's several reasons for this:

It's less typing/rework when you want to handle a new kind of event.
Using an Event enum will help me decouple the platform layer, and it'll be more consistent with what I have in mind for custom game loops in the future.
Due to pattern matching, you don't have to import as many types.
The Twitter horde liked it more 😅

There is now an event for every window event I'm currently handling (might add more later), and every input method available (in other words, anything you can do with the input module you can also now do with events).


serialize functions for requestBodySerializer are generated with wrong interface

The kiota generator generates an invalid serialize function. This requires the strictNullChecks to be set to false in the tsconfig. The kiota generator however should include null in the function interface.
This behaviour is occurring always, no matter the OpenAPI document content.
Command
kiota generate -l typescript --clean-output -d swagger.json -c PostsClient -o .\src\generated-sources
Error
TS2322: Type
(writer: SerializationWriter, userName?: Partial<UserName> | undefined) => void
is not assignable to type
PrimitiveTypesForDeserialization | ModelSerializerFunction<Parsable> | undefined
Type
(writer: SerializationWriter, userName?: Partial<UserName> | undefined) => void
is not assignable to type ModelSerializerFunction<Parsable>
Types of parameters userName and value are incompatible.
Type Partial<Parsable> | null | undefined is not assignable to type Partial<UserName> | undefined
Type null is not assignable to type Partial<UserName> | undefined

Generated function
/**
 * Serializes information the current object
 * @param writer Serialization writer to use to serialize this model
 */
export function serializeUserName(writer: SerializationWriter, userName: Partial<UserName> | undefined = {}) : void {
    writer.writeStringValue("name", userName.name);
}

expected result
/**
 * Serializes information the current object
 * @param writer Serialization writer to use to serialize this model
 */
export function serializeUserName(writer: SerializationWriter, userName: Partial<UserName> | null | undefined = {}) : void {
    writer.writeStringValue("name", userName.name);
}

Alternatively the serializer interfaces should not have null as possible value.
Example OpenAPI Document
{
    "x-generator": "NSwag v<IP_ADDRESS> (NJsonSchema v<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>))",
    "openapi": "3.0.0",
    "info": {
        "title": "Example",
        "version": "1.0.0"
    },
    "servers": [
        {
            "url": "https://localhost:5041"
        }
    ],
    "paths": {
        "/api/weatherforecast/user-info": {
            "post": {
                "tags": [
                    "WeatherForecast"
                ],
                "operationId": "WeatherForecast_SetUser",
                "requestBody": {
                    "x-name": "user",
                    "content": {
                        "application/json": {
                            "schema": {
                                "$ref": "#/components/schemas/UserName"
                            }
                        }
                    },
                    "required": true,
                    "x-position": 1
                },
                "responses": {
                    "200": {
                        "description": "",
                        "content": {
                            "application/json": {
                                "schema": {
                                    "$ref": "#/components/schemas/UserName"
                                }
                            }
                        }
                    }
                }
            }
        }
    },
    "components": {
        "schemas": {
            "UserName": {
                "type": "object",
                "additionalProperties": false,
                "properties": {
                    "name": {
                        "type": "string"
                    }
                }
            }
        }
    }
}

Hi @Weeb6279
Thank you for using kiota and for reaching out.
Kiota is already generating the following code.
export function serializeUserName(writer: SerializationWriter, userName: Partial<UserName> | undefined | null = {}) : void {
    if (userName) {
        writer.writeStringValue("name", userName.name);
    }
}

Please make sure you have the latest version of kiota (1.21.0) and of the dependencies (preview 77)
Let us know if you have any additional comments or questions.

Hi @baywet,
that was indeed the issue. I forgot that the kiota cli is installed in an extra step. The installed version was 1.15. I updated to 1.21 and now the function interface is matching, thank you for your help.


Possible minor data structure optimization and string allocation minimization

Pulled and tweaked changes in https://github.com/pusewicz/wave-function-collapse-ruby/pull/2. Thanks!


fails for VSCode

When building the VSCode Recipe with bash -ex pkg2appimage-with-docker VSCode it fails in a weird way i can't figure out right now.
Done
+ FILES=/workspace/VSCode//workspace/VSCode/code_1.48.0-1597304990_amd64.deb
+ '[' '!' -z /workspace/VSCode//workspace/VSCode/code_1.48.0-1597304990_amd64.deb ']'
+ echo /workspace/VSCode//workspace/VSCode/code_1.48.0-1597304990_amd64.deb
+ read file
+ cp -s /workspace/VSCode//workspace/VSCode/code_1.48.0-1597304990_amd64.deb .
cp: cannot stat '/workspace/VSCode//workspace/VSCode/code_1.48.0-1597304990_amd64.deb': No such file or directory
+ cleanup error
+ '[' appimage-build-21rhu4qd == '' ']'
+ '[' error == error ']'
+ log 'error occurred, cleaning up...'
+ echo -e '\e[91m\e[1merror occurred, cleaning up...\e[0m'
error occurred, cleaning up...
+ docker ps -a
+ grep -q appimage-build-21rhu4qd
+ docker rm -f appimage-build-21rhu4qd

I don't understand where the /workspace/VSCode//workspace is coming from.

Maybe one of the latest commits has broken it. Can you go back and try older commits, and tell me which one is the newest that still works?
E.g., this one
https://raw.githubusercontent.com/AppImage/pkg2appimage/dc1dd8a522c6d913b3d3f7cd025a4adf2fa4295e/pkg2appimage

I didn't have enough time just now. I "fixed" it, by changing the script:
  FILES=$(apt-get --allow-unauthenticated -o Apt::Get::AllowUnauthenticated=true $OPTIONS -y install --print-uris $INSTALL | cut -d "'" -f 2 | grep -e "^file" | cut -d ':' -f 2 | sed -En "s/\/workspace\/VSCode\/(\/.*)/\1/p") || true
  if [ ! -z "${FILES}" ] ; then
    echo $FILES | while read file ; do
      cp -s $file . || true
    done
  fi
fi

Dirty, but it worked. I just needed a quick replacement for my current flatpak. It still is not as i would want it (as running podman/docker still is broken), but at least it works.
I'm on Silverblue right now, and probably will go back to a normal fedora with vscode installed as deb. All those packaging solutions so far only complicated my life, sadly :-/
Or I give the vscode server stuff another try.

fwiw, there is also readymade AppImages of VSCodium:
https://github.com/VSCodium/vscodium/releases

It seems same issue as #429.

Please retry now.
wget -c https://github.com/$(wget -q https://github.com/AppImage/pkg2appimage/releases -O - | grep "pkg2appimage-.*-x86_64.AppImage" | head -n 1 | cut -d '"' -f 2)
chmod +x ./pkg2appimage-*.AppImage
./pkg2appimage-*-x86_64.AppImage VSCode
./out/Visual_Studio_Code-*-x86_64.AppImage

works for me:

Feel free to comment if it doesn't for you.


Extend documentation for NextJS

With the existing functions it should be possible to add this library easily to Nextjs. BC I need it 😅 and probably many do. I’ll try to do it in the coming days, maybe someone’s quicker 🚀

I'm sure it's possible, but I don't personally have time to work on it. Happy to merge a PR that adds utilities for Next.js though


Creating a view in csv connection

Hi!
I couldn't find any documentation on creating views, especially in the case of a csv connection. Basically, that would be a csv to cvs view. Is this possible?
thx & tia,
ada

Driver that is used by DBeaver for now, doesn't support View creation.
By the way, you could try some third-party drivers.
Possibility to create view from UI would be disabled in scope of #9361


Sidecar telemetry interface

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

closing in favor of dd_trace_php_wip branch


different validation AP/AR result for coco

I'm running valid.py for 256x192 resnet 50 network in COCO dataset.
I get different validation result from yours in readme.
This is your result
256x192_pose_resnet_50_d256d256d256 | 0.704 | 0.886 | 0.783 | 0.671 | 0.772 | 0.763 | 0.929 | 0.834 | 0.721 | 0.824
and this is what i get
Average Precision  (AP) @[ IoU=0.50:0.95 | area=   all | maxDets= 20 ] = 0.724
Average Precision  (AP) @[ IoU=0.50      | area=   all | maxDets= 20 ] = 0.915
Average Precision  (AP) @[ IoU=0.75      | area=   all | maxDets= 20 ] = 0.804
Average Precision  (AP) @[ IoU=0.50:0.95 | area=medium | maxDets= 20 ] = 0.697
Average Precision  (AP) @[ IoU=0.50:0.95 | area= large | maxDets= 20 ] = 0.765
Average Recall     (AR) @[ IoU=0.50:0.95 | area=   all | maxDets= 20 ] = 0.756
Average Recall     (AR) @[ IoU=0.50      | area=   all | maxDets= 20 ] = 0.930
Average Recall     (AR) @[ IoU=0.75      | area=   all | maxDets= 20 ] = 0.823
Average Recall     (AR) @[ IoU=0.50:0.95 | area=medium | maxDets= 20 ] = 0.723
Average Recall     (AR) @[ IoU=0.50:0.95 | area= large | maxDets= 20 ] = 0.804

Arch
AP
Ap .5
AP .75
AP (M)
AP (L)
AR
AR .5
AR .75
AR (M)
AR (L)

256x192_pose_resnet_50_d256d256d256
0.724
0.915
0.804
0.697
0.765
0.756
0.930
0.823
0.723
0.804

I download all pretrained models from google drive and run command below
python3 pose_estimation/valid.py --cfg experiments/coco/resnet50/256x192_d256x3_adam_lr1e-3.yaml --flip-test --model-file models/pytorch/pose_coco/pose_resnet_50_256x192.pth.tar
Is there any update of model or weight?

got it! after i got this result, i downloaded a person detector's result and got same result.
Maybe there is a cache of detector's bbox generated by GT somewhere.
Thanks!


Error while pulling latest image from docker hub

$ docker run --rm -p 7000:8080 \
  -v /home/octodi/caido/projects:/home/caido/.local/share/caido caido:latest
✔ docker.io/library/caido:latest
Trying to pull docker.io/library/caido:latest...
Error: initializing source docker://caido:latest: Requesting bearer token: invalid status code from registry 500 (Internal Server Error)

Previously it was working for 0.28.0

Now it's working

It was probably an issue on dockerhub, we should publish it to another registry too thanks for raising!


openjdk 8, R 3.2.2, and compile cleanup

Just an update to versions and fixing some out-of-date references.

Yes, this should be better. Please accept it

+1


Add support for highlight-indentation-mode

More information

I hope this looks good to you

Wow that was fast! Thank you :+1:


Add startTime to the Traceflow Status

The startTime is used to determine if a Traceflow has timed out and
should be reported as failed.
Until now we were relying on the CreationTimestamp set by the
kube-apiserver. However, by chance, I was testing Traceflow on a cluster
with a clock skew between the control plane Node (running the
kube-apiserver) and the worker Node running the
antrea-controller. Because of the clock skew, each Traceflow request was
tagged as failed as soon as I created it (with reason timeout). It took
me a while to figure out the reason.
By introducing the startTime field (set & used by the
antrea-controller), we avoid the possibility of such issues. If
startTime is not available for any reason, we fall back to the
CreationTimestamp.
This API change is backwards-compatible.
Signed-off-by: Antonin Bas<EMAIL_ADDRESS>

Codecov Report

Merging #2952 (571d38f) into main (6d9230b) will decrease coverage by 12.13%.
The diff coverage is 58.33%.

@@             Coverage Diff             @@
##             main    #2952       +/-   ##
===========================================
- Coverage   52.68%   40.54%   -12.14%
===========================================
  Files         283      158      -125
  Lines       23822    19968     -3854
===========================================
- Hits        12551     8097     -4454
- Misses       9885    11098     +1213
+ Partials     1386      773      -613

Flag
Coverage Δ

kind-e2e-tests
?

unit-tests
40.54% <58.33%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/controller/traceflow/controller.go
67.20% <58.33%> (-2.46%)
:arrow_down:

pkg/ovs/openflow/default.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/util/runtime/runtime.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/agent/cniserver/pod_configuration_linux.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/ovs/openflow/logs.go
9.52% <0.00%> (-90.48%)
:arrow_down:

pkg/apis/controlplane/register.go
0.00% <0.00%> (-90.00%)
:arrow_down:

pkg/agent/nodeportlocal/k8s/annotations.go
0.00% <0.00%> (-83.88%)
:arrow_down:

pkg/agent/agent_linux.go
0.00% <0.00%> (-80.00%)
:arrow_down:

pkg/agent/client.go
0.00% <0.00%> (-77.42%)
:arrow_down:

pkg/ovs/ovsconfig/ovs_client_linux.go
0.00% <0.00%> (-76.93%)
:arrow_down:

... and 206 more

/test-all
@wenqiq This may be the reason why Traceflow failed immediately in your testbed. You can check if the clock on controlplane node is at least 10s sooner than the clock on the Node antrea-controller runs.

/test-integration

It seems you forgot to update generated code.
diff --git a/pkg/apis/crd/v1alpha1/zz_generated.deepcopy.go b/pkg/apis/crd/v1alpha1/zz_generated.deepcopy.go
index a2a892fd..435977f4 100644
--- a/pkg/apis/crd/v1alpha1/zz_generated.deepcopy.go
+++ b/pkg/apis/crd/v1alpha1/zz_generated.deepcopy.go
@@ -732,6 +732,7 @@ func (in *TraceflowSpec) DeepCopy() *TraceflowSpec {
 // DeepCopyInto is an autogenerated deepcopy function, copying the receiver, writing into out. in must be non-nil.
 func (in *TraceflowStatus) DeepCopyInto(out *TraceflowStatus) {
        *out = *in
+       in.StartTime.DeepCopyInto(&out.StartTime)
        if in.Results != nil {
                in, out := &in.Results, &out.Results
                *out = make([]NodeResult, len(*in))

I think that other people using the Vagrant-based cluster may experience the same issue if they keep it running for a long time.
@tnqn thanks for the reminder, I updated the generated code

/test-all

/test-e2e
/test-networkpolicy

@wenqiq This may be the reason why Traceflow failed immediately in your testbed. You can check if the clock on controlplane node is at least 10s sooner than the clock on the Node antrea-controller runs.

Thanks for this information. I will take a look at it. Related issue #2944

@wenqiq #2944 is not caused by this. I meant the issue when we used "antctl traceflow" to debug connection issue, which failed immediately with Timeout error.

@wenqiq #2944 is not caused by this. I meant the issue when we used "antctl traceflow" to debug connection issue, which failed immediately with Timeout error.

Thanks, I got it now.

@wenqiq This may be the reason why Traceflow failed immediately in your testbed. You can check if the clock on controlplane node is at least 10s sooner than the clock on the Node antrea-controller runs.

Yes, you are right. The clock on controlplane node is at least 19s sooner than the clock on the Node antrea-controller runs.
The clock on controlplane node:
[core@sunq-antrea-scale-01-6w6g6-master-0 ~]$ date
Fri Nov  5 07:18:05 UTC 2021

The Node antrea-controller runs:
[core@sunq-antrea-scale-01-6w6g6-worker-z22ws ~]$ date
Fri Nov  5 07:18:24 UTC 2021

/test-e2e

2 Traceflow tests are failing with this change, I am investigating the failures
            --- FAIL: TestTraceflow/testTraceflowIntraNode/traceflowGroupTest/hostNetworkSrcPodIPv4 (15.02s)
            --- FAIL: TestTraceflow/testTraceflowIntraNode/traceflowGroupTest/nonExistingSrcPodIPv4 (15.03s)

/test-all

/test-all

@tnqn could you please review the last commit? I had to make a change in order to support K8s versions older than 1.20.

/test-integration


python310Packages.datetime: 5.1 -> 5.2

Diff: https://github.com/zopefoundation/datetime/compare/refs/tags/5.1...5.2
Changelog: https://github.com/zopefoundation/DateTime/releases/tag/5.2
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 249633 run on x86_64-linux 1

8 packages built:

python310Packages.datetime
python310Packages.datetime.dist
python310Packages.finvizfinance
python310Packages.finvizfinance.dist
python311Packages.datetime
python311Packages.datetime.dist
python311Packages.finvizfinance
python311Packages.finvizfinance.dist


sample_multinomial crashes on vector input

Note: Providing complete information in the most concise form is the best way to get help. This issue template serves as the checklist for essential information to most of the technical issues and bug reports. For non-technical issues and feature requests, feel free to present the information in what you believe is the best form.
For Q & A and discussion, please start a discussion thread at https://discuss.mxnet.io
Description
sample_multinomial / random.multinomial crashes when input probability is a vector.  @piiswrong
Environment info (Required)
Deep Learning AMI Ubunut
Package used (Python/R/Scala/Julia): python
(I'm using ...)
Build info (Required if built from source)
Compiler (gcc/clang/mingw/visual studio):
MXNet commit hash: 41394a448a92efbe7704fe21c48a8504fd8d3edc
(Paste the output of git rev-parse HEAD here.)
Build config:
(Paste the content of config.mk, or the build command.)
cp make/config.mk .
echo "USE_BLAS=openblas" >>config.mk
echo "ADD_CFLAGS += -I/usr/include/openblas" >>config.mk
echo "USE_CUDA=1" >>config.mk
echo "USE_CUDA_PATH=/usr/local/cuda" >>config.mk
echo "USE_CUDNN=1" >>config.mk

Error Message:
(Paste the complete error message, including stack trace.)
Minimum reproducible example
(If you are using your own code, please provide a short script that reproduces the error. Otherwise, please provide link to the existing example.)
>>> import mxnet as mx
>>> prob = mx.nd.ones((3,)) / 3
>>> prob

[ 0.33333334  0.33333334  0.33333334]
<NDArray 3 @cpu(0)>
>>> mx.nd.sample_multinomial(prob, shape=(25), get_prob=True)
[
[1 1 2 2 1 2 1 2 1 1 1 1 1 0 2 0 2 0 1 1 2 2 1 1 1]
<NDArray 25 @cpu(0)>,
-1.0986123085
<NDArray  @cpu(0)>]
>>> mx.nd.sample_multinomial(prob, shape=(25), get_prob=True)
*** Error in `python': free(): invalid next size (fast): 0x00007f8700004db0 ***
Bus error (core dumped)

Steps to reproduce
(Paste the commands you ran that produced the error.)

What have you tried to solve it?

These are deprecated. use mx.nd.random.multinomial now.
We should fix the document

Also core dump if mx.nd.random.multinomial is used


feat: add ability to pre release

Problem
Cannot test intermediate changes before release.
Solution
Add pre-release
Notes

Resolves #1543

@fryorcraken are you ok with this PR?
I think you'll be spammed now on npm RC publishes

@fryorcraken are you ok with this PR?
I think you'll be spammed now on npm RC published

I'll do email rules


Template generator update

Feature template generator refactored to include data paths from template schema to differentiate model fields

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/371


Example get route param

How to get param from router
<RouterLink to="/doc/123">Document</RouterLink>
How to get param document_id in DocumentDetail component
export default {
  mode: 'history',
  routes: {
    '/': Home,
    '/doc': Document,
    '/doc/:document_id':DocumentDetail,
    default: NotFound
  }
}

Thank you.

@mahadoang Not sure if this is the official way to do it but you can get the param using this.options.data.path.p in your DocumentDetail component from your example. Or you can inspect this.options.data.path to get the path info. Hope that helps.


The main program isn't executable on Linux by default

I have to use chmod to set it as executable after I download the package from here (Linux x64 version) and extracted the .tar.gz package:
kevin@Arch ~/D/Hozz-linux-x64> ls
content_shell.pak  Hozz  icudtl.dat  libgcrypt.so.11  libnode.so  locales/  natives_blob.bin  resources/
kevin@Arch ~/D/Hozz-linux-x64> chmod 755 Hozz

Thanks for pointing it out

Ahhh, my bad. Shouldn't use 7z X [...].tar.gz instead of tar xzf [...].tar.gz.


fix: removed console.log

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adding Integration tests

cc @Minishlink
This is a clean start of the integration tests (Trying to minimize any issues with your other PR)

Thank you very much!


fix the affinity value names

fixes: https://github.com/kiali/kiali/issues/3921

This needs a review.

To test this, you just have to run the server helm chart with a custom values.yaml that sets deployment.affinity.pod and deployment.affinity.pod_anti and make sure that those settings go in the correct spot in the server deployment. You don't even have to actually deploy it - you can use "helm template" and just look at the resultant Deployment yaml and check for correctness.

This looks good. Tests are OK.
Run make build-helm-charts to produce the new helm charts. Then run the tests like this:
helm template \
  kiali-server \
  -f values.yaml \
  -n istio-system \
  _output/charts/kiali-server-1.34.0-SNAPSHOT.tgz  > results.txt

With values.yaml set to:

deployment:
  affinity:
    node:
      someKey1: someValue1

the results.txt show this in Deployment:
      affinity:
        nodeAffinity:
          someKey1: someValue1

With values.yaml set to:

deployment:
  affinity:
    node:
      someKey1: someValue1
    pod:
      someKey2: someValue2
    pod_anti:
      someKey3: someValue3

the results.txt show this in Deployment:
      affinity:
        nodeAffinity:
          someKey1: someValue1
        podAffinity:
          someKey2: someValue2
        podAntiAffinity:
          someKey3: someValue3

this is all good - simple change and test shows it producing the correct yaml now.


[LUCI] We should test packaging on master without uploading

Today we only run packaging on dev/beta/stable.  We should test it on master to make sure the script gets exercised.
/cc @gspencergoog

@christopherfujino is it possible to run the packaging script in dry-run mode?

@dnfield what exactly would you like to catch? regressions in the script?
Sort of related:

https://github.com/flutter/flutter/issues/61751 (open)
https://github.com/flutter/flutter/issues/64209 (closed)

Oh, I see that this was opened a while ago. My current plans are to migrate this script into the conductor, and then add integration tests there.

@christopherfujino can we close this issue now that we have the conductor tool ready?

\cc @sealesj this is related to the work being done with packages.


NPE when package of interface is empty.

[x] I have searched the issues of this repository and believe that this is not a duplicate.
[x] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.0

Steps to reproduce this issue

Interface without package.

Export service.

serviceConfig.setInterface(HelloService.class.getName());
serviceConfig.setRef(new HelloServiceImpl());

Expected Result
Export service.
Actual Result
Catch NPE when export service.
java.lang.NullPointerException
	at com.alibaba.dubbo.common.Version.getVersion(Version.java:127)
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrlsFor1Protocol(ServiceConfig.java:440)
	at com.alibaba.dubbo.config.ServiceConfig.doExportUrls(ServiceConfig.java:358)
	at com.alibaba.dubbo.config.ServiceConfig.doExport(ServiceConfig.java:317)

Does the picture have problems ? The interface is in package "com".


Update release-notes with latest output of the release-notes tool

I re-ran the release-notes tool during the 1.7 release and it picked up the following change.

@irbekrm This is the change you made to that PR release-note but I removed the Bugfix prefix since it does seem like feature.

@wallrj I changed it from feature to bugfix because it was not actually a new feature

It's probably not super-important, but marking it as bugfix would make it easier to understand in which release this got fixed (like in case of the person who commented on that PR and had ran into the bug with 1.6.1)

I changed it back to bugfix. The problem was that the PR originally had both kind/feature and kind/bug so the release-notes tool chose feature. PTAL

/lgtm

/unhold

/hold cancel


With admission-webhook, nsm-coredns assumes kubedns service IP is <IP_ADDRESS>

Expected Behavior

Pod use of kubedns should still function, regardless of injection of nsm-coredns sidecar.
Current Behavior

For k8s clusters with service CIDRs != <IP_ADDRESS>/16, the admission webhook will inject the nsm-coredns sidecar with invalid config for the kubedns mapping.  This breaks the pod's ability to do DNS queries for other kubernetes pods/services.
Failure Information (for bugs)

Steps to Reproduce

k8s cluster with service CIDR != <IP_ADDRESS>/16
install NSM with the admission-webhook, ie. via helm.
create network services, NSEs
bring up NSC pod
workload does DNS lookup and it doesn't work

Context

k8s cluster with service CIDR != <IP_ADDRESS>/16
NSM install with admission-webhook to inject sidecars in NSCs

Failure Logs

@tiswanso can you please test the workaround what I talked about on nsm-dev slack channel?
Workaround is

Implement function handler, for example
https://slack-redir.net/link?url=https%3A%2F%2Fgithub.com%2Fnetworkservicemesh%2Fnetworkservicemesh%2Fblob%2Fmaster%2Ftest%2Fapplications%2Fcmd%2Ficmp-responder-nse%2Fmain.go%23L108
And put into dnscontext your configs.
Add your handler to your endpoint list, for example https://github.com/networkservicemesh/networkservicemesh/blob/master/test/applications/cmd/icmp-responder-nse/main.go#L74

Potential work-arounds and evaluations
nsm-coredns env var UPDATE_API_DEFAULT_DNS_SERVER
Evaluation
This isn't usable with the nsm-admission-webhook as it handles all of the pod's settings for the nsm-coredns container and it doesn't set UPDATE_API_DEFAULT_DNS_SERVER
coredns config via configmap
Evaluation
This isn't usable with the nsm-admission-webhook as it handles all of the pod's settings for the nsm-coredns container and it doesn't set the container up to mount the coredns config file from a configmap.
NSE setting DNS settings in connection context
Evaluation
This should work to set nameservers that workloads could use for the network/s connected via the NSE.  This is unlikely to be a setup that would be usable to restore the kubedns functionality for reaching the local k8s cluster's pods via service names.

@denis-tingajkin -- thanks for the info.  I will use the pointer for my own NSE but that work-around only works if you're the developer of the NSEs and it requires knowledge of the exact k8s env setup the NSE and clients are deployed in.

@tiswanso yes sure, you are right. This just for test :)

@tiswanso Hello, can you please retest the Issue with the last changes?