text:
merge up to gamma-tubulin complex

GO:0061494    gamma-tubulin large complex, mitotic spindle pole body
GO:0055032    gamma-tubulin large complex, spindle pole body
GO:0061495     gamma-tubulin small complex, mitotic spindle pole body
(not used in annotation)

And we keep
'gamma-tubulin large complex, equatorial microtubule organizing center'
and
'gamma-tubulin large complex, interphase microtubule organizing center'?

and what about
'gamma-tubulin small complex, centrosomal'
'gamma-tubulin small complex, mitotic spindle pole body'
'gamma-tubulin small complex, spindle pole body'

I think so. Has anyone used them  other than PomBase? I remember requesting them years ago.

SGD used 'gamma-tubulin small complex, spindle pole body' about 15 times (EXP); @srengel would you be OK merging this into the parent 'gamma-tubulin small complex'?
Thanks, Pascale

Hi @srengel  you would probably want to annotate to both gamma tubulin complex, and SPB.
The rationale is  that it didn't make sense to have location-specific complexes. We had
gamma tubulin complex , SPB
gamma tubulin complex , equatorial MTOC
gamma-tubulin large complex, interphase microtubule organizing center
etc, etc
and we would not want to do this for other complexes that occur in multiple locations.

sure this is fine.  it's 15 annotations but only 3 genes, and they each already have some flavor of spindle pole body annotation.
do we need to do anything, or just let the merge happen and the annotations will automatically get updated?

In P2GO the merge will move the annotations automatically.

authors: ValWood pgaudet srengel


text:
Missing parent GO:0062209 	 spatial regulation of meiotic DNA double-strand break formation involved in reciprocal meiotic recombination

| GO:0062209 | spatial regulation of meiotic DNA double-strand break formation involved in reciprocal meiotic recombination
is missing the correct parents to slim to
DNA recombination (GO:0006310)

Added missing relation to parent: GO:1905261 regulation of meiotic DNA double-strand break formation involved in reciprocal meiotic recombination
intersection_of: GO:0065007 ! biological regulation
intersection_of: regulates GO:0010780 ! meiotic DNA double-strand break formation involved in reciprocal meiotic recombination
+relationship: part_of GO:0007131 ! reciprocal meiotic recombination

Hmm, I thought the relation we wanted was regulates ... that's what used to be inferred back when the regulates relations were treated as transitive over part_of. But either would restore the slim results Val wants.

... and it makes sense biologically: regulating DSB formation regulates the overall recombination process

source: gharchive/issue

authors: ValWood mah11 pgaudet

repo: geneontology/go-ontology

license_type: permissive

license_source: github-api


text:
Obsoletion notice: GO:0018010  glycoprotein N-palmitoyltransferase activity

[x] GO:0018010  glycoprotein N-palmitoyltransferase activity links to EC:2.3.1.96, which is deleted.

0 annotations

Dear all,
The proposal has been made to obsolete

GO:0018010 glycoprotein N-palmitoyltransferase activity links to EC:2.3.1.96, which is deleted.
and GO:0019105 N-palmitoyltransferase activity, because it is an unnecessary grouping class.

There are no annotations; These terms are not present in any subsets.

GO:0018010 maps to GLYCOPROTEIN-N-PALMITOYLTRANSFERASE-RXN
GO:0019105 has no mappings.

You can comment on the ticket: https://github.com/geneontology/go-ontology/issues/22971
Thanks, Pascale


text:
Add command to dump models to JSON files.

For #500.
@kltm here's a quick implementation if you want to try while I'm away. It's a bit slow. The command line would be:
./minerva-cli/bin/minerva-cli.sh --dump-owl-json --journal blazegraph.jnl --ontojournal blazegraph-go-lego-reacto-neo.jnl --folder jsonout

Noting it took about an hour and change to run locally at 8GB.

source: gharchive/pull-request

authors: balhoff kltm

repo: geneontology/minerva

license_source: bigquery


text:
[Question/Bug] Allowing for Schema Evolution

I am trying to figure out if I am able to change my schema over time. As a test I ran the following schema
interface Human {
  id: ID!
  name: String
}

type Boy implements Human {
  id: ID!
  name:String!
  sisters: [Girl]!
}

type Girl implements Human {
  id: ID!
  name:String!
  brothers: [Boy]!
}

(Using IndexedDB) I see that a Boy_Girl_Human table is created and items have a Boy_Girl_Human_[id] structure.
Adding the following to my schema (not changing the other types at all)
type Father implements Human {
  id: ID!
  name: String!
  sons: [Boy]!
}

A Boy_Father_Girl_Human table is created and items have a Boy_Father_Girl_Human_[id] structure. This actually breaks https://genie-team.github.io/graphql-genie-client and queries/mutations do not go through at all (until I delete the IndexedDB)
How can I structure things to be able to make changes to my schema definition without breaking my database?

Implemented @storeName custom directive to better facilitate altering schema
Added documentation on altering your schema

authors: acoreyj ecwyne

repo: genie-team/graphql-genie

license: MIT


text:
Catalog statistics only include dataset counts

nonGeographicDatasets are not included, etc.
https://github.com/geodatagouv/geoplatform/blob/master/lib/jobs/compute-catalog-metrics/index.js#L40-L43
https://backend.geo.data.gouv.fr/api/geogw/catalogs/5b05cfb34714df049794ee5f

Fixed in #197

repo: geodatagouv/geoplatform


text:
add Tensor.ones_like()

need to improve the tests so we don't repeat code

I'm wondering if it would be better to have something like torch.full_like.
Maybe switch Tensor.ones to be Tensor.full as well then add Tensor.ones back calling Tensor.full

yeah makes sense, gonna work on it

make sure to add tests for full and full_like as well

LGTM!

authors: geohot ubihot wozeparrot

repo: geohot/tinygrad


text:
Use GH actions instead of Travis

With this change, we are just changing the platform to run the tests before starting with major changes to better support newer Ruby versions. The next step will be to try again something like #240, ensuring that we support newer Ruby versions and dropping the support to EOL versions.

@olleolleolle Since you're the most active contributor around, I'd like to know your thoughts about this before merging it.

repo: geokit/geokit

license: mit


text:
【下载安装问题】群晖NAS的虚拟机环境下，下载AC LAN失败

通过HACS的集成入口，搜索并下载Midea AC LAN，会一直停留在这个下载的界面，不停转圈，等待了一天还是如此。

也尝试过手动安装，在component的文件夹中解压，但是在重启Homeassistant之后，并没有在集成端显示安装成功。

HA的版本信息如下：

通过HACS的集成入口，搜索并下载Midea AC LAN，会一直停留在这个下载的界面，不停转圈，等待了一天还是如此。
...
也尝试过手动安装，在component的文件夹中解压，但是在重启Homeassistant之后，并没有在集成端显示安装成功。
...

国内对Github的访问困难，所以直接使用HACS下载有时候比较困难，要么多试几次，要么翻墙。
直接放到本地，你放的文件夹有问题，应该把midea_ac_lan-0.3.16/custom_components/media_ac_lan这个文件夹，放到HA的custom_componnents文件夹下

我这边其他的都可以下载，就这个提示未知错误怎么弄

我也遇到相同情况，别的应用可以下载，Midea AC LAN下载失败

我也遇到相同情况，别的应用可以下载，Midea AC LAN下载失败

same problem


text:
[Question] Is this package no longer maintained?

Thanks for creating this awesome library. I want to ask if this package is still maintained? Thanks

Thank you for your kind words! Yes, we're still maintaining the library, but it might take some time to address all issues because we're not actively working on maintaining this library anymore. Your feedback is important, so please don't hesitate to report any specific problems or suggestions you have. We appreciate your support!

Could you update the darts version to 0.26.0 (this lib's darts is 0.23.0)? Thank you very much!

authors: angeliney thuyng-ing

repo: georgian-io/pyoats


text:
Several errors thrown when trying to connect

I suspect this is an issue with the Oauth2 authentication. I'm using the same configurations that worked last time. When hitting Test connection or making a search I'm redirected throw the Oatuh2 flow and I end up onto the usual confirm page:

However the plugin throws the following exceptions. I've looked into the network debugger and all the responses are 200, so everything looks ok, unless the real response is the login page. But I can't spot it from the network panel.

@giohappy I was not able to replicate this while connecting to both

https://master.demo.geonode.org
https://dev.nexus.geosolutionsgroup.com

I tried with and without authentication (OAuth2)
Maybe you were using a different GeoNode deployment when you got this error? Please provide a bit more detail so that I may be able to replicate the issue

I guess we can close this issue, since it seems to not be reproducible. Additionally, we now have Basic Auth as the preferred connection method

authors: giohappy ricardogsilva

repo: geosolutions-it/nexus-geonode


text:
Validate minimum/maximum values in NumberField

Currently the minimum and maximum values are not checked by the validation for NumberField.

I think this was fixed with https://github.com/geostyler/geostyler/pull/220. Please reopen if i am wrong.

repo: geostyler/geostyler


text:
Is it possible to support vscode extension?

Would you have plan to build a vscode extension?

Sure, there would be one after markmap-lib@^0.9.0 is released.

Markmap for VSCode is now released: https://marketplace.visualstudio.com/items?itemName=gera2ld.markmap-vscode


text:
Adding 'master' by itself

The list includes 'master-slave' but does not include 'master' by itself.  I think that it should.
https://inclusivenaming.org/language/word-list/
https://github.com/github/renaming
Signed-off-by: John Bent john.bent@seagate.com
Please check if the PR fulfills these requirements

[ ] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make due to this PR?)
Other information:

Hi @johnbent! Thanks for the PR! I prefer that any new rules that a user of woke wants to use be added to their own config file instead of being added as a default. See https://github.com/get-woke/woke#rules.
That said, I do agree that master alone should be in the default rule set, but maybe with a "warning" severity, in case some orgs have not moved away from the "master" branch name yet. It might help push them along.
I also see some failing tests, are you able to resolve them?

Thanks @caitlinelfring .  Having users maintain their own lists is the exact problem I'm hoping to solve because I think these lists should be community maintained.  I don't trust myself nor other engineers in my org to always know which words are offensive.  I'd much rather entrust that responsibility to a larger community.

Closing in favor of #104

authors: caitlinelfring johnbent

repo: get-woke/woke


text:
Bug: Sent transactions are out of order on wallet page

This is because we order by created date, but display the settled date.

ahh, I guess then it's fine?

authors: bumi rolznz

repo: getAlby/hub


text:
After trying to enter the incorrect password, when entering with the correct one, messages about incorrect entry appear (one for each try)

Description:
After trying to enter the password incorrectly, when entering with the correct password, messages about incorrect entry appear (one for each try)
Screenshots:

Steps to reproduce:

Click on the Extension icon
Input incorrect password
Input correct password
The extension unlocks and notification about incorrect password appears (as many as were incorrect password attempts)

Alby information
Alby Version: [v1.13.0]
Alby installed through Google Chrome
Device information:
OS: [macOS Monterey 12.0.1 ]

Browser [chrome]
 Browser Version [Chrome Version 103.0.5060.114]
Are you working on this issue?
No

Some background

Toast is trggered by
https://github.com/getAlby/lightning-browser-extension/blob/master/src/common/lib/utils.ts#L30
Initial message comes from here
https://github.com/getAlby/lightning-browser-extension/blob/master/src/extension/background-script/actions/accounts/unlock.ts#L26
The unlock screen needs a message to show it here
https://github.com/getAlby/lightning-browser-extension/blob/master/src/app/screens/Unlock/index.tsx#L87

authors: AnastasiaVolk escapedcat

repo: getAlby/lightning-browser-extension


text:
Support to skip the  spec/scenario execution deliberately

I see a similar requirement in [https://github.com/getgauge/gauge/issues/1397]
I created this new ticket since the old ticket is closed .
Example for the requirement
Lets say i have used a tag 'Android' in spec level. Now in the BeforeSpec hook, i will get devicetype at run time and skip the spec execution deliberately if device type is iOS.
I need this to be reflected as skipped specs in Gauge html report as well
DO we have any feature to skip the spec execution deliberately(say any static method/ exception to skip)
Any suggestions would be helpful

@NSDInesh30 There is no feature to skip execution at runtime. The only workaround would be add conditions to the execute or not. If you can, then it's best to use tags and pre-determine the device type before running the tests.

is it possible to provide this feature in Gauge to skip  the execution by spec level
like Gauge.report(""), is it possible to give Gauge.skipSpec,  Gauge.skipScenario. SO when this is used, all the steps in this spec should be skipped and same be reflected in report.
I could use these methods inside BeforeSpec hooks, to determine whether this spec to run or to skip

repo: getgauge/gauge


text:
Drag and drop should drop the element in the selected element

Expected behavior
Drag and drop should drop the element in the selected element
Actual behavior
It does not drop in the specified location
Steps to replicate
const { openBrowser, goto, text, inputField, rightClick, $, dragAndDrop } = require('taiko');
(async () => {
    try {
        await openBrowser();
goto("https://www.w3schools.com/HTML/html5_draganddrop.asp",{timeout:60000});
        await dragAndDrop($("#drag1"),$("#div2"));
    } catch (e) {
        console.error(e);
    } finally {
        await closeBrowser();
    }
})();

Version
commit - c184a28f73a14c8bfd25a9c9f3e319c0c3b23a02

Blocks #107

Happening because of https://github.com/getgauge/taiko/issues/279

authors: NivedhaSenthil sguptatw

repo: getgauge/taiko


text:
Collection filter based on more than one taxonomy discards criteria where terms are not in the taxonomy

This could be contentious, it's a case where surprising behaviour happened when creating a filtered collection by more than one taxonomy vocabulary.
This snippet demonstrates the collection I am trying to make in the page frontmatter:
content:
    items:
        '@taxonomy': {tag: staff, team: hygienists}

So I want pages tagged 'staff' and (the default) also ascribed the term 'hygienists' from the vocabulary 'team'. The example is taken from examples provided in Grav documentation.
There are currently no pages where taxonomy:team=hygienists, but this is a placeholder for when there may be, and I expect the filter to return an empty collection until then. That's the part that may be controversial, but in my context it makes perfect sense.
What I see instead in the resulting collection is all pages tagged staff (i.e. the first @taxonomy criterion).
(I have tried the alternate YAML formats suggested. When setting similar page collections and the term does exist in the 'team' vocabulary, the filter works as expected.)
I can see the code that is responsible for this behaviour in Taxonomy.php, and it is unchanged in Grav 1.1:
        foreach ((array)$taxonomies as $taxonomy => $items) {
            foreach ((array)$items as $item) {
                if (isset($this->taxonomy_map[$taxonomy][$item])) {
                    $matches[] = $this->taxonomy_map[$taxonomy][$item];
                }
            }
        }

Expected behaviour could be achieved by adding an else clause on line 96 after the if stanza, something like:
else {
   $matches[] = []; /* actually I'm not exactly sure what type $matches should be, ..
                       but we want a value here that will produce an empty set when ..
                       $operator is 'and' and make no difference when it's 'or'. */
}

Let me know if you want me to write that patch. :)

I tested and I'm not getting the problem. Did you add team to the site taxonomies in the Site configuration (or user/config/site.yaml)?

Thanks for checking. Yes, I forgot to mention that I have registered the vocab there. Also, that I am using Grav v.1.1.8! (sorry, was late and I have to move on to another project)
I'm surprised you can't reproduce because, if I traced the code back correctly, you can see in that predicate (isset($this->taxonomy_map[$taxonomy][$item])) where it will not add the criterion if the term does not exist in the vocabulary.
I'll try reproducing on a clean install, and also adding that patch in to Taxonomy.php. Don't have time right now though.
!remindme one week
(does that work on Github?)

I tried with taxonomies already defined (tag and category)

I was able to reproduce this. Github won't allow me to attach a git patch file, so I created a Gist, hope that works for you :) You need to apply it to the user directory of a clean Grav 1.1.8.
As mentioned, I also tested my suggested fix to Taxonomy.php where I add an else block. It produced the behaviour I wanted/expected, i.e. no results.
After you've confirmed a bug, would you like me to submit a pull request?

Thanks! Fixed in develop. I was able to reproduce the problem with your patch. So basically if there are 2 taxonomies required but one has 0 items, it's going to simply pick the ones corresponding to the other taxonomy, thus generating a wrong result. Didn't get the problem in the first place. 👍

I thought maybe you didn't grok, but that is because I gave a poor explanation :/ My bad. Thank you.

authors: flaviocopes hughbris

repo: getgrav/grav


text:
OPcache warning crashing some GRAV installs with php 7.2

Using Grav with Linode / Serverpilot and php 7.2 (only 7.2, not php 7.0 and 7.1) gives the following error:

An exception has been thrown during the rendering of a template (“Zend OPcache API is restricted by “restrict_api” configuration directive”).

This error can be fixed as per Joseph's comment here: https://discourse.getgrav.org/t/again-zend-opcache-api-is-restricted-by-restrict-api-configuration-directive/4569/7
Suggest this edit should maybe be rolled into the next Grav update, as it appears fix a bug on some setups...
Add an '@' prefix on line 71 of this file
/vendor/twig/twig/lib/Twig/Cache/Filesystem.php
              @opcache_invalidate($key, true);

Unfortunately, that's a Twig bug and is upstream.  We can't fix that directly as it needs to be fixed in twig repo.

@MattAppleton  OK, there is a proper fix, that I came across while trying to solve this on a serverpilot controlled digital ocean droplet:
The error is caused by a configuration in php.ini for opcache: http://php.net/manual/en/opcache.configuration.php
To resolve, simply edit this setting in your php.ini (or relevant configuration file) for opcache settings.  In my case I had an /etc/php7.2-sp/conf.d/opcache.ini file that contained:
opcache.restrict_api=1

I just changed this to:
opcache.restrict_api=

and restarted PHP FPM with: sudo service php7.2-fpm-sp restart

Good stuff, thanks! Was manually editing vendor twig file in Grav core before, not ideal :)
Sent from Matt's mobile

On 9 Apr 2018, at 23:06, Andy Miller notifications@github.com wrote:
@MattAppleton OK, there is a proper fix, that I came across while trying to solve this on a serverpilot controlled digital ocean droplet:
The error is caused by a configuration in php.ini for opcache: http://php.net/manual/en/opcache.configuration.php
To resolve, simply edit this setting in your php.ini (or relevant configuration file) for opcache settings. In my case I had an /etc/php7.2-sp/conf.d/opcache.ini file that contained:
opcache.restrict_api=1
I just changed this to:
opcache.restrict_api=
and restarted PHP FPM with: sudo service php7.2-fpm-sp restart
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

authors: MattAppleton rhukster


text:
Check for unique IDs during build process

If an ID or no ID specified is not specified for each node element, at some point the app will crash.

Build process should auto assign a unique ID to a node element if not specified.
If there an ID check against all others to make sure it differs.

Hi @alexkn1,
Yeah, a valid point, sometimes you don't need an id, so you shouldn't be forced to define it.
For now, you need to provide id always, as it is a pretty important factor of framework mechanisms, and as you notice we don't generate any random one when it doesn't exist.
Also maybe you want to share some kind of example so we could understand better what you would like to achieve.
Or is it only about not being forced to create an id when you don't need it later?
For now, I will mark it as enhancement and hope someone picks it up in the near future.

repo: getndazn/kopytko-framework


text:
Consolidate XForms fixtures

I have verified this PR works in these browsers (latest versions):

[x] Chrome
[ ] Firefox
[ ] Safari (macOS)
[ ] Safari (iOS)
[x] Not applicable

There is some branchy logic for browser/Node differences. Otherwise I think if there were any potential for browser-specific issues we'd probably see test failures.
What else has been done to verify that this works as intended?
Ran tests and dev modes for each downstream package to validate.
Why is this the best possible solution? Were any other approaches considered?
I think the separation between special directories (test-javarosa, test-scenario) and regular category directories (all the others) could be more clear! But I was already getting wary of this becoming an over-engineered yak shave, and feel this is probably good enough to at least have clear iteration points if we need better guardrails.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
The only users it should affect are us (tests, dev mode). CI says tests are unaffected, I've manually verified both pertinent dev modes.
Do we need any specific form for testing your changes? If so, please attach one.
They're all here, that's what this PR is about 🙃
What's changed

Moved all fixtures into @getodk/common
Introduced a generalized XFormFixture interface for metadata about a given fixture, and providing an (asynchronous) method to load the fixture's XML content
Introduced a few shared points to access the project's fixtures
Migrated all usage (@getodk/scenario, @getodk/web-forms, @getodk/ui-solid) to these access points and interfaces

As mentioned, the XFormFixture design intentionally makes fixture loading asynchronous. This addresses a couple of issues that have been lurking and/or growing:

As we add more (and especially larger) fixtures, the UI client demos suffer degraded load performance. This is frustrating during dev, and tends to give a misleading picture of actual form load time.
Synchronous loading (import.meta.glob with eager: true) is a constant risk of mistakenly bundling fixtures in published packages.

The same design is backed by an abstract class meant to provide roughly the same interface for loading remote XForms, e.g. in the upcoming preview functionality. Ideally this will be trivial to consume for that purpose, and allow isolation of user-facing code from preview IO/XLSForm integration.
Beyond that, there are a few lint/formatting config updates to address changes to the filesystem structure, and a few lint/formatting fixes to address modules which were previously ignored by mistake.

