Support chromedriver on apple silicon

Right now if I use wasm-pack to run my tests on my new M1-using macbook, I run into this error message. The text of the error is currently correct but won't be once the binaries are available.

One alternative in the meantime would be to support running an x86_64 chromedriver on aarch64 macs.

One alternative in the meantime would be to support running an x86_64 chromedriver on aarch64 macs.


[Bug] The name of the Widget is 'MultiTreeSelect' in Widget Pane and 'MultiSelectTree' in the canvas

Description
Release/Production - It is observed that the name of the Widget is 'MultiTreeSelect' in Entity Explorer but when it is dragged to canvas the name of the widget is 'MultiSelectTree'
Expected Result:
Name of the widget should be same both in Canvas and Widget pane
Steps to reproduce the behaviour:
Launch Appmsith app in the release Environment
Open any of the App
Expand widget pane and check for MultiTreeSelect Widget
Drag and drop MiltiTreeselect to Canvas and observe the name
Important Details

Version: [11.3]
OS: [MacOS]
Browser [chrome, safari]
Environment [production, release]

@Indrakant-Dana An humble request here, Kindly ask the maintainer / author of the issue assign the issue to you before you actually start working on it. This saves time for everyone. Right now the contributor before you have show interest and it would not be possible for me to accept your code right away. Ill give priority here, Shall let you know if your PR is accepted.
@AR10X please raise you PR soon, Ill move on the next contributor in the next 2 days!

@Indrakant-Dana it is indeed open, but to avoid confusion and wastage of time, we first assign the issue and only then ask the contributor to work on it. This way we can make sure others do not waste there time. Please feel free to look under the label hactoberfest to find more issue you might be interested in.

@somangshu Ok Sure. Please have a look at my PR when I become eligible.

This PR #8371  resolves #8367 . 😄


Use ActiveSupport.on_load to correctly re-open ActiveRecord::Base.

Will fix https://github.com/sferik/rails_admin/issues/2785. Based on https://github.com/rails/rails/issues/23589#issuecomment-229247727.

Thanks 👍


Try/catch for Docker client

Describe changes
When your Docker daemon is not running in a Docker based stack, users get somewhat obscure errors like DockerException: Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory')).
This PR wraps all DockerClient.from_env() calls where no try/catch construct is present with one, raising a more user-friendly error as to what is wrong and could be done to help resolve the issue.
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[x] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

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

Summary by CodeRabbit

New Features

Not applicable.

Bug Fixes

Improved error handling across various components when creating a Docker client fails, providing clearer error messages to help diagnose issues with the Docker environment.

Documentation

Not applicable.

Refactor

Enhanced exception handling for Docker client creation to ensure consistent error reporting.

Style

Not applicable.

Tests

Not applicable.

Chores

Not applicable.

Revert

Not applicable.

@coderabbitai review

thanks for merging @strickvl !


HttpLogFormatter makes multipart requests unprocessable in Spring

When trying to log a multipart request with a HttpLogFormatter the request body is logged correctly, but when the request eventually reaches Spring's MultipartResolver, it cannot be resolved anymore and a MissingServletRequestPartException is thrown. The behavior in Spring seems similar to #637, but it is reproducible on the latest Logbook version 2.14.0.
Description
I encountered this behavior when I tried to log the body of a multipart request with Logbook. By default, there is a BodyReplacer  in place which just replaces the body with <multipart>, so I disabled the existing RequestFilter. Requests would then be logged inside of a custom Sink which uses the JsonHttpLogFormatter to format the request, but it is also reproducible with the DefaultHttpLogFormatter.
Code has been ported from Kotlin to Java for the sake of this report - I hope it's compilable, but at the very least it should be understandable.
class CustomSink extends Sink {
    private HttpLogFormatter jsonHttpLogFormatter = JsonHttpLogFormatter(); // DefaultHttpLogFormatter has the same issue

    @Override
    void write(Precorrelation precorrelation, HttpRequest request) {
        RawJsonAppendingMarker marker =  new RawJsonAppendingMarker("http", jsonHttpLogFormatter.format(precorrelation, request));
        String message = request.getMethod() + request.getRequestUri();
        log.info(marker, message);
    }
   ...
}

When I instead just put a static String inside the RawJsonAppendingMarker, the request comes out intact, so the issue seems to be related to calling the HttpLogFormatter.
Expected Behavior
When formatting a request with a HttpLogFormatter, the request should afterwards still work as expected when it reaches the controller.
Actual Behavior
When formatting a request with a HttpLogFormatter, Spring will not be able to resolve the request afterwards and throw an exception.
Possible Fix
Not sure if that really counts a fix, it's more of a nice-to-have. What I ended up doing to solve the problem is writing my own HandlerInterceptor which logs the request (which is a javax.servlet.http.HttpServletRequest here) as the individual parts. If the request would be resolved by Logbook, maybe instead of being restricted to just logging the body, the user could be able to log individual parts through Filters (e.g. log text, but don't log files).
Steps to Reproduce
either

checkout the repo and run the requests mentioned in the readme

or

create a simple RestController in Spring which takes a multipart request through POST e.g. public void create(@RequestPart("text") String text) { }
disable the default RequestFilter by setting RequestFilter.none() to avoid replacement of the body.
create a custom sink for logging similar to the one mentioned above.
call HttpLogFormatter.format on the request and precorrelation
send a simple multipart request, e.g.

POST http://localhost:8080/test
Accept: application/vnd.api+json
Content-Type: multipart/form-data; boundary=abc

--abc
Content-Disposition: form-data; name="text"
Content-Type: text/plain

Hello World
--abc--

Context
I was unable to log the body of the multipart request in order to understand whether or not it was correctly formatted and had the correct headers and parts.
Your Environment

Version used: 2.14.0
Link to your project: HttpLogFormatterDemo

so the issue seems to be related to calling the HttpLogFormatter.

My guess would be that we're consuming the request body incorrectly or rather that we don't preserve the original one.
I'd advice to dig into Spring (w/ a debugger) and figure out what the body actually contains. Is it empty? Is it incorrectly cut short, etc.?

My guess would be that we're consuming the request body incorrectly or rather that we don't preserve the original one. I'd advice to dig into Spring (w/ a debugger) and figure out what the body actually contains. Is it empty? Is it incorrectly cut short, etc.?

The problem is that Spring resolves multipart arguments with javax.servlet.http.HttpServletRequest#getParts()
org.zalando.logbook.servlet.RemoteRequest contains inside org.apache.catalina.connector.RequestFacade, which contains inside org.apache.catalina.connector.Request
When logbook logs incoming request, org.zalando.logbook.servlet.RemoteRequest read all data from org.apache.catalina.connector.Request#inputStream and store it in own buffer.
In case incomin request  is Json Spring gets this buffer by org.zalando.logbook.servlet.RemoteRequest#getInputStream(), but in case multipart request Spring doesn't use overrode org.zalando.logbook.servlet.RemoteRequest#getInputStream(), Spring uses org.zalando.logbook.servlet.RemoteRequest#getParts(), which delegates to org.apache.catalina.connector.RequestFacade#getParts(), which delegates to org.apache.catalina.connector.Request#getParts(), which uses its own InputStream (this stream has already been read by logbook)
Spring Boot version: 2.5.1
LogBook starter: 2.14.0
@Bean
public Logbook logbook() {
    return Logbook.builder()
            .bodyFilter(none())
            .requestFilter(none())
            .build();
}


dashboard/app: add link to bug into reproducers

If a developer has just a C repro, it may be hard to find the corresponding bug. We could include link to the bug into the reproducers.

@borkmann as you wish
try:
https://syzkaller.appspot.com/text?tag=ReproSyz&x=11513317600000
https://syzkaller.appspot.com/text?tag=ReproC&x=116cec88e00000


Ability to hide home assistant icon

I'm using title templating and would love to hide (unneeded for me) home assistant icon before the template.

I will look into adding a feature to hide the icon, though it may not be possible because of Electrons limitations.

Not possible with electron.


Update multi-region-writers.md

Spelling mistake

@PhilStollery : Thanks for your contribution! The author, @rimman, has been notified to review your proposed change.

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @rimman, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


PTFE-1481 fixes for check run interactions

Codecov Report
Attention: Patch coverage is 42.85714% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 36.82%. Comparing base (68afcf3) to head (6222d8c).
Report is 1 commits behind head on main.

Files
Patch %
Lines

bert_e/git_host/github/__init__.py
0.00%
6 Missing :warning:

bert_e/workflow/pr_utils.py
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #175      +/-   ##
==========================================
- Coverage   36.83%   36.82%   -0.01%
==========================================
  Files          70       70
  Lines       10056    10060       +4
==========================================
+ Hits         3704     3705       +1
- Misses       6352     6355       +3

Flag
Coverage Δ

api-mock
36.82% <42.85%> (-0.01%)
:arrow_down:

server
36.82% <42.85%> (-0.01%)
:arrow_down:

unittests
36.82% <42.85%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Regression: Bleeding shadow when using tabs in stacknavigator

Current Behavior

Expected Behavior

Your Environment

software
version

react-navigation
beta 9

react-native
0.43

node
6.9.2

