Favicon of web interface missing

The web interface currently does not serve a favicon. This lets e.g. Firefox display its own icon, which can lead to misunderstandings.
One can produce a simple logo(type) and render it as a favicon, or do it the other way round and let the favicon generator create a logo.

The https://www.faviator.xyz/playground (https://github.com/faviator/faviator) gives me some examples with these settings:
{
  "size": 256,
  "text": "bp",
  "dx": 4,
  "dy": 4,
  "fontSize": 91,
  "fontFamily": "PT Sans",
  "fontColor": "#000",
  "backgroundColor": "#eee",
  "borderWidth": 0,
  "borderColor": "#fff",
  "borderRadius": 50
}

As PNG this renders into .

A manually edited SVG
<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
<svg xmlns="http://www.w3.org/2000/svg" width="256" height="256" viewBox="0 0 100 100">
  <defs>
    <style type="text/css">
      @import url('https://fonts.googleapis.com/css?family=PT+Sans');
    </style>
  </defs>

<rect x="0"
  y="0"
  rx="50"
  ry="50"
  width="100"
  height="100"
  fill="#eee"></rect>

<text x="50"
  y="78"
  dx="3"
  dy="4"
  fill="#000"
  font-size="92"
  font-family="PT Sans"
  font-weight=""
  text-anchor="middle"
  dominant-baseline="central">bp</text>

<rect x="0"
  y="0"
  rx="50"
  ry="50"
  width="100"
  height="100"
  fill-opacity="0"
  stroke="#fff"
  stroke-width="0"></rect>
</svg>

Settings JSON
{
  "size": 256,
  "text": "bp",
  "dx": 4,
  "dy": 4,
  "fontSize": 91,
  "fontFamily": "PT Sans",
  "fontColor": "#000",
  "backgroundColor": "#eee",
  "borderWidth": 0,
  "borderColor": "#fff",
  "borderRadius": 50
}

There is actually already a logo, but it wasn't being properly embedded in the executable during the build process. Should be fixed on the demo instance now and will go into the next release.

Also curious what your thoughts are on the current logo vs this other idea I had: https://github.com/boringproxy/boringproxy/blob/00978992893eb3a4c28ec303b302b8ccac990999/logo_concept.svg

It may actually make sense to have a different logo for the project and the web UI itself. I'd lean towards keep it simple and leave them the same, but not sure.

That logo is lovely. No need to duplicate efforts here, I think.
On Wed, 4 Nov 2020 at 17:35, Anders Pitman<EMAIL_ADDRESS>wrote:

It may actually make sense to have a different logo for the project and
the web UI itself. I'd lean towards keep it simple and leave them the same,
but not sure.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/boringproxy/boringproxy/issues/11#issuecomment-721838989,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMRV7EHUJ556XSXU7SHJSTSOF7FDANCNFSM4TKAPWCA
.


dimensionName field of ScaledObject is documented as optional but seems to be required

Report
According to https://keda.sh/docs/2.7/scalers/aws-cloudwatch/, the dimensionName field should be optional.
The metric for scaling has no dimensions:

However, after applying the below resource definition,
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: redash-rq-worker
spec:
  scaleTargetRef:
        apiVersion: apps/v1
        kind: Deployment
        name: redash-rq-worker
  minReplicaCount: 1
  maxReplicaCount: 4
  triggers:
  - type: aws-cloudwatch
    metadata:
      namespace: Redash/Workers
      metricName: BUSY
      metricCollectionTime: "300" # the default
      metricStat: "Average" # the default
      metricStatPeriod: "30"
      metricUnit: ""
      targetMetricValue: "4"
      awsRegion: us-east-1
      identityOwner: operator

Expected Behavior
The ScaledObject should be ready for scaling with dimensionName omitted in the manifest.
Actual Behavior
After kubectl apply of the above manifest,
kubectl describe ScaledObject redash-rq-worker gives:
  Warning  ScaledObjectCheckFailed  13s (x12 over 24s)  keda-operator  Failed to ensure HPA is correctly created for ScaledObject
  Warning  KEDAScalerFailed         3s (x13 over 24s)   keda-operator  error parsing cloudwatch metadata: dimension name not given

Steps to Reproduce the Problem

Install KEDA 2.7.1
kubectl apply the manifest given above
kubectl describe ScaledObject redash-rq-worker

Logs from KEDA operator
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:114
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:311
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.11.2/pkg/internal/controller/controller.go:227
1.6539913265347884e+09	ERROR	controller.scaledobject	Reconciler error	{"reconciler group": "keda.sh", "reconciler kind": "ScaledObject", "name": "redash-rq-worker", "namespace": "default", "error": "error parsing cloudwatch metadata: dimension name not given"}

KEDA Version
2.7.1
Kubernetes Version
1.21
Platform
Amazon Web Services
Scaler Details
AWS CloudWatch
Anything else?
No response

hey,
I have checked the docs and dimensionName is only optional using expression
.
TBH, I don't know if this makes sense or not. @JonasMatos0 r @dekelev could know more due they have worked on things related inside the scaler

Thanks for the response JorTurFer.
When I was going through the docs, I did not go all the way into the detailed field explanations it seems, so must have missed this. So, not a bug.


inputClass is not working

I am pretty new to Vue JS so i may be doing this wrong, but it looks like that the inputClass option is nog working. My code is looking like this:
<autocomplete-vue
        inputClass="form-control"
        :list="[{name: 'item1'}, {name: 'item2'}, {name: 'item3'}]"
        placeholder="Autocomplete"
></autocomplete-vue>

But this does not set the class on the input element:

You have to write it as input-class (kebab-case) if it is not in a vue-component.


generator to read pipelines from the flowmanager db.

Currently, we are using SourceSpecRegistry to read from DB what pipelines need to be run.  Since we extracted planning part of assembling and changed the flow management,  SourceSpecRegistry is not useful anymore.
Acceptance Criteria

[x] generator reads from new db and runs pipelines accordingly

Tasks

[x] use FlowManager as dependency and query the DB
[x] integrate with BB tests

FIXED


Merge pull request #1 from Moya/master

20150520

Codecov Report

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

@@            Coverage Diff             @@
##           master    #1132      +/-   ##
==========================================
- Coverage   76.51%   73.79%   -2.72%
==========================================
  Files          22       22
  Lines         728      729       +1
==========================================
- Hits          557      538      -19
- Misses        171      191      +20

Impacted Files
Coverage Δ

Sources/RxMoya/RxMoyaProvider.swift
42.1% <0%> (-52.49%)
:arrow_down:

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 5f7c8f6...ef0eb93. Read the comment docs.

