Determine modular scale

What is currently in place is loosely based on the powers of two, as described in Brent Jackson's article, Mathematical Web Typography. The powers-of-two scale produces easy-to-understand numbers (e.g. .25, .5, 1, 2, 4).
We have a few other options to consider:
UNL currently uses a perfect fourth modular scale. Common aspect ratios for photos and videos align nicely with this scale—16÷9=1.777 and 4÷3=1.333.
I've used the golden ratio modular scale in several projects and have found it to work great.
Some might say that the perfect fourth and golden ratio scales produce magic numbers. However, if we're asking framework users to choose from a set of utility classes with pre-determined values for sizing and spacing, is it important to know that the value of a particular class is 1.5 vs 1.777 vs 1.618 when choosing which class to use is relative only to the other values in the set?

Hello everyone, Richard here.
From my understanding of today's (Oct 26) discussion, participants have voiced that font-size values being abstracted into class names might play a more importance role than the actual value itself for the typical framework user. I would agree with that line of thought. I have, at times, apply existing classes to see if they achieve my desired visual effect, and only after I have exhausted my classname options do I specify my own font-size. For the advanced devs, nothing is as easy as going to a website or printing out the scale and sticking it somewhere visible. I have found that after using the same font-sizes couple of times, it just sticks in my head.
I have suggested to @skoolbus39 that he might as well go ahead and try a scale which matches his needs and doesn't have huge negative impact on the existing design that he has created so far. In addition, it be easier on us to judge visually if one scale is superior than the other.
Overall, I think there is quite a number of design factors that hinges on the chosen scale and we should move quickly on deciding one so that if one scale doesn't work, we have enough time to decide on another.

Consensus is to go with the perfect fourth modular scale. Here is the multi-stranded version in use: http://typs.hupkens.be/?b=16&r=0&s=3&or=1&ou=1&ol=0


Add support for running netperf as part of benchmarks.

add --netperf  option to run_peformance_tests.py.   Once enabled, runs netperf TCP_RR as the first scenario and uploads   latency data (50,90 and 99 percentile values) to bigquery.
Tested locally that it works (including uploading to bigquery), but currently the perf workers don't have the right scopes associated to actually upload the data  (only the driver machine has the bigquery scope, and with this the client machine needs to have access to bigquery).

CC @vjpai

LGTM except for nit on netperf execution

Addressed the comment, waiting for tests.

LGTM


Remove unused gen.go file from root

Signed-off-by: Denis Tingajkin<EMAIL_ADDRESS>
Description

Motivation and Context
gen.go file from the root is not used.
How Has This Been Tested?

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[X] Tested locally
[ ] Have not tested

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Changes not related to failed test, merging.


ACCUMULO-3913 Added per table sampling

This a large PR, if you don't have time to look at the impl, a review of the API changes, docs, and test would be very helpful.
I took Readme.sample from this PR and made a Gist out of it so it would render nicely for reading.

Looks like github doesn't want to show me the changes to core/src/main/java/org/apache/accumulo/core/tabletserver/thrift/TabletClientService.java  :(

Made a quick first pass, but I'd like to take a look at the RPC impl. If github won't show it cuz the contents are too big, maybe push this over to RB?

Made a quick first pass, but I'd like to take a look at the RPC impl. If github won't show it cuz the contents are too big, maybe push this over to RB?

I made the changes smaller with 8d6db5d which reverted the automatically generated thrift changes.  Need to revert 8d6db5d inorder to build this branch.   This made git diff  9d25381 | wc go from 13k to 8k.   I think all of the diffs load on GH now.

I think all of the diffs load on GH now.

Cool, thanks Keith. I'll try to take a look at the rest of the changes later today.

Ok, made it through the rest of the diffs. It looks good to me. I mentioned a couple of nits, but I don't think any of them are blockers (I think IteratorEnvironment is already very obtuse). I'll defer to your choice.

thanks for all the feedback @joshelser


Show help for nested subcommands

There's no official way to see help messages for nested subcommands.
The usage for kcctl is easy to view, via kcctl help, kcctl -h, or kcctl --help, and provides a list of all commands along with a brief description of what each does.
The usage for any top-level commands (e.g., kcctl apply) is also easy to view, via kcctl help <command> (e.g., kcctl help apply or kcctl help delete).
If any of these commands contains nested subcommands, the subcommands are listed with a brief description of what they do. For example:
> kcctl help delete
Usage: kcctl delete [<args>...] [COMMAND]
Deletes connectors
      [<args>...]
Commands:
  connector  Deletes specified connector

However, there's no way to get usage information for those nested subcommands that doesn't involve hacks like throwing in an unrecognized flag (e.g., -h) that causes the command to exit with a non-zero status and print an error message. For example:
> kcctl delete connector -h
Unknown option: '-h'
Usage: kcctl delete connector [-e] [CONNECTOR NAME...]
Deletes specified connectors
      [CONNECTOR NAME...]   Name of the connector
  -e, --reg-exp             use CONNECTOR NAME(s) as regexp pattern(s) to apply
                              on all connectors

We should make it as easy as possible for users to learn about the syntax/semantics of subcommands. Some options for this include:

kcctl help <command> <subcommand> (right now this only shows the usage information for <command>)
kcctl <command> help <subcommand> (right now this prints an error message and then the usage information for <command>)
kcctl <command> <subcommand> -h and/or kcctl <command> <subcommand> --help (right now this prints an error message and then the usage information for <subcommand>)
kcctl <command> <subcommand> help (right now this invokes the subcommand with an argument of help)

IMO option 1 has the most intuitive syntax, but may be difficult to implement. Options 2 and 3 are straightforward to implement via the existing CommandLine.HelpCommand class and mixinStandardHelpOptions annotation option, respectively. Option 4 is also straightforward to implement with the CommandLine.HelpCommand class, but is a little uglier as it causes the subcommand to have its own subcommand named help, which pollutes usage messages a bit.
I'd like to implement option 3 unconditionally (-h is a deeply-ingrained reflex for many CLI users), and then either option 1 (if it can be done with reasonable effort) or option 2 (if option 1 can't be done). Interested in others' perspectives!