npm or yarn
yarn 0.23.2

Should be fixed by https://github.com/react-community/react-navigation/pull/1271
Can you check?

Though this makes me wonder, why doesn't stack navigator hide it's overflow.

Ah, missed that, couldn't find an issue relating the issue.


Linux support / installation instructions

Package.json says linux is supported... is that true?
if not, what is needed?
if so, you have installation hints?

I build on Linux. It's a bit complex and requires some minor code changes to fix platform-specific bugs (see my fork here: https://github.com/Pierowheelz/Meisunry - I've just added some pre-built binaries for you as a Release).
Most notably, the base path needs to be adjusted for any code fetching image paths. Also, the 'trash' npm dependency doesn't seem to work, so I've swapped this out with a simple fs.unlink(). I'm sure these could be addressed in a cross-platform compatible way in a proper Pull Request, but I don't have the time right now.
I use electron-forge for the build process. Use their documentation here to install dependencies: https://www.electronjs.org/docs/latest/development/build-instructions-linux
After that, just run: npm i then npm run make. Your build will end up in the /out/make/rpm (or /out/make/deb) folder.
I've noticed the following issues:

Default directory does not exist (Meisunry defaults to C:/, whic doesn't exist in Linux).
App Icon does not work.
Deleting images and copying image paths does not work (hotfix in my fork).

🙏 @Pierowheelz


add timezone for docker install

add support for timezone

I reverted this change because it fails the build pipeline for ARM. My assumption is that the alpine:latest image is an amd64 image and it cannot run apk. I think there is a way to solve this, but for this hotfix release I didn't have time.
Failed pipeline: https://github.com/binwiederhier/ntfy/runs/6718645921?check_suite_focus=true

hmm that's odd. I am using buildx for multi arch builds and my image also has tzdata install with no issues but I am not using goreleaser. just direct docker buildx action.

Goreleaser can do buildx apparently. https://goreleaser.com/customization/docker/
And you can set the platform flag too i think.

You may be able to do something like this: https://github.com/zinclabs/zinc/blob/main/Dockerfile#L6

Any progress on this - using Delay send with absolute time not simple in Docker as it is using UTC and I am not in UTC!! Delay with offset is fine but would be nice to be able to use absolute time also.

I was really confused because the docs were not reverted.

Time zone can be added using docker-compose, let me know if you would like me to share @egooner @kruton

I have the following already set ... but to be honest cannot recall whether this did the trick or not but if I issue date in the console I get this so I think not!!

Fri Sep  8 18:46:27 UTC 2023

environment:
- "TZ=Europe/London"
volumes:
- "/etc/localtime:/etc/localtime:ro"

You can check for the correct time zone and there are 2 issues, both the machine running the container as well as the container have to be on the correct time zone. I believe you can manage it for your machine but for the docker instance here are my instructions:
docker-compose.yml
version: "2.3"

services:
  ntfy:
    build: . # This will build dockerfile in current dir
    container_name: ntfy
    command:
      - /usr/bin/ntfy
      - serve
    volumes:
      - /var/cache/ntfy:/var/cache/ntfy
      - /etc/ntfy:/etc/ntfy
      - /etc/letsencrypt:/etc/letsencrypt
    ports:
      - 8080:80
    healthcheck: # optional: remember to adapt the host:port to your environment
        test: ["CMD-SHELL", "wget -q --no-check-certificate --tries=1 https://localhost:80/v1/health -O - | grep -Eo '\"healthy\"\\s*:\\s*true' || exit 1"]
        interval: 60s
        timeout: 10s
        retries: 3
        start_period: 40s
    restart: unless-stopped

Dockerfile
# Use the original ntfy image as the base
FROM binwiederhier/ntfy

# Install tzdata and tini packages
RUN apk update && apk add tzdata tini

# Set the timezone
ENV TZ=Asia/Colombo

# Use tini as the entrypoint
ENTRYPOINT ["/sbin/tini", "--"]

This is what I used, change the time zone to yours as needed. I also had to use tini which reaps zombie processes that were accumulated by 'ssl_client' process of ntfy. Also note that you can set the time zone in docker-compose as an environment variable OR in the Dockerfile. Dockerfile is easier if you don't plan on changing the time zone often
To check if the time zone of the container is correct you can do the following:
# sudo docker exec -it ntfy /bin/sh
# date

Thanks for that @Ishrathh - I did your docker build example with the exception of the tini which did not seem to work for me!!
Would be good to see Timezone built into the system rather than having to do this!! @binwiederhier  - any chance of incorporating the tzdata package into the build and supporting passing the TZ in the Environment variable. The solution above works but creates more effort on behalf of the users to do this.

Your welcome @egooner, if you would like me to assist you with the setup of tzdata without the tini part let me know :D

I reverted this change because it fails the build pipeline for ARM. My assumption is that the alpine:latest image is an amd64 image and it cannot run apk. I think there is a way to solve this, but for this hotfix release I didn't have time.
Failed pipeline: https://github.com/binwiederhier/ntfy/runs/6718645921?check_suite_focus=true

@binwiederhier Would be awesome if we can get the time zone released on arch's that support it

How are we supposed to do that? Different docker files just because of this?

Not sure how your build process works @binwiederhier  (not very good on docker build etc) but I spotted this on conditional docker build not sure if it helps. Docker File Conditions

Re-added for linux/amd64 in https://github.com/binwiederhier/ntfy/commit/8adb9ee633c5cca607892b9ab42b2685fa7fec73, see #894


[docs] add unknown route to troubleshooting

For https://github.com/elastic/kibana/issues/51733.
This is a rough copy/pasta of @SylvainJuge's comment on discuss. I've made a few changes to adapt it for documentation.

Codecov Report

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

@@             Coverage Diff              @@
##             master     #965      +/-   ##
============================================
- Coverage     63.23%   63.17%   -0.06%
  Complexity       85       85
============================================
  Files           245      245
  Lines         10055    10055
  Branches       1330     1330
============================================
- Hits           6358     6352       -6
- Misses         3314     3320       +6
  Partials        383      383

Impacted Files
Coverage Δ
Complexity Δ

...pm/agent/report/IntakeV2ReportingEventHandler.java
70.9% <0%> (-3.64%)
0% <0%> (ø)

Continue to review full report at Codecov.

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

Thanks @eyalkoren! Updated with your suggested text change and removed the + to remove the indentation.


Hero idea: Forgotten Samurai

*Ember Spirit base model
*Melee, Agility.
*1st Ability: (Dash for Honor) Dashes forward and damages all units in its way. (invincible for duration)
*2nd Ability: (Extreme Training) Get X permanent Agility for every boss/hero kill.
*3rd Ability: (Keen Eye) Lets you ignore a percentage of evasion + If enemy doesn't have evasion you get a crit chance.
*4th Ability (Ult): (Last Stand) Sacrifices percentage of max HP to become invincible for a duration. If you have less HP than the Ult takes you die after Ult ends. (can get health back through life steal only)

I don't think we're doing heroes yet. Keep those for later.


Doc Request: AWS Cloud Provider Offering Caching

Tell us about your request
Amend the documentation for the AWS cloud provider to talk about offering caching.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
The issue is that a customer receives an insufficient capacity error for all the instance types attempted in trying to fulfill a set of bin packed pods. To address this, Karpenter caches these errors and will avoid those combinations of capacity type and availability zone (an "offering") for those instance types for a set period of time (currently, 45 seconds - not user configurable). This allows Karpenter to attempt a bin packing on its next reconciliation attempt that doesn't utilize such offerings, i.e. it removes those offerings from consideration by the bin packer so that it knows that it can't bin pack into those shapes/zones. This means that it could split up a large packing into multiple smaller ones in order to launch on smaller instance sizes, or launch in a different AZ from that which is preferred by node affinity, or (in our next release) try a different capacity type. Even if a node is successfully launched, Karpenter will look at the errors from Fleet to see what offerings were attempted but hit an insufficient capacity error and will cache those to optimize future bin packings (for the ensuing 45 seconds, at least).
Not sure if there's a current page this fits in, may need to create a new sub-node under "AWS". Also, we should consider adding "offerings" to our Concepts page as it's part of the InstanceType interface available to all cloud providers (though the caching is specific to the AWS cloud provider for right now). Basically, an instance type has an array of offerings (combination of capacity type and zone) that represent the availability of an instance type (generated from the cloud provider's own API), for use by the bin packer. That being said, general users wouldn't need to be aware of what an offering is aside from in relation to understanding this caching logic or contributing code (i.e. there's no labels or anything using the "offering" vernacular).
Are you currently working around this issue?
N/A
Additional context
The PR for the capacity type fallback: https://github.com/aws/karpenter/pull/893/files
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Closing because issue is old, please reopen if you feel this is still an issue.


Kusto Notebooks Show SQL as Kernel on Reopen

Azure Data Studio Version:
Version: 1.25.0-rc1 (user setup)
Commit: 634ea0ab6a60543d712dbc77266059de1d70c08c
Date: 2020-12-08T19:09:44.467Z
VS Code: 1.48.0
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Steps to Reproduce:

Create a new notebook connecting to ~Python~ KQL Kernel.
Save the file.
Reopen it. The kernel will not be set to ~Python~ KQL and will get changed back to the default, which is SQL.

An additional ask would be to remember the default connection string / compute location, where applicable.

@MsSQLGirl I cannot repro, either on Windows or on Mac. Using the 1.25 (stable). Let's sync offline on this, because that's quite concerning.

Updating the description. It is an issue for KQL (not Python. apologies.

@MsSQLGirl just want to confirm, this is for the Kusto Kernel correct? I believe that this issue would be similar: #12566.

@VasuBhog  - yes similar, but this one only concerns on the Kusto kernel (and not the connection strings / Attach To details)

This is important for livesite customers. It is not intuitive for the customer to realize that there is a Kusto query on the Notebook, and switch the kernel dropdown to Kusto, before choosing the connection. If a Notebook was saved with the Kusto kernel displayed in the dropdown, it should re-open with the same kernel displayed, and not switch back to displaying SQL.

@MsSQLGirl need your help with priority here. Any chance that you could help?

This issue is now tracked here: 14545


Removes double quotes around table to support schema-qualified table names

Fixes #31

As noted in the bug report, just dropping the quotes would break on table names that require double-quotes, such as "ThisTableName" or "This Table Name" (which are legal table names if quoted). Fixing this will require a bit more work, so we're closing the PR for now.


libite: 2.4.0 -> 2.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/troglobit/libite/releases.
meta.description for libite is: "Lightweight library of frog DNA"
meta.homepage for libite is: "https://github.com/troglobit/libite"
meta.changelog for libite is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 2.4.1 with grep in /nix/store/9jw7r2jn60hx8dky4s8380k5ibq718d3-libite-2.4.1

found 2.4.1 in filename of file in /nix/store/9jw7r2jn60hx8dky4s8380k5ibq718d3-libite-2.4.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
0 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
0 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
inadyn
libite

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9jw7r2jn60hx8dky4s8380k5ibq718d3-libite-2.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libite https://github.com/r-ryantm/nixpkgs/archive/5edd2858ebde17381c63b8af5d7a3f695fd36b14.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9jw7r2jn60hx8dky4s8380k5ibq718d3-libite-2.4.1
ls -la /nix/store/9jw7r2jn60hx8dky4s8380k5ibq718d3-libite-2.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

inadyn
libite

Maintainer pings
cc @fpletz for testing.

Upstream is at 2.5.1


Add scalafmt code formatter

I would like to propose adding scalafmt to this codebase for the same set of obvious reasons why having a code formatter is a good idea. The typical problem with adding a code formatter is it causes merge conflicts for currently open PR's however scalafmt is in a stage where there are only a couple of major PR's which are planned to be merged soon i.e.

https://github.com/sbt/sbt-github-actions/pull/65
https://github.com/sbt/sbt-github-actions/pull/136
https://github.com/sbt/sbt-github-actions/pull/66
https://github.com/sbt/sbt-github-actions/pull/98

The idea would be to introduce scalafmt after these PR's are merged. In regards to the actual scalafmt configuration, I am personally not that fussed. From introducing scalafmt to other projects usually there are 2 approaches to this, either try to find configuration that matches current style as much as possible (which can be a bit of work) or to just use something basic and deal with a large diff
@eed3si9n @armanbilge Thoughts?

just use something basic and deal with a large diff

that's fine. we can do the formatting in a separate commit and add it to .git-blame-ignore-revs.

that's fine. we can do the formatting in a separate commit and add it to .git-blame-ignore-revs.

Perfect, specifically with .git-blame-ignore-revs I have already done this in Pekko and I can confirm it works without problems (almost every IDE/editor/tool that I can think of defers to git for git blame so it will respect  .git-blame-ignore-revs).


Various improvements to C API bindings

Please see individual commits for descriptions.

I rebased, fixed conflicts, and merged the change. Thanks for the review!


httpd 2.4 support

Sammie S. Taunton has tested mod_fastcgi_handler using the latest release of Apache 2.4.1 and it works so far without any flaws while using the socket version of PHP-FPM however, while using the IP:PORT many pages do not show.
This needs to be investigated.

It does not seem to function properly for me with either sockets or ports, both end up in this error
[Thu Mar 01 19:43:26.562790 2012] [:error] [pid 29960:tid<PHONE_NUMBER>] (104)Connection reset by peer: [client x:53361] FastCGI: failed to read from backend $

@dancom96 that would of been me . I still cannot make it work under 32bit and I'm finding several posts around the web where others are finding this project and are reporting the same problems. As for 64 bit it works pretty good but I'm starting to find random 500 errors now that I cannot explain the reasons for. I've been using the socket version regardless as I was unable to make the IP version to work at all.


Converting wav files to WEM produces static in Metal Gear Solid V: The Phantom Pain

I'm trying to get wav files into Metal Gear Solid V: The Phantom Pain as wem files, but all the converted sounds are played back as ear-shattering static when in the game.
I'm using Ravioli Explorer to preview and extract the wem files to wav.
This happens even with the vanilla files. I've uploaded a number of files for your convenience:
RIFF_0041.wem: Original wem file. This file is reported as being a standard stereo PCM wav file at 41000hz sample rate.
File0001.wav: The extracted wem file.
File0001.wav.wem: The converted wav file using WEMConverter.
https://drive.google.com/drive/folders/1cNQYpry0ifoNbEmKZsne6cpAKMTa3u1q?usp=sharing
Just to note, the converted wem files do playback fine in Ravioli, just once they're played back by the game's audio engine it's nothing but static noise.
Cheers!

This may not be related to this software as far as I can tell, especially considering that other tools play it properly. MGSV may be forcefully loading them in a different format that causes it to not play properly (which, while it is a violation of WEM's standards to do so, is possible).
I don't think there's much that can be done here. Sorry.


Custom input types

Hi 👋,
1st of all thanks a lot for this wonderful Kotlin GQL server which is compatible with KTor. I really like it.
I have  few small question please. Please be patient with me I am really a beginner when it comes in writing GQL servers. So I really don't have that much experience.
When I have custom input types within my schema, used on the GQL operations like fe. within a Mutation, how to correctly retrieve them in the code?
Fe. I have this schema:
input UserObjectInput {
    userId: String!
    userName: String
    userBirthday: String
}

type ResultObject {
    attributeA: String!
    attributeB: String!
    attributeC: String
    productType: ProductType
}

enum ProductType {
    PRODUCT_A,
    PRODUCT_B,
    UNKNOWN
}

type Mutation {
    mutationWithUser(user: UserObjectInput!): ResultObject!
}

type Query {
    helloWorld: String
}

My Application class of my Ktor Server looks like this:
// Input object for GQL input object "UserObjectInput" from schema.graphql
data class MyUserInput(id: String, name: String?, birthday: String?)

// How to map ProductType schema enum to this Kotlin enum?
enum class ProductType { A_PRODUCT, B_PRODUCT, UNKNOWN }

data class MyResult(myAttr1: String, myAttr2: String, myAttr3: String?, type: ProductType)

fun main() {

    arianeServer {
        // Load schema.graphql file from resources folder
        schema = loadSchema("schema.graphql")
        //Indicate which HTTP port should be used (80 by default)
        port = 3000

        serverListener = object : ServerListener {
            override fun onStart(host: String, port: Int, path: String) {
                log.info("Server ready 🚀. Listening at http://localhost:$port$path")
            }
        }

        resolvers {
            Mutation {
                resolve("mutationWithUser") {
                	// The retrieved object by arguments is a LinkedHashMap?
                	// Do I manually need to create here `MyUserInput` oject from this `LinkedHashMap`
                	val user: LinkedHashMap<String, Any> = arguments["user"]

                	// Here the outcome of function `doSth()` would be `MyResult`
                	// How to map this to the GQL schema object `ResultObject`?
                	val result: MyResult = doSth()
                	result
                }
            }

        }
    }.launch()
}

Can you please tell me how the mapping "schema GQL objects" <-> Kotlin data classes needs to work with ariane-server? The mapping is my only issue here.

Hey,
Thanks for your comment, unfortunately, it's not possible yet. The project is still in early stage.
But I'm actively working on it. I'll keep you posted once it's possible.

Hello @rb090
I just published a new version that should handle argument typing (v0.3.0).
Also, I published a Gradle plugin.
The plugin will generate the types according to your graphQL schema, and the resolver functions.
For instance, with this plugin, instead of writing
resolvers {
   Mutation {
      resolve<UserObjectInput>("mutationWithUser") {
         println("User ID = ${it.userId}")
      }
   }
}

You can write
resolvers {
   Mutation {
      mutationWithUser { (user) ->
         println("User ID = ${user.userId}")
      }
   }
}

More info here: https://arianegraphql.com/docs/codegen
Feel free to test it out and give me your feedback 🙏


Add start-api subcommand

cargo lambda start-api could start an http gateway that forwards requests to the lambda functions in target/lambda.

I'm working on this, coming soon.


feat(misc): create pyproject.toml

Reference: #2817, #2828, #2848 (I apologise for the multiple PRs the git history was messed up in the last PR)
@cgarciae
What does this PR do?
This PR aims to minimize the number of configuration files for the project. Instead of a separate .style.yapf, mypy.ini, pytest.ini, pytype.cfg and setup.cfg, we now would have all the configurations within the pyproject.toml file leading to a overall minimal code structure. I've also updated the .pre-commit-config.yaml file with the addition of a "check-toml" hook.

Codecov Report

Merging #2955 (bea376e) into main (351248c) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2955      +/-   ##
==========================================
- Coverage   81.86%   81.85%   -0.01%
==========================================
  Files          55       55
  Lines        5918     5915       -3
==========================================
- Hits         4845     4842       -3
  Misses       1073     1073

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

@cgarciae any updates on this ? Can I help ?

Hey @SauravMaheshkar, thanks for the persisted interest!
Here is the update: this PR has to be merged via a separate route than copybara (google's system that syncs github PRs with their internal repo) but only a googler can do this so @chiamp will help us with this.
We will try to integrate this soon.


Visual Editor's multi-selection feature is broken

Describe the bug
Drag to select multiple nodes always failed.

Version

Browser

[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

@a-b-r-o-w-n This feature was broke by Form Extension PR.
onFocus will redraw Visual Editor completely caused the selection states cleared. Do you know what's the changes on onFocus API or ExtensionContainer?
Context
Visual Editor's multi-selection behavior:

Start dragging
If only one node is selected, call onFocus with that node's id
If multiple nodes selected, call onSelect with node ids
End dragging

I'll fix this today.

addressed via https://github.com/microsoft/BotFramework-Composer/pull/2439


feat: add CLI command encode-connect-info

This is for the encoding part of #1730.
I've used named arguments in accordance with #1562.
I understood from yesterday's dev call that it might be better to pass in a JSON directly instead of individual --id and --urls arguments, so I could do that instead if required.

Codecov Report
Patch and project coverage have no change.

Comparison is base (3f9e4b5) 63.22% compared to head (759c5e2) 63.23%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1796   +/-   ##
=======================================
  Coverage   63.22%   63.23%
=======================================
  Files         124      124
  Lines       24713    24718    +5
=======================================
+ Hits        15626    15631    +5
  Misses       9087     9087

Impacted Files
Coverage Δ

client/cli/src/main.rs
0.25% <0.00%> (-0.01%)
:arrow_down:

fedimint-core/src/api.rs
79.82% <0.00%> (-0.54%)
:arrow_down:

fedimint-server/src/lib.rs
76.22% <0.00%> (-0.26%)
:arrow_down:

modules/fedimint-ln/src/lib.rs
74.28% <0.00%> (-0.14%)
:arrow_down:

fedimint-server/src/consensus/mod.rs
81.11% <0.00%> (+0.15%)
:arrow_up:

fedimint-server/src/net/peers.rs
88.00% <0.00%> (+2.57%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Furnace Bug

Steps to Reproduce (as best as you can)
Make him smelt something and sometimes it happens
Expected Behavior
Should just smelt as normal
Actual Behavior (What lead to the bot getting permanently stuck)
It trys to open the frunace and closes it again
Crashlogs and Screenshots (if applicable)
(you may drag + drop text logs and images here, thanks GitHub)
Other mods (if applicable)
https://user-images.githubusercontent.com/93351159/161241593-e188d309-cc33-491c-b895-a6dd147a0e3a.mp4
Discord username (if you want updates)
TheGamerGerman#9321
Developer Notes (leave this blank)
Difficulty: __
Estimated Time Required: __
Once development starts.

are you on 1.18.1 or 1.18.2? I have not encountered this bug on 1.18.1. Can you provide more details on how you made this happen? Does it happen every time?

1.18.1 always

It does not happen always but very often tho


Loss Scaling

This PR adds a loss scaling feature: http://docs.nvidia.com/deeplearning/sdk/mixed-precision-training/index.html#lossscaling.
You can use the loss scaling feature by just setting the scaling factor using a method set_loss_scaling_factor() as below.
from chainer import training

training.set_loss_scaling_factor(1024.0)
trainer.run()

When the scaling factor is set and data type of parameters is fp16, a fp32 copy of parameters are created automatically and parameters are updated with fp32.
Please note that only StandardUpdater is supported for now. After some consensus is obtained that this API is OK, I will make the loss scaling available to other Updaters.

Thank you for the PR.
I think the loss calling should be a feature of backprop computation instead of framework-wide "mode". For example, if the feature can be implemented by adding loss_scale option to Variable.backward and chainer.grad, that's great. We may also want to make StandardUpdater support configuring that argument.
IMO, the fp32 update should be treated separately from the loss scaling setting (and thus it's better to split the PR itself as well). I recommend you to implement it as a feature of UpdateRule instead of Parameter.

I will split this PR to two PRs: one for fp32 update, the other for loss scaling.

I've just submitted a PR for fp32 update as #3708. Please review #3708 first.

The loss scaling feature was re-implemented as a feature of backprop as suggested and the fp32 update feature was removed from this PR.
A loss_scale option is added to Variable.backward and chainer.grad, so that you can use the loss scaling by adding the loss_scale option to Variable.backward or chainer.grad in your code like below.
loss = lossfunc(y, t)
loss.backward(loss_scale=1024)

When loss scaling factor is set, the gradient of the loss is scaled up (multiplied by the scaling factor), and the scaling factor is propagated to whole gradients of parameters in a computational graph along the backprop. The gradients of each parameter are scaled down (divided by the scaling factor) just before the parameter is to be updated, so that in principle the same result can be obtained as when loss scaling is not used.
The loss_scale option is also added to StandardUpdater, so if you use StandardUpdater, you can use loss scaling by adding the loss_scale option to StandardUpdater in your code like below.
updater = training.StandardUpdater(..., loss_scale=1024)


Pre-flight OPTIONS only set on POST #63

Release 0.0.26 - 2019-12-11

Preflight OPTIONS bug fix Issue #125

@kousikmitra just a heads up , this fixes the preflight bug finally. Will patch up.

@joegasewicz sorry didn't follow up. But looks great 👍


fix(ui): support for partial-success for pipeline runs

Describe your changes :

I worked on supporting #10281

Update OM monogram with correct one

Type of change :

[x] Bug fix
[x] Improvement
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Frontend Preview (Screenshots) :

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@Sachin-chaurasiya @ShaileshParmar11 comments addressed


Do not check self compatibility when pattern Class.method is used

Environment data

Language Server version: 2021.9.1-pre.1
OS and version: Windows 7
Python version (& distribution if applicable, e.g. Anaconda): 3.8.11 Anaconda

Sample code
from __future__ import annotations

from abc import ABC
from typing import Any, overload

class Base(ABC):
    @overload
    def f(self: A) -> A:
        ...

    @overload
    def f(self: B) -> B:
        ...

    def f(self: Any) -> Any:
        return self

class A(Base):
    pass

class B(Base):
    pass

_ = Base.f(A())

Expected behavior
No warnings.
Actual behavior

Explanation
In practice, the class Base could be a base class, or a mix-in used in limited concrete classes, and the method f could be a method with different signatures in different concrete classes but uses a same implementation. Static access of Base.f alone should always be valid. Base().f, aside from the ABC restriction, should be considered invalid because of self compatibility.

A type checker can't ignore type annotations in some cases. If a parameter is annotated, type consistency needs to be validated.
If I correctly understand your use case, it should be handled using a bound type variable, like this:
from typing import TypeVar

_T = TypeVar("_T", bound="Base")

class Base(ABC):
    def f(self: _T) -> _T:
        return self

There are cases in my project that the return type does not match the type of self, so the method signature cannot simply be written with type variables.
While I could try some work-around, I'd like to know why you decided to check the type of self on static access of a method, when the method might not even get called.

The self needs to be type checked because a member access results in a "binding" operation where the self parameter passed an argument implicitly. Any time an argument is passed to a parameter, a type checker validates type consistency.

Thank you for explaining. While this behavior breaks some of my tricks, I see what it accomplishes and I'll adapt.


Monix 3.0 / Scala 2.13

Monix 3.0 / Scala 2.13 release?

@aksharp 1.0.0-RC5 should be released for both Monix 3.0 and Scala 2.13


Little code change

You guys might need to add the declaration of the "remoteIp" inside the filter (executing):
var remoteIp = context.HttpContext.Connection.RemoteIpAddress;
Cheers!

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

ID: 517dfd6c-0771-77d8-66e1-d07724134c6c
Version Independent ID: 51de9bc4-775c-36b6-79d4-71ff635b53a6
Content: Client IP safelist for ASP.NET Core
Content Source: aspnetcore/security/ip-safelist.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @damienbod
Microsoft Alias: riande

🙈 Good idea @SndrSchnklshk! 🙈
Thanks ... I'll take care of it.


is this repo still maintained?

 And still, there are lots of issues reported and PRs waiting to be merged.
Is this repo still maintained? if not please add a note in the readme file.

@skv-headless

more importantly, is there an active fork?


Add iam:ListPolicyTags to recommended policy

Issue #, if available:

Fixes aws-controllers-k8s/community/issues/1296

Description of changes:
This PR is to add the missing iam:ListPolicyTags permission to the policy document.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks good!
/approve

/lgtm


[FIX] member was redirecting to wrong place

Objective:
Member only was redirecting to the wrong place

ah! Sorry!


I am unable to see the results of my JS code

For example if i type "rect(100, 100, 100, 100); I do not see a rectangle in the output.
I know I must be doing something wrong.
can you assist?
<EMAIL_ADDRESS>

Bin url??
On 21 May 2015 06:31, "Drock490"<EMAIL_ADDRESS>wrote:

For example if i type "rect(100, 100, 100, 100); I do not see a rectangle
in the output.
I know I must be doing something wrong.
can you assist?
<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub
https://github.com/jsbin/jsbin/issues/2376.

drock490/test

first time here...

Can you try that again. This isn't a bin url: https://jsbin.com/drock490/test

http://jsbin.com/feseme/1/ here is my site
I enter "rect(10, 10, 10, 10); " I should see a rectangle

No, that's not JavaScript (nor a jsbin issue). I suggest checking out http://eloquentjavascript.net/ or posting your question to a community like StackOverflow - as you're asking a question about how JavaScript works.
Cheers and good luck.


mtar generated on Windows cannot be deployed when native node module is included

When building an mtar with a NodeJS app on Windows and the app contains a dependency which calls node-gyp-build as installation instruction, e.g. bufferutil , the deployment will fail.
We created a sample repository with which the issue can easily be reproduced. It also contains two prebuild mtar artifacts, one built on MacOSX and one built on Windows 10. You can either use those or build them again if you have those environments available. They got built with mbt build.
The build works fine, but the error will happen during deployment of the Windows build to CF with cf deploy com.example.application_0.0.1-win.mtar.
Deploying the artifact built on MacOSX works also fine on Windows.
Please provide the following info:

MBT Version: 1.0.16
OS Version: Windows 10 1909
If possible, provide a link to the project
https://github.wdf.sap.corp/D045390/node-gyp-issue

Steps to Reproduce:

mbt build on Windows machine of the given project
cf deploy of the mtar archive with latest cf multiapps plugin (v2.5.0)
observe deployment failure with error message

Prebuild detected (node_modules already exists)
Rebuilding any native modules
<EMAIL_ADDRESS>install /tmp/app/node_modules/bufferutil
node-gyp-build
sh: 1: node-gyp-build: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR<EMAIL_ADDRESS>install: `node-gyp-build`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
...
**ERROR** Unable to build dependencies: exit status 126
ERR Failed to compile droplet: Failed to run all supply scripts: exit status 14

Hi @Kiemes ,
I could not find a difference in the mtars.
The issue should be addressed first by CF-MTA deploy service.
Regards

@michawai Could you please forward this to the cf mta deploy service? I don't know how to reach them. Also please link the issue here so we have a complete thread. Thx so much.

Hello @michawai,
If the Mac-build mtar gets deployed successfully and the Windows-build mtar - not, then this issue is not related to the MTA deploy service and it is most probably related to MBT or the used build/package tools. Keep in mind that the MTA deploy service does nothing with the application sources, but only gives them to the NodeJS buildpack for staging (where the error comes). I assume that the NodeJS buildpack does the same for both the Mac-build and the Windows-build mtars. What about the case in which the Windows npm adds some permission restrictions to the node_modules or something like that?
Regards,
Radoslav

@michawai Since we figured out that the issue is with the mta-build tool in combination with Windows, could you please reopen the issue?
To bring the findings here, the issue is that when you do an npm install on a Windows machine of a node project with a dependency that calls node-gyp-build, it will download the binaries of node-gyp. Those binaries will not have an executable flag set in their permissions since Windows has a different permissions system then unix-like systems. Trying to execute this binary within the node buildpack will fail as this is using a linux container.
I wonder how the cf cli does this with cf push when running on windows, packaging everything into an archive and uploading this to CF. Are they modifying the binaries locally first before archiving? Or are they modifying the files within the archive? The archive will also be handled by the same buildpack in the same container image.

Hi,
By design, the MTA build tool does not perform any "magic" manipulations for module builds. It just applies standard technologies commands according to the module type and then packages the build results "as is" into an MTA archive.
By default, for nodejs modules, it applies the "npm install --production" command in the module's root folder and then takes this folder with all its content into the MTA archive. You can track this behavior via the build console output.
If the applied command does not produce the expected results, the MTA tool cannot do anything about it. You can raise this issue to the package that has the problematic dependencies or configure a different command of your own that solves the issue.
As the issue cannot be resolved by the tool, I am closing the issue.
Regards
Natalia


Add initial documentation for RQT2

Pretty self explanatory. We'll definitely be updating this closer to Crystal's launch.

@dirk-thomas please review

@dirk-thomas I've applied updates re: the feedback, can we get this merged in?

I've applied updates re: the feedback, can we get this merged in?

Using the case / term RQT2 isn't something I want to merge. The documentation should either use rqt (which is the case used throughout ROS 1 documentation as well as the GUI and the code) or I would be ok with following the suggestion from @chapulina to use RQt (due to the case of Qt itself). In the latter case this patch should be extended by a set of PRs to the source which update the usage of rqt to RQt in the GUI / code.

Argument 1: when your rational for renaming catkin to ament, and then to colcon, was google searchability. I would like the documentation for RQT2 to be easily searchable as opposed to RQT original.

The separation of catkin and ament is based on the fact that their API is very different. Major concepts from catkin like the devel space have been removed in ament. Due to that significant different a name change was chosen. That is not the case for rqt. The code base is mostly identical. Only minor changes have been applied. So this is comparing apples and oranges.

Argument 2: Rviz was renamed to Rviz2 even though it looks exactly the same. This is an equivalent Qt GUI that is being ported to work with ROS2, so it should be renamed to have the "2". What are we going to do when we migrate the rviz2 plugin to rqt?

The same rational applies here: rviz has been significantly refactored to accommodate sharing a lot of the code across the major ROS versions. There are actually two different packages within the same repo named rviz and rviz2.

Argument 3: Everything else in core ROS was completely renamed (rcl?) so why do we have to keep the name RQT when its a new thing?

That statement might be true for some package but certainly not for all packages. rclcpp is a completely different implementation than roscpp and also needs to be able to coexist in a single compilation unit. Many other packages (e.g. tf2, image pipeline, gazebo_ros_pkgs and many more) keep their package name as-is. In the transition to ROS 2 they haven't undergone any drastic changes and existing documentation still applies as is.
So I still think we should keep the name without a 2 suffix.

@dirk-thomas renamed to just RQt, please merge.

We can perfect this documentation in future PRs, this one gets us started and is ready to merge.

I guess some changes have been force pushed which wiped some recent changes applied. I will have to re-review and apply them again...

I guess some changes have been force pushed which wiped some recent changes applied. I will have to re-review and apply them again...

I don't understand, did you make changes to to this PR ontop of my commits? You didn't mention this if you did. Its common practice to git amend small fixes, which is exactly what I did. I believe Tully taught me to do this, actually.

Branches which are shared and iterated on by multiple people shouldn't be force pushed. Every time reviewers get back to it and want to see what has changed since their last review they need to re-review the full diff without any information what has changed.

This branch is in my personal @davetcoleman fork, so I wasn't aware its changed.

Every time reviewers get back to it and want to see what has changed since their last review they need to re-review the full diff without any information what has changed.

I wasn't aware of this policy but I do see the value given the limitations of GitHub. I'm spoiled by Gerrit which shows every past commit diff, even when you force push.


Add reindex ITs

Description
Add reindex ITs in neural search
Issues Resolved
Issue: https://github.com/opensearch-project/neural-search/issues/386
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@zane-neo can we add reindex IT for other processors too?

@zane-neo any update on this PR?

@zane-neo can we add reindex IT for other processors too?

The issue in ml-commons is not specific to individual processor, it's more like a generic issue(user info not restored after the listener ran), so one or two processor to cover this is enough I thought.

@zane-neo can we add reindex IT for other processors too?

The issue in ml-commons is not specific to individual processor, it's more like a generic issue(user info not restored after the listener ran), so one or two processor to cover this is enough I thought.

I won't agree with this. It will be good if we have reindex ITs for atleast all the local model like splade and text embeddings. Text + image processor works on remote model so we cannot integrate here.

@zane-neo can we add reindex IT for other processors too?

The issue in ml-commons is not specific to individual processor, it's more like a generic issue(user info not restored after the listener ran), so one or two processor to cover this is enough I thought.

I won't agree with this. It will be good if we have reindex ITs for atleast all the local model like splade and text embeddings. Text + image processor works on remote model so we cannot integrate here.

This PR already includes splade and text embedding processors.

Using Text_image_embeddings processor with only text field should work with local model. Processor uses mlClient to call the model, and model type is abstracted by the client.

Using Text_image_embeddings processor with only text field should work with local model. Processor uses mlClient to call the model, and model type is abstracted by the client.

it's a text embedding case right?

Using Text_image_embeddings processor with only text field should work with local model. Processor uses mlClient to call the model, and model type is abstracted by the client.

it's a text embedding case right?

I think it's not. Embeddings are only text, that's correct, but the processor is text_image. That processor can work with text, image and text+image. If we want to test that reindexing works with all processors it would not be correct to test it with text_embedding and assume that text_image_embedding processor is also tested.

Using Text_image_embeddings processor with only text field should work with local model. Processor uses mlClient to call the model, and model type is abstracted by the client.

it's a text embedding case right?

I think it's not. Embeddings are only text, that's correct, but the processor is text_image. That processor can work with text, image and text+image. If we want to test that reindexing works with all processors it would not be correct to test it with text_embedding and assume that text_image_embedding processor is also tested.

current tests covered local models which can prove the correctness of ml-commons code, no need to add other cases IMO.

current tests covered local models which can prove the correctness of ml-commons code, no need to add other cases IMO.

This is not the sole purpose of these tests. If the purpose is for correctness of ML code, the tests should be in MLCommons.
We want to cover as many use cases as possible in which an ingestion processor can be used. Re-indexing is one of the use-case here. I know we started this PR as part of making sure that bug we got here: https://github.com/opensearch-project/neural-search/issues/386 can be caught in future, but that is not the sole purpose of the tests.

current tests covered local models which can prove the correctness of ml-commons code, no need to add other cases IMO.

This is not the sole purpose of these tests. If the purpose is for correctness of ML code, the tests should be in MLCommons.
We want to cover as many use cases as possible in which an ingestion processor can be used. Re-indexing is one of the use-case here. I know we started this PR as part of making sure that bug we got here: #386 can be caught in future, but that is not the sole purpose of the tests.

There're quite a lot different flows/features in OpenSearch, e.g. shrink index, split index, restore index etc. Do we have a way to cover all these features when implementing a new feature to ensure they're not breaking? Is covering only reindex enough?

Do we have a way to cover all these features when implementing a new feature to ensure they're not breaking? Is covering only reindex enough?

Given the issue in hand we should start with re-index and then add more case which you provided after this. We can cut a github issue to make sure that we are covering the cases you mentioned too.

Do we have a way to cover all these features when implementing a new feature to ensure they're not breaking? Is covering only reindex enough?

Given the issue in hand we should start with re-index and then add more case which you provided after this. We can cut a github issue to make sure that we are covering the cases you mentioned too.

Is there already a generic approach to address this? Like which can be used for all plugins so that no need to implement this in individual plugin separately?

Do we have a way to cover all these features when implementing a new feature to ensure they're not breaking? Is covering only reindex enough?

Given the issue in hand we should start with re-index and then add more case which you provided after this. We can cut a github issue to make sure that we are covering the cases you mentioned too.

Is there already a generic approach to address this? Like which can be used for all plugins so that no need to implement this in individual plugin separately?

As per my understanding there is no such thing. Main thing which I was trying to put here was, you are adding ITs only for sparse and text embedding processor. There are other processors too in the plugin. So it will be better if you can add re-index ITs for those processors too.

Will do more test on open source part to reproduce this issue, will reopen this or create a new PR to this. Closing this now.


Libuwsc and rtty only support aarch64?

RT, I just tested building in ubuntu-18.04-amd64-docker env and found an error:
Scanning dependencies of target uwsc
[  5%] Building C object src/CMakeFiles/uwsc.dir/uwsc.c.o
[ 11%] Building C object src/CMakeFiles/uwsc.dir/log.c.o
[ 16%] Building C object src/CMakeFiles/uwsc.dir/utils.c.o
[ 22%] Building C object src/CMakeFiles/uwsc.dir/buffer.c.o
[ 27%] Building C object src/CMakeFiles/uwsc.dir/sha1.c.o
[ 33%] Building C object src/CMakeFiles/uwsc.dir/base64.c.o
[ 38%] Building C object src/CMakeFiles/uwsc.dir/ssl.c.o
make[2]: *** No rule to make target '/usr/lib/aarch64-linux-gnu/libev.so', needed by 'src/libuwsc.so.3.2.2'.  Stop.
CMakeFiles/Makefile2:87: recipe for target 'src/CMakeFiles/uwsc.dir/all' failed
make[1]: *** [src/CMakeFiles/uwsc.dir/all] Error 2
Makefile:129: recipe for target 'all' failed
make: *** [all] Error 2

This is my dockerfile, those COPY are the source code I downloaded from the release. 'install-rtty-6.sh' is the official script to build rtty you provided. I just modifed it to use the local source code.
FROM amd64/ubuntu:18.04
USER root

# change to Asia/Shanghai
ENV TZ=Asia/Shanghai

COPY rtty/libuwsc-3.2.2/ /root/libuwsc-3.2.2/
COPY rtty/install-rtty-6.sh /root/
COPY rtty/rtty-6.6.1/ /root/rtty-6.6.1/
COPY rtty/supervisor-linux-amd64 /root/

RUN sed -i s@/archive.ubuntu.com/@/mirrors.aliyun.com/@g /etc/apt/sources.list \
    && apt-get clean \
    && apt-get update -y \
    && apt-get install -y apt-utils libev-dev \
    && chmod 777 /root/install-rtty-6.sh \
    && cd /root \
    && /bin/sh install-rtty-6.sh \
    && chmod 777 /root/supervisor-linux-amd64

CMD ["/root/supervisor-linux-amd64"]

I tried in Cent OS 7 amd64 and Ubuntu 18.04 amd64 host, all failed leaving that error. :(

Please use the latest version.


Migrate devicelab tests and test runners to null safety.

Part of #85995.
This migrates the devicelab tests and test runners to null safety. With this everything in the device lab should be running with null safety turned on.

Just pulled in the latest from the other PRs that landed recently.
This is still currently blocked by a bug in vm_service: https://github.com/dart-lang/sdk/issues/46559, which will have to be resolved and rolled into flutter master before this can land.


Refactor annot-columns for new store

The annot-columns component needs to be refactored to prepare for our big store refactor.
Use cases - I/O

[x] Display columns mapped to the current category: while I am annotating a specific category, this component shows me a list of all the columns that have been mapped to this category (in the previous categorization step).

input:

activeCategory (prop from parent): I need to know what category I am invoked for
mappedColumns (or some better name) (getter): the store should return all the columns to me that have been mapped to my activeCategory
columnDescription (getter): as I am building my visual representation of the columns, I go back and ask the store if there are any descriptions for each column

output: none

[ ] Fire a store mutation to remove a column from this category (unlink): if I notice that one of the columns has been linked to my activeCategory by accident, then there should be some UI element that allows me to "unlink" this column so that it is no longer linked to my activeCategory in the store

input: as above
output:

unlink / changeCategoryLink (mutation): fire a store mutation for the column that is being unlinked (we might already have something like this that can be reused in #243)

Internal State
This component doesn't have to keep local state
Tasks

[ ] Write the component tests to test (at least) the two above functionalities
[ ] Include in the test a mock of the mutation (for documentation, not technically necessary)
[ ] Refactor the component to pass the component tests
[ ] Check that there is no logic leftover inside of the component that we don't need any more

Does removeColumn method in the current implementation in a way do the unlink/changeCategoryLink mutation's job mentioned here?

Very close, but not quite. It emits the fact that a column should be removed / unlinked as an event that a parent component would have to listen to. We instead want to declare this to the store via mutation / action

So check when the button is clicked a mutation is set off?

Yes, that's how I had thought of the second functionality checkbox in the issue description.


Remove argo-dataflow pipelines component from the UI

Summary
What change needs making?
People ask a lot about what this is and why it always errors out on this page. Given that argo-dataflow is still in argoproj-labs and under major refactoring/updates (possibly no longer part of Argo?), we should consider removing it from the UI.
WDYT? @alexec

Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Yes. I think this is a dupe?

https://github.com/argoproj/argo-workflows/issues/7088 is a more general request. I can take this specific one though.

Not a dupe. I think most of the original work would have been done in a57b3ad9e. Try reverting that. You'll find a lot of conflicts, prefer what is on master. The search for dataflow, Dataflow, pipeline to see what was missed.

@alexec @terrytangyuan
We currently use argo dataflow pipelines and rely on it being present and usable within argo.
Does this change mean we can't use argo dataflow pipelines with Argo 3.4+ ?

Yes you'll have to use it separately.


Dev Test: Mean: Share and Balance 1.0.0-dev.6

Dev Test
Mentions: @samreid @amanda-phet @kathy-phet
Simulation links

github repository for issues
phet top level directory
sim: all_phet.html

Test Matrix
Please include all (non-screen reader) feature testing in these records if applicable.

[x] Latest macOS, Safari (Time = 2.5hrs)
[ ] Windows 10, Chrome (Time = 1)
[ ] Windows 10, Firefox (Time = )
[x] Latest iOS, Safari (Time = 2hrs)
[x] Windows 11, Chrome (Time = 2)

Light testing, or optionally skip if time crunch:

[x] Latest macOS, Chrome (Time = .75hr)
[x] Latest Chrome OS, Chrome (Time = 1.5hrs)

Features included

PhET-iO
[x] Alternative Input (Including multi touch)
UI Sound
Sonification
Description
Voicing

Focus and Special Instructions
Focus of this test is to release a prototype of Intro Screen. This is the second time QA is taking a look, everything is fair game.
Issues to Verify

[x] https://github.com/phetsims/mean-share-and-balance/issues/29

For QA...

General features

What to Test

Click every single button.
If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Try to include browser version numbers
If there is a console available, check for errors and include them in the Problem Description.
Run through the string tests on at least one platform, especially if it is about to go to rc.
Check the Game Up harness on one platform.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a
screen reader bug, please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel controls. Please test magnfication and make sure
it is working as intended and well with the use cases of the simulation. Due to the way screen readers handle user input, magnification is NOT expected to
work while using a screen reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

Memory test:

Calling QA here.

Closing this dev test as done.


"python -m digits.download_data" fails with TypeError exception

using the python script described in the wiki to download dataset fails with the following error:
[milijan@OAK digits]$ python -m digits.download_data cifar10 ../cifar10
Downloading url=http://www.cs.toronto.edu/~kriz/cifar-10-python.tar.gz ...
Uncompressing file=cifar-10-python.tar.gz ...
Extracting images file=../cifar10/cifar-10-batches-py/data_batch_1 ...
Traceback (most recent call last):
File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"main", fname, loader, pkg_name)
File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/data/digits/digits/download_data/main.py", line 44, in
d.getData()
File "digits/download_data/downloader.py", line 34, in getData
self.processData()
File "digits/download_data/cifar10.py", line 57, in processData
self.__extractData(filepath, phase, label_names)
File "digits/download_data/cifar10.py", line 102, in __extractData
PIL.Image.fromarray(image).save(filename)
File "/usr/lib64/python2.7/site-packages/PIL/Image.py", line 1477, in save
save_handler(self, fp, filename)
File "/usr/lib64/python2.7/site-packages/PIL/PngImagePlugin.py", line 608, in _save
ImageFile._save(im, _idat(fp, chunk), [("zip", (0,0)+im.size, 0, rawmode)])
File "/usr/lib64/python2.7/site-packages/PIL/ImageFile.py", line 456, in _save
e = Image._getencoder(im.mode, e, a, im.encoderconfig)
File "/usr/lib64/python2.7/site-packages/PIL/Image.py", line 395, in _getencoder
return encoder(mode, *args + extra)
TypeError: function takes at most 4 arguments (6 given)

My issue was related to PIL/Pillow install and was fixed by uninstalling PIL. I'll leave this issue open in case there is a more elegant way to handle the error.

What platform are you on? Who uses /usr/lib64/?

It certainly does look like a problem with your PIL installation. Thanks for reporting back.

no worries. Cheers.
On Tue, Oct 11, 2016 at 11:31 PM, Luke Yeager<EMAIL_ADDRESS>wrote:

It certainly does look like a problem with your PIL installation. Thanks
for reporting back.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIA/DIGITS/issues/1150#issuecomment-253066653, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABOnfEuRU40GcSw_-urAB2CXfYDAaITJks5qzA5IgaJpZM4KTCgh
.


luci-base: update Japanese translation

Updated Japanese translations.
Signed-off-by: INAGAKI Hiroshi<EMAIL_ADDRESS>

Thanks!


Updating a card is a POST action, not PUT

See docs: https://stripe.com/docs/api#update_card
Code at: https://github.com/robconery/stripity-stripe/blob/master/lib/stripe/cards.ex#L81
I was planning to send you a patch, but #62, and the number of open pull requests suggests I should look elsewhere. 😦

I'm busy, just like you. I have a family and summer vacations to juggle and, yeah sometimes these PRs might sit for a few weeks until I can get to them. I'll be honest with you: I don't appreciate the comment.
As far as POST vs. PUT - I'd love to have your help if you had the time because as you can tell, I'm having a hard time pulling in the PRs quickly. Most of this is due to switching over to coveralls and trying to figure out how the builds can run safely.

Apologies. It was frustrating to be met with a failing build when I have such a small change to make. I understand that it's open source and I shouldn't expect you to drop everything to fix up stripity_stripe.
Thanks for cleaning up the PRs.
I'm not sure I understand the current issue with the build and Coveralls. Is it an issue with specifying the Stripe credentials in such a way that they don't leak?

@nathany the build is now fixed in https://github.com/robconery/stripity-stripe/pull/64. Coveralls is not an issue (it usually is when a PR reduces the % of code coverage, which was not the case with the build right now).
There actual problem with the build was the fact, that we began escaping properly (in https://github.com/robconery/stripity-stripe/pull/59), and VCR cassettes were recorded back when escaping was done incorrectly. This was addressed in #64 .

@nathany I've fixed this issue in #66. That PR still fails, as others, until #64 is merged.

Closing for now - cheers all thank you for your help :)>


Request for Docker

Think this way, we could all avoid library incompatibility issues and enjoy it with even greater with fellow internet buds.

Super logical, but maybe the microphone and screenshot mechanism can be really hard.

We will publish within 3 days later


Ms multimap

In this PR

allow multiple mapping reads to be tag-ed with multiple gene ID
update dropseq docker

jenkins retest please

retest this please


Support SongPro format

The SongPro format looks interesting. It'd be nice to support it as a file format and in the editor.
cc @spilth

Do you have a preference for how you'd like to specify/determine the format of a song that a user is providing?
A couple of options I can think of:

Check for attributes set in either ChordPro or SongPro style in the source of a songsheet.

For example: {t: Losing My Religion } vs @title=Losing My Religion
It would probably be good to have a format attribute we manage internally to "cache" the answer of this whenever a Songsheet is created/updated.

Make the user specify which format they are using via a dedicate form field.

For example, a select option or radio button selection
Requires more user work and potentially something they could get wrong.

There is currently a very rudimentary heuristic for deciding which parser to use that could be quickly added to, but there are a few caveats:

Both the displaying of songsheets and editing currently assume a ChordSheetJS parser and directly use the returned Song model. So the new parser either needs to be implemented in ChordSheetJS, or some kind of new model is needed that both are convert into.
The editor currently has logic to convert to chordpro on paste. There's nothing in the server-side storage that currently requires chordpro, so it wouldn't be difficult to support other formats as long as they can provide metadata.
The editor has a mode for chordpro with snippets, chord completion, and metadata completion. It'd be nice to have the same features for SongPro.

So that first one is really the biggest lift.


["RFC"] Adding end-to-end regression tests

Looking through the repository, I was not able to find a place where to put end-to-end regression tests. I think it'd be great to take advantage of the reproducers provided in bug reports to add new regression tests. E.g., the code in issue #1601 would make a great regression test to accompany PR #1602.
Is this already done anywhere and did I miss it? If not, is there any reason why we should not do that?

We already have some end-to-end tests.
https://github.com/openai/triton/blob/main/python/test/unit/operators/test_inductor.py

Right---though is the intent is for those to be general end-to-end regression tests? My understanding, also based on the test/unit/operators path, makes me think that this is about specific existing kernels.

I'm not sure where this should be. Seems to me that you can simplify it a bit and add it to test_core.py. cc @ptillet

I have some troubles seeing what you mean by end-to-end regression tests, since to me the - inductor and operators test fall into that category.
To me it seems like this particular example should be an additional lit test for the pipeline pass


There are no such file.

Instead, explicitly show that its a placeholder for a file name.

Coverage remained the same at 88.806% when pulling 47fca4e2828a10e412e8a24a7c7f91dd7d806577 on hbina:patch-1 into 702e7f1e158348e873740c24c09658df62799e83 on alex-dukhno:master.


should include tmux and tpm install scripts

curl
rustup
nvim
dein
tmux
tpm
fish
fd-find
ripgrep

move config files to home directory

included for ubuntu by one of the last commits before the recent personal-hat branch merge :)


Random taps on hamster

Is it possible to make the taps on the hamster more random so as not to look like a bot? 3-4 taps per second for example or sleep after some clicks ?

When you tap in-game, the game will send taps to the server when you stop tapping for example: when you have 10000 points and if you tap all of them, the client will send only one request to the server. that's similar to that.


Compatibility of option flags and missing features

Hi there,
I have been long user of serve and what I liked about the server is that it was a simpler alternative to http-server.  However, I noticed the latest version of serve is now using different options compared to the last stable version 1.4.0. It seems that now some options are assumed as defaults (like compression enabled by default).
Somehow I prefer to specify explicitly if I want to enable a feature in the server or not, it's a much simpler mental model for using CLIs. I understand there is an ongoing code refactor but not sure why the server options are not backwards compatible?
For example, the latest serve version has the following options:
$ serve --help

  Usage: serve [options] [command]

  Commands:

    help  Display help

  Options:

    -a, --auth       Serve behind basic auth
    -c, --cache <n>  How long static files should be cached in the browser (seconds) (defaults to 3600)
    -o, --cors       Setup * CORS headers to allow requests from any origin (disabled by default)
    -h, --help       Output usage information
    -i, --ignore     Files and directories to ignore (defaults to "")
    -p, --port <n>   Port to listen on (defaults to 3000)
    -s, --single     Serve single page apps with only one index.html
    -u, --unzipped   Disable GZIP compression
    -v, --version    Output the version number

but version 1.4.0 uses this:
$ serve --help

  Usage: serve [options] [dir]

  Options:

    -h, --help                output usage information
    -V, --version             output the version number
    -a, --auth <user>:<pass>  specify basic auth credentials
    -F, --format <fmt>        specify the log format string
    -p, --port <port>         specify the port [3000]
    -H, --hidden              enable hidden file serving
    -S, --no-stylus           disable stylus rendering
    -J, --no-jade             disable jade rendering
        --no-less             disable less css rendering
    -I, --no-icons            disable icons
    -L, --no-logs             disable request logging
    -D, --no-dirs             disable directory serving
    -f, --favicon <path>      serve the given favicon
    -C, --cors                allows cross origin access serving
        --compress            gzip or deflate the response
        --exec <cmd>          execute command on each request

From looking at the server options, it seems some features are missing from the latest version?
One last thing, there seems to be an inconsistency (or bug) when passing a folder to serve (in latest version):
In serve 2.1.2:
# this doesn't pick up the folder as input
serve --cors ./my-folder
Running on http://localhost:3000

Hint: check your README.md

Run it
$ serve <path> [options]

In serve 1.4.0:
# this picks up the folder as input
serve --cors ./my-folder
serving /Users/random/my-folder on port 3000

This is the old package. The package name is now owned by a different group of people (@zeit - us) and we added a different content to it.
According to the semver spec, we acted just right and incremented the major version number.


Animated.View causing import { View } from 'react-native' to be flagged as 'View' is defined but never used.

Im not sure why there is a flag for when a View is used as an Animated.View for this.
The View is being used.. anyone know how to silence this ?
I do not want to create an animated component because its extra code that is not needed.

I'm not sure what you mean. Can you provide the exact code being warned, and the exact warning you get on the command line?

import { StyleSheet, View } from 'react-native'
// I get a warning about View not being used here because im turning it into a Animated.View
import Animated from 'react-native-reanimated'

const LoadingView = forwardRef((props, ref) => {
    return (
        <Animated.View ref={contViewRef} pointerEvents="none" style={style}>

        </Animated.View>
    )
})

export default React.memo(LoadingView)

You're not "turning it" into an Animated.View - you're not using View at all. Animated provides its own View which is what Animated.View references.
In other words, the linter warning is correct, and you should be able to just delete the View import entirely, and everything should work the same.

Ahhhh, noob mistake, thank you for clarifying.


IObit Uninstaller Pro Crack <IP_ADDRESS> + Key Download

IObit Uninstaller Pro Crack Free Download is a powerful uninstall application that helps you easily remove unwanted programs, even if Windows “Add or Remove Programs” fails. In addition to removing unwanted applications, it’s easy to scan and delete residues. The most appealing part is that it generates a recovery image before each uninstall. Using the newly added toolbar to uninstall modules, it helps you completely remove unwanted toolbars.
Download Link
The new tools in the IObit Uninstaller 13 Pro key 2024 can help them continue to scan the programs in the uninstall history and clean up other useless updates/installation packages and invalid shortcuts. Download the IObit Uninstaller Pro License Key website and you can even easily find the basic Windows tools.
/
/
/
/
/
/
/
/
/
/
/
/

✅▶▶DOWNLOAD IObit Uninstaller Pro
✅▶▶MIRROR IObit Uninstaller Pro Crack


Balder/test numconnections control

@lesters or @jobergum

There are test errors:
[ERROR] Failures:
[ERROR]   ConnectionParamsTest.testDefaults:28
Expected: is <1>
     but: was <4>
[INFO]
[ERROR] Tests run: 168, Failures: 1, Errors: 0, Skipped: 33

Tests help. Fixed


Watermark on an image

I used this command to add a watermark on an image:
ffmpeg -i input.png -i watermark.png -filter_complex overlay=15:15 output.png
But I got this error:
[NULL @ 0x7a1403f800] Unable to find a suitable output format for '/storage/emulated/0/images/img_wat.png'
I already add a watermark on a video but I don't know how to do that in this case for an image instead of a video.
Could someone help me please?

Please enable image2 and segment muxers!

FYI @msroid I use image2 command to create a slideshow of images in my app. Also, put a Watermark over a video as you commented.

@Aracem I can put watermark on a video but it doesn't work when I try to put a watermark on an image!
Have you tried to put a watermark on an image?


bobcat: 4.07.00 -> 4.08.03

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/bobcat/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 4.08.03 with grep in /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03
directory tree listing: https://gist.github.com/d768d97dc8cf8403bf62c2981e533bed

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: bobcat
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: bobcat
Partial log (click to expand)

  Installation completed
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03
shrinking /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03/lib/libbobcat.so.4.08.03
gzipping man pages under /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03/lib
patching script interpreter paths in /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03
checking for references to /build in /nix/store/dqhrp35b4vijwd6k77is0ma96vq9arwj-bobcat-4.08.03...

Success on aarch64-linux (full log)
Attempted: bobcat
Partial log (click to expand)
  Installation completed
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03
shrinking /nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03/lib/libbobcat.so.4.08.03
gzipping man pages under /nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03/share/man/
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03/lib
patching script interpreter paths in /nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03
checking for references to /build in /nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03...
/nix/store/nmcvqnc83nvq64l40lkd38jg6vvm8jr2-bobcat-4.08.03


[Bug]: Native ORACLE import stored procedure, comment line break error

ODC version
ODC424
OB version
independent
What happened?
Native ORACLE import stored procedure, comment line break error

What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?
58794_export_file.zip
Anything else we need to know?
No response
Cloud
No response

pass


I get connection error when I try to run map-reduce.sh command with kafka.pull conf

Hi
Any idea about this error... i can see my spark/hadoop/kafka looks fine but when i run the command
bin/gobblin-mapreduce.sh start --conf /home/ubuntu/gobblin/gobblin-dist/conf/config/kafka.pull
Exception in thread "main" java.net.ConnectException: Call From <<host name/IP>> to localhost:8020 failed on connection exception: java.net.ConnectException:e:  http://wiki.apache.org/hadoop/ConnectionRefused

@prasadnh please double check if localhost:8020 is the correct uri for your hdfs. You may use hdfs getconf -confKey fs.default.name to verify.

thanks for the response...
so we cannot have different port  for hdfs?but we are using 9000...
-Prasad
On Mon, Oct 19, 2015 at 4:52 PM, Ziyang Liu<EMAIL_ADDRESS>wrote:

@prasadnh https://github.com/prasadnh please double check if
localhost:8020 is the correct uri for your hdfs. You may use hdfs getconf
-confKey fs.default.name to verify.
—
Reply to this email directly or view it on GitHub
https://github.com/linkedin/gobblin/issues/394#issuecomment-149379315.

--
Thanks,
Prasad

@prasadnh please change the setting of fs.uri in conf/gobblin-mapreduce.properties to the correct URI for the NameNode of your HDFS setup, e.g., fs.uri=hdfs://localhost:9000.

Thanks... I put wrong port number in properties file...updated and tried again...
but I see same issue
Exception in thread "main" java.net.ConnectException: Call From <> to localhost:8020 failed on connection exception: java.net.ConnectException:e: http://wiki.apache.org/hadoop/ConnectionRefused

I think we cannot give localhost...instead we need to hostname with 9000...but i get different exception
Exception in thread "main" java.lang.IllegalArgumentException: java.net.UnknownHostException: hdfs

@prasadnh you can take a look at the stack trace. If the exception happens during the initialization of state store, you need to set state.store.fs.uri=hdfs://localhost:9000.

This value already there in properties file
state.store.fs.uri=${fs.uri}

what could be the reason command hangs forever here
./gobblin-mapreduce.sh stop --conf /home/ubuntu/gobblin/gobblin-dist/conf/config/kafka.pull
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/ubuntu/gobblin/gobblin-dist/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/bin/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

gobblin-mapreduce.sh does not support the option stop.

oops copied wrong command... same behavior with start
./gobblin-mapreduce.sh start --conf /home/ubuntu/gobblin/gobblin-dist/conf/config/kafka.pull
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/ubuntu/gobblin/gobblin-dist/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/bin/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

gobblin-mapreduce.sh does not support the option start either... Have you read https://github.com/linkedin/gobblin/wiki/Gobblin Deployment#Hadoop-MapReduce-Deployment?

sorry...not sure why I used this stop/start... i was running standalone before and just changed to mapreduce....
even no start/stop same issue... SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
./gobblin-mapreduce.sh --conf /home/ubuntu/gobblin/gobblin-dist/conf/config/kafka.pull
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/ubuntu/gobblin/gobblin-dist/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/usr/local/bin/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

I see process running but i don't see any logs, not sure its really working.

Please remove gobblin-dist/lib/slf4j-log4j12-1.7.5.jar and give a try.

@prasadnh any update on this issue?

No update... No success so far.
I am working on upgrading our servers... Will try one more time once it's up and running.
Sent from Outlook
On Thu, Oct 29, 2015 at 12:16 PM -0700, "Yinan Li"<EMAIL_ADDRESS>wrote:
@prasadnh any update on this issue?
—
Reply to this email directly or view it on GitHub.


Removed Vagrantfile from startproject command

Cleaned up another small relict from vagrant times...

Good catch - thanks!