CORTX-31012:  Include timestamp in Core dump filename.

Signed-off-by: Papan Kumar Singh<EMAIL_ADDRESS>
Description

To avoid same core file name when m0d start with the same pid,
add timestamp in core file name.
Currently core file name is core.,
Change it to core..
Breaking change

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates

Applicable issues

This change fixes an issue: #CORTX-31012
This change is related to an issue: #

CORTX image version requirements

This change requires the following images:

cortx-all:<version>
cortx-rgw:<version>

How was this tested?
[root@cortx-data-headless-svc-ssc-vm-rhev4-2614 ~]# sysctl -a | grep core
kernel.core_pattern = core.%t
[root@cortx-data-headless-svc-ssc-vm-rhev4-2614 m0d-0x7200000000000001:0x5a]# pwd
/etc/cortx/motr/m0d-0x7200000000000001:0x5a
[root@cortx-data-headless-svc-ssc-vm-rhev4-2614 m0d-0x7200000000000001:0x5a]# ls
core.1651139893.104  db  db-log  stobs

Additional information

Checklist

[x] The change is tested and works locally.
[ ] New or changed settings in the solution YAML are documented clearly in the README.md file.
[x] All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change addresses a CORTX Jira issue:

[x] The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

@papan-singh, I know this is a simple change,  but please fill out the info in the PR template as requested.

The change as-is looks good, but it should also be made in k8_cortx_cloud/cortx-cloud-helm-pkg/cortx-data/templates/cortx-data-cm-nodeconfig.yaml as well.
The prereq script is only a recommended reference approach to what a cluster is needed to have to run and is not required by the end user to be run. The nodeconfig script is included at startup time for each of the Data Pods and while redundant at the moment, is more likely the long-term landing place for anything in the prereq script that we will persist long-term.

incorporated


update the documentation of how to use in the homepage.

specifically remove the /src portion while importing.

Thanks for the PR


Chore: Rewrite cosmos client with osmojs RPC client

Only minor nitpicks review changes, LGTM!

Thanks for the feedback. I have updated the syntax accordingly. 👍
@gurbaj5124871


Set kanban board for SystemDS JIRA

https://confluence.atlassian.com/display/JIRASOFTWARESERVER083/Advanced+searching

Backlogs:

Board

Configure board:
1.

get quick filter syntax from search bar

Add as quick filter and description


Flex in vscode is error

@dxdleikai can you please hove on the error highlight, it will show cause of the error


Enabling PySpark as a data source

datashader enables meaningful visualization of big data, but these data must be made available through dask. Spark is much more widely deployed and, depending on setup and circumstance, it's not always possible to deploy dask.
This PR implements a pyspark.sql.dataframe as a data source for datashader. It works by bootstrapping the core pandas implementations on serialized pyspark.rdd partitions. There is a large serialization penalty paid, but future versions of pyspark will have improved support for data transfer from the JVM to Python using Apache Arrow.* The downside to this approach is that it's more complicated to deploy on a Spark cluster (e.g., using YARN) than a pyspark.sql-based approach would be.
I don't have tests included yet, and I have included pyspark as a dependency. My reading of the code suggests that both dask and pyspark should be installable as extras, rather than datashader core dependencies. I wanted to thoughts on the concept and eyes on the implementation early, in case large changes are necessary.
* There is some Arrow support in the current PySpark release (2.3). However, the two exposed methods (1) don't allow aggregation and (2) require a full dataframe shuffle prior to aggregation. I tried to hack (1) to work by using a pyspark.Accumulator, but it's not available to the Python process running the Arrow UDF. (2) can be used, but I feel that the required shuffle is a larger performance penalty than RDD serialization.
Additional -- I think I used the intended approach to extend datashader in this PR. This required bootstrapping existing code onto Spark using a non-preferred interface with lower performance characteristics. And this is only possible with something like Spark that supports Python computation pretty well.
There is a lot of data in the world in various storage systems. Data scientists often access these data through Python clients or APIs, but the amount of data they can bring back is limited by client system size.  I'd like to gauge interest in refactoring datashader a bit to allow a more extensible API so that "code can be taken to the data." For example, a better Spark implementation would be to use the SQL API to perform mapping and aggregation. This would improve performance and be much simpler to deploy. You could similarly envision an RDBMS implementation using some Python API (e.g., blaze) or client.

There is some Arrow support in the current PySpark release (2.3). However, the two exposed methods (1) don't allow aggregation and (2) require a full dataframe shuffle prior to aggregation. I tried to hack (1) to work by using a pyspark.Accumulator, but it's not available to the Python process running the Arrow UDF. (2) can be used, but I feel that the required shuffle is a larger performance penalty than RDD serialization.

Arrow is under very active development, so if you have suggestions for how to make it support what you need to do, please make sure they hear them!

Thanks for the review James. I'll be working on these over the course of the week.

@jbednar I think I have taken this as far as I can inside the current API. All PySpark tests are passing. I can't figure out why some of the trimesh tests are failing, I didn't make any changes. Let me know what else you need for this PR.

Uhhh I think I just realized there's a much cleaner way to do this. Closing for now.

Nevermind, it's late and I remembered why I had to go this way. Sorry for the spam.

Just picking this back up after a busy month. I added a usage notebook at examples/topics/pyspark-notes.ipynb. If you read through it, you'll see the big performance gap between the Spark implementation in this PR and Dask.
This code works, and I've tested it on a large cluster with 25 billion data points, but I'm not sure if it makes sense to merge this given the complications with deployment and obvious performance downsides. I don't know how to implement the orders of magnitude faster Spark-based computations without significant changes to the existing datashader codebase.


Add view source button on preview page

See also 917fd94fb31e95fdf6939bcf2432d894d9f5f074

This would be relatively simple to implement, we just need some icon for the button and decide where to put it.


Pre-loaded selections not binding with existing choices

If  the multi-select is preloaded with previous (saved) choices. The user is still able to select the choice again that are already preselected. See fig trees as an example where it can be selected again if it has already been preloaded into the select.

<ui-select multiple data-ng-model="product.selected" theme="bootstrap">
<ui-select-match placeholder="Products">{{$item.productName}}</ui-select-match>
<ui-select-choices repeat="p.id as p in products">

</ui-select-choices>
</ui-select>
//select options
$scope.products = [{"id":1,"productName":"Windows - Anderson"},{"id":2,"productName":"Doors"},{"id":3,"productName":"Fig Trees"}]
//Data for preloading select
$scope.product.selected = [2,1,3]

Closing. This plunker had everything i needed.
http://plnkr.co/edit/tHeHtwLddooe3WveH2yJ?p=preview


Unclear country input expectation for GraphQL checkout address attach mutation

What I'm trying to achieve
I'm trying to create an shipping or billing address via GraphQL checkout attach. But it's unclear what is expected in the AddressInput.country field.
Steps to reproduce the problem

Call Mutations.checkoutShippingAddressUpdate using string for country input like "USA", "United States"
We get back errors from Django GraphLQ saying that "invalid country code"

What I expected to happen
There seems to validation going on in saleor/graphql/account/i18n.py that checks country string with phone number as well as converts country string to country code and checks against list of valid country codes. The problem, I see here is that because the GraphQL API expects a any string, it's not obvious what the correct string should be. I would make it a just to expect the country code instead and link in the documentations what the expected values are to make it easier for developers.
Screenshots

https://www.dropbox.com/s/eow0x246dru5ga6/Screenshot 2019-07-16 13.22.55.png?dl=0
https://www.dropbox.com/s/02w3fxi1r1x38ih/Screenshot 2019-07-16 13.30.23.png?dl=0
System information
Operating system: MacOS
Browser: Chrome 75

It is expecting a two letter country code (ISO 3166-1), e.g. US, PL, FR, etc.

So it seems that there is a wrong input type for the country field in AddressInput type. Instead of String it should use the CountryCode enum.

Yea, I agree. I think it should be Enum of CountryCode to avoid confusion.


Build and install contrib classes

Hello @ramtingh,
I would like to have contrib classes enabled for vmtk. Contrib scripts are currently enabled, but contrib classes are turned off, which makes scripts like vmtkdistancetospheres fail. For example see the following output:
$ vmtkdistancetospheres -ifile input.vtp -ofile output.vtp

Automatic piping vmtkdistancetospheres
Parsing options vmtkdistancetospheres
    SurfaceInputFileName = input.vtp
    SurfaceOutputFileName = output.vtp
Explicit piping vmtkdistancetospheres
Input vmtkdistancetospheres members:
    Id = 0
    Disabled = 0
    Surface = None
    SurfaceInputFileName = input.vtp
    DistanceToSpheresArrayName = DistanceToSpheres
    DistanceOffset = 0.0
    DistanceScale = 1.0
    MinDistance = 0.0
    MaxDistance = -1.0
    Opacity = 1.0
    vmtkRenderer = None
    SurfaceOutputFileName = output.vtp
Reading VTK XML surface file.
Executing vmtkdistancetospheres ...
Please position the mouse and press space to add spheres, 'u' to undo
Quit renderer
Traceback (most recent call last):
  File "/home/johannr/miniconda3/envs/vmtk/lib/python3.10/site-packages/vmtk/pypeserver.py", line 48, in RunPypeProcess
    pipe.Execute()
  File "/home/johannr/miniconda3/envs/vmtk/lib/python3.10/site-packages/vmtk/pype.py", line 324, in Execute
    scriptObject.Execute()
  File "/home/johannr/miniconda3/envs/vmtk/lib/python3.10/site-packages/vmtk/vmtkdistancetospheres.py", line 355, in Execute
    self.Surface = self.ComputeDistances()
  File "/home/johannr/miniconda3/envs/vmtk/lib/python3.10/site-packages/vmtk/vmtkdistancetospheres.py", line 91, in ComputeDistances
    distanceToSpheresFilter = vtkvmtk.vtkvmtkPolyDataDistanceToSpheres()
AttributeError: module 'vmtk.vtkvmtk' has no attribute 'vtkvmtkPolyDataDistanceToSpheres'

