kube-prometheus/Makefile: Change target output from files to folder

Previously the manifests and vendor folder content has been build
via manifests/** and vendor/** target definitions. This results in
two issues:

The GNU Make recipe is executed for every single file in the folders.

Not all timestamps inside the manifests folder would be updated on
every run, thereby needing to be rerun on all following target
executions.

Solution:

Define the target based on the folder, not individual files

Remove target folder before execution recipe to ensure all timestamps
are updated.

Could you rebase this, otherwise lgtm

Actually it seems I could resolve the conflicts from the UI.

Merging this as it significantly speeds up CI and CI failures are fixed on master.


NIFI-5960 add compatibility rating to RECORD schemas

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

[x] Is your initial contribution a single, squashed commit?

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] ~If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?~
[x] ~If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?~
[x] ~If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?~
[x] ~If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?~

For documentation related changes:

[x] ~Have you ensured that format looks appropriate for the output in which it is rendered?~

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

I think it will be important, in the JIRA, to explain the plan/strategy for what a compatibility score would mean and how it would be calculated in general.  It is probably best to discuss if that score would be sufficiently meaningful or not before diving too far into the PR itself.  The idea is certainly interesting but we probably need to discuss what it means, how it is calculated, how it is used.

I intended for JIRA to only describe the issue, not the solution (as I'd prefer not to steer anyone trying to solve that issue into a particular solution, there might be alternate approaches).
The issue at hand is that, when determining if a record is compatible with a given schema, we consider nullable fields to be compatible with null values. Generally, this makes sense, but not for union types. If one of the union choices is a record with only nullable fields, this choice suddenly becomes compatible with pretty much everything - like, you can feed it a record with completely unrelated field names, and it would still be considered compatible (see JIRA for an example).
This PR aims to address that issue by keeping track of how many non-nullable fields were found compatible, as a ratio to the total # of fields checked. The ratio goes from -1 (not compatible) to 100 (fully compatible). So the above example would still be considered "sorta-compatible", with a rating of 0, but the compatibility check would still continue, and if a schema choice with a higher rating is found (all it takes for that is one non-nullable field to be found compatible), that schema would be used instead.

Ok I now think I understand what you are proposing.  The JIRA states the problem is that we can choose a suboptimal type in certain situations.  Your PR aims to address this by having a compatibility scoring approach and then iterate through all possible compatible options and choose the most compatible.
Is the choice of 0...100 as ints an optimization over using a double between 0...1?
Thanks
Joe

The range goes -1..100, not 0..100. The reason is because a schema with rating 0 (all nullable fields) is still a valid backup choice, if we can't find anything better. So I either had to make the formula more complex, or to have the "incompatible" value be outside of range (I chose the latter). As for why using integers - I prefer not to deal with floating point arithmetic unless it's genuinely necessary.

Merged latest master and resolved conflicts (record compatibility check was refactored into a separate method, made my job a little easier)

Fixed the Javadoc for the new method

closing due to inactivity


In Edge-DevTools, I can't enable/disable css styles

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Like this, I disabled background-color, but nothing has changed.

AB#49009863

Hello there, is that in the browser or in the extension?

Hello there, is that in the browser or in the extension?

It's in the entension. I used vscode to open the code editor(left), Edge-DevTools(center) and the built-in browser(right). like this:

When I use Edge-DevTools to turn off some CSS styles, it doesn't work, the styles still exist.

Hello there, is that in the browser or in the extension?

Wait, I seem to have found a way to reproduce this problem.

Open like my actions.
Now it works fine. but when I edited something later, like:

This error occurs:

Needed me to refresh the page again and it was back to normal again.

Thanks for the reproducing information, we will look into this.

Hello there, we tried to repro this on our end and we can't see the problem, even with the editing step. What local server are you running? Are there any conversion/build steps that might delay the changes of the CSS?

All right, I used a VSCode extension named "Live Server" as the server, had no other steps.

Hello there, it seems there is a compatibilty issue with the live server extension that it reloads the document before our changes are applied. Also see #872 for reference. We will try to reach out to the live server team and see what we can do.
@digitarald can you give some more information?

Hello there, it seems there is a compatibilty issue with the live server extension that it reloads the document before our changes are applied. Also see #872 for reference. We will try to reach out to the live server team and see what we can do. @digitarald can you give some more information?

Nothing else, thanks for your help! And before that, I will try some other ways.

I would recommend filing an issue on https://github.com/ritwickdey/vscode-live-server/ , @codepo8. Maybe there is also a fix possible on this extension, as live server has wide adoption?

Would love to, yes.

Closing this issue now. Our dev team tried reproducing it but couldn't. Let me know if there's still a problem here and we can reopen the issue.


Feature Request: SearchTextFieldItem as protocol or extendable class

I would really like to store some meta-data in the SearchTextFieldItems, so that I can access that data when the item is selected.
Example: mix suggestions from various sources, and then when the user clicks, immediately know the source.
Seems pretty straightforward to me :-)

Works great.  I cloned the repo to change struct -> class
:)

I think this will also solve the problems in #64 and #43 and leaves your code as simple as it is now.

hey @btanner!, I made this change and updated to 1.1.7. Thanks for the suggestion!.

@apasccon  Doh!
Worked for me when I tested it in my code, but that's because it was not in a module for me. In a module, it must be an "open class" to be extensible.  Sorry!

Fixed!


[move] support const in const

Description
Support constants in constants.
Test Plan
Added new tests

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[x] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes
The error for using const-in-const changed to point at the feature gating.

I'll fix the nits when I get back to the office, but -- doesn't the transactional test I posted do the correct thing for testing they are actually folded?

doesn't the transactional test I posted do the correct thing for testing they are actually folded?

Egads you're totally right. For some reason my eyes just went to the expected value files and errors, and I didn't see those. But yes, those are exactly the correct tests so please disregard :)


recipes are not installing in node1(ubuntu)

i created a recipe file using below resources

and i added that cookbook to runlist, then i login to node1. then i run sudo hef-client this command to execute those resources, but those resources are not installing once check below

check the below things:

Go to your berks file(located in your cookbook folder) and execute the below commands

berks install
#berks upload

go to your chef server and edit the run_list
finally go to chef node and execute this command
#sudo chef-sudo
I think it is useful to you, if not please ignore
if already find the solution to this please close the issue.

I was expecting that you uploaded your cookbook first then modified your cookbook on workstation and if you want to update it on the server change your metadata version and do Berks upload again, Please update the issue accordingly,
Thanks

check the below things:
Go to your berks file(located in your cookbook folder) and execute the below commands
#berks install
#berks upload
go to your chef server and edit the run_list
finally go to chef node and execute this command
#sudo chef-sudo
I think it is useful to you, if not please ignore
if already find the solution to this please close the issue.
Note: if you modify the recipes please change the version in metadata file
and again do the berks install , berks upload ,change the run_list and execute the sudo chef-client
I think it is useful to you, if not please ignore
if you already find the solution to this please close the issue.

please change cookbook version in metadata.rb and berks upload again and add to run_list

There might be another possibility make sure auto save is enabled in vs code


Interface/implementation mismatch errors not reported.

When working on vscode with "reason.bsb.enabled": true, this is the flow I'm observing:

Rename a function foo in the .re file to foo2, keep .rei unchanged.
Error "does not match the interface..." only reported in the terminal, not in the editor.
Rename to foo2 also in the .rei file.
Now follow-on usage errors "value foo2 can't be found" reported both in the terminal and in the editor.

So it seems the issue is specifically for the interface/implementation mismatch error.

I have the same problem.
Can reproduce it with only 2 re files. It happens with or without reason.bsb.enabled.
If I start with:
/* File A */
let function1 = () => "hello";

/* File B */
A.function1();

Now, when I rename function1 to function2 in both files, the editor marks File B with an error on
[merlin] Error: Unbound value A.function2

The javascript compilation (bsb -make-world -w) in background completes ok and with the function renamed in both .js files.
If I Reload window on vscode the error disappears.

I tried reproducing this with @ccaseiro in discord and was unsuccessful. The main difference in our setups is that I am on Linux.

Error "does not match the interface..." only reported in the terminal, not in the editor.

This part of the issue reported by @cristianoc sounds to me like some output from bsb that the ocaml-lan-server parser is not able to process. I can look into this.
The other problem reported by @ccaseiro sounds Merlin related, not bsb:

The javascript compilation (bsb -make-world -w) in background completes ok and with the function renamed in both .js files

