User-based service protection API limits

The User-based service protection API limits section starts with "Two of the" and then there are 3 factors. Do we know which 2 or random?

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

ID: cc0a8dff-9a51-bd7b-bc9a-841acba03aba
Version Independent ID: cc0a8dff-9a51-bd7b-bc9a-841acba03aba
Content: Service protection API limits - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/data-entities/service-protection-api-limits.md
Service: dynamics-365-cross-app
GitHub Login: @jaredha
Microsoft Alias: jaredha

Yes, this is detailed in the table in that section of the topic. The "Number of requests" and "Execution time" limits are measured within a five-minute sliding window.


Updated links to terms of use

Docs Build status updates of commit 6bc8449:
:warning: Validation status: warnings

File
Status
Preview URL
Details

.openpublishing.redirection.json
:warning:Warning

Details

docs/breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/docfx.json
:white_check_mark:Succeeded

docs/rest/toc.yml
:white_check_mark:Succeeded

.openpublishing.redirection.json

[Warning] Master redirection file .openpublishing.redirection.json has a redirection rule on file 'docs/rest/terms-of-use.md'. However, the file already exists in the Git repo in conflict with the redirection rule. Docs will ignore the file and populate with the redirection rule instead. To resolve this warning, please remove the original file in Git repo.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


datapath:  Create DSR CT entry even if CT entry is found

TODO

[ ] Update docs
[ ] Create issue for enabling DSR with svc annotation

Fix #10897

test-me-please

test-me-please

Discussed offline, a different approach will be taken to fix the issue.


Enchancement rename materialized-view to materialized-index

Proposed changes
In the past doris, we have rollup and materialized view, which are fully synchronized with the base table and can be used to speed up the query.
In the new version, we have introduced multiple table materialized view, which can be directly queried and cannot accelerate the query of the base table. Its positioning is more like a view, while the rollup/mv in the old version is more like an index.
In order to clarify their design positioning, I renamed materialized view to materialized index in this pr. Since then, doris supports syntax like create materialized index, but the old syntax is still supported.
This pr mainly made the following changes:

Added materialized-index related syntax support
Change materialized-view in related documents to materialized-index
Change the case in the related test (feut/regression-test) to materialized-index

Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.31 seconds
stream load tsv:          427 seconds loaded<PHONE_NUMBER>9 Bytes, about 167 MB/s
stream load json:         23 seconds loaded<PHONE_NUMBER> Bytes, about 97 MB/s
stream load orc:          72 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          30 seconds loaded 861443392 Bytes, about 27 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230413072054_clickbench_pr_128451.html

run buildall


Use the current version of the instance registry API

Is your feature request related to a problem? Please describe.
The current implementation of the instance registry (IR) in the WebAPI is using the old version of the IR API, which did not consider docker functionality.
Describe the solution you'd like
Upgrade the WebAPI to use the current version of the IR API, which is documented in the current development branch of the IR repository (the .yaml file).  Please keep in mind the workflow we intended for instances:
IF an environment variable called 'INSTANCE_ID' is present, we are running inside a docker container. This means:

Call 'reportStart(id)' with the id form the environment variable instead of the old 'register' when the application successfully started
Call 'reportFailure(id)' with the id from the environment variable instead of the old 'deregister' when a failure occured

IF no such variable is present, we are running outside a docker container. This means:

Call 'register()' and retrieve and store the id the IR assigned (like it is done now)
Call 'deregister()' on failure (like it is done now)

EDIT
The current version of the branch "feature/newApiImplementation" now also defines the "/reportStop" endpoint. This, in contrary to "/reportFailure", should be called when the WebApi is shut down manually (and successfully). This way the IR will know that, while the container is still running, the application inside the container is not running anymore.

Tested by @johannesduesing


Better highlighting

[x] Update test code to handle begin/end regexes

Closes #5, #11

This will go out in the next release


Mouse stutters and pc slows down while using V13 classic wallet on windows

Hello,
I think it's a rather old issure, but I wanted to bring it up again. Whenever I start the classic wallet on my Windows 10 laptop, the usability decreases masively. The mouse stutters from time to time and it is not possible to watch a simple Youtube video anymore because the audio stutters as well. I could understand it, if it was a very old laptop, but this is a brand new and pretty powerful one.
Here you can find a screenshot from my taskmanager with the wallet open:
https://imgur.com/a/mp16NBY

Duplicate of https://github.com/nanocurrency/raiblocks/issues/227

Thanks for the reference. I thought it was addressed with v13, so I wanted to bring it up again.

Thanks for the answer.
Basically it doesn't matter. While it's synching it's worse but the problem is still there when the wallet is fully synched. Also I set io_threads to 2 now and while the CPU load is lower now the audio in a video still stutters from time to time.

@Nanoraii Cinebench generates a completely different load than the node. The node uses a db which mmap's disk files, and which causes a large amount of hard pagefaults. Windows gets issues like audio drops when there's a flurry of pagefaults.

Thanks a lot for the explanation! I'm really a beginner in such things. Would it help to load the whole ledger into the RAM? Or is that not feasible?

I don't know if it's the April update of Windows or the transition to state blocks, but my problem seems to be gone. My laptop runs completely smooth now with the Nano wallet open.


Invalid constants

include/flatcc/portable/pendian.h includes the following constants in the bswap macros:
#define bswap32(v)                                                          \
      ((((uint32_t)(v) << 24))                                              \
          | (((uint32_t)(v) << 8) & UINT32_C(0x00FF0000U))                  \
          | (((uint32_t)(v) >> 8) & UINT32_C(0x0000FF00U))                  \
          | (((uint32_t)(v) >> 24)))
#endif