Hey @leo-lp, I'm assuming this is a mistake-PR so I'm gonna close it. If it's not, please describe what was your intention here and we will work things out 👍


Please give credit in the README if you use any of my code.

^

alright... doing that now.

Thank! 😸


Add support for signal sensing on analog audio inputs

This PR adds audio sensing for the analog RCA inputs (red & white jacks).

This PR adds audio sensing for the analog RCA inputs (red & white jacks).

Hello, I am new to this. I have my TV connected to the optical and a sound system to the Analog. It would be great if cinesense could turn on Bose when it senses signals on either input. Did you manage to make the enhancement? I have all of the components and ready to start soldering, so before I start, I wanted to check if Analog is now available. THX, this is amazing by the way.

Hi! Thanks. This PR is not done yet. There are some circuit changes
required as well as software modifications. No support for analog inputs is
provided yet. You can subscribe to updates from this PR is you would like
to be kept up to date.
On Sat, Oct 29, 2022 at 1:55 PM fndo63 @.***> wrote:

This PR adds audio sensing for the analog RCA inputs (red & white jacks).
Hello, I am new to this. I have my TV connected to the optical and a sound
system to the Analog. It would be great if cinesense could turn on Bose
when it senses signals on either input. Did you manage to make the
enhancement? I have all of the components and ready to start soldering, so
before I start, I wanted to check if Analog is now available. THX, this is
amazing by the way.
—
Reply to this email directly, view it on GitHub
https://github.com/jaytavares/cinesense/pull/5#issuecomment-1295918303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFNTV4GLNHDPJVLXZSH3FDWFVQHRANCNFSM5W2X4JCQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Sent from my iPhone

FNDO> Hi, thanks for the quick response and thank you for the detailed project, I build it and it works great!!
One favor, I use the analog inputs for my stereo system, the logic in the Cinesense shuts off the Bose when there is not signal in the optical.
When I turn the Bose to listen to music, the Cinesense shuts the Bose right away because the optical is off (connected to the TV), so I cannot listen to music on my Bose unless I remove the Cinesense.

Could you tell me if there is a parameter, constant or a subroutine I can remove from the program to stop Cinesnse from shutting the Bose off?
Best Regards,
Fernando

