merge package template from arlac77/npm-package-template

package.json

chore(scripts): update prepare@rollup -c from template
chore(devDependencies): add<EMAIL_ADDRESS>from template

doc/jsdoc.json

chore: update from template

Coverage increased (+0.6%) to 96.439% when pulling 9d7026b965daebc41743a609a5e2f173d2aeaf47 on template-sync-1 into 394a312280adec29d38acffeee118c4b7238a738 on master.

Codecov Report

Merging #190 into master will increase coverage by 0.59%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #190      +/-   ##
==========================================
+ Coverage   95.84%   96.43%   +0.59%
==========================================
  Files          27       27
  Lines         337      337
==========================================
+ Hits          323      325       +2
+ Misses         14       12       -2

Impacted Files
Coverage Δ

tests/worker-test.js
100% <0%> (+15.38%)
:arrow_up:

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 394a312...9d7026b. Read the comment docs.


Robusta cli cannot reach runner

Describe the bug
I have deployed robusta using helm chart via flux2 helmrelease. Generated values initially with robusta cli, added custom playbooks to values, then generated a helmrelease file deployed. All working good, however I cannot trigger playbooks manually using the cli. KUBECONFIG variable is set to the cluster where I deployed robusta, and Im in the same dir I created the generated_values.yaml file. I can't really use the cli to interact with robusta, Im seeing the following errors:
Triggering action...
======================================================================
running cmd: curl -X POST http://localhost:5000/api/trigger -H 'Content-Type: application/json' -d '{"action_name": "popeye_scan", "action_params": {}}'
error: pod, type/name or --filename must be specified
error: Cannot trigger playbook - usually this means Robusta just started. Will try again
error: pod, type/name or --filename must be specified
error: Cannot trigger playbook - usually this means Robusta just started. Will try again
======================================================================
Fetching logs...
======================================================================
error: expected 'logs [-f] [-p] (POD | TYPE/NAME) [-c CONTAINER]'.
POD or TYPE/NAME is a required argument for the logs command
See 'kubectl logs -h' for help and examples
======================================================================
Cannot fetch logs. robusta-runner not found
======================================================================
======================================================================
Done!

To Reproduce
Steps to reproduce the behavior:

generate values using robusta cli and deploy to cluster in a custom namespace (robusta)
set KUBECONFIG env var to point to the kubernetes cluster were you deployed robusta.
run export DOCKER_DEFAULT_PLATFORM=linux/amd64 to allow docker cli running in m1 Mac to use amd64 images.
run the robusta cli docker version to list playbooks: ./robusta playbooks list

Expected behavior
Interact with the features robusta cli offers.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
MacOS Ventura 13.4 m1.
Additional context
As I said, probably Im just doing something wrong but just not seeing the same issue happening to anyone here in issues nor in documentation, so Im assuming its pretty straight forward and Im just overlooking something. Thanks!

Does it work with ./robusta playbooks list --namespace=robusta?

it does! thanks!, can't believe I missed this.

Cool, making the error message more clear in #921 and closing this.
Thanks for reporting :)


Raspberry Pi 3B+ GPU setting

Hi,
Thanks for the great work. I follow the instruction to install, the chrome browser is working fine. But when I use it to watch some .ts streaming video, it start to lag and choppy, and it finally stop rendering the video. So I start to realize may be I need to tune up the GPU memory for my raspi3b+, I tried to modify the config.txt file and change gpu_mem=16 (default ?) to gpu_mem=192, but it still the same, Now I have question,
Does this option under config.txt is working after kernel load up ? and Should I buy the MPEG2 & VC-1 license and add it under config.txt, will it take effect for better performance ?
Seems the chrome://gpu show up using hardware acceleration, but I want to confirm the config.txt is working under FydeOS before I buy the license.
Thanks.

Do we know if Chromium OS use the config.txt file? I tried to modify it but it didn't work. After I burn the .img to the Micro SD card and modify the file I got a : Write Protection Error. But burning Raspbian or other OS .img, modifying the config.txt file work.

In fact, Rpi 3B(+) plays the video with software decoder. There is no compatible interface for chromium to visit the hardware decoder of VC4. We need the hackers or Broadcom official to provide compatible driver fro chromium os.

according to https://www.raspberrypi.org/documentation/configuration/config-txt/, Rpi 3B(+) will use the config.txt. Also, the Chrome browser able to use the HW decoder. I think it should be the OS level to communicate with HW decoder, at lease I found the config.txt able to use by Raspberry OS.


Added support for dict and dataframe for TreeNode.from_taxonomy

Addressing #2009
Please complete the following checklist:

[x] I have read the contribution guidelines.

[x] I have documented all public-facing changes in the changelog.

[ ] This pull request includes code, documentation, or other content derived from external source(s). If this is the case, ensure the external source's license is compatible with scikit-bio's license. Include the license in the licenses directory and add a comment in the code giving proper attribution. Ensure any other requirements set forth by the license and/or author are satisfied.

It is your responsibility to disclose code, documentation, or other content derived from external source(s). If you have questions about whether something can be included in the project or how to give proper attribution, include those questions in your pull request and a reviewer will assist you.

[x] This pull request does not include code, documentation, or other content derived from external source(s).

Note: This document may also be helpful to see some of the things code reviewers will be verifying when reviewing your pull request.

@wasade @mortonjt Maybe let's merge this PR, and have another PR for lineage-to-columns conversion? Which skbio module do you think it will fit in? Currently there is no taxonomy module in scikit-bio. A work around might be to have a lineage file format.

+1 for lineage format. Then we can have TreeNode.read take in files as input
On Mon, Jun 10, 2024 at 5:15 PM Qiyun Zhu @.***> wrote:

@wasade https://github.com/wasade @mortonjt
https://github.com/mortonjt Maybe let's merge this PR, and have another
PR for lineage-to-columns conversion? Which skbio module do you think it
will fit in? Currently there is no taxonomy module in scikit-bio. A work
around might be to have a lineage file format.
—
Reply to this email directly, view it on GitHub
https://github.com/scikit-bio/scikit-bio/pull/2042#issuecomment-2159295501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXPPC3XKLCVFQEESFD3ZGYJNHAVCNFSM6AAAAABJCYRO7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGI4TKNJQGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


AUI-1866 Fix aui-form-builder-layout-builder tests on smaller screens

Just started reviewing :) :octocat: Sent from GH.

Just started reviewing :) :octocat: Sent from GH.


At the moment, any crewmember with a screwdriver can open a borgs panel and remove the MMI in one button press and about one second. This makes it too easy to grief the cyborg. Players who feel slighted by the cyborg can easily remove them from their shell, and ion stormed cyborgs get their RP runied by one quick screwdriver and a button push.
Additional context
Perhaps make it so emags force open the panel or give crewmembers a longer or more complicated method of opening a panel.

This changes nothing in regular cyborg gameplay since a crewmember can law 2 it to open panel. It is more so to give a cyborg an added layer of protection against griefers or for their law 0 RP.

just needs to be access locked like ss13

Or require some wrench action to remove the MMI after the panel is open

This got implemented with the borg qol pr emisse made


Simplify backports

Addresses #258. As I mentioned there, we could also do without if-let* and when-let*, but those are used much more extensively, so waiting for your opinion on that.

This doesn't have to be addressed in this pull request, but I think the compatibility definitions of alist-get, if-let*, and when-let* could be simplified because we don't use many of the features, including the REMOVE argument to alist-get, the ability of if-let* and when-let* to take nonstandard binding vectors, etc.
Plus it would probably be smarter to condition on fboundp rather than checking the version of Emacs.

I've rebased the appropriate commit with your suggestions (the straight-override-recipe one is a bit convoluted, not sure if I got it right) and added an alist-get simplification. Haven't looked in depth into the internal--* functions and if-get* logic yet though.

Thanks!


Airspeed sensor setup

How did you guys setup your airspeed sensor with the naze32? I haven't found any good information on how to do this anywhere. I am using the same airspeed sensor that you recommended here: http://docs.rosflight.org/en/latest/user-guide/hardware-setup/.

It is just an I2C connection (including scl, sda, 5V, gnd).  Your naze should break out the correct pins. They are probably some un-soldered pads or through holes. I recommend doing a quick internet search for the pinout of your board version. You just need to solder some kind of connection with the airspeed sensor wire. I think we just used some male headers and put a female header on the wire, but more reliable connectors are obviously preferable.

Thanks! That is what I thought but I wasn't sure and couldn't find a definitive answer.


Building ECommerceDDD.IdentityServer Throws 'HostNotFound' Exception

Hi Felipe,
This is more of a general FYI and it could have easily been an issue with my computer set-up, but I was unable to get the app to run after running docker-compose up.
I narrowed it down to when I would build ECommerceDDD.IdentityServer, the project would threw a 'HostNotFound' exception every time and then the app would not authenticate so the SPA was not responding.
I found an alternative set-up for the IdentityServer and used the set-up supplied here .
Using their set-up, I removed DataSeeder.SeedConfiguration and modified builder.Services.AddIdentityServer from
    builder.Services.AddIdentityServer(opt =>
            opt.IssuerUri = tokenIssuerSettings.GetValue<string>("Authority"))
        .AddDeveloperSigningCredential() // without a certificate, for dev only
        .AddAspNetIdentity<ApplicationUser>()
        .AddConfigurationStore(options =>
        {
            options.ConfigureDbContext = b =>
                b.UseNpgsql(connectionString, sql => sql.MigrationsAssembly(migrationsAssembly));
        })
        .AddOperationalStore(options =>
        {
            options.ConfigureDbContext = b =>
                b.UseNpgsql(connectionString, sql => sql.MigrationsAssembly(migrationsAssembly));
            options.EnableTokenCleanup = true;
        });

to
builder.Services.AddIdentityServer(opt =>
        opt.IssuerUri = tokenIssuerSettings.GetValue<string>("Authority"))
    .AddDeveloperSigningCredential() // without a certificate, for dev only
    .AddInMemoryApiScopes(IdentityConfiguration.ApiScopes)
    .AddInMemoryApiResources(IdentityConfiguration.ApiResources)
    .AddInMemoryClients(IdentityConfiguration.Clients)
    .AddOperationalStore(options =>
    {
        options.ConfigureDbContext = b => b.UseNpgsql(connectionString);
        options.EnableTokenCleanup = true;
    })
    .AddConfigurationStore(options =>
    {
        options.ConfigureDbContext = b =>
            b.UseNpgsql(connectionString, sql => sql.MigrationsAssembly(migrationsAssembly));
    })
    .AddAspNetIdentity<ApplicationUser>();

