Few tests write to the project folder

That increases the list of changed files - we don't want that!
Those tests should copy the test data to a temp folder, and that's what the tests in question should use. Afterwards the tests should remove that folder, leaving no footprint.

I am not sure whether this is literally true or a misunderstanding. I assume you are refering to the test cases Test_NuGet_010 and Test_UC_045 for which a lot of "transient" data is removed in the current state of PR #59.
However, these irrelevant pieces of data are not the result of the two test cases being executed in the project folder themselves. Both tests are bases on Cider projects with installed NuGet dependencies. For instance, the test case description for Test_NuGet_010 reads:
⍝ Open a project that has already two NuGet dependencies

The current approach to test this (before PR #59) is to have a fully configured Cider project (with NuGet dependencies) under the path Tests/Test_NuGet_010 that is copied to a temporary folder and opened in Cider from there. The problem is that the Cider project under Tests/Test_NuGet_010 has been generated by executing ]Cider.AddNuGetDependencies beforehand. This approach has two problems:

A fully configured Cider project with NuGet dependencies has these dependencies in a publication folder which contains dlls targeting a specific target framework. A Cider project build with net5.0 as target will not be compatible with a Dyalog APL installation targeting net6.0. This is the reason why in PR #59 I split the test data for Test_NuGet_010 in two subfolders Tests/Test_NuGet_010/net5.0 and Tests/Test_NuGet_010/net6.0 that only vary by the target framework.
When using NuGet.Add we ultimately call dotnet publish. This command is meant to create a self-contained folder published containing all assemblies and metadata to deploy a dotnet application anywhere. However, in order to do this, the dotnet application which covers our NuGet dependencies has to be built first. The bin and obj folders will contain the build artifacts as well as metadata that is specific to the environment in which the build took place. This is the reason that we saw file paths that only make sense in the context of my machine in the first version of #59.

With respect to the tests we can get rid of both problems by removing the hard-coded Cider projects and changing the tests to first create Cider projects with the desired specifications (under a temporary folder, of course) and then exercising it.  However, this tests not quite the same thing and in fact for Test_NuGet_010 this would be equivalent to deleting this test, since Test_NuGet_004 is essentially the test we would get by modifying Test_NuGet_010 in this way.
However, I think that the observations 1 and 2 above transcend test:

I think a Cider project should not depend on a target framework when this is not strictly necessary. This is probably hard to acommodate.
We should probably not store transient data in a Cider project at all. I think it would make sense to automatically delete the bin and obj folders after adding a NuGet dependency via ]Cider.AddNuGetDependencies. That is essentially what I manually did in my last change to PR #59.

Solved by running the test in question in a separate instance of Dyalog, with its own data folder.


More cleanup after repo migration

Ooops, Lua Rocks link shouldn't have changed. On the other hand the link inside the rock should!
Making this a draft until I can figure out whats up with coveralls. I think it's not reporting because it doesn't have history to report against any more, but there could be more to it than that.

 It doesn't know what to do with itself inside other the GH Actions CI runner yet. Until better support is baked in (see moteus/luacov-coveralls#17) I've hacked together something that should give some output, but allowed it to fail.
It won't generate a failure on coverage reduction, it won't post comments back to the PR, it won't aggregate results from all the Lua version runs, etc., but it is better than nothing. Maybe. Probably.
Also I don't think it will work at all except on master because Github Actions isn't exposing the secret to the PR. I think that might happen in the future after this lands on master, but it's hard to predict.

Yay! The coverage did get updated once it hit master.


Struct defined in yaml uses map

In GitLab by @ksiero on Jan 26, 2021, 10:18
Struct defined in yaml uses map. It must use a list to be sure the correct order of members are read.

In GitLab by @ksiero on Feb 11, 2021, 11:52
mentioned in commit 4b6ba30892a462b4f8cb36bf4932a07eb8c8e0e0

In GitLab by @ksiero on Feb 26, 2021, 10:47
mentioned in commit 41ad98e0132b3a6df35a99228cd8ecac0ffcd2ad

In GitLab by @ksiero on Feb 24, 2021, 16:17
mentioned in commit 5c9d78be640f38332ff0d4a3ddb0871a1aea1b9a

In GitLab by @ksiero on Feb 26, 2021, 11:12
mentioned in commit f9f0d937524e561e2d60e764f559644517786607

In GitLab by @ksiero on Feb 26, 2021, 12:17
mentioned in commit e77b05239785afe034836d065758017e40fee2ad


New version: Rocket v1.3.11

Registering package: Rocket
Repository: https://github.com/biaslab/Rocket.jl
Created by: @bvdmitri
Version: v1.3.11
Commit: e7a033678abba42ce75dc2c2c32204aa6a5315b2
Reviewed by: @bvdmitri
Reference: https://github.com/biaslab/Rocket.jl/commit/e7a033678abba42ce75dc2c2c32204aa6a5315b2#commitcomment-50967165

[noblock]
Is something wrong with the registration process? Should I do something about it or just wait?

Is something wrong with the registration process?

Yes: https://www.githubstatus.com/incidents/m16jzl31gnqt

Should I do something about it or just wait?

Just wait, unfortunately.
[noblock]


GraphQL Mesh SDK with Next.js - Module parse failed: 'import' and 'export' may appear only with 'sourceType: module' (1:0)

Describe the bug
error - ./.mesh/index.js
Module parse failed: 'import' and 'export' may appear only with 'sourceType: module' (1:0)
File was processed with these loaders:

./node_modules/next/dist/build/webpack/loaders/next-swc-loader.js
You may need an additional loader to handle the result of these loaders.

import { compileQuery, isCompiledQuery } from 'graphql-jit';
| import { AggregateError } from '@graphql-tools/utils';
| import { getMesh } from '@graphql-mesh/runtime';
(node:46369) [DEP_WEBPACK_MODULE_ISSUER] DeprecationWarning: Module.issuer: Use new ModuleGraph API

To Reproduce
Steps to reproduce the behavior:

Install the latest next js with typescript
Install @graphql-mesh/cli, @graphql-mesh/graphql, @graphql-mesh/transform-prefix and graphql
Added "generate": "mesh build" and "mesh": "mesh dev" script in package.json
Added .graphql files
Run "npm run generate"
Run "npm run dev"

https://codesandbox.io/s/keen-shockley-n7zczo?file=/.mesh/index.js
Expected behavior

Environment:

OS:
@graphql-mesh/...:
NodeJS: node v16.13.2

Additional context

Solved by changing the type to module in .mesh > package.json
{   "name": "mesh-artifacts",   "private": true,   "type": "module",   "main": "index.js",   "module": "index.mjs",   "sideEffects": false,   "typings": "index.d.ts",   "typescript": {     "definition": "index.d.ts"   },   "exports": {     ".": {       "require": "./index.js",       "import": "./index.mjs"     },     "./*": {       "require": "./*.js",       "import": "./*.mjs"     }   } }
But it keeps getting back to commonjs after mesh build. Am I missing some configuration? Here's my .meshrc.yml
`documents:

./src/graphql/**/*.{gql,graphql}

sources:

name: GoldAU
handler:
graphql:
endpoint: http://<IP_ADDRESS>:30052/wp/graphql
transforms:

prefix:
mode: wrap
value: GoldAU_
includeRootOperations: true

name: BlueAU
handler:
graphql:
endpoint: http://<IP_ADDRESS>:31139/wp/graphql
transforms:

prefix:
mode: wrap
value: BlueAU_
includeRootOperations: true

name: GoldNZ
handler:
graphql:
endpoint: http://<IP_ADDRESS>:31333/wp/graphql
transforms:

prefix:
mode: wrap
value: GoldNZ_
includeRootOperations: true

name: BlueNZ
handler:
graphql:
endpoint: http://<IP_ADDRESS>:30038/wp/graphql
transforms:

prefix:
mode: wrap
value: BlueNZ_
includeRootOperations: true`

Fixed in the latest version


License update/request

Good Afternoon Professor Martin,
I was hoping to utilize this software for some of our research and development efforts. As an organization we cannot use unlicensed software. I was curious if adding an appropriate license or requesting explicit permission was possible?
Ideally an MIT/BSD/GNU license would allow the community to utilize software. Thanks in advance for your consideration.
-Joe

Thank you very much Francisco. :-)
On Mon, Aug 28, 2023 at 12:34 PM Francisco Martín Rico <
@.***> wrote:

Hi @joestg https://github.com/joestg
This package has an Apache 2.0 license
https://github.com/MOCAP4ROS2-Project/mocap4ros2_optitrack/blob/6db09a8a9048d7fe4b98dd56fcda2d9cad4eca85/mocap_optitrack_driver/package.xml#L13
Best
Francisco
—
Reply to this email directly, view it on GitHub
https://github.com/MOCAP4ROS2-Project/mocap4ros2_optitrack/issues/19#issuecomment-1696000072,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BAMNU6C2DVWCTGDYKB5AUJ3XXTCBDANCNFSM6AAAAAAZV72SMQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Check output consistency of .validate and similar

Came across an issue with the newest version where an output of .validate(), which I think was previously a pd.DataFrame is now a pd.Series.
Not a problem in itself - but scripts that then take this output and perform operations that only work with DataFrame will throw an error. - So backward compatibility is reduced.
In our case it was .drop(..., axis=1)  (i.e. drop columns), which is not possible on  pd.Series
Error given is:
ValueError: No axis named 1 for object type <class 'pandas.core.series.Series'>

