Remove save_screenshot from Lint/Debugger (revival)

This PR is a revival of PR #7853. Please see the PR #7853 description for details.
Closes #7853

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Run bundle exec rake default. It executes all tests and RuboCop for itself, and generates the documentation.

Not sure what's up with circleci. I'll merge nevertheless as changes are fine

And we still have to make this configurable at some point. :-)

It seems good to add AllowedMethods option to Lint/Debugger like Lint/RedundantSafeNavigation:
https://github.com/rubocop-hq/rubocop/blob/25c22bc3efed74092d26cadef75447f646cbbf2d/config/default.yml#L1762-L1773

@ybiquitous Yeah, exactly.

@bbatsov I've opened a new issue #8927. 👌


[Question] GetX force update

When using GetX, can we force update by calling refresh inside the GetxController?

Do you mean using the refresh()  method that inherited from ListNotifier, or the rxvar.refresh() of a reactive model class?

Thanks for the reply.
I mean the refresh() method that inherited from ListNotifier.
I have tried but it seems not update, however, with GetBuilder it does.
Thank you.

I think this is by design, refresh() method should only be worked when wrapped by GetBuilder.
Code in ListNotifier, you can see refresh() method call the _notifyUpdate, which will execute the GetStateUpdate callback.
And GetStateUpdate callback list will be added in GetBuilder class initState method, which actually is a wrapper of setState, so when you force call refresh, it will do setState for the GetBuilder stateful widget, that's it.
I am not 100% sure about this, could you please correct me? @jonataslaw
code in ListNotifier
List<GetStateUpdate?>? _updaters = <GetStateUpdate?>[];

  void _notifyUpdate() {
    for (var element in _updaters!) {
      element!();
    }
  }

  @override
  Disposer addListener(GetStateUpdate listener) {
    assert(_debugAssertNotDisposed());
    _updaters!.add(listener);
    return () => _updaters!.remove(listener);
  }

code in GetBuilder
  /// Register to listen Controller's events.
  /// It gets a reference to the remove() callback, to delete the
  /// setState "link" from the Controller.
  void _subscribeToController() {
    _remove?.call();
    _remove = (widget.id == null)
        ? controller?.addListener(
            _filter != null ? _filterUpdate : getUpdate,
          )
        : controller?.addListenerId(
            widget.id,
            _filter != null ? _filterUpdate : getUpdate,
          );
  }

  /// Experimental method to replace setState((){});
  /// Used with GetStateUpdate.
  void getUpdate() {
    if (mounted) setState(() {});
  }

I think this is by design, refresh() method should only be worked when wrapped by GetBuilder.
Code in ListNotifier, you can see refresh() method call the _notifyUpdate, which will execute the GetStateUpdate callback.
And GetStateUpdate callback list will be added in GetBuilder class initState method, which actually is a wrapper of setState, so when you force call refresh, it will do setState for the GetBuilder stateful widget, that's it.
I am not 100% sure about this, could you please correct me? @jonataslaw
code in ListNotifier
List<GetStateUpdate?>? _updaters = <GetStateUpdate?>[];

  void _notifyUpdate() {
    for (var element in _updaters!) {
      element!();
    }
  }

  @override
  Disposer addListener(GetStateUpdate listener) {
    assert(_debugAssertNotDisposed());
    _updaters!.add(listener);
    return () => _updaters!.remove(listener);
  }

code in GetBuilder
  /// Register to listen Controller's events.
  /// It gets a reference to the remove() callback, to delete the
  /// setState "link" from the Controller.
  void _subscribeToController() {
    _remove?.call();
    _remove = (widget.id == null)
        ? controller?.addListener(
            _filter != null ? _filterUpdate : getUpdate,
          )
        : controller?.addListenerId(
            widget.id,
            _filter != null ? _filterUpdate : getUpdate,
          );
  }

  /// Experimental method to replace setState((){});
  /// Used with GetStateUpdate.
  void getUpdate() {
    if (mounted) setState(() {});
  }

You're right, refresh() (predecessor to update()) will only work with GetBuilder.
@jasonlaw I think it is not a good solution to try to force the update of a reactive variable using refresh(), first because it doesn't work, and second because even though it has an GetBuilder ancestor that is updated and ends up updating the state, this is a bad solution that plays in garbage the biggest advantage of using GetX which is the construction optimization of the exact widget that was changed

Thanks for all the clarifications, I am clear now, thank you very much!


docs(structural-directives): move ng-container section later in page

This is a follow-up to https://github.com/angular/angular.io/pull/3345#issuecomment-285511144.

No changes were done to the <ng-container> section prose.
At the end of the template section I linked the "write your own structural directive" text to the "unless" directive section (because now there is <ng-container> in between the two).

@wardbell: @kapunahelewong and I discussed the section relocation, and she agrees with the change -- other edits to this guide, if any, will come in follow-up PRs.

Oups, it seems that I omitted to back propagate some copyedits. They've been added in the separate "post review" commit.

This will do for now. I'll be revisiting shortly for v.4 to cope with changes to the microsyntax and the move to <ng-template> whose implications I have not yet thought through.


error_on_line_overflow = true ignores #[rustfmt::skip]

macro_rules! test_macro {
    ($($id:ident),*) => {};
}

fn main() {
    test_macro! { one, two, three, four, five, six, seven, eight, night, ten, eleven, twelve, thirteen, fourteen, fiveteen };
    #[rustfmt::skip] test_macro! { one, two, three, four, five, six, seven, eight, night, ten, eleven, twelve, thirteen, fourteen, fiveteen };
}

when error_on_line_overflow = true I expect to get an error on the first line, but no error on the second line due to the #[rustfmt::skip] attribute, but rustfmt errors twice here.

This is fixed with #3322, I think


feat: update icons

Automated Pull Request to update icons.

You can download the apk here :
sample-debug.apk :
https://app.bitrise.io/app/62ac2962b2dd627a/build/4e10a542-5824-4fde-a939-cd98cda3174e/artifact/accc7fa987428fce/p/d844d0f4c2ed7cd4c6736f79260bda78


Move from_config/from_config_file out of HowIs::CLI

Move HowIs::CLI.new.from_config() and HowIs::CLI.new.from_config_file() to somewhere more appropriate than HowIs::CLI. Probably directly under HowIs?

This was resolved during the API overhaul.


Fix assertion in GHA tests

I noticed that on the recent release, the action_default_tests were failing asserting that the calling python was 3.10 when in fact it was 3.11 due to #667
This PR updates the assertion to 3.11

Hmm looks like Ubuntu 18.04 still defaults to 3.10?

Also, only just noticed but we only run actions_all_tests on Windows for some reason?
https://github.com/wntrblm/nox/blob/6957a4c1bf4f8f403fc30664812cbb19eb0b2417/.github/workflows/action.yml#L25


Missing check?

Hi,
I am doing some static analysis on openssl source code. I have noticed the following check in 14 files in apps directory ( e.g. dhparam.c (dhparam_main function), dsaparam.c (dsaparam_main function), ecparam.c (ecparam_main function), enc.c (enc_main function), ....]:
if (!opt_rand(o))
goto end;
But doesn't appear in apps/ocsp.c ( ocsp_main function).
Would you let me know if the check is missed or not?

ocsp doesn't have the -rand flag so the call is not there.
Basic questions like this should be posted to the mailing list; see https://mta.openssl.org for details.


Error Creating While Getting sesson.secure

/app/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221
            throw new Error('Evaluation failed: ' + helper_js_1.helper.getExceptionMessage(exceptionDetails));
                  ^

Error: Evaluation failed: TypeError: Cannot read properties of undefined (reading 'LegacyPhoneFeatures')
    at __puppeteer_evaluation_script__:13:76
    at ExecutionContext._evaluateInternal (/app/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:221:19)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ExecutionContext.evaluate (/app/node_modules/puppeteer/lib/cjs/puppeteer/common/ExecutionContext.js:110:16)
    at async Client.initialize (/app/node_modules/whatsapp-web.js/src/Client.js:267:9)

same here

You need to fix this.

Hey everyone
Note that this repostry is no longer maintained
Because i think that it's original maintainer ran away


cleanup installation process

as a developer, I want to be able to do everything only with npm.

if you could just add the documentation in the README.md that would be great


Mark contents in iframe from same origin

Hello, I am having troubles to get mark.js working  with contents in iframe from same origin.
At the moment of cration of the new Mark instance is present the iframe content but the search function does not mark its contents. Here is the plunker where is reproduced my issue. I believe to being missing something and need your help. Thanks in advance!
Steps to reproduce

visit: https://plnkr.co/edit/kbO60qEPLvZpH9BXhrZd

Environment

mark.js v8.6.0

Hi @alessiodecastro,
Thanks for submitting.
I haven't digged into the issue completely, but it seems to be a bug. To workaround the issue until I've solved it please specify iframes: true in the .unmark() method call and it'll work. The reason is, that the internal iterator instance is only created once, with the options that are available at this time. At the creation of the iterator you haven't passed any other option than "done". The iterator isn't updated with the options you've passed in the second call (.mark()).

Hi @julmot ,
thanks for the quick response and for the workaround.
Anyway, after specify the option iframes to true in the unmark call, yes it now marks the text but unfortunately is still present some bugs because the unmark does't remove the previous marks in the iframe.

