Events API Support

💡 This is not a bug report so much as it's intended to be a discussion about what the best solution would be in the context of this SDK.
At Slack, we've been putting together a few tutorials around using various SDKs to implement the Slack Events API into an app or bot. One of those tutorials was written using this library and a simple Sinatra app to provide endpoints for Events API calls from Slack. While that approach is more of a boilerplate for new developers or experienced developers to use as a starting point, we've also been discussing what it might look like to add this support to some of the SDKs themselves.
Adding Events API support has the potential to improve the development workflows and time it takes to build and troubleshoot Slack apps, but it comes with the cost of added dependencies and complexity in the SDK itself. In the Ruby ecosystem, for example, I think the most likely candidates would be Grape or Sinatra.
I'd love to hear your thoughts @dblock, as well as those of your community. 🤖

If I understand correctly you'd like slack-ruby-bot to support events delivered via HTTP GET/POST? Support things like slash commands? I think it's a great idea, developers want all-in-one solutions that are super easy to put together.
https://github.com/slack-ruby/slack-ruby-bot-server could be another place to do this, as it solves higher level problems.
Generally you want to be able to decompose things in gems, so if I am writing a Rails app I should be able to take slack-ruby-bot, slack-rails-api (doesn't exist) and tie all these things together super easily.

Oops, I realize now that I posted this to the wrong repo. I meant to post it in ruby-slack-client.
I agree with the idea of an a la carte model to include only the items a developer would want, rather than a massive collection of dependencies a developer may not use. I need to do a bit of research regarding gems that invoke a webserver to see what the existing strategies are...

Wondering if there's been any progress on this? Would love to switch to the events API from rtm using this library.

not AFAIK

What would be the best way to tackle this? The Events API provides an easier foundation to build scalable bots and it looks like Slack is putting it on equal ground with the Realtime API. I'm going to rewrite our bot to use it and would like to contribute back to this library if possible.

I would start in slack-api-ref and work up the stack from there.

@alexagranov

@dblock Got it.
For my testing so far, all I've had to do was add an endpoint to my Sinatra server, /events, and then registered that as the Request URL on the Slack "Event Subscriptions" page for the app in question.
I then just break out specific event handling logic via case-statement - I'm only listening for things like team_join, tokens_revoked, and (god forbid) app_uninstalled so far, but I don't see it being an issue to handle something like app_mention and reply back to User via Web API.  Action callbacks (buttons, dialog submissions) and slash commands already have their own respective endpoints.
As far as I can see, there is no way to automate event subscription via API (https://api.slack.com/events-api#subscriptions) - everything has to be done manually on the Slack app developer page - so I'm left wondering:

Is there really anything left for us to do in slack-api-ref?  Or slack-ruby-client for that matter?

Do we just need to parse the text of an app_mention and invoke the message hook call method which should route to the appropriate registered command for us?

Thinking about this some more...I'm wondering if there isn't overlap here with the desire for slash command support (#68):
In our bot, I ended up abstracting how slash commands (via Sinatra endpoint) and slack-ruby-bot command handlers (via RTM) respond with the use of ActiveJob - as many of the tasks we offer will take longer to execute than the maximum time Slack allows for slash commands to return a response.
Should we separate how command handlers are registered ("routing") - which the current dsl handles nicely - from some kind of "executor" interface that allows developers to implement either sync or async responses?

@alexagranov - I don't have good answers to these specific questions, but I'd like to be able to take a bot that I have written (eg. https://github.com/slack-ruby/slack-shellbot) and turn it into a bot that is not RTM based, but event based with some configuration.

@dblock Gotchya.  Let me think about this some more, but I may start proposing a direction in a PR soon.

@dblock I've fully moved over to Events API and am happy to report my bots don't need to be invited into people's sensitive channels - as well as no disconnect issues.
Looked around here some more and I do think we could leverage the MVC pattern, as exemplified by the Inventory example:

Controllers can continue to define instance methods that are offloaded to command blocks
Controllers could offer another mechanism for delegating Event API events to instance methods for handling
Views can offload response handling to whichever client implementation - RTM or Web - has been injected
It would still be up to upstream (slack-ruby-bot-server) to serve endpoints via Sinatra/Rails and instantiate Controllers as necessary

I think the first bit to bite off is to abstract the SlackRubyBot::Client away from being a pure Slack::RealTime::Client and allow for "bot" clients to also be a Slack::Web::Client when injected into Controllers.  This way Web clients can offer their own implementation of say which everything is using right now.
How does that sound?

This seems like a reasonable step to make things easy, give it a shot, make some PRs :)

I've started https://github.com/slack-ruby/slack-ruby-bot-server-slack that makes it easier to handle events, slash commands and interactive buttons with slack-ruby-bot-server, if anyone wants to try it.

Released https://github.com/slack-ruby/slack-ruby-bot-server-events that has complete events, slash commands and actions support.


hide only menu button

It is possible to add a hide_menu_button option to block ui modification?
Thank you

Duplicate of #53 and #38
Read those issues for my reasoning behind not including this in kiosk-mode and towards the end of #38 it's explained how to do this with card mod.


can not read body stream, Request.Body.length =0

Describe the bug
A clear and concise description of what the bug is.
can not read body steam
To Reproduce
    [ApiController]
    [Route("[controller]/[action]")]
    public class WeatherForecastController : ControllerBase
    {
        [HttpPost]
        public async Task<string> Encode([FromBody]string xx)
        {
            var body = "test";
            Request.EnableBuffering();
            using (var reader = new StreamReader(Request.Body, encoding: Encoding.UTF8))
            {
                body = await  reader.ReadToEndAsync();
                Request.Body.Position = 0;
            }
            return body;
        }
    }

I want to read http body as string.
but in my test, Request.Body.length  always is  0;so it get empty result
may be you can give a method  like  Request.BodyAsString ,it is a useful feature
Further technical details

ASP.NET Core version  3.1.0

Thanks for contacting us, @gitlsl.
@pranavkm can you please look into this? Thanks!

@gitlsl you'll have to read the request body before MVC has had read it. Here's an example that shows this: https://github.com/aspnet/AspNetCore/issues/15009#issuecomment-542291956. https://github.com/aspnet/AspNetCore/issues/15009#issuecomment-542444635 has an explanation as to why this behavior changed between 2.x and 3.x.


All radio buttons and checkboxes have bold text

I think that was changed by accident?
Before:

After:

Fix pushed!

ref: https://github.com/BustByte/coronastatus/commit/b0fe8064f1cdbf8d9f8fe75c7223f4a65143f78c

Awesome, thanks :)


Make listener priority configurable

Symfony has a AddRequestFormatListener registered as priority 1, which happens after this is registered.
We have some additional json content types we register against the framework, which aren't picked up by this listener with it's existing priority.

Hi, Sam!
Thanks for pull request. Update your branch, please.

Updated 👍

I've decided to make this configurable, with a default of 100, in case changing it to lower is a breaking change for other peoples applications.

I'm very grateful. Thanks for your support.


Update config schema deafults

Make extra_args and edge_bits reflect what is in the code and default sys.config

See (permanent links to current master branch):

https://github.com/aeternity/epoch/blob/4619527562c168e9a6efa59ccbfd6fc26ed9c990/apps/aecore/src/aec_pow_cuckoo.erl#L35
https://github.com/aeternity/epoch/blob/4619527562c168e9a6efa59ccbfd6fc26ed9c990/config/sys.config#L42

Not sure if in the scope of this PR updating also dev1, dev2 and dev3 using a single mining thread.


Property Rights

It's unclear in this proposal where the ADA to be delegated would come from.
If the idea is that it should come from the initial founding allocations to the founding entities IOHK, Emurgo, and the CF, then this can't be enforced by the CIP process without violating their property rights. This should instead be taken up with each founding entity directly.

Hi @ia-davidpichler,
Thanks very much for your input. How and at what point in a review process would it be appropriate to contact each founding entity in order to seek some initial feedback or indication regarding potential interest or support for an idea that employees may exercise some direct responsibility for delegating ADA owned by the respective entity?
Oliver


Fix new dashboard mixpanel

New dashboard fails in production since the code path was using a faulty variable.
Further precautions would be to update staging environment to at least have some random values set for the code paths to match production env. Updated app_config to recommend frontend devs to set these too to catch them in dev env already.
Ideally this part of the code should have been tested as well, but that can be solved later.

@CartoDB/frontend FYI

:+1:


Udemy-dl v1.0 execution errors

Greetings,
I've just downloaded the v1.0 release and when I try to execute
the command "python .\udemy-dl.py", it doesn't work and show some errors:
Traceback (most recent call last):
File ".\udemy-dl.py", line 31, in
import udemy
File "C:\udemy-dl-1.0\udemy_init_.py", line 32, in
from udemy.udemy import course, fetch_enrolled_courses
File "C:\udemy-dl-1.0\udemy\udemy.py", line 27, in
from udemy.internal import InternUdemyCourse as Udemy
File "C:\udemy-dl-1.0\udemy\internal.py", line 26, in
from udemy.compat import time, sys
File "C:\udemy-dl-1.0\udemy\compat.py", line 33, in
import m3u8
ModuleNotFoundError: No module named 'm3u8'
Thank you.

 My bad!
Now it works flawlessly!
Thank you caleb-tolu


Android build using animated: false in router will cause resume / suspend actions to break content inside

Which platform(s) does your issue occur on?
Android device, just my LGV20
Please, provide the following version numbers that your issue occurs with:

CLI: (run tns --version to fetch it) -- 4.1.0
Cross-platform modules: (check the 'version' attribute in the
node_modules/tns-core-modules/package.json file in your project)

  "nativescript": {
    "platforms": {
      "ios": "4.0.0",
      "android": "4.0.0"
    }
  },

Runtime(s): (look for the "tns-android" and "tns-ios" properties in the package.json file of your project)

    "tns-android": {
      "version": "4.1.3"
    },
    "tns-ios": {
      "version": "4.1.1"
    }

Please, tell us how to recreate the issue in as much detail as possible.
Just do a simple this.routerExtensions.navigate with the option animated: false.
Then, once you've run that and redirected to a route inside <page-router-outlet>, if you hit the "Home" menu, and switch to another app (suspend). And then switch back to your NativeScript Angular app (resume), it will be completely white.
In my app, I had the following in the app.component.html:
<!-- https://docs.nativescript.org/angular/core-concepts/angular-navigation.html#page-router-outlet -->
<GridLayout rows="*,auto">
  <RadSideDrawer row="0">
    <StackLayout tkDrawerContent>
      <io-sidemenu [input]="vm.sideMenuInput"
                   (itemSelected)="onSideMenuTap($event)"></io-sidemenu>
    </StackLayout>
    <page-router-outlet tkMainContent></page-router-outlet>
  </RadSideDrawer>
  <FlexboxLayout row="1"
                 flexDirection="row"
                 justifyContent="center">
    <io-tab-bar [tabs]="vm.tabs"
                (tabTapped)="onTabTap($event)"
                *ngIf="show.tabBar()"></io-tab-bar>
  </FlexboxLayout>
</GridLayout>

The stuff inside <page-router-outlet tkMainContent></page-router-outlet> doesn't show. The tabs work.
If you navigate again after this, say with the tab bar that I have, it will show the content again. But suspend / resume seem to break when you do animated: false

Closing due to inactivity

This is happening even without navigation. Having a tab view in the page is causing issue I feel. Unable to reproduce in other pages.
Please reopen this issue @NickIliev

@sivsushruth can you please provide a Playground demo or a GitHub project that can reproduce the issue?


Follow Docstring Conventions

PR Description
I have noticed an inconsistent convention used throughout xgboost's core Python file. So I made some changes that will make the core file to respect docstring conventions according to PEP 257.

Thanks, is it possible to enforce this via pylint?

Codecov Report

Merging #4959 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4959   +/-   ##
=======================================
  Coverage   71.82%   71.82%
=======================================
  Files          11       11
  Lines        2300     2300
=======================================
  Hits         1652     1652
  Misses        648      648

Impacted Files
Coverage Δ

python-package/xgboost/core.py
76.98% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks.

I am not sure if there is a linter for this, but there should be one.

Em.  Usually I just build the doc myself and if there's no warning then I will submit it.


swag init cant’t

swag init
only search local path ./
Not work import packages which in go.mod

make sure your main.go is behind root project directly

what should I do if main.go file is in cmd dir?
@YXY-121
root
   /cmd
      /main.go
   /modules


Symfony workflow enhancement

Hi and thanks for this action.
The first time when you run php bin/phpunit it tries to install phpunit dependencies which it messes the tests log.

to avoid that, we should add php bin/phpunit install command to Install Composer Dependencies step to install dependencies first then run the tests.

@smoqadam Will you be willing to submit a PR to improve this.

Fixed in #377


Gh-3158: Improve Federated Store tests to use properties file

Related issue

Resolve #3158

This PR doesn't address the issue. I've updated the original issue to clarify the required changes. There are at least 11 files which can be changed based on a quick search.

Hello,
I worked on improving the FederatedStoreVisibilityTest.java file as described in the original issue. However, in your latest feedback, you mentioned there are 11 other files that need to be updated as well.
I apologize that I missed that requirement. Could you kindly provide more details on which 11 files need to be changed? I want to make sure I understand the full scope of changes required before making further updates.
Since it was not explicitly called out upfront, I assumed only the FederatedStoreVisibilityTest.java needed to be updated based on the initial issue description. Please let me know the name and location of the other 11 files, so I can incorporate the necessary changes in those places too.
I would greatly appreciate your guidance on this, so I can address the issue properly. Thank you!

This PR doesn't address the issue. I've updated the original issue to clarify the required changes. There are at least 11 files which can be changed based on a quick search.

Hello, @GCHQDeveloper314
I worked on improving the FederatedStoreVisibilityTest.java file as described in the original issue. However, in your latest feedback, you mentioned there are 11 other files that need to be updated as well.
I apologize that I missed that requirement. Could you kindly provide more details on which 11 files need to be changed? I want to make sure I understand the full scope of changes required before making further updates.
Since it was not explicitly called out upfront, I assumed only the FederatedStoreVisibilityTest.java needed to be updated based on the initial issue description. Please let me know the name and location of the other 11 files, so I can incorporate the necessary changes in those places too.
I would greatly appreciate your guidance on this, so I can address the issue properly. Thank you!

This PR doesn't address the issue. I've updated the original issue to clarify the required changes. There are at least 11 files which can be changed based on a quick search.

I have resolved this issue. #3158
Could you kindly review and merge it when you have the chance?


Introduce scope based access control for web hook APIs

Describe your problem(s)
As a subset of streaming APIs, webhooks APIs will be added. This issues is to add support scope based access control for those apis.

resolving since the pr is merged


releasing multiple opam packages from a single repository

first, thanks for your work on dune-release to make releases of opam packages that use dune so easy.
with dune-release 1.6.1 the synopsis is taken from a random opam file. e.g. https://github.com/ocaml/opam-repository/pull/21158 uses the dnssec.opam (where my expectation would have been to use dns.opam -- the one in dune-project).

Is there any news on this topic? Can we use dune-release with repository containing multiple opam files?

Can we use dune-release with repository containing multiple opam files?

Yes, you can (ocaml-zmq does that for example).
But the semantics are not necessarily solid as @hannesm notes. It should definitely prioritize getting the synopsis for the PR from the package in the (name) field in dune-project if available.


In mobile, touch event is triggered while scrolling through timeseries graph

Describe the bug
In mobile, touch event is triggered on the graphs making it changing always while scrolling through timeseries graph.
To Reproduce
Steps to reproduce the behavior (Mobile):

Go to Home
Go down to timeseries graphs
Scroll up and down
See error

Expected behavior
Scrolling through the timeseries graph should not affect the graphs.

Can you elaborate?

![ezgif com-video-to-gif](https://user-images.githubusercontent.com/11428805/79619122-9adc6a00-8129-11ea-9b0e-fe50c6f9b399.gif)
Notice how the dots in graphs moves while scrolling across the graphs.

Notice how the dots in graphs move while scrolling across the graphs

@nayakrahul This functionality is there to view previous data by horizontally scrolling the time series. It resets when you lift your finger. I'm sorry, I don't understand what the problem is. Is it interfering with normal scrolling for you?

@shuklaayush Thing is that when we scroll up and down on mobile devices, we don't move our finger at exact 90 degree, it involves a bit of horizontal scrolling too. So that's why when you scroll up and down, the dots in timeseries graph change too. I don't know if you understand or not. In the gif, you can see that i am not doing horizontal scrolling rather i am scrolling up and down.

Okay, I see your point. But we need an alternative interaction then. A lot of people find it useful to scroll horizontally across the chart to view data from earlier dates.

If there is upward or downward movement of page, we should keep the charts static.

Okay, can you fix this? I'll assign it to you then

Actually, the problem is related to d3.js . The same problem can also be seen when we zoom the page  in or out on mobile devices by putting fingers on the timeseries charts.

Anyhow I have made a hack to prevent charts from changing while scrolling but I don't know if it is a complete solution.


[provenance] Project name not displaying on retirement page for ICR retirements

Describe the bug
Project name not displaying on retirement page for ICR retirements. And also on the retirement certificate.
To Reproduce
Steps to reproduce the behavior:

Go to https://www.carbonmark.com/retirements/0x6476edf98bdc5ee62f9d4e4bf8932d69ed685483/44
The project name is not showing.

Expected behavior
The project name should be displayed

After investigating his actually is the project name, just an extremely long one

After investigating his actually is the project name, just an extremely long one

Ho lol :)


Annotation for ServiceBinding resource in the absence of an extension

PR #104 is introducing the Direct Secret Reference extension. Currently, there is a Custom Projection extension. If there is an annotation that is used in the absence of any extension, it would be easy for implementors. This will also help those who are creating new extensions; the code is not going to break as soon as they introduce non-compatible changes.
I propose to add this annotation for the ServiceBinding resource in the absence of an extension:
service.binding/type: "Standard"

If a spec extensions changes the default behavior so significantly that it breaks the behavior of existing resources. I'd argue that any implementation of that extension would be out of conformance with the core spec.

If an implementor decides to implement core specification without any extension. Currently, they need to put logic in the controller to skip any incompatible ServiceBinding resources based on all the supported extensions.  When the spec introduces new extensions in the upcoming versions, the code will be required to change again.  I think in addition to the above-mentioned annotation, probably there should be a spec version number also. Something like this:
service.binding/spec-version: "1.0"

If an implementor decides to implement core specification without any extension. Currently, they need to put logic in the controller to skip any incompatible ServiceBinding resources based on all the supported extensions.

That's not how spec extensions work. The core behavior is the only portable, guaranteed behavior; extensions are extensions of the core behavior. If we ship 1.0 of the spec, and then add a new extension in 1.1, every 1.0 conformant implementations does not suddenly become non-conformant.

When the spec introduces new extensions in the upcoming versions, the code will be required to change again.

If so, we failed as spec authors.

I think in addition to the above-mentioned annotation, probably there should be a spec version number also. Something like this:

service.binding/spec-version: "1.0"

K8s resources already have an api version number.
apiVersion: service.binding/v1alpha2
kind: ServiceBinding
...

This was discussed during the interlock call. Continuing the discussion here...

From yesterday's interlock call, these are my understanding. The spec is not extensible, but it has well-defined extensions.  The core spec and extensions are coherent to each other.  The implementation should be aware of extensions, even if it doesn't implement it.  This way, implementation can display better error messages when it doesn't support a particular extension.
So, I am closing this issue.

The spec is not extensible, but it has well-defined extensions.

The spec very much is extensible. There are extensions that we publish along side the spec, but there's no reason why extensions need to be versioned with the core. An implementation may define its own extensions to the spec so long as the behavior remains conformant with the core spec.
The rub with extensions is that they are inherently not portable between implementations since there is no guarantee that the other implementation supports the same extensions. For portable behavior, you can only depend on the core.

The implementation should be aware of extensions, even if it doesn't implement it.

I strongly disagree. The core spec is perfectly capable without awareness of any extensions, this is a fundamental requirement for the core. Extensions are aware of the core semantics and add new capabilities in a compatible way. An extension that brings the core out of conformance would mean the implementation of that extension would no longer conform to the core spec.

This way, implementation can display better error messages when it doesn't support a particular extension.

The failure mode for a user attempting to consume an unimplemented extension is dependent on what the extended behavior is. For example, with the direct secret extension the failure mode would be that the service won't resolve to a secret. We don't need to extend the core to add that behavior, that's the default behavior of the core spec.
It's the responsibility of extension authors to create extensions that layer on top of the core behavior in a way that is compatible with the core. If the implementation chooses to be aware of common extensions it doesn't support that fine, but we cannot require that behavior since there is no way to know of all possible extensions.
The user is responsible for ensuring the system implements any extension they depend upon. It's worth discussing how we can make enabled extensions detectable for smarter clients.


Redirect report

Is there any way how to track redirects? For example I load page domain.tld, it redirects to domain.com and it redirects to domain.com/en/ ...now I need to know all these url's where user will be redirected to reach final destination

Any solution?


[FancyZones Editor] Merge zones after resizer deletion

In https://github.com/microsoft/PowerToys/pull/12969 was added an opportunity to delete resizer in a grid layout. After the resizer was deleted, all zones adjacent to that resizer are merged.
In some cases, when coordinates and sizes of zones match, another way of merging is more preferable, e.g. for a 4-zones grid:
Expected:

Actually:

In other cases, the way to merge should be as it is.

The first example (expected versus actual) is clear to me. I wonder about the last one. 1 and 2 stay as they were (only the width is reset to 50%?) but 3 and 4 are merged. Why the difference between "zones above" versus "zones below" splitter? Why is the result not like the top-right image here? [ 1 | 2 ] (1+3 and 2+4)

@Jay-o-Way perhaps I described it not clear enough. The last two images are just different cases. In both last cases, the only way we can handle the deletion of the dotted resizer is to merge all four in a single zone.

Oh yes, nevermind then :)

how much work is here?  small / medium / large?


Get rid of the httpsCallable for legal in general

Originally tracked in #472 . Another way of doing it is to have a separate slugs collection, with read permissions (but not list?) and then allow security rules that verify that when a card is having a slug added that slug doesn't exist in the slugs collection.

Status still has it, but that handles failures OK and there's less risk of that causing breakage

[ ] Remove the disable_callable_cloud_functions command


Multiple Transform Pattern Endpoint

related to https://github.com/KittyCAD/engine/pull/2822

close in favor of #630


(P75) Typo

Hi,
Before figure 12-1, "two input and four output units" should be "four input and two output units".
Thanks! :)