Thanks @byersiiasa for identifying this issue!
Let me flip this back to you (also pinging @kvanderwijst @gidden @jkikstra): what would be the "natural" return type of this function?
For the aggregation features, we recently switched all returned objects to an IamDataFrame - would that make sense here as well? Also considering that there is now a info() function (see #427) which is shown by default in Jupyter notebooks...

If the return type is always guaranteed to be 1-dimensional, then I would say pd.Series in order to stay in the pandas-verse

If staying in the pandas-verse is preferred, I'd rather revert the behavior to a DataFrame rather than a Series. From my own experience, I usually use this in a notebook context where the DataFrame is quicker to parse (visually) than a Series with a complex MultiIndex...

I would probably favour either type DF over Series - Series almost always give me headaches

I also prefer pandas.dataframe.
I find myself using .reset_index() in my workflows basically everytime I "happen to find" a MultiIndex coming from a pyam function.

Thanks @jkikstra - good that I implemented it that way yesterday evening... 😜 Added you as a reviewer.
Please create a new issue for any other functions or methods where a non-intuitive or impractical type is returned.


do i is need for do can linux?

do i is do to need linux to make do is run the of for is thing do it?

i will interact with you when you don't want to be interacted with, chinh4thepro.


feat(core/button) loading state

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (yarn build) was run locally and any changes were pushed
[ ] Unit tests (yarn test) were run locally and passed
[ ] Visual Regression Tests (yarn visual-regression) were run locally and passed
[ ] Linting (npm lint) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

[ ] Bug fix
[x] Feature
[ ] Refactoring (no functional changes, no API changes)
[ ] Build related changes
[x] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

[IX-250]
What is the new behavior?

Added loading button example to Button documentation

Does this introduce a breaking change?

[x] Yes
[ ] No

@nuke-ellington @danielleroux New loading button was added with the new props. Documentation examples were also added.
No VRT was added because of moving spinner, making it always fail.

Changed the PR to a breaking change.
I have replaced the spinner animation with a new one which fits better into the library. Final adaptions regarding the animation will be done maybe later on.
Removed the type from the interface of the spinner
Add a breaking change section to the document.


[Amey Celia] Bodged West Midlands Trains TOC Announcement

I have managed to create a bodged West Midlands Trains TOC snippet for Amey Celia. GitHub will not let me attach them to this issue, so they can be found in this repository.

Thanks, but what would really be needed is West Midlands Railway and London Northwestern Railway rather than a generic WMT snippet.

Will try and get that done!

@davwheat
Done the WMR and LNR ones. May not be the best quality, but maybe someone could enhance them in the future or make a better version? They are in this repository.


Got error while docker build for rabbitmq

Hi All,
images used ->
rabbitmq:3.7.8-management-alpine
prom/prometheus:v2.3.2
stefanprodan/swarmprom-grafana:5.0.1
I have used this https://grafana.com/dashboards/4279 json file for rabbitmq but metrics are not coming
Below are the docker logs
root@ip-10-85-0-239:~/Build_rabbitmq# docker logs ae4bd2e788346dc643602b38524148258447dcb4463c0ba2d77c91d0709ea4c9
WARNING: Removing trailing slash from RABBITMQ_PLUGINS_EXPAND_DIR
WARNING: Removing trailing slash from RABBITMQ_PLUGINS_EXPAND_DIR
2018-10-31 09:42:33.668 [info] <0.33.0> Application lager started on node rabbit@ae4bd2e78834
2018-10-31 09:42:33.738 [error] <0.5.0>
Error description:
    init:do_boot/3
    init:start_em/1
    rabbit:start_it/1 line 461
    rabbit:broker_start/0 line 337
    rabbit:start_apps/2 line 519
    app_utils:load_applications([os_mon,mnesia,rabbit_common,rabbit])
error:undef
Log file(s) (may contain more information):
   <stdout>

BOOT FAILED
===========

Error description:
    init:do_boot/3
    init:start_em/1
    rabbit:start_it/1 line 461
    rabbit:broker_start/0 line 337
    rabbit:start_apps/2 line 519
    app_utils:load_applications([os_mon,mnesia,rabbit_common,rabbit])
error:undef
Log file(s) (may contain more information):
   <stdout>

init terminating in do_boot (undef)
{"init terminating in do_boot",undef}

Crash dump is being written to: /var/log/rabbitmq/erl_crash.dump...done

Please let me how to fix this issue.
Thank you in advance.

FYI...  inside rabbitmq docker container
/opt/rabbitmq/plugins # rabbitmq-plugins list | grep prome
[E*] prometheus_rabbitmq_exporter      <IP_ADDRESS>
/opt/rabbitmq/plugins #

hi, I would say I need more logs

I have pasted above docker logs while docker run the image.

Fixed in dockerfile itself


Search

Why is your search bar gone!
I'm loving the icons, such a bummer I can't search anymore ...

Oh yeah, even I noticed that. Lemme fix it off. :)

Thanks! 😄

search was not in the generator file. when I generated new doc it was gone.
:(
On May 4, 2016 8:17 PM, "Neeltje Chanterie"<EMAIL_ADDRESS>wrote:

Thanks! 😄
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/thesabbir/simple-line-icons/issues/49#issuecomment-216879049

Fixed it. :+1:

Awesome! Thanks for the quick replies!

 :)

Thanks @praveenscience
We generate docs automatically with this file
php genarate.php > index.html

So changing index.html is not effective if we generate docs for new icons.

@thesabbir I'll take care of it as well... ;)


Update prediction probability list concatenation in VQC code

Summary
Using the return value of numpy.concatenate() to update prediction lists.
Details and comments
As reported in issue #733 , this bug is fixed with the small changes below.

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

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

@ezeeEric Would you please sign the CLA via the link in the CLAassistant message above. Submissions cannot be accepted until author(s) have signed this.

Hello @woodsp-ibm, unfortunately there seems to be a problem with signing the CLA. I tried several times (also initially when setting up this PR) and successfully signed it. However, the check here does not update. I might close this and reopen the PR.
Thanks for checking,
Eric


Type testing stubs for generic types with type parameters do not fully test types of type parameters

import "package:expect/expect.dart";

class A<T> {
  test(x) => x as B<T>;
}

class B<T> {
}

class C<T> {
}

main() {
  final a = A<C<int>>();
  a.test(new B<C<int>>());
  Expect.throwsCastError(() => a.test(new B<C<num>>()));
}

This test fails in AOT mode (but works in JIT):
pkg/vm/tool/precompiler2 foo.dart foo.snapshot && pkg/vm/tool/dart_precompiled_runtime2 foo.snapshot
Unhandled exception:
Expect.throws(CastError) fails: Did not throw
#0      Expect._fail (package:expect/expect.dart:682)
#1      Expect.throws (package:expect/expect.dart:585)
#2      Expect.throwsCastError (package:expect/expect.dart:598)
#3      main (file:///.../foo.dart:17)
#4      _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:301)
#5      _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:168)

This happens because type testing stub for a generic type with type parameter B<T>, when testing if B<X> is assignable to B<T>, only tests if X.type_class_id == T.type_class_id, but it doesn't test that X.arguments are compatible with T.arguments.
https://github.com/dart-lang/sdk/blob/bef363bfb7d6364ddbaabd691c0fdc963cff8cc6/runtime/vm/type_testing_stubs.cc#L437-L446
/cc @mkustermann

/cc @crelier

I can take a look at this.

Thanks Martin!

I think this should be fixed now.


[BUG]: DetailsList - Automatic sorting functionality does not work when working with delegable functions in "Items"

Description of the bug
When I reference a Dataverse-table (using a simple, delegable SortByColumns(Filter())-function), the data that is returned is not sorted according to the parameters set in the SortByColumns-function, nor the sort order defined in a referenced Dataverse-view.
The sorting-functionality works fine when I manually click on the column header of the DetailsList - but the point of the SortByColumns-functions is to make sure that the data is pre-sorted when the user navigates to the screen.
When manual sorting-functionality (which is imposed when I am working with a local collection or a non-delegable function) also works fine.
To reproduce
Steps to reproduce the behavior:

Add a delegable function to "Items" that references a Dataverse-table (DO NOT reference a local collection / table), and use SortByColumns to sort the records by name. Make sure to have a suitable number of records (+10) in the table.

Example: SortByColumns(     Filter(         'Checklist steps',         Checklist.'Checklist ID' = GLOBVARChecklistRecord.'Checklist ID'     ),     "cgi_stepnumber",     SortOrder.Ascending )

Add the column that is being sorted to the column_Items property, so that it is being displayed.

Confirm the unintended behaviour.

@denise-msft Please provide solution how to set default sorting by Descending in DetailsList based on Dataverse data. Because autosorting by default sort by Ascending!


Cursor in notebook cell lose focus after toggle on & off the terminal pane

