Broken source maps for bundles with packages from node_modules

Describe the bug
I have a workspace with two packages:

pkg-a build a bundle of its own code and packages from node_modules
pkg-b runs test from vitest that import code from pkg-a

The sourcemaps for errors thrown from inside pkg-a report incorrect source locations:
$ pnpm vitest

Error: Test error
 ❯ Module.foo ../node_modules/.pnpm/base32-decode@1.0.0/node_modules/base32-decode/index.js:5:9
 ❯ index.test.js:5:3

Running similar code in node JS produces the correct stack trace:
$ node --enable-source-maps script.js
/Users/dmaretskyi/vitest-sourcemap-bug/pkg-a/index.js:5
  throw new Error("Test error");
        ^

Error: Test error
    at foo (/Users/dmaretskyi/vitest-sourcemap-bug/pkg-a/index.js:5:9)
    at file:///Users/dmaretskyi/vitest-sourcemap-bug/pkg-b/script.js:3:1
    at ModuleJob.run (node:internal/modules/esm/module_job:217:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async loadESM (node:internal/process/esm_loader:34:7)
    at async handleMainPromise (node:internal/modules/run_main:66:12)

Reproduction
https://github.com/dmaretskyi/vitest-sourcemap-bug
See README for repro steps
System Info
System:
    OS: macOS 14.0
    CPU: (10) arm64 Apple M1 Pro
    Memory: 78.80 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.9.0 - ~/.nodenv/versions/20.9.0/bin/node
    Yarn: 1.22.21 - ~/.nodenv/versions/20.9.0/bin/yarn
    npm: 10.2.4 - ~/.nodenv/versions/20.9.0/bin/npm
    pnpm: 8.11.0 - ~/.nodenv/versions/20.9.0/bin/pnpm
    bun: 1.0.25 - ~/.bun/bin/bun
  Browsers:
    Chrome: 128.0.6613.138
    Safari: 17.0
  npmPackages:
    vitest: ^2.1.1 => 2.1.1

Used Package Manager
pnpm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[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 open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

For the bug to trigger it seems to be essential to have a package from node_modules in the bundle. Just bundling two local source files together does not repro the bug

I've started debugging this...
It seems like the source file paths get corrupted when the source map is loaded

After doing a dump with VITE_NODE_DEBUG_DUMP=1 it seems like those modules have broken source maps

I've traced it down to vite's source map combining code. The actual source positions are correct, but something corrupts the source paths

This looks similar to https://github.com/vitest-dev/vitest/issues/5523. Workaround is to prevent Vitest/Vite from processing already bundled pkg-a and you can do that by configuring test.server.deps.external. I don't think Vite currently has a way to read existing dist.js.map and remapping during own transform.
export default defineConfig({
  test: {
    server: {
      deps: {
        external: [/pkg-a/],
      }
    }
  }
})

Looks like bug in Vite. map.sources are incorrect when file is SSR transformed.
Error: Test error
 ❯ Module.foo ../node_modules/.pnpm/base32-decode@1.0.0/node_modules/base32-decode/index.js:5:9
                                                                                ^^^ This is pkg-a/index.js, not contents of base32-decode

I renamed pkg-a/index.js to pkg-a/pkg-a-entrypoint.js here to make it unique from index.js.
When we request the pkg-a here, we get following. Notice the "...base32-decode/pkg-a-entrypoint.js" part:
https://github.com/vitest-dev/vitest/blob/2a50464d58e98f58fed513971a570a952081bfef/packages/vite-node/src/server.ts#L411
console.log(result.map.sources);
> {
>   "sources": [
>     "../node_modules/.pnpm/base32-decode<EMAIL_ADDRESS>><EMAIL_ADDRESS>>   ],
>   ...
> }

Minimal repro without Vitest:
import { createServer } from "vite";

const server = await createServer();
await server.listen();

const ssrResult = await server.transformRequest(
  "/Users/x/vitest-sourcemap-bug/pkg-a/dist.js",
  { ssr: true }
);
console.log(ssrResult.map);
/*
  sources: [
    '../node_modules/.pnpm/base32-decode<EMAIL_ADDRESS><EMAIL_ADDRESS>  ],
  file: '/Users/x/vitest-sourcemap-bug/pkg-a/dist.js'
*/

// Without SSR:
const webResult = await server.transformRequest(
  "/Users/x/vitest-sourcemap-bug/pkg-a/dist.js",
  { ssr: false }
);
console.log(webResult.map);
/*
  sources: [
<EMAIL_ADDRESS>    'pkg-a-entrypoint.js'
  ],
*/

server.close();

If I manually fix the path in vite-node we get proper stack trace in errror:
 FAIL  index.test.js > repro
Error: Test error
 ❯ Module.foo ../pkg-a/pkg-a-entrypoint.js:5:9
 ❯ index.test.js:5:3
      3|
      4| test("repro", () => {
      5|   foo();
       |   ^
      6| });
      7|

I just ran into this yesterday, and this bug is very timely!
Just a "me, too." Keep up the good work!

This should be fixed in Vite 6.beta-2 (not released yet).


Autosave

Autosave did not work for me.
I fix it by changing the code in line 1114.
line 1114:
filedir = filePath.split(basename)[0].split("/")[-2:-1][0] to filedir = filePath.split(basename)[0].split("\ \ ")[-2:-1][0]

Hi @eschacht ,
Thanks. I think it is OS file path separator issue. I will fix it

Fixed https://github.com/tzutalin/labelImg/commit/e13d154ad8b2217883cbedd085ffba00d8753f40


Port C Entire CI Recipes from CWR

Description
Since the Native CI is entirely in shell scripts, I have to port the existing job recipes here. Data source: https://github.com/hollowaykeanho/cwr
Expected Behavior
Template can initiate a C workspace immediately.
Current Behavior
To initiate C workspace, manual efforts are needed.
Associated Data Files
No response

Stuck?

Most complicated one... too many permutation to handle...


Generates not.finished file for complete downloads while run from an external application

Python version:  3.5.4
Bandcamp-dl version: 0.0.8.post6
Bancamp-dl options:  --debug --base-dir=/home/sernick/Temp
url: https://overwerk.bandcamp.com/album/conquer
options:
Describe the issue:
I've made a little app in C++, and I'm calling the bandcamp-dl via system() command and it crashes. Same command from terminal runs fine.
URL:https://overwerk.bandcamp.com/album/conquerhttps://overwerk.bandcamp.com/album/conquer
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): overwerk.bandcamp.com
DEBUG:urllib3.connectionpool:https://overwerk.bandcamp.com:443 "GET/album/conquerhttps://overwerk.bandcamp.com/album/conquer HTTP/1.1" 404 None
DEBUG:root: Generating BandcampJSON..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
Traceback (most recent call last):
File "/usr/local/bin/bandcamp-dl", line 11, in
sys.exit(main())
File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/main.py", line 91, in main
album = bandcamp.parse(url, True, arguments['--embed-lyrics'], arguments['--debug'])
File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcamp.py", line 40, in parse
bandcamp_json = BandcampJSON(self.soup, debugging).generate()
File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcampjson.py", line 25, in generate
self.js_to_json()
File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcampjson.py", line 50, in js_to_json
self.get_js()
File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcampjson.py", line 37, in get_js
self.js_data = self.body.find("script", {"src": False}, text=re.compile(self.target)).string
AttributeError: 'NoneType' object has no attribute 'string'

Looking at your debug log it seems like you are mashing two copies of the URL together though?

Yeah, the problem looks like a doubled URL. The problem is that I launch bandcamp-dl with correct syntax, that works in a terminal, but not via the system() command. It just looks like it doubles the URL by itself.
Another example:
bandcamp-dl --debug --base-dir='/home/sernick/Temp' https://scandroid.bandcamp.com/album/the-force-theme-single
DEBUG:root:
        URL: https://scandroid.bandcamp.com/album/the-force-theme-singlehttps://scandroid.bandcamp.com/album/the-force-theme-single
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): scandroid.bandcamp.com
DEBUG:urllib3.connectionpool:https://scandroid.bandcamp.com:443 "GET /album/the-force-theme-singlehttps://scandroid.bandcamp.com/album/the-force-theme-single HTTP/1.1" 404 None
DEBUG:root: Generating BandcampJSON..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
Traceback (most recent call last):
  File "/usr/local/bin/bandcamp-dl", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/__main__.py", line 91, in main
    album = bandcamp.parse(url, True, arguments['--embed-lyrics'], arguments['--debug'])
  File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcamp.py", line 40, in parse
 bandcamp_json = BandcampJSON(self.soup, debugging).generate()
  File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcampjson.py", line 25, in generate
    self.js_to_json()
  File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcampjson.py", line 50, in js_to_json
    self.get_js()
  File "/usr/local/lib/python3.5/dist-packages/bandcamp_dl/bandcampjson.py", line 37, in get_js
    self.js_data = self.body.find("script", {"src": False}, text=re.compile(self.target)).string
AttributeError: 'NoneType' object has no attribute 'string'

Ok, so apparently debug printing from the app was the reason for doubled URLs (I know it sounds stupid, but hey). After turning debug off I can download only one album, because the first download creates a 0.0.8-06.not.finished file (even though the download is successful) and all other next system() calls instead of downloading another url, just try to redownload the first one.
DEBUG:root:
	URL: https://scandroid.bandcamp.com/album/the-force-theme-single
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): scandroid.bandcamp.com
DEBUG:urllib3.connectionpool:https://scandroid.bandcamp.com:443 "GET /album/the-force-theme-single HTTP/1.1" 200 None
DEBUG:root: Generating BandcampJSON..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
DEBUG:root: BandcampJSON generated..
DEBUG:root: Generating Album..
DEBUG:root: Generating track metadata..
DEBUG:root: Track metadata generated..
DEBUG:root: Album generated..
DEBUG:root: Album data:
	{'date': '2017', 'tracks': [{'duration': 323.084, 'track': '1', 'url': 'http://popplers5.bandcamp.com/download/track?enc=mp3-128&fsig=6c52c44b7acfc7108679e2180bf35736&id=2601497724&stream=1&ts=1505026865.0', 'title': 'The Force Theme'}], 'label': 'FiXT', 'full': True, 'art': 'https://f4.bcbits.com/img/a1852508397_16.jpg', 'artist': 'Scandroid', 'title': 'The Force Theme (Single)'}
DEBUG:root:Preparing download process..
DEBUG:root:Initiating download process..
DEBUG:root: Generating filepath/trackname..
DEBUG:root: filepath/trackname generated..
DEBUG:root:
	Path: /home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3