Thanks for the note, I can confirm, this is a typo and should be "four input and two output units"

Added it to the errata here: https://github.com/rasbt/MachineLearning-QandAI-book/blob/main/errata/README.md


Is not scraping games, did they do something to prevent scraping?

Is not scraping games, did they do something to prevent scraping?

Returned from dir(Scoreboard()):
['__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__getstate__', '__gt__', '__hash__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__', '__weakref__', 'scrape_games']

No games scheduled for today, my mistake.


Updating Chart in a quick setInterval with specific animation dosen't draw the chart

Expected Behavior
Updating Chart in a quick setInterval with specific animation does draw the chart
Current Behavior
Updating Chart in a quick setInterval with specific animation dosen't draw the chart
Steps to Reproduce (for bugs)
https://jsfiddle.net/e2vn0gLt/2/
Environment

Browser name and version: Chrome
Link to your project: https://jsfiddle.net/e2vn0gLt/2/

@PodaruDragos setiing the interval 100ms you should align the animation duration to your interval otherwise the update of chart is invoked before chart is able to complete the update.
Be aware that the default animation is 1000 ms.
Try changing your animation options, aligning it to your interval, as following
animation: {
	easing: 'easeInOutElastic',
	duration: 100
},

@stockiNail oh thanks


Ensure empty AttributedSubstrings produce no runs