And with this I was able to build successfully and populate the database.
I'm not sure if this is an issue with something I did on my end or if this still produces the desired result, but after successfully building, I was able to use the app and it as able to authenticate.
Just wanted to drop this here in case it provides any value.
If not, feel free to delete (or let me know where I went wrong in my set-up.
Great work and great articles - they have been very helpful - primarily seeing your Angular SPA app at work with Event Sourcing.
Thanks!

Hi @stemadocafe, you're right. This is a known issue, but I haven't had time to fix it. I thank you enormously for this fix and the support of my blog and projects. Would you mind making a pull request with the fix? I'd like to have you as a contributor.
Regarding the solution, the only thing it wouldn't work is referring to the non-existing IdentityConfiguration.ApiResources. Did you add it as well? And as you said, the final solution should remove the DataSeeder class.
Thank you so much

Oh yeah, good call!
I did add ApiResources to the IdentityConfiguration.cs:
   // ApiScopes => (...)

    public static IEnumerable<ApiResource> ApiResources =>
        new ApiResource[]
        {
            new ApiResource(api_scope, "MyActions API")
            {
                Scopes = { api_scope }
            }
        };

    Clients => (...)

Regarding the pull-request, you bet!
I will add the above ApiResources method IdentityConfiguration.cs in the pull request.
I will submit it first thing in the morning.


Overflow still present

It is still possible to cause the hack.chat server to restart.

It's probably overflowing in the read call, since the node ws library I'm using doesn't have a way to buffer input streams. But if it's fixed on your development server but not in hack.chat, maybe I didn't upgrade the production server correctly.

I suspected that you may have just not updated it correctly, it happens.


Implement rules:exists

.gitlab-ci.yml illustrating the issue:
variables:
  MY_FILE: example.txt

stages:
  - build

this runs:
  stage: build
  script:
    - echo $CI_JOB_NAME

this does not:
  stage: build
  script:
    - echo $CI_JOB_NAME
  rules:
    - exists:
       - $MY_FILE

example.txt:
blablabla

Expected behavior
Both jobs should run as they do on GitLab (see this pipeline)
Host information
Ubuntu 22.04
$ gitlab-ci-local --version
4.45.2
$ docker --version
Docker version 24.0.7, build afdd53b

I'm pretty sure this is in fact a feature request. I'll have to checkup, but labeling it feature for now.

Hi thanks for the quick response.
It's a bit more subtle than the new issue title suggests, because "rules: exists" is already working when the target filename is referenced directly in a "rules: exists: [filename]". It just doesn't work when the filename is provided indirectly via a variable.
I've updated my example to better show this.
This isn't super important or blocking my use of gitlab-ci-local, I just thought you should know.
Thanks!

Ooooh.... LoL I didn't even realise we've implemented rules exists 😁


What should you trigger?

I feel what i had most problem grasping, was what you should trigger in the Reflux Stores.
All the examples is very simple like:
this.trigger({
  currentStatus: status
})

But later when you try to add more listeneres in a React component, you found out that a store triggers every event and not only the one you listen to.
// You would think that it would only trigger when "status" change
this.unsubscribe = statusStore.listen(this.onStatusChange);
// But then you try this and it also triggers when status change
this.unsubscribe = statusStore.listen(this.onCommentsChange);

So solution:
I think the docs should mention that you should trigger the whole Store's output every time, and not just different part of data and the change the docs to say:
statusStore.listen(this.onChange);

The component should actually pull the data it needs by itself. You can pass some kind of a change summary as an argument to trigger() but that should not be the way you pass the actual state to the component. At least that's what I would describe as a good practice.

@jankuca How would that look? :) Do you have an example?
There is an example in the docs that triggers all the data like this
https://github.com/spoike/refluxjs#listening-to-changes-in-other-data-stores-aggregate-data-stores

init: function () {
  this.listenTo(store, this.handleChange)
},
handleChange: function () {
  // use a getter on the store to get the data
  this._state.someKey = store.getWhatINeed();
  this.trigger();
},
// provide a getter for a possible dependant to use
getSome: function () {
  return this._state.someKey;
}

Quite simple really. You might want to pass an ID of a changed record in the store to trigger but I'd recommend you just let the component (or the dependant) get what it needs on its own via getters.
handleChange: function (changed_item_id) {
  this._names[changed_item_id] = store.getName(changed_item_id);
  this.trigger();
}

If you wanted to use different handlers for different trigger payloads, you'd need to have some kind of a routing done in the main handler.
handleChange: funciton (summary) {
  switch (summary.type) {
  case 'status': this.handleStatusChange(summary);
  case 'comments': this.handleCommentChange(summary);
  }
}

We do something closer to the following:
var getStateFromStores = function() {
  return {
    widgets: WidgetStore.getWidgets(),
    fobs: FobStore.getFobs(),
    unreadFobs: FobStore.getUnread()
  };
};

var App = React.createClass({

  mixins: [
    Reflux.listenTo(WidgetStore, 'onStoreChange'),
    Reflux.listenTo(FobStore, 'onStoreChange'),
  ],

  getInitialState() {
    return getStateFromStores();
  },

  onStoreChange() {
    this.setState(getStateFromStores());
  },

  render() {
    <WidgetContainer widgets={this.state.widgets} />
    <Fobs fobs={this.state.fobs} unread={this.state.unreadFobs} />
  }
});

Our stores look like this:
var _fobs = [],
    _unreadFobs = {};

var FobStore = Reflux.createStore({
  addFob(fob) {
    _fobs.push(fob);
    _unreadFobs[fob.id] = true
    this.trigger();
  },

  markAsRead(fob) {
    _unreadFobs[fob.id] = false;
    this.trigger();
  },

  getFobs() {
    return _fobs;
  },

  getUnread() {
    return _unreadFobs;
  }
});

This has the advantage of keeping our stores nice and clean, and our components always get the right data at the time from the stores.

@jankuca @akre54 Thank you very much for the examples! It gave me something to think about and they do see like better solutions! I wish the examples looked like these.


Bug: generator crashes at runtime if --host_macos_minimum_os isn't set correctly

Describe the bug
My colleague @cricklet is receiving the following error when trying to build an xcodeproj target:
❯ bazel build //fullscreen:xcode
INFO: Analyzed target //fullscreen:xcode (3 packages loaded, 1499 targets configured).
INFO: Found 1 target...
ERROR: /Users/kenrick/figma/figma/fullscreen/BUILD.bazel:1166:10: GenerateXcodeProj fullscreen/xcode.xcodeproj failed: (Aborted): generator failed: error executing command
  (cd /private/var/tmp/_bazel_kenrick/5bddae61325b18dc7cde052c88d77833/sandbox/darwin-sandbox/193/execroot/figma && \
  exec env - \
  bazel-out/darwin_arm64-opt-exec-2B5CBBC6/bin/external/com_github_buildbuddy_io_rules_xcodeproj/tools/generator/generator bazel-out/darwin_arm64-fastbuild/bin/fullscreen/xcode_spec.json bazel-out/darwin_arm64-fastbuild/bin/fullscreen/xcode_xccurrentversions bazel-out/darwin_arm64-fastbuild/bin/fullscreen/xcode_extensionpointidentifiers external/com_github_buildbuddy_io_rules_xcodeproj/xcodeproj/internal/bazel_integration_files bazel-out/darwin_arm64-fastbuild/bin/fullscreen/xcode.xcodeproj fullscreen/fullscreen.xcodeproj bazel)
# Configuration: b3bf8d2de0ebd02e8c0eca177af5323c5fd8f43503bddf53c8022478b7613a85
# Execution platform: @local_config_platform//:host
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
dyld[48697]: Symbol not found: _swift_isUniquelyReferenced_nonNull
  Referenced from: /private/var/tmp/_bazel_kenrick/5bddae61325b18dc7cde052c88d77833/execroot/figma/bazel-out/darwin_arm64-opt-exec-2B5CBBC6/bin/external/com_github_buildbuddy_io_rules_xcodeproj/tools/generator/generator
  Expected in: /usr/lib/swift/libswiftCore.dylib
Target //fullscreen:xcode failed to build
INFO: Elapsed time: 1.548s, Critical Path: 0.13s
INFO: 2 processes: 2 internal.
FAILED: Build did NOT complete successfully

Reproduction steps

Expected behavior
Xcode project is generated successfully.
Versions

Bazel: 5.2.0
rules_xcodeproj: 019c10ee5f8b6ff74433570311245d2a3df49ea8
rules_apple: 1.0.1
rules_swift: As installed by swift_rules_dependencies from rules_xcodeproj
macOS: 12.1
Xcode: 13.4.1

Additional context
When trying to diagnose the issue, I found https://stackoverflow.com/questions/55550759/swift-why-is-symbol-not-found, but I am not sure how to interpret this. In this case there is only a single macOS version in play, so I'm not sure how Swift 4 and 5 would be getting mixed.

Does setting build --host_macos_minimum_os=12.1 fix it?

That worked, thanks!

Awesome. Hazel defaults the minimum os for macOS to the version of the SDK, and in Xcode 13.4.1 that is macOS 12.3.
By 1.0's release we will precompile the generator as a fat binary, so you won't need this flag anymore.

https://github.com/buildbuddy-io/rules_xcodeproj/issues/223

we will want to support people using non-release versions as well

Or anyone stuck on macOS n-1 for 6 months after any major release :)

The optimized releases would mean that we have a compiled binary and this bug wouldn't happen. So I meant that if someone wanted to use a non-release version of rules_xcodeproj (developers or commit based checkouts) it would be nice if they didn't have to set the flag globally.


Spelling

Generated by https://github.com/jsoref/spelling f; to maintain your repo, please consider fchurn

Rad. Is there a way to automate this check? Some kind of Rake task on Travis CI?

https://github.com/checkstyle/checkstyle/blob/master/.ci/test-spelling-unknown-words.sh is Travis integration I wrote once.


[IOTDB-1230]Support cross multi time partition when loading one TsFile

When load one tsfile which cross multi time partition interval, we first read the tsfile and rewrite it to some new tsfiles according to its belongs time partition.

@HTHou  PTAL

Our common goal is to make iotdb better
@sunjincheng121
Thank you for your sincere suggestions. Your suggestions are very good. Yes, we all hope iotdb will be better and better :).
BTW, I've unified the vocabulary to use spans time partition to represent one tsfile spans multiple time partitions.
Thank you again for your careful review.

The PR will be merged after the CI completed...


Add cancel button to configuration options popup