I don't think this warrants a changeset in its current state. I think we'd probably want to consider it post-1.0, but for now it should be entirely internal.

repo: getodk/web-forms


text:
Use Tesseract's Orientation detection

This PR replaces the orientation correction mechanism with Tesseract's. It resulted in ~60-70% reduction in time taken by the orientation correction step (1.862s -> 756.95ms).
The confidence returned by the Tesseract is based on the number of glyphs detected and can result in extremely low scores (<1) even for correct detections. This is why this PR doesn't have a confidence threshold, as finding a score that works universally is a hard problem.
Before this change, the test resulted in ~63% accuracy. The dataset was randomly rotated to either 0, 90, 180, or 270 degrees, indicated as "randomly rotated" in the table below. This dataset was then used to compare Tesseract OSD and the chunking strategy. Tesseract OSD produced almost perfect results (61%) coming in close to the original Zerox performance of 63% (This 3% step down is discussed later on). On the other hand, the chunking strategy produced 47.10% accuracy (25% down).

Orientation detection mechanism
Dataset
Accuracy

In-house chunking strategy
Zerox test
~63% (baseline)

Tesseract OSD
Zerox test - randomly rotated
~61%

In-house chunking strategy
Zerox test - randomly rotated
~47.10%

This randomly rotated dataset can be found here.
Why the 2% step down?
Well, Tesseract failed to identify orientation for two images with the message "Too few characters. Skipping this page". For one of the image, cropping in to the receipt fixed this problem.
Tesseract has a configuration min_characters_to_try, which was set to 0 but got the same result.
And...
This PR also adds the image correction (trimming and orientation correction) if the image (PNG) is passed, which were bypassed before. This required in change in the temp directory folder structure which is expected to have no user facing impact.
Note:
When running this for the first time, tesseract downloads a file osd.traineddata sized 10.6MB

That is correct: all the tests were run using the npm run test. With an ideal orientation detection system, we'll get the same accuracy on the original test dataset and the randomly rotated (i-e, all pages were corrected accurately). With Tesseract OSD, we are getting a 2% reduction in the accuracy compared to how Zerox performed with the original dataset that had all but one correctly oriented pages.

@tylermaran your question made me realize that it'll be more helpful to know the exact count of misclassifications across both approaches, and if've now added that to the PR's description.

repo: getomni-ai/zerox


text:
failed to create state file when provided

I'm getting the following error when trying to use a porter bundle that has "state" provided in the manifest when running in the operator:
could not create a new gzip reader for the statefile: unexpected EOF
This is when using "state" to store off terraform tfstate files ex:
state:
  - name: tfstate
    path: terraform/terraform.tfstate
  - name: tfvars
    path: terraform/terraform.tfvars.json

This works when setting the tfstate file as a bundle output and using it that way.
Running this on beta.2 in the operator
originally reported by @sgettys

Looks like how k8s mounts the /porter/state.tgz file there needs to be a check for the unexpected EOF. The state file will exist but be empty. Adding in fix and testing this now

After some investigation from @sgettys , the problem is related to https://github.com/cnabio/cnab-go/issues/266.
the k8s driver writes "null" file onto the volume that's used by invocation image which causes unexpectedEOF error.
The reason why this is working with porter CLI is because docker-driver treats all files as tars. https://github.com/cnabio/cnab-go/blob/main/driver/docker/docker.go#L440

The workaround fix in porter is completes: https://github.com/getporter/porter/issues/2307

Can we close this issue or is there still something else that needs to happen?

This should be complete

authors: VinozzZ carolynvs sgettys

repo: getporter/operator


text:
SQLite drives seems to skip quoting table and column names

Version: 0.10.0
Module: quill-jdbc
Expected behavior
Queries should have identifiers properly escaped (e.g., "Transaction").
Actual behavior
Identifiers are not escaped, resulting in invalid queries like:
INSERT INTO Transaction (id,timestamp,amount) VALUES (?, ?, ?)

Steps to reproduce the behavior
case class Transaction(id: Long)
val ctx = new JdbcContext[SqliteDialect, Literal](ConfigFactory.parseMap(Map(
    "driverClassName" -> "org.sqlite.JDBC",
    "jdbcUrl" -> "jdbc:sqlite:test.db"
  ).asJava))
ctx.run(ctx.quote(
  query[Transaction].insert(lift(Transaction(0))
))

@getquill/maintainers

Related to #405

Closed in favor of #405

authors: Rogach cambridgemike fwbrasil

repo: getquill/quill


text:
What do I need auth.token for?

In sentry.properties there's a property auth.token. What do I need it for? Is it safe to bundle my auth token into the app?
Thanks!

The auth.token is used for uploading sourcemaps and debug symbols to sentry in order so we can symbolicate the crash correctly.
There is no need to bundle sentry.properties in your app.

Oh kk thanks. BTW what all permissions are needed for the access token?

Good question, I believe it's just project:releases but don’t pin me down to that 😅

#123

@HazAT created an access token with release rights only and it worked 👍
@suksoom ?

I cannot find a place to get the auth token in the sentry UI. Is it project based or in the org settings?

@tuneZola https://sentry.io/api/

@HazAT Where would this be stored at? I cannot find a list of keys in the Sentry UI.

Click on the little icon on the bottom left, and then on API

authors: HazAT simPod suksoom tuneZola

repo: getsentry/react-native-sentry


text:
Severe logs should be included as breadcrumbs for other events

Problem Statement
I have multiple errors happening in the app as a result of a bug. These are triggering multiple severe logs and uncaught exceptions. When looking at the events through Sentry, the severe logs are not present in the breadcrumbs for the event related to the uncaught exception.
The code looks something like this:
try {
   resource = createResource();
} except (e) {
  log.severe('bug');
  resource.cleanup();
 rethrow;
}

The rethrow is never caught, and the event for the uncaught exception does not include the bug log as a breadcrumb. This made me assume that this is not the branch that failed. I only realised what's going on after adding random throws around the code and comparing the Sentry logs between the original event and my modified version.
Solution Brainstorm
When sentry submits an event, previous events from the same sessions should be included as breadcrumbs.
Are you willing to submit a PR?
Yes

Hi,
thank you for the message, this looks like a bug.
The logger.sever creates a breadcrumb and event, the breadcrumb should be included in the event created from the rethrown exceptions. We will investigate it.

Hi, thank you for the message, this looks like a bug.
The logger.sever creates a breadcrumb and event, the breadcrumb should be included in the event created from the rethrown exceptions. At the moment I don't see why it's not included. We will investigate it.

I have hunch, that the different ways of serialization for whole events vs serialization for the native sync is the issue.
When doing serialization for whole events, it's done via https://github.com/getsentry/sentry-dart/blob/d78342459141e1798a213da74ad13e89235cbe31/dart/lib/src/utils.dart#L31
but for the native sync there's nothing like that
https://github.com/getsentry/sentry-dart/blob/d78342459141e1798a213da74ad13e89235cbe31/flutter/lib/src/sentry_native_channel.dart#L59
thus when non-serializable objects are added to a breadcrumb it just fails.

@maBarabas can you share your SDK init code snippet?
Also, a minimal reproducible example would help unless you are swallowing your exceptions, every unhandled exception should be captured automatically, and the previous errors should be part of breadcrumbs, as long as they were within the same session.
Last question, which library/package are you using for log.severe('bug');?

@marandaneto I was able to reproduce the issue with this code, adjusted the tryCatch function from our example app.
Future<void> tryCatch() async {
  try {
    throw StateError('try catch');
  } catch (error, stackTrace) {
    Logger("test").severe('bug');
    // await Sentry.captureException(error, stackTrace: stackTrace);
    rethrow;
  }
}

@marandaneto, here is my init:
Future<void> main() async {
  // Work around sentry not printing these errors for now. I've created a PR
  // that adds logging support. We can delete this after that's merged.
  // https://github.com/getsentry/sentry-dart/pull/1257
  PlatformDispatcher.instance.onError = (e, s) {
    return false;
  };

  // Make sure that severe and above logs have a stack trace for good grouping
  // in sentry. If there is no stack, then all the different log lines are
  // grouped together by default. We have worked around that by setting up a
  // grouping rule to split those groups by the messages.
  recordStackTraceAtLevel = Level.SEVERE;
  await SentryFlutter.init(
    (options) {
      options
        ..dsn = sentryDsn
        // enable debug logging for local development use cases, disable for
        // production
        ..debug = kDebugMode || kProfileMode
        ..diagnosticLevel = SentryLevel.info
        ..addIntegration(LoggingIntegration())
        // The app does all of its logging trough the logging package. We also
        // log to the console for debugging. Disable breadcrumbs for the console,
        // so that we don't see duplicate breadcrumbs in Sentry.
        //
        // Temporary fix: https://monitoraudio.atlassian.net/browse/MUF-264
        //
        // Sentry is missing error level logs in breadcrumbs for other related
        // events: https://github.com/getsentry/sentry-dart/issues/1583
        //
        // Every log is printed to the console, so this works around the issue.
        ..enablePrintBreadcrumbs = true
        // Set tracesSampleRate to 1.0 to capture 100% of transactions for performance monitoring.
        // We recommend adjusting this value in production.
        ..tracesSampleRate = 1.0
        ..attachScreenshot = true;
    },
    appRunner: appMain,
  );
}

Logging is done with package:logging so that I can make use of the LoggingIntegration.
The default log level is set to INFO.
I also use SentryUserInteractionWidget and SentryScreenshotWidget at the root of the app's widget tree.
I think the setup proposed by Kryštof should be representative.

Ok, I see, the problem is that Logger.root.onRecord.listen takes a void onData(T event)? function but it does not await the function call, so its added to the event loop since Sentry's callback is a Future.
The Logger("test").severe('bug'); call captures a new event and breadcrumb, but due to the event loop, the crumb is added a bit after the rethrow event is also captured.
In both cases, I see both events captured in the sentry.io dashboard though.

The StateError error does not contain the bug breadcrumb, but it should.
Since we don't have control over the logging API, we cannot change this behavior but rather make it as best effort, this only happens when creating the crumb and an error happens very next to each other, right?

Similar issue https://stackoverflow.com/questions/75752421/flutter-run-async-function-on-stream-listen
onRecord is a get so I cannot overwrite and combine with asyncMap or something else.
@maBarabas or @ueman do you have any ideas on how to fix this?

As we don't have control over the Logger implementation the workaround is to create a custom breadcrumb that will be awaited and therefore created before the rethrow.
Future<void> tryCatch() async {
  try {
    throw StateError('try catch');
  } catch (error, stackTrace) {
    Logger("test").severe('bug');
    await Sentry.addBreadcrumb(
      Breadcrumb(
        message: 'bug',
      ),
    );
    rethrow;
  }
}

authors: krystofwoldrich maBarabas marandaneto ueman

repo: getsentry/sentry-dart


text:
Request body consumed and not available to later middleware handlers

Summary
We're using Gorillamux and net/http and ran into an issue where the Sentry handler consumes the request body, which makes int unavailable for later handlers/middleware to use.
Steps To Reproduce
I don't have a fully reproducible code path, but rough outline:
router.HandleFunc("/some/path", PathHandler())

var sentryHandler = sentryhttp.New(sentryhttp.Options{
	Repanic:         true,
	WaitForDelivery: false,
})

func AuthUser() func(http.ResponseWriter, *http.Request) {
  return sentryHandler.handleFunc(func(rw http.ResponseWriter, r *http.Request) {
    r.ParseForm()
    someForm := r.FormValue("formKey")
    // someForm is blank and the parseForm will be empty because the body has been consumed
  })
}

When removing the sentry handler, the request form can be read as normal.
Expected Behavior
Later handler functions are able to use the body on the original request without having to pre-cache or otherwise get the body before the Sentry handler is used.
Screenshots
Sentry.io Event
n/a
Environment
SDK

sentry-go version: 0.27
Go version: 1.22.1
Using Go Modules? yes

Sentry

Using hosted Sentry in sentry.io? yes
Using your own Sentry installation? Version: n/a
Anything particular to your environment that could be related to this issue?

Additional context

I tested this in multiple ways (just a route, wrapped, middleware) and every time it worked fine with and without the sentry handler.
Could you please provide a way to reproduce this?

authors: clinejj ribice

repo: getsentry/sentry-go


text:
Do not call magic methods when seralizing object IDs in stack traces

This also invokes magic __isset() (and then __get() ) method for objects, which can be problematic if these magic methods have side effects. Which is exactly what I had to investigate and deal with in our own codebase today.
I'd propose that this behavior (magically getting some kind of ID of objects present within traceback) should check if the property actually exists first (via property_exists(), which doesn't invoke magic methods).
Or at least this magic feature should be optional - i,e. there should be an option to disable it.
Originally posted by @smuuf in https://github.com/getsentry/sentry-php/pull/1443#discussion_r1116010136