Empty AttributedSubstrings should contain no runs, however there was a small index calculation bug in which empty substrings in the middle of the string (neither at the start or end indices) would incorrectly expand their ranges to the next run. This resolves the bug by ensuring that the Runs.startIndex == Runs.endIndex for all empty substrings regardless of their location in the string.
Resolves rdar://138432081

@swift-ci please test


SAML IDP: Ability to customize the SAML EntityID

Preflight Checklist

[X] I could not find a solution in the existing issues, docs, nor discussions
[X] I have joined the ZITADEL chat

Describe your problem
When creating/managing a SAML IDP in the instance or organization settings, there is no way to customize the entityID attribute of the EntityDescriptor element (see section 2.3.2 of the specification). The value of the Entity ID is always set as https://{DOMAIN}/idps/{IDP_ID}/saml/metadata.
Describe your ideal solution
The ideal solution would be to allow setting a custom Entity ID via the SAML IDP configuration page/form. The field would be optional. When empty, the entity ID would default to https://{DOMAIN}/idps/{IDP_ID}/saml/metadata.
Version
No response
Environment
ZITADEL Cloud
Additional Context
The main benefit delivered by this is that it helps us facilitate the transition process of our customers from Auth0 to Zitadel.

Thank you for sharing your idea.
If there is a significant demand from customers/community, we will carefully consider implementing the feature.
Currently, the issue will be added to our product backlog to collect feedback.
Meanwhile, if you're interested in implementing it yourself, we also welcome pull requests.


http-client-java, add a basic readme

Add a very basic readme. I've omitted the emitter option part.
Had it proofread by copilot.
I think it should appear on npm package page, if http-client-java get released to npm.

No changes needing a change description found.

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs


Add timezone to information provided by module.

Hey @rebeccahughes any comments on the pr?

@juankiz  - Can you please implement this on Android as well?  I think this library is keen on keeping parity between iOS and Android.
Also, you might be able to do this with a 100% javascript solution right?
let offset = new Date().getTimezoneOffset();

Added a java impl on https://github.com/rebeccahughes/react-native-device-info/pull/59
@GantMan Not possible to get an Olson formatted timezone form javascript.

Closed via #59


Add a wiki: The Coppermind

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://stormlightarchive.fandom.com/, https://mistborn.fandom.com/
Link to destination (independent) wiki: https://coppermind.net/

Now available in version 2.2.0


On Android, baseline information is busted if line-height:normal

From @Hixie on June 23, 2015 22:54
See: https://code.google.com/p/chromium/issues/detail?id=503780
Copied from original issue: domokit/mojo#266

Maybe it's specific to the default sans-serif font.