#ifndef bswap64
#define bswap64(v)                                                          \
      ((((uint64_t)(v) << 56))                                              \
          | (((uint64_t)(v) << 40) & UINT64_C(0x00FF000000000000ULL))       \
          | (((uint64_t)(v) << 24) & UINT64_C(0x0000FF0000000000ULL))       \
          | (((uint64_t)(v) << 8) & UINT64_C(0x000000FF00000000ULL))        \
          | (((uint64_t)(v) >> 8) & UINT64_C(0x00000000FF000000ULL))        \
          | (((uint64_t)(v) >> 24) & UINT64_C(0x0000000000FF0000ULL))       \
          | (((uint64_t)(v) >> 40) & UINT64_C(0x000000000000FF00ULL))       \

The problem comes in that UINT32_C and UINT64_C append U and ULL to the end of the constant passed to them, so the resulting text has U and ULL appended twice:
include/flatcc/flatcc_endian.h", line 76.3: 1506-258 (S) Hexadecimal integer constant 0x00FF000000000000ULLULL is not valid.
ULLULL is not a valid ANSI C99 specifier.  GCC must let it thru, but other compilers do not.
Remove the extra constant specifiers from inside the bswap() macros and let UINT32/64_C add them naturally.
Note:
I'm doing testing of flatcc under AIX using the native IBM compiler, so I'll probably have some more suggestions/comments like this.
Thanks!

Fixed, and thanks for reporting this - the portable library depends on such user feedback.
Please provide feedback on how flatcc works on AIX also if there are no further problems.


Work on martini lunch page

Fix double cactus link - one is cuoco.
Add some fb/twitter icon links.

Fixed Cuoco/Cactus link.

Added social media icons linked to FB &/or Twitter for all sit down restaurants that have them.


Tidy up PicoCliDelegate

No functional changes.

Removes extra declarations for subcommands where they don't add any value.
Remove else statement where the if does a return
Remove copying over subcommand args when we can just run the whole thing again,
this time in the knowledge that we are executing a subcommand.

Codecov Report

Merging #1077 into master will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #1077      +/-   ##
============================================
- Coverage     99.39%   99.39%   -0.01%
  Complexity     2257     2257
============================================
  Files           342      342
  Lines          6154     6145       -9
  Branches        358      358
============================================
- Hits           6117     6108       -9
  Misses            5        5
  Partials         32       32

Flag
Coverage Δ
Complexity Δ

#unittests
99.39% <100.00%> (-0.01%)
2257.00 <0.00> (ø)

Impacted Files
Coverage Δ
Complexity Δ

...com/quorum/tessera/config/cli/PicoCliDelegate.java
97.87% <100.00%> (-0.19%)
19.00 <0.00> (ø)

Continue to review full report at Codecov.

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


Update collections

[x] Add Collection.models plain array
[x] Pluralize schema classes (schema.user => schema.users)
[x] add this.serialize to route handlers

woot - last breaking changes for 0.2! It's about time we release.


feat: Uses out-of-band protocol instead of didexchange

Uses out-of-band protocol instead of didexchange.
Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

@soluchok have you tested this in the sandbox with updated adapter and edge-agent images?

@soluchok have you tested this in the sandbox with updated adapter and edge-agent images?

I tested only edge-agent. Also, I asked @sudeshrshetty to help me to check it. sandbox I did not test.

@soluchok

@soluchok have you tested this in the sandbox with updated adapter and edge-agent images?

@llorllale I tested only edge-agent. Also, I asked @sudeshrshetty to help me to check it. sandbox I did not test.

Please test in the sandbox and make sure the DIDComm flow works.


Look into .Net Core's Service Model

Reminder from Discord

Grabbed by Finite

Turns out the service model is part of ASP.Net Core, not .Net Core, and I dont want to bring in another dep from outside of the corefx. Closing this.

Don't think the service model is a part of ASP.Net Core, but instead a part of Microsoft.Extensions.DependencyInjection or Microsoft.Extensions.DependencyInjection.Abstractions NuGet packages.

That's the namespace which ASP.NET DI uses; see https://github.com/aspnet/DependencyInjection


remove unused dependencies

Are the following used?

minimist
express
sinon
npm-logical-tree

Nope. They should be removed

Resolved in #1685.


No support for Locust performance test tool

When I use the Locust performance test tool (see Locust.io) with the Artifactory Python package it will collect and stats. Other than that works fine.
I am using Locust 1.4.4., WIN7 , 16GB on a VM.

BTW I am using Python 3.8


split systemverilog compile and generate

added questa as simulation target

Hi, Simon, thanks for your contribution, please follow the instruction above to sign a Contributor License Agreement (CLA).

I think this is now done.

From: taoliug<EMAIL_ADDRESS>Sent: 16 February 2019 08:36
To: google/riscv-dv
Cc: Simon Davidmann; Author
Subject: Re: [google/riscv-dv] split systemverilog compile and generate (#5)
Hi, Simon, thanks for your contribution, please follow the instruction above to sign a Contributor License Agreement (CLA).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/google/riscv-dv/pull/5#issuecomment-464315647, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADdf5KDEdo9gR_tqRuooK1oyr3Sup46Aks5vN8MKgaJpZM4a-GEV.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

Googlers can find more info about SignCLA and this PR by following this link.

Simon has signed LCA, please review

Simon, somehow I cannot find your username or corporate account in the CLA search, can you double check you have signed CLA correctly?

BTW, I think you should sign as corporate signer. I cannot find Imperas in the corporate signer list though


How to broadcast the original image to UDP

I'm not sure offhand, this is probably more a ROS question than OPT question. This discussion may be of some use. I hope it's of some use!


Backtesting - ValueError: Out of range float values are not JSON compliant

Describe the bug
When running backtesting for kucoin with 3 order levels on a total amount of 70usdt, im getting an error of Expecting value: line 1 column 1 (char 0). I tried to increase the total amount but getting same error

Check the backend-api logs found:
INFO:     <IP_ADDRESS>:34744 - "GET /is-docker-running HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:34750 - "GET /all-controller-configs HTTP/1.1" 200 OK
/opt/conda/envs/backend-api/lib/python3.10/site-packages/hummingbot/strategy_v2/backtesting/backtesting_engine_base.py:279: RuntimeWarning: divide by zero encountered in scalar divide
  sharpe_ratio = returns.mean() / returns.std() if len(returns) > 1 else 0
INFO:     <IP_ADDRESS>:34760 - "POST /run-backtesting HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py", line 396, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 70, in __call__
    return await self.app(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/fastapi/applications.py", line 1054, in __call__
    await super().__call__(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/applications.py", line 123, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/middleware/errors.py", line 186, in __call__
    raise exc
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/middleware/errors.py", line 164, in __call__
    await self.app(scope, receive, _send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 65, in __call__
    await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/routing.py", line 756, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/routing.py", line 776, in app
    await route.handle(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/routing.py", line 297, in handle
    await self.app(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/routing.py", line 77, in app
    await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
    raise exc
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
    await app(scope, receive, sender)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/routing.py", line 72, in app
    response = await func(request)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/fastapi/routing.py", line 307, in app
    response = actual_response_class(content, **response_args)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/responses.py", line 184, in __init__
    super().__init__(content, status_code, headers, media_type, background)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/responses.py", line 41, in __init__
    self.body = self.render(content)
  File "/opt/conda/envs/backend-api/lib/python3.10/site-packages/starlette/responses.py", line 187, in render
    return json.dumps(
  File "/opt/conda/envs/backend-api/lib/python3.10/json/__init__.py", line 238, in dumps
    **kw).encode(obj)
  File "/opt/conda/envs/backend-api/lib/python3.10/json/encoder.py", line 199, in encode
    chunks = self.iterencode(o, _one_shot=True)
  File "/opt/conda/envs/backend-api/lib/python3.10/json/encoder.py", line 257, in iterencode
    return _iterencode(o, 0)
ValueError: Out of range float values are not JSON compliant
2024-06-25 12:24:54,084 - apscheduler.executors.default - WARNING - Run time of job "update_active_bots (trigger: interval[0:00:10], next run at: 2024-06-25 12:25:02 UTC)" was missed by 0:00:01.109299
INFO:     <IP_ADDRESS>:42104 - "GET /is-docker-running HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:42106 - "GET /all-controller-configs HTTP/1.1" 200 OK

Steps to reproduce bug

Clone https://github.com/hummingbot/deploy and run bash setup.sh to setup
Once setup is complete, open the deploy directory and go to bots/conf/controllers
Create a .yml file and paste the config below.( This was created from dashboard )buy_amounts_pct:
- 0.16666666666666666
- 0.16666666666666666
- 0.16666666666666666
buy_spreads:
- 0.01
- 0.015
- 0.02
candles_config: []
connector_name: kucoin
controller_name: pmm_simple
controller_type: market_making
cooldown_time: 60.0
executor_refresh_time: 180.0
id: robin-compute_0.2
leverage: 20
manual_kill_switch: null
position_mode: HEDGE
sell_amounts_pct:
- 0.16666666666666666
- 0.16666666666666666
- 0.16666666666666666
sell_spreads:
- 0.01
- 0.015
- 0.02
stop_loss: 0.015
take_profit: 0.006999999999999999
take_profit_order_type: 2
time_limit: 900
total_amount_quote: 70
trading_pair: XCAD-USDT
trailing_stop:
  activation_price: 0.018
  trailing_delta: 0.002

Reload dashboard page, go to config generator
Load the config then run backtest

Reproduced when using the config below on different exchanges binance, kucoin, bybit on 15mins interval
buy_amounts_pct:
- 0.5
buy_spreads:
- 0.005
candles_config: []
connector_name: bybit
controller_name: pmm_simple
controller_type: market_making
cooldown_time: 180.0
executor_refresh_time: 300.0
id: test-config_0.1
leverage: 1
manual_kill_switch: null
position_mode: HEDGE
sell_amounts_pct:
- 0.5
sell_spreads:
- 0.005
stop_loss: 0.01
take_profit: 0.006999999999999999
take_profit_order_type: 2
time_limit: 900
total_amount_quote: 50
trading_pair: XRP-USDT
trailing_stop:
  activation_price: 0.018
  trailing_delta: 0.002


Receiving error in files option

I have tried several combinations:
files: '/**/*.css',

or
files: './src/**/*.less',

Here is full webpack.config.js if this will help
/**
 * webpack.config.js
 * Mike Erickson<EMAIL_ADDRESS> * 2016.06.06 18:40 (mikee)
 * 2016.07.20 14:44 - mikeerickson
 * =============================================================================
 */

var path                = require('path')
var ProgressBarPlugin   = require('progress-bar-webpack-plugin')
var CopyWebpackPlugin   = require('copy-webpack-plugin');
var BuildNotifierPlugin = require('webpack-build-notifier')
var msg                 = require('gulp-messenger')
var webpack             = require('webpack')
var StyleLintPlugin     = require('stylelint-webpack-plugin');

var outputPath     = path.join(__dirname, '/dist')
var outputFilename = 'bundle.js'
var publicPath     = outputPath

var webpackConfig = {
  context: __dirname + '/src',
  devtool: 'eval', // source-map
  entry:   './index.js',
  output: {
    path:       outputPath,
    filename:   outputFilename,
    publicPath: publicPath
  },
  // devServer: {
  //   contentBase: outputPath,
  //   hot: true
  // },
  module: {
    preLoaders: [
      {test: /\.js$/, loader: "eslint-loader", exclude: /node_modules/}
    ],
    loaders: [
      {test: /\.js?$/,   loaders: ['ng-annotate', 'babel'], exclude: /node_modules/},
      {test: /\.html?$/, loaders: ['raw']},
      {test: /\.less$/,  loaders: ['style!css!less']},
      {test: /\.css$/,   loader:  "style!css"},
    ]
  },
  plugins: [

    // Display notification when build completed
    new BuildNotifierPlugin(),

    new StyleLintPlugin({
      configFile: '.stylelintrc',
      context: 'inherits from webpack',
      files: './src/**/*.less',
      failOnError: false,
    }),

    // Removes duplicate modules from the build
    new webpack.optimize.DedupePlugin(),

    // Configure ProgressBar
    new ProgressBarPlugin({
      format: msg.chalk.yellow.bold('  Building [:bar] ') + msg.chalk.green.bold(':percent') + msg.chalk.bold(' (:elapsed seconds)'),
      clear:   false,
      summary: true
    }),

    // Copy assets not part of bundle
    new CopyWebpackPlugin([
      { from: './index.html', to: './index.html' },
      { from: './fonts',      to: './fonts' },
      { from: './css',        to: './css' },
      { from: './data',       to: './data' },
    ]),

    // Compress build
    new webpack.optimize.UglifyJsPlugin({
      compress: {
        warnings: false
      }
    }),

  ]
};

module.exports = webpackConfig;

This is probably caused by the (default) webpack context. If relative paths are ok you can just use files: 'src/**/*.less',.

@mikeerickson sorry for the delayed response, but @cascornelissen's suggestion would be what I would suggest. Is this still an issue for you?

@mikeerickson I'm going to close this for now, the documentation was improved recently in #36. Hope this isn't an issue for you anymore!


Update to WQX ref (ft, in, m) and TADA (mass/mass to mass/volume) ref

Kevin has updated the WQX ref to reflect the changes. We decided to keep target units to inches, and fixing those 3 rows for the conversion factors.
I've added additional rows in TADA.PriorityCharConvertRef for common mass/mass to mass/volume conversions.
I ran a random testing TADA_DataRetrieval and found a #/100mL unit with no conversions to CFU/100mL, and added on this as a row to TADA.PriorityCharConvertRef in the csv.
Checking the conversion factors for reasonableness will be good for review, and if these additional rows make sense.

The unit conversions (output from TADA_ConvertResultUnits) and the TADA version of the WQX unit reference table look good now. However, the output df from TADA_CreateUnitRef still does not reflect the correct conversion factor (TADA.WQXUnitConversionFactor). See test2 output below.
I am sure this can be fixed, but I was also thinking that it might not be necessary to include the conversion factors and coefficients in the table produced by TADA_CreateUnitRef, since that information is available to users if they want it via TADA_ConvertResultUnits when transform = FALSE. Either way, it looks like TADA_CreateUnitRef needs additional review/updating to finish off this issue.

`r
test <- TADA_DataRetrieval(
startDate = "2020-01-01",
endDate = "null",
countrycode = "null",
countycode = "null",
huc = "null",
siteid = "null",
siteType = "null",
characteristicName = "Depth, bottom",
characteristicType = "null",
sampleMedia = "null",
statecode = "null",
organization = "null",
project = "null",
providers = "null",
applyautoclean = FALSE
)
test2 <- TADA_CreateUnitRef(test)
test3 <- TADA_ConvertResultUnits(test, transform = FALSE)
test4 <- TADA_ConvertResultUnits(test)
`
Note: I addressed a few other issues as part of the PR:

Updated TADA_FlagResultUnit so it can now run without autoclean being run first
I found that PPM was "Accepted" unit for "Depth, Bottom". Changed this to "Rejected" in WQX validation table. Reviewed many other depth result units as well & updated the WQX validation table for those as part of this update.
Updated reference tables and example data again
Removed TADA.WQXTargetUnit and added TADA.Target.ResultMeasure.MeasureUnitCode to required cols
Updated ordering of columns and comparable data ID when transform = FALSE
Adds TADA.WQXUnitConversionCoefficient and TADA.WQXResultUnitConversion to column ordering (only relevant when transform = FALSE)
Updated documentation

@cristinamullin - the reason I had left the units in the TADA_CreateUnitRef output was for cases where a user might want to convert to a unit that we don't have in the unit refs. But if that scenario is not going to happen (or extremely unlikely), then I agree we can remove those columns as users can access the conversion info through TADA_ConvertResultUnits when transform = FALSE.
@wokenny13 - do you want to work on the updates needed for TADA_CreateUnitRef? Or would you like me to do that?

test <- TADA_DataRetrieval(
startDate = "2020-01-01",
endDate = "null",
countrycode = "null",
countycode = "null",
huc = "null",
siteid = "null",
siteType = "null",
characteristicName = "Depth, bottom",
characteristicType = "null",
sampleMedia = "null",
statecode = "null",
organization = "null",
project = "null",
providers = "null",
applyautoclean = FALSE
)

I can work on making these updates. I will let you know if I have any questions as I catch up on these comments.

@hillarymarler @cristinamullin

Updated list of mass/mass to mass/volume TADAPriorityCharConvertRef.csv units to be converted to mg/L and UG/L.
Rearranged columns of output for TADA_CreateUnitRef. Keeping in the Conversion Factor and Coefficient but hope to make it clear which columns are being referenced with this rearrangement.
Included the updates to test-that CriteriaComparison.R in this pull request - see comments in #525

These updates look great - thank you @wokenny13! I just merged in updates from develop. Once the checks complete, it can be merged in.


nimbleModel class name too long

Hi, first thanks for this great software.
Using NIMBLE version 0.9.0 on linux I get the following error when moving from a model with 6 dcar_proper random effects to 7 dcar_proper random effects, i.e., the model builds, complies, and samples without error when I comment out the components for the 7th random effect, but the addition of the 7th random effect elicits the error below.

Rmodel <- nimbleModel(code, constants, data, inits)
defining model...
Adding adj, num as data for building model.
building model...
Error in @<-(*tmp*, ".xData", value = ) :
class name too long in '@<-'

Here's the model
code <- nimbleCode({
for(i in 1:p){
    beta[i] ~ dnorm(0, sd = 100)
    tau[i] ~ dgamma(0.001, 0.001)
    gamma[i] ~ dunif(-1, 1)
}

sigma ~ dgamma(0.001, 0.001)

s1[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[1], gamma=gamma[1])
s2[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[2], gamma=gamma[2])
s3[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[3], gamma=gamma[3])
s4[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[4], gamma=gamma[4])
s5[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[5], gamma=gamma[5])
s6[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[6], gamma=gamma[6])
s7[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[7], gamma=gamma[7])
#s8[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[8], gamma=gamma[8])
#s9[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[9], gamma=gamma[9])
## s10[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[10], gamma=gamma[10])
## s11[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[11], gamma=gamma[11])
## s12[1:N] ~ dcar_proper(mu[1:N], adj=adj[1:L], num=num[1:N], tau=tau[12], gamma=gamma[12])

for(i in 1:n) {
    mu[i] <- 0
    y[i] ~ dnorm(x[i,1]*(beta[1] + s1[poly.id[i]]) + x[i,2]*(beta[2] + s2[poly.id[i]]) + x[i,3]*(beta[3] + s3[poly.id[i]]) +
                 x[i,4]*(beta[4] + s4[poly.id[i]]) + x[i,5]*(beta[5] + s5[poly.id[i]]) + x[i,6]*(beta[6] + s6[poly.id[i]]) +
                 x[i,7]*(beta[7] + s7[poly.id[i]]),# + x[i,8]*(beta[8] + s8[poly.id[i]]) + x[i,9]*(beta[9] + s9[poly.id[i]]) +
                 #x[i,10]*(beta[10] + s10[poly.id[i]]) + x[i,11]*(beta[11] + s11[poly.id[i]]) + x[i,12]*(beta[12] + s12[poly.id[i]]),
                 sd = sigma)
}

})
N <- length(num)
L <- length(adj)
constants <- list(poly.id = poly.id, adj = adj, num = num, n = n, p = p, N = N, L = L)
data <- list(y = y, x = x)
inits <- list(sigma = 0.01, beta = beta, tau = rep(1, p), gamma = rep(0.5, p),
s1 = rep(0, N), s2 = rep(0, N), s3 = rep(0, N),
s4 = rep(0, N), s5 = rep(0, N), s6 = rep(0, N),
s7 = rep(0, N))#, s8 = rep(0, N)), s9 = rep(0, N)),
#s10 = rep(0, N), s11 = rep(0, N), s12 = rep(0, N))
params <- c("beta", "tau", "gamma", "sigma", "s1", "s2", "s3", "s4", "s5", "s6", "s7")#, "s8", "s9", "s10", "s11", "s12")
Rmodel <- nimbleModel(code, constants, data, inits)

Hi @finleya Thanks for filing this issue.  We'll look into it. In the meantime, let me suggest a workaround.  I think if you break up your long sum into a couple of terms and then add those together, the problem will be avoided.  i.e. something like
part1[i] <- x[i,1]*(beta[1] + s1[poly.id[i]]) + x[i,2]*(beta[2] + s2[poly.id[i]])
part2[i] <- x[i,3]*(beta[3] + s3[poly.id[i]]) + x[i,4]*(beta[4] + s4[poly.id[i]])
y[i] ~ dnorm( part1[i] + part2[i], sd = sigma)

(where obviously I haven't included all the terms you want in part1[i] and part2[i]).  Fingers crossed.

@finleya It could potentially also help to provide the name argument to nimbleModel.  Just trying to give some quick things to try until we have time to take a look.

Hi Perry,
Thank you very much for the ultra quick response and fix! I had tried passing the name argument without success, but your "part" approach worked. Again, thanks to you and the NIMBLE team for this fantastic software!

Thanks @finleya.  Phew, glad we got a workaround for you.  If you don't mind, I'm going to reopen the issue so that the dev team remembers to look into it further.  It's not very friendly behavior!

see RnameToCppName - if too long, truncate and add on _uID and use labelmaker (all_utils.R).

@perrydv This is more complicated than I anticipated. I see that the same strings are being passed through Rname2CppName repeatedly and we are expecting that the resulting names in a pair of .h and .cpp files are expected to be the same.
But if I truncate and then tack on additional characters to make the result unique, when it gets passed through Rname2CppName again it gets truncated again and a new unique label is tacked on, which results in inconsistent names between the .h and .cpp files.
I could truncate with some additional chopping off as a buffer, so the resulting truncated name, even after having additional  characters tacked on, is not subject to the truncation. Feels kludgey as I don't know for sure how many characters will maximally be tacked on, but I can presumably be generous.
However, it does feel like Rname2CppName is being used in cases where it doesn't need to be, given that after an initial usage in building the model, I don't think that any problematic characters (e.g., brackets) would remain in any of the names of things in the R model. Nor do I see why usage of deparse would be needed. So given the only operations are deparse and gsub, usage of Rname2CppName in compiling is surprising me, but it's likely there is a need for it that I am not seeing.

Per Perry's suggestion, I added a check that only does truncation if hasn't been truncated before, based on grepping for "TRUNC", which is the string I used in the label maker. The use of three underscores is because we have cases where we insert two underscores, so this felt like the best way to ensure one would not have the string occur except via insertion under these circumstances.


DBZ-191 support parsing default value

https://issues.jboss.org/browse/DBZ-191

Hiya,
Any chance you can support this for PostgreSQL, as well? It suffers from the same issue.

@ian-axelrod Could you please raise a separate Jira for it? This will need to be done in different way as we would need to include chanec into decoder plugins too.

Hey @sweat123 getting back to this one (sorry for the long delay, I was on PTO/conference travel). I'll review this one ASAP. What's the name we should add for you to the authors list, "Lao Mei"?
@jpechane, I think you took a look already, right? What's your take, any bigger issues remaining? On a related note, are default values supported by Roman's new parser implementation already?

Hey @ian-axelrod, did you get a chance to file that JIRA issue for adding this to the PG connector? Also, I'm curious why you need the default value in the schema. Actual messages should always contain the value, so I'm wondering when the schema's default value would be applied. That's not to say I'm not for implementing this, I'm just eager to learn more about the use case. Thanks!

Last @gunnarmorling question was already answered in the corresponding JIRA ticket, but for those who are not following and are wondering here's the link: https://issues.jboss.org/browse/DBZ-191?focusedCommentId=13581673&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13581673. Just FYI.

@gunnarmorling I have not filed it. I do not think I will have a chance to contribute myself, as I only have weekends available and I do not desire to code over the weekend when I already code 6-12 hours 5 days a week. I love coding, but I am not obsessed, hehe. I will probably have to look into a paid solution that sees more frequent updates, sadly.
I can file it so that others can take it on, however. Is that still needed?

@ian-axelrod, totally understandable regarding finding the time for contributing. Everything helps, so if you just filed that JIRA issue for your requirement, that'd be great already.
In terms of frequent updates, we aim at a 3-weekly release cadence, which was interrupted recently a bit due to me being on leave and conference travel for a while. The change here (for MySQL) is scheduled for 0.8 which is due in two weeks.
As far as paid support is concerned, can you please send me an e-mail to "myfirstname AT hibernate.org" to discuss that topic? Cheers!

Thanks, @burdiyan, that makes a lot of sense. If you have any thoughts on that timestamp issue (function-based default value), please let us know.

@gunnarmorling Oh, I haven't thought about the case of timestamps default VALUE. I think to avoid compatibility issues with the schema registry in this particular case the default value on the schema could be 0/empty string (I don't remember if TIMESTAMP is parsed to string or long from the top of my head now).
But basically, the idea is to put something in the schema to avoid issues on the schema registry side, since anyway the correct default value will be set by the database itself, so in theory there's nothing to be worrying about.

Yeah, that could be a way out. Probably would have to be something like epoch then (1970-1-1 00:00:00). Not ideal, but as you say, if documented well, it may be good enough. Let's see what @sweat123 thinks about it and then decide.

@gunnarmorling It should not be difficult to merge this PR with the new parser. I think the PR looks great but not all datatypes are sill supported e.g. geometry.
We should either support all types or enumerate those supported to avoid confusion between users.

@jpechane GEOMETRY columns don't support default values as per the docs (as JSON, BLOB and TEXT). Do you see any specific types still unsupported?

@gunnarmorling Thanks for pointing it out to me! I went through the rest of datattypes and IMHO we are clear to go.

Thanks for double-checking. It looks good to me, too. Going to merge it and
add a sentence to the docs about the default values being considered in
schemas.

Rebased and applied. Thanks a lot, @sweat123! I added the name "Luobo" to COPYRIGHT.txt (taken from the commit authorship). Please let me know if I should use something else instead.
Great contribution overall, much appreciated!

@gunnarmorling Thanks for the review!
My name is WenZe Hu, thanks a lot! :smile:


Get pixel value by lat/lon from a local tile (COG)

Thanks to localtileserver @banesullivan https://github.com/banesullivan/localtileserver/issues/43, it is now possible to get pixel values from a local tile. This feature will improve the Inspector tool to support local tile.
https://github.com/banesullivan/localtileserver/blob/main/localtileserver/client.py#L183
from localtileserver import get_leaflet_tile_layer, TileClient
from ipyleaflet import Map

# First, create a tile server from local raster file
tile_client = TileClient('~/Downloads/dem.tif')

# Create ipyleaflet tile layer from that server
t = get_leaflet_tile_layer(tile_client)

# Create ipyleaflet map, add tile layer, and display
m = Map(center=tile_client.center())
m.add_layer(t)
m

tile_client.pixel(37.869365, -118.943481, units="EPSG:4326")

This feature has been implemented. See notebook example https://github.com/giswqs/leafmap/blob/master/examples/notebooks/32_local_tile.ipynb

Available in localtileserver >=0.3.14

@giswqs, I really need to add some tests to this to verify I'm grabbing the right values... Need to find a sample raster with simple data/big pixels. I will look in the GDAL testing data

I just did some testing, and there are indeed some issues with the pixel values. The same image, same lon/lon with different results with Titiler endpoint and localtileserver.
import leafmap
import localtileserver
m= leafmap.Map()
url = "https://s3.eu-central-1.amazonaws.com/floris.calkoen.open.data/tile_2523.tif"
m.add_cog_layer(url, bands=[4, 3, 2])
m

remote_url = "https://s3.eu-central-1.amazonaws.com/floris.calkoen.open.data/tile_2523.tif"
local_url = "~/Downloads/landsat.tif"
lat = 53.404415
lon = 6.872292
leafmap.cog_pixel_value(lon, lat, url)
tile_client = localtileserver.TileClient(local_url)
leafmap.local_tile_pixel_value(lon, lat, tile_client)

The values aren't widely different which gives me some hope that this may be a precision issue with either large_image/localtileserver or titiler.
I will try to add some tests in localtileserver to make sure everything is good there.

I will add that this is extensively tested in large_image and localtileserver simply wraps this functionality. https://github.com/girder/large_image/blob/9251babd4acaa0eecd37c4749f7d9eeac6379171/test/test_source_gdal.py#L148
But I'd still like to add some sort of user/visual test in localtileserver


cannot configure python module with Python 3.6.4 & PyCharm 2020.3.3

Description
Maybe the doc "Python development environment" need to be updated? I tried about 3 hours to configure python module, but the Intelligence is not working.
At the beginning I thought it was caused by an incorrect version of Python (3.6.8), maybe it was too new to RenderDoc, so I tried 3.6.4, which was told in #1838, it says "3.6.4 by default". But still not works.
I tried to use the enviroment enumerated in the documentation, I installed PyCharm 2020.3.3, but nothing different really happened. I saw the file ".failed__renderdoc" in "python_stubs" directory and content "1.147" within.
Perhaps in the latest few versions, the generated .pyd files are no longer compatible with Python 3.6.
I am a newbie in python, and I am not a native English speaker, this issue is written by google translate, looking forward to your reply : )
Steps to reproduce

Compile RenderDoc(x64) and copy "pymodules" directory.
Install PyCharm and python 64-bit executable installer
Replace "module_redeclarator.py"
Configure python module in project settings
Failed to import even if delete the "python_stubs"

Environment

RenderDoc version: 1.22 (github)
Operating System: Win 11 Pro
Graphics API: DX12
Python: 3.6.8 / 3.6.4
PyCharm: 2022.2.1 / 2020.3.3

This works correctly for me following the steps on PyCharm 2022.2.1, and it was working as well on PyCharm 2021. I cannot feasibly provide debugging support for users making mistakes using third party software like that. If you can show clear evidence there is a RenderDoc bug then I can look into it, but this seems like you have not properly configured the interpreter which is out of scope of this project.


Introduce short-lived rollover_taker::Actor

Very similar to the other ones we've done.
Things to consider:

Shall we consolidate the usage of "rollover" over "roll over" across the entire codebase? I don't think I have been able to stay consistent even in this PR :(
I've added an OrderId to the wire::MakerToTaker::ConfirmRollOver message, because the maker could be talking about more than one rollover.
The taker_cfd::Actor no longer handles the raw wire::MakerToTaker enumeration of messages :tada: After creating all these short-lived actors it only needs to handle a dedicated CurrentOrder message originating from the maker.
Error handling is worth reviewing in detail as I've messed that up in previous related PRs.

bors r+


Optimize imports using Intellij IDEA

This is a new version of #821
Imports in the project are not cleaned up, and are not consistant: this is an update just using the "optimise imports" action from IntelliJ IDEA.
If that's fine with you @langchain4j , I can do another PR adding https://github.com/jhipster/prettier-java which is the official Prettier version for Java, maintained by the JHipster project.

Closing it as it's annoying to maintain, but super easy to recreate from scratch

Prettier will do much more, here it's only the imports: that's simple and not risky


Support development lifecycle from Xcode with XCTest

Allows developers to seamlessly transition from a Xcode-base build system to a Gradle-base build system without affecting their development lifecycle.
Expected Behaviors
Gradle will generate Xcode projects allowing a developer to:

Build and run test using the action button (See A)
Build and run specific test using inline test button from the text editor
View test results from the Test navigator (See B)

Test cases

[ ] Build and execute test using xcodebuild through the CLI

@lacasseio WRT "manually testing", is there a command-line equivalent of the button presses from Xcode that we could drive via a test fixture to sanity check that the generated xcode projects are usable?

I was going to add this as a separate item of work, but I think you are right to do the extra mile now and add some xcodebuild support now.

From my point of view, a feature with no functional tests does not exist. We should really try hard to avoid stories where manual testing is the only testing we do. Otherwise, it's a spike not a feature.

You are right @adammurdoch, my mistake. I will look into having as many functional tests as possible through the CLI and xcodebuild as suggested by @big-guy.

I experimented a little bit with SikuliX and it seems we could create real acceptance test for Xcode for the features that aren't testable via xcodebuild. What's your thought about using such framework? We could automate scenario like "given a Xcode project, the user can execute all test using the test action button".

I've used Sikuli.  Maintenance was too much of a burden, IMO. I think our xcodebuild fixture get us 80-90% of what we need.  We know we're generating working xcode project files and I think it's safe to rely on complaints from users if we somehow work from the command-line but fail from the IDE.
Since using Sikuli would require macOS build agents, I'd rather just have the macOS build agents and run our xcodebuild tests there.

Sounds good, moving this in done as all item assign to this epic has been delivered.


Can't build library importing uuid

This is a description of the problem along with the variations attempted:
https://stackoverflow.com/questions/59221867/angular-build-results-in-error-cannot-call-a-namespace-v1
This is the repository containing the code:
https://github.com/fireflysemantics/slice/tree/angular-package-format/angular-package-format-workspace
The library is projects/slice .  If I try this import:
import * as v1 from "uuid/v1";

The tests run but Angular will not build the package.  The error logged is:

Error: Cannot call a namespace ('v1')

So I decided to refactor my own library to confirm to the APF ... but these compiler restrictions on software that was working fine in all demoes seem a bit excessive ...

@fireflysemantics, uuid exports a v1 from the primary entrypoint. https://github.com/kelektiv/node-uuid/blob/master/index.js
Using the below statement should fix the problem;
import { v1 } from "uuid";

With the following import import * as v1 from "uuid/v1"; v1 is a namespace  and rollup doesn't allow this to be invoked.
https://rollupjs.org/repl/?version=1.27.8&shareable=JTdCJTIybW9kdWxlcyUyMiUzQSU1QiU3QiUyMm5hbWUlMjIlM0ElMjJtYWluLmpzJTIyJTJDJTIyY29kZSUyMiUzQSUyMmltcG9ydCUyMColMjBhcyUyMHYxJTIwZnJvbSUyMCU1QyUyMnV1aWQlMkZ2MSU1QyUyMiUzQiU1Q252MSgpJTIyJTJDJTIyaXNFbnRyeSUyMiUzQXRydWUlN0QlNUQlMkMlMjJvcHRpb25zJTIyJTNBJTdCJTIyZm9ybWF0JTIyJTNBJTIyY2pzJTIyJTJDJTIybmFtZSUyMiUzQSUyMm15QnVuZGxlJTIyJTJDJTIyYW1kJTIyJTNBJTdCJTIyaWQlMjIlM0ElMjIlMjIlN0QlMkMlMjJnbG9iYWxzJTIyJTNBJTdCJTdEJTdEJTJDJTIyZXhhbXBsZSUyMiUzQW51bGwlN0Q=


Breaking backwards compatible removal of #define SHA_SIZE

Checklist

[x] Checked the issue tracker for similar issues to ensure this is not a duplicate
[ ] Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
[ ] Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?
always
Expected behavior
I expected it to be able to compile esp-matter project without error.
Compiling using

esp-idf v5.2.1 commit a322e6bdad4b6675d4597fb2722eea2851ba88cb
esp-matter commit c5d583525116bea8ce97e3567bf6f4e18985a960

Actual behavior (suspected bug)
Instead it trigger 'SHA_SIZE' undeclared error
Error logs or terminal output
managed_components/espressif__esp_insights/src/esp_insights_cbor_encoder.c:176:22: error: 'SHA_SIZE' undeclared here (not in a function)
  176 |     char sha_sum[2 * SHA_SIZE + 1]

Steps to reproduce the behavior

remove managed_component folder
remove dependencies.lock
idf.py fullclean
idf.py set-target esp32s3
idf.py build

Project release version
v1.2.1
System architecture
Intel/AMD 64-bit (modern PC, older Mac)
Operating system
Linux
Operating system version
Ubuntu 22.04
Shell
Bash
Additional context
No response

@vikramdattu , I've increase the version for esp_insights in esp-matter/connectedhomeip/connectedhomeip/config/esp32/components/chip/idf_component.yml to 1.2.1 and it solve the problem.
Will this be reflected on the esp-matter repo in the near future?

@SCCatADT , the fix by pinning the version to 1.0.1 for espressif/esp_diag_data_store is available on latest esp-matter here.


Add new Lint/SafeNavigationChain cop

Safe navigation operator returns nil if the receiver is nil.
So if you chain an ordinary method call after safe navigation operator, it raises NoMethodError.
We should use safe navigation operator after safe navigation operator.
This cop checks the problem.
For example
x = nil
x&.foo.bar   # => NoMethodError: undefined method `bar' for nil:NilClass
x&.foo&.bar  # => nil

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

Another great contribution! Thanks! 👍 ❤ 🚀


Training suddenly freezes

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): unknown 2.0.0 (see below)

tensorboard=2.0.0=pyhb38c66f_1
tensorflow=2.0.0=gpu_py37h57d29ca_0
tensorflow-base=2.0.0=gpu_py37h390e234_0
tensorflow-estimator=2.0.0=pyh2649769_0
tensorflow-gpu=2.0.0=h0d30ee6_0
tensorflow-probability=0.8.0=py_0

Python version: Python 3.7.6 (Anaconda)
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: cudatoolkit=10.0.130=0 / cudnn=7.6.4=cuda10.0_0
GPU model and memory: Nvidia GeForce RTX 2070 8GB

Describe the current behavior
Training a CNN using tf.keras.Model.fit() and tensorflow's data pipeline with tfrecord files randomly seems to freeze/stop/hang. Whenever this happens, the console process stays open but the CPU/GPU will return to 0% utilization. Using verbose=1 as well as tensorboard also shows that no progress is being made anymore.
Waiting for a while does not help. However, if I restart the training without rebooting my PC, the hang is much more likely to occur again.
Looking into Process explorer, I can see that there is only one really active thread:

A Callstack for the thread is attached below. The upper few frames (nvcuda.dll!cuProfilerStop) change when refreshing but the rest of the frame stays constant.
Describe the expected behavior
The training should continue normally.
Code to reproduce the issue
Since I was not able to reproduce the problem reliably, I have no idea which part of my code might actually be important, The data pipeline uses dataset.map() with num_parallel_calls = tf.data.experimental.AUTOTUNE for multiprocessing and contains two tf.np_function()s (after which I have to use tf.ensure_shape to recover the correct shape for the data).
Other info / logs
nvcuda.dll!cuProfilerStop+0x226617
nvcuda.dll!cuProfilerStop+0x17243c
nvcuda.dll+0x4bbbe
nvcuda.dll+0x10c29d
nvcuda.dll!cuProfilerStop+0x5cc42
nvcuda.dll!cuProfilerStop+0x5da20
nvcuda.dll+0x10bbf0
nvcuda.dll+0x10be3c
nvcuda.dll+0xeac0
nvcuda.dll!cuCtxSynchronize+0x1c2
_pywrap_tensorflow_internal.pyd!std::unique_ptr<tensorflow::Status::State,std::default_delete<tensorflow::Status::State> >::~unique_ptr<tensorflow::Status::State,std::default_delete<tensorflow::Status::State> >+0x10b4f
_pywrap_tensorflow_internal.pyd!tensorflow::Env::NowSeconds+0xd16
_pywrap_tensorflow_internal.pyd!tensorflow::AllocationRecord::Clear+0x550c
_pywrap_tensorflow_internal.pyd!google::protobuf::RepeatedPtrField<tensorflow::InterconnectLink>::Add+0x8f0c
_pywrap_tensorflow_internal.pyd!std::vector<tensorflow::DtypeAndPartialTensorShape,std::allocator<tensorflow::DtypeAndPartialTensorShape> >::operator=+0x623
_pywrap_tensorflow_internal.pyd!TFE_TensorHandleResolve+0x227
_pywrap_tensorflow_internal.pyd!tensorflow::DataTypeSet::Contains+0x2350
_pywrap_tensorflow_internal.pyd!std::vector<tensorflow::monitoring::Point::Label,std::allocator<tensorflow::monitoring::Point::Label> >::reserve+0x85a
python37.dll!PyMethodDef_RawFastCallKeywords+0x387
python37.dll!PyMethodDef_RawFastCallKeywords+0xa5c
python37.dll!PyEval_EvalFrameDefault+0x403
python37.dll!PyFunction_FastCallDict+0xdd
python37.dll!PyObject_FastCall_Prepend+0x6c
python37.dll!PySet_Contains+0x50d
python37.dll!PyErr_NoMemory+0x24eaf
python37.dll!PyEval_SliceIndex+0x42
python37.dll!PySlice_Unpack+0x9d
_multiarray_umath.cp37-win_amd64.pyd+0xc117e
_multiarray_umath.cp37-win_amd64.pyd+0xc0093
python37.dll!PyEval_EvalFrameDefault+0x7e4
python37.dll!PyEval_EvalCodeWithName+0x1a6
python37.dll!PyFunction_FastCallDict+0x1ba
python37.dll!PySlice_New+0x23d
python37.dll!PyEval_EvalFrameDefault+0x1174
python37.dll!PyEval_EvalCodeWithName+0x1a6
python37.dll!PyFunction_FastCallDict+0x1ba
python37.dll!PyObject_Call_Prepend+0x6c
python37.dll!PyType_GetDocFromInternalDoc+0x22d
python37.dll!PyObject_Call+0x75
_pywrap_tensorflow_internal.pyd!std::default_delete<tensorflow::kernel_factory::OpKernelRegistrar::PtrOpKernelFactory>::operator()+0x97d
_pywrap_tensorflow_internal.pyd!std::default_delete<tensorflow::kernel_factory::OpKernelRegistrar::PtrOpKernelFactory>::operator()+0x420
_pywrap_tensorflow_internal.pyd!tensorflow::NodeDef::mutable_experimental_debug_info+0xef56
_pywrap_tensorflow_internal.pyd!tensorflow::NodeDef::mutable_experimental_debug_info+0x11f78
_pywrap_tensorflow_internal.pyd!tensorflow::data::DatasetBaseIterator::RecordElement+0x6f
_pywrap_tensorflow_internal.pyd!Eigen::ThreadPoolTempl<tensorflow::thread::EigenEnvironment>::WorkerLoop+0x3f6
_pywrap_tensorflow_internal.pyd!Eigen::ThreadPoolTempl<tensorflow::thread::EigenEnvironment>::WorkerLoop+0x701
_pywrap_tensorflow_internal.pyd!tensorflow::WindowsFileSystem::TranslateName+0x255
_pywrap_tensorflow_internal.pyd!tensorflow::SavedAsset::GetCachedSize+0x2c19
ucrtbase.dll!beginthreadex+0x142
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

@muellesi, Could you provide the standalone code to replicate the issue.

@muellesi, Is this still an issue?

Unfortunately yes, but it only happens very sporadically and I was not yet able to reproduce the problem reliably. Therefore I also don't have any piece of standalone code that reliably reproduces the issue. However, I had the problem on three different PCs now.

@muellesi, Any update on code snippet?

same issue!

I met this bug again!
The training is suddenly stop, no errors, no exceptions, and no logs.

The training step is stop at 783.
I use the GPU7 inside a docker container. Here is the outputs of nvidia-smi:

The process is just exist, no any informations.

@luozhouyang : Do you also use the tensorflow dataset pipline? And if so, do you also use np_function? Maybe we can find  a common factor between our cases and extract a reproduction snippet.

Yes, I construct a tf.data.TFRecordDataset from a list of .tfrecord files.
I found that, if I set dataset = dataset.shuffle(buffer_size=2000000) then the training is more likely stop. But if I set the buffer_size=1500000, the training goes well. The usage of memory in both settings is about 16G/32G, so it's not a OOM exception.

@muellesi, Any update on reproducible code snippet? Thanks

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!

I'm having a similar issue. I am training a model with a fairly complex tf.data.datset pipeline with one tf.np_function. I use a map function that takes a batch and modifies it according to the other elements in the batch. The bigger the batch size, the easier it is to send the process to sleep at some random time. But even running the same script twice, it might have different outcomes. I'm using tf2.2 in a linux machine with 4 processors and 32GB of ram. When the process halts the memory usage is not too high ~20%

I have the same issue with TF 2.3.2 on Windows 10 with classic keras CNN models and model.fit.
The training freeze/hang at a random batch inside an epoch. I need to restart my training over and over gain starting with latest checkpoint saved.  Sometime N epochs complete and it hangs at the N+1 epochs.

I found this which might be useful https://github.com/tensorflow/tensorflow/issues/36072#issuecomment-664672783

I have same issue with latest Tensorflow on WSL2 (Ubuntu 20). Training randomly stucks around 10-15 epoch, with 0 resources consumption after stucking.


shim: remove unused variable

Fix the compilation error from gcc:
shim.c: In function ‘handle_image’:
shim.c:1121:15: error: unused variable ‘size’ [-Werror=unused-variable]
unsigned int size;
^~~~
Signed-off-by: Gary Lin<EMAIL_ADDRESS>

Thanks, pushed to master.


Improve validation of hex code in OmeroChannel

Sometimes, users enter a hex code with the # (e.g. #000000) instead of just the six numbers/letters as the docstring says (000000). This then leads to issues when opening the image in napari.
We should validate this better, if possible in 2 places:

During runtime of the task, we should check that the color is a valid six-letter string that actually maps to a color (i.e. here, instead of just checking for str: https://github.com/fractal-analytics-platform/fractal-tasks-core/blob/c7c576cef86410ac20f50707daa4f748574e924c/fractal_tasks_core/lib_channels.py#L76C6-L76C6).
In the web interface, we should not allow users to save if they enter anything different than 6 numbers/letters => @tcompa can we do this with our schemas? Best would be to only allow number & letters, not #. But also just limiting it to 6 characters would be useful.

We certainly want to get 1. done well. But let's not invest too much on the web validation part of this, because the long-term goal here would be to expose a color picker that then auto-fills the hex code :)
cc @al-mcintyre

Given that the longer-term solution should be to abstract this away with a color picker, I'd say we're fine with option A and a relevant error if a user provided something bad.
That would mena: the web interface is not checking for a correct hex string, but has a helper info text saying it's a hex color code of 6 characters, no #. If the user provides something else, the task fails while starting because the pydantic input validation fails).
Also, can we limit string.ascii_letters to only a-f & A-F?
If that expectation is correct, I'd be happy with A for the moment


[Bug Report] Tree component item loses checkmark and node-key is change after drag&drop

Element UI version
2.4.0
OS/Browsers version
win10-64/Chrome-68.0.3440.84
Vue version
2.5.16
Reproduction Link
https://jsfiddle.net/L5gm34jr/12/
Steps to reproduce
1、First check one item,
2、Drag & drop it to a different position.
What is Expected?
1、The dragged item should stay checked state.
2、The node-key of the node-drop event parameter draggingNode not change.
What is actually happening?
1、The dragged item losed checked state.
2、The node-key of the node-drop event parameter draggingNode has changed that can't reset the checked state.

Duplicate of #11927


Error running command in powershell

Describe the bug

Changing single quotes for doubles in the script works

To Reproduce
Steps to reproduce the behavior:

npm run prettier

Desktop (please complete the following information):

OS: Windows 10
Node Version: 8.12.0
Angular & Angular/CLI Version: 7.0.3 & 7.0.4

PD: Thanks for amazing tool ❤

Thank you for reporting and debugging :) If you can test out then latest version (2.0.1) for the fix that would be very helpful. I don't have a Windows machine to verify with. Thanks!


docs(CONTRIBUTING.md): fix error description (e2e command)

Summary
When I read  CONTRIBUTING.md, I found the e2e command has some error
In before CONTRIBUTING.md

In fact, the current command to run e2e is

Related Links
None!

 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.


Expand census coverage: make this a fixture instead of a simple test

Interop tests don't seem happy, albeit seemingly unrelated:
PHP Catchable fatal error:  Argument 2 passed to Grpc\BaseStub::_clientStreamRequest() must be callable, string given, called in /var/local/git/grpc/src/php/tests/interop/test.php on line 35 and defined in /var/local/git/grpc/src/php/lib/Grpc/BaseStub.php on line 255

I don't think the interop thing is related


Dev docusaurus

Description

Fix #XXX

Test

To test this pull request, you can run the following commands:

Additional Information
Tradeoff

Potential improvement

Thank you! It looks beautiful and well organized. I have the same couple of issues @raulcabello points to. I'm also running it through yarn install and yarn start.
I went through all the pages and I found some small issues, not sure how you want them to be reported.

The issue with the mutating bit is because I re-added it

I understand that we cannot do so when YAML files are embedded in a kubectl apply -f - command, but that's fine, I only mean in this case, where the YAML file appears alone.

That falls on me, I convinced José to change all the markdown blocks in that page to  ```console, and indeed some of them could be  ```yaml, including the ones that start with kubectl apply -f. It would look better.
See: https://github.com/kubewarden/docs/blob/main/src/psp-migration.md?plain=1#L50


Error when spellchecking repositories with lots of files

On Bazel:
Getting a list of files in the working tree...
Error: RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded

https://stackoverflow.com/questions/23429499/stdout-buffer-issue-using-node-child-process


No link creation and impossible to click on

When I use the bot, it is impossible to click on the invitation link, and it names the server as "deprecated", see attachment.

which discord js version are you using?

You have to use the verison specified in the package file ->  "discord.js": "^12.5.1",
with newer versions it wont work since the library changed

Maybe I'm a noob, but I can't install the package or update it on my host, or locally.

try
npm view discord.js version
you can install a specific verison of an package with:
npm i<EMAIL_ADDRESS>


Add Merkle Signature option

https://en.wikipedia.org/wiki/Merkle_signature_scheme
Merkle signatures can be quantum resistant, so adding these to Iroha would be beneficial.

@takemiyamakoto I'm willing to take up this task.
Could you please tell me more about this issue( like where to add MSS)?

Great! It should be implemented here: https://github.com/hyperledger/iroha/tree/develop/libs/crypto

Is this still relevant issue?

Thanks @Warchant for the reminder.
I think this feature is still pending, I'll start a PR for this as suggested by @takemiyamakoto


fix: commands and jenkins template

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: Disable mobile-only media query

Description
Hey there, sorry for the delay with delivering this feature, I had tons of work lately.
I thought it would be nice to implement it for the /map page, as it has pretty much the same layout and style for both mobile & desktop. Let me know if you approve it, then I'll incorporate this feature as well.
screenshots
Not expanded:

Expanded:

Thanks for the contribution! Hope will continue help us with the project!


Cleanup Kustomize

3 problems with kustomize:

code is scattered across 2 dirs, should be in one only: see below
code was just a test for me to learn, and 2 weeks after is destined to become the #1 repo on github :) I need some cleanup and make sure it all works.
Does it make sense to use kustomize at all? I mean, the ONLY use which is REALLY important is: canary 9 pods, prod 1 pod. And a common selector for canary and prod. Coudl I just create 4 copies of k8s manifests to increase readability?

I'd love a kustomize expert to help me on this.
scattered code (1)
ricc@ricc:~/git/clouddeploy-platinum-path$ 🐼 find . -name components
./components
./apps/components

Alex, I can of coruse merge the two components folder, I just you to tell me:

Q1. Where should I put the components folder: which to keep and which to kill?
Q3. Does it make sense to have kustomize at all for my use case? Think of the N users who'll read the blog. Do they need that extra complexity?

the 'betterification' fo code can be done at later stage :)


Provide Dashboard Templates

Users usually don't use the Discord competitions. Provide a set of templates for the Dashboard with different widgets.

Solved with 2.2.0


Implement get_columns_in_query macro to fix snapshots with check_cols='all'

Fix for snapshots failing if check_cols='all' is set in config, due to default implementation of get_columns_in_query not being valid MS SQL.

Thank you for this! I didn't know that.


Regression when running DDL (CREATE SCHEMA or CREATE VIEW) in PreparedStatement

The following code:
try (Connection c = new com.microsoft.sqlserver.jdbc.SQLServerDriver().connect(url, properties)) {
    try (PreparedStatement s1 = c.prepareStatement("create schema x");
         PreparedStatement s2 = c.prepareStatement("drop schema x")) {
        System.out.println(s1.execute());
        System.out.println(s2.execute());
    }
}

... works with:
<dependency>
    <groupId>com.microsoft.sqlserver</groupId>
    <artifactId>mssql-jdbc</artifactId>
    <version>6.1.0.jre8</version>
</dependency>

... but it no longer works with:
    <version>6.2.0.jre8</version>

The error I'm getting is this:
com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near the keyword 'schema'.
	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1547)
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:528)
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:461)
	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2689)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:224)
	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:204)
	at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.execute(SQLServerPreparedStatement.java:445)
	at SQLServer.main(SQLServer.java:69)

