text:
Deploy & publish model

Issue
https://github.com/gravitee-io/issues/issues/6433
Description
Select a deployment mode and deploy the model:

Documented API: the created API will be created in APIM with a Swagger documentation
Mocked API: the create API will be created with a Swagger documentation, the Mock policy will be configured on all flows and the API will be started on the Gateway
Published API: the create API will be created with a Swagger documentation, with the Mock policy configured, started on the Gateway and it will be published on the Portal.

Additional context
Related to https://github.com/gravitee-io/gravitee-cockpit/pull/1319

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.

Gravitee.io Automatic Deployment
📚 View the storybook of this branch here

Gravitee.io Automatic Deployment
Congrats, all the CI steps were 🟢 . The Bot was able to deploy the build of this PR, so you can now try it directly here! 🚀
Notes: The deployed app is linked to the management API of the Element Zero team's environment.

authors: graviteeio jgiovaresco

repo: gravitee-io/gravitee-api-management


text:
feat: udpate all colors with perseverance

APIM-102
Issue

🚀 CI was able to deploy the build of this PR, so you can now try it directly here
Notes: The deployed app is linked to the management API of APIM master. (Same login and password as APIM master)

📚  View the storybook of this branch here

Closing in favor of https://github.com/gravitee-io/gravitee-api-management/pull/2606

source: gharchive/pull-request

authors: gaetanmaisse gcusnieux

license_type: permissive

license_source: github-api


text:
feat: create transform status code policy

Issue
https://gravitee.atlassian.net/browse/APIM-5451
Description
As an API publisher
I want to transform the status code sent from the upstream service from one HTTP status to another
so that I can send a response that I want to the client if I can’t change the upstream response.
Additional context

https://github.com/user-attachments/assets/f142bde2-1612-41ac-97dc-52a9d5e0c7ae

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 1.0.0
download it from Artifactory here

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on:

1.0.0-alpha.1
GitHub release

Your semantic-release bot :package::rocket:


text:
Install KSM CLI on Alpine using the new binary

KSM team has built a binary for Alpine: https://github.com/Keeper-Security/secrets-manager/issues/239

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/gravitee-io/keeper?version=dev:9286bcc3dd03d8b9ba6805981040927dc046d0a6

repo: gravitee-io/keeper-circleci-orb

license: MIT


text:
(1c) Preliminary analysis/semantic tagging of data elements

(1c) Preliminary analysis and semantic tagging of data elements definitions complete   [@frostyfan109]

This work involves attempting different strategies to tag each data dictionary data element with appropriate keywords to characterize the element. The idea is that by reducing the element to a non-trivial number of keywords, it may be easier to find elements that are similar.

See also https://github.com/frostyfan109/cde-harmonization/issues/3 for more detailed considerations for this activity.

source: gharchive/issue

repo: graybeal/radx-data-dictionary-analysis


text:
Fix a syntax error in the types definition file on TypeScript 3.9.3

This file was throwing a TypeScript syntax error when being required:
  ../../node_modules/@gadgetinc/react-hotkeys/index.d.ts(31,64): error TS1005: ';' expected.

This fixes it, types aren't like interfaces and can't have empty brackets.

@airhorns come to the community edition: https://github.com/ibash/react-hotkeys

@airhorns come to the community edition: https://github.com/ibash/react-hotkeys

authors: airhorns ibash

license: ISC


text:
README: fix minor typo

one -> once
I hereby consent to the Corporate CLA provided in assets/cla/corporate_cla.md

@simaotwx, migrated to https://authp.github.io/
Please re-submit PR there.

authors: greenpau simaotwx

repo: greenpau/caddy-auth-portal


text:
Ability to add default photos from custom folder path

Ability to add default photos from custom folder path

I have a forked version that do this already, i can send a PR if wanted.
class ImageGenerator(generators.ImageGenerator):
    """
    Extends base class to expose ``get_placeholder_image`` as a method,
    so child classes can easily override default implementation.
    """

    @staticmethod
    def get_placeholder_image(*args, **kwargs):
        from autofixture.placeholder import get_placeholder_image
        return get_placeholder_image(*args, **kwargs)

    def generate(self):
        # from .placeholder import get_placeholder_image

        width, height = random.choice(self.sizes)

        # Ensure that _autofixture folder exists.
        i = 0
        path = self.generate_file_path(width, height)

        while self.storage.exists(path):
            i += 1
            path = self.generate_file_path(width, height, '_{0}'.format(i))

        return self.storage.save(
            path,
            ContentFile(self.get_placeholder_image(width, height))
        )