Hi @alessiodecastro,
Good news. The issue is solved now in the v8.10.1 release. I can't reproduce any other issue. Here's the code I've tested with:
            var keywordInput = document.querySelector("input[name='keyword']");

            function performMark() {

            var markInstance = new Mark(document.querySelector(".context"));

                var keyword = keywordInput.value;

                markInstance.unmark({
                    iframes: true,
                    done: function () {
                        markInstance.mark(keyword, options);
                    }
                });
            };

            keywordInput.addEventListener("input", performMark);

It's necessary to unmark with iframes: true too, to always remove highlights in iframes.

Hi @julmot I think this problem still exists in v8.11.1 (tested in v8.10.1 as well).
unmark() function does not work sometimes and if acrossElements: false then marking does not work since previous marked elements still exist, else it marks on top of existing mark elements as following.
<mark data-markjs="true">
  <mark data-markjs="true">
    <mark data-markjs="true">
      <mark data-markjs="true">do</mark>
    </mark>
  </mark>
</mark>

You can reproduce this with input "dolor" using Plunker link given above (Remember to change the version and options). It works fine till 3rd letter.


[ Responsiveness ]: UI enhancement and responsiveness for Screens (About Page)

Issue Description:

UI enhancement and responsiveness for Screens (About Page)

Issue Severity:

Medium
Comment below to get yourself assigned.

Hello ma'am, I would like to work on this issue.

@shefali12-ab go ahead

@riasenpai ma'am  I am geeting this error while running the project on local machine. Please help.

@shefali12-ab  could you join the WhatsApp group https://chat.whatsapp.com/Cp57VDO5tN3BdwdUGQkHWE

@shefali12-ab could you join the WhatsApp group https://chat.whatsapp.com/Cp57VDO5tN3BdwdUGQkHWE

okay sure sir.


🐛 Bug: package-json/order-properties changes scripts keys

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Expected
It should only sort the top-level keys
Actual
It complains about key order in deeper paths as well
Additional Info
With this config
{
  "files": ["package.json"],
  "plugins": ["package-json"],
  "rules": {
    "package-json/order-properties": [
      "error",
      {
        "order": [
          "name",
          "scripts",
          "dependencies"
        ]
      }
    ],
    "package-json/sort-collections": [
      "error",
      ["dependencies", "devDependencies", "peerDependencies"]
    ]
  }
}

I'm expecting this
{
  "scripts": {
    "start": "",
    "dev": ""
  }
  "name": "",
  "dependencies": []
}

To only reorder on top-level, like this
{
  "name": "",
  "scripts": {
    "start": "",
    "dev": ""
  },
  "dependencies": []
}

But it seems to change scripts order as well
{
  "name": "",
  "scripts": {
    "dev": "",
    "start": ""
  },
  "dependencies": []
}

I'm stuck on ^0.1.5 because of this :disappointed:

👋 thanks for filing! Could you provide a little more detail please?

What is your package.json before running with --fix?
What is your package.json after running with --fix?
Why don't you want the ordering to be changed the way it is?

👋 thanks for filing! Could you provide a little more detail please?

What is your package.json before running with --fix?
What is your package.json after running with --fix?

I updated the post with more examples.

Why don't you want the ordering to be changed the way it is?

The rule package-json/order-properties is described as only re-ordering top-level keys.
But now is seem that it also acts as package-json/sort-collections even tho I'm not enabling it for scripts.

Got it! Thanks, that makes sense. Looks like this is an issue with the "order": "sort-package-json" logic added in #55. I'd defaulted it to 'standard-order' in #40 (https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/issues/31#issuecomment-1766678258).
cc @kendallgassner as FYI 👋

@all-contributors please add @andreaslindbergpaf for bug.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙

@JoshuaKGoldberg sort-package-json chooses to make it less configurable, so what method do you recommend to fix this problem?

fork sort-package-json (I can help to maintain it and keep it synced with the source)
auto-fix manually by using sort-object-keys and detect-indent

Hmm, I think the more manual strategy (2) is probably more sustainable long-term. I haven't looked deeply at which packages are best for that these days.


[Request] Generate Externs for v2

Hello, glad to hear work has begun on v2.
I'd like to request that google closure library externs are generated once v2 is complete.

Our current plan is to tackle this during either around or after our beta launch. We're thinking of writing typescript definition files, which could then be translated into closure externs via Tsickle.

Superceded by https://github.com/material-components/material-components-web/issues/43


mount a Minio bucket as a file system on VMs

Download the 'goofys' executable; and give the file executable permisions: chmod +x ./goofys
scp the file for each of the machines

For each of the VMs;
3. install the fuse package from apt-get
4. Log in, create dir '~/.aws/' and   add the minio  credentials to ~/.aws/credentials: (goofys will use the [default] profile by default:
[default]
aws_access_key_id= INSERT MINIO KEY HERE
aws_secret_access_key= INSERT MINIO SECRET ACCESS KEY HERE
5. Create a local dir. For example ( mkdir ~/minio)
6. Execute command:
./goofys --endpoint <end_point_url> <bucket_name> <local_dir_path>
./goofys --endpoint http://parrot0.phenovari-utwente.surf-hosted.nl:9091/ test ~/minio
7. The script exits with no message, to be sure check: /var/log/syslog
Test show there is some delay for the file system to be updated with the corresponding changes
in the case of uploading a file to my local mount and showing on the mount in the VM, However, the change in the Minio UI is instant.
Future update: Automation  Install , mount and unmount with Ansible

Handle through shell script mount and unmount:
==== mount====
for i in $(seq 0 3); do  echo "Execute mount $i:"; ssh -i files/parrot.key<EMAIL_ADDRESS>"./goofys --endpoint http://parrot:9091$i.phenovari-utwente.surf-hosted.nl/ test ~/minio"; done
==== unmount====
for i in $(seq 0 3); do "Execute umount $i:"; ssh -i files/parrot.key<EMAIL_ADDRESS>"sudo umount ~/minio"; done

Changes:

new minio  bucket name : datastorage
new local file system binding:  /data/local/home/parrot/minio
set 777 permissions both to folders and files :  --dir-mode 0777 --file-mode 0777
set root owner and root group : --uid 0 --gid 0
make the necessary changes from here : https://github.com/kahing/goofys/issues/93 and add -o allow_other

final command:
sudo ./goofys -o allow_other --dir-mode 0777 --file-mode 0777 --uid 0 --gid 0 --endpoint http://parrot0.phenovari-utwente.surf-hosted.nl:9091/ datastorage /data/local/home/parrot/minio


RI Utilization Policy - add fields to incident report

Description
Add scope & type to incident report of RI Utilization policy
Issues Resolved
N/A
Contribution Check List

[X] All tests pass.
[X] New functionality includes testing.
[X] New functionality has been documented in the README if applicable
[X] New functionality has been documented in CHANGELOG.MD

          1 Warning

:warning:
Should this include readme changes

  Generated by :no_entry_sign: Danger


On boarding/bmi calc

Description
Completed BMI Calculator and added it to OnBoarding page
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[X] New feature (non-breaking change which adds functionality)

Change Status

[X] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[X] Viewed what was displayed on start and interacted with component
[ ] Test B

Checklist

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] There are no merge conflicts

 On-boarding: BMI Calculator


max() and min() get weird with large integer values

On OSX with influx version 0.9 built from source
Playing around with large integer values, I got some weird results:
Adding largest signed 64-bit integer
> insert large value=9223372036854775807
> select min(value) from large
name: large
-----------
time			min
1970-01-01T00:00:00Z	-9223372036854775808

Gradually decreasing the number:
> insert large value=9223372036854775700
> select min(value) from large
name: large
-----------
time			min
1970-01-01T00:00:00Z	-9223372036854775808

Til things get even weirder:
> insert large value=922337203685477570
> select min(value) from large
name: large
-----------
time			min
1970-01-01T00:00:00Z<PHONE_NUMBER>85477632

> insert large value=922337203685477560
> select min(value) from large
name: large
-----------
time			min
1970-01-01T00:00:00Z<PHONE_NUMBER>85477504

The returned min is always off by a little.
> select * from large
name: large
-----------
time				value
2015-06-24T21:24:42.658912887Z<PHONE_NUMBER>854775807
2015-06-24T21:26:03.033411599Z<PHONE_NUMBER>854775700
2015-06-24T21:27:13.4970835Z<PHONE_NUMBER>85477570
2015-06-24T21:27:51.591725309Z<PHONE_NUMBER>85477560

I've identified why and where this bug occurs, but I don't have a fix since I'm not familiar enough with the code base. I've attached sample code to simulate the behavior.
package main

import (
	"fmt"
)

// ReduceMin/ReduceMax in influxql/functions.go shoehorns all numeric
// values into float64
func testMinimum(n int64) int64 {
	return int64(float64(n))
}

func main() {
	values := []int64{
<PHONE_NUMBER>854775807,
<PHONE_NUMBER>854775700,
<PHONE_NUMBER>85477570,
<PHONE_NUMBER>85477560,
	}
	for _, value := range values {
		fmt.Printf("%v becomes %v\n", value, testMinimum(value))
	}
}

This is the output:
9223372036854775807 becomes -9223372036854775808
9223372036854775700 becomes -9223372036854775808
922337203685477570 becomes<PHONE_NUMBER>85477632
922337203685477560 becomes<PHONE_NUMBER>85477504

This seems to be fixed in the new query engine and TSM. I'm not sure exactly where the fix came from, but this works:
Connected to http://localhost:8086 version unknown
InfluxDB shell 0.9
> create database mydb
> use mydb
Using database mydb
> insert large value=9223372036854775807
> select min(value) from large
name: large
-----------
time    min
0       9.223372036854776e+18

> insert largei value=9223372036854775807i
> select min(value) from largei
name: largei
------------
time    min
0<PHONE_NUMBER>854775807