A workaround is to resort to static statements. The same is true for CREATE VIEW statements:
// Works on both versions
try (Statement s1 = c.createStatement();
     Statement s2 = c.createStatement()) {
    System.out.println(s1.execute("create view x as select 1 a"));
    System.out.println(s2.execute("drop view x"));
}

// Works only on version 6.1.0
try (PreparedStatement s1 = c.prepareStatement("create view x as select 1 a");
     PreparedStatement s2 = c.prepareStatement("drop view x")) {
    System.out.println(s1.execute());
    System.out.println(s2.execute());
}

I think that's quite a significant regression. Other DDL statements might be affected as well.

The SQL Server Profiler shows:
JDBC driver version 6.1.0:
declare @p1 int
set @p1=1
exec sp_prepexec @p1 output,NULL,N'create schema x'
select @p1

JDBC driver version 6.2.0:
exec sp_executesql N'create schema x',NULL

Possibly related: https://github.com/Microsoft/mssql-jdbc/issues/166. See also comment on Stack Overflow by @gordthompson: https://stackoverflow.com/q/44950970/521799

@lukaseder Thanks for raising this issue. We are investigating this.
@TobiasSQL Would appreciate your thoughts on this, as well.

Additional information: I saw the same results from SQL Profiler that @lukaseder reported. Subsequent fooling around with sqlcmd yielded
1> SELECT LEFT(@@VERSION, 67);
2> go