DEBUG:root: Directory:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single
DEBUG:root: Directory doesn't exist, creating..
DEBUG:root: Current file:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3.tmp
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): f4.bcbits.com
DEBUG:urllib3.connectionpool:https://f4.bcbits.com:443 "GET /img/a1852508397_16.jpg HTTP/1.1" 200 56240
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): popplers5.bandcamp.com
DEBUG:urllib3.connectionpool:http://popplers5.bandcamp.com:80 "GET /download/track?enc=mp3-128&fsig=6c52c44b7acfc7108679e2180bf35736&id=2601497724&stream=1&ts=1505026865.0 HTTP/1.1" 302 0
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): p4.bcbits.com
DEBUG:urllib3.connectionpool:http://p4.bcbits.com:80 "GET /download/track/4fec66f8f27a6b1647d411ca64115620/mp3-128/2601497724?fsig=7a50b7b192b2d7c2213754bb4f4c3231&id=2601497724&stream=1&ts=1505073600.0&token=1505073660_a5d31c3b01fc80a3cdd7eddb0cf13de9ff03418e HTTP/1.1"<PHONE_NUMBER>
DEBUG:root: Encoding process starting..
DEBUG:root: Encoding process finished..
DEBUG:root: Renaming:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3.tmp -to-> /home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3
DEBUG:root:
	URL: https://scandroid.bandcamp.com/album/the-force-theme-single
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): scandroid.bandcamp.com
DEBUG:urllib3.connectionpool:https://scandroid.bandcamp.com:443 "GET /album/the-force-theme-single HTTP/1.1" 200 None
DEBUG:root: Generating BandcampJSON..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
DEBUG:root: BandcampJSON generated..
DEBUG:root: Generating Album..
DEBUG:root: Generating track metadata..
DEBUG:root: Track metadata generated..
DEBUG:root: Album generated..
DEBUG:root: Album data:
	{'tracks': [{'duration': 323.084, 'track': '1', 'title': 'The Force Theme', 'url': 'http://popplers5.bandcamp.com/download/track?enc=mp3-128&fsig=6c52c44b7acfc7108679e2180bf35736&id=2601497724&stream=1&ts=1505026865.0'}], 'artist': 'Scandroid', 'label': 'FiXT', 'title': 'The Force Theme (Single)', 'full': True, 'date': '2017', 'art': 'https://f4.bcbits.com/img/a1852508397_16.jpg'}
DEBUG:root:Preparing download process..
DEBUG:root:Initiating download process..
DEBUG:root: Generating filepath/trackname..
DEBUG:root: filepath/trackname generated..
DEBUG:root:
	Path: /home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3
DEBUG:root: Directory:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single
DEBUG:root: Directory doesn't exist, creating..
DEBUG:root: Current file:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3.tmp
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): popplers5.bandcamp.com
DEBUG:urllib3.connectionpool:http://popplers5.bandcamp.com:80 "GET /download/track?enc=mp3-128&fsig=6c52c44b7acfc7108679e2180bf35736&id=2601497724&stream=1&ts=1505026865.0 HTTP/1.1" 302 0
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): p4.bcbits.com
DEBUG:urllib3.connectionpool:http://p4.bcbits.com:80 "GET /download/track/4fec66f8f27a6b1647d411ca64115620/mp3-128/2601497724?fsig=7a50b7b192b2d7c2213754bb4f4c3231&id=2601497724&stream=1&ts=1505073600.0&token=1505073660_a5d31c3b01fc80a3cdd7eddb0cf13de9ff03418e HTTP/1.1"<PHONE_NUMBER>
File: 01 - the-force-theme.mp3 already exists and is complete, skipping..

As for the not.finished file not being deleted that has actually been fixed since 0.0.8-06 by @Nzen I simply had not pushed a new release since.. my bad, I'll do that now.

Thanks for the update! Unfortunately, now things got even weirder. The 0.0.8-07 file is generated after the first download, and during the second download it disappears for a moment only to appear again, but this time with the second url appended to the urlstring.
{'--album': None, '--artist': None, '--base-dir': '/home/sernick/Temp/Downloads', '--debug': True, '--embed-art': False, '--embed-lyrics': False, '--full-album': False, '--group': False, '--help': False, '--no-art': False, '--no-slugify': False, '--overwrite': False, '--template': '%{artist}/%{album}/%{track} - %{title}', '--track': None, '--version': False, 'URL': 'https://scandroid.bandcamp.com/album/the-force-theme-singlehttps://scandroid.bandcamp.com/album/a-thousand-years-single'}

Strange I just updated and grabbed both of those just fine (even running the commands back to back very quickly in the same directory)
Id be interested in seeing exactly how you are calling bandcamp-dl in your code.

If your codes purpose is for downloading in batches keep in mind that Bandcamp limits connections, so downloading more at once only slows down each individual download (Unless you support proxies)
Otherwise if you are just writing an app to make downloading multiple tracks/albums more convenient I could always make passing multiple urls work, docopt supports such things natively so I doubt it would take much work.

I'm actually making a simple gui as a programming exercise . All it does is collect urls from user, and then (in a loop) cycles through them all, and in each cycle it calls bandcamp-dl with a few options and one url (Link) . But multiple url support would be pretty helpful in this case.

For now here is a version that will ignore the not.finished file if a url is provided:
bandcamp_downloader-0.0.8.post8.dev0-py3-none-any.zip
Just extract that and pip install the resulting .whl file.
Keep in mind https://scandroid.bandcamp.com/album/a-thousand-years-single no longer exists so that is a guaranteed failure if you try to download it.

@8sync Any update on this?

Sorry for a delayed response. So the new stable and dev builds behave same as before, and the modified build (thanks for the special version btw) fails altogether (even when downloading only one album).
Log from the modified version:
DEBUG:root:
	URL: https://scandroid.bandcamp.com/album/the-force-theme-single
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): scandroid.bandcamp.com
DEBUG:urllib3.connectionpool:https://scandroid.bandcamp.com:443 "GET /album/the-force-theme-single HTTP/1.1" 200 None
DEBUG:root: Generating BandcampJSON..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
DEBUG:root: Grabbing target data..
DEBUG:root: Converting JS to JSON..
DEBUG:root: Grabbing embedded script..
DEBUG:root: BandcampJSON generated..
DEBUG:root: Generating Album..
DEBUG:root: Generating track metadata..
DEBUG:root: Track metadata generated..
DEBUG:root: Album generated..
DEBUG:root: Album data:
	{'date': '2017', 'artist': 'Scandroid', 'title': 'The Force Theme (Single)', 'art': 'https://f4.bcbits.com/img/a1852508397_16.jpg', 'tracks': [{'url': 'http:https://t4.bcbits.com/stream/232027152f787d1c6abfe69de755cdc7/mp3-128/2601497724?p=0&ts=1506694880&t=69782ba1ec31d0ee3bee6933b2dfcac73faefa66&token=1506694880_cccef40571176c31a65e03e7520e62a924c7bfcf', 'title': 'The Force Theme', 'duration': 323.084, 'track': '1'}], 'label': 'FiXT', 'full': True}
DEBUG:root:Preparing download process..
DEBUG:root:Initiating download process..
DEBUG:root: Generating filepath/trackname..
DEBUG:root: filepath/trackname generated..
DEBUG:root:
	Path: /home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3
DEBUG:root: Directory:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single
DEBUG:root: Directory doesn't exist, creating..
DEBUG:root: Current file:
	/home/sernick/Temp/Downloads/scandroid/the-force-theme-single/01 - the-force-theme.mp3.tmp
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): f4.bcbits.com
DEBUG:urllib3.connectionpool:https://f4.bcbits.com:443 "GET /img/a1852508397_16.jpg HTTP/1.1" 200 56240
No connection adapters were found for 'http:https://t4.bcbits.com/stream/232027152f787d1c6abfe69de755cdc7/mp3-128/2601497724?p=0&ts=1506694880&t=69782ba1ec31d0ee3bee6933b2dfcac73faefa66&token=1506694880_cccef40571176c31a65e03e7520e62a924c7bfcf'
Downloading failed..

Yeah an issue was reported after I built that version which pointed me towards a change Bandcamp made which results in that error (They now include the protocol in the url, it used to just be //t4bcbits/com/etc etc) Its fixed in the latest.
I can't figure out why calling bandcamp-dl in a loop with individual urls would break, there is no logical reason for it especially considering this is not the first time it has been used externally like this.
I looked at the code and didn't notice anything that would be an issue either. Have you tried adding a print for the url variable and see if its actually doubling up before it gets to bandcamp-dl?

Have you tried adding a print for the url variable and see if its actually doubling up before it gets to bandcamp-dl?

Yeah, initially when starting this issue I had something like that in my code, and the urls were extracted from the text field just fine. And every time the loop starts a new cycle, you can see the command which is being executed and imo they look perfectly fine, and when entered manually into a terminal, they also work perfectly fine.

I can't figure out why calling bandcamp-dl in a loop with individual urls would break, there is no logical reason for it especially considering this is not the first time it has been used externally like this.

Exactly.


Is this unstable?

Hey!
The current version of this project is 0.0.7. Is it actually in development, or is it done?
If it's done, it should be on 1.x as per semver.org

I don't think this project has large enough adoption to tell whether it is really stable. Also, it is not as actively maintained as some other projects. So, I'd rather keep it on 0.x

We were using it on https://www.lostmy.name/ for quite a long time to generate our responsive images. We're now calling gm directly because we wanted to access a property on the vinyl file object and it wasn't possible when using gulp-gm, but when we used this plugin, we never had any problems with it :)


Download manifest view

This PR adds a view for the downloadable samples.

Sorry to jump in here. About the design:
please only add one button at the top of the table, as drafted in the wireframe. What does generate do?
It suffices to just have one button which is activated for the selection of the project

Sorry to jump in here. About the design:
please only add one button at the top of the table, as drafted in the wireframe. What does generate do?
It suffices to just have one button which is activated for the selection of the project

What does that button do then? I thought the whole point was to download data available for a specific project?


How to set the cell format ?

cell format as example:

How to set the cell format to the text ?

You can set cell A1 as text by number format like this:
var style int
if style, err = f.NewStyle(&excelize.Style{NumFmt: 49}); err != nil {
    fmt.Println(err)
    return
}
if err = f.SetCellStyle("Sheet1", "A1", "A1", style); err != nil {
    fmt.Println(err)
    return
}

How about to set the format to Numberic? What would be the numFmt value? I cannot find the doc on this from anywhere

Sorry for my late reply, you can find more built-in number format mapping details in the documentation.


Crash when I run HazelInput or Sandbox using VS2017.

Crash when I run HazelInput or Sandbox using VS2017.
More infomations.

Any help will be greatly appreciated.

I can't read Chinese but it's probably the same problem as #133 judging by the 0x00 addresses.
What's the output from the console?


Stepper Circle Margin

Use case
Widget _buildCircle(int index, bool oldState) {
return Container(
margin: const EdgeInsets.symmetric(vertical: 8.0),
width: _kStepSize,
height: _kStepSize,
child: AnimatedContainer(
curve: Curves.fastOutSlowIn,
duration: kThemeAnimationDuration,
decoration: BoxDecoration(
color: _circleColor(index),
shape: BoxShape.circle,
),
child: Center(
child: _buildCircleChild(index, oldState && widget.steps[index].state == StepState.error),
),
),
);
}
this is the code for building the circle of the stepper the margin is const. It should be dynamic to change by the developer.
also the size of the circle of the step we need to change it size to match our designs.
const double _kStepSize = 24.0;
Proposal
we need to pass it form the step or stepper
also we need to make every step open feature to be not only one step opened

I have the same problem with this widget in old project and I replaced it with a package.
thank you for opening this issue

the same with me

thanks for opening this issue.

@amramer522  Please provide minimum code sample to produce the issue

I provide it in the use case this the code in the stepper widget

Hi everyone,

also the size of the circle of the step we need to change it size to match our designs.
const double _kStepSize = 24.0;

This is a known issue being tracked at https://github.com/flutter/flutter/issues/103124 so please follow up on it for further updates.
Labeling this issue as a separated proposal for Customizable circle margin.


Fix 4.12 nightly rebase

go-bindata is no longer used by openshift/kubernetes, it's planned to be changed with go:embed in future

/lgtm

/lgtm


fix android wrong multi-touch pointerid

Fix #43519
I have the same issue, and this PR fixed it.
I think the ActionIndex may be changing in the godotView.queueEvent.

Looks correct to me, though I don't understand why it was like that before (https://github.com/godotengine/godot/pull/42360/files you can see here that I only changed semantic and didn't change functionality of that function, so I can't guess why it wasn't brought out before)