Bug: Notebook Editor, Interactive Window, Editor cells
When editing a normal .py file, I can use the default shortcut Ctrl-` to toggle the terminal. When I toggle on the terminal and toggle off the terminal, my cursor focus would go back to the previous spot in the .py file. But when my cursor is focus on a notebook cell list or cell and I toggle on, off the terminal, my cursor focus will be neither cell list nor cell, I have to use the Left key on the mouse to select the list or the cell to activate the cursor.
Steps to cause the bug to occur

Cursor in a notebook cell.
Toggle on the terminal(Ctrl - `)
Toogle off the terminal(Ctrl - `)

Actual behavior

Cursor not in the previou position of the notebook cell.

Expected behavior
4.Cursor in the previou position of the notebook cell.
Your Jupyter and/or Python environment
Please provide as much info as you readily know

**Jupyter server running: Local
**Extension version: 2020.8.101144
**VS Code version: 1.48.0
**Setting python.jediEnabled: false
**Setting python.languageServer: None
**Python and/or Anaconda version: Python 3.8.5
**OS: macOS 10.15.6
**Virtual environment: venv

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

Thanks for the bug report! This is likely because our existing notebook viewers are implemented as a webview and so are not first-class editors in VS Code. This issue will be addressed when VS Code adds native support for editing notebooks. Please see https://github.com/microsoft/vscode/issues/91987 for more information.


Setting id frontmatter unexpectedly affects the published path of a document

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Description
We recently discovered that setting id in the frontmatter has the same effect as setting slug, specifically it will set the path of the document to /{id} instead of /{filename}.
The documentation describes this value as "A unique document ID.", and does not mention this important side effect.
I was able to track this down to https://github.com/facebook/docusaurus/blob/main/packages/docusaurus-plugin-content-docs/src/docs.ts#L143, but I am still unclear about the intent of reading frontMatter.id here and using it instead of unprefixedFilename if it exists.
So, I am not sure if this is a bug, or a documentation issue.  I think if there's already a way to override using the filename as the path (by setting slug frontmatter), setting id should not also change it.  If this is intentional for whatever reason, we should update the documentation to mention that setting this will also change the path.
Self-service

[X] I'd be willing to address this documentation request myself.

To me, this is a documentation issue on a historical behavior. We may revisit the behavior but after all these years you are the first to open an issue, so I guess it must be fine 😄
Changing the behavior would be a breaking change, so it's better to document it for now.
I guess we could mention that here: https://docusaurus.io/docs/create-doc#doc-urls
If you want stable URLs, you'd rather always use slug.


components.d.ts cannot work with Nuxt3

Describe the bug
If enable unplugin-vue-components, the types of components that are auto-imported by Nuxt is lost.
Reproduction
https://github.com/kaikaibenkai/unplugin-vue-components-demo-657
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (6) x64 AMD Ryzen 5 4500U with Radeon Graphics
    Memory: 1.42 GB / 7.23 GB
  Binaries:
    Node: 18.15.0 - C:\nodejs\node.EXE
    Yarn: 1.22.19 - C:\nodejs\yarn.CMD
    npm: 9.6.4 - C:\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.1992.0), Chromium (114.0.1823.79)
    Internet Explorer: 11.0.22621.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Is there a reason why you would want to use this plugin in Nuxt?

Is there a reason why you would want to use this plugin in Nuxt?

Because auto-import of Arco Design only supports this plugin, if I use Nuxt auto-import, I must fully import Arco Design, causing the package volume to expand.

hi, you can try:

patch the nuxt.config.ts

export default defineNuxtConfig({
  ssr: false,
  components: false,
  vite: {
    plugins: [
      Components({
        dts: true,
        dirs: ['components'],
        directoryAsNamespace: true,
        resolvers: [
          ArcoResolver({ resolveIcons: true }),
        ],
      }),
    ],
  },
});

patch the tsconfig.json

{
  // https://nuxt.com/docs/guide/concepts/typescript
  "extends": "./.nuxt/tsconfig.json",
  "include": [
    "./.nuxt/nuxt.d.ts",
    "**/*"
  ]
}


Don't break up JSXOpeningElement if it only has a single text attribute

Addresses a pain point mentioned in https://github.com/jlongster/prettier/issues/467 according to an algorithm proposed by @vjeux in https://github.com/jlongster/prettier/issues/467#issuecomment-275230393
specifically, don't break opening elements such as
<div className="i use bootstrap and just put loooaads of classnames in here all the time">
  hello world
</div>

Looks good to me, I'll let @jlongster review if we want this feature in or not.

Sounds good. It feels good to me. Thanks!


Container size

My Dockerfile
FROM gliderlabs/alpine
RUN apk-install alpine-sdk
RUN apk del alpine-sdk

After build container is 139.6Mb in size. Tried using with different packages, result is same. Tried using --virtual pak option. Tried to build on my machine and on docker hub. Any advice? My goal is to install build dependecies and remove then after building packages from sources.

You need to do those operations in the same RUN command or they will result
in additive two layers.
On Tue, Feb 17, 2015 at 3:11 AM, V<EMAIL_ADDRESS>wrote:

My Dockerfile
FROM gliderlabs/alpine
RUN apk-install alpine-sdk
RUN apk del alpine-sdk
After build container is 139.6Mb in size. Tried using with different
packages, result is same. Tried using --virtual pak option. Tried to build
on my machine and on docker hub. Any advice? My goal is to install build
dependecies and remove then after building packages from sources.
—
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/docker-alpine/issues/6.

--
Jeff Lindsay
http://progrium.com

Thanks


[Statistics] Reduce DB size by removing unused data - original UserAgent-strings

This data is not used in any functionality today. We only track it because we have the data available at w3c-log parsing time, and it could be useful from operational point of view. So far, we only used this once to correct a few parsing errors in the early days of this parser - to avoid having to deal with reimporting a huge set of data. It is questionable in terms of cost-effectiveness, as well as usefulness (as we only retain 6 weeks of data, parsing errors will heal itself over time).
We could still store it elsewhere for operational purposes (e.g. in Azure table storage). Or we could reconsider storing this data when revisiting the design of the NuGet statistics feature.

Note
Even when we no longer import these datapoints into the stats database, we still have all the data in the w3c-logs we upload to blob storage.

Impact on database
A database size reduction could be achieved totalling 55,672.16 MB (or 54.37 GB)!
Removing these indices will also improve performance of insert/delete operations against the [dbo].[Fact_Download] and [dbo].[Fact_Dist_Download] tables.
In addition, we generate less churn on the data by avoiding clean-up operations.
The following database objects would become obsolete:

Table [dbo].[Fact_UserAgent] (size = 29.65 MB)
Table column [dbo].[Fact_Download].[Fact_UserAgent_Id] (size = 2,585.75 MB)
Table column [dbo].[Fact_Dist_Download].[Fact_UserAgent_Id] (size = 23.63 MB)
Stored procedure [dbo].[CleanupFactUserAgent]
Stored procedure [dbo].[EnsureUserAgentFactExists]
Stored procedure [dbo].[PatchClientDimensionForUserAgent]
SQL Type [dbo].[UserAgentFactTableType]
Non-clustered index [dbo].[Fact_Download].[Fact_Download_NCI_UserAgent] (size = 52,560.89 MB)
Non-clustered index [dbo].[Fact_Dist_Download].[Fact_Dist_Download_NCI_UserAgent] (size = 472.24 MB)

The following database objects would decrease in size:

Non-clustered index [dbo].[Fact_Dist_Download].[Fact_Dist_Download_NCI_Client] would no longer need to include the Fact_UserAgent_Id column, or would perhaps also be obsolete.
Non-clustered index [dbo].[Fact_Download].[Fact_Download_NCI_Client] would no longer need to include the Fact_UserAgent_Id column, or would perhaps also be obsolete.

Impact on jobs
The Stats.ImportAzureCdnStatistics job would still need to parse the original user agent strings, however, it would no longer need to store the original data, which would improve import speed, throughput, and overall performance of the job.
We could:

avoid the need to check whether a UserAgent string already exists, and if not, create it during import;
avoid the need to retain already imported UserAgent facts into in-memory cache;
reduce complexity of import by no more linking original UserAgent-string identifiers to the download facts.

The Stats.RefreshClientDimension job would become obsolete. This job is the ad-hoc executable to patch a client dimension when a parsing error in user agent strings needs to be fixed.

We decided to go in a different direction to reduce DB size. Will reopen if needed.


Add nested buckets.

Overview
This pull request adds the ability to nest buckets inside of other buckets. It also replaces the buckets page with a root bucket. This pull request looks bigger than it is. It's mostly moving a lot of Tx functionality over to the Bucket.
API Changes
Previously, the ability to create, retrieve, and delete buckets was entirely in Tx and buckets. This made sense because buckets were a top-level construct. Now that buckets can exist inside other buckets, all this functionality has moved into the Bucket type.
Buckets and simple byte slice values all exist in the same keyspace. However, trying to create a bucket named foo and simple value with the foo key will return an ErrIncompatibleValue error.
New Bucket functions:
func (b *Bucket) Bucket(name []byte) *Bucket
func (b *Bucket) CreateBucket(key []byte) error
func (b *Bucket) CreateBucketIfNotExists(key []byte) error
func (b *Bucket) DeleteBucket(key []byte) error

Changes in Bucket functions:

Bucket.Get() returns nil when a bucket key is provided.

Bucket.Put() returns ErrIncompatibleValue when putting to an existing bucket key.

Bucket.Delete() returns ErrIncompatibleValue when deleting an existing bucket key.

Tx functions
All the previous Tx bucket functions still exist and simply wrap the root bucket's same functions:
func (tx *Tx) Bucket(name []byte) *Bucket
func (tx *Tx) CreateBucket(name []byte) error
func (tx *Tx) CreateBucketIfNotExists(name []byte) error
func (tx *Tx) DeleteBucket(name []byte) error

However, since buckets are in the regular keyspace, their names are byte slices instead of strings.
File Format Changes
Allowing buckets to be nested made the buckets page redundant. Now, instead of a specialized page type, there is a root bucket that the Tx uses to find and create top-level buckets. This root bucket is only accessible to the Tx so it only stores buckets (e.g. no simple byte slice values).
Because of this change, older Bolt databases are not compatible after this pull request is merged. I'll be merging in an import/export tool through a separate PR before this pull request is merged. That will allow databases to be exported to a generalized JSON format and imported into a new version of Bolt.
The data format version has been bumped to 2 with this PR. Opening previous data format versions of the database will return ErrVersionMismatch error.
Upgrading
To upgrade a Bolt database that uses the previous version (1), you'll need to install Bolt from the data/v1 tag:
$ cd $GOPATH/src/github.com/boltdb/bolt
$ git fetch origin
$ git checkout "data/v1"
$ go install ./cmd/bolt
$ bolt export path/to/db > dump.json

Then install Bolt from master:
$ git checkout master
$ go install ./cmd/bolt
$ bolt import --input dump.json path/to/newdb

Now you can swap out your old database:
$ mv path/to/db path/to/db.bak
$ mv path/to/newdb path/to/db

Other Notes
This pull request lacks a few optimizations that will be coming in future PRs:

Inline buckets (#124) - Currently buckets require their own root page. Inlining buckets would allow small buckets (< pageSize) to be written with their data into the same value that their bucket header exists.

Allocations (#125) - Currently subbuckets require allocation of a Bucket for access. This is mostly to track nodes for each bucket but that shouldn't be required for read-only transactions. Tweaking this should make iteration faster for nested buckets.

Cursor Reuse (#126) - If someone is iterating over two levels of buckets then they should be able to only allocate two cursors and reuse them for each level. Currently Bolt requires a new cursor after every change in a higher level bucket.

Fixes #56.
/cc @tv42 @snormore @mkobetic

I don't see in the docs or in the tests how to traverse the bucket trees (i.e. nested buckets). It seems when cursor or ForEach hits upon a sub-bucket key it returns the value as nil. Is that the only case where you can get nil; i.e., if you see nil value in that context is that guaranteed to be a subbucket? And then how do you access the sub-bucket to traverse it? I guess it's actually stored at the root level of the db? Meaning all buckets actually share that one namespace and you have to worry about naming collisions among all subbuckets and top level buckets?  I'd be happy to work on embellishing the documentation with this stuff if you welcome contributions like that.
Awesome software btw, thank you for open sourcing :)

http://godoc.org/github.com/boltdb/bolt#Cursor
"Cursors see nested buckets with value == nil."
http://godoc.org/github.com/boltdb/bolt#Bucket.Bucket
"Bucket retrieves a nested bucket by name."

Oh, right, Bucket.Bucket. Thanks.


Generated package: single vs multiple packages

There are two major ways to generate the photon client. It could be generated into a single file, but it could also be generated into separate packages, i.e. a photon package plus one package per model.
1) Single File
The client will be generated in a single file, e.g. prisma/photon_gen.go.
This is a simple approach where you can access anything photon-related by importing "photon".
Example directory structure
prisma/
  photon_gen.go
main.go

Example
import (
  "github.com/org/repo/photon"
)

func main() {
  client := photon.New()

  user, err := client.User.FindOne(
    photon.User.Email.Equals("hi@prisma.io"),
  )
}

Notes

Very simple approach. One file contains everything you need.
You can simply use a "." import if you don't want to type "photon." all time
since User is already used for the User query builder, it clashes with the actual User result struct which now has to be named UserObject or UserResult

2) Multiple packages
The client will be generated in multiple files.
Example directory structure
photon/
  client.go
  tx.go
  user/
    user.go
  user_query.go
  group.go
main.go

...
photon/
  photon_gen.go
  user/
    user_gen.go
  post/
    post_gen.go

The photon package contains the basic API to call CRUD functions like FindOne, Update, Delete, etc., as well as helper methods for nullability or common enums such as Order.ASC.
The model packages contain the mapped Go struct and all related query functions.
Example
import (
  "github.com/org/repo/photon"
  "github.com/org/repo/user"
)

func main() {
  // the photon package contains common structs and functions
  client := photon.New()

  usr, err := client.User.FindOne(
    // since this is a query for the user model, we can use the user package here
    user.Email.Equals("hi@prisma.io"),
  )
}

This makes the API slightly cleaner because you can access model-specific query functions.
Notes

It results in typing fewer chars (typing user. instead of photon.User), but you can just use dot imports for the photon package and save yourself the trouble of multiple packages.

Caveats with multiple packages
There are many drawbacks of having multiple packages:

The user package clashes with the usual variable name user, which forces you to name it differently, for example usr. That is against the philosophy of Go: don’t use package names which clash with common variable names.
Multiple imports. Users may get confused about many packages and when to use which. If it's a single package, they can just type photon. and get editor completions on what they can type.
Common practice. Other code generators, let it be google/wire or 99designs/gqlgen, always output to a single file because codegen always works like “helpers” or “additional code”.
What if a model gets deleted? The user would have to clean it up manually*

*We could solve that by re-creating the photon/ folder from scratch each time, but this would mean it would be isolated from any other code. This would mean we would have to delete the directory, which may result in confusing and unwanted behavior, like file system issues (recursively deleting files, accidentally deleting /) or accidentally deleting user code. This also means that users could not add anything to the photon package, which some users may want. For example, you may want to extend a User type to an Admin and Moderator type, and then you could add your own functions in your own user.go file in the same photon package. See #4 for more information as this is closely related.
Related:

photon code mutability
gqlgen: Split generated stubs into multiple files
ent go generates multiple packages, but does not re-create everything from scratch

I prefer having all the generated code in a singe file.
I use wire for dependency injection which means that I need to have a provider function which returns the completely configured prisma client.
func NewClient() *Client {
  return New(&Config{
    Endpoint: "..."
    Secret: "..."
    // ...
  })
}

With the Prisma 1 Client I would always put this provider function in the same package along with the generated client. I would like being able to do that with the new client as well.

For now, we have decided to use a single package for the reasons listed in the original issue.


Loading YAML configuration should default to an empty hash

On Heroku, running#yaml_config raises an exception, as it attempts to call #symbolize_keys on nil. In general, any attempt to load the YAML configuration that fails should return an empty configuration.

Dossier doesn't work on Heroku for me at all.
Not sure if this is related:
rake aborted!
No such file or directory @ rb_sysopen - /app/config/dossier.yml. /app/config/dossier.yml must exist for Dossier to connect to the database.
/app/vendor/bundle/ruby/2.1.0/gems/dossier-2.12.2/lib/dossier/configuration.rb:32:in `rescue in setup_client!'

I can report that this does in fact fix the incompatibility with Heroku.  It breaks the test suite... but that's because the test suite is broken.  Until this all gets resolved upstream this fork is the one to use on Heroku.
cc @adamhunter

Hey Guys,
Sorry for the incredible delay in handling this.  I'm sure this is well outdated for your use case but this has been resolved in https://github.com/adamhunter/dossier/commit/64f657a8b15f2d138c54efeeaf27bb5491ffc5ec
I'll be doing a release later today.  Thanks!!

Awesome!  Will check it out!  CC @brettfishman


agent->kafka->collector->elasticsearch

I think this framework may be better:
agent->kafka->collector->elasticsearch
use kafka as a buffer, so collector can be deploy as cluster.
elasticsearch is easily to search, and can be easily integrated with kibana, grafana.

stagemonitor.org write this article: https://www.elastic.co/blog/elasticsearch-as-a-time-series-data-store

Hi qifuren1985,
Adding kafka did come up a few times internally, but we haven't decided to add it to the pipeline to keep it simple. Adding kafka also entails a lot of work as we'll have separate out connections for span/stat data (which points to kafka) and connections for real-time data (which needs a connection directly to the collector).
Also, there can already be multiple collectors if they're behind a l4.
Elastic search backend does look attractive - we'll take a closer look into this.
You can always experiment with it and throw us a PR as well! if you've got something going :)
Thanks.


JLink probe interface always uses SWD for ARM targets

When attaching without a specified target, probe-rs tries to automatically determine the connected chip.
Actual Behaviour
When this is done with a connected J-Link, it will first try to detect a connected ARM chip. For this,
the DAPAccess trait is used. The implementation for J-Link uses SWD specific function. When these functions are used, the probe automatically tries to to switch to the SWD protocol. However, not all J-Links support this switch. If the connected probe does not support switching protocols (i.e. capability SELECT_IF is missing), this leads to an error. This error means that auto-detection fails, and the connection procedure is aborted. The following error is shown, if the probe only supports JTAG:
Error processing command: An error with the usage of the probe occured: An error specific to a probe type occured: device is missing capabilities (SELECT_IF) for operation

Expected behaviour
If detecting an ARM chip fails, we should still try detecting a RISCV chip. Also, if auto-detection fails, the error should clearly indicate this.

Fixed by #204 .


Fine tuning task: Predicting Diabetes patient risk to develop Heart Failure with Med-BERT

Can you please clarify after converting the pretrained model to Pytorch, is there any additional step?
I am not able to understand the input for the following in the fine tuning model definition.

self.PreBERTmodel=BertForSequenceClassification.from_pretrained("pretrained_py_models/45M_chk"

)
The output of converting model from TenforFlow to Pytorch was a .bin file but the above code uses something different.

The path used is the path for the model folder containing both the model checkpoint (.bin) and the configuration file (config.json)


Add liquidDoc tag to liquidHTMLParser

--wip-- [skip ci]
--wip-- [skip ci]
What are you adding in this PR?

What's next? Any followup issues?

What did you learn?

Before you deploy

[ ] This PR includes a new checks or changes the configuration of a check

[ ] I included a minor bump changeset
[ ] It's in the allChecks array in src/checks/index.ts
[ ] I ran yarn build and committed the updated configuration files

[ ] If applicable, I've updated the theme-app-extension.yml config

[ ] I included a minor bump changeset
[ ] My feature is backward compatible

[ ] I included a patch bump changeset

#621  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


docs: use vitepress features

I kind of like the functionality to switch between inputs and outputs, but with this we can't use embedme.
I think the codeblocks are improving the experience and that this wins of the functionality that embedme provides. Ideally, we just have to write the examples once and update them when we make significant changes. A small nit, is that I don't like the comment as first line e.g. // examples/create-fixture-extension.test.ts#L2-L36 because that also makes in into the visible docs.
Thoughts?

Someone recommended https://github.com/SimonCropp/MarkdownSnippets for the snippets 👀

It looks like VitePress handles snippets already.
The reason I liked embedme was because it was pulling from actual code, which means the code is guaranteed to work and, with inline snapshots, the output is also guaranteed to match. Ideally, anywhere we include code snippets will be code that's been linted and output that's been verified.
I'm not a fan of the ::: in the markdown.
Apparently VitePress uses markdown-it, so it's possible we could write our own plugins and build step that outputs cleaner README.md.

Seems like the vercel integration is not 100%, you can preview it via https://zod-fixture-git-vitepress-features-timdeschryver.vercel.app/README


Modal to display game instructions and header to display username and score in the DOM

Created a modal that displays game instructions 2seconds after page load, and a form to take username. When a user submits, it then displays the user name and score in the dom

Went through it and it looks solid!

I don't think we should actually block the game until a name is input. The name can be optional, we're not storing it anywhere so it's not necessary to have it. It's just a little something extra.

The name submission also triggers for the score to be displayed in the DOM


Improve PyTest Fixtures

🐞 Bug Report
The PyTest fixtures are a great addition to this project, however they are getting unwieldy in the ever growing and unorganized conftest.py file.
Desired outcomes of a PR that resolves this issue:

better test modularity/isolation

Right now all test modules pretty much have access to all trak app fixtures. For maintainability purposes, it would be good if the test modules did not have to know about each other.
The models in general are relatively entangled, we may need to duplicate some fixtures or employ factory style implementation to help abstract away the details of other models.

better test readability

Right now, if you want to inspect a fixture used by a test, you need to navigate to conftest.py and search the long file for the fixture. Ideally, we store the fixtures in the same file or module of the tests that uses them

consistent fixture naming conventions

Improve the readability, maintainability, preferably less verbose, by applying a consistent naming convention and remove

If we can get the size of the conftest.py file down to only fixtures that are used by the entire trak app, and store the remaining fixtures in the test files that use them, that would be great.

An option, use conftest as a space to implement our package level fixtures using a factory as a fixture pattern. We can then use those as factories to create file/class level fixtures locally. These means the class can be in charge of creating its own fixtures, it's readable, isolated, and will cut down on the boilerplate (even if it increases the complexity a little bit). Wet can include a blurb in the documentation.


Fix POINTER_INPUT_TYPE missing initial value

According to MSDN: tagPOINTER_INPUT_TYPE enumeration (winuser.h) , the POINTER_INPUT_TYPE enum's value is starting at 1.
But in the code, it missing the initial value, which makes its value from starting at 0 by default.

Thank you!


Added a new parse util method to avoid repetition / refactored code with new method

Description
This change adds a static util method that helps with reusing a piece of code and avoids repetition for the future
Issues Resolved
Will resolve [FEATURE] Create a new Util method for a common pattern -> https://github.com/opensearch-project/flow-framework/issues/720
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Yes, i will get on it !
On Thu, 30 May 2024 at 18:50, Daniel Widdis @.***>
wrote:

@.**** commented on this pull request.
Thanks for your contribution! This looks great!
Note there's 2 more changes upcoming in #718
https://github.com/opensearch-project/flow-framework/pull/718, so if
that gets merged first you can update, or if your PR gets merged first than
@owaiskazi19 https://github.com/owaiskazi19 can update. :)
Can you make a few naming changes to make the method more generic? Also we
need to add a CHANGELOG entry and add a unit test in ParseUtilsTest?
In src/main/java/org/opensearch/flowframework/util/ParseUtils.java
https://github.com/opensearch-project/flow-framework/pull/721#discussion_r1620988682
:

@@ -472,4 +473,8 @@ public static Map<String, String> convertStringToObjectMapToStringToStringMap(Ma
return stringToStringMap;
}
}

