exception_object in not present in payload

Hi, I am trying following from the Readme to have exception backtrace:
YourApp::Application.configure do
  config.lograge.enabled = true
  config.lograge.custom_options = lambda do |event|
    {
      exception: event.payload[:exception], # ["ExceptionClass", "the message"]
      exception_object: event.payload[:exception_object] # the exception instance
    }
  end
end

But once an error is raised exception_object is not present in a payload resulting to Could not log "process_action.action_controller" event. NoMethodError: undefined method "backtrace" for nil:NilClass.
Why it is not there and how I can get it?

@mkarganov Did you find a solution for this? I am also facing the same issue. payload[:exception_object] is nil for me.

@vik-y @mkarganov Where are the exceptions thrown? Do you have a stack trace?

No, I have not solved it. I log errors now within a custom logger which has access to exception by handling them via rescue.
@pxlpnk I would not try again, but if you will try the part from documentation that I posted and try to raise an exception via normal flow - you will find out that the proposed code does not work event object is nil

Exactly. I tried to test it by making a syntax error in my views and using the code provided in the documentation. I did get correct error message in payload[:exception] but payload[:exception_object] was nil.

It shows up for me in a subset of events. When it does it doesn't have any backtrace... Rails 5.0 here.

I am also facing this issue e.g inspection the payload I can see
:exception=>["ActiveRecord::RecordNotFound", "Couldn't find Upload with 'id'=318375"]
:exception_object is not set.

looks like lib/lograge/log_subscribers/base.rb might be the place to fix it:
      def extract_status(payload)
        if (status = payload[:status])
          { status: status.to_i }
        elsif (error = payload[:exception])
          exception, message = error
          { status: get_error_status_code(exception), error: "#{exception}: #{message}" }
        else
          { status: default_status }
        end
      end

This also explains a weird discrepancy that I had somehow worked around some time ago, I have a
config.lograge.formatter = lambda do |data| ...
...block, in which I reference data[:error] to get the exception


Risk of provisioning in production environment

Category

[x ] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

What are the known risks of provisioning the Custom Learning for Office 365 Beta Preview in a  production environment?

Hello @donavanmarais As with any Beta solution our service management team reserves the right to make changes to the service and its components.  As we are actively resolving bugs and UX issues you would likley need to update the WebPart.  At this point I'd advise that you test the solution but not in production as we are quickly moving toward coming out of our Beta phase.   Stay tuned on our Driving Adoption blog to learn more about this timing.  (https://aka.ms/DriveAdoption)

Thank you for your response. Perhaps I should ask the question this way rather: would you recommend provisioning this solution to a production tenant knowing that it contains bugs and UX issues or would you rather contain it to a test environment until such time as this solution comes our of your beta phase? Thanks

The best practice is to deploy to a test tenant as you work through the solution.  Both for the fixes we are creating and to familiarize yourself with the solution.   Technically there is no reason not to put it to production but practically speaking you don't want to reserve the site name with a "test".

Hello @donavanmarais As with any Beta solution our service management team reserves the right to make changes to the service and its components. As we are actively resolving bugs and UX issues you would likley need to update the WebPart. At this point I'd advise that you test the solution but not in production as we are quickly moving toward coming out of our Beta phase. Stay tuned on our Driving Adoption blog to learn more about this timing. (https://aka.ms/DriveAdoption)

Hi @karuanag , I've checked the Adoption blog but couldn't see anything regarding the timeframe for coming out of Beta. Could you provide a rough timescale? That would be really useful for our roadmap to roll this out to Production.


Autorest Regen Preview to 3.0.0-alpha.20231127.10 by Mingzhe Huang from refs/pull/3981/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3981

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


204 should be an integer in the generated OpenAPI document

When generating an OpenAPI document from an entity resource file, the 204 status is the only one that is generated as a string instead of as an integer.
Other (non-204) response statuses look like the following:
responses:
    200:
      description: Item found by id

For 204s, it will instead look like this:
responses:
    "204":
      description: Item deleted

To Reproduce
Steps to reproduce the behavior:

Use an entity resource file to create an OpenAPI document with the CLI
In the interactive prompt, for any given entity, select the HTTP methods PUT and/or DELETE
Check the generated OpenAPI document to see that the 204s are noted as strings

Expected behavior
Instead of "204", the status should simply be 204 (no quotation marks).

Fixed at #14


RN-153 Show emoji reactions on posts

Needs https://github.com/mattermost/mattermost-redux/pull/198 to work.
Summary
This PR adds the ability to display post reactions.
Ticket Link
https://mattermost.atlassian.net/browse/RN-153
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] Added or updated unit tests (required for all new features)
[ ] All new/modified APIs include changes to mattermost-redux (please link)
[x] Has UI changes
[ ] Includes text changes and localization file updates

Device Information
This PR was tested on:
iPhone 6 iOS 10
iPhone 7 iOS 10
Galaxy s7 - Android 6.0 API 23
Screenshots

@enahum done.

@jarredwitt what about the makeMapStateToProps function ?

@enahum should be there now.


feat(extension): conventional commit w/ gitmoji

Description

Extension: Conventional Comments
Addition to prepare a conventional commit with the option of using Gitmoji (emoji preference).
Type of change

Bug fix / improvement for somebody else's extension. Extension author: @krzysztofzuraw

Screencast

https://user-images.githubusercontent.com/3099369/147155782-fc63c992-531c-41dd-910f-cf7c0bde64cd.mov
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing

Before taking out of draft state for potential review, wanted to see if we could / should instead combine this with:

conventional-comments

https://github.com/raycast/extensions/pull/94

We could add an option if the person is writing a comment or a commit and keep this to one extension.
Thoughts @krzysztofzuraw ? If this is going down an acceptable path the PR can be reworked to include both.
Unsure if adding gitmoji makes this too opinionated for your initial extension addition. 🙇🏻

Awesome work 👍🏻 . Maybe we can combine those two extensions into one with option to use emoji or not in preferences? @JeromeFitz

Sweet, sounds great @krzysztofzuraw!
@pernielsentikaer I should have time to rework this PR over the weekend to keep as one extension within Raycast with two commands.
Conventional

Insert Conventional Comment
Insert Conventional Commit

Sound like a plan to merge them into one instead of having two similar extensions 😄

Hey there :wave:
Correct me if I'm wrong, but sometimes you have to combine several emojis in one commit. The example that first came to my mind is :beers: and any other emoji, but there are definitely more of them :thinking:.
So perhaps it makes sense to add smth like a plus button to add one more commit type? :smiley:

Hey guys, what's the status with this PR? (draft mode and last activity 28 days ago...)

👋🏻 @fe9lix , thanks for the ping.

♻ refactored the commit part to be more streamlined
🚚 moved it into the existing extension: conventional-comments

There are now two commands:

Insert Conventional Comment
Insert Conventional Commit

I've left the initial comment as-is, if we want to add in gitmoji / emojis to that later we can. CC: @krzysztofzuraw
Unsure if this extension should be renamed to conventional, however, was not sure how that may work with existing installs so left as-is.
@Four-Velocity I think that could be a cool idea for sure. Perhaps something that could be added in the future. 🆒

Thanks for the review @fe9lix and detailed breakdown. 💯
✅ Updated the checkbox to the proper standards. Removed the handler in preference to the Controlled Checkbox behavior. (+ removed ROADMAP from README).
For the last dropdown Format, the (current) intent is to show the 3 formats available to compile the information being set in the fields above. The last one does not have an emoji, as the user is not selecting a format that displays one.
https://user-images.githubusercontent.com/3099369/147262074-5169f61d-5a0c-46ab-8f8a-92cbd1abc901.mov
In general format could probably be more intuitive to the end user. I will give it more thought, however, maybe removing the format field in preference to it being a configuration setting could reduce clutter and enable a better user experience when the Breaking Change Info appears as well.
🤔  Maybe a more stepped approach where the person can focus (quickly) on one thing at a time and rapidly move through.


[request] smaller candle size (smaller than 1min)

Note: for support questions, please join our Discord server

I'm submitting a ...
[ ] bug report
[X] feature request
[ ] question about the decisions made in the repository

Action taken (what you did)
I've looked through the docs trying to find out where candleCreator got its "1min" minimum candle size from, hoping that there would be one variable referenced from a config file specifying the length of time in each mini candle (the ones from which 1hr/1day/etc candles are made).

Expected result (what you hoped would happen)
There would be a variable in some config file somewhere that was set to 60000 milliseconds or something like that, which could easily be changed to 10000ms or even 1000ms for smaller candle sizes.

Actual result (unexpected outcome)
the 1min candle size seemed to be hard-coded into the candleCreator, not something that could easily be changed.

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

I would suggest if someone is familiar with the gekko's internals, that they re-code the candleCreator to operate using a candle size that can be set either from a config file, or even set in just one variable at the top of the page. Maybe using a switch(minCandleSize) statement to determine some of the syntax for the candle start dates and such

I'm guessing this was for performance reasons? How difficult/valuable would it be to support this

Hey! There are a few different reasons why the candle is limited to 1 minute, the short story is here. The longer story:

It makes the whole codebase a lot simpler: throughput is limited (since in most situations you get one tick a minute outside of backtesting). It makes calculating bigger candles (say hourly candles) very lightweight: Gekko stores 1 minute candles on disk, converting those to hourly candles on the fly is not a heavy operation. If Gekko had second candles the performance would look very different for people who want to run over hourly candles. Since if you want second candles in your strategy Gekko can't store minute candles, since than you can't backtest over 1 second candles.
Since gekko is storing market data to disk, if we store minute candles we are not dealing with a lot of data, but secondly candles would mean up to 60 times bigger storage size.