class RandomImageGenerator(ImageGenerator):
    """
    Randomly picks an image from a given directory and saves it to the ``settings.MEDIA_ROOT``.
    """

    def __init__(self, source_dir=None, *args, **kwargs):
        if source_dir:
            assert os.path.exists(source_dir)
            self.source_dir = source_dir
            self.available_files = os.listdir(self.source_dir)
        super(RandomImageGenerator, self).__init__(*args, **kwargs)

    def get_placeholder_image(self, *args, **kwargs):
        if self.available_files:
            file_path = random.choice(self.available_files)
            with open(os.path.join(self.source_dir, file_path), 'rb') as f:
                return f.read()  # Must returns bytes
        else:
            return super(RandomImageGenerator, self).get_placeholder_image(*args, **kwargs)

@cvng Tnx, but maybe it will be better to add such functionality to main repo....

Yes, I can send a PR if needed

authors: ArtemBernatskyy cvng

repo: gregmuellegger/django-autofixture

license_source: bigquery


text:
no flavour cookie

I followed the installation steps except 5 and 6

A cookie is only set when you force a flavour. In which situation do you expect a cookie to be set, can you post the actual response headers that should set the cookie but didn't?

I would like to store the flavour at user's browser,then detemine initial page size of api results.

Like I said, the cookie will be set the first time when the ?flavour=... GET parameter is used.
You can read the currently active flavour with django_mobile.get_flavour

oh,I just thought it will be set when detected the flavour,if I use get_flavour multi-time,It may becoming inefficient

Why would you think that, the implementation is really simple: https://github.com/gregmuellegger/django-mobile/blob/master/django_mobile/init.py#L78

looks really simple! If I set the store_backend to cookie,and ?flavour=... not presented ,it will looks into request object then  _local variable which stores flavour  in threading.local(),thank god,First time heard of threading.local(),Thank your for answerd my question.

:) Have fun using it.

repo: gregmuellegger/django-mobile


text:
Can't apply Theme in Material > v4.0.0 when mui-datatables is present