-------------------------------------------------------------------
Microsoft SQL Server 2014 (SP2-GDR) (KB3194714) - 12.0.5203.0 (X64)

(1 rows affected)
1> EXEC sp_executesql N'create schema x', NULL;
2> go
Msg 214, Level 16, State 3, Server GORD-HP\SQLEXPRESS, Procedure sp_executesql, Line 1
Procedure expects parameter '@params' of type 'ntext/nchar/nvarchar'.
1> EXEC sp_executesql N'create schema x', N'';
2> go
Msg 156, Level 15, State 1, Server GORD-HP\SQLEXPRESS, Line 1
Incorrect syntax near the keyword 'schema'.
1> EXEC sp_executesql N'create schema x';
2> go
1>

That is, simply omitting the trailing NULL parameter seems to avoid the problem.

Correctamundo, this is a bug. @v-afrafi I suggested a change in your fix.

I was hit by this bug, probably the version 6.2 should be withdrawn and marked as flawed.

@jorsol @lukaseder @gordthompson Thank you for reporting this issue. We are in the process of releasing a hotfix soon, so in the meantime, we would suggest using the last driver version.

Hi,
as I see here https://github.com/Microsoft/mssql-jdbc/releases/tag/v6.2.1, v6.2.1 reverts some metadata caching commits previously done with #377.
Is the metadata caching planned to be released/reintroduced after some more testing?