In this example I open a file input.vtp using vmtkdistancetospheres and a window pops up as expected. I then add some spheres using space and then quit the program using q. The program fails because vtkvmtkPolyDataDistanceToSpheres is not available. This is because contrib classes were not enabled at build time. Setting -DVTK_VMTK_CONTRIB:BOOL=ON when configuring vmtk should fix this issue.
I see that contrib classes are explicitly turned off with -DVTK_VMTK_CONTRIB:BOOL=OFF on macOS and Windows, so I am not sure if enabling contrib will make the build fail on these platforms. I will make a pull request that enables contrib classes on Linux, but let me know if I should enable it on macOS and Windows as well.

@johannesring I believe the contrib classes were disabled as they weren't updated for new VTK and causing build issues, however as they seem to work fine on linux I don't think there's any problem with enabling them on linux for now. Thanks for the pull request!

Fixed in PR #18.


Option to push console logs to file

Pushing logs to file is not optional as of now. All logs are written to file but warnings and errors are written to console as well https://github.com/coding-yogi/bombardier/commit/4d40fd8cd194c20bd9b3d6e1c49f8463806c222b


Consider using musl.cc cross toolchain instead of crosstool-ng

I think http://musl.cc/ is a better choice, as musl is lightweight and easy to static link, and it's does not require a high version kernel and glibc.
Maybe also will resolve #104
Thanks.

Closing here. Using musl unfortunately isn't feasible for usable builds.

does not require a high version kernel and glibc.

Why is that good? Kernel and glibc are both very buggy, and lets not start on gcc. Insane bugs and 💩 code, at least they kinda had to have such insane code, especially glibc.


Rolemaster Unified Official: Some tweaks to creatures.

Remove a lot of debug in level up and stuff.
Allow creatures to be called NPCs on drop
Creatures (NPCS) now display spells

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.


Improvement: docs: corrected minutes grammactical errors in README.md

Changes proposed ✍
What
Corrected minute grammatical errors in README.md
Checklist ✅

[x] Label appropriately with Feature, Improvement, or Bug.
[ ] Add screenshots to the PR description for relevant FE changes
[ ] New backend functionality has been unit-tested.
[] API documentation has been updated (if necessary) (see docs on API documentation).
[] Quality standards are met.

@sausage-todd @joanagmaia
Pease review my PR and if according to the guidelines please do merge it :)

 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.


Make the @yamada-ui/toggle component headless

script: make-component-headless
package: @yamada-ui/toggle
Description
Currently, the @yamada-ui/toggle component has minimal styles set within the component's source code.
We want to make this style transferable to the theme and make the component headless, enabling more flexible UI customization.
Problem Statement/Justification
By making the @yamada-ui/toggle component headless, we can achieve more flexible styling tailored to the project.
Proposed Solution or API
The styles within the component are mostly defined by css: CSSUIObject and set to a prop named __css. We will transfer these styles to the packages/theme/src/components.
The code below is just an example and not the actual code.
packages/components/input/src/input-group.tsx
const css: CSSUIObject = {
- width: "100%",
- display: "flex",
- position: "relative",
  ...styles.container,
}

packages/theme/src/components/input.ts
baseStyle: {
  container: {
+   width: "100%",
+   display: "flex",
+   position: "relative",
  },
  field: {
    width: "100%",
    minWidth: 0,
    outline: 0,
    position: "relative",
    appearance: "none",
    transitionProperty: "common",
    transitionDuration: "normal",
    _disabled: {
      opacity: 0.4,
      cursor: "not-allowed",
    },
  },
  element: {
    color: ["blackAlpha.600", "whiteAlpha.700"],
  },
},

[!TIP]
In cases where the styles within the component are dynamically changed, there may be instances where it is not possible to transfer the styles to the theme.
In such cases, it needs to be discussed in this issue. Please feel free to send comments to this issue.

Additional Information
The @yamada-ui/toggle component exists in packages/components/toggle/src. You need to check all the components in this folder and if they contain styles internally, you need to modify them.
This change could have a significant impact on projects using Yamada UI, so we will work on it within the scope of v2.0.
Please create the branch for working on this issue from the remote branch v2.0, and direct your pull requests to the v2.0 branch as well.
Please select major for the changeset and create a pull request.

Hi @hirotomoyamada, can I work on this one?

@Hiroto1224
Hi, thanks for the comment!
Yes, pls.

Fixed #1921


ghc-8.8.x: jailbreak io-streams-haproxy

io-streams-haproxy build was failing due to overly restrictive uper bounds package versions. Tests are passing with just simple jailbreak.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

rebased after the force push to base branch.

@turboMaCk Could you report this upstream, and then add a comment and a link to the upstream issue/PR in the configuration-ghc-8.8.x.nix file?  This will help the nixpkgs maintainers know when the jailbreak can be removed.

sure will do @cdepillabout. PLS wait with merge until the furher notice

@cdepillabout it should be done. Thanks for the good point I will be adding this to all similar PRs going forward. Let me know if there is something else I can do. Also I don't think this merge is supper important so we can wait until upstream accepts the change as well if you wish.

@turboMaCk Thanks!
@peti This should be ready to merge.
Or, like @turboMaCk says, we can just wait for https://github.com/snapframework/io-streams-haproxy/pull/17 to be merged, which should fix this.  Then we could just close this PR.


[RESTEASY-3266] RestEasy JSAPI Servlet does not work with root "/" or empty @ApplicationPath("")

https://issues.redhat.com/browse/RESTEASY-3266

Hello, petrberan. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

looks good!

Thanks @jamezp Licence headers added


Re-enable 'test:realsvc' on Tinylicious after addressing stability issues

Describe the bug
Not specific to code coverage.  Running test:realsvc often fails 1 or 2 tests from AgentScheduler and/or DetachedContainer.
This was blocking ci:test:coverage and consequently publishing and downstream ODSP tests, so I've modified 'test:report' in the root package.json to exclude 'test:realsvc' for now.
To Reproduce
Steps to reproduce the behavior:

npm run test:realsvc