(baseline.dart will demonstrate the problem once I've checked that in)


Optimized local Minimal API delegation to InvokeAsync() and InvokeAsync()

I bleeping hate that folks seem primarily interested in using Wolverine as a MediatR replacement and want this:
app.MapGet((Body body, IMessageBus bus) => bus.InvokeAsync<Response>(body));

// or

app.MapPost((Command cmd, IMessageBus bus) => bus.InvokeAsync(cmd));

It'd be nice to have a little more performant relay of ASP.Net Core to Wolverine w/o having to bounce through the dictionary lookups you do by calling InvokeAsync().
Instead, what if the Wolverine.Http package had a MapGetToWolverine<TRequest, TResponse>(url pattern) and
MapPostToWolverine<TCommand>(url)?
Also getting requests to relay metadata about TenantId to Wolverine innards that would be detected somehow on the HttpContext.

That would be great! Already doing something like that as extension methods. One challenge though is with parameters. If following REST approach to the endpoints we usually have {id} parameter for the entity the command/query operate upon. What is your recommendation to the endpoint URLs design? Especially if they are mostly for supporting the UI and not really a public Web API of some sort.

Just read this post https://www.freecodecamp.org/news/rest-is-the-new-soap-97ff6c09896d/
Will try to minimize RESTfullness of my apis moving forward. Just the command/query name as the URL and the payload in the body should be enough with small exceptions of really simple getters by id, which would not even need any mediators.


PROTEUS unit tests

We should aim to get the test coverage to 100% before the PROTEUS method paper in JOSS. Alternatively we need to label (or remove) parts of the code that are not yet necessary anymore.

Here's a breakdown of the current test coverage, for reference.
Name                                         Stmts   Miss Branch BrPart  Cover
------------------------------------------------------------------------------
src/proteus/__init__.py                          4      0      0      0   100%
src/proteus/atmos_clim/__init__.py               3      0      0      0   100%
src/proteus/atmos_clim/agni.py                 199    199     48      0     0%
src/proteus/atmos_clim/common.py                49      2     12      2    93%
src/proteus/atmos_clim/dummy.py                 70     18     14      4    69%
src/proteus/atmos_clim/janus.py                137     29     44     12    72%
src/proteus/atmos_clim/wrapper.py               88     39     30      8    55%
src/proteus/cli.py                              82     82      8      0     0%
src/proteus/config/__init__.py                  13      0      0      0   100%
src/proteus/config/_atmos_clim.py               62      5      6      3    88%
src/proteus/config/_config.py                   33      0      0      0   100%
src/proteus/config/_converters.py               12      0      6      0   100%
src/proteus/config/_delivery.py                 28      0      0      0   100%
src/proteus/config/_escape.py                   17      0      0      0   100%
src/proteus/config/_interior.py                 28      0      0      0   100%
src/proteus/config/_orbit.py                    11      0      0      0   100%
src/proteus/config/_outgas.py                   24      0      0      0   100%
src/proteus/config/_params.py                   69      1      2      1    97%
src/proteus/config/_star.py                     21      0      0      0   100%
src/proteus/config/_struct.py                    9      0      0      0   100%
src/proteus/escape/wrapper.py                   48      3     20      3    91%
src/proteus/interior/__init__.py                 3      0      0      0   100%
src/proteus/interior/aragog.py                  86      1      8      1    98%
src/proteus/interior/dummy.py                   53      2     10      2    94%
src/proteus/interior/spider.py                 259    259     52      0     0%
src/proteus/interior/timestep.py                51      5     14      3    88%
src/proteus/interior/wrapper.py                 94     18     38      9    77%
src/proteus/orbit/__init__.py                    2      0      0      0   100%
src/proteus/orbit/wrapper.py                    11      0      0      0   100%
src/proteus/outgas/__init__.py                   3      0      0      0   100%
src/proteus/outgas/atmodeller.py                 6      6      2      0     0%
src/proteus/outgas/calliope.py                  52      7     22      5    84%
src/proteus/outgas/wrapper.py                   22      3     12      3    82%
src/proteus/plot/__init__.py                    22      0      0      0   100%
src/proteus/plot/_cpl_helpers.py                 7      0      0      0   100%
src/proteus/plot/cpl_atmosphere.py              51     10      8      3    78%
src/proteus/plot/cpl_atmosphere_cbar.py         72     55     14      2    22%
src/proteus/plot/cpl_elements.py                50      8     10      3    82%
src/proteus/plot/cpl_emission.py                86     21     16      5    71%
src/proteus/plot/cpl_escape.py                  51      9     12      5    78%
src/proteus/plot/cpl_fluxes_atmosphere.py       52      5      4      2    88%
src/proteus/plot/cpl_fluxes_global.py           55      9      6      3    80%
src/proteus/plot/cpl_global.py                 134     10     42      3    91%
src/proteus/plot/cpl_heatingrates.py            40     30      6      2    26%
src/proteus/plot/cpl_interior.py               137     35     46     13    64%
src/proteus/plot/cpl_interior_cmesh.py         124     28     44     12    71%
src/proteus/plot/cpl_observables.py             42      8      6      3    77%
src/proteus/plot/cpl_offchem_grid_cross.py     126    112     48      2     9%
src/proteus/plot/cpl_offchem_species.py         79     64     24      2    17%
src/proteus/plot/cpl_offchem_time.py            91     78     34      2    12%
src/proteus/plot/cpl_offchem_year.py            64     51     22      2    17%
src/proteus/plot/cpl_population.py             110     12     16      5    87%
src/proteus/plot/cpl_sflux.py                   96     23     28     10    73%
src/proteus/plot/cpl_sflux_cross.py             92     22     26      6    75%
src/proteus/plot/cpl_structure.py              109     19     18      5    80%
src/proteus/proteus.py                         231     57     66     12    75%
src/proteus/star/__init__.py                     2      0      0      0   100%
src/proteus/star/dummy.py                       30      0      6      2    94%
src/proteus/star/wrapper.py                    110     13     34      8    80%
src/proteus/utils/constants.py                  39      0      0      0   100%
src/proteus/utils/coupler.py                   275     23     82     19    88%
src/proteus/utils/data.py                      138     74     36      6    44%
src/proteus/utils/helper.py                    134     55     68     11    50%
src/proteus/utils/logs.py                       74     25     20      6    59%
src/proteus/utils/phys.py                       16      0      0      0   100%
src/proteus/utils/plot.py                      123     63     32      4    46%
src/proteus/utils/plot_offchem.py               85     76     32      0     8%
------------------------------------------------------------------------------
TOTAL                                         4596   1674   1154    214    60%

A lot of it is the offline chemistry stuff, which is going to be completely reworked anyway. Some of it is the AGNI wrapper, which we could address quite easily. Some of it is from the SPIDER wrapper, which would be harder to do.

Ok, I believe the offline chemistry lines will probably be touched anyway within the next few months I presume, so that seems doable. The SPIDER wrapper in itself is probably reasonable to touch, but I agree we shouldn't go overboard with this.

I agree it is important to increase the coverage but I don't think the 100% coverage is a reasonable goal. It is not required for JOSS.

It is not required, but why is it in general unreasonable? I understand that this means rigorously sorting the current code lines. But in truth, any thing below 100% will in the long run become much harder to keep up because in practice it will be difficult to keep track of where tests are missing, when many users are adding code lines.

What I mean is that 100% coverage is great but it requires a lot of effort and doesn't mean that it is bug-free because it depends on how to test things.
The mors bug is a good example, everything works fine at low time evolution and then you add one data point at a bigger time (which does not increase the coverage) and then the test fails.
Also at the moment we change the test data more or less at each PR because adding new physics/parameters change everything. We are happy because the test pass but it does not guarantee the implementation is correct.
In conclusion, I definitely agree we need to increase the coverage but it should not be the unique focus point.

I agree with @lsoucasse that 100% is an impossible target. I think that 80% is a solid and realistic target for this code base. Just think about it in this way, to achieve 100% coverage, every single branch (e.g. if statement) must be tested.
+1 on @lsoucasse point to consider is test quality. 100% test coverage does not mean 100% correctness. It just means that the code runs and does not crash.

Ok ok :) Let's have 70-80% as a continuous target then. Testing that the code does not crash is a already a massively helpful goal to achieve.


Support for IBM Z (s390x)

Is it possible to add support for IBM Z (s390x) to the binary releases of Zstd-jni? I have compiled and tested the project natively on the platform and it appears not to require any code modifications.
For the binary release it should be ok to use cross-compilation. I think the process would be very similar to that done for armhf in #117. Alternatively (or in addition) hardware access can be provided via the LinuxOne community cloud or Travis CI.
I suggest using the flag -march=z196 if possible to avoid compiling for very old versions of the machine. The major commercial Linux distributors for IBM Z (Red Hat, SuSE and Canonical) all require a z196 or newer machine for their supported distributions.
Do let me know if I can provide any assistance. I am more than happy to help with any PRs, testing etc. that is required. Thanks!

Yes, I will do it. It will take some time as I am away of my build setup for a few weeks

Thanks! Really appreciate it.

Hi @mundaym , added it through cross-compilation. Just released 1.4.5-7. Please try it.

Thanks @luben. I've tried out the library and ran into the following issue:
Unsupported OS/arch, cannot find /linux/s390x/libzstd-jni.so or load zstd-jni from system libraries. Please try building from source the jar or providing libzstd-jni in your system.
        at java.base/java.lang.ClassLoader.loadLibrary(ClassLoader.java:2670)
        at java.base/java.lang.Runtime.loadLibrary0(Runtime.java:830)
        at java.base/java.lang.System.loadLibrary(System.java:1873)
        at com.github.luben.zstd.util.Native.load(Native.java:78)
        at com.github.luben.zstd.util.Native.load(Native.java:54)
        at com.github.luben.zstd.ZstdOutputStream.<clinit>(ZstdOutputStream.java:16)

It looks like the shared object is present in the jar file but is in the folder linux/s390 (32-bit) rather than linux/s390x (64-bit). I'm currently testing the shared object manually. It looks like it was correctly compiled for s390x (64-bit) so I think that the folder just needs to be renamed linux/s390x to fix the issue.

I see, I didn't know about the correct name. Fixing it now.

Just pushed v1.4.5-9 with the correct path - it should be available on maven-central shortly

@mundaym , it's already on maven-central.

Thanks @luben, it is working now!


Scan and Label don't contain same number of points?

Hi, @benemer
Below the first picture is the result labels of 4dmos, when i use semantic-kitti-api script visualize_mos.py but get a error like the second picture, why the reason for this?

Which configuration do you use? For evaluation on SemanticKITTI, you can pass the kitti config to classify moving/non-moving for all points in the scan.
As you can see from the error message, there are less labels in your predictions than points Most likely, your max_range for mos was not set to -1 which disables the clipping and/or the min_range was not set to 0.

Thanks for your replay, below the first file the SemanticKITTI configure file which i changed it's format yaml to txt for uploading, the second file is 4dmos configure file, but i am not sure 4DMOS configure like kitti.yaml or other file is need to be modified?
semantic-kitti-mos.txt
kitti.txt

You do not need to modify the file, just pass the path to the kitti.txt (the 4DMOS config file) using the -c flag when running the pipeline.

I have get the right result in the below picture, i will close my issue, thanks for your help and appreciate your work.


other: update specs2-core from 4.12.0 to 4.12.1

Updates org.specs2:specs2-core from 4.12.0 to 4.12.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2", artifactId = "specs2-core" } ]

labels: test-library-update, semver-patch

Codecov Report