Hi @mimmoz81 Thank you for your feedback regarding improvement of performance.
The feature was removed due to some regressions. We will be adding the feature to our next preview releases once we conduct more comprehensive tests. Please stay tuned for the updates!

Adding to what @v-afrafi said, the issues found post release showed that even though we passed all of our regression tests we still have issues (I think mainly related to batch execution) which we need to make sure to get better test coverage for.
The feature is available in the dev branch and you can for sure use this if it works for you given the caveat mentioned above.

fixed by pr #388 . Thank you so much @lukaseder for creating this issue.

Thank YOU for fixing it so quickly :)


FIx for #215

This PR addresses multiple issues.

Fixes #215 by deprecating fix_all and adding fix_local and fix_full functions. Currently fix_all points to fix_local, but this behavior may be changed in the future by pointing it to fix_full.
Introduces a preliminary scaffolding for serializing Optimizable objects into JSON/YAML objects. Tested for individual Optimizable objects without any dependencies
Source distribution now contains the external packages also.
Modules with graph_ prefix are deprecated and are supplanted with corresponding modules without the graph_ prefix. They will be removed completely in the future.
Due to 4, this PR needs to be merged at the earliest to minimize merge conflicts when someone updates code in those modules.

Git is not playing nice when a file is moved and then a new file with the same name is created.
Changes for 1. and 2. are lost in optimizable.py, which shows up as a new file despite my best efforts.
For 2, look at as_dict and from_dict methods in Optimizable and a few subclasses such as objectives.functions.Adder.

