About the MSF in apollo.

Hi,
I've learned this paper relevant to the MSF implemented in Apollo. MSF is a localization scheme that contains many components and possible combinations, why this paper only select these specific methods for its implementation in Apollo?
Regards,
HY

@hongyi-zhao , Thanks for your question. As you said, more sensors integrated into MSF could improve the reliability and availability for the whole solution, and we do now (2020) employ more sensors like cameras to the list. But dated back to 2018,  due to the limited computing resource and available sensor suit, we only chose the RTK/LiDAR/IMU combinations. You can follow our latest progress on vision in paper(DA4AD: End-to-end Deep Attention Aware Features Aided Visual Localization for Autonomous Driving) for more details. Thanks again.

@renlancai I find this paper here according to your guidance. But it seems that you are not in the list of authors. Are you a member of the research group which published this paper?

@hongyi-zhao The paper @renlancai mentioned proposed a camera based localization module which can add to MSF. This camera based localization module has the same input/output as the LiDAR localization module, so it's easy to be integrated into MSF. Back to your original question, in 2018, due to the limited computing resource and available sensor suit, we only chose the RTK/LiDAR/IMU combinations to build the MSF scheme.


Unexpected 'Fragment cannot be spread' error

Hi,
I am trying to use interfaces in my query using morpheus client. My gql file looks something like (excluded some excessive detail. Let me know if you want my full file):
"""
An object with an ID.
"""
interface Node {
  """
  ID of the object.
  """
  id: ID!
}

"""
Represents a Git object.
"""
interface GitObject {
  id: ID!
}

"""
Represents a Git reference.
"""
type Ref implements Node {
  id: ID!

  """
  The object the ref points to.
  """
  target: GitObject!
}

type Commit implements GitObject & Node {

  id: ID!

  """
  Authorship details of the commit.
  """
  author: String
}

type Tree implements GitObject & Node {
  """
  A list of tree entries.
  """
  treeName: String

  id: ID!
}

And my query looks something like:
defineByDocumentFile
  "../resource/minimal-github.graphql"
  [gql|
    query FetchRepoHeadCommit ($repoOwner: String!, $repoName: String!) {
      repository(name: $repoName, owner: $repoOwner) {
        defaultBranchRef {
          target {
            ... on Commit {
               author
            }
          }
        }
      }
    }
  |]

This fails with Fragment cannot be spread here as objects of type \"GitObject\" can never be of type \"Commit\. Changing   target: GitObject! to target: Commit! makes it work. This confuses me as I have type Commit implements GitObject.
My expectation is that this should work based on 2 from https://github.com/morpheusgraphql/morpheus-graphql#interface . Am I missing something?

Thanks, you are right.
Query validation was written bevore we supported "interfaces", so i forgot to update it too.
I will fix it

@AlistairB i started fixin it in  #495

@AlistairB please try it with new master

Unfortunately I am still getting the same error building with morpheus based on commit https://github.com/morpheusgraphql/morpheus-graphql/commit/57de5110e95b834fb92aba393757923273241328 (current head on master).

ooh. that weird i wrote tests for it. can you share full schema?

and query with fragment

If you clone https://github.com/AlistairB/morpheus-repro and stack build it should reproduce the issue. It will only compile if you change https://github.com/AlistairB/morpheus-repro/blob/master/minimal-github.graphql#L89 to target: Commit!.

so, if we have schema.
interface GitObject {
  id: ID!
}

type Commit implements GitObject & Node {
  id: ID!
  author: String
}

type Query  {
  target: GitObject!
}

your query would look like:
{
   target {
    ... on Commit {
         author
         }
   }
}

and would be invalid. as long target guarantees to provide fields defined by GitObject nut by Commit.
if we had
so, if we have schema where target has concrete type Commit.
interface GitObject {
  id: ID!
}

type Commit implements GitObject & Node {
  id: ID!
  author: String
}

type Query  {
  target: Commit!
}

we can query on it GitObject and Commit.
{
   t1: target {
    ... on Commit {
         author
         }
   }
   t2: target {
    ... on GitObject {
         author
         }
   }
}

Hmm, I'm not sure if I understand. My understanding is that you can use the spread operator to conditionally get data IF the type matches.
For example using https://developer.github.com/v4/explorer/
query {
  repository(owner: "facebook", name: "react") {
    defaultBranchRef {
      target {
        id
        ... on Commit {
          author {
            name
          }
        }
      }
    }
  }
}

will fetch all this data, as target is in fact a Commit.
On the other hand:
query {
  repository(owner: "facebook", name: "react") {
    defaultBranchRef {
      target {
        id
        ... on Blob {
          byteSize
        }
      }
    }
  }
}

Will only fetch the id, but will not return an error. This is because target: GitObject and type Blob implements GitObject, so it could be a Blob.
And you can combine them:
query {
  repository(owner: "facebook", name: "react") {
    defaultBranchRef {
      target {
        id
        ... on Commit {
          author {
            name
          }
        }
        ... on Blob {
          byteSize
        }
      }
    }
  }
}

In terms of the schema I am using, I have directly copied the bits I need from the official github public schema. See https://docs.github.com/en/graphql/overview/public-schema .
This query with the schema does work on github which makes me think it is valid?

okey.  may i got something wrong.  what you say looks like type casting.
i will read specifications and fix it.

@AlistairB can you check again , i fixed it #498

@AlistairB validation workded well bot there is some problem with type Generation that i am fixing in #499

@AlistairB now it should finally work

Thanks David! This is now working for most cases that I tested. The below is happy and works.
    query FetchRepoHeadCommit ($repoOwner: String!, $repoName: String!) {
      repository(name: $repoName, owner: $repoOwner) {
        defaultBranchRef {
          target {
            id
            ... on Commit {
              committedDate
            }
          }
        }
      }
    }

However, I get an error if I remove returning the id. eg.
    query FetchRepoHeadCommit ($repoOwner: String!, $repoName: String!) {
      repository(name: $repoName, owner: $repoOwner) {
        defaultBranchRef {
          target {
            ... on Commit {
              committedDate
            }
          }
        }
      }
    }

produces No Empty fields on \"RepositoryDefaultBranchRefTargetGitObject\". It seems that you must fetch something from the interface otherwise it errors. I have pushed a new commit demonstrating this failure to https://github.com/AlistairB/morpheus-repro
Possibly worth noting that I believe putting interface level fields inside the spread is also valid. eg.
    query FetchRepoHeadCommit ($repoOwner: String!, $repoName: String!) {
      repository(name: $repoName, owner: $repoOwner) {
        defaultBranchRef {
          target {
            ... on Commit {
              id
              committedDate
            }
          }
        }
      }
    }

I think this is working aside from the above error. Although, I don't think supporting this style is super important.

thanks @AlistairB.
i fixed it in #500

Awesome, now working! thanks!


Issue/fix memory leak

Description

Fixed memory leak introduced in #2787
Also added slots to FunctionUnit

Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

test run looks good!
https://jenkins.inmanta.com/job/integration-tests/job/compilerscaling/892/console

Processing this pull request

Merged into branches master in 0f2678b770668537ddef9f0a52a827a498ddfea7

Processing #2824.

Processing #2825.


refactor: immutable module graph during code generation

Summary

Test Plan

Require Documentation?

[ ] No
[ ] Yes, the corresponding rspack-website PR is __

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #5542

PR #5543   👈

This stack of pull requests is managed by Graphite.

!bench

!bench

!bench is useless since we don't enable newTreeshaking by default.

!bench

!bench is useless since we don't enable newTreeshaking by default.

Should I enable new tree shaking on acro-pro in my local repo and run benchmark on it ?

Should I enable new tree shaking on acro-pro in my local repo and run benchmark on it ?

You could have a try.

Should I enable new tree shaking on acro-pro in my local repo and run benchmark on it ?

You could have a try.

Currently the diffcases/acro-pro repo has enabled new tree shaking, benched on main branch and this pr, it seems that there is no significant performance regression:

main
pr

1
4.41
4.39

2
4.50
4.42

3
4.37
4.48

4
4.51
4.43

5
4.50
4.52

6
4.48
4.56

7
4.48
4.49

8
4.41
4.49

9
4.53
4.49

10
4.66
4.32

11
4.53
4.50

12
4.66
4.48

13
4.46
4.49

14
4.50
4.54

15
4.57
4.47

16
4.48
4.49

17
4.53
4.47

18
4.36
4.46

19
4.43
4.47

20
4.55
4.41

avg
4.496
4.4685


Duplicated contained type

I use Sourcery 0.13.1.
Using this template:
{% for subtype in type.TestForSourcery.containedTypes %}
  {{subtype.name}}
{% endfor %}

For this code:
struct TestForSourcery {
  struct InnerStruct {
    static let test = 5
  }
}

private extension TestForSourcery.InnerStruct {
 static var secondVar: Int { return 6 }
}

The output is just fine:
TestForSourcery.InnerStruct
But if I separate extension to another file, move private extension TestForSourcery.InnerStruct to any other file except one with definition, I have output duplicated:
            TestForSourcery.InnerStruct
            TestForSourcery.InnerStruct

Is it a bug? If not and it is expected behavior, is there a workaround?

fixed long ago


AVM-Review-PR

Description

Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[ ] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] I did run all  pre-commit checks

e2e test / testexamples fails here due to quota issues in the subscription where the example is being executed, they pass when run locally in a specified subscription with quota


Date field requires moment library (crashes)

value = moment(value).format("MMM. YYYY");

The moment.js library provides a nice way for formatting dates. The function was added during a manual merge without actually adding the library. So, if a bibtex entry has the date field it will crash unless the library is manually added to the html file.