ng4 highlight works on ngAfterViewChecked hook but not on ngAfterViewInit

Hello, for some reasons I wasn't able to highlight a code using ngAfterViewInit hook.
After few tries I was succeed with AfterViewChecked interface.
here is a code sample
if it's expected behavior, then maybe better update documentation.

BR, Max

Thanks for the update will have a look.


Schema tool for reflective schema generation.

Changes

:gift: New schema generator based on reflection and go comments.

/kind  enhancement
I found an interesting tool that @Harwayne built inside of Knative-GCP, I have cherrypicked that tool and created the start of a CLI from that code. Work in progress.
In use https://github.com/knative-sandbox/discovery/pull/153
Release Note
Adding the start of a base cli for generating schema examples in place for downstream projects.

/lgtm
/approve

/approve
we are going to start with this to get to 1.0 and then we can move to something better. This gets us close without needing to do a ton of manual labor.

/retest


[iOS Export] Check directory content before deleting old export leftovers.

Fixes https://github.com/godotengine/godot/issues/89715
Makes iOS export a bit safer. Instead of deleting previous export folders (project_name and project_name.xcodeproj, was partially broken) without any checks, exporter delete them only if most of the files in the folder match expected files for the previous export (or export option to delete unconditionally is enabled).

Thanks!


fix(ingest): fix handling of spaces in complex hive types (#6157)

This closes #6157
Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[x] Links to related issues (if applicable)
[x] Tests for the changes have been added/updated (if applicable)
[x] (Not applicable) Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[x] (Not applicable) For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Looks like lint is failing due to Optionals! Once we address we are good to merge this in :)

Hi @kirillmakhonin - Did you plan to update this PR?
Otherwise, the Acryl team will take ownership of this change.

Closing this for now. Acryl team will take it from here.
Cheers
John


[bug] MacOS Problem accessing video via tauri:// path

Describe the bug
https://user-images.githubusercontent.com/19820469/197306310-0ab1cea5-53d3-4493-a162-5c38406776fa.mp4
I'm trying to open a file index.html with a video tag. Video sample 2.5 mb
<body><video src="./video/test.mp4" autoplay muted width="640" height="480"></video></body>
Reproduction
No response
Expected behavior
No response
Platform and versions
<EMAIL_ADDRESS>tauri

tauri

Environment
› OS: Mac OS 12.6.0 X64
› Node.js: 16.17.1
› npm: 8.15.0
› pnpm: Not installed!
› yarn: Not installed!
› rustup: 1.25.1
› rustc: 1.64.0
› cargo: 1.64.0
› Rust toolchain: stable-x86_64-apple-darwin
Packages
› @tauri-apps/cli [NPM]: 1.1.1
› @tauri-apps/api [NPM]: 1.1.0
› tauri [RUST]: 1.1.1,
› tauri-build [RUST]: 1.1.1,
› tao [RUST]: 0.14.0,
› wry [RUST]: 0.21.1,
App
› build-type: bundle
› CSP: unset
› distDir: ../src
› devPath: ../src
App directory structure
├─ node_modules
├─ src-tauri
├─ .vscode
└─ src
Stack trace
No response
Additional context
No response

through asset path (asset://) works correctly.

is that video packaged inside the binary, eg exists in the dist dir? if so do you really need it to be package inside the binary?
you should use asset:// protocol if you need to play a video, because it supports streaming while tauri:// will just serve the file as whole.
For this type of files (large files especially) it is recommended to embed them as resources see https://tauri.app/v1/guides/building/resources and then use asset:// if you want to stream them

yes, I wrote that everything works if I use asset://.


Problems with Travis CI environment variables "Requirements are not satisfied."

I have problem with Travis CI integration
$ php vendor/bin/coveralls -v
Load coverage clover log:
  - /home/travis/build/Mahout/Mahout/build/artifacts/logs/clover.xml
Found 3 source files:
  - 100.00% Mahout/Request.php
  - 100.00% Mahout/Utils.php
  - 100.00% Mahout/Utils/KeySpaceConstrainedParams.php
Coverage: 100.00% (192/192)
Collect git info
Read environment variables
Requirements are not satisfied.
  - TRAVIS='true'
  - TRAVIS_JOB_ID='18683918'
  - CI_NAME='travis-ci'
  - COVERALLS_REPO_TOKEN='EEqvgAJ379f5x05BlyQo87E7oYC3kzh0t'
Set environment variables properly like the following.
For Travis users:
  - TRAVIS
  - TRAVIS_JOB_ID
For CircleCI users:
  - CIRCLECI
  - CIRCLE_BUILD_NUM
  - COVERALLS_REPO_TOKEN
For Jenkins users:
  - JENKINS_URL
  - BUILD_NUMBER
  - COVERALLS_REPO_TOKEN
From local environment:
  - COVERALLS_RUN_LOCALLY
  - COVERALLS_REPO_TOKEN
elapsed time: 0.071 sec memory: 4.25 MB

Job url: https://travis-ci.org/Mahout/Mahout/jobs/18683918
Github url: http://github.com/Mahout/Mahout/

Same issue here. For now I fixed it by adding COVERALLS_RUN_LOCALLY=1 to the travis build environment variables. Of course now the travis build numbers are ignored but I can live with that

it's just a bug. requireServiceJobId =>
return isset($this->serviceName) && isset($this->serviceJobId) && !isset($this->repoToken);

@kkamkou Thanks, I'll take a look and try to fix this

So what's the root cause here? What's the proper fix? Sorry for my ignorance, but if anyone can explain it, I will appreciate it very much!

Still getting same issue

I'm trying to figure this out after migrating from running OK on CircleCI. This is what looks fishy to me:  https://github.com/satooshi/php-coveralls/blob/c1eb3b6c25740897e35afee80780308be2e5197b/tests/Satooshi/Bundle/CoverallsV1Bundle/Collector/CiEnvVarsCollectorTest.php#L69
shouldCollectTravisProEnvVars() looks for CI_NAME, CI_JOB_ID which are environment vars that don't exist on Travis -- but if that's the issue, then I'm not sure why export CI_BUILD_NUMBER=$TRAVIS_BUILD_NUMBER fixes things.
When I set that, I'm able to submit builds but Coveralls exhibits the "random commits" syndrome that seems to indicate a missing Travis Pro build ID. That would match up with the missing CI_JOB_ID var. When I don't, I get something like a 422 "Unprocessable Entity" after submitting a successful job to Coveralls.
Currently working through variations of this in hopes of a fix:
export CI_NAME="travis-pro"
export CI_JOB_ID="$TRAVIS_BUILD_ID"
export CI_BUILD_NUMBER="$TRAVIS_BUILD_NUMBER"

My issue boils down to that when I set export CI_BUILD_NUMBER="$TRAVIS_BUILD_NUMBER" I get random commits looked up on Coverall's end of things. When I cat build/logs/coveralls-upload.json I see this is because travis-ci and not travis-pro is set as the service_name even when this is set correctly in my .coveralls.yml

@kkamkou solution worked for me too

This issue has confused me quite a bit.  My issue was that my new fancy --rootdir flag had caused my coveralls.yml to go "missing" and I hadn't separated the two problems.
The code comments say setting CI_BUILD_NUMBER is required but this is not provided by Travis. So The solution proposed works to fix the problem. I think there may be other missing variables, too. Here's what I'm using today with success:
export CI_BUILD_NUMBER="$TRAVIS_BUILD_NUMBER"
export CI_PULL_REQUEST="$TRAVIS_PULL_REQUEST"
export CI_BRANCH="$TRAVIS_BRANCH"

If you are missing a build number or PR # on Coveralls.io perhaps look into these vars further.

@buley  thanks, this solved the problem! :)
Is there a way to do this automaticly in this package!?

Should we close this, or if not, what's the proper fix?

I believe it can be closed for now.
PR: https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/3755
Travis: https://travis-ci.org/FriendsOfPHP/PHP-CS-Fixer/jobs/379818840
Coveralls: https://coveralls.io/jobs/36572092
both, PR and build number are exposed in Coveralls.


Gatlab next

I see that the sciml integration got cut in this PR. What is the plan there?

I see that the sciml integration got cut in this PR. What is the plan there?

Even though it was in a package extension, it got loaded for the tests, which made our tests run 5x slower. I think that it should just be in a separate package.

I get that testing against MTK brings in a lot of dependencies, but we could still do the @lens construction to make the ODE and then interpret it directly (by using substitution of numbers for variables and evaluation of the primitive functions) and do our own Euler's method as an example of using the package for the docs.
I tried to uncomment out the following from the Theories.Algebra module

# @theory ThAb <: ThMonoid begin
#   using ThGroup
#   using ThCMonoid
# end

# @theory ThRing <: ThSet begin
#   using ThAb: ⋅ as +, i as -, e as zero
#   using ThMonoid: ⋅ as *, e as one
#   a * (b + c) == (a * b) + (a * c) ⊣ [a,b,c]
# end

# @theory ThCRing <: ThRing begin
#   a * b == b * a ⊣ [a,b]
# end

# @theory ThRig <: ThSet begin
#   using ThCMonoid: ⋅ as +, e as zero
#   using ThMonoid: ⋅ as *, e as one
#   a * (b + c) == (a * b) + (a * c) ⊣ [a,b,c]
# end

# @theory ThCRig <: ThRig begin
#   a * b == b * a ⊣ [a,b]
# end