public static Boolean checkIfInputsContainsKey(Map<String, Object> inputs, String enumKey){

This method is good but the naming implies we're just checking whether the
key exists. How about parseBooleanIfExists or something similar?
Also as a more generic util method it may not be "inputsso just a more
generic map variable name; and the key may be a string constant, not
necessarily an enum so justkey` probably works there.
This needs a Javadoc added explaining what the method does.
—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/flow-framework/pull/721#pullrequestreview-2088701028,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU52WT3KIH4TJ2IVMRBZPBDZE5DD3AVCNFSM6AAAAABIQ4AWA6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAOBYG4YDCMBSHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

this is a good suggestion! But to be right instead of

       return Float.parseFloat(value.toString());

it should be

       return type.cast(Float.parseFloat(value.toString()));

i will push the changes now!
On Sat, Jun 1, 2024 at 1:49 AM Owais Kazi @.***> wrote:

@.**** commented on this pull request.
In src/main/java/org/opensearch/flowframework/util/ParseUtils.java
https://github.com/opensearch-project/flow-framework/pull/721#discussion_r1623005339
:

/**

* Checks if the inputs map contains the specified key and parses the associated value to a generic class.

*

* @param inputs the map containing the input data

* @param key the key to check in the map

* @param type the class to parse the value to

* @return the generic type value associated with the key if present, or null if the key is not found

*/

public static  T parseIfExists(Map<String, Object> inputs, String key, Class type) {

   if (!inputs.containsKey(key)) {

       return null;

   }

   Object value = inputs.get(key);

   if (type == Boolean.class) {

       return type.cast(Boolean.valueOf(value.toString()));

⬇ Suggested change

       return type.cast(Boolean.valueOf(value.toString()));

       return Booleans.parseBoolean(value.toString())

In src/main/java/org/opensearch/flowframework/util/ParseUtils.java
https://github.com/opensearch-project/flow-framework/pull/721#discussion_r1623005746
:

*

* @param inputs the map containing the input data

* @param key the key to check in the map

* @param type the class to parse the value to

* @return the generic type value associated with the key if present, or null if the key is not found

*/

public static  T parseIfExists(Map<String, Object> inputs, String key, Class type) {

   if (!inputs.containsKey(key)) {

       return null;

   }

   Object value = inputs.get(key);

   if (type == Boolean.class) {

       return type.cast(Boolean.valueOf(value.toString()));

   } else if (type == Float.class) {

       return type.cast(Float.valueOf(value.toString()));

⬇ Suggested change

       return type.cast(Float.valueOf(value.toString()));

       return Float.parseFloat(value.toString());

—
Reply to this email directly, view it on GitHub
https://github.com/opensearch-project/flow-framework/pull/721#pullrequestreview-2091801963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AU52WT2W4Z2DM4BKW7PNHMLZFD46RAVCNFSM6AAAAABIQ4AWA6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAOJRHAYDCOJWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

@martinpkr you also need to amend your changes with -s for the DCO check to pass.
git commit -s --amend

@martinpkr thanks for your patience working through code review!   one note: you do need to sign your commits with DCO (Signed-off-by: Your Name youremail@example.com).  If committing on git command line just use -s assuming you've configured your name and email in git.
Also be sure to run ./gradlew spotlessApply and add a change log entry!

add a change log entry!

@dbwiddis since this PR just adds a util method, we can ignore the CHANGELOG. Wdyt?

Signed off my commits and did an changelog entry for the issue, tell me if there is anything else .

Signed off my commits and did an changelog entry for the issue,also fixed the javadoc to include info about , tell me if there is anything else .

Just ./gradlew :spotlessApply is left and we should be good to merge this.

Signed off my commits and did an changelog entry for the issue,also fixed the javadoc to include info about , tell me if there is anything else .

Just ./gradlew :spotlessApply is left and we should be good to merge this.

just done that , see if everything is okay now... first time using gradle, so i'm sorry for the confusion.


Investigate allowing headings within table captions

What
Investigate whether allowing headings within table captions may make it easier for users to understand the hierarchy of information on a page or to navigate the page.
Why
Captions are styled similarly to headings, but are not headings so do not show up in headings lists and are not included when navigating using headings in screen readers.
The content model for the caption element allows for any flow content, which includes headings, so it's a valid thing to do according to the HTML spec.
Assumptions
Including a heading within the caption does not affect the role of either the caption or the heading, nor how they are communicated to users of assistive technologies.
Timebox
TBC
Who is working on this?
Spike lead: TBC
Spike buddy: TBC
Questions to answer

Is there any established best practise around this?
Do users expect to see table captions included in the list of headings, or to expect them to act as headings e.g. for navigation?
In which scenarios does it make sense to put a heading in a caption, if any?
What changes do we need to make to allow headings in captions?

Done when

[ ] Questions have been answered or we have a clearer idea of how to get to our goal
[ ] Findings have been reviewed and agreed with at least one other person
[ ] Findings have been shared, e.g: via a write-up on the ticket, at a show & tell or team meeting

Here's a bit of investigation work I did into the theoretical and fundamental question of: can heading elements be used within table caption elements?
there doesn’t appear to be any specification-level issue with having a heading <h*> element inside of a .
I think we’d want to test it with screen readers though, just to be sure screen readers are interpreting headings within captions as just regular ol’ headings.
It’s probably best to check this stuff before making a decision on allowing headings inside captions:

do screen readers list the heading in the list of headings they produce?
do screen readers use the caption content as the label for the table in the list of tables they produce?

After that, here's some questions we may want to add to our guidance, for teams whenever using headings inside captions across varying services:

does the heading styling conflict with local caption styling?
does the heading styling look exactly like all other captions when it’s within a caption?
does the heading within the caption’s content-writing style match that of the rest of the headings on the page?

Here's some things it’s probably best to disallow (likely via guidance) if a heading is inside a caption:

no custom caption styling (background colours, italics, etc.
no multiple flow content elements within that caption

for example, no heading then followed by a paragraph, all wrapped inside a caption. If you need paragraph or any other text between the heading and the start of the table, then make a separate heading and caption.

Places I checked for evidence for or against heading elements inside of caption elements:

HTML spec caption element
MDN page on
Ctrl+F scan of the WCAG 2.x techniques index
WCAG 2.1 quick reference guide filtered to just criteria relevant to headings


V3.9.0

Version 3.9.0
New features

Optional track and show status of input signals to e.g. show them in UI

Improvements

Status of the input signal of signal links (running via cFlow) is now provided additional via 'OnNewFlowInputState[ENUM]'-event.

Bugfix

Removed signal links were not set to SCRIPT mode

Following tasks were checked

[x] Module is coded and structured according to the "Developing guideline for modules" described within the CSK documentation
[x] All functions/events/parameters are documented within the manifest documentation
[x] The manifest description of the main CROWN includes main information about the purpose of the module and how to use it in general
[x] API docu based on the manifest was created and stored within the "docu"-folder of the repository
[x] Internal LUA code documentation exists for variables and non served functions
[x] All relevant infos are logged via the SharedLogger 'ModuleLogger'
[x] Module supports persistent data feature based on 'CSK_Module_PersistentData'
[x] Module supports user management based on 'CSK_Module_UserManagement'
[x] No open "ToDos" within the code or at least clearly explained comments why they exist...
[x] "Version" key in app manifest was updated following semantic versioning (and use '0.x.y' for test / experimental modules which are not yet ready to be officially released)
[x] Meaningful IDs used for UI elements
[x] Module was tested on an AppSpace device (at least on SICK AppEngine) with no error message
[x] README.md is up to date (incl. info of device + firmware the module was tested with)
[x] CHANGELOG.md is up to date

Many thanks to golluroSICKAG for this contribution!


rbenv install 2.3.4 fails on High Sierra

rbenv install 2.3.4                                                                                ⏎
Downloading ruby-2.3.4.tar.bz2...
-> https://cache.ruby-lang.org/pub/ruby/2.3/ruby-2.3.4.tar.bz2
Installing ruby-2.3.4...
ruby-build: use readline from homebrew

BUILD FAILED (OS X 10.13 using ruby-build 20170523)

Inspect or clean up the working tree at /var/folders/4m/2vw_y7pj1m77shz3hqskwn7h0000gn/T/ruby-build.20170709224713.53134
Results logged to /var/folders/4m/2vw_y7pj1m77shz3hqskwn7h0000gn/T/ruby-build.20170709224713.53134.log

Last 10 log lines:
installing capi-docs:         /usr/local/var/rbenv/versions/2.3.4/share/doc/ruby
The Ruby openssl extension was not compiled.
ERROR: Ruby install aborted due to missing extensions
Configure options used:
  --prefix=/usr/local/var/rbenv/versions/2.3.4
  --with-readline-dir=/usr/local/opt/readline
  CC=clang
  CFLAGS= -O3 -Wno-error=shorten-64-to-32
  LDFLAGS=-L/usr/local/var/rbenv/versions/2.3.4/lib
  CPPFLAGS=-I/usr/local/var/rbenv/versions/2.3.4/include

Having same issues as well

@lvnilesh @nebtrx https://github.com/rbenv/ruby-build/issues/377#issuecomment-310569462

It's ruby-build issue. I will close this.


Feature

As this is a solo tutorial project, it doesn't need review, so I will simply merge.

Good job!

This project's status is APPROVED!!
Congratulations and good luck on your next projects!

Project Status: WELL DONE!


dashboard supports incremental backup

What type of PR is this?

[ ] bug
[ ] feature
[ ] enhancement

What problem(s) does this PR solve?
Issue(s) number:
Description:
How do you solve it?
Special notes for your reviewer, ex. impact of this fix, design document, etc:

https://github.com/vesoft-inc/nebula-dashboard-ent/issues/1149


Added support for older projects targets .net framework 4.5 and up.

Removed Condition to always have full debug pdb. #thatfrankdevApproved
Tested on project targeting .Net 4.5.1 👍

Pull-request #7 will be impacted by this.


Overwrite users in environment configuration

I need to change admin password in staging and prod.
Can I overwrite users in the environment configuration?
I have tried to put the users in user/localhost/accounts but it doesn't work.

You will need to override accounts:// stream in the stream configuration for that site.

Can you give me an example for that?

Here is documentation from the old way: https://learn.getgrav.org/16/advanced/multisite-setup
The new way is basically the same, but you can use streams.yaml where you have something like:
accounts:
  paths:
    - user/site/accounts

Do I have to use the Multisite Setup? Current I use only the Automatic Environment Configuration https://learn.getgrav.org/16/advanced/environment-config

You can just throw the streams.yaml file into your site config. But the ideas in the docs apply.

I put the ./user/localhost/config/streams.yaml with
schemes:
  accounts:
    paths:
      - user/localhost/accounts

and I put the user.yaml to user/localhost/accounts but it didn't work

Any news here. I believe I encountered the same problem here:
I am currently reworking my multisite. During that I wanted to move some files to sub directories as cleanup.
A brief structure
user/

accounts/
sites/

site1/

site2/

Both sites are mostly independent, but the users are the same. As the user stream is the site1/site2 directly, I wanted to overwrite the account stream. But as soon as I did that, Grav did not find any user and I got the redirected to create the first admin user.
My current workaround is to set "user" as additional path in the user stream.
I tried both ways. Setting it via config/streams.yaml and the "old way" as you called it in the setup.php. The Grav version is the current 1.7.RC20. But as I recall it also happened on 1.6.
Dumping the locator shows the seemingly correct path in the schemes.

Any news here. I believe I encountered the same problem here:
I am currently reworking my multisite. During that I wanted to move some files to sub directories as cleanup.
A brief structure
user/

accounts/
sites/

site1/

site2/

Both sites are mostly independent, but the users are the same. As the user stream is the site1/site2 directly, I wanted to overwrite the account stream. But as soon as I did that, Grav did not find any user and I got the redirected to create the first admin user.
My current workaround is to set "user" as additional path in the user stream.
I tried both ways. Setting it via config/streams.yaml and the "old way" as you called it in the setup.php. The Grav version is the current 1.7.RC20. But as I recall it also happened on 1.6.
Dumping the locator shows the seemingly correct path in the schemes.

To me this works:
schemes:
  account:
    type: 'Stream'
    force: true
    prefixes:
      '': 'user/accounts'

To me this works:
schemes:
  account:
    type: 'Stream'
    force: true
    prefixes:
      '': 'user/accounts'

Oh, thank you. Didn't think about this way. Works fine for me too!

Oh, thank you. Didn't think about this way. Works fine for me too!

I have to correct myself. I didn't test one function... Reading the user accounts works fine and logging is working too, but creating new users will create them in an accounts folder of the subpage even if the directory didn't exist before.

I have to correct myself. I didn't test one function... Reading the user accounts works fine and logging is working too, but creating new users will create them in an accounts folder of the subpage even if the directory didn't exist before.

I think I got it working now. The solution seems to be moving to the "new" method of setting the streams using the streams.yaml and the environment variables. Using the old method (returning an array in setup.php) seems not to be working correctly. As far as I debugged it, the method initializeLocator is called four times. On the first call the values are right, but as soon the second call is made the array from setup.php seems to be ignored for some values and they will be reset to default.
Hopefully this will help you.

I think I got it working now. The solution seems to be moving to the "new" method of setting the streams using the streams.yaml and the environment variables. Using the old method (returning an array in setup.php) seems not to be working correctly. As far as I debugged it, the method initializeLocator is called four times. On the first call the values are right, but as soon the second call is made the array from setup.php seems to be ignored for some values and they will be reset to default.
Hopefully this will help you.

It "works" also from setup.php, but there's a caveat: it only serves as an initial configuration and as the variables are overridden in system/config/streams.php, it won't work. I removed the system file so that the examples should work again. I also updated documentation to prefer schemes.yaml.

It "works" also from setup.php, but there's a caveat: it only serves as an initial configuration and as the variables are overridden in system/config/streams.php, it won't work. I removed the system file so that the examples should work again. I also updated documentation to prefer schemes.yaml.


As Frontend developer

Bug Report
Expected Result:
The website must be responsive on all screens
Actual Result:
The website is not responsive on all screens

Hi, thanks for taking the trouble to raise this issue. Work on mobile support for the site is under way.


gnutls out of date

Ping @stefanfransen
3.6.9 ->3.6.10

Created a PR at #37. Sorry for the late response, been busy.

All good.


✨ Allow multiple tags in docker.#Push and cli.#Load

What are you trying to do?
Sometimes you want to push an image to multiple tags (e.g., 0.1.0 and latest). BuildKit supports this by setting name to multiple values split by a comma:
push: core.#Push & {
	dest:  "localhost:5042/test1:\(randomString.output),localhost:5042/test1:latest,localhost:5042/test1:random"
	input: randomString.image.output
	config: env: FOO: randomString.output
}

Full plan
package main

import (
	"dagger.io/dagger"
	"dagger.io/dagger/core"
)

dagger.#Plan & {
	actions: {
		randomString: {
			baseImage: core.#Pull & {
				source: "alpine:3.15.0@sha256:e7d88de73db3d3fd9b2d63aa7f447a10fd0220b7cbf39803c803f2af9ba256b3"
			}

			image: core.#Exec & {
				input: baseImage.output
				args: [
					"sh", "-c", "echo -n $RANDOM > /output.txt",
				]
			}

			outputFile: core.#ReadFile & {
				input: image.output
				path:  "/output.txt"
			}

			output: outputFile.contents
		}

		// Push image with random content
		push: core.#Push & {
			dest:  "localhost:5042/test1:\(randomString.output),localhost:5042/test1:latest,localhost:5042/test1:random"
			input: randomString.image.output
			config: env: FOO: randomString.output
		}
	}
}

This doesn't work only because we're parsing dest and normalizing it, but we can change this. Either:

Split string by comma, normalize parts and join back with comma to give to BuildKit
Allow dest to accept a list of values:

docker.#Push & {
  dest: [
    "<registry>/<image>:tag1",
    "<registry>/<image>:tag2",
    "<registry>/<image>:latest",
  ]
}

Question here is how to handle result. Currently we have a single result: string. Same as dest, it can

Be different fields for string and [...string]
Same field with string | [...string]
Maybe always [...string]

Sometimes the result value is used directly somewhere and it needs to handled differently if it's a list. There's also the question of the action's output, since a list won't be shown in plain format (default). But we can support lists with something like this:
➜ dagger do push
[✔] ...
[✔] actions.push
Field     Value
result.0  "localhost:5042/example:latest@sha256:47a163eb7b572819d862b4a2c95a399829c8c79fab51f1d40c59708aa0e35331"
result.1  "localhost:5042/example:0.1.0@sha256:47a163eb7b572819d862b4a2c95a399829c8c79fab51f1d40c59708aa0e35331"

Why is this important to you?
This has been asked multiple times in Discord and it's not hard to do.
How are you currently working around this?
Just using multiple docker.#Push in a template or loop with different targets.
With cli.#Load there's a bigger performance impact though. I recommended a user in Discord to run docker tag after the cli.#Load to go around the perfomance hit:
actions: images: {
    img1: tags: {
        latest: _
        "0.1.0":  _
    }
    img2: tags: {
        latest: _
        "0.1.0":  _
    }
    img3: tags: {
        latest: _
        "0.1.0":  _
    }
    [img=string]: {
        build: docker.#Dockerfile & {
            source: client.filesystem["./images/\(img)"].read.contents
        }
        load: cli.#Load & {
            image: build.output
            host:  client.network."unix:///var/run/docker.sock".connect
            tag:   img
        }
        tags: {
            [imagetag=string]: {
                tag: cli.#Run & {
                    host: client.network."unix:///var/run/docker.sock".connect
                    env: DEP: "\(load.success)"
                    command: {
                        name: "tag"
                        args: [load.tag, "\(img):\(imagetag)"]
                    }
                }
            }
        }
    }
}

This doesn't work only because we're parsing dest and normalizing it, but we can change this. Either:

I think dest: string | [...string] is simpler than using ,.
It will not deprecate anything, just add a feature.

Question here is how to handle result. Currently we have a single result: string. Same as dest, it can

I agree with option 2, since outputs will be managed differently, that will be painful to work with multiple fields.
For instance, with string | [...string], current users that use docker.#Push and use the reference, should have no additional changes to do.
Just a question, is it possible to mange array display from dagger engine?

Closing since the 0.2 CUE API is frozen, in favor of the GraphQL API.


Can not display Chinese characters

Hi, this project is very useful for me. But it seems can't display chinese character.
I download a chinese font from google font here. Copy your example code, just replace the font to the downloaded font, and replace the 'hello world' to ramdom chinese character. The result is two square. It works if i change back to english.

Thanks for your great work!

I know why.
I didn't use the node-canvas package, instead  i used @napi-rs/canvas because it works out of box. In this case, I need to register font using @napi-rs/canvas'sGlobalFonts.registerFromPath instead of flow.registerFont. This solve my problem.

Glad you figured it out. I'll look into adding something to the README for @napi-rs/canvas.


Update README.md

Changes made for style and readability. Also changed the foo.com example to example.com, which is a fictitious domain provided for free use in technical documentation. Because of the origins of the expression, "foo" is usually scrubbed from documentation and exposed code comments.
Questions:
Contact Harness for value - Should this be "Contact Harness for the values"?
Suggested edits for some code comments:
Private Docker Image registry, will override all registries defined in subcharts --> This private Docker image registry will override any registries that are defined in subcharts. loadbalancerURL: https://myhostname.foo.bar --> loadbalancerURL: https//myhostname.example.com Do not have ingress enabled and istio enabled at the same time. --> Enable Istio or ingress; do not enable both. If istio.enabled is true, ingress.enabledmust not be.  Enabling ingress create kubernetes Ingress Objects for nginx. --> Setingress.enabledtotrue` to create Kubernetes Ingress objects for Nginx. Istio Ingress Settings --> Istio ingress settings
Enabled will deploy CI to your cluster --> Enable to deploy CI to your cluster. Enabled will deploy STO to your cluster --> Enable to deploy STO to your cluster.

Since the documentation is auto generated, these changes should be applied to README.md.gotmpl and override.yaml in /src/prod.
Thank you!

This PR has been automatically closed due to inactivity.


getAccessTokenFromAuthCode?

Hi,
trying to use your thing because it seems promising.
However, I'm stuck  early... Your documentation uses a method called "getAccessTokenFromAuthCode".
What is that?
Do I have to implement that on my own and if so, what should be done?

Hey,
Yes, the method getAccessTokenFromAuthCode is a made up method that is supposed to exchange the auth code returned by the IPC for an access token. That is how OAuth works.
To know how to do it, you must first understand how OAuth2.0 works. Easily available information online (hint: OAuth2.0 supports multiple "flows", the flow you're looking for is called the authorization code flow). Then you need to apply that knowledge to Discord APIs. The documentation explains the specifics for Discord.

Just wanted to say: DiscordIPC works like a charm!
Thanks a lot for sharing!

Thank you for the feedback! Glad to know it's working well. There may or may not be a useful Discord related desktop app coming soon that uses DiscordIPC under the hood ;).


Cleanup cpp api

Also fix a slight memory leak.

Thanks for the PR!
I think its about time we discussed how we want update semantics to work in general, and it would be nice to see whatever we decide to be well asserted with tests & benchmarks as well.  For now, this is a strict improvement on the haphazard delta implementation we use ...


Should we remove the pagination Tab from APIs in Query Modules?

https://www.notion.so/Should-we-remove-the-pagination-Tab-from-APIs-260425c3fa44471296e0879b47a42d68

@pedro-santos-rodrigues Need inputs

There are differences in the UI between APIs and GraphQL

Bumping this issue up to prod because it should have made it's way there by now if it was not fixed


counts unique terms if not available in Lucene

See issue #2052:  Unique terms not available in IndexReaderUtils
I did not add a new unit test for this.

Hi @djoerd - sorry for the late response...
To get an accurate count of the vocab size, you have to use the -optimize flag, which merges all the index segments down into a single one.
I don't think your patch of just adding the unique counts from each segment works, because the vocab space will overlap.


Confusing removeInterceptor

Hi, I was reading in source code that .get returns an interceptor, so I was looking to do basically:
var interceptor_1 = nock(service1URI)
	.persist()
	.get('/api/route1');
var scope1 = interceptor_1.reply(function() {
	console.log('GOT NOCKED');
	return [200, JSON.parse(mockData)];
});
var interceptor_2 = nock(service2URI).....

...snip...

nock.removeInterceptor(interceptor_1); // not _2!

But that doesn't seem to be working. Am I misunderstanding something? If not, could it be supported?

The API for removeInterceptor is not that one. It's:
https://github.com/pgte/nock/blob/master/README.md#removeinterceptor

Anyway, I see now what you're doing on this PR https://github.com/pgte/nock/pull/448.
You're trying to use the interceptor as the options for removing.
I'll keep this open for tracking.


pointer to bias so that array will be updated and saved

It seems Layer::_bias is disconnected from Node::_bias so Layer::_bias is not being updated or saved to file. This PR corrects that

Dear Mr.hieuhoang,
I want ask you if the code is run correctly with you to ask question, please. And where I can find your code with pointer bias please.

@hieuhoang


Under Android SVG size uses pixels instead of device independent pixels

It used to be that width and height were in DIP (like the rest of XF) but now the SVG specified width/height is used as the bitmap pixel size.  This causes the resultant image to be grainy.
To confirm with XF this should be changed back to DIP.

Hey @philipag Great job spotting this.
I pushed in a fix it is in version 17.
https://www.nuget.org/packages/Xam.Plugins.Forms.Svg/<IP_ADDRESS>
The images should be back to crispy clean :)
Cheers
Paul

Thanks!
On March 6, 2015 9:31:40 PM Paul P<EMAIL_ADDRESS>wrote:

Hey @philipag Great job spotting this.
I pushed in a fix it is in version 17.
https://www.nuget.org/packages/Xam.Plugins.Forms.Svg/<IP_ADDRESS>
The images should be back to crispy clean :)
Cheers
Paul