I feel bad for opening another issue with 203 open right now, but I have to at least mention it in case anybody else runs into this problem:
Theming and styles in Material UI in version 4 and onwards will not be applied if mui-datatables is present. Other Material UI features work (and I see that some work has happened vis-a-vis Material UI v4: https://github.com/gregnb/mui-datatables/issues/886), but <ThemeProvider theme={theme}> will be ignored unless mui-datatables is disabled.

Haha, no worries @larissa-n, issues are issues! I do need to clean a bunch of the out as there are a lot of old ones out there that I think are no longer relevant.
What do you mean by "mui-datatables is disabled?" Are you saying that any project using mui v4 and this library will prevent any styling from working anywhere, even outside of the library?
If so, can you provide an example of the breakage in a codesandbox so I can take a look?

Hi,
I do also have strange behavior with MUI theme in the table.
e.g. when simply using the table (copied from the example) I get a white font on a white background for the header.
The background should be black. That's at least how my appbar look like, white on black.
However when I put the MuiThemeProvider again directly around the table setting the same theme, the table header font color is black.
No, I don't set any special font colors in-between.

Can you post a simple example to codesandbox @hbinkle?

Can you post a simple example to codesandbox @hbinkle?
I'm sorry, I'm not allowed to extract any code. Especially the MUI theme is owned by our customer and I can't share it.
The structure I'm using is:
 <MyApp>       <MuiThemeProvider theme={CustomTheme}>         <CssBaseline>           <TranslationProvider translations={TranslationsI18n}>              <Header>                 <AppBar>                   <Toolbar>                       .....                   </Toolbar>                 </AppBar>              </Header>              <Main>                 <div key={'page'}>                       <MUIDataTable title='Test' data={data} columns={columns} />                 </div>              </Main>           </TranslationProvider>         </CssBaseline>       </MuiThemeProvider>     </MyApp>

This causes the Theme not applied correctly. The AppBar has black background and white font.
But the header of MUIDataTable is white background and white font.
When I put <MuiThemeProvider theme={CustomTheme}> again directly around the MUIDataTable then I get black font, but still white background.

Hi,
with further investigation I found that the style "MUIDataTableHeadRow" overrides "MuiTableHead".
"MUIDataTableHeadRow" can't be set any longer for MUIv4.x.
How can I set "MUIDataTableHeadRow" in an typescript enviroment to get the correct background color?

Can confirm, muidatatables blocks dark mode for the entire webpage.

Also seeing issues where the stylings implemented through MUI of all components on the same page as the MUIDataTable are lost. Any movement on this issue @gabrielliwerant ?

authors: BinarySteve bentheiii gabrielliwerant hbinkle larissa-n

repo: gregnb/mui-datatables


text:
Working way to install for rails 7?

I have been struggling trying top get this installed and working with rails 7. Not sure if this gem is being worked on still, but was wondering if anyone could list the steps they have taken? I tried the methods listed in #153  and am getting errors on loading the javascript stating:
script: Expected a JavaScript module script but the server responded with a MIME type of "text/coffeescript". Strict MIME type checking is enforced for module scripts per HTML spec.

Wow i got it working. What I did was add this to importmap.rb
pin_all_from "app/javascript/recurring-select", under: "recurring-select"
Added the javascript files from #153 at the bottom under app/javascript/recurring-select. I had to change the jquery reference at the top of recurring_select_dialogue.js:
Old:
var $, RecurringSelectDialog;

$ = require("jquery");

New:
var RecurringSelectDialog;

import $ from "jquery";

Then in application.js I added  import "recurring-select".
In application.tailwind.css I added @import "recurring_select/recurring_select"; and oput the two files referenced in that location.
Seems to be working! I'll need to go through and tweak the styles to bring over to tailwind.

jQuery loads a bit differently in my Rails 7 app, so i followed your same instructions:

importmap.rb pin_all_from "app/javascript/recurring-select", under: "recurring-select"
pasted 2 JS files inside new app/javascript/recurring-select directory
pasted 2 CSS files inside new app/stylesheets/recurring_select directory

except inside the 2 JS files i replaced:
import $ from "jquery";

with:
var $ = jQuery;

thanks for sharing this!

authors: ryanckulp spacerobotTR


text:
Update index.js

Add version 3

@devotox Hi! I just saw your pull request right after publishing the new version of this package. I've accepted It (with a patch), so you are now on the contributors' list. Thank you for your support. 😃

authors: devotox greguz

repo: greguz/fastify-no-additional-properties


text:
profitability calculator

 Issue by Erkan-Yilmaz
Saturday Jan 21, 2017 at 14:28 GMT
Originally opened as https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/16

e.g. to find out which BOINC project is good for your hardware
useful for newcomers and "veterans", but newcomers always ask:

which BOINC project should I crunch now ?

Possible via XML files, but:

shows only users who did not hide their devices

mentioned in hangout 2: 5:00

 Comment by grctest
Saturday Jan 21, 2017 at 19:26 GMT

https://cryptocointalk.com/topic/50952-gridcoinboinc-profitability-calculations/
Startail seems to be taking up the challenge! We may see some form of profitability calculator on gridcoinstats.eu in the future.

 Comment by startailcoon
Tuesday Jan 24, 2017 at 10:44 GMT

I am, but are still in the progress of finding what sources we can use for these statistics. Until we find any other source I will continue to explore the possibility of making some good balanced general stats from the hits files of each project.

 Comment by tomasbrod
Wednesday Apr 12, 2017 at 16:10 GMT

Individual projects can be compared by the following formula:
$prj['coinval']= (($prj['rac'] / $prj['netrac']) / $prj['rec']) *1022222.22222222;

Where rac is host_expavg_credit, rec is rec from client_state.xml and netrac is 4th field from output of comman gridcoinresearchd execute explainmagnitude2.

 Comment by grctest
Wednesday Apr 12, 2017 at 10:47 GMT

How could we simplify the profitability calculator for use on the many crypto profitability calculator websites?
Think we could get away with simply stating that 'magnitude' is our equivalent of Mh/s?
(((Mag/TotalMag)*DailyReward)*Current_GRC_Value)-(operational costs) = 24hr profit estimation
We could potentially get listed on several profitability sites with the above, though it wouldn't be good for new users who don't have a RAC nor MAG.. hmm


text:
Is there a better way to create a page for each category?

I use gridsome-source-mysql plugin to get data from MySQL.
The articles has more than 50 categories, I want to create a page for each category.
Now my code looks like this:

./src/components/Category01.vue file:

<template>
  ...
  ...
</template>

<static-query>
query {
  allPosts(filter: { Category: { in: ["Category01"] }})  {
    edges {
      node {
        id
        Category
        Title
      }
    }
  }
}
</static-query>

<script>
export default {
    name: "Category01",
};
</script>

./src/components/Category02.vue file:

<template>
  ...
  ...
</template>

<static-query>
query {
  allPosts(filter: { Category: { in: ["Category02"] }})  {
    edges {
      node {
        id
        Category
        Title
      }
    }
  }
}
</static-query>

<script>
export default {
    name: "Category02",
};
</script>

All are the same except for the different category name.
Is there a better way to create a page for each category?
Thank you!

Hi,
yes, you can!
You only need one template for your categories.
Preview

https://gridsome-starter-casper-v3.now.sh/category/getting-started
https://gridsome-starter-casper-v3.now.sh/category/health/

How did I solved it?
In the gridsome.config.js I have defined a template for the Category collection:
It includes the template which should be used and also the path ( see the preview links above ).
Source: https://github.com/noxify/gridsome-starter-casper-v3/blob/master/gridsome.config.js#L75
The template contains the the html logic and runs a query against the category collection.
And here is the difference to your current solution. You're currently using the posts collection.
https://github.com/noxify/gridsome-starter-casper-v3/blob/master/src/templates/Category.vue#L38
Maybe you have to configure some relations in the gridsome.config.js to make it work ( if you haven't ;) ) .
Hope that helps.
Regards,
Marcus

@noxify This is a good idea, thank you! ❤

authors: RankinKeanan noxify

repo: gridsome/gridsome


text:
Include results of variable lookup in main query results

I'm trying to look up a few items based on the results of a query.
Here's my main query. location and speakers return IDs.
query Sessions {
  sessions: allSession(sortBy: "start") {
    edges {
      node {
        title
        start(format: "h:mm a")
        end(format: "h:mm a")
        location
        speakers
      }
    }
  }
}

Right now, I get this response from the above query:
{
  "data": {
    "sessions": {
      "edges": [
        {
          "node": {
            "title": "Opening Keynote",
            "start": "9:00 am",
            "end": "10:00 am",
            "id": "cjyw7ggwc00003c5p8bd9rgoj",
            "location": "cjyw86yqs00003c59u3r6qq2l",
            "speakers": [
              "cjyw88u6u00003c59tjdeb0la",
              "cjyw888cn00003c593u057hm7"
            ]
          }
        },
        {
          "node": {
            "title": "Session Name 2",
            "start": "10:15 am",
            "end": "11:00 am",
            "id": "cjz4fhi7j000101mj0skwf9lb",
            "location": "cjyw86yqs00003c59u3r6qq2l",
            "speakers": [
              "cjyw88u6u00003c59tjdeb0la",
              "cjyw888cn00003c593u057hm7"
            ]
          }
        }
      ]
    }
  }
}

I know that I can have additional queries that would return the location and speakers based on variables from the main query, but they would be grouped separately.
Is there any way I can use a variable to look up the speakers and location and have them returned in the node for each session in the response? I don't think it would work to have these broken out in a completely separate response. Thanks!

Well, consider this another one closed. I came across exactly what I needed here:
https://jozefm.dev/articles/2019/06/18/gridsome-netlify-cms-collection-relations/
The reference field will return an ID even if you don't register it in gridsome.config.js, which was my error. By adding the reference, speakers becomes queryable, and I can get everything from the speakers.
{
      use: '@gridsome/source-filesystem',
      options: {
        path: 'content/sessions/*.md',
        typeName: 'Session',
        route: 'sessions/:title',
        refs: {
          speakers: 'Speaker',
        }
      }
    }


text:
News in 2021?

the project stopped?

A while back. Thought about starting it up again.

repo: grit-engine/grit-engine

license: mit


text:
Incredible description part 1

#1 This is a pull request to alleviate the glaring issues. In fact it is the only Issue at this moment and will clean your slate once again.

Level Surfaces: a browser based 3D surface grapher

Although I would like it to, OpenSCAD does not work in the browser.

Yes I checked browser compatability, and although there is a browser renderer that defeats the point of writing this independently. :(

If we could change this to say it renders in the OpenSCAD program, that would improve the quality of this pull request.

on it, master

Amazing work

authors: Samir-Rashid grnnja

repo: grnnja/level-surfaces


text:
Support Sublime Text 3 + General Overhaul

switched support from ST2 to ST3
added command for creating new tasks
updated and beautified README.md
added command palette entries
reworked main menu entries

Additional info:

According to maintainers of SublimeText, the percentage of ST2 users compared to the whole users base is below 2% as of 2017.
Therefore updating to ST3 will allow mdTodo to benefit 50x the users.
Those wishing to still use ST2 can install the original plugin iTodo which offers almost identical functionality

The package control channel needs to be updated accordingly, to reflect the changed compatibility
@groenewege
I noticed neither iTODO nor this plugin has received many updates during the last 5 years.
In case you need a new maintainer, I am gladly taking over it. I maintain a range of other SublimeText plugins already and are actively involved in their development on a daily basis.

Hello,
I don't mind giving you maintainer access to this repo.
How do I go about doing this ?
best regards,
gunther
On Sun, Oct 29, 2017 at 4:46 PM, Ben Felder notifications@github.com
wrote:

The package control channel needs to be updated accordingly, to reflect
the changed compatibility
@groenewege https://github.com/groenewege
I noticed neither iTODO nor this plugin has received many updates
during the last 5 years.
In case you need a new maintainer, I am gladly taking over it. I maintain
a range of other SublimeText plugins already and are actively involved in
their development on a daily basis.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/groenewege/mdTodo/pull/4#issuecomment-340271821, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAna7qty6cuvq9zCfrO0FJR1OH5OmDjMks5sxJ3kgaJpZM4QKW7S
.

Sure, we could maintain it together.
Thanks for your trust, Gunther!

authors: groenewege pykong

repo: groenewege/mdTodo


text:
#46 Added remove-tests for TabStrip and TabControl.

TabControl's SelectedContent fails.

Thanks Robertofon - sorry about the delay, I was refactoring the ItemsControl based controls. Your tests now pass, minus the SelectedContent test, which is a property I will remove.

authors: Robertofon grokys

repo: grokys/Perspex


text:
Model identification can't distinguish between some models from each other

The goal of the analysis step is to identify all unique models within a given script. We consider two models distinct from each other if they have a different architecture.
However, there is a risk that two models with the same architecture will be instantiated within the same script, causing our model identification to fail or produce wrong results.
The example above shows linear.py slightly modified.
# Model and input configurations
input_features_len = 10
output_features_len = 10
model_a = LinearTestModel(input_features_len, output_features_len)
model_b = LinearTestModel(input_features_len, output_features_len)
inputs = {"x": torch.rand(input_features_len)}

# Call model
model_b(**inputs)

Note that although model_b is executed, analysis  reports that model_a was executed.
Models found while running 'linear'

model_a (executed 1x - 0.00s)
        Model Type:     Pytorch (torch.nn.Module)
        Class:          LinearTestModel (<class 'linear.LinearTestModel'>)
        Location:       /net/home/dhnoronha/mlagility/models/selftest/linear.py, line 22
        Parameters:     110 (<0.1 MB)
        Hash:           d5b1df11

We consider two models distinct from each other if they have a different architecture AND they correspond to different instantiations of a class.

@jeremyfowers for vis

@danielholanda this seems like a corner case that most people wont hit. Suggest bumping it down to p2 unless it starts causing someone a headache.

authors: danielholanda jeremyfowers

repo: groq/mlagility


text:
Not working in iOS 14 (dev beta 4)

The plugin is not working any more in iOS 14. Is not possible (in the Eve app) to activate the switch of the notification any more: "HomeKit reports that the accessory is not accessible"

Can not confirm this. Everything is working fine on my iPhone running iOS 14 PB 4.
My HK hub (ATV4) is also running the tvOS 14 Beta.

Do not ask me about prerelease Apple software. They’re known broken and I would not use them at home. I’ll try to take some time in the fall when they’re ready.

authors: grover roboterm vidalpascual

repo: grover/homebridge-telegram


text:
Supported platforms

Can we use this for ios/android development?

This would work fine for Android. On new versions of iOS you need to use Metal. There are some emulators that run OpenGL/OpenGL ES on top of Metal but I don't think I'd recommend that if you can avoid it.

AFAIK, Apple deprecated OpenGL ES from ios12 but apps using OpenGL ES still build and run normally on even ios16-17.
Just wondering whether glow already has the binding for that target, or I have to add it myself.
For an OpenGL ES implementation on top of Metal, MetalAngle works pretty well but I understand your reason for avoiding it.

Sure, as long as you're ok relying on GL availability in iOS then you should be able to use glow there.

I can confirm that glow work on ios, I shamelessly copied some rust-objc and get_proc_addr calls from miniquad and render stuffs just fine.

authors: grovesNL implicit-invocation

repo: grovesNL/glow