Can you provide a similar fix for the master branch.

Did it myself with #44067.

Looks good! Can you provide a similar fix for the master branch.
cc @thebestnom

Sorry for that,  I thought you  requested thebestnom to do that fix for master branch.

Thanks! And congrats for your first merged Godot contribution :tada:


What cause starting nginx controll failure?

I build ingress nginx controller and fail to start it. env: kubernetes 1.3.2, docker 1.11.2. CentOS 7.2.1
The output of kubectl describe is:
7m    7m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Created         Created container with docker id e1d3670bad8c
7m    7m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Started         Started container with docker id e1d3670bad8c
7m    7m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Killing         Killing container with docker id e1d3670bad8c: pod "nginx-ingress-controller-du1gp_default(ac3b025c-75a8-11e6-9cd1-00505697649c)" container "nginx-ingress-lb" is unhealthy, it will be killed and re-created.
2m    2m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Created         Created container with docker id 6e71d8c77211
2m    2m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Started         Started container with docker id 6e71d8c77211
1m    1m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Started         (events with common reason combined)
1m    1m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Created         (events with common reason combined)
17m   1m      10      {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Pulled          Container image "nginx-ingress:0.8.3" already present on machine
1m    1m      1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Killing         Killing container with docker id 6e71d8c77211: pod "nginx-ingress-controller-du1gp_default(ac3b025c-75a8-11e6-9cd1-00505697649c)" container "nginx-ingress-lb" is unhealthy, it will be killed and re-created.
16m   40s     12      {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Warning Unhealthy       Liveness probe failed: Get http://<IP_ADDRESS>:10249/healthz: dial tcp <IP_ADDRESS>:10249: getsockopt: connection refused
37s   37s     1       {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Normal  Killing         (events with common reason combined)
7m    8s      27      {kubelet <IP_ADDRESS>}                                          Warning FailedSync      Error syncing pod, skipping: failed to "StartContainer" for "nginx-ingress-lb" with CrashLoopBackOff: "Back-off 5m0s restarting failed container=nginx-ingress-lb pod=nginx-ingress-controller-du1gp_default(ac3b025c-75a8-11e6-9cd1-00505697649c)"
12m   8s      47      {kubelet <IP_ADDRESS>}  spec.containers{nginx-ingress-lb}       Warning BackOff Back-off restarting failed docker container
The output of kubectl logs is:
2016/09/08 09:52:38 [debug] 22#22: epoll add event: fd:16 op:1 ev:00002001
2016/09/08 09:52:38 [debug] 23#23: epoll add event: fd:17 op:1 ev:00002001
2016/09/08 09:52:38 [debug] 24#24: epoll add event: fd:18 op:1 ev:00002001
2016/09/08 09:52:38 [debug] 22#22: epoll add event: fd:14 op:1 ev:00002001
2016/09/08 09:52:38 [debug] 22#22: epoll add event: fd:15 op:1 ev:00002001
2016/09/08 09:52:38 [debug] 22#22: epoll add event: fd:20 op:1 ev:00002001
2016/09/08 09:52:38 [debug] 25#25: epoll add event: fd:19 op:1 ev:00002001
2016/09/08 09:52:47 [debug] 24#24: epoll add event: fd:14 op:1 ev:00002001
2016/09/08 09:52:47 [debug] 22#22: epoll del event: fd:14 op:2 ev:00000000

How is your deployment file?
Which version are you building?
Logs saying that kubernetes is killing the pod due to liveness probe failure, so probably the initialDelaySeconds of livenessProbe is too small or the /healthz is really down for too much time!

@tjliupeng please update the healthz port to 10254

Hi @tjliupeng, I have the same problem, and i wanner how can i determine the right port, because the early version of nginx-ingress-controller, the health port is 10249.

@aledbf , why should I update the port to 10254? In nginx-ingress.yaml, the livenessProbe setting is:
name: nginx-ingress-lb

        livenessProbe:
          httpGet:
            path: /healthz
            port: 10249
            scheme: HTTP
          initialDelaySeconds: 30
          timeoutSeconds: 5

Oh, I just check the code, in main.go:
healthPort = 10254


Xarray import

Execute data import and concatenation with xarray.

Looks good in general. A few fixes to be made:

Zohar data is not aligned correctly, please double check
Alter data should include functional dataset, but I'll let you start a new pull request to fix that
Chung 2021: you should include "Pan IgG" and make it a separate kind of receptor
I suggest that in the test function, for each dataset, you should include at least two entries that you look up and certify by hand, preferably different sample/receptor/antigen/day. For example, in Kaplonek MGH, you can add

assert np.isclose(MGH4D().loc["C4-014", "CMV", "IgG1", "D3"], 2.88166991)

Everything else looks good. Let me know when these are fixed, and I'll take another look.


Remove changelog: labels in osparc-simcore

AFAIK the pink changelog:-prefixed labels for release changelogs were not as useful as expected.
Right now we have a combination of old/new labels and it is not clear to me which/how to use them.

I think is time to review the purpose of these tags and cleanup (e.g. start with changelog: ones if there is no need for them).
Some interesting strategies are presented in https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63
SEE https://github.com/ITISFoundation/osparc-simcore/labels

done


Added Morpheus to new MVVM category

Swift library for functional and reactive MVVM
Project URL
https://github.com/mpurland/Morpheus
Description
Added Morpheus to new MVVM category
Checklist

[x] Only one project is in the request
[x] Addition in chronological order (bottom of category)
[x] Travis CI pass
[ ] Supports iOS 7 and later
[ ] Has a commit from less than 2 years ago
[x] Has a clear README in English

Hmm. Not sure about this, given the this is very alpha warning on both this and #810.
@dkhamsing, @lfarah, @vsouza what you think?

Right, let's have @mpurland resubmit when it is more stable
Also the README could be improved

Agreed. A good push to add documentation and remove the alpha flags now that the api is relatively stable. Thanks!

On May 7, 2016, at 7:03 PM, dkhamsing<EMAIL_ADDRESS>wrote:
Right, let's have @mpurland resubmit when it is more stable
Also the README could be improved
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub


Revert "Read API Source v2 (#25392)"

Fixes #26354
This reverts commit 4ce8eeda19699cc64ae8cf310267a478cfe9e4b8.
setEnableBundling is defunct since added to Beam repo and opt-in it will result in data loss, see #26354. After #26267 the number of sources returned by split is no longer an issue and BigQueryStorageStreamBundleSource is not needed after all.
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

The only conflict is on the removal of Experimental annotation on master, giving this diff (+105 −2,863) different from original PR (+2,867 −105)

R: @ahmedabu98

IIRC the setEnableBundling option was implemented to resolve RPC latency issues (design doc here)
@vachan-shetty is this mode no longer needed?

Added --enableStorageReadApiV2 pipeline option to replace --enableBundling, tested on both runner v1 and v2:
it gives "Read session returned 1954 streams", and all records are read. See the internal gcp project
@vachan-shetty PTAL

@Abacn @vachan-shetty what are next steps here?

👍🏽

R: @ahmedabu98  rebased onto latest master to resolve merge conflict. PTAL

Can we update CHANGES.md to explain this breaking changes?

Can we update CHANGES.md to explain this breaking changes?

I thought it is fine to remove it without mention it as last time the addition of --enableBundling wasn't mentioned in CHANGES.md either, and it's not been used. However indeed we should note "setEnableStorageReadApiV2" is experimental and could update CHANGES, will do.

SpannerChangeStreamOrderedWithinKeyIT.testOrderedWithinKey unrelated flaky test, merging for now


Automatically skip auth if ctx is not set.

Why do we need this?  I mean, if we want to skip auth programmatically, we already have the way: https://oss.platformatic.dev/docs/reference/db/authorization/introduction#programmatically-skip-authorization-rules

I would make skipAuth true by default for all plugin requests.

I would make skipAuth true by default for all plugin requests.

This is essentially what this would do.


fix: incorrectly calculates next semantic version with large commit bodies containing possible keywords

closes #359

Codecov Report

Merging #371 (d51a1ff) into main (309fd5c) will decrease coverage by 0.28%.
The diff coverage is 73.91%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #371      +/-   ##
==========================================
- Coverage   80.69%   80.42%   -0.28%
==========================================
  Files          40       40
  Lines        1865     1900      +35
==========================================
+ Hits         1505     1528      +23
- Misses        268      277       +9
- Partials       92       95       +3

Files Changed
Coverage Δ

internal/semver/parser.go
73.91% <73.33%> (-26.09%)
:arrow_down:

internal/task/nextsemver/nextsemver.go
88.34% <100.00%> (ø)


Include CSS from node_modules

I am trying to include a CSS file from node_modules, specifically at:

semantic-ui-css/semantic.min.css

How would you properly import this? Currently, I am adding
@import "~semantic-ui-css/semantic.min.css";
to the top of styles.scss. It starts normally, but gives the error below when the page is loaded.

Unknown error from PostCSS plugin. Your current PostCSS version is 6.0.12, but postcss-partial-import uses 5.2.17. Perhaps this is the source of the error below.
ERROR in ./node_modules/css-loader?{"modules":true,"localIdentName":"[local]","sourceMap":true,"minimize":false,"importLoaders":2}!./node_modules/postcss-loader/lib?{"sourceMap":true}!./node_modules/sass-loader/lib/loader.js?{"outputStyle":"expanded","sourceMap":true,"sourceMapContents":true}!./src/resources/css/style.scss
Module build failed: Error: Failed to find '~semantic-ui-css/semantic.min.css'
in [
/home/coldwhistle/dev/react-pwa/src/resources/css
]
at /home/coldwhistle/dev/react-pwa/node_modules/postcss-import/lib/resolve-id.js:48:11
at
@ ./src/resources/css/style.scss 4:14-209 18:2-22:4 19:20-215

@mrtysn I would copy the css file to libs in "src/resources/css/libs/semantic.min.css" all files in resources are imported via loaders and without modification of name i.e. localIdentName=[local] thus not changing its implementation. Then you can directly use the css classes in the application.
However I would recommend not to do that and use the css in component isolated whenever possible. This reduces the size of common style and loads the css in required module only.

Thank you for the answer. I am using Semantic as a global framework, therefore I need it in almost every component. As explained here, the CSS is distributed via their CDN or an npm package. So, copy-pasting would mean regularly checking if they released a new version or not. Since that is not an optimal way of doing it, I would very much prefer if I could directly import it the same way I did it in create-react-app previously, that is:
import 'semantic-ui-css/semantic.min.css';
in index.js.
The problem is, this CSS file also contains ttf,woff,woff2 thus css-loader fails to load it. Any solutions for such use cases? I believe many people are using a global UI framework and including its CSS so this is a common problem for this react-pwa project.

@mrtysn Yes I can think we can specify that using anything from node_modules should be treated same as we do with src/resources/libs, That should solve the problem.  If that works for you, I shall add it to master branch and next release.
Does that work ?

Of course, that would be great! We really like the project so far, thank you for the work.
If we can smoothly migrate our existing project and solve the further problems that have not occurred yet, we are considering to drop create-react-app in favor of react-pwa.  We would also be happy to back the project if you'd help us solve such performance issues.
I am keeping this issue open for now, until it is resolved.

I know Stack Overflow has become quite the troll farm these days. Perhaps there's room for a free Discord server as this repo gains mindshare and popularity, to help keep the repo clean of help requests.

@mrtysn I have pushed the changes to master and tested it with Semantic-UI-CSS with simple
import 'semantic-ui-css/semantic.min.css';
if you want it globally then use the import in src/client.js, that will include the semantic css in common bundle. thus you can use it whole application.

@mrtysn Ok. The build is yarn test - ed. Let me know if this solves the problem of css include from node_modules.
@jhabdas I updated this cause many would like to use 3rd party plugins and css via node_modules and totally made sense.

@tirthbodawala Hi Tirth, importing css still gives error:

ERROR in ../node_modules/semantic-ui-css/semantic.min.css
Module build failed: ModuleNotFoundError: Module not found: Error: Can't resolve 'themes/default/assets/fonts/icons.eot' in '/home/coldwhistle/dev/react-pwa/node_modules/semantic-ui-css'

Can you provide a working example?

@mrtysn how are you importing it? in css? or in client.js?

I am working with the latest commit in the master branch.

I've installed semantic-ui-css & semantic-ui-react" as devDependencies.
Added import "semantic-ui-css/semantic.min.css";  to src/client.js
Both yarn start and yarn build fails

I did the same, and was working well. I have droped you an email regarding skype chat or any screenshare. Let me know if that is possible.

For anyone who are still facing the issue, please do not include minified version of css from node_modules,
In this case do not include "semantic.min.css" but use "semantic.css"
There are path resolution issues with menified css.

@tirthbodawala has this issue been resolved? currently hitting it right now, was there ever a workaround created?

@EvanBurbidge We are launching react-pwa v2 that would solve the issue. please stay with us a bit longer. It is a very big change.


Display the list of commands in a tabular form to aid readability

It would be nice to display the results of ^tag command in a tabular form
eg.
All available tags:
 ++                  busychannel  gsdp                 javafxpom  naming     premade                   srp         unsupported
 abstract            debug        intellij             js         nio        projects                  stacktrace  uri
 ad                  debugger     interface            lsp        oracle     question                  static      visbility-chart
 android-getstarted  docker       interface-abstract2  mcve       ossu       regex                     student     w3
 arch                framework    interrupt            method     parseLine  scanner                   syntax      xy
 ask                 gist         javadoc              mockdata   person     share                     this
 bnf                 git          javafx-swing         mooc       ping       spring-password-handling  typeparam

but what I am not sure is what if all users don't have a wide enough device to accommodate the width of the table. So this one is debatable

Upon trying this on my phone, both landscape and portrait modes are hard to properly read.
Based on this, 2 or 3 may be a better option than 8.

With 3, this looks relatively manageable on portrait mode.


API tables not aligning vertically

The two tables should align vertically. Basically based on the screen size. Not sure why we have this issue in the first place. Scanpy and Squidpy don't have it.

/*Set max width to none so the theme uses all available width*/
.wy-nav-content {
    max-width: none;
}

Apparently this is the issue.

td:nth-child(1) {
    width: 100%;
}
td:nth-child(2) {
    width: 100%;
}

best I could do. TBH I don't really understand the CSS here.


(packaging) Bump version to 4.9.4

This updates Puppet's version to 4.9.4 in preparation for the 1.9.3
release of puppet-agent.

👍


Position argument seemingly not picked up

Hey,
I'm currently using spray-swagger and encountering the following issue:
I have three @Api each containing a position argument.
Each of these api contains multiple @ApiOperation containing a position argument as well.
The problem is that those position arguments do not seem to be picked up by spray-swagger. Indeed, the @Api and @ApiOperation seem to be ordered alphabetically.
Any ideas why?

I am also seeing this issue. Any updates?


[DOCFIX] Updating Chinese Doc

Make it more native in docs/cn/Clients-Go.md by replacing some words with more native ones

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/818/
Test PASSed.


Deprecation warning not needed for Ruby 1.9.2

Redis is giving me an unnecessary deprecation warning when firing up a Rails server. I get:
WARNING: using the built-in Timeout class which is known to have issues when used for opening connections. Install the SystemTimer gem if you want to make sure the Redis client will not hang.
I'm on 1.9.2 so it's unnecessary.

Which version of the gem are you using? Using the latest version on 1.9 shouldn't display a warning.
See: https://github.com/ezmobius/redis-rb/blob/be3d7e0b4194fcb7e91bee9153daf6073dbc1268/lib/redis/connection/ruby.rb#L111-130


'module' object is not callable

In English, please.

In English, please.

In English, please.

Sorry for the late response, bro, I've been negligent.
First of all, congratulations on your outstanding achievements in this work and I'd like to ask for your advice.
I used and activated the conda create command to create a python 3.8 environment，Finally, follow your steps to install setup.py. Next, I started to train the model.The following error occurred：
(laneatt) root@ubuntu:/mnt/zdm/LaneATT-main# python main.py train --exp_name zdmr34 --cfg cfgs/laneatt_culane_resnet34.yml
[2021-02-01 08:56:49,254] [lib.datasets.culane] [INFO] Loading CULane annotations (cached)...
[2021-02-01 08:56:58,711] [lib.datasets.culane] [INFO] 88880 annotations loaded, with a maximum of 4 lanes in an image.
[2021-02-01 08:56:58,712] [lib.datasets.lane_dataset] [INFO] Transforming annotations to the model's target format...
[2021-02-01 08:58:19,387] [lib.datasets.lane_dataset] [INFO] Done.
0%|                                                                                | 0/15 [00:01<?, ?it/s]
Traceback (most recent call last):
File "main.py", line 59, in
main()
File "main.py", line 52, in main
runner.train()
File "/mnt/zdm/LaneATT-main/lib/runner.py", line 51, in train
outputs = model(images, **self.cfg.get_train_parameters())
File "/home/crc/anaconda3/envs/laneatt/lib/python3.8/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/mnt/zdm/LaneATT-main/lib/models/laneatt.py", line 108, in forward
proposals_list = self.nms(reg_proposals, attention_matrix, nms_thres, nms_topk, conf_threshold)
File "/mnt/zdm/LaneATT-main/lib/models/laneatt.py", line 129, in nms
keep, num_to_keep, _ = nms(proposals, scores, overlap=nms_thres, top_k=nms_topk)
TypeError: 'module' object is not callable
0%|                                                                                | 0/11110 [00:03<?, ?it/s]
Segmentation fault
(laneatt) root@ubuntu:/mnt/zdm/LaneATT-main#
I'm at a loss about it. Can you answer this question? Thank you!

It might be the same problem as #15. Are you using PyTorch 1.6 with CUDA 10.2?

It might be the same problem as #15. Are you using PyTorch 1.6 with CUDA 10.2?

Thank you for your quick reply！I just checked it, and the results are as follows：

I seem to have used pytorch 1.6 with CUDA 10.2.Please check if there are any problems I didn't find.I look forward to your reply，bro~

Is the global installation of CUDA (the one in /usr/local/cuda) in version 10.2?

Is the global installation of CUDA (the one in /usr/local/cuda) in version 10.2?

Bro！Thanks for your patient reply. I find CUDA (the one in /usr/local/cuda) only has 10.0 and 10.1. I will download 10.2 under the path /usr/local/. and see if the problem can be solved.Thank you very very much!!!

Make sure that the NMS module is compiled with CUDA 10.2. Before compiling it with 10.2, clean any previous compilation  (i.e., rm build dist -rf inside the nms directory).

Make sure that the NMS module is compiled with CUDA 10.2. Before compiling it with 10.2, clean any previous compilation (i.e., rm build dist -rf inside the nms directory).

Thank you bro!! I will try!

Make sure that the NMS module is compiled with CUDA 10.2. Before compiling it with 10.2, clean any previous compilation (i.e., rm build dist -rf inside the nms directory).

I'm sorry to disturb you again，bro. I downloaded cuda10.2 and the results are as follows:

It seems to have used  CUDA (the one in /usr/local/cuda) in version 10.2. But there is still the original mistake.
Can you give me some advices? I would appreciate it!!

Sorry for the delay. I'm not sure. Did you make sure to clean any previous compilation?

Hello, I also encountered this error. My pytorch and CUDA versions are correct, and any previous compilation has been cleared, but there is still this error. Can you give me some suggestions? Thank you very much.

Did the NMS module compile correctly? You can also try using a Dockerfile.

NMS 模块是否正确编译？您也可以尝试使用Dockerfile。

OK, thank you for your reply，I'll try.

In English, please.

Sorry for the late response, bro, I've been negligent. First of all, congratulations on your outstanding achievements in this work and I'd like to ask for your advice.
I used and activated the conda create command to create a python 3.8 environment，Finally, follow your steps to install setup.py. Next, I started to train the model.The following error occurred：
(laneatt) root@ubuntu:/mnt/zdm/LaneATT-main# python main.py train --exp_name zdmr34 --cfg cfgs/laneatt_culane_resnet34.yml [2021-02-01 08:56:49,254] [lib.datasets.culane] [INFO] Loading CULane annotations (cached)... [2021-02-01 08:56:58,711] [lib.datasets.culane] [INFO] 88880 annotations loaded, with a maximum of 4 lanes in an image. [2021-02-01 08:56:58,712] [lib.datasets.lane_dataset] [INFO] Transforming annotations to the model's target format... [2021-02-01 08:58:19,387] [lib.datasets.lane_dataset] [INFO] Done. 0%| | 0/15 [00:01<?, ?it/s] Traceback (most recent call last): File "main.py", line 59, in main() File "main.py", line 52, in main runner.train() File "/mnt/zdm/LaneATT-main/lib/runner.py", line 51, in train outputs = model(images, **self.cfg.get_train_parameters()) File "/home/crc/anaconda3/envs/laneatt/lib/python3.8/site-packages/torch/nn/modules/module.py", line 722, in _call_impl result = self.forward(*input, **kwargs) File "/mnt/zdm/LaneATT-main/lib/models/laneatt.py", line 108, in forward proposals_list = self.nms(reg_proposals, attention_matrix, nms_thres, nms_topk, conf_threshold) File "/mnt/zdm/LaneATT-main/lib/models/laneatt.py", line 129, in nms keep, num_to_keep, _ = nms(proposals, scores, overlap=nms_thres, top_k=nms_topk) TypeError: 'module' object is not callable 0%| | 0/11110 [00:03<?, ?it/s] Segmentation fault (laneatt) root@ubuntu:/mnt/zdm/LaneATT-main#
I'm at a loss about it. Can you answer this question? Thank you!

How did you solve the problem

try this in lanatt.py
import sys
sys.path.append('lib/nms/dist/nms-0.0.0-py3.8-linux-x86_64.egg')
import nms
keep, num_to_keep, _ = nms.nms(proposals, scores, overlap=nms_thres, top_k=nms_topk)  #line129


Feature request: Display k8s namespace in addition to cluster in Github Deployments activity log and 'active deployment' boxes

The deployments overview in my Github repository has an activity log and above that two boxes for active deployments to the k8s clusters prod-fss and dev-fss. In my build & deploy pipeline I deploy the same version of my app twice to dev-fss - to two seperate k8s namespaces - and once to prod-fss (to the default namespace). This is because some people think that when deploying to production I need to first deploy to a verification environment, then to the production environment and then to a production-like environment. The view in Github does not display this. A solution would be to display the namespace name in addition to the cluster name in the activity log. The same goes for the boxes for active deployments, but I guess this implies that we will have more boxes: one for each combination of cluster and namespace.
The image shows that my one Travis CI build resulted in three deployments, out of which only two get the status "active". (See the commit hashes.) There should be three active deployments. Two of these deployments were to seperate k8s namespaces in the dev-fss cluster.

Sorry, but we have little control over the activity log feature. This is Github's user interface and Github doesn't really know which namespace we use, or that we use Kubernetes at all in any case. We don't have any way to report back "extra" fields.
The only way to solve this issue would be to create a dashboard solution ourselves. @christeredvartsen anything to add here?

Kunne vi ikke bare skrevet cluster:namespace i tittelen? I stedet for bare cluster?

@Kyrremann we don't have any control over the presentation layer here. At Github there is environment which here corresponds to the cluster in question.
Appreciate if you keep the discussion in English as well :)

Why don't we just write environment:namespace instead of just environment?

I https://github.com/navikt/circleci-nais-orb/issues/6 kjemper jeg stadig for at konseptet "miljø" (alias "environment") i Nais-kontekst skal være definert av kombinasjonen av clusternavn og namespacenavn. Dvs. at @Kyrremann sitt forslag ovenfor bør navngis "cluster:namespace".

I diskusjon på Slack https://nav-it.slack.com/archives/CL3G3HZ37/p1563957258013100 kom vi fram til at namespace ikke skal brukes til å simulere miljøer. Det er en endring i forhold til det jeg så for meg da jeg opprettet denne issuen. Men det som forblir det samme er at mitt prosjekt kommer til å ha behov for å deploye flere versjoner av en app til samme cluster (dev-fss). I følge @TheUnnamedDude https://nav-it.slack.com/archives/CL3G3HZ37/p1563969992030200?thread_ts=1563957258.013100&cid=CL3G3HZ37  kan det løses ved å deploye samme app men med ulike appnavn i nais.yaml fila. Det har jeg fremdeles samme problem som opphavet til denne issuen: Jeg har flere aktive deploys til samme cluster fra samme Github repo, men visningen av Github deploys vil bare vise én av dem som aktiv. Nytt forslag til løsning blir da å skrive environment:appname. For å ta høyde for alt kan man skrive environment:appname:namespace.

Closing this because we want people to use the default namespace, instead of spread their app out on different "miljø". Using different namespaces will also not be possible when a team moves over to the cloud/GCP, as every team gets their own namespace.


Login Failed: 'The words you typed didn't match the picture. Please try again.'

When I use rbx.login(username, password) I am getting the following error and cannot log in. I believe this may be related to a Roblox image CAPTCHA. I can't find any information on this error anywhere.
Unhandled rejection Error: Login failed, known issues: ["The words you typed didn't match the picture. Please try again."]
    at C:\Users\user\node_modules\roblox-js\lib\user\login.js:64:13
    at tryCatcher (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\promise.js:512:31)
    at Promise._settlePromise (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\promise.js:569:18)
    at Promise._settlePromise0 (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\promise.js:614:10)
    at Promise._settlePromises (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\promise.js:693:18)
    at Async._drainQueue (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\async.js:133:16)
    at Async._drainQueues (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\async.js:143:10)
    at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\user\node_modules\roblox-js\node_modules\bluebird\js\release\async.js:17:14)
    at processImmediate [as _immediateCallback] (timers.js:358:17)

Although this repo doesn't seem to be maintained anymore...

This is a result of the captcha. Use a jar/cookie to bypass this.

@EraGamer how would I do that?


Finish FieldValue migration to Protobuf

This is the last PR in everyone's favorite series. It addresses random issues and contains the changes that have not yet been reviewed.

Looks like ASAN party is over! Whee


Multiple vault types for a given collateral type

Context
See https://github.com/Agoric/agoric-sdk/issues/6518
Development Analysis
Components Expected to be Affected

vaultDirector

Implement feature code
We must implement a new method named addNewManager. This method;

makes sure the collateral type is already registered
initialParamValues are checked just like in addVaultType
creates its own storage node
returns its public facet

Solve how to handle paramManagers
Currently paramManagers are tracked for every collateral manager according to their collateral brand. Having multiple collateral managers for one collateral type will break this implementation. We must come up with a new way to track collateral managers. I suggest looking into durable handlers.

Testing Considerations

make sure the new vault manager can be added
make sure new vault types can be added so nothing's broken
make sure liquidations carried out correctly

every vault manager triggers liquidations according to its LR
proceeds distribution happens without any problems
A bug in one collateral manager does not prevent other collateral manager from being liquidated

Open Questions
Is it possible to have more than one retail vault manager?
In other words, for a given and already accepted collateral type, is it safe to assume that all incoming new vault managers will be of type institutional or can EC choose to create a new retail vault manager?
I believe the answer to this question is most likely "yes".  See https://github.com/anilhelvaci/agoric-sdk/issues/3
Can EC add new accounts to the whitelist for a particular vault manager?
Can EC remove accounts from the whitelist for a particular vault manager?
Regression Considerations
Changing the way we index vault managers would probably end up changing a lot of the existing tooling around vaultFactory.
Deliverables
All the iterations will come with their corresponding FE implementations.
Iteration One: Enable only institutional vault managers first

Focus on the feature only
Retail vault managers requires extensive change to whole agoric-sdk

Iteration Two: Enable retails vault managers

Example FE flow for iteration one
sequenceDiagram
    participant user as institutionalUser
    participant int as dapp-inter
    participant vs as vStorage
    participant vf as vaultFactory

    user ->> int: connect keplr
    int ->> vs: query = list of institutional managers and the white-list
    vs -->> int: [manager0, manager1]
    Note over int, int: find which managers the user is whitelisted
    int ->> int: display retail AND institutional managers
    int ->> int: display all vaults belonging to the user
    int -->> user: page loaded
    user ->> int: Click "open vault" for institutional manager
    int ->> int: calculate prevOfferId
    Note over int,int: Inst users can send offers using continuing invitations
    Note over int,int: e.g {address}-manager-{managerIndex}-{?iteration}
    int ->> vf: Send vault offer
    Note over int, vf: offer = {invitationSpec = {source = continuing, prevOfferId, makeVaultInvitation}}
    vf -->> int: success

New Approach to Retail VMs
After giving some deeper thoughts, it is clear that we need identifiers for both retails and institutional VMs. Which leads me to think that we can leverage these identifiers to store our VMs. Below is a high level illustration of how I think we can store the ever increasing VMs.
flowchart LR
    A(EC) --> |Add new VM| D(VaultDirector)
    D(VaultDirector) --> C{Retail or Institutional}
    C -->|Retail| F(Retail VMs Store)
    --> |collateralBrand| E(Get VM store for a Col Type)
    --> |VM identifier| K(Init new retail VM)
    C -->|Institutional| G(Institutional VM store)
    --> |collateralBrand| N(Get VM store for a Col Type)
    --> |VM identifier| L(Init new retail VM)

However, before we come to any conclusion we must answer more questions. Preferably with diagrams. Here are some of those questions.
How is EC going to update parameters for retail and institutional VMs?
[WIP]
How is an outside user will know about the VM identifiers? How will the vstorage look like?
[WIP]
How is an ordinary user going to open a vault on a newly added retail VM?
[WIP]
What are the structural differences between retail and institutional VMs?
[WIP]
How is an institutional user going to be granted access to an institutional VM?
[WIP]
How is an institutional user going to open a vault on an institutional VM?
[WIP]
Is this new way of storing VMs going to cause any changes how vault lifecycles are carried out?
[WIP]

New Approach to Retail VMs

Just to clarify if I understood your approach, the structure of VaultManagers stores will be similar to the following?
Retail/Institutional VMs Store

Key (collateralBrand)
Value (VM store)

stAtom
stAtomStore

stOsmo
stOsmoStore

stAtomStore

Key (VM identifier)
Value (VM)

stAtomMananger_1
vaultManager

stAtomMananger_2
vaultManager

How is an outside user will know about the VM identifiers? How will the vstorage look like?
Current structure

published

vaultFactory

managers

manager0

vaults

vault0

New Structure:

How is an outside user will know about the VM identifiers? How will the vstorage look like?
The current structure of vStorage is:
published
│__vaultFactory
│  │__managers
│     │__manager0
│        │__vaults
│           │__vault0
│           │__vault1
│     │__manager1
│        │   ...

Lets assume that we wish to implement the minimum changes possible to keep back compatibility, but still be able to open and query a vaultManager that has the same collateral as other vaultManagers.
If we record on vstorage the Retail and Institutional VMs Store, from which we can fetch the manager index, we could keep the same vstorage structure by simply add a new step on the query process.
Diagram in progress ...

How is an institutional user going to be granted access to an institutional VM?
Assumptions:

the addVaultManager was included based on the new method proposed above that will serve a similar purpose of addVaultType
the PostalService was included to provide a possible solution to distribute the necessary invitation to all whitelisted Institutional addresses

sequenceDiagram

    actor I as Institution
    participant EC as EconCommittee
    participant ECC as EconCommitteeCharter
    participant VD as VaultDirector
    participant PS as PostalService

    I ->> EC: provide account addresses to be whitelisted
    I ->> EC: provide desired collateral and initialParamValues
    Note over I, EC: Should the communication above happen off-chain?
    EC ->> ECC: makeCharterMemberInvitation
    ECC -->> EC: invitationMakers
    note over EC: invitationMakerName: 'VoteOnApiCall'
    note over EC: invitationArgs: [VaultDirector, addNewManager, [collateralIssuer, initialParamValues]]
    EC ->> VD : executeOffer()

    create participant VM as VaultManager
    VD ->> VM: makeVaultManagerKit()
    VM -->> VD: VaultManagerKit
    VD ->> VD: Build invitationMaker for the institution
    Note over VD: { invitationMakers = { GetVmPF = kit.self.getPublicFacet } }
    loop Whitelisted addresses
        VD ->> PS: sendTo(addr, payment)
    end
    PS -->> I: Invitation
    I ->> I: Exercise invitation to fetch VaultManager publicFacet
    I ->> VM: makeVaultInvitation()
    VM -->> I: vaultKit

VaultManager PublicFacet (collateral interface):
  collateral: M.interface('collateral', {
        makeVaultInvitation: M.call().returns(M.promise()),
        getPublicTopics: M.call().returns(TopicsRecordShape),
        getQuotes: M.call().returns(NotifierShape),
        getCompoundedInterest: M.call().returns(RatioShape),
      }),

How is an ordinary user going to open a vault on a newly added retail VM?  (WIP)
The diagram is a working in progress which detail will be improved
sequenceDiagram

   participant sw as User SmartWallet
   participant vd as VaultDirector
   participant vm as VaultManager

    sw ->> vd: getCollateralManager(brandIn, managerIndex)
    vd ->> vd: getVaultManagerStore(brandIn)
    vd ->> vd: getVaultManager(managerIndex)
    vd -->> sw : vaultManagerPublicFacet
    sw ->> vm : makeVaultInvitation()
    vm -->> sw : invitation
    Note over sw, vm: user exercises the invitation
    sw ->> vm : makeVaultKit()
    vm -->> sw : vaultKit

What are the structural differences between retail and institutional VMs?

Current structure of a Retail VaultManager
Vstorage
published
│__vaultFactory
│  │__managers
│     │__manager0
│        │__governance
│        │__metrics
│        │__quotes
│        │__vaults

manager0.governance:
{
  "value": {
    "blockHeight": "14588605",
    "values": [
      {
        "body": {
          "current": {
            "DebtLimit": {
              "type": "amount",
              "value": {
                "brand": "$0.Alleged: IST brand",
                "value": "+500000000000"
              }
            },
            "InterestRate": {
              "type": "ratio",
              "value": {
                "denominator": {
                  "brand": "$0",
                  "value": "+10000"
                },
                "numerator": {
                  "brand": "$0",
                  "value": "+75"
                }
              }
            },
            "LiquidationMargin": {
              "type": "ratio",
              "value": {
                "denominator": {
                  "brand": "$0",
                  "value": "+10000"
                },
                "numerator": {
                  "brand": "$0",
                  "value": "+15000"
                }
              }
            },
            "LiquidationPadding": {
              "type": "ratio",
              "value": {
                "denominator": {
                  "brand": "$0",
                  "value": "+10000"
                },
                "numerator": {
                  "brand": "$0",
                  "value": "+1000"
                }
              }
            },
            "LiquidationPenalty": {
              "type": "ratio",
              "value": {
                "denominator": {
                  "brand": "$0",
                  "value": "+10000"
                },
                "numerator": {
                  "brand": "$0",
                  "value": "+1000"
                }
              }
            },
            "MintFee": {
              "type": "ratio",
              "value": {
                "denominator": {
                  "brand": "$0",
                  "value": "+10000"
                },
                "numerator": {
                  "brand": "$0",
                  "value": "+50"
                }
              }
            }
          }
        },
        "slots": [
          "board0257"
        ]
      }
    ]
  }
}

manager0.metrics:
{
  "value": {
    "blockHeight": "15731831",
    "values": [
      {
        "body": {
          "liquidatingCollateral": {
            "brand": "$0.Alleged: ATOM brand",
            "value": "+0"
          },
          "liquidatingDebt": {
            "brand": "$1.Alleged: IST brand",
            "value": "+0"
          },
          "lockedQuote": null,
          "numActiveVaults": 21,
          "numLiquidatingVaults": 0,
          "numLiquidationsAborted": 0,
          "numLiquidationsCompleted": 21,
          "retainedCollateral": {
            "brand": "$0",
            "value": "+0"
          },
          "totalCollateral": {
            "brand": "$0",
            "value": "+2372752124"
          },
          "totalCollateralSold": {
            "brand": "$0",
            "value": "+79749677"
          },
          "totalDebt": {
            "brand": "$1",
            "value": "+2852358601"
          },
          "totalOverageReceived": {
            "brand": "$1",
            "value": "+0"
          },
          "totalProceedsReceived": {
            "brand": "$1",
            "value": "+622939841"
          },
          "totalShortfallReceived": {
            "brand": "$1",
            "value": "+25127984"
          }
        },
        "slots": [
          "board05557",
          "board0257"
        ]
      }
    ]
  }
}

manager0.quotes:
{
  "value": {
    "blockHeight": "15766049",
    "values": [
      {
        "body": {
          "quoteAmount": {
            "brand": "$0.Alleged: quote brand",
            "value": [
              {
                "amountIn": {
                  "brand": "$1.Alleged: ATOM brand",
                  "value": "+1000000"
                },
                "amountOut": {
                  "brand": "$2.Alleged: IST brand",
                  "value": "+6106876"
                },
                "timer": "$3.Alleged: timerService",
                "timestamp": {
                  "absValue": "+1720433835",
                  "timerBrand": "$4.Alleged: timerBrand"
                }
              }
            ]
          },
          "quotePayment": "$5.Alleged: quote payment"
        },
        "slots": [
          null,
          "board05557",
          "board0257",
          "board05674",
          "board0425",
          null
        ]
      }
    ]
  }
}

manager0.vaults.vault0
{
  "value": {
    "blockHeight": "10445656",
    "values": [
      {
        "body": {
          "debtSnapshot": {
            "debt": {
              "brand": "$0.Alleged: IST brand",
              "value": "+0"
            },
            "interest": {
              "denominator": {
                "brand": "$0",
                "value": "+100"
              },
              "numerator": {
                "brand": "$0",
                "value": "+100"
              }
            }
          },
          "locked": {
            "brand": "$1.Alleged: ATOM brand",
            "value": "+0"
          },
          "vaultState": "closed"
        },
        "slots": [
          "board0257",
          "board05557"
        ]
      }
    ]
  }
}

The retail VMs will continue to follow the current flow where a core-eval proposal is submitted and voted by the BLD stakers.
Regarding the institutional VMs, they will be created via the EconComittee as it is described on this diagram https://github.com/anilhelvaci/agoric-sdk/issues/1#issuecomment-2208664281

@Jorge-Lopes @anilhelvaci - Can you clarify this statement? If a collateral type has already been approved by the BLD stakers - then it's over to the EC to add additional vault types of that already supported collateral type. i.e. new vault types of already supported collateral type shouldn't need to be voted in by BLD stakers.
Similarly for those institutional vaults - if the collateral type has already been added via BLD stakers - i.e. ATOM then the EC should be able to create an institutional ATOM vault from the Econ Gov UI - rather than it needing to go back to BLD stakers. Does both of these flows aligns with what you had in mind?

@Jorge-Lopes @anilhelvaci - Can you clarify this statement? If a collateral type has already been approved by the BLD stakers - then it's over to the EC to add additional vault types of that already supported collateral type. i.e. new vault types of already supported collateral type shouldn't need to be voted in by BLD stakers.
Similarly for those institutional vaults - if the collateral type has already been added via BLD stakers - i.e. ATOM then the EC should be able to create an institutional ATOM vault from the Econ Gov UI - rather than it needing to go back to BLD stakers. Does both of these flows aligns with what you had in mind?

Yes, the flow you described aligns with our design.
I apologize if the previous comment was unclear; it was a draft meant to initiate discussion.
We are currently preparing a new issue as Analysis Milestone: 2. The goal is to provide a clear description of the intended design, supported by necessary diagrams for comprehensive visualization.
This issue will take into account your responses from Analysis Milestone: 1, as well as the recent feedback you provided.


3.x: upgrade MicroProfile GraphQL in Helidon(master) to 2.0-RC3

[x] Upgrade MicroProfile GraphQL in Helidon to 2.0-RC3 or newer
[x] Enable TCK tests (they are currently disabled: tck-graphql/pom.xml:        <skipTests>true</skipTests>)
[x] Verify examples
[x] Update documentation if needed

Will be fixed by https://github.com/oracle/helidon/pull/4147

Validated example.
No documentation update required.


chore: release 3.0.14

:robot: I have created a release *beep* *boop*
3.0.14 (2022-10-13)
Bug Fixes

program chashed when swagger without parameters (bbe6105)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/keq-request/keq-cli/releases/tag/v3.0.14 :sunflower:


Remove pytest-runner from requirements.txt

Already addressed in: https://github.com/TailorDev/Watson/pull/91


Synchronize credentials for IaaS integration

Technology manager credentials are registered in APP and stored encrypted in controller configuration settings. Once the credentials are changed in the OSCM portal they need to be updated in the APP database as well. OSCM should provide for respective synchronization to APP in order to avoid manual procedures and possible lock out here.

Acceptence creteria:

Avoid any tight coupling between BES and APP.

Proposed solution until SSO is avaiable

Internal service in APP implemented as EJB
Connectable via RMI / IIOP only via internal port (non-exposed)
Client connector injected in IdententyServiceBean and notifying APP on password change
No logging of user data


Added browser annotations to image quantities

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
45

Relevant Lines:
45

💛  - Coveralls


Makes the web worker in the web_worker_fib example use a relative path for the web worker

Description
Fixes #3030
The path for the webworker was previously set to be absolute, which was causing the hosted example page to fail to load it.
After this change the example worth both when running trunk serve, as it did before.
It is now works if you run trunk build --public-url web_worker_fib/dist and then statically host the ./examples path.
I am conifident this will work, as the ./ci/build-examples's trunk build uses the public url option
I was unable to get the ./ci/build-examples to run locally
Checklist

[x] cargo make test-flow passes
[x] cargo make lint passes
[x] cargo fmt has been ran
[x] I have reviewed my own code
[x] I have verified that the examples work as intended when statically hosted
[x] I have verified that the examples work as intended when dynamically hosted through trunk
[ ] I have reviewed my own code
[ ] I have added tests

Shout out to @SpanishPear for identifying the issue


".ctor" file not found!

the last command shows an error: New-WindowsOnlineImage -ConfigFilePath $ConfigFilePath
translated to English:
New-Object : Exception when calling ".ctor" with 1 argument(s):
"The specified file could not be found."
In C:\Users\nsrakbr\Desktop\windows-imaging-tools\windows-openstack-imaging-tools\WinImageBuilder.psm1:121 chars:13
+
return (New-Object WIMInterop.WimFile -ArgumentList $WimFilePath)
+
+ CategoryInfo
InvalidOperation: (:) [New-Object], MethodInvocationException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands

guys, i am working on this custom image of windows since days, but i cant go further. can anyone help please?

I ran into the same issue today. My problem was that I didn't mount the Windows ISO. After mounting the ISO (e.g. under E:\), you also have to correctly set the config wim_file_path to the install.wim inside the mounted ISO:
[DEFAULT]
...
wim_file_path=E:\sources\install.wim
...

Check that the [DEFAULT] section for wim_file_path is defined.


Resource name missing after reindexing of subresources

Godot version:
3.3.stable.official
OS/device including version:
OS: Solus x86_64 (Kernel 5.11.12-177.current)
Issue description:
The resource_name of custom resources disappeared. I noticed this in one of my git commits:
- [sub_resource type="Resource" id=1]
- resource_name = "A"
+ [sub_resource type="Resource" id=2]
  script = ExtResource( 2 )
  _value = Vector3( 0, 0, 0 )

As you can see the resources were all reindexed in that commit, but it also removed the resource names. All I did was open the project, play the main scene, and close it again.
The resources in question are custom ones from a GDScript extending Reference.
Steps to reproduce:
I am not quite sure as I did not get godot to reindex the scene manually. It just happens from time to time. Every time it happens the resource names are cleared.
Minimal reproduction project:
As I was not able to find a reliable way to reproduce this I can't really provide a reproduction project.

Here's a reindexing test project with custom resource:
ReindexTest.zip
Remove the Panel2 node, save scene, reload and save again. Resource ids will change. But the names aren't cleared. Would be useful if you provided your project.

I'll try to create a minimal reproduction project based on your test project, thanks! I can't really share the project where the error occurs as I don't have ownership over it.

I am kinda in despair over this issue. So far I had this only happen to custom resources. Today it happened to a built in animation resource:
-[sub_resource type="Animation" id=44]
-resource_name = "reset"
+[sub_resource type="Animation" id=45]
 tracks/0/type = "value"
 tracks/0/path = NodePath("3D to 2D Collection:Projection Origin:_value")
 tracks/0/interp = 1

(full diff in case it can be helpful, but I doubt it. I only use the diff to illustrate the problem.)
What bugs me most is that I really can't seem to find a reproducible way to trigger this. Has anyone any idea that could help in recreating this? I wish I could just share the project :/

I was finally able to reproduce this in the minimal project provided by @KoBeWi in a reliable way :tada:
Turns out it does not happen when deleting Panel 2. But it does happen if you add a new Panel 4 that shares it's resource with Panel 2.
I have uploaded the reproduction here: https://gitlab.com/winston-yallow/debug-resource-names
It has a commit after every step I did to easily see the process. The tag before-reindexing can be used to have the state where the reindexing happens when saving the scene.
In case you need a zipped version of that state:
ReindexTest.zip
Simply open the scene and save it. The resource name will disappear.

The zipped test scene doesn't already have the name. If I add it manually in the tscn and then open and close the scene, it stays there. Could you list the exact steps for the issue to appear?

Oh I'm sorry, I must have zipped from the wrong commit where the error already happened, This one still has the resource name:
ReindexTest.zip
The steps are:

Open scene.
Select panel 2
Press Ctrl C to copy panel 2
Select root node
Press Ctrl V to paste
Save, close scene, open scene, save again.

The process above until step 5 results in a new panel 4 that has the same resource as panel 2. The diff until step 5 is this for me:
+ [node name="Panel4" type="Node" parent="."]
+ script = SubResource( 1 )
+ resource = SubResource( 3 )

Ok this is interesting. The name just dissappears the moment you save the scene 🤔


[Task]: Allow to toggle edges on/off

Task description
Add toggle to show/hide edges, probably the way to go is just change the color to be exactly like the background color

Not needed, we will probably just improve the colors of the edges


import typing fails

typing module fails to import with IronPython. Here's the error:

import typing
Traceback (most recent call last):
File "", line 1, in
File "C:\Program Files\IronPython 2.7\Lib\site-packages\typing.py", line 1788, in
File "C:\Program Files\IronPython 2.7\Lib\abc.py", line 109, in register
File "C:\Program Files\IronPython 2.7\Lib\site-packages\typing.py", line 1249, in __subclasscheck__
File "C:\Program Files\IronPython 2.7\Lib\abc.py", line 154, in __subclasscheck__
File "C:\Program Files\IronPython 2.7\Lib\site-packages\typing.py", line 1128, in _abc_negative_cache_version
AttributeError: 'GenericMeta' object has no attribute '_abc_generic_negative_cache_version'

The issue appears to be something like this:
x = [0]

class TestA(type):
    def __new__(mcls, name, bases, namespace):
        cls = super(TestA, mcls).__new__(mcls, name, bases, namespace)
        cls.a = 2
        return cls

class TestB(TestA):
    def __new__(cls, name, bases, namespace):
        return super(TestB, cls).__new__(cls, name, bases, namespace)
    def __setattr__(self, attr, value):
        x[0] = value

class TestC(object):
    __metaclass__ = TestB

TestC()

assert x[0] == 2

Looks like there's also an interaction with setters so it's more complicated than above:
class Test(type):
    def __new__(cls, name, bases, namespace):
        cls = super(Test, cls).__new__(cls, name, bases, namespace)
        cls.a = 10
        assert not hasattr(cls, "a")
        cls.test = 10
        assert cls.test == 10
        return cls

    @property
    def test(self):
        return self._test

    @test.setter
    def test(self, value):
        self._test = value

    def __setattr__(self, attr, value):
        if attr in ("test", "_test"):
            super(Test, self).__setattr__(attr, value)

class TestMeta(object):
    __metaclass__ = Test

Is there a workaround or fix in Ipy3?


Verification for TehBrian

What is your username and discriminator?
TehBrian
Why did you join Discord Linux?
Because I like Linux! I've not used Linux personally, actually, I just really don't like Windows and when I switch from my current 2010 Macbook I'm going to use Linux.
Where did you hear about Discord Linux?
On the PaperMC Discord server.
What is the passphrase that was assigned to you by the bot?
advertising-towel-creator-fly

From Vix#0011 :
Looks good.  I've given you a temporary role so that you can enter the passphrase in the welcome channel.


Survey App with Js

I would like to contribute to GSSOC'21 by making this project. Please assign me this Project.

/assign

Thank u for assigning me this project.
On Sun, 14 Mar 2021, 8:38 pm Aliya Rahmani, @.***>
wrote:

/assign
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/423#issuecomment-798923669,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4JWRYEPXBEEPXYTXKH4MLTDTGOZANCNFSM4ZD6H7VA
.

Hi I want to work on this.

Hi @Tanu-priya-Roy, these projects have been already made, you can improve that project or if you have something specific with it then please describe in details, what will be the features of that project.

Ok, will do that Sir.
On Tue, 16 Mar 2021, 3:03 pm Harsh Gupta, @.***> wrote:

Hi @Tanu-priya-Roy https://github.com/Tanu-priya-Roy, these projects
have been already made, you can improve that project or if you have
something specific with it then please describe in details, what will be
the features of that project.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/423#issuecomment-800102402,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4JWR6P47GOGMQQWBNUPELTD4QXHANCNFSM4ZD6H7VA
.

I am assigning this issue to you. You can go ahead @Tanu-priya-Roy

Thanks a lot.
On Sat, 3 Apr 2021, 11:31 am Vishal Rajput, @.***>
wrote:

Assigned #423
https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/423
to @Tanu-priya-Roy https://github.com/Tanu-priya-Roy.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/423#event-4547800758,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4JWR44PEZO45KIE2MQTOTTG2VKZANCNFSM4ZD6H7VA
.

@Tanu-priya-Roy Any update?, Kindly reply within 2 days or I have to close it.

Yes, I am working on it.
On Sun, 25 Apr 2021, 1:01 pm Harsh Gupta, @.***> wrote:

@Tanu-priya-Roy https://github.com/Tanu-priya-Roy Any update?, Kindly
reply within 2 days or I have to close it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Vishal-raj-1/Awesome-JavaScript-Projects/issues/423#issuecomment-826274176,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ4JWRZ6P77A73Y6TH3DUDLTKPAMPANCNFSM4ZD6H7VA
.

@Tanu-priya-Roy update??


Crashing with Firmware 11.0.0

I updated my N3DS to latest firmware 11.0.0 yesterday and NTR is not working anymore since then. Is it the known issue and we are developing the newer version of NTR for FW 11.0.0?
Best regard!

You need to use a 10.2 firmware.bin.  https://github.com/44670/BootNTR/issues/36

Can you please give me the download link? Sorry, I'm a newbie

This issue is closed for requesting files.


refmterr 3.2.0

Should add some notes to CHANGELOG.md as well. I know @kpsuperplane added some features to refmterr, but I don't really know what else has been added since the last release (note I already released this version earlier today)

Unbumped ocaml version somehow, closing in favor of a 3.2.1 pr


Prevent outdated settings

Prevent having to restart Obsidian or re-load the plug-in after updating the settings for them to take effect.

Hi, @brianpetro, thank you for your input!


Unable to install llvm --with-ocaml— “cannot create directory”, “cannot copy file” errors

[X] Ran brew update and retried your prior step?
[X] Ran brew doctor, fixed as many issues as possible and retried your prior step?
[?] Confirmed this is a problem with Homebrew/brew and not specific formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/new

I'm trying to install LLVM with ocaml support using brew install llvm --with-lldb --with-ocaml --with-python --with-toolchain (note: I know really nothing about OCaml; I'm just trying to make a tool written in OCaml & C++).
Partway through the first install, it aborted with this error message:
CMake Error at bindings/ocaml/llvm/cmake_install.cmake:39 (file):
  file cannot create directory: /usr/local/lib/ocaml/llvm.  Maybe need
  administrative privileges.