I was looking to update the bsb parser in order to fix this, but it's hard because the error explanation that bsb outputs can literally be any string of any number of lines, and right now there's no characters delimiting it.
@chenglou Is there anything that can be done on the bsb side to separate the context (that includes the line numbers like 2 | someCode) and the error itself?
   8 ┆ test(
   9 ┆   "one limb number",
  10 ┆   () => expect(Bn.fromFlfdoat(12345.) |> Bn.toString(~base=16)) |> toB
       e("3039")
  11 ┆ );
  12 ┆ test(

  /* SEPARATOR OR ERROR HEADER HERE */

  The value fromFlfdoat can't be found in Bn

  Hint: Did you mean fromFloat?

ninja: build stopped: subcommand failed.

That'd help fixing this issue without increasing the complexity of the regexps.
The output right now for the error mentioned by @cristianoc is:
ninja: Entering directory `lib/bs'
[1/2] Building src/Bn.cmj
FAILED: src/Bn.cmj /Users/javi/Development/github/bs-bn.js/lib/js/src/Bn.js
/Users/javi/.nvm/versions/node/v6.11.2/lib/node_modules/bs-platform/lib/bsc.exe -bs-package-name bs-bn.js  -bs-package-output commonjs:lib/js/src -bs-assume-has-mli -bs-no-builtin-ppx-ml -bs-no-implicit-include   -I src  -w -30-40+6+7+27+32..39+44+45+101 -nostdlib -I '/Users/javi/Development/github/bs-bn.js/node_modules/bs-platform/lib/ocaml' -bs-super-errors -no-alias-deps -color always -bs-re-out -bs-super-errors -o src/Bn.cmj -c  src/Bn.mlast

  We've found a bug for you!
  /Users/javi/Development/github/bs-bn.js/src/Bn.re

  The implementation src/Bn.mlast
       does not match the interface src/bn.cmi:
       The value `toString' is required but not provided

ninja: build stopped: subcommand failed.

@chenglou Is there anything that can be done on the bsb side to separate the context (that includes the line numbers like 2 | someCode) and the error itself?

If the error context always consists of lines like that couldn't you match all the lines at once with /^\d+\s+\|\s+.*$/gm and then advance the parser to the error message based on the result?
In case it's not so straightforward, I'll just add that I've been planning to rewrite the bsb output parser (and the ocamldoc parser) using chevrotain very soon and maybe it'd be easier to deal with at that point.
The ocamldoc parser currently uses peg.js but there are some corner cases I need to fix there and I'd like to move all of the parsing duties over to chevrotain since it's cleaner and more flexible (I've been using it in another language server with good results).
For the bsb parser, I'd also like it to be able to handle error reports even when the super errors functionality is enabled but last time I checked this produces different output that the current patterns don't seem to match against.


feat: add sns topic support

Closes: #1772

awesome, let's add SNS to https://github.com/iasql/iasql-engine#aws-services-with-basic-api-coverage

now that https://github.com/iasql/iasql-engine/pull/1801 has been merged you could rebase and add a test to avoid regressions.


Vagueness around rollup field paragraph

I find this paragraph below vague. What does this mean? If a rollup field is not updated for 2 months, does this mean that it won't be updated for 10 years, if the next update happens after 3 months?

Notice that, when the situation occurs where the rollup column is never updated, the Mass Calculate Rollup Field job won’t run again for that column until after 10 years have passed. This behavior is by design. When there aren’t any updates in the underlying columns associated with the rollup field, there isn’t any reason to run the job more frequently.

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

ID: d7aaa057-dbfa-e5b0-2222-5f59299c4960
Version Independent ID: c88e45f0-47ec-ab48-66c0-1a13b0aa2ad5
Content: Define rollup columns with Power Apps - Power Apps
Content Source: powerapps-docs/maker/data-platform/define-rollup-fields.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

Thanks for your comment, @rajyraman. This issue has been assigned to the doc author for review.

@rajyraman - No, the Mass Calculate Rollup Field job will run 12 hours after the change whether you make an update to the column today, tomorrow, two months or three months from now. As the article states, when a change occurs the Mass Calculate Rollup Field job runs within 12 hours. If no change occurs, the Mass Calculate Rollup Field job won't run until about 10 years have passed.
Closing issue.


[CT-1220] [Bug] dbt documentation does not list macros that were migrated from dbt-utils

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
dbt documentation currently has no mention of the macros that were migrated from dbt-utils in March (https://github.com/dbt-labs/dbt-core/issues/4813) and subsequently released.
For example for date-diff, dbt-utils doc mentions: "DEPRECATED: This macro is now provided in dbt Core. It is no longer available in dbt_utils and backwards compatibility will be removed in a future version of the package."
Expected Behavior
Having list of macros included in dbt-core and expected behaviour documented like they were in dbt-utils
Steps To Reproduce
Search for macros in the dbt documentation and find nothing. https://docs.getdbt.com/
Search for macros in dbt-utils and see that they are deprecated. https://github.com/dbt-labs/dbt-utils#datediff-source
Relevant log output
No response
Environment
dbt 1.2

Which database adapter are you using with dbt?
No response
Additional Context
No response

Thanks @ali-infostrux! I'm going to move this one over to the dbt-docs repo.
Here's the spot where we explicitly filter out any macros defined in the dbt (global project) namespace:
https://github.com/dbt-labs/dbt-docs/blob/aa128ea4aa0b1a1e84a4ea32706ab2ab2b2de452/src/app/services/project_service.js#L337-L339
Should we keep doing that? Perhaps not! There's good reason to want easy access and documentation to these utilities — especially if we added description, args hints, ...


🐛主题设置字体大小之后，compact布局下，单元格信息仍然显示不全

🏷 Version

Package
Version

@antv/s2
1.44.0

Sheet Type

[x] PivotSheet
[ ] TableSheet
[ ] GridAnalysisSheet
[ ] StrategySheet
[ ] EditableSheet

🖋 Description
通过setTheme设置dataCell中text字体大小fontSize为15。在layoutWidthType为compact时，单元格大小未自适应布局，显示不全。
⌨ Code Snapshots

const s2 = new PivotSheet(…);
s2.setTheme({
   dataCell:{
      text:{
         fontSize:15,
      }
   }
});
s2.render();

🔗 Reproduce Link

🤔 Steps to Reproduce
初始化显示
😊 Expected Behavior
紧凑布局下，单元格内容应该全部显示
😅 Current Behavior

Environment
Info

System
Mac

Browser
chrome:v103.0

:tada: This issue has been resolved in version @antv/s2-v1.51.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v1.44.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-v2.0.0-next.11 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-react-v2.0.0-next.10 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version @antv/s2-vue-v2.0.0-next.10 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add all Matches to regex engine

#4

Hello @ArielTriana! Thanks for opening this PR.

In the file src/language/regex/nfa.py:

Line 14:1: W293 blank line contains whitespace
Line 15:1: E303 too many blank lines (3)
Line 17:15: W291 trailing whitespace
Line 63:39: W291 trailing whitespace
Line 71:101: E501 line too long (119 > 100 characters)
Line 84:1: W293 blank line contains whitespace
Line 95:1: W293 blank line contains whitespace
Line 98:1: W293 blank line contains whitespace

In the file src/language/regex/regex.py:

Line 40:1: E302 expected 2 blank lines, found 1
Line 42:29: W292 no newline at end of file

Do see the Hitchhiker's guide to code style


Improve restart time of subgraphs with many data sources

Uniswap in the hosted service is taking 15 minutes to restart. We need to identify if this is due to slow graphql queries to grab the data sources or something else and improve this. There are probably opportunities for concurrency.

The first part of improving this was introducing the IPFS file cache. The second part of making this fast is is #1386. We should be able to close this issue after #1386 is merged and rolled out.

Here's the time it takes to run the query in DataSourceLoader::dynamic_data_sources_query for different first parameters, i.e., by varying the batch size with which they are loaded.
The data is pretty noisy, but it shows that we should raise the batch size for that particular query to 500 with prefetching.
The first column is the number of dynamic data sources we fetch with each invocation of the query. The slow and prefetch columns show how long it takes to load such a batch, the slow / 1k and prefetch / 1k scale that time to a batch size of 1000 for easier comparison.
All times in ms; measurements were for the subgraph leoyvens/nuonetworkdebug
(Qmf2aet9s2sdYA3qgTseffSyqDQijnZ9CSUZA6FQTCQHru) which has ~ 5200 dynamic data source entities, and holds the record for that in the production dump I am working with.

first
slow
prefetch
slow / 1k
prefetch / 1k

50
750
170
15000
3400

100
1500
210
15000
2100

200
2800
320
14000
1600

500
6300
640
12600
1280

1000
14500
1400
14500
1400

2000
27000
2500
13500
1250


Get-DbaDbBackupHistory - Avoid a .ToString() that pollutes $error

Found this while cleaning up Linux paths but wanted to make it its own PR since the command is so important

All tests pass so I'll merge. If there are any issues, we'll take a closer look.


New Metric: Altitude

Hi, I just came across your excellent project! As I want to use Hauk to keep track of my buddies when paragliding, I'd also like to have the altitude displayed. I made all necessary changes to the android app, backend and frontend (plus some refactoring) and hope you find it useful. I tested both unencrypted and encrypted communication and it looks fine. Let me know if something needs to be changed and feel free to cherry pick if you don't like my refactorings.
Cheers!
P.S.: If I find the time I would like to incorporate the OpenElevation API in order to get the height above ground and maybe also a custom icon for when the tracked user is airborne.

This looks very good, and a welcome addition to the project. I've proposed some changes that are mainly in how the markers are rendered. I suggest moving the altitude display to its own line underneath the velocity to make the marker label a bit more compact; see proposed changes.

I agree, that would look much nicer!

Maybe it would be an idea to also allow altitude to be hidden? I.e. an altitude_unit of NONE that would hide it from the map altogether. From my experience, altitude fixes on phone GPS units can be.. inaccurate, and for most users, knowing user's altitudes probably isn't of great importance. Although for your use case, altitude display looks to be a very useful feature, and should definitely be included.

Supporting altitude_unit of NONE also came to my mind, but I thought that maybe you might want to use the unit in some other place in the future, so I would suggest to add flags for each metric like display_speed and display_alt_amsl.

Any considerations on how to handle cases where a device only reports a 2D fix? Currently it appears to default to 0.0 meters, or the last available altitude, if any.

If Location.hasAltitude() is false, then I would suggest either displaying n/a as value or not displaying the altitude at all. I prefer the latter solution, because it does not waste valuable screen estate. Although, If the device sends bogus values, I don't think there is anything we can do about it.

Regarding the metric panel, I played around on JSFiddle a bit. What do you think about this:

You can find the demo here:
https://jsfiddle.net/hqwjaxo8/2/
I did not include "AMSL", because as there is no other altitude value, yet.

@tuffnerdstuff thanks for this very good idea !
I would like to try it and I have checked-out my branch to your PR and added the parameters to my config.php, but when I am watching the files changes, it seems that the Android App needs to have some changes...I don't have any dev machine or env, is there a simple way to create the apk somehow? excuse my ignorance, I never tried to build/compile an Android app before.

@2Belette I doubt that there is something like a 1-click option to compile an Android Project. That said, it is much easier nowadays to set up your machine to do so than it was a few years ago. If you have any kind of Mac/Windows/Linux PC, just grab the Android SDK (command line tools are sufficient to compile), it's not too hard to set up. If you just want to try it out and/or you don't want to start hacking, then here is my locally built version. Use it on your own risk, though, it's always safer to compile stuff yourself.

Sorry about being super late to get back to this. I've had a lot of other things on my hands and kind of forgot about this pull request.
I'm not sure if we need both velocity and altitude to be explicitly labeled. My main concern was that altitude would be easy to mix up with distance (e.g. distance from map viewer) without labeling that specifies it as the altitude. I'm wondering if we could either stick to just e.g. "353.1 masl."/"1022 ft.amsl", or if we could maybe use icons in front of the labels as a replacement for text (which could also be more translation-friendly).
Something like this is the concept I'm thinking of:
🚶 3.4 km/h
⛰ 351.3 m
I don't have time to make a mock-up right now, so I just used emoji for that demo, but I'm thinking we could use some kind of monochrome icons that fit well with the rest of the design. Let me know what you think, and I can write up a demo and post it this weekend.

Sorry about being super late to get back to this. I've had a lot of other things on my hands and kind of forgot about this pull request.

No problem :)

I'm wondering if we could either stick to just e.g. "353.1 masl."/"1022 ft.amsl", or if we could maybe use icons in front of the labels as a replacement for text (which could also be more translation-friendly).

Using icons was exactly what I was thinking too. I did a cursory search for suitable icons in the fontawesome set, but couldn't find anything. Maybe you're luckier than me :) I was thinking about some speedometer icon for "speed" and an arrow pointing upwards above wavy lines (water) for height AMSL. In that case we could also leave out the AMSL, as the icon would express the meaning.

@bilde2910 just wondering if you plan to merge/integrate this nice feature soon into the F-droid app ? Or if something prevents it from happening ? many thanks!

@2Belette if I recall correctly @bilde2910 wanted icons instead of text labels, so if you would like to help getting the feature merged, then feel free to propose a nice GUI solution.

I've honestly been meaning to look into this pull request and the other issues on the repository for a while, but it's fallen completely off the radar, and for that I'm sorry. The truth is, I've been rather overwhelmed with commitments due to university and work, so I haven't been able to work on this project at all for a long time.
I've been thinking of passing the main responsibility for the project to someone else, so that the project doesn't just die off. I haven't entirely made up my mind yet, but if anyone has any thoughts about this, I'd be happy to discuss. I'm open to granting co-contributor rights to the repository to someone else.

@tuffnerdstuff @bilde2910 for this particular PR is it just a matter of icon vs. text which is blocking it or anything else ? If we want to stick with the current speed, text is fine but I think any of them is cool as long as we have the option it would be a very nice add-on. For the project globally, it would be indeed to bad if it would be abandoned as I really like it !

Is there any reason why this great proposal is still at the the same stage and blocked ?

@bilde2910 would you consider to add this PR in the coming versions ? I am glad to see that the project is still live and your are back! So glad when I saw this morning F-Ddoid to propose the update


Initialize multiple commitment units

Overview / Motivation
If a user wants to expend more than one post commitment unit, we need to expand the post init with the additional units (according to the current design, the final design might change a bit).
The Task
Support expanding of the init commitment. At the first stage, we can allow blocking of any proof generation during the init work.
Implementation Notes
TODO: Add links to relevant resources, specs, related issues, etc...
Contribution Guidelines
Important: Issue assignment to developers will be by the order of their application and proficiency level according to the tasks complexity. We will not assign tasks to developers who have'nt introduced themselves on our Gitter dev channel

Introduce yourself on go-spacemesh dev chat channel - ask our team any question you may have about this task
Fork branch develop to your own repo and work in your repo
You must document all methods, enums and types with godoc comments
You must write go unit tests for all types and methods when submitting a component, and integration tests if you submit a feature
When ready for code review, submit a PR from your repo back to branch develop
Attach relevant issue to PR

Part of the https://github.com/spacemeshos/go-spacemesh/issues/838 epic


Add cli support

This PR adds a cenity function that will take options working with zenity to create terminal output similar to zenity dialogs.

Indentation is 2 spaces instead of 4. Needs to be fixed


I know how to keep result value type when inject other deal in orElse().

Thank you for maintaining this library.
I know how to keep result value type when inject other deal.
Don't orElse() return other type error?
const writeCache = (cacheFilePath: string, content: string): Result<void, Error> => {
    fs.writeFileSync(cacheFilePath, content)
    return ok(undefined)
}

const requestByApi = async (): Promise<string> => {
    console.log('calling api...')
    return Promise.resolve('new content')
}

const safeRequestByApi = (): ResultAsync<string, unknown> => {
    return ResultAsync.fromPromise(requestByApi(), (e) => e)
}

okAsync(undefined)
    .orElse(_ => {  // Compile Error
        return safeRequestByApi()
            .andThen(res => {
                const mayWrote = writeCache('cachePath', res) // I want to tap only.
                if (mayWrote.isOk()) {
                    return ok(res) // I want not change return keeping the returned of safeRequestByApi().
                }
                return err(mayWrote.error)
            })
    })

Got TypeScript Error
No overload matches this call.
  Overload 1 of 3, '(f: (e: never) => Result<undefined, unknown>): ResultAsync<undefined, unknown>', gave the following error.
    Argument of type '(_: never) => ResultAsync<string, unknown>' is not assignable to parameter of type '(e: never) => Result<undefined, unknown>'.
      Type 'ResultAsync<string, unknown>' is not assignable to type 'Result<undefined, unknown>'.
        Type 'ResultAsync<string, unknown>' is missing the following properties from type 'Err<undefined, unknown>': error, isOk, isErr, asyncAndThen, and 3 more.
  Overload 2 of 3, '(f: (e: never) => ResultAsync<undefined, unknown>): ResultAsync<undefined, unknown>', gave the following error.
    Argument of type '(_: never) => ResultAsync<string, unknown>' is not assignable to parameter of type '(e: never) => ResultAsync<undefined, unknown>'.
      Type 'ResultAsync<string, unknown>' is not assignable to type 'ResultAsync<undefined, unknown>'.
        Type 'string' is not assignable to type 'undefined'.
  Overload 3 of 3, '(f: (e: never) => Result<undefined, unknown> | ResultAsync<undefined, unknown>): ResultAsync<undefined, unknown>', gave the following error.
    Argument of type '(_: never) => ResultAsync<string, unknown>' is not assignable to parameter of type '(e: never) => Result<undefined, unknown> | ResultAsync<undefined, unknown>'.
      Type 'ResultAsync<string, unknown>' is not assignable to type 'Result<undefined, unknown> | ResultAsync<undefined, unknown>'.
        Type 'ResultAsync<string, unknown>' is not assignable to type 'ResultAsync<undefined, unknown>'.ts(2769)

when inject other deal.

I'm not sure what you mean by this.

In any case, I am able to reproduce your type error. But this stems from a mismatch of types and not some bug in neverthrow.
Looking at the type signature of orElse
class Result<T, E> { // <--- INPUT
  orElse<A>(
    callback: (error: E) => Result<T, A>
  ): Result<T, A> { ... } // <-- OUTPUT
}

We can see that the input result has a "success" type of T and the output result has a success type of T. In other words; the success type does not change.
You can fix this by changing the code to the following:
  const writeCache = (cacheFilePath: string, content: string): Result<void, Error> => {
    fs.writeFileSync(cacheFilePath, content)
    return ok(undefined)
  }

  const requestByApi = async (): Promise<string> => {
    console.log('calling api...')
    return Promise.resolve('new content')
  }

  const safeRequestByApi = (): ResultAsync<string, unknown> => {
    return ResultAsync.fromPromise(requestByApi(), (e) => e)
  }

+ okAsync<string, unknown>('now its a string')
- okAsync(undefined)
    .orElse(_ => {  // Compile Error
        return safeRequestByApi()
            .andThen(res => {
                const mayWrote = writeCache('cachePath', res) // I want to tap only.
                if (mayWrote.isOk()) {
                    return ok(res) // I want not change return keeping the returned of safeRequestByApi().
                }
                return err(mayWrote.error)
            })
    })


messaging.getToken response http status 401

Step 1: Describe your environment

Operating system:  windows 10
Browser: Chrome Version 91.0.4472.114
Firebase SDK version: 8.6.8

Step 2: Describe the problem:
step by step
https://github.com/firebase/quickstart-js/tree/master/messaging
Observed Results:
messaging.getToken({vapidKey: 'BNL5iJili85g3W1UMO7OZv7S1zVyF9iwTi4rPdNDUy_tpO2norwetJ_hlqEO0dBi94mhMG_qdq-Pyg4uw8t9-iY'}) // error

An error occurred while retrieving token.  FirebaseError: Messaging: A problem occurred while subscribing the user to FCM: Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project. (messaging/token-subscribe-failed).
how should i do??

Same as me.

Chrome: Version 91.0.4472.114 (Official Build) (x86_64)
Os: macos catalina 10.15.3
Firebase SDK version: 8.6.8

curl 'https://fcmregistrations.googleapis.com/v1/projects/test-7fff6/registrations'
-H 'authority: fcmregistrations.googleapis.com'
-H 'sec-ch-ua: " Not;A Brand";v="99", "Google Chrome";v="91", "Chromium";v="91"'
-H 'accept: application/json'
-H 'x-goog-api-key: AIzaSyBR2DCCc9zqiCeMojdNYsb_fmm1Wkme4KU'
-H 'x-goog-firebase-installations-auth: FIS eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJhcHBJZCI6IjE6Mzg0MDU3NzI3MzUwOndlYjo1YWJiZDQyZDdmNWZhOTRlNDM0MjU3IiwiZXhwIjoxNjI1NzQ3NzEzLCJmaWQiOiJjbnZlLU5CdlNDQXpKZTdnYWJDSHJ5IiwicHJvamVjdE51bWJlciI6Mzg0MDU3NzI3MzUwfQ.AB2LPV8wRQIgPZt0h5HCRM4PN4R74DKXns3THn8oPuk4_Vyo44WqnvYCIQDzgLrKl35-L9U5ai9vSN7IAXYBZZi-hPDp3bgqX-TNkg'
-H 'sec-ch-ua-mobile: ?0'
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36'
-H 'content-type: application/json'
-H 'origin: https://dev.g.alicdn.com'
-H 'x-client-data: CIS2yQEIpbbJAQjBtskBCKmdygEIoKDLAQjd8ssBCI74ywEItPjLAQie+csB'
-H 'sec-fetch-site: cross-site'
-H 'sec-fetch-mode: cors'
-H 'sec-fetch-dest: empty'
-H 'referer: https://dev.g.alicdn.com/'
-H 'accept-language: zh-CN,zh;q=0.9,ja;q=0.8'
--data-raw '{"web":{"endpoint":"https://fcm.googleapis.com/fcm/send/d9x_HRJKJHo:APA91bEOqtQLGurHnKVyr8EaIqL06muPvKurbqjrGjkrep9xfj31C4b2iefdN6dZsw-a4oiRi78nCH9mDb0ypOTB4FBL-RP_8iTTWO0BQ56kJrRsbiXEJalx5DqxHdhhb2672sPt8lud","auth":"Z1Lsr2Qwk_NkVZc1sTGSAA","p256dh":"BK1PXbcZAgDWM5Vx0aWZvQ-Wf9s4Si9bybCtFKMn7lrDUSvmh2OvlgKqqsK5RQW9ySvV9KFgnvAIlbioaDbDV-4","applicationPubKey":"BN7QEPrRd6ey-mYKw8OE8hb0uxcxh0WmDq6J6U5pC0oP6qriVKVg3KhAIf6ALu_ZJ315SUT3LpeT_NCuzIEydiE"}}'
--compressed

Interesting that you both ran into this issue at the same time, are these new issues in an existing codebase?
It seems pretty unlikely that this is an issue with the quickstart-js repo. If this is happening in production I'd encourage you to report this to Firebase Support: https://firebase.google.com/support

Ah this is the same issue:
https://github.com/firebase/firebase-js-sdk/issues/5081
Let's centralize the discussion over there.


Combining with an external VAD or diarization

Start/End times of the segments are not always correct. Actually, the first segment always starts at the beginning of the file, even if it starts with a long silence. Apart from the timing being off, it can also cause the model to hallucinate a transcript, as it tries to transcribe this silence.
This can be solved by doing the segmentation based on voice activity detection (VAD) first, and then using whisper to transcribe each segment.
While we are at it, we can even put pyannote in the pipeline to support the full diarization.

Perhaps pulling from https://huggingface.co/spaces/vumichien/Whisper_speaker_diarization to get started with diarization.

WhisperX integration is coming soon :)