Thanks, Matt for quickly going through the changes.

fix_all() and unfix_all() are still used in many unit tests and in some of the examples.
Converted them to fix_local and unfix_local.

The docs/source/optimizable.rst docs page still talks about fix_all() and unfix_all() rather than the new local/full functions.
Fixed this.

I see a few remaining graph_ prefixes in docs/source/mpi.rst, src/_core/optimizable.py, and examples/README.md
Removed references to graph_ prefixes

In tests/core there is both test_optimizable and test_graph_optimizable.
In tests/objectives there is both test_least_squares and test_graph_least_squares
In tests/solve there is both test_mpi and test_graph_mpi, and both test_least_squares and test_graph_least_squares
This is by design. The test_graph_*.py still import modules with graph_ prefix. I want to make sure the existing code does not break down.

There are several orthogonal changes going on in this PR. In the future it would be nice to have these kinds of changes as separate PRs. Then we could e.g. resolve #215 without having to simultaneously merge the incomplete serialization bits.
Yes. I agree. I made the changes in separate branches and then merged them due to the anticipated merge conflicts. It is a pain point when files are renamed.  Alternatively, I should have sat on 4.

Working implementation for serializing Optimizable objects with dependencies on other Optimizable objects.


Missing Storm API: IMetricsConsumer