From: Jay Tavares @.>
Sent: Saturday, October 29, 2022 3:42 PM
To: jaytavares/cinesense @.>
Cc: fndo63 @.>; Comment @.>
Subject: Re: [jaytavares/cinesense] Add support for signal sensing on analog audio inputs (PR #5)
Hi! Thanks. This PR is not done yet. There are some circuit changes
required as well as software modifications. No support for analog inputs is
provided yet. You can subscribe to updates from this PR is you would like
to be kept up to date.
On Sat, Oct 29, 2022 at 1:55 PM fndo63 @.***> wrote:

This PR adds audio sensing for the analog RCA inputs (red & white jacks).
Hello, I am new to this. I have my TV connected to the optical and a sound
system to the Analog. It would be great if cinesense could turn on Bose
when it senses signals on either input. Did you manage to make the
enhancement? I have all of the components and ready to start soldering, so
before I start, I wanted to check if Analog is now available. THX, this is
amazing by the way.
—
Reply to this email directly, view it on GitHub
https://github.com/jaytavares/cinesense/pull/5#issuecomment-1295918303,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFNTV4GLNHDPJVLXZSH3FDWFVQHRANCNFSM5W2X4JCQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Sent from my iPhone
—
Reply to this email directly, view it on GitHubhttps://github.com/jaytavares/cinesense/pull/5#issuecomment-1295951293, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A34NUPHVEF2TZZ6RJRFOYXDWFV42VANCNFSM5W2X4JCQ.
You are receiving this because you commented.Message ID: @.***>

Have a look at the code here: https://github.com/jaytavares/cinesense/blob/master/src/AudioSense.cpp
You can simply remove the auto-off code that starts at line 129. Bear in mind, the speakers will still turn off after approximately 30 minutes as they normally do.

Fndo> Hi, I just commented out the off command and it appears to be working. Thanks so much. This is a good little older Bose system, this enhancement extends its lifespan.
Regards,
Fernando Montenegro
Sent from my mobile device
Please excuse typos
On Nov 1, 2022, at 10:44 AM, Jay Tavares @.***> wrote:

Have a look at the code here: https://github.com/jaytavares/cinesense/blob/master/src/AudioSense.cpp
You can simply remove the auto-off code that starts at line 129. Bear in mind, the speakers will still turn off after approximately 30 minutes as they normally do.
—
Reply to this email directly, view it on GitHubhttps://github.com/jaytavares/cinesense/pull/5#issuecomment-1298613008, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A34NUPF2NE74FTLKH7JI3DTWGEUFRANCNFSM5W2X4JCQ.
You are receiving this because you commented.Message ID: @.***>


Docker

Include the tool in a docker container

This is going to be interesting -- I have no idea how we will trigger Dask with Slurm from inside a container. I would at this point label this as low-priority but with lots of learning potential.


Update

close #11

Coverage remained the same at 100.0% when pulling d88dd59308c218ee413083f498a81f311aad2b6d on update into c3c5dad0fe4be7a1eca23f02ebcccfc13acad8ba on master.


nftables module: Add new module for nftables firewall settings

Motivation for this change
This adds a simple service for setting up firewall rules using nftables instead of iptables. It includes a few examples, and it allows you to specify files so they can be generated from scripts.
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

If you have ideas for a better interface, I'd be happy to listen. I use rulesetFile, but it would be annoying to have to do pkgs.writeText if you're just writing inline rules. The wants change is a good idea.
I use this personally, but if it's not useful for NixOS I'm happy to close the PR

Actually the wants change isn't a good idea. This module does the same as firewall.

Then the firewall module is broken too...
About network-pre.target source:

It's a passive unit: you cannot start it directly and it is not pulled in by the the network management service, but by the service that wants to run before it. [...] Services that want to be run before the network is configured should place Before=network-pre.target and also set Wants=network-pre.target to pull it in.

Yeah, I guess I'll fix it here then. The nftables module isn't intended to replace the firewall, but it is incompatible with the firewall. nftables itself is probably a little too early to go all out on, but it's nice to have for now as a module with some examples.

Fixed?

Fixed?

I think we need some wantedBy.. Maybe basic.target?

Added wantedBy = multi-user.target, this is how another firewall package does it.

My 2¢ as someone who manages many complex Linux firewalls, and in the process of switching some of them to NixOS.
I would like to have an abstraction layer over tables, chains and rules, so I can split my firewall configuration over multiple Nix files, eg. have a vpn.nix define a VPN connection and add some iptables/nftables rules to the relevant chains. Then the NixOS module system would merge all the rules and chains and generate a single text file as input for iptables-restore/nftables, so the ruleset can be loaded atomically.
An example of what I'm thinking about:
networking.firewall = {
  ipRules = {

    filter.INPUT = [
      { inputInterface = "eth2"; chain = "dmz"; }
    ];

    filter.dmz = [
      { proto = "tcp"; destinationPort = [ 80 443 ]; target = "ACCEPT"; } # expands to 2 iptables rules
      { allowedTCPPorts = [ 80 443 ]; }  # shortcut for the rule above
    ];

    nat.POSTROUTING = [
      { source = "<IP_ADDRESS>/24"; outputInterface = "eth1"; target = "SNAT"; targetArgs = "--to <IP_ADDRESS>"; }
    ];

    mangle.PREROUTING = [
      { source = "<IP_ADDRESS>/24"; inputInterface = "eth0"; mark = "0"; target = "MARK"; targetArgs = "--set-mark 0x20"; }
    ];
  };

  ip6Rules = {
    # ...
  };
};

The proposal in #12940 would be a step in the right direction for iptables IMO.
However, nftables has a much more expressive language than iptables, and abstracting all its features with Nix would be way overkill.
So let's thin the abstraction and generate the rulesets from text fragments; it would be simpler to implement as a module, and still be nice to the firewall builder.
Something like this:
networking.firewall.iptablesRules = {

  filter.INPUT = [
    "-i eth2 -j dmz"
  ];

  filter.dmz = [
    "-p tcp --dport 80 -j ACCEPT"
    "-p tcp --dport 443 -j ACCEPT"
  ];

};

Or, for nftables:
networking.firewall.nftables = {

  sets.private = ''
    { <IP_ADDRESS>/16, <IP_ADDRESS>/8 }
  '';

  ipRules.filter.input = ''
    ip saddr @private log drop
    iif eth2 jump dmz
  '';

  ipRules.filter.dmz = ''
    tcp dport { 80, 443 } accept
  '';

  ip6Rules.filter.input = "...";

};

The existing allowedTCPPorts options would generate rules like these so we can keep backwards compatibility and a simple option for basic firewalls.
Let me know what you think.

Should this be renamed to something like nftables-raw then?

Something I do with my nftables ruleset files is to put flush ruleset at the top of the file, so I can always just re-run nft on that file and it will automatically flush + reload all rules. I find this nicer than doing it explicitly in ExecReload.

On Fri, Sep 23, 2016 at 06:15:14PM -0700, Aneesh Agrawal wrote:

Something I do with my nftables ruleset files is to put flush ruleset at the
top of the file, so I can always just re-run nft on that file and it will
automatically flush + reload all rules. I find this nicer than doing it
explicitly in ExecReload.

Having it twice doesn't hurt, and having it in ExecReload allows it to ensure
that things are loaded atomically. However, I'm open to changing this given that
it's hard to use the rules outside of nft reliably.
Would it be better to update documentation to include "flush ruleset" and also
provide a way to avoid the automatic flushing in cases people don't want that?
Perhaps rulesetFile could not include it.

I can't imagine a scenario where you wouldn't want atomic flushing. IMO, always automatically adding flush ruleset to the top of the file is the simplest and thus best solution - no special ExecReload rule, impossible to forget it using nft, don't need to document how to enable it because it's always on.
If there is a good reason not to use atomic flushing, I would like to hear about it.

On Fri, Sep 23, 2016 at 08:48:13PM -0700, Aneesh Agrawal wrote:

I can't imagine a scenario where you wouldn't want atomic flushing. IMO,
always automatically adding flush ruleset to the top of the file is the
simplest and thus best solution - no special ExecReload rule, impossible to
forget it using nft, don't need to document how to enable it because it's
always on.

What's the difference between adding it at build-time versus runtime?

If there is a good reason not to use atomic flushing, I would like to hear
about it.

Load fast crash hard?

@aneeshusa even is ExecStart is atomic, one still want to have an ExecReload, because there otherwise it will leave the system unprotected for a short amount of time between ExecStop and ExecStart on restart.

@grahamc security

Thanks!

@Mic92 Why did you merge this without any regard to #23181? (Don't want to flame her but I'm honestly a bit upset...)
A also see multiple issues with this PR (not that familiar with nftables though, so I might be wrong...). I'll probably post some comments anyway.

@primeos I saw your rfc, but I thought this pull request orthogonal. A generic firewall can still apply its rules using this module. Also my guess was that it would also take some time, while this module is already useful.

How about leaving it ruleset null at the moment by default and moving default to example? Then user can set rules as they like.

Also my guess was that it would also take some time, while this module is already useful.

Agreed, I just hope we don't have to make any changes later that could break many setups.

How about leaving it ruleset null at the moment by default and moving default to example? Then user can set rules as they like.

Would probably be a good idea. Generally that obviously wouldn't be desirable but it would hopefully prevent SSH breakage (e.g. with services.openssh.ports).
But we should probably at least keep "# Check out https://wiki.nftables.org/ for better documentation." and fix the "# Allow anything in." comment.

I saw your rfc, but I thought this pull request orthogonal.

It probably is but I initially feared this would cause too many problems later.

Suggestion for the example:
          # Table for both IPv4 and IPv6.
          table inet filter {
            # Block all IPv4/IPv6 input traffic except SSH.
            chain input {
              type filter hook input priority 0;

              # accept any localhost traffic
              iifname lo accept

              # accept traffic originated from us
              ct state {established, related} accept

              # accept neighbour discovery otherwise IPv6 connectivity breaks
              ip6 nexthdr icmpv6 icmpv6 type { nd-neighbor-solicit, echo-request, nd-router-advert, nd-neighbor-advert } accept

              # accept SSH connections (required for a server)
              tcp dport 22 accept

              # count and drop any other traffic
              counter drop
            }

            # Allow anything out.
            chain output {
              type filter hook output priority 0;

              oifname lo accept

              accept
            }

            chain forward {
              type filter hook forward priority 0;

              accept
            }
          }

A potential fix (from the Arch-Wiki) for the ICMP packets (but they might already be covered by the conntrack state related):
# ICMP
# routers may also want: mld-listener-query, nd-router-solicit
ip6 nexthdr icmpv6 icmpv6 type { destination-unreachable, packet-too-big, time-exceeded, parameter-problem, nd-router-advert, nd-neighbor-solicit, nd-neighbor-advert } accept
ip protocol icmp icmp type { destination-unreachable, router-advertisement, time-exceeded, parameter-problem } accept

I'd probably add fragmentation-required for ICMP(v4) as well (just to be extra save - but since it's only an example it probably doesn't really matter anyway). And sorry for the delayed update... :o (doesn't really matter if it's too late).

changed in 6c36d9fa208ac1b03966e4349f4850b2ec4301be

@Mic92 Great, thanks :smile:


Action bar not switching

tDF 2.1.3
When I use "Stealth" main action bar are not switch for another "stance"

Unfortunately, I don't see a way around this. The "MainActionBar" art never moves and the buttons are set to overlay on top of it. Essentially, the Stealth bar is under that, which you can't see. Hope this makes sense.

It works, the Stealth bar is just invisible. You can move the abilities you want to that top row, go stealth, then move them into your stealth bar.

Added this to the Known issues list for future reference.


Current Frame: POST route for adding a new window to the window table and getting its ID

Okay so - I was stupid, and tried something different (feature branch on my fork, merge to my fork, then PR to remote/origin). I think that flow could work as things become more complicated (potentially - I don't think this had any negative impacts but tbd. I also don't know if this will auto-resolve the GH issue - will check).

Fixed the merge conflict (in the base server file).

 I think that flow could work as things become more complicated (potentially - I don't think this had any negative impacts but tbd. I also don't know if this will auto-resolve the GH issue - will check).

That works fine too! You just need to select which branch you want to PR from. So you could have done your PR directly from steve-shumaker:fb-window-post to avcopan:main.
If you want to go this route, you can actually create a branch directly from the issue (bottom right on the issue page). Just make sure your origin main is up to date before you do that, because that's what it will branch from.


Onboard Schema Registry service

Schema Registry is a new service that is currently in private preview.
This issue is to track work to onboard the SDK for this service.
This work is planned for the August milestone and does not involve shipping the package which will be done in the September milestone.

decide package name
auto generate the package using the latest v6 code generator on the swagger
set up CI

For reference, please see the Java SDK for Schema Registry

Please wait until the swagger makes it to the https://github.com/Azure/azure-rest-api-specs/ repo. I'll post an update here when it does

decide package name

@ramya-rao-a  Is there a formal process for approving a name? Should we pick an interim name pending a review? @azure/schema-registry?

Please wait until the swagger makes it to the https://github.com/Azure/azure-rest-api-specs/ repo

I checked with Arthur about this and he will be looking at this soon.

@azure/schema-registry sounds perfect. @bterlson, do we have your blessing?

The current swagger caused a problem for the generator, sent https://github.com/Azure/autorest.typescript/pull/705 to fix it

+1 for @azure/schema-registry.

https://github.com/Azure/azure-rest-api-specs/pull/10220 is the link to the PR adding the swagger to the rest-api-specs repo. Please retry the generation and see if there are any other issues now that the upstream bug with the code generator is fixed

Generation succeeds on https://github.com/Azure/azure-rest-api-specs/commit/1296087cd0050d62dce3292b1d0d2eab2e7729b9 (latest commit in PR at this time). :)

If you have not started yet, please do use the template folder in the repo. We'd like to hear what works and what doesn't when using the template as a reference to add a new package to the repo

Ok. I will use the template folder 📂
Get Outlook for iOShttps://aka.ms/o0ukef

From: Ramya Rao<EMAIL_ADDRESS>Sent: Tuesday, July 28, 2020 7:33:26 PM
To: Azure/azure-sdk-for-js<EMAIL_ADDRESS>Cc: Sarangan Rajamanickam<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [Azure/azure-sdk-for-js] Onboard Schema Registry service (#10076)
If you have not started yet, please do use the template folder in the repo. We'd like to hear what works and what doesn't when using the template as a reference to add a new package to the repo
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-sdk-for-js%2Fissues%2F10076%23issuecomment-665395121&data=02|01|sarajama%40microsoft.com|4920ca466bc04b7fac4f08d83367c59e|72f988bf86f141af91ab2d7cd011db47|1|0|637315868072642566&sdata=rvP9iN4QlrCeEplnaEUBO9KBCIMZ05OKXdDe2SpidRc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAETCWC33H4KOWV5PC4KWELR56C7NANCNFSM4O2HFRMA&data=02|01|sarajama%40microsoft.com|4920ca466bc04b7fac4f08d83367c59e|72f988bf86f141af91ab2d7cd011db47|1|0|637315868072642566&sdata=%2Btmx%2BGnQMSt517XbtW%2BtBE27BJ8KBHBfcNPZuxsBbFM%3D&reserved=0.

@sarangan12 @ramya-rao-a This issue got assigned to me and I have started on it (a little). So far I just copied an autorest config file from another library and pointed it at various in-progress versions of the swagger. This led to https://github.com/Azure/autorest.typescript/pull/705. I haven't started on setting up the build or anything, so nothing much to redo starting from the template, which I can definitely do. I do want to make sure I'm not duplicating work by continuing on this issue, though...

There was a slight confusion here :)
The issue was initially assigned to @sarangan12, so when he got notified of my comment above, he jumped to reply without seeing the previous context
No harm done, this is all you @nguerrera, go on full steam ahead!

@ramya-rao-a I put up a draft PR: #10336. Feedback welcome. It's still completely untested and likely missing things to get it to work end-to-end. My next step will be to try to use it, adding appropriate tests and samples.

#10336 is out of draft. I am going to look at testing as part of building the outer convenience layer. #10336 doesn't export anything so there's nothing to test as part of that PR.


GPG key expired 21 Jun 2024

Description
Using the directions at https://docs.gitea.com/installation/install-from-binary the build verifies but warns about the key expiry.
# gpg --verify gitea-1.21.11-linux-amd64.asc gitea-1.21.11-linux-amd64
gpg: Signature made Mon 15 Apr 2024 11:43:42 PM EDT
gpg:                using RSA key CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpg: Good signature from "Teabot<EMAIL_ADDRESS>[expired]
gpg: Note: This key has expired!
Primary key fingerprint: 7C9E 6815 2594 6888 62D6  2AF6 2D9A E806 EC15 92E2
     Subkey fingerprint: CC64 B1DB 67AB BEEC AB24  B645 5FC3 4632 9753 F4B0

# gpg --list-keys
/root/.gnupg/pubring.kbx
------------------------
pub   rsa4096 2018-06-24 [SC] [expired: 2024-06-21]
      7C9E68152594688862D62AF62D9AE806EC1592E2
uid           [ expired] Teabot<EMAIL_ADDRESS>
Gitea Version
1.21.11-linux-amd64
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Installing Gitea from binary v1.21.11
Database
None

https://github.com/go-gitea/gitea/blob/24f4ebb8a957e4593e7f8472cf29f0a40b9dc161/SECURITY.md?plain=1#L19-L27

Please verify it again after upgrading the key from a public key server.

https://github.com/go-gitea/gitea/blob/24f4ebb8a957e4593e7f8472cf29f0a40b9dc161/SECURITY.md?plain=1#L19-L27

The security documentation looks like needs to be updated.

Please verify it again after upgrading the key from a public key server.

@lunny  which server?

No change.
# gpg --refresh-keys
gpg: refreshing 1 key from hkps://keys.openpgp.org
gpg: key 2D9AE806EC1592E2: "Teabot<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

# gpg --verify gitea-1.21.11-linux-amd64.asc gitea-1.21.11-linux-amd64
gpg: Signature made Mon 15 Apr 2024 11:43:42 PM EDT
gpg:                using RSA key CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpg: Good signature from "Teabot<EMAIL_ADDRESS>[expired]
gpg: Note: This key has expired!
Primary key fingerprint: 7C9E 6815 2594 6888 62D6  2AF6 2D9A E806 EC15 92E2
     Subkey fingerprint: CC64 B1DB 67AB BEEC AB24  B645 5FC3 4632 9753 F4B0

No change.
# gpg --refresh-keys
gpg: refreshing 1 key from hkps://keys.openpgp.org
gpg: key 2D9AE806EC1592E2: "Teabot<EMAIL_ADDRESS>not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

# gpg --verify gitea-1.21.11-linux-amd64.asc gitea-1.21.11-linux-amd64
gpg: Signature made Mon 15 Apr 2024 11:43:42 PM EDT
gpg:                using RSA key CC64B1DB67ABBEECAB24B6455FC346329753F4B0
gpg: Good signature from "Teabot<EMAIL_ADDRESS>[expired]
gpg: Note: This key has expired!
Primary key fingerprint: 7C9E 6815 2594 6888 62D6  2AF6 2D9A E806 EC15 92E2
     Subkey fingerprint: CC64 B1DB 67AB BEEC AB24  B645 5FC3 4632 9753 F4B0

Please try again. Now the keys will be sent to

keyserver.ubuntu.com
pgp.mit.edu
keys.openpgp.org


Clean metadata for 2022 content

Docs Build status updates of commit 974e9d5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docset/winserver2022-ps/adfs/Remove-AdfsFarmNode.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/smbshare/Disable-SmbDelegation.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/smbshare/Enable-SmbDelegation.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/smbshare/Get-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/smbshare/Get-SmbDelegation.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/smbshare/Remove-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/smbshare/Set-SmbBandwidthLimit.md
:warning:Warning
View (WindowsServer2022-ps)
Details

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Disable-DiagnosticDataViewing.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Enable-DiagnosticDataViewing.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticData.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticDataTypes.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticDataViewingSetting.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Get-DiagnosticStoreCapacity.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Microsoft.DiagnosticDataViewer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.DiagnosticDataViewer/Set-DiagnosticStoreCapacity.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Disable-ServerManagerStandardUserRemoting.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Enable-ServerManagerStandardUserRemoting.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Export-SmigServerSetting.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Get-SmigServerFeature.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Get-WindowsFeature.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Import-SmigServerSetting.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Microsoft.Windows.ServerManager.Migration.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Receive-SmigServerData.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Send-SmigServerData.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/ServerManager.md
:white_check_mark:Succeeded

docset/winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md
:white_check_mark:Succeeded

docset/winserver2022-ps/activedirectory/ActiveDirectory.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADCentralAccessPolicyMember.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADComputerServiceAccount.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADDomainControllerPasswordReplicationPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADFineGrainedPasswordPolicySubject.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADGroupMember.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADPrincipalGroupMembership.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Add-ADResourcePropertyListMember.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Clear-ADAccountExpiration.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Clear-ADClaimTransformLink.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Disable-ADAccount.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Disable-ADOptionalFeature.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Enable-ADAccount.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Enable-ADOptionalFeature.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADAccountAuthorizationGroup.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADAccountResultantPasswordReplicationPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADAuthenticationPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADAuthenticationPolicySilo.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADCentralAccessPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADCentralAccessRule.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADClaimTransformPolicy.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADClaimType.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

docset/winserver2022-ps/activedirectory/Get-ADComputer.md
:white_check_mark:Succeeded
View (WindowsServer2022-ps)

This comment lists only the first 50 files in the pull request.

docset/winserver2022-ps/adfs/Remove-AdfsFarmNode.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Uninstall-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Disable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Enable-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Get-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Get-SmbDelegation.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Remove-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

docset/winserver2022-ps/smbshare/Set-SmbBandwidthLimit.md

Line 0, Column 0: [Warning-link-out-of-scope] File 'winserver2022-ps/Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' referenced by link '../Microsoft.Windows.ServerManager.Migration/Install-WindowsFeature.md' will not be built because it is not included in build scope.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Texture compression support in gltf

This adds basisu texture compressions and transcoding support for gltf.
In order to support the required basisu extension I ended up having to change the gltf library from tinygltf to cgltf (which also supports other extensions that can be easily enabled as well). This change actually notably simplified the gltf loading code while I tried to keep it similar to what was already there.
I also implemented a non-standard feature in that when a metallicity-roughness texture is found in the gltf file it will look for optional standalone (i.e. separate) texture files for each component. There is discussion about adding this sort of capability as an official extension, as combining metal/rough when using texture compression is not ideal, but it will be a little while before that eventuates so this is an interim workaround.

It's a bit hard for me to review this just by looking at the code 😅
So I propose that we merge this once the flipped obj textures issue is resolved, then I'll go and test it on content.
Really great that we're getting compressed textures support though, we'll be able to test way bigger scenes now 🙂


update README with facebook connect support info

Hi @pscanf
I've created a meteor package and asteroid patch that enables native facebook connect to work seamlessly with the code you've already written in asteroid.
In this pull request I make a reference to it in the README under the appropriate section so that others can easily find it and install it via meteor and bower.
Thanks,
Keyvan

Coverage remained the same at 70.56% when pulling e387fc11bcd3ccade06ac5c89d77cb7a476beb1c on keyvanfatehi:readme-patch into 5d3e6242e4400e18af4c8ab99b112c804b87d85b on mondora:master.

Wonderful, thanks!


Unable to Install Package, No "Shipment" Object

Installation of the package fails because test classes refer to "Shipment" object which is not part of the package.

Fixed.

Fixed.


Spark to javalin

Convert from JavaSpark to Javalin
Closes #91

@floogulinc – The Javalin documentation uses Mockito to mock controllers for testing, which is how @wallerli's tests work. That's why he added it to the dependencies.

We will need to explain the new testing method and how its different from the other in the write-ups somewhere. Any ideas on what the guidance will be as to what we expect students to test with each one?

We will need to explain the new testing method and how its different from the other in the write-ups somewhere. Any ideas on what the guidance will be as to what we expect students to test with each one?

This definitely add complexity that we'll have to address. We'll need to explain mock objects (some lecture on this will be useful) and at least a few features of Mockito. It'll be useful to help the students understand what's Javalin and what's Mockito so they know where to search when they're trying to understand something or add some new functionality. I know I spent a while flailing in the wrong space before I figured out how to use Mockito to capture the argument passed to ctx.json().
I can try to write that up today sometime (he says with a slightly nervous tone). 😜

Before we merge this we should remove Util.java since it's not used anymore.


Docker TLS Support

I currently can't use registrator because it's not supporting docker tls.
I'm new to Go, but I tried to add the feature in a fork and didn't got it working..
BTW The current used docker client (from fsouza) already has tls support.
I think it wouldn't be that hard for someone with some go experience to add this feature. ;)

Why is TLS necessary? It should be connecting on the same host using Unix socket.

I have a Docker Swarm running and I needed to switch to TCP so the Servers can be managed through Swarm. In my case all my servers are located at different Datacenters, so I use TLS to secure the data.
The docker "socket" is now only reachable over the network and using the certificates.
So TLS is in this case needed.
After some testing I found out that you also at least need the certifcates to connect to the socket.

You can bind to both a TCP socket and a Unix socket right? And when you mean over the network you mean you aren't running registrator on the same host as Docker?

Binding on TCP and Unix socket didn't work for me..
Could you provide me your way of binding to unix socket? Maybe I'm doing something wrong.
But it would be also nice to have registrator work with tls secured network sockets, wouldn't it?

Working with secure network sockets encourages people to run registrator on a separate host from a particular Docker instance, which is not how it was designed to be used or best practice.
You can provide multiple -H options to the docker daemon when starting it:
docker -H tcp://<IP_ADDRESS>:2376 -H unix:///var/run/docker.sock

Thanks for you docker socket example you sent.
I tested it and the fix for me was that the DOCKER_TLS_VERIFY environment variable was set when connecting to the non tls local docker.socket.
Thanks for your help!

@progrium docker for windows is not support docker.sock, can you add tls support or any other client else in the future? i'm very interested in this project, it's amazing, thanks.

@liiujinfu as I mentioned before, none of the developers on registrator have a Windows machine to even test docker support, so if you want docker support on windows for registrator, you're going to need to do some legwork to make that possible. I'll definitely review your pull request once its open.

@josegonzalez I'm so sorry for that, I check docker-client code, and found that support for communication in tls, at windows platform, it works too, so I got that question, I have not learn golang, but, anyway, I'll try to learn that and make it possible, sorry for that...


Password Hash Sync for AD Synced users

We have completed all of the steps in these articles, however passwords for AD synchronized users are not working in the managed domain. Passwords only work if they have been changed in AD after Azure ADDS was enabled. Can someone confirm if password changes are required for all synchronized users after enabling Azure ADDS? The article says password changes are required for cloud users, but it doesn't say they are required for AD synchronized users.

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

ID: 80784d9f-1c4d-00ed-dc71-033ae276b267
Version Independent ID: 940da10a-71c3-300b-2187-c34b44add22b
Content: Azure Active Directory Domain Services: Synchronization in managed domains
Content Source: articles/active-directory-domain-services/synchronization.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@1trevor  Thanks for your feedback! We will investigate and update as appropriate.

@1trevor  The next paragraph explains how to handle those accounts. "For user accounts synced from on-premises AD using Azure AD Connect Sync, you need to configure Azure AD Connect to synchronize password hashes in the NTLM and Kerberos compatible formats."
Have you already done this?
@iainfoulds

Hope the above answers your question. Since I have not heard back I will proceed to close this thread. If you have further questions feel free to tag me in the comments or open a new issue and I will gladly continue the discussion.


<EMAIL_ADDRESS>decompress error

Failed to extract files from C:\Users\docto\scoop\apps\twilio\4.1.0\twilio-win32-x64.tar.
Log file:
~\scoop\apps\twilio\4.1.0\7zip.log

Hi @AriRoxx  , Thanks for reaching out. I tried replicating this issue but didn't get any errors. Can you try uninstalling twilio cache (if you've installed it before ever)?
Execute:
scoop uninstall twilio
scoop install twilio