Is whisperX now available?


[SPARK-5881][SQL] RDD remains cached after the table gets overridden by "CACHE TABLE"

See JIRA for the example to reproduce the bug (https://issues.apache.org/jira/browse/SPARK-5881).

Test build #27710 has started for   PR 4689 at commit d41d688.

This patch merges cleanly.

Test build #27710 has finished for   PR 4689 at commit d41d688.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27710/
Test PASSed.

This PR also added a CLEAR CACHE statement, would be good to add this in the PR description.

I will open another PR to add the clearCache command. Closing this one


Allow a Row to be passed to merge_cells

This PR updates Worksheet.merge_cells to allow a Row to be passed (or row.cells). Previously, it was necessary to call sheet.merge_cells row.cells.to_a.

Looks like the CI failure is due to the fact that a newer rake is being pulled in that is incompatible with Ruby 1.9. Looks like @donv fixed this in #483 via commit 3622e8a1a9be13a24e0ebc8d3db56cd8b90f1c9e
Another approach to consider besides modifying the make Gemfile would be to use the appraisal gem.

@md5 - would you be so kind as to rebase and push?

@randym I've rebased and pushed


Add Node 20 support

Node 20 went into Long Term Support (LTS) on October 24th. First LTS version is 20.9.0.

didnt realize node 20 wasnt lts yet, we'll want to wait for that

https://nodejs.dev/en/about/releases/

Why does CI get skipped for this PR? Given that we don't have Node 20 for mobile, the MacOS_Node_20 job should fail when it gets to the part where it runs the iOS integration test and iOS backend unit tests.

Why does CI get skipped for this PR? Given that we don't have Node 20 for mobile, the MacOS_Node_20 job should fail when it gets to the part where it runs the iOS integration test and iOS backend unit tests.

The usual jobs were running (just under outdated MacOS_Node_18 name).
Why are we running iOS tests in MacOS_Node_20 job ? Since we don't support Node 20 for iOS, doesn't this prevent us from running MacOS jobs with Node 20 (even though Node 20 supports MacOS) ?

Why are we running iOS tests in MacOS_Node_20 job ? Since we don't support Node 20 for iOS, doesn't this prevent us from running MacOS jobs with Node 20 (even though Node 20 supports MacOS) ?

The iOS tests run in the MacOS_Node_20 job because that's the only place they can run. Having said that, since they obviously pass, apparently everything still works even though the iOS backend is using Node 18 instead of Node 20.


jsdoc linting

Feature request

What is the expected behavior?
Currently there are valid-jsdoc rule and eslint-plugin-jsdoc that validate jsdoc.
What is motivation or use case for adding/changing the behavior?
In this case could be some contradictions, for instance:
"valid-jsdoc": [
 "error",
 {
  prefer: {
   class: "DONTUSE"
 }
],
"jsdoc/check-tag-names": "error"

/** @constructor */
function A {}

jsdoc/check-tag-names error  👆 (@class preferable by default )
/** @class */
function A {}

valid-jsdoc error  👆
So motivation is to prevent such behaviour
How should this be implemented in your opinion?
Use eslint-plugin-jsdoc, since it implement more options
Are you willing to work on this yourself?
yes

Send a PR


Add option to disable presence when any activity is detected

Added an option to disable presence when any other activity is detected. This is useful for e.g. games. Moved the checks to updateData, otherwise if you switch these options on while the presence is active it will remain stuck and not update. Also fixed the version shown in the plugin menu.

The detection is busted in this for some reason. Give me a minute and I'll PR a fix.


⚠ Bofrost.be has degraded performance

In e19c614, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 876 ms

Resolved: Bofrost.be performance has improved in c39d0ff after 313 days, 8 hours, 10 minutes.


bcbio_vm error

Version info

bcbio version (bcbio_nextgen.py --version):
OS name and version (lsb_release -ds):

To Reproduce
Exact bcbio command you have used:
bcbio_vm.py run -n 16 sample.yaml
[sample_yaml.txt](https://github.com/bcbio/bcbio-nextgen/files/4873449/sample_yaml.txt)

Your sample configuration file:
upload:
  dir: /data/NA12878/
details:
  - files: [/data/NA12878/HG001_R1.fastq,/data/NA12878/HG001_R2.fastq]
    description: wgs_HG001
    analysis: 'variant'
    genome_build: hg38
    lane: wgs_HG001
    algorithm:
      aligner: bwa
      trim_reads: false
      mark_duplicates: true
      recalibrate: true
      realign: false
      variantcaller: [gatk-haplotype,freebayes,vardict,strelka2]
      svcaller: [lumpy,manta,gatk-cnv]
      ensemble:
       numpass: 1
       use_filtered: false
      tools_off: [gemini]
      tools_on: [qualimap_full, picard]

Observed behavior
Error message or bcbio output:
Using GATK jar /usr/local/share/bcbio-nextgen/anaconda/share/gatk4-<IP_ADDRESS>-0/gatk-package-<IP_ADDRESS>-local.jar
Running:
    java -Dsamjdk.use_async_io_read_samtools=false -Dsamjdk.use_async_io_write_samtools=true -Dsamjdk.use_async_io_write_tribble=false -Dsamjdk.compression_level=2 -Xms750m -Xmx45864m -Djava.io.tmpdir=/mnt/work/bcbiotx/tmpemesijeh -jar /usr/local/share/bcbio-nextgen/anaconda/share/gatk4-<IP_ADDRESS>-0/gatk-package-<IP_ADDRESS>-local.jar BaseRecalibratorSpark -I /mnt/work/align/wgs_HG001/wgs_HG001-sort.bam --output /mnt/work/bcbiotx/tmpemesijeh/wgs_HG001-sort-recal.grp --reference /usr/local/share/bcbio-nextgen/genomes/Hsapiens/hg38/seq/hg38.fa --spark-master local[16] --conf spark.driver.host=localhost --conf spark.network.timeout=800 --conf spark.executor.heartbeatInterval=100 --conf spark.local.dir=/mnt/work/bcbiotx/tmpemesijeh --known-sites /usr/local/share/bcbio-nextgen/genomes/Hsapiens/hg38/variation/dbsnp-153.vcf.gz -L /mnt/work/align/wgs_HG001/wgs_HG001-sort-callable_sample.bed --interval-set-rule INTERSECTION
' returned non-zero exit status 3.
' returned non-zero exit status 1.

Expected behavior
A clear and concise description of what you expected to happen.
Log files
Please attach (10MB max): bcbio-nextgen.log, bcbio-nextgen-commands.log, and bcbio-nextgen-debug.log.
Additional context
Add any other context about the problem here.

bcbio-nextgen.log

I've tried reproducing this using the sample config file you've provided. It looks like the issue is that your input files are not getting compressed for some reason which causes a downstream failure: OSError: Not a gzipped file (b'@H') and FileNotFoundError: [Errno 2] No such file or directory: '/data/NA12878/HG001_R1.fastq.gz', and so on.
My log shows the following near the beginning:
Running bcbio version: 1.2.3
global config: /mnt/work/bcbio_system-forvm.yaml
run info config: /mnt/work/bcbio_sample-forvm.yaml
[2020-07-17T14:09Z] bgzip input file
[2020-07-17T14:09Z] bgzip input file

while your log shows an error instead:
Uncaught exception occurred
Traceback (most recent call last):
  File "/data/install/bcbio-vm/anaconda/lib/python3.7/site-packages/bcbio/provenance/do.py", line 26, in run
    _do_run(cmd, checks, log_stdout, env=env)
  File "/data/install/bcbio-vm/anaconda/lib/python3.7/site-packages/bcbio/provenance/do.py", line 106, in _do_run
    raise subprocess.CalledProcessError(exitcode, error_msg)
subprocess.CalledProcessError: Command 'docker attach --no-stdin efa65fe7dde4aebdef451abc943a1ff97f9bcafa7bf3610b9f78ed5eb8199c45

Could you share your bcbio-nextgen-commands.log? It might have more information.


bug: add testing to CI

nvm lol CI has tests it's just that they run so fast I thought they weren't actually added to CI. lol


User Preferences Fix

Fixes

Modified interaction.client.user.username to interaction.user.username in certain command files.

Notes

Concurrency was tested with this bugfix and the Ollama update seems to work out of the box for use!
Please refer to #53 for screenshots.

The reason why we remove "client" is because the client for this interaction is the bot, but we don't want that bots Info. We want the info of the user that performed that interaction.
@JT2M0L3Y


fix bug passing single-string safety settings.

I think we just need to reformat with black ., and then I go ahead approve this. Otherwise, LGTM.

Done.


Proxy Pallet is not working on Version 4.0.0

I am trying to add the proxy pallet to the latest version of substrate 4.0.0-dev. It is giving an Error.
Is not compatible with the latest version?
Error:
pankajchaudhary@pankajs-MacBook-Pro testnet-beta-development % cargo build --release
Updating crates.io index
error: failed to select a version for parity-util-mem.
... required by package sp-core v3.0.0
... which satisfies dependency sp-core = "^3.0.0" of package frame-support v3.0.0
... which satisfies dependency frame-support = "^3.0.0" of package frame-system v3.0.0
... which satisfies dependency frame-system = "^3.0.0" of package pallet-proxy v3.0.0
... which satisfies dependency pallet-proxy = "^3.0.0" of package node-template-runtime v4.0.0-dev (/Users/pankajchaudhary/Downloads/testnet-beta-development/runtime)
... which satisfies path dependency node-template-runtime (locked to 4.0.0-dev) of package node-template v4.0.0-dev (/Users/pankajchaudhary/Downloads/testnet-beta-development/node)
versions that meet the requirements ^0.9.0 are: 0.9.0
the package parity-util-mem links to the native library parity-util-mem-ban-duplicates, but it conflicts with a previous package which links to parity-util-mem-ban-duplicates as well:
package parity-util-mem v0.10.2
... which satisfies dependency parity-util-mem = "^0.10.2" of package sc-informant v0.10.0-dev (https://github.com/paritytech/substrate.git?tag=devhub/latest#e6fbbd5c)
... which satisfies git dependency sc-informant (locked to 0.10.0-dev) of package sc-service v0.10.0-dev (https://github.com/paritytech/substrate.git?tag=devhub/latest#e6fbbd5c)
... which satisfies git dependency sc-service (locked to 0.10.0-dev) of package frame-benchmarking-cli v4.0.0-dev (https://github.com/paritytech/substrate.git?tag=devhub/latest#e6fbbd5c)
... which satisfies git dependency frame-benchmarking-cli (locked to 4.0.0-dev) of package node-template v4.0.0-dev (/Users/pankajchaudhary/Downloads/testnet-beta-development/node)
Only one package in the dependency graph may specify the same links value. This helps ensure that only one copy of a native library is linked in the final binary. Try to adjust your dependencies so that only one package uses the links ='parity-util-mem' value. For more information, see https://doc.rust-lang.org/cargo/reference/resolver.html#links.

Looks like you are trying to mix some crates.io released Substrate crates with some from git. This will not work.


Add No Chat Reports

Please update your PR to fix the conflict (README.md no longer contains mods)

Not sure if it's good idea to promote that mod...

Not sure if it's good idea to promote that mod...

I do not see what is wrong with it. Although some people may agree with chat reporting, many do not, and having it listed as a mod on the website would allow users that dislike the system to easily disable it in their game. It is an opinion, and users can choose to use it or not.


D3.csv not supported in d3-dsv

Hi,
I tried to just import d3-dsv.v1.js to use the function of d3.csv("file"..) to read external file. But it seems d3.csv function is not found in the d3-dsv module. Though it works if I use d3.v4.js, but I really like to know which module this function d3.csv is defined? Thanks a lot.
NewtoD3

It's in d3-request. You could find what module you want in the API doc.


derive the type of transpose on arrays of tuples more correctly

Motivation

@sushain97 wanted to know how hard this was.  Not hard. 😛
Test plan

See included automated tests.

Added some more testcases.  I think we get away easy because of the limitations of tuple types.

@froydnj can you also test on Stripe's codebase?

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_Oe3tfKZj3Hl4r1
→ https://go/builds/bui_Oe3tj3wDnSJ21P
→ https://go/builds/bui_Oe3tjvxB2Ma1aY

@froydnj can you also test on Stripe's codebase?

Done.  There are a couple of redundant T.cast/T.must errors that I'll fix up on the next internal bump, but I won't commit this until next week.


Feature: support last_id for Redis stream consumer group

Currently, you can set up a subscriber for a redis stream like this:
@broker.subscriber(stream=StreamSub('stream-name', group='faststream', consumer='1'))
async def handle_msg(msg) -> None:
    logger.info(f"Received: {msg}")

However, if you try to past a last_id parameter:
@broker.subscriber(stream=StreamSub('stream-name', group='faststream', consumer='1', last_id='0-0'))
async def handle_msg(msg) -> None:
    logger.info(f"Received: {msg}")

You get a warning:
RuntimeWarning: last_id has no effect with consumer group
It seems that in the redis/handler.py, it's hard-coding the '>' special id rather than passing through the last_id parameter (which it does when not using a consumer group)
# redis/handler.py,
if stream.group and stream.consumer:
    read = client.xreadgroup(
        groupname=stream.group,
        consumername=stream.consumer,
        streams={stream.name: ">"},
        block=stream.polling_interval,
        noack=stream.no_ack,
    )

else:
    read = client.xread(
        {stream.name: self.last_id},
        block=stream.polling_interval,
    )
``

Is there a reason why we couldn't just pass self.last_id through to the dictionary and have last_id have the default value of ">"?

That way if you want to pull from a different offset while using a consumer group, you can.

@chrisgoddard seems like we broke Redis Streams behavior:
Consumer group start position can be setted only by (xgroup_create command)[https://redis.io/docs/data-types/streams/#consumer-groups]
But, last_id should be always >.

If the ID is the special ID > then the command will return only new messages never delivered to other consumers so far, and as a side effect, will update the consumer group's last ID.

If the ID is any other valid numerical ID, then the command will let us access our history of pending messages. That is, the set of messages that were delivered to this specified consumer (identified by the provided name), and never acknowledged so far with XACK.

Specific ID is suitable only for one-time requests, but not regular consuming. I should rollback this behavior


runtime dependencies cannot depend on RUBY_VERSION

The gemspec is evaluated when the gem is built and baked into the metadata and is not evaluated at install time. Any logic around RUBY_VERSION is applied based on the ruby that built the gem, not the
end user's ruby as is desired.
This is fairly common and has been known to cause issues on other gems, see https://github.com/AuthorizeNet/sdk-ruby/pull/116

cheers - in any case these versions are quite a few years old now so not worth worrying about anyway (and yes RUBY_VERSION logic at gem build time doesn't make sense)

cheers - in any case these versions are quite a few years old now so not worth worrying about anyway (and yes RUBY_VERSION logic at gem build time doesn't make sense)

I've had to revert this, so that tests for ruby < 2.2.2 still work.
It shouldn't be an issue though, because the one runtime dependency that is dependent on RUBY_VERSION, rack, is such that the general version dependency (which will be baked into the gem when built) is a superset of the < 2.2.2 dependency. The latter more restrictive one is still needed for tests.

I've had to revert this, so that tests for ruby < 2.2.2 still work.
It shouldn't be an issue though, because the one runtime dependency that is dependent on RUBY_VERSION, rack, is such that the general version dependency (which will be baked into the gem when built) is a superset of the < 2.2.2 dependency. The latter more restrictive one is still needed for tests.

actually ignore that - that wasn't the problem - added back in

actually ignore that - that wasn't the problem - added back in


Add CPU and GPU options to setup.py

Sonnet and Tensorflow have both different packages with and without GPU support. Our setup.py should be able to handle both cases.
Checkout Sonnet setup.py

Related https://github.com/tensorflow/tensorflow/issues/7166


some URLs crashing

/data/taxnode/128648/relations/children/?sort=name&page=3 => generated 2004 bytes in 312 msecs (HTTP/1.1 500)
/data/taxnode/2191359/relations/children/?page=2&sort=name => generated 2004 bytes in 233 msecs (HTTP/1.1 500)
/data/taxnode/2274495/relations/children/?page=3&sort=name => generated 2004 bytes in 2024 msecs (HTTP/1.1 500)
/data/taxnode/279060/relations/children/?page=2&sort=name => generated 2004 bytes in 238 msecs (HTTP/1.1 500)
/data/taxnode/279060/relations/children/?page=2&sort=name => generated 2004 bytes in 243 msecs (HTTP/1.1 500)
/data/taxnode/279060/relations/children/?page=2&sort=name => generated 2004 bytes in 260 msecs (HTTP/1.1 500)
/data/taxnode/2909/relations/children/?page=1&sort=name => generated 2004 bytes in 259 msecs (HTTP/1.1 500)
/data/taxnode/395708/relations/children/?sort=name => generated 2004 bytes in 280 msecs (HTTP/1.1 500)
/data/uniref100/106975085/relations/taxa/?sort=name => generated 2004 bytes in 209 msecs (HTTP/1.1 500)
/data/uniref100/137693017/relations/taxa/?sort=name => generated 2004 bytes in 117 msecs (HTTP/1.1 500)
/data/uniref100/164538991/relations/taxa/?sort=name => generated 2004 bytes in 99 msecs (HTTP/1.1 500)
/data/uniref100/20693014/relations/taxa/?sort=name => generated 2004 bytes in 102 msecs (HTTP/1.1 500)
/data/uniref100/20750799/relations/taxa/?sort=name => generated 2004 bytes in 356 msecs (HTTP/1.1 500)
/data/uniref100/214651515/relations/taxa/?sort=name => generated 2004 bytes in 101 msecs (HTTP/1.1 500)
/data/uniref100/226177072/relations/taxa/?sort=name => generated 2004 bytes in 122 msecs (HTTP/1.1 500)
/data/uniref100/232143585/relations/taxa/?sort=name => generated 2004 bytes in 146 msecs (HTTP/1.1 500)
/data/uniref100/23900685/relations/taxa/?sort=name => generated 2004 bytes in 94 msecs (HTTP/1.1 500)
/data/uniref100/278436375/relations/taxa/?sort=name => generated 2004 bytes in 125 msecs (HTTP/1.1 500)
/data/uniref100/30149589/relations/taxa/?sort=name => generated 2004 bytes in 137 msecs (HTTP/1.1 500)
/data/uniref100/35453703/relations/taxa/?sort=name => generated 2004 bytes in 161 msecs (HTTP/1.1 500)
/data/uniref100/39076762/relations/taxa/?sort=name => generated 2004 bytes in 113 msecs (HTTP/1.1 500)
/data/uniref100/76295431/relations/taxa/?sort=name => generated 2004 bytes in 163 msecs (HTTP/1.1 500)
/data/uniref100/96172623/relations/taxa/?sort=name => generated 2004 bytes in 104 msecs (HTTP/1.1 500)
/filter/sample/?filter-geo_loc_name=Lake+Erie&page=4&sort=sample_type => generated 2004 bytes in 1813 msecs (HTTP/1.1 500)
/search/dataset/ => generated 2004 bytes in 36 msecs (HTTP/1.1 500)
/search/global/ => generated 2004 bytes in 35 msecs (HTTP/1.1 500)
/search/global/ => generated 2004 bytes in 35 msecs (HTTP/1.1 500)
/search/global/ => generated 2004 bytes in 36 msecs (HTTP/1.1 500)
/search/global/?model= => generated 2004 bytes in 30 msecs (HTTP/1.1 500)
/search/global/?model=global&query= => generated 2004 bytes in 33 msecs (HTTP/1.1 500)
/search/global/?model=global&query= => generated 2004 bytes in 36 msecs (HTTP/1.1 500)
/search/global/?model=global&query= => generated 2004 bytes in 43 msecs (HTTP/1.1 500)
/search/global/?model=global&query= => generated 2004 bytes in 46 msecs (HTTP/1.1 500)
/search/global/?model=global&query= => generated 2004 bytes in 53 msecs (HTTP/1.1 500)
/search/taxnode/ => generated 2004 bytes in 34 msecs (HTTP/1.1 500)

500 status on those /search/ requests correspond to issue #47 so those got fixed there.

Can't reproduce issue with those /relations/ URLs, seems to work fine now.


The MessengerController example seems to return all users.

I'm using the example controller from the examples folder, and it seems to return all users that aren't participants rather than users who are:
https://github.com/cmgmyr/laravel-messenger/blob/master/examples/MessagesController.php#L57

Hi @Rhym, yes that is intended and completely optional. The idea is that you could see anyone who isn't on the current thread and include them in the view. If you don't want this functionality there is no harm in removing it.
The example files are just to show what is possible, but not very performant if used as-is. I'd recommend to pare down on anything you don't need.

@cmgmyr Ah, my mistake completely. Thank you for your prompt response. Have a great day!


quadricuspid aortic valve

Add new term:
quadricuspid aortic valve (under abnormal aortic valve cusp morphology MP:0010595)
DEF: presence of four cusps (leaflets) of equal or varying sizes in the aortic valve instead of the normal three
SYN: QAV
SYN: four-cusp aortic valve
SYN: four-leaflet aortic valve
SOURCES: HP:0031655 , PMID: 28076624
Annotations from J:21034

Add new term:
quadricuspid aortic valve MP:0031538


Is it suitable to train the HF-Net using other common datasets instead of Googble Landmarks/BDD?

When training HF-Net with multi-task distillation, is it feasible to train the HF-Net using some other common datasets instead of Googble Landmarks/BDD? Because we actually don't need labeled data here and is it better to train the whole HF-Net using some other data according to our application scenario?
For example, if we want to deploy it on autonomous vehicles, we could train a HF-Net using a larger training set from Kitti or RobotCar.

Yes, HF-Net can be trained on pretty much any collection of images depending on your target domain: autonomous driving, indoor data, etc. Of course the performance will always be upper bounded by the teacher network.

Thanks!


[bugfix] JSHint error: describe and it are not defined

As mentioned in https://github.com/switchfly/ember-cli-mocha/issues/37#issuecomment-74305975, I think the best way to go is to shim describe and it so that we can:
import { describe, it } from 'mocha';

I just submitted https://github.com/switchfly/ember-mocha/pull/23 to add these shims, and we will need further work in this repo to update the blueprints.

I totally agree. This one should be closed.
BTW, thank you for your awesome works. :smile:

Please see https://github.com/switchfly/ember-cli-mocha/issues/37#issuecomment-75455345 for upgrade instructions.


WithMaximumUtilization

Due to lack of documentation, I was wondering what does the .WithMaximumUtilization(1) would do when a license is generated? Does this mean the license allowed 1 installation? If this is the case how is it validated?

As what i have seen in the source, this only sets the .Quantity property of the license (Per-Developer-License). This is just a property and you would have to implement the logic to check if this limit is exceeded on your own. This could be realized if each installation of your software would register itself with a unique identifier on your own licensing service. You could then prevent activation if too many users have already registered this license.


Add up the FT sensors to the hips

As per the title.

@Nicogene is dealing with this in https://github.com/robotology/robots-configuration/tree/fix/addHipFtErgocub.

Hi @Nicogene
I've rebased again the fix branch on top of the latest devel.
Please, do a pull rebase on your local system to get aligned.

Today I tried the xml files on ergoCub and I noticed that yarprobotinterface does not start because seems that the FT sensors in the hips are not connected, I cannot find them with the FirmwareUpdater, but they are there, they are visible.
cc @AntonioConsilvio @sgiraz

cc @Fabrizio69 too.

Hi, we noticed that there aren't FT sensors in the hips. So we need replace the dummy (the fake FT sensor mounted on the robot) to two real sensors.

We don't have 2 brand new FT58; the only 2 FT58 we have are on iCub3.

cc @giulioromualdi @traversaro

Hi, we noticed that there aren't FT sensors in the hips. So we need replace the dummy (the fake FT sensor mounted on the robot) to two real sensors.

We don't have 2 brand new FT58; the only 2 FT58 we have are on iCub3.

I don't know what would be the timing for having new FT58. The only option to start working with wbd, is to remove the FT from the model.

I don't know what would be the timing for having new FT58.

It'll take some time.

@Nicogene @pattacini would it be possible for you to apply this patch?

Yep 👍🏻

I don't know what would be the timing for having new FT58. The only option to start working with wbd, is to remove the FT from the model. @Nicogene @pattacini would it be possible for you to apply this patch?

Just mentioning that this change is needed only on the ergoCubSN000 model urdf, and not the ergoCubGazeboV1 which has wholebodydynamics device running as of this morning.
If the plan is to change the simulation model as well to keep the consistency, we may also change the configurations to match the change on the real robot before opening the relevant PR @HosameldinMohamed

For the time being I removed them only from the ergocubSN000 see https://github.com/icub-tech-iit/ergocub-software/pull/45


API Updates for v1.1-dev (minor tweaks and additions, 3/3)

These changes cover:

Add a ‘controls’ attribute to Devices, permitting control endpoint exposure in the same style as Node ‘services’
Add a device_id keys to Flow attributes, enabling Nodes which do not act as a Source (e.g. encoders, decoders, scalers)
Permit ‘null’ flow_id against a Sender in order to allow advertisement before internal device routing has occurred

A corresponding discussion is active as part of the AMWA Incubator Basecamp

Merging following no major issues called out on Basecamp. Full testing to be carried out once reference registry implementation updated.


Added guidance on how to add snowflake acct field

Added guidance below based on users asking and having an issue on connecting. usually they include the snowflakecomputing.com. Please can someone verify this is correct guidance? thank you
Note: When connecting to Snowflake, pay close attention to the relevant parts of your Account URL when filling in the "Account" field.  For example, below you can see guidance on what to enter in the "Account" field in dbt Cloud or your profiles.yml file for dbt Core.
• If the URL for your Snowflake account is abc12345.eu-central-1.snowflakecomputing.com, then you should enter abc12345.eu-central-1. Basically, remove the snowflakecomputing.com portion of your URL
Description & motivation

To-do before merge

Pre-release docs
Is this change related to an unreleased version of dbt?

[ ] Yes: please

update the base branch to next
add Changelog components: <Changelog>[New/Changed] in v0.x.0</Changelog>
add links to the "New and changed documentation" section of the latest Migration Guide

[x] No: please ensure the base branch is current
[ ] Unsure: we'll let you know!

Checklist
If you added new pages (delete if not applicable):

[ ] The page has been added to website/sidebars.js
[ ] The new page has a unique filename

If you removed existing pages (delete if not applicable):

[ ] The page has been removed from website/sidebars.js
[ ] An entry has been added to _redirects

Added guidance below based on users asking and having an issue on connecting. usually they include the snowflakecomputing.com. Please can someone verify this is correct guidance? thank you

@mirnawong1 It looks like we have similar Snowflake account information listed here:
https://docs.getdbt.com/guides/getting-started/getting-set-up/setting-up-snowflake#connect-dbt-cloud-to-snowflake
Is there any way to keep both locations in-sync somehow?
Some research
I haven't verified any of the following personally, so your mileage may vary.
It sounds like Snowflake has two formats:

Format 1 (Preferred): Account Name in Your Organization
Format 2 (Legacy): Account Locator in a Region

It might be that only Format 2 works for dbt + Snowflake currently. If so, that means dbt-snowflake would need a format like this.
Ideas for querying the values
Unverified(!) monstrosities like the following might work for querying the relevant Snowflake Account Locator (assuming the user has logged into the Snowflake Web UI:
Option 1: One query with substrings
select lower(current_account() || '.' || replace(substring(current_region(), position('_', current_region())+1), '_', '-') || '.' || left(current_region(), position('_', current_region())-1)) as account_locator;

Option 2: Three queries with result_scan
show regions;
set show_regions = last_query_id();
select
  lower(current_account()) || '.' || "region" || '.' || "cloud" as account_locator
from table(result_scan($show_regions))
where "snowflake_region" = current_region()
;

Here are the relevant Snowflake docs for each of the functions from the monstrosities:

current_region
current_account
position
result_scan
substring
replace
lower

thank you @dbeatty10 that's really helpful and i will check with the team to see if there is a way to keep them in sync.
to clarify, do you mean if something changes on this document, it should be reflected here as well?
i am proposing making the below changes to this document so it's simpler and clearer:
:white_check_mark: Use: db5261993,db5261993.east-us-2.azure<br> :x: Avoid:db5261993.eu-central-1.snowflakecomputing.com |

Your proposed changes to make it simpler and clearer look great and make sense. 🤩
So my ideas & suggestions aren't directly relevant to your edits!
My ideas/suggestions are basically two-fold:

Getting Started with dbt Cloud → Getting set up → Set up and connect Snowflake should match Configuring dbt Cloud → Connecting your database.
Profiles (CLI only) → Snowflake Profile → Account could contain a verified version of one or both of the example queries prototyped above.

It could also contain your emoji hints:

:white_check_mark: db5261993,db5261993.east-us-2.azure  :x: db5261993.eu-central-1.snowflakecomputing.com

in order to sync both pages, i've added src snippet per instructions here: https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/versioningdocs.md#reusing-snippets-of-content
i do need to have pr https://github.com/dbt-labs/docs.getdbt.com/pull/1923 approved first and this is also included in the open pr https://github.com/dbt-labs/docs.getdbt.com/pull/1924 as well

yay thank you sooo much for your help @dbeatty10 ! you da best!


Export PI names (monthly)

https://drive.google.com/drive/u/0/folders/1NVO29WLrUP650FuQbA_CdRDTEtYzM5ft

Developed a process for this and exported a new list.


flutter doctor check throws FormatException: Unexpected extension byte (at offset 5)

After update Flutter is no longer supported in this version.  Flutter doctor reports [x] due to an error, the doctor check did not complete, FormatException: Unexpected extension byte (at offset 5), IntelliJ Version (2021.3 Ultimate Edition), flutter version 2.6.0-12.0.pre.871.

Same problem...

Duplicate of https://github.com/flutter/flutter-intellij/issues/5872

Fixed.

I’m a little confused?  What, where and how?  I don’t see a fix in IntelliJ and rebuilt the Flutter tool, after the build the Flutter doctor repots a crash still.  Can you elaborate on your ‘Fixed’ statement?  Regards.

Yes, I just loaded the new Flutter PLUGIN and my Flutter has been re-established as it was.  Regards and thank you.

thank you soooooooooooo much！！！！！！

Closing this as fixed in dedicated plugin and per above comments.

Reopening this, as this seems to be a Flutter tool issue and have received several reports on it:
/cc @christopherfujino

Duplicate of #94060


Would be great to be able to return Variable Values from an RSJob

Although this may be a headache to implement this could be useful for helping diagnose any issues with any jobs that have been set and any possible outputs from them

I'll have to think about this one. It sounds like it might be hard to do... Any chance you could provide an example of sort of what you might be looking for so I can look in that direction?

I'm in the same situation. on each runspace I output some data on screen for me to later review and return a variable with the actual data I need. When I retrieve the job data using the Receive-RSJob cmd the output contains both everything whats on screen and the variable data.
When using PSJobs, I could do $Job = get-job | receive-job. This will show that console output on screen and then the $Job variable will contain the output variable.
Hope this makes sense.

@greatwallx2 Any chance you could provide some code on that? I'm not quite following what you are describing (or at lease what I am thinking might be wrong) and would like to see an example that I could work off of.

Great script, saved me a ton of time.
@greatwallx2 and @kilasuit , If I understand your request right, this can be done.
What you're asking is that a command is run in a thread, the output is a variable or array, and you want that variable/array available to the rest of the script?
I am doing this currently, parsing through LUN data, grabbing the data I want on each thread/LUN, and then grabbing that data from get-rsjob | receive-rsjob.
example: $lunlist | start-rsjob -name "lundata" -scriptblock{
$luninfo = #foo to parse data from XML file
$lunname = #match name from specific LUN
#info stored in $lunname variable, output to thread by running $lunname. This will result in the HasMoreData field being True.
$lunname
}
#Check for completion of threads, and report status every 30 seconds
do {
$runningcount = (Get-RSjob -name "lundata" | ? {$_.state-eq "Running"}).count
Write-Host "$runningcount threads remaining"
Start-Sleep -Seconds 30
} until ($runningcount -eq 0)
Write-Host "All threads complete"
#Get the output from each thread, and store it in an array
$rsobjs = @()
$rsObjs = Get-RSJob -Name "lundata" | Receive-RSJob
#rsObjs now contains the output from all threads, and is available to the rest of the script.
The real script is more complex, I'll gladly provide more info if this is what you're looking for.

@jeffpeacock - although that is certainly useful what I was more ideally requesting would be to see if it would be possible to capture all variable values that are used within the Runspace just prior to the runspace being closed.
Example being that if I were to mistype something into the scriptblock in Start-RSJob then I may be able to diagnose what it was a bit easier though this is more for those larger operations that you may pass to RSJobs.
Hopefully that helps you understand my ask a bit better now @proxb ? PS sorry for delay in better explaining this

@kilasuit Yea, that does help me out more. Just to clarify, you want a way to view the variables within a runspace prior to it being disposed of for debugging purposes. This might go along with another request to have a way to debug a scriptblock, but I will research this further to see if I can push the variable values to a collection or something if a parameter is used.

may be [hashtable]::Synchronized  can be used in this case ?
something like that:
$syncHash = [hashtable]::Synchronized(@{})

$scriptblock = {
    try {
        #some code
    }
   finally {
        $syncHash['vars'] = (Get-Variable)
    }
}
Start=RSJob $criptblock | Wait-RSJob
$syncHash['vars']

@MVKozlov That would definitely be an alternative to get the variables. Just a quick note that you would have to use $SyncHash like this: ($Using:Synchash)['vars'] for it to work properly within the scriptblock as the parser will complain about assignment expression being invalid.

OK, already found that my example not usable as it was :). Edited to correct form

something strange happen with this example:
$syncHash = [hashtable]::Synchronized(@{})
$scriptblock = {
    try {
        #some code
        $Test = $_
        $Test
    }
   finally {
        #Lock the object to prevent issues with writing to the same object across threads
        [System.Threading.Monitor]::Enter(($Using:syncHash).syncroot)
        #Use pipeline variable so the job name matches the key in the hashtable
        ($Using:syncHash)[$Test] = (Get-Variable)
        #Release the object so other threads can write to it
        [System.Threading.Monitor]::Exit(($Using:syncHash).syncroot)
    }
}

1..10 | Start-RSJob -Name {$_} $scriptblock | Wait-RSJob | Receive-RSJob

#Look at the variables within each scriptblock
Write-Host '---'; $SyncHash.getenumerator() | %{ $_.Value | ? name -eq 'Test' } | Select-Object -ExpandProperty Value

and result:
1
2
3
4
5
6
7
8
9
10
---
10
10
10
10
10
10
10
10
10
10

Agree that $_ was probably not the best choice for Finally block :)
I did see that _ showed the correct value when iterating through the hashtable, but $Test was definitely not playing nice. Could definitely be some weird threading issue with the contents of Get-Variable considering that this is using a runspacepool and the threads are reused. Definitely need to do some more testing.

here is nasty workaround. this way we get all variables values
but it is really nasty :-
($Using:syncHash)[$Test] = (Get-Variable | Foreach-Object {<EMAIL_ADDRESS>Value = (Invoke-Expression ('$'+$_.Name))} })

This would be great to have implemented. I'm doing something similar where I want particular output from the jobs that are running. Currently I need to rely on what's on the output stream, which means you have to be very careful what's getting written out.


Special layout files now work (https://github.com/jenius/roots/pull/379)

This implements a fix from https://github.com/jenius/roots/pull/379 on the v2 branch.

:+1: working just dandy on our project @jenius but wanted to just get your eyes on it, and maybe get a nice lil 2.15 release out :)

Looks good to me. I'll push a release with this shortly. Sorry this was unresolved for so long!

:boom: thanks @jenius

This was also shipped as<EMAIL_ADDRESS>


GPT安全问题

Challenges and Remedies to Privacy and Security in AIGC: Exploring the Potential of Privacy Computing, Blockchain, and Beyond
https://arxiv.org/pdf/2306.00419.pdf
ChatGPT 安全和隐私问题仍然存在于 GPT-4 中
https://www.esecurityplanet.com/threats/gpt4-security/
GPT-4将人工智能安全风险推向高潮
https://venturebeat.com/security/security-risks-evolve-with-release-of-gpt-4/
GPT has entered the security threat intelligence chat
https://venturebeat.com/security/gpt-has-entered-the-security-threat-intelligence-chat/

收录"Challenges and Remedies to Privacy and Security in AIGC: Exploring the Potential of Privacy Computing, Blockchain, and Beyond"。其余内容的原创性有待商榷。


RDS: investigate fixes for checkov issues

Summary
Checkov has identified the following issues with the RDS cluster:
- CKV2_AWS_8  # RDS enable Query Logging
- CKV2_AWS_27 # RDS setup AWS Backup plan

Once the existing AWS resources have been imported into the new Terraform state, we should attempt to fix them.
Related

#101

yup, once the team gets started on Form we should be able to pick this up

Closing this as we have recently reworked the infra and created new issues to review some todos including checkov mentioned in this ticket.


Create Microsoft Defender AV details.yaml

A list of all devices with below AV information
Required items, please complete
Change(s):

Adding a new query to fetch Microsoft defender AV details

Reason for Change(s):

Introduced a new feature for showing up to date reports in Device health tab. Customers are asking for AH queries as well.

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

Yes ran the query on required DB and table using the same KQL query

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Thanks for the contributions. Provided a few small template related suggestions. Would you please make the same changes with the other submissions in the PR as well.

Resolved the comments


Enhance visualisation of ticket states in Web

Reported by atze on 8 Jan 2014 12:12 UTC
The ticket views can be enhanced for different kinds of tickets.
Examples:

Locked meta ticket: children should be grey or folded or something
failed tickets: should be much easier to find, either implement a separate filter view or display them on top of the list
needs attention flag and comments of a meta ticket should be inherited by children (visually, not in DB)
tickets that are assigned to a worker for more than 2 hours should be marked to get attention by the operator

maybe shorter period, if ping command can be evaluated for this

encoding tickets that are locked due to non-obviously reasons should be grey or similar (see ticket:58)

Modified by texec on 13 Jul 2014 10:11 UTC

Comment by texec on 13 Jul 2014 10:12 UTC
Also add icon for servicable states in place where the action button would be (in queue, in service by worker x).


Add test for logical router port collector and refactor

Add test for logical router port and some refactors to help build the test:

Wrap constructor that can pass client interface
Change signature of metrics generator to not return prometheus.Metric
Logical Router Port client build abstraction to list all logical router ports
Extract method to build logical router port metrics

Address: #36
Signed-off-by: William Albertus Dembo<EMAIL_ADDRESS>

/lgtm only nit comments


April Community Gems start

Here is the start of the April Comm Gems.  Please check my answers for accuracy.
@flippedcoder  will be adding to this and completing.

@jendefig is it ready? or WIP? (In general, it's better to ping everyone when we have something close to the final version.)

deployment is broken, #2411 - we'll need to merge master when it's fixed

@jorgeorpinel @shcheklein Would you mind reviewing?

Thanks for all the feedback @shcheklein! I made some updates to the post that should clear up the comments so far. Let us know if there's anything else we can do better. :)

At this point we may need to change dates and make this May Community Gems and put out on the Friday the 28th?

@jendefig Probably... 😔 Sorry this one is taking so long.

@shcheklein I reached out and got some help clarifying the last few comments. Hopefully it's good this time!

@flippedcoder I think we need to adjust dates now and it should good to go?

@shcheklein I pushed up those changes to the date and image so it's ready to merge whenever you are!


[Docs] Section about running on GPUs

Description
This PR adds a small "Running on GPUs" section to the documentation's Advanced Usage Guide.
It is mostly a simplified adaption of this announcement.
I tried to keep it short as a more "hands-on" section. If you feel the need for any changes, just let me know and I can adapt the text.
Fixes #1387

Sure, just updated the docs to be a subsection.

Thanks @iagoleal!