Thanks for bringing this up! I'd also lean towards option 3.
My initial reaction then was to only support option 3 (as I generally prefer to not offer multiple ways for doing the same thing), but then I noticed that kubectl also supports kubectl help some-command. And as we generally strive towards "intuition compatibility" with kubectl, I think we also should support either 1 or 2 in addition, depending on what kubectl does (couldn't find out with a quick test, does it have sub-commands like we do?), if that's doable with picocli.
In terms of consistency, I feel 2 is better than 1, as it makes help a sub-command of each command, with the name of the sub-command to display the help for being an option to help.

I forgot about the goal of syntax parity with kubectl, that's definitely worth considering.
Based on a single case study of kubectl top and kubectl top node, it looks like they've gone with options 1 and 3:

kubectl help top shows usage info for top, and kubectl help top node shows usage info for top node
kubectl top help node isn't recognized as a valid command
kubectl top -h and kubectl top --help show usage info for top, and kubectl top node -h and kubectl top node --help show usage info for top node
kubectl top help isn't recognized as a valid command, and kubectl top node help tries to run top node with an argument of help

Interestingly, even though it looks like all subcommands implicitly support the -h and --help flags, they are not included in the usage info for anything except the top-level command, and even that only mentions the --help flag.

it looks like they've gone with options 1 and 3

Sweet, then I'd say let's try and do the same, too (again, if we reasonably can within the framework provided by picocli).

Interestingly, even though it looks like all subcommands implicitly support the -h and --help flags, they are not included in the usage info for anything except the top-level command, and even that only mentions the --help flag.

Interesting indeed. If we can, I'd deviate from kubectl's behavior in this case for the sake of consistency and display them in the usage info. Not a super-strong preference though. If you feel it should be different, I'll be happy with that too :)

Great! I agree that it'd be nice to include the -h/--help flags in the usage info for any command that supports them. Will reopen #364 and see if I can clean it up to address the comments left on it.


fix sorting of customer overview

1. Why is this change necessary?
Since shopware 5.3 the newest customers won't be listed as first entries. The sorting was changed to customernumber. This is a problem since the customernumber is optional and can be deactivated in the basic settings.
2. What does this change do, exactly?
Change the sorting to firstlogin (= creation date)
3. Describe each step to reproduce the issue or behaviour.
Add a few customers and change one customernumber to 99999, this entry will be listed as first customer in the grid
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/SW-19907
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-21182
Please use this issue to track the state of your pull request.

Hi @mnaczenski, thank you for your PR! We'll close it as agreed!


ROS service headers not visible to tango_ros_streamer package

Issue: When cloning the repo, the header files, generated from the ROS services (*.srv files) are not visible to the tango_ros_streamer package. "catkin build" will fail on this package.
Hacky fix: Copy the include files (which are really just symlinks) from ".../tango_ros_ws/devel/include" to ".../tango_ros_ws/src/tango_ros/third_party/roscpp_android_ndk/include".
How would this be properly fixed? I had a look at some package.xmls and CMakeLists.txts, but everything seems OK...

@fishcu Thanks for taking a look, #269 should fix this issue.


Build UI - Eval Form Step 2 - Evaluation Criteria Add/Remove Criteria

What/Why
This task allows the user to create the basics of the criteria as well as add and remove criteria on the form. After this task is complete, valid forms can be created and published, albeit using only the numeric scoring option.
Acceptance Criteria

[x] Initial/empty state:

[x] Add Another Criteria Button adds a new, empty criteria to the form
[x] Delete button removes the criteria from the form

[x] when the last criteria is remove the form will have one criteria in the empty/default state

[x] Close button collapses the options to a single row view ~showing the Title~

[x] Expand displays the options

[x] Title, Description, Points, Scoring Type are required
[x] Numeric type of scoring is selected and functional

Rating and Binary scale are out of scope, if selected nothing happens (the form is always :numeric scoring at this point)

[x] Criteria Points / Weight are positive integers

no decimal or negative numbers may be entered

Disregard the following if this work does not include any UI changes

[ ] WAVE screenshot
[ ] Automated a11y tests (axe-rspec specs)
[x] Keyboard accessibility (tab navigation, form interactions)
[x] Responsiveness at desktop and mobile

Out of Scope


Schema/async request details

DB schema for Proxy  server to store  Async details

Can one of the admins verify this patch?


Add pull-secret window

Ask for pull secret if its not set during start
Be able to change pull-secret from settings window
Ask for pull-secret during setup phase from the welcome screen

@gbraad I think @dgolovin did something similar for vscode-openshift

We added a wizard step that asks for the content of the pull-secret, which then gets stored in the keyring.

@fbricon unfortunately not. We are instead storing the contents in the Windows credentials manager or keychain on macOS. We do have an option for the file, but this is Linux only to be honest.


Layouts location meaning

In #9 I read that process layouts from src/layouts is design concept.
Could you please explain what is the reason of this decision? What advantages does it give?

Just in Metalsmith's src/layouts directory. You can change it. Any other good default that would be good?

I am migrating form 123

Just now was hit by this behavior and default configuration of .pattern = '**' and .layoutPattern = 'layouts/**'.
With next example, you always get error:
src/layouts/test.pug
= date.format()
!= contents

src/index.md
---
layout: layouts/test.pug
data: <Moment.js object initialized by some metalsmith plugin>
---
Some text.

Error
[16:36:14] TypeError: metalsmith_test/src/layouts/test.pug:1
  > 1| p= date.format()
    2| != contents

Cannot read property 'format' of undefined
    at Object.eval (eval at wrap (metalsmith_test/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:6:61)
    at Object.template [as fn] (eval at wrap (metalsmith_test/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:8:77)
    at metalsmith_test/node_modules/jstransformer/index.js:314:30
    at tryCallOne (metalsmith_test/node_modules/promise/lib/core.js:37:12)
    at metalsmith_test/node_modules/promise/lib/core.js:123:15
    at flush (metalsmith_test/node_modules/asap/raw.js:50:29)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickDomainCallback (internal/process/next_tick.js:122:9)

With default configuration during 'Render all individual content' phase, current implementation also tries to render src/layouts/test.pug and gets error because this file doesn't have date metadata.

That is why, it's interesting, what is the reason of this decision? Why don't your plugin read layouts separate from metalsmith files read?

I think this is a design decision. I think everything that's processed by metalsmith should be in the src directory. The benefits out of this are that you can use YAML front-matter in the layouts, pre-compile them for better performance, and even mix them in with the content, if you really wanted.
This isn't stopping you from using something like metalsmith-assets to copy the assets in to have them process with metalsmith-jstransformer though. They just need to become part of the files array before it goes through. Means the plugin doesn't have to read them twice.

gets error because this file doesn't have date metadata.

Did you move the Moment.js metalsmith plugin before metalsmith-jstransformer? The object isn't there, leads me to believe it wasn't created yet. In your layout, you're using data rather then date. Intentional?

Thank you for detailed explanation. It is clear now.
As for my error. First yes data is typo in my comment, in code it is date. The reason of this error is trying to compile layout file as content in processFile function and because it isn't have date property in metadata, pug throws error. I fix it by set more strict .pattern configuration parameter.

Very cool :+1:
What was the new pattern that you used? Out of curiosity.

Because I consider metalsmith-jstransformer convention my contest file name pattern is <name>.html.<transformer> and layout file name pattern is <name>.<transformer>, so for .pattern configuration parameter currently I use **.html*.


Update zio-prelude to 1.0.0-RC27

About this PR
📦 Updates dev.zio:zio-prelude from 1.0.0-RC26 to 1.0.0-RC27
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-prelude" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio", artifactId = "zio-prelude" }
}]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #1320.


Update requirements.md

A quick line under the Ruby environment section to specify a supported version of Ruby.
As indicated here https://github.com/jedi4ever/veewee/issues/774

2.2.0 should be better

Tweaked


I try to get video path, but it don't know how ? onVideoRecorded doesn't return path

Hi @amalnaami  did you get black camera issue.

Hi @whumpentertainment
I record video but it doesn't push me to another page to show it ang doesn't give me a path .
Do you have a path after you recording video

Yes i have path and i don't face any type of path issue. The only issue is black camera issues from back camera on second time.

Hello i'm running the demo, but the onVideoRecorded doesn't triggered after i finish the video recording, any suggestion? Would be awesome if you continue supporting this plugin

Android 10 this issue still remains


Model package e2e

Adds ModelPackage CRD and tests for both unversioned and versioned model packages. Also includes samples for ModelPackage and ModelPackageGroup. Updates sagemaker-controller to the latest codegen and runtime changes.
Do not review/merge until ModelPackageGroup is merged into main and tests are running

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

@akartsky need another review. It's almost ready to merge

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

/test sagemaker-kind-e2e

https://github.com/aws-controllers-k8s/sagemaker-controller/pull/54#pullrequestreview-714193265

Missed addressing this. Not blocking this PR. Lets iterate


feat: DIA-1577: OpenAI usage limits for Trial accounts

Hi @robot-ci-heartex!
This PR was automaticaly generated via Follow Merge.
Please ensure that all linked upstream Pull Requests are merged before proceeding with this one.

https://github.com/HumanSignal/label-studio-sdk/pull/354 linked by Workflow Run

/git merge


[20.03] go_1_13: 1.13.7 -> 1.13.8, go_1_12: 1.12.16 -> 1.12.17 (backport)

Motivation for this change
https://github.com/golang/go/releases/tag/go1.12.17
https://github.com/golang/go/releases/tag/go1.13.8
Backport of #80165
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-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.

This change is

@GrahamcOfBorg build yq-go hugo restic


Catch AttributeError in client connected check

If the client has never connected, there will be no __transport attribute.

Thanks!


SOLR-16270: address dangling javadocs

https://issues.apache.org/jira/browse/SOLR-16270
Description
intellij is warning of "dangling javadocs" and "invalid @returns" tags.
Solution
Fix them!  Make some javadocs actuall inline comments and block comments.  fix the @returns tags.
Tests
manual
Checklist
Please review the following and check all that apply:

[X ] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ X] I have created a Jira issue and added the issue ID to my pull request title.
[ X] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[ X] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

@cpoerschke do you have

Would be tempted to remove the commented out code that "looks like" javadocs due to spotless application.

Would be tempted to remove the commented out code that "looks like" javadocs due to spotless application.

Do you have an example of this?   I wondered about removing commented out tests as well!

I am going to merge this one, and lets have a seperate ticket about commented out code...  Feel free to add it to SOLR-16222 as a subtask.


gtk3: 3.24.38 → 3.24.39

Description of changes
https://gitlab.gnome.org/GNOME/gtk/-/compare/3.24.38...3.24.39
Fixes: https://github.com/NixOS/nixpkgs/issues/274240

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg eval


CI: fix example imports for App as standalone

What does this PR do?
some examples are called part of App full, but there were referring wrong import
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @carmocca @akihironitta @borda @tchaton @rohitgr7

The core of the PR is alright, however it seems that there are some tests failing, @Borda. Those failures seem to originate from incorrect installation as it cannot find some packages

Those failures seem to originate from incorrect installation as it cannot find some packages

if you are talking about these imports in app pytest for monolithic package:
https://github.com/Lightning-AI/lightning/pull/15260#issuecomment-1288578677
I believe these are artifact of meta package and shall be fixed with #15105

Yes, that is from the meta package, but for our own sanity, I'd try to merge with failing CI as little as possible - i.e. merge #15105 first and only if everything works, I'd merge this one.

I'd try to merge with failing CI as little as possible - i.e. merge #15105 first and only if everything works, I'd merge this one.

I would rather do it wise versa, as this is a valid scenario and shall be working since the beginning but we did not validate it... so as far it these LAI jobs are not required it shall not block any development

Those failures seem to originate from incorrect installation as it cannot find some packages

If you are talking about these imports in app pytest for monolithic package: #15260 (comment) ~I believe these are artifacts of the meta package and shall be fixed with #15105~ Interesting problem, but I did not touch the package, so was it ever working?

seems some tests have invalid imports

seems some tests have invalid imports

yes, fixing it now together with @otaj
anyway wondering how was it passed before since the imports were there for a while... :/

all the
E           AttributeError: <module 'lightning.app.XXX' from '/home/runner/work/lightning/lightning/src/lightning/app/utilities/login.py'> does not have the attribute 'YYY'

are artifacts of meta package and will be fixed with #15105

@otaj moving your 44133cb0585627755ae5b5c7f51c5510e8a7f93c to separate branch https://github.com/Lightning-AI/lightning/tree/refactor/monkeypatch
if this is the right way, we shall fix it in many more places... :otter:


Buggy main menu's that don't open

new version no files open.
seems on certain sidebars open and depending on what is selected in those sidebars some upon selected the sidebar auto active things in the sidebar.. but when this occurs some of the main menu's dropdowns become buggy.. ie you can't select the 'File' menu and move the mouse across to the next menu item and have it drop down aswel...
I can't be explain it, test yourself its broken...  select something like the Debug sidemenu, and the top menu's all work fine.. but the 'Search' sidemenu seems broken.. attached screenshots of what the sidebar looks like when the menus at the top are glitchy...
shouldn't be like this at all.

Operating System: win10
Theia Version: Version 1.54.0