One of the teams at Spotify uses a custom Storm metrics consumer that implements backtype.storm.metric.api.IMetricsConsumer. This interface is missing from the Heron API.
The ask is to add support for this API to avoid code changes.

#1445

Resolved.

That was super fast. Thank you!


The modal closes unexpectedly

In the ImportSecretKey.tsx file there is a modal for entering the secret key for recovering the wallet.
On the submit button there are some zones where if you click the modal closes unexpectedly
(effectively clicking on the label instead of the button element)

Solved in Sveltekit


Re: No such file or directory @ rb_sysopen - tmp/rspec_guard_result with a syntax error

re: https://github.com/guard/guard-rspec/issues/362
Hello, I've met the problem again and prepared debug info
$ beg -d
17:12:51 - DEBUG - Command execution: hash stty
17:12:51 - DEBUG - Guard starts all plugins
17:12:51 - DEBUG - Hook :start_begin executed for Guard::Bundler
17:12:52 - INFO - Bundle already up-to-date
17:12:52 - DEBUG - Hook :start_end executed for Guard::Bundler
17:12:52 - DEBUG - Hook :start_begin executed for Guard::LiveReload
17:12:52 - INFO - LiveReload is waiting for a browser to connect.
17:12:52 - DEBUG - Hook :start_end executed for Guard::LiveReload
17:12:52 - DEBUG - Hook :start_begin executed for Guard::RSpec
17:12:52 - INFO - Guard::RSpec is running
17:12:52 - DEBUG - Hook :start_end executed for Guard::RSpec
17:12:52 - DEBUG - Hook :start_begin executed for Guard::Spork
17:12:52 - DEBUG - Killing Spork servers with PID:
17:12:52 - INFO - Starting Spork for RSpec
17:12:52 - DEBUG - guard-spork command execution: ["exec", "spork", "-p", "8989"]
Using RSpec, Rails
Preloading Rails environment
      ** Notice: The native BSON extension was not loaded. **

      For optimal performance, use of the BSON extension is recommended.

      To enable the extension make sure ENV['BSON_EXT_DISABLED'] is not set
      and run the following command:

        gem install bson_ext

      If you continue to receive this message after installing, make sure that
      the bson_ext gem is in your load path.

17:13:22 - ERROR - Could not start Spork server for RSpec after 30 seconds. I will continue waiting for a further 60 seconds.
Loading Spork.prefork block...
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/actionpack-3.2.22/lib/action_dispatch/http/mime_type.rb:102: warning: already initialized constant PDF
DEPRECATED: Passing a block to Capybara::server is deprecated, please use Capybara::register_server instead
Spork is ready and listening on 8989!
17:13:44 - INFO - Spork server for RSpec eventually started after 52 seconds. Consider adjusting your :wait option beyond this time.
17:13:44 - DEBUG - Hook :start_end executed for Guard::Spork
17:13:45 - INFO - Guard is now watching at '/home/dima/devel/mice/katalysator'
17:13:45 - DEBUG - Start interactor
17:14:35 - DEBUG - Interactor was stopped or killed
17:14:35 - DEBUG - Hook :run_on_modifications_begin executed for Guard::RSpec
17:14:35 - INFO - Running: spec spec/support/negotiations/contract_arbitrator_spec.rb
17:14:35 - DEBUG - Guard::RSpec: results file: /home/dima/devel/mice/katalysator/tmp/rspec_guard_result
Running tests with args ["--color", "--failure-exit-code", "2", "--format", "progress", "--format", "Guard::RSpecFormatter", "--require"<EMAIL_ADDRESS>"spec", "spec/support/negotiations/contract_arbitrator_spec.rb"]...
Exception encountered: #<SyntaxError: /home/dima/devel/mice/katalysator/spec/support/negotiations/contract_arbitrator_spec.rb:29: syntax error, unexpected '{', expecting keyword_end
    it 'should return value from Arbitrator' { should == 12 }
                                              ^
/home/dima/devel/mice/katalysator/spec/support/negotiations/contract_arbitrator_spec.rb:29: syntax error, unexpected '}', expecting keyword_end
/home/dima/devel/mice/katalysator/spec/support/negotiations/contract_arbitrator_spec.rb:35: syntax error, unexpected $end, expecting keyword_end>
backtrace:
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:245:in `load'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:245:in `block in load'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:236:in `load_dependency'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:245:in `load'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1361:in `block in load_spec_files'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1359:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rspec-core-3.4.4/lib/rspec/core/configuration.rb:1359:in `load_spec_files'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:106:in `setup'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rspec-core-3.4.4/lib/rspec/core/runner.rb:92:in `run'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/test_framework/rspec.rb:12:in `run_tests'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/run_strategy/forking.rb:13:in `block in run'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/forker.rb:21:in `block in initialize'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/forker.rb:18:in `fork'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/forker.rb:18:in `initialize'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/run_strategy/forking.rb:9:in `new'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/run_strategy/forking.rb:9:in `run'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/bundler/gems/spork-224df492657e/lib/spork/server.rb:49:in `run'
/usr/local/rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/drb/drb.rb:1548:in `perform_without_block'
/usr/local/rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/drb/drb.rb:1508:in `perform'
/usr/local/rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/drb/drb.rb:1586:in `block (2 levels) in main_loop'
/usr/local/rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/drb/drb.rb:1582:in `loop'
/usr/local/rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/drb/drb.rb:1582:in `block in main_loop'
Done.