Close 58720c1e19b5f6c4204dc94d9b60278559234bbf fixes this issue.


pyright not working

pyright is not working for my project... no autocompletion and LSP command not working
but lspShowAllServers says my pyright is running
var lspServers = [
    {
	    name: 'golang',
	    filetype: ['go', 'gomod'],
	    path: 'gopls',
	    args: ['serve'],
	    syncInit: true
    },
    {
	    name: 'python',
	    filetype: 'python',
	    path: 'pyright-langserver',
	    args: ['--stdio'],
    },
]

Found the issue. User error.

Can you describe how you fixed the problem, so that it will be useful for others? Thanks.

You need to have pythonPath set.

Could you indicate which version of Pyright you are using? I have tried version 1.1.378 without success. Additionally, it would be helpful to know whether you installed the npm or pip version of Pyright.
I am also curious about the role of the python.pythonPath in the initialization options. I don't see how adding it would make a difference in this context.
If you could share more details about how you resolved this issue, it would be useful for both me and the project.


make sure to update the data before stopping the state machine

There was a bug where if a state was marked as "End": true it would not capture the result of the Resource callback. This fixes the issue.

This addresses issue https://github.com/CityBaseInc/states_language/issues/6

@entone Thank you for the update. I had noticed that a resource that had any state that had "End": true it would not capture the result of the Resource callback. I found myself needing to complete all transformations before having a state with "End": true. I had wondered if this was by design.

It was not.
On Thu, Apr 2, 2020 at 12:27 PM Clifton McIntosh<EMAIL_ADDRESS>wrote:

@entone https://github.com/entone Thank you for the update. I had
noticed that a resource that had any state that had "End": true it would
not capture the result of the Resource callback. I found myself needing to
complete all transformations before having a state with "End": true. I
had wondered if this was by design.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CityBaseInc/states_language/pull/8#issuecomment-607984609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABGNLJ5R3GHEZFO2XETYJLRKTDH5ANCNFSM4L2OXT5A
.


Obsoletion request: 	GO:0016255    attachment of GPI anchor to protein

Please provide as much information as you can:

GO term ID and Label

GO:0016255    attachment of GPI anchor to protein

Reason for deprecation Put an x in the appropriate box:

[x] The reason for obsoletion is that this term represents a molecular function.

This term is represented by the MF
GO:0003923   GPI-anchor transamidase activity

"Replace by" term (ID and label)

GO:0006506 GPI anchor biosynthetic process

"Consider" term(s) (ID and label)
Suggestions for reannotation

Are there annotations to this term?

How many EXP:

Are there mappings and cross references to this term? (InterPro, Keywords; check QuickGO cross-references section)

Is this term in a subset? (check the AmiGO page for that term)

Any other information

Checklist for ontology editor
Check term usage and metadata in Protégé

[ ] check term usage in the ontology
[ ] check internal mappings: RHEA, EC, MetaCyc
[ ] check subset usage
[ ] check taxon constraints

Check annotations

[ ] create Annotation Review spreadsheet

Annotation Review template: https://docs.google.com/spreadsheets/d/1izV3q1jnq_Ybg5MJ53O_b5BCTkGtjl_Fi-cOg3-7eBE/edit#gid=0

Instructions: https://wiki.geneontology.org/Annotation_Review_Request

[ ] create annotation review ticket: https://github.com/geneontology/go-annotation/issues/new?assignees=&labels=annotation+review&template=annotation-review-for-obsoletion.md&title=Review+annotations+to+[INSERT+GO+TERM]
[ ] find external mappings (via IEAS), include in obsoletion notice
[ ] tag curators in Annotation Review ticket. Responsible annotator for each group: https://github.com/geneontology/go-site/blob/master/metadata/group-contacts.csv

Notification

[ ] create obsoletion announcement
[ ] announce to GO friends<EMAIL_ADDRESS>[ ] paste the text in the ontology ticket

@pgaudet  agreed single step.

proposed solution for this one is in
https://github.com/geneontology/go-ontology/issues/28227
(we keep this term, because it is post-anchor biosynthesis)


Make PDE model parameters compatible with SciML

Implement stuff defined in https://docs.sciml.ai/SciMLStructures/stable/ and add tests.

Duplicated due to Github server issues.


优化DB2 Driver的推断逻辑

1、推断Driver的逻辑不稳定, 应抽取方法给子类保留替换的机会
2、优化DB2 Driver的推断逻辑，参考自 https://www.cnblogs.com/lidg/articles/3588566.html

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 All committers have signed the CLA.


Follow up to CCR docs

Follow up for 11821
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please


fix errors on multiplayer file parsing

add missing params on multiplayer parsing to prevent errors

@tessig got there first but made the same two fixes and got the checker working again, would be good to get this merged


How can I load html downloaded page?

Does this
article.download()
equalivent to
article.html=html_downloaded
And later I can parse and get article text.

a = Article('')
a.set_html(html)
a.parse()
This was already mentionned in: #74

can be closed


[cmake] support packages that provide optional ros2 integration but do not require it by default

Many packages try to provide ros integration without making ros a requirement for other potential package users that do not or cannot support ros/ros2 for legacy, contractual, or application specific reasons. Ideally the new build system will make it as simple a process as possible to enable a package to support ROS2 messages/nodes while not requiring them. This means if a recommended layout is provided it is not required, and if ament isn't installed on the system CMake builds can still succeed, perhaps depending on a simple parameter or check for the presence of amant.
Thanks for considering this request!

Please describe the desired use case in more detail. Especially what are the goals and which parts can currently not yet be achieved.

Example libraries are:
GitHub.com/ahundt/grl
https://github.com/jhu-cisst/cisst
One specific example from above is that I shouldn't need to write a hanky findros.cmake, ROS should provide standard cmake 3.x config.cmake script support where libraries install their own configuration tools. See cmake 3.x documentation for details, though note I believe 3.2 or higher is more ideal due to fixes of string handling and actual cmake code bugs in earlier 3.0 and 3.1.
I just chose them because I've done development for them. I'm specifically talking about the "ROS wrapper" case. http://wiki.ros.org/navigation/ROS_Wrappers
Essentially, I would like if there was a well thought through approach making it easy to put a ROS wrapper into libraries that don't use ROS now, without breaking existing use cases (in particular the build of libraries) when ROS is not available.
Also making the reverse easy is another specific case. I've encountered a number of libraries that really only use the catkin build system and no heavy ROS dependencies but untangling the cmake to build when ROS isn't present could be made much easier. Here are two specific libraries where that is the case:
https://gitlab.mech.kuleuven.be/rob-dsl/geometric-relations-semantics.git
https://gitlab.mech.kuleuven.be/rob-dsl/pose_twist_graph.git

https://github.com/ahundt/grl

One specific example from above is that I shouldn't need to write a hanky findros.cmake