The biggest thing though:
Gekko is a platform to create trend watching trading bots, this involves looking at how the price has historically developed and trying to base predicitons of of that. But the smaller your timeframe the more noise and the less reliable the concept of candles work. You can definitely build strategies that trade on shorter timeframes, but you wouldn't use candles:

You'd use raw trades.
You'd look at the orderbook since that directly impacts where there is price resistance right now. You'd study things like micro market structures and order flow imbalance.

Even though it sounds similar, it's a very different problem space. And when building strategies that trade on short timeframes you'd build a completely different system in all aspects. (Gekko is 100% based on candles).


Release 0.25.0, but different!

https://github.com/Kong/go-kong/pull/105 had the unwanted effect of bumping the go-logr version. This made KIC very unhappy: https://github.com/Kong/kubernetes-ingress-controller/issues/2045
Reverting it to re-tag the 0.25.0 release without it.

Codecov Report

Merging #107 (388fdf9) into main (406a40f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #107   +/-   ##
=======================================
  Coverage   43.49%   43.49%
=======================================
  Files          42       42
  Lines        3722     3722
=======================================
  Hits         1619     1619
  Misses       1786     1786
  Partials      317      317

Flag
Coverage Δ

2.0.5
38.04% <ø> (ø)

2.1.4
37.85% <ø> (ø)

2.2.2
37.85% <ø> (ø)

2.3.3
37.85% <ø> (ø)

2.4.0
37.85% <ø> (ø)

community
38.04% <ø> (ø)

enterprise
43.17% <ø> (ø)

enterprise-<IP_ADDRESS>
43.17% <ø> (ø)

enterprise-<IP_ADDRESS>
42.02% <ø> (ø)

enterprise-<IP_ADDRESS>
42.02% <ø> (ø)

enterprise-<IP_ADDRESS>
42.02% <ø> (ø)

integration
43.49% <ø> (ø)

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

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 406a40f...388fdf9. Read the comment docs.

Reverting it to re-tag the 0.25.0 release without it.

Re-tagging is a deadly sin - especially for "library" projects. Caution advised and recommend bumping up, burning tags when such things happen is a good thing.
This problem has been worsened by dependabots that fire off everyday.


CORS

Hi again. I have a suggestion, maybe you could add the CORS on the module itself since the request is done inside the module it will be confusing where to manage the CORS on browser side thank you. :)

CORS is enabled via separate server side api. It cannot be done in the javascript module.


Fatal error if the OUTPUT_DIR contains spaces

Waiting for a real fix of #138, add an error when the output_dir contains a space.

Hi @Krysztophe normally Perl supports this so I guess that the error occurs in a system command call. Can you post here the origin error message please?

@darold : see #138, that was just a call on the command line

Hi,
Simple fix for this case https://github.com/ng-pe/pgcluu/commit/161da1973e18a24753e591191046ed7680b2f6c4

Hi
Some others fix are required
WIP ...

As a real patch is WIP, I'm removing this PR


Resium Duplicates KML while in React StrictMode

I've encountered an issue with Resium in StrictMode on the following Resium versions:

1.16.1
1.17.1

Resium will duplicate KML while in StrictMode.
Steps to Replicate
These are the steps I used to replicate the issue.

Run npx create-react-app test-resium-duplication --template typescript
Inside the test-resium-duplication project, run npm install --save @craco/craco craco-cesium cesium<EMAIL_ADDRESS>Follow steps 3 and 4 here to set up craco
Replace the code in App.tsx with the following:

function App() {
  const kmlBlob = new Blob([
    '<kml xmlns="http://earth.google.com/kml/2.1"><GroundOverlay><color>55ffff</color><name>Region</name><LatLonBox><north>45</north><south>25</south><east>-80</east><west>-100</west></LatLonBox></GroundOverlay></kml>'
  ])

  return (
    <Viewer>
      <KmlDataSource
        data={kmlBlob}
      />
    </Viewer>
  );
}

Start the app
Open the React DevTools "Components" tab
In the Components tab, navigate to App > Viewer > Context.Provider
With Context.Provider Selected, select props > value > viewer > _dataSourceCollection > _dataSources
When in StrictMode, under _dataSources you will see:

Disable StrictMode (remove the React.StrictMode tags from index.tsx). Under _dataSources you will see:

+1 for this!
I am getting an entire duplication of the <Viewer></Viewer> component when using React.StrictMode on a brand new project.

Bump.  Getting the same issue.

+1, same issue.

The issue happens to all layers(?) under Viewer. I was wondering why onLayerAdd (under ImageryLayerCollection) was triggered 4 times for every layer


nixpkgs.hostPlatform not set

I want to use Nixos module with flakes to build Hyprland, while got error with nixpkgs.hostPlatform not set.
Command I execute:
sudo nixos-rebuild switch --flake '.#aimi'
Output:
[sudo] password for aimi:
error: Neither nixpkgs.hostPlatform nor the legacy option nixpkgs.system has been set.
       You can set nixpkgs.hostPlatform in hardware-configuration.nix by re-running
       a recent version of nixos-generate-config.
       The option nixpkgs.system is still fully supported for NixOS 22.05 interoperability,
       but will be deprecated in the future, so we recommend to set nixpkgs.hostPlatform.
(use '--show-trace' to show detailed location information

Expect output:
Everything is ok.
Other message:
NixOS version:
NixOS 22.11
nix version:
nix (Nix) 2.11.1
flake.nix:
# hyprland flake.nix
{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    hyprland.url = "github:hyprwm/Hyprland";
  };

  outputs = {nixpkgs, hyprland, ...}: {
    nixosConfigurations.aimi = nixpkgs.lib.nixosSystem {
      # ...
      modules = [
        hyprland.nixosModules.default
        {programs.hyprland.enable = true;}
        # ...
      ];
    };
  };
}

(the sample one in wiki)
flake.nix place:
/etc/nixos/env/hyprland/flake.nix
I run command in /etc/nixos/env/hyprland/
I checked my hardware-configuration.nix and fount nixpkgs.hostPlatform is ok:
nixpkgs.hostPlatform = lib.mkDefault "x86_64-linux";
And I've tried nixos-generate-config, still this error.
Is this my personal environment bug?

@fufexan

I don't have enough context about your pkgs to know what's wrong.
Are you setting nixpkgs.pkgs like I do here? Or are you letting the module system import it by itself?
I do not get this error, and neither does @colemickens. So there must be something different between our nixpkgs versions.
Something else I could add is to try using nixos-unstable instead of 22.11.

I'm experiencing this problem. Followed steps in wiki.

I'm experiencing this problem. Followed steps in wiki.

Did you solved it?

Do you have something like this in hardware-configuration.nix?
nixpkgs.hostPlatform = lib.mkDefault "x86_64-linux";

Edit 2 Try adding this to your inputs
inputs.nixpkgs.follows = "nixpkgs";

Why, exactly? This means you no longer get cache hits.

Edit 2 Try adding this to your inputs
inputs.nixpkgs.follows = "nixpkgs";

Why, exactly? This means you no longer get cache hits.

Adding inputs.nixpkgs.follows = "nixpkgs"; to my flake file resulted in the following error
error: stack overflow (possible infinite recursion)

Hi! @itsOnly1Jah - Could you share your config directory structure?
I am getting the same error on a fresh install and my configuration.nix, hardware-configuration.nix, and flake.nix are all in the same /etc/nixos directory.

Hi! @itsOnly1Jah - Could you share your config directory structure?
I am getting the same error on a fresh install and my configuration.nix, hardware-configuration.nix, and flake.nix are all in the same /etc/nixos directory.

I store my flake in a .setup directory of my home folder like so.  The only file that references the hardware-configurarion.nix  is my configuration.nix file.
├── flake.lock
├── flake.nix
├── hosts
│   ├── configuration.nix
│   ├── default.nix
│   ├── hardware-configuration.nix
│   └── home.nix
└── modules

Thank you very much. I'll give this structure a go over the weekend and hopefully fixes my issue as well.
Dritan
On January 23, 2023 6:54:03 PM EST, itsOnly1Jah @.***> wrote:

Hi! @itsOnly1Jah - Could you share your config directory structure?

I am getting the same error on a fresh install and my configuration.nix, hardware-configuration.nix, and flake.nix are all in the same /etc/nixos directory.

I store my flake in a .setup directory of my home folder like so.  The only file that references the hardware-configurarion.nix  is my configuration.nix file.

├── flake.lock

├── flake.nix

├── hosts

│   ├── configuration.nix

│   ├── default.nix

│   ├── hardware-configuration.nix

│   └── home.nix

└── modules

-- >
Reply to this email directly or view it on GitHub:
https://github.com/hyprwm/Hyprland/issues/1334#issuecomment-1401163905
You are receiving this because you commented.
Message ID: @.***>

Thank you very much. I'll give this structure a go over the weekend and hopefully fixes my issue as well. -- Dritan
…
On January 23, 2023 6:54:03 PM EST, itsOnly1Jah @.> wrote: > Hi! @itsOnly1Jah - Could you share your config directory structure? > > > I am getting the same error on a fresh install and my configuration.nix, hardware-configuration.nix, and flake.nix are all in the same /etc/nixos directory. I store my flake in a .setup directory of my home folder like so. The only file that references the hardware-configurarion.nix is my configuration.nix file. ├── flake.lock ├── flake.nix ├── hosts │   ├── configuration.nix │   ├── default.nix │   ├── hardware-configuration.nix │   └── home.nix └── modules -- > Reply to this email directly or view it on GitHub: #1334 (comment) You are receiving this because you commented. Message ID: @.>

