MGMT-9937: Fix Logout

LGTM

:tada: This PR is included in version 1.1.13 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Jagged Line With SVG In Chrome For Diagonal Header Bar

It seems like the svg at the top of the page used to make the diagonal effect for the header is a bit jagged in Chrome.  From what I can tell this is more visible on screen with lower pixel density... (I notice it on my lower quality laptop screen and not on a mobile device.)  It also seems to be a thing Chrome, since it shows up fine in Firefox and Edge.  I'll try to include some screenshots below, though it may be hard to see from that.  Are there any tricks that could be used to make SVG render more smooth in Chrome?
Chrome:

Firefox:

Edge: (shadow doesn't render correctly in Edge as well...)

I don’t think we have any control over how Chrome renders SVG. But I might turn this into a Chrome Bug once CDS insanity is over :)

Pretty much, it's down to the browsers and there isn't much I can do. Going to close it for now.

Alright, fair enough. Might seem like splitting hairs.  If you are viewing it on your high pixel density laptop display I doubt you can see much of an issue.
For what it's worth my colleagues immediately asked about it when I showed them the site as well...  The jaggedness looks bad enough that it almost looks like the material design tab underline thing under the various section in the header...  I guess there are lot of known issues when it comes to Chrome and rendering svg consistently that I see a lot people complaining on stack-overflow about.


HTTPS redirection

For non-API routes, users should be forced to use HTTPS.