Closed due to inactivity.


Multipart upload corrupting file under trinidad

Multipart file upload seams to be broken.  When posting a binary file (in my case, an jpg image) the file is transfered correctly when the server is running under MRI or jruby + webrick (eg, $ jruby -S bundle exec rails s), but not when run under trinidad.  Under trinidad, the binary temp file created does not match the original--about ~10% has changed, including (always) the first few bytes which cause it to not be recognized as an image.
I'll attach a simple test app that can be used to repro--basically, I just generated a new rails app and slapped in a #create method on the default controller to examine the posted binary.  Steps to repro:

start the server: $ jruby -S rails s
post the image: $ curl -i -s -S -F "foo=bar" -F<EMAIL_ADDRESS>-X POST http://localhost:3000
the above should be successful; it should puts success in the console and return a 200
now stop the server and restart with trinidad, taking the defaults:  $ trinidad
post the image again: $ curl -i -s -S -F "foo=bar" -F<EMAIL_ADDRESS>-X POST http://localhost:3000
the second time fails, per the file comparison between the rack-created tempfile and the original image.

As mentioned above, the behavior is the same under both osx and windows.  Everything should be latest versions, but I also tried regressing back one version for most things, with similar results (although I think a few combinations yielded a SEVERE ERROR on the trinidad console rather than corrupting the image).
Environment(s):