Merging #32 (e69996f) into master (7dd1615) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              master       #32   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity        29        29
===========================================
  Files              1         1
  Lines            114       114
  Branches           8         8
===========================================
  Hits             114       114

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 7dd1615...e69996f. Read the comment docs.


Provide a simple way for a local project to depend on another local project with a different scalaBinaryVersion (important for dotty/scala2 interop)

Dotty can read Scala 2 signatures (and soon the reverse will be true too), so a dotty project can depend on a scala 2 project, sbt-dotty makes this as convenient as possible by providing a withDottyCompat method to change the cross version:
libraryDependencies += ("a" %% "b" % "c").withDottyCompat(scalaVersion.value)

However, when using dependsOn to declare a local dependency between two projects, there is no way to specify the cross version, this prevents having a local dotty project that depends on a local scala2 project and vice-versa, even though this would be extremely useful for progressively porting a project to dotty.
As a workaround, one can fiddle with projectDependencies, but it's not very nice:
lazy val scala2Lib = project.in(file("scala2Lib"))
  .settings(
    scalaVersion := "2.13.1"
  )

lazy val dottyApp = project.in(file("dottyApp"))
  .dependsOn(scala2Lib)
  .settings(
    // Set withDottyCompat on the scala2Lib dependency if we had a mix of dotty
    // and scala2 dependencies, we would have to be more careful here.
    projectDependencies := {
      projectDependencies.value.map(_.withDottyCompat(scalaVersion.value))
    },
    scalaVersion := "0.21.0-RC1"
  )

@eed3si9n Was this issue addressed on the SBT side?

No action has been taken yet.

As an alternative one can set the crossVersion in the scala2Lib project:
lazy val scala2Lib = project.in(file("scala2Lib"))
  .settings(
    scalaVersion := "2.13.3",
    crossVersion := CrossVersion.constant("0.26.0-RC1")
  )

lazy val dottyApp = project.in(file("dottyApp"))
  .dependsOn(scala2Lib)
  .settings(
    scalaVersion := "0.26.0-RC1"
  )

But I am sure if it is a good idea in general.

Here's my PR for this - https://github.com/sbt/sbt/pull/5767
@adpi2 CrossVersion.constant("0.26.0-RC1") may use _0.26.0-RC1 as opposed to the normal binary suffix?

CrossVersion.constant("0.26.0-RC1") may use _0.26.0-RC1 as opposed to the normal binary suffix?

Here the scala2lib is only compiled to the scala2lib\target\scala-2.13 directory. My understanding is that the CrossVersion.constant("0.26.0-RC1") tells sbt that the project can be consumed by a 0.26.0-RC1 project. It does not change the binary version of neither the dependency nor the dependent project.
It works as well if I write CrossVersion.constant("0.26").


help,there is throw a mistake.

2017-03-31T07:41:10.167Z	6835cdb1-15e5-11e7-ae5d-7dd945e4dd5c	TypeError: Cannot read property 'key' of undefined
at exports.handler.S3.getObject.promise.then.then (/var/task/index.js:9:40)

Same problem! Have no idea what is going wrong.

Hmm - are you running it through an API Gateway Lambda proxy? It appears like the query string parameters are not defined.

In my case i made a mistake setting URL environment variable. So setting url from endpoint static website hosting fixed problem.

@imamatory Glad you figured it out! @hare2011 Please let me know a little more about how you're running the function and definitely double check your environment variables.

there is my config

@hare2011 When I hit your endpoint, it appears to be working for me. Hitting:
http://images-vamily.s3.amazonaws.com/
I can see an index of all images in your bucket. When I hit them, I can resize them. See:
http://images-vamily.s3-website-us-west-2.amazonaws.com/500x500/4.jpg
http://images-vamily.s3-website-us-west-2.amazonaws.com/300x300/4.jpg

why i access this url throw mistake.
https://0ty0msuku6.execute-api.us-west-2.amazonaws.com/prod/resize?key=300×300/5.png

great. thank you much very.

Because the x in there is some Unicode "x" and not an actual ASCII x as the sample code is attempting to match via a regular expression. See:
http://images-vamily.s3-website-us-west-2.amazonaws.com/300x300/5.png

so bad . i copy the 'x' from the web page.  @jpignata  thank you for you help.

there is problem for me .i watch the lambda log .i access the images .the log will add record.

@hare2011 Sorry, I don't follow.


guessSortFn throws error, getSortFn expects null return

Within the rowSorter, the getSortFn expects the guessSortFn to return null if it couldn't guess the correct sort function. Instead it throws an exception. Either guessSortFn should return a default function or the call should be wrapped in a try catch.
Without this, one can't specify a custom colDef.type without breaking sorting.

colDef.type is a value that the grid uses, I'm not sure you can just invent new types and expect things to work.  Is there a reason you cannot use a different field for type - perhaps colDef.myType or something?

Perhaps I'm confused...
"type
the type of the column, used in sorting. If not provided then the grid will guess the type. Add this only if the grid guessing is not to your satisfaction. Refer to gridUtil.guessType for a list of values the grid knows about"
Reading it again, I can interpret it to say type may be provided as long as it is one of the supported types. A list of the supported types would be of great help. I'll change my implementation to add a new property type for what I was doing and key off of that instead.
I was setting the type to be "select" for use when performing an edit.


Hide passwords if overridden value is used as placeholder

1. Why is this change necessary?
A password can be exposed without the intention when specifying the sales channel to configure  a password for.
2. What does this change do, exactly?
Add a property for password fields to expect placeholders be passwords as well and thus can be made visible like the value itself.

3. Describe each step to reproduce the issue or behaviour.

4. Checklist

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

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

Hi @JoshuaBehrens
thank you again for your contribution 🎉
Your PR was merged to 6.2
Best regards
Timo

You're all welcome at @shopwareBot 💜 💙 🎉


Find alternative to port mapping RPC on k8s

Right now to connect to the RPC on k8s you have to port map from your cluster to local 9276 which is what warcli is expecting.
This does not feel very elegant, we should investigate an alternative. Perhaps use ingress / loadbalancer or a tunneling project that could be integrated into the cli tool?

This is now not an issue, but I opened #587 to track adding ingress.
Going to close this one


dotnet restore for f# missing reference

#Hi,
I tried to create a F# project on Mac OsX Yosemite with the latest .Net Core.

NET Command Line Tools (1.0.0-beta-001598)
Product Information:
Version:     1.0.0-beta-001598
Commit Sha:  7582649f88
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.11
OS Platform: Darwin
Runtime Id:  osx.10.11-x64

The creation works fine, but when I tried to run the restore, I'm getting everytime an error:

NotFound https://myget-2e16.kxcdn.com/artifacts/fsharp-daily/nuget/v3/flatcontainer/microsoft.netcore.platforms/index.json

This is the verbose log of the restore command:og  : Restoring packages for

/Users/palutz/Projects/fsharp/dotnetcore01/project.json...
info :   CACHE https://dotnetmyget.blob.core.windows.net/artifacts/dotnet-core/nuget/v3/flatcontainer/microsoft.netcore.platforms/index.json
info :   CACHE https://api.nuget.org/v3-flatcontainer/microsoft.netcore.platforms/index.json
info :   GET https://myget-2e16.kxcdn.com/artifacts/fsharp-daily/nuget/v3/flatcontainer/microsoft.netcore.platforms/index.json
info :   NotFound https://myget-2e16.kxcdn.com/artifacts/fsharp-daily/nuget/v3/flatcontainer/microsoft.netcore.platforms/index.json 595ms
info : Committing restore...
log  : Restore completed in 1577ms.
NuGet Config files used:
/Users/palutz/Projects/fsharp/dotnetcore01/NuGet.Config
/Users/palutz/.nuget/NuGet/NuGet.Config
Feeds used:
https://dotnet.myget.org/F/dotnet-core/api/v3/index.json
https://api.nuget.org/v3/index.json
https://www.myget.org/F/fsharp-daily/api/v3/index.json

I don't know if this is the reason why also the compile (run) is not working after.
Regards,
Stefano

Your version of the CLI is quite old. It should work with a new one from here: https://github.com/dotnet/cli

This is the version provided with the "official package" got directly from the "Getting started" page on the official site.
https://dotnet.github.io/getting-started/#/macosx
Which one is the latest version and how can I get it, pls?

The Readme.md on the cli github repo should be fine. The current os x link is: https://dotnetcli.blob.core.windows.net/dotnet/beta/Installers/Latest/dotnet-dev-osx-x64.latest.pkg