Thanks you for creating the issue as I haven't had the time to do it myself yet.

@smuuf I am curious about your usecase here. I would not expect a __isset and __get to have any side effects since they are existence checks and a getter (which in theory should never have side-effects), what is your use-case where they do have side-effects?
I did propose a fix in #1483, but I am still not sure if it's really needed... so curious about your case!

@stayallive As you say - "in theory" 😄 As no one can enforce that the magic __isset/__get will not have side effects, one has to presume that they might have.
Our specific case was (I admit) a rather convoluted one, but nevertheless it's what was happening.

https://www.notorm.com/#api (https://www.notorm.com/) - uses __isset/__get to represent/access relationships among tables/rows.

For example like this:

Some debugging libraries - in our case https://github.com/nette/tracy (https://tracy.nette.org/cs/) - register their own exception & error handler. - which may be registered in such order (in relation to Sentry's own handlers) that the Tracy's handlers are invoked first. Also, some debugging libraries may have something which Tracy calls "strict mode" - they handle errors/exceptions that are triggered - display them and then they totally die().
Then, some exception happens in our code (in our case it was some TypeError) - and one of the arguments present in the traceback is our NotORM object representing some DB row.
Sentry tries to serialize the traceback's arguments - stumbles upon our NotORM object (representing some DB row) and tries to access $object->id (which really is $databaseRow->id), which then fails with Undefined array key "id_id", because accessing $row->id expects to find a defined relationship between that row's own table and another table called id.

A warning is emitted, (apparently) Sentry's error handler converts it into exception (here I'm not sure exactly about the correct order of things), which Tracy catches, displays it and then stops the execution.