Rails 3.2 (also under 3.1.x)
JRuby 1.6.6 (also under <IP_ADDRESS>)
Ruby 1.9
OSX & Win64
Trinidad 1.3.2 (also tried earlier)
jruby-rack 1.1.3

Here's a zip file containing the test rails app, along with an image to use with the curl command:  http://dl.dropbox.com/u/12710/jupload.zip
It's really nothing more than a default new jruby/rails app with the following function added to the application controller:
def create
puts
image = params[:photo]
if image && FileUtils.compare_file(image.tempfile.to_path,'image.jpg')
puts ">> SUCCESS #{image.tempfile.to_path}"
render :text => "Success", :status => :ok
else
puts ">> FAIL"
FileUtils.cp image.tempfile,  "bad.jpg"
render :text => "Failed", :status => :unprocessable_entity
end
end

At the moment this issue is keeping me from deploying with trinidad.  Would deploying under tomcat or glassfish be any different, or will they end up calling the same jruby-rack code path?  That is, of course, if the issue is in jruby-rack.

@nicksieger maybe it's worth doing a 1.1.4 release already (if you have some time)
... since Dave seems to be willing to put it on production if this one works :)


Allow multiple clients within a same context

The configuration seems to be based on clients so you can only operate using the client you have set for a context:
contexts:
    test-password:
        issuer: http://localhost:8080/realms/test
        client: test-password
        flow: password
        user: test-user
        user-password: test-user-password