I assume you're talking about: https://github.com/ahundt/grl/blob/master/config/FindROS.cmake? (please link directly to files when you reference them so others don't have to go searching) If so, I'd say that file doesn't exactly make sense because ROS is not a single entity you can find_package and that is by design. Each ROS 1 package, that is a catkin package, exposes itself as a CMake project and provides a pkg-config file. The file you referenced isn't necessary as far as I can tell and would only work on Ubuntu and only if ROS was installed to /opt/ros. That is admittedly the most common case, but it is by far not the only way people use ROS.
If you were to source a the setup.bash file present in any of the /opt/ros/* folders then you would just be able to do things like find_package(roscpp REQUIRED) and target_link_libraries(roscpp_LIBRARIES). The setup file is required because we install to /opt to allow multiple versions to be installed at the same time more easily.
In the latest versions of Ubuntu and Debian, you don't even need to source the setup file for many things because there are ROS packages upstream which are installed to /usr. However, I'll caution you that those packages will conflict with the ones installed from our server (http://packages.ros.org/ros/ubuntu/) because of the version of some common dependencies which are out of our control, see: http://wiki.ros.org/UpstreamPackages Also the packages available in upstream will be older and there will be less of them, but it might meet your needs without having to worry about adding our repositories or sourcing our setup files.
You might want to have a look at https://github.com/gerkey/ros1_external_use and http://lists.ros.org/pipermail/ros-users/2016-February/069867.html for a simple example of how to use ROS as if it were a small collection of CMake projects, either using CMake or Make.
For ROS 2, this story doesn't change, because any ament package that uses CMake will provide a standard CMake <package>Config.cmake and <package>Config-version.cmake file (just like catkin and ROS 1).

Essentially, I would like if there was a well thought through approach making it easy to put a ROS wrapper into libraries that don't use ROS now, without breaking existing use cases (in particular the build of libraries) when ROS is not available.

I think it is a fair point that this is an under-advertised and under-documented use case, but it is completely possible as-is. Again, I think you'll find https://github.com/gerkey/ros1_external_use very insightful in that case. We're working on addressing this by improving documentation and polishing off rough edges.

Also making the reverse easy is another specific case. I've encountered a number of libraries that really only use the catkin build system and no heavy ROS dependencies but untangling the cmake to build when ROS isn't present could be made much easier. Here are two specific libraries where that is the case:

We encourage this, as you linked to http://wiki.ros.org/navigation/ROS_Wrappers. We have done this for many of the built-in robot capabilities for ROS. I think it's a hard case to make to grad students that aren't using their stuff outside of ROS and don't have time to worry about it otherwise. This is unfortunate, but it is relatively easy to convert from catkin to plain CMake if the package doesn't use ROS stuff. For example, my serial library is built with catkin: https://github.com/wjwwood/serial but it is totally trivial to convert it to CMake or embed it directly into another CMake project: https://github.com/wjwwood/serial/issues/52#issuecomment-28848337
Other examples where people have done "the right thing" and written a ROS agnostic library and wrapped it in ROS (or taken a ROS agnostic library and written a separate ROS wrapper rather than extend the library itself to optionally support ROS):

(non-ROS and ROS packages)
stage and stage_ros
gazebo and gazebo_ros
pcl and pcl_ros
opencv and vision_opencv
libsegwayrmp and segway_rmp (my packages)
gmapping and slam_gmapping
many others...

Also, we mention this as the preferred strategy in the wiki.
From http://wiki.ros.org/ROS/Introduction#Goals:

ROS-agnostic libraries: the preferred development model is to write ROS-agnostic libraries with clean functional interfaces.

Obviously not all of ROS hits the mark, but people are trying to do this when they can.

https://gitlab.mech.kuleuven.be/rob-dsl/geometric-relations-semantics.git
https://gitlab.mech.kuleuven.be/rob-dsl/pose_twist_graph.git

Both of those libraries (at least on the default branch) are rosbuild packages, which has all but been replaced at this point. It was replaced in part because of the issues you're talking about, so you're preaching to the choir. So while I agree with you that those packages would be hard to integrate with, I don't think that using them as examples helps to support your case in this issue.
I appreciate your interest and feedback. However, I think this issue has been opened against the wrong repository as none of the things you linked to as examples are ROS 2 or ament packages. So without looking at ament you can't possibly know if the criticisms apply.
I'm going to close this since I do not believe there is anything that we need to do to satisfy the request in a technical sense. We're aware of the need for documentation of this kind of use of ROS, but we're not to that point with ROS 2 yet (we'll keep it in mind though). Feel free to continue to discuss here and we can reopen the issue if appropriate.

Thanks for your consideration and listening to my feedback! What would be the right place to open issues with ROS 1 which should be considered in ROS 2?

I will also definitely take a look at some of those examples you recommend. Is there a centralized location with "best of" (i.e. very good nontrivial full implementations of functionality that are recommended as a reference) and "best practice" information I can use as a reference and send to others?

For general ROS 2 related tickets which are not specific for a package please use https://github.com/ros2/ros2
The ros2 org unit contains two repositories with demos and examples. They will be a good starting point beside the tutorials in the wiki.


Error: dark mode button animation does not work

Describe the Error
The dark mode button in the Navigation Menu does not toggle or change color and logo as it turns on and off.
Expected behavior
The button should toggle back and forth, change color and logo according to whether it is now in light mode or dark mode.
Screenshots

I will also change the text UnLiked to Unliked as it should be written in proper english.

you can assign this task to me...


Update README title for consistency

Description

Updated README title from "WinUI 3" to "WinUI".
Motivation and Context

The README itself uses "WinUI" instead of "WinUI 3".

I think - even though the main text uses mostly "WinUI", it's short for "WinUI 3". So I think having a more explicit title isn't bad?

This PR has become old. Closing it.


Tab level permissions

Hi Volkan,
Is it possible to have tab level permissions?

its possible. handle tab visibility on script side permission control. If required, check permission from repository or endpoint too.

@VictorTomaili thanks for the quick reply! Is it possible to make them visible but not editable? Tried adding just readpermission on the tabbed row but it still allows me to edit it, as a last resort I will do it repository/grid level..?

Also may I please get an example of the script side permission control?

there is methot for check permission. You can check edit permission for disable edit mod.
https://github.com/volkanceylan/Serene/blob/0ff1ea9e9ab3f8003a456b585cf6b2b3934bf947/Serene/Serene.Web/Modules/Administration/User/Authentication/Authorization.ts#L10

@VictorTomaili thanks!! Did something like
protected getPropertyItems() {             let items = super.getPropertyItems();             let per = Authorization.userDefinition.Permissions;             if (Authorization.hasPermission("ServiceProviders:ServiceProviders:Read"))                 items = items.filter(x => x.readOnly = true);// != ServiceProvidersRow.Fields.ServiceProviderTypeId);             return items;


Fix holland backup monitor for greenfield

This fix will create a holland backup when not present.
In addition, the holland backup monitor is checking for one
successful backup within 48 hours in order to go into an
OK state. This fixes specifically the greenfield
installation where no backup is present from 'yesterday'
Closes-Bug: #2048

This change looks good to me. I'll circle back around to this PR once the gate jobs finish successfully

This will also need a backport to the newton-14.0 branch.

@alextricity25 https://github.com/rcbops/rpc-openstack/pull/2070


[Spec] Disable mqtt option for DA products

This patch disables the mqtt option in the case of DA products.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #209. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Fix the Display impl for Fp* instances

Description

This change allows the output of the derived ToString impl to be used with
the from_str functions.  Previously, the Display impl output hex.
closes: #320

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[x] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md (I did not do this, to avoid merge conflicts while rebasing)
[ ] Re-reviewed Files changed in the Github PR explorer

@hdevalence That makes sense to me. I've added a test which verifies your change - could you please allow edits on this PR and I'll just add my commit right here?
In addition we could implement UpperHex to still preserve the option to output hex.

@hdevalence That makes sense to me. I've added a test which verifies your change - could you please allow edits on this PR and I'll just add my commit right here?

@mmagician Oops! sorry about that .... I actually don't see the "allow edits from maintainers" box, mysteriously? This page says it should be a checkbox in the sidebar, but it seems to be missing.

I'll try to figure this out but in the meantime, if you point me at the commit you made, I can cherry-pick it into the branch.

In addition we could implement UpperHex to still preserve the option to output hex.

Sounds reasonable. Would you like to do that as part of this PR, or as a follow-on issue?
This is a bit bikesheddy, so I don't want to waste time on it, but would it make sense to align the UpperHex /  LowerHex impls to the canonical serialization formats (e.g., make them print the hex encoding of the canonical serialization?)

I think Henry would not see the box to "allow edits from maintainers"---organization repos have more restricted permission settings.
(I do recommend submitting a PR from personal repos.)

This is a bit bikesheddy, so I don't want to waste time on it, but would it make sense to align the UpperHex / LowerHex impls to the canonical serialization formats (e.g., make them print the hex encoding of the canonical serialization?)

I guess this depends on the purported use case for UpperHex/LowerHex: are they intended to be machine-friendly serializations? Or are they just human-friendly representations?

I guess this depends on the purported use case for UpperHex/LowerHex: are they intended to be machine-friendly serializations? Or are they just human-friendly representations?

IMO there's not a clear distinction here -- as a human using the library, it's convenient if the hex display is something I can decode as bytes and parse using the serializer, since it means I can use it to generate test vectors, etc.  I'm not sure what a human-friendly hex representation would be, a decimal integer is pretty human-friendly (can be pasted into Sage, is a number, etc), but usually hex data is already intended for machine interactions.

I think Henry would not see the box to "allow edits from maintainers"---organization repos have more restricted permission settings.
(I do recommend submitting a PR from personal repos.)

Ah, apparently there is no way to enable this setting for organization repos, which is deeply unfortunate -- we'd like to use our fork to accumulate changes, so that we're not pulling upstream maintainers into a development cycle for a product they're not part of.

Ah, apparently there is no way to enable this setting for organization repos, which is deeply unfortunate -- we'd like to use our fork to accumulate changes, so that we're not asking upstream maintainers to work around our development cycle.

Can you give arkworks-rs/algebra access to the penumbra fork? Then maintainers of this repo can push to your fork

Ah, apparently there is no way to enable this setting for organization repos, which is deeply unfortunate -- we'd like to use our fork to accumulate changes, so that we're not asking upstream maintainers to work around our development cycle.

Can you give arkworks-rs/algebra access to the penumbra fork? Then maintainers of this repo can push to your fork

I tried setting this as a team, but I wasn't able to. I can try to add people individually but the easiest thing might be to just point at commits that I can cherry-pick.

Hello, I am interested in the feature implemented in this PR (which fixes https://github.com/arkworks-rs/algebra/issues/320) and I am wondering whether this would eventually be merged.
I understand that the function which is modified by this PR was modified very much a few days ago in master. It is now https://github.com/arkworks-rs/algebra/blob/08c4cdb5137591e27171f7aea2543b0602ad27d9/ff/src/fields/models/fp/mod.rs#L720-L727
What is preventing this function to be replaced to output something which can be used with from_str?


Running zulu init script breaks autocompletion with zsh 5.7.1 and oh-my-zsh

Running the initialization script will prompt the following error message:
zulu init ✔ Switched to Zulu master _zulu_init_setup_completion:9: compinit: function definition file not found _zulu_init:61: promptinit: function definition file not found zsh: prompt: command not found...
then autocompletion fails with
expand-or-complete-with-indicator:3: _main_complete: function definition file not found

Same error for me using zulu without oh-my-zsh.

Same here after upgrading my macbook to 10.15 (Catalina).


Change signoff check image to slim-buster

Signed-off-by: Peixin Li<EMAIL_ADDRESS>alpine image is failing to build required env after recent updates

Going to force merge this to fix


Source Code Preview Component

usage:
<Preview>
  <ButtonColors />
</Preview>

<Preview markup={`
  <Button color={color}>Color Example</Button>
`}
  script={`
    let color = red;\n$: classes= "btn-" + color;\n
`}
  style={`
    .btn { background-color: red; }
`}>
  <ButtonColors/>

</Preview>

or simpler (similar to storybook) usage:

<Preview component={ButtonColors} />

or from file url:
<Preview src="./example/button-colors.svelte" />

@pournasserian please check above comment and let me know did I understand correctly? and please share your suggestions with me.
thanks

@TheHadiAhmadi the first scenario is correct. We may extend the second one later. Let's try to implement the first one and see how it will be. Thanks

@TheHadiAhmadi it should be something like this:

<Preview markup={`
  <Button color={color}>Color Example</Button>
`}
  script={`

<Preview src="../lib/components/Counter.svelte">
  <Counter />
</Preview>

is it okay to have a src prop to make it easier to search for Component's file?

<Preview src="../lib/components/Counter.svelte">
  <Counter />
</Preview>

I don't think you need the source file path again. You will have access to the path during preprocessing.

it would be hard if we import components from some index file
// we don't know ButtonColors where is located
import {ButtonColors, ButtonOutline, ButtonActive, ButtonDefault} from './button/examples'

it would be hard if we import components from some index file
// we don't know ButtonColors where is located
import {ButtonColors, ButtonOutline, ButtonActive, ButtonDefault} from './button/examples'

Svelte parser will provide that (I think)

No We cannot parse

    {#if framed}

          Content loaded in an iframe

    {/if}

      {#if framed}

      {:else}
        <slot />
      {/if}

        {@html code}

        {codeRaw}


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.15.8",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=58f15f5ae7786c824868f3a7e093859b74669ce7"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "58f15f5ae7786c824868f3a7e093859b74669ce7",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "HID: bigbenff: prevent null pointer dereference\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.8 by commit 58f15f5ae7786c824868f3a7e093859b74669ce7. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002584


Improve delete label to not miss confuse users on what is being deleted

I think we should cancel this for the first release. Let's see how our users will react to delete key instead of overthinking this label for now. WDYT @JPedroBorges ?

Agread 👍🏻


removed tss-react from cord-field -<PHONE_NUMBER>

┆Issue is synchronized with this Monday item by Unito
┆Link To Item: https://seed-company-squad.monday.com/boards/3451697530/pulses/3466487404

Will you squash/fixup that second commit as well?

@CarsonF
What second commit? If you're talking about the one with the yarn updates, that has been removed.These 2 commits here are only with the tss-react changes

These 2 commits here are only with the tss-react changes

Yeah I'd just prefer that "clean up" commits get squashed so we are left with single purpose commits.

This lived to the end of its lifetime and died


Validate database names

After #750.
MongoDB database names restrictions are documented there: https://www.mongodb.com/docs/manual/reference/limits/#naming-restrictions
PostgreSQL restrictions – there: https://www.postgresql.org/docs/current/sql-syntax-lexical.html
For collection names, we use a special settings table in the schema matching database name. Let's not complicate things for database/schema names. Instead, let's limit database names to what PostgreSQL supports.
Let's validate that database/schema name:

matches regular expression ^[a-z_][a-z0-9_]{0,62}$;
can't start with a reserved prefix _ferretdb_ (just in case).

We could relax those rules in the future.

[ ] implement database name validation on database/schema creation;
[ ] add integration test;
[ ] document the difference in rules in README.md;
[ ] add diff dance test.

Tigris is not in scope.

@seeforschauer Please don't forget about the diff test in dance

@AlekSi yeah, I just remember that the dance test fails w/o FerretDB changes in main.

dance tests left.


Error 'cannot find file' in newer version

Hi,
I upgraded from a very old version (0.3.6) of Django-rest-swagger to the newer version 2.1.2 and now I got a problem. The swagger site now produces an error:
{"schemaValidationMessages":[{"level":"error","message":"Can't read from file https://localhost/apidocs/?format=openapi"}]}
Update: I have changed this ticket as I now partly understand why this problem occurs. It seems like django-swagger doesn't recognise that it should be using ssl (https). It tries to find the api-urls under http, which doesn't work of course. Then it produces this error. How can I force django-swagger to add https with the urls?

This issue is affecting my application as well. However, I'm seeing it happening locally, without using SSL at all. And if I just try to load the URL accused in the error message, it loads just fine for me. I think it's an issue with reading the content of the response.
P.S.: Not sure how relevant this is, but I'm using Python 3.6.

You guys figure this out? I am experiencing the same thing, with Django 1.10.5

Experiencing this over SSL as well (not publicly accessible). The file/URL that it claims can't be read from DOES load and the JSON is valid.
I'm running:
Django==1.11.9
djangorestframework==3.7.7
django-filter==1.1.0
django-rest-swagger==2.1.2
nose-parameterized==0.5.0
django-cors-headers==2.1.0
django-cors-middleware==1.3.1

I'm using Django == 2.0 and django-rest-swagger == 2.1.2, facing the same problem.


fallback selection should return some data

non-logged in queues may not replenish via the subject selector for grouped selection. So this will now instead just return some data from the workflow taking into account the group if set.

LGTM

@marten refactored to move the setup state into the constructor but left a limit override on the method to change selection set size on the fly.

I'm going to call YAGNI on that.

your probably right, i did need it for testing the sliding window spec here and i didn't want to rewrite that spec (though it does need it).
This fixes a bug so we should get it out and then fix the spec / limit override later.

That's fine. It's not worse than the original. LGTM if you get the specs green.

should be good to go now @marten


Add fixed amount to gas limit.

Background
related to this issue.
I suggest increasing a fixed amount to gas limit(about 100K now) (NOT gas_estimate param in SLC).
Because, we spend such amount of gas to get params in SLC function in Solidity.
Done when

[ ] add 100K in gas limit of txes to Compass-evm

@webelf101 we need to close on this today.

Of course, it is reflected in gas estimation. But the main issue is the point I check the gas in the smart contract. At the checkpoint, some gas was already spent so reduced gas amount will be compared with the gas estimate parameter. The gas spending happens when I get the parameters at the very beginning of the tx. It is about 100K right now. So I am comparing the remaining gas amount (reduced about 100K) and the gas estimate parameter value. That's why we sometimes fail the gas estimate validation check. And so I am asking to increase the gas limit for the tx. Does this make sense? @byte-bandit @taariq

Fixed with https://github.com/palomachain/pigeon/pull/449


add starter-kit redirect to bids-starter-kit

closes #171
@effigies is this what you had in mind?

What would the effect of this be?

you'll be able to do https://bids.neuroimaging.io/starter-kit and have it direct you to the bids-starter-kit
there may be another way to do it, but I piggy backed on the setup we have for BEP redirection

see: https://50-164719390-gh.circle-artifacts.com/0/_site/starter-kit.html

Got it. LGTM.


Chore: Speed up code editor tests

Checklist
General

[x] Test run locally.

Motivation, Context and Decription
Removes unneeded module imports from the code-editor-file-browser.component.spec.ts and converts sinon/chai to jest. I also removed imports from the other code-editor files where possible, but did not convert them.
Code Review

[ ] Review 1
[ ] Review 2

Test Coverage
Should be unchanged

only very small style issues left, then I'll approve


[FEATURE]: Test that I've selected valid combo of direction, origin and destination stop

First of all, thank you for this. I've been using original gtfs integration for about two years and it was fine for the three lines I have available from my apartment; but I've now wanted to put public transport times to additional HA instances I have at different places (my parents house etc.), and this has made it so much easier!
Describe the solution you'd like

I think it would be a good idea to have some sort of "test validity" button at this step in adding schedule. At least for my city, every line shows multiple stops of the same name - sometimes up to four (one entry for bus stop, one for tram stop, times two for each direction - and this is shown even when I've specifically selected a bus line; but it sometimes does use the tram terminal... it's just a mess :D).
Since I know my city's GTFS formatting and naming conventions for the stops a little by know, it was fairly easy to navigate, but I've still chosen the wrong combo a few times which resulted in the "Start and/or End destination incorrect, possibly no transport 'today' or not in same direction, please check logs" error message and having to start over, instead of just switching one stop and trying again.
Thanks for considering this :)

Thanks for the feedback
On the rquirement, I believe you want to avoid re-re-re-re opening the same screen until you have a combination that works, not?
Actually... this is the next step after this screen, hence you recieve that message "...incorrect, possibly..."
There are some challenges and I am not very confident that this can be resolved easily.
0. this is part of configflow functionality of HA, it works but it is limited as well

when you are in that screen, it only has selected the data into the screen but your selection is not stored anywhere yet, like a webform and when in th emiddle of entering you refresh the screen, entries are gone
only after submit the entries become part of the configflow attributes
The only option I see is to 'submit', run the test and then go back to the screen if the test fails, I could prepopulate this then with the values just selected (i.e. those that failed).

Can you pleae confirm if I am assuming the correct things?

Yes, that is exactly correct. Once I get the message that the selected schedule is incorrect, I have to start over. If it would be possible to go back and re-fill all the selected values, that would of course worked as well :)

And with this lightning speed of a solution, maybe you can help with the Czech translation, i.e provice the cz.json ?
No pressure if you donot want to :)


code --list-extensions should also show extension versions

Testing https://github.com/Microsoft/vscode/issues/12658
Right now it's only a list of extension names, but listing the versions as well would be exceedingly helpful for narrowing down potential install issues w/ extensions

I'd make it into an option --show-versions, while the default should be the format that can be parsed into calling further commands like --uninstall-extension.


FAVICON FETCHER (ISSUE NUMBER : #260)

@Harikaraja From the next time mention your project's name as the name of the PR. Other than that everything looks good.

I have received the message saying it is approved what are the new changes
requested can you please let me know
On Sun, 15 Jan 2023, 18:31 Vanshita Mathur, @.***>
wrote:

@.**** requested changes on this pull request.
Please link the issue which you have resolved !
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/pull/281#pullrequestreview-1249222051,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHWHIYBQGER3GQCCBWLWSPYKVANCNFSM6AAAAAAT32GJCU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks shubam .
I have received the mail from Mathur saying that make the required changes
On Sun, 15 Jan 2023, 18:21 Shubham Singh, @.***> wrote:

@Harikaraja https://github.com/Harikaraja From the next time mention
your project's name as the name of the PR. Other than that everything looks
good.
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/pull/281#issuecomment-1383142848,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHQ5YGSEFANUCBHLIBDWSPXDJANCNFSM6AAAAAAT32GJCU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Harikaraja From the next time mention your project's name as the name of the PR and also add a small description in the PR chat as well.

Ok

I have received the message saying it is approved what are the new changes requested can you please let me know
…
On Sun, 15 Jan 2023, 18:31 Vanshita Mathur, @.> wrote: @.* requested changes on this pull request. Please link the issue which you have resolved ! — Reply to this email directly, view it on GitHub <#281 (review)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATCQWHWHIYBQGER3GQCCBWLWSPYKVANCNFSM6AAAAAAT32GJCU . You are receiving this because you were mentioned.Message ID: @.***>

What are the changes i requested . please let me know

Mentioned mam
On Sun, 15 Jan 2023, 19:26 rishika vishnoi, @.***>
wrote:

@.**** requested changes on this pull request.
@Harikaraja https://github.com/Harikaraja Kindly mention issue no that
was assigned to you and also change the title of PR
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/pull/281#pullrequestreview-1249235500,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHRWKUF3TFWLRR7E6KTWSP62JANCNFSM6AAAAAAT32GJCU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Please link the

Please link the issue which you have resolved !

Mam how to link the issue can you please clarify me

Please link the

Please link the issue which you have resolved !

Mam how to link the issue can you please clarify me

Closes: #issuenumber

Closes: #260

Please link the

Please link the issue which you have resolved !

Mam how to link the issue can you please clarify me

By using Closes: #issuenumber in the PR comment section

Mam done !! please check

How can I know my score sir.
On Wed, 18 Jan 2023, 02:12 Tushar Kesarwani, @.***>
wrote:

Merged #281
https://github.com/TusharKesarwani/Front-End-Projects/pull/281 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/TusharKesarwani/Front-End-Projects/pull/281#event-8249605792,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHQWFW4YZ4ABKVO3OSDWS37ZRANCNFSM6AAAAAAT32GJCU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>


Add ALEJobStarted User autocommand event

The ALELintPre and ALELintPost autocommand events are currently being
used by lightline-ale to refresh the status line and check the linter
status for a current buffer. One of the plugin's checks looks to see if
linters are currently running, via ale#engine#IsCheckingBuffer(). This
currently only works partially in certain situations. In my particular
case, working with Go files, this only seems to function properly when a
file is initially opened. Saving a file does not correctly update the
status.
This seems to be due to the fact that ALELintPre actually runs before
any jobs are carried out, making it plausible that hooking into
ALELintPre for the purpose of checking to see if there are any currently
running linters for a buffer is unreliable as it would be prone to
pretty obvious race conditions.
This adds a new User autocommand, ALEJobStarted, that gets fired at the
start of every new job that is successfully run. This allows a better
point to hook into checking the linter status of a buffer using
ale#engine#IsCheckingBuffer() by ensuring that at least one job has
started by the time IsCheckingBuffer is run.

I've included tests for most of the above explained things here, namely for the new event and also to confirm the timing issues above surrounding using IsCheckingBuffer at ALELintPre. Let me know if there's anything else that needs fixing - or if the autocommand should be named something else or placed at a different location, etc.
Thanks!

Interesting. My notes:

Looks like lightline-ale is a bit obsolete, it subscribes to ALELint autocmd, which as I see now is deprecated according to https://github.com/w0rp/ale/pull/1203. And ALELint is only an old name for ALELintPost, so lightline-ale does not currently subscribe to ALELintPre at all (we should fix that).
Instead of adding new autocmd events, can we maybe request some guarantees from ALE itself, that by the time ALELintPre is being fired, ale#engine#IsCheckingBuffer is guaranteed to return true, and by the time ALELintPost is being fired, it is guaranteed to return false? Basically I want to solve the race conditions within ALE itself, not on the lightline-ale side, and not with adding more events that would make lightline-ale refresh more often than necessary.

What do you think?

Hey @maximbaz,
Yeah, it totally slipped my mind in all of my troubleshooting that lightline-ale is subscribing to the deprecated event!
I'm all for less things, for sure, but right now the problem is with the placement of the other events. ALELintPre fires here, which I think is technically correct as it's designed to be a pre-lint hook, so that make sense. The core of the issue is that the current implementation of IsCheckingBuffer is not based on a opaque started/stopped flag, but rather determines its status from a more real-time measure of whether or not any linters are literally running for the buffer at that specific point in time (via checking the active linter list for a buffer). Hence more often than not, IsCheckingBuffer will not return true at the time that event fires.
Considering the above, I think it would be correct in concluding that the ALELintPre event should not be used in conjunction with IsCheckingBuffer, nor do I think it should be moved, as other plugins of course may depend on its current location.
Thinking about it, I almost wonder if it would be a good idea to just not even bother with ALELintPre (considering that it would not really be useful to lightline-ale at all) and maybe hook into something like ALEJobStarted (or whatever it ends up being). This event fires at the successful start of any job and pretty much guarantees that IsCheckingBuffer will be true, as shown by the supplied tests. I think this is close to what you are looking for and should only result in a marginal performance hit (assuming someone does not have dozens of buffers open with lots of expensive linters, although in that case I think the performance demands of a refreshing statusline will be trivial in comparison).
Thoughts?

I see, thanks for explaining the details!
I'm not opposed to your proposal, but more as a curiosity I quickly drafted https://github.com/maximbaz/lightline-ale/pull/9, could you test whether it solves your issue, and tell me what you think about that approach in general? 🙂
That code simply doesn't use IsCheckingBuffer which as you said is not really linked to ALELintPre and ALELintPost, instead it tracks the lint status in a buffer variable.

Hey @maximbaz, I won't have a chance to test extensively right now, but I don't think this will work 100% as expected as if I understand correctly, the autocommand events fire independent of a specific buffer. See https://github.com/w0rp/ale/issues/1363#issuecomment-368307402 for an explanation (which also seemed to be the genesis of IsCheckingBuffer being public).

Makes sense, then I think your approach is the best we can get 😉

Nice! Thanks @w0rp!


MBP 13" early 2011 no response whatsoever

After running the 2.0 installer, signing out and back in to iCloud several times, and several reboots, we do not get the slightest response it seems.  We have the IOGear dongle.  I use this same one on my other mid-2010 13" MBP and it works fine, but this slightly newer MBP, no luck.  I wanted to try the 2.0.1 beta but it does not look like there is an installer zip/pkg for it, just source files to browse on your repository here.  Any suggestions in general??  Thanks,
-Marco

I ran the 2.0 installer a little under a month ago on my 13" MBP late 2011. For a few weeks, it worked perfectly fine and I loved it. Then, the other day I attempted to use Airdrop between my 5s and MBP, when I realized that none of the functions are working anymore. I'm pretty sure I've run through all of the troubleshooting steps, so I'm not sure how to fix it at this point. So, yeah, pretty much the same problem as marcocd.

Hi,
First check if the CAT system diagnostic mentions NOT OK on any steps.
If the CAT System Diagnostic reports OK for all checks, then continue. If it doesn't, follow the recommendations of the tool.
The problem you describe seems to be related to the handshake between your devices which isn't happening. Here's what I'd do:
0. Follow the official troubleshooting steps from Apple. Follow everything that's said there before trying anything else. Continue if it's still not working.

Make sure there aren't other active Macs nearby, which might interfere with the handshake, signout iCloud on your iOS device + Mac.
Open Keychain, select "All items" category, then search for "handoff"
Delete any keys you see there
Reboot your iOS device + Mac
Sign in iCloud on iOS + OS X
Open a Safari page on both the iOS device and Mac
Try handoff after a couple of minutes (the handshake can take as much as 20 mins). You can see Continuity activity in the Console app, if you filter on "sharingd"

Good luck!

Thank you I will give this a try.  Can you also specify the download link for the 2.0.1 version of the software, even if it is in beta still?  I'd like to try this out and I can't seem to find an all-in-one installer package for 2.0.1 on your site.  Thank you so much,
-Marco


Page#published? undefined in Readme

In default values example, #default_editor_title calls #published?, but as far as I can tell #published? isn't defined. I'm guessing its just a Readme error?

Yes that was a readme error :) thanks for catching this! it's been fixed


Implement line coloring for console output

Not entirely sure how to do this yet, but running the tool on a large project means that you might have a lot of lines being written that we should be classifying (not everything is an error).

In fact, the whole IProgress<string> seems like a bad choice for advanced logging.

This is now in the 2.0 branch


Ported to .NET Standard / .NET Core

Hi! Thanks to you and @danm-de for the nice library.
I was wondering whether you're still maintaining it? I wanted to use it in a .NET Core 2.0 app, so I've ported it to .NET Standard (you can see my changes here: https://github.com/Daniel15/gpgme-sharp/pull/1) and published it to NuGet: https://www.nuget.org/packages/gpgme-sharp. I'm also planning on adding some basic unit/integration tests.
Let me know if you'd like me to submit a pull request with my changes, or add you as an admin to the NuGet package.
Thanks!

@Daniel15 Sure you can provide send me a pull request. I would also be happy to have the admin rights on the nuget package. My nickname on nuget is wget as well.

Thanks, submitted as #6

@Daniel15 Yes, I know the issue of not being an admin :) Indeed having an organization is better in this regard when doing CI stuff. I'll move the repo to the organization today. :)
If you can give me access to the CI build system, this would be nice of you.

I haven't actually configured any CI system yet... Will do that when I get
a chance.
Sent from my phone.
On Mon, Feb 4, 2019, 12:38 AM William Gathoye<EMAIL_ADDRESS>wrote:

@Daniel15 https://github.com/Daniel15 Yes, I know the issue of not
being an admin :) Indeed having an organization is better in this regard
when doing CI stuff. I'll move the repo to the organization today. :)
If you can give me access to the CI build system, this would be nice of
you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wget/gpgme-sharp/issues/5#issuecomment-460167689, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAFnHYBvg5pStDLWeDJcNcFG5lsvJBjZks5vJ_GYgaJpZM4aboqw
.

@wget Do you think you'll move this repo to the org soon, if you're okay with that? I can set up the CI stuff once it's there. Otherwise, I could move my fork. I've got a few other PRs I'd like to submit too... Will get to those soon.

@Daniel15 moved to the org :)

Nice, thanks!


(PUP-5487) Add ability to supress warnings about storeconfig

This patch adds the ability to disable warnings about storeconfigs
not beeing enabled with:
--disable_warnings storeconfigs

As per the discussion in the ticket - I think this should be done a different (and much better way) by only issuing warnings when the expressions in question are evaluated/used. See the ticket for how that is easily implemented.
The way this is changed in this ticket means that it would stop issuing warnings at evaluation time as well  as when validating. It would fall back to the lowest level warning (deep inside) that gives no information about where the problem is in the manifests.
So, I am closing this PR.


Koel won't log me in... The log page just reloads, then a message flashes on the console ( "localhost:8000/api/data 401 (Unauthorized) )

OS, browser maybe? I can't help you with this little information.

Windows 10... I'm sorry if the information is insignificant.. i just don't understand why it happened like that... i had an older version of Koel and it worked fine... but when i cloned the latest version, that problem started

What "older" and what "current" are we looking at then?
On Sun, Jun 25, 2017 at 18:04 fsavalam<EMAIL_ADDRESS>wrote:

Windows 10... I'm sorry if the information is insignificant.. i just don't
understand why it happened like that... i had an older version of Koel and
it worked fine... but when i cloned the latest version, that problem started
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/phanan/koel/issues/616#issuecomment-310914613, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHrt0kMtcQF7ffW2L2gCLNcng9m88g2oks5sHpMkgaJpZM4OETtm
.

v3.5.5 (older version)
v3.6.2 (new version)

How are you running koel?


Will property be included in the mpdel if it was declared using Interface or Abstract class?

Can Interfaces or Abstract classes be used to create model properties?

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

ID: 76c24b57-557f-a6d6-16f1-1da50e4744cd
Version Independent ID: 8bee29c6-58e4-1d07-025e-0bdcead9b5a1
Content: Including & Excluding Properties - EF Core
Content Source: entity-framework/core/modeling/included-properties.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @rowanmiller
Microsoft Alias: avickers

@DeveloperLookBook I assume you mean entity types that have properties where the property type is an interface or an abstract type. If so, yes for abstract types. For interfaces, see https://github.com/aspnet/EntityFrameworkCore/issues/13344 and https://github.com/aspnet/EntityFrameworkCore/issues/757


Enhancing User Data Retrieval with GitHub Personal Access Tokens.

Currently, we are using the static link to fetch users profile picture and username only.
However, we can enhance our approach by implementing GitHub Personal Access Tokens. This way, we can access the user's data through a backend API, which can then be used to populate the relevant fields on the frontend, providing a more dynamic and secure solution.

I can work on this issue once it's approved.

Hi @satvik225
Using GitHub API to get dynamic data is something we are also planning.
We are currently in the process of creating the roadmap.
We'll post on discord as soon as the roadmap is ready.
Connect on discord to get notified.

Join our Discord server to discuss ideas, ask questions, and collaborate with others.

Check #58


fix(ci): address errors in CI to enable branch protection rules

Overview

Update CI to enable branch protections

@coderabbittai ignore


Incomplete tests: External DNS integration #1077

Context: production readiness proposal and plan
The feature "External DNS integration #1077" is identified as incomplete test coverage. As a measure to reach Istio production quality in 0.3, this issue is opened to track the progress of providing sufficient test coverage for the feature in question.
This issue is initially assigned to the working group leads.
Recommendations:

Come up with a test plan for how the feature should be tested. Identify and document (in this issue, or a separate document this issue will link to) test cases and whether each will be covered by an integration test (with some level of mocking and/or starting up selected components in test environment), or end to end test (aka system test, which brings up the whole Istio to exercise the feature; currently live in the istio/istio repo).
If you expect the test plan is complex and controversial, consider having it formally reviewed.
State an ETA in the issue, and assign this to a developer who will execute the test plan.
Execute the test plan as the highest priority for 0.3.
For any bug or defect identified by the new test cases, file a new issue and link it from this one.
Close this issue only when the test plan is completely executed, and all additional issues identified in step 3 are fixed.

If you see a risk of not fixing this issue by end of 0.3, please contact<EMAIL_ADDRESS>as soon as possible. We will also periodically ping the issue for update.

External DNS no longer scheduled for 0.3/0.4 - will reopen when we add it to the roadmap.


Allow setting an alternate manifest source in your user-data

This allows you to set #manifest: /path/to/manifest anywhere in your user-data (no need to use JSON) after which we'll attempt to load that file and parse it as is.
Especially useful for "cloud-config" or simple bash user-data scripts.
Fixes https://github.com/mycloudandme/spacel-agent/issues/2
@pebble/webops

+1
Alternate ideas: read from stdin or as an argument?

+1


Remove curation reward on comments

It's possible to remove curation reward when you publish a comment on Steem with the parameter allow_curation_rewards: false, for comment_options operation. This doesn't work on root post but we should enable it on comment that would give around 25% more for comment authors.

It should be default or should we give a user a choice?

By default @Sekhmet


fix log epoch

What does this PR do?
Change to trainer/epoch when logging
CO-1812

Now moved under `/trainer/`

Should there be a data point in that image?

Should there be a data point in that image?
Hm... I don't know what happened there... I checked again and it's there?? maybe it was buffering...

Here's a new run new project. I'm going to claim wandb bug


Repo to be merged to malc

I intend to merge this repo in the malc one to reduce the number of repos. Before doing this I'd like to be sure you don't see a reason why it's a bad idea.
@gbonnefille
@freyssin
@lacourte

As far as I know, there are two motivations to use two distincts repositories.
The first one is the technology stack: one is raw C while other is a Java/Maven providing a plugin for an other tool.
The second one is the (initial) motivation to consider malc as an independent low level layer. This component could be used without the codes generated by the generator.
IMHO, even if this increase the number of repositories, I feel it is cleaner/simpler to keep the repositories separated.
Eventually, a merge should be evaluated against the official generator. Such merge will certainly offer a transparent support for this plugin: less repo, less maintenance effort.

@gbonnefille I quite value your argument I would have one other thought for merging the stub with its api: it is very unlikely that a développer implements MO Services without using a stub generator. Writing the full boil-plate code for each service and operation seems very repetitive and not that interessant.
Is that enough to merge them?. Maybe not. I am not sure

@gbonnefille I quite value your argument I would have one other thought for merging the stub with its api: it is very unlikely that a développer implements MO Services without using a stub generator. Writing the full boil-plate code for each service and operation seems very repetitive and not that interessant.

I had the same thought during the initial meeting with @freyssin and @lacourte. I remember the motivation was to have a really low-level API in order to be able to create component like routers.
Other thought: even the Java implementation use separated repositories.
If the motivation is to simplify the initial checkout, I would suggest to take a look at git submodule: adding a super-repository linking all needed components, at the expected commit. Such super-repository will be updated only when releasing a new version. It would be possible to link in this repository, all CNES' implementations (malc, mal-java, malgo) and eventually the related COTS (zeromq).


🚀 - Add Support for Golang

Which @codeimage/* package(s) are relevant/releated to the feature request?
codeimage
Description
Add support for Go Programming Language

Released with 1.6.1


issues with daily cdm conversion for august release

A couple of minor issues with the code and the ancillary files.
1)The code is creating triplicate timestamps for the same observation.
AGE00147708-3-1879-01-07--44-13|3|1879-01-07 00:00:00+00|1|36.72|4.05|1|44|710|20.0|13|13||1|AGE00147708|TIZI OUZOU|0|1|229
AGE00147708-2-1879-01-07--44-13|3|1879-01-07 00:00:00+00|1|36.72|4.05|1|44|710|20.0|13|13||1|AGE00147708|TIZI OUZOU|0|1|229
AGE00147708-1-1879-01-07--44-13|3|1879-01-07 00:00:00+00|1|36.72|4.05|1|44|710|20.0|13|13||1|AGE00147708|TIZI OUZOU|0|1|229
It's because of source 229 is mingled several times within one station , (ECA&D ) is the source so you in the record_id file you will have:
AG000060590-229-1
AG000060590-229-2
AG000060590-229-3
I have edited the record_id.csv now so that it maps to only one record _id for all stations with source 229.

Line 271 of the daily_to_cdm_obs_table_v1.py has an extra +"-" which needs to be removed
original:  df["observation_id"] = df["observation_id"]  +"-" + df['observed_variable'] + '-' + df['value_significance']
should be:  df["observation_id"] = df["observation_id"]  + df['observed_variable'] + '-' + df['value_significance']

Line 211 of the daily_to_cdm_lite_v1.py has an extra +"-" which needs to be removed
original:  df["observation_id"] = df["observation_id"] +"-" + df['observed_variable'] + '-' + df['value_significance']
should be:  df["observation_id"] = df["observation_id"]  + df['observed_variable'] + '-' + df['value_significance']

Note - will need to ensure local changes to record_id.csv are transferred to JASMIN

A new record_id.csv has ben upload to JASMIN with the neccassary edits


net: lwm2m: Bypass send_queue when sending empty Ack

In case we want to immediately send empty Ack to server, we should bypass all send queues.
This is required when we try to send Ack from callbacks that happen from socket-loop context. On those cases the Ack would have not been send because the callback might be blocking the socket-loop while processing a request (like write callbacks).
This fix makes the API submitted in https://github.com/zephyrproject-rtos/zephyr/pull/30392 to actually work on post-write callbacks that block for a long time. For example FOTA process that erases a flash before writing the content.

With the fix

First Ack immediately.
Then the actual response 10 seconds later.
Without this fix

First ack after 13 seconds. Server already retried twice.


Add new template SharePoint-SingleFarm-FullConfig

This is a new SharePoint template that is basically a DTL version of this one: https://azure.microsoft.com/en-us/resources/templates/sharepoint-adfs/
Contrary to the existing one, it creates only 1 SharePoint farm (either 2013, 2016 or 2019) and the configuration is much more extensive:

1 web application created with 2 zones: Windows NTLM on Default zone and ADFS on Intranet zone.
ADFS is installed on the DC, and SAML trust is configured in SharePoint.
A certificate authority (ADCS) is provisioned on the DC and issues all certificates needed for ADFS and SharePoint.
A couple of site collections are created, including host-named site collections that are configured for both zones.
User Profiles Application service is provisioned and personal sites are configured as host-named site collections.
Add-ins service application is provisioned and an app catalog is created.
2 app domains are set (1 for for each zone of the web application) and corresponding DNS zones are created.
Latest version of claims provider LDAPCP is installed and configured.

@leovms is this PR in your radar?


Key vault access policy worked in v0.1, but not in v0.2.3

Bicep version
Bicep CLI version 0.2.3 (be18b406d7)
Describe the bug
Receive the following error: Error BCP036: The property "name" expected a value of type "'add' | 'remove' | 'replace'" but the provided value is of type "string".
To Reproduce
Add access policy to Key Vault outside the parent, something similar to the below, where ${resourcePrefix} is passed in as a parameter:
resource keyVaultAccessPolicy 'Microsoft.KeyVault/vaults/accessPolicies@2019-09-01' = {
  name: '${resourcePrefix}-kv/add'
  properties: {
    accessPolicies: [
      {
        objectId: site.identity.principalId
        tenantId: subscription().tenantId
        permissions: {
            keys: []
            secrets: [
              'get'
              'list'
            ]
            certificates: []
            }
      }
    ]
  }
}

Additional context
According to the docs https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/child-resource-name-type#outside-parent-resource, this is the correct way to add child resource outside of it's parent.

Thanks for reporting this. It looks like another case of #657. Please can you try using any() to work around this until we have a fix available:
resource keyVaultAccessPolicy 'Microsoft.KeyVault/vaults/accessPolicies@2019-09-01' = {
  name: any('${resourcePrefix}-kv/add')
  properties: {
  ...

Closing as dup of #657


[FreeBSD] vnstat: not found

Reporting Issues:
To ensure that a I has enough information to work with please include all of the following information.
Use proper markdown syntax to structure your post (i.e. code/log in code blocks).
Make sure you provide the following information below:

[x] Version
https://github.com/Hellowlol/HTPC-Manager/commit/02ce2ba6360dc95e64669946383866d1ad347f8d

[x] Branch
master2

[x] Commit hash
https://github.com/Hellowlol/HTPC-Manager/commit/02ce2ba6360dc95e64669946383866d1ad347f8d

[x] Operating system
FreeBSD-10.3-RELEASE-amd64-64bit-ELF

[x] Python version
2.7.11

[x] What you did?
Installed vnstat & paramiko

[x] What happened?
getting vnstat: not found, is working fine in the shell

[x] What you expected?
vnstat to work. Is there a way to find out what path it's looking for or to set a manual path like git ?

[x] How can we reproduce your issue?
Is a fresh install of freebsd

[x] What are your (relevant) settings?

[x] Include a link to your FULL (not just a few lines!) log file that has the error. Please use Gist or Pastebin.

Close your issue when it's solved! If you found the solution yourself please comment so that others benefit from it.
Link to log:
htpcmanager.log https://gist.github.com/T-600/65a370ba4a8ae6189e391a01715dba3e
vnstat --dumpdb --xml https://gist.github.com/T-600/f456fca188fa96b740070e555e62e5d3

in short return ocde 127 means command not found. Have you installed vnstat for your jail?

yes and it's working fine from the command line, just not in htpc manager

Hmm. Strange, you dont seem to be using paramiko. What happens if you check the use ssh option and enter the ip and port of the freenas computer?

paramiko is installed. using ssh is erroring out aswell, this is quite strange.
https://gist.github.com/T-600/8d01f8faf057e39ac7d4e808ddce11e2

Can you post a screenshot of your vnstat module settings?

What paramiko version have you installed?

paramiko (2.0.0)

Seems to be a path issue, if i add the path to the cmd variable it works fine.

That's working on my end, i'll wait till it's added thank you.


[WIP] [API] add GET identifiers

@miq-bot add-label wip

[ ] accounts
[ ] auth
[ ] automation_requests
[ ] availability_zones
[ ] categories
[ ] chargebacks
[ ] clusters
[ ] conditions
[ ] data_stores
[ ] events
[ ] features
[ ] flavors
[ ] groups
[ ] hosts
[ ] instances
[ ] pictures
[ ] policies
[ ] policy_actions
[ ] policy_profiles
[ ] providers
[ ] provision_dialogs
[ ] provision_requests
[ ] rates
[ ] reports
[ ] request_tasks
[ ] requests
[ ] resource_actions
[ ] resource_pools
[ ] results
[ ] roles
[ ] security_groups
[ ] servers
[ ] service_catalogs
[ ] service_dialogs
[ ] service_requests
[ ] service_templates
[ ] services
[ ] software
[ ] custom_attributes
[ ] tags
[ ] tasks
[ ] templates
[ ] tenants
[ ] users
[ ] vms
[ ] zones

@abellotti did some more work to bring this in line with https://github.com/ManageIQ/manageiq/pull/6630. As with that PR, it implements all the identifiers I know about, so moving this out of WIP.
@miq-bot rm-label wip
@miq-bot add-label api, enhancement

In general this is good, I haven't double checked the identifiers from miq_product_features, but they look about right.
Might be a good idea to have @h-kataria or @AparnaKarve try out the SSUI with this PR applied on the API side, as any visibility or behavioral changes will affect them first (getting 403 vs empty results on queries).

@AparnaKarve are you able to kick the tires on this?

@AparnaKarve bump

@imtayadeway Finally got a chance to test this.
I tried logging into SSUI, and noticed that the below 2 APIs were returning 400 Bad Request
GET http://localhost:3001/api/settings 400 (Bad Request)
GET http://localhost:3001/api/services?filter[]=service_id=nil 400 (Bad Request)

//<PHONE_NUMBER>2817
// http://localhost:3000/api/settings

{
  "error": {
    "kind": "bad_request",
    "message": "Unsupported Collection settings specified",
    "klass": "ApiController::BadRequestError"
  }
}

//<PHONE_NUMBER>2928
// http://localhost:3000/api/services?filter[]=service_id=nil

{
  "error": {
    "kind": "bad_request",
    "message": "attribute service_id does not exist",
    "klass": "ApiController::BadRequestError"
  }
}

@AparnaKarve thanks for checking this out! Unfortunately it looks like master and SSUI have moved on quite a bit since I last rebased (hence your issue with the Settings API), so I just rebased against latest master to incorporate those changes (and also add GET identifiers to the new Settings API). Would you mind giving this another kick? Thanks! :heart:

@imtayadeway The last update on this PR looks really great and captures all the cases that I know of in SSUI. 👍
It has also helped me identify a few areas in SSUI where we can prevent making a REST API call if the RBAC disallows it.
OK to merge. Thanks 😄

👍
🎹


Torch is required even when we are using Tensorflow

See https://github.com/eto-ai/rikai/runs/5199485143?check_suite_focus=true
from #538
E                   : java.lang.RuntimeException: 2022-02-15 11:52:34.988360: W tensorflow/stream_executor/platform/default/dso_loader.cc:64] Could not load dynamic library 'libcudart.so.11.0'; dlerror: libcudart.so.11.0: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.9.10/x64/lib2022-02-15 11:52:34.988399: I tensorflow/stream_executor/cuda/cudart_stub.cc:29] Ignore above cudart dlerror if you do not have a GPU set up on your machine.2022-02-15 11:52:37,188 INFO Rikai (tfhub_registry.py:65): Resolving model tfssd from tfhub:///tensorflow/ssd_mobilenet_v2/2/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/spark/sql/model.py:270: UserWarning: Using schema and pre_processing/post_processing explicitlyis deprecated and will be removed in Rikai 0.2. Please migrate to a concrete ModelType.  warnings.warn(2022-02-15 11:52:37,215 ERROR Rikai (base.py:90): Unsupported model flavor: tensorflowTraceback (most recent call last):  File "<string>", line 6, in <module>  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/spark/sql/codegen/base.py", line 97, in command_from_spec    return registry.resolve(row_spec)  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/experimental/tfhub/tfhub_registry.py", line 76, in resolve    return udf_from_spec(spec)  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/spark/sql/codegen/base.py", line 82, in udf_from_spec    codegen = importlib.import_module(codegen_module)  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/importlib/__init__.py", line 127, in import_module    return _bootstrap._gcd_import(name[level:], package, level)  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked  File "<frozen importlib._bootstrap_external>",
line 850, in exec_module  File "<frozen importlib._bootstrap>",
line 228, in _call_with_frames_removed  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/spark/sql/codegen/tensorflow.py",
line 23, in <module>    from rikai.pytorch.pandas import PandasDataset  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/pytorch/__init__.py",
line 18, in <module>    from rikai.pytorch.data import Dataset  # noqa: F401  File "/opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/rikai/pytorch/data.py",
line 23, in <module>    import torchModuleNotFoundError: No module named 'torch'

The tensorflow codegen should use the tensorflow PandasDataset instead of the torch PandasDataset in #507

Here is the related issue: #40

closed by https://github.com/eto-ai/rikai/issues/583


Heapster cannot get metrics from other nodes

I have a k8s cluster with one master and two nodes. I found that the heapster can only get metrics from the node where its pod resides on, but cannot get metrics from other nodes.
The err log says:
E0903 21:38:21.235223       1 model_handlers.go:530] unable to get node metric: the requested entity does not have any metrics yet
[{default/kubedash-mi08u 0 0} {default/jenkins5-84q70 0 0} {default/guestbook2-u6ryy 0 0} {default/jenkins2-h5xh7 0 0} {default/jenkins1-1d47t 0 0} {default/guestbook3-gp92t 0 0}]

Does anyone else encounter the same problem? Any help or suggestions will be appreciated, thanks.

Are the pods running on the other node? Is the other node in a Ready
state?
On Thu, Sep 3, 2015 at 6:59 AM, yuqi huang<EMAIL_ADDRESS>wrote:

I have a k8s cluster with one master and two nodes. I found that the heapster
can only get metrics from the node where its pod resides on, but cannot get
metrics from other nodes.
The err log says:
E0903 21:38:21.235223       1 model_handlers.go:530] unable to get node metric: the requested entity does not have any metrics yet
[{default/kubedash-mi08u 0 0} {default/jenkins5-84q70 0 0} {default/guestbook2-u6ryy 0 0} {default/jenkins2-h5xh7 0 0} {default/jenkins1-1d47t 0 0} {default/guestbook3-gp92t 0 0}]
Does anyone else encounter the same problem? Any help or suggestions will
be appreciated, thanks.
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/issues/516.

Yes,all nodes works normally, some pods works on these nodes. I have entered the container, heapster can visit the kubelet's rest api of all nodes and get the metrics information.

If the pod and containers exist and heapster is able to reach the kubelets,
I don't expect any issues. As of now, heapster does not take into account
pod state from the Kubernetes API server. This might result in failures
until the pod is running or while it is restarting.
On Fri, Sep 4, 2015 at 5:48 AM, yuqi huang<EMAIL_ADDRESS>wrote:

Yes,all nodes works normally, some pods works on these nodes. I have
entered the container, heapster can visit the kubelet's rest api of all
nodes and get the metrics information.
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/issues/516#issuecomment-137727534
.

I have the same issue. I have three nodes, but it shows metrics only from two of those.

Can you post heapster logs?
On Sat, Sep 5, 2015 at 3:24 AM, Alexander<EMAIL_ADDRESS>wrote:

I have the same issue. I have three nodes, but it shows metrics only from
two of those.
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/issues/516#issuecomment-137939843
.

@vishh sure. I run heapster with influxsb & grafana:
$ kubectl get nodes

NAME            LABELS                                 STATUS
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready

$ kubectl get pods

NAME                    READY     STATUS    RESTARTS   AGE
heapster-i1p6s          1/1       Running   0          23h
infludb-grafana-n7r10   2/2       Running   0          1d
kube-dns-v4-rwohe       3/3       Running   3          3d
kube-ui-v1-xtsti        1/1       Running   0          3d

$ kubectl logs heapster-i1p6s
I0905 10:15:51.614496       1 heapster.go:55] /heapster --source=kubernetes:http://<IP_ADDRESS>:8080 --sink=influxdb:http://monitoring-influxdb:8086
I0905 10:15:51.614557       1 heapster.go:56] Heapster version 0.17.0
E0905 10:15:51.614632       1 helper.go:247] expected to load root ca config from /var/run/secrets/kubernetes.io/serviceaccount/ca.crt, but got err: open /var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory
I0905 10:15:51.614706       1 kube_factory.go:168] Using Kubernetes client with master "http://<IP_ADDRESS>:8080" and version "v1"
I0905 10:15:51.614722       1 kube_factory.go:169] Using kubelet port 10255
I0905 10:15:51.622892       1 driver.go:376] created influxdb sink with options: {root root monitoring-influxdb:8086 k8s false}
I0905 10:15:51.626697       1 heapster.go:66] Starting heapster on port 8082
E0905 11:41:33.543960       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [74377/73811]) [75376]
E0905 12:40:39.647016       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [75452/75377]) [76451]
E0905 14:18:21.181591       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [77229/76453]) [78228]
E0905 15:17:40.914829       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [78308/78229]) [79307]
E0905 15:46:16.775288       1 driver.go:235] failed to write stats to influxDB - Post http://monitoring-influxdb:8086/db/k8s/series?u=root&p=root&time_precision=s: dial tcp: lookup monitoring-influxdb: no such host
E0905 16:17:36.695847       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [79400/79309]) [80399]
E0905 17:32:39.776462       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [80765/80401]) [81764]
E0905 18:29:33.833213       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [81801/81766]) [82800]
E0905 18:46:22.582508       1 driver.go:235] failed to write stats to influxDB - Post http://monitoring-influxdb:8086/db/k8s/series?u=root&p=root&time_precision=s: dial tcp: lookup monitoring-influxdb: no such host
E0905 19:52:36.871247       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [83319/82802]) [84318]
E0905 21:37:56.957708       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [85234/84319]) [86233]
E0905 21:46:28.278056       1 driver.go:235] failed to write stats to influxDB - Post http://monitoring-influxdb:8086/db/k8s/series?u=root&p=root&time_precision=s: dial tcp: lookup monitoring-influxdb: no such host
E0905 23:27:05.381356       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [87220/86234]) [88219]
E0906 00:46:38.663397       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [88669/88220]) [89668]
E0906 02:13:33.865975       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [90249/89669]) [91248]
E0906 03:45:51.049016       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [91926/91250]) [92925]
E0906 05:16:11.084423       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [93570/92928]) [94569]
E0906 07:05:17.620307       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [95558/94570]) [96557]
E0906 08:26:19.942406       1 reflector.go:183] watch of *api.Pod ended with: 401: The event in requested index is outdated and cleared (the requested history has been cleared [97032/96558]) [98031]

It's a bit strange, but sometimes lookup to influxdb is failed.

@NOX73 Would you check the date of all the nodes? If the node's date is not synchronous with the node where the  heapster resided, the heapster cannot collect the metrics normally.

You can run kubectl describe on the influxdb pod to figure out if it is
restarting. I notice a few issues.

Service accounts have not been setup. You can take a look at the source
configuration docs in heapster repo to get more info about this.

Watch for pods fails continuously. If heapster is not able to retrieve
pods, it will not collect any container stats belonging to pods.

Ensuring time synchronization is also required.
On Tue, Sep 8, 2015 at 8:57 PM, yuqi huang<EMAIL_ADDRESS>wrote:

@NOX73 https://github.com/NOX73 Would you check the date of all the
nodes? If the node's date is not synchronous with the node where the
heapster resided, the heapster cannot collect the metrics normally.
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/issues/516#issuecomment-138772124
.

@huangyuqi you are right, after time synchronization and restarting heapster all goes wll, thanks.

this issue will not happen when i  ensure time synchronization between nodes.  So i close this issue.


Incorrect value for Batch Norm Moving Variance?

I am playing around with Keras' BatchNormalization layer with the following code.
`bn_layer = keras.Sequential()
bn_layer.add(keras.layers.BatchNormalization(momentum=0,
moving_mean_initializer=keras.initializers.constant(0),
moving_variance_initializer=keras.initializers.constant(0),
input_shape=(1,)))
bn_layer.compile('sgd', loss='mean_squared_error')
X = np.array([1,2,3,4])[:, np.newaxis] # with mean 2.5 and variance 1.25
y = 2*X
bn_layer.fit(X, y)
`
When look at bn_layer.layers[0].get_weights(), I get [array([1.0247195], dtype=float32),  array([0.09999999], dtype=float32),  array([2.5], dtype=float32),  array([1.6672224], dtype=float32)]
Since I set momentum = 0, then the moving average and moving variance should be the mean and variance of the X. However, the moving variance I get is 1.6672224 instead of 1.25. Any idea why this is happening?

I found the problem. The std deviation is calculated using Bessel's correction[https://en.wikipedia.org/wiki/Bessel's_correction].


[Loading]: .close() can be called earlier than visible=true

TL;DR: Sometimes the async sequence of operations can be: this.visible = false; this.visible = true; leaving the "Loading" opened forever.
In some scenarios the .close() can be called before
  Vue.nextTick(() => {
    instance.visible = true;
  });

Scenarios include some in-memory caching (Relay/Apollo GraphQL for example).
First time the "Loading" div shows fine. The second time (when a value is cached in memory) it shows and stays forever because .close() was called right after the Loading constructor call.
The proposed fix solves the bug. Not sure if that's the right way, or if I broke anything else. Probably need testing from core maintainers.
Happy to rework if needed.

Recommend add tests for your use case.
Also, have a look at the failed test.