Reply to this email directly or view it on GitHub:
https://github.com/paulpatarinski/Xamarin.Forms.Plugins/issues/16#issuecomment-77668681


Minimum Value to Trigger barMinHeight

Hello there, thank you for the nice library!
I guess it would be better to add new option parameter to trigger "barMinHeight" instead of "0" value.

For an example, here in bundled version, I changed line 1344 like this. (changed "0 ==" to "5 <="). So we users can have a more stable graphic when there are a little parasites in the sound that makes bar height between 0 and 5.
Can be named as: "barMinHeightTrigger" as an integer.

@flyingatm does pr #2523 fix this for you?

no feedback, closing.


refactor: optimize judgment conditions

Please describe the changes this PR makes and why it should be merged:
optimize judgment conditions
Status

[ ] Code changes have been tested against prettier, or there are no code changes
[x] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[ ] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[x] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 63.75%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
1287

Relevant Lines:
2089

💛  - Coveralls

LGTM, thank you


Add X-Stormpath-Agent header

Closes #106

I've verified that this works as expected with and without CORS in Chrome, Safari, and Firefox. :+1:
However, both the Node SDK and Express SDK also includes the framework version in their user agent strings. So I've appended the AngularJS version to the X-Stormpath-Agent header as well (543b27032d7961e17c420a9e8034f2f54360ec77).
Please have a look if this is correct. If so, we might want to clarify that in the framework spec. If not, I will just revert my commit.