The result is exactly the same. Didn't change anything and didn't update anything, at least with the version number (maybe it wasn't updated).
Which version do you have on your Mac?

You'll need to remove the old one before.. it's a known bug with the installer (location of the dotnet executable was changed and an entries in /etc/paths.d/dotnet are not removed). If you installed globally (default afaik), you can sudo rm -rf /usr/local/share/dotnet and run the installer again.

I actually did it.
Anyhow, installing the new (just released) version solved all.
I used the uninstall script provided and the new installer.
Now the F# project is compiling and running.
Nice!


Update pubsub mqtt document to include TLS options

Update MQTT as a Dapr pubsub component to include TLS options.
In addition to the existing options:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: <name>
spec:
  type: pubsub.mqtt
  metadata:
  - name: url
    value: 'tcp://[username][:password]@host.domain[:port]'
  - name: qos
    value: ''
  - name: retain
    value: ''
  - name: cleanSession
    value: ''

Update additional new TLS options:
  metadata:
  - name: url
    value: 'tcps://host.domain[:port]'
  - name: caCert
    value: ''
  - name: clientCert
    value: ''
  - name: clientKey
    value: ''

Where:
caCert (required for using TLS) is the certificate authority certificate.
clientCert (required for using TLS) is the client certificate.
clientKey (required for using TLS) is the client key.
url scheme (required for supporting TLS) should be updated from ~tcp://~ to tcps://

https://github.com/dapr/components-contrib/issues/357


Dependency-Check-plugin failing while updating NVD

Hello Team,
I am just upgraded Dependency-Check-plugin to version 9.2.0. as per recommended without an NVD API key as it not compulsory. With updated verification
when tried on local environment it run sucessfully. Download and updated all NVD. But when i am trying it same config on Jenkins it failing there while at start only with below exception of 403/404.
Why is this difference?
Environment: maven
Config set for Dependency-Check-plugin

org.owasp
Dependency-Check-plugin
9.2.0
false

org.owasp
Dependency-Check-plugin
9.2.0

 false
false
0

....

Two things - you must upgrade to 10.0.0+ due to changes at the NVD.

See #6758


feat: add master_instance_name and instance_type to mysql module

Relates to my feature request: https://github.com/terraform-google-modules/terraform-google-sql-db/issues/554
fix #554

@OscarVanL thx for the PR. We already have replica code where these parameters are passed. That specific code is for Master instance. Replica code is here.
https://github.com/terraform-google-modules/terraform-google-sql-db/blob/master/modules/mysql/read_replica.tf

@OscarVanL thx for the PR. We already have replica code where these parameters are passed. That specific code is for Master instance. Replica code is here.
https://github.com/terraform-google-modules/terraform-google-sql-db/blob/master/modules/mysql/read_replica.tf

Hi @imrannayer
I think it would help for me to elaborate on the use-case I described in the feature request more so you have more context.
I want to create a CloudSQL instance that replicates from my on-prem MySQL instance that will at a later stage become the master.
To start with, I want to create some cascading replicas from my on-prem database in CloudSQL. The instance I changed (which currently can only act as the master) will begin as the "root" replica. In the diagram below it is the root replica:

Initially, there will be no master in CloudSQL, only replicas on-prem.
Eventually once I'm ready, the "root" CloudSQL instance will be promoted to the master instance and my on-premises DB will be shut down.
I hope this gives some clarity on why I want the resource I edited to act as a replica.

/gcbrun

@imrannayer Hey, apologies I found a mistake in this PR. Please hold the release of 18.2.0.
I should also prevent backups being created for the replica instance. I will make a follow-up PR shortly.


Some questions about the code

in LocalGrouper.forward
std = torch.std((grouped_points-mean).reshape(B,-1),dim=-1,keepdim=True).unsqueeze(dim=-1).unsqueeze(dim=-1)

It would seem not consistent with standard deviation of local k neighborhood points in the paper?

@OuyangJunyuan  Previously, there is a bug for calculating the std. Please refer the updated arXiv version (https://arxiv.org/abs/2202.07123).

@ma-xu  and i also find some file lacked in part_segmentation.main.py from util.data_util import PartNormalDataset

@OuyangJunyuan Thanks for your kind remind. I will doubel check this part after Mar/10.

@OuyangJunyuan
Thanks for your interest. I just double-checked: mistakenly uploaded the wrong folder in experiments.
Our development codes are based on PAConv, GDANet(yes), and Curevenet. We tried several implementations; as a result, we uploaded the wrong folder. You can see it in my pointsmlp repo, which is our development repo.
It is fixed now. Please have a try and let me know if there are still any issues.

@OuyangJunyuan Thanks for your interest. I just double-checked: mistakenly uploaded the wrong folder in experiments. Our development codes are based on PAConv, GDANet(yes), and Curevenet. We tried several implementations; as a result, we uploaded the wrong folder. You can see it in my pointsmlp repo, which is our development repo. It is fixed now. Please have a try and let me know if there are still any issues.

many thanks!


Grammar fixes, typos etc.

📝

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: IonicaBizau sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Missing reversed params comparison ops for C++17

C++17 needs additional comparison operator overloads with reversed parameters. For C++20 and newer it is unnecessary due to "synthesized three-way comparison" feature.

The comparison operators of expected have not yet be adopt in STL,, refered in P0323R12 .
To avoid the possibly incompatible behaviour with STL, it's not perferred to implement this feature right now.
Free free to tell me if someday it comes :)

I don't understand. The comparison ops for std::expected are available since the beginning, see:
https://wg21.link/std23
Chapter:
<IP_ADDRESS> Equality operators

Hi, @mcencora
Equality is not all of the comparison. To acheive equality, we need only two functions, the operator== and operator!=, but six (plus operator<, operator>, operator<= and operator>=) for comparison.
As what you post,

https://wg21.link/std23
Chapter:
<IP_ADDRESS> Equality operators

it only define three overloads of operator==. So this is the thing of equality, and zeus::expected has reached that.

You are missing the point, I am talking here about support for C++17, and to achieve (non-)equality we need in 12 overloads in total.
These are defined in spec (for non-void T):
operator==(expected, expected<T2, E2>)
operator==(expected, T2)
operator==(expected, unexpected)
So for C++17 you need additionally following:
reversed param order:
operator==(expected<T2, E2>, expected)
operator==(T2, expected)
operator==(unexpected, expected)
not-equal:
operator!=(expected, expected<T2, E2>)
operator!=(expected, T2)
operator!=(expected, unexpected)
not-equal reversed param order:
operator!=(expected<T2, E2>, expected)
operator!=(T2, expected)
operator!=(unexpected, expected)


[Bug] fluentbit sidecar breaks with SOCI index

Description
Hi,
I was reading the blog post about SOCI and was really excited and wanted to give it a try.
Basically I have a AWS ECS task with two containers defined. One is my application (corretto + spring boot app) and one is a fluentbit sidecar for AWS Firelens log shipping.
The fluentbit docker image is built by
FROM fluent/fluent-bit:2.0.11

ADD fluent-bit.conf /fluent-bit/alt/fluent-bit.conf
ADD level-filters.conf /fluent-bit/alt/level-filters.conf

CMD ["/fluent-bit/bin/fluent-bit", "-c", "/fluent-bit/alt/fluent-bit.conf"]

It works pretty well without a SOCI index.
Then I deployed the partner solution and took the same image (tag+digest) for my app container and the sidecar one, retagged it with a "soci" prefix.
While deploying the new image tags for my service the fluentbit sidecar container dies with the following message:
[error] configuration file contains errors, aborting.
[warn] [config] Read twice. path=/fluent-bit/alt/level-filters.conf

Keep in mind the same image (digest) was used, no changes to the software/config included just lazy loaded via SOCI.
Im not quite sure if this is an issue with the fluentbit code or SOCI lazy loading within ECS/Fargate.
The reduction we saw (started vs created datetime) was really really nice (like 2 min vs 30s) and I would love to integrate it :)
Steps to reproduce the bug
No response
Describe the results you expected
I would expect that the integration is somehow transparent and would not affect any kind of file operations from whatever runs inside the container. If this is not the case we cannot really integrate it.
Host information
Runtime: AWS Fargate ECS 1.4
SOCI index creation via this solution https://aws-ia.github.io/cfn-ecr-aws-soci-index-builder/ deployed today (26.7)
Any additional context or information about the bug
No response

Thanks for the report. We are going to try to reproduce this behavior with default/empty fluentbit configs and a base coretto image, but it would be helpful if you could provide a dockerfile for coretto plus a minimum test case app, and your config files, so we can get closer to the situation you're encountering.

Thanks for your answer @sparr . A real repro repo will take some time but I hope this helps too.
We use a task def like this:
TaskDefinition:
  Type: AWS::ECS::TaskDefinition
  Properties:
    Memory: !Ref MemoryLimit
    Cpu: !Ref CpuLimit
    NetworkMode: awsvpc
    RequiresCompatibilities:
      - FARGATE
    ExecutionRoleArn: !Ref ExecutionRoleArn
    TaskRoleArn: !Ref TaskRoleArn
    ContainerDefinitions:
      - Name: app
        Image: my-ecr-image-with-soci-index
        LogConfiguration:
          LogDriver: awsfirelens
        PortMappings:
          - ContainerPort: 8080
      - Name: log-router
        Image: my-fluentbit-image-with-soci-index
        Essential: true
        FirelensConfiguration:
          Type: fluentbit
          Options:
            enable-ecs-log-metadata: 'true'
        Environment:
          - Name: LOKI_HOST
            Value: my-loki-instance
          - Name: LOKI_PORT
            Value: 3000
          - Name: SERVICE
            Value: my-service
        Secrets:
          - Name: TENANT_ID
            ValueFrom: my-tentant-id-from-parameter-store
        LogConfiguration:
          LogDriver: awslogs
          Options:
            awslogs-stream-prefix: firelens
            awslogs-group: !Ref AWS::StackName
            awslogs-create-group: 'true'
            awslogs-region: !Ref AWS::Region

And these are the 2 config files:

fluent-bit.conf
[SERVICE]
    Parsers_File /fluent-bit/etc/parsers.conf
    flush                     1
    # default stopTimeout of ecs is also 30s, could be increased up to 120s but this has to be done in the task definition as well
    grace                     30
    storage.path              /tmp/flb-storage/input
    storage.sync              normal
    storage.checksum          off
    storage.backlog.mem_limit 5M
    # 25 * 2mb (usual chunk size) = 50m memory, more or less the same amount is additionally needed as soon as the output is healthy again and we ingest and output logs at the same time
    storage.max_chunks_up     25

[INPUT]
    Name forward
    unix_path /var/run/fluent.sock
    storage.type filesystem