Hi my friend, I am a noob in nix but I find a solution on web which add system = "xxxxx" line
nixosConfigurations.HOSTNAME = nixpkgs.lib.nixosSystem {
system = "x86_64-linux";
modules =
[
.......
];
};

If you're putting flake.nix and configuration.nix in the same place, make sure to import configuration.nix in flake.nix

If you're putting flake.nix and configuration.nix in the same place, make sure to import configuration.nix in flake.nix

Do you mind clarifying what you mean here? I am new to NixOS and can't find an obvious way to import the configuration.nix in to the flake.nix.
Thanks!

If you're putting flake.nix and configuration.nix in the same place, make sure to import configuration.nix in flake.nix

Do you mind clarifying what you mean here? I am new to NixOS and can't find an obvious way to import the configuration.nix in to the flake.nix.
Thanks!

Just add it to your nixosConfiguration modules is ok.
such as this one (original flake comes from Hyprland Wiki)
# hyprland flake.nix
{
  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
    hyprland.url = "github:hyprwm/Hyprland";
  };

  outputs = {nixpkgs, hyprland, ...}: {
    nixosConfigurations.aimi = nixpkgs.lib.nixosSystem {
      # ...
      modules = [
        hyprland.nixosModules.default
        {programs.hyprland.enable = true;}
        configuration.nix # Just like this, add the position of your configuration.nix to here
        # ...
      ];
    };
  };
}


fix(selection): highlight selected nodes when set programatically

This was introduced by #1133, it was a simple matter of forgetting to commit the selection after making changes to it which resulted in the nodes not being highlighted as they should be. A visual regression test is included to test that the selection is rendered properly.
Closes #1135.

Kazaaam!  That was fast!
Thanks for a regular contributor!
(Metacognitive Technology LLC)


Latest brew install needs extended sudo rights

This fixes: https://github.com/chef-cookbooks/homebrew/issues/105

Hey, @Sauraus, have you completed the DCO step? https://blog.chef.io/2016/09/19/introducing-developer-certificate-of-origin/ Here is some more info.

would really love this fix right now.  👍

Why has this not been merged?

@Sauraus There are a bunch of failures on CI from Rubocop—perhaps getting those fixed will move this along to getting merged 🙂

Additional errors I’m getting with this change applied onto 3.0.0:
    ==> Searching online for the Command Line Tools
    ==> /usr/bin/sudo /usr/bin/touch /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
    ==> Installing Command Line Tools (macOS Sierra version 10.12) for Xcode-8.2
    ==> /usr/bin/sudo /usr/sbin/softwareupdate -i Command\ Line\ Tools\ (macOS\ Sierra\ version\ 10.12)\ for\ Xcode-8.2
    Software Update Tool
    Copyright 2002-2015 Apple Inc.

    Downloading Command Line Tools (macOS Sierra version 10.12) for Xcode
    Downloaded Command Line Tools (macOS Sierra version 10.12) for Xcode
    Installing Command Line Tools (macOS Sierra version 10.12) for Xcode
    Done with Command Line Tools (macOS Sierra version 10.12) for Xcode
    Done.
    ==> /usr/bin/sudo /bin/rm -f /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
    ==> /usr/bin/sudo /usr/bin/xcode-select --switch /Library/Developer/CommandLineTools
    STDERR: sudo: no tty present and no askpass program specified
    Failed during: /usr/bin/sudo /usr/bin/xcode-select --switch /Library/Developer/CommandLineTools
    ---- End output of /opt/workstation/.chef/local-mode-cache/cache/homebrew_go < /dev/null ----
    Ran /opt/workstation/.chef/local-mode-cache/cache/homebrew_go < /dev/null returned 1

    Resource Declaration:
    ---------------------
    # In /opt/workstation/.chef/local-mode-cache/cache/cookbooks/homebrew/recipes/default.rb

     49:   execute 'install homebrew' do
     50:     command "#{homebrew_go} < /dev/null"
     51:     environment lazy { { 'HOME' => ::Dir.home(homebrew_owner), 'USER' => homebrew_owner } }
     52:     user homebrew_owner
     53:     not_if { ::File.exist? '/usr/local/bin/brew' }
     54:   end
     55: ensure

After which I added /usr/bin/xcode-select to the list of commands, and the Homebrew install worked (though a later install of a Homebrew cask failed with sudo issues).

I just ran several kitchen tests on my local mac and they all converged just fine, not a single fault to be found.

@Sauraus Did you run rubocop linting though? This is what the failed build indicates.

@discentem I did but I wasn't going to break the code just to satisfy rubocop BTW. When I run rubocop locally I get 16 offenses and not 6.
Inspecting 24 files
.C.C.C.C..W...C........C

Offenses:

Gemfile:10:1: C: Gem rake should appear before tomlrb in their gem group.
gem 'rake'
^^^^^^^^^^
Gemfile:12:1: C: Gem community_cookbook_releaser should appear before stove in their gem group.
gem 'community_cookbook_releaser'
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Rakefile:24:23: C: Avoid comma after the last item of a hash.
        progress: true,
                      ^