... or something like that ...
In any case, what we got as error message was a warning originating from the fact that Sentry was trying to access magic id property on some traceback's argument - and not the TypeError which was the original bug in our code - and we had no way of knowing this.
After I spent some time investigating this, I compacted my argument to "Accessing $obj->id may have unexpected side effects". Even though our case was a bit convoluted (I'm not even really sure now if I traced the problem and its partial steps correctly), the problem can really be boiled down to this:

Magic issetters/getters can have side effects and the only really safe solution is to check if the id property really exists and one is 100% sure that accessing it does not do anything else.

And here is what I came up with when trying to create a minimum-reproducible-example (even without Tracy):
<?php

//
// Needs:
// composer require sentry/sentry==3.13.1 php-http/curl-client guzzlehttp/psr7 php-http/message
//

require __DIR__ . "/vendor/autoload.php";

ini_set('zend.exception_ignore_args', '0');
ini_set('display_errors', 1);

set_error_handler(function(...$args) {
	$str = json_encode($args);
	echo "Caught error and exiting! Info: $str";
	die;
});

\Sentry\init([
	'dsn' => 'https://aaaaabbbbbcccccdddddeeeeefffff12@localhost/0',
]);

error_reporting(E_ALL);

function _reproduce_sentry_stuff() {

	$someObj = new class {
		private $emptyArray = [];

		public function __isset($name) {
			$this->emptyArray[$name];
		}
	};

	_throw_exception($someObj);

}

function _throw_exception($obj) {
	throw new ErrorException("Some exception I want to know about");
}

echo "reproducing\n";
_reproduce_sentry_stuff();

Then, what I got:
$ php sentry_stuff.php
reproducing
Caught error and exiting! Info: [2,"Undefined array key \"id\"","\/mnt\/w\/php\/_bugs\/sentrystuff.php",31,[]]

... and what I wanted:
$ php sentry_stuff.php
reproducing
PHP Fatal error:  Uncaught ErrorException: Some exception I want to know about in /mnt/w/php/_bugs/sentrystuff.php:40

Thanks a lot for the great write-up!
Does https://github.com/getsentry/sentry-php/pull/1483 fix your issue?

That is awesome, and thanks for the incredibly detailed response, it actually kinda makes sense what you are seeing. I was a little on the fence about the fix but reading this I'm happy we are making it, closing the issue since we got it merged and fixed but the actual release might take a few days. Thanks for reporting and detailing 👍

Released via https://github.com/getsentry/sentry-php/releases/tag/3.14.0

authors: cleptric smuuf stayallive

repo: getsentry/sentry-php


text:
Properly handle projects/workspaces with spaces in the name

We aren't doing this correctly everywhere right now.

I think right now we're just messing it up for the run actions.

This should include scheme names with spaces, too.

I wonder if someone like @gabebw or @pbrisbin have ideas here. We're passing the scheme and workspace/project to the run_ios_app script correctly, and then using $@ to pass those to the xcodebuild command, but it seems like the quotes are getting stripped somewhere along the line.

More specifically:

We're creating the command here.
s:build_target_with_scheme is calling out to s:scheme
s:cli_args uses shellescape to escape the values properly
We're passing the arguments to xcodebuild with $@

My assumption is that by the time the flags get to $@ they have lost the quotes, but I'm not sure how to fix that.

The part that jumps out to me is that in your last link, $@ isn't quoted like "$@".
I wrote about the differences, but the idea is that $@ without quotes doesn't respect quotes even if the arguments are quoted.

shellcheck agrees:
$ shellcheck run_ios_app

In run_ios_app line 5:
build_path=$(xcodebuild -showBuildSettings $@ 2>/dev/null | egrep "\bBUILD_DIR\b" | sed -E "s/[[:space:]]+BUILD_DIR = //")
                                           ^-- SC2068: Double quote array expansions to avoid re-splitting elements.

shellcheck found the same problem in run_mac_app too:
$ shellcheck run_mac_app

In run_mac_app line 3:
build_path=$(xcodebuild -showBuildSettings $@ 2>/dev/null | egrep "\bBUILD_DIR\b" | sed -E "s/[[:space:]]+BUILD_DIR = //")
                                           ^-- SC2068: Double quote array expansions to avoid re-splitting elements.

shellcheck found the same problem in some of the other scripts in bin. This is the full output:
$ shellcheck bin/*

In bin/list_schemes.sh line 5:
xcrun xcodebuild -list $@ 2>/dev/null \
                       ^-- SC2068: Double quote array expansions to avoid re-splitting elements.

In bin/run_ios_app line 5:
build_path=$(xcodebuild -showBuildSettings $@ 2>/dev/null | egrep "\bBUILD_DIR\b" | sed -E "s/[[:space:]]+BUILD_DIR = //")
                                           ^-- SC2068: Double quote array expansions to avoid re-splitting elements.

In bin/run_mac_app line 3:
build_path=$(xcodebuild -showBuildSettings $@ 2>/dev/null | egrep "\bBUILD_DIR\b" | sed -E "s/[[:space:]]+BUILD_DIR = //")
                                           ^-- SC2068: Double quote array expansions to avoid re-splitting elements.

In bin/use_simulator.sh line 5:
xcrun xcodebuild -showBuildSettings $@ 2>/dev/null \
                                    ^-- SC2068: Double quote array expansions to avoid re-splitting elements.

Ah, I didn't realizing that quoting $@ worked that way. Neat. I should look into getting ci set up to run shellcheck against PRs.

I should look into getting ci set up to run shellcheck against PRs.

You could also use Code Climate :D
https://codeclimate.com/github/pbrisbin/aurget/issues

In addition to a shellcheck engine, there's also vint. I'm not sure how good it is, but worth a shot.

authors: gabebw gfontenot pbrisbin sharplet

repo: gfontenot/vim-xcode


text:
Needs License

I'm looking to use this project, but there's no licensing information. Please add one.

MIT License has been added! Closing.

repo: ggarber/sdpparser


text:
Is it possible to use message pack instead of json/xml for request bodies?

Hi, thanks for the great library!
Right now, the library supports json, xml for request bodies. Is it possible to support for msgpack as well? Can I write a custom directive executor for this new format?
Should I be using RegisterBodyFormat, RegisterBodyDecoder or something else?
Any guidance is appreicated. TIA!

Please check out https://pkg.go.dev/github.com/ggicci/httpin@v0.17.0/core#RegisterBodyFormat

Thanks, just wanted to confirm!

authors: ggicci vamshiaruru

repo: ggicci/httpin


text:
History not saved

I'm running oterm 0.6.5 on a Chromebook Plus (Linux penguin 6.6.46-04024-g9e7e147b4900) and I'm getting the following error, which seems to be blocking the sqlite history to function -- i.e. no chat log is saved to it, but the chat tab renaming does persist between restarts of oterm.

Task exception was never retrieved
future: <Task finished name='Task-597' coro=<ChatContainer.on_submit..response_task() done, defined at /home/pp/.local/lib/python3.11/site-packages/oterm/app/widgets/chat.py:127> exception=AttributeError("'Vertical' object has no attribute 'can_view'")>
Traceback (most recent call last):
File "/home/pp/.local/lib/python3.11/site-packages/oterm/app/widgets/chat.py", line 157, in response_task
if message_container.can_view(response_chat_item):
^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Vertical' object has no attribute 'can_view'

I've installed oterm using pip.
$ pip --version
pip 23.0.1 from /usr/lib/python3/dist-packages/pip (python 3.11)
History does save and function if I comment out the two...
# if message_container.can_view(response_chat_item):
...while keeping the two...
message_container.scroll_end()
...but I'm sure that's breaking something else I haven't noticed yet. ;-)

Hey, thank you!
It appears that textual has removed can_view from widgets. I will fix and release asap.

authors: ggozad pphuck

repo: ggozad/oterm


text:
don't use fenced code block for inline code

fenced code blocks only really work when they are in an own paragraph, not inline.
if used inline the language selector is rendered as part of the code.

Thank you!

authors: evgeni ggravlingen

repo: ggravlingen/pytradfri


text:
Use Pattern type rather than Enum type for error component attr property

As described here in issue #74 , for DRF serializer ListField or DictField drf-spectacular combined with drf-standardized-errors will generate the following:
list_field_nameINDEXErrorComponent:
      type: object
      properties:
        attr:
          enum:
          - list_field_name.INDEX
          type: string
          description: '* `list_field_name.INDEX` - list_field_name.INDEX'
        code:
          enum:
          - blank
          - invalid
          - max_length
          - 'null'
          - null_characters_not_allowed
          - required
          - surrogate_characters_not_allowed
          type: string
          description: |-
            * `blank` - blank
            * `invalid` - invalid
            * `max_length` - max_length
            * `null` - null
            * `null_characters_not_allowed` - null_characters_not_allowed
            * `required` - required
            * `surrogate_characters_not_allowed` - surrogate_characters_not_allowed
        detail:
          type: string

If you're like me and use Schemathesis to generate and run tests against your documented API, this will result in errors due to list_field_name.INDEX being a string literal as see here:
- Response violates schema

    'null' is not one of ['parse_error']

    Schema:

        {
            "enum": [
                "parse_error"
            ],
            "type": "string",
            "description": "* `parse_error` - Parse Error"
        }

    Value:

        "null"

[400] Bad Request:

    `{"type":"validation_error","errors":[{"code":"null","detail":"This field may not be null.","attr":"list_field_name.0"}]}`

Reproduce with:

    curl -X POST -H 'Authorization: [Filtered]' -H 'Content-Type: application/json' -H 'Cookie: [Filtered]' -d '{"list_field_name": [null]}' http://0.0.0.0:8000/api/my-resource/

Suggestion
To use the Pattern data type rather than Enum for the attr error component property. Examples can be found here.

Sorry it took me so long to get to this and unfortunately, I don't have good news. The gist of it is: using a pattern for attr isn't enough to solve the schema conformance issues raised by schemathesis. For now, I'll keep things as they are until we have a solution for all issues raised by schemathesis.
in #79, I went ahead and added schemathesis to the test suite along with the exact cases reproducing the issues described here. After that, I updated the implementation so that attr is a string with a pattern (for a list field, the pattern is some_list_field\.\d+). Still, schemathesis kept showing similar conformance issues (can be seen in the PR checks). Looking at the docs, I thought this FAQ entry will help since drf-spectacular doesn't add additionalProperties: false by default. So, I tried adding that manually to see if it solves the issue. Again, schemathesis kept raising a conformance issue.
Then I created a minimal API spec to experiment with it (notice how attr is set as a string with a pattern)
API Spec

openapi: 3.0.3
info:
  title: API
  version: 1.0.0
  description: Amazing API
paths:
  /fuzzing/list_field/:
    post:
      operationId: fuzzing_list_field_create
      tags:
        - fuzzing
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ListFieldFuzzing'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListFieldFuzzing'
          description: ''
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FuzzingListFieldCreateErrorResponse400'
          description: ''
components:
  schemas:
    FuzzingListFieldCreateError:
      oneOf:
        - $ref: '#/components/schemas/FuzzingListFieldCreateNonFieldErrorsErrorComponent'
        - $ref: '#/components/schemas/FuzzingListFieldCreateField1ErrorComponent'
        - $ref: '#/components/schemas/FuzzingListFieldCreateField1INDEXErrorComponent'
      discriminator:
        propertyName: attr
        mapping:
          non_field_errors: '#/components/schemas/FuzzingListFieldCreateNonFieldErrorsErrorComponent'
          field1: '#/components/schemas/FuzzingListFieldCreateField1ErrorComponent'
          field1.INDEX: '#/components/schemas/FuzzingListFieldCreateField1INDEXErrorComponent'
    FuzzingListFieldCreateErrorResponse400:
      oneOf:
        - $ref: '#/components/schemas/FuzzingListFieldCreateValidationError'
      discriminator:
        propertyName: type
        mapping:
          validation_error: '#/components/schemas/FuzzingListFieldCreateValidationError'
    FuzzingListFieldCreateField1ErrorComponent:
      type: object
      properties:
        attr:
          type: string
          pattern: field1
        code:
          enum:
            - not_a_list
            - 'null'
            - required
          type: string
        detail:
          type: string
      required:
        - attr
        - code
        - detail
      additionalProperties: false
    FuzzingListFieldCreateField1INDEXErrorComponent:
      type: object
      properties:
        attr:
          type: string
          pattern: field1\.\d+
        code:
          enum:
            - invalid
            - max_string_length
            - 'null'
            - required
          type: string
        detail:
          type: string
      required:
        - attr
        - code
        - detail
      additionalProperties: false
    FuzzingListFieldCreateNonFieldErrorsErrorComponent:
      type: object
      properties:
        attr:
          type: string
          pattern: non_field_errors
        code:
          enum:
            - invalid
            - 'null'
          type: string
        detail:
          type: string
      required:
        - attr
        - code
        - detail
      additionalProperties: false
    FuzzingListFieldCreateValidationError:
      type: object
      properties:
        type:
          $ref: '#/components/schemas/ValidationErrorEnum'
        errors:
          type: array
          items:
            $ref: '#/components/schemas/FuzzingListFieldCreateError'
      required:
        - errors
        - type
      additionalProperties: false
    ListFieldFuzzing:
      type: object
      properties:
        field1:
          type: array
          items:
            type: integer
      required:
        - field1
      additionalProperties: false
    ValidationErrorEnum:
      enum:
        - validation_error
      type: string

The above API spec generates the following conformance issue
Conformance issue details

E       1. Response violates schema
E
E           {'code': 'null', 'detail': 'This field may not be null.', 'attr': 'field1.0'} is valid under each of {'$ref': '#/components/schemas/FuzzingListFieldCreateField1INDEXErrorComponent'}, {'$ref': '#/components/schemas/FuzzingListFieldCreateField1ErrorComponent'}
E
E           Schema at /oneOf/0/properties/errors/items:
E
E               {
E                   "oneOf": [
E                       {
E                           "$ref": "#/components/schemas/FuzzingListFieldCreateNonFieldError...
E                       },
E                       {
E                           "$ref": "#/components/schemas/FuzzingListFieldCreateField1ErrorCo...
E                       },
E                       {
E                           "$ref": "#/components/schemas/FuzzingListFieldCreateField1INDEXEr...
E                       }
E                   ],
E                   "discriminator": {
E                       "propertyName": "attr",
E                       "mapping": {
E                           "non_field_errors": "#/components/schemas/FuzzingListFieldCreateN...
E                           "field1": "#/components/schemas/FuzzingListFieldCreateField1Error...
E                           "field1.INDEX": "#/components/schemas/FuzzingListFieldCreateField...
E                       }
E                   // Output truncated...
E               }
E
E           Value:
E
E               {
E                   "code": "null",
E                   "detail": "This field may not be null.",
E                   "attr": "field1.0"
E               }
E
E       [400] Bad Request:
E
E           `{"type":"validation_error","errors":[{"code":"null","detail":"This field may not be null.","attr":"field1.0"}]}`
E
E       Reproduce with:
E
E           curl -X POST -H 'Content-Type: application/json' -d '{"field1": [null]}' http://127.0.0.1:8000/fuzzing/list_field/
E
E       Falsifying explicit example: test_compliance_to_api_schema_for_list_field(
E           case=Case(body={'field1': [None]}),
E       )

That's when I understood the real issue is in the discriminator mapping which still shows field1.INDEX:
    FuzzingListFieldCreateError:
      oneOf:
        - $ref: '#/components/schemas/FuzzingListFieldCreateNonFieldErrorsErrorComponent'
        - $ref: '#/components/schemas/FuzzingListFieldCreateField1ErrorComponent'
        - $ref: '#/components/schemas/FuzzingListFieldCreateField1INDEXErrorComponent'
      discriminator:
        propertyName: attr
        mapping:
          non_field_errors: '#/components/schemas/FuzzingListFieldCreateNonFieldErrorsErrorComponent'
          field1: '#/components/schemas/FuzzingListFieldCreateField1ErrorComponent'
 ======>  field1.INDEX: '#/components/schemas/FuzzingListFieldCreateField1INDEXErrorComponent'

Afterwards, I tried to see if it's possible to express the pattern at the discriminator level in openapi but couldn't find a way to do that. That led me to think: even though #79 is a step in the right direction, the API spec generated doesn't properly describe the API response. So for now, I'll keep things as they are without merging #79 until openapi adds some sort of conditional schemas that fully solves the issue or someone finds a different solution.

I see. That's a shame. Thanks for trying @ghazi-git.

authors: GiancarloFusiello ghazi-git

repo: ghazi-git/drf-standardized-errors


text:
关于 cdalign/scripts/extract_phrase.py 的bug

请问在cdalign/scripts/extract_phrase.py  中的greedy文件是什么，在运行中，报错缺乏greedy文件，但该参数为false参数～

The greedy file is the tgt sentences which are generated with greedy search.


text:
Auth for Sandbox

How do I set the instance to sandbox?  Currently
UsernamePasswordAuthenticationFlow(clientId, clientSecret, username, password) set to  prod by default.

You need to point to sandbox end-point:  https://test.salesforce.com/services/oauth2/token
More info at the wiki wiki

authors: giacomelli svemoory

repo: giacomelli/SalesforceSharp


text:
Report owner team for any failing Apps

What this PR does
Towards: https://github.com/giantswarm/giantswarm/issues/32040
Introduces a custom FailureHandler that will attempt to pull out the owner team of any App CRs that have failed to install and include that team on the test result for the failed test case so it can be used by the Slack notifications.
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

@giantswarm/team-shield / @giantswarm/team-atlas - FYI this team also marks you are the owners of the security-bundle apps and observability-bundle apps test cases, respectively.

repo: giantswarm/cluster-test-suites


text:
Support Google Cloud in the web UI

This issue is about supporting the Cluster API provider GCP (Google Cloud Platform) in the Giant Swarm web UI.
Details

CRDs - YAML representation is available with releases (example)
CAPG does not support MachinePool, we are using MachineDeployment for node pools
Cluster app in giantswarm/cluster-gcp

Tasks

[x] Provide machine types metadata, based on GCP region europe-west1

Web UI:

[ ] Add support for getting GCP machine types
[ ] Add client types and functions for CAPG resources
[ ] Add support for fetching CAPG control plane nodes (Machine and GCPMachineTemplate)
[ ] Add support for fetching CAPG node pools (MachineDeployment and GCPMachineTemplate)
[ ] Add support for determining permissions:

[ ] clusters
[ ] control plane nodes
[ ] node pools

Display

[ ] Display cluster details:

[ ] description
[ ] conditions
[ ] release/cluster app version

[ ] Display cloud provider and provider credentials (region, project ID, service account, link to provider console)
[ ] Display control plane node details:

[ ] number of replicas and ready replicas
[ ] zones (failure domains)

[ ] Display control plane nodes stats (i.e. count, CPUs, and RAMs)
[ ] Display node pool details:

[ ] description
[ ] instance type
[ ] desired
[ ] current
[ ] scaling (TODO: check how node pool scaling is configured)

[ ] Display node pool stats (i.e. count, CPUs, and RAMs)
[ ] Display release/cluster app version details: (TODO: spec)

[ ] release modal
[ ] K8s version
[ ] oldest/newest release in Organizations details

[ ] Update permissions use cases:

[ ] permissions for inspecting releases
[ ] permissions for inspecting workload clusters
[ ] permissions for managing workload clusters

[ ] Update CLI guides:

[ ] inspecting a cluster
[ ] inspecting a cluster's release
[ ] listing node pools (TODO: check if kubectl-gs supports listing nodepools for GCP)

To be continued

Today @kuosandys @fiunchinho and I had a call about implementation details. Notes are available in this internal document.

I've started looking into the underlying resources and fields we need to display information in the web UI. Here's a table I've started to keep my notes in one place - sharing it here in case it's also helpful for anyone else, and please feel free to edit!

This command should work for templating a GCP workload cluster
k gs --context gs-gohan template cluster --provider gcp --organization giantswarm --region europe-west3 --gcp-project giantswarm-352614 --gcp-failure-domains europe-west3-a,europe-west3-b,europe-west3-c --gcp-machine-deployment-failure-domain europe-west3-a

Added support to allow defining the machine-deployment.giantswarm.io/name annotation to GCP clusters.

Some notes

first milestone is to display resources, but it shouldn't be delivered at this stage (the product isn't complete)
option 1: limit customers with RBAC to make them read-only users for the entire MAPI

customers would see "you do not have permissions.." in happa
we can explain to customers that this is an interim state
caveat: GS staff would still see the UI with full permissions, and it would have to be communicated that the UI does not support mutating the UI yet

default apps could still be referred to as "preinstalled apps" - we could include a short description

hierarchical display of the default apps (app bundle) is not necessarily required here
3 column display for the preinstalled apps should be removed in favour of a flat list (similar to the user-installed app list above, with the difference that default apps are not mutable)
we want to align preinstalled and user-installed apps in the UI, and display the app icon

ingress tab - we would like to display instructions for configuring ingress regardless of whether ingress controller has been installed (this applies generally)
client certificates tab - we would like to replace this with an "Access" tab to provide instructions on how to gain access to a WC (TODO: link related issue)

Tasks:

Clarify with customers if the above solution would be suitable for them.
Right now in our cluster list page (homepage) we can see a cluster app with the same name as the installation displayed (e.g. gohan "workload cluster" in the gohan installation). We should check with Team Hydra whether this Cluster resource would always be there, and consider hiding it from the list.
We would need to gather a list of availability zones per GCP region in order to support selecting AZs during cluster and node pool creation
Ask Team Hydra about node pool scaling (and other TODO items from the first refinement)
Marian to clarify in #area-kaas whether we want to still refer to the cluster app's version as its "release"?

How should our release widget in cluster details be adapted?
Does it still make sense to show available upgrades?

We came across an interesting question:

How to handle a CAPI management cluster CR showing up in happa

@marians as you seem to be most in the know on this ticket, could you update the status collumn in the roadmap board to reflect your estimated ETA of this?

Status field updated to 1 - 3 months.
Basic support for displaying clusters properly on GCP is currently in progress. Creation and modification will follow.

Notes from refinement (19th August 2022)
Discussion about the first milestone:

Downside of limiting customer permissions via RBAC: this would involve communicating with each customer to determine what permissions they need, as this would affect their access to the MAPI and not just the web UI
idea: hide everything not currently usable, as this is a transitional stage

Decisions:

cluster and worker nodes details should not be editable, hide creation buttons, hide actions tab
apps installation will be adapted (can use kubectl gs template app as reference for how app installation needs to be adapted)
organizations management, access, permissions features remain the same

On GCP we see some new labels appear on all clusters, and which are not hidden by default currently:

I suggest to set the following label patterns to be hidden by default:

Starts with app.kubernetes.io
Starts with helm.sh

Not sure what to do about the app label. Opinions?

The Kubernetes API endpoint is currently displayed as an IP address.

There has been a change to kubectl-gs login to use a host name instead of the IP for the kubeconfig file. If that works for customers too, which I assume, I'd like us to be consistent in happa and show the same host name instead of the IP address.
I asked some questions in Slack.

We should indeed copy the mechanism from https://github.com/giantswarm/kubectl-gs/pull/876/files?diff=unified&w=0#diff-1f160945410f9311805f9b1ff5284e4cbb59cdd8934057db5bd7b3e40049979fR208 for happa and display a host name instead of IP to users.

Notes from refinement:

Hide labels starting with app.kubernetes.io and helm.sh and app
Show Kubernetes API hostname instead of an IP: https://github.com/giantswarm/kubectl-gs/pull/876/files#diff-1f160945410f9311805f9b1ff5284e4cbb59cdd8934057db5bd7b3e40049979fR208

Let's test Happa on frieza for read-only users.

authors: fiunchinho gusevda kuosandys marians puja108 vvondruska

repo: giantswarm/roadmap


text:
refactor kvm networking

Towards EPIC_URL
User Story

As giant  swarm SRE, I would like to refactor kvm  networking  so that it is more reliable
As a giant swarm PE I would like that kvm networking is refactored so that it is easier to implement new stories.

Acceptance Criteria

[ ] Given PRECONDITION when I do ACTION then I should get RESULT

Dependencies

[ ] URL - TITLE

Tasks

[ ] URL - TITLE

won't do


text:
Use definitions in default-apps-eks schema

See https://github.com/giantswarm/default-apps-cloud-director/blob/bda0dc8af518cd530dc4974c1e46ec2b7ffda39d/helm/default-apps-cloud-director/values.schema.json#L84 as an example

@giantswarm/team-turtles the default-apps concept is kinda going away, does this make sense?

authors: T-Kukawka kopiczko


text:
Gather analytics of dashboards usage

Towards https://github.com/giantswarm/roadmap/issues/182 Give customers access to Grafana
Description
We'd like to know if customers are using Grafana, and if so, how long are they on pages, which pages are they going to. It'd be cool also to have similar data for Giant Swarm employees.
TODO

[ ] Check if we can use the GA plugin for Grafana to collect usage data
[x] check Grafana analytics panel plugin
[ ] clean-up ghost

Hi @marians, Joe mentioned you may have already looked into this? Just picking this up and wanted to check.

First thing I came across is macropower-analytics-panel, it's not Google, but allows feeding analytics data from Grafana back into Grafana! More privacy friendly, but requires running a service to store the data.

OK, I did a rather extensive search and I cannot see an easy/documented/useful way to hook Google Analytics into Grafana. In the end it's all HTML so maybe injecting a <script> would somehow be possible, but I'm not sure what context we'd get that way and so if it would be very useful.
BTW most info out there is about feeding data from Google Analytics into Grafana so it can be visualised and analysed there. There is pretty much nothing about analysing Grafana usage. There is this issue at GitLab where they looked into that but eventually went a different route (user research, aka talking to SRE team to ask how they use the dashboards, and possibly using logs).
I'm inclined to try this analytics-panel plugin and see how it works first, before getting into hacky solutions.

I experimented with the macropower-analytics-panel plugin and here are the results, for reference.
I deployed the simple backend service that acts as a receiver for the frontend plugin to send data to and as temporary storage for that data to ghost MC in grafana-analytics-panel-server namespace. This is a simple Deployment + Service + Ingress that can be turned into an app.
The Ingress hooks into the Grafana subdomain and exposes the service via an additional path and uses URL rewriting so the backend is unaware it's not running under /. For ref, this looks like:

Ingress definition
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: "nginx"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
  labels:
    app: grafana-analytics-panel-server
  name: grafana-analytics-panel-server
  namespace: grafana-analytics-panel-server
spec:
  rules:
  - host: grafana.g...o
    http:
      paths:
        - backend:
            service:
              name: grafana-analytics-panel-server
              port:
                number: 8080
          path: /grafana-analytics-panel-server(/|$)(.*)
          pathType: ImplementationSpecific

Once that's running, we need to configure the frontend. Unfortunately the way it works is that the plugin adds a panel that has to be added to every dashboard that we want to track. But this can be done programmatically if we use Jsonnet to generate/modify the dashboard JSON files.

For ref, manual setup

open a dashboard, add a panel

configure the endpoint, in case of ghost this is https://grafana..../grafana-analytics-panel-server/write

panel should now be working (no error)

and metrics should start appearing when browsing the metrics endpoint: https://grafana..../grafana-analytics-panel-server/metrics

Joe found there's a somewhat briefly documented built-in option in Grafana config to supply details for Google Analytics after all, and thanks to Marian I now have access to https://analytics.google.com/ sorted, so I'm going to be trying this out now.

I got the Google Analytics integration sort of working. Well, it seems to be working fine on our end and on GA end as when loading up Grafana I can see requests to google-analytics.com, and I can see data appearing in GA in the realtime section (and eventually in the main section as well).
The problem is the call to GA only happens on full page load (whether it's to the / or directly to some dashboard). It doesn't happen when navigating between components in the app (e.g. if I go to / I'll get a hit then, but when I navigate to some dashboard from there, nothing is sent to GA).
Full page load (/):

Full page load (Alerts dashboard):

Navigating from / to Alerts dashboard:

Bummer.
I'd say the general "user hits dashboards" info is better than nothing.
Can we actually distinguish customer users from Giant Swarms staff?

That's a good point, I'll check that.

In the meantime I opened a topic in Grafana Community: https://community.grafana.com/t/grafana-google-analytics-integration/50114

Hmm, customer login doesn't work for me, I'm getting an error page with: login.OAuthLogin(get info from generic_oauth).

In which installation?

In which installation?

Sorry, this is on ghost.

Works for me

Can we actually distinguish customer users from Giant Swarms staff?

OK, I think the answer here is no.
I can see you logging in on 9th ~1:45 PM, but the only way I can tell is because there's a new session from Germany. It seems it only knows about location, browser, browser language and OS, so that's not enough to distinguish customers / staff.
I still got no responses on the community forum regarding in-app navigation, so given that and the fact this doesn't even provide enough info, I don't think using Google Analytics makes much sense.
It seems the analytics-panel plugin requires more setup but it does provide the data we need, so we just need to make a decision on if it's worth the effort.

Let's brainstorm™ if there is another way to get what we want.
Can we use any of our metrics? Maybe from NGINX ingress controller, from dex? Or isn't there an Oauth proxy involved when accessing grafana? (I still wouldn't know how to distinguish customers from GS staff.)
Does Grafana log access somehow?

With dex / OAuth, I'm guessing that will depend on whether the access is direct or through Happa as the user would've been already authenticated then, right?
I can check NGINX. Logs may be a potential avenue as I think Grafana logs something on access and I know folks from GitLab were exploring that route. But we'd need a solution to ingest logs to take advantage of that.

With dex / OAuth, I'm guessing that will depend on whether the access is direct or through Happa as the user would've been already authenticated then, right?

No, a user coming from happa would technically be the same as one entering the URL manually or clicking a bookmark etc.

I checked the options you mentioned.
Logs
Logs definitely contain enough info to distinguish users as you get a message like this on login:
t=2021-07-14T13:05:26+0000 lvl=info msg="Successful Login" logger=http.server User=mig4@...

As for which dashboards are accessed, it seems to log a message only the first time a dashboard is loaded:
t=2021-07-15T08:59:00+0000 lvl=info msg="Initialized channel handler" logger=live channel=grafana/dashboard/uid/be7wLwgnk address=grafana/dashboard/uid/be7wLwgnk
t=2021-07-15T09:00:20+0000 lvl=info msg="Initialized channel handler" logger=live channel=grafana/dashboard/uid/qMN01qkWz address=grafana/dashboard/uid/qMN01qkWz

i.e. if I open a dashboard "Alerts" it logs that message, but when I navigate away and navigate back to the "Alerts" dashboard, or even if I navigate to it from a completely separate session / different user, there are no subsequent messages.
So it would tell us which dashboards are completely unused, but it wouldn't tell us how much a dashboard is used. Note that this means that even if a dashboard is open even once during its entire lifetime you wouldn't be able to distinguish it from one that's used every day.
nginx
I checked NGINX-IC metrics.
None of them contain user info:
 mig-debug  ~  curl --silent --globoff --request GET 'http://prometheus-operated:9090/ghost/api/v1/query?query={ingress="grafana"}' | jq '.data.result[].metric' | grep -c 'mig4'
0

None of them contain path info (qMN01qkWz is the ID of the nodes overview dashboard which is part of the URL when viewing it in browser):
 mig-debug  ~  curl --silent --globoff --request GET 'http://prometheus-operated:9090/ghost/api/v1/query?query={ingress="grafana"}' | jq '.data.result[].metric' | grep -c 'qMN01qkWz'
0

dex
We run dex without the telemetry endpoint enabled, but I tested things with it enabled (https://github.com/giantswarm/dex-app/pull/92) and the only metrics it exposes are:
http_requests_total{code="200",handler="/.well-known/openid-configuration",method="GET"} 2
http_requests_total{code="200",handler="/auth",method="GET"} 1
http_requests_total{code="200",handler="/healthz",method="GET"} 76
http_requests_total{code="200",handler="/token",method="POST"} 1
http_requests_total{code="200",handler="/userinfo",method="GET"} 1
http_requests_total{code="302",handler="/auth/{connector}",method="GET"} 1
http_requests_total{code="303",handler="/approval",method="GET"} 1

So not useful here.
OAuth Proxy
Not used with Grafana.

Could be that the logs info would be enough already. I think it's not important to know how often a dashboard has been opened by one user during one session. If a dashboard access is counted once, that would suffice. As long as a session ends at some point...
On dex:
Is this actually the metric? http_requests_total{code="302",handler="/auth/{connector}",method="GET"} 1 and is the actual connector name not visible there?

As long as a session ends at some point...

To clarify, that message in the logs mentioning specific dashboards is something I've only seen once during the lifetime of the backend instance. So it's not related to user session, it seems to be related to just the backend loading the dashboard. It doesn't get repeated on any subsequent new sessions, etc.

On dex:
Is this actually the metric? http_requests_total{code="302",handler="/auth/{connector}",method="GET"} 1 and is the actual connector name not visible there?

Yip, exactly, connector name is not visible.

Dang. That's not cool.
Next thing we can evaluate is including an arbitrary image src (e. g. invisible PNG) via a HTML panel per dashboard.
Currently we don't have the service for that in place. However we need something like this for happa, too (biscuit story).

Next thing we can evaluate is including an arbitrary image src (e. g. invisible PNG) via a HTML panel per dashboard.

That sounds more or less like what the analytics-panel plugin does. Have you seen my message about the proof of concept I deployed?

Yes, but not processed. Let's do a call soon, maybe I understand it then.

Sure, good idea, I'll talk to Joe and we can organise something maybe tomorrow to hash this out and decide.

refinement 20/07/21, @marians @mig4 @JosephSalisbury

agreement on existing requirements:

see which dashboards people have checked out
distinguish between GS staff and customers

not too fussed about advanced features: e.g: time on page, want at least 'number of times person hit page'
@mig4 demoed analytics panel
discussed disappointment w/ google analytics integration
continue w/ analytics panel
make sure to drop user_login and user_name labels from ingestion
check if users can access lists of user data
don't even send the user details to the backend server / add upstream contribution to make user details configurable
add analytics panel to dashboards, use giantswarm/dashboards
build dashboard in cortex to show fancy data for our dashboard usage

Some thoughts on splitting tasks:

create an app for analytics-panel-server

ensure the service is scraped by Prometheus

check if customer users can access the analytics-panel-server endpoint

if no; ensure Prometheus drops user_login and user_email labels when scraping

add recording rules to send Grafana analytics data to cortex / Grafana Cloud

add option to upstream analytics-panel plugin to filter out PII

add analytics-panel plugin to g8s-grafana deployment

add analytics-panel to public dashboards

build a dashboard usage dashboard in GC/cortex

@marians I think I have the permissions to delete the Google Analytics properties for Grafana. Let me know if you want me to leave them for now, otherwise I'll clean up later on this week.

I already deleted the unused one. Feel free to delete the other one, too.

Opened an issue upstream to discuss adding an option to avoid including PII in collected data - https://github.com/MacroPower/macropower-analytics-panel/issues/22

We discussed an alternative architecture where instead of having the backend app on each installation, we'd have a single global one on the operations cluster, which is similar to how GA works. There are some risks associated with that, but we'll be looking into it as it would simplify deployment and authentication.

How do we want to expose the distinction between GS staff and customers on the dashboard usage dashboard?

I cleaned up all test artifacts from ghost 🧹

@snizhana-dynnyk do we wanna move the 'add analytics plugin to private dashboards' to a follow up issue? i think it'd be cool to close out here, and we can prioritise that separately

yes!

Well, I started poking around and found some problems. I'll add them to the list + open issues for them.

authors: JosephSalisbury marians mig4 snizhana-dynnyk


text:
Can't push changes to branch

Hi @iamtekson
I cannot seem to push changes to a branch. I am able to create it on the GitHub UI (I just did, it's called sphinx-docs. But when I try to push my changes to it, I get:
21:12:54.285: [geoserver-rest] git -c credential.helper= -c core.quotepath=false -c log.showSignature=false push --progress --porcelain origin refs/heads/sphinx-docs:refs/heads/sphinx-docs --set-upstream
remote: Permission to gicait/geoserver-rest.git denied to iboates.
fatal: unable to access 'https://github.com/gicait/geoserver-rest.git/': The requested URL returned error: 403

Am I maybe missing a permission?

Nevermind, it is because Github has disabled username/password auth for pushing

repo: gicait/geoserver-rest


text:
Audio Issues

The application creates a lot of audio profiles, which over time results into a mess like in the image below. The application does not play any audio including notifications, except for the received audio messages or videos.

To give more detail.. It seems that a new audio profile is created every time I switch the chatroom (change who i am chatting with)

@Njegosh Sorry for this problem :(
It's an upstream bug. If you try with epiphany browser it will happen.
For now, I'm closing this issue

authors: Njegosh gigitux

repo: gigitux/gtkwhats


text:
Puppy Linux logo

Can we add Puppy to the list?
https://upload.wikimedia.org/wikipedia/commons/9/9d/Puppy_logo.svg

Added c855b83987e4851760ebe7a5bef36230cc54cc42
Thanks

authors: gilbarbara totymedli

repo: gilbarbara/logos


text:
Fixed #141 where not all markdown files are displayed if they h…

…ave 3 dashes (---) in the content, but no metadata header. This change modifies the metadata regex to check for metadata data headers of the following types at the beginning of the file: /* {header} */ or --- {header} ---. Updated tests.
Also fixed issue with metadata being added as: {header} ---, which is an incorrect format for yaml header in markdown files. This change modifies it to insert the header as: --- {header} ---.
The previous way of adding metadata creates several conflicts when trying to parse valid markdown (horizontal rules, tables, code blocks) when no metadata header is actually present.

Note that this change will slightly break existing pages that had yaml-type metadata headers added by the Raneto UI. Users will have to manually change the header to have 3 dashes (---) at the beginning. Pages that aren't updated will just show the header as part of the content. So instead of:
Title: Test1
Description: test1
Sort: 2
---

It should be:
---
Title: Test1
Description: test1
Sort: 2
---

Since the previous format is incorrect, I think this is reasonable to ask if users upgrade.

Thanks for this @shimizust
Appreciate you documenting, adding tests, and not changing existing tests
This will be part of a new version and since the breaking change is minor, it's ok
(Please PR against dev in the future)

Thanks for the quick turnaround. I'll make sure to PR against dev next time.

authors: ryanlelek shimizust

repo: gilbitron/Raneto


text:
🛑 Receipt metadata URL is down

In aa4bcb9, Receipt metadata URL (https://ipfs.io/ipfs/bafkreih7cvpjocgrk7mgdel2hvjpquc26j4jo2jkez5y2qdaojfil7vley) was down:

HTTP code: 429
Response time: 2 ms

Resolved: Receipt metadata URL is back up in 31e6be8.

repo: gildlab/upptime


text:
Remove binaries from source tree

Greetings,
Why does the source tree contain the binary files?
Thanks,
coast

OK, i understand.


text:
Square Player

I want 1:1 square player instead of 16:9. My view is 375x375, but this solution is not working. Any tip? Thank you.

Sorry for the delay here. I'm doing some Spring cleaning, so due to inactivity I'll be closing this issue.
Please leave a comment or open a pull request if this issue persists. Thank you.

authors: gilesvangruisen szalaidaniel

repo: gilesvangruisen/Swift-YouTube-Player


text:
Improve code coverage for DerivedAsyncCache

It's currently only 59% tested, see https://coveralls.io/builds/13267639/source?filename=src%2Fmain%2Fscala%2Fcom%2Fgilt%2Fgfc%2Fcache%2FDerivedAsyncCache.scala
Code coverage should be >95%

Wrong repo 🤦♂

repo: gilt/gfc-concurrent


text:
how to unmarshal something which is not interface{}?

documentation is pretty lacking, and it is quite unclear how to unmarshal to something which is not interface{} which will actually work with Validate().
for example:
type T struct {
    a int
}

f, _ := os.Open(path)
decoder := json.NewDecoder(f)
t := new(T)
err = decoder.Decode(t)
if err != nil { .. }
// The following throws an error.
p, err := bigqueryConfigSchema.Validate(t)
i := new(interface{})
i = t
// Also error.
p, err := bigqueryConfigSchema.Validate(&i)

Closed as a result of discussion in issue #3.

authors: gima oryband

repo: gima/jsonv

license: unlicense


text:
Problem with custom libraries

When using custom libraries folder, the package foreach is installed fine but when running generate.R using Shiny the following error occurs:
Package ‘foreach’ version 1.4.4 cannot be unloaded:
 Error in unloadNamespace(package) : namespace ‘foreach’ is imported by ‘caret’ so cannot be unloaded

Problem with packages is fixed by adding loading foreach and inerators libraries in utils.R.
Next problem:
When running generate.R:
Subsetting data to match the given training genes...
Data subset. Generating models...
Error: `data` and `reference` should be factors with the same levels.

Files ada_model.rds. ada_matrix.txt, ada_summary.txt and ada_testing.tsv are generated and not empty but then this error occurs.

Fixed by adding
cm <- caret::confusionMatrix(as.factor(predictions), as.factor(validation_set[["status"]]), positive = "1")
caret version 79 changes:
"when creating a confusion matrix using two vectors, the input data are now required to be factors with the same levels"

repo: gimelbrantlab/magic


text:
Handle compressed ELF sections

For gimli's dwarfdump to handle compressed ELF sections, support should be added to object.

Actually I guess support needs to be added to both goblin and object.

I suppose we could just handle it in object.
Would you accept addding a method ObjectSection::uncompressed_data that returns Cow<'data, [u8]>? Perhaps also Object::uncompressed_section_data_by_name?

And we'd have to add a flate2 dependency.

SGTM!

Would Object::uncompressed_section_data_by_name automatically load .zdebug_info if .debug_info is requested?

Would Object::uncompressed_section_data_by_name automatically load .zdebug_info if .debug_info is requested?

Note that libbfd will look for .debug_info first and fall back to .zdebug_info if that's not found, independent of the setting of the compression flag.
It would probably make more sense to define yet another function, say uncompressed_debug_section_data, that does the magical .zdebug fallback and "ZLIB" decompression.

Is that what you want?

I'm happy with anything that works, but we need to do the fallback somewhere, and currently gimli consumers only look for the single name provided by Section::section_name. So doing it here would mean no changes needed in gimli.

What about doing that for all .debug_* sections?

Yes it would have to be all sections.

Would it be OK with you if it also automatically decompressed debug sections starting with "ZLIB" like libbfd does?

Yes.

It would probably make more sense to define yet another function, say uncompressed_debug_section_data, that does the magical .zdebug fallback and "ZLIB" decompression.

Do you mean Object::uncompressed_debug_section_data?
I'd rather we only add separate methods if we think there's going to be use cases that require them. So I'd actually be okay with changing Object::section_data_by_name to do all the magic and return Cow<'data, [u8]>, unless you think there's a reason not to.

That makes it sound like we shouldn't decompress sections simply because they start with ZLIB then. So I think Object::section_data_by_name should do the following:

look up the section with the given name
if it exists and has the SHF_COMPRESSED flag, then decompress it
otherwise if the section name starts with .debug_, then look up the .zdebug_ section, verify it starts with ZLIB, and then decompress it

OK I've implemented this. First we need to add support for ELF Chdrs to goblin: https://github.com/m4b/goblin/pull/83

I'm fine with temporarily changing Cargo.toml to specify a git version.

I'm not in a hurry with this so I guess it's less churn to wait for the goblin release.

FYI, goblin 0.0.15 has been released.

Fixed by #50

authors: fitzgen philipc rocallahan

repo: gimli-rs/object


text:
fix: affiche un fil d'ariane sur la page du diag France travail

:wrench: Problème
Actuellement, lorsqu'on affiche le diagnostic Franc Travailn aucun fil d'ariane n'apparait
:cake: Solution
rajouter un fil d'ariane
:rotating_light:  Points d'attention / Remarques
ras
:desert_island: Comment tester
se rendre sur le carnet de diane rose avec different profil
voir le fil d'ariane
fix #1881

:tada: This PR is included in version 1.242.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: lionelB service-dev-gip-inclusion

repo: gip-inclusion/carnet-de-bord


text:
Svelte 5 compatibility

Hello, and thank you for developing this !
I'm migrating my projects to Svelte 5, but svelte-undo doesn't play nice with it :)
Is this just a dependency declaration or is there an actual problem using it with Svelte 5 ?

Maybe just a peer dependency issue. I'll look into it later.

What do you mean by 'doesn't play nice with it'? Is it just the npm warning, or is there something else?

Sorry I should have poster this in the first post..
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: goldenboard@0.0.1
npm error Found: svelte@5.2.3
npm error node_modules/svelte
npm error   dev svelte@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer svelte@"^3.55.1 || ^4.0.0" from @gira-de/svelte-undo@1.2.2
npm error node_modules/@gira-de/svelte-undo
npm error   dev @gira-de/svelte-undo@"*" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error C:\Users\bkupe\AppData\Local\npm-cache\_logs\2024-11-18T23_07_32_490Z-eresolve-report.txt
npm error A complete log of this run can be found in: C:\Users\bkupe\AppData\Local\npm-cache\_logs\2024-11-18T23_07_32_490Z-debug-0.log

@benkuper Thanks for using svelte-undo, we hope that you have fun with it 🤘
We just released version 1.3.0, which is compatible with svelte 5.0. Feel free to test it, and if you like we'd be glad to hear feedback.

Thank you very much !
Is there some documentation on how to work with Svelte 5 runes like $state ? My whole app is now flowing with them and it would be so great to have seamless integration on that !

Currently, only classic Svelte stores are supported. We started experimenting with runes. However it's not ready yet. https://github.com/gira-de/svelte-undo/tree/svelte-5-runes

authors: benkuper bztes daniel-albuschat

repo: gira-de/svelte-undo


text:
Increase font size throughout the website.

A few members have suggested that the font size is a bit small for folks to read. This is throughout the site and will most likely need to be updated and tested throughout.

I'll be submitting a PR shortly.

Fixed with #150

authors: dutchbay juliaelman

repo: girldevelopit/gdi-new-site


text:
Android-Kotlin : 09.7 NestedScrollView in Android (Kotlin)

Description 📜

Give a step-by-step tutorial of NestedScrollView in Android (Kotlin).
Required Documentation or Video or Audio.

Domain of Contribution 📊

[x] Android Dev (Flutter, Java, Kotlin)

References :

https://www.geeksforgeeks.org/nestedscrollview-in-android-with-example/

Please Read it Carefully Before Contributing

Changes should be made in Android_Development_With_Kotlin/ directory under Android_Development_With_Kotlin branch.
Inside Android_Development_With_Kotlin/ directory creates a directory and names it according to the topic ( for this issue 09. Dynamic User Interface)
Inside 09. Dynamic User Interface/ directory add your task with subtopic number and name and make changes accordingly.
You have to push your PR to the Android_Development_With_Kotlin branch only.
You can take help to the references but don't simply try to copy it. Just explain in your own word.
This issue is for GWOC'21 contributors only.
You need to push in a single commit. If there exists more than one commit then you need to squash your commits into one commit.
Will assign you on a first come first serve basis.
Please try to complete your assigned task within 7 days. If you need some more time then, please inform mentors and supervisors.
If you have two previously assigned issues on Android-Kotlin pending then please first complete them.

Supervisor @rahulsain

Happy Contributing. Best of Luck.💖

/assign

Hey @rahulsain and @sitamadex11 , I have created the PR please review it, and if there are no issues you can merge it.
THANKYOU

repo: girlscript/winter-of-contributing


text:
Cybersecurity 4.6 Vigenère Cipher

Description
Description
Explain What is Vigenère cipher is and its encryption/decryption process also.
Note:

If interested, mention in which format you want to contribute: Documentation or Video
Please avoid copy/paste, BE YOURSELF
Try to explain with Diagrams
Changes should be made inside the Cyber_Security/ directory & Cyber_Security branch.
Task will be assigned on first come first serve
Check it out Contribution Guidelines

Domain
Cyber Security
Type of Contribution
Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Hey I want to do the documentation part

/assign
for documentation

Hey I want to do the documentation part

Assigned!

@AtharvaaPatil When you are going to submit your work?

Is this not merged yet?
Did I make a mistake???


text:
Aggregation - order

In gitlab by @sylvaingaudan on Apr 28, 2017, 13:34

In gitlab by @MohamedHamouGisaia on May 2, 2017, 10:30
assigned to @MohamedHamouGisaia

In gitlab by @MohamedHamouGisaia on May 2, 2017, 16:34
closed

In gitlab by @sfalquier on May 3, 2017, 11:03
reopened

In gitlab by @sfalquier on May 3, 2017, 11:03
added ~1918368 label

In gitlab by @sfalquier on May 3, 2017, 11:03
added ~1918367 and removed ~1918368 labels

In gitlab by @sfalquier on May 3, 2017, 11:03
closed

In gitlab by @sfalquier on May 3, 2017, 11:03
removed ~1918909 ~1918367 labels

repo: gisaia/ARLAS-server


text:
Add option to use plain input instead of markdown

Recently, my users have posted NSFW content using images through markdown. It will be nice if giscus has an option for me to disable markdown editing for users.

This just points to discussion on GitHub. I'd suggest using the "Report Content" function in github so the accounts are suspended

authors: naptestdev nschonni

repo: giscus/giscus