Call Stack (most recent call first):
  bindings/ocaml/cmake_install.cmake:32 (include)
  cmake_install.cmake:56 (include)

“So fine” I said and I did a mkdir /usr/local/lib/ocaml/llvm and tried to install again.  This time I got this error message:
CMake Error at bindings/ocaml/llvm/cmake_install.cmake:39 (file):
  file INSTALL cannot copy file
  "/tmp/llvm-20170317-32737-soia7o/bindings/ocaml/llvm/llvm.mli" to
  "/usr/local/lib/ocaml/llvm/llvm.mli".
Call Stack (most recent call first):
  bindings/ocaml/cmake_install.cmake:32 (include)
  cmake_install.cmake:56 (include)

“So it's having trouble copying things into Homebrew's dir.  I know how to fix that.” I thought and proceeded to run sudo chown -R capnslipp:admin /usr/local; sudo chmod -R g+w /usr/local.  I also checked that there wasn't anything serious or llvm/ocaml-related reported by brew doctorand brew uninstalled a few things just for the sake of cleanliness.
Running the install takes about an hour on my machine (LLVM is kind of a big deal), so I wanted to avoid any further issue so I ran chmod 777 /usr/local/lib/ocaml/llvm before trying the install again:
CMake Error at bindings/ocaml/llvm/cmake_install.cmake:39 (file):
  file cannot create directory: /usr/local/lib/ocaml/llvm.  Maybe need
  administrative privileges.