Thanks @timothyej !  Yes, we do need the framework version as well.  This looks good so I'm going to merge.


Hello World in java

:warning: This is a Pull Request Template :warning:

Checkout all the things you've done by placing an *x*\ within the square braces.

Proposed Changes

[x] I've forked the repository.
[ ] I've created a branch and made my chagnes in it.
[x] I've read the CODE OF CONDUCT and abide to it.
[x] I've read the CONTRIBUTING.md
[x] I understand opening a PULL REQUEST doesn't mean it will be merged for sure.

@VJFernandez123 - Please resubmit with your own code sample. Thank you!


new regex with barrel cortex barrel names exception

as discussed:  https://github.com/BlueBrain/atlas-commons/pull/5
For layers 6a and 6b the regex still keeps the 6[ab] part, the rest is removed.
Uncertain why the original layer 3 regex had additional symbols: [^/]3, am I missing something?

OK. Can I rerun the Atlas pipeline with this new version of isocortex_metadata.json?

For me, yes!

Was the pipeline rerun w/ this @lecriste?
If so, we can work on getting CI to pass, and get it merged.

Not yet.

Vishal and I , had looked at this issue, and what we found was that the issue with the earlier regexes could be potentially be resolved by setting "with_descendants": false within layers element in the isocortex_metadata.json .  What is the rationale for "with_descendants": true in the current code?