VS Code API Version: 1.93.1

does this only occur if you have not opened a folder/workspace?

No it occurrs even with a project and files open

maybe


Add collapsible form part

No. I'm going to close it.
There is an issue if all supposedly collapsed fields are hidden, based on the request type. Fixing this adds more complexity which is not warranted in my opinion.
Since we already have the requestType selection, having 2 axis to display/hide fields is going to generate conflicts.


Potential bug: TaskLoader does not run when patching and using 'Gapfill' samlping strategy

Description
The Taskloader function seems to freeze when asked to generate patched functions using the gapfill sampling strategy:
Reproduction steps
This first example runs fine
# Instantiate task loader
task_loader = TaskLoader(
    context = [modis_ds, amsr_ds] *5,
    target = modis_ds,
    context_delta_t = [-2, -2, -1, -1, 0, 0, 1,1,2,2],
    target_delta_t = 0,
    #links = [(4, 0)],
)
for date in tqdm(dates, disable=not progress):
    tasks_per_date = task_loader(date, context_sampling=["all", "all", "all", "all", "all",
                                                                "all", "all", "all", "all", "all"],
                            target_sampling="all",
                            patch_strategy="sliding",
                            patch_size=0.5,
                            stride=0.25
            )
            for task in tasks_per_date:
                task.remove_context_nans().remove_target_nans()
            train_tasks.extend(tasks_per_date)

But if you call this example, nothing happens:
# Instantiate task loader
task_loader = TaskLoader(
    context = [modis_ds, amsr_ds] *5,
    target = modis_ds,
    context_delta_t = [-2, -2, -1, -1, 0, 0, 1,1,2,2],
    target_delta_t = 0,
    links = [(4, 0)],
)
## Code runs down to here and then stops:
for date in tqdm(dates, disable=not progress):
     tasks_per_date = task_loader(date, context_sampling=["all", "all", "all", "all", "gapfill",
                                                                "all", "all", "all", "all", "all"],
                            target_sampling="gapfill",
                            patch_strategy="sliding",
                            patch_size=0.5,
                            stride=0.25
            )
            for task in tasks_per_date:
                task.remove_context_nans().remove_target_nans()
            train_tasks.extend(tasks_per_date)

Version
Patchwise_train fork, monotonic errors branch,
Screenshots
![DESCRIPTION](LINK.png)

OS
Windows

Could you maybe send your code (privately) so I can see whether this is relating to the datasets used? I haven't been able to replicate this behaviour so far, though using a different dataset I expect.
 I'd like to check 1. Is it really hanging indefinitely, or just taking a long time, and if so 2. where is the freezing happening, is it actually in TaskLoader.__call__?

In running your example @MartinSJRogers , I've tracked the hanging behaviour down to this section of deepsensor.data.TaskLoader.task_generation:
https://github.com/davidwilby/deepsensor/blob/23733df8c0967f33bfabb056d7940df3e76a3f17/deepsensor/data/loader.py#L1367-L1395
In this section keep_searching is never being set to True for some or all of your patches I think, so this while loop just runs indefinitely.
target_mask = added_mask & ~curr_mask
if isinstance(target_var, xr.Dataset):
    keep_searching = np.all(target_mask.to_array().data == False)
else:
    keep_searching = np.all(target_mask.data == False)
if keep_searching:
    continue  # No target points -- use a different `added_mask`

Resolved by #11 - moving the spatial slicing operation after the gapfill operation.
Will also be addressed by #12  - but at a later date.


unify with os-js?

love the work done here, and the user-experience of daedalOS is simply awesome.
however, i also love the work being done at OS.js, mainly the structure, application packaging, etc.
from a community perspective, wouldn't it be awesome if we could all work together and build the best of both worlds?
from a neutral community member's perspective (unaffiliated with either project at the moment), i would love to see daedalOS components and superior look-and-feel contributed into the OS.js structure and packaging model.  that would make for one ass-kicking web-desktop architecture.
see also: https://github.com/os-js/OS.js/issues/800

Thanks! That's a cool idea indeed. OS.js was one of a few projects that inspired me early on in my work on my project.
I do indeed have a plan to make it easier to add 3rd party support to daedalOS, and it would be good if existing OS.js apps/packages had a way to run in daedalOS. Do you have any examples apps worth trying to port as a first attempt? Or any docs about their structure/package model?


Use std bean naming for getters

...as this should make JSON serialization easier later, as getXXX() style getters are auto-included by libraries like Jackson.

Coverage remained the same at 100.0% when pulling 547d7d697652535b34a94f74655764f1ec8bd633 on bean_accessors into 923a10f2dcd3582f90ff562cae1cf084ee94cb68 on main.


"create_source_map: null" trick only works if >1 mapping is specified.

If I only have 1 src->dest mapping specified, setting create_source_map: null in compilerOpts does not generate source mappings, since isMapping (in closureCompiler.js) is set to this.files.length > 1. For example,
closureCompiler: {
  options: {
    compilerFile: '/home/rwsims/tools/compiler.jar',
    compilerOpts: {
      create_source_map: null,
    }
  },
  compile: {
    files: {
      'foo.js': [ 'bar.js', 'baz.js' ]
    }
  }
}

will not generate source mappings; it passes an empty create_source_map flag to the compiler.

You need to set that parameter with the path and name of the map file, something like this:
create_source_map: 'path/to/your/destination/file.min.js.map',

closing due to inactivity, feel free to re-open if the issue persists.


Add support keys that are already unicode encoded and for keys of other types

We bumped into a bug where an already encoded unicode string with unicode characters could not be processed by the keyslot function.
While fixing the bug we also added support for other key types such as float, int, long.
The PR include additions to the unit test for the keyslot function
There was another pull request (#170) that is overlapping, but that didn't cover all cases, had no unit test and was pending since beginning of December. This in PR includes the fix in #170.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

Coverage decreased (-0.1%) to 85.017% when pulling 128b10a9466a6416bacd9c0a6fb6a4c8116c8f43 on VascoVisser:unstable into b14bb5fc6e2939ff065b7aafbc06052a6a31a192 on Grokzen:unstable.

@VascoVisser Looks good from my pov. The 2 things left to do is to add a line in release notes and (optional) add your self to authors list. Will be easily merged after those changes.

Coverage decreased (-0.1%) to 84.351% when pulling b3cc73084134ea24f30af409532a9304f5fd957c on VascoVisser:unstable into 53b8e04bb07121d0a26324422e1b61db431a027d on Grokzen:unstable.

When is this PR planned for merging and release?

@VascoVisser I tried to resolve the conflict that was still present from the webb gui and it caused more issues and a wierd merge commit. I will manually merge this MR later tonight and possibly make a new release becuase there is nothing more pending that i wait for to be able to make a release.

@VascoVisser Manually merged these commits and resolved the minor conflict that was still present from a seperate PR that was merged before.
Commits:

https://github.com/Grokzen/redis-py-cluster/commit/1b175368a96e41d9826b886fcb084e947f1d23d8
https://github.com/Grokzen/redis-py-cluster/commit/06a9c15975bcbf7b760130ac9966ee3439ab8417

Travis testing of 4.0 still compalins becuase the building there is still kinda broken.

Many thanks for the patch :)


Solo question?

When I run the script: python tools/analysis_tools/get_flops.py, but it occur the error "forward_dummy" is not implemented in SOLO?
How to solve it?

@lijoe123 Sorry. Not yet supported.


Template files are confusing

Looking through them, there's a lot of html mixed in with js, and I don't really grok how you separate out text from formatting. Also, there are .html and .tpl templates, and I'm not sure why there's a difference. Is there a better way of doing this?

You are talking about the website......

I'm talking about this: https://github.com/Urigo/angular-meteor/tree/master/.docs/angular-meteor/client/views/steps
That's in this repo, no?

that's the code for the http://angularjs.meteor.com/ site.
There stuff are a bit different because I need to use both Markdown and HTML for angular and Meteor.
I've also haven't updated the site to the new angular-meteor yet.
But it works...

It works, but I think it might be a barrier to having people improve the docs.

yes I have a task to update that.
But first - update videos...


unexpected behavior with unlisted package

This is edge case that probably isn't worth exploring, but I wanted to document what I saw. Trying to update UnionArgParser from 0.8.7, it updates to 0.6.3. The project was unlisted in the NuGet Gallery because of a name change. With 20k downloads, it probably would have been better to mark it deprecated and provide a link to the new package. /cc @eiriktsarpalis
In this case, I simply have to provide the explicit version as a workaround. I find it very confusing that the NuGet API returns the 0.6.3 version at all when it is unlisted.
https://www.nuget.org/packages/UnionArgParser
https://www.nuget.org/packages/Argu
https://github.com/nessos/Argu
PS C:\Tachyus\x> .\tools\paket.exe update nuget UnionArgParser
Paket version <IP_ADDRESS>
Updating UnionArgParser in C:\Tachyus\x\paket.dependencies group Main
Resolving packages for group Main:
 - UnionArgParser 0.6.3
Locked version resolution written to C:\Tachyus\x\paket.lock
1 second - ready.

Closing, as it is probably not worth looking into.


[Doc] Added a missing reference in Live Component docs

Q
A

Bug fix?
no

New feature?
no

Issues
-

License
MIT

Fixes this error:
Found invalid reference "update-parent-model" in file "index"

Thanks Javier.


Improve SSL setup / documentation

It looks like quite a few have problems getting the SSL setup done right:

We could improve documentation but maybe a separate setup ABAP would be helpful that checks parameters and uploads/updates the required certificates.
https://docs.abapgit.org/guide-ssl-setup.html
https://docs.abapgit.org/other-test-ssl.html

@mbtools are you looking into this one?

yes