As a user, I would like to be able to define a single context where all the clients associated with a given issuer are defined so that I don't have multiple issuer entries pointing to the same URL. The main motivation for this is:

Make it easier to update a context so all users and clients associated with an issuer are grouped. For instance, if I want to change the URL for an issuer I don't need to go over multiple contexts.
Make it easier to read the configuration file when you have multiple issuers and multiple users and clients for each one
Setting context-level configuration settings that apply to all users and clients within a context easier

When executing commands within a context, I would also like to choose a client from the context rather than be forced to switch to a different context.
If the configuration is similar to this:
contexts:
    test:
        issuer: http://localhost:8080/realms/test
        client: client-a
        user: user-a
        users:
            user-a:
                credentials:
                    password: mypassword
            user-b:
                credentials:
                    password: mypassword
        clients:
            flow: password
            client-a:
                 credentials:
                     secret: mysecret
            client-b:
                 credentials:
                     secret: mysecret

I can now run commands like(assuming test context is active):
# Use default client-a and user-a
kct token

# Use a different client
kct token --client client-b

# Use a different user
kct token --user user-b

For testing purposes, I'm also wondering if it makes sense to expose options to override/set the following options when using the token command:

flow (perhaps it should be grant-type because flow in Keycloak is another thing and grant type is easy to map to the specs)
user
user-password