# drop source if available, this will be always stdout/stderr on ECS/firelens
[FILTER]
    Name modify
    Match *
    Remove source

# parse json from `log` and lift its key/value
[FILTER]
    Name parser
    Match app-firelens*
    Key_Name log
    Parser json
    Reserve_Data true

# if the logs originate from a container named `app` we add the source if its not present (services send a source `app`, only stdout logs from supervisor&co will get `console`)
[FILTER]
    Name modify
    Match app-firelens*
    Condition Key_does_not_exist source
    Add source console

# if the logs originate from a container named `otel` we add otel as source
[FILTER]
    Name modify
    Match otel-firelens*
    Add source otel

# otherwise its unknown
[FILTER]
    Name modify
    Match *
    Condition Key_does_not_exist source
    Add source unknown

# map log levels to old behaviour
@INCLUDE /fluent-bit/alt/level-filters.conf

# off to loki :)
[OUTPUT]
    Name loki
    Match *
    # we retry until the end of time with an exponential backoff
    Retry_Limit no_limits
    host ${LOKI_HOST}
    port ${LOKI_PORT}
    tenant_id ${TENANT_ID}
    line_format json
    labels $source, $container_id, service=${SERVICE}
    remove_keys ecs_task_arn,ecs_task_definition,source,ecs_cluster,container_name
    tls on
    # we store up to 1G of logs on disk, afterwards old entries will be removed
    storage.total_limit_size 1G

level-filters.conf
[FILTER]
    Name modify
    Match app-firelens*
    Condition Key_value_equals level TRACE
    Remove level
    Add level trace

[FILTER]
    Name modify
    Match app-firelens*
    Condition Key_value_equals level DEBUG
    Remove level
    Add level debug

[FILTER]
    Name modify
    Match app-firelens*
    Condition Key_value_equals level INFO
    Remove level
    Add level info

[FILTER]
    Name modify
    Match app-firelens*
    Condition Key_value_equals level WARN
    Remove level
    Add level warn

[FILTER]
    Name modify
    Match app-firelens*
    Condition Key_value_equals level ERROR
    Remove level
    Add level error

It doenst really matter what your "app" container actually is because in our current setup the essential container (called log-router) does not start at all and the task dies.

Were you able to reproduce your issue on multiple task launches? It would be helpful to know if we're looking for a consistent failure or a transient one.

Yes it happened 8 out of 8 attempts.

I'm not able to reproduce this. I used your Dockerfile and config files and deployed with the following task definition:
{
    "family": "fluentbit",
    "containerDefinitions": [
        {
            "name": "log-router",
            "image": "fluent-bit-image-with-soci-index",
            "cpu": 0,
            "portMappings": [],
            "essential": true,
            "environment": [
                {
                    "name": "LOKI_HOST",
                    "value": "localhost"
                },
                {
                    "name": "TENANT_ID",
                    "value": "tenant"
                },
                {
                    "name": "SERVICE",
                    "value": "my-service"
                },
                {
                    "name": "LOKI_PORT",
                    "value": "3000"
                }
            ],
            "mountPoints": [],
            "volumesFrom": [],
            "logConfiguration": {
                "logDriver": "awslogs",
                "options": {
                    "awslogs-create-group": "true",
                    "awslogs-group": "fluentbit",
                    "awslogs-region": "us-west-2",
                    "awslogs-stream-prefix": "fluentbit"
                }
            }
        }
    ],
    "executionRoleArn": "execution-role-arn",
    "networkMode": "awsvpc",
    "requiresCompatibilities": [
        "FARGATE"
    ],
    "cpu": "1024",
    "memory": "3072"
}

I'm seeing everything start up correctly:
[ info] [sp] stream processor started

Just a spot check - can you still reproduce it by deploying your task again?

Yes its still happening. Tried the old images and also some fresh built ones.
This is the output of the fluentbit container

which basically leads to

I think the only real differences are firelens, a second container and eu-central-1 region

To be sure, I tried again in eu-central-1 and I'm still seeing the container start up correctly:
Fluent Bit v2.0.11
* Copyright (C) 2015-2022 The Fluent Bit Authors
* Fluent Bit is a CNCF sub-project under the umbrella of Fluentd
* https://fluentbit.io
[2023/08/04 16:59:07] [ info] [fluent bit] version=2.0.11, commit=bf22d53a69, pid=1
[2023/08/04 16:59:07] [ info] [storage] created root path /tmp/flb-storage/input
[2023/08/04 16:59:07] [ info] [storage] ver=1.4.0, type=memory+filesystem, sync=normal, checksum=off, max_chunks_up=25
[2023/08/04 16:59:07] [ info] [storage] backlog input plugin: storage_backlog.1
[2023/08/04 16:59:07] [ info] [cmetrics] version=0.6.0
[2023/08/04 16:59:07] [ info] [ctraces ] version=0.3.0
[2023/08/04 16:59:07] [ info] [input:forward:forward.0] initializing
[2023/08/04 16:59:07] [ info] [input:forward:forward.0] storage_strategy='filesystem' (memory + filesystem)
[2023/08/04 16:59:07] [ info] [input:forward:forward.0] listening on unix:///var/run/fluent.sock
[2023/08/04 16:59:07] [ info] [input:storage_backlog:storage_backlog.1] initializing
[2023/08/04 16:59:07] [ info] [input:storage_backlog:storage_backlog.1] storage_strategy='memory' (memory only)
[2023/08/04 16:59:07] [ info] [input:storage_backlog:storage_backlog.1] queue memory limit: 4.8M
[2023/08/04 16:59:07] [ info] [output:loki:loki.0] configured, hostname=localhost:3000
[2023/08/04 16:59:07] [ info] [sp] stream processor started

It's possible there's something about having 2 containers in the task definition that's changing things. I'll give that a shot as well.
If possible, could you share the SOCI index? We don't have great tooling for that right now. The easiest way is probably to share the ECR repository. I'll see if I can get a script or something for that.
To confirm: You were previously using this exact same fluentbit image successfully. You retagged it and pushed it (to a different ECR repository?). Then you updated your task definition (or created a new one) referencing the new tags. Is that correct? No docker build step in there, right?

Yes thats correct.
However, my first attempt was like: let the CI build a new version of the images, push to ECR, wait for Lambda to create SOCI index and deploy. This resulted in this strange error. Afterwards I re-used older working images, retagged and pushed them to ECR as well. Every time the same two ECR repos (app&sidecar one) but result was the same.
Out of curiosity: do you create the SOCI index via CLI or lambda?

I'm using the lambda. I tried both from the us-east-1 bucket that is referenced in the documentation and the eu-central-1 local bucket.
Were your images built with docker? There are a lot of ways to end up with non-reproducible builds, but the image digest I got out of your dockerfile + configs was sha256:52087906566349bba942a74abb33a1d901bb7969ce9cde82525829ce42781b77 in case there's a chance we ended up producing the bit-for-bit equivalent images.
Can you confirm that the image that you re-pushed was from that exact dockerfile? You weren't using an older version of fluentbit?

Unfortunately its not the same digest but yes I used them same fluentbit version (2.0.11) in the old and in the new image because its the first one where back pressure handling after an unhealthy output properly worked.
Images are build by docker v20 (client+daemon).


Rewrite the custom upload logic.

The sole purpose of the crypto-js library is our custom upload logic. Try to rewrite it using @rails/activesupport package. This needs to be added to peer dependencies.
Part of https://github.com/bigbinary/neeto-editor/issues/1123
@deepakjosp  _a

This is implemented as part of the ticket - https://github.com/bigbinary/neeto-editor/issues/1126.
Closing the issue.
cc: @AbhayVAshokan


Praise

Praise: @AbdallahHemdan  Great job ✨🎉
It's so useful for me and I was waiting for something like that for a long time

@abdallahabusedo Thanks a lot for your feedback ❤


I don't know how to use Python. How do I make this work?

What is the purpose of your issue?

[ ] Bug
[ ] Feature Request
[x] Question
[ ] Other

Description
I already installed the Spotify Downloader into Python 3.8, but the problem is, I have no idea what I'm doing. I don't know how to use Python. When I try to copy and paste the commands from the instructions, I get a syntax error and I'm unable to go ahead. How exactly am I supposed to type each command?

You should not copy the $ symbol. The $ is the beginning of a command when you use a terminal like the Linux one. If you use python directly just write:
spotdl --song ecc

Thank you so much!
What about quotation marks, though? There's a syntax error for those (I'm using Windows 10 mind you)

Thank you so much!
What about quotation marks, though? There's a syntax error for those (I'm using Windows 10 mind you)

You don't need to run it in python shell

@Teslahaha As @Alessiocc mentioned you need to run the command directly in your command-prompt (and not in the python interpreter as in your screenshot) without the "$" symbol. The "$" symbol simply exists as a convention to indicate the command is to be run in a shell (command-prompt in your case).


return all errors from RESTStorage registration

If there is an error while registering RESTStorage for any resource only the first error is returned.  This change makes sure that the error is reported to the caller, but error messages are provided for every failing type.

LGTM
Sent from my iPhone

On Jan 28, 2015, at 8:30 AM, David Eads<EMAIL_ADDRESS>wrote:
If there is an error while registering RESTStorage for any resource, no resource gets registered. This change makes sure that the error is reported to the caller, but registration for all correct resources succeeds and error messages are provided for every failing type.
You can view, comment on, or merge this pull request online at:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3867
Commit Summary
allow partial RESTStorage registration
File Changes
M pkg/apiserver/apiserver.go (9)
Patch Links:
https://github.com/GoogleCloudPlatform/kubernetes/pull/3867.patch
https://github.com/GoogleCloudPlatform/kubernetes/pull/3867.diff
—
Reply to this email directly or view it on GitHub.