Cleanup around extractLogSafeErrorProperties

Remove extractLogSafeErrorProperties from common-utils
Small improvements to the code that removes message from stack
Fix semi-recent typo/bug where fetchStack param was no longer ever passed as true

Scoped changes from #6951

@jatgarg - could you take a look at this one and merge it if it looks good?
Or not - it's not a big deal to leave this out for now. If you decide it's not worth it just close it and I'll revisit when I'm back. Thanks!
Cc @anthony-murphy


fix: fix some issues about database generator

What type of PR is this?

/kind bug
What this PR does / why we need it:
This PR fixes some issues about the database generator.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., design docs, usage docs, etc.:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 77.102%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
8667

Relevant Lines:
11241

💛  - Coveralls


Question on quasi-static electromagnetic problem

Hi, everyone
I am trying solve a quasi-static electromagnetic prolem with MFEM. I use the equation is:
$$\nabla \times \mu^{-1} \nabla \times \mathbf{E}+i \omega \sigma \mathbf{E}=-i \omega  \mathbf{J}^{s}, $$
where $\mathbf{J}^s$ is current source. It will be a wire on the ground.
This is a commonly used formula in geophysical electromagnetism.
As shown in the figure below, I plan to simulate the electromagnetic field generated by a long wire source laid on the surface, where the research zone is the main calculation area. The boundary condition of the problem is the Dirichlet condition, so in order to reduce the impact of the boundary condition, a larger extend zone is required.

I built a simple model through gmsh, as shown below.
I refined the tetrahedral cells around the long wire sources and observation points. This can be done by specifying the refined area using gmsh.

I found it difficult to construct the right-hand side term for a long wire source in MFEM, so I first used VectorDeltaCoefficient to construct the right-hand side term. After that, I wrote a program based on the ex22p example. However, I found that although the program could run successfully, the calculation results were wrong.
So, please help me. Please point out the mistakes in my code.
csem_test.zip

Hello, @spvfly,
I think the trouble may be that the VectorDeltaCoefficient is only non-zero at one point. You seem to need a coefficient which is non-zero along a line segment. I don't think we have that in MFEM so you'll need to write a custom VectorCoefficient. The easiest thing to do would be to define a function which is non-zero inside a cylinder with a finite diameter. As long as that diameter is adequately captured by the mesh it should produce the desired result as long as you don't look too close to the cylinder.
It may also be possible to define something similar to the DeltaCoefficient but I think that would require more extensive changes to the library.
Best wishes,
Mark

Hi, @spvfly,
Unfortunately, I cannot reproduce your results. The images I compute appear fine. Here is the E_real just below the xy plane. This was produced by writing the grid functions to disk and visualizing in GLVis.

I used the same command line that you showed above. I did modify the source function's amplitude slightly because my compiler complained about an unused variable. The function apparently computed amp but used a instead. These only differ by a factor of Omega=2pi so my results should be about 6 times larger than yours but the pattern should be the same.
The imaginary part does show large values near the boundary if the limits are set to be between 1e-15 and 1e-7:

But the magnitude of E_real has a maximum near 300 and the solver tolerance is 1e-12 so we should be suspicious of any field values below 3e-10. If we increase the range the image looks more reasonable:

Of course we should compare the real and imaginary parts on the same scale so here is E_real:

I think these look reasonable. Of course the outer region is under-resolved but you expected that. The "research zone" probably looks smoother but I cannot easily restrict the image to that region with GLVis.
Best wishes,
Mark

Hello, @mlstowell,
Thanks again for your reply,
Depending on your answer, I also use glvis to draw E_img and E_real, I set a large range of values and use logarithmic scale colar bar.
E_imag：

E_real：

From the figure, I find that although I set the Dirichlet boundary condition $\bf{n}\cdot\bf{E}=0$, there are still large values on the boundary surface, and only the edges of the model seem to satisfy the constraint of the boundary condition.What causes this?
Best wishes,
spvfly

Hello, @spvfly,
A homogeneous Dirichlet boundary condition in this problem is actually $(n\times E)\times n=0$ which constrains the tangential part of $E$. Along the edges of the domain these constraints combine to produce $E=0$. It is common for the normal component of $E$ to be noticeable on the surfaces of the domain even though its tangential components are zero. In these plots the normal component seems to be around $10^{-10}$ which seems fairly small.
Best wishes,
Mark

Same as the previous question。
Assuming that I use the nedelect type of finite element, the physical coordinates of dof should fall on the edge of the mesh, and the corresponding solution vector corresponds to dof.
After getting the solution vector, I need to calculate the vector value at the mesh vertex, and I found the function
void GridFunction::GetVectorFieldNodalValues(
Vector &val,int comp) const
{
   int i, k;
   Array<int> overlap(fes->GetNV());
   Array<int> vertices;
   DenseMatrix vals, tr;

   val.SetSize(overlap.Size());
   overlap = 0;
   val = 0.0;

   comp--;
   for (i = 0; i < fes->GetNE(); i++)
   {
      const IntegrationRule *ir =
         Geometries.GetVertices(fes->GetFE(i)->GetGeomType());
      fes->GetElementVertices(i, vertices);
      GetVectorFieldValues(i, *ir, vals, tr);
      for (k = 0; k < ir->GetNPoints(); k++)
      {
         val(vertices[k]) += vals(k, comp);
         overlap[vertices[k]]++;
      }
   }

   for (i = 0; i < overlap.Size(); i++)
   {
      val(i) /= overlap[i];
   }
}

It seems that this problem can be solved.
However, I am confused as to why in the functionGetVectorFieldValues(i, *ir, vals, tr); use the FElem->CalcVShape(*Tr, vshape);,  instead of usingCalcPhysVShape.
If I want to get the curl of the field, then I should use CalcPhysCurlShape?

Hi, @spvfly,
This function will probably provide the values you need although if an observation point lies on a processor boundary this function will not average values from different processors. I think each processor will return a separate average. You may need to combine these to obtain useable data.
The "Phys" portion of these function names is not used consistently. In this case CalcPhysVShape simply calls CalcVShape(*Tr, vshape). In order to evaluate the field values in physical space it is usually necessary to provide the element transformation. On the other hand, evaluation in reference space does not require the element transformation. Consequently, in all cases "Phys" functions have an ElementTransformation argument and their reference space counterparts do not. So, "Phys" is redundant and we could just distinguish functions by their arguments. In short, make sure to provide the element transformation and use the function name with the "Phys" nomenclature and you should be fine.
Best wishes,
Mark

Hi, @mlstowell,
In the past few days, according to your answer, I can basically use MFEM to solve my problem. By searching for the grid edge index that coincides with the long wire source, I create a ParGridFunctionrhs and assign the current density at the dof corresponding to the edge, rhs(edge_dof)=j_source.
For the solver, I referred to hertz example and used the solution of FGMRESSolver+HypreAMS.
However, I found that the accuracy of the numerical solution does not seem to be very good as follows. Is there a better solver for quasi-static frequency domain electromagnetic field problems?
Analytical solution
----------------------------
order=1, freq=1000:
-3.49589e-05   -7.61841e-06j
-2.19623e-06   -5.95355e-07j
-5.54844e-07   -3.45684e-08j
-1.25527e-07   +2.97161e-09j
-6.32282e-08   +3.73476e-10j
-1.88706e-08   -7.17314e-12j
-7.95753e-09   +1.74364e-13j
============================
Numerical solution
----------------------------
order=1, freq=1000:
-3.48672e-05  -7.84548e-06j
-2.18228e-06  -6.85143e-07j
-5.82168e-07  -6.53981e-08j
-1.38615e-07  -7.79784e-10j
-6.8483e-08    4.39073e-10j
-2.13192e-08   1.82408e-10j
-8.44217e-09   3.13843e-10j
=============================

Best wishes,
spvfly


Does the MAVSDK support mavlink ftp server

Hi support,
I know there are ftp server example. I try to use this example but seems not working.
I read some mavskd proto code. And found the plugins have pair server and client side( e.g.: camera -> camera_server, param->param_server). But for ftp there is only ftp proto (seems to work as client).  So if I want to support ftp server, I need to add the ftp_server.proto. And implment it as a server component.
Is my understanding correct or  just am I missing something in MAVSDK?

Right now, both clients and servers are using ftp.proto. But there is ongoing work to split that into something like ftp.proto and ftp_server.proto.
Still the examples should work. What do you mean "they seem to not be working"? Did you compile and try them?

It's work in progress: https://github.com/mavlink/MAVSDK/pull/2060
If you need it urgently, consider my consulting services.

Has been done for a while now.


code review set_center() in abel/tools/center.py

#296 correction to set_center() has exposed some odd, perhaps legacy, code lines in this function:
def set_center(data, origin, crop='maintain_size', axes=(0, 1), verbose=False, center=_deprecated):
  """
  :
   origin : tuple
        (row, column) coordinates of the image origin
  """
  :
    origin = list(origin)
    if origin[0] < 0:
        origin[0] += data.shape[0]
    if origin[1] < 0:
        origin[1] += data.shape[1]

Apart from the redundant list dtype change, origin values cannot be negative.
   :
        container = np.zeros((data.shape[0] + shift0, data.shape[1] + shift1), dtype=data.dtype)

        area = container[:, :]
        if shift0:
            if delta0 > 0:
                area = area[:-shift0, :]
            else:
                area = area[shift0:, :]
        if shift1:
            if delta1 > 0:
                area = area[:, :-shift1]
            else:
                area = area[:, shift1:]
        area[:, :] = data[:, :]
        data = container

The above code appears not to be used.
In the end set_center() simply calls scipy.ndimage.interpolation.shift(image, offset_from_geometric_center).  I don't think the PyAbel code needs to be so complex.
This issue is a place holder to facilitate discussion, and the code change.