Otherwise, I'm forced to update the context configuration whenever I want to test a new one. Or perhaps #8 is enough to make it easier to set/update a context with additional configuration.
I hope it makes sense.

Ability to re-use issuer-url, client config, and user credentials makes sense, but don't think it'll work in the way you've proposed.
I don't really want to have a ton of config options to the commands, and would rather want just --context. In addition a context is used to associate stored tokens. If you try the latest release you can even do things like get the initial refresh token with a broad scope, then request tokens from that with a smaller scope. With that one thing I'd like to try to achieve is the ability to have a SSO scenario. Where you have one refresh token that is used for multiple purposes, but then each different purpose can get a subset of the scopes.
Need to think about this a little bit, but I could imagine something like:
issuers:
   local-test: http://localhost:8080/realms/test
   remote-test: http://remote/realms/test
users:
  admin:
     user: admin
     password: admin
clients:
 myclient:
    id: myclient
   secret: mysecret
contexts:
  main:
     issuer-ref: local-test
     user-ref: admin
     client-ref: myclient
     scope: foo, bar
  sub:
    context-ref: main
    scope: foo
  custom:
     issuer: http://localhost:8080/realms/something
     client: anotherclient
     flow: device

That allows you to do the straightforward just configure a context, or use re-usable stuff. It does complicate the CRUD commands for config a bit, but may be worth it.

Take two:
issuers:
  local-test:
    url: http://localhost:8080/realms/test
    clients:
      myclient:
        client-id:
        flow: device
    users:
      pedro:
        username: pedro
        password: test

contexts:
  main:
     issuer-ref: local-test
     user-ref: pedro
     client-ref: myclient


mention what happens if OPENSSL_NO_RC2 is defined

The changes in cset 7e1b7485 modified the pkcs12 command to use 3DES for certificate encryption if RC2 is disabled. This updates the man page to reflect the change.

Yep, let me ping the internal person.

Can I suggest we just always make 3DES the default.

Can I suggest we just always make 3DES the default.

In master, yes. In 1.1.1 we can't really do that so this PR would still be relevant there.

I can't believe that NID_pbe_WithSHA1And3_Key_TripleDES_CBC is still the best that pkcs#12 supports, and I wonder what happens if you use the -aes128 option.

I forgot to say but this is intended for 1.1.1 in the end.
Dne pá 19. 7. 2019 16:33 uživatel mattcaswell<EMAIL_ADDRESS>napsal:

Can I suggest we just always make 3DES the default.
In master, yes. In 1.1.1 we can't really do that so this PR would still be
relevant there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/openssl/openssl/pull/9415?email_source=notifications&email_token=AAWMMDEAFG5VHAHYGFMMYI3QAHGDFA5CNFSM4IFGJKFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2LZWYY#issuecomment-513252195,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWMMDDJ72H5PWCJQGX2DRTQAHGDFANCNFSM4IFGJKFA
.

closing to kick the CLA bot

The internal person has somewhat disappeared but they managed to obtain a letter from an othorty Filter in Oracal Legal.  The response added you to the Oracle CCLA.
It will take a day for this to be incorporated into the contributors database.

Seems like this was already cleared.
Dne čt 8. 8. 2019 13:33 uživatel Pauli<EMAIL_ADDRESS>napsal:

The internal person has somewhat disappeared but they managed to obtain a
letter from an othorty Filter in Oracal Legal. The response added you to
the Oracle CCLA.
It will take a day for this to be incorporated into the contributors
database.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/openssl/openssl/pull/9415?email_source=notifications&email_token=AAWMMDERS5ME7TFOYVTTLELQDP77LA5CNFSM4IFGJKFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD33KK5A#issuecomment-519480692,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAWMMDFYVAZGIMHFOG34Q2DQDP77LANCNFSM4IFGJKFA
.

Pushed to master and 1.1.1. Thanks.


Feature Request / Question: noqa inline quick fix

Hello! A quick question on existing features / possible future feature:
I currently only see the option to exclude rules from the workspace or global settings using the quick fix tooltip:

Is there a feature currently to have an inline quick fix option like the below (from the ruff extension)?:

Which results in:

If not, this would a terribly useful quick fix action to have.
Appreciative of this lovely tool!

Which version of the extension are you on? I believe there should be options to ignore the individual rule for that line or to ignore all rules for that line.

Hmm, it is working for me on that version. Do you have sqlfluff.codeActions.noqa set in your settings.json? If that is false (it is not false by default) then the code actions will not show.

@pep-sanwer  Actually taking a look at it, that ST06 rule is excluded from the noqa by default. Don't remember exactly why, but you can set sqlfluff.codeActions.noqa: true to enable the code actions for all the rules, the ones set in the array by default do not show code actions for those rules.


Update references in tutorial

Also kicking the CI as the MNE-BIDS branch and data has been updated, I want to ensure it all still runs with a fresh CI install.

Codecov Report

Merging #266 (6304db1) into master (e840317) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #266   +/-   ##
=======================================
  Coverage   97.55%   97.55%
=======================================
  Files          41       41
  Lines        1104     1104
  Branches      157      157
=======================================
  Hits         1077     1077
  Misses         11       11
  Partials       16       16

Impacted Files
Coverage Δ

...rs/datasets/fnirs_motor_group/fnirs_motor_group.py
100.00% <ø> (ø)

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 e840317...6304db1. Read the comment docs.


"pet- does not have storage.objects.get access to undefined/undefined" for gs:// Workspace Data

I have a key/value pair in my Workspace Data:
my_gcs_path -> gs://my-bucket/path

The Terra UI hyperlinks the value, but clicking on it produces a dialog with an error:
File Details
Error loading data. You may not have permission to view this file.
Details
{
  "error": {
    "errors": [
      {
        "domain": "global",
        "reason": "forbidden",
        "message"<EMAIL_ADDRESS>does not have storage.objects.get access to undefined/undefined."
      }
    ],
    "code": 403,
    "message"<EMAIL_ADDRESS>does not have storage.objects.get access to undefined/undefined."
  }
}

We will definitely look into the source of the 403. Is this KV still giving this error?
The reason for going with the basename here is that the UI component powering the Key Value data is also powering the tables. There, individual cells are typically more cramped. So you'd get a whole column of values displaying like "gs://my-bucke... ". We've had issues in the past trying to put ellipses other places, like "...t/path". I can't recall what exactly made that hard. I'm not sure if we could display the full path in just this particular table, since it's two column.

Hi Brad.
I just checked the behavior clicking on the value has not changed.
I see how it is a shared component with Tables and the use case there definitely makes sense. I have a table with a "bam_output_path" column. If the gs:// URL were displayed there, all of those would either be super-wide columns or would look something like:
bam_output_path
gs://mybucket/genomes/bams/...
gs://mybucket/genomes/bams/...

It seems like both views could benefit from a reduction of whitespace and for the key/value pairs, it would be nice if the behavior was different since there is more space available. I'm viewing it right now on my laptop monitor (not even a large external monitor) and there's a lot of horizontal and vertical space going unused.
Thanks!


HTML page title is missing

We need to add a title to the HTML page, so that people looking at the tabs would know that this is about the SEMIC Style Guide.
Currently it looks like this:

This happens only on the sub pages, because they don't have a title-level header (starting with = ). The main page (index.html) has a title, and it is also shown in the browser tab.
One solution would be to repeat the title on each subpage. Perhaps even trying to hide it somehow. ^1 I am not sure how this would interact with the contents/index generation.
Another solution (although not recommended) would be to define a header file, where the title of the page is defined:
https://docs.asciidoctor.org/asciidoc/latest/docinfo/#head

It is fixed now. Each page has an H1 title.


Add missing winapi features

To support RLS in Rust repo, features from https://github.com/rust-lang/rust/pull/51677#issuecomment-402781751
r? @alexcrichton

@bors: r+

:pushpin: Commit 4671a2aa7ad5fbd55ba0a0f5cea31a95cda88dc8 has been approved by alexcrichton

:hourglass: Testing commit 4671a2aa7ad5fbd55ba0a0f5cea31a95cda88dc8 with merge af9e40c26b4ea2ebd6f31ee86ee61d5ac1c74eb0...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing af9e40c26b4ea2ebd6f31ee86ee61d5ac1c74eb0 to master...


Define variable needed for block

This fixes an AppController crash when there are instances assigned to a machine that is going to be terminated.

https://ocd.appscale.com:8080/job/Daily Build/3803/


add hierarchicalforecast to github workflow

Description of changes:
add hierarchicalforecast to github workflow
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Please tag this pr with at least one of these labels to make our release process faster: BREAKING, new feature, bug fix, other change, dev setup

I vote for merging this with the statsforecast one https://github.com/awslabs/gluonts/blob/dev/.github/workflows/tests-statsforecast.yaml

Propose a name for it and we can do it. Nixtla, maybe? At the end these are wrappers from their repositories.

Propose a name for it and we can do it. Nixtla, maybe? At the end these are wrappers from their repositories.

Yes, sounds good to me

Just the workflow name otherwise good to go! 🚀


Bind internal services to localhost

Let's bind internal services like tracing and metrics to localhost by default, for security reasons.

This will break our current node deployments inside containers which were originally all binding to localhost and then no one was able to communicate with them.

This will break our current node deployments inside containers which were originally all binding to localhost and then no one was able to communicate with them.

@dconnolly can we change the configs for those specific nodes as part of this PR? Where are the zebrad configs for those deployments?
It's better to choose secure defaults, and then modify them as needed.

We can do this fix post-release if you'd like. I thought it was a quick fix, but it seems like it's more complicated than I expected.

@dconnolly Can we set a specific zebrad.toml for the deployments? If so, would this work: https://github.com/ZcashFoundation/zebra/pull/649#discussion_r454798878 ?

Currently our deployments run 'zebrad start' on container startup, we can package up or generate config files and either build that in or pass to the container on startup (I might prefer the latter so that we can still have the option of 'shipping' our built container images, but having a  easy to run container with minimal config as a shipped artifact is also nice, those wanting different configs can build and run with their own config). I'm up for making changes but yes would rather wait until post-release so that we're not fiddling with Dockerfiles etc in the meantime. 📦

Opened ticket #660 to deal with this issue.


Data analysis added eda enhancement to streamlit app.py file

Issue no.: #406
@sanjay-kv  I have added eda to to existing streamlit.app file and also updated  README.md file as per requirements .
Is there any changes then let me know
Please check PR .

@sanjay-kv pls check pr and merged it !

@sanjay-kv pls assigned this labels

@sanjay-kv pls add Gssoc-ext label !