Vishal and I , had looked at this issue, and what we found was that the issue with the earlier regexes could be potentially be resolved by setting "with_descendants": false within layers element in the isocortex_metadata.json . What is the rationale for "with_descendants": true in the current code?

I don't know but are you sure that's enough to fix the issue @alTeska mentioned here?

I tracked the file in the Atlas pipeline repo:
https://bbpgitlab.epfl.ch/dke/apps/blue_brain_atlas_pipeline/-/blob/develop/metadata/isocortex_metadata.json
Once you agree on the new version, please open an MR there and the pipeline will automatically consume the new file. @rai-pranav

Right now, I guess you can update the current pipeline with what @alTeska regex solution. I will test separately , if my solution produces the same result or not.

The placement hints produced with this version of isocortex_metadata.json and the new CCFv2022 BBPa annotation are here:
/gpfs/bbp.cscs.ch/data/project/proj84/atlas_pipeline_runs/2024-05-26T20:43:55+02:00/placement_hints/
Let me know if they look good. @alTeska @rai-pranav

I had a look at the new [PH]y.nrrd, there is no artefact in this placement hints, approved.

Was the pipeline rerun w/ this @lecriste? If so, we can work on getting CI to pass, and get it merged.

@mgeplf, it seems we can proceed.

Ok, I also did a release: https://github.com/BlueBrain/atlas-placement-hints/releases/tag/v0.1.3


Expose tiny-skia features

tiny-skia has a couple of features which aren't required for resvg as a library but are nonetheless always enabled: simd, png-format. It is better to leave it up to the user to decide what features they want.

No. This is not necessary. All those features must be enabled.

It compiles fine without the png feature so it doesn't look like it needs to be enabled. The reason I made this PR is that I was going through my dependency tree and was surprised to see the png crate there when I'm not doing anything with pngs.

The png crate is a tiny dependency. It might not even be present in the final binary if you do not use it.
But each build feature is a maintenance burden. And I cannot afford it. It's already too complicated.


Drawing support

Currently, our build of graph-tool doesn't support drawing, since one of the dependencies (gtk+3) is not yet available via conda-forge.  Once that changes, we should update this recipe.
In the meantime, it may be possible for users to enable drawing support by installing the required dependencies themselves, as described here.
~Something like this might work:~
conda install -c conda-forge -c pkgw/label/superseded graph-tool pygobject cairo gtk3

Update: The above does not work:

The channel mentioned above is obsolete, and has been superseded by a newer one: pkgw-forge.
Even using that newer channel, there is no version available of gtk3 (and pyobject)  that supports python 3.7.  But python 3.6 is supported.
However, even using python 3.6, one immediately encounters a problem:In [1]: import graph_tool.draw

** (process:84798): WARNING **: 10:08:04.847: Failed to load shared library '/miniforge/envs/py36/lib/libpango-1.0.0.dylib' referenced by the typelib: dlopen(/miniforge/envs/py36/lib/libpango-1.0.0.dylib, 9): Library not loaded: @rpath/libgobject-2.0.0.dylib
  Referenced from: /miniforge/envs/py36/lib/libpango-1.0.0.dylib
  Reason: Incompatible library version: libpango-1.0.0.dylib requires version 5601.0.0 or later, but libgobject-2.0.0.dylib provides version 5501.0.0

... bla bla ...

/miniforge/envs/py36/lib/python3.6/site-packages/gi/overrides/__init__.py in override(type_)
    200
    201         g_type = info.get_g_type()
--> 202         assert g_type != TYPE_NONE
    203         if g_type != TYPE_INVALID:
    204             g_type.pytype = type_

AssertionError:

Evidently (on Mac at least), the gtk3 package is not compatible with the version of pango available on conda-forge.
So the best option is to contribute a gtk3 recipe to conda-forge.  Assuming the pkgw-forge is a suitable starting point, that will involve contributing 4 new recipes in total:
$ conda create -n test-gtk3 -c pkgw-forge -c conda-forge gtk3 pygobject

...

$ conda list -n test-gtk3 | grep -v conda-forge
# packages in environment at /miniforge/envs/test-gtk3:
#
# Name                    Version                   Build  Channel
at-spi2-atk               2.26.2               h2fbb542_0    pkgw-forge
at-spi2-core              2.28.0               h2fbb542_0    pkgw-forge
epoxy                     1.5.2                         0    pkgw-forge
gtk3                      3.22.30              h7a40bec_0    pkgw-forge

xref conda-forge/staged-recipes#9314

Hi, I have just installed the latest release of graph-tool using conda-forge. I would like to use the graph_draw method to visualise network graphs but it fails to import the cairo_draw module. This is my environment:
Ubuntu 18.04 (bionic)
Anaconda3-2019.07-Linux-x86_64
Python 3.7.4
I have created my conda virtual environment and installed graph_tool with
conda install -c conda-forge graph-tool
graph-tool  2.29

The package has been successfully installed under
~/anaconda3/envs/TRIADB/lib/python3.7/site-packages
Then I tried
from graph_tool.all import *
g = Graph()
v1 = g.add_vertex()
v2 = g.add_vertex()
e = g.add_edge(v1, v2)
Backend Qt5Agg is interactive backend. Turning interactive mode on.
/home/athan/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool/all.py:40: RuntimeWarning: Error importing draw module, proceeding nevertheless: /home/athan/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool/draw/libgraph_tool_draw.so: undefined symbol: _ZN5Cairo7Context9show_textERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
  warnings.warn(msg, RuntimeWarning)