I think this code (minus header comments) does the job of image re-centering:
def set_center(data, origin, crop='maintain_size', axes=(0, 1), verbose=False,
               center=_deprecated):
    """
      :
    """
    if center is not _deprecated:
        _deprecate('abel.tools.center.set_center() '
                   'argument "center" is deprecated, use "origin" instead.')
        origin = center

    # [delrow, delcol] delta: geometric center - specified origin
    delta = np.array(data.shape) // 2 - np.array(origin)

    # apply recentering delta only to the specified axes
    if isinstance(axes, int):
        delta[1-axes] = 0

    # pad the image to prevent losing data when re-centered
    # round to nearest integer
    idelta = np.round(np.abs(delta)).astype(int)
    pad0 = (idelta[0], 0) if delta[0] < 0 else (0, idelta[0])
    pad1 = (idelta[1], 0) if delta[1] < 0 else (0, idelta[1])

    pad_data = np.pad(data, (pad0, pad1))

    # move geometric center to the specified origin
    centered_data = shift(pad_data, delta)

    if crop == 'valid_region':   # crop to region containing data
        r, c = centered_data.shape
        centered_data = centered_data[pad0[0]:r-pad0[1],
                                      pad1[0]:c-pad1[1]]

    return centered_data

It would be nice to be able to broadcast pad = (idelta[:], 0) if delta[:] < 0 else (0, idelta[:]) but the if test fails.
Still testing.

It turns out that the current center.py code is fine, it appears to do the correct thing.
code gist

My comment

The above code appears not to be used.

cannot be correct.
Hence. there is no need to delay merging PR #299.  I will continue to looking at my version. But for now I am fighting a cold. It's winter in OZ.

Apart from the redundant list dtype change, origin values cannot be negative.

Now they can:

Image coordinates are in the (row, column) format, consistent with NumPy array indexing, and negative values are interpreted as relative to the end of the corresponding axis. For example, (-1, 0) refers to the lower left corner (last row, 0th column).

The casting to list is thus needed/useful because if this origin is passed as a tuple (which looks more natural than a list), it's reduction to 0 ≤ y < height (origin[0] += data.shape[0]) would not work. Maybe I should have put a comment there...

Neat! Thanks, for the explanation.

(replying to this comment from #299)

Cropping is a real pain, in the sense that I do not fully comprehend the cropping options

As I understand, they are supposed to work like this:

Why not pad the image for all cases and then crop to a PyAbel friendly nearest odd-column size? In which case centered_data = centered_data[padr:-padr, padc:-padc] will do the right thing, no need for any crop-options.

I think, these different cropping options above make sense for different applications, so allowing the users to choose among them is a useful thing.
Regarding always padding and then cropping, the question is whether we should care about the efficiency (time and memory). For example, maintain_size can be done directly by scipy.ndimage.interpolation.shift() without any padding and cropping; valid_region does not need padding, and maintain_data does not need cropping. For whole-pixel shift, the latter two can be done, respectively, by pure cropping and padding, without scipy.ndimage.interpolation.shift() at all, but doing fractional shifts properly and efficiently is where it gets complicated.

A very nice clear diagram, which has sorted my confusion. It would be great to include the figure in the docs.
You have made good point about the execution time for scipy.ndimage.interpolation.shift(). E.g. a 4096x4096 images takes about 2 seconds to shift on my PC.
In [1]: import numpy as np

In [2]: from scipy.ndimage.interpolation import shift

In [3]: im = np.loadtxt('O2-ANU4096.txt.bz2')

In [4]: %timeit shift(im, -0.5)
1.98 s ± 2.25 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

I agree in principle with your comment, integer-pixel shifts could be handled via crop/pad, but in reality, how often would the data-center be whole pixel shifted from the geometric center?
Also:
Q: What happens for input data has an even number of columns, for crop="maintain_size"?

throw an exception, or
return a centered same even-column size, unsuitable for PyAbel, or
return a smaller centered odd-column size

takes about 2 seconds to shift on my PC

It's interesting that in Python 2 (and older SciPy) scipy.ndimage.shift was slightly faster. :–)

how often would the data-center be whole pixel shifted from the geometric center?

I would say that most experimental images must be shifted by >1 pixel, but subpixel shifts are important only for very-very high-resolution data. Which must have been also circularized with subpixel accuracy, and its center found with subpixel accuracy (taking into account that not all find_origin methods can do that)... Since scipy.ndimage.shift seems to be ~2 orders of magnitude slower (even with integer shifts) than whole-pixels shifts by direct NumPy array manipulations, we might consider whether it's worth to have “fast” and “slow” (but more accurate) centering methods. But how slow are find_origin methods?

Q: What happens for input data has an even number of columns, for crop="maintain_size"?

The high-level function https://pyabel.readthedocs.io/en/latest/abel.html#abel.tools.center.center_image() does have the odd_size argument, which should take care of this, so it's probably not very necessary to do anything special in the low-level set_center() (those who call it directly must understand what they are doing).

It would be great to include the figure in the docs.

I agree!

we might consider whether it's worth to have “fast” and “slow” (but more accurate) centering methods. But how slow are find_origin methods?

We can speed scipy.ndimage.interpolation.shift up a little bit by specifying order=1, which should be completely accurate for integer shifts. Still, it's not nearly as fast. Even if the find_origin methods are slow, there is probably still a case where you want really fast integer shifts. For example, back in grad school I would process huge folders full of photoelectron distributions. I would find the center for only one image (it was always the same for that instrument). Then, I would process the whole folder of hundreds of images, centering them and Abel transforming them. So, having a fast centering algorithm is important for the overall workflow.
I agree that in many datasets, sub-pixel shifts are unnecessarily small and that integer pixel shifts are more practical. I suppose that I'm arguing that we should have both a fast and a slow method, even though it's clunkier to implement.

It's interesting that in Python 2 (and older SciPy) scipy.ndimage.shift was slightly faster. :–)

Is that for the O2-ANU4096.txt image size, not 2048? I used a larger image for my test.

(those who call it directly must understand what they are doing)

We can issue a warning.

process huge folders full of photoelectron distributions

Same here, but with each center determined. However, a few seconds is not much out of the total time for a full spectral analysis.

should have both a fast and a slow method

Sounds fine. In addition, in principle, the core of set_center() need only operate on one axis, with an image transpose .T used to operate on the other (for a 2D image data). This may help when using set_center() for 1D-data.

In fact, there is a good use case that needs fast shifts without calling find_origin for each frame — video processing (since we claim that PyAbel can do this).
I played a little bit with scipy.ndimage.shift() parameters, and with order=0 it apparently does whole-pixel shift, although still slower than NumPy slicing/padding. So, I guess, we can expose the interpolation order parameter, setting it to 3 by default for high-quality results, mention that lower orders are faster, and maybe reimplement order=0 ourselves to make it even faster. By the way, scipy.ndimage.shift() currently has broken boundary treatment.
(about even-sized images)

We can issue a warning.

I don't know. Warning does not make much sense, since passing the result further will either be fine or produce an error.
If I understand correctly, the only Abel-transform method that can work with even-sized images is rbasex, but it does not need preliminary centering. So there is probably no need for set_center() to return even-sized images at all. On the other hand, center_image() does have the odd_size argument, so if there is any use for it there, maybe we can also add it to set_center().

in principle, the core of set_center() need only operate on one axis, with an image transpose .T used to operate on the other (for a 2D image data)

The problem with this is that scipy.ndimage.shift() is no faster when shifting along one axis only, so separating axes shifts will make it twice slower.

It's interesting that in Python 2 (and older SciPy) scipy.ndimage.shift was slightly faster. :–)

Is that for the O2-ANU4096.txt image size, not 2048? I used a larger image for my test.

For any sizes. For 4096×4096 I get ≲2.2 s in Python 2 (SciPy 1.2.2) and ~2.3 s in Python 3 (SciPy 1.4.1). Not a big, but consistent difference.

Well, I've made a whole-pixel version that uses only NumPy array manipulations and is 1–2 orders of magnitude faster than scipy.ndimage.shift() (for example, it takes ≲2 ms for 1025×1025 images, whereas shift() takes 120 ms with order=3 (default) and 14 ms with order=0).
In principle, if we can tolerate losing fractional edge pixels (which currently occurs in scipy.ndimage.shift() anyway and in any case must have zero intensity for meaningful Abel transforms), this implementation can be easily augmented with subpixel (⩽0.5 px) shifts for order > 0. Otherwise, doing proper fractional shifts (with circumventing scipy.ndimage.shift() bugs) will take some more effort.
@stggh, your code above does not seem to treat the crop='maintain_size' case, but the examples below it look correct (except that the “maintain_data” result is even-sized). Is that code incomplete? Do you have the full version and tests?

Yes, sorry, the code is complete. I have written another version that includes integer shifts, but it is not fully working for all the crop options.  I have been hung up with the treatment of odd vs even image centers and cropping.
It seems that your slick code could be wrapped with a fall through to scipy.ndimage.shift() for fractional shifts.

@MikhailRyazanov your integer shift code looks very nice, and it works(*):

test code
(*) There may be a 1-pixel offset for crop='maintain_shape', which remains an even-image (400, 400).  However, this is likely my fault in the test-code. :-(

For even-sized images it assumes that the “center” is at n/2 - 1:
012345
  ^

but your test assumes it at n/2:
012345
   ^

I do not know which is better: n/2 looks “simpler”, but n/2 - 1 allows to crop the image to odd-sized (by removing the last row/column) without changing its “center”, as described in the docstring. If we want to use the n/2 convention for even sizes, then I just need to remove  - 1 from one line.
Current PyAbel code apparently uses n/2:
https://github.com/PyAbel/PyAbel/blob/f110ba34ad1e8e6bc920c40b402a3963527064b2/abel/tools/center.py#L205
but for odd_size=True it crops the last column (before centering):
https://github.com/PyAbel/PyAbel/blob/f110ba34ad1e8e6bc920c40b402a3963527064b2/abel/tools/center.py#L127-L129

Hmm,  I think old_center needs to be float if an even column size image.
Perhaps, add the parameter odd_size to set_center()?

Hmm, I think old_center needs to be float if an even column size image.

But this will make the output image centered “between pixels”, at least for crop='maintain_size', contrary to PyAbel conventions.

Perhaps, add the parameter odd_size to set_center()?

Why not just call center_image(IM, origin, odd_size=True)? :–)

This is the standard PyAbel grid image

Either set_center() must always return an odd-column image, or the center must be between pixels (even-columns)?

Why not just call center_image(IM, origin, odd_size=True)? :–)