If a resource can't get registered... Why does the server continue starting up?  Why is this necessary?  Just debugging?

Allowing most of the application to come up and continue working seems to be a better option than completely disabling it.  This is already accepted in concept, since we allow start up to continue even in cases where the app doesn't have the rights to modify iptables rules.  Services will not function properly without those rights, but it is more useful to allow start up with hobbled functionality than to not start up at all.  I view this as a similar situation, functionality may be hobbled by missing resource availability, but it's generally more useful to have something working than nothing.
The caller can still decide to fall over if they want to, but they are no longer forced to fail hard.

Looked to me it still fails to start, just lets you get the full list of errors instead of doing whack a mole.
Sent from my iPhone

On Jan 28, 2015, at 9:11 AM, Clayton Coleman<EMAIL_ADDRESS>wrote:
If a resource can't get registered... Why does the server continue starting up? Why is this necessary? Just debugging?
—
Reply to this email directly or view it on GitHub.

/cc @jwhonce @markturansky

I want app to fail, but give aggregate error.
Sent from my iPhone

On Jan 28, 2015, at 9:18 AM, David Eads<EMAIL_ADDRESS>wrote:
Allowing most of the application to come up and continue working seems to be a better option than completely disabling it. This is already accepted in concept, since we allow start up to continue even in cases where the app doesn't have the rights to modify iptables rules. Services will not function properly without those rights, but it is more useful to allow start up with hobbled functionality than to not start up at all. I view this as a similar situation, functionality may be hobbled by missing resource availability, but it's generally more useful to have something working than nothing.
The caller can still decide to fall over if they want to, but they are no longer forced to fail hard.
—
Reply to this email directly or view it on GitHub.

I want app to fail, but give aggregate error.

That's what kubernetes does https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/master/master.go#L372.  By not failing until after the container.add call in InstallREST, callers now have a choice: detect the error and fail or detect the error and continue hobbled.

There is no case I can imagine in which I want the service to start up with partial RESTStorage.  That's a critical prod hole waiting to happen.  But I'm fine with aggregate error (use []error and return errors.NewAggregate).

On Jan 28, 2015, at 9:22 AM, David Eads<EMAIL_ADDRESS>wrote:
I want app to fail, but give aggregate error.
That's what kubernetes does https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/master/master.go#L372. By not failing until after the container.add call in InstallREST, callers now have a choice: detect the error and fail or detect the error and continue hobbled.
—
Reply to this email directly or view it on GitHub.

Renamed the commit and the pull request to more accurately describe what it does

LGTM


Not working on Codepen.io

When I downloaded the framework and began to experiment with the functions and API, I was unable to modify the div I created, even though I used the correct syntax. I attempted to call the script through this pen: http://codepen.io/juliangarnier/pen/4032af61ca0478304ab7b31b70a44804. Unfortunately, while CodePen recognized the syntax, it would not execute the animation.

.waden {
height: 200px;
width: 200px;
background: #000000
}
var myAnimation = anime({
target: '.waden',
translateX: '16px',
rotate: 360,
borderRadius: '8px',
duration: 2000,
loop: true,
`

You must load anime.js before executing anime({}).

That's what I did, in the HTML section of Codepen. It still would not register the animation, even though I linked it as such:

:(

You have 'target' instead of 'targets'
http://codepen.io/hotmilo23/pen/YWVAkd?editors=1111

@lukebatchelor Unfortunately, I set the up the script like you showed me, yet it still won't work. Here's a link to what's going on:

The script tag you have there would only work if you had the file saved and being delivered on the same domain you are on. You need it to point to a server that is serving that file.
 for example.
That pulls the script directly from this repo.
In codepen you can also put dependencies under settings -> JavaScript.
.
Instead of pointing to gihub, you could point at the pen you posted earler too.
http://codepen.io/juliangarnier/pen/4032af61ca0478304ab7b31b70a44804.
Hope that helps

Awesome! Thanks, Luke! I'll try and see if it works in the morning. :D
On Jul 1, 2016 12:48 AM, "lukebatchelor"<EMAIL_ADDRESS>wrote:
The script tag you have there would only work if you had the file saved and
being delivered on the same domain you are on. You need it to point to a
server that is serving that file.
 for example.
That pulls the script directly from this repo.
In codepen you can also put dependencies under settings -> JavaScript.
https://camo.githubusercontent.com/8f277e738bfb34601a47d68a6ef707b33efe36cf/687474703a2f2f692e696d6775722e636f6d2f73414d366c36462e706e67
.
Instead of pointing to gihub, you could point at the pen you posted earler
too.
http://codepen.io/juliangarnier/pen/4032af61ca0478304ab7b31b70a44804.
Hope that helps
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/juliangarnier/anime/issues/19#issuecomment-229853042,
or mute the thread
https://github.com/notifications/unsubscribe/ARH6TLecR4NHFNz5fhSNMm-qLIOIYtzaks5qRJwCgaJpZM4JB4rr
.

@lukebatchelor @juliangarnier Thank you both so very much for helping. It worked when I changed the source of the script to:

I'll be sure to start using this framework more often, and if possible, I'd like to start contributing to this repository. :D


Make relTargetPathBase an exported field

I've been trying to "solve" the issue of surfacing images inside nested subfolders in section lists, and would love to have access to .relTargetPathBase inside a layout template to rebuild image URLs.
That way I could have a post listing that did something like this:
 {{ if eq .Section "photos" }}
   <!-- Take .Content and try to reformat img src -->
{{ else }}
    {{ .Summary }}
{{ end }]

This is because right now it appears to be impossible to have Hugo automatically rewrite SRC paths when you have a nested folder structure, even though I've been investigating the forums and issues for workarounds (I'm trying to move across a site with around 3000 image assets that are inside a year/month/day folder hierarchy, and are referenced locally in the index.md files -- individual posts render fine, but building a list view that shows images correctly is apparently impossible)

Bump to keep this as a feature request with the original rationale.

On 19 Nov 2018, at 20:19, stale[bot]<EMAIL_ADDRESS>wrote:
This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

 I don't understand it from the description above.

I can try to build a (non-working) example, but it’s probably best to explain the scenario:
I have a post-by-folder setup with images alongside markup, and I would like to be able to build a section index (a month or a year) with the title and hero image of each post.
Right now there is no way to do that using relative paths inside a layout template.


Fix Cohen kappa

fix issue, https://github.com/tensorflow/addons/issues/1821
See code: https://colab.research.google.com/drive/1rLIKY0Y8VkzdsP71vUNvjIM-_XlJ_RZU?usp=sharing

@aakashkumarnain
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.

Thanks @autoih for fixing this. I don't know how it got slipped in the docs. Thanks again.


Project Description isn't shown anywhere

v0.22.1-rc2
Steps to Reproduce:

Create a project with a description.

Result: Can't find anywhere that displays the project's description.
Either remove the option of being able to add a description to a project or find a place to show the project description.

Dupe of https://github.com/rancherio/rancher/issues/555


Regenerates CSS

Runs grunt to regenerate CSS.

Will be updated in https://github.com/cfpb/cfgov-refresh/pull/327


--local should not be the default for worker starter templates

local mode should not be the default for developing workers, since the behaviour is different from our actual runtime.

Is this still the case @JacobMGEvans? We are in the process of moving over the templates to workers-sdk monorepo: https://github.com/cloudflare/workers-sdk/tree/main/templates
I'll be closing this for now, and I'll recreate this in the new home for templates if this is still required.


Added name and pdf link to the syllabus and papers directory (5b discussion leader)

This is a huge PR that includes some great things including the renaming of papers (that must have taken so long!!!). However, there are a few things that I'd like to see changed: I believe that renaming some of the papers will break links on the syllabus. The links need to be updated. I also really don't like spaces in file names.  The "2a - blah.pdf" naming scheme should be "2a-blah.pdf". I know it is a huge pain, but would it be possible to make this change? A strategic sed/awk script might automate the change.

Oops, I actually did not mean to include the renamed papers in this PR! I had initially included this naming scheme into my local repo to better help my eyes. I can definitely revert this to the original version, unless you'd like to keep the "1a", "2a" names without the spaces and have the current links on the syllabus updated. Either change would not be a problem for me to make. Would you prefer the first or latter option? @gparmer

I really like your change. Adding the "2a-x.pdf" is great. If you have the time and are willing to remove the spaces, that would be amazing. That said, if you don't have the time, that's fine. In that case, you can just PR the addition of the links.
In short, I'd prefer the latter, but would understand if you don't have time to do the rename.

Hi Gabe, I've updated the PR to include the new naming scheme with no white spaces, and also updated the existing links to the papers in the syllabus and papers directory. The links in the syllabus currently break on my forked repo because the newer naming scheme does not yet exist in the collaboration repo (i.e. references github.com/gwu-iot/... rather than github.com/rachellkm/...), but it should work once everything gets merged in. @gparmer

Brilliant, Thanks!


Basic housekeeping on device error handling

Resets the error type in the appropriate places to prevent unintended behaviour when two errors occur in a row, also removed the error info field as it's no longer used and a useful enough procedure name is already given in the builtin error messages. Also renames some things to better reflect how they are now used.
I'm thinking of changing some stuff with the request adapter and device error handling to make it more consistent with device errors next. But this PR should be safe to merge as is.

I'm thinking of maybe making the get_error_message thing global to all error messages and then using that instead having the print calls in the request procedure, that way the API has a consistent way of getting the error message on error for all places where errors happen.