I have also tried to set LD_LIBRARY_PATH to solve the following ImportError but this did not work
echo $LD_LIBRARY_PATH
/home/athan/anaconda3/envs/TRIADB/lib:/home/athan/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool:

It appears that the error in more depth is the following
 from graph_tool.draw import cairo_draw
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-e914249e8560> in <module>
----> 1 from graph_tool.draw import cairo_draw

~/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool/draw/cairo_draw.py in <module>
     87
     88 from .. dl_import import dl_import
---> 89 dl_import("from . import libgraph_tool_draw")
     90 try:
     91     from .libgraph_tool_draw import vertex_attrs, edge_attrs, vertex_shape,\

~/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool/dl_import.py in dl_import(import_expr)
     59
     60     try:
---> 61         exec(import_expr, local_dict, global_dict)
     62     finally:
     63         sys.setdlopenflags(orig_dlopen_flags)  # reset it to normal case to

~/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool/draw/cairo_draw.py in <module>

ImportError: /home/athan/anaconda3/envs/TRIADB/lib/python3.7/site-packages/graph_tool/draw/libgraph_tool_draw.so: undefined symbol: _ZN5Cairo7Context9show_textERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE

Is there anything else to try in my environment to enable drawing ?

I have also tried installation via apt package manager in Ubuntu bionic following graph-tool instructions here
sudo apt install python3-graph-tool

The following additional packages will be installed:
  libboost-context1.65.1 libboost-graph1.65.1 libboost-python1.65.1 libboost-regex1.65.1 libcgal13 python3-decorator python3-numpy
  python3-scipy
Suggested packages:
  graphviz gfortran python-numpy-doc python3-dev python3-nose python3-numpy-dbg python-scipy-doc
Recommended packages:
  python3-matplotlib

And if you execute
Python 3.6.8 (default, Oct  7 2019, 12:59:55)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from graph_tool.all import *
/usr/lib/python3/dist-packages/graph_tool/draw/cairo_draw.py:39: RuntimeWarning: Error importing cairo. Graph drawing will not work.
  warnings.warn(msg, RuntimeWarning)
/usr/lib/python3/dist-packages/graph_tool/draw/cairo_draw.py:39: RuntimeWarning: Error importing cairo. Graph drawing will not work.
  warnings.warn(msg, RuntimeWarning)
/usr/lib/python3/dist-packages/graph_tool/all.py:40: RuntimeWarning: Error importing draw module, proceeding nevertheless: No module named 'matplotlib'
  warnings.warn(msg, RuntimeWarning)

I installed  sudo apt install python3-matplotlib and tried again
 python3 -c 'from graph_tool.all import *'

/usr/lib/python3/dist-packages/graph_tool/draw/cairo_draw.py:39: RuntimeWarning: Error importing cairo. Graph drawing will not work.
  warnings.warn(msg, RuntimeWarning)
/usr/lib/python3/dist-packages/graph_tool/draw/cairo_draw.py:39: RuntimeWarning: Error importing cairo. Graph drawing will not work.
  warnings.warn(msg, RuntimeWarning)
/usr/lib/python3/dist-packages/graph_tool/draw/cairo_draw.py:39: RuntimeWarning: Error importing cairo. Graph drawing will not work.
  warnings.warn(msg, RuntimeWarning)
/usr/lib/python3/dist-packages/graph_tool/all.py:40: RuntimeWarning: Error importing draw module, proceeding nevertheless: /usr/lib/python3/dist-packages/cairo/_cairo.cpython-36m-x86_64-linux-gnu.so: undefined symbol: cairo_tee_surface_index
  warnings.warn(msg, RuntimeWarning)

And that is where I decided to stop the effort .... :-(

Update: Someone is working on adding gtk+3 to conda-forge, and it looks like they're close:
https://github.com/conda-forge/staged-recipes/pull/10979
Once that's merged, maybe we can support drawing in our build of graph-tool.

Whoops, I left out the matplotlib dependency.  Working on a PR now.  Meanwhile, users who need drawing support will have to install matplotlib explicitly:
conda install -c conda-forge graph-tool matplotlib

I have just installed graph-tool 2.33 and verified that graph_draw method works fine now.

Have you guys solve this problems successfully? I met the same problems like this  undefined symbol: _ZN5Cairo7Context9show_textERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE.
I used miniconda2 to install graph-tools.

@werhoog Yes, drawing should work now.  Please try the following commands.  If something goes wrong, open a new issue.
conda create -n gt -c conda-forge graph-tool=2.35
conda activate gt
python -c "import graph_tool as gt"


wee_alloc tutorial page not matching current template

🐛 Bug description
https://github.com/rustwasm/wasm-pack/blob/master/docs/src/tutorials/npm-browser-packages/template-deep-dive/wee_alloc.md
the cfg_if! segment is no longer correct based on the present template (https://github.com/rustwasm/wasm-pack-template/blob/master/src/lib.rs)
🤔 Expected Behavior
This could be omitted or updated to reflect the non-conditional nature of use

related PR on the tutorials: https://github.com/rustwasm/wasm-pack/pull/894


ui: rearranged structure

added loader
added ErrorBoundary
closes #107

LGTM. One question. Should we make every component of the application overridable or only a certain set of them?

@Pineirin I think it depends on the use case, where we want to allow for overridability as developers. In this case I am still expanding the set of the overridables and in the next PRs you will see more of them


Update build image and update changelog

PR Checklist

[x] CHANGELOG.md updated

LGTM, just waiting for "Check Docker images" to pass which will take ~30m for the Windows build


[Discord] WalletConnect Safe App is not loading

https://discordapp.com/channels/477106835862716416/477391201708802058/812439570003132426
Is the wallet connect safe app broken right now?  All I get is a blank white frame when trying to load it
The first time I tried to load it up I got a loading symbol.  Left it for 15 minutes and nothin'.  Did a hard refresh of the page and reconnected to my Safe.  Now I don't even get the loading symbol.
Just to see, I was able to load up some of the other safe apps like the Aave and Compound ones

(Just transferred it to safe-react-apps)
I'm not able to reproduce this issue.
We serve the WalletConnect app from https://cloudflare-ipfs.com/ipfs/QmT3VxxfFtfEcvq8AeaoFAyUGxePRa2zisvnxLTrQXU5Uf - Does this load for the user?
As Richard mentioned, we need more context. Things like

Web or desktop?
Which browser?
Which owner wallet?
Which env.

Basically things that are in the bug issue template ;)

@tschubotz afaik we serve it from ipfs.io not cloudlfare. Was it changed?

@mikheevm this was a bit of a hidden change in the 3.0.1 release due to the many rate limit errors with ipfs.io :)
https://gnosisinc.slack.com/archives/C63LQTGNB/p1613573599230800

The user figured it out, the problem was on their side:
[8:26 AM] bitznbrewz: FIGURED IT OUT
[8:29 AM] bitznbrewz: K, soooo, I had connected with my Trezor wallet through metamask.  I just connected using Trezor Bridge in Firefox and now it seems ok.  :thumbsup:.  I was actually unable to get the bridge to work in Brave browser.

But, going forward, I guess I will make sure to use the native Trezor integration with Gnosis


Merge branch 'release/1.4.16' into main

Merge branch 'release/1.4.16' into main #6

Closing as this is probably a mistake.


Idea: Work in Kubernetes

Is it possible to make go-storage work in k8s?
Ideas

Provide CSI via go-storage?

References

Paper: A Unified Storage Layer for Supporting DistributedWorkflows in Kubernetes

It doesn't make sense.


So/apply filter request

In a separate PR we will rename models as ViewModels as appropriate, all inside Models folder (probably)

The unit tests on the controller don't test that the mappers are called with the correct params, this will be fixed when we refactor to use a factory method for creating the view model

Some comments are missing - we cheated by putting in empty ones :)


isomorphic-fetch headers not added in IE11

I'm submitting a bug report

Library Version:
1.0.0

Operating System:
Windows 8.1

Node Version:
6.3.1

NPM Version:
3.10.5

JSPM OR Webpack AND Version
webpack 2.1.0-beta.21

Browser:
IE 11

Language:
TypeScript 2.0

Current behavior:
When trying to use the same piece of code that properly runs on Chrome and FF (no need for polyfills) IE 11 does not seem to add the specified headers.
polyfill added (taken from ts-webpack-skeleton)
const fetch = !self.fetch ? System.import('isomorphic-fetch') : Promise.resolve(self.fetch);
example:
async myMethod(): Promise<any> {
    await fetch;
    const response = await this.httpClient.fetch('myUrl', {
            headers: {
                'My-Custom-Header': ''
            }
        });
}

What is the expected behavior?
Add the provided headers

I know this is probably related to the fetch polyfill provided within isomorphic-fetch.
Does anyone got this? Workarounds? Other suggested polyfill libraries?
Cheers,
Enrico

Maybe It was a misconfiguration in CORS Asp.Net WebApi 2, I've ended up removing Microsoft.AspNet.WebApi.Cors dependency and handling it manually in the web.config under <system.webServer> node
    <httpProtocol>
      <customHeaders>
        <!-- CORS settings for NTLM -->
        <add name="Access-Control-Allow-Origin" value="http://localhost:9000" /> <!-- "*" is disallowed when Access-Control-Allow-Credentials is true -->
        <add name="Access-Control-Allow-Headers" value="X-Requested-With, origin, content-type, accept, X-Division-Name, Accept-Language" />
        <add name="Access-Control-Allow-Methods" value="GET, PUT, POST, DELETE, HEAD, OPTIONS" />
        <add name="Access-Control-Allow-Credentials" value="true" /> <!-- Allows send user auth (NTLM) -->
      </customHeaders>
    </httpProtocol>

and then adding credentials: 'include' option when calling fetch method.
I found CORS behavior very inconsisten across Chome / FF / IE .. for ex Chrome sends a preflight request with OPTIONS verb which caused me a big headhake yesterday!


Go client requires _type to be set, while ES itself does not require it

Which version of Elastic are you using?
[x] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
Go client does not return error if I do not set _type. (Type() methods.)
Please describe the actual behavior
Go client returns error if I do not set _type.
Any steps to reproduce the behavior?
Just use Index service without setting _type with Type() method. Go client returns error:
https://github.com/olivere/elastic/blob/f82cf7c66881f3f18d0354a68086e9aa2f9a48d1/index.go#L236-L238
Comment out those strings and then it works and ES response is OK.

Hmm. In the latest REST API spec for 6.x the type is still marked as required.

In the 7.x branch it is no longer required. This is in line with the plan for removing mapping types.


Display the gist url

The gist URL is displayed in the browser console. I am currently looking a better way to display it to the user.

A button copy it to clipboard.