Agreed. I thought that @Mobbybobby had called the function set_center() directly, but that may not be the case.
Your nice code corrects the previous errors in this function. I am happy with it, once you include a default to scipy.ndimage.shift() for fractional pixel shifts (= my user case).

After looking at other PyAbel tools, it seems that the all use size // 2 for the center, so I've switched to that. I think, using the center “between pixels” doesn't make sense, since nothing else in PyAbel can work with that...
I have created PR #302 with the new, hopefully complete and correct, code.

@stggh, should we close this now?

Yes, issue addressed by #302.


initial Windows successful compile

This is an initial notification, as discussed.
I am a novice github user, so I don't know how things work on your side.  I imagined you would want to create your own 'sift' branch in order to be able to play around with my code rather than only merging to master...[stack overflow ] (http://stackoverflow.com/questions/5884784/how-to-pull-remote-branch-from-somebody-elses-repo).
I have reviewed the vlfeat code and everywhere dsift and sift are separate files (.m, .mex, .c). so I would propose that cysift be changed to cy_dsift which corresponds to vl_dsift mex file.

Great - thanks for this - this looks like a good start. Notice that below your message is the outcome of the continuous integration servers. This runs your pull request on a fresh Linux 64-bit and Windows 32/64-bit environments to see if it will work for a new user. It's really great practise for catching mistakes!
Anyhow, see that they are both failing? If you click on Details, you can see that there is a syntax error in sift.py:
cyvlfeat/sift/sift.py line 9
Looks like a copy paste error :)

Thanks. I haven't got to the python code yet- just making sure the cython compiled.

could you explain how I go about using conda for developing pyvlfeat only.. is there a one liner?

Hey!
I've update the README, hopefully that makes things more clear. Also, unfortunately, I had need of the vlfeat SIFT method myself, and I've actually implemented it already... Please see the other PR. What would be really great would be maybe if you could add some of the pure Python SIFT functionality such as vl_plotsiftdescriptor?

I do want to implement them, but don't know when I will find the time, so
probably better you do it yourself..
On Thu, Jul 2, 2015 at 1:12 PM, Patrick Snape<EMAIL_ADDRESS>wrote:

Hey!
I've update the README
https://github.com/menpo/cyvlfeat/blob/master/README.md, hopefully that
makes things more clear. Also, unfortunately, I had need of the vlfeat SIFT
method myself, and I've actually implemented it already... Please see the
other PR. What would be really great would be maybe if you could add some
of the pure Python SIFT functionality such as vl_plotsiftdescriptor?
—
Reply to this email directly or view it on GitHub
https://github.com/menpo/cyvlfeat/pull/4#issuecomment-118001772.

Yeah, unfortunately, I just need the SIFT method for extracting features in a very un-SIFT like way (for face alignment). So I don't need any of the keypoint/matching viewing methods. I tried to update the README to be more descriptive to make contributing easier. Hopefully this will make everything more useful for you in the future!
If you want to install the latest cyvlfeat build with SIFT from conda you should be able to use the command:
conda install -c menpo/channel/master cyvlfeat

Thanks for getting this started though, I really appreciate it!


docs: link to docs hub fuel installation guide

Description
In order to remove documentation redundancy issues, the fuel installation guide is being centralized in the docs-hub.
Check docs-hub/62

You'll want to run pnpm changeset so that this will pass the pipeline 🙂

That was an accidental close, sorry!


Fixed a sentence typo

Why:
Closes [issue link]

What's being changed: The document had a sentence typo which I found while I was trying to get help.

Check off the following:

[✔] I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
[✔] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Thanks for opening a PR 👍 Please fill out the pull request template in the top comment in this pull request, then we'll get this up for review!

I want see gst sury
في الثلاثاء، ٢٥ مايو، ٢٠٢١ ٧:٤٠ ص Janice @.***> كتب:

Merged #6629 https://github.com/github/docs/pull/6629 into main.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/6629#event-4789761565, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDXJPGSF57GBUVXPOOJPY3TPML4RANCNFSM45IRT25A
.

The above this for i with my money from
@.*** can you hld my for this
في الثلاثاء، ٢٥ مايو، ٢٠٢١ ٧:٤٥ ص Ali Alaadh @.***> كتب:

I want see gst sury
في الثلاثاء، ٢٥ مايو، ٢٠٢١ ٧:٤٠ ص Janice @.***> كتب:

Merged #6629 https://github.com/github/docs/pull/6629 into main.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/6629#event-4789761565, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUDXJPGSF57GBUVXPOOJPY3TPML4RANCNFSM45IRT25A
.


who to get the Data from DynamicBuffer

Hello,
first I can compile and run this project and works all as expected, fast and robust, congratulations.
I use VS2022, with the debugger I can run and inspect step by step.  But unfortunately no chance to understand what is going on.
(I write my tools in C and have little experience with C++).
I just want to get the data from the read buffer into a char[1024] variable,
in read.hpp
public:
    read_some_op(
        AsyncReadStream& s,
        DynamicBuffer& b,
        basic_parser<isRequest>& p)
        : s_(s)
        , b_(b)
        , p_(p)

  ....

     b_.commit(bytes_transferred);

//    the data is there, now I try to copy this to my  Variable
//    but NOTHING WORKS

       char mycstri[1024];

       memcpy( mycstri, b_.begin_ , bytes_transferred);
       memcpy( mycstri, b_.data() , bytes_transferred);
       memcpy( mycstri, reinterpret_cast<const char *>(b_.data() ), bytes_transferred);

//       beast::make_printable(b_.data())

after 4 hours of searching and trying I have no chance to access it somehow, nothing works
can someone help, please
TIA

I remember when I first tried Boost.Asio, like idk.... I think it was actually 19 years ago, and I had this exact problem. I ended up avoiding it for years because of it. Can you show your code? Generally speaking if you want to copy out the data you might write:
char buf[ 256 ];
DynamicBuffer db;
...
std::size_t amount_copied = boost::asio::buffer_copy(
    boost::asio::buffer( buf ), db.data() );

But it would be easier for you to just use the beast::flat_buffer class which guarantees that it returns its results in a single memory region:
boost::beast::flat_buffer fb;
...
boost::beast::flat_buffer::const_buffers_type cb = fb.data();

std::string_view s( reinterpret_cast<char const*>( cb.data() ), cb.size() );

Now you have a string view, which is better than making an unnecessary copy of the data.
Hope this helps!