Using Flask-SSLify (#870) didn't quite work, because the Google Cloud load balancer terminates SSL and sends an HTTP request to our app.
One possible approach would be configuring nginx: http://serverfault.com/a/735223
if ($http_x_forwarded_proto = "http") { return 302 https://$host$request_uri; } I'm not sure how to exclude /api though.
Perhaps another approach would be to implement this ourselves: if the request has X-Forwarded-Proto as http and the route is not /api, send a 302 and set the HSTS header. Essentially, just adapt some of the flask_sslify source.

A simple approach for now is to set PREFERRED_URL_SCHEME = 'https' in the config so url_for returns https links

We now redirect all urls to HTTPS (with HSTS)


[Issue #182] PEM action added

Simple implementation via console call
Related issue #182

I'll try to work out a solution, that doesn't use the console call.

And here we go: https://github.com/KrauseFx/fastlane/commit/80a9d0a43068eee3e75e579379fcfc18e7c49298
Thanks again for your work!

Wow, looks great!  Thank YOU for your amazing work! :+1:  :smiley:

Thanks for pushing me to work on this. I think the PEM integration is great now :+1:
I haven't yet released the update of fastlane, but you know how to install it locally in the mean time :wink:


First failure is not captured by Silent Retry

Hello! Love the gem.
I am facing an issue where, seemingly, the first time a silenced error occurs on a given Sidekiq job, it causes an error to be raised by the gem itself as it tries to check for a value that is not available -- the job_payload['retry_count'].
Sidekiq shows that a nil value is used in a comparison:

I've added a breakpoint where the error happens, and looked at the contents of job_payload on the first and on the second retries. I added debugger before line 20 on this file:
https://github.com/trusted/sidekiq-silent-retry/blob/e7dcdb2d296578343133d7b0fbbad703206d7786/lib/sidekiq/silent_retry/server_middleware.rb#L19-L21
# 1st time the job failed by a silenced error
==> job_payload
{"retry"=>3,
 "queue"=>"my_queue",
 "retry_in"=>300,
 "silent_retry"=>["SilencedError"],
 "args"=>["redacted"],
 "class"=>"MyJob",
 "jid"=>"redacted",
 "created_at"=>1723749896.382946,
 "bid"=>"redacted",
 "enqueued_at"=>1723749896.383102}
==> continue
# then the method fails with a "NoMethodError: undefined method `>=' for nil:NilClass" error
# which triggers the alerts on my application since it's an unexpected error.

# 2nd time the job failed, when it is retried by Sidekiq for the 1st failure
==> job_payload
{"retry"=>3,
 "queue"=>"my_queue",
 "retry_in"=>300,
 "silent_retry"=>["SilencedError"],
 "args"=>["redacted"],
 "class"=>"MyJob",
 "jid"=>"redacted",
 "created_at"=>1723749896.382946,
 "bid"=>"redacted",
 "enqueued_at"=>1723750427.9472692,
 "error_message"=>"undefined method `>=' for nil:NilClass",  # new
 "error_class"=>"NoMethodError",                             # new
 "failed_at"=>1723750118.844531,                             # new
 "retry_count"=>0}                                           # new
==> continue
# this time around the method continues normally and raises the MySilentRetryError error
# without triggering any alerts, as I expect it to.

Faced the same issue
I'm able to help if needed!


Light theme styles result in unreadable text colors

Hi! Trying out logdy for the first time. Seems useful, but the light theme behavior seems to result in text that is unreadable:

If I manually edit the root theme styles like this in the DevTools CSS viewer:
@media (prefers-color-scheme: light)
:root {
    /* color: #213547; */
    /* background-color: #fff;

Then I get a dark theme that seems readable:

Could you check the light theme behavior and see if it needs tweaking?

Nice, thanks!


Change attach statsbeat allowed values

From specs

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


import/namespace in combination with @vercel/node is increasing the linting time by a factor of x80

Repo for reproduction is here: https://github.com/ChristianIvicevic/import-namespace-issue-repro
I noticed that eslint takes ages linting the single file in this repo and profiling timings yields the following:
Rule                                      | Time (ms) | Relative
:-----------------------------------------|----------:|--------:
import/namespace                          |  8546.897 |    99.8%
@typescript-eslint/no-floating-promises   |     9.076 |     0.1%
@typescript-eslint/no-unused-vars         |     1.006 |     0.0%
@typescript-eslint/no-unsafe-argument     |     0.989 |     0.0%
@typescript-eslint/no-misused-promises    |     0.556 |     0.0%
@typescript-eslint/ban-types              |     0.318 |     0.0%
@typescript-eslint/no-empty-function      |     0.270 |     0.0%
@typescript-eslint/no-loss-of-precision   |     0.257 |     0.0%
@typescript-eslint/triple-slash-reference |     0.220 |     0.0%
@typescript-eslint/no-unsafe-call         |     0.163 |     0.0%

After trial-and-error I noticed that the offending line is this:
https://github.com/ChristianIvicevic/import-namespace-issue-repro/blob/9ec4d56d22280ad3d94671fb282262107dd47304/.eslintrc.js#L38-L40
Removing all JS extensions fixes the abysmal speed of import/namespace:
Rule                                       | Time (ms) | Relative
:------------------------------------------|----------:|--------:
import/namespace                           |    92.790 |    87.9%
@typescript-eslint/no-floating-promises    |     8.542 |     8.1%
@typescript-eslint/no-unsafe-argument      |     0.962 |     0.9%
@typescript-eslint/no-unused-vars          |     0.843 |     0.8%
@typescript-eslint/no-misused-promises     |     0.468 |     0.4%
@typescript-eslint/no-empty-function       |     0.249 |     0.2%
@typescript-eslint/ban-types               |     0.209 |     0.2%
@typescript-eslint/no-loss-of-precision    |     0.202 |     0.2%
@typescript-eslint/no-unsafe-member-access |     0.136 |     0.1%
@typescript-eslint/no-unsafe-call          |     0.127 |     0.1%

For the time being I have disabled import/namespace for my lambdas that import @vercel/node.

The slow part is the ExportMap.get call, which has to build up a dependency graph of everything - including @vercel/node, which must take awhile to traverse.
If you enable multiple import rules that use the ExportMap, whichever is first will be "blamed" for being slow, and the rest will be fast. In other words, this doesn't have anything to do with namespace specifically, but something with the ExportMap combined with @vercel/node.

@ljharb Is there anything either the plugin can do to better or that @vercel/node can improve?

Almost certainly yes on both counts - #2531 may help, if @vercel/node imports an inordinate number of type definitions from d.ts files, but beyond that, someone would have to do some pretty thorough debugging to figure out what was making it slow.

related: https://github.com/import-js/eslint-plugin-import/issues/2340


About RPN

Thanks for your work.
I've noticed: 'We first adopt the rotation-equivariant backbone to extract rotation-equivariant features, followed by an RPN and RoI Transformer (RT)'
But in your config file, you are using class RPNHead. But I can't find where you implement the transformer?
btw. the `class RPNHeadRbbox' is for the RRPN? (https://arxiv.org/pdf/1703.01086.pdf)

RPN(RPNHead) and RoI Transoformer(SharedFCBBoxHeadRbbox)
https://github.com/csuhan/ReDet/blob/0b9addf3c2734659fd6ffc7824f2e659fde4419c/configs/ReDet/ReDet_re50_refpn_1x_dota1.py#L17-L47

the `class RPNHeadRbbox' is for the RRPN?

RPNHeadRbbox is a temp version of RRPN, we do not suggest to use it.

RPN(RPNHead) and RoI Transoformer(SharedFCBBoxHeadRbbox)
https://github.com/csuhan/ReDet/blob/0b9addf3c2734659fd6ffc7824f2e659fde4419c/configs/ReDet/ReDet_re50_refpn_1x_dota1.py#L17-L47

the `class RPNHeadRbbox' is for the RRPN?

RPNHeadRbbox is a temp version of RRPN, we do not suggest to use it.

I've read a lot from that project in these days. I think if we want the rbox, we need to define the ROI Transformer from line 17 - line 66 right?
https://github.com/csuhan/ReDet/blob/0b9addf3c2734659fd6ffc7824f2e659fde4419c/configs/ReDet/ReDet_re50_refpn_1x_dota1.py#L17-L66
so basically, if I'm right, you've only used your own rotation-equivariant backbone and FPN in this config?
Thanks again for saving a lot of time for us


If < or > exists in a step name, it is removed from the report HTML

Environment (please complete the following information):

multiple-cucumber-html-reporter: 1.13.1
Node.js version: v12.13.1
Yarn version: 1.19.1
Platform name and version: Ubutnu 19.10
Cucucmber version: 6.0.5

Config of multiple-cucumber-html-reporter
    reporter.generate({
        jsonDir: args.report,
        reportPath: args.output,
        customMetadata: true,
        displayDuration: true
    })

Describe the bug
We have a step that takes a string argument, and that argument often times has strings like this in it: <timestamp>. We use it to parse entries from a text file by searching for the string argument.
However, when we generate the report, the argument is changed to an empty string:

To Reproduce
Here is an example report I used to generate the above screenshot:
[
  {
    "keyword": "Feature",
    "name": "Test",
    "line": 1,
    "id": "test",
    "tags": [],
    "uri": "features/test.feature",
    "elements": [
      {
        "id": "test;wait-for-2-seconds",
        "keyword": "Scenario",
        "line": 2,
        "name": "Wait for 2 seconds",
        "tags": [],
        "type": "scenario",
        "steps": [
          {
            "arguments": [],
            "keyword": "Given ",
            "line": 3,
            "name": "we look for this text in the file \"<myTest>\"",
            "match": {
              "location": "features/steps/test.js:7"
            },
            "result": {
              "status": "passed",
              "duration": 0
            }
          }
        ]
      }
    ]
  }
]

Expected behavior
I would expect "" to appear in the report, and not an empty string. It's a bit confusing to have it stripped out, as the report does not match the actual step run.

Looking at the output, it seems the browser interprets it as a tag, causing it not to be shown. Here's the above report:

@dawn-minion
Can you please verify it with https://github.com/wswebcreation/multiple-cucumber-html-reporter/releases/tag/v1.13.2?

@wswebcreation Will do this morning, thanks for releasing it

Just tried the release, works great.

Awesome, thanks for your time!


#159 Refactor file structure

Note: As of right now there is a unit test that is failing because it can't find ResourceType. I'm still working on this, but the rest is ready for review.

Refactored the file structure to be more consistent with PowerShell project community standards.
Refactored some aspects of the files internals to be more consistent with PowerShell community standards.
Updated unit tests to work with the new file structure.
Added a build script that works both locally (dot sourcing files) and for deployment to PS Gallery (merged into a single .psm1 file).
Updated the docs to reflect the changes and requirements.

I have to fix ci-publish-docs-branch.yml. It has an incorrect reference path. It needs to use the artifacts from the ci.yml workflow instead.


can I make Command into a protocol, and have a few "built-in" commands to allow for easier non-library expansion

There's a lot of options, and potential complications, when taking this to other platforms. In particular, it's mostly built with Ansible's preconceptions that ssh is a command-line tool that's readily available via a local subprocess shell, and that may not be the case. There's some really interesting libraries out there (Citadel, in particular) that can do a pure-swift SSH connection if that's not the case. Likewise, you might easily want to use SwiftCommand or Shwift - neither of which would plug in today.
I think, in particular, I want to break up the declaration of a command and it's implementation - likely using Generics, and letting someone assemble their own commands that a Playbook could run in sequence, even well beyond the bits that I'm doing here with .shell, .copy, etc that are using Foundation's process today (also see #31).
As I'm layering "Resources" into something that uses commands, that may complicate the definition of Resource and how it's described, perhaps making a resource generic over the command type, or forcing an explicit choice in the resource protocol definition to enable it - both for querying state and resolving state (the later not yet really established)

I've also just stumbled across swift-commands - another variant on the subprocess thing that's been around a while, and I missed completely when searching for it.


New version release v0.10.0

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

Codecov Report

Merging #1006 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1006      +/-   ##
==========================================
- Coverage   54.98%   54.95%   -0.04%
==========================================
  Files         244      244
  Lines       23684    23684
==========================================
- Hits        13023    13015       -8
- Misses       9467     9472       +5
- Partials     1194     1197       +3

Impacted Files
Coverage Δ

pkg/stream/stream.go
46.66% <0%> (-13.34%)
:arrow_down:

pkg/network/connection.go
34.97% <0%> (-0.38%)
:arrow_down:

pkg/module/http2/frame.go
84.17% <0%> (-0.31%)
:arrow_down:

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 d5ba9b8...2b96de4. Read the comment docs.


New version: 8x8.Work version 7.13.2

Pull request has been created with Komac v1.11.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Related to: https://github.com/microsoft/winget-pkgs/issues/135119


Add authentication section for gdrive NPX

Description
gdrive --> README.md --> Usage with Desktop App --> NPX, Authentication section are not documented.
Server Details

Server: gdrive
Changes to: README.md only

Motivation and Context

NPX users may become confused.
How Has This Been Tested?

Verified README formatting
Confirmed command and descriptions are accurate
Tested with Claude Desktop

Breaking Changes

No breaking changes - documentation update only.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation update

Checklist

[x] I have read the MCP Protocol Documentation
[x] My changes follows MCP security best practices
[x] I have updated the server's README accordingly
[x] I have tested this with an LLM client
[x] My code follows the repository's style guidelines
[x] New and existing tests pass locally
[x] I have added appropriate error handling
[x] I have documented all environment variables and configuration options

Additional context

FYI, due to unreleased bugfixes, it won't work with NPX until the package is published.
https://github.com/modelcontextprotocol/servers/issues/402#issuecomment-2562917712


Formattin and config in CLI

Added the following to the CLI:

config init command that creates a new configuration file

config schema print JSON schema for the config (will be useful for TOML ide completions)

fmt (--check) check formatting and/or format files in place

It is now possible to mass-format files via the cli.
Custom operators are supported based on the definition files that can be found according to the Rhai.toml or default config, this means that at the beginning we build up a HIR. It might sound overkill just for formatting, but this way the user does not have to do anything extra to support custom operators.

So I do a rhai fmt in a directory?

Yes, if you do just rhai fmt, files included in the config (or current dir if no rhai config exists) will be formatted, alternatively you can do rhai fmt . or rhai fmt "some/glob/**/*.rhai"


Increment version for C SDK releases

Increment sdk version after release of C SDK

Closing this in favor of https://github.com/Azure/azure-sdk-for-c/pull/2171 which updates the az_version.h post-stable-release properly, and gets rid of the undef.


update(cmake): bump libs to 0.12.0 and driver to 5.1.0+driver

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Engine version has been bumped to 20 accordingly.
Does this PR introduce a user-facing change?:
update(cmake): bump libs and driver to 0.12.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 43c88b5545ac6b320d276e7fba315a544b76d5be

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Bug: Unable to use tools in conversation

When the model try to call the tools that it have, it would always failed and return:
{"message":"An unexpected error occurred"}

Screenshot:

Will investigate.
Any additional info you can share about your tools is helpful!
Also - that UI needs work. Woof.

Any additional info you can share about your tools is helpful!

Sure thing!😊 I use several tools to do tasks like search on GitHub, open files on GitHub, search develop documentation on DevDocs, and many others. These tools does not require any kind of header.


Not working anymore

Hi,
I wanted to use your example but it's not working anymore.
this is the error logged by spring:
tailable cursor requested on non capped collection' on server localhost:27017

In order to support a tailable cursor (in order to read records as they come) in a Mongodb collection you need to create it with the capped attribute set to true, just create the collection manually with something similar to the below command inside the mongo shell (delete the collection if it's already created),
db.createCollection("tweets", {capped:true, max:1500, size:1000000})
That should make that error go away, let me know otherwise.


[contracts] feat: Implement Locking of Liquidity Provider (LP) Tokens for 6 Months

Issue: Implement Locking of Liquidity Provider (LP) Tokens for 6 Months
Description
The objective of this issue is to implement a feature in the smart contract to lock the Liquidity Provider (LP) tokens for a period of six months. This locking mechanism is intended to enhance the trust and stability of the token by ensuring that liquidity is maintained in the market for a substantial period after launch.
Requirements

Locking Mechanism: Develop a smart contract function or module that locks the LP tokens for a period of six months from the date of the liquidity being added to the pool.
Time Tracking: Implement a reliable and accurate time-tracking system within the contract to track the 6-month lock period.
Unlocking Functionality: After the lock period has elapsed, ensure that there is a secure and efficient mechanism for the LP tokens to be unlocked and made available.
Transparency and Security: Ensure that the locking mechanism is transparent and secure, providing confidence to token holders and liquidity providers.

Implementation Notes

Pay close attention to the accuracy and security of the time-lock mechanism.
Ensure that the lock and unlock functionalities are resistant to common smart contract vulnerabilities.
Consider the gas costs associated with these functionalities and optimize where possible.
Thoroughly test the lock and unlock process, including edge cases around the timing of the lock period expiration.

I can take that

I can take that

Great, assigned to you


Post to a live thread.

public String postToLive(String message, String thread) throws IOException {
  String apiParams = "api_type=json&body=" + message+ "&uh=" + user.getModhash();

  Response res = restClient.post(apiParams, "/api/live/" + thread + "/update", user.getCookie());

  return res.getResponseText();
}

@eduardog3000 can you make a pull request with the things that you want to add?


fixed missing -t option

While --interval nn worked, -t nn did not.
Reordered the switches to reflect switch-case order.

First I thank you for the interest in improving this software.
However, I see that this pull request covers a bunch of different issues that are unrelated from the PR title and description. I ask you if you can remove the unrelated commits from this PR and submit them in dedicated ones, so that they can be addressed separately.
Thank you!

Dear Alessandro,
yes, I completely see your point. It was not my intention to introduce that pile of changes. I was using Subversion since 20 years (and RCS, CVS the ten years before) and I switched late to Git, right last Christmas. Still learning Git. It was very surprising for me to see that my local branches re-integrations created more and more entries for the pull request here.
Regarding the growing CLI, I completely confirming your opinion. With recent experiments, my CLI will grow fast and I also pull additions from other forks to see how they can help. There will be some day to cut off overblown or useless stuff. And to focus related options into one (i.e.: I could imagine a kind of --verbose 1..n switch, the higher the verbosity, the talkative the outputs).
So I'd like to propose this: You close and ignore this PR, I follow my next 3 weeks agenda - really fixing the 32 byte FTDI bulk transfer + integrating an optionally content decoding. After I finished my stuff, we both take a look into a smart way to offer only the fixes to your origin. To be honest, I hope I can learn and train Git a bit more with your support then ;-)

No problem! I know that git at the beginning may seem hard.
I see that the problem is that you opened a PR from your own fork branch master. That is then you modified and added commit to the master branch and that changed the content of this PR. Differently from other systems git supports multiple code branches.
What you usually do is:

align your own fork with the latest main project
create a branch where to work into
create commits on this branch
when you have done doing changes, open a PR from your repo:branch to the remote
if you want to do changes on the PR, you just commit new files on this branch

The most simple thing to fix this situation would be to archive your local changes, reset your fork to the remote state and proceed by creating a branch for each feature and integrating your own changes.
However, if you want to learn git more in depth, you can try experimenting the cherry-pick feature. You can create a branch starting from the latest commit on this repository (a commit is identified by an hash), then add to that branch the commit you made in your branch that you want to add. Then open the PR through GitHub. Then repeat this operation for all the feature you want to submit as PR.
If you have any other questions I'm glad to answer them.

Closed for inactivity.


Error @Code.gs:30

I need help. I get this error when I run the code.
Error	TypeError: Cannot read property '_rowIndex' of undefined
setRowData	@ Code.gs:30

You need to submit a request via Google Form to run this code.


adr: do not (re)try lowering txpower on txpower nACK

Dear @brocaar
I am currently evaluating the ADR functionality of loraserver.
The node is an RN2483, and ADR is set on.
On the backend the node is registered with OTAA and ADR interval=2.
After the node is reset and join successfully happens, the network server starts to change the tx power level of the node. This starts from req_tx_power_idx=1, which corresponds to 14dBm, and it decreases the req_tx_power_idx by 1 after each node transmission. So far so good. The node acknowledges these adr commands until req_tx_power_idx<5.

Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="mac-command block added to queue" cid=LinkADRReq dev_eui=0004a30b001bc49a frmpayload=false
Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="adr request added to mac-command queue" dev_eui=0004a30b001bc49a dr=5 nb_trans=1 req_dr=5 req_nb_trans=1 req_tx_power_idx=5 tx_power=4
Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a
Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="backend/gateway: publishing tx packet" topic="gateway/5ccf7fffff1e22fe/tx"
Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a
Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="pending mac-command block set" cid=LinkADRReq commands=1 dev_eui=0004a30b001bc49a frm_payload=false
Jul 14 15:24:19 nwsrv loraserver[4229]: time="2017-07-14T15:24:19+02:00" level=info msg="mac-command block removed from queue" cid=LinkADRReq dev_eui=0004a30b001bc49a
Jul 14 15:24:53 nwsrv loraserver[4229]: time="2017-07-14T15:24:53+02:00" level=info msg="packet(s) collected" dev_eui=0004a30b001bc49a gw_count=1 gw_macs=5ccf7ffffff7a009 mtype=ConfirmedDataUp
Jul 14 15:24:53 nwsrv loraserver[4229]: time="2017-07-14T15:24:53+02:00" level=info msg="rx info sent to network-controller" dev_eui=0004a30b001bc49a
Jul 14 15:24:53 nwsrv loraserver[4229]: time="2017-07-14T15:24:53+02:00" level=info msg="mac-command block removed from pending" cid=LinkADRReq dev_eui=0004a30b001bc49a
Jul 14 15:24:53 nwsrv loraserver[4229]: time="2017-07-14T15:24:53+02:00" level=info msg="link_adr request acknowledged" dev_eui=0004a30b001bc49a dr=5 enabled_channels=[0 1 2] nb_trans=1 tx_power_idx=5
Jul 14 15:24:53 nwsrv loraserver[4229]: time="2017-07-14T15:24:53+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a

But the network server does not stop to decrease, so it sends again with req_tx_power_idx=6. This can not be handled by the node, since this parameter can have 1...5 value according to the RN2483 command reference and the LoRaWAN specification 1.0, section 7.1.3.

Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="mac-command block added to queue" cid=LinkADRReq dev_eui=0004a30b001bc49a frmpayload=false
Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="adr request added to mac-command queue" dev_eui=0004a30b001bc49a dr=5 nb_trans=1 req_dr=5 req_nb_trans=1 req_tx_power_idx=6 tx_power=5
Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a
Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="backend/gateway: publishing tx packet" topic="gateway/5ccf7fffff1e22fe/tx"
Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a
Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="pending mac-command block set" cid=LinkADRReq commands=1 dev_eui=0004a30b001bc49a frm_payload=false
Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="mac-command block removed from queue" cid=LinkADRReq dev_eui=0004a30b001bc49a
Jul 14 15:25:26 nwsrv loraserver[4229]: time="2017-07-14T15:25:26+02:00" level=info msg="packet(s) collected" dev_eui=0004a30b001bc49a gw_count=1 gw_macs=5ccf7ffffff7a009 mtype=ConfirmedDataUp
Jul 14 15:25:26 nwsrv loraserver[4229]: time="2017-07-14T15:25:26+02:00" level=info msg="rx info sent to network-controller" dev_eui=0004a30b001bc49a
Jul 14 15:25:26 nwsrv loraserver[4229]: time="2017-07-14T15:25:26+02:00" level=info msg="mac-command block removed from pending" cid=LinkADRReq dev_eui=0004a30b001bc49a
Jul 14 15:25:26 nwsrv loraserver[4229]: time="2017-07-14T15:25:26+02:00" level=warning msg="link_adr request not acknowledged" channel_mask_ack=true data_rate_ack=true dev_eui=0004a30b001bc49a power_ack=false
Jul 14 15:25:26 nwsrv loraserver[4229]: time="2017-07-14T15:25:26+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a

From this point onward the network server always tries to set req_tx_power_idx=6, but the node always denies to perform this action as per above.
And I think this has an effect on the data_rate setting aswell, beacuse the node is getting commanded to set the date_rate=5 but remains on the original data rate .

Jul 14 16:53:22 nwsrv loraserver[4229]: time="2017-07-14T16:53:22+02:00" level=info msg="mac-command block added to queue" cid=LinkADRReq dev_eui=0004a30b001bc49a frmpayload=false
Jul 14 16:53:22 nwsrv loraserver[4229]: time="2017-07-14T16:53:22+02:00" level=info msg="adr request added to mac-command queue" dev_eui=0004a30b001bc49a dr=3 nb_trans=1 req_dr=5 req_nb_trans=1 req_tx_power_idx=6 tx_power=5
Jul 14 16:53:22 nwsrv loraserver[4229]: time="2017-07-14T16:53:22+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a

Jul 14 16:55:46 nwsrv loraserver[4229]: time="2017-07-14T16:55:46+02:00" level=info msg="mac-command block removed from pending" cid=LinkADRReq dev_eui=0004a30b001bc49a
Jul 14 16:55:46 nwsrv loraserver[4229]: time="2017-07-14T16:55:46+02:00" level=warning msg="link_adr request not acknowledged" channel_mask_ack=true data_rate_ack=true dev_eui=0004a30b001bc49a power_ack=false
Jul 14 16:55:46 nwsrv loraserver[4229]: time="2017-07-14T16:55:46+02:00" level=info msg="node-session saved" dev_addr=06ab9849 dev_eui=0004a30b001bc49a

Which results in that in time the node reaches dr=0, and unable to get back to dr=5, just with a reset.
(the gateway and node distance in this case is a couple of meter)
Could you please look into this?
I am open to test a new public release if solution is found.
Thanks.
Regards,
Tamas

Hi Tamas, the new LoRaWAN Regional Parameters spec defines more TXPower indices than the current RN2483 node supports, so it is expected that these nodes will nACK the tx-power change to 6. Please note that the ADR engine first tries to increase the data-rate, before it tries to decrease the TX Power.

Jul 14 15:25:05 nwsrv loraserver[4229]: time="2017-07-14T15:25:05+02:00" level=info msg="adr request added to mac-command queue" dev_eui=0004a30b001bc49a dr=5 nb_trans=1 req_dr=5 req_nb_trans=1 req_tx_power_idx=6 tx_power=5

Please note that at this time, the node is already operating on dr=5 and tx_power=5.

Hi Brocaar!
Thank you very much for your information. I understand that additional tx power idx has been added (read in the other issue topic), and that is refused by the RN2483 firmware. But what I am trying to describe, is that in a situation where an unsupported tx power idx is sent to the RN2483 it is not able to perform dr change.
I briefly summarize the situation.

After node reset the node starts with dr=5, tx power=14. The OTAA join successfully done.

Jul 16 15:40:27 nwsrv loraserver[4229]: time="2017-07-16T15:40:27+02:00" level=info msg="backend/gateway: rx packet received"
Jul 16 15:40:28 nwsrv loraserver[4229]: time="2017-07-16T15:40:28+02:00" level=info msg="packet(s) collected" dev_eui=0004a30b001bc49a gw_count=1 gw_macs=5ccf7fffff1e22fe mtype=JoinRequest
Jul 16 15:40:28 nwsrv loraserver[4229]: time="2017-07-16T15:40:28+02:00" level=info msg="node-session saved" dev_addr=06d09b52 dev_eui=0004a30b001bc49a
Jul 16 15:40:28 nwsrv loraserver[4229]: time="2017-07-16T15:40:28+02:00" level=info msg="backend/gateway: publishing tx packet" topic="gateway/5ccf7fffff1e22fe/tx"

RN2483 state:
mac join otaa
ok
accepted
mac get dr
5
radio get pwr
14

packet 1 - OK
packet 2 - OK (note: ADR interval is set to 2)
packet 3 - OK. Network server instructs node to change pwr level idx.

Jul 16 15:46:30 nwsrv loraserver[4229]: time="2017-07-16T15:46:30+02:00" level=info msg="backend/gateway: rx packet received"
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="packet(s) collected" dev_eui=0004a30b001bc49a gw_count=1 gw_macs=5ccf7fffff1e22fe mtype=ConfirmedDataUp
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="rx info sent to network-controller" dev_eui=0004a30b001bc49a
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="mac-command block added to queue" cid=LinkADRReq dev_eui=0004a30b001bc49a frmpayload=false
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="adr request added to mac-command queue" dev_eui=0004a30b001bc49a dr=5 nb_trans=0 req_dr=5 req_nb_trans=1 req_tx_power_idx=1 tx_power=0
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="node-session saved" dev_addr=06d09b52 dev_eui=0004a30b001bc49a
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="backend/gateway: publishing tx packet" topic="gateway/5ccf7fffff1e22fe/tx"
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="node-session saved" dev_addr=06d09b52 dev_eui=0004a30b001bc49a
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="pending mac-command block set" cid=LinkADRReq commands=1 dev_eui=0004a30b001bc49a frm_payload=false
Jul 16 15:46:31 nwsrv loraserver[4229]: time="2017-07-16T15:46:31+02:00" level=info msg="mac-command block removed from queue" cid=LinkADRReq dev_eui=0004a30b001bc49a

RN2483 state:
mac get dr
5
radio get pwr
14

packet 4 - OK. Node ack's ADR request.
RN2483 state:

mac get dr
5
radio get pwr
14

packet 5 - OK. Network server instructs node to increase power idx=2.
RN2483 state:

mac get dr
5
radio get pwr
11

packet 5 - Couple of unsuccessful transmit attempts. Node dr: 5-> 2. Mac error.
packet 6 - OK. No action on network server side to change MAC
packet 7 - OK. Previous MAC command is processed. Node dr: 2->5. Network server adds MAC command to change dr 2->5 and pwr_idx=3
packet 8 - OK. Node ack ADR change.
RN2483 state:

mac get dr
5
radio get pwr
8

So far operating fine regarding handling the dr  and pwr_idx.

packet 9 - OK. Network server adds MAC command to change dr 5->5 and pwr_idx=4
packet 10 - OK. Node ack ADR change.
RN2483 state

mac get dr
5
radio get pwr
5

packet 11 - OK. Network server adds MAC command to change dr 5->5 and pwr_idx=5
packet 10 - OK. Node ack ADR change.
RN2483 state

mac get dr
5
radio get pwr
2

packet 12 - OK. Network server adds MAC command to change dr 5->5 and pwr_idx=6
packet 13 - OK. Node nack ADR change due to invalid pwr_idx.

As per your comment, this is the "desired" operation, and I agree with that.
But from this point if the node dr is decreasing due to any condition (network, or manually set), the adr command sent by the network server is not processed by the node due to the "invalid" pwr idx=6
During this example I set it manually to dr=4

packet 14 -OK.
RN2483 state

mac get dr
5
mac set dr 4
ok
radio get pwr
2
mac tx cnf 1<PHONE_NUMBER>
ok
mac_tx_ok

Jul 16 16:13:19 nwsrv loraserver[4229]: time="2017-07-16T16:13:19+02:00" level=info msg="backend/gateway: rx packet received"
Jul 16 16:13:19 nwsrv loraserver[4229]: time="2017-07-16T16:13:19+02:00" level=info msg="packet(s) collected" dev_eui=0004a30b001bc49a gw_count=1 gw_macs=5ccf7ffffff7a009 mtype=ConfirmedDataUp
Jul 16 16:13:19 nwsrv loraserver[4229]: time="2017-07-16T16:13:19+02:00" level=info msg="rx info sent to network-controller" dev_eui=0004a30b001bc49a
Jul 16 16:13:19 nwsrv loraserver[4229]: time="2017-07-16T16:13:19+02:00" level=info msg="mac-command block added to queue" cid=LinkADRReq dev_eui=0004a30b001bc49a frmpayload=false
Jul 16 16:13:19 nwsrv loraserver[4229]: time="2017-07-16T16:13:19+02:00" level=info msg="adr request added to mac-command queue" dev_eui=0004a30b001bc49a dr=4 nb_trans=1 req_dr=5 req_nb_trans=1 req_tx_power_idx=6 tx_power=5
Jul 16 16:13:19 nwsrv loraserver[4229]: time="2017-07-16T16:13:19+02:00" level=info msg="node-session saved" dev_addr=06d09b52 dev_eui=0004a30b001bc49a

packet 15 -OK. Node nack ADR change.

Jul 16 16:16:02 nwsrv loraserver[4229]: time="2017-07-16T16:16:02+02:00" level=info msg="rx info sent to network-controller" dev_eui=0104a30b001bc49a
Jul 16 16:16:02 nwsrv loraserver[4229]: time="2017-07-16T16:16:02+02:00" level=info msg="node-session saved" dev_addr=072e0c46 dev_eui=0104a30b001bc49a
Jul 16 16:16:05 nwsrv loraserver[4229]: time="2017-07-16T16:16:05+02:00" level=info msg="backend/gateway: rx packet received"
Jul 16 16:16:05 nwsrv loraserver[4229]: time="2017-07-16T16:16:05+02:00" level=info msg="packet(s) collected" dev_eui=0004a30b001bc49a gw_count=1 gw_macs=240ac4ffff035c30 mtype=ConfirmedDataUp
Jul 16 16:16:05 nwsrv loraserver[4229]: time="2017-07-16T16:16:05+02:00" level=info msg="rx info sent to network-controller" dev_eui=0004a30b001bc49a
Jul 16 16:16:05 nwsrv loraserver[4229]: time="2017-07-16T16:16:05+02:00" level=info msg="mac-command block removed from pending" cid=LinkADRReq dev_eui=0004a30b001bc49a
Jul 16 16:16:05 nwsrv loraserver[4229]: time="2017-07-16T16:16:05+02:00" level=warning msg="link_adr request not acknowledged" channel_mask_ack=true data_rate_ack=true dev_eui=0004a30b001bc49a power_ack=false
Jul 16 16:16:05 nwsrv loraserver[4229]: time="2017-07-16T16:16:05+02:00" level=info msg="node-session saved" dev_addr=06d09b52 dev_eui=0004a30b001bc49a
RN2483 state
mac get dr
**4**
radio get pwr
2

As you can see node could not apply the previous MAC command dr: 4->5 and pwr_idx=6. And I am suspecting this is due that it gets a pwr_idx which is out of range it can set.
And for the next packets sent by the node this repeats until forever, i bad network conditions in time the node decreases further its dr until it reaches dr=0. And no chance (just with reset) to bring it back to better data rates.
Do you think it would be possible to add an option to this flow as an exception if node does not supports additional power level indexes, then the network server would not try to decrease further the power level?
Because currently we will loose the ADR flexibility at least with the RN2483 (and suppose RN2983 aswell, but i haven't checked the US version)
Thanks.
Kind regards,
Tamas

Thanks @mogyoros for your extended info. I understand your point now!

Do you think it would be possible to add an option to this flow as an exception if node does not supports additional power level indexes, then the network server would not try to decrease further the power level?

What you propose sounds like a good solution. I'll look into this soon.

Thanks @brocaar . Glad that I could explain the situation.
Awaiting for your feedback regarding the solution.
Of course I am ready to help and test it, when it becomes available.
Cheers,
Tamas

I need to do some more testing (real testing), but in the above commit I've updated the ADR engine to deal with data-rate and tx-power nACKs. In case of a nACK, it will store a maxSupportedTXPower or maxSupportedData rate which is the requested value - 1. So when TXPower 5 results in a nACK, the next time it will try with TXPower 4. The same for the data-rate.
What I still need to do:

[ ] Implement TXPower reset in node-session in case the data-rate was changed by the node (without ADR request). Else there might be the risk that the node is using TXPower 0, where the server still things it is transmitting using TXPower 3. When LoRa Server then would ask the node to lower the TXPower by one, it would ask the node to change to 4, where 1 is desired.

@mogyoros All changes have been made. Would you be able to test against the 0_20_fixes branch? https://github.com/brocaar/loraserver/tree/0_20_fixes

@brocaar willing to do it, but do I understand correctly, that I need to setup a docker compose environment and compile it for myself?
Until now I've just used the precompiled binaries available for ubuntu in the repo...
If so, I need a bit more time to learn the how to... :-)

@mogyoros I can compile a binary for you :-) let me know what platform you're using (windows, mac, linux / 32 or 64 bit).

@brocaar ubuntu linux x64 16.04 . And thanks for the shortcut! :-)

@mogyoros here you go: https://www.dropbox.com/sh/3a67pshdarcudrx/AABBNPK0mYsdiyxVW9bhR9Aha?dl=0

@brocaar : thank you. Downloaded and checked the functionality.

OTAA join, node dr=5, radio pwr=14

2 packets xmit ok

nwsrv: ADR command dr 5->5, pwr_idx 0->5

ADR ack, node dr=5, radio pwr=2

nwsrv: ADR command dr 5->5, pwr_idx 5->7

ADR nack, node dr=5, radio pwr=2

nwsrv: ADR command dr 5->5, pwr_idx 5->6

ADR nack, node dr=5, radio pwr=2

nwsrv: ADR command dr 5->5, pwr_idx 5->5

ADR ack, node dr=5, radio pwr=2

Node: setting manually dr=3

nwsrv: ADR command dr 3->5, pwr_idx 5->5

ADR ack, node dr=5, radio pwr=2

I think with this procedure we can live, and the RN2483 node can accommodate its dr to the network conditions.
Cheers,
Tamas

@mogyoros great! I was at a conference last week, but will do a release with this updated functionality this week :-)


GH-34540: [C++] Removed set but unused variable

Rationale for this change
The variable has been left from https://github.com/apache/arrow/commit/144699c4210ac0b75d16395a583671b2874acc9e, simply removed this variable from the code.
It breaks builds when -Werror option is used.

Are these changes tested?
It was successfully built.

Closes: #34540

cc @westonpace @wjones127 , mind take a look?


Download Version problem

Hello
I can not download your last source code
May you check it ?

How are you downloading? Git, zip, and release are all working fine...

I try Download and Clone button
some file was missing in zip file
may you check it again ?
i try to know how can i auto Detect GPS plug to computer

Runs fine for me so I'll need more information in order to help. Do you have any logs, errors, or screenshots?

Severity	Code	Description	Project	File	Line
Error		Unable to find manifest signing certificate in the certificate store.	Porty

Thank you, I see the problem. I just pushed the fix.


Memory corruption in format/2 with lots of atoms

Something I noticed while debugging a program which printed a really long list.
Test program:
test :-
    length(L, 1000), % lengths around 100 or larger seem to break it for me
    maplist(=(aaaaaaaaaaaaaaaabbbbbbbbbbbbbccccccccccccc), L),
    format("~w", [L]).

$ valgrind ./tpl -f segfault.pl -g test,halt
==4422== Memcheck, a memory error detector
==4422== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==4422== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==4422== Command: ./tpl -f segfault.pl -g test,halt
==4422==
==4422== Invalid write of size 1
==4422==    at 0x487B3D0: strcpy (in /usr/libexec/valgrind/vgpreload_memcheck-arm64-linux.so)
==4422==    by 0x133FBF: do_format (format.c:572)
==4422==    by 0x1BDD53: fn_format_2 (predicates.c:5746)
==4422==    by 0x1F870F: start (query.c:1591)
==4422==    by 0x1F91B3: execute (query.c:1808)
==4422==    by 0x183757: run (parser.c:3618)
==4422==    by 0x1EE4C3: pl_eval (prolog.c:139)
==4422==    by 0x116C0F: main (tpl.c:280)
==4422==  Address 0x59b9360 is 55,728 bytes inside an unallocated block of size 57,872 in arena "client"
==4422==
==4422== Invalid write of size 1
==4422==    at 0x487B3D8: strcpy (in /usr/libexec/valgrind/vgpreload_memcheck-arm64-linux.so)
==4422==    by 0x133FBF: do_format (format.c:572)
==4422==    by 0x1BDD53: fn_format_2 (predicates.c:5746)
==4422==    by 0x1F870F: start (query.c:1591)
==4422==    by 0x1F91B3: execute (query.c:1808)
==4422==    by 0x183757: run (parser.c:3618)
==4422==    by 0x1EE4C3: pl_eval (prolog.c:139)
==4422==    by 0x116C0F: main (tpl.c:280)
==4422==  Address 0x59b9361 is 55,729 bytes inside an unallocated block of size 57,872 in arena "client"
==4422==

valgrind: m_mallocfree.c:303 (get_bszB_as_is): Assertion 'bszB_lo == bszB_hi' failed.
valgrind: Heap block lo/hi size mismatch: lo = 57937, hi =<PHONE_NUMBER>131513954.
This is probably caused by your program erroneously writing past the
end of a heap block and corrupting heap metadata.  If you fix any
invalid writes reported by Memcheck, this assertion failure will
probably go away.  Please try that before reporting this as a bug.

host stacktrace:
==4422==    at 0x58040FEC: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x58041143: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x580412AB: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x5804B9D7: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x580392D3: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x58037993: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x5803C537: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x58036B03: ??? (in /usr/libexec/valgrind/memcheck-arm64-linux)
==4422==    by 0x1003093BDF: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 4422)
==4422==    at 0x487B3E8: strcpy (in /usr/libexec/valgrind/vgpreload_memcheck-arm64-linux.so)
==4422==    by 0x133FBF: do_format (format.c:572)
==4422==    by 0x1BDD53: fn_format_2 (predicates.c:5746)
==4422==    by 0x1F870F: start (query.c:1591)
==4422==    by 0x1F91B3: execute (query.c:1808)
==4422==    by 0x183757: run (parser.c:3618)
==4422==    by 0x1EE4C3: pl_eval (prolog.c:139)
==4422==    by 0x116C0F: main (tpl.c:280)
client stack range: [0x1FFEFB3000 0x1FFF000FFF] client SP: 0x1FFEFFF6E0
valgrind stack range: [0x1002DC4000 0x1002EC3FFF] top usage: 19584 of 1048576

$ ./tpl --version
Trealla Prolog (c) Infradig 2020-2023, v2.24.6

Runs smoothly now, thanks!


install ODBC Driver as part of the installation package

Hi,
It would be very handy to include the installation or update the ODBC driver as part of the configurable installation items.
We use SQL Server to store and manage most of our spatial data. I have to manually install the ODBC driver in order for the portal/server to register the connection file to the SQL DB.
This is just a wish list. Thanks for the consideration.
Helen

Vote Up!  This hit us today on testing out a PSDSC install of ArcGIS Enterprise.  We will be looking for alternative automated install options for the SQL Server Driver as well so that we dont have to manually complete this work.
Thanks for the consideration.

Vote Up!

Hello @dird-hyang @pfoppe and @DCHuber,
This has been added to the latest release, v3.0.0:
https://github.com/Esri/arcgis-powershell-dsc/releases
Tutorial Wiki:
https://github.com/Esri/arcgis-powershell-dsc/wiki/V3.-Register-an-Enterprise-Geodatabase-with-ArcGIS-Server-site
Sample Config:
https://github.com/Esri/arcgis-powershell-dsc/blob/master/SampleConfigs/v3/Gis Servers/GISServer-Database.json

Great news!!! Thank you!


CORE-18930: make transaction ID deterministic

The privacy salt currently gets a unique ID for transactions that is random. We need it to be unique but also deterministic. The random aspect will be replaced with a concatenation of FlowID+suspendCount which are obtained from the checkpoint. To get this data, FlowFiberService will be used. A service will be created that uses FlowFiberService to give our privacy salt, so this can be injected in several places. Testing should show that transactions with the same flowID and suspendCount give the same ID (deterministic) even if created multiple times.

Can two privacy salts be requested whileFlowID+suspendCount is the same?
Although probably it is not a real problem if that is not possible, since toSignedTransaction()s, where the privacy salt gets assigned, suspend anyway. (at least for the signing operation IIRC.)

Details

@vlajos I've checked with @LWogan and we would say no, for the reason you mention (because toSignTransaction will always suspend) and as long as we're always signing after creating transactions the suspendCount will increment.


Shared code and Enchantment color refactor

This PR shares a single renderLore function between the client and server and changes it so that the max level enchants are gold

About the failing CI / check typescript... can anything be done about it?

About the failing CI / check typescript... can anything be done about it?

not sure I'll look into it soon

About the failing CI / check typescript... can anything be done about it?

fixed in https://github.com/SkyCryptWebsite/SkyCrypt/pull/1087/commits/b3cec2f6b509ec783456943dfdae2f9b183ac5f3

somehow rollup got broken but it should all be good now


Warn when missing minimal bounds when using tool.uv.sources

When using tool.uv.sources, we warn that requirements have a bound, i.e. at least a lower version constraint.
When using a library, the symbols you import were introduced in different versions, creating an implicit lower bound. This warning makes this explicit. This is crucial to prevent backtracking resolvers from selecting an ancient versions that is not compatible (or worse, doesn't build), and a performance optimization on top.
This feature is gated to tool.uv.sources (as it should have been to begin with for #3263/#3443) to not unnecessarily break legacy workflows. It is also helpful specifically when using a tool.uv.sources section that contains constraints that are not published to pypi, e.g. for workspace dependencies. We can adjust those later to e.g. not constrain workspace dependencies with publish = false, but i think it's the right setting to start with.

I think I have a strong preference for this being a warning?

This is a correctness check (no lower bound is almost certainly incorrect), you should not be able to silence correctness checks; the correct way to get rid of the warning is to add the lower bound your project has, either implicitly or by policy.

I'm not totally convinced that I want this, but I guess it's fine for now if it's limited to tool.uv.sources and doesn't show up for non-sources users.

Is there a way to add lower bounds automatically for installed dependencies?
Not sure what exactly triggered the warning, update to 0.3.1 or (I guess more likely) adding a dependency from GitHub.

Sorry, should have added more context from the beginning.
I updated from uv 0.3.0 to 0.3.1 AND replaced the spyne package from pypi with spyne package from GitHub like that:
uv remove spyne
uv add git+https://github.com/arskom/spyne@f105ec2f41495485fef1211fe73394231b3f76e5

After that I tried to run uv sync and received warnings
warning: Missing version constraint (e.g., a lower bound) for `celery`
warning: Missing version constraint (e.g., a lower bound) for `django`

My dependencies at the moment:
[project]
dependncies = [
  "celery",
  "django",
 ]

This was expected, so no error (not even a real problem) here.
But since I had a ton of dependencies, I thought, maybe there is a way to "half-lock" them in the [project] table.
So that I could turn the example above into something like:
[project]
dependncies = [
  "celery>=5.4.0",
  "django>=5.1",
 ]

for all regular and dev dependencies.


Rate limiting has to be effective for rate and feedforward parts

This log from @Zefz shows that the rate limiting is currently not effective for all gains:
http://dash.oznet.ch/view/VHo7DDhC9Sxy9FCEuQgJUK#A_RollRate_PLOT
This leads to an altitude loss with the new auto-scaling mixer. @tumbili This should be a quick fix.

@LorenzMeier @Zefz I don't think this is the problem. What about the number of satellites you had? Zero seems a bit too low for me.

Oh sorry, might have looked at the wrong thing

Yeah, sorry I didn't see the scaling of the axes

@LorenzMeier @Zefz I think you have a problem with the position controller. Why does it give you a constant velocity setpoint of -1? Actually the sign should be different.

@tumbili Can you try to fly the position_controller_inav with any of the attitude estimators and see if your Iris quad behaves properly?
I can run another longer test to collect more data.

@Zefz Yes, just flashed latest master, did calibrations and just heard my charger beeping to say that battery is full :-)

@Zefz Just flew with INAV enabled, no problems at all? Are you flying the latest master?

Completely Independent of how the Position Controller operates rate limiting is not working, or it is applied after logging. This issue is about fixing this, so please focus the discussion / effort here on it. @Zefz flight performance is an entirely different topic and there are certainly usage problems involved.

@LorenzMeier I don't fully understand what is wrong with the rates. Where do you see any violation?

@tumbili have you inspected the rate limiting? Why are we seeing the spikes in @Zefz log?

There are spikes but what do they have to do with rate limiting?

Maybe we are talking of different things

actually at 360 dps -4 rad/s is possible. The question is if 360 dps is the right rate limit as default. Maybe we should apply a tighter limit?

No, the problem is something else. Why is there a spike in the roll_rate_sp? There is not huge attitude error.

There is also a huge spike in the pitch setpoint

Yes, those spikes are what I'm trying to hunt down. Do they happen in your flight log as well?

No

And I see that attitude setpoint quaternions are not logged, probably the new estimator does not log yet.

Because that is the relevant thing to look at.

Just fixing that

Ah, I had that mistaken. Ok, I see that the quaternion setpoint is generally not logged.

Here is another log showing the same problem. It enters PosHold first and AltHold the second time.
It seems the attitude spike setpoints only happen on the first initial mode change into a flight assisted mode. Curiously this did not seem to happen without GPS (AltHold only). Maybe this is a problem in the mc position controller?

@Zefz @LorenzMeier A possible cause for the spike seem to be the desired acceleration in y direction of the position controller. If you plot it in flight plot you can see it very nicely. I just haven't understood yet where this spike comes from.

@Zefz @LorenzMeier One cause I see is that the mc_pos_controller does not reset it's D part.

It looks to me as though RC inputs are commanding the spikes at around 43.5 seconds. Am I looking at the wrong event?

@kd0aij I'm looking at t == 16 seconds

will do a quick POSCTL check with Q estimator

@kd0aij Just a second, can you use the PR I will do in 10 seconds?

OK

checked out branch mc_pos_D_reset. flashing now

very short flight; battery low. But it appeared to start toilet-bowling immediately on entering POSCTL.
Looks like mag calibration problems again.

@kd0aij Could you show the log please?

@kd0aij I did a param reset today with my IRIS and flew position control mode. Everything worked fine.
That's why I'm really surprised.

http://dash.oznet.ch/view/9vTwVDUV88TTTkQE8GGBJS
Toilet bowling strong about 8 seconds after entering posctl

Interestingly, no problem with Flow: http://dash.oznet.ch/view/8bYbgkFh8DzR3stnTEKgNU
Back to GPS, and posctl is still no good: http://dash.oznet.ch/view/6hPRkZutbLuWfUAMTQZreE

@kd0aij Thrust and magnetic field are correlated in your case:
http://dash.oznet.ch/view/6hPRkZutbLuWfUAMTQZreE#Thrust_PLOT
The overall vector orientation is different between power-off and power on (look at the takeoff sequence):
http://dash.oznet.ch/view/6hPRkZutbLuWfUAMTQZreE#IMU_Mag_PLOT
To me it looks marginal - it might just work or just not work, very hard to tell. It would certainly be enough to explain toilet-bowling, but it its not as strong as I could definitely pinpoint it as the source.

And in your last log with GPS, your roll / pitch tracking is horrible:
http://dash.oznet.ch/view/6hPRkZutbLuWfUAMTQZreE#A_PitchRate_PLOT
This is your primary issue. As long as that is not resolved this quad will continue to raise false positives in terms of performance. You really, really need to re-tune it 8).

I'm closing this in favour of #2143, which likely will resolve this.

@LorenzMeier This is very interesting... How could the pitchrate tracking be so good in the flow run, and so bad on the next flight with GPS a minute later? I certainly didn't change any tuning parameters, just put the lens cap on the flow camera.

There are also suboptimal areas in the manual flight section of the flow log. Your system seems to be right at the edge of ok, but not quite there.

Any suggestions on what might be wrong with the tuning? In my opinion there
are no problems with manual flight so the required procedure is completely
unknown to me.
On Fri, May 8, 2015 at 6:34 AM, Lorenz Meier<EMAIL_ADDRESS>wrote:

There are also suboptimal areas in the manual flight section of the flow
log. Your system seems to be right at the edge of ok, but not quite there.
—
Reply to this email directly or view it on GitHub
https://github.com/PX4/Firmware/issues/2140#issuecomment-100218690.

--
Mark Whitehorn
<EMAIL_ADDRESS>

I guess this points out how valuable an auto-tuning procedure would be. It would encapsulate the knowledge which I (the user) lack and improve user experience immeasurably by eliminating crashes which currently result simply from switching from manual to posctl mode. A step in the right direction would be an auto-analysis procedure which examines a log and suggests changes to specific tuning parameters to correct problems.


Assign Roles/Permissions with Spatie Laravel Permission on Import

Laravel Version: #5.8#
Adldap2-Laravel Version: #6.0#
PHP Version: #7.1.3#
LDAP Type: ActiveDirectory

Description:
I am using the AdLDAP2-Laravel and Spatie Laravel-Permissions and I would like to know if there is a way that I can map users to specific roles/permissions upon bulk import using the import command?
Can this be done with an override?
I can't figure out what file or function I should be looking at.

Hi @kellerisddev,
This is absolutely possible. I would use an event listener and listen on the Adldap\Laravel\Events\Synchronized event, as this event includes the saved Laravel database model and your LDAP user model:
<?php

namespace App\Listeners;

use App\Role;
use Adldap\Laravel\Events\Synchronized;

class AssignUserRoles
{
    /**
     * Handle the event.
     *
     * @param Synchronized $event
     *
     * @return void
     */
    public function handle(Synchronized $event)
    {
        if ($this->user->inGroup('Administrators') {
            $adminRole = Role::firstOrFail(['name' => 'administrator']);

            $this->model->roles()->attach($adminRole);
        }
    }
}

You'll definitely want to modify the above listener for you own use, but it should get you started!

Hi Steve,
I am just now following up on this and I have never used Event Listeners in Laravel before.  I have implemented the following in a Listener called ADSyncRoles
I ran the command php artisan make:listener and named it  ADSyncRoles
`
namespace App\Listeners;
use App\AdRole;
use Illuminate\Support\Facades\Log;
use Spatie\Permission\Models\Role;
use Spatie\Permission\Models\Permission;
use Adldap\Laravel\Events\Synchronized;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
class ADSyncRoles
{
public function handle(Synchonrized $event)
{
    Log::info("User '{$event->user->getCommonName()}' is being synced with Laravel.");
}

}
`
I have also added the following to my EventServiceProvider.php file:
  protected $listen = [              'Adldap\Laravel\Events\Imported' => [             'App\Listeners\ADSyncRoles',         ],           ];
Now when I run php artisan adldap:import from the command line I do not see anything logging.
Am I missing something

Nevermind, I wasn't passing the filter to the console command on import.  Working now. Thanks


Initialization/warmstarting for RoBERTa pretraining

I am currently trying to further pretrain a RoBERTa model on a custom dataset, initializing the model with roberta-base weights. I am using this script which works fine for pretraining from scratch. The function load_training_checkpoint allows to resume training from an existing deepspeed checkpoint but I haven't found an easy way to initialize the pretraining with weights not obtained through deepspeed training (e.g. roberta-base weights). I have looked at the docs and I tried to set the load_module_only argument to True but I get a TypeError:
TypeError: load_checkpoint() got an unexpected keyword argument 'load_module_only'
Could you please help me on this? Is there any easy way to do warmstarting with DeepSpeed?
I am using deepspeed==0.4.3 and transformers==4.4.0.

Did you solve this by any chance?

@malteos, sorry for the delayed response. Can you please confirm that this problem exists with latest deepspeed? Please also share a stack trace. Thanks!

Thanks for the reply. The issue was due to Megatron/HF and not DS related but it is solved now. See the discussion at https://github.com/bigscience-workshop/Megatron-DeepSpeed/issues/229


faceid does not pop on pixel 7pro (Android)

Hi,
FaceId popup does not appear on pixel 7 pro.
I first check for biometrics and then try to save using biometrics.
try {
String key = 'pwdkey';
String secret = '1111';
await FlutterLocker.save(
SaveSecretRequest(
key: key,
secret: secret,
androidPrompt: AndroidPrompt(
title: authPrompt.title,
cancelLabel: "Cancel",
descriptionLabel: authPrompt.description)),
);
return true;
} on Exception catch (exception) {
return false;
}

The underlying Android library only uses strong authentication. Face recognition on that phone is just a plain camera and can not be considered strong, it can be easily proved false-positive with a photo of a person.
For strong face authentication, you need to have a few more sensors (like the NIR sensor) that iPhone has. The only Android that has that is Pixel 4.


chore: format number for delegators count

Delegators count should be formatted like 123,456 instead of 123456

Fixed in https://github.com/snapshot-labs/sx-ui/commit/c14bd127a62e126823d0171873d56e8c5cdb0c4a


Request . PicoStill Support

I know there is probably not too many Picostill users out there.  But this would be great to implement.
When starting up the Picostill when connected tot he server It gets all the way until right before it sets up the Picostill then gives Sever error 7.
It sees the mac address of the picostill and lets me select it. So it must be looking for some instructions from the server.
I just hooked it back up to picobrews servers and off it went and started going.
Any assistance That I can give to help I would gladly do with my limited skill level.

I think Trevor (@tmack8001) is getting a picostill soon so he should be able to capture data for any needed support

I did just receive a brand new still this past weekend. Priority so far has been to get the Z support up and running so I go kiss PB goodbye forever.
Once that gets completed next few days I'll check the logs for the Still.
On those lines @chiefwigms adding a flask filter to dump the request payload (method, uri and body only) would be amazing addition for collecting user feedback when things go wrong.
Likely we would want to push that to say a debug-log file or toggle it somehow via the UI. Likely a per session debug-log attached to each session would be most ideal. This is the only way I think we will over time collect error states and understand their meaning.

great!.  I am in no hurry, just would like my picostill to be saved from the bin as well.
I really make easy and tasty rum.

Rum... Yum (I haven't even explored what or how to even use this... For "citrus extraction").
We should talk "privately" to share best practices and tips on T1 and suction.

I will (hopefully, finally) have my Z up and running this week. I will then be able to get my Picostill set up. If you haven't already gotten that far, Trevor, I'll see what I can contribute.

Sounds good @peterloron now that most aren't having issues I should get some focus time to get the still requests mapped out and functioning this week with the server.

@msav72 and @peterloron I've intercepted the initial "check firmware" request along with the latest firmware binary for inclusion here.
The ZSeries also has a "enabled logging" feature which seems to register the device to the Z's associated Picobrew account. Though without explicitly enabling that in "settings" I didn't see that be sent from the device (I'll test more throughout the weekend, but in 10 minutes tomorrow morning I can likely get the firmware requests supported).

This weekend I added endpoints to support a PicoStill working with a Pico C. I now have the still working on my home network and equipment. Note that it doesn't appear to send log data back to picobrew like the other processes (likely for legal reasons). So no graphical capabilities. But essentially there's a gate api request to enable the picostill.
I have a branch I created with the work but can't push it up to this repo due to permissions. If you want to grant me access I can push it and open a PR. If there's another approach you'd prefer let me know.

@troyef for legal reasons the still never sent data back to picobrew, though there is an added setting in the ZSeries devices for enabling logging of data... that is what I'm working on right now to get Z support mapped out.

FYI.  the picostill has it's own Web interface. once you find out the picostill ip address just put it into a web browser and there is info direct from the still.

@msav72 yeah and with the Z some of these values get pushed to a "brew session" if you toggle on that feature. This ideally brings most if not all data into a single UI for consumption, but yes the Still also has an embedded webserver itself

Got the Z+Still mapped and running a distillate of simply water today to make sure everything is working as expected over a several hour distillate session.
Note this level of logging for PicoStill sessions is only possible with a ZSeries device. I have some thoughts and exploring ideas on how to get this level of logging and more from any Picobrew device.... but that will take time and is less priority than the server setup, configuration and device coverage work.

It could also be useful to look up the IP for the picostill (if possible) and put a link on the server homepage. Just to make it easier to access. I suspect the Pico saves it in RAM somewhere to facilitate communication...

@troyef could even just have an option to have an included iframe of the embedded server page. The Picostill upon bootup communicates to the python webserver anyways. If we say had a registry of all "registered devices" (those that have started their boot up sequences on the offline server) we easily have their IP addresses (client ip) due to the network requests made from them.
I'm almost confident that the Z is making a request to the PicoStill via an API somehow, not sure how the Z would get the PicoStill's IP address as that isn't communicated to the Z over the www.picobrew.com requests.

Is the picostill in the current docker image.
I just pulled it down and copied over my recipes. and copied over my config.yaml. But i did not see any files specific to the picostill in there.
Maybe the is not any Picostill related config files.

@msav72 once the kids go to bed I'll push the latest docker image. Sorry I didn't do that this morning.
Also will push up changes to the repo to automatically publish the docker image to tag "latest" upon merging or pushing to the master branch.

is there a way to set my docker image to update automatically.
will have have to copy my recipes, and config.yaml file back after each update.
I had to reinstall docker on my Western digital cause I accidentally broke the bridge network that portainer was using.  It was faster to reinstall then go mucking around in command line trying to figure out how to recreate it.

thanks @chiefwigms for the quick docker push, I have a github action I tested with my own namesspace in docker hub that will make this a thing of the past 😜
https://github.com/chiefwigms/picobrew_pico/pull/72/files
I will also look at making the UI action to "upgrade and restart" to be able to do that from within docker as well, think it just involves changing the file structure around a bit to be similar to what we do with raspberry pi.

@msav72 the new docker images are continually updated upon every merge to master. The sources in the image aren't updated while the container is running as to keep them consistently the same as what was built.
You simply "pull" them to update the image running. You should setup volume mounts for recipes, sessions, etc allowing you to keep them stored elsewhere as they shouldn't be stored on the container itself.


Wrong filename is passed to transform function (jadeify transform fails).

Hi!
I want a simple configuration: require jadeify-ed jade templates in my clientside js code.
In order to get this I've tried to use jadeify transform, which works perfectly in the command line (browserify -t jadeify app.js) with require('template.jade') in app.js.
Buy trying to make it work with gulp-browserify I've found a strange error and cannot guess where actually does it come from.
Trying to use simple transform jadeify in my gulpfile.js:
gulp.task('js', function() {
    gulp.src('client/app.js')
        .pipe(browserify({
            transform: ['jadeify']
        }))
        .pipe(gulp.dest('static'))
});

Jadeify is installed and perfectly require-d, but fails because it gets wrong file name fake_XXXXXX.js instead of template.jade. I've crawled the sources trying to find a fix, but could find nothing.
Maybe module-deps creates such strange filenames?

hey @sogko, I have read your nice article, https://medium.com/@sogko/gulp-browserify-the-gulp-y-way-bb359b3f9623 and understand streams and buffers and gulp a lot better now .. BUT I still cannot get jadeify to work. I placed the whole code (above) into a new clean gulp project, and I get the error:: Error: write after end
If i remove the line .transform(jadeify) then the build works - but obvs thats no good to any of us.
Please give me some insight!

I found a post where by removing .transform(jadeify) and by putting this in your project.json file instead:
"browserify": {   "transform": [     "jadeify"   ] }
Does seem to work - but why. I dont know.


fix(seed): Add more accurate tests

Pre-Submission Checklist

[ ] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #15726
Description
I added two more regex assertions.
Firstly, data must be stored into the previously declared variable html at some point.
Secondly, it checks whether an opening and closing strong tag can be found with some content in it

@BerkeleyTrue if merged, are we likely to push this to the production server?

No, production is on a feature freeze. According to the issue, this change has already been made to staging so this PR/issue are no longer needed. @ahmadabdolsaheb apologies.
Happy Coding


'cannot load such file -- cucumber/formatter/hook_query_visitor' getting for reportal portal

Hi,
I am facing 'cannot load such file -- cucumber/formatter/hook_query_visitor' error while trying to use agent-ruby.
cannot load such file -- cucumber/formatter/hook_query_visitor
Error creating formatter: ReportPortal::Cucumber::Formatter (LoadError)
C:/Ruby26/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in require' C:/Ruby26/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in require'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/reportportal-0.7/lib/report_portal/cucumber/report.rb:20:in <top (required)>' C:/Ruby26/lib/ruby/gems/2.6.0/gems/reportportal-0.7/lib/report_portal/cucumber/formatter.rb:21:in require_relative'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/reportportal-0.7/lib/report_portal/cucumber/formatter.rb:21:in <top (required)>' C:/Ruby26/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in require'
C:/Ruby26/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in require' C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/constantize.rb:19:in rescue in constantize'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/constantize.rb:8:in constantize' C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/configuration.rb:215:in formatter_class'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/configuration.rb:201:in block in formatter_factories' C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/configuration.rb:199:in map'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/configuration.rb:199:in formatter_factories' C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/runtime.rb:187:in formatters'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/runtime.rb:172:in report' C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/runtime.rb:76:in run!'
C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/lib/cucumber/cli/main.rb:29:in execute!' C:/Ruby26/lib/ruby/gems/2.6.0/gems/cucumber-4.1.0/bin/cucumber:9:in <top (required)>'
C:/Ruby26/bin/cucumber:23:in load' C:/Ruby26/bin/cucumber:23:in '
environment details
ruby -2.6
latest reprotportal with docker.
Please help me with it to resolve
Thank you

Yeah, the gem wasn't updated for Cucumber 4. But I don't have time to support it.

@radhakrishnanakireddy I've added support for cucumber > 4 in to a branch at https://github.com/pmthexton/agent-ruby/tree/cucumber4
I'm not convinced this is the cleanest or most correct way of doing so, but if your focus on it simply "working", then it should be good enough to see you through.
Note: I've only done this for cucumber, I've not paid any attention to parallel cucumber or rspec as I didn't need to worry about them for my use case.

Is reportportal support cucumber 6.0.0?
We are using the ruby with BDD.
I'm getting error like below
cannot load such file -- http
Error creating formatter: ReportPortal::Cucumber::Formatter (LoadError)

@pmthexton I have inserted     gem 'reportportal', git: 'https://github.com/pmthexton/agent-ruby.git', branch: 'cucumber4' in my Gemfile to use your fix for Cucumber > 4, but I still get the same error mentioned here. Care to shed some light here?


[WIP] fix: relpath test correctly handles different OS separator

Test was failing on Windows VM causing all PRs to fail
Resolves #185

Hey devs, there are more tests failing due to the path separator character. But I am starting to wonder if this code is used to create the relative browser URLs. If that's true, then we should use the slash character rather than use the File.separator character based on OS.
Thoughts?

May need to setup on Windows gag

Update: yes this fails because the test compares the xml aggregated name based on MD5 against a static file. I do believe this should be the generic forward-slash for web consumption. Will implement in this way then confirm it works on  Windows machine.

#200 Supersedes this PR. Closing this one.


Migrate to cobra CLI

We intend to migrate to the cobra cli from urfave/cli because the
project is more well maintained.  There are also some technical reasons
as well which extend into our remote client work.
Signed-off-by: baude<EMAIL_ADDRESS>

This PR is not ready for review yet.  I'm first trying to see if we can pas integration testing with what we have.  Next I will need to conduct a majorly painful rebase.

This is ready for review while I try to convince make vendor and the integrations tests that we are cool

tested with rootless containers, and it seems to work

Great work, @baude! make vendor seems happy now :+1:

LGTM

LGTM too, I'm sure there'll be a few things that shake out from this, but I say ship this now and fix any malingering issues later.
Really, really nice job here @baude.

/lgtm


feat(wmg): gene select refit and add more functionality

Reviewers
Functional: @tihuan
Readability: @Bento007

Changes

add

Add ability to paste comma separated genes
Add SDS MenuSelect component
Add custom virtualization for gene list

https://user-images.githubusercontent.com/8716829/154753078-98f3ce4a-a297-43c0-a2e1-00e036cbf688.mov

Known Issues:

The ability to paste genes in isn't advertised at the moment.  It will be added as an input placeholder once chanzuckerberg/sci-components#121 is addressed.
A loading bar is shown on paste enter even if no genes are valid

@seve resolved! I think somehow czifui wasn't upgraded before, so I just pushed a commit to do that along with type fixes! PTAL again thank you 😊

@tihuan lgtm! Turning on auto-merge!


Remove Webjobs.Script.Extensibility  dll and nuget package

With BYOB, all extensibility should go through the public WebJobs SDK interfaces and we shouldn't need ScriptBinding classes anymore. Remove all ScriptBinding classes and the Webjobs.Script.Extensibility dll completely.
This is still used for some internal grandfathered bindings.  Even while there are still scriptbinding classes, we should be able to remove the nuget package since this is now entirely internal and use the project reference.

See https://github.com/Azure/azure-webjobs-sdk-extensions/commit/9eda3e2308c1aaf98cf70e0c6aaf8730d45f7668 for an example of doing this for SendGrid.
Steps to do this:

Add a new [Binding] attribute on your attribute.
Use the new fluent interfaces on ExtensionConfigContext. Only BindToInput, BindToCollector are supported.
In your extension's initialize method, call Apply() to set the config.
Make sure your binding supports JObject conversions so it can be called from Node.

Nuget project is removed with https://github.com/Azure/azure-webjobs-sdk-script/commit/bd63b0b02e3e70bd54a90805ff1a3e0962c3dc43

Any other work remaining for this task? Or are we good to close this as completed?

The previous fix got rid of the nuget package and demoted this to be internal-only. But we should remove the entire project and ScriptBindingProvider* classes.


vue-cli-service builds successfully even when there are errors

Version
4.5.9
Reproduction link
https://github.com/robinzimmermann/vue-build-issue-1
Environment info
Environment Info:

  System:
    OS: macOS 11.0.1
    CPU: (8) x64 Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
  Binaries:
    Node: 10.18.1 - ~/.nvm/versions/node/v10.18.1/bin/node
    Yarn: Not Found
    npm: 6.13.4 - ~/.nvm/versions/node/v10.18.1/bin/npm
  Browsers:
    Chrome: 87.0.4280.88
    Edge: Not Found
    Firefox: 82.0.3
    Safari: 14.0.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.0-rc.2
    @vue/babel-plugin-jsx:  1.0.0-rc.3
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.9
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.9
    @vue/cli-plugin-babel: ~4.5.0 => 4.5.9
    @vue/cli-plugin-eslint: ~4.5.0 => 4.5.9
    @vue/cli-plugin-router: ~4.5.0 => 4.5.9
    @vue/cli-plugin-typescript: ~4.5.0 => 4.5.9
    @vue/cli-plugin-unit-jest: ~4.5.0 => 4.5.9
    @vue/cli-plugin-vuex: ~4.5.0 => 4.5.9
    @vue/cli-service: ~4.5.0 => 4.5.9
    @vue/cli-shared-utils:  4.5.9
    @vue/compiler-core:  3.0.4
    @vue/compiler-dom:  3.0.4
    @vue/compiler-sfc: ^3.0.0 => 3.0.4
    @vue/compiler-ssr:  3.0.4
    @vue/component-compiler-utils:  3.2.0
    @vue/eslint-config-prettier: ^6.0.0 => 6.0.0
    @vue/eslint-config-typescript: ^5.0.2 => 5.1.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/reactivity:  3.0.4
    @vue/runtime-core:  3.0.4
    @vue/runtime-dom:  3.0.4
    @vue/shared:  3.0.4
    @vue/test-utils: ^2.0.0-0 => 2.0.0-beta.12
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^7.0.0-0 => 7.1.0
    jest-serializer-vue:  2.0.2
    typescript: ~3.9.3 => 3.9.7
    vue: ^3.0.0 => 3.0.4
    vue-eslint-parser:  7.2.0
    vue-hot-reload-api:  2.3.4
    vue-jest: ^5.0.0-0 => 5.0.0-alpha.7 (3.0.7)
    vue-loader:  15.9.5 (16.1.0)
    vue-router: ^4.0.0-0 => 4.0.0-rc.6
    vue-style-loader:  4.1.2
    vue-template-es2015-compiler:  1.9.1
    vuex: ^4.0.0-0 => 4.0.0-rc.2
  npmGlobalPackages:
    @vue/cli: 4.5.9

Steps to reproduce

Check out the repo the reproduces: https://github.com/robinzimmermann/vue-build-issue-1

From the command line, build for production:
$ npm run build

The build fails, as expected.

Now immediately run the command again:
$ npm run build

The build succeeds, and no error is reported.

FYI That repo was just a basic creation using vue-cli with the following modifications:

Create a new project:
$ vue create hello-world

Here are the options I chose (from my ~/.vuerc file):
{
  "useTaobaoRegistry": false,
  "presets": {
    "base-01": {
      "useConfigFiles": true,
      "plugins": {
        "@vue/cli-plugin-babel": {},
        "@vue/cli-plugin-typescript": {
          "classComponent": false,
          "useTsWithBabel": true
        },
        "@vue/cli-plugin-router": {
          "historyMode": true
        },
        "@vue/cli-plugin-vuex": {},
        "@vue/cli-plugin-eslint": {
          "config": "prettier",
          "lintOn": [
            "save"
          ]
        },
        "@vue/cli-plugin-unit-jest": {}
      },
      "vueVersion": "3",
      "cssPreprocessor": "dart-sass"
    }
  }
}

Edit .eslintrc.js, in the rules section, change:
"no-console": process.env.NODE_ENV === "production" ? "warn" : "off"

to:
"no-console": process.env.NODE_ENV === "production" ? "error" : "off"

i.e. linting should error out if you have console.log in your app.

Edit src/main.ts and add a console.log statement:
...
console.log("Here we go!");

createApp(App)
  .use(store)
  .use(router)
  .mount("#app");

What is expected?
The second time the build is run, it should have failed.
The conditions are the same as the first run, and the console.log "error" is still present, so it should have failed.
What is actually happening?
The first time you run a build, it fails as expected.
But subsequent runs build, when they should fail.
NOTE: If you save src/main.js and build again, then the build fails.

We need to be able to rely on the build failing if the project has errors.
If this is indeed a bug, and not a user error, then I would consider it a serious problem as  it would be bad to successfully build when the project has errors.

duplicate of #3065, it will be fixed after replacing eslint-loader by eslint-webpack-plugin

Close via #6094

Problem is still there. Even after updating all vue-cli project dependencies. Running vue-cli-service lint --no-fix && vue-cli-service serve helps, but this is not the mot performant way, since it is running the linter twice now.

Agreed with @BenediktZoller, the issue is still there.


Put object support content encoding header

Put object support content encoding header

Thanks for your PR firstly.
This code is generated and should not be modified manually, please send a PR to https://github.com/yunify/qingstor-api-specs, and add this header into file like this: https://github.com/yunify/qingstor-api-specs/blob/master/2016-01-06/swagger/object.json#L38-L43


Offscreen canvas issues

Still not quite there; uses of document without checking for its existence first e.g.
effect.js:133 Uncaught ReferenceError: document is not defined
    at new Effect (effect.js:133)
    at Engine.ThinEngine.createEffect (thinEngine.js:1664)
    at ShaderMaterial.isReady (shaderMaterial.js:463)
    at Mesh.render (mesh.js:1508)
    at SubMesh.render (subMesh.js:281)
    at RenderingGroup.renderUnsorted (renderingGroup.js:208)
    at RenderingGroup.render (renderingGroup.js:109)
    at RenderingManager.render (renderingManager.js:91)
    at RenderTargetTexture.renderToTarget (renderTargetTexture.js:706)
    at RenderTargetTexture.render (renderTargetTexture.js:630)

 else if (baseName.vertexElement) {
  vertexSource = document.getElementById(baseName.vertexElement);  // <--- error
  if (!vertexSource) {
    vertexSource = baseName.vertexElement;
}

Shimming round it by adding to self
.document = {
    getElementById: (id) => null
}

Seems to be only issue

Will fix that asap! thanks for reporting


Merge into master for 0.5.0 release.

Merging in all the changes on devel to master for the 0.5.0 release of OpenGHG. See (CHANGELOG.md)[https://github.com/openghg/openghg/blob/devel/CHANGELOG.md] for the big changes in this release.

Codecov Report

Merging #603 (41018c4) into master (90c93c7) will decrease coverage by 45.41%.
The diff coverage is 0.00%.

:exclamation: Current head 41018c4 differs from pull request most recent head fa942c2. Consider uploading reports for the commit fa942c2 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##           master     #603       +/-   ##
===========================================
- Coverage   78.27%   32.87%   -45.41%
===========================================
  Files         170      172        +2
  Lines       12551    13106      +555
===========================================
- Hits         9824     4308     -5516
- Misses       2727     8798     +6071

Impacted Files
Coverage Δ

openghg/__init__.py
0.00% <0.00%> (-94.45%)
:arrow_down:

openghg/_version.py
0.00% <0.00%> (-41.50%)
:arrow_down:

openghg/analyse/_scenario.py
0.00% <0.00%> (-76.49%)
:arrow_down:

openghg/dataobjects/__init__.py
0.00% <ø> (-100.00%)
:arrow_down:

openghg/dataobjects/_datahandler.py
0.00% <0.00%> (-88.70%)
:arrow_down:

openghg/dataobjects/_obsdata.py
0.00% <0.00%> (-46.43%)
:arrow_down:

openghg/objectstore/_local_store.py
0.00% <0.00%> (-60.00%)
:arrow_down:

openghg/retrieve/_access.py
0.00% <0.00%> (-77.15%)
:arrow_down:

openghg/retrieve/_search.py
0.00% <ø> (-81.45%)
:arrow_down:

openghg/retrieve/ceda/_retrieve.py
0.00% <0.00%> (-77.11%)
:arrow_down:

... and 91 more

... and 42 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat: add build-started and build-finished events

This PR contains a:

[ ] bugfix
[x] new feature
[ ] code refactor
[x] test update
[ ] typo fix
[ ] metadata update

Motivation / Use-Case
Users have requested events to be notified when a build starts and ends.
Breaking Changes
None
Additional Info

Can I apply plugins to the compiler on 'build-start', or should It be done on "before-build-start"?
I'm asking because that way I could change webpack-serve-waitpage to apply the ProgressPlugin on it's own without asking the developer to do it.


Gstreamer RTSP Docs Update

Hoping this help others avoid hours of frustration.
Issue #, if available:
#193
Description of changes:
As noted in the helpful but well hidden issue comment https://github.com/awslabs/amazon-kinesis-video-streams-producer-sdk-cpp/issues/193#issuecomment-474093882, the Gstreamer examples for RTSP do not run at all.  I'm no Gstreamer expert but using h264parse works perfectly, while video/x-h264, format=avc,alignment=au just causes the pipeline to hang.
This is just a documentation update.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Removed the duplicate h264parse element, that was a typo.
I've learned a bit more since I first posted this. For example, either of these work on my test Raspberry pi running v4l2rtspserver:
gst-launch-1.0 rtspsrc location="rtsp://somehost:8554/somestream" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="delete-me-test"
gst-launch-1.0 rtspsrc location="rtsp://somehost:8554/somestream" short-header=TRUE ! rtph264depay ! h264parse ! kvssink stream-name="delete-me-test"
But if I remove h264parse, the pipeline hangs, due to kvssink caps not accepting the pipeline data.

Removed the duplicate h264parse element, that was a typo.
I've learned a bit more since I first posted this. For example, either of these work on my test Raspberry pi running v4l2rtspserver:
gst-launch-1.0 rtspsrc location="rtsp://somehost:8554/somestream" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="delete-me-test"
gst-launch-1.0 rtspsrc location="rtsp://somehost:8554/somestream" short-header=TRUE ! rtph264depay ! h264parse ! kvssink stream-name="delete-me-test"
But if I remove h264parse, the pipeline hangs, due to kvssink caps not accepting the pipeline data.

Yep the capsfilter is not necessary but the h264parse element is.  Thank you for this change I'm sure it will be helpful to others I've seen others hit this issue many times in the past.

Removed the duplicate h264parse element, that was a typo.
I've learned a bit more since I first posted this. For example, either of these work on my test Raspberry pi running v4l2rtspserver:
gst-launch-1.0 rtspsrc location="rtsp://somehost:8554/somestream" short-header=TRUE ! rtph264depay ! h264parse ! video/x-h264, format=avc,alignment=au ! kvssink stream-name="delete-me-test"
gst-launch-1.0 rtspsrc location="rtsp://somehost:8554/somestream" short-header=TRUE ! rtph264depay ! h264parse ! kvssink stream-name="delete-me-test"
But if I remove h264parse, the pipeline hangs, due to kvssink caps not accepting the pipeline data.

Yep the capsfilter is not necessary but the h264parse element is. Thank you for this change I'm sure it will be helpful to others I've seen others hit this issue many times in the past.

@vattay Just wanted to say there are several place where there are still duplicate h264parse elements.  Once they are removed we can push this in.

I removed the rest (hopefully), of the last remaining duplicate elements.


Demo files do not include the MIT license.

Shouldn't the demo files include the MIT license in them?

I guess so, but never thought of that. Thanks!

I did not create a pull request for this.
I am leaving this to you to address. 😄


(no bugs - just help) display one field of text but execute a command that uses another field as the argument.

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[x] Etc.
(linux & linux_android)

Shell

[x] bash
[ ] zsh
[ ] fish

No Bug! - just assistance.
First THANK YOU! fzf is amazing!
Can I have fzf display one field of text but execute a command (on <ENTER>) that uses another field (on the same line) as the argument?
Example:
I have a function, it outputs all the info I need to a file, that file looks kinda like this:
Title :: /A/Directory/A/File
Title2 :: /Another/Directory/File

Now I can either:
# get title:
cat $file | awk -F' :: ' '{print $1}'
# get directory:
cat $file | awk -F' :: ' '{print $2}'
# or assign values for each field:
title=$(cat $file | awk -F' :: ' '{print $1}')
directory=$(cat $file | awk -F' :: ' '{print $2}')

I would like to display only the "title" in fzf for people to select, but return each lines "directory" instead as the argument for my command. Lets say this is my command:
nvim $(bat $file | awk -F' :: ' '{print $1}' | fzf)

This displays all of the first field (the "titles") - perfect!
When I press enter (obviously) the argument to nvim is "title" but I would like this to be the line's second field that isnt being shown ("directory") as the argument to nvim.
Is this possible? better yet, can I supply fzf with the whole line instead Title :: /A/Directory/A/File and have it display field one only but use field 2 (the "directory") as the argument on pressing <ENTER>?
Or would --execute be best here used instead?
Sorry, you must be busy without me, but after a few hours or research I'm stuck still.
Thank you again, it really is appreciated, the more I learn of fzf's capabilities, the more I find myself integrating it everywhere!

If file paths don't contain any spaces, it's pretty simple.
echo -e 'Title :: /A/Directory/A/File\nTitle2 :: /Another/Directory/File' |
  fzf --with-nth=1..-3 --bind 'ctrl-x:execute:less {-1}' | awk -F' :: ' '{print $2}'

But if they do, you need to set --delimiter option as well.
echo -e 'Title :: /A/Directory/A/File\nTitle2 :: /Another/Directory/File' |
  fzf --delimiter=' :: ' --with-nth=1 --bind 'ctrl-x:execute:less {-1}' | awk -F' :: ' '{print $2}'

But the problem here is that fzf will print the delimiter as well (> Title ::) which is probably not what you want. A simple solution would be to use tab character as the delimiter.
echo -e 'Title\t/A/Directory/A/File\nTitle2\t/Another/Directory/File' |
  fzf --with-nth=1 --bind 'ctrl-x:execute:less {2}' | awk -F'\t' '{print $2}'


[web-components]: upgrade Storybook to v7

Upgrade @carbon/ibmdotcom-web-components to Storybook 7 + Vite

Dupe of #11537


chore: Add additional focus-visible mixin to support "fake" focus

Issue #, if available:
Description of changes:
This allows focus-visible to be used in places where we manually override focus (e.g. because a different element is focused than the one we want to actually show the focus ring around: https://github.com/cloudscape-design/components/blob/main/src/file-upload/file-input/styles.scss#L25)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

general question for understanding, why do we want to fake the focus and what is the use-case for that? does this cause any a11y issues?

For example in the file upload component, there is a hidden "real" file upload input that we want to receive focus, but we visually hide so we can render a Cloudscape button. The focus outline therefore should go around the button not the real upload input.


Dot was not allowed before plus. Escaping was allowing slashes to be …

…present in email

SimianArmy-pull-requests #187 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » SimianArmy » SimianArmy-pull-requests #15 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » SimianArmy » SimianArmy-pull-requests #16 SUCCESS
This pull request looks good

SimianArmy-pull-requests #188 SUCCESS
This pull request looks good


Add support for Ruby 2.3

Thanks!

Released v0.0.5 https://rubygems.org/gems/latest_ruby/versions/0.0.5

Thanks 😍


User error

I am trying to build a similar model using Tensorflow 2 with a slightly different neural network. The only error I continue to encounter is in the agent's "best_move" function. It continues to provide an error stating I am comparing "float" values to "None" values. I am unsure if this is a result of my improperly building the network, and as a result I am incorrectly feeding values to the network or if this is due to me incorrectly building the agent.

Sorry for the delayed response. It might be a problem with the Tensorflow installation, since that operation calls the predict function. I tested with Tensorflow 2 and it worked as expected.