Logs
Example log from a bad run:
@fluidframework/test-end-to-end-tests:   1) AgentScheduler
@fluidframework/test-end-to-end-tests:        compat N-2 - new driver
@fluidframework/test-end-to-end-tests:          Single client
@fluidframework/test-end-to-end-tests:            "before each" hook for "Can pick tasks":
@fluidframework/test-end-to-end-tests:      Uncaught Error: read ECONNRESET
@fluidframework/test-end-to-end-tests:       at createR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:19:20)
@fluidframework/test-end-to-end-tests:       at Object.throwR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:35:26)
@fluidframework/test-end-to-end-tests:       at RouterliciousStorageRestWrapper.request (/workspaces/f2/packages/drivers/routerlicious-driver/dist/restWrapper.js:61:26)
@fluidframework/test-end-to-end-tests:       at runMicrotasks (<anonymous>)
@fluidframework/test-end-to-end-tests:       at processTicksAndRejections (internal/process/task_queues.js:97:5)
@fluidframework/test-end-to-end-tests:   2) AgentScheduler
@fluidframework/test-end-to-end-tests:        compat N-2 - new driver
@fluidframework/test-end-to-end-tests:          Multiple clients
@fluidframework/test-end-to-end-tests:            "before each" hook for "No tasks initially":
@fluidframework/test-end-to-end-tests:      Error: read ECONNRESET
@fluidframework/test-end-to-end-tests:       at createR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:19:20)
@fluidframework/test-end-to-end-tests:       at Object.throwR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:35:26)
@fluidframework/test-end-to-end-tests:       at RouterliciousOrdererRestWrapper.request (/workspaces/f2/packages/drivers/routerlicious-driver/dist/restWrapper.js:61:26)
@fluidframework/test-end-to-end-tests:       at runMicrotasks (<anonymous>)
@fluidframework/test-end-to-end-tests:       at processTicksAndRejections (internal/process/task_queues.js:97:5)
@fluidframework/test-end-to-end-tests:   3) AgentScheduler
@fluidframework/test-end-to-end-tests:        compat N-2 - old container runtime
@fluidframework/test-end-to-end-tests:          Single client
@fluidframework/test-end-to-end-tests:            "before each" hook for "No tasks initially":
@fluidframework/test-end-to-end-tests:      Error: socket hang up
@fluidframework/test-end-to-end-tests:       at createR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:19:20)
@fluidframework/test-end-to-end-tests:       at Object.throwR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:35:26)
@fluidframework/test-end-to-end-tests:       at RouterliciousOrdererRestWrapper.request (/workspaces/f2/packages/drivers/routerlicious-driver/dist/restWrapper.js:61:26)
@fluidframework/test-end-to-end-tests:       at runMicrotasks (<anonymous>)
@fluidframework/test-end-to-end-tests:       at processTicksAndRejections (internal/process/task_queues.js:97:5)
@fluidframework/test-end-to-end-tests:   4) AgentScheduler
@fluidframework/test-end-to-end-tests:        compat N-2 - new driver
@fluidframework/test-end-to-end-tests:          Single client
@fluidframework/test-end-to-end-tests:            "before each" hook for "Can pick tasks":
@fluidframework/test-end-to-end-tests:      done() called multiple times in hook <AgentScheduler compat N-2 - new driver Single client "before each" hook for "Can pick tasks"> of file /workspaces/f2/packages/test/test-end-to-end-tests/dist/test/agentScheduler.spec.js; in addition, done() received error: Error: Runtime is closed
@fluidframework/test-end-to-end-tests:     at RuntimeWithRequestHandler.verifyNotClosed (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:671:19)
@fluidframework/test-end-to-end-tests:     at RuntimeWithRequestHandler.submit (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:598:14)
@fluidframework/test-end-to-end-tests:     at RuntimeWithRequestHandler.submitChannelOp (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:595:14)
@fluidframework/test-end-to-end-tests:     at /workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:231:203
@fluidframework/test-end-to-end-tests:     at ChannelDeltaConnection.submitFn (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/channelContext.js:13:126)
@fluidframework/test-end-to-end-tests:     at ChannelDeltaConnection.submit (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/channelDeltaConnection.js:52:14)
@fluidframework/test-end-to-end-tests:     at SharedDirectory.submitLocalMessage (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/shared-object-base/dist/sharedObject.js:229:43)
@fluidframework/test-end-to-end-tests:     at SharedDirectory.submitDirectoryMessage (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:355:14)
@fluidframework/test-end-to-end-tests:     at SubDirectory.submitKeyMessage (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:1002:24)
@fluidframework/test-end-to-end-tests:     at SubDirectory.set (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:718:14)
@fluidframework/test-end-to-end-tests:     at SharedDirectory.set (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:227:19)
@fluidframework/test-end-to-end-tests:     at Context.<anonymous> (/workspaces/f2/packages/test/test-end-to-end-tests/dist/test/agentScheduler.spec.js:28:30)
@fluidframework/test-end-to-end-tests:     at runMicrotasks (<anonymous>)
@fluidframework/test-end-to-end-tests:     at processTicksAndRejections (internal/process/task_queues.js:97:5)
@fluidframework/test-end-to-end-tests:   Error: done() called multiple times in hook <AgentScheduler compat N-2 - new driver Single client "before each" hook for "Can pick tasks"> of file /workspaces/f2/packages/test/test-end-to-end-tests/dist/test/agentScheduler.spec.js; in addition, done() received error: Error: Runtime is closed
@fluidframework/test-end-to-end-tests:       at RuntimeWithRequestHandler.verifyNotClosed (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:671:19)
@fluidframework/test-end-to-end-tests:       at RuntimeWithRequestHandler.submit (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:598:14)
@fluidframework/test-end-to-end-tests:       at RuntimeWithRequestHandler.submitChannelOp (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:595:14)
@fluidframework/test-end-to-end-tests:       at /workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/dataStoreRuntime.js:231:203
@fluidframework/test-end-to-end-tests:       at ChannelDeltaConnection.submitFn (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/channelContext.js:13:126)
@fluidframework/test-end-to-end-tests:       at ChannelDeltaConnection.submit (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/datastore/dist/channelDeltaConnection.js:52:14)
@fluidframework/test-end-to-end-tests:       at SharedDirectory.submitLocalMessage (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/shared-object-base/dist/sharedObject.js:229:43)
@fluidframework/test-end-to-end-tests:       at SharedDirectory.submitDirectoryMessage (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:355:14)
@fluidframework/test-end-to-end-tests:       at SubDirectory.submitKeyMessage (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:1002:24)
@fluidframework/test-end-to-end-tests:       at SubDirectory.set (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:718:14)
@fluidframework/test-end-to-end-tests:       at SharedDirectory.set (/workspaces/f2/packages/test/test-version-utils/node_modules/.legacy/0.38.4/node_modules/@fluidframework/map/dist/directory.js:227:19)
@fluidframework/test-end-to-end-tests:       at Context.<anonymous> (dist/test/agentScheduler.spec.js:28:30)
@fluidframework/test-end-to-end-tests:       at runMicrotasks (<anonymous>)
@fluidframework/test-end-to-end-tests:       at processTicksAndRejections (internal/process/task_queues.js:97:5)
@fluidframework/test-end-to-end-tests:       at runMicrotasks (<anonymous>)
@fluidframework/test-end-to-end-tests:       at processTicksAndRejections (internal/process/task_queues.js:97:5)
@fluidframework/test-end-to-end-tests:   5) Detached Container
@fluidframework/test-end-to-end-tests:        compat N-2 - old data runtime
@fluidframework/test-end-to-end-tests:          Load attached container and check for dataStores:
@fluidframework/test-end-to-end-tests:      Error: socket hang up
@fluidframework/test-end-to-end-tests:       at createR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:19:20)
@fluidframework/test-end-to-end-tests:       at Object.throwR11sNetworkError (/workspaces/f2/packages/drivers/routerlicious-driver/dist/errorUtils.js:35:26)
@fluidframework/test-end-to-end-tests:       at RouterliciousOrdererRestWrapper.request (/workspaces/f2/packages/drivers/routerlicious-driver/dist/restWrapper.js:61:26)

I believe this is caused by port exhaustion because of TIME_WAIT delay on TCP sockets disconnection.

did we ever figure out the problem here. will #7909  help?

@justus-camp this is done, right? should we close this?

Yeah this is done. I messed up the "fixes" syntax in the PR that should've closed this one


Limit of 50 sources

getContentList only returns 50 items. We need to loop the request using cnt and stIdx parameters to get the next batch and so on until last one is returned.

Fix is here:
https://github.com/aparraga/braviarc/pull/9


dot in query string causes "Unsupported Referer" via checkWildcardSubdomain()

Been chasing down 403s from 1.1.0 version using allowedReferers="//*.domain.com".  URLs with coords that have dot failed referer checking.  checkWildcardSubdomain() splits on dot to make part comparisons to allowedReferer, and requestedReferer can have a query sting with a dot.  suggest chopping off query string before comparison

Hi @aaronkilbey, thanks for the suggestions. We are aware of this bug and are trying to fix it in the next release. Will update here about the specific pull request in case you want to manually apply the patch. Thanks

@aaronkilbey can you tell us which proxy are you using? DotNet or JSP?

DotNet on 2012/IIS 8.5.  Also, in evaluating responses for this, I noticed the error return has IIS HTML output after the JSON "Server Error in '/' Application...''.  Fixed by response.End(); at the end of sendErrorResponse().  (I know barely enough asp to debug this otherwise I'd pull request)

This is fixed by #285 and can be closed! Thanks @aaronkilbey


switch to docker registry to GCEME app

The gceme sample app does not appear to exist on Google Container Registry anymore.
We're getting ImagePullBackOff errors and this is causing issues for material that uses this repo.

Thanks for the contribution!


Monkey patching error

Prerequisites

[X] I am using the latest version of Locust
[X] I am reporting a bug, not asking a question

Description
C:\Customs\python\python312\Lib\site-packages\locust_init_.py:15: MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. It may also silently lead to incorrect behaviour on Python 3.7. Please monkey-patch earlier. See https://github.com/gevent/gevent/issues/1016. Modules that had direct imports (NOT patched): ['urllib3.util.ssl_ (C:\Customs\python\python312\Lib\site-packages\urllib3\util\ssl_.py)', 'urllib3.util (C:\Customs\python\python312\Lib\site-packages\urllib3\util\init.py)'].
Command line
locust -f mylocustfile.py -t 10s --headless
Locustfile contents
\locust\__init__.py:15: MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. It may also silently lead to incorrect behaviour on Python 3.7. Please monkey-patch earlier. See https://github.com/gevent/gevent/issues/1016. Modules that had direct imports (NOT patched): ['urllib3.util.ssl_ (C:\\Customs\\python\\python312\\Lib\\site-packages\\urllib3\\util\\ssl_.py)', 'urllib3.util (C:\\Customs\\python\\python312\\Lib\\site-packages\\urllib3\\util\\__init__.py)'].

Python version
3.12
Locust version
2.24.1
Operating system
Windows

Make sure to import locust before other imports.

it fixed, thanks

issue does not appear after moving the import locust to the begining