Call Stack (most recent call first):
  bindings/ocaml/cmake_install.cmake:32 (include)
  cmake_install.cmake:56 (include)

“Wait, what?  It deleted the dir and then complains that it can't recreate it? WTF?”
Frustrated at this point, I decided that the simplest solution was to just run the install as root (naughty, I know) and then chmod/chown everything back to capnslipp:admin afterwards.  So I chmoded `brew to be owned by root:
$ which brew
/usr/local/bin/brew
$ chown root:admin /usr/local/bin/brew
$ chown -h root:admin /usr/local/bin/brew
$ ls -l /usr/local/bin/brew
lrwxr-xr-x  1 root  admin  20 Sep 24 12:44 /usr/local/bin/brew -> ../Homebrew/bin/brew
 ls -l /usr/local/Homebrew/bin/brew
-rwxr-xr-x  1 root  admin  1681 Mar  7 17:23 /usr/local/Homebrew/bin/brew

and then tried the install again as root:
$ sudo -u root -H bash
$ brew install llvm --with-lldb --with-ocaml --with-toolchain
Error: Running Homebrew as root is extremely dangerous and no longer supported.
As Homebrew does not drop privileges on installation you would be giving all
build scripts full access to your system.

“Wait, really?  Well WTF do I do now?”
At this point I'm completely stuck.  I've just spent the better part of a day trying to build & run some polygon-tri optimization tool I found on GitHub (and am thus still unsure whether it'll fit my needs yet, much less integrated with our build system) and am stuck on either of two issues:

llvm's ocaml stuff must do some weird *ish with what user it decides to run under.
Homebrew apparently doesn't let the user (me) retain control over my computer— it seems to simply refuse to run as root even though I fully understand and accept all consequences this may entail, and release Homebrew and associated parties of any damages or ill effects, including but not limited to injury or death, from any responsibility.

Halp?  This level of frustration to a skilled and seasoned dev shouldn't be happening.  I'm on the verge of downloading llvm & and doing all the other stuff that brew would do by hand as root, just to get it to f-ing work.  I might even reboot into single user mode for good measure.  Please help before I regret everything I may end up doing in the next 24 hours— critical deadlines are justification for just about anything, you know.

Thanks for reporting this. Yes, I can reproduce this issue with 4.0.0. I did previously have --with-opam working with 3.9, so I'm checking now whether 3.9 is still OK or if it has come down with the same flu.

It works fine with 3.9, and this is llvm 4 specific. @JCount has a fix for you.

This should fix it:
diff --git a/Formula/llvm.rb b/Formula/llvm.rb
index f627060c37..7fcd7e08e7 100644
--- a/Formula/llvm.rb
+++ b/Formula/llvm.rb
@@ -242,6 +242,7 @@ class Llvm < Formula

     mktemp do
       if build.with? "ocaml"
+        args << "-DLLVM_OCAML_INSTALL_PATH=#{lib}/ocaml"
         ENV["OPAMYES"] = "1"
         ENV["OPAMROOT"] = Pathname.pwd/"opamroot"
         (Pathname.pwd/"opamroot").mkpath

Ok, I just merged the fix, so you should be able to do brew update; brew install llvm --with-lldb --with-ocaml --with-python --with-toolchain.

Closed via https://github.com/Homebrew/homebrew-core/pull/11223.

Alright, thank you for the help.  However, now I'm getting a different error (I'm not sure if it's related to the original issue or not).
My build now fails on ==> opam install ocamlfind ctypes
The relevant erroring & env section in the log file listed (~/Library/Logs/Homebrew/llvm/03.opam) are:
…
[ocamlfind: ./configure] Command started
[ERROR] The compilation of ocamlfind failed at "./configure -bindir
        /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/bin
        -sitelib
        /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/lib
        -mandir
        /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/man
        -config
        /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/lib/findlib.conf
        -no-custom -no-topfind".
[ocamlfind: ocamlfind remove] Command started
[ocamlfind: ./configure] Command started
[ocamlfind: make uninstall] Command started
[ocamlfind: rm] Command started

#=== ERROR while installing ocamlfind.1.7.1 ===================================#
# opam-version         1.2.2
# os                   darwin
# command              ./configure -bindir /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/bin -sitelib /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/lib -mandir /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/man -config /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/lib/findlib.conf -no-custom -no-topfind
# path                 /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/build/ocamlfind.1.7.1
# compiler             system (4.04.0)
# exit-code            1
# env-file             /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/build/ocamlfind.1.7.1/ocamlfind-8351-6cc03f.env
# stdout-file          /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/build/ocamlfind.1.7.1/ocamlfind-8351-6cc03f.out
# stderr-file          /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/build/ocamlfind.1.7.1/ocamlfind-8351-6cc03f.err
### stdout ###
…

Also of note (and what I believe to be the core problem here is what's in ~/Library/Logs/Homebrew/llvm/build.sandbox.log:
Mar 18 16:48:37 sandboxd[5560]: ruby(7748) deny forbidden-exec-sugid
Mar 18 16:49:41 sandboxd[5560]: sh(8458) deny forbidden-exec-sugid
Mar 18 16:49:41 sandboxd[5560]: sh(8532) deny forbidden-exec-sugid
Mar 18 16:49:41 sandboxd[5560]: opam(8533) deny forbidden-exec-sugid
Mar 18 16:49:42 sandboxd[5560]: ruby(8536) deny forbidden-exec-sugid
Mar 18 16:49:50 sandboxd[5560]: sh(8551) deny forbidden-exec-sugid

We use time to filter sandbox log. Therefore, unrelated logs may be recorded.

I suspect sandbox is the culprit because I additionally tried:

stopping brew just before ==> opam install ocamlfind ctypes
went to https://opam.ocaml.org/packages/ocamlfind/ocamlfind.1.7.1/ and downloaded the tar.gz of ocamlfind.1.7.1
unzipped and placed it at /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/build/ocamlfind.1.7.1/
cded to /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/build/ocamlfind.1.7.1/
and ran ./configure -bindir /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/bin -sitelib /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/lib -mandir /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/man -config /private/tmp/homebrew/llvm-20170318-7747-1iwkfz4/opamroot/system/lib/findlib.conf -no-custom -no-topfind

And that run without any errors, as did running make all afterwards.  Continuing the brew process, of course, tried the ./configure … again, failed, and aborted.

After discovering and adding the --no-sandbox to my invocation (making it brew install llvm --with-lldb --with-ocaml --with-toolchain --no-sandbox), llvm built & installed as expected.  Thanks!


show recent artifacts

Let's show them all

Job gh:yegor256/jpeek#44 assigned to @yegor256, please go ahead (policy).

@rultor release, tag is 0.10.2

Bug was reported: +15 points just awarded to @yegor256, total is +4915.

@rultor release, tag is 0.10.2

@yegor256 OK, I will release it now. Please check the progress here

Manual assignment of issues is discouraged, see par.19: -5 points just awarded to @yegor256, total is +4915.

Job gh:yegor256/jpeek#44 is now out of scope.

Order was successfully finished: +30 points just awarded to @yegor256, total is +4945.

@rultor release, tag is 0.10.2

@yegor256 Done! FYI, the full log is here (took me 15min)


Fixed jsdoc description

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes

Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

I closed it for retrying. sorry.


Close button doesn't match accent color on mainnet

For example, the close button on the PaymentView

Cannot reproduce