Hello,
Excellent, just as I wanted, thank you so much.
I will also give a try with the string view
but at 66 years, the chances of me getting further are not so good :(

You can replace std::string_view with std::string in the code I posted, and it will work the same way.

@FriNagy is this issue resolved?

yes, is solved
I get so the request filename in the read.hpp
if (bytes_transferred) {

    boost::beast::flat_buffer::const_buffers_type cb = b_.data();
    std::string_view s(reinterpret_cast<char const*>(cb.data()), cb.size());

    std::size_t httpfound = s.find(" HTTP");  // search in header

    if (httpfound != std::string::npos) {
       if (httpfound < 100) {
            char  dest[100];
            std::copy(s.begin(), s.begin() + ++httpfound, dest);
            dest[httpfound] = '\0';

Thank you!


updated google maps version

updated google maps version number

This has been fixed in the now-merged pull request #79


More then one GPU

face_recognition version: Latest
Python version: 3.6.6
Operating System: Ubuntu server 18.04

Description
I im running the CNN model at the moment with a 1060 3GB GTX GPU and it is working fine!
But i have a curios question regarding multiple GPU's would this work or is there any limitations to this?

Ah thank you for the reply! :)
On a side note, using batch_face_location is there an easy way to calculate how much GPU ram is needed for doing X amount of images and also calculate in upsampling=1?
Becouse i cannot even run the 128 frame batch example with upsampling=0 without getting cuda malloc error.
I know the 3GB i have is low but would be Nice to know how to calculate it so i dont have to just try different batch sizes and could help in future upgrades to GPU purches

I don't have the exact math handy. But it breaks down to this - at minimum you want an old GT 980 Ti with 6GB of RAM. Above that, you could get a 1080 Ti or 2080 Ti (newest). I wouldn't waste money on anything else since RAM is so important and those cards give you the best RAM options.

Thanks for the awnser @ageitgey🥇 ! Loving the API so far and experimenting with some applications for it

Nice! Let us know if you build anything cool :)


[Question] For GLFW_MOUSE_PASSTHROUGH is it possible to selectively pass mouse event through?

I have a case where the window is partially transparent (using GLFW_TRANSPARENT_FRAMEBUFFER), I would like to pass mouse events on if the click was on a transparent portion of the window, and handle them if not. I can determine that in my code, but is there a way in GLFW to catch them and then pass back if I don't want to handle the event?
GLFW_MOUSE_PASSTHROUGH seems to be all or nothing. When set, even the window decoration buttons are no longer clickable.

Anyone have any thoughts on this? I was considering adding a new define like GLFW_MOUSE_SELECTIVE_PASSTHROUGH, and a callback taking the event data and returning a bool to determine if GLFW passes the event to the OS or not.
I'm new to this library though, so some advice and guidance would be most appreciated.

@elmindreda I'm not following you on "non-rectangular windows". I don't need GLFW to decide, just delegate to application code the ability to decide based on the coordinates of the mouse click. I'll have a look at the implementation, but GLFW currently handles both cases. I just want to be able to handle the click (GLFW_MOUSE_PASSTHROUGH not defined) or send it on as though GLFW_MOUSE_PASSTHROUGH was defined.
Is the issue that this is only configurable prior to window creation for some reason?
It may not be a priority for the project, but it is for mine. I have to find a way to do this, move to another library, or write platform specific code for the window layer. I've had a really good experience working with GLFW thus far, so that's my preferred choice! ;^)

@elmindreda Thank you for clarifying and keeping me from spending too much time in that direction. I'm really hoping I can find a way to add this then to the library even in a fork. I would hate to give up glfw just for click-through, but it is a requirement for the app I'm working on.
Any and all advice most welcome!


3 otp benchmark

update gitignore
added otp example

which part is not running for you? I imagine it might be something to do with java, maybe?

See #12 for changes, not sure yet, testing again...


[WHLSL] Support compute shaders

Migrated from https://bugs.webkit.org/show_bug.cgi?id=189384:
At 2018-09-06T23:35:57Z<EMAIL_ADDRESS>wrote:
Support compute shaders

At 2018-09-13T01:50:20Z<EMAIL_ADDRESS>wrote:
rdar://problem/44402993

At 2018-09-22T08:57:40Z<EMAIL_ADDRESS>wrote:
There's probably nothing that actually has to be done for this. We just need some tests.

At 2018-09-22T21:05:55Z<EMAIL_ADDRESS>wrote:
*** This bug has been marked as a duplicate of bug 189108 ***


sls wsgi serve returns "Unable to import werkzeug"

Currently, the "sls wsgi serve" command has an error when calling wsgi.
It will return: "Unable to import werkzeug (run: pip install werkzeug)"
even though the werkzeug requirement is in the requirements.txt file of the wsgi package.
The steps to directly reproduce on a fresh Ubuntu 16.04 VirtualBox Install can be found here:
https://serverless.com/blog/flask-python-rest-api-serverless-lambda-dynamodb/
Just for kicks:
-I installed werkzeug locally and sudo cp'd it into the serverless-wsgi main directory and there was another requirement that needed to be installed (boto3, botocore, click, etc). I did this for a couple of iterations before coming here.
-I pip installed everything needed for the ^^ dependency tree failure in a virtualenv and pip freezed the venv into the serverless-wsgi requirements.txt , also no avail.

Ubuntu 16.04 comes with Python 3.5 by default. The sls wsgi serve command will run the Lambda runtime python version by default, i.e. python3.6. So chances are you've set up your venv and run pip install under Python 3.5 and sls wsgi serve is running under Python 3.5 and thus not finding your packages.
You can customize your python binary using the following option, as described in the README:
custom:
  wsgi:
    app: api.app
    pythonBin: python3

However, preferably, ensure that your virtualenv and pip install is running under Python 3.6, so you run under the same version as Lambda.

Is there any way to make this play nice with pyenv?


kerning-pairs not available in current release build

Is there a chance that you could build a new executable release with the kerning-pairs feature in please?
The current build was before the kerning-pairs feature was added
Cheers
Nigel

Hi!
Just released the newest Release, hope it will work =)