This PR renames the OK button to Continue and adds a Cancel button to the configuration options pop-up.
This feature will give the user an option to abort opening the configuration file if they want to. This is an essential helpful feature that was missing in the master branch.
In some windows managers such as Windows I3. The exit button at the top right corner is missing. So this feature becomes crucial there. And even when the exit button is there, it doesn't prevent the opening of the configuration file even when pressed.
Additionally, it will always be possible to close using Keyboard Shortcut. This PR helps accessibility for those who need to use a mouse.

Master

PR

Concept ACK. Can remove extra QMessageBox::Ok

I agree with the concept proposed @ShaMan239 conceptually, which aborts the opening of the config file in case of keystroke by mistake on the tab.
There are a few points I believe should be addressed here about this window.

The text that appears on the screen on clicking Open Configuration File is a message, meant for the user describing what a config file is. It is a pretty essential message for new users to Bitcoin and are trying to get hands-on experience with GUI. But because of the UI Symbol present in the dialogue, it appears more like a warning than message. This needs to be addressed.

I would like to put forward another approach that might enhance the feature. There are users/contributors who are very much familiar with Bitcoin GUI and hence are aware of what a configuration file is. Getting a message every time they try to open the configuration file can get irritating at some point.
Adding a Do not show this message again option will resort to it. This will allow the user to allow the UI to show this message or NOT to show this message based on their preference. If a user checks this option and proceeds, they will not be shown this message ever again unless they change the setting back manually. I believe this will serve both the purpose of why this message was placed in the window in the first place (to provide an important message to new users) and providing existing experienced users with an option to turn it off forever.

Please let me know your views on the suggested addition. If it looks good, we could work on it together :)

@jarolrod,

To address this let's just not use any icons.

I like this idea better. That might clear the confusion and depict it like a message as it is supposed to be.
Also would appreciate it if you could provide your views on the Do not show this message again I have mentioned above?

In the PR description

there is a "Close" button. Is it a correct screenshot?

Updated from f9ff47c6ed77cb6502f42fc37c7aa71ca92af476 to 25bee9251374fa78d19077f2fb5fa0bfc5d651a2 (pr391.01 -> pr391.03)
Addressed comments of @JarolRod, @PSancheti, and @Hebasto
Changes made are:

Removed Icons for Buttons
Changed ordering of button to now match the sequence of open and cancel button of the parent option dialog box
Fixed Clang formatting

there is a "Close" button. Is it a correct screenshot?

The PR description was erroneous and is now updated.

qt/optionsdialog.cpp: In member function ‘void OptionsDialog::on_openBitcoinConfButton_clicked()’:
qt/optionsdialog.cpp:308:18: error: unused variable ‘close_button’ [-Werror=unused-variable]
     QPushButton* close_button = config_msgbox.addButton(tr("Close"), QMessageBox::RejectRole);
                  ^~~~~~~~~~~~

Updated from 25bee92 to 13930ea (pr391.03 to pr391.04)
Addressed this comment by @hebasto
Changes made:

Removed the added Close button to be declared as a separate variable, which corrected the `unused variable warning.

Updated from 13930ea to bb17cd8 (pr391.04 -> pr391.05)
changes: addressed this change suggested by @jarolrod

Updated translator comments.

Updated from bb17cd8 to ddec692 (pr391.04 -> pr391.05)
changes: addressed this and this changes suggested by @jarolrod

Updated translator comments.
Removed unnecessary comment about action role.

Thanks, @jarolrod  for the suggestions.

Updated from ddec692 to 4a0b791
The first force commit was pushed by mistake, and the second one is a correction to it.
For the reviewers: There are no changes made by the above two commits

tACK  4a0b791
This window looks good now without the confusing icons. PR functions as intended.
Screenshot of current window:

@GBKS @bosch-0
Could you look into this PR, please?
What, in your designer's opinion, is the best text on:

the button which continues the procedure and actually opens the bitcoin.conf file
the button which aborts the procedure of opening the bitcoin.conf, and returns the GUI to the previous state

?

How about "Continue" and "Cancel"?
Just as a side note, on my Mac, the pop-up does not have a title, so I don't see the text "Configuration options" shown in the screenshots above.

Updated from 4a0b791 to 52aec5dd2338a3af627a6897dd5efe59a928bd10 (pr391.05 -> pr391.06)
Addressed @GBKS and @jarolrod comments. Thanks, @GBKS, for taking the time to review this PR and giving your valuable suggestions. Thanks, @jarolrod, for suggesting the appropriate changes in the translator's comments that I had missed earlier.
Changes:

Updated buttons names from “Open” and “Close” to “Continue” and “Cancel.”
Updated translator comments as per @jarolrod suggestions.
Updated PR description accordingly

Updated from 52aec5d to 0b869df1c913839855148d728514c76ba7664092 (pr391.06 -> pr391.07)
Addressed 1 and 2 comments by @hebasto
Changes made:

Rewritten Translators’ comment to now be not addressed to a second person
QMessageBox config_msgbox -> QMessageBox config_msgbox(this) to preserve behavior.

Thank you very much to everyone who had given their valuable time to review this PR.


feat: create the home page

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 17 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-4.4%) to 76.37%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/service_worker/index.ts
0
2
0.0%

src/home/index.tsx
0
15
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-4.4%

Covered Lines:
193

Relevant Lines:
258

💛  - Coveralls


dotnet test from the solution directory

The current topic (for xUnit, perhaps NUnit and MSTest as well) remark that the dotnet test command must be executed from the test project's folder, which was true prior to the release of 15.9.

From the PrimeService.Tests folder, ...

https://youtu.be/9Bhp8tw9wEw?t=818

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

ID: e39c2f1b-f41a-bdf9-2646-09379941453d
Version Independent ID: 422811cb-6287-03af-ba8d-1daebee9744d
Content: Unit testing C# code in .NET Core using dotnet test and xUnit - .NET Core
Content Source: docs/core/testing/unit-testing-with-dotnet-test.md
Product: dotnet-core
GitHub Login: @ardalis
Microsoft Alias: wiwagn

Good catch!

Props @RehanSaeed! 🎸


2x2 page alignment issues

Hi recently the 2x2 conversion is working very weird. The first 9pages are done properly and from then onwards the pages looks very small. Here in the attached file you can see after the page 8 all the images in each page looks very small compared to that from pages 1-8. I converted a 236 pages pdf document to 2x2 for printing purpose. Please look into this issue.
2x2.pdf

Hi there, does it occur when only converting to 2x2 without inverting?

yes tried without inverting.. its still the same.. also tried reducing the pages.. did a 63page 2x2 conversion.. same result.. now from my experiments i can say it happens after page 9 so if i do 2x2 of single pdfs then there is no problem cuz single pdfs doesnt contain many pages. So idk whats the issue here but i also tried doing 2x2 from another website that is https://pdfresizer.com/multipage  .. same issues i am facing.. maybe the issue is with my source files although i will try converting pdfs from other sources and tell you. but i have been using this method since months nothing happened till now..


Adding option to rescale time series instead of clipping them

Issue #, if available:
When generating time series with ComplexSeasonalTimeSeries, if the range [min_val, max_val] isn't symmetric the time series are clipped. E.g. with the range [0, 10] all the negative values become 0 which is sometimes undesirable.
Description of changes:
Adding the possibility to rescale the time series in the range [min_val, max_val].
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Job PR-114/1 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-114/1/index.html

Codecov Report

Merging #114 into master will decrease coverage by 0.06%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
- Coverage   79.05%   78.98%   -0.07%
==========================================
  Files         110      110
  Lines        6301     6306       +5
==========================================
  Hits         4981     4981
- Misses       1320     1325       +5

Impacted Files
Coverage Δ

src/gluonts/dataset/artificial/_base.py
31.7% <0%> (-0.47%)
:arrow_down:

@SSappy actually, it looks like some dataset is generated in the tests, but nothing is really tested, see here: https://github.com/awslabs/gluon-ts/blob/master/test/dataset/test_loader.py#L77
Maybe you could write a dedicated test for this? Such as, a test asserting that the produced time series have the desired features (min & max values, min & max length, and so on).

Job PR-114/2 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-114/2/index.html

Job PR-114/3 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-114/3/index.html

Job PR-114/4 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-114/4/index.html

Job PR-114/5 is complete.
Docs are uploaded to http://gluon-ts-staging.s3-accelerate.dualstack.amazonaws.com/PR-114/5/index.html

Codecov Report

Merging #114 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
- Coverage   79.05%   79.01%   -0.04%
==========================================
  Files         110      110
  Lines        6301     6305       +4
==========================================
+ Hits         4981     4982       +1
- Misses       1320     1323       +3

Impacted Files
Coverage Δ

src/gluonts/dataset/artificial/_base.py
32.08% <0%> (-0.09%)
:arrow_down:


Leetcode Question Number 44

Leetcode Question Number 44 soultion needs to be added in the repo .
The link for the question is this.
Accepted Languages C++ / JAVA .
You Only need to add the  class Solution in the file.
Make Sure you have read the contributions guidelines before creating an PR.

Assign me


Webhook requests are not being pruned

Describe the bug
Postal has a cron job that prunes old, unexecuted webhook requests, and uses the following line:
@database.select(:webhook_requests, where: { timestamp: { less_than: 10.days.ago.to_f } }, order: "timestamp", direction: "desc", limit: 1, fields: ["id"])
However, webhook_requests does not have a timestamp column. It does, however, have a created_at column. The payload has a timestamp key.-
Expected behaviour
A clear and concise description of what you expected to happen.
Environment details

Version 2.1.4

Other info
The following would probably work instead:
last = WebhookRequest.where(created_at: ..10.days.ago).order(created_at: :desc).limit(1).pluck(:id).first

I think you'll find there are multiple tables of webhook_requests, one variety is in the individual message databases and the other is in the main database.
Unfortunately they have different schemas so you're wrong in that the individual message databases version seems to be getting cleaned up.
But you're right in that nothing seems to be clearing out the one in the main database, I can see some really old entries in ours but I'm not sure why they are there at all and there are some very large gaps in the IDs so something is intermittently cleaning them up.

@willpower232 ahh of course!
I think I'll add then some cron job of my own.


Workaround for ES modules

if using  "type": "module" in package.json then
import { PartitionResponse } from "unstructured-client/dist/sdk/models/operations/";
needs to become
import { PartitionResponse } from "unstructured-client/dist/sdk/models/operations/index.js";
else error
Directory import ".../node_modules/unstructured-client/dist/sdk/models/operations" is not supported resolving ES modules imported from .../.netlify/functions-serve/upload/netlify/functions/upload.mjs
Did you mean to import "unstructured-client/dist/sdk/models/operations/index.js"?

Consider giving out of the box support for ES module.

Hi there! I've looked into this, and the autogenerated client here has been designed to be ESM compatible. Barrel files are not supported and so index.js will have to be a direct import.


TKML tool not showing global args in help menu

Description
Management tools are not showing global args in help menu, resulting in a poor user experience.
Example
turnkey cache --help
usage: turnkey cache [-h] (-b BUILD_NAMES [BUILD_NAMES ...] | -a) (-l | -s | --delete | --clean)

options:
  -h, --help            show this help message and exit
  -b BUILD_NAMES [BUILD_NAMES ...], --build-names BUILD_NAMES [BUILD_NAMES ...]
                        Name of the specific build(s) to be operated upon, within the cache directory
  -a, --all             Operate on all the builds in the cache
  -l, --list            List all of the builds in the cache
  -s, --stats           Print the collected stats for the selected build(s)
  --delete              Permanently delete the selected build(s)
  --clean               Remove the build artifacts from the selected build(s)

Should be something along the lines of
turnkey cache --help
usage: turnkey [--cache-dir CACHE_DIR] cache [-h] (-b BUILD_NAMES [BUILD_NAMES ...] | -a) (-l | -s | --delete | --clean)

positional arguments (to be used before the tool 'cache '):
  cache_dir          Path to the cache directory

options:
  -h, --help            show this help message and exit
  -b BUILD_NAMES [BUILD_NAMES ...], --build-names BUILD_NAMES [BUILD_NAMES ...]
                        Name of the specific build(s) to be operated upon, within the cache directory
  -a, --all             Operate on all the builds in the cache
  -l, --list            List all of the builds in the cache
  -s, --stats           Print the collected stats for the selected build(s)
  --delete              Permanently delete the selected build(s)
  --clean               Remove the build artifacts from the selected build(s)

Unassigning myself because I dont promise to get this done before pat leave. It's a stretch goal for me.


Version 0.40.0 gives 12 issues in xcode

Straight from init a new project and opening it with Xcode and running it in the iOS simulator I get 12 issues in Xcode, and this is without changing any code.
Did not get any issues with version 0.39.0

––––––––––––––––––––––––––––––

React Native version: 0.40.0
Platform: iOS
Operating System: MacOS

Maybe some modules are affect by this?
https://github.com/facebook/react-native/releases/tag/v0.40.0

Maybe some modules are affected by this?
https://github.com/facebook/react-native/releases/tag/v0.40.0

No modules, I get this straight from initializing the project, so it's clean. No code changed, no modules, nothing. This is the files originally created.

Those are warning and you can mostly ignore those warning. You project should run fine with those warning.

It would be great if someone can send a PR to fix those warning, from the screenshot it seems pretty straightforward.

also these problems? when i use 0.40, some third packages are wrong

For the RCTExecuteOnMainThread warnings, the deprecation warning states:
RCT_EXTERN void RCTExecuteOnMainThread(dispatch_block_t block, BOOL sync)
__deprecated_msg("Use RCTExecuteOnMainQueue instead. RCTExecuteOnMainQueue is "
                 "async. If you need to use the `sync` option... please don't.");

the two uses that are generating warnings are in RCTUtils.m and are low level functions for getting screen scale and size -- they both have many callers that expect a synchronous method signature.
// RCTUtils.m

CGFloat RCTScreenScale()
{
  static CGFloat scale;
  static dispatch_once_t onceToken;
  dispatch_once(&onceToken, ^{
    RCTExecuteOnMainThread(^{
      scale = [UIScreen mainScreen].scale;
    }, YES);
  });

  return scale;
}

CGSize RCTScreenSize()
{
  // FIXME: this caches the bounds at app start, whatever those were, and then
  // doesn't update when the device is rotated. We need to find another thread-
  // safe way to get the screen size.

  static CGSize size;
  static dispatch_once_t onceToken;
  dispatch_once(&onceToken, ^{
    RCTExecuteOnMainThread(^{
      size = [UIScreen mainScreen].bounds.size;
    }, YES);
  });

  return size;
}

I understand why we don't want to make synchronous calls on the main thread. Is this an exception? Would the preferred approach be to dispatch directly from these two functions instead of using the deprecated function? Or is the solution to refactor all callers to handle an asynchronous method signature?

In this case we might want to silence the warning since there isn't an alternative to this.

Another option (maybe better) would be to create RCTExecuteOnMainQueueSync that does what RCTExecuteOnMainThread(block, YES) does. RCTExecuteOnMainQueueSync could have a comment that says you shouldn't use it unless you know what you are doing.

Thanks for the info @janicduplessis.
It's 2am in Portugal so I'm gonna call it for tonight but will implement this suggestion and submit tomorrow, although I'm not sure the issue will still be there by then judging by the trajectory @rh389 is on with these warnings :)

Haha I'm also about to call it a night (UK) - I'll leave the RCTExecuteOnMainThread warnings to you as I was unsure how to handle those myself. The event dispatcher one is also tricky since switching to a scoped event would be a BC.
Some progress though - if these go through it's 8 down, 4 to go.
https://github.com/facebook/react-native/pull/11797
https://github.com/facebook/react-native/pull/11798
https://github.com/facebook/react-native/pull/11799

https://github.com/facebook/react-native/pull/11806 and https://github.com/facebook/react-native/pull/11807 just leaves the RCTExecuteOnMainThread and sendDeviceEventWIthName deprecation warnings.
I'm going to take a break for now and do something I'm paid for ;). Will revisit this in a day or two if there's still anything outstanding.

Thanks a lot for working on this :)

Ok so in latest release, 0.41 warnings are still there.
So basically my question now is if it's something I should worry about, or should I just try to mute them out?

Most of them are fixed in master, I think these commits didn't made it to 0.41 sadly. You can just ignore them.

@janicduplessis I'd appreciate your thoughts on the last one remaining (last I checked). sendDeviceEventWithName is deprecated, apparently RCTUIManager should switch to module-scoped events instead. That in itself would be a small BC but probably acceptable.
The messy part is that this would diverge from the way Android emits the same events. AFAIK Android has no similar mechanism for module emitters and everything's global there. So the listening side, Dimensions , for example, would have to fork by platform, and must be aware of UIManager
If global events are genuinely deprecated (ie, will be removed) in iOS then this is something we've just got to do, and hopefully Android will catch up some day. If global events are going to hang around for a while yet, we might be better suppressing this warning until there's an Android equivalent. Or do we just take the plunge now and accept a bit of inconsistency?

Hey, @rh389, @janicduplessis does this seem sensible?

@janicduplessis I'm still getting very similar errors in 0.43.2. Is this still a valid issue?

@janicduplessis If I sent a pull request to remove all of these deprecation warnings, how long might it take for that to be accepted?

I think the only outstanding deprecation already has a PR https://github.com/facebook/react-native/pull/12209.
Many of the unused param warnings only appear in release builds because they're due to debug checks that get preprocessed away. I guess it should be possible to suppress that warning via a compiler setting for release only.

@rh389 Ah great, thanks.
Yeah that would be great if they could be suppressed. There's a lot of noise when I build the project in Xcode, and I have to scroll down a long way to see the actual errors.

@ndbroadbent, you can actually filter to show only errors and not warnings in XCode.

It's the second icon on the right.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with Canny! Check out its new home: https://react-native.canny.io/feature-requests/p/version-0400-gives-12-issues-in-xcode

This issue is still valid, actually, I got closer to 100 warnings and a couple of "Logic errors" - from a fresh install! Those are noisy when trying to develop native components.
@rh389 said many where due to automatic release pre-processing. To suppress these warning - ONLY ON THE REACT STUFF - ie. not on your own code; change build settings for the relevant targets:

https://stackoverflow.com/questions/7997636/disable-warnings-in-xcode-from-frameworks

Confirm this issue still appears on React-Native "0.55.4". 170 warnings

Please give 0.56.0-rc a try - this is specifically called out in the changelog.


feat(TripPlan.Feedback): save/modify responses

Summary of changes

Asana Ticket: Trip planner feedback backend
Recommend reviewing by each commit, as the total set of changes ended up on the larger side.
Changes on the feedback form are propagated to the frontend via two new routes. The form response is combined with a metadata representation of the trip plan, compressed into a binary and saved into our S3 bucket with a unique identifier meant to capture (a) the respondent, (b) the index of the particular itinerary being commented on and (c) the timestamp when the set of itineraries was generated. Whenever the form is modified, the corresponding object is also modified – or deleted, if the user unselects the previously-selected thumb up or down button.

General checks

[x] Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
[x] Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
[x] Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

It works fine locally, but will need https://github.com/mbta/devops/pull/1586 before deploying.


code --no-sandbox --user-data-dir=~ opens to blank window as root

Type: Bug

log in as root
apt -y reinstall ./code_1.79.1-1686587647_amd64.deb
code --no-sandbox --user-data-dir=~

VSCode opens a window frame with only a menu and blank workspace, no status bar, no side bar. None of the menu items work when clicked. The UI is fully broken.
2023-06-14 10:42:49 root@control-tower:~# apt -y reinstall ./code_1.79.1-1686587647_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'code' instead of './code_1.79.1-1686587647_amd64.deb'
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
Get:1 /root/code_1.79.1-1686587647_amd64.deb code amd64 1.79.1-1686587647 [95.9 MB]
(Reading database ... 108537 files and directories currently installed.)
Preparing to unpack .../code_1.79.1-1686587647_amd64.deb ...
Unpacking code (1.79.1-1686587647) over (1.79.1-1686587647) ...
Setting up code (1.79.1-1686587647) ...
Processing triggers for shared-mime-info (2.0-1) ...
Processing triggers for mailcap (3.69) ...
Processing triggers for desktop-file-utils (0.26-1) ...
W: Repository is broken: code:amd64 (= 1.79.1-1686587647) has no Size information
N: Download is performed unsandboxed as root as file '/root/code_1.79.1-1686587647_amd64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
2023-06-14 10:46:52 root@control-tower:~# code --no-sandbox --user-data-dir=~
2023-06-14 10:48:16 root@control-tower:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
2023-06-14 10:54:35 root@control-tower:~# cat /proc/version
Linux version 5.10.0-22-amd64<EMAIL_ADDRESS>(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.178-3 (2023-04-22)
2023-06-14 10:54:48 root@control-tower:~#

/duplicatte https://github.com/microsoft/vscode/issues/184687


All deciduous and permanent tooth codes have been corrected to the most granular codes.

One of the CLI arguments is --image-type. However, a new user would not know the allowed values for this field.

Teeth are not part of the requirements.


Unable to obtain matrix information for image

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:  Chrome/108.0.5359.215
Operating system and its version:  win10
PDF.js version:   "pdfjs-dist": "^4.0.269"
Is a browser extension:

Steps to reproduce the problem:
1.
const image = page.objs.get(imageName);
const bmp = image.bitmap;
console.log(bmp)
2.
What is the expected behavior? (add screenshot)
Hope to obtain matrix information of image deformation and correct width/height

What went wrong? (add screenshot)
Unable to obtain matrix information and correct width/height for image deformation

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

Attach (recommended) or Link to PDF file here:

This part of the ISSUE_TEMPLATE is always required in order for any issue to be actionable/valid.

Steps to reproduce the problem:
[...]

Please note https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.


Made grammar changes to line 32 added "the values"

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ xx] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


OVDB-45: Collapse houdini/ and maya/ subdirectories

This eliminates the unnecessary openvdb_houdini/houdini/ and openvdb_maya/maya/ subdirectories by merging their contents into their respective parent directories.

@pcucka - this didn't build the Circle check. Can you unfollow your personal fork of OpenVDB in your personal CircleCI account and then push an empty commit to trigger a new build please?

I'm planning to merge this today.  Please let me know ASAP if you want me to wait.

I'm planning to merge this today. Please let me know ASAP if you want me to wait.

I just tried to combine your change here and #404 (which touches every single SOP) and git was smart enough to handle it without conflicts. Sounds good to me. :+1:

Thanks for confirming that!  Hopefully this won't be disruptive for anyone.


Add release target for workbench-session-init image

Follow-up to https://github.com/rstudio/rstudio-docker-products/pull/862 to add the release build for the Workbench session init container image.
We're only building the session components for 2024.11.0, so I added a new WORKBENCH_SESSION_INIT_VERSION variable that gets the daily version. Once we release 2024.11.0 and update RSW_VERSION in this repo, we can remove it and update the target steps to use the default release version.
I think this will also require a new repo rstudio/workbench-session-init to be added to our Docker hub.
Part of https://github.com/rstudio/rstudio-pro/issues/6920

I'm wondering if it would be better to hold off and put this in  along with the updates we normally do for the Workbench release. That way we wouldn't need the interim WORKBENCH_SESSION_INIT_VERSION variable as a workaround for the fact that the release version is currently still 2024.09


RessourceDefinition the defaultLink should be LinkType.DETAIL more than EDIT

@ismaelguerrib I disagree as most of entities do not have detail pages. Usually the detail page concerns only the 2 or 3 most important entities whereas most of entities have edit pages.
Feel free to open this topic in discussions if you want to.


Handling signals

We are using Ansible to power up one of the Custom library written in Python. Ansible API has to have a callback registered to tap into the Results so in handling this i noticed that in Ansible code, they actually have a hard coded time.sleep(0.0001) if they dont see a result and check back again
the problem is this triggers a signal to Robot and it stops execution. Can someone enlighten me on the signal handling mechanism in Robot? Pls point me to something if a doc/note already exists
Traceback (most recent call last):
23:11:33   File "////local/lib/python2.7/site-packages/ansible-<IP_ADDRESS>-py2.7.egg/ansible/executor/process/result.py", line 109, in run
23:11:33     time.sleep(0.0001)
23:11:33   File "////local/lib/python2.7/site-packages/robotframework-3.0-py2.7.egg/robot/running/signalhandler.py", line 43, in call
23:11:33     self._stop_execution_gracefully()
23:11:33   File "/**/local/lib/python2.7/site-packages/robotframework-3.0-py2.7.egg/robot/running/signalhandler.py", line 46, in _stop_execution_gracefully
23:11:33     raise ExecutionFailed('Execution terminated by signal', exit=True)
23:11:33 ExecutionFailed: Execution terminated by signal
23:11:44 Execution forcefully stopped.

time.sleep() shouldn't itself send signals, but apparently some code sends SIGINT or SIGTERM. How Robot handles them is explained here:
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#stopping-test-execution-gracefully

Closing due to lack of new information.


Linux to On-Prem: Task zip empty

Hi,
I have installed vsoagent on RHEL6 with node 4.2.5.
When I start a build then it complains: Could not find task: _work/tasks/Maven/1.0.13/task.json
I looked at the zip file in the same directory and it is empty (size 0).
Is there a way to solve this?
We are offline, the server does not have any connection to internet and the vso agent is connected to tfs 2015
Jan

We were looking at a separate case yesterday with the same issue.
We think it's a name resolution issue.  If you could help us confirm, that would be great.
What happens is the server sends an url to the agent for downloading the task (we download as build job demands).  That url I think is based on what's in the notification field in the TFS admin console (that field represents what others know the server url to be - reachable by everyone because that's what we will put in emails etc...).
If the agent can't resolve the name in the url (let's say it's http://mytfsserver:8080 but you're addressing via ip or dns/hostname from Linux) then downloading the task fails and you end up with a 0 byte zip file on disk.  You can delete _work/tasks and it will download again if the root issue is addressed.  I have a bug to make it robust to failures (write to temp dir and rename etc...)

So - the action item is - look at the notification url in the admin console (and maybe the server url).  Are those resolvable from your Linux machine?  If not, a host file change to confirm the issue and don't forget to delete _work/tasks folder

We may have found the issue.  Can you verify by commenting out part of a function
In agent/taskmanager.js at line 119, you see this function.  Comment out the first check block
TaskManager.prototype.getTaskDefinitionsUri = function () {
    var taskDefinitionsUri = this.executionContext.variables[cm.vars.systemTaskDefinitionsUri];

/*
if (!taskDefinitionsUri) {
taskDefinitionsUri = this.executionContext.variables[cm.vars.systemTfCollectionUri];
}
*/
if (!taskDefinitionsUri) {
taskDefinitionsUri = this.executionContext.config.settings.serverUrl;
}
return taskDefinitionsUri;
};

I will need to check at work. (un)fortunatly I am off until tuesday.
the issue with the URL could be it. We have a port redirect over an F5. So TFS thinks it is on port 8080 while the agent is connected over port 80 to the F5.
I believe the task should be downloaded from the location of the URL that you need to enter when connecting with the server, not via a property coming from the server. That would eliminate such an issue.

I agree.  Should be the host from what you entered and relative path to task sent from server.
I will fix the bug I mentioned above and take a crack at using the host by Tuesday.  Will reply when it's in.  You'll want to stamp out a new agent.  Read instructions because I also wrote docs specifically for on prem this week

I fixed this.  Get a new agent.  I would recommend installing the preview one (see instructions)

Ok it seems to work!

Awesome.  Thanks for confirming


v0.37/v0.38: Changelog should document all API-breaking changes

The changelog for release v0.37 does not include information/documentation about changes in some publicly exported APIs. This was reported by the SDK team.
These API breaking changes should be included in changelog/upgrading:

[ ] #747 (v0.38.x)
[ ] added a boolean parameter (terminateOnError) to NewIndexerService. The function creates a new indexer service to index events (#228). (v0.37.x)

Is this issue solved?

@cason not sure about the second one


VP9 support

I bumped into this project just today. I verified VP8 works. Great work Michel !
sudo modprobe v4l2loopback video_nr=10
v4l2compress_vp8 /dev/video0 /dev/video10
v4l2rtspserver -fVP80 /dev/video10
What is involved to add VP9 support? I believe Live555 does support VP9

Hi,
You are right live555 support VP9, but V4L2 kernel include seems to not define it videodev2.h even if it is described in V4L2 documentation
However it is possible to use directly v4l2_fourcc('V', 'P', '9', '0') or define V4L2_PIX_FMT_VP9.
I guess adding support of VP9 is straight forward :

libvpx support VP9 then initialization of codec should be modified in https://github.com/mpromonet/v4l2tools/blob/master/src/v4l2compress_vp8.cpp
live555 support VP9 then initialization of  RTPSink should be added in src/ServerMediaSubsession.cpp and little modification in src/main.cpp

Best Regards,
Michel.

Hi Michel,
I tried making the changes outlined by you yesterday itself and was not successful as the v4l2 kernel module did not recognize VP9 format even after I successfully compiled v4l2compress_vp9
Could you give it a try and see what the issue is ?
Thanks

Hi,
You are right, v4l2loopback doesnot support VP9 v4l2loopback_formats.h , it needs to modify it.
I am making a try and will let you know.
Regards,
Michel

I am still having issues with VP90. VP80 works but VP90 does not
I get an ERROR -- "Cannot set pixelformat to:VP90 format is:BGR4"
anand@saket9:~/rtsp-stuff/v4l2tools$ ./v4l2compress_vpx -f VP80 /dev/video0 /dev/video10
2016-12-01 13:04:00,008 [NOTICE] - src/V4l2Device.cpp:115
driver:uvcvideo 84200001
2016-12-01 13:04:00,008 [NOTICE] - src/V4l2Device.cpp:119
/dev/video0 support streaming
2016-12-01 13:04:00,019 [NOTICE] - src/V4l2Device.cpp:177
/dev/video0:YUYV size:640x480 bufferSize:614400
2016-12-01 13:04:00,029 [NOTICE] - src/V4l2Device.cpp:198
fps:1/30
2016-12-01 13:04:00,029 [NOTICE] - src/V4l2Device.cpp:199
nbBuffer:0
2016-12-01 13:04:00,030 [NOTICE] - src/V4l2MmapDevice.cpp:70
Device /dev/video0 nb buffer:10
2016-12-01 13:04:00,264 [NOTICE] - src/V4l2Device.cpp:115
driver:v4l2 loopback 85208002
2016-12-01 13:04:00,264 [NOTICE] - src/V4l2Device.cpp:117
/dev/video10 support read/write
2016-12-01 13:04:00,264 [NOTICE] - src/V4l2Device.cpp:118
/dev/video10 support output
2016-12-01 13:04:00,264 [NOTICE] - src/V4l2Device.cpp:119
/dev/video10 support streaming
2016-12-01 13:04:00,266 [NOTICE] - src/V4l2Device.cpp:177
/dev/video10:VP80 size:640x480 bufferSize:1228800
2016-12-01 13:04:00,266 [NOTICE] - src/V4l2MmapDevice.cpp:70
Device /dev/video10 nb buffer:8
2016-12-01 13:04:00,267 [NOTICE] - src/v4l2compress_vpx.cpp:186
Start Capturing from /dev/video0
2016-12-01 13:04:00,267 [NOTICE] - src/v4l2compress_vpx.cpp:192
Start Compressing /dev/video0 to /dev/video10
anand@saket9:~/rtsp-stuff/v4l2tools$ ./v4l2compress_vpx -f VP90 /dev/video0 /dev/video10
2016-12-01 13:05:36,616 [NOTICE] - src/V4l2Device.cpp:115
driver:uvcvideo 84200001
2016-12-01 13:05:36,616 [NOTICE] - src/V4l2Device.cpp:119
/dev/video0 support streaming
2016-12-01 13:05:36,627 [NOTICE] - src/V4l2Device.cpp:177
/dev/video0:YUYV size:640x480 bufferSize:614400
2016-12-01 13:05:36,637 [NOTICE] - src/V4l2Device.cpp:198
fps:1/30
2016-12-01 13:05:36,637 [NOTICE] - src/V4l2Device.cpp:199
nbBuffer:0
2016-12-01 13:05:36,637 [NOTICE] - src/V4l2MmapDevice.cpp:70
Device /dev/video0 nb buffer:10
2016-12-01 13:05:36,876 [NOTICE] - src/V4l2Device.cpp:115
driver:v4l2 loopback 85208002
2016-12-01 13:05:36,876 [NOTICE] - src/V4l2Device.cpp:117
/dev/video10 support read/write
2016-12-01 13:05:36,876 [NOTICE] - src/V4l2Device.cpp:118
/dev/video10 support output
2016-12-01 13:05:36,876 [NOTICE] - src/V4l2Device.cpp:119
/dev/video10 support streaming
2016-12-01 13:05:36,876 [ERROR ] - src/V4l2Device.cpp:164
Cannot set pixelformat to:VP90 format is:BGR4
2016-12-01 13:05:36,877 [ERROR ] - src/V4l2Device.cpp:65
Cannot init device:/dev/video10
VIDIOC_STREAMOFF: Bad file descriptor
VIDIOC_REQBUFS: Bad file descriptor
2016-12-01 13:05:36,877 [WARN  ] - src/v4l2compress_vpx.cpp:182
Cannot create V4L2 output interface for device:/dev/video10

Hi,
This is because v4l2loopback doesnot support VP9, you need to modify it, and reload de kernel module.
Doing this, I was able to run v4l2compress_vpx, however I was not able to read the VP9 using ffplay or vlc.
Best Regards,
Michel.

Strange I still see the same error, I pulled v4l2loopback from your repository (git clone https://github.com/mpromonet/v4l2) and added these lines to v4l2loopback_formats.h and reloaded the v44l2loopback kernel modle
#ifdef V4L2_PIX_FMT_VP9
{
.name     = "VP9",
.fourcc   = V4L2_PIX_FMT_VP9,
.depth    = 32,
.flags    = FORMAT_FLAGS_COMPRESSED,
},
#endif /* V4L2_PIX_FMT_VP9 */
Are there more v4l2loopback changes than the one above?

Hi,
This deosnot work because V4L2_PIX_FMT_VP9 is not defined in kernel header.
Instead you could use :
{
.name = "VP9",
.fourcc = v4l2_fourcc('V', 'P', '9', '0'),
.depth = 32,
.flags = FORMAT_FLAGS_COMPRESSED,
},
My fork of v4l2loopback is quite old, and I didnot commit my tries.
Regards,
Michel.

I freshly clone v4l2loopback and added the following lines to v4l2loopback_formats.h
#define V4L2_PIX_FMT_VP9      v4l2_fourcc('V', 'P', '9', '0') /* VP9 /
#ifdef V4L2_PIX_FMT_VP9
{
.name     = "VP9",
.fourcc   = V4L2_PIX_FMT_VP9,
.depth    = 32,
.flags    = FORMAT_FLAGS_COMPRESSED,
},
#endif / V4L2_PIX_FMT_VP9 */
It works now. Thanks. Closing issue


Section doesn't have the correct format and shows the md structure on the index

Where is the problem?
https://learn.qiskit.org/course/ch-demos/estimating-pi-pi-using-quantum-phase-estimation-algorithm
What is the problem?
First section doesn't have the correct format and shows the md structure on the index (left side panel):

What would you expect?
Correct format

I am looking into this as a first issue.


[TASK] Raise compatibility to PHP 7.1-8.4

drops PHP 7.0 compatibility (due to not having nullable types)
introduces PHP 8.4 compatibility

Breaking Changes
ℹ Raised min. required PHP version to 7.1
The following classes/interfaces have been modified.
Individual code that is extending/implementing those components needs to be updated manually.
⚠ \TYPO3\PharStreamWrapper\Collectable
- public function collect(PharInvocation $invocation, int $flags = null): bool;
+ public function collect(PharInvocation $invocation, ?int $flags = null): bool;

- public function findByCallback(callable $callback, $reverse = false);
+ public function findByCallback(callable $callback, bool $reverse = false): ?PharInvocation;

⚠ \TYPO3\PharStreamWrapper\Resolvable
- public function resolve(string $path, int $flags = null);
+ public function resolve(string $path, ?int $flags = null): ?PharInvocation;

hey @ohader
What's the status for this PR? I can't see the issue in the automated tests?
thanks

hey @ohader What's the status for this PR? I can't see the issue in the automated tests? thanks

Hi @HLeithner, the v4.0.0 release has been published (new major version, due to the necessity to introduce breaking changes to interfaces and public API to be compatible with PHP 8.4).

For the records (and others reading this) I'm leaving the PHP 8 note here as well:
The typo3/phar-stream-wrapper is not required anymore since PHP 8.0 in terms of mitigating the insecure deserialization vulnerability. In PHP 8.0 the deserialization process in not invoked automatically anymore, see issue https://github.com/TYPO3/phar-stream-wrapper/issues/64 for details.

thx @ohader for the pr and the head ups.


Start to manage ssh config with home-manager

May relate to #262
macos
Host github.com
  AddKeysToAgent yes
  UseKeychain yes
  IdentityFile ~/.ssh/id_ed25519

ssh sign in git https://docs.github.com/ja/authentication/managing-commit-signature-verification/about-commit-signature-verification 👀

Integrating git sign with ssh will be done in another PR


Elm lacks String -> Number (and Number -> String) functions

Elm does not seem to have a built-in function for converting a string to a number.  I don't think it has a function for converting a number to a string, either (e.g. plainText $ show n ++ " bottles of beer on the wall").
To address the former, we could add the following functions, perhaps to Prelude, Foreign.JavaScript, or even a new "Numeric" module.
parseInt     :: String -> Maybe Int
parseIntBase :: Int -> String -> Maybe Int
parseFloat   :: String -> Maybe Float

Here is the corresponding JavaScript.  We must be careful not to shadow the system parseInt and parseFloat when defining our functions.
function parseIntBase(base) {
    return function(str) {
        var n = parseInt(castStringToJSString(str), base);
        return isNaN(n) ? Nothing : Just(n);
    };
}

...

return {
    parseInt:     parseIntBase(10),
    parseIntBase: parseIntBase,
    parseFloat: function(str) {
        var n = parseFloat(castStringToJSString(str));
        return isNaN(n) ? Nothing : Just(n);
    }
};

Would something like this be good?  Or did you have bigger plans, like a read function whose return type determines behavior.

Since this is still a top Google search result for parsing ints from strings in Elm, readInt has been deprecated. The current function is String.toInt : String -> Result String Int. See the docs here: http://package.elm-lang.org/packages/elm-lang/core/2.1.0/String#toInt

I came here looking for a way to convert Numbert -> String, but no cigar

@rafaeleyng Use toString : a -> String.

@mgold how can converting a number to a String be done now that toString has been removed?

Elm 0.19's String module has functions to convert in both directions.

@mgold but only if you know whether it is an Int or a Float. I'm trying to convert a number to a String and Elm has no way of detecting whether a value is an Int or a Float. You have to know it beforehand.

If you have further questions, please take them over to the discourse.


React only on close inside drawer (by drag or click close)

Looks like onOpenChange trigger when I change the open property, but I want to react only on close inside drawer.
also onClose triggers then I change open to false and it doesn't allow me to make needed flow.

I use open there I pass boolean which check should this drawer be opened or not (I use name of drawer and compare it with state)
then I click on Continue button in drawer it change state to name of another drawer
and onClose I set name of previous drawer
In the current realization of this library instead of opening the next drawer after clicking on Continue button, it triggers also onClose which call change of state which return user to the previous drawer

I made example to demonstrate what all react HTML primitives don't call some onChange callback on value prop changes
https://codesandbox.io/s/blissful-firefly-f32tg3?file=/src/App.tsx

and this is my code that I talked about above:
export const TransactionDetails = () => {
  const [state, send] = useStateMachine();

  const open = state.matches("SEND_TOKEN.TRANSACTION_DETAILS");

  return (
    <Sheet
      open={open}
      onClose={() => send("back")}
      icon="settings_ethernet"
      title="Transaction details"
    >

 send("transactionSubmitted")}
      >
        <Button>Continue</Button>

    </Sheet>
  );
};

export const Sheet: FunctionComponent<Props> = ({
  trigger,
  open,
  onClose,
  icon,
  title,
  children,
}) => {
  return (
    <Drawer.Root open={open} onClose={onClose}>
      {trigger ? <Drawer.Trigger asChild>{trigger}</Drawer.Trigger> : null}
      <Drawer.Portal>
        <Drawer.Overlay className="fixed inset-0 bg-black/40" />
        <Drawer.Content className="bg-white flex flex-col rounded-t-[10px] mt-24 fixed bottom-0 left-0 right-0">

              <Icon name={icon} className="w-6 h-6 mb-4" />
              <Drawer.Title className="text-[22px] font-normal font-['Roboto'] leading-7 mb-[18px]">
                {title}
              </Drawer.Title>
              {children}

        </Drawer.Content>
      </Drawer.Portal>
    </Drawer.Root>
  );
};

Also experiencing this issue.
With shadcn, I used onOpenChange to handle closing behavior for Sheet and Dialog -- calling various clean up functions, and then onClose().
With Vaul, onOpenChange gets triggered immediately when open is set to true, which means the Drawer closes immediately after opening.

Also experiencing this issue.
With shadcn, I used onOpenChange to handle closing behaviors for Sheet and Dialog -- combining clean up functions + onClose().
With Vaul, onOpenChange gets triggered immediately when open is set to true, which means putting the clean up functions inside onOpenChange closes Drawer immediately after opening it.

Also experiencing this issue.
With shadcn, I used onOpenChange to handle modal closing logic for Sheet and Dialog -- combining clean up functions with onClose().
With vaul, onOpenChange gets triggered immediately when open is set to true, so putting the clean up functions inside onOpenChange makes Drawer close immediately after opening it.

Also experiencing this issue.
With shadcn, I used onOpenChange to handle modal closing logic for Sheet and Dialog -- combining clean up functions with onClose().
With vaul, onOpenChange gets triggered immediately when open is set to true. This makes the clean up functions inside onOpenChange close Drawer immediately after opening it.

Fixed in #408


Fix desktop tests

Motivation for this change
https://hydra.nixos.org/build/100471962
https://hydra.nixos.org/build/100471851
https://hydra.nixos.org/build/100472011
A lot of these tests, though strangely not all, were failing at the
$machine->succeed("getfacl /dev/snd/timer | grep -q alice");

step which seems to also be done in the login test.
The same issue popped up there so I duplicated the fix https://github.com/NixOS/nixpkgs/commit/f59b4cb8d545d3bb1bd954f9e3267cb7ebec3557.
In general all these tests could be nicer.
I also took the liberty to bump the memorySize for the xfce tests https://github.com/NixOS/nixpkgs/commit/5b42b1f40158f6ee6277bab8bb59c5360d2153e0 https://github.com/NixOS/nixpkgs/commit/9f43d809b32c7f0ee3ce13ff3a3454ab7e2e9d18 to what all the other desktop tests have.
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Notify maintainers
cc @

cc @andir as you authored https://github.com/NixOS/nixpkgs/commit/f59b4cb8d545d3bb1bd954f9e3267cb7ebec3557 and systemd bump.

I do wonder if we shouldn't default sound to enabled when a DE is activated.

Just realized that certain DE's enable pulseaudio which in turn enables sound. Probably why in certain cases it wasn't failing.

I do wonder if we shouldn't default sound to enabled when a DE is activated.

It's only like that for certain modules with pulseaudio.

I've opted to just enable pulseaudio in those particular tests.

backported in b0e36731a8b7cd110ae20e3a65321c354c3ea688...c6332a7fbfd01673ed552a9e291e87d6f621427a


Warnings from PARAMO vignette

I get the following warnings from the PARAMO vignette when rendering it for the course website:
Warning messages:
1: In FUN(X[[i]], ...) :
  cannot unserialize ALTVEC object of class 'wrap_logical' from package 'base'; returning length zero vector
2: In FUN(X[[i]], ...) :
  cannot unserialize ALTVEC object of class 'wrap_logical' from package 'base'; returning length zero vector

I can't tell how consequential these are, and what I can do to make them go away. If they result in bad output, someone who does not see these warnings needs to render the vignette so it appears properly on the website.

Seems to be related to this problem, will try to figure out but perhaps you can help me by letting me know your sessionInfo and how to reproduce it?

Yes, that sounds like it could be it. I was (am) indeed running R 3.5.x (and this is also the minimum required version in DESCRIPTION). (Specifically, I am running R version 3.5.2 (2018-12-20).) Were you indeed saving the data files from R 3.6.x?
I can post the full session info, but if you're looking for specific packages, I can maybe make it easier by fishing out those versions?

For the record, this wasn't a problem with the PARAMO vignette itself, but with two of the data files it uses.


can't print slide numbers

It doesn't seem to be possible to have slide numbers printed out.
I've implemented a custom Provider that puts props.index into a fixed position on each slide. This works great in normal mode. However, in print mode, this prints as a 0 for every slide.
I tried to rework the page numbers so they are position: relative, but that became a mess and I gave up.

Sorry for the delay! With the way the components are set up, I don't think it's possible to do this in the print view


Modded survivors don't auto sprint any more

Any modded survivor I tried (including bandit, akali, and twitch) doesn't auto sprint anymore after the last update. Before that update they all did perfectly, I get it that they are not "supported" but is there no way to make them work at least the same way they used to?

    Fixed some 1.0 issues.
    Added Captain.
    Removed the very poor partial support for unspecified/custom survivors as it just breaks things.

Sadly it looks like this is intended

It's certainly possible if I can figure a way to make it so that it's not a gamble on if it breaks a character or not. The issue is with skills that work as a "toggle" - think Artificers Ice Wall or Flamethrower. Without a specific workaround, those skills will immediately cast (ice wall) or cancel (flamethrower) if you move, because the mod will make you sprint.
This was the reason Captain was completely broken and unplayable on the old version, because both types of his probe skills work like this.

Is it possible to just have the sprint on custom characters disabled by default and we can then enable it via console command to see if it works for a specific modded character? Many thanks for all the work you've done on the mod so far, it's an essential mod for sure.

Yeah, I thought about a solution for this and I think I might be able to do a config option that can use the name of the survivor to create a list for what buttons allow/disable autosprint. It would still break the toggle type skills, but it would be a much better solution than having either "isn't allowed at all" and "might completely break a character".

Here's the first draft. I thought how to do it and decided to go with a blacklist, custom survivors are enabled by default and can be disabled from the config file. I'm still trying to figure out how I could make it more configurable than a simple enabled/disabled case, such as adding a check to disable autosprint when holding down a button with a certain survivor, which could be an acceptable workaround for some skills.
I know how to do the in-game part, but I need to somehow make it configurable.
https://github.com/JohnEdwa/RTAutoSprintExtended/releases/tag/1.1.0-RC1

Unfortunately my knowledge of C# is severely lacking, so I'm not sure of the correct syntax, however, if it was possible to add third party support perhaps those creating custom survivors could simply add a check for your mod in their script, if at all possible adding an exception while a specific skill was being used. One such example I could think of is the Goku mod, which can sprint while flying, but as it's using ki the whole time, the previous system would break thinking it was a skill, but if Kinggrinyov would specify that sprint can work while using the skill, it would mesh well and be less of a headache for you. I'd say you have this luxury as your mod is looked upon as a necessity by many.
Best of luck, if you need any testing, I'd be willing to lend a helping hand whenever available, I reiterate, my C# knowledge is limited but general logic or in-game testing I can help with.

Could you maybe add a config option to have the sprint key toggle sprint on/off? So that when you're flying you can quickly toggle off sprint and fly then toggle it back on afterwards. It's not a super good solution but, for me at least, it would be better to be able to toggle than hold down the walk button to allow flying to function better.

Give this one a try, I added a new config option called ToggleAutoSprint, which does that. It also overrides HoldSprintToWalk, maybe I'll eventually add the kind of a "tap or hold" thing where tapping toggles and holding doesn't, but that's in the future.
1_1_3.zip


Add CNCF Recommendations for Attribution Notices

Hopefully the community would find this useful as well

thanks @terrytangyuan!


Sync readme with docs

Edit: Changed to just sync the docs with the readme (will move readme to another pr). An automated solution may be better here, but seems fine for now to just update the docs pages.

Hmm, I'm generally pro putting things in the README, since I don't think people will actually go and read the docs. The reason I have a gallery is to try to create credibility for "this library is actually used by real researchers", and the reason I have the tutorials is to nerd-snipe people who want to learn about mech interp, and IMO the README is something such people are likely to read. I'd be pro keeping them in

Makes sense - for now I'll add a quick solution in so that the readme sections and their corresponding pages on the docs site are kept in sync.
In general my approach for starting to use a new lib is this:

Skim the readme intro to understand what it does
Do a few quick checks (e.g. check it's still maintained with recent commits, see if it seems robust)
Skim the API docs to understand what functionality there is
Use the Quick Start to get going and then mostly use code hints (from the docstrings) + the API docs pages.

My thinking is if we can support this flow, and encourage people to follow it, it will help people get to grips with the lib in a faster way. It's also nice for the user if all the important docs are in one place, and then tutorials can supplement this for specific use cases.
Btw I've been adding a bunch of PRs recently and merging (been discussing with @jbloomAus and @bryce13950 a bit behind the scenes as well). If you want to have more oversight into the direction of the docs let me know and I can mark more stuff for review instead.

Hmm, I'm generally pro putting things in the README, since I don't think people will actually go and read the docs. The reason I have a gallery is to try to create credibility for "this library is actually used by real researchers", and the reason I have the tutorials is to nerd-snipe people who want to learn about mech interp, and IMO the README is something such people are likely to read. I'd be pro keeping them in

Switched for now to just sync the docs with the readme (which was more up to date). Will pull the other stuff into a separate PR.


DOC: Added examples to docstrings of DataArray methods

Added examples to the docstring of the following methods:
DataArray.drop_vars()
DataArray.reindex_like()
I will gradually edit this PR and add more examples to other methods.
I'll gladly accept feedback to improve upon my work :)

Great, thank you @DanielGoman !
You might also be interested to look at this other recent PR which also added some examples to DataArra methods. https://github.com/pydata/xarray/pull/7088

Excellent @DanielGoman !
(not to use xarray to tout my personal projects — but re the doctest failures — running https://github.com/max-sixty/pytest-accept over them will auto-fix them, if that's helpful)

I performed doctests on my machine inside a conda venv following the Contributing Guide using Python 3.9, and passed the them.
Yet, it doesn't pass the github tests. Any ideas as to why that might be?

I assume you are on windows? Same always happens to me.

I assume you are on windows? Same always happens to me.

Indeed I am.
Thank you very much, I just tried running the script in the same manner on WSL and that seems to give the expected output.
Any ideas about how to avoid this issue on Windows?

Any ideas about how to avoid this issue on Windows?

I have not figured that out. Usually the difference is small enough to fix it by hand.
Maybe we could add a CI run that generates it and commits a correction if necessary, the same way we do it for black right now.

The documentation of DataArray.interp_like says that the method accepts method='polynomial', but will require the additional argument order.
The issue is that DataArray.interp_like doesn't accept such a parameter, nor do the methods called by it.
Could anybody clarify this please?

I noticed that DataArray.interp_like takes an argument called kwargs, but not in the traditional manner which allows passing keyworded arguments (**kwargs).
If this is the intended behavior then I think kwargs is kind of a misleading name for this argument.

I noticed that DataArray.interp_like takes an argument called kwargs, but not in the traditional manner which allows passing keyworded arguments (**kwargs).
If this is the intended behavior then I think kwargs is kind of a misleading name for this argument.

See #7130

I'm trying to figure out how to add examples to DataArray.cumsum and DataArray.cumprod, but it's not so clear to me.
It seems like they have partially dynamic docstrings. I have found the following script in xarray/core/common.py:
    _cum_extra_args_docstring = dedent(
        """\
        dim : str or sequence of str, optional
            Dimension over which to apply `{name}`.
        axis : int or sequence of int, optional
            Axis over which to apply `{name}`. Only one of the 'dim'
            and 'axis' arguments can be supplied."""
    )

However, it is not clear to me where the rest of the docstring is located, nor where the docstrings of each function (cumsum, cumprod) are located.
I'd appreciate if anybody could direct me to the explanation of this design :)

I'm running into an issue when trying to directly use the DataArray.reduce method.
At first I used DataArray.cumsum to see the expected behavior:
>>> data = np.arange(12).reshape(4,3)
>>> da = xr.DataArray(data=data, dims=['x', 'y'], coords={'x': [10, 20, 30, 40], 'y': [70, 80, 90]})
>>> da.cumsum(dim='x')
<xarray.DataArray (x: 4, y: 3)>
array([[ 0,  1,  2],
       [ 3,  5,  7],
       [ 9, 12, 15],
       [18, 22, 26]])
Coordinates:
  * x        (x) int64 10 20 30 40
  * y        (y) int64 70 80 90

When I'm trying to achieve the same result through DataArray.reduce I'm running into the following crash:
>>> func = xr.DataArray.cumsum
>>> da.reduce(func=func, dim='x')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/mnt/c/Users/GoMaN/Desktop/GoMaN/Projects/xarray/xarray/core/dataarray.py", line 3442, in reduce
    var = self.variable.reduce(func, dim, axis, keep_attrs, keepdims, **kwargs)
  File "/mnt/c/Users/GoMaN/Desktop/GoMaN/Projects/xarray/xarray/core/variable.py", line 1883, in reduce
    data = func(self.data, axis=axis, **kwargs)
  File "/mnt/c/Users/GoMaN/Desktop/GoMaN/Projects/xarray/xarray/core/common.py", line 63, in wrapped_func
    return self.reduce(
AttributeError: 'numpy.ndarray' object has no attribute 'reduce'

Am I using DataArray.reduce incorrectly?
Thanks in advance :)

cumsum will be a lot more work, see ongoing work in #7152 . Thanks for looking in to it.

cumsum will be a lot more work, see ongoing work in https://github.com/pydata/xarray/pull/7152 . Thanks for looking in to it.

I see, thanks for the heads up :)

RTD failure is real:
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7123/xarray/core/dataarray.py:docstring of xarray.core.dataarray.DataArray.drop_vars:32: ERROR: Unexpected indentation.
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7123/xarray/core/dataarray.py:docstring of xarray.core.dataarray.DataArray.drop_vars:35: WARNING: Block quote ends without a blank line; unexpected unindent.
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7123/xarray/core/dataarray.py:docstring of xarray.core.dataarray.DataArray.drop_vars:37: WARNING: Definition list ends without a blank line; unexpected unindent.
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7123/xarray/core/dataarray.py:docstring of xarray.core.dataarray.DataArray.drop_vars:43: ERROR: Unexpected indentation.
/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7123/xarray/core/dataarray.py:docstring of xarray.core.dataarray.DataArray.drop_vars:46: WARNING: Block quote ends without a blank line; unexpected unindent.

RTD failure is real:

Corrected it, now the CI fails on the following:
ImportError: cannot import name 'QUANTILE_METHODS' from 'xarray.core.npcompat' (/home/docs/checkouts/readthedocs.org/user_builds/xray/checkouts/7123/xarray/core/npcompat.py)

Any ideas how to approach this, or is this one of those fails that is sovled by merging with the main branch?

RTD failure is real:

Well I just fixed the issue to that.
Correct me if I'm wrong, but before pushing my corrected version I pulled the latest version from the remote branch, which seems to contain changes that fail the CI.

The QUANTILE_METHODS has been moved and renamed to core.types.QuantileMethods.
Probably something went wrong in the merge.

Since the merge apparently failes, I took the freedom to rebase this from the current master.
Feel free to continue or we merge here :)


vier.be: Unable to extract video id

When trying to download a video from vier.be, the following error occurs:
youtube-dl --verbose http://www.vier.be/deslimstemensterwereld/videos/aflevering-van-13-oktober-kathy-pauwels-kevin-janssens-en-kim-clijsters/1324756
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--verbose', u'http://www.vier.be/deslimstemensterwereld/videos/aflevering-van-13-oktober-kathy-pauwels-kevin-janssens-en-kim-clijsters/1324756']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2015.10.13
[debug] Python version 2.7.8 - Windows-7-6.1.7601-SP1
[debug] exe versions: ffmpeg N-75976-gd59bfcd
[debug] Proxy map: {}
[vier] aflevering-van-13-oktober-kathy-pauwels-kevin-janssens-en-kim-clijsters:
Downloading webpage
ERROR: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "youtube_dl\YoutubeDL.pyo", line 660, in extract_info
  File "youtube_dl\extractor\common.pyo", line 290, in extract
  File "youtube_dl\extractor\vier.pyo", line 43, in _real_extract
  File "youtube_dl\extractor\common.pyo", line 584, in _search_regex
RegexNotFoundError: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

When I try to view in the browser I get this message:

Maak uw gratis account aan zodat u deze volledige afleveringen kunt bekijken.
Met dit account kan u inloggen op zowel VIER en VIJF. Zo blijf je op de hoogte van de laatste nieuwtjes, kan je meespelen met onze wedstrijden en zelf reageren op onze video's en foto's.

Can you watch it in a browser without login with an account?

Now that you mention it, no, you need to login first. Woops. So, I've tried specifying the login credentials with -u and -p but it still didn't work. It gave the exact same error message.

Now that you mention it, no, you need to login first. Woops. So, I've tried specifying the login credentials with -u and -p but it still didn't work. It gave the exact same error message.

Thanks for checking it, we'll need to add login support.

+1 for this!

+1

It seems there's a backdoor for retrieving the playlist bypassing the need for having to log in: https://bitbucket.org/basrieter/xbmc-online-tv/issues/809


Run code for VIN number detection

Can I test code for Vehicle Identification Number(VIN) number recognition.

number of char is important

so how I go ahead Actually I am having 12000 images with groud truth file .


Remove get endpiont

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (104657e) 88.25% compared to head (9cff4ec) 89.58%.
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #477      +/-   ##
==========================================
+ Coverage   88.25%   89.58%   +1.33%
==========================================
  Files          19       19
  Lines        1107     1095      -12
==========================================
+ Hits          977      981       +4
+ Misses        130      114      -16

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[wallet-ext] Add sentry logging to wallet

Description
Describe the changes or additions included in this PR.
Test Plan
How did you test the new or updated feature?

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

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

Release notes

Current dependencies on/for this PR:

main

PR #8602   👈

This comment was auto-generated by Graphite.


High level APIs for train and deploy in notebooks

This is a first attempt at creating high level APIs that hides as much of underlying details as possible. This is currently focused on notebooks with function preprocessor and we will be expanding to other preprocessor and work with python files.

This change is

Some comments from prev PR (now closed) https://github.com/kubeflow/fairing/pull/123#issuecomment-474096863

/lgtm
Will let @r2d4 review and approve as well.


add code completion to e2e test file

What would you like to be added:
Add cypress into tsconfig.json's types
Why is this needed:
To improve intelligent code completion feature in e2e .spec
Additional note:
Currently adding types into tsconfig.json will cause the following issue when running Missing Translation workflow
Error: app/translations/reporter/index.ts(2,21): error TS2307: Cannot find module 'fs' or its corresponding type declarations.

Similar to this https://github.com/DeFiCh/wallet/issues/324

/duplicate in favor #324
Assigned 324 to @kyleleow


[Bug/Feature]: Better Biblatex would export .bib even if uncheck the "keep updated" and "background export"

Debug log ID
983NYQ2T-refs-euc
What happened?
Hello,
There is a bug as we do the steps below:

Start the Zotero,
Click the "File" of the top-left in the Zotero,
Select the "Better Biblatex" for "Format",
Select the "Keep updated" and "Background export",
Select the location where we store the .bib file,
When we modify any information of any references in Zotero, we would find the Zotero modify the .bib file in time,
Deselect the  "Keep updated" and "Background export",
When we modify any information of any references in Zotero, we would find the Zotero still modify the .bib file in time. That is weird.

The bug I reported just contains the step 8.
Thanks.

Maybe I should not choose "On change" of "Automatic export" of Better Bibtex? This function is a little duplicate of  "Keep updated" and "Background export".

What you find weird is just a misunderstanding of what the checkbox "keep updated" means.
The checkboxes in the export screen apply to the export you are doing at that specific point. They bear no relationship to any other export, regardless of whether the file paths happen to be the same.
So in the first export, you check "keep updated", and to Zotero that means "For the collection/library I selected for export, keep exporting them to the file I will select next".
Then you do another export, you uncheck "keep updated", and to Zotero that means For the collection/library I selected for export, export them once to the file I will select next".
So you overwrite the export file once, and then if you next update the collection/library, the promise of the first auto-export kicks in.
If you want to delete auto-export, you have already found them in the preferences, you can delete them there. There is a "Remove" button in the preferences  under the auto-export you set up.
The "on change" option just pauses all auto-exports, it doesn't permanently delete them, so it isn't a little duplicate of the "Remove" button, which removes one auto-export (the one you have selected in the prefs screen).

May you tell me what is the difference between "on change" of "auto export" and "keep updated" in exporting?

"Keep updated" just means "when something relevant changes, schedule an export to reflect this". The "on change" setting concerns when this scheduled export actually happens: on change = immediately, on idle = when you're not using zotero, disabled = only when you explicitly say so. But in each of these cases the export is in fact scheduled to be run after a change.

Thanks a lot. I know now. Regards.

I've updated the docs in the hopes that this is explained better now.
"Background export" is orthogonal to that, it just means that the export (whether auto or not) runs without disturbing the Zotero user interface (which all Zotero exports do except BBT+background). Auto-exports are always done in the background. For manual exports it is user choice.


Added tags as data attribute on post and named classes on tag labels

I think it's beneficial to be able to target specifically tagged posts. For instance, if I wanted to tag certain posts as sponsored and then give them a blue background, I could do the following in css:
section[data-tags~=promoted] {
  background: #c3e9ff;
}

Likewise, I can target the tag label as well:
span.tag-promoted {
  background: #c3e9ff;
}

Coverage decreased (-40.67%) when pulling fa058192429afcf66a629b0a71ef1c33252bcdb5 on ben5516:post_tags into 0ef9ed3f7ae12e5c71fa2d53505ebdc94ab8b4d6 on jipiboily:master.

@jipiboily could you trigger Travis again for this PR?

@msevestre just did. Do you know a way for me to give you access to that on Travis by any chance?