[Icon Request] Support for cookbooks

[x] I'm sure this issue is not a duplicate.
[x] I'm submitting an icon request:

Type: languageId
Icon Name: cookbook
Sample original Icon:

Extensions: .ckbk

Language ids: cookbook

Which vscode extension uses cookbook as languageid?

It's our custom extension within our company. Do I need to upload it to the market place? It's called fsmscookbooks


Problems with PVTS recognizing classes in sub directories in projects in Python 3.4+ without init.py

Hi. I'm not sure where the forum is.  This may be best answered in a forum, and not as a bug.  If you redirect me, I'll put it there.
I just have a bunch of python scripts that work just fine in my Pycharm project, and when run in python. I'd like to use Visual Studio python tools, as it looks to have better intellisense.   It appears that PVTS is not finding my classes located in sub directories.
I added the directories to the search path, but it did not help.  What did seem to help was mangling the import command to just note the class name, but then I figured python probably wouldn't run my project, so I'd like to see what I need to do for PVTS to work correctly.
I have the following structure. It's actually a collection py.test tests, with start script that initializes py.test:
project-dir
apitestrunner.py (test setup script)
|
|---ApiTestSuites
| |
| --test_api_app.py (Pytest module)
|
|---helpers
|
|
---Config.py   (def class Config)
---ServicesClass.py  (def class ServicesClass)
apitestrunner.py is the "startup script". It gets some config settings, and fires up pytest to run tests
Because I have problems in both apitestrunner, and my test class, I do not think this has anything to do with pytest.
pytools is telling me that it cannot resolve references to class Config.py, or ServicesClass.py from apitestrunner.py and test_api_app.py. Normally main-script does not import the test scripts (test_api_app.py), but I just tried it, and importing that seemed to work just fine.
Is there some reason why the ide would have trouble recognizing the helper classes? The classes have the same name as the file names, and as I said this all works fine in other IDEs.
Here are my import statements:
apitestrunner.py:
from helpers.Config import Config
from helpers.ServicesClass import ServicesClass
test_api_app.py:
from helpers.Config import Config
from helpers.ServicesClass import ServicesClass
Thanks!
Sam

Did you purposefully leave out your init.py files in your example or do you not have them? Does that make a difference?
And here is an attempt to rebuild the diagram of files and folders so it's readable.
project-dir
apitestrunner.py (test setup script)
|
|---ApiTestSuites
| |
| --test_api_app.py (Pytest module)
|
|---helpers
       |
       |
       ---Config.py   (def class Config)
       ---ServicesClass.py  (def class ServicesClass)

Hi.  I don't have an init.py script. I don't deploy this anywhere.
Would PTVS look at init.py
On Thu, Dec 17, 2015 at 11:27 AM, Brett Cannon<EMAIL_ADDRESS>wrote:

Did you purposefully leave out your init.py files in your example or do
you not have them? Does that make a difference?
And here is an attempt to rebuild the diagram of files and folders so it's
readable.
project-dir
apitestrunner.py (test setup script)
|
|---ApiTestSuites
| |
| --test_api_app.py (Pytest module)
|
|---helpers
|
|
---Config.py   (def class Config)
---ServicesClass.py  (def class ServicesClass)
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/PTVS/issues/1031#issuecomment-165555850.

To Add to what Brett said, if you don't have init.py files it will not run in Python 2.7. It would work in Python 3.5 so I am assuming that is what you are using?

Hi.  Sorry I guess that would be important to know.  I'm running Python
3.4.3
Thanks!
Sam
On Thu, Dec 17, 2015 at 11:45 AM, Christopher Wilcox <
<EMAIL_ADDRESS>wrote:

To Add to what Brett said, if you don't have init.py files it will
not run in Python 2.7. It would work in Python 3.5 so I am assuming that is
what you are using?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/PTVS/issues/1031#issuecomment-165561297.

Perfect. I am going to update the title to specify 3.4+ Python since it is sort of relevant.  I can add some screen caps from my side. There is an actual issue here and we will have to make improvements to analysis.
Thanks for your feedback!
Chris

From @zooba, who is currently in a place nicer than Seattle on holiday:
We currently infer full package names backwards from the directory structure (rather than forwards from a search path), so namespace packages don't get their full name and we can't resolve them.
I'm fixing this in analyzer 2.0. For now, you can add init.py files and make your interpreter happy.

https://github.com/Microsoft/PTVS/issues/572 is tracking the fix for namespace packages.