Many thanks
Cheers
Nigel
From: Vladimir Gamalyan @.>
Sent: 05 January 2023 12:32
To: vladimirgamalyan/fontbm @.>
Cc: NworbLegin @.>; Author @.>
Subject: Re: [vladimirgamalyan/fontbm] kerning-pairs not available in current release build (Issue #23)
Hi!
Just released the newest Release https://github.com/vladimirgamalyan/fontbm/releases/tag/v0.6.1 , hope it will work =)
—
Reply to this email directly, view it on GitHub https://github.com/vladimirgamalyan/fontbm/issues/23#issuecomment-1372157567 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGMSFH7MRJFC2A7QX7S2VU3WQ25KNANCNFSM6AAAAAATQWAWLU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AGMSFH2QZBKYGO7YFXSYKSDWQ25KNA5CNFSM6AAAAAATQWAWLWWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSRZF3H6.gif Message ID: @.*** @.***> >

Yep - seems to be working correctly when I set it to -kerning-pairs extended, but I didn't get any kerning values with basic or regular when testing with Google's NotoSans-Regular.ttf

It seems Freetype somehow can't read kerning information from the font file (due limitations or bugs) and there are no kernings at all from fontbm perspective.
"extended" option adds extra synthesized kernings, you can see with -kerning-pairs extended.


Typo on index.html in wasm

THIS clears the error.
style="z-index: 10;" style="background: #FFFFFF;"
Anyways its awesome

fix in https://github.com/pygame-web/pygbag/commit/c99518bb2d8a96fb47930850db36232649088f74


Add CNAME pointing at modelviewer.dev to the root

Per the docs, this needs to live in the root of our deployed source.
If we don't want to include the actual file here we could have it as a step in the deploy, but that seemed more complex.

Fixes #605


buildGoModule: copy vendor instead of symlinking

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-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
[x] Fits CONTRIBUTING.md.

We should have new versions of go in the next day or two. I'll merge the buildGoModule copy vendor commits with the version bumps and do trimpath in another PR.


Check if eid app is installed..

https://capacitorjs.com/docs/apis/app#canopenurl

https://capacitorjs.com/docs/apis/device


Style paragraph text that has been indexed to highlight it

some change in header template so that only paragraph indexed are highlighted
place span inside anchor, not outside. Makes it easier to style.
provide the indexing data as a 'tool-tip'

I have found it strange when selecting a search item that is indexed, or a link to an indexed item, to get thrown into a page without it being obvious why there. By highlighting the indexed text, it is then visually obvious why the link has been made.
But very useful when looking for unfulfilled links (a source link is targeting an indexed item, but the browser did not find it).

Can you give me a page with an example with &without so I can see the diff?

@coke  See image below. Same page in docs.raku.org and in new-raku.finanalyst.org (window on top).
The 'quote-words' term has X<> markup around it.
The question I have is about the content of the tooltip when you hover over the highlighted term.
On new-raku, I have implemented a before with the meta portion of the X<DISPLAY|META>. I could instead try to get the link in the tool-tip, so the hovering and right-clicking allows you to copy the link. This behaviour might be more useful, but I haven't worked out how to do it.

I was very confused until I realized both of your links send me to docs.raku.org.

I don't think the tooltip is adding any benefit in these cases. The display styling is fine.

@coke my bad with the links. I'll remove the tooltip, and create a PR.

this PR needs to be rebased to main. It's getting too complicated here. I'm deleting this branch and creating a new one.

You can rebase the existing branch and force push when dealing with PRs. If you're the only working on a branch, the force push is OK, IMO.


[IOS] .getAll() and .get() always returns an empty object

We have been using this package for a while now and it has always worked up until now, since we updated our react-native version to 0.60.4 both of the above stated functions always return an empty object.
Could use some help on why this is happening.
React-native version: 0.60.4
React-native-cookies version: 3.3.0

same

do you find way to work?

the react-native-webview use wkwebview default ,  the react-native-cookies can't work with wkwebview . you can set useWebkit of react-native-webview to false. then react-native-cookies can work, have a try!

same

same problem on:
React-native version: 0.60.5
React-native-cookies version: 3.3.0

For me (React-native version: 0.60.5) work's next steps:

npm install git+https://github.com/joeferraro/react-native-cookies
in my project go to 'node_modules/react-native-cookie/ios/RNCookieManagerIOS/RNCookieManagerIOS.m' and delete this function:
RCT_EXPORT_METHOD(getAll:(RCTPromiseResolveBlock)resolve  rejecter:(RCTPromiseRejectBlock)reject) {  NSHTTPCookieStorage *cookieStorage = [NSHTTPCookieStorage sharedHTTPCookieStorage];  NSMutableDictionary *cookies = [NSMutableDictionary dictionary];  for (NSHTTPCookie *c in cookieStorage.cookies) {      NSMutableDictionary *d = [NSMutableDictionary dictionary];      [d setObject:c.value forKey:@"value"];      [d setObject:c.name forKey:@"name"];      [d setObject:c.domain forKey:@"domain"];      [d setObject:c.path forKey:@"path"];      [d setObject:[self.formatter stringFromDate:c.expiresDate] forKey:@"expiresDate"];      [cookies setObject:d forKey:c.name];  } }
Build project on REAL DEVICE

I have forked the repo here: https://github.com/safaiyeh/react-native-cookie-store
We can create issues and PRs there to continue the development of the project.


dio and google font not working on web and mac os

Package
google_fonts
Existing issue?

[X] I checked the existing issues

What happened?
Expected vs actual result:
Steps to reproduce:
flutter: Error: google_fonts was unable to load font Ubuntu-Regular because the following exception occurred:
Exception: Failed to load font with url https://fonts.gstatic.com/s/a/0c6760f323ee57525ee9fec23bf7c14af2667970250d0931f33a7f195e7ac11b.ttf: ClientException with SocketException: Connection failed (OS Error: Operation not permitted, errno = 1), address = fonts.gstatic.com, port = 443, uri=https://fonts.gstatic.com/s/a/0c6760f323ee57525ee9fec23bf7c14af2667970250d0931f33a7f195e7ac11b.ttf
flutter:
Relevant log output
flutter: Error: google_fonts was unable to load font Ubuntu-Regular because the following exception occurred:
Exception: Failed to load font with url https://fonts.gstatic.com/s/a/0c6760f323ee57525ee9fec23bf7c14af2667970250d0931f33a7f195e7ac11b.ttf: ClientException with SocketException: Connection failed (OS Error: Operation not permitted, errno = 1), address = fonts.gstatic.com, port = 443, uri=https://fonts.gstatic.com/s/a/0c6760f323ee57525ee9fec23bf7c14af2667970250d0931f33a7f195e7ac11b.ttf
flutter:

I got the same issue on the web.
Also, I tried to put fonts into the res folder, but nothing happened.

Closing in favor of #560


The extension ignores git.autofetch and periodically fetches all remotes

Extension version: v0.76.0
VSCode Version: 1.83.1 (Universal)
OS: macOS Sonoma 14.1 Beta
Repository Clone Configuration (single repository/fork of an upstream repository): Huh?
Github Product (Github.com/Github Enterprise version x.x.x): github.com

Steps to Reproduce:

Install the extension

Expected Results:
The configured remotes are only fetched on explicit user interaction.
Actual Resulst:
The configured remotes are periodically fetched in the background, whether the users wants or not.
This is a an issue in at least two separate ways:

As a user, I never consented to this behavior. It took me hours and hours to track down which extension violated my explicitly stated preference to not fetch in the background ("git.autofetch": false).
It breaks my workflow. I periodically need to rebase my branches, and I'm often working on more than one computer on the same branch and/or I'm collaborating with a co-worker on the same branch. I rely on git push --force-with-lease when I need to force-push a branch to not accidentally overwrite a push from a different computer or a from a co-worker. This relies on me, the human developer, having full control on when which branches are fetched from origin. I do not want automatic fetching in the background, and I expect you to honor my stated preferences.

The configured remotes are periodically fetched in the background

It should just be the remote for the branch you're currently. Are you seeing it do otherwise?

Additionally, the fetch should only be happening in the following cases:

The extension activates
You check out a PR from the PRs view
You switch to a branch associated with a PR
You open the PR description

It could be that it's just fetching the current remote, but I also don't want that done in the background. If it's necessary for the extension, could you fetch into your own namespace (instead of updating the default remote tracking branch)? I.e. instead of (the command line equivalent of)
git fetch <remote> <branch>

you'd do something like
get fetch <url> <branch>:vscode-github-pr/<branch>

Otherwise, I'd really strongly prefer an option to just turn off any automatic fetching. Thank you.

Ok. I will add a setting that you can change so that we never fetch if the branch already exists locally.

@toh-ableton starting in the pre-release version of the extension tomorrow, you can use the following two settings to get the behavior you're looking for:
"githubPullRequests.pullPullRequestBranchBeforeCheckout": false
"githubPullRequests.allowFetch": false

@alexr00 Wow amazing thanks for the quick turnaround! This is great. 💐

@toh-ableton if you do try out the pre-release version of the extension then it would be helpful if you could comment back here in the issue to say whether the changes work the way you expected!

@alexr00 I tried the preview, and it's working exactly as I expected. Thank you very much again for the quick fix!

Glad to hear, thanks for trying it out!


I see that the secp256k1-zkp library has configuration options hard coded instead of using the ./configure

I see that the secp256k1-zkp library has configuration options hard coded instead of using the ./configure script:
https://github.com/cryptonomex/fc/blob/master/CMakeLists.txt
https://github.com/ElementsProject/secp256k1-zkp
That is causes build errors on some systems:
In file included from /home/pi/graphene/graphene/libraries/fc/vendor/secp256k1-zkp/src/secp256k1.c:11:0:
/home/pi/graphene/graphene/libraries/fc/vendor/secp256k1-zkp/src/util.h:102:37: error: ‘__int128’ is not supported for this target
SECP256K1_GNUC_EXT typedef unsigned __int128 uint128_t;
since not all architectures have __int128
just running ./autogen.sh and ./configure then make works in that folder, but the fc cmake build does not work
I know it's early and it's probably just set up for testing at this point, but I wanted to give a heads up.

https://bitsharestalk.org/index.php/topic,17156.msg219199.html#msg219199

This commit is at least a starting point:
https://github.com/maqifrnswa/fc/commit/f6bd3274c408fddc9ab48a62b545c74fe4afb33b
I'm testing now - it will obviously be optimized for everyone's  individual machine, maybe some performance increase there.

A bug in the above diff, it needs a "include_directories(libraries/fc/vendor/secp256k1-zpk/include)" -- I don't have it the above diff. If it's helpful, great - but if not, that's find too, hopefully it helps


aio.core: Debug logging cleanups

Signed-off-by: Ryan Northey<EMAIL_ADDRESS>

ill have to land this with #361 as that has the fixes for the breaking changes


In registration page, language of country and "language" do not match

Country names are all in english, yet langage names are in different languages. It would be useful to have them both the same. Additionally, it is probably not useful to offer choices that the project does not intend to support.

the version of the handlebar library does not support your request. Even if you are true for the field country, many, many other fields and pages offer the two supported languages.
Therefore I close this issue for now


Strip transport from image name when looking for local image

When a user pulls an image using a transport, like docker-daemon, we try to lookup
the new image in storage by the input name after the pull.  Because the input name
has a transport (different than local storage), that lookup would fail.
Signed-off-by: baude<EMAIL_ADDRESS>

I saw this when someone pulled from a docker-daemon.  I dont want to add docker to our CI environment.

LGTM

@rh-atomic-bot r+


Web services are broken or offline.

Hi, it seems as if the website, and most web implementations are now offline and not working because of a content delivery error. Also, a similar issue has been posted on instant.io's github

Thanks for posting this issue. It's resolved now. The webtorrent.io server had run out of disk space. I only had log rotation set up for the node.js server logs. I'm setting it up for the nginx logs as well now. Cheers!


Creating databases / database not configured

Just starting out with OrientDB and immediately ran into an issue.
In the console:
create database plocal:test
... (create classes, etc) (works fine)
list databases

* GrateFulDeadConcerts

=> new database is missing!

create database plocal:test

=> database already exists

Try to connect again:
connect remote:localhost/test root root
=> database is not configured on server

You can't create a database using plocal (=local) under the current directory and let the server scan the entire disk to find it. Rather create the database against the server with the url: remote:localhost/test

Alright, thanks.
The docs should really mention this!

Please help on improving docs. Which docs did you follow?

http://orientdb.com/docs/


Fix issue #416 and google-java jar added

Is there any internal reference a user can use to setup the linting/formatting process?

The pre-commit file should be moved into the user's local .git/hook directory. The .git directory is local only so I've stored this file in .gitsettings for now

Can we integrate the formatting thing into ant, e.g. ant format, so we can check code style any time?

@yulongaion good idea, how about creating a ticket for add ant format task, then we do another PR?


Unhandled error during execution of scheduler flush

Version
3.2.21
Reproduction link
github.com
Steps to reproduce
https://github.com/webtutsplus/ecommerce-ui/tree/vue-bug
Checkout the branch vue-bug.
Go to http://localhost:8080/admin/product
Click on edit in any product. It is working. But when you refresh the page, it stops working.
What is expected?
Edit fields should be populated.
What is actually happening?
Edit fields are not being populated.

https://ibb.co/NnwYbZS
https://ibb.co/8KssmdT

Most likely your problem is in this line. You are setting a new product, but it may be undefined because the list of products hasn't been fetched yet from the API, therefore you can't access property name  (product.name) in the template.

Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the SFC Playground.
Remember to use the forum or the Discord chat to ask questions!


GetValue<string[]>() cause an Exception: cannot convert "System.Object[]" to "System.String[]"

var c= conf["a"]["b"].GetValue<string[]>();
cause an Exception: cannot convert "System.Object[]" to "System.String[]"

Could you post an example config with that?

Sorry.
var c= conf["a"]["b"].GetValue<string[]>();
The statement above cause the exception.
[a]
b={abc,def}

Are you sure your call to GetValue is correct? GetValue normally requires a parameter (the type).

I think you tried to use GetValue(typeof(string[])) or GetValue<string[]>()?
If so, that wouldn't work (not implemented yet). But what you can do is, get the value as an object array and then convert it to a string array or treat all elements as strings. Example:
var objArray = conf["a"]["b"].GetValue<object[]>();
// If you have access to C# Lambdas.
// If not, convert all elements manually.
var myStrings = Array.ConvertAll(objArray, o => { return o.ToString(); });
// Otherwise, treat every element as a string.
var myString = (string)objArray[...];


chore: Prepare 3.10.0 release

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: c87fc8f18a24f14d21c1d988508e2dc5a30ee6b0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: c87fc8f18a24f14d21c1d988508e2dc5a30ee6b0
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 05375d55819add3ad9aa19d953b347ac172e0cb2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 05375d55819add3ad9aa19d953b347ac172e0cb2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


jekyll.environment not set to production on deployed site

Describe the bug
jekyll.environment set to development instead of production after deployment on GitHub Pages
To Reproduce

Create a new page with the following code

---
layout: default
title: test
permalink: /test
---

Environment: {{ jekyll.environment }}

deploy site on GitHub pages
navigate to page

Expected behavior
Page should print Environment: production
Screenshots

System (please complete the following information):

OS: macOS
Browser (and its version) Chrome and Safari
Jekyll version 4.3.2 (local version)
Ruby version 3.0.2p107 (local version)

I noticed the env variable is set here
but not
here
I'm wondering if that's the issue?

@george-gca Just submitted, pls take a look