libraries/homebrew_mixin.rb:22:1: C: Missing top-level class documentation comment.
class Chef12HomebrewUser
^^^^^
libraries/homebrew_mixin.rb:42:14: C: Align the parameters of a method call if they span more than one line.
             "Homebrew owner is 'root' which is not supported. " \ ...
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
providers/cask.rb:46:1: C: Use alias instead of alias_method at the top level.
alias_method :action_cask, :action_install
^^^^^^^^^^^^
providers/cask.rb:47:1: C: Use alias instead of alias_method at the top level.
alias_method :action_uncask, :action_uninstall
^^^^^^^^^^^^
recipes/default.rb:43:14: W: (...) interpreted as grouped expression.
    variables (
             ^
recipes/default.rb:44:12: C: Avoid using {...} for multi-line blocks.
      lazy {
           ^
recipes/default.rb:45:11: C: Use the new Ruby 1.9 hash syntax.
        { :user => homebrew_owner, :hostname => node['hostname'],
          ^^^^^^^^
recipes/default.rb:45:36: C: Use the new Ruby 1.9 hash syntax.
        { :user => homebrew_owner, :hostname => node['hostname'],
                                   ^^^^^^^^^^^^
recipes/default.rb:46:11: C: Use the new Ruby 1.9 hash syntax.
          :commands => node['homebrew']['sudo']['commands'] }
          ^^^^^^^^^^^^
recipes/default.rb:72:121: C: Line is too long. [151/120]
  only_if { shell_out('/usr/local/bin/brew analytics state', user: homebrew_owner).stdout.include?('enabled') != node['homebrew']['enable-analytics'] }
                                                                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
resources/cask.rb:5:3: C: Align the parameters of a method call if they span more than one line.
  name_attribute: true, ...
  ^^^^^^^^^^^^^^^^^^^^^
resources/cask.rb:10:3: C: Align the parameters of a method call if they span more than one line.
  kind_of: String
  ^^^^^^^^^^^^^^^
test/integration/default/default_spec.rb:10:23: C: Use 0o for octal literals.
  it { should be_mode 0755 }
                      ^^^^

24 files inspected, 16 offenses detected

@tas50 I've fixed the rubocop warnings, but the spec tests are something entirely different IMO.

FWIW, as Sauraus seemed to see, we went the route of just installing Homebrew under its own system user which can do passwordless sudo. Then a “real” user just does e.g. sudo -Hu homebrew brew install whatever, and then we can just set the chef homebrew cookbook user attribute to “homebrew”.

@andrew-cc saw that yes, still scary to having a user with limitless sudo ;)

Since it’s a user that can’t be logged-in to, some other user must use sudo to become them. It’s perhaps a shame in some sense that Homebrew isn’t designed like any other major *nix package manager. In some sense it’s “safer” having everything owned by a different user since it prevents arbitrary user software from modifying /usr/local since it doesn’t have perms.

Agree with your sentiment.
PS. Don't say any of that to the Homebrew maintainers @Brantone has experience with that...

@Sauraus the spec failures are likely related to this issue https://github.com/chef-cookbooks/homebrew/issues/114.

I'm going to close this out at this point because this just isn't an appropriate solution for most users. We try to implement the path of least surprise at Chef and giving blanket sudo rights is not going to be expected or desired by a good chunk of our userbase.


need more pair for 1.14.3

hi, im looking for list of pair for 1.14.3
my core wallet sync very slowly and my pair node have 20k ms
anyone have à pair list ?

Here are some nodes you use:
[2a01:4f9:2b:1bde::2]:22556
[2a01:4f8:160:8048::2]:22556
[2001:19f0:6001:1409:5400:1ff:fe61:1558]:22556
[2a02:c207:2017:2654::1]:22556
[2a01:e34:ec29:e8d0:3884:86b6:a4d:815b]:22556
[2600:3c00::f03c:91ff:fe50:bfd4]:22556
[2001:bc8:4700:2400::100f]:22556
[2a04:ac00:4:d18:5054:ff:fe00:d35d]:22556


Count total pages in section

Hello, I've read the documentation many times, maybe I'm not very thorough, but can I count the total pages in a specific section and display it in the layout?
Thanks for any help.

Hello again there, sorry to bother hehe.I just explored the twig documentation page. My crooked logic thought and I found the way below. If there's still a shorter way, please keep telling me 😄
For example, the section I'm going to count is the "majors" section, I'm using a filter function, like this.
{{ site.pages.all|filter(s => s.section == 'majors')|length }}

Maybe the filter function that I use here also works if you want to display a list of pages that are in a section to a certain layout.
{% for major in site.pages.all|filter(s => s.section == 'majors') %}
    {# ... #}
{% endfor %}

If there's still a shorter way, please keep telling me

Nope, you use the best way! 👍


Something goes rogue for unknown reasons

Eats all the server CPU. Minimal information. Likely related to MariaDB migration. https://chat.stackexchange.com/transcript/message/46580791#46580791 - possibly related to deploys, check_smokey_status job, 11a UTC.

Can we get a status update on where we are with this, what's the current hypothesis?

@Undo1 I think we concluded this was MariaDB? But anyways, with the new 3-server setup, this is no longer an issue AFAIK.


Paint the code black

Let's implement the one and only uncompromising code formatter for python, just as the guys in https://github.com/CodeForPoznan/codeforpoznan.pl_v3 did :)
This includes both adding it to CI and reformatting the backend.

Let's discuss this on the next team meeting.


Merged HashtagsParser and IncludeInParser into ChangeInfoParser

Hi, proceeding with issue #119 I merged the classes HashtagsParser and IncludeInParser into ChangeInfoParser (now renamed ChangeInfosParser) as they all parse information at the change entry point level.
I also updated the copyright to 2021 in all the classes I modified.
As usual, let me know if something needs to be fixed or changed.

Thanks @EFregnan!


created Longest Common subsequence

Added a c++ file for Longest Common Subsequence using DP in C++

Hello @SR-Sunny-Raj ,
I have added a C++ code for Longest Common subsequence using DP in C++. Please check and merge my request.
Thanks

Sorry to inform but this repository has been excluded from hacktoberfest. So inorder to make your PR count towards hacktoberfest, request you to make your contribution in this repository -> https://github.com/SR-Sunny-Raj/Hacktoberfest2022-for-everyone


Can't get GlobalPackageReference to work with MinVer

Hi,
I can't get the GlobalPackageReference feature to work with the MinVer nuget package. It seems that it only include Analyzers and Build, but AFAIK it should include BuildMultiTargeting and possibly BuildTransitive as well (re. https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files)

You are correct, I'll update the IncludeAssets today and release a new version.  Thanks for reporting this!

Great. When can I expect the new package to be out on nuget.org?

https://www.nuget.org/packages/Microsoft.Build.CentralPackageVersions/2.0.52

Cheers!


Enable silent log no longer works

Since the last update, the "Enable silent log" no longer works. The messages are still all written in the output. Would it be possible to adjust this again so that you don't always have all the logs?
In general, the question would be whether it is possible to hide all messages? Even with the old version, not all logs were disabled if Enable silent log was checked.

Thanks for the info, I will verify that!
The silentlog disables all the logs expect critical stuff, besides that all the log will still appear in debug mode.

Ok, that would be great! Worked great for me before the update. But since the update, all the messages are coming. Here is an example of the messages that all come in.
[7.12.2023, 10:23:40] [webostv] [Fernseher] Connected to TV
[7.12.2023, 10:23:44] [webostv] [Fernseher] Got TV information
[7.12.2023, 10:23:44] [webostv] [Fernseher] TV webOS version: 6.0
[7.12.2023, 10:23:44] [webostv] [Fernseher] App launched, current appId: com.webos.app.livetv
[7.12.2023, 10:23:44] [webostv] [Fernseher] TV turned on!
[7.12.2023, 10:23:44] [webostv] [Fernseher] Channel changed. Current channel: 11, WELT HD, channelId: 7_32_11_11_1053_21108_1
[7.12.2023, 10:23:44] [webostv] [Fernseher] Sound output changed. Current sound output: tv_speaker
[7.12.2023, 10:23:44] [webostv] [Fernseher] Subscribed to TV services
[7.12.2023, 10:23:45] [webostv] [Fernseher] Connected to remote pointer input socket
[7.12.2023, 10:23:45] [webostv] [Fernseher] Setup finished
[7.12.2023, 10:23:45] [webostv] [Fernseher] TV setup finished, ready to control tv
[7.12.2023, 11:11:34] [webostv] [Fernseher] Pixel refresher started!
[7.12.2023, 11:17:52] [webostv] [Fernseher] TV turned off!
[7.12.2023, 11:17:52] [webostv] [Fernseher] Disconnected from TV
[7.12.2023, 11:17:57] [webostv] [Fernseher] Starting TV alive polling

I have just installed it and as far as I can see there are no more messages :-)
Thank you very much for the quick support and such a quick troubleshooting is really great! Thanks!
Marco


Re-write and re-imaging of via

Background
I started this project about four years ago as an experiment in exploring different code reuse patterns and separating concerns in Rust. At the time, async Rust was still in its infancy, and this project helped me understand the performance characteristics and constraints associated with concurrent programming in Rust. After putting together a few examples inspired by other web application frameworks with a strong OO influence, I eventually shelved the project for a couple of years.
Fast forward to June of this year. I found myself with some spare time and decided to dive back into Rust. What better way to reacquaint myself with the language than by revisiting an old project, right? Returning to the project with fresh eyes, I realized my original approach to thinking about Rust code was not very... rusty. This led me back to the drawing board to reassess my goals. With a background in the agency world and experience in both backend and frontend projects, I wanted to create something I would have appreciated in past projects. For better or worse, this brought me back to thinking about JavaScript.
JavaScript has been a popular choice for many high-profile clients at the agency I previously worked for. Being a multi-paradigm language, JavaScript allows programmers to express themselves in many ways. Combining its good parts with a relatively quick learning curve, it becomes a reliable choice for companies aiming for productivity. This got me thinking: since Rust is also a multi-paradigm language with an expressive type system and powerful features, is there a way to combine simplicity, power, and expressiveness to make Rust the best choice for backend server development?
Async Rust has evolved significantly over the past four years. Like JavaScript, it has both its strengths and weaknesses. Fortunately, many great frameworks now make it enjoyable to be a Rust programmer. If your team knows what they're doing, it's hard to go wrong with the available frameworks today. With that said, I envisioned a framework that caters to both Rust experts and beginners. Here is what I came up with.
Principles
At the start of any project, it's essential to define the problem you're solving and decide on the trade-offs you're willing to make. We've seen time and again that file systems, databases, and external services often become the bottlenecks in a web application backend. However, we're writing Rust for a reason, so let's not be wasteful with CPU cycles or memory where it matters. But let's also be practical and think about the people writing the code rather than just the computer running it.
Hyper is a state-of-the-art HTTP library that offers excellent performance out of the box. Like many other frameworks, starting with a solid foundation, such as a fast and correct HTTP implementation, is crucial. However, what happens next can make or break the rest of the stack.
Consider the following principles like layers of a cake, each representing a different level of abstraction. Starting from the bottom up. Except for the section on Security—it's mentioned last but it's not the top layer. It's more like the plate that the cake is served on.
Fast and Flexible Routing
One hallmark of a great web application backend is the separation of concerns. When onboarding to a new project, a great way to start is by examining all the routes available in an application. URL paths and routes often form a tree-like structure that indicates the separation of concerns for a particular web server. For example, routes prefixed with /api will likely return a JSON response. With that in mind, let's use the path as a starting point for code reuse. Since the router I started working on four years ago could be considered a prefix-tree, we were already off to a good start.
Philosophy
An engineer should be able to open a file and see every possible route that can serve a request. Co-locating associated middleware for a route and its descendants alongside the HTTP method a route accepts makes it easy to see what happens when someone visits the corresponding URL. Let's not introduce any ambiguity here. In my opinion, it's more important to see the HTTP method at the route definition rather than the function. Additionally, it's helpful to know that the function signature for any given middleware or responder is async fn _(request: Request, next: Next) -> Result<Response>. Therefore, I decided to remove the codegen crate to rule out the use of proc-macros to define routes.
Many frameworks, such as Tide, follow this philosophy, and you can see Tide's influence on the public API of the router. However, there's one crucial difference in how routing works in via compared to Tide. Via supports the concept of partial route matches by leveraging the tree-like data structure of our routes. The benefit of this feature is that we can use the URL path as a 1-to-1 mapping of the separation of concerns across routes and resources in a via application. For example, suppose a new JIRA ticket is automatically created from webhooks to an error reporting service with the title JSON.parse: unexpected character at line 1 column 1 of the JSON data. This is likely caused by an error response returned from an endpoint that should respond with JSON, but in case of an error, a plaintext response is sent to the client. With via, you can include middleware that runs unconditionally anytime the URL path partially matches a route. This means you can apply error-handling logic, compression, authentication for any middleware or responder downstream from /api without having to repeat yourself or introduce some higher-order function that eventually becomes the source of every heisenbug in your app. The benefit of defining routes this way can be seen in the blog-api example.
let mut api = app.at("/api");

// Apply specific error handling logic to the /api namespace.
api.include(ErrorBoundary::map(|mut error| {
    use diesel::result::Error as DieselError;

    if let Some(DieselError::NotFound) = error.source().downcast_ref() {
        // The error occurred because a record was not found in the
        // database, set the status to 404 Not Found.
        *error.status_mut() = StatusCode::NOT_FOUND;
    }

    // Return the error with the response format of JSON.
    error.json()
}));

api.at("/posts").scope(|posts| {
    use api::posts;

    posts.include(posts::authenticate);

    posts.respond(via::get(posts::index));
    posts.respond(via::post(posts::create));

    posts.at("/:id").scope(|post| {
        post.respond(via::get(posts::show));
        post.respond(via::patch(posts::update));
        post.respond(via::delete(posts::destroy));
    });
});

api.at("/users").scope(|users| {
    use api::users;

    users.respond(via::get(users::index));
    users.respond(via::post(users::create));

    users.at("/:id").scope(|user| {
        user.respond(via::get(users::show));
        user.respond(via::patch(users::update));
        user.respond(via::delete(users::destroy));
    });
});

Performance
Now that we've defined how we want the router to work, the next step was to build it and make it fast. The result of the time spent optimizing the router when I started this rewrite a month ago can be seen by running the benchmark in via-router on this branch. On my machine, it takes roughly 135ns per iteration to find all matching routes for a path with nested resources in a router with 100 routes. This is better than I anticipated and fast enough to allow for some compromises higher up in the stack.
Pragmatic Trade-Offs
We all have fought with the borrow checker and know how it feels after a long day of helpful yet despairing compiler errors. Often, the solution to these errors involves re-imagining and re-ordering the sequence of events in a function in a way that makes sense to a computer. This is an important part of being a Rust programmer. Nobody denies that. However, it's a hard conversation to have with your manager when you spend all day fighting the borrow checker, only to find
out that the implementation using borrowed data is slower than the version you initially wrote using Arc. It's also no secret that using borrows unnecessarily only makes it more difficult to onboard a Rust beginner. Still, this is a complex subject in the language, and we shouldn't hide the parts of Rust that one will inevitably have to use.
The Middle Ground
With via, I think it's important to find the intersection of performance and ease of use. Therefore, when it comes to data in a request, we treat performance requirements as a top priority. This means that when you work with path and query parameters from a via::Request, we return references (with the underlying type &str) that truly reference the data in the URL path. When you read the request body in a particular responder, the data is moved out of the request rather than copied to avoid wasting resources downstream. Above all, query parameters and other types of data related to a request (cookies, etc.) are always parsed and stored lazily so the query parser code does not run unless you actually use query parameters.
However, we don't want you to stay late at work unless you really, really want to. Therefore, we do some things that might be considered controversial by some in the Rust community (I'm half-joking here). We wrap middleware and responders added to a route in an Arc and use an owned reference to call the middleware when we unwind the stack because I like using the termination operator on line 1 of the function I'm writing. In all seriousness, I think it's important for productivity and onboarding to allow for request and next to move into the future returned from middleware. I believe the performance implications of doing so are acceptable for anyone comfortable using a framework rather than writing a hyper service from scratch for their next project. We also return a reference to an Arc of the global state returned from Request::state so you can clone it as much as you want and tell your boss that we told you to do it!
Unix-Like
When I initially started this four years ago, I wanted to provide a batteries-included option (similar to Django and Rails) but for Rust. However, I think it's important to support an ecosystem of libraries as unique as the community for which this framework was built. It's fun to write your own CORS middleware or static server, and we don't want to take that away from you. Via is meant to be a thin layer on top of hyper, giving you control over the important decisions. We'll provide a few "official" crates, such as via-serve-static introduced in this pull request, but we won't require you to use it or make it a part of our core API. Write your own if that makes you happy. That's what I told myself when I was looking at Rust web frameworks, and had I not done that, I would have been so bored last month. Competition is good for everyone, and I want to see if someone else will write an auth crate so I can deny culpability if need be. We'll also feature flag the stuff you expect, such as JSON support via serde, and never include default features.
** via-serve-static is very, very fast and secure, and is a great choice for serving static files, but you can still write your own if you want to.
Security
Rust allows us to write code that is verified to be correct at compile time. I believe it is our responsibility to uphold the guarantees advertised by the language and not introduce unsafe blocks for a slight or even substantial performance improvement. I'm okay with being second best (or even in the top 5) if that means it's easier for me to sleep at night. I know what it's like to be a victim, and I love that Rust prioritizes safety and security.
The only place you should see unsafe in the source code is for Pin projections, as I believe it is important for us to write our own pin projections to verify their correctness as a community.
Epilogue
Thank you for taking the time to read this description. I know test coverage can be improved, and that's a priority of mine, but I appreciate your time and effort in reviewing this substantial PR. If anyone can confirm the existence of and/or pinpoint the source of a small but potential memory leak, I promise you will be the first to receive a via t-shirt if this framework becomes popular. I welcome your constructive feedback and insights. Let's work together to make this project reach the potential that I believe it has!
You can find more traditional examples in this work-in-progress branch: https://github.com/zacharygolba/via/tree/refactor-simplified-examples/docs/examples.
Stay tuned as I plan on adding some issues for features that didn't make it into this pull request over the next week.

Edit: From what I can tell, the memory leak in via-router has been fixed. There may be improvements to be made with regards to memory management but memory usage should be stable at this point.

Short-Term and Medium-Term Roadmap
Blocking the first release:

[X] Refactor the Request type and Error struct to prevent the need to pass around a channel or EventListener. (d714bc7)
[X] Use a semaphore or some other mechanism to prevent the server from crashing if there are too many open file descriptors (2a6be5a)
[X] Support graceful shutdown. (a8be8de)
[X] Support TLS and HTTP/2. (#20)
[X] The ability to percent-decode path params. (#21)
[X] Cookies. (#22)
[ ] FlatMap.
[ ] Cleanup via-serve-static, rename it to via-fs, keep bitflags.

Nice to have for the first release:

[ ] Proxy middleware as an official crate (via-proxy).
[ ] Multipart support.
[ ] Tracing.
[ ] TLS via OpenSSL.
[ ] Async closure support.

Things to follow shortly after the first release:

[ ] An official crate for compression / decompression.
[ ] Auth. I'm thinking an official crate with traits and some common adapters (i.e basic, jwt, cookies, etc.).
[ ] A recipe book or official crate for integrating various templating engines.
[ ] Compatibility with other async runtimes (tokio is great but being able to chose is also great).
[ ] Either a basic built-in way of supporting websockets or an official crate with a slightly higher-level API. I don't want to re-invent elixir but it would be nice if we had a story for supporting realtime applications if need be.

575f518 is my way of saying that I'm sorry. It is a bit verbose, but I think it is a good starting point to ensure that the code in via-router does what it is supposed to do. I'm also hopeful that it inspires the community to further improve the performance of the router.

Considering the progress made in #11 and #9, here is short summary of what is preventing this PR from merging and the first version of Via from being released.

[] Refactor the Request type and Error struct to prevent the need to pass around a channel or EventListener.
[] Use a semaphore or some other mechanism to prevent the server from crashing if there are too many open file descriptors
[] Support graceful shutdown.
[] Support https and http2.
[] Cookies.

Things to follow shortly after the first release:

[] Tracing.
[] Multipart support.
[] An official crate for compression / decompression.
[] The ability to flat_map a request and response body (may be required for compression).
[] A recipe book or official crate for integrating various templating engines.
[] Either a basic built-in way of supporting websockets or an official crate with a slightly higher-level API. I don't want to re-invent elixir but it would be nice if we had a story for supporting realtime applications if need be.

If you want to try out Via and want to know what branch you should specify in your Cargo.toml, use refactor-app-service for now.

I'm considering refactoring the error module and replacing the custom type with an extension trait that works seamlessly with std::error::Error and also serde::Serialize if the json feature flag is enabled.

The FlatMap task could be a Fold. However, I like the idea of FlatMap since the input and output type would always be Bytes. We could borrow some of the logic in the implementation of Buffered to ensure that whatever is returned from the map fn will be flattened to 8KB chunks. I do like the idea of supporting local state for the map function similar to the accumulator argument passed to fold. In my opinion, that would allow the vast majority of use-cases to benefit from a statically-dispatched body. For all other use-cases, the http-body-util crate can be used in combination with AnyBody::Box(BoxBody). Once implemented, the AnyBody enum can be marked as non_exhuastive.


Create MFA State Check and see it working

If we would add a MfaState.php file in https://github.com/nextcloud/server/blob/master/apps/workflowengine/lib/Check/
and then also add a Vue template for it in https://github.com/nextcloud/server/tree/master/apps/workflowengine/src/components/Checks
then it should (we think) show up as an available condition for file access blocking in http://localhost:8080/index.php/settings/admin/workflow
Let's test if this works!

Done


Revert "Update to AGP 8.1.0 (#482)"

This reverts commit 58ccfc7266b4a0b7ac4b35bdae440acbd1f12b80.

Closing as we're fixing forward


Components z-index not following Carbon Design System

Detailed description

Describe in detail the issue you're having.
When using DataTable the batchActions header has z-index of 6000 which causes it to overlap the service header.

Is this issue related to a specific component?
Not necessarily - According to the layout map there might be other components that are not following the design system layout guidelines

What browser are you working in?
I'm using Chrome - but this will affect all browsers

What version of the Carbon Design System are you using?
V9

What offering/product do you work on? Any pressing ship or release dates we should be aware of?
I'm part of Certificate Manager team.

Hi @idohu! 👋 Thanks for reporting this. Would you want to try submitting a PR with the fix? Should just be updating one line in order to fix this 🙂

@joshblack can I take this over ?

@idohu its my first time trying to reproduce an issue here. can you please explain how one can reproduce it?

@idohu 👋 was this resolved, friend?

Closing this as it has been a few months without a response. If there is still a problem, feel free to reopen the issue with more steps to reproduce.


Register restart for resume

Related to: #3165
Changes:

This PR calls RegisterApplicationRestart to register winget to restart upon a reboot. The resume command and the resume id are passed as arguments to the winget process so that it can resume from where it left off prior to reboot.
Registering for a restart will only take place if the result of the installation is REBOOT_REQUIRED_FOR_INSTALL.
The checkpoint database will only persist if the result of the installation is REBOOT_REQUIRED_FOR_INSTALL.
Added a new settings value called maxResumes that limits the number of times a resume state can be "resumed". This is to ensure that continuous reboots don't occur.
In order for the process to be restarted, the reboot must be kicked off while the process is still running. The winget process cannot be terminated normally or else Windows Error Reporting will not initiate the restart. My workaround is to have the process sleep while the reboot process is kicked off.
Moved the InitiateReboot() flow to take place after --wait argument is processed so that the user is prompted to continue before a reboot is kicked off.

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service rerun


Fix crash when joystick name is unavailable

Fixes issue #694
I've been unable to test this locally (since I don't have any joysticks / controllers that don't report a name), but it's a pretty simple fix. This matches the behavior found in linux_joystick.c

Thank you!


Navbar component

Hello,
is it possible to add navbar component? How can I extend block elements?

@matteod
I have started the implementation for some missing elements of mjml 4 in a new branch at
https://github.com/larsdecker/grapesjs-mjml/tree/feature/newElements
It is not finished yet, but the basic structure is there. Maybe you can help us.

@matteod @larsdecker
Implemented it #109

https://github.com/artf/grapesjs-mjml/releases/tag/v0.1.8 released


How to pass the images in assests array to an api as post

Hi, I would like to pass the images to an api request as post.I know the images are stored in assets as a DKAsset Array but i dont know how to fetch whole image itself to the reguest. I want to pass the image name, type, size and image itself.
Thanks in advance.

Just iterate through array of DKAssets and fetch the image by using following method defined in DKAsset Class
public func fetchOriginalImage(_ sync: Bool, completeBlock: @escaping (_ image: UIImage?, _ info: [AnyHashable: Any]?) -> Void) {}
You can able to get the image name from info as shown in below
let url = info?["PHImageFileURLKey"] as? URL {
let imageName = url.lastPathComponent
DKAsset have a var isVideo: Bool
which is used to identify video, if the dkasset is not a video type, then it is image

Can you please explain a little bit more. My code is as below
` import UIKit
class CameraTabViewController: UIViewController,UICollectionViewDataSource,
UICollectionViewDelegate{
var pickerController: DKImagePickerController!

var assets: [DKAsset]?

        override func viewDidLoad() {
    super.viewDidLoad()

    // Do any additional setup after loading the view.

}

override func didReceiveMemoryWarning() {
    super.didReceiveMemoryWarning()
    // Dispose of any resources that can be recreated.
}

@IBAction func saveCamBtn(_ sender: Any) {
    let parent = self.parent as! DiaryEntryViewController
    parent.CameraView.isHidden  = true
}
@IBAction func selectPhotoBtn(_ sender: Any) {

    let pickerController = DKImagePickerController()
    pickerController.defaultSelectedAssets = self.assets

    pickerController.didCancel = { ()
        print("didCancel")
    }

    pickerController.didSelectAssets = { [unowned self] (assets: [DKAsset]) in
        self.updateAssets(assets: assets)
    }

    self.present(pickerController, animated: true)
}

@IBOutlet var previewView: UICollectionView!
func collectionView(_ collectionView: UICollectionView, numberOfItemsInSection section: Int) -> Int{

    return self.assets?.count ?? 0
}

func collectionView(_ collectionView: UICollectionView, cellForItemAt indexPath: IndexPath) -> UICollectionViewCell {

    let asset = self.assets![indexPath.row]
    var cell: UICollectionViewCell?
    var imageView: UIImageView?
    if asset.isVideo {
        cell = collectionView.dequeueReusableCell(withReuseIdentifier: "CellVideo", for: indexPath)
        imageView = cell?.contentView.viewWithTag(1) as? UIImageView
    } else {
        cell = collectionView.dequeueReusableCell(withReuseIdentifier: "CellImage", for: indexPath)
        imageView = cell?.contentView.viewWithTag(1) as? UIImageView
    }

    if let cell = cell, let imageView = imageView {
        let layout = collectionView.collectionViewLayout as! UICollectionViewFlowLayout
        let tag = indexPath.row + 1
        cell.tag = tag
        asset.fetchImageWithSize(layout.itemSize.toPixel(), completeBlock: { image, info in
            if cell.tag == tag {
                imageView.image = image
            }
        })
    }

    return cell!

}

func updateAssets(assets: [DKAsset]) {
    print("didSelectAssets")
    self.assets = assets
    self.previewView?.reloadData()

}

}
`

Looks like you selected image from picker and showing preview in collection view. Probably ,you have to create upload button and try to upload the images.
In your code,
func updateAssets(assets: [DKAsset]) returns array of assets
Here, you already know how to fetch the image and showing preview in collection view
asset.fetchImageWithSize(layout.itemSize.toPixel(), completeBlock: { image, info in
if cell.tag == tag {
imageView.image = image
}
You have to convert this image to Data by using UIImageJPEGRepresentation/UIImagePNGRepresentation API
Following links may help you...
https://mobikul.com/make-multipart-request-using-alamofire-3-0-swift/
https://medium.com/@hanifsgy/alamofire-multipart-with-parameters-upload-image-from-uiimagepickercontroller-swift-a4abada24ae

Hi,
Can you help me to get selected files as Data type. My code is working for images but I'm not sure how to work with video files.
This part is for presenting view for choosing files:
let pickerController = DKImagePickerController()         pickerController.sourceType = .photo         pickerController.didSelectAssets = { (assets: [DKAsset]) in             if assets.count > 0 {                 self.getImagesFromGalleryAndSend(assets)             }         }         self.present(pickerController, animated: true) {}
This part of code is to get image from selected files:
`func getImagesFromGalleryAndSend(_ images: [DKAsset]){
for item in images {
item.fetchOriginalImageWithCompleteBlock({ (image, info) in
    })
}

}`
What method should I use to get files as Data?


redesign/concept for probr analysis

merge session and loyalty, rename to utilization done
global filter for tags and daterange
heatmap becomes "location" -> either you filter via tags/daterange or mac address
devices beomces "stats" -> shorten the last day seen to 50 devices and xxx more done
packets becomes "log" done

See our wonderful sketches:

Renaming is done completely. URL parameters for all "use case"-views are done too.


Add Internet Format for ja_JP.

Unified Internet and Person format.
Because the internet class format is small and there are many duplications.

Thanks!


[1.11] Allow disabling tracing (#34217)

Fixes https://github.com/istio/istio/issues/34369

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.11
1eb34e89b66179b3e93c65f5bceef4fada011617
link
/test release-notes_istio_release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.11
1eb34e89b66179b3e93c65f5bceef4fada011617
link
/test release-notes_istio_release-1.11

integ-security-multicluster-tests_istio_release-1.11
1eb34e89b66179b3e93c65f5bceef4fada011617
link
/test integ-security-multicluster-tests_istio_release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@howardjohn is this something worth of release notes?

I just added one

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio_release-1.11
1eb34e89b66179b3e93c65f5bceef4fada011617
link
/test integ-security-multicluster-tests_istio_release-1.11

release-notes_istio_release-1.11
6b744e121d0b692ba896fadc9a86d901b88d6b71
link
/test release-notes_istio_release-1.11

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Missing Steps for GKE - “If you wish to use a static IP for Kong, you have to reserve a static IP address”

What part of the site needs attention?
totally ignored what needs to be done in pass a static IP to GKE => “If you wish to use a static IP for Kong, you have to reserve a static IP address”

Summary

Steps To Reproduce

Hi @eddadjei - we don't have enough information to make this actionable. If you'd like to contribute to improvements of our docs, please submit a PR with the changes you're expecting!


It does not work with typescript

It does not work with typescript because it does not have a @ types / react-bootstrap-maskedinput

Hi there -- I'm happy to accept a PR if you'd like to add types for the module. You can also declare types in your codebase for untyped npm modules.


Add name field to all example app configs

What this PR does / why we need it:
With it, those who try PipeCD using examples can register an app without manual input.
This PR also fixes places where use deprecated fields like triggerPaths.
Which issue(s) this PR fixes:
Ref https://github.com/pipe-cd/pipe/pull/2935#issuecomment-993399168
Does this PR introduce a user-facing change?:

NONE

🚀
/approve


Node 7

Can package.json add support for a node engine greater than 7?

Travis CI uses nvm to manage and make easier the management of NodeJS versions, as such 7 is an nvm alias for the latest NodeJS 7.x branch, currently that is 7.10.2 as can be seen here.

My bad - I thought I my install of Yarn had also added node 7, but apparently I'm still on 6.2.2, so the error message is correct.


i have update angularjs from 1.4.8 to 1.6.0 and get this error

i have update angularjs from 1.4.8 to 1.6.0 and get this error
``TypeError: a is not a function
at d (angular-animate.js:2132)
at angular-animate.js:2122
at I (angular-animate.js:3210)
at Array.fn (angular-animate.js:3058)
at c (angular-animate.js:403)
at b (angular-animate.js:373)
at Array. (angular-animate.js:3080)
at Scope.$digest (angular.js:17851)
at Scope.$apply (angular.js:18066)
at done (angular.js:12207)```

I'm submitting a ...

[ ] bug report
[ ] feature request
[ ] other (Please do not submit support requests here (see above))

Current behavior:

Expected / new behavior:

Minimal reproduction of the problem with instructions:

Angular version: 1.6.

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Anything else:

There's little information to know what's causing the issue. Please provide a reproduction.
Anyway, a wild guess: Are all your libraries being updated to 1.6.0? Or do you still have some 1.4.8?
Other than that, your issue reads like a support question. This github repo is only for bug reports and feature requests. Please try one of the listed Support Channels. Thanks!

yes i use the correct libraries ok  will try it to make reproduction soon

It also looks like some parts are minified, it might be a good idea to avoid minification when trying to interpret the stacktrace.

hmm i get this error TypeError: $$animateJs is not a function

As @frederikprijck said, it is impossible to tell what is wrong without a reproduction. In any case, this doesn't look like an issue in AngularJS. (Mismatched versions sounds like a possible cause indeed).
Also, make sure you read about the breaking changes introduced between 1.4 and 1.6 (Migration Guide, Changelog). Finally, the general support channels are a good place to get help with these types of problems.


pull request for e2e test at 11/25/2016 03:26:07

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


New-SelfSignedCertificate doesn't exist on windows

Type New-SelfSignedCertificate, we got
PS C:\Program Files\PowerShell\6.0.2> New-SelfSignedCertificate
New-SelfSignedCertificate : The term 'New-SelfSignedCertificate' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

New-SelfSignedCertificate

CategoryInfo          : ObjectNotFound: (New-SelfSignedCertificate:String) [], CommandNotFoundException
FullyQualifiedErrorId : CommandNotFoundException

At least it should work on windows 2016

New-SelfSignedCertificate is in PKI module. The module is outside the repository. You could send the request by UserVoice site.

"It's not our fault. You should blame another department"


removes last traces of apex etc from PL module

removes last traces of apex etc from PL module

Hello @williamFalcon! Thanks for updating this PR.

In the file pl_examples/basic_examples/autoencoder.py:

Line 105:15: W292 no newline at end of file

LGTM, much cleaner and the abstraction reduces code complexity.

horovod is failing to install... trying on another branch


replace call to print with logging.debug

quick fix for py3 compatibility :)

Wow.  That should have been a debug for other reasons too.  Thanks for catching.  Will approve and bump a new release Monday or Tuesday.

On Sep 6, 2015, at 3:07 PM, Martin Contento<EMAIL_ADDRESS>wrote:
quick fix for py3 compatibility :)
You can view, comment on, or merge this pull request online at:
https://github.com/jvanasco/pyramid_debugtoolbar_dogpile/pull/2
Commit Summary
replace call to print with logging.debug
File Changes
M pyramid_debugtoolbar_dogpile/init.py (2)
Patch Links:
https://github.com/jvanasco/pyramid_debugtoolbar_dogpile/pull/2.patch
https://github.com/jvanasco/pyramid_debugtoolbar_dogpile/pull/2.diff
—
Reply to this email directly or view it on GitHub.

Cool, thanks for getting a new version out quickly, I hate having -e git:/ lines in my requirements files :)
On another note: I tried to make the most minimal change possible here, but if you are interested I can follow it up with a PR that goes over the various pylint warnings in the project?

This is merged into the 0.0.5 tag and release on pypi (09/08/2015, 11:04am est)
what sort of warnings are you seeing in pylint that worry you?  this passes my flake8 checks -- though I have a handful of settings regarding line length and bracket formatting turned off.

thanks! :)
most of the warnings are about the single letter variable names i think (i'm in the non-python) office right now, can't check ;) but if you are not bothered -> let's not touch a running system :)


why SQLite4Unity3d exists link is broken

http://www.codecoding.com/sqlite4unity3d-using-sqlite-net-library-and-unity3d-free-edition/ is a broken link,
Im trying to find what the difference is between this repo and the original.

which one is the original one?

The website http://www.codecoding.com/ seems to be down. The last archived content of this link can be found here:
Archive.org

@AlexSchuetz, yes, the site is down. I decided to discontinue it. I'll move that docs to the new one when I have some time.

@robertohuertasm Or just include the content of that article in your readme ;)

You're totally right! 🤦🏻♂


Feature Request: Chrome DevTools pin

Welcome! Please use this template for reporting documentation issues on https://developers.google.com/web/.
For questions about Chrome DevTools, checkout the
google-chrome-devtools tag on StackOverflow.
For questions about Chrome, check the google-chrome
tag. If you think you've found a Chrome bug, check out our
feedback page for more details on how to file it.
Page Affected: https://developers.google.com/web/TODO
What needs to be done?
Please provide description of what's needs to be done here. Please be sure to include the link to the original page
and any supporting links/data.
Requesting
I would like a clickable sticky/pin/thumbtack within devtools so that I can easily toggle when new tabs have devtools pre-opened.
Reason
It is not possible to programmatically open devtools by design. I fully support the merits of this design choice, however, I believe the currently provided method of adding --auto-open-devtools-for-tabs to the command line to be too tedious on the end user.
I do understand the reasons for deciding to implement this feature in this way, however, I believe I may have a solution where we can meet in the middle offering both security and convenience. See the next section for how.
Adding and removing a command line flag while doing certain types of dev work can be tedious, particularly if you do not exclusively use the browser in question for development work. There is clear demand for such a feature as outlined both by the amount of questions like the one linked as well as the feature --auto-open-devtools-for-tabs existing at all.
More Nuanced Reason (improving debugger;)
I believe having this feature would greatly extend the value of the debugger; keyword, allowing users to rely upon breakpoints always breaking.
Today, using debugger; will not break unless chrome devtools are open which causes some fast approaching breakpoints to be missed entirely. That can mean that (particularly newer) devs will simply open devtools and trigger again, however, they may be unknowingly seeing the issue from a new context, not understanding why their code works when running the debugger but not when ran without it.
Implementation Idea
In order to maintain security but allow this functionality to exist, I have some implementation suggestions that I think may allow the desired behavior of keeping the user in complete control of when devtools are opened and closed along with improving the user experience. I will outline those suggestions here. I recommend using them as a catalyst for thought rather than taking me by my word and implementing exactly as suggested, though if I happen to have made such a robust a suggestion all the better.

Add a new command line flag --devtools-enable-pin
When the command line flag is supplied, add a pin button above the Dock side ellipsis menu item with the label "Automatically Open Devtools"
When enabled, all new tabs/windows come with devtools pre-opened
When not enabled, behavior resumes as usual
When command line flag not supplied, behavior resumes as usual (and option is absent or disabled in ellipsis menu)

Final Thoughts
I apologize if a similar implementation method has been suggested and I somehow missed it. I did do a reasonable amount of searching before posting. I hope this post is of the appropriate detail level. Please let me know if I need to update/improve this request I'll be happy to do that.

[ ] Appropriate type-something label has been added.
[ ] Appropriate section-something label has been added.

I'm now realizing I posted this here believing it to be the appropriate place for a chrome devtools feature/issue, but it appears to be focused on the documentation only. I got here via following the link in Thank you for the feedback. If you have specific ideas on how to improve this page, please create an issue. of the feedback section in Open Chrome DevTools.
I'm having trouble identifying the correct place to post, could someone help guide me? I will update/remove/close once I've found it.

Hey Chad, for FR's related to DevTools you can file them in our chromium repo: https://bugs.chromium.org/p/chromium/issues/entry?template=DevTools+issue


Cross link Create VM gallery doc to sample script

https://github.com/MicrosoftDocs/Virtualization-Documentation/tree/live/hyperv-tools/vmgallery
Add link to create gallery doc

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Use repr for pretty printing indices

Currently, except for the special case :, string is used to print indices. I think we should use repr instead, because:
julia> @varname(x[:a])
x[a]

julia> string(:a)
"a"

julia> repr(:a)
":a"

I think x[a] is a misrepresentation.
From the docs:

Note that repr(x) is usually similar to how the value of x would be entered in Julia.

Haha, I just noticed this yesterday too when noting the bug in the PR and meant to make a PR today replacing it with repr :sweat:


CKAN Versions support going forward

We are planning on significantly extending and improving the current features and for that we need to focus our efforts. New features are python3 dependent, so users will need to choose the right ckanext-validation version depending on their CKAN version, with the goal that eventually everybody will be using CKAN 2.9+ on Python 3.

[x] ckanext-validation 0.0.8 supports CKAN <= 2.8
[x] ckanext-validation 1.0.0 will support CKAN 2.8 and 2.9 (py2 and py3). This is almost done in https://github.com/frictionlessdata/ckanext-validation/pull/55
[ ] ckanext-validation 2.0.0 will support CKAN >= 2.9 with Python 3 support only. Here's where we will do the planned work, including replacing goodtables with frictionless-py, which is Python 3 only

Once #55 is done I'll release the new version and update the README with these guidelines
cc @aivuk @ThrawnCA
edit: added support for CKAN 2.8 in 1.0.0

Are you sure it's really that difficult to keep supporting multiple versions? We're already doing it in the qld-gov-au fork and it doesn't seem to be all that hard.

ooookay ookay, we'll include support for 2.8 in 1.0.0 :)
Personally I think compatibility hacks like the ones to support calls to Flask or Pylons test apps make the test harder to read (and extend!) but we'll make an effort to keep up with the core support policy

I like the idea of a version that supports all CKAN versions. It means you can update components one at a time, instead of having to simultaneously update CKAN and the plugin.

This extension is only now becoming compatible with newer CKAN+Python. CKAN 2.9 has been out for a while, 2.8 hasn't been accepting pull requests except serious bug fixes, but if the plugins aren't compatible, how can end users upgrade? Dropping 2.8 compatibility when people haven't even had the chance to properly try out 2.9 yet is too quick. There needs to be a transition period.
We recently updated to CKAN 2.9, but we had to update a bunch of extensions ourselves in order to make it work, and we're still dealing with a lot of bugs in the fallout, things that were overlooked in different extensions, etc. It's nice that the upstream for different plugins is now being updated, but it would have been nicer if that happened before people were being pushed to drop 2.8.

This extension is only now becoming compatible with newer CKAN+Python. CKAN 2.9 has been out for a while, 2.8 hasn't been accepting pull requests except serious bug fixes, but if the plugins aren't compatible, how can end users upgrade? Dropping 2.8 compatibility when people haven't even had the chance to properly try out 2.9 yet is too quick. There needs to be a transition period.

We (CKAN team) make an effort before a new CKAN version is released to upgrade the officially supported extensions (this was done for 2.9 and it is being done for 2.10). Of course we can not cover every single extension out there, specially others maintained by other organizations. In this case, we (OKF) just didn't have the time or resources to update this particular extension until now (or previously, when I started #55 but other priorities came in). To the question of how can end users upgrade in this situation I'd say that one way to help is to contribute as many compatibility fixes as possible to the upstream repos to help bring up extensions up to speed.

We recently updated to CKAN 2.9 because of the lack of support for 2.8, but we had to update a bunch of extensions ourselves in order to make it work, and we're still dealing with a lot of bugs in the fallout, things that were overlooked in different extensions, etc.

As I said, support for 2.9 has been in place for a while in most official extensions. If there are bugs or things overlooked in the migration again the best thing to do is to send the patch upstream (which I'm aware you do in many cases). CKAN is mostly run by volunteers and the community.

It's nice that the upstream for different plugins is now being updated, but it would have been nicer if that happened before people were being pushed to drop 2.8.

Again, we'd love to keep all things always up to date but that's just not possible. Users are encouraged to drop 2.8 (released on 2018, 4 years ago) because there are more modern versions that are safer and the CKAN team can actually maintain, that's just how open source software works. It's unfortunate that this particular extension could not keep up with the core release cycle for a while but hopefully it will from now on.

Hi @amercader,
Per ckan supported versions documentations.
At any one time, the CKAN Tech Team will support the latest patch release of the last released minor version plus the last patch release of the previous minor version.
2.9.x is the latest offical release at this time, as such 2.8.x still needs to be supported. Once 2.10.x drops, then you could possibly drop py2 support at that time also.  Though when things like https://github.com/ckan/ckan/issues/7095 happen. It does not seem like 2.10 is yet viable.

I came here after looking at the Compatibility table in README.md and looking for support for current CKAN version: 2.11. Just making sure that 2.11 as stated there is unsupported as it sounds somehow contradictory to this sentence:

ckanext-validation 2.0.0 will support CKAN >= 2.9 with Python 3 support only. Here's where we will do the planned work, including replacing goodtables with frictionless-py, which is Python 3 only

It is slightly confusing wording, particularly the use of >=, but I'm pretty sure it was never intended to mean "Version 2.0.0 will support every future CKAN version." More likely it's: "Version 2.0.0 will support CKAN 2.9, and will possibly work on later versions depending on what they change."

Hi @rantoniuk,
Per @ThrawnCA, 2.10 is fully supported on the qld-gov-au branch, this upstream repo has recently been transferred to the CKAN org and the qld-gov-au maintainers have been granted access to continue to improve it.
2.10 + 2.11 for this upstream repo is coming soon. You can see the progress here: https://github.com/ckan/ckanext-validation/actions/runs/12346855699
The qld-gov-au maintainer group is working on this but sadly the code bases between the two forks has drifted and needs heaps more TLC then we previously thought. The readme also needs updating, currently I've put in what is 'currently' supported by this repo after it was moved.
With all the improvements now getting done on this repo version including auto pypi version releases, the qld-gov-au fork should only be requiredfor alpha testing or feature enhancements our business folk request in the near future.

2.11's biggest hurdle atm is correcting db startup for this plugin as in 2.11 it now throws
sqlalchemy.exc.UnboundExecutionError: Table object 'validation' is not bound to an Engine or Connection.  Execution can not proceed without a database to execute against. before we even get to testing.

2.11's biggest hurdle atm is correcting db startup for this plugin as in 2.11 it now throws
sqlalchemy.exc.UnboundExecutionError: Table object 'validation' is not bound to an Engine or Connection.  Execution can not proceed without a database to execute against. before we even get to testing.

Yep, that's exactly where I got after adding the plugin in my dockerized instance via:
RUN  pip3 install -e<EMAIL_ADDRESS>&& \
     pip3 install -r https://raw.githubusercontent.com/ckan/ckanext-validation/2.2.0/requirements.txt

on a 2.11 setup, just to see if it works. Took me a while to decipher that the paster validation init-db -c ../path/to/ini/file should have been replaced by ckan, but then... I guess there is a chicken-egg problem

validation cannot be added to the list of loaded plugins because the tables were not created for it
tables cannot be created, because the plugin is not loaded, so ckan validation init-db cannot be run

Am I guessing correctly?

@ThrawnCA  suggest i look into ckanext-datarequests as he fixed it up for 2.11
I'll get to that after incorporating the  keitaroinc/ckan-2.10 pr.


Fix duplicate database variable in the production vars

database key was created twice, so only the second dictionary
was kept.

What does the snapshot_id here do? Seems like a very old one?

But :+1:  for the code fix otherwise.

@TheDoubleK "snapshot_id" is the only way we found to do DB restores/rollbacks in the future. By setting snapshot_id from the start we can change it to a newer snapshot to replace the DB if we need to. We can't remove it since this will trigger a database replacement.


Does TrustWallet support cosmos_signDirect for WalletConnect

Seems Trustwallet does but no doc on the data types like here in WC docs
https://docs.reown.com/advanced/multichain/rpc-reference/cosmos-rpc#cosmos_signdirect
bodyBytes and authInfoBytes are both encoded in base64, does TrustWallet require base64, hex or raw bytes in json?

Hi @borngraced, bodyBytes and authInfoBytes both are raw bytes as declared in Cosmos.proto:
https://github.com/trustwallet/wallet-core/blob/7523c9805ce094639dfbda6d643e439f5ef1705e/src/proto/Cosmos.proto#L240-L246
You can always check doc comments in the Protobuf files

@satoshiotomakan, sorry I'm reopening this issue.
I want to confirm if this is the expected json def trustwallet is expecting according to your proto defs and since I'm still encountering failed to sign message
json!({
           "signingMode": "Protobuf",
           "accountNumber": sign_doc.account_number.to_string(),
           "chainId": sign_doc.chain_id,
            "messages": [
             {
               "signDirectMessage": {
                   "bodyBytes": sign_doc.body_bytes,
                    "authInfoBytes": sign_doc.auth_info_bytes
                  }
             }
         ]
})


Put in place analytics for the demo site

Description
We would like to know more precisely which pages / frameworks are more visited in the site.

For 1.0, we will use Google Analytics.


Error With Running the samples

I recently pulled Nvidiai Docker container for tensorrt inference engine and Ran Simple_Client.py example
without any change but Inference Engine returns this error which I have not been able to get an insight why it is complaining about . The Error Message is as follow : "nvidia.inferencserver.InferRequestHeader.Input" has no field named "dims" . I checked the message sent by client and it looked fine . I ran both client and engine on same machine and aslo tried to run the engine on another machine but got the same error .
I appreciate if you know what is going on .
with grpc protocol I had another error and it didn't work as well .
The grpc_image_client.py sample also throws an error: ( if I remeber correctly it was compalining about input size 0 )
python grpc_image_client.py -m resnet50_netdef ~/tensorrt-inference-server/qa/images/mug.jpg
Request 0, batch size 1
Traceback (most recent call last):
File "grpc_image_client.py", line 325, in
postprocess(response.meta_data.output, result_filenames[idx], FLAGS.batch_size)
File "grpc_image_client.py", line 188, in postprocess
raise Exception("expected 1 result, got {}".format(len(results)))
Exception: expected 1 result, got 0

I assume the docker container is not compatible with the master branch ! Docker Container 19.01-py3 . I am going to pull the right branch with github and will give it a try , it should fix the problem

building the right branch from github fixed the issue as expected . closing the ticket


[CARBONDATA-3133] Update the document to add spark 2.3.2 and datamap mv compiling method.

Update the document to add spark 2.3.2 and datamap mv compiling method.
Update file:
https://github.com/apache/carbondata/tree/master/build/README.md
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[x] Any interfaces changed?
No

[x] Any backward compatibility impacted?
No

[x] Document update required?
Yes

[x] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.
No

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1545/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9805/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1757/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/1548/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1760/

Build Success with Spark 2.3.1, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/9808/

LGTM

LGTM

LGTM

Merged. Thanks for  your contribution 👍