Hi.  Thank you.
are you actually talking about init.py files?  That's all I found when
I googled the subject.  (I haven't had a need to create a module before)
Thanks!
Sam
On Thu, Dec 17, 2015 at 11:58 AM, Christopher Wilcox <
<EMAIL_ADDRESS>wrote:

From @zooba https://github.com/zooba, who is currently in a place nicer
than Seattle on holiday:
We currently infer full package names backwards from the directory
structure (rather than forwards from a search path), so namespace packages
don't get their full name and we can't resolve them.
I'm fixing this in analyzer 2.0. For now, you can add init.py files and
make your interpreter happy.
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/PTVS/issues/1031#issuecomment-165565874.

Yep, Chris is talking about __init__.py files. Unfortunately they come out as "init.py" when you use Markdown.

Dup of #572


feat(treeshaking): A start on making the component tree shakable

This attempts to create a base for tree shaking, this change is related to changes to the core. Currently however this implementation isn't working as intended yet.
Suggested change:
We create 2 different components

Flag (The default usage, which allows for the current use)
PerfFlag (Name should probably be different) (Doesn't accept Code and instead only accepts a Flag object from the core)

Backstory
The react component currently uses the imageUrl method, this has the issue that this prevents tree shaking as the core has no way to know which elements are used and which are unused.
My suggestion
Would be to allow users to import a flag from the core and pass that to the component, this way the user can opt-out of loading all flags.
The most desired here would be that a user can do: import { PerfFlag } from 'react-flagpack', this works now however it doesn't tree shake (because we have side effects caused by scss). So the user needs to now do 'react-flagpack/dist/PerfFlag.esm'
Problems that still happen:
This partially works, the react component is smaller and doesn't have all the flags. However the core seems to import all the SVG's and flags even if we only export a small amount of them.
Possible fixes for that would be:

Change core even more so that each flag generates a JS file, so the user can import NL from 'flagpack-core/NL' (this however wouldn't be most optimal as that becomes a lot when using a lot of flags)
Find a method that allows us to have the exports but still tree shake (I know that this is possible but I can't remember the way)

Test environment
I used the following environment to test the changes in (Note that this PR depends on the PR in the core)
PerfFLag:
import Head from 'next/head'
import { PerfFlag } from 'react-flagpack/dist/PerfFlag.esm'
import { AD, AI, AL, CC } from 'flagpack-core/dist/allFlags.esm'

import styles from '../styles/Home.module.css'

export default function Home() {
  return (

        <title>Create Next App</title>
        <link rel="icon" href="/favicon.ico" />

      <PerfFlag flag={AD}/>
      <PerfFlag flag={AI} />
      <PerfFlag flag={AL} />
      <PerfFlag flag={CC} />

  )
}

Flag:
import Head from 'next/head'
import styles from '../styles/Home.module.css'

import Flag from 'react-flagpack'

export default function Home() {
  return (

        <title>Create Next App</title>
        <link rel="icon" href="/favicon.ico" />

      <Flag code="NL" size="l" />

  )
}

Next config:
const withImages = require('next-images');
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')

module.exports = withImages({
  webpack: (config, { dev, isServer }) => {
    config.plugins.push(new BundleAnalyzerPlugin({
      analyzerMode: 'static',
      openAnalyzer: false,
      reportFilename: `../../analyzer/report-${Math.random()}.html`
    }))

    return config
  }
});

Would love to see where this effort leads.
The library is great, but the inability to import individual flags w/o bringing the whole 18kb package is a showstopper for us.
Would having the individual flags exported as their own named modules be a possibility?
import { FlagNL } from 'react-flagpack';
// or
import FlagNL from 'react-flagpack/nl';

Hi @adamduncan 👋 We've been prioritising some other things within flagpack, but I agree that some form of this tree shaking should implementated. Anyway, I really like both of these implementations and I think this is definitely something we could work towards.

We have internally discussed tree shaking and have come up with an implementation.
Feedback is welcome, and will be considered.
https://github.com/Yummygum/flagpack-core/discussions/46
We will close this PR as the implementation here is very different from the approach we aim to implement now.


[Bugfix] Fix negative scale for function round/truncate

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #10267
Problem Summary(Required) ：

Checklist:

[x] I have added test cases for my bug fix or my new feature
[x] I have added user document for my new feature or new function

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

Admit test failed, because the failed cases should also be updated.

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

@Mergifyio backport branch-2.2

@Mergifyio backport branch-2.3

@Mergifyio backport branch-2.4


Update duty cycle code

Added suggestions from https://github.com/openaps/oref0/issues/1058 and removed emergency actions since a different script is rebooting when radio problems occur.

@scottleibrand can you please review the changes? It'll make the core much simpler and removes redundant functionality :)

@scottleibrand other issues ?


Modify examples to use new source-generated Iter/Each callbacks.

The examples were all written before the generic callback source generators were introduced. It would be a good idea to sweep through the examples and use the shorter Each callbacks wherever possible.
Before:
Routine routine = world.Routine(
    filter: world.FilterBuilder()
        .With<Position>()
        .With<Velocity>(),
    callback: (Iter it, int i) =>
    {
        Column<Position> p = it.Field<Position>(1);
        Column<Velocity> v = it.Field<Velocity>(2);

        p[i].X += v[i].X;
        p[i].Y += v[i].Y;
    }
);

After:
Routine routine = world.Routine(
    filter: world.FilterBuilder<Position, Velocity>(),
    callback: (ref Position p, ref Velocity v) =>
    {
        p.X += v.X;
        p.Y += v.Y;
    }
);

Completed here https://github.com/BeanCheeseBurrito/Flecs.NET/pull/19


xkalamine doesn't work with Fedora Silverblue and immutable OSes in general

xkalamine install layout.toml reasonably assumes that /usr/share/X11/xkb exists and can be written to.
These assumptions fail when it comes to Fedora Silverblue (and by extension, all the other members of the wild Universal Blue family), as /usr is read-only since the root partition is immutable. That is, after all, one of the main selling points of these OSes.
The normal approach to making any necessary changes to your immutable OS install is to either install Flatpaks to userland or to overlay rpm to the base OS image, using rpm-ostree install.
This essentially means building your own rpm to install your custom keyboard layout. At least, that's the only answer I've found so far. I have not wanted to do that so far, so I've not been able to install custom keyboard layouts (and learn them).
I'm not sure what I expect here, but I suppose my goal in opening this issue is twofold:

document the fact that xkalamine doesn't know it can run on immutable OSes and that it falls apart when trying to use it to install
share what I've found so far, and see if others have better options or ideas

thanks!

by default, when /usr/share/X11/xkb is not writable (e.g. used without sudo, immutable distro. etc.)  kalamine fallbacks to userspace (i.e. installing in ~/.local/share/)… So I do not understand how it is not working, unless Fedora Silverblus do not support Wayland ? Userspace install only work under wayland.

Hmm, i just tried it again, after updating to kalamine 0.38 (via pipx in a toolbox):
xkalamine apply ergol.toml
You appear to be running Wayland, which does not support this operation.

xkalamine install ergol.toml
Traceback (most recent call last):
  File "/var/home/axel/.local/bin/xkalamine", line 8, in <module>
    sys.exit(cli())
             ^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/kalamine/cli_xkb.py", line 84, in install
    xkb_index = xkb_install(xkb_root)
                ^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/kalamine/cli_xkb.py", line 76, in xkb_install
    xkb.update()
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/kalamine/xkb_manager.py", line 83, in update
    update_symbols(self._rootdir, self._index)  # XKB/symbols/{locales}
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/home/axel/.local/share/pipx/venvs/kalamine/lib64/python3.12/site-packages/kalamine/xkb_manager.py", line 303, in update_symbols
    with path.open("w") as file:
         ^^^^^^^^^^^^^^
  File "/usr/lib64/python3.12/pathlib.py", line 1013, in open
    return io.open(self, mode, buffering, encoding, errors, newline)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/usr/share/X11/xkb/symbols/fr

It's true, /usr/share/X11/xkb does not exist in Fedora Silverblue.
But if i manually create:
/usr/share/X11/xkb
/usr/share/X11/xkb/fr
/usr/share/X11/xkb/symbols/
then xkalamine acts as you described:
/usr/share/X11/xkb
    Not writable: switching to user-space.

... /var/home/axx/.config/xkb/rules/evdev.xml
... /var/home/axx/.config/xkb/symbols/fr
      + fr/ergol

Successfully installed.
Warning: user-space layouts only work with Wayland.

Hope this helps!

In addition to this, might be nice to document ~/.config/xkb install in https://github.com/OneDeadKey/kalamine?tab=readme-ov-file#linux-root-xkb_symbols as system-wide install is not an option for immutable OSes users.


Fix DUSD related fixture

What kind of PR is this?:

/kind fix
What this PR does / why we need it:

DUSD fixture correction
old: set DUSD token as normal token and minted
new: set DUSD token as loan token and should own DUSD from takeLoan

test paybackLoan with DUSD

test zero interest

What about the other loan tokens that we mint in regtest🤔. IMO don't see a problem as long as if it does not interfere with the test scope.

Yeah definitely something we need to refactor.


Support yielding streams?

Thoughts on adding support for streams to be yieldable? Happy to make a PR if needed.

nope, streams are a node/iojs concept, not a javascript concept. there will also be whatwg streams, which are promise based and thus yieldable.
you can search for stream in https://github.com/tj/co/wiki for many modules that may suite your needs.


Node.js  Loaders Team Meeting 2024-04-23

Time
UTC Tue 23-Apr-2024 18:00 (06:00 PM):

Timezone
Date/Time

US / Pacific
Tue 23-Apr-2024 11:00 (11:00 AM)

US / Mountain
Tue 23-Apr-2024 12:00 (12:00 PM)

US / Central
Tue 23-Apr-2024 13:00 (01:00 PM)

US / Eastern
Tue 23-Apr-2024 14:00 (02:00 PM)

EU / Western
Tue 23-Apr-2024 19:00 (07:00 PM)

EU / Central
Tue 23-Apr-2024 20:00 (08:00 PM)

EU / Eastern
Tue 23-Apr-2024 21:00 (09:00 PM)

Moscow
Tue 23-Apr-2024 21:00 (09:00 PM)

Chennai
Tue 23-Apr-2024 23:30 (11:30 PM)

Hangzhou
Wed 24-Apr-2024 02:00 (02:00 AM)

Tokyo
Wed 24-Apr-2024 03:00 (03:00 AM)

Sydney
Wed 24-Apr-2024 04:00 (04:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+Loaders Team+Meeting+2024-04-23&iso=20240423T1800
or https://www.wolframalpha.com/input/?i=06PM+UTC%2C+Apr+23%2C+2024+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1GHNmq23UdBLE-zitYWdpIXq615-AKuGl8_ntJUqyg-0/edit

Agenda
Extracted from loaders-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

Proposal for a simple, universal module loader hooks API to replace require() monkey-patching #52219
ESM Hook deadlocks since 21.2.0 a3e09b3 #50948
esm: spawn only one hooks thread #50752

Invited

Loaders team: @nodejs/loaders

Observers/Guests
Notes
The agenda comes from issues labelled with loaders-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/97506450082

For those who just want to watch: https://www.youtube.com/c/nodejs+foundation/live

I can't attend this one.

I couldn't build node all week (until like 10pm last night), so I made almost no progress on my items :(


Storage type issue in createRoomContext in liveblocks.config.ts

Describe the bug
To Reproduce
Steps to reproduce the behavior:

Initialize storage
Stop internet connection
Mutate the storage using another user
Restore internet connection
The storage is not in sync

Expected behavior
A clear and concise description of what you expected to happen. Ex: I should see
the updates performed on storage while I was disconnected.
Illustrations
If applicable, add screenshots or video recordings to help explain your problem.
Upload your file with a drag and drop on the text area.
Environment (please complete the following information):

Liveblocks packages and packages version [e.g<EMAIL_ADDRESS><EMAIL_ADDRESS>Browser's version [e.g. chrome v99.0.4, safari]
[...]

Additional context
Add any other context about the problem here.

Was in wrong place. creating a new discussion


Publish to Bower registry

It would be nice if this polyfill could be found in the Bower registry so it's a breeze to install in projects :)

Thanks for the comment, I'll consider it when I'll have migrated the project to the new polyfill infrastructure I built for css-grid-polyfill. I'm keeping this issue open at the moment.


code-gen is not working in my project

Issue summary
Before opening this issue, I have:

[ ] Upgraded to the latest version of the relevant packages

@shopify/* package and version:

"@shopify/api-codegen-preset": "^0.0.7",

"@shopify/storefront-api-client": "^0.3.4",

"@shopify/shopify-api": "^10.0.0",

"@shopify/admin-api-client": "^0.2.9",

Node version: Hono on cloudflare

Operating system: WSL

[ ] Set { logger: { level: LogSeverity.Debug } } in my configuration, when applicable
[ ] Found a reliable way to reproduce the problem that indicates it's a problem with the package
[ x] Looked for similar issues in this repository
[ x] Checked that this isn't an issue with a Shopify API

If it is, please create a post in the Shopify community forums or report it to Shopify Partner Support

Expected behavior
What do you think should happen?
In my code, I should have type completion. This is a simple Hono project and the code works fine, but I simply get no types
Actual behavior
What actually happens?
I get returned RequestReturn and no types.
Steps to reproduce the problem
This is my code:
import { Hono } from 'hono'
import '../types/admin.generated.d.ts';
import '@shopify/shopify-api/adapters/cf-worker';
import {shopifyApi, LATEST_API_VERSION, DeliveryMethod} from '@shopify/shopify-api';
import { restResources } from "@shopify/shopify-api/rest/admin/2024-04";
const { ACCESS_TOKEN, API_KEY, SECRET_KEY, SHOP_HOST_NAME } = env(c)
const shopify = shopifyApi({
apiSecretKey: SECRET_KEY,
apiVersion: LATEST_API_VERSION,
isCustomStoreApp: true,
adminApiAccessToken: ACCESS_TOKEN,
isEmbeddedApp: false,
hostName: SHOP_HOST_NAME,
// Mount REST resources.
restResources,
});
const session = shopify.session.customAppSession(SHOP_HOST_NAME);
const queryString = #graphql {   products (first: 3) {     edges {       node {         id         handle       }     }   } }
const client = new shopify.clients.Graphql({session});
const products = await client.query({
data: queryString,
});
this is my .graphqlrc.ts file:
import {shopifyApiProject, ApiType} from '@shopify/api-codegen-preset';
import {LATEST_API_VERSION} from '@shopify/shopify-api';
export default {
// For syntax highlighting / auto-complete when writing operations
schema: https://shopify.dev/admin-graphql-direct-proxy/${LATEST_API_VERSION},
documents: ['./src//*.{js,ts,jsx,tsx}'],
projects: {
// To produce variable / return types for Admin API operations
default: shopifyApiProject({
apiType: ApiType.Admin,
apiVersion: LATEST_API_VERSION,
documents: ['./src//*.{js,ts,jsx,tsx}'],
outputDir: './types',
}),
},
};

All is good, I think it was the .request as you said!


added changelog

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@5cc6b24). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #121   +/-   ##
=========================================
  Coverage          ?   91.70%
=========================================
  Files             ?       11
  Lines             ?      241
  Branches          ?        0
=========================================
  Hits              ?      221
  Misses            ?       20
  Partials          ?        0

Continue to review full report at Codecov.

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


Renaming a token that is used in a Composition does not remap them

I have a variant set for different kind of buttons. When I rename my token from for example - "button-l" to "size.button-l" it does not remap all my variants. This apparently only happens when renaming tokens in composition tokens.

So to be clear:
You have a token named button-A
and you are using the token in a composition token
and then you rename that token to button-B
the changes are not done on tokens of type composition (eg the one where you were using it in)?

Can't reproduce the bug

My guess is this is related to https://github.com/tokens-studio/figma-plugin/issues/1528 - closing it as we'll ship a fix for that one next release.


[dev] Removes redundant call to ARAppNotificationsDelegate

This makes sure the ARAppNotificationsDelegate is called only once when a push notification is received.

Let’s wait with merging this until you’ve had the chance to check that everything works as expected on iOS 9 and 11.

I'm gonna close this for now as we've not done the testing for it, if it comes back up we should cherry-pick this commit back into a future PR.


LoadBalancerRetryContext should not be package-private

Describe the bug
The LoadBalancerRetryContext type is passed as a parameter in the LoadBalancerRetryPolicy, which is supposed to be implemented for custom policies. Being package-private makes that rather difficult.
Sample
Any custom implementation of LoadBalancerRetryPolicy outside the LoadBalancerRetryContext package should be able to reproduce the problem.

Makes sense @ajschutte .


Add support for RSpec::Core::MultipleExceptionError

Hello.
When I get several exception during test execution then I see only:
Failure:
RSpec::Core::MultipleExceptionError
Backtrace:

But this class has @all_exceptions property with a array of all exceptions.
It would be nice print all exceptions in a html report instead RSpec::Core::MultipleExceptionError.

Hi @JohnBat26
I guess that this problem is probably the same as GH-67 .
I'm trying to fix it at GH-83. Please wait until release 0.6.0 (not pre) 🙇

@gongo  thanks for quick answer. We will wait for version 0.6. :)

Hi @JohnBat26
I've released 0.6.0.pre.beta.5 that corrected this problem.
Please try this .

Hi @gongo. I've tried this. While all works OK. Now I don't see MultipleExceptionError. Thanks. :)

💪


Add logging into a file

Mostly for debugging purposes, it'd be nice to have Builda logging all of its logs into a file instead of just the standard output.

Fixed in #6


⚠ Bofrost.de has degraded performance

In e3c0ab4, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1631 ms

Resolved: Bofrost.de performance has improved in a846022 after 57 minutes.


chore(deps): update common-dev-assets digest to 67f3ce5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
3d44f8a -> 67f3ce5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This issue has been resolved in version 1.15.1 :tada:
The release is available on:

GitHub release
v1.15.1

Your semantic-release bot :package::rocket:


Editor blackout rendering bug when showing diff or doing expensive actions

Issue Type: Bug
Whenever I open diff views for search or git in random occasions over the last few months I get this annoying bug where parts of the ui get greyed out by background colored boxes and are no longer visible.
Can not reproduce intentionally and can't explain why.
Makes me freak out every time when it happens because everyhting looks good, but once you move your cursor there its gone.

VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T07:11:15.873Z)
OS version: Linux x64 4.18.9-arch1-1-ARCH

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 2101)

GPU Status
2d_canvas: unavailable_softwarechecker_imaging: disabled_offflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabled_readbackwebgl2: unavailable_off

Load (avg)
4, 4, 4

Memory (System)
15.43GB (3.98GB free)

Process Argv
/opt/visual-studio-code/code

Screen Reader
no

VM
0%

Extensions (23)

Extension
Author (truncated)
Version

ng-template
Ang
0.1.10

emojisense
bie
0.4.1

vscode-svgviewer
css
1.4.6

vscode-markdownlint
Dav
0.20.0

bazel-code
Dev
0.1.9

gitlens
eam
8.5.6

remotehub
eam
0.2.0

vsc-material-theme
Equ
2.4.2

vscode-pull-request-github
Git
0.1.6

todo-tree
Gru
0.0.92

kubesquash
ile
0.0.4

code-beautifier
mic
2.1.0

Angular-BeastCode
Mik
6.2.30

vscode-scss
mrm
0.6.2

vscode-kubernetes-tools
ms-
0.1.14

python
ms-
2018.8.0

Go
ms-
0.6.90

color-highlight
nau
2.3.0

vscode-yaml
red
0.0.17

code-spell-checker
str
1.6.10

sensitive-replace
vil
0.1.1

vscode-todo-highlight
way
1.0.4

vscode-open-in-github
ziy
1.3.6

(2 theme extensions excluded)

I also get this when moving my mouse above the code, so nothing list specific (i guess).

We are building exploration builds that use a much newer version of Electron (our UI framework). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux: Download
Windows: Download

I am currently using the aur package here:
https://aur.archlinux.org/packages/visual-studio-code-bin
Got to figure out how to use the version you suggested, might take until next week.

@kwiesmueller https://github.com/Microsoft/vscode/issues/59977#issuecomment-428440740

@bpasero Ok, thank you very much, I am trying to reinstall this version to see if there will be similar problems.


Conditional Footer Display

Modify the footer to only appear when reaching the bottom of the explore page or as part of the bottom menu section, providing a cleaner experience.

I updated the code by changing:

to:

Problem solved!


Tidy up title for customisable graphs

What does this PR do?
This PR addresses tasks set out in the JIRA tasks below (contains backend functionality)
What JIRA task is related to this PR?
https://airqoteam.atlassian.net/jira/software/projects/NLYTCS/boards/29?assignee=5d922cc14258550c23a16713&selectedIssue=NLYTCS-102
How do I test out this PR?

git fetch branch ft-tidy-up-chart-title
run pip install -r requirements/dev.txt to get all the relevant packages.
Afterwards run flask run to start the backend service and then run frontend to view the changes

Which end points should are ready for testing?
 check frontend to view the changes

Please resolve this conflicts and update the PR so that it can be merged

Could we add the Dockerfile for this service? Isn't it already in our master branch? @sserurich

@Baalmart , kindly re-check again, Dockerfile seems it already exists in the branch.


[VoiceOver] Can not focus on TextField when inside sliver list that is scrolled.

Internal: b/151285964

When a text field is in the body of a sliver list, and you scroll the sliver list under a sliver app bar, the text field is no longer editable through iOS VoiceOver.
Seems similar to https://github.com/flutter/flutter/issues/45394.
Steps to Reproduce
Using the following example app:
import 'package:flutter/material.dart';

void main() {
  runApp(Demo());
}

class Demo extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: CustomScrollView(
          slivers: [
            SliverAppBar(
              pinned: true,
              expandedHeight: 200,
              flexibleSpace: Container(height: 100),
            ),
            SliverList(
              delegate: SliverChildListDelegate([
                Container(
                  height: 400,
                  child: Center(child: TextField()),
                ),
                Container(
                  height: 400,
                  child: Center(child: Text('empty box')),
                ),
              ]),
            ),
          ],
        ),
      ),
    );
  }
}

Run the above app on an iOS device.
Enable VoiceOver mode.
Scroll the app down so that the SliverAppBar is collapsed.
Attempt to edit the text field, notice that you can not focus on the text field, despite the VoiceOver saying "Text field, double tap to edit".

Also notice that if the app is not scrolled, the TextField is editable even with VoiceOver enabled.
Expected results:
Text field can be focused on and text can be entered.
Actual results:
Text field can not be focused on or edited.

Flutter doctor output

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel fix-defaultTextStyleAboveMaterialApp, v1.15.12-pre.4, on Mac OS X 10.14.6 18G3020, locale en-US)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[!] Xcode - develop for iOS and macOS (Xcode 11.3)
    ! CocoaPods 1.7.5 out of date (1.8.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade:
        sudo gem install cocoapods
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.6)
[✓] Android Studio (version 3.5)
[✓] Connected device (5 available)

! Doctor found issues in 2 categories.

@johnsonmh I am not able to reproduce this. When I scroll all the way down, I can move a11y focus to the text field and when I double-tap it gets input focus and I can enter text.
When you say that you "cannot focus on the text field" - what do you mean by this? You can't give it a11y focus? Or you can't get it into a mode where it has input focus?
Also, what iOS device where you using?

I'm using the iPhone XS, not the XS Max, but rather the smaller size (which could account for the difference).
And by "cannot focus on the text field", I mean when I navigate to the text field with voiceover, it says "Text Field, double tap to enter", but when I double tap, it does not bring the keyboard up.
Can you try it again on your device but make the second container ~1200 pixels tall instead of 400? I think it's important that the header fully collapse before the bug reproduces.

Thanks for the information. I can reproduce this now.

I looked at this briefly. When you double-tap while the textfield has a11y focus, that double tap is not forwarded to the flutter framework (window.onSemanticsAction does not fire), which is odd (This is true whether or not the textfield is scrolled up). Somehow, double-tapping on a textfield is completely handled in the engine's a11y bridge and it seems that the engine can only properly bring up the keyboard if the actual TextField is in the center of the semantics node.
This problem can actually easily be reproduced in much simpler settings without scrolling:
import 'package:flutter/material.dart';

void main() {
  runApp(Demo());
}

class Demo extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Semantics(
          container: true,
          child: Container(
            color: Colors.green,
            height: 500,
            child: Align(
              alignment: Alignment.bottomCenter,
              child: TextField(),
            ),
          ),
        ),
      ),
    );
  }
}

The problem occurs whenever the textfield is not in the center of the a11y-focused area.

I quick work-around is to wrap the textfield in a Semantics container to make sure that the semantics node only has the size of the actual textfield:
                Container(
                  height: 400,
                  child: Center(
                    child: Semantics(
                      container: true,
                      child: TextField(),
                    ),
                  ),
                ),

@johnsonmh Is this enough to unblock the customer? Or is fixing this still customer critical?

/cc @xster FYI since the actual problem seems to be in the iOS accessibility bridge.

There's still an issue here: If you have an accessibility node with a text field inside you cannot input-focus it if the textfield is not in the center of the node, see https://github.com/flutter/flutter/issues/52863#issuecomment-604159185.

I can focus on texiifeld  after scrolll

flutter doctor -v
[✓] Flutter (Channel dev, 1.20.0-7.1.pre, on Mac OS X 10.15.6 19G73, locale
    en-GB)
    • Flutter version 1.20.0-7.1.pre at /Users/taha/Code/flutter_dev
    • Framework revision 7736f3bc90 (6 days ago), 2020-07-10 16:33:05 -0700
    • Engine revision d48085141c
    • Dart version 2.9.0 (build 2.9.0-21.2.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version
    30.0.0)
    • Android SDK at /Users/taha/Code/sdk
    • Platform android-30, build-tools 30.0.0
    • ANDROID_HOME = /Users/taha/Code/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google
      Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[✓] Connected device (5 available)
    • SM M305F (mobile)      • 32003c30dc19668f          • android-arm64  •
      Android 10 (API 29)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            •
      iOS 13.6
    • macOS (desktop)        • macos                     • darwin-x64     •
      Mac OS X 10.15.6 19G73
    • Web Server (web)       • web-server                • web-javascript •
      Flutter Tools
    • Chrome (web)           • chrome                    • web-javascript •
      Google Chrome 83.0.4103.116

• No issues found!


refactor: drop support for node 10 and add support for 16

This PR drops support for any version of node below Node 12 (the oldest version in maintenance mode) and changes CI to run on the latest versions of Node 12, 14 and 16. This also changes the target ES version to es2019 (the latest supported in node 12) and changes the lib to es2021 (the latest available in node 16). Due to how Typescript works, the project will compile to es2019, thus supporting older versions while still allowing us to write source code with recent features.
Lastly, I also changed some places in the code where new features could be used and changed package.json to specify the "engines.node" field. I also noticed package-lock.json was built before npm v7 (latest version is v8.4.0), so I highly recommend updating that, but I will leave that up to maintainers and can include that in this PR if you wish

I would also like to recommend bumping @types/node to the latest @16 version, however I cannot do that without bumping the lockfile to version 2, so let me know if you'd like that to happen

Hi @ImRodry, thanks a lot for your contribution!


Macromolecule biosynthetic process and x protein production

Hello,
"Macromolecule biosynthetic process" concerning proteins and "production" of proteins are represented quite heterogeneously in the GO.
'GO:0009059 macromolecule biosynthetic process' has a lot of children that are actually proteins, ie, where 'biosynthesis' per se does not apply, but 'production' is more appropriate. Those are:
GO:0032800  receptor biosynthetic process
GO:0042966  biotin carboxyl carrier protein biosynthetic process
GO:0045112  integrin biosynthetic process
GO:0045341  MHC class I biosynthetic process
GO:0045342  MHC class II biosynthetic process
GO:0048152  S100 beta biosynthetic process
GO:0048153  S100 alpha biosynthetic process
GO:0050757  thymidylate synthase biosynthetic process
GO:0051767  nitric-oxide synthase biosynthetic process
GO:0032964  collagen biosynthetic process
GO:0002378  immunoglobulin biosynthetic process
Proteins under the child term "GO:0034645 cellular macromolecule biosynthetic process"
GO:0009101  glycoprotein biosynthetic process
GO:0042158  lipoprotein biosynthetic process
GO:0042541  hemoglobin biosynthetic process
GO:0042964  thioredoxin biosynthetic process
GO:0042965  glutaredoxin biosynthetic process
GO:0042967  acyl-carrier-protein biosynthetic process
GO:0043172  ferredoxin biosynthetic process
Then in a completely different area of the GO we have

GO:0044707 single-multicellular organism process
-- GO:0001816 cytokine production
--- having as children, many cytokines, as well as other stuff, such as GO:0032605 hepatocyte growth factor production and GO:0090269 fibroblast growth factor production,  GO:0071604 transforming growth factor beta production (surely those are misplaced?)

I would argue that only 'translation' results in production of proteins. So, in all cases, what we are annotating is 'regulation of x production'  - in other words, all those terms could be placed under 'GO:0023019  signal transduction involved in regulation of gene expression' (since 'gene expression' as defined by GO includes protein production).
So I propose to do the following:

for all the x biosynthetic process terms above, rename to 'regulation of x production' and move under GO:0023019     signal transduction involved in regulation of gene expression
Merge GO:0001816 cytokine production GO:0001817  regulation of cytokine production
Fix parentage of terms under 'cytokine production', we should perhaps create a term 'regulation of growth factor production'.

Thanks,
Pascale
Reported by: pgaudet
Original Ticket: geneontology/ontology-requests/10600

See GOC meeting discussion: https://docs.google.com/document/d/1HjFgya5d5vL63GoU4k_M0CkOBPIe7xjzOL5_WGtUcPM/edit#
Cytokine production, https://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0001816. Proteins annotated to cytokine production should really be annotated to ‘regulation of cytokine production’, https://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0001817
David H: proposes get rid of cytokine production and retain regulation of cytokine production as a regulation of biological quality where ‘cytokine production’ refers to the measurement of levels of a cytokine.
Aleks: general pattern (e.g. apoptotic process) where there is a signalling phase and an executive phase
Judy: perhaps check with Alex Diehl (who put those terms in initially)

Action Item: move protein production (and protein secretion?) to  regulation of production’. Tickets have already been generated (follow the link above)

I don't think the AI is quite right. We already discussed in this ticket why 'regulation of production' is not good. I think the resolution we made at the meeting was to define as 'regulation of X levels', making use of OBA

Hi Chris,
'regulation of X levels sounds good', as long as it doesn't limit to protein, since in some instances the mRNA may be measured. The best parent is 'regulation of gene expression, since this encompasses both mRNA and protein.
Cheers,
Pascale

Based on the discussion here: https://github.com/geneontology/go-ontology/issues/18370
I am closing this. I think that the production classes are useful to the community.

Production yes- the question was about 'biosynthetic process' ; we still have loads of those terms.


Add disable click option

Added disableClick which will disable the opening of the window when the user clicks the tray icon. You can still use showWindow to open the window.
This allows for multiple windows to be assigned to a tray icon. In my instance i have the main window still assigned to the default option, and a about window which has disableClick=true which is opened via a context menu. Both windows open under the tray icon nicely :)

Bump


issue with import and export

i am unable to import a json file which contains several links
i also exported my current list but instead of json file it got saved as a .txt file
if possible can you add " import from html file" as it is already support in all browsers

i am unable to import a json file which contains several links

Import/export is pretty dumb right now; I will fix it as soon as I fix the others.

if possible can you add " import from html file" as it is already support in all browsers

Yeah, sure. I'll see what I can do. If I'm not mistaken, you are referring to the browser bookmark exports/imports. This will also be added as soon as I release 0.8.x. Thanks for mentioning this.

First of all, I would like to congratulate you on your application. I just discovered it.
I find it unfortunate that an HTML file containing internet links or bookmarks cannot be used for importing or exporting bookmarks.
The JSON format is problematic. Indeed, most web browsers on computers or some web browsers on Android offer the option to export favorites or bookmarks to an HTML file (containing our internet addresses).
It would be really great if you could implement this feature.

@franco27

The JSON format is problematic

The thing is, I built this project only for myself, so I was fine with it 😅😅; but now, as HTML seems the best option for export/import, I'll remove the current mechanism and will release the HTML-based export/import soon.

I would like to congratulate you on your application.

:)

Thank you very much, that's great news. On Crowdin, I started the French translation.

On Crowdin, I started the French translation

Thank you for taking the time to add those; I appreciate it.

@franco27

The JSON format is problematic

The thing is, I built this project only for myself, so I was fine with it 😅😅; but now, as HTML seems the best option for export/import, I'll remove the current mechanism and will release the HTML-based export/import soon.

I would like to congratulate you on your application.

:)

will it auto update like it does for browser ?

@Zaxx69
auto-update? I'm not sure what you mean by that 🤔

HTML-based imports/exports are now available in the latest release, along with the fixes for this issue: https://github.com/sakethpathike/Linkora/releases/tag/release-v0.10.0
Thanks for raising this issue; I really appreciate it :)


Fix issues with security changes in rollup runnner (#161)

Issue #, if available:

https://github.com/opensearch-project/index-management/issues/162
https://github.com/opensearch-project/index-management/issues/163

Description of changes:
Fixing the issues with RollupRunner when security filtering is enabled and when non-admin user with incomplete permissions
CheckList:

[X ] Commits are signed per the DCO using --signoff

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.

Codecov Report

Merging #164 (4b46f12) into 1.1 (4386d96) will decrease coverage by 0.07%.
The diff coverage is 40.74%.

@@             Coverage Diff              @@
##                1.1     #164      +/-   ##
============================================
- Coverage     75.80%   75.73%   -0.08%
  Complexity     1917     1917
============================================
  Files           260      260
  Lines         10992    11006      +14
  Branches       1720     1721       +1
============================================
+ Hits           8333     8335       +2
- Misses         1708     1719      +11
- Partials        951      952       +1

Impacted Files
Coverage Δ

...g/opensearch/indexmanagement/util/SecurityUtils.kt
20.00% <0.00%> (ø)

...opensearch/indexmanagement/rollup/RollupIndexer.kt
53.96% <18.18%> (-3.18%)
:arrow_down:

...arch/indexmanagement/transform/TransformIndexer.kt
67.92% <58.33%> (-3.82%)
:arrow_down:

.../opensearch/indexmanagement/rollup/RollupRunner.kt
65.48% <100.00%> (ø)

...earch/indexmanagement/transform/TransformRunner.kt
82.97% <100.00%> (ø)

...ent/rollup/action/explain/ExplainRollupResponse.kt
75.00% <0.00%> (-10.00%)
:arrow_down:

...dexmanagement/transform/model/TransformMetadata.kt
85.54% <0.00%> (-3.62%)
:arrow_down:

...nt/rollup/action/stop/TransportStopRollupAction.kt
69.51% <0.00%> (-1.22%)
:arrow_down:

.../rollup/action/start/TransportStartRollupAction.kt
65.06% <0.00%> (-1.21%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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


Extend MetalLB CR to support nodeselector

There is a request to limit MetalLB speaker Daemonset to specific worker nodes, this PR added NodeSeletor capability to MetalLB CR
for more details on how to use nodeSelector in k8s pls refer to
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/

One last nit: I'd try to explain the rationale behind the change in the first commit.
IIUC, this is necessary so we are able to use metallb l2 in clusters where we only have a subset of nodes connected to the subnet where we want to advertise services.
Then looks good.

LGTM


Ignoring bugs, any owned value that is used in a read only manner should be able
to be borrowed and used in such a place as well.
Originally this code (before refactoring) would assert, so we were checking that
this could not happen in our asserts builds. Due to refactoring the assert was
lost. This changes the code to have the assert again, this time explicitly
instead of inside the method.

@swift-ci test

@swift-ci test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - 83dbdc4b048fd6c9e9d8a2113b2c395cdb2819b9

@swift-ci test linux platform


Training continues without horizon value entered

Model Builder Version: In which Model Builder version was the bug encountered?
Visual Studion Version: In which Visual Studio version was the bug encountered?
Bug description
A clear and concise description of what the bug is.
Steps to Reproduce

List the minimal steps required to reproduce the bug.
Thanks for reporting!

Expected Experience
A description of what you expected to happen. If applicable, add screenshots or "Machine Learning" Output Logs to help explain what you expected.
Actual Experience

Additional Context
Add any other context about the problem here, such as unusual system configurations, network restrictions, etc.

Not repro this issue on latest main: <IP_ADDRESS>7601
The default value is 10:


runtime: "goroutine stack exceeds 250000000-byte limit" on linux-arm

We're seeing stack overflows this week in various tests on the linux-arm builder.
This may be related to #35349, but the stack traces on linux-arm are more diverse.
CC @ianlancetaylor @aclements @mknyszek @cherrymui
2019-11-08T19:24:30-e6c12c3/linux-arm
2019-11-07T19:20:35-ceca99b/linux-arm
2019-11-07T18:39:03-05aa4a7/linux-arm
2019-11-07T16:13:31-0bf2eb5/linux-arm
2019-11-05T20:56:05-81559af/linux-arm
2019-11-05T17:19:16-1b3a1db/linux-arm

These stacks are not large at all, so the problem is not actual stack overflow, but a false report of stack overflow.

I can imagine a possibility: if there are both a synchronous preemption request (by clobbering the stack guard) and an asynchronous one (by signal), and the goroutine in a function prologue first sees the clobbered stack guard, so it will call morestack. If the signal lands after the CMP instruction but before the call to morestack, it will be asynchronously preempted, enter the scheduler. When it is resumed, the scheduler clears the preemption request, unclobbers the stack guard. But the resumed goroutine will still call morestack (as it has passed the CMP instruction). morestack will, as there is no preemption request, double the stack unnecessarily. If this happens multiple times, the stack may grow too big, although only a small amount is actually used.
I let it print the current stack bounds in the stack-too-large error message, and the stack is indeed quite large, with only a small amount used:
runtime: goroutine stack exceeds 250000000-byte limit
	sp=0x1847dad8 stack=[0x10480000, 0x18480000]
fatal error: stack overflow

In theory this can happen on other platforms. Not sure why this is only seen on the ARM builder.

Maybe we want to disable async preemption in function prologue between the CMP instruction and the call to morestack? As it will call morestack, it will be preempted anyway.

@cherrymui That sounds like a good idea.
I think we might have to start at the load of the stack guard, as the CMP result is predestined at that point. But then maybe we need to only prevent async preemption if that loaded value is in fact the preempted guard.
Tricky.

See also #35784.

Should we also close #35784?

Yeah, I think we can close that.


Demo pages should link to official AdminLTE demo pages

Documentation has a link, but it would be good if the "live demo" pages also had clear links to the official AdminLTE demo.
The official AdminLTE demo has more content and is more comprehensive. But the "live demo" is good for an overview, and also quickly verifying most content displays as expected.

By "live demo" pages, do you mean all of the sample pages that are available when you add the URLs included with the project? Or are you only referring to the "demo-css" page from those URLs? I think a link could probably be added to all of them pretty easily. Though if you are searching for this package, you are probably already familiar with the AdminLTE2 package. Especially if you read any of our documentation.


how to set epoch and  batch_size

For SSL DefectMaker  training task, you can create  and assign a new param by :
1.  create a new param for the DefectMaker task.
like in reb_mvtec/param_space.py, you can create a new param by  the following snippet:
res18_dm_com6_bs2048_epo500= res18_dm_com6_bs1024_epo300.clone()

set_train_param(res18_dm_com6_bs2048_epo500,num_iter_bofer_update_grad=6,batch_size=2048,epoches=500  )

2. then you can use it in your command line by:
$ cd  REB/projects/reb_mvtec
#  Self-supervised learning  (fine-turning ImageNet-pretrained model with DefectMaker))  Resnet18
python main.py  -exp_name res18_dm_com6_bs2048_epo500   -K 9 -run_name run1  -run_mode 0

# only run LDKNN (after fine-turning ImageNet-pretrained model with DefectMaker)  Resnet18
$ python main.py  -exp_name res18_dm_com6_bs2048_epo500    -K 9 -run_name run1  -run_mode 1

``


missing LedgerEntry fields

there were a few missing fields in LedgerEntry that are present when calling /ledgers/{currency}

package updated


Fatal error encountered

Hi,
im getting always this error, no matter what mode and what settings im using:
21:03:24: Fatal error encountered:
21:03:24:
21:03:24: Traceback (most recent call last):
21:03:24:   File "main.py", line 155, in main
21:03:24:   File "twitch.py", line 587, in run
21:03:24:   File "twitch.py", line 747, in _run
21:03:24:   File "twitch.py", line 1656, in bulk_check_online
21:03:24:   File "asyncio\tasks.py", line 571, in _wait_for_one
21:03:24:   File "twitch.py", line 1387, in gql_request
21:03:24: exceptions.GQLException: [{'message': 'service error', 'path': ['channel', 'viewerDropCampaigns']}]
21:03:24:
21:03:24: Exiting...
21:03:24:
21:03:24: Application Terminated.
21:03:24: Close the window to exit the application.

Hello,
I need to close this one as a duplicate of #590, even though it was submitted later - this is because it contains more information about the issue. You can post your traceback there if you want to, but since it's the same, you don't need to, as I'm already aware of the issue.


Error Parsing Error: The Keyword 'Import' Is Reserved - Upgrading SPFX v1.10 to v1.18.2

Hey @s-KaiNet. I'm running into issues when upgrading my SPFX webpart from 1.10 to 1.18.2. I'm currently using spfx-fast-serve-helpers 1.18.0.  My fast serve doesn't appear to working as I'm not seeing any of my local changes appear on my site page after serving my webpart.  Additionally, after serving, when I make a local change and save I'm receiving the following error in my terminal: 1:1 error Parsing error: The keyword 'import is reserved.  I've deleted my lock file and node_modules folder multiple times. I've updated my eslintrc.js, tsconfig.js, and package.json files after referencing your example here.  I've tried serving the webpart with the flag --eslint=false and am still running into the same error message.  Also, I've updated my package.json serve script to the following with no success: "set NODE_OPTIONS=--openssl-legacy-provider --max-old-space-size=8000 && gulp bundle --custom-serve --max_old_space_size=8000 && fast-serve".  Let me know if there's any additional info I can provide that'd be of assistance to you.  Thanks!

<EMAIL_ADDRESS>

please in your project run npm i<EMAIL_ADDRESS>-DE, then run again npm list spfx-fast-serve-helpers - it should print 1.18.11 version. After that try npm run serve again and see if it works.

Was able to successfully install 1.18.11 and validate using 'yarn list spfx-fast-serve-helpers'.  Getting the above error message when attempting to serve.

do you have fast-serve/config.json file? If yes, could you delete it and try running serve again?

I did have the fast-serve/config.json file and deleted it.  Was able to successfully serve.  After attempting to make a change in my local repo, I'm still running into the intiital error '1:1 error Parsing error: The keyword 'import' is reserved'.  Also, I made a UI change in my repo to see on the initial serve if it'd be reflected in the browser, and I did not see the update there.

In this case try to run fast-serve with --eslint=false parameter.

This worked.  Is there a way to now successfully add back the fast-serve/config.json file or does that need to stay removed?

You could add the config file by running npx fast-serve config add. Then add any supported options there.
But since --eslint=false worked for you, then still something wrong with your .eslintrc.js file, I recommend you to find out what's wrong, because eslint is very useful feature.


Reformat

Use prime number 3907 for opcache.max_accelerated_files
Set the opcache.mmap_base to 0x20000000 to get rid of Base address marks unusable memory region
And changed the value of  opcache.interned_strings_buffer to 16 because 8 is too little

Use a descriptive commit message
Do not alter the parameters unless you know what you're doing

First  off it's good to use prime numbers rather than the number 4000 for  opcache.max_accelerated_files
Sadly I don't know the significance of the value 0x20000000 but I can ensure you that this helps solving issues related to Base address marks unusable memory region(tried and tested).
And at last opcache.interned_strings_buffer should be set to 16MB. This setting improves performance and and saves memory. This saves memory caching one string and calling it every time it's repeated. I explained so you know that I actually understand what is it for.

Do not blindly tune the parameters. Benchmark and show the difference.
As dktapps showed in the issue comment, the random generated value exist as a address base workaround. We cannot add something that other people don't need.


Chrome 40.0.2214.111 m issue

Menu doesn't open properly, and when it does submenus open only half way in the latest Chrome version (both desktop and mobile). Earlier version works fine.
The examples on the site are affected by this as well.
Anyone else have this issue?

I'm on version 40.0.2214.111 (64-bit) on a macbook but can't find anything wrong with the menu or examples.

Any update on your side?
I still can't reproduce the issue.

I'm now on 40.0.2214.115 m and the issue is gone!


Remove provider initializations

Modules should not initialize providers
https://github.com/GoogleCloudPlatform/terraform-google-out-of-band-security/blob/d5bcc43e9e29fcaf8a49d6fd28c3900fdf6bd1d6/main.tf#L17-L24

Fixed without having to create a PR. Please let me know if a PR was necessary. Thanks!


isDashboardSelectorAvailable as Boolean instead of String

Related to issue #69

@K-Phoen please review&merge&release

It might result in breaking changes who rely on String type for their checks.

@Shandur I don't think it's a big deal. People are usually converting it into that boolean, so they simplify their code.. Just a minor warning in release notes...


Fix #314: no_update is not applied to subclasses

Fix for #314

Looks good to me man. I'll merge this for you now.


Refactor Route test

Cleans up the route test and makes the setup/expectations clearer in each test case.

OoooOOoOOo mumma, our code climate is gonna go through the roof
LGTM - @mkorfmann ?


Merge pull request #1 from Microsoft/develop

Update develop branch from original

Please ignore this - made accidentaly.


Correction for raw affiliation Inserm U1111, CNRS UMR 5308, Inserm/CNRS/Université Claude Bernard, Lyon, France

Correction needed for raw affiliation Inserm U1111, CNRS UMR 5308, Inserm/CNRS/Université Claude Bernard, Lyon, France
raw_affiliation_name: Inserm U1111, CNRS UMR 5308, Inserm/CNRS/Université Claude Bernard, Lyon, France
new_rors: 029brtt94;02vjkv261;02feahw73;059sz6q14
previous_rors: 029brtt94;02vjkv261;02feahw73
works_examples: W2443136200
contact: 14ae688797c37caab98932cf3adb8a2a:38c218b09a9038609fe0849c8d18 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


[Fix] Avoid typescript-eslint deprecation warnings about typeParameters

Motivation
When using eslint-plugin-react (7.35.0; latest) in a Typescript project with @typescript-eslint/parser": "^7.0.0", I got the following warnings when running ESLint:
# NODE_OPTIONS=--trace-deprecation yarn lint
(node:236) DeprecationWarning: The 'typeParameters' property is deprecated on CallExpression nodes. Use 'typeArguments' instead. See https://typescript-eslint.io/troubleshooting/faqs/general#the-key-property-is-deprecated-on-type-nodes-use-key-instead-warnings.
    at Object.defineProperty.get (/builds/cherrymoss/immigration/node_modules/@typescript-eslint/typescript-estree/dist/convert.js:2545:29)
    at markAnnotatedFunctionArgumentsAsDeclared (/builds/cherrymoss/immigration/node_modules/eslint-plugin-react/lib/util/propTypes.js:1037:22)
    at /builds/cherrymoss/immigration/node_modules/eslint-plugin-react/lib/util/Components.js:281:9
    at Array.forEach (<anonymous>)
    at mergedHandler (/builds/cherrymoss/immigration/node_modules/eslint-plugin-react/lib/util/Components.js:280:16)
    at ruleErrorHandler (/builds/cherrymoss/immigration/node_modules/eslint/lib/linter/linter.js:1076:28)
    at /builds/cherrymoss/immigration/node_modules/eslint/lib/linter/safe-emitter.js:45:58
    at Array.forEach (<anonymous>)
    at Object.emit (/builds/cherrymoss/immigration/node_modules/eslint/lib/linter/safe-emitter.js:45:38)
    at NodeEventGenerator.applySelector (/builds/cherrymoss/immigration/node_modules/eslint/lib/linter/node-event-generator.js:297:26)

Changes

Change all references to typeParameters so that they:

Try looking for typeArguments first (to support @typescript-eslint/typescript-estree v7+)
Fall back to typeParameters (to support @typescript-eslint/typescript-estree vv+)

Testing
Used yarn patch-package to also patch propTypes.js and verified that the deprecation errors disappeared on my project.

Unfortunately we're not even testing on v6 yet, let alone v7 - see #3629, which I think this would need to be blocked on (or, that one would cover this one)


Use Vite Plugin with Electron Forge

Use the Vite plugin with Electron Forge's plugin system.

git fetch origin
git checkout 20-use-vite-plugin-with-electron-forge


disable auto js extensions

Here's a prototype for https://github.com/ModuleLoader/es6-module-loader/issues/218.

In normalize, we normalize relative to the parentName, and when none is provided we normalize relative to the baseURL.
Paths are applied in normalize, before normalization, only on names that do not start with "scheme:", "./", "../", "/".
Locate does a final normalization relative to the baseURL

All tests passing.
Feedback welcome @caridy.

This has been replaced by https://github.com/ModuleLoader/es6-module-loader/pull/317.


debugging py_test targets with pytest main "hangs"

Description of the bug:
pytest targets executed with pytest.main() seems to hang, but appears to be running stat() every file in the filesystem.  The debugging session doesn't ever start because there are inevitably unreadable files with throws errors.
Which category does this issue belong to?
Intellij, PyCharm
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
a minimal repo can be found here
If you debug the unit_test target, I am able to set successfully debug.  However, if you try to debug the pytest_test target, it "hangs" on with the folllowing:
import sys; print('Python %s on %s' % (sys.version, sys.platform))
/usr/bin/python3 "/Users/rkrishnamurthy/Library/Application Support/JetBrains/IntelliJIdea2024.2/plugins/python-ce/helpers/pydev/pydevd.py" --multiprocess --qt-support=auto --client <IP_ADDRESS> --port 51013 --file /private/var/tmp/_bazel_rkrishnamurthy/5303facb39f6d1f7ffd509576224e2f0/execroot/videoamp/bazel-out/darwin_arm64-fastbuild/bin/demo/python/idea_debug/py/py_test
Connected to pydev debugger (build 242.23339.11)
============================= test session starts ==============================
platform darwin -- Python 3.9.18, pytest-7.0.1, pluggy-1.0.0
rootdir: /

if you pause/restart the debugging session a few times, there are repeated calls to Path.stat() in lib/python3.9/pathlib.py
Which Intellij IDE are you using? Please provide the specific version.
IDEA ultimate 2024.2.3
What programming languages and tools are you using? Please provide specific versions.
python 3.9 toolchain
What Bazel plugin version are you using?
2<IP_ADDRESS>.1-api-version-242
Have you found anything relevant by searching the web?
There is an ongoing slack thread, however, the ability to debug py_test targets is new, so I suspect people haven't run into this yet.
Any other information, logs, or outputs that you want to share?
No response

Hey @rajukrishnamurthy, could you verify if #6847 fixes the issue for you?

@agluszak Can I get this from the beta channel?

@agluszak I pulled down master built and installed the plugin and am getting the same behavior with the repo I referenced above.

Oh, just found we've already received this report in #5146

@agluszak I pulled down master built and installed the plugin and am getting the same behavior with the repo I referenced above.

It's not merged yet, so you need to build branch agluszak/fix-6824

@rajukrishnamurthy I have merged that, you can try master branch now

Apologies, I didn't look at that closely enough.  Okay, with the fix in place it is no longer scanning the entire filesystem, however it doesn't seem to actually run the test.  I've noticed a couple of things:

when pytest.main() is called in my stripped down example, I can trace to pytest_cmdline_main return NO_TESTS_COLLECTED.  Perhaps my main is incorrect?
We override the py_test macro where we set environment variables args that we use to pass to pytest.main(). It seems to bypass that entirely and use the py_test from rules_python.  I've added an example with an override of py_test defined here.  This is probably a separate problem, but I imagine many people do this.

In both cases, bazel test runs the tests correctly.
I'm happy to continue to be a tester and I will try to be more timely in my response.
Thanks!

Regarding 1,  I cannot reproduce the issues you're describing. I can normally debug all of your 3 examples. Please see the video.
https://github.com/user-attachments/assets/9bf7b9fb-6ecf-40a2-8f63-d948d08d284a
Note that I'm using a python run configuration, not a bazel run configuration.
Regarding 2, as far as I know (although I have very little experience with how Python is exactly implemented), Bazel rules are not at all involved in debugging and running tests if they are run as a python run configuration. They are probably run through IntelliJ's native test runner, not through Bazel. If you want to pass custom env variables, you can do so in the run configuration.

Or, if you want to run the test through Bazel, you can create a run config like this:

Here, I agree, something weird is going on. If you Run this run configuration, it will use the env specified in your custom rule. If you debug it, it will use the one set in the run configuration.
Could you please record a video of how you run the test?

Hi @agluszak @rajukrishnamurthy
I recently also had problems when using a pytest wrapper script as part of py_test + debug. I was able to get it mostly working.
See my comment here: https://github.com/bazelbuild/intellij/issues/6821#issuecomment-2439697168 (you can ignore everything above this comment because my initial theory was wrong)
While debugging the problem, I noticed two things:

The working path within the python pytest script was the system root / and not the sandbox root. This was resulting in "file not found errors"
Not all the env values were being passed which are passed when the test target is run via bazel CLI

I was able to fix the "file not found" error by extracting the sandbox root from the absolute path of the python pytest wrapper script located in the sandbox (other methods of getting the sandbox root didn't work because the variables wasn't showing up).
import glob
import contextlib

@contextlib.contextmanager
def new_cd(x):
    d = os.getcwd()

    # This could raise an exception, but it's probably
    # best to let it propagate and let the caller
    # deal with it, since they requested x
    os.chdir(x)

    try:
        yield

    finally:
        os.chdir(d)

if __name__ == "__main__":
    import os
    import sys

    import pytest

    # NOTE: RUNFILES_DIR isn't present when this script is called via the intelij plugin. I had to comment it all out.
    # runfiles = os.environ.get("RUNFILES_DIR")
    # logic with runfiles

    if os.environ.get("PYCHARM_HOSTED"):
        # sys.argv[0] this has the location of pytest_test.py within the sandbox.
        path_to_script = sys.argv[0].replace("custom_main/pytest_test.py", "")

        with new_cd(path_to_script): # change the working directory to the sandbox root
            sys.exit(pytest.main(sys.argv[1:]))
    else:
        # Normal case when running a bazel test from the cli "bazel test ..."
        sys.exit(pytest.main(sys.argv[1:]))

cc @sellophane


chore: eslint config exivity

I had some version conflicts in glass when I had them as direct dependencies.

I had some version conflicts in glass when I had them as direct dependencies.

What you can do, is remove the lockfile from this project. I recently learned this is considered best practice for packages: https://github.com/sindresorhus/ama/issues/479#issuecomment-310661514


feat: port CategoryTheory.Limits.Shapes.WidePullbacks

[x] depends on : #2368

Should have squashed...

Thanks :tada:
bors merge


Prevent name collision when parsing multiple files

Fixes #5

Resolved in https://github.com/ben-eb/cssnano/releases/tag/v4.0.0-rc.0.


Texts for singulars

I used to see the following when translating:

Used on %u URL
Used on %zu URLs

But today I also saw this:

Delete Bookmark
Delete %u Bookmarks

I guess in English and German at least, we could always drop the %u for singulars?

Yes, in strings with a single format placeholder, it is perfectly OK to leave it out when if it isn't needed. These strings basically go into printf(), and that will ignore unused values.

Done!


double namespace/prefix when using MultiProcessCollector

Hi,
We've been trying to wrap around prometheus client in order to standardize some things within our application (in this case, prefixes/namespaces). We have one application that uses a process pool and so we started to use the MultiProcessCollector and faced an issue with metrics appearing with a duplicated prefix. Tracing this down we found that the first version was kind of our own fault, but then moving to using the namespace argument that this is a deeper-running issue with the client.
I don't know why this only happens with MultiProcessCollector, as I've seen it happen internally in the prometheus lib itself while debugging this issue without MultiProcessCollector, but then somehow the weird metrics don't appear in the final output.
Minimal POC below, please ensure that you've set prometheus_multiproc_dir env var to somewhere convenient to you and that you don't forget to remove the *.db files between runs.
#!/usr/bin/env python

from prometheus_client import generate_latest
from prometheus_client import CollectorRegistry
from prometheus_client.multiprocess import MultiProcessCollector
from prometheus_client import Counter

prometheus_registry = CollectorRegistry()
MultiProcessCollector(prometheus_registry)

MY_PREFIX = "dejavu"

class MyCounter1(Counter):
    def __init__(self, name, *args, **kwargs):
        name = "_".join((MY_PREFIX, name))
        super().__init__(name, *args, **kwargs)

class MyCounter2(Counter):
    def __init__(self, name, *args, **kwargs):
        super().__init__(name, namespace=MY_PREFIX, *args, **kwargs)

if __name__ == "__main__":
    counter_1 = MyCounter1("first", "the premiere", ("label_one", "label_two"), registry=prometheus_registry)
    counter_2 = MyCounter2("second", "the less premiere-y one", ("label_three", "label_four"), registry=prometheus_registry)

    counter_1.labels("one", "two").inc(3)
    counter_2.labels("three", "four").inc(3)

    print(generate_latest(prometheus_registry))

this should result in:
# HELP dejavu_dejavu_first_total Multiprocess metric
# TYPE dejavu_dejavu_first_total counter
dejavu_dejavu_first_total{label_one="one",label_two="two"} 3.0
# HELP dejavu_dejavu_second_total Multiprocess metric
# TYPE dejavu_dejavu_second_total counter
dejavu_dejavu_second_total{label_four="four",label_three="three"} 3.0
# HELP dejavu_first_total the premiere
# TYPE dejavu_first_total counter
dejavu_first_total{label_one="one",label_two="two"} 3.0
# HELP dejavu_first_created the premiere
# TYPE dejavu_first_created gauge
dejavu_first_created{label_one="one",label_two="two"} 1.591620096175255e+09
# HELP dejavu_second_total the less premiere-y one
# TYPE dejavu_second_total counter
dejavu_second_total{label_four="four",label_three="three"} 3.0
# HELP dejavu_second_created the less premiere-y one
# TYPE dejavu_second_created gauge
dejavu_second_created{label_four="four",label_three="three"} 1.591620096175297e+09

notice the dejavu_ and dejavu_dejavu_ prefixes. This also happens for Histograms, etc.
this POC was run on Ubuntu with a fresh virtualenv running python 3.8.2 and prometheus-client==0.8.0
Thank you!

Why are you subclassing Counter? That's not supported - can you reproduce this without doing that?

Also custom registries aren't compatible with multi-process mode, the custom registry should only have the MultiProcessCollector in it.

Thanks for the super quick response!
What do you mean by custom registry? I (thought) i followed the examples provided in the multiprocess mode section of the README.md
The reason we're subclassing here is only to provide a relatively automatic/standardized way for our applications to provide a prefix to metric names without having to constantly add it each time a metric is declared/registered.

That code isn't following the examples, you'll note that the custom registry is only used for exposition - not metrics.
I'd generally recommend having the duplication, it makes grepping the codebase to find a metric easier.

Why are you subclassing Counter? That's not supported - can you reproduce this without doing that?

Can't do so, no, but subclassing/extending would be (I'd think) anybody's go-to method of customizing a library with minimal pain.

That code isn't following the examples, you'll note that the custom registry is only used for exposition - not metrics.

okay, that cleared up some weirdness i was seeing in the metrics (certain metrics appearing twice) but the prefix issue (if you consider it one) remains - personally it didn't strike me as obvious to declare a new registry but not attach metrics directly to it.

I'd generally recommend having the duplication, it makes grepping the codebase to find a metric easier.

This is a solved problem for us as we put the metrics in one location and wrap them with functions that make them easy to use as well as provide common instantiations/set labels where applicable. We've standardized on how we do prefixes on metrics and each application only needs to set a configuration which sets the prefix on all metrics of that application. This isn't my preferred approach personally but is an existing standard throughout the organization and I'm trying to make it something that nobody has to think actively about.
This approach also means that static analysis in our IDEs can detect where different metrics are used.
new working example, if you're interested:
#!/usr/bin/env python

from multiprocessing import Pool

from prometheus_client import generate_latest
from prometheus_client import CollectorRegistry
from prometheus_client.multiprocess import MultiProcessCollector
from prometheus_client import Counter

prometheus_registry = CollectorRegistry()
MultiProcessCollector(prometheus_registry)

MY_PREFIX = "dejavu"

class MyCounter1(Counter):
    def __init__(self, name, *args, **kwargs):
        name = "_".join((MY_PREFIX, name))
        super().__init__(name, *args, **kwargs)

class MyCounter2(Counter):
    def __init__(self, name, *args, **kwargs):
        super().__init__(name, namespace=MY_PREFIX, *args, **kwargs)

if __name__ == "__main__":
    counter_1 = MyCounter1("first", "the premiere", ("label_one", "label_two"))
    counter_2 = MyCounter2("second", "the less premiere-y one", ("label_three", "label_four"))
    counter_3 = Counter("third", "the vanilla counter", ("label_five", "label_six"), namespace=MY_PREFIX)

    counter_1.labels("one", "two").inc(1)
    counter_2.labels("three", "four").inc(1)
    counter_3.labels("five", "six").inc(1)

    def increment_counters(pid):
        counter_1.labels("one", "two").inc(1)
        counter_2.labels("three", "four").inc(1)
        counter_3.labels("five", "six").inc(1)

    with Pool(processes=4) as pool:
        pool.map(increment_counters, [1, 2, 3])  # whatever data, stolen from multiproc pool base example

    print(generate_latest(prometheus_registry))

generates:
# HELP dejavu_dejavu_first_total Multiprocess metric
# TYPE dejavu_dejavu_first_total counter
dejavu_dejavu_first_total{label_one="one",label_two="two"} 4.0
# HELP dejavu_dejavu_second_total Multiprocess metric
# TYPE dejavu_dejavu_second_total counter
dejavu_dejavu_second_total{label_four="four",label_three="three"} 4.0
# HELP dejavu_third_total Multiprocess metric
# TYPE dejavu_third_total counter
dejavu_third_total{label_five="five",label_six="six"} 4.0

which is obviously doing better in terms of general duplications (my bad), but still has a double prefix.
if you consider this an expected behaviour, feel free to close

Hmm, the only one showing the problem there is where there's subclassing. So there's something weird going on here, but I'm not sure where the fault lies.

each application only needs to set a configuration which sets the prefix on all metrics of that application.

This is not a good practice, see https://www.robustperception.io/target-labels-not-metric-name-prefixes

From the tracing i managed to do it's related to calling the class's __init__ function again internally in the library's metrics.py file here - with the name, since the name is already prefixed, it gets added again.
There was a lot of other stuff going on and i had already spent a lot of time just tracing this so i couldn't tell why this happens only with multiproc and not in the default single process mode.

This is not a good practice, see https://www.robustperception.io/target-labels-not-metric-name-prefixes

Myself and the SRE I work with are convinced - there's unfortunately too much history here for us to rip that up at it's current state. Once the lib is in place and retrofitted to enough project it may be an easy en-masse change to a label instead, without changing hundreds of lines of code through tens of codebases. Embrace, extend, extinguish in a good way :joy: - but we can't do that if we can't wrap/customize some common functionality, which is why I'm here.
For the moment I hackily worked around it in our wrapper lib, I'm still happy to help investigating though, and if a solution comes to my head from the limited prom code i looked at i might dish out a PR, but honestly, i can't commit to that.

From the tracing i managed to do it's related to calling the class's init function again internally in the library's metrics.py file

That'd be incorrect usage then as the subclassing is interfering with the implementation. I'm not sure there's anything to be done here on the client_python side, especially as the particular use case here is in the service of a bad practice.

a suboptimal practice is not necessarily a bad practice - but point taken.
I'd be quite surprised if nobody has tried to subclass, extend, or otherwise wrap this library and found it difficult to do - to explicitly not support it however, is surprising.
Of course, in the end it is your time and your decision and I'd like to thank you for that and for responding here. Have a good week!

Generally the library is there to be build on top of, not to poke around its innards. If you want to do something fancier it's best to use a custom collector.


Fix consumed insets handling when using asPaddingValues()

#376

How would the nesting look like? Would I have to pass the parent content padding to the child? And how?

Replaced by #534.


How to export the flattened version generated by truffle-flattener?

Hi, it seems that this script only generate the flattened version and print them into the terminal. Is there a way to export the flattened into a file? If not is there a point in generating the flattened version and print them into the terminal?

truffle-flattener mycontract.sol > mycontract-flattened.sol

The size of the pipe is limited, so it would be wise to have --output file
https://stackoverflow.com/questions/6977561/pipe-vs-temporary-file
Also some contracts have unicode, not sure what happens with those.


rename yml files

to use visual designer instead of yml files

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


SimpleSchema.RegEx.IPv4 not validating

So I've a simple collection with the below shortened schema:
ipAddress: {
    type: SimpleSchema.RegEx.IPv4,
    label: "Server IP",
    defaultValue: "<IP_ADDRESS>",
    optional: true
  }

When I go an update it using autoforms as
{{#autoForm collection="Settings" doc=settings id="updateSettingsForm" type="update"}}
  {{> afQuickField name='ipAddress'}}
{{/autoform}}

Anything I type into the field gets accepted and written to the document, with no errors or warnings anywhere.
Versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Meteor <IP_ADDRESS>

And I see my own error in writing it out! It's regEx: SimpleSchema.RegEx.IPv4, that I'm missing, not type!


Terraform setup for db read replica

Problem
Setup terraform for DB read replica + Route53.
Add pg_cron job to refresh the new mat view.

In progress on mainnet. Still needs pg_cron.

https://github.com/connext/monorepo/pull/4199 PR completed.


'DPN' object has no attribute 'input_space'  Cifar10 example

When setting the pre_trained_model to False, running 'dpns' gave the error 'DPN' object has no attribute 'input_space'  in Cifar10 example. Except Resntes, all models gave this error. Using the attribute input_size=(32, 32)  in make_model resolved the issue. [32x32] is the cifar10 resolution for each band.
model = make_model(
    args.model_name,
    pretrained=True,
    num_classes=len(classes),
    dropout_p=args.dropout_p,
    input_size=(32, 32)
)

However, this 'input_size' gave the error: ResNet' object has no attribute 'features'
for all the Resnets. Thus, an if statement may be used to make-the-model.
NB. For VGG* and squeezenet*, we need to provide the input-size in any case, Exception: You must provide input_size, e.g. make_model(vgg11, num_classes=10, pretrained=True, input_size=(224, 224)

First exception ('DPN' object has no attribute 'input_space') should be fixed in
b690d27. The exception occurred because only pre-trained models contain attributes such as input_space or input_shape, but the library tried to read those attributes even when pretrained was set to False.

The second exception should be fixed in e7dc01f. I have changed the function that calculates the number of input features for the classifier, now it should work correctly for all models.

I think there is still an issue with the code,
File "/anaconda3/lib/python3.6/site-packages/cnn_finetune/base.py", line 160, in calculate_classifier_in_features
with no_grad_variable(torch.zeros(1, 3, *self.input_size)) as input_var:
TypeError: zeros() argument after * must be an iterable, not NoneType

Can you give an example of code that produces this exception?
Calls to make_model like model = make_model('dpn68', pretrained=False, num_classes=10, dropout_p=0.5, input_size=(32, 32)) and model = make_model('dpn68', pretrained=False, num_classes=10, dropout_p=0.5) work for me without any errors.

Strangely, it is working now without problems.