# @theory ThElementary <: ThCRing begin
#   sin(x) ⊣ [x]
#   cos(x) ⊣ [x]
#   tan(x) ⊣ [x]
#   exp(x) ⊣ [x]
#   sigmoid(x) ⊣ [x]
# end

but it looks like the using thing is broken. Is there an updated version of the using syntax?

I get that testing against MTK brings in a lot of dependencies, but we could still do the @lens construction to make the ODE and then interpret it directly (by using substitution of numbers for variables and evaluation of the primitive functions) and do our own Euler's method as an example of using the package for the docs.

Yeah, we should definitely do this. Gotta love the 5 line Euler's method in Julia.


Upgrade dependencies

Various dependency upgrades to latest versions for libraries we're using

Coverage increased (+0.01%) to 90.334% when pulling 09de3c4c9d5b9497e24a2c17cf592b11e8957fe5 on tgianos:upgradeDependencies into cc42971056b1900cb6f0f440d6047e700a9258ad on Netflix:master.

Codecov Report

Merging #748 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #748   +/-   ##
=========================================
  Coverage     87.26%   87.26%
  Complexity     2547     2547
=========================================
  Files           310      310
  Lines         10387    10387
  Branches        711      711
=========================================
  Hits           9064     9064
  Misses         1005     1005
  Partials        318      318

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 cc42971...09de3c4. Read the comment docs.


sov-modules: Figure out how #[query] methods should work

It is still unclear how exactly the #[query] method should work.
We need a better QueryResult type definition and analysis of how the #[query] will be called.

fixed #53


Define models without connecting to the database

We have a big problem using Bookshelf with a web application we are developing. Our customers have users that must connect to different PostgreSQL databases. Any user has its own database connection property. For example:
john -> {database : 'db1',user : 'user1',password : 'password1',host : '<IP_ADDRESS>',port : 5432}
alan -> {database : 'db2',user : 'user2',password : 'password2',host : 'localhost',port : 4000}
paul -> {database : 'db3',user : 'user3',password : 'password3',host : '<IP_ADDRESS>',port : 5432}
Users are in a SQLite database, so I have a single connection module that connect to this database and initialize the Users model. But when an application route is invoked, I have to require the PostgreSQL models (that extend a general model) based on the authenticated user connection property. Now, Bookshelf require to establish a database connection before extending their base model and defining custom models.
Is there a way to define Bookshelf models without a connection and to establish a connection later? For example, we need using Bookshelf like this:
/models/items.js
var bookshelf = require('bookshelf'),

itemsBookshelf = bookshelf(); // WITHOUT Knex instance!

itemsBookshelf.Model = itemsBookshelf.Model.extend({

    tableName : 'items',

    hasTimestamps : false,

    parse : function(attrs) {
        // Parse function code...
    },

    format : function(attrs) {
        // format function code...
    }

},
{

    browse : function(options) {
        // Browse records function code...
    }

});

module.exports = itemsBookshelf;

/routes/items.js
var express = require('express'),
knex = require('knex'),

router = express.Router();

itemsBookshelf = require('../models/items'),

Users = require('../models/users'); // Require SQLite Users model.

router.get('/',function(req,res,next) {

    var id = req.user.id; // Authenticated user ID.

    Users.getById(id).then(function(user) {

        var conn = user.get('connection'); // Get authenticated user database connection parameters as an object.

        conn.charset = 'utf8';

        var db = {
            client : 'pg',
            connection : conn,
            useNullAsDefault : true
        };

        // Connect to the database and invoke the browse() method.
        itemsBookshelf(knex(db)).browse().then(function(items) {

            res.json(items);

        }).catch(function(err) {

            res.status(400).json([]);

        });

    }).catch(Users.NotFoundError,function() {

        var err = new Error('User not found.');

        res.status(400).json(err);

    });

});

module.exports = router;

If there is no way to do this, have you planned to implement this feature or a similar feature in Bookshelf? Based on Stackoverflow questions, I know other users need a feature like this.

There has been some talk about this before, and it would be a nice side-effect if Bookshelf was converted to conform to the Data Mapper pattern, which is something that is actually a long term goal for this project. I'll leave this open as a reminder of that.


Make the document preview work with the new data model

Make the document preview work with the new data model
Cleanup, comments

#2901  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite

Merge activity

Jul 29, 12:16 PM EDT: @nickgraz started a stack merge that includes this pull request via Graphite.


Is there a method to disable all feature & recording and only stream the video?

I'm using it with frigate and I don't need camera features anymore, I only want a reliable and stable stream

There isn't a single switch, but you can disable the features one at a time.
Below the most important options:
Disable cloud - ON
Recording without Cloud - OFF
Snapshot - OFF
MQTT Enable - OFF
Motions... - OFF

Thanks, and this?

You can't disable it.
You could try with the app. It depends, in some model there is a switch to turn it on/off.

Okay thanks


test(e2e): validate that pulling from an acr registry attached to aks via --attach-acr with karpenter nodes works

Fixes #
Description
As part of the efforts to fix 1.30 bootstrap we removed a flag that removes functionality for out of tree providers. One of the side affects of this is that ACR Pull will not work in the same way. We needed a way to validate this image pull works in a reproducible and consistent way.
This test suite is that. Currently it has to be ran locally to target specific k8s versions so a nice followup at lower priority would be to add the ability to run our e2es against a specific k8s version.
How was this change tested?

make az-e2etests

[251.679 seconds]
------------------------------

Ran 1 of 1 Specs in 251.874 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
--- PASS: TestAcr (251.87s)
PASS
ok      github.com/Azure/karpenter-provider-azure/test/suites/acr       252.588s

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.701%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
36294

Relevant Lines:
37148

💛  - Coveralls

https://github.com/Azure/karpenter-provider-azure/actions/runs/10392432538/job/28777647831

Its failing remotely because the acr name passed in is wrong
cd test && CLUSTER_NAME=mc AZURE_ACR_NAME=karpenter go test
-p 1
-count 1
-timeout "3h"
-v
./suites/acr/...
--ginkgo.focus=""
--ginkgo.timeout="3h"
--ginkgo.grace-period=3m
--ginkgo.vv

cd test && CLUSTER_NAME=mc AZURE_ACR_NAME=acracr1285317475 go test
-p 1
-count 1
-timeout "3h"
-v
./suites/acr/...
--ginkgo.focus=""
--ginkgo.timeout="3h"
--ginkgo.grace-period=3m
--ginkgo.vv

https://github.com/Azure/karpenter-provider-azure/actions/runs/10503169793/job/29096028129 should pass now?

1m 55s
0s
Run goveralls -coverprofile=coverage.out -service=github
bad response status from coveralls: 405

405 Not Allowed

405 Not Allowed
nginx

Error: Process completed with exit code 1.
_--
CI test is failing due to coveralls outage. Just gonna merge as it is.


AspNetCore 1.0.2 is not compatible with AI 2.2-beta4

I upgraded my ASP.NET Core app (target net 452) to AI 2.2-beta4 and got the error
Method not found: 'Microsoft.ApplicationInsights.Extensibility.Implementation.TelemetryProcessorChainBuilder Microsoft.ApplicationInsights.Extensibility.TelemetryProcessorChainBuilderExtensions.UseAdaptiveSampling(Microsoft.ApplicationInsights.Extensibility.Implementation.TelemetryProcessorChainBuilder)'.
The above method has been removed from AI 2.2-beta4.
https://github.com/Microsoft/ApplicationInsights-dotnet/commit/30f33f698ff6c86d812189551208c11969bf3320
Here is the snippet of my project.json.
"Microsoft.ApplicationInsights.AspNetCore": "1.0.2",
"Microsoft.ApplicationInsights": "2.2.0-beta4",
"Microsoft.ApplicationInsights.Agent.Intercept": "2.0.5",
"Microsoft.ApplicationInsights.DependencyCollector": "2.2.0-beta4",
"Microsoft.ApplicationInsights.PerfCounterCollector": "2.2.0-beta4",
"Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel":  "2.2.0-beta4"

We will be updating the AI SDK for ASP.NET Core very soon.
Please be advised that it may contain a couple minor breaking changes with how the library is initialized in Startup.cs.

Anything new on this one?

Please try the new version of the SDK and report here if you experience any issues.
As mention previously there may be some minor breaking changes with code in Startup.cs.


Support multiple ads accounts on customer match

Two changes are included:

Added possibility to setup an Ads account for each Customer Match destination. This replaces the Ads account present on the Intro tab for that destination only.
Fix: customer match audience creation fails when there's a homonym list on a MCC above the target account.

TODO: after merging, the template sheet should have the "Help" tab updated accordingly.


Fix issue that caused database rename to and from saved to fail

llvm::sys::fs::rename cannot rename directories becasue it creates a file handle for the file to rename, which doesn't work for directories. Implement a custom rename function that uses MoveFileW on Windows.
Fixes https://github.com/swiftlang/sourcekit-lsp/issues/1750

@swift-ci Please test

https://github.com/swiftlang/swift/pull/77015
@swift-ci Please test Windows

For the record, llvm::sys::fs::rename tries to create a file handle for the directory using CreateFileW and that fails. From Windows documentation of CreateFileW:

Creates or opens a file or I/O device. The most commonly used I/O devices are as follows: file, file stream, directory,

To open a directory using CreateFile, specify the FILE_FLAG_BACKUP_SEMANTICS flag as part of dwFlagsAndAttributes

FILE_FLAG_BACKUP_SEMANTICS: The file is being opened or created for a backup or restore operation. The system ensures that the calling process overrides file security checks when the process has SE_BACKUP_NAME and SE_RESTORE_NAME privileges. For more information, see Changing Privileges in a Token.