"Unhandled Promise rejection: SyntaxError: Unexpected token import"

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Component should load MdButton from "2angular2-material/button" and display the UI.
What is the current behavior?
Doesn't render anything and gives error on console
zone.js:461 Unhandled Promise rejection: SyntaxError: Unexpected token import
	    at Object.eval (http://localhost:3000/app/navbar/navbar.component.js:12:16)
	    at eval (http://localhost:3000/app/navbar/navbar.component.js:37:4)
	    at eval (http://localhost:3000/app/navbar/navbar.component.js:38:3)
	Evaluating<EMAIL_ADDRESS>	Evaluating http://localhost:3000/app/navbar/navbar.component.js
	Evaluating http://localhost:3000/app/app.component.js
	Evaluating http://localhost:3000/app/index.js
	Evaluating http://localhost:3000/main.js
	Error loading http://localhost:3000/main.js ; Zone: <root> ; Task: Promise.then ; Value: Error: SyntaxError: Unexpected token import(…)consoleError @ zone.js:461_loop_1 @ zone.js:490drainMicroTaskQueue @ zone.js:494ZoneTask.invoke @ zone.js:426
zone.js:463 Error: Uncaught (in promise): Error: SyntaxError: Unexpected token import(…)

What are the steps to reproduce?
initi project using angular-cli and follow instructions on 3rd library installation instructions given on the angular-cli github page to set up material 2 components, and trying using any of the material 2 directives in a component. In my case:
import { Component } from '@angular/core';
import { MdButton } from '@angular2-material/button';

@Component({
  moduleId: module.id,
  selector: 'app-navbar',
  templateUrl: 'navbar.component.html',
  styleUrls: ['navbar.component.css'],
  directives: [MdButton]
})
export class NavbarComponent {
  navItems : Array<string> = [
    'About',
    'Services',
    'Policies',
    'Fees',
    'Contact'
  ]
}

Which versions of Angular, Material, OS, browsers are affected?
Angular: rc4
Material: ^2.0.0-alpha.8-1
Browser: Chrome
OS: Windows10
Is there anything else we should know?
This has taken me all day and still couldn't fix..

@javascriptonian the problem might be because you use Angular RC4 with alpha.8 which might not be compatible due to alignments with the latest Angular RCs. Also, make sure you run TypeScript 2.0 as it's the requirement for material2 alpha.8

Same issue here.
Angular: 2.0.0-rc.6
Material: 2.0.0-alpha.8-1
Browser: Chrome
OS: macOS 10.11
Typescript: 2.0.0

@richardklose that's not a possible fix, that's what you should do. Check CHANGELOG.md for alpha.8

@m0t0r is right; if you still want the CommonJS output, use the umd bundles from alpha.8 forward.
(also alpha.8 does depend on Angular RC6 or greater)


Make file storage backend's atomic rename async

Description
This change tries to make the atomic rename operation async.
Related Issue(s)

closes #369
Documentation

thread 'concurrent_writes_fs' panicked at 'called `Result::unwrap()` on an `Err` value: StorageError { source: Io { source: Custom { kind: Other, error: "failed to rename ./tests/data/concurrent_workers\\_delta_log\\_commit_1f8a32c2-c9da-45f3-948a-d46e154c0fb2.json.tmp to ./tests/data/concurrent_workers\\_delta_log\\00000000000000000007.json: Access is denied. (os error 5)" } } }', rust\tests\concurrent_writes_test.rs:114:31
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'concurrent_writes_fs' panicked at 'called `Result::unwrap()` on an `Err` value: JoinError::Panic(...)', rust\tests\concurrent_writes_test.rs:54:28

Is this related error? Seems not. Can we rerun the test?


add a JD vector database: vearch

I added an open source vector database from JD: Vearch.
Vearch provides a well-developed REST interface that can be used in Java projects, just like chromadb.
Here's the code address for vearch: https://github.com/vearch/vearch
The documentation address: https://vearch.readthedocs.io/en/latest/

Hi @z199172177 thank you so much! Please note that there is already this https://github.com/langchain4j/langchain4j/pull/525


Added support for tags to consul discovery

Hi @brian-brazil,
We are using Consul for the service discovery. We cannot maintain a static configuration file with all the services since they are dynamically added or removed. The services which need to be monitored typically are tagged in consul with the tag "metrics".
We have extended the consul-discovery module in prometheus, so you can add tags to the configuration. All the services with this tag will be scraped. This greatly simplifies our setup and scraping process. Up til now, we had a job which rewrites the prometheus.yml and reload this configuration.
An example of the new configuration looks like:
consul_sd_configs:
- server: 'consul:8500'
  services:
  - 'cadvisor'
  - 'node-exporter'
  - 'consul-exporter'
  tags:
  - 'metrics'

The combination of services and tags works in an "OR"-fashion.

That's a use case for relabeling
https://www.robustperception.io/finding-consul-services-to-monitor-with-prometheus/
On Mon, May 15, 2017 at 3:36 PM Jan De Cooman<EMAIL_ADDRESS>wrote:

Hi @brian-brazil https://github.com/brian-brazil,
We are using Consul for the service discovery. We cannot maintain a static
configuration file with all the services since they are dynamically added
or removed. The services which need to be monitored typically are tagged in
consul with the tag "metrics".
We have extended the consul-discovery module in prometheus, so you can add
tags to the configuration. All the services with this tag will be
scraped. This greatly simplifies our setup and scraping process. Up til
now, we had a job which rewrites the prometheus.yml and reload this
configuration.
An example of the new configuration looks like:
consul_sd_configs:

server: 'consul:8500'
services:

'cadvisor'
'node-exporter'
'consul-exporter'
tags:
'metrics'

The combination of services and tags works in an "OR"-fashion.
You can view, comment on, or merge this pull request online at:
https://github.com/prometheus/prometheus/pull/2720
Commit Summary

Added tags to consul discovery

File Changes

M config/config.go
https://github.com/prometheus/prometheus/pull/2720/files#diff-0 (3)
M discovery/consul/consul.go
https://github.com/prometheus/prometheus/pull/2720/files#diff-1 (42)

Patch Links:

https://github.com/prometheus/prometheus/pull/2720.patch
https://github.com/prometheus/prometheus/pull/2720.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prometheus/prometheus/pull/2720, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAANaKM1dOJf8W_90wZTtHnV7sA5Au_4ks5r6FTagaJpZM4NbJM3
.

Good point, learned about action: keep :1st_place_medal:


Refactor Position#move to work correctly when prev/next is list section

The moveRight and moveLeft methods on Position are now smarter about moving to prev/next leaf sections.
Changes most of the card-related cursor movement tests to use assert.positionIsEqual.
fixes #270

:clap: :clap: :clap: :clap: :clap:


Bump version to 4.0.0

Describe the changes
Bump version to 4.0.0

Why would you bump the version, version 4.0.0 will be released once it is ready...

Because when you download the package with npm or yarn it doesn't download the latest version from the repo, also the readme file references version 4.0.0 :)


(demo): add create_rsa_keypair.sh for account manager

Codecov Report

Merging #420 (16620c7) into release-1.0.0 (f53f818) will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             release-1.0.0     #420   +/-   ##
================================================
  Coverage            14.98%   14.98%
  Complexity             397      397
================================================
  Files                  180      180
  Lines                 8074     8074
  Branches               664      664
================================================
  Hits                  1210     1210
  Misses                6777     6777
  Partials                87       87


Replace Request Lib

Request is deprecated and should be replaced with an alternative like fetch or node-fetch.

Hi @flyboarder and thanks for reaching out! As of Feb 11th 2020, request is fully deprecated. No new changes are expected land. We've looked into information about why request is deprecated and will explore possible alternatives.
This GitHub issue will remain open until we refactor the NodeJS SDK with a request alternative in the future.
Please be on the look out for any pull requests that are created to resolve this issue.

This package is causing a "High" npm vulnerability report because of request

Hi @thallada We will prioritize this to be reviewed and resolved within the next quarter. Please be on the look out for any pull requests that are created to resolve this issue.
Thanks!


Looking for XML based configuration for the same.

Hi,
Do we have an XML based configuration to implement ShadLock over my scheduler? I am not using core spring. My application is built on Liferay and I am using Liferay spring portlet.

There used to be support for XML config up to ShedLock 2.6.0. So you can either use old version or use this https://github.com/lukas-krecan/ShedLock#locking-without-a-framework


[Issue #48] Fix rootlocation goal.

see discussion in #48 - this PR does only work if the root/aggregator pom is also the parent pom
i've created PR #92 as a replacement


[Bug Report] Form inputs validation on disabled inputs

Element UI version
2.14.1
OS/Browsers version
Any
Vue version
2.6.12
Reproduction Link
https://codepen.io/pen/OJROEgy
Steps to reproduce
Make a form, make validations, disable some elements
What is Expected?
Disabled elements should not be considerable
What is actually happening?
Wont let submit the form because Input is required but same time disabled. This is Bad logic.

You can disabled the button when form item is invalid by yourself.ElementUI is component library only.

I know, but when you have a form with a fieldset or checkbox that enables 2 more fields even if fields are disabled they are still being validated. let me give an example.
registration form
2 radio
O - register as individual
O - register as business
if register as business is checked I want to enable Business number field else stays disabled.
Now validation rules have that field
rules : { business:{ required: true }}
This rule should not be consider if field is disabled because it wont allow form submit.
I dont know if async validation package issue or element,  but all it need is an if (field disabled) dont consider rule where rules and fields are checked.

I know, but when you have a form with a fieldset or checkbox that enables 2 more fields even if fields are disabled they are still being validated. let me give an example.
registration form
2 radio
O - register as individual
O - register as business
if register as business is checked I want to enable Business number field else stays disabled.
Now validation rules have that field
rules : { business:{ required: true }}
This rule should not be consider if field is disabled because it wont allow form submit.
I dont know if async validation package issue or element,  but all it need is an if (field disabled) dont consider rule where rules and fields are checked.


Shape of get_sequence_output() is wrong

I'm running this code (only relevant part) :
xlnet_config = xlnet.XLNetConfig(json_path=FLAGS.model_config_path)
  run_config = xlnet.create_run_config(is_training, True, FLAGS)

  print(inp_k)
  print(seg_id)
  print(inp_mask)
  print(mems)
  print(perm_mask)
  print(target_mapping)
  print(inp_q)

  xlnet_model = xlnet.XLNetModel(
      xlnet_config=xlnet_config,
      run_config=run_config,
      input_ids=inp_k,
      seg_ids=seg_id,
      input_mask=inp_mask,
      mems=mems,
      perm_mask=perm_mask,
      target_mapping=target_mapping,
      inp_q=inp_q)

  output = xlnet_model.get_sequence_output()
  print("THIS IS MEGADEBUG : {}".format(output))

and the output of this code is : (on TPU)

Tensor("transpose:0", shape=(640, 1), dtype=int32)                   # inp_k
Tensor("transpose_2:0", shape=(640, 1), dtype=int32)                  # seg_id
Tensor("transpose_3:0", shape=(640, 1), dtype=float32)               # inp_mask
None                                                                                # mem
Tensor("transpose_4:0", shape=(640, 640, 1), dtype=float32)        # perm_mask
Tensor("transpose_5:0", shape=(126, 640, 1), dtype=float32)        # target_mapping
Tensor("transpose_1:0", shape=(640, 1), dtype=float32)               # inp_q
THIS IS MEGADEBUG : Tensor("model/transformer/dropout_3/dropout/mul_1:0", shape=(126, 1, 1024), dtype=float32)

According to the comments of the class XLNetModel, my input's shape are correct.
But why my output has this shape ? According to comments of get_sequence_output(), the output shape should be [640, 1, 1024], not [126, 1, 1024]
Any guidance is welcome :)

This is happening because your target_mapping has size 126.
Looking at the docs for transformer_xl, we can see that target_mapping has the following description:
    ...
    target_mapping: float32 Tensor in shape [num_predict, len, bsz].
      If target_mapping[i, j, k] = 1, the i-th predict in batch k is
      on the j-th token.
      Only used during pretraining for partial prediction.
      Set to None during finetuning.
    ...

Since the size of target_mapping is (126, 640, 1), the size of the output is (126, 1, 1024).

Thanks for your input @lukemelas !
However, I still don't understand. From the comments :

target_mapping is supposed to be [num_predict, len, bsz].
In my case it is [126, 640, 1], so we have : num_predict = 126, len = 640 and bsz = 1
get_sequence_output is supposed to be [len, bsz, d_model].
So in my case, it should be [640, 1, 1024]. But it is [126, 1, 1024]

Is the comment of get_sequence_output wrong ? The real output size is [num_predict, bsz, d_model] ?


Improve logging or store questions in db for audit purposes

Current logging is left to be desired. We need to improve logging to enhance our capability of auditing the questions asked in order to imrpove the chatbot/myssc+ content.
Tasks

[ ] create TF template for a database that will receive the data.
[ ] log every request made to the server (payload sent, etc) to the db
[ ] log every response made by the server  to the db

BONUS

[ ] investigate if we can control headers we receive to the app from the reverseproxy/idp authentication flow (user id/or other information for stats purpose (unique users, etc)

In relation to https://github.com/dto-btn/ssc-assistant/issues/57


Replace Snowpark with SQLAlchemy

Snowpark is...

not compatible with apple silicon right now
only works with up to Python 3.8
slow
uses its own DataFrame structure which needs to be converted to Pandas DataFrame (or whatever else you want to use) -> this conversion sometimes crashes Python
needs you to import a number of similarly named packages and subpackages, which adds even more confusion

Sqlalchemy has none of these issues. We should switch all functions over from snowpark to sqlalchemy.

Done. Closing.


Function.prototype.name is not supported in IE

Closes https://github.com/blainekasten/enzyme-matchers/issues/81

Ping?

Sorry @juanca, pretty busy at work lately. I'll merge this and try to release a new version soon

Sorry @juanca, pretty busy at work lately. I'll merge this and try to release a new version soon


Door sensor (mcs or qt?) not reporting battery status

Describe the bug
I have 2 door sensors (mcs) one has a second entity that reports battery % the other doesn't.
Expected behavior
2nd door sensor to have a second entity for battery %
Home Assistant Version

2021.8.8

Device info (please complete the following information, which can be found in log):
{
"active_time":<PHONE_NUMBER>,
"biz_type": 18,
"category": "mcs",
"create_time":<PHONE_NUMBER>,
"icon": "smart/product_icon/qt.png",
"id": "00112223807d3a2a2e39",
"ip": "***",
"lat": "***",
"local_key": "***",
"lon": "***",
"model": "",
"name": "Front door",
"online": true,
"owner_id": "4826775",
"product_id": "7by9ERqg60JA8wxA",
"product_name": "Door Sensor",
"status": [
{
"code": "doorcontact_state",
"value": false
},
{
"code": "battery_value",
"value": 73
}
],
"sub": false,
"time_zone": "+00:00",
"uid": "***",
"update_time":<PHONE_NUMBER>,
"uuid": "00112223807d3a2a2e39"
},

Device specifications (please complete the following information, which can be found in log):
2021-08-27 22:03:37 DEBUG (SyncWorker_4) [tuya iot] Request: method = GET, url = https://openapi.tuyaeu.com/v1.0/devices/00112223807d3a2a2e39/specifications, params = None, body = None, t =<PHONE_NUMBER>319
2021-08-27 22:03:37 DEBUG (SyncWorker_4) [tuya iot] Response: {
"result": {
"category": "mcs",
"functions": [],
"status": [
{
"code": "doorcontact_state",
"type": "Boolean",
"values": "{}"
},
{
"code": "battery_value",
"type": "Integer",
"values": "{\"unit\":\"v\",\"min\":0,\"max\":1000,\"scale\":-2,\"step\":1}"
}
]
},
"success": true,
"t":<PHONE_NUMBER>388
}

Additional context
A few notes:

The door sensor that has the second entity for battery %, when debugging it on iot.tuya.com I can see that the DPCODE is batter_percentage however the second door sensor that doesn't report batter % has the DPCODE battery_value, which is OK but when setting it up under sensor.py on the tuya_2 folder like the below:
DPCODE_BATTERY_VALUE = "battery_value"

    if DPCODE_BATTERY_VALUE in device.status:
                entities.append(
                    TuyaHaSensor(
                        device,
                        device_manager,
                        DEVICE_CLASS_BATTERY,
                        DPCODE_BATTERY_VALUE,
                        PERCENTAGE,
                    )
                )

It doesn't work, a second entity is created but just shows "unavailable"

Also to point out when debugging the second door sensor (the one without the battery status) on iot.tuya.com the "Product Category" is set as "qt" however HA reports it as "mcs", which is quite bizarre but adding the "qt" category in sensor.py doesn't seem to change anything.

battery_value is not supported in v1.5.0. But will be supported soon.
Can you try the master branch?

HI @tsutsuku tried the master branch but no cigar, I'll wait do be added no worries ;)

This has been addressed and added/fixed with the Home Assistant Core version of the integration and is pending release with Home Assistant 2021.11.


Fixed Pull Request for Mac OS updates.

1. Rename plist to proper name (broken in master)
2. Add support for node['chef_client']['task']['user'].

Again, suggestions welcome for where to store the user. Root is not appropriate to run chef as on Mac OS for most configurations.

I guess I'll consider this a fork rather than a pull request then.

So here's the thing, in my opinion.
This is a cookbook that tries to do too much. It needs to be refactored to provide a resource, chef_client_service that has platform specific providers for managing a service in the "native" way for said platforms. It needs fewer node attributes. It needs to not be responsible for managing log rotation, or scheduled tasks/cron setup of chef-client runs. Likewise, there should be a chef_client_config resource that works similarly.
Flexibility to run as a non-privileged user would be nice, but I think we should have the refactoring done before we approach that, as I think it can be done in a clean, cross platform way.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@danieljimenez

Please sign the CLA here.

I think this may conflict with #294's changes and not merge cleanly.

@danieljimenez are you still working on this?

No response in some time so I assume OP is no longer interested in this.

I am interested but unable to find a working solution or everyone.


How to turn the 10 mass bots to fb?

I have no idea how to make my bots fb

Cookies :)

Cookies?
On 24 Apr 2016 17:28, "JakeTDC"<EMAIL_ADDRESS>wrote:

Cookies :)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/davidmann4/ogar-feeder-bot/issues/473#issuecomment-213997044

Yes cookiiiiiiiies

For real... tell me.

For making mass bots you need facebook accounts.. and what most ppl. here do is to steal users cookies to use their account as bots.

And how do you do that...

I do that :D

Good for you, have a cookie.

Can u make a little vid or something? ?

He steals cookies... meaning he codes an extension/script and gives it out to users calling it free bots.. then he gets the cookies of those users that used it.

But where do you put the cookies and stuff...

just wait for his video of 'free bots' :D

Do you have skype, I really need help.

sejo.dedic4 I can tell you from where you get cookies, and where you put it, but you will still be without fb bots

My bots stopped working nvm


Fix regex double escaping of rabbitmqctl list_policies

+1

I have tested this patch and it fixes the problem for us we no longer get an update on each run:
before patch we get the below every run
/Stage[main]/manage_rabbitmq::Federation/Rabbitmq_policy[eu-federation@vhost]/pattern: pattern changed '^eu\.' to '^eu.'

@sspreitzer could you add some unit tests for this?

Ok well i have no idea how add more to a pull request but here is some tests
spec_test.patch.txt
Theses have not been tested as "you guys and your crazzy Beaker"

If folks don't mind, I added @DrOwl's test (with attribution to @sspreitzer for the whole commit, couldn't figure out how to break it up) and resubmitted as #561


Feedback for “Tools and Plugins”

The website describes which plug-ins are supported. However, I am missing instructions on how to configure these plug-ins.

Plugins will be deprecated soon in favor of "Agents"


0.10 Release notes should mention breaking changes caused by switch to coroutine listeners

While the coroutine listeners are mostly equivalent, upgrading to 0.10 requires updating import statements, and also some behavior has changed because of the lack of return values. Most problematic is something like the following:
onEditorAction { _, _, _
  // do something
  true
}

This will continue to compile with the coroutine listener, but the true return value is ignored, so the behavior will change unless it's updated to onEditorAction(returnValue = true) {....
It's also no longer possible to make the return value change based on the inputs, such as the event type unless I'm missing something.

My bad- didn't see the note about anko--listeners


[DOCS]: No proper info on how to use createBillingAgreement with PayPalButtons

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
https://paypal.github.io/react-paypal-js/?path=/docs/example-paypalbuttons--default
Describe the problem
I need to create a Billing Agreement ID with PayPalButtons and I cannot find any relevant information on how to do it. I cannot find any docs on createBillingAgreement for PayPalButtons either.
Describe the improvement
Add use cases with createBillingAgreement
Anything else?
No response

I try to add Button with intent = "tokenize"
and can't find proper  info about createBillingAgreement in <PayPalButtons>

Hi @alexdonets, here you can find an example

that example is only for BraintreePayPalButtons only, not for PayPalButtons

yep, you can't use createBillingAgreement  in PayPalButtons
I think you should use BraintreePayPalButtons or use some Braintree libs

Hi @alexdonets, here you can find an example

The issue with Braintree is that they don't authorize anyone as a merchant that easily and if your application doesn't get approved - you can't use their tools.

So I actually found a solution for this. I ended up implementing createBillingAgreement actions manually in the handler.
createBillingAgreement={async () => {
                    // Start Checkout and create a billing token
                    const { TOKEN } = await (await fetch('/api/paypal/authorize')).json();

                    authBillingToken = TOKEN;

                    return TOKEN;
}}

where /api/paypal/authorize is an endpoint I created in my app.
import { EURO_CODE } from '@app/account/constants';
import paypal from '@core/paypal/client';

// Types
import { NextApiRequest, NextApiResponse } from 'next';

const authorize = async (req: NextApiRequest, res: NextApiResponse) => {
    if (req.method === 'GET') {
        try {
            const query = {
                PAYMENTREQUEST_0_AMT: 0, // Set this field to 0 if the transaction does not include a one-time purchase such as when you set up a billing agreement for a recurring payment that is not immediately charged.
                PAYMENTREQUEST_0_CURRENCYCODE: EURO_CODE,
                PAYMENTREQUEST_0_PAYMENTACTION: 'AUTHORIZATION',
                RETURNURL: '', // add your returnUrl
                CANCELURL: '', // add your cancelUrl
                L_BILLINGTYPE0: 'MerchantInitiatedBilling',
                L_BILLINGAGREEMENTDESCRIPTION0: '', // add your billing description
            };

            const auth = await paypal.request('SetExpressCheckout', query);

            res.status(200).json(auth);
        } catch (err) {
            res.status(500).json(err);
        }
    } else {
        res.setHeader('Allow', 'GET');
        res.status(405).end('Method Not Allowed');
    }
};

export default authorize;

After this, we get a billing token in onApprove and create an actual billing agreement in the handler:
onApprove={async (data, actions) => {
                    await handleApprove(data.billingToken);
}}

const handleApprove = async (billingToken: string) => {
        try {
            // Create Billing Agreement
            const { BILLINGAGREEMENTID } = await (
                await fetch('/api/paypal/create-billing-agreement', {
                    method: 'POST',
                    headers: {
                        'Content-Type': 'application/json',
                    },
                    body: JSON.stringify({ token: billingToken }),
                })
            ).json();

            await dispatch(
                createSubscription({
                    gateway: 'paypal',
                    paymentToken: BILLINGAGREEMENTID
                    // whatever other data
                }),
            );
        } catch (err) {
            setError(err);
        }
    };

where /api/paypal/create-billing-agreement is another endpoint I created locally:
import paypal from '@core/paypal/client';

// Types
import { NextApiRequest, NextApiResponse } from 'next';

const createBillingAgreement = async (req: NextApiRequest, res: NextApiResponse) => {
    if (req.method === 'POST') {
        const { token } = req.body;

        try {
            const query = {
                TOKEN: token,
            };

            const billingAgreement = await paypal.request('CreateBillingAgreement', query);

            res.status(200).json(billingAgreement);
        } catch (err) {
            res.status(500).json(err);
        }
    } else {
        res.setHeader('Allow', 'POST');
        res.status(405).end('Method Not Allowed');
    }
};

export default createBillingAgreement;


Automate velero secret deployment

By adding a new policy and placement to deliver the secret from
the ramen namespace on the managed cluster to the velero namespace
on the managed cluster.
Using a single policy fails as that expects to be able to resolve
the configuration policy before applying the same. As the velero
secret is delivered using the delivered S3 secret in the ramen
namespace, such a single policy scheme fails.
Related changes to protect the secret using additional finalizers
and addressing upgrade cases are also covered in the commit.
Further to delivering the secret, update s3StoreAccessorsGet to process
the new secret as the veleroNamespaceSecretKeyRef when the latter is
not present in the config file
Signed-off-by: Shyamsundar Ranganathan<EMAIL_ADDRESS>

The policy related changes look good to me. I am a bit worried about adding velero field to the secretsUtil as it doesn't really belong there.
Shouldn't we send the velero details from the ramenconfig in the methods which are implemented by secretUtil?

Should be addressed in the latest set of changes. This part is good for a review.

TODO:

[ ] Testing with imperative apps in e2e, to ensure changes are in working order
[ ] Any updates to default ramen config, to not configure veleroNamespaceSecretKeyRef
[ ] Updates to drenv, to ignore creating velero secrets in the required format and namespace

The ramenctl changes looks good.
The first commit is huge and I don't fully understand it. Chang of this size is likely to contain bugs and regressions, I hope it is not targeted to 4.16.

It is for 4.16

Main issues:
* Why do we use the "v" prefix instead of creating a new clear ramen control name for the secret we generate?

To control overall name length in these cases (including the name length of the OCM policy)

* Why we need different finalizer for velero secerts? (not of code changes for this, not clear what is the benefit)

Answered inline

* I hope we don't adopt _any_ secret from velero namespace. I think we should protect only secrets labeled with ramen specific label. This will help to avoid issue like [Ramen controllers are caching secret/configmaps from all namespaces #1434](https://github.com/RamenDR/ramen/issues/1434)

No we do not, we deliver a secret to the Velero namespace and this is not related to the posted issue.


kicad fails to build

Issue description
Kicad build fails with an error from CMake:
CMake Error at CMakeModules/CheckCXXSymbolExists.cmake:41 (_CHECK_SYMBOL_EXISTS):
  Unknown CMake command "_CHECK_SYMBOL_EXISTS".
Call Stack (most recent call first):
  CMakeModules/PerformFeatureChecks.cmake:86 (check_cxx_symbol_exists)
  CMakeLists.txt:141 (perform_feature_checks)

Steps to reproduce
invoke nix-env -iA nixos.kicad
Technical details

system: "x86_64-linux"
host os: Linux 4.14.56, NixOS, 18.09pre146471.d7d31fea7e7 (Jellyfish)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0.4
channels(root): "nixos-18.09pre145679.dae9cf6106d, nixpkgs-18.09pre146471.d7d31fea7e7"
channels(nek0): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

can @viric or anybody else look into this and maybe even update kicad to version 5.0.0?

@nek0 See https://lists.launchpad.net/kicad-developers/msg35240.html

I have opened #44122 bumping Kicad to 5.0.0.

Workaround:
I have build kicad from  90c01001396 one commit before  cmake was upgraded. Works fine.

fixed in https://github.com/NixOS/nixpkgs/pull/44122


[BUG]: DFP example uses older/incompat container version

Version
23.01
Which installation method(s) does this occur on?
Docker
Describe the bug.
The docker-compose.yml builds upon v22.09.00-runtime which uses SRF, but the stages have been updated to use MRC.
This can be worked-around by setting MORPHEUS_CONTAINER_VERSION
Minimum reproducible example
No response
Relevant log output
No response
Full env printout
No response
Other/Misc.
No response
Code of Conduct

[X] I agree to follow Morpheus' Code of Conduct
[X] I have searched the open bugs and have found no duplicates for this bug report

Also dask is missing


Add Kronecker product

This is a slightly modified version of the one in #209, which uses some symmetries for the CSC^2 -> CSR^2 case.
The incompatible storage case is now handled by converting the second matrix to the opposite storage. This might not be the most efficient, but the performance should be predictable in this case.
Closes #209

Thanks, that's a very clean implementation.

This might not be the most efficient, but the performance should be predictable in this case.

Indeed, it might be best to dynamically choose which matrix should be converted, but this would need benchmarks first. I think it's best to first have this implementation, then later we'll see if the performance needs to be improved. And since the performance is predictable, this means the calling code is free to perform its own manipulations to enforce best performance.


XR_EXTX_Overlay support

SteamVR does not implement this extension, only tested on Monado.
Open questions:

public variables on the extension wrapper okay?
should main_session_visible be a NO_EDITOR property instead of calling get_main_session_visible every _process()?
env.background_color.a = 0.0 doesn't actually make the background transparent fixed: I forgot XR_COMPOSITION_LAYER_BLEND_TEXTURE_SOURCE_ALPHA_BIT

New problem: A call to get_tree().get_root().set_transparent_background(true)  or get_tree().get_root().set_transparent_background(false) breaks VR rendering, produces weird flickering of wrong/old textures.

New problem: A call to get_tree().get_root().set_transparent_background(true) or get_tree().get_root().set_transparent_background(false) breaks VR rendering, produces weird flickering of wrong/old textures.

The problem here is that this triggers resizing the viewport back to its original dimensions, for some reason this breaks when used in combination with render targets supplied by the VR plugin, I've got it on my list to look into but haven't gotten to it yet.
A viable workaround is to not use the main viewport but a separate viewport for VR rendering, only works for desktop VR though. You can have a look at the demo on the OpenVR plugin which uses this approach.


feat(frontend): add Ethereum transactions in AllTransactionsList

Motivation
As last part of splitting #3547 , we add the Ethereum transactions in the UI.
Tests
Note that UI wise, there will be other PRs

[OISY-130]


Running Traefik v2 from BASH causes error: "msg="error while parsing rule Host(bash: "

Do you want to request a feature or report a bug?

Bug

What did you do?

I attempted to run the Traefik v2 container without loading any local files. I have a situation where I do not want to keep any static or dynamic TOML files, I wish only to load all of the arguments in the command line.
What did you expect to see?
I expect it to work exactly the same as it would when using static and dynamic TOML files.
What did you see instead?
I couldn't connect to the dashboard or any applications behind the Traefik proxy.
Output of traefik version: (What version of Traefik are you using?)

time="2020-03-03T00:02:40Z" level=error msg="error while parsing rule Host(bash: ui.docker.localhost: command not found): 1:10: missing ',' in argument list" entryPointName=web routerName=traefik@docker
time="2020-03-03T00:02:40Z" level=error msg="error while parsing rule Host(bash: ui.docker.localhost: command not found): 1:10: missing ',' in argument list" routerName=traefik-secure@docker entryPointName=web-secure

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


feat: support to replicate rbac message to kafka

add kafka rbac replication func
[WIP]: complete kafka ci test

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

Project coverage is 63.95%. Comparing base (364e07b) to head (12080d9).

Files with missing lines
Patch %
Lines

core/writer/kafka_handler.go
56.83%
55 Missing and 24 partials :warning:

core/writer/kafka_formatter.go
70.00%
2 Missing and 1 partial :warning:

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #122      +/-   ##
==========================================
- Coverage   64.50%   63.95%   -0.56%
==========================================
  Files          52       52
  Lines        6902     7024     +122
==========================================
+ Hits         4452     4492      +40
- Misses       2167     2224      +57
- Partials      283      308      +25

Files with missing lines
Coverage Δ

core/writer/kafka_formatter.go
67.39% <70.00%> (-7.08%)
:arrow_down:

core/writer/kafka_handler.go
59.40% <56.83%> (-19.65%)
:arrow_down:


[FormRecognizer] upgrade dev dependency prettier to v3

and remove dependency on @types/prettier as v3 package include types already.
Issues associated with this PR
#27974

API change check
API changes are not detected in this pull request.


Some fixes failing to be applied when image is rebased

Log attached:
https://github.com/CircleOf8/TemplePlus/blob/master/Crashlogs/2015-04-02TemplePlus.crashlog

Silly issue: I used the logger before it was initialized


More test updates for DV Decimal

Followup to https://github.com/microsoft/Power-Fx/pull/1821, cleaning up a few more things and ensuring this is compatible with the power-fx-dataverse repo.

✅ No public API change.

✅ No public API change.

✅ No public API change.


More Cask options

Replaced homebrew_cask_appdir with a more generic homebrew_cask_opts, to allow setting more options. I was specifically looking for a non-default Caskroom location, but this can be used for other options as well.

I like this; much cleaner. I'll run some local tests before merging.

Actually, I am now wondering if this whole section is now required. If we're asserting state=present via homebrew_cask, then ansible will do all the checks itself, won't it? I'll test this and push another commit if it works
# Cask.
- name: Get list of apps installed with cask.
  command: >
    bash -l -c '{{ homebrew_brew_bin_path }}/brew cask list'
  register: homebrew_cask_list
  always_run: yes
  changed_when: false


Update changelog to reflect recent PRs

@Amanieu Any updates on when you might release 0.8.1? Anything outstanding I can help with?

I just published it.


catalog: GetServiceEndpoints API

We are introducing a new API called GetServiceEndpoints, which will
attempt to return the virtual or cluster IP endpoint for a given service,
or alternatively return all the individual instance endpoints at which
the service is avilable at.
To properly test, needs some larger changes that I will follow up
with on a commit on top.
Please describe the motivation for this PR and provide enough
information so that others can review it.
Please mark with X for applicable areas.

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [ ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests / CI System      [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?

I missed explaining purpose for this API.
Addressing all, plus adding more context and explanation to the change.

Codecov Report

Merging #1645 into main will increase coverage by 1.36%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##             main    #1645      +/-   ##
==========================================
+ Coverage   55.05%   56.41%   +1.35%
==========================================
  Files         117      117
  Lines        4922     5032     +110
==========================================
+ Hits         2710     2839     +129
+ Misses       2210     2190      -20
- Partials        2        3       +1

Impacted Files
Coverage Δ

pkg/catalog/endpoint.go
51.72% <40.00%> (-26.06%)
:arrow_down:

cmd/osm-controller/osm-controller.go
31.38% <0.00%> (-2.48%)
:arrow_down:

pkg/envoy/route/config.go
95.74% <0.00%> (-0.71%)
:arrow_down:

pkg/envoy/rds/response.go
26.86% <0.00%> (-0.41%)
:arrow_down:

pkg/featureflags/featureflags.go
100.00% <0.00%> (ø)

cmd/cli/install.go
65.98% <0.00%> (+1.80%)
:arrow_up:

cmd/osm-controller/certificates.go
26.82% <0.00%> (+2.38%)
:arrow_up:

pkg/catalog/routes.go
81.60% <0.00%> (+2.41%)
:arrow_up:

cmd/cli/namespace_remove.go
54.16% <0.00%> (+7.82%)
:arrow_up:

cmd/cli/namespace_add.go
60.00% <0.00%> (+13.84%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


Explore available tools/services/common components to support external user intake

Describe the task
Existing resource for further exploration:

CCBC code
GC Forms
CHEF

Acceptance Criteria

[x] Meet with CCBC team for a demo
[x] Review GC Forms
[x] Review CHEFS
[ ] Explore MUNI/LGIS
[ ] Review and present options to scrum team for feedback

Additional context

Note a meeting has been scheduled with CCBC on December 14th for a demo

Met with CCBC team Product Owner on December 14, 2022 for a demo of their applicant intake portal. Some key takeaways:

App was built in 5 months and leveraged CIIP/CIF code
Currently the app has no validation on the front end as there wasn't a lot of fields where validation would be beneficial
There are several intake screens related to document upload for form templates (Note: proponents need to first download the templates from the website, complete them and then upload into the system)
They have an area for contact information to be entered (note: CIF hasn't requested this feature, but could be valuable?)
Biggest amount of work for our team could be related to the document upload/management. More user research/conversations with CIF team are needed to really understand the basic requirements.

cc @suhafa @pbastia - feel free to add your notes here from today's conversation.

Met with GC Forms CDS team on 22 Dec. Their Github repo can be found here and you can demo their sandbox. Provinces are not able to use it, and it is limited to Federal Government, so we may not be able leverage this as of now, but it will be good to have on our radar for future work.

A few more CCBC notes to add to your points @LindsayMacfarlane

The CCBC team will reach out to the user to correct mistakes, as there is no validation. (I don't know if we would be happy with that outcome as it would create additional work for CIF. Might need to explore that)
The CCBC app allows for a lot of flexibility: unvalidated fields can be submitted provided to you check a box that acknowledges that you as the user are submitting incomplete data, the user can edit and update the application even after submission until intake closes. After that they can view the submission
Uploads are limited to not more than 100mb in size with specific file types predetermined, but can again be flexible if need be.

Feedback from January 5, 2023 Sprint Review:

MH: supports idea of using CHEFS if possible. Also, recently had a conversation with GC Forms regarding using a common repo for this type of functionality between Province and Federal Government.

Scrum Team feedback on CHEFS:

To decide on using CHEFS, we need to determine all the requirements of the application and validate with CIF first
to use CHEFS then will be a binary choice, either we go ahead with it or we don't depending on the complexity of the platform
If we go ahead with CHEFS, we will need to decide if we want to host it on our platform or theirs

@LindsayMacfarlane adding CHES to the AC. Any suggestions for how we could reach out to Donna Coe from LGIS/MUNI?

Will this be worked on next sprint? @suhafa cc @LindsayMacfarlane

I'm going to pull MUNI out of this ticket as it is a lower more exploratory ticket. I think this ticket can be wrapped up. Perhaps @mikevespi can comment on whether we would use CHEFS later on in development given how we are approaching the first slice? My thought, since we are trying to mirror/reuse what we've built in CIF so far, we probably won't utilize CHEFS at this point...but it is still an option to keep in the back of our minds.

I'm leaning away from using CHEFS. Since the information the proponents will be able to enter and see is information we already capture in the system, we already have the components we need built. Reusing our existing code has a number of benefits:

Lower maintenance costs
One less external dependency, and more control over the apps UI/UX
Consistent look and feel to the site from both sides
Since we've already done user research on our processes and designs, it means we're re-leveraging that work as well (I think this is easy to underestimate. Having already gone through iterations of these features means that we can move forward with this portion of the app at a faster pace with a relatively high degree of confidence)

The closer we mirror the internal side, the more value we get out of work already done.


Fix wording and add proper method description

Description
Fix a tiny grammar issue and update method docblocks with proper description.
Related Issues
Not Applicable

 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.


Replace "NeuronTracing" with "Reconstruction" activity in prov template

Reconstruction from imageStack and reconstruction from slice should be aligned by using the same activity naming.

Before addressing this issue, I want clear answers and comments on the following:
1- Schemas are defined for types defined in a given vocabulary (through targetClass). If a NeuroTracing activity is a specific Reconstruction activity then they should be linked by a subClass relation in the bbp core vocabulary independently of the schemas which are used to constrain them.
But if a Neurotracing activity is yet an other synonym for Reconstruction (i.e all Reconstruction activities can be safely considered as NeuroTracing activities) then:
a) we should keep a unique name (Reconstruction) and a single schema for both in all of our prov templates
b) assert in the bbp core vocabulary that NeuroTracing is a synonym of Reconstruction activity.
2- In case NeuroTracing activity is a subclass of Reconstruction activity, we should have two different schemas for both types only if we think the set of metadata to describe them are different. If they are described by the exact set of metadata, we should have one schema for both.

Neuron tracing, reconstruction
After a discussion with Anna and after looking into the some sources we concluded that "neuron tracing" is used as synonym of "neuron reconstruction", these terms are sometimes both used in a single page (https://goo.gl/oLa54b)
I think we should also take into account what scientist and authorities in the subject are already using:
- Allen -> 3D neuron reconstruction
- Neuromorpho -> reconstruction
- LNMC -> reconstruction
On the other hand, "cell reconstruction" does not refer only to morphology reconstruction, it also refers to 3D cell reconstruction from images (https://goo.gl/zKAkJ1).
In any case, whatever term we decide to use we should use it consistently (i.e. update also our ontologies).

Thank you for this comment. If I understand correctly: "neuron tracing" is used as "neuron reconstruction" from various sources.
So I would suggest to:

pick one name to represent this type of activity ("Reconstruction", "NeuronReconstruction", "Reconstruction", ...).
use a single schema for both
assert in the bbp core vocabulary that "neuron tracing" is a synonym of "neuron reconstruction" activity.

We cannot really use a single schema due to the "used"  entities that are not the same.
-For the reconstruction from slices we have a "used" "LabeledCell".
-For the reconstruction from image stack we will have a "used" "ImageStack".

I see. What else differentiate a reconstruction for image stack and reconstruction from slices and that are not part of the protocols description (which I guess will be different) ?
If the only difference is the type of used entity then we can add an "sh:or" clause in the Reconstruction activity schema.
Thoughts ?

The activity named "neuron tracing" or "cell reconstruction" can be done using a brain slice or an image stack. This activity always uses the neurolucida software in a manual or semi-automatic mode. I would suggest that we align the way we name these activities since naming it "neuron tracing" when it has as an input an image or "cell reconstruction" when it has as an input a slice  doesn't make a lot of sense.


interesting result?

Hi, shaoshuai, did you try to not use ry as the angle label ? I convert ry to -(ry + pi / 2) to convert ry to lidar coordinate, and then use -(ry + pi / 2) as angle label, after finishing training, I convert it back to ry.
The result is very interesting,  -(ry + pi / 2) is poor than ry when iou is 0.7, generally lower than 20 points, but when the iou is 0.5, the result is close.

@AndyYuan96  Why do you want to convert it to -(ry + pi/2)? I am not very familiar with pcdet, but the reason SECOND and Det3D converts it to -(ry + pi/2) for nuScenes is because nuScenes uses a different coordinate system than KITTI. However, for PCDet, the conversion from an original KITTI label to -(ry + pi/2) may break those augmentation / nms / other code, one example is the flip augmentation I guess.

@tianweiy ,in KITTI,  -(ry + pi/2) is the true angle of bounding box in lidar coordinate, convert to -(ry+pi/2) will not break nms and other code, except for augumentation. I use -(ry + pi/2) , because the angle is the true angle of ground truth bounding box in lidar coordinate, and the anchor is also in lidar coordinate. If use ry to assign gt with anchor, we are using gt(in camera coordinate) and anchor(in lidar coordinate) to match,  though it's a little confused to understand.  but it does work.


obelisk: 0.6.0 -> 0.7.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/Lelio-Brun/obelisk/releases.
meta.description for obelisk is: Simple tool which produces pretty-printed output from a Menhir parser file (.mly)
meta.homepage for obelisk is: https://github.com/Lelio-Brun/Obelisk
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.7.0 with grep in /nix/store/hrbymwyfs5a01s9nvnvqjpm5zhzk0xj9-ocaml5.1.1-obelisk-0.7.0
found 0.7.0 in filename of file in /nix/store/hrbymwyfs5a01s9nvnvqjpm5zhzk0xj9-ocaml5.1.1-obelisk-0.7.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

obelisk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hrbymwyfs5a01s9nvnvqjpm5zhzk0xj9-ocaml5.1.1-obelisk-0.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A obelisk https://github.com/r-ryantm/nixpkgs/archive/be4eafa804e78a9de7720d2a727e816b15140dd0.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/be4eafa804e78a9de7720d2a727e816b15140dd0#obelisk

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/hrbymwyfs5a01s9nvnvqjpm5zhzk0xj9-ocaml5.1.1-obelisk-0.7.0
ls -la /nix/store/hrbymwyfs5a01s9nvnvqjpm5zhzk0xj9-ocaml5.1.1-obelisk-0.7.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

obelisk

Maintainer pings
cc @vbgl for testing.

Result of nixpkgs-review pr 324198 run on aarch64-linux 1

1 package built:

obelisk


(maint) Fix service assertions in acceptance

This came up when runnning all acceptance tests for Ruby 2.7. We have additional spaces in the puppet resource output due to a param with a longer name, so update the assertions to match that.

CLA signed by all contributors.


[MonorepoBuilder] Add ability to split non-master branch

Suppose I have 1.1-dev in master branch and 1.0-dev in 1.0 branch.
I wan't to add fix commits to 1.0-dev and to release patch versions.
If I am not mistaken, --branch=master is currently hardcoded and I cannot use vendor/bin/monorepo-builder split --branch=1.1.

This was supported before but the added complexity and maintenance didn't show as sustainable for the mainstream monorepo split - there were performance issues, bugs and it became super complex for begginers. Scope for this package is only master + last tag split.
Luckily, there is package that is ready for complex scenarios as yours: https://github.com/shopsys/monorepo-tools
I recommend to check it!


Fatal error: exception Sys_error

I use the infer to analysis the java file, but I get this info
TODO: print error message
Starting analysis (Infer version v0.1.0)
Fatal error: exception Sys_error("/Users/monkey/Documents/open_source/infer/examples/infer-out/captured: No such file or directory")
[ERROR] Failure during create_makefile, original command was

[u'inferJ', u'-g', u'-a', 'infer', u'javac', 'Hello.java']

Traceback (most recent call last):
  File "/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/inferJ", line 19, in <module>
    stats = analysis.start()
  File "/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/inferlib.py", line 634, in start
    self.analyze_and_report()
  File "/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/inferlib.py", line 613, in analyze_and_report
    if self.analyze() == os.EX_OK:
  File "/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/inferlib.py", line 489, in analyze
    self.args.analyzer
  File "/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/inferlib.py", line 318, in run_command
    raise e
subprocess.CalledProcessError: Command '[u'/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/InferAnalyze', u'-results_dir', '/Users/monkey/Documents/open_source/infer/examples/infer-out', u'-makefile', u'Makefile', u'-allow_specs_cleanup', u'-models', u'/Users/monkey/Documents/dev_tool/infer-osx-v0.1.0/infer/infer/bin/../lib/java/models.jar', u'-project_root', '/Users/monkey/Documents/open_source/infer/examples']' returned non-zero exit status 2

My java version is 1.7, python version is 2.7.

@monkeytest15: thanks for reporting this. It seems that several people have experienced the same issue coming a failure in the library we use to parse bytecode. We are working on fixing the issue upstream.

@monkeytest15 can you please provide the exact version of javac you have? Simply run javac -version
Thanks!

Hi, I met the same error.  My java version is 1.6

$ java -version
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
same problem.

Closing as probable duplicate of #30. Feel free to re-open if you think that's not the case.


Add required to return value of useTextField

Closes  #1750 ( Proposal )
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[x] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
run yarn test.

🧢 Your Project:

Closing as we do not intend to change this behavior at this time.
Thank you!


Publishing to maven local broken

I want to preface this by saying I'm pretty unfamiliar with Java build systems in general, Gradle included. I suspect if that weren't the case I could give you a pull request with a solution instead of just a problem.
In any case, attempting to publish to the local maven repository as described in the readme doesn't work. Running "gradle clean build publishToMavenLocal" produces an error message like this:
Execution failed for task ':hellocharts-library:publishMavenPublicationToMavenLocal'.
> Failed to publish publication 'maven' to repository 'MavenLocal'
   > Invalid publication 'maven': artifact file does not exist: <containing dir>/hellocharts-android/hellocharts-library/build/outputs/aar/hellocharts-library.aar'
```
The issue seems to be that the build step spits out "hellocharts-library-debug.aar" and "hellocharts-library-release.aar". I ran the clean and build steps, copied the release library into a new file named "hellocharts-library.aar" and then ran the publishToMavenLocal step last and everything worked fine. It seems like it's just a naming issue in some Gradle config file, but it's potentially discouraging to new users.

Thanks for report.


Issue with TFRecord from URL

I'm building a plugin for CML using TFRecord files.
When I point the MultiURL method at https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/TripCloud0.0.tfrecord
the file is successfully downloaded and loaded.
When I point it at https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/TripCloud0.1.tfrecord
the call to cml.load_source(....) fails with
Unknown file type /hugetmp/tmp-climetlab/url-63428528b56eb9c50418511287b38d1c7c53e6e203671861fb71faf86e6cbb72.man (b'PP\x00\x00\x00\x00\x00\x00'), ignoring

Examining the cache directory, the first file has been downloaded as a .tfrecord file and the second has been downloaded as a .man file.
Thanks.
Mat

@floriankrb this still happens with 0.8.5.

Thanks for the test data.
This works for climetlab 0.8.6:

s = cml.load_source('url', 'https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/EWCTest0.0.tfrecord')
s.to_tfdataset()

s = cml.load_source('url', 'https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/EWCTest0.1.tfrecord')
s.to_tfdataset()

I expect 0.8.6 version to be release  on pip in 30 min

But it still not work with you initial example.
The reason may be that the http header is providing the wrong data type (x-troff-man).
As you see (with pip install httpie):
$ http https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/TripCloud0.1.tfrecord
...
Content-Type: application/x-troff-man

$ http https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/EWCTest0.1.tfrecord
...
Content-Type: application/octet-stream

We will work on this shortly.

This issue definitely comes from the http server, but we can try some workarounds.
we could add an argument "extension" to load_source for urls. This would work as:
t = cml.load_source(
    "url",
    "https://storage.ecmwf.europeanweather.cloud/MAELSTROM_AP3/TFR/TripCloud0.1.tfrecord",
    extension="tfrecord",
)
t.to_tfdataset()

This would be experimental and may not work in future release (we will keep the functionaly if it is needed)

and this would be implemented with commit df7f5a5, current develop branch.

Works out-of-the box with version 0.8.9. No need for the "extension" argument.


WIP: Add default configs and overrides

use defaultconfig.yaml (content derived from kube-core) as base
add config-override.yaml files for all three phases

Some questions around args, we need an issue to remove the IDP, but nothing that speaks against this as useful for merging for progress.

/lgtm


lint: add better per-checker docs

Some checkers do not describe their action precisely.
Note: check documentation formatting with godoc.
It understands code blocks (pre-formatted text), headings and paragraphs.

We should also work on documentation format for it to be consistent, so adding discussion label.


icon showing only in some workspace

i use i3 and Font Awesome and the icon i use for my workspace only works on 1 and 2 the other one do not show and get the default one
polybar config
[module/i3]
ws-icon-0 = 1;
ws-icon-1 = 2;
ws-icon-3 = 3;
ws-icon-4 = 4;
ws-icon-5 = 5;
ws-icon-6 = 6;
ws-icon-7 = 7;
ws-icon-8 = 8;
ws-icon-9 = 9;
ws-icon-10 = 10;
ws-icon-default = 

i3 config
set $w1 1
set $w2 2
set $w3 3
set $w4 4
set $w5 5
set $w6 6
set $w7 7
set $w8 8
set $w9 9
set $w10 10

# switch to workspace
bindsym $mod+1 workspace $w1
bindsym $mod+2 workspace $w2
bindsym $mod+3 workspace $w3
bindsym $mod+4 workspace $w4
bindsym $mod+5 workspace $w5
bindsym $mod+6 workspace $w6
bindsym $mod+7 workspace $w7
bindsym $mod+8 workspace $w8
bindsym $mod+9 workspace $w9
bindsym $mod+0 workspace $w10

# move focused container to workspace
bindsym $mod+Shift+1 move container to workspace $w1
bindsym $mod+Shift+2 move container to workspace $w2
bindsym $mod+Shift+3 move container to workspace $w3
bindsym $mod+Shift+4 move container to workspace $w4
bindsym $mod+Shift+5 move container to workspace $w5
bindsym $mod+Shift+6 move container to workspace $w6
bindsym $mod+Shift+7 move container to workspace $w7
bindsym $mod+Shift+8 move container to workspace $w8
bindsym $mod+Shift+9 move container to workspace $w9
bindsym $mod+Shift+0 move container to workspace $w10

i have set all the label-* to %icon%
this is how it looks like

You're missing the ws-icon-2 setting. Polybar reads all the ws-icon-* in order and stops as soon as it doesn't find next ws-icon-* setting. So in your config polybar only recognizes ws-icon-0 and ws-icon-1

so blind, fixed thanks