17:14:57 - DEBUG - Guard::RSpec: RSpec command bundle exec rspec -c --drb -f progress -r<EMAIL_ADDRESS>-f Guard::RSpecFormatter --failure-exit-code 2  spec spec/support/negotiations/contract_arbitrator_spec.rb exited with: 0
17:14:57 - ERROR - Guard::RSpec cannot open results file: "/home/dima/devel/mice/katalysator/tmp/rspec_guard_result". This is likely a bugso please report this at http://github.com/guard/guard-rspec/issues/new along with as muchinformation as possible to reproduce this issue.
17:14:57 - ERROR - Guard::RSpec failed to achieve its <run_on_modifications>, exception was:
> [#] Errno::ENOENT: No such file or directory - /home/dima/devel/mice/katalysator/tmp/rspec_guard_result
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/results.rb:11:in `readlines'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/results.rb:11:in `initialize'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/rspec_process.rb:57:in `new'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/rspec_process.rb:57:in `_read_results'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/rspec_process.rb:18:in `initialize'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/runner.rb:65:in `new'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/runner.rb:65:in `_really_run'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/runner.rb:54:in `_run'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec/runner.rb:38:in `run'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec.rb:42:in `block in run_on_modifications'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec.rb:48:in `_throw_if_failed'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-rspec-4.7.3/lib/guard/rspec.rb:42:in `run_on_modifications'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:82:in `block in _supervise'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:79:in `catch'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:79:in `_supervise'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:61:in `block (3 levels) in run_on_changes'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:56:in `each'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:56:in `block (2 levels) in run_on_changes'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:119:in `block (2 levels) in _run_group_plugins'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:117:in `each'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:117:in `block in _run_group_plugins'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:116:in `catch'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:116:in `_run_group_plugins'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:54:in `block in run_on_changes'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:53:in `each'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/runner.rb:53:in `run_on_changes'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/internals/queue.rb:23:in `process'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/commander.rb:43:in `start'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/cli/environments/valid.rb:16:in `start_guard'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/cli.rb:122:in `start'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/aruba_adapter.rb:32:in `execute'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/aruba_adapter.rb:19:in `execute!'
> [#] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/bin/_guard-core:11:in `<main>'
17:14:57 - INFO - Guard::RSpec has just been fired
17:14:57 - DEBUG - Start interactor

The next save of the file does not perform the run just returning
17:16:06 - DEBUG - Interactor was stopped or killed
17:16:06 - DEBUG - Hook :run_on_additions_begin executed for Guard::Bundler
17:16:06 - INFO - Bundle already up-to-date
17:16:06 - DEBUG - Hook :run_on_additions_end executed for Guard::Bundler
17:16:06 - DEBUG - Start interactor

When leaving guard via ^D I received
17:30:43 - DEBUG - Interactor was stopped or killed
17:30:43 - DEBUG - Guard stops all plugins
17:30:43 - DEBUG - Hook :stop_begin executed for Guard::LiveReload
17:30:43 - DEBUG - Hook :stop_end executed for Guard::LiveReload
17:30:43 - DEBUG - Hook :stop_begin executed for Guard::Spork
17:30:43 - DEBUG - Killing Spork servers with PID: 22011
E, [2016-11-08T17:30:43.533388 #21984] ERROR -- : run() in thread failed: undefined method `callback!' for nil:NilClass:\n /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/event.rb:128:in `callback!'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:238:in `block in process'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:238:in `each'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:238:in `process'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:221:in `run'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/adapter/linux.rb:38:in `_run'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/adapter/base.rb:78:in `block in start'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/internals/thread_pool.rb:6:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/internals/thread_pool.rb:6:in `block in add'\n\ncalled from:\n /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/backend.rb:26:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/listener.rb:67:in `block in <class:Listener>'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/fsm.rb:120:in `instance_eval'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/fsm.rb:120:in `call'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/fsm.rb:91:in `transition_with_callbacks!'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/fsm.rb:57:in `transition'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/listener.rb:90:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/commander.rb:35:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/cli/environments/valid.rb:16:in `start_guard'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/cli.rb:122:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/aruba_adapter.rb:32:in `execute'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/lib/guard/aruba_adapter.rb:19:in `execute!'
/usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/guard-2.13.0/bin/_guard-core:11:in `<main>'
17:30:43 - ERROR - Guard::Spork failed to achieve its <stop>, exception was:
> [#0D8F44B3775F] NoMethodError: undefined method `callback!' for nil:NilClass
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/event.rb:128:in `callback!'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:238:in `block in process'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:238:in `each'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:238:in `process'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/rb-inotify-0.9.5/lib/rb-inotify/notifier.rb:221:in `run'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/adapter/linux.rb:38:in `_run'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/adapter/base.rb:78:in `block in start'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/internals/thread_pool.rb:6:in `call'
> [#0D8F44B3775F] /usr/local/rvm/gems/ruby-1.9.3-p551@mp_katalysator/gems/listen-3.0.5/lib/listen/internals/thread_pool.rb:6:in `block in add'
17:30:43 - INFO - Guard::Spork has just been fired
17:30:43 - INFO - Bye bye...

Hey, I am having almost the same issue.

Unfortunately none of the solutions provided in the related issues helped me.
ruby 2.3.3p222
guard (2.14.1)
guard-rspec (4.7.3)

Interesting is that it worked with this combo:
ruby 2.1.9p490
guard (2.13.0)
guard-rspec (4.6.4)

And also I found out that this combo also works:
ruby 2.3.3p222
guard (2.14.1)
guard-rspec (4.6.4)

That's why I conclude that the bug is in guard-rspec between 4.6.4 and 4.7.3

guard-rspec's handling of the results file should be refactored and made more robust using mktemp().  There's a ton of issues going back a few years all related to being unable to open the results file.


Server Status not updating

I'm working on a discord bot but the status of the server doesn't update. If the server is online when i start the script, the server status stays online even if the server is already offline for 10 min. Is there a function to update the status?

View #39 and #22.


Add additional colors to syntax-variables

This moves additional color variables over to syntax-variables.less to help clean up the CSS a bit more.

Not sure how things have changed since this PR but pinging @simurai for thoughts :bulb:

I think it's a good idea, but it seems outdated.
There are now a few official variables that get used in `index.less: https://github.com/atom/atom-light-syntax/blob/master/styles/syntax-variables.less#L32-L44
The rest could still be changed to variables too, but this PR would need to be updated or might be easier to make a new one?

My suggestion would be to move the new variables into a new file

That's a good suggestion. That way when you look at syntax-variables.less, you can be sure to use everything in there. I should change that with the other themes too.

This seems too outdated, let's close it. 😞


Is there any way to disable auto scrolling?

Thanks for the great program.
When I open the dropdown again after selecting something, it auto scrolls the selected item to the top. Is there a way to turn off the auto scrolling? The state showSelectedOptionsFirst = false.

@daeyoonlee this is the default behaviour when showSelectedOptionsFirst is false.
I will add a new property to disable auto scroll in the future release.

@daeyoonlee set focusSelectedOptionOnOpen: false property.
This feature is available in the release v1.0.37

It works fine. thank you!


Compile Linux arm (Raspberry) cannot find -lX11

Robotgo version (or commit ref): #8ba73388617a008c9e9e2e28d69f3549e15b750b
Go version: 1.18
Gcc version: g++ (Ubuntu 11.2.0-7ubuntu2) 11.2.0
Operating system and bit: Ubuntu 21.10 64bit

git clone https://github.com/go-vgo/robotgo.git
cd robotgo
env GOOS=linux GOARCH=arm CGO_ENABLED=1 CC=arm-linux-gnueabihf-gcc go build .

Result:
# github.com/go-vgo/robotgo
/usr/lib/gcc-cross/arm-linux-gnueabihf/11/../../../../arm-linux-gnueabihf/bin/ld: cannot find -lX11
/usr/lib/gcc-cross/arm-linux-gnueabihf/11/../../../../arm-linux-gnueabihf/bin/ld: cannot find -lXtst
collect2: error: ld returned 1 exit status

Are you install linux X11 library?
https://github.com/go-vgo/robotgo#requirements.

I can compile for Linux amd64 and Windows 64 so I think so
(Doing sudo apt install xorg libxtst-dev response everything is up to date)

Any update?


Remove \r from strings before parsing

I guess this is the correct thing to do here, seems like jdtls also separates (not terminates) lines with \r\n (at least).
(also means we can't re-use the function for reading an entire file from loaders.util, where line-terminators are assumed).

merged via cherry-pick.


Refactor role security, support it for ext. auth flow

Refactors role security as it was implemented on auth-clients into more reusable function.
Implement same/similar role-security structure on external auth providers and allow permitted/prohibited/forbidden roles to be applied when user authenticates via IdP.

Codecov Report

Merging #287 (b7e02a7) into 2021.9.x (cdb60c9) will increase coverage by 0.05%.
The diff coverage is 44.83%.

@@             Coverage Diff              @@
##           2021.9.x     #287      +/-   ##
============================================
+ Coverage     42.93%   42.98%   +0.05%
============================================
  Files           773      777       +4
  Lines         69892    70594     +702
============================================
+ Hits          30010    30347     +337
- Misses        35702    36049     +347
- Partials       4180     4198      +18

Impacted Files
Coverage Δ

compose/rest/namespace.go
44.93% <0.00%> (-1.47%)
:arrow_down:

compose/rest/request/namespace.go
11.73% <0.00%> (-1.18%)
:arrow_down:

compose/service/locale.gen.go
6.20% <0.00%> (-18.80%)
:arrow_down:

compose/service/namespace.go
35.62% <0.00%> (-6.17%)
:arrow_down:

compose/service/namespace_actions.gen.go
42.82% <0.00%> (-2.43%)
:arrow_down:

pkg/actionlog/context.go
100.00% <ø> (ø)

pkg/actionlog/service.go
83.67% <ø> (ø)

pkg/envoy/resource/rbac_references_system.gen.go
12.50% <0.00%> (-1.79%)
:arrow_down:

pkg/envoy/resource/rbac_rules_parse.gen.go
36.49% <0.00%> (-1.97%)
:arrow_down:

pkg/envoy/store/rbac_rule_marshal.go
46.75% <0.00%> (ø)

... and 87 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 e8bc614...b7e02a7. Read the comment docs.

merged manually.


Splunk Configuration Instructions

Hi,
We're trying to try out this tool, which looks like it could be very useful. We have data in a Splunk instance, which our CASCADE server is successfully authenticating against.
I understand that the next step for us is to normalise our sensor data using the CAR data model. However this appears to be easier said than done, because:

Our Splunk instance doesn't have the CAR Data Model created.
Our Splunk instance doesn't have any of the tags created which are used by the CASCADE server. (See example query below)
Our Splunk instance also doesn't understand the 'export' command, which I assume is a custom search command. (See example query below)

Example query:
tag=dm-process-create ( exe="sc.exe" AND command_line="* start *") | fields command_line current_directory duration exe fqdn hostname image_path integrity_level md5_hash parent_command_line parent_exe parent_image_path pid ppid sha1_hash sha256_hash sid terminal_session_id user | export add_timestamp=f add_offset=t segmentation=none
Are we missing something here - do we need to manually create the data models and tags, or are configuration scripts / a Splunk app available? What about the missing 'export' command?
Thank you in advance.

Hi, how do you autheitcate your splunk to cascade , please guide me thanks


Make sausagelink pickle-compatible

It's not possible to pickle a Link object right now... that sucks.

Fixed in the 1.5 release!


Docker start failed

I follow all the instructions to build docker images, but I meet such exception when starting the application.
What is the reason? Thank you for your help.

OpenAI IP forbidden.


fixes typo res => err

Hi, this fixes a small typo: res is undefined

Actually I think it should just be txhash there (defined in the enclosing scope), since err is an error object and doesn't have a txHash property.  Thanks for bringing this to my attention; closing and pushing a fix.