So, looks like CreateFileW can open directories but it’s not really supposed to except for backup purposes and should not be the go-to solution for renaming directories.


How to add Content Middleware to a Composer bot?

Hello @neetgupta7
The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github repos are the preferred platform for submitting bug fixes and feature requests.
The only middleware supported in Composer OOB is the typing and inspection middleware. You can enable these by setting these values to true in the settings:
    "UseShowTypingMiddleware": true,
    "UseInspectionMiddleware": true,

Otherwise, you will want to use a custom runtime and modify the code to use middleware.


API changes for the Foundation

This is quite a large number of commits that implements a number of additions and changes that were requested by the Foundation. We have:

The ability optionally to use structures embedded in the Picamera2 object to configure the camera.
The ability optionally to use objects to set control values instead of dictionaries.
Some changes to allow the amount of boilerplate code to be reduced. For example, start() and start_recording() can optionally be given a camera configuration, and will configure the camera with default values if complete unconfigured. start() can also start a preview window.
Video encoders can optionally be asked to calculate bitrates and quality parameters for themselves.
There are some convenient "very high level" API functions which may suit some simple use cases for those who want to know less about what Picamera2 does ("start_and_capture_files", "start_and_record_video" etc.)

Yep, this failure is the classic "lurking request reappears when it shouldn't" problem.

I think this all looks good to merge now! Just a few thoughts, for potential future alterations:
Should we be using the libcamera functions directly, or could we abstract them e.g. with:
config = picam2.create_preview_configuration(transform=libcamera.Transform(hflip=1, vflip=1))

I wonder if the following use of an empty dictionary might be a little confusing:
capture_config = picam2.create_still_configuration(raw={})

The easy jpeg and video functions look great!  Along with the new quality parameters for video capture.
The new configuration pattern of the following looks neat too:
picam2.video_configuration.size = (800, 480)

@davidplowman  Are you ok for me to merge now?


add and test synopsis func. fix #195

Adds an editable synopsis on the case page (markdown support)
ping @guillermo-carrasco  :wink: :wine_glass:

Neat! keep bringing in more new stuff :-D Flask-Markdown.. awesome

Coverage decreased (-0.1%) to 80.857% when pulling 16811cef2e56ed51afbcc79056f08da50a4510e0 on synopsis into 7101b93f81bf94477f5243f0f502d0386dd878b3 on master.


Issue 886 - Updated LocationGroup and TimeSeriesGroup patch

Issue #886  - Updated LocationGroup and TimeSeriesGroup patch office handling to allow for assigning non-CWMS TS/locations to a CWMS-owned group

Rebased to fix build errors


Export from VSCode

First of all, I just learned about Markwhen, and it's absolutely amazing - thanks for developing it!
Small'ish issue: Currently, it is not possible to export from the VSCode extension. From the docs and #127, I can see that it should be possible to export from the app, although it might not be at the moment. Hopefully SVG export could be possible from both VSCode and the app.

+1


e621 not working

Bug description
As of some hours ago, e621.net as a source seems to have stopped working. From what I understand it seems like the upped their cloudflare security or something after the site went offline for some hours and then after coming back Grabber just doesn't seems to work anymore with it.
Steps to reproduce

Select e621.net as source
Search any tag
"Possible reason: server offline error" returned

Expected behavior
For e621 as a soruce to work.
Context
main.log
Screenshots
System information

OS: Windows 10
Grabber version: 7.9.1 x64

Additional context
In all honesty, this just seems to be more of the same cloudflare conundrum that just keeps growing and growing as more booru sites opt to hire cloudflare for their protection services. I don't want to sound too pessimistic but the way things are currently shaping up for  Grabber means that it's going to eventually loose it's original purpose of serving as a tool for ripping content from boorus (or at least the ones using cloudflare)

So looking a little bit more into it, the cause of this bug seems to be some part of some left over jank from their recent maintenance (the reason the site was down) since some users are reporting API issues within the site itself and other projects that interact with the e621 API also reporting issues. I'm hoping it's just something temporary really and doesn't need to be addressed yet.

Let's hope that's the case 😄

Hit this same issue with The Wolf's Stash on Android.  The app had to open up a browser so that cloudflare could verify/validate/authorize/whatever the connection.    I've tried connecting via Chrome on Windows which did give me the cloudflare page for a few seconds before allowing me in, but it looks like it's tied specifically to that browser.  When opening in Firefox, I got the same page for a few seconds before proceeding.  The only thing I could think of at this point that would help would be some kinda browser within grabber that could open a window, wait for cloudflare, then grab whatever cookies are being set.
After connecting in browser, check your cookies.  There should be a cf_clearance cookie.  I tried bringing this into grabber with no luck.

Seems they fixed whatever they had going on at the moment and things seem to be working fine once more.


FrontEnd SPA application

I noticed this in the Roadmap. Has anybody down this? How far away would one be?

Hi @iang0ld,
Yes, it is in the Roadmap but I have not started yet.
However, I started to wonder if anyone would like to do something like that. It sounds simple but still requires some effort and time.

@kgrzybek What kind of framework would you like to have as your SPA frontend?
Angular? React? Vue? Or some other kind?

@szenadam It can be any of these 3. Any help will be really, really useful.

Angular is dead, let's showcase one of Top-3: React, Vue or Svelte.
https://2019.stateofjs.com/front-end-frameworks/

I vote for Vue with nswag.  I feel Svelte is too new. Not enough tools and community for a serious project.  Personally I much prefer HTML to JSX, and I think Vue improves React by introducing some of the good things from Angular. Maby I'm a bit BIAS :)

I'm interested to understand if there has been any discussion/thought around the structure of the front end UI, as well as possible technologies to implement?
I'm thinking specifically how the UI relates to the existing bounded contexts, how should it align with those and how should it be designed so that it is modular in line with those, maybe with a thin composition layer (e.g. composite UI)?
Is it possible it needs its own bounded context or contexts? There was an interesting discussion in the virtual ddd community which I understood to be about whether the users may need a seperate model/bounded context to those created wiht domain experts, that is their view may be a simplfied view of the internal bounded contexts. I think this is probably not be the case here, as the domain models of the bounded contexts align with the users view and would probably be revealed during event storming, etc..

I would also consider Blazor as means to showcase the .NET stack

Due to the lack of interest in this topic by others, some time ago I decided to implement SPA application using the React library. The first, very beta version is almost ready and will be released soon.
Of course, I invite you to contribute because there will be a lot of work to do.

I propose also Blazor :).

As I wrote I published a week ago the first version of FrontEnd application in React: https://github.com/kgrzybek/modular-monolith-with-ddd-fe-react
Once again, I invite you to contribute.


Remove Companion objects with non-public member from Public API

What does this PR do?
Small change to remove companion objects with only non-public members from the public API. Otherwise empty Companion class may be hanging in the suggestions list on the user side.
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

Codecov Report

Merging #1207 (0dd9ef9) into feature/sdkv2 (932cecb) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@              Coverage Diff               @@
##           feature/sdkv2    #1207   +/-   ##
==============================================
  Coverage          82.59%   82.59%
==============================================
  Files                351      351
  Lines              12480    12475    -5
  Branches            2058     2056    -2
==============================================
- Hits               10307    10303    -4
- Misses              1533     1535    +2
+ Partials             640      637    -3

Impacted Files
Coverage Δ

...atadog/android/core/configuration/Configuration.kt
98.59% <ø> (ø)

.../kotlin/com/datadog/android/rum/RumResourceKind.kt
100.00% <ø> (ø)

.../com/datadog/android/tracing/TracingInterceptor.kt
96.79% <ø> (ø)

...n/kotlin/com/datadog/android/DatadogInterceptor.kt
81.13% <100.00%> (ø)

.../main/kotlin/com/datadog/android/rum/RumMonitor.kt
78.85% <100.00%> (ø)

...dog/android/rum/resource/RumResourceInputStream.kt
90.77% <100.00%> (ø)

.../rum/tracking/ActivityLifecycleTrackingStrategy.kt
96.00% <100.00%> (ø)

...adog/android/sqlite/DatadogDatabaseErrorHandler.kt
91.67% <100.00%> (ø)

...android/log/internal/logger/TelemetryLogHandler.kt
71.43% <0.00%> (-14.29%)
:arrow_down:

...ain/java/com/datadog/opentracing/PendingTrace.java
57.76% <0.00%> (-1.72%)
:arrow_down:

... and 12 more


Fixes printf for text

We are wrapping the multiline text with a quote so that the entire multiline text is printed instead of just the first line.
For example, wrapping a multiline text without quotes throws the following error:
eval "printf this is line 1
> this is line 2
> this is line 3"
thisbash: this: command not found
bash: this: command not found

Wrapping the multiline text with quote will print successfully:
eval "printf 'this is line 1
this is line 2
this is line 3'"
this is line 1
this is line 2
this is line 3

@drnic @longnguyen11288 : when we get this merged, can we create a new bosh release with the updated resource as well please?
**update: ** Noticed that this is actually failing for strings with spaces as well.

@longnguyen11288 It looks like the pipeline to package it into the bosh release may have failed: https://ci.starkandwayne.com/pipelines/slack-notification-resource-boshrelease/jobs/embed/builds/18

yeah i upgraded concourse... and it broke pipeline... and havent had chance to
look at it. let me put it on older version of concourse and cut a release for
you.

On Feb 9 2016, at 2:13 pm, Brenda Chan<EMAIL_ADDRESS>wrote:

@longnguyen11288 It looks like the
pipeline to package it into the bosh release may have failed:
<https://ci.starkandwayne.com/pipelines/slack-notification-resource-
boshrelease/jobs/embed/builds/18>

—
Reply to this email directly or [view it on GitHub](https://github.com
/cloudfoundry-community/slack-notification-resource/pull/6#issuecomment-182012
505).![](https://github.com/notifications/beacon/AA4rDHyHxsRb6vH3Suo7Yh8wHFp4S
AWmks5pijHMgaJpZM4HVvJC.gif)

done new release cut

On Feb 9 2016, at 3:05 pm, Long Nguyen<EMAIL_ADDRESS>wrote:
yeah i upgraded concourse... and it broke pipeline... and havent had chance to
look at it. let me put it on older version of concourse and cut a release for
you.

On Feb 9 2016, at 2:13 pm, Brenda Chan<EMAIL_ADDRESS>wrote:

@longnguyen11288 It looks like the
pipeline to package it into the bosh release may have failed:
<https://ci.starkandwayne.com/pipelines/slack-notification-resource-
boshrelease/jobs/embed/builds/18>

—
Reply to this email directly or [view it on GitHub](https://github.com
/cloudfoundry-community/slack-notification-resource/pull/6#issuecomment-182012
505).![](https://github.com/notifications/beacon/AA4rDHyHxsRb6vH3Suo7Yh8wHFp4S
AWmks5pijHMgaJpZM4HVvJC.gif)


<EMAIL_ADDRESS>is not in this registry.

op@os-MacBook-Air resolute-serverless-backend % npm install -D serverless-plugin-typescript typescript
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/severless-plugin-typescript - Not found
npm ERR! 404
npm ERR! 404<EMAIL_ADDRESS>is not in this registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!      /Users/op/.npm/_logs/2021-12-08T09_49_10_636Z-debug.log

There's a misspelling in the registry

I misspelled it


Hover support for custom symbols (variables, constants, functions)

Hover Support for custom symbols would be great, e.g. in the following snippet I would like to hover main and say_hello and get the docstring and function definution, like for builtin symbols.
"""
say something
"""
def say_hello(what):
    print("hello", what)

"""
main func
"""
def main():
    say_hello("name")

main()

I think this works already -- in Python, and consequently, starlark, the docstrings go after the declared thing. Try again with
def say_hello(what):
    """
    say something
    """
    print("hello", what)

def main():
    """
    main func
    """
    say_hello("name")

@nicksieger you're right concerning the docstring. Obviously I'm too much in Go and Typescript :-).
So the only improvement here were if the symbol definition could also be provided in the hover.


compatible with lower versions registering "default." keys

fixes https://github.com/apache/dubbo/issues/5948

EDAS, they report they need this fix to test lower version compatibility.

We need this to be merged into master for the snapshot version to be released.

您好，为什么这部分内容没有在2.7.7和最新的2.7.8的分支中看到呢？我也遇到了想同的问题


Tooling updates

Porting over some of the tooling stuff I had baked into what I started tinkering with in another repo:

Updates dependencies to resolve vulnerabilities
Adds prettier support (and reformats the existing code -- I probably should have done this in a separate commit, but figured the amount of code is still very small so it would be manageable
Adds styling support for components and some trivial examples of using it
Adds a make command to link the dev location to the extensions directory for local development/testing (as directed by the lens documentation
Adds linting support via eslint
Adds two PR checks: a linting check, which covers both eslint and prettier, and a build check

Test runs of the PR checks can be found over here:  https://github.com/jdonenine/lens-ide-extension/pull/4/checks


Add guitar-songs app

This is an app that lets you upload lyrics and chords for playing songs on the guitar.

Wow, that's really neat - thanks!


cmd/asm: bad assembly accepted, misassembled

MOVB (BX)(R8*4), AH
The assembler accepts this instruction but silently misassembles it to:
MOVB (BX)(R8*4), SP
This is because we need the RAX prefix for the indexed address, but then the RAX prefix also forces the use of standard register naming instead of the weird *H register naming.
gas rejects this instruction movb (%rbx,%r8,4),%ah with can't encode register '%ah' in an instruction requiring REX prefix.
@rsc

We'll catch this as part of the big asm fixup.

But expanding what I said yesterday just a bit: never use MOVB or MOVW with a register destination, since it's inefficient (it's a read-modify-write on the target register). Instead use MOVL for reg->reg and use MOVBLZX or MOVWLZX for mem->reg; those are pure writes on the target register.

Actually, on third glance I'm even more surprised you are trying to address AH (not AL). Why?

SSA never uses AH.  I just ran into this while writing a test case.


Validate channel is set earlier than StandardSlackService

Refer to #506
this.roomIds = roomId.split("[,; ]+");

Which means you haven't set a channel, it should error higher up and not with a null pointer exception.
Originally posted by @timja in https://github.com/jenkinsci/slack-plugin/issues/506#issuecomment-463560926

this has been done


chore: Add env variable for git filesystem in CI

Description

Set a file path for the git to store files during the CI runs. As this was not set earlier TCs were failing with the error Creating a directory failed

Type of change

Bug fix (non-breaking change which fixes an issue)

@abhvsn if the folder doesn't exist, does the server create it and it's parents on startup automatically?

@abhvsn if the folder doesn't exist, does the server create it and it's parents on startup automatically?

@sharat87 Yes in local setup when we run the java -jar command and if env is present it creates the directory if not present alredy


Issue with opening sfm from a script/dmenu

An issue that I spotted is when I try to run sfm from a script, it fails to start.
I tried "st -e sfm", "st sfm" or just a script with sfm, but nothing succeded unfortunately.

https://github.com/afify/sfm/issues/26

yes, thanks @viyoriya , it totally helped.
Sorry for the duplicate issue, but it might be worth either replacing those termbox.c, termbox.h and utf8.c files or just mention this issue somewhere on readme for now.


Add alter index statement

For #4156 and #3947.

Pull Request Test Coverage Report for Build 1598

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 65.175%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

shardingsphere-sql-parser/shardingsphere-sql-parser-engine/src/main/java/org/apache/shardingsphere/sql/parser/sql/statement/ddl/AlterIndexStatement.java
0
1
0.0%

Totals

Change from base Build 767:
-0.004%

Covered Lines:
10920

Relevant Lines:
16755

💛  - Coveralls


SassC::SyntaxError: Error: malformed URL

on line 1:9 of ../../../.rvm/gems/ruby-2.6.0/gems/active_skin-0.0.12/app/assets/stylesheets/active_skin.sass
from line 19:1 of app/assets/stylesheets/active_admin.css.scss
@import url(//fonts.googleapis.com/css?family=Source+Sans+Pro:400,"600","700

error when compiling:
https://github.com/SoftwareBrothers/active_skin/blob/master/app/assets/stylesheets/active_skin.sass#L1
Please give me the best solution to this issue, thank you.

the gem you are using doesn't work with sassc. You need to open an issue on that gem. Thank you for reporting.


Fix typo instane -> instance

Hello, small typo fix in the notebook.

Typo fixed using the PR https://github.com/IBM/watson-openscale-samples/pull/65 hence closing this PR


Support Deployment of Sub-Applications / Virtual Directories

In many cases, applications we deploy are not root applications.  They are hosted as sub-applications underneath a single site.  It'd be great if the WinRM tasks directly supported this scenario.  We're currently trying to find a combination of arguments to pass in to make it work, trying to avoid custom tasks.

Thanks for your feedback adding our PM @RoopeshNair  to note this feedback

We have in our backlog to support the deployment of virtual applications.
For now, please refer to GitHub link: https://github.com/Microsoft/vsts-rm-extensions/issues/56 which has more details around this.


[SPARK-22285] [SQL] Change implementation of ApproxCountDistinctForIntervals to TypedImperativeAggregate

What changes were proposed in this pull request?
The current implementation of ApproxCountDistinctForIntervals is ImperativeAggregate. The number of aggBufferAttributes is the number of total words in the hllppHelper array. Each hllppHelper has 52 words by default relativeSD.
Since this aggregate function is used in equi-height histogram generation, and the number of buckets in histogram is usually hundreds, the number of aggBufferAttributes can easily reach tens of thousands or even more.
This leads to a huge method in codegen and causes error:
org.codehaus.janino.JaninoRuntimeException: Code of method "apply(Lorg/apache/spark/sql/catalyst/InternalRow;)Lorg/apache/spark/sql/catalyst/expressions/UnsafeRow;" of class "org.apache.spark.sql.catalyst.expressions.GeneratedClass$SpecificUnsafeProjection" grows beyond 64 KB.

Besides, huge generated methods also result in performance regression.
In this PR, we change its implementation to TypedImperativeAggregate. After the fix, ApproxCountDistinctForIntervals can deal with more than thousands endpoints without throwing codegen error, and improve performance from 20 sec to 2 sec in a test case of 500 endpoints.
How was this patch tested?
Test by an added test case and existing tests.

cc @cloud-fan

test this please

Test build #82798 has started for PR 19506 at commit 652b301.

Test build #82796 has started for PR 19506 at commit 652b301.

Test build #82798 has finished for PR 19506 at commit 652b301.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ApproxCountDistinctForIntervalsQuerySuite extends QueryTest with SharedSQLContext

Merged build finished. Test PASSed.

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

Test build #82796 has finished for PR 19506 at commit 652b301.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class ApproxCountDistinctForIntervalsQuerySuite extends QueryTest with SharedSQLContext

Merged build finished. Test PASSed.

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

Test build #82929 has started for PR 19506 at commit 2d1b070.

Test build #82929 has finished for PR 19506 at commit 2d1b070.

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

Merged build finished. Test PASSed.

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

Test build #82947 has started for PR 19506 at commit 1b75428.

Test build #82948 has started for PR 19506 at commit 49b4ac2.

Test build #82947 has finished for PR 19506 at commit 1b75428.

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

Merged build finished. Test PASSed.

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

Test build #82948 has finished for PR 19506 at commit 49b4ac2.

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

Merged build finished. Test PASSed.

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

LGTM except a few minor comments

Test build #82966 has started for PR 19506 at commit 1e95a2f.

Test build #82966 has finished for PR 19506 at commit 1e95a2f.

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

Merged build finished. Test PASSed.

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

thanks, merging to master!


[Core] Clarify use of summaries.

TODOs:

Fix potential bugs in summary specs
-Add/Create FAQ how to use summaries
Create example configs in examples folder

I'll create an example script for a learning DQNAgent with summaries on the NN vars.

This has been completed and can be tried out in the global_training_time_step_and_summaries-branch (file: rlgraph/examples/dqn_cartpole_with_tf_summaries.py).

There was a bug where the summary_regexp was not passed into the graph_builder and the global_training_timestep of the graph executor was never properly increased.
After testing confirmation, this branch will be merged into master.


Need to handle left-looking LOS

Code reference:
https://github.com/dbekaert/RAiDER/blob/3dca5aa8de0a1750cc5aac410c00e5446d38c718/tools/RAiDER/losreader.py#L253
Currently no explicit handling of left-looking sensors; incidence angle would need to be negative?

NISAR is a left looking instrument. We should circle back to this and address it.

This shouldn't be an issue, according to Heresh. The only part of the code this would affect is calculating unit look vectors from heading and incidence angle, and the heading should account for the look direction. Thus the existing code should work fine. The other part of the code uses the satellite state vectors and should also work fine.


There is a memory leak defect at line 141 in the file /openssl/test/cmp_hdr_test.c.

This defect is located in a different function than the one mentioned in the issue https://github.com/openssl/openssl/issues/24469. They are two distinct defects, even though they are in the same file and the variable names are the same.
In the file /openssl/test/cmp_hdr_test.c, at line 134, a pointer variable named x509name is defined and allocated a dynamic memory region through the function X509_NAME_new. When the if statement at line 136 returns false, it indicates that the dynamic memory region pointed to by x509name was successfully allocated. If the if statement at line 140 returns true, the program will return at line 141, thereby skipping the release of the dynamic memory region pointed to by x509name at line 150. This results in a memory leak defect, as shown in the following diagram(note that the defect path provided in the figure does not match my description; my description should be considered accurate):
https://github.com/LuMingYinDetect/openssl_defects/blob/main/openssl_28.png

This was fixed by https://github.com/openssl/openssl/pull/24511


Cequel Sinatra

I'm using Sinatra for my API because I've separated out the "view" component for scalability-purposes. Will cequel work with Sinatra and other Rack-based frameworks (other than Rails)?

Follow-up question: The README says that Rails is not required but config/cequel.yml is. Is there anything else required other than?:
development:
  host: '<IP_ADDRESS>'
  port: 9042
  keyspace: Blog

I figured out I can just use cassandra-driver for simple interactions.


Use ServerTimer instead of Gauge for emitting cpu time metric

Gauge is not the right choice for this timer related metric. It should be emitted similar to ServerTimer or ServerQueryPhase which underneath use the API addTimedTableValue.
See the discussion here - https://github.com/apache/incubator-pinot/pull/6680#discussion_r595643785

LGTM

Will this change the reported JMX naming for those metrics?

please format your code to pass ci


sign cosmwasm store code msg fail with error Ledger Native Error: Output buffer too small

Is this a problem with Ledger itself or app? Why is this problem occurring?
I'm guessing this is because the size of the contract file is too large to hold contain all contents in buffer.

Hi @loin3, can you share the transaction here? I think that it's too big to be handle by the device. Are you using a NanoS?

Yes. I am using NanoS.
I used cosmwasm/hackatom.wasm file to test store code. And I found that only 13KB size of contract can be signed with NanoS.

The devices have very limited resources and big transactions might not be able to be processed. Actually, 13kB it's a lot in terms of transactions for hardware wallets


feat(lanelet2_extension)!: move package to autoware_common

Description

See https://github.com/autowarefoundation/autoware_common/pull/84 and https://github.com/autowarefoundation/autoware_common/pull/85.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

❯ git log --oneline c45e59756e0ef451f70c89e4f17bbdda9b6613f1..origin/main map/lanelet2_extension/
141b7a913 fix(lanelet2_extension): make all polygons clockwise in ll2 visualization (#1461)
4c76f992e fix(lanelet2_extension): fix getCurrentLanelets() (#1318)
56885ed56 feat(behavior_path_planner): update pull_over module (#873)

@kenji-miyake
Can I add this bug fix before moving to autoware_common?


Debugger click-to-resume overlay broken on 0.19

There's a regression in the Elm 0.19 debugger's "click-to-resume" feature. In Elm 0.18, when you time-travel into the past, a big "click-to-resume" overlay covers your app and clicking it time travels to the present. But in 0.19, the overlay is not shown. Clicking anywhere in your app while in this state will do nothing. It's especially bad if the user closes the debugger popup window while in this state, as they will be unable to reopen the debugger in order to resume.
Steps to reproduce
First, compile Main.elm using --debug
module Main exposing (..)

import Browser
import Html exposing (button, div, text)
import Html.Attributes exposing (id)
import Html.Events exposing (onClick)

main = Browser.sandbox { init = 0 , view = view , update = update }

type Msg = Increment

update _ n = n + 1

view n =
    div []
        [ text (String.fromInt n)
        , button [ onClick Increment ] [ text "+" ]
        ]

open the resulting index.html
click the "+" button a few times
open the Elm debugger popup
select a msg from the past
observe that inputs are blocked, but no overlay is shown

Here's a video demonstrating the bug in Safari (Chrome looks similar)
Notice that after time-travelling, clicking the "+" button in the Elm app does nothing, and the user has no way to know why it's not working.
I would expect an overlay to be shown like how Elm 0.18 does it:

But in 0.19, the overlay is not shown.

It is shown outside of the window. I could make it shown by adding position: fixed to the overlay (from devtool), but the "Resume" event was still not handled.
I think this is the event handler but seems like not working.
https://github.com/elm/browser/blob/813607120cad18bae101c9ec502733d9d940c612/src/Debugger/Overlay.elm#L147

Can we get some action on this issue? I want to demonstrate the awesomeness of Elm and use 0.19, but this regression would make me look silly if I try to show off the debugger.
 I think something is wrong in handling virtual DOM in the kernel logic. If you want to debug, you can do something like this.

That's pretty cool. I'm seeing a runtime error getting tossed.
Uncaught TypeError: domNode.replaceData is not a function
`function _VirtualDom_applyPatch(domNode, patch)
{
switch (patch.$)
{
case 0:
return _VirtualDom_applyPatchRedraw(domNode, patch.s, patch.u);
	case 4:
		_VirtualDom_applyFacts(domNode, patch.u, patch.s);
		return domNode;

	case 3:
		domNode.replaceData(0, domNode.length, patch.s);
		return domNode;`

But... it looks like this should have been resolved a while back. Maybe it's a regression. https://github.com/elm/virtual-dom/pull/20

Sorry, I get a very different behavior because I have a page with two Elm apps in it, and it barfs in special ways when I open both debuggers.

@evancz How do I debug codez in here so I can contribute? I tried jinjor's suggestion of using elm-kernel-debug, but that didn't honor the changes I made in the Browser module and compile them into index.html.
How do you do it when working on stuff?

@Pilatch Did you understand what the shell script does? It is just a dirty hack, not a library.

Yea, I understand what it's doing. I wanted to test the browser library, so I made changes in there, put it in the base of the project alongside virtual-dom, changed the package variable in the shell script and re-built. The script puts my changes into the 0.19.0 folder, but the generated index.html file doesn't have those changes in it.

OK, I think I see what's up. Thanks to a helpful person in slack, I discovered that you can negate the cache by deleting .dat files, and by putting stuff in your ~/.elm folder, which would mean the build script would change line 23 to
target_dir=~/elm/0.19.0/package/$author/$package/$version

Nope. Finally found it. There was a version conflict with virtual-dom. The one I was modifying was 1.0.2, but elm was building 1.0.0. Will update your readme and send pull request... among other things. :)

Update. Now that I have that running smoothly I can debug enough to confidently say:

The overlay can display properly by adding styles in Overlay.elm as @jinjor suggested.

                    , style "position" "fixed"
                    , style "top" "0"
                    , style "left" "0"

Clicking to resume is bugged not because of Elm code, but because of Debugger.js. I was reminded by the adage, "When you find a bug, it's probably in JS." We also know the Elm code is not at fault because the Resume button on the little popout thingy works as expected, and that just sends a simple Resume message.

We can prove this by allowing click events through. in the _Debugger_blocker function in Debugger.js we can add this check against click events, which will make the overlay's click event work as intended.
	if (event.type !== 'click')
	{
		event.stopPropagation();
		event.preventDefault();
	}

Of course that lets all click events through, which will have undesirable consequences and will probably corrupt the program's state in some cases. So my task is now to only allow click events on the overlay. How to do that is not immediately obvious because hoo-boy this code is funky!

Derp. Looks like I just needed to add id "elm-debugger-overlay" to the overlay in Elm. Incoming merge request.

Created. https://github.com/elm/browser/pull/40

The fix in #40 ended up in some debugger improvements that @Skinney worked on recently. The plan is to release that in a PATCH change by Monday, so it should be possible to get the fixed version by just changing from 1.0.1 to 1.0.2 once it is out!


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

OK


Very old content

[Enter feedback here]
This document is not relevant for .NET 6, it is using the Startup.cs file which was deprecated.

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

ID: c8d9b842-de22-59e7-e36a-662e2060ae7a
Version Independent ID: bda934c5-a268-721f-1a3e-1f73fc25c15f
Content: ASP.NET Core MVC web app tutorial using Azure Cosmos DB
Content Source: articles/cosmos-db/nosql/tutorial-dotnet-web-app.md
Service: cosmos-db
Sub-service: nosql
GitHub Login: @StefArroyo
Microsoft Alias: esarroyo

Hi @acidrod ,
Thanks for sharing this feedback. We will look into this and update as appropriate.

Hi @StefArroyo,
Could you please look into this request. Thanks

#reassign:seesharprun

Hi @acidrod ,
Thanks for sharing this feedback. We will look into this and update as appropriate.

Looking forward to some updates on this doc! Thank you for the effort!

@acidrod, we are starting the work to update this tutorial now.
It will use .NET 6 and ASP.NET.

@acidrod: Thanks for this feedback. We are working on a new tutorial that should launch later this week.
I will assign this issue to the work for that tutorial. Once the tutorial enters our publishing pipeline, this issue will automatically close. Thanks again for championing for great content in our Docs!


Video Streaming Issue

Specify the sample to which the issue belongs (use [x]):
[ ] P2P Call sample
Platform (use [x])
[ ] Flutter
Device info
Manufacture:
Model:
OS version:
Describe the bug:
I am facing an issue in the video view that when two-person make a video call then the video of both the persons are shrunk to center and empty space is shown on both left and right side. If we change the code and then the view is stretched and the image quality goes down. How we can create video view call like WhatsApp video call or how we can fix the stretched video part. Please provide some solution.
Steps to Reproduce:

RTCVideoView

today we released the new version of our SDK and now RTCVideoRenderer has field videoWidth and videoHeight maybe it will help you to realize the required functionality.

No activity for a long time, closing. If you have any other issues, please create a new one with details.


400 Bad request error with valid token

Have downloaded latest version, grabbed token and put into .humble-cli-key however receiving following error:

Which OS are you using?
Can you also try humble-cli list --id-only to see if you get any result back?

Tried on both Ubuntu 20.04 & 22.04

Sorry, I couldn't reproduce the issue on an Ubuntu machine.
Does this work for you? humble-cli list --id-only

Yup, on one machine I can see the ID's print out successfully, on the other I'm getting the following error:
$./humblecli: error while loading shared libraries: libssl.so.1.1: cannot open share dobject file: No such file or directory
(This is a fresh ubuntu 22.04 install)

Yes, there is a problem with SSL library on newer Ubuntu versions. I will fix that in #7.
Since you can see ID's, this means the token is correct. I suspect one of the purchases is in a format that humble-cli cannot handle. Humble Bundle doesn't have a documented API, so I have implemented and tested this tool based on my own purchases :)
You can find the culprit in your purchases with this command:
humble-cli list --id-only | xargs -I {} sh -c 'echo Bundle ID = {} && humble-cli details {}'

I think I found the root-cause. You probably have too many bundles and that's why getting all of their info at once fails.
Just to confirm, can you tell me the output this command gives you?
humble-cli list --id-only | wc -l

Hi @Monthrect. Please check the new 0.6.0 release. It should fix the SSL and 400 Bad Request errors.

Hi @smbl64 great news, 0.6.0 is working great, except the full help file isn't printing with --help but other than that downloads are working.


SCORM Profile Example

This isn't intended to be a final form of the SCORM Profile, or directly in the path of it, but an example using the SCORM Profile as a jumping off point to illustrate a few capabilities of profiles

And the profile itself didn't post... let me see...

{
    "@id": "https://w3id.org/xapi/scorm#profile",
    "name": {
        "en": "Experience API SCORM Profile"
    },
    "seeAlso": "https://adl.gitbooks.io/scorm-profile-xapi/content/",
    "versions": [
        {
            "@id": "https://w3id.org/xapi/scorm#v2",
            "generatedAtTime": "...",
            "wasRevisionOf": ["https://w3id.org/xapi/scorm"]
        },
        {
            "@id": "https://w3id.org/xapi/scorm",
            "generatedAtTime": "..."
        }
    ],
    "author": {
        "@type": "Group",
        "name": "ADL"
    },
    "concepts": [
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/initialized",
            "
            ": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "initialized"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/terminated",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "terminated"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/suspended",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "suspended"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/resumed",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "resumed"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/passed",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "passed"
            },
            "broader": ["http://adlnet.gov/expapi/verbs/completed"]
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/failed",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "failed"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/scored",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "scored"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/completed",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "completed"
            }
        },
        {
            "@type": "Verb",
            "@id": "http://adlnet.gov/expapi/verbs/responded",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "responded"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/course",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "course"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/module",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "module"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/lesson",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "SCO"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/assessment",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "assessment"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/interaction",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "interaction"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/objective",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "objective"
            }
        },
        {
            "@type": "ActivityType",
            "@id": "http://adlnet.gov/expapi/activities/attempt",
            "inScheme": "https://w3id.org/xapi/scorm",
            "prefLabel": {
                "en": "attempt"
            }
        }
    ],
    "templates": [
        {
            "@id": "_:initialization",
            "name": {
                "en": "initialization"
            },
            "verb": "http://adlnet.gov/expapi/verbs/initialized",
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                }
            ]
        },
        {
            "@id": "_:termination",
            "name": {
                "en": "termination"
            },
            "verb": "http://adlnet.gov/expapi/verbs/terminated",
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                }
            ]
        },
        {
            "@id": "_:suspension",
            "name": {
                "en": "suspension"
            },
            "verb": "http://adlnet.gov/expapi/verbs/suspended",
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                }
            ]
        },
        {
            "@id": "_:resumption",
            "name": {
                "en": "resumption"
            },
            "verb": "http://adlnet.gov/expapi/verbs/resumed",
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                }
            ]
        },
        {
            "@id": "_:scoactivity",
            "name": {
                "en": "SCO activity"
            },
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                },
                {
                    "location": "verb.id",
                    "none": [
                        "http://adlnet.gov/expapi/verbs/resumed",
                        "http://adlnet.gov/expapi/verbs/suspended",
                        "http://adlnet.gov/expapi/verbs/terminated",
                        "http://adlnet.gov/expapi/verbs/initialized"
                    ]
                }
            ]
        },
        {
            "@id": "_:commenting",
            "name": {
                "en": "commenting"
            },
            "verb": "http://adlnet.gov/expapi/verbs/commented",
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                },
                {
                    "location": "result.response",
                    "rule": "included"
                }
            ]
        },
        {
            "@id": "_:completing",
            "name": {
                "en": "completing"
            },
            "verb": "http://adlnet.gov/expapi/verbs/completed",
            "objectActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                },
                {
                    "location": "context.contextActivities.parent[*].id",
                    "rule": "excluded"
                }
            ]
        },
        {
            "@id": "_:otheractivity",
            "name": {
                "en": "other activity"
            },
            "contextParentActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                }
            ]
        },
        {
            "@id": "_:interactionactivity",
            "name": {
                "en": "interaction activity"
            },
            "verb": "http://adlnet.gov/expapi/verbs/responded",
            "objectActivityType": "TODO look up interaction activity URI",
            "contextParentActivityType": "http://adlnet.gov/expapi/activities/lesson",
            "rules": [
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/attempt"]
                },
                {
                    "location": "context.contextActivities.grouping[*].definition.type",
                    "any": ["http://adlnet.gov/expapi/activities/course"]
                },
                {
                    "location": "timestamp",
                    "rule": "included"
                }
            ]
        }
        // TODO multiple objectives statements
        // TODO progressed
        // TODO scored
        // TODO passed
        // TODO failed
        // TODO location of state data
        // TODO check lots of templates exist for both object & parent (at least potentially)
        // TODO double check templates don't multi-match. Or consider an order of checking rule?
        // That might be better.
    ],
    "patterns": [
        {
            "name": {
                "en": "General Pattern"
            },
            "definition": {
                "en": "This pattern describes the overall sequence of statements sent over the course of an attempt"
            },
            "sequence": ["_:initialization", "_:middlestatements", "_:optionallycontinue", "_:termination"]
        },
        {
            "@id": "_:activitystatements",
            "alternates": ["_:scoactivity", "_:otheractivity", "_:commenting", "_:interactionactivity", "_:completing"]
        },
        {
            "@id": "_:middlestatements",
            "zeroOrMore": "_:activitystatements"
        },
        {
            "@id": "_:suspendresume",
            "sequence": ["_:suspension", "_:resumption", "_:middlestatements"]
        },
        {
            "@id": "_:optionallycontinue",
            "zeroOrMore": "_:suspendresume"
        }

    ]
}

Since this has been added to the repository, I'm closing this issue.


Use exit code 1 for non example error

When there's a non example error, we want to label it as a "failed" process with exit code 1. Replicating rspec's --error-exit-code=1 flag

LGTM
is there any other case that we are expected but still return 0?

Rspec test failure is covered
Rspec error outside example is covered

Worker failure (crash, etc.) is covered by